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 Art]

[0002] Patent Document 1 discloses a method for generating a plurality of mutually different missions for each of a plurality of users based on user information. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2015-002975 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] However, it may be difficult for a person to maintain the motivation to achieve goals related to exercise such as walking on their own.

[0005] The present invention provides a server, a computer program, and an information processing method that, when users work toward set goals, can generate a sense of responsibility and cooperative relationships among a plurality of users working toward the same goal, and improve and maintain motivation for achieving the goal. [Means for Solving the Problem]

[0006] A server according to one aspect of the present invention comprises a goal setting unit, a user information collecting unit, and a determination unit. The goal setting unit sets a goal, the goal is achieved by satisfying an achievement condition, the achievement condition includes a plurality of individual conditions that are to be satisfied by mutually different users, the user information collecting unit collects, from a user terminal, information related to a predetermined action of a user for satisfying the individual condition, and the determination unit determines whether the goal is achieved based on the collected information related to the predetermined action.

[0007] According to one aspect of the present invention, when users work towards a set goal, a relationship of responsibility and cooperation can be created among multiple users working towards the same goal, thereby improving and maintaining their motivation to achieve the goal. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an overview of the goal achievement support system 1 according to each embodiment of the present invention. [Figure 2] Block diagram showing the hardware configuration of server 10 according to the first embodiment. [Figure 3] This is a block diagram showing the hardware configuration of the user terminal 20 according to the first embodiment. [Figure 4] This is a block diagram showing the functional configuration of the server 10 according to the first embodiment. [Figure 5] Figures 5A to 5E illustrate the flow from goal setting to goal achievement in the first embodiment. [Figure 6] This diagram shows the processing flow of the goal achievement support system 1 according to the first embodiment until the individual condition C1 is satisfied. [Figure 7] This diagram shows the processing flow of the goal achievement support system 1 according to the first embodiment until the individual condition C2 is satisfied. [Figure 8] This is a block diagram showing the functional configuration of the server 10 according to the second embodiment. [Figure 9] Figures 9A and 9B show the states in which the authorization setting unit 11d can be set and the states in which it cannot be set in the second embodiment. Figure 9C shows the state in which the authorization setting unit 11d cannot be set in Modification 1 of the second embodiment. [Figure 10] Figures 10A to 10C illustrate the flow of authority transfer in a modified example 2 of the second embodiment. [Figure 11] This figure shows the new objectives and the inherited objectives in Modification 3 of the second embodiment. [Figure 12] Figures 12A and 12B illustrate an example in Modification 3 of the Second Embodiment in which two permissions can be set for one user. [Figure 13] Figures 13A and 13B illustrate an example in Modification 3 of the Second Embodiment where two permissions cannot be set for a single user. [Figure 14] This diagram illustrates an example in Modification 3 of the Second Embodiment, where one user is assigned to individual conditions included in the four objectives, and two permissions are set. [Figure 15] This figure shows a modified example of the second embodiment, variation 4, in which the number of continuous targets is limited. [Figure 16] This figure shows an example in Modification 5 of the Second Embodiment where one user is assigned to individual conditions included in the four objectives, and two permissions are set, with one permission being set to active. [Figure 17] This diagram illustrates the processing flow from when the individual condition C1 of the goal achievement support system 1 according to the second embodiment is met until a candidate for the successor user is specified. [Figure 18] This diagram illustrates the processing flow until the individual condition C2 of the goal achievement support system 1 according to the second embodiment is met and a candidate user for the successor is specified. [Figure 19] Figure 12A shows an example in the third embodiment where deadlines are set for individual conditions. Figure 12B shows an example where the deadlines for individual conditions are reset. [Figure 20] This is a block diagram showing the functional configuration of the server 10 according to the fourth embodiment. [Modes for carrying out the invention]

[0009] Several embodiments of the present invention will be described below with reference to the drawings. The various features shown in the embodiments below can be combined with each other. Furthermore, each feature constitutes an independent invention.

[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 apparatus that forms 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 capable of communicating with each user terminal 20 via a communication line 5. The server 10 can set goals to be achieved by a plurality of users, collect information on user behaviors transmitted from each user terminal 20, and manage the progress status of the goals and users working toward achieving the goals. The server 10 supports users in achieving their goals through such goal setting, progress management, and user management. Each configuration will be described below.

[0012] (1-2. Hardware configuration of goal achievement support system 1) Referring to FIG. 2 and FIG. 3, the hardware configuration of the goal achievement support system 1 will be described.

[0013] (1-2-1. Hardware configuration of server 10) FIG. 2 is a block diagram showing the hardware configuration of the server 10 according to the present 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 configured with a keyboard, a mouse, or the like that receives input of various operations, and a monitor 15 such as a liquid crystal display device that displays 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 portion of the memory unit 12 consists of, for example, RAM (Random Access Memory) or DRAM (Dynamic Random Access Memory), and is used as a work area when the control unit 11 executes various programs. Another portion of the memory unit 12 consists of, for example, non-volatile memory such as ROM (Read Only Memory) or an HDD (Hard Disk Drive), and stores various data such as information about targets and information about user 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, and programs for realizing various functions, and include the computer programs according to this embodiment.

[0017] The communication unit 13 is, for example, a NIC (Network Interface Controller) and has the function of connecting to the communication line 5. Alternatively, the communication unit 13 may have functions to connect to a wireless LAN (Local Area Network), a wireless WAN (Wide Area Network), short-range wireless communication such as Bluetooth®, and infrared communication, either in place of or in conjunction with the NIC. The server 10 is connected to other information processing devices such as user terminals 20 via the communication line 5 and can send and receive various types of data with these other information processing devices.

[0018] The control unit 11, storage unit 12, communication unit 13, operation input unit 14, and monitor 15 are electrically connected to each other via a system bus 16. Therefore, the control unit 11 can access the storage unit 12, display images on the monitor 15, understand the user's operation status on the operation input unit 14, 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) Figure 3 is a block diagram showing the hardware configuration of the user terminal 20 according to this embodiment. The user terminal 20 is, for example, an information processing terminal such as a smartphone or tablet, and comprises a control unit 21, a storage unit 22, and a communication unit 23. The user terminal 20 may also be equipped with an inertial sensor 24, a touch panel display 25 that can display images and accept operations, a speaker 26 that outputs sound, a microphone 27 that receives sound input, a camera 28 that captures images of subjects, and operation buttons 29. The following explanation 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 caused by the user's body movements, and is, for example, an acceleration sensor or a gyroscope (angular velocity sensor). For example, by detecting the movement of the user terminal 20 using the inertial sensor 24, the control unit 21 can detect the movements of the user holding the user terminal 20, such as walking or running, and calculate the number of steps.

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

[0022] These components—the control unit 21, memory unit 22, communication unit 23, inertial sensor 24, touch panel display 25, speaker 26, microphone 27, camera 28, and operation buttons 29—are electrically connected to each other via the system bus 30. Therefore, the control unit 21 can access the memory unit 22, detect user movement using the inertial sensor 24, display images on the touch panel display 25, understand the user's operation status on the touch panel display 25 and operation buttons 29, 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] User terminals 20a, 20b, and 20c are configured similarly as user terminal 20, but their specifications, such as size and performance, may be identical or different from each other.

[0024] (1-3. Functional configuration of Server 10) As shown in Figure 4, the control unit 11 of the server 10 includes a target setting unit 11a, a user information collection unit 11b, and a determination unit 11c.

[0025] The goal setting unit 11a sets the goal. The user information collection unit 11b collects information from the user terminal 20 regarding the user's predetermined actions to satisfy individual conditions (details of which will be described later). The determination unit 11c determines whether the goal has been achieved based on the collected information regarding predetermined actions. Details of each function will be described later.

[0026] The functional configuration described above may be implemented by software (including so-called applications) appropriately installed on the server 10, or by hardware. When implemented by software, the control unit 11 can implement various functions by executing programs that constitute the software.

[0027] If implemented by executing a program, the program may be stored in the storage unit 12 built into the server 10, or in a non-temporary recording medium readable by a computer. Alternatively, the program may be read from an external storage device and implemented through so-called cloud computing. Or, if implemented by hardware, it can be implemented by various circuits such as ASICs, SOCs, FPGAs, or DRPs. Furthermore, some of the functional configurations described above may be processed by software or hardware on the user terminal 20.

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

[0029] Referring to Figure 5, the function of the target setting unit 11a will be explained in detail. The target setting unit 11a sets target M1 as shown in Figure 5A. Target M1 may be set automatically according to predetermined conditions, or it may be set by instructions from the administrator of the server 10 or the user of the user terminal 20.

[0030] Achievement condition R1 is set for objective M1. Achievement condition R1 includes multiple 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 that has the function of assigning individual conditions to users. Figure 5 shows an example in which the achievement condition includes three individual conditions, but it is sufficient to include multiple, i.e., two or more individual conditions.

[0031] Each individual condition is a condition that is met by the user performing a predetermined action. A predetermined action is, for example, the user's actual actions while holding the user terminal 20 or operations performed on the user terminal 20. More specifically, the user's actual actions include specific actions such as walking or running while carrying the user terminal 20, or repeatedly moving the user terminal 20 in a certain direction while holding it in the hand. More specifically, operations performed on the user terminal 20 include specific input operations via the touch panel display 25 or operation buttons 29 in an application running on the user terminal 20.

[0032] If the predetermined action is walking or running while carrying the user terminal 20, the walking or running action can be quantified as, for example, the number of steps calculated based on the user's movements detected by the inertial sensor 24 of the user terminal 20, or the distance traveled based on location information such as GPS identified by the communication unit 23. In other words, the predetermined action by the user can be handled as numerical data in this way. Note that the calculation (counting) of the number of steps may be performed based on both the detection result from the inertial sensor 24 and the detection result of movement based on the identification of location information. Furthermore, the distance traveled may be calculated so that only movement at a speed below a certain speed is added to the distance traveled.

[0033] Figures 5B to 5E show examples where each of the individual conditions C1 to C3 is met by different users U1 to U3. Here, as an example, we will explain the case where the goal M1 is set to "three users walk 3000 steps" and the individual conditions C1 to C3 are set to "met when a user walks 1000 steps".

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

[0035] As shown in Figure 5C, user U1 walks 1000 steps to satisfy individual condition C1, and if individual condition C1 is satisfied (i.e., C1 is cleared), a different user U2 will perform a walking action as a predetermined user action to satisfy individual condition C2.

[0036] Next, as shown in Figure 5D, user U2 walks 1000 steps to satisfy individual condition C2. If individual condition C2 is satisfied (i.e., C2 is cleared), user U3, who is different from both user U1 and user U2, will perform a walking action as a predetermined user action to satisfy individual condition C3.

[0037] Similarly, as shown in Figure 5E, when user U3 walks 1000 steps to satisfy individual condition C3, and individual condition C3 is satisfied (i.e., C3 is cleared), then all individual conditions C1 to C3 are satisfied, thus fulfilling achievement condition R1, and thus objective M1 is achieved.

[0038] Furthermore, the goal setting unit 11a may set the achievement condition R1 to include other conditions in addition to the individual conditions C1 to C3. If the achievement condition R1 includes other conditions, the achievement condition R1 will be satisfied when the other conditions are met in addition to the individual conditions C1 to C3. Various conditions can be set as other conditions, but examples include conditions related to time limits from the start of goal efforts to achievement, conditions related to deadlines such as achieving by a specific date, and conditions related to user attributes such as requiring goal sharing by users with specific attributes.

[0039] In the example shown in Figure 5 above, we have illustrated an example where each of the individual conditions C1 to C3 is satisfied by different users U1 to U3. Here, "the individual conditions are satisfied by different users" does not necessarily mean that the individual conditions are satisfied by only one user. That is, in one embodiment, the individual conditions may be satisfied by a group of users that includes one or more users. The settings may be configured so that each group of users does not allow to contain the same user (no overlap of users between user groups), or the settings may be configured so that each group of users can contain the same user (i.e., the user groups do not need to be completely identical).

[0040] (1-5. Functions of the user information collection unit 11b) The user information collection unit 11b collects information about predetermined user actions to satisfy individual conditions transmitted from each user terminal 20 via the communication unit 13. Specifically, the communication unit 13 stores the information about predetermined actions received in the storage unit 12 and performs aggregation of these. The server 10 may request the user terminal 20 to transmit information about predetermined actions at predetermined timings, or it may wait for the user terminal 20 to transmit the information without making a request.

[0041] In the example shown in Figure 5 above, in state 5B, information regarding a predetermined action taken by user U1 to satisfy individual condition C1 (number of steps taken by user U1) is received from user terminal 20a of user U1, and this information is aggregated (for example, the total number of steps is calculated). Similarly, in state 5C, information regarding a predetermined action taken by user U2 is received from user terminal 20b of user U2, and in state 5D, information regarding a predetermined action taken by user U2 is received from user terminal 20c of user U3, and this information is aggregated.

[0042] If the individual conditions are met by a group of users including one or more users, the system may be configured so that multiple users transmit information about a predetermined action from their respective user terminals 20, and this information is collected by the server 10.

[0043] (1-6. Function of the determination unit 11c) The determination unit 11c determines whether the goal has been achieved based on the information collected regarding predetermined actions. In the example shown in Figure 5 above, the determination unit 11c determines whether individual conditions C1 to C3 have been met based on the information collected from each user terminal 20a to 20c. For example, if individual condition C1 is set to "met when the user walks 1000 steps", the determination unit 11c determines whether the total number of steps received and aggregated by the user information collection unit 11b has reached 1000 steps. The determination unit 11c also determines whether achievement condition R1 has been met.

[0044] In this configuration, the server 10 sets a goal that is achieved when achievement conditions are met, which include multiple individual conditions that are met by different users, the user information collection unit 11b collects information from the user terminal 20, and the determination unit 11c determines whether the individual conditions and achievement conditions have been met to determine whether the goal has been achieved. With this configuration, the goal is not achieved unless at least all individual conditions are met, which creates a sense of responsibility among goal-sharing users towards other goal-sharing users and improves and maintains each user's motivation to contribute to achieving the goal.

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

[0046] First, as shown in Figure 6, the goal setting step (S110) is performed. In S110, the goal setting unit 11a of the server 10 sets a goal M1 which has achievement conditions R1 that include a plurality of individual conditions C1 to C3. The goal M1 is stored in the storage unit 12, but it may also be transmitted to the user terminal 20a at the time of setting and stored separately or instead in the storage unit 22 of the user terminal 20a.

[0047] Next, S210 is executed. In S210, a target M1 is selected on the user terminal 20a, in which efforts toward achieving the target will be initiated according to the actions of user U1 or predetermined conditions, and a request to start the target is sent to the server 10. Also in S210, a request is sent to the server 10 to assign the individual conditions included in the achievement conditions R1 of target M1 to user U1.

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

[0049] Here, regarding the assignment, the conditions may be assigned to users sequentially as each individual condition is met, as shown in Figures 5A to 5D. Alternatively, at the start of objective M1, all individual conditions C1 to C3 may be assigned simultaneously to all users U1 to U3 according to user U1's designation or predetermined conditions. In the case of simultaneous assignment, the consent of users U2 and U3 may be required.

[0050] Next, the user information collection step (S120) and S220 are executed. In S220, the user terminal 20a transmits information about a predetermined action of user U1 to satisfy individual conditions. In S120, the user information collection unit 11b receives the information transmitted from the user terminal 20a. The received information is stored in the storage unit 12 and aggregated. In S120, the user information collection unit 11b may request the user terminal 20a to transmit information about a predetermined action of user U1, that is, to execute S220.

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

[0052] If individual condition C1 is met, S130 is executed. In S130, it is determined whether achievement condition R1 is met. In Figure 6, only individual condition C1 is met out of individual conditions C1 to C3, so it is determined that achievement condition R1 is not met.

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

[0054] Next, S230 is executed. In response to the approval request from server 10, user terminal 20b sends an approval or rejection message according to user U2's actions or predetermined conditions.

[0055] If approval is sent in S230, then S140 is executed. In S140, as in 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 Figure 7, only individual conditions C1 and C2 are satisfied among individual conditions C1 to C3, so it is determined that achievement condition R1 is not satisfied.

[0057] Next, as shown in Figure 7, the same processing as in S135-S155 is performed for individual condition C3 in relation to user U3 and user terminal 20c. Then, in determining the achievement condition, if all individual conditions C1-C3 are met, and there are no other conditions or all other conditions are met, it is determined that achievement condition R1 has been met. In other words, it is determined that objective M1 has been achieved.

[0058] <2. Second Embodiment> (2-1. Goal achievement support system 1 according to the second embodiment) The following describes the goal achievement support system 1 according to the second embodiment of the present invention. The goal achievement support system 1 in the second embodiment differs from the first embodiment in that it further includes an authorization setting unit 11d, as shown in Figure 8. The following will focus on the differences.

[0059] In the second embodiment, the authorization setting unit 11d manages the authorization to execute the goals, thereby enabling more detailed management of the progress of the goals and the users working to achieve the goals.

[0060] (2-2. Functional configuration of Server 10) As shown in Figure 8, the control unit 11 of the server 10 includes a target setting unit 11a, a user information collection unit 11b, a determination unit 11c, and an authorization setting unit 11d.

[0061] (2-3. Functions of the permission setting section 11d) The authorization setting unit 11d sets the authority to execute the goal for a user. The user who has been granted authorization is designated as an authorized user, and only one authorization can be set for the same goal at a time. Authorized users can send information about their predetermined actions to the server 10 to satisfy individual conditions, and this information can be collected by the server 10. Other users are unable to send information about their predetermined actions to satisfy those individual conditions (even if sent from another user's user terminal 20, it will not be collected by the user information collection unit 11b of the server 10 and will not become basic information for the determination unit 11c). With this configuration, the authorization setting unit 11d sets only one user to work on the same goal at a time, and the fulfillment of individual conditions must be carried out by the authorized user, creating a greater sense of responsibility to other users who share the goal, and improving and maintaining their motivation to contribute to achieving the goal.

[0062] Referring to Figures 9 to 14, the functions of the authorization setting unit 11d will be explained in detail. In Figure 9A, the authorization G1 to execute objective M1 is set for user U3. User U3 has information collected by the server 10 regarding predetermined actions to satisfy individual condition C3. Authorization G1 has been removed from user U1. When authorization G1 is removed from user U1, the deletion authorization DG1, which indicates that user U1 had authorization G1, may be recorded in the storage unit 12 and associated with user U1.

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

[0064] If a specific condition is assigned to only one user, the removal and establishment of permissions will, in principle, only occur when the specific condition is met. On the other hand, if a specific condition is assigned to multiple users, the removal and establishment of permissions may occur even when the specific condition is not met. In other words, permissions for that specific condition may be transferred among users belonging to the group of users to which the condition is assigned.

[0065] (2-3-1. Modification 1 of the function of the permission setting unit 11d) Furthermore, the authorization setting unit 11d may be configured to set authorizations for users who have not yet been granted authorizations for the goal. With this configuration, it is possible to control the system so that multiple individual conditions are addressed by a single, different user, and the goal is achieved by the same number of different users as there are individual conditions. In other words, it is possible to control the system so that the same user repeatedly satisfies the individual conditions, and the goal is not achieved by fewer users than there are individual conditions.

[0066] In this case, the target setting unit 11a is configured in the same way as in the first embodiment, but is further configured to set individual conditions so that they are 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 containing two or more users to one individual condition.

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

[0068] (2-3-2. Modification of the function of the permission setting unit 11d 2) Furthermore, the authorization setting unit 11d may be configured to erase the authorization of the transferor user who is an authorized user, set authorization on one of the transferor user candidates (one or more users other than the transferor user) that the transferor user designated as a candidate for the transferor user, and designate the newly authorized user as the transferor user. With this configuration, the authorization is transferred to a user who is eligible to take over at the time of transfer, so the users who share the goal are not fixed at the time of goal setting, but are transferred flexibly, and it is possible to expect an expansion of the range of users who share the goal. In other words, the user who started working on the goal (user U1 in Figure 10A) is not limited to users who are eligible to take over, and it becomes possible to take over the authorization of subsequent users (user U2 in Figure 10C).

[0069] In Figure 10A, user U1 is granted the authority G1 to execute objective M1. User U1 has information collected by server 10 regarding predetermined actions to satisfy individual condition C1. If the determination unit 11c determines that individual condition C1 has been satisfied, the authority setting unit 11d removes authority G1 from user U1, as shown in Figure 10B.

[0070] User U1, whose authority G1 has been revoked, can be configured to specify one or more users from the list of potential successor users who will be assigned authority G1 next to individual condition C2. Here, user U1, whose authority G1 has been revoked and who intends to transfer the authority to the next user, is referred to as the successor user, and the one or more users specified to user U1 are referred to as potential successor users.

[0071] In one embodiment, when specifying a candidate user to take over, a list of available users may be displayed on the touch panel display 25 of the user terminal 20a of user U1 (the user taking over). The users displayed in the list as available users are selected, for example, based on information regarding their relationship with user U1 (hereinafter also referred to as "friend information").

[0072] Friend information is an index of interactions both inside and outside the service that provides the goal achievement support system 1. In other words, the users displayed may be prioritized according to the degree of interaction with user U1 (or the depth of the friendship, closeness, etc.). Interactions within the service include, for example, exchanging service accounts or IDs and being able to contact each other. Interactions outside the service include, for example, making some kind of contact (so-called "likes," "follows," "add friends," etc.) on social networking services (SNS) such as chat applications.

[0073] One reason a user might be given higher priority when displayed is that they have previously shared goals with a user other than Goal M1, or that they have met or are highly likely to meet many of the individual conditions for goals other than Goal M1.

[0074] In Figure 10B, users U2 to U4 are specified as candidates for the user to take over. If individual condition C2 is assigned to user U2 and permission G1 is set, then user U2 becomes an authorized user in M1, as shown in Figure 10C. User U2, who has taken over permission G1, is also referred to as the user to take over.

[0075] Furthermore, the authorization setting unit 11d may be configured to set authorizations for the first candidate user approved as a successor user when the original user designates multiple users as candidates for successor users, and to remove the designation of other users as successor user candidates. In one embodiment, approval of a successor user candidate is transmitted from the user terminal 20 to the server 10 according to user operation or predetermined conditions. When the server 10 receives such approval, it is configured to assign individual conditions and set authorizations.

[0076] This configuration prevents a situation where, if the user is transferred to one of the transferee users, other transferee users remain designated even though they are no longer eligible to become the transferee user for that target. In other words, it prevents duplicate approval by multiple transferee user candidates.

[0077] In Figure 10B, if user U2 approves first, the designation of users U3 and U4 as potential users to take over authority G1 will be removed.

[0078] In one embodiment, when user U2 (a candidate user to take over) performs approval, a list of specifications for each approved goal may be displayed on the touch panel display 25 of user U2's user terminal 20b. User U2 selects a specification from the list and performs the approval operation.

[0079] If user U2 approves first, the designation of user U3 as a potential successor user is removed, but the removed designation is no longer included in the list of approved designs displayed on the touch panel display 25 of user terminal 20c. Even if user U3 selects and approves the removed designation, it will be rejected by server 10.

[0080] (2-3-3. Modification 3 of the function of the permission setting unit 11d) Furthermore, the permission setting unit 11d may be configured to allow setting one permission each for new goals and inherited goals for a single user.

[0081] The goals set by the goal setting unit 11a become either new goals or inherited goals depending on the progress of the goals. A new goal is a goal in which the assigned authorized user is the first authorized user. An inherited goal is a goal in which the assigned authorized user is the second or subsequent authorized user.

[0082] In other words, if an individual condition included in the achievement conditions set for a goal has not yet been met, and the user assigned to that individual condition is granted permission for the first time in that goal, then that goal becomes a new goal. In Figure 11, goal M1 is a new goal because permission G1 has been granted to user U1 for the first time. Goal M4 is also a new goal in the same way.

[0083] On the other hand, if the assigned user has been granted permissions, one or more individual conditions included in the achievement conditions set for the goal have already been met, and this is not the first time that permissions have been granted for that goal (second time or later), then that goal becomes a carryover goal. In Figure 11, goal M2 is a carryover goal because the setting of permissions G2 for user U1 is the second time, following the setting for user UA. Similarly, goal M3, which is the third setting, is also a carryover goal.

[0084] Figures 12 to 14 illustrate the feasibility of setting permissions for user U1 in relation to several combinations of the objectives in Figure 11.

[0085] In Figure 12A, user U1 is simultaneously assigned two permissions, G1 and G2. Permission G1 is for the new objective M1. On the other hand, permission G2 is for the individual condition C2-2 set in the middle of the inherited objective M2. Thus, the permission setting unit 11d can set one permission each for the new objective and the inherited objective. In Figure 12B, permission G1 is the same as in Figure 12A. On the other hand, permission G3 is for the individual condition C3-3 set at the end of the inherited objective M3. The permission setting unit 11d can also set one permission each for this combination of new objective and inherited objective.

[0086] On the other hand, in Figure 13A, user U1 is simultaneously assigned two permissions, G2 and G3. Permission G2 is the permission for objective M2, which is a transfer objective. Permission G3 is also the permission for objective M3, which is a transfer objective. Therefore, since the permission setting unit 11d can set one permission each for new objectives and transfer objectives for one user, it is not possible to set more than one permission for transfer objectives in this manner. Similarly, in Figure 13B, permissions G1 and G4 are the permissions for new objective M1 and new objective M4, respectively, so the permission setting unit 11d is also unable to set more than one permission for new objectives in this manner.

[0087] In Figure 14, the permissions for objectives M2 and M4 are transferred to different users. Therefore, even if user U1 is assigned to individual conditions included in the four objectives M1 to M4, the permission setting unit 11d can set one permission each for the new objective and the transferred objective. By configuring the system in this way to limit the number of permissions that can be set for the same user, it is possible to avoid an imbalance in the distribution of objectives among users and to distribute them evenly.

[0088] (2-3-4. Modification of the function of the permission setting unit 11d 4) Furthermore, the authorization setting unit 11d may be configured such that, if authorization is set for a user in the first new objective, authorization can be set for that user in the second new objective after the first new objective is achieved, and if authorization is set for a user in the first handover objective, authorization can be set for that user in the second handover objective after the first handover objective is achieved.

[0089] In the example in Figure 14, goals M1 to M4 are unachieved goals, but are ongoing goals for which efforts toward achievement are continuing. User U1 has been granted permission G1 for goal M1 and permission G3 for goal M3. In addition, user U1 was granted permission G2 for goal 2 and permission G4 for goal M4 (delete permission DG2, delete permission DG4).

[0090] In other words, in the above modified example 3, after granting authority to a user in the first new goal or handover goal, it is possible to grant authority to that user in the second new goal or handover goal before the first new goal or handover goal is achieved. Even if efforts toward achieving the new goal or handover goal for which authority has been granted are ongoing, authority can be granted in other new goals or handover goals as well.

[0091] On the other hand, in this modified example, the number of permissions and elimination permissions corresponding to users in the ongoing goals is limited. Below, we will explain examples of what can be set in this modified example with reference to Figure 15. In Figure 15, goals M1 and M2 are ongoing goals because they have not been achieved, while goals M3 and M4 are not ongoing goals because they have been achieved.

[0092] User U1 had permissions set for both objective M1 and objective M4. However, objective M1 is a continuing objective, while objective M4 is not. In other words, the only continuing objective for which user U1 has permissions, or has had permissions set, is objective M1. Objective M4 was handed over from user U1 to user UE and is a handed-over objective for user UE, but for user U1, for whom permissions were set as a new objective, it can be considered a new objective even after the handover. Furthermore, user U1 had permissions set for two handed-over objectives, objective M2 and objective M3. However, objective M2 is a continuing objective, while objective M3 is not. In other words, the only continuing objective for which user U1 has permissions, or has had permissions set, is objective M1.

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

[0094] In this way, by configuring the permission setting unit 11d to limit the number of permissions and deletion permissions corresponding to users in continuous goals, it is possible to avoid an imbalance in goals among users and to distribute them evenly. Furthermore, it is possible to prevent users from having many goals at the same time and neglecting some of them.

[0095] (2-3-5. Modification of the function of the permission setting unit 11d 5) Furthermore, the authorization setting unit 11d may be configured to activate one of the multiple authorizations if multiple authorizations are set for a single user. In this case, the user information collection unit 11b is configured to collect information about a predetermined action for the objective related to the active authorization. This configuration makes it possible to restrict the simultaneous fulfillment of individual conditions for multiple objectives by a single action by the user. The authorization setting unit 11d may also be configured to activate and deactivate an authorization even if only one authorization is set for a single user.

[0096] For example, as shown in the example in Figure 14 above, if a user is assigned one permission each for new goals and inheritance goals, the permission setting unit 11d can activate only the permission assigned to either the new goal or the inheritance goal. In Figure 16, user U1 is assigned two permissions, permission G1 and permission G3, but only permission G3 for goal M3 is set to be active, becoming the active permission AG3.

[0097] (2-4. Flow from goal setting to goal achievement using the goal achievement support system 1 according to the second embodiment) Referring to Figures 17 and 18, the process from goal setting to goal achievement using the goal achievement support system 1 according to the second embodiment will be explained for goal M1 in Figure 16 described above.

[0098] As shown in Figure 17, the authorization setting step (S160) is executed after S115. In S160, the authorization setting unit 11d sets authorization G1 for user U1. That is, user U1 sends information about a predetermined action to satisfy individual condition C1-1 to the server 10, and is set as a user from whom the server 10 collects this information.

[0099] Next, in one embodiment, S290 and S190 are executed. In S190, one of the privileges G1 set for user U1 is activated. Activation is performed according to an operation by user U1 or predetermined conditions. For example, according to an operation by user U1, user terminal 20a sends a request to activate privilege G1. Server 10, which receives the request, activates the privilege G1 set for user U1 by the privilege setting unit 11d.

[0100] If S190 is executed, in S120 and S220, the user terminal 20a transmits information regarding a predetermined action taken by user U1 to satisfy 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 individual condition C1 is met based on the information collected in S120. If individual condition C1 is not met, S120 is executed again.

[0102] In S125, if it is determined that individual condition C1-1 is met, the authorization cancellation step (S165) is executed. In S165, the authorization setting unit 11d cancels authorization G1 set for user U1. If authorization G1 was activated, the authorization setting unit 11d deactivates authorization G1.

[0103] Next, in one embodiment, S250 is executed. In S250, candidate users U2 to U4 are designated according to the operation of user U1 or predetermined conditions (see Figure 10B), and the designated content is sent from the user terminal 20a to the server 10. The designation may be made by a request from the server 10 to the user terminal 20a, but if it is determined that the individual conditions have been met, the designated content may be sent from the user terminal 20a to the server 10 without a request from the server 10.

[0104] Next, as shown in Figure 18, S136 is executed instead of S135 in Figure 7. In S136, the authorization setting unit 11d makes an authorization transfer request to each user terminal 20 of the transferee user candidates U2 to U4 to set authorization G1.

[0105] Next, S231 is executed instead of S230. In S231, user terminal 20b sends an authorization request to server 10 regarding the transfer of authority to set authority G1 to user U2.

[0106] Next, S140 and S170 are executed. In S140, individual condition C1-2 is assigned to user U2, who was the first among the candidate users U2 to U4 to approve the transfer, and at the same time, permission G1 is set for user U2. Meanwhile, S180 is executed, and the designations for the other candidate users U3 to U4 are removed.

[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 following describes the goal achievement support system 1 according to the third embodiment of the present invention. The goal achievement support system 1 in the third embodiment differs from the first embodiment and others in that, as shown in Figure 19, the goal setting unit 11a sets a deadline for the individual conditions to be met for the goal. The following will focus on the differences.

[0108] In the third embodiment, the goal setting unit 11a can facilitate the user taking predetermined actions to satisfy individual conditions by setting deadlines for when individual conditions must be met.

[0109] (3-2. Functions of the goal setting unit 11a) The goal-setting unit 11a is configured to set deadlines for when individual conditions must be met for the goal. If the individual conditions are not met within the deadline, it becomes impossible to meet the individual conditions after the deadline, the achievement conditions are not met, and the effort toward the goal ends in failure. With this configuration, it is expected that users will proactively take the prescribed actions to meet the individual conditions within the set deadline, and efforts toward achieving the goal will not stagnate.

[0110] The goal setting unit 11a sets deadlines T1 to T3 for each of the individual conditions C1 to C3 of goal M1, as shown in Figure 19A, for example. User U1, who is assigned individual condition C1, is required to satisfy individual condition C1 by deadline T1.

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

[0112] Furthermore, the goal-setting unit 11a may be configured to extend the deadline through an extension procedure. This configuration prevents stagnation in goal achievement by setting a deadline, while also avoiding a decline in user motivation due to failure to achieve the goal.

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

[0114] The extension procedure may involve, for example, a specific user action, a specific user behavior, or payment of consideration. The consideration may be, for example, user-owned value (a medium of exchange) such as points usable within the service, or five elements within the service system such as items for extension. Payment of consideration may be made through the consumption or use of these.

[0115] Furthermore, a limit may be placed on the number of extension procedures that can be performed under a single individual condition (for example, limiting it to once). By imposing such a limit, a balance can be struck between preventing stagnation in goal achievement and preventing a decline in motivation.

[0116] Furthermore, the target setting unit 11a may be configured to reset the extended deadline when an extension procedure is performed before the deadline expires. The target setting unit 11a may also be configured to reset the extended deadline when an extension procedure is performed after the deadline expires. If the extension procedure is performed by payment of consideration, the extension procedure after the deadline expires may be set to require a higher consideration than the consideration required for the procedure before the deadline expires.

[0117] <4. Fourth Embodiment> (4-1. Goal achievement support system 1 according to the fourth embodiment) The following describes the goal achievement support system 1 according to the fourth embodiment of the present invention. The goal achievement support system 1 in the fourth embodiment differs from the first embodiment and others in that it further includes a reward granting unit 11e, as shown in Figure 20. The following will focus on explaining the differences.

[0118] In the fourth embodiment, the reward granting unit 11e grants rewards set for the target to users who have contributed to achieving the target, thereby increasing motivation to perform predetermined actions to meet individual conditions and contribute to achieving the target.

[0119] (4-2. Functional configuration of Server 10) As shown in Figure 20, the control unit 11 of the server 10 includes a target setting unit 11a, a user information collection unit 11b, a determination unit 11c, an authorization setting unit 11d, and a benefit granting unit 11e.

[0120] (4-3. Functions of the goal setting unit 11a) The goal setting unit 11a is configured to set rewards for goals. The rewards to be set are, for example, rewards that are given to each user who has met the individual conditions included in the achievement conditions when the achievement conditions are met and the goal is achieved. Alternatively, the rewards to be set may be rewards that are given to users who have met the individual conditions when those individual conditions are met.

[0121] The benefits granted may differ for each user. Furthermore, the benefits granted may be set to vary depending on the user's attributes, the role the user played in achieving the goals, and other conditions.

[0122] The benefits granted may include, for example, points or other values ​​usable both inside and outside the service providing the goal achievement support system 1, or game elements such as items or in-game currency usable in related games inside and outside the service.

[0123] (4-4. Functions of the benefit granting unit 11e) The reward granting unit 11e is configured to grant rewards to each user who has met the individual conditions included in the achievement conditions when the determination unit 11c determines that the goal has been achieved. This configuration allows rewards to be granted to users who have contributed to achieving the goal, thereby increasing their motivation to contribute.

[0124] Furthermore, the reward granting unit 11e may be configured to grant rewards to users who meet individual conditions when those conditions are met. By configuring it in this way, even if the overall goal is not achieved, rewards will be granted to users who have met individual conditions and contributed to achieving the goal 6, which can further enhance motivation for contribution.

[0125] Furthermore, the reward granting unit 11e may be configured to grant more rewards to users who were authorized to set new goals than to users who were authorized to set inherited goals when granting rewards. By configuring it in this way, it is possible to improve the motivation of users who take on goals as new goals (users who start working towards achieving the goals).

[0126] <5. Other Embodiments> While embodiments and modifications thereof of the present invention have been described above, the application of this disclosure is not limited to the above.

[0127] Furthermore, although the above embodiment primarily describes a configuration in which the server 10 provides each function, it is possible to configure the user terminal 20 to provide some functions, or for both the server 10 and the user terminal 20 to provide them, provided that such configurations are permissible by their nature.

[0128] Furthermore, although the above embodiment described an example in Figure 10B where specific users U2 to U4 were specified, in one embodiment, it is not necessary to individually select the candidate users to take over, and the system may be configured to specify all users who can be specified at the time of specification all at once. In addition, the number of times that a batch specification can be performed within a certain period may be limited.

[0129] Furthermore, in the above embodiment, the list of candidate users to take over, as specified in Figure 10B, is described in an example where the list of designations for each approved goal is displayed on a screen in the application related to the goal achievement support system 1. Such designations can also be made for potential users who have not yet used the goal achievement support system 1.

[0130] For example, the transferring user (or Goal Achievement Support System 1) may notify potential users who have not yet used Goal Achievement Support System 1 of the designation via a chat application, email, etc. When designating potential users on a screen displayed in an application, etc., the system may be configured so that users extracted from contacts held in services other than Goal Achievement Support System 1 are displayed on the screen as candidates for the transfer user. In addition, instructions on how to use the Goal Achievement Support System 1 service may be sent to potential users at the same time.

[0131] Furthermore, the control unit 11 may be configured such that, if individual conditions for the first new objective are assigned to the user, individual conditions for the second new objective are assigned to the user after the first new objective is achieved, and if individual conditions for the first successor objective are assigned to the user, individual conditions for the second successor objective are assigned to the user after the first successor objective is achieved.

[0132] Furthermore, the server 10 (or user terminal 20) may have a function (support notification unit) that allows a user to indicate that they are supporting another user who has not yet met their assigned individual conditions. That is, if user B sends a message to the server 10 via user terminal 20 indicating that they are supporting user A, who is working on a predetermined action to meet their assigned individual conditions, the server 10 records this in the storage unit 12. When the message of support is recorded, user A's user terminal receives information about the record from the server 10, and a message indicating that user B is supporting user A is displayed on user A's user terminal.

[0133] Furthermore, although the above embodiment describes a configuration in which the goal setting unit 11a sets deadlines for when individual conditions for the goal should be met, the goal setting unit 11a may also be configured to set other deadlines. For example, the goal setting unit 11a may set a period during which all achievement conditions should be met. Alternatively, the goal setting unit 11a may set a deadline from the designation of a candidate user to the approval of the designation.

[0134] Furthermore, although the user terminal 20 in the above embodiment was described as an information processing terminal such as a smartphone or tablet equipped with an inertial sensor 24, etc., the system is not limited to this example. The system may be configured to detect the user's movements using a detection device equipped with an inertial sensor 24, etc., share the detected information wirelessly or via wired connection between the detection device and various information processing devices, and transmit information related to a predetermined action from the various information processing devices.

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

[0136] A server 10 according to one aspect of the present invention comprises a goal setting unit 11a, a user information collection unit 11b, and a determination unit 11c. The goal setting unit 11a sets a goal, which is achieved by fulfilling achievement conditions, and these achievement conditions include a plurality of individual conditions that are fulfilled by different users. The user information collection unit 11b collects information from the user terminal regarding predetermined user actions to fulfill the individual conditions, and the determination unit 11c determines whether the goal has been achieved based on the collected information regarding predetermined actions. With this configuration, the goal is not achieved unless at least all individual conditions are fulfilled, creating a sense of responsibility to other users who share the goal, and thus improving and maintaining the motivation to contribute to achieving the goal.

[0137] Server 10 further includes an authorization setting unit 11d, which sets authorizations for users, designates users to be authorized users, and limits the number of authorizations that can be set simultaneously for the same goal to one. With this configuration, the authorization setting unit sets only one user to work on the same goal at a time, requiring that individual conditions be met by only one user, thereby increasing responsibility to other users who share the goal and improving and maintaining their motivation to contribute to achieving the goal.

[0138] The authorization setting unit 11d sets authorization for users who have not yet been granted authorization for the goal. With this configuration, multiple individual conditions are addressed by a single, 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 the process so that the same user does not repeatedly satisfy the individual conditions and achieve the goal.

[0139] The authorization setting unit 11d revokes the authorization of the transferor user, who is an authorized user, and sets the authorization on one of the one or more users other than the transferor user that the transferor user designated as a candidate for the transferee user. The newly authorized user becomes the transferee user. With this configuration, the authorization is transferred to a user who is eligible to take over at the time of transfer, so the participants are not fixed when setting the goal, the transfer is fluid, and a wider range of users who can share the goal can be expected. The scope is not limited to users who are directly eligible to take over from the user who created the goal.

[0140] The authorization setting unit 11d, when a user who is taking over designates multiple users as candidates for the receiving user, sets the authorization for the first receiving user candidate that is approved, and removes the designation of the other designated users as receiving user candidates. This configuration prevents a situation where, when the user is taken over by one of the receiving user candidates, the other receiving user candidates remain designated in a state where they cannot become the target receiving user. In other words, it prevents duplicate approval by multiple receiving user candidates.

[0141] The objectives are either new objectives or inherited objectives. A new objective is one in which the assigned user becomes the first authorized user in that objective, while an inherited objective is one in which the assigned user becomes the second or subsequent authorized users in that objective. The authorization setting unit 11d can set one authorization each for new objectives and inherited objectives for a single user. This configuration prevents an imbalance in the distribution of objectives among users and allows for better distribution.

[0142] The authorization setting unit 11d, if multiple authorizations are set for a single user, sets one of the authorizations to be active, and the user information collection unit 11b collects information regarding predetermined actions related to the active authorization. This configuration makes it possible to restrict the fulfillment of individual conditions for multiple goals from progressing through a single action by the user.

[0143] The goal-setting unit 11a sets deadlines for the individual conditions that must be met for each goal. This configuration prevents delays in achieving the goals by setting deadlines.

[0144] The goal-setting unit 11a extends the deadline through an extension procedure. This configuration prevents the achievement of goals from stagnating due to setting deadlines, while also avoiding a decline in motivation due to failure to achieve the goals.

[0145] Server 10 further includes a reward granting unit 11e. The goal setting unit 11a sets rewards for the goals, and the reward granting unit 11e grants rewards to each user who has met the individual conditions included in the achievement conditions when the determination unit 11c determines that the goals have been achieved. This configuration enhances motivation for contribution by granting rewards to users who have contributed to achieving the goals.

[0146] The reward granting unit 11e grants rewards to users who meet the individual conditions when those conditions are met. This configuration further enhances motivation for contribution by granting rewards to users who have contributed to achieving the overall goal by meeting individual conditions, even if the overall goal is not achieved.

[0147] Server 10 further includes a reward granting unit, where goal setting unit 11a sets rewards for goals, and the reward granting unit grants more rewards to users who were authorized for the new goal than to users who were authorized for the inherited goal when granting rewards. This configuration improves the motivation of users to take on a new goal (users who start working towards achieving the goal).

[0148] A computer program according to one aspect of the present invention is a computer program that causes a computer (server 10, etc.) to execute a goal setting step S110, a user information collection step S120, and a determination step S130, wherein in the goal setting step S110, a goal is set, which is achieved by fulfilling achievement conditions, and which include a plurality of individual conditions that are fulfilled by different users, in the user information collection step S120, information on predetermined user actions to fulfill the individual conditions is collected from the user terminal, and in the determination step S130, the achievement of the goal is determined based on the collected information on predetermined actions.

[0149] An information processing method according to one aspect of the present invention comprises a goal setting step S110, a user information collection step S120, and a determination step S130, wherein the goal setting step S110 sets a goal which is achieved by fulfilling achievement conditions which include a plurality of individual conditions that are fulfilled by different users, the user information collection step S120 collects information from the user terminal about predetermined user actions to fulfill the individual conditions, and the determination step S130 determines whether the goal has been achieved based on the collected information about predetermined actions. [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 unit, 11d: Authorization setting unit, 11e: Benefit granting unit, 12: Storage unit, 13: Communication unit, 14: Operation input unit, 15: Monitor, 16: System bus, 20 (20a, 20b, 20c): User terminal, 21: Control unit, 22: Storage unit 23: Communications unit, 24: Inertial sensor, 25: Touch panel display, 26: Speaker, 27: Microphone, 28: Camera, 29: Operation buttons, 30: System bus, AG3: Permissions, C1~C3, C1-1~C1-3, C2-1~C2-4, C3-1~C3-3, C4-1~C4-2: Individual conditions, AG3: Active permission, DG1: Deletion permission, M1~M4: (New / Inherited) Goals, R1: Achievement conditions, T1 (T1'), T2, T3: Expiry date, U1: User (Original user), U2: User (Permissions) (Takeover user (candidate)), U3: User (Takeover user candidate), U4: User (Takeover user candidate)

Claims

1. The processor comprises, We set a goal that is achieved by different users fulfilling multiple individual conditions. A first individual condition is assigned to the first user who has set the aforementioned goal among multiple users. If a user who has met the aforementioned individual conditions is designated by that user, and the other users who have not been assigned the aforementioned individual conditions are assigned the other unmet individual conditions, and if multiple users among the aforementioned other users are designated as candidates for successor users, the other individual conditions are assigned to the user who first approves of becoming the successor user, and the designation of the other designated users as candidates for successor users is removed from the list of users other than the approved user. Information regarding the actions of users to whom individual conditions have been assigned is collected from the user terminal of each user to whom the individual conditions have been assigned, and based on this information, it is determined whether or not the individual conditions of the user to whom the individual conditions have been assigned have been met. The system receives, via the user terminal of the second user, a message from the second user to whom individual conditions have been assigned, indicating support for a third user who is different from the second user and has not met the individual conditions; records the received message of support; and transmits information to the user terminal of the third user indicating that the second user is supporting the third user. Information processing device.

2. The processor sets a goal that is achieved by different users fulfilling multiple individual conditions. The processor assigns a first individual condition to the first user who has set the aforementioned goal among multiple users. The processor assigns the other unfulfilled individual conditions to other users designated by the user who has fulfilled the individual conditions, who have not been assigned the individual conditions, and if multiple users among the other users are designated as candidates for successor users, the processor assigns the other individual conditions to the user who first approves to become the successor user, and removes the designation of the other designated users as successor user candidates from the user who did not approve. The processor collects information regarding the actions of users to whom individual conditions have been assigned from the user terminal of each user to whom the individual conditions have been assigned, and based on this information, determines whether or not the individual conditions of the user to whom the individual conditions have been assigned have been met. The processor receives, via the second user's user terminal, a message from the second user to whom individual conditions have been assigned, indicating support for a third user who is different from the second user and has not met the individual conditions; records the received message of support; and transmits information to the third user's user terminal indicating that the second user is supporting the third user. Information processing methods.

3. The processor is given a goal that is achieved by fulfilling multiple individual conditions, each different from the other. The processor is instructed to assign the first individual condition to the first user who has set the aforementioned goal among multiple users. The processor is instructed to assign the other unfulfilled individual conditions to other users who have not been assigned the individual conditions, as specified by the user who has fulfilled the individual conditions; if multiple users among the other users are designated as candidates for successor users, the processor is instructed to assign the other individual conditions to the user who first approved becoming the successor user, and to remove the designation of the other specified users as successor user candidates from the user who approved the approval; The processor collects information regarding the actions of users to whom individual conditions have been assigned from the user terminal of each user to whom the individual conditions have been assigned, and determines, based on this information, whether or not the individual conditions of the user to whom the individual conditions have been assigned have been met. The processor receives, via the second user's user terminal, a message from a second user to whom individual conditions have been assigned, indicating support for a third user who is different from the second user and has not met the individual conditions; records the received message of support; and transmits information to the third user's user terminal indicating that the second user is supporting the third user. program.

4. Equipped with a server and user terminals, The aforementioned server, We set a goal that is achieved by different users fulfilling multiple individual conditions. A first individual condition is assigned to the first user who has set the aforementioned goal among multiple users. If a user who has met the aforementioned individual conditions is designated by that user, and the other users who have not been assigned the aforementioned individual conditions are assigned the other unmet individual conditions, and if multiple users among the aforementioned other users are designated as candidates for successor users, the other individual conditions are assigned to the user who first approves of becoming the successor user, and the designation of the other designated users as candidates for successor users is removed from the list of users other than the approved user. Information regarding the actions of users to whom individual conditions have been assigned is collected from the user terminal of each user to whom the individual conditions have been assigned, and based on this information, it is determined whether or not the individual conditions of the user to whom the individual conditions have been assigned have been met. The system receives, via the user terminal of the second user, a message from the second user to whom individual conditions have been assigned, indicating support for a third user who is different from the second user and has not met the individual conditions; records the received message of support; and transmits information to the user terminal of the third user indicating that the second user is supporting the third user. system.

Images