Transportation use history management system, transportation use history management method, and transportation use history management program

Abstract

To allow a user to easily cancel a once stored use history in a system in which the use history of transportation of the user is stored with reading of predetermined information by a terminal carried by the user as a trigger.SOLUTION: First obtaining means (the communication section 13) for obtaining first tag memory information D1 from the user terminals 6, second obtaining means (the communication section 13) for obtaining second tag memory information D9 from the user terminals 6, first storage control means (the control section 11) for storing the use history information in the storage section 12 when the first obtaining means obtains the first tag memory information D1, and second storage control means (the control section 11), wherein the second storage control means deletes the selected use history information when the second obtaining means obtains the second tag memory information D9, after the lapse of the prescribed period, settlement is performed on the basis of the use history information excluding the use history information deleted by the second storage control means among the use history information in the prescribed period.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a transportation facility usage history management system, a transportation facility usage history management method, and a transportation facility usage history management program. [Background technology]

[0002] When using public transport such as trains or buses, users often hold their IC card over a designated device, such as an automatic ticket gate at a station or a terminal installed on a bus, to read the information stored on the IC card, which then stores the user's public transport usage history on a server connected to the device. However, to make this possible, it is necessary to install dedicated devices at each station, on each bus, etc. that can read the information stored on the IC card, which is very costly.

[0003] Therefore, instead of such devices, systems have been developed in which station ticket gates, bus interiors, etc. are equipped with only storage media, such as NFC (near field communication) tags, that can read information using devices such as smartphones.The information stored on such storage media can then be read by users of public transport using devices they carry, such as smartphones, which then send the read information from the devices to a designated server, which then stores the public transport usage history and processes fare payments etc. based on this information (see, for example, non-patent document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] East Japan Railway Company website, [searched June 29, 2021], Internet<URL:https: / / www.jreast.co.jp / press / 2019 / 20191209_ho01.pdf> , JR East Top / News Release / 2019 / Technical verification using NFC tags Summary of the Invention [Problem to be solved by the invention]

[0005] When using such a system, users of public transport must use their own terminal to set, for example, the number of passengers before having the terminal read the information stored on a storage medium such as an NFC tag. However, if the information is read with an incorrect setting, the incorrect setting will be sent to the server, and the public transport usage history will be stored according to the incorrect setting. In this case, it is necessary to cancel such usage history, but in conventional systems, there was no mechanism for cancellation, so in order to cancel usage history that had once been stored, it was necessary, for example, to access the server and ask someone with the authority to perform the cancellation process to perform the cancellation process one by one, which was extremely time-consuming.

[0006] The object of the present invention is to make it easier for a user to cancel usage history that has been stored in a system in which a user's transportation usage history is stored when the user has a terminal that reads specified information. [Means for solving the problem]

[0007] In order to solve the above problem, the invention described in claim 1 is a transportation usage history management system, a first acquisition means for acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by a user; a second acquisition means for acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control means for causing a first storage means to store usage history information, which is information relating to the user's usage history of a transportation facility, when the first acquisition means acquires the transportation facility usage information; a second storage control means for deleting the usage history information stored in the first storage means when the second acquisition means acquires the transportation facility usage cancellation information; Equipped with The transportation facility use cancellation information is selected by a user on the terminal device, After a predetermined period has elapsed, payment is made based on the usage history information during the predetermined period, excluding the usage history information deleted by the second storage control means.

[0008] The invention described in claim 2 is the transportation facility usage history management system described in claim 1, a list of the usage history information relating to the user who uses the terminal device stored in the first storage means is transmitted to the terminal device; The transportation facility usage cancellation information is characterized in that it is selected from the list of the usage history information.

[0009] The invention described in claim 3 is a transportation usage history management method by a transportation usage history management system, a first acquisition step of acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by the user; a second acquisition step of acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control step of storing, when the first acquisition step acquires the transportation facility usage information, usage history information relating to the transportation facility usage history of the user in a first storage means; a second storage control step of deleting the usage history information stored in the first storage means when the second acquisition step acquires the transportation facility usage cancellation information; Including, The transportation facility use cancellation information is selected by a user on the terminal device, After a predetermined period has elapsed, payment is made based on the usage history information during the predetermined period, excluding the usage history information deleted by the second storage control step.

[0010] The invention described in claim 4 is a transportation usage history management program for a computer, a first acquisition means for acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by the user; a second acquisition means for acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control means for causing a first storage means to store usage history information, which is information relating to the user's usage history of transportation facilities, when the first acquisition means acquires the transportation facility usage information; a second storage control means for deleting the usage history information stored in the first storage means when the second acquisition means acquires the transportation facility usage cancellation information; It functions as The transportation facility use cancellation information is selected by a user on the terminal device, After a predetermined period has elapsed, payment is made based on the usage history information during the predetermined period, excluding the usage history information deleted by the second storage control means. [Effects of the Invention]

[0011] According to the present invention, in a system in which a user's transportation usage history is stored when the user has a terminal that reads specified information, it is possible to make it easier for the user to cancel usage history that has been stored once. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a block diagram showing the configuration of a transportation facility usage history management system according to an embodiment. [Figure 2]10 is a flowchart showing the flow of operations when storing a usage history in the transportation usage history management system according to the embodiment. [Figure 3] 10 is a flowchart showing the flow of operations when canceling a usage history in the transportation usage history management system according to the embodiment. [Figure 4] 10 is a flowchart showing the flow of operations when paying for a transportation facility usage history management system according to an embodiment. [Figure 5] 10 is a flowchart showing the flow of operations when storing a usage history in a transportation usage history management system according to a modified example. [Figure 6] 10 is a flowchart showing the flow of operations when storing a usage history in a transportation usage history management system according to a modified example. DETAILED DESCRIPTION OF THE INVENTION

[0013] A transportation usage history management system 100 according to an embodiment of the present invention will be described below with reference to Figures 1 to 6. However, the technical scope of the present invention is not limited to the illustrated examples. In addition, the following description will be given as an example of a case where a user rides a bus on the same route with a flat fare regardless of the section used. However, the same content can also be applied to a case where a user rides a one-man train on the same route with a flat fare regardless of the section used, for example.

[0014] [First Configuration Explanation] The transportation usage history management system 100 is a system that stores information related to the usage history of transportation facilities and performs payment processing in which bus operators receive payment for transportation usage fees from users based on the stored information related to the usage history of transportation facilities.As shown in Figure 1, it is configured with a usage history management server 1 and a payment server 2, which are servers owned by a specific operator that manages and operates this system, and these servers are connected via a communication network N.

[0015] In addition, in the transportation usage history management system 100, the usage history management server 1 is connected via a communication network N to a driver terminal 5, which is a terminal carried by each bus driver, and a user terminal 6, which is a terminal carried by each user who rides a bus using this system, and the payment server 2 is connected to the user terminal 6.

[0016] It should be noted that the above-mentioned servers do not necessarily have to be provided separately, and a single information device such as a PC (Personal Computer), WS (Work Station), etc. may also function as multiple servers. In this case, a program for operating the single information device such as a PC or WS is stored in the single information device, and in accordance with the program, the single information device performs both the operation of the usage history management server 1 and the operation of the payment server 2, which will be described later in the description of the operation. Conversely, each of the above servers does not necessarily have to be realized by a single information device such as a PC or WS, and the functions of each server may be realized by multiple information devices such as PCs or WSs connected via a communication network N.

[0017] [1 Usage history management server] The usage history management server 1 is, for example, an information device such as a PC or WS owned by a company that manages and operates the transportation usage history management system 100, and stores information related to the user's bus usage history based on information received from the user terminal 6, as described below. As shown in FIG. 1, the usage history management server 1 includes, for example, a control unit 11, a storage unit 12, and a communication unit 13.

[0018] [(1) Control Unit] The control unit 11 is the part that controls the operation of the usage history management server 1, and is configured with, for example, a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc., and controls each part of the usage history management server 1 in cooperation with the program data stored in the memory unit 12 and the CPU.

[0019] [(2) Storage section] The memory unit 12 is a part where various information necessary for the operation of the usage history management server 1 is stored, and is composed of, for example, an HDD (Hard Disk Drive), semiconductor memory, etc., and stores data necessary for the operation of the usage history management server 1 in a manner that allows it to be read and written by the control unit 11. The memory unit 12 stores a program including various instructions to the control unit 11 for operating the usage history management server 1, and the operation of the usage history management server 1 described in the operation explanation below is performed in accordance with the program stored in the memory unit 12.

[0020] The memory unit 12 also includes a bus list information memory unit 121 that stores bus list information D4, and a usage history memory unit 122 that stores information relating to the user's bus usage history, such as bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7, linked together. Details of the information stored in each storage unit will be described in the explanation of the operation.

[0021] [(3) Communications Department] The communication unit 13 is a part used for communication between the usage history management server 1 and the payment server 2, the driver terminal 5, and the user terminal 6, and is, for example, a communication interface having a communication IC (Integrated Circuit) and a communication connector, and performs data communication via the communication network N using a predetermined communication protocol under the control of the control unit 11.

[0022] [2 Payment Server] The payment server 2 is, for example, an information device such as a PC or WS owned by a company that manages and operates the transportation usage history management system 100, and performs processing related to the payment of transportation usage fees based on information related to the transportation usage history obtained from the usage history management server 1. As shown in FIG. 1, the payment server 2 is configured to include, for example, a control unit 21, a storage unit 22, and a communication unit 23, similar to the usage history management server 1.

[0023] The configurations of the control unit 21 and the communication unit 23 are the same as those of the control unit 11 and the communication unit 13 in the usage history management server 1, respectively.

[0024] The storage unit 22, like the storage unit 12 in the usage history management server 1, is configured with, for example, an HDD, a semiconductor memory, etc., and stores data required for the operation of the payment server 2 in a manner that allows the control unit 21 to read and write the data. The memory unit 22 stores a program including various instructions to the control unit 21 for operating the payment server 2, and the operation of the payment server 2 described in the operation explanation below is performed in accordance with the program stored in the memory unit 22.

[0025] The memory unit 22 also includes a travel pass / commuter pass information memory unit 221 in which user identification information D3 and travel pass / commuter pass information D11 are linked and stored, and a payment method information memory unit 222 in which user identification information D3 and payment method information D12 are linked and stored. Details of the information stored in each storage unit will be described in the explanation of the operation.

[0026] [3. First short-range wireless communication tag] The first short-range wireless communication tag 3 is a near-field wireless communication (NFC) tag installed inside the bus, and first tag storage information D1, which is information indicating the user's use of the bus as described below, is stored so as to be readable by the user terminal 6. The first short-range wireless communication tag 3 may be fixedly attached to a predetermined position inside the bus, such as near the boarding entrance, or may be carried by the driver while driving the bus. Even if the first short-range wireless communication tag 3 is not fixedly installed inside the bus, as long as the first short-range wireless communication tag 3 is located inside the bus, it is considered to be installed inside the bus.

[0027] [4 Second short-range wireless communication tag] The second short-range wireless communication tag 4 is a near-field wireless communication (NFC) tag installed inside the bus, and stores second tag storage information D9, which is information indicating the user's cancellation of bus use, readable by the user terminal 6, as described below. Like the first short-range wireless communication tag 3, the second short-range wireless communication tag 4 may be fixedly attached to a predetermined position inside the bus, such as near the boarding entrance, or may be carried by the driver while driving the bus. Even if the second short-range wireless communication tag 4 is not fixedly attached inside the bus, it is considered to be included in the case where the second short-range wireless communication tag 4 is attached inside the bus, as long as the second short-range wireless communication tag 4 is located inside the bus.

[0028] It is preferable that the first short-range wireless communication tag 3, which the user must use when boarding the bus using this system, be fixedly attached near the bus entrance, and the second short-range wireless communication tag 4, which the user will only use when canceling their usage history due to an input error or other reason, be carried by the driver while driving the bus and only be taken out when the user wishes to use it.

[0029] [5 Driver's terminal] The driver terminal 5 is, for example, an information device such as a smartphone or tablet terminal carried by the driver while driving the bus, and is used to notify the driver of information regarding whether or not users using this system can board the bus, as described below. As shown in Figure 1, the driver terminal 5 is configured to include, for example, a control unit 51, a memory unit 52, and a communication unit 53, similar to the usage history management server 1, and further includes a display unit 54 and an operation unit 55.

[0030] The configurations of the control unit 51 and the communication unit 53 are the same as those of the control unit 11 and the communication unit 13 in the usage history management server 1, respectively. The storage unit 12 stores a driver terminal application 521, which is a program including various commands to the control unit 51 for operating the driver terminal 5, as will be described later in the description of the operation.

[0031] The display unit 54 includes a display such as an LCD (Liquid Crystal Display), and displays an image based on the display control signal output from the control unit 51 on the display screen.

[0032] The operation unit 55 includes, for example, a keyboard having letter input keys, number input keys, and other keys associated with various functions, and receives operation input from the driver using the driver terminal 5 and outputs an operation signal corresponding to the operation input to the control unit 51. The operation unit 55 may be, for example, a touch panel formed integrally with the display unit 54, and is not particularly limited as long as it can receive operation input from the driver.

[0033] [6 User Devices] The user terminal 6 is, for example, an information device such as a smartphone or tablet terminal carried by each user who rides the bus using this system, and is used to read information from the first short-range wireless communication tag 3 or the second short-range wireless communication tag 4 and transmit the read information to the usage history management server 1, as described below. As shown in Figure 1, the user terminal 6 is configured to include, for example, a control unit 61, a memory unit 62, a communication unit 63, a display unit 64, and an operation unit 65, similar to the driver terminal 5, as well as a tag reading unit 66 and a location information acquisition unit 67.

[0034] The configurations of the control unit 61, communication unit 63, display unit 64, and operation unit 65 are no different from the control unit 51, communication unit 53, display unit 54, and operation unit 55, respectively, of the driver terminal 5. The memory unit 62 stores a user terminal application 621, which is a program including various commands to the control unit 61 for operating the user terminal 6, as will be described later in the description of the operation.

[0035] The tag reading unit 66 is a part for reading information stored in a short-range wireless communication tag, and is not particularly limited as long as it can read the first tag stored information D1 from the first short-range wireless communication tag 3 and the second tag stored information D9 from the second short-range wireless communication tag 4, as described below.

[0036] The location information acquisition unit 67 is a part that acquires information about the location of the user terminal 6, and for example, a GPS (Global Positioning System) receiver is used. The GPS receiver receives GPS signals, which are positioning radio waves provided by multiple GPS satellites that make up the GPS, and uses these to acquire location information of the user terminal 6, and ultimately of the user who owns it. The location information acquisition unit 67 is not limited to a GPS receiver as long as it can acquire location information of the user terminal 6. For example, a receiver for signals related to other satellite positioning systems, such as a QZSS (Quasi-Zenith Satellite System) receiver, may also be used.

[0037] [7 Communication Network] The communication network N is, for example, the Internet, a telephone line network, a mobile phone communication network, a wireless LAN communication network, etc., and connects each server that constitutes the transportation usage history management system 100, the driver terminal 5, and the user terminal 6, as shown in Figure 1. The communication network N is not particularly limited as long as it can connect each server, driver terminal 5, and user terminal 6 that make up the transportation usage history management system 100 as described above and enable data to be sent and received between them.

[0038] [Second operation explanation] The operation of the transportation facility usage history management system 100 according to this embodiment will be explained below, dividing it into storing usage history (step S1), canceling usage history (step S2), and paying usage fees (step S3).

[0039] [1 Step S1: Storing usage history] First, the operation of the present system when storing information relating to a user's bus usage history in the usage history management server 1 will be described with reference to the flowchart of FIG.

[0040] When a bus user carrying a user terminal 6 uses this system to board a bus, the user first performs a predetermined operation using the operation unit 65 in accordance with the user terminal application 621, and inputs the number of passengers on the bus and whether they are adults or children (step S1-1). For example, if there is only one user riding, they would enter "1 adult"; if there are two friends, they would enter "2 adults"; if there are four family members, two of whom are children, they would enter "2 adults and 2 children."

[0041] Next, the user holds the user terminal 6 over the first short-range wireless communication tag 3 provided in the bus. When the user terminal 6 is held over the first short-range wireless communication tag 3, the control unit 61 of the user terminal 6 causes the tag reading unit 66 to read the first tag stored information D1 (step S1-2).

[0042] The first tag storage information D1 is information stored in the first short-range wireless communication tag 3 so as to be readable by the user terminal 6, and includes bus identification information D1-1 and authentication information D1-2. The bus identification information D1-1 is information that can identify a bus equipped with a first short-range wireless communication tag 3 that stores the information, such as a number or identifier assigned to each bus. The authentication information D1-2 is information for determining whether the first tag storage information D1 is authentic or not. In this embodiment, such first tag storage information D1 is information indicating that the user will use the bus associated with the bus identification information D1-1, and corresponds to the transportation means usage information of the present invention.

[0043] When the first tag storage information D1 is read by the tag reading unit 66, the control unit 61 transmits the information regarding the number of passengers input in step S1-1 (number of passengers information D2) and the first tag storage information D1 read in step S1-2, together with information that can identify the user, such as an ID assigned to each user (user identification information D3), from the communication unit 63 via the communication network N to the usage history management server 1 (step S1-3).

[0044] In the usage history management server 1, which receives the first tag storage information D1, number of passengers information D2, and user identification information D3 transmitted from the user terminal 6 via the communication unit 13, the control unit 11 determines the authenticity of the received first tag storage information D1 (whether the information is legitimate information, i.e., whether it is information actually stored in the first short-range wireless communication tag 3 installed in the bus) (step S1-4). That is, since the first tag stored information D1 includes authentication information D1-2, which is information for determining whether the information is authentic, the control unit 11 uses the authentication information D1-2 to determine whether the first tag stored information D1 is authentic. Note that the content of the authentication information D1-2 and the method of determination using the authentication information D1-2 are not particularly limited, and any existing method can be adopted.

[0045] Next, the control unit 11 of the usage history management server 1 identifies the route that the user will take (step S1-5). In other words, the first tag storage information D1 includes bus identification information D1-1, which is information that can identify a bus equipped with a first short-range wireless communication tag 3 in which information such as the number and identifier assigned to each bus is stored, as described above.Furthermore, the bus list information D4 stored in the bus list information storage unit 121 of the storage unit 12 of the usage history management server 1 is information in which the bus identification information D1-1 for each bus, the name of the route on which the bus runs, and the fare for that route are linked and stored.Therefore, the control unit 11 can identify the route taken by the user by extracting from the bus list information D4 the route name that is stored in linkage with the bus identification information D1-1 included in the first tag storage information D1 received in step S1-3.

[0046] Next, the control unit 11 of the usage history management server 1 links the bus identification information D1-1, number of passengers information D2, and user identification information D3 received in step S1-3 with information related to the route identified in step S1-5 (route information D5), information related to the date and time the information was received in step S1-3 (usage date and time information D6), and fare information D7, which is information related to the usage fee for the route, and stores them in the usage history memory unit 122 of the memory unit 12 (step S1-6). In this embodiment, the bus identification information D1-1, passenger number information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7 linked together indicate the user's transportation usage history, and therefore correspond to the usage history information of the present invention.

[0047] Once step S1-6 is completed, the control unit 11 of the usage history management server 1 generates boarding availability information D8, which is predetermined information indicating that the user is available to board the bus, and transmits it from the communication unit 13 via the communication network N to the driver terminal 5 used by the driver driving the bus corresponding to the bus identification information D1-1 included in the first tag memory information D1 received in step S1-3 (step S1-7).In the driver terminal 5 that receives the boarding availability information D8 transmitted from the usage history management server 1 via the communication unit 53, the control unit 51 causes the display unit 54 to display a predetermined display indicating that the user is available to board the bus (step S1-8). This allows the bus driver to know whether the user who held the user terminal 6 over the first short-range wireless communication tag 3 in step S1-2 is able to board the bus using this system, depending on whether the above display is displayed on the display unit 54.

[0048] In addition, the control unit 11 of the usage history management server 1 transmits the boarding availability information D8 from the communication unit 13 via the communication network N to the user terminal 6 that transmitted the information in step S1-3 (step S1-9), and in the user terminal 6 that receives the boarding availability information D8 transmitted from the usage history management server 1 via the communication unit 63, the control unit 61 causes the display unit 64 to display a predetermined display indicating that the user is able to board (step S1-10). This allows the user to know whether the process has been carried out normally and whether he or she can board the bus using this system, depending on whether the above message is displayed on the display unit 64 or not.

[0049] [2 Step S2 Cancel usage history] Next, the operation of the system when a user cancels a usage history stored in the storage unit 12 of the usage history management server 1 in step S1 will be described with reference to the flowchart of FIG.

[0050] After the display unit 64 of the user terminal 6 displays in step S1-10 that boarding is possible, if the user wishes to cancel the stored usage history, for example because the information regarding the number of passengers entered in step S1-1 was incorrect, the user holds the user terminal 6 over the second short-range wireless communication tag 4 provided in the bus. When the user terminal 6 is held over the second short-range wireless communication tag 4, the control unit 61 of the user terminal 6 causes the tag reading unit 66 to read the second tag stored information D9 (step S2-1).

[0051] The second tag storage information D9 is information stored in the second short-range wireless communication tag 4 so as to be readable by the user terminal 6, and includes bus identification information D9-1, authentication information D9-2, and a cancellation flag D9-3. The contents of the bus identification information D9-1 and the authentication information D9-2 are the same as the bus identification information D1-1 and the authentication information D1-2 included in the first tag storage information D1, respectively. The cancellation flag D9-3 is information that simply indicates that the information is for cancellation. In this embodiment, such second tag storage information D9 is information indicating that the user cancels the use of the bus associated with the bus identification information D9-1, and corresponds to the transportation use cancellation information of the present invention. The second tag storage information D9 does not necessarily need to include the cancellation flag 9-3, as long as it allows the usage history management server 1 to identify the bus equipped with the second short-range wireless communication tag 4 in which the information is stored and whether the information is for cancellation. For example, the second tag storage information D9 may include the number of the tag in which the information is stored, and the usage history management server 1 may use the number to identify whether the received information is for cancellation.

[0052] When the second tag storage information D9 is read by the tag reading unit 66, the control unit 61 transmits the second tag storage information D9 read in step S2-1, together with the user identification information D3, from the communication unit 63 via the communication network N to the usage history management server 1 (step S2-2).

[0053] In the usage history management server 1, which receives the second tag storage information D9 and user identification information D3 transmitted from the user terminal 6 via the communication unit 13, the control unit 11 determines the authenticity of the received second tag storage information D9 (whether the information is legitimate information, i.e., information actually stored in the second short-range wireless communication tag 4 installed in the bus) (step S2-3). In other words, the second tag storage information D9 also contains authentication information D9-2, which is information for determining whether the second tag storage information D9 is genuine or not, in the same format as the authentication information D1-2 contained in the first tag storage information D1, so the control unit 11 can use this information to determine whether the second tag storage information D9 is genuine or not.

[0054] Next, the control unit 11 of the usage history management server 1 identifies the route for which the user wishes to cancel the usage history (step S2-4). In other words, since the second tag storage information D9 also contains bus identification information D9-1 with the same content as the bus identification information D1-1 contained in the first tag storage information D1, the control unit 11 can identify the route for which the user wants to cancel the usage history by extracting from the bus list information D4 the route name stored in association with the bus identification information D9-1 contained in the second tag storage information D9 received in step S2-2.

[0055] Next, the control unit 11 of the usage history management server 1 deletes the most recent usage history stored in the usage history memory unit 122 of the memory unit 12, i.e., the information stored in association with bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7, where the user identification information D3 matches the user identification information D3 received in step S2-2 and the route information D5 matches the route identified in step S2-4, i.e., the most recent usage date and time information D6 (stored at the time closest to the time the second tag memory information D9 was obtained in step S2-2) (step S2-5). Furthermore, it may be possible to determine whether the bus associated with bus identification information D1-1 matches the bus associated with bus identification information D9-1 included in the second tag storage information D9 received in step S2-2 and the date and time associated with usage date and time information D6 is within a predetermined time period, such as two hours, and to delete only information for which the bus associated with bus identification information D1-1 matches the bus associated with bus identification information D9-1 included in the second tag storage information D9 received in step S2-2 and the date and time associated with usage date and time information D6 is within a predetermined time period, such as two hours. In this case, only usage histories associated with the same bus that are within a predetermined time period from the time the cancellation process is performed in the usage history management server 1 are subject to cancellation.

[0056] Once step S2-5 is completed, the control unit 11 of the usage history management server 1 transmits cancellation completion information D10, which is predetermined information indicating that the cancellation of the usage history has been completed, from the communication unit 13 via the communication network N to the driver terminal 5 used by the driver driving the bus related to the bus identification information D9-1 included in the second tag storage information D9 received in step S2-2 (step S2-6), and in the driver terminal 5 that has received the cancellation completion information D10 transmitted from the usage history management server 1 via the communication unit 53, the control unit 51 causes the display unit 54 to display a predetermined display indicating that the cancellation of the usage history has been completed (step S2-7).

[0057] In addition, the control unit 11 of the usage history management server 1 transmits the cancellation completion information D10 from the communication unit 13 via the communication network N to the user terminal 6 that transmitted the information in step S2-2 (step S2-8), and in the user terminal 6 that receives the cancellation completion information D10 transmitted from the usage history management server 1 via the communication unit 63, the control unit 61 causes the display unit 64 to display a predetermined message indicating that the cancellation of the usage history has been completed (step S2-9).

[0058] [3 Step S3 Payment of usage fee] Next, the operation of this system when settling a usage fee based on the information stored in the usage history storage unit 122 of the storage unit 12 of the usage history management server 1 will be described with reference to the flowchart of FIG.

[0059] At predetermined intervals, such as once every two weeks, the control unit 11 of the usage history management server 1 transmits all information related to usage history (excluding information deleted in step S2-5) stored in the usage history memory unit 122 of the memory unit 12 in step S1-6 during that period in a lump sum from the communication unit 13 via the communication network N to the payment server 2 (step S3-1).

[0060] In the payment server 2, when the communication unit 23 receives the information sent from the usage history management server 1, the control unit 21 determines, for each usage history, i.e., the information linked and stored including bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7, whether the user associated with the user identification information D3 holds a ticket that can be purchased before using the bus, such as a round-trip ticket or a commuter pass, for the route associated with the route information D5, i.e., whether the fare for the bus usage associated with the usage history has been paid (step S3-2).

[0061] That is, the round-trip ticket / commuter pass information storage unit 221 of the storage unit 22 of the payment server 2 stores round-trip ticket / commuter pass information D11, which is information related to tickets that can be purchased before using the bus, such as round-trip tickets / commuter passes that each user has purchased and paid for, linked to user identification information D3 related to each user. The round-trip ticket / commuter pass information D11 also includes information related to routes that can be traveled using the ticket. Therefore, for each usage history, the control unit 21 extracts from the round-trip pass / commuter pass information D11 stored in the round-trip pass / commuter pass information storage unit 221 the user identification information D3 associated with and stored in the round-trip pass / commuter pass information storage unit 221 that matches the user identification information D3 included in the usage history, and then compares the route information D5 included in each usage history with the information on routes that can be traveled with the ticket included in the extracted round-trip pass / commuter pass information D11. If there is a match, it is determined that the user associated with the user identification information D3 is in possession of a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, for the route associated with the route information D5.

[0062] Next, the control unit 21 of the payment server 2 performs payment of the bus fare for the usage history information received in step S3-1, for which it has been determined in step S3-2 that the user does not possess a ticket that can be purchased before using the bus, such as a round-trip ticket or a commuter pass (step S3-3).

[0063] That is, the payment method information storage unit 222 of the storage unit 22 stores payment method information D12, which is information related to the payment method of each user, such as credit cards and various electronic money, linked to user identification information D3 related to each user. Therefore, the control unit 21 excludes information from the information related to the usage history received in step S3-1 that indicates in step S3-2 that the user is in possession of a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, and then deducts the amount related to the fare information D7 related to each usage history from the credit card, electronic money, etc. related to the payment method information D12 that matches the user identification information D3.In this way, the bus fares used by the user during the above-mentioned specified period, excluding the usage history related to routes for which the user is in possession of a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, i.e., routes for which the fare has already been paid, are paid to the specified business operator that operates the route, as specified for each bus route.

[0064] [Third effect explanation] Next, the effects of the transportation utilization history management system 100 according to this embodiment will be described.

[0065] According to the transportation usage history management system 100 of this embodiment, when the usage history management server 1 acquires first tag storage information D1 from the user terminal 6, it stores the user's bus usage history (information linked to bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7) in the memory unit 12, and deletes the user's bus usage history stored in the memory unit 12 when it acquires second tag storage information D9 from the user terminal 6. This allows the user to cancel the bus usage history that has been stored once simply by obtaining the second tag storage information D9 using the user terminal 6 and having the user terminal 6 send this to the usage history management server 1, making it easy for the user to cancel the bus usage history that has been stored once in the usage history management server 1.

[0066] Furthermore, since the first tag storage information D1 is stored in a first short-range wireless communication tag 3 that is provided on board the bus and can read the stored information by a user terminal 6, and the second tag storage information D9 is stored in a second short-range wireless communication tag 4 that is provided on board the bus and can read the stored information by a user terminal 6, the user can perform operations related to canceling usage history, etc. on board the bus. Furthermore, since the information storage medium installed inside the bus is a short-range wireless communication tag that takes a short time to read by the user terminal 6, such operations can be performed quickly, which reduces the risk of congestion at the bus entrance.

[0067] In addition, in the past, if a user wanted to cancel their usage history, they had to contact the transportation company's inquiry desk separately after getting off the bus and request that the usage history be canceled.In this case, however, it was not easy for staff at the transportation company's inquiry desk to accurately identify the usage history that the user wanted to cancel, and there was a risk of mistakes such as accidentally canceling the wrong usage history. According to the transportation usage history management system 100 of this embodiment, such problems can be solved by simply having the user terminal 6 read the second tag storage information D9 inside the bus before the user gets off the bus, thereby canceling the usage history.

[0068] Furthermore, the first tag storage information D1 and the second tag storage information D9 include bus identification information D1-1 or D9-1, which is information that can identify a bus equipped with a first short-range wireless communication tag 3 in which information such as a number and identifier assigned to each bus is stored, and the usage history management server 1 stores bus list information D4, which is information in which the bus identification information D1-1 or D9-1 for each bus is linked to the name of the route on which the bus runs, in the bus list information storage unit 121 of the storage unit 12.This makes it easy for the usage history management server 1, which receives the first tag storage information D1 or the second tag storage information D9 from the user terminal 6, to identify the route on which the user is boarding or for which the user wishes to cancel their usage history.

[0069] In addition, when the usage history management server 1 acquires the second tag storage information D9 from the user terminal 6, it deletes the most recent usage history stored in the memory unit 12, i.e., the information that matches the user and route and has the most recent usage date and time information D6 (the information stored at the time closest to the time the second tag storage information D9 was acquired by the usage history management server 1), making it possible to immediately cancel the entry if the user makes a mistake, for example.

[0070] Furthermore, when paying the usage fee, the payment server 2 determines from the information relating to the user's usage history obtained from the usage history management server 1 only information relating to routes for which the user holds a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, i.e., information relating to bus usage for which the user has already paid the fare, and the bus usage fee is paid only for the usage history excluding this information.This makes it easy to distinguish between the usage history of transportation for which the user has already paid the fare and the usage history of transportation for which the user has not already paid the fare, even in a system such as the transportation usage history management system 100, in which the transportation usage history is stored by having the user terminal 6 read the first tag storage information D1, and to pay the usage fee only for the latter.

[0071] [Fourth Modification] Next, a modified example of the transportation utilization history management system 100 according to this embodiment will be described.

[0072] [1 Variation 1: Determining whether or not a passenger has a round-trip ticket, commuter pass, etc. in the usage history management server] In the above, in step S3-1, information related to the usage history stored in the usage history memory unit 122 of the memory unit 12 for a predetermined period is sent in bulk from the usage history management server 1 to the payment server 2, and in step S3-2, the payment server 2 determines whether the user has a ticket such as a round-trip pass or a commuter pass that can be purchased before using the bus for each route related to the usage history.However, instead of this, the usage history management server 1 may determine whether the user has a ticket such as a round-trip pass or a commuter pass that can be purchased before using the bus for each route related to the usage history, and then send only the usage history related to routes for which the user does not have a round-trip pass or a commuter pass to the payment server 2.

[0073] That is, the round-trip ticket / commuter pass information D11 stored in the memory unit 22 of the payment server 2 as described above is stored in the memory unit 12 of the usage history management server 1, and then the control unit 11 in the usage history management server 1 uses this information to determine the usage history related to routes for which the user holds a ticket such as a round-trip ticket or a commuter pass that can be purchased before using the bus from the information related to the usage history stored in the usage history memory unit 122 of the memory unit 12 in step S1-6 for a specified period, and then transmits the information excluding this from the communication unit 13 to the payment server 2 via the communication network N. In this case, the payment server 2 deducts the amount related to the fare information D7 for all information related to the usage history received from the usage history management server 1 from the credit card, electronic money, etc. related to the payment method information D12 that matches the user identification information D3, and the bus fares used by the user during the specified period are paid to the specified operator that operates the route, which is specified for each bus route, except for the usage history related to routes for which the user holds a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, i.e., routes for which the fare has already been paid.

[0074] In the case where a ticket that can be purchased before using a bus, such as a round-trip pass or a commuter pass, is closely linked to the use of a bus, for example, a bus commuter pass, it is preferable for the usage history management server 1 to determine whether the user has a ticket that can be purchased before using a bus, such as a round-trip pass or a commuter pass, for the route related to each usage history. On the other hand, in the case of a ticket that has little connection to bus use, such as a round-trip ticket that can be used on a wide range of transportation means other than buses, as described in the above embodiment, it is preferable for the payment server 2 to determine whether the user has a ticket that can be purchased before using the bus, such as a round-trip ticket or a commuter pass, for the route related to each usage history. In addition, it is possible to determine whether the passenger is eligible for both types of bus passes and which type to use depending on the type of ticket that can be purchased before using the bus, such as a round-trip ticket or a commuter pass.

[0075] [2 Variation 2: Application of pay-per-use charges to routes] The above example explains how to manage the usage history of buses on the same route, where the fare is a flat rate regardless of the section used, but it can also be applied to pay-per-ride routes, where the fare varies depending on the section traveled. Specifically, the following two methods can be considered.

[0076] [(1) When using location information acquired by the user device] The operation of this system (step S2A) when using location information acquired by the user terminal to support pay-per-use routes will be described with reference to the flowchart of FIG.

[0077] In this case, when getting on the bus, the user uses the operation unit 65 of the user terminal 6 to input the number of passengers on the bus and whether they are adults or children (step S1-1A), and then holds the user terminal 6 over the first short-range wireless communication tag 3 provided inside the bus, causing the tag reading unit 66 to read the first tag stored information D1 stored in the first short-range wireless communication tag 3 (step S1-2A). After reading the first tag stored information D1, the location information acquisition unit 67 of the user terminal 6 subsequently acquires the location information of the user terminal 6 (step S1-3A).

[0078] When the location information of the user terminal 6 is acquired by the location information acquisition unit 67, the control unit 61 of the user terminal 6 transmits the location information of the user terminal 6 acquired in step S1-3A (boarding location information D13) together with the number of passengers information D2, the first tag memory information D1, and the user identification information D3 from the communication unit 63 via the communication network N to the usage history management server 1 (step S1-4A).

[0079] In the usage history management server 1, which receives the first tag storage information D1, number of passengers information D2, user identification information D3, and boarding location information D13 transmitted from the user terminal 6 when the user boards the bus via the communication unit 13, the control unit 11 determines the authenticity of the received first tag storage information D1 (whether the information is regular information, i.e., information actually stored in the first short-range wireless communication tag 3 provided in the bus) (step S1-5A), and then identifies the route the user will board (step S1-6A). The methods for determining authenticity and identifying the boarding route are the same as those described in steps S1-4 and S1-5.

[0080] Next, the control unit 11 of the usage history management server 1 identifies the bus stop where the user boarded (step S1-7A). Specifically, the location information of each bus stop is stored in advance in the memory unit 12 of the usage history management server 1, and the control unit 11 compares the location information of the user terminal 6 at the time the user boarded, received in step S1-4A, with the location information of each bus stop stored in the memory unit 12, and identifies the bus stop closest to the location information of the user terminal 6 at the time the user boarded as the bus stop from which the user boarded. Also, for example, the bus stop located within a predetermined range from the location information of the user terminal 6 at the time the user boarded (the closest if there are multiple stops) may be identified as the bus stop from which the user boarded, and if there is no bus stop located within the predetermined range, the bus stop cannot be identified.

[0081] Next, the control unit 11 of the usage history management server 1 links the bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and information related to the bus stop where the user identified in step S1-7A boarded, and stores the information in the usage history memory unit 122 of the memory unit 12 (step S1-8A).

[0082] The subsequent steps from step S1-9A to step S1-12A are the same as those described in step S1-7 to step S1-10.

[0083] When the user gets off the bus, the user also holds the user terminal 6 over the first short-range wireless communication tag 3 provided in the bus, causing the tag reading unit 66 to read the first tag stored information D1 stored in the first short-range wireless communication tag 3 (step S1-13A). After the first tag stored information D1 is read, the location information acquiring unit 67 in the user terminal 6 subsequently acquires the location information of the user terminal 6 (step S1-14A).

[0084] When the location information of the user terminal 6 is acquired by the location information acquisition unit 67, the control unit 61 of the user terminal 6 transmits the location information of the user terminal 6 acquired in step S1-14A (location information at the time of disembarking D14) together with the first tag storage information D1 and the user identification information D3 from the communication unit 63 via the communication network N to the usage history management server 1 (step S1-15A).

[0085] In the usage history management server 1, which receives the first tag storage information D1, user identification information D3, and location information at the time of disembarking D14 sent from the user terminal 6 by the communication unit 13 when the user disembarks, the control unit 11 determines the authenticity of the received first tag storage information D1 (whether the information is legitimate information, i.e., information actually stored in the first short-range wireless communication tag 3 installed in the bus) (step S1-16A), and then identifies the bus stop where the user will disembark (step S1-17A). Specifically, in this case too, the location information of each bus stop is stored in advance in the memory unit 12 of the usage history management server 1, and the control unit 11 compares the location information of the user terminal 6 at the time the user disembarked, received in step S1-15A, with the location information of each bus stop stored in the memory unit 12, and identifies the bus stop closest to the location information of the user terminal 6 at the time the user disembarked as the bus stop where the user will disembark. This identifies both the bus stop where the user boards and the bus stop where the user disembarks, and identifies the user's travel section.

[0086] Next, the control unit 11 of the usage history management server 1 links the information related to the bus stop where the user identified in step S1-17A gets off and the fare information D7 stored in the usage history memory unit 122 of the memory unit 12 to the bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6 stored in step S1-8A and information related to the bus stop where the user identified in step S1-7A got on, and the fare information D7 (step S1-18A). In this case, the fare information D7 is determined by identifying the bus fare corresponding to the user's travel section (between the bus stop identified in step S1-7A and the bus stop identified in step S1-17A) and storing the amount of the fare. The amount of the fare can be determined by, for example, storing information related to a list of fare amounts corresponding to the travel section in advance in the storage unit 12 and then referencing the information.

[0087] As a result, the bus fare corresponding to the section traveled by the user is stored as fare information D7 in the usage history storage unit 122 of the storage unit 12 of the usage history management server 1, and therefore in step S3, the amount related to the fare information D7 stored in the usage history storage unit 122 of the storage unit 12 can be deducted from the credit card, electronic money, etc. related to the payment method information D12, thereby allowing the user to pay the fare corresponding to the section traveled by bus.

[0088] In addition, the transmission of location information when the user boards and disembarks to the usage history management server 1 does not necessarily have to be performed from the user terminal 6. For example, the bus vehicle may be equipped with a device including a location information acquisition means such as a GPS receiver, and the location information when the user terminal 6 reads the first tag storage information D1 from the first short-range wireless communication tag 3 may be transmitted from that device to the usage history management server 1.

[0089] [(2) When short-range wireless communication tags are installed at bus stops] The operation (step S2B) of this system when it corresponds to a pay-per-use route by installing the first short-range wireless communication tag 3 at the bus stop where passengers board and disembark from the bus will be described with reference to the flowchart in Figure 6.

[0090] In this case, the first short-range wireless communication tag 3 is provided at each bus stop instead of inside the bus, and first tag storage information D1A including bus stop identification information D1-3 is stored instead of the bus identification information D1-1. The bus stop identification information D1-3 is information that can identify the bus stop provided with the first short-range wireless communication tag 3 that stores information such as a number and an identifier assigned to each bus stop. In this case, the memory unit 12 of the usage history management server 1 stores bus stop list information, which is information in which the bus stop identification information D1-3 for each bus stop is linked to the bus stop name.

[0091] Before boarding a bus, the user inputs the number of passengers and whether they are adults or children using the operation unit 65 of the user terminal 6 at the bus stop where the user will board the bus (step S1-1B), and then holds the user terminal 6 over the first short-range wireless communication tag 3 provided at the bus stop, causing the tag reading unit 66 to read the first tag stored information D1A stored in the first short-range wireless communication tag 3 (step S1-2B). After reading the first tag stored information D1A, the control unit 61 of the user terminal 6 causes the communication unit 63 to transmit the number-of-passengers information D2, the first tag stored information D1A, and the user identification information D3 to the usage history management server 1 via the communication network N (step S1-3B).

[0092] In the usage history management server 1, which receives the first tag memory information D1A, number of passengers information D2, and user identification information D3 sent from the user terminal 6 when the user boards the bus via the communication unit 13, the control unit 11 determines the authenticity of the received first tag memory information D1 (whether the information is legitimate information, i.e., information actually stored in the first short-range wireless communication tag 3 installed in the bus) (step S1-4B), and then identifies the bus stop at which the user boards (step S1-5B). That is, the first tag memory information D1A includes stop identification information D1-3, which is information that can identify the stop equipped with the first short-range wireless communication tag 3 in which information such as the number and identifier assigned to each stop is stored, as described above, and the memory unit 12 of the usage history management server 1 stores stop list information, which is information in which the stop identification information D1-3 for each stop is linked to the stop name and stored.Therefore, the control unit 11 can identify the stop at which the user will board by extracting from the stop list information the stop name that is stored in linkage with the stop identification information D1-3 included in the first tag memory information D1A received in step S1-3B.

[0093] Next, the control unit 11 of the usage history management server 1 links the bus stop identification information D1-3, the number of passengers information D2, the user identification information D3, the usage date and time information D6, and the information related to the bus stop at which the user identified in step S1-5B boards, and stores the information in the usage history memory unit 122 of the memory unit 12 (step S1-6B).

[0094] Once step S1-6B is completed, the control unit 11 of the usage history management server 1 transmits the boarding availability information D8 from the communication unit 13 via the communication network N to the user terminal 6 that transmitted the information in step S1-3B (step S1-7B), and in the user terminal 6 that receives the boarding availability information D8 transmitted from the usage history management server 1 via the communication unit 63, the control unit 61 causes the display unit 64 to display a predetermined display indicating that the user is able to board (step S1-8B).

[0095] When the user gets off the bus, at the bus stop where the user got off, the user holds the user terminal 6 over the first short-range wireless communication tag 3 provided at the bus stop, and the tag reading unit 66 reads the first tag stored information D1A stored in the first short-range wireless communication tag 3 (step S1-9B). After reading the first tag stored information D1A, the control unit 61 of the user terminal 6 causes the communication unit 63 to transmit the first tag stored information D1A and the user identification information D3 to the usage history management server 1 via the communication network N (step S1-10B).

[0096] In the usage history management server 1, which receives the first tag storage information D1A and user identification information D3 sent from the user terminal 6 when the user disembarks via the communication unit 13, the control unit 11 determines the authenticity of the received first tag storage information D1A (whether the information is legitimate information, i.e., information actually stored in the first short-range wireless communication tag 3 installed at the bus stop) (step S1-11B), and then identifies the bus stop where the user disembarked (step S1-12B). In this case, the control unit 11 can identify the stop at which the user got off by extracting from the stop list information the stop name stored in association with the stop identification information D1-3 contained in the first tag storage information D1A received in step S1-10B. This identifies both the bus stop where the user boarded the bus and the bus stop where the user disembarked, and the user's travel section.

[0097] Next, the control unit 11 of the usage history management server 1 links the information related to the bus stop where the user identified in step S1-12B disembarked and the fare information D7 stored in the usage history memory unit 122 of the memory unit 12 to the bus stop identification information D1-3, number of passengers information D2, user identification information D3, usage date and time information D6 stored in step S1-6B and information related to the bus stop where the user identified in step S1-5B boards (step S1-13B). In this case, the fare information D7 is also obtained by identifying the bus fare corresponding to the user's travel section (between the bus stop identified in step S1-5B and the bus stop identified in step S1-12B) and storing the amount of the fare. The amount of the fare can be identified by, for example, storing information related to a list of fares corresponding to the travel section in advance in the storage unit 12 and then referencing the information.

[0098] As a result, the bus fare corresponding to the section traveled by the user is stored as fare information D7 in the usage history storage unit 122 of the storage unit 12 of the usage history management server 1, and therefore in step S3, the amount related to the fare information D7 stored in the usage history storage unit 122 of the storage unit 12 can be deducted from the credit card, electronic money, etc. related to the payment method information D12, thereby allowing the user to pay the fare corresponding to the section traveled by bus.

[0099] [3 Variation 3: Deleting multiple usage histories at once] In the above, when canceling the usage history in step S2, when the user holds the user terminal 6 over the second short-range wireless communication tag 4 in step S2-1, only the most recent usage history, i.e., the most recent usage date and time information D6, is deleted in step S2-5. However, it is also possible to delete multiple usage histories at once.

[0100] In this case, the user holds the user terminal 6 over the second short-range wireless communication tag 4 consecutively for the number of times that the user wants to delete the usage history within a predetermined time, and the control unit 61 of the user terminal 6 causes the tag reading unit 66 to read the second tag stored information D9 stored in the second short-range wireless communication tag 4 every time the user terminal 6 is held over the second short-range wireless communication tag 4. As a result, the user terminal 6 acquires the number of pieces of second tag stored information D9 that matches the number of times the user has held the user terminal 6 over the second short-range wireless communication tag 4.

[0101] Each time the tag reading unit 66 reads the second tag storage information D9, the control unit 61 of the user terminal 6 causes the communication unit 63 to transmit the read second tag storage information D9 together with the user identification information D3 to the usage history management server 1 via the communication network N.

[0102] In the usage history management server 1, when the communication unit 13 acquires the same second tag storage information D9 and user identification information D3 multiple times within a specified time period, the control unit 11 determines the authenticity of the second tag storage information D9 and identifies the route for which the user will cancel the usage history, and then deletes the usage history stored in the usage history storage unit 122 of the storage unit 12, i.e., the information stored in association with bus identification information D1-1, number of passengers information D2, user identification information D3, route information D5, usage date and time information D6, and fare information D7, in which the user identification information D3 matches the user identification information D3 received from the user terminal 6 and the route information D5 matches the route to be canceled as identified, starting with the most recent one, i.e., the one with the most recent usage date and time information D6, in the number that matches the number of times the same second tag storage information D9 and user identification information D3 were acquired within the specified time period.

[0103] This allows the user to cancel multiple usage histories at once, starting with the most recent one.

[0104] In the explanation of the above variant example 3, we have described a case where each time the second tag storage information D9 is read by the tag reading unit 66 of the user terminal 6, the read second tag storage information D9 is sent from the user terminal 6 to the usage history management server 1 together with the user identification information D3.However, instead of this, the user terminal 6 may count the number of second tag storage information D9 read within a specified period of time, and then link information related to the number of times such second tag storage information D9 was read within a specified period of time on the user terminal 6 to the second tag storage information D9 and the user identification information D3 and send it to the usage history management server 1. In this case, the usage history management server 1 deletes the usage histories whose number matches the information related to the number of reads of the second tag storage information D9 in the user terminal 6, starting with the most recent one.

[0105] [4 Variation 4: Deletion of Optional Usage History] In the above, when canceling the usage history in step S2, when the user holds the user terminal 6 over the second short-range wireless communication tag 4 in step S2-1, only the most recent usage history, i.e., the one with the most recent usage date and time information D6, is deleted in step S2-5. However, it is also possible for the user to select any usage history and delete only that usage history.

[0106] In this case, the usage history management server 1 transmits to the user terminal 6 a list of usage histories relating to the user using the user terminal 6, which is stored in the usage history storage unit 122 of the storage unit 12, and in the user terminal 6, the control unit 61 causes the display unit 64 to display the list of usage histories relating to the user. Note that the list of usage histories may include all past usage histories, but since this may be an enormous amount, only information relating to usage histories within a predetermined period may be transmitted from the usage history management server 1 to the user terminal 6 and displayed on the display unit 64.

[0107] Then, the user uses the operation unit 65 to select the usage history that they wish to cancel from the list of usage histories displayed on the display unit 64, and then holds the user terminal 6 over the second short-range wireless communication tag 4 to read the second tag memory information D9 stored in the second short-range wireless communication tag 4.

[0108] Then, in addition to the second tag storage information D9 and the user identification information D3, information relating to the usage history selected by the user and desired to be canceled is sent from the user terminal 6 to the usage history management server 1, and the usage history management server 1 identifies the usage history that the user wishes to cancel based on the received information, and then performs the cancellation process for that usage history (deleting the information stored in the usage history storage unit 122 of the storage unit 12 of the usage history management server 1).

[0109] This allows the user to delete any usage history, not just the most recent one.

[0110] [5 Variation 5: Application to transportation other than buses] The above describes the case where bus usage history is managed using the transportation usage history management system 100, but the transportation to which this system can be applied is not limited to buses, and it can also be used for other transportation as long as it can be equipped with a short-range wireless communication tag inside the transportation or at boarding and disembarking points such as bus stops.

[0111] For example, in the case of use on a railway, instead of automatic ticket gates, the ticket gates at the station can be equipped with a first short-range wireless communication tag 3 and a second short-range wireless communication tag 4, and the user's travel section can be identified in the same manner as described in (2) of Variant 2, and the user can pay the fare according to the section of the train they travel on.

[0112] [6 Variation 6: Use of storage media other than short-range wireless communication tags] In the above, we have described a case where short-range wireless communication tags (first short-range wireless communication tag 3 and second short-range wireless communication tag 4) are used as storage media for storing first tag storage information D1 and second tag storage information D9, which are installed inside a bus or at a bus stop. In this regard, it is preferable to use a short-range wireless communication tag because it takes less time for the user terminal 6 to read it and can be completed in a short time, especially when continuous reading is required as described in variant example 3. However, the information storage medium provided on board a bus or at a bus stop is not limited to a short-range wireless communication tag, as long as it can store the first tag storage information D1 or the second tag storage information D9 and be able to be read by the user terminal 6.

[0113] Examples of storage media that can be used other than short-range wireless communication tags include two-dimensional codes such as QR Code (registered trademark), and IC cards.

[0114] [7 Variation 7: Application to tickets other than round-trip tickets and commuter passes] In the above, we have given the explanation of round-trip tickets and commuter passes as examples of tickets that a user can purchase before using a means of transportation, but tickets that can be stored in advance in the memory unit 22 of the payment server 2 as information related to a means of transportation for which the user has already paid the fare, and that can be excluded from the usage history of a means of transportation for which the user has already paid the fare when the amount related to the fare information D7 is deducted from the credit card, electronic money, etc. related to the payment method information D12 during payment of the usage fare (step S3), are not limited to round-trip tickets or commuter passes.

[0115] For example, in addition to round-trip tickets and commuter passes, information relating to single-use tickets for which the user has paid in advance may be stored in the memory unit 22 of the payment server 2, and the usage history relating to routes for which such single-use tickets are held may also be excluded from the targets for which usage fees are paid in step S3. In addition, unlike round-trip tickets and commuter passes, a single-use ticket broadly includes tickets that expire after one use. For example, a ticket that can be used a specified number of times, such as a 10-use ticket, is also included in the category of a single-use ticket, since the ticket for that specific number of uses expires after one use.

[0116] In the case of single-ride tickets for which the fare has been paid in advance, the number of single-ride tickets that the user has purchased and paid for can be stored in the usage history management server 1 by type (for example, by route if the fare is uniform for each route, or by route and section if the fare varies for each section), and the usage history can be stored and canceled by increasing or decreasing the number.

[0117] For example, if a user has 10 single-ride tickets for a certain route (with a flat fare within the route), the usage history management server 1 stores in the memory unit 12 the number of single-ride tickets owned for that route (10), linked to information that can identify the user (user identification information D3) and information that can identify the route. In this case, the usage history management server 1 reduces the number of buses held when it acquires the first tag storage information D1 relating to a bus running on the route from the user terminal 6 held by the user (if it acquires first tag storage information D1 linked to passenger count information D2 for two people, it will subtract two from 10 to make it 8), and restores the number of buses held when the usage history relating to the first tag storage information D1 is canceled (if the usage history including passenger count information D2 for two people is canceled, it will add two to 8 to make it 10). In this way, when a user uses a form of transportation on a one-time basis, it is possible to accommodate both prepaid rides where the fare is paid in advance and postpaid rides where the fare is paid after the fact.

[0118] [8 Variation 8: Change in settlement frequency] In the above, in step S3-1, the information relating to the usage history stored in the usage history memory unit 122 of the memory unit 12 is sent in bulk from the usage history management server 1 to the payment server 2 at predetermined intervals, such as once every two weeks, and payment is made in bulk for the usage history during the predetermined period. However, the frequency of payment is not limited to this. For example, the information relating to the usage history may be sent from the usage history management server 1 to the payment server 2 each time the user uses public transportation, and each time the user uses the public transportation, it may be determined whether the user has paid the fare for that usage history, and payment of the fare is made only if it is determined that the fare has not been paid.

[0119] However, even when payment is made each time a use is made, in order to enable the cancellation of the usage history described in step S2 before payment, it is preferable that, after information relating to the usage history of the transportation facility is stored in the usage history memory unit 122 of the memory unit 12 in the usage history management server 1, the information is transmitted from the usage history management server 1 to the payment server 2 after a predetermined time has passed for the user to cancel the information.

[0120] [9 Variation 9: Automatic transition to commuter pass] In the above, we have explained a case where, at the time of payment of the usage fee in step S3, information relating to the usage history received in step S3-1 is excluded from information which indicates in step S3-2 that the user is in possession of a ticket that can be purchased before using the bus, such as a round-trip pass or a commuter pass, and then the usage fee is paid by deducting the amount relating to the fare information D7 for each usage history from the credit card, electronic money, etc. relating to the payment method information D12 that matches the user identification information D3.

[0121] In this case, the total amount related to the fare information D7 for each individual use will be deducted from the credit card, electronic money, etc. related to the payment method information D12. However, if the payment amount related to the usage history including the same user identification information D3 and the same route information D5 exceeds a predetermined amount (if the number of times a specific route is used by a specific user exceeds a predetermined number within a predetermined period), the fee structure for the use of that route by that user will automatically be switched to that of a commuter pass (a flat rate that is lower than the total amount related to the fare information D7), and the flat rate based on this commuter pass fee structure will be deducted from the credit card, electronic money, etc. related to the payment method information D12, instead of the total amount related to the fare information D7. This means that if a user uses the same route a specified number of times or more within a specified period, the usage fee will automatically be paid using the same commuter pass fee structure, which will benefit users who use the same route frequently. [Explanation of symbols]

[0122] 100 Transportation usage history management system 1. Usage history management server 11 control unit (first storage control means, second storage control means) 12 Storage unit (first storage means, second storage means) 13 Communication Department (first acquisition means, second acquisition means) 2. Payment Server 3. First short-range wireless communication tag (first storage medium) 4. Second short-range wireless communication tag (second storage medium) 5 Driver's terminal 6 User terminal (terminal device) N Communication Network D1, D1A First tag storage information (transportation usage information) D1-1 Bus identification information (identification information) D1-2 Authentication Information D1-3 Bus stop identification information D2 Number of passengers information (number of passengers information) D3 User Identity Information D4 Bus List Information D5 Route Information D6 Usage date and time information D7 Fare Information D8 Boarding information D9 Second tag storage information (transportation use cancellation information) D9-1 Bus identification information (identification information) D9-2 Authentication Information D9-3 Cancellation flag D10 Cancellation completion information D11 Tourist pass / commuter pass information D12 Payment method information D13 Location information when boarding D14 Location information when getting off

Claims

1. a first acquisition means for acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by a user; a second acquisition means for acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control means for causing a first storage means to store usage history information, which is information relating to the user's usage history of a transportation facility, when the first acquisition means acquires the transportation facility usage information; a second storage control means for deleting the usage history information stored in the first storage means when the second acquisition means acquires the transportation facility usage cancellation information; Equipped with The transportation facility use cancellation information is selected by a user on the terminal device, A transportation usage history management system characterized in that, after a predetermined period of time has passed, payment is made based on the usage history information for the predetermined period, excluding the usage history information that has been deleted by the second storage control means.

2. a list of the usage history information relating to the user who uses the terminal device stored in the first storage means is transmitted to the terminal device; 2. The transportation facility usage history management system according to claim 1, wherein the transportation facility usage cancellation information is selected from the list of the usage history information.

3. In a transportation usage history management method using a transportation usage history management system, a first acquisition step of acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by the user; a second acquisition step of acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control step of storing, in a first storage means, usage history information relating to a usage history of a transportation facility by the user when the first acquisition step acquires the transportation facility usage information; a second storage control step of deleting the usage history information stored in the first storage means when the second acquisition step acquires the transportation facility usage cancellation information; Including, The transportation facility use cancellation information is selected by a user on the terminal device, A transportation usage history management method characterized in that, after a predetermined period of time has passed, payment is made based on the usage history information for the predetermined period, excluding the usage history information that has been deleted by the second storage control step.

4. Computer, a first acquisition means for acquiring transportation facility use information, which is information indicating the use of a predetermined transportation facility, read from a storage medium by a terminal device used by the user; a second acquisition means for acquiring transportation facility use cancellation information, which is information indicating cancellation of use of a predetermined transportation facility read by the terminal device; a first storage control means for causing a first storage means to store usage history information, which is information relating to the user's usage history of a transportation facility, when the first acquisition means acquires the transportation facility usage information; a second storage control means for deleting the usage history information stored in the first storage means when the second acquisition means acquires the transportation facility usage cancellation information; It functions as The transportation facility use cancellation information is selected by a user on the terminal device, A transportation usage history management program characterized in that, after a predetermined period of time has passed, payment is made based on the usage history information for the predetermined period, excluding the usage history information that has been deleted by the second storage control means.

Images