Information processing device, fare adjustment program, and fare adjustment method

Abstract

To provide an information processing device, a fare settlement program and a fare settlement method, which allow for collecting fares while preventing stagnation of users while disembarking.SOLUTION: A settlement unit carries out settlement of fares of a transportation system while users are onboard the transportation system. A provision unit provides an image used for getting off the transport system to users upon completion of fare settlement by the settlement unit.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, a fare adjustment program, and a fare adjustment method. [Background technology]

[0002] When using public transport such as trains and buses, fares are paid when passengers get off the train. To systematize such fare payments, high processing speed is required. For this reason, fare payment systems using IC (integrated circuit) cards are known. For example, Patent Document 1 discloses a system in which charged (deposited) amount information is stored in an IC card, and the fare is paid by deducting the fare from the amount information stored in the IC card by touching the IC card to a reader in an automatic ticket gate. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2004-310683 A Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional fare payment systems using IC cards require users to carry an IC card, which makes their introduction difficult. There is also a risk of the IC card being lost.

[0005] Therefore, it is conceivable that the user's fare information could be managed in a server device, and when getting off the train, the user could access the server device from a user terminal such as a smartphone carried by the user, deduct the fare from the fare information, and pay the fare.

[0006] However, when a user gets off the train, the server device is accessed from the user terminal to carry out a process of deducting the fare from the amount information, which lengthens the processing time and causes the user to remain stuck after getting off the train.

[0007] The present disclosure aims to provide an information processing device, a fare settlement program, and a fare settlement method that can collect fares while preventing users from staying behind when getting off the train. [Means for solving the problem]

[0008] According to an embodiment of the present disclosure, there is provided an information processing device including a payment unit and a providing unit. The payment unit performs payment of a fare for a transportation facility while a user is riding on the transportation facility. When the payment unit completes payment of the fare, the providing unit provides the user with an image to be used when getting off the transportation facility. Effect of the Invention

[0009] According to one embodiment of the present disclosure, it is possible to collect fares while preventing users from staying behind after getting off the train. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a fare payment system according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the first embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a data configuration of ticket information according to the first embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a data configuration of the display mode information according to the first embodiment. [Diagram 5] FIG. 5 is a diagram illustrating a flow of purchasing a ticket in the fare payment system according to the first embodiment. [Figure 6] FIG. 6 is a flowchart illustrating an example of a procedure of the payment process according to the first embodiment. [Figure 7] FIG. 7 is a diagram illustrating the flow of payment of transportation fares using tickets in the fare payment system according to the first embodiment. [Figure 8]FIG. 8 is a diagram illustrating the flow of payment of transportation fares using tickets in the fare payment system according to the first embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a change in the display mode of the get-off image according to the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a change in a display mode in response to a touch operation on the image for getting off according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of sound output in response to a touch operation on the image for getting off according to the first embodiment. [Figure 12] FIG. 12 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the second embodiment. [Figure 13] FIG. 13 is a flowchart illustrating an example of a procedure of the payment process according to the second embodiment. [Figure 14] FIG. 14 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the third embodiment. [Figure 15] FIG. 15 is a flowchart illustrating an example of a procedure of the payment process according to the third embodiment. [Figure 16] FIG. 16 is a block diagram showing an example of the hardware configuration of the fare adjustment device according to the first to third embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the present embodiment will be described in detail with reference to the drawings. In this specification and the drawings, the same reference numerals are used to denote substantially the same components, and redundant description will be omitted.

[0012] The explanation will be given in the following order. 1. First embodiment 1.1. System configuration example 1.2. Example of functional configuration 1.3.Functional Flow 2. Second embodiment 2.1. Example of functional configuration 2.2. Functional Flow 3. Third embodiment 3.1. Example of functional configuration 3.2. Functional Flow 4. Hardware configuration example 5. Summary 6.Effects

[0013] <1. First embodiment> <<1.1. System configuration example>> First, a fare payment system including an information processing device of the present disclosure will be described. A fare payment system 10 according to a first embodiment is a system used for paying fares for transportation such as trains and buses. FIG. 1 is a diagram showing an example of a schematic configuration of the fare payment system 10 according to the first embodiment. The fare payment system 10 has a settlement device 11, a fare adjustment device 12, and a user terminal 13. In this embodiment, the fare adjustment device 12 corresponds to the information processing device of the present disclosure.

[0014] The payment device 11, the fare adjustment device 12, and the user terminal 13 are communicatively connected to a network N. As an embodiment of the network N, any type of communication network, whether wired or wireless, such as a mobile communication network such as a mobile phone, the Internet, a LAN (Local Area Network), or a VPN (Virtual Private Network) can be adopted. In the example of FIG. 1, the network N is provided with a base station N1 of a mobile communication network. The user terminal 13 is communicatively connected to the network N by mobile communication via the base station N1. Note that, although the example of FIG. 1 illustrates a case where one user terminal 13 is provided, this is not limiting, and any number of user terminals 13 can be used.

[0015] The payment device 11 is a device that executes a payment for a user. The payment device 11 is, for example, a computer such as a server computer. The payment device 11 may be implemented as one computer, or may be implemented by multiple computers. In this embodiment, the payment device 11 will be described as an example of one computer.

[0016] The payment device 11 is operated by a payment business operator. Examples of the payment business operator include a bank, a credit company, and a wallet business operator. For example, a user opens an account with a payment business operator and deposits money into the account. The payment device 11 performs payment from the user's account.

[0017] The fare adjustment device 12 is a device that provides a function for paying fares for transportation such as trains and buses. The fare adjustment device 12 is, for example, a computer such as a server computer. The fare adjustment device 12 may be implemented as a single computer, or may be implemented by multiple computers. In this embodiment, the fare adjustment device 12 will be described as an example of a single computer.

[0018] The user terminal 13 is a communication terminal device carried by a user. For example, the user terminal 13 is an information processing device such as a smartphone or a mobile terminal carried by a user. The user terminal 13 is provided with a camera. A user who uses a means of transport accesses the fare settlement device 12 using the user terminal 13 and pays the fare for the means of transport.

[0019] In the first embodiment, a payment service provider provides an application that can be used on a user terminal 13. The application is provided with a button linked to the fare settlement device 12. A user who uses a means of transport installs the application provided by the payment service provider into the user terminal 13. The user then uses the application on the user terminal 13 to access the fare settlement device 12 and pays the fare for the means of transport.

[0020] <<1.2. Functional configuration example>> Next, an example of the functional configuration of the fare adjustment device 12 will be described. Fig. 2 is a diagram showing an outline of the functional configuration of the fare adjustment device 12 according to the first embodiment. The fare adjustment device 12 has a communication unit 20, a storage unit 21, and a control unit 22.

[0021] (Communication Department 20) The communication unit 20 is a communication interface that communicates with the network N. The communication unit 20 transmits and receives various data to and from the payment apparatus 11 and the user terminal 13 via the network N.

[0022] (Storage unit 21) The storage unit 21 is a storage device such as a hard disk, a solid state drive (SSD), or an optical disk. The storage unit 21 may be a semiconductor memory capable of rewriting data, such as a random access memory (RAM), a flash memory, or a non-volatile static random access memory (NVSRAM). The storage unit 21 stores an operating system (OS) executed by the control unit 22 and various programs for executing various processes. Furthermore, the storage unit 21 stores various types of information. For example, the storage unit 21 stores ticket information 30 and display mode information 31. The storage unit 21 may store various other types of information.

[0023] (Ticket Information 30) Ticket information 30 is data that stores various information related to tickets that can be used as fares for transportation. FIG. 3 is a diagram showing an example of the data configuration of ticket information 30 according to the first embodiment. As shown in FIG. 3, ticket information 30 has the following items: "Ticket ID", "Owner user", "Transportation", "Type", "Purchase date", "Date of use", "Number of uses", "Maximum number of uses", "Number of days available for use", "Start date of use", and "End date of use". Note that each item of ticket information 30 shown in FIG. 3 is an example, and other items may be included.

[0024] The ticket ID field is an area for storing identification information for identifying a ticket. A unique ticket ID (identification) is assigned to the ticket as identification information. The ticket ID field stores the ticket ID assigned to the ticket. The owner user field is an area for storing the user who owns the ticket. A unique user ID is assigned to the user as identification information. The owner user field stores the user ID of the user who owns the ticket. The transportation field is an area for storing transportation for which the ticket can be used. A unique code is assigned to the transportation as identification information. The transportation field stores a code indicating the transportation for which the ticket can be used. The type field is an area for storing the type of ticket. In this embodiment, the types of tickets are "ST", "RT", "CP", and "XT". "ST" is a ticket that allows one ride on transportation. "RT" is a ticket that allows two rides on transportation, assuming a round trip by transportation. "CP" is a ticket intended for commuting by public transport and allows passengers to ride public transport for the period of use. "XT" is a ticket intended for use on public transport over multiple consecutive days for travel, etc. and allows passengers to ride public transport for multiple days. Below, "ST" tickets are also referred to as one-way tickets, "RT" tickets are also referred to as round-trip tickets, "CP" tickets are also referred to as commuter tickets, and "XT" tickets are also referred to as X-day tickets.

[0025] The purchase date field is an area that stores the date the ticket was purchased. The usage date field is an area that stores the date the ticket was used. In the case of one-way tickets and round-trip tickets, the date the transportation was used is stored in the usage date field, and in the case of X-day tickets, the date the use of the X-day ticket began is stored. For one-way tickets, round-trip tickets, and X-day tickets, when used, the date is stored in the usage date field. The number of uses field is an area that stores the number of times the ticket was used to board transportation. In the case of round-trip tickets, the number of times it was used is stored in the number of uses field. The maximum number of uses field is an area that stores the maximum number of times the ticket can be used to board transportation. In the case of round-trip tickets, two rides are possible, so the maximum number of uses field stores 2. The number of available days field is an area that stores the number of days the ticket can be used to board transportation. In the case of X-day tickets, the number of available days field stores the number of days the ticket can be used. The usage start date field is an area that stores the start date of the ticket usage period. The field for the start date of use stores the start date of the usage period for commuter tickets. The field for the end date of use stores the end date of the usage period for tickets. The field for the end date of use stores the end date of the usage period for commuter tickets.

[0026] In the example of FIG. 3, two one-way tickets, one round-trip ticket, one commuter ticket, and one X-day ticket are stored. The two one-way tickets, one round-trip ticket, and one X-day ticket are all unused tickets because no date is stored in the date of use field. The commuter ticket has a usage period from March 1, 2021 to March 31, 2021. The X-day ticket has a usable period of seven days.

[0027] (Display mode information 31) The display mode information 31 is data that stores the display mode of an image used for disembarking (hereinafter also referred to as "disembarking image"), which will be described later. FIG. 4 is a diagram showing an example of the data configuration of the display mode information 31 according to the first embodiment. As shown in FIG. 4, the ticket information 30 has the items of "transportation", "date", and "color". Note that the items of the display mode information 31 shown in FIG. 4 are merely examples, and other items may be included.

[0028] The transportation field is an area that stores the transportation for which the display mode of the disembarking image is to be changed. The transportation field stores a code indicating the transportation. The date field is an area that stores the date for which the display mode is to be changed. The background color field is an area that stores the color for which the display mode of the disembarking image is to be changed. The color field stores the color to be displayed on the disembarking image.

[0029] In the example in Figure 4, the transportation agency whose code is "001" is set to display red in the disembarking image on March 1, 2021.

[0030] (Control unit 22) The control unit 22 is a device that controls the entire fare settlement device 12. The control unit 22 is, for example, a processor. The control unit 22 has an internal memory for storing programs that define various processing procedures and control data, and executes various processes using these. The control unit 22 functions as various processing units by the operation of various programs. For example, the control unit 22 has a sales unit 40, a transportation facility identification unit 41, a determination unit 42, a settlement unit 43, and a provision unit 44.

[0031] (Sales Department 40) The sales unit 40 is a processing unit that controls the sale of tickets that can be used as fares for transportation. For example, the sales unit 40 transmits image information of a ticket purchase screen to the user terminal 13, and causes the user terminal 13 to display the ticket purchase screen. The ticket purchase screen displays tickets that can be purchased, and allows a purchase operation to purchase tickets. In this embodiment, one-way tickets, round-trip tickets, commuter tickets, and X-day tickets are sold from the ticket purchase screen. In response to a purchase operation on the ticket purchase screen, the sales unit 40 notifies the payment device 11 of the payment business operator of the price of the purchased ticket, and performs payment to purchase the ticket with the payment device 11. The sales unit 40 stores information on the purchased ticket in the ticket information 30.

[0032] (Transportation Specific Section 41) The transportation means identification unit 41 identifies the transportation means that the user will board. The transportation means identification unit 41 acquires information indicating the transportation means obtained from inside the transportation means. The transportation means identification unit 41 identifies the transportation means that the user will board from the acquired information indicating the transportation means. For example, a code image including a code indicating the transportation means is provided inside the transportation means such as a train or a bus. The code image may be a two-dimensional code image such as a QR (Quick Response) code, or a one-dimensional code image such as a barcode. When the user boards the transportation means, the user photographs the code image provided inside the transportation means with the user terminal 13. The user terminal 13 transmits information on the photographed code image to the fare adjustment device 12. The transportation means identification unit 41 of the fare adjustment device 12 identifies the transportation means that the user will board from the code indicating the transportation means included in the received code image. Note that the method of identifying the transportation means that the user will board is not limited to this. For example, in transportation means such as a train or a bus, a wireless device such as a beacon may be installed inside the transportation means, and a code indicating the transportation means may be transmitted from the wireless device. When the user boards a transportation facility, the user terminal 13 receives a code indicating the transportation facility. The user terminal 13 transmits the received code indicating the transportation facility to the fare adjustment device 12. The transportation facility identification unit 41 of the fare adjustment device 12 may identify the transportation facility that the user will board from the received code indicating the transportation facility.

[0033] (Judgment unit 42) The determination unit 42 determines whether any of the tickets in the ticket information 30 stored in the memory unit 21 is usable as the fare for the transportation mode identified by the transportation mode identification unit 41. For example, the determination unit 42 determines whether any of the tickets in the ticket information 30 is within the period in which the transportation mode identified by the transportation mode identification unit 41 can be used. If there is no ticket within the period in which the transportation mode can be used, the determination unit 42 further determines whether any unused ticket is usable as the fare for the transportation mode identified by the transportation mode identification unit 41.

[0034] (Payment Department 43) The payment unit 43 pays for the fare for the transportation facility while the user is riding on the transportation facility. For example, if the determination unit 42 determines that there is a usable ticket, the payment unit 43 updates the ticket in the ticket information 30 to "used" and pays for the fare for the transportation facility. For example, if the determination unit 42 determines that there is no ticket in the ticket information 30 within the period in which boarding is possible and there is an unused ticket that is usable, the payment unit 43 updates the unused ticket in the ticket information 30 to "used" and pays for the fare for the transportation facility.

[0035] (Providing Department 44) When the payment unit 43 completes the payment of the fare, the providing unit 44 provides the user with an image (disembarking image) to be used for disembarking from the transportation facility. For example, when the payment unit 43 completes the payment of the fare, the providing unit 44 transmits the disembarking image to the user terminal 13. When the determination unit 42 determines that there is a ticket within the period during which boarding is possible, the providing unit 44 transmits the disembarking image to the user terminal 13. On the other hand, when the determination unit 42 determines that there is no ticket within the period during which boarding is possible, the providing unit 44 transmits the disembarking image to the user terminal 13 when the payment unit 43 completes the payment of the fare. Furthermore, when the determination unit 42 determines that there are multiple unused tickets available, the providing unit 44 provides a selection screen for selecting a ticket to be used from the multiple unused tickets. Furthermore, the providing unit 44 provides, as the disembarking image, an image in which at least a part of the display mode is changed according to at least one of the date, the time period, the transportation facility, and the transportation facility line. For example, the providing unit 44 provides an image for getting off the train, at least a part of which is in the color of the color item, for each date and transportation means based on the display mode information 31.

[0036] The user terminal 13 displays the provided image to prove that the fare has been paid. At the transportation facility, a driver verifies that the user who owns the user terminal 13 has paid the fare by using the image displayed on the user terminal 13.

[0037] An example of the functional configuration of the fare adjustment device 12 according to this embodiment has been described above. Note that the above functional configuration described using FIG. 2 is merely an example. The functional configuration of the fare adjustment device 12 according to this embodiment is not limited to the above functional configuration. For example, the fare adjustment device 12 does not necessarily have all of the configuration shown in FIG. 2, and some of the configuration may be provided in a computer different from the fare adjustment device 12. In addition, the fare adjustment device 12 may have multiple configurations as a single configuration. The functional configuration of the fare adjustment device 12 according to this embodiment can be flexibly modified according to specifications and operation.

[0038] The functions of each component may be performed by a computing device such as a CPU (Central Processing Unit) reading a control program from a storage medium such as a ROM (Read Only Memory) or a RAM (Random Access Memory) that stores a control program describing the processing procedures for realizing these functions, and interpreting and executing the program. Therefore, the configuration to be used can be changed as appropriate depending on the technical level at the time of implementing this embodiment. An example of the hardware configuration of the fare settlement device 12 will be described later.

[0039] <<1.3.Functional Flow>> Next, the flow of various processes executed in the fare payment system 10 according to the first embodiment will be described. First, the flow of purchasing a ticket will be described. FIG. 5 is a diagram illustrating the flow of purchasing a ticket in the fare payment system 10 according to the first embodiment. When a user uses a payment service provider to pay for a transportation fare, the user opens an account with the payment service provider and deposits money into the account. The payment service provider sets authentication information for user authentication, such as a user ID and password, and notifies the user. The authentication information may be registerable by the user to the payment service provider.

[0040] A user installs an application provided by a payment service provider on the user terminal 13 owned by the user. The application accepts input of authentication information. The user operates the user terminal 13 and inputs the authentication information into the application. When the application accepts the authentication information, it performs user authentication, and becomes available for use once authenticated. Once authenticated, the application may store the authentication information and not require user authentication for a certain period of time. In addition, the application may perform user authentication when using a payment-related function such as purchasing a ticket.

[0041] In addition, when the payment business operator stores the telephone number of the user terminal 13 in association with each user, the application may transmit the telephone number of the user terminal 13 to the payment business operator, identify the user from the telephone number, and perform user authentication. For example, when the payment device 11 stores the telephone number of the user terminal 13 in association with each user, the application may transmit the telephone number of the user terminal 13 to the payment device 11, identify the user from the telephone number, and perform user authentication.

[0042] The application has a link button in the menu that links to the fare adjustment device 12. The application also has a browser function, and can display linked pages within the application.

[0043] A user who uses public transport operates user terminal 13 in advance to access fare adjustment device 12 by selecting a link button in the application menu. Fare adjustment device 12 displays a menu screen related to the payment of public transport fares on user terminal 13. The menu screen provides direct payment, ticket purchase, and ticket display. Direct payment is an item that specifies payment of the fare from the user's account. Ticket purchase is an item that specifies the purchase of tickets that can be used on public transport. Ticket display is an item that specifies the display of tickets that have already been purchased.

[0044] When purchasing a ticket, the user selects purchasing a ticket. When purchasing a ticket is selected, the sales unit 40 of the fare settlement device 12 transmits image information of a purchase screen on which the user can select the ticket to purchase. The purchase screen is displayed on the user terminal 13. The purchase screen displays tickets that can be purchased, and the user can select a ticket. For example, in FIG. 5, "Single trip", "Round trip", "Commuter", and "X-Day" are displayed as tickets that can be purchased. "Single trip" is a one-way ticket that can be used once. "Round trip" is a round trip ticket that can be used twice to make a round trip. "Commuter" is a commuter ticket that can be used for a certain period of time. "X-Day" is an X-day ticket that can be used for X days.

[0045] The user selects a ticket to purchase. If the selected ticket is a commuter ticket, the purchase screen displays an input area for the start date of the ticket's validity period and a selection area for selecting the ticket's validity period, for example, 30 days, 60 days, 90 days, etc. If the user selects a commuter ticket, the user inputs the start date of the ticket's validity period in the input area of ​​the purchase screen and selects the ticket's validity period in the selection area. The sales unit 40 transmits image information of the purchase screen displaying the price of the selected ticket. The purchase screen is displayed on the user terminal 13. The ticket purchase screen is provided with the price of the selected ticket and a decision button for confirming the purchase.

[0046] When the user wishes to purchase the selected ticket, the user selects the decision button. When the decision button is selected, the user terminal 13 returns to the application screen and displays a payment screen showing the price of the ticket. The payment screen is provided with a payment button. When the user wishes to make payment from the user's account at the payment business operator, the user selects the payment button. When the payment button is selected, the application transmits the price of the ticket to the payment device 11.

[0047] The settlement device 11 performs settlement by deducting the received ticket price from the amount information of the user's account. When the settlement is completed, the settlement device 11 notifies the user terminal 13 of the completion of the settlement.

[0048] When the user terminal 13 is notified that payment is complete, the application displays that payment is complete and notifies the fare adjustment device 12 that ticket payment is complete. When the sales unit 40 of the fare adjustment device 12 is notified that payment is complete, it stores information about the purchased ticket in the ticket information 30. Then, the sales unit 40 transmits image information of a ticket purchase completion screen. The ticket purchase completion screen is displayed on the user terminal 13.

[0049] Next, a flow of a payment process for paying a transportation fare with a ticket in the fare payment system 10 according to the first embodiment will be described. Fig. 6 is a flowchart showing an example of the procedure of the payment process according to the first embodiment. Figs. 7 and 8 are diagrams explaining the flow of paying a transportation fare with a ticket in the fare payment system 10 according to the first embodiment.

[0050] The application has a menu with a settlement button for paying the fare linked to the fare settlement device 12. A user who boards the transportation facility operates the user terminal 13 and selects the settlement button from the application menu before getting off. The application starts the camera when the settlement button is selected. For example, a code image including a code indicating the transportation facility is provided inside the transportation facility such as a train or bus. The user photographs the code image provided inside the transportation facility with the user terminal 13. The application transmits information of the photographed code image to the fare settlement device 12.

[0051] When the fare adjustment device 12 receives the information of the code image, the transportation facility identification unit 41 identifies the transportation facility that the user will board from the code indicating the transportation facility included in the received code image (step S10).

[0052] The determination unit 42 determines whether any of the tickets in the ticket information 30 stored in the memory unit 21 is usable as the fare for the transportation mode identified by the transportation mode identification unit 41. For example, the determination unit 42 determines whether any of the tickets in the ticket information 30 is within a period during which the transportation mode identified by the transportation mode identification unit 41 can be used.

[0053] In this embodiment, first, the determination unit 42 determines whether there is a commuter ticket or an X-day ticket within the period during which the transportation can be used (step S11). Specifically, the determination unit 42 determines whether there is a commuter ticket in which the transportation code is a code indicating the transportation included in the code image, and the user's boarding date is between the use start date and the use end date, or an X-day ticket in which the user's boarding date is within the number of available days from the date recorded as the use date, in the ticket information 30. The current system date may be used as the user's boarding date, or the boarding date may be received from the user terminal 13. If there is either a commuter ticket or an X-day ticket (step S11: Yes), the process proceeds to step S21 described later.

[0054] On the other hand, if there is neither a commuter ticket nor an X-day ticket (step S11: No), the determination unit 42 then determines whether there is a round-trip ticket in progress that can be used to board a means of transport (step S12). Specifically, the determination unit 42 determines whether there is a round-trip ticket in the ticket information 30, in which the code of the means of transport is included in the code image, the date of use is recorded, and the number of times of use has not reached the upper limit number of times. If there is a round-trip ticket (step S12: Yes), in order to process the boarding as using a round-trip ticket that has not reached the upper limit number of times of use, the settlement unit 43 counts up the number of times of use of the round-trip ticket that has not reached the upper limit number of times (step S13) by 1, and proceeds to step S21 described later.

[0055] On the other hand, if there is no in-use round-trip ticket (step S12: No), the determination unit 42 determines whether there is an unused ticket that can be used as the fare for the transportation identified by the transportation identification unit 41 (step S14) since there is no in-use ticket that can be used as the fare for the transportation. Specifically, the determination unit 42 determines whether there is a one-way ticket, a round-trip ticket, or an X-day ticket in the ticket information 30, in which the transportation code is a code indicating the transportation included in the code image and the date of use is not recorded. If there is none of these tickets, the determination unit 42 determines that there is no unused ticket. If there is no unused ticket (step S14: No), the provision unit 44 transmits information to the user terminal 13 that the fare cannot be paid with the ticket (step S15), and ends the process.

[0056] When the user terminal 13 receives information indicating that the fare cannot be paid with a ticket, the user terminal 13 displays a message indicating that the fare cannot be paid with a ticket. The user purchases a ticket or pays the fare in another manner, such as by cash.

[0057] If there is an unused ticket (step S14: Yes), the determination unit 42 determines whether there are multiple unused tickets (step S16). If there is only one unused ticket (step S16: No), the settlement unit 43 updates the unused ticket in the ticket information 30 to today's date as the date of use, thereby updating the ticket to "used," and settles the transportation fare (step S17).

[0058] If there are a plurality of unused tickets (step S16: Yes), the providing unit 44 transmits image information of a selection screen for selecting a ticket to be used from the plurality of unused tickets (step S18).

[0059] A selection screen is displayed on the user terminal 13. The user selects the ticket to be used to pay the fare from the selection screen.

[0060] The settlement unit 43 determines whether or not a ticket has been selected on the selection screen (step S19). If a ticket has not been selected (step S19: No), the settlement unit 43 waits for a ticket to be selected. If a ticket has been selected (step S19: Yes), the settlement unit 43 records today's date as the use date of the selected unused ticket in the ticket information 30, thereby updating it to used, and settles the fare for the transportation means (step S20).

[0061] The providing unit 44 provides the image for getting off the train to the user. For example, the providing unit 44 transmits the image for getting off the train to the user terminal 13 (step S21), and ends the process.

[0062] The user terminal 13 displays the received image for getting off the vehicle. When getting off the transportation vehicle, the user shows the displayed image to the driver. The driver confirms from the image displayed on the user terminal 13 that the user who has the user terminal 13 has already paid the fare.

[0063] As a result, if there is a commuter ticket or an X-day ticket within the period in which the means of transport can be used, if there is a round-trip ticket in progress that can be used to ride the means of transport, or if there is one unused ticket that can be used as the fare for the means of transport, when the user photographs a code image provided inside the means of transport with the user terminal 13, as shown in Fig. 7, an image for disembarking is displayed on the user terminal 13. In Fig. 7, "Accept" is displayed as the image for disembarking.

[0064] On the other hand, if there are no commuter tickets or X-day tickets within the period in which the transportation can be used, no partially used round-trip tickets that can be used to ride the transportation, and multiple unused tickets that can be used as transportation fares, as shown in FIG. 8, when the user photographs a code image provided inside the transportation vehicle with the user terminal 13, a selection screen is displayed on the user terminal 13. FIG. 8 displays the selection screen to select either "Single trip" or "Round trip." When a ticket is selected on the selection screen, an image for disembarking is displayed on the user terminal 13. In FIG. 8, "Accept" is displayed as the image for disembarking.

[0065] However, if the disembarking image is always the same, there is a risk that a user may take a screenshot of the screen displaying the disembarking image on the user terminal 13, thereby forging the image and allowing unauthorized boarding.

[0066] Therefore, the providing unit 44 provides an image in which at least a part of the display mode is changed according to at least one of the date, the time period, the transportation means, and the transportation line as the image for getting off. For example, the providing unit 44 provides an image for getting off in which at least a part of the image is the color of the color item for each date and transportation means based on the display mode information 31. FIG. 9 is a diagram for explaining an example of a change in the display mode of the image for getting off according to the first embodiment. For example, in the image for getting off, the background color of "Accept" is displayed in red for February 1, 2021, the background color of "Accept" is displayed in blue for February 2, 2021, and the background color of "Accept" is displayed in yellow for February 3, 2021. Note that in FIG. 9, a case where the background color of the characters is changed as a change in the display mode of the image for getting off is described, but the change in the display mode is not limited to this. The displayed characters, the color of the entire background, and the pattern may be changed. In addition, the date and time may be displayed in the image for getting off. In addition, the image for getting off may be a moving image in which a mark or the like moves.

[0067] The transportation company notifies the driver of the display format of the disembarking image in advance. The driver can confirm that the disembarking image displayed on the user terminal 13 is not a fake by checking whether the image is in the display format that was notified in advance, and thus fraudulent boarding can be prevented.

[0068] The providing unit 44 may provide, as the image for getting off, an image in which at least a part of the display mode changes in response to an operation. For example, the providing unit 44 provides an image in which at least a part of the color or display content of the image for getting off changes in response to a touch operation. FIG. 10 is a diagram for explaining an example of a change in the display mode in response to a touch operation of the image for getting off according to the first embodiment. For example, when the image for getting off is touched, the character portion of "Accept" vibrates. Note that, in FIG. 10, a case in which the character portion vibrates as a change in the display mode in response to a touch operation is described, but the change in the display mode is not limited to this. In response to a touch operation, a mark or the like may appear and disappear, and the color or pattern of the displayed characters or the entire background may be changed.

[0069] The transportation company notifies the driver in advance how the color and display content of the disembarking image will change in response to the touch operation. When disembarking, the driver or the user touches the disembarking image displayed on the user terminal 13. By checking whether the disembarking image displayed on the user terminal 13 is the change that was notified in advance, the driver can confirm that the image displayed on the user terminal 13 is not a counterfeit, and fraudulent boarding can be prevented.

[0070] The providing unit 44 may provide, as the image for getting off, an image from which a sound is output in response to an operation. For example, the providing unit 44 provides an image from which a sound is output in response to a touch operation. FIG. 11 is a diagram for explaining an example of sound output in response to a touch operation on the image for getting off according to the first embodiment. For example, when the image for getting off is touched, a sound such as a chime sound is output. Note that the sound output is not limited to a chime sound.

[0071] A transportation company notifies a driver in advance of the sound that will be output in response to a touch operation. When the driver or the user wants to get off the vehicle, the driver or the user touches the image for getting off that is displayed on the user terminal 13. The driver can confirm that the image for getting off that is displayed on the user terminal 13 is not a fake by checking whether the sound that will be output in response to a touch operation is the sound that was notified in advance, thereby preventing unauthorized boarding.

[0072] In this way, even when the fare is paid from an account, the fare settlement device 12 provides the user terminal 13 with an image for disembarking when the fare payment is completed. Before disembarking, the user can pay the fare and display the image for disembarking on the user terminal 13, and have the driver confirm it, which allows the user to disembark, thereby preventing the user from staying at the vehicle after disembarking. Furthermore, the driver can visually confirm the image displayed on the user terminal 13 by the transportation company to confirm that the user who owns the user terminal 13 has paid the fare, so transportation payment can be introduced without equipping the transportation company with a new device.

[0073] <2. Second embodiment> Next, a second embodiment will be described. In the second embodiment, a case will be described in which the fare for a transportation facility is paid from a user's account instead of a ticket. Also, in the second embodiment, a case will be described in which the fare is used to pay for a fixed-fare transportation facility in which the fare is a fixed amount, and for a variable-fare transportation facility in which the fare varies according to the distance traveled. The configuration of the fare payment system 10 according to the second embodiment is similar to that of the fare payment system 10 according to the first embodiment shown in FIG. 1, and therefore a description thereof will be omitted.

[0074] <<2.1. Example of functional configuration>> Fig. 12 is a diagram showing a schematic functional configuration of the fare adjustment device 12 according to the second embodiment. The fare adjustment device 12 according to the second embodiment has a configuration partially similar to that of the fare adjustment device 12 according to the first embodiment shown in Fig. 2, so similar components are denoted by similar reference numerals and explanations are omitted, and mainly different parts are explained.

[0075] (Storage unit 21) The storage unit 21 does not store ticket information 30, but further stores blacklist information 32. The blacklist information 32 is data that registers users who are denied boarding public transport. For example, in the blacklist information 32, users who have caused trouble, such as non-collection of fares, are registered as users who are denied boarding public transport. Note that, when there are multiple payment service providers, the blacklist information 32 may be stored for each payment service provider, or may be stored for multiple payment service providers.

[0076] (Control unit 22) The control unit 22 further has a fare type identification unit 45 and a derivation unit 46.

[0077] (Judgment unit 42) The determination unit 42 determines whether a user who boards a transportation facility is a user registered in the blacklist information 32. For example, when a user boards a transportation facility, information about the boarding user is transmitted from the user terminal 13 to the fare settlement device 12. The determination unit 42 identifies the user from the received information about the user, and determines whether the identified user is a user registered in the blacklist information 32. The determination unit 42 also determines from the received information whether the user has boarded the transportation facility and whether the fare has been settled. Note that, in the case where there are multiple payment service providers, the determination unit 42 determines whether the identified user is a user registered in the blacklist information 32 of the payment service provider requesting payment of the fare.

[0078] (Payment Department 43) The settlement unit 43 settles the transportation fare from the user's account. For example, the settlement unit 43 notifies the payment device 11 of the transportation fare, and the payment device 11 settles the transportation fare from the user's account.

[0079] (Providing Department 44) When the payment unit 43 completes payment of the fare, the providing unit 44 provides the user with an image for disembarking from the transportation facility. For example, the providing unit 44 provides an image in which at least a part of the display mode is changed according to at least one of the date, the time period, the transportation facility, and the transportation facility line as the image for disembarking. For example, the providing unit 44 provides an image for disembarking in which at least a part of the image is the color of the color item based on the display mode information 31 for each date and transportation facility.

[0080] Furthermore, when a user who boards a transportation facility is a user registered in the blacklist information 32, the providing unit 44 notifies the user that boarding is denied. For example, when the determining unit 42 determines that the user is a user registered in the blacklist information 32, the providing unit 44 notifies the user terminal 13 that boarding is denied.

[0081] (Freight Type Specific Section 45) The fare type identification unit 45 identifies whether the fare of the transportation to be boarded is a fixed fare type or a variable fare type that varies depending on the distance traveled. For example, the fare settlement device 12 is notified of information for determining whether the fare of the transportation to be boarded by the user is a fixed fare type or a variable fare type from the user terminal 13. The notified information may be fare type information indicating whether the fare is a fixed fare type or a variable fare type, or may be boarding transportation information indicating the transportation to be boarded. When the notified information is fare type information, the fare type identification unit 45 identifies whether the fare is a fixed fare type or a variable fare type from the notified fare type information. On the other hand, when the notified information is boarding transportation information, the fare settlement device 12 stores in the storage unit 21, as master data of the transportation, whether the fare of the transportation is a fixed fare type or a variable fare type for each transportation. The fare type identification unit 45 identifies whether the fare of the transportation of the notified boarding transportation information is a fixed fare type or a variable fare type from the master data stored in the storage unit 21.

[0082] (Derivation part 46) When the fare type identification unit 45 identifies the fare as a variable fare type, the derivation unit 46 derives the fare from the boarding section of the transportation to be boarded. For example, when the fare is a variable fare type transportation, the fare settlement device 12 is notified of information on the boarding point and the alighting point as the boarding section of the transportation to be boarded from the user terminal 13. The derivation unit 46 derives the fare from the boarding section from the notified information on the boarding section. For example, the derivation unit 46 inputs the boarding point and the alighting point to an existing fare calculation system and derives the fare using the fare calculation system. Note that the fare settlement device 12 may store fare information in which fares are registered for each combination of the boarding point and the alighting point of the transportation in the storage unit 21, and the derivation unit 46 may derive the fare by calculating the fare corresponding to the notified boarding point and alighting point from the fare information.

[0083] <<2.2. Functional flow>> Next, a description will be given of the flow of a payment process for paying a transportation fare using the fare payment system 10 according to the second embodiment. Fig. 13 is a flowchart showing an example of the procedure of the payment process according to the second embodiment.

[0084] The transportation facility has a communication device installed at the boarding gate where the user boards, capable of communicating with the user terminal 13. The communication device is set to determine whether the fare for the transportation facility is a fixed fare type or a variable fare type. When the user terminal 13 touches the communication device, the communication device notifies the user terminal 13 of fare type information indicating whether the fare is a fixed fare type or a variable fare type, for example, via short-range wireless communication such as Bluetooth (registered trademark). Furthermore, when the fare is a variable fare type, the communication device notifies the user terminal 13 of boarding point information indicating the boarding point via short-range wireless communication. Note that the communication device may be set with boarding transportation facility information indicating the transportation facility, and notify the user terminal 13 of the set boarding transportation facility information via short-range wireless communication.

[0085] When boarding a transportation facility, the user touches the user terminal 13 to the communication device at the boarding gate. The user terminal 13 transmits information notified by the communication device via short-range wireless communication to the fare adjustment device 12 together with authentication information and a telephone number. For example, the user terminal 13 receives fare type information, boarding transportation facility information, and boarding location information from the communication device via short-range wireless communication. The user terminal 13 transmits the received fare type information, boarding transportation facility information, and boarding location information to the fare adjustment device 12 together with authentication information and a telephone number. The fare type information or boarding transportation facility information may be transmitted from a wireless device such as a beacon installed inside the transportation facility. The fare type, the transportation facility the user will board, and the boarding location may be input by the user to the user terminal 13.

[0086] The determination unit 42 of the fare adjustment device 12 determines whether or not the user has boarded the vehicle based on the received information (step S50). For example, when the determination unit 42 receives fare type information or boarding transportation facility information, the determination unit 42 determines that the user has boarded the vehicle.

[0087] When it is determined that the user has boarded the vehicle upon receiving the fare type information or the boarding transportation information (step S50: Yes), the determination unit 42 identifies the user based on the authentication information and the phone number received together with the fare type information or the boarding transportation information (step S51). The determination unit 42 determines whether the identified user is a user registered in the blacklist information 32 (step S52). If the identified user is a user registered in the blacklist information 32 (step S52: Yes), the provision unit 44 presents the user with a message that boarding is denied (step S53). For example, the provision unit 44 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process.

[0088] When the user terminal 13 receives the screen information indicating that boarding is denied, the user terminal 13 displays a message indicating that boarding is denied. This makes it possible to prevent users registered in the blacklist information 32 from boarding the vehicle.

[0089] On the other hand, if the user is not registered in the blacklist information 32 (step S52: No), the fare type identification unit 45 identifies whether the fare is a fixed fare type or a variable fare type from the received fare type information or boarded transportation information (step S54). For example, when the fare type identification unit 45 receives fare type information, it identifies whether the fare is a fixed fare type or a variable fare type from the fare type information. When the fare type identification unit 45 receives boarded transportation information, it identifies whether the fare of the transportation in the boarded transportation information is a fixed fare type or a variable fare type from the master data stored in the memory unit 21.

[0090] The determination unit 42 determines whether the specified fare is a fixed fare type (step S55). If the fare is a variable fare type and not a fixed fare type (step S55: No), the process ends. If the fare is a variable fare type, the fare will be settled later.

[0091] On the other hand, if the fare is a flat-rate fare (step S55: Yes), the settlement unit 43 notifies the fare to the business that executes the settlement for the user, and the business executes the settlement of the fare. For example, the settlement unit 43 transmits the fare, authentication information, and telephone number to the settlement device 11 of the settlement business (step S56).

[0092] The settlement unit 43 judges whether a response of the completion of the settlement is received from the settlement device 11 (step S57). If the response is not received (step S57: No), the settlement unit 43 waits for the reception of the response. For a fixed-fare type transportation facility, the fare may be stored in the master data, or may be received from the user terminal 13.

[0093] The payment device 11 identifies the user from the received authentication information and telephone number, and performs payment by deducting the fare from the amount information of the account of the identified user. When the payment is completed, the payment device 11 responds that the payment is complete, and when the fare cannot be deducted, the payment device 11 responds that the payment is not possible.

[0094] When a response is received from the payment device 11 (step S57: Yes), the providing unit 44 judges whether the response indicates that the payment is complete (step S58). When the response indicates that the fare cannot be paid (step S58: No), the providing unit 44 transmits a message to the user terminal 13 indicating that the fare cannot be paid (step S59), and ends the process.

[0095] On the other hand, if the answer is that the payment is completed (step S58: Yes), the providing unit 44 provides the user with an image for disembarking from the transportation facility. For example, the providing unit 44 transmits an image for disembarking in which at least a part of the image is the color of the color item for each date and transportation facility based on the display mode information 31 (step S60), and ends the process.

[0096] When the user terminal 13 receives information indicating that the fare cannot be paid, it displays that the fare cannot be paid. The user pays the fare by another method, such as by cash. On the other hand, when the user terminal 13 receives an image for getting off the train, it displays the received image for getting off the train.

[0097] On the other hand, if the fare is a variable fare type, when the user gets off the transportation facility, the user inputs the alighting point into the user terminal 13. The user terminal 13 transmits boarding point information and alighting point information indicating the alighting point to the fare settlement device 12. Note that if the boarding point information has already been transmitted at the time of boarding, transmission may be omitted.

[0098] If the received information is boarding point information or disembarking point information, the determination unit 42 of the fare settlement device 12 determines that the passenger has disembarked (step S61) because the received information is not fare type information or boarding transportation facility information (step S50: No). Note that the determination unit 42 may also determine that the passenger has disembarked because the received information is boarding point information or disembarking point information.

[0099] The derivation unit 46 derives the fare from the boarding section of the transportation means to be boarded (step S62). For example, the derivation unit 46 derives the fare from the boarding point in the boarding point information to the alighting point in the alighting point information. For example, the derivation unit 46 inputs the boarding point and the alighting point to an existing fare calculation system, and derives the fare using the fare calculation system. Note that, when fare information in which fares are registered for each combination of the boarding point and the alighting point is stored in the memory unit 21, the derivation unit 46 may derive the fare by finding the fare corresponding to the boarding point and the alighting point from the fare information.

[0100] The settlement unit 43 notifies the business operator who executes the settlement for the user of the fare, and the business operator executes the settlement of the fare. For example, the settlement unit 43 transmits the fare derived by the derivation unit 46, the authentication information, and the telephone number to the settlement device 11 of the settlement business operator (step S63). The settlement unit 43 determines whether a response to the completion of settlement has been received from the settlement device 11 (step S64). If the settlement unit 43 has not received a response (step S64: No), it waits for the reception of the response.

[0101] The payment device 11 identifies the user from the received authentication information and telephone number, and performs payment by deducting the fare from the amount information of the account of the identified user. When the payment is completed, the payment device 11 responds that the payment is complete, and when the fare cannot be deducted, the payment device 11 responds that the payment is not possible.

[0102] When a response is received from the payment device 11 (step S64: Yes), the providing unit 44 judges whether the response indicates that the payment is complete (step S65). When the response indicates that the fare cannot be paid (step S65: No), the providing unit 44 transmits a message to the user terminal 13 indicating that the fare cannot be paid (step S66), and ends the process.

[0103] On the other hand, if the answer is that the payment is completed (step S65: Yes), the providing unit 44 provides the user with an image for getting off the transportation facility. For example, the providing unit 44 transmits an image for getting off the transportation facility, at least a part of which is the color of the color item, for each date and transportation facility based on the display mode information 31 (step S67), and ends the process.

[0104] When the user terminal 13 receives information indicating that the fare cannot be paid, it displays that the fare cannot be paid. The user pays the fare by another method, such as by cash. On the other hand, when the user terminal 13 receives an image for getting off the train, it displays the received image for getting off the train.

[0105] In this way, the fare adjustment device 12 according to the present embodiment can collect fares while preventing users from staying at the transportation facility after getting off, regardless of whether the transportation facility fare is a fixed fare type or a variable fare type. In addition, the fare adjustment device 12 can prevent users registered in the blacklist information 32 from boarding the transportation facility.

[0106] <3. Third embodiment> Next, a third embodiment will be described. In the third embodiment, a case where a plurality of pieces of blacklist information are included will be described. The configuration of the fare payment system 10 according to the third embodiment is similar to that of the fare payment system 10 according to the first embodiment shown in FIG. 1, and therefore the description thereof will be omitted.

[0107] <<3.1. Example of functional configuration>> Fig. 14 is a diagram showing a schematic functional configuration of the fare adjustment device 12 according to the third embodiment. The fare adjustment device 12 according to the third embodiment has a configuration partially similar to that of the fare adjustment device 12 according to the first and second embodiments shown in Fig. 2 and Fig. 12, so similar components are denoted by similar reference numerals and descriptions are omitted, and mainly different parts are described.

[0108] (Storage unit 21) The storage unit 21 further stores first blacklist information 33 and second blacklist information 34 instead of the blacklist information 32. The first blacklist information 33 is data that registers users who are refused boarding fixed-fare and variable-fare transportation. For example, the first blacklist information 33 registers users who should be highly cautious, such as users who cannot make payments with a payment service provider and users who are refused use of transportation. The second blacklist information 34 is data that registers users who should be highly cautious, such as users who cannot make payments with a payment service provider and users who are refused use of transportation. The second blacklist information 34 registers users who should be highly cautious, such as users who cannot make payments with a payment service provider and users who are refused use of transportation. The second blacklist information 34 registers users who have unpaid fares but should be low in the degree of caution. In addition, when there are multiple payment service providers, the first blacklist information 33 and the second blacklist information 34 may be stored for each payment service provider, or may be stored for multiple payment service providers. If there are multiple payment service providers, the judgment unit 42 judges whether the identified user is a user registered in the first blacklist information 33 and the second blacklist information 34 of the payment service provider requesting payment of the fare.

[0109] (Providing Department 44) When a user who boards a transportation facility is a user registered in the first blacklist information 33, the providing unit 44 notifies the user that boarding is denied. In addition, when a user who boards a transportation facility is a user registered in the second blacklist information 34, the providing unit 44 notifies the user that boarding of the transportation facility with a variable fare is denied.

[0110] <<3.2. Functional flow>> Next, the flow of payment processing for paying transportation fares using the fare payment system 10 according to the third embodiment will be described. Fig. 15 is a flow chart showing an example of the procedure of the payment processing according to the third embodiment. The procedure of the payment processing according to the third embodiment is partially similar to the procedure of the payment processing according to the second embodiment shown in Fig. 13, so similar processing parts are given the same reference numerals and their explanations are omitted, and mainly different processing parts will be described.

[0111] When the user is identified in step S51, the determination unit 42 determines whether the identified user is a user registered in the first blacklist information 33 (step S70). If the identified user is a user registered in the first blacklist information 33 (step S70: Yes), the provision unit 44 presents the user with a message that boarding is denied (step S71). For example, the provision unit 44 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process. On the other hand, if the identified user is not a user registered in the first blacklist information 33 (step S70: No), the process proceeds to step S54.

[0112] Furthermore, if the fare is a flat-rate fare (step S55: Yes), the judgment unit 42 judges whether the identified user is a user registered in the second blacklist information 34 (step S72). If the identified user is a user registered in the second blacklist information 34 (step S72: Yes), the provision unit 44 presents the user with a notice that boarding is denied (step S73). For example, the provision unit 44 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process. On the other hand, if the identified user is not a user registered in the second blacklist information 34 (step S72: No), the process proceeds to step S56.

[0113] In this way, the fare adjustment device 12 according to this embodiment can permit or deny a user who should be wary from boarding fixed-fare and variable-fare public transportation services depending on the degree of wariness.

[0114] <4. Hardware configuration example> Next, a hardware configuration example of the fare adjustment device 12 according to the first to third embodiments will be described. FIG. 16 is a block diagram showing a hardware configuration example of the fare adjustment device 12 according to the first to third embodiments. Referring to FIG. 16, the fare adjustment device 12 has, for example, a processor 801, a ROM 802, a RAM 803, a host bus 804, a bridge 805, an external bus 806, an interface 807, an input device 808, an output device 809, a storage 810, a drive 811, a connection port 812, and a communication device 813. Note that the hardware configuration shown here is an example, and some of the components may be omitted. In addition, components other than those shown here may be further included.

[0115] (Processor 801) The processor 801 functions, for example, as an arithmetic processing device or control device, and controls all or part of the operation of each component based on various programs recorded in the ROM 802, the RAM 803, the storage 810, or the removable recording medium 901.

[0116] (ROM802, RAM803) The ROM 802 is a means for storing the programs to be read into the processor 801, data to be used for calculations, etc. The RAM 803 temporarily or permanently stores, for example, the programs to be read into the processor 801, various parameters that change appropriately when the programs are executed, etc.

[0117] (host bus 804, bridge 805, external bus 806, interface 807) The processor 801, ROM 802, and RAM 803 are connected to each other via, for example, a host bus 804 capable of high-speed data transmission. On the other hand, the host bus 804 is connected to an external bus 806 having a relatively low data transmission speed via, for example, a bridge 805. In addition, the external bus 806 is connected to various components via an interface 807.

[0118] (Input device 808) Examples of the input device 808 include a mouse, a keyboard, a touch panel, a button, a switch, and a lever. Furthermore, a remote controller capable of transmitting control signals using infrared rays or other radio waves may be used as the input device 808. The input device 808 also includes an audio input device such as a microphone.

[0119] (Output Device 809) The output device 809 is a device capable of visually or audibly notifying the user of acquired information, such as a display device such as a CRT (Cathode Ray Tube), LCD, or organic EL, an audio output device such as a speaker or a headphone, a printer, a mobile phone, a facsimile, etc. The output device 809 according to this embodiment also includes various vibration devices capable of outputting tactile stimuli.

[0120] (Storage 810) The storage 810 is a device for storing various types of data. For example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device may be used as the storage 810.

[0121] (Drive 811) The drive 811 is a device that reads information recorded on a removable recording medium 901 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, and writes information to the removable recording medium 901.

[0122] (Connection port 812) The connection port 812 is a port for connecting an external device 902, such as a Universal Serial Bus (USB) port, an IEEE1394 port, a Small Computer System Interface (SCSI), an RS-232C port, or an optical audio terminal.

[0123] (Communication device 813) The communication device 813 is a communication device for connecting to a network, such as a communication card for wired or wireless LAN, Bluetooth (registered trademark), or WUSB (Wireless USB), a router for optical communications, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various types of communications.

[0124] (Removable recording media 901) The removable recording medium 901 is, for example, a DVD medium, a Blu-ray (registered trademark) medium, an HD DVD medium, various semiconductor storage media, etc. Of course, the removable recording medium 901 may be, for example, an IC card equipped with a non-contact type IC chip, or an electronic device.

[0125] (External connection device 902) The external connection device 902 is, for example, a printer, a portable music player, a digital camera, a digital video camera, or an IC recorder.

[0126] The storage unit 21 according to the present embodiment is realized by the ROM 802, the RAM 803, and the storage 810. The control unit 22 according to the present embodiment, which is realized by the processor 801, reads out and executes each control program that realizes the sales unit 40, the transportation facility identification unit 41, the determination unit 42, the settlement unit 43, the provision unit 44, the fare type identification unit 45, and the derivation unit 46 from the ROM 802, the RAM 803, etc. The communication unit 110 according to the present embodiment reads out data from the ROM 802, the RAM 803, etc., and transmits the data to the communication device 813 via the host bus 804, the bridge 805, the external bus 806, and the interface 807, thereby transmitting the data to the external device. The communication unit 110 writes the data received by the communication device 813 to the ROM 802 or the RAM 803 via the interface 807, the external bus 806, the bridge 805, and the host bus 804, and receives data from the external device.

[0127] <5. Summary> As described above, the fare settlement device 12 has the settlement unit 43 and the provision unit 44. The settlement unit 43 settles the fare for the transportation facility while the user is riding on the transportation facility. When the settlement unit 43 completes the settlement of the fare, the provision unit 44 provides the user with an image for getting off the transportation facility.

[0128] This allows the fare adjustment device 12 to collect fares while preventing users from staying behind after getting off the train.

[0129] Although the preferred embodiment of the present disclosure has been described in detail above with reference to the attached drawings, the technical scope of the present disclosure is not limited to such examples. It is clear that a person having ordinary knowledge in the technical field of the present disclosure can conceive of various modified or amended examples within the scope of the technical ideas described in the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure.

[0130] For example, in the above embodiment, the fare settlement device 12 displays an image on an application provided by a payment service provider. However, the present invention is not limited to this. The fare settlement device 12 may provide each function of the sales unit 40, the transportation means identification unit 41, the determination unit 42, the settlement unit 43, the provision unit 44, the fare type identification unit 45, and the derivation unit 46 as an API (Application Programming Interface) that can be called from an external device. The application may also be created by the payment service provider on a screen related to fare payment, and the application may execute each function of the sales unit 40, the transportation means identification unit 41, the determination unit 42, the settlement unit 43, the provision unit 44, the fare type identification unit 45, and the derivation unit 46 by calling the API of the fare settlement device 12 in response to an operation on the screen related to fare payment.

[0131] In the above embodiment, the fare adjustment device 12 is described as an information processing device of the present disclosure. However, this is not limited to this. The user terminal 13 may be the information processing device of the present disclosure. For example, an application that has the functions of the sales unit 40, the transportation means identification unit 41, the determination unit 42, the settlement unit 43, the provision unit 44, the fare type identification unit 45, and the derivation unit 46 and performs fare settlement may be installed in the user terminal 13, and the user terminal 13 may execute the functions of the sales unit 40, the transportation means identification unit 41, the determination unit 42, the settlement unit 43, the provision unit 44, the fare type identification unit 45, and the derivation unit 46.

[0132] <6. Effects> As described above, the information processing device (fare adjustment device 12, user terminal 13) may have the following configuration and provide various effects. However, the effects described in this specification are merely descriptive or exemplary and are not limiting. In other words, the technology disclosed herein may provide other effects that are apparent to a person skilled in the art from the description of this specification, in addition to or in place of the above effects.

[0133] (1) a payment unit 43 for allowing a user to pay for a fare for a transportation facility while riding the transportation facility; a provision unit 44 that provides the user with an image (disembarking image) to be used when disembarking from the transportation facility when the fare payment is completed by the payment unit 43; An information processing device having the above configuration.

[0134] This enables the information processing device to collect fares while preventing users from staying behind when getting off the train.

[0135] (2) The providing unit 44 provides an image in which at least a part of the display mode is changed according to at least one of the date, the time period, the transportation facility, and the route of the transportation facility, as the image used for getting off the train. An information processing device as described in (1).

[0136] This enables the information processing device to prevent unauthorized boarding.

[0137] (3) The provision unit 44 provides, as the image used for getting off, an image whose display state at least in part changes in response to an operation. An information processing device according to (1) or (2).

[0138] This enables the information processing device to prevent unauthorized boarding.

[0139] (4) A memory unit 21 that stores ticket information 30 indicating tickets that can be used as fares for transportation; A transportation facility identification unit 41 that identifies the transportation facility in which the user boards; The determination unit 42 further includes a determination unit 42 that determines whether the ticket information 30 includes a ticket for a period during which the transportation facility identified by the transportation facility identification unit 41 can be used; The providing unit 44 provides the user with an image to be used for disembarking when the determining unit 42 determines that the user has a ticket within the period during which the user can board the train. An information processing device according to any one of (1) to (3).

[0140] As a result, if there is a ticket for the period during which the transportation can be used, the information processing device can pay the fare using the ticket for the period during which the transportation can be used.

[0141] (5) If there is no ticket within the period during which travel is permitted, the determination unit 42 further determines whether there is an unused ticket in the ticket information 30 that can be used as the fare for the transportation facility identified by the transportation facility identification unit 41; If there is an unused ticket available as a result of the determination by the determination unit 42, the settlement unit 43 updates the unused ticket in the ticket information 30 to a used ticket and settles the fare for the transportation means. (4) An information processing device.

[0142] As a result, if there is no ticket within the period during which the transportation can be used, the information processing device can settle the fare with an unused ticket that can be used as the fare for the transportation.

[0143] (6) The transportation facility identification unit 41 identifies the transportation facility that the user will board from information indicating the transportation facility obtained from inside the transportation facility. An information processing device according to (4) or (5).

[0144] This allows the information processing device to identify the transportation facility that the user will board, even if the user does not specify it.

[0145] (7) The transportation facility identification unit 41 identifies the transportation facility in which the user boards from the code obtained by photographing a code image provided inside the transportation facility, the code including a code indicating the transportation facility. An information processing device according to any one of (4) to (6).

[0146] In this way, the information processing device can identify the transportation facility that the user is riding in by photographing a code image provided inside the transportation facility. Also, since the transportation facility only needs to place the code image inside the vehicle, the introduction cost can be reduced.

[0147] (8) a fare type identification unit 45 that identifies whether the fare of the transportation to be used is a fixed fare type or a variable fare type that varies depending on the travel distance; and a derivation unit 46 for deriving a fare from a boarding section of the transportation facility when the fare type determination unit 45 determines that the fare is the variable fare type. When the fare type identification unit 45 identifies the fare as the fixed fare type, the settlement unit 43 notifies the fixed fare of the transportation facility to the business operator who executes the settlement for the user, and when the fare type identification unit 45 identifies the fare as the variable fare type, the settlement unit 43 notifies the business operator of the fare derived by the derivation unit 46. An information processing device according to any one of (1) to (7).

[0148] This allows the information processing device to collect the fare while preventing users from staying behind when getting off the train, even if the fare is a fixed fare type or a variable fare type.

[0149] (9) The device further includes a storage unit 21 for storing first blacklist information 33 that registers users who are denied boarding of fixed-fare and variable-fare transportation means, and second blacklist information 34 that registers users who are denied boarding of variable-fare transportation means, The provision unit 44, when a user who has boarded the transportation facility is a user registered in the first blacklist information 33, presents the user with a notice that boarding will be denied, and when a user who has boarded the transportation facility is a user registered in the second blacklist information 34, presents the user with a notice that boarding of the transportation facility with a variable fare will be denied. An information processing device according to any one of (1) to (8).

[0150] This allows the information processing device to permit or deny rides on fixed-fare and variable-fare public transportation for users who should be wary, depending on the degree of caution they should be aware of. [Explanation of symbols]

[0151] 10 Fare payment system 11 Payment device 12 Fare settlement device 13 User terminal 20 Communications Department 21 Memory section 22 Control section 30 Ticket Information 31 Display mode information 32 Blacklist Information 33 First Blacklist Information 34 Secondary Blacklist Information 40 Sales Department 41 Transportation Specific Division 42 Judgment section 43 Payment Department 44 Providing Department 45 Fare Type Specific Department 46 Derivation part

Claims

1. A memory unit that stores ticket information indicating tickets that can be used as fares for transportation; A transportation facility identification unit that identifies the transportation facility in which the user will board; a determination unit that determines whether the ticket information includes a ticket for a period during which the transportation facility identified by the transportation facility identification unit is valid; a payment unit for allowing a user to pay for a fare for the transportation facility while the user is riding the transportation facility; a provision unit that provides the user with an image to be used for disembarking from the means of transportation when the determination unit determines that there is a ticket for the period during which the user can board the vehicle, and provides the user with the image to be used for disembarking from the means of transportation when the determination unit determines that there is no ticket for the period during which the user can board the vehicle and when the payment unit has completed payment of the fare; An information processing device having the above configuration.

2. The providing unit provides an image in which at least a part of a display mode is changed according to at least one of a date, a time period, the transportation facility, and a route of the transportation facility, as the image used for getting off the train. The information processing device according to claim 1 .

3. The providing unit provides, as the image used for getting off, an image in which at least a part of a display state changes in response to an operation.

3. The information processing device according to claim 1 or 2.

4. When there is no ticket within the period during which travel is permitted, the determination unit further determines whether the ticket information includes an unused ticket that can be used as a fare for the transportation facility identified by the transportation facility identification unit; When a usable unused ticket is found as a result of the determination by the determination unit, the settlement unit updates the unused ticket in the ticket information to a used ticket and settles the fare for the transportation facility.

4. The information processing device according to claim 1.

5. The transportation facility identification unit identifies the transportation facility that the user will board from information indicating the transportation facility obtained from inside the transportation facility.

5. An information processing device according to claim 1.

6. The transportation facility identification unit includes a code indicating the transportation facility, and identifies the transportation facility in which the user boards from the code obtained by photographing a code image provided inside the transportation facility.

6. An information processing device according to claim 1.

7. a fare type identification unit that identifies whether the fare of the transportation means to be used is a fixed fare type or a variable fare type that varies depending on the travel distance; and a derivation unit that derives a fare from a boarding section of the transportation facility when the fare type determination unit determines that the fare is the variable fare type, When the fare type identification unit identifies the fare as the fixed fare type, the settlement unit notifies the fixed fare of the transportation facility to a business that executes settlement with the user, and when the fare type identification unit identifies the fare as the variable fare type, the settlement unit notifies the business of the fare derived by the derivation unit.

7. An information processing device according to claim 1.

8. The device further includes a storage unit for storing first blacklist information in which users who are to be denied boarding of fixed-fare and variable-fare transportation means are registered, and second blacklist information in which users who are to be denied boarding of variable-fare transportation means are registered, The provision unit, when a user who has boarded the transportation facility is a user registered in the first blacklist information, presents to the user that boarding will be denied, and when a user who has boarded the transportation facility is a user registered in the second blacklist information, presents to the user that boarding of the transportation facility with a variable fare will be denied.

8. An information processing device according to claim 1.

9. Identifying the transportation facility in which the user will board; determining whether or not there is a ticket within a period during which the specified transportation facility can be used among ticket information stored in a storage unit, the ticket information indicating a ticket that can be used as a fare for the transportation facility; If the result of the determination is that the user has a ticket within the period during which the user can board the vehicle, an image to be used for disembarking from the vehicle is provided to the user. If the result of the determination is that there is no ticket within the period during which the user can board the transportation facility, the user pays the fare for the transportation facility while boarding the transportation facility, and when the fare payment is completed, an image to be used for disembarking the user is provided. A fare adjustment program that causes a computer to execute a process.

10. Identifying the transportation facility in which the user will board; determining whether or not there is a ticket within a period during which the specified transportation facility can be used among ticket information stored in a storage unit, the ticket information indicating a ticket that can be used as a fare for the transportation facility; If the result of the determination is that the user has a ticket within the period during which the user can board the vehicle, an image to be used for disembarking from the vehicle is provided to the user. If the result of the determination is that there is no ticket within the period during which the user can board the transportation facility, the user pays the fare for the transportation facility while boarding the transportation facility, and when the fare payment is completed, an image to be used for disembarking the user is provided. A fare settlement method characterized in that the processing is executed by a computer.

Images