Vehicle Fare Settlement System

Abstract

To provide a vehicle fare settlement system and a vehicle fare settlement apparatus configured to automatically calculate a fare for a vehicle related to an electronic settlement by using one or both of a predetermined code label presented on a mobile terminal and an IC tag registered in advance in association with the predetermined code label.SOLUTION: A vehicle fare settlement system 1 includes: a mobile terminal 2 which can present a code label CL formed by coding code label information including a user ID when a user U gets on and gets off from a vehicle M; a code label / IC tag read terminal 3 which is mounted on the vehicle M and reads the presented code label or reads a presented IC tag F registered in advance in association with the code label CL; a vehicle fare settlement apparatus 4 which is mounted on the vehicle M and automatically calculates a fare by detecting a GPS signal on the basis of the read information; and a management center server 6 which manages a history of use of the vehicle M for both code label CL and IC tag F presented, to be transmitted to the mobile terminal 2.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a vehicle fare payment system and a vehicle fare payment device that automatically calculates vehicle fares related to electronic payments for transportation services. [Background technology]

[0002] When a user uses a vehicle such as a bus, taxi, or train, the user pays a fare according to the distance traveled by cash, a ticket, an IC (Integrated Circuit) card, etc. In recent years, in addition to cash, payment by electronic money, credit card, etc. has also become common as a method of paying fares.

[0003] However, when a user uses a vehicle such as a bus, taxi, or train, they pay a fare according to the distance traveled. However, there are often problems such as the fare becoming unknown due to "lost tickets," or users being unable to identify themselves after the fact due to "hit and run" or "impersonation," resulting in losses.

[0004] Incidentally, a settlement system that enables a user who has received a transportation service to quickly complete payment of a fare has been disclosed (see, for example, Patent Document 1).

[0005] The settlement system disclosed in Patent Document 1 comprises a fare meter and a management terminal installed in a taxi that outputs transaction information related to transportation services, and a host terminal that acquires user information and transaction information from a user terminal that acquires the transaction information, and acquires fare information from the fare meter that can be linked to the user information, and the management terminal installed in the taxi has a management display unit that displays the transaction information as a QR code (registered trademark) so that it can be read by the user terminal.

[0006] The settlement system disclosed in Patent Document 1 is a settlement technology that allows a user who has received a transportation service to quickly complete payment of the fare, and has a management display unit that displays transaction information as a QR code (registered trademark), which allows the user terminal to make electronic payments via a host terminal, but it cannot solve the above problem. That is, since the user terminal does not present the QR code (registered trademark), user information cannot be identified from the QR code (registered trademark) itself. In addition, the QR code (registered trademark) issued by the payment maker's application only contains information for payment, and the QR code (registered trademark) is updated after a certain period of time has passed, so even if transaction information such as the fare, such as where to get on and off, is displayed as a QR code (registered trademark), the user terminal cannot be identified.

[0007] In addition, users desire a system that allows them to use the system with confidence, since the freight charges for transactions related to transportation services are reliably calculated based on the distance or time used, while maintaining the confidentiality of the users.

[0008] In view of this, a vehicle fare calculation system has been disclosed that enhances the security of transactions related to transportation services and is also convenient for users (see, for example, Patent Document 2).

[0009] The vehicle fare calculation system disclosed in Patent Document 2 comprises a mobile terminal used by a user that enables the user to present a code label encoded with user information when getting on or off the vehicle, a code label reading terminal that is mounted on the vehicle and reads the code label from the mobile terminal to extract the user information, a GPS receiving function that is mounted on the vehicle and receives GPS signals to obtain the vehicle's current location information and current date and time information, and a vehicle fare payment device that has a fare calculation function that detects the location information and date and time information at the time the user gets on the vehicle and the location information and date and time information at the time the user gets off the vehicle, automatically calculates a predetermined fare for a transaction related to a transportation service, and controls so that it is automatically displayed on a designated fare display.

[0010] In other words, in the "vehicle fare calculation system" disclosed in Patent Document 2, a user displays a code label using a dedicated application (also referred to as the "TicketQR" app in this specification) on a mobile terminal, and the vehicle fare is automatically calculated by presenting the code label when the user gets on or off the vehicle, and the automatically calculated fare is paid by any settlement method, such as cash, a boarding ticket, or an IC card. Therefore, as a suitable form of use of the settlement method in the "vehicle fare calculation system" disclosed in Patent Document 2, a demonstration experiment of a "vehicle fare payment system" that enables electronic payment of fares on a dedicated application ("TicketQR") began on December 1, 2020 in preparation for practical application, and in addition, practical application began on October 1, 2021 (for example, see Non-Patent Document 1). [Prior art documents] [Patent documents]

[0011] [Patent Document 1] JP 2020-74146 A [Patent Document 2] Patent Publication No. 2022-18823 [Non-patent literature]

[0012] [Non-Patent Document 1] “QR Code (registered trademark) payment (TicketQR)”, [online], Ueda Bus Online, [searched on August 1, 2022], Internet〈URL:www.uedabus.co.jp / QR.html〉 Summary of the Invention [Problem to be solved by the invention]

[0013] The "vehicle fare calculation system" disclosed in Patent Document 2 and the "vehicle fare payment system" disclosed in Non-Patent Document 1 above allow users to present a code label using a dedicated application ("TicketQR" app) on a mobile terminal, and the vehicle fare for the transportation service is automatically calculated by the user presenting the code label when entering or exiting the vehicle, thereby improving the safety and convenience of transactions. In particular, the "vehicle fare payment system" disclosed in Non-Patent Document 1 allows electronic payment of fares on the dedicated application ("TicketQR"), further improving the safety and convenience of transactions.

[0014] However, with the "Vehicle fare payment system" disclosed in Non-Patent Document 1, if a user does not carry a mobile terminal that uses a dedicated application (the "TicketQR" app) or if the mobile terminal is not charged enough and does not work, the "Vehicle fare payment system" cannot be used at all, and in that case the only way to use the vehicle is to use a different payment method that is not related to the "Vehicle fare payment system" (cash or a so-called "transportation IC card", etc.).

[0015] For this reason, there is a demand for a new "vehicle fare payment system" that can automatically calculate vehicle fares for electronic payments for transportation services based on a dedicated application (the "TicketQR" app), even if the user does not carry a mobile terminal that uses the dedicated application (the "TicketQR" app) or if the mobile terminal is not fully charged and does not work.

[0016] Therefore, in consideration of the above-mentioned problems, the object of the present invention is to provide a vehicle fare payment system and a vehicle fare payment device that automatically calculates vehicle fares related to electronic payments for transportation services based on a dedicated application even when a user does not carry or is unable to operate a mobile terminal that uses the dedicated application. [Means for solving the problem]

[0017] The vehicle fare payment system of the present invention is a vehicle fare payment system that automatically calculates vehicle fares related to electronic payments for transportation services, and includes a mobile terminal used by a user that enables the user to present a code label in which code label information including at least a user ID is encoded when the user gets on or off the vehicle, a code label / IC tag reading terminal that is mounted on the vehicle and is capable of reading the code label presented by the mobile terminal used by the user and extracting the code label information, and is also capable of reading an IC tag that is registered in advance in association with the code label and presented by the user and extracting unique IC tag identification information, a GPS receiving function unit that is mounted on the vehicle and receives a GPS signal to obtain current location information and current date and time information of the vehicle based on reception of either the code label information or the IC tag identification information extracted by the code label / IC tag reading terminal, and a vehicle fare payment system that automatically calculates vehicle fares related to electronic payments for transportation services, and includes a mobile terminal used by the user that enables the user to present a code label in which code label information including at least a user ID is encoded when the user gets on or off the vehicle, a code label / IC tag reading terminal that is mounted on the vehicle and is capable of reading the code label presented by the mobile terminal used by the user and extracting the code label information, and an IC tag reading terminal that is registered in advance in association with the code label and extracts unique IC tag identification information, a GPS receiving function unit that is mounted on the vehicle and receives a GPS signal to obtain current location information and current date and time information of the vehicle based on reception of either the code label information or the IC tag identification information extracted by the code label / IC tag reading terminal, and and a fare calculation unit that detects location information and date and time information at the time the user boards the vehicle and location information and date and time information at the time the user disembarks, and controls the automatic calculation of a predetermined fare for a transaction related to the transportation service; and a management center server that manages the registration of the code label information and the linked registration of the IC tag identification information to the code label information so as to enable matching of the code label information and the IC tag identification information from the vehicle fare payment device, and stores user usage information of transactions related to transportation services for one or more user IDs for a certain period of time for each vehicle in order to manage the usage history of the vehicle whether the user presents the code label or the IC tag, and executes a user usage information notification process that notifies the mobile terminal corresponding to the user ID as usage history each time the user usage information is updated on a user ID basis.

[0018] In addition, in the vehicle fare payment system of the present invention, the code label is purchased and acquired in advance so that it can be displayed on a dedicated application launched on the mobile terminal, and indicates one of the following types of tickets: a one-time payment for making electronic payment each time, a commuter pass purchased and acquired with prepaid electronic payment which allows the vehicle to be used freely for a specified period of time, a multiple-use ticket purchased and acquired with prepaid electronic payment which allows the vehicle to be used for the number of times it is used, and a prepaid ticket which is paid for by prepaid electronic payment when the vehicle is used within the amount charged by advance electronic payment, and the IC tag is configured so that only one of the code labels can be registered in conjunction with the management center server, and one of the code labels is configured so that one or more IC tags can be registered in conjunction with the management center server.

[0019] In addition, in the vehicle fare payment system of the present invention, the vehicle fare payment device further has a user usage information management control unit that manages user usage information of transactions related to transportation services of one or more user IDs using the vehicle as a user usage information table for a certain period of time after the fare calculation unit calculates the fare, and a gateway function unit that controls communication with the management center server, and the user usage information management control unit, in cooperation with the gateway function unit, has the function of sending the user usage information whose history is managed for the vehicle to the management center server sequentially each time it is updated, or periodically, or in response to a request from the management center server, and storing the user usage information for a certain period of time.

[0020] In addition, in the vehicle fare payment system of the present invention, the gateway function unit, when the code label requires electronic payment when the vehicle is used, automatically, or after an acceptance response to a payment confirmation to the mobile terminal, performs processing to request electronic payment of the fare calculated by the fare calculation unit to a payment company server selected by the user and complete the electronic payment, and is further characterized by having a payment request processing unit that causes the user usage information management control unit to historically manage the fare and user usage information related to the electronic payment.

[0021] The vehicle fare payment device of the present invention is a vehicle fare payment device in the vehicle fare payment system of the present invention, and comprises: a GPS receiving function unit that receives a GPS signal to obtain current location information and current date and time information of the vehicle based on reception of either the code label information or the IC tag identification information extracted by the code label / IC tag reading terminal; a fare calculation unit that detects location information and date and time information at the time the user gets on the vehicle and location information and date and time information at the time the user gets off the vehicle, and controls to automatically calculate a predetermined fare for a transaction related to the transportation service; a user usage information management control unit that historically manages user usage information of transactions related to the transportation service of one or more user IDs that have used the vehicle as a user usage information table for a certain period of time after the fare calculation unit calculates the fare; and a gateway function unit that controls communications with the management center server, and the gateway function unit notifies the management center server of the usage of the code label information. The device has a usage eligibility determination processing unit that performs a comparison regarding eligibility, a linkage determination processing unit that performs a comparison with the management center server regarding the linkage registration of the IC tag identification information against the code label information, and when the code label requires electronic payment when using the vehicle, for the fare calculated by the fare calculation unit, automatically or after an acceptance response to a payment confirmation to the mobile terminal, performs a process to request electronic payment of the fare to a payment company server selected by the user and complete the electronic payment, and has the user usage information related to the fare and electronic payment managed in the user usage information management control unit as a history, and the user usage information management control unit has a function of working in cooperation with the gateway function unit to send the user usage information whose history is managed for the vehicle to the management center server sequentially each time it is updated, or periodically, or in response to a request from the management center server, and storing the user usage information for a certain period of time. Effect of the Invention

[0022] According to the present invention, the vehicle fare for electronic payment for transportation services based on a dedicated application running on a mobile terminal is automatically calculated by using either or both of a specific code label presented on the mobile terminal and an IC tag previously registered in association with the specific code label, so that even if a user does not carry a mobile terminal that uses the dedicated application or is unable to operate the mobile terminal, the vehicle can be used in a manner that ensures high transaction security, and the user's convenience is further improved compared to the past. Therefore, according to the present invention, the user's convenience is improved and the use of the vehicle fare payment system according to the present invention is promoted. [Brief description of the drawings]

[0023] [Figure 1] 1 is a block diagram showing a schematic configuration of a vehicle fare payment system according to an embodiment of the present invention; [Diagram 2] 1 is a block diagram showing a schematic configuration of a vehicle fare payment device and a mobile terminal in a vehicle fare payment system according to an embodiment of the present invention. [Diagram 3] 1A and 1B are diagrams showing examples of code label types and code label information, and examples of IC tag types and IC tag identification information, which are registered and set in a code label management server for each user in a vehicle fare payment system according to one embodiment of the present invention. [Figure 4] 1 is a diagram showing an example of a linkage registration information table in an IC tag linkage management server in a vehicle fare payment system according to one embodiment of the present invention; [Diagram 5] 4 is a flowchart showing an example of system operation when a vehicle is used with a code label in the vehicle fare payment system of one embodiment according to the present invention. [Figure 6] 4 is a flowchart showing an example of system operation when a vehicle is used with an IC tag in the vehicle fare payment system of one embodiment according to the present invention. [Figure 7] 1 is a diagram showing an example of a user usage information table in a vehicle fare payment device in a vehicle fare payment system according to one embodiment of the present invention; [Figure 8]1 is a diagram showing an example of a user usage information table in a code label management server in a vehicle fare payment system according to an embodiment of the present invention; FIG. [Figure 9] 1 is a diagram showing an example of a user usage information table in a management center server that integrates a code label management server and an IC tag linkage management server in an embodiment of a vehicle fare payment system according to the present invention; [Figure 10] 1(a) and (b) are diagrams showing typical examples of fare calculation and electronic payment in a vehicle fare payment system according to an embodiment of the present invention, when a user uses an IC tag to board and disembark from a vehicle, respectively. [Figure 11] 13(a) and 13(b) are diagrams showing typical examples of fare calculation and electronic payment in a vehicle fare payment system according to one embodiment of the present invention, when a user boards a vehicle using a code label that the user has purchased and presented on a mobile terminal, and disembarks using an IC tag that has been registered in association with that code label. [Figure 12] 4 is a flowchart showing a first example of the operation of linking and registering a code label and an IC tag in the vehicle fare payment system according to one embodiment of the present invention. [Figure 13] 10 is a flowchart showing a second operational example of linked registration of a code label and an IC tag in the vehicle fare payment system according to one embodiment of the present invention. [Figure 14] 13A to 13E are diagrams showing examples of list displays on a mobile terminal relating to registered and linked IC tags for each type of code label in a vehicle fare payment system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] Hereinafter, a vehicle fare payment system 1 according to an embodiment of the present invention will be described with reference to the drawings. Fig. 1 is a block diagram showing a schematic configuration of the vehicle fare payment system 1 according to an embodiment of the present invention. Fig. 2 is a block diagram showing a schematic configuration of a vehicle fare payment device 4 and a mobile terminal 2 in the vehicle fare payment system 1 according to an embodiment of the present invention.

[0025] [Vehicle fare payment system] The vehicle fare payment system 1 shown in FIG. 1 includes a mobile terminal 2 used by a user U, a code label / IC tag reading terminal 3 that is mounted on a vehicle (a bus in the illustrated example) M that is the subject of a transaction related to a transportation service used by the user U and that is linked to an operation panel 5 that also serves as a fare display (not illustrated), a vehicle fare payment device 4 that can wirelessly communicate with various servers (a management center server 6 and a payment company server 7), and a management center server 6. In this example, a bus is used as an example of the vehicle M, but the vehicle that is the subject of a transaction related to a transportation service, such as a taxi or a train, may also be used. In addition, the management center server 6 (also referred to as the "TicketQR server" in this specification) is composed of a code label management server 61 and an IC tag linkage management server 62, and the code label management server 61 and the IC tag linkage management server 62 can be integrated, but in this example, for convenience of explanation, an example in which the code label management server 61 and the IC tag linkage management server 62 are configured separately will be mainly explained.

[0026] In the vehicle fare payment system 1, when getting on or off a vehicle M, a user U can hold a code label CL, which is displayed on a mobile terminal 2 and contains encoded code label information including at least a user ID (identifier) ​​that identifies the user U, over a code label / IC tag reading terminal 3 to have it read. In this example, the code label CL is a two-dimensional code label in an existing format such as a QR code (registered trademark), but it may also be a one-dimensional code label in an existing format such as a barcode.

[0027] The code label CL is purchased and acquired from the website related to the vehicle fare payment system 1 that operates the code label management server 61 after the user U performs user registration for the code label management server 61 that manages the vehicle fare payment devices 4 mounted on each of the vehicles M, for example, by using the mobile terminal 2 to access the website related to the vehicle fare payment system 1. In user registration, the user U first uses the mobile terminal 2 to access the website related to the vehicle fare payment system 1 and downloads a dedicated application ("TicketQR" application). Then, the user U executes user registration on the dedicated application and transmits personal information including at least the user name and an email address specifying the mobile terminal 2 to the code label management server 61 via the access to the website related to the vehicle fare payment system 1. Alternatively, instead of downloading the dedicated application for the mobile terminal 2, the user U presents the mobile terminal 2 by accessing the website related to the vehicle fare payment system 1, and for user registration, uses any communication terminal (including a personal computer) to access the website related to the vehicle fare payment system 1 and transmits personal information including at least the user name and an email address specifying the mobile terminal 2 to the code label management server 61. In addition, the code label CL itself may be generated by a system on a website related to the vehicle fare payment system 1 and provided on a dedicated application, and registered and managed in the code label management server 61, or the dedicated application may have a function to generate the code label CL and have it registered and managed in the code label management server 61.

[0028] When the code label management server 61 acquires the personal information, it assigns a unique identification number to the user and manages it as a user ID (identifier), and replies to the email address with URL information (with an access time limit) for confirming the user registration information corresponding to the user ID. Therefore, the user ID can identify the personal information including the user name and the email address specifying the mobile terminal 2. Then, the user U accesses the URL specified by the email address to confirm the user registration information, and sends a notification of approval of the user registration to the code label management server 61. Next, after user registration, the user U performs operations on a dedicated application (the "TicketQR" application) to set the payment company that will perform electronic payment (i.e., to specify the payment company server 7 to be used for payment of the code label CL) and to purchase and acquire a code label CL corresponding to a specified ticket (described later with reference to FIG. 3(a)). In response to the settings of the payment company performing the electronic payment and the user's operation to purchase and acquire a code label CL corresponding to the specified ticket, the code label management server 61 generates a code label CL indicating at least the user ID corresponding to the specified ticket with an expiration date after confirming the user registration (user authentication), transmits the code label CL so that it can be used by the mobile terminal 2, and has the mobile terminal 2 hold the code label CL. If the expiration date set for the code label CL has expired, the code label management server 61 invalidates the code label CL.

[0029] In this embodiment, as shown in Fig. 3(a), five types of tickets (Type 0 to Type 4) are assumed for the type of code label CL. Fig. 3(a) shows an example of the type of code label CL and code label information registered and set in the code label management server 61 for each user related to the vehicle fare payment system 1 of this embodiment. As described above, each of the five types of tickets can be purchased and acquired by downloading a dedicated application ("TicketQR" app) to the mobile terminal 2 used by the user U, or by displaying the dedicated application on the mobile terminal 2 by accessing a website related to the vehicle fare payment system 1, and using the dedicated application ("TicketQR" app) as a function.

[0030] Specifically, there are "pay-per-use" (Type 0, 1) for making electronic payment each time the vehicle M is used, "commuter pass" (Type 2) purchased and acquired by prepaid electronic payment that allows the vehicle M to be used freely for a specific period, such as 3 months, 6 months, or 1 year, in a manner that makes each specific period identifiable, "ticket" (Type 3) purchased and acquired by prepaid electronic payment that allows the vehicle M to be used for a specific number of times, such as 10 times, 20 times, or 30 times, in a manner that makes each number of times identifiable, and "prepaid ticket" (Type 4) that allows prepaid electronic payment when the vehicle M is used within the range of an amount charged by advance electronic payment, such as 2000 years, 3000 yen, or 5000 yen. A code label ID that identifies each of Types 1 to 4 is assigned and is included in the code label information together with the user ID. Therefore, by holding the code label CL displayed on the mobile terminal 2 over the code label / IC tag reading terminal 3 to read it, at least the "user ID" is specified, and in addition, the code label information that identifies whether it is a "pay-per-use", "commuter pass", "ticket coupon", or "prepaid ticket" is extracted by the code label / IC tag reading terminal 3. In this embodiment, as a suitable example that allows the user U to purchase and acquire multiple code labels CL of the same type, although this is not essential, the code label information includes at least the user ID and also includes a ticket issuing number that makes it possible to identify each code label CL. Here, the code label information may be one in which the code label ID is omitted so that the ticket issuing number can identify each code label CL, or the code label information may be one in which the ticket issuing number and the code label ID are distinguished. The code label CL purchased and acquired by the user U is managed by the code label management server 61 together with a predetermined expiration date based on the user ID registered by the user.

[0031] Thus, the user U can purchase and acquire a code label CL that can identify five types of tickets (Type 0 to Type 4) from a website related to the vehicle fare payment system 1 that functions the code label management server 61 by performing an operation to purchase and acquire a code label CL corresponding to a predetermined ticket, and can display the code label CL on the mobile terminal 2. The code label CL itself has an expiration date and can be read by the code label / IC tag reading terminal 3. However, the only code label information that is read is the code label information that identifies at least the above-mentioned "user ID" and also identifies whether the ticket is a "pay-per-use ticket," "commuter pass," "ticket coupon," or "prepaid ticket" together with the ticket issuing number. Therefore, the confidentiality of the user U's personal information is maintained, and the security of the transaction is also maintained. Note that the code label information may be further encoded and embedded as user information in the code label CL to further enhance the confidentiality of the personal information and the security of the transaction. As described above, this code label information is originally designed to identify the mobile terminal 2 by the user ID, but device information for identifying the mobile terminal 2 may also be added to this code label information for device authentication of the mobile terminal 2.

[0032] In the present invention, a user U can register one or more IC tags F in association with each code label CL that he or she has purchased, so that the user U can use the vehicle M using the registered associated IC tag F instead of using the code label CL.

[0033] The IC tag F according to the present invention may be any as long as it can be read by a code label / IC tag reading terminal 3 configured as a general IC tag reader. The IC tag identification information read from the IC tag F by the code label / IC tag reading terminal 3 is unique information that can be distinguished from other IC tags. The IC tag F is generally known as an "IC card", and there are also other types that are not card-shaped but key holder-shaped (for example, a character key holder that allows the use of public transportation in Taiwan). For example, FIG. 3(b) shows the types of IC tags F and examples of IC tag identification information read from the IC tag F. Current IC tags can be broadly divided into "transportation IC cards" related to payments for use of public transportation and "distribution IC cards" related to payments at supermarkets, convenience stores, online shops, etc., but there are also other types, such as attendance management, attendance confirmation (for children, students, etc.), ID card authentication printer systems, stamp rallies, store visit point systems, book lending, reception management, screen saver lock, PC lock door entry / exit, PC login, etc. The IC chips stored in these IC tags F store IC tag identification information that conforms to various standards. As shown in FIG. 3(b), they can be broadly divided into types that store IC tag identification information that conforms to RFID (Radio Frequency Identification) including the HF and UHF bands, and types that store IC tag identification information that conforms to NFC (Near Field Communication).

[0034] 4, the IC tag linkage management server 62 registers and manages, for each user ID, IC tag identification information uniquely stored in one or more IC tags F to be linked with the code label information of each code label CL purchased and acquired by the user U and registered in the code label management server 61. Note that the operation of linking and registering any one or more IC tags with each code label CL purchased and registered in the code label management server 61 by the user U will be described in detail later with reference to FIGS.

[0035] Therefore, in the vehicle fare payment system 1 of this embodiment, when getting on or off a vehicle M, instead of holding the code label CL that has been purchased and acquired and registered in the code label management server 61 over the code label / IC tag reading terminal 3, the user U can hold the IC tag F that stores the IC tag identification information that has been registered in association with the code label CL over the code label / IC tag reading terminal 3 to have it read.

[0036] The code label / IC tag reading terminal 3 has a function of transmitting code label information read from the code label CL to the vehicle fare payment device 4 by wired or short-range wireless communication (LAN, etc.), and a function of transmitting IC tag identification information read from an IC tag F used by a user U that has been registered for linkage to the vehicle fare payment device 4 by wired or short-range wireless communication (LAN, etc.). The code label / IC tag reading terminal 3 is also configured to work in conjunction with an operation panel 5 operated by the driver of the vehicle M, and the operation of the code label / IC tag reading terminal 3 can be controlled by operating the operation panel 5. The vehicle fare payment device 4 also controls the link between the operation panel 5 and the code label / IC tag reading terminal 3, and can display a fare display, which will be described in detail later, and a usability notification or an error notification based on usability matching, on the operation panel 5 and the code label / IC tag reading terminal 3.

[0037] This code label / IC tag reading terminal 3 can use a general-purpose device that can read two-dimensional or one-dimensional code labels CL in an existing format and also read IC tags F. Note that the code label / IC tag reading terminal 3 is not limited to a device that integrates a device for reading code labels CL and a device for reading IC tags F, and may be configured as separate devices for each.

[0038] The vehicle fare payment device 4 is capable of wireless communication with various servers (the management center server 6 consisting of the code label management server 61 and the IC tag linkage management server 62, and the payment company server 7) via a wireless communication network. In particular, the vehicle fare payment device 4 has a GPS receiving function that receives GPS signals indicating GPS position information and GPS date and time information from multiple GPS (Global Positioning System) satellites (not shown) to obtain the current position information and current date and time information of the vehicle M. Thus, the vehicle fare payment device 4 determines the position information and date and time information at the time of boarding and disembarking when it receives the code label information or IC tag identification information from the code label / IC tag reading terminal 3 by its GPS receiving function when the user U boards and disembarks the vehicle M. In addition, the vehicle fare payment device 4 has a fare calculation function that automatically calculates the fare of the vehicle M, which is predetermined for a transaction related to a transportation service, by detecting the position information and date and time information at the time of boarding the vehicle M of the user U and the position information and date and time information at the time of disembarking.

[0039] The vehicle fare payment device 4 has a gateway (GW) function having a function of performing a use availability determination process by matching the code label information transmitted from the code label / IC tag reading terminal 3 or the code label information linked to the IC tag identification information with the code label management server 61, a function of performing a link determination process by matching the IC tag identification information with the IC tag linkage management server 62, a function of performing a payment request process to make a fare payment request to the payment company server 7 designated by the registered user U for the code label CL purchased and acquired by the user U who requires electronic payment when using the vehicle M, and to execute the payment of the fare by making the electronic payment, and a function of performing linkage registration process between the code label CL and the IC tag according to instructions from the operation panel 5. Note that, for the code labels CL of "commuter passes" and "tickets", these are tickets that have already been purchased on a dedicated application ("TicketQR" app), and therefore there is no need to request the payment company server 7 for the electronic payment of the fare, and therefore the payment request process in the gateway (GW) function is targeted at electronic payments corresponding to "pay as you go" or "prepaid tickets".

[0040] The vehicle fare payment device 4 also performs interlocking control to transmit and display a usability notification relating to the usability determination of the code label CL, a fare information notification indicating the fare, and a payment completion notification indicating the completion of payment to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown), and has a function of managing user usage information relating to the use of the vehicle M within its own device and transmitting it to the code label management server 61 to be managed as user usage information. The vehicle fare payment device 4 is configured to enable a user U who requires electronic payment when using the vehicle M to pay the fare by electronic payment for the purchased and acquired code label CL, but also performs interlocking control to transmit and display a notice of the error to the code label / IC tag reading terminal 3 and the operation panel 5 if an error occurs in the usability determination process, the linkage determination process, or the electronic payment.

[0041] Here, the vehicle fare payment device 4 has a user usage information management control function that manages user usage information of transactions related to transportation services of one or more user IDs using the vehicle M, which is the vehicle itself, as a user usage information table in the memory unit 42 for a certain period of time after fare calculation (and after electronic payment if electronic payment is required when using vehicle M), and has a function that cooperates with the gateway (GW) function to send the user usage information to the code label management server 61 sequentially each time it is updated, or periodically, or in response to a request from the code label management server 61, and stores the user usage information for a certain period of time. The code label management server 61 manages the registration of code label information (and manages the linked registration of IC tag identification information for code label information in cooperation with the IC tag linkage management server 62) so as to enable matching of the code label information and the IC tag identification information from the vehicle fare payment device 4, and has a function of storing the user usage information for a certain period of time for each vehicle M in order to manage the usage history of the vehicle M when the user U presents either the code label CL or the IC tag F, and executing a user usage information notification process to notify the mobile terminal 2 of the usage history each time it is updated. From the viewpoint of increasing the confidentiality of personal information and the security of transactions, it is preferable that the vehicle fare payment device 4 and the code label management server 61 have a function of automatically erasing the user usage information that has been in effect for a certain period of time since the fare was calculated.

[0042] According to this vehicle fare payment system 1, the fare for vehicle M for transportation services can be automatically calculated and electronically paid by using either or both of a predetermined code label CL and an IC tag F presented on a mobile terminal 2. When a user U uses vehicle M, there is no risk of the fare becoming unknown due to "lost ticket," and even if a problem occurs due to "hit and run" or "impersonation," an unscrupulous user U can be identified after the fact, which leads to the reduction of losses. Furthermore, a legitimate user U can use the system with peace of mind, since the fare for a transaction related to transportation services is reliably calculated based on the distance or time used, while the confidentiality of the user U is maintained.

[0043] [Mobile terminal] 2, the mobile terminal 2 includes a control unit 20, a terminal UI (user interface) 21, a storage unit 22, a display unit 23, and a communication unit 24. In addition, the mobile terminal 2 preferably, but not necessarily, further includes an IC tag reading unit 25 that enables reading of IC tag identification information of the IC tag F when linking and registering the code label CL and the IC tag F.

[0044] The terminal UI 21 is a human-machine user interface that enables the user U to operate the mobile terminal 2 .

[0045] The storage unit 22 is a memory that stores various application programs and data used by the mobile terminal 2 .

[0046] The display unit 23 is a display that displays various applications and data used in the mobile terminal 2.

[0047] The communication unit 24 is a functional unit that performs wireless communication with other devices, and in this example, includes wireless communication with the code label management server 61 when performing user registration settings for use of this system on a dedicated application (the "TicketQR" app), purchasing and acquiring a code label CL, viewing usage history and registration information, etc., and wireless communication with the payment company server 7 when specifying and setting a payment company that performs electronic payment using the code label CL, and as a preferred example, wireless communication with the IC tag linkage management server 62 when registering the linkage between the code label CL and an IC tag, and has the function of communicating with these various servers (the code label management server 61 that manages multiple vehicle fare payment devices 4, the IC tag linkage management server 62, and the payment company server 7) via a wireless communication network (e.g., the Internet).

[0048] Here, as a preferred example that is easy to use, an example will be described in which a dedicated application ("TicketQR" app) 201 has already been installed. However, as a variation thereof, as described above, a dedicated application ("TicketQR" app) 201 may be presented by accessing a website related to the vehicle fare payment system 1, thereby producing the same functions as if the dedicated application had been installed.

[0049] The control unit 20 can be composed of a central processing unit (CPU), and by reading and executing a dedicated application ("TicketQR" app) 201 stored in a specified storage area of ​​the memory unit 22 via the terminal UI 21, it causes each of the functional units, namely a user registration unit 202, a code label acquisition management unit 203, and a code label display control unit 204, to function, and preferably, although not essential, further causes a linked registration function unit 205 to function to link and register the code label CL and the IC tag F.

[0050] The user registration unit 202 is a functional unit that performs user registration in the code label management server 61 by user operation on the dedicated application 201 via the communication unit 24 as described above.

[0051] The code label acquisition management unit 203 is a functional unit that purchases and acquires code labels CL that can identify five types of tickets (Type 0 to Type 4) in this example from a website dedicated to this system linked to the code label management server 61 by user operation on the dedicated application 201, and manages the purchased and acquired code labels CL as a list. In this example, the code label acquisition management unit 203 stores and manages the list in the storage unit 22, but as a modified example, the list may be read by accessing the code label management server 61 and the IC tag linkage management server 62 without storing the list in the storage unit 22, and may be managed by forming the list. Note that, although details will be described later with reference to FIG. 14, in this embodiment, one or more IC tags F desired by the user U can be linked and registered with each of the purchased and acquired multiple code labels CL, but one IC tag F can be linked and registered with only one code label CL, and as a function of the dedicated application 201, it can be displayed as a list on the display unit 23 of the mobile terminal 2.

[0052] The code label display control unit 204 is a functional unit that displays, on the display unit 23, a code label CL that can identify five types of tickets (Type 0 to Type 4) after user registration and purchase acquisition by the code label acquisition management unit 203, in response to a user operation on the dedicated application 201.

[0053] The linkage registration function unit 205, the details of which will be described with reference to Fig. 13, is a function unit that executes linkage registration between the code label information of a predetermined code label CL that has been purchased and acquired and the IC tag identification information of an IC tag F desired by a user U that has been read using the mobile terminal 2 on the dedicated application 201, and registers the linkage in the IC tag linkage management server 62. Normally, if the mobile terminal 2 is configured as a smartphone, an IC tag reading unit 25 capable of reading the IC tag identification information of the IC tag F is mounted, and the IC tag reading unit 25 can be used when the user U links and registers the code label CL that has been purchased and acquired and the IC tag F. Even if the mobile terminal 2 does not have the IC tag reading unit 25 mounted thereon, an external general-purpose IC tag reader capable of reading the IC tag identification information of the IC tag F may be connected to the mobile terminal 2 and used. After completing the linkage registration, the IC tag linkage management server 62 generates a linkage registration completion notification indicating the linked code label CL and IC tag F and notifies the mobile terminal 2 of the same, and the mobile terminal 2 manages the purchased and acquired code labels CL, including the linkage registration information of the IC tag F, as a list on the dedicated application 201 using the code label acquisition management unit 203.

[0054] As a result, when getting on or off vehicle M, user U can present the code label CL displayed on mobile terminal 2 by holding it over the code label / IC tag reading terminal 3 to have the code label information read. Also, when getting on or off vehicle M, user U can present the IC tag F that has been registered in association with the purchased code label CL by holding it over the code label / IC tag reading terminal 3 to have the IC tag identification information read.

[0055] [Vehicle fare payment device] As shown in FIG. 2, the vehicle fare payment device 4 includes a control unit 40, a communication unit 41, a storage unit 42, a GPS receiving unit 43, an interlocking control unit 44, and a communication unit 45.

[0056] The communication unit 41 is a functional unit that communicates with the code label / IC tag reading terminal 3 via wired or short-range wireless communication (LAN, etc.), and has a function of receiving code label information obtained by reading the code label CL by the code label / IC tag reading terminal 3, and a function of receiving IC information obtained by reading the IC tag F by the code label / IC tag reading terminal 3.

[0057] The storage unit 42 is a memory that stores programs for functioning as the vehicle fare payment device 4 and various data.

[0058] The GPS receiving unit 43 is a functional unit that receives GPS signals indicating GPS position information and GPS date and time information from a plurality of GPS satellites (not shown) and acquires the current position information of the vehicle M and the current date and time information.

[0059] The interlocking control unit 44 has the function of performing interlocking control with the code label / IC tag reading terminal 3 when receiving instructions from the operation panel 5 operated by the driver of the vehicle M and performing interlocking registration between the code label information of the code label CL and the IC tag identification information of the IC tag F (described later with reference to Figure 12), using the functions of the control unit 40, and the function of performing interlocking control to send and display a usability notification regarding the determination of whether the code label CL to be used can be used, a notification regarding the determination of interlocking with the IC tag F (error notification), a fare information notification indicating the fare, and a payment completion notification indicating completion of payment to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown).

[0060] The communication unit 45 is a functional unit that performs wireless communication with other devices. In this example, the communication unit 45 uses the functions of the control unit 40 to perform wireless communication with the code label management server 61 for comparison to determine whether the code label CL can be used, to collect and update user usage information, to perform wireless communication with the IC tag linkage management server 62 for linkage matching of the IC tag F, to perform wireless communication with the user-designated and set payment company server 7 that performs electronic payment for the use of a code label CL that requires electronic payment when using the vehicle M or an IC tag F that has been linked and registered for that code label CL, and to perform wireless communication with the IC tag linkage management server 62 to accept instructions from the operation panel 5 operated by the driver of the vehicle M based on the linkage control of the linkage control unit 44 and perform linkage registration between the code label CL and the IC tag. The communication unit 45 has the function of performing mutual communication with these various servers (the code label management server 61 that manages multiple vehicle fare payment devices 4, the IC tag linkage management server 62, and the payment company server 7) via a wireless communication network (e.g., the Internet).

[0061] The control unit 40 can be composed of a central processing unit (CPU), and while the transportation service is in operation, it constantly reads and executes a program for functioning as the vehicle fare payment device 4, which is stored in a designated storage area of ​​the memory unit 42, to cause each of the functional units, the GPS receiving function unit 401, the fare calculation unit 402, the user usage information management control unit 403, and the gateway function unit 404, to function.

[0062] The GPS receiving function unit 401 is a functional unit that, when receiving usable code label information or linkable IC tag identification information from the code label / IC tag reading terminal 3 when user U gets in and out of vehicle M, causes the GPS receiving unit 43 to function, receives GPS signals indicating GPS position information and GPS date and time information from multiple GPS satellites (not shown), obtains the current position information and current date and time information of vehicle M, and determines the position information and date and time information at the time they were transmitted from the code label / IC tag reading terminal 3.

[0063] The fare calculation unit 402 is a functional unit that works in cooperation with the GPS receiving function unit 401 to detect location information and date and time information at the time when the user U boards the vehicle M, and location information and date and time information at the time when the user disembarks, and automatically calculates the predetermined fare for the vehicle M for a transaction related to the transportation service.

[0064] The user usage information management control unit 403 is a function unit that, as a function of the control unit 40, manages user usage information of transactions related to transportation services of one or more user IDs using a vehicle M, which is a vehicle identified by a vehicle ID, as a history in the storage unit 42 for a certain period after fare calculation and electronic payment as a user usage information table. In addition, the user usage information management control unit 403 has a function of transmitting the user usage information to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61, in cooperation with a gateway (GW) function unit 404 that controls communication with various servers, and storing the user usage information for a certain period. The code label management server 61 stores the user usage information for a certain period for each vehicle M, and executes a user usage information notification process that notifies the mobile terminal 2 corresponding to the user ID as a usage history each time the user usage information is updated on a user ID basis.

[0065] The gateway function unit 404 is equipped with a usage eligibility determination processing unit 4041, a linkage determination processing unit 4042, a payment request processing unit 4043, and a linkage registration processing unit 4044, and in order to function these processing units, it controls various servers (the code label management server 61 that manages multiple vehicle fare payment devices 4, the IC tag linkage management server 62, and the payment company server 7) via the communication unit 45 to communicate with each other via a wireless communication network (e.g., the Internet), causes the linkage control unit 44 to function to perform linkage control over the code label / IC tag reading terminal 3 and the operation panel 5 that also serves as a fare display (not shown), and controls the user usage information management control unit 403 to transmit the user usage information historically managed in the memory unit 42 to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61.

[0066] More specifically, the usability determination processing unit 4041 is a functional unit that performs usability determination processing by comparing the code label information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41, or the code label information linked to the IC tag identification information, with the code label management server 61 via the communication unit 45, and generates a usability notification indicating that the code label information is usable, and generates an unusable notification (error notification) indicating that the code label information is unusable, and transmits this to the code label / IC tag reading terminal 3 and the operation panel 5 via the linkage control unit 44 for display.

[0067] In addition, the linkage determination processing unit 4042 is a functional unit that performs linkage determination processing by comparing the IC tag identification information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41 with the IC tag linkage management server 62 via the communication unit 45, and if the IC tag identification information has already been registered for linkage, it obtains the registered code label information from the IC tag linkage management server 62, and if the IC tag identification information is not linked, it generates a no-linkage notification (error notification) indicating this, and transmits it to the code label / IC tag reading terminal 3 and the operation panel 5 via the linkage control unit 44 for display.

[0068] When the code label CL requires electronic payment for the fare calculated by the fare calculation unit 402 when using the vehicle, the payment request processing unit 4043 performs processing to request electronic payment of the fare to the payment company server 7 via the communication unit 45 automatically or after receiving an acceptance response for payment confirmation to the mobile terminal 2, and completes the electronic payment. When the payment request processing unit 4043 receives a payment completion notice indicating the completion of payment from the payment company server 7, it processes to transmit the notice to the code label / IC tag reading terminal 3 and the operation panel 5 also serving as a fare display (not shown) via the interlocking control unit 44 and display the notice. The control unit 40 causes the user usage information management control unit 403 to function and manage the history of the user usage information related to the fare and electronic payment in the storage unit 42, and processes to transmit the user usage information to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61. The code label management server 61 stores the user usage information for each vehicle M for a certain period of time, and whenever there is an update, notifies the mobile terminal 2 of the usage history. Note that for the code labels CL of "commuter passes" and "tickets", since these are tickets that have already been purchased on the dedicated application 201, there is no need to request electronic payment of the fare from the payment company server 7, and therefore the payment request processing unit 4043 targets electronic payment for code labels CL corresponding to "pay as you go" or "prepaid tickets".

[0069] The linked registration processing unit 4044, details of which will be described with reference to Figure 12, transitions to a linked registration mode in which the linked registration between the code label CL and the IC tag F is executed when an instruction for the linked registration mode is received from the operation panel 5 operated by the driver of the vehicle M via the interlocking control unit 44, and waits for input of the IC tag information of the IC tag F and the code label information of the code label CL related to the linked registration via the communication unit 41. Then, when the linkage registration mode is entered, the linkage registration processing unit 4044 causes the code label / IC tag reading terminal 3 to read the IC tag identification information of the IC tag F and the code label information of the code label CL in a predetermined order, and causes the usability determination processing unit 4041 to execute usability determination processing for the code label management server 61 via the communication unit 45, and then executes linkage registration for the IC tag identification information of the IC tag F and the code label information of the code label CL that have been read, via the communication unit 45, with the IC tag linkage management server 62, and after the linkage registration is completed, generates a linkage registration completion notice indicating that fact, and transmits it to the code label / IC tag reading terminal 3 and the operation panel 5 via the linkage control unit 44 to be displayed. After the linkage registration is completed, the IC tag linkage management server 62 also generates a linkage registration completion notice indicating the linked code label CL and IC tag F, and notifies the mobile terminal 2 of the linkage registration completion. The mobile terminal 2 manages, on the dedicated application 201, as a function of the code label acquisition management unit 203, the purchased and acquired code labels CL including the association registration information of the IC tag F as a list.

[0070] (System operation: When using vehicle M with code label CL) FIG. 5 is a flowchart showing an example of a system operation when a vehicle M is used with a code label CL in the vehicle fare payment system 1 according to one embodiment of the present invention.

[0071] As shown in Fig. 3(a) above, in this embodiment, code labels CL corresponding to "pay per use", "commuter pass", "ticket book", and "prepaid ticket" are assumed. In the following, for the code labels CL of "commuter pass" and "ticket book", since they are tickets already purchased on the dedicated application 201, there is no need to request electronic payment of the fare from the payment company server 7. Therefore, the use of vehicle M with a code label CL corresponding to "pay per use" or "prepaid ticket" will be described as a representative.

[0072] When a user U gets into a vehicle M, the mobile terminal 2 starts up a dedicated application 201 through an operation by the user U, and a code label CL that has been preregistered and purchased and is related to the use of the vehicle M is displayed on the display unit 23 of the mobile terminal 2. Then, when getting into the vehicle M, the user U performs an operation to present the code label CL by holding it over the code label / IC tag reading terminal 3 (step S1).

[0073] Then, the code label / IC tag reading terminal 3 reads the code label CL presented by holding it over the display unit 23 of the mobile terminal 2, extracts the code label information including at least the user ID that identifies the user U, and transmits it to the vehicle fare payment device 4 (step S2).

[0074] Next, when the vehicle fare payment device 4 receives the code label information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41, the gateway function unit 404 causes the usability determination processing unit 4041 to function, which performs usability determination processing by matching the code label management server 61 via the communication unit 45, and generates a usability notification indicating that the code label information is usable, and generates an unusable notification (error notification) indicating that the code label information is unusable, and transmits the notification to the code label / IC tag reading terminal 3 and the operation panel 5 via the interlocking control unit 44 and displays it (step S3). When an unusable notification (error notification) is generated due to expiration or other reasons, the user U cannot use the vehicle M, so the subsequent operations are not performed and the user U must perform the operations from step S1 again. Here, the subsequent operations will be described assuming that a usability notification is generated.

[0075] Next, after generating a usability notification for the code label information at the time of boarding, the vehicle fare payment device 4 causes the GPS receiving function unit 401 to function to receive GPS signals indicating GPS position information and GPS date and time information from multiple GPS satellites (not shown), and obtains the current position information and current date and time information of the vehicle M, thereby detecting the boarding position and boarding date and time, and records these in the storage unit 42 as a user usage information table together with the vehicle ID that identifies the device (own vehicle) (step S4).The user usage information management control unit 403 also has a function of working with the gateway function unit 404 that controls communication with various servers to transmit the user usage information to the code label management server 61 successively each time it is updated, or periodically, or in response to a request from the code label management server 61, and storing the user usage information for a certain period of time. Here, for ease of explanation, it is assumed that the user usage information management control unit 403 cooperates with the gateway function unit 404 to transmit the user usage information to the code label management server 61 each time it is updated, and stores the user usage information for a certain period of time.

[0076] On the other hand, when the user U gets off the vehicle M, he or she presents the same code label CL that was used when getting on by holding it over the code label / IC tag reading terminal 3 (step S5).

[0077] Then, the code label / IC tag reading terminal 3 reads the code label CL presented by holding it over the display unit 23 of the mobile terminal 2, extracts the code label information, and transmits it to the vehicle fare payment device 4 (step S6).

[0078] Next, when the vehicle fare payment device 4 receives the code label information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41, the gateway function unit 404 causes the usability determination processing unit 4041 to function, which performs usability determination processing by matching with the code label management server 61 via the communication unit 45, and verifies whether the code label information is the same as that at the time of boarding. If the code label information is the same as that at the time of boarding and the code label information is usable, a usability notification indicating that is generated, and if the code label information is unusable, a usability notification (error notification) indicating that is generated, and the process is performed so that the usability notification is transmitted to the code label / IC tag reading terminal 3 and the operation panel 5 via the interlocking control unit 44 and displayed (step S7). When the usability notification (error notification) is generated, for example, when the user U mistakenly presents a code label CL different from that at the time of boarding, the user U cannot use the vehicle M, so the subsequent operations are not performed, and the user U must perform the operations from step S5 again. Here, the subsequent operations will be described assuming that the usability notification is generated.

[0079] Next, after generating the notification of availability at the time of disembarking, the vehicle fare payment device 4 causes the GPS receiving unit 43 to function using the GPS receiving function unit 401, receives GPS signals indicating GPS location information and GPS date and time information from multiple GPS satellites (not shown), and obtains the current location information and current date and time information of the vehicle M, thereby detecting the boarding location and boarding date and time.The fare calculation unit 402 automatically calculates a predetermined fare for the transaction related to the transportation service based on the detected location information and date and time information at the time of user U boarding vehicle M and the location information and date and time information at the time of disembarking, and records this in the memory unit 42 as a user usage information table together with the vehicle ID that identifies the device (vehicle) (step S8).

[0080] Here, when the fare calculation unit 402 automatically calculates the fare, the vehicle fare payment device 4 generates a fare information notification indicating the fare, and transmits it via the interlocking control unit 44 to the code label / IC tag reading terminal 3 and the operation panel 5 which also functions as a fare display (not shown) for display. Note that the code label / IC tag reading terminal 3 is assumed to have a fare display function, but if it does not have this function, the transmission of the fare information notification to the code label / IC tag reading terminal 3 is omitted. However, the fare information is included in the user usage information, and is notified to the mobile terminal 2 from the code label management server 61 in step S10 described later.

[0081] As a function of the control unit 40, the user usage information management control unit 403 cooperates with the gateway function unit 404, which controls communication with various servers, to transmit the user usage information to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61, and has the function of storing the user usage information for a certain period of time. For ease of explanation, the user usage information management control unit 403 will be described as cooperating with the gateway function unit 404 to transmit the user usage information to the code label management server 61 each time it is updated.

[0082] Next, when the code label CL requires electronic payment when using the vehicle M for the fare calculated by the fare calculation unit 402, the vehicle fare payment device 4 automatically, or after receiving an acceptance response to confirm payment to the mobile terminal 2, functions a payment request processing unit 4043 which requests electronic payment of the fare to the payment company server 7 via the communication unit 45 and completes the electronic payment, and when it receives a payment completion notice indicating completion of payment from the payment company server 7, processes it to send it via the interlocking control unit 44 to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown) for display, and functions the user usage information management control unit 403 to manage the history of the fare and user usage information related to the electronic payment in the memory unit 42 (step S9).

[0083] In this example, since it is assumed that the code label CL corresponds to a "pay per use" or "prepaid ticket", the operation by the payment request processing unit 4043 is explained, however, for the code labels CL of a "commuter pass" and a "ticket coupon", since these are tickets that have already been purchased, it is not necessary to request electronic payment of the fare from the payment company server 7 after the fare is calculated. In this case, the operation of requesting electronic payment in step S9 is omitted.

[0084] In addition, with regard to electronic payment of the fare to the settlement company server 7 when the vehicle M is used by the code label CL corresponding to "pay per use" or "prepaid ticket", the settlement request processing unit 4043 automatically executes an electronic payment request for the fare calculated by the fare calculation unit 402 when the code label CL corresponding to "pay per use" or "prepaid ticket" requires electronic payment when the vehicle is used. Here, depending on the settlement company server 7, there may be a transaction form in which the electronic payment request is executed after "payment confirmation" for the user (i.e., the mobile terminal 2). Even in this case, in this embodiment, the settlement company server 7 does not directly request "payment confirmation" from the mobile terminal 2, but the settlement request processing unit 4043 notifies the mobile terminal 2 via the code label management server 61 to act as a proxy for the "payment confirmation" from the settlement company server 7. Then, the settlement request processing unit 4043 monitors whether the code label management server 61 receives and records an acceptance notice indicating acceptance of the "payment confirmation" notice from the mobile terminal 2, and as soon as the acceptance notice is received, the settlement company server 7 transfers the acceptance notice to the settlement company server 7 to act as a proxy.

[0085] When the code label management server 61 notifies the mobile terminal 2 of "payment confirmation", the dedicated application 201 on the mobile terminal 2 automatically starts, and the dedicated application 201 can respond with approval to the "payment confirmation". This "payment confirmation" is only for the purpose of confirming approval of the electronic payment at the payment company, and if the user U rejects the "payment confirmation" (i.e. does not respond with approval), it is recorded as "unpaid" in the code label management server 61. Thereafter, a message is displayed on the dedicated application 201 indicating that the user corresponding to the user ID of the mobile terminal 2 cannot use the system until the payment of the "unpaid" amount is completed on the dedicated application 201.

[0086] However, in the case where the IC tag F is registered in association with a code label CL corresponding to "pay-per-use" or "prepaid ticket" and "payment confirmation" is required to be requested from the mobile terminal 2 when using the vehicle M, if the user U does not carry the mobile terminal 2 when using the vehicle M or if the mobile terminal 2 is not in operation due to insufficient charge, the user U cannot respond to the "payment confirmation" notification. For this reason, in this example, the user U can select and set in the dedicated application 201 of the mobile terminal 2 that the payment request processing unit 4043 of the vehicle fare payment device 4 omits requesting "payment confirmation" from the mobile terminal 2 and instead sends the consent notification for the code label CL corresponding to "pay-per-use" or "prepaid ticket". For users U who find the operation of responding to consent to these "payment confirmation" notifications or the omission setting cumbersome, it is recommended that the IC tag F be registered in association with the code label CL of a "commuter pass" or a "book of tickets" for which electronic payment processing is not required when using the vehicle M.

[0087] The user usage information management control unit 403 then processes the user usage information relating to the fare and electronic payment to be sent to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61. For ease of explanation, it will be explained here that the user usage information management control unit 403 cooperates with the gateway function unit 404 to send the user usage information to the code label management server 61 each time it is updated, and stores the user usage information for a certain period of time.

[0088] The code label management server 61 stores the user usage information for each vehicle M for a certain period of time, and each time the user usage information is updated on a user ID basis, executes a user usage information notification process to notify the mobile terminal 2 corresponding to that user ID as usage history (step S10).

[0089] In this way, the user U can use the vehicle M using the code label CL displayed on the mobile terminal 2. The code label CL itself has an expiration date, and furthermore, it can be read by any code label / IC tag reading terminal 3, but since only the user ID is decoded, the confidentiality of the user U's personal information and the security of the transaction are maintained. Note that the code label CL may further include encoded information embedded as user information to further enhance the confidentiality of the personal information and the security of the transaction. Furthermore, device information identifying the mobile terminal 2 may be added to this code label information for device authentication of the mobile terminal 2.

[0090] (System operation: When vehicle M is used with IC tag F) 6 is a flowchart showing an example of a system operation when a vehicle M is used with an IC tag F in the vehicle fare payment system 1 according to an embodiment of the present invention. In FIG. 6, the same step numbers are assigned to operations that are the same as those shown in FIG. 5.

[0091] 3(a) described above, in this embodiment, code labels CL corresponding to "pay per use," "commuter pass," "ticket coupon," and "prepaid ticket" are assumed, and an IC tag F can be registered in association with any of these in the IC tag association management server 62. In the following, since the code labels CL of "commuter pass" and "ticket coupon" are tickets that have already been purchased, there is no need to request electronic payment of the fare from the payment company server 7. Therefore, the use of a vehicle M using an IC tag F that has been registered in association with a code label CL corresponding to "pay per use" or "prepaid ticket" will be described as a representative example.

[0092] First, when the user U gets into the vehicle M, the user U performs an operation of presenting the IC tag F that has been registered in association with the purchased code label CL by holding it over the code label / IC tag reading terminal 3 (step S1').

[0093] Then, the code label / IC tag reading terminal 3 reads the IC tag F that has been registered for linkage, extracts the IC tag identification information, and transmits it to the vehicle fare payment device 4 (step S2').

[0094] Next, when receiving the IC tag identification information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41, the vehicle fare payment device 4 activates the linkage determination processing unit 4042, which performs linkage determination processing by matching with the IC tag linkage management server 62 via the communication unit 45 by the gateway function unit 404, and if the IC tag identification information has been registered for linkage, obtains the code label information of the registered code label CL from the IC tag linkage management server 62, and if the IC tag identification information is not linked, generates a no-linkage notice (error notice) indicating that (not shown), and transmits it to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown) via the linkage control unit 44 to display it (step S3'). When a no-linkage notice (error notice) is generated, the user U cannot use the vehicle M with the IC tag F, so the subsequent operations are not performed, and the user U needs to perform operations again from step S1' (or step S1 shown in FIG. 5). Here, the subsequent operations will be explained assuming that the code label information of the code label CL linked to the IC tag F has been acquired.

[0095] Next, the vehicle fare payment device 4 operates substantially in the same manner as the operation of step S3 in Fig. 5. When receiving the code label information acquired from the IC tag linkage management server 62, the gateway function unit 404 causes the use permission determination processing unit 4041 to function, which performs a use permission determination process by matching the code label management server 61 via the communication unit 45, and if the code label information is usable, generates a use permission notice indicating that, and if the code label information is unusable, generates an unusable notice (error notice) indicating that, and transmits the notice to the code label / IC tag reading terminal 3 and the operation panel 5 via the linkage control unit 44 and displays them (step S3). When the unusable notice (error notice) is generated, the user U cannot use the vehicle M, so the subsequent operations are not performed, and the user U must perform the operations from step S1' (or step S1 shown in Fig. 5) again. Here, the subsequent operations will be described assuming that the use permission notice is generated. Furthermore, when performing the linkage determination process related to step S3', the subsequent usability determination process of step S3 may be omitted, or the management center server 6 consisting of the code label management server 61 and the IC tag linkage management server 62 may perform steps S3' and S3 as a single process.

[0096] Next, the vehicle fare payment device 4 operates substantially in the same manner as in step S4 in Fig. 5, and after generating a notice of availability at the time of boarding, the GPS receiving function unit 401 causes the GPS receiving unit 43 to function, and receives GPS signals indicating GPS position information and GPS date and time information from multiple GPS satellites (not shown), and obtains current position information and current date and time information of the vehicle M, thereby detecting the boarding position and boarding date and time, and recording them in the storage unit 42 as a user usage information table together with the vehicle ID that identifies the device (own vehicle) (step S4). In addition, the user usage information management control unit 403 has a function of working with the gateway function unit 404 that controls communication with various servers to transmit the user usage information to the code label management server 61 successively every time it is updated, or periodically, or in response to a request from the code label management server 61, and storing the user usage information for a certain period of time. Here, for ease of explanation, it is assumed that the user usage information management control unit 403 cooperates with the gateway function unit 404 to transmit the user usage information to the code label management server 61 each time it is updated, and stores the user usage information for a certain period of time.

[0097] On the other hand, when the user U gets off the vehicle M, he or she presents the same IC tag F that was used when getting on by holding it over the code label / IC tag reading terminal 3 (step S5').

[0098] Then, the code label / IC tag reading terminal 3 reads the IC tag F that has been registered for linkage, extracts the IC tag identification information, and transmits it to the vehicle fare payment device 4 (step S6').

[0099] Next, when the vehicle fare payment device 4 receives the IC tag identification information transmitted from the code label / IC tag reading terminal 3 via the communication unit 41, it causes the gateway function unit 404 to function as an interconnection determination processing unit 4042, which performs an interconnection determination process by matching the IC tag interconnection management server 62 via the communication unit 45.If the IC tag identification information has already been registered for interconnection, it obtains the code label information of the registered code label CL from the IC tag interconnection management server 62 and verifies whether it is the same code label information as when boarding.If the IC tag identification information extracted at the time of disembarking is not linked to the code label CL, it generates a no-interconnection notification (error notification) indicating this (not shown), and transmits it via the interconnection control unit 44 to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown) for display (step S7'). When a non-linked notification (error notification) for the code label CL is generated, such as when the user U mistakenly presents an IC tag F that is not linked to the code label CL, the user U cannot use the vehicle M with the IC tag F, so subsequent operations are not performed and the user U must perform operations again from step S5'. Here, the subsequent operations will be explained assuming that the code label information has been verified to be the same as when the user got on the vehicle.

[0100] Next, after verifying at the time of disembarking that the code label information is the same as that at the time of boarding, the vehicle fare payment device 4 operates in substantially the same manner as in step S8 in Figure 5, and causes the GPS receiving function unit 401 to function, receives GPS signals indicating GPS location information and GPS date and time information from multiple GPS satellites (not shown), and obtains the current location information and current date and time information of vehicle M, thereby detecting the boarding location and boarding date and time.The fare calculation unit 402 automatically calculates a predetermined fare for the transaction related to the transportation service based on the detected location information and date and time information at the time of boarding of vehicle M and the location information and date and time information at the time of disembarking, and records this in the memory unit 42 as a user usage information table together with the vehicle ID that identifies the device (vehicle) (step S8).

[0101] Here, when the fare calculation unit 402 automatically calculates the fare, the vehicle fare payment device 4 generates a fare information notification indicating the fare, and transmits it via the interlocking control unit 44 to the code label / IC tag reading terminal 3 and the operation panel 5 which also functions as a fare display (not shown) for display. Note that the code label / IC tag reading terminal 3 is assumed to have a fare display function, but if it does not have this function, the transmission of the fare information notification to the code label / IC tag reading terminal 3 is omitted. However, the fare information is included in the user usage information, and is notified to the mobile terminal 2 from the code label management server 61 in step S10 described later.

[0102] As a function of the control unit 40, the user usage information management control unit 403 cooperates with the gateway function unit 404, which controls communication with various servers, to transmit the user usage information to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61, and has the function of storing the user usage information for a certain period of time. For ease of explanation, the user usage information management control unit 403 will be described as cooperating with the gateway function unit 404 to transmit the user usage information to the code label management server 61 each time it is updated.

[0103] Next, the vehicle fare payment device 4 operates in substantially the same manner as in step S9 in Figure 5, and when the code label CL requires electronic payment for the fare calculated by the fare calculation unit 402 when using the vehicle M, it automatically, or after an acceptance response to a payment confirmation to the mobile terminal 2, functions a payment request processing unit 4043 to request electronic payment of the fare to the payment company server 7 via the communication unit 45 and complete the electronic payment, and when it receives a payment completion notice indicating completion of payment from the payment company server 7, it processes it to send it via the interlocking control unit 44 to the code label / IC tag reading terminal 3 and the operation panel 5 which also serves as a fare display (not shown) for display, and functions the user usage information management control unit 403 to manage the history of the fare and user usage information related to the electronic payment in the memory unit 42 (step S9).

[0104] In this example, since it is assumed that the code label CL corresponds to a "pay per use" or "prepaid ticket", the operation by the payment request processing unit 4043 is explained, however, for the code labels CL of a "commuter pass" and a "ticket coupon", since these are tickets that have already been purchased, it is not necessary to request electronic payment of the fare from the payment company server 7 after the fare is calculated. In this case, the operation of requesting electronic payment in step S9 is omitted.

[0105] In addition, with regard to electronic payment of the fare to the payment company server 7 when using vehicle M with a code label CL corresponding to "pay per use" or a "prepaid ticket", the payment request processing unit 4043 automatically executes an electronic payment request for the fare calculated by the fare calculation unit 402 when the code label CL corresponding to "pay per use" or a "prepaid ticket" requires electronic payment when using the vehicle.

[0106] Here, depending on the payment company server 7, there may be a transaction form in which an electronic payment request is executed after "payment confirmation" is made to the user (i.e., mobile terminal 2). Even in this case, in this embodiment, as described above, the user U can select and set on the dedicated application 201 on the mobile terminal 2 that for code labels CL corresponding to "pay per use" or "prepaid tickets", the payment request processing unit 4043 of the vehicle fare payment device 4 will omit requesting "payment confirmation" from the mobile terminal 2 and will instead send an acceptance notification.

[0107] The user usage information management control unit 403 then processes the user usage information relating to the fare and electronic payment to be sent to the code label management server 61 each time it is updated, or periodically, or in response to a request from the code label management server 61. For ease of explanation, it will be explained here that the user usage information management control unit 403 cooperates with the gateway function unit 404 to send the user usage information to the code label management server 61 each time it is updated, and stores the user usage information for a certain period of time.

[0108] The code label management server 61 stores the user usage information for each vehicle M for a certain period of time, and each time the user usage information is updated on a user ID basis, executes a user usage information notification process to notify the mobile terminal 2 corresponding to that user ID as usage history (step S10).

[0109] 7 shows an example of a user usage information table in the vehicle fare payment device 4 in the vehicle fare payment system 1 according to one embodiment of the present invention. As shown in the example of FIG. 7, the vehicle fare payment device 4 is capable of managing user usage information by associating the read code label information, the read registered linked IC tag identification information, the corresponding user ID, boarding information, disembarking information, and the fare / electronic payment amount for each vehicle ID of its own device (own vehicle), and updating and monitoring the usage status of the vehicle M of the user U.

[0110] On the other hand, Fig. 8 is a diagram showing an example of a user usage information table in the code label management server 61 in the vehicle fare payment system 1 of one embodiment according to the present invention. As shown in Fig. 8, the code label management server 61 is capable of managing user usage information by associating, for each user ID, registered code label information, a vehicle ID used by a user U having the user ID, boarding information, disembarking information, and fare / electronic payment amount, and updating and monitoring the usage history of each vehicle of the user U. As shown in Fig. 4, the linkage registration information table in the IC tag linkage management server 62 registers and manages user IDs, registered code label information, and linked and registered IC tag identification information in a corresponding manner.

[0111] Here, Fig. 9 shows an example of a user usage information table in the management center server 6 when the code label management server 61 and the IC tag linkage management server 62 are integrated. That is, Fig. 9 is an example in which all of the information exemplified in Fig. 4 and Fig. 8 is associated with each other and organized into a table, and the management center server 6 can manage the user usage information by using the user usage information table shown in Fig. 9 to update and monitor the usage history of each vehicle of the user U.

[0112] (Typical example of system behavior) Figures 10(a) and (b) are diagrams showing typical examples of fare calculation and electronic payment in a vehicle fare payment system 1 of one embodiment of the present invention, when a user U uses an IC tag F to board and disembark a vehicle M, respectively.

[0113] As shown in Figure 10(a), when a user U boards a vehicle M related to this system, the vehicle fare payment device 4 acquires IC tag information from the IC tag F that has been registered in association with the code label CL that the user U has purchased and acquired via the code label / IC tag reading terminal 3, and then identifies the code label information of the code label CL that the user U has purchased and acquired through an association determination process. Then, based on the code label information, a usability determination process is performed, and the boarding location and boarding date and time of the user U are recorded and managed using the function of the GPS receiving function unit 401.

[0114] 10(b), when a user U gets off a vehicle M related to this system, the vehicle fare payment device 4 acquires IC tag information from the IC tag F linked and registered for the code label CL purchased and acquired by the user U via the code label / IC tag reading terminal 3, and verifies whether the linked and registered code label information is the same as that at the time of boarding through a link determination process, and then records and manages the location and date and time of the user U by the function of the GPS receiving function unit 401, and automatically calculates the fare. The vehicle fare payment device 4 omits the request process for electronic payment of the fare for the code label CL of a "commuter pass" or "ticket", but performs the request process for electronic payment of the fare for the code label CL of a "pay-per-use" or "prepaid ticket", and records the request process for electronic payment of the fare as user usage information in the vehicle fare payment device 4 of the vehicle M as usage history and manages it for a predetermined period, and also records the request process for usage history in the management center server (TicketQR server) 6 and manages it for a predetermined period. Furthermore, every time the usage history of the user U is updated, the management center server (TicketQR server) 6 notifies the mobile terminal 2 of the user history information related to the update.

[0115] In this way, the user U can use the vehicle M by using the IC tag F that has been registered in association with the code label CL, instead of using the code label CL displayed on the mobile terminal 2. Therefore, even if the user does not carry the mobile terminal 2 that uses the dedicated application 201, or even if the mobile terminal 2 is inoperable due to insufficient charge, the user U can use the vehicle fare payment system 1 according to the present invention by using the standard IC tag F that has been registered in association in advance, thereby making it even more convenient for the user U than before.

[0116] In fact, since it operates using a code label CL that has been registered in advance as a standard "IC tag," the code label CL itself has an expiration date. Furthermore, although it can be read by any code label / IC tag reading terminal 3, only the user ID is decoded, so the confidentiality of the user U's personal information and the security of the transaction are maintained.

[0117] (Another typical example of system behavior) Figures 11(a) and (b) are diagrams showing typical examples of fare calculation and electronic payment in a vehicle fare payment system 1 of one embodiment of the present invention, when a user U boards a vehicle M using a code label CL that he or she has purchased and presented on a mobile terminal 2, and disembarks using an IC tag F that has been registered in association with that code label CL.

[0118] As shown in Figure 11(a), when a user U boards a vehicle M related to this system, the vehicle fare payment device 4 acquires code label information from the code label CL that the user U has purchased and displayed on the mobile terminal 2 via the code label / IC tag reading terminal 3, and then performs a usability determination process based on the code label information. Then, using the function of the GPS receiving function unit 401, the boarding location and boarding date and time of the user U are recorded and managed.

[0119] 11(b), when a user U gets off a vehicle M related to this system, the vehicle fare payment device 4 acquires IC tag information from the IC tag F registered in association with the code label CL used when boarding through the code label / IC tag reading terminal 3, verifies whether the code label information of the code label CL associated with the IC tag information is the same as that at the time of boarding through an association determination process, and then records and manages the alighting location and alighting date and time of the user U by the function of the GPS receiving function unit 401, and automatically calculates the fare. The vehicle fare payment device 4 omits the request process for electronic payment of the fare for the code label CL of a "commuter pass" and a "ticket coupon", but performs the request process for electronic payment of the fare for the code label CL of a "pay-per-use" or "prepaid ticket", and records the request process for electronic payment of the fare as user usage information in the vehicle fare payment device 4 of the vehicle M as usage history and manages it for a predetermined period, and also records the request process for usage history in the management center server (TicketQR server) 6 and manages it for a predetermined period. Furthermore, every time the usage history of the user U is updated, the management center server (TicketQR server) 6 notifies the mobile terminal 2 of the user history information related to the update.

[0120] In this way, the user U can use the vehicle M by using the code label CL that the user U has purchased and presented on the mobile terminal 2 when getting into the vehicle M, and by using the IC tag F that has been registered in association with the code label CL when getting out of the vehicle M.

[0121] In addition, although illustration and explanation are omitted, the user U can also use the vehicle M by using the IC tag F when boarding the vehicle M and using the code label CL displayed on the mobile terminal 2 when disembarking the vehicle M, in the opposite manner to the example shown in FIG.

[0122] Therefore, according to this embodiment, usability for users is improved, and the use of the code label CL in the vehicle fare payment system 1 according to the present invention is promoted.

[0123] Two examples of the operation of linking and registering the code label CL and the IC tag will be described below.

[0124] (Example 1 of the operation of linking code label CL and IC tag F) FIG. 12 is a flowchart showing a first operation example of the linked registration of the code label CL and the IC tag F in the vehicle fare payment system 1 according to one embodiment of the present invention.

[0125] In this operation example 1, in response to the driver's operation on the operation panel 5, the code label / IC tag reading terminal 3 transitions to a linkage registration mode for the code label CL and IC tag F that the user U wishes to link, outputs an instruction for the linkage registration mode to the vehicle fare payment device 4, and enters a standby state for reading the IC tag F and code label CL (step S101).

[0126] Also, in the vehicle fare payment device 4, when an instruction for the linked registration mode is received from the operation panel 5 operated by the driver of the vehicle M via the interlocking control unit 44, the linked registration processing unit 4044 of the gateway function unit 404 is made to function, and the device transitions to the linked registration mode which executes the linked registration between the code label CL and the IC tag F, and waits for input of the IC tag information of the IC tag F and the code label information of the code label CL related to the linked registration via the communication unit 41 (step S102).

[0127] Next, the driver operates the operation panel 5 to cause the code label / IC tag reading terminal 3 and the vehicle fare payment device 4 to enter link registration mode, and then the user U holds the IC tag F that he or she wishes to link over the code label / IC tag reading terminal 3 (step S103).The code label / IC tag reading terminal 3 then reads the IC tag F, extracts the IC tag identification information, and outputs it to the vehicle fare payment device 4 (step S104).

[0128] Next, when the vehicle fare payment device 4 receives the IC tag identification information via the communication unit 41, the linked registration processing unit 4044 temporarily stores the IC tag identification information in the memory unit 42 and waits for the input of code label information for the code label CL (step S105).

[0129] Next, the user U starts the dedicated application 201 on the mobile terminal 2, displays the pre-registered and acquired code label CL related to vehicle use on the screen of the mobile terminal 2, and holds the code label CL over the code label / IC tag reading terminal 3 (step S106).The code label / IC tag reading terminal 3 reads the code label CL, extracts the code label information, and outputs it to the vehicle fare payment device 4 (step S107).

[0130] Next, when the vehicle fare payment device 4 receives code label information as a link registration mode via the communication unit 41, the link registration processing unit 4044 activates the usability determination processing unit 4041, performs a usability determination process by checking against the code label management server 61 via the communication unit 45, and generates a usability notification indicating that the code label information is usable, and generates an unusable notification (error notification) indicating that the code label information is unusable, and transmits the unusable notification (error notification) to the code label / IC tag reading terminal 3 and the operation panel 5 via the link control unit 44 for display (step S108). When an unusable notification (error notification) is generated due to expiration or other reasons, link registration is not possible, so subsequent operations are not performed and the user U must perform the operation of step S56 again. Here, the subsequent operations are described assuming that a usability notification is generated.

[0131] Next, the vehicle fare payment device 4 generates a notification of availability for the code label information in the linked registration mode, and then executes linked registration with the IC tag linkage management server 62 via the communication unit 45 for the IC tag identification information of the temporarily stored IC tag F and the code label information of the usable code label CL by the linked registration processing unit 4044, and after the linked registration is completed, generates a linked registration completion notification indicating that fact, and processes it to be sent to the code label / IC tag reading terminal 3 and the operation panel 5 via the linkage control unit 44 for display (step S109). Note that, in this example, the linkage procedure has been described taking as an example a procedure in which the code label CL is read after the IC tag is read, but the procedure may also be a procedure in which the IC tag is read after the code label CL is read, and this is in a predetermined order.

[0132] After completing the linkage registration, the IC tag linkage management server 62 generates a linkage registration completion notification indicating the linked code label CL and IC tag F, and notifies the mobile terminal 2 (step S59). The mobile terminal 2 manages the purchased and acquired code labels CL including the linkage registration information of the IC tag F as a list on the dedicated application 201 (step S110). Note that, similar to the procedure of the registration operation described above, the driver can cancel the linkage registration of each of the IC tags F linked and registered with the code label CL on the IC tag linkage management server 62 by operating the operation panel 5. Also, the driver can cancel the linkage registration of each of the IC tags F linked and registered with the code label CL on the IC tag linkage management server 62 by performing a setting operation on the list displayed on the dedicated application 201.

[0133] (Example 2 of the linked registration of code label CL and IC tag F) FIG. 13 is a flowchart showing a second operation example of the linked registration of the code label CL and the IC tag F in the vehicle fare payment system 1 of one embodiment according to the present invention. Here, an example will be described in which the mobile terminal 2 is "equipped with an IC tag reading function." Normally, if the mobile terminal 2 is configured as a smartphone, it is equipped with an IC tag reading unit 25 capable of reading the IC tag identification information of the IC tag F, and can be used when the user U registers the code label CL and the IC tag F that he or she has already purchased. Also, even if the mobile terminal 2 does not have an IC tag reading unit 25, an external IC tag reader capable of reading the IC tag identification information of the IC tag F may be connected to the mobile terminal 2 and used.

[0134] In this operation example 2, the user U launches the dedicated application 201 on the mobile terminal 2, and on that dedicated application (the "TicketQR" app), as a function of the linked registration function unit 205, transitions to a linked registration mode between the code label CL and the IC tag F that the user U wishes to link (step S201).

[0135] Next, after transitioning to the link registration mode on the dedicated application, the user U holds the IC tag F that he or she wishes to link over the mobile terminal 2 with an "IC tag reading function," and the mobile terminal 2 with an "IC tag reading function" reads the IC tag F and extracts the IC tag identification information (step S202), and in the link registration mode on the dedicated application 201, as a function of the link registration function unit 205, temporarily stores the extracted IC tag identification information in the memory unit 22 (step S203).

[0136] Next, in the mobile terminal 2 with "IC tag reading function", the code label acquisition management unit 203 stores the purchased and acquired code labels CL including the linked registration information of the IC tag F as a list in the memory unit 22 on the dedicated application 201, or as a variant, reads the list by accessing the code label management server 61 and the IC tag linked management server 62 to form the list, and therefore, in the linked registration mode on the dedicated application 201, as a function of the linked registration function unit 205, a pre-registered and acquired code label CL related to the vehicle usage that is to be linked and registered with the temporarily stored IC tag identification information is specified from this list (step S204).

[0137] Next, the mobile terminal 2 with "IC tag reading function" executes a usage confirmation process of the specified code label CL to the code label management server 61 as a function of the linked registration function unit 205 in the linked registration mode on the dedicated application 201 (step S205). That is, when a code label CL is specified in the linked registration mode, the code label information is automatically extracted, and the mobile terminal 2 transmits a usage confirmation inquiry request to the code label management server 61 via the communication unit 24 regarding the code label information of the specified code label CL.

[0138] In response to this usage confirmation inquiry request, the code label management server 61 generates a usage permission notice indicating that the code label information is usable, and generates an unusable notice (error notice) indicating that the code label information is unusable, and returns this notice to the mobile terminal 2. If the code label management server 61 returns a usage permission notice (error notice) due to expiration or other reasons, linked registration is not possible, so subsequent operations are not performed and the user U must perform the operation of step S204 again. Here, the subsequent operations will be explained assuming that a usage permission notice has been returned.

[0139] Next, the mobile terminal 2 with "IC tag reading function" executes, as a function of the linkage registration function unit 205 in the linkage registration mode on the dedicated application 201, a linkage registration process for linking and registering the temporarily stored IC tag identification information of the IC tag F and the code label information of the usable code label CL in the IC tag linkage management server 62 via the communication unit 24 (step S206). At this time, the IC tag linkage management server 62 performs linkage registration in response to the linkage registration request transmitted by the execution of the linkage registration process, and after the linkage registration is completed, generates a linkage registration completion notice indicating the linked code label CL and IC tag F and notifies the mobile terminal 2. Note that, in this example, the linkage procedure has been described taking, as an example, a procedure in which the code label CL is specified after reading the IC tag, but the linkage procedure may also be a procedure in which the IC tag is read after the code label CL is specified, and this is a predetermined order.

[0140] Next, the mobile terminal 2 manages the purchased and acquired code labels CL including the association registration information of the IC tags F as a list on the dedicated application 201 (step S207). Note that, by performing a setting operation on the list displayed on the dedicated application 201, it is possible to cancel the association registration on the IC tag association management server 62 for each of the IC tags F that have been associated with the code labels CL.

[0141] (Example of a list display of IC tags F that have been registered for each type of code label CL) 14(a) to (e) are diagrams showing examples of list displays on a mobile terminal relating to IC tags F that have been registered in association with each type of code label CL in the vehicle fare payment system 1 according to one embodiment of the present invention.

[0142] 14(a) to 14(e) show examples of list display related to IC tags F that have been registered in association with various purchased and acquired code labels CL, such as "pay-per-use," "commuter pass," "ticket coupon," and "prepaid ticket," and one or more IC tags F can be registered in association with one code label CL. However, one IC tag F can only be registered in association with one code label CL.

[0143] 14(a) to 14(e) on the list display screen, the display mode can be changed from the illustrated reduced display to the enlarged display, and from the enlarged display to the illustrated reduced display, each time "display of code label CL" is tapped. Also, the display mode can be changed from the illustrated title display to the detailed display, and from the detailed display to the title display, each time "usage history" is tapped. Also, the display modes of "IC tag 1", "IC tag 2", etc. are identification displays assigned by the IC tag linkage management server 62 to each IC tag information of the IC tag F for the user ID, but by tapping to specify "IC tag 1", for example, the user U can arbitrarily change the type of "IC tag 1" to a desired name that allows unique understanding, or can transition to a setting change menu for deleting the linkage registration, etc.

[0144] As described above, one code label CL can be registered in association with one or more IC tags F. Therefore, according to the vehicle fare payment system 1 of this embodiment, it is possible to automatically calculate and electronically pay the fare for the vehicle M for the transportation service by using either or both of a specific code label CL presented on the mobile terminal 2 and an IC tag F registered in advance in association with the specific code label CL.

[0145] Although the present invention has been described above by way of examples of specific embodiments, the present invention is not limited to the above-described embodiments and can be modified in various ways without departing from the technical concept thereof. [Industrial Applicability]

[0146] INDUSTRIAL APPLICABILITY The present invention can enhance the security of transactions relating to transportation services and also enhance convenience for users, and is therefore useful for automatic calculation and electronic payment of vehicle fares. [Explanation of symbols]

[0147] 1. Vehicle fare payment system 2 Mobile terminals 3. Code label / IC tag reading terminal 4. Vehicle fare payment device 5 Operation Panel 6 Management Center Server 6 7 Payment company server 20 Control section 21 Terminal UI (User Interface) 22 Memory section 23 Display section 24 Communications Department 25 IC tag reader 201 Applications 202 User Registration Department 203 Code Label Acquisition Management Department 204 Code label display control section 205 Linked Registration Function Unit 40 Control section 41 Communications Department 42 Storage section 43 GPS receiver 44 Interlocking control section 45 Communications Department 61 Code label management server 62 IC tag linkage management server 401 GPS receiving function unit 402 Fare Calculation Department 403 User usage information management control unit 404 Gateway Function Unit 4041 Availability determination processing unit 4042 Cooperation judgment processing unit 4043 Payment request processing unit 4044 Linkage registration processing unit CL Code Label F IC tag U User M Vehicle

Claims

1. A vehicle fare settlement system for automatically calculating the fare of a vehicle related to electronic payment for a transportation service, a mobile terminal used by a user, which is capable of presenting a code label in which at least code label information including a user ID is encoded, a vehicle equipped with a code label / IC tag reading terminal that can read the code label presented by the mobile terminal used by the user when the user gets on and off, extract the code label information, and read an IC tag pre-registered in association with the code label and presented by the user to extract unique IC tag identification information. Based on the reception of either the code label information or the IC tag identification information extracted by the code label / IC tag reading terminal, a GPS receiving unit that receives a GPS signal to obtain the current position information and current date and time information of the vehicle, a communication unit that performs wireless communication, and a control unit that functions the GPS receiving unit to detect the position information and date and time information at the time when the user gets on the vehicle and the position information and date and time information at the time when the user gets off the vehicle, and controls to settle a predetermined fare for a transaction related to the transportation service automatically calculated based on the detected position information and date and time information at the time when the user gets on the vehicle and the position information and date and time information at the time when the user gets off the vehicle. A vehicle equipped with a vehicle fare settlement device, communicates with the vehicle fare settlement device mounted on the vehicle via the communication unit, manages the registration of the code label information and the linked registration of the IC tag identification information with respect to the code label information so as to enable collation of the code label information and the IC tag identification information obtained from the vehicle fare settlement device, and manages the usage history of using the vehicle in both cases where the user presents a code label and where the user presents an IC tag. For a certain period for each vehicle, user usage information of transactions related to the transportation service of one or more user IDs is stored, and each time there is an update of the user usage information in units of user ID, a user usage information notification process is executed to notify the mobile terminal corresponding to the user ID as a usage history. A management center server, characterized by comprising the above.

2. The code label is pre-purchased and can be displayed on a dedicated application launched on the mobile terminal. It can be purchased and obtained through per-use payment for electronic payment each time, prepaid electronic payment that allows free use of the vehicle for a specified period (season ticket), per-use ticket purchased and obtained through prepaid electronic payment that allows use of the vehicle for the number of uses, and a prepaid ticket that is used for prepaid electronic payment when using the vehicle within the range of the amount charged through prior electronic payment. It indicates one of these types. The IC tag is configured to be able to be linked and registered with the management center server only for one of the code labels. The vehicle fare settlement system according to claim 1, characterized in that one of the code labels is configured to be able to link and register one or more IC tags with the management center server.

3. The vehicle fare settlement device includes, as a function of the control unit, a gateway function unit that performs communication control with the management center server. The gateway function unit includes a usability determination processing unit that performs verification regarding the usability of the code label information with respect to the management center server, a linkage determination processing unit that performs verification regarding the linkage registration of the IC tag identification information with respect to the code label information with respect to the management center server, and a settlement request processing unit that, when the code label requires electronic payment when using the vehicle for the automatically calculated fare, automatically or through a commitment response for payment confirmation to the mobile terminal, requests electronic payment of the fare to the settlement company server designated by the user and completes the electronic payment, and manages the history of the user usage information related to the fare and the electronic payment. The vehicle fare settlement system according to claim 2, characterized by having the above.

Images