Information processing method, information processing program, information processing method, condition setting program, vehicle rental program, refund setting program, and application program
The information processing method addresses unfair fees by calculating vehicle rental costs based on actual mileage and offering rewards for visiting desired locations, enhancing financial transactions and promoting vehicle usage.
Patent Information
- Application Number
- JP2023087287
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-26
- Publication Date
- 2024-12-06
AI Technical Summary
Existing systems for vehicle usage and rental do not effectively calculate fees based on actual mileage, leading to unreasonable additional payments when users drive less than expected, and lack methods for calculating returns when visiting desired locations.
An information processing method that calculates fees based on vehicle usage period and mileage, allowing users to rent vehicles and receive rewards for visiting specified locations, using a system that includes a server, user terminals, and communication devices to manage vehicle usage and location data.
Enables fair fee calculation for vehicle rentals and rewards for visiting desired locations, optimizing financial transactions and encouraging vehicle usage based on actual mileage and location visits.
Smart Images

Figure 2024170240000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing method for outputting a fee to be paid by a user of a vehicle when the vehicle is used. [Background technology]
[0002] In recent years, the selling price of automobiles has been rising. Residual value automobile credits are being used to reduce the financial burden of purchasing an automobile. Residual value automobile credits do not cover the full vehicle price, but rather assume that the automobile will be driven for a certain amount of time and distance, and the residual value of the automobile is estimated in advance. The principal to be paid is the amount obtained by subtracting the residual value from the principal. However, if the actual distance driven by the residual value automobile credit user is less than the estimated distance, the user will have to pay an extra residual amount equivalent to the difference in distance, which is unreasonable.
[0003] With the advancement of IT technology, it has become easier for individuals to contact each other, and people are now lending and borrowing things using IT technology. Patent Document 1 proposes a system for supporting the shared use of objects (vehicles, residences, etc.). However, the system described in Patent Document 1 does not mention a method for calculating the amount of payment from the lessee to the lessor. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent No. 6481076 Summary of the Invention [Problem to be solved by the invention]
[0005] The present invention has been made in consideration of such circumstances. A first object of the present invention is to provide an information processing method, etc., that calculates the fee that a user will receive from another person when the user lends the vehicle to the other person. A second object of the present invention is to provide an information processing method, etc., that calculates the amount of rebate that a user will receive when the user uses the vehicle to visit a place requested by the other person. [Means for solving the problem]
[0006] In one aspect of the information processing method of the present application, a computer executes a process to obtain a fee to be paid by a vehicle user for the vehicle, calculated from a basic fee determined based on the period of vehicle usage and a pay-per-use fee determined based on the distance traveled by the vehicle within a specified period, calculate the rental fee obtained by renting out the vehicle or the rebate amount obtained when using the vehicle to travel to a specified attraction location as the fee to be paid by the vehicle user for the vehicle, and output the fee to be paid by the vehicle user and the fee to be paid by the vehicle user. Effect of the Invention
[0007] In one aspect of the present application, when a user lends a car to another person, it is possible to calculate the fee to be paid by the user from the other person. Also, in one aspect of the present application, when the user uses the car to visit a place requested by the other person, it is possible to calculate the amount of rebate to be received for the visit. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an example of the configuration of an automobile trading system. [Diagram 2] FIG. 2 is a block diagram showing an example of a hardware configuration of a server. [Diagram 3] 2 is a block diagram showing an example of a hardware configuration of a user terminal; [Figure 4] 2 is a block diagram showing an example of a hardware configuration of an owner terminal; [Diagram 5] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a communication device. [Figure 6] 4 is a block diagram showing an example of a hardware configuration of a lessee terminal. FIG. [Figure 7] 4 is a block diagram showing an example of a hardware configuration of a provider terminal; [Figure 8] FIG. 13 is an explanatory diagram illustrating an example of a customer DB. [Figure 9] FIG. 11 is an explanatory diagram showing an example of a contract DB. [Figure 10] FIG. 11 is an explanatory diagram illustrating an example of a device DB. [Figure 11] FIG. 2 is an explanatory diagram showing an example of a position information DB. [Figure 12] FIG. 11 is an explanatory diagram showing an example of a mileage DB. [Figure 13] FIG. 2 is an explanatory diagram showing an example of a driving performance DB; [Figure 14] FIG. 13 is an explanatory diagram showing an example of a billing record DB. [Figure 15] FIG. 2 is an explanatory diagram showing an example of a lending condition DB; [Figure 16] FIG. 11 is an explanatory diagram showing an example of a reservation DB. [Figure 17] FIG. 13 is an explanatory diagram showing an example of a loan record DB. [Figure 18] 13 is a flowchart illustrating an example of a procedure for position information acquisition processing. [Figure 19] 10 is a flowchart showing an example of a procedure for a travel distance calculation process. [Figure 20] 13 is a flowchart showing an example of a procedure for registering lending conditions; [Figure 21] 13 is a flowchart showing an example of a procedure for registering lending conditions; [Figure 22] 13 is a flowchart showing an example of a procedure for reservation processing. [Figure 23] 13 is a flowchart showing an example of a procedure for reservation confirmation processing. [Figure 24] 13 is a flowchart showing an example of a procedure for starting lending. [Diagram 25] 13 is a flowchart showing an example of a procedure for ending lending. [Figure 26] 13 is a flowchart showing an example of a procedure for rent calculation processing. [Figure 27] FIG. 13 is an explanatory diagram showing an example of a fee setting screen. [Figure 28] FIG. 13 is an explanatory diagram showing an example of a schedule registration screen. [Figure 29] FIG. 13 is an explanatory diagram showing an example of a time period setting sub-screen. [Diagram 30] FIG. 13 is an explanatory diagram showing an example of a lending / delivery registration screen. [Diagram 31] FIG. 13 is an explanatory diagram showing an example of a rental registration information screen. [Diagram 32] FIG. 13 is an explanatory diagram showing an example of a reservation screen. [Diagram 33] FIG. 13 is an explanatory diagram showing an example of a reservation status screen. [Diagram 34] FIG. 13 is an explanatory diagram showing an example of a provider DB. [Diagram 35] FIG. 13 is an explanatory diagram showing an example of an attraction DB. [Diagram 36] FIG. 11 is an explanatory diagram showing an example of an application DB. [Figure 37] 13 is a flowchart showing an example of a procedure for invitation registration processing. [Figure 38] 13 is a flowchart showing an example of a procedure for application processing. [Figure 39] 13 is a flowchart showing an example of a procedure for reward claim processing. [Diagram 40] 13 is a flowchart showing an example of a procedure for a reward granting process. [Diagram 41] FIG. 13 is an explanatory diagram showing an example of an invitation registration screen. [Diagram 42] FIG. 13 is an explanatory diagram showing an example of an application screen. [Diagram 43] 13 is a flowchart showing an example of a procedure for billing processing. [Diagram 44] FIG. 13 is an explanatory diagram showing an example of a usage fee display screen. [Diagram 45] FIG. 13 is an explanatory diagram showing another example of the usage fee display screen. [Figure 46] FIG. 13 is an explanatory diagram showing another example of the usage fee display screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] (Embodiment 1) Hereinafter, an embodiment will be described with reference to the drawings. Fig. 1 is an explanatory diagram showing an example of the configuration of an automobile trading system. The automobile trading system 100 includes a server 1, a user terminal 2, an owner terminal 3, a communication device 4, a lessee terminal 5, and a provider terminal 6. In this embodiment, the provider terminal 6 is not a required component.
[0010] The server 1 is an information processing device that handles various information processes related to the operation of the automobile trading system 100. The server 1 is composed of a server computer, a workstation, a PC (Personal Computer), etc. The server 1 may also be composed of a multicomputer or cluster system consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of the server 1 may be realized by a cloud service.
[0011] 2 is a block diagram showing an example of the hardware configuration of the server 1. The server 1 includes a control unit 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a reading unit 15. Each component is connected to a bus B.
[0012] The control unit 11 has one or more arithmetic processing devices such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), a GPU (Graphics Processing Unit), etc. The control unit 11 reads out and executes a control program 1P (program, program product) stored in the auxiliary storage unit 13, thereby performing various information processing, control processing, etc., handled by the server 1, and realizing various functional units.
[0013] The main memory unit 12 is a static random access memory (SRAM), a dynamic random access memory (DRAM), a flash memory, etc. The main memory unit 12 mainly temporarily stores data necessary for the control unit 11 to execute arithmetic processing.
[0014] The auxiliary storage unit 13 is a hard disk or a solid state drive (SSD), etc., and stores the control program 1P and various DBs (databases) necessary for the control unit 11 to execute processing. The auxiliary storage unit 13 stores a customer DB 131, a contract DB 132, a device DB 133, a location information DB 134, a mileage DB 135, a driving record DB 136, a billing record DB 137, a rental condition DB 138, a reservation DB 139, a rental record DB 13A, a provider DB 13B, an invitation DB 13C, and an application DB 13D. The auxiliary storage unit 13 may be an external storage device externally connected to the server 1. The various DBs, etc. stored in the auxiliary storage unit 13 may be stored in a database server or cloud storage different from the server 1.
[0015] The communication unit 14 communicates with the user terminal 2, the owner terminal 3, the communication device 4, the lessee terminal 5, and the provider terminal 6 via the network N. In addition, the control unit 11 may use the communication unit 14 to download the control program 1P from another computer via the network N or the like, and store it in the auxiliary storage unit 13.
[0016] The reading unit 15 reads the portable storage medium 1a including a CD (Compact Disc)-ROM and a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 15 and store it in the auxiliary storage unit 13. The control unit 11 may also read the control program 1P from the semiconductor memory 1b.
[0017] The user terminal 2 is a terminal used by a vehicle user who uses an automobile. In the automobile trading system 100, it is assumed that the vehicle user purchases an automobile through an auto loan, residual value credit, or the like, or rents an automobile under a lease contract. The user terminal 2 is composed of a smartphone, a tablet computer, a notebook computer, a PC, or the like. Hereinafter, a vehicle user is also simply referred to as a user. An automobile is also referred to as a vehicle.
[0018] 3 is a block diagram showing an example of the hardware configuration of a user terminal 2. The user terminal 2 includes a control unit 21, a main memory unit 22, an auxiliary memory unit 23, a communication unit 24, a display panel 25, an operation unit 26, and an imaging unit 27. Each component is connected by a bus B.
[0019] The control unit 21 has one or more arithmetic processing devices such as a CPU, an MPU, a GPU, etc. The control unit 21 provides various functions by reading and executing a control program 2P (program, program product) stored in the auxiliary storage unit 23.
[0020] The main memory unit 22 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 22 mainly temporarily stores data necessary for the control unit 21 to execute arithmetic processing.
[0021] The auxiliary storage unit 23 is a hard disk or an SSD, etc., and stores various data necessary for the control unit 21 to execute processing. The auxiliary storage unit 23 may be an external storage device externally connected to the user terminal 2. The various DBs, etc. stored in the auxiliary storage unit 23 may be stored in a database server or cloud storage.
[0022] The communication unit 24 communicates with the server 1 via the network N. In addition, the control unit 21 may use the communication unit 24 to download the control program 2P from another computer via the network N or the like, and store it in the auxiliary storage unit 23.
[0023] The display panel 25 can be configured with a liquid crystal panel or an organic EL (Electro Luminescence) display, etc. The operation unit 26 can be configured with, for example, a touch panel incorporated in the display panel 25, and allows the user to perform predetermined operations on the display panel 25. The operation unit 26 can also perform operations on a software keyboard displayed on the display panel 25. The operation unit 26 may also be a hardware keyboard, a mouse, etc.
[0024] The imaging unit 27 is, for example, a CCD camera or a CMOS camera, and obtains image data by photoelectrically converting an optical signal input via a CCD or a CMOS.
[0025] The owner terminal 3 is a terminal used by the owner of the vehicle. The owner of the vehicle may be a loan company, a credit company, a leasing company, etc. The operator of the vehicle trading system 100 may also be the owner. The owner terminal 3 is configured with a PC, a notebook computer, a tablet computer, a smartphone, etc.
[0026] 4 is a block diagram showing an example of the hardware configuration of the owner terminal 3. The owner terminal 3 includes a control unit 31, a main memory unit 32, an auxiliary memory unit 33, a communication unit 34, an input unit 35, and a display unit 36. Each component is connected by a bus B.
[0027] The control unit 31 has one or more arithmetic processing devices such as a CPU, an MPU, a GPU, etc. The control unit 31 provides various functions by reading and executing a control program 3P (program, program product) stored in the auxiliary storage unit 33.
[0028] The main memory unit 32 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 32 mainly temporarily stores data necessary for the control unit 31 to execute arithmetic processing.
[0029] The auxiliary storage unit 33 is a hard disk or an SSD, etc., and stores various data necessary for the control unit 31 to execute processing. The auxiliary storage unit 33 may be an external storage device externally connected to the owner terminal 3. The various DBs, etc. stored in the auxiliary storage unit 33 may be stored in a database server or cloud storage.
[0030] The communication unit 34 communicates with the server 1 via the network N. In addition, the control unit 31 may use the communication unit 34 to download the control program 3P from another computer via the network N or the like, and store it in the auxiliary storage unit 33.
[0031] The input unit 35 is a keyboard and a mouse. The display unit 36 includes a liquid crystal display panel or an organic EL (electro Luminescence) display panel. The display unit 36 displays user information and the like output by the server 1. The input unit 35 and the display unit 36 may be integrated to configure a touch panel display. The owner terminal 3 may display on an external display device.
[0032] The communication device 4 is a device installed in an automobile. The communication device 4 has a function of measuring its own position using a satellite positioning system or the like, and a function of transmitting the measured position to the server 1 via a mobile communication network. The communication device 4 is, for example, configured by a communication type drive recorder.
[0033] 5 is a block diagram showing an example of the hardware configuration of the communication device 4. The communication device 4 includes a control unit 41, a main memory unit 42, an auxiliary memory unit 43, a communication unit 44, a position acquisition unit 45, and an imaging unit 46. Each component is connected by a bus B.
[0034] The control unit 41 has one or more arithmetic processing units such as a CPU, an MPU, a GPU, etc. The control unit 41 controls the communication device 4 by reading and executing a control program 4P (program, program product) stored in the auxiliary storage unit 43.
[0035] The main memory unit 42 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 42 mainly temporarily stores data necessary for the control unit 41 to execute arithmetic processing.
[0036] The auxiliary storage unit 43 is an SD memory card or an SSD, etc., and stores various data necessary for the control unit 41 to execute processing. The auxiliary storage unit 43 also stores position information acquired by the position acquisition unit 45 and images acquired by the imaging unit 46.
[0037] The communication unit 44 communicates with the server 1 via the network N. The communication unit 44 includes a SIM (Subscriber Identity Module) card 441, and transmits location information and images to the server 1 using a mobile communication network.
[0038] The position acquisition unit 45 is configured with a GPS (Global Positioning System) receiver, etc. The position acquisition unit 45 receives radio waves from GPS satellites. The position acquisition unit 45 determines its own position based on the received satellite radio waves.
[0039] The imaging unit 46 is configured with, for example, a CCD camera, a CMOS camera, etc. The imaging unit 46 obtains image data by photoelectrically converting an optical signal input via the CCD or CMOS, etc.
[0040] The lessee terminal 5 is a terminal used by a person (renter) who rents a car by the hour from a user. The lessee terminal 5 is composed of a smartphone, tablet computer, notebook computer, PC, etc. When renting a car by the hour, the user becomes the lessor.
[0041] 6 is a block diagram showing an example of the hardware configuration of the lessee terminal. The lessee terminal 5 includes a control unit 51, a main memory unit 52, an auxiliary memory unit 53, a communication unit 54, a display panel 55, an operation unit 56, and an imaging unit 57. Each component is connected by a bus B. The main memory unit 52, the auxiliary memory unit 53, the communication unit 54, the display panel 55, the operation unit 56, and the imaging unit 57 are similar in configuration to the control unit 21, the main memory unit 22, the auxiliary memory unit 23, the communication unit 24, the display panel 25, the operation unit 26, and the imaging unit 27 of the user terminal 2, respectively, and therefore their explanations are omitted.
[0042] The provider terminal 6 is a terminal used by a corporation or public organization (attractor) that is engaged in activities to attract general consumers to designated facilities, tourist spots, etc. (attraction locations). The attractor uses the automobile trading system 100 to provide incentives such as money or points when a user or lessee visits the attraction location. The provider terminal 6 is composed of a PC, a laptop computer, a tablet computer, a smartphone, etc.
[0043] 7 is a block diagram showing an example of the hardware configuration of a provider terminal 6. The provider terminal 6 includes a control unit 61, a main memory unit 62, an auxiliary memory unit 63, a communication unit 64, an input unit 65, and a display unit 66. Each component is connected by a bus B. The control unit 61, the main memory unit 62, the auxiliary memory unit 63, the communication unit 64, the input unit 65, and the display unit 66 have the same configuration as the main memory unit 32, the auxiliary memory unit 33, the communication unit 34, the input unit 35, and the display unit 36 of the owner terminal 3, respectively, and therefore description thereof will be omitted.
[0044] Next, the usage fee collected from users in the automobile transaction system 100 will be described. The usage fee is a two-tiered system consisting of a monthly base fee and a metered fee. The base fee is fixed each month, and the metered fee is calculated based on the vehicle's monthly mileage. There are various methods that can be used to calculate the distance-based rate for the base fee and the metered fee. What is relevant to this case is that the usage fee is a two-tiered system consisting of a base fee and a metered fee. As for the method of calculating the distance-based rate for the base fee and the metered fee, it is not very relevant to this case, so only one calculation method will be described below using a specific example.
[0045] Here, we will explain how to calculate the basic fee and the distance-based metered fee for a fee plan entitled "3-year lease, unlimited ride up to 300km per month." In this fee plan, if the total monthly vehicle mileage is within 300km, the usage fee is the basic fee only. If the total monthly mileage exceeds 300km, the usage fee is the basic fee plus the metered fee calculated from the excess distance (in 1km increments) and the distance-based metered fee.
[0046] Vehicle residual value data is used to calculate the basic fee and distance cost. Residual value data is either the residual value or the residual value rate. Residual value is an abbreviation for remaining price. Residual value indicates the future value of a vehicle. For example, if the vehicle price at the start of the lease is 2 million yen and the vehicle price three years after the lease expires is 1 million yen, the residual value is 1 million yen and the residual value rate is 50%. Residual value is determined by the vehicle model, mileage, grade, body color, etc. Residual value and residual value rate are determined based on used car market trends. Alternatively, residual value data is obtained from a research company, etc.
[0047] For example, for a vehicle to be calculated, the residual value rate is calculated based on the current vehicle price and the residual value after three years assuming that the total mileage during the three-year lease period is 10,800km. 10,800km is the total mileage over three years assuming a total monthly mileage of 300km. Let's assume that the residual value rate is 85%. Let's also assume that the calculation base amount, which is the vehicle price at the start of the lease plus various expenses and profits, is 7.2 million yen.
[0048] If you define the basic fee as the calculation base amount x (1-residual value rate) ÷ (number of months of lease), then under the above conditions, it will be 30,000 yen. Note that the calculation method for the basic fee is just an example and is not limited to this.
[0049] The cost per kilometer is calculated based on two residual values with different total mileages. Assume that the residual value of a vehicle with a total mileage of 18,000km over three years is 180,000 yen less than the residual value of a vehicle with a total mileage of 10,800km. At this time, the decrease is converted to a per kilometer value. Here, the difference in the total mileage is 7,200km, so 180,000 yen ÷ 7,200km = 25 yen / km. Assuming that 5 yen is needed for various expenses and profits in addition to the 25 yen, the cost per kilometer is 30 yen.
[0050] Next, the databases used by the automobile transaction system 100 will be described. FIG. 8 is an explanatory diagram showing an example of a customer DB. The customer DB 131 stores information about customers. In this case, the customers are users or lessees. The customer DB 131 includes a customer ID column, a type column, a name column, a gender column, a date of birth column, and an address column. The customer ID column stores a customer ID that can uniquely identify a customer. The type column stores the type of customer, here a user or lessee. The name column stores the name of the customer. The gender column stores the gender of the customer. The date of birth column stores the date of birth of the customer. The address column stores the address of the customer. The customer DB may also store other personal information such as the customer's email address, occupation, hobbies, and annual income.
[0051] FIG. 9 is an explanatory diagram showing an example of the contract DB. The contract DB 132 stores information on the vehicle usage contract. The contract DB 132 includes a customer ID column, a vehicle ID column, a payment start month column, a payment end month column, a fee plan column, a monthly basic fee column, a distance unit price column, and a bonus payment column. The customer ID column stores the customer ID. The vehicle ID column stores the vehicle ID of the target vehicle for which the customer has a usage contract. The vehicle ID may be any ID that can uniquely identify each vehicle in the automobile transaction system 100. The vehicle ID may be issued independently, but the vehicle identification number (Vehicle Identification Number, abbreviated as VIN) defined by ISO3833 or the chassis number assigned by the Ministry of Land, Infrastructure, Transport and Tourism may also be used. The payment start month column stores the year and month when the user starts or has started paying the fee. The payment end month column stores the year and month when the user ends or has ended paying the fee. The fee plan column stores the name of the fee plan. The monthly basic fee column stores the basic fee per month. The distance unit price column stores the fee per unit distance used to calculate the pay-as-you-go fee. In this case, it is the fee per 1 km. The bonus payment column stores the payment month and amount when the usage fee is paid as a bonus.
[0052] 10 is an explanatory diagram showing an example of a device DB. The device DB 133 stores information about the communication device 4. The device DB 133 includes a vehicle ID column, a terminal management number column, an IMEI column, and a SIM column. The vehicle ID column stores the vehicle ID of the vehicle to which the communication device 4 is attached. The terminal management number column stores the management number of the communication device 4. The IMEI column stores the International Mobile Equipment Identifier. The SIM column stores the terminal serial number of the SIM card 441 included in the communication device 4.
[0053] FIG. 11 is an explanatory diagram showing an example of the location information DB. The location information DB 134 stores the location of the communication device 4, i.e., the location of the vehicle. The location information DB 134 includes an IMEI column, a SIM column, a trip start column, a trip end column, a time column, a latitude column, and a longitude column. The IMEI column stores the International Mobile Equipment Identity of the communication device 4. The SIM column stores the terminal serial number of the SIM card 441 included in the communication device 4. A flag is set in the Trip start column if the record corresponds to the start of a trip. A flag is set in the Trip end column if the record corresponds to the end of a trip. A trip is a set operation of a vehicle. The trip start point of a trip is the time when the engine starts, and the trip end point is the time when the engine stops. In FIG. 11, a check mark indicates that a flag is set. The time column stores the time when the position was observed. The latitude column stores the latitude indicating the position. The longitude column stores the longitude indicating the position.
[0054] FIG. 12 is an explanatory diagram showing an example of a mileage DB. The mileage DB 135 stores the mileage of each trip. The mileage DB 135 includes a vehicle ID column, an IMEI column, a start column, an end column, a trip column, and a mileage column. The vehicle ID column stores the vehicle ID. The IMEI column stores the IMEI assigned to the communication device 4. The start column stores the start date and time of the trip. The end column stores the end date and time of the trip. The trip column stores a sequence number. The mileage column stores the mileage of the trip. In the example of FIG. 12, the unit is meters (m). The mileage is calculated as follows. Based on the location information DB 134, the start point, end point, and passing points on the way are plotted on an electronic map having road network data, and a route from the start point to the end point is obtained by map matching technology. The distance of each road segment that constitutes the route is obtained from the attributes of the road network data. The obtained distances are added together to calculate the mileage.
[0055] FIG. 13 is an explanatory diagram showing an example of the driving record DB. The driving record DB 136 stores the total distance for each vehicle per month. The driving record DB 136 includes a vehicle ID column, an IMEI column, a year / month column, and a total distance column. The vehicle ID column stores the vehicle ID. The IMEI column stores the IMEI assigned to the communication device 4. The year / month column stores the year and month that are the subject of the calculation. The total distance column stores the total driving distance for the subject month. The total driving distance is calculated by extracting data for the subject month from the driving distance DB 135 and adding up the driving distances of the extracted records. For trips that span multiple months, it is determined in advance whether to judge based on the start date and time or the end date and time.
[0056] FIG. 14 is an explanatory diagram showing an example of a billing actual DB. The billing actual DB 137 stores the actual billing results for usage fees to users. The billing actual DB 137 includes a customer ID column, a vehicle ID column, an IMEI column, a usage date column, a pay-per-use column, and a usage fee column. The customer ID column stores the customer ID. The vehicle ID column stores the vehicle ID of the vehicle used by the user. The IMEI column stores the IMEI assigned to the communication device 4. The usage date column stores the month of use of the vehicle that is the subject of the billing. The pay-per-use column stores the value of the pay-per-use fee that was billed. The usage fee column stores the value of the usage fee that was billed.
[0057] FIG. 15 is an explanatory diagram showing an example of a rental condition DB. The rental condition DB 138 stores the conditions under which a user wishes to rent a vehicle to another person. The rental condition DB 138 includes a rental ID column, a customer ID column, a vehicle ID column, a distance unit price column, a rental date and time registration column, a start date and time column, an end date and time column, and a publication column. The rental ID column stores a rental ID for identifying each offer. The customer ID column stores the customer ID of the user. The vehicle ID column stores the vehicle ID of the vehicle to be rented out. The distance unit price column stores the rental fee for each mileage. The rental date and time registration column stores the name of the offer. The start date and time column stores the start date and time when rental is available. The end date and time column stores the end date and time when rental is available. The publication column stores whether or not the rental information is published.
[0058] FIG. 16 is an explanatory diagram showing an example of a reservation DB. Reservation DB 139 stores vehicle use reservation information by lessees. Reservation DB 139 includes a rental ID column, a branch number column, a customer ID column, a name column, a mobile phone number column, a vehicle ID column, a vehicle IMEI column, a distance unit price column, a scheduled start date and time column, a scheduled end date and time column, and a status column. The rental ID column stores the rental ID. The branch number column stores the branch number. This is to identify when multiple reservations are made for one rental ID. The customer ID column stores the customer ID of the lessee. The name column stores the lessee's name. The mobile phone number column stores the lessee's mobile phone number. The vehicle ID column stores the vehicle ID of the vehicle to be rented. The vehicle IMEI column stores the IMEI of the communication device 4 attached to the vehicle. The distance unit price column stores the rental fee for each mileage. The scheduled start date and time column stores the scheduled date and time to start renting out the vehicle. The Scheduled End Date column stores the scheduled end date and time of the rental. The Status column shows the status of the reservation. Immediately after a reservation is registered, the status is waiting for approval. If the user approves the reservation, the status becomes approved. If the user rejects the reservation, the status becomes not approved.
[0059] FIG. 17 is an explanatory diagram showing an example of a rental history DB. Rental history DB13A stores information on the history of vehicle rentals by lessees. Rental history DB13A includes a rental ID column, a branch number column, a customer ID column, a start date and time column, an end date and time column, a mileage column, a billed fee column, a fee column, and a payment amount column. The rental ID column stores the rental ID. The branch number column stores the branch number. The customer ID column stores the customer ID of the lessee. The start date and time column stores the date and time when the rental of the vehicle started. The end date and time column stores the date and time when the rental of the vehicle ended. The mileage column stores the mileage of the vehicle during the rental period. The billed fee column stores the fee billed to the lessee. The fee column stores the system usage fee collected by the operator, etc. The payment amount column stores the amount paid to the user.
[0060] Next, the information processing performed by the automobile transaction system 100 will be described. FIG. 18 is a flowchart showing an example of the procedure of the location information acquisition processing. The location information acquisition processing is a processing for acquiring location information from the communication device 4 attached to the vehicle and storing the vehicle's location in the location information DB 134. The communication device 4 detects that the engine of the vehicle has started and starts the processing. The control unit 41 of the communication device 4 transmits an authentication request to the server 1 (step S1). The control unit 11 of the server 1 receives the authentication request (step S2). The control unit 11 performs authentication (step S3). For example, the control unit 11 performs SMS authentication. The control unit 11 transmits the authentication result to the communication device 4 (step S4). The control unit 41 of the communication device 4 receives the authentication result (step S5). The control unit 41 determines whether the authentication is successful or not (step S6). If the control unit 41 determines that the authentication is unsuccessful (NO in step S6), the processing ends. When the control unit 41 determines that the authentication is successful (YES in step S6), it transmits the positioning result of the position acquisition unit 45 to the server 1 (step S37). The control unit 11 of the server 1 receives the positioning result (step S38). The control unit 11 stores the vehicle's position information based on the positioning result in the position information DB 134 (step S9). The control unit 11 transmits a response to the effect that the position information has been stored to the communication device 4 (step S10). The control unit 41 of the communication device 4 receives the response (step S11). The control unit 41 determines whether or not to end the process (step S12). For example, when the control unit 41 detects that the engine of the vehicle has stopped, it determines to end the process. When the control unit 41 determines not to end the process (NO in step S12), it returns the process to step S7 and continues the process. When the control unit 41 determines to end the process (YES in step S12), it transmits an end to the server 1 (step S13). The control unit 11 of the server 1 receives the end (step S14). The control unit 11 stores the end (step S15). For example, the control unit 11 sets a Trip end flag in the latest location information. The control unit 11 transmits a response to the communication device 4 (step S16). The control unit 41 of the communication device 4 receives the response (step S17) and ends the process.
[0061] FIG. 19 is a flowchart showing an example of the procedure of the mileage calculation process. The mileage calculation process is a process for calculating the vehicle mileage of each trip based on the position information stored in the position information DB 134. The control unit 11 of the server 1 acquires the position information included in one trip to be processed (step S31). Based on the position information, the control unit 11 plots the start position, end position, and intermediate positions of the trip on an electronic map (step S32). At that time, the control unit 11 checks the overlap of each point with the road line data, and corrects it so that all points are on the road (performs map matching). The control unit 11 generates a route from the start position to the end position based on the plotted positions and the road line data or road network data (step S33). The control unit 11 calculates the mileage based on the route and the road network data (step S34). The control unit 11 stores the mileage in the mileage DB 135 (step S35). The control unit 11 determines whether to end the process (step S36). The control unit 11 determines to end the process if there is no trip for which the mileage has not been calculated, and determines not to end the process if not. If the control unit 11 determines not to end the process (NO in step S36), it returns the process to step S31 and continues the process. If the control unit 11 determines to end the process (YES in step S36), it ends the process. Note that the mileage calculation process desirably calculates the mileage for a trip each time the end of a trip is detected in the location information acquisition process. In this case, step S36 is not necessary.
[0062] FIG. 20 and FIG. 21 are flowcharts showing an example of the procedure of the rental condition registration process. The rental condition registration process is a process executed when a user sets the conditions for renting a vehicle. The user selects the rental condition registration menu on the screen of the user terminal 2. The control unit 21 of the user terminal 2 transmits a registration request to the server 1 (step S51). The control unit 11 of the server 1 receives the registration request (step S52). The control unit 11 creates a fee setting screen (step S53). The fee setting screen is a screen for setting a distance unit price. In the case of a new registration, the distance unit price field is left blank, and in the case of an existing registration, the current setting value is set. The control unit 11 transmits the fee setting screen to the user terminal 2 (step S54). The control unit 21 of the user terminal 2 receives the fee setting screen (step S55). The control unit 21 displays the fee setting screen on the display panel 25 (step S56). The user sets a rental fee for each mileage (called a rental unit price). The control unit 21 accepts the fee setting (step S57). The control unit 21 judges whether the rental unit price exceeds the contract unit price (second distance unit price) (step S58). The contract unit price is the distance unit price in the plan to which the user has contracted. When the control unit 21 judges that the rental unit price is equal to or lower than the contract unit price (NO in step S58), it issues a warning (step S59). This is because if the rental unit price is equal to or lower than the contract unit price, the user may incur a loss even if the user rents the vehicle to another person. However, if the user has contracted for an unlimited ride plan up to 500 km, for example, and depending on the actual usage (mileage up to yesterday), if the user does not use the vehicle for 500 km in the current month, the user may not incur a loss even if the rental unit price is set lower than the contract unit price. Therefore, the user can select whether or not to modify the rental unit price on the screen that displays the warning. Based on the selection input by the user, the control unit 11 judges whether or not to modify the rental unit price (step S60). If the control unit 11 determines that the rental unit price should be revised (YES in step S60), the process returns to step S56. If the control unit 11 determines that the rental unit price should not be revised (NO in step S60), the process proceeds to step S61. If the control unit 21 determines that the rental unit price exceeds the contract unit price (YES in step S58), the control unit 21 transmits the rental unit price set by the user to the server 1 (step S61).The control unit 11 of the server 1 receives the rental unit price (step S62). The control unit 11 creates a schedule registration screen (step S63). The schedule registration screen is a screen for setting a rental schedule. In the case of a new registration, the schedule is left unset, and in the case of an existing registration, the current settings are reflected on the screen. The control unit 11 sends the schedule registration screen to the user terminal 2 (step S64). The control unit 21 of the user terminal 2 receives the schedule registration screen and displays it on the display panel 25 (step S65). The user inputs the schedule (rentable period). The control unit 21 accepts the schedule (step S66). The control unit 21 sends the schedule to the server 1 (step S67). The control unit 11 of the server 1 receives the schedule (step S68). The control unit 11 creates a rental / delivery registration screen (step S69). The rental / delivery registration screen is a screen for setting the location where the vehicle is rented out and the location where the vehicle is returned at the start and end of rental, and how the key is handed over. In the case of a new registration, the setting is left unset, and in the case of an existing registration, the current setting is reflected on the screen. The control unit 11 transmits the rental / delivery registration screen to the user terminal 2 (step S70). The control unit 21 of the user terminal 2 receives the rental / delivery registration screen and displays it on the display panel 25 (step S71). Go to FIG. 21. The user inputs the setting of the place to rent the vehicle and the place to receive the return of the vehicle, and the key delivery method, to the rental / delivery registration screen. The control unit 21 accepts the setting of the rental location and the key delivery setting (step S72). The control unit 21 transmits the accepted contents to the server 1 (step S73). The control unit 11 of the server 1 receives the setting of the rental location and the key delivery setting (step S74). The control unit 11 stores the rental unit price, schedule, setting of the rental location, and setting of the key delivery in the rental condition DB 138 (step S75), and ends the process. The rental location settings and key handover settings may be stored in the customer DB 131.
[0063] FIG. 22 is a flowchart showing an example of the procedure of the reservation process. The reservation process is a process in which a lessee reserves the use of a vehicle. The lessee uses the lessee terminal 5 to access the rental site of the automobile transaction system 100. A map with the location of the lessee terminal 5 at the center is displayed on the top screen, and rental locations of vehicles that can be rented are displayed as icons on the map. When an icon is selected, the reservation process starts. The control unit 51 of the lessee terminal 5 sends a display request to the server 1 (step S81). The display request includes a vehicle ID (identification information). The control unit 11 of the server 1 receives the display request (step S82). The control unit 11 creates a rental registration information screen including vehicle information, terms of use, etc. (step S83). The control unit 11 sends the rental registration information screen to the lessee terminal 5 (step S84). The control unit 51 of the lessee terminal 5 receives the rental registration information screen (step S85). The lessee checks the rental conditions, and if he / she wishes to make a rental reservation, he / she selects the reservation procedure button. If not, the lessee selects a back button or the like. The control unit 51 accepts the operation and determines whether or not to carry out the reservation procedure (step S86). If the control unit 51 judges that the reservation procedure is not to be carried out (NO in step S86), it ends the process. If the control unit 51 judges that the reservation procedure is to be carried out (YES in step S86), it sends a reservation request to the server 1 (step S87). The control unit 11 of the server 1 receives the reservation request (step S88). The control unit 11 creates a reservation screen (step S89). The control unit 11 sends the reservation screen to the lessee terminal 5 (step S90). The control unit 51 of the lessee terminal 5 receives the reservation screen and displays it on the display panel 55 (step S91). The lessee inputs the start date and time and the end date and time on the reservation screen and selects the reservation button. The control unit 51 accepts the input (step S92). The control unit 51 sends the accepted start date and time and end date and time to the server 1 (step S93). The control unit 11 of the server 1 receives the start date and time and the end date and time (step S94). The control unit 11 stores the reservation information including the lessee's customer ID, the vehicle ID, the start date and time, and the end date and time in the reservation DB 139 (step S95). The control unit 11 transmits a notification that the reservation has been registered to the user (step S96). The control unit 11 transmits a completion screen to the lessee terminal 5 (step S97).The control unit 51 of the lessee terminal 5 receives the completion screen, and displays it on the display panel 55 (step S98). The control unit 51 ends the process.
[0064] Regarding the reservation process, a search function may be provided to search for vehicles available for rental by specifying rental conditions including the desired rental period and the desired unit price per distance. When the lessee selects one of the vehicles found in the search, the reservation process begins.
[0065] FIG. 23 is a flowchart showing an example of the procedure of reservation confirmation processing. A notification that a reservation has been registered is displayed on the display panel 25 of the user terminal 2. When the user selects a hyperlink in the notification for confirming the reservation details, the reservation confirmation processing is started. The control unit 21 of the user terminal 2 transmits a request for transmitting the reservation status to the server 1 (step S111). The control unit 11 of the server 1 receives the request for transmitting the reservation status (step S112). The control unit 11 creates a reservation status screen showing the reservation status (step S113). The control unit 11 transmits the reservation status screen to the user terminal 2 (step S114). The control unit 21 of the user terminal 2 receives the reservation status screen and displays it on the display panel 25 (step S115). The user selects an unapproved reservation. The control unit 21 displays the details of the reservation (step S116). The user confirms the details and inputs whether to approve or reject the reservation. The control unit 21 accepts the input (step S117). The control unit 21 transmits the received approval or rejection information to the server 1 (step S118). The control unit 11 of the server 1 receives the information (step S119). The control unit 11 creates a message for the lessee (step S120). For example, if approved, the message is "Your reservation has been approved." If rejected, the message is "Unfortunately, your reservation has been rejected." The control unit 11 transmits the message to the lessee (step S121). The control unit 11 transmits a completion screen to the user terminal 2 (step S122). The control unit 21 of the user terminal 2 receives the completion screen and displays it on the display panel 25 (step S123). The control unit 21 ends the process.
[0066] FIG. 24 is a flowchart showing an example of the procedure of the rental start process. The renter goes to the designated rental location at the rental start time and receives the rental of the vehicle. Prior to starting to use the vehicle, the renter operates the renter terminal 5 to declare the start of rental. The control unit 51 of the renter terminal 5 starts the rental start process. The control unit 51 transmits the rental start to the server 1 (step S141). The transmitted information includes the rental ID and the customer ID of the renter. The control unit 11 of the server 1 receives the rental start (step S142). The control unit 11 stores a new record in the rental history DB 13A (step S143). The control unit 11 searches the reservation DB 139 using the received rental ID and customer ID as search keys, and acquires the corresponding use reservation information. The control unit 11 stores the rental ID, branch number, and customer ID included in the use reservation information in the rental history DB 13A. In addition, the start date and time is stored as the current date and time or the scheduled start date and time. The control unit 11 creates a confirmation screen including the reservation information (step S144). The control unit 11 sends the confirmation screen to the lessee terminal 5 (step S145). The control unit 51 of the lessee terminal 5 receives the confirmation screen and displays it on the display panel 55 (step 146). The control unit 51 ends the process. Note that if the lessee does not report the start of rental, the start time is treated as the reserved time.
[0067] FIG. 25 is a flowchart showing an example of the procedure of the rental end process. After the lessee has finished using the vehicle and has returned it to the user, he / she operates the lessee terminal 5 to report the end of the rental. The control unit 51 of the lessee terminal 5 starts the rental end process. The control unit 51 transmits the rental end to the server 1 (step S161). The transmitted information includes the rental ID and the customer ID of the lessee. The control unit 11 of the server 1 receives the rental end (step S162). The control unit 11 stores the end date and time in the rental record DB 13A (step S163). The control unit 11 searches the rental record DB 13A using the received rental ID and customer ID as search keys to identify the corresponding record information. The control unit 11 sets the current date and time as the end date and time of the corresponding record information. Note that if the start date and time is not set, the control unit 11 sets the scheduled start date and time stored in the reservation DB 139 as the start date and time. The control unit 11 performs the rent calculation process (step S164). The control unit 11 creates an end screen and transmits it to the lessee terminal 5 (step S165). The end screen includes the amount billed to the lessee. The control unit 51 of the lessee terminal 5 receives the end screen and displays it on the display panel 55 (step S166). The control unit 51 ends the process. In order to prevent the lessee from committing fraud, when the lessee reports an end, the control unit 11 may inform the user of the end report by push notification or the like, and may continue the rental end process only if the user responds by agreeing to the end. Alternatively, when the lessee reports an end, the rental end may be continued only if it is confirmed that the vehicle is located at the place where it should be returned. Furthermore, even if the lessee does not report an end, when the control unit 11 detects the end of the Trip, if it determines that the end location of the Trip is the place where it should be returned, it may process the rental end as the end.
[0068] FIG. 26 is a flowchart showing an example of the procedure of the rent calculation process. The control unit 11 of the server 1 searches the reservation DB 139 using the rental ID as a search key, and acquires the vehicle ID of the vehicle that has been rented out (step S181). The control unit 11 searches the mileage DB 135 using the vehicle ID, start date and time, and end date and time as keys (step S182). The control unit 11 judges whether the search is a hit (step S183). Note that the start time and end time do not necessarily match the times stored in the mileage DB 135 completely, so a search with a certain degree of freedom is performed. If the control unit 11 judges that the search is not a hit (NO in step S183), it executes the mileage calculation process (step S184). The mileage calculation process is the process shown in FIG. 19. If the control unit 11 judges that the search is a hit (YES in step S183), it calculates the rent, etc. (step S185). The rent is calculated from the mileage and the distance unit price included in the use reservation information. The fee collected by the management side is calculated from the rent and a predetermined rate. The payment amount paid to the user is the rent minus the fee. The control unit 11 stores the calculated rent (charge), fee, and payment amount in the lending record DB 13A (step S186). The control unit 11 returns the process to the caller.
[0069] The following exceptions may be applied when calculating rent. Rent is calculated based on the distance traveled and the cost per distance, but for example, a case where the distance traveled is 5km for a two-hour use is also assumed. In this case, the user may feel that the rent obtained is small because the distance traveled is extremely short compared to the length of the rental time, and that lending the vehicle to others is not worth it. Therefore, a minimum deemed mileage is set according to the length of use. For example, for a two-hour use, it is set to 20km. In this case, even if the mileage does not exceed 20km, the mileage is set to 20km for rent calculation purposes. When the mileage is 20km, the rent is calculated based on that mileage.
[0070] In addition, when calculating the rent, fuel costs according to the distance traveled may be calculated and added to the rent. When a rental car company rents out a gasoline-powered vehicle, the vehicle is rented out with a full gas tank, and the vehicle can be refueled just before returning the vehicle, and returned in a full tank. However, if the vehicle being rented out is a hybrid or electric vehicle, it may be difficult to return the vehicle with a full tank of fuel. Also, it is time-consuming for the vehicle user to fill up the tank with fuel every time the vehicle is rented out. If the rule for setting the rental price takes fuel costs into account, there is no need to calculate fuel costs.
[0071] Next, the screens displayed by the user terminal 2 or the lessee terminal 5 will be described. FIG. 27 is an explanatory diagram showing an example of a fee setting screen. The fee setting screen d01 is a screen for setting the distance unit price (rental unit price, first distance unit price, fee unit price) when the user rents out the vehicle to another person. The fee setting screen d01 includes a plan d011, a distance unit price d012, a mileage d013, a weekday unit price column d014, a holiday unit price column d015, a rent guideline table d016, and a registration button d017. The plan d011 displays the plan to which the user has contracted. The distance unit price d012 displays the distance unit price (contract unit price) when calculating the metered fee. The mileage d013 displays the total mileage of the current month up to the previous day. The weekday unit price column d014 is a column for setting the distance unit price that is the basis of the rent to be collected when the vehicle is rented out on a weekday. The holiday unit price column D015 is a column for setting the distance unit price that is the basis of the rent to be collected when a vehicle is rented out on Saturdays, Sundays, and holidays. The rental guideline table D016 displays the rent by rental distance based on the distance unit price set in the weekday unit price column D014 and holiday unit price column D015. The expected time is different from the driving distance time and displays the approximate expected rental time. When the registration button D017 is selected, the distance unit price set in the weekday unit price column D014 and holiday unit price column D015 is sent to server 1. As mentioned above, if the set distance unit price is lower than the contract unit price, it is not sent to server 1 and a warning is displayed.
[0072] FIG. 28 is an explanatory diagram showing an example of a schedule registration screen. The schedule registration screen d02 is a screen for setting a time period during which the user can rent out the vehicle to others. The schedule registration screen d02 includes a day of the week specification field d021, a start time field d022, an end time field d023, a registration button d024, a calendar d025, and a next month link d026. The day of the week specification field d021 is a field for setting the same schedule for each day of the week. Checking Sunday allows you to set a schedule for every Sunday. The start time field d022 is a field for setting the rental start time. The end time field d023 is a field for setting the rental end time. When the registration button d024 is selected, a schedule is registered in which the vehicle can be rented out during the time period specified in the start time field d022 and end time field d023 on every day of the week selected in the day of the week specification field d021. The calendar d025 shows the schedule registration status. In the example of FIG. 28, schedules are registered every Sunday and from the 8th to the 11th. When a specific day is selected on the calendar d025, a time zone setting sub-screen, described later, is displayed, and it is possible to set only the selected day. When the next month link d026 is selected, the displayed month of the calendar d025 changes to the next month. When the displayed month of the calendar d025 is, for example, the next month, a previous month link is displayed, and when the link is selected, the displayed month changes to the current month.
[0073] FIG. 29 is an explanatory diagram showing an example of a time period setting sub screen. The time period setting sub screen d03 is a screen for setting a time period for a specific day. For example, the time period setting sub screen d03 has two modes, a lending designation mode and a private designation mode. FIG. 29A shows an example of a time period setting sub screen in the lending designation mode. In the lending designation mode, a time period during which lending is possible can be set. By operating the time period field d032, a time period during which lending is possible and a time period during which lending is not possible can be set. When the left scroll button d033 is selected, the display of the time period field d032 is scrolled to display a time period before the displayed time period. Similarly, when the right scroll button d034 is selected, the display of the time period field d032 is scrolled to display a time period after the displayed time period. When the register button d035 is selected, the setting of the time period is registered. FIG. 29B shows an example of a time period setting sub screen in the private designation mode. In the private designation mode, a time period for private use can be set. That is, it is used to set a time period during which lending is not possible. The screen operations are the same as in the lending designation mode, so the explanation will be omitted.
[0074] FIG. 30 is an explanatory diagram showing an example of a rental / delivery registration screen. The rental / delivery registration screen d04 is a screen for registering the location where the vehicle is rented / returned and the location where the vehicle key is delivered when the user rents the vehicle to another person. The rental / delivery registration screen d04 includes a location type setting field d041, an address field d042, a decision button d043, a map field d044, and a delivery method field d045. The location type setting field d041 sets the type of location where the vehicle is rented. Here, home or other than home is selected as the rental location. The address field d042 is a field for inputting the address of the rental location when other than home is selected as the rental location. When the decision button d043 is selected, the address entered in the address field d042 is transmitted to the server 1 or a map service. The map field d044 displays a map of the vicinity of the address entered in the address field d042. The user moves the location mark d0441 to the rental location in the map field d044. The key delivery method field d045 sets the key delivery method. There are three options. The first option is when the user himself delivers the key at the rental location. The second option is when the user's agent delivers the key at the rental location. The third option is when a smart key is used. This option can be selected only when the vehicle is equipped with a smart key. Here, a digital key that is an extension of the smart key is assumed. In other words, it allows the vehicle to be unlocked and locked using a smartphone. An ID with a validity period (share key) is sent to the lessee terminal 5. The validity period is from the scheduled rental start date and time to the scheduled rental end date and time. The lessee can use the share key received by the lessee terminal 5 to unlock and lock the vehicle and start and stop the engine.
[0075] FIG. 31 is an explanatory diagram showing an example of a rental registration information screen. The rental registration information screen d05 is a screen on which a lessee who rents a vehicle from a user refers to rental conditions, etc. The rental registration information screen d05 contains a large amount of information, so it is not possible to display the entire screen at once, and it is assumed that the contents shown in FIG. 31A and FIG. 31B can be referred to by scrolling. The rental registration information screen d05 includes a vehicle photo d051, a weekday unit price d052, a holiday unit price d053, a rental fee guideline table d054, a reservation status table d055, a link to the next month d056, a delivery location d057, vehicle information d058, a vehicle introduction d059, a user profile d05A, and a reservation procedure button d05B. The vehicle photo d051 is a photo of the vehicle to be rented. The photo is stored in a vehicle DB (not shown). The weekday unit price d052 is the distance unit price on weekdays. The holiday unit price d053 is the distance unit price on Saturdays, Sundays, and holidays. The rental fee guideline table d054 shows the rent calculated based on the mileage set for each usage time. If the actual mileage falls below the mileage set for each usage time, the rent is calculated based on the distance shown in the rental fee guideline table d054. A notice is displayed stating that the fee displayed for each usage time is the minimum rent. The reservation status table d055 shows the reservation status from the current day onwards. In FIG. 31A, four days are displayed. By scrolling vertically, the status of other days can be viewed. In FIG. 31A, the reservation status table d055 shows six hours for a time period. By scrolling horizontally, the reservation status of the previous and next time periods can be viewed. When the next month link d056 is selected, the display of the reservation status table d055 will change to the next month. The delivery location d057 shows the delivery location of the key. It is assumed that the delivery location and the vehicle rental and return location are the same or close to each other. The vehicle information d058 shows vehicle information such as the capacity and the equipment status of optional items. The vehicle introduction d059 is an introduction to the vehicle entered by the user. Vehicle information and the vehicle introduction are stored in the vehicle DB. The user profile d05A indicates the user's profile, such as the evaluation from the lessee, the average response time from when the rental reservation is registered until an approval / rejection response is received, and the proportion of approval responses to the number of rental reservations (approval rate). The user's profile is stored in the customer DB131. Selecting the reservation procedure button d05B will transition to the reservation screen.
[0076] FIG. 32 is an explanatory diagram showing an example of a reservation screen. The reservation screen d06 is a screen for a renter to reserve a vehicle rental. The reservation screen d06 includes a date and time designation table d061, a link to the next month d062, a scheduled start and end date and time d063, a distance unit price d064, a rental fee guideline table d065, a reply deadline d066, a message field d067, and a reservation button d068. The date and time designation table d061 is a table similar to the reservation status table d055 of the rental registration information screen d05. The date and time designation table d061 has three types of displays for each time slot: a reservation possible display d0611, a reservation impossible display d0612, and a selection status display d0613. The reservation possible display d0611 indicates that the time slot is available for reservation and is not in a selected state. The reservation impossible display d0612 indicates that the time slot is unavailable for reservation. The selection status display d0613 indicates that the time slot is available for reservation and is in a selected state. When a time slot in the available for reservation display d0611 is selected, the selection status display d0613 appears. When a time slot in the selection status display d0613 is selected, the available for reservation display d0611 appears again. By vertically scrolling the date and time designation table d061, it is possible to make reservations for other days that are not displayed. By horizontally scrolling the date and time designation table d061, it is possible to make reservations for the previous or next time slot. When the next month link d062 is selected, the date and time designation table d061 will display the next month. The scheduled start and end dates d063 display the scheduled rental start date and time and the scheduled rental end date and time according to the specifications in the date and time designation table d061. The distance unit price d064 displays the distance unit price. The rental fee guideline table d065 displays the rent by mileage based on the distance unit price. The mileage is set as an estimated distance for each length of rental time. The rental fee guideline table d065 displays the length of time the renter plans to rent the property. If the mileage is shorter than expected, and rent is charged as if the expected distance was driven, a notice is displayed near the rent guideline d065. The response deadline d066 sets the deadline by which the user should respond as to whether to approve or reject the rental reservation. A message from the lessee to the user is entered in the message field d067. When the reservation button d068 is selected, a reservation request is made with the details set on the reservation screen d06.
[0077] FIG. 33 is an explanatory diagram showing an example of a reservation status screen. The reservation status screen d07 is a screen for a user to check the reservation status, etc. FIG. 33A shows the reservation status screen d07. FIG. 33B shows a response screen d08 displayed as a pop-up window by operating the reservation status screen d07. The reservation status screen d07 includes a reservation status table d071, a next month link d072, an operation table d073, and a request table d074. The reservation status table d071 shows the reservation status for each time slot. The reservation status table d071 has five types of displays for each time slot. The unavailable display d0711 shows a time slot that is not available for rental. The available display d0712 shows a time slot that is available for rental but has no reservations. The transacted display d0713 shows a time slot that has been completed for rental. The reserved display d0714 shows a time slot that has been reserved and approved. The waiting for approval display d0715 shows a time slot that has been reserved but has not been answered. When the next month link d072 is selected, the reservation etc. status table d071 will display the next month. The operation table d073 displays the status of any reservations made on the day. The request table d074 displays reservations that are awaiting a response. When the operation button d0741 in the status column of the request table d074 is selected, the response screen d08 will pop up.
[0078] The answer screen d08 includes detailed information d081, a reject button d082, and an accept button d083. The detailed information d081 displays detailed information about the reservation. If the reject button d082 is selected, the reservation is rejected and the reservation is considered not to have existed. If the accept button d083 is selected, the reservation is approved and the reservation is completed.
[0079] The present embodiment provides the following advantages: A vehicle user can rent out a vehicle to a lessee during a time period when the vehicle user is not using the vehicle, and can calculate the rent to be paid by the user.
[0080] (Embodiment 2) This embodiment relates to an attraction transaction that promotes the use of vehicles. An attraction transaction is a transaction in which a vehicle user or vehicle lessee receives a monetary reward from the provider when the user or lessee visits a place (attraction place, destination) that the provider wishes the user or lessee to visit. The provider registers in advance the places that the user or lessee wishes the user or lessee to visit and the reward for visiting the places in the automobile transaction system 100. For example, the reward may be a refund of the fare for the distance traveled from the user or lessee's registered address to the attraction place.
[0081] In addition to the databases described in the first embodiment, databases used in this embodiment will be described. Fig. 34 is an explanatory diagram showing an example of a provider DB. The provider DB 13B stores information on providers who provide rewards. The provider DB 13B includes a provider ID column, a name column, and an address column. The provider ID column stores a provider ID that can uniquely identify a provider. The name column stores the name of the provider. The address column stores the address of the provider.
[0082] FIG. 35 is an explanatory diagram showing an example of an attraction DB. The attraction DB 13C stores attraction information (return information) such as an attraction location and a reward. The attraction DB 13C includes an attraction ID column, a provider ID column, a name column, an address column, an image column, an introduction column, a start date and time column, an end date and time column, a target column, a return type column, an amount column, a grant date column, and a grant condition column. The attraction ID column stores an attraction ID that uniquely identifies the attraction information. The provider ID column stores a provider ID. The name column stores the name of the attraction location. The address column stores the address of the attraction location. For example, when a hotel is the provider, the provider and the attraction location match, so the name column and the address column store the name and address of the provider, respectively. The image column stores an image of the attraction location. The image file name may be stored instead of the image. The introduction column stores an introduction of the attraction location. The start date and time column stores the start date and time of the period for which the reward is to be granted. The end date and time column stores the end date and time of the period. The target person column stores the type of customer to whom the reward is to be given. In this specification, it is a user or a renter. The rebate type column stores the form of the reward. For example, the rebate of the one-way distance fee from the departure point (such as the customer's home) to the attraction location, the rebate of the round trip distance fee from the departure point to the attraction location, a flat amount regardless of the distance traveled, a flat amount coupon, etc. The amount column stores the specified amount when a reward form that specifies an amount is selected. The grant date column stores the scheduled date for providing the reward. The grant condition column stores the conditions for granting the reward. The grant condition specifies the operation that indicates that the attraction location has been visited. For example, a photo of a two-dimensional code or an image of a receipt issued by the attraction location.
[0083] FIG. 36 is an explanatory diagram showing an example of an application DB. The application DB 13D stores application information for the issuance of a reward. The application DB 13D includes an attraction ID column, a customer ID column, a rebate type column, a rebate amount column, and a status column. The attraction ID column stores an attraction ID. The customer ID column stores the customer ID of the customer who made the application. The rebate type column stores the form of the reward. The rebate amount column stores the rebate amount to be granted. The status column stores the status of the rebate. For example, the status column stores Entry, which indicates the status when the application was made, In Operation, which indicates the status when the vehicle is heading to the attraction location, Arrived, which indicates that arrival at the attraction location has been confirmed, Awaiting Reward, which indicates the status when the reward is waiting to be granted, and Reward Completed, which indicates that the granting of the reward has been completed.
[0084] The information processing in the second embodiment will be described. FIG. 37 is a flow chart showing an example of the procedure of the attraction registration processing. The provider operates the provider terminal 6 to request the registration of the attraction information. The control unit 61 of the provider terminal 6 transmits the request to the server 1 (step S201). The control unit 11 of the server 1 receives the request (step S202). The server 1 transmits a screen for registering the attraction information to the provider terminal 6 (step S203). The control unit 61 of the provider terminal 6 receives the screen and displays it on the display unit 66 (step S204). The provider inputs the attraction information on the screen. The control unit 61 accepts the attraction information (step S205). The control unit 61 transmits the attraction information to the server 1 (step S206). The control unit 11 of the server 1 receives the attraction information (step S207). The control unit 11 stores the attraction information in the attraction DB 13C (step S208). The control unit 11 transmits a completion screen to the provider terminal 6 (step S209). The control unit 61 of the provider terminal 6 receives the completion screen, and displays it on the display unit 66 (step S210). The control unit 61 then ends the process.
[0085] FIG. 38 is a flowchart showing an example of the procedure of the application process. The application process is a process for applying for an invitation transaction. The procedure of the application process is the same whether it is performed by a user or a tenant, so the following explanation will be given for the case where the user applies. The user operates the user terminal 2 to request the invitation information. At this time, search conditions for the invitation information (conditions such as location and period) may be set. The control unit 21 of the user terminal 2 transmits a request for the invitation information to the server 1 (step S221). The control unit 11 of the server 1 receives the request (step S222). The control unit 11 refers to the invitation DB 13C, creates a list of invitation information that matches the conditions, and transmits the list to the user terminal 2 (step S223). The control unit 21 of the user terminal 2 receives the list and displays it on the display panel 25 (step S224). The user selects the invitation information to be applied for from the list, and the control unit 21 accepts the selection (step S225). The control unit 21 transmits the selection information to the server 1 (step S226). The control unit 11 of the server 1 receives the selection information (step S227). The control unit 11 creates a details screen showing details of the selected attraction information and transmits it to the user terminal 2 (step S228). If the rebate type is the rebate of the distance fee, the control unit 11 calculates the road distance from the user's address (starting place) to the attraction location using a known route search technique based on the user's address and the address of the attraction location. Based on the calculated distance and the user's distance unit price, the control unit 21 calculates the rebate amount and embeds the value in the details screen. The control unit 21 of the user terminal 2 receives the details screen and displays it on the display panel 25 (step S229). The user checks the details of the attraction information and inputs an application. The control unit 21 accepts the input (step S230). The control unit 21 transmits an application instruction to the server 1 (step S231). The control unit 11 of the server 1 receives the application instruction (step S232). The control unit 11 stores the application information in the application DB 13D (step S233). The control unit 11 transmits an application completion screen to the user terminal 2 (step S234). The control unit 21 of the user terminal 2 displays the application completion screen on the display panel 25 (step S235). The control unit 21 ends the process.
[0086] FIG. 39 is a flowchart showing an example of the procedure of the reward claim process. In the reward claim process, a user or a lessee who applied for an invitation transaction declares that he or she has arrived at the invitation location and claims a reward such as a refund of a fee. As with the application process, the case where the user performs the process will be described. After arriving at the invitation location, the user operates the grant condition. The user photographs a two-dimensional code installed at the invitation location with the imaging unit 27 of the user terminal 2. Alternatively, the user photographs a receipt or invoice issued for the usage fee of the invitation location or the purchase of an item with the imaging unit 27. The control unit 21 of the user terminal 2 acquires an image from the imaging unit 27 (step S251). The control unit 21 determines whether the image is a two-dimensional code (step S252). If the control unit 21 determines that the image is not a two-dimensional code (NO in step S252), the control unit 21 transmits the image to the server 1 (step S253). The control unit 11 of the server 1 receives the image (step S254). The control unit 11 performs image recognition and judges whether the use was at the attraction location based on the information on the location where the receipt or the like was issued (step S255). If the control unit 11 judges that the use was at the attraction location (YES in step S255), it updates the value of the status column of the application DB 13D to, for example, arrived (step S256). The control unit 11 creates a response screen, here a screen indicating that the arrival at the attraction location and the use of the attraction location have been confirmed, and transmits it to the user terminal 2 (step S257). If the control unit 11 judges that the use was not at the attraction location (NO in step S255), it creates a response screen indicating that the arrival at the attraction location and the use of the attraction location have not been confirmed, and transmits it to the user terminal 2 (step S257). The control unit 21 of the user terminal 2 receives the response screen and displays it on the display panel 25 (step S258). The control unit 21 ends the process. If the control unit 21 determines that the image is a two-dimensional code (YES in step S252), it transmits information to the server 1 based on the information embedded in the two-dimensional code (step S259). For example, this is a POST of a form in which an attraction ID is embedded. The server 1 receives the information (step S260). The control unit 11 executes steps S256 and onward. It is also possible to determine that the vehicle has arrived at the attraction location from the position information obtained from the communication device 4, and include the arrival determination result in the response screen.
[0087] FIG. 40 is a flow chart showing an example of the procedure of the reward granting process. The reward granting process is a process of granting a reward for an invitation transaction that has reached the reward grant date. It is assumed that the reward granting process is executed daily. The control unit 11 of the server 1 searches the invitation DB 13C and extracts invitation information whose grant date is the current day (step S271). The control unit 11 selects one of the extracted invitation information (step S272). The control unit 11 searches the application DB 13D using the invitation ID of the selected invitation information as a key, and extracts application information whose invitation ID matches and whose status column value is waiting for grant (step S273). The control unit 11 updates the value of the status column of the extracted application information to grant completion (step S274). Note that if the reward to be granted is a coupon, the control unit 11 separately performs a process of granting the coupon. The process related to the coupon is publicly known, so the description will be omitted. The control unit 11 judges whether there is any unprocessed invitation information (step S275). If the control unit 11 determines that there is unprocessed attraction information (YES in step S275), the control unit 11 returns the process to step S272. If the control unit 11 determines that there is no unprocessed attraction information (NO in step S275), the control unit 11 ends the process.
[0088] FIG. 41 is an explanatory diagram showing an example of an attraction registration screen. The attraction registration screen d09 is a screen for a provider to register attraction information. Since the attraction registration screen d09 has a large amount of information, it is not possible to display the entire screen at once, and it is assumed that the contents shown in FIG. 41A and FIG. 41B can be referred to by scrolling. The attraction registration screen d09 includes a name and address field d091, an image field d092, an introduction field d093, a period field d094, a target field d095, a benefit field d096, a grant date field d097, a grant condition field d098, and a registration button d099. The name and address field d091 is a field for setting the name and address of the attraction location. The name and address field d091 includes a name field d0911, a decision button d0912, an address field d0913, and a decision button d0914. When the name of the attraction location is input in the name field d0911 and the decision button d0912 is selected, the name is set. Enter the address of the attraction location in the address field d0913 and select the decision button d0914 to set the address. The image field d092 is a field for setting a photo of the attraction location, etc. Select the selection button d0921 and specify an image file. The loaded image is displayed in the display area d0922. Enter an introduction for the attraction location in the introduction field d093. The period field d094 is a field for setting the target period. The target person field d095 is a field for setting the target person for the benefit. Checking the check box d0951 makes vehicle users eligible. Checking the check box d0952 makes renters (rental users) eligible. Checking both check boxes makes users and renters eligible. The benefit field d096 is a field for setting the benefit (rebate content). Checking the check box d0961 makes the benefit a rebate of the distance fee equivalent to the one-way distance to the attraction location. If check box d0962 is checked, the benefit will be a refund of the distance fee equivalent to the round trip distance to the attraction location. If check box d0963 is checked, the benefit will be a flat-rate refund of the distance fee. If a flat-rate amount is selected in pull-down menu d0964 and confirmation button d0965 is selected, the flat-rate amount will be set. If check box d0966 is checked, the benefit will be a flat-rate coupon. If the amount is set in pull-down menu d0967 and confirmation button d0968 is selected, the coupon amount will be set.The grant date field d097 is a field for setting the date on which the benefit will be granted. The grant date is set by selecting a date in the pull-down menu d0971 and selecting the decision button d0972. The grant condition field d098 is a field for setting the conditions for granting the benefit. Checking the check box d0981 makes it a condition for granting the benefit to photograph the two-dimensional code at the attraction location. Checking the check box d0982 makes it a condition for granting the benefit to photograph the receipt issued at the attraction location. Selecting the registration button d099 sends the set attraction information to the server 1 and stores it in the attraction DB 13C.
[0089] FIG. 42 is an explanatory diagram showing an example of an application screen. The application screen d10 is a screen for a user or lessee to apply for an attraction transaction. The application screen d10 includes a period d101, a benefit d102, an image d103, a name etc. d104, a condition rule table d105, facility information d106, and an entry button d107. The period d101 indicates the period of use of the vehicle during which the benefit can be obtained. The benefit d102 indicates the benefit (reward) content such as a reduction in mileage charges. The image d103 indicates an image of the attraction information. The name etc. d104 indicates the name etc. of the attraction location. The condition rule table d105 indicates the conditions and rules for receiving a reduction in mileage charges. The facility information d106 indicates information on the attraction location. When the entry button d107 is selected, information to the effect that an attraction transaction is applied for is transmitted to the server 1, and the application information is stored in the application DB 13D.
[0090] In this embodiment, the user or lessee can obtain a benefit such as a reduction in distance charges through the attraction transaction. The provider of the benefit can encourage the user or lessee to visit the attraction location.
[0091] Next, the billing process will be described. The billing process is performed for both the user and the lessee, but only the billing process for the user will be described here. FIG. 43 is a flow chart showing an example of the procedure of the billing process. The billing process is monthly, since it is assumed that the billing process is performed every month (predetermined period). The control unit 11 of the server 1 searches the customer DB 131 and extracts information on the customer (user) to be billed (step S291). The control unit 11 selects the customer to be processed (step S292). The control unit 11 calculates the total mileage for the selected customer in the month (step S293). The control unit 11 acquires the mileage of each trip for the customer in the target month from the mileage DB 135, and calculates the total mileage by adding up the acquired mileages. The control unit 11 stores the calculated total mileage for the month (used mileage) in the mileage record DB 136. The control unit 11 calculates the pay-per-use fee (distance fee) (step S294). The control unit 11 calculates the metered fee by multiplying the distance unit price stored in the contract DB 132 by the total mileage. In the case of the unlimited ride plan up to 300 km per month described above, the metered fee is calculated based on the mileage when the total mileage exceeds 300 km. The control unit 11 calculates the rental payment amount (step S295). The control unit 11 acquires the rental record of the customer for the target month from the rental record DB 13A, and calculates the monthly rental payment amount by adding up the payment amounts included in the acquired rental record. The control unit 11 calculates the refund amount (step S296). The control unit 11 extracts the application information for the target month of the customer from the application DB 13D, which has the value of the status column as "granted". The control unit 11 calculates the monthly refund amount by adding up the refund amounts included in the extracted application information. The control unit 11 determines whether to offset (step S297). The offset here applies to the basic fee and metered fee payable by the user, and the loan payment amount and refund amount to be received by the user. It is assumed that whether or not to offset is determined in advance. The setting of whether or not to offset may be common to all customers, or may be set for each customer. If the control unit 11 determines that offset should be performed (YES in step S297), it calculates the billing amount (step S298). Billing amount = basic fee + metered fee - (loan payment amount + refund amount). The control unit 11 determines whether the calculated billing amount is less than or equal to 0 (step S299).When the control unit 11 determines that the billing amount is not equal to or less than 0 (NO in step S299), it performs billing processing for the calculated billing amount (step S300). The control unit 11 advances the process to step S306. When the control unit 11 determines that the billing amount is 0 or less (YES in step S299), it determines whether or not to pay the negative amount (step S301). It is assumed that whether or not to pay the negative amount is predetermined. The setting of whether or not to pay the negative amount may be common to all customers, or may be set for each customer. When the control unit 11 determines that the negative amount is to be paid (YES in step S301), it performs payment processing (step S302). The control unit 11 proceeds to processing in step S306. When the control unit 11 determines that the negative amount is not to be paid (NO in step S301), it stores the negative amount as the remaining amount in the auxiliary storage unit 13 or the like (step S303). The control unit 11 proceeds to processing in step S306. When the control unit 11 determines that the amount is not to be offset (NO in step S297), it bills the total amount of the basic fee and the metered fee as the usage fee (step S304). The control unit 11 performs processing to pay the total amount of the loan payment amount and the refund amount (step S305). The control unit 11 advances the process to step S306. The control unit 11 determines whether or not there is an unprocessed customer (step S306). If the control unit 11 determines that there is an unprocessed customer (YES in step S306), the control unit 11 returns the process to step S292. If the control unit 11 determines that there is no unprocessed customer (NO in step S306), the control unit 11 ends the process.
[0092] FIG. 44 is an explanatory diagram showing an example of a usage fee display screen. The usage fee display screen d11 is a screen for offsetting the basic fee, metered fee, loan payment amount, and refund amount. The usage fee display screen d11 includes the billed amount d111, payment information d112, usage fee d113, deposit amount d114, and deposit details d115. The billed amount d111 indicates the billed amount after offsetting. Payment information d112 indicates the payment date such as the control method and deduction date. The usage fee d113 indicates the basic fee and distance fee (metered fee). The deposit amount d114 indicates the amount received by the user. The deposit details d115 indicates the loan payment amount obtained from the loan transaction and the refund amount obtained from the attraction transaction.
[0093] FIG. 45 is an explanatory diagram showing another example of the usage fee display screen. The usage fee display screen d12 is a screen for offsetting the basic fee, the metered fee, the loan payment amount, and the refund amount, and when the offset result is negative, the amount is carried over as the balance. The usage fee display screen d12 includes the billed amount d121, payment information d122, the usage fee d123, the amount received d124, the details of the payment d125, and the remaining amount d126. The billed amount d121 indicates the billed amount after offsetting. If the amount received is 0 or less, 0 is displayed. The payment information d122 indicates the payment date such as the control method and the deduction date. The usage fee d123 indicates the basic fee and the distance fee (metered fee). The amount received d124 indicates the amount received by the user. The details of the payment d125 indicates the loan payment amount obtained from the loan transaction and the refund amount obtained from the attraction transaction. The balance d126 indicates the remaining amount to be offset against the usage fee the following month.
[0094] FIG. 46 is an explanatory diagram showing another example of the usage fee display screen. The usage fee display screen d13 is a screen when the basic fee, metered fee, loan payment amount, and refund amount are not offset. The usage fee display screen d13 includes billing amount d131, payment information d132, usage fee d133, payment amount d134, and payment details d135. The billing amount d131 indicates the billing amount. The payment information d132 indicates the payment date such as the control method and the deduction date. The usage fee d133 indicates the basic fee and distance fee (metered fee) which are the breakdown of the billing amount. The payment amount d134 indicates the amount paid by the user. The payment details d135 indicates the loan payment amount obtained from the loan transaction and the refund amount obtained from the attraction transaction.
[0095] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims. The claims are written in a format in which a claim cites two or more other claims (multiple claim format), but are not limited to this format. A claim may be written in a format in which multiple claims cite at least one other claim (multi-multi claim format). [Explanation of symbols]
[0096] 100: Automobile trading system 1: Server 11: Control section 12: Main memory 13: Auxiliary storage section 131:Customer DB 132: Contract DB 133: Device DB 134: Location information DB 135: Mileage DB 136: Driving record DB 137: Billing record DB 138: Lending conditions DB 139: Reservation DB 13A: Loan performance DB 13B: Provider DB 13C: Attraction DB 13D: Application DB 14: Communications Department 15: Reading section 16: Display panel 1P: Control program 1a: Portable storage medium 1b: Semiconductor memory 2: User terminal 21: Control section 22: Main memory 23: Auxiliary storage section 24: Communications Department 25: Display panel 26:Operation section 27: Imaging section 2P: Control program 3: Owner device 4: Communication devices 41: Control section 42: Main memory 43: Auxiliary storage section 44: Communications Department 441: SIM card 45: Position acquisition part 46: Imaging section 4P: Control program 5: Renter's terminal 51: Control section 52: Main memory 53: Auxiliary storage section 54: Communications Department 55: Display panel 56:Operation unit 57: Imaging section 6: Provider terminal B: Bus N: Network
Claims
1. Acquire a fee to be paid by a vehicle user for the vehicle, the fee being calculated from a basic fee determined based on a period of use of the vehicle and a metered fee determined based on a distance traveled by the vehicle within a predetermined period of time; Calculate the rental fee obtained by renting out the vehicle, or the rebate amount obtained when using the vehicle to travel to a specified attraction location as the fee to be paid by the vehicle user for the vehicle; Outputting the fare to be paid by the vehicle user and the fare to be paid by the vehicle user An information processing method in which processing is performed by a computer.
2. A rental user who rents the vehicle from the vehicle user calculates the rental fee to be paid by the rental user based on the mileage of the vehicle and a first distance unit price determined by the vehicle user; Output the calculated rental fee The information processing method according to claim 1 .
3. The pay-per-use fee is determined based on a second distance unit price, When the vehicle user sets the first distance unit price to an amount lower than the second distance unit price, the vehicle user is notified of this fact. The information processing method according to claim 2 .
4. The mileage is determined based on the location information of the vehicle during the rental period. The information processing method according to claim 2 .
5. The period for calculating the mileage is determined based on the declaration from the rental user. The information processing method according to claim 2 or 3.
6. The rental fee plus a predetermined handling fee is output to the rental user. The information processing method according to claim 2 or 3.
7. The rental fee is deducted from the fee paid by the vehicle user. The information processing method according to claim 2 or 3.
8. Calculating the amount of rebate based on a route from a predetermined departure location to the attraction location set as a destination of the travel using the vehicle and a distance cost; The calculated refund amount is returned to the vehicle user or rental user. The information processing method according to claim 1 .
9. The route is calculated based on the route determined by the satellite positioning system. The information processing method according to claim 8.
10. When it is detected that the vehicle has arrived at the attraction location, the rebate is given to the vehicle user or the rental user. The information processing method according to claim 8.
11. The arrival of the vehicle at the attraction location is detected by a notification from the terminal of the vehicle user or the rental user that a two-dimensional code installed at the attraction location has been read. The information processing method according to claim 10.
12. The arrival of the vehicle at the attraction location is detected based on the location information of the vehicle. The information processing method according to claim 10.
13. The refund to the vehicle user is a process for paying the refund amount to the vehicle user or a process for deducting the refund amount from the fare paid by the vehicle user, The refund to the lending user is a process for paying the refund amount to the lending user, or a process for deducting the refund amount from the lending fee. The information processing method according to any one of claims 8 to 12.
14. A coupon equivalent to the rebate amount is provided to the vehicle user or the rental user. The information processing method according to any one of claims 8 to 12.
15. A basic fee is charged based on the period of vehicle use. Calculating a pay-per-use charge based on the mileage of the vehicle used within a predetermined period and the distance cost; Calculate the rental fee obtained by renting out the vehicle, or the rebate amount obtained when traveling using the vehicle to a specified attraction location; Output the usage fee calculated from the basic fee and the usage fee, and the rental fee or the refund amount. An information processing program that causes a computer to execute processing.
16. A basic fee is charged based on the period of vehicle use. Calculating a pay-per-use charge based on the mileage of the vehicle used within a predetermined period and the distance cost; Calculate the rental fee obtained by renting out the vehicle, or the rebate amount obtained when traveling using the vehicle to a specified attraction location; Output the usage fee calculated from the basic fee and the usage fee, and the rental fee or the refund amount. An information processing method in which processing is performed by a computer.
17. Accepting rental conditions including a rental period for the vehicle and a unit price for each mileage of the vehicle; Send the accepted loan conditions A condition setting program that causes a computer to execute a process.
18. If the received charge unit price is lower than the unit price used to calculate the metered charge paid by the vehicle user of the vehicle, a warning is output. The condition setting program according to claim 17.
19. Accept rental conditions, including the rental period for which you would like to rent the vehicle and the desired unit price for the mileage used to calculate the rental fee; Transmitting the accepted lending conditions; receiving information on vehicles that meet the rental conditions; Displaying the received vehicle information; When a vehicle selection operation is accepted, identification information of the selected vehicle is transmitted. A vehicle rental program that causes a computer to execute processing.
20. When the start of use of the vehicle is accepted, a notification of the start of use of the vehicle is transmitted; When the end of the use of the vehicle is accepted, a notice of the end of the use of the vehicle is transmitted.
20. The vehicle rental program of claim 19.
21. receiving information on an attraction location that is set as a destination for travel using a vehicle and reward information including a benefit to be granted when the vehicle is driven to the attraction location as a destination; Send the received rebate information A rebate setting program that causes a computer to execute the process.
22. Accept the conditions for the destination of the vehicle trip; Transmitting the accepted conditions; Receive attraction locations that meet the above conditions; Display the received attraction location, When the selection operation of the attraction location is accepted, the identification information of the selected attraction location is transmitted. An application program that causes a computer to execute a process.
23. Scan the two-dimensional code installed at the attraction location, Based on the information contained in the read two-dimensional code, information is transmitted indicating that the customer has arrived at the attraction location.
23. The application program of claim 22.
24. When an operation indicating that the user has arrived at the attraction location is accepted, information indicating that the user has arrived is transmitted; receiving an arrival determination result based on the position of the vehicle; Display the received arrival determination result 23. The application program of claim 22.
Citation Information
Patent Citations
Picture data register system for picture file system
JP1989081076A
