Information processing equipment

Abstract

To provide a technique capable of creating an attractive mission.SOLUTION: Information processing equipment comprises: a memory; a memory which stores a mission created by a host user and including at least one task; a monitor unit which monitors achievement of the mission by a guest user; and an imparting unit which imparts a first reward to the host user in a first case in which the monitor unit determines that the mission is achieved. The "information processing equipment" includes a server provided by a provider of service. The server includes, for example, a server for providing SNS (Social Network Service).SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The technology disclosed in this specification relates to an information processing apparatus.

Background Art

[0002] Patent Document 1 discloses a reward management system for managing rewards given to a plurality of users participating in an online event. In the system of Patent Document 1, reward granting criteria according to the user's rank are provided, and the satisfaction of each user participating in the online event is achieved.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the technology of Patent Document 1, the online events and missions that users can participate in are limited to those prepared by the organizer who hosts the event or mission. There is also a possibility that attractive events and missions may not be prepared.

[0005] This specification provides a technology capable of creating attractive missions.

Means for Solving the Problems

[0006] The information processing apparatus disclosed in this specification includes a memory, a memory that stores a mission created by a host user and includes at least one task, a monitoring unit that monitors whether a guest user achieves the mission, and a granting unit that grants a first reward to the host user when it is determined by the monitoring unit that the mission has been achieved in a first case.

[0007] The above-mentioned "information processing device" includes a server provided by a service provider. The server includes, for example, a server for providing an SNS (Social Network Service). The "host user" includes a user who newly creates a mission. The "guest user" includes a user who participates in a created mission. The host user may also act as a guest user. The "accomplishment of a mission" is not limited to accomplishing all at least one task included in the mission, but also includes accomplishing a predetermined number of tasks (or a predetermined percentage of tasks) among at least one task included in the mission. The accomplishment conditions of the mission may be determined by the host user. The "first reward" includes any valuable item such as, for example, a prize, a bonus, a coupon, points available within the service, a lottery participation right, etc. Also, the "first reward" may include the ability to participate in a specific mission (so-called "opening" of a specific mission). The "first reward" may include points related to the promotion or demotion of the user's rank, status, level, etc. within the service (for example, bronze, silver, gold, platinum, etc.).

[0008] According to the above configuration, when a guest user accomplishes a mission, a reward can be given to the host user who created the mission. For the host user, the giving of the reward can be a motivation to create attractive missions. As a result, more attractive missions that more guest users hope to participate in and accomplish can be created.

[0009] In the first case, the awarding unit may further award a specific reward to the guest user.

[0010] According to this configuration, for guest users, the granting of rewards can also serve as an incentive to participate in missions. It can also motivate host users to create more attractive missions. As a result, a virtuous cycle can be generated where more attractive missions can be created. Note that the "specific reward" also includes any valuable items such as prizes, bonuses, coupon vouchers, points that can be used within the service, lottery participation rights, etc. The "specific reward" may also include the ability to participate in specific missions (so-called "opening" of specific missions). The "specific reward" may also include points related to the promotion or demotion of a user's rank, status, level, etc. within the service.

[0011] The mission may include a plurality of the tasks. The monitoring unit may further monitor that the guest user achieves a first task that is a part of the plurality of tasks. The granting unit may grant a second reward smaller than the first reward to the host user when it is determined by the monitoring unit that the first task has been achieved in a second case.

[0012] The "second reward" also includes any valuable items such as prizes, bonuses, coupon vouchers, points that can be used within the service, lottery participation rights, etc. The "second reward" may also include the ability to participate in specific missions (so-called "opening" of specific missions). The "second reward" may also include points related to the promotion or demotion of a user's rank, status, level, etc. within the service. The "second reward" may be a part of the first reward (a part of the reward granted for achieving the mission), or it may be a reward different from the first reward and of less value than the first reward.

[0013] According to this configuration, even when a guest user does not complete all the missions but only completes some of the tasks of the mission, a reward can be granted to the host user. This can motivate the host user to create large-scale missions.

[0014] An expiration date may be set for the mission.

[0015] According to this configuration, since the mission has an expiration date, it is possible to give guest users a motivation to participate based on the feeling of exclusivity that the mission is time-limited. Attractive missions can be provided to guest users.

[0016] At least one of the tasks may include a second task involving actual activities in the real world by the guest user.

[0017] According to this configuration, it is possible to make guest users who participate in the mission perform tasks involving activities in the real world. Therefore, for example, attractive missions can be provided in cooperation with stores, tourist spots, classrooms, lectures, etc. of cultural schools in the real world.

[0018] A control method, a computer program, and a computer-readable recording medium storing the computer program for realizing the above information processing apparatus are also novel and useful. An information processing system including the above information processing apparatus is also novel and useful.

Brief Description of Drawings

[0019]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Embodiments for Carrying Out the Invention

[0020] (First Embodiment) (Overview of the System: Figure 1) The mission management system 2 shown in Figure 1 is a system for managing missions that users participate in and aim to achieve, and rewards given to users. The mission management system 2 of this embodiment includes a server 10 and user terminals 40 and 50. Both the server 10 and the user terminals 40 and 50 are connected to the Internet 4. The server 10 and the user terminals 40 and 50 can communicate via the Internet 4.

[0021] The user terminals 40 and 50 are smartphones, tablet terminals, notebook PCs, desktop PCs, etc. held by each user. In the example of Figure 1, the user terminal 40 is carried by the user U1 to whom the user ID "UID1" is assigned. The user terminal 50 is carried by the user U2 to whom the user ID "UID2" is assigned. Although only two user terminals 40 and 50 are shown in Figure 1, actually the mission management system 2 includes a plurality of user terminals according to the number of users using the system.

[0022] In the memories (not shown) of the user terminals 40 and 50, various programs such as an OS program, a browser application program, and an SNS application program of the SNS provided by the server 10 are stored. Hereinafter, in this specification, the application program may be simply referred to as "app". The SNS app is an app provided by an SNS operator (for example, the installer of the server 10). The user terminals 40 and 50 can access the server 10 according to the browser app or the SNS app. Users U1, U2, etc. can register their user information (user ID, password, etc.) with the server 10 by accessing the server 10 and performing a predetermined membership registration. A user who has completed membership registration may be referred to as a "member user". Both the users U1 and U2 in Figure 1 are member users. Member users U1, U2, etc. can post content (photos, articles, etc.) to the server 10 or view the content posted to the server 10 via the user terminals 40, 50, etc.

[0023] In addition, the member users U1 and U2 can participate in missions registered in the server 10 via the user terminals 40 and 50. A mission is an event, assignment, task, etc. that includes at least one task (action, work, etc.) that the user must accomplish. The member users U1 and U2 can also create their own missions and post them to the server 10. A member user who participates in a mission may be called a "guest user," and a member user who creates a mission may be called a "host user." All member users can act as guest users. A host user can also act as a guest user. In order for a member user to perform activities such as posting a mission as a host user, he or she may need to pass a prior screening by the administrator of the server 10, etc. In the example of FIG. 1, the user U1 is a host user and guest user, and the user U2 is a guest user (not a host user).

[0024] In this embodiment, a preset reward is given to a guest user who completes a mission. Furthermore, in this embodiment, when a guest user completes a mission, a preset reward is also given to the host user who created and posted the mission. The reward given to the guest user when the mission is completed and the reward given to the host user may be the same or different. The reward given to the guest user may be greater than the reward given to the host user.

[0025] As described above, the "mission" in this embodiment refers to events, tasks, missions, etc. that guest users can participate in. A mission includes at least one task. Preferably, a mission includes a plurality of tasks. The "task" mentioned here refers to small goals, small tasks, etc. that guest users should achieve. Therefore, for example, a "mission" may be a stamp rally or the like whose achievement condition is to reach the goal after passing all the checkpoints to be passed. In that case, the user's arrival at each checkpoint corresponds to each task, and reaching the goal after passing each checkpoint (i.e., after completing all tasks) may be the achievement condition of the mission. In addition to arriving at a checkpoint, the "task" may be to perform a specific action (for example, a user running a predetermined distance, performing training a predetermined number of times, purchasing a predetermined item, completing a predetermined work, etc.). Therefore, in another example, a "mission" may be a work event whose achievement condition is to complete the target work by completing a plurality of steps in a predetermined order (for example, completing a handicraft, completing cooking, etc.). Note that the achievement condition of a mission is not limited to achieving all at least one task included in the mission, and may be achieving a predetermined number of tasks (or a predetermined percentage of tasks) among at least one task included in the mission. The achievement condition of a mission may be arbitrarily determined by the host user.

[0026] In this embodiment, at least one of the tasks included in the mission is a task involving the actual activities of the guest user in the real world (for example, arriving at a predetermined place in the real world, etc.). In other examples, all of the tasks included in the mission may be those that do not involve the actual activities of the guest user in the real world (for example, a character representing the guest user in the game clearing a predetermined condition, etc.).

[0027] (Configuration of Server 10; FIGS. 1 to 3) The configuration of server 10 will be described in detail. Server 10 is a server provided by an operator that offers an SNS. Server 10 provides services such as posting content such as images and comments posted by member users on web pages so that other users can view them. Further, in this embodiment, server 10 manages missions and rewards given to member users (guest users, host users). The SNS provided by server 10 is related to missions and rewards. Server 10 includes a communication I / F (interface) 12 and a control unit 20. In FIG. 1, server 10 is shown as being composed of one computer, but the actual server 10 may be composed of multiple computers. When multiple computers are used for server 10, they may be connected to each other via a communication network so that logically one server 10 is configured.

[0028] Communication I / F 12 is an I / F for executing communication with other devices via the Internet 4. The control unit 20 includes a CPU 22 and a memory 24. The CPU 22 executes various processes according to a program 30 stored in the memory 24. The memory 24 is composed of a ROM, a RAM, etc. The memory 24 stores the program 30, a user database 32, and a mission database 34.

[0029] The program 30 includes various programs such as an OS program and an SNS server program. By having the CPU 22 execute the SNS server program, each function of server 10 including mission management and reward management (see FIG. 6) is realized.

[0030] The user database 32 is a database that stores user information of member users. Figure 2 shows an example of the user database 32. As shown in Figure 2, the user database 32 includes a plurality of user information 60a to 60c corresponding to a plurality of member users. In the example of Figure 2, it is shown that the user database 32 includes three pieces of user information 60a to 60c, but actually the user database 32 includes user information according to the number of member users.

[0031] The types of information included in each of the user information 60a to 60c are common. Hereinafter, the user information 60a will be described as an example. Note that the user information 60a shown in Figure 2 is merely an example, and the actual content of the user information may be different from that shown in the figure. The user information 60a includes basic information 62, created mission information 64, participated mission information 66, and point-related information 68.

[0032] The basic information 62 includes basic information about the member user, such as user ID, user name, email address, password, etc. The user ID is identification information assigned to the user at the time of membership registration. The user name, email address, and password are all the member name, contact information, and access password applied by the user at the time of membership registration. Membership registration can be performed by each user accessing the server 10 via a user terminal 40 or the like and inputting necessary items. After the membership registration is completed, the member user can access the server 10 via his / her own user terminal 40 or the like and can view the member's my page and the like. In the example of Figure 2, the basic information 62 includes information such as user ID "UID1", user name "Alfa", email address "abc@xxx.com", and password "xxxx". That is, the user information 60a is information corresponding to the user U1 in Figure 1.

[0033] The created mission information 64 includes information about the missions created by the member user as the host user. If the member user has created and posted missions in the past, the created mission information 64 includes detailed information including the mission IDs. In the example of FIG. 2, the created mission information 64 includes detailed information 64a, 64b of two missions represented by mission IDs "M1" and "M2". That is, it indicates that the member user with user ID "UID1" has created and posted two missions represented by mission IDs "M1" and "M2" as the host user. The detailed information 64a, 64b is linked to mission information 80a, 80b, etc. in the mission database 34 described later.

[0034] The participated mission information 66 includes information about the missions participated in by the member user as a guest user. If the member user has participated in missions in the past, the participated mission information 66 includes detailed information including the mission IDs. In the example of FIG. 2, the participated mission information 66 includes detailed information 66a, 66b of two missions represented by mission IDs "M3" and "M4". That is, it indicates that the member user with user ID "UID1" has participated in two missions represented by mission IDs "M3" and "M4" as a guest user. Information indicating "CLEAR" is associated with the detailed information 66a. It indicates that the member user has completed the mission represented by mission ID "M3". The detailed information 66a, 66b is also linked to mission information 80c, etc. in the mission database 34 described later.

[0035] The point-related information 68 includes point information 68a and history information 68b. The point information 68a indicates the number of points currently held by the member user. Although not shown in detail in the figure, the history information 68b includes information indicating the history of increases and decreases in the number of points of the member user. In this embodiment, points are valuable media that can be used for payments within the SNS, participation in lotteries, etc. In this embodiment, points are awarded as rewards for achieving missions participated in as a guest user and for other users participating in and achieving missions created as a host user.

[0036] The information included in the user information 60a has been described above. The user information 60b is information regarding the member user corresponding to the user ID "UID2" (i.e., user U2 in FIG. 1). The user information 60c is information regarding the member user corresponding to the user ID "UID3".

[0037] The mission database 34 is a database that stores information regarding missions created by host users. FIG. 3 shows an example of the mission database 34. As shown in FIG. 3, the mission database 34 includes a plurality of mission information 80a to 80c corresponding to a plurality of missions. In the example of FIG. 3, it is shown that the mission database 34 includes three pieces of mission information 80a to 80c, but actually, the mission database 34 includes mission information according to the number of missions created so far.

[0038] The types of information included in each piece of mission information 80a to 80c are common. Hereinafter, the mission information 80a will be described as an example. Note that the mission information 80a shown in FIG. 3 is merely an example, and the actual content of the mission information may be different from that shown in the figure. The mission information 80a includes a mission ID 81a, a mission name 81b, host user information 82, basic information 83, a posted image 84, a hashtag 85, a map 86, and task information 88, 90, 92, 94.

[0039] Mission ID 81a indicates the identification information assigned to the created mission. Mission name 81b is the name of the created mission, which is the name of the mission specified by the host user. Host user information 82 indicates the user ID of the host user who created the mission. Host user information 82 may be the user name of the host user who created the mission. Basic information 83 includes basic information about the mission, such as the number of participating users, the number of likes, comments, achievement points, difficulty level, etc. The number of participating users indicates the number of guest users who participated in the mission. The number of likes indicates the number of users who gave a high evaluation to the mission. Comments indicate the number of comments posted for the mission. Although not illustrated in detail, basic information 83 also includes the text of the comments posted. Achievement points indicate the number of reward points that can be obtained when a guest user completes the mission. Difficulty level indicates the difficulty level of mission completion. The difficulty level is represented by the number of star marks. The difficulty level is predetermined by the host user. In the example of FIG. 3, mission information 80a has a mission ID of "M1" and a mission name of "Challenge Cycling". The creator of the mission is the user with user ID "UID1", and 5000 guest users have participated so far. The mission has received 3000 high evaluations, and 200 comments have been posted. The reward for mission completion is 500 points, and the difficulty level is "3".

[0040] Posted image 84 includes images related to the mission posted by guest users who participated in the mission. Hashtag 85 is a tag set so that it can be used for searching the mission, etc. Hashtag 85 is set by the host user. Map 86 is a map showing the movement route, etc. necessary for mission completion. Inside map 86, landmarks and the positions of tasks (checkpoints) to be completed within the mission are also shown. When the mission does not involve movement, map 86 may be omitted.

[0041] Task information 88, 90, 92, and 94 each contain information about tasks to be completed within a mission. In the example of FIG. 3, task information 88 indicates the first task ("Checkpoint 1 XX Temple"). Task information 90 indicates the second task ("Checkpoint 2 XX Tea House"). Task information 92 indicates the third task ("Checkpoint 3 XX Post Office"). Task information 94 indicates the final task ("Goal XXX Hot Spring"). In the example of FIG. 3, mission information 80a includes four pieces of task information 88, 90, 92, and 94, but the number of task information (i.e., the number of tasks) is not limited to four and can be any number as long as it is one or more. In the example of FIG. 3, each task corresponding to task information 88, 90, 92, and 94 involves actual activities (such as movement, visit, purchase, work, etc.) in the real world by guest users participating in the mission. The mission shown in FIG. 3 is, for example, a cycling event that moves from start to goal and is a stamp rally-style event that requires achieving tasks such as visiting multiple checkpoints on the way to the goal.

[0042] The information included in mission information 80a has been described above. Mission information 80b is information about the mission corresponding to mission ID "M2". Mission information 80c is information about the mission corresponding to mission ID "M3". The member user acting as the host user can prepare each piece of information as shown in mission information 80a and create a mission from the member's my page in a predetermined procedure. The host user can post the created mission to server 10 in a predetermined procedure. When the mission is posted, the CPU 22 of server 10 creates mission information 80a, etc. based on the posted content and stores it in mission database 34. After that, the mission indicated by the mission information stored in mission database 34 is publicly available as a mission that guest users can participate in.

[0043] The procedure for guest users to participate in a mission will be described. A member user can access the server 10 via their own user terminal 40 or the like and view their member-only my page. By inputting a predetermined mission viewing operation while viewing the member-only my page, the member user can view a list of missions stored in the mission database 34. The member user can also search for a desired mission by narrowing down the search using a hashtag or the like. While information about the desired mission is being displayed on their user terminal, the member user can input a predetermined participation operation. As a result, the member user can participate in the desired mission as a guest user. Guest users participating in a mission complete tasks according to the conditions specified in the mission and aim to achieve the mission.

[0044] With reference to FIGS. 4 and 5, an example of a screen displayed on the user terminal of a guest user during mission participation will be described. FIGS. 4 and 5 are examples of screens displayed on the user terminal 50 when the user U2 (FIG. 1) participates in a mission represented by the mission ID "M1" as a guest user. FIG. 4 represents the mission screen 100. FIG. 5 represents the task screen 120. However, the screen examples shown in FIGS. 4 and 5 are merely examples, and the actual displayed screen may be different from these.

[0045] User U2 can access server 10 via user terminal 50, select a mission represented by mission ID "M1" from the member's my page, and input a mission participation operation. As a result, user U2 can participate in the mission. When participating in the mission, mission screen 100 shown in FIG. 4 is displayed on user terminal 50. Mission screen 100 is the main screen of the mission in progress. Information indicating the outline of the mission in progress is displayed on mission screen 100. Mission screen 100 is displayed based on mission information 80a. Mission screen 100 includes mission ID 101a, mission name 101b, host user information 102, basic information 103, posted image thumbnail 104, hashtag 105, map 106, and task buttons 108, 110, 112, 114.

[0046] Mission ID 101a, mission name 101b, host user information 102, and basic information 103 are the same as mission ID 81a, mission name 81b, host user information 82, and basic information 83 in FIG. 3.

[0047] Posted image thumbnail 104 is a thumbnail image of a part of posted image 84 in FIG. 3. When a guest user selects a desired thumbnail image, the image corresponding to the selected thumbnail image can be enlarged and displayed. Hashtag 105 is a tag set to be available for searching the mission, etc.

[0048] Map 106 is the same as map 86 in FIG. 3. Map 106 shows the movement route, etc. necessary for mission completion. In map 106, marks and the positions of tasks (checkpoints) to be completed within the mission are also shown. When map is not included in mission information 80a (for example, when the mission does not involve movement, etc.), map 106 is omitted.

[0049] The task buttons 108, 110, 112, and 114 are buttons that are displayed based on the task information 88, 90, 92, and 94 in FIG. 3, respectively. Each of the task buttons 108, 110, 112, and 114 corresponds to a task to be completed within the mission. In the example of FIG. 4, the task button 108 corresponds to the first task ("Checkpoint 1 XX Temple"). The task button 110 corresponds to the second task ("Checkpoint 2 XX Tea House"). The task button 112 corresponds to the third task ("Checkpoint 3 XX Post Office"). The task button 114 corresponds to the final task ("Goal XXX Hot Spring").

[0050] In this embodiment, each of the task buttons 108, 110, and 112 is a button that can be selected when the guest user (user U2) moves to a position where the task can be executed. Until the user U2 arrives at a position where the task can be executed, the user U2 cannot select each of the task buttons 108, 110, and 112. When the user U2 moves to a position where the task can be executed, the task button corresponding to the task is activated, and an operation of selecting the task button of the task can be input. When the task button 108 or the like is selected, a task screen (see FIG. 5 or the like) corresponding to the selected task button is displayed on the user terminal 50. Monitoring whether the guest user moves to a position where each task can be executed can be performed, for example, by monitoring whether the user terminal possessed by the guest user moves to a predetermined position by GPS or the like. The method of monitoring whether the guest user moves to a position where each task can be executed is not limited to this, and any method can be used.

[0051] FIG. 5 shows an example of a task screen 120 displayed on the user terminal 50 when the task button 108 in FIG. 4 is selected. The task screen 120 in FIG. 5 includes a task name 122, a message 124, and a stamp button 126. The task name 122 indicates the name of the task being displayed (in FIG. 5, it is "Checkpoint 1 XX Temple"). The message 124 indicates a message regarding the work to be completed within the task (in FIG. 5, it is "Task 'Let's walk to the main hall!'"). The stamp button 126 is a button that can be selected by a guest user (user U2) when the task achievement conditions are met. For example, when the task is "Let's walk to the main hall", if user U2 who holds the user terminal 50 reaches a predetermined position near the main hall of the temple, the stamp button 126 becomes selectable. Whether the guest user has reached the predetermined position near the main hall can be monitored by, for example, GPS or the like. When the guest user selects the stamp button 126 in a state where the task achievement conditions are met, the task achievement is reported to the server 10. As a result, the stamp button 126 in the task screen 120 is changed to a clear button 128 indicating task completion. After that, when user U2 inputs a predetermined display termination operation, the display of the task screen 120 ends on the user terminal 50, and the mission screen 100 is redisplayed.

[0052] (Reward granting process; FIG. 6) Referring to FIG. 6, the reward granting process executed by the CPU 22 of the server 10 will be described. The reward granting process is a process for granting rewards to a guest user and a host user when predetermined reward granting conditions are met. The CPU 22 continuously executes the reward granting process in FIG. 6 according to the program 30 in the memory 24 while the server 10 is operating.

[0053] In S10, the CPU 22 monitors whether the mission is completed. Guest users participating in the mission can complete (achieve) the mission by completing all tasks. In other examples, guest users may complete (achieve) the mission by completing a predetermined number of tasks (or a predetermined percentage of tasks) among the multiple tasks included in the mission. The mission completion conditions may be arbitrarily determined by the host user who created the mission. When the mission is completed, a mission completion notification indicating mission completion is sent from the guest user's user terminal to the server 10. The mission completion notification includes the guest user's user ID and the mission ID of the completed mission. When the CPU 22 of the server 10 receives the mission completion notification, it determines YES in S10.

[0054] In the subsequent S12, the CPU 22 awards a reward to the guest user. Specifically, the CPU 22 refers to the mission database 34 to identify the mission corresponding to the mission ID included in the mission completion notification (hereinafter sometimes referred to as the "specific mission"). Next, the CPU 22 identifies the reward when the specific mission is completed. In this embodiment, the reward is points. Then the CPU 22 awards the reward to the guest user corresponding to the user ID included in the mission completion notification (hereinafter sometimes referred to as the "specific guest user"). Specifically, the CPU 22 increases the current point count of the user included in the user information 60a, etc. (FIG. 2) corresponding to the user ID included in the mission completion notification by the amount of the reward for the completion of the specific mission.

[0055] In subsequent S14, the CPU 22 awards a reward to the host user who is the creator of a specific mission. Specifically, the CPU 22 refers to the mission database 34 to identify the user ID of the host user who created a specific mission (hereinafter sometimes referred to as the "specific host user"). Then the CPU 22 identifies the reward to be given to the specific host user. For example, the CPU 22 identifies, as the reward to be given to the specific host user, a number of points corresponding to 1% to 10% of the reward given to a specific guest user in S12. In other examples, the number of points to be given to the host user may be predetermined. The CPU 22 increases the current number of points of the user by the identified reward amount in the user information 60a, etc. (Fig. 2) corresponding to the user ID of the host user. After finishing S14, the CPU 22 returns to monitoring S10 again. When a mission is achieved again (YES in S10), the CPU 22 executes the processes of S12 and S14 again.

[0056] The mission management system 2 of this embodiment has been described above. As described above, in this embodiment, when a guest user achieves a mission (YES in S10 of Fig. 6), the CPU 22 can award a reward to the host user who created the mission (S14). For the host user, the awarding of the reward can be a motivation to create an attractive mission. As a result, more attractive missions that many guest users hope to participate in and achieve can be created.

[0057] In this embodiment, when a guest user achieves a mission (YES in S10), the CPU 22 also awards a reward to the guest user (S12). For the guest user, the awarding of the reward can also be a motivation to participate in the mission. It can also be a motivation for the host user to create more attractive missions. A virtuous cycle can occur in which more attractive missions can be created.

[0058] In this embodiment, each task included in the mission includes tasks accompanied by actual activities (such as movement, visit, purchase, work, etc.) of the guest user in the real world. Attractive missions can be provided in cooperation with stores and tourist attractions in the real world, classrooms and lectures such as cultural schools in the real world, etc.

[0059] The correspondence between this embodiment and the claims will be described. The server 10 is an example of an "information processing device". The process of S10 in FIG. 6 is an example of a "monitoring unit". The processes of S12 and S14 are examples of an "awarding unit". The case where it is YES in S10 is an example of a "first case". Each task corresponding to the task buttons 108, 110, 112, 114 in the mission screen 100 of FIG. 4 is an example of a "second task". The reward awarded in S14 is an example of a "first reward". The reward awarded in S12 is an example of a "specific reward".

[0060] (Second Embodiment) Regarding the mission management system 2 of the second embodiment, the differences from the first embodiment will be mainly described. The basic configuration of the mission management system 2 of this embodiment and the operation of the server 10 are common to the first embodiment. In this embodiment, part of the mission configuration and the reward awarding process (FIG. 6) are different from the first embodiment.

[0061] In this embodiment, in addition to rewarding the user when the mission is completed, when a part of the tasks included in the mission is completed, a reward smaller than when the mission is completed is also given to the user (guest user and host user), which is different from the first embodiment. In other words, in this embodiment, when a part of the tasks included in the mission is completed, a small reward is given to the user as so-called "partial points". For example, in this embodiment, when the first task (the task corresponding to the task button 108) in the mission screen 100 of FIG. 4 is completed, 10 points are given to the guest user and 1 point is given to the host user, and the mission is configured in this way. Hereinafter, a part of the tasks that are the conditions for giving a small reward to the user may be referred to as "specific tasks".

[0062] In this embodiment, in the reward granting process (Fig. 6), the CPU 22 simultaneously monitors S10 and S20 (see the dashed arrows in the figure). The monitoring of S10 and the content of each process of S12 and S14 when YES in S10 are the same as those in the first embodiment. In S20, the CPU 22 monitors that a specific task is achieved. A guest user participating in a mission can achieve (complete) a specific task in the process of mission achievement. When a specific task is achieved, a specific task achievement notification indicating the achievement of the specific task is sent from the user terminal of the guest user to the server 10. The specific task achievement notification includes the user ID of the guest user and the mission ID of the mission including the specific task. The specific task achievement notification may further include task information indicating the achieved specific task. When the CPU 22 receives the specific task achievement notification, it determines YES in S20.

[0063] In the subsequent S22, the CPU 22 grants a small reward to the guest user. Specifically, the CPU 22 refers to the mission database 34 to identify the mission (specific mission) corresponding to the mission ID included in the specific task achievement notification. Next, the CPU 22 identifies the small reward when the specific task is achieved. Then the CPU 22 grants a small reward to the guest user (specific guest user) corresponding to the user ID included in the mission achievement notification. Specifically, the CPU 22 increases the current point number of the user included in the user information 60a etc. (Fig. 2) corresponding to the user ID included in the specific task achievement notification by the reward amount (small reward amount) for the achievement of the specific task.

[0064] In subsequent S24, the CPU 22 gives a small reward to the host user who is the creator of a specific mission. Specifically, the CPU 22 refers to the mission database 34 to identify the user ID of the host user (hereinafter sometimes referred to as the "specific host user") who created a specific mission. Then the CPU 22 identifies the small reward to be given to the specific host user. For example, the CPU 22 identifies, as the small reward to be given to the specific host user, a number of points corresponding to 1% to 10% of the small reward given to a specific guest user in S22. In other examples, the number of points to be given as a small reward to the host user may be predetermined. The CPU 22 increases the current number of points of the user by the identified amount of the small reward in the user information 60a etc. (Figure 2) corresponding to the user ID of the host user. After finishing S24, the CPU 22 returns to monitoring S10 and S20 again. When a specific task is achieved again (YES in S20), the CPU 22 executes the processes of S22 and S24 again.

[0065] In this embodiment, even when the guest user does not achieve all the missions and achieves only some of the tasks of the mission (YES in S20), a reward is given to the host user (S24). This can motivate the host user to create large-scale missions. Also, a reward is given to the guest user (S22). This can also motivate the guest user to participate in large-scale missions. The case of YES in S20 is an example of the "second case". The specific task is an example of the "first task". The small reward given in S24 is an example of the "second reward".

[0066] (Third Embodiment) The mission management system 2 of the third embodiment is a modification of the first and second embodiments. In this embodiment, it is different from the first and second embodiments in that an expiration date is set for the mission. In this embodiment, the mission information 80a etc. (Figure 3) includes expiration date information (not shown) indicating the expiration date. The participation of the guest user in the mission and the giving of rewards upon achievement are both limited to within the period until the expiration date of the mission elapses.

[0067] In this embodiment, by providing an expiration date for the mission, it is possible to give guest users a motivation to participate based on the sense of premium that the mission is time-limited. Attractive missions can be provided to guest users.

[0068] As described above, the embodiments have been described in detail, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modification examples may be adopted.

[0069] (Modification Example 1) In each of the above embodiments, each task included in the mission is a task involving the actual activities of the guest user in the real world. This is not limited thereto, and at least one of the plurality of tasks included in the mission may be a task involving the actual activities of the guest user in the real world. Tasks other than those involving actual activities in the real world may be tasks involving activities in a virtual world (for example, the guest user performs a specific action in a game), for example.

[0070] (Modification Example 2) All tasks included in the mission may be tasks involving activities in a virtual world.

[0071] (Modification Example 3) In each of the above embodiments, the reward given to the user (guest user and host user) when the guest user completes the mission is points (S12, S14 in FIG. 6). This is not limited thereto, and the reward may include any valuable item such as, for example, a prize, a bonus, a coupon, points available within the service, a lottery participation right, etc. The reward may include the ability to participate in a specific mission (so-called "opening" of a specific mission). The reward may include points related to the promotion or demotion of the user's rank, status, level, etc. within the service (for example, bronze, silver, gold, platinum, etc.).

[0072] (Modification Example 4) In the above-described Second and Third Embodiments, the small rewards given to the user (guest user and host user) when a specific task is achieved by the guest user are also points (S22, S24 in FIG. 6). Not limited to this, the small rewards may also include any valuable items such as, for example, prizes, bonuses, coupon tickets, points available for use within the service, lottery participation rights, and the like. Also, the small rewards may include the ability to participate in a specific mission. Also, the small rewards may include points related to the promotion or demotion of the user's rank, status, level, etc. (e.g., bronze, silver, gold, platinum, etc.) within the service. The small reward may be a part of the reward given for achieving the mission, or may be a reward different from the reward at the time of mission achievement, and may be a reward of less value than the reward at the time of mission achievement.

[0073] Also, the technical elements described in this specification or the drawings exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Also, the technology illustrated in this specification or the drawings achieves a plurality of purposes simultaneously, and has technical utility by achieving one of those purposes itself.

Description of Reference Numerals

[0074] 2: Mission Management System 4: Internet 10: Server 20: Control Unit 22: CPU 24: Memory 30: Program 32: User Database 34: Mission Database 40, 50: User Terminal 60a~60c: User Information 80a~80c: Mission Information 100: Mission Screen 120: Task Screen

Claims

1. An information processing apparatus, a memory that stores a mission created by a host user and including at least one task, a monitoring unit that monitors whether a guest user achieves the mission, and a giving unit that gives a first reward to the host user when the monitoring unit determines that the mission has been achieved in a first case. Information processing apparatus.

2. The giving unit further gives a specific reward to the guest user in the first case. The information processing apparatus according to claim 1.

3. The mission includes a plurality of the tasks, the monitoring unit further monitors whether the guest user achieves a first task that is a part of the plurality of tasks, and the giving unit gives a second reward smaller than the first reward to the host user when the monitoring unit determines that the first task has been achieved in a second case. The information processing apparatus according to claim 1.

4. An expiration date is set for the mission. The information processing apparatus according to claim 1.

5. At least one of the tasks includes a second task involving actual activities of the guest user in the real world. The information processing apparatus according to claim 1.

Images