Vehicle management server

Abstract

To provide a vehicle management server which prevents a management load of a vehicle that is sequentially used by a plurality of users from being centered on a specific person.SOLUTION: In a vehicle management system, a vehicle management server 3 comprises: a management unit 32 which manages a user account corresponding to a user who uses a vehicle and including a superordinate account, a medium account and a subordinate account; and a distribution unit 33 which distributes an electronic key of the vehicle to at least one of terminals possessed by the user. The management unit manages the superordinate account as the user account given with an authority for applying for registration or deletion of the medium account and the subordinate account corresponding to the superordinate account, manages the medium account as the user account given with an authority for applying for registration or deletion of the subordinate account corresponding to the medium account, and manages the subordinate account as the user account not given with an authority for applying for registration or deletion of other user accounts.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a vehicle management server.

Background Art

[0002] Patent Document 1 describes a vehicle control device including: a storage unit that stores terminal information of a mobile terminal; a communication unit that communicates with the mobile terminal based on the terminal information stored in the storage unit; an authentication information generation unit that generates authentication information for permitting starting of a vehicle; an authentication information notification unit that notifies the authentication information generated by the authentication information generation unit into the vehicle; a vehicle start authentication unit that performs authentication related to starting of the vehicle based on the received authentication information when the authentication information notified by the authentication information notification unit is received from the mobile terminal by the communication unit; and a vehicle start permission unit that permits starting of the vehicle based on an authentication result of the vehicle start authentication unit.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the prior art, regarding a passenger car used for carsharing and sequentially used by a plurality of users, the owner of the passenger car registers user accounts separately for specific users and unspecified users. An unspecified user applies to the owner for a date and time and a usage period, and an electronic key is issued when the owner approves. The unspecified user uses the passenger car using the electronic key. The authority to register or approve a user account is given only to the owner, and not to specific users or unspecified users. Therefore, vehicle management for the owner may become complicated.

[0005] In view of such a situation, an object of the present invention is to prevent the management burden of a vehicle sequentially used by a plurality of users from concentrating on a specific person.

Means for Solving the Problems

[0006] To achieve the above object, a vehicle management server according to the present invention includes a management unit that manages a plurality of user accounts respectively corresponding to a plurality of users who use a vehicle, and a distribution unit that distributes an electronic key of the vehicle to at least one of a plurality of terminals respectively owned by the plurality of users. The plurality of user accounts include a superior account, a middle account, and a lower account. The management unit manages the superior account and the middle account in association with each other, manages the middle account and the lower account in association with each other, manages the superior account as a user account to which the authority to apply for registration or deletion of the middle account and the lower account corresponding to the superior account is given, manages the middle account as a user account to which the authority to apply for registration or deletion of the lower account corresponding to the middle account is given, and manages the lower account as a user account to which the authority to apply for registration and deletion of other user accounts is not given.

Effects of the Invention

[0007] According to the present invention, it is possible to prevent the management burden of a vehicle sequentially used by a plurality of users from concentrating on a specific person.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Embodiments for Carrying Out the Invention

[0009] Hereinafter, the present invention will be described based on the illustrated embodiments. However, the present invention is not limited by the embodiments described below.

[0010] As shown in FIG. 1, the vehicle management system S includes a vehicle 1 such as a passenger car, and terminals 2 each owned by a plurality of users who sequentially use the vehicle 1. The vehicle 1 is a connected car and has a data communication ECU 11 and an electronic key ECU 12. The vehicle management system S further includes a connected car management server 3, a key management server 4, and a reservation management server 5.

[0011] The data communication ECU 11 and the connected car management server 3 are configured to be able to communicate with each other. The electronic key ECU 12 and the terminal 2 are configured to be able to perform short-range wireless communication by BLE (Bluetooth Low Energy) or the like. Also, the terminal 2 and the connected car management server 3 are configured to be able to communicate with each other. The connected car management server 3 is configured to be able to communicate with the key management server 4 and the reservation management server 5.

[0012] An electronic key for using the vehicle 1 is provided to the terminal 2. The provision of this electronic key can be performed from the key management server 4 via the connected car management server 3. When the terminal 2 with the provided electronic key performs short-range wireless communication with the electronic key ECU 12 of the vehicle 1 in the locked state, the electronic key ECU 12 communicates with the connected car management server 3 through the data communication ECU 11 to authenticate the electronic key provided to the terminal 2. When this electronic key is authenticated as being legitimate, the vehicle 1 is unlocked and can be started. Also, when the use of the vehicle 1 ends, the terminal 2 can communicate with the electronic key ECU 12 to lock the vehicle 1.

[0013] As shown in FIG. 2, the connected car management server 3 includes a reception unit 31, a management unit 32, and a distribution unit 33. Details of each unit will be described later.

[0014] The connected car management server 3, which is also called a vehicle management server, has a list for managing a plurality of users who sequentially use the vehicle 1. In this list, the accounts of the above-mentioned plurality of users are managed by being classified into any one of a higher-level account with higher-level authority, a middle-level account with middle-level authority, and a lower-level account with lower-level authority.

[0015] The key management server 4 receives a request from the connected car management server 3, generates an electronic key, and distributes the electronic key to the connected car management server 3. The reservation management server 5 manages the reservation of the vehicle 1 in the car-sharing service.

[0016] The connected car management server 3 is configured by computer hardware. Although not shown, the connected car management server 3 includes a CPU, an interface device, a display device, an input device, a drive device, an auxiliary storage device, and a memory device, which are interconnected by a bus.

[0017] The program that realizes the functions of the connected car management server 3 is provided by a recording medium such as a CD-ROM. When the recording medium storing the program is set in the drive device, the program is installed from the recording medium via the drive device into the auxiliary storage device. Alternatively, the installation of the program does not necessarily have to be performed by a recording medium, and it can also be downloaded from another computer via a network. The auxiliary storage device stores the installed program and also stores necessary files, data, etc.

[0018] When there is an instruction to start the program, the memory device reads out the program from the auxiliary storage device and stores it. The CPU realizes the functions of the connected car management server 3 according to the program stored in the memory device. The interface device is used as an interface for connecting to other computers through the network. The display device displays a GUI (Graphical User Interface), etc. according to the program. The input device is a keyboard, a mouse, etc.

[0019] Note that the vehicle 1, the terminal 2, the key management server 4, and the reservation management server 5 have the same computer hardware as the connected car management server 3.

[0020] FIG. 3 shows the flow of owner key distribution in the owner key service. The owner key service is a service that enables a vehicle owned by an owner, who is an ordinary user, to be used by the owner or other persons (such as the owner's family members, friends, etc.). Through the process shown in FIG. 3, an owner key with owner authority is distributed to the owner. First, in step S102, the owner's terminal 2 receives an input from the owner and sends an owner key distribution request to the connected car management server 3. Subsequently, in step S104, the reception unit 31 in the connected car management server 3 receives the owner key distribution request sent from the owner's terminal 2 in step S102. In the subsequent step S106, the management unit 32 in the connected car management server 3 sends a key distribution request for owner authority to the key management server 4. In the subsequent step S108, the key management server 4 generates a key and distributes the key to the connected car management server 3. In the subsequent step S110, the distribution unit 33 in the connected car management server 3 receives the key distributed from the key management server 4 in step S108 and sends the key to the owner's terminal 2.

[0021] Fig. 4 shows the flow of sub-owner key distribution in the owner key service. By this process, a key with sub-owner authority is distributed to the sub-owner. Step S202 is a step for classifying whether the key distribution to the sub-owner is due to the sub-owner's own request or the owner's request. In the former case, step S204 is performed next, and in the latter case, step S302 is performed next. In this way, on the system, the key application can be made from either the sub-owner or the owner. In step S204, the sub-owner's terminal 2 receives an input from the sub-owner and sends a key distribution request to the connected car management server 3. In the subsequent step S206, the reception unit 31 in the connected car management server 3 receives the key distribution request sent from the sub-owner's terminal 2 in step S204. In the subsequent step S208, the management unit 32 in the connected car management server 3 notifies the owner's terminal that it has received a key distribution request from the sub-owner. In this step, further, the owner makes an input on the owner's terminal to approve the key distribution to the sub-owner in response to the above notification. The owner's terminal receives the input and notifies the connected car management server 3 that the key distribution has been approved. In the subsequent step S210, the management unit 32 in the connected car management server 3 receives the notification from the owner's terminal and confirms the approval result by the owner. In the subsequent step S212, the management unit 32 in the connected car management server 3 sends a key distribution request for sub - owner authority to the key management server 4. In the subsequent step S214, the key management server 4 generates a key and distributes the key to the connected car management server 3. In the subsequent step S216, the distribution unit 33 in the connected car management server 3 receives the key distributed from the key management server 4 in step S214 and sends the key to the sub - owner's terminal 2.

[0022] In step S302, the owner uses their own terminal to perform a procedure for registering a sub - owner in the user list. The content of this procedure is sent from the owner's terminal to the connected car management server 3. After the reception unit 31 in the connected car management server 3 receives the content of the above - mentioned procedure, the management unit 32 updates the above - mentioned list. As a result, the said user is registered in the list as a sub - owner. In the subsequent step S304, the owner uses their own terminal to request the connected car management server 3 to distribute a key to the sub - owner. Subsequently, step S212 is performed.

[0023] Fig. 5 shows the flow of user key distribution in the owner key service. By this process, a key with user authority is distributed to the user. Steps S402 and S404 are steps for classifying whether the key distribution to the user is due to the user's own request, the sub - owner's request, or the owner's request. If it is due to the user's own request, step S406 is performed next. If it is due to the sub - owner's request, step S502 is performed next. If it is due to the owner's request, step S602 is performed next. In this way, on the system, the user, sub - owner, and owner can all apply for a key. In step S406, the user's terminal 2 receives an input from the user and sends a key distribution request to the connected car management server 3. In the subsequent step S408, the reception unit 31 in the connected car management server 3 receives the key distribution request sent from the user's terminal 2 in step S204. In the subsequent step S410, the management unit 32 in the connected car management server 3 determines whether there is a sub-owner associated with the user. If it is determined that there is a sub-owner associated with the user, step S414 is performed; otherwise, step S412 is performed. In step S412, the management unit 32 in the connected car management server 3 notifies the owner's terminal that it has received a key distribution request from the user. In this step, further, the owner makes an input on the owner's terminal to approve the key distribution to the user upon receiving the above notification. The owner's terminal receives the input and notifies the connected car management server 3 that the key distribution has been approved. Subsequently, step S416 is performed. In step S414, the management unit 32 in the connected car management server 3 notifies the sub-owner's terminal that it has received a key distribution request from the user. In this step, further, the sub-owner makes an input on the sub-owner's terminal to approve the key distribution to the user upon receiving the above notification. The sub-owner's terminal receives the input and notifies the connected car management server 3 that the key distribution has been approved. Subsequently, step S416 is performed. In step S416, the management unit 32 in the connected car management server 3 performs either the first process or the second process described below. First process: Receive the notification sent from the owner's terminal in step S412 and confirm the approval result by the owner. Second process: Receive the notification sent from the sub-owner's terminal in step S414 and confirm the approval result by the sub-owner. In the subsequent step S418, the distribution unit 33 in the connected car management server 3 sends a key distribution request for user authority to the key management server 4. In the subsequent step S420, the key management server 4 generates a key and distributes the key to the connected car management server 3. In the subsequent step S422, the distribution unit 33 in the connected car management server 3 receives the key distributed from the key management server 4 in step S214 and sends the key to the user's terminal 2.

[0024] In step S502, the sub-owner performs a procedure for registering a user in the user list using their own terminal. The content of this procedure is sent from the sub-owner's terminal to the connected car management server 3. After the reception unit 31 in the connected car management server 3 receives the content of the above procedure, the management unit 32 updates the above list. As a result, the said user is registered in the list as a user. In the subsequent step S504, the sub-owner requests the connected car management server 3 to distribute a key to the user using their own terminal. Subsequently, step S418 is performed.

[0025] In step S602, the owner performs a procedure for registering a user in the user list using their own terminal. The content of this procedure is sent from the owner's terminal to the connected car management server 3. After the reception unit 31 in the connected car management server 3 receives the content of the above procedure, the management unit 32 updates the above list. As a result, the said user is registered in the list as a user. In the subsequent step S604, the owner requests the connected car management server 3 to distribute a key to the user using their own terminal. Subsequently, step S418 is performed.

[0026] Fig. 6 shows the flow of the car-sharing service. The car-sharing service is different from the owner key service assuming use by general users in that it is a service assuming use by a corporation. First, in step S702, the terminal 2 of the user of the car-sharing service receives a vehicle reservation operation by the user and sends a reservation request to the connected car management server 3. This reservation request is received by the reception unit 31 in the connected car management server 3. In the subsequent step S704, the management unit 32 in the connected car management server 3 sends the reservation request to the reservation management server 5. In the subsequent step S706, the reservation management server 5 confirms the availability of the vehicle reservation based on the reservation request sent from the connected car management server 3 in step S704. In the subsequent step S708, the reservation management server 5 determines whether the vehicle reservation based on the above reservation request is possible. If it is determined that the vehicle reservation based on the above reservation request is possible, step S710 is performed. If it is determined that the vehicle reservation based on the above reservation request is not possible, it is sent from the reservation management server 5 to the connected car management server 3 that the vehicle reservation is not possible, and it is also sent from the management unit 32 in the connected car management server 3 to the user's terminal. Subsequently, step S702 is performed again. In step S710, the reservation management server 5 notifies the connected car management server 3 of the reservation availability result, that is, in this case, that the reservation is possible. In the subsequent step S712, the reception unit 31 in the connected car management server 3 receives a key distribution request sent from the user's terminal 2. In the subsequent step S714, the management unit 32 in the connected car management server 3 sends a key distribution request for user authority to the key management server 4. In the subsequent step S716, the key management server 4 generates a key and distributes the key to the connected car management server 3. In the subsequent step S718, the distribution unit 33 in the connected car management server 3 receives the key distributed from the key management server 4 in step S108 and sends the key to the user's terminal 2.

[0027] In the above embodiment, the user accounts of the vehicle 1 are classified and managed by the management unit 32 into a top-level account, a middle-level account, and a bottom-level account. The top-level account can be a user account corresponding to the owner of the vehicle. The top-level account has the right to apply for registration or deletion of middle-level accounts and bottom-level accounts. The middle-level account has the right to apply for registration or deletion of bottom-level accounts when permitted by the top-level account. The bottom-level account is managed as a user account that does not have the right to apply for registration and deletion of other user accounts. The top-level account is managed in association with the registered middle-level accounts and bottom-level accounts. The middle-level account is managed in association with the registered bottom-level accounts. The middle-level account has the right to set the available period and available time zone for each registered bottom-level account.

[0028] As described above, each embodiment shown in FIGS. 3 to 5 can be utilized in the owner key service, and the embodiment shown in FIG. 6 can be utilized in the car-sharing service. That is, in either the owner key service or the car-sharing service, the configuration of a top-level account, a middle-level account, and a bottom-level account can be adopted. Conventionally, the top-level account (i.e., the owner of the vehicle) managed all user accounts. However, according to this embodiment, a plurality of middle-level accounts (sub-owners) are provided, and a plurality of bottom-level accounts (users) are associated with each of the middle-level accounts. The middle-level account does not manage all the bottom-level accounts associated with the top-level account, but manages a relatively small number of bottom-level accounts associated with the middle-level account. Thereby, a part of the management burden of the top-level account is dispersed to a plurality of middle-level accounts, and the management burden of the top-level account is reduced. Improvement in management systems and security is also expected.

[0029] That is, the key management server grants specified permissions and manages the account in response to an application from a higher-level account. The higher-level account lends the vehicle to a middle-level account (sub-owner) for a certain period. The middle-level account (sub-owner) can distribute an electronic key to a lower-level account (user) as an owner key service or a car-sharing service within the granted authority range. The lower-level account (user) can receive the key and use the vehicle by specifying the date and time and making a key distribution reservation.

[0030] Also, when the higher-level account is deleted from the list, the middle-level account and the lower-level account associated with the higher-level account are deleted in a linked manner in a batch. When the middle-level account is deleted from the list, the lower-level accounts associated with the middle-level account are deleted in a linked manner in a batch. When applying for the registration of a lower-level account, the higher-level account can associate the lower-level account with an arbitrary middle-level account. In this way, when an account is deleted, the accounts associated with that account are deleted in a linked manner in a batch. Therefore, the omission of deleting unnecessary accounts is eliminated, and management becomes easier.

[0031] Keys issued by the key management server are given different functions and permissions for every three accounts. For example, different functions and permissions can be given regarding the following points. · Whether the reset operation of the driving distance is possible · Whether the remote ignition on operation by the electronic key is possible · Whether the remote air conditioner on operation by the electronic key is possible · Whether the limitation of the door and trunk opening / closing operations by the electronic key is possible

[0032] The higher-level account can register the account information of the middle-level account and the lower-level account in the connected car management server. The available period and time zone of the middle account and the associated lower accounts can be set. The account information of the upper account, middle account, and lower account can be deleted from the connected server. When the account information of the upper account is deleted, the account information of the associated middle account and lower account will also be deleted in a linked batch. Similarly, when the account information of the middle account is deleted, the account information of the linked lower account will also be deleted in a linked batch. The account information of the lower account can be linked to any middle account. It is possible to receive a notification of the reservation application of the lower account.

[0033] The middle account (sub-owner) can register and delete the lower account on the connected car management server. It is also possible to restrict (make it unusable) the registration and deletion permissions of the middle account by the upper account's authority. · It is possible to receive a notification of the reservation application of the lower account.

[0034] The lower account (user) can be set as a user account that cannot register and delete other user accounts on the connected car management server. When usage request conditions (date / time, time zone, location, etc.) are applied from the lower account, the vehicle reservation management server checks the availability of the reservation and makes a reservation if there is availability. That is, it is automatically approved by the middle account or upper account associated with that lower account. Alternatively, manual approval by the upper account or middle account is also possible. The automatic and manual switching can be performed by the upper account or middle account.

[0035] In addition, by providing a middle-level account, when searching for a certain lower-level account in a user's list, instead of searching all lower-level accounts, only a plurality of lower-level accounts associated with a certain middle-level account can be set as search targets. Therefore, compared with the case where no middle-level account is provided and all user accounts associated with the owner's account are search targets, the search targets are narrowed down, and an improvement in search speed is expected. That is, according to each embodiment of the present invention, an improvement in the performance of the computer can be expected.

[0036] In connection with the above embodiment, the following supplementary notes are disclosed. [Supplementary Note 1] A management unit that manages a plurality of user accounts corresponding to a plurality of users who use a vehicle, A distribution unit that distributes an electronic key of the vehicle to at least one of a plurality of terminals respectively owned by the plurality of users and the plurality of user accounts include a top-level account, a middle-level account, and a lower-level account, the management unit manages by associating the top-level account with the middle-level account, and manages by associating the middle-level account with the lower-level account, manages the top-level account as a user account to which the authority to apply for registration or deletion of the corresponding middle-level account and lower-level account is given, manages the middle-level account as a user account to which the authority to apply for registration or deletion of the corresponding lower-level account is given, manages the lower-level account as a user account that is not given the authority to apply for registration and deletion of other user accounts, a vehicle management server. [Supplementary Note 2] The management unit manages a plurality of middle-level accounts by associating them with the top-level account, Manage the upper account as a user account with the authority to set the available period and available time zone of the vehicle for each of the plurality of middle accounts. The distribution unit For each of the plurality of middle accounts, distribute an electronic key that enables the vehicle to be used during the available period and time zone of the vehicle set by the upper account. The management unit Manage a plurality of lower accounts in association with the middle account. Manage the middle account as a user account with the authority to set the available period and available time zone of the vehicle within the range set by the upper account for each of the plurality of lower accounts. The distribution unit For each of the plurality of lower accounts, distribute an electronic key that enables the vehicle to be used during the available period and time zone of the vehicle set by the middle account. The vehicle management server according to Appendix 1. [Appendix 3] Further include a reception unit that receives a registration application for a user account. When the reception unit receives a registration application for a lower account from the upper account, the management unit associates the lower account with one of the plurality of middle accounts. The vehicle management server according to Appendix 2. [Appendix 4] The management unit manages the upper account as a user account with the authority to set the available period and available time zone of the vehicle of the plurality of middle accounts corresponding to the upper account without overlap. The vehicle management server according to any one of Appendices 1 to 3. [Appendix 5] The reception unit Receives a vehicle use application from the lower account. Notifies the upper account or the middle account associated with the lower account that there has been a vehicle use application. Receiving approval from the upper account or the middle account for the vehicle use application; The distribution unit distributes an electronic key corresponding to the vehicle use application to the lower account; The vehicle management server described in Appendix 4. [Appendix 6] The management unit manages the upper account as a user account with the authority to restrict the use of the functions provided in the vehicle for the middle account and the lower account associated with the upper account; manages the middle account as a user account with the authority to restrict the use of the functions provided in the vehicle within the scope of the authority given by the upper account for the middle account and the lower account associated with the middle account; The vehicle management server described in Appendix 5. [Appendix 7] The management unit When there is an application for deleting the upper account, the upper account is deleted from the list, and the middle account associated with the upper account and the lower account associated with the middle account are deleted from the list; When there is an application for deleting the middle account, the middle account is deleted from the list, and the lower account associated with the middle account is deleted from the list; The vehicle management server described in Appendix 6. [Appendix 8] The vehicle management server described in Appendix 7, wherein the registration application and the deletion application of the user account are completed by multi-factor authentication.

[0037] As described above, the embodiments of the present invention have been described. However, the present invention is not limited to the described embodiments, and various modifications and changes are possible based on the technical idea of the present invention.

Explanation of Reference Numerals

[0038] S Vehicle management system 1 Vehicle 2 Terminal 3 Connected Car Management Server 31 Reception Unit 32 Management Unit 33 Distribution Unit 4 Key Management Server 5 Reservation Management Server

Claims

1. A management unit that manages a plurality of user accounts respectively corresponding to a plurality of users who use a vehicle, and a distribution unit that distributes an electronic key of the vehicle to at least one of the plurality of terminals respectively owned by the plurality of users. The vehicle management server is provided with: The plurality of user accounts include a top-level account, a middle-level account, and a lower-level account. The management unit: Manages the top-level account and the middle-level account in association with each other, and manages the middle-level account and the lower-level account in association with each other. Manages the top-level account as a user account that is given the authority to apply for registration or deletion of the middle-level account and the lower-level account corresponding to the top-level account. Manages the middle-level account as a user account that is given the authority to apply for registration or deletion of the lower-level account corresponding to the middle-level account. Manages the lower-level account as a user account that is not given the authority to apply for registration and deletion of other user accounts. A vehicle management server.

2. The management unit: Manages a plurality of middle-level accounts in association with the top-level account. Manages the top-level account as a user account that is given the authority to set the available period and available time zone of the vehicle for each of the plurality of middle-level accounts. The distribution unit: For each of the plurality of middle-level accounts, distributes an electronic key that enables the vehicle to be used during the available period and time zone of the vehicle set by the top-level account. The management unit: Manages a plurality of lower-level accounts in association with the middle-level account. Manages the middle-level account as a user account that is given the authority to set the available period and available time zone of the vehicle within the range set by the top-level account for each of the plurality of lower-level accounts. The distribution unit: For each of the plurality of lower-level accounts, distributes an electronic key that enables the vehicle to be used during the available period and time zone of the vehicle set by the middle-level account. The vehicle management server according to Claim 1.

3. The vehicle management server further includes a reception unit that receives an application for registration of a user account. When the reception unit receives an application for registration of a lower-level account from the top-level account, the management unit associates the lower-level account with any one of the plurality of middle-level accounts. The vehicle management server according to Claim 2.

4. The management unit manages the upper-level account as a user account with the authority to set the available period and available time zone of the vehicle for a plurality of middle-level accounts corresponding to the upper-level account so that they do not overlap, for the vehicle management server according to claim 3.

5. The reception unit receives a vehicle use application from the lower-level account, notifies the upper-level account or the middle-level account associated with the lower-level account that there has been a vehicle use application, receives approval from the upper-level account or the middle-level account for the vehicle use application, and the distribution unit distributes an electronic key corresponding to the vehicle use application to the lower-level account, for the vehicle management server according to claim 4.

6. The management unit manages the upper-level account as a user account with the authority to restrict the use of functions provided in the vehicle for the middle-level accounts and lower-level accounts associated with the upper-level account, and manages the middle-level account as a user account with the authority to restrict the use of functions provided in the vehicle within the scope of the authority given from the upper-level account for the middle-level accounts and lower-level accounts associated with the middle-level account, for the vehicle management server according to claim 5.

7. When there is a deletion application for the upper-level account, the management unit deletes the upper-level account from the list and deletes the middle-level account associated with the upper-level account and the lower-level account associated with the middle-level account from the list, and when there is a deletion application for the middle-level account, the management unit deletes the middle-level account from the list and deletes the lower-level account associated with the middle-level account from the list, for the vehicle management server according to claim 6.

8. The registration application and deletion application of the user account are completed by multi-factor authentication, for the vehicle management server according to claim 7. ​ ​

Images