Management system and management program

Abstract

To provide a management system and management program capable of controlling rental vehicles.SOLUTION: A management system 100 for managing vehicles 1 lent to users for use, the electric vehicles 1 traveling using charged electric power, comprises a control processing part 431, when control input information representing a control content for controlling a vehicle 1 is input in a terminal device 3 used by a user using the vehicle 1, causing the vehicle 1 to execute control processing of controlling the control content represented by the control input information. The management system 100 includes a terminal device 3 and a server device 4 capable of communicating with the vehicle 1 side and the terminal device 3, the server device 4 includes a control processing part 431, and the control processing part 431 executes processing of transmitting server-side control information for causing the vehicle 1 to execute the control of the control content represented by the control input information, to the vehicle 1 side as the control processing.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a management system and a management program.

Background Art

[0002] Conventionally, an electric vehicle that runs using the power charged in a mounted battery has been known (for example, see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, a service has been proposed in which an electric vehicle is lent to a user for use, and in this service, a technology for controlling an electric vehicle has been demanded.

[0005] The present invention has been made in view of the above facts, and an object thereof is to provide a management system and a management program capable of controlling a rental vehicle.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the management system described in claim 1 is a management system for managing a rental vehicle that is lent to a user for use, and is an electric rental vehicle that runs using charged electricity, comprising: control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using the rental vehicle; acquisition means for acquiring management information for managing the rental vehicle; and management means for performing return-related management processing for managing the return of the rental vehicle to a predetermined return location based on the management information acquired by the acquisition means, wherein a charging device for charging the rental vehicle is provided at the predetermined return location, and the acquisition means The management means acquires power-related information indicating whether the rental vehicle's power is on or off, and charging status information indicating whether the rental vehicle is being charged, as management information. The management means performs the return-related management processing based on the power-related information and charging status information acquired by the acquisition means. When information indicating control content for turning on the rental vehicle's power is input to the user terminal as control input information, and the rental vehicle's power is turned on, the acquisition means acquires information indicating that the rental vehicle's power is on as power-related information. When information indicating control content for turning off the rental vehicle's power is input to the user terminal as control input information, and the rental vehicle's power is turned off, the acquisition means acquires information indicating that the rental vehicle's power is off as power-related information.

[0007] The management system according to claim 2 is the management system according to claim 1, wherein the management means performs a charging-related determination to determine whether the rental vehicle is charged based on the charging status information acquired by the acquisition means, a power-related determination to determine whether the power to the rental vehicle is off based on the power-related information acquired by the acquisition means, and a permission-related determination to determine whether to permit the return of the rental vehicle based on the determination result of the charging-related determination and the determination result of the power-related determination, and the management means performs the return-related management processing based on the determination result of the permission-related determination, and if the management means determines in the permission-related determination that the return of the rental vehicle should not be permitted due to the determination result of the charging-related determination, it outputs information regarding charging the rental vehicle via the user terminal as information indicating the user actions that need to be taken in order to permit the return of the rental vehicle.

[0008] The management program described in claim 3 is a management program for managing an electric rental vehicle that is lent to a user for use and runs using charged electricity, wherein the computer functions as: a control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using the rental vehicle; an acquisition means for acquiring management information for managing the rental vehicle; and a management means for performing return-related management processing for managing the return of the rental vehicle to a predetermined return location based on the management information acquired by the acquisition means, wherein a charging device for charging the rental vehicle is provided at the predetermined return location, and the acquisition means is the The management means acquires power-related information indicating whether the rental vehicle's power is on or off, and charging status information indicating whether the rental vehicle is being charged, as management information. The management means performs the return-related management processing based on the power-related information and charging status information acquired by the acquisition means. When information indicating control content for turning on the rental vehicle's power is input to the user terminal as control input information, and the rental vehicle's power is turned on, the acquisition means acquires information indicating that the rental vehicle's power is on as power-related information. When information indicating control content for turning off the rental vehicle's power is input to the user terminal as control input information, and the rental vehicle's power is turned off, the acquisition means acquires information indicating that the rental vehicle's power is off as power-related information. [Effects of the Invention]

[0009] According to the management system described in claim 1 and the management program described in claim 3, when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using a rental vehicle, control processing is performed to carry out the control content indicated by the control input information on the rental vehicle, thereby making it possible to control the rental vehicle via the user terminal, for example.

Brief Description of Drawings

[0010] [Figure 1] This is a block diagram conceptually showing the management system according to this embodiment. [Figure 2] This is a block diagram conceptually showing a vehicle. [Figure 3] This is a block diagram conceptually showing an in-vehicle device. [Figure 4] This is a block diagram conceptually showing a terminal device. [Figure 5] This is a diagram for explaining a station. [Figure 6] This is a diagram exemplifying user information. [Figure 7] This is a diagram exemplifying vehicle information. [Figure 8] This is a diagram exemplifying station information. [Figure 9] This is a diagram exemplifying usage information. [Figure 10] This is a diagram exemplifying usage reservation information. [Figure 11] This is a diagram exemplifying return reservation information. [Figure 12] This is a flowchart of vehicle control processing. [Figure 13] This is a flowchart of return processing. [Figure 14] This is a flowchart of normal return screen display processing. [Figure 15] This is an example display of a normal return screen. [Figure 16] This is an example display of a normal return screen. [Figure 17] This is an example display of a normal return screen. [Figure 18] This is an explanatory diagram regarding guidance information. [Figure 19] This is a flowchart of non-charging return screen display processing. [Figure 20] This is an example display of a non-charging return screen. [Figure 21] This is an example display of a non-charging return screen. [Figure 22] It is an explanatory diagram regarding guidance information.

Embodiments for Carrying Out the Invention

[0011] Hereinafter, referring to the attached drawings, embodiments of the management system and management program according to this invention will be described in detail. First, [I] the basic concept of the embodiment will be described, then [II] the specific content of the embodiment will be described, and finally, [III] modifications to the embodiment will be described. However, the present invention is not limited by the embodiments.

[0012] [I] Basic Concept of the Embodiment First, the basic concept of the embodiment will be described. The embodiment relates to a management system and a management program. The management system according to the present invention is a system for managing rental vehicles, and includes, for example, a system for managing the return of rental vehicles and a system for managing the control of rental vehicles.

[0013] A "rental vehicle" is a vehicle lent to a user for use, and is an electric vehicle that runs using the charged electric power. A "rental vehicle" is, for example, a concept indicating a vehicle that runs using the electric power charged in a battery as the main power source, and as an example, includes concepts such as electric two-wheel vehicles, electric three-wheel vehicles, electric four-wheel vehicles, and electric assist bicycles.

[0014] Then, in the following embodiments, the case where the "rental vehicle" is an electric two-wheel vehicle will be described.

[0015] [II] Specific Content of the Embodiment <​​​​​​First, the configuration of the management system according to this embodiment will be described. Figure 1 is a block diagram that functionally illustrates the management system according to this embodiment, Figure 2 is a block diagram that functionally illustrates the vehicle, Figure 3 is a block diagram that functionally illustrates the in-vehicle equipment, Figure 4 is a block diagram that functionally illustrates the terminal equipment, and Figure 5 is a diagram for explaining the station.

[0017] Note that the number of vehicles 1, on-board devices 2, and terminal devices 2 in Figure 1 is arbitrary, and many are provided, but here only some of the components are specifically illustrated and explained as representative. Furthermore, unless otherwise specified, each component of the same type will be described using the symbols shown in Figure 1. Also, Figure 5 is a map of the roads and other areas around Station 91.

[0018] The management system 100 in Figure 1 is a system for managing vehicle 1 and includes, for example, vehicle 1, in-vehicle device 2, terminal device 3, and server device 4.

[0019] (Composition - Vehicles) Vehicle 1 in Figure 1 is a rental vehicle that a rental company lends to a user for use by that user, and is, for example, an electric two-wheeled vehicle. The structure of Vehicle 1 is arbitrary, but for example, a structure that can be folded and stored when not in use may be adopted, or other structures may be adopted.

[0020] The rental and return of Vehicle 1 will be carried out at a station. A "station" is a place where Vehicle 1 is rented out and returned, and is a facility that is set up in many locations, for example, and includes Station 91, which is set up along the road as shown in Figure 5.

[0021] Vehicle 1 can be returned to the same station where it was rented, or to a different station from the one where it was rented. Each station is equipped with a charging device for charging the battery 11 (described later) installed in Vehicle 1, and a predetermined number of charging cables (not shown) for charging the battery 11 of Vehicle 1 are provided by the charging device. In other words, each station can simultaneously charge the same number of Vehicle 1 as the number of charging cables provided. For example, a station equipped with four charging cables can simultaneously charge four Vehicle 1.

[0022] It should also be interpreted that the station in this embodiment corresponds to a "designated return location".

[0023] As shown in Figure 2, Vehicle 1 includes, for example, a battery 11, a motor 12, a communication unit 13, a recording unit 14, and a control unit 15. In reality, Vehicle 1 has various other elements implemented in addition to these, but in this embodiment, we will focus on the elements specifically described (the same applies to the other devices).

[0024] (Configuration - Vehicle - Battery) The battery 11 in Figure 2 is a storage means for storing energy (specifically, electricity) to operate and drive the vehicle 1, and can be constructed using, for example, a lead-acid battery, a nickel-metal hydride battery, or a lithium-ion battery.

[0025] (Configuration - Vehicle - Motor) The motor 12 in Figure 2 is a driving means for driving and moving the vehicle 1. For example, it uses electricity based on energy stored in the battery 11 to rotate the wheels of the vehicle 1, thereby driving the vehicle 1.

[0026] (Configuration - Vehicles - Communications Department) The communication unit 13 in Figure 2 is a communication means for communicating with other devices (for example, the in-vehicle device 2), and can be configured using, for example, a communication circuit that communicates via a wire.

[0027] (Configuration - Vehicle - Recording Unit) The recording unit 14 in Figure 2 is a recording means for recording (i.e., storing) programs and various data necessary for the operation of the vehicle 1. For example, it can be configured using flash memory or a hard disk (not shown) as an external recording device (the same applies to the recording units of other devices).

[0028] (Components - Vehicle - Control Unit) The control unit 15 in Figure 2 is a control means for controlling the vehicle 1, and specifically, it is a computer comprising a CPU, various programs interpreted and executed on the CPU (including basic control programs such as the OS and application programs launched on the OS to realize specific functions), and internal memory such as RAM for storing programs and various data (the control units of other devices are similar).

[0029] (Configuration-In-vehicle equipment) The on-board device 2 in Figure 1 is a device mounted on the vehicle 1 to perform various processes related to the vehicle 1, and for example, one device is provided for each vehicle 1. As a variation, the functions of the on-board device 2 may be incorporated into the vehicle 1.

[0030] As shown in Figure 3, the in-vehicle device 2 includes, for example, a communication unit 21, a current position detection unit 22, a recording unit 23, and a control unit 24.

[0031] (Configuration - In-vehicle equipment - Communication department) The communication unit 21 in Figure 3 is a communication means for communicating with other devices (for example, the vehicle 2 and the server device 4). For example, it is a means for wired communication with the vehicle 2 and wireless communication with the server device 4. The communication unit 21 can be configured using, for example, a communication circuit that communicates via wired and wireless connections. The wireless communication function in the communication unit 21 may be implemented, for example, by a communication circuit that communicates via a so-called LTE (Long Term Evolution) line.

[0032] (Configuration - On-board device - Current position detection unit) The current position detection unit 22 in Figure 3 is a current position detection means for detecting the current position (current location) of the on-board device 2. Since the on-board device 2 is mounted on the vehicle 1, the current position detection unit 22 will detect the current position of the vehicle 1 on which the on-board device 2 is mounted. The current position detection unit 22 has, for example, a GPS-compatible system and is configured to detect the current position (coordinates corresponding to longitude and latitude) of the on-board device 2 (vehicle 1) by a known method.

[0033] (Configuration - In-vehicle device - Recording unit) The recording unit 23 in Figure 3 is a recording means for recording programs and various data necessary for the operation of the in-vehicle device 2. For example, the recording unit 23 records in-vehicle device identification information (hereinafter, "identification information" will also be referred to as "ID") for uniquely identifying the in-vehicle device 2.

[0034] (Configuration - On-board equipment - Control unit) The control unit 24 in Figure 3 is a control means for controlling the in-vehicle device 2.

[0035] (Configuration - Terminal equipment) The terminal device 3 in Figure 1 is a user terminal used by a user of vehicle 1, and is, for example, a smartphone or tablet device carried by the user.

[0036] As shown in Figure 4, the terminal device 3 includes, for example, a communication unit 31, a touchpad 32, a display 33, a recording unit 34, and a control unit 35.

[0037] (Configuration - Terminal Equipment - Communication Unit) The communication unit 31 in Figure 4 is a communication means for communicating with other devices (for example, the server device 4), and can be configured using, for example, a communication circuit that communicates wirelessly.

[0038] (Configuration - Terminal device - Touchpad) The touchpad 32 is an operating means that receives various operation inputs from the user when pressed by the user's finger or the like. The specific configuration of the touchpad 32 is arbitrary, but for example, a known one equipped with an operation position detection means such as a resistive type or a capacitive type can be used.

[0039] (Configuration - Terminal device - Display) The display 33 is a display means for displaying various images. The specific configuration of the display 33 is arbitrary, but for example, a known liquid crystal display or an organic EL display, such as a flat panel display, can be used. In this embodiment, for example, the touch pad 32 and the display 33 are integrally formed as a touch panel.

[0040] (Configuration - Terminal device - Recording unit) The recording unit 34 in Figure 4 is a recording means for recording programs and various data necessary for the operation of the terminal device 3.

[0041] (Configuration - Terminal device - Control unit) The control unit 35 in Figure 4 is a control means for controlling the terminal device 3, and functionally, it includes, for example, an acquisition unit 351 and a management unit 352.

[0042] The acquisition unit 351 is an acquisition means for acquiring management information for managing rental vehicles. The management unit 352 is a management means that performs return-related management processing to manage the return of rental vehicles to a predetermined return location based on the management information acquired by the acquisition means. The processing performed by each part of the control unit 355 will be described later.

[0043] (Configuration - Server Equipment) The server device 4 in Figure 1 includes, for example, a communication unit 41, a recording unit 42, and a control unit 43.

[0044] (Configuration - Server device - Communication unit) The communication unit 41 in Figure 1 is a communication means for communicating with other devices (for example, the in-vehicle device 2 and the terminal device 3), and can be configured using, for example, a wireless communication circuit.

[0045] (Configuration - Server device - Recording unit) The recording unit 42 in Figure 1 is a recording means for recording programs and various data necessary for the operation of the server device 4. As shown in Figure 1, the recording unit 42 includes, for example, a user information database (hereinafter referred to as "DB") 421, a vehicle information DB 422, a station information DB 423, a usage information DB 424, a usage reservation information DB 425, and a return reservation information DB 426.

[0046] (Configuration - Server device - Recording unit - User information DB) The user information DB421 in Figure 1 is a user information storage means for storing user information. Figure 6 is an example of user information. User information refers to information about the user of vehicle 1, and for example, the information of each item in Figure 6 is interconnected.

[0047] ===User ID, User Identification Information=== The information corresponding to the "User ID" item in Figure 6 is the user ID that uniquely identifies the user (e.g., "IDu0001" in Figure 6). The information corresponding to the "User Identification Information" item in Figure 6 is user identification information used to identify the user (e.g., the user's name and gender in Figure 6, e.g., "AAAA, Male,..."). Note that "AAAA" in Figure 6 is for convenience only and represents the name.

[0048] === Example Data === The information at the top of Figure 6 indicates, for example, that the user identified by "IDu0001" is named "AAAA," and that the user is male.

[0049] ===Storage Example=== Note that the method for storing user information shown in Figure 6 is arbitrary; for example, the information may be stored by the user inputting it via terminal device 3.

[0050] (Configuration - Server device - Recording unit - Vehicle information DB) The vehicle information DB422 in Figure 1 is a vehicle information storage means for storing vehicle information. Figure 7 is an example of vehicle information. Vehicle information refers to information about vehicle 1, and for example, the information of each item in Figure 7 is interconnected.

[0051] ===Vehicle ID, Onboard Device ID, Vehicle Identification Information=== The information corresponding to the "Vehicle ID" item in Figure 7 is the vehicle ID used to uniquely identify vehicle 1 (e.g., "IDb0001" in Figure 7). The information corresponding to the "Onboard Device ID" item in Figure 7 is the onboard device ID used to uniquely identify onboard device 2 installed in vehicle 1 (e.g., "IDm0001" in Figure 7). The information corresponding to the "Vehicle Identification Information" item in Figure 7 is the vehicle identification information used to identify vehicle 1 (e.g., the vehicle registration number "Minato-ku nu〇〇" in Figure 7).

[0052] ===Status Information=== The information corresponding to the item "Status Information" in Figure 7 is status information indicating the current state of vehicle 1. This status information is arbitrary, but in this embodiment, we will explain cases where, for example, "Vacant," "Reserved," "On Loan," "Loan Suspended," and "Broken" are used.

[0053] "Vacant" means the vehicle is not reserved and is not in use. "Reserved" means the vehicle is reserved and is not in use. "Rented out" means the vehicle is in use. "Rental suspended" means that rentals have been suspended. "Broken" means the vehicle is broken down.

[0054] ===Current location information=== The information corresponding to the item "Current Location Information" in Figure 7 is the current location information indicating the current position of Vehicle 1 (i.e., the on-board device 2 installed in Vehicle 1) (in Figure 7, this is the coordinates corresponding to longitude and latitude, such as "X1, Y1"). Note that "X1, Y1" is included for explanatory purposes only, and the same applies to other coordinate descriptions.

[0055] ===Power Status Information=== The information corresponding to the item "Power Status Information" in Figure 7 is power status information indicating whether the power to vehicle 1 is on or off. This power status information is arbitrary, but in this embodiment, for example, the case in which "ON" indicating that the power is on and "OFF" indicating that the power is off are used will be described.

[0056] Furthermore, "power on" refers to a state in vehicle 1 where the battery 11 and various elements (for example, the motor 12, or various LEDs, etc.) are electrically connected to each other, and power from the battery 11 is supplied to the various elements. Conversely, "power off" refers to a state in vehicle 1 where the battery 11 and various elements are electrically disconnected from each other, and power from the battery 11 is not supplied to the various elements.

[0057] Furthermore, in this embodiment, the control of switching the power on and off is performed, for example, in the vehicle control process described later, and is performed, for example, by user operation via terminal device 3.

[0058] ===Charging Status Information=== The information corresponding to the item "Charging Status Information" in Figure 7 is charging status information indicating whether the battery 11 installed in the vehicle 1 is being charged or not. This charging status information is arbitrary, but in this embodiment, for example, the case in which "Charging" indicating that it is being charged and "Not Charging" indicating that it is not being charged will be described.

[0059] In this embodiment, the vehicle 1 will be described using an example where the battery 11 installed in the vehicle 1 is charged using a charging cable (not shown) of a charging device provided at the station, as described above.

[0060] For example, suppose that vehicle 1 is provided with a socket into which the plug of the charging cable (the tip of the charging cable, the part that is inserted) is inserted. When the plug of the charging cable is inserted into the socket of vehicle 1, the charging device and vehicle 1 are electrically connected to each other via the charging cable, and power from the charging device is supplied to vehicle 1, and this power charges the battery 11 of vehicle 1. When the plug of the charging cable is unplugged from the socket of vehicle 1, the charging device and vehicle 1 are electrically disconnected from each other, and power from the charging device is not supplied to vehicle 1, so the battery 11 of vehicle 1 is not charged.

[0061] In other words, for example, when the plug of the charging cable is inserted into the socket of vehicle 1, charging of the battery 11 of vehicle 1 begins, and charging of the battery 11 continues until the plug of the charging cable is removed from the socket of vehicle 1. Then, for example, when the plug of the charging cable is removed from the socket of vehicle 1, charging of the battery 11 of vehicle 1 ends.

[0062] With this configuration, "Charging Status Information" = "Charging" in Figure 7 indicates that a charging cable is connected to vehicle 1, while "Charging Status Information" = "Not Charging" indicates that a charging cable is not connected to vehicle 1.

[0063] === Example Data === The information at the top of Figure 7 indicates, for example, that the vehicle 1 identified by "IDb0001" is equipped with the in-vehicle device 2 identified by "IDm0001," and that the vehicle registration number of the vehicle 1 is "Minato-ku Nu〇〇." It also indicates that the current status of the vehicle 1 is "on loan," that the current location of the vehicle 1 corresponds to "X1, Y1," and that the power to the vehicle 1 is on. Furthermore, it indicates that the battery 11 of the vehicle 1 is not charged, meaning that a charging cable is not connected to the vehicle 1.

[0064] ===Storage Example=== Note that the vehicle information storage method shown in Figure 7 is arbitrary; for example, the vehicle ID, onboard device ID, and vehicle identification information are stored by the administrator entering the information. On the other hand, information other than this is stored through the processes described later.

[0065] (Configuration - Server device - Recording unit - Station information DB) The station information DB423 in Figure 1 is a station information storage means for storing station information. Figure 8 is an example of station information. Station information refers to information about a station, and for example, the information of each item in Figure 8 is interconnected.

[0066] ===Station ID, Installation Location Information=== The information corresponding to the "Station ID" item in Figure 8 is the station ID that uniquely identifies the station (in Figure 8, this is "IDs0001" which identifies station 91 in Figure 5). The information corresponding to the "Installation Location Information" item in Figure 8 is the installation location information that indicates the location where the station is installed (in Figure 8, this is the coordinates corresponding to longitude and latitude, such as "X33, Y33").

[0067] ===Information on the number of installed ports and the number of available ports=== The information corresponding to the item "Number of installed ports" in Figure 8 is the number of installed ports, indicating the number of charging cables provided at the station (e.g., "4" in Figure 8). Note that charging cables may also be referred to as "charging ports." The information corresponding to the item "Number of available ports" in Figure 8 is the number of available ports, indicating the number of charging cables provided at the station that are not connected to vehicle 1 and are therefore available (e.g., "1" in Figure 8).

[0068] ===Information on the number of motorcycles available for rent=== The information corresponding to the item "Number of available motorcycles for rent" in Figure 8 is the number of available motorcycles that can be rented out at the station (in Figure 8, it is shown as "XX units," etc.).

[0069] === Example Data === The information at the top of Figure 8 indicates, for example, that Station 91 in Figure 5, identified by "IDs0001," is located at the position corresponding to "X33, Y33," that Station 91 has four charging cables, one of which is free, and that the number of vehicles available for loan at Station 91 is "XX units."

[0070] ===Storage Example=== Note that the method for storing station information shown in Figure 8 is arbitrary; for example, station ID, installation location information, and number of installed ports information can be stored by the administrator by inputting the information.

[0071] Furthermore, regarding the information on the number of available ports, the server device 4 may identify the number of available charging cables based on other information (for example, the current location information and charging status information in Figure 7, and the installation location information and number of installed ports information in Figure 8), and store the information based on the identification result. Alternatively, information indicating available charging cables may be repeatedly transmitted from each station to the server device at regular intervals, and the server device 4 may identify the number of available charging cables based on the transmitted information and store the information based on the identification result.

[0072] Furthermore, information on the number of motorcycles available for rental may be stored in the same manner as the information on the number of available ports mentioned above.

[0073] (Configuration - Server device - Recording unit - Usage information database) The usage information DB424 in Figure 1 is a usage information storage means for storing usage information. Figure 9 is an example of usage information. Usage information refers to information about the user's use of vehicle 1, and for example, the information for each item in Figure 9 is interconnected.

[0074] ===User ID, Vehicle ID=== The information corresponding to the "User ID" item in Figure 9 is the User ID that identifies the user using Vehicle 1. This User ID is stored as "IDu0001," which is the User ID in Figure 6. The information corresponding to the "Vehicle ID" item in Figure 9 is the Vehicle ID that identifies Vehicle 1 being used by the user (i.e., Vehicle 1 that has been lent to the user and is being used by that user). This Vehicle ID is stored as "IDb0001," which is the Vehicle ID in Figure 7.

[0075] ===Information on start and end times of use=== The information corresponding to the "Start Time Information" item in Figure 9 is the start time information, indicating the date and time when the user began using vehicle 1. The information corresponding to the "End Time Information" item in Figure 9 is the start time information, indicating the date and time when the user ended using vehicle 1. For each of these time pieces of information, "March 18th, 9:10 AM" etc. will be stored, and if the use has not yet ended, no information will be stored for the end time information.

[0076] ===Starting Station ID, Returning Station ID=== The information corresponding to the "Start Station ID" item in Figure 9 is the Start Station ID, which identifies the station from which the user began using Vehicle 1 (i.e., the station from which Vehicle 1 was lent to the user). The information corresponding to the "Return Station ID" item in Figure 9 is the Return Station ID, which identifies the station from which the user returned Vehicle 1. For each of these Station IDs, the Station ID "IDs0001" from Figure 8 is stored, and if the vehicle has not yet been returned, no information is stored for the Return Station ID.

[0077] ===Usage time information, distance traveled information=== The information corresponding to the item "Usage Time Information" in Figure 9 is usage time information, which shows the amount of time the user used vehicle 1. The information corresponding to the item "Distance Traveled Information" in Figure 9 is distance traveled information, which shows the distance the user traveled by driving vehicle 1 during use.

[0078] === Example Data === Furthermore, the information at the top of Figure 9 indicates, for example, that the user identified by "IDu0001" used (is using) vehicle 1 identified by "IDb0001," and that the use began at "9:10 AM on March 18th" and that vehicle 1 was rented and used at station 91 in Figure 5, indicated by "IDs0001."

[0079] ===Storage Example=== Note that the method for storing the usage information in Figure 9 is arbitrary and can be stored, for example, by the processes described later (the same applies to the usage reservation information and return reservation information described later).

[0080] (Configuration - Server device - Recording unit - Reservation information DB) The reservation information DB425 in Figure 1 is a reservation information storage means for storing reservation information. Figure 10 is an example of reservation information. Reservation information refers to information regarding the reservation of vehicle 1 for use, and for example, the information of each item in Figure 10 is interconnected.

[0081] ===Reservation User ID, Reservation Vehicle ID==== The information corresponding to the "Reservation User ID" item in Figure 10 is the Reservation User ID, which identifies the user who made the reservation. This Reservation User ID may include the User ID "IDu0001" from Figure 6. The information corresponding to the "Reservation Vehicle ID" item in Figure 10 is the Reservation Vehicle ID, which identifies the vehicle 1 that was reserved. This Reservation Vehicle ID may include the Vehicle ID "IDb0001" from Figure 7.

[0082] ===Reservation Station ID==== The information corresponding to the item "Reservation Station ID" in Figure 10 is the reservation station ID that identifies the station where the reserved vehicle 1 is located. This reservation station ID may include "IDs0001," which is the station ID in Figure 8.

[0083] ===Reservation Time Information==== The information corresponding to the item "Reservation Time Information" in Figure 10 is reservation time information indicating the date and time of the reservation (in Figure 10, it is "March 18th 9:00 AM - March 18th 9:15 AM," etc.).

[0084] === Example Data === Furthermore, the information at the top of Figure 10 indicates, for example, that the user identified by "IDu0001" has reserved vehicle 1, identified by "IDb0001," located at station 91 in Figure 5, identified by "IDs0001," for a 15-minute period from 9:00 AM to 9:15 AM on March 18th.

[0085] (Configuration - Server device - Recording unit - Return reservation information DB) The return reservation information DB426 in Figure 1 is a return reservation information storage means for storing return reservation information. Figure 11 is an example of return reservation information. Return reservation information is information about the reservation of the station to which the vehicle 1 being used will be returned, and for example, the information of each item in Figure 11 is interconnected. In addition, for each piece of information in Figure 11, the same information as the information with the same name in Figure 10 is stored.

[0086] ===Reservation User ID, Reservation Vehicle ID==== The information corresponding to the "Reservation User ID" item in Figure 11 is the Reservation User ID, which identifies the user who made the reservation. The information corresponding to the "Reservation Vehicle ID" item in Figure 11 is the Reservation Vehicle ID, which identifies Vehicle 1, the vehicle to be returned.

[0087] ===Reservation Station ID==== The information corresponding to the item "Reservation Station ID" in Figure 11 is the reservation station ID, which identifies the station to which vehicle 1 is reserved for return.

[0088] ===Reservation Time Information==== The information corresponding to the item "Reservation Time Information" in Figure 11 is reservation time information, which indicates the date and time of the reservation.

[0089] === Example Data === The information at the top of Figure 11 shows, for example, that the user identified by "IDu0001" has reserved station 91 in Figure 5, identified by "IDs0001," for a 15-minute period from 10:00 AM to 10:15 AM on March 18th, as the station to which vehicle 1, identified by "IDb0001," will be returned.

[0090] (Configuration - Server device - Control unit) The control unit 43 in Figure 1 is a control means for controlling the server device 4, and functionally, it includes, for example, a control processing unit 431. The control processing unit 431 is a control processing means that, when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using a rental vehicle, performs control processing to execute the control content indicated by the control input information on the rental vehicle. The processing performed by each part of the control unit 43 will be described later.

[0091] (process) Next, the vehicle-side information storage process, usage reservation process, usage start process, vehicle control process, return reservation process, and return process executed by the management system 100 according to this embodiment will be described.

[0092] (Processing - Vehicle-side information storage process) First, let's explain the vehicle-side information storage process. The "vehicle-side information storage process" is the process of storing information related to vehicle 1 in the server device 4, for example, the process of storing the current location information, power status information, and charging status information shown in Figure 7.

[0093] The timing of this vehicle-side information storage process is arbitrary; for example, it may be executed repeatedly at regular time intervals, or when a predetermined event occurs (such as an event where the power of vehicle 1 is switched on or off). The regular time interval at which it is repeatedly executed is arbitrary; for example, it may be 15 seconds when the power of vehicle 1 is on, and 1 minute when the power is off.

[0094] In the vehicle-side information storage process, for example, steps 1 to 4 are executed.

[0095] ===Step 1=== First, in the first step, the control unit 24 of the in-vehicle device 2 determines the current position of the vehicle 1, whether the power to the vehicle 1 is on or off, and whether the battery 11 of the vehicle 1 is being charged.

[0096] =Current position= Specifically, the in-vehicle device 2 identifies the current position detected by the current position detection unit 22 (Figure 3) as the current position of the vehicle 1 on which the in-vehicle device 2 is installed.

[0097] =Power On / Off= Furthermore, the in-vehicle device 2 determines whether the power supply of the vehicle 1 is on or off based on the results of a power supply state determination means (for example, a predetermined electrical circuit, etc.) used to determine whether the power supply is on or off.

[0098] =Battery charging= Furthermore, the on-board device 2 determines whether or not the vehicle's battery 11 is being charged. While this determination method is arbitrary, for example, the following method may be used.

[0099] Specifically, a detection circuit may be provided for vehicle 1 to detect whether the plug of the charging cable (not shown) of each station is inserted into the socket of vehicle 1, and a method may be used to determine whether or not the battery 11 of vehicle 1 is being charged based on the detection result of the detection circuit.

[0100] For example, if the detection circuit detects that the charging cable plug is inserted into the socket of vehicle 1, the on-board device 2 determines that the battery 11 of vehicle 1 is being charged. Also, for example, if the detection circuit does not detect that the charging cable plug is inserted into the socket of vehicle 1 (i.e., if the detection circuit detects that the charging cable plug is not inserted into the socket of vehicle 1), the on-board device 2 determines that the battery 11 of vehicle 1 is not being charged.

[0101] In this embodiment, as described above, the operation involves charging the battery 11 of vehicle 1 using a charging cable. Therefore, in the first step, "identifying that the battery 11 of vehicle 1 is being charged" is synonymous with "identifying that a charging cable is connected to vehicle 1," and "identifying that the battery 11 of vehicle 1 is not being charged" is synonymous with "identifying that a charging cable is not connected to vehicle 1."

[0102] Alternatively, as a variation, other methods may be used to determine whether or not the battery is being charged. For example, a method may be used to determine whether or not the battery is being charged based on a change in the voltage of the battery 11 (for example, an increase in voltage). Or, for example, a method may be used to determine whether or not the battery is being charged based on whether or not current is supplied to the battery 11. Or, a method may be used to determine whether or not the battery is being charged based on whether or not current is being output from the charging device.

[0103] ===Step 2=== Next, in the second step, the control unit 24 of the in-vehicle device 2 transmits information indicating each identification result from the first step to the server device 4. Specifically, the in-vehicle device 2 obtains the in-vehicle device ID from its own recording unit 23 (Figure 3), correlates the obtained in-vehicle device ID with the information indicating each identification result from the first step, and transmits it to the server device 4.

[0104] Here, we will illustrate and explain a case where, for example, in the first step, the current position is identified as "X1, Y1", the power of vehicle 1 is identified as being on, it is identified as not being charged, and "IDm0001" is stored as the onboard device ID of onboard device 2. In this case, in the second step, onboard device 2 associates the information "X1, Y1" (coordinate information), "ON" (information indicating that the power is on), "Not charged" (information indicating that it is not being charged), and "IDm0001" with each other and transmits them to server device 4.

[0105] ===Step 3=== Next, in the third step, the control unit 43 of the server device 4 receives the information transmitted from the in-vehicle device 2.

[0106] Here, for example, "X1,Y1", "ON", "Not charging", and "IDm0001" are received.

[0107] ===Step 4=== Next, in the fourth step, the control unit 43 of the server device 4 stores the current location information, power status information, and charging status information shown in Figure 7, based on the information received in the third step. Specifically, it obtains the in-vehicle device ID from the information received in the third step, and stores the information indicating the corresponding identification result from the first step among the information received in the third step as the current location information, power status information, and charging status information of the vehicle information where the same information as the obtained in-vehicle device ID is stored as the in-vehicle device ID in Figure 7.

[0108] Here, for example, "IDm0001" is obtained from "X1,Y1", "ON", "Not charging", and "IDm0001" received in the third step, and "X1,Y1", "ON", and "Not charging" are stored as the current location information, power status information, and charging status information of the vehicle information shown at the top of Figure 7, where the obtained "IDm0001" is stored as the in-vehicle device ID.

[0109] In practice, as mentioned above, the vehicle-side information storage process is executed repeatedly, so steps 1 through 4 are also executed repeatedly. In step 4, the information is always updated with the latest information, and the latest information transmitted from each in-vehicle device 2 is stored.

[0110] Furthermore, while previous information other than the latest information transmitted from the in-vehicle device 2 to the server device 4 may be deleted, in this embodiment, it is stored in the server device 4's (not shown) history information DB for a predetermined period (for example, one week to one month). Note that the history information DB may also store the latest information. This concludes the explanation of the vehicle information storage process.

[0111] (Processing - Reservation processing) Next, we will explain the reservation process. The "reservation process" is the process of reserving vehicle 1 for use, and is, for example, the process of storing the reservation information in Figure 10 and the status information in Figure 7.

[0112] The timing of this reservation process is arbitrary and is executed, for example, when a user performs a predetermined operation via the touchpad 32 of their terminal device 3 (the same applies to the processes described later). Here, we will explain, for example, the case where a user logs in by entering their user ID, "IDu0001", into the terminal device 3 via the touchpad 32 (the same applies to the processes described later).

[0113] The reservation process involves executing steps 1 through 4.

[0114] ===Step 1=== First, in the first step, the control unit 35 of the terminal device 3 acquires information about the vehicle 1 to be reserved.

[0115] Specifically, the server device 4 stores information indicating the vehicles 1 available for reservation and the stations where those vehicles 1 are located. The terminal device 3 can display a reservation screen on the display 33 showing the vehicles 1 available for reservation at each station, based on the information stored in the server device 4. The information stored in the server here is arbitrary and may be the information in the aforementioned storage database, or other information.

[0116] Then, when the user selects the station where the vehicle 1 to be reserved is located and the vehicle 1 to be reserved on the reservation screen of the terminal device 3, and inputs information indicating the selected station and vehicle 1 via the touchpad 32, the terminal device 3 obtains the station ID and vehicle ID corresponding to the input information, and also obtains the user ID entered during login.

[0117] In this case, terminal device 3 records and retains the vehicle ID from the acquired information as reservation information in its recording unit 34 for a certain period of time (for example, 15 minutes). "Reservation information" refers to information indicating the vehicle 1 that the user wishes to reserve for use, and includes, for example, the vehicle ID.

[0118] Here, for example, if a user inputs information indicating the nearest station, Station 91 (Figure 5), and the vehicle 1 located at Station 91, the terminal device 3 obtains "Station ID" = "IDs0001" and "Vehicle ID" = "IDb0001," as well as "User ID" = "IDu0001" entered during login. In this case, the terminal device 3 records and retains "Vehicle ID" = "IDb0001" as reservation information in its own recording unit 34 for a certain period of time.

[0119] ===Step 2=== Next, in the second step, the control unit 35 of the terminal device 3 transmits each piece of information acquired in the first step. Specifically, the terminal device 3 correlates each piece of information acquired in the first step and transmits it to the server device 4.

[0120] Here, for example, terminal device 3 associates "Station ID" = "IDs0001", "Vehicle ID" = "IDb0001", and "User ID" = "IDu0001" with each other and sends them to server device 4.

[0121] ===Step 3=== Next, in the third step, the control unit 43 of the server device 4 receives the information transmitted from the terminal device 3.

[0122] Here, for example, "Station ID" = "IDs0001", "Vehicle ID" = "IDb0001", and "User ID" = "IDu0001" are received.

[0123] ===Step 4=== Next, in the fourth step, the control unit 43 of the server device 4 stores the information of the reservation information in Figure 10 and the status information in Figure 7, based on the information received in the third step.

[0124] Specifically, for each piece of information in the reservation information shown in Figure 10, the User ID, Vehicle ID, and Station ID received in step 3 are stored as the Reservation User ID, Reservation Vehicle ID, and Reservation Station ID in Figure 10. In addition, information indicating the time from the current date and time up to 15 minutes later is stored as reservation time information. Here, for example, the information shown at the top of Figure 10 is stored.

[0125] Specifically, regarding the status information in Figure 7, the vehicle ID is obtained from the information received in step 3, and the same information as the obtained vehicle ID is stored as the status information for the vehicle information in Figure 7, where "Reserved" is stored. Here, for example, "Reserved" is stored as the status information in the top row of Figure 7. Note that, regarding this status information, before the usage reservation process, vehicle 1 was neither reserved nor in use, and "Vacant" was stored, so here it is updated from "Vacant" to "Reserved". This concludes the explanation of the usage reservation process.

[0126] (Processing - Start of Use Process) Next, the process for starting use will be explained. The "process for starting use" is the process for starting the use of vehicle 1. Specifically, it is the process that is executed after the use reservation process is completed, and is, for example, the process for storing some of the usage information in Figure 9 and the status information in Figure 7.

[0127] Here, we will explain using an example where a user who has reserved vehicle 1 travels to the station where vehicle 1 is located, and the usage start process is initiated near vehicle 1 at that station.

[0128] The initial setup process involves executing steps 1 through 4.

[0129] ===Step 1=== First, in the first step, the control unit 35 of the terminal device 3 acquires information about the vehicle 1 to be used.

[0130] Specifically, the user performs an operation to start using the reserved vehicle 1 via the touchpad 32 of their terminal device 3 (for example, by tapping the "unlock button" to start using the vehicle). In this case, the control unit 35 of the terminal device 3 obtains the vehicle ID recorded (held) in the recording unit 34 as reservation information, and also obtains the user ID entered during login.

[0131] Here, for example, if a user taps the "unlock button" to start using the vehicle within a certain time after entering vehicle 1, etc. in the aforementioned reservation process (i.e., within the time the vehicle ID is recorded as reservation information), terminal device 3 retrieves the "vehicle ID" = "IDb0001" recorded (held) in the recording unit 34 as reservation information, and also retrieves the "user ID" = "IDu0001" entered during login.

[0132] ===Step 2=== Next, in the second step, the control unit 35 of the terminal device 3 transmits the vehicle ID, etc. Specifically, the terminal device 3 associates each piece of information acquired in the first step with each other and transmits it to the server device 4.

[0133] Here, for example, terminal device 3 associates "Vehicle ID" = "IDb0001" and "User ID" = "IDu0001" with each other and sends them to server device 4.

[0134] ===Step 3=== Next, in the third step, the control unit 43 of the server device 4 receives the information transmitted from the terminal device 3.

[0135] Here, for example, "Vehicle ID" = "IDb0001" and "User ID" = "IDu0001" are received.

[0136] ===Step 3=== Next, in the third step, the control unit 43 of the server device 4 receives the information transmitted from the terminal device 3.

[0137] ===Step 4=== Next, in the fourth step, the control unit 43 of the server device 4 stores some of the usage information shown in Figure 9 and the status information shown in Figure 7, based on the information received in the third step.

[0138] Specifically, some of the information in the usage information shown in Figure 9 is stored as the User ID and Vehicle ID received in the third step, and the information indicating the current date and time is stored as the usage start time information in Figure 9. In addition, the station ID stored as the reservation station ID in Figure 10 during the aforementioned reservation process is identified, and the identified station ID is stored as the start station ID in Figure 9. Here, for example, the information shown at the top of Figure 9 is stored.

[0139] Specifically, regarding the status information in Figure 7, the vehicle ID is obtained from the information received in step 3, and the same information as the obtained vehicle ID is stored as the status information for the vehicle information in Figure 7, where "On Loan" is stored. Here, for example, "On Loan" is stored as the status information in the top row of Figure 7. Note that this status information was previously stored as "Reserved" due to the aforementioned usage reservation process, so here it is updated from "Reserved" to "On Loan". This concludes the explanation of the usage start process.

[0140] (Processing - Vehicle control processing) Next, we will explain the vehicle control process. Figure 12 is a flowchart of the vehicle control process (in the following explanations of each process, steps will be abbreviated as "S"). The "vehicle control process" is, in general terms, the process for controlling vehicle 1, such as turning the power of vehicle 1 on or off.

[0141] Here, for example, each step of the vehicle control process will be explained using an example of turning on the power, and after the completion of each step, an example of turning off the power will be explained.

[0142] ===SA1==== In SA1 shown in Figure 12, the control unit 35 of the terminal device 3 transmits the terminal-side control signal to the server device 4.

[0143] A "terminal-side control signal" is a signal transmitted by the terminal device 3 to control the vehicle 1. For example, it is a signal that causes the control content indicated by the control input information to be executed. One example of such a signal is one that includes the control input information and the user ID.

[0144] "Control input information" refers to information indicating the control content for controlling the vehicle. Specifically, it is information input by the user via the terminal device 3. In this embodiment, for example, it is information indicating the control content for turning on the power of vehicle 1 or the control content for turning off the power of vehicle 1. The control input information indicating the control content for turning on the power of vehicle 1 will be referred to as "on control input information," and the control input information indicating the control content for turning off the power of vehicle 1 will be referred to as "off control input information."

[0145] Specifically regarding the processing of SA1, when a user taps a control button (for example, an "on button" to turn on the power, or an "off button" to turn off the power) to control the vehicle 1 they are using via the touchpad 32 of their terminal device 3, control input information indicating the control content corresponding to the operated control button is input to the terminal device 3.

[0146] The control unit 35 of the terminal device 3 then acquires the input control input information and the user ID entered during login, generates a terminal-side control signal including the acquired control input information and user ID, and sends it to the server device 4.

[0147] Here, for example, if a user taps the "on button" on their terminal device 3, on control input information is input to terminal device 3. Terminal device 3 then retrieves the input on control input information and the "user ID" = "IDu0001" entered during login, and then generates a terminal-side control signal including the on control input information and "user ID" = "IDu0001" and sends it to server device 4.

[0148] ===SA2==== Meanwhile, in SA2 in Figure 12, the control processing unit 431 of the server device 4 receives terminal-side control signals from the terminal device 3. Here, for example, it receives terminal-side control signals that include ON control input information and "User ID" = "IDu0001".

[0149] ===SA3==== In SA3 in Figure 12, the control processing unit 431 of the server device 4 identifies the on-board device 2 installed in the vehicle 1 which is the object to be controlled.

[0150] Specifically, by referring to the usage information in Figure 9 and the vehicle information in Figure 7, SA2 identifies the vehicle 1 currently being used by the user indicated by the user ID included in the terminal-side control signal received by SA2 as the control target, and then identifies the in-vehicle device 2 installed in the identified vehicle 1.

[0151] In detail, first, the user ID included in the terminal-side control signal received by SA2 is obtained, and by referring to the usage information in Figure 9, vehicle 1 indicated by the vehicle ID that is associated with the user ID that stores the same information as the obtained user ID, and is also associated with "Status Information" = "On Loan" in the vehicle information in Figure 7, is identified as the vehicle 1 to be controlled.

[0152] As a variation, by referring to the usage information in Figure 9, one may identify Vehicle 1 as the vehicle to be controlled if it is associated with a user ID that stores the same information as the acquired user ID mentioned above, and if the associated vehicle ID does not store any usage end time information.

[0153] Next, referring to the vehicle information in Figure 7, the on-board device ID associated with the vehicle ID representing the previously identified vehicle 1 is identified, and the on-board device 2 indicated by the identified on-board device ID is identified as the on-board device 2 installed in the vehicle 1 to be controlled.

[0154] Here, for example, the "User ID" = "IDu0001" included in the terminal-side control signal received by SA2 is obtained, and by referring to the usage information in Figure 9, the vehicle 1 indicated by the "Vehicle ID" = "IDb0001", which is associated with the user ID that stores the same information as the obtained User ID and is also associated with "Status Information" = "On Loan" in the vehicle information in Figure 7, is identified as the vehicle 1 to be controlled. Next, by referring to the vehicle information in Figure 7, the "Onboard Device ID" = "IDm0001" associated with the identified vehicle 1 is identified, and the onboard device 2 indicated by the identified "IDm0001" is identified as the onboard device 2 installed in the vehicle 1 to be controlled.

[0155] ===SA4==== In SA4 in Figure 12, the control processing unit 431 of the server device 4 transmits a server-side control signal to the in-vehicle device 2 identified in SA3.

[0156] "Server-side control signals" are signals transmitted by the server device 4 to control vehicle 1. For example, these are signals that execute the control content indicated by the control input information. One example is a signal that includes the control input information and the on-board device ID. It is also possible to interpret these server-side control signals as corresponding to "server-side control information."

[0157] Specifically, SA4's processing involves acquiring control input information contained in the terminal-side control signal received by SA2, identifying the in-vehicle device ID that indicates the in-vehicle device 2 identified by SA3, generating a server-side control signal including the acquired control information and the identified in-vehicle device ID, and transmitting it to the in-vehicle device 2.

[0158] Here, for example, SA2 acquires the ON control input information contained in the terminal-side control signal received, SA3 identifies the "vehicle device ID" = "IDm0001" which indicates the vehicle device 2 identified, generates a server-side control signal including the acquired ON control information and the identified "vehicle device ID" = "IDm0001", and transmits it to the vehicle device 2.

[0159] Furthermore, in SA2 to SA4 of Figure 12, the processing performed by server device 4 may be interpreted as corresponding to "control processing."

[0160] ===SA5==== Meanwhile, in SA5 in Figure 12, the control unit 24 of the in-vehicle device 2 receives server-side control signals from the server device 4. Here, for example, it receives server-side control signals that include ON control input information and "In-vehicle device ID" = "IDm0001".

[0161] ===SA6==== In SA6 of Figure 12, the control unit 24 of the in-vehicle device 2 determines whether or not to control the vehicle 1. Specifically, it obtains the in-vehicle device ID included in the server-side control signal received in SA5, compares the obtained in-vehicle device ID with the in-vehicle device ID stored in its own recording unit 23, and makes a decision based on the comparison result.

[0162] If the IDs of each in-vehicle device do not match, the system determines that the signal is a server-side control signal to another in-vehicle device 2, and decides not to control vehicle 1 (SA6 NO), and terminates the process. On the other hand, if the IDs of each in-vehicle device do match, the system determines that the signal is a server-side control signal to itself, and decides to control vehicle 1 (SA6 YES), and proceeds to SA7.

[0163] Here, for example, the control unit 24 of the in-vehicle device 2 acquires the "in-vehicle device ID" = "IDm0001" included in the server-side control signal received by SA5, compares the acquired "in-vehicle device ID" = "IDm0001" with the "in-vehicle device ID" = "IDm0001" stored in its own recording unit 23, and since each in-vehicle device ID matches, it determines that it is a server-side control signal directed to itself, and then decides to control vehicle 1.

[0164] ===SA7==== In SA7 of Figure 12, the control unit 24 of the in-vehicle device 2 controls the vehicle 1 on which it is installed. Specifically, it acquires control input information contained in the server-side control signal received in SA5, and performs the control content indicated by the acquired control input information on the vehicle 1 on which it is installed. More specifically, it sends a command to the vehicle 1 to perform the control content indicated by the control input information, and the control unit 15 of the vehicle 1 performs the control content indicated by the control input information based on the command sent from the in-vehicle device 2.

[0165] Here, for example, the SA5 acquires the ON control input information contained in the server-side control signal received, sends a command to the vehicle 1 to perform the control content of "turn on the power of vehicle 1" indicated by the acquired ON control input information, and the control unit 15 of vehicle 1 turns on the power of vehicle 1 based on the command sent from the in-vehicle device 2.

[0166] ===Example of turning off the power=== The process for turning off the power is the same as the process for turning on the power, so only an overview will be provided.

[0167] First, in SA1 shown in Figure 12, when a user taps the "off button" to turn off the power on their terminal device 3, off control input information is input to terminal device 3. Terminal device 3 receives the input off control input information and also receives the "user ID" = "IDu0001" entered during login. Then, it generates a terminal-side control signal including the off control input information and "user ID" = "IDu0001" and sends it to server device 4.

[0168] Then, in the same manner as when turning on the power, SA2 to SA4 in Figure 12 are executed, and in SA5, the in-vehicle device 2 receives server-side control signals, including off-control input information.

[0169] Next, in SA7 following SA6 in Figure 12, the in-vehicle device 2 acquires the off-control input information included in the server-side control signal received in SA5, and sends a command to the vehicle 1 to perform the control content of "turn off the power to vehicle 1" indicated by the acquired off-control input information. The control unit 15 of vehicle 1 then turns off the power to vehicle 1 based on the command sent from the in-vehicle device 2.

[0170] In this way, when vehicle control processing is performed and the power of vehicle 1 is switched on or off, the power status information in Figure 7, which is stored in the repeatedly executed vehicle-side information storage processing described above, is updated from "ON" to "OFF" or vice versa. This concludes the explanation of vehicle control processing.

[0171] (Processing - Return reservation processing) Next, we will explain the return reservation process. The "return reservation process" is the process of reserving a station to which the vehicle 1 being used will be returned, and is, for example, the process of storing each piece of information in the return reservation information shown in Figure 11.

[0172] The return reservation process involves executing steps 1 through 4.

[0173] ===Step 1=== First, in the first step, the control unit 35 of the terminal device 3 acquires information about the station to be reserved.

[0174] Specifically, terminal device 3 is capable of displaying a display screen indicating each station on display 33 based on the station information shown in Figure 8 stored in server device 4.

[0175] Then, when the user selects a station to which they will return vehicle 1 on the display screen and enters information indicating the selected station, terminal device 3 obtains the station ID corresponding to the entered information and also obtains the user ID entered during login.

[0176] Here, for example, if a user using vehicle 1 with "IDb0001" selects station 91 (Figure 5) and enters information indicating that station 91, terminal device 3 obtains the "Station ID" = "IDs0001" corresponding to the entered information, and also obtains the "User ID" = "IDu0001" entered during login.

[0177] ===Step 2=== Next, in the second step, the control unit 35 of the terminal device 3 correlates the information acquired in the first step and transmits it to the server device 4.

[0178] Here, for example, terminal device 3 associates "Station ID" = "IDs0001" and "User ID" = "IDu0001" with each other and sends them to server device 4.

[0179] ===Step 3=== Next, in the third step, the control unit 43 of the server device 4 receives the information transmitted from the terminal device 3.

[0180] Here, for example, "Station ID" = "IDs0001" and "User ID" = "IDu0001" are received.

[0181] ===Step 4=== Next, in the fourth step, the control unit 43 of the server device 4 stores the information of the return reservation information in Figure 11 based on the information received in the third step.

[0182] Specifically, regarding each piece of information in the return reservation information in Figure 11, first, the user ID received in step 3 is obtained, and by referring to the usage information in Figure 9, vehicle 1, indicated by the vehicle ID associated with the user ID that stores the same information as the obtained user ID, and which is associated with "Status Information" = "Currently Rented" in the vehicle information in Figure 7, is identified as vehicle 1 used by the user. Next, the user ID received in step 3, the vehicle ID indicating the identified vehicle 1, and the station ID received in step 3 are stored as the reservation user ID, reservation vehicle ID, and reservation station ID in Figure 11. In addition, information indicating the time from the current date and time to 15 minutes later is stored as reservation time information. Here, for example, the information shown at the top of Figure 11 is stored. This concludes the explanation of the return reservation process.

[0183] (Processing - Return Processing) Next, we will explain the return process. Figure 13 is a flowchart of the return process. The "return process" is, in general terms, the process of returning vehicle 1 to the station, and for example, the process of storing some of the usage information in Figure 9 and the status information in Figure 7.

[0184] Furthermore, the return process is performed by terminal device 3, which communicates with server device 4 and processes the information stored in each DB of the server device 4's recording unit 42 as appropriate. However, any communication, including requests and responses to those requests, can be applied as communication between terminal device 3 and server device 4 to utilize the information stored in server device 4, so a detailed explanation of the processing of the communication itself will be omitted.

[0185] Alternatively, for example, after the return process has started, the terminal device 3 may be configured to download information stored in the server device 4 at regular intervals and temporarily store it in the recording unit 34, and then execute each process based on the stored information.

[0186] Here, we will explain using an example where a user using vehicle 1, indicated by "IDb0001," initiates the return process at station 91 in Figure 5.

[0187] ===SB1==== In SB1 of Figure 13, the control unit 35 of the terminal device 3 determines whether or not there is an available charging cable (i.e., a charging cable not connected to a vehicle) at the nearest station to the vehicle 1 used by the user of the terminal device 3.

[0188] Specifically, first, the user ID entered during login is obtained, and by referring to the usage information in Figure 9, vehicle 1, which is associated with a user ID that stores the same information as the obtained user ID and is associated with "Status Information" = "On Loan" in the vehicle information in Figure 7, is identified as vehicle 1 used by the user. Next, by referring to the current location information in Figure 7 and the installation location information in Figure 8, the nearest station to the identified vehicle 1 (i.e., the station closest in distance from vehicle 1's current location) is identified, and by referring to the available port information in Figure 8, it is determined whether or not there is an available charging cable at the identified station.

[0189] Regarding the determination in detail, if "0" is stored as the available port information, it is determined that there are no available charging cables at the nearest station (SB1 NO), and the process moves to SB4. On the other hand, if information other than "0" is stored as the available port information (i.e., information indicating a number of "1" or more), it is determined that there are available charging cables (SB1 YES), and the process moves to SB2.

[0190] Here, for example, the "User ID" entered during login = "IDu0001" is obtained, and by referring to the usage information in Figure 9, vehicle 1 indicated by "IDb0001," which is associated with the user ID that stores the same information as the obtained "User ID" = "IDu0001" and is also associated with "Status Information" = "On Loan" in the vehicle information in Figure 7, is identified as vehicle 1 being used by the user. Next, by referring to the current location information in Figure 7 and the installation location information in Figure 8, station 91 (Figure 5) is identified as the nearest station to the identified vehicle 1, and by referring to the available port information in Figure 8, it is determined whether or not there is an available charging cable at the identified station.

[0191] Then, in the station information in Figure 8, the "Station ID" for station 91 is "IDs0001", and the "Number of available ports" associated with it is "1", so it is determined that there is an available charging cable.

[0192] ===SB2==== In SB2 in Figure 13, the control unit 35 of the terminal device 3 performs the normal return screen display process. Figure 14 is a flowchart of the normal return screen display process. The "normal return screen display process" is the process for displaying the normal return screen.

[0193] <<<Normal return screen>>> Figure 15 shows an example of the normal return screen. The "normal return screen" is a screen used to return vehicle 1 while its battery 11 is charging (i.e., with the charging cable connected to vehicle 1). Specifically, it is a screen displayed on the display 33 of the terminal device 3, and as shown in Figure 15, it includes, for example, an image display area 51, a first information display area 521, a second information display area 522, a third information display area 523, and a return button 53.

[0194] Image display area 51 is a field where images representing each station are displayed.

[0195] The first information display area 521, the second information display area 522, and the third information display area 523 are fields where guidance information and status information 520 are displayed.

[0196] "Instructional information" refers to information indicating the user's actions necessary to allow the return of vehicle 1, and is a concept that includes information to guide such actions, such as text messages like "Please move to the station."

[0197] As will be explained later, this guidance information will be highlighted as appropriate. For the sake of explanation, if hatching (multiple diagonal lines) is shown in each display field (see Figure 16 below), the guidance information in that field will be highlighted. Conversely, if hatching is not shown in each display field, the guidance information in that field will not be highlighted. "Highlighting" is a concept that indicates making something stand out, and is specific to this purpose. It includes, for example, making the font bolder, changing the font color or background color, etc.

[0198] "Status Information" 520 indicates whether or not the criteria for allowing the item to be returned have been met.

[0199] The return button 53 is a button image that is tapped by the user to return vehicle 1, and is a button that can be activated or deactivated.

[0200] "The return button 53 is enabled" means that the terminal device 3 is able to accept a tap operation of the return button 53 by the user, and "the return button 53 is disabled" means that the terminal device 3 is unable to accept a tap operation of the return button 53 by the user.

[0201] In other words, for example, if the return button 53 is enabled, and the user taps the return button 53 via the touchpad 32, information indicating that the return button 53 has been tapped is input to the terminal device 3, and the processing that is executed when the return button 53 is tapped is performed.

[0202] On the other hand, for example, if the return button 53 is disabled and the user taps the return button 53 via the touchpad 32, no information indicating that the return button 53 has been tapped will be input to the terminal device 3, and therefore the process that would normally be executed when the return button 53 is tapped will not be performed.

[0203] For the sake of clarity, if hatching is shown on the return button 53, it indicates that it is enabled; if hatching is not shown, it indicates that it is disabled.

[0204] ===SC1==== In SC1 of Figure 14, the acquisition unit 351 of the terminal device 3 acquires management information.

[0205] "Management information" refers to information used to manage vehicle 1, specifically information used to manage the return of vehicle 1, and is a concept that includes, for example, connection-related information, power-related information, and current location information.

[0206] "Connection-related information" refers to information indicating whether or not a charging cable is connected to the rental vehicle. In this embodiment, as mentioned above, the charging status information in Figure 7 indicates that "Charging" means a charging cable is connected to vehicle 1, and "Not charging" means that a charging cable is not connected to vehicle 1. Therefore, the charging status information corresponds to the "connection-related information".

[0207] "Power-related information" refers to information indicating whether the rental vehicle's power is on or off. In this embodiment, regarding the power status information in Figure 7, "ON" indicates that the power of vehicle 1 is on, and "OFF" indicates that the power of vehicle 1 is off. Therefore, the power status information corresponds to "power-related information".

[0208] "Current location information" refers to information indicating the current location of the rental vehicle, and in this embodiment, it corresponds to the current location information shown in Figure 7.

[0209] Specifically, regarding the processing of SC1, in the same manner as in the case of SB1 in Figure 1, the vehicle 1 being used by the user of terminal device 3 is identified, and by referring to the vehicle information in Figure 7, the current location information, power status information, and charging status information associated with the vehicle ID representing the identified vehicle 1 are obtained as management information.

[0210] Here, for example, vehicle 1, indicated by "IDb0001," is identified as the vehicle 1 being used by the user. Referring to the vehicle information in Figure 7, the "current location information" = "X33,Y33" (not shown in Figure 7, but coordinates indicating the same location as station 91 in Figure 5), "power status information" = "ON," and "charging status information" = "not charging" associated with the identified vehicle 1, "vehicle ID" = "IDb0001," are obtained as management information.

[0211] ===SC2==== In SC2 of Figure 14, the management unit 352 of the terminal device 3 determines whether or not to permit the return of vehicle 1 based on the management information acquired in SC1.

[0212] Specifically, the criteria for determining whether to allow the return of vehicle 1 are as follows: the current location of vehicle 1 coincides with the station's installation location (hereinafter, "First Criterion"), the power to vehicle 1 is off (hereinafter, "Second Criterion"), and a charging cable is connected to vehicle 1 (hereinafter, "Third Criterion"). Based on these criteria, a decision is made, and for example, the following first to fourth processes are performed.

[0213] =First Process= First, in the first process, the management unit 352 refers to the station information in Figure 8 and determines whether there is station information that stores installation location information indicating the same location as the current location information obtained by SC1 (i.e., information indicating a station installed at a location corresponding to the current location of vehicle 1 being used by the user). If it determines that such information exists, it determines that the current location of vehicle 1 matches the installation location of the station (the result of the first process is "YES"). On the other hand, if it determines that such information does not exist, it determines that the current location of vehicle 1 does not match the installation location of the station (the result of the first process is "NO").

[0214] Furthermore, regarding the determination of a match in location, the system may consider the size of the station or the accuracy of the current location detection to determine that the locations match even if they are slightly off. In other words, even if there is a station that stores installation location information indicating a location slightly away from the location indicated by the current location information acquired by SC1 (i.e., a location within a predetermined distance), the system may be configured to determine that the current location of vehicle 1 matches the installation location of the station. Additionally, when using a GPS system for location detection, considering that the reception status of the GPS signal depends on whether the station has a roof or the surrounding environment of the station, and that the location detection accuracy depends on these factors, a threshold (e.g., 200m, 250m, etc.) may be set for each station. If the distance between the location of vehicle 1 and the location of the station is within the threshold, the system may be configured to determine that they match, and if the distance is longer than the threshold, the system may be configured to determine that they do not match.

[0215] =Second Process= Next, in the second process, the management unit 352 determines that the power to vehicle 1 is off if the power status information acquired by SC1 is "OFF" (the result of the second process is "YES"), while determining that the power to vehicle 1 is not off if the power status information acquired by SC1 is "ON" (the result of the second process is "NO").

[0216] =Third Process= Next, in the third process, the management unit 352 determines that if the charging status information acquired by SC1 is "charging", a charging cable is connected to vehicle 1 (the determination result of the third process is "YES"). On the other hand, if the charging status information acquired by SC1 is "not charging", the management unit 352 determines that a charging cable is not connected to vehicle 1 (the determination result of the third process is "NO").

[0217] =Fourth Process= Next, in the fourth process, if the judgment result in any of the judgments in the first to third processes is "NO", then the first to third judgment criteria mentioned above will not be met, and the management unit 352 will decide not to permit the return of vehicle 1 (SC2 NO), and proceed to SC4. On the other hand, if the judgment results in all of the judgments in the first to third processes are "YES", then the judgment criteria including the first to third judgment criteria mentioned above will be met, and the management unit 352 will decide to permit the return of vehicle 1 (SC2 YES), and proceed to SC3.

[0218] Here, for example, in SC1, "current location information" = "X33, Y33", "power status information" = "ON", and "charging status information" = "not charging" are obtained. Therefore, the result of the first process is "YES", and the results of the second and third processes are "NO", so it is determined that the return of vehicle 1 is not permitted.

[0219] ===SC3==== In SC3 of Figure 14, the management unit 352 of terminal device 3 displays the normal return screen with the return button 53 activated.

[0220] Specifically, as shown in Figure 15, the management unit 352 generates a normal return screen and displays it on the display 33. In other words, in this case, the management unit 352 activates the return button 53.

[0221] Then, in the normal return screen shown in Figure 15, if the user taps the return button 53, information indicating that the return button 53 has been tapped is input to the terminal device 3, and the normal return screen display process is returned.

[0222] ===SC4==== On the other hand, in SC4, after SC2 in Figure 14 determines that the return of vehicle 1 is not permitted (SC2 NO), the management unit 352 of terminal device 3 displays the normal return screen with the return button 53 disabled and proceeds to SC2. Figures 16 and 17 show examples of the normal return screen display, and Figure 18 is an explanatory diagram regarding guidance information.

[0223] Specifically, as shown in Figure 16, the management unit 352 generates a normal return screen and displays it on the display 33, in which an image of the station is displayed in the image display area 51, guidance information and status information 520 are displayed in the first information display area 521, the second information display area 522, and the third information display area 523, and a disabled return button 53 is displayed. In other words, in this case, the management unit 352 disables the return button 53.

[0224] =Highlighting of information= Regarding guidance information, the management unit 352, based on the judgment results of SC2's "Judgment of First Processing" to "Judgment of Third Processing," highlights guidance information indicating the user actions necessary to change the judgment result to "YES" for judgment criteria where the result is "NO," as shown in the "Guidance Information" column of Figure 18.

[0225] In detail, SC2 determines that the current location of vehicle 1 does not match the station's installation location, and if the result of the "Determination of First Processing" is "NO", the message "Please move to the station" in the first information display field 521 is highlighted, as illustrated in the "Guidance Information" field corresponding to "Number" = "1" in Figure 18.

[0226] Furthermore, in SC2, if it is determined that the power to vehicle 1 is not off, and the result of the "Determination of the second process" is "NO", the message "Please turn off the power" in the second information display field 522 is highlighted, as illustrated in the "Guidance Information" field corresponding to "Number" = "2" in Figure 18.

[0227] Furthermore, in SC2, if it is determined that the charging cable is not connected to vehicle 1, and the result of the "Determination of the Third Process" is "NO", the message "Please connect the charging cable" in the third information display field 523 is highlighted, as illustrated in the "Information" field corresponding to "Number" = "3" in Figure 18.

[0228] =Status Information= Regarding status information 520, the management unit 352, based on the judgment results of SC2's "Judgment of First Processing" to "Judgment of Third Processing", displays image information indicating that the judgment criteria are met in the status information 520 field where guidance information regarding the judgment criteria for a judgment result of "YES" is displayed, and displays image information indicating that the judgment criteria are not met in the status information 520 field where guidance information regarding the judgment criteria for a judgment result of "NO" is displayed.

[0229] Here, for example, in SC2, if the result of the first process is "YES" and the results of the second and third processes are "NO", the normal return screen is displayed, as shown in Figure 16, in which the guidance information in the second information display field 522 and the third information display field 523 is highlighted.

[0230] After this, SC2 in Figure 14 will be executed again. For example, if the user turns off the power to vehicle 1, the result of the second process will change from "NO" to "YES". In SC4, which will be executed again, the normal return screen will be displayed with the guidance information in the third information display field 523 highlighted, as shown in Figure 17.

[0231] Subsequently, for example, if the user connects a charging cable to vehicle 1, the result of the second process in SC2 in Figure 14 will be "YES," and the results of the first to third processes will all be "YES." Therefore, it is determined that the return of vehicle 1 is permitted (YES in SC2), and the process moves to SC3, where the return button 53 on the normal return screen is activated, as shown in Figure 15.

[0232] ===SB3=== After the normal return screen display process shown in Figure 14 is returned, the management unit 352 of terminal device 3 in SB3 of Figure 13 transmits return-related information to server device 4 and terminates the process. "Return-related information" refers to information indicating that vehicle 1 has been returned and the use of vehicle 1 has ended.

[0233] Specifically, terminal device 3 identifies a station ID indicating the nearest station to vehicle 1 identified by SB1, and after obtaining the user ID entered during login, it transmits the identified station ID, the obtained user ID, and other return-related information to server device 4.

[0234] Meanwhile, the control unit 43 of the server device 4 receives return-related information transmitted from the terminal device 3, and stores some of the usage information shown in Figure 9 and the status information shown in Figure 7 based on the received return-related information.

[0235] Specifically, first, the vehicle 1 being used by the user is identified, similar to SB1. Next, the same information as the user ID and vehicle ID that identify the identified vehicle 1, which are included in the received return-related information mentioned above, is stored as the user ID and vehicle ID in the usage information stored in Figure 9. The usage end time and return station ID are stored as information indicating the current date and time, and the station ID included in the received return-related information mentioned above. In addition, the usage time and travel distance are determined by any method, and the information indicating the determined usage time and travel distance is stored as the usage time information and travel time information in Figure 9. Furthermore, in the vehicle information in Figure 7, "Vacant" is stored as the status information associated with the vehicle ID that identifies the identified vehicle 1 (i.e., the vehicle ID that identifies the vehicle 1 being used by the user). In this case, the status information will be updated from "On Loan" to "Vacant".

[0236] ===SB4=== On the other hand, in SB4, after determining that there are no available charging cables in SB1 in Figure 13, the control unit 35 of the terminal device 3 performs the process of displaying the "no charge return" screen. Figure 19 is a flowchart of the "no charge return" screen display process. The "no charge return" screen display process is the process for displaying the normal return screen.

[0237] <<<Return screen without charging>>> Figure 20 shows an example of the display of the uncharged return screen. The "uncharged return screen" is a screen used to return vehicle 1 when the vehicle's battery 11 is not charged (i.e., when the charging cable is not connected to vehicle 1). Specifically, it is a screen displayed on the display 33 of the terminal device 3, and as shown in Figure 20, it includes, for example, an image display area 61, a first information display area 621, a second information display area 622, a third information display area 623, and a return button 63.

[0238] The intention behind this uncharged return (i.e., returning vehicle 1 with its battery 11 uncharged) is not limited to any specific scenario, but the following is a possible explanation: Even if all the charging cables installed at the station are in use and none are available (for example, if all four charging cables are connected to four other vehicles), the uncharged return method allows for the return of vehicle 1. Furthermore, in such an uncharged return, to prevent the user returning vehicle 1 from disconnecting a charging cable already connected to and used by another vehicle for their own use, the fact that no charging cable is connected to vehicle 1 (i.e., the "third criterion" described later) is defined as one of the criteria for determining whether the return of vehicle 1 is permitted, as explained in SD2 of Figure 19 below.

[0239] Image display area 61 is the area where images representing each station are displayed.

[0240] The first information display column 621, the second information display column 622, and the third information display column 623 are columns where guidance information and status information 620 are displayed.

[0241] The return button 63 is a button image configured in the same manner as the return button 53 in FIG. 15. Specifically, it is a button image tapped by the user to return the vehicle 1, and is a button that can be enabled or disabled.

[0242] ===SD1==== In SD1 of FIG. 19, the acquisition unit 351 of the terminal device 3 acquires management information. Specifically, it performs the same processing as SC1 in FIG. 14, and acquires the current position information, power supply state information, and charging state information in FIG. 7 regarding the vehicle 1 used by the user as management information.

[0243] ===SD2==== In SD2 of FIG. 19, the management unit 352 of the terminal device 3 determines whether to permit the return of the vehicle 1 based on the management information acquired in SD1.

[0244] Specifically, as the criteria for determining to permit the return of the vehicle 1, it is determined that the return is permitted when the current position of the vehicle 1 coincides with the installation position of the station (hereinafter, "first criterion"), and the power supply of the vehicle 1 is off (hereinafter, "second criterion"), and no charging cable is connected to the vehicle 1 (hereinafter, "third criterion"). Based on this criterion, it is determined, and for example, the following first process to fourth process are performed.

[0245] =First Process and Second Process= First, in the first process and the second process, the management unit 352 performs the same processing as the first process and the second process of SC2 in FIG. 14.

[0246] =Third Process= Next, in the third process, the management unit 352 determines that if the charging status information acquired by SD1 is "not charging", then no charging cable is connected to vehicle 1 (the result of the third process is "YES"). On the other hand, if the charging status information acquired by SD1 is "charging", then it determines that a charging cable is not disconnected from vehicle 1 (i.e., a charging cable is connected to vehicle 1) (the result of the third process is "NO").

[0247] =Fourth Process= Next, in the fourth process, if the judgment result in any of the judgments in the first to third processes is "NO", then the first to third judgment criteria mentioned above will not be met, and the management unit 352 will decide not to permit the return of vehicle 1 (SD2 NO), and proceed to SD4. On the other hand, if the judgment results in all of the judgments in the first to third processes are "YES", then the judgment criteria including the first to third judgment criteria mentioned above will be met, and the management unit 352 will decide to permit the return of vehicle 1 (SD2 YES), and proceed to SD3.

[0248] ===SD3==== In SD3 of Figure 19, the management unit 352 of terminal device 3 displays a screen showing the uncharged return with the return button 63 activated.

[0249] Specifically, as shown in Figure 20, the management unit 352 generates a no-charge return screen and displays it on the display 33. This screen displays an image of the station in the image display area 61, status information 620, which is image information indicating that guidance information that is not highlighted and that each judgment criterion corresponding to each piece of guidance information is met, in the first information display area 621, the second information display area 622, and the third information display area 623, and also displays an activated return button 63. In other words, in this case, the management unit 352 activates the return button 63.

[0250] Then, in the uncharged return screen shown in Figure 16, if the user taps the return button 63, information indicating that the return button 63 has been tapped is input to the terminal device 3, and the process of displaying the uncharged return screen is returned.

[0251] ===SD4==== On the other hand, in SD4, after SD2 in Figure 19 determines that the return of vehicle 1 is not permitted (SD2 NO), the management unit 352 of terminal device 3 displays a no-charge return screen with the return button 63 disabled, and then proceeds to SD2. Figure 21 is an example of the no-charge return screen display, and Figure 22 is an explanatory diagram regarding guidance information.

[0252] Specifically, as shown in Figure 21, the management unit 352 generates a no-charge return screen and displays it on the display 33, in which an image of the station is displayed in the image display area 61, guidance information and status information 620 are displayed in the first information display area 621, the second information display area 622, and the third information display area 623, and a disabled return button 63 is displayed. In other words, in this case, the management unit 352 disables the return button 63.

[0253] =Highlighting of information= The guidance information is the same as the SC4 process in Figure 14. Based on the judgment results of SD2's "Judgment of First Process" to "Judgment of Third Process," the management unit 352 highlights guidance information indicating the user actions necessary to change the judgment result to "YES" for the judgment criteria where the result is "NO," as shown in the "Guidance Information" column of Figure 22.

[0254] In detail, SD2 determines that the current location of vehicle 1 does not match the station's installation location, and if the result of the "Determination of First Processing" is "NO", the message "Please move to the station" in the first information display field 621 is highlighted, as illustrated in the "Guidance Information" field corresponding to "Number" = "1" in Figure 22.

[0255] Furthermore, in SD2, if it is determined that the power to vehicle 1 is not turned off, and the result of the "Determination of the second process" is "NO", the message "Please turn off the power" in the second information display field 622 is highlighted, as illustrated in the "Information" field corresponding to "Number" = "2" in Figure 22.

[0256] Furthermore, in SD2, if it is determined that the charging cable is not connected to vehicle 1, and the result of the "Determination of the third process" is "NO", the message "Do not connect the charging cable" in the third information display field 623 is highlighted, as illustrated in the "Information" field corresponding to "Number" = "3" in Figure 22.

[0257] =Status Information= The status information 620 is the same as the processing of SC4 in Figure 14, so the explanation is omitted.

[0258] Here, for example, in SD2, if the judgment result of the ninth process and the judgment result of the third process are "YES" and the judgment of the second process is "NO", a no-charge return screen is displayed, as shown in Figure 21, in which the guidance information in the second information display field 622 is highlighted.

[0259] Subsequently, for example, if the user turns off the power to vehicle 1, the result of the second process in SD2 in Figure 19, which is executed again, will be "YES," and the results of the first to third processes will all be "YES," so it is determined that the return of vehicle 1 is permitted (YES in SD2), and the process moves to SD3, where the return button 53 on the uncharged return screen is activated, as shown in Figure 20.

[0260] ===SB5=== After returning the uncharged return screen shown in Figure 19, the management unit 352 of terminal device 3 in SB5 of Figure 13 transmits return-related information to server device 4 and terminates processing. Specifically, by performing the same processing as in SB3, some of the usage information shown in Figure 9 and the status information shown in Figure 7 are stored. This concludes the explanation of the return process.

[0261] (Interpretation of Terms) It may be interpreted that the processing of SC3 and SC4 in FIG. 14 and the processing of SD3 and SD4 in FIG. 19 correspond to the "Return-related Management Processing".

[0262] The "Return-related Management Processing" is a process for managing the return of rental vehicles to a station which is a predetermined return location. For example, it is a concept including a first process that enables the transmission of information indicating that a rental vehicle has been returned from a user terminal used by a user using the rental vehicle to the administrator side of the rental vehicle (in this embodiment, the server device 4 side), and a second process that disables the transmission of information indicating that a rental vehicle has been returned from the user terminal to the administrator side of the rental vehicle (in this embodiment, the server device 4 side), etc.

[0263] Also, when the return buttons 53 and 63 on the normal return screen (FIG. 15, etc.) and the non-charging return screen (FIG. 20, etc.) are enabled, when these return buttons 53 and 63 are tapped, the normal return screen display process in FIG. 14 and the non-charging return screen display process in FIG. 19 are returned, and a process of transmitting return-related information of SB3 or SB5 in FIG. 13 is performed. On the other hand, when the return buttons 53 and 63 are enabled, the normal return screen display process in FIG. 14 and the non-charging return screen display process in FIG. 19 cannot be returned, so it becomes impossible to perform the process of transmitting return-related information of SB3 or SB5 in FIG. 13. Considering this point, the process of enabling the return buttons 53 and 63 may be interpreted as corresponding to the "first process that enables the transmission of information indicating that a rental vehicle has been returned", and the process of disabling the return buttons 53 and 63 may be interpreted as corresponding to the "second process that disables the transmission of information indicating that a rental vehicle has been returned".

[0264] (Effects of this Embodiment) According to this embodiment, when control input information indicating control content for controlling vehicle 1 is input to a terminal device 3 used by a user of vehicle 1, it becomes possible to control vehicle 1 via the terminal device 3 by performing control processing to execute the control content indicated by the control input information on vehicle 1.

[0265] Furthermore, by controlling the vehicle 1 via the server device 4, it becomes possible to control the vehicle 1 appropriately, for example.

[0266] Furthermore, since the control input information indicates the control content for turning the power of vehicle 1 on or off, it becomes possible to turn the power of vehicle 1 on or off via terminal device 3, for example.

[0267] Furthermore, by performing return-related management processing, it becomes possible to manage the return of, for example, vehicle 1. By performing return-related management processing based on power-related information, for example, vehicle 1 can be returned with the power turned off, thereby preventing misuse after the return and preventing accidents caused by unintended operation of vehicle 1.

[0268] [III] Modifications of the Embodiment While embodiments of the present invention have been described above, the specific configurations and means of the present invention can be arbitrarily modified and improved within the scope of the technical idea of ​​each invention described in the claims. Such modifications will be described below.

[0269] (Regarding the problems to be solved and the effects of the invention) First, the problems that the invention aims to solve and the effects of the invention are not limited to those described above, and may vary depending on the implementation environment and details of the invention's configuration. In some cases, only a portion of the problems described above may be solved, or only a portion of the effects described above may be achieved.

[0270] (Regarding decentralization and integration) Furthermore, the aforementioned electrical components are functional concepts and do not necessarily need to be physically configured as shown in the diagram. In other words, the specific forms of distribution and integration of each part are not limited to those shown in the diagram, and all or part of them can be functionally or physically distributed or integrated in any unit.

[0271] For example, in the return process shown in Figure 13, the server device 4 may perform some or all of the processing on the terminal device 3 side using the information recorded in the server device 4 in response to a request from the terminal device 3, and then transmit the processing results to the terminal device 3 to execute each step in Figure 13.

[0272] (Regarding the decision on whether to allow the return) Furthermore, in the above embodiment, the case in SC2 of Figure 14 where it is determined whether or not to return vehicle 1 based on the three criteria from the first to the third criteria has been described, but the system is not limited to this. For example, the system may be configured to make a decision using only one of these three criteria, or only two criteria. Alternatively, for example, any number of criteria other than the first to the third criteria may be added, and the system may be configured to make a decision based on these added criteria. The SD2 in Figure 19 may be configured in a similar manner.

[0273] (Information about the guide (Part 1)) Furthermore, in the above embodiment, highlighting guidance information (for example, a message such as "Please move to the station" in Figure 15) may be interpreted as corresponding to "outputting information via the user terminal that indicates the user's actions necessary to allow the return of the rental vehicle."

[0274] (Information about the guide (Part 2)) Furthermore, while the above embodiment described cases where guidance information is highlighted or not highlighted, other display modes may be adopted. For example, a display mode of displaying or not displaying information may be adopted. Specifically, instead of not highlighting, the information may be hidden, and instead of highlighting, it may be displayed.

[0275] (Information about the guide (Part 3)) Furthermore, while the above embodiment describes a case where guidance information (for example, a message such as "Please move to the station" in Figure 15) is displayed and output on the display 33 of the terminal device 3, the invention is not limited to this. For example, it may be configured to output audio via the speaker of the terminal device 3.

[0276] (Regarding the standard return screen and the uncharged return screen) Furthermore, the normal return screen (Figure 15, etc.) and the uncharged return screen (Figure 20, etc.) of the above embodiment may be configured to switch to and display the screen intended by the user based on a predetermined operation performed by the user via the touchpad 32.

[0277] (Regarding vehicle control) Furthermore, although the above embodiment describes a case in which the terminal device 3 controls the vehicle 1 via the server device 4, it is not limited to this. For example, it may be configured to control without going through the server device 4. Specifically, the terminal device 3 may directly transmit a terminal-side control signal to the in-vehicle device 2, and the in-vehicle device 2 may be configured to control the vehicle 1 based on the terminal-side control signal.

[0278] (Regarding each database on the server device) Furthermore, the databases (DBs) of the server device 4 described in the above embodiment are illustrative examples, and any other database may be used as long as it can realize the functions described in this embodiment. Also, all or part of the same databases as those of the server device 4 may be provided in the terminal device 3.

[0279] (Other features) Furthermore, in the above embodiment, the terminal device 3 may be configured to acquire the current location information, power status information, and charging status information of the server device 4 shown in Figure 7, and to display the acquired information on the display 33 in any format.

[0280] Furthermore, the power on / off control of vehicle 1 may be configured to be controllable only by the vehicle control process shown in Figure 12, or a power switch may be provided for vehicle 1, and the power may also be controllable by operating the switch.

[0281] Furthermore, when the vehicle 1 is returned by tapping the return button 63 on the uncharged return screen in Figure 20, the system may be configured to charge the user a return fee. Specifically, although optional, for example, when the user taps the return button 63 on the uncharged display screen shown in SB4 in Figure 13, the terminal device 3 may be configured to display a payment screen using the user's pre-registered credit card, and only proceed to SB5 if the user performs an operation on that screen to pay the fee for returning the vehicle 1 without charging. Alternatively, for example, when the user taps the return button 63 on the uncharged display screen shown in SB4 in Figure 13, the system may be configured to automatically charge the aforementioned fee using the user's pre-registered credit card. Note that when the vehicle is returned by tapping the return button 53 on the normal return screen in Figure 17, the above-mentioned fee billing process will not be performed.

[0282] (Regarding the processing of SC2 in Figure 14 (first criterion)) Furthermore, in the above embodiment, we have described a case in SC2 of Figure 14 where the current location of vehicle 1 coincides with the installation location of the station is used as the "first criterion," but the system is not limited to this. For example, the system may be configured to process the case where the current location of the terminal device 3 used by a user who is renting and using vehicle 1 coincides with the installation location of the station as the "first criterion."

[0283] In this configuration, the first processing of SC2 may be configured such that the control unit 35 of the terminal device 3 acquires current location information indicating the detection result of the current location detection unit (means for detecting the current location of the terminal device 3) implemented in the terminal device 3, and performs processing similar to the processing described in the embodiment based on the acquired current location information to determine whether or not the current location of the terminal device 3 matches the installation location of the station.

[0284] Furthermore, the method described in the embodiment and the method described here may be combined to configure the system to process the case where both the current position of vehicle 1 and the current position of terminal device 3 coincide with the installation location of the station as the "first determination criterion".

[0285] Furthermore, the variations described here may also be applied to the "First Criterion" in SD2 of Figure 19.

[0286] (Combination of features) Furthermore, at least some of the features described in the above embodiment and at least some of the features described in the modified example may be arbitrarily combined.

[0287] (Note) The management system described in Appendix 1 is a management system for managing rental vehicles that are lent to users and run on electric power using charged electricity, and comprises control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user of the rental vehicle.

[0288] The management system described in Appendix 2 is the management system described in Appendix 1, wherein the management system comprises the user terminal and a server device that can communicate between the rental vehicle and the user terminal, the server device comprises the control processing means, the user terminal transmits the control input information to the server device when the control input information is input, and when the server device receives the control input information, the control processing means of the server device performs the process of transmitting server-side control information to the rental vehicle side for causing the rental vehicle to perform the control of the control content indicated by the control input information as the control process.

[0289] The management system in Appendix 3 is the management system described in Appendix 1 or 2, in which the control input information is information indicating the control content for turning the power of the rental vehicle on or off.

[0290] The management system described in Appendix 4 comprises, in the management system described in Appendix 1, an acquisition means for acquiring management information for managing the rental vehicle, and a management means for performing return-related management processing for managing the return of the rental vehicle to a predetermined return location based on the management information acquired by the acquisition means. The acquisition means acquires power-related information indicating whether the power of the rental vehicle is on or off as the management information, and the management means performs the return-related management processing based on the power-related information acquired by the acquisition means. When information indicating control content for turning on the power of the rental vehicle is input to the user terminal as the control input information, and the power of the rental vehicle is turned on, the acquisition means acquires information indicating that the power of the rental vehicle is on as the power-related information, and when information indicating control content for turning off the power of the rental vehicle is input to the user terminal as the control input information, and the power of the rental vehicle is turned off, the acquisition means acquires information indicating that the power of the rental vehicle is off as the power-related information.

[0291] The management program in Appendix 5 is a management program for managing rental vehicles that are lent to users for use and are electric vehicles that run using charged electricity, and the management program causes a computer to function as a control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user of the rental vehicle.

[0292] (Effect of the note) According to the management system described in Appendix 1 and the management program described in Appendix 5, when control input information indicating the control content for controlling the rental vehicle is input to the user terminal used by a user using a rental vehicle, control processing is performed to execute the control content indicated by the control input information on the rental vehicle, thereby making it possible to control the rental vehicle via the user terminal, for example.

[0293] According to the management system described in Appendix 2, by controlling rental vehicles via a server device, it becomes possible to properly control rental vehicles, for example.

[0294] According to the management system described in Appendix 3, the control input information is information indicating the control content for turning the rental vehicle's power on or off, making it possible, for example, to turn the rental vehicle's power on or off via a user terminal.

[0295] According to the management system described in Appendix 4, by performing return-related management processing, it becomes possible to manage the return of rental vehicles, for example. By performing return-related management processing based on power-related information, it becomes possible to have rental vehicles returned with the power turned off, for example, thereby preventing misuse after the return and preventing accidents caused by the unintended operation of the rental vehicle. [Explanation of Symbols]

[0296] 1 vehicle 2 Onboard equipment 3 Terminal devices 4 Server devices 11 batteries 12 motors 13 Communications Department 14 Records Section 15 Control Unit 21 Communications Department 22 Current position detection unit 23 Records Department 24 Control Unit 31 Communications Department 32 Touchpads 33 displays 34 Records Section 35 Control Unit 41 Communications Department 42 Records Section 43 Control Unit 51 Image display area 53 Return button 61 Image display area 63 Return button 91 Station 100 Management Systems 351 Acquisition Department 352 Management Department 421 User Information Database 422 Vehicle Information Database 423 Station Information Database 424 Usage information DB 425 Reservation Information Database 426 Return Reservation Information Database 431 Control Processing Unit 520 Status Information 521 1st information display column 522 2nd information display column 523 Third information display column 620 Status Information 621 1st information display column 622 2nd information display column 623 Third information display column

Claims

1. A management system for managing rental vehicles that are lent to users for use and are electric vehicles that run using charged electricity, A control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using the rental vehicle, A means for acquiring management information for managing the aforementioned rental vehicles, The system comprises a management means that performs return-related management processing for managing the return of the rental vehicle to a predetermined return location based on the management information acquired by the acquisition means, The aforementioned designated return location is equipped with a charging device for charging the rental vehicle. The acquisition means acquires power-related information indicating whether the rental vehicle's power is on or off, and charging status information indicating whether the rental vehicle is being charged, as the management information. The management means performs the return-related management process based on the power-related information and charging status information acquired by the acquisition means. The acquisition means is, When information indicating the control content for turning on the power of the rental vehicle is input to the user terminal as the control input information, and the power of the rental vehicle is turned on, information indicating that the power of the rental vehicle is on is acquired as the power-related information. When information indicating a control to turn off the power of the rental vehicle is input to the user terminal as control input information, and the power of the rental vehicle is turned off, information indicating that the power of the rental vehicle is off is acquired as power-related information. Management system.

2. The aforementioned management means is Based on the charging status information acquired by the acquisition means, a charging-related determination is made to determine whether or not the rental vehicle is being charged. Based on the power-related information acquired by the acquisition means, a power-related determination is made to determine whether or not the power to the rental vehicle is off. Based on the results of the charging-related determination and the power supply-related determination, a permit-related determination is made to determine whether or not to permit the return of the rental vehicle. The aforementioned management means is Based on the result of the aforementioned permission-related determination, the aforementioned return-related management process is performed. The aforementioned management means is If, as a result of the charging-related determination, the permission-related determination determines that the return of the rental vehicle should not be permitted, then information regarding the charging of the rental vehicle will be output via the user terminal as information indicating the user actions necessary to permit the return of the rental vehicle. The management system according to claim 1.

3. A management program for managing rental vehicles that are lent to users for use and are electric vehicles that run using charged electricity, Computers, A control processing means for performing control processing on the rental vehicle when control input information indicating control content for controlling the rental vehicle is input to a user terminal used by a user using the rental vehicle, A means for acquiring management information for managing the aforementioned rental vehicles, Based on the management information acquired by the acquisition means, the management means functions as a management means that performs return-related management processing for managing the return of the rental vehicle to a predetermined return location. The aforementioned designated return location is equipped with a charging device for charging the rental vehicle. The acquisition means acquires power-related information indicating whether the rental vehicle's power is on or off, and charging status information indicating whether the rental vehicle is being charged, as the management information. The management means performs the return-related management process based on the power-related information and charging status information acquired by the acquisition means. The acquisition means is, When information indicating the control content for turning on the power of the rental vehicle is input to the user terminal as the control input information, and the power of the rental vehicle is turned on, information indicating that the power of the rental vehicle is on is acquired as the power-related information. When information indicating a control to turn off the power of the rental vehicle is input to the user terminal as control input information, and the power of the rental vehicle is turned off, information indicating that the power of the rental vehicle is off is acquired as power-related information. Management program.

Images