Server, computer program and information processing method

Abstract

To provide a server, a computer program, and an information processing method that when a user works on a set goal, can create responsibility and cooperation among a plurality of users who work on the same goal, thereby improving and maintaining motivation to achieve the goal.SOLUTION: A server is provided that includes a goal setting unit, a user information collection unit, and a determination unit. The goal setting unit sets a goal. The goal is achieved by satisfying achievement conditions. The achievement conditions include a plurality of individual conditions that are satisfied by different users. The user information collection unit collects information on a user's predetermined action for satisfying each individual condition from a user terminal. The determination unit determines whether the goal is achieved based on the collected information on the predetermined action.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Patent Document 1 discloses a method for generating a plurality of different missions for a plurality of users based on user information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2015-002975 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when it comes to exercise goals such as walking, it can be difficult to stay motivated to achieve them on your own.

[0005] The present invention provides a server, a computer program, and an information processing method that, when users work toward a set goal, creates a sense of responsibility and cooperation among multiple users working toward the same goal, thereby improving and maintaining motivation to achieve the goal. [Means for solving the problem]

[0006] A server according to one embodiment of the present invention is a server comprising a goal setting unit, a user information collecting unit, and a judgment unit, wherein the goal setting unit sets a goal, the goal is achieved by satisfying achievement conditions, the achievement conditions including a plurality of individual conditions satisfied by different users, the user information collecting unit collects information relating to the user's specified behavior for satisfying the individual conditions from a user terminal, and the judgment unit judges whether the goal has been achieved based on the collected information relating to the specified behavior.

[0007] According to one aspect of the present invention, when a user works towards a set goal, a relationship of responsibility and cooperation can be created among multiple users working towards the same goal, thereby increasing and maintaining motivation to achieve the goal. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing an overview of a goal achievement support system 1 according to each embodiment of the present invention. [Diagram 2] 1 is a block diagram showing a hardware configuration of a server 10 according to a first embodiment. [Diagram 3] 1 is a block diagram showing the hardware configuration of a user terminal 20 according to the first embodiment. [Figure 4] 2 is a block diagram showing a functional configuration of a server 10 according to the first embodiment. FIG. [Diagram 5] 5A to 5E are diagrams showing a flow from goal setting to goal achievement in the first embodiment. [Figure 6] FIG. 1 is a diagram showing a process flow until an individual condition C1 is satisfied in the goal achievement support system 1 according to the first embodiment. [Figure 7] FIG. 11 is a diagram showing a process flow until an individual condition C2 is satisfied in the goal achievement support system 1 according to the first embodiment. [Figure 8] FIG. 11 is a block diagram showing a functional configuration of a server 10 according to a second embodiment. [Figure 9] 9A and 9B are diagrams showing states in which the authority setting unit 11d can and cannot set in the second embodiment, and Fig. 9C is a diagram showing states in which the authority setting unit 11d cannot set in the first modified example of the second embodiment. [Figure 10] 10A to 10C are diagrams showing the flow of authority takeover in the second modification of the second embodiment. [Figure 11] FIG. 13 is a diagram showing a new target and a takeover target in the third modified example of the second embodiment. [Figure 12] 12A and 12B are diagrams showing an example in which two authorities can be set for one user in the third modification of the second embodiment. [Figure 13] 13A and 13B are diagrams showing an example in which two authorities cannot be set for one user in the third modification of the second embodiment. [Figure 14] FIG. 13 is a diagram showing an example in which two authorities are set when one user is assigned to individual conditions included in four goals in the third modification of the second embodiment. [Figure 15] FIG. 13 is a diagram showing a modification in which the number of continuing goals is limited in the fourth modification of the second embodiment. [Figure 16] FIG. 13 is a diagram showing an example in which, in a fifth modified example of the second embodiment, when one user is assigned to individual conditions included in four goals, two authorities are set and one authority is set as active. [Figure 17] FIG. 11 is a diagram illustrating a flow of processing until an individual condition C1 of the goal achievement support system 1 according to the second embodiment is satisfied and a takeover user candidate is designated. [Figure 18] FIG. 11 is a diagram illustrating a process flow until an individual condition C2 of the goal achievement support system 1 according to the second embodiment is satisfied and a takeover user candidate is designated. [Figure 19] Fig. 12A is a diagram showing an example in which a deadline is set for an individual condition in the third embodiment, and Fig. 12B is a diagram showing an example in which the deadline for the individual condition is reset. [Figure 20] FIG. 13 is a block diagram showing a functional configuration of a server 10 according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, several embodiments of the present invention will be described with reference to the drawings. Various features shown in the following embodiments can be combined with each other. Also, each feature can be an invention independently.

[0010] <1. First embodiment> (1-1. Goal Achievement Support System 1) A server 10 according to an embodiment of the present invention is an information processing device constituting a part of a goal achievement support system 1 as shown in Fig. 1. The goal achievement support system 1 includes the server 10 and a plurality of user terminals 20 (20a, 20b, and 20c).

[0011] The server 10 is configured to be able to communicate with each user terminal 20 via a communication line 5. The server 10 can set goals to be achieved by multiple users, collect information on user actions transmitted from each user terminal 20, and manage the progress of the goals and users working to achieve the goals. The server 10 supports users in achieving their goals through such goal setting, progress management, and user management. Each component will be described below.

[0012] (1-2. Hardware configuration of goal achievement support system 1) The hardware configuration of the goal achievement support system 1 will be described with reference to FIGS.

[0013] (1-2-1. Hardware configuration of server 10) 2 is a block diagram showing a hardware configuration of the server 10 according to this embodiment. The server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The server 10 may also include an operation input unit 14 including a keyboard, a mouse, etc., for accepting input of various operations, and a monitor 15 such as a liquid crystal display device for displaying various images.

[0014] The control unit 11 is, for example, a CPU (Central Processing Unit), a microprocessor, a DSP (Digital Signal Processor), or the like, and controls the overall operation of the server 10.

[0015] A part of the storage unit 12 is composed of, for example, a random access memory (RAM) or a dynamic random access memory (DRAM), and is used as a work area or the like when the control unit 11 executes processes based on various programs. In addition, a part of the storage unit 12 is, for example, a non-volatile memory such as a read only memory (ROM) or a hard disk drive (HDD), and stores various data such as information on goals and information on the user's actions, as well as programs used in the processing of the control unit 11.

[0016] The programs stored in the memory unit 12 include, for example, an OS (Operating System) for realizing the basic functions of the server 10, drivers for controlling various hardware, programs for realizing various functions, etc., and include the computer program related to this embodiment.

[0017] The communication unit 13 is, for example, a NIC (Network Interface Controller) and has a function of connecting to the communication line 5. Instead of or together with the NIC, the communication unit 13 may have a function of connecting to a wireless LAN (Local Area Network), a function of connecting to a wireless WAN (Wide Area Network), a function of enabling short-distance wireless communication such as Bluetooth (registered trademark), and infrared communication, etc. The server 10 is connected to other information processing devices such as a user terminal 20 via the communication line 5, and can transmit and receive various data to and from the other information processing devices, etc.

[0018] The control unit 11, storage unit 12, communication unit 13, operation input unit 14, and monitor 15 are electrically connected to one another via a system bus 16. Therefore, the control unit 11 can access the storage unit 12, display images on the monitor 15, grasp the operation state of the operation input unit 14 by the user, and access various communication networks and other information processing devices via the communication unit 13.

[0019] (1-2-2. Hardware Configuration of User Terminal 20) 3 is a block diagram showing a hardware configuration of a user terminal 20 according to this embodiment. The user terminal 20 is, for example, an information processing terminal such as a smartphone or a tablet terminal, and includes a control unit 21, a storage unit 22, and a communication unit 23. The user terminal 20 may also include an inertial sensor 24, a touch panel display 25 capable of displaying images and receiving operations, a speaker 26 that outputs sound, a microphone 27 to which sound is input, a camera 28 that captures an image of a subject, and operation buttons 29. The following description will focus on the differences from the server 10.

[0020] The inertial sensor 24 is a sensor capable of detecting the movement of the user terminal 20 resulting from the user's body movement, etc., and is, for example, an acceleration sensor or a gyro sensor (angular velocity sensor), etc. For example, by detecting the movement of the user terminal 20 using the inertial sensor 24, the movement of the user carrying the user terminal 20, such as walking or running, can be detected, and the control unit 21 can calculate the number of steps.

[0021] The operation buttons 29 are provided on the side of the user terminal 20, and include a power button for starting and stopping the user terminal 20, a volume adjustment button for the sound output by the speaker 26, and the like.

[0022] The control unit 21, the storage unit 22, the communication unit 23, the inertial sensor 24, the touch panel display 25, the speaker 26, the microphone 27, the camera 28, and the operation buttons 29 are electrically connected to one another via a system bus 30. Therefore, the control unit 21 can access the storage unit 22, detect the user's movement by the inertial sensor 24, display an image on the touch panel display 25, grasp the operation state of the touch panel display 25 and the operation buttons 29 by the user, input sound to the microphone 27, output sound from the speaker 26, control the camera 28, and access various communication networks and other information processing devices via the communication unit 23.

[0023] The user terminals 20a, 20b, and 20c are configured similarly as the user terminal 20, but may have the same specifications, such as size and performance, or may be different from each other.

[0024] (1-3. Functional configuration of server 10) As shown in FIG. 4, the control unit 11 of the server 10 includes a goal setting unit 11a, a user information collecting unit 11b, and a determining unit 11c.

[0025] The goal setting unit 11a sets a goal. The user information collecting unit 11b collects information on the user's predetermined behavior for satisfying individual conditions (described in detail later) from the user terminal 20. The determining unit 11c determines whether the goal has been achieved based on the collected information on the predetermined behavior. Details of each function will be described later.

[0026] The above-mentioned functional configuration may be realized by software (including so-called applications) appropriately installed in the server 10, or may be realized by hardware. When realized by software, various functions can be realized by the control unit 11 executing a program constituting the software.

[0027] When the function is realized by executing a program, the program may be stored in the storage unit 12 built into the server 10, or may be stored in a non-transitory recording medium readable by a computer. The function may also be realized by reading out a program stored in an external storage device, so-called cloud computing. When the function is realized by hardware, it may be realized by various circuits such as ASIC, SOC, FPGA, or DRP. The above-mentioned functional configuration may be partially processed by the user terminal 20 using software or hardware.

[0028] (1-4. Functions of the target setting unit 11a) The goal setting unit 11a sets a goal. Specifically, the goal setting unit 11a sets a goal that is to be achieved by a plurality of users sharing and cooperating to satisfy achievement conditions, and stores the goal in the storage unit 12.

[0029] The function of the goal setting unit 11a will be described in detail with reference to Fig. 5. The goal setting unit 11a sets a goal M1 as shown in Fig. 5A. The goal M1 may be set automatically according to a predetermined condition, or may be set by an instruction from an administrator of the server 10 or a user of the user terminal 20.

[0030] Achievement conditions R1 are set for the goal M1. The achievement conditions R1 include a plurality of individual conditions C1 to C3 that are satisfied by different users. The control unit 11 assigns each individual condition to a user. In one embodiment, the control unit 11 may have an assignment unit having a function of assigning individual conditions to users. Although an example in which the achievement conditions include three individual conditions is shown in FIG. 5, it is sufficient that the achievement conditions include a plurality of individual conditions, i.e., two or more individual conditions.

[0031] Each individual condition is a condition that is satisfied when the user performs a predetermined action. The predetermined action is, for example, a real-world action of the user who holds the user terminal 20, an operation on the user terminal 20, etc. More specifically, the real-world action of the user is a specific action such as walking or running while carrying the user terminal 20, or holding the user terminal 20 in the hand and repeatedly moving it in a certain direction, etc. More specifically, the operation on the user terminal 20 is a specific input operation via the touch panel display 25, the operation button 29, etc. in an application running on the user terminal 20, etc.

[0032] When the predetermined behavior is walking or running while carrying the user terminal 20, the walking or running behavior can be quantified, for example, as the number of steps calculated based on the user's behavior detected by the inertial sensor 24 of the user terminal 20, or the moving distance based on the position information by GPS or the like specified by the communication unit 23. That is, the predetermined behavior of the user can be handled as numerical data in this form. The number of steps may be calculated (counted) based on both the detection result by the inertial sensor 24 and the detection result of the movement by specifying the position information. Also, the moving distance may be calculated by adding only the movement at a certain speed or less to the moving distance.

[0033] 5B to 5E show an example in which the individual conditions C1 to C3 are satisfied by different users U1 to U3. As an example, a case will be described in which the goal M1 is set as "walking 3000 steps by three users" and the individual conditions C1 to C3 are set as "satisfied when the users walk 1000 steps."

[0034] 5B shows a state in which the user U1 performs a walking action as a predetermined action to satisfy the individual condition C1, and the action of the user U1 is detected by the user terminal 20a and the number of steps is calculated. The predetermined action may be performed continuously or intermittently. For example, if the user walks 500 steps when going to work in the morning and 500 steps when returning home in the evening, the number of steps may be totaled to 1000 steps.

[0035] As shown in FIG. 5C, user U1 walks 1,000 steps to satisfy individual condition C1, and when individual condition C1 is satisfied (i.e., C1 is cleared), user U2, who is different from user U1, performs walking as a predetermined user behavior to satisfy individual condition C2.

[0036] Next, as shown in FIG. 5D, user U2 walks 1,000 steps to satisfy individual condition C2, and when individual condition C2 is satisfied (i.e., C2 is cleared), user U3, who is different from both user U1 and user U2, performs the action of walking as a specified user behavior to satisfy individual condition C3.

[0037] Similarly, as shown in FIG. 5E, when user U3 walks 1,000 steps to satisfy individual condition C3 (i.e., C3 is cleared), the achievement condition R1 is satisfied as all individual conditions C1 to C3 are satisfied, and therefore goal M1 is achieved.

[0038] The goal setting unit 11a may set the achievement condition R1 to include other conditions other than the individual conditions C1 to C3. When the achievement condition R1 includes other conditions, the achievement condition R1 is satisfied when the other conditions are satisfied in addition to the individual conditions C1 to C3. As the other conditions, various conditions can be set, and examples of the other conditions include a condition related to a time limit from the start of the goal effort to the achievement, a condition related to a deadline to achieve the goal by a specific date, and a condition related to a user attribute that requires the goal to be shared by a user having a specific attribute.

[0039] In the example of FIG. 5 described above, an example was shown in which the individual conditions C1 to C3 are satisfied by mutually different users U1 to U3. Here, "individual conditions are satisfied by mutually different users" does not necessarily mean that the individual conditions are satisfied by only one user. That is, in one aspect, the individual conditions may be satisfied by a user group including one or more users. The user groups may be set so as not to allow each group to include the same user (there is no overlap of users between the user groups), or may be set so as to allow each group to include the same user (that is, it is sufficient that the user groups are not completely identical to each other).

[0040] (1-5. Functions of user information collection unit 11b) The user information collection unit 11b collects information on the user's predetermined behavior for satisfying the individual conditions transmitted from each user terminal 20 via the communication unit 13. Specifically, the information on the predetermined behavior received by the communication unit 13 is stored in the storage unit 12 and compiled. Note that the server 10 may request the user terminal 20 to transmit the information on the predetermined behavior at a predetermined timing, or may wait for the information to be transmitted from the user terminal 20 without making a request.

[0041] In the example of Fig. 5 described above, in the state of Fig. 5B, information on the predetermined behavior of user U1 for satisfying individual condition C1 (the number of steps of user ∪1) transmitted from user terminal 20a of user U1 is received and tallied (for example, the total number of steps is calculated). Similarly, in the state of Fig. 5C, information on the predetermined behavior of user U2 is received from user terminal 20b of user U2, and in the state of Fig. 5D, information on the predetermined behavior of user U2 is received from user terminal 20c of user U3, and these are tallied.

[0042] In the case where an individual condition is satisfied by a user group including one or more users, a configuration may be adopted in which a plurality of users transmit information on a predetermined action from each user terminal 20 and the information is collected by the server 10.

[0043] (1-6. Functions of the Determination Unit 11c) The determination unit 11c determines whether the goal has been achieved based on the collected information on the predetermined behavior. In the example of FIG. 5, the determination unit 11c determines whether the individual conditions C1 to C3 have been satisfied based on the information collected from each of the user terminals 20a to 20c. For example, if the individual condition C1 is set to be "satisfied when the user walks 1000 steps", the determination unit 11c determines whether the total number of steps received and tallied by the user information collection unit 11b has reached 1000 steps. The determination unit 11c also determines whether the achievement condition R1 has been satisfied.

[0044] In this manner, in the server 10, the goal setting unit 11a sets a goal to be achieved by satisfying achievement conditions including a plurality of individual conditions satisfied by different users, the user information collecting unit 11b collects information from the user terminal 20, and the determining unit 11c determines whether the individual conditions and achievement conditions are satisfied, thereby determining whether the goal has been achieved. With such a configuration, the goal will not be achieved unless at least all the individual conditions are satisfied, which creates a responsibility for users who share a goal toward other users who share the goal, thereby improving and maintaining each user's motivation to contribute to the achievement of the goal.

[0045] (1-7. Flow from goal setting to goal achievement using the Goal Achievement Support System 1) 6 and 7, a flow from goal setting to goal achievement by the goal achievement support system 1 in the example of FIG. 5 will be described.

[0046] First, a goal setting step (S110) is executed as shown in Fig. 6. In S110, the goal setting unit 11a of the server 10 sets a goal M1 having an achievement condition R1 including a plurality of individual conditions C1 to C3. The goal M1 is stored in the storage unit 12, but may be transmitted to the user terminal 20a when set and stored separately or instead in the storage unit 22 of the user terminal 20a.

[0047] Next, S210 is executed. In S210, a goal M1 for which an effort to achieve is to be started according to an operation of the user U1 or a predetermined condition is selected on the user terminal 20a, and a request to start the goal is made to the server 10. In S210, a request is also made to the server 10 to assign to the user U1 individual conditions included in the achievement condition R1 of the goal M1.

[0048] Next, S115 is executed. In S115, the individual condition C1 is assigned to the user U1. That is, the control unit 11 of the server 10 sets the user U1 as a user who performs a predetermined action to satisfy the individual condition C1 and transmits information about the predetermined action to the server 10. The user U1 to which the individual condition C1 is assigned can be said to be a user who shares the goal M1. Note that the assignment of the individual condition may be performed automatically by the control unit 11 according to a predetermined condition when a goal start request is received, not according to a request from the user terminal 20a.

[0049] Here, the allocation may be performed sequentially to the users as each individual condition is achieved, as shown in Fig. 5A to Fig. 5D. As another embodiment, at the start of the goal M1, all the individual conditions C1 to C3 may be simultaneously assigned to all the users U1 to U3 according to the designation of the user U1 or a predetermined condition. In the case of simultaneous allocation, the consent of the users U2 and U3 may be required.

[0050] Next, a user information collection step (S120) and S220 are executed. In S220, the user terminal 20a transmits information related to the predetermined behavior of the user U1 for satisfying the individual condition. In S120, the user information collection unit 11b receives the information transmitted from the user terminal 20a. The received information is stored in the memory unit 12 and aggregated. In S120, the user information collection unit 11b may request the user terminal 20a to transmit information related to the predetermined behavior of the user U1, i.e., to execute S220.

[0051] Next, the determination steps (S125 and S130) are executed. In S125, it is determined whether the individual condition C1 is satisfied based on the information collected in S120. If the individual condition C1 is not satisfied, S120 is executed again.

[0052] If the individual condition C1 is satisfied, S130 is executed. In S130, it is determined whether the achievement condition R1 is satisfied. In FIG. 6, since only the individual condition C1 of the individual conditions C1 to C3 is satisfied, it is determined that the achievement condition R1 is not satisfied.

[0053] Next, S135 is executed as shown in Fig. 7. In S135, the control unit 11 makes an approval request to the user terminal 20b to assign the individual condition C2 to the user U2.

[0054] Next, S230 is executed. In response to the approval request from the server 10, the user terminal 20b transmits approval or denial of approval in accordance with an operation of the user U2 or a predetermined condition.

[0055] If approval is sent in S230, then S140 is executed. In S140, similar to S115, individual condition C2 is assigned to user U2.

[0056] Next, S145, S245, S150, and S155 are executed in the same manner as S120, S220, S125, and S130. In Fig. 7, since only the individual conditions C1 and C2 among the individual conditions C1 to C3 are satisfied, it is determined that the achievement condition R1 is not satisfied.

[0057] 7, the same processes as S135 to S155 are executed for the individual condition C3 in relation to the user U3 and the user terminal 20c. Then, in the determination of the achievement conditions, since all of the individual conditions C1 to C3 are satisfied, if there are no other conditions or other conditions are satisfied, it is determined that the achievement condition R1 is satisfied. In other words, it is determined that the goal M1 is achieved.

[0058] <2. Second embodiment> (2-1. Goal achievement support system 1 according to the second embodiment) A goal achievement support system 1 according to a second embodiment of the present invention will be described below. The goal achievement support system 1 in the second embodiment is different from the first embodiment in that it further includes an authority setting unit 11d, as shown in Fig. 8. The following description will focus on the differences.

[0059] In the second embodiment, the authority setting unit 11d manages the authority to execute a goal, thereby making it possible to manage the progress of the goal and the users working to achieve the goal in more detail.

[0060] (2-2. Functional configuration of server 10) As shown in FIG. 8, the control unit 11 of the server 10 includes a goal setting unit 11a, a user information collecting unit 11b, a determining unit 11c, and an authority setting unit 11d.

[0061] (2-3. Functions of the authority setting unit 11d) The authority setting unit 11d sets the authority to execute the goal to the user. The user to whom the authority is set is called an authorized user, and the number of authorities that can be set simultaneously for the same goal is one. The authorized user transmits information on the user's predetermined behavior for satisfying the individual conditions to the server 10, and the information can be collected by the server 10. Other users cannot transmit information on the user's predetermined behavior for satisfying the individual conditions (even if transmitted from the user terminal 20 of another user, it is not collected by the user information collecting unit 11b of the server 10, and does not become basic information for the judgment of the judgment unit 11c). With such a configuration, the authority setting unit 11d sets that only one user can work on the same goal at the same time, and the satisfaction of the individual conditions needs to be progressed by the user to whom the authority is set, and the user is more responsible for other users who share the goal, which improves and maintains the motivation to contribute to the achievement of the goal.

[0062] The function of the authority setting unit 11d will be described in detail with reference to Figs. 9 to 14. In Fig. 9A, authority G1 to execute goal M1 is set for user U3. Information on a predetermined action of user U3 to satisfy individual condition C3 is collected by the server 10. Authority G1 is deleted from user U1. When authority G1 is deleted from user U1, deletion authority DG1 indicating that user U1 had authority G1 may be linked to user U1 and recorded in the storage unit 12.

[0063] The number of authorities that the authority setting unit 11d can set simultaneously for the same target is 1. Since authority G1 has been deleted from users U1 and U2 and authority G1 has been set only for user U3, the state shown in FIG. 9A can be set by the authority setting unit 11d. On the other hand, in FIG. 9B, authority G1 has been set for two users, user U2 and user U3. However, the authority setting unit 11d cannot set such a state.

[0064] In addition, if individual condition 1 is assigned only to user 1, the authority will be deleted or set in principle when the individual condition is met. On the other hand, if individual condition 1 is assigned to multiple users, the authority may be deleted or set in cases other than when the individual condition is met. In other words, the authority for the individual condition may be transferred between users belonging to the user group to which the individual condition is assigned.

[0065] (2-3-1. Modification 1 of the Function of the Authority Setting Unit 11d) The authority setting unit 11d may be configured to set authority to a user who has not yet been set authority for the goal. With such a configuration, it is possible to control so that a plurality of individual conditions are tackled by one different user, and the goal is achieved by the same number of different users as the individual conditions. In other words, it is possible to control so that the individual conditions are repeatedly satisfied by the same user, and the goal is not achieved by users less than the number of individual conditions.

[0066] In this case, the goal setting unit 11a is configured similarly to the first embodiment, but is further configured to set an individual condition to be satisfied by one user. That is, the control unit 11 assigns one user to one individual condition. In other words, the control unit 11 is configured not to assign a user group including two or more users to one individual condition.

[0067] In Fig. 9C, a user U1 who has already been assigned to an individual condition C1 and has been assigned authority G1 once for a target M1 is assigned to an individual condition C3 again and has authority G1 set. However, in this modified example, the authority setting unit 11d cannot set such a state.

[0068] (2-3-2. Modification 2 of the Function of the Authority Setting Unit 11d) The authority setting unit 11d may be configured to delete the authority of the takeover source user who is the authorized user, set the authority to one user (among one or more users other than the takeover source user) among the takeover destination user candidates designated by the takeover source user as candidates for the takeover destination user, and set the user to whom the authority is newly set as the takeover destination user. With such a configuration, the authority is handed over to a user who can take over at the time of handover, so that the user who shares the goal at the time of goal setting is not fixed, but is handed over fluidly, and it is expected that the range of users who share the goal will be expanded. In other words, it is possible for a user who has started working on the goal (user U1 in FIG. 10A) to take over the authority of a subsequent user (user U2 in FIG. 10C) without being limited to a user who can take over.

[0069] In Fig. 10A, authority G1 to execute goal M1 is set for user U1. Information on a predetermined action of user U1 to satisfy individual condition C1 is collected by server 10. Then, when determination unit 11c determines that individual condition C1 is satisfied, authority setting unit 11d deletes authority G1 from user U1 as shown in Fig. 10B.

[0070] The user U1 from whom the authority G1 has been deleted is the next user to be assigned to the individual condition C2, and one or more users to whom the authority G1 is to be set can be designated from among the candidate succession users. Here, the user U1 from whom the authority G1 has been deleted and who is to transfer the authority to the next user is called the succession source user, and the one or more users designated by the user U1 are called the candidate succession users.

[0071] In one aspect, when a takeover target user candidate is designated, a list of users who can be designated may be displayed on the touch panel display 25 of the user terminal 20a of the user U1 (the takeover source user). The users displayed in the list as users who can be designated are selected based on, for example, information about friendships with the user U1 (hereinafter, also referred to as "friend information").

[0072] The friend information is an index of interactions within and outside the service that provides the goal achievement support system 1. In other words, the displayed users may be prioritized according to the degree of interaction (or the depth of friendship, intimacy, etc.) between the user U1 and the user. An example of an interaction within the service is when two users exchange accounts or IDs for the service and are connected so that they can contact each other. An example of an interaction outside the service is when two users have some kind of contact (so-called "like," "follow," "add friend," etc.) on a social networking service (SNS) such as a chat app.

[0073] One reason why a user may be given a higher priority as a displayed user may be that they have shared goals with other goals than goal M1, or that they have met or are likely to meet many individual conditions for goals other than goal M1.

[0074] In Fig. 10B, users U2 to U4 are designated as candidates for the takeover user. When individual condition C2 is assigned to user U2 from among them and authority G1 is set, user U2 becomes an authorized user in M1 as shown in Fig. 10C. Authorized user U2 who has taken over authority G1 is also called a takeover user.

[0075] Furthermore, when the takeover source user designates multiple users as candidates for the takeover target user, the authority setting unit 11d may be configured to set authority to the takeover target user candidate who is first approved to become the takeover target user, and to cancel the designation as takeover target user candidates of users other than the approved user. In one aspect, approval of the takeover target user candidate is transmitted from the user terminal 20 to the server 10 according to a user operation or a predetermined condition. When the server 10 receives the approval, individual conditions are assigned and authority is set.

[0076] With this configuration, when a user is taken over by one of the takeover destination user candidates, it is possible to prevent the other takeover destination user candidates from remaining designated even though they are in a situation where they cannot become the takeover destination user of the target. In other words, it is possible to prevent multiple takeover destination user candidates from being approved in duplicate.

[0077] In FIG. 10B, if user U2 approves first, the designation of users U3 and U4 as candidates for users to whom authority G1 is to be taken over is cancelled.

[0078] In one embodiment, when the user U2 (a candidate for a takeover user) gives approval, a list of specifications for each approvable goal may be displayed on the touch panel display 25 of the user terminal 20b of the user U2. The user U2 selects a specification from the list and performs an operation to approve it.

[0079] If user U2 approves first, the designation of user U3 as a takeover user candidate is cancelled, but the list of approvable designations displayed on the touch panel display 25 of the user terminal 20c of user U3 no longer includes the cancelled designation. Even if the cancelled designation is selected and approved, it will be rejected by the server 10.

[0080] (2-3-3. Modification 3 of the Function of the Authority Setting Unit 11d) The authority setting unit 11d may be configured to be able to set one authority each for new goals and handover goals for one user.

[0081] The goal set by the goal setting unit 11a becomes a new goal or a takeover goal depending on the progress of the goal. A new goal is a goal in which the set authorized user becomes the first authorized user of the goal. A takeover goal is a goal in which the set authorized user becomes the second or subsequent authorized user of the goal.

[0082] That is, when an individual condition included in the achievement condition set for a goal has not yet been satisfied and the authority is set for the first time for the goal to the user assigned to the individual condition, the goal becomes a new goal. In FIG. 11, the goal M1 is a new goal because the authority G1 is set for the user U1 for the first time. The goal M4 is also a new goal.

[0083] On the other hand, when authority is set for the assigned user, one or more individual conditions included in the achievement conditions set for the goal have already been satisfied, and it is not the first time that authority has been set for the goal (second or subsequent time), the goal becomes a handover goal. In Fig. 11, goal M2 is a handover goal because the setting of authority G2 for user U1 is the second time following the setting for user UA. Goal M3, which is the third setting, is also a handover goal.

[0084] 12 to 14 are diagrams for explaining whether or not authority can be set for user U1 in relation to some combinations of the goals in FIG.

[0085] In FIG. 12A, two authorities G1 and G2 are set simultaneously for user U1. Authority G1 is authority for goal M1, which is a new goal. Meanwhile, authority G2 is authority for individual condition C2-2 set in the middle of goal M2, which is a taking-over goal. In this way, the authority setting unit 11d can set one authority each for new goals and taking-over goals. Also, in FIG. 12B, authority G1 is the same as in the case of FIG. 12A. Meanwhile, authority G3 is authority for individual condition C3-3 set at the end of goal M3, which is a taking-over goal. The authority setting unit 11d can set one authority each for such a combination of new goals and taking-over goals.

[0086] On the other hand, in FIG. 13A, two authorities G2 and G3 are set for user U1 at the same time. Authority G2 is the authority for goal M2, which is the takeover goal. Authority G3 is also the authority for goal M3, which is the takeover goal. Therefore, since the authority setting unit 11d can set one authority each for a new goal and a takeover goal for one user, it is not possible to set more than one authority for the takeover goal in this way. Also, in FIG. 13B, authority G1 and authority G4 are the authorities for new goal M1 and new goal M4, respectively, so similarly, the authority setting unit 11d cannot set more than one authority for the new goal in this way.

[0087] In Fig. 14, the authority for the goal M2 and the goal M4 are respectively taken over by different users. Therefore, even if the user U1 is assigned to the individual conditions included in the four goals M1 to M4, the authority setting unit 11d can set one authority for each of the new goal and the taken-over goal. By limiting the number of authorities that can be set for the same user in this way, it is possible to avoid uneven distribution of goals among users and to distribute them.

[0088] (2-3-4. Modification 4 of the Function of the Authority Setting Unit 11d) In addition, the authority setting unit 11d may be configured so that, when authority is set for a user in a first new goal, authority can be set for the user in a second new goal after the first new goal is achieved, and, when authority is set for a user in a first handover goal, authority can be set for the user in a second handover goal after the first handover goal is achieved.

[0089] In the example of Fig. 14, goals M1 to M4 are unachieved goals and are ongoing efforts to achieve them (ongoing goals). User U1 has been set with authority G1 for goal M1 and authority G3 for goal M3. User U1 has also been set with authority G2 for goal 2 and authority G4 for goal M4 (deletion authority DG2, deletion authority DG4).

[0090] That is, in the above-mentioned modified example 3, after authority is set for a user in a first new goal or a takeover goal, authority can be set for the user in a second new goal or a takeover goal before the first new goal or the takeover goal is achieved. Even if an effort is ongoing to achieve the new goal or the takeover goal for which authority has been set, authority can also be set for other new goals or takeover goals.

[0091] On the other hand, in this modified example, the number of authorities and deletion authorities corresponding to the user in the continuing goal is limited. Below, an example that can be set in this modified example will be described with reference to Fig. 15. In Fig. 15, the goals M1 and M2 are continuing goals because they have not been achieved, and the goals M3 and M4 are not continuing goals because they have been achieved.

[0092] The user U1 has been set with authority in the goal M1, and has been set with authority in the goal M4, but the goal M1 is a continuing goal, while the goal M4 is not a continuing goal. That is, the continuing goal for which the authority is set or the authority was set for the user U1 is one of the new goals, the goal M1. Note that the goal M4 is handed over from the user U1 to the user UE, and is a handover goal for the user UE, but for the user U1 for whom the authority was set as a new goal, it can be considered as a new goal even after the handover. In addition, the user U1 has been set with authority in two handover goals, the goal M2 and the goal M3, but the goal M2 is a continuing goal, while the goal M3 is not a continuing goal. That is, the continuing goal for which the authority is set or the authority was set for the user U1 is one of the handover goals.

[0093] Therefore, the authority setting unit 11d can set the state exemplified in Fig. 15. However, in this modified example, the authority setting unit 11d cannot set the state exemplified in Fig. 14. As new goals, since both goals M1 and M4 are considered as continuing goals, even if the authority G4 is inherited in the goal M4, the authority setting unit 11d cannot set the authority G1 to the user U1 in the goal M1. As inherited goals, since both goals M2 and M3 are considered as continuing goals, even if the authority G2 is inherited in the goal M2, the authority setting unit 11d cannot set the authority G3 to the user U1 in the goal M3.

[0094] In this way, by configuring the authority setting unit 11d to limit the number of authorities and deletion authorities corresponding to users in the continuing goal, it is possible to prevent the goals from being biased among users and to distribute them. In addition, it is possible to prevent a user from having many goals at the same time and neglecting efforts on some goals.

[0095] (2-3-5. Fifth modified example of the function of the authority setting unit 11d) Furthermore, when multiple authorities are set for one user, the authority setting unit 11d may be configured to set (activate) any one of the multiple authorities as active. In this case, the user information collecting unit 11b is configured to collect information on a predetermined action for a goal related to the active authority. With such a configuration, it is possible to restrict the simultaneous progress of the satisfaction of individual conditions for multiple goals by one action of the user. Note that, even when only one authority is set for one user, the authority setting unit 11d may be configured to set the authority as active and to cancel (deactivate) the active setting.

[0096] For example, as in the example of Fig. 14 above, when one authority each for a new goal and a takeover goal is set for one user, the authority setting unit 11d can activate only the authority set for either the new goal or the takeover goal. In Fig. 16, two authorities, authority G1 and authority G3, are set for user U1, but only authority G3 for goal M3 is set as active, becoming active authority AG3.

[0097] (2-4. Flow from goal setting to goal achievement by the goal achievement support system 1 according to the second embodiment) With reference to FIGS. 17 and 18, a flow from goal setting to goal achievement by the goal achievement support system 1 according to the second embodiment will be described for the goal M1 in FIG.

[0098] 17, an authority setting step (S160) is executed after S115. In S160, the authority setting unit 11d sets authority G1 to the user U1. That is, the user U1 is set as a user who transmits information on a predetermined action for satisfying the individual condition C1-1 to the server 10 and whose information is collected by the server 10.

[0099] Next, in one aspect, S290 and S190 are executed. In S190, one of the authorities G1 set for the user U1 is activated. The activation is performed according to an operation of the user U1 or a predetermined condition. For example, according to an operation of the user U1, the user terminal 20a transmits a request to activate the authority G1. Then, the server 10 that receives the request activates the authority G1 set for the user U1 by the authority setting unit 11d.

[0100] When S190 is executed, in S120 and S220, the user terminal 20a transmits information on a predetermined action of the user U1 for satisfying the individual condition C1-1 related to the activated authority G1.

[0101] Next, the determination steps (S125 and S130) are executed. In S125, it is determined whether the individual condition C1 is satisfied based on the information collected in S120. If the individual condition C1 is not satisfied, S120 is executed again.

[0102] If it is determined in S125 that the individual condition C1-1 is satisfied, an authority deletion step (S165) is executed. In S165, the authority setting unit 11d deletes the authority G1 set for the user U1. If the authority G1 has been activated, the authority setting unit 11d deactivates the authority G1.

[0103] Next, in one aspect, S250 is executed. In S250, takeover target user candidates U2 to U4 are designated in accordance with an operation of user U1 or a predetermined condition (see FIG. 10B), and the designated content is transmitted from user terminal 20a to server 10. The designation may be performed by a request from server 10 to user terminal 20a, but when it is determined that an individual condition is satisfied, the designated content may be transmitted from user terminal 20a to server 10 without a request from server 10.

[0104] Next, as shown in Fig. 18, S136 is executed instead of S135 in Fig. 7. In S136, the authority setting unit 11d requests approval for authority takeover to set authority G1 for each of the user terminals 20 of the takeover destination user candidates U2 to U4.

[0105] Next, S231 is executed instead of S230. In S231, the user terminal 20b transmits to the server 10 approval for authority takeover for setting the authority G1 to the user U2.

[0106] Next, S140 and S170 are executed. In S140, the individual condition C1-2 is assigned to the user U2 who is the first among the takeover destination user candidates U2 to U4 to approve the takeover, and at the same time, the authority G1 is set to the user U2. Meanwhile, S180 is executed, and the designation for the other takeover destination user candidates U3 to U4 is cancelled.

[0107] Next, S195 and S295 are executed in the same manner as S190 and S290. <3. Third embodiment> (3-1. Goal Achievement Support System 1 According to the Third Embodiment) The goal achievement support system 1 according to the third embodiment of the present invention will be described below. The goal achievement support system 1 in the third embodiment is different from the first embodiment in that the goal setting unit 11a sets a deadline for which an individual condition should be satisfied for the goal, as shown in Fig. 19. The following description will focus on the difference.

[0108] In the third embodiment, the goal setting unit 11a sets a deadline within which an individual condition should be satisfied, thereby encouraging the user to take a predetermined action to satisfy the individual condition.

[0109] (3-2. Functions of the target setting unit 11a) The goal setting unit 11a is configured to set a deadline for the goal by which the individual conditions should be satisfied. If the individual conditions are not satisfied within the deadline, the individual conditions cannot be satisfied after the deadline has passed, the achievement conditions are not satisfied, and the effort toward the goal ends in failure. With this configuration, it is expected that the user will actively take a predetermined action to satisfy the individual conditions within the set deadline, and it is possible to prevent the effort toward the achievement of the goal from stagnating.

[0110] 19A, the goal setting unit 11a sets deadlines T1 to T3 for the individual conditions C1 to C3 of the goal M1, respectively. A user U1 to which the individual condition C1 is assigned is required to satisfy the individual condition C1 by the deadline T1.

[0111] Here, the deadline T1 may be set as a certain length of time after the user U1 is assigned. For example, if the deadline T1 is set to two days, the user U1 who is assigned the individual condition C1 at 18:00 PM on February 1, 2020 must satisfy the individual condition C1 by 18:00 PM on February 3, 2020. The deadline T1 may also be set as a specific date and time (for example, 00:00 AM on July 24, 2020) regardless of when the user U1 is assigned.

[0112] The goal setting unit 11a may be configured to extend the deadline by an extension procedure. By configuring in this way, it is possible to prevent the achievement of the goal from stagnating by setting a deadline, while preventing the user's motivation from decreasing due to failure to achieve the goal.

[0113] For example, as shown in FIG. 19B, the goal setting unit 11a extends the deadline T1 set in the individual condition C1 for the extension procedure performed by the user U1 via the user terminal 20a, and resets it to a deadline T1'.

[0114] The extension procedure may be, for example, a specific operation of the user, a specific action of the user, or the payment of a consideration. The consideration may be, for example, a value (value exchange medium) owned by the user such as points that can be used in the service, or five elements in the service system such as items for extension. The payment of the consideration may be made by consuming or using these.

[0115] In addition, a limit may be set on the number of extension procedures that can be performed for one individual condition (for example, limiting it to one time). By setting such a limit, it is possible to strike a balance between preventing stagnation in goal achievement and preventing a decrease in motivation.

[0116] The goal setting unit 11a may be configured to reset the extended deadline by performing an extension procedure before the deadline has elapsed. The goal setting unit 11a may be configured to reset the extended deadline by performing an extension procedure after the deadline has elapsed. If the extension procedure is performed by paying a fee, the extension procedure after the deadline may be set to require a larger fee than the fee required for the procedure before the deadline has elapsed.

[0117] <4. Fourth embodiment> (4-1. Goal achievement support system 1 according to the fourth embodiment) A goal achievement support system 1 according to a fourth embodiment of the present invention will be described below. The goal achievement support system 1 in the fourth embodiment is different from the first embodiment and the like in that it further includes a privilege granting unit 11e, as shown in Fig. 20. The following description will focus on the differences.

[0118] In the fourth embodiment, the reward granting unit 11e grants a reward set for a goal to a user who contributes to achieving the goal, thereby increasing the motivation of the user to take a specified action to satisfy individual conditions and contribute to achieving the goal.

[0119] (4-2. Functional configuration of server 10) As shown in FIG. 20, the control unit 11 of the server 10 includes a goal setting unit 11a, a user information collecting unit 11b, a determining unit 11c, an authority setting unit 11d, and a privilege granting unit 11e.

[0120] (4-3. Functions of the target setting unit 11a) The goal setting unit 11a is configured to set a reward for the goal. The reward to be set is, for example, a reward that is given to each user who satisfies an individual condition included in the achievement condition when the achievement condition is met and the goal is achieved. In addition, the reward to be set may be a reward that is given to a user who satisfies an individual condition when the individual condition is met.

[0121] The rewards given to each user may be different. In addition, the rewards given to each user may be set to vary depending on the attributes of the user, the role played by the user in achieving the goal, and other conditions.

[0122] The granted benefit may be, for example, a value such as points that can be used inside or outside the service that provides the goal achievement support system 1, or game elements such as items or in-game currency that can be used in related games inside or outside the service.

[0123] (4-4. Functions of the Benefit Granting Unit 11e) The reward granting unit 11e is configured to grant a reward to each user who satisfies an individual condition included in the achievement condition when the determining unit 11c determines that the goal has been achieved. By configuring in this way, a reward is granted to a user who has contributed to the achievement of the goal, and motivation for contribution can be improved.

[0124] The reward giving unit 11e may be configured to give a reward to a user who has satisfied an individual condition when the individual condition is satisfied. By configuring in this way, even if the entire goal is not achieved, a reward is given to a user who has satisfied an individual condition and contributed to the achievement of the goal, and the motivation for contribution can be further improved.

[0125] The reward granting unit 11e may be configured to grant more rewards to a user who was an authorized user of a new goal than to a user who was an authorized user of a handover goal when the reward is granted. By configuring in this way, it is possible to improve the motivation of a user who is working on a new goal (a user who starts working on achieving a goal).

[0126] <5. Other embodiments> Although the embodiment and its modified examples of the present invention have been described above, application of the present disclosure is not limited to the above-mentioned contents.

[0127] In addition, in the above embodiment, the aspects in which each function is mainly provided by the server 10 have been described, but if permitted by the nature of the functions, some functions may be provided by the user terminal 20, or by both the server 10 and the user terminal 20.

[0128] In the above embodiment, the example of designating specific users U2 to U4 in Fig. 10B has been described, but in one aspect, the designation of the takeover destination user candidates does not need to be selected individually, and all users that can be designated at the time of designation may be configured to be designated at once. Also, the number of times that the designation at once can be performed within a certain period of time may be limited.

[0129] In the above embodiment, the takeover user candidates designated in Fig. 10B are configured to display a list of designations for each approvable goal on a screen displayed in an application related to the goal achievement support system 1. Such designation of takeover user candidates can be performed for potential users who have not yet used the goal achievement support system 1.

[0130] For example, the takeover source user (or the goal achievement support system 1) may notify the potential user who has not yet used the goal achievement support system 1 of the designation by a chat app, email, or the like. When the potential user is designated on a screen displayed in an application or the like, a configuration may be adopted in which users extracted from contacts held in a service other than the goal achievement support system 1 are displayed on the screen as takeover target user candidates. Note that a guide for using the service of the goal achievement support system 1 may be simultaneously transmitted to the potential user.

[0131] In addition, the control unit 11 may be configured so that, when an individual condition in a first new goal is assigned to a user, the control unit 11 can assign an individual condition in a second new goal to the user after the first new goal is achieved, and, when an individual condition in a first handover goal is assigned to a user, the control unit 11 can assign an individual condition in a second handover goal to the user after the first handover goal is achieved.

[0132] Furthermore, the server 10 (or the user terminal 20) may have a function (cheer notification unit) that allows a certain user to indicate to other users who have not yet satisfied the assigned individual conditions that the certain user is cheering on the other user. That is, when another user B transmits to the server 10 via the user terminal 20 that he is cheering on user A who is taking a predetermined action to satisfy the assigned individual condition, the server 10 records this in the storage unit 12. Then, when the cheering is recorded, the user terminal of user A receives information about the record from the server 10, and the fact that user B is cheering on user A is displayed on the user terminal of user A.

[0133] In the above embodiment, the goal setting unit 11a sets a deadline for which individual conditions should be satisfied for the goal, but the goal setting unit 11a may be configured to be able to set other deadlines as well. For example, the goal setting unit 11a may set a period in which all of the achievement conditions should be satisfied. In addition, the goal setting unit 11a may set a deadline from the designation of the takeover destination user candidate to the approval of the designation.

[0134] In the above embodiment, the user terminal 20 has been described as an information processing terminal such as a smartphone or tablet terminal equipped with the inertial sensor 24, but is not limited to this example. A configuration may be adopted in which a detection device equipped with the inertial sensor 24 detects a user's movement, the detection device and various information processing devices share the detected information wirelessly or via wires, and information related to a predetermined action is transmitted from the various information processing devices.

[0135] <6. Features of the embodiment> The features of the embodiments of the present invention are summarized below.

[0136] A server 10 according to an embodiment of the present invention includes a goal setting unit 11a, a user information collecting unit 11b, and a judgment unit 11c, in which the goal setting unit 11a sets a goal, the goal is achieved by satisfying achievement conditions, the achievement conditions include a plurality of individual conditions that are satisfied by different users, the user information collecting unit 11b collects information on the user's predetermined actions for satisfying the individual conditions from the user terminal, and the judgment unit 11c judges the achievement of the goal based on the collected information on the predetermined actions. With this configuration, the goal is not achieved unless at least all the individual conditions are satisfied, and responsibility arises for other users who share the goal, thereby improving and maintaining motivation to contribute to the achievement of the goal.

[0137] The server 10 further includes an authority setting unit 11d, which sets authority for a user, the user to whom the authority is set is regarded as an authorized user, and the number of authorities that can be set simultaneously for the same goal is 1. With such a configuration, the authority setting unit sets only one user to be able to work on the same goal at the same time, and an individual condition needs to be satisfied by one user, which creates more responsibility for other users who share the goal, and improves and maintains motivation to contribute to achieving the goal.

[0138] The authority setting unit 11d sets the authority to a user who has not yet been set with authority for the goal. With this configuration, it is possible to control so that a plurality of individual conditions are tackled by one different user, and the goal is achieved by the same number of different users as the individual conditions. In other words, it is possible to control so that the same user does not repeatedly satisfy the individual conditions and achieve the goal.

[0139] The authority setting unit 11d deletes the authority of the takeover source user who is the authorized user, sets the authority to one of one or more users other than the takeover source user designated by the takeover source user as a candidate for the takeover destination user, and sets the user to whom the authority is newly set as the takeover destination user. With such a configuration, the user is taken over to a user who can take over at the time of taking over, so that the participants are not fixed at the time of goal setting, but are taken over fluidly, and it is expected that the range of users who share the goal will be expanded. The range is not limited to users who can take over the goal directly by the user who created the goal.

[0140] When the takeover source user designates multiple users as candidates for the takeover destination user, the authority setting unit 11d sets the authority to the takeover destination user candidate who is first approved to become the takeover destination user, and cancels the designation as a takeover destination user candidate for the multiple designated users other than the approved user. With this configuration, when the takeover destination user candidate is taken over by one user, it is possible to avoid a situation where the other takeover destination user candidates remain designated even though they cannot become the target takeover destination user. In other words, it is possible to prevent multiple takeover destination user candidates from being approved in duplicate.

[0141] The goal is a new goal or a takeover goal, a new goal is a goal in which the set authorized user becomes the first authorized user in the goal, a takeover goal is a goal in which the set authorized user becomes the second or subsequent authorized user in the goal, and the authority setting unit 11d can set one authority in the new goal and one authority in the takeover goal for one user. By configuring in this way, it is possible to avoid uneven distribution of goals among users and to distribute them.

[0142] When multiple authorities are set for one user, the authority setting unit 11d sets one of the multiple authorities as active, and the user information collecting unit 11b collects information on a predetermined action related to the active authority. With this configuration, it is possible to limit the progress of satisfaction of individual conditions for multiple goals by a single action of the user.

[0143] The goal setting unit 11a sets a deadline for the goal by which the individual conditions should be satisfied. With this configuration, it is possible to prevent the achievement of the goal from stagnating due to the setting of a deadline.

[0144] The goal setting unit 11a extends the deadline by an extension procedure. By adopting such a configuration, it is possible to prevent the achievement of the goal from stagnating by setting a deadline, while also preventing a decrease in motivation due to failure to achieve the goal.

[0145] The server 10 further includes a reward granting unit 11e, in which the goal setting unit 11a sets a reward for the goal, and when the determination unit 11c determines that the goal has been achieved, the reward granting unit 11e grants a reward to each user who satisfies an individual condition included in the achievement condition. With this configuration, rewards are granted to users who have contributed to the achievement of the goal, thereby improving motivation for contribution.

[0146] When the individual conditions are satisfied, the reward granting unit 11e grants a reward to the user who has satisfied the individual conditions. With this configuration, even if the entire goal is not achieved, a reward is granted to the user who has satisfied the individual conditions and contributed to the achievement of the goal, thereby further increasing the motivation for contribution.

[0147] The server 10 further includes a reward granting unit, and the goal setting unit 11a sets a reward for the goal, and the reward granting unit grants a larger reward to the user who was the authorized user of the new goal than to the user who was the authorized user of the takeover goal when the reward is granted. This configuration improves the motivation of the user to work on the goal as a new goal (user who starts working on achieving the goal).

[0148] A computer program according to one embodiment of the present invention causes a computer (such as a server 10) to execute a goal setting step S110, a user information collecting step S120, and a judgment step S130, in which a goal is set and the goal is achieved by satisfying achievement conditions, the achievement conditions including a plurality of individual conditions that are satisfied by different users, in which the user information collecting step S120 collects information from a user terminal regarding a specific behavior of the user for satisfying the individual conditions, and in which the judgment step S130 judges whether the goal has been achieved based on the collected information regarding the specific behavior.

[0149] An information processing method according to one embodiment of the present invention includes a goal setting step S110, a user information collecting step S120, and a judgment step S130. In the goal setting step S110, a goal is set and the goal is achieved by satisfying achievement conditions, the achievement conditions including a plurality of individual conditions that are satisfied by different users. In the user information collecting step S120, information relating to a specific behavior of the user for satisfying the individual conditions is collected from the user terminal. In the judgment step S130, it is judged whether the goal has been achieved based on the collected information relating to the specific behavior. [Explanation of symbols]

[0150] 1: goal achievement support system, 5: communication line, 10: server, 11: control unit, 11a: goal setting unit, 11b: user information collection unit, 11c: judgment unit, 11d: authority setting unit, 11d: authority setting, 11d: authority setting unit, 11e: privilege granting unit, 12: memory unit, 13: communication unit, 14: operation input unit, 15: monitor, 16: system bus, 20 (20a, 20b, 20c): user terminal, 21: control unit, 22: memory unit ,23: Communication unit, 24: Inertial sensor, 25: Touch panel display, 26: Speaker, 27: Microphone, 28: Camera, 29: Operation button, 30: System bus, AG3: Authority, C1 to C3, C1-1 to C1-3, C2-1 to C2-4, C3-1 to C3-3, C4-1 to C4-2: Individual conditions, AG3: Active authority, DG1: Deletion authority, M1 to M4: (New / takeover) goal, R1: Achievement condition, T1 (T1'), T2, T3: deadline, U1: user (original user), U2: (authority) user (successor user (candidate)), U3: User (successor user candidate), U4: User (successor user candidate)

Claims

1. a processor, the processor comprising: Setting a goal that is to be achieved by different users fulfilling a plurality of individual conditions; assigning a first individual condition to a first user among the plurality of users who has set the goal; Allocating other unfulfilled individual conditions to other users, designated by the user who has fulfilled the individual conditions and who have not been allocated the individual conditions; collecting information on the actions of users to whom individual conditions have been assigned from user terminals of the users to whom the individual conditions have been assigned, and determining, based on the information, whether or not the individual conditions of the users to whom the individual conditions have been assigned have been achieved; determining whether or not the goal by the multiple users has been achieved based on the achievement status of the individual conditions of each user to which the individual conditions have been assigned; Information processing device.

2. The processor, When the first user achieves the first individual condition, other users who have not been assigned the individual condition and who are selected based on a priority level set based on a degree of interaction with the first user are displayed on a user terminal of the first user. The information processing device according to claim 1 .

3. A processor sets a goal to be achieved by different users fulfilling a plurality of individual conditions; A processor assigns a first individual condition to a first user among the plurality of users who sets the goal; A processor assigns other unfulfilled individual conditions to other users who have not been assigned the individual conditions and who are designated by the user who has fulfilled the individual conditions; A processor collects information on the actions of users to which individual conditions are assigned from user terminals of the users to which the individual conditions are assigned, and determines, based on the information, whether or not the individual conditions of the users to which the individual conditions are assigned have been achieved; The processor determines whether or not the goal by the multiple users has been achieved based on the achievement status of the individual conditions of each user to which the individual conditions have been assigned. Information processing methods.

4. A method for determining a goal to be achieved by a plurality of individual conditions being achieved by different users, comprising: causing a processor to assign a first individual condition to a first user among the plurality of users who sets the goal; causing a processor to assign other unfulfilled individual conditions to other users who have not been assigned the individual conditions and who are designated by the user who has fulfilled the individual conditions; causing a processor to collect information on the actions of users to which individual conditions are assigned from a user terminal of each user to which the individual conditions are assigned, and to determine, based on the information, whether or not the individual conditions of the users to which the individual conditions are assigned have been achieved; causing the processor to determine whether or not a goal by multiple users has been achieved based on the achievement status of the individual conditions of each user to which the individual conditions have been assigned; program.

5. A server and a terminal device are provided, The server, Setting a goal that is to be achieved by different users fulfilling a plurality of individual conditions; assigning a first individual condition to a first user among the plurality of users who has set the goal; Allocating other unfulfilled individual conditions to other users, designated by the user who has fulfilled the individual conditions and who have not been allocated the individual conditions; collecting information on the actions of users to whom individual conditions have been assigned from user terminals of the users to whom the individual conditions have been assigned, and determining, based on the information, whether or not the individual conditions of the users to whom the individual conditions have been assigned have been achieved; determining whether or not the goal by the multiple users has been achieved based on the achievement status of the individual conditions of each user to which the individual conditions have been assigned; system.

Images