Server and notification program

Abstract

To provide a server capable of making an owner of a vehicle grasp which share device has newly executed a registration request of a share key.SOLUTION: The management server 70 manages information related to digital keys that can be registered in the vehicle 20. The digital key includes a shared key that can be registered in plurality in the same vehicle 20. The plurality of devices include a share device that stores information regarding a share key and an owner device 40 that is a device belonging to an owner of the vehicle 20. The friend device 51 and the non-friend device 52 are share devices. The management server 70 transmits, to the owner devices 40, an entry notice M61 including information for identifying the friend devices 51 that have made entry requests for storing information on new share keys in other devices.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a server and a notification program. [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 Publication No. 2023-184349 Summary of the Invention [Problem to be solved by the invention]

[0004] When there are multiple devices functioning as digital keys for a vehicle, it is difficult for the owner of the vehicle to know which device has made a registration request to enable another person's device to function as the digital key for the vehicle. [Means for solving the problem]

[0005] A server for solving the above problem communicates with a vehicle and multiple devices and manages information about digital keys that can be registered to the vehicle. The digital keys include shared keys that can be registered multiple times to the same vehicle. The multiple devices include a shared device that stores information about the shared key and a device belonging to the owner of the vehicle. The server transmits a registration notification to the device belonging to the vehicle owner, the registration notification including information identifying the shared device that has made a registration request to store information about the new shared key in another device.

[0006] A notification program for solving the above problem is stored in a storage device of a device in a digital key system that causes multiple devices to store information about digital keys that can be registered to a vehicle and causes the devices to function as the digital keys for the vehicle. The digital keys include shared keys that can be registered to the same vehicle. The multiple devices include a shared device that stores information about the shared key and a device belonging to the owner of the vehicle. When a shared device sends a registration request to store information about a new shared key in another device, the notification program causes a processing circuit of the shared device that sent the registration request to execute a process to send a registration notification including information identifying the shared device to the device belonging to the vehicle owner. [Effects of the Invention]

[0007] The server and notification program allow the vehicle owner to know which share device has newly executed a share key registration request. [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 the data in the database. [Figure 5] FIG. 5 is an explanatory diagram showing a series of processes performed by the management system when an owner key is registered. [Figure 6] FIG. 6 is an explanatory diagram showing a series of processes performed by the management system when a friend key is registered. [Figure 7] FIG. 7 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is registered. [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 for displaying registration information performed by the management system of the first embodiment. [Figure 11] FIG. 11 is a diagram showing a display example of an image presented by a device as registration information. [Figure 12] FIG. 12 is an explanatory diagram showing a series of processes for displaying deletion information performed by the management system of the first embodiment. [Figure 13] FIG. 13 is a diagram showing an example of an image displayed by a device as deletion information. [Figure 14] FIG. 14 is an explanatory diagram showing a series of processes for displaying registration information performed by the management system of the second embodiment. [Figure 15] FIG. 15 is a schematic diagram showing a friend device according to the third embodiment. [Figure 16] FIG. 16 is a schematic diagram illustrating a notification unit in the management system of the third embodiment. [Figure 17]FIG. 17 is an explanatory diagram showing a series of processes for displaying registration information performed by the management system of the third embodiment. [Figure 18] FIG. 18 is an explanatory diagram showing a series of processes for displaying deletion information performed by the management system of the third embodiment. [Figure 19] FIG. 19 is an explanatory diagram showing a series of processes for displaying registration information performed by a management system according to a modified example of the third embodiment. [Figure 20] FIG. 20 is a schematic diagram showing a non-friend device according to the fourth and fifth embodiments. [Figure 21] FIG. 21 is a schematic diagram showing a notification unit in the management system according to the fourth and fifth embodiments. [Figure 22] FIG. 22 is an explanatory diagram showing a series of processes for displaying registration information performed by the management system of the fourth embodiment. [Figure 23] FIG. 23 is an explanatory diagram showing a series of processes for displaying deletion information performed by the management system of the fourth embodiment. [Figure 24] FIG. 24 is an explanatory diagram showing a series of processes for displaying registration information performed by the management system of the fifth embodiment. [Figure 25] FIG. 25 is a schematic diagram showing the transmission of notifications in the management systems of the first and second embodiments. [Figure 26] FIG. 26 is a schematic diagram illustrating the transmission of a notification in the management system of the third embodiment. [Figure 27] FIG. 27 is a schematic diagram showing the transmission of notifications in the management systems of the fourth and fifth embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0009] (First embodiment) The management system 10 according to the first embodiment will be described below with reference to FIGS. 1 to 13 and 25. FIG.

[0010] <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 server 70 manages information related to a plurality of digital keys that can be registered to a vehicle 20. There is a standard for digital keys, the Car Connectivity Consortium (CCC). Matters related to the digital keys in this embodiment comply with the CCC. The management system 10 includes the vehicle 20, a plurality of devices 30, a device server 60, and the management server 70.

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

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

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

[0014] 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 execution device 27 executes the vehicle program PV, causing the execution device 27 to store and delete the authentication information AT. The authentication information AT is information for authenticating the digital key so that the vehicle 20 can be controlled using the digital key when the digital key is used. The authentication information AT is provided for each digital key to be authenticated. The execution device 27 is a CPU. The execution device 27 executes the vehicle program PV to perform processes related to the storage and deletion of the authentication information AT. The authentication information AT is information related to the digital key.

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

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

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

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

[0019] 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. In other words, the key information DK is information related to the digital key.

[0020] 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 in the OS. The execution unit 36 ​​executes the device program PD to perform processes related to the storage and deletion of key information DK. The execution unit 36 ​​is a processing circuit.

[0021] The multiple devices 30 include multiple devices 40BO belonging to the owner of the vehicle 20 and multiple shared devices 50. The owner device 40 is one of the devices 40BO belonging to the owner of the vehicle 20. The owner device 40 stores owner key information DKO indicating the owner key KO as key information DK. The owner key information DKO is information related to the owner key KO. Only one owner key KO can be registered to one vehicle 20. Therefore, only one owner key KO exists for one vehicle 20.

[0022] The device 40BO belonging to the owner of the vehicle 20 is not limited to the owner device 40. The device 41, the device 42, and the device 43 shown in FIG.

[0023] The device 40BO belonging to the owner of the vehicle 20 is an information processing terminal owned by the owner of the vehicle 20. The information processing terminal is, for example, a personal computer, a smartphone, a tablet terminal, a wearable terminal, etc. Examples of wearable terminals include a ring-type terminal worn on the wrist and a necklace-type terminal worn around the neck. Note that, among the multiple shared devices 50, the shared device 50 owned by the owner of the vehicle 20 is also a device 40BO belonging to the owner of the vehicle 20.

[0024] The device 40BO belonging to the owner of the vehicle 20 may be a server. For example, when a rental business operator and a sharing business operator are the owners of the vehicle 20, the device 40BO belonging to the owner of the vehicle 20 may be a server.

[0025] The device 40BO belonging to the owner of the vehicle 20 may not store the owner key information DKO. For example, none of the device 41, the device 42, and the device 43 stores the owner key information DKO. The device 40BO belonging to the owner of the vehicle 20 may not store the key information DK. For example, none of the device 41, the device 42, and the device 43 stores the key information DK.

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

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

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

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

[0030] As shown in FIG. 1, the shared device 50 stores shared key information DKS indicating a shared key KS as key information DK. The shared key information DKS is information related to the shared key KS. 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.

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

[0032] The friend key KF is a shared key KS registered based on a registration request D21 sent directly from the owner device 40, as will be described later. The registration request D21 is a request to store friend key information DKF, which is key information DK, in the device 30. In other words, the registration request D21 is a request to store information related to a new shared key KS in another device 30.

[0033] The non-friend key KN is a shared key KS registered based on a registration request D31 from a friend device 51, as will be described later. The registration request D31 is a request to store non-friend key information DKN, which is new shared key information DKS, in the device 30. In other words, the registration request D31 is a request to store information related to the new shared key KS in another device 30. 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 other than the owner device 40.

[0034] Note that a state in which a digital key is registered means that the digital key is usable. That is, when a digital key is registered, the vehicle 20 stores authentication information AT corresponding to the key information DK, and the device 30 stores key information DK corresponding to the authentication information AT. 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. If the key information DK is information related to the shared key KS, the authentication information AT corresponding to the key information DK is also information related to the shared key KS.

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

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

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

[0038] 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 device 50 that stores the shared key information DKS. For example, it is set as an identifiable name for each shared device 50 by operation from the owner device 40. The authority information ATP7 is information that indicates the range of functions that can be performed by the device 30 that stores the authority information ATP7.

[0039] The range of executable functions is, for example, the number of share keys KS that can be requested to be registered, the range of vehicle 20 functions that can be implemented by authenticating the digital key, etc. For example, the number of friend keys KF that the owner device 40 can request to be registered is greater than the number of non-friend keys KN that the friend device 51 can request to be registered.

[0040] The range of executable functions of the vehicle 20 indicates, for example, possible controls among control of starting the engine of the vehicle 20, control of turning on the power supply of the vehicle 20, and control of unlocking and locking the doors of the vehicle 20. For example, if the range of executable functions of the vehicle 20 is the above-mentioned three controls, the range of executable functions of the vehicle 20 is wider than if the range of executable functions of the vehicle 20 is only control of unlocking and locking the doors of the vehicle 20. More specifically, the range of functions of the vehicle 20 that the friend device 51 can execute is the above-mentioned three functions, while the range of functions of the vehicle 20 that the non-friend device 52 can execute is control of turning on the power supply of the vehicle 20 and control of unlocking and locking the doors of the vehicle 20.

[0041] 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 the first type of device 30 communicates is different from the device server 60 with which the second type of device 30 communicates. Each device server 60 relays communication with the management server 70, so that the different types of devices 30 can communicate with the management server 70 via the device server 60. Note that Fig. 1 illustrates only one device server 60.

[0042] <Administration Server 70> The management server 70 manages the digital key. 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.

[0043] The storage device 72 stores a server program PS, a notification program PM, and a database DB. When the server program PS is executed by the execution device 71, the execution device 71 registers a digital key in the database DB and deletes the digital key from the database DB. When the notification program PM is executed by the execution device 71, the execution device 71 executes a process of sending notifications indicating that a digital key has been registered and deleted to the owner device 40 and the shared device 50. When the execution device 71 executes the notification program PM, the execution device 71 executes a process of sending notifications indicating that a digital key has been registered and deleted to the owner device 40 and the shared device 50. The execution device 71 is a processing circuit.

[0044] In the database DB, for each of a plurality of digital keys, the corresponding vehicle 20 and the registered device 30 are associated with each other. In the database DB, data DA is separated for each vehicle 20. When a digital key is registered, the management server 70 stores, in the data DA, information indicating the device 30 that stores key information DK indicating the digital key.

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

[0046] A state in which digital keys are registered to seven devices 30 for one vehicle 20 will be described. 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. The digital key registered to the first device 30A is referred to as the first digital key. The digital key registered to the second device 30B is referred to as the second digital key. The digital key registered to the third device 30C is referred to as the third digital key. The digital key registered to the fourth device 30D is referred to as the fourth digital key. The digital key registered to the fifth device 30E is referred to as the fifth digital key. The digital key registered to the sixth device 30F is referred to as the sixth digital key. The digital key registered to the seventh device 30G is referred to as the seventh digital key.

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

[0048] In the data DA, the devices 30 whose digital key type is registered as a shared key KS are the second device 30B, the third device 30C, the fourth device 30D, the fifth device 30E, the sixth device 30F, and the seventh device 30G. That is, the second device 30B, the third device 30C, the fourth device 30D, the fifth device 30E, the sixth device 30F, and the seventh device 30G are shared devices 50. That is, the second digital key, the third digital key, the fourth digital key, the fifth digital key, the sixth digital key, and the seventh digital key are all shared keys KS.

[0049] More specifically, in the data DA, the devices 30 whose digital key type is registered as a friend key KF are the second device 30B and the fifth device 30E. That is, the second device 30B and the fifth device 30E are friend devices 51. In the data DA, the devices 30 whose digital key type is registered as a non-friend key KN are the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G. That is, the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G are non-friend devices 52.

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

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

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

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

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

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

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

[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 tracking 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 tracking request D23 is a request to store new authentication information AT in the vehicle 20. In other words, the key tracking request D23 is a request to store information about the digital key 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 registration 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 second device 30B, which is 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 third device 30C 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, name information ATP5, and authority information ATP7. Note that the validity start time information ATP3, expiration date information ATP4, name information ATP5, and authority information ATP7 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] Upon receiving the key track request D33, the management server 70 transmits a storage request D34 to the vehicle 20, requesting storage of the authentication package ATP, which is information about the digital key. In other words, the key track request D33 is a request to have the vehicle 20 store information about the digital key.

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

[0103] 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 third device 30C 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.

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

[0105] <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 second device 30B, which is the friend device 51, based on the deletion reservation D41.

[0106] 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 signal that reserves the deletion of the non-friend key KN.

[0107] The deletion reservation D41 includes a signal requesting the 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 the 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 the deletion reservation D41 was received. The deletion reservation D41 includes name information ATP5, which is information identifying the friend device 51 that transmits the deletion reservation D41 to the management server 70. The friend device 51 then transmits the deletion reservation D41 of the non-friend key KN to the management server 70.

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

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

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

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

[0112] In step S66, the management server 70 generates a deletion command D42 to delete 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 command D42 to the third device 30C, which is the non-friend device 52.

[0113] Thereafter, when the non-friend device 52 receives the deletion command D42, it performs the processing of step S67. In step S67, the non-friend device 52 deletes the non-friend key information DKN in accordance with the deletion command 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 command D42 has been completed.

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

[0115] In step S69, the management server 70 generates a deletion command D43 for the authentication information AT. The deletion command 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 command D43 to the vehicle 20.

[0116] Thereafter, when the vehicle 20 receives the deletion command D43, the vehicle 20 performs the processing of step S70. In step S70, the vehicle 20 deletes the authentication information AT for authenticating the non-friend key KN that is the target of the deletion reservation D41 in accordance with the deletion command 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 command D43 has been completed.

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

[0118] 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 to the friend device 51 a deletion completion notification M44 indicating that the series of deletions of the non-friend key KN in accordance with the deletion reservation D41 has been completed.

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

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

[0121] When a predetermined operation requesting deletion of the non-friend key KN is executed in the third device 30C, which is 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.

[0122] 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 second device 30B, which is the friend device 51, indicating that the non-friend key information DKN has been deleted.

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

[0124] After processing in step S82, the management server 70 performs processing in step S84. In step S84, the management server 70 generates a deletion command D51 to delete 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 command D51 to the vehicle 20.

[0125] Thereafter, when vehicle 20 receives deletion command D51, vehicle 20 performs the 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 command D51. Then, vehicle 20 transmits completion notification M53 to management server 70 indicating that deletion of authentication information AT in accordance with deletion command D51 has been completed.

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

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

[0128] <Process to notify that a registration request D31 has been received> Next, a series of processes in the management system 10 for notifying the owner device 40, which is a device 40BO belonging to the owner of the vehicle 20, that a registration request D31 has been made for a non-friend key KN, which is a shared key KS, will be described. This series of processes is performed during the series of processes shown in Fig. 7 that the management system 10 performs to register the non-friend key KN. In this series of processes, the management server 70 also notifies shared devices 50 other than the shared device 50 that made the registration request D31 that a registration request D31 has been made.

[0129] 7, the management system 10 performs a series of processes to register the non-friend key KN. An operation is performed in the second device 30B, which is the friend device 51, to request the third device 30C to register the non-friend key KN, and as a result, the management server 70 receives non-friend key information DKN and a key track request D33 for the non-friend key KN. Thereafter, the management server 70 performs the process of step S49. In step S49, the management server 70 manages the registration of the non-friend key KN.

[0130] As shown in FIG. 10, after performing the processing of step S49, 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. Having received the authentication package ATP and the storage request D34, the vehicle 20 performs the processing of step S50. The processing of step S50 is the same as the processing of step S50 shown in FIG. 7. After completing the registration management, the management server 70 transmits a key track completion notification M33 to the third device 30C. Having received the completion notification M33, the non-friend device 52 performs the processing of step S51. The processing of step S51 is the same as the processing of step S51 shown in FIG. 7.

[0131] Thereafter, the management server 70 performs processing of step S91. In step S91, the management server 70 generates a registration notification M61 and a registration notification M62. The registration notification M61 and the registration notification M62 include the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 from the non-friend key information DKN received by the management server 70. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that made the registration request D31. In other words, the registration notification M61 and the registration notification M62 include information that identifies the shared device 50 that made the registration request D31 to store new shared key information DKS in another device 30.

[0132] The management server 70 transmits a registration notification M61 to the owner device 40. That is, the management server 70 transmits to the owner device 40 the registration notification M61 including information identifying the shared device 50 that has issued a registration request D31 to store new shared key information DKS in another device 30.

[0133] The management server 70 transmits a registration notification M62 to the fifth device 30E, which is a friend device 51. The fifth device 30E is a friend device 51 that has not made a registration request D31, which is a request to store non-friend key information DKN in the third device 30C. The management server 70 transmits the registration notification M62, which includes information identifying the share device 50 that has made the registration request D31 to store new share key information DKS in another device 30, to a share device 50 other than the share device 50 that has made the registration request D31.

[0134] <Processing performed by the owner device 40 upon receiving the registration notification M61> Upon receiving the registration notification M61, the owner device 40 performs the process of step S92. In step S92, the owner device 40 displays the registration information based on the registration notification M61.

[0135] The owner device 40 presents, as registration information, information identifying the shared device 50 that issued the registration request D31 to the HMI 32. For example, as shown in Fig. 11, the owner device 40 displays a name identifying the second device 30B in the "Second Device" field based on the signature information ATP1 included in the registration notification M61.

[0136] The owner device 40 presents, as registration information, the latest date and time at which the newly registered non-friend key KN can be used to the HMI 32. For example, as shown in Fig. 11 , the owner device 40 displays, on the HMI 32, an image indicating the latest date and time at which the non-friend key KN registered in the third device 30C can be used, based on the expiration date information ATP4 included in the registration notification M61.

[0137] The owner device 40 presents, as registration information, a name identifying the shared device 50 that stores the non-friend key information DKN indicating the newly registered non-friend key KN to the HMI 32. For example, as shown in Fig. 11, the owner device 40 displays a name identifying the third device 30C in the "Third Device" field based on the name information ATP5 included in the registration notification M61.

[0138] The owner device 40 presents to the HMI 32 the range of functions executable by the shared device 50 that stores, as registration information, non-friend key information DKN indicating the newly registered non-friend key KN. For example, as shown in Fig. 11 , the owner device 40 displays on the HMI 32 an image indicating the range of functions executable by the third device 30C, including unlocking and locking control of the doors of the vehicle 20, based on the authority information ATP7 included in the registration notification M61.

[0139] <Processing performed by the friend device 51 upon receiving the registration notification M62> When the fifth device 30E, which is the friend device 51, receives the registration notification M62, it performs the process of step S93. In step S93, the friend device 51 displays the registration information based on the registration notification M62.

[0140] The friend device 51 presents, as registration information, information identifying the shared device 50 that issued the registration request D31 to the HMI 32. For example, as shown in FIG. 11 , the friend device 51 displays a name identifying the second device 30B in the “Second Device” field based on the signature information ATP1 included in the registration notification M62.

[0141] The friend device 51 presents, as registration information, the latest date and time at which the newly registered non-friend key KN can be used to the HMI 32. For example, as shown in Fig. 11 , the friend device 51 displays, on the HMI 32, an image indicating the latest date and time at which the non-friend key KN registered in the third device 30C can be used, based on the expiration date information ATP4 included in the registration notification M62.

[0142] The friend device 51 presents, as registration information, a name identifying the shared device 50 that stores the non-friend key information DKN indicating the newly registered non-friend key KN to the HMI 32. For example, as shown in Fig. 11 , the friend device 51 displays a name identifying the third device 30C in the "Third Device" field based on the name information ATP5 included in the registration notification M62.

[0143] The friend device 51 presents to the HMI 32 the range of functions executable by the shared device 50 that stores, as registration information, non-friend key information DKN indicating the newly registered non-friend key KN. For example, as shown in Fig. 11 , the friend device 51 displays, on the HMI 32, an image indicating the range of functions executable by the third device 30C, namely, unlocking and locking the doors of the vehicle 20, based on the authority information ATP7 included in the registration notification M62. Thereafter, the management system 10 ends this series of processes.

[0144] <Processing to notify that a deletion request D71 has been made> Next, a series of processes will be described for notifying the owner device 40 that a deletion request D71 has been made to delete the shared key information DKS stored in the shared device 50 in the management system 10. In this series of processes, the management server 70 also notifies other shared devices 50 other than the shared device 50 that made the deletion request D71 that a deletion request D71 has been made.

[0145] 12, the management system 10 performs a series of processes to delete the non-friend key KN. In the second device 30B, which is the friend device 51, an operation to request deletion of the non-friend key KN registered in the third device 30C is executed, and the friend device 51 first performs the process of step S101. In step S101, the friend device 51 generates a deletion request D71 for the non-friend key KN. The deletion request D71 is a signal requesting deletion of the non-friend key KN.

[0146] The deletion request D71 includes a signal requesting the deletion of the non-friend key KN, digital key identification information ST3 indicating the non-friend key KN, and name information ATP5 that is a name identifying the second device 30B that sent the deletion request D71. The friend device 51 sends the deletion request D71 for the non-friend key KN to the management server 70.

[0147] When the management server 70 receives a deletion request D71 for the non-friend key KN from the friend device 51, it performs processing in step S102. In step S102, the management server 70 generates a deletion command D42 for deleting the non-friend key information DKN indicating the non-friend key KN that is the target of the deletion request D71. In other words, the deletion request D71 is a signal for deleting the shared key information DKS stored in the shared device 50. The deletion command D42 generated by the management server 70 in step S102 is the same as the deletion command D42 generated by the management server 70 in step S66 shown in FIG. 8. The management server 70 transmits the deletion command D42 to the third device 30C, which is the non-friend device 52.

[0148] Thereafter, the management server 70 performs the process of step S103. In step S103, the management server 70 generates a deletion notification M71 and a deletion notification M72. The deletion notification M71 and the deletion notification M72 include name information ATP5, which is a name that identifies the second device 30B that made the deletion request D71. That is, the deletion notification M71 and the deletion notification M72 include information that identifies the shared device 50 that made the deletion request D71. The deletion notification M71 and the deletion notification M72 include name information ATP5, which is a name that identifies the third device 30C that stores the non-friend key information DKN that is the target of the deletion request D71.

[0149] The management server 70 transmits a deletion notification M71 to the owner device 40. That is, when the management server 70 receives a deletion request D71 to delete the shared key information DKS stored in the shared device 50, the management server 70 transmits to the owner device 40 a deletion notification M71 including information identifying the shared device 50 that made the deletion request D71.

[0150] The management server 70 transmits a deletion notification M72 to the fifth device 30E, which is a friend device 51. The fifth device 30E is a friend device 51 that has not issued a deletion request D71, which is a request to delete the non-friend key KN registered in the third device 30C. The deletion request D71 is a request to delete the shared key information DKS stored in the share device 50. When the management server 70 receives the deletion request D71, it transmits a deletion notification M72, which includes information identifying the share device 50 that issued the deletion request D71, to share devices 50 other than the share device 50 that issued the deletion request D71.

[0151] When the non-friend device 52 receives the deletion command D42, it performs the process of step S67 shown in Fig. 8. After performing the process of step S67, the non-friend device 52 transmits a completion notification M42 to the management server 70. After receiving the completion notification M42 from the non-friend device 52, the management server 70 performs the processes from step S69 onwards shown in Fig. 8.

[0152] <Processing performed by the owner device 40 upon receiving the deletion notification M71> Upon receiving the deletion notification M71, the owner device 40 performs the process of step S104. In step S104, the owner device 40 displays the deletion information based on the deletion notification M71.

[0153] The owner device 40 presents, as the deletion information, information identifying the shared device 50 that made the deletion request D71 and information identifying the shared device 50 that received the deletion command D43 on the HMI 32. For example, as shown in FIG. 13, the owner device 40 displays a name identifying the second device 30B in the "Second Device" field based on name information ATP5 that identifies the second device 30B that made the deletion request D71. For example, as shown in FIG. 13, the owner device 40 displays a name identifying the third device 30C in the "Third Device" field based on name information ATP5 that identifies the third device 30C that receives the deletion command D42.

[0154] <Processing performed by the friend device 51 upon receiving the deletion notification M72> Upon receiving the deletion notification M72, the friend device 51 performs processing in step S105. In step S105, the friend device 51 displays deletion information based on the deletion notification M72. In step S105, the friend device 51 presents, as deletion information, information identifying the shared device 50 that issued the deletion request D71 and information identifying the shared device 50 that received the deletion command D43 on the HMI 32. For example, as shown in FIG. 13, the friend device 51 displays a name identifying the second device 30B in the "Second Device" field based on name information ATP5 that identifies the second device 30B that issued the deletion request D71. For example, as shown in FIG. 13, the friend device 51 displays a name identifying the third device 30C in the "Third Device" field based on name information ATP5 that identifies the third device 30C that receives the deletion command D42. The management system 10 then terminates this series of processes.

[0155] <Operation of the First Embodiment> As shown in FIG. 25, when a registration request D31 is made for a non-friend key KN, which is a shared key KS, the management server 70 transmits a registration notification M61 to the owner device 40. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The registration request D31 is a request to store information about a new shared key KS in another device 30. The registration notification M61 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that made the registration request D31 for the non-friend key KN.

[0156] <Effects of the first embodiment> (1-1) The management server 70 can allow the owner of the vehicle 20 to know which shared device 50 has made a registration request D31, which is a request to store information about a new shared key KS in another device 30.

[0157] (1-2) When the management server 70 receives the key track request D33, it sends a registration notification M61 to the owner device 40. The key track request D33 is a request to store the authentication information AT in the vehicle 20. The authentication information AT corresponds to the non-friend key information DKN, which is information about the shared key KS. Therefore, the authentication information AT is also information about the shared key KS. The registration notification M61 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that made the registration request D31 for the non-friend key KN.

[0158] This allows the owner of the vehicle 20 to understand which shared device 50 has made the registration request D31 and based on which information about the shared key KS that will be newly stored in the vehicle 20 is information about the shared key KS that will be stored in the vehicle 20.

[0159] 25, the management server 70 also transmits the registration notification M62 to the fifth device 30E, which is a friend device 51 other than the second device 30B that made the registration request D31. This allows the management server 70 to allow the user of the friend device 51 other than the second device 30B that made the registration request D31 to know which shared device 50 has newly made the registration request D31.

[0160] (1-4) When the management server 70 receives the deletion request D71, it transmits a deletion notification M71 to the owner device 40. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The deletion request D71 is a request to delete the non-friend key information DKN stored in the third device 30C. The non-friend key information DKN is information related to the shared key KS. The deletion notification M71 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that made the deletion request D71. This allows the management server 70 to allow the owner of the vehicle 20 to know which shared device 50 made the deletion request D71.

[0161] (1-5) When the management server 70 receives the deletion request D71, it also transmits a deletion notification M72 to the fifth device 30E, which is a friend device 51 other than the second device 30B that made the deletion request D71. In this way, the management server 70 allows the user of the friend device 51 other than the second device 30B that made the deletion request D71 to know which shared device 50 made the deletion request D71.

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

[0163] <Example of changes regarding registration notifications M61 and M62> The management server 70 does not have to transmit the registration notification M61 to the owner device 40 as long as it transmits the registration notification M61 to the device 40B0 that belongs to the owner of the vehicle 20. For example, of the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 25, the management server 70 may transmit the registration notification M61 only to the device 41. Furthermore, the management server 70 may transmit the registration notification M61 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the management server 70 may transmit the registration notification M61 to the owner device 40, the device 41, the device 42, and the device 43.

[0164] The management server 70 may transmit the registration notification M62 to a non-friend device 52. That is, the management server 70 may transmit the registration notification M62 to a share device 50 other than the friend device 51 that made the registration request D31.

[0165] The non-friend device 52 may issue a registration request D31. Even in this case, the management server 70 transmits a registration notification M62 to the owner device 40. The non-friend device 52 may issue a registration request D31. In this case, the management server 70 may transmit a registration notification M62 to a share device 50 other than the non-friend device 52 that issued the registration request D31.

[0166] If the management server 70 transmits the registration notification M61 to the device 40BO belonging to the owner of the vehicle 20, the management server 70 does not need to be able to transmit the registration notification M62 to a shared device 50 other than the shared device 50 that made the registration request D31.

[0167] If the management server 70 sends the registration notification M61 to the device 40BO that belongs to the owner of the vehicle 20, it does not need to send the deletion notification M72 to shared devices 50 other than the shared device 50 that made the deletion request D71. If the management server 70 sends the registration notification M61 to the device 40BO that belongs to the owner of the vehicle 20, it does not need to be able to send the deletion notification M71 to the device 40BO that belongs to the owner of the vehicle 20.

[0168] As long as the registration notification M61 can be transmitted to the device 40BO belonging to the owner of the vehicle 20, the storage device that stores the notification program PM is not limited to the storage device 72 of the management server 70. For example, the notification program PM may be stored in a storage device (not shown) of the device server 60. In this case, a processing circuit (not shown) of the device server 60 executes the notification program PM to transmit the registration notification M61 to the device 40BO belonging to the owner of the vehicle 20. The notification program PM causes a processing circuit (not shown) of the device server 60 to execute a process of transmitting the registration notification M61 to the device 40BO belonging to the owner of the vehicle 20.

[0169] The series of processes for displaying the registration information is not limited to the example of the first embodiment. For example, the management server 70 may perform the process of step S91 before transmitting the storage request D34 and the authentication package ATP to the vehicle 20.

[0170] The information displayed as registration information is not limited to the example in the first embodiment. The registration information may include information for identifying the shared device 50 that issued the registration request D31. That is, the expiration date information ATP4, name information ATP5, and authority information ATP7 shown in FIG. 11 may not be included in the registration information. For example, the registration information may include vehicle identification information ST1 in addition to the information shown in FIG. 11.

[0171] <Example of changes regarding deletion notices M71 and M72> The management server 70 may not necessarily transmit the deletion notification M71 to the owner device 40 as long as the deletion notification M71 is transmitted to the device 40B0 that belongs to the owner of the vehicle 20. For example, the management server 70 may transmit the deletion notification M71 only to the device 41 among the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 25 . The management server 70 may also transmit the deletion notification M71 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the management server 70 may transmit the deletion notification M71 to the owner device 40, the device 41, the device 42, and the device 43.

[0172] If the management server 70 sends the deletion notification M71 to the device 40BO belonging to the owner of the vehicle 20, it does not need to send the deletion notification M72 to a shared device 50 other than the shared device 50 that made the deletion request D71.

[0173] The management server 70 may send the deletion notification M72 to a non-friend device 52. That is, the management server 70 may send the deletion notification M72 to a share device 50 other than the friend device 51 that made the deletion request D71.

[0174] The non-friend device 52 may issue a deletion request D71. Even in this case, the management server 70 transmits a deletion notification M72 to the device 40BO belonging to the owner of the vehicle 20.

[0175] The non-friend device 52 may issue a deletion request D71. In this case, the management server 70 may transmit the registration notification M62 to the sharing device 50 other than the non-friend device 52 that issued the deletion request D71.

[0176] The series of processes for displaying the deletion information is not limited to the example in the first embodiment. For example, the management server 70 may perform the process of step S103 before transmitting the deletion command D42 to the non-friend device 52.

[0177] The information displayed as deletion information is not limited to the example in the first embodiment. The deletion information may include information identifying the shared device 50 that issued the deletion request D71. That is, the name information ATP5 of the shared device 50 that received the deletion command D42 shown in FIG. 13 does not have to be included in the deletion information. For example, the deletion information may include vehicle identification information ST1 in addition to the information shown in FIG. 13.

[0178] (Second embodiment) The management system 10 according to the second embodiment will be described below with reference to Figures 7, 10, 11, 14, and 25. In the second embodiment, the timing at which the management server 70 transmits the registration notification to the owner device 40 and the shared device 50 is different from that in the first embodiment. The following description will focus on the differences from the first embodiment, and the description of the same points will be simplified or omitted.

[0179] <Pairing Between Vehicle 20 and Third Device 30C> The non-friend device 52 shown in Fig. 14 is the third device 30C that has been registered as the non-friend device 52 through the series of processes shown in Fig. 7. That is, the non-friend key KN has been registered in the third device 30C based on the registration request D31 from the second device 30B.

[0180] In step S111, the vehicle 20 and the third device 30C are paired with each other. When the pairing is completed, the vehicle 20 establishes a secure channel for data communication with the third device 30C.

[0181] Thereafter, the vehicle 20 verifies whether the authentication information AT stored in the vehicle 20 matches the authentication package ATP in the non-friend key information DKN stored in the third device 30C. The third device 30C verifies whether the authentication package ATP in the non-friend key information DKN stored in the third device 30C matches the authentication information AT stored in the vehicle 20.

[0182] When both the vehicle 20 and the third device 30C determine that the authentication package ATP and the authentication information AT match, pairing is completed. When pairing is completed, the third device 30C is validated as a non-friend key KN. This makes the third device 30C usable as a non-friend key KN for the vehicle 20. The third device 30C then proceeds to step S112. Note that in the second embodiment, if pairing is not completed, the third device 30C cannot be used as a non-friend key KN for the vehicle 20.

[0183] <Generating and sending the activation completion notification M80> In step S112, the third device 30C generates an activation completion notification M80. The activation completion notification M80 is a notification sent by the shared device 50 when the shared device 50 is activated as a digital key. The activation completion notification M80 includes the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 from the non-friend key information DKN stored in the third device 30C. The third device 30C transmits the activation completion notification M80 to the management server 70.

[0184] When the management server 70 receives the activation completion notification M80 from the third device 30C, it performs the process of step S113. In step S113, the management server 70 generates a registration notification M81 and a registration notification M82. The registration notification M81 and the registration notification M82 include the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 included in the activation completion notification M80 received by the management server 70. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that issued the registration request D31 shown in FIG. 7. In other words, the registration notification M81 and the registration notification M82 include information that identifies the shared device 50 that issued the registration request D31 to store new shared key information DKS in another device 30.

[0185] The management server 70 transmits a registration notification M81 to the owner device 40. That is, the management server 70 transmits to the owner device 40 the registration notification M81 including information for identifying the shared device 50 that has made the registration request D31.

[0186] The management server 70 transmits the registration notification M82 to the fifth device 30E, which is a friend device 51. The fifth device 30E is a friend device 51 that has not made the registration request D31, which is a request to store the non-friend key information DKN in the third device 30C. In other words, the management server 70 transmits the registration notification M82, which includes information identifying the share device 50 that made the registration request D31, to a share device 50 other than the share device 50 that made the registration request D31.

[0187] <Processing performed by the owner device 40 upon receiving the registration notification M81> Upon receiving the registration notification M81, the owner device 40 performs the process of step S114. In step S92, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M81. For example, as shown in FIG. 11, the owner device 40 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M81. Step S114 is the same as step S92 shown in FIG. 10, and therefore a detailed description thereof will be omitted.

[0188] <Processing performed by the friend device 51 upon receiving the registration notification M82> Upon receiving the registration notification M82, the friend device 51 performs processing in step S115. In step S93, the friend device 51 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M82. For example, as shown in FIG. 11 , the friend device 51 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M82. Step S115 is the same as step S93 in the first embodiment, and therefore a detailed description thereof will be omitted. Thereafter, the management system 10 ends this series of processing.

[0189] <Operation of the Second Embodiment> When the management server 70 receives an activation completion notification M80 sent by the non-friend device 52 when it is activated as a digital key, the owner device 40 receives a registration notification M81 from the management server 70, as shown in Figure 25. The owner device 40 is a device 40BO belonging to the owner of the vehicle 20. The registration notification M81 includes signature information ATP1, which is information that identifies the friend device 51 that made the registration request D31 of the non-friend key KN to the non-friend device 52 that sent the activation completion notification M80.

[0190] <Effects of the second embodiment> (2-1) The management server 70 allows the owner of the vehicle 20 to know which shared device 50 executed the registration request D31 to register the newly validated shared device 50.

[0191] (2-2) As shown in Fig. 25, the management server 70 also transmits the registration notification M82 to other share devices 50 than the share device 50 that made the registration request D31. This allows the management server 70 to allow the user of the share device 50 to know which share device 50 executed the registration request D31 to register the newly enabled share device 50.

[0192] <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 with each other to the extent that they are not technically inconsistent.

[0193] <Example of changes regarding activation completion notification M80> The activation completion notification M80 may include only the signature information ATP1 from the non-friend key information DKN stored in the third device 30C.

[0194] The activation completion notification M80 does not have to include the signature information ATP1 if the registration notification M81 and the registration notification M82 include information identifying the shared device 50 that issued the registration request D31 to store new shared key information DKS in another device 30. For example, if the management server 70 that receives the activation completion notification M80 can select appropriate signature information ATP1 by referring to the database DB stored in the storage device 72, the activation completion notification M80 does not have to include the signature information ATP1.

[0195] <Example of changes regarding registration notifications M81 and M82> The management server 70 may not necessarily transmit the registration notification M81 to the owner device 40 as long as the management server 70 transmits the registration notification M81 to the device 40B0 that belongs to the owner of the vehicle 20. For example, the management server 70 may transmit the registration notification M81 only to the device 41 among the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 25 . The management server 70 may also transmit the registration notification M81 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the management server 70 may transmit the registration notification M81 to the owner device 40, the device 41, the device 42, and the device 43.

[0196] If the management server 70 sends the registration notification M81 to the device 40BO belonging to the owner of the vehicle 20, the management server 70 does not need to be able to send the registration notification M82 to a shared device 50 other than the shared device 50 that made the registration request D31.

[0197] The management server 70 may transmit the registration notification M82 to a non-friend device 52. In other words, the management server 70 may transmit the registration notification M82 to a shared device 50 other than the friend device 51 that made the registration request D31.

[0198] (Third embodiment) A management system 10 according to the third embodiment will be described below with reference to FIGS. 3, 7, 8, 11 to 13, 15 to 18, and 26. In the third embodiment, the second device 30B, which is a friend device 51, transmits a registration notification M91 and a deletion notification M101 to the owner device 40. In the third embodiment, the friend device 51 also transmits a registration notification M92 and a deletion notification M102 to the fifth device 30E, which is another friend device 51. In the third embodiment, the second device 30B, which is a friend device 51, stores contact information for the first device 30A and the fifth device 30E in the storage device 37. The following description will focus on differences from the first embodiment, and descriptions of the same points will be simplified or omitted.

[0199] 15, in a friend device 51, which is a shared device 50, the storage device 37 stores a notification program PM2. The notification program PM2 is a program that, when executed by the execution device 36, causes the execution device 36 to function as a notification unit 51M.

[0200] 16, the execution device 36 executes the notification program PM2, causing the execution device 36 to function as a notification unit 51M. In the third embodiment, the friend device 51 includes the notification unit 51M.

[0201] <Process to notify that a registration request D31 has been received> A series of processes in the management system 10 of the third embodiment will be described. In this series of processes, the friend device 51 notifies the owner device 40 that it has made a registration request D31. In this series of processes, the friend device 51 also notifies the shared devices 50 other than the friend device 51 that has made the registration request D31 that it has made the registration request D31.

[0202] The execution device 36 starts execution of the notification program PM2 when the friend device 51 transmits a registration request D31 for storing new shared key information DKS in another device 30. Specifically, the execution device 36 starts execution of the notification program PM2 when the friend device 51 generates non-friend key information DKN.

[0203] Fig. 17 is an explanatory diagram showing the processing from step S44 onwards in Fig. 7. By performing the series of processing shown in Fig. 7, the non-friend key KN is registered in the third device 30C based on the registration request D31 from the second device 30B.

[0204] Step S44 in FIG. 17 is the same as step S44 in FIG. 7. Step S45 in FIG. 17 is the same as step S45 in FIG. 7. Step S46 in FIG. 17 is the same as step S46 in FIG. 7. That is, the friend device 51 generates non-friend key information DKN in the processing of step S46. 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 indicating that the completed non-friend key information DKN has been uploaded to the URL link to the third device 30C. As shown in FIG. 3, the completed non-friend key information DKN 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.

[0205] After generating the non-friend key information DKN in step S46, the friend device 51 starts executing the notification program PM2. When the friend device 51 starts executing the notification program PM2, it first performs the process of step S121.

[0206] In step S121, the friend device 51 generates a registration notification M91 and a registration notification M92 based on the non-friend key information DKN generated in step S46 by the friend device 51. The registration notification M91 and the registration notification M92 include the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 from the information included in the non-friend key information DKN.

[0207] The signature information ATP1 is information for identifying the second device 30B, which is the friend device 51 that made the registration request D31. In other words, the registration notification M91 and the registration notification M92 include information for identifying the shared device 50 that made the registration request D31 to store new shared key information DKS in another device 30.

[0208] The friend device 51 transmits a registration notification M91 to the owner device 40. That is, the friend device 51 transmits to the owner device 40 a registration notification M61 including information identifying the shared device 50 that has made the registration request D31 to store the new shared key information DKS in another device 30.

[0209] The friend device 51 transmits a registration notification M92 to the fifth device 30E, which is also a friend device 51. The fifth device 30E is a friend device 51 that has not made the registration request D31, which is a request to store the non-friend key information DKN in the third device 30C. The friend device 51 transmits a registration notification M62, including information identifying the share device 50 that has made the registration request D31 to store the new share key information DKS in another device 30, to a share device 50 other than the share device 50 that has made the registration request D31.

[0210] <Processing Performed by the Owner Device 40 Upon Receiving the Registration Notification M91> Upon receiving the registration notification M91, the owner device 40 performs the process of step S122. In step S122, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M91. For example, as shown in FIG. 11 , the owner device 40 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M91. Step S122 is the same as step S92 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0211] <Processing performed by the friend device 51 upon receiving the registration notification M92> Upon receiving the registration notification M92, the friend device 51 performs processing in step S123. In step S123, the friend device 51 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M92. For example, as shown in FIG. 11 , the friend device 51 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M92. Step S123 is the same as step S93 in the first embodiment, and therefore a detailed description thereof will be omitted. Thereafter, the management system 10 ends this series of processing.

[0212] <Processing to notify that a deletion request D71 has been made> Next, a series of processes for notifying the owner device 40 that a deletion request D71 has been made in the management system 10 of the third embodiment will be described. In this series of processes, the friend device 51 notifies the owner device 40 that a deletion request D71 has been made. In this series of processes, the friend device 51 also notifies other sharing devices 50 other than the sharing device 50 that made the deletion request D71 that a deletion request D71 has been made.

[0213] After the friend device 51 transmits the deletion request D71 to the management server 70, the execution apparatus 36 shown in FIG. 15 starts executing the notification program PM2. 18, the management system 10 performs a series of processes to delete the non-friend key KN. When an operation to request deletion of the non-friend key KN is executed in the second device 30B, which is the friend device 51, the friend device 51 first performs the process of step S101.

[0214] In step S101, the friend device 51 generates a deletion request D71 for the non-friend key KN. The deletion request D71 includes a signal requesting the deletion of the non-friend key KN, digital key identification information ST3 indicating the non-friend key KN, and name information ATP5 that is a name identifying the second device 30B that transmits the deletion request D71. The friend device 51 transmits the deletion request D71 for the non-friend key KN to the management server 70. Thereafter, the friend device 51 performs the process of step S131.

[0215] In step S131, the friend device 51 generates a deletion notification M101 and a deletion notification M102. The deletion notification M101 and the deletion notification M102 include name information ATP5, which is a name that identifies the second device 30B that made the deletion request D71. In other words, the deletion notification M101 and the deletion notification M102 include information that identifies the shared device 50 that made the deletion request D71. The deletion notification M101 and the deletion notification M102 include name information ATP5, which is a name that identifies the third device 30C that stores the non-friend key information DKN that is the target of the deletion request D71.

[0216] The friend device 51 transmits a deletion notification M101 to the owner device 40. That is, after transmitting a deletion request D71 to delete the shared key information DKS stored in the shared device 50, the friend device 51 transmits the deletion notification M101 to the owner device 40.

[0217] The friend device 51 transmits the deletion notification M102 to the fifth device 30E, which is also the friend device 51. The fifth device 30E is a friend device 51 that has not made the deletion request D71, which is a request to delete the non-friend key KN registered in the third device 30C. In other words, after transmitting the deletion request D71 to delete the shared key information DKS stored in the shared device 50, the friend device 51 transmits the deletion notification M102 to the shared device 50 other than the shared device 50 that made the deletion request D71.

[0218] When the management server 70 receives a deletion request D71 for the non-friend key KN from the friend device 51, it performs the process of step S102. In step S102 shown in FIG. 18, the management server 70 generates a deletion command D42, similar to step S102 shown in FIG. 12. The management server 70 transmits the deletion command D42 to the third device 30C, which is the non-friend device 52. When the non-friend device 52 receives the deletion command D42, it performs the process of step S67 shown in FIG. 8. After performing the process of step S67, the non-friend device 52 transmits a completion notification M42 to the management server 70. After receiving the completion notification M42 from the non-friend device 52, the management server 70 performs the processes from step S69 onwards shown in FIG. 8.

[0219] <Processing Performed by the Owner Device 40 Upon Receiving the Deletion Notification M101> When the owner device 40 receives the deletion notification M101, it performs the process of step S132. In step S132, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that made the deletion request D71 and information identifying the shared device 50 that will receive the deletion command D42. Step S132 is the same as step S104 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0220] <Processing performed by the friend device 51 upon receiving the deletion notification M102> When the friend device 51 receives the deletion notification M101, it performs the process of step S133. In step S133, the friend device 51 presents, to the HMI 32, information identifying the share device 50 that made the deletion request D71 and information identifying the share device 50 that will receive the deletion command D42. Step S133 is the same as step S105 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0221] <Operation of the Third Embodiment> When the second device 30B, which is a friend device 51, sends a registration request D31, the notification program PM2 causes the execution device 36 of the second device 30B to execute processing to send a registration notification M91 to the owner device 40, as shown in FIG. 26. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The registration request D31 is a request to store information about a new shared key KS in a third device 30C, which is another device 30. The registration notification M91 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is a friend device 51 that sent the registration request D31.

[0222] <Effects of the third embodiment> (3-1) The notification program PM2 allows the owner of the vehicle 20 to know which friend device 51 has newly transmitted the registration request D31.

[0223] (3-2) When the second device 30B generates new non-friend key information DKN after sending the registration request D31, the notification program PM2 causes the execution device 36 of the second device 30B to execute a process of sending a registration notification M91 to the owner device 40. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The registration notification M91 includes signature information ATP1, which is information that identifies the friend device 51 that made the registration request D31. In this way, the notification program PM2 allows the owner of the vehicle 20 to know which friend device 51 has sent the new registration request D31 for the non-friend key KN.

[0224] (3-3) When the friend device 51 sends the registration request D31, the notification program PM2 causes the execution unit 36 ​​of the friend device 51 to execute a process of sending a registration notification M92 to the fifth device 30E as well, as shown in FIG. 26. The fifth device 30E is a shared device 50 other than the second device 30B, which is the friend device 51 that sent the registration request D31. The registration notification M92 includes signature information ATP1, which is information that identifies the second device 30B, which is the friend device 51 that sent the registration request D31. In this way, the notification program PM2 allows the user of the shared device 50 other than the second device 30B, which is the friend device 51 that sent the registration request D31, to know which friend device 51 sent the registration request D31.

[0225] (3-4) After the second device 30B transmits the deletion request D71 to the management server 70, the notification program PM2 causes the execution unit 36 ​​of the friend device 51 to execute a process of transmitting a deletion notification M101 to the owner device 40, as shown in FIG. 26. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The deletion request D71 is a request to delete non-friend key information DKN stored in the third device 30C, which is a non-friend device 52. The non-friend key information DKN is information related to the shared key KS. The deletion notification M101 includes name information ATP5. The name information ATP5 is information that identifies the second device 30B, which is the friend device 51 that transmitted the deletion request D71 to the management server 70.

[0226] As a result, the notification program PM2 allows the execution device 36 of the friend device 51 that sent the deletion request D71 to know which friend device 51 sent the deletion request D71, and allows the owner of the vehicle 20 to know which friend device 51 sent the deletion request D71.

[0227] (3-5) After the second device 30B transmits the deletion request D71 to the management server 70, the notification program PM2 causes the execution unit 36 ​​of the second device 30B to execute processing to also transmit a deletion notification M102 to the fifth device 30E, as shown in FIG. 26. The deletion request D71 is a request to delete the non-friend key information DKN stored in the third device 30C, which is a non-friend device 52. The non-friend key information DKN is information related to the shared key KS. The deletion notification M102 includes name information ATP5. The name information ATP5 is information that identifies the second device 30B, which is the friend device 51 that transmitted the deletion request D71 to the management server 70. The fifth device 30E is a friend device 51 other than the second device 30B that transmitted the deletion request D71.

[0228] As a result, the notification program PM2 allows the execution device 36 of the friend device 51 that sent the deletion request D71 to know which friend device 51 sent the deletion request D71, and allows the user of the friend device 51 other than the friend device 51 that sent the deletion request D71 to know which friend device 51 sent the deletion request D71.

[0229] <Modification of the third embodiment> The third embodiment can be modified as follows: The third embodiment and the following modifications can be combined and implemented within the scope of no technical contradiction.

[0230] <Examples of changes to registration notifications M91 and M92> The notification program PM2 may not cause the execution device 36 of the friend device 51 to execute a process of transmitting the registration notification M91 to the owner device 40, as long as the execution device 36 of the friend device 51 executes a process of transmitting the registration notification M91 to the device 40B belonging to the owner of the vehicle 20. For example, the notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of transmitting the registration notification M91 to only the device 41 among the devices 40B belonging to the owner of the vehicle 20 shown in FIG. 26 . The notification program PM2 may also cause the execution device 36 of the friend device 51 to execute a process of transmitting the registration notification M91 to multiple devices 40B belonging to the owner of the vehicle 20. For example, the notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of transmitting the registration notification M91 to the owner device 40, the device 41, the device 42, and the device 43.

[0231] The notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of sending a registration notification M92 to a non-friend device 52. In other words, the notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of sending the registration notification M92 to a shared device 50 other than the friend device 51 that made the registration request D31.

[0232] If the notification program PM2 causes the execution unit 36 ​​of the friend device 51 to execute a process of sending a registration notification M91 to the device 40BO belonging to the owner of the vehicle 20, the notification program PM2 does not need to cause the execution unit 36 ​​of the friend device 51 to execute a process of sending a registration notification M92 to a shared device 50 other than the shared device 50 that made the registration request D31.

[0233] If the notification program PM2 causes the execution device 36 of the friend device 51 to execute a process to send a registration notification M91 to the device 40B0 that belongs to the owner of the vehicle 20, the notification program PM2 does not need to cause the execution device 36 of the friend device 51 to execute a process to send a deletion notification M102 to a shared device 50 other than the shared device 50 that issued the deletion request D71. If the notification program PM2 causes the execution device 36 of the friend device 51 to execute a process to send a registration notification M91 to the device 40B0 that belongs to the owner of the vehicle 20, the notification program PM2 does not need to execute a process to send a deletion notification M101 to the device 40B0 that belongs to the owner of the vehicle 20.

[0234] The timing at which the notification program PM2 causes the execution device 36 of the friend device 51 to execute a series of processes for transmitting the registration notification M91 to the device 40BO belonging to the owner of the vehicle 20 is not limited to when the friend device 51 generates new non-friend key information DKN. For example, the execution device 36 may start executing the notification program PM2 after transmitting the registration request D31 to the relay server. Below, with reference to FIGS. 7 and 19, a description is given of the series of processes that the notification program PM2 causes the execution device 36 of the friend device 51 to execute.

[0235] <Process to notify that a registration request D31 has been received> After transmitting the registration request D31 to the relay server, the execution unit 36 ​​starts executing the notification program PM2.

[0236] Fig. 19 is an explanatory diagram showing the processing from step S41 onwards in Fig. 7. By performing the series of processing shown in Fig. 7, the non-friend key KN is registered in the third device 30C based on the registration request D31 from the second device 30B.

[0237] Step S41 in Fig. 19 is the same as step S41 in Fig. 7. That is, in step S41, the friend device 51 transmits a registration request D31 for the non-friend key KN to a relay server (not shown).

[0238] After transmitting the registration request D31 to the relay server, the friend device 51 starts executing the notification program PM2. When the friend device 51 starts executing the notification program PM2, the friend device 51 performs the process of step S141.

[0239] In step S141, the friend device 51 generates a registration notification M111 and a registration notification M112. The registration notification M111 and the registration notification M112 include the name information ATP5 that the friend device 51 has stored in the storage device 37.

[0240] The friend device 51 transmits a registration notification M111 to the owner device 40. That is, the friend device 51 transmits the registration notification M111 including information identifying the shared device 50 that made the registration request D31 to the owner device 40. The owner device 40 is a device 40BO that belongs to the owner of the vehicle 20.

[0241] The friend device 51 transmits the registration notification M112 to the fifth device 30E, which is also the friend device 51. The fifth device 30E is a friend device 51 that has not made the registration request D31, which is a request to store the non-friend key information DKN in the third device 30C. In other words, the friend device 51 transmits the registration notification M112, which includes information for identifying the share device 50 that made the registration request D31, to a share device 50 other than the share device 50 that made the registration request D31.

[0242] Thereafter, the friend device 51 performs the process of step S42. The process of step S42 is the same as the process of step S42 shown in FIG. 7. After performing the process of step S42, the friend device 51 transmits invitation information IV2 to the third device 30C. Thereafter, upon receiving the invitation information IV2, the third device 30C performs the process of step S43. The process of step S43 is the same as the process of step S43 shown in FIG. 7. Thereafter, the management system 10 performs a series of processes from step S44 onwards shown in FIG. 7.

[0243] <Processing Performed by the Owner Device 40 Upon Receiving the Registration Notification M111> Upon receiving the registration notification M111, the owner device 40 performs the process of step S142. In step S142, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that made the registration request D31, based on the registration notification M91. For example, the owner device 40 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the name information ATP5 included in the registration notification M111.

[0244] <Processing Performed by the Friend Device 51 Upon Receiving the Registration Notification M112> Upon receiving the registration notification M112, the friend device 51 performs processing in step S143. In step S143, the friend device 51 presents, to the HMI 32, information identifying the friend device 51 that issued the registration request D31, based on the registration notification M112. For example, the friend device 51 displays, on the HMI 32, an image indicating a name that identifies the second device 30B, based on the name information ATP5 included in the registration notification M112.

[0245] <Example of changes regarding deletion notices M101 and M102> The notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of transmitting the deletion notification M101 to the device 40B0 that belongs to the owner of the vehicle 20, but may not cause the execution device 36 of the friend device 51 to execute a process of transmitting the deletion notification M101 to the owner device 40. For example, the notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of transmitting the deletion notification M101 to only the device 41 among the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 26. The notification program PM2 may also cause the execution device 36 of the friend device 51 to execute a process of transmitting the deletion notification M101 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of transmitting a registration notification M91 to the owner device 40, the device 41, the device 42, and the device 43.

[0246] The notification program PM2 may cause the execution unit 36 ​​of the friend device 51 to execute a process of sending the deletion notification M102 to the non-friend device 52. In other words, the notification program PM2 may cause the execution unit 36 ​​of the friend device 51 to execute a process of sending the deletion notification M102 to a shared device 50 other than the friend device 51 that made the deletion request D71.

[0247] The notification program PM2 may cause the execution unit 36 ​​of the friend device 51 to execute a process of sending a deletion notification M101 to the device 40BO belonging to the owner of the vehicle 20, but may not cause the execution unit 36 ​​to execute a process of sending a deletion notification M102 to a shared device 50 other than the shared device 50 that made the deletion request D71.

[0248] The series of processes for displaying the deletion information is not limited to the example of the third embodiment. For example, the friend device 51 may perform the process of step S103 before transmitting the deletion request D71 to the management server 70.

[0249] (Fourth embodiment) A management system 10 according to a fourth embodiment will be described below with reference to FIGS. 7, 8, 11 to 13, 20 to 23, and 27. In the fourth embodiment, a third device 30C, which is a non-friend device 52, transmits a registration notification and a deletion notification to a first device 30A, which is an owner device 40, and a fifth device 30E, which is a shared device 50. In the fourth embodiment, the third device 30C, which is a non-friend device 52, stores contact information for the first device 30A and the fifth device 30E in the storage device 37. The following description will focus on differences from the first embodiment, and descriptions of the same points will be simplified or omitted.

[0250] 20, in the fourth embodiment, the storage device 37 of the non-friend device 52, which is a shared device 50, stores a notification program PM3. The notification program PM3 is a program that causes the execution device 36 to function as a notification unit 52M when executed by the execution device 36.

[0251] 21, the execution device 36 executes the notification program PM3, causing the execution device 36 to function as a notification unit 52M. In the fourth embodiment, the non-friend device 52 has the notification unit 52M.

[0252] <Process to notify that a registration request D31 has been received> A series of processes in the management system 10 of the fourth embodiment will be described. In this series of processes, the non-friend device 52 notifies the owner device 40 that a registration request D31 has been made. In this series of processes, the non-friend device 52 also notifies other sharing devices 50 other than the sharing device 50 that made the registration request D31 that the registration request D31 has been made.

[0253] The execution unit 36 ​​shown in FIG. 21 starts executing the notification program PM3 when the device 30 stores the non-friend key information DKN and is registered as a non-friend device 52.

[0254] Figure 22 is an explanatory diagram showing the processing after step S49 in Figure 7. Step S49 in Figure 22 is the same as step S49 in Figure 7. That is, the non-friend key KN is registered in the third device 30C based on the registration request D31 from the second device 30B.

[0255] As shown in FIG. 22, after performing the processing of step S49, 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. Having received the authentication package ATP and the storage request D34, the vehicle 20 performs the processing of step S50. The processing of step S50 is the same as the processing of step S50 shown in FIG. 7. After completing the registration management, the management server 70 transmits a key track completion notification M33 to the second device 30B. Having received the completion notification M33, the non-friend device 52 performs the processing of step S51. The processing of step S51 is the same as the processing of step S51 shown in FIG. 7.

[0256] Thereafter, the non-friend device 52 performs the process of step S151. In step S151, the non-friend device 52 generates a registration notification M121 and a registration notification M122.

[0257] The registration notification M121 and the registration notification M122 include the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 from the non-friend key information DKN stored in the non-friend device 52. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that made the registration request D31. In other words, the registration notification M121 and the registration notification M122 include information that identifies the shared device 50 that made the registration request D31 to store new shared key information DKS in another device 30.

[0258] The non-friend device 52 transmits a registration notification M121 to the owner device 40. That is, the non-friend device 52 transmits to the owner device 40 the registration notification M121 including information for identifying the shared device 50 that has made the registration request D31 to store the new shared key information DKS in another device 30.

[0259] The non-friend device 52 transmits a registration notification M122 to the fifth device 30E, which is a friend device 51. The fifth device 30E is a friend device 51 that has not made the registration request D31, which is a request to store the non-friend key information DKN in the third device 30C. The registration request D31 is a request to store new shared key information DKS in another device 30. The non-friend device 52 transmits the registration notification M122, which includes information for identifying the shared device 50 that made the registration request D31, to a shared device 50 other than the shared device 50 that made the registration request D31.

[0260] <Processing Performed by the Owner Device 40 Upon Receiving the Registration Notification M121> Upon receiving the registration notification M121, the owner device 40 performs the process of step S152. In step S152, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M121. For example, as shown in FIG. 11 , the owner device 40 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M121. Step S152 is the same as step S92 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0261] <Processing Performed by the Friend Device 51 Upon Receiving the Registration Notification M122> Upon receiving the registration notification M122, the friend device 51 performs processing in step S153. In step S153, the friend device 51 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the registration notification M122. For example, as shown in FIG. 11 , the friend device 51 displays, on the HMI 32, an image indicating a name identifying the second device 30B, based on the signature information ATP1 included in the registration notification M122. Step S153 is the same as step S93 in the first embodiment, and therefore a detailed description thereof will be omitted. Thereafter, the management system 10 ends this series of processing.

[0262] <Processing to notify that a deletion request D71 has been made> Next, a series of processes for notifying the owner device 40 that a deletion request D71 has been made in the management system 10 of the fourth embodiment will be described. In this series of processes, the non-friend device 52 notifies the owner device 40 that a deletion request D71 has been made. In this series of processes, the non-friend device 52 also notifies other sharing devices 50 other than the sharing device 50 that made the deletion request D71 that a deletion request D71 has been made.

[0263] When the execution device 36 shown in FIG. 20 receives the deletion command D43 shown in FIG. 23 from the management server 70, it starts executing the notification program PM3. 23, the management system 10 performs a series of processes to delete the non-friend key KN. When an operation to request deletion of the non-friend key KN registered in the third device 30C is executed in the second device 30B, which is the friend device 51, the friend device 51 first performs the process of step S101.

[0264] In step S101, the friend device 51 generates a deletion request D71 for the non-friend key KN. The deletion request D71 is a signal requesting the deletion of the non-friend key KN. The deletion request D71 includes the signal requesting the deletion of the non-friend key KN, digital key identification information ST3 indicating the non-friend key KN, and name information ATP5 which is a name identifying the second device 30B that transmits the deletion request D71. The friend device 51 transmits the deletion request D71 for the non-friend key KN to the management server 70.

[0265] When the management server 70 receives the request D71 to delete the non-friend key KN from the friend device 51, the management server 70 performs the process of step S160. In step S160, the management server 70 generates a deletion command D43 based on the deletion request D71 to delete the non-friend key information DKN indicating the non-friend key KN that is the target of the deletion request D71. The deletion command D43 includes name information ATP5, which is information that identifies the friend device 51 that transmitted the deletion request D71, which is the cause of the deletion command D43, to the management server 70. The management server 70 transmits the deletion command D43 to the non-friend device 52. Upon receiving the deletion command D43, the non-friend device 52 performs the processing of step S161.

[0266] In step S161, the non-friend device 52 generates a deletion notification M131 and a deletion notification M132 based on the name information ATP5 of the non-friend key information DKN stored in the non-friend device 52 and the deletion command D43. The deletion notification M131 and the deletion notification M132 include name information ATP5, which is a name identifying the second device 30B that made the deletion request D71. In other words, the deletion notification M131 and the deletion notification M132 include information identifying the shared device 50 that made the deletion request D71. The deletion notification M131 and the deletion notification M132 include name information ATP5, which is a name identifying the third device 30C that stores the non-friend key information DKN that is the target of the deletion request D71.

[0267] The non-friend device 52 transmits a deletion notification M131 to the owner device 40. That is, when the non-friend device 52 receives the deletion command D43, it transmits the deletion notification M131 to the owner device 40.

[0268] The non-friend device 52 transmits the deletion notification M132 to the fifth device 30E, which is the friend device 51. The fifth device 30E is a friend device 51 that has not issued the deletion request D71, which is a request to delete the non-friend key KN registered in the third device 30C. In other words, when the non-friend device 52 receives the deletion command D43, it transmits the deletion notification M132 to the sharing device 50 other than the sharing device 50 that issued the deletion request D71.

[0269] <Processing Performed by the Owner Device 40 Upon Receiving the Deletion Notification M131> Upon receiving the deletion notification M131, the owner device 40 performs the process of step S162. In step S162, the owner device 40 presents, to the HMI 32, information identifying the share device 50 that made the deletion request D71 and information identifying the share device 50 that received the deletion command D43, based on the deletion notification M131. Step S162 is the same as step S104 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0270] <Processing performed by the friend device 51 upon receiving the deletion notification M132> Upon receiving the deletion notification M132, the friend device 51 performs processing in step S163. In step S163, the friend device 51 presents, to the HMI 32, information identifying the share device 50 that issued the deletion request D71 and information identifying the share device 50 that received the deletion command D43, based on the deletion notification M132. Step S163 is the same as step S105 in the first embodiment, and therefore a detailed description thereof will be omitted. Thereafter, the management system 10 ends this series of processing.

[0271] <Operation of the Fourth Embodiment> As shown in FIG. 27, the notification program PM3 causes the execution device 36 of the third device 30C, which has been registered in the vehicle 20 as a non-friend device 52 by storing non-friend key information DKN, to execute a process of transmitting the non-friend key information DKN to the owner device 40. The owner device 40 is a device 40B belonging to the owner of the vehicle 20. The non-friend key information DKN is information related to the shared key KS. The registration notification M121 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that sent the registration request D31 to store the non-friend key information DKN in the device 30.

[0272] <Effects of the Fourth Embodiment> (4-1) The notification program PM3 enables the execution device 36 of the non-friend device 52 to make the owner of the vehicle 20 aware of which friend device 51 has newly transmitted the registration request D31.

[0273] (4-2) As shown in FIG. 27, the notification program PM3 causes the execution device 36 of the third device 30C to execute processing to send a registration notification M122 to the fifth device 30E as well. The registration notification M122 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that sent the registration request D31 to store the non-friend key information DKN in the third device 30C. The non-friend key information DKN is information related to the shared key KS. The fifth device 30E is a friend device 51 other than the second device 30B that sent the registration request D31.

[0274] As a result, the notification program PM3 allows the user of a friend device 51 other than the second device 30B that sent the registration request D31 to know which friend device 51 sent the registration request D31 to the execution device 36 of the third device 30C that is registered as a non-friend device 52.

[0275] (4-3). When the non-friend device 52 receives a deletion command D43 from the management server 70, the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute a process of transmitting a deletion notification M131 to the owner device 40, as shown in FIG. 27. The owner device 40 is a device 40B0 that belongs to the owner of the vehicle 20. The deletion command D43 is a command to delete non-friend key information DKN stored in the storage device 37 of the non-friend device 52. The non-friend key information DKN is information related to the shared key KS. The deletion command D43 includes name information ATP5. The name information ATP5 is information identifying the second device 30B, which is the friend device 51 that transmitted the deletion request D71, which caused the deletion command D43, to the management server 70. The deletion notification M131 includes the same name information ATP5 as the deletion command D43.

[0276] As a result, the notification program PM3 allows the execution device 36 of the non-friend device 52 that received the deletion command D43 to know to the owner of the vehicle 20 which friend device 51 sent the deletion request D71 that caused the deletion command D43.

[0277] (4-4) As shown in FIG. 27, when the third device 30C receives a deletion command D43 from the management server 70, the notification program PM3 causes the execution unit 36 ​​of the third device 30C to execute processing to send a deletion notification M132 to the fifth device 30E as well. The third device 30C is a non-friend device 52. The deletion notification M132 includes name information ATP5. The name information ATP5 is information that identifies the second device 30B, which is the friend device 51 that sent the deletion request D71, which caused the deletion command D43, to the management server 70. The fifth device 30E is a friend device 51 other than the second device 30B that sent the deletion request D71.

[0278] As a result, the notification program PM3 allows the execution device 36 of the non-friend device 52 that received the deletion command D43 to know which friend device 51 sent the deletion request D71 that caused the deletion command D43, and allows the user of the friend device 51 other than the friend device 51 that sent the deletion request D71 to know.

[0279] <Modification of the Fourth Embodiment> The above-described fourth embodiment can be modified and implemented as follows: The above-described fourth embodiment and the following modifications of the fourth embodiment can be implemented in combination with each other within the scope of technical compatibility.

[0280] <Examples of changes to registration notifications M121 and M122> The notification program PM3 may not cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the registration notification M121 to the owner device 40, as long as the execution device 36 of the non-friend device 52 executes a process of transmitting the registration notification M121 to the device 40B0 that belongs to the owner of the vehicle 20. For example, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the registration notification M121 to only the device 41 among the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 27. The notification program PM3 may also cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the registration notification M121 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the registration notification M121 to the owner device 40, the device 41, the device 42, and the device 43.

[0281] The notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending a registration notification M122 to the non-friend device 52. In other words, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending the registration notification M122 to a shared device 50 other than the friend device 51 that made the registration request D31.

[0282] · If the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute a process of sending a registration notification M121 to a device 40BO belonging to the owner of the vehicle 20, it does not need to cause the execution device 36 of the non-friend device 52 to execute a process of sending a registration notification M122 to a share device 50 other than the share device 50 that made the registration request D31.

[0283] If the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute processing to send a registration notification M121 to a device 40B0 that belongs to the owner of the vehicle 20, it does not have to cause the execution device 36 of the non-friend device 52 to execute processing to send a deletion notification M132 to a shared device 50 other than the shared device 50 that issued the deletion request D71. If the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute processing to send a registration notification M121 to a device 40B0 that belongs to the owner of the vehicle 20, it does not have to cause the execution device 36 of the non-friend device 52 to execute processing to send a deletion notification M131 to a device 40B0 that belongs to the owner of the vehicle 20.

[0284] <Example of changes regarding removal notices M131 and M132> The notification program PM3 may not cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the deletion notification M131 to the owner device 40, as long as the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute a process of transmitting the deletion notification M131 to the owner device 40. For example, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the deletion notification M131 to only the device 41 among the devices 40B0 belonging to the owner of the vehicle 20 shown in FIG. 27. The notification program PM3 may also cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the deletion notification M131 to multiple devices 40B0 belonging to the owner of the vehicle 20. For example, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the deletion notification M131 to the owner device 40, the device 41, the device 42, and the device 43.

[0285] The notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending a deletion notification M132 to the non-friend device 52. In other words, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending the deletion notification M132 to a shared device 50 other than the friend device 51 that made the deletion request D71.

[0286] The notification program PM2 may cause the execution device 36 of the friend device 51 to execute a process of sending a deletion notification M131 to the device 40BO belonging to the owner of the vehicle 20, but may not cause the execution device 36 to execute a process of sending a deletion notification M132 to a shared device 50 other than the shared device 50 that made the deletion request D71.

[0287] The series of processes for displaying the deletion information is not limited to the example of the fourth embodiment. For example, after performing the process of step S67, the non-friend device 52 may transmit a deletion notification M131 to the device 40BO belonging to the owner of the vehicle 20. After performing the process of step S67, the non-friend device 52 may transmit a deletion notification M132 to the shared device 50.

[0288] (Fifth embodiment) The management system 10 according to the fifth embodiment will be described below with reference to Figures 1, 7, 10, 11, 14, 20, 21, 24, and 27.

[0289] In the fifth embodiment, the third device 30C, which is a non-friend device 52, transmits an activation completion notification M141 to the first device 30A, which is the owner device 40. The third device 30C, which is a non-friend device 52, also transmits an activation completion notification M142 to the fifth device 30E, which is a shared device 50. In the fifth embodiment, the third device 30C, which is a non-friend device 52, stores contact information for the first device 30A and the fifth device 30E in the storage device 37.

[0290] The following description will focus on the differences from the second embodiment, and the description of the same points will be simplified or omitted. 20, in the fifth embodiment, the storage device 37 of the non-friend device 52, which is a shared device 50, stores a notification program PM3. The notification program PM3 is a program that, when executed by the execution device 36, causes the execution device 36 to function as a notification unit 52M.

[0291] 21, the execution device 36 executes the notification program PM3, causing the execution device 36 to function as a notification unit 52M. In the fifth embodiment, the non-friend device 52 has the notification unit 52M.

[0292] <Generation and Transmission of Activation Completion Notification M141 and Activation Completion Notification M142> A series of processes in the management system 10 of the fifth embodiment will be described. In this series of processes, the non-friend device 52 notifies the owner device 40 that a registration request D31 has been made. In this series of processes, the non-friend device 52 also notifies other sharing devices 50 other than the sharing device 50 that made the registration request D31 that the registration request D31 has been made.

[0293] The execution unit 36 ​​shown in FIG. 21 starts executing the notification program PM3 when the non-friend device 52 is validated as the non-friend key KN. The non-friend device 52 shown in Fig. 24 is the third device 30C that has been registered as the non-friend device 52 through the series of processes shown in Fig. 7. The non-friend key KN has been registered in the third device 30C based on the registration request D31 from the second device 30B.

[0294] In step S111, similar to step S111 shown in FIG. 14, pairing is performed between the vehicle 20 and the third device 30C. When pairing is complete, the third device 30C is validated as a digital key. This allows the third device 30C to be used as a non-friend key KN for the vehicle 20. The third device 30C then proceeds to step S171. Note that in the fifth embodiment, similar to the second embodiment, if pairing is not completed, the third device 30C cannot be used as a non-friend key KN for the vehicle 20.

[0295] In step S171, the third device 30C generates an activation completion notification M141 and an activation completion notification M142. The activation completion notification M141 and the activation completion notification M142 are notifications sent by the shared device 50 when the shared device 50 is activated as a digital key. The activation completion notification M141 and the activation completion notification M142 include the signature information ATP1, expiration date information ATP4, name information ATP5, and authority information ATP7 of the non-friend key information DKN stored in the third device 30C. The non-friend device 52 transmits the activation completion notification M141 to the owner device 40. The non-friend device 52 transmits the activation completion notification M142 to the fifth device 30E, which is the friend device 51.

[0296] <Processing Performed by the Owner Device 40 Upon Receiving the Activation Completion Notification M141> Upon receiving the activation completion notification M141, the owner device 40 performs processing in step S172. In step S172, the owner device 40 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the activation completion notification M141. For example, as shown in FIG. 11 , the owner device 40 displays, on the HMI 32, an image indicating a name identifying the second device 30B, which is the shared device 50 that issued the registration request D31, based on the signature information ATP1 included in the activation completion notification M141. Step S172 is the same as step S92 shown in FIG. 10 , and therefore a detailed description thereof will be omitted.

[0297] <Processing Performed by the Friend Device 51 Upon Receiving the Activation Completion Notification M142> Upon receiving the activation completion notification M142, the friend device 51 performs processing in step S173. In step S173, the friend device 51 presents, to the HMI 32, information identifying the shared device 50 that issued the registration request D31, based on the activation completion notification M142. For example, as shown in FIG. 11 , the friend device 51 displays, on the HMI 32, an image indicating a name identifying the second device 30B, which is the shared device 50 that issued the registration request D31, based on the signature information ATP1 included in the activation completion notification M142. Step S173 is the same as step S93 shown in FIG. 10 , and therefore a detailed description thereof will be omitted. Thereafter, the management system 10 ends this series of processing.

[0298] <Operation of the Fifth Embodiment> When the third device 30C, which has non-friend key information DKN stored in the storage device 37, is activated, the notification program PM3 causes the execution device 36 of the third device 30C to execute a process of sending an activation completion notification M141 to the owner device 40, as shown in FIG. 27. The owner device 40 is a device 40B0 belonging to the owner of the vehicle 20. The third device 30C is a non-friend device 52. The activation completion notification M141 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that sent the registration request D31 to store the non-friend key information DKN in the third device 30C.

[0299] <Effects of the Fifth Embodiment> (5-1) The notification program PM3 enables the execution device 36 of the non-friend device 52 to make the owner of the vehicle 20 aware of which friend device 51 has newly transmitted the registration request D31.

[0300] (5-2) As shown in FIG. 27, the notification program PM3 causes the execution device 36 of the third device 30C to execute processing to send an activation completion notification M142 to the fifth device 30E as well. The third device 30C is a non-friend device 52. The activation completion notification M142 includes signature information ATP1. The signature information ATP1 is information that identifies the second device 30B, which is the friend device 51 that sent the registration request D31 to store the non-friend key information DKN in the third device 30C. The fifth device 30E is a friend device 51 other than the second device 30B that sent the registration request D31.

[0301] As a result, the notification program PM3 allows the execution device 36 of the non-friend device 52 to make the user of a friend device 51 other than the friend device 51 that sent the registration request D31 aware of which friend device 51 sent the registration request D31.

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

[0303] The non-friend device 52 may transmit an activation completion notification M141 to the owner device 40 via the device server 60. The non-friend device 52 may transmit an activation completion notification M142 to the fifth device 30E, which is the friend device 51, via the device server 60.

[0304] <Example of changes to activation completion notifications M141 and M142> The validation completion notification M141 and the validation completion notification M142 may include only the signature information ATP1 from the non-friend key information DKN stored in the third device 30C.

[0305] <Example of changes regarding registration notifications M81 and M82> As long as the notification program PM3 causes the execution device 36 of the non-friend device 52 to execute a process of transmitting the activation completion notification M141 to the device 40B0 that belongs to the owner of the vehicle 20, the notification program PM3 does not have to cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the activation completion notification M141 to the owner device 40. For example, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the activation completion notification M141 to only the device 41 among the devices 40B0 that belong to the owner of the vehicle 20 shown in FIG. 27. Furthermore, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of transmitting the activation completion notification M141 to multiple devices 40B0 that belong to the owner of the vehicle 20. For example, the notification program PM3 may cause the execution unit 36 ​​of the non-friend device 52 to execute a process of transmitting an activation completion notification M141 to the owner device 40, device 41, device 42, and device 43.

[0306] The notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending an activation completion notification M141 to the device 40BO belonging to the owner of the vehicle 20, but may not cause the execution device 36 to execute a process of sending an activation completion notification M142 to a shared device 50 other than the shared device 50 that made the registration request D31.

[0307] The notification program PM3 may cause the execution device 36 of the non-friend device 52 to execute a process of sending an activation completion notification M142 to another non-friend device 52. In other words, the notification program PM3 may cause the execution device 36 of the non-friend device 52 to send the activation completion notification M142 to a shared device 50 other than the friend device 51 that issued the registration request D31.

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

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

[0310] For example, as shown in FIG. 4 , the third device 30C, which is the 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 for the vehicle 20. As a result, a new device 30 that stores the key information DK for the new non-friend key KN of the vehicle 20 is registered as the non-friend device 52. In this case, the second device 30B that stores friend key information DKF indicating the friend key KF is the device 30 that stores key information DK indicating the first digital key. The third device 30C that stores non-friend key information DKN indicating the non-friend key KN to be registered based on the registration request D31 from the second device 30B is the device 30 that stores key information DK indicating the second digital key. The new device 30 that stores key information DK indicating the new non-friend key KN to be registered based on the request from the third device 30C is the device 30 that stores key information DK indicating the third digital key.

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

[0312] The digital key-related matters in the above embodiments do not have to comply with the CCC. 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0325] 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 . Thereafter, the management server 70 transmits a request to delete the non-friend key information DKN to the non-friend device 52. Upon receiving 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 . Thereafter, the non-friend device 52 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.

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

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

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

[0329] <Additional Notes> The technical concepts that can be understood from the above-described embodiments and modifications will be described below. [Appendix 1] A server that communicates with a vehicle and multiple devices and manages information regarding digital keys that can be registered to the vehicle, wherein the digital keys include shared keys that can be registered multiple times to the same vehicle, and the multiple devices include a shared device that stores information regarding the shared key and a device belonging to the owner of the vehicle, and the server sends a registration notification to the device belonging to the owner of the vehicle, the registration notification including information identifying the shared device that has made a registration request to store information regarding a new shared key in another device.

[0330] [Appendix 2] The server described in Appendix 1, which, when receiving a request to store information regarding the new shared key in the vehicle, sends the registration notification to a device belonging to the owner of the vehicle.

[0331] [Appendix 3] A server as described in Appendix 1 or Appendix 2, which, upon receiving an activation completion notification sent by the shared device when it is activated as the digital key, sends the registration notification to a device belonging to the owner of the vehicle.

[0332] [Appendix 4] The digital key includes an owner key, of which only one can be registered for the same vehicle, and the multiple devices include an owner device that stores information about the owner key, the owner device being a device belonging to the owner of the vehicle, and a server described in any one of Appendices 1 to 3 that transmits the registration notification to the owner device.

[0333] [Supplementary Note 5] The server according to any one of Supplementary Note 1 to Supplementary Note 4, which transmits the registration notification to the share device other than the share device that made the registration request. [Appendix 6] A server according to any one of Appendices 1 to 5, which, when receiving a deletion request to delete information relating to a share key stored in the share device, sends a deletion notification including information identifying the share device that made the deletion request to a device belonging to the owner of the vehicle.

[0334] [Appendix 7] The digital key includes an owner key, of which only one can be registered for the same vehicle, and the multiple devices include an owner device that stores information about the owner key, the owner device being a device belonging to the owner of the vehicle, and the server described in Appendix 6 that sends the deletion notification to the owner device.

[0335] [Appendix 8] The server according to appendix 6 or appendix 7, which, when receiving the deletion request, also transmits the deletion notification to the share device other than the share device that made the deletion request.

[0336] [Appendix 9] A notification program stored in a storage device of a device in a digital key system that causes multiple devices to store information about digital keys that can be registered to a vehicle and causes the devices to function as the digital keys of the vehicle, wherein the digital keys have share keys, multiple of which can be registered to the same vehicle, and the multiple devices include a share device that stores information about the share keys and a device belonging to the owner of the vehicle, and when a share device sends a registration request to store information about a new share key in another device, the notification program causes a processing circuit of the share device that sent the registration request to execute a process to send a registration notification including information that identifies the share device to the device belonging to the owner of the vehicle.

[0337] [Appendix 10] A notification program as described in Appendix 9, which causes the processing circuit of the share device to execute a process of sending the registration notification to a device belonging to the owner of the vehicle when the share device generates information regarding the new share key after sending the registration request.

[0338] [Appendix 11] A notification program as described in Appendix 9 or Appendix 10, which causes the processing circuit of the shared device to execute a process of sending the registration notification to a device belonging to the owner of the vehicle when the device stores information about the new shared key and is registered as the shared device.

[0339] [Appendix 12] The digital key includes an owner key, of which only one can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, the owner device being a device belonging to the owner of the vehicle, and a notification program described in any one of Appendices 9 to 11 that executes a process of sending the registration notification to the owner device.

[0340] [Appendix 13] A notification program described in any one of Appendices 9 to 12, which causes the processing circuit of the share device to execute a process of sending the registration notification to share devices other than the share device that made the registration request.

[0341] [Appendix 14] A notification program as described in any one of Appendices 9 to 13, which, when activated as the digital key, causes the processing circuit of the shared device to execute a process of sending an activation completion notification to a device belonging to the owner of the vehicle, the activation completion notification including information identifying another shared device that made the registration request.

[0342] [Appendix 15] The digital key includes an owner key, of which only one can be registered for the same vehicle, and the multiple devices include an owner device that stores information about the owner key, the owner device being a device belonging to the owner of the vehicle, and the notification program described in Appendix 14 that executes a process to send the activation completion notification to the owner device.

[0343] [Appendix 16] A notification program as described in Appendix 14 or Appendix 15, which causes the processing circuit of the share device to execute a process of sending the activation completion notification to share devices other than the share device that made the registration request.

[0344] [Appendix 17] A notification program as described in any one of Appendices 9 to 16, which causes the sharing device to send a deletion request to a server that manages information about the digital key, to delete information about the sharing key stored in another sharing device, and then causes the processing circuit of the sharing device to execute a process of sending a deletion notification to a device belonging to the owner of the vehicle, the deletion notification including information identifying the sharing device that sent the deletion request to the server.

[0345] [Appendix 18] A notification program according to any one of Appendices 9 to 17, wherein the deletion command for deleting information relating to the shared key stored in the shared device includes information identifying the shared device that sent the deletion request that caused the deletion command to a server that manages information relating to the digital key, and when the deletion command is received from the server, the notification program causes the processing circuit of the shared device to execute a process of sending a deletion notification to a device belonging to the owner of the vehicle, the deletion notification including information identifying the shared device that sent the deletion request to the server.

[0346] [Appendix 19] The digital key includes an owner key, of which only one can be registered for the same vehicle, and the multiple devices include an owner device that stores information about the owner key, the owner device being a device belonging to the owner of the vehicle, and a notification program as described in Appendix 17 or Appendix 18 that executes a process to send the deletion notification to the owner device.

[0347] [Appendix 20] A notification program according to any one of appendices 17 to 19, which executes a process of sending the deletion notification to share devices other than the share device that sent the deletion request. [Explanation of symbols]

[0348] AT…Authentication information D31...Registration request D42…Deletion order D71...Deletion request DK...Key information DKO…Owner key information DKS…Share Key Information KO…Owner key KS...Share Key M61, M62, M81, M82, M91, M92, M111, M112, M121, M122...Registration notification M71, M71, M101, M102, M131, M132...Deletion notice M80, M141, M142…Activation completion notification PM2, PM3…Notification program 20...Vehicle 30, 41, 42, 43…Device 36...Execution device 37…Storage device 40...Owner device 40BO...Devices belonging to the vehicle owner 50...Shared devices 70...Administration server

Claims

1. a server that communicates with a vehicle and a plurality of devices and manages information about a digital key that can be registered to the vehicle; The digital key includes a shared key, multiple of which can be registered to the same vehicle, and the multiple devices include a shared device that stores information about the shared key and a device that belongs to the owner of the vehicle, A registration notification including information identifying the shared device that has made a registration request to store information about a new shared key in another device is transmitted to a device belonging to the owner of the vehicle. server.

2. sending the registration notification to a device belonging to the owner of the vehicle when a request to store information about the new shared key in the vehicle is received; The server of claim 1 .

3. When the shared device receives an activation completion notification transmitted by the shared device upon activation as the digital key, the shared device transmits the registration notification to a device belonging to the owner of the vehicle. The server of claim 1 .

4. The digital keys include an owner key, only one of which can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, the owner device is a device belonging to an owner of the vehicle; Sending the registration notification to the owner device. The server according to any one of claims 1 to 3.

5. The registration notification is also sent to the share device other than the share device that made the registration request. The server according to any one of claims 1 to 3.

6. When a deletion request is received to delete information about a share key stored in the share device, A deletion notification including information identifying the shared device that made the deletion request is sent to a device belonging to the owner of the vehicle. The server of claim 1 .

7. The digital keys include an owner key, only one of which can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, the owner device is a device belonging to an owner of the vehicle; Sending the deletion notification to the owner device. The server of claim 6.

8. When the deletion request is received, the deletion notification is also transmitted to the share device other than the share device that made the deletion request. The server of claim 6.

9. A notification program stored in a storage device of a plurality of devices in a digital key system that stores information about a digital key that can be registered to a vehicle and causes the devices to function as the digital key for the vehicle, The digital key includes a shared key that can be registered multiple times to the same vehicle, The plurality of devices include a shared device that stores information about a shared key and a device that belongs to the owner of the vehicle, When the share device transmits a registration request to store information about a new share key in another device, the processing circuit of the share device that transmitted the registration request executes a process of transmitting a registration notification including information identifying the share device to a device belonging to the owner of the vehicle. Notification program.

10. When the share device generates information about the new share key after transmitting the registration request, the processing circuit of the share device executes a process of transmitting the registration notification to a device belonging to the owner of the vehicle. The notification program according to claim 9.

11. When the device stores information about the new share key and is registered as the share device, the processing circuit of the share device executes a process of transmitting the registration notification to a device belonging to the owner of the vehicle. The notification program according to claim 9.

12. The digital keys include an owner key, only one of which can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, The owner device is a device belonging to the owner of the vehicle, and executes a process of transmitting the registration notification to the owner device. The notification program according to any one of claims 9 to 11.

13. causing the processing circuit of the share device to execute a process of transmitting the registration notification to the share device other than the share device that made the registration request; The notification program according to any one of claims 9 to 11.

14. When the digital key is validated, the processing circuit of the shared device executes a process of transmitting an activation completion notice, including information identifying the other shared device that made the registration request, to a device belonging to the owner of the vehicle. The notification program according to claim 9.

15. The digital keys include an owner key, only one of which can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, The owner device is a device belonging to an owner of the vehicle, and executes a process of transmitting the activation completion notification to the owner device. The notification program according to claim 14.

16. causing the processing circuit of the share device to execute a process of transmitting the validation completion notification to the share device other than the share device that made the registration request; The notification program according to claim 14.

17. After the share device transmits a deletion request to a server that manages information about the digital key, requesting that information about the share key stored in another share device be deleted, the processing circuit of the share device executes a process of transmitting a deletion notice, including information identifying the share device that transmitted the deletion request to the server, to a device belonging to the owner of the vehicle. The notification program according to claim 9.

18. the deletion command for deleting information about the share key stored in the share device includes information for identifying the share device that transmitted the deletion request that caused the deletion command to a server that manages information about the digital key; When the deletion command is received from the server, the processing circuit of the shared device executes a process of transmitting a deletion notification, including information identifying the shared device that transmitted the deletion request to the server, to a device belonging to the owner of the vehicle. The notification program according to claim 9.

19. The digital keys include an owner key, only one of which can be registered to the same vehicle, and the plurality of devices include an owner device that stores information about the owner key, The owner device is a device belonging to an owner of the vehicle, and the deletion notification is transmitted to the owner device.

19. The notification program according to claim 17 or 18.

20. and executing a process of transmitting the deletion notification to the share device other than the share device that transmitted the deletion request.

19. The notification program according to claim 17 or 18.

Images