Information processing method, information processing program, information processing apparatus, and display program

Abstract

To provide an information processing method, an information processing apparatus, and a display program for outputting the amount to be billed for charge based on a travel distance of a vehicle.SOLUTION: An information processing method causes a computer to execute the processes of: acquiring residual value data based on a period of use and total travel distance of a vehicle; calculating, based on the residual value data, a basic fee within a predetermined period for the vehicle and an additional fee based on a travel distance within the predetermined period; and output the amount to be billed calculated based on the basic fee and the additional fee.SELECTED DRAWING: Figure 17

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 for a usage fee based on a vehicle's travel distance. [Background technology]

[0002] Residual value credit is used as a payment method for the purchase price of a passenger car (Patent Document 1, etc.). With residual value credit, the future trade-in price (residual value) is set in advance, and the monthly repayment amount is set based on the amount obtained by subtracting the residual value from the vehicle price. Residual value credit has the advantage that the amount of each repayment is cheaper than normal credit payments, because the residual value is kept unchanged until the contract maturity. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-67659 A Summary of the Invention [Problem to be solved by the invention]

[0004] In residual value credit, it is important to set the residual value accurately. The residual value of a vehicle is primarily inversely proportional to the number of years since initial registration and the total mileage, and the longer the number of years and the total mileage, the lower the residual value. However, in conventional residual value credit, although there are cases where a certain number of options are provided for the total mileage when setting the residual value, it is almost always set uniformly at the time of contracting. Therefore, for users who do not use the vehicle frequently and drive a small distance each time, a residual value lower than a reasonable residual value is set, which creates a sense of unfairness.

[0005] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an information processing method, an information processing program, an information processing device, and a display program for outputting a usage fee bill based on a vehicle's mileage. [Means for solving the problem]

[0006] An information processing method according to one aspect of the present application includes a process in which a computer executes a process of acquiring residual value data based on a vehicle's usage period and total mileage, calculating a basic fee for the vehicle within a specified period and an additional fee based on the mileage within the specified period based on the residual value data, and outputting a billing amount calculated from the basic fee and the additional fee. Effect of the Invention

[0007] In one aspect of the present application, it is possible to output a usage fee bill based on the vehicle's mileage. [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] FIG. 2 is an explanatory diagram showing an example of a vehicle DB; [Figure 7] FIG. 13 is an explanatory diagram showing an example of a residual value DB. [Figure 8] FIG. 11 is an explanatory diagram showing an example of a fee DB. [Figure 9] FIG. 11 is an explanatory diagram showing an example of a user DB. [Figure 10] FIG. 13 is an explanatory diagram showing an example of a contract DB. [Figure 11]FIG. 11 is an explanatory diagram illustrating an example of a device DB. [Figure 12] FIG. 2 is an explanatory diagram showing an example of a position information DB. [Figure 13] FIG. 11 is an explanatory diagram showing an example of a mileage DB. [Figure 14] FIG. 13 is an explanatory diagram showing an example of a monthly total distance DB. [Figure 15] FIG. 13 is an explanatory diagram showing an example of a billing DB. [Figure 16] FIG. 13 is an explanatory diagram showing an example of calculation of a unit cost price. [Figure 17] 13 is a flowchart showing an example of a procedure for fee calculation processing. [Figure 18] 13 is a flowchart showing an example of a procedure for a basic fee calculation process. [Figure 19] 13 is a flowchart showing an example of a procedure for a billing unit price calculation process. [Figure 20] 13 is a flowchart illustrating an example of a procedure for position information acquisition processing. [Figure 21] 10 is a flowchart showing an example of a procedure for a travel distance calculation process. [Figure 22] 13 is a flowchart showing an example of a procedure for calculating a total monthly traveling distance; [Figure 23] 13 is a flowchart showing an example of a procedure for a usage fee calculation process. [Figure 24] FIG. 13 is an explanatory diagram showing an example of a usage fee display screen. [Diagram 25] FIG. 13 is an explanatory diagram showing another example of a residual value DB. [Figure 26] FIG. 13 is an explanatory diagram showing an example of calculation of a unit cost price. [Figure 27] FIG. 13 is an explanatory diagram showing another example of a residual value DB. [Figure 28] FIG. 13 is an explanatory diagram showing a method of correcting a distance cost. [Figure 29] 13 is a flowchart showing an example of a procedure for cost correction processing. [Diagram 30] FIG. 13 is an explanatory diagram showing an example of a training DB. [Diagram 31] FIG. 2 is an explanatory diagram illustrating an example of the configuration of an estimation model. [Diagram 32]13 is a flowchart illustrating an example of a procedure for model generation processing. [Diagram 33] 13 is a flowchart illustrating another example of procedure of the fee calculation process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) An embodiment will be described below with reference to the drawings. Fig. 1 is an explanatory diagram showing an example of the configuration of an automobile trading system. An automobile trading system 100 includes a server 1, a user terminal 2, an owner terminal 3, and a communication device 4.

[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 central processing unit (CPU), a micro-processing unit (MPU), a graphics processing unit (GPU), 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., performed by the server 1, and realizing various functional units such as an acquisition unit, a calculation unit, an output unit, etc.

[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 an SSD (Solid State Drive) or the like, 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 vehicle DB 131, a residual value DB 132, a fee DB 133, a user DB 134, a contract DB 135, a device DB 136, a location information DB 137, a mileage DB 138, a monthly total distance DB 139, a billing DB 13A, and a training DB 13B. The auxiliary storage unit 13 may be an external storage device externally connected to the server 1. The various DBs and the like 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. 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 through a subscription or 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, an organic EL (Electro Luminescence) display, or the like. 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, or the like.

[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] Next, the databases used by the automobile transaction system 100 will be described. FIG. 6 is an explanatory diagram showing an example of a vehicle DB. The vehicle DB 131 stores information on vehicles handled by the automobile transaction system 100. The vehicle DB 131 includes a vehicle ID column, a manufacturer column, a vehicle model column, a grade column, a body color column, a first registration date column, and a price column. The vehicle ID column stores a vehicle ID that can uniquely identify a vehicle. 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 manufacturer column stores the manufacturer of the vehicle. The vehicle model column stores the vehicle model. The grade column stores the grade of the vehicle. The body color column stores the color of the vehicle body (body color). The first registration date column stores the first registration date. The initial registration date is the date when the vehicle was first registered at the local Land Transport Bureau and accepted. The price column stores the vehicle price at the time of initial registration. In the example of Figure 6, the vehicle price is stored in 10,000 yen.

[0041] FIG. 7 is an explanatory diagram showing an example of a residual value DB. Residual value DB 132 stores the residual value of a vehicle. Residual value DB 132 consists of a header 1321 and a table 1322. Header 1321 stores the vehicle ID, vehicle model, grade, and body color. Table 1322 stores the residual value rate and the residual value in association with the total mileage of the vehicle and the number of years elapsed from the present time. Header 1321 and table 1322 shown in FIG. 7 are created and stored for each vehicle handled by automobile trading system 100. Residual value DB 132 is created when calculating the basic fee and billing unit price described below.

[0042] FIG. 8 is an explanatory diagram showing an example of a fee DB. Fee DB 133 stores vehicle usage fees. Fee DB 133 includes a vehicle ID column, a base fee column, a billing unit price column, and a calculation date column. The vehicle ID column stores the vehicle ID. The base fee column stores the fixed portion of the fee that does not change for each billing. The billing unit price column stores the unit price that is the basis for calculating the usage fee (additional fee) that changes for each billing. 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, the usage fee is described as being paid monthly, but this is not limited to this.

[0043] FIG. 9 is an explanatory diagram showing an example of a user DB. The user DB 134 stores information on vehicle users. The user DB 134 includes a user ID column, a name column, a gender column, a date of birth column, and an address column. The user ID column stores a user ID that uniquely identifies a user. The name column stores the name of the user. The gender column stores the gender of the user. The date of birth column stores the date of birth of the user. The address column stores the address of the user.

[0044] FIG. 10 is an explanatory diagram showing an example of a contract DB. The contract DB 135 stores information on a vehicle usage contract concluded between an owner and a user. The contract DB 135 includes a user 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 billing unit price column, and a bonus payment column. The user ID column stores a user ID. The vehicle ID column stores the vehicle ID of the contracted vehicle. The payment start month column stores the year and month when the user starts or started paying the fee. The payment end month column stores the year and month when the user ends or 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 billing unit price column stores the unit price used to calculate the pay-per-use fee. In this specification, the pay-per-use fee is determined according to the mileage. The billing unit price is a pay-per-use fee per unit mileage, for example, per 1 km. The bonus payment column stores the payment month and amount when the usage fee is paid as a bonus.

[0045] 11 is an explanatory diagram showing an example of a device DB. The device DB 136 stores information about the communication device 4. The 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 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 (IMEI). The SIM column stores the terminal serial number of the SIM card 441 included in the communication device 4.

[0046] FIG. 12 is an explanatory diagram showing an example of a location information DB. The location information DB 137 stores the location of the communication device 4, that is, the location of the vehicle. The location information DB 137 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 IMEI assigned to 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. For example, in FIG. 12, 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. The coordinates indicating the location are not limited to the latitude and longitude of the geographic coordinate system, but may be coordinate values ​​of the UTM coordinate system or a plane rectangular coordinate system.

[0047] FIG. 13 is an explanatory diagram showing an example of a mileage DB. The mileage DB 138 stores the mileage of each trip. The mileage DB 138 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. 13, the unit is meters (m).

[0048] FIG. 14 is an explanatory diagram showing an example of a monthly total distance DB. The monthly total distance DB 139 stores the total mileage of each vehicle for each month. The monthly total distance DB 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 that are the subject of the calculation. The total distance column stores the total mileage for the subject month. The total mileage is calculated by extracting data for the subject month from the mileage DB 138 and adding up the mileage 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.

[0049] FIG. 15 is an explanatory diagram showing an example of a billing DB. The billing DB 13A stores the amount of usage fee billed to the user. The billing DB 13A includes a user ID column, a vehicle ID column, an IMEI column, a usage date column, a basic fee column, a metered fee column, and a usage fee column. 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 the communication device 4. The usage date column stores the month of use of the vehicle that is the subject of the billing. The basic fee column stores the amount of the basic fee billed. If a bonus payment is set, the basic fee will be a different amount for a normal month and a bonus month. The metered fee column stores the amount of the metered fee billed. The usage fee column stores the amount of the usage fee billed (= basic fee + metered fee).

[0050] Next, the calculation method of the basic fee and the billing unit price that are the basis of the usage fee will be explained. Hereinafter, the amount by which the residual value decreases will be referred to as depreciation. In this specification, the factors (depreciation factors) that cause the residual value of a vehicle to decrease are various, but this specification focuses on the fact that 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 from the initial registration even if the total mileage is 0. Based on these items, depreciation due to the passage of time is mainly included in the basic fee regardless of the total mileage of the vehicle, and depreciation due to the total mileage is mainly collected as a metered fee. Below, a specific example will be explained.

[0051] First, the residual value data on which the calculation is based will be described. Residual value data (residual value rate and residual value) associated with each vehicle model, each grade, and each body color, as well as the number of years since the initial registration month and the total mileage is acquired. Hereinafter, this residual value data will be referred to as basic residual value data. For example, the server 1 acquires the residual value data from an information provider by downloading it, 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 differs depending on the rating determined by the vehicle condition, etc. In this embodiment, residual value data of a rating indicating a better condition than the average condition is acquired.

[0052] Next, calculate the number of years that have passed since the first registration of the vehicle model at the time of calculation or the planned start of use. For example, if you are calculating in April 2023 for a vehicle that was first registered in December 2020, the number of years that have passed is two years.

[0053] Next, calculate the expected total number of years that have elapsed by adding the expected period of the usage contract. In other words, calculate the number of years that have elapsed at the end of the usage period. In the above example, if the usage period (predetermined period) is three years from April 2023, the expected total number of years that have elapsed is 2 years + 3 years = 5 years.

[0054] Next, by referring to the basic residual value data, a table is created that associates the expected total number of years elapsed and the total mileage with the residual value rate and the residual value. An example is the residual value DB 132 shown in FIG. 7. In the above example, the expected total number of years elapsed is 5 years = 60 months. In FIG. 7, the table is also created for cases where the usage period is 1 year and 5 years, that is, the expected total number of years elapsed is 3 years = 36 months and 7 years = 84 months.

[0055] The residual value and the residual value rate for the total mileage of 0 km in the expected total elapsed years are identified by referring to the created residual value DB 132. In the example of Fig. 7, when the expected total elapsed years is 3 years, the residual value is 2,507,000 yen and the residual value rate is 89.3%.

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

[0057] Principal = vehicle price - (vehicle price x residual value) + maintenance fee + tax + miscellaneous expenses … (1) The vehicle price is the vehicle price at the time of initial registration stored in the price column of the vehicle DB. Maintenance fees are the costs for vehicle inspections and regular inspections during the period of use. 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 certification fees, and delivery fees.

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

[0059] Basic fee = (principal amount + interest fee) / number of payments … (2) If payments are made monthly during the subscription period, the number of payments is equal to the number of months in the subscription period. If the subscription period is 3 years, the number of payments is 36.

[0060] The calculated basic fee is stored in the fee DB 133. The reason why the basic fee is calculated based on the residual value or residual value rate when the total mileage is 0 km is based on the above-mentioned idea that the amount of the residual value that decreases over time, regardless of the total mileage of the vehicle, is collected as the basic fee. The calculation methods of the basic fee using formulas (1) and (2) are examples and are not limited to these.

[0061] Next, we will explain how to calculate the unit price. First, from the residual value data for each total mileage over the expected total age of the vehicle, two corresponding residual values ​​are identified based on any two total mileages. The depreciation per unit distance is calculated by dividing the difference between the identified residual values ​​by the difference between the two total mileages.

[0062] FIG. 16 is an explanatory diagram showing an example of calculating the unit cost price. The unit cost price is the unit price that forms the basis of the billing price. In the example shown in FIG. 16, the expected total elapsed years is 3 years = 36 months, and the combination of two residual values ​​is 0 km and other distances. The depreciation (absolute value) per km of mileage when the total mileage is 18,000 km is calculated as follows. One of the combinations of two residual values ​​does not have to be 0 km; for example, the depreciation per km of mileage may 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 unit price = (2,507,000 yen - 2,423,000 yen) / (18,000 - 0) = 5 yen (rounded to the nearest decimal place) When the other total distances are calculated, the value in the kilometer unit row in Figure 16 is obtained. Based on the obtained multiple depreciation values ​​(absolute values), the value to be used in subsequent processing (called the unit cost) is determined. For example, the maximum, median, or average value of the multiple depreciation values ​​(absolute values) is set as the unit cost. If the maximum value is used, the unit cost will be 6 yen.

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

[0065] Billing price = 16 yen x (1 + 0.05) x 1.1 = 18 yen (rounded to the nearest whole number) As described above, the method of determining the basic fee and the billing unit price is as described above, and the depreciation due to the passage of time is collected as the basic fee, regardless of the total mileage of the vehicle, using the average rating value. The depreciation due to the total mileage is collected as a metered fee. A fee plan calculated in this way is called a standard plan.

[0066] Next, the information processing performed by the automobile transaction system 100 will be described. Fig. 17 is a flow chart showing an example of the procedure of the fee calculation processing. The fee calculation processing is a process that is started upon a request from a person (prospective user) who is to become a customer of the automobile transaction system 100 and a user of a vehicle. For ease of explanation, the prospective user will be referred to as a user, and the terminal to be used will be referred to as a user terminal 2.

[0067] The user operates the user terminal 2 to instruct the fee calculation. The control unit 21 of the user terminal 2 transmits a calculation request to the server 1 (step S1). The control unit 11 of the server 1 receives the calculation request (step S2). The control unit 11 transmits an input screen for inputting information on the target vehicle to the user terminal 2 (step S3). The control unit 21 of the user terminal 2 receives the input screen (step S4). The control unit 21 displays the input screen on the display panel 25 (step S5). The user inputs information on the used vehicle into the input screen. The information to be input is the vehicle model, grade, and color (body color). The control unit 21 accepts the input (step S6). Note that the user may be prompted to input the vehicle usage period in addition to the vehicle information. The control unit 21 transmits the accepted vehicle model, grade, and color to the server 1 (step S7). The control unit 11 of the server 1 receives the vehicle model, grade, and color (step S8). The control unit 11 determines whether or not there is stock (step S9). In the automobile transaction system 100, since it is assumed that the procurement of vehicles is performed from an affiliated dealer, the control unit 11 inquires of the affiliated dealer's system and judges whether or not there is stock. When the control unit 11 judges that there is stock (YES in step S9), it specifies the expected total elapsed years (step S10). The control unit 11 calculates the number of years elapsed from the initial registration date to the processing date from the vehicle information obtained from the inquiry to the dealer. It specifies the number of years elapsed at the time of expiration of the usage period = the expected total elapsed years by adding the usage period to the current number of years elapsed. If the user specifies the usage period, the specified period is added. If the user does not specify the usage period, the expected total elapsed years are specified assuming 3 years, 5 years, 7 years, etc. At this time, it is possible to specify multiple expected total elapsed years and perform the following process for each expected total elapsed year. The control unit 11 creates a residual value and residual value rate table for the expected total elapsed years (step S11). The residual value DB 132 shown in FIG. 7 is an example. The control unit 11 calculates the basic fee (step S12). The control unit 11 calculates the billing unit price (step S13). The control unit 11 stores the calculated basic fee and billing unit price in the fee DB 133 (step S14). The control unit 11 creates a fee screen including the basic fee and billing unit price, and transmits it to the user terminal 2 (step S15).The control unit 21 of the user terminal 2 receives the fee screen and displays it on the display panel 25 (step S16). The control unit 21 ends 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 end the process or to search for another vehicle without ending. The control unit 21 accepts the input (step S19). The control unit 21 determines whether to end the process (step S20). If the control unit 21 determines that there is no stock (NO in step S20), it returns the process to step S5. If the control unit 21 determines that there is no stock (YES in step S20), it ends the process.

[0068] Fig. 18 is a flow chart showing an example of the procedure for the basic fee calculation process. The control unit 11 of the server 1 refers to the residual value DB 132 and identifies the residual value rate for a total mileage of 0 km in the expected 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 acquires various expenses and fees such as compulsory automobile liability insurance and garage certification (step S33). The control unit 11 calculates the basic fee (step S34). The basic fee is calculated, for example, using the above-mentioned formula (1). The control unit 11 returns the process to the caller.

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

[0070] The user enters into a vehicle usage contract with the owner, subject to the basic fee and the unit price calculated by the fee calculation process. After the usage contract is concluded, the vehicle is delivered and the user begins using it.

[0071] Next, the calculation of the usage fee will be described. The usage fee is calculated for each specified period, here for each month. To calculate the usage fee, it is necessary to calculate the total mileage for the specified period, which is the basis for calculating the pay-per-use fee, here for the total monthly mileage. The process for calculating the total monthly mileage will be described.

[0072] FIG. 20 is a flowchart showing an example of the procedure of the location information acquisition process. The location information acquisition process is a process of acquiring location information from the communication device 4 attached to the vehicle and storing the vehicle location in the location information DB 137. The communication device 4 detects that the engine of the vehicle has started and starts the process. The control unit 41 of the communication device 4 transmits 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 transmits 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 is successful or not (step S66). If the control unit 41 determines that the authentication is unsuccessful (NO in step S66), the process ends. When the control unit 41 determines that the authentication is successful (YES in step S66), it transmits the positioning result of 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 transmits a response to the effect that the position information has been stored to the communication device 4 (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 end the process (step S72). 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 S72), it returns the process to step S67 and continues the process. When the control unit 41 determines to end the process (YES in step S72), it transmits an end to the server 1 (step S73). The control unit 11 of the server 1 receives the end (step S74). The control unit 11 stores the end (step S75). 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 S76). The control unit 41 of the communication device 4 receives the response (step S77) and ends the process.

[0073] FIG. 21 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 137. The control unit 11 of the server 1 acquires the position information included in one trip to be processed (step S91). 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 S92). At that time, the control unit 11 checks the overlap of each point with the road line data, and corrects the points 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 S93). The control unit 11 calculates the mileage based on the route and the road network data (step S94). The control unit 11 stores the mileage in the mileage DB 138 (step S95). The control unit 11 determines whether to end the process (step S96). 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 S96), the process returns to step S91 and continues. If the control unit 11 determines to end the process (YES in step S96), the process ends. Note that, in the mileage calculation process, it is desirable to calculate the mileage for a trip each time the end of the trip is detected in the location information acquisition process. In this case, step S96 is unnecessary.

[0074] FIG. 22 is a flowchart showing an example of the procedure of the monthly total mileage calculation process. The monthly total mileage calculation process is a process for calculating the monthly total mileage for each vehicle. The monthly total mileage calculation process is executed by monthly batch processing or the like. The control unit 11 of the server 1 acquires 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. The control unit 11 acquires the mileage data for each trip within the target period from the mileage DB 138 (step S112). As described above, when the start and end of a trip span across months, it is determined in advance whether to judge based on 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 target vehicle ID to calculate 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 there is an unprocessed vehicle ID (step S116). If the control unit 11 determines that there is an unprocessed vehicle ID (YES in step S116), the control unit 11 returns the process to step S113 and performs processing on the unprocessed vehicle ID. If the control unit 11 determines that there is no unprocessed vehicle ID (NO in step S116), the control unit 11 ends the process.

[0075] FIG. 23 is a flowchart showing an example of the procedure of the usage fee calculation process. The usage fee calculation process is a process for calculating the monthly usage fee to be billed to each contractor. The usage fee calculation process is executed by monthly batch processing or the like. Note that it is assumed that the monthly total mileage calculation is completed before the usage fee calculation process is executed. The control unit 11 of the server 1 extracts information of the user to be calculated from the user DB 134 (step S131). The control unit 11 selects the user to be processed (step S132). The control unit 11 acquires the monthly total mileage of the selected user from the monthly total mileage DB 139 (step S133). The control unit 11 acquires the billed unit price of the user from the contract DB 135, and multiplies it by the monthly total mileage to calculate the metered fee (step S134). The control unit 11 calculates the usage fee by adding the calculated metered fee to the monthly basic fee acquired from the contract DB 135 (step S135). The control unit 11 stores the basic fee, the metered fee, and the usage fee in the billing DB 13A (step S136). Based on the billing information stored in the billing DB 13A, a separate billing process is performed for the user. The control unit 11 determines whether or not there are any unprocessed users (step S137). If the control unit 11 determines that there are any unprocessed users (YES in step S137), it returns the process to step S132. If the control unit 11 determines that there are no unprocessed users (NO in step S137), it ends the process. After the usage fee is calculated, the user may be notified of the calculated usage fee. For example, the notification is performed by email, push notification, etc.

[0076] FIG. 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 a usage fee d011, payment information d012, a basic fee d013, and a usage fee d014. The usage fee d011 indicates the usage fee to be charged. The payment information d112 indicates the payment date such as the payment method and the deduction date. The basic fee d013 indicates the monthly basic fee. The usage fee d014 indicates a usage fee according to the total monthly mileage.

[0077] In this embodiment, the usage fee is a charge based on the vehicle's mileage. Therefore, the usage fee is a reasonable value whether the user drives a long or short distance. If the owner is a leasing company or the like and the operator of the automobile trading system 100 is responsible for collecting the usage fee, the operator may hold the monthly usage fee until the expiration of the usage period, and after the expiration of the usage period, the operator may pay the total amount (accumulated value) of the usage fee to the owner. In this case, it is desirable to calculate the accumulated value of the usage fee for each contract every month and store it in the contract DB 135. This is because it becomes possible to confirm how much additional fee has been collected during the usage period. Furthermore, if the accumulated value is stored, it becomes possible to quickly process the payment to the owner after the usage period expires.

[0078] (Embodiment 2) This embodiment relates to a form in which, if the total monthly mileage is within a specified value, no metered fee is charged, and if it exceeds the specified value, a metered fee according to the distance exceeded is charged. For example, if the total monthly mileage is within 500 km, no metered fee is charged, and only the basic fee is charged. This fee plan is called a plan free of charge up to 500 km per month. The reason why it is set at 500 km per month is that a survey of car owners showed that the average monthly mileage is 500 km. Therefore, it is considered that free of charge up to 500 km per month has a certain degree of validity, but this embodiment is not limited to this. For example, free of charge may be set up to 300 km per month, or free of charge may be set up to 700 km per month. Such fee plans in which no metered fee is charged 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 charge for up to 500 km per month, it is assumed that the user will drive the vehicle at least 500 km per month during the usage period. That is, if the usage period is 36 months, the basic fee is calculated assuming that the total mileage is 18,000 km. In addition, since it is assumed that the total mileage is longer than in the standard plan, the vehicle rating obtained as residual value data is a rating indicating an average condition, whereas the standard plan uses a rating indicating that the vehicle condition is better than average. This embodiment differs from the first embodiment in the method of calculating the basic fee, and this point will be mainly explained below.

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

[0081] The basic fee is calculated as follows. If the expected number of years elapsed is 3 years = 36 months, the residual value DB 132 is referenced to identify the residual value rate for a total mileage of 18,000 km in the expected total number of years elapsed. In the example of FIG. 25, it is 83.0%. Using this residual value rate, the basic fee is calculated using formula (1) shown in the first embodiment. The difference is that while the first embodiment adopted a residual value rate for a total mileage of 0 km, this embodiment adopts a residual value rate for a total mileage of 18,000 km.

[0082] FIG. 26 is an explanatory diagram showing an example of calculation of the unit cost. The calculation method is the same as that of the first embodiment described with reference to FIG. 16. As in FIG. 16, the expected total elapsed years is 3 years = 36 months, and the combination of two residual values ​​is 0 km and other distances. This is not limited to this, and one of them may not be 0 km, for example, a combination of a residual value for a total mileage of 18,000 km and a residual value for a total mileage of 24,000 km may be used. The depreciation (absolute value) per km of mileage when the total mileage is 18,000 km is calculated as follows.

[0083] Cost unit price = (2,416,000 yen - 2,331,000 yen) / (18,000 - 0) = 5 yen (rounded to the nearest decimal place) If the maximum value is adopted as the unit cost, the unit cost will be 6 yen. Furthermore, the unit cost is added with profit, the amount equivalent to various expenses necessary for billing, and consumption tax to determine the billing unit price. The idea of ​​calculating the billing unit price from the unit cost is the same as in the first embodiment.

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

[0085] In the free-of-charge plan for up to 500 km per month proposed in this embodiment, the fixed monthly basic fee is higher than that of the standard plan; however, no additional fees (metered charges) are incurred for total monthly mileage up to 500 km, making this a more reasonable fee plan than the standard plan for users who expect their vehicle mileage to be around 500 km per month.

[0086] (Embodiment 3) This embodiment is a fee plan that reduces the fixed basic fee more than the standard plan. It is called the economy plan because it reduces the basic fee. The economy plan is a plan that assumes a lower total monthly mileage than the standard plan. Therefore, while the standard plan has a rating that indicates that the vehicle condition is better than average, this embodiment has a rating that is even better than the standard plan, as residual value data. This embodiment differs from embodiment 1 in the residual value data that is the basis for calculating the basic fee and the metered fee.

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

[0088] The calculation method of the basic fee and the usage fee is the same as that of the first embodiment (standard plan), so the explanation is omitted. Also, the processing performed in this embodiment is the same as that shown in the flowcharts of Figs. 17 to 23.

[0089] In the economy plan proposed in this embodiment, the fixed monthly basic fee is cheaper than that of the standard plan, so this plan is suitable for users who do not use the vehicle as a practical means of transportation, but rather own and admire it, or simply enjoy driving it, and who drive a short total distance and whose main purpose is to get pleasure from owning the vehicle.

[0090] (Embodiment 4) This embodiment relates to a form in which the billing unit price of the standard plan and the economy plan is corrected in comparison with the plan with no charge up to 500 km per month. As described above, residual value data is used to calculate the basic charge and the metered charge of each plan. To repeat, the residual value differs depending on the rating indicating the condition of the vehicle. Depreciation is considered to have a positive correlation with the total mileage, and the basic charge and the metered charge are calculated by adopting the residual value data of a vehicle with an average rating for the plan with no charge up to 500 km per month, the residual value data of a vehicle with a rating slightly higher than the average for the standard plan, and the residual value data of a vehicle with an even higher rating for the economy plan, depending on the total mileage assumed in each plan. However, regardless of the rating of the vehicle, if it is used at a total mileage of 500 km per month, which is said to be the average, it is expected that the residual value evaluated after several years will be an average value. In other words, if the total monthly mileage of a user who has signed a contract for the Standard Plan or Economy Plan fluctuates unexpectedly around 500km during the usage period, the residual value at the end of the usage period may be lower than the residual value assumed at the time of the contract. In addition, the pay-per-use fee is a fee to recover the depreciation according to the mileage, but since it is calculated under the assumption that the vehicle rating will not change, it is unlikely that it will be able to compensate for the unpaid basic fee. Therefore, the billing rate for the Standard Plan and Economy Plan is adjusted using the billing rate for the plan with no charge up to 500km per month.

[0091] FIG. 28 is an explanatory diagram showing a method of correcting distance cost. FIG. 28 shows an example in which the usage period is 36 months, similar to the examples so far. The plan column shows the name of the plan. The expected total mileage column shows the total mileage of the vehicle during the usage period assumed when calculating the fee. For the plan with no charge up to 500 km per month, it is 18,000 km. For the standard plan and economy plan, the expected total mileage is not set. The initial residual value rate column shows the residual value rate at the end of the usage period when the total mileage, which is the basis of the basic fee, is 0 km. Similarly, the initial residual value column shows the residual value at the end of the usage period when the total mileage is 0 km. The base cost column shows the cost unit price calculated in the billing unit price processing for each plan. The expiration residual value column shows the residual value at the end of the usage period when the total mileage during the usage period is 18,000 km for each plan. The upper column shows the difference between the residual value at the end of the flat-rate plan and the standard or economy plan, and the residual value at the end of the plan with no charge for up to 500 km per month (reference residual value data). The column shows the residual value rate at the end of the usage period when the total mileage during the usage period is 18,000 km for each plan. The lower column shows the difference between the residual value rate at the end of the flat-rate plan and 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 no charge for up to 500 km per month. The adjusted cost column shows the value in the upper column showing the difference between the differential from the flat-rate plan and the standard or economy plan divided by 18,000. The distance cost column shows the unit cost, which is the sum of the value in the distance cost column and the value in the adjusted cost column. The billing unit price (excluding tax) column shows the billing unit price obtained by adding profits, etc. to the unit cost price. The billing unit price (including tax) column shows the billing unit price including consumption tax.

[0092] As described above, in the case of 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 for 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 for up to 500 km per month, it is possible to recover the decrease in residual value by treating the difference in residual value as the adjusted cost per km and adding it to the cost unit price.

[0093] As described above, after the unit cost price is corrected, the billing unit price is calculated. The procedure for correcting the unit cost price will be explained again using a flowchart. FIG. 29 is a flowchart showing an example of the procedure for the cost correction process. The cost correction process is executed in place of step S45 in the billing unit price calculation process shown in FIG. 19. That is, following step S44, the cost correction process is executed, and step S45 is not executed and the process returns.

[0094] The control unit 11 of the server 1 judges whether the calculation target is a flat-rate plan (step S151). Here, the flat-rate plan is a plan with no charge up to 500 km per month. The designation of the fee plan to be calculated is accepted in step S6 of the fee calculation process shown in FIG. 17. If the control unit 11 judges that the plan is not a flat-rate plan (NO in step S151), it acquires 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 when the total mileage during the usage period is 18,000 km in the target plan (step S152). The control unit 11 calculates the difference between the two acquired residual values ​​(step S153). The control unit 11 divides the difference in the residual value by the expected total mileage (here, 18,000 km) to calculate the adjusted cost (step S154). The control unit 11 calculates the distance cost (step S155). The distance cost is obtained by adding the adjustment cost to the cost unit price (standard cost) calculated in step S44 of Fig. 19. The control unit 11 calculates the billing unit price from the distance cost (step S156). If the control unit 11 determines that the plan is a flat-rate plan (YES in step S151), it executes step S156. The control unit 11 ends the process.

[0095] In this embodiment, if, contrary to expectations, the vehicle usage by a user who has signed up for the Standard Plan or Economy Plan fluctuates with the total monthly mileage during the usage period remaining close to 500 km, and the residual value at the end of the usage period falls below the residual value assumed at the time of signing the contract and becomes the same level as the residual value of the plan with no charge up to 500 km per month, it is possible to recover the amount by which the residual value falls short by charging a usage fee at a billing unit price that takes into account the adjustment cost.

[0096] If the actual price when the vehicle is sold after the expiration of the usage period falls below the expected residual value assumed at the time of the contract, an open-end method may be adopted and the difference between the selling price and the expected residual value may be collected from the user. Alternatively, a closed-end method may be adopted and no additional collection may be made from the user. Whether the method is an open-end method or a closed-end method is determined in advance. Alternatively, the method to be used may be decided through discussion between the user and the owner at the time of the contract.

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

[0098] FIG. 30 is an explanatory diagram showing an example of a training DB. The training DB 13B stores training data for learning a learning model described later. The training DB 13B includes a vehicle type column, a vehicle type class column, a color column, a grade column, an age column, a gender column, an occupation column, a usage period column, and a total mileage column. The vehicle type column to the grade column store data related to vehicles for which a usage contract was made in the past. The vehicle type column stores the name of the vehicle. The vehicle type class column stores the class of the vehicle. The classes are, 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 age column to the occupation column store usage information. The age column stores the age of the user. It may be an age group 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 period of use. The training DB 13B is generated by referring to the user DB 134, the contract DB 135, the monthly total mileage DB 139, etc.

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

[0100] FIG. 32 is a flowchart showing an example of the procedure of the model generation process. The control unit 11 of the 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 one record of the selected training data (step S173). For example, the control unit 11 inputs vehicle information, user information, and usage period included in the training data to the estimation model M, and optimizes parameters such as weights between neurons constituting the estimation model M so that the estimated value of the total mileage output from the estimation model M approaches the value of the total mileage included in the training data. The control unit 11 determines whether or not there is an unprocessed record that has not been used for learning (step S174). If the control unit 11 determines that there is an unprocessed record (YES in step S174), the control unit 11 returns the process to step S172 and continues the process. If the control unit 11 determines that there is no unprocessed training data (NO in step S174), the control unit 11 stores the estimation model M obtained by learning (step S175) and ends the process.

[0101] FIG. 33 is a flowchart showing another example of the procedure of the fee calculation process. The user operates the user terminal 2 to instruct fee calculation. The control unit 21 of the user terminal 2 transmits a request for calculation to the server 1 (step S181). The control unit 11 of the server 1 receives the request for calculation (step S182). The control unit 11 transmits an input screen for inputting vehicle information, period of use, etc. to the user terminal 2 (step S183). The control unit 21 of the user terminal 2 receives the input screen (step S184). The control unit 21 displays the input screen on the display panel 25 (step S185). The user inputs information about the vehicle used on the input screen. The information to be input is the vehicle model, grade, color (body color), and period of use. A desired fee plan may be input. Note that, with regard to the flat-rate plan, the total monthly mileage for which no metered fee is charged is determined by the total mileage during the period of use, so the upper limit of the total monthly mileage for which the flat rate is charged is not displayed on the input screen. The control unit 21 accepts the input (step S186). The control unit 21 transmits the accepted vehicle model, grade, color, and usage period to the server 1 (step S187). The control unit 11 of the server 1 receives the vehicle model, grade, color, and usage period (step S188). The control unit 11 judges whether or not there is stock (step S189). In the automobile trading system 100, since it is assumed that the procurement of vehicles is performed from affiliated dealers, the control unit 11 inquires the affiliated dealer's system and judges whether or not there is stock. If the control unit 11 judges that there is stock (YES in step S189), it specifies the expected total elapsed years (step S190). The control unit 11 calculates the number of years elapsed from the initial registration date to the processing date from the vehicle information obtained from the inquiry to the dealer. The current number of years elapsed is added to the usage period specified by the user to specify the number of years elapsed at the expiration of the usage period = the expected total elapsed years. The control unit 11 estimates the total mileage (step S191). That is, the control unit 11 inputs user information, vehicle information, and usage period to the estimation model M, and acquires an estimated value of the total mileage from the estimation model M. The control unit 11 creates a residual value / residual value rate table for the expected total elapsed years, taking into account the estimated total mileage (step S192). The control unit 11 adjusts the vehicle rating when acquiring the residual value data, depending on the estimated total mileage.The control unit 11 calculates the basic fee (step S193). The control unit 11 calculates the billing unit price (step S194). In the calculation of the flat-rate plan, the estimated total mileage is used as the assumed total mileage to calculate the basic fee and the billing unit price. The control unit 11 stores the calculated basic fee and the billing unit price in the fee DB 133 (step S195). The control unit 11 creates a fee screen including the basic fee and the billing unit price, and transmits it to the user terminal 2 (step S196). The fee screen of the flat-rate plan includes the upper limit distance for the monthly fee calculated by dividing the estimated total mileage by the number of months of the usage period. For example, when the estimated total mileage is 14,400 km and the number of months of the usage period is 36 months, the upper limit distance per month is 400 km. The control unit 21 of the user terminal 2 receives the fee screen and displays it on the display panel 25 (step S197). The control unit 21 ends the process. 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 end the process or to search for other vehicles without ending the process. The control unit 21 accepts the input (step S200). The control unit 21 determines whether to end the process (step S201). If the control unit 21 determines not to end the process (NO in step S201), it returns the process to step S185. If the control unit 21 determines to end the process (YES in step S201), it ends the process.

[0102] In this embodiment, the estimation model M is used to estimate the total mileage during the usage period, so that the residual value and the residual value rate at the end of the usage period can be estimated with high accuracy.

[0103] (Interpolation of Residual Value Data) As mentioned above, it is assumed that residual value data will be obtained from an information provider. Therefore, the residual value data obtained is discrete, and it is assumed that the residual value data required for fee calculation will not be obtained. In that case, 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) are available, and residual value data for 3.5 years (42 months) is required, the difference between the 4-year residual value data and the 3-year residual value data is divided by 12 to find the depreciation per month, and the depreciation calculated is multiplied by 6 and subtracted from the 3-year residual value to obtain the residual value for 3.5 years.

[0104] Interpolation for distance is done in the same way as distance cost. If residual value data for 18,000km and 24,000km are available and residual value data for 20,000km is required, divide the difference in the residual value data by the difference in distance (6,000km) to find the depreciation per km. Multiplying the depreciation found by 2,000, and subtracting the result from the residual value data for 18,000km, it is possible to obtain the residual value data for 20,000km.

[0105] Interpolation for the body color is difficult, but the following process can be used. For example, if residual value data is available for solid white but not for pearl white, the residual value data for solid white can be used instead, 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 solid white can be multiplied by 0.9 across the board to use that value as the residual value data for pearl white.

[0106] In addition, it has been determined that the popularity ranking of body colors is 6th place: red, 7th place: brown / beige, and 8th place: green. Residual value data for red and green has been obtained, but in the event that the necessary residual value data for brown / beige is not available, the midpoint between the red data and the green data will be used as the residual value data for brown / beige.

[0107] The above-mentioned interpolation method is linear interpolation, but if another interpolation method is suitable, it may be adopted.

[0108] 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.

[0109] 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.

[0110] In addition, the claims are written in a format in which a claim cites two or more other claims (multiple claim format), but this is 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]

[0111] 100: Automobile trading system 1: Server 1P: Control program 11: Control section 12: Main memory 13: Auxiliary storage section 131: Vehicle DB 132: Residual value DB 1321: Header 1322: Table 133: Fee DB 134: User DB 135: Contract DB 136: Device DB 137: Location information DB 138: Mileage DB 139: Monthly total distance DB 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 section 22: Main memory 23: Auxiliary storage section 24: Communications Department 25: Display panel 26:Operation section 27: Imaging unit 2P: Control program 3: Owner device 3P: Control program 4: Communication devices 41: Control section 42: Main memory 43: Auxiliary storage section 44: Communications Department 45: Position acquisition part 46: Imaging section 4P: Control program B: Bus N: Network

Claims

1. Acquire residual value data based on the period of use and total mileage of the vehicle; Calculating a basic fee for the vehicle for a predetermined period and an additional fee based on the mileage for the predetermined period based on the residual value data; Output the billing amount calculated from the basic fee and the additional fee An information processing method in which processing is performed by a computer.

2. The additional charge is calculated based on a distance unit price calculated based on the residual value data and a mileage within a predetermined period. The information processing method according to claim 1 .

3. The distance unit price is determined by selecting two residual values ​​with different mileages from residual value data for each mileage in the number of years since the initial registration of the vehicle, and based on 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 in the number of years elapsed since the initial registration of the vehicle is less than the reference residual value data corresponding to the number of years elapsed and the mileage, an adjusted cost is calculated based on the amount corresponding to the shortfall and the mileage; The distance unit price is corrected based on the calculated adjusted cost. The information processing method according to claim 3.

5. Generate multiple sets of two residual value combinations; The distance cost is calculated for each pair generated, and the highest value, median value or average value is adopted as the distance cost. The information processing method according to claim 3.

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

7. Each time the additional charge is calculated, an integrated value of the calculated additional charge is calculated; The obtained integrated value is stored; After the predetermined period has elapsed, the stored integrated value is output. The information processing method according to any one of claims 1 to 5.

8. The basic fee is calculated based on the number of years that have passed since the initial registration of the vehicle at the time of expiration of the usage period. The information processing method according to any one of claims 1 to 5.

9. The basic fee is calculated based on the difference between the new vehicle price of the vehicle or the current residual value and the residual value after a specified period of time has elapsed and the mileage of the vehicle is set to zero. The information processing method according to any one of claims 1 to 5.

10. The base fee and the cost per distance are calculated by referring to a table in which the vehicle type, grade, and body color, the number of years since the initial registration, and residual value data for each total mileage are associated with each other. The information processing method according to any one of claims 2 to 5.

11. Acquire residual value data based on the period of use and total mileage of the vehicle; Calculating a basic fee for the vehicle for a predetermined period and an additional fee based on the mileage for the predetermined period based on the residual value data; Output the billing amount calculated from the basic fee and the additional fee An information processing program that causes a computer to execute processing.

12. an acquisition unit that acquires residual value data based on a period of use and a total mileage of a vehicle; a calculation unit that calculates a basic fee for the vehicle within a predetermined period and an additional fee based on a mileage within the predetermined period based on the residual value data; an output unit that outputs a billing amount calculated from the basic fee and the additional fee; An information processing device comprising:

13. receiving a basic fee calculated using residual value data based on a period of use and a total distance traveled of a vehicle, an additional fee calculated using the residual value data based on a distance traveled within a predetermined period, and a billing amount calculated based on the basic fee and the additional fee; Displaying the received basic fee, additional fee, and billing amount A display program that causes a computer to execute processing.

14. Obtaining vehicle location information for each trip from a database that stores vehicle location information in association with a measurement date and time; Plotting the acquired location information on an electronic map for each trip; Correcting each position plotted on the electronic map so that it is a position on a road; Identifying a route from a start position to an end position of the trip based on each corrected position; Calculating a distance traveled for the trip based on the identified route; Calculate a metered charge for a predetermined period based on a total distance traveled for each trip during the predetermined period and a preset distance unit price; The basic fee for the specified period and the calculated usage fee for the specified period are added together to calculate the billing amount for the specified period. An information processing method in which processing is performed by a computer.

15. A method for storing the pay-per-use charge for each predetermined period in a storage unit, When the usage period of the vehicle expires, the amount obtained by accumulating the usage fees for the predetermined period stored in the storage unit is paid to the owner of the vehicle. The information processing method according to claim 14 , wherein the processing is executed by the computer.

16. The trip is the time from when the engine of the vehicle is started to when it is stopped.

16. The information processing method according to claim 14 or 15.

Images