Fee calculation device and fee calculation system

Abstract

To facilitate application of an appropriate extra fare or discount fare in accordance with variations in supply and demand for taxis.SOLUTION: In such a case where a user of a taxi reserves a taxi on a server 31, an extra / discount charge in which a busyness / inactive situation corresponding to a pickup location area and a time zone is reflected is made applicable to a pre-fixed charge presented by the server 31 to the user. The server 31 performs statistical processing on past data accumulated in advance in a business record database DB1 per area and per time zone to register busyness degree data in a database DB2. Further, a database DB3 in which a charge correction factor in accordance with the busyness degree is allocated per area and per time zone is utilized. When the server 31 calculates the pre-fixed charge at user's reservation, an extra / discount charge of the charge correction factor relevant to the area and time zone is applied.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a fare calculation device and a fare calculation system that can be used when reserving a taxi or riding in a taxi. [Background technology]

[0002] 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 that reduces or eliminates 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 demand at each location. Furthermore, it provides appropriate commercial facility information according to passengers.

[0003] Furthermore, Patent Document 2 discloses a taxi meter system that reduces or eliminates the burden on taxi drivers when a taxi arrives at a destination. Specifically, when a taxi arrives at a destination, the system notifies the passenger of the arrival using voice or other means. When the taxi arrives at the 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 an 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 exit the vehicle. 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 the distance and time. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-128842 [Patent Document 2] Japanese Patent Application Publication No. 2019-20984 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, while the number of taxi vehicles and drivers owned by taxi companies and the like does not change much, the number of taxi users fluctuates depending on the location, season, time of day, etc. In other words, in the taxi industry, the balance between demand and supply of taxis changes significantly depending on the situation, and there are busy and quiet times.

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

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

[0008] 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, which often makes it difficult for passengers to board a taxi.

[0009] 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 specific area, the extra effort required to get there will not increase motivation, and the driver is unlikely to be motivated to actively travel to that specific area to operate. Therefore, it is difficult to increase the number of taxis operating in busy areas.

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

[0011] Furthermore, even in quiet areas, there are likely to be 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 the actual taxi fare remains constant, it is not possible to stimulate taxi demand by potential taxi users.

[0012] On the other hand, when applying dynamic pricing to taxi fares and trying to make fares variable, it is difficult to determine the appropriate fare. For example, if a premium fare that is too high is applied in a busy area, the number of taxi users may decrease rapidly. Also, 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.

[0013] In particular, unless premium or discount fares are appropriately determined based on the actual level of busyness or quietness, 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 quietness and determine an appropriate fare.

[0014] The present invention has been made in consideration of the above-mentioned circumstances, and its purpose is to provide a fare calculation device and a fare calculation system that can easily determine appropriate surcharges and discount fares in accordance with fluctuations in taxi supply and demand. [Means for solving the problem]

[0015] The above object of the present invention can be achieved by the following configuration.

[0016] At the very least, we need to have the past vehicle sales record data accumulated in advance. Using Statistical processing of supply and demand trends Based on the results of the statistical processing, , fare correction data representing busy or quiet conditions classified into multiple strata for at least one of each vehicle's travel area and each travel time period; Generate a correction data storage unit for storing the correction data; 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:

[0017] Taxi vehicles and a server that manages the taxi vehicles; The server At the very least, we need to have the past vehicle sales record data accumulated in advance. Using Statistical processing of supply and demand trends Based on the results of the statistical processing, , fare correction data representing busy or quiet conditions classified into multiple strata for at least one of each vehicle's travel area and each travel time period; Generate a correction data storage unit for storing the correction data; 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: [Effects of the Invention]

[0018] The fare calculation device and fare calculation system of the present invention make it easy to determine appropriate surcharge and discount fares in accordance with fluctuations in taxi supply and demand. That is, because supply and demand trends obtained by statistical processing of previously accumulated past vehicle business record data are stored as fare adjustment data that indicate busy or quiet conditions, it becomes possible to grasp busy or quiet areas and time periods and appropriately reflect this in fares.

[0019] The present invention has been briefly described above. The details of the present invention will become clearer by reading the following detailed description of the invention (hereinafter referred to as "embodiments") with reference to the accompanying drawings. [Brief explanation of the drawings]

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

[0021] Specific embodiments of the present invention will be described below with reference to the accompanying drawings.

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

[0023] The fare calculation system 100 shown in Fig. 1 includes a soft meter 10 mounted on a taxi vehicle 25 and a server 31 installed in a data center or the like. Of course, a general taxi meter can be used instead of the soft meter 10.

[0024] Furthermore, each taxi user 40A, 40B who uses the taxi vehicle 25 can communicate with the server 31 using user terminals 41, 42, for example, when making a reservation. The user terminals 41, 42 can be, for example, a mobile terminal such as a general smartphone or a personal computer (PC).

[0025] The soft meter 10 is a device that can perform the same functions as a general taxi meter installed in a taxi vehicle. However, while a taxi meter is a specified measuring instrument that is subject to the Measurement Act, the soft meter 10 is not currently a specified measuring instrument.

[0026] Specifically, a taximeter measures distance by integrating the circumference of a rotating part such as a wheel to measure the actual distance. On the other hand, the soft meter 10 calculates distance based on vehicle position information identified using a Global Navigation Satellite System (GNSS) such as GPS, and determines the taxi fare based on that distance.

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

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

[0029] The control unit 11 is configured by an electronic circuit mainly including, for example, a microcomputer, and performs control to realize the functions required for the soft meter 10 by executing a program prepared in advance.

[0030] The GPS receiver 21 receives radio wave signals from multiple (three or more) GPS satellites and calculates the latitude / longitude that represents the current position based on the time of the received signal, i.e., performs 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 identify the current position.

[0031] Position information detected by the GPS receiver 21 periodically (for example, every second) is input to the control unit 11 via the interface 12. Information indicating whether the GPS receiver 21 is currently measuring its position is also input to the control unit 11 together with the position information.

[0032] The fare system information storage unit 13 is configured with a read-only memory (ROM) or the like and stores data on a predetermined fare system. For example, data such as a predetermined basic fare amount, a unit distance traveled, an additional fare per unit distance traveled, a length of a unit time, and an additional fare per unit time is stored in the fare system information storage unit 13.

[0033] The ETC vehicle-mounted unit 22 performs road-to-vehicle wireless communication with, for example, roadside equipment (not shown) on an expressway or toll road. 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, etc.) with the roadside equipment.

[0034] The operation button unit 15 is arranged on the front of the soft meter 10 and has buttons such as "empty," "occupied," 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 such as "empty," "occupied," and "payment" and their changes, just as in the case of a general taxi meter.

[0035] The inertial measurement unit 16 is an electronic device that incorporates a gyro sensor that detects acceleration in three axial directions and a sensor that detects rotational angular acceleration in three axial directions. 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 cannot determine the position, it is possible to obtain an estimate of the current position of the vehicle from the measurement results of the inertial measurement unit 16.

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

[0037] The touch panel 18 can be used by the control unit 11 to read a touch by 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 located on the front of the soft meter 10.

[0038] 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 using 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.

[0039] On the other hand, the server 31 is connected to an LTE network 33 via the Internet 32. The soft meter 10 mounted on the taxi vehicle 25 and each user terminal 41, 42 can connect to the server 31 by wireless communication using the LTE communication module 23.

[0040] The server 31 shown in Fig. 1 has a function for realizing dynamic pricing as a distinctive function. Specifically, when calculating fares for the taxi vehicles 25, the server 31 has a function for applying surcharges or discounts according to the busyness of the area or time of day.

[0041] 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 ​​the boarding and disembarking locations and the time of day the ride will take place.

[0042] In reality, the server 31 accumulates and stores a database (DB) DBA of business records that represent past performance. Therefore, by statistically processing past performance, it is possible to construct a processed database DBB of busy conditions stratified by boarding and disembarking areas and boarding time periods. The server 31 can reflect the busy conditions in the processed database DBB in pre-determined fares, etc.

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

[0044] The business record database DB1 in Fig. 2 corresponds to the business record DBA in Fig. 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).

[0045] The business performance data stored in the business 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.

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

[0047] 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 item by area and time period 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 be included in the busyness level database DB2.

[0048] The server 31 also has a reservation function (S15) for accepting taxi reservations from each of the taxi users 40A and 40B. Specifically, in response to access to the server 31 from each of the user terminals 41 and 42 that have pre-installed predetermined application software (app), the server 31 can issue a coupon ticket or a taxi ticket for using a taxi.

[0049] For example, when a user specifies the boarding location, disembarking location, and travel time, the server 31 presents the user with a pre-determined fare and issues the corresponding coupon ticket or taxi ticket. The coupon tickets and taxi tickets issued by the 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 of the coupon ticket or taxi ticket using the user terminal 41, 42.

[0050] Information on coupon tickets and taxi tickets issued by the server 31 is registered and managed in the taxi reservation database DB4. When a user gets into 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).

[0051] FIG. 3 is a block diagram showing the major functional components of soft meter 10.

[0052] In the example shown in Figure 3, the soft meter 10 includes a boarding and disembarking 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.

[0053] The boarding and alighting point information acquisition unit 51 acquires, as the position of the boarding point, the latitude / longitude of the latest vehicle position acquired from the GPS receiver 21, for example, when the driver of the taxi vehicle 25 operates the "actual vehicle" button. Also, as the position of the disembarking point, the boarding and alighting point information acquisition unit 51 acquires, as the position of the boarding point, the latitude / longitude of the latest vehicle position acquired from the GPS receiver 21, for example, when the driver of the taxi vehicle 25 operates the "payment" button. Alternatively, the boarding and alighting point information acquisition unit 51 acquires, as the position of the disembarking point, the position of the destination on a map specified by the passenger, for example.

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

[0055] 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 the boarding and disembarking points calculated on a road map, and the correction coefficient acquired by the correction coefficient acquisition unit 53. Alternatively, the pre-determined fare calculation unit 55 successively measures the travel distance from the boarding point based on changes in position information detected at regular intervals, and calculates the normal taxi fare in real time based on the 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.

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

[0057] The reservation code authentication unit 57 reads the reservation code (e.g., a QR code) of the taxi coupon or taxi ticket presented by the user with the external equipment input device 24, and authenticates whether it is a legitimate 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 inquires of the server 31 whether the reservation code matches a pre-registered reservation code. Furthermore, if a pre-determined fare determined at the time of reservation is registered in the server 31, the reservation code authentication unit 57 obtains information about that pre-determined fare from the server 31.

[0058] Fig. 4 is a flowchart showing the details of the operation of statistically processing the business performance in terms of busyness. That is, Fig. 4 shows a specific example of the process S12 in Fig. 2 by the server 31. The operation in Fig. 4 will be described below.

[0059] 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, the server 31 extracts and acquires business records for the past one or two months from that point in time.

[0060] 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 area with a certain radius (for example, 1 km or 2 km) from a characteristic point with a lot of pedestrian traffic, such as a railway station.

[0061] 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 vehicles for each area based on the business records for the areas extracted in S23 (S25). Note that the number of operating vehicles of taxi businesses operating in the area may be used in S25 instead of the average number of empty vehicles.

[0062] 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 state for each time period for each area. Note that the threshold value used for comparison in S27 can be changed as needed.

[0063] The server 31 recognizes the time period and area where the occupancy rate is equal to or greater than the threshold as a "busy" situation (S28). In addition, the server 31 recognizes the time period and area that do not fall under the "busy" situation as a "quiet" situation (S29).

[0064] The server 31 registers the results of the recognition in S28 and S29 in Fig. 4 in the busyness degree database DB2 shown in Fig. 2. That is, data representing the busyness degree by area and by time period is registered in the busyness degree database DB2.

[0065] In addition, a fee correction coefficient according to the busyness level by area and time period registered in the busyness level database DB2 is assigned to each area and time period in S13 in FIG. 2 and registered in the correction coefficient database DB3.

[0066] Fig. 5 is a flowchart showing the operation when the server 31 calculates a predetermined fee. That is, Fig. 5 shows a specific example of the operation of the process S14 shown in Fig. 2 by the server 31. The operation of Fig. 5 will be described below.

[0067] For example, when a taxi user 40A makes a reservation, if the user specifies the boarding location and boarding time of the reserved taxi, the information is input to the server 31. The server 31 then reads the input boarding location and boarding time in S31 and proceeds to the next process in S32.

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

[0069] If the specified boarding location and boarding time fall within a busy time period and area, the server 31 reads out 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).

[0070] 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 calculated fall under the "busy area and time period" (S34). For example, the server 31 controls the application running on the user terminal 41 to display a message indicating the "busy area and time period" on the screen or to announce the same by voice output. Alternatively, the server 31 or the soft meter 10 controls the application running on the user terminal 41 to display a message indicating that the soft meter 10 falls under the "busy area and time period" to a passenger in the taxi vehicle 25 or to announce the same by voice output.

[0071] 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 out 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).

[0072] Furthermore, when applying a fare correction coefficient for a discount fare, the server 31 notifies the user that the area and time period for which the fare is currently calculated fall under the "off-peak area and time period" (S36). For example, the server 31 controls the application running on the user terminal 41 to display a message indicating the "off-peak area and time period" on the screen or to announce the message by voice output. Alternatively, the server 31 or the soft meter 10 controls the application running on the user terminal 41 to display a message indicating that the soft meter 10 falls under the "off-peak area and time period" to a passenger in the taxi vehicle 25 or to announce the message by voice output.

[0073] For example, when a taxi user 40A makes a reservation, if the drop-off location of the reserved taxi, i.e., the destination, is specified, the information is input to the server 31. Then, the server 31 reads the input drop-off location in S37 and proceeds to the next process of S38.

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

[0075] The server 31 calculates a predetermined fare based on the predetermined taxi fare system and the planned distance traveled calculated in S38, and also calculates a 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.

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

[0077] 6 is a sequence diagram showing an example of the operation of the entire system. The operation shown in FIG. 6 will be explained below.

[0078] Users, i.e., taxi users 40A and 40B, connect to the server 31 via the Internet 32 ​​using user terminals 41 and 42, and can use the communication services of the server 31. Specifically, users can purchase a taxi coupon or taxi ticket from the server 31 and make a reservation for a taxi ride (S51).

[0079] When a user specifies a boarding location, a drop-off location, a day of the week, a time period, etc. when making a taxi reservation, the server 31 can determine the amount of a pre-determined fare by, for example, executing the process shown in Fig. 5. The server 31 presents the determined amount of the pre-determined fare to the user (S52).

[0080] When the user confirms the amount of the pre-determined fare and carries out the procedure to purchase a coupon ticket or taxi ticket, the server 31 accepts the user's reservation, 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 purchases a coupon ticket or a taxi ticket receives a reservation code issued by the server 31 at a user terminal 41, 42.

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

[0082] In order to confirm that the reservation code read from the user terminal 41 is a valid code that can be used, the soft meter 10 connects to the server 31 using the LTE communication module 23 and makes an authentication inquiry.

[0083] The server 31 searches the taxi reservation database DB4 and executes authentication processing for the reservation code inquired about by the soft meter 10 (S58). If the authentication of the reservation code is successful, the server 31 can obtain information on the coupon or taxi ticket linked to the reservation code from the taxi reservation database DB4, and then notifies the soft meter 10 of the information.

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

[0085] The present invention is not limited to the above-described embodiments, and can be appropriately modified, improved, etc. Furthermore, the material, shape, size, number, location, etc. of each component in the above-described embodiments are arbitrary and not limited as long as they can achieve the present invention.

[0086] For example, in the above-mentioned fare calculation system 100, it is assumed that when a user pre-reserves a taxi, the server 31 applies 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.

[0087] In such a case, it is possible that fare surcharges 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 expected that the server 31 etc. will present to the user at the time of reservation conditions such as the area, time period, and degree of surcharge / discount to which the fare surcharge or discount applies.

[0088] 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 surcharges or discounts to passengers who have made reservations in advance according to the busyness of the area and time period.

[0089] 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 the vehicle's running area and running time zone, as a result of statistically processing at least previously accumulated past vehicle sales record data (sales record database DB1) regarding supply and demand trends; 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 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 (S39) as a pre-determined fare; A fee calculation device (server 31) comprising:

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

[0091] [2] Taxi vehicles (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 vehicle travel area and travel time zone, as a result of statistically processing supply and demand trends on at least previously accumulated past vehicle sales record data (sales 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 an alighting 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:

[0092] The fare calculation system configured as described in [2] above makes it possible to present a user reserving a taxi with a pre-determined fare that reflects the expected peak or trough conditions for each area and each driving time period. Furthermore, because the fare reflects the expected supply and demand trends based on the vehicle's past sales record data accumulated in advance, there is no need to constantly monitor the actual peak or trough conditions. This makes it possible to apply appropriate dynamic pricing to taxi vehicles without increasing the processing load on the server.

[0093] [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 (predetermined fare calculation unit 55, 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 alighting 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.

[0094] According to the fare calculation system configured as described above in [3], it is 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.

[0095] [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 described in [2] or [3] above.

[0096] According to the fare calculation system configured as described in [4] above, when a user who has made a reservation in advance gets into a taxi as a passenger, the taxi driver and passenger can use the on-board device to check the reservation status of the user. Therefore, it is possible to reduce the possibility of inconsistencies occurring between the pre-determined fare confirmed by the user at the time of reservation and the fare presented when the user actually gets into the taxi.

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

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

[0099] 10 Soft Meter 11 Control section 12,14,20 Interface 13. Fee system information storage unit 15 Operation buttons 16 Inertial Measurement Unit 17 Memory Unit 18 Touch Panel 19 Display 21 GPS receiver 22 ETC on-board device 23 LTE communication module 24 External device input device 25 taxi vehicles 31 servers 32 Internet 33 LTE network 40A, 40B Taxi users 41,42 User terminal 51 Boarding and alighting point information acquisition unit 52 Time zone identification section 53 Correction coefficient acquisition unit 54 Communications Department 55 Advance Fee Calculation Department 56 Fare Display Section 57 Reservation code authentication section 100 Fee Calculation System DB1, DBA Sales record DB DB2 Busyness DB DB3 Correction coefficient DB DB4 Taxi Reservation DB DBB Processed DB

Claims

1. 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:

2. 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:

3. 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 .

4. 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.

5. 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 .

Images