JP2017016450A - Vehicle rental system, vehicle rental method and management server - Google Patents

Abstract

A new type of vehicle rental system, a vehicle rental method, and a management server are provided that are not easily restricted by the scale of a management organization. In a vehicle lending system or a vehicle lending method, a management server 28 communicates with each of a plurality of business entity terminals 20 via a network 34 and collectively manages lending and returning of vehicles 26 of a plurality of lending business entities. Is used. When the server control device 94 accepts the reservation of the vehicle 26, the server control device 94 displays the lending agreement data corresponding to the lending business entity that manages the vehicle 26 on the customer terminal 22, and sends the agreement to the customer terminal 22 that agrees to the contents of the data. The rental reservation is permitted on condition that there is an operation input. [Selection] Figure 11

Description

  The present invention relates to a vehicle rental system, a vehicle rental method, and a management server that can be commonly used by a plurality of management organizations.

  In recent years, so-called car sharing, in which a plurality of members jointly use a single vehicle, has attracted attention as a new form of use of the vehicle, and a technique related to car sharing has been developed (Patent Document 1).

  In the car sharing support system of Patent Document 1, communication between an information terminal device (such as a mobile phone) of a sharing member α and a system server of a system operator, and parking of the system server and parking lots A, B, and C are performed. A car sharing service is provided through communication with the parking lot management device ([0039] to [0042], FIG. 1). In the car sharing support system of Patent Document 1, a member who has registered as a member is given priority ([0039]).

JP 2004-178385 A

  As described above, in the car sharing support system (vehicle lending system) of Patent Document 1, when a share car is used, a member who has registered in advance is given priority. In a car sharing support system such as Patent Document 1, a user does not own a vehicle, but becomes a member of a management organization that manages rental vehicles (share cars), and reserves rental vehicles managed by the management organization when necessary. Then borrow.

  Such management organizations exist in various sizes. From the viewpoint of vehicle management operations such as rental and maintenance of owned vehicles and collective management of members, it is considered that a management organization that is somewhat large in scale is more advantageous for business development.

  On the other hand, focusing on the business form of the management organization of car sharing, since car sharing is used by multiple members, it is unique even in a relatively small community even if the number of vehicles owned is small. It can be said that it is possible to conduct a lending business that takes advantage of its operational characteristics.

  However, as described above, since vehicle management and member management are required for each management organization, the burden of business management costs will increase if there is no certain number of owned vehicles. It is an obstacle. In other words, the car sharing support system (vehicle lending system) of Patent Document 1 is not necessarily configured to be easy to use for a small administrative organization.

  Further, focusing on user convenience, the car sharing support system of Patent Document 1 restricts rental vehicles for each management organization belonging to a member and can be used mutually beyond the management organization. There was a problem that it was difficult.

  The present invention has been made in view of the above-described problems, and an object thereof is to provide a new form of a vehicle rental system, a vehicle rental method, and a management server that are not easily restricted by the scale of a management organization.

The vehicle lending system according to the present invention is for lending a plurality of vehicles,
The vehicle rental system includes:
A plurality of business entity terminals used by each of a plurality of rental business entities that manage the vehicle for rental;
A management server that communicates with each of the plurality of business entity terminals via a network and collectively manages lending and returning of the vehicles of the plurality of rental business entities,
The management server
A reservation database that collectively manages reservations and returns of the vehicles of each of the plurality of lending entities;
A clause database storing individual loan agreement data for each of the plurality of loan entities;
A server control device that manages lending of the vehicle that each of the plurality of lending entities individually has,
The server control device
A reservation screen for accepting a rental reservation for the vehicle of the plurality of rental entities is displayed on the customer terminal according to an operation on a customer terminal by a customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The lending reservation is permitted on condition that an operation input to the customer terminal to agree to the contents of the lending contract data is received.

  According to the present invention, the management server collectively manages reservations and returns of the vehicles individually owned by the plurality of lending enterprises. For this reason, the management server manages the management server (management entity) while reducing the calculation load on the plurality of entity terminals by collectively performing the processing performed on the plurality of entity terminals. It becomes possible to collectively manage the rental management of the vehicles of each rental business entity.

  Accordingly, each lending business entity can easily concentrate on a business specialized in a business part (core part) that actually handles the vehicle, such as provision and maintenance of the vehicle managed by itself. That is, each lending business entity can focus on the business part that lends the vehicle as an asset and obtains a fee by leaving the management business entity to reserve and return (peripheral part) of the vehicle that it manages.

  Therefore, each lending entity can easily develop a vehicle lending business that maintains its own business management environment, including its own lending agreement, while suppressing the cost of business support even if the number of vehicles owned is small. It becomes. For example, each lending business unit can easily develop a business as a small-scale franchise such as using a parking lot of a convenience store.

  In addition, the management entity handles all the vehicles from each rental entity, resulting in a reduction in management costs per unit due to an increase in the number of units and service expandability, and a stable usage fee for the system. It can be secured.

  The management server may include a fee database that stores a rental fee for the vehicle set for each of the plurality of rental business entities and for each usage time and travel distance of the vehicle. The server control device acquires the use time and travel distance of the vehicle in one rental from the vehicle or a parking lot terminal arranged in a parking lot used by the vehicle, and the acquired use time and the The rental fee may be calculated based on a travel distance and the rental entity that manages the vehicle or the vehicle itself.

  This makes it possible to set individual charges for each lending business entity. As a result, each lending entity can set a lending fee that reflects the regional characteristics and management philosophy of each lending entity, and it is possible to create a business that takes advantage of its uniqueness without being affected by other lending entities. Can be promoted.

  The vehicle rental system may include a settlement server that settles the rental fee. The server control device notifies the settlement server of the lending fee and the customer and the lending business entity corresponding thereto, and the settlement server performs the billing process for the customer and the payment process for the lending business entity. You may do this based on the price.

  As a result, the management server itself can omit the billing process for the customer and the billing process for the lending business entity. In other words, reservation management and billing / payment management can be separated. Thereby, the configuration of the management server can be simplified.

  The management server may include a customer database that collectively manages customer information including authentication information for reservation of the customer of a management entity that manages the management server. The server control device causes the customer terminal to display the reservation screen on the condition that the authentication based on the customer's reservation authentication information is successful when the management server is accessed from the customer terminal. Also good.

  As a result, the management server permits the reservation of the vehicle only to customers who have been successfully authenticated. In other words, since the management of the customer is performed by the management server (management business entity), the business entity terminal (lending business entity) can omit the management of the customer. For this reason, it is possible to further reduce the calculation load on the business entity terminal. Also, from the customer's perspective, customer information that can be grasped by each lending entity can be limited to the track record of the vehicle owned by that lending entity, and the usage record flows out to other lending entities. It is possible to suppress the leakage of personal information. As a result, the lending business entity can concentrate on the business part (core part) that actually handles the vehicle.

  The customer database may store personal identification information stored in a storage medium embedded in the card-type license as rental authentication information. The vehicle rental system may include a card reader that is provided in the vehicle itself or in a parking lot where the vehicle parks and reads the personal identification information from the card type license. The server control device, as a condition for permitting rental of the vehicle, that the personal identification information of the customer in the rental reservation registered in the reservation database matches the personal identification information read by the card reader Also good.

  Thereby, the customer can receive the rental of the vehicle by having the card reader read the personal identification information in the card type license. Therefore, it is not necessary to create a special membership card or carry it, and the convenience of the customer can be improved.

  The vehicle rental system may include a maintenance server that communicates with each of the plurality of business entity terminals and the management server via the network, and manages maintenance of the vehicle of the plurality of rental business entities. When the maintenance server receives a maintenance order from the business entity terminal, the maintenance server may transmit the order information to the management server. When the management server receives an inquiry about the reservation status of the maintenance target vehicle from the maintenance server or from a maintenance terminal connected to the maintenance server, the management server may notify the reservation status of the maintenance target vehicle.

  As a result, even when the reservation management of the vehicles of a plurality of lending enterprises is performed collectively on the management server, the maintenance entity using the maintenance server or the maintenance terminal connected thereto confirms the reservation status of the maintenance target vehicle. Is possible.

The vehicle lending method according to the present invention is a method using a vehicle lending system for lending a plurality of vehicles,
The vehicle rental system includes:
A plurality of business entity terminals used by each of a plurality of rental business entities that manage the vehicle for rental;
A management server that communicates with each of the plurality of business entity terminals via a network and collectively manages lending and returning of the vehicles of the plurality of rental business entities,
The management server
A reservation database that collectively manages reservations and returns of the vehicles that each of the plurality of lending entities individually has,
A clause database storing individual loan agreement data for each of the plurality of loan entities;
A server control device that manages lending of the vehicles of each of the plurality of lending entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle of the plurality of rental entities is displayed on the customer terminal according to an operation on a customer terminal by a customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The lending reservation is permitted on condition that an operation input has been made to the customer terminal to agree to the contents of the lending agreement data.

The vehicle rental reservation management server according to the present invention communicates via a network with each of a plurality of business entity terminals used by each of a plurality of rental business entities that manage a vehicle for rental, and centralizes the reservation of the vehicle rental Management,
The management server
Reservation database for managing reservation and return of the vehicle that each of the lending entities individually has,
A contract database storing individual loan contract data for each of the lending entities;
A server control device that manages lending of the vehicle of each of the lending business entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle is displayed on the customer terminal according to the operation of the customer terminal by the customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The lending reservation is permitted on condition that the customer terminal has been operated to agree to the contents of the lending agreement data.

The vehicle rental reservation management server according to the present invention communicates via a network with each of a plurality of business entity terminals used by each of a plurality of rental business entities that manage a vehicle for rental, and centralizes the reservation of the vehicle rental Management,
The management server
Reservation database for managing reservation and return of the vehicle that each of the lending entities individually has,
A server control device that manages lending of the vehicle of each of the lending business entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle is displayed on the customer terminal according to the operation of the customer terminal by the customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, when the server control device receives an inquiry about a reservation status from an entity terminal of a specific lending entity, the server control device displays the reservation status of only the vehicle corresponding to the specific lending entity. It is characterized by being displayed on the business entity terminal.

  According to the present invention, when the management server receives a reservation status inquiry from an entity terminal of a specific lending entity, the entity terminal of the specific lending entity corresponds to the specific lending entity. Only the reservation status of the vehicle is displayed. For this reason, even when reservations for vehicles of a plurality of lending entities are collectively managed by the management server, it is possible to prevent the reservation status regarding the vehicles of other lending entities from leaking to the specific lending entity.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to provide the vehicle rental system of the new form which is hard to receive the restrictions by the scale of a management organization, the vehicle rental method, and a management server.

It is a schematic structure figure showing simply a vehicle rental system concerning one embodiment of the present invention. It is the flowchart which showed simply the process at the time of the input of business entity information with respect to a management server from the business entity terminal in the said embodiment. It is the flowchart which showed simply the process at the time of the input of the vehicle information with respect to the said management server from the said entity terminal in the said embodiment. It is the flowchart which showed simply the process at the time of the input of customer information with respect to the said management server from the customer terminal in the said embodiment (namely, at the time of member registration). It is the 1st flowchart which showed simply the process at the time of reservation in the embodiment. It is the 2nd flowchart which showed simply the process at the time of reservation in the embodiment. It is a figure which shows the 1st example of the reservation screen in the said embodiment. It is a figure which shows the 2nd example of the said reservation screen in the said embodiment. It is a figure which shows the 3rd example of the said reservation screen in the said embodiment. It is a figure which shows the 4th example of the said reservation screen in the said embodiment. It is a figure which shows an example of the reservation confirmation screen in the said embodiment. It is the flowchart which showed simply the process at the time of the use start of the vehicle in the said embodiment. It is the flowchart which showed simply the process at the time of the use completion of the said vehicle in the said embodiment. It is a figure which shows an example of the vehicle monitoring screen in the said embodiment. It is the flowchart (detail of S93 of FIG. 13) which showed simply the process at the time of completion of use in the embodiment. It is the flowchart which showed simply the process at the time of the maintenance order with respect to the maintenance server from the said entity terminal in the said embodiment. It is the flowchart which showed simply the process at the time of the data inquiry with respect to the said management server from the said entity terminal in the said embodiment. It is the flowchart which showed simply the process at the time of the data inquiry with respect to the said management server from the said maintenance server in the said embodiment.

A. One Embodiment [A1. Configuration of vehicle rental system 10]
(A1-1. Overall configuration)
FIG. 1 is a schematic configuration diagram schematically illustrating a vehicle lending system 10 (hereinafter also referred to as “lending system 10” or “system 10”) according to an embodiment of the present invention. In the system 10, a plurality of vehicles 26 owned by a plurality of lending entities (hereinafter referred to as “lending entity EL”) are lent to a plurality of customers (hereinafter referred to as “customer C”) via the management server 28. . Thereby, the lending business entity EL can perform the lending business regardless of its scale. Further, the customer C can easily select the vehicle 26 possessed by the plurality of rental business entities EL as the rental target vehicle, and convenience is improved.

  The system 10 includes a plurality of business entity terminals 20, a plurality of customer terminals 22, a settlement server 30, and a maintenance server 32 in addition to the plurality of vehicles 26 and the management server 28. These components are communicable via a communication network 34 (hereinafter also referred to as “network 34”). In FIG. 1, only one business entity terminal 20, customer terminal 22, and vehicle 26 are shown. A plurality of management servers 28, settlement servers 30 and maintenance servers 32 may be provided.

(A1-2. Business entity terminal 20)
A plurality of business entity terminals 20 (hereinafter also referred to as “terminals 20”) are installed at each business office of the plurality of lending business entities EL, confirming the reservation status of the vehicle 26 of the lending business entity EL, and confirming customer information. Used for etc. It should be noted that the terminal 20 of this embodiment does not directly manage the rental and return of the vehicle 26.

  The terminal 20 includes a communication unit 40, an input / output unit 42, a calculation unit 44, and a storage unit 46. As the terminal 20, for example, a personal computer can be used.

  The communication unit 40 inputs and outputs signals with the management server 28, the settlement server 30, the maintenance server 32, and the like. The input / output unit 42 performs input / output between an employee of the lending business entity EL or a person equivalent thereto and the business entity terminal 20. In other words, the input / output unit 42 is an HMI (Human-Machine Interface). The input / output unit 42 includes, for example, a keyboard, a mouse, and a display device (all not shown).

  The calculation unit 44 controls each unit of the terminal 20 by executing a program stored in the storage unit 46. For example, the calculation unit 44 communicates with the management server 28 via the communication unit 40 and acquires various types of information related to the rental of the vehicle 26 from the management server 28. In addition, the calculation unit 44 communicates with the payment server 30 via the communication unit 40 and acquires payment information Is (described later) associated with the rental of the vehicle 26 from the payment server 30. Further, the calculation unit 44 communicates with the maintenance server 32 via the communication unit 40 and exchanges information regarding the maintenance of the vehicle 26 with each other. The processing of the calculation unit 44 will be described later with reference to FIGS. 2, 3, 6, 16, and 17.

  The storage unit 46 includes a volatile memory and a non-volatile memory (not shown), and stores various programs executed by the calculation unit 44 and various data.

(A1-3. Customer terminal 22)
A plurality of customer terminals 22 (hereinafter also referred to as “terminals 22”) are owned by a plurality of customers C, and are provided by a business entity that manages the system 10 (hereinafter referred to as “management business entity EM”). It is used for membership registration to the service, reservation of the vehicle 26, and the like.

  The terminal 22 includes a communication unit 50, an input / output unit 52, a calculation unit 54, and a storage unit 56. As the terminal 22, for example, a personal computer or a smartphone can be used.

  The communication unit 50 inputs and outputs signals with the management server 28, the payment server 30, and the like. The input / output unit 52 performs input / output between the customer C (member) and the customer terminal 22. In other words, the input / output unit 52 is an HMI. When the terminal 22 is a personal computer, the input / output unit 52 includes, for example, a keyboard, a mouse, and a display device (all not shown). When the terminal 22 is a smartphone, the input / output unit 52 includes, for example, a touch panel (not shown).

  The calculation unit 54 controls each unit of the terminal 22 by executing a program stored in the storage unit 56. For example, the calculation unit 54 communicates with the management server 28 via the communication unit 50, and exchanges various information (including member registration information) regarding the rental of the vehicle 26 with the management server 28. In addition, the calculation unit 54 communicates with the payment server 30 via the communication unit 50 and acquires the payment information Is associated with the rental of the vehicle 26 from the payment server 30. The processing of the calculation unit 54 will be described later with reference to FIGS.

  The storage unit 56 includes a volatile memory and a non-volatile memory (not shown), and stores various programs executed by the calculation unit 54 and various data.

(A1-4. Vehicle 26)
The plurality of vehicles 26 are managed as rental objects by each rental business entity EL. The term “manage” here is used not only to mean “own” but also to have management responsibility for maintenance of the vehicle 26. That is, not only the case where the lending entity EL has ownership but also the case where it is loaned from another entity or an individual, for example.

  The vehicle 26 includes a communication unit 70, an input / output unit 72, a calculation unit 74, a storage unit 76, a lock mechanism 78, and various sensors 80. The communication unit 70 inputs and outputs signals with the management server 28.

  The input / output unit 72 performs input / output between the customer C (member) and the vehicle 26. In other words, the input / output unit 72 is an HMI. The input / output unit 72 includes, for example, a touch panel or a button (not shown). The input / output unit 72 also includes a card reader 84 that reads authentication information Iid from an authentication card 82 (hereinafter also referred to as “card 82”) possessed by the customer C. The card 82 of this embodiment can be a driver's license with an integrated circuit (IC) incorporated therein, for example. Further, the card reader 84 of the present embodiment is fixed to a specific part of the vehicle 26 (for example, below the rear window), and is provided for each vehicle 26.

  The calculation unit 74 controls each unit related to rental and return of the vehicle 26 by executing a program stored in the storage unit 76. For example, the calculation unit 74 transmits the information of the customer C read via the card reader 84 at the start of use of the vehicle 26 to the management server 28 via the communication unit 70. The management server 28 that has received the information on the customer C determines whether or not the corresponding reservation information Ir exists. If there is corresponding reservation information Ir, the management server 28 transmits an unlocking command to the calculation unit 74. Receiving the unlock command, the calculation unit 74 operates the lock mechanism 78 to unlock.

  In addition, the calculation unit 74 communicates with the management server 28 via the communication unit 70, and exchanges various types of information related to the rental of the vehicle 26 (including detection values of various sensors 80) with the management server 28. Interact. Further, the calculation unit 74 operates the lock mechanism 78 in accordance with a command from the management server 28 to perform unlocking or locking.

  The processing of the calculation unit 74 will be described later with reference to FIGS.

  The storage unit 76 includes a volatile memory and a non-volatile memory (not shown), and stores various programs executed by the calculation unit 74 and various data.

  The lock mechanism 78 automatically unlocks and locks a door lock (not shown). Various sensors 80 detect various values of the vehicle 26 (see FIG. 14).

(A1-5. Management Server 28)
The management server 28 (hereinafter also referred to as “server 28”) is set in a business establishment of the management entity EM of the vehicle rental system 10 and performs various types of management in the entire vehicle rental system 10. In the present embodiment, instead of each business entity terminal 20 (or a server provided by each rental business entity EL), the management server 28 manages the rental and return of the vehicle 26 and the like.

  The server 28 includes a communication unit 90, an input / output unit 92, a calculation unit 94, and a storage unit 96. The communication unit 90 inputs and outputs signals between the business entity terminal 20, the customer terminal 22, the vehicle 26, the settlement server 30, and the maintenance server 32. The input / output unit 92 performs input / output between the employee of the management entity EM or a person equivalent thereto and the server 28. In other words, the input / output unit 92 is an HMI. The input / output unit 92 includes, for example, a keyboard, a mouse, and a display device (all not shown).

  The calculation unit 94 controls each unit of the server 28 by executing a program stored in the storage unit 96. As shown in FIG. 1, the calculation unit 94 includes a business entity management unit 100, a customer management unit 102, a reservation management unit 104, a vehicle management unit 106, a billing management unit 108, and a maintenance management unit 110. .

  The business entity management unit 100 manages the lending business entity EL through control related to the business entity terminal 20. The customer management unit 102 manages the customer C (member) through control related to the customer terminal 22. The reservation management unit 104 manages reservation and return of the vehicle 26. The vehicle management unit 106 performs unlocking and locking of the vehicle 26, monitoring of the running state, and the like. The bill management unit 108 manages bills associated with the use of the vehicle 26. The maintenance management unit 110 manages information related to maintenance of the vehicle 26. The processing of the calculation unit 94 will be described later with reference to FIGS.

  The storage unit 96 includes a volatile memory and a non-volatile memory (not shown), and stores various programs executed by the calculation unit 94 and various data. As shown in FIG. 1, the storage unit 96 includes a business entity database 120, a customer database 122, a reservation database 124, a terms and conditions database 126, a vehicle database 128, a billing database 130, and a maintenance database 132.

  The business entity database 120 (hereinafter referred to as “business entity DB 120”) stores information related to the lending business entity EL (hereinafter also referred to as “business entity information Ie”). The business entity information Ie includes, for example, general information (name, location, telephone number, business hours, etc.), an outline of the managed vehicle (vehicle type, year, etc.), and usage conditions.

  The customer database 122 (hereinafter referred to as “customer DB 122”) stores information related to the customer C (hereinafter also referred to as “customer information Ic”). The customer information Ic includes, for example, general information (name, address, telephone number, etc.) and usage history.

  The reservation database 124 (hereinafter referred to as “reservation DB 124”) has information (hereinafter also referred to as “reservation information Ir”) of the reservation status (including the start of rental and return time) regarding the vehicle 26 of each rental entity EL. accumulate. The reservation information Ir managed by the reservation DB 124 of this embodiment relates to the vehicle 26 of each lending business entity EL.

  The terms and conditions database 126 (hereinafter referred to as “terms and terms DB 126”) accumulates loan terms and conditions data Dcl (hereinafter also referred to as “terms and terms data Dcl”) of each lending entity EL.

  The vehicle database 128 (hereinafter referred to as “vehicle DB 128”) stores information related to each vehicle 26 (hereinafter also referred to as “vehicle information Iv”). The vehicle information Iv includes, for example, an identification code of a rental entity EL to be managed, a vehicle type, a year, a VIN (Vehicle Identification Number), a current position, a travel distance (cumulative, at the start of rental, at the time of return, etc.), for vehicle driving The remaining amount of energy and the remaining amount of battery for auxiliary equipment are included.

  When the vehicle 26 is a gasoline vehicle (including a hybrid vehicle), the vehicle driving energy remaining amount indicates the remaining amount of gasoline, and the vehicle 26 is an electric vehicle (battery vehicle, hybrid vehicle, fuel cell vehicle, etc.). ), The remaining amount of the high voltage battery is included. When the vehicle 26 is a fuel cell vehicle, the remaining amount of energy includes the remaining amount of hydrogen gas. The remaining amount of auxiliary battery includes the remaining amount of low voltage auxiliary battery (for example, 12V battery).

  In the billing database 130 (hereinafter referred to as “billing DB 130”), the rental fee information of the vehicle 26 (hereinafter referred to as “charge information If”) is stored for each of a plurality of rental business entities EL and for each usage time and travel distance of the vehicle 26. Is remembered. The billing DB 130 stores billing information (hereinafter also referred to as “billing information Ich”) associated with the rental of the vehicle 26 for each use based on the fee information If. The billing information Ich includes, for example, date / time and fee. The billing information Ich is managed for each vehicle 26 or for each customer C, for example.

  The maintenance database 132 (hereinafter referred to as “maintenance DB 132”) stores information related to maintenance of the vehicle 26 (hereinafter also referred to as “maintenance information Im”). The maintenance information Im includes, for example, a scheduled maintenance date and maintenance content.

  In FIG. 1, each database 120, 122, 124, 126, 128, 130, 132 is shown separately, but some databases (for example, terms and conditions DB 126) are replaced with other databases (for example, reservation DB 124). It may be a part.

(A1-6. Settlement server 30)
The settlement server 30 (hereinafter also referred to as “server 30”) is set in a business establishment or the like of an entity that settles the rental fee of the vehicle 26 (hereinafter referred to as “settlement entity ES”). Perform credit and settlement. The server 30 includes a communication unit 140, an input / output unit 142, a calculation unit 144, and a storage unit 146.

  The communication unit 140 inputs and outputs signals between the business entity terminal 20, the customer terminal 22, the management server 28, and the maintenance server 32. The input / output unit 142 performs input / output between an employee of the settlement business entity ES or a person equivalent thereto and the server 30. The input / output unit 142 includes, for example, a keyboard, a mouse, and a display device (all not shown). In other words, the input / output unit 92 is an HMI.

  The computing unit 144 controls each unit of the server 30 by executing a program stored in the storage unit 146. For example, the computing unit 144 outputs information related to credit (hereinafter referred to as “credit information Icr”) in response to an inquiry from the management server 28 regarding credit of the customer C. In addition, when the billing information Ich associated with the use of the vehicle 26 is acquired from the management server 28, the calculation unit 144 bills the customer C for a rent fee (including deduction from a bank account) based on the billing information Ich. At the same time, payment to the lending entity EL (transfer to bank account, etc.) is performed. That is, the settlement server 30 (or the settlement entity ES) performs the collection of the rental fee from the customer C.

  The storage unit 146 includes a volatile memory and a non-volatile memory (not shown), and stores various programs executed by the calculation unit 144 and various data. As illustrated in FIG. 1, the storage unit 146 includes a credit database 150 and a payment database 152.

  The credit database 150 (hereinafter referred to as “credit DB 150”) stores credit information Ic for each customer C. The settlement database 152 (hereinafter referred to as “settlement DB 152”) stores settlement information Is for each lending business entity EL and for each customer C. The settlement information Is includes payment information (debt information) related to the loan entity EL from the settlement entity ES and billing information Ich (bond information) related to the customer C from the settlement entity ES.

  In the present embodiment, the management entity EM managing the management server 28 does not directly charge the rental fee to the customer C. Instead, the management entity EM collects the usage fee of the system 10 for each rental from the rental entity EL.

(A1-7. Maintenance server 32)
The maintenance server 32 (hereinafter also referred to as “server 32”) is set in an establishment of an entity (hereinafter referred to as “maintenance entity EMC”) that performs maintenance of the vehicle 26 in place of the rental entity EL, and the vehicle. 26 maintenance is managed. In the present embodiment, whether or not to entrust maintenance of the vehicle 26 to the maintenance business entity EMC is left to the judgment of each lending business entity EL.

  The server 32 includes a communication unit 160, an input / output unit 162, a calculation unit 164, and a storage unit 166. The communication unit 160 inputs and outputs signals between the business entity terminal 20 and the management server 28. The input / output unit 162 performs input / output between the employee of the maintenance business entity EMC or a person equivalent thereto and the server 32. In other words, the input / output unit 162 is an HMI. The input / output unit 162 includes, for example, a keyboard, a mouse, and a display device (all not shown).

  The computing unit 164 controls each unit of the server 32 by executing a program stored in the storage unit 166. For example, the calculation unit 164 receives maintenance in response to a request from the business entity terminal 20. The server 32 also manages the maintenance information Im via the maintenance database 170 (hereinafter referred to as “maintenance DB 170”) in the storage unit 166. In addition, in response to a request from an employee or the like of the maintenance business entity EMC, the calculation unit 164 inquires of the management server 28 about the reservation status of the vehicle 26 that is being maintained by the maintenance business entity EMC.

[A2. Processing in each scene]
Next, processing of each component in each scene of the present embodiment will be described in association with a user operation.

(A2-1. When inputting business entity information Ie (when registering a lending business entity EL))
FIG. 2 is a flowchart schematically showing processing at the time of inputting business entity information Ie from the business entity terminal 20 to the management server 28 in the present embodiment. 2, steps S1, S3, S5, and S9 on the business entity terminal 20 side are executed by the calculation unit 44, and steps S2, S4, S6, and S8 on the management server 28 side are executed by the calculation unit 94 (business The body management unit 100) executes.

  In step S <b> 1, the user of the business entity terminal 20 accesses the management server 28 via the business entity terminal 20. In other words, the business entity terminal 20 accesses the website of the management server 28 in response to a user operation input. In step S <b> 2, the management server 28 transmits the input screen information of the business entity information Ie according to the operation input from the business entity terminal 20.

  In step S <b> 3, the user inputs the business entity information Ie on the input screen of business entity information Ie and transmits it to the management server 28. In other words, the business entity terminal 20 displays the input screen on the display device (input / output unit 42) based on the input screen information from the management server 28. Then, the business entity terminal 20 displays the business entity information Ie according to the user's input on the display device. When the transmission button in the display device is selected by the user, the business entity information Ie is displayed on the management server 28. Send to.

  The business entity information Ie here includes, for example, the name of a corporation, representative name, head office location, sales office location, business hours of each sales office, station location, number of employees, capital, establishment year, bank account information, Loan agreement data Dcl and the like are included.

  In step S <b> 4, the management server 28 transmits information on a confirmation screen (input confirmation screen) for confirming the business entity information Ie received from the business entity terminal 20 to the business entity terminal 20.

  In step S5, the user confirms the contents of the input confirmation screen and then presses a confirmation button. In other words, the business entity terminal 20 displays an input confirmation screen on the display device (input / output unit 42) based on the input confirmation screen information from the management server 28. When the user selects the confirmation button in the display device, the business entity terminal 20 transmits a notification (input information confirmation notification) to the management server 28 that the entered business entity information Ie has been confirmed. To do.

  In step S6, when receiving the input information confirmation notification from the business entity terminal 20, the management server 28 provisionally registers (or temporarily stores) the business entity information Ie in the business entity DB 120. In step S7, the management entity EM managing the management server 28 performs an examination (subscription examination) as to whether or not the lending entity EL is permitted to join the service based on the provisionally registered entity information Ie. .

  In step S <b> 8, the management entity EM transmits the result of the subscription examination to the entity terminal 20 via the management server 28. In step S9, when the business entity terminal 20 receives the notification of the examination result from the management business entity EM, the business entity terminal 20 displays it on the display device. In addition, when the enrollment examination is passed, the management entity EM fully registers the entity information Ie temporarily registered in the entity DB 120. In addition, the management entity EM mails a user ID and password for editing the entity information Ie, vehicle information Iv, and the like on the website of the management server 28.

  The processing in FIG. 2 can also be performed in writing without communication between the business entity terminal 20 and the management server 28. In this case, the management entity EM registers much of the entity information Ie in the entity DB 120. Further, the clause data Dcl may be stored in a storage medium such as a CD-ROM or a USB memory and then mailed from the lending entity EL to the management entity EM. Then, the management entity EM that has received this storage medium registers the contract data Dcl in the contract DB 126.

(A2-2. When vehicle information Iv is input (when rental vehicle 26 is registered))
FIG. 3 is a flowchart schematically showing processing at the time of inputting the vehicle information Iv from the business entity terminal 20 to the management server 28 in the present embodiment. 3, steps S11, S13, and S15 on the business entity terminal 20 side are executed by the calculation unit 44, and steps S12, S14, and S16 on the management server 28 side are executed by the calculation unit 94 (the business unit management unit 100). ) Is executed.

  In step S <b> 11, the user of the business entity terminal 20 accesses the management server 28 via the business entity terminal 20. In other words, the business entity terminal 20 accesses the website of the management server 28 in response to a user operation input. In step S <b> 12, the management server 28 transmits the input screen information of the vehicle information Iv according to the operation input from the business entity terminal 20.

  In step S <b> 13, the user inputs the vehicle information Iv on the input screen of the vehicle information Iv and transmits it to the management server 28. In other words, the business entity terminal 20 displays the input screen on the display device (input / output unit 42) based on the input screen information from the management server 28. Then, the business entity terminal 20 displays the vehicle information Iv according to the user input on the display device, and when the transmission button in the display device is selected by the user, the input vehicle information Iv is sent to the management server 28. To send.

  The vehicle information Iv here includes, for example, each vehicle type, color, vehicle number (number plate number), rental business entity EL, and sales office (management sales office OM) that actually manages the vehicle 26.

  In step S <b> 14, the management server 28 transmits information on the confirmation screen (input confirmation screen) for confirming the vehicle information Iv received from the business entity terminal 20 to the business entity terminal 20.

  In step S15, after confirming the content of the input confirmation screen, the user presses a confirmation button. In other words, the business entity terminal 20 displays an input confirmation screen on the display device (input / output unit 42) based on the input confirmation screen information from the management server 28. When the confirmation button in the display device is selected by the user, the business entity terminal 20 transmits to the management server 28 a notification that the input vehicle information Iv has been confirmed (input information confirmation notification). .

  In step S16, when receiving the input information confirmation notification from the business entity terminal 20, the management server 28 registers (or stores) the vehicle information Iv in the business entity DB 120, the reservation DB 124, and the vehicle DB 128.

  The vehicle information Iv registered in the business entity DB 120 includes, for example, the vehicle type, color, vehicle number (number of the number plate), and management office OM. The vehicle information Iv registered in the reservation DB 124 includes, for example, the vehicle type, color, vehicle number, and identification code of the lending entity EL (name of the lending entity EL, etc.). The vehicle information Iv registered in the vehicle DB 128 includes, for example, the vehicle type, color, vehicle number, identification code of the lending business entity EL, and identification code of the management office OM.

  Note that the processing of FIG. 3 can also be performed in writing without communication between the business entity terminal 20 and the management server 28. In that case, the management entity EM registers the vehicle information Iv in the vehicle DB 128.

(A2-3. When entering customer information Ic (when registering as a member))
FIG. 4 is a flowchart schematically showing processing when the customer information Ic is input from the customer terminal 22 to the management server 28 (that is, at the time of member registration) in the present embodiment. 4, the calculation unit 54 executes steps S21, S23, and S25 on the customer terminal 22 side, and the calculation unit 94 (customer management unit 102) performs steps S22, S24, and S26 on the management server 28 side. Run.

  In step S <b> 21, the user of the customer terminal 22 (that is, the customer C) accesses the management server 28 via the customer terminal 22. In other words, the customer terminal 22 accesses the website of the management server 28 in response to a user operation input. In step S <b> 22, the management server 28 transmits the input screen information of the customer information Ic according to the operation input from the customer terminal 22.

  In step S <b> 23, the user inputs the customer information Ic on the input screen of the customer information Ic and transmits it to the management server 28. In other words, the customer terminal 22 displays the input screen on the display device (input / output unit 52) based on the input screen information from the management server 28. Then, the customer terminal 22 displays the customer information Ic corresponding to the user input on the display device, and when the user selects the send button in the display device, the input customer information Ic is sent to the management server 28. Send.

  The customer information Ic here includes, for example, a name, an address, a telephone number, and an e-mail address. The customer information Ic includes authentication information Iid for authenticating the customer C. The authentication information Iid includes reservation-time authentication information Iid1 when making a reservation for the vehicle 26 and rental-time authentication information Iid2 when actually renting the vehicle 26.

  The reservation authentication information Iid1 includes a login ID and a password. In addition, the license information of the customer C can be included in the rental authentication information Iid2. This makes it easy to authenticate the customer C when using an IC license as the card 82. Further, the customer information Ic may include a credit card number. In this case, the management server 28 can make an inquiry to the settlement server 30 for credit information using a credit card number or the like.

  In step S <b> 24, the management server 28 transmits information on the confirmation screen (input confirmation screen) for confirming the customer information Ic received from the customer terminal 22 to the customer terminal 22.

  In step S25, the user confirms the contents of the input confirmation screen and then presses a confirmation button. In other words, the customer terminal 22 displays the input confirmation screen on the display device (input / output unit 52) based on the input confirmation screen information from the management server 28. When the confirmation button in the display device is selected by the user, the customer terminal 22 transmits a notification (input information confirmation notification) that the inputted customer information Ic has been confirmed to the management server 28.

  In step S <b> 26, when receiving the input information confirmation notification from the customer terminal 22, the management server 28 registers (or stores) the customer information Ic in the customer DB 122.

  Note that the processing in FIG. 4 can also be performed in writing without communication between the customer terminal 22 and the management server 28. In that case, the management entity EM registers the customer information Ic in the customer DB 122.

(A2-4. At the time of reservation)
(A2-4-1. Processing at the time of reservation)
FIG. 5 and FIG. 6 are first and second flowcharts schematically showing processing at the time of reservation in the present embodiment. Of the steps in FIGS. 5 and 6, steps S31, S33, S35, S42, and S45 on the customer terminal 22 side are executed by the calculation unit 54. Steps S32 and S34 on the management server 28 side are executed by the customer management unit 102 of the calculation unit 94, and steps S36, S39 to S41, and S44 are executed by the reservation management unit 104 of the calculation unit 94. The calculation unit 144 executes steps S37 and S38 of the settlement server 30, and the calculation unit 44 executes step S43 of the business entity terminal 20.

  In step S <b> 31, the user of the customer terminal 22 (that is, customer C) accesses the management server 28 via the customer terminal 22. In other words, the customer terminal 22 accesses the website of the management server 28 in response to a user operation input. In step S <b> 32, the management server 28 transmits information (reservation screen information) related to a reservation screen (reservation screen 200 (FIGS. 7 to 10)) in response to an operation input from the customer terminal 22.

  In step S <b> 33, the user inputs reservation information Ir on the reservation screen 200 and transmits it to the management server 28. In other words, the customer terminal 22 displays the reservation screen 200 on the display device (input / output unit 52) based on the reservation screen information from the management server 28. Then, the customer terminal 22 displays the reservation information Ir corresponding to the user input on the display device, and when the user selects the transmission button in the display device, the input reservation information Ir is sent to the management server 28. Send.

  When making a reservation for the vehicle 26, the management server 28 first transmits login screen information to the customer terminal 22 and requests input of a login ID and a password. The reservation of the vehicle 26 is permitted only when the customer C (member) is successfully authenticated by the login ID and the password.

  In the present embodiment, the vehicle 26 can be reserved while switching the reservation screens 200 of FIGS. 7 to 10 as necessary. Further, the vehicles 26 that can be selected on the reservation screen 200 are managed by a plurality of lending enterprises EL. Therefore, it is possible to present more options for the vehicle 26 to the customer C. The reservation screen 200 of FIGS. 7 to 10 will be described in detail later.

  In step S <b> 34, the management server 28 transmits information (reservation confirmation screen information) on a confirmation screen (reservation confirmation screen 300) for confirming the reservation information Ir received from the customer terminal 22 to the customer terminal 22. At this time, as shown in FIG. 11, the terms and conditions display column 312 of the reservation confirmation screen 300 includes the terms and conditions data Dcl (details will be described later).

  In step S <b> 35, the user confirms the content of the reservation confirmation screen 300 and then presses the registration button 316. In other words, the customer terminal 22 displays the reservation confirmation screen 300 on the display device (input / output unit 52) based on the reservation confirmation screen information from the management server 28. When the registration button 316 is selected while the check box 320 in the display device is checked by the user, the customer terminal 22 notifies that the inputted reservation information Ir has been confirmed (reservation information confirmation notification). Is transmitted to the management server 28.

  When the customer C does not agree to the terms and conditions and the confirmation button is pressed, the customer terminal 22 notifies the management server 28 to that effect. The management server 28 that has received the notification causes the customer terminal 22 to display a display indicating that consent to the terms and conditions is necessary.

  In step S <b> 36 of FIG. 6, the management server 28 transmits a credit request together with the customer information Ic to the settlement server 30. The customer information Ic here includes, for example, the name and credit card number of the customer C. In step S37, the settlement server 30 that has received the credit request makes a credit decision based on the customer information Ic from the management server 28 and the credit information Ic in the credit DB 150. In subsequent step S <b> 38, the settlement server 30 transmits the result of the credit determination to the management server 28.

  In step S <b> 39, the management server 28 determines whether or not the credit judgment result received from the settlement server 30 recognizes the credit (whether or not the credit is established). If credit is established (S39: YES), in step S40, the management server 28 registers the reservation information Ir in the reservation DB 124. Thereby, the reservation of the vehicle 26 is confirmed. It should be noted that the reservation information Ir can be provisionally registered in the reservation DB 124 at the time of step S36 and can be fully registered in step S40. In this case, if NO in step S39, the management server 28 deletes the temporary registration information.

  In step S <b> 41, the management server 28 notifies the customer terminal 22 and the business entity terminal 20 of the confirmed reservation information Ir (and that the reservation has been confirmed). The customer terminal 22 and the business entity terminal 20 that have received the notification display the reservation information Ir in steps S42 and S43. In addition, the content of the expression form of the notification transmitted from the management server 28 to the customer terminal 22 and the business entity terminal 20 can be different from each other.

  Returning to step S39, when the result of the credit judgment received from the settlement server 30 is one that does not permit credit (when credit is not established) (S39: NO), in step S44, the management server 28 cannot make a reservation. The customer terminal 22 is notified to that effect. The customer terminal 22 that has received the notification displays the content of the notification in step S45.

(A2-4-2. Details of reservation screen 200)
7 to 10 are diagrams illustrating first to fourth examples of the reservation screen 200 in the present embodiment. The reservation screen 200 (200a) in FIG. 7 includes a map display unit 210, an address / nearest station search column 212, a station search column 214, a vehicle type search column 216, search execution buttons 218a to 218c, and an information column 220. And have.

  The map display unit 210 displays a map indicating the presence or absence of a station (parking lot) for renting the vehicle 26 by district. When a part of the map displayed on the map display unit 210 is selected, the screen is switched to a reservation screen 200c (FIG. 9) showing a list of stations at the selected location.

  The address / nearest station search column 212 is a column for inputting an address or the nearest station name in order to search for a station. The station search column 214 is a column for inputting a station name to search for a station. The vehicle type search column 216 is a column for inputting a vehicle type in order to search for a station. Note that the search fields 212, 214, and 216 are not limited to character input using a keyboard or the like, and can be configured to be selected using pull-down options.

  The search execution buttons 218a to 218c are buttons for executing a search based on the contents input in the search fields 212, 214, and 216. The information column 220 is a column that displays various types of information (for example, rules related to refueling).

  The reservation screen 200 (200b) in FIG. 8 has a plurality of district option display fields 230a to 230f. Each area option display column 230a-230f is used in order to narrow down a station. In the display columns 230a to 230f, for each district in the map display section 210, an option for selecting the entire district (“all districts”) and an option for selecting a district further divided into the districts (FIG. 8 is “***”).

  When one of the options is selected by the customer C, a reservation screen 200 (same screen as in FIG. 9) corresponding to the option is displayed. That is, when any option is selected by the customer C, the selection content is transmitted from the customer terminal 22 to the management server 28. The management server 28 transmits new reservation screen information corresponding to the received selection content to the customer terminal 22. And the customer terminal 22 which received new reservation screen information displays the reservation screen 200 according to the received reservation screen information.

  The reservation screen 200 (200c) in FIG. 9 is an example of the reservation screen 200 that is displayed when a search is performed using the address / nearest station search field 212 in FIG. The reservation screen 200c includes a search result number display column 240, a search result station display column 242, a screen switching button 244, an all check button 246, an all exclude button 248, and a return button 250.

  The search result number display column 240 is a column for displaying the number of stations as a search result. The search result station display column 242 is a column for displaying a station and address search as a search result. The management server 28 can simultaneously include stations of a plurality of rental business entities EL in the display field 242. For this reason, the customer C (member) can simultaneously search for stations of a plurality of lending business entities EL.

  The display field 242 includes a reservation target check box 252 (hereinafter referred to as “check box 252”). The check box 252 is a check box for selecting a specific station from the stations displayed in the display field 242, and a plurality of check boxes 252 can be selected at the same time.

  The screen switching button 244 is a button for shifting to the reservation screen 200d of FIG. 10 for the station whose check box 252 is checked. The all item check button 246 is a button for checking all the check boxes 252. The all item exclusion button 248 is a button for removing the check from all the check boxes 252. The return button 250 is a button for returning to the previous screen.

  A reservation screen 200 (200d) in FIG. 10 is an example of the reservation screen 200 displayed when a station is selected. The reservation screen 200d includes a reference date / time selection field 260, an update button 262, an availability display field 264, a reservation information input field 266, a reservation registration button 268, and a driver additional registration button 270.

  The reference date / time selection column 260 is a column for selecting a reference date / time for checking the availability of the vehicle 26. The update button 262 is a button for updating the reference date and time selected in the selection field 260. The vacancy status display column 264 is a column that displays the vacancy status of the vehicle 26 for a predetermined period (for example, 14 days) based on the reference date and time selected in the selection column 260. The vacancy status display column 264 includes a station name display column 272, a vehicle type name display column 274, a vehicle number display column 276, a color display column 278, and a date-by-day vacancy information display column 280.

  The station name display column 272 is a column for displaying a station name. The vehicle type name display column 274 is a column for displaying the vehicle type name of each vehicle 26. The vehicle number display column 276 is a column for displaying the vehicle number of each vehicle 26. The color display column 278 is a column for displaying the color of each vehicle 26. The vacancy information display column 280 for each day is a column indicating the vacancy status of each vehicle 26 for each date. Here, “○” (circle) is displayed for a day when there is sufficient vacancy for the rental time zone of the vehicle 26, and “△” (triangle) is displayed for a day when there is not enough vacancy. “×” (cross mark) is displayed for days that do not exist at all.

  The reservation information input field 266 is a field for inputting the scheduled boarding date and time, the usage time, and the vehicle 26. For example, a pull-down type option can be used. The reservation registration button 268 is a button for registering a reservation with the contents displayed in the reservation information input field 266. The driver addition registration button 270 is a button for displaying a driver addition screen (not shown) for adding a driver of the vehicle 26 to be lent.

(A2-4-3. Details of reservation confirmation screen 300)
FIG. 11 is a diagram showing an example of a reservation confirmation screen 300 in the present embodiment. The reservation confirmation screen 300 in FIG. 11 includes a reservation content display field 310, terms and conditions display field 312, terms and conditions agreement check field 314, a registration button 316, and a return button 318.

  The reservation content display column 310 is a column for displaying the reservation content. The reservation content here includes a member number, a name of the reservation person, and a reservation date and time (scheduled date and time of return and return date and time). The clause display column 312 is a column for displaying a clause based on the clause data Dcl. The agreement agreement check column 314 has a check box 320 indicating that the agreement based on the agreement data Dcl is agreed. The registration button 316 is a button for agreeing to the reservation contents and terms and conditions displayed in the display field 310 and registering the reservation information Ir. The return button 318 is a button for returning to the previous screen.

(A2-5. At the start of use of the vehicle 26)
FIG. 12 is a flowchart schematically showing processing at the start of use of the vehicle 26 in the present embodiment. Of the steps in FIG. 12, step S51 on the vehicle 26 side is executed by the card reader 84 and the calculation unit 74, steps S52, S57, and S60 are executed by the calculation unit 74, and step S56 is executed by the calculation unit 74 and the lock. The mechanism 78 executes. Steps S53, S54, S55, S58, and S59 of the management server 28 are executed by the calculation unit 94 (reservation management unit 104).

  In step S <b> 51, the vehicle 26 determines whether or not the authentication information Iid has been acquired from the card 82 of the customer C held over the card reader 84 provided below the rear window of the vehicle 26. When the authentication information Iid is not acquired (S51: NO), the vehicle 26 repeats step S51 every predetermined period. When the authentication information Iid is acquired (S51: YES), the vehicle 26 transmits the authentication information Iid to the management server 28 in step S52.

  In step S53, the management server 28 searches the reservation DB 124 for the authentication information Iid and the parking lot ID received from the vehicle 26 and inquires the reservation information Ir. Specifically, the management server 28 determines whether or not there is reservation information Ir that matches the parking lot ID, the reservation time, and the authentication information Iid (reservation person).

  When there is such reservation information Ir (S54: YES), in step S55, the management server 28 transmits a use permission notification (or unlock command) permitting the use of the vehicle 26 to the vehicle 26. In step S56, the vehicle 26 that has received the use permission notification operates the lock mechanism 78 to unlock it.

  When unlocking is normally performed, the vehicle 26 transmits an unlock notification to the management server 28 in step S57. In step S58, the management server 28 that has received the unlock notification inputs the use start time to the reservation information Ir in the reservation DB 124 and updates the reservation DB 124. Note that step S58 may be performed together with step S55.

  Returning to step S54, if there is no reservation information Ir that matches the parking lot ID, the reservation time, and the authentication information Iid (reservant) (S54: NO), in step S59, the management server 28 gives an error ( That the corresponding reservation information Ir does not exist). Upon receiving the error notification, the customer terminal 22 displays an error on the display unit (input / output unit 52).

(A2-6. During use of vehicle 26 and at the end of use)
(A2-6-1. Overall flow)
FIG. 13 is a flowchart schematically showing processing during use of the vehicle 26 and at the end of use in the present embodiment. In FIG. 13, steps S71 to S74 of the vehicle 26 and steps S91 to S93 of the management server 28 will be described separately. The calculating part 74 performs step S71-S74 of the vehicle 26. FIG. Steps S91 and S92 of the management server 28 are executed by the vehicle management unit 106 of the calculation unit 94, and step S93 will be described later with reference to FIG.

In step S <b> 71, the vehicle 26 transmits the detection values (sensor values Mc) of the various sensors 80 to the management server 28. In step S72, the vehicle 26 determines whether the locking condition is satisfied. The locking conditions here include, for example, the following conditions (a) to (c).
(A) The engine of the vehicle 26 is stopped. (B) The key of the vehicle 26 is returned to the key box of the vehicle 26. (c) From the card 82 of the customer C held over the card reader 84. The acquired authentication information Iid (lending authentication information Iid2) corresponds to the vehicle 26 being used and the parking lot to be returned.

  For example, the following method is used to confirm that the rental authentication information Iid2 corresponds to the parking lot scheduled to be returned (in other words, the vehicle 26 is located in the parking lot scheduled to be returned). That is, the calculation unit 74 of the vehicle 26 detects the position (latitude and longitude) of the parking lot registered in the management server 28 and the current position detected by the current position detection device (for example, navigation device) mounted on the vehicle 26. Match position. And the calculating part 74 determines with the vehicle 26 being in the parking lot which is going to return, when both correspond, or when both distance is less than a predetermined distance threshold value.

  The location of the parking lot registered in the management server 28 may be acquired by the vehicle 26 communicating with the management server 28 at the time of return, or acquired in advance (for example, at the time of locking). . It is also possible to increase the accuracy of the determination by providing a predetermined marker at the parking position and detecting the marker with a vehicle-mounted camera.

  If the locking condition is not satisfied (S72: NO), the process returns to step S71. When the locking condition is satisfied (S72: YES), in step S73, the vehicle 26 locks by operating the lock mechanism 78. In step S <b> 74, the vehicle 26 transmits a notification (locking notification (or usage end notification)) notifying the management server 28 of locking, and ends the current process.

  In step S91, the management server 28 updates the vehicle DB 128 with the sensor value Mc received from the vehicle 26. Details of the sensor value Mc will be described later with reference to FIG. In step S <b> 92, the management server 28 determines whether a lock notification has been received from the vehicle 26.

  When the lock notification has not been received (S92: NO), the process returns to step S91. When the lock notification is received (S92: YES), in step S93, the management server 28 performs a process at the end of use. The process at the end of use will be described later with reference to FIG.

(A2-6-2. Details of vehicle monitoring screen 400)
FIG. 14 is a diagram showing an example of a vehicle monitoring screen 400 (hereinafter also referred to as “monitoring screen 400”) in the present embodiment. A monitoring screen 400 in FIG. 14 shows the operation state of each vehicle 26. The monitoring screen 400 includes a rental business entity display column 410 (hereinafter also referred to as “business entity display column 410”) and a vehicle operation status display column 412 (hereinafter also referred to as “operation status display column 412”). .

  The business entity display column 410 displays the name of the specific rental business entity EL that is the display target of the operation status display column 412. The operation status display column 412 displays current status information Ist indicating the operation status of each vehicle 26 managed by the specific rental business entity EL. Specifically, the operation status display field 412 includes a vehicle number (serial number), vehicle status, overuse, parking address, presence / absence of activation of a global positioning system sensor (GPS sensor), card reader 84 Start / stop, security start / stop, immobilizer start / stop, battery voltage Vbat, ignition switch position (OFF, ACC, ON), door open / close, key box lock status, fuel level, odometer, last use The current status information Ist includes the number of days since the start date and whether the vehicle inspection date is imminent.

(A2-6-3. Processing at the end of use)
FIG. 15 is a flowchart (detail of S93 in FIG. 13) schematically showing the process at the end of use in the present embodiment. 15, steps S101 and S102 are executed by the billing management unit 108 of the calculation unit 94, and step S103 is executed by the reservation management unit 104, the vehicle management unit 106, and the billing management unit 108 of the calculation unit 94. . Step S104 is executed by the business entity management unit 100, the customer management unit 102, and the billing management unit 108.

  In step S <b> 101, the management server 28 determines fee calculation information Ifc for calculating the cost Fch (hereinafter also referred to as “use cost Fch” or “billing cost Fch”) associated with the use of the vehicle 26.

  The charge calculation information Ifc includes, for example, the identification code of the lending business entity EL, the travel distance of the vehicle 26, the usage time, and the vehicle type. As described above, the travel distance of the vehicle 26 is transmitted from the vehicle 26 to the management server 28 (S71 in FIG. 13).

  The use time is the time from the use start time to the use end time. The use start time can be, for example, the time when the management server 28 receives the unlock notification from the vehicle 26 (S58 in FIG. 12) or the time when the use permission notification is transmitted to the vehicle 26 (S55). The use end time can be set, for example, as the time when the management server 28 receives a lock notification from the vehicle 26 (S92 in FIG. 13: YES).

  In step S102, the management server 28 calculates a usage fee Fch (billing information Ich) based on the confirmed fee calculation information Ifc and the fee information If in the billing DB 130.

  In step S103, the management server 28 updates the reservation DB 124, the vehicle DB 128, and the billing DB 130 to reflect the current usage. Specifically, regarding the reservation DB 124, the management server 28 (reservation management unit 104) registers the return date and time. Regarding the vehicle DB 128, the management server 28 (vehicle management unit 106) registers the state when the vehicle 26 is returned (for example, travel distance, remaining amount of energy for driving the vehicle). Regarding the billing DB 130, the management server 28 (billing management unit 108) registers a charge billing amount F, a use start date / time, a return date / time, etc. associated with the current use.

  In step S104, the management server 28 transmits the use result to the lending entity EL, the customer C and the entity terminal 20 of the settlement entity ES, the customer terminal 22 and the settlement server 30 related to the current use.

  Specifically, the management server 28 (enterprise management unit 100) sends a use completion report of the vehicle 26 (including the return date and time, the travel distance, and the charge amount F) to the entity terminal 20, for example, e-mail. Send in the format. The business entity terminal 20 (calculation unit 44) that has received the information displays the information on the display device (input / output unit 42).

  In addition, the management server 28 (the billing management unit 108) gives a thank-you letter for using the vehicle 26, the use date and distance of the vehicle 26, and the charge amount calculated as the use result of the vehicle 26. F is transmitted to the customer terminal 22. The customer terminal 22 (calculation unit 54) that has received the information displays the information on the display device (input / output unit 52).

  Furthermore, the management server 28 (the billing management unit 108) transmits the charge billing amount F and the usage date to the settlement server 30. The settlement server 30 (calculation unit 144) that has received these pieces of information executes billing processing for the customer C and payment processing for the lending business entity EL.

  The billing process is a process of billing each customer C for the sum of the charge billing amount F every month. The payment process is a process of paying the total usage charge amount F collected from the customer C to each lending business unit EL every month.

(A2-7. Maintenance order)
FIG. 16 is a flowchart schematically showing processing at the time of maintenance ordering from the business entity terminal 20 to the maintenance server 32 in the present embodiment. Of the steps in FIG. 16, the calculation unit 44 executes steps S111, S113, and S115 of the business entity terminal 20. The calculation unit 164 executes steps S112, S114, S116, and S117 of the maintenance server 32. Step S118 of the management server 28 is executed by the maintenance management unit 110 of the calculation unit 94.

  In step S <b> 111, the user of the business entity terminal 20 accesses the maintenance server 32 via the business entity terminal 20. In other words, the business entity terminal 20 accesses the website of the maintenance server 32 in accordance with a user operation input. In step S <b> 112, the maintenance server 32 transmits information (ordering screen information) on a screen (ordering screen) for placing an order for maintenance in response to an operation input from the business entity terminal 20.

  In step S <b> 113, the user inputs ordering information Io on the ordering screen and transmits it to the maintenance server 32. In other words, the business entity terminal 20 displays the order screen on the display device (input / output unit 42) based on the order screen information from the maintenance server 32. Then, the business entity terminal 20 displays the order information Io according to the user input on the display device, and when the user selects the transmission button in the display device, the input order information Io is sent to the maintenance server 32. To send.

  The order information Io here includes, for example, the vehicle type, vehicle number and color of the vehicle 26 to be maintained, and the delivery date of maintenance.

  When placing an order for maintenance, the maintenance server 32 first transmits login screen information to the business entity terminal 20 and requests input of a login ID and a password. Then, the maintenance order is permitted only when the authentication of the lending entity EL is successful by the login ID and the password.

  In step S <b> 114, the maintenance server 32 transmits information on a confirmation screen (order confirmation screen) for confirming the order information Io received from the business entity terminal 20 to the business entity terminal 20.

  In step S115, the user confirms the contents of the order confirmation screen and then presses a confirmation button. In other words, the business entity terminal 20 displays the order confirmation screen on the display device (input / output unit 42) based on the order confirmation screen information from the maintenance server 32. When the user selects a confirmation button in the display device, the business entity terminal 20 transmits a notification (order information confirmation notification) that the input order information Io has been confirmed to the maintenance server 32. .

  In step S116, when receiving the order information confirmation notification from the business entity terminal 20, the maintenance server 32 registers the order information Io in the maintenance DB 170. In step S117, the maintenance server 32 notifies the management server 28 of the order information Io.

  In step S118, the management server 28 updates the maintenance DB 132 based on the received order information Io.

  Note that the processing of FIG. 16 can also be performed by writing, FAX, or telephone without communication between the business entity terminal 20 and the maintenance server 32. In that case, the maintenance business entity EMC registers the order information Io in the maintenance DB 170. The same applies to communication between the maintenance server 32 and the management server 28.

(A2-8. At the time of data inquiry from the entity terminal 20)
FIG. 17 is a flowchart schematically showing processing at the time of data inquiry from the business entity terminal 20 to the management server 28 in the present embodiment. Of the steps in FIG. 17, steps S121, S123, S126 to S128, S130, and S132 of the business entity terminal 20 are executed by the calculation unit 44. The reservation management unit 104 of the calculation unit 74 executes steps S122, S124, S125, S129, and S131 of the management server 28.

  In step S <b> 121, the user of the business entity terminal 20 accesses the management server 28 via the business entity terminal 20. In other words, the business entity terminal 20 accesses the website of the management server 28 in response to a user operation input.

  In step S <b> 122, the management server 28 transmits login screen information in response to an operation input from the business entity terminal 20. The login screen includes an input field for login information (login ID and password).

  In step S123, the user inputs login information Ilg on the login screen and transmits it to the management server 28. In other words, the business entity terminal 20 displays the input screen on the display device (input / output unit 42) based on the login screen information from the management server 28. The business entity terminal 20 displays the login information Ilg according to the user's input on the display device (input / output unit 42), and when the user selects the send button in the display device, the input login information Ilg Is transmitted to the management server 28.

  In step S <b> 124, the management server 28 determines whether or not authentication has been established based on the login information Ilg received from the business entity terminal 20. When authentication is established (S124: YES), in step S125, the management server 28 provides information on a data inquiry screen (not shown) corresponding to the login information Ilg (rental entity ID) (hereinafter referred to as “data inquiry screen information Idr”). Is transmitted to the business entity terminal 20.

  In step S126, the entity terminal 20 displays a data inquiry screen based on the received data inquiry screen information Idr. For example, on the data inquiry screen, reservation information Ir, current information Ist (FIG. 14), and charge information F of the vehicle 26 managed by the lending entity EL can be inquired. Furthermore, customer information Ic related to the use of the vehicle 26 of the lending business entity EL can be inquired. Thereby, the lending business entity EL can easily check various information managed by itself.

  In step S127, the business entity terminal 20 determines whether or not the user has requested to switch the data inquiry screen. When there is a switching request (S127: YES), the business entity terminal 20 sends the switching request to the management server 28 in step S128. The management server 28 that has received the switching request from the business entity terminal 20 transmits data inquiry screen information Idr corresponding to the lending business entity ID to the business entity terminal 20 in response to the switching request in step S129. In this case, the process proceeds to step S126.

  Returning to step S127, when there is no switching request (S127: NO), the entity terminal 20 determines whether or not to end the display of the data inquiry screen in step S130. This determination is made based on, for example, whether or not there is a logout request from the user. When the display of the data inquiry screen is not terminated (S130: NO), the process returns to step S127. When the display of the data inquiry screen is terminated (S130: YES), the current process is terminated.

  Returning to step S124, if the authentication is not established (S124: NO), the management server 28 transmits an error message to the business entity terminal 20 in step S131. Receiving this, the business entity terminal 20 displays an error message in step S132.

(A2-9. At the time of data inquiry from the maintenance server 32)
FIG. 18 is a flowchart schematically showing processing at the time of data inquiry from the maintenance server 32 to the management server 28 in the present embodiment. 18, the operation unit 164 executes steps S141, S143, S146 to S148, S150, and S152 of the maintenance server 32. Steps S142, S144, S145, S149, and S151 of the management server 28 are executed by the maintenance management unit 110 of the calculation unit 74.

  Steps S141 to S152 in FIG. 18 are basically the same as steps S121 to S132 in FIG. However, in the case of FIG. 18, in steps S145 and S149, on the data inquiry screen provided from the management server 28, it is possible to inquire the reservation information Ir of the vehicle 26 that the maintenance business entity EMC has performed or has performed.

[A3. Effects in this embodiment]
According to the present embodiment as described above, the management server 28 collectively manages reservations and returns of the vehicles 26 managed by the plurality of rental business entities EL (FIGS. 5, 6, 12, 13, and 13). FIG. 15). For this reason, the management server 28 collectively manages the processing performed on the plurality of business entity terminals 20, thereby reducing the calculation load on the plurality of business entity terminals 20 and managing the management server 28. However, lending management of the vehicles 26 of each lending business entity EL can be collectively managed.

  Accordingly, each lending business entity EL easily concentrates on a business specialized in a business part (core part) that actually handles the vehicle 26 such as provision and maintenance of the vehicle 26 managed by itself. In other words, each lending entity EL can leave the reservation and return (peripheral part) of the vehicle 26 managed by the lending entity EL to the management entity EM and focus on the business portion that lends the vehicle 26 as an asset and obtains a fee. it can.

  Therefore, each lending entity EL maintains its own business management environment including setting its own lending agreements, and even if the number of vehicles 26 is small, the vehicle lending business has reduced the cost of business support. Is easy to deploy. For example, each rental business EL can easily develop a business as a small-scale franchise such as using a parking lot of a convenience store.

  In addition, the management entity EM handles all the vehicles 26 from each rental entity EL, thereby reducing the management cost per unit due to the increase in the number of units and the scalability of the service, and reducing the system usage fee. It becomes possible to ensure stably.

  In the present embodiment, the management server 28 includes a billing DB 130 (charge database) that stores a rental fee for the vehicle 26 set for each of a plurality of rental entities EL and for each usage time and travel distance of the vehicle 26 (FIG. 1). ). The computing unit 94 (server control device) of the management server 28 acquires the usage time and travel distance of the vehicle 26 in one rental from the vehicle 26 (S101 in FIG. 15). Then, the computing unit 94 calculates a rental fee based on the acquired usage time and travel distance and the rental entity EL (in other words, based on the fee information If for each rental entity EL) (S102).

  Thereby, it becomes possible to set individual charges for each lending business entity EL. As a result, each lending entity EL can set a lending fee reflecting the regional characteristics and management philosophy of each lending entity EL, taking advantage of its uniqueness without being influenced by other lending entities EL Business can be promoted.

  In the present embodiment, the vehicle rental system 10 includes a settlement server 30 that settles a rental fee (FIG. 1). The computing unit 94 (server control device) of the management server 28 notifies the settlement server 30 of the rental fee and the customer C and the rental business entity EL corresponding to the rental fee (S104 in FIG. 15). The settlement server 30 performs billing processing for the customer C and payment processing for the lending business entity EL based on the lending fee. As a result, the management server 28 itself can omit the billing process for the customer C and the billing process for the lending business entity EL. In other words, reservation management and billing / payment management can be separated. Thereby, the configuration of the management server 28 can be simplified.

  In this embodiment, the management server 28 includes a customer DB 122 that collectively manages customer information Ic including the login ID and password (authentication information) of the customer C of the management entity EM that manages the management server 28 (FIG. 1). . When the computing unit 94 (server control device) of the management server 28 accesses the management server 28 from the customer terminal 22 (S31 in FIG. 5), the authentication based on the login ID and password of the customer C is successful. As a condition, the reservation screen 200 is displayed on the customer terminal 22 (S32, S33).

  Thereby, the management server 28 permits the rental of the vehicle 26 only to the customer C who has been successfully authenticated. In other words, since the management of the customer C is performed by the management server 28 (management business entity EM), the business entity terminal 20 (lending business entity EL) can omit the management of the customer C. For this reason, it is possible to further reduce the calculation load on the business entity terminal 20. Further, from the viewpoint of the customer C, the customer information Ic that can be grasped in each lending business entity EL can be limited to the use record of the vehicle 26 that the lending business entity EL has, and the use record is other lending. It becomes possible to suppress the leakage of personal information such as leakage to the business entity EL. As a result, the lending business entity EL can concentrate on the business part (core part) that actually handles the vehicle 26.

  In the present embodiment, the customer DB 122 stores personal identification information stored in an IC (storage medium) embedded in a card 82 (card-type license) as an IC-attached license as rental-time authentication information Iid2. The vehicle rental system 10 includes a card reader 84 that is provided in the vehicle 26 itself and reads personal identification information from a card 82 (FIG. 1). The computing unit 94 (server control device) of the management server 28 confirms that the personal identification information of the customer C in the rental reservation registered in the reservation DB 124 matches the personal identification information read by the card reader 84. A condition for permitting the rental is set (S54 in FIG. 12).

  Thereby, the customer C can receive the rental of the vehicle 26 by causing the card reader 84 to read the personal identification information in the card 82. Therefore, it is not necessary to create a special membership card or carry it, and the convenience of the customer C can be improved.

  In the present embodiment, the vehicle rental system 10 includes a maintenance server 32 that communicates with each of the plurality of business entity terminals 20 and the management server 28 via the network 34 and manages maintenance of the vehicles 26 of the plurality of rental business entities EL. (FIG. 1). When receiving the maintenance order from the business entity terminal 20, the maintenance server 32 transmits the order information Io to the management server 28 (S117 in FIG. 16). When the management server 28 receives an inquiry about the reservation status of the maintenance target vehicle 26 from the maintenance server 32, the management server 28 notifies the reservation status of the maintenance target vehicle 26 (S145 and S149 in FIG. 18).

  Thereby, even when the reservation management of the vehicles 26 of the plurality of rental business entities EL is collectively performed in the management server 28, the maintenance business entity IME using the maintenance server 32 may confirm the reservation status of the vehicle 26 to be maintained. It becomes possible.

  According to the present embodiment, when the management server 28 receives an inquiry about the reservation status from the entity terminal 20 of a specific lending entity EL, the entity terminal 20 of the specific lending entity EL has a specific Only the reservation status of the vehicle 26 corresponding to the rental entity EL is displayed (S125, S129 in FIG. 17). For this reason, even when reservations for the vehicles 26 of a plurality of lending entities EL are managed together in the management server 28, the reservation status regarding the vehicles 26 of other lending entities EL leaks to the specific lending entity EL. Can be prevented.

B. Modifications It should be noted that the present invention is not limited to the above-described embodiment, and it is needless to say that various configurations can be adopted based on the description of the present specification. For example, the following configuration can be adopted.

[B1. Applicable to]
In the above embodiment, the system 10 is used for the vehicle 26. However, the system 10 is not limited thereto, and may be used for other mobile bodies (airplanes, ships, helicopters, etc.), for example. Alternatively, it can be used for other apparatuses or devices (manufacturing apparatus, measuring instrument, portable terminal, etc.).

[B2. Vehicle 26]
In the above embodiment, the card reader 84 is provided in the vehicle 26 (FIG. 1). However, for example, from the viewpoint of reading information on the card 82, the present invention is not limited to this. For example, the card reader 84 can be provided in a parking lot terminal (not shown) disposed in a parking lot where the vehicle 26 is parked. In addition, when the parking lot terminal as described above is provided, a part of communication between the vehicle 26 and the management server 28 (for example, notification of usage time and / or travel distance when returning the vehicle 26), You may go via a parking lot terminal.

[B3. Management server 28]
In the above embodiment, the business entity management unit 100, the customer management unit 102, the reservation management unit 104, the vehicle management unit 106, the billing management unit 108, and the maintenance management unit 110 are included in one management server 28 (FIG. 1). However, for example, if attention is paid to the functions of the respective management units 100, 102, 104, 106, 108, 110, the present invention is not limited to this. For example, it is possible to provide one or more other servers that execute one or more functions of the management units 100, 102, 104, 106, 108, 110.

[B4. Payment server 30]
In the above embodiment, the payment server 30 is provided separately from the management server 28 (FIG. 1), but the function of the payment server 30 can also be provided in the management server 28. Further, for example, instead of the billing process in the settlement server 30, it is possible to provide a settlement machine in the parking lot and collect the billing cost Fch immediately after the use of the vehicle 26 is finished.

[B5. Maintenance server 32]
In the above embodiment, the maintenance server 32 is provided (FIG. 1), but a configuration in which the maintenance server 32 is omitted is also possible.

  In the above embodiment, the main body that inquires the management server 28 for the reservation information Ir related to the maintenance target vehicle 26 is the maintenance server 32 (FIG. 18). However, for example, from the viewpoint of referring to the management server 28 for the reservation information Ir regarding the vehicle 26 to be maintained, the present invention is not limited to this. For example, in addition to the maintenance server 32, one or a plurality of maintenance terminals (not shown) may be provided, and reservation information Ir regarding the maintenance target vehicle 26 may be inquired from the maintenance terminal to the management server 28.

[B6. At the time of reservation (Figures 5 and 6)]
In the above embodiment, the credit is requested from the management server 28 to the settlement server 30 when the vehicle 26 is reserved (S36 in FIG. 6). However, for example, from the viewpoint of performing reservation management of the vehicles 26 of a plurality of lending business entities EL with the management server 28, the present invention is not limited to this. For example, the reservation of the vehicle 26 may be terminated without a request for credit from the management server 28 to the settlement server 30.

[B7. When the vehicle 26 is used (FIGS. 12 to 14)]
In the above embodiment, during use of the vehicle 26, the detection values (sensor value Mc) of the various sensors 80 are transmitted from the vehicle 26 to the management server 28 (S71 in FIG. 13, FIG. 14). However, for example, from the viewpoint of performing reservation management of the vehicles 26 of a plurality of lending business entities EL with the management server 28, the present invention is not limited to this. For example, a configuration in which the sensor value Mc is not transmitted while the vehicle 26 is being used (or during travel) is possible. In this case, for example, the sensor value Mc can be transmitted when the vehicle 26 stops.

[B8. When the use of the vehicle 26 ends (FIG. 15)]
In the above embodiment, the billing cost Fch is calculated based on the identification code of the lending business entity EL, the travel distance of the vehicle 26, the usage time, and the vehicle type (S102 in FIG. 15). However, for example, from the viewpoint of performing reservation management of the vehicles 26 of a plurality of lending business entities EL with the management server 28, the present invention is not limited to this. For example, the billing cost Fch may be calculated based on the identification code of the lending business entity EL, the travel distance of the vehicle 26, and the usage time. Alternatively, it is possible to calculate the billing cost Fch based on the combination of the identification code of the lending entity EL and the usage time of the vehicle 26 or the combination of the identification code of the lending entity EL and the travel distance of the vehicle 26. Alternatively, it is possible to calculate the fee based on the travel distance, usage time, and vehicle type of the vehicle 26 without using the individual fee for each rental business entity EL.

[B9. Data inquiry (Fig. 17, Fig. 18)]
In the above embodiment, the data inquiry to the management server 28 is possible from the business entity terminal 20 and the maintenance server 32 (FIGS. 17 and 18). However, for example, from the viewpoint of performing reservation management of the vehicles 26 of a plurality of lending business entities EL with the management server 28, the present invention is not limited to this. For example, a configuration in which data inquiry from one or both of the business entity terminal 20 and the maintenance server 32 to the management server 28 is not possible is also possible. Alternatively, in addition to or instead of the business entity terminal 20 and / or the maintenance server 32, the customer terminal 22 may be able to inquire data regarding the customer C from the management server 28.

DESCRIPTION OF SYMBOLS 10 ... Vehicle rental system 20 ... Business entity terminal 22 ... Customer terminal 26 ... Vehicle 28 ... Management server 30 ... Payment server 32 ... Maintenance server 34 ... Communication network 82 ... Authentication card (card type license) 84 ... Card reader 94 ... Management Server computing unit (server controller)
122 ... Customer DB 124 ... Reservation DB
126 ... Terms and Conditions DB
130 ... Billing DB (charge database)
200, 200a to 200d ... Reservation screen C ... Customer EL ... Lending entity EM ... Management entity Ic ... Customer information Iid1 ... Reservation authentication information Iid2 ... Lending authentication information Io ... Ordering information

Claims (9)

A vehicle rental system for renting a plurality of vehicles,
The vehicle rental system includes:
A plurality of business entity terminals used by each of a plurality of rental business entities that manage the vehicle for rental;
A management server that communicates with each of the plurality of business entity terminals via a network and collectively manages lending and returning of the vehicles of the plurality of rental business entities,
The management server
A reservation database that collectively manages reservations and returns of the vehicles that each of the plurality of lending entities individually has,
A clause database storing individual loan agreement data for each of the plurality of loan entities;
A server control device that manages lending of the vehicles of each of the plurality of lending entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle of the plurality of rental entities is displayed on the customer terminal according to an operation on a customer terminal by a customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The vehicle lending system is characterized in that the lending reservation is permitted on condition that an operation input to the customer terminal to agree to the contents of the lending agreement data is received. In the vehicle rental system according to claim 1,
The management server includes a fee database that stores a rental fee of the vehicle set for each of the plurality of rental entities and for each usage time and mileage of the vehicle,
The server control device
The use time and travel distance of the vehicle in one rental are acquired from the vehicle or from a parking lot terminal arranged in a parking lot used by the vehicle,
The vehicle rental system, wherein the rental fee is calculated based on the acquired usage time and the travel distance, and the rental business entity that manages the vehicle or the vehicle itself. In the vehicle rental system according to claim 2,
The vehicle rental system includes a settlement server that settles the rental fee,
The server control device notifies the payment server of the lending fee and the customer and the lending entity corresponding to the lending fee,
The payment server performs a billing process for the customer and a payment process for the lending entity based on the lending fee. The vehicle rental system according to any one of claims 1 to 3,
The management server comprises a customer database that collectively manages customer information including authentication information for reservation of the customer of the management entity that manages the management server,
The server control device displays the reservation screen on the customer terminal on the condition that the authentication based on the reservation authentication information of the customer is successful when the management server is accessed from the customer terminal. A vehicle rental system characterized by In the vehicle rental system according to claim 4,
The customer database stores personal identification information stored in a storage medium embedded in a card type license as authentication information at the time of lending,
The vehicle lending system is provided in a parking lot where the vehicle itself or the vehicle parks, and includes a card reader that reads the personal identification information from the card type license,
The server control device, according to the condition for permitting rental of the vehicle, that the personal identification information of the customer in the rental reservation registered in the reservation database and the personal identification information read by the card reader match. A vehicle rental system characterized by In the vehicle rental system according to any one of claims 1 to 5,
The vehicle lending system includes a maintenance server that communicates with each of the plurality of business entity terminals and the management server via the network, and manages maintenance of the vehicles of the plurality of lending business entities,
When the maintenance server receives an order for maintenance from the business entity terminal, the maintenance server transmits the order information to the management server;
When the management server receives an inquiry about the reservation status of the maintenance target vehicle from the maintenance server or from a maintenance terminal connected to the maintenance server, the management server notifies the reservation status of the maintenance target vehicle. Lending system. A vehicle lending method using a vehicle lending system for lending a plurality of vehicles,
The vehicle rental system includes:
A plurality of business entity terminals used by each of a plurality of rental business entities that manage the vehicle for rental;
A management server that communicates with each of the plurality of business entity terminals via a network and collectively manages lending and returning of the vehicles of the plurality of rental business entities,
The management server
A reservation database that collectively manages reservations and returns of the vehicles that each of the plurality of lending entities individually has,
A clause database storing individual loan agreement data for each of the plurality of loan entities;
A server control device that manages lending of the vehicles of each of the plurality of lending entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle of the plurality of rental entities is displayed on the customer terminal according to an operation on a customer terminal by a customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The vehicle lending method is characterized in that the lending reservation is permitted on condition that an operation input to the customer terminal to agree to the contents of the lending contract data is received. A vehicle lending reservation management server that communicates with each of a plurality of business entity terminals used by a plurality of lending business entities that manage lending vehicles via a network and centrally manages lending reservations for the vehicles. And
The management server
Reservation database for managing reservation and return of the vehicle that each of the lending entities individually has,
A contract database storing individual loan contract data for each of the lending entities;
A server control device that manages lending of the vehicle of each of the lending business entities,
The server control device
A reservation screen for accepting a rental reservation for the vehicle is displayed on the customer terminal according to the operation of the customer terminal by the customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, the server control device includes:
When accepting the lending reservation, the lending contract data corresponding to the lending entity that manages the vehicle to be lent is displayed on the customer terminal,
The lending reservation is permitted on condition that the customer terminal has been operated to agree to the contents of the lending agreement data. A vehicle lending reservation management server that communicates with each of a plurality of business entity terminals used by a plurality of lending business entities that manage lending vehicles via a network and centrally manages lending reservations for the vehicles. And
The management server
A reservation database for managing reservation and return of the vehicle of each of the lending entities;
A server control device that manages lending of the vehicle that each of the lending entities individually has, and
The server control device
A reservation screen for accepting a rental reservation for the vehicle is displayed on the customer terminal according to the operation of the customer terminal by the customer,
Accepting the lending reservation according to the operation at the customer terminal and registering it in the reservation database,
Furthermore, when the server control device receives an inquiry about a reservation status from an entity terminal of a specific lending entity, the server control device displays the reservation status of only the vehicle corresponding to the specific lending entity. Management server characterized by being displayed on any business terminal.

Images