JP5767066B2 - System server device and program capable of requesting processing to other device - Google Patents

Description

  The present invention relates to a server apparatus of a system that can request a certain process from another apparatus to another apparatus.

  Grid computing, which is a mechanism for distributing and executing a single calculation process to many computers, has been put into practical use. In grid computing, the server device monitors the status of the grid, that is, each computer, appropriately divides the calculation process, requests execution of the divided calculation process to each computer, and obtains the result. Here, Non-Patent Document 1 proposes a mechanism for requesting calculation processing to an apparatus such as each computer.

Dianji Huang, et al. , “MobiClood: Building Secure Cloud Framework for Mobile Computing and Communication,” In Proc. Of the 2010 Fifth IE International Symposium.

  With the recent development of computer technology and communication technology, for example, portable devices such as mobile phones can be regarded as small computers that can communicate wirelessly. These devices are equipped with various functions such as a temperature sensor and a camera. Therefore, for example, a user who has a device such as a mobile phone in a number of areas is asked to measure the temperature by the device or to take an image of a certain condition using the device, and the measurement result or the image is taken. By acquiring images and the like, various information can be collected efficiently. Moreover, a large amount of processing can be completed in a short time by a system that requests a certain processing to a plurality of portable devices or a fixed type device such as a desktop PC and receives processing results from each device like grid computing. Is possible.

  However, in order to realize the above-described system, a mechanism for linking a person who requests a certain process and his / her device and a person who executes the process and his / her apparatus is necessary. Furthermore, since some process is performed using another person's device, some remuneration is required for the person who performed the requested process. In addition, a mechanism that allows a person who executes the process to easily execute the requested process is also required.

  The present invention provides the above-described mechanism to provide a server device that links a device that requests processing with a device that executes the requested processing, and a program that causes a computer to operate as the server device.

The server device according to the present invention selects, for each executor, an executor management unit that holds a database including executor information and an executor identifier used to select an executor, and a requester. Information indicating an executioner condition for performing, information indicating a distribution number condition that is a condition for the number of requests distributed, information indicating a remuneration condition that is a payment condition for a request for processing, and an execution device for requesting processing When the request message including the execution software to be operated in is received, the number of executioner identifiers corresponding to the executioner information that matches the executioner condition is acquired from the executioner management unit by the number that matches the distribution number condition. A process of transmitting an execution request message including information indicating the reward condition and the execution software to the execution device of the performer corresponding to the acquired identifier. Processing means comprises a case where the request message said contains servers running software running on the server device, the processing means processes the processing result received from the execution unit in the server execution software The obtained intermediate processing result is transmitted to the request device, and when the server execution software is not included in the request message, the processing means transmits the processing result received from the execution device to the request device. Features.

  The requester who corresponds to the requesting device by the server device can make a request for processing by presenting the reward condition to the executing device of the unskilled executor. Further, by making a request with the execution software attached, it becomes easy to execute the processing requested by the executor.

The system block diagram in one Embodiment. The block diagram of each apparatus in one Embodiment. The figure which shows the request message and execution request message in one Embodiment. The figure which shows the feedback matrix in one Embodiment. Explanatory drawing of calculation of the rank of an executor in one Embodiment.

  FIG. 1 is a schematic configuration diagram of a system in the present embodiment. In FIG. 1, a request apparatus 1 is an apparatus used by a person who requests some processing (hereinafter referred to as a requester), and an execution apparatus 3 is an apparatus that performs a requested process in accordance with a request from the requester. is there. A person who owns and operates the execution device 3 is called an executor. The server device 2 is a device for connecting the requesting device 1 and the execution device 3. The request device 1 and the execution device 3 are each a personal computer, a mobile phone, or the like, for example. In the present embodiment, the execution device 3 is mainly a so-called smart phone equipped with a camera function and a temperature sensor, but is not a portable device such as a desktop computer. There may be. In the figure, only three execution devices are shown, but this is an example, and any number of execution devices 3 can be used. Furthermore, although the requesting device 1 and the execution device 3 are displayed as different devices, they may be devices having the same function. That is, the requesting device 1 can also operate as the execution device 3 that processes requests from other requesters, and the execution device 3 can operate as the requesting device 1 that requests processing from other performers. .

  The request device 1, the server device 2, and the execution device 3 can be connected to the network 4. The request device 1 can communicate with at least the server device 2, and each execution device 3 can communicate with the server device 2. In the present embodiment, the requesting device 1 and the execution device 3 do not need to communicate directly, but rather, as will be described later, the present system keeps the identity of the executor confidential to the requester. In addition, information about the requester and the executor and the request device 1 and the execution device 3 used by the requester and the executor are registered in the server device 2 in advance. Assume that the client ID and executor ID, which are identifiers, are assigned.

  FIG. 2 is a diagram illustrating a schematic configuration of each of the requesting device 1, the server device 2, and the execution device 3. The request unit 11 of the requesting device 1 transmits a request message to the server device 2 when requesting some processing. As shown in FIG. 3A, the request message includes a requester ID for requesting, a request ID, the number of distributions, an executor condition, a request condition, a reward condition, a memo, server execution software, Contains each field of execution software.

  The requester ID field stores the requester ID of the requester corresponding to the requesting device 1 that has transmitted the request message. The request ID field stores a request ID which is a unique value for the requester and is an identifier for the requester to identify each request. For example, the requesting apparatus 1 can use a request ID as a hash value of a value obtained by combining a time when a request is made and execution software described later. The distribution number field stores information indicating the number of persons who request execution processing, that is, a distribution number condition which is a condition for the number of distributions of an execution request message described later. For example, a specific number such as 100 people can be specified as the distribution number condition. Further, as the distribution number condition, for example, a range of numbers such as 100 or more and 200 or less can be designated. In addition, if there are more than a certain number of people who meet the performer condition described below, the distribution is made only to the predetermined number of people, and if it is less than the predetermined number, all people who meet the performer condition The condition for distribution to can also be set as the distribution number condition. In addition, when the executor condition is a request to each executor in each area, the distribution number condition can be specified for each area.

  The executor condition field stores information indicating an executor condition for specifying a condition of an executor to be requested. For example, it is possible to specify by an executor in a certain area, a function of the execution device 3 possessed by the executor, or a combination thereof. Specifically, the client who wants to obtain an image of the current coastal situation specifies the executor condition with the person having the execution device 3 with the camera function located in the vicinity of the coast where each prefecture is located. Can do. Note that the geographical range is specified by, for example, the center position and its radius. In addition, for example, it is possible to specify a condition such as an executor's profile such as the executor's age, sex, hobby, etc. The conditions that can be specified in the executor condition depend on the information of each executor held in the executor database of the server apparatus 2 described later and the information on the execution apparatus 3 possessed by each executor.

  The request condition field stores information indicating the execution of the requested process and the request condition to be satisfied by the result. The request conditions are classified into general conditions for the entire request process and individual conditions for individual performers.

  The individual condition is, for example, a condition that is set when each performer is requested to transmit a plurality of processing results, and includes a time interval for executing the process, the number of times to execute the process, and a combination thereof. The time interval can be specified in a certain time range such as once every 4 to 6 hours, for example. In addition, the number of times can be specified by a specific value such as 10 times, or can be specified in a certain range such as at least 10 times or 10 to 20 times.

  The overall condition includes a transmission time limit that is a time limit for transmitting the processing result requested by the execution device 3 to the server device 2 and the minimum number of successful performers. The successful executor is an executor who has transmitted the processing result of the requested process to the server device 2 within the transmission deadline. If the individual requirement is specified, the individual requirement is satisfied by the transmission deadline. It is the executor who transmitted the processing result to be satisfied to the server device 2. If the number of successful performers is less than the minimum number of successful performers, the request is determined to be unsuccessful, and if the number is greater than the minimum number of successful performers, the request is determined to be successful. In this embodiment, when the request is successful, the requester pays a reward according to a reward condition described later. On the other hand, if the request is unsuccessful, it is not necessary to pay a reward even for a successful performer. When there is no need to determine whether the request is successful or unsuccessful, or when a reward is always paid to a successful performer, 0 is set as the minimum number of successful performers.

  In the reward condition field, a reward condition for specifying what kind of reward is paid to the performer who has accepted the request and executed the process is stored. The reward conditions can be classified into a reward target person condition for specifying a person who receives the reward and a reward amount condition related to the amount to be paid to the receiver. First, all successful performers when the request is successful can be targeted for remuneration. However, not all successful performers, but only a predetermined number of persons in the order in which the processing results are transmitted to the server device 2 can be targeted for remuneration. In addition, when the processing result is requested a predetermined number of times or more in the individual condition of the request condition, if the transmission result is transmitted to the server device 2 even once within the transmission time limit, even if it is not a successful performer, the reward target It can also be a person.

  In addition, the reward amount condition can be provided with a condition that a predetermined amount is paid to a reward target person who is a successful performer. In addition, it is possible to make the total amount constant and condition that the reward target person who is a successful performer is equally distributed. It is also possible to set a condition such that the successful performer who returns the processing result earlier increases the reward amount. In the case where a processing result of a predetermined number of times or more is requested under individual conditions, if the reward is paid even if it is not a successful performer, the amount of reward can be made proportional to the number of times the processing result is transmitted. In this case, the amount per transaction can be a fixed amount or can be an amount obtained by multiplying the amount paid to the successful performer by a certain coefficient. Furthermore, the amount of reward for each transmission of the processing result can be defined so as to increase as the number of transmissions increases.

  Subsequently, characters and the like actually displayed on the execution device 3 are stored in the memo field. The memo field is a field for storing an arbitrary message that the requester wants to convey to the performer, for example, points to be noted when performing processing, explanation of remuneration, data indicating the purpose of the request, etc. Used to determine whether the performer receives a received request.

  In the server execution software field, for example, the requester does not need the processing result itself from the executor, that is, the raw data acquired by the execution device 3 and requests that the server device 2 perform some intermediate processing. In addition, server execution software for intermediate processing executed by the server device 2 is stored. For example, when the client needs only the average value and the variance value of the data obtained from each execution device 3, software for calculating the average value and the variance value is stored in the server execution software field. The execution software field stores software that needs to be executed by the execution device 3 when the request is executed. In this way, by using the server execution software, the requesting apparatus 1 can cause the server apparatus 2 to perform preprocessing, and can reduce the processing load on the requesting apparatus 1.

  Returning to FIG. 2, the request unit 11 of the requesting apparatus 1 transmits a request message and then shifts to a result acquisition waiting state. The feedback unit 12 transmits an evaluation value of the acquired result to the server device 2 after the result is acquired. The feedback process will be described later.

  The executor management unit 21 of the server device 2 has an executor database including an executor ID indicating the executor and executor information about the executor. Here, the executor information includes information about the executor and information about the executor 3 of the executor, and is used to determine an executor that matches the executor condition included in the request message. Specifically, the executor database, for each executor ID, information for accessing the executor 3 of the executor, for example, the telephone number, host name, IP address, etc. of the executor 3, and the executor Profile of age, gender, occupation, hobby, etc., current position received from the execution device 3 of the performer, and functions held by the execution device 3 of the performer, for example, presence or absence of a camera function Information indicating the type of sensor and the like, the past execution history of the performer, and the history of received rewards. For example, the execution history includes information indicating the number of times the executor has been requested, the number of times the executor has accepted the request, and the number of times the executor has completed the request and has become a successful executor. It is out. The reward history includes information on the total amount of rewards received so far and the rewards received at each request.

  Further, the executor management unit 21 further holds a feedback matrix. The feedback matrix is generated based on the evaluation value for each request transmitted by the feedback unit 12 of the client, and is used for ranking each performer. In other words, the executor management unit 21 determines the executor who makes the request from the feedback matrix when the executor that matches the executor condition is larger than the maximum number of persons that match the distribution number condition indicated by the distribution number field. Narrow down by person's ranking. In addition, the ranking process of performers by the feedback matrix will be described later.

  The requester management unit 22 holds a requester database for managing requesters. The requester database holds information about the requesting device 1 and request history of the requester for each requester ID. The request history includes, for each request, a request date and time, a request condition, a reward condition, a flag indicating whether or not the request is successful, and a reward amount determined for each performer.

  The processing unit 23 is for linking the request apparatus 1 and the execution apparatus 3 together. Specifically, when a request message is received from the request apparatus 1, the executor management unit 21 is inquired about an executor that matches the executor condition included in the request message. At this time, the processing unit 23 also notifies the executor management unit 21 of the distribution number condition. As described above, when the number of performers that match the performer condition is greater than the maximum value specified by the distribution number condition, the performer management unit 21 executes the number of executions equal to the number of distributions in descending order of rank of performers. The operator is selected, and the processing unit 23 is notified of the executor ID of the selected executor. When the number of performers that match the performer condition is less than the minimum value that satisfies the distribution number condition, the performer management unit 21 notifies the processing unit 23 to that effect.

  For example, when the distribution number condition included in the request message is 1000 to 2000 and the number of performers that match the performer condition is 500, the executer management unit 21 executes the execution that matches the executer condition. The processing unit 23 is notified that the number of persons is 500, which is smaller than the minimum number of 1000 that satisfies the distribution number condition. On the other hand, when the number of performers that match the performer condition is 1300, the performer management unit 21 notifies the processing unit 23 of the 1300 performer IDs. Further, when the number of performers that match the performer condition is 2500, the performer management unit 21 notifies the processing unit 23 of the top 2000 performer IDs of the 2500 performers. In addition, when receiving a notification from the executor management unit 21 that the number of executors that match the executor condition does not satisfy the distribution number condition, the processing unit 23 confirms that the number of distributions does not match the condition to the requesting device 1. And terminates the process.

  On the other hand, when the distribution number condition is satisfied, the processing unit 23 issues a session ID and associates and saves the session ID and the request ID included in the request message. Subsequently, the processing unit 23 transmits an execution request message to the execution device corresponding to the performer ID acquired from the performer management unit 21. As shown in FIG. 3B, the execution request message includes the session ID generated by the processing unit 23, the request condition, the reward condition, the memo, and the execution software included in the request message. If the server execution software is included in the request message in order to perform the intermediate processing in the server device 2, the server execution software is stored in association with the request ID.

  After the execution request message is distributed, the processing unit 23 waits for a processing result from each execution apparatus 3 as a distribution destination. Here, when a rejection message for rejecting execution of the requested process is received from the execution apparatus 3 that has transmitted the execution request message, the processing unit 23 rejects that the execution apparatus 3 has rejected the process, that is, does not accept it. Save things. Then, the execution device 3 that has not transmitted the rejection message treats it as having accepted the execution. However, only when an explicit acceptance message is received from the execution device 3, the execution device 3 may be treated as having accepted the request, and otherwise the execution may be rejected.

  The reception waiting state of the processing unit 23 continues until the transmission deadline indicated by the request condition. However, if a processing result that matches the request condition is received by the transmission deadline from each execution device 3 that has accepted the request, At this point, the reception wait state can be terminated. When the processing unit 23 receives the processing result from the execution device 3 in the reception waiting state, the processing unit 23 stores the received processing result. In addition, in the individual conditions of the request condition, for example, when a process execution interval is specified, it is determined whether or not the received process result matches this condition. Discard. When the transmission deadline indicated by the request condition expires, the server device determines the number of successful performers, and determines whether the request is successful by determining whether the number of successful performers is equal to or greater than the minimum number of successful performers. judge.

  When the request is successful and the intermediate processing in the server device 2 is necessary, the processing unit 23 performs processing by the server execution software and transmits the intermediate processing result to the requesting device 1. On the other hand, when the intermediate process is not necessary, the processing unit 23 transmits the processing result from the execution apparatus 3 corresponding to the successful performer to the request apparatus 1 as it is. Successful execution is required when paying a remuneration according to the number of times to the executor who requested the processing result more than a predetermined number of times under individual conditions and sent the transmission result to the server device 2 even once within the time limit. The processing result from the executor is transmitted to the requesting apparatus 1 even if it is not a person. That is, the processing unit 23 transmits the processing result from the performer who is the target of receiving the reward to the requesting device 1, and transmits the processing result from the performer who is not the target of receiving the reward to the requesting device 1. Do not perform.

  In the above embodiment, the server device 2 stores the processing results received from the execution devices 3 and transmits them to the requesting device 1 in a lump after the transmission deadline. However, when the processing result is received from the execution device 3, if it is already determined that a reward for the processing result is generated, the received processing result can be transmitted to the requesting device 1 as it is. For example, when the minimum number of successful performers is 1 and the individual condition is not specified, the success of the request is confirmed by receiving the first processing result, so that intermediate processing using a plurality of processing results in the server device 2 Is not necessary, the treatment unit 23 can transmit the processing result to the requesting apparatus 1 as it is. Furthermore, even when the individual condition is specified, when the performer who has transmitted the processing result even once within the time limit is set as the reward receiving target in the remuneration target person condition, the treatment unit 21 performs the processing result as it is. Can be transmitted to the requesting apparatus 1.

  In any case, the processing unit 23 transmits only the processing result from the performer who is the target of receiving the reward to the requesting device 1 or as an input of an intermediate process to be transmitted to the requesting device 1. Thereafter, the processing unit 23 determines the amount of reward for the person receiving the reward based on the reward condition, notifies the performer management unit 21 and the requester management unit 22 of necessary information, and executes the performer database and the requester database. Let each of you update. For each request, the remuneration paid by the client to each performer and the remuneration received by each performer are recorded in the performer database and the requester database, respectively, and recorded in the performer database and the requester database. The actual payment process is performed based on the contents. Note that the payment processing from the requester to the performer for the determined remuneration amount can be performed by an arbitrary method. Thus, in the present embodiment, the server device 2 mediates between the request device 1 and the execution device 3, and the processing unit 23 performs the request based on the request condition and the reward condition included in the request message from the request device 1. Determine the amount of remuneration that a person should pay to each performer. Normally, the server device 2 is installed and operated by, for example, a network operator or a provider providing the service. That is, since these operators or business operators determine and record the remuneration amount, it is possible to reduce problems that may occur in the processing related to the remuneration amount and payment between the client and the performer.

  Subsequently, when receiving the execution request message from the server, the execution unit 31 of the execution device 3 displays on the display that the execution request message has been received and prompts the user to select whether or not to accept the request. At this time, the reward information and the information stored in the memo field are also displayed on the display. When the user performs an operation of accepting the request, the execution unit 31 executes the execution software included in the execution request message. When the request is rejected, a reject message is transmitted to the server device 2. For example, in the case of a request to periodically measure the temperature and position, the execution software measures the position and temperature at a predetermined period and transmits to the server device 2. When the requested process is a predetermined calculation process, the execution software performs the predetermined calculation process.

  Note that execution of the requested processing in the execution unit 31 is performed by a performer such as taking a still image or a moving image, even if it is a process that does not require an operator's operation, such as temperature acquisition or predetermined calculation processing. It may be a process that requires an operation. For example, in the case of a still image shooting process, the execution software may add information such as a shooting position and a shooting direction from the position to the shot image.

  The registration unit 32 of the execution device 3 periodically transmits the position of the execution device 3 to the server device 2 and corrects the profile information and the like of the executor in the executor database held by the server device 2 It is a block.

  Next, feedback processing in the present embodiment will be described. When the processing unit 23 of the server device 2 transmits the processing result or the intermediate processing result to the requesting device 1, the processing unit 23 acquires the processing device that acquired the processing result or the processing result that is the basis of the intermediate processing result. Instead of the executor ID of the execution device 3, the processing unit 23 notifies the requesting device 1 of a temporary executor ID that is a temporary identifier of the executor generated each time. This is to conceal the executor who acquired the individual processing results from the requesting apparatus 1. Therefore, the processing unit 23 stores the relationship between the executor ID and the temporary executor ID. The requester of the requesting device 1 that has received the processing result inputs an evaluation value for the processing result or the intermediate processing result, and the feedback unit 12 of the requesting device 1 sends the evaluation value and the temporary performer ID of the processing result to the server device 2. Send to. The evaluation value is, for example, the highest value in the range of −1 to +1. When the client does not evaluate, the feedback unit 11 automatically transmits a central value, for example, 0 as an evaluation value when the evaluation value is in the range of −1 to +1. be able to. In addition, about the evaluation value of the executor who did not evaluate the requester and did not transmit the evaluation value to the server device 2, the processing unit 23 of the server device 2 uses the evaluation value of the executor as a central value. It may be a form.

  For example, in a request to measure the outside air temperature at a specific time 10 times or more, at the measurement time, the execution device 3 is requested to be exposed to the outside air in the memo field, and 12 processing results are received. To do. However, for example, in the case where several measurement results out of twelve measurement results seem to be measured indoors, the requester can provide feedback with a lower evaluation of the performer. .

The processing unit 23 converts the temporary executor ID included in the evaluation value received from the requesting device 1 into an executor ID, and outputs it to the executor management unit 21 together with the evaluation value. The performer management unit 21 holds the feedback matrix shown in FIG. The feedback matrix is a matrix indicating the total evaluation value, which is the average of the evaluation values of the requester to the performer, for each combination of each requester and each performer. 4, for example, the requester ID is #j requester, the overall evaluation value invoker's ID is the practitioner is #i is F _ij. For example, when the performer management unit 21 receives the value X as an evaluation value for the performer with the performer ID #i from the requester with the requester ID #j for the new request, Update the value in column j to (F _ij + X) / L. Here, L is the number of evaluations of the requester whose requester ID is #j to the performer whose performer ID is #i. For example, when the evaluation value of the intermediate processing result generated from the processing results from three performers is Y, the evaluation value of each performer is updated as Y / 3. However, the evaluation value of each performer may be Y.

  The executor management unit 21 generates an evaluation rank for each executor based on the feedback matrix. The concept of ranking is not to place an emphasis on the evaluation of clients who perform extremely biased evaluations, but to place an emphasis on the evaluation of performers who have a high average evaluation and little variation. This will be described in detail.

First, each column vector of the feedback matrix indicates a comprehensive evaluation value for each performer of the corresponding client. Therefore, as shown in FIG. 5, an average evaluation value A that is an average value of each element of the column vector is obtained for each client. For example, evaluation average value A ₁ of the requester ID is # 1 requester is the average value of each element of the first row of the feedback matrix of FIG. Subsequently, as shown in FIG. 5, an evaluation variance V is obtained for each client. For example, the evaluation variance V ₁ of the client whose client ID is # 1 is the variance of each element in the first column of the feedback matrix in FIG. Subsequently, as shown in FIG. 5, an evaluation standard deviation S is obtained for each client. For example, the evaluation standard deviation S ₁ Requester ID is # 1 requester is the square root of the evaluation dispersion V ₁ of the same requester.

Finally, a deviation matrix D is obtained from the average evaluation value A and the evaluation standard deviation S shown in FIG. Here, the value D _ij of the element of i row j column of the deviation matrix D is
D _ij = | (F _ij −A _j ) / (S _j × S _max ) |
It is. Here, S _max is a predetermined coefficient for adjusting the value of D _ij . _In the case _{where D ij} is greater than _1, and 1 _{D ij.}

Subsequently, the executor management unit 21 obtains the final evaluation value E of each executor from the values of the elements of the deviation matrix D and the feedback matrix F. For example, the final evaluation value E _i of the executor whose executor ID is #i is a coefficient obtained from the element corresponding to the executor of the deviation matrix for each comprehensive evaluation value of the executor (1-D _ik ) multiplied by
E _i = (1 / n) Σ (F _ik × (1−D _ik ))
It becomes. Here, n is the number of clients, and Σ in the above equation represents the integration from k = 1 to n. The executor management unit 21 assumes that an executor with a higher final evaluation value E has a higher evaluation, and the executor that matches the executor condition is equal to or greater than the maximum number of distributions determined by the distribution number condition. Select performers for distribution in descending order of evaluation.

  As described above, the requester can request the performer who is not acquainted to execute the process. In addition, by specifying various reward conditions, an incentive for the performer to execute the process occurs. Note that it is possible to control the transmission of only the processing result to be paid to the requesting device 1 through the mediation of the server device 2. Further, the mediation of the server device 2 makes it difficult for a problem related to receiving a reward to occur, and the executor can accept the process with peace of mind. In addition, by ranking the performers using the evaluation value, it is possible to make a request for processing in preference to the performer who performs appropriate processing.

  The server device according to the present invention can be realized by a program that causes a computer to operate as the server device described above. These computer programs can be stored in a computer-readable storage medium or distributed via a network.

Claims (10)

A server device,
For each executor, executor management means for holding a database containing executor information and executor identifiers used to select the executor;
Information indicating an executioner condition for selecting an executor from the requesting device, information indicating a distribution number condition that is a condition for the number of distributions of a request, information indicating a remuneration condition that is a payment condition for a request for processing, and When a request message including execution software to be executed by the execution device for the requested processing is received, an identifier of the performer corresponding to the performer information that matches the executer condition is received from the executer management unit. Processing means for acquiring a number matching the condition, and performing processing for transmitting an execution request message including the information indicating the reward condition and the execution software to the execution device of the performer corresponding to the acquired identifier;
Equipped with a,
When the request message includes server execution software to be executed by the server device, the processing means obtains an intermediate processing result obtained by processing the processing result received from the execution device by the server execution software. To
When the server execution software is not included in the request message, the processing unit transmits the processing result received from the execution device to the requesting device. The request message includes a message to be displayed on the performer device,
The processing means includes a message to be displayed on the performer device in the execution request message.
The server device according to claim 1. The reward condition further includes a condition for becoming a person who receives a reward for the requested process,
In response to the transmission of the execution request message, the processing means determines whether or not an executor corresponding to the execution device that has transmitted a processing result to the server device is a recipient of a reward according to the reward condition. Judging according to
The server device according to claim 1 or 2. The processing means transmits the processing result received from the execution device of the performer who is the recipient of the reward or the intermediate processing result obtained from the processing result to the request device, and the execution is not the recipient of the reward The processing result received from the execution device of the person is not transmitted to the requesting device, and is not used to obtain the intermediate processing result.
The server device according to claim 3 . The processing means corresponds to the execution device that transmitted the processing result or the execution device that transmitted the processing result that is the basis of the intermediate processing result when transmitting the processing result or the intermediate processing result to the requesting device. Generating a temporary identifier of the performer, and transmitting the generated temporary identifier together with the processing result or the intermediate processing result to the requesting device;
The server device according to claim 4 . When the processing means receives the evaluation result indicating the evaluation of the processing result or the intermediate processing result together with the temporary identifier from the requesting device after transmitting the processing result or the intermediate processing result to the requesting device, Notifying the executor management means of the identifier of the executor corresponding to the temporary identifier, information indicating the requesting device, and the received evaluation value,
The executor management unit holds a comprehensive evaluation value for each executor of each requester, and an execution corresponding to the notified identifier of a requester corresponding to the requesting device notified from the processing unit Updating the overall evaluation value of the person using the notified evaluation value,
The server device according to claim 5 . The executor management means holds a comprehensive evaluation value for each executor of each client, calculates the rank of each executor based on the total evaluation value for each executor of each client, and executes the execution If the number of performers corresponding to the performer information that matches the performer condition is greater than the maximum number of distributions that satisfy the distribution number condition, the rank of the performers corresponding to the performer information that meets the performer condition The processing means is notified of the number of performer identifiers equal to the maximum number of distributions satisfying the distribution number condition in descending order of the distribution number,
The server device according to any one of claims 1 to 6 . The executor management means calculates a final evaluation value for the executor by multiplying each total evaluation value for the executor by a coefficient and adds up, and calculates a rank of each executor in descending order of the calculated final evaluation value. ,
The coefficient is determined according to the requester, and is a value that decreases as the standard deviation of the overall evaluation value for each performer of the requester decreases.
The server device according to claim 7 . When the number of performers corresponding to the performer information that matches the performer condition is less than the minimum value that satisfies the distribution number condition, the processing means executes execution corresponding to the performer information that meets the performer condition The requesting device is notified that the number of users is less than a minimum value satisfying the distribution number condition;
The server device according to any one of claims 1 to 8 . Program for causing a computer to function as a server device according to any one of claims 1 to 9.

Images