JP5098585B2 - Billing distribution system, in-vehicle terminal, and billing distribution method - Google Patents

Description

  The present invention relates to a charging distribution system, an in-vehicle terminal, and a charging distribution method for distributing a fuel cost of a vehicle to either a fuel cost to be charged or a fuel cost not to be charged.

  In recent years, there has been a remarkable spread of car navigation systems. In addition, as a simplified version of a car navigation system, an increasing number of users use simple vehicle-mounted terminals such as PND (Personal Navigation Device).

  At the same time as broadband communication and wireless communication have been improved and spread, short-range wireless communication using a non-contact IC chip and the like as represented by mobile Suica has also spread.

  Under such circumstances, in-vehicle terminals that can use short-range wireless communication are applied to various services.

For example, Patent Document 1 discloses that an in-vehicle terminal performs short-range wireless communication with a service device of a fueling station. According to this, when the vehicle visits the store, there is an advantage that the vehicle can be quickly identified and appropriate action can be taken.
JP 2006-096060 A

  By the way, in local companies, there are very many employees who use vehicles as commuting means. However, the present situation is that each company has an ambiguous method for charging transportation costs, which are fuel costs for vehicles.

  Employees tend to find fuel stations with low fuel prices, especially for private use, and refuel, but when charging for transportation expenses, it is also possible to charge a fee calculated at a high fuel price. It is done. In addition, with the recent soaring refueling price, the price of the refueling station is also inevitable, and there is a strong desire to lock in customers in order to secure stable profits.

  Therefore, for a company, it is assumed that the vehicle will be refueled in partnership with a specific fuel station, and the fuel cost of the vehicle in that case will be charged to the employee, Alternatively, it is a very important issue to allocate to one of the non-chargeable fuel costs that the company bears as transportation costs.

  Therefore, an object of the present invention is to provide a charging distribution system, an in-vehicle terminal, and a charging distribution method that solve the above-described problems.

In order to achieve the above object, the billing distribution system of the present invention includes:
A charging distribution system that distributes the fuel cost of a vehicle to either a fuel cost subject to billing or a fuel cost not subject to billing,
Route data registration means for registering the planned route data of the vehicle in advance;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data Data registration means;
Refueling history data registration means for registering the fuel unit price of the refueled fuel as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Means,
Charge distribution means for distributing the actual fuel cost of the travel history data in which the flag is ON to a fuel cost that is not charged.

In order to achieve the above object, the in-vehicle terminal of the present invention
An in-vehicle terminal that distributes the fuel cost of a vehicle to either a fuel cost subject to billing or a fuel cost not subject to billing,
Route data registration means for registering the planned route data of the vehicle in advance;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data Data registration means;
Refueling history data registration means for registering the fuel unit price of the refueled fuel as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Means,
Charge distribution means for distributing the actual fuel cost of the travel history data in which the flag is ON to a fuel cost that is not charged.

In order to achieve the above object, the billing distribution method of the present invention includes:
A charging distribution method performed by an in-vehicle terminal that distributes the fuel cost of a vehicle to either a fuel cost subject to charging or a fuel cost not subject to charging,
A route data registration step for pre-registering the planned route data of the vehicle;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data A data registration step;
A refueling history data registration step of registering a fuel unit price of fuel supplied as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Steps,
A charge distribution step of distributing the actual fuel cost of the travel history data whose flag is ON to the fuel cost not charged.

  According to the present invention, on the assumption that the vehicle travels in accordance with the planned route data registered in advance, when the vehicle travels according to the planned route data, the fuel cost consumed during the travel is not charged. Since it is the structure which distributes to expense, the effect that the fuel cost of a vehicle can be allocated to either the fuel cost of charge object, or the fuel cost which is not charge object is acquired.

  In addition, since the fuel cost that is not charged is calculated using the fuel consumption during travel and the unit price of fuel, there is an effect that the fuel cost can be accurately calculated.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

(First embodiment)
FIG. 1 shows a configuration of a billing distribution system according to an embodiment of the present invention.

  In the following description, the present invention is a billing that allocates the fuel cost of a vehicle to either the billing fuel cost billed to the employee or the non-billing fuel cost billed by the company as a transportation cost. Although described as being a distribution system, the present invention is not limited to this, and the present invention is not limited to this, and can be applied to any charging distribution system that distributes the fuel cost of a vehicle to either a fuel cost to be charged or a fuel cost to be charged. It is possible to apply.

  As shown in FIG. 1, the charging distribution system of the present embodiment includes an in-vehicle terminal 10, a PC (Personal Computer) terminal 20, and a charging management server 30.

  In the present embodiment, short-range wireless communication / infrared communication is performed between the in-vehicle terminal 10 and the refueling machine 40 outside the system, and between the in-vehicle terminal 10 and the PC terminal 20. Further, it is assumed that HTTP / HTTPS communication is performed between the in-vehicle terminal 10 and the charge management server 30. Further, it is assumed that LAN communication is performed between the PC terminal 20 and the charge management server 30.

  The in-vehicle terminal 10 is a simple in-vehicle terminal such as a PND that can be carried by an employee as a user, and has a simple car navigation function. The in-vehicle terminal 10 performs various operations by means realized by executing the in-vehicle terminal application downloaded from the billing management server 30, and detailed description thereof will be described later.

  When the address and telephone number of the departure point and destination point are input, the PC terminal 20 displays a route search function for searching for a route from the departure point to the destination point, and displays or transfers the searched route to the in-vehicle terminal 10. It has a function to do. Furthermore, the PC terminal 20 has a function of transferring various data received from the in-vehicle terminal 10 to the accounting management server 30 and a function of authenticating the in-vehicle terminal 10.

  The billing management server 30 has a function of providing an in-vehicle terminal application executed in the in-vehicle terminal 10 to the in-vehicle terminal 10.

  The refueling machine 40 is installed in a refueling stand and supplies fuel such as gasoline to the vehicle. When receiving the refueling request from the in-vehicle terminal 10, the refueling machine 40 refuels the vehicle by the amount requested from the in-vehicle terminal 10.

  FIG. 2 shows the configuration of the in-vehicle terminal 10.

  As shown in FIG. 2, the in-vehicle terminal 10 includes a control unit 11, a storage unit 12, a communication unit 13, a wireless communication unit 14, and an application acquisition unit 15.

  The control unit 11 performs basic operation control of the entire in-vehicle terminal 10 such as task management and memory management, and includes a communication control unit 111, a route data registration unit 112, a travel history data registration unit 113, and a fuel supply. A history data registration unit 114, a fuel cost calculation unit 115, and a billing distribution unit 116 are included.

  The storage unit 12 includes a travel history database (DB, hereinafter the same) 121, a user database 122, a fuel supply history database 123, and a route database 124.

  The communication unit 13 performs HTTP / HTTPS communication with the charge management server 30.

  The wireless communication means 14 performs short-range wireless communication / infrared communication between the PC terminal 20 and the fueling device 40.

  The application acquisition unit 15 acquires the in-vehicle terminal application from the charge management server 30 via the communication unit 13. The route data registration unit 112, the travel history data registration unit 113, the refueling history data registration unit 114, the fuel cost calculation unit 115, and the billing distribution unit 116 may use the in-vehicle terminal application acquired by the application acquisition unit 15. This is realized by executing by an application execution means (not shown).

  The communication control unit 111 controls the communication unit 13 and the wireless communication unit 14.

  The route data registration unit 112 registers vehicle route data received from the PC terminal 20 via the wireless communication unit 14 in the route database 124 in advance. The route data (GPS format) registered by the PC terminal 20 and the route data transferred from the PC terminal 20 to the in-vehicle terminal 10 have the same data format.

  The travel history data registration unit 113 registers travel history data in the travel history database 121 for each travel history.

  The refueling history data registration unit 114 registers the refueling history data received from the refueling machine 40 via the wireless communication unit 14 in the refueling history database 123 for each refueling history.

  The fuel cost calculation means 115 calculates the fuel cost of the vehicle among the travel history data registered in the travel history database 121, and additionally registers the calculated fuel cost as travel history data in the travel history database 121.

  The charging apportioning means 116 is the fuel cost of the charging object for charging the vehicle fuel cost of the driving history data registered in the driving history database 121 to the employee, or the non-charging fuel that the company bears as the transportation cost. Allocate to one of the expenses.

  In the travel history database 121, for each travel history (travel history ID), the route ID 121a of the route data set by the employee at the start of travel and the travel history data 121b are registered. The travel history data 121b includes a travel distance (scheduled / actual), fuel consumption (actual), fuel consumption (actual), fuel cost (scheduled / actual), and a route indicating whether the vehicle traveled according to the planned route data. And a determination flag (see FIGS. 6 and 8).

  User data is registered in the user database 122. The user data includes a user ID 122a, individual identification information 122b uniquely assigned to the in-vehicle terminal 10, and a refueling availability flag 122c indicating whether refueling is possible.

  In the refueling history database 123, refueling history data is registered for each refueling history (refueling history ID). The refueling history data includes a refueling amount 123a and a fuel unit price (price per liter) 123b.

  In the route database 124, for each route (route ID), route data 124a, an expiration date 124b, and a scheduled use count 124c are registered.

Hereinafter, the operation of this embodiment will be described.
[When downloading applications for in-vehicle devices]
Initially, the operation | movement at the time of the download of the application for vehicle-mounted terminals is demonstrated with reference to FIG. Here, the telecommunications carrier providing the service registers in advance in the billing management server 30 a pair of the user name of the employee belonging to the company and the user ID uniquely assigned to the user name. Also, it is assumed that the password assigned to the user ID is distributed to the employees.

  As shown in FIG. 3, first, in the in-vehicle terminal 10, the application acquisition unit 15 requests the charging management server 30 to download the in-vehicle terminal application (step A1). At this time, the user ID and password input to the in-vehicle terminal 10 by the employee and the individual identification information uniquely assigned to the in-vehicle terminal 10 are transmitted to the accounting management server 30 together.

  Next, the accounting management server 30 acquires the user ID, password, and individual identification information transmitted from the in-vehicle terminal 10 and authenticates the in-vehicle terminal 10 (step A2).

  When the authentication of the in-vehicle terminal 10 is completed, the charging management server 30 transmits the user ID and the individual identification information to the PC terminal 20 (step A3), and the PC terminal 20 receives the user ID and the information received from the charging management server 30. Individual identification information is registered (step A4).

  When the registration to the PC terminal 20 is normally performed, the billing management server 30 transmits the in-vehicle terminal application to the in-vehicle terminal 10 (step 5).

  When the in-vehicle terminal application is downloaded to the in-vehicle terminal 10, the downloaded in-vehicle terminal application is executed by an application execution unit (not shown), whereby route data registration unit 112, travel history data registration unit 113, fueling A history data registration unit 114, a fuel cost calculation unit 115, and a charge distribution unit 116 are realized.

In the user database 122, a user ID, individual identification information, and an ON / OFF refueling flag indicating that refueling is possible are registered (step A6).
[When refueling]
Next, the operation during refueling will be described with reference to FIG.

  As shown in FIG. 4, the employee goes to a gas station where the company to which the employee belongs is affiliated. In the in-vehicle terminal 10, if the refueling availability flag is ON, the refueling history data registration unit 114 starts communication with the refueling machine 40 and designates the fuel type, the refueling amount, and the like to the refueling machine 40. Then, a refueling request is made (step B1).

  Next, the refueling machine 40 supplies the vehicle with fuel for the amount of fuel requested from the in-vehicle terminal 10 (step B2). When refueling is completed, the refueling machine 40 transmits the refueling amount and the fuel unit price to the in-vehicle terminal 10 (step B3).

Next, in the in-vehicle terminal 10, the refueling history data registration unit 114 registers the refueling amount and the fuel unit price received from the refueling machine 40 in the refueling history database 123 as refueling history data in association with the refueling history ID. (Step B4).
[During driving]
Next, the operation during traveling will be described with reference to FIG.

  As shown in FIG. 5, the employee first inputs the address of the departure point and the destination point to the PC terminal 20 (step C1). Then, the PC terminal 20 searches for a route (for example, the route with the shortest distance) from the departure point to the destination point, and displays the search result (if there are a plurality of routes, a plurality of routes are displayed) (step C2). ).

  Next, the employee looks at the search result displayed on the PC terminal 20, determines the route to be used, inputs the route to the PC terminal 20 (step C3), determines the scheduled number of times to use the route, and the PC. Input to the terminal 20 (step C4). For example, “20” is input as the scheduled number of times of use when the route is used for commuting and the working days are 20 days.

  Next, in response to an instruction from the employee (for example, pressing a transfer button), the PC terminal 20 transfers the route data of the route, the expiration date, and the scheduled number of use together with the route ID to the in-vehicle terminal 10 ( Step C5). For example, the expiration date of the route is set to a unit (one month) in which transportation expenses are settled.

  Next, in the in-vehicle terminal 10, the route data registration unit 112 registers the route data received from the PC terminal 20, the expiration date, and the scheduled number of times of use in the route database 124 in association with the route ID (step). C6).

  Before starting the travel by the vehicle, the employee sets one of the route data registered in the route database 124 as the planned route data to the in-vehicle terminal 10 and then starts the travel (step C7).

  When the vehicle travel is completed (step C8), in the in-vehicle terminal 10, the travel history data registration unit 113 associates the travel history ID with the route ID of the planned route data set by the employee in association with the travel history database 121. 6, as shown in FIG. 6, the travel history database 121 includes travel distance (planned), travel distance (actual), fuel consumption (actual), fuel consumption (actual), and route determination flag as travel history data. (Step C9). In FIG. 6, the fuel cost (planned) and fuel cost (actual) calculated by the fuel cost calculation unit 115 are registered.

  Here, “travel distance (planned)” is the travel distance planned when traveling according to the planned route data, “travel distance (actual)” is the travel distance actually traveled, “fuel consumption (actual) ) "Is the actual fuel consumed during travel," Fuel consumption (actual) "is the distance traveled (actual) divided by fuel consumption (actual), and" Route determination flag " It is a flag indicating whether or not the vehicle has traveled on the street.

For example, the determination of whether or not the vehicle has traveled according to the scheduled route data by the travel history data registration unit 113 can be performed by an arbitrary method using a normal car navigation function. Specifically, it is possible to track the travel route of the vehicle based on the latitude and longitude of the vehicle position, and to determine that the vehicle has deviated from the planned route when the vehicle leaves a predetermined distance from the planned route. It is possible, but not limited to this.
[When calculating and transferring fuel costs]
Next, the operation during fuel cost calculation / transfer will be described with reference to FIG.

  As shown in FIG. 7, first, in the in-vehicle terminal 10, the fuel cost calculation unit 115 requests the PC terminal 20 to transfer fuel cost information (step D <b> 1). At this time, the user ID input to the in-vehicle terminal 10 by the user and the individual identification information uniquely assigned to the in-vehicle terminal 10 are transmitted to the billing management server 30 together.

  Next, the PC terminal 20 collates the user ID and individual identification information transmitted from the in-vehicle terminal 10 with the user ID and individual identification information registered in the billing management server 30, whereby the in-vehicle terminal 10 Is authenticated (step D2).

  When the authentication is successful, the PC terminal 20 notifies the in-vehicle terminal 10 that the authentication is completed (step D3), and gives permission for the fuel cost calculation process. On the other hand, when the authentication fails, the PC terminal 20 transmits an error screen to the in-vehicle terminal 10 and ends the process.

  In the in-vehicle terminal 10, when the fuel cost calculation process is permitted from the PC terminal 20, the fuel cost calculation unit 115 acquires all the route IDs registered in the travel history database 121, and further acquires the acquired route ID. Among them, all the travel history data linked to the route IDs within the range of the expiration date registered in the route database 124 are acquired (step D4).

  The fuel cost calculation means 115 calculates the fuel cost (planned) and the fuel cost (actual) based on the travel history data (travel distance, fuel consumption, fuel consumption) and the refueling history data (fuel unit price) (step) D5) The calculated fuel cost (scheduled) and fuel cost (actual result) are linked to the travel history ID, and are further registered in the travel history database 121 as travel history data.

  Here, “fuel cost (scheduled)” is obtained by dividing the travel distance (scheduled) by the fuel consumption (actual) to obtain the fuel consumption (scheduled), and the fuel consumption (scheduled) is calculated as a fuel unit price (for example, fuel cost). “Fuel cost (actual)” is obtained by multiplying the fuel consumption (actual) by the refueling unit price.

  After the fuel cost is calculated by the fuel cost calculation unit 115, the route data registration unit 112 subtracts 1 from the number of scheduled uses associated with the route ID in the route database 124 (if the scheduled number of uses is 0, the vehicle cannot be used because it cannot be used) Return the error screen and error message to 10).

  The series of operations described above are performed for all travel history data associated with the route IDs within the validity period (steps D4 to D6).

  Next, the charging distribution means 116 determines that the employee has used the travel history data for which the route determination flag is ON, and the company uses the fuel cost (actual result) of the travel history data as the transportation cost. Is transferred to the PC terminal 20 as a non-chargeable fuel cost, and on the other hand, it is determined that the travel history data for which the route determination flag is not ON is used by the employee for private use, and the fuel cost of the travel history data is (Schedule) is transferred to the PC terminal 20 as the fuel cost to be charged for the employee (step D7).

  However, if the route determination flag is not ON, that is, if the route deviates from the planned route, the fuel cost is paid to the employee until the reason is force majeure and cannot be taken by the employee. It is considered to be harsh. In order to make the employee determine whether or not to apply for an exception for the fuel cost in such a case, as shown in FIG. 9, it is possible to provide an application target column on the display screen of the travel history data.

  In FIG. 9, the travel histories that deviate from the planned route are “A2 to A3” and “A4 to A5”.

  Among these, “A2 to A3” are cases where a customer visits a convenience store to purchase breakfast or the like before work. In this case, it is considered as private use and should not be borne by the company, so the application field is not checked at the discretion of the employee. Therefore, the fuel cost (scheduled) that was initially expected is transferred to the PC terminal 20 as the fuel cost to be charged.

  On the other hand, “A4 to A5” is a case where the planned route is unavoidably detoured due to construction regulations or the like. In this case, since it is force majeure and it is harsh to burden the employee, the application subject column is checked at the employee's discretion. For this reason, the fuel cost (actual result) is transferred to the PC terminal 20 as a fuel cost that is not charged.

  In the case of an exception application, if an application reason is necessary, a column for describing the reason for the application can be further provided.

  When the PC terminal 20 receives a request for transfer of fuel cost information from the charge management server 30 (step D8), the PC terminal 20 sends fuel charge information for each employee (total fuel cost not subject to charge and charge target information). Transfer the total fuel cost) (step D9).

When the transfer of the fuel cost information is normally completed, the charging management server 30 notifies the PC terminal 20 of the completion of the transfer (Step D10). In addition, it is desirable for the company side to check for any contradiction from the number of implementations, actual working days, customer visit history, etc. after the transfer is completed.
[At checkout]
The company will allow the employee to pay the fueling station by the due date for the fuel cost subject to charge that the employee uses for private use. On the other hand, non-chargeable fuel costs that employees use for business and should be borne by the company as transportation expenses are credited to the gas station from the company.

(Second Embodiment)
This embodiment is different from the first embodiment in that the fuel cost calculation process is not performed by the in-vehicle terminal 10 but by the PC terminal 20.

  The configuration of the present embodiment is basically the same as the configuration of the first embodiment, but in comparison with the first embodiment, in FIG. 2, the fuel cost calculation means 115 is necessary for calculating the fuel cost. The difference is that only the function of transferring data to the PC terminal 20 is provided, and the expiration date 124b and the scheduled usage count 24c of the route database 124 do not exist and are registered in the PC terminal 20.

Since the operation of this embodiment is similar to that of the first embodiment, different points will be described below.
[When calculating and transferring fuel costs]
As shown in FIG. 10, in the present embodiment, when the PC terminal 20 completes the authentication of the in-vehicle terminal 10 through steps D1 to D3 as in the first embodiment, the in-vehicle terminal 10 then stores The travel history data and the refueling history data registered in the unit 12 are transferred to the PC terminal 20 (step E1), and the fuel cost calculation process is performed by the PC terminal 20 (steps E2 to E4). The subsequent steps D8 to D9 are the same as in the first embodiment.

  In the present embodiment, as in the first embodiment, when an exception application is required, a screen as shown in FIG. 9 is displayed on the PC terminal 20, so that the employee can display the screen. Check if necessary in the application target field. In addition, in the case of an exception application, if an application reason is necessary, it is possible to further provide a column for describing the reason for the application.

(Third embodiment)
This embodiment is different from the first embodiment in that the billing management server 30 provides an in-vehicle terminal application using an ASP (Application Service Provider) method.

  In the first embodiment, the PC terminal 20 and the charge management server 30 are connected by a LAN provided by a communication carrier. In this embodiment, the charge information server 30 and the PC terminal 20 are connected by a WAN. It is connected.

  The operation of this embodiment is the same as that of the first or second embodiment.

(Fourth embodiment)
This embodiment is different from the first embodiment in that the in-vehicle terminal 10 has the function of the PC terminal 20.

  In the first embodiment, the in-vehicle terminal 10 and the PC terminal 20 are provided independently of each other. However, in the present embodiment, the in-vehicle terminal 10 has functions such as a route search function provided in the PC terminal 20. This is different from the point that processing such as authentication and fuel information transfer is directly performed between the in-vehicle terminal 10 and the charge management server 30.

  The operation of this embodiment is the same as that of the first or second embodiment.

It is a figure which shows the structure of the charge distribution system of the 1st Embodiment of this invention. It is a block diagram which shows the structure of the vehicle-mounted terminal which concerns on the 1st Embodiment of this invention. It is a flowchart explaining the operation | movement at the time of the download of the application for vehicle-mounted terminals in the accounting distribution system of the 1st Embodiment of this invention. It is a flowchart explaining the operation | movement at the time of refueling in the charge distribution system of the 1st Embodiment of this invention. It is a flowchart explaining the operation | movement at the time of driving | running | working in the charge distribution system of the 1st Embodiment of this invention. It is a figure explaining the example of the travel history data (before fuel cost calculation) which concerns on the 1st Embodiment of this invention. It is a flowchart explaining the operation | movement at the time of fuel cost calculation and transfer in the charge distribution system of the 1st Embodiment of this invention. It is a figure explaining the example of the travel history data (after fuel cost calculation) which concerns on the 1st Embodiment of this invention. It is a figure explaining the example of the screen which provided the application object column in the travel history data which concerns on the 1st Embodiment of this invention. It is a flowchart explaining the operation | movement at the time of the fuel cost calculation and transfer in the charge distribution system of the 2nd Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 In-vehicle terminal 11 Control means 111 Communication control means 112 Route data registration means 113 Travel history data registration means 114 Fuel supply history data registration means 115 Fuel cost calculation means 116 Charge distribution means 12 Storage means 121 Travel history database 122 User database 123 Oil supply history Database 124 Route database 13 Communication means 14 Wireless communication means 15 Application acquisition means 20 PC terminal 30 Charge management server 40 Refueling machine

Claims (4)

A charging distribution system that distributes the fuel cost of a vehicle to either a fuel cost subject to billing or a fuel cost not subject to billing,
Route data registration means for registering the planned route data of the vehicle in advance;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data Data registration means;
Refueling history data registration means for registering the fuel unit price of the refueled fuel as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Means,
The actual fuel costs of the travel history data the flag is ON, the have a, a charging distributing means distributes the fuel costs outside the billable,
The travel history data registration means further registers, as the travel history data, the planned travel distance of the planned route data and the fuel consumption during travel for each travel history,
The fuel cost calculation means calculates a planned fuel cost using the planned travel distance and fuel consumption of the travel history data and the fuel unit price of the refueling history data for each travel history, and uses the calculated planned fuel cost for the travel history. Further register as historical data,
The charging distribution unit is a charging distribution system that distributes a scheduled fuel cost of travel history data in which the flag is not ON to a fuel cost to be charged. It further has billing management means for providing an application in the ASP system,
The route data registration means, the travel history data registration means, the oil supply history data registration means, said fuel cost calculation unit, and the charging distribution means is realized by execution of the application, according to claim 1 billing sorting system according to. An in-vehicle terminal that distributes the fuel cost of a vehicle to either a fuel cost subject to billing or a fuel cost not subject to billing,
Route data registration means for registering the planned route data of the vehicle in advance;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data Data registration means;
Refueling history data registration means for registering the fuel unit price of the refueled fuel as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Means,
The actual fuel costs of the travel history data the flag is ON, the have a, a charging distributing means distributes the fuel costs outside the billable,
The travel history data registration means further registers, as the travel history data, the planned travel distance of the planned route data and the fuel consumption during travel for each travel history,
The fuel cost calculation means calculates a planned fuel cost using the planned travel distance and fuel consumption of the travel history data and the fuel unit price of the refueling history data for each travel history, and uses the calculated planned fuel cost for the travel history. Further register as historical data,
The charging distribution means is an in- vehicle terminal that distributes a scheduled fuel cost of travel history data whose flag is not ON to a fuel cost to be charged . A charging distribution method performed by an in-vehicle terminal that distributes the fuel cost of a vehicle to either a fuel cost subject to charging or a fuel cost not subject to charging,
A route data registration step for pre-registering the planned route data of the vehicle;
A travel history for registering, as travel history data, a flag that is ON when the vehicle travels according to the planned route data and a fuel consumption amount during travel for each travel history that the vehicle has traveled after setting the planned route data A data registration step;
A refueling history data registration step of registering a fuel unit price of fuel supplied as refueling history data for each refueling history refueled by the vehicle;
For each of the travel histories, the actual fuel cost is calculated using the fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the fuel cost calculation for further registering the calculated actual fuel cost as the travel history data Steps,
The actual fuel costs of the travel history data the flag is ON, the have a, a charging distribution step of distributing the fuel costs outside the billable,
In the travel history data registration step, for each travel history, the planned travel distance of the planned route data and the fuel consumption during travel are further registered as the travel history data,
In the fuel cost calculation step, for each travel history, the planned fuel cost is calculated using the planned travel distance and fuel consumption of the travel history data and the fuel unit price of the refueling history data, and the calculated planned fuel cost is used as the travel cost. Further register as historical data,
In the charging distribution step, a charging distribution method for distributing the scheduled fuel cost of the travel history data in which the flag is not ON to the fuel cost to be charged.

Images