Information processing device

Abstract

To mitigate local users' dissatisfaction with transportation services during peak hours. [Solution] The information processing device includes a communication unit 33 that communicates with terminal devices of multiple users, and a control unit 31 that counts the number of uses of each digital transport ticket for each second period included in the first period, detects digital transport tickets whose number of uses in at least one second period is equal to or greater than a usage threshold as congested area tickets, identifies users from among the multiple users who correspond to the detected congested area tickets as congested area users, and transmits incentive information regarding incentives to be given to congested area users to the terminal devices of the identified congested area users via the communication unit 33.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus.

Background Art

[0002] Patent Document 1 discloses an apparatus that determines whether a resident has taken a specific action based on the action history of the resident using a local wallet service, and grants an incentive when it is determined that the resident has taken the specific action. The specific actions include participating in events that contribute to local revitalization and purchasing locally produced products.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In areas where tourists are concentrated due to factors such as revitalization of inbound tourism, public transportation may become crowded, which may reduce the satisfaction of local users such as local residents or commuters or students along local routes with the services of transportation operators. Therefore, measures that can suppress the reduction in the satisfaction of local users even when the number of tourists increases are required.

[0005] An object of the present disclosure is to suppress dissatisfaction of local users with the services of transportation operators during congestion.

Means for Solving the Problems

[0006] An information processing apparatus according to the present disclosure includes: a communication unit that communicates with terminal apparatuses of a plurality of users; counting, for a plurality of digital transport tickets, the number of uses of each digital transport ticket for each second period included in the first period, Among the multiple digital transportation tickets mentioned above, digital transportation tickets whose usage in at least one of the second periods exceeds the usage threshold are detected as congestion area tickets. Among the multiple users mentioned above, the user corresponding to the detected congestion area ticket is identified as a congestion area user. The communication unit transmits incentive information regarding the incentives to be given to the identified users in the congested area to their terminal devices. Control unit and It is equipped with. [Effects of the Invention]

[0007] According to this disclosure, by providing incentives to users in congested areas based on the degree of congestion or the number of days of congestion, it is possible to mitigate dissatisfaction among local users with the services provided by transportation operators during congested periods. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the configuration of a system according to some embodiments of this disclosure. [Figure 2] This is a block diagram showing the configuration of a server device corresponding to an information processing device according to some embodiments of this disclosure. [Figure 3] This is a flowchart showing the operation of the server device according to the first embodiment. [Figure 4] This table shows an example of data registered in the database. [Figure 5] This table shows an example of data registered in the database. [Figure 6] This figure shows an example of a terminal device screen. [Figure 7] This figure shows another example of a terminal device screen. [Figure 8] This is a flowchart showing an example of the operation of the server device according to the first embodiment. [Figure 9] This table shows an example of data registered in the database. [Figure 10]This is a flowchart showing the operation of the server device according to the second embodiment. [Figure 11] This is a table showing an example of data registered in the database. [Figure 12] This is a flowchart showing a modified example of the operation of the server device according to the second embodiment. [Figure 13] This is a flowchart showing the operation of the server device according to the third embodiment. [Figure 14] This is a flowchart showing a modified example of the operation of the server device according to the third embodiment. [Modes for Carrying Out the Invention]

[0009] Hereinafter, several embodiments of the present disclosure will be described with reference to the drawings.

[0010] In each drawing, the same or corresponding parts are denoted by the same reference numerals. In the description of each embodiment, descriptions of the same or corresponding parts will be omitted or simplified as appropriate.

[0011] A first embodiment which is one embodiment of the present disclosure will be described.

[0012] The configuration of the system 10 according to the present embodiment will be described with reference to Figure 1.

[0013] The system 10 according to the present embodiment includes terminal devices 20 of a plurality of users 11 and a server device 30. Each terminal device 20 is a smartphone in the present embodiment, but may be other types of mobile terminals such as a tablet. The server device 30 may be a cloud server or an on-premises server.

[0014] The server device 30 can communicate with each terminal device 20 via a network 40. The network 40 includes a mobile communication network, the Internet, or both.

[0015] In this embodiment, the server device 30 counts the number of uses for each of the multiple digital transport tickets for each second period included in the first period. The server device 30 detects digital transport tickets among the multiple digital transport tickets whose number of uses in at least one second period is equal to or greater than the usage threshold as congested area tickets. The server device 30 identifies the user 11 corresponding to the detected congested area ticket from among the multiple users 11 as a congested area user. The server device 30 transmits incentive information regarding the incentive to be given to the congested area user to the identified congested area user's terminal device 20 via the network 40.

[0016] According to this embodiment, by providing incentives to users in congested areas, dissatisfaction among users of transportation services during peak hours can be suppressed. For example, if the first period is one month and the second period is one day, and there is a region where a considerable number of tourists traveled using digital transportation tickets on at least one day of the previous month, then incentives such as points or coupons will be given to users in the corresponding region, thereby suppressing dissatisfaction among users of transportation services during peak hours.

[0017] For example, server device 30 manages the sale of digital transport tickets. Server device 30 stores the area set for each digital transport ticket. Server device 30 determines that the area of ​​a digital transport ticket is congested if the number of uses of that digital transport ticket in a second period exceeds a usage threshold. Server device 30 stores the number of times that area was determined to be congested in a first period which is longer than the second period. Server device 30 stores the users 11 who reside in that area during the first period. Server device 30 distributes incentives equal to the number of times it has been stored to the terminal devices 20 of the stored users 11. In this example, users 11 are given incentives when their residential area is congested due to factors such as a concentration of tourists, thus reducing feelings of annoyance.

[0018] Referring to Figure 2, the configuration of the server device 30 according to this embodiment will be described.

[0019] The server device 30 comprises a control unit 31, a storage unit 32, and a communication unit 33.

[0020] The control unit 31 includes at least one processor, at least one programmable circuit, at least one dedicated circuit, or any combination thereof. The processor is a general-purpose processor such as a CPU (central processing unit) or GPU (graphics processing unit), or a dedicated processor specialized for a specific process. The programmable circuit is, for example, an FPGA (field-programmable gate array). The dedicated circuit is, for example, an ASIC (application-specific integrated circuit). The control unit 31 controls each part of the server device 30 and executes processes related to the operation of the server device 30.

[0021] The storage unit 32 includes at least one semiconductor memory, at least one magnetic memory, at least one optical memory, or any combination thereof. The semiconductor memory is, for example, RAM (random access memory), ROM (read-only memory), SSD (solid-state drive), or flash memory. The magnetic memory is, for example, HDD (hard disk drive). The storage unit 32 functions, for example, as main memory, auxiliary memory, or cache memory. A database 34 is constructed in the storage unit 32. The storage unit 32 stores information used for the operation of the server device 30 and information obtained by the operation of the server device 30.

[0022] The communication unit 33 includes at least one communication module. The communication module is, for example, a module compatible with a wired LAN (local area network) standard such as Ethernet®, or a wireless LAN standard such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. The communication unit 33 communicates with each terminal device 20. Instead of the database 34 being built in the storage unit 32, the database 34 may be built in external storage accessible via the communication unit 33. The communication unit 33 receives information used in the operation of the server device 30 and transmits information obtained through the operation of the server device 30.

[0023] The functions of the server device 30 are realized by executing a server program on a processor acting as a control unit 31. In other words, the functions of the server device 30 are realized by software. The server program can be stored on a non-temporary computer-readable medium. Examples of non-temporary computer-readable media include flash memory, magnetic recording devices, optical discs, magneto-optical recording media, or ROM.

[0024] Some or all of the functions of the server device 30 may be implemented by a programmable circuit or dedicated circuit as a control unit 31. In other words, some or all of the functions of the server device 30 may be implemented by hardware.

[0025] The operation of the server device 30 according to this embodiment will be explained with reference to Figure 3.

[0026] Before S101, the database 34 registers the type, target area, and multiplier for each digital transport ticket, as shown in Figure 4. The type represents the classification of the corresponding digital transport ticket by usage form, usage conditions, or other attributes. The target area is the area where the corresponding digital transport ticket can be used. If the corresponding digital transport ticket connects a government-designated city with other regions, only the other regions may be set as the target area. If the corresponding digital transport ticket connects an airport with other regions, only the other regions may be set as the target area. Unlimited ride tickets that span multiple cities do not need to have a target area registered, and in this case, they will be excluded from the tickets subject to congestion judgment. The multiplier is a weighting coefficient applied to the count value of the number of uses for the corresponding digital transport ticket. The multiplier is set lower the more densely populated the target area of ​​the corresponding digital transport ticket is, such as urban areas, and higher the more densely populated the area is, such as tourist destinations. The multiplier may be set lower than "1" if the target area of ​​the corresponding digital transport ticket is a government-designated city, and set to "1" otherwise. The multiplier may be changed depending on the time of year or time of day, such as during periods when specific events are held in the area covered by the corresponding digital transport ticket, or during seasons or times when tourists tend to gather. In the example shown in Figure 4, a one-way ticket for train R1 from station T2 to station T3 is set to type 1, target area area A1, and multiplier "1". In Figure 4, train R1, train R2, and bus B1, etc., are the names of the transport operators, routes, or nicknames or abbreviations of the routes, respectively.

[0027] In S101, the control unit 31 counts the number of uses for each of the multiple digital transport tickets for each second period included in the first period. Specifically, the control unit 31 counts the number of uses for each of the multiple digital transport tickets for each day of the previous month. The first period and the second period are not limited to one month and one day, respectively, but can be any combination of periods selected from years, fiscal years, half-years, quarters, months, weeks, days, hours, and other periods, such that the relationship that the first period includes multiple second periods holds true.

[0028] In S102, the control unit 31 detects as congested area tickets any digital transport tickets among a plurality of digital transport tickets whose usage in at least one second period exceeds a predetermined threshold. Specifically, the control unit 31 detects as congested area tickets any digital transport tickets among a plurality of digital transport tickets whose usage in at least one day exceeds a threshold.

[0029] As a result of step S102, the database 34 registers the usage count for each digital transport ticket for each day of the previous month, as well as a congestion flag, as shown in Figure 5. A multiplier as shown in Figure 4 is applied to the usage count. The congestion flag indicates whether the usage count for the corresponding digital transport ticket on the corresponding date is equal to or greater than the usage threshold. In the example shown in Figure 5, the usage threshold is set to "1000", but this can be changed as appropriate. On January 1, 2025, the usage count for a one-way ticket on train R1 from station T2 to station T3 is "1000", so the congestion flag is set to "1", indicating congestion. On January 2, 2025, the usage count for a one-way ticket on train R1 from station T2 to station T3 is "800", so the congestion flag is set to "0", indicating no congestion. On January 3, 2025, the number of users for a one-way ticket on train R1 from station T2 to station T3 is "755", so the congestion flag is set to "0", indicating no congestion. On January 4, 2025, the number of users for a one-way ticket on train R1 from station T2 to station T3 is "1020", so the congestion flag is set to "1", indicating congestion. In other words, a one-way ticket on train R1 from station T2 to station T3 is considered a congested area ticket on January 1, 2025 and January 4, 2025, but is not considered a congested area ticket on January 2, 2025 and January 3, 2025.

[0030] In S103, the control unit 31 identifies the user 11 corresponding to the congestion area ticket detected in S102 as a congestion area user from among the multiple users 11. Specifically, the control unit 31 searches the database 34 to identify the user 11 whose residential area is the same as the area covered by the congestion area ticket as a congestion area user. The database 34 is assumed to have the residential area of ​​each user 11 pre-registered. If a user 11's residential area in January 2025 is area A1, then in the example shown in Figure 5, that user 11 would be a congestion area user on January 1st and January 4th, 2025, but not on January 2nd and January 3rd, 2025. Residential areas are updated, for example, monthly, but may also be updated daily, or more or less frequently.

[0031] Any procedure may be used to register the residential area of ​​each user 11, but for example, one of the following three procedures can be used.

[0032] As the first step, the control unit 31 receives location information regarding the location of each user 11 from the terminal device 20 of each user 11 via the communication unit 33. The location information includes, for example, positioning results obtained by the GNSS (global navigation satellite system) receiver installed in the terminal device 20. Based on the received location information, the control unit 31 estimates the residential area. The control unit 31 registers the estimated residential area in the database 34. For example, the control unit 31 registers the municipality that appeared most frequently in the location information within a specific period in the past as the municipality of each user 11.

[0033] In the second step, the control unit 31 detects digital transportation tickets from among multiple digital transportation tickets that are used by each user 11 at a certain frequency or higher as residential area tickets. The control unit 31 registers the target area of ​​the detected residential area tickets as a residential area in the database 34. For example, the control unit 31 identifies and registers the residential area of ​​each user 11 based on the number of times the digital transportation ticket has been used in a specific period in the past and the target area of ​​the digital transportation ticket.

[0034] In the third step, the control unit 31 receives address information for each user 11 from an external system via the communication unit 33. The address information includes information on the city or town where each user 11 resides, obtained through linkage with a public personal identification system managed by the government, such as the My Number system in Japan. Based on the received address information, the control unit 31 estimates the residential area. The control unit 31 registers the estimated residential area in the database 34.

[0035] In S104, the control unit 31 transmits incentive information regarding the incentive to be given to the congested area user to the terminal device 20 of the congested area user identified in S103, via the communication unit 33. The control unit 31 may adjust the incentive based on the number of times in the second period, which is included in the first period, that the number of times the number of congested area tickets used exceeds a threshold. Specifically, the control unit 31 may adjust the incentive based on the number of days in the month preceding the month in which the incentive is given that the number of times the number of congested area tickets used exceeds a threshold.

[0036] For example, as shown in Figure 6, the control unit 31 awards points to users in congested areas based on the number of days in the month preceding the month in which the number of congested area tickets used exceeds a threshold. Alternatively, as shown in Figure 7, the control unit 31 may award users in congested areas coupons usable in their residential area if the number of days in the month preceding the month in which the number of congested area tickets used exceeds a threshold is a certain number or more. Coupons usable in the residential area could be discount coupons for digital transport tickets usable in the residential area, or discount coupons applicable to any digital transport ticket without limiting the target area. Incentive information may be presented as a pop-up that appears only once when a congested area user launches the application at the beginning of the month. If the residential area is updated daily, in the example shown in Figure 6 or Figure 7, the notation "Your sightseeing incentive for last month" may be replaced with "Your sightseeing incentive for last month." In this way, if the residential area is updated daily, even if user 11 moves in the middle of the month and their residential area changes, they can still receive the incentive, thus reducing the sense of unfairness.

[0037] Referring to Figure 8, a modified example of the operation of the server device 30 according to this embodiment will be described.

[0038] Steps S201 and S202 are the same as steps S101 and S102 shown in Figure 3, respectively, so their explanation will be omitted.

[0039] In S203, the control unit 31 identifies users 11 from among multiple users 11 whose residential area is the same as the area covered by the congestion area ticket, and who used the same digital transportation ticket as the congestion area ticket during at least one second period in which the number of congestion area ticket users exceeded a threshold, as congestion area users. Specifically, the control unit 31 searches the database 34 to identify users 11 whose residential area is the same as the area covered by the congestion area ticket, and who used the same digital transportation ticket as the congestion area ticket on the same day, as congestion area users.

[0040] Before S203, the database 34 registers a record of which digital transport ticket each user 11 used and on which date, as shown in Figure 9. In the example shown in Figure 9, a record is registered that user 11, corresponding to user ID "12345", used a one-way ticket for train R1 from station T2 to station T3 on January 4, 2025. Therefore, if user 11's residential area in January 2025 is area A1, then in the example shown in Figure 5, user 11 is a user in a congested area on January 4, 2025, but not in a congested area on January 1, 2025, as well as on January 2, 2025, and January 3, 2025.

[0041] Step S204 is the same as step S104 shown in Figure 3, so its explanation will be omitted.

[0042] According to this modified version, users 11 who actually use the relevant public transportation during peak hours are given an incentive, so there is no sense of unfairness.

[0043] A second embodiment, which is another embodiment of the present disclosure, will be described.

[0044] The configuration of system 10 according to this embodiment is the same as that of system 10 according to the first embodiment, which was described with reference to Figure 1, so its description is omitted. The configuration of server device 30 according to this embodiment is also the same as that of server device 30 according to the first embodiment, which was described with reference to Figure 2, so its description is omitted.

[0045] The operation of the server device 30 according to this embodiment will be explained with reference to Figure 10.

[0046] Steps S301 and S302 are the same as steps S101 and S102 shown in Figure 3, respectively, so their explanation will be omitted.

[0047] In S303 and S304, the control unit 31 identifies the user 11 corresponding to the congestion area ticket detected in S302 as a congestion area user from among the multiple users 11. Specifically, in S303, the control unit 31 detects the digital transportation tickets used by each user 11 at a frequency equal to or greater than a predetermined threshold from among the multiple digital transportation tickets as the residential area tickets of each user 11. In S304, the control unit 31 identifies the user 11 whose residential area ticket detected in S303 is the same as the congestion area ticket as a congestion area user from among the multiple users 11.

[0048] Before S303, the database 34 registers a record of how many times each user 11 has used each digital transport ticket in the past, as shown in Figure 11. The number of uses may be the total number of uses in the past, or the number of uses within a specific period in the past, such as the month before the month in which the incentive is awarded. Instead of the number of uses, a usage rate obtained by dividing the number of uses by the period may be used. The record includes a resident flag for each combination of user 11 and digital transport ticket. The resident flag is a flag that indicates whether the number of uses of the corresponding digital transport ticket within a certain period by the corresponding user 11 is above a frequency threshold. In the example shown in Figure 11, the frequency threshold is set to "20", but it can be changed as appropriate. For user 11 corresponding to user ID "12345", the number of uses for the one-way ticket from station T2 to station T3 on train R1 is "30", so the resident flag is set to "1". For user 11, corresponding to user ID "12345", the resident flag is set to "0" because the usage count for other digital transport tickets is "10" or "0". In other words, for user 11, corresponding to user ID "12345", the one-way ticket for train R1 from station T2 to station T3 corresponds to a residential area ticket. Therefore, in the example shown in Figure 5, user 11, corresponding to user ID "12345", is a congested area user on January 1, 2025 and January 4, 2025. If there are multiple tickets for a single user ID with usage counts exceeding the frequency threshold, the resident flag may be assigned to the transport ticket with the highest frequency, or the resident flag may be assigned to all transport tickets with usage counts exceeding the frequency threshold. In the latter case, congestion determination may be performed multiple times for the same second period for a single user ID.

[0049] Step S305 is the same as step S104 shown in Figure 3, so its explanation will be omitted.

[0050] In the first embodiment, users 11 whose residential area is the same as the target area of ​​a congested area ticket are identified as congested area users. In contrast, in this embodiment, for each user 11, the digital transport ticket they use most frequently is detected as a residential area ticket, and users 11 whose residential area ticket is the same as a congested area ticket are identified as congested area users. Therefore, as shown in the example in Figure 4, it is no longer necessary to register the target area of ​​each digital transport ticket in the database 34.

[0051] According to this embodiment, an incentive is given to users 11 who frequently use the same public transportation as crowded public transportation, so there is no sense of unfairness.

[0052] Referring to Figure 12, a modified example of the operation of the server device 30 according to this embodiment will be described.

[0053] Steps S401 to S403 are the same as steps S301 to S303 shown in Figure 10, so their explanation will be omitted.

[0054] In S404, the control unit 31 identifies as a congested area user any user 11 among multiple users 11 whose residential area ticket detected in S403 is the same as a congested area ticket, and who used the same digital transport ticket as the congested area ticket in the same second period as at least one second period in which the number of congested area tickets used exceeded a threshold. Specifically, the control unit 31 searches the database 34 to identify as a congested area user any user 11 whose residential area ticket is the same as a congested area ticket, and who used the same digital transport ticket as the congested area ticket on the same day.

[0055] Before S404, the database 34 registers a record of which digital transport ticket each user 11 used and on which date, as shown in Figure 9. In the example shown in Figure 9, a record is registered that user 11, corresponding to user ID "12345", used a one-way ticket for train R1 from station T2 to station T3 on January 4, 2025. Therefore, as in the example shown in Figure 11, when the one-way ticket for train R1 from station T2 to station T3 corresponds to a residential area ticket for that user 11, in the example shown in Figure 5, that user 11 is a congested area user on January 4, 2025, but not a congested area user on January 1, 2025.

[0056] Step S405 is the same as step S305 shown in Figure 10, so its explanation will be omitted.

[0057] According to this modified version, users 11 who actually use the relevant public transportation during peak hours are given an incentive, so there is no sense of unfairness.

[0058] A third embodiment, which is yet another embodiment of the present disclosure, will be described.

[0059] In the first and second embodiments, people who used digital transportation tickets are reflected in the congestion information, but in this embodiment, people who used the transit guidance service to search for routes are reflected in the congestion information. For example, areas where the number of searches for the transit guidance service has suddenly increased are identified as congested areas on a daily basis. The determination of a sudden increase is made by whether the number of searches in the same area has increased by a certain percentage or more compared to the same day or day of the week in the previous month, or the same day or day of the week in the same month of the previous year.

[0060] The configuration of system 10 according to this embodiment is the same as that of system 10 according to the first embodiment, which was described with reference to Figure 1, so its description is omitted. The configuration of server device 30 according to this embodiment is also the same as that of server device 30 according to the first embodiment, which was described with reference to Figure 2, so its description is omitted.

[0061] The operation of the server device 30 according to this embodiment will be explained with reference to Figure 13.

[0062] In S501, the control unit 31 counts the number of searches for routes using public transportation within each of the multiple areas for each third period included in the first period. Specifically, the control unit 31 counts the number of searches for routes using public transportation within each of the multiple areas on a daily basis. The first period and the third period are not limited to months and days, respectively, but may be any combination of periods selected from years, fiscal years, half-years, quarters, months, weeks, days, hours, and other periods, such that the relationship that the first period includes multiple third periods holds true.

[0063] In S502, the control unit 31 detects as congested areas areas in which the number of searches in at least one third period is at least a certain ratio compared to the number of searches in a specific period prior to that third period, that is, areas where the number of searches in at least one third period has increased sharply. Specifically, the control unit 31 detects as congested areas areas in which the number of searches in at least one day is at least a certain ratio compared to the number of searches on the same day or day of the same month of the previous month, or the same day or day of the same month of the previous year. As a modification, the control unit 31 may detect as congested areas areas in which the number of searches in at least one third period is at least a predetermined threshold. Specifically, the control unit 31 may detect as congested areas areas in which the number of searches in at least one day is at least a threshold.

[0064] In S503, the control unit 31 identifies the user 11 corresponding to the congested area detected in S502 as a congested area user from among the multiple users 11. Specifically, the control unit 31 searches the database 34 to identify the user 11 whose residential area is the same as the congested area as a congested area user. The database 34 is assumed to have the residential area of ​​each user 11 pre-registered, as in the first embodiment.

[0065] In S504, the control unit 31 transmits incentive information regarding the incentive to be given to the congested area user to the terminal device 20 of the congested area user identified in S503 via the communication unit 33. The control unit 31 may adjust the incentive based on the number of third periods included in the first period in which the number of searches for routes traveling within the congested area increased sharply. Specifically, the control unit 31 may adjust the incentive based on the number of days in a month in which the number of searches for routes traveling within the congested area exceeded a certain ratio compared to the number of searches on the same day or day of the same week in the previous month, or the same month, same day or day of the same week in the previous year. Alternatively, the control unit 31 may adjust the incentive based on the number of third periods included in the first period in which the number of searches for routes traveling within the congested area exceeded a threshold. Specifically, the control unit 31 may adjust the incentive based on the number of days in the previous month in which the number of searches for routes traveling within the congested area exceeded a threshold.

[0066] Referring to Figure 14, a modified example of the operation of the server device 30 according to this embodiment will be described.

[0067] Steps S601 and S602 are the same as steps S501 and S502 shown in Figure 13, respectively, so their explanation will be omitted.

[0068] In S603, the control unit 31 identifies users 11 from among multiple users 11 as congested area users if they used a digital transport ticket whose residential area is the same as the congested area and whose target area is the same as the congested area, during at least one third period in which the number of searches for routes traveling within the congested area increased sharply. Specifically, the control unit 31 searches the database 34 to identify users 11 as congested area users if they used a digital transport ticket whose residential area is the same as the congested area and whose target area is the same as the congested area, on the same day in which the number of searches for routes traveling within the congested area increased sharply.

[0069] Step S604 is the same as step S504 shown in Figure 13, so its explanation will be omitted.

[0070] According to this modified version, users 11 who actually used the relevant public transportation when the number of searches increased are given an incentive, so there is no sense of unfairness.

[0071] This embodiment and the first embodiment may be integrated. That is, both steps S101 and S102 shown in Figure 3 and steps S501 and S502 shown in Figure 13 may be performed. Subsequently, the control unit 31 may identify not only the user 11 corresponding to the congestion area ticket detected in S102, but also the user 11 corresponding to the congestion area detected in S502 as a congestion area user. Further modifications, such as those shown in Figures 8 and 14, may be applied.

[0072] This disclosure is not limited to the embodiments described above. For example, two or more blocks described in the block diagram may be combined, or one block may be divided. Instead of executing two or more steps described in the flowchart in chronological order as described, they may be executed in parallel or in a different order, depending on the processing capacity of the device performing each step, or as necessary. Other modifications are possible without departing from the spirit of this disclosure. [Explanation of Symbols]

[0073] 10 Systems 11 users 20 Terminal devices 30 Server Devices 31 Control Unit 32 Storage section 33 Communications Department 34 Databases 40 Networks

Claims

1. A communication unit that communicates with terminal devices of multiple users, For multiple digital transport tickets, count the number of uses for each digital transport ticket within the second period included in the first period. Among the multiple digital transportation tickets mentioned above, digital transportation tickets whose usage in at least one of the second periods exceeds the usage threshold are detected as congestion area tickets. Among the multiple users mentioned above, the user corresponding to the detected congestion area ticket is identified as a congestion area user. The communication unit transmits incentive information regarding the incentives to be given to the identified users in the congested area to their terminal devices. Control unit and An information processing device equipped with the following features.

2. The information processing apparatus according to claim 1, wherein the control unit searches a database in which the residential area of ​​each user is registered and identifies users whose residential area is the same as the area covered by the congestion area ticket as the congestion area user.

3. The control unit, The communication unit receives location information regarding each user's location from each user's terminal device. Based on the received location information, the residential area is estimated, The information processing apparatus according to claim 2, which registers the estimated residential area in the database.

4. The control unit, Among the aforementioned multiple digital transportation tickets, digital transportation tickets that are used by each user at a certain frequency or higher are detected as residential area tickets. The information processing device according to claim 2, which registers the target area of ​​the detected residential area ticket as the residential area in the database.

5. The control unit, Among the aforementioned multiple digital transportation tickets, digital transportation tickets whose usage frequency by each user exceeds a frequency threshold are detected as tickets for each user's residential area. The information processing device according to claim 1, wherein, among the plurality of users, the user whose detected residential area ticket is the same as the crowded area ticket is identified as the crowded area user.

6. The information processing apparatus according to claim 1, wherein the control unit adjusts the incentive based on the number of second periods included in the first period in which the number of uses of the congested area tickets is equal to or greater than the usage threshold.

7. The information processing apparatus according to any one of claims 1 to 5, wherein the control unit identifies a user among the plurality of users who used the same digital transportation ticket as the congestion area ticket during the same second period as at least one second period as the congestion area ticket.

8. The control unit, For multiple areas, the number of searches for routes using public transportation within each area is counted for each third period included in the aforementioned first period. Among the aforementioned multiple areas, areas where the number of searches in at least one third period is at least a certain ratio compared to the number of searches in a specific period prior to that at least one third period, or areas where the number of searches in at least one third period is at or above a search threshold, are detected as congested areas. The information processing device according to claim 1, wherein, among the plurality of users, the user corresponding to the detected congestion area is also identified as a congestion area user.

9. A communication unit that communicates with terminal devices of multiple users, For multiple areas, count the number of searches for routes using public transportation within each area, for each third period included in the first period. Among the aforementioned multiple areas, areas where the number of searches in at least one third period is at least a certain ratio compared to the number of searches in a specific period prior to that at least one third period, or areas where the number of searches in at least one third period is at or above a search threshold, are detected as congested areas. Among the multiple users mentioned above, the user corresponding to the detected congestion area is identified as a congestion area user. The communication unit transmits incentive information regarding the incentives to be given to the identified users in the congested area to their terminal devices. Control unit and An information processing device equipped with the following features.

10. The information processing apparatus according to claim 9, wherein the control unit searches a database in which the residential area of ​​each user is registered and identifies users whose residential area is the same as the congested area as congested area users.

11. The information processing apparatus according to claim 9 or 10, wherein the control unit identifies a user among the plurality of users who used a digital transportation ticket in which the target area is the same as the congested area during the same third period as at least one third period as the congested area user.

Images