Server, setting method, program, and system

Abstract

To provide a server capable of changing, when a range of a function executable by a digital key is changed, a range of a function executable by another digital key generated on the basis of the digital key according to the changed range of the function executable by the digital key.SOLUTION: The management server 70 manages a plurality of digital keys that can be used for the vehicle 20. The plurality of digital keys include a first digital key and a second digital key generated based on the first digital key. When the range of functions that can be executed by the friend key KF, which is the first digital key, is changed, the management server 70 sets the range of functions that can be executed by the non-friend key KN, which is the second digital key, according to the changed range.SELECTED DRAWING: Figure 12

Description

[Technical Field]

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

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

[0003] The management server manages multiple digital keys, such as owner keys and multiple shared keys. When a vehicle uses a digital key, it authenticates the digital key and allows it to unlock the vehicle and perform other controls. [Prior art documents] [Patent documents]

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

[0005] In a management system such as that described in Patent Document 1, it is conceivable that a new share key may be registered by a share key making a further registration request. This new share key is referred to as a non-friend key. In such a case, there is a need to set the range of functions that the non-friend key can perform as a digital key based on the range of functions that the share key that registered the non-friend key can perform as a digital key. Specifically, for example, there is a need to set the range of functions that the non-friend key can perform as a digital key to be narrower than the range of functions that the share key that registered the non-friend key can perform as a digital key.

[0006] Here, it is possible that the range of functions that a share key can perform as a digital key may change, and even in such cases, there is a desire to change the range of functions that a non-friend key can perform as a digital key accordingly. [Means for solving the problem]

[0007] A server for solving the above problem manages multiple digital keys that can be used for a vehicle. The multiple digital keys include a first digital key and a second digital key generated based on the first digital key. When the range of functions that the first digital key can perform is changed, the server sets the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform.

[0008] A setting method for solving the above problem is executed by a server that manages multiple digital keys that can be used for a vehicle. The multiple digital keys include a first digital key and a second digital key generated based on the first digital key. The setting method includes the steps of: a communication device of the server receiving information that the range of functions that the first digital key can perform has changed; and, when the range of functions that the first digital key can perform has changed, a processing circuit of the server setting the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform.

[0009] The program for solving the above problem is stored in a storage device of a server that manages multiple digital keys that can be used for vehicles. The multiple digital keys include a first digital key and a second digital key generated based on the first digital key. When the range of functions that the first digital key can perform is changed, the program causes a processing circuit of the server to execute a process for setting the range of functions that the second digital key can perform in accordance with the changed range of functions that the first digital key can perform.

[0010] A system for solving the above problem includes a vehicle that stores information related to a digital key and a server that manages multiple digital keys that can be used for the vehicle. The multiple digital keys include a first digital key and a second digital key generated based on the first digital key. When the range of functions that the first digital key can perform is changed, the system sets the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform.

[0011] A system for solving the above problem includes a plurality of devices that store information related to digital keys and a server that manages the plurality of digital keys. The plurality of digital keys include a first digital key and a second digital key generated based on the first digital key. When the range of functions that the first digital key can perform is changed, the system sets the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform. [Effects of the Invention]

[0012] When the range of functions that a digital key can perform is changed, the above-mentioned server, setting method, program, and system can change the range of functions that another digital key generated based on the digital key can perform, depending on the changed range of functions that the digital key can perform. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a schematic diagram showing a management system. [Figure 2] FIG. 2 is a schematic diagram showing owner key information. [Figure 3] FIG. 3 is a schematic diagram showing the share key information. [Figure 4] FIG. 4 is a schematic diagram showing data in the database of the management server. [Figure 5] FIG. 5 is an explanatory diagram showing a series of processes performed by the management server when an owner key is registered. [Figure 6] FIG. 6 is an explanatory diagram showing a series of processes performed by the management server when a friend key is registered. [Figure 7] FIG. 7 is an explanatory diagram showing a series of processes performed by the management server when a non-friend key is registered. [Figure 8] FIG. 8 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is deleted in response to a request from a friend device. [Figure 9] FIG. 9 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is deleted in response to a request from a non-friend device. [Figure 10] FIG. 10 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the first embodiment. [Figure 11] FIG. 11 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 12] FIG. 12 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 13] FIG. 13 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 14] FIG. 14 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the second embodiment. [Figure 15] FIG. 15 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 16] FIG. 16 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 17] FIG. 17 is an explanatory diagram showing a series of processes performed by a management system including a management server according to a modified example of the second embodiment. [Figure 18] FIG. 18 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 19] FIG. 19 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the third embodiment. [Figure 20] FIG. 20 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 21] FIG. 21 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 22] FIG. 22 is an explanatory diagram showing a continuation of the processing of FIG. [Figure 23] FIG. 23 is a schematic diagram showing the relationship between an owner device, a friend device, and a non-friend device. [Figure 24] FIG. 24 is an explanatory diagram showing a series of processes performed by a management system including a management server according to a modified example. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0016] The communication module 21 communicates with the management server 70 via a wireless communication network. The communication module 21 is a communication device. 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, sounds, etc. The presentation device is, for example, a monitor and a speaker.

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

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

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

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

[0021] The communication module 31 communicates with the device server 60 via a wireless communication line. The communication module 31 is a communication device. 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, sounds, etc. The presentation device is, for example, a monitor and a speaker.

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

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

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

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

[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] 1, the shared device 50 stores shared key information DKS indicating a shared key KS as key information DK. A shared key KS is a digital key that can be registered in multiple numbers for one vehicle 20 when registering the digital key to enable use of the digital key. In other words, multiple shared keys KS can exist for one vehicle 20.

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

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

[0033] The non-friend key KN is a shared key KS registered based on an indirect registration request D31 from a friend device 51, as will be described later. The non-friend key information DKN is key information DK indicating the non-friend key KN. The non-friend device 52 is a device 30 that stores key information DK indicating the non-friend key KN. The non-friend key KN is a shared key KS registered based on an indirect registration request from a shared device 50, which is a device 30 different from the owner device 40. In other words, the registration request D31 is a request to have the device 30 store the non-friend key information DKN, which is key information DK.

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

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

[0039] The authority information ATP7 is information indicating the range of functions that can be performed by the device 30 that stores the authority information ATP7. The range of functions that can be performed includes, for example, the number of share keys KS that can be requested to be registered and the range of vehicle 20 functions that can be performed by authenticating the digital key. The range of vehicle 20 functions that can be performed indicates, for example, the possible controls among starting the engine of the vehicle 20, turning on the power of the vehicle 20, and unlocking and locking the doors of the vehicle 20. For example, if the range of vehicle 20 functions that can be performed includes the above-mentioned three controls, the range of vehicle 20 functions that can be performed is wider than if the range of vehicle 20 functions that can be performed is limited to unlocking and locking the doors of the vehicle 20. More specifically, the range of vehicle 20 functions that can be performed by the friend device 51 includes the above-mentioned three functions, while the range of vehicle 20 functions that can be performed by the non-friend device 52 includes turning on the power of the vehicle 20 and unlocking and locking the doors of the vehicle 20.

[0040] As shown in FIG. 1, the device server 60 relays communication between the devices 30 and the management server 70. A device server 60 is provided for each type of device 30. That is, the device server 60 with which a first type of device 30 communicates is different from the device server 60 with which a second type of device 30 communicates. For example, the type refers to the model of the device 30, and a device server 60 is provided for each model of the device 30. For example, the type refers to the communication line used by the device 30, and a device server 60 is provided for each communication line used by the device 30. Each device server 60 relays communication with the management server 70, so that devices 30 of different types can communicate with the management server 70 via the device server 60. Note that FIG. 1 illustrates only one device server 60.

[0041] <Administration Server 70> The management server 70 manages the digital key. The management server 70 is capable of communicating with the vehicle 20 and multiple devices 30. The management server 70 includes an execution device 71, a storage device 72, and a communication module 73. The communication module 73 communicates with the device server 60 via a wireless communication line. The communication module 73 is also capable of wireless communication with the communication module 21 of the vehicle 20. The communication module 73 is a communication device.

[0042] The storage device 72 stores a server program PS, a change program PM, and a database DB. The server program PS is executed by the execution device 71, causing the execution device 71 to register a digital key in the database DB and delete a digital key from the database DB. The execution device 71 is a processing circuit. Details of the change program PM will be described later.

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

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

[0045] The following describes a state in which digital keys are registered to seven devices 30 for one vehicle 20. The seven devices 30 are a first device 30A, a second device 30B, a third device 30C, a fourth device 30D, a fifth device 30E, a sixth device 30F, and a seventh device 30G.

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

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

[0048] More specifically, in the data DA, the devices 30 whose digital key type is registered as the friend key KF are the second device 30B and the fifth device 30E. That is, the second device 30B and the fifth device 30E are friend devices 51.

[0049] In the data DA, the devices 30 whose digital key type is registered as a non-friend key KN are the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G. In other words, the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G are non-friend devices 52.

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

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

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

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

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

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

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

[0057] When the management server 70 receives a registration request D11 for the owner key KO from the first device 30A or the like, the management server 70 first performs 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.

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

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

[0060] In step S13, the vehicle 20 generates a vehicle public key PKV, which is the public key of the vehicle 20, and a vehicle private key SKV, which is the private key of the vehicle 20. Then, the vehicle 20 transmits generation data DC for generating the owner key KO to the first device 30A via 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.

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

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

[0063] In step S17, 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.

[0064] Thereafter, when the first device 30A receives the completion notification M11, the first device 30A performs the process of step S18. In step S18, the first device 30A generates a key track request D12 for the owner key KO. The key track request D12 is a signal requesting the management server 70 to update the database DB. 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.

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

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

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

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

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

[0070] The share information SH1 includes, for example, share key structure information STS, password information ATP2, validity start time information ATP3, expiration date information ATP4, and name information ATP5. 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.

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

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

[0073] In step S25, the owner device 40 generates signature information ATP1. Specifically, the owner device 40 causes the HMI 32 to present the acquired 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.

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

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

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

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

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

[0079] On the other hand, if the friend key KF that received the key track request D23 is not on the rejection list, the management server 70 registers the friend key KF that received the key track request D23 in the database DB. 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.

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

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

[0082] After completing the registration management, the management server 70 transmits a key track completion notification M23 to the second device 30B. Thereafter, upon receiving the key track completion notification M23, the second device 30B performs the 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.

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

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

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

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

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

[0088] In step S44, the third device 30C uses the share information SH2 to generate unsigned non-friend key information DKNN. The unsigned non-friend key information DKNN is non-friend key information DKN that does not include signature information ATP1. Specifically, the third device 30C generates each piece of information included in the acquired share information SH2 as the unsigned non-friend key information DKNN. The third device 30C then sends 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.

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

[0090] In step S45, the friend device 51 generates signature information ATP1. Specifically, the friend device 51 causes the HMI 32 to present the acquired 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.

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

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

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

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

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

[0096] On the other hand, if the non-friend key KN is not on the rejection list, the management server 70 registers the non-friend key KN that is the 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.

[0097] Thereafter, the management server 70 transmits the authentication package ATP of the non-friend key information DKN and a storage request D34 to store 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.

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

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

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

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

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

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

[0104] 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 is pending in accordance with the deletion reservation D41. Then, the management server 70 transmits the pending notification M41 to the friend device 51.

[0105] Thereafter, when the friend device 51 receives the on-hold notification M41, the friend device 51 performs the process of step S63. In step S63, the friend device 51 presents information indicating that the non-friend key KN that is the target of the deletion reservation D41 is on hold to the HMI 32. For example, the friend device 51 displays an image on the HMI 32 indicating that the non-friend key KN that is the target of the deletion reservation D41 is on hold.

[0106] After the process of step S62, the management server 70 performs the process of step S64. In step S64, the management server 70 stores the state of the non-friend key KN that is the target of the 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.

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

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

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

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

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

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

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

[0114] In step S72, the management server 70 updates the database DB. Specifically, the management server 70 deletes the non-friend device 52 having the non-friend key KN to be deleted in this series of processes from the data DA of the vehicle 20 in the database DB. Thereafter, the management server 70 transmits 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.

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

[0116] <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 based on a deletion operation in the non-friend device 52.

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

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

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

[0120] After the process of step S82, the management server 70 performs the process of step S84. In step S84, the management server 70 generates a deletion request D51 for deleting the authentication information AT for authenticating the non-friend key information DKN that was deleted in step S81. Then, the management server 70 transmits the deletion request D51 to the vehicle 20.

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

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

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

[0124] <Change of authority information ATP7 by management server 70 in the first embodiment> Next, a series of processes that the management server 70 executes to change the authority information ATP7 of the friend key KF and the authority information ATP7 of the non-friend key KN in response to a request from the owner device 40 will be described.

[0125] The authority information ATP7 of the friend key KF is information that indicates the range of functions that the friend key KF can perform. Specifically, the authority information ATP7 of the friend key KF is information that indicates the range of functions of the vehicle 20 that the friend device 51 that stores the authority information ATP7 can perform as the friend key KF. The functions of the vehicle 20 that the friend device 51 can perform as the friend key KF include starting the engine of the vehicle 20, turning on the power of the vehicle 20, and unlocking and locking the doors of the vehicle 20. The management server 70 is configured to be able to change the range of functions that the friend key KF can perform by changing the authority information ATP7 of the friend key KF. Specifically, the management server 70 changes the range of functions of the vehicle 20 that the friend device 51 can perform as the friend key KF by changing the authority information ATP7 stored in the friend device 51 that stores key information DK that indicates the friend key KF.

[0126] The authority information ATP7 of the non-friend key KN is information that indicates the range of functions that the non-friend key KN can perform. Specifically, the authority information ATP7 of the non-friend key KF is information that indicates the range of functions of the vehicle 20 that the non-friend device 52 that stores the authority information ATP7 can perform as the non-friend key KN. The functions of the vehicle 20 that the non-friend device 52 can perform as the non-friend key KN are power-on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. The management server 70 is configured to be able to change the range of functions that the non-friend key KN can perform by changing the authority information ATP7 of the non-friend key KN. Specifically, the management server 70 changes the range of functions of the vehicle 20 that the non-friend device 52 can perform as the non-friend key KN by changing the authority information ATP7 stored in the non-friend device 52.

[0127] 1, in management server 70, storage device 72 stores change program PM. Execution device 71 executes change program PM stored in storage device 72. In this way, management server 70 executes a series of processes.

[0128] Fig. 10 shows the flow of a series of processes executed by the management server 70 to change the authority information ATP7 in the friend key KF in response to a request from the owner device 40. The owner device 40 shown in Fig. 10 is the first device 30A that stores key information DK indicating the owner key KO through the series of processes shown in Fig. 5. The owner key KO registered in the first device 30A is a third digital key.

[0129] The friend device 51 in Fig. 10 is the second device 30B that stores key information DK indicating the friend key KF through the series of processes shown in Fig. 6. The friend key KF registered in the second device 30B is a first digital key.

[0130] The non-friend device 52 shown in Fig. 10 is a third device 30C that stores key information DK indicating a non-friend key KN through the series of processes shown in Fig. 7. The non-friend key KF registered in the third device 30C is a second digital key.

[0131] The relationship between the third device 30C in which the second digital key is registered and the second device 30B in which the first digital key is registered is such that the second digital key, which is a non-friend key KN, is registered in the third device 30C based on a registration request from the second device 30B. That is, the second digital key is a digital key generated based on the first digital key. The relationship between the second device 30B in which the first digital key is registered and the first device 30A in which the third digital key is registered is such that the friend key KN, which is the first digital key, is registered in the second device 30B based on a registration request from the first device 30A. That is, the first digital key is a digital key generated based on the third digital key.

[0132] When an operation to request a change to the authority information ATP7 of the friend key KF is executed in the owner device 40, the owner device 40 first performs the processing of step S91. In step S91, the owner device 40 generates a change request D61 for the authority information ATP7 of the first digital key, which is the friend key KF. The change request D61 is a request to change the authority information ATP7 of the first digital key, which is the friend key KF.

[0133] The change request D61 includes a signal requesting deletion of the friend key KF, digital key identification information ST3 indicating the friend key KF, and a signal requesting registration of the changed friend key KF. The signal requesting registration of the changed friend key KF includes new authority information ATP7. The new authority information ATP7 indicates that the functions of the vehicle 20 that the friend device 51 can perform include power-on control for the vehicle 20 and lock and unlock control for the doors of the vehicle 20. In other words, the new authority information ATP7 indicates that the functions of the vehicle 20 that the first digital key can perform include power-on control for the vehicle 20 and lock and unlock control for the doors of the vehicle 20.

[0134] When the management server 70 receives the change request D61, it performs the process of step S92. In step S92, the management server 70 generates a pending notification M61 indicating that the change is pending in accordance with the change request D61. Then, the management server 70 transmits the pending notification M61 to the owner device 40.

[0135] Thereafter, when the owner device 40 receives the pending notification M61, the owner device 40 performs the process of step S93. In step S93, the owner device 40 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 is pending.

[0136] <Change reservation D100 and change reservation D101> After processing step S92, the management server 70 performs processing step S120. In step S120, the management server 70 generates a change reservation D100 for the friend key information DKF indicating the friend key KF that is the target of the change request D61, and a change reservation D101 for the non-friend key information DKN indicating the non-friend key KN. The change reservation D100 is a command to reserve a change of the friend key information DKF. The change reservation D101 is a command to reserve a change of the non-friend key information DKN. The management server 70 transmits the change reservation D100 to the friend device 51. The management server 70 transmits the change reservation D101 to the non-friend device 52.

[0137] When the friend device 51 receives the change reservation D100, it performs the process of step S121. In step S121, the friend device 51 presents to the HMI 32 information indicating that a change of the authority information ATP7 has been reserved.

[0138] When the non-friend device 52 receives the change reservation D101, it performs the process of step S122. In step S122, the non-friend device 52 presents to the HMI 32 information indicating that a change of the authority information ATP7 has been reserved.

[0139] After processing step S120, the management server 70 performs processing step S123. In step S120, the management server 70 stores the state of the friend key KF that is the target of the change reservation D100 as a fade-out state in the database DB. The fade-out state is a state in which the change reservation D100 has been received but the execution of the change is still pending. The management server 70 stores the state of the non-friend key KN that is the target of the change reservation D101 as a fade-out state in the database DB. The fade-out state is a state in which the change reservation D101 has been received but the execution of the change is still pending. Thereafter, the management server 70 proceeds to processing step S124.

[0140] In step S124, the management server 70 confirms that the predetermined condition RC is satisfied. The predetermined condition RC is a condition necessary to start the change after the change reservation D100 and the change reservation D101 are transmitted. 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 change reservation D100 and the change reservation D101 were generated. When the management server 70 confirms that the predetermined condition RC is satisfied, the management server 70 proceeds to step S94.

[0141] <Deletion of Friend Key Information DKF and Non-Friend Key Information DKN> After processing step S124, the management server 70 performs processing step S94. In step S94, the management server 70 generates a deletion request D62 for deleting the friend key information DKF indicating the friend key KF that is the target of the change request D61, and a deletion request D63 for deleting the non-friend key information DKN indicating the non-friend key KN. The management server 70 transmits the deletion request D62 to the friend device 51. The management server 70 transmits the deletion request D63 to the non-friend device 52. The series of processes proceeds to FIG. 11.

[0142] 11, when the friend device 51 receives the deletion request D62, it performs processing in step S95. In step S95, the friend device 51 presents to the HMI 32 information indicating that the authority information ATP7 is being changed. For example, the friend device 51 displays an image on the HMI 32 indicating that the authority information ATP7 is being changed. After processing in step S95, the friend device 51 performs processing in step S96. In step S96, the friend device 51 deletes the friend key information DKF in accordance with the deletion request D62. Then, the friend device 51 transmits to the management server 70 a completion notification M62 indicating that the deletion in accordance with the deletion request D62 has been completed.

[0143] When the non-friend device 52 receives the deletion request D63, it performs processing of step S97. In step S97, the non-friend device 52 presents information indicating that the authority information ATP7 is being changed to the HMI 32. For example, the non-friend device 52 displays an image indicating that the authority information ATP7 is being changed on the HMI 32. After processing of step S97, the non-friend device 52 performs processing of step S98. In step S98, the non-friend device 52 deletes the non-friend key information DKN in accordance with the deletion request D63. Then, the non-friend device 52 transmits a completion notification M63 to the management server 70 indicating that the deletion in accordance with the deletion request D63 has been completed.

[0144] When the management server 70 receives the completion notification M62 and the completion notification M63, the management server 70 performs the process of step S99. In step S99, the management server 70 stores a deletion history of the deletion of the friend key information DKF in the friend device 51 and the non-friend key information DKN in the non-friend device 52. The management server 70 then proceeds to the process of step S100.

[0145] <Delete the authentication information AT of the friend key KF and the authentication information AT of the non-friend key KN> In step S100, the management server 70 generates a deletion request D64 for the authentication information AT of the friend key KF and a deletion request D65 for the authentication information AT of the non-friend key KN. The management server 70 then transmits the deletion request D64 and the deletion request D65 to the vehicle 20. The series of processes continues in FIG.

[0146] 12, when the vehicle 20 receives the deletion request D64 and the deletion request D65, the vehicle 20 performs the processing of step S101. In step S101, the vehicle 20 deletes the authentication information AT of the friend key KF that is the target of the deletion request D64 and the authentication information AT of the non-friend key KN that is the target of the deletion request D65 in accordance with the deletion request D64 and the deletion request D65. The vehicle 20 then transmits a completion notification M64 to the management server 70 indicating that the deletion of the authentication information AT of the friend key KF and the authentication information AT of the non-friend key KN has been completed.

[0147] When the management server 70 receives the completion notification M64, the management server 70 performs the process of step S102. In step S102, the management server 70 stores the deletion history of the deletion of the authentication information AT of the friend key KF and the authentication information AT of the non-friend key KN in the vehicle 20. Thereafter, the management server 70 proceeds to the process of step S103.

[0148] <Generating changed friend key information DKF and changed non-friend key information DKN> In step S103, the management server 70 generates changed friend key information DKF by changing the authority information ATP7 from the friend key information DKF, and changed non-friend key information DKN by changing the authority information ATP7 from the non-friend key information DKN.

[0149] The management server 70 generates the changed friend key information DKF by combining the authority information ATP7 included in the change request D61 with information other than the authority information ATP7 included in the friend key information DKF stored in the database DB.

[0150] When the range of functions of the vehicle 20 that can be performed by the friend device 51 is changed, the management server 70 sets the range of functions of the vehicle 20 that can be performed by the non-friend device 52 according to the range of functions of the vehicle 20 that can be performed by the friend device 51 after the change.

[0151] The authority information ATP7 included in the change request D61 shown in FIG. 10 indicates that the range of vehicle 20 functions that the friend device 51 can perform includes power-on control for the vehicle 20 and lock and unlock control for the doors of the vehicle 20. Therefore, the management server 70 sets the vehicle 20 functions that the non-friend device 52 can perform to lock and unlock control for the doors of the vehicle 20. To achieve this, the management server 70 generates authority information ATP7 that indicates the vehicle 20 door unlock and lock control as the vehicle 20 door functions that the non-friend device 52 can perform. In other words, the authority information ATP7 indicates the vehicle 20 door unlock and lock control as the vehicle 20 door functions that the second digital key can perform. The management server 70 then generates the changed non-friend key information DKN by combining the authority information ATP7 with information other than the authority information ATP7 that is included in the non-friend key information DKN stored in the database DB. As a result, the management server 70 sets the authority information ATP7, which indicates the range of functions of the vehicle 20 that can be performed by the non-friend device 52, to a range narrower than the range of functions of the vehicle 20 that can be performed by the changed friend device 51. Thereafter, the management server 70 proceeds to step S104 shown in FIG.

[0152] <Database update> In step S104, the management server 70 updates the database DB. Specifically, the management server 70 deletes the authentication information AT of the friend key KF and the authentication information AT of the non-friend key KN for the vehicle 20 that is the target of deletion in this series of processes from the data DA of the vehicle 20 in the database DB. The management server 70 registers the authentication information AT of the changed friend key information DKF generated by the management server 70 in step S103 and the authentication information AT of the changed non-friend key information DKN in the data DA of the vehicle 20 in the database DB. That is, the management server 70 stores the authority information ATP7 included in the change request D61 in the database DB.

[0153] <Send the key information DK and the authentication package ATP> The management server 70 sends the changed friend key information DKF and a storage request D66 to store the changed friend key information DKF to the friend device 51. The management server 70 sends the changed non-friend key information DKN and a storage request D67 to store the changed non-friend key information DKN to the non-friend device 52. The management server 70 sends the authentication package ATP of the changed friend key information DKF and the authentication package ATP of the changed non-friend key information DKN to the vehicle 20. The management server 70 sends the storage request D68 to the vehicle 20 to store the authentication package ATP of the changed friend key information DKF and the authentication package ATP of the changed non-friend key information DKN.

[0154] <Processing after the device 30 receives the key information DK> When the friend device 51 receives the changed friend key information DKF and the storage request D66, the friend device 51 performs the process of step S105. In step S105, the friend device 51 stores the changed friend key information DKF. That is, the management server 70 stores the authority information ATP7 in the changed friend key information DKF in the friend device 51, which is a shared device. As a result, the request to change the authority information ATP7 of the friend key KF made in the owner device 40 is reflected in the friend device 51. The series of processes is continued in FIG. 13.

[0155] 13. In step S106, the friend device 51 presents, to the HMI 32, information indicating that the change to the authority information ATP7 has been completed. For example, the friend device 51 displays, on the HMI 32, an image indicating that the change to the authority information ATP7 has been completed. After the process of step S106, the friend device 51 transmits, to the management server 70, a storage completion notification M65 indicating that storage of the authority information ATP7 in accordance with the storage request D66 has been completed.

[0156] When the non-friend device 52 receives the changed non-friend key information DKN and the storage request D67, the non-friend device 52 performs the process of step S107. In step S107, the non-friend device 52 stores the changed non-friend key information DKN. That is, the management server 70 stores the authority information ATP7 in the changed non-friend key information DKN in the non-friend device 52, which is a shared device.

[0157] Thereafter, the non-friend device 52 performs processing of step S108. In step S108, the non-friend device 52 presents information indicating that the change of the authority information ATP7 has been completed to the HMI 32. For example, the non-friend device 52 displays an image indicating that the change of the authority information ATP7 has been completed on the HMI 32. After processing of step S108, the non-friend device 52 transmits a storage completion notification M66 to the management server 70 indicating that storage of the authority information ATP7 has been completed in accordance with the storage request D67.

[0158] <Processing after vehicle 20 receives authentication package ATP> When the vehicle 20 receives the authentication package ATP of the changed friend key information DKF, the authentication package ATP of the changed non-friend key information DKN, and the storage request D68, the vehicle 20 performs processing in step S109. In step S109, the vehicle 20 stores the authentication package ATP of the changed friend key information DKF and the authentication package ATP of the changed non-friend key information DKN. That is, the management server 70 stores the authority information ATP7 in the changed friend key information DKF and the authority information ATP7 in the changed non-friend key information DKN in the vehicle 20. As a result, the request to change the authority information ATP7 of the friend key KF made in the owner device 40 is reflected in the vehicle 20.

[0159] <Processing after the management server 70 receives the completion notification M65 and the completion notification M66> Upon receiving the completion notification M65 and the completion notification M66, the management server 70 performs the process of step S110. In the process of step S110, the management server 70 generates a completion notification M67 indicating that the change of the authority information ATP7 of the friend device 51, which is the target of the change request D61, and the authority information ATP7 of the non-friend device 52 has been completed. The management server 70 transmits the completion notification M67 to the owner device 40.

[0160] When the owner device 40 receives the completion notification M67, the owner device 40 performs processing in step S111. In step S111, the owner device 40 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the first digital key, which is the friend key KF that is the target of the change request D61, has been completed, and information indicating that the change of the authority information ATP7 of the second digital key, which is the non-friend key KN, has been completed. For example, the owner device 40 displays on the HMI 32 an image indicating that the change of the authority information ATP7 of the first digital key, which is the friend key KF that is the target of the change request D61, has been completed, and that the change of the authority information ATP7 of the second digital key, which is the non-friend key KN, has been completed. Thereafter, the management system 10 ends the series of processes for changing the authority information ATP7 of the first digital key, which is the friend key KF.

[0161] <Operation of the First Embodiment> The management server 70 changes the range of functions of the vehicle 20 that can be performed by the non-friend device 52 to which the second digital key is registered when the range of functions of the vehicle 20 that can be performed by the friend device 51 to which the first digital key is registered is changed.

[0162] <Effects of the first embodiment> (1-1) When the range of functions that the first digital key can perform is changed, the management server 70 can change the range of functions that the second digital key generated based on the first digital key can perform, depending on the changed range of functions that the first digital key can perform.

[0163] (1-2) When the range of functions of the vehicle 20 that can be performed by the friend device 51 to which the first digital key is registered is changed, the management server 70 sets the range of functions that can be performed by the non-friend device 52 to which the second digital key is registered based on the registration request D31 executed by the friend device 51 before the change to a range narrower than the range of functions that can be performed by the friend device 51 after the change. As a result, the range of functions of the vehicle 20 that can be performed by the second digital key for which the friend device 51 made the registration request D31 is narrower than the range of functions of the vehicle 20 that can be performed by the first digital key registered to the friend device 52. As a result, the management server 70 can narrow the range of functions that can be performed by the non-friend device 52 to which the second digital key is registered to a range narrower than the range of functions that can be performed by the friend device 51 to which the first digital key is registered.

[0164] (1-3) When a request is made to change the range of functions of the vehicle 20 that can be performed by the friend device 51 to which the first digital key is registered, if the predetermined condition RC is met, the management server 70 sets the range of functions of the vehicle 20 that can be performed by the non-friend device 52 to which the second digital key is registered, based on the changed range of functions of the vehicle 20 that can be performed by the friend device 51. If the predetermined condition RC is not met, the management server 70 does not change the range of functions of the vehicle 20 that can be performed by the non-friend device 52 to which the second digital key is registered. In other words, when the range of functions that can be performed by the first digital key is changed, if the predetermined condition RC is met, the management server 70 sets the range of functions that can be performed by the second digital key based on the changed range of functions that can be performed by the first digital key. If the predetermined condition RC is not met, the management server 70 does not change the range of functions that can be performed by the second digital key. In this way, the management server 70 can reduce the possibility that the user of the non-friend device 52 to which the second digital key is registered will experience inconvenience when operating the vehicle 20.

[0165] (1-4) The first digital key is a digital key generated based on the third digital key, which is the owner key KO. The third digital key is registered in the owner device 40. When the range of functions that the first digital key can perform is changed, the management server 70 sets the range of functions that the second digital key can perform to a narrower range than the range of functions of the vehicle 20 that the first digital key can perform after the change. In other words, when the range of functions that the first digital key can perform is changed, the management server 70 sets the range of functions that the second digital key can perform to a range that does not exceed the range of functions that the first digital key can perform. As a result, the range of functions of the vehicle 20 that can be performed by the second digital key for which the owner device 40 has not made the registration request D21 is narrower than the range of functions of the vehicle 20 that can be performed by the first digital key for which the owner device 40 has made the registration request D21. This allows the owner of the vehicle 20 to feel secure even when the user of the non-friend device 52 to which the second digital key is registered operates the vehicle 20.

[0166] (1-5) The management server 70 includes a communication module 73, which is a communication device. The management server 70 includes an execution device 71, which is a processing circuit. The setting method executed by the management server 70 includes the steps of: the communication module 73 receiving a request to change the range of functions that can be performed by the friend key KF, which is the first digital key (step S92); and the execution device 71, when the range of functions that can be performed by the first digital key has been changed, setting the range of functions that can be performed by the non-friend key KF, which is the second digital key, in accordance with the changed range of functions that can be performed by the first digital key (steps S94, S100, and S103). By executing this setting method, when the range of functions that can be performed by the first digital key has been changed, the management server 70 can change the range of functions that can be performed by the second digital key generated based on the first digital key in accordance with the changed range of functions that can be performed by the first digital key.

[0167] (1-6) The storage device 72 of the management server 70 stores a change program PM that causes the execution device 71 of the management server 70 to execute processing. When the range of functions that the first digital key can perform is changed, the change program PM causes the execution device 71 to execute processing that sets the range of functions that the second digital key can perform, in accordance with the changed range of functions that the first digital key can perform. In this way, when the range of functions that the first digital key can perform is changed, the management server 70 can change the range of functions that the second digital key generated based on the first digital key can perform, in accordance with the changed range of functions that the first digital key can perform.

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

[0169] The range of vehicle 20 functions that can be performed by the non-friend device 52 that stores the key information DK indicating the second digital key may be configured to be changeable by the friend device 51 that made the registration request D31 for the second digital key. In this case, the friend device 51 may be configured to be able to change the range of vehicle 20 functions that can be performed by the non-friend device 52 only within the range of vehicle 20 functions that can be performed by the friend device 51.

[0170] The management server 70 may set the range of functions of the vehicle 20 that can be performed by the friend device 51 after the change to a range that is wider than the range of functions of the vehicle 20 that can be performed by the friend device 51 before the change.

[0171] The management server 70 may change the range of functions of the vehicle 20 that can be performed by the non-friend device 52 after the change to a wider range than the range of functions of the vehicle 20 that can be performed by the non-friend device 52 before the change.

[0172] The management server 70 may set the range of functions of the vehicle 20 that can be performed by the non-friend device 52 after the change to the same range as the range of functions of the vehicle 20 that can be performed by the friend device 51 after the change.

[0173] (Second embodiment) The management server 70 according to the second embodiment will be described below with reference to Figures 14 to 16. The second embodiment will be described mainly focusing on the differences from the first embodiment. The management server 70 in the second embodiment changes the range of functions of the vehicle 20 that can be performed by the digital key by changing the authority information ATP7 that indicates the range of functions of the vehicle 20 that can be performed by the digital key.

[0174] 14 shows the flow of a series of processes that the management server 70 executes to change the authority information ATP7 in the friend key KF in response to a request from the owner device 40. Before executing this series of processes, the range of functions of the vehicle 20 that the friend device 51 can perform is control of starting the engine of the vehicle 20, control of turning on the power to the vehicle 20, and control of unlocking and locking the doors of the vehicle 20. Before executing this series of processes, the range of functions of the vehicle 20 that the non-friend device 52 can perform is control of turning on the power to the vehicle 20, and control of unlocking and locking the doors of the vehicle 20. The owner device 40, friend device 51, non-friend device 52, and vehicle 20 are the same as in the first embodiment.

[0175] When an operation to request a change to the authority information ATP7 of the friend key KF is executed in the owner device 40, the owner device 40 first performs the processing of step S91. In step S91, the owner device 40 generates a change request D61 for the authority information ATP7 of the friend key KF. The change request D61 is a request to change the authority information ATP7 of the friend key KF.

[0176] The change request D61 includes digital key identification information ST3 indicating the friend key KF and a signal requesting a change to the authority information ATP7 of the friend key KF. The signal requesting a change to the authority information ATP7 of the friend key KF indicates functions of the vehicle 20 that the friend device 51 can perform, such as power-on control of the vehicle 20 and locking and unlocking control of the doors of the vehicle 20.

[0177] When the management server 70 receives the change request D61, it performs the process of step S300. In step S300, the management server 70 generates a change-in-progress notification M300 indicating that a change will be made in accordance with the change request D61. Then, the management server 70 transmits the change-in-progress notification M300 to the owner device 40.

[0178] Thereafter, when the owner device 40 receives the change-in-progress notification M300, the owner device 40 performs the process of step S301. In step S300, the owner device 40 performs the process of step S301. In step S301, the owner device 40 presents to the HMI 32 information indicating that the authority information ATP7 of the friend key KF that is the target of the change request D61 is being changed.

[0179] After processing step S300, the management server 70 performs processing step S201. In step S201, the management server 70 generates a change request D71 requesting a change to the authority information ATP7 in the friend key information DKF, and a change request D72 requesting a change to the authority information ATP7 in the non-friend key information DKN.

[0180] The change request D71 includes a signal requesting a change to the authority information ATP7 of the friend key KF. Similar to the change request D61, the signal requesting the authority information ATP7 of the friend key KF indicates the vehicle 20 functions that the friend device 51 can perform, such as power-on control of the vehicle 20 and locking and unlocking control of the doors of the vehicle 20.

[0181] When receiving a request to change the range of functions that the friend device 51 can perform, the management server 70 sets the range of functions that the non-friend device 52 can perform to a range narrower than the range of functions that the friend device 51 can perform after the change.

[0182] The signal requesting the authority information ATP7 of the friend key KF included in the change request D61 indicates that the functions of the vehicle 20 that the friend device 51 can perform are to control the power supply to the vehicle 20 on and to control the unlocking and locking of the doors of the vehicle 20. Therefore, the management server 70 generates a change request D72. The change request D72 includes a signal requesting a change to the authority information ATP7 in the non-friend key KN. The signal requesting a change to the authority information ATP7 in the non-friend key KN indicates that the functions of the vehicle 20 that the non-friend device 52 can perform are to control the unlocking and locking of the doors of the vehicle 20.

[0183] The management server 70 transmits a change request D71 to the friend device 51. The management server 70 transmits a change request D72 to the non-friend device 52. <Change of authority information ATP7 on device 30> When the friend device 51 receives the change request D71, it performs the processing of step S202. In step S202, the friend device 51 presents information indicating that the authority information ATP7 is being changed to the HMI 32. After the processing of step S202, the friend device 51 performs the processing of step S203. In step S203, the friend device 51 changes the authority information ATP7 in the friend key information DKF in accordance with the change request D71. Then, the friend device 51 transmits a change completion notification M71 to the management server 70 indicating that the change in accordance with the change request D71 has been completed.

[0184] When the non-friend device 52 receives the change request D72, it performs processing in step S204. In step S204, the non-friend device 52 presents information indicating that the authority information ATP7 is being changed to the HMI 32. After processing in step S204, the non-friend device 52 performs processing in step S205. In step S205, the non-friend device 52 changes the authority information ATP7 in the non-friend key information DKN in accordance with the change request D72. The non-friend device 52 then transmits a change completion notification M72 to the management server 70 indicating that the change in accordance with the change request D72 has been completed. Processing then proceeds to FIG. 15.

[0185] When the management server 70 receives the completion notification M71 and the completion notification M72, the management server 70 performs the process of step S206 shown in Fig. 15. In step S206, the management server 70 stores the change history of the friend key information DKF in the friend device 51 and the non-friend key information DKN in the non-friend device 52. The management server 70 then proceeds to step S207.

[0186] In step S207, the management server 70 generates a change request D73 for the authority information ATP7 in the authentication information AT of the friend key KF and a change request D74 for the authority information ATP7 in the authentication information AT of the non-friend key KN. Then, the management server 70 transmits the change request D73 and the change request D74 to the vehicle 20.

[0187] <Change of authority information ATP7 in vehicle 20> When vehicle 20 receives change request D73 and change request D74, vehicle 20 performs processing of step S208. In step S208, vehicle 20 changes the authority information ATP7 in the authentication information AT of the friend key KF that is the target of change request D73 in accordance with change request D73. Vehicle 20 changes the authority information ATP7 in the authentication information AT of the non-friend key KN that is the target of change request D74 in accordance with change request D74. Thereafter, vehicle 20 transmits a change completion notification M73 to management server 70 indicating that the change of the authority information ATP7 in the authentication information AT of the friend key KF and the authority information ATP7 in the authentication information AT of the non-friend key KN has been completed.

[0188] When the management server 70 receives the completion notification M73, the management server 70 performs the process of step S209. In step S209, the management server 70 stores the change history of the changes made to the authority information ATP7 in the authentication information AT of the friend key KF in the vehicle 20 and the authority information ATP7 in the authentication information AT of the non-friend key KN. After the process of step S209, the management server 70 proceeds to step S210 shown in FIG.

[0189] In step S210, the management server 70 updates the database DB. Specifically, the management server 70 changes the authority information ATP7 of the friend key KF and the authority information ATP7 of the non-friend key KN that are the targets of change in this series of processes in the database DB for the vehicle 20. Thereafter, the management server 70 proceeds to step S211.

[0190] In step S211, the management server 70 generates a completion notification M74 of change completion, indicating that the change of the authority information ATP7 in the friend device 51, which is the target of the change request D61, and the authority information ATP7 in the non-friend device 52 has been completed. The management server 70 generates a completion notification M75, indicating that the change of the authority information ATP7 in the friend device 51 has been completed. The management server 70 generates a completion notification M76, indicating that the change of the authority information ATP7 in the non-friend device 52 has been completed. The management server 70 transmits the completion notification M74 to the owner device 40. The management server 70 transmits the completion notification M75 to the friend device 51. The management server 70 transmits the completion notification M76 to the non-friend device 52.

[0191] When the owner device 40 receives the completion notification M74, the owner device 40 performs the process of step S212. In step S212, the owner device 40 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed, and information indicating that the change of the authority information ATP7 of the non-friend key KN has been completed.

[0192] When the friend device 51 receives the completion notification M75, the friend device 51 performs the process of step S213. In step S213, the friend device 51 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed.

[0193] When the non-friend device 52 receives the completion notification M76, the non-friend device 52 performs the process of step S214. In step S214, the non-friend device 52 presents information indicating that the change of the authority information ATP7 of the non-friend key KN has been completed to the HMI 32. Thereafter, the management system 10 ends the series of processes for the change of the authority information ATP7 of this friend key KF.

[0194] <Operation of the Second Embodiment> When the authority information ATP7 of the first digital key registered in the friend device 51 is changed, the management server 70 changes the authority information ATP7 of the second digital key registered in the non-friend device 52.

[0195] <Effects of the second embodiment> (2-1) When the range of functions that the first digital key can perform is changed by changing the authority information ATP7 of the first digital key, the management server 70 can change the range of functions that the second digital key generated based on the first digital key can perform in accordance with the range of functions that the changed first digital key can perform.

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

[0197] <Processing in the Case Where Only the Vehicle 20 Stores the Authorization Information ATP7> The authority information ATP7 may be stored only in the vehicle 20. Figure 17 shows the flow of a series of processes that the management server 70 executes to change the authority information ATP7 in the friend key KF in response to a request from the owner device 40 in the case where only the vehicle 20 stores the authority information ATP7. Before executing this series of processes, the range of functions of the vehicle 20 that the friend device 51 can perform is control of starting the engine of the vehicle 20, control of turning on the power to the vehicle 20, and control of unlocking and locking the doors of the vehicle 20. Before executing this series of processes, the range of functions of the vehicle 20 that the non-friend device 52 can perform is control of turning on the power to the vehicle 20, and control of unlocking and locking the doors of the vehicle 20.

[0198] When an operation to request a change to the authority information ATP7 of the friend key KF is executed in the owner device 40, the owner device 40 first performs the processing of step S91. In step S91, the owner device 40 generates a change request D61 for the authority information ATP7 of the friend key KF. The change request D61 is a request to change the authority information ATP7 in the authentication information AT of the friend key KF.

[0199] The change request D61 includes a signal requesting a change to the authority information ATP7 of the friend key KF. The signal requesting the authority information ATP7 of the friend key KF indicates the functions of the vehicle 20 that the friend device 51 can perform, such as power-on control of the vehicle 20 and locking and unlocking control of the doors of the vehicle 20.

[0200] When the management server 70 receives the change request D61, it performs the process of step S300. The process of step S300 is the same as that of the second embodiment. After the process of step S300, when the owner device 40 receives the change notification M300, the owner device 40 performs the process of step S301. The process of step S93 is the same as that of the second embodiment.

[0201] After processing step S300, the management server 70 performs processing step S207. In step S207, the management server 70 generates a change request D73 requesting a change to the authority information ATP7 of the friend key KF in the vehicle 20, and a change request D74 requesting a change to the authority information ATP7 of the non-friend key KN in the vehicle 20.

[0202] The change request D73 includes digital key identification information ST3 indicating the friend key KF and a signal requesting a change to the authority information ATP7 in the authentication information AT of the friend key KF. Similar to the change request D61, the signal requesting a change to the authority information ATP7 of the friend key KF indicates that the functions of the vehicle 20 that the friend device 51 can perform include power-on control for the vehicle 20 and unlocking and locking control for the doors of the vehicle 20. The change request D74 includes a signal requesting a change to the authority information ATP7 in the authentication information AT of the non-friend key KN. The signal requesting a change to the authority information ATP7 of the non-friend key KN indicates that the functions of the vehicle 20 that the non-friend device 52 can perform include unlocking and locking control for the doors of the vehicle 20. The management server 70 transmits the change request D73 and the change request D74 to the vehicle 20.

[0203] <Change of authority information ATP7 in vehicle 20> When vehicle 20 receives change request D73 and change request D74, vehicle 20 performs processing of step S208. In step S208, vehicle 20 changes the authority information ATP7 of the friend key KF that is the target of change request D73 in accordance with change request D73. Vehicle 20 changes the authority information ATP7 in the authentication information AT of the non-friend key KN that is the target of change request D74 in accordance with change request D74. Thereafter, vehicle 20 transmits a change completion notification M73 to management server 70 indicating that the change of the authority information ATP7 of the friend key KF and the authority information ATP7 of the non-friend key KN has been completed.

[0204] <Processing after the management server 70 receives the completion notification M73> When the management server 70 receives the completion notification M73, the management server 70 performs the process of step S209. In step S209, the management server 70 stores the change history of the changes made to the authority information ATP7 in the authentication information AT of the friend key KF in the vehicle 20 and the authority information ATP7 in the authentication information AT of the non-friend key KN. Thereafter, the management server 70 proceeds to step S210 shown in FIG. 18.

[0205] In step S210, the management server 70 updates the database DB. Specifically, the management server 70 changes the authority information ATP7 of the friend key KF and the authority information ATP7 of the non-friend key KN that are the targets of change in this series of processes in the database DB for the vehicle 20. Thereafter, the management server 70 proceeds to step S211.

[0206] In step S211, the management server 70 generates a completion notification M74 of change completion, indicating that the change of the authority information ATP7 in the friend device 51, which is the target of the change request D61, and the authority information ATP7 in the non-friend device 52 has been completed. The management server 70 generates a completion notification M75, indicating that the change of the authority information ATP7 in the friend device 51 has been completed. The management server 70 generates a completion notification M76, indicating that the change of the authority information ATP7 in the non-friend device 52 has been completed. The management server 70 transmits the completion notification M74 to the owner device 40. The management server 70 transmits the completion notification M75 to the friend device 51. The management server 70 transmits the completion notification M76 to the non-friend device 52.

[0207] When the owner device 40 receives the completion notification M74, the owner device 40 performs the process of step S212. In step S212, the owner device 40 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed, and information indicating that the change of the authority information ATP7 of the non-friend key KN has been completed.

[0208] When the friend device 51 receives the completion notification M75, the friend device 51 performs the process of step S213. In step S213, the friend device 51 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed.

[0209] When the non-friend device 52 receives the completion notification M76, the non-friend device 52 performs the process of step S214. In step S214, the non-friend device 52 presents information indicating that the change of the authority information ATP7 of the non-friend key KN has been completed to the HMI 32. Thereafter, the management system 10 ends the series of processes for the change of the authority information ATP7 of this friend key KF.

[0210] The management system 10 described above is a system including a vehicle 20 that stores information about digital keys, and a management server 70 that manages a plurality of digital keys that can be used for the vehicle 20. When the range of functions that can be performed by the first digital key stored in the vehicle 20 is changed, the management system 10 sets the range of functions that can be performed by the second digital key in accordance with the range of functions that can be performed by the changed first digital key. When the range of functions that can be performed by the first digital key is changed by changing the authority information ATP7 of the first digital key stored in the vehicle 20, the management system 10 can change the range of functions that can be performed by the second digital key generated based on the first digital key in accordance with the range of functions that can be performed by the changed first digital key.

[0211] (Third embodiment) The management server 70 according to the third embodiment will be described below with reference to Figures 19 to 22. The third embodiment will be described mainly focusing on the differences from the second embodiment. When the management server 70 in the third embodiment receives a request to change the range of functions that can be performed by a first digital key, it sets the range of functions that can be performed by a second digital key generated based on the changed first digital key to a range narrower than the range of functions that can be performed by the changed first digital key.

[0212] FIG. 19 shows the flow of a series of processes executed by the management server 70 to change the authority information ATP7 in the friend key KF in response to a request from the owner device 40. Before executing this series of processes, the range of vehicle 20 functions that the friend key KF can perform is engine start control for the vehicle 20, power-on control for the vehicle 20, and door unlocking and locking control for the vehicle 20. Before executing this series of processes, the range of vehicle 20 functions that the non-friend device 52 can perform is power-on control for the vehicle 20 and door unlocking and locking control for the vehicle 20. The owner device 40 and the vehicle 20 are the same as those in the second embodiment. The friend device 51 is the second device 30B that stores the friend key information DKF. The third device 30C and the fourth device 30D are devices 30 that do not store the non-friend key information DKN and are designated as non-friend devices 52 through this series of processes.

[0213] <Registration of non-friend key KN to third device 30C> When an operation is executed in the friend device 51 to request the third device 30C to register the non-friend key KN, the friend device 51 first performs the process of step S41. Step S41 is the same as step S41 shown in FIG. 7. In this series of processes, the friend device 51 performs the processes of steps S41, S42, S45, and S46 shown in FIG. 7. In this series of processes, the third device 30C performs the processes of steps S43, S44, S47, S48, and S51. In this series of processes, the management server 70 performs the process of step S49. In this series of processes, the vehicle 20 performs the process of step S50. In FIG. 19, steps S42 to S46 shown in FIG. 7 are not illustrated. As a result, the third device 30C becomes a non-friend device 52.

[0214] 19 is completed, the range of functions of the vehicle 20 that the second device 30B, which is the friend device 51, can perform is control to start the engine of the vehicle 20, control to turn on the power of the vehicle 20, and control to unlock and lock the doors of the vehicle 20. When the process of step S51 shown in FIG. 19 is completed, the range of functions of the vehicle 20 that the third device 30C, which is the non-friend device 52, can perform is control to turn on the power of the vehicle 20, and control to unlock and lock the doors of the vehicle 20.

[0215] <Execute an operation to request a change to the friend key KF authority information ATP7> In the third embodiment, as in the second embodiment, when an operation requesting a change to the authority information ATP7 of the friend key KF is executed in the owner device 40, the owner device 40 performs the process of step S91. In step S91, the owner device 40 generates a change request D61 for the authority information ATP7 of the friend key KF. The change request D61 is a request to change the authority information ATP7 of the friend key KF.

[0216] The change request D61 includes digital key identification information ST3 indicating the friend key KF and a signal requesting a change to the authority information ATP7 of the friend key KF. The signal requesting the authority information ATP7 of the friend key KF indicates the vehicle 20 functions that the friend device 51 can perform, namely, power-on control of the vehicle 20 and locking and unlocking control of the doors of the vehicle 20. The series of processes continues in FIG. 20.

[0217] <Processing Performed by the Management Server 70 After Receiving the Change Request D61> When the management server 70 receives the change request D61, it performs the process of step S300 shown in Fig. 20. The process of step S300 is the same as that in the second embodiment. After the process of step S300, when the owner device 40 receives the change-in-progress notification M300, the owner device 40 performs the process of step S301. The process of step S301 is the same as that in the second embodiment.

[0218] After the process of step S300, the management server 70 performs the process of step S401. In step S401, the management server 70 generates a change request D81. The change request D81 includes a signal requesting a change to the authority information ATP7 of the friend key KF. The signal requesting a change to the authority information ATP7 of the friend key KF indicates the functions of the vehicle 20 that the friend device 51 can perform, such as power-on control of the vehicle 20 and locking and unlocking control of the doors of the vehicle 20.

[0219] The change request D81 includes a signal that sets the range of functions that can be performed by the device 30 to which the non-friend key KN is registered based on the registration request D31 executed by the friend device 51 that received the change request D81 to a range narrower than the range of functions that can be performed by the friend device 51.

[0220] The signal requesting a change to the authority information ATP7 of the friend key KF included in the change request D61 indicates that the range of functions that the friend device 51 can perform after the change includes power-on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. Based on the request to register the friend device 51 that received the change request D81, the management server 70 generates a signal that sets the range of functions that the device 30 to which the non-friend key KN is registered can perform to a range narrower than the range of functions that the friend device 51 can perform.

[0221] The signal indicates the range of vehicle 20 functions that can be performed by the device 30 to which the non-friend key KN is registered based on the registration request from the friend device 51, including unlocking and locking the doors of the vehicle 20. The management server 70 transmits a change request D81 to the friend device 51.

[0222] <Processing Performed by the Friend Device 51 After Receiving the Change Request D81> When the friend device 51 receives the change request D81, it performs the processing of step S202. The processing of step S202 is the same as that of the second embodiment. After the processing of step S202, the friend device 51 performs the processing of step S500. In step S500, the friend device 51 changes the authority information ATP7 in the friend key information DKF in accordance with the change request D81. As a result, the functions of the vehicle 20 that the friend device 51 can perform become the power-on control of the vehicle 20 and the unlocking and locking control of the doors of the vehicle 20. In accordance with the change request D81, the friend device 51 changes the range of functions of the vehicle 20 that the device 30 to which the non-friend key KN is registered based on the registration request D31 executed by the friend device 51 can perform to the unlocking and locking control of the doors of the vehicle 20.

[0223] When the process of step S500 ends, the friend device 51 transmits a completion notification M81 to the management server 70. <Processing performed by the management server 70 after receiving the completion notification M81> When the management server 70 receives the completion notification M81, the management server 70 performs the process of step S402. In step S402, the management server 70 stores the change history of the friend key information DKF in the friend device 51. After that, the management server 70 proceeds to the process of step S403.

[0224] In step S403, the management server 70 generates a change request D82 for the authority information ATP7 in the authentication information AT of the friend key KF. Then, the management server 70 transmits the change request D82 to the vehicle 20. The series of processes continues in FIG. 21.

[0225] <Processing to be performed after the vehicle 20 receives the change request D82> When the vehicle 20 receives the change request D82, the vehicle 20 performs the processing of step S404 shown in Fig. 21. In step S404, the vehicle 20 changes the authority information ATP7 in the authentication information AT of the friend key KF that is the target of the change request D82 in accordance with the change request D82. The vehicle 20 then transmits a change completion notification M82 to the management server 70 indicating that the change of the authority information ATP7 in the authentication information AT of the friend key KF has been completed.

[0226] <Processing performed by the management server 70 after receiving the completion notification M82> When the management server 70 receives the completion notification M82, the management server 70 performs the process of step S405. In step S405, the management server 70 stores the change history of the change to the authority information ATP7 in the authentication information AT of the friend key KF in the vehicle 20. Thereafter, the management server 70 proceeds to the process of step S406.

[0227] In step S406, the management server 70 updates the database DB. Specifically, the management server 70 changes the authority information ATP7 in the authentication information AT of the friend key KF for the vehicle 20 that is the target of change in this series of processes, in the data DA of the vehicle 20 in the database DB. Thereafter, the management server 70 proceeds to step S407.

[0228] In step S407, the management server 70 generates a change completion notification M83 indicating that the change of the authority information ATP7 in the friend device 51 that is the target of the change request D61 has been completed. The management server 70 generates a completion notification M84 indicating that the change of the authority information ATP7 in the friend device 51 has been completed. The management server 70 transmits the completion notification M83 to the owner device 40. The management server 70 transmits the completion notification M84 to the friend device 51.

[0229] <Processing after the management server 70 transmits the completion notification M83 and the completion notification M84> When the owner device 40 receives the completion notification M83, the owner device 40 performs the process of step S408. In step S408, the owner device 40 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed.

[0230] When the friend device 51 receives the completion notification M84, the friend device 51 performs the process of step S409. In step S409, the friend device 51 presents to the HMI 32 information indicating that the change of the authority information ATP7 of the friend key KF that is the target of the change request D61 has been completed. The series of processes continues in FIG. 22.

[0231] <Registration of non-friend key KN for fourth device 30D> After the friend device 51 has completed the change of the authority information ATP7 of the friend key KF, the friend device 51 executes an operation to request the fourth device 30D to register a non-friend key KN, whereby the friend device 51 performs the process of step S41 shown in FIG. 22 with respect to the fourth device 30D. Step S41 is the same as step S41 shown in FIG. 7. In this series of processes, the friend device 51 performs the processes of steps S41, S42, S45, and S46 shown in FIG. 7. In this series of processes, the fourth device 30D performs the processes of steps S43, S44, S47, S48, and S51, similar to the third device 30C shown in FIG. 7. Step S47 shown in FIG. 22 is the same as step S47 shown in FIG. 7. Step S48 shown in FIG. 22 is the same as step S48 shown in FIG. 7. Step S51 shown in FIG. 22 is the same as step S51 shown in FIG. 7. In this series of processes, the management server 70 performs the process of step S49. Step S49 shown in FIG. 22 is the same as step S49 shown in FIG. 7. In this series of processes, the vehicle 20 performs the process of step S50. Step S50 shown in FIG. 22 is the same as step S50 shown in FIG. 7. Steps S42 to S46 shown in FIG. 7 are not shown in FIG. 22. As a result, the fourth device 30D becomes a non-friend device 52.

[0232] <Range of Functions of the Vehicle 20 That the Fourth Device 30D Can Perform> The authority information ATP7 in the non-friend key information DKN stored in the fourth device 30D indicates that the range of functions of the vehicle 20 that the fourth device 30D can perform includes unlocking and locking control of the doors of the vehicle 20.

[0233] 22 is completed, the range of functions of the vehicle 20 that the friend device 51 can perform is power-on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. When the process of step S51 shown in FIG. 22 is completed, the range of functions of the vehicle 20 that the third device 30C, which is a non-friend device 52, can perform is power-on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. When the process of step S51 shown in FIG. 22 is completed, the range of functions of the vehicle 20 that the fourth device 30D, which is a non-friend device 52, can perform is only unlocking and locking control of the doors of the vehicle 20.

[0234] <Operation of the Third Embodiment> The management server 70 sets the range of functions that can be performed by the second digital key generated based on the first digital key to a range narrower than the range of functions that can be performed by the first digital key.

[0235] <Effects of the third embodiment> (3-1) The management server 70 can set the range of functions of the vehicle 20 that can be performed by the second digital key to a narrower range than the range of functions that can be performed by the first digital key before the second digital key is registered in the device 30.

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

[0237] The series of processes for changing the range of vehicle 20 functions that can be performed by the non-friend device 52 when the range of vehicle 20 functions that can be performed by the friend device 51 is changed is not limited to the examples in the above embodiments. For example, the management server 70 may update the database DB after step S110, which is the process of generating the completion notification M67 in FIG. 13. The series of processes for changing the range of vehicle 20 functions that can be performed by the device 30 may be changed as appropriate to suit the structure of the information included in the authority information ATP7.

[0238] The range of vehicle 20 functions that the device 30 can perform, as indicated in the authority information ATP7, is not limited to the functions described in the embodiment. For example, the authority information ATP7 may include functions that only permit unlocking and locking of the trunk box in the vehicle 20.

[0239] The management server 70 may set the range of functions of the vehicle 20 that the friend device 51 can implement using the friend key KF for each device 30. The second device 30B and the third device 30C shown in FIG. 4 are friend devices 51. The management server 70 may set different ranges for the range of functions of the vehicle 20 that the second device 30B can implement using the friend key KF and the range of functions of the vehicle 20 that the third device 30C can implement using the friend key KF.

[0240] 23 is a schematic diagram showing the device 30 that made the request that caused the registration of a digital key when the digital key was registered in the device 30. The relationship between the second device 30B and the first device 30A is such that the friend key KF was registered in the second device 30B based on the registration request from the first device 30A. The relationship between the fifth device 30E and the first device 30A is such that the friend key KF was registered in the fifth device 30E based on the registration request from the first device 30A.

[0241] 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. 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. 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. 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. The relationship between the eighth device 30H and the third device 30C is such that the non-friend key KN is registered in the eighth device 30H based on a registration request from the third device 30C.

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

[0243] When the range of functions of the vehicle 20 that can be implemented by one of the friend devices 51 is changed, the management server 70 may change the range of functions of the vehicle 20 that can be implemented by all of the non-friend devices 52. For example, when the range of functions that can be implemented by the second device 30B is changed, the management server 70 changes the range of functions that can be implemented by the third device 30C, the fourth device 30D, the sixth device 30F, the seventh device 30G, and the eighth device 30H.

[0244] When the range of functions that a friend device 51 can perform is changed, the management server 70 may change the range of functions that a non-friend device 52 to which the non-friend key KN is registered, based on a registration request from the friend device 51. For example, when the management server 70 changes the range of functions of the vehicle 20 that the second device 30B, which is a friend device 51, can perform, the management server 70 changes the range of functions of the vehicle 20 that the third device 30C and the fourth device 30D can perform.

[0245] When the range of functions that a non-friend device 52 can perform is changed, the management server 70 may change the range of functions that the non-friend device 52 in which the non-friend key KN is registered can perform based on a registration request from the non-friend device 52. For example, if the management server 70 changes the range of functions of the vehicle 20 that the third device 30C, which is a non-friend device 52, can perform, the management server 70 changes the range of functions of the vehicle 20 that the eighth device 30H can perform. In this case, the second device 30B that stores friend key information DKF indicating the friend key KF is the device 30 in which the third digital key is registered. 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 in which the first digital key is registered. The eighth device 30H that stores non-friend key information DKN indicating the non-friend key KN to be registered based on the registration request from the third device 30C is the device 30 in which the second digital key is registered. When the range of functions that the first digital key can perform is changed, the management server 70 can change the range of functions that the second digital key generated based on the first digital key can perform in accordance with the changed range of functions that the first digital key can perform.

[0246] When the range of vehicle 20 functions that can be implemented by a friend device 51 is changed, the management server 70 may change the range of vehicle 20 functions that can be implemented by a non-friend device 52 in which the non-friend key KN is registered based on a registration request from the friend device 51, and the range of vehicle 20 functions that can be implemented by a non-friend device 52 in which the non-friend key KN is registered based on a registration request from the non-friend device 52. For example, when the management server 70 changes the range of vehicle 20 functions that can be implemented by the second device 30B, which is the friend device 51, the management server 70 changes the range of vehicle 20 functions that can be implemented by the third device 30C, the fourth device 30D, and the eighth device 30H. In other words, when the range of functions that can be implemented by a share key KS is changed, the management server 70 may set the range of functions that can be implemented by the share key KS registered in response to a request made by the share key KS in accordance with the changed range.

[0247] <Example of changes to management system 10> The authority information ATP7 may be stored only in the device 30. Fig. 24 shows the flow of a series of processes executed by the management server 70 to change the authority information ATP7 in the friend key KF in response to a request from the owner device 40 when the authority information ATP7 is stored only in the device 30. The management server 70 changes the range of functions of the device 30 that can be implemented by the digital key by changing the authority information ATP7 that indicates the range of functions of the device 30 that can be implemented by the digital key.

[0248] When an operation to request a change to the authority information ST9 in the owner key information DKF stored in the owner device 40 is executed in the owner device 40, the owner device 40 first performs the process of step S500. In step S500, the owner device 40 changes the authority information ST9 in the owner key information DKF. For example, by changing the authority information ST9, the owner device 40 reduces the number of share keys KS that the owner device 40 can request to register. Then, the owner device 40 performs the process of step S501. In step S501, the owner device 40 generates a change notification M400. The change notification M400 is a notification to the management server 70 requesting a change to the authority information ATP7 in the friend key information DKF stored in the friend device 51. The notification requesting a change to the authority information ATP7 in the friend key information DKF includes information to increase the number of share keys KS that the friend device 51 can request to register. Then, the owner device 40 transmits the change notification M400 to the management server 70.

[0249] When the management server 70 receives the change notification M400, it performs the process of step S502. In step S502, the management server 70 generates a change request D400. The change request D400 includes a signal for increasing the number of share key KS registrations that the friend device 51 can request. The management server 70 transmits the change request D400 to the friend device 51.

[0250] When the friend device 51 receives the change request D400, it performs the process of step S503. In step S503, the friend device 51 presents information indicating that the authority information ATP7 is being changed to the HMI 32. For example, the friend device 51 displays an image indicating that the authority information ATP7 is being changed on the HMI 32. After the process of step S503, the friend device 51 performs the process of step S504.

[0251] In step S504, the friend device 51 changes the authority information ATP7 in the friend key KF that is the target of the change request D400 in accordance with the change request D400. That is, the friend device 51 increases the number of shared keys KS that the friend device 51 can request to register. Thereafter, the friend device 51 transmits a change completion notification M401 indicating that the change of the authority information ATP7 of the friend key KF has been completed to the management server 70. Thereafter, the management system 10 ends this series of processes.

[0252] The management system 10 is a system including a plurality of devices 30 that store information related to digital keys, and a management server 70 that manages the plurality of digital keys. The plurality of digital keys include an owner key KO, which is a first digital key, and a friend key KF, which is a second digital key generated based on the first digital key. When the range of functions that the owner key KO can perform is changed by changing the authority information ATP7 in the owner key information DKO stored in the owner device 40, the management system 10 can set the range of functions that the friend key KF generated based on the owner key KO can perform, depending on the range of functions that the changed owner key KO can perform.

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

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

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

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

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

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

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

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

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

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

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

[0264] In the database DB, the authority information ATP7 may not be uniformly determined according to the type of digital key, but may be set for each digital key. Also, the authority information ATP7 does not have to be determined in the database DB.

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

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

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

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

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

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

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

[0272] <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 manages multiple digital keys that can be used for a vehicle, the multiple digital keys including a first digital key and a second digital key generated based on the first digital key, and when the range of functions that the first digital key can perform is changed, the server sets the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform.

[0273] [Appendix 2] The server according to Appendix 1, configured to change the range of functions that the second digital key can perform by changing the authority information indicating the range of functions that the second digital key can perform.

[0274] [Supplementary Note 3] The server according to Supplementary Note 2, which stores the authority information in the vehicle. [Appendix 4] A server as described in Appendix 2 or Appendix 3, which stores the authority information indicating the range of functions that the second digital key can perform in a device that stores information about the second digital key.

[0275] [Appendix 5] A server described in any one of Appendices 2 to 4, which stores the authority information indicating the range of functions that the first digital key can perform in a device that stores information about the first digital key.

[0276] [Supplementary Note 6] The server according to any one of Supplementary Note 2 to Supplementary Note 5, which stores the authority information. [Appendix 7] A server according to any one of Appendices 1 to 6, which, when the range of functions that the first digital key can perform is changed, sets the range of functions that the second digital key can perform to a range narrower than the range of functions that the first digital key can perform after the change.

[0277] [Appendix 8] A server as described in Appendix 7, which, when the range of functions that the first digital key can perform is changed, sets the range of functions that the second digital key can perform after the change to a range narrower than the range of functions that the second digital key could perform before the change.

[0278] [Appendix 9] A server as described in any one of Appendices 1 to 8, which, when the range of functions that the first digital key can perform is changed, sets the range of functions that the second digital key can perform according to the changed range of functions that the first digital key can perform if a predetermined condition is met, and does not change the range of functions that the second digital key can perform if the predetermined condition is not met.

[0279] [Appendix 10] A server described in any one of Appendices 1 to 9, wherein the plurality of digital keys further includes a third digital key, and the first digital key is a digital key generated based on the third digital key.

[0280] [Appendix 11] The digital key includes a share key that can be registered in multiple numbers to the vehicle, and when the range of functions that the share key can perform is changed, the server described in any one of Appendices 1 to 10 sets the range of functions that the registered share key can perform based on the registration request made by the share key, in accordance with the range of functions that the changed share key can perform. [Explanation of symbols]

[0281] ATP7, ST9...Authority Information D11, D21, D31...Registration request DK...Key information KS...Share Key 20...Vehicle 30…Devices 70...Administration server 28, 37, 72…Storage device RC...default conditions

Claims

1. A server that manages a plurality of digital keys that can be used for a vehicle, the plurality of digital keys include a first digital key and a second digital key generated based on the first digital key; When the range of functions that the first digital key can perform is changed, the range of functions that the second digital key can perform is set according to the changed range of functions that the first digital key can perform. server.

2. The range of functions that the second digital key can perform can be changed by changing authority information that indicates the range of functions that the second digital key can perform. The server of claim 1 .

3. The authorization information is stored in the vehicle. The server of claim 2.

4. The authorization information indicating the range of functions that the second digital key can perform is stored in a device that stores information about the second digital key. The server of claim 2.

5. The authorization information indicating the range of functions that the first digital key can perform is stored in a device that stores information about the first digital key. The server of claim 2.

6. Storing the authority information The server of claim 2.

7. When the range of functions that the first digital key can perform is changed, The range of functions that can be performed by the second digital key is set to a range narrower than the range of functions that can be performed by the first digital key after the change. The server of claim 1 .

8. When the range of functions that the first digital key can perform is changed, The range of functions that can be performed by the second digital key after the change is set to a range narrower than the range of functions that can be performed by the second digital key before the change. The server of claim 7.

9. When the range of functions that the first digital key can perform is changed, If a predetermined condition is met, the range of functions that the second digital key can perform is set according to the changed range of functions that the first digital key can perform; If the predetermined condition is not met, the range of functions that can be performed by the second digital key is not changed. The server of claim 1 .

10. the plurality of digital keys further includes a third digital key; The first digital key is a digital key generated based on the third digital key. The server of claim 1 .

11. the digital key includes a shared key that can be registered in multiple numbers to the vehicle; When the range of functions that the share key can perform is changed, the range of functions that the share key registered by the registration request made by the share key can perform is set according to the range of functions that the share key can perform after the change. The server of claim 1 .

12. A configuration method executed by a server that manages multiple digital keys available for a vehicle, the plurality of digital keys include a first digital key and a second digital key generated based on the first digital key; a step of receiving, by a communication device of the server, information that the range of functions that the first digital key can perform has been changed; and when the range of functions that the first digital key can perform is changed, the processing circuit of the server sets the range of functions that the second digital key can perform in accordance with the changed range of functions that the first digital key can perform. How to set it up.

13. A program stored in a storage device of a server that manages a plurality of digital keys that can be used for a vehicle, the plurality of digital keys include a first digital key and a second digital key generated based on the first digital key; When the range of functions that can be performed by the first digital key is changed, the processing circuit of the server executes a process of setting the range of functions that can be performed by the second digital key in accordance with the changed range of functions that can be performed by the first digital key. program.

14. a vehicle that stores information related to a digital key; a server that manages a plurality of digital keys that can be used for the vehicle; A system comprising: the plurality of digital keys include a first digital key and a second digital key generated based on the first digital key; When the range of functions that the first digital key can perform is changed, the range of functions that the second digital key can perform is set according to the changed range of functions that the first digital key can perform. system.

15. a plurality of devices storing information related to the digital key; a server that manages a plurality of digital keys; A system comprising: the plurality of digital keys include a first digital key and a second digital key generated based on the first digital key; When the range of functions that the first digital key can perform is changed, the range of functions that the second digital key can perform is set according to the changed range of functions that the first digital key can perform. system.

Images