JP2009076066A - Translation request management method, translation request management device, and translation request management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a translation request management method, a translation request management device and a translation request management program reducing a burden of payment concerning a translation request of a translation client. <P>SOLUTION: The translation client accesses a management server 1 and requests translation. The management server 1 transmits e-mail for requesting a translator of the translation and charges the client for the translation. The translator submits a translated result to the management server 1. The management server 1, upon accepting the translated result, pays the translator for the translation. A secondary user making use of the translated result other than the translation client accesses the management server 1 and receives the translated result. The management server 1 charges the secondary user for the use. The management server 1 pays a predetermined percentage of the fee for the usage of the translated result to the translation client as a return and also pays the predetermined percentage of the fee to the translator as secondary pay. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a translation request management method, a translation request management apparatus, and a translation request management program. More specifically, the present invention relates to a translation request management method, a translation request management apparatus, and a translation request management program that reduce the burden of payment related to a translation request of a translation client.

  Conventionally, various contents are disclosed on a network such as the Internet. These contents are created in various languages. Therefore, translation is required when it is desired to use content written in a language that the user cannot understand. In such a case, the user may have a person (translator) who understands both the language of the content and the language understandable by the user translate it or perform machine translation using translation software. Can do.

  However, with machine translation, there is a problem that the subtle meanings of words cannot be fully translated and the attractiveness of content cannot be fully conveyed. On the other hand, in the case of translation by a translator, there is a problem that it takes time to obtain a translation result and a translation fee to be paid to the translator is required. Therefore, for example, in Patent Document 1, in response to a translation request from a user computer used by a user, first, machine translated content obtained by machine translation is presented, and then translation by a translator is performed. A translation service system that replaces machine translated content with translated content by a translator is disclosed.

Japanese Patent Laid-Open No. 2003-6455

  However, in the above-described conventional translation service system, the translation fee generated for translation by a translator is not taken into consideration. That is, when actually requesting a translator to translate, there is a problem that a user cannot easily request a translation because a great translation fee is generated.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a translation request management method, a translation request management apparatus, and a translation request management program that reduce the burden of payment related to a translation request of a translation client.

  In order to solve the above problem, the translation request management method of the invention according to claim 1 is a translation request management method processed by a translation request management apparatus connectable to a network, and the translation request management via the network A request reception step for receiving request information, which is information related to a content translation request, output from a user device connected to the device via the network, and the content indicated by the request information received in the request reception step A translation requesting step for requesting a translator to translate the content, a translation reward determining step for determining a translation reward that is a reward paid to the translator for the translation of the content, and the translation reward determining step Based on the translation fee, the request as a fee required for the translation of the content A translation fee determining step for determining a translation fee to be charged to a translation requester who has operated the user device that has output the request information received in the appending step; and a translation fee requesting step for charging the translation request to the translation requester. A translation result receiving step for receiving a translation result by the translator requested for translation in the translation request step, and the translation result received in the translation result receiving step, provided in the translation request management device, A translation result storage step that is stored in a translation result storage means that can be disclosed on the network; and a reduction reward determination step that determines a reduction reward that is a reward paid to the translation requester in order to reduce a part of the translation fee; A secondary user using the translation result stored in the translation result storage means. And a usage billing step to charge, the usage fee, wherein the is the amount of over-reduction compensation.

  The translation request management method of the invention according to claim 2 is a secondary determination method for determining a secondary reward that is a reward paid to the translator for use of the translation result in addition to the configuration of the invention of claim 1. A reward determining step, wherein the usage fee is equal to or greater than a total amount of the return reward and the secondary reward.

  In the translation request management method of the invention according to claim 3, in addition to the configuration of the invention according to claim 1 or 2, the request information includes location information indicating a storage location of the content on the network, The translation request management device comprises location information storage means for storing the location information, and original text storage means for storing the original text of the content acquired from the location indicated by the location information as an acquired original text, the request receiving step Past request determination step for determining whether or not the request for translation of the content has been received, depending on whether or not the location information included in the request information received in the step is stored in the location information storage means And the content stored in the location indicated by the location information included in the request information received in the request reception step. A change determination step for determining whether or not a sentence and the acquired original sentence stored in the original sentence storage means are the same, and the change determination step determines that the original sentence and the acquired original sentence are not the same In this case, a translation instruction is requested from the user device through the network, and a translation request is requested from the translator in the translation request step. An original text storage step of storing the original text of the content stored in the location indicated by the location information as the acquired original text in the original text storage means, and the translation request step includes the continuation instruction reception step. When an instruction to continue the translation request is received in the previous request determination step and the previous request determination step, If it is determined that there is never received translation request Ntsu, characterized in that a request for translation to the translator.

  In the translation request management method of the invention according to claim 4, in addition to the configuration of the invention according to any one of claims 1 to 3, the translation fee is used for the usage fee charged in the usage fee billing step. And a usage fee determination step for determining the usage fee based on at least one of the total number of the usage fees collected during the first predetermined period.

  In the translation request management method of the invention according to claim 5, in addition to the configuration of the invention according to any one of claims 1 to 4, in the reduction reward determination step, the usage fee collected during the second predetermined period is included. Multiplying a total amount by a predetermined ratio to determine the return reward, based on the number of times the translation result is used, and at least one of the total amount of the usage fee collected in a third predetermined period, The method further comprises a ratio changing step for changing the predetermined ratio.

  In the translation request management method of the invention according to claim 6, in addition to the configuration of the invention according to any one of claims 1 to 5, the request reception step includes at least information on the return reward for the translation indicated by the request information. A translation information output step for outputting translation information to the user device via the network, and an instruction for confirming a request for translation of the content after the translation information is output in the translation information output step, A request confirmation receiving step for receiving from the user device via the network, and in the translation request step, when an instruction to confirm the request for translation is received in the request confirmation receiving step, the translator is translated. It is characterized by requesting.

  The translation request management apparatus according to the invention of claim 7 is a translation request management apparatus connectable to a network, and translates content output from a user apparatus connected to the translation request management apparatus via the network Request accepting means for accepting request information, which is information related to the request, via the network; translation request means for requesting a translator to translate the content indicated by the request information accepted by the request accepting means; and the content As a fee required for translation of the content based on the translation reward determined by the translation reward determination means and a translation reward determination means for determining a translation reward that is a reward paid to the translator for The user device that has output the request information received by the request receiving means is operated. A translation fee determining means for determining a translation fee to be charged to the requester, a translation fee requesting means for charging the translation requester to the translation requester, and a translation result by the translator requested to translate by the translation requesting means. A translation result receiving unit for receiving, a translation result storing unit for storing the translation result received in the translation result receiving unit so as to be openable on the network, and the translation requester for reducing a part of the translation fee. A reduction reward determining means for determining a reduction reward that is a reward to be paid, and a usage charge requesting means for charging a usage fee to a secondary user using the translation result stored in the translation result storage means. The usage fee is an amount equal to or more than the return reward.

  According to an eighth aspect of the present invention, a translation request management program causes a computer to execute various processing steps of the translation request management method according to any one of the first to sixth aspects.

  In the translation request management method of the invention according to claim 1, the translation requester pays a translation fee when making a translation request, and the translator is paid a translation fee. When the translation result is used by a secondary user, a reduction reward is paid to the translation requester. Therefore, the translation requester can obtain a reduction fee as the translation result of the translation requested by him / her is used secondarily. As a result, the cost of the translation requester's translation request is reduced. It is reduced. If a lot of secondary usage occurs, the cumulative amount of reduction fees will exceed the translation fee and bring benefits to the translation requester, so the translation requester will make an initial investment (the time it takes to obtain the translation fee and translation result) ).

  Further, in the translation request management method of the invention according to claim 2, in addition to the effect of the invention of claim 1, when the translation result is secondarily used, it is secondary to the translator who created the translation result. A reward is paid. Therefore, the more the translation result is used secondarily, the more profitable the translator can be.

  Further, in the translation request management method of the invention according to claim 3, in addition to the effect of the invention according to claim 1 or 2, if a content translation request has already been made, the current original text and the past The acquired original text, which is the original text acquired at the time when the translation request was made, is compared. Then, when the current original text is changed from the acquired original text, the translation requester can specify whether to continue the translation request or cancel the translation request. Therefore, the translation requester can cancel the translation request if it is enough to refer to the past translation even if there is a change in the already translated content. You don't pay a translation fee. Also, if there is a change in the already translated content, if you want to translate again, you can continue to request translation and obtain new translation results. Therefore, the translation requester can obtain a translation result with the latest content.

  In addition, in the translation request management method of the invention according to claim 4, in addition to the effect of the invention according to any one of claims 1 to 3, collection is performed at the number of times the translation result is referred to and the first predetermined period. Based on at least one of the total amount of the usage fees, the usage fee for secondary use of the translation result can be determined. Therefore, it is possible to determine the usage fee by grasping the income state of the usage fee due to secondary use of the translation result. Therefore, it is possible to set the usage fee to be lower when the secondary usage progresses with respect to the usage fee when the number of secondary usages is small. Thereby, further secondary utilization can be promoted. In addition, if secondary usage progresses, the usage fee can be set higher. Thereby, a profit can be increased.

  Further, in the translation request management method of the invention according to claim 5, in addition to the effect of the invention according to any one of claims 1 to 4, collection is performed at the number of times the translation result is referred to and a third predetermined period. The ratio for determining the return reward can be changed based on at least one of the total amount of the usage fees. Therefore, the predetermined ratio for determining the return reward can be changed according to the income state by secondary use of the translation result. For example, when the secondary use of the translation result progresses, the ratio can be changed so as to decrease. In this case, since the collection of the translation fee paid to the translator is also progressing, the burden on the translator is not increased even if the predetermined ratio is lowered and the reduction fee to the translator is reduced. Also, if secondary use of translation results progresses, the burden on the translation requester can be further reduced by increasing the ratio and increasing the return reward to the translation requester.

  In addition, in the translation request management method of the invention according to claim 6, in addition to the effect of the invention according to any one of claims 1 to 5, the translation requester includes at least a reduction reward when making a translation request Information is output and then the translation request can be confirmed. Therefore, the translation requester can determine whether or not to request translation using the translation information as a determination material.

  In the translation request management apparatus of the invention according to claim 7, the translation requester pays a translation fee when making a translation request, and the translator is paid a translation fee. When the translation result is used by a secondary user, a reduction reward is paid to the translation requester. Therefore, the translation requester can obtain a reduction fee as the translation result of the translation requested by him / her is used secondarily. As a result, the cost of the translation requester's translation request is reduced. It is reduced. If a lot of secondary usage occurs, the cumulative amount of reduction fees will exceed the translation fee and bring benefits to the translation requester, so the translation requester will make an initial investment (the time it takes to obtain the translation fee and translation result) ).

  Further, in the translation request management program of the invention according to claim 8, any one of claims 1 to 6 is performed by causing a computer to execute various processing steps of the translation request management method according to any one of claims 1 to 6. The effect similar to the effect of invention described in 1 can be show | played.

  Embodiments of a translation request management system using the translation request management method of the present invention will be described below with reference to the drawings. First, an overview of the translation request management system of the present embodiment will be described with reference to FIG. 1 and FIG. FIG. 1 is a schematic diagram illustrating a configuration of an apparatus used in the translation request management system, and FIG. 2 is a schematic diagram illustrating a processing procedure in translation request and translation result use. A schematic configuration of the translation request management system will be described with reference to FIG. As shown in FIG. 1, in the present embodiment, a management server 1, a client client 2, a translator client 3, a secondary user client 4, and a Web server 5 are connected to the Internet 7.

  The requester client 2 is an apparatus used by a translation requester who is a person who requests translation. The translator client 3 is an apparatus used by a translator who is a translator. The secondary user client 4 is a device used by a person who uses the translation result translated by the translator (hereinafter referred to as a secondary user).

  The management server 1 is a device that manages translation requests, charges various fees associated with translation requests, pays rewards, manages translation results, charges various fees associated with secondary use of translation results, and pays rewards. The management server 1 includes a translation result database (DB) 1551 that stores translation results, and a request DB 1531 that stores information on translation requests and the use status of translation results. The Web server 5 stores a Web page 51 that is published on the Internet 7. The management server 1 is connected to a credit company management computer 6 via a network 8. The network 8 may be a dedicated network constructed using a telephone line or an optical fiber, or may be the Internet 7.

  Next, a rough procedure at the time of requesting translation will be described with reference to FIG. In FIG. 2, the process indicated by the solid line arrow is the process performed at the time of requesting translation. First, a translation requester who requests translation (hereinafter simply referred to as a requester) operates the requester client 2 to access the management server 1 to request a translation (translation request screen 201, FIG. 14). The requester specifies the URI of the Web page for which translation is requested and requests translation. Then, the management server 1 determines the translation fee, and after confirming the requester, transmits an e-mail requesting the translator to translate.

  The management server 1 charges the requester for a translation fee, which is a fee required for translating the Web page. In the present embodiment, the management server 1 creates data for requesting payment collection from the client, and transmits the data to the credit company management computer 6. The management server 1 receives a translation fee from the client. Actually, the credit company collects the translation fee from the client's contracted bank account and pays the person who manages the management server 1. The translation fee can be used, for example, as a funding source for a translation reward to a translator described later.

  The translator submits the translation result to the management server 1 after performing the translation. In the present embodiment, the translator transmits the translation result data to the management server 1 via the Internet 7. When the management server 1 accepts the translation result, the management server 1 pays the translator a translation reward, which is a reward for the translation performed in response to the request by the translator. In the present embodiment, the management server 1 transfers the amount of translation reward to the bank account reported by the translator.

  Next, with reference to FIG. 2, a rough procedure when the translation result is used by another user (secondary user) will be described. A process indicated by a dotted line in FIG. 2 is a process performed at the time of secondary use. First, the secondary user operates the secondary user client 4 to access the management server 1 and receive a translation result. The management server 1 charges the secondary user for a usage fee that is a fee for using the translation result. In the present embodiment, the management server 1 collects a usage fee using a credit company in the same manner as the collection of the translation fee from the client. That is, the management server 1 creates data for a request for collecting a price from a secondary user, and transmits the data to the credit company management computer 6. Then, the credit company collects the usage fee from the contract bank account of the secondary user and pays it to the person who manages the management server 1.

  In this embodiment, when the translation result is secondarily used, the management server 1 pays a requester and a translator. The fee collected from the secondary user is applied to the funds for the reward. Specifically, the management server 1 calculates a return reward, which is a reward paid to the client in order to return a part of the translation fee paid by the client, and sends it to the bank account reported by the client. Transfer reduction reward. In addition, the management server 1 calculates a secondary reward, which is a reward paid to the translator regarding the use of the translation result created by the translator, and pays the secondary reward to the bank account reported by the translator.

  Next, the management server 1 will be described with reference to FIGS. FIG. 3 is a block diagram showing an electrical configuration of the management server 1. 4 is a schematic diagram showing a configuration of the translator information storage area 151 provided in the HDD 15 of the management server 1. FIG. 5 shows a client information storage area provided in the HDD 15 of the management server 1. FIG. 6 is a schematic diagram illustrating a configuration of a request DB storage area 153 provided in the HDD 15 of the management server 1.

  First, the electrical configuration of the management server 1 will be described with reference to FIG. As shown in FIG. 3, the management server 1 includes a CPU 10 that controls the management server 1. Connected to the CPU 10 are a RAM 11 for temporarily storing various data, a ROM 12 for storing BIOS and the like, and an I / O interface 14 for mediating data transfer. A hard disk device 15 is connected to the I / O interface 14. The hard disk device 15 includes a translator information storage area 151, a requester information storage area 152, a request DB storage area 153, a source text storage area 154, a translation result storage area 155, a program storage area 156, and other An information storage area 157 is provided at least.

  In the translator information storage area 151, information relating to translators is stored. The requester information storage area 152 stores information about the requester. In the request DB storage area 153, a request DB 1531 is stored. The original text storage area 154 stores the original text of the Web page requested for translation. The translation result storage area 155 stores a translation result DB 1551 (see FIG. 1). The program storage area 156 stores a program executed by the CPU 10. The other information storage area 157 stores other information used by the management server 1 such as a screen form to be displayed on the browser screen of the clients 2, 3, 4.

A mouse controller 18, a video controller 16, a key controller 17, and a communication device 19 are connected to the I / O interface 14. A mouse 181 is connected to the mouse controller 18. A display 161 is connected to the video controller 16. A keyboard 171 is connected to the key controller 17. The communication device 19 can be connected to the Internet 7 and the network 8.

  Next, the translator information storage area 151 will be described with reference to FIG. As shown in FIG. 4, the translator information storage area 151 is provided with at least a number field, a name field, an address field, a transfer account field, a contact field, and a language field. In the number column, a number (translator number) for identifying a translator is stored. The name column stores the name of the translator, and the address column stores the address of the translator. In the transfer account column, information on a bank account into which a translation fee or a secondary fee paid to the translator is transferred is stored. The contact address field stores the contact information for the translator. In the language column, languages that can be translated by the translator are stored. In the example shown in FIG. 4, the translator “Hanako Ito” with the number “T1” understands Japanese and English, so he can translate from Japanese to English and from English to Japanese. It has been shown that it can.

  Next, the client information storage area 152 will be described with reference to FIG. As shown in FIG. 5, the client information storage area 152 is provided with at least a number field, a name field, an address field, a transfer account field, and a contact address field. In the number column, a number (requester number) for identifying the requester is stored. The name field stores the name of the client, and the address field stores the address of the client. In the transfer account column, information of a bank account into which a reduction fee paid to the client is transferred is stored. The contact address field stores a contact address to the requester.

  Next, the request DB storage area 153 will be described with reference to FIG. As shown in FIG. 6, the request DB 1531 stored in the request DB storage area 153 includes a request number field, a requester number field, a translator number field, a request URI field, a language field, an original URI field, and a translation result URI. Column, translation fee column, usage fee column, usage count column, cumulative count column, other contact address column, request date column, and translation date column are provided.

  In the request number column, a request number that is a number for identifying one request is stored. The requester number column stores the requester number of the requester who made the request. In the translator number column, the translator number of the translator who performed the translation is stored. In the request URI column, a URI (hereinafter referred to as “request URI”) of a Web page requested to be translated (hereinafter referred to as “request content”) is stored. In the language column, a value indicating which language is requested to be translated is stored. In the original text URI column, information (URI) indicating the location where the original text at the time of translation is stored is stored. In the translation result URI column, information (URI) indicating the location where the translation result is stored is stored. A translation fee paid by the client for this translation is stored in the translation fee column. In this embodiment, it is assumed that the translation fee paid to the translator is the same as the translation fee. Therefore, the amount stored in the translation fee box means a translation reward.

  The usage fee column stores a usage fee charged to the secondary user at the time of secondary usage. The number of times of use of the translation result during the predetermined period is stored in the number-of-uses column. In the present embodiment, it is assumed that the predetermined period is one month. The total number of times of secondary use since the translation result is registered is stored in the total number of times column. In the other contact field, after the request for translation, until the translation result is registered, that is, during translation, when a translation request to the same language is made for the same Web page, the request is made later. The contact information of the client who made the request is stored. In the request date column, the date when the translation request is received by the management server 1 is stored. In the translation date column, the date when the translation result is registered in the translation result DB 1551 is stored.

  In the example shown in FIG. 6, the translation request with the request number “1” is a request from the requester with the requester number “R1” for the Web page with the request URI “http / www.bbb.co.jp”. In response to this request, translation is performed by a translator having a translator number “T2”. The original text at the time of translation is stored in “http / www.bbb.co.jp / A1.html”, and the translation result is “http / www.bbb.co.jp / B1.html”. Is stored. The translation fee is 50,000 yen and the usage fee is 500 yen. The number of uses in this period is 50 times, and the cumulative number of uses since the translation result is registered is 263 times. The request date is June 27, 2007, and the translation date is July 1, 2007.

  Next, a translation request process performed at the time of a translation request will be described with reference to the flowcharts of FIGS. FIG. 7 is a flowchart of the translation request process, and FIG. 8 is a flowchart of the request execution process executed in the translation request process. FIG. 9 is a flowchart of the secondary usage process executed in the translation request process. The translation request process is a process performed when the translation request management program executed by the CPU 10 of the management server 1 receives an http request for requesting display of the translation request screen 201 (see FIG. 14) from the client client 2. It is.

  As shown in FIG. 7, the CPU 10 of the management server 1 first displays the translation request screen 201 on the client client 2 (S1). The translation request screen 201 is a screen displayed in a display area of a display window displayed by so-called browser software. Specifically, information for displaying the translation request screen 201 is transmitted to the requester client 2 as a response to the http request from the requester client 2. As shown in FIG. 14, the translation request screen 201 includes, for example, a URI input field for inputting the URI of a Web page that the client wants to request translation, a language list box field for selecting which language to translate, and an OK button. Is provided.

  A process for accepting a URI input is performed (S2). When the requester inputs a URI on the translation request screen 201, selects a language and presses an OK button, the requester client 2 transmits an http request describing the input URI. In the management server 1, the URI and language are stored in a requested URI storage area (not shown) and a language storage area (not shown) of the RAM 11.

  Next, it is determined whether or not a request for translating the accepted Web page of the URI into the selected language (hereinafter referred to as “designated language”) has been made (S3). If the request URI is stored in the request URI column of the request DB 1531 and there is an entry in which the specified language is stored in the language column, it is determined that translation of the Web page of the URI has been requested (S3: YES). ). On the other hand, if there is no entry in the request DB 1531 that stores the same request URI and specified language, the request is not made (S3: NO). Therefore, a translation reward calculation process is performed (S4). Specifically, the translation reward for the requested content is determined based on a predetermined rule and stored in a predetermined storage area of the RAM 11.

  The translation reward may be determined based on, for example, the number of characters and the number of lines in the translated content. In addition, depending on the level of difficulty and expertise of the contents described in the requested content, the translation reward may be set high for highly difficult content or highly specialized content. In the present embodiment, the system administrator collects a fee equivalent to the translation fee paid to the translator as a translation fee from the client. The translation fee is a fee paid by the client. Therefore, here, the translation fee is calculated and determined, but the translation fee is also determined.

A request confirmation screen 202 (see FIG. 15) is displayed on the requester client 2 (S41). The request confirmation screen 202 describes at least the translation fee stored in a predetermined storage area of the RAM 11, and is a screen for allowing the client to finally confirm whether or not to request a translation with this translation fee. is there. As shown in FIG. 15, the request confirmation screen 202 is provided with an OK button and a cancel button. In addition to the translation fee, the request confirmation screen 202 may include, for example, the scheduled delivery date of the translation result and the amount of money that the requester can obtain as a return reward. When the reduction reward is described, the requester can determine whether or not to request translation using this information as a determination material.

  Next, confirmation result acceptance processing is performed (S42). When the requester client 2 selects the OK button by the client, information indicating that the request is confirmed is transmitted to the management server 1. When the cancel button is selected, information indicating that the request is canceled is displayed on the management server 1. Sent to. In the management server 1, these pieces of information are stored in a predetermined storage area of the RAM 11. It is determined whether or not the client client 2 has selected to confirm the translation request (S43). When the OK button has been pressed and the management server 1 has received information to confirm the request, a request execution process is performed (S44, see FIG. 8).

  In the request execution process, as shown in FIG. 8, first, a personal information input screen (not shown) is displayed on the client client 2 (S51). The personal information input screen is a screen for allowing the client to input information for collecting a translation fee. In the personal information input screen, the requester number input field, address input field, transfer account input field, contact input field, name input field, credit card type selection field, credit card number input field, credit card expiration date input field, and At least an OK button is provided. The address input field, transfer account input field, and contact address input field are used for registering requester information in the management server 1 as a requester when a person who is not registered in the management server 1 as a requester makes a translation request. It is an input field. A requester who has already been registered as a requester only needs to input the requester number.

  Next, a reception process of personal information input on the personal information input screen is performed (S52). When an OK button is selected by the client in the client client 2, information input in each input field is transmitted to the management server 1. The received information is stored in a predetermined storage area of the RAM 11. When the client number is not input, the client information is added to the client information stored in the client information storage area 152. Specifically, the client number is assigned and stored in the number field of the client information storage area 152. Also, the received address, transfer account, and name information are stored in the address column, transfer account column, and name column, respectively. The client number entered in the client number input field on the personal information input screen or the assigned client number is stored in the client number storage area (not shown) of the RAM 11.

  Translation fee billing processing is performed (S53). Specifically, the credit card type management computer 6 of the credit card type entered on the personal information input screen stores the credit card number, the credit card expiration date, and the name card in the translation fee storage area of the RAM 11. Information that charges the amount of money is sent.

  The web page of the request URI is acquired and stored in the original text storage area 154 (S54). Next, the translation request entry is stored in the request DB 1531 (S55). Specifically, a request number is assigned and stored in the request number column. The client number stored in the client number storage area of the RAM 11 is stored in the client number column. The amount stored in the translation fee storage area of the RAM 11 is stored in the translation fee column. In the original text URI column, a URI indicating the original text stored in S54 is stored. The URI stored in the request URI storage area of the RAM 11 is stored in the request URI column. The language stored in the language storage area of the RAM 11 is stored in the language column. The usage fee is determined, and the usage fee is stored in the usage fee column.

  The usage fee may be determined according to the translation fee or the translation fee, or may be determined according to the number of characters or the number of lines of the requested content. The usage fee may be a uniform fee for any content. Further, the usage fee may be determined according to the number of characters in the translation result. In this case, the usage fee may be determined not when the request information is registered in the request DB 1531 but when the translation result is registered in the request DB 1531 in a registration process described later, and stored in the usage fee column. Further, today's date is stored in the request date column.

  A request mail for requesting translation is sent to the translator (S56). Specifically, among the translators stored in the translator information storage area 151, one translator is extracted from the translators in which both the description language of the requested content and the specified language are stored in the language column. The In the request DB 1531, the extracted translator number of the translator is stored, and the contact information of the translator is read out and used as the destination of the e-mail. The request mail includes at least the original URI stored in the original URI field and the request number. The request execution process ends, the process returns to the translation request process (see FIG. 7), and the translation request process also ends.

  The case where the request content has already been requested to be translated will be described. As shown in FIG. 7, if there is an entry of the same request URI and specified language in the request DB 1531 and the request has been requested (S3: YES), the translation result URI is stored in the translation result URI column of the request DB storage area 153. Based on whether or not it is stored, it is determined whether or not the translation has been completed (S11). If the translation result URI is not stored (S11: NO), since the requested content is being translated, the contact input screen 203 (see FIG. 16) is displayed on the client client 2 (S12).

  The contact input screen 203 informs the client that another person has already requested translation of the requested content in the same language, and a contact address (e-mail address) to be notified when the translation is completed. ). As shown in FIG. 16, the contact input screen 203 is provided with a contact input field and an OK button. Contact reception processing is performed (S13). When the OK button is selected by the client in the client client 2, the contact address entered in the contact address input field is transmitted to the management server 1. The received contact information is stored in the contact address column in addition to the request number of the request in the request DB 1531. Then, the translation request process ends.

  If the requested content has already been requested for translation (S3: YES) and has been translated (S11: YES), the content of the requested content at the time of past translation is changed to the content of the current requested content. It is determined whether or not there has been (S20). Here, when there are a plurality of entries that are the request URI input in the request URI field and the translation result is stored in the translation result field, the entry with the newest request date is used. The original text (request content at the time of past translation) stored in the original text URI stored in the original text URI column of the entry to be used is acquired and compared with the current requested content stored in the request URI. If there is no difference between the two contents, there is no change in the contents of the requested contents from the time of translation in the past (S20: NO). In other words, since there is no need for translation, the requester becomes a secondary user, and the translation result can be obtained at this point.

  Therefore, secondary use processing is performed (S21, see FIG. 9). As shown in FIG. 9, in the secondary usage process, first, a usage confirmation screen 204 (see FIG. 17) is displayed on the client client 2 (S22). The usage confirmation screen 204 presents a usage fee to the secondary user and accepts an input as to whether or not to use the translation result with this usage fee. The usage fee is the amount stored in the usage bill of the request DB 1531 and is stored, for example, when the translation request is registered as described above (S55 in FIG. 8).

  As shown in FIG. 17, the usage confirmation screen 204 describes usage fees, and is provided with various information input fields for collecting usage fees from a credit card, an OK button, and a cancel button. The input fields for the credit card are a number input field, a name input field, a term input field, and a type selection field. When using the presented usage fee, the secondary user enters the credit card information in the credit card input field and presses the OK button. The secondary user presses the cancel button when not using it. The requester client 2 transmits a confirmation result corresponding to the pressed button to the management server 1. In the management server 1, a confirmation result receiving process for receiving the confirmation result from the requester client 2 is performed (S23).

  When the confirmation result confirms the use of the translation result, that is, is transmitted in response to the pressing of the OK button (S24: YES), a usage fee billing process is performed (S25). Specifically, request data for collecting a usage fee from a secondary user is transmitted to the credit card company management computer 6 with which the secondary user has a contract. The request data includes information input by the secondary user in the number input field, name input field, time limit input field, and type selection field, and the billing fee (usage fee).

  Subsequently, the number of times of secondary use of the translation result is updated (S26). Specifically, 1 is added to each of the usage count column and the cumulative count column of the request DB 1531. The translation result is presented to the client client 2 (S27). Specifically, the translation result stored in the location indicated by the translation result URI stored in the translation result URI column of the request DB 1531 is converted into data that can be displayed on the client client 2 and transmitted. Then, the secondary usage process shown in FIG. 9 ends, the process returns to the translation request process shown in FIG. 7, and the translation request process also ends.

  In S20, when it is determined that the requested content at the time of past translation is different from the current requested content and the content has been changed since the past translation (S20: YES), the past translation is used, Alternatively, a process for causing the client to select whether to request a new translation is performed. Specifically, the retranslation confirmation screen 205 (see FIG. 18) is displayed on the client client 2 (S31). The retranslation confirmation screen 205 presents the ratio of the difference between the two contents and the translation date / time of the past translation to the requester and allows the user to specify whether to use the past translation or to request a new translation. is there.

  As shown in FIG. 18, the retranslation confirmation screen 205 is provided with a ratio of differences between two contents, a translation date and time of a past translation, a retranslation request button, and a past translation use button. For example, the difference between the two contents may be determined by checking the match for each character, and adopting the ratio of characters that do not match the requested content at the time of past translation among all characters of the current requested content. Further, for example, a match may be checked for each row, and a ratio of differences may be adopted as the proportion of rows that do not match the requested content at the time of past translation among all the rows of the current requested content. The requester presses a retranslation request button when requesting retranslation, and presses a past translation use button when using a past translation result. The requester client 2 transmits a confirmation result corresponding to the pressed button to the management server 1. In the management server 1, a confirmation result receiving process for receiving the confirmation result from the requester client 2 is performed (S32).

  If the confirmation result is a request for retranslation, that is, a request sent in response to pressing of the retranslation request button (S33: YES), a translation request is calculated (S34), and then a translation request is made. The process for performing is performed (S41-S44). Then, the translation request process shown in FIG. 7 ends. On the other hand, when the confirmation result uses the past translation result, that is, when the confirmation result is transmitted in response to the press of the past translation use button (S33: NO), the translation result is obtained with the requester as the secondary user. Secondary usage processing for use is performed (S21). Then, the translation request process shown in FIG. 7 ends.

  As described above, when the management server 1 receives an http request for requesting the display of the translation request screen 201 (see FIG. 14) from the requester client 2, the management server 1 inputs the URI of the content to be translated to the requester. The request URI is received (S2). If the requested content indicated by the requested URI has already been requested for translation, but the translation has not yet been completed (S3: YES, S11: NO), a message to that effect is presented to the requester (S12). If the client registers the contact information (S13), the translation completion notification can be received when the translation result is registered. Therefore, the requester does not need to confirm whether or not the translation result is registered, and can know it immediately after registration.

  In addition, when the requested content has already been translated (S3: YES, S11: YES), the management server 1 determines whether or not the requested content has changed from the time of translation. (S20: NO), the client is treated as a secondary user, and the usage fee is presented to the client (secondary user) (FIG. 9, S22). The management server 1 provides the translation result (S27) when the client confirms the use as paying the usage fee (S24: YES). Therefore, what has already been translated is not translated many times. Therefore, the secondary user can obtain the translation result only by paying the usage fee without paying the translation fee.

  In addition, when there is a change in the requested content from the time of translation (S20: YES), the management server 1 instructs the requester to use the past translation result or re-translate ( S31). Therefore, even if there is already a translation result, the requester can select whether to use a past translation result or to request a retranslation if the requested content has changed from the time of translation. .

  Further, since the ratio of the difference between the requested contents is presented, the requester can determine that the past translation result is used if the difference is small, or can determine that the retranslation is requested if the difference is large. The requester can cancel the translation request if it is enough to refer to the past translation even if there is a change in the already translated content. Never pay. In addition, if it is desired to translate the already translated content again, the translation request can be continued and a new translation result can be obtained. Therefore, the client can obtain the translation result with the latest content.

  Next, a translation result registration process in which a translator registers a translation result in the management server 1 will be described with reference to the flowchart of FIG. FIG. 10 is a flowchart of the translation result registration process. The translation result registration process is performed when the translation request management program executed by the CPU 10 of the management server 1 receives an http request for requesting display of the translation result registration screen 206 (see FIG. 19) from the translator client 3. Process.

  As shown in FIG. 10, first, the translation result registration screen 206 is displayed on the translator client 3 (S61). The translation result registration screen 206 is a screen displayed in a display area of a display window displayed by so-called browser software. Specifically, information for displaying the translation result registration screen 206 is transmitted to the translator client 3 as a response to the http request from the translator client 3.

  As shown in FIG. 19, the translation result registration screen 206 is provided with a request number input field for inputting a request number, a translation result file attachment field for attaching a translation result file, and an OK button. A request number and translation result reception process is performed (S62). The translator enters the request number on the translation result registration screen 206, attaches the translation result file to the translation result file attachment field, and presses the registration button. The described http request is transmitted. In the management server 1, the request number and the attached file are stored in a predetermined area of the RAM 11.

  The translation result is stored in the translation result DB 1551, and a URI is given to the stored translation result (S63). Then, in the request DB 1531, the URI given in S63 is stored in the translation result URI column of the received request number entry, and the current date is stored in the translation date column (S64).

  The requester is notified that the translation is complete (S65). Specifically, the requester number of the received request number entry in the request DB 1531 is read, and the contact information of the requester number is read from the requester information storage area 152. Then, a notification mail is transmitted to the read contact information. In the notification mail to the client, at least the translation result URI is described. In addition, a request URI and a translation request number may be described.

  The other contact is notified that the translation is complete (S66). Specifically, the notification mail is transmitted to the contact stored in the other contact column of the request DB 1531. A notification URI to other contact information includes at least a request URI. The other contact, when trying to obtain the translation result, had already requested translation for the target translation object, and the translation was not completed at that time. The contact information for those who are waiting for completion. Thus, neither translation fees nor usage fees have been paid. Therefore, only the request URI is presented, and only the completion of translation of the content of the URI is notified. The person who has requested the translation completion can request the secondary use of the translation result and use the translation result by paying the translation usage fee.

  A translation reward is paid to the translator (S67). Specifically, the translator number of the received request number entry in the request DB 1531 is read, and the transfer account of the translator number is read from the translator information storage area 151. And the process which transfers a translation reward to the read transfer account is performed. After the transfer process, the translation result registration process ends.

  As described above, the management server 1 displays the translation result registration screen 206 on the translator client 3 in response to an access from the translator client 3 by the translator (S61). When the translator attaches the translation result file to the translation result registration screen 206, the translation result is delivered to the management server 1 (S62). The translation result is registered in the translation result DB 1551 (S63, S64). When the translation result is registered in the translation result DB 1551, the requester and other contact information are notified (S65, S66). Therefore, the requester does not need to confirm whether or not the translation result has been registered, can know that the translation result has been registered immediately after registration, and can obtain the translation result. In addition, a person who requests to receive a notification when the translation result is registered can know that the translation result has been registered immediately after the registration.

  Next, monthly processing will be described with reference to the flowcharts of FIGS. 11 is a flowchart of monthly processing, FIG. 12 is a flowchart of translator compensation processing executed in monthly processing, and FIG. 13 is client compensation executed in monthly processing. It is a flowchart of a process. The monthly process is a process in which the management server 1 pays a secondary reward and a return reward for one month on a predetermined day (for example, one day) of one month.

  As shown in FIG. 11, in the monthly process, first, a reward reward process is performed (S71, see FIG. 12), and then a secondary reward process is performed (S72, see FIG. 13). Then, the value in the usage count column of the request DB 1531 is cleared to zero (0) (S73). Then, the monthly process ends.

  The return reward process will be described with reference to the flowchart of FIG. First, the first requester (first record) is read from the requester information storage area 152 (S81). If the requester can read (S82: YES), the initial value of zero (0) is stored in the return reward storage area (not shown) provided in the RAM 11 (S83). The translation result URI of the first entry in the request DB 1531 is read (S84). If the translation result URI can be read (S85: YES), the request can be used for secondary use. Therefore, the usage count of the entry is acquired (S86), and the usage fee is acquired (S87). A value obtained by multiplying the usage fee, the number of uses, and the client allocation rate is added to the value (reduction reward) stored in the return reward storage area at this time, and stored in the return reward storage area (S88). In this embodiment, the client distribution rate is 15% for any client.

  The process returns to S84, and the translation result URI of the next entry is read (S84). If the next translation result URI can be read (S85: YES), the number of uses is acquired (S86), the use fee is acquired (S86), and the reward of the entry is added to the return reward (S88). Then, the process returns to S84 again.

  When the processing of S84 to S88 is repeated and the reduction reward for the requester is accumulated in the reduction reward storage area for all entries, the translation result URI is not read in S84 and it is determined that there is no translation result URI. (S85: NO). Accordingly, it is determined whether or not the value (reward reward) stored in the return reward storage area is greater than zero (0) (S89). If the return reward is not greater than zero (0) (S89: NO), there is no need to transfer the return reward to the client, so the process returns to S81 and the next client is processed. If the return reward is greater than zero (0) (S89: YES), it is necessary to pay the return reward to the client. Then, the transfer account column of the requester information storage area 152 is referred to, and a process of transferring the value (reduction reward) stored in the return reward storage area to the account is performed (S90). Then, the process returns to S81, and the next requester's process is performed.

  When the processes of S81 to S90 are repeatedly performed and the processes of all the requesters stored in the requester information storage area 152 are completed (S82: NO), the return reward process shown in FIG. Return to.

  The secondary reward process will be described with reference to the flowchart of FIG. First, the first translator (first record) is read from the translator information storage area 151 (S91). If the translator can read (S92: YES), the initial value of zero (0) is stored in the secondary reward storage area (not shown) provided in the RAM 11 (S93). The translation result URI of the first entry in the request DB 1531 is read (S94). If the translation result URI can be read (S95: YES), the request can be used for secondary use. Therefore, the usage count of the entry is acquired (S96), and the usage fee is acquired (S97). A value obtained by multiplying the usage fee, the number of uses, and the translator allocation rate is added to the value (secondary reward) stored in the secondary reward storage area and stored in the secondary reward storage area (S98). ). In this embodiment, the translator distribution ratio is 10% for any translator.

  The process returns to S94, and the translation result URI of the next entry is read (S94). When the next translation result URI can be read (S95: YES), the number of uses is acquired (S96), the usage fee is acquired (S96), and the reward of the entry is added to the secondary reward (S98). Then, the process returns to S94 again.

  When the processing of S94 to S98 is repeatedly performed and the secondary reward for the translator is accumulated in the secondary reward storage area for all entries, the translation result URI is not read in S94, and the translation result URI is It is determined that there is not (S95: NO). Therefore, it is determined whether or not the value (secondary reward) stored in the secondary reward storage area is zero (0) (S99). If the secondary reward is not greater than zero (0) (S99: NO), there is no need to transfer the secondary reward to the client, so the process returns to S91 and the next translator is processed. If the secondary reward is greater than zero (0) (S99: YES), it is necessary to pay the translator a secondary reward. Then, the transfer account column of the translator information storage area 151 is referred to, and a process of transferring the value (secondary reward) stored in the secondary reward storage area to the account is performed (S100). Then, the process returns to S91, and the next translator process is performed.

  When the processes of S91 to S100 are repeatedly performed and the processes of all the translators stored in the translator information storage area 151 are completed (S92: NO), the secondary reward process shown in FIG. Return to the next process.

  As described above, the return reward for the client and the secondary reward for the translator are calculated and paid to the client and translator every month according to the situation in which the translation result is used in the month. Is called. Since the reduction fee and the secondary fee are covered by the usage fee, the usage fee is larger than the sum of the reduction fee and the secondary fee. In the present embodiment, the client allocation rate is 15%, the translator allocation rate is 10%, and the remaining 75% is the revenue of the system administrator of the translation request management system. As described above, the requester and the translator can obtain a reward when the translation result is secondarily used.

  In the present embodiment, the requester can obtain a reduction reward when the translation result of the translation requested by the client is secondarily used. Therefore, the requester can collect the translation fee paid at the time of the translation request according to the use of the translation result. Furthermore, if secondary usage increases, a reduction reward more than the translation fee can be obtained, which may generate profits. In addition, the translator can receive a translation reward at the time of translation result registration, and can further obtain a secondary reward if the translation result is secondarily used. Thereby, the burden of the expense of the client who concerns on a translation request is reduced.

  In the above embodiment, the step (S2) of receiving information input in various input fields of the translation request screen 201 performed by the CPU 10 of the management server 1 in the translation request process shown in FIG. This corresponds to a “request reception step”. The step (S56) of sending a request mail to the translator performed by the CPU 10 in the translation request execution process shown in FIG. 8 corresponds to the “translation request step” of the present invention. The steps (S4, S34) for calculating the translation reward performed by the CPU 10 in the translation request process correspond to the “translation reward determination step” and the “translation fee determination step” of the present invention. The step of charging a translation fee (S53) performed by the CPU 10 in the translation request execution process corresponds to the “translation fee billing step” of the present invention. The step of receiving the translation result (S62) performed by the CPU 10 in the translation result registration process shown in FIG. 10 corresponds to the “translation result receiving step” of the present invention, and the step of storing the translation result in the translation result storage area 155 (S62). Corresponds to the “translation result storing step” of the present invention.

  The steps (S83 to S88) for calculating the return reward performed by the CPU 10 in the return reward process shown in FIG. 12 correspond to the “reward reward determination step” of the present invention. The steps (S93 to S98) for calculating the secondary reward performed by the CPU 10 in the secondary reward process shown in FIG. 13 correspond to the “secondary reward determination step” of the present invention. The step (S25) in which the CPU 10 charges the secondary user for the usage fee in the secondary usage processing shown in FIG. 9 corresponds to the “utilization fee charging step” of the present invention.

  The request DB storage area 153 of the management server 1 corresponds to “location information storage means” of the present invention, and the original text storage area 154 corresponds to “original text storage means” of the present invention. The step (S3) of determining whether or not the translation has been requested performed by the CPU 10 in the translation request processing corresponds to the “past request determination step” of the present invention. The step (S20) of determining whether the content of the current requested content has been changed from the content of the requested content at the time of past translation performed by the CPU 10 in the translation request process corresponds to the “change determining step” of the present invention. . The step (S32) of receiving the inquiry result transmitted from the requester client 2 in response to the retranslation confirmation screen 205 performed by the CPU 10 in the translation request process corresponds to the “continuation instruction receiving step” of the present invention. The step (S54) of storing the original text in the original text storage area 154 performed by the CPU 10 in the request execution process corresponds to the “original text storage step” of the present invention.

  The step (S41) of displaying the request confirmation screen 202 on the requester client 2 performed by the CPU 10 in the translation request process corresponds to the “translation information output step” of the present invention. The step (S42) of receiving the inquiry result transmitted from the requester client 2 in response to the request confirmation screen 202 performed by the CPU 10 in the translation request process corresponds to the “request definition receiving step” of the present invention. Further, in the above embodiment, the period until the next monthly process is performed is “first predetermined period”, “second predetermined period”, “third predetermined period”. It corresponds to.

  The translation request management method, translation request management apparatus, and translation request management program of the present invention are not limited to the above-described embodiment, and it is needless to say that various modifications can be made to the above-described embodiment. .

  In the above embodiment, the HDD 15 of the management server 1 includes the translation result storage area 155 and the original text storage area 154. However, these storage areas may not be provided in the management server 1. For example, the translation result and the original text may be stored in a storage medium that can be accessed by the management server 1 directly or indirectly through another server through the Internet or another dedicated network. Moreover, in the said embodiment, although the reduction | restoration reward process (refer FIG. 12) and the secondary reward process (FIG. 13) are performed for every month, the space | interval which performs these processes is not restricted to one month. These processes may be performed, for example, every day or every week. Further, it is not necessary to perform each process at the same timing or interval.

  In the above embodiment, the translation fee collected from the client and the translation fee paid to the translator are the same amount, and the funding source for the translation fee is the translation fee. In addition, a part of the usage fee is used as a source of funds for return and secondary compensation, and the rest is used as a profit for the system administrator. However, the relationship between the charges is not limited to this. For example, the translation fee may be larger than the translation fee, and the difference may be the revenue of the system administrator. Further, the translation fee may be set to be smaller than the translation fee, and the difference may be borne by the system administrator. In this case, the share of the system administrator in the usage fee may be increased so that the collection of the burden amount can be accelerated.

  Further, instead of determining the translation fee based on the translation fee, the translation fee may be determined after determining the translation fee. As a method for determining the translation fee, for example, there is a method in which the requester specifies. In this case, the requester may input an amount “Request translation for this amount” and use that amount as the translation fee. Alternatively, a bid may be made such that a plurality of clients are designated with a translation fee, and the client who has designated the highest translation fee is determined as the final client. Further, the entire usage fee may be used as a return reward and a secondary reward. That is, the ratio of the client distribution rate and the translator distribution rate can be set to 100%.

  In the above embodiment, the correspondence to the copyright of the requested content in the translation request management system is not described. When considering the correspondence to copyright, in the above embodiment, the management server 1 does not determine whether or not the copyright is infringed by translation, but is a person (system) belonging to an organization that provides a translation request management system. Administrator). Specifically, the system administrator confirms whether or not there is a copyright statement (a statement that translation is permitted) in the content, or negotiates with the copyright owner for translation. To do. The management server 1 requests the translator to translate only when translation is permitted or translation negotiation is established.

  For example, in S56 of the request execution process shown in FIG. 9, the management server 1 displays a translation negotiation success / failure input screen (not shown) before performing the process of determining a translator and sending a request mail, and thereafter It is only necessary to wait for the process. The translation negotiation establishment input screen is provided with a “translation possible” button and a “translation impossible” button. When the system administrator selects the “translation impossible” button, the management server 1 sends an e-mail notifying that the negotiation for translation has not been established to the requester, and notifies the request DB of data. delete. If the “translation enabled” button is selected, it is determined that translation negotiation has been established, and the process of S56 is performed.

  Further, for example, a copyright negotiation column is provided in the request DB 1531, and the management server 1 stores a value indicating “negotiating” before the process of S56, and ends the request execution process without performing the process of S56. You may let them. In this case, the management server 1 may execute a copyright negotiation registration process after the copyright negotiation is completed. In the copyright negotiation registration process, the above-described translation negotiation success / failure screen is displayed, and the system administrator inputs the negotiation result. When the “translation impossible” button is selected, the management server 1 sends an e-mail notifying that the negotiation for translation has not been established to the requester, and deletes the data from the request DB 1531. When the “translation enabled” button is selected, the management server 1 determines that a translation negotiation has been established, determines a translator, and transmits a request mail.

  As described above, when a person negotiates copyright, a system administrator is burdened with copyright negotiation. Therefore, the allocation rate for determining the reward allocated to the system administrator from the translation fee and usage fee may be increased.

  A predetermined amount may be paid to the copyright holder from the translation fee. For example, in the above embodiment, the system administrator receives 75%, but 10% of the amount may be paid to the copyright holder. In this case, transfer to the account of the copyright owner is performed after the copyright negotiation is established. Further, a reward distributed from the usage fee may be paid to the copyright holder. For example, the copyright holder allocation rate is 10% of the usage fee, the translator allocation rate is 10% of the usage fee, the client allocation rate is 20% of the usage fee, and the remaining 60% is the system administrator allocation rate. Can do.

  If the copyright owner clearly states the copyright treatment in the content and the system administrator does not need to negotiate translation with the copyright owner, the system can be set to reduce the revenue of the system administrator. Good. For example, if the system administrator's profit is added to the translation reward, the added amount may be lowered. Further, the distribution rate of the usage fee may be lowered.

  As a method for the copyright holder to clearly indicate the handling of the copyright in the content, it is conceivable that the usage conditions are displayed when the content is displayed on the display. In this case, the system administrator may decipher the description and determine whether translation is possible. There is also a method for presenting the terms of use of copyrighted works proposed in a project called Creative Commons. As the presenting method, there are a method of displaying a use condition with a mark when content published on the network is displayed on a display, and a method of embedding the use condition in content metadata. Since the metadata is embedded with information about the use conditions in a fixed description, the management server 1 can automatically determine whether or not the content can be translated. Therefore, the confirmation work of the translation of the system administrator to the copyright holder is greatly reduced.

  In the above embodiment, the usage fee is a fixed value, but may be changed according to the number of times of use. For example, the usage fee may be increased by increasing the usage fee when the usage count exceeds a predetermined number, or the usage fee may be reduced by increasing the usage fee when the usage frequency exceeds the predetermined count. In this case, the period from when the translation result is registered to when the usage fee is changed corresponds to the “first predetermined period”. In addition, the usage fee is not changed only by the number of usages. For example, a predetermined period such as one month or one week is set as a “first predetermined period”, and the usage fee is set according to the number of usages for each first predetermined period. You may decide. In this case, the first usage fee may be used if the number of uses during the predetermined period is the number of times of the first width, and the second usage fee may be used if the number of times of use is the second width.

  Further, the usage fee may be changed according to the total usage fee, not the number of usages. For example, the usage fee may be reduced or increased when the total usage amount exceeds a predetermined amount. In this case, the period from when the translation result is registered to when the usage fee is changed corresponds to the “first predetermined period”. In addition, for example, if a predetermined period such as one month or one week is set as the “first predetermined period” and the total amount of the usage fee for each first predetermined period is within the first range, the first usage fee, If the amount is in the second range, the second usage fee may be used. Further, the usage fee may be determined in consideration of both the number of usages and the total amount of the usage fee. Alternatively, secondary user management may be performed and a usage fee may be set for each user. In this way, it is possible to determine the usage fee by grasping the revenue status of the usage fee due to secondary use of the translation result.

  The client distribution ratio is uniform in the above embodiment, but the client distribution ratio may be changed according to the number of uses. For example, if the number of uses exceeds a predetermined number, the client distribution rate and translator distribution rate may be increased to distribute more profit. In this case, the time from when the translation result is registered until the time when the distribution rate is changed corresponds to the “third predetermined period”. In this case, the burden on the client is further reduced. When the number of uses in the third predetermined period becomes equal to or greater than the predetermined number, the client allocation rate may be lowered to secure more profits for the system administrator. In this case, since the collection of the translation fee paid to the translator is also progressing, the burden on the client will not increase even if the client allocation rate is lowered to reduce the return reward to the client.

  Also, instead of changing the distribution rate only by the number of uses, for example, a predetermined period such as one month or one week is set as a “third predetermined period”, and the client distribution rate is determined according to the number of uses for each third predetermined period. May be determined. In this case, if the number of uses in the third predetermined period is the number of times of the first width, the first rate is determined, and if the number of times of use is the number of the second width, the second rate is determined. Also good. In addition, the client distribution ratio may be determined according to the total amount of usage charges during the third predetermined period, instead of the number of uses. For example, when the total amount of usage money exceeds a predetermined amount, the rate may be reduced or the price may be increased.

  In addition, for example, a predetermined period such as one month or one week is set as a “third predetermined period”, and if the total amount of usage fees for each third predetermined period is within the first range, the first ratio, If the amount is in the second range, it may be determined to be the second ratio. In addition, the client distribution rate may be determined in consideration of both the number of times of use and the total amount of usage charges. In addition, the requester distribution ratio may be set for each requester. It should be noted that not only the client allocation rate but also the translator allocation rate may be changed based on the number of usages during a predetermined period and the total amount of usage fees, such as the client allocation rate. In this way, the ratio for determining the return reward and the secondary reward can be changed according to the income state by the secondary use of the translation result.

  In the above embodiment, the return reward is determined in the monthly processing that is performed every month. More specifically, the reward is calculated by multiplying the total amount of usage multiplied by the usage fee during the period from the previous monthly processing to the current monthly processing, by the client allocation rate. Is determined. In this case, the period from the previous monthly process to the current monthly process corresponds to the “second predetermined period”. However, the amount multiplied by the client allocation rate is not limited to the total amount of usage charges during the period between the monthly processing and the monthly processing. When the processing for determining the return reward is every day and every week, the total amount of user fees for each day and week may be multiplied by the client allocation rate.

  Further, the timing for determining and paying the return reward may not be a regular timing such as every day, every week, or every month. In this case, the period from the previous determination of the return reward to the determination of the next return reward corresponds to the “second predetermined period”. However, for the first time, the period from when the translation result is registered until the first reduction reward is determined is the “second predetermined period”. In addition, when changing the client allocation rate, there are a period (second predetermined period) used as a calculation criterion for the return reward and a period (third predetermined period) used as a criterion for determining the client allocation rate. May be different. For example, when determining return rewards in monthly processing, the amount multiplied by the client allocation rate is the total amount of usage amount from the previous monthly processing to the present, and the client allocation rate is from one week ago to the present It may be determined based on the total amount of usage charges up to.

  In the above embodiment, one translator is requested to translate one translation request, and one translation result is registered in the translation result DB 1551. However, translation may be requested to a plurality of translators. In this case, for example, the translation result of the translator who registered the translation request in the translation result DB 1551 earliest may be used. The translation result submitted within a predetermined period may be checked by the administrator of the translation request management system, and the most excellent translation result may be registered in the translation result DB 1551.

  A plurality of translation results may be registered in the translation result DB 1551. In this case, for example, before providing the translation result to the secondary user, a part of the translation result is presented, and the secondary user refers to it and selects which translation result to use. Also good. In this way, when the secondary user makes a selection, a better translation result is used more. Therefore, translators can expect more secondary rewards by creating better translation results, allowing translators to compete to provide higher quality translations and improve translation levels. become.

  In the above embodiment, the translation fee and usage fee are charged through the credit card company, but the billing and collection methods are not limited to those using the credit company, and other financial institutions and financial systems can also be used. Good. Moreover, you may use a point instead of cash as a charge and a reward. In this case, the point of each user is managed by the management server 1, and the user can pay the translation fee with points or acquire the translation reward with points.

  In the above embodiment, when the content of the current requested content is changed from the content of the requested content at the time of past translation (FIG. 7, S20: YES), the requester requests retranslation (S33: YES), the translator is requested to translate the content at the time of the translation request (S56). However, when re-translating content that has been translated in the past, it is possible to request re-translation of only the changed portion instead of translating the entire content. In this case, the translation fee and the translation reward may be determined at a lower price than when requesting translation of the entire content.

It is a schematic diagram which shows the structure of the apparatus used with a translation request management system. It is explanatory drawing which shows the process sequence in a translation request and translation result utilization. 2 is a block diagram showing an electrical configuration of the management server 1. FIG. 4 is a schematic diagram showing a configuration of a translator information storage area 151. FIG. 4 is a schematic diagram showing a configuration of a requester information storage area 152. FIG. 5 is a schematic diagram showing a configuration of a request DB storage area 153. FIG. It is a flowchart of a translation request process. It is a flowchart of the request execution process performed in a translation request process. It is a flowchart of the secondary use process performed in a translation request process. It is a flowchart of a translation result registration process. It is a flowchart of a monthly process. It is a flowchart of the reduction | restoration reward process performed in a monthly process. It is a flowchart of the secondary reward process performed in a monthly process. It is a schematic diagram which shows the translation request screen 201. FIG. It is a schematic diagram which shows the request confirmation screen. It is a schematic diagram which shows the contact input screen 203. FIG. It is a schematic diagram which shows the usage confirmation screen. It is a schematic diagram which shows the retranslation confirmation screen. It is a schematic diagram which shows the translation result registration screen.

Explanation of symbols

1 Management Server 2 Client Client 3 Translator Client 4 Secondary User Client 5 Web Server 7 Internet 10 CPU
15 Hard disk device 151 Translator information storage area 152 Requester information storage area 153 Request DB storage area 154 Original text storage area 155 Translation result storage area 156 Program storage area 1531 Request DB
1551 Translation Result DB

Claims (8)

A translation request management method processed by a translation request management apparatus connectable to a network,
A request accepting step for accepting request information, which is information related to a content translation request, output from a user device connected to the translation request management device via the network, via the network;
A translation requesting step for requesting a translator to translate the content indicated by the request information received in the request receiving step;
A translation reward determination step for determining a translation reward that is a reward paid to the translator for the translation of the content;
Based on the translation reward determined in the translation reward determination step, as a fee required for translation of the content, to the translation requester who has operated the user device that has output the request information received in the request reception step A translation fee determination step for determining a translation fee to be charged;
A translation fee requesting step of charging the translation requester to the translation requester;
A translation result receiving step for receiving a translation result by the translator requested to translate in the translation requesting step;
A translation result storage step of storing the translation result received in the translation result reception step in a translation result storage means provided in the translation request management device and publishable on the network;
A reduction reward determining step for determining a reduction reward that is a reward paid to the translation requester in order to reduce a part of the translation fee;
A usage fee billing step of charging a usage fee to a secondary user using the translation result stored in the translation result storage means,
The translation request management method, wherein the usage fee is an amount equal to or more than the reduction fee. A secondary reward determination step for determining a secondary reward that is a reward paid to the translator for use of the translation result;
The translation request management method according to claim 1, wherein the usage fee is an amount that is equal to or greater than a total amount of the return reward and the secondary reward. The request information includes location information indicating a storage location of the content on the network,
The translation request management device includes:
Location information storage means for storing the location information;
Original text storage means for storing the original text of the content acquired from the location indicated by the location information as an acquired original text;
Whether the location information included in the request information received in the request reception step is stored in the location information storage means determines whether or not the content translation request has been received. A past request determination step;
Whether the original text of the content stored in the location indicated by the location information included in the request information received in the request reception step is the same as the acquired original text stored in the original text storage unit A change determination step for determining whether or not
When it is determined in the change determining step that the original text and the acquired original text are not the same, an instruction to continue or cancel the translation request indicated by the request information is received from the user device via the network. A continuation instruction reception step;
An original text storage step of storing the original text of the content stored in the location indicated by the location information as the acquired original text in the original text storage means when the translator is requested to translate in the translation requesting step; Prepared,
In the translation request step, when an instruction to continue the translation request is received in the continuation instruction reception step, and when it is determined that the content translation request has not been received in the past request determination step, 3. The translation request management method according to claim 1, wherein the translation is requested to the translator.   Usage in which the usage fee charged in the usage fee requesting step is determined based on at least one of the number of times the translation result is used and the total amount of the usage fee collected during the first predetermined period. The translation request management method according to claim 1, further comprising a fee determination step. In the return reward determination step, the return reward is determined by multiplying the total amount of the usage fee collected during the second predetermined period by a predetermined ratio,
The method further comprises a ratio changing step of changing the predetermined ratio based on at least one of the number of times the translation result is used and the total amount of the usage fee collected in a third predetermined period. The translation request management method according to any one of claims 1 to 4, wherein The request reception step includes:
A translation information output step of outputting, via the network, translation information including at least information on the return reward for the translation indicated by the request information;
A request confirmation accepting step for accepting an instruction for confirming a request for translation of the content from the user device via the network after outputting the translation information in the translation information output step;
6. The translation requesting step requests the translator to perform translation when an instruction to confirm the request for translation is accepted in the request confirmation accepting step. Translation request management method. A translation request management device connectable to a network,
Request accepting means for accepting request information, which is information relating to a content translation request, output from a user device connected to the translation request management device via the network, via the network;
Translation request means for requesting a translator to translate the content indicated by the request information received by the request reception means;
Translation reward determining means for determining a translation reward that is a reward paid to the translator for translation of the content;
Based on the translation reward determined by the translation reward determination means, the translation requester who has operated the user device that has output the request information received by the request reception means as a fee required for the translation of the content. A translation fee determining means for determining a translation fee to be charged;
A translation fee requesting unit that charges the translation requester to the translation requester;
A translation result accepting means for accepting a translation result by the translator requested to translate in the translation requesting means;
Translation result storage means for storing the translation result received by the translation result reception means so as to be openable on the network;
A reduction reward determining means for determining a reduction reward that is a reward paid to the translation requester to reduce a part of the translation fee;
Usage fee billing means for billing a secondary user using the translation result stored in the translation result storage means;
The translation request management apparatus, wherein the usage fee is an amount equal to or more than the return reward.   A translation request management program for causing a computer to execute various processing steps of the translation request management method according to claim 1.

Images