Methods for managing shared vehicles, server equipment, and computer programs

Abstract

To improve convenience for drivers who reserve shared vehicles. [Solution] At the first time point, first identification information including information identifying the driver 40 is transmitted from the mobile device 12 to the server device 11. The server device 11 verifies whether the driver's license of the driver 40 is valid at the first time point based on the first identification information. If the driver's license is confirmed to be valid, the server device 11 completes the reservation of the shared vehicle 20 by the driver 40 and enables the mobile device 12 to download authentication information. At the second time point, which is after the first time point, if the driver's license is confirmed to be valid within the usage period of the shared vehicle 20, the use of the shared vehicle 20 using the authentication information is permitted.

Description

Technical Field

[0001] The present invention relates to a method for managing a shared vehicle jointly used by a plurality of drivers. The present invention also relates to a server device used in the method and a computer program executable by a processor mounted on the server device.

Background Art

[0002] Patent Document 1 discloses a system for reserving a shared vehicle jointly used by a plurality of drivers. A driver who wishes to use the shared vehicle makes a reservation application from a client device to a server device. At the time of application, information including the expiration date of the driver's driver's license is transmitted to the server device. In the server device, it is confirmed whether the expiration date expires before the last day of the use period of the shared vehicle. If the expiration date expires before the last day, the application is rejected.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a need to improve the convenience of drivers who make reservations for shared vehicles.

Means for Solving the Problems

[0005] One exemplary aspect that can be provided by the present disclosure is a method for managing a shared vehicle jointly used by a plurality of drivers, At a first point in time, first identification information including information identifying a driver is transmitted from a first client device to a server device, In the server device, based on the first identification information, it is confirmed whether the driver's license is valid at the first time point in time. If the driver's license is confirmed to be valid, the server device will complete the reservation of the shared vehicle by the driver and enable the second client device to download the authentication information. If, at a second point in time following the first point in time, it is confirmed that the driver's license is valid during the period of use of the shared vehicle, then permission to use the shared vehicle based on the authentication information will be granted.

[0006] One example of an embodiment that may be provided by this disclosure is a server device, At the first point in time, an interface receives first identification information, including information that identifies the driver, from the first client device, A processor that, if it is confirmed that the driver's license is valid at the first time point based on the first identification information, allows the driver to make a reservation for the shared vehicle, and enables the download of authentication information by a second client device to make the shared vehicle available for use if it is confirmed that the driver's license is valid at a second time point later than the first time point. It is equipped with.

[0007] One example of an embodiment that may be provided by this disclosure is a computer program that can be executed by a processor installed in a server device, By being executed, the server device will At the first point in time, the first client device receives first identification information, including information that identifies the driver. If, based on the first identification information, it is confirmed that the driver's license is valid at the first time point, the reservation of the shared vehicle by the driver is completed, and if, at a second time point later than the first time point, it is confirmed that the driver's license is valid, the second client device is made able to download authentication information to enable the use of the shared vehicle.

[0008] According to the configurations described in each of the above examples, even if a driver's license expires during the period of use of the shared vehicle, if the driver's license is valid at the first point in time, the reservation is confirmed and the authentication information necessary for using the shared vehicle can be downloaded by the second client device. This gives the driver time to renew their driver's license by the second point in time. Therefore, it is possible to improve the convenience of drivers who make reservations for shared vehicles. On the other hand, if the driver's license is not valid when using the authentication information, the use of the shared vehicle is not permitted, so compliance with the law can be ensured. [Brief explanation of the drawing]

[0009] [Figure 1] This illustrates the configuration of a reservation management system according to one embodiment. [Figure 2] Figure 1 illustrates the functional configuration of the server device. [Figure 3] Figure 2 shows an example of the processing flow performed by the mobile device. [Figure 4] Figure 2 shows an example of the processing flow executed by the processor. [Figure 5] Figure 2 shows another example of the processing flow executed by the processor. [Modes for carrying out the invention]

[0010] An example of an embodiment will be described in detail below, with reference to the attached drawings. In each drawing, the scale has been appropriately changed to make the illustrated elements recognizable.

[0011] Figure 1 schematically illustrates the configuration of a reservation management system 10 according to one embodiment. The reservation management system 10 is a system for managing reservations for the use of a shared vehicle 20. The shared vehicle 20 is a vehicle used jointly by multiple drivers.

[0012] The reservation management system 10 includes a server device 11 and a mobile device 12. The mobile device 12 can be carried by the driver 40. The server device 11 and the mobile device 12 are configured to transmit and receive data via a communication network 30. The data to be transmitted and received may be in the form of analog data or digital data according to the specifications of each device and the communication network 30.

[0013] As illustrated in FIG. 2, the server device 11 includes a communication interface 111. The communication interface 111 is configured as a hardware interface that permits data transmission and reception with the mobile device 12. When the data is in the form of analog data, the communication interface 111 includes an appropriate conversion circuit including an A / D converter and a D / A converter.

[0014] A driver 40 who wishes to use the shared vehicle 20 needs to perform user registration in advance. Specifically, license information LC that identifies his / her driver's license is transmitted from the mobile device 12 to the server device 11. The license information LC includes information that identifies the driver 40 and information indicating the expiration date of the driver's license.

[0015] The server device 11 includes a processor 112 and a storage 113. When the license information LC is received by the communication interface 111, the processor 112 stores the license information LC in the storage 113.

[0016] The storage 113 is a storage device that can be realized by a semiconductor memory, a hard disk device, a magnetic tape device, etc. The storage 113 may be an independent device capable of transmitting and receiving data with the server device 11 via the communication network 30.

[0017] Processor 112 can be implemented by at least one general-purpose microprocessor that operates in cooperation with at least one general-purpose memory. Examples of general-purpose microprocessors can include CPUs, MPUs, and GPUs. Examples of general-purpose memories can include ROM and RAM. In this case, various computer programs for realizing the functions exemplified in the present disclosure can be stored in the ROM. The ROM is an example of a non-transitory computer-readable medium that stores a computer program. The general-purpose microprocessor designates at least a part of the computer program stored on the ROM and expands it onto the RAM, and executes the above-described processing in cooperation with the RAM. Note that a part of the storage 113 may be used as a general-purpose memory.

[0018] Processor 112 may also be implemented by at least one dedicated integrated circuit capable of executing the above computer program. Examples of dedicated integrated circuits include microcontrollers, ASICs, FPGAs, etc. In this case, the above computer program is pre-installed in at least one storage element included in the dedicated integrated circuit. The storage element is an example of a non-transitory computer-readable medium that stores a computer program. Processor 112 may be implemented by a combination of a general-purpose microprocessor and a dedicated integrated circuit.

[0019] While referring to FIGS. 3 and 4, a reservation management method for the shared vehicle 20 performed by the server device 11 and the mobile device 12 configured as described above will be described. [[ID=lo]]

[0020] As described above, the driver 40 transmits the license information LC from the mobile device 12 to the server device 11 in order to perform user registration (STEP10 in FIG. 3). The license information LC is received by the communication interface 111 of the server device 11 (STEP20 in FIG. 4). The processor 112 of the server device 11 stores the license information LC in the storage 113 (STEP21 in FIG. 4).

[0021] Subsequently, when the driver 40 wishes to reserve the use of the shared vehicle 20, they perform the reservation procedure from the mobile device 12. Specifically, reservation identification information RS is transmitted from the mobile device 12 to the server device 11 (Figure 2; STEP 11 in Figure 3). This timing is an example of the first point in time.

[0022] The reservation identification information RS includes information that identifies the driver 40 and information that identifies the period of use of the shared vehicle 20. The reservation identification information RS is an example of primary identification information.

[0023] As illustrated in Figure 4, the reservation identification information RS is received by the communication interface 111 (STEP 22). The processor 112 determines whether the driver's license of driver 40 is valid based on the reservation identification information RS (STEP 23). Specifically, information identifying driver 40 is extracted from the reservation identification information RS and compared with the driver's license information LC of driver 40 stored in the storage 113.

[0024] If it is determined at this point that driver 40's driver's license is invalid (expired) (NO in STEP 23), the processor 112 sends a failure notification information UA ​​indicating that the reservation was unsuccessful to the mobile device 12 via the communication interface 111 (Figure 2; STEP 24 in Figure 4). After that, the process ends.

[0025] If it is determined that driver 40's driver's license is valid (YES in STEP 23), the processor 122 generates authentication information AT and makes it available for download (STEP 25). In addition, as illustrated in Figure 2, the processor 122 transmits confirmation notification information AP, indicating that the reservation has been confirmed, to the mobile device 12 via the communication interface.

[0026] The confirmation notification information AP contains information for downloading the authentication information AT. An example of such information is a link to a download URL. The authentication information AT is configured to enable the use of the shared vehicle 20 when downloaded to the mobile device 12.

[0027] Specifically, as illustrated in Figure 1, when a driver 40 carrying a mobile device 12 approaches a shared vehicle 20, an authentication process using short-range wireless communication is performed between an authentication device 21 located inside the shared vehicle 20 and the mobile device 12, which has downloaded authentication information AT. The authentication device 21 houses a key device 22 that can remotely control the operation of the locking and unlocking device of the shared vehicle 20. The authentication device 21 is equipped with an actuator for operating a movable part provided on the key device 22. Once the authentication process is successful, the authentication device 21 causes the key device 22 to unlock the doors of the shared vehicle 20. This makes it possible for the driver 40 to use the shared vehicle 20.

[0028] Alternatively, authentication may be performed using short-range wireless communication between the mobile device 12, which has downloaded the authentication information AT, and a control device (not shown) for controlling the operation of the locking / unlocking device installed in the shared vehicle 20. Once authentication is successful, the control device causes the locking / unlocking device to unlock the doors of the shared vehicle 20. In other words, in this example, the mobile device 12, which has downloaded the authentication information AT, is used as the key device.

[0029] As illustrated in Figure 3, the mobile device 12 determines whether the reservation based on the reservation identification information RS has been made (STEP 12). Specifically, it determines whether it has received a confirmation notification information AP or a rejection notification information UA ​​from the server device 11. If a rejection notification information UA ​​is received (NO in STEP 12), a notification that the reservation could not be made due to the expiration of the driver's license is made in an appropriate manner, and the process ends.

[0030] If the confirmation notification information AP is received (YES in STEP 12), the driver 40 downloads the authentication information AT from the server device 11 before using the shared vehicle 20. When instructions are entered through the appropriate user interface provided by the mobile device 12, a download request DR is sent from the mobile device 12 to the server device 11 (Figure 2; STEP 13 in Figure 3).

[0031] As illustrated in Figure 4, the processor 112 of the server device 11 determines whether a download request DR has been received via the communication interface 111 (STEP 26). This process is repeated until it is determined that a download request DR has been received (NO in STEP 26).

[0032] When it is determined that a download request DR has been received (YES in STEP 26), the processor 112 transmits authentication information AT from the communication interface 111 to the mobile device 12 (Figure 2; STEP 27 in Figure 4).

[0033] As illustrated in Figure 3, the authentication information AT is received by the mobile device 12 (STEP 14). Subsequently, when the shared vehicle 20 is actually to be used, the driver 40 inputs an instruction indicating their intention to start using the vehicle through an appropriate user interface provided by the mobile device 12. This timing is an example of the second point in time. The mobile device 12 determines whether the instruction has been input (STEP 15). This process is repeated until it is determined that the instruction has been input (NO in STEP 15).

[0034] When an instruction indicating the intention to start using the device is entered (YES in STEP 15), the mobile device 12 determines whether the driver's license of driver 40 is valid by referring to the license information LC (STEP 16).

[0035] If the driver's license is determined to be invalid at this point (NO in STEP 16), the mobile device 12 performs a process to invalidate the downloaded authentication information AT (STEP 17). In other words, the driver 40 is prohibited from using the shared vehicle 20.

[0036] If the driver's license is still deemed valid at this point (YES in STEP 16), the mobile device 12 performs the authentication process using the downloaded authentication information AT. In other words, the driver 40 is permitted to use the shared vehicle 20.

[0037] According to the configuration of this embodiment, even if the driver's license expires during the period of use of the shared vehicle 20, the reservation is confirmed if the driver's license is valid at the time of reservation, and the authentication information AT necessary for using the shared vehicle 20 can be downloaded to the mobile device 12. This gives the driver 40 time to renew their driver's license before actually using the shared vehicle 20. Therefore, the convenience of the driver 40 making a reservation for the shared vehicle 20 can be improved. On the other hand, if the driver's license is not valid when using the authentication information AT, the use of the shared vehicle 20 will not be permitted, thus ensuring compliance with the law.

[0038] If a driver's license is renewed after a reservation for the use of the shared vehicle 20 has been made, the driver 40 transmits a renewed driver's license information UL containing the information of the renewed driver's license from the mobile device 12 to the server device 11. As illustrated in Figure 2, the renewed driver's license information UL is received by the communication interface 111 of the server device 11. The renewed driver's license information UL is an example of second identification information. The transmission timing of the renewed driver's license information UL is an example of a third point in time.

[0039] The processing related to the renewed license information UL is substantially the same as the processing related to the license information LC, as explained with reference to Figures 3 and 4. That is, the processor 112 of the server device 11 updates the license information LC stored in the storage 113 with the received renewed license information UL.

[0040] In this example, the processor 112 determines, based on the reservation identification information RS, whether the driver's license of the driver 40 expires before or during the period of use of the shared vehicle 20 (STEP 28 in Figure 4).

[0041] If it is determined that the expiration date will not expire (NO in STEP 28), the processor 112 terminates processing because compliance with the law is ensured in the use of the shared vehicle 20 by the authentication information AT.

[0042] If it is determined that the expiration date has passed (YES in STEP 28), the processor 112 determines whether the driver's license of driver 40 has been renewed after the generation of the authentication information AT (STEP 29). Specifically, it determines whether the renewed license information UL has been received via the communication interface 111.

[0043] When it is determined that the renewed license information UL has been received (YES in STEP 29), the processor 112 updates the authentication information AT and makes it available for download by the mobile device 12 (STEP 25).

[0044] Subsequently, when a download request DR is received from the mobile device 12 (YES in STEP 26), the processor 112 transmits the updated authentication information AT to the mobile device 12 via the communication interface 111 (STEP 27). The driver 40 then uses the updated authentication information AT to perform the authentication process when actually using the shared vehicle 20.

[0045] If the renewal license information UL is not received even after the usage period for the shared vehicle 20 has begun (NO in STEP 29), the processor 112 determines that the use of the shared vehicle 20 was not permitted and terminates the process.

[0046] This configuration allows for a smooth transition to a state where compliance is ensured, while maintaining the reservation for the shared vehicle 20 that was established based on the initial driver's license information LC. Since there is no need to go through the reservation procedure again, it improves convenience for drivers who reserve the shared vehicle 20.

[0047] As illustrated in Figure 3, if the authentication information AT generated based on the initial driver's license information LC becomes invalid due to the expiration of the driver's license, the driver may be given the opportunity to enter the renewed driver's license information UL. In this case, a driver 40 who renewed their driver's license after the reservation for use of the shared vehicle 20 was made, but forgot to register the information of the renewed driver's license, can be given the opportunity to obtain permission to use the shared vehicle 20. Since the driver can obtain the updated authentication information AT while maintaining the initial reservation, the convenience for drivers making reservations for the shared vehicle 20 can be improved.

[0048] In the embodiments described so far, the same mobile device 12 is used to transmit license information LC and download authentication information AT. However, as illustrated in Figure 1, the reservation management system 10 may include a reservation client device 13. The reservation client device 13 is a device used by the driver 40 to reserve the use of the shared vehicle 20. The reservation client device 13 may be a device installed in a specific location or a mobile device.

[0049] In this case, the reservation client device 13 is an example of a first client device, and the mobile device 12 is an example of a second client device. In other words, in the above embodiment, the mobile device 12 operates as both a first client device and a second client device. The renewed license information UL may be transmitted from the reservation client device 13 or from the mobile device 12.

[0050] As illustrated in Figure 1, the reservation management system 10 may include a management client device 14. The management client device 14 is a device used by the manager of the shared vehicle 20. The management client device 14 may be a device installed in a specific location or a mobile device. The management client device 14 is an example of a third-party client device.

[0051] The administrator of the shared vehicle 20 is required to register the vehicle in advance. Specifically, as illustrated in Figure 2, the administrator sends expiration date information PR, which specifies the expiration dates for the vehicle inspection and vehicle insurance related to the shared vehicle 20, from the management client device 14 to the server device 11. If the shared vehicle 20 is subject to a lease agreement, the expiration date information PR may include information specifying the expiration date of the said agreement.

[0052] When the expiration information PR is received by the communication interface 111 of the server device 11, the processor 112 saves the expiration information PR to the storage 113.

[0053] As illustrated in Figure 2, the reservation identification information RS transmitted from the mobile device 12 (or reservation client device 13) to the server device 11 may include vehicle identification information VC that identifies the shared vehicle 20 to be used. Vehicle identification information VC is an example of third-party identification information.

[0054] In this case, as illustrated in Figure 5, the processor 112 of the server device 11 identifies the shared vehicle 20 to be used based on the vehicle identification information VC received via the communication interface 111 (STEP 30).

[0055] Next, the processor 112 verifies whether at least one of the identified shared vehicle 20 is valid, including vehicle inspection, vehicle insurance, and lease agreement (STEP 31). Specifically, the shared vehicle 20 identified by the vehicle identification information VC is compared with the expiration information PR stored in the storage 113.

[0056] If it is determined that the vehicle inspection, vehicle insurance, and lease agreement have not expired (YES in STEP 31), then there are no expiration date issues with the shared vehicle 20 being used, and the processor 112 terminates processing.

[0057] If it is determined that at least one of the vehicle inspection, vehicle insurance, and lease agreements has expired (NO in STEP 31), the processor 112 sends notification information NT indicating that the shared vehicle 20 is unavailable to the management client device 14 via the communication interface 111 (Figure 2; STEP 32 in Figure 5). The process then terminates.

[0058] When notification information NT is received by the management client device 14, the administrator is notified via an appropriate user interface that the shared vehicle 20 related to the reservation identification information RS is unavailable. The administrator takes measures such as preparing a replacement shared vehicle 20 whose vehicle inspection, vehicle insurance, and lease agreement have not expired, or taking steps to restore the vehicle to a state where the expiration dates have not expired.

[0059] This configuration helps to avoid situations where compliance with the law regarding the use of the shared vehicle 20 is compromised due to circumstances on the administrator's side. Therefore, it can improve convenience for drivers 40 who make reservations for the shared vehicle 20.

[0060] The configurations described herein are merely examples to facilitate understanding of this disclosure. Each configuration example may be modified and combined with other configuration examples as appropriate, without departing from the spirit of this disclosure.

[0061] The configurations listed below also constitute part of this disclosure. Item 1: A method for managing a shared vehicle used jointly by multiple drivers, At the first point in time, the first client device transmits first identification information, including information identifying the driver, to the server device. In the server device, based on the first identification information, it is confirmed whether the driver's license is valid at the first time point in time. If the driver's license is confirmed to be valid, the server device will complete the reservation of the shared vehicle by the driver and enable the second client device to download the authentication information. If, at a second time point after the first time point, it is confirmed that the driver's license is valid during the period of use of the shared vehicle, permission will be granted to use the shared vehicle based on the authentication information. Management methods for shared vehicles. Item 2: At a third time point, which is after the first time point, the first client device or the second client device transmits second identification information, including the updated driver's license information, to the server device. In the server device, the authentication information is updated based on the second identification information, and the download by the second client device is enabled. The management method for the shared vehicles described in item 1. Item 3: Third identification information, including information identifying the shared vehicle, is transmitted from the first client device to the server device. The server device verifies whether at least one of the vehicle inspection, vehicle insurance, and lease agreement for the shared vehicle is valid. If it is confirmed that at least one of the aforementioned vehicle inspection, vehicle insurance, and lease agreement is invalid, a notification is sent from the server device to a third-party client device used by the administrator of the shared vehicle. The management method for shared vehicles as described in item 1 or 2. Item 4: The first client device and the second client device are identical. The method for managing shared vehicles as described in any one of items 1 to 3. Item 5: The aforementioned authentication information is used to operate a key device located inside the shared vehicle in order to lock and unlock the shared vehicle. A method for managing shared vehicles as described in any one of items 1 through 4. [Explanation of Symbols]

[0062] 11: Server device, 12: Mobile device, 13: Reservation client device, 14: Management client device, 20: Shared vehicle, 22: Key device, 40: Driver, AT: Authentication information, RS: Reservation identification information, UL: Renewal license information, VC: Vehicle identification information

Claims

1. A method for managing a shared vehicle used jointly by multiple drivers, At the first point in time, the first client device transmits first identification information, including information identifying the driver, to the server device. In the server device, based on the first identification information, it is confirmed whether the driver's license is valid at the first time point in time. If the driver's license is confirmed to be valid, the server device will complete the reservation of the shared vehicle by the driver and enable the second client device to download the authentication information. If, at a second time point after the first time point, it is confirmed that the driver's license is valid during the period of use of the shared vehicle, permission will be granted to use the shared vehicle based on the authentication information. Management methods for shared vehicles.

2. At a third time point, which is after the first time point, the first client device or the second client device transmits second identification information, including the updated driver's license information, to the server device. In the server device, the authentication information is updated based on the second identification information, and the download by the second client device is enabled. The method for managing a shared vehicle according to claim 1.

3. Third identification information, including information identifying the shared vehicle, is transmitted from the first client device to the server device. The server device verifies whether at least one of the vehicle inspection, vehicle insurance, and lease agreement for the shared vehicle is valid. If it is confirmed that at least one of the aforementioned vehicle inspection, vehicle insurance, and lease agreement is invalid, a notification is sent from the server device to a third-party client device used by the administrator of the shared vehicle. The method for managing a shared vehicle according to claim 1.

4. The first client device and the second client device are identical. The method for managing a shared vehicle according to claim 1.

5. The aforementioned authentication information is used to operate a key device located inside the shared vehicle in order to lock and unlock the shared vehicle. The method for managing a shared vehicle according to claim 1.

6. At the first point in time, an interface receives first identification information, including information that identifies the driver, from the first client device, A processor that, if it is confirmed that the driver's license is valid at the first time point based on the first identification information, allows the driver to make a reservation for the shared vehicle, and enables the download of authentication information by a second client device to make the shared vehicle available for use if it is confirmed that the driver's license is valid at a second time point later than the first time point. It is equipped with Server device.

7. The interface receives second identification information, including updated driver's license information, from the first client device or the second client device at a third time point after the first time point. The aforementioned processor, The authentication information is updated based on the second identification information, and the download by the second client device is enabled. The server device according to claim 6.

8. The interface receives third identification information, including information identifying the shared vehicle, from the first client device. The processor, if it is determined that at least one of the vehicle inspection, vehicle insurance, and lease agreement for the shared vehicle is invalid, sends a notification to a third-party client device used by the administrator of the shared vehicle. The server device according to claim 6 or 7.

9. A computer program that can be executed by a processor installed in a server device, By being executed, the server device will At the first point in time, the first client device receives first identification information, including information that identifies the driver. If, based on the first identification information, it is confirmed that the driver's license is valid at the first time point, the reservation of the shared vehicle by the driver is completed, and if, at a second time point later than the first time point, it is confirmed that the driver's license is valid, the second client device is enabled to download authentication information to make the shared vehicle available for use. Computer program.

10. By being executed, the server device will At a third time point, which is after the first time point, the second identification information, including updated driver's license information, is received from the first client device or the second client device. The authentication information is updated based on the second identification information, and the download by the second client device is enabled. The computer program according to claim 9.

11. By being executed, the server device will Third identification information, including information identifying the shared vehicle, is received from the first client device. If it is confirmed that at least one of the vehicle inspection, vehicle insurance, and lease agreement for a shared vehicle identified by the aforementioned third identification information is invalid, a notification is sent to a third-party client device used by the administrator of the shared vehicle. The computer program according to claim 9 or 10.

Images