Charged amount calculating system
The billing amount calculation system addresses the challenge of settling charges for multiple contractors by using time and distance metrics, along with fuel costs, to efficiently determine and communicate individual billing amounts.
Patent Information
- Application Number
- JP2025081620
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-05-17
- Filing Date
- 2025-05-15
- Publication Date
- 2025-11-28
AI Technical Summary
Conventional systems face difficulties in accurately settling billing amounts when a single vehicle is rented to multiple contractors within the same contract period.
A billing amount calculation system that calculates charges based on the time and distance of vehicle use for each contractor, including fuel costs, and notifies each contractor via email.
Facilitates easier settlement of billing amounts by accurately calculating and communicating individual charges to multiple contractors.
Smart Images

Figure 2025174922000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a billing amount calculation system. [Background technology]
[0002] It is well known that a computer system is used for management in vehicle rental services. For example, Patent Document 1 describes a system in which vehicle management data related to vehicle rental status and reservations is stored in a database, and whether or not to accept a rental reservation from a user is determined based on this database. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-102553 Summary of the Invention [Problem to be solved by the invention]
[0004] However, with conventional technology, there was a problem in that it was difficult to settle the billed amounts when one vehicle was rented to multiple contractors within the same contract period.
[0005] The present invention has been made to solve such problems, and aims to provide a billing amount calculation system that makes it easier to settle billing amounts when a single vehicle is rented to multiple contractors within the same contract period. [Means for solving the problem]
[0006] An example of a billing amount calculation system according to the present invention includes: A billing amount calculation system that calculates a billing amount for a vehicle loan to two or more first contractors and one or more second contractors, The billing amount calculation system includes: - for each of said vehicle uses, The date and time when the vehicle was used; At least one of the time the vehicle was used and the distance traveled by the vehicle; Get - calculating the amount to be charged to each of the second contractors based on at least one of the time the vehicle was used and the distance traveled by the vehicle for each of the uses relating to each of the second contractors;
[0007] In one example, The billing amount calculation system includes: - Obtain the total rental fee for each primary contractor; - calculating the amount to be charged to each of the secondary contractors based on the duration of the vehicle use for each of the uses relating to each of the secondary contractors; - Calculating the amount to be charged to each of the first contractors based on the total rental fee and the duration of use of the vehicle for each of the uses relating to each of the second contractors.
[0008] In one example, Any of the first contractors is a specified first contractor, The other person of the first contractor is an unspecified first contractor, The billing amount calculation system includes: - Obtain the total fuel cost, - calculating the fuel cost equivalent for each of the second contractors based on the mileage of the vehicle for each of the uses related to each of the second contractors; - calculating the amount to be claimed from each of the second contractors based on the fuel cost equivalent for each of the second contractors; - Calculating the amount equivalent to the fuel cost for each of the unspecified first contractors based on the mileage of the vehicle for each of the uses related to the unspecified first contractors; - calculating the amount to be claimed from each of said unspecified first contractors based on the amount equivalent to the fuel costs for each of said unspecified first contractors; - Calculate the amount to be claimed for the specified first contractor based on the total fuel cost, the amount equivalent to the fuel cost for each of the second contractors, and the amount equivalent to the fuel cost for each of the unspecified first contractors.
[0009] In one example, the billing amount calculation system further includes an odometer, and obtains the time the vehicle is used and the mileage of the vehicle based on information from the odometer.
[0010] In one example, the system accepts and stores input of the date and time when each of the second contractors plans to use the vehicle.
[0011] In one example, the billing calculation system includes: notify each of the first contractors of the amount due by email; The amount of the invoice to each of the second contractors will be notified to each of the second contractors by individual email.
[0012] An example of the program according to the present invention causes a computer to function as the billing amount calculation system described above.
[0013] An example of a billing amount calculation method according to the present invention is as follows: A method for calculating a claim amount for a vehicle loan to two or more first contractors and one or more second contractors, The billing amount calculation method is - the computer calculates, for each of said vehicle uses, The date and time when the vehicle was used; At least one of the time the vehicle was used and the distance traveled by the vehicle; obtaining a - calculating by a computer an amount to be charged to each of the second contractors for each of the uses related to each of the second contractors based on at least one of the time the vehicle was used and the distance traveled by the vehicle; Equipped with.
[0014] An example of a billing amount calculation system according to the present invention includes: A billing amount calculation system that calculates a billing amount for a vehicle loan to two or more first contractors and one or more second contractors, - calculating the amount to be charged to each of the Secondary Contractors for the first contract period based on the time and fuel costs of the use of the vehicle by that Secondary Contractor; - Calculate the amount to be charged to at least one first contractor for the first contract period based on the total rental fee, the total fuel cost, and the time for use of the vehicle and the amount equivalent to the fuel cost for each second contractor. [Effects of the Invention]
[0015] The billing amount calculation system according to the present invention makes it easier to settle billing amounts when one vehicle is rented to multiple contractors within the same contract period.
[0016] Effects other than those mentioned above will be explained by the embodiments and modifications described in this specification and the drawings. [Brief explanation of the drawings]
[0017] [Figure 1] 1 is an outline of a contract form for vehicle rental (leasing) according to the first embodiment. [Figure 2] 1 shows an example of a configuration including a vehicle rental processing system 100 according to a first embodiment. [Figure 3] 2 shows an example of the configuration of the vehicle rental processing system 100 of FIG. 1. [Figure 4] 4 shows an example of the configuration of the central server 110 in FIG. 3. [Figure 5] 4 is a configuration example of contract data D1 in FIG. 3. [Figure 6] 4 is a configuration example of the driver data D2 in FIG. 3. [Figure 7] 4 is a configuration example of the driving history data D3 in FIG. 3. [Figure 8] 10 shows an example of the flow of processing executed by the driving history management server 120 to generate driving history data D3. [Figure 9] 4 is a configuration example of reservation data D4 in FIG. 3. [Figure 10] 4 shows an example of a processing flow of the central server 110 of FIG. 3. [Figure 11] 10 shows an example of a configuration including a user identification processing system 200 according to a second embodiment. [Figure 12] 1 shows an example of the configuration of a controller 210 of a vehicle 10. [Figure 13] 10 shows an example of a processing flow of the central server 110 according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0018] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. [Embodiment 1] FIG. 1 shows an outline of a contract form for vehicle rental (leasing) according to this embodiment. A vehicle 10 is rented by a lessor to multiple lessees, i.e., contractors. The contractors include a main contractor (first contractor) who enters into a main contract (first contract) and temporary use contractors (second contractors) who enter into temporary use contracts (second contracts). Here, the term "main contractor" can be arbitrarily changed and is not necessarily limited to a contractor who primarily (mainly) uses the vehicle (e.g., a contractor who uses the vehicle for the longest period of time). Similarly, the term "temporary use contractor" can be arbitrarily changed and is not necessarily limited to a contractor who temporarily (e.g., for a short period of time or infrequently) uses the vehicle.
[0019] In the example of Figure 1, Company X and Person A exist as main subscribers, and Company Y and Person B exist as temporary subscribers. In this embodiment, as an example, Company X and Company Y are corporations, and Persons A and B are natural persons. In this embodiment, Persons A and B are employees of Company X and Company Y, respectively, but in modified examples, they do not need to be employees.
[0020] The temporary user may be selected by the landlord based on the recommendation of the main user, and the landlord may enter into a contract with the temporary user. However, the terms of the contract with the temporary user may be changed at will, and are not limited to these conditions.
[0021] Multiple drivers are registered in relation to each contractor. Registered drivers are called "notified drivers," but for simplicity, they may be referred to simply as "drivers" in the drawings and below. In the example of Figure 1, multiple employees of main contractor X are registered as drivers related to the main contractor X (Mr. A, Company X Employee 1, Company X Employee 2). Furthermore, in addition to Mr. A himself, two other drivers related to the main contractor A are registered: Mr. A's relative 1 and Mr. A's relative 2.
[0022] Additionally, several employees of Company Y are registered as drivers related to Company Y (Company Y Employee 1, Company Y Employee 2, Company Y Employee 3). Furthermore, in addition to Mr. B himself, Mr. B's Friend 1 and Mr. B's Friend 2 are registered as drivers related to Mr. B.
[0023] There are no essential restrictions on the relationship between the contractor and the driver, and it can be freely defined depending on the contract content and the type of rental service, etc., and drivers other than employees or friends can also be registered.
[0024] There are multiple main contractors. The handling of cases such as when the contract for one of the main contractors is terminated can be determined by contract or other arrangements. Also, although there are multiple temporary contractors in the example of Figure 1, there may be only one temporary contractor. Furthermore, although there are multiple drivers registered in relation to each contractor in the example of Figure 1, there may be only one driver associated with any or all contractors.
[0025] The number of contractors may be limited according to the requirements of the contract or computer system. For example, the total number of main contractors and temporary contractors may be limited to a maximum of five. Similarly, the number of drivers may also be limited according to the requirements of the contract or computer system. For example, the number of drivers may be limited to a maximum of five per contractor.
[0026] As shown in Fig. 1, one trustee is defined for the rental of the vehicle 10. The duties of the trustee may be determined by a separate contract, but for example, the trustee may clean the vehicle 10, refuel it, take it to a maintenance shop for regular inspection and maintenance, repair it when a breakdown occurs, bring it to a maintenance shop when a breakdown occurs, and determine whether the temporary use contract holder can reserve the vehicle 10.
[0027] The management trustee is the person (natural person) who is the main contract holder and driver, and in the example in Figure 1, it is Mr. A. If there are multiple people who are both main contract holders and drivers, any of them may become the management trustee, but for example, the lessor may appoint one at their discretion.
[0028] Since the management contractor is selected from among the main contractors, hereinafter, the management contractor will be referred to as the "main management contractor," and the main contractor who is not a management contractor will be referred to as the "non-main management contractor." For example, in the example in Figure 1, Mr. A is the main management contractor, and Company X is the non-main management contractor.
[0029] The name of the "management trustee" can be changed arbitrarily and is not limited to the name defined in the contract, etc. Furthermore, in this embodiment, the management of the vehicle 10 is entrusted, but in modified examples, the management of the vehicle 10 may not be entrusted, in which case another name can be used. For this reason, the management trustee main contractor can be simply called the specified first contractor, and a main contractor that is not the management trustee (non-management trustee main contractor) can be simply called the non-specified first contractor.
[0030] FIG. 2 shows an example of a configuration including a vehicle rental processing system 100 according to this embodiment. The vehicle rental processing system 100 is used in connection with a contract for renting a vehicle 10. The vehicle 10 has a well-known configuration (mechanisms and control devices necessary for driving, etc.), and may be, for example, a commercially available automobile. The vehicle 10 is also equipped with, among other things, a GPS receiver 11, a drive recorder 12, and a digital key recognition system 13.
[0031] A physical key 14 and a digital key 15 are provided for use of the vehicle 10. The vehicle 10 is configured to be usable using either the physical key 14 or the digital key 15. A "physical key" refers to a key specific to the vehicle 10, provided by, for example, the manufacturer of the vehicle 10, and is not limited to a metal key configured to be inserted into a keyhole, but also includes a key that can communicate with the vehicle 10 electronically. A "digital key" refers to a key in the form of electronic data that can be installed on, for example, a smartphone, or a program that communicates with the vehicle 10 based on such a key, and is configured to be recognized electronically by the digital key recognition system 13. The digital key may be what is called a smart key.
[0032] The digital key recognition system 13 is generally different from the system for recognizing the physical key 14, but may be the same as the system for recognizing the physical key 14. The digital key 15 can be used, for example, on a smartphone or mobile device via an OS such as iOS or Android, but is not limited to this. Note that the physical key 14 may not be usable via the digital key recognition system 13 or via an OS such as iOS or Android.
[0033] The digital key 15 may be associated with authority to control the vehicle 10, and may be configured, for example, so that operating the digital key 15 alone will unlock the doors of the vehicle 10 and / or enable the engine of the vehicle 10 to start. Alternatively, the digital key 15 may be configured so that it cannot control the vehicle 10 alone, and may be configured, for example, so that communicating with another device (e.g., a physical key placed inside the vehicle) will unlock the doors of the vehicle 10 and / or enable the engine of the vehicle 10 to start.
[0034] The vehicle rental processing system 100 is used in connection with a contract for renting a vehicle 10 to two or more main contractors and one or more temporary use contractors for the same period, and in particular calculates the amount billed for the rental of the vehicle 10. Note that in this embodiment, for the sake of convenience, only one vehicle 10 is shown, but similar processing can be performed when there are multiple vehicles, for example, sequentially or in parallel.
[0035] The vehicle rental processing system 100 also functions as a billing amount calculation system for calculating the billing amount for the rental of the vehicle 10. For example, the vehicle rental processing system 100 can calculate the billing amount for the rental of the vehicle 10 to two or more main contractors and one or more temporary use contractors.
[0036] The vehicle rental processing system 100 can communicate with the vehicle 10 via a communication network. The vehicle 10 has known components necessary for this communication (for example, a control device mounted on the vehicle 10 and an external communication interface). The communication network is, for example, a wired network (such as the Internet or a CAN (Controller Area Network)) and / or a wireless network (using IEEE 802.11, IEEE 802.15.1, etc.).
[0037] Furthermore, vehicle rental processing system 100 may be capable of communicating with one or more client terminals via a communication network. In the example of Figure 2, vehicle rental processing system 100 includes client terminal 21 used by the administrator of vehicle rental processing system 100, client terminal 22 used by the main contractor, and client terminals 23 and 24 used respectively by multiple temporary use contractors.
[0038] The administrator and each contractor may use multiple client terminals or no client terminals depending on the situation. Also, instead of or in addition to each contractor's client terminal, each driver may have a client terminal with the same configuration and functions.
[0039] 3 shows an example configuration of a vehicle rental processing system 100. The vehicle rental processing system 100 includes a central server 110, a driving history management server 120, and a reservation management server 130. The central server 110 stores contract data D1 and driver data D2. Similarly, the driving history management server 120 stores driving history data D3, and the reservation management server stores reservation data D4.
[0040] 4 shows an example of the configuration of the central server 110. The central server 110 has a known hardware configuration as a computer, and includes, for example, a calculation means 111, a storage means 112, and an input / output means 113. The calculation means 111 includes, for example, a processor. The processor can be manufactured using an integrated circuit, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or the like. The storage means 112 includes, for example, a storage medium such as a semiconductor memory device or a magnetic disk device. Part or all of the storage medium may be non-transitory storage media.
[0041] In the central server 110, the contract data D1 and driver data D2 are stored in a storage means 112. The storage means 112 may also store a program (not shown). A processor of a computer may execute the program, causing the computer to perform the functions of the central server 110 described in this embodiment.
[0042] The input / output means 113 includes, for example, input devices such as a keyboard and a mouse, output devices such as a display and a printer, and communication devices such as a network interface. The communication devices can function as both input devices and output devices. The communication devices can perform wired communication and / or wireless communication.
[0043] Although the internal configurations of the driving history management server 120 and the reservation management server 130 are not shown in the drawings, they each have a hardware configuration as a known computer, for example, a configuration similar to the configuration described above for the central server 110. Furthermore, the storage means of the driving history management server 120 stores driving history data D3, and the storage means of the reservation management server 130 stores reservation data D4. Furthermore, although the internal configurations of the client terminals 21 to 24 are not shown in the drawings, they each have a hardware configuration as a known computer, for example, a configuration similar to the configuration described above for the central server 110.
[0044] FIG. 5 shows an example of the configuration of contract data D1. For one or more vehicles, contract data D1 associates a vehicle ID that identifies each vehicle with information about the contractor. The vehicle ID is information that distinguishes multiple vehicles from one another. Contractors include main contractors and temporary use contractors, as described above. Whether a contractor is a main contractor or a temporary use contractor is stored, for example, in the contractor classification column. In the example of FIG. 5, vehicle #1 is associated with Company X and Mr. A as main contractors, and only Mr. A is the main contractor for entrusted management. Furthermore, vehicle #1 is associated with Company Y and Mr. B as temporary use contractors.
[0045] Furthermore, a main subscriber is associated with a contract period, and further associated with a rental fee for each contract unit period within that contract period (for example, one year, one month, one week, etc., which may differ for each main subscriber). The contract period may be a length that includes multiple contract unit periods (for example, a three-year contract period with a one-year contract unit period), or it may coincide with the contract unit period. The rental fee may be determined separately according to the contract, and may differ for each main subscriber. This rental fee is the fee used as the total amount in calculating the billing amount, which will be explained in detail below, and may be referred to below as the "total rental fee." For temporary use subscribers, a rental fee is not set according to the contract unit period.
[0046] 5 does not specifically show the basis for calculating the rental fee, the rental fee may be defined for a unit of time shorter than the contract unit period (for example, a daily or monthly unit), and the rental fee shown in Fig. 5 may be calculated by summing these. The contract data D1 may include details of such a short unit of time.
[0047] The contract data D1 or a copy thereof may be used as a work file in calculating the billing amount, which will be described later. For example, each main contract user may be associated with a rebate fee (the sum of the hourly fees of temporary contract users, which will be described later in relation to Equation 2, etc.) used in the calculation.
[0048] FIG. 6 shows an example of the configuration of driver data D2. Driver data D2 associates one or more drivers with each combination of vehicle and contractor for one or more vehicles. The associated drivers can be selected by the lessor and each contractor based on a separate contract, etc. In the example of FIG. 6, the contractors and drivers shown in FIG. 1 are registered.
[0049] The driver data D2 also associates a digital key ID with each driver. The digital key ID is information that identifies multiple digital key IDs. In this embodiment, each driver is associated with a different digital key ID. Therefore, once the digital key ID used to use the vehicle is identified, the driver can be identified based on the digital key ID.
[0050] However, the vehicle rental processing system 100 does not need to actually perform processing based on the digital key ID recognized by the digital key recognition system 13, and it is also possible to determine who used the vehicle 10 externally to the vehicle rental processing system 100. For example, an administrator of the vehicle rental processing system 100 may identify the driver for a time period based on the contents of the reservation data D4 (described below) and the time period during which the vehicle 10 was used, and input the result into the vehicle rental processing system 100. In either case, the vehicle rental processing system 100 can identify the driver for each use of the vehicle 10. Furthermore, after the digital key ID or the driver has been identified, by referring to the driver data D2, it is possible to identify the contractor related to that use (i.e., the billing party to whom the fee for the use should be charged) based on the digital key ID or the driver.
[0051] In this embodiment, the driver data D2 does not include information about the physical key, but information about the physical key can be stored separately in an appropriate database or the like. Alternatively, as a variant, the driver data D2 may include information about the physical key. For example, if the physical key for the vehicle 10 is loaned to Mr. A, information about the physical key may also be associated with Mr. A. Furthermore, a contract may stipulate that the main management contractor (Mr. A) must always use a physical key. In this case, the association of the digital key ID with the main management contractor (Mr. A) may be omitted.
[0052] 7 shows an example of the configuration of the driving history data D3. The driving history data D3 associates driving histories with one or more vehicles. The driving history represents, for example, the history of use of the vehicle, and includes the date and time of use, the duration of use, and the distance traveled.
[0053] Here, strictly speaking, the use of a vehicle is carried out by a driver, but the system is configured to be able to identify the contractor linked to the driver based on driver data D2, etc., so it can be interpreted that the vehicle was used by one of the contractors, and it is also possible to identify the contractor to whom the fees for that use will be billed.
[0054] In the example of FIG. 7, the usage date and time represents a time period defined by the usage start date and time and the usage end date and time, but the expression format is not limited to this. The usage start date and time is, for example, the time when the door lock of the vehicle 10 is released, the time when the key is turned on, the time when the ignition is turned on, or the time when the engine is started, but is not limited to these. The usage end time is, for example, the time when the door lock of the vehicle 10 is set, the time when the key is turned off, the time when the ignition is turned off, or the time when the engine is stopped, but is not limited to these. The usage time represents the time when the vehicle was used, and is expressed in minutes, for example. Note that in the example of FIG. 7, the usage time may be omitted (in which case, the usage time can be calculated from the usage start date and time and the usage end date and time). The mileage represents the distance traveled by the vehicle during each use, and is expressed in kilometers, for example.
[0055] Alternatively, the driving history may further include a digital key ID. In this case, by referencing the driver data D2 based on the digital key ID, it becomes possible to automatically identify the driver associated with each driving history.
[0056] Fig. 8 shows an example of the flow of processing executed by the driving history management server 120 to generate driving history data D3. The processing in Fig. 8 is started, for example, when the vehicle 10 starts to be used, but can also be started when the vehicle 10 ends to be used. The following description will be given with reference to Fig. 8.
[0057] The driving history management server 120 acquires the date and time of use and the mileage (step S1). The specific method for acquiring the date and time of use may be designed in any way, but for example, a predetermined mileage measurement device may be used. The vehicle rental processing system 100 may be equipped with such a mileage measurement device. The mileage acquisition device may include, for example, a GPS receiver 11 (see FIG. 2), and may acquire the mileage based on the distance traveled by the vehicle 10. In another example, the mileage acquisition device may include a device for detecting the number of wheel rotations, and may acquire the mileage based on the number of wheel rotations. Various other known mileage acquisition devices may also be used. The vehicle rental processing system 100 or the central server 110 may acquire the date and time when the vehicle 10 was used, the length of time for which the vehicle was used, and the mileage of the vehicle 10 based on information from such a mileage measurement device.
[0058] Next, the driving history management server 120 updates the driving history data D3 (step S2). For example, the driving history data D3 may be stored in association with information identifying the vehicle involved in the new use (vehicle ID), the date and time of use, the duration of use, and the distance traveled.
[0059] The specific timing and processing content of communication between the devices installed in the vehicle 10 (GPS receiver 11, drive recorder 12, digital key recognition system 13, other mileage acquisition devices, etc.) and the driving history management server 120 can be appropriately designed by a person skilled in the art based on publicly known technologies, etc.
[0060] Although one example has been described above, a specific example of the process for generating the driving history data D3 is not limited to the one shown in FIG. 8 and can be designed appropriately by a person skilled in the art.
[0061] 9 shows an example of the configuration of reservation data D4. The reservation data D4 associates one or more usage plans with one or more vehicles. The usage plan includes, for example, the scheduled usage date and time and information indicating the temporary usage contractor involved in the usage. The scheduled usage date and time includes, for example, the usage start date and time and the usage end date and time.
[0062] The contents of the reservation data D4 can be updated as needed by the temporary use contractor for each vehicle (or each driver associated with the temporary use contractor) with the permission of the main contractor. The temporary use contractor can view and update the contents of the reservation data D4 by accessing the reservation management server 130, for example, from the client terminal 23 or the client terminal 24. In this way, the reservation management server 130 accepts and stores input of the planned date and time when the temporary use contractor (or each driver associated with the temporary use contractor) will use the vehicle 10. By preparing such reservation data D4, it is possible to confirm in advance that there will be no conflicts in planned use between the main contractor and the temporary use contractor, or between temporary use contractors themselves.
[0063] In this embodiment, reservation data D4 does not include the use schedule of the main subscriber, but if the temporary use subscriber obtains permission from the management entrusted main subscriber when updating reservation data D4 (this may be stipulated in a contract or other arrangement, for example), conflicts in use schedules between the main subscriber and the temporary use subscriber can be avoided. As a variation, reservation data D4 may include the use schedule of the main subscriber.
[0064] In addition, in this embodiment, there are multiple main subscribers, but by making arrangements such as reaching an agreement in advance between the main subscribers regarding usage times and separately sharing usage schedules, conflicts of usage between the main subscribers can be avoided.
[0065] 10 shows an example of the processing flow of the central server 110. In particular, FIG. 10 shows an example of processing as a billing amount calculation system. The operation of the central server 110 will be described below with reference to FIG.
[0066] The process of Fig. 10 is executed, for example, as needed in response to an operation by an administrator of the vehicle rental processing system 100, or periodically in response to a contract period, etc. The process of Fig. 10 is also executed for each vehicle (more precisely, for each vehicle ID). The following describes the process related to vehicle 10 as an example.
[0067] In the process of FIG. 10, the central server 110 first acquires the contract data D1 (step S11).
[0068] Next, the central server 110 receives and acquires the driving history data D3 from the driving history management server 120, and further refers to this to acquire the driving history of the vehicle 10 (step S12). Here, for each use of the vehicle 10, the central server 110 acquires the date and time when the vehicle 10 was used, the duration for which the vehicle 10 was used, and the distance traveled by the vehicle 10. The central server 110 may also receive and acquire reservation data D4 from the reservation management server 130. It is assumed that the vehicle 10 is used in accordance with the reservation in the reservation data D4, and the reservation data D4 includes the start date and time and end date and time of use of the vehicle 10, i.e., it can be considered to include the date and time when the vehicle 10 was used and the duration for which the vehicle 10 was used.
[0069] Next, the central server 110 calculates the hourly fee for each temporary use contractor (Company Y and Mr. B in this embodiment) related to the vehicle 10 (step S13). For example, the central server 110 calculates the hourly fee for each temporary use contractor (and thus the billing amount, as will be described later) based on the time the vehicle was used for each use related to each temporary use contractor (more precisely, use by each driver related to each temporary use contractor).
[0070] Here, the method for determining which of the multiple driving histories included in the driving history data D3 belongs to a temporary use contractor can be designed as appropriate, as described above. For example, the administrator of the vehicle rental processing system 100 may refer to the reservation data D4 to identify the driver or contractor associated with each driving history and input the results into the vehicle rental processing system 100. Alternatively, if the driving history data D3 includes a digital key ID, the central server 110 may refer to the driver data D2 based on the digital key ID and automatically identify the contractor. Alternatively, the central server 110 may refer to the reservation data D4 and, if the vehicle 10 is used within a time period corresponding to one of the scheduled dates and times, process the use as if it were used by the corresponding temporary use contractor.
[0071] For example, the hourly fee can be calculated by multiplying the usage time by the hourly rate, that is, based on the following formula: <Temporary use contract hourly rate> = <Total usage time> × <Hourly rate>… (Formula 1) Note that Equation 1 is an example, and other calculations may be used in addition to or instead of multiplication. Also, factors other than the usage time and the hourly rate may be taken into consideration. The hourly rate may vary depending on the time of day. In this case, the central server 110 or another computer may store information indicating the relationship between the time of day and the hourly rate. The hourly rate may differ for each subscriber.
[0072] Next, the central server 110 acquires the total rental fee for each main contractor (step S14). The total rental fee can be acquired based on the contract data D1 as described above, for example, but the acquisition method can be designed arbitrarily.
[0073] Next, the central server 110 calculates the rental fee for each main contractor (Company X and Mr. A in this embodiment) related to the vehicle 10 (step S15). The rental fee for the main contractor is calculated based on, for example, the total rental fee for the main contractor and the duration of use of the vehicle 10 for each use related to each temporary use contractor.
[0074] As an example, the rental fee for each main contractor can be calculated by subtracting the deduction for the use of each temporary user contractor (which can be called a "rebate fee") from the total rental fee for that main contractor, that is, it can be calculated based on the following formula. <Rental fee for main user> = <Total rental fee> - <Total usage time for each temporary user> × <Hourly rate> … (Formula 2) In Equation 2, the usage time of the temporary user contract refers only to the time period included in the period corresponding to the total rental fee. Also, in Equation 2, the hourly rate may be fixed, but it may also be different for each main contract.
[0075] In this way, the central server 110 calculates the amount to be charged to each main contractor based on the total rental fee and the time the vehicle 10 was used for each use related to each temporary use contractor (in other words, the time each main contractor was unable to use the vehicle 10). Note that Equation 2 is an example, and other calculations may be used in addition to or instead of subtraction. Also, factors other than the total rental fee and the hourly fee may be taken into consideration.
[0076] Next, the central server 110 calculates the amount equivalent to the fuel cost for each temporary use contractor related to the vehicle 10 (step S16). For example, the amount equivalent to the fuel cost for each temporary use contractor is calculated based on the mileage of the vehicle for each use by the temporary use contractor (more precisely, for each use by each driver related to each temporary use contractor). The amount billed to each temporary use contractor is calculated based on this amount equivalent to the fuel cost, as will be described later.
[0077] As an example, the amount equivalent to the fuel cost for the temporary use subscriber can be calculated by multiplying the distance traveled by the cost per distance, that is, based on the following formula. <Fuel cost equivalent for temporary user> = <Total distance traveled> x <Distance cost> … (Formula 3) Note that Equation 3 is an example, and operations other than multiplication may be used, and factors other than the mileage and the distance cost may be considered. The distance cost may be determined in advance as appropriate depending on the price of fuel such as gasoline, but may also be changed as needed, for example, by the administrator depending on fluctuations in the price of gasoline. The distance cost may also differ for each subscriber.
[0078] Next, central server 110 calculates the fuel cost equivalent for each non-management main contractor (only Company X in this embodiment) associated with vehicle 10 (step S17). For example, the fuel cost equivalent for each non-management main contractor is calculated based on the vehicle's mileage for each use associated with the relevant main contractor (more precisely, use by each driver associated with the non-management main contractor). The amount billed to each non-management main contractor is calculated based on this fuel cost equivalent.
[0079] As an example, the fuel cost equivalent for a non-managed main contractor can be calculated by multiplying the distance traveled by the cost per distance, in the same way as for a temporary use contractor, that is, based on the following formula. <Fuel cost equivalent for non-management main contractor> = <Total distance traveled> x <Distance cost> … (Formula 4) Note that Equation 4 is an example, and operations other than multiplication may be used, and factors other than the mileage and the distance cost may be considered. The distance cost may be determined in advance as appropriate depending on the price of fuel such as gasoline, but may also be changed as needed, for example, by the administrator depending on fluctuations in the price of gasoline. The distance cost may also differ for each subscriber.
[0080] Next, central server 110 acquires the total fuel cost for the management entrusted main contractor (step S18). The total fuel cost may be stored in advance in storage means 112 of central server 110, or may be acquired from an external computer (for example, a computer that manages fuel costs at the lender) when step S18 is executed. The method for acquiring the total fuel cost can be designed as desired.
[0081] The total fuel cost can be, for example, the total cost of fuel (for example, gasoline, but it can also be hydrogen or other fuel) supplied to vehicle 10 within the contract unit period (within the period corresponding to the total rental fee). As an example of a specific procedure, if the lessor lends a credit card for fuel supply to the management entrusted main contractor in advance and the management entrusted main contractor uses that credit card when supplying fuel, the amount charged to that credit card (or the total thereof) can be used as the total fuel cost.
[0082] Next, central server 110 calculates the fuel cost equivalent for the management main contractor (Mr. A in this embodiment) for vehicle 10 (step S19). The fuel cost equivalent for the management main contractor is calculated, for example, based on the total fuel cost, the fuel cost equivalent for each temporary use contractor, and the fuel cost equivalent for each non-management main contractor.
[0083] As an example, the amount equivalent to the fuel cost for the management main contractor can be calculated by subtracting the amount equivalent to the fuel cost for each temporary use contractor from the total fuel cost, and then subtracting the amount equivalent to the fuel cost for each non-management main contractor, that is, it can be calculated based on the following formula. <Fuel cost equivalent amount for management main contract holder> = <Total fuel cost> - <Total sum of fuel cost equivalent amounts for all temporary use contract holders> - <Total sum of fuel cost equivalent amounts for all non-management main contract holders> … (Formula 5) In other words, the amount equivalent to the fuel costs for the main management contractor is the total fuel cost minus the amount equivalent to the fuel costs for all contractors other than the main management contractor.
[0084] Note that Equation 5 is an example, and calculations other than subtraction may be used, and factors other than the total fuel cost and the amount equivalent to the fuel cost for each contractor may be considered. For example, a predetermined fee may be added. This fee may vary depending on the distance traveled.
[0085] Next, the central server 110 calculates the amount to be charged to each contractor (step S20). For example, the amount can be calculated by adding the fuel cost equivalent amount and the rental fee or time fee, that is, the amount can be calculated based on the following formulas. <Amount billed to the management main contracting party> = <Rental fee to the management main contracting party> + <Amount equivalent to fuel costs to the management main contracting party> … (Equation 6) <Amount billed to non-management main contractor> = <Rental fee to the non-management main contractor> + <Amount equivalent to fuel costs to the non-management main contractor>… (Equation 7) <Amount billed to temporary use contract holder> = <Hourly fee for said temporary use contract holder> + <Amount equivalent to fuel cost for said temporary use contract holder> … (Equation 8)
[0086] Note that Equations 6 to 8 are examples, and calculations other than addition may be used, and factors other than the fuel cost equivalent, rental fee, and hourly rate may be considered. For example, taking into consideration that the value (assessed value) of the vehicle decreases depending on the mileage, an amount equivalent to the assessed decrease may be added to the amount claimed. The amount equivalent to the assessed decrease can be calculated, for example, using the following equation: <Amount equivalent to the assessed reduction> = <Distance traveled> × <Unit price of assessed reduction> … (Equation 9) The amount equivalent to the assessed reduction can be calculated for each of the management contract main contract holder, non-management contract main contract holder and temporary use contract holder according to the mileage and added to the respective billing amount.
[0087] In addition, ETC usage fees may be added to the amount billed to the management contract main contractor. In this case, the process for acquiring ETC usage fees can be appropriately designed by a person skilled in the art based on known technology, etc.
[0088] Next, central server 110 notifies each subscriber of the amount due by individual e-mail (step S21). That is, central server 110 notifies each main subscriber of the amount due by individual e-mail, and notifies each temporary use subscriber of the amount due by individual e-mail.
[0089] The email may include, for example, at least the name of the lessor, the name of the contractor, and the amount claimed. It may also include other information, such as a breakdown of the amount claimed, driving history, mileage, driving time, etc. The wording can be prepared in advance by a person skilled in the art or the lessor as appropriate. The specific processing for sending the email can be designed as appropriate by a person skilled in the art based on publicly known technology, etc.
[0090] Thereafter, the actual billing procedure may be performed. Although the billing procedure is not shown in the flowchart of FIG. 10, it can be performed automatically by the vehicle rental processing system 100 or another computer, or based on instructions input from an administrator. The details of the processing related to the billing procedure can be appropriately designed by a person skilled in the art based on known techniques, etc.
[0091] As described above, according to the vehicle rental processing system 100 of embodiment 1, when one vehicle is rented to multiple contractors within the same contract period, the amount billed to each contractor is automatically calculated, making it easier for the administrator to settle the billed amount.
[0092] In particular, the vehicle rental processing system 100 calculates the amount billed to each temporary use contractor for a specific contract period (first contract period) based on the amount of time and fuel costs associated with the temporary use contractor's vehicle usage, while calculating the amount billed to at least one main contractor (management main contractor) for the same period (first contract period) based on the total rental fee, the total fuel costs, and the amount of time and fuel costs associated with the vehicle usage of each temporary use contractor. Furthermore, the system calculates the amount billed to other main contractors (non-management main contractors) for the same period (first contract period) based on the total rental fee, the amount of fuel costs, and the amount of time and fuel costs associated with the vehicle usage of each temporary use contractor. In this way, rentals to multiple contractors within the same contract period can be appropriately processed.
[0093] Those skilled in the art can arbitrarily add, modify, or delete components in the above-described first embodiment. For example, in the first embodiment, the central server 110 calculates the billing amount for each temporary use subscriber based on both the time the vehicle was used and the distance traveled by the vehicle, but it is not necessary to use both of these; at least one of the time the vehicle was used and the distance traveled by the vehicle may be used. In that case, the central server 110 may acquire at least one of the time the vehicle was used and the distance traveled by the vehicle in step S12 of FIG. 10.
[0094] In the first embodiment, the vehicle rental processing system 100 is configured with three computers as shown in FIG. 3, but it may also be configured with one computer, or with two or four or more computers. In that case, a person skilled in the art can appropriately design which computer executes each step described in FIGS. 8 and 10. The vehicle rental processing system 100 may also include client terminals (e.g., client terminals 21 to 24) as shown in FIG. 2.
[0095] Data (e.g., contract data D1, driver data D2, driving history data D3, reservation data D4, etc.) may be stored in an external computer or storage device that is not included in vehicle rental processing system 100. In this case, a component of vehicle rental processing system 100 (e.g., central server 110) can obtain the necessary information from the external computer or storage device at an appropriate time.
[0096] The order of the steps shown in Figures 8 and 10 is not limited to that shown in the figures and can be changed as appropriate. For example, step S14 in Figure 10 can be executed at any time after step S11 and before step S15.
[0097] [Embodiment 2] FIG. 11 is a configuration example including a user identification processing system 200 according to a second embodiment. The second embodiment is a configuration example including the user identification processing system 200. The user identification processing system 200 executes processing for identifying a user of the vehicle 10. The user identification processing system 200 also uses an authentication card 215 (an item carried by the user). The authentication card 215 has a function for short-range wireless communication such as NFC (Near Field Communication). Specific examples of the authentication card 215 include a My Number card, a driver's license, a credit card, a cash card, an electronic transportation card, an employee ID card, and a point card. The authentication card 215 may also be a medium with an NFC function, such as a smartphone. It is preferable that the authentication card 215 is capable of identifying the user.
[0098] FIG. 12 shows an example of the configuration of the controller 210 of the vehicle 10. The controller 210 is mounted on the vehicle 10. The controller 210 has a hardware configuration as a known computer, and includes, for example, a calculation means 211, a storage means 212, and an input / output means 213. The calculation means 211 includes, for example, a processor. The processor can be manufactured using an integrated circuit, an ASIC, an FPGA, or the like. The storage means 212 includes, for example, a storage medium such as a semiconductor memory device or a magnetic disk device. Part or all of the storage medium may be non-transitory storage media.
[0099] The input / output means 213 includes, for example, input devices such as a camera, a card reader 214, operation buttons, and a touch panel provided in the cabin of the vehicle 10, output devices such as a display and a speaker, and a communication device such as a network interface. The card reader 214 has a function for short-range wireless communication with the authentication card 215. That is, the card reader 214 can acquire ID information from the authentication card 215 by communicating with the authentication card 215. The communication device can function as both an input device and an output device. The communication device can perform wired communication and / or wireless communication.
[0100] Fig. 13 shows an example of the processing flow of the central server 110 according to the second embodiment. Fig. 13 particularly shows an example of the processing of the user identification processing system 200. The operation of the central server 110 according to the second embodiment will be described below with reference to Fig. 13.
[0101] The processing in FIG. 13 is executed as needed or periodically, for example, in response to the use of the vehicle 10 by the user. In the processing in FIG. 13, first, the central server 110 acquires ID information of the authentication card 215 (step S101). Specifically, the user enters the cabin of the vehicle 10 using the physical key 14 and holds the authentication card 215 over the card reader 214. As a result, the controller 210 of the vehicle 10 acquires the ID information stored in the authentication card 215 via the input / output means 213. The controller 210 of the vehicle 10 stores the acquired ID information in the storage means 212. The controller 210 of the vehicle 10 transmits the ID information to the central server 110 via a communication device included in the input / output means 213. As a result, the central server 110 can acquire the ID information of the authentication card 215 from the controller 210 of the vehicle 10 (step S101). In addition, the controller 210 of the vehicle 10 may transmit the ID information to the central server 110 each time it acquires the ID information (at any time), or may store the ID information and the date and time when it was acquired in the storage means 212 for a certain period (for example, the period of the contract unit mentioned above) and transmit the ID information and the date and time when it was acquired to the central server 110 every certain period (periodically).
[0102] Next, the central server 110 identifies the user from the ID information (step S102). Specifically, the central server 110 associates ID information with users (main subscribers and temporary use subscribers) and stores the ID information in advance in the storage means 112, and identifies the user by comparing the ID information acquired in step S101 with the user. The central server 110 then stores the date and time of use of the vehicle 10 by the user in the storage means 112 (step S103), and terminates this routine. If the processing of FIG. 13 is executed as needed in response to the user's use of the vehicle 10, the date and time of use of the vehicle 10 may be the time when the central server 110 acquired the ID information. Furthermore, if the ID information and the date and time when the ID information was acquired are acquired from the controller 210 of the vehicle 10 at regular intervals, the "date and time when the ID information was acquired" included in the information acquired from the controller 210 may be used as the date and time of use of the vehicle 10.
[0103] This allows the central server 110 to identify the user of the vehicle 10 based on the user's operation of holding the authentication card 215 over the card reader 214. In particular, since the controller 210 of the vehicle 10 acquires ID information using the authentication card 215, the cost of implementing the user identification processing system 200 can be reduced.
[0104] The central server 110 executes the user identification processing system 200, thereby facilitating switching of usage modes by users. For example, referring to FIG. 1, Mr. A is an employee of Company X and also a main contractor. As a specific example, when Mr. A uses the vehicle 10 as an employee of Company X, he holds, for example, his transportation electronic card as the authentication card 215 over the card reader 214. When Mr. A uses the vehicle 10 for personal use, he holds, for example, his driver's license as the authentication card 215 over the card reader 214. This allows the usage mode to be switched using the authentication card 215 even when the same person has different usage modes. Therefore, the central server 110 can identify users and their usage modes by, for example, previously storing ID information and users in the storage means 112, linked to each usage mode.
[0105] Furthermore, by identifying the user of the vehicle 10 in this way, the central server 110 can improve the accuracy of various processes, such as the processing as a billing amount calculation system (FIG. 10). For example, in step S12, when acquiring the driving history data D3 from the driving history management server 120, the user, usage mode, and usage date and time of the vehicle 10 are used, thereby making it possible to identify the user and usage mode corresponding to the usage date and time of the vehicle 10. Therefore, the accuracy of calculation of the fee for each contractor in the processing from step S13 onwards can be improved.
[0106] As described above, the user identification processing system 200 according to the second embodiment stores the user who used the vehicle 10 for each use of the vehicle 10, thereby enabling the billing amount to be calculated appropriately. Furthermore, the vehicle 10 acquires a user ID from an item carried by the user, such as an authentication card 215, and the user identification processing system 200 identifies the user from the user ID. This allows the user to be appropriately identified with a simple configuration. In particular, the user identification processing system 200 identifies the usage mode of the vehicle 10 by the user based on the user ID, and can identify the user and usage mode based on the authentication card 215 even when there is a user who can use the vehicle 10 in multiple usage modes.
[0107] The above has described the user identification processing system 200 according to the second embodiment, but these are merely examples and can be modified as appropriate. For example, in the second embodiment, it has been described that Mr. A uses two types of authentication cards 215. However, it is also possible for Mr. A to hold his authentication card 215 over the card reader 214 only when he personally uses the vehicle 10. In other words, when Mr. A uses the vehicle 10 as an employee of Company X, he does not hold his authentication card 215 over the card reader 214 and uses the vehicle 10 as is. As a result, for example, when the vehicle 10 is used without holding the authentication card 215 over the card reader 214, the user identification processing system 200 may determine that the vehicle 10 is being used by employees of Company X, including Mr. A. [Explanation of symbols]
[0108] 10...Vehicle 11...GPS receiver 12...Dashcam 13...Digital key recognition system 14...Physical key 15...Digital key 21~24: Client terminal 100...Vehicle rental processing system 110...Central server 120...Driving history management server 130...Reservation management server 200...User identification processing system 215...Authentication card (item carried by user) D1...Contract data D2: Driver data D3: Driving history data D4...Reservation data
Claims
1. A billing amount calculation system that calculates a billing amount for a vehicle loan to two or more first contractors and one or more second contractors, The billing amount calculation system includes: - for each of said vehicle uses, - the date and time when the vehicle was used; At least one of the time the vehicle is used and the distance traveled by the vehicle; Get - calculating the amount to be charged to each of the second contractors based on at least one of the time the vehicle was used and the distance traveled by the vehicle for each of the uses relating to each of the second contractors; Billing amount calculation system.
2. 2. The billing amount calculation system according to claim 1, The billing amount calculation system includes: - Obtain the total rental fee for each primary contractor; - calculating the amount to be charged to each of the secondary contractors based on the duration of the vehicle use for each of the uses relating to each of the secondary contractors; - calculating the amount to be charged to each of the first contractors based on the total rental fee and the duration of use of the vehicle for each of the second contractors; Billing amount calculation system.
3. 2. The billing amount calculation system according to claim 1, Any of the first contractors is a specified first contractor, The other person of the first contractor is an unspecified first contractor, The billing amount calculation system includes: - Obtain the total fuel cost, - calculating the fuel cost equivalent for each of the second contractors based on the mileage of the vehicle for each of the uses related to each of the second contractors; - calculating the amount to be claimed for each of the second contractors based on the fuel cost equivalent for each of the second contractors; - Calculating the amount equivalent to the fuel cost for each of the unspecified first contractors based on the mileage of the vehicle for each of the uses related to the unspecified first contractors; - calculating the amount to be claimed from each of the non-specified primary contractors based on the amount equivalent to the fuel costs for each of the non-specified primary contractors; - calculating the amount to be claimed from the specified primary contractor based on the total fuel cost, the amount equivalent to the fuel cost for each of the secondary contractors, and the amount equivalent to the fuel cost for each of the unspecified primary contractors; Billing amount calculation system.
4. 2. The billing amount calculation system according to claim 1, The billing amount calculation system further includes a mileage measurement device, and acquires the time during which the vehicle is used and the mileage of the vehicle based on information from the mileage measurement device. Billing amount calculation system.
5. 2. The billing amount calculation system according to claim 1, Accepting and storing input of the date and time when each of the second contractors plans to use the vehicle; Billing amount calculation system.
6. 2. The billing amount calculation system according to claim 1, The billing amount calculation system includes: notifying each of said first contractors of the amount due by email; notifying each of the secondary contractors of the amount due by email; Billing amount calculation system.
7. 2. The billing amount calculation system according to claim 1, For each use of the vehicle, store the user who used the vehicle; Billing amount calculation system.
8. 8. The billing amount calculation system according to claim 7, The vehicle acquires a user ID from an item carried by the user, The billing amount calculation system identifies the user from the user ID. Billing amount calculation system.
9. 9. The billing amount calculation system according to claim 8, The billing amount calculation system identifies the manner of use of the vehicle by the user based on the user ID. Billing amount calculation system.
10. A program that causes a computer to function as the billing amount calculation system according to claim 1.
11. A method for calculating a claim amount for a vehicle loan to two or more first contractors and one or more second contractors, the method comprising: The billing amount calculation method is - the computer calculates, for each of said vehicle uses, - the date and time when the vehicle was used; At least one of the time the vehicle is used and the distance traveled by the vehicle; obtaining a - calculating by a computer an amount to be charged to each of the second contractors for each of the uses related to each of the second contractors based on at least one of the time during which the vehicle was used and the distance traveled by the vehicle; A billing amount calculation method comprising:
12. A billing amount calculation system that calculates a billing amount for a vehicle loan to two or more first contractors and one or more second contractors, - calculating the amount to be charged to each of the secondary contractors for the first contract period based on the time and fuel costs of the vehicle used by that secondary contractor; - calculating the amount to be charged to at least one first contractor for the first contract period based on the total rental fee, the total fuel cost, and the time and fuel cost equivalent for the use of the vehicle for each second contractor; Billing amount calculation system.
Citation Information
Patent Citations
Vehicle management server, and computer program
JP2017102553A