Information processing system, information processing method and program

Abstract

To enable users to smoothly use public transportation.SOLUTION: An information processing system comprises: a detection unit that detects a user device of a user to use public transportation; a status acquisition unit that acquires from a server device a status regarding a fare payment of the user, which indicates the relation between a balance required for the user to pay the public transportation fare associated with the user device and a threshold; and a response determination unit that, when the user device of the user using the public transportation is detected, determines a response to the user regarding the use of the public transportation based on the status.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing method, and a program. [Background technology]

[0002] BACKGROUND ART Conventionally, a ticket system based on the ABT (Account Based Ticketing) method has been known for use of transportation such as trains and buses.

[0003] For example, Patent Document 1 describes a ticket gate system that, assuming the ABT system, issues a warning to a user when transferring from a first ride to a second ride outside the ticket gate and accidentally uses a different transportation medium for the second ride. In the ticket gate system described in Patent Document 1, each ticket gate accesses a center server, and the ticket gate warns the user based on the user's transportation medium ID stored in the center server. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2023-112792 Summary of the Invention [Problem to be solved by the invention]

[0005] The ticket gate system described in Patent Document 1 is based on the ABT system, and therefore a center server manages information related to the user's boarding medium. Therefore, in this ticket gate system, for example, when a ticket gate determines whether a user can board or disembark, the ticket gate may request the balance from the center server and make a determination based on the balance.

[0006] However, when a ticket gate determines whether or not a passenger can board or disembark based on the remaining balance, the amount of information processed by the ticket gate increases, which can cause delays in users' use of public transport.

[0007] Therefore, an object of the present invention is to enable users to use public transportation smoothly. [Means for solving the problem]

[0008] An information processing system according to one aspect of the present invention includes a detection unit that detects a user device of a user for using public transportation; a status acquisition unit that acquires from a server device a status regarding the user's fare payment, which indicates the relationship between a balance for the user associated with the user device to pay the fare for the public transportation and a threshold; and a response determination unit that, when the user device of the user using the public transportation is detected, determines a response to the user regarding their use of the public transportation based on the status. [Effects of the Invention]

[0009] According to the present invention, smooth use of transportation facilities by users is realized. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an overview of processing in a transportation system 10 according to an embodiment of the present invention. [Figure 2] 10 is a database showing an example of device information D111. [Figure 3] 10 is a database showing an example of edge device information D211. [Figure 4] 1 is a flowchart of the processing of the transportation system 10. [Figure 5] FIG. 2 illustrates an example of a hardware configuration. DETAILED DESCRIPTION OF THE INVENTION

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described with reference to the accompanying drawings, in which: Figure 1 is a diagram showing an overview of processing in a transportation system 10 according to an embodiment of the present invention;

[0012] <<Configuration Overview>> An overview of the configuration of a transportation system 10 will be described with reference to Fig. 1. Fig. 1 is a diagram showing an overview of transportation system 10.

[0013] The transportation system 10 is a system that manages the use of transportation facilities by users based on a status corresponding to the balance of the user device 300 of the user who uses the transportation facilities. For example, the transportation system 10 determines whether or not a user can use transportation facilities based on a status determined based on the balance, rather than determining whether or not a user can use transportation facilities based on the user's balance itself.

[0014] The transportation means includes, for example, trains, public buses, taxis, ships, and the like, which transport users.

[0015] The status is information related to the user's fare payment, indicating the relationship between the balance required for the user associated with the user device 300 to pay the transportation fare and a threshold. Specifically, the status may be, for example, a class indicating a balance equal to or greater than the maximum fare for the transportation facility (or a specified section of the transportation facility) (hereinafter referred to as "sufficient balance"), a class indicating a balance less than the maximum fare but equal to or greater than the minimum fare, where, for example, an insufficient balance may occur due to fluctuations in the minimum fare or depending on the destination station (hereinafter referred to as "risk of insufficient balance"), or a class indicating a balance less than the minimum fare (hereinafter referred to as "insufficient balance"). The status is an identification flag that can identify each class.

[0016] In this way, by managing the balance of the user device 300 by status, the transportation system 10 can reduce the amount of information processing in the transportation edge devices (for example, automatic ticket gates for trains and on-board devices for collecting bus fares), which allows the transportation system 10 to reduce its construction costs.

[0017] As shown in FIG. 1, a transportation system 10 includes, for example, a device management apparatus 100, a transportation fare collection apparatus 200, a user device 300, and a transportation apparatus 400.

[0018] The device management apparatus 100 is an apparatus that manages various types of information related to users and user devices 300. The device management apparatus 100 may collectively manage information related to users and user devices 300 related to multiple different modes of transportation. The device management apparatus 100 may be, for example, a cloud computer, a server computer, a personal computer (e.g., a desktop, a laptop, a tablet, etc.), a media computer platform (e.g., a cable or satellite set-top box, a digital video recorder), a handheld computer device (e.g., a PDA, an email client, etc.), or any other type of computer or communication platform.

[0019] The transportation fare collection device 200 is a device that controls the boarding and alighting of users using transportation facilities. The transportation fare collection device 200 is, for example, a device that controls ticket gates at train stations, a device that controls boarding and alighting of users on buses, and a device that calculates fares.

[0020] The user device 300 is a device capable of short-range wireless communication with the traffic toll collection device 200, or a device capable of communicating with the traffic toll collection device 200 via a communication network N10. As shown in FIG. 1, the user device 300 includes a detected unit 310 that displays a read code (e.g., a two-dimensional code) or transmits a device ID via NFC, UWB, or BLE communication. The user device 300 may also include an acquisition unit 320 that acquires various information from other devices. The user device 300 may be, for example, a computer, a smartphone, a tablet device, a wearable device (e.g., a glasses-type device, a watch-type device), or a personal computer. The user device 300 may also be a key fob or a tag that can be detachably attached to a mobile device. For example, the user device 300 stores identification information that can identify the device, such as a device-specific identification number.

[0021] The transportation device 400 is a device that manages ticket gates at train stations, fare collection machines on buses, etc. As shown in Fig. 1, the transportation device 400 has a deposit acceptance unit 410 for charging cash to the balance of the user device 300 via the user device 300. In the following, as an example, the transportation device 400 will be described as a fare collection machine.

[0022] The device management device 100, the transportation fare collection device 200, the user device 300, and the transportation device 400 are communicatively connected to each other via, for example, a communication network N10. The communication network N10 may be a mobile phone network, a wireless local area network (LAN), a long term evolution (LTE), a wired LAN, Wi-Fi, Bluetooth (registered trademark), near field communication (NFC), Bluetooth low energy (BLE) (registered trademark), ultra-wide band (UWB) communication, or a connection via the cloud by displaying and reading a two-dimensional code.

[0023] <<Processing Overview>> Referring to FIG. 1, an overview of the processing of transportation system 10 will be described.

[0024] In step S10, the device management apparatus 100 identifies a status according to the balance of the user device 300. The device management apparatus 100 stores the status in the storage unit 110 in association with a device ID that can uniquely identify the user device 300.

[0025] In step S11, the device management apparatus 100 transmits to the transportation fare collection apparatus 200 information indicating whether the user device 300 is valid (hereinafter referred to as “validity information”).

[0026] The validity information is, for example, an identification flag indicating whether the user device 300 is "valid" or "invalid." "Invalid" may include, for example, the user device 300 being "lost," "stolen," or "suspended."

[0027] In step S12, the user device 300 is detected by the transportation fare collection device 200 when the user uses transportation.

[0028] In step S13, if the transportation fare collection device 200 detects the user device 300, it identifies the device ID associated with the user device 300. The transportation fare collection device 200 identifies validity information associated with the device ID. The transportation fare collection device 200 determines whether the user device 300 is valid or invalid based on the validity information.

[0029] If the user device 300 is valid, the transportation fare collection device 200 allows the user to use transportation, for example (for example, by allowing the user to pass through a fare collection machine on a bus). At this time, the transportation fare collection device 200 may transmit, for example, a device ID and information indicating that the user has boarded the bus (hereinafter referred to as "boarding information") to the device management device 100. The boarding information may include information indicating the boarding point.

[0030] On the other hand, if the user device 300 is invalid, the transportation fare collection device 200 will make the transportation unavailable to the user and, for example, will notify the user device 300 that it is unavailable (for example, by displaying an error message on the bus fare collection machine).

[0031] In step S14, the traffic fare collection device 200 transmits a status request (hereinafter referred to as a "status request") to the device management device 100 through API (Application Programming Interface) linkage.

[0032] In step S15, the device management apparatus 100 transmits the status of the user device 300 of the user currently using the transportation facility to the transportation fare collection apparatus 200 based on the status request received from the transportation fare collection apparatus 200.

[0033] In step S16, when the user finishes using the transportation facility, the transportation fare collection device 200 determines, based on the status of the user device 300, whether the fare can be paid using the balance of the user device 300.

[0034] When the transportation fare collection device 200 determines that the fare can be paid based on the remaining balance, it performs processing to allow the user to disembark from the transportation facility. At this time, the transportation fare collection device 200 may transmit, for example, a device ID and information indicating that the user has disembarked (hereinafter referred to as "disembarkation information") to the device management device 100. The disembarkation information may include information indicating the disembarkation point.

[0035] On the other hand, if the transportation fare collection device 200 determines that the fare cannot be paid based on the remaining balance, it notifies, for example, the user device 300 or the transportation device 400, that the balance is insufficient.

[0036] As described above, in the transportation system 10, the transportation fare collection device 200 pre-stores the validity information of the user device 300. As a result, the transportation fare collection device 200 determines whether the transportation facility is available for use by the user device 300 based on the validity information of the user device 300, and therefore does not need to communicate constantly with the device management device 100 when the user is riding.

[0037] For example, if a transportation fare collection device 200 for a bus operating in a mountainous area with poor communication environments requires constant communication, the problem of users being unable to board the bus may arise depending on the communication environment at the bus's stops. Transportation system 10 does not require constant communication when a user is on board, so this problem can be solved.

[0038] Furthermore, in the transportation system 10, the transportation fare collection device 200 acquires the status at any timing from the device management device 100. In this way, the transportation fare collection device 200 does not need to communicate with the device management device 100 all the time, but can acquire the status of the user device 300 at any timing when the communication environment is good from the time the user starts using the transportation facility until the time the user finishes using the transportation facility.

[0039] For example, the transportation fare collection device 200 may be unable to obtain the status from the device management device 100 due to a poor communication environment when the user begins using the transportation facility. In such a case, the transportation fare collection device 200 can obtain the status of the user device 300 from the device management device 100 at any time when the communication environment is good between the start of the transportation facility use and arrival at the destination. This makes the transportation system 10 more tolerant to the communication environment and enables users to board and disembark appropriately and quickly.

[0040] Furthermore, in the transportation system 10, the device management device 100 manages the balance of the user device 300 by status, so the transportation fare collection device 200 can appropriately allow users to get on and off transportation without managing the balance of the user device 300. In this way, in the transportation system 10, the transportation fare collection device 200 does not need to calculate the relationship between the balance and the fare, so the amount of information processing by the transportation fare collection device 200 can be reduced. For example, when the transportation system 10 is operated in an area that handles a huge number of users, the equipment scale of the transportation fare collection device 200 can be reduced.

[0041] Furthermore, since the transportation system 10 manages the balance of the user device 300 using the status, it is possible to control the boarding and disembarking of users using only the status, without using the balance of the user device 300 in the transportation fare collection device 200, at least for users who have sufficient balance and users who clearly have insufficient balance.

[0042] For example, the transportation system 10 processes a user device 300 whose status indicates that the balance is equal to or greater than the transportation's maximum fare (sufficient balance) so as to allow the user to disembark. On the other hand, the transportation system 10 processes a user device 300 whose status indicates that the balance is less than the transportation's minimum fare (insufficient balance) so as not to allow the user to disembark. This enables the transportation system 10 to reduce the amount of information processed by the transportation fare collection device 200, thereby enabling users to board and disembark smoothly without experiencing delays due to system processing.

[0043] Furthermore, because the transportation system 10 manages the balance of the user device 300 as a status, the transportation fare collection device 200 can prompt a user whose balance may be insufficient to cover the fare to load cash (or settle the payment with a credit card) before getting off the vehicle, without performing calculations based on the balance. For example, the transportation system 10 notifies a user of a user device 300 whose status indicates that the balance is less than the transportation's maximum fare but equal to or greater than the transportation system's minimum fare (risk of insufficient balance) to load cash. This allows the transportation system 10 to allow users to get off the vehicle without delay while reducing the amount of information processed by the system.

[0044] <<Device Management Apparatus 100>> As shown in FIG. 1, the device management device 100 includes a memory unit 110, an acquisition unit 120, a validity determination unit 130, a balance determination unit 140, a status determination unit 150, a validity transmission unit 160, a status transmission unit 170, and a settlement management unit 180.

[0045] The storage unit 110 stores various types of information. The storage unit 110 has, for example, device information D111. The device information D111 will be described with reference to Fig. 2. Fig. 2 is a database showing an example of the device information D111. The device information D111 is a database that is referenced when identifying, for example, a status.

[0046] As shown in FIG. 2, the device information D111 includes items such as [Device ID], [Validity], [Balance], [Boarding Point], [Status], [Threshold], [Commuter Pass], [Usage History], and [User Information]. [Device ID] stores identification information that can uniquely identify the user device 300. [Validity] stores validity information, which is an identification flag indicating validity or invalidity (e.g., valid is "1" and invalid is "0"). [Balance] stores the balance of the user device 300. [Boarding Point] stores information that can identify the location where the user device 300 is detected (e.g., station name, station number, etc.). [Status] stores the status identified by the status identification unit 150. [Threshold] stores a threshold to be compared with the balance. [Commuter Pass] stores whether the pass is registered as a commuter pass and the validity zone of the commuter pass. [Usage History] stores past boarding points, disembarking points, and payment status of the user device 300. [User Information] stores personal information such as the user's name.

[0047] The acquisition unit 120 acquires various types of information. For example, the acquisition unit 120 acquires a device ID, boarding information, disembarking information, a status request, and the like from the transportation fare collection device 200. The acquisition unit 120 acquires, from the transportation facility device 400, deposit information indicating the result of the deposit process, and the like.

[0048] The validity determination unit 130 determines whether the user device 300 is valid. Specifically, the validity determination unit 130 determines the validity of the user device 300 based on, for example, payment information obtained from a predetermined payment service provider indicating that the user is unable to make payments, suspension information indicating that the use of the user device 300 has been suspended due to loss, theft, withdrawal, etc., and deposit failure information indicating that the deposit process could not be completed when the user performed a deposit process on the transportation device 400. The validity determination unit 130 stores the validity information in the storage unit 110.

[0049] The balance specifying unit 140 specifies the balance of the user device 300 by referring to the device information D111. The balance specifying unit 140 may also specify the balance when a deposit process or fare payment process for the user device 300 is accepted. Specifically, when a user deposits money into a transportation device 400 that is capable of executing a deposit process for the user device 300, the transportation device 400 transmits deposit information to the device management device 100. The balance specifying unit 140 specifies the balance in the updated device information D111 based on the deposit information.

[0050] The status identification unit 150 identifies the status of the user device 300. The status identification unit 150 identifies the status based on the balance in the device information D111. The status identification unit 150 stores the identified status in the device information D111 in association with the device ID.

[0051] Specifically, the status identification unit 150 identifies the status based on the result of comparing the balance with a threshold indicating the amount. For example, if the threshold is 200 yen, the status identification unit 150 may identify the status as "insufficient balance" if the balance in the device information D111 is 100 yen (balance less than the threshold), and may identify the status as "sufficient balance" if the balance is 300 yen (balance equal to or greater than the threshold).

[0052] Specifically, the status identification unit 150 may identify the status based on the result of comparing the balance with multiple thresholds. The status identification unit 150 may compare the balance with a first threshold and a second threshold greater than the first threshold. For example, if the first threshold is 200 yen and the second threshold is 1000 yen, the status identification unit 150 may identify the status as "insufficient balance" when the balance in the device information D111 is 100 yen (a balance less than the first threshold), identify the status as "risk of insufficient balance" when the balance is 500 yen (a balance equal to or greater than the first threshold and less than the second threshold), and identify the status as "sufficient balance" when the balance is 2000 yen (a balance equal to or greater than the second threshold). For example, the status determination unit 150 sets the status to "sufficient balance" if the balance is equal to or greater than the maximum fare for the transportation facility (or a specified section of the transportation facility), sets the status to "insufficient balance" if the balance is less than the minimum fare, and sets the status to "risk of insufficient balance" if an insufficient balance may occur due to fluctuations in the minimum fare or depending on the disembarking station.

[0053] Specifically, the status identification unit 150 may set the status based on different thresholds for each of the plurality of transportation modes. For example, the status identification unit 150 may set a first threshold for a first transportation mode and a second threshold for a second transportation mode to different thresholds. In other words, the status identification unit 150 can set the status taking into consideration the minimum, maximum, and variable fares that differ for each of the plurality of transportation modes. The status identification unit 150 may also use a common threshold for the plurality of transportation modes.

[0054] Specifically, the status identification unit 150 may identify the status based on information related to a commuter pass (hereinafter referred to as "commuter pass information"). For example, the status identification unit 150 refers to the device information D111 and identifies the range of travel possible for the minimum fare, taking into account the validity zone of the commuter pass. The status identification unit 150 identifies the status based on the identified range, the minimum fare, and the remaining balance.

[0055] The status identification unit 150 may execute a process of identifying the status at a predetermined timing, for example. Specifically, the status identification unit 150 may execute a process of identifying the status at a timing when the balance is updated, for example. For example, the status of the user device 300 is updated when a user performs charging (for example, charging by account linkage or credit card settlement) between boarding and disembarking. This enables the user to board and disembark appropriately and promptly. Furthermore, specifically, the status identification unit 150 may identify the status at a timing when boarding information or disembarking information is obtained from the transportation fare collection device 200 through API linkage, for example. This reduces the number of processes for identifying the status, thereby reducing the amount of information processing by the device management device 100.

[0056] The validity sending unit 160 sends the validity information to the transportation toll collection device 200. In response to a validity sending request including a device ID acquired from the transportation toll collection device 200 through API linkage, the validity sending unit 160 refers to the device information D111 and sends validity information related to the device ID of the user device 300 to the transportation toll collection device 200.

[0057] The status transmission unit 170 transmits the status to the transportation toll collection device 200. In response to a status transmission request including a device ID acquired from the transportation toll collection device 200 through API linkage, the status transmission unit 170 refers to the device information D111 and transmits the status related to the device ID of the user device 300 to the transportation toll collection device 200.

[0058] The settlement management unit 180 calculates the fare based on the result of the user's use of transportation. The settlement management unit 180 subtracts the fare from the balance and updates the balance. Specifically, the settlement management unit 180 calculates the fare based on the boarding information and disembarking information. In addition, the settlement management unit 180 replaces the balance in the device information D111 with the balance obtained by subtracting the calculated fare from the balance in the device information D111.

[0059] The settlement management unit 180 may also have a function of transmitting the balance to the transportation fare collection device 200. In this case, the settlement management unit 180 may refer to the device information D111 and transmit the balance associated with the device ID of the user device 300 to the transportation fare collection device 200 in response to a balance transmission request including a device ID acquired from the transportation fare collection device 200 through API linkage. Note that the settlement management unit 180 may transmit the balance to the transportation fare collection device 200 when acquiring boarding information from the transportation fare collection device 200.

[0060] <<Transportation Toll Collection Device 200>> As shown in FIG. 1, the traffic fare collection device 200 includes a memory unit 210, a detection unit 220, a validity acquisition unit 230, a validity determination unit 240, a validity notification unit 250, a status request unit 260, a status acquisition unit 270, and a response determination unit 280.

[0061] The storage unit 210 stores various types of information. The storage unit 210 has, for example, edge device information D211. The edge device information D211 will be described with reference to FIG. 3. FIG. 3 is a database showing an example of the edge device information D211. The edge device information D211 is a database that is referenced when determining validity, for example.

[0062] 3, the edge device information D211 includes items such as [Device ID], [Validity], [Balance], and [Status]. [Device ID] stores identification information that can uniquely identify the user device 300. [Validity] stores validity information, which is an identification flag indicating valid or invalid. [Balance] stores the balance of the user device 300. [Status] stores the status of the user device 300. [Status] stores the status of the user device 300.

[0063] Here, in the edge device information D211, it is desirable that all validity information stored in the device management device 100 is stored in [Validity], and only the status of the user device 300 of the user who boarded is stored in [Status]. In this case, the transportation fare collection device 200 performs a primary check of boarding permission using the validity information, and only for user devices 300 that pass the primary check, performs a secondary check of disembarking permission using the status of the user device 300 of the user, which is obtained at any time after the user boards. This makes it possible to reduce the storage capacity of the transportation fare collection device 200, thereby enabling a lower system cost. Note that [Status] may store all statuses stored in the storage unit 110 of the device management device 100.

[0064] The detection unit 220 detects the user device 300 of a user who uses public transportation. Specifically, the detection unit 220, for example, reads a read code (e.g., a two-dimensional code) displayed on the user device 300, or detects a device ID through NFC, UWB, or BLE communication.

[0065] The validity acquisition unit 230 acquires validity information from the device management apparatus 100 through API collaboration. For example, the validity acquisition unit 230 may acquire the validity information from the device management apparatus 100 through API collaboration in advance before the transportation facility starts its daily operations. Alternatively, the validity acquisition unit 230 may acquire the validity information from the device management apparatus 100 through API collaboration at any timing while the transportation facility is in operation.

[0066] When the validity determination unit 240 detects the user device 300, it determines whether the user device 300 is valid based on the validity information in the device information D211. For example, the validity determination unit 240 uses the device ID of the user device 300 as a key to identify the validity information related to the device ID in the device information D211. For example, the validity determination unit 240 determines the user device 300 as "valid" when the identification flag in the validity information is "1", and determines the user device 300 as "invalid" when the identification flag is "0".

[0067] If the validity notification unit 250 determines that the user device 300 is invalid, it sends a notification indicating that the transportation facility is unavailable (hereinafter referred to as an "unavailable notification") to the user device 300 or the transportation facility device 400. This allows the transportation fare collection device 200 to appropriately notify the user that the user device 300 is invalid before the user boards the vehicle, thereby reducing the amount of processing required for the status-based determination process in the response determination unit 280, which will be described later.

[0068] The status request unit 260 requests a status from the device management apparatus 100 through API cooperation. For example, when the detection unit 220 detects the user device 300, the status request unit 260 may request the status of the user device 300 from the device management apparatus 100. Alternatively, after the detection unit 220 detects the user device 300, the status request unit 260 may request the status from the device management apparatus 100 at any timing when the communication environment is good. This allows the transportation fare collection device 200 to reliably obtain the status before the user gets off the vehicle, without being affected by the communication environment.

[0069] In response to a request from the status request unit 260 to the device management apparatus 100, the status acquisition unit 270 acquires a status from the device management apparatus 100 through API linkage.

[0070] When the detection unit 220 detects the user device 300, the response determination unit 280 determines the response to the user regarding the use of public transportation based on the status. After the detection unit 220 detects the user device 300, the response determination unit 280 may determine the response to the user based on the status if the validity determination unit 240 determines that the user device 300 is valid. In this way, the transportation fare collection device 200 performs the determination process of the user device 300 based on the status only when the user device 300 is valid, thereby reducing the amount of information processing.

[0071] "Handling the user" may be, for example, when the status is "sufficient balance," executing a process to have the user get off the vehicle. Also, "handling the user" may be, for example, when the status is "insufficient balance" (for example, when the balance is less than the fare the user can pay (such as the minimum fare)), executing an increase request notification urging the user to charge cash or a refusal notification indicating that the user will be refused entry until the user charges cash. Also, "handling the user" may be, for example, when the status is "risk of insufficient balance," executing a notification indicating that the balance may be insufficient.

[0072] <<First Modification>> A transportation system 10 according to a first modification will be described. In the first modification, the transportation fare collection device 200 may have a balance acquisition unit that acquires balance information indicating a balance. Specifically, when the detection unit 220 detects a user device 300, the transportation fare collection device 200 may request the balance information of the user device 300 from the device management device 100 through API linkage. Furthermore, after the detection unit 220 detects the user device 300, the transportation fare collection device 200 may request the balance information from the device management device 100 at any time when the communication environment is good.

[0073] Specifically, the transportation toll collection device 200 may acquire balance information only for user devices 300 whose status is, for example, "risk of insufficient balance" or "insufficient balance." In this case, the device management device 100 identifies the status associated with the device ID based on the device ID acquired from the transportation toll collection device 200 through API linkage. If the device management device 100 determines that the status is "risk of insufficient balance" or "insufficient balance," it transmits balance information to the transportation toll collection device 200. This enables the transportation toll collection device 200 to notify users who may have difficulty getting off the vehicle of information related to the balance, thereby enabling users to get on and off the vehicle appropriately and quickly.

[0074] The transportation fare collection device 200 may also have a balance notification unit that notifies the user device 300 of balance information indicating the balance. Specifically, the transportation fare collection device 200 may display the balance information on a display unit of the user device 300. In this case, the transportation fare collection device 200 may notify the user device 300 of the amount by which the balance is insufficient for the fare, along with amount data indicating the balance. This allows the transportation fare collection device 200 to notify the user of information regarding the balance, thereby enabling the user to board and disembark appropriately and promptly.

[0075] <<Second Modification>> A second modified example of the transportation system 10 will be described. In the second modified example, the transportation system 10 may have a function of sending a notification to the user device 300 to increase the user's balance (hereinafter referred to as an "increase notification") based on the status.

[0076] Specifically, when the status acquisition unit 270 acquires a status indicating that the balance is less than a predetermined amount, the response determination unit 280 of the transportation fare collection device 200 determines to notify the user device 300 of an increase notification based on the status. The predetermined amount may be, for example, the minimum fare (status "insufficient balance") or the maximum fare (status "insufficient balance" or "risk of insufficient balance").

[0077] In this case, the notification request unit (not shown) of the transportation fare collection device 200 sends an increase notification request to the device management device 100 via API linkage to have the increase notification sent to the user device 300. The device management device 100 then sends the increase notification to the user device 300 based on the increase notification request. This enables the transportation system 10 to ensure that users can board and disembark appropriately and quickly.

[0078] Furthermore, in the transportation system 10 according to the second modification, it is not necessary to determine whether the user device 300 is valid based on the validity information, for example, and the transportation fare collection device 200 may determine whether or not to board or disembark based only on the status. This allows the storage capacity of the transportation fare collection device 200 to be reduced.

[0079] Then, when the status request unit 260 of the transportation fare collection device 200 has sent the increase notification request, it sends a status request to the device management device 100, requesting that the device management device 100 send a status at a predetermined timing. The predetermined timing may be, for example, a predetermined time after the increase notification request is sent, or a fixed time interval. The device management device 100 sends the status to the transportation fare collection device 200 based on the status request. This enables the transportation system 10 to ensure that users can board and disembark appropriately and quickly.

[0080] ===Processing=== The processing flow of the transportation system 10 will be described with reference to Fig. 4. Fig. 4 is a flowchart of the processing of the transportation system 10.

[0081] In step S100, the user performs an operation to charge cash to the user device 300 using a fare collection terminal (for example, a train charge terminal or a bus fare payment device) of the transportation device 400 (charging process). Note that the user may also perform an operation to charge cash to the user device 300 by credit card payment or account linkage without going through the transportation device 400.

[0082] In step S101, the transportation device 400 transmits value information equivalent to the loaded cash together with the device ID to the device management device 100 via API linkage.

[0083] In step S102, the device management apparatus 100 identifies the balance of the user device based on the device ID, and updates the balance in the device information D111 based on the value information. Note that the device management apparatus 100 may transmit the balance information to the user device 300 when updating the balance.

[0084] In step S103, the device management apparatus 100 identifies the status corresponding to the updated balance, and stores the status in the storage unit 110 in association with the device ID.

[0085] In step S200, the transportation fare collection device 200 detects the user device 300 and identifies the device ID of the user device 300 when the user uses transportation.

[0086] In step S201, the traffic fare collection device 200 identifies validity information associated with the device ID by referring to the edge device information D211. The traffic fare collection device 200 determines whether the user device 300 is valid based on the validity information.

[0087] If it is determined that the user device 300 is valid (step S201: YES), in step S202, the transportation fare collection device 200 performs processing to allow the user to pass through, for example, an entrance gate of the transportation facility (passing processing).

[0088] If it is determined that the user device 300 is invalid (step S201: NO), in step S203, the traffic fare collection device 200 notifies the device management device 100 that the user device 300 is not allowed to pass. The device management device 100 notifies the user device 300 that it is not allowed to pass (passage addition process).

[0089] In step S204, the transportation fare collection device 200 transmits a status request to the device management device 100 via API linkage, for the status associated with the device ID of the user currently using the transportation facility.

[0090] In step S205, the device management device 100 refers to the device information D111 and transmits the status associated with the device ID to the traffic toll collection device 200. The traffic toll collection device 200 stores the acquired status in the storage unit 210.

[0091] In step S206, the transportation fare collection device 200 identifies the response to the user device 300 based on the status. At this time, if the status is, for example, "insufficient balance" or "risk of insufficient balance," the transportation fare collection device 200 may send an increase notification to the user device 300 via the device management device 100 to request that cash be charged to the user device 300 (or settle the bill with a credit card). Also, if the status is, for example, "sufficient balance," the transportation fare collection device 200 may notify the user device 300 of balance information via the device management device 100.

[0092] In step S207, the transportation fare collection device 200 detects the user device 300 and identifies the device ID of the user device 300 when the user finishes using the transportation facility.

[0093] In step S208, the traffic fare collection device 200 refers to the edge device information D211 to identify the status associated with the device ID.

[0094] In step S209, the transportation fare collection device 200 determines whether the user device 300 is allowed to disembark based on the status. For example, if the status is "insufficient balance," the transportation fare collection device 200 determines that disembarkation is not permitted, and if the status is "sufficient balance," the transportation fare collection device 200 determines that disembarkation is permitted.

[0095] If the user device 300 determines that it is possible to disembark (step S209: disembark allowed), in step S210, the transportation fare collection device 200 performs processing to allow the user to pass through, for example, the exit gate of the transportation facility (passing processing).

[0096] If it is determined that the user device 300 is not allowed to disembark (step S209: disembark not permitted), in step S211, the transportation fare collection device 200 notifies, for example, the device management device 100, that the user device 300 is not allowed to disembark. The device management device 100 notifies the user device 300 that disembarkation is not permitted (disembark not permitted processing).

[0097] In this way, the transportation system 10 can provide smooth transportation services because the transportation fare collection device 200 does not need to be in constant communication with the device management device 100. Furthermore, the transportation system 10 determines whether the user can get off the vehicle based on the status in the transportation fare collection device 200, so the transportation fare collection device 200 does not need to calculate the relationship between the fare and the balance, thereby reducing the amount of information processing.

[0098] ===Hardware Configuration=== An example of the hardware configuration of the device management device 100, the transportation fare collection device 200, the user device 300 (for example, a personal computer), and the transportation device 400 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the hardware configuration.

[0099] As shown in FIG. 5, the computer 1000 includes a processor 1001, a memory 1002, a storage device 1003, an input I / F unit 1004, a data I / F unit 1005, a communication I / F unit 1006, and a display unit 1007.

[0100] The processor 1001 is a control unit that controls various processes in the computer 1000 by executing programs stored in the memory 1002 .

[0101] The memory 1002 is a storage medium such as a RAM (Random Access Memory), etc. The memory 1002 temporarily stores the program code of the program executed by the processor 1001 and data required when the program is executed.

[0102] The storage device 1003 is a non-volatile storage medium such as a hard disk drive (HDD), flash memory, etc. The storage device 1003 stores an operating system and various programs for realizing the above-mentioned components.

[0103] The input I / F unit 1004 is a device for receiving input from a user. Specific examples of the input I / F unit 1004 include a keyboard, a mouse, a touch panel, various sensors, and a wearable device. The input I / F unit 1004 may be connected to the computer 1000 via an interface such as a USB (Universal Serial Bus).

[0104] The data I / F unit 1005 is a device for inputting data from outside the computer 1000. A specific example of the data I / F unit 1005 is a drive device for reading data stored in various storage media. The data I / F unit 1005 may be provided outside the computer 1000. In this case, the data I / F unit 1005 is connected to the computer 1000 via an interface such as a USB.

[0105] The communication I / F unit 1006 is a device for performing data communication via the Internet N, either wired or wirelessly, with devices external to the computer 1000. The communication I / F unit 1006 may be provided external to the computer 1000. In this case, the communication I / F unit 1006 is connected to the computer 1000 via an interface such as a USB.

[0106] The display unit 1007 is a device for displaying various types of information. Specific examples of the display unit 1007 include a liquid crystal display, an organic EL (Electro-Luminescence) display, and a display of a wearable device. The display unit 1007 may be provided outside the computer 1000. In this case, the display unit 1007 is connected to the computer 1000 via, for example, a display cable. Furthermore, when a touch panel is used as the input I / F unit 1004, the display unit 1007 can be configured as an integrated unit with the input I / F unit 1004.

[0107] ===Summary=== <1> The transportation system 10 includes a detection unit 220 that detects a user device 300 of a user who intends to use transportation, a status acquisition unit 270 that acquires from a device management device 100 (server device) a status related to the user's fare payment, which indicates the relationship between the balance for the user associated with the user device 300 to pay the transportation fare and a threshold, and a response determination unit 280 that, when a user device 300 of a user who intends to use transportation is detected, determines a response to the user regarding their use of transportation based on the status. This eliminates the need for the transportation system 10 to manage the balance in the transportation fare collection device 200, thereby reducing the storage capacity of the transportation fare collection device 200 and enabling the user to disembark without delay through a simple determination based on the status.

[0108] <2> The transportation system 10 further includes a validity determination unit 240 that, when detecting a user device 300 of a user using transportation, determines whether the user device 300 is valid based on validity information indicating whether the user device 300 is valid. If the user device 300 is determined to be valid, the response determination unit 280 determines a response to the user based on the status. <1> In this transportation system, the transportation fare collection device 200 determines whether the transportation facility is available for use by the user device 300 based on the validity information of the user device 300, and therefore does not need to communicate with the device management device 100 constantly when the user boards the transportation facility, thereby enabling smooth use of the transportation facility by the user.

[0109] <3> The transportation system 10 further includes a validity notification unit 250 that, if it is determined that the user device 300 is not valid, sends an unavailable notification to the user device 300 or the transportation facility indicating that the transportation facility is unavailable. <2> In this way, the transportation system 10 determines whether the transportation facility is available for use by the user device 300 in the transportation fare collection device 200 based on the validity information of the user device 300, so that the user does not need to communicate with the device management device 100 constantly when boarding the transportation facility. This allows the transportation system 10 to realize smooth use of transportation facilities by users.

[0110] <4> When the status acquisition unit 270 in the transportation system 10 detects the user device 300 of a user using transportation, the status acquisition unit 270 acquires the user's status from the device management apparatus 100 (server device), and the response determination unit 280 determines the response to the user based on the status. <1> from <3> In this way, the transportation system 10 does not need to constantly communicate with the device management device 100 in the transportation fare collection device 200, but can obtain the status of the user device 300 at any time when the communication environment is good, which makes it possible to have strong resistance to the communication environment and enable users to board and disembark appropriately and quickly.

[0111] <5> When the user device 300 of the transportation system 10 is detected at the end of the transportation use, the action determination unit 280 determines the action to take for the user based on the status. <4> This allows the transportation system 10 to reduce the amount of processing for identifying the status in the device management apparatus 100, thereby reducing the amount of information processing by the device management apparatus 100.

[0112] <6> When the status acquisition unit 270 acquires a status indicating that the balance is less than a predetermined amount, the response determination unit 280 in the transportation system 10 determines, based on the status, to notify the user of an increase notification including content for increasing the balance. <4> This allows the transportation system 10 to realize appropriate and prompt boarding and disembarking of users.

[0113] <7> The transportation system 10 further includes a notification request unit (not shown) that, when the response determination unit 280 determines that an increase notification should be sent to the user, sends an increase notification request to the device management apparatus 100 (server apparatus) requesting that an increase notification be sent to the user, and a status request unit 260 that, when the increase notification request has been sent, sends a status request to the device management apparatus 100 (server apparatus) requesting that a status be sent at a predetermined timing. <6> This allows the transportation system 10 to realize appropriate and prompt boarding and disembarking of users.

[0114] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention.

[0115] In addition, in the present invention, a "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "unit" or device may be realized by two or more physical means, devices, or software modules, and the functions of two or more "units" or devices may be realized by one physical means, device, or software module. [Explanation of symbols]

[0116] 10 Transportation system, 100 Device management device, 110 Memory unit, 120 Acquisition unit, 130 Validity determination unit, 140 Balance determination unit, 150 Status determination unit, 160 Validity transmission unit, 170 Status transmission unit, 200 Transportation fare collection device, 210 Memory unit, 220 Detection unit, 230 Validity acquisition unit, 240 Validity determination unit, 250 Validity notification unit, 260 Status request unit, 270 Status acquisition unit, 280 Response determination unit, 300 User device, 310 Detected unit, 320 Acquisition unit, 400 Transportation device, 410 Deposit acceptance unit.

Claims

1. a detection unit that detects a user device of a user for using public transportation; a status acquisition unit that acquires, from a server device, a status regarding the user's fare payment, the status indicating a relationship between a balance for the user associated with the user device to pay the fare for the transportation facility and a threshold; a response determination unit that, when detecting the user device of the user using the transportation facility, determines a response to the user regarding the use of the transportation facility based on the status; An information processing system comprising:

2. a validity determination unit that, when detecting the user device of the user using the transportation facility, determines whether the user device is valid based on validity information indicating whether the user device is valid; the response determination unit determines a response to the user based on the status when the user device is determined to be valid. The information processing system according to claim 1 .

3. and a validity notification unit configured to, when it is determined that the user device is not valid, notify the user device or the transportation facility of an unavailable notification indicating that the transportation facility is unavailable. The information processing system according to claim 2 .

4. when the status acquisition unit detects a user device of the user using the transportation facility, the status acquisition unit acquires the status of the user from the server device; the response determination unit determines a response to the user based on the status. The information processing system according to claim 1 .

5. the response determination unit, when detecting a user device of the user at the time of ending use of the transportation facility, determines a response to the user based on the status. The information processing system according to claim 4 .

6. The correspondence determination unit When the status acquisition unit acquires the status indicating that the balance is less than a predetermined amount, determining, based on the status, to notify the user of an increase notification including content for increasing the balance; The information processing system according to claim 4 .

7. a notification request unit that transmits, to the server device, an increase notification request requesting that the server device notify the user of the increase notification when the response determination unit determines that the increase notification should be notified to the user; a status request unit that, when the increase notification request is transmitted, transmits a status request to the server device to request that the server device transmit the status at a predetermined timing; The information processing system according to claim 6 , further comprising:

8. the server device that holds the status, The information processing system according to any one of claims 1 to 7.

9. a status identification unit that identifies a status regarding the user's fare payment, the status indicating a relationship between a balance for the user to pay the fare of the transportation facility associated with the user's user device and a threshold; a status transmission unit that transmits the status to the transportation fare collection device in response to a request received from the transportation fare collection device when a user device of the user using the transportation facility is detected in the transportation fare collection device that manages the user's boarding and disembarking; A server device comprising:

10. The computer Detecting a user device of a user for using transportation; obtaining, from a server device, a status of the user's fare payment indicating a relationship between a balance for the user associated with the user device to pay the transportation fare and a threshold value; When the user device of the user using the transportation facility is detected, determining a response to the user regarding the use of the transportation facility based on the status; An information processing method that performs the above.

11. On the computer, Detecting a user device of a user for using transportation; obtaining, from a server device, a status of the user's fare payment indicating a relationship between a balance for the user associated with the user device to pay the transportation fare and a threshold value; When the user device of the user using the transportation facility is detected, determining a response to the user regarding the use of the transportation facility based on the status; A program that executes the following.

Images