Information processing device, information processing method, program, and terminal device

Abstract

To provide a technology capable of mitigating congestion in a migration type event.SOLUTION: An exemplary information processing device of the present invention includes a controller. The controller changes, according to congestion information of a plurality of destinations, a difficulty level of a task to be performed at the plurality of destinations by a user mitigating the destinations, incentive obtained at the destinations, and a route to visit the destinations.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present invention relates to a technique for managing a tour-type event in which participants visit multiple destinations. [Background technology]

[0002] Traditionally, events that involve moving around a community, such as stamp rallies and puzzle-solving games that involve touring the city, have been known as events that revitalize the community.

[0003] Furthermore, conventionally, techniques for realizing congestion relief are known (see, for example, Patent Document 1). Patent Document 1 discloses a configuration for acquiring a travel route used by a user, calculating the degree of difficulty for the user to use the travel route from the user's travel schedule, and granting a reward according to the degree of difficulty. Patent Document 1 also discloses that congestion relief can be realized by granting a reward according to the difficulty of the travel route. Patent Document 1 also discloses that when it is determined from the user's travel schedule (travel plans) that the user will use a travel route during a crowded time period, a suggestion is made to encourage the user to change their travel schedule. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-99880 Summary of the Invention [Problem to be solved by the invention]

[0005] In a migratory event, people may gather at popular spots. Also, in a migratory event, if all participants are set to visit multiple destinations along the same route, people may gather at a certain spot. In other words, the occurrence of congested spots can be a problem in a migratory event.

[0006] In a migratory event, the route of a user moving between multiple destinations may be determined in advance, or the user may move around while guessing the next destination by solving a puzzle. For this reason, it may not be possible or desirable to give an incentive to users to select a more difficult route or to suggest changes to each user's travel plans, as in Patent Document 1. In other words, it is considered that the conventional methods are not necessarily suitable for resolving congestion in a migratory event.

[0007] In view of the above, an object of the present invention is to provide a technique that can alleviate congestion at roaming events. [Means for solving the problem]

[0008] An exemplary information processing device of the present invention is an information processing device equipped with a controller that changes the difficulty of tasks to be performed at multiple destination points by a user traveling between the multiple destination points, the incentives obtained at the destination points, or the route to visit the destination points, in accordance with congestion information at the multiple destination points. Effect of the Invention

[0009] According to the exemplary embodiment of the present invention, congestion at a roaming event can be alleviated. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 shows a schematic configuration of an information processing system. [Diagram 2] A block diagram showing a configuration of an information processing device. [Diagram 3] FIG. 13 is a diagram showing an example of a user information table. [Figure 4] FIG. 13 is a diagram showing an example of a location information table; [Diagram 5] FIG. 13 is a diagram showing an example of a task information table. [Figure 6] FIG. 13 is a diagram showing an example of a coupon information table. [Figure 7A]FIG. 13 is a diagram showing preconditions for explaining an example in which the setting conditions are changed according to congestion information. [Figure 7B] FIG. 11 is a diagram for explaining a first embodiment of changing setting conditions according to congestion information; [Figure 7C] FIG. 1 is a diagram for explaining a modification of the first embodiment; [Figure 8] A flowchart showing an example of a process performed by an information processing device for each user participating in a roaming event. [Figure 9] FIG. 13 is a diagram showing an example of a screen of a terminal device owned by a user participating in a roaming event. [Figure 10] A flowchart showing an example of a process for changing a setting condition in a roaming event, which is executed by an information processing device. [Figure 11] FIG. 13 is a diagram showing an example of a screen of a terminal device when a setting condition is changed; [Figure 12] A flowchart showing an example of a point redemption process executed by an information processing device. [Figure 13] FIG. 13 is a diagram showing an example of a screen related to point redemption displayed on a terminal device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings.

[0012] <1. Information processing system> 1 is a diagram showing a schematic configuration of an information processing system 100 according to an embodiment of the present invention. The information processing system 100 is an event management system that manages a roaming event in which users who register with the system 100 participate.

[0013] A migratory event is an event in which participants visit multiple destinations. In a migratory event, the user is usually made to perform a task at at least one of the multiple destinations. The task may be, for example, collecting stamps or answering a quiz. The task does not necessarily have to be performed at the destination. Specific examples of migratory events are stamp rallies, puzzle solving games, or a combination thereof. Participants in a migratory event may begin participating in the event at a set time or within a set time range (for example, from 9:00 to 12:00), although this is not intended to be a limitation.

[0014] As shown in FIG. 1, the information processing system 100 includes an information processing device 1, a people flow estimation device 2, an external server 3, and a terminal device 4.

[0015] The information processing device 1 mainly manages the operation of the roaming event and manages users who participate in the roaming event. The information processing device 1 is a server configured by a computer device. The information processing device 1 is provided so as to be connectable to a communication network 5 such as the Internet or a telephone line network by wire or wirelessly. Details of the information processing device 1 will be described later.

[0016] The information processing device 1 may be a physical server or a cloud server. The information processing device 1 may be composed of a single server or multiple servers. In some cases, the information processing device 1 may be composed of not only a server but also a server and a terminal. An example of a terminal here is a terminal placed at a destination point of a roaming event. The terminal placed at the destination point is, for example, a terminal provided in a facility such as a store.

[0017] The pedestrian flow estimation device 2 is a device that estimates the flow of people at a migratory event. The pedestrian flow estimation device 2 is a server configured by a computer device. The pedestrian flow estimation device 2 is provided so as to be connectable to a communication network 5 by wire or wirelessly. The pedestrian flow estimation device 2 is capable of communicating with the information processing device 1 via the communication network 5. The pedestrian flow estimation device 2 may be included in the information processing device 1.

[0018] The people flow estimation device 2 acquires data required for estimating people flow using, for example, a camera, a pyroelectric sensor, carrier data, a beacon, or a combination thereof. For example, the people flow estimation device 2 collects image data from cameras installed around each destination point of the migratory event, and position data from terminals owned by each user. Then, the people flow estimation device 2 estimates people flow using input information such as the degree of congestion at each shooting point obtained by image analysis using the collected image data, the location of each user, and the movement state of each user. The estimated people flow information includes the human density (i.e., congestion information) at each destination point in the migratory event.

[0019] For estimating the people flow, known software for simulating people flow or the like may be used. As an example, the people flow estimation device 2 may be configured to estimate people flow information using an estimation model using artificial intelligence (AI). The estimation model is a prediction model that estimates and outputs people flow information at the destination by inputting various information such as number of people information at the destination obtained from the above-mentioned camera or the like, map information around the destination, and travel time information of people participating in the event.

[0020] The estimation model for estimating people flow can be created by learning data from past migratory events, for example. The data input for learning may include information on the number of people who started participating in each time period in past migratory events, information on the number of people at each time period at the destination point, environmental information such as weather, and travel time information between each point of the event participants. In addition, congestion information of each actual destination point in past migratory events is used as correct answer data for learning. Then, by inputting information similar to the input information used for the above-mentioned learning into the generated estimation model, estimated information on people flow (e.g., congestion information) is output from the model. The people flow estimation device 2 stores the learned estimation model in a memory (not shown), and estimates people flow using the estimation model stored in the memory (not shown).

[0021] The external server 3 is capable of communicating with the information processing device 1 and the people flow estimation device 2 via the communication network 5. The external server 3 provides information in response to requests from the information processing device 1 and the people flow estimation device 2. The external server 3 may be singular or plural. At least one of the external servers 3 may be included in the information processing device 1.

[0022] The external server 3 may be, for example, a server that accumulates information (image data) from a camera installed around each destination point of the above-mentioned migratory event. The external server 3 may also be a server that accumulates data from the above-mentioned pyroelectric sensor, carrier data, etc. The external server 3 may also be, for example, a server that provides environmental information such as weather information in response to a request from the information processing device 1 or the people flow estimation device 2.

[0023] The terminal device 4 is a terminal device used by a user who is registered in the information processing system 100. More specifically, the user is a participant in a roaming event. That is, the terminal device 4 is owned by a user who roams between multiple destinations. The terminal device 4 is preferably a mobile terminal owned by a user who participates in the event. The terminal device 4 is, for example, a smartphone, a tablet terminal, or a notebook computer. The terminal device 4 has a screen for displaying information. The terminal device 4 preferably has an audio output device (speaker) for outputting information as sound.

[0024] The terminal device 4 is provided so as to be connectable to the communication network 5 by wire or wirelessly. The terminal device 4 is capable of communicating with the information processing device 1 via the communication network 5. The terminal device 4 appropriately transmits user information, which is information relating to the user, to the information processing device 1 via the communication network 5. The transmitted user information includes, for example, a user ID and the user's current location. The user's current location is, to be precise, the current location of the terminal device 4 used by the user, and is, for example, location information obtained from a GPS (Global Positioning System) receiver included in the terminal device 4. The terminal device 4 is provided so as to be able to receive various information relating to the roaming event from the information processing device 1.

[0025] In this embodiment, an app (application software) required for participating in a roaming event is installed in the terminal device 4 by downloading or the like. In addition, in FIG. 1, the number of terminal devices 4 connected to the communication network 5 is one, but in reality, the number of terminal devices 4 connected to the communication network 5 is multiple.

[0026] <2. Information processing device> Fig. 2 is a block diagram showing the configuration of an information processing device 1 according to an embodiment of the present invention. Note that Fig. 2 shows components necessary for explaining the features of the embodiment, and omits descriptions of general components.

[0027] 2, the information processing device 1 includes a controller 11. The information processing device 1 further includes a memory unit (memory) 12 and a communication unit 13. The information processing device 1 may include an input device such as a keyboard and an output device such as a display.

[0028] The controller 11 includes an arithmetic circuit that performs arithmetic processing. The arithmetic circuit is specifically configured with a processor. The processor may include, for example, a CPU (Central Processing Unit). The controller 11 may include one processor or multiple processors. When the controller 11 includes multiple processors, it is sufficient that the processors are connected to each other so as to be able to communicate with each other.

[0029] The memory unit 12 includes a volatile memory and a non-volatile memory. The volatile memory is specifically a RAM (Random Access Memory). The non-volatile memory is specifically a ROM (Read Only Memory). The non-volatile memory may also be a flash memory, a hard disk drive, or the like. The non-volatile memory stores programs and data that can be read by a computer.

[0030] The communication unit 13 is configured as a communication interface having an interface circuit for connecting to the communication network 5 .

[0031] 2, the controller 11 includes, as its functions, an acquisition unit 111, a user management unit 112, an event management unit 113, a notification unit 114, and a point exchange unit 115. In this embodiment, the functions of the controller 11 are realized by a processor executing arithmetic processing in accordance with a program stored in the memory unit 12.

[0032] The program stored in the memory unit 12 is a computer program that causes a processor (computer) to realize the functions of the information processing device 1. Such a computer program may be provided, for example, by a computer-readable nonvolatile recording medium. The nonvolatile recording medium may be, for example, an optical recording medium (for example, an optical disk), a magneto-optical recording medium (for example, a magneto-optical disk), a USB memory, or an SD card, in addition to the above-mentioned nonvolatile memory. As another example, the computer program may be provided from a program providing server via a communication line such as the Internet, or provided by so-called downloading.

[0033] Further, each of the functional units 111 to 115 may be realized by one program, but may be configured to be realized by separate programs for each functional unit. Further, each of the functional units 111 to 115 may be realized as separate servers. Further, each of the functional units 111 to 115 may be realized by having a processor execute a program, that is, by software, as described above, but may be realized by other methods. Each of the functional units 111 to 115 may be realized by using, for example, an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). That is, each of the functional units 111 to 115 may be realized by hardware using a dedicated IC or the like. Further, each of the functional units 111 to 115 may be realized by using both software and hardware. Further, each of the functional units 111 to 115 is a conceptual component. A function executed by one component may be distributed to multiple components. Further, functions possessed by multiple components may be integrated into one component.

[0034] The acquisition unit 111 acquires information from outside the information processing device 1. The acquisition unit 111 acquires information from outside via, for example, the communication network 5 and the communication unit 13. The information acquired via the communication network 5 includes information from the people flow estimation device 2, the external server 3, and the terminal device 4. The acquisition unit 111 may also acquire information from outside by manual input using an input device. The input device is a device connected to the information processing device 1, or a device included in the information processing device 1. The acquisition unit 111 may also acquire information from outside by reading information from a recording medium such as an optical disk.

[0035] The acquisition unit 111 acquires, for example, information on a user (user information), information on a destination point (location information), information on a task assigned to the user at the destination point (task information), and information on a coupon that can be exchanged for points held by the user (coupon information). Note that the user is a person who participates in a roaming event. The destination point is a place where the user roams in the roaming event.

[0036] The acquisition unit 111 appropriately stores information acquired from the outside in the memory unit 12. At least a part of the information stored in the memory unit 12 may be deleted when a predetermined period of time has passed. The acquisition unit 111 stores, for example, user information, location information, task information, coupon information, and the like acquired from the outside in the memory unit 12 as table information.

[0037] FIG. 3 is a diagram showing an example of the user information table 121. The user information table 121 is information obtained by the acquisition unit 111 in the form of a table and stored in the memory unit 12. The acquisition unit 111 acquires the user information from, for example, the terminal device 4. The user information is information on users who have registered as users among the participants of the event. Here, the user is not limited to an individual, but is a broad concept of a user that includes a group (a group of people who essentially act together in a migratory event). The acquisition unit 111 acquires the user information from, for example, the terminal device 4 of a representative user of the group. As shown in FIG. 3, the user information table 121 includes a user ID, a location, a participation status, a visited location, owned points, owned coupons, and the number of members.

[0038] "User ID" is identification information that identifies each user. "User ID" functions as the primary key of user information table 121. A data record is generated for each user ID. The data record stores information corresponding to each user ID, such as "location," "participation status," "visited locations," "owned points," "owned coupons," and "number of members."

[0039] "Location" is information indicating the current location of the user. The current location of the user can be obtained, for example, from a GPS receiver or the like provided in the terminal device 4 owned by the user. The current location is expressed, for example, by latitude and longitude. In the example shown in FIG. 3, for convenience of explanation, the information indicating "location" is expressed abstractly, such as "position UP1". However, in reality, the information indicating the location is a specific numerical value expressed by latitude and longitude. In this specification and drawings, each table information may be expressed abstractly in a similar manner.

[0040] The "participation status" is information indicating the participation status of the user in the migratory event. Specifically, the participation status includes "before participating" indicating a state before participating in the event, "participating" indicating participating in the event, and "finished" indicating participation in the event has ended. The "visited location" is information indicating a location that has been visited among destinations that the user should visit in the migratory event. The "owned points" is information on the number of points owned by the user. Note that a user who participates in a migratory event may earn points depending on the situation, and may also use (consume) points. Details of points will be described later. The "owned coupon" is information on coupons owned by the user. The user can exchange points for coupons as appropriate, and the "owned coupon" includes information on coupons that the user has acquired by exchanging points. Note that in this example, the "owned coupon" is registered with a coupon ID (see FIG. 6) described later. That is, the user information table 121 and the coupon information table 124 (see FIG. 6) are used in association with each other. The "members" is information indicating the number of members of the user's group. In addition, if an individual participates in a roaming event, the number of participants will be 1.

[0041] In the example shown in FIG. 3, a user identified by a user ID "US01" has a current location of "Location UP1", and a participation status of the event is "before participation", so the visited location is "none". The number of points held by the user is "Points PP1", and the number of coupons held is "none". The user is participating in the event with "3 people". The user information table 121 may include other information such as the user's name, place of residence, email address, gender, age, etc. The registered information for each item in the user information table 121 may be updated as appropriate.

[0042] 4 is a diagram showing an example of the point information table 122. The point information table 122 is information that is obtained by the acquisition unit 111 and organized into a table and stored in the memory unit 12. The acquisition unit 111 acquires the point information, for example, from the external server 3, a terminal (not shown) of a store that is the destination point, or by manual input, etc. As shown in FIG. 4, the point information table 122 stores a point ID, a position, a point arrival point, a task, a participation point, a clear point, a point type, and congestion information.

[0043] "Point ID" is identification information that identifies each destination point to be visited in a migratory event. "Point ID" functions as the primary key of point information table 122. A data record is generated for each point ID. The data record stores information corresponding to each point ID, such as "location," "point arrival point," "task," "participation point," "clear point," "point type," and "congestion information."

[0044] "Location" is information indicating the location of a destination point on a map. The location is information expressed, for example, by latitude and longitude. "Destination arrival points" is information on the number of points given to a user participating in a migratory event when the user reaches a destination point that the user should visit. "Task" is information on a task assigned to a user at the destination point of a migratory event. Note that in this example, a task ID (see FIG. 5), which will be described later, is registered in "task." In other words, the destination information table 122 and the task information table 123 are used in association with each other.

[0045] "Participation points" is information on the number of points required for a user participating in a roaming event to participate in a task at a destination point to be visited by the user. That is, in this embodiment, the user pays points at the destination point to participate in the task. Participation in the task at the destination point may be mandatory, but need not be mandatory. "Clear points" is information on the number of points the user acquires when the task is successful (cleared).

[0046] It should be noted that the points to be awarded or paid at the destination point do not necessarily have to be set. In other words, at least one of the point arrival points, participation points, and clear points may not be set. The number of points to be awarded and the number of points to be paid may be determined in advance, for example, by the event organizer or a facility such as a store that is the destination point. However, the number of points to be awarded may be determined by a machine, not a human, using AI or the like.

[0047] The "point type" is information indicating the type (attribute) of the destination point. Specifically, the point type may be, for example, a store, a park, a shrine, a temple, an amusement park, or a stadium.

[0048] The "congestion information" is information indicating the degree of congestion at a destination point. It is preferable that the congestion information includes not only the current congestion degree but also the future congestion degree (estimated congestion degree). The congestion degree is an index value indicating the degree of congestion at each destination point (location). In detail, the congestion degree may be, for example, the density of people estimated to stay at the destination point, for example, the average number of people per a predetermined area such as per 100 square meters. The congestion degree may be information indicated by a level value divided into several stages according to the density of people and the magnitude of the congestion rate. The current congestion degree may be calculated by a machine (such as the people flow estimation device 2 or the controller 11) using, for example, image data obtained from a camera set around the destination point described above, or carrier data obtained from the terminal device 4 owned by the user. The current congestion degree may be obtained by counting the number of visitors who stay at the destination point. The estimated congestion degree may be calculated by the people flow estimation device 2 described above.

[0049] In this embodiment, the congestion information is acquired using people flow estimation that estimates the flow of people visiting multiple destinations set in a migratory event. The people flow estimation is performed by the people flow estimation device 2. That is, the acquisition unit 111 (controller 11) acquires the congestion information as a result of people flow estimation performed externally. However, the acquisition unit 111 may also acquire the congestion information by performing people flow estimation by itself. In order to acquire the congestion information as a result of people flow estimation, measures to alleviate congestion can be implemented before congestion actually occurs.

[0050] In the example shown in FIG. 4, the destination point identified by the point ID "PO01" is located at "position DP1" on the map, and the number of point arrival points given to a user who reaches the point is "point AP1". Furthermore, at the point, the task ID of the task assigned to the user is "TK01", the participation points for the task are "point JP1", and the clear points given to a user who succeeds (clears) the task are "point CP1". Furthermore, the destination point has a point type of "store", and the congestion information of the destination point is "congestion information KD1". Note that the point information table 122 may include other information such as the name of the destination point, recommended information at the destination point (such as gourmet information or tourist information), or the difficulty level of the task at the destination point. Furthermore, the registered information of each item in the point information table 122 may be updated as appropriate.

[0051] 5 is a diagram showing an example of the task information table 123. The task information table 123 is information in which the task information acquired by the acquisition unit 111 is organized into a table and stored in the memory unit 12. The acquisition unit 111 acquires task information, for example, from a manual input by an event organizer or the like, a terminal (not shown) of a store that is the destination point, an external server 3, or the like. As shown in FIG. 5, the task information table 123 stores a task ID, a target point ID, a task type, task difficulty, task content, and the like.

[0052] "Task ID" is identification information that identifies the task assigned to the user at the destination point of the wandering event. "Task ID" serves as the primary key of task information table 123. A data record is generated for each task ID. The data record stores information corresponding to each task ID, such as "target location ID," "task type," "task difficulty," and "task content."

[0053] The "target point ID" is identification information indicating the position of the destination point where the task is provided. The same ID as the point ID shown in FIG. 4 is used as the point target ID. That is, from this point of view, the task information table 123 is linked to the point information table 122. The "task type" is information indicating the type of the task. Specific examples of the task type are quiz, puzzle solving, game, photography, stamp collection, etc. The "task difficulty" is information indicating the difficulty of the task. The difficulty of the task may be numerically expressed information or information divided into multiple levels. For example, the information indicating the task difficulty may be three levels of information, namely, "high" indicating that the task is difficult to accomplish, "medium" indicating that the task is of medium difficulty, and "low" indicating that the task is easy to accomplish. The "task content" is information indicating the specific content of the task. For example, if the task type is a quiz, the specific content of the quiz is registered in the "task content".

[0054] In the example shown in Figure 5, the task identified by the task ID "TK01" is a task targeted at the location ID "PO01", the task type is "quiz", the task difficulty is "low", and the task content is "task TC1".

[0055] In the example shown in FIG. 5, three tasks with task IDs "TK01", "TK02", and "TK03" are tasks targeted at the location ID "PO01". That is, it can be seen that three types of tasks with different task difficulty levels are prepared in advance for the location ID "PO01". In the location information table 122 shown in FIG. 4, the task ID "TKO1" is registered as a task for the location ID "PO01". For this reason, it can be seen by referring to the task information table 123 that a quiz with a low task difficulty level (easy) is set as a task at the destination point registered with the location ID "PO01". The difficulty level of the task can be changed by changing the task ID of the task in the location information table 122. It is not necessarily necessary to prepare multiple types of tasks at all destination points, and only one task may be prepared at a certain destination point.

[0056] The task information table 123 may include other information such as hints for completing a task, a person in charge of the task, etc. The registered information for each item in the task information table 123 may be updated as appropriate.

[0057] Fig. 6 is a diagram showing an example of the coupon information table 124. The coupon information table 124 is information in which the coupon information acquired by the acquisition unit 111 is organized into a table and stored in the memory unit 12. The acquisition unit 111 acquires coupon information, for example, from a manual input by an event organizer or the like, a terminal (not shown) of a store that is a destination point, the external server 3, or the like. As shown in Fig. 6, the coupon information table 124 stores a coupon ID, a provider, coupon contents, exchange points, and the like.

[0058] "Coupon ID" is identification information that identifies a coupon that can be exchanged for points acquired by a user at a roaming event. The coupon is an exchange ticket, and more specifically, may be a discount ticket or a preferential coupon. The coupon is, for example, an electronic exchange ticket. "Coupon ID" serves as the primary key of coupon information table 124. A data record is generated for each coupon ID. Information corresponding to each coupon ID, such as "provider," "coupon content," and "exchange points," is stored in the data record.

[0059] "Provider" is information that identifies the store or other facility that issues the coupon. Specifically, the provider may be the name of the store or other facility. "Coupon content" is information that indicates the specific content of the coupon. For example, "free glass of juice" or "10% off food and drink." "Exchange points" is information that indicates the number of points required to exchange the coupon in question.

[0060] In the example shown in FIG. 6, the coupon identified by the coupon ID "CP01" is provided by "facility SH1". The user can obtain a coupon with the coupon content "coupon CC1" by paying redemption points "points EP1". The coupon information table 124 may include other information such as the address, telephone number, and email address of the coupon provider, or the remaining number of redeemable coupons. The registered information for each item in the coupon information table 124 may be updated as appropriate.

[0061] 2, the user management unit 112 manages each user participating in the roaming event. The user management unit 112 executes user-related management by exchanging data with the terminal device 4 of each user via the communication network 5.

[0062] The user management unit 112 accepts registration of a user in the information processing system 100 and registers user information. For example, the user management unit 112 permits a user who has registered in the system 100 to log in to a site for a migratory event. For example, the user management unit 112 recognizes the start and end of a migratory event by a user, arrival at a destination point during participation in the event, and completion of a task at each destination point from the user's operation on the terminal device 4 and the location information of the terminal device 4. The user management unit 112 appropriately updates the user information table 121 based on the recognized information. The update also includes an update of owned points that change according to the user's actions.

[0063] The user earns points according to the above-mentioned point arrival points and clear points. The user also consumes points according to the above-mentioned participation points and exchange points. These are merely examples, and the user may earn points according to, for example, initial registration with the system 100, the walking distance during the event, shopping at a store during the event, or participation in a questionnaire regarding the event.

[0064] The event management unit 113 manages various settings required for executing a roaming event. The various settings include, for example, settings related to the event's holding time, settings related to the event's destination, settings of points for the event, and settings of coupons that can be exchanged for points. The event management unit 113 manages, for example, the location information table 122, task information table 123, and coupon information table 124 described above.

[0065] In this embodiment, the event management unit 113 (controller 11) changes the setting conditions given to a user traveling between multiple destination points according to congestion information at the multiple destination points. In other words, the event management unit 113 causes the computer to change the setting conditions given to a user traveling between multiple destination points according to congestion information at the multiple destination points. In this embodiment, the congestion information includes not only the current congestion situation but also the future congestion situation (estimated congestion situation). However, the congestion information may be configured to include only one of the current congestion situation and the future congestion situation. In a preferred embodiment, the congestion information is information acquired by the controller 11 in real time.

[0066] In this way, by changing the setting conditions given to users in a roaming event based on congestion information, the time spent at each destination by users participating in the event can be adjusted. As a result, congestion at each destination to which the user roams can be prevented. In other words, the satisfaction of event participants (users) can be improved. In addition, the burden on those who host (operate) the event can be reduced. Furthermore, since it is possible to prevent people from concentrating in a specific location, it can also serve as an infectious disease prevention measure. Specific examples of changing the setting conditions based on congestion information will be described later.

[0067] The notification unit 114 appropriately notifies the user of information that needs to be notified. Information that needs to be notified to the user is, for example, information related to the management of the roaming event and information related to changes in the user's points. In this embodiment, the information related to the management of the roaming event includes information related to changes in the setting conditions according to the congestion information described above. That is, the notification unit 114 (controller 11) notifies the terminal device 4 owned by the user of the changes in the setting conditions. This allows the user to quickly understand the changes in the setting conditions.

[0068] The points redemption unit 115 performs a process of exchanging the points owned by the user for a coupon in response to a request from the user. The details of this process will be described later.

[0069] The controller 11 may have functions other than those described above. For example, the controller 11 may have a function of providing the user with travel guidance using transportation such as a taxi when the travel distance between the user's destinations is equal to or greater than a predetermined distance (e.g., 1 km) in cooperation with the external server 3.

[0070] Here, specific examples (three examples) of changing the setting conditions according to congestion information, which is executed by the event management unit 113, will be described. FIG. 7A is a diagram showing preconditions for explaining an example of changing the setting conditions according to congestion information. As shown in FIG. 7A, the visiting (circulating) route in a migratory event is set to visit points A, B, C, and D in that order. Then, it is predicted that a concentration (congestion) of people will occur at point C by estimating people flow using the people flow estimation device 2. The visiting route may or may not be notified to the participants in advance. An example of the latter is a configuration in which the next visiting point is known by visiting each visiting point. Specifically, an example can be given in which the answer to a quiz given at each visiting point is the next visiting point.

[0071] [2-1. First Example] FIG. 7B is a diagram for explaining a first embodiment of changing the setting conditions according to congestion information. As shown in FIG. 7B, in the first embodiment, the travel route is changed according to the congestion information. In other words, the change of the setting conditions may include a route change that changes the visiting route of a plurality of predetermined destination points. By changing the visiting route according to the congestion information, the flow of people can be changed, and the occurrence of congestion can be suppressed.

[0072] In the example shown in FIG. 7B, the setting of the visiting route is changed to the order of point A, point B, point D, and point C. However, this route change is merely an example, and how to change the visiting route may be determined as appropriate. Also, how to change the visiting route may be determined by a person or automatically by a machine (controller 11). When the visiting route is automatically determined by a machine, the positional relationship between the visiting points and the result of the people flow estimation by the people flow estimation device 2 may be used. Also, in an example where the next visiting point is revealed by a quiz given at a visiting point, the content of the quiz given at each visiting point needs to be changed in response to the change in the visiting route.

[0073] It is preferable that the change in the visiting route is effective only for participants (some participants) whose future visiting routes should be changed as a result of the change. For example, in the case of the preconditions shown in FIG. 7A, it is not necessarily appropriate to change the route of a participant who has already arrived at point C or is heading to point C. For this reason, it is preferable that the route change is not applied to such participants. In the example shown in FIG. 7, for example, it is preferable that the route change is effective for participants who have not yet visited points A and B.

[0074] FIG. 7C is a diagram for explaining a modified example of the first embodiment. In other words, FIG. 7C is a diagram for explaining a modified example of route change for changing the visiting route. As shown in FIG. 7C, when congestion at point C is expected, a configuration may be adopted in which a point C1 is set to replace point C. Note that the alternative point C1 may be stored in advance in the memory unit 12 or the like, and may be automatically set when a route change is required. However, this is not limiting, and an alternative point may be set in response to a request from a facility such as a store that has registered to participate in a roaming event, for example.

[0075] In addition, in this example, the configuration is such that the visiting points (and the associated route change) are changed in response to congestion information, but the visiting points may also be changed when, for example, danger information such as near-miss information (partial damage to a building) is acquired from the external server 3 or the like. At this time, the people flow estimation device 2 may predict the flow of people taking into account the danger information, and the route may be changed. Note that when the route is changed in response to danger information, in some cases, it is not necessary to set an alternative visiting point. In other words, a route change that changes the visiting route may include the deletion of some of the visiting points.

[0076] [2-2. Second Example] In the second embodiment, the event management unit 113 (controller 11) changes the incentive given to the user at at least one of the multiple destination points in response to the congestion information. That is, the change in the setting conditions made in response to the congestion information may include an incentive change that changes the incentive given to the user at at least one of the multiple destination points. Note that the incentive is some kind of reward given to the user. The incentive may be, for example, points, coupons, or both. It is expected that the granting of the incentive will cause some of the event participants to change their behavior schedules. Then, the occurrence of those who change their behavior schedules can suppress the occurrence of congestion.

[0077] Specifically, the event management unit 113 (controller 11) extracts a congested point from among multiple destination points based on congestion information, and increases the incentive at a destination point just before the congested point. The incentive makes people stay at a point just before the congested point, and congestion at the destination point that is considered to be a congested point can be suppressed.

[0078] It is not necessary that the congested point is extracted based on the congestion information, but it may be extracted when there is a point that is predicted to be congested or a point that is determined to be congested. Whether or not a point is a congested point may be determined, for example, based on whether or not the congestion level exceeds a preset congestion level threshold.

[0079] For example, in the case of the preconditions shown in FIG. 7A, the incentive given to the user is set high at point B, which is a fixed destination point just before point C (congested point) where congestion is expected. Specifically, the longer the user stays at point B, the more the point arrival points are increased. For example, if the stay time is less than 15 minutes, the point arrival points are 100 points, and if the stay time is between 15 minutes and 30 minutes, the point arrival points are 150 points. Points are increased according to the length of stay. However, in order to prevent too many people staying at point B for a long time, causing congestion at point B, an upper limit may be set on the number of points given by the incentive.

[0080] It is preferable that the incentive change is effective only for participants (some participants) for whom the change affects the congestion situation. For example, in the case of the preconditions shown in FIG. 7A, there is no need to inform participants who have already reached point C of the incentive change. Therefore, the incentive change does not need to be applied to such participants. In the example shown in FIG. 7A, for example, it is preferable that the incentive change is effective for participants who have not yet visited point A or point B, and participants who have reached point B.

[0081] [2-3.Third Example] In a third embodiment, the event management unit 113 (controller 11) changes the difficulty of a task performed by a user at at least one of the multiple destination points in response to congestion information. That is, the change in the setting conditions performed in response to congestion information may include a difficulty change that changes the difficulty of a task performed by a user at at least one of the multiple destination points. Note that a task is a job or assignment assigned to a user at each destination point, such as answering a quiz or playing a game. By changing the difficulty of the task, the time that an event participant stays at each destination point can be adjusted. This makes it possible to prevent people from concentrating (causing congestion) at any one of the destination points.

[0082] Specifically, the event management unit 113 (controller 11) extracts a congested point from among a plurality of destination points based on congestion information. Then, the event management unit 113 executes at least one of lowering the difficulty level of the task at the congested point and raising the difficulty level of the task at a destination point just before the congested point. Note that the congested point does not necessarily need to be extracted based on congestion information, as in the case described in the second embodiment.

[0083] By lowering the difficulty of the tasks at the crowded points, the time spent by event participants at the crowded points can be shortened. Also, by increasing the difficulty of the tasks at destination points before the crowded points, the time spent by event participants at destination points before the crowded points can be lengthened. This makes it possible to prevent people from congesting at crowded points.

[0084] For example, in the case of the preconditions shown in Fig. 7A, a task with a low level of difficulty (e.g., a quiz) is set at point C (congested point) where congestion is expected. Also, in the case of the preconditions shown in Fig. 7A, a task with a high level of difficulty (e.g., a quiz) is set at point B just before point C (congested point) where congestion is expected. Note that the event management unit 113 refers to the task information table 123 (see Fig. 5), for example, to select a task (task ID) with the set level of difficulty.

[0085] It is preferable that the change in the difficulty of the task is effective only for participants (some participants) for whom the change affects the congestion situation. For example, in the case of the preconditions shown in FIG. 7A, there is no need to inform participants who have already completed the task at point C of the difficulty change. For this reason, it is preferable that the difficulty change is not applied to such participants. In the example shown in FIG. 7A, for example, it is preferable that the difficulty change is effective for participants who have not yet completed the task at point C. It is also possible that the difficulty change is not applied to those who have not completed the task at point C but know the task content.

[0086] [2-4.Other] The change of the setting conditions according to the congestion information may be implemented by combining at least two of the methods of the first embodiment, the second embodiment, and the third embodiment described above. For example, the route may be changed while increasing the incentive at the point next to the congestion point. In the case of the preconditions shown in FIG. 7A, the incentive at the point D next to the congestion point C may be increased while the order of visiting destination points may be changed so that the point D comes before the point C.

[0087] In addition, for example, there may be participants who do not want to change the route or the difficulty of the task. For this reason, when changing the setting conditions such as changing the route or changing the difficulty of the task, the user may be allowed to select whether or not to make the change.

[0088] <3. Information processing method> Next, a specific example of an information processing method executed by the information processing device 1 will be described.

[0089] Fig. 8 is a flowchart showing an example of processing that the information processing device 1 performs for each user participating in the migratory event. The processing shown in Fig. 8 is performed separately for each user (each terminal device 4), and is usually performed at different times for each user. The processing shown in Fig. 8 is based on the premise that the user has completed registration for participation in the information processing system 100 using the terminal device 4 and started the migratory event. The information processing device 1 recognizes that the user has started participating in the migratory event, for example, from a start notification from the user using the terminal device 4.

[0090] In step S1, the user management unit 112 starts providing the necessary information to the terminal device 4. The user management unit 112 provides the necessary information to the terminal device 4 at an appropriate timing as appropriate. The necessary information may be automatically distributed to the terminal device 4 by a machine (information processing device 1), or may be distributed to the terminal device 4 by the information processing device 1 in response to a request from a user using the terminal device 4.

[0091] The necessary information includes, for example, map information including each destination point in a roaming event, information related to each destination point, information on changes to setting conditions related to the event, and information related to the user's points, etc. The information on each destination point includes, for example, information on facilities (stores, etc.) present at the destination point, information on tasks given to the user at the destination point, and congestion information at the destination point, etc.

[0092] When the provision of the necessary information to the terminal device 4 starts, the process proceeds to the next step S2. When the terminal device 4 is provided with the necessary information from the information processing device 1, the terminal device 4 appropriately displays the provided information on the screen of the terminal device 4. Before describing the process of step S2 performed by the information processing device 1, an example of the screen of the terminal device 4 after the provision of the necessary information starts (during participation in the roaming event) will be described. Fig. 9 is a diagram showing an example of the screen of the terminal device 4 owned by a user participating in the roaming event.

[0093] The screen illustrated in Fig. 9 includes a map area R1, a point display area R2, and an operation unit display area R3. The map area R1 occupies more than half of the screen and displays the destination point of the roaming event and a map of the surrounding area. For example, the destination point and the user's current location are displayed on the map displayed in the map area R1.

[0094] In the example shown in FIG. 9, the difficulty of the task to be performed by the user at each destination point and congestion information for each destination point are displayed superimposed on a map. As an example, the difficulty of the task is displayed in three levels, "high," "medium," and "low," in order of increasing task difficulty. The congestion information includes the current congestion level and the congestion level in the future (for example, one hour from now). Each congestion level is displayed in two levels, "congested," indicating that the area is crowded, and "empty," indicating that the area is not crowded.

[0095] The difficulty and congestion information of the task do not need to be displayed for all destination points. In addition, the difficulty and congestion information of the task do not necessarily need to be displayed superimposed on the map. That is, the terminal device 4 may display the difficulty and congestion information of the task performed by the user for at least one of the multiple destination points to which the user travels. In other words, the controller 11 may perform a process that enables the difficulty and congestion information of the task at the destination point to be displayed on the screen of the terminal device 4 owned by the user. With such a configuration, the event participants can grasp the situation of the destination point before visiting. This allows the event participants to make a travel schedule according to the situation of the destination point. In addition, if each participant can decide the travel route of the travel-type event, the destination point can be visited while avoiding the crowded points.

[0096] The point display area R2 displays the number of points currently held by the user. This allows the user to quickly grasp the number of points he or she owns. The operation unit display area R3 displays various buttons BN1 that the user can operate. In this example, the buttons BN1 are software keys, but they may also be physical buttons. In the example shown in FIG. 9, the buttons BN1 include "Home", "Acquired Coupons", "Check-in", "Crowd Information", and "Menu", but the number and types of buttons BN1 may be changed as appropriate.

[0097] "Home" is a button that instructs the display of the home screen. "Acquired Coupons" is a button that displays coupons that the user has already acquired. "Check-in" is a button that notifies the user that they have reached their destination. "Crowd Information" is a button that switches between displaying and hiding the congestion information displayed on the map. "Menu" is a button that is used to select various functions other than the above-mentioned functions that can be performed using button BN1.

[0098] Returning to FIG. 8, in step S2, the user management unit 112 determines whether or not the user has arrived at the destination point. In this embodiment, the user management unit 112 detects when the user uses the terminal device 4 to notify (check-in notification) that the user has arrived at the destination point. However, this is an example, and the user's arrival at the destination point may be automatically detected based on the user's current location information obtained from the terminal device 4. If it is determined that the user has arrived at the destination point (Yes in step S2), the process proceeds to the next step S3. If it is not determined that the user has arrived at the destination point (No in step S2), the process of step S2 is repeated.

[0099] In step S3, the user management unit 112 executes a process (arrival response process) corresponding to the user's arrival at the destination point. The arrival response process includes, for example, giving the user point arrival points (see FIG. 4). The user management unit 112 performs a process of updating the points held in the user information table 121 in response to the point arrival points being given. The updated information on the points held may be notified to the user by the notification unit 114 as appropriate. The arrival response process also includes a process of providing task information to the user. The user management unit 112 refers to, for example, the point information table 122 and the task information table 123 to determine the task information to be provided to the user, and provides the task information. When the arrival response process is completed, the process proceeds to the next step S4.

[0100] In step S4, the user management unit 112 judges whether the user has achieved the location clearing condition. The location clearing condition is achieved, for example, by performing a task (such as a quiz). The execution of a task may include not only a case where the task is successful, but also a case where the task is failed. However, there may be a case where the task is not required to be performed, or a location where a task is not set may exist. For this reason, the location clearing condition may be achieved by something other than the execution of a task. For example, the location clearing condition may be achieved when the destination point is reached. Also, the location clearing condition may be achieved when the stay time at the destination point exceeds a specified time. The user management unit 112 judges whether the user has achieved the location clearing condition based on information obtained from the terminal device 4, or information obtained from a person or machine that performs task management at each destination point, if there is such information. If it is judged that the user has achieved the location clearing condition (Yes in step S4), the process proceeds to the next step S5. On the other hand, if it is judged that the user has not achieved the location clearing condition (No in step S4), the process of step S4 is repeated.

[0101] In step S5, the user management unit 112 executes a process (location clearing process) corresponding to the user's achievement of the location clearing condition. The location clearing process includes, for example, a point process required for the user's execution of the task. Specifically, a calculation process is performed regarding the participation points that must be paid for participation in the task and the clear points (see FIG. 4) that are granted when the task is successful (cleared). Then, according to the result of the calculation process, the user management unit 112 performs a process of updating the points held in the user information table 121. The location clearing process also includes a process of updating the visited locations in the user information table 121. When the location clearing process is completed, the process proceeds to the next step S6.

[0102] In step S6, the user management unit 112 determines whether the user has visited all destination points. The user management unit 112 can determine whether the user has visited all visited points by referring to the information on visited points in the user information table 121. If all destination points have been visited (Yes in step S6), the process proceeds to the next step S7. If all destination points have not been visited (No in step S6), the process returns to step S2, and the processes from step S2 onwards are performed again.

[0103] In step S7, the user management unit 112 performs an event completion process. The event completion process includes, for example, a process of generating a completion certificate (electronic data or the like) for the roaming event, a process of generating a participation record such as a user's record regarding the event, or a process of finalizing the points held. When the event completion process is completed, the process shown in FIG. 8 ends.

[0104] Fig. 10 is a flowchart showing an example of processing related to changing the setting conditions in a migratory event, executed by the information processing device 1. The processing shown in Fig. 10 is continuously performed from the start time to the end time of the event determined by the organizer of the migratory event. The processing shown in Fig. 10 is also performed in parallel with the processing shown in Fig. 8 described above.

[0105] In step S11, the event management unit 113 determines whether or not the setting conditions need to be changed according to the congestion information at each destination point acquired in real time from the people flow estimation device 2. For example, when it is estimated that there is a destination point whose congestion level exceeds a predetermined congestion level threshold after a certain time (e.g., after 15 minutes), the event management unit 113 determines that the setting conditions need to be changed. On the other hand, when it is estimated that there is no destination point whose congestion level exceeds a predetermined congestion level threshold after a certain time, the event management unit 113 determines that the setting conditions do not need to be changed. If it is determined that the setting conditions need to be changed (Yes in step S11), the process proceeds to the next step S12. If it is determined that the setting conditions do not need to be changed (No in step S11), the process proceeds to step S14.

[0106] In step S12, the event management unit 113 performs a process of changing the setting conditions. The process of changing the setting conditions may include at least one of a process of changing the travel route, a process of changing the incentive, and a process of changing the difficulty level of the task, as described above. The process of changing the setting conditions includes a change of table information in the memory unit 12 that is required in accordance with the change of the setting conditions. For example, when the difficulty level of the task is changed, a process of changing the task ID in the location information table 122 (see FIG. 4) is included. Once the change process is executed, the process proceeds to the next step S13.

[0107] In step S13, the notification unit 114 performs a notification process related to the change in the setting conditions. The notification unit 114 may notify all event participants of the change in the setting conditions. However, it is preferable that the notification unit 114 notifies the change in the setting conditions only to those event participants who are the targets of the change in the setting conditions. When the process of notifying the change in the setting conditions is completed, the process proceeds to the next step S14.

[0108] In addition, in the terminal device 4 that has been notified of the change in the setting conditions, a process of displaying the change on the screen is appropriately performed. The display process may be performed automatically by the terminal device 4 or may be performed in response to an instruction from the user. FIG. 11 is a diagram showing an example of a screen of the terminal device 4 when the setting conditions are changed. In FIG. 11, the change in the setting conditions is assumed to be a change in the difficulty level of the task. Notification information IF1 notifying details of the change in the setting conditions is displayed on the screen of the terminal device 4. In FIG. 11, the notification information IF1 is displayed large at a position overlapping the map area R1. After being displayed on the screen, the notification information IF1 may be displayed for a preset period of time and then automatically hidden, or may be hidden in response to an instruction from the user.

[0109] In step S14, the event management unit 113 determines whether it is the end time of the event determined by the organizer of the roaming event. If it is the event end time or has passed (Yes in step S14), the process shown in Fig. 10 ends. If it is a time before the event end time (No in step S14), the process returns to step S11 and the processes from step S11 onwards are performed again.

[0110] Fig. 12 is a flowchart showing an example of a point redemption process executed by the information processing device 1. The process shown in Fig. 12 may be executed at any time within a preset point redemption period, and may be executed during or after an event is held. A user may redeem points while participating in an event. In this embodiment, redemption of points refers to exchanging points owned by the user for a coupon.

[0111] In step S21, the point redemption unit 115 determines whether or not a point redemption request has been made by the user. The user makes a point redemption request using the terminal device 4. The point redemption request includes information on the coupon for which the user wishes to redeem points (e.g., a coupon ID; see FIG. 6). It is preferable that the information processing device 1 appropriately distributes information (type) of coupons that can be redeemed for points held by the user to the terminal device 4 held by the user. The distribution may be performed automatically or upon request from the user. If a point redemption request has been made by the user (Yes in step S21), the process proceeds to the next step S22. If a point redemption request has not been made by the user (No in step S21), the process of step S21 is repeated.

[0112] In step S22, the point exchange unit 115 performs a screen display process to display information related to point exchange on the screen of the terminal device 4. The screen display process, in detail, includes the generation of a screen including point information and the delivery process of the generated screen information to the terminal device 4. When generating the screen including point information, the point exchange unit 115 appropriately refers to the coupon information table 124. When the screen display process is completed, the process proceeds to step S23.

[0113] The terminal device 4 that has received the screen information performs a process of displaying the delivered screen information on its own screen. FIG. 13 is a diagram showing an example of a screen related to point redemption displayed on the terminal device 4. As shown in FIG. 13, the screen of the terminal device 4 includes information on a coupon obtained by point redemption and point information related to point redemption. The coupon information includes store information where the coupon can be used and the contents of the coupon. The point information includes points required for redemption of the coupon (points to be consumed) and the number of points remaining after point redemption. Also, a confirmation button BN2 that the user presses to confirm the redemption of the coupon is displayed on the screen of the terminal device 4. The confirmation button BN2 is a software key.

[0114] In step S23, the point exchange unit 115 judges whether or not the point exchange requested by the user may be confirmed. The point exchange unit 115 confirms the point exchange when there is a confirmation notification from the user of the point exchange using the terminal device 4. For example, when the user presses the confirmation button BN2 shown in FIG. 13, a confirmation notification of the point exchange is sent from the terminal device 4 to the information processing device 1. If there is no confirmation notification from the terminal device 4 within a preset certain period of time, it is judged that the user does not want to exchange the points. If it is judged that the point exchange may be confirmed (Yes in step S23), the process proceeds to the next step S24. If it is judged that the user does not want to exchange the points (No in step S23), the process shown in FIG. 12 is terminated.

[0115] In step S24, the point redemption unit 115 performs a point redemption process. The point redemption process includes issuing a coupon and delivering the issued coupon to the terminal device 4. In this embodiment, the coupon issued is data that functions as a coupon in the terminal device 4. The data may be information displayed on the screen of the terminal device 4, such as barcode information or two-dimensional code information. The point redemption process also includes updating the owned points and owned coupons in the user information table 121 in response to the user's use of points. When the point redemption process is completed, the process shown in FIG. 12 ends.

[0116] <4. Things to keep in mind> Various technical features disclosed in the description of the invention may be modified in various ways without departing from the spirit of the technical creation. Furthermore, the embodiments and modifications disclosed in the description of the invention may be combined to the extent possible. [Explanation of symbols]

[0117] 1. Information processing device 2...Person flow estimation device 11. Controller

Claims

1. An information processing device including a controller, The controller is an information processing device that changes the difficulty of a task to be performed at a destination point by a user traveling between multiple destination points, an incentive to be obtained at the destination point, or a route to visit the destination points, in accordance with congestion information at the multiple destination points.

2. A memory for storing information on the difficulty level of the task divided into a plurality of levels, The information processing device according to claim 1 , wherein the controller changes a difficulty level of a task to be performed by the user at at least one of the plurality of destination points.

3. The controller: extracting congestion points from among the plurality of destination points based on the congestion information; The information processing device according to claim 2 , further comprising: at least one of lowering a difficulty level of the task at the congested point and increasing a difficulty level of the task at the destination point just before the congested point.

4. The information processing device according to claim 2 , wherein the controller performs processing to enable display of the difficulty level of the task and the congestion information at the destination point on a screen of a terminal device owned by the user.

5. The information processing device according to claim 1 , wherein the incentive is at least one of points and a coupon given to the user.

6. The controller: extracting congestion points from among the plurality of destination points based on the congestion information; The information processing device according to claim 5 , wherein the incentive is increased at the destination point just before the congestion point.

7. The congestion information is obtained using people flow estimation that estimates a flow of people visiting the plurality of destination points; The information processing device according to claim 1 , wherein the controller obtains the congestion information as a result of the people flow estimation performed externally, or obtains the congestion information by performing the people flow estimation itself.

8. The information processing apparatus according to claim 1 , wherein the controller notifies a terminal device of the user of the change in the setting condition.

9. An information processing method in which a device executes a process of notifying a terminal device of a user traveling between multiple destination points of the difficulty of tasks to be performed at the destination points, incentives to be obtained at the destination points, or changes to the route to visit the destination points in response to congestion information at the multiple destination points.

10. A program that causes a computer to change the difficulty of a task to be performed at a destination by a user traveling to multiple destinations, the incentive obtained at the destinations, or the route to visit the destinations, in accordance with congestion information at the multiple destinations.

11. A terminal device owned by a user who travels around a plurality of destination points, A terminal device that displays the difficulty level and congestion information of a task to be performed by the user for at least one of the plurality of destination points.

Images