Information processing method, information processing program, and information processing device

Abstract

To provide an information processing method, information processing device, and display program that output the amount of usage fees based on the vehicle's mileage. [Solution] The information processing method involves a computer that acquires residual value data based on the vehicle's usage period and total mileage, calculates the basic fee for the vehicle within a predetermined period and additional charges based on the mileage within that period based on the residual value data, and outputs the billing amount calculated from the basic fee and additional charges.

Description

Technical Field

[0001] The present invention relates to an information processing method, an information processing program, an information processing device, and a display program for outputting a charge amount for usage fees based on the travel distance of a vehicle.

Background Art

[0002] As a method of paying the purchase price of a passenger car, residual value credit is used (such as Patent Document 1). Residual value credit sets the monthly repayment amount based on the amount obtained by subtracting the residual value from the vehicle price after setting the future trade-in price (residual value) in advance. In residual value credit, since the residual value is kept until the end of the contract, there is an advantage that the repayment amount per time is lower than that of ordinary credit payment.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In residual value credit, it is important to accurately set the residual value. The residual value of a vehicle is mainly inversely proportional to the number of years elapsed since the initial registration and the total travel distance. The longer the number of years elapsed and the total travel distance, the lower the residual value. However, in conventional residual value credit, in setting the residual value, although there are some cases where a certain option is provided for the total travel distance, it is determined almost uniformly at the time of contract. Therefore, for users with low usage frequency and short travel distance per time, a residual value lower than a reasonable residual value is set, resulting in a sense of unfairness.

[0005] This invention was made in view of the above circumstances. Its purpose is to provide an information processing method, an information processing program, an information processing device, and a display program that output the amount of usage fees based on the mileage traveled by a vehicle. [Means for solving the problem]

[0006] An information processing method according to one aspect of the present invention involves a computer performing the following steps: acquiring residual value data based on the vehicle's usage period and total mileage; calculating a basic charge for the vehicle within a predetermined period and an additional charge based on the mileage within that predetermined period, based on the residual value data; and outputting a billing amount calculated from the basic charge and the additional charge. [Effects of the Invention]

[0007] In one aspect of this application, it becomes possible to output a billing amount for usage fees based on the vehicle's mileage. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram showing an example configuration of an automobile trading system. [Figure 2] Block diagram showing an example of a server hardware configuration. [Figure 3] Block diagram showing examples of user terminal hardware configurations. [Figure 4] This is a block diagram showing an example of the hardware configuration of the owner's device. [Figure 5] Block diagram showing examples of hardware configurations for communication devices. [Figure 6] This is an explanatory diagram showing an example of a vehicle database. [Figure 7] This is an explanatory diagram showing an example of residual value database (DB). [Figure 8] This is an explanatory diagram showing an example of a pricing database. [Figure 9] This is an explanatory diagram showing an example of a user database. [Figure 10] This is an explanatory diagram showing an example of a contract database. [Figure 11]It is an explanatory diagram showing an example of a device DB. [Figure 12] It is an explanatory diagram showing an example of a location information DB. [Figure 13] It is an explanatory diagram showing an example of a travel distance DB. [Figure 14] It is an explanatory diagram showing an example of a monthly total distance DB. [Figure 15] It is an explanatory diagram showing an example of a billing DB. [Figure 16] It is an explanatory diagram showing an example of the calculation of unit cost. [Figure 17] It is a flowchart showing an example of the procedure of charge calculation processing. [Figure 18] It is a flowchart showing an example of the procedure of basic charge calculation processing. [Figure 19] It is a flowchart showing an example of the procedure of billing unit price calculation processing. [Figure 20] It is a flowchart showing an example of the procedure of location information acquisition processing. [Figure 21] It is a flowchart showing an example of the procedure of travel distance calculation processing. [Figure 22] It is a flowchart showing an example of the procedure of monthly total travel distance calculation processing. [Figure 23] It is a flowchart showing an example of the procedure of usage charge calculation processing. [Figure 24] It is an explanatory diagram showing an example of a usage charge display screen. [Figure 25] It is an explanatory diagram showing another example of a residual value DB. [Figure 26] It is an explanatory diagram showing an example of the calculation of unit cost. [Figure 27] It is an explanatory diagram showing another example of a residual value DB. [Figure 28] It is an explanatory diagram showing a method for correcting distance cost. [Figure 29] It is a flowchart showing an example of the procedure of cost correction processing. [Figure 30] It is an explanatory diagram showing an example of a training DB. [Figure 31] It is an explanatory diagram showing an example of the configuration of an estimation model. [Figure 32]This flowchart shows an example of the model generation process. [Figure 33] The flowchart shows other examples of the fee calculation process. [Modes for carrying out the invention]

[0009] (Embodiment 1) The following embodiments will be described with reference to the drawings. Figure 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, and a communication device 4.

[0010] Server 1 is an information processing device that handles various information processing related to the operation of the automobile trading system 100. Server 1 consists of a server computer, workstation, PC (Personal Computer), etc. Furthermore, Server 1 can be configured as a multicomputer with multiple computers. It may also consist of a cluster system, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of Server 1 may be implemented as a cloud service.

[0011] Figure 2 is a block diagram showing an example of a server hardware configuration. Server 1 includes a control unit 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a read unit 15. Each component is connected by bus B.

[0012] The control unit 11 has one or more arithmetic processing units such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or a GPU (Graphics Processing Unit). The control unit 11 reads and executes the control program 1P (program, program product) stored in the auxiliary storage unit 13, thereby performing various information processing, control processing, etc., that are handled by the server 1, and realizing various functional units such as an acquisition unit, a calculation unit, and an output unit.

[0013] The main memory unit 12 includes SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), flash memory, etc. The main memory unit 12 is primarily controlled by the control unit 11 It temporarily stores the data necessary to perform the calculation.

[0014] The auxiliary storage unit 13 is a hard disk or SSD (Solid State Drive), and the control unit The auxiliary storage unit 13 stores the control program 1P and various DBs (Databases) necessary for 11 to execute processing. The auxiliary storage unit 13 stores the vehicle DB 131, residual value DB 132, fee DB 133, user DB 134, contract DB 135, device DB 136, location information DB 137, mileage DB 138, monthly total mileage DB 139, billing DB 13A, and training DB 13B. The auxiliary storage unit 13 may be an external storage device connected to the server 1. The various DBs 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, and the communication device 4 via the network N. Alternatively, the control unit 11 may use the communication unit 14 to download a control program 1P from another computer via the network N, etc., and store it in the auxiliary storage unit 13.

[0016] The reading unit 15 reads a portable storage medium 1a, including CD (Compact Disc)-ROM and 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. Alternatively, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

[0017] User terminal 2 is a terminal used by vehicle users who use automobiles. In the automobile transaction system 100, it is assumed that vehicle users purchase automobiles through auto loans, residual value credit, etc., or rent automobiles through subscription or lease agreements. User terminal 2 consists of smartphones, tablet computers, laptop computers, PCs, etc. Hereafter, vehicle users will also be simply referred to as users, and automobiles will also be referred to as vehicles.

[0018] Figure 3 is a block diagram showing an example of the hardware configuration of a user terminal. 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 bus B.

[0019] The control unit 21 has one or more arithmetic processing units such as CPUs, MPUs, and GPUs. The control unit 21 provides various functions by reading and executing control programs 2P (programs, program products) stored in the auxiliary storage unit 23.

[0020] The main memory unit 22 is an SRAM, DRAM, flash memory, etc. The main memory unit 22 primarily temporarily stores data necessary for the control unit 21 to perform calculations.

[0021] The auxiliary storage unit 23 is a hard disk or SSD, and stores various data necessary for the control unit 21 to execute processing. The auxiliary storage unit 23 may also be an external storage device connected to the user terminal 2. Various databases, 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. Alternatively, the control unit 21 may use the communication unit 24 to download a 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 made of a liquid crystal panel or an organic EL (Electro-Luminescence) display, etc. The operation unit 26 can be made of, for example, a touch panel incorporated into the display panel 25, and can 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, mouse, etc.

[0024] The imaging unit 27 is, for example, a CCD camera or a CMOS camera, and acquires image data by photoelectric conversion of optical signals input via a CCD or CMOS, etc.

[0025] Owner terminal 3 is a terminal used by the owner of the vehicle. The owner of the vehicle may be a loan company, credit company, leasing company, etc. The operator of the vehicle transaction system 100 may also be the owner. Owner terminal 3 consists of a PC, laptop computer, tablet computer, smartphone, etc.

[0026] Figure 4 is a block diagram showing an example of the hardware configuration of the owner terminal. 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 bus B.

[0027] The control unit 31 has one or more arithmetic processing units such as CPUs, MPUs, and GPUs. The control unit 31 provides various functions by reading and executing control programs 3P (programs, program products) stored in the auxiliary storage unit 33.

[0028] The main memory unit 32 is an SRAM, DRAM, flash memory, etc. The main memory unit 32 primarily temporarily stores data necessary for the control unit 31 to perform calculations.

[0029] The auxiliary storage unit 33 is a hard disk or SSD, and stores various data necessary for the control unit 31 to execute processing. The auxiliary storage unit 33 may also be an external storage device connected to the owner terminal 3. Various databases, 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. Alternatively, the control unit 31 may use the communication unit 34 to download a 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 or mouse. The display unit 36 ​​includes a liquid crystal display panel or an organic EL (electroluminescence) display panel, etc. The display unit 36 ​​displays user information output by the server 1. Alternatively, the input unit 35 and the display unit 36 ​​may be integrated to form a touch panel display. The owner terminal 3 may also display information on an external display device.

[0032] Communication device 4 is a device installed in a vehicle. Communication device 4 has the function of measuring its own position using a satellite positioning system, etc., and the function of transmitting the measured position to server 1 via a mobile communication network. Communication device 4 is composed of, for example, a communication-type drive recorder.

[0033] Figure 5 is a block diagram showing an example of the hardware configuration of a communication device. 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 bus B.

[0034] The control unit 41 has one or more arithmetic processing units such as CPUs, MPUs, and GPUs. Unit 41 controls the communication device 4 by reading and executing the control program 4P (program, program product) stored in the auxiliary storage unit 43.

[0035] The main memory unit 42 is an SRAM, DRAM, flash memory, etc. The main memory unit 42 primarily temporarily stores data necessary for the control unit 41 to perform arithmetic processing.

[0036] The auxiliary storage unit 43 is an SD memory card or SSD, and stores various data necessary for the control unit 41 to perform processing. The auxiliary storage unit 43 also stores location information acquired by the location 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 is equipped with a SIM (Subscriber Identity Module) card 441 and transmits location information and images to the server 1 using the mobile communication network.

[0038] The position acquisition unit 45 consists of a GPS (Global Positioning System) receiver and the like. The position acquisition unit 45 receives radio waves from GPS satellites. Based on the received satellite radio waves, the position acquisition unit 45 determines its own position.

[0039] The imaging unit 46 is composed of, for example, a CCD camera or a CMOS camera. The imaging unit 46 acquires image data by photoelectric conversion of optical signals input via the CCD or CMOS.

[0040] Next, the database used by the automobile trading system 100 will be described. Figure 6 is an explanatory diagram showing an example of a vehicle database. The vehicle database 131 stores information on vehicles handled by the automobile trading system 100. The vehicle database 131 includes columns for vehicle ID, manufacturer, vehicle type, grade, body color, initial registration date, and price. The vehicle ID column stores a vehicle ID that can uniquely identify a vehicle. The vehicle ID only needs to be able to uniquely identify each vehicle in the automobile trading system 100. The vehicle ID may be issued independently, but it may also be a vehicle identification number (VIN) as defined in ISO 3833 or one issued by the Ministry of Land, Infrastructure, Transport and Tourism. The assigned chassis number may be used. The Manufacturer column stores the vehicle's manufacturer. The Vehicle Type column stores the vehicle type. The Grade column stores the vehicle's grade. The Body Color column stores the vehicle's body color. The First Registration Date column stores the first registration date. The first registration date is the month and year in which the vehicle was first applied for and accepted by the Land Transport Bureau. The Price column stores the vehicle's price at the time of first registration. In the example in Figure 6, the unit of the stored vehicle price is 10,000 yen.

[0041] Figure 7 is an explanatory diagram showing an example of a residual value database. The residual value database 132 stores the residual value of a vehicle. The residual value database 132 consists of a header 1321 and a table 1322. Header 1321 stores the vehicle ID, vehicle type, grade, and body color. Table 1322 stores the residual value rate and residual value, associated with the vehicle's total mileage and the number of years elapsed from the present. The header 1321 and table 1322 shown in Figure 7 are created and stored for each vehicle handled by the automobile trading system 100. The residual value database 132 is created when calculating the basic fee and billing unit price, which will be described later.

[0042] Figure 8 is an explanatory diagram showing an example of a fare database. Fare database 133 stores vehicle usage fees. Fare database 133 includes columns for vehicle ID, base fare, billing unit price, and calculation date. The vehicle ID column stores the vehicle ID. The base fare column stores the fixed portion of the fee that does not change with each billing cycle. The billing unit price column stores the unit price that forms the basis for calculating the variable usage fee (additional charge) that changes with each billing cycle. The usage fee is calculated based on the distance traveled. Details will be described later. The calculation date column stores the date on which the fee was calculated. In this specification, usage fees are described as being paid on a monthly basis, but this is not the only option.

[0043] Figure 9 is an explanatory diagram showing an example of a user database. User database 134 stores information about vehicle users. User database 134 includes columns for user ID, name, gender, date of birth, and address. The user ID column stores a user ID that uniquely identifies the user. The name column stores the user's name. The gender column stores the user's gender. The date of birth column stores the user's date of birth. The address column stores the user's address.

[0044] Figure 10 is an explanatory diagram showing an example of a contract database. The contract database 135 stores information about the vehicle usage contract concluded between the owner and the user. The contract database 135 includes columns for User ID, Vehicle ID, Payment Start Month, Payment End Month, Rate Plan, Monthly Base Charge, Billing Unit Price, and Bonus Payment. The User ID column stores the User ID. The Vehicle ID column stores the Vehicle ID of the contracted vehicle. The Payment Start Month column stores the year and month in which the user begins or has begun paying the charges. The Payment End Month column stores the year and month in which the user ends or has ended paying the charges. The Rate Plan column stores the name of the rate plan. The Monthly Base Charge column stores the monthly base charge. The Billing Unit Price column stores the unit price used when calculating the usage charge. In this specification, the usage charge is determined according to the distance traveled. The Billing Unit Price is the usage charge per unit distance traveled, for example, per kilometer. The bonus payment column stores the payment month and amount when the usage fee is paid via bonus payment.

[0045] Figure 11 is an explanatory diagram showing an example of a device database. Device DB 136 stores information about communication device 4. Device DB 136 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 communication device 4 is installed. The Terminal Management Number column stores the management number of communication device 4. The IMEI column stores the International Mobile Equipment Identifier (IMEI). The SIM column stores the terminal serial number of the SIM card 441 provided by the communication device 4.

[0046] Figure 12 is an explanatory diagram showing an example of a location information database. The location information database 137 stores the location of the communication device 4, i.e., the location of the vehicle. The location information database 137 includes columns for IMEI, SIM, Trip Start, Trip End, Time, Latitude, and Longitude. The IMEI column stores the IMEI assigned to the communication device 4. The SIM column stores the terminal serial number of the SIM card 441 equipped in the communication device 4. The Trip Start column is flagged if it is a record corresponding to the start of a trip. The Trip End column is flagged if it is a record corresponding to the end of a trip. A trip is a set of vehicle operations. The start time of a trip is the time the engine is started, and the end time of a trip is the time the engine is stopped. For example, in Figure 12, a check mark indicates that the flag is set. The Time column stores the time the location was observed. The Latitude column stores the latitude indicating the location. The Longitude column stores the longitude indicating the location. The coordinates indicating location are not limited to latitude and longitude in a geographic coordinate system; they can also be UTM coordinates or plane rectangular coordinates.

[0047] Figure 13 is an explanatory diagram showing an example of a mileage database. The mileage database 138 stores the mileage for each trip. The mileage database 138 includes columns for vehicle ID, IMEI, start, end, trip, and mileage. 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 the sequence number. The mileage column stores the mileage of the trip. In the example in Figure 13, the unit is meters (m).

[0048] Figure 14 is an explanatory diagram showing an example of a monthly total distance database. The monthly total distance database 139 stores the total monthly mileage for each vehicle. The monthly total distance database 139 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 used for calculation. The total distance column stores the total mileage for the target month. The total mileage is obtained by extracting data for the target month from the mileage database 138. This value is the sum of the mileage recorded from the extracted records. For trips spanning multiple months, it should be predetermined whether the determination is based on the start date and time or the end date and time.

[0049] Figure 15 is an explanatory diagram showing an example of a billing database. Billing database 13A stores the amount of usage charges billed to users. Billing database 13A includes columns for User ID, Vehicle ID, IMEI, Usage Month / Year, Base Charge, Usage Charge, and Usage Charge. The User ID column stores the user ID. The Vehicle ID column stores the vehicle ID of the vehicle used by the user. The IMEI column stores the IMEI assigned to communication device 4. The Usage Month / Year column stores the usage month of the vehicle subject to billing. The Base Charge column stores the amount of the base charge billed. If bonus payments are set up, the base charge will be different for regular months and bonus months. The Usage Charge column stores the amount of the usage charge billed. The Usage Charge column stores the amount of the usage charge billed (= base charge + usage charge).

[0050] Next, we will explain how to calculate the base fee and the unit price that form the basis of the usage fee. Hereinafter, the decrease in residual value will be referred to as depreciation. In this specification, we focus on the fact that there are various factors that cause the residual value of a vehicle to decrease (depreciation factors), but broadly speaking, there are "factors that depreciate according to the amount used" and "factors that depreciate according to the passage of time even if not used". The former is depreciation determined by the total mileage of the vehicle. The latter is depreciation determined by the passage of time since the initial registration, even if the total mileage is 0. Based on these matters, depreciation due to the passage of time, regardless of the amount of total mileage of the vehicle, will be mainly recovered by including it in the base fee, and depreciation due to total mileage will be mainly recovered as a usage-based fee. The following will explain with a specific example in mind.

[0051] First, let's explain the residual value data that forms the basis of the calculation. We obtain residual value data (residual value rate and residual value) associated with each vehicle model, grade, and body color, as well as the number of years elapsed since the initial registration month and the total mileage. Hereafter, this residual value data will be referred to as the basic residual value data. Server 1 obtains the residual value data, for example, by downloading it from an information provider, and stores it in the auxiliary storage unit 13, etc. Even if the vehicle model, grade, and body color are the same, the residual value will differ depending on the rating determined by the condition of the vehicle, etc. In this embodiment, we obtain residual value data for ratings that indicate a condition better than average.

[0052] Next, determine the number of years elapsed since the initial registration month of the vehicle in question, either at the time of calculation or the planned start date of use. For example, if the calculation is performed in April 2023 for a vehicle that was initially registered in December 2020, the number of years elapsed is 2 years.

[0053] Next, we calculate the estimated total number of years elapsed by adding the estimated period of the service agreement. In other words, we calculate the number of years elapsed at the end of the service period. In the example above, if the service period (specified period) is 3 years from April 2023, the estimated total number of years elapsed is 2 years + 3 years = 5 years.

[0054] Next, a table is created that associates the assumed total elapsed years and total mileage with the residual value rate and residual value, using the basic residual value data. One example is residual value DB132 shown in Figure 7. In the example above, the assumed total elapsed years are 5 years = 60 months. However, Figure 7 also shows tables for usage periods of 1 year and 5 years, i.e., when the assumed total elapsed years are 3 years = 36 months and 7 years = 84 months.

[0055] Referencing the created residual value DB132, determine the residual value and residual value rate for a total mileage of 0 km over the assumed total elapsed years. In the example in Figure 7, for an assumed total elapsed years of 3 years, the residual value is 2,507,000 yen and the residual value rate is 89.3%.

[0056] The principal payment, which is the total amount to be collected as a basic fee, is calculated using the residual value or residual value rate for a specified total mileage of 0 km. For example, using the residual value rate, it is calculated using the following formula (1).

[0057] Principal = Vehicle price - (Vehicle price × residual value rate) + Maintenance fee + Taxes + Miscellaneous expenses ... (1) The vehicle price is the initial registration price recorded in the price column of the vehicle database. Maintenance fees cover costs for vehicle inspections, regular maintenance, etc., during the usage period. Taxes include automobile tax (light vehicle tax), environmental performance tax, automobile weight tax, and consumption tax. Miscellaneous expenses include compulsory automobile liability insurance premiums, inspection and registration fees, garage certificate fees, and delivery fees.

[0058] The basic fee is calculated from the principal amount using the following formula (2).

[0059] Basic fee = (Principal + Interest and fees) / Number of payments ... (2) If payments are made monthly during the usage period, the number of payments will be equal to the number of months in the usage period. If the usage period is 3 years, the number of payments will be 36.

[0060] The calculated base fare is stored in the fare database DB133. The reason for calculating the base fare based on the residual value or residual value rate for a vehicle with a total mileage of 0 km is based on the aforementioned idea that the decrease in residual value due to the passage of time, regardless of the total mileage of the vehicle, is recovered as a base fare. Note that the calculation methods for the base fare using equations (1) and (2) are examples only and are not the only methods.

[0061] Next, we will explain how to calculate the invoice unit price. First, from the residual value data for each total mileage over the assumed total number of years elapsed for the target vehicle, we identify two corresponding residual values ​​based on any two total mileages. By dividing the difference between the identified residual values ​​by the difference between the two total mileages, we can find the depreciation per unit distance.

[0062] Figure 16 is an explanatory diagram showing an example of cost unit price calculation. The cost unit price is the unit price that forms the basis of the invoice unit price. In the example shown in Figure 16, the assumed total elapsed time is 3 years = 36 months, and the two residual value combinations are 0 km and other distances. The depreciation per kilometer of mileage (absolute value) when the total mileage is 18,000 km is calculated as follows. The two residual value combinations do not have to be 0 km; for example, the depreciation per kilometer of mileage can be calculated from the residual value for a total mileage of 18,000 km and the residual value for a total mileage of 24,000 km.

[0063] Cost per unit = (2,507 thousand yen - 2,423 thousand yen) / (18,000 - 0) = 5 yen (rounded to the first decimal place) Calculating for other total distances will yield the values ​​in the kilometer row of Figure 16. Based on the multiple depreciation values ​​(absolute values) obtained, the value to be used in subsequent processing (called the cost unit price) is determined. For example, the maximum value, median, or average value from among the multiple depreciation values ​​(absolute values) will be used as the cost unit price. If the maximum value is adopted, the cost unit price will be 6 yen.

[0064] Furthermore, the invoiced unit price is determined by adding profit, the amount equivalent to the various expenses necessary for billing, and consumption tax to the cost unit price. Expenses include, for example, administrative fees related to billing, transfer fees paid to financial institutions, and fees paid to payment collection agencies. For example, if a profit of 10 yen is added, the cost with profit (distance cost) is 16 yen. Adding 5% for expenses and 10% consumption tax, the unit price to be billed to the user (invoiced unit price) becomes 18 yen, as shown below.

[0065] Invoice unit price = 16 yen × (1 + 0.05) × 1.1 = 18 yen (rounded to the first decimal place) As described above, the method for determining the base charge and the unit price involves using an average rating value for depreciation due to the passage of time, regardless of the total mileage of the vehicle, and recovering this as the base charge. Depreciation due to total mileage is then recovered as a usage charge. A pricing plan calculated using this method is called the Standard Plan.

[0066] Next, we will explain the information processing performed by the automobile trading system 100. Figure 17 shows the fee calculation. This is a flowchart illustrating an example of the processing procedure. The fee calculation process is initiated by a request from a person who intends to become a customer of the automobile transaction system 100 and a user of a vehicle (a prospective user). For the sake of explanation, the prospective user will be referred to as the user, and the terminal used will be referred to as user terminal 2.

[0067] The user operates user terminal 2 to instruct the system to calculate the fare. The control unit 21 of user terminal 2 sends a calculation request to server 1 (step S1). The control unit 11 of server 1 receives the calculation request (step S2). The control unit 11 sends an input screen to user terminal 2 for entering information about the vehicle in question (step S3). The control unit 21 of user terminal 2 receives the input screen (step S4). The control unit 21 displays the input screen on display panel 25 (step S5). The user enters information about the vehicle used into the input screen. The information to be entered is the vehicle type, grade, and color (body color). The control unit 21 accepts the input (step S6). The user may also be asked to enter the vehicle usage period in addition to the vehicle information. The control unit 21 sends the accepted vehicle type, grade, and color to server 1 (step S7). The control unit 11 of server 1 receives the vehicle type, grade, and color (step S8). The control unit 11 determines whether or not the vehicle is in stock (step S9). In the automobile trading system 100, it is assumed that vehicles are procured from affiliated dealers, so the control unit 11 queries the affiliated dealer's system to determine whether or not there is stock. If the control unit 11 determines that there is stock (YES in step S9), it identifies the estimated total elapsed years (step S10). From the vehicle information obtained from the inquiry to the dealer, the control unit 11 calculates the elapsed years from the initial registration date to the processing date. It adds the usage period to the current elapsed years to identify the elapsed years at the end of the usage period = estimated total elapsed years. If the user has specified a usage period, the specified period is added. If the user has not specified a usage period, it identifies the estimated total elapsed years by assuming 3 years, 5 years, 7 years, etc. At this time, multiple estimated total elapsed years may be identified, and subsequent processing may be performed for each estimated total elapsed years. The control unit 11 creates a residual value / residual value rate table for the estimated total elapsed years (step S11). The residual value DB 132 shown in Figure 7 is an example. The control unit 11 calculates the basic charge (step S12). The control unit 11 calculates the invoice unit price (step S13). The control unit 11 stores the calculated basic charge and invoice unit price in the charge DB 133 (step S14). The control unit 11 creates a charge screen including the basic charge and invoice unit price and sends it to the user terminal 2 (step S15).The control unit 21 of the user terminal 2 receives the fare screen and displays it on the display panel 25 (step S16). The control unit 21 terminates the process. If the control unit 11 determines that there is no stock (NO in step S9), it creates a screen notifying the user that there is no stock and sends it to the user terminal 2 (step S17). The control unit 21 of the user terminal 2 receives the screen and displays it on the display panel 25 (step S18). The user inputs whether to terminate or not and search for other vehicles. The control unit 21 accepts the input (step S19). The control unit 21 determines whether to terminate or not (step S20). If the control unit 21 determines not to terminate (NO in step S20), it returns the process to step S5. If the control unit 21 determines to terminate (YES in step S20), it terminates the process.

[0068] Figure 18 is a flowchart showing an example of the procedure for calculating the basic fee. The control unit 11 of Server 1 refers to the residual value DB 132 to identify the residual value rate for a total mileage of 0 km over the assumed total number of years elapsed (step S31). The control unit 11 calculates taxes such as automobile tax and consumption tax (step S32). The control unit 11 obtains various expenses and fees such as compulsory automobile liability insurance and garage certificate (step S33). The control unit 11 calculates the basic fee (step S34). The basic fee is calculated, for example, using formula (1) described above. The control unit 11 returns the process to the caller.

[0069] Figure 19 is a flowchart showing an example of the procedure for calculating the invoice unit price. The control unit 11 of server 1 refers to the residual value DB 132 and selects two total mileage (step S41). The control unit 11 calculates the depreciation per unit kilometer (step S42). The control unit 11 divides the difference in residual values ​​corresponding to the two selected total mileage by the difference in total mileage to calculate the depreciation per kilometer. The control unit 11 calculates the cost. The control unit 11 determines whether there are other combinations of total mileage (step S43). If the control unit 11 determines that there are other combinations of total mileage (YES in step S43), it returns the process to step S41. If the control unit 11 determines that there are no other combinations of total mileage (NO in step S43), it determines the cost unit price from all the calculated depreciation per unit kilometer (step S44). For example, the maximum value of depreciation, the average value of depreciation, or the median value of depreciation is used as the cost unit price. The control unit 11 calculates the invoice unit price by adding profit, necessary expenses for billing, consumption tax, etc. to the cost unit price (step S45). The control unit 11 returns the process to the caller.

[0070] Based on the base fee and billing unit price determined through the fee calculation process, the user enters into a vehicle usage agreement with the owner. After the usage agreement is concluded, the vehicle is delivered, and the user begins using it.

[0071] Next, we will explain how usage fees are calculated. Usage fees are calculated for each predetermined period, in this case, monthly. To calculate usage fees, it is necessary to calculate the total mileage traveled during the predetermined period, which is the basis for calculating the usage-based fee, in this case, the total monthly mileage. We will now explain the process for determining the total monthly mileage.

[0072] Figure 20 is a flowchart illustrating an example of the location information acquisition process. The location information acquisition process involves acquiring location information from a communication device 4 installed in the vehicle and storing the vehicle's location in the location information DB 137. The communication device 4 detects when the vehicle's engine has started and begins processing. The control unit 41 of the communication device 4 sends an authentication request to the server 1 (step S61). The control unit 11 of the server 1 receives the authentication request (step S62). The control unit 11 performs authentication (step S63). For example, the control unit 11 performs SMS authentication. The control unit 11 sends the authentication result to the communication device 4 (step S64). The control unit 41 of the communication device 4 receives the authentication result (step S65). The control unit 41 determines whether the authentication was successful or not (step S66). If the control unit 41 determines that the authentication failed (NO in step S66), it terminates the process. If the control unit 41 determines that authentication was successful (YES in step S66), it sends the positioning result from the position acquisition unit 45 to the server 1 (step S67). The control unit 11 of the server 1 receives the positioning result (step S68). The control unit 11 stores the vehicle's position information based on the positioning result in the position information DB 137 (step S69). The control unit 11 sends a response to the communication device 4 indicating that the position information has been stored (step S70). The control unit 41 of the communication device 4 receives the response (step S71). The control unit 41 determines whether or not to terminate the process (step S72). For example, if the control unit 41 detects that the vehicle's engine has stopped, it determines to terminate. If the control unit 41 determines not to terminate the process (NO in step S72), it returns to step S67 and continues the process. If the control unit 41 determines to terminate the process (YES in step S72), it sends a termination message to the server 1 (step S73). The control unit 11 of server 1 receives the termination (step S74). The control unit 11 stores the termination (step S75). For example, the control unit 11 sets the Trip termination flag for the latest location information. The control unit 11 sends a response to the communication device 4 (step S76). The control unit 41 of the communication device 4 receives the response (step S77) and terminates processing.

[0073] Figure 21 is a flowchart showing an example of the procedure for calculating the distance traveled. The distance traveled calculation process calculates the vehicle distance traveled for each trip based on the location information stored in the location information DB 137. The control unit 11 of Server 1 acquires the location information included in one trip to be processed (step S91). Based on the location information, the control unit 11 plots the start position, end position, and intermediate passing positions of the trip on the electronic map (step S92). At that time, the control unit 11 checks the overlap between each point and the road line data and corrects it so that all points lie on the road (map matching is performed). The control unit 11 generates a route from the start position to the end position using the plotted positions and the road line data or road network data. Step S93). The control unit 11 calculates the distance traveled from the route and road network data (Step S94). The control unit 11 stores the distance traveled in the distance traveled DB 138 (Step S95). The control unit 11 determines whether to terminate or not (Step S96). The control unit 11 determines to terminate if there are no trips for which the distance traveled has not been calculated, and to not terminate otherwise. If the control unit 11 determines not to terminate (NO in Step S96), it returns to Step S91 and continues processing. If the control unit 11 determines to terminate (YES in Step S96), it terminates the process. It is desirable that the distance traveled calculation process be performed for each trip for which the end of the trip is detected during the location information acquisition process. In this case, Step S96 is unnecessary.

[0074] Figure 22 is a flowchart showing an example of the procedure for calculating the total monthly mileage. The total monthly mileage calculation process calculates the total monthly mileage for each vehicle. The total monthly mileage calculation process is executed by a monthly batch process or the like. The control unit 11 of Server 1 obtains the period to be calculated (step S111). The period is, for example, from the 1st of the previous month to the last day of the previous month. It is not limited to this, and may be from the 21st of the previous month to the 20th of the current month, for example. The control unit 11 obtains the mileage data for each trip within the target period from the mileage DB 138 (step S112). As mentioned above, if the start and end of a trip spans across months, it should be predetermined whether to determine the start date and time or the end date and time. The control unit 11 selects the vehicle ID to be calculated (step S113). The control unit 11 adds up the mileage of each trip for the selected vehicle ID and calculates the total monthly mileage (step S114). The control unit 11 stores the calculated total monthly mileage in the monthly total mileage DB 139 (step S115). The control unit 11 determines whether or not there are any unprocessed vehicle IDs (step S116). If the control unit 11 determines that there are any unprocessed vehicle IDs (YES in step S116), it returns to step S113 and processes the unprocessed vehicle IDs. If the control unit 11 determines that there are no unprocessed vehicle IDs (NO in step S116), it terminates the process.

[0075] Figure 23 is a flowchart illustrating an example of the procedure for calculating usage fees. The usage fee calculation process calculates the monthly usage fee to be billed to each subscriber. The usage fee calculation process is executed by a monthly batch process, etc. It is assumed that the calculation of the total monthly mileage has been completed before the usage fee calculation process is executed. The control unit 11 of Server 1 extracts information on the users to be calculated from the user DB 134 (step S131). The control unit 11 selects the users to be processed (step S132). The control unit 11 obtains the total monthly mileage of the selected users from the total monthly mileage DB 139 (step S133). The control unit 11 obtains the billing unit price for the users from the contract DB 135 and calculates the usage fee by multiplying it by the total monthly mileage (step S134). The control unit 11 calculates the usage fee by adding the monthly basic fee obtained from the contract DB 135 to the calculated usage fee (step S135). The control unit 11 stores the basic charge, usage charge, and usage charge in the billing DB 13A (step S136). Based on the billing information stored in the billing DB 13A, billing processing is performed separately for the users. The control unit 11 determines whether or not there are any users who have not yet been processed (step S137). If the control unit 11 determines that there are users who have not yet been processed (YES in step S137), it returns the process to step S132. If the control unit 11 determines that there are no users who have not yet been processed (NO in step S137), it terminates the process. After calculating the usage charge, the user may be notified of the calculated usage charge. For example, the notification may be made by email, push notification, etc.

[0076] Figure 24 is an explanatory diagram showing an example of a usage fee display screen. The usage fee display screen d01 is a screen that displays the monthly usage fee. The usage fee display screen d01 includes the usage fee d011, payment information d012, basic fee d013, and usage-based fee d014. The usage fee d011 shows the usage fee to be billed. The payment information d012 shows the payment method, withdrawal date, and other payment dates. The basic fee d013 shows the monthly basic fee. The usage-based fee d014 shows the usage-based fee according to the total monthly mileage.

[0077] In this embodiment, the usage fee is calculated based on the vehicle's mileage. Therefore, the usage fee is reasonable regardless of whether the user drives long or short distances. If the owner is a leasing company or the like, and the operator of the automobile transaction system 100 collects the usage fees, the operator may hold the monthly usage fee until the end of the usage period, and then pay the total amount (cumulative value) of the usage fee to the owner after the period expires. In this case, it is desirable to calculate the cumulative value of the usage fee each month for each contract and store it in the contract DB 135. This allows for verification of how much additional charges have been collected during the usage period. Furthermore, storing the cumulative value allows for prompt payment processing to the owner after the end of the usage period.

[0078] (Embodiment 2) This embodiment relates to a pricing structure in which no usage-based charges are applied if the total monthly mileage is within a specified value, and usage-based charges are applied if the mileage exceeds the specified value, according to the distance exceeding the limit. For example, if the total monthly mileage is within 500km, no usage-based charges are incurred, and only the basic fee is charged. This pricing plan is called the "free mileage up to 500km per month" plan. The reason for setting the limit at 500km per month is that, according to a survey of car owners, the average monthly mileage is 500km. Therefore, it is considered reasonable to offer free mileage up to 500km per month, but this embodiment is not limited to this. For example, it may be free mileage up to 300km per month, or free mileage up to 700km per month. Pricing plans that do not charge usage-based charges when the total monthly mileage is within a specified value are collectively called "flat-rate plans."

[0079] In calculating the basic fee and billing unit price for the plan with no charges up to 500km per month, it is assumed that the user will drive the vehicle at least 500km each month during the usage period. That is, if the usage period is 36 months, the basic fee will be calculated assuming a total mileage of 18,000km. Furthermore, since a longer total mileage is assumed than in the standard plan, the vehicle rating acquired as residual value data will be an average condition rating, whereas in the standard plan, the vehicle condition will be rated as being above average. The difference between this embodiment and Embodiment 1 lies in the method of calculating the basic fee, which will be explained mainly below.

[0080] Figure 25 is an explanatory diagram showing another example of residual value database. The structure of residual value database 132 shown in Figure 25 is the same as that of residual value database 132 shown in Figure 7, so no explanation is given. As mentioned above, compared to the standard plan, the plan with no charges up to 500km per month uses residual value data with a lower rating, so both the residual value rate and residual value shown in Figure 25 are smaller than the values ​​shown in Figure 7.

[0081] The basic fee is calculated as follows: If the assumed elapsed time is 3 years = 36 months, the residual value DB132 is referenced to determine the residual value rate for a total mileage of 18,000 km over the assumed total elapsed time. In the example in Figure 25, it is 83.0%. Using this residual value rate, the basic fee is calculated using formula (1) shown in Embodiment 1. The difference in this embodiment is that Embodiment 1 uses the residual value rate for a total mileage of 0 km, whereas Embodiment 1 uses the residual value rate for a total mileage of 0 km.

[0082] Figure 26 is an explanatory diagram showing an example of cost unit calculation. The calculation method is the same as in Embodiment 1, which was explained with reference to Figure 16. Similar to Figure 16, the assumed total elapsed time is 3 years = 36 months, and the two residual value combinations are 0 km and other distances. However, it is not limited to this; a combination where one of the distances is not 0 km is also acceptable, for example, a residual value for a total mileage of 18,000 km and a residual value for a total mileage of 24,000 km. The depreciation per kilometer of mileage (absolute value) when the total mileage is 18,000 km is calculated as follows.

[0083] Cost per unit = (2,416 thousand yen - 2,331 thousand yen) / (18,000 - 0) = 5 yen (rounded to the first decimal place) If the maximum value is adopted as the cost unit price, the cost unit price will be 6 yen. Furthermore, the invoice unit price is determined by adding profit, the amount equivalent to the various expenses necessary for billing, and consumption tax to the cost unit price. The approach to determining the invoice unit price from the cost unit price is the same as in Embodiment 1.

[0084] The process performed in this embodiment is the same as that shown in the flowcharts from Figures 17 to 23. However, the residual value rate specified in step S31 of the basic fare calculation process (Figure 18) is the value corresponding to a total mileage of 18,000 km.

[0085] In the proposed plan for free mileage up to 500km per month, the fixed monthly base fee is higher than the standard plan. However, since no additional charges (metered rates) are incurred for total monthly mileage up to 500km, it is a more reasonable pricing plan than the standard plan for users whose vehicle mileage is expected to be around 500km per month.

[0086] (Embodiment 3) This embodiment is a pricing plan that reduces the fixed base fee compared to the Standard Plan. Focusing on the reduction of the base fee, it is called the Economy Plan. The Economy Plan is designed for users with a lower total monthly mileage than the Standard Plan. Therefore, while the Standard Plan uses a rating that indicates the vehicle is in better-than-average condition, this embodiment uses a rating that is even better than the Standard Plan. The difference between this embodiment and Embodiment 1 lies in the residual value data used to calculate the base fee and usage-based fee.

[0087] Figure 27 is an explanatory diagram showing another example of residual value database. The structure of residual value database 132 shown in Figure 27 is the same as that of residual value database 132 shown in Figure 7, so no explanation is given. As mentioned above, compared to the standard plan, the economy plan uses residual value data with a higher rating, so both the residual value rate and residual value shown in Figure 27 are larger than the values ​​shown in Figure 7.

[0088] The calculation methods for the basic charge and usage-based charge are the same as in Embodiment 1 (Standard Plan), so we will omit the explanation. Furthermore, the processing performed in this embodiment is the same as that shown in the flowcharts from Figures 17 to 23.

[0089] In the economy plan proposed in this embodiment, the fixed monthly base fee is lower than that of the standard plan. Therefore, it is a suitable plan for users whose primary purpose is to own and admire a vehicle, or to simply enjoy driving, rather than using the vehicle practically as a means of transportation, and who tend to drive fewer miles and derive joy from ownership.

[0090] (Embodiment 4) This embodiment relates to a method of adjusting the billing rates for the Standard Plan and Economy Plan in comparison to the Plan with no charges up to 500km per month. As mentioned above, residual value data is used to calculate the basic charge and usage charge for each plan. Again, the residual value differs depending on the rating indicating the condition of the vehicle. Depreciation is thought to have a positive correlation with total mileage, and based on the magnitude of the total mileage assumed for each plan, the residual value data of an average-rated vehicle is used for the Plan with no charges up to 500km per month, the residual value data of a vehicle with a rating slightly higher than average is used for the Standard Plan, and the residual value data of an even higher-rated vehicle is used for the Economy Plan, and the basic charge and usage charge are calculated accordingly. However, it is expected that regardless of the vehicle's rating, if it is used at the average monthly total mileage of 500km, the residual value assessed after several years will be an average value. In other words, if the use of the vehicle by a user contracted under the Standard Plan or Economy Plan is contrary to expectations, If the total monthly mileage during the usage period remains around 500km, the residual value at the end of the usage period may fall below the residual value assumed at the time of contract. Furthermore, while the usage-based charge is intended to recover the depreciation amount based on mileage, it is calculated assuming that the vehicle's rating remains unchanged, making it unlikely to compensate for any uncollected amounts in the basic charge. Therefore, the billing rates for the Standard Plan and Economy Plan will be adjusted using the billing rate for the plan with no charges up to 500km per month.

[0091] Figure 28 is an explanatory diagram showing the method for correcting distance costs. As with the previous examples, Figure 28 shows an example with a usage period of 36 months. The "Plan" column shows the name of the plan. The "Assumed Total Mileage" column shows the total mileage of the vehicle during the usage period assumed when calculating the fee. For the "Free up to 500km per month" plan, this is 18,000km. The Standard Plan and Economy Plan do not have an assumed total mileage set. The "Initial Residual Value" column shows the residual value at the end of the usage period when the total mileage that forms the basis of the base fee is 0km. Similarly, the "Initial Residual Value" column shows the residual value at the end of the usage period when the total mileage is 0km. The "Base Cost" column shows the cost unit price calculated in the billing unit price processing for each plan. The "Residual Value at Expiry" column shows the residual value at the end of the usage period for each plan when the total mileage during the usage period is 18,000km. The upper column showing the difference from the fixed-rate plan shows the difference between the residual value at the end of the Standard or Economy plan and the residual value at the end of the plan with free mileage up to 500km per month (reference residual value data). The column showing the residual value rate at the end of the usage period shows the residual value rate at the end of the usage period for each plan, assuming a total mileage of 18,000km during the usage period. The lower column showing the difference from the fixed-rate plan shows the difference between the residual value rate at the end of the Standard or Economy plan and the residual value rate at the end of the plan with free mileage up to 500km per month. The adjusted cost column shows the value obtained by dividing the value in the upper column showing the difference from the fixed-rate plan by 18,000. The distance cost column shows the cost unit price, which is the sum of the value in the distance cost column and the value in the adjusted cost column. The invoice unit price (excluding tax) column shows the invoice unit price with profit etc. added to the cost unit price. The invoice unit price (including tax) column shows the invoice unit price including consumption tax.

[0092] As described above, in the Standard Plan and Economy Plan, if the total mileage during the usage period reaches 18,000 km, which is the assumed total mileage for the plan with no charges up to 500 km per month, even if the residual value at the end of the usage period falls to the same value as the residual value for the plan with no charges up to 500 km per month, it is possible to recover the reduced residual value by adding the difference in residual value as an adjusted cost per kilometer to the cost unit price.

[0093] As described above, the invoice price is calculated after the cost unit price has been adjusted. The procedure for adjusting the cost unit price will be explained again using a flowchart. Figure 29 is a flowchart of an example of the cost adjustment procedure. The cost adjustment process is executed in place of step S45 in the invoice price calculation process shown in Figure 19. That is, the cost adjustment process is executed following step S44, and the process returns without executing step S45.

[0094] The control unit 11 of server 1 determines whether the plan being calculated is a flat-rate plan or not (step S151). In this case, the flat-rate plan is a plan where charges are free up to 500km per month. The specification of the rate plan to be calculated is accepted in step S6 of the rate calculation process shown in Figure 17. If the control unit 11 determines that it is not a flat-rate plan (NO in step S151), it obtains the residual value at the end of the usage period of the flat-rate plan and the residual value at the end of the usage period for the target plan if the total mileage during the usage period was 18,000km (step S152). The control unit 11 calculates the difference between the two obtained residual values ​​(step S153). The control unit 11 divides the difference in residual values ​​by the assumed total mileage (18,000km in this case) to calculate the adjusted cost (step S154). The control unit 11 calculates the distance cost (step S155). The distance cost is calculated by adding the adjustment cost to the cost unit price (base cost) obtained in step S44 of Figure 19. The control unit 11 calculates the invoice unit price from the distance cost (step S156). If the control unit 11 determines that it is a fixed-rate plan (in step S151) YES), step S156 is executed. The control unit 11 terminates the process.

[0095] In this embodiment, even if a user who has contracted for a Standard Plan or Economy Plan uses a vehicle and, contrary to expectations, the total monthly mileage during the contract period remains around 500km, and the residual value at the end of the contract period falls below the residual value assumed at the time of contract, and becomes the same level as the residual value of the plan with no charges up to 500km per month, it is possible to recover the amount that has fallen below the residual value by billing a usage-based fee at a billing rate that takes adjustment costs into account.

[0096] Furthermore, if the actual selling price of the vehicle after the expiration of the usage period falls below the assumed residual value anticipated at the time of the contract, an open-end method may be adopted, and the difference between the selling price and the assumed residual value may be collected from the user. Alternatively, a closed-end method may be adopted, and no additional collection from the user may be required. Whether to use an open-end or closed-end method should be determined in advance. However, the user and owner may also decide which method to use through consultation at the time of the contract.

[0097] (Embodiment 5) When calculating the base fee and billing unit price, the key point is how to determine the estimated total mileage during the usage period. In this embodiment, a learning model is used to set the estimated total mileage for each user.

[0098] Figure 30 is an explanatory diagram showing an example of a training database. Training DB 13B stores training data for training the learning model described later. Training DB 13B includes columns for vehicle type, vehicle class, color, grade, age, gender, occupation, usage period, and total mileage. The columns from vehicle type to grade store data about vehicles that have been contracted for use in the past. The vehicle type column stores the name of the vehicle. The vehicle class column stores the class of the vehicle. Classes include, for example, compact car class, standard class, luxury (high-end car) class, ecology class, SUV class, and commercial vehicle class. The color column stores the body color of the vehicle. The grade column stores the grade of the vehicle. The columns from age to occupation store usage information. The age column stores the age of the user. It may also be an age range such as 40s. The gender column stores the gender of the user. The occupation column stores the occupation of the user. The usage period column stores the period during which the vehicle was used. The Total Mileage column stores the actual total mileage of the vehicle during the usage period. Training DB13B is generated by referencing User DB134, Contract DB135, Monthly Total Mileage DB139, etc.

[0099] Figure 31 is an explanatory diagram showing an example of the estimation model configuration. Estimation model M is a learning model that outputs an estimated value of the total mileage of a vehicle during a usage period when vehicle information, user information, and usage period are input. Estimation model M is a neural network generated by deep learning, and is composed of, for example, a CNN (Convolutional Neural Network). In the learning process, estimation model M learns using training data stored in training DB13B. In the example shown in Figure 31, the vehicle information is the vehicle type, vehicle class, color, and grade. The user information is age, gender, and occupation.

[0100] Figure 32 is a flowchart showing an example of the model generation process. The control unit 11 of server 1 acquires training data from the training DB 13B (step S171). The control unit 11 selects one record from the training data (step S172). The control unit 11 performs learning using the selected record of training data (step S173). For example, the control unit 11 inputs vehicle information, user information, and usage period included in the training data into the estimation model M, and optimizes parameters such as weights between neurons that constitute the estimation model M so that the estimated total mileage output from the estimation model M approaches the total mileage value included in the training data. The control unit 11 determines whether or not there are any unprocessed records that have not been used for learning (step S174). If the control unit 11 determines that there are unprocessed records (YES in step S174), it returns to step S172 and continues processing. If the control unit 11 determines that there is no unprocessed training data (NO in step S174), it stores the learned estimated model M (step S175) and terminates processing.

[0101] Figure 33 is a flowchart showing another example of the procedure for calculating charges. The user operates user terminal 2 to instruct the user to calculate charges. The control unit 21 of user terminal 2 sends a calculation request to server 1 (step S181). The control unit 11 of server 1 receives the calculation request (step S182). The control unit 11 sends an input screen to user terminal 2 for entering vehicle information, usage period, etc. (step S183). The control unit 21 of user terminal 2 receives the input screen (step S184). The control unit 21 displays the input screen on display panel 25 (step S185). The user enters information about the vehicle used into the input screen. The information to be entered is the vehicle type, grade and color (body color), and usage period. The user may also be able to enter their desired rate plan. Regarding the flat-rate plan, the total monthly mileage for which usage charges are not billed is determined by the total mileage during the usage period, so the upper limit of the monthly total mileage for which the flat rate applies is not displayed on the input screen. The control unit 21 accepts the input (step S186). The control unit 21 transmits the accepted vehicle type, grade, color, and usage period to the server 1 (step S187). The control unit 11 of the server 1 receives the vehicle type, grade, color, and usage period (step S188). The control unit 11 determines whether or not there is stock (step S189). In the automobile trading system 100, it is assumed that vehicles are procured from affiliated dealers, so the control unit 11 queries the affiliated dealer's system to determine whether or not there is stock. If the control unit 11 determines that there is stock (YES in step S189), it identifies the estimated total elapsed years (step S190). From the vehicle information obtained from the inquiry to the dealer, the control unit 11 calculates the elapsed years from the initial registration date to the processing date. It adds the usage period specified by the user to the current elapsed years to determine the elapsed years at the end of the usage period = estimated total elapsed years. The control unit 11 estimates the total mileage (step S191). Specifically, the control unit 11 inputs user information, vehicle information, and usage period into the estimation model M, and obtains an estimated total mileage from the estimation model M. The control unit 11 creates a residual value / residual value rate table for the assumed total elapsed years, taking into account the estimated total mileage (step S192). The control unit 11 adjusts the vehicle rating when obtaining residual value data based on the estimated total mileage.The control unit 11 calculates the basic charge (step S193). The control unit 11 calculates the billing unit price (step S194). In calculating the flat-rate plan, the estimated total mileage is used as the assumed total mileage to calculate the basic charge and billing unit price. The control unit 11 stores the calculated basic charge and billing unit price in the charge DB 133 (step S195). The control unit 11 creates a charge screen including the basic charge and billing unit price and sends it to the user terminal 2 (step S196). The charge screen for the flat-rate plan includes an upper limit distance for which the monthly charge is fixed, calculated by dividing the estimated total mileage by the number of months of the usage period. For example, if the estimated total mileage is 14,400 km and the number of months of the usage period is 36 months, the monthly upper limit distance will be 400 km. The control unit 21 of the user terminal 2 receives the charge screen and displays it on the display panel 25 (step S197). The control unit 21 terminates processing. If the control unit 11 determines that there is no stock (NO in step S189), it creates a screen notifying the user that there is no stock and sends it to the user terminal 2 (step S198). The control unit 21 of the user terminal 2 receives the screen and displays it on the display panel 25 (step S199). The user inputs whether to terminate or continue searching for other vehicles. The control unit 21 accepts the input (step S200). The control unit 21 determines whether to terminate or not (step S201). If the control unit 21 determines not to terminate (NO in step S201), it returns the process to step S185. If the control unit 21 determines to terminate (YES in step S201), it terminates the process.

[0102] In this embodiment, the total mileage during the usage period is estimated using the estimation model M, making it possible to accurately estimate the residual value and residual value rate at the end of the usage period.

[0103] (Interpolation of residual value data) As mentioned above, residual value data is assumed to be obtained from information providers. Therefore, the residual value data obtained is discrete, and it is anticipated that residual value data necessary for fee calculation may not be available. In such cases, it will be calculated by interpolation from the available data. For example, if residual value data for 3 years (36 months) and 4 years (48 months) is available, and residual value data for 3.5 years (42 months) is needed, the residual value for 3.5 years can be obtained by dividing the difference between the residual value data for 4 years and the residual value data for 3 years by 12 to find the monthly depreciation, multiplying the calculated depreciation by 6, and subtracting this value from the residual value for 3 years.

[0104] Interpolation for distance is similar to the concept of cost per distance. If residual value data for 18,000 km and 24,000 km is available, and residual value data for 20,000 km is needed, the difference in residual value data is divided by the difference in distance (6,000 km) to find the depreciation per km. By multiplying the calculated depreciation by 2,000 and subtracting this value from the residual value data for 18,000 km, it is possible to obtain the residual value data for 20,000 km.

[0105] Interpolating body color data is difficult, but the following methods can be employed. For example, if residual value data for solid white is available but not for pearl white, the residual value data for solid white can be used as a substitute since they are both white-based colors. Alternatively, if it is known that pearl white is slightly less popular than solid white, the residual value data for pearl white can be obtained by uniformly multiplying the residual value data for solid white by 0.9.

[0106] Furthermore, the popularity ranking of the main body color has been found to be 6th: Red, 7th: Brown / Beige, and 8th: Green. While residual value data for red and green is available, if residual value data for brown / beige is not available, the residual value for brown / beige will be set to an intermediate value between the red and green data.

[0107] The interpolation method described above is linear interpolation, but if another interpolation method is more suitable, that may be used instead.

[0108] The technical features (constituent elements) described in each embodiment are combinable with each other, and by combining them, new technical features can be formed.

[0109] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not in the sense described above, and all modifications within the sense and scope equivalent to the claims are intended.

[0110] Furthermore, while the claims are written in a format that includes claims referencing two or more other claims (multi-claim format), they are not limited to this. They may also be written in a format that includes multi-claims referencing at least one multi-claim (multi-multi-claim format). [Explanation of symbols]

[0111] 100: Automobile trading system 1: Server 1P: Control Program 11: Control Unit 12: Main memory 13: Auxiliary storage section 131: Vehicle Database 132: Residual Value Database 1321: Header 1322: Table 133: Pricing Database 134: User DB 135: Contract DB 136: Device DB 137: Location information DB 138: Mileage Database 139: Monthly Total Distance Database 13A: Billing DB 13B: Training DB 14: Communications Department 15: Reading section 16: Display Panel 1a: Portable storage medium 1b: Semiconductor memory 2: User terminal 21: Control Unit 22: Main memory 23: Auxiliary storage section 24: Communications Department 25: Display Panel 26:Operation section 27: Imaging Unit 2P: Control Program 3: Owner's terminal 3P: Control Program 4: Communication devices 41: Control Unit 42: Main memory 43: Auxiliary storage section 44: Communications Department 45: Position acquisition part 46: Imaging Department 4P: Control Program B: Bus N: Network

Claims

1. We obtain residual value data based on the vehicle's usage period and total mileage. Based on the residual value data, the basic fee for the vehicle within a predetermined period and the additional fee based on the mileage within the predetermined period are calculated. Output the billing amount calculated from the above basic fee and the above additional charges. An information processing method in which a computer performs the processing.

2. The aforementioned additional charge is calculated based on the distance-based rate calculated using the residual value data and the total distance traveled within a specified period. The information processing method according to claim 1.

3. The aforementioned unit price per mile is determined by selecting two residual values ​​with different mileage from residual value data for each mileage over the number of years elapsed since the vehicle's initial registration, and then determining the difference between the two selected residual values. The information processing method according to claim 2.

4. If the residual value data corresponding to a predetermined mileage for the number of years elapsed since the initial registration of the vehicle is less than the reference residual value data associated with the elapsed years and the mileage, an adjustment cost shall be calculated based on the amount equivalent to the difference and the mileage. The unit price per distance is adjusted using the calculated adjustment cost. The information processing method according to claim 3.

5. Generate multiple combinations of two residual values, For each generated pair, calculate the distance cost and adopt the highest value, median, or average as the distance cost. The information processing method according to claim 3.

6. The additional charge is calculated based on the adopted distance rate plus a predetermined value. The information processing method according to any one of claims 2 to 5.

7. Each time the aforementioned additional charge is calculated, the cumulative value of the calculated additional charges is determined. The calculated cumulative value is stored, After the expiration of the predetermined period, the stored cumulative value is output. The information processing method according to any one of claims 1 to 5.

8. The aforementioned basic fee is calculated based on the number of years elapsed since the initial registration of the vehicle at the end of the usage period. The information processing method according to any one of claims 1 to 5.

9. The aforementioned basic fee is calculated based on the difference between the vehicle's price when new, or its current residual value, and the residual value of the vehicle after a predetermined period has elapsed and the mileage is assumed to be zero. The information processing method according to any one of claims 1 to 5.

10. The basic fee and the per-mile rate are calculated by referring to a table that associates vehicle type, grade, body color, years elapsed since initial registration, and residual value data for each total mileage. The information processing method according to any one of claims 2 to 5.

11. We obtain residual value data based on the vehicle's usage period and total mileage. Based on the residual value data, the basic fee for the vehicle during a predetermined period and additional charges based on the mileage during that period are calculated. Output the billing amount calculated from the above basic fee and the above additional charges. An information processing program that instructs a computer to perform a task.

12. An acquisition unit that acquires residual value data based on the vehicle's usage period and total mileage, A calculation unit that calculates the basic charge for the vehicle within a predetermined period and an additional charge based on the mileage within the predetermined period, based on the residual value data, An output unit that outputs the billing amount calculated from the above basic charge and the above additional charge. An information processing device equipped with the following features.

13. The system receives a basic fee calculated using residual value data based on the vehicle's usage period and total mileage, an additional charge calculated using the residual value data based on the mileage within a specified period, and a total bill calculated based on the basic fee and the additional charge. The received basic charge, additional charges, and total billing amount are displayed. A display program that instructs a computer to perform a process.

Images