JP6431338B2 - Taximeter and taximeter system - Google Patents

Description

  The present invention relates to a taximeter and a taximeter system.

  2. Description of the Related Art Conventionally, a taxi meter that calculates a fare based on a travel distance and a rent time when a taxi vehicle is rented is known (see, for example, Patent Document 1). Such taximeters use taxi tickets issued by taxi operators and taxi tickets issued by local governments (sometimes called welfare tickets, which can be paid in full or in part). Taxi fees may be settled.

JP 2010-262348 A

  However, there are the following problems in the settlement of taxi fare with a conventional taxi ticket. First, passengers hand taxi tickets to the crew at the time of taxi fare settlement. The crew members had to visually check whether the taxi tickets that were handed out were issued by a usable group or were valid. For this reason, when there is an error in the visual confirmation of the crew, the taxi fare may be settled despite the invalid ticket. In particular, when using taxi tickets, passengers cannot wait for a long time, and further, when using taxi tickets at night, it becomes more difficult to see, so it is easy to make visual errors. End up. And since taxi tickets will be billed to users at a later date, taxi fees will be generated if the taxi fee is settled despite being an invalid ticket. It will be connected.

  The present invention has been made to solve such conventional problems, and an object of the present invention is to provide a taximeter and a taximeter system capable of preventing the occurrence of uncollected money. is there.

A taximeter according to the present invention is a taximeter that calculates and displays a taxi fare according to a travel distance to a destination designated by a passenger and a stop time in a rented state, and is described in the taxi ticket. Based on the barcode including ticket information for determining whether or not the ticket is valid, the reading means for reading the ticket information, and determining whether the ticket is valid based on the ticket information read by the reading means Valid judgment means and communication means capable of transmitting and receiving information to and from the management server wirelessly, wherein the communication means transmits the ticket number information included in the ticket information read by the reading means to the management server And a determination result of whether or not the ticket indicated by the ticket number is used, which is determined by the management server. The ticket information includes determination information of at least one of type information indicating a taxi company that can use the taxi ticket and expiration date information indicating an expiration date that can use the taxi ticket. After the ticket number information is transmitted to the management server by the communication means, it is determined whether the ticket is valid based on the determination information without going through the communication means, and then the communication means It is determined whether the ticket is valid based on the received determination result .

According to the taximeter of the present invention, since it is determined whether or not the ticket is valid based on the read ticket information, it is not necessary for the crew to visually check, and payment is made with an invalid taxi ticket due to a crew member's confirmation error. Can be prevented. Therefore, generation | occurrence | production of uncollected money can be prevented. The ticket number information included in the ticket information is sent to the management server, the judgment result on whether the taxi ticket indicated by the ticket number is used, which is judged by the management server, is received, and the result that it is used Is received, it is determined that the ticket is not valid. For this reason, it is not necessary to store a huge amount of used ticket number data in the taximeter when it is managed by the ticket number, and the storage capacity of the taximeter can be reduced. it can.

  In this taxi meter, the ticket information, the taxi boarding place and the getting off place of the passenger by using the ticket, the taxi route from the boarding place to the getting off place, the taxi settlement amount for using the ticket, and The storage means for storing at least one piece of information on the settlement date using the taxi with the ticket, the end determination means for determining the end of taxi business, and the end determination means when the end of business is determined, It is preferable to further comprise output means for outputting the at least one information stored in the storage means.

  According to this taximeter, when it is determined that the business has ended, at least one of the stored ticket information and information such as the taxi boarding location and the getting off location is output. The crew can write various information on the ticket at the time of settlement, and this can be used to reduce the trouble of taking the ticket to the taxi operator's office.

  The taximeter system of the present invention includes the taximeter described above, and a management server that transmits and receives information via the taximeter and the communication unit, and the management server is read by the reading unit. The taxi ticket indicated by the received ticket number is used by receiving the ticket number information contained in the received ticket information and determining whether the received ticket number is included in the stored used ticket number. If it is determined that it is not used, it is transmitted to the taximeter, and the received ticket number is stored as a used ticket number.

  According to the taximeter system of the present invention, the management server receives the ticket number information included in the read ticket information, determines whether the taxi ticket indicated by the received ticket number is used, and is used. If not, the fact is transmitted to the taximeter and the received ticket number is stored as the used ticket number. For this reason, if a taxi ticket number that has not been used is received, it is stored as a used ticket number on the assumption that the taxi ticket with this number will be used for payment. It is possible to save the trouble of transmitting the ticket number to the management server again as the used ticket number.

  ADVANTAGE OF THE INVENTION According to this invention, the taximeter which can prevent generation | occurrence | production of uncollected money can be provided.

It is a block diagram which shows the taximeter system containing the taximeter which concerns on embodiment of this invention. It is a block diagram which shows the taximeter which concerns on embodiment of this invention. It is a flowchart which shows the process of the taximeter which concerns on this embodiment. It is a flowchart which shows the process of the management server which comprises the taximeter system which concerns on this embodiment.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of the invention will be described with reference to the drawings. The present invention is not limited to the embodiments shown below.

  FIG. 1 is a block diagram showing a taximeter system including a taximeter according to an embodiment of the present invention. As shown in FIG. 1, the taximeter system includes a taximeter 1 mounted on a taxi vehicle and a management server 2 that communicates with the taximeter 1.

  Here, the barcode B is given to the taxi ticket C used for the settlement of the taxi fare in this embodiment. The barcode B here is, for example, a one-dimensional barcode or a two-dimensional barcode, and ticket information for determining whether the taxi ticket C is valid is coded. The ticket information includes ticket number information, type information, and expiration date information.

  The ticket number information is information of different numbers assigned to each taxi ticket C. That is, the number of a specific taxi ticket C is not basically the same as the number of another taxi ticket C. The type information is information for determining which taxi company can use the taxi ticket C, and includes, for example, information on the ticket company code and information on the type of taxi ticket. The expiration date information is information indicating a period during which the taxi ticket C is valid.

  In this embodiment, a taxi ticket C on which a barcode B is written is used. The taximeter main body 10 reads ticket information from the barcode B through the barcode reader 40 provided in the taximeter 1 and determines whether the taxi ticket C is valid. In addition, a wireless communication unit 17 is connected to the taximeter main body 10 and communicates with the management server 2 as necessary to determine whether the taxi ticket C is valid.

  Thus, since the taximeter 1 determines whether the taxi ticket C is valid based on the ticket information read via the barcode reader 40, it is unnecessary for the crew to determine whether the taxi ticket C is valid. Thus, it is possible to prevent a settlement with an invalid taxi ticket due to an error in the crew member's confirmation.

  The management server 2 stores the ticket number of the taxi ticket C used by a plurality of taxi operators as information on the used taxi ticket C. In the following description, the management server 2 will be described as one that stores information on used taxi tickets C installed in a ticket center and used by a plurality of taxi operators. It may be installed in a taxi operator's office and may function as a storage of information on used taxi tickets C only for a specific taxi operator.

  Furthermore, when the management server 2 is installed in the ticket center, the taxi operator can connect to the management server 2 through the Internet line I from the taxi operator's PC 3, and the taxi operator can use, for example, a ticket used in his company. You can browse and download the information. The management server 2 may transmit various information (particularly ticket information or settlement information described later) to the PC 3 as needed.

  The details of the taximeter 1 will be described below with reference to FIG.

  FIG. 2 is a block diagram showing the taximeter 1 according to the embodiment of the present invention. As shown in FIG. 1, a taximeter 1 includes a taximeter body 10, a GPS (Global Positioning System) receiver 20 connected to the taximeter body 10, an ETC (Electronic Toll Collection System) vehicle-mounted device 30, and a barcode. A reader (reading means) 40.

  The taximeter main body 10 calculates and displays a taxi fare according to the travel distance to the destination designated by the passenger and the stop time in the rented state. The taximeter body 10 includes a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 12, a ROM (Read Only Memory) 13, a clock IC 14, a non-contact card read ride interface (hereinafter referred to as non-contact R / R). W / I / F) 15, display 16, wireless communication unit (communication means) 17, and various interfaces (referred to as I / F) 18 a to 18 c.

  The CPU 11 controls the entire taximeter body 10, and includes a RAM 12, a ROM 13, a clock IC 14, a non-contact R / W • I / F 15, a display 16, a wireless communication unit 17, and an I / F 18a. To 18c.

  The RAM 12 is used as a work area when the CPU 11 performs processing. For example, the RAM 12 temporarily stores information such as a travel distance and a stop time in a taxi vehicle in a rental state, and a vehicle speed. The travel distance information is updated based on a speed signal from a vehicle speed sensor (not shown), and the stop time information is updated based on the time measured by the clock IC 14.

  The ROM 13 stores programs and the like. The clock IC 14 has a function of measuring the stop time in the rental state (including the waiting state for waiting for arrival) and a function of grasping the current date and time. The non-contact R / W / I / F 15 is a reading / writing device into which a crew card owned by a crew member who rides in a taxi vehicle is inserted. The display 16 displays, for example, the current taxi fare at the time of renting and the tariff state. As described with reference to FIG. 1, the wireless communication unit 17 transmits and receives information to and from the management server 2 installed in a ticket center, for example.

  The first I / F 18 a serves as a connection part with the GPS receiver 20, and the second I / F 18 b serves as a connection part with the ETC in-vehicle device 30. The third I / F 18 c serves as a connection part with the barcode reader 40.

  In addition to the above, the taximeter main body 10 has an EEPROM (Electrically Erasable) that stores a charge table with set values such as initial fare, how many kilometers to add for how many kilometers, and how many yen to add for how many minutes to stop. Programmable Read Only Memory (not shown).

  The CPU 11 includes a calculation unit 11a for calculating a taxi fare, and the calculation unit 11a calculates the current taxi fare based on the price table and causes the display 16 to display the taxi fare.

  The GPS receiver 20 acquires information about its own position by receiving radio waves from GPS satellites, and transmits the acquired position information to the taximeter main body 10. The ETC in-vehicle device 30 performs wireless communication with an antenna attached to a toll booth on the highway, and pays a high-speed fee by exchanging appropriate fee information. The ETC vehicle-mounted device 30 transmits the paid fee information and the information on the highway use section to the taximeter main body 10.

  The barcode reader 40 reads ticket information from the barcode B described in the taxi ticket C. The barcode reader 40 transmits the read ticket information to the taximeter main body 10 via the interface 18c.

  Further, the CPU 11 includes a ticket data analysis unit (valid determination unit) 11b. The ticket data analysis unit 11b determines whether the taxi ticket C is valid based on the ticket information read by the barcode reader 40.

  In the present embodiment, the ticket data analysis unit 11b 1) determines whether or not the ticket C can be used based on, for example, a company code, and 2) determines whether or not the ticket C can be used based on whether or not it is within the expiration date. Judgment 3) Judgment whether or not the ticket C can be used based on whether or not it has been used 4) Whether or not the ticket C can be used based on whether or not it is a bad ticket registered as unusable 4 judgments are made. If the ticket data analysis unit 11b determines that all the above four are usable, the ticket data analysis unit 11b finally determines that the taxi ticket C is valid. On the other hand, when it is determined that any one of them is not usable, the ticket data analysis unit 11b determines that the taxi ticket C is invalid.

  First, the determination of 1) will be described in detail. The above-described barcode B of the taxi ticket C includes type information (ticket company code information). The ticket company code is a code indicating a taxi company that can use the taxi ticket C. Further, the company code information of the company is stored in the ROM 13 or the like of the taximeter main body 10. For this reason, the ticket data analysis unit 11b determines whether the ticket company code included in the barcode B matches the company code stored in the ROM 13 or the like, and if it matches, the taxi ticket C is used. Judge that it is possible.

  Next, the determination of 2) will be described. The bar code B of the taxi ticket C includes information on the expiration date of the taxi ticket C. The ticket data analysis unit 11b compares the information on the expiration date of the taxi ticket C included in the barcode B with the information on the current date and time measured by the clock IC 14, and the current time is within the expiration date of the taxi ticket C. If it is within the expiration date, it is determined that the taxi ticket C can be used.

  The determination of 3) will be described. The barcode B of the ticket C includes the ticket number information. Further, the management server 2 installed in the ticket center stores information on the number of the used taxi ticket C. When acquiring the ticket number information included in the barcode B, the CPU 11 transmits the ticket number information to the management server 2 through the wireless communication unit 17. The management server 2 receives the ticket number information and determines whether the stored ticket number is included in the stored number of the used taxi ticket C. Thereby, the management server 2 determines whether the taxi ticket C indicated by the received ticket number has been used. If the management server 2 determines that it has not been used, the management server 2 transmits the fact to the taximeter 1. The taximeter main body 10 determines that the taxi ticket C can be used when receiving information indicating that it has not been used via the wireless communication unit 17. Note that when the management server 2 receives the ticket number information, it is expected that the taxi ticket C indicated by the ticket number will be used for payment, so the received ticket number information is used as the used ticket number information. Will be remembered.

  Furthermore, the determination of 4) will be described. First, a taxi operator or a company that is billed for a taxi fare by taxi ticket C can set a taxi ticket C that the user does not want to use. For example, when the taxi ticket C is stolen in a company or the like, the taxi ticket C number stolen via the PC 3 is registered in the management server 2. As a result, the registered taxi ticket C number is registered as a defective ticket C number in the management server 2. Therefore, the management server 2 determines whether the ticket number received as described above is registered as the number of the defective ticket C, and determines that the taxi ticket C can be used if not registered.

  When it is determined that the taxi ticket C is usable in all of the above four processes, the CPU 11 determines that the taxi ticket C is valid and performs settlement processing. That is, the CPU 11 issues a receipt, which is a receipt dedicated to the use of the taxi ticket C, or performs a process of counting sales by the taxi ticket C.

  The RAM 12 includes a ticket settlement data storage unit (storage unit) 12a. The ticket settlement data storage unit 12a stores at least one of the ticket information and settlement information of the taxi ticket C. Here, the payment information includes the taxi boarding place and the getting off place of the passenger by using the taxi ticket C, the taxi way place from the boarding place to the getting off place, the amount of the taxi settlement by using the ticket C, and It means at least one piece of information on the settlement date using the taxi with the ticket C.

  Further, the CPU 11 includes an end determination unit (end determination unit) 11c and an output unit (output unit) 11d. The end determination unit 11c determines the end of taxi business. The end determination unit 11c determines that the business has ended, for example, when a predetermined button provided on the taximeter main body 10 is operated, and determines that the business is in operation until the predetermined button is operated.

  The output unit 11d outputs information stored in the ticket settlement data storage unit 12a when the end of the business is determined by the end determination unit 11c. The output destination is, for example, the memory card MC connected to the taximeter main body 10 or the wireless communication unit 17. When the output destination is the wireless communication unit 17, the information is transmitted to the taxi operator's PC 3 through the wireless communication unit 17. In this way, the information is stored in the ticket settlement data storage unit 12a and output to the memory card MC or the wireless communication unit 17, so that a lot of labor is required as compared with the case where various information is written on the paper ticket and brought back to the office. Can be reduced.

  In addition, both when the output unit 11d outputs information to the memory card MC and when outputting to the taxi operator's PC 3 through the wireless communication unit 17, manual input work by a taxi operator's office worker or the like is required. Omitted. That is, in the past, various information described in the taxi ticket was manually input to the PC 3 by the taxi operator's office worker, etc. In both cases, the information in the memory card MC and the information to be transmitted are It only needs to be read into PC3, and the time and labor within the taxi operator can be reduced.

  Next, processing of the taximeter system according to the present embodiment will be described. FIG. 3 is a flowchart showing processing of the taximeter 1 according to the present embodiment. As shown in FIG. 3, first, the CPU 11 of the taximeter 1 determines whether the ticket information has been read via the barcode reader 40 (S1).

  If it is determined that the ticket information has not been read (S1: NO), this process is repeated until it is determined that the ticket information has been read. On the other hand, if it is determined that the ticket information has been read (S1: YES), the CPU 11 stores the read ticket information in the ticket settlement data storage unit 12a (S2).

  Next, the CPU 11 transmits the ticket number information to the management server 2 through the wireless communication unit 17 (S3). Thereafter, the ticket data analysis unit 11b determines whether the taxi ticket C is usable by the taxi company to which the taxi vehicle equipped with the taxi meter 1 belongs based on the type information included in the ticket information (S4). ).

  If it is determined that the taxi operator can use the taxi ticket C (S4: YES), the ticket data analysis unit 11b determines that the taxi ticket C is within the expiration date based on the expiration date information included in the ticket information. It is judged whether it is a thing (S5).

  When it is determined that it is within the expiration date (S5: YES), the ticket data analysis unit 11b determines whether the determination result from the management server 2 has been received (S6). The determination result here is a determination result of whether the taxi ticket C having the ticket number transmitted in step S3 is a used ticket C or a defective ticket C.

  If it is determined that the determination result from the management server 2 has not been received (S6: NO), this process is repeated until it is determined that the determination has been received. On the other hand, when it is determined that the determination result from the management server 2 has been received (S6: YES), the ticket data analysis unit 11b determines that the taxi ticket C is the used ticket C based on the determination result from the management server 2. Is determined (S7).

  When it is determined that the taxi ticket C is not a used ticket C (S7: NO), the ticket data analysis unit 11b determines whether the taxi ticket C is a defective ticket C based on the determination result from the management server 2. (S8).

  When it is determined that the taxi ticket C is not a defective ticket C (S8: NO), the ticket data analysis unit 11b determines that the taxi ticket C is valid. Then, the CPU 11 executes ticket settlement processing (S9), and stores settlement information in the ticket settlement data storage unit 12a (S10). Then, the process shown in FIG. 3 ends.

  By the way, when it is determined that the taxi ticket C is not usable by the taxi operator (S4: NO), when it is determined that the taxi ticket C is not within the expiration date (S5: NO), the taxi ticket C has been used. When it is determined that the ticket C is the ticket C (S7: YES) and when the taxi ticket C is determined to be the defective ticket C (S8: YES), the ticket data analysis unit 11b determines that the taxi ticket C is invalid. to decide. Then, the CPU 11 executes a ticket settlement NG process (S11), and the process shown in FIG.

  The ticket settlement NG process is, for example, a process of displaying that the taxi ticket C is invalid on the display 16 or outputting a voice indicating that the taxi ticket C is invalid from a voice output unit (not shown). is there.

  Here, as is apparent from FIG. 3, the taximeter 1 determines whether the taxi ticket C can be used by the taxi operator based on the type information included in the ticket information (S4), and Prior to both processing for determining whether the taxi ticket C is within the expiration date based on the expiration date information included in the ticket information (S5), the ticket number information is transmitted to the management server 2 (S3). ). As a result, the information of the ticket number is transmitted in step S3, and after that, the process of steps S4 and S5 is executed until the judgment result is returned from the management server 2 so as to contribute to the reduction of the waiting time of the passengers. I have to.

  Furthermore, in the process of step S11, the CPU 11 preferably deletes the ticket information stored in step S2. In the process of step S2, ticket information is stored in the ticket settlement data storage unit 12a in order to execute processes in later steps S3 to S5. For this reason, when it is determined that the taxi ticket C is invalid, it is not necessary to store the taxi ticket C, so it is preferable to delete it. When it is determined that the taxi ticket C is valid, it is preferable not to delete the ticket information of the used taxi ticket C because it is necessary for management by the taxi operator.

  FIG. 4 is a flowchart showing processing of the management server 2 constituting the taximeter system according to the present embodiment. As shown in FIG. 4, the management server 2 first determines whether or not ticket number information has been received (S21). If it is determined that the ticket number information has not been received (S21: NO), this process is repeated until it is determined that the ticket number has been received.

  When determining that the ticket number information has been received (S21: YES), the management server 2 determines whether the received ticket number corresponds to the used ticket C (S22). When it judges that it corresponds (S22: YES), management server 2 transmits that it is used ticket C to taximeter 1 (S23). Then, the process shown in FIG. 4 ends.

  On the other hand, when it is determined that the received ticket number does not correspond to the used ticket C (S22: NO), the management server 2 determines whether the received ticket number corresponds to the defective ticket C (S24). If it is determined that this is the case (S24: YES), the management server 2 transmits to the taximeter 1 that it is a defective ticket C (S25). Then, the process shown in FIG. 4 ends.

  When it is determined that the received ticket number does not correspond to the defective ticket C (S24: NO), the management server 2 determines that the taxi ticket C indicated by the received ticket number is usable, and transmits that fact. (S26). And the management server 2 memorize | stores the received ticket number as a number of the used ticket C on the assumption that the taxi ticket C will be used by transmission of step S26 (S27). Then, the process shown in FIG. 4 ends.

  Here, as is clear from FIG. 4, when the received ticket number corresponds to the number of the used ticket C (S22: YES), it is not determined whether or not the ticket is a defective ticket C (S24). That is, when the ticket corresponds to the used ticket C, the taxi ticket C is invalid regardless of whether it is a defective ticket C, so the processing is omitted to speed up the process.

  Thus, according to the taximeter 1 according to the present embodiment, it is determined whether the ticket C is valid based on the read ticket information. It is possible to prevent the settlement with an invalid taxi ticket C. Therefore, generation | occurrence | production of uncollected money can be prevented.

  In addition, when it is determined that the business has ended, at least one of the stored ticket information and information such as the taxi boarding location and the getting off location is output. Various information can be written by the crew, which can be used to reduce the time and effort required to take the ticket to the taxi operator's office.

  When the above information is output to a portable recording medium such as a memory card MC in more detail, the memory card MC may be taken back to the taxi operator's office, and the trouble of writing in the taxi ticket may be omitted. it can. Furthermore, when the above information is output wirelessly to the taxi operator's office, not only the trouble of writing in the ticket but also the trouble of bringing the memory card MC back to the office can be omitted.

  In addition, the ticket number information included in the ticket information is transmitted to the management server 2, and the judgment result on whether the taxi ticket C indicated by the ticket number is used, which is judged by the management server 2, is received and used. Is received, a determination is made that the ticket C is not valid. For this reason, it is not necessary to store a huge amount of used ticket C number data in the taximeter 1 when it is managed by the ticket number, and the storage capacity of the taximeter 1 is reduced. can do.

  Moreover, according to the taximeter system according to the present embodiment, the management server 2 receives the ticket number information included in the read ticket information, and whether the taxi ticket C indicated by the received ticket number has been used. If it is determined that it has not been used, the fact is transmitted to the taximeter 1 and the received ticket number is stored as the number of the used ticket C. Therefore, when a taxi ticket C number that has not been used is received, it is stored as the number of the used ticket C on the assumption that the taxi ticket C of this number is used for the settlement. However, it is possible to omit the trouble of transmitting the ticket number to the management server 2 again as the number of the used ticket C after the settlement is completed.

  Moreover, since the management server 2 receives the ticket information read by the barcode reader 40 as needed and stores it as the number of the used ticket C, the management server 2 stores the information on the number of the used ticket C in real time. It will be accumulated. As a result, for example, compared with a method of downloading information on a used taxi ticket C at the start of business, the management server 2 updates the information on the used taxi ticket C at any time. It is possible to prevent fraud by using the same taxi ticket C immediately afterwards.

  As described above, the present invention has been described based on the embodiment, but the present invention is not limited to the above embodiment, and may be modified without departing from the gist of the present invention.

  For example, in the above embodiment, the taximeter 1 transmits the ticket number information to the management server 2 so that the management server 2 determines whether the ticket is a used ticket C or a bad ticket C. However, the present invention is not limited to this, the taximeter 1 or the memory card MC stores information on the number of the used ticket C and information on the number of the defective ticket C, and the used ticket C is used in the CPU 11 of the taximeter 1. Or whether it is a bad ticket C may be executed.

  In the above embodiment, the company code determines whether the taxi ticket C is issued by a group that can be used. However, the present invention is not limited to this, and the determination may be made based on the ticket number. Good. In this case, it is determined whether a usable group is issued based on the regularity of the ticket number (for example, the first several digits). In addition, when the ticket number information is transmitted to the management server 2, it may be determined whether or not it is issued by an organization that can be used in the management server 2.

1: Taximeter 2: Management server 3: PC
10: Taximeter body 11: CPU
11a: calculation unit 11b: ticket data analysis unit (validity determination means)
11c: End determination unit (end determination means)
11d: Output unit (output means)
12: RAM
12a: ticket settlement data storage unit (storage means)
13: ROM
14: Clock IC
15: Non-contact R / W / I / F
16: Display 17: Wireless communication unit (communication means)
18a to 18c: I / F
20: GPS receiver 30: ETC vehicle-mounted device 40: Bar code reader (reading means)
B: Barcode C: Taxi ticket I: Internet line MC: Memory card

Claims (3)

A taximeter that calculates and displays a taxi fare according to the travel distance to the destination specified by the passenger and the stop time in the rented state,
Reading means for reading the ticket information from a bar code including ticket information for determining whether or not the ticket is valid written on the taxi ticket;
Valid judgment means for judging whether the ticket is valid based on the ticket information read by the reading means;
A communication means capable of transmitting and receiving information to and from the management server wirelessly,
The communication means includes
Sending ticket number information contained in the ticket information read by the reading means to the management server;
Receiving a determination result of whether the ticket indicated by the ticket number is used, which is determined by the management server;
The ticket information includes type information indicating a taxi company that can use the taxi ticket, and determination information of at least one of expiration date information indicating an expiration date that can use the taxi ticket,
The validity determination means determines whether the ticket is valid based on the determination information without passing through the communication means after ticket number information is transmitted to the management server by the communication means, and then It is determined whether the ticket is valid based on the determination result received by the communication means.
Taximeter characterized by that . The ticket information, the taxi boarding area and the getting off place of passengers by using the ticket, the taxi transit area from the boarding place to the getting off place, the taxi settlement amount for using the ticket, and the taxi with the ticket Storage means for storing at least one piece of information on a settlement date using
An end determination means for determining the end of taxi operation,
An output means for outputting the at least one information stored in the storage means when the end of business is judged by the end judgment means;
The taximeter according to claim 1, further comprising: Taximeter according to claim 1 or claim 2 ,
A management server that transmits and receives information via the taximeter and the communication means,
The management server receives the ticket number information included in the ticket information read by the reading unit, and determines whether the received ticket number is included in the stored used ticket number, It is determined whether the taxi ticket indicated by the received ticket number has been used. If it is determined that the taxi ticket has not been used, the fact is transmitted to the taximeter and the received ticket number is stored as the used ticket number. Taximeter system characterized by that.