JP7810571B2 - Fee calculation device and fee calculation system - Google Patents

Description

The present invention relates to a fare calculation device and fare calculation system that can be used when reserving or riding a taxi.

In the case of taxis, attempts are being made to use a server installed outside the vehicle to perform processing such as fare calculation.
For example, Patent Document 1 discloses a taxi meter system for reducing or eliminating the burden on taxi drivers. Specifically, a taxi meter onboard unit installed in an unmanned taxi vehicle is constantly connected to an external server via wireless communication while the vehicle is in operation. The taxi meter onboard unit detects passenger status, such as boarding and disembarking, and transmits information such as the passenger's designated destination and current location to the external server. The external server automatically switches the taxi meter status between vacant, occupied, and paid, calculates fares, and determines fares. The taxi meter onboard unit displays fares, determines fares, and settles fares according to instructions from the external server. The external server detects and automatically handles abnormalities in each vehicle. Furthermore, it efficiently dispatches vacant vehicles by predicting passenger demand at each location. Furthermore, it provides appropriate commercial facility information according to passengers.

Patent Document 2 also discloses a taxi meter system that reduces or eliminates the burden on taxi drivers when a taxi arrives at its destination. Specifically, when the taxi arrives at its destination, the system notifies the passenger of its arrival using voice or other means. When the taxi arrives at its destination, the system determines the fare amount and notifies the passenger of this amount via a smartphone or other device. The fare is paid electronically using a credit card or other means through communication between the passenger's smartphone or other device and the in-vehicle payment terminal. When the system recognizes that the payment has been successfully completed, it issues a receipt and unlocks the vehicle doors, allowing the passenger to disembark. The in-vehicle taxi meter unit is connected to an external server via wireless communication, and the external server calculates the route to the destination and the fare based on distance and time.

Japanese Patent Application Laid-Open No. 2018-128842 Japanese Patent Application Laid-Open No. 2019-20984

While the number of taxi vehicles and drivers owned by taxi companies and other organizations does not change much, the number of people using taxis fluctuates depending on the location, season, time of day, etc. In other words, in the taxi industry, the balance between supply and demand for taxis changes significantly depending on the situation, and there are busy and quiet times.

On the other hand, taxi fares are generally fixed regardless of whether the route is busy or quiet. In other words, passengers are presented with a fare system determined in advance by each taxi company, and a fare that is determined based on factors such as distance traveled and travel time.

For example, the Ministry of Land, Infrastructure, Transport and Tourism is currently experimenting with applying dynamic pricing to taxi fares in order to improve taxi convenience. However, the practical application of dynamic pricing remains a challenge for the future.

For example, in busy areas, the number of available taxis does not increase despite the large number of passengers wanting to ride in a taxi. As a result, passengers often find it difficult to board a taxi.

Furthermore, even if a taxi driver is operating in a quiet area and obtains information indicating that another specific area is busy, if the distance to that specific area is long or the driver is unfamiliar with the roads in that area, the extra effort required will not increase the driver's motivation, and they will be unlikely to actively travel to that specific area to operate. Therefore, it is difficult to increase the number of taxis operating in busy areas.

On the other hand, in quiet areas, the number of people actually using taxis is low compared to the number of available taxis, so each taxi has to wait for a long time empty until a customer shows up, making it difficult to increase operating revenue.

Furthermore, even in quiet areas, it is believed that there are potential taxi users. For example, if taxi fares could be offered at lower rates than current fares, potential taxi users would actually use taxis, which would increase taxi demand. However, since actual taxi fares remain constant, it is not possible to stimulate taxi demand by potential taxi users.

On the other hand, when applying dynamic pricing to taxi fares and trying to make fares variable, it is difficult to determine an appropriate fare. For example, if a surcharge that is too high is applied in a busy area, the number of taxi users may drop sharply. Furthermore, if a discount fare that is too low is applied in an unpopulated area, the number of taxi users may increase, but the operating revenue per taxi vehicle may not increase.

In particular, if premium and discount fares are not appropriately determined based on the actual level of busyness or off-peak traffic, the disadvantages of dynamic pricing may outweigh the benefits. However, it is difficult for each taxi operator to accurately grasp the actual level of busyness or off-peak traffic and determine appropriate fares.

The present invention was made in consideration of the above-mentioned circumstances, and its purpose is to provide a fare calculation device and fare calculation system that makes it easy to determine appropriate surcharge and discount fares in accordance with fluctuations in taxi supply and demand.

The above-mentioned object of the present invention is achieved by the following configuration.

a correction data storage unit that performs statistical processing of supply and demand trends using at least previously accumulated past vehicle business record data, and generates and stores fare correction data that represent busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period based on the results of the statistical processing;
a correction data acquisition unit that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by a user at least when accepting a taxi reservation from the user;
a fare presentation unit that, when accepting at least a taxi reservation from a user, presents to the user a fare calculated based on an estimated taxi vehicle travel distance calculated based on a boarding location and a drop-off location designated by the user, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation device comprising:

Taxi vehicles and
a server that manages the taxi vehicles;
The server
a correction data storage unit that performs statistical processing of supply and demand trends using at least previously accumulated past vehicle business record data, and generates and stores fare correction data that represent busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period based on the results of the statistical processing;
a correction data acquisition unit that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by the user terminal when accepting a reservation for the taxi vehicle from at least the user terminal of the taxi user;
a fare presentation unit that, when accepting a reservation for the taxi vehicle from at least the user terminal, presents to the user a fare calculated based on an estimated travel distance of the taxi vehicle calculated based on a boarding location and a drop-off location designated from the user terminal, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation system comprising:

The fare calculation device and fare calculation system of the present invention make it easy to determine appropriate surcharge and discount fares in line with fluctuations in taxi supply and demand. In other words, supply and demand trends obtained through statistical processing of previously accumulated past vehicle sales record data are stored as fare adjustment data indicating busy or quiet conditions, making it possible to grasp busy or quiet areas and time periods and appropriately reflect this in fares.

The present invention has been briefly described above. Furthermore, details of the present invention will become clearer by reading the detailed description of the invention (hereinafter referred to as "embodiments") described below with reference to the accompanying drawings.

FIG. 1 is a block diagram showing the configuration of a fee calculation system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the main functional components of the server. FIG. 3 is a block diagram showing the main functional components of the soft meter. FIG. 4 is a flowchart showing the details of the operation for statistically processing the business performance in terms of busyness. FIG. 5 is a flowchart showing the operation when the server calculates a pre-determined fee. FIG. 6 is a sequence diagram showing an example of the operation of the entire system.

Specific embodiments of the present invention are described below with reference to the accompanying drawings.

Figure 1 is a block diagram showing the configuration of a fee calculation system 100 according to an embodiment of the present invention.

The fare calculation system 100 shown in Figure 1 comprises a soft meter 10 mounted on a taxi vehicle 25 and a server 31 installed in a data center or the like. Of course, it is also possible to use a general taxi meter instead of the soft meter 10.

In addition, each taxi user 40A, 40B using the taxi vehicle 25 can communicate with the server 31 using a user terminal 41, 42, for example, when making a reservation. The user terminals 41, 42 can be, for example, a mobile terminal such as a typical smartphone, or a personal computer (PC).

Soft meter 10 is a device that can perform the same functions as a general taximeter installed in a taxi vehicle. However, while taximeters are specified measuring instruments that are subject to the Measurement Act, soft meter 10 does not currently qualify as specified measuring instruments.

Specifically, a taximeter measures distance by integrating the circumference of a rotating part, such as a wheel, to determine the actual distance. On the other hand, the soft meter 10 calculates distance based on vehicle position information determined using a global navigation satellite system (GNSS) such as GPS, and determines the taxi fare based on that distance.

The soft meter 10 in Figure 1 includes a control unit (CPU) 11, an interface (I/F) 12, a fee system information storage unit 13, an interface 14, an operation button unit 15, an inertial measurement unit (IMU) 16, a memory unit 17, a touch panel 18, a display 19, and an interface 20.

In addition, the GPS receiver 21 is connected to the control unit 11 via interface 12, the ETC vehicle unit 22 is connected to the control unit 11 via interface 14, the external device input device 24 is connected to the control unit 11 via interface 20, and the LTE communication module 23 is connected to the control unit 11.

The control unit 11 is composed of electronic circuits, primarily a microcomputer, and executes pre-prepared programs to perform control to realize the functions required for the soft meter 10.

The GPS receiver 21 receives radio signals from multiple (three or more) GPS satellites and can calculate the latitude and longitude representing the current location based on the time of the received signals, i.e., perform positioning. Therefore, under normal conditions where radio waves can be received simultaneously from a predetermined number of satellites or more, the GPS receiver 21 can correctly determine the current location.

Location information detected by the GPS receiver 21 periodically (e.g., every second) is input to the control unit 11 via the interface 12. Information indicating whether the GPS receiver 21 is currently measuring position is also input to the control unit 11 along with the location information.

The fare system information storage unit 13 is composed of read-only memory (ROM) or the like, and stores data on pre-determined fare systems. For example, data such as the pre-determined basic fare amount, unit distance traveled, additional fare per unit distance traveled, length of unit time, and additional fare per unit time is stored in the fare system information storage unit 13.

The ETC vehicle-mounted unit 22 performs road-to-vehicle wireless communication, for example, with roadside equipment (not shown) on expressways or toll roads. Through this wireless communication, the ETC vehicle-mounted unit 22 exchanges information necessary for toll settlement (taxi vehicle model information, ETC card number, entrance toll gate, exit toll gate, toll fee, etc.) with the roadside equipment.

The operation button unit 15 is located on the front of the soft meter 10 and includes buttons such as "Vacant," "Accumulated," and "Payment" that can be operated by the driver of the taxi vehicle 25. The control unit 11 reads the state of each button on the operation button unit 15 and can grasp the states and changes of "Vacant," "Accumulated," and "Payment" in the same way as with a typical taxi meter.

The inertial measurement unit 16 is an electronic device that incorporates a gyro sensor that detects acceleration in three axes and a sensor that detects rotational angular acceleration in three axes. The control unit 11 can calculate the momentum of the vehicle using the results measured by the inertial measurement unit 16. Therefore, for example, when the GPS receiver 21 is unable to determine its position, it is possible to obtain an estimate of the vehicle's current position from the measurement results of the inertial measurement unit 16.

Memory unit 17 has built-in RAM (random access memory) and ROM. The RAM in memory unit 17 is used by control unit 11 to temporarily store various data. The ROM in memory unit 17 holds pre-prepared programs, constant data, pre-prepared tables, etc. that can be used by control unit 11.

The touch panel 18 can be used by the control unit 11 to read the touch of a user (driver or passenger) on a touch button displayed on the screen of the display device 19 .
The display 19 is configured, for example, by a liquid crystal display (LCD) and can display information such as the taxi status (e.g., "vacant,""occupied," and "payment"), the fare, and numbers and characters required for input operations in a manner visible to the driver and passengers. The display 19 is disposed on the front of the soft meter 10.

The LTE communication module 23 is a device that allows the control unit 11 of the soft meter 10 to connect to the server 31 via the LTE network 33 and perform data communication.
The external device input device 24 is an external terminal having, for example, a camera, a numeric keypad, a magnetic card reader, an IC card reader, etc. This external terminal is used, for example, to read QR codes (registered trademark) and to settle rental fees using credit cards, electronic money cards, etc.

Meanwhile, the server 31 is connected to the LTE network 33 via the Internet 32. The soft meter 10 installed in the taxi vehicle 25 and each user terminal 41, 42 can connect to the server 31 via wireless communication using the LTE communication module 23.

The server 31 shown in Figure 1 has a distinctive function for implementing dynamic pricing. Specifically, when calculating fares for taxi vehicles 25, it has the function of applying surcharges or discounts according to the busyness of different areas and time periods.

For example, when a taxi user 40A reserves a taxi vehicle 25, the server 31 can present the user with a pre-determined fare. When calculating this pre-determined fare, dynamic pricing can be applied, taking into account the area of boarding and disembarking locations and the time of day the ride will take place.

In reality, server 31 accumulates and stores a database (DBA) of business records, which are past performance data. Therefore, by statistically processing past performance data, it is possible to build a processed database DBB of busy times stratified by boarding and disembarking areas and boarding times. Server 31 can reflect the busy times in the processed database DBB in pre-determined fares, etc.

FIG. 2 is a block diagram showing the main functional components of the server 31.
The server 31 shown in FIG. 2 has a business record database DB1, a busyness level database DB2, a correction coefficient database DB3, and a taxi reservation database DB4.

The business record database DB1 in Figure 2 corresponds to the business record DBA in Figure 1. Each taxi vehicle 25 equipped with a soft meter 10 or a communication-enabled taxi meter transmits business performance data to the server 31 each time it conducts business or on a business day basis. The server 31 collects the business performance data from each taxi vehicle 25 and stores it in the business record database DB1 (S11).

The sales performance data accumulated in the sales record database DB1 includes information such as the latitude/longitude of boarding and disembarking points for each business trip, the date, day of the week, time (hours, minutes, seconds), distance traveled, and fare.

Server 31 performs statistical processing (S12) using past data stored in business record database DB1, for example, in periodic daily, weekly, or monthly processing, to generate busyness data stratified by area and time period. Details of this processing will be explained later. This busyness data is stored and managed in busyness database DB2. Specifically, data representing the degree of busyness of each time period (e.g., XX hour to XX hour on XX day) in each area (e.g., within XX km of XX station) is stored in busyness database DB2. This busyness database DB2 corresponds to the processed database DBB in Figure 1.

The server 31 also assigns a fee correction coefficient corresponding to the busyness level to each of the busyness level data stratified by area and time period (S13). This fee correction coefficient is registered and stored in the correction coefficient database DB3. Therefore, each area and time period item in the busyness level database DB2 is linked to each fee correction coefficient in the correction coefficient database DB3. Note that the data in the correction coefficient database DB3 may also be included in the busyness level database DB2.

The server 31 also has a reservation function (S15) for accepting taxi reservations from each taxi user 40A, 40B. Specifically, in response to access to the server 31 from each user terminal 41, 42 that has pre-installed specified application software (app), the server 31 can issue coupon tickets or taxi tickets for using a taxi.

For example, when a user specifies the boarding and disembarking locations, travel time, etc., server 31 presents the user with a pre-determined fare and issues the corresponding coupon ticket or taxi ticket. Coupon tickets and taxi tickets issued by server 31 are managed by individually assigned numbers, and each is assigned a different QR code, for example. The user can obtain the QR code for the coupon ticket or taxi ticket using user terminals 41 and 42.

Information about coupon tickets and taxi tickets issued by the server 31 is registered and managed in the taxi reservation database DB4. When a user boards a taxi vehicle 25 and presents the QR code of the coupon ticket or taxi ticket on the user terminal 41, the external equipment input device 24 connected to the soft meter 10 reads the QR code. The soft meter 10 queries the server 31 for the coupon ticket or taxi ticket with the read QR code. The server 31 can refer to the reservation information registered in the taxi reservation database DB4 and authenticate the coupon ticket or taxi ticket (S16).

Figure 3 is a block diagram showing the main functional components of the soft meter 10.

In the example shown in Figure 3, the soft meter 10 includes a boarding and alighting point information acquisition unit 51, a time zone identification unit 52, a correction coefficient acquisition unit 53, a communication unit 54, a pre-determined fare calculation unit 55, a fare presentation unit 56, and a reservation code authentication unit 57.

The boarding and alighting point information acquisition unit 51 acquires the latitude/longitude of the most recent vehicle position acquired from the GPS receiver 21 as the location of the boarding point, for example, when the driver of the taxi vehicle 25 operates the "Actual Vehicle" button. Also, for example, when the driver of the taxi vehicle 25 operates the "Pay" button, it acquires the latitude/longitude of the most recent vehicle position acquired from the GPS receiver 21 as the location of the disembarking point. Alternatively, for example, it acquires the location of the destination on a map specified by the passenger as the location of the disembarking point.

The time zone determination unit 52 determines the time zone based on time information such as the latest current time, date, and day of the week acquired from the GPS receiver 21, for example.
The correction coefficient acquisition unit 53 acquires a correction coefficient for the fare according to the degree of busyness, based on the information on the boarding and alighting points acquired by the boarding and alighting point information acquisition unit 51 and the information on the time period acquired by the time period specification unit 52. Specifically, the correction coefficient acquisition unit 53 transmits the information on the boarding and alighting points and the time period to the server 31 via the communication unit 54, and acquires the correction coefficient from the server 31.

The pre-determined fare calculation unit 55 calculates the pre-determined fare based on the fare system information stored in the fare system information storage unit 13, the distance between boarding and disembarking points calculated on a road map, and the correction coefficient acquired by the correction coefficient acquisition unit 53. Alternatively, the unit 55 continuously measures the distance traveled from the boarding point based on changes in location information detected at regular intervals, and calculates the regular taxi fare in real time based on that distance, the fare system information stored in the fare system information storage unit 13, and the correction coefficient acquired by the correction coefficient acquisition unit 53.

The fare presentation unit 56 displays the pre-determined fare calculated by the pre-determined fare calculation unit 55, the regular taxi fare, or the pre-determined fare determined when the user made a reservation in advance on the display 19 so that the user and the driver can see it.

The reservation code authentication unit 57 reads the reservation code (e.g., a QR code) on the taxi coupon or taxi ticket presented by the user using the external device input device 24 and authenticates whether it is a valid reservation code that can be used. In practice, the reservation code authentication unit 57 communicates with the server 31 via the communication unit 54 and queries the server 31 to determine whether the reservation code matches a pre-registered reservation code. Furthermore, if a pre-determined fare determined at the time of reservation is registered on the server 31, the reservation code authentication unit 57 obtains information about that pre-determined fare from the server 31.

Figure 4 is a flowchart showing the details of the operation of statistically processing sales results in terms of busyness. That is, Figure 4 shows a specific example of process S12 in Figure 2 by server 31. The operation in Figure 4 is explained below.

In S21, the server 31 acquires data for a certain period from the past business records stored in the business record database DB1. For example, it extracts and acquires business records for the past one or two months from that point in time.

The server 31 classifies all the data within the range acquired in S21 by day of the week and by time period (S22).
In S23, the server 31 extracts areas with many records of "start of actual vehicle" for each day of the week and time period based on the data classified in S22. For example, the area of each business record is specified as a circular range with a certain radius (e.g., 1 km, 2 km) from a characteristic point with a lot of pedestrian traffic, such as a railway station.

The server 31 calculates the average number of actual vehicle starts for each area based on the business records of the areas extracted in S23 (S24).
The server 31 calculates the average number of empty taxis for each area based on the business records for the areas extracted in S23 (S25). Note that the number of taxis in operation by taxi operators operating in the area may be used in S25 instead of the average number of empty taxis.

The server 31 calculates the vehicle occupancy rate for each time period in S26.
Vehicle availability rate = number of vehicles / (number of vehicles + number of empty vehicles)
The server 31 compares the vehicle occupancy rate calculated in S26 with a threshold value (e.g., 90%) in S27 to identify the busy status for each time period for each area. Note that the threshold value used for comparison in S27 can be changed as needed.

The server 31 recognizes time periods and areas where the occupancy rate is equal to or greater than the threshold as "busy" situations (S28). Furthermore, it recognizes time periods and areas that do not fall under the "busy" situation as "quiet" situations (S29).

The server 31 registers the results recognized in S28 and S29 in FIG. 4 in the busyness database DB2 shown in FIG. 2. In other words, data representing the busyness by area and time period is registered in the busyness database DB2.

Furthermore, fee correction coefficients corresponding to the busyness levels by area and time period registered in the busyness level database DB2 are assigned by area and time period in S13 of Figure 2 and registered in the correction coefficient database DB3.

Figure 5 is a flowchart showing the operation of the server 31 when calculating a pre-determined fee. That is, Figure 5 shows a specific example of the operation of process S14 shown in Figure 2 by the server 31. The operation of Figure 5 is described below.

For example, when taxi user 40A makes a reservation, he or she specifies the boarding location and boarding time of the taxi to be reserved, and this information is input to server 31. Server 31 then reads the input boarding location and boarding time in S31 and proceeds to the next process in S32.

In S32, the server 31 searches the busyness database DB2 to determine whether the boarding location and boarding time specified in S31 fall within a busy time period or area, or to identify the degree of busyness in that time period or area.

If the specified boarding location and boarding time fall within a busy time period or area, server 31 reads the fare correction coefficient for the surcharge assigned to that time period and area from the correction coefficient database DB3 and sets it as a parameter for calculating the current fare (S33).

Furthermore, when applying a fare correction coefficient for a surcharge, the server 31 notifies the user that the area and time period for which the fare is currently being calculated are "busy area and time period" (S34). For example, the server 31 controls the app running on the user terminal 41 to display a message indicating "busy area and time period" on the screen, or to announce this through an audio output message. Alternatively, the server 31 or the soft meter 10 controls the passenger in the taxi vehicle 25 to display a message indicating that the soft meter 10 is in a "busy area and time period," or to announce this through an audio output message.

On the other hand, if the specified boarding location and boarding time fall within a time period and area that is not busy (off-peak), the server 31 reads the fare correction coefficient for the discounted fare assigned to that time period and area from the correction coefficient database DB3 and sets it as a parameter for calculating the current fare (S35).

Furthermore, when applying a fare correction coefficient for a discounted fare, the server 31 notifies the user that the area and time period for which the fare is currently being calculated are "off-peak area and time period" (S36). For example, the server 31 controls the app running on the user terminal 41 to display a message indicating "off-peak area and time period" on its screen, or to announce this through an audio output message. Alternatively, the server 31 or the soft meter 10 controls the app running on the user terminal 41 to display a message indicating that the soft meter 10 is in an "off-peak area and time period" to passengers aboard the taxi vehicle 25, or to announce this through an audio output message.

For example, when taxi user 40A makes a reservation, he or she specifies the drop-off location of the reserved taxi, i.e., the destination, and this information is input to server 31. Server 31 then reads the input drop-off location in S37 and proceeds to the next process in S38.

In S38, the server 31 calculates the distance between the boarding location specified in S31 and the disembarking location specified in S37. For example, it searches a road map database for a planned route for traveling on roads from the boarding location to the disembarking location, and calculates the distance traveled on the planned route.

The server 31 calculates a predetermined fare based on the predetermined taxi fare system and the planned distance traveled calculated in S38, and calculates the final fare in S39 by taking into account the fare correction coefficient set in S33 or S35. Of course, the fare reflects not only the distance traveled but also the length of time required.

The server 31 presents the fare calculated in S39 to the user in S40. For example, when a taxi user 40A purchases a taxi coupon or taxi ticket by reservation, the server 31 outputs the amount of the coupon or taxi ticket calculated as a pre-determined fare to the user terminal 41 so that the taxi user 40A can check it before purchasing.

Figure 6 is a sequence diagram showing an example of the operation of the entire system. The operation shown in Figure 6 is explained below.

Users, i.e., taxi passengers 40A and 40B, use user terminals 41 and 42 to connect to server 31 via the Internet 32 and use the communication services of server 31. Specifically, they can purchase taxi coupons or taxi tickets from server 31 and make reservations for taxi rides (S51).

When a user specifies the boarding location, disembarking location, day of the week, time period, etc. when booking a taxi, the server 31 can determine the amount of the pre-determined fare by, for example, executing the process shown in Figure 5. The server 31 presents the determined pre-determined fare amount to the user (S52).

When the user confirms the amount of the pre-determined fare and carries out the procedure for purchasing the coupon ticket or taxi ticket, the server 31 accepts the reservation of the user, issues a unique reservation code for the coupon ticket or taxi ticket, and registers it in the taxi reservation database DB4 (S53).
A user who has purchased a coupon ticket or a taxi ticket receives a reservation code issued by the server 31 at a user terminal 41, 42.

On the other hand, when a user who has previously purchased a coupon ticket or taxi ticket actually boards a taxi vehicle 25, the user presents the reservation code acquired in advance on the user terminal 41 (S55). For example, if the reservation code is a QR code, an on-board device such as a soft meter 10 installed in the taxi vehicle 25 uses the camera of the external device input device 24 to capture the image displayed on the screen of the user terminal 41 and read the QR code (S56).

To confirm that the reservation code read from the user terminal 41 is a valid and usable code, the soft meter 10 connects to the server 31 using the LTE communication module 23 and performs an authentication inquiry.

The server 31 searches the taxi reservation database DB4 and performs authentication processing for the reservation code inquired about by the softmeter 10 (S58). If the authentication of the reservation code is successful, information on the coupon or taxi ticket linked to the reservation code can be obtained from the taxi reservation database DB4, and the server 31 notifies the softmeter 10 of this information.

The soft meter 10 receives the authentication result of the reservation code from the server 31 and obtains information about the coupon ticket or taxi ticket. If the soft meter 10 receives information about a pre-determined fare from the server 31, the soft meter 10 presents that amount to the user (S57).

The present invention is not limited to the above-described embodiments, and modifications, improvements, etc. are possible as appropriate. Furthermore, the material, shape, dimensions, number, placement location, etc. of each component in the above-described embodiments are arbitrary and not limited as long as they achieve the present invention.

For example, in the above-mentioned fare calculation system 100, it is assumed that when a user makes a taxi reservation in advance, the server 31 will apply a surcharge or discount to the pre-determined fare that reflects the expected busyness based on past business performance, but it is also possible to make a reservation without determining the fare at the time of reservation.

In such cases, it is possible that fare increases or discounts may be applied even if the user's boarding and disembarking locations and boarding and disembarking times have not been confirmed, and it is also anticipated that the server 31 or the like may present to the user at the time of reservation conditions such as the area, time period, and degree of increase/discount to which the fare increase or discount applies.

In this case, by installing a soft meter 10 capable of communicating with the server 31 in the taxi vehicle 25, it becomes possible to apply fare surcharges or discounts to passengers who make reservations in advance depending on the area and the busyness of the time period.

Here, the features of the fee calculation system according to the embodiment of the present invention described above will be briefly summarized and listed below in [1] to [5].
[1] A correction data storage unit (correction coefficient database DB3) that stores fare correction data representing busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period, as a result of statistical processing of supply and demand trends on at least previously accumulated past vehicle business record data (business record database DB1);
a correction data acquisition unit (S33, S35) that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by the user at least when accepting a taxi reservation from the user;
a fare presentation unit (S15, S40) that, when accepting a taxi reservation from a user, presents to the user a fare calculated (S39) based on an estimated taxi vehicle travel distance calculated based on a boarding location and an alighting location designated by the user, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation device (server 31) comprising:

The fare calculation device configured as described in [1] above can present a user reserving a taxi with a pre-determined fare that applies a surcharge or discount that reflects the expected busy or quiet conditions for each area and driving time period. Furthermore, because the surcharge or discount fare reflects expected supply and demand trends based on previously accumulated past vehicle sales record data, there is no need to constantly monitor the actual busy or quiet conditions. This makes it possible to apply appropriate dynamic pricing without increasing the processing load on the server. Furthermore, applying a surcharge during busy times can increase the motivation of taxi drivers, thereby helping to quickly alleviate busy conditions. Furthermore, applying a discount during quiet times can stimulate demand from new taxi customers, helping to quickly alleviate quiet conditions.

[2] A taxi vehicle (25);
A server (31) that manages the taxi vehicles,
The server
a correction data storage unit (correction coefficient database DB3) that stores fare correction data representing busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period, as a result of statistically processing supply and demand trends from at least previously accumulated past vehicle business record data (business record database DB1);
a correction data acquisition unit (S33, S35) that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by the user terminal when accepting a reservation for the taxi vehicle from at least the user terminal of the taxi user;
a fare presentation unit (S15, S40) that, when accepting a reservation for the taxi vehicle from at least the user terminal, presents to the user a fare calculated based on an estimated travel distance of the taxi vehicle calculated based on a boarding location and a drop-off location designated from the user terminal, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation system (100) comprising:

The fare calculation system configured as described in [2] above makes it possible to present users reserving a taxi with a pre-determined fare that reflects the expected busy or quiet conditions for each area and driving time period. Furthermore, because the expected supply and demand trends based on previously accumulated past vehicle sales record data can be reflected in the fare, there is no need to constantly monitor the actual busy or quiet conditions. Therefore, appropriate dynamic pricing can be applied to taxi vehicles without increasing the processing load on the server.

[3] An on-board device (soft meter 10) mounted on the taxi vehicle,
The vehicle-mounted device
an on-board correction data acquisition unit (correction coefficient acquisition unit 53) that acquires appropriate fare correction data from the server based on at least one of the passenger boarding location and the boarding time zone;
an on-board fare presentation unit (a pre-determined fare calculation unit 55, a fare presentation unit 56) that presents to the passenger a fare calculated based on the distance traveled by the taxi vehicle calculated based on the passenger's boarding and disembarking locations, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit;
The fee calculation system according to [2] above, comprising:

The fare calculation system configured as described above in [3] makes it possible to apply appropriate dynamic pricing to taxi fares for passengers who have booked a taxi in advance and passengers who board a taxi vehicle without a reservation.

[4] An on-board device (soft meter 10) mounted on the taxi vehicle,
The vehicle-mounted device
A reservation confirmation unit (reservation code authentication unit 57) is provided which, when a user who has made a reservation in advance boards the vehicle as a passenger, communicates with the server to confirm the reservation status of the user.
The fee calculation system according to [2] or [3] above.

With the fare calculation system configured as described in [4] above, when a user who has made a reservation in advance boards a taxi as a passenger, the taxi driver and passenger can use the on-board device to check the reservation status of the user. This reduces the possibility of inconsistencies occurring between, for example, the pre-determined fare confirmed by the user when making the reservation and the fare presented when the user actually boards the taxi.

[5] When applying the fare correction data to increase or reduce the fare, the fare presentation unit presents the user with information indicating the busy or quiet status along with the pre-determined fare (S34, S36).
A fee calculation system according to any one of [2] to [4] above.

The fare calculation system configured as described above in [5] allows users to check whether a fare surcharge or discount has been applied, and to check the reasons for the surcharge or discount, such as peak or off-peak traffic. Users can also understand the peak or off-peak conditions for the area and time period in which they use a taxi.

DESCRIPTION OF SYMBOLS 10 Soft meter 11 Control unit 12, 14, 20 Interface 13 Fare system information storage unit 15 Operation button unit 16 Inertial measurement unit 17 Memory unit 18 Touch panel 19 Display 21 GPS receiver 22 ETC onboard unit 23 LTE communication module 24 External device input device 25 Taxi vehicle 31 Server 32 Internet 33 LTE network 40A, 40B Taxi user 41, 42 User terminal 51 Boarding and alighting point information acquisition unit 52 Time period identification unit 53 Correction coefficient acquisition unit 54 Communication unit 55 Pre-determined fare calculation unit 56 Fare presentation unit 57 Reservation code authentication unit 100 Fare calculation system DB1, DBA Business record DB
DB2 Busyness DB
DB3 Correction coefficient DB
DB4 Taxi reservation DB
DBB Processed DB

Claims (5)

a correction data storage unit that performs statistical processing of supply and demand trends using at least previously accumulated past vehicle business record data, and generates and stores fare correction data that represent busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period based on the results of the statistical processing;
a correction data acquisition unit that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by a user at least when accepting a taxi reservation from the user;
a fare presentation unit that, when accepting at least a taxi reservation from a user, presents to the user a fare calculated based on an estimated taxi vehicle travel distance calculated based on a boarding location and a drop-off location designated by the user, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation device comprising: Taxi vehicles and
a server that manages the taxi vehicles;
The server
a correction data storage unit that performs statistical processing of supply and demand trends using at least previously accumulated past vehicle business record data, and generates and stores fare correction data that represent busy or quiet conditions stratified into multiple categories for at least one of each vehicle's travel area and each travel time period based on the results of the statistical processing;
a correction data acquisition unit that acquires appropriate fare correction data based on at least one of a boarding location and a boarding time zone designated by the user terminal when accepting a reservation for the taxi vehicle from at least the user terminal of the taxi user;
a fare presentation unit that, when accepting a reservation for the taxi vehicle from at least the user terminal, presents to the user a fare calculated based on an estimated travel distance of the taxi vehicle calculated based on a boarding location and a drop-off location designated from the user terminal, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit as a pre-determined fare;
A fee calculation system comprising: An on-board device mounted in the taxi vehicle,
the on-board device is a soft meter that calculates a distance based on location information of the taxi vehicle identified using a global navigation satellite system, and determines a fare based on the calculated distance;
The vehicle-mounted device
an on-board correction data acquisition unit that acquires appropriate fare correction data from the server based on at least one of the passenger boarding location and the boarding time zone;
an on-board fare presentation unit that presents to the passenger a fare calculated based on the distance traveled by the taxi vehicle calculated based on the passenger's boarding location and disembarking location, a predetermined fare system, and the fare correction data acquired by the correction data acquisition unit;
The fee calculation system according to claim 2 . An on-board device mounted in the taxi vehicle,
the on-board device is a soft meter that calculates a distance based on location information of the taxi vehicle identified using a global navigation satellite system, and determines a fare based on the calculated distance;
The vehicle-mounted device
a reservation confirmation unit that, when a user who has made a reservation in advance gets on the train as a passenger, communicates with the server to confirm the reservation status of the user;
The fee calculation system according to claim 2 or 3. The fare presentation unit presents to the user information indicating busy or quiet conditions along with the pre-determined fare when applying the fare correction data to increase or discount the fare.
The fee calculation system according to claim 2 .