JP2004157906A - Trouble information management server, terminal device, method of reporting trouble, and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To relieve a WWW site of a burden of monitoring the trouble of its own Web page. <P>SOLUTION: A trouble information management server 1 which manages trouble information about the trouble of a Web page disclosed at a WWW site 2 is provided with a trouble information acquisition part 101 by which information on the trouble of the Web page found when a user browses the Web page using a terminal device 3 is acquired from the terminal device 3 as trouble report information DT1; a reward payment process part 161 which performs a process for rewarding the user who sent the trouble report information DT1 acquired for providing the trouble information; and a trouble reporting part 102 which reports the trouble of the Web page to an operator of the WWW site 22 disclosing the Web page related to the acquired trouble report information DT1. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a defect information management server that manages information relating to a defect on a Web page found on a user terminal device.
[0002]
[Prior art]
In recent years, with the development of the Internet, many companies, organizations, individuals, and the like have opened WWW sites (Web sites). As a result, the number and types of Web pages transmitted from WWW sites are increasing.
[0003]
Furthermore, Web pages using various technologies have been realized. For example, a Web page having an electronic bulletin board (BBS) is realized by executing a CGI (Common Gateway Interface) program on a WWW server. Thereby, many users can exchange opinions on the electronic bulletin board. In addition, by executing a program written in a language such as JavaScript (registered trademark), Java applet (registered trademark), or ActiveX control (registered trademark) on a WWW browser of a terminal device, a dynamic Web page that changes and Web pages that perform various processes are realized. Thus, a user using the Internet can browse and use various types of Web pages.
[0004]
[Patent Document 1]
JP 2000-101635 A
[0005]
[Patent Document 2]
JP 2001-188825 A
[0006]
[Problems to be solved by the invention]
However, with the development of various technologies, there is an increasing danger that a Web page that is inconvenient for both the WWW site and the user will be released. For example, if a Web page infected with a virus is released, the WWW site may lose credibility to the user, and the user who browses the Web page may be adversely affected, such as breaking the system of his terminal device. There is a risk. If a web page is modified by a cracker (a malicious hacker) to attack, the WWW site loses its credibility and the user may be damaged by the terminal device system.
[0007]
In addition, if information that slanders others or slanders is written on an electronic bulletin board, the user may suffer disadvantages such as feeling unpleasant, and the WWW site may be forced to close. In addition, if an adult Web page such as pornography can be browsed without restriction, it is inconvenient when a child searches for information on the Internet.
[0008]
Therefore, the operator of the WWW site needs to be responsible for the contents of the Web page that he / she has disclosed, and grasp whether or not the Web page has any problems. On the other hand, the user needs to be careful not to collect information on a defective Web page and to access such a Web page.
[0009]
However, continuing to monitor the published Web pages imposes a heavy burden on the WWW site operator. In addition, since new Web pages are transmitted one after another on the Internet, collecting information on defective Web pages imposes a heavy burden on the user. Even if the techniques disclosed in Patent Literatures 1 and 2 are used, it is not possible to efficiently collect information on Web page inconveniences and reduce the burden on WWW site operators and users.
[0010]
SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and has as its object to reduce the burden on a WWW site operator of monitoring a defect on his or her Web page. It is another object of the present invention to efficiently prevent a user from accessing a Web page having a problem.
[0011]
[Means for Solving the Problems]
A defect information management server according to the present invention is a defect information management server that manages defect information relating to a defect of a Web page published on a WWW site, and is found when a user is browsing a Web page with a terminal device. A defect information acquisition unit that acquires the defect information of the defect of the Web page from the terminal device, and a reward for providing the defect information to a user of the transmission source of the defect information acquired by the defect information acquisition unit. A reward giving unit that performs a process for giving the information and a WWW site operator that publishes a Web page related to the defect information acquired by the defect information acquiring unit is notified that there is a defect in the Web page. Failure reporting means.
[0012]
Preferably, when the acquired plural pieces of defect information relate to the same defect on the same Web page, the reward granting means only rewards a predetermined number of users who provided the defect information earlier. give.
[0013]
Alternatively, there is provided a report fee collecting means for performing processing for collecting a price for reporting that there is a defect in the web page from a WWW site that discloses the web page.
[0014]
Alternatively, it is determined whether there is a defect in a defect information database storing the defect information acquired by the defect information acquisition unit and a Web page requested by the terminal device to be viewed by a user of the terminal device. And a result transmitting means for transmitting a result of the determination by the defect presence determining means to the requesting terminal device, wherein the URL of a Web page related to the defect information is included in the defect information. The defect presence / absence determination unit includes a defect in the Web page by comparing the URL of the Web page to be browsed with the URL of each of the defect information stored in the defect information database. It is determined whether or not. Alternatively, there is provided a determination fee collecting means for performing processing for collecting a price for the determination from the user of the terminal device requesting the determination.
[0015]
A terminal device according to the present invention is a terminal device connectable to a defect information management server that manages defect information related to a defect of a Web page, and stores a pattern information indicating the pattern for each defect pattern of a Web page. The information storage unit and the code group for configuring the Web page being browsed by the user are checked to see if any of the patterns indicated by the pattern information is included in the code group. Fault detecting means for detecting a fault to be detected, and fault reporting means for performing processing for reporting a fault found by the fault detecting means to the fault information management server.
[0016]
Preferably, the apparatus further includes a defect information acquisition unit that acquires the defect information managed by the defect information management server, wherein the defect report unit determines whether the defect of the Web page discovered by the defect detection unit is the defect information acquisition. If the information is not shown in any of the defect information obtained by the means, a process for reporting the defect to the defect information management server is performed.
[0017]
In the present invention, the “defect” means that at least one of the operator of the WWW site and the user who browses the Web page is inconvenient or inconvenient.
[0018]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 is a diagram showing an example of a configuration of a defect information management system having a defect information management server 1 and a terminal device 3 according to the present invention, FIG. 2 is a diagram showing an example of a hardware configuration of the defect information management server 1, and FIG. Is a diagram showing an example of a functional configuration of the defect information management server 1, FIG. 4 is a diagram showing an example of a user information database 1D1, FIG. 5 is a diagram showing an example of a site information database 1D2, and FIG. FIG. 7 is a diagram showing an example of a defect report form HG1, FIG. 8 is a diagram showing an example of a defect information database 1D4, FIG. 9 is a diagram showing an example of an e-mail for reporting defect information DT2, FIG. Is a diagram showing an example of a caution screen HG2.
[0019]
As shown in FIG. 1, a defect information management server 1 according to the present invention is operated by, for example, a provider (Internet Service Provider) 100 and manages information on a defect of a Web page published on each WWW site 2. are doing. Hereinafter, such information may be referred to as “defect information”. The failure information management server 1 is connected to a terminal device 3 of a user (hereinafter simply referred to as a “user”) using the Internet, each device of a WWW site 2, and a system such as a bank or a credit company via a network 4. To exchange information about payment of a reward or deduction of a fee, which will be described later. As the network 4, the Internet, a dedicated line, a public line, or the like is used.
[0020]
The terminal device 3 is a personal computer having a WWW browser function and a communication device, a mobile phone device, a PDA (Personal Digital Assistant), or the like. The user can browse Web pages published on each WWW site 2 by inputting a URL (Uniform Resource Locator) to the terminal device 3 or the like. A user may find a defect in a Web page being viewed. At this time, by providing the provider 100 with information on the defect (defect information), a reward can be obtained from the WWW site 2 via the provider 100. Further, the user can receive a service for inspecting (checking) whether or not there is a defect in the Web page that he or she is trying to view, using the defect information collected by the provider 100. In this case, the user pays the usage fee to the provider 100. That is, the user is both a provider and a user of the defect information.
[0021]
Each WWW site 2 has a contract with the provider 100 so as to have the Web site published by the WWW site 2 among the defect information discovered by the terminal device 3 and provided to the provider 100 provided. Examples of the form of the WWW site 2 include a WWW site operated by a company, a school, a research institution, a public organization, and the like, and a WWW site operated by a user who subscribes to the provider 100 or another provider (so-called individual site). .
[0022]
The WWW site 2 is realized by the WWW server 2a. Basically, one or a plurality of WWW servers 2a are provided for each WWW site 2. However, in the case of a personal site, a WWW site of a company branch or an affiliated company, or a WWW site of a branch of an organization, the WWW server 2a of the provider, the head office, or the head office may be shared. In addition, the operator of each WWW site 2 has a terminal device 2b for receiving defect information from the provider 100.
[0023]
As shown in FIG. 2, the defect information management server 1 includes a CPU 10a, a RAM 10b, a ROM 10c, a magnetic storage device 10d, a display device 10e, an input device 10f such as a mouse or a keyboard, and various interfaces. The magnetic storage device 10d stores an OS (operating system) and programs and data for performing processing described later. The programs and data are loaded into the RAM 10b as needed, and the programs are executed by the CPU 10a.
[0024]
With such a configuration, the defect information management server 1 includes, as shown in FIG. 3, a defect information acquisition unit 101, a defect notification unit 102, a defect information distribution unit 103, a defect inquiry unit 104, a defect notification unit 105, and a financial process. Functions such as the unit 106 and the information storage unit 107 are realized.
[0025]
The information storage unit 107 has a user information database 1D1, a site information database 1D2, a failure category database 1D3, a failure information database 1D4, and the like.
[0026]
In the user information database 1D1, as shown in FIG. 4, the user ID, name, contact information, e-mail address, account number of the transfer destination of the reward for providing the trouble information, etc. Stores information about
[0027]
As shown in FIG. 5, in the site information database 1D2, the site ID and site name of the WWW site 2 receiving the service (provision of the defect information) of the provider 100, the URL (root URL) serving as the root of the WWW site 2, Information on contact information and the e-mail address of the operator is stored.
[0028]
As shown in FIG. 6, the type (category) of a defect is stored in the defect category database 1D3 in association with the category ID. “Virus infection” means that the Web page is infected with a virus. “Broken link” means that all or some of the hyperlinks provided on the Web page are not correctly linked. "Web page absent" means that the Web page indicated by the URL does not exist.
[0029]
“Attack” means that a malicious attack is launched on the terminal device 3. As an attack (attack), for example, there is a program that causes the terminal device 3 to execute a program that opens the window of the WWW browser indefinitely, causing a large load on the CPU or the like to cause damage. “Error occurrence” means that an error occurs when a program for realizing a Web page function is executed by a WWW browser. "Adult information,""illegalinformation,""wronginformation," and "old information" are information that may be offensive to minors, such as pornography, unauthorized purchase or sale of drugs or dangerous goods, Means that information that guides users to illegal activities such as the introduction of MLM, information that is different from the fact, and information that has become useless over time (for example, information on campaigns whose period has expired) is posted I do.
[0030]
The defect information acquisition unit 101 acquires the defect information found by the user from the terminal device 3 of the user, and the information storage unit 107 performs a process for registering the acquired defect information in the defect information database 1D4. These processes are performed in the following procedure.
[0031]
First, in the terminal device 3, when the user finds a defect on the Web page while browsing the Web page, the user inputs a predetermined URL (Uniform Resource Locator) to the WWW browser, and the defect as shown in FIG. The report form HG1 is displayed. The screen information for displaying the failure report form HG1, that is, the hypertext, may be transmitted from the failure information management server 1 or may be transmitted from another WWW server.
[0032]
The user inputs the URL of the Web page and the state of the defect in the defect report form HG1. For example, if it is found that a comment that slanders a person is written on a certain electronic bulletin board (BBS) of a provider, the URL of the Web page with the electronic bulletin board is entered in the text box TX11, and the check box group CB is entered. Click to select the check box corresponding to "Slander." Further, if necessary, a specific content of the defect is input to the text box TX12. If the category falls under any category other than slander, also select the corresponding check box. If the category does not fall into any of the categories or if it is difficult to classify the category, the user may select the "Other" check box and enter the specific content of the defect in the text box TX12.
[0033]
In the text boxes TX13 to TX16, the user ID, name, contact information, and account number of the transfer destination of the bounty of the user who found the defect are input. However, in the case of a user who has subscribed to the provider 100, since information such as a name is registered in the user information database 1D1 shown in FIG. 4, only the user ID needs to be input. In the case of a user who has not subscribed, since no user ID has been given, it is only necessary to input each item other than the user ID. When the transmission button BN1 is clicked, the contents entered in the text boxes TX11 to TX16 and the items checked in the check boxes (categories of the state of the defect) are reported as defect report information DT1 from the user terminal device 3 to the defect information management. Sent to server 1.
[0034]
Here, the defect information acquisition unit 101 in FIG. 3 receives the defect report information DT1 and notifies the operator of the provider 100 of the fact. The operator immediately browses the Web page indicated in the defect report information DT1 and checks the authenticity of the content of the report. If the contents are correct, a command to register the defect information is issued to the information storage unit 107. It should be noted that a device such as “Web page non-existence” or “broken link” that can be mechanically checked for authenticity may be configured to automatically check. Regarding “slandering” or “wrong information”, it is desirable for the operator to actually browse and confirm the Web page.
[0035]
Then, the information storage unit 107 stores the URL indicated in the defect report information DT1 in the defect information database 1D4 as shown in FIG. Further, based on the failure category database 1D3 in FIG. 6, the category ID of the failure state is registered in association with the URL and the storage date and time (registration date and time). Then, the defect information acquiring unit 101 transmits a message to the effect that information provision has been accepted to the terminal device 3 that has transmitted the defect report information DT1.
[0036]
In this way, the defect information found by the user is collected and stored in the defect information management server 1 one after another. Hereinafter, failure information including information such as a registration date and time, a URL, a category ID, and remarks as shown in FIG. 8 is referred to as “defect information DT2”. The information input to the text boxes TX13 to TX16 in FIG. 7 in the defect report information DT1 is used for processing for paying a reward to the user.
[0037]
As soon as it is confirmed that the content of the received defect report information DT1 is correct, the defect reporting unit 102 informs the WWW site 2 that discloses the Web page indicated by the information that a defect has been found. Report (report).
[0038]
For example, when the failure report information DT1 having the content shown in FIG. 7 is obtained, first, each route URL stored in the site information database 1D2 in FIG. 5 is compared with the URL indicated in the failure report information DT1. It specifies that the WWW site 2 that discloses the defective Web page is the “provider BBB”. Then, an e-mail for reporting the defect information DT2 as shown in FIG. 9 is generated and transmitted to the e-mail address of the operator of the provider BBB. The operator of the provider BBB that has received the defect information DT2 checks the content and performs maintenance of the Web page.
[0039]
When a plurality of pieces of defect report information DT1 for the same defect on the same Web page are sent at the same time, the defect information acquisition unit 101 registers the defect information DT2 based on only the defect report information DT1 acquired first. Do. Similarly, the failure reporting unit 102 also reports to the WWW site based on only the first failure report information DT1.
[0040]
The defect information distribution unit 103 transmits the defect information DT2 newly stored in the defect information database 1D4 to the terminal device 3 of each user during a predetermined period (for example, one week). Alternatively, the defect information DT2 may be transmitted each time it is newly stored in the defect information database 1D4, or may be transmitted when requested by the terminal device 3.
[0041]
The defect information DT2 is stored in the defect information database 3D1 (see FIG. 16) in the terminal device 3, and is used as follows for checking (checking) the contents of the Web page that the user intends to browse. When the user attempts to browse a Web page with a WWW browser, a check program installed in the terminal device 3 is started, and the URL of the Web page matches the URL indicated in any of the defect information DT2 in the defect information database 3D1. It is determined whether or not to perform. Then, when the URL matches one of the URLs indicated in the defect information DT2, as shown in FIG. 10, the content of the defect information DT2 is displayed on the caution screen HG2, and the Web page being viewed has a defect. Attention to the user.
[0042]
The user may be allowed to freely set which of the various fault categories shown in FIG. For example, when a child uses the terminal device 3, a setting is made so that a warning is given when trying to access a “adult-oriented” Web page. Alternatively, no attention is given to the web pages of “broken link” and “non-existence of web page” because no harm is caused to the system of the terminal device 3, and no harm is caused to the web pages of “virus infection” and “attack”. There may be a setting so that attention is given.
[0043]
Inspection of the content of the Web page that the user intends to browse can be performed not by the terminal device 3 but by the defect information management server 1. When the URL of the Web page to be browsed on the terminal device 3 is specified, the failure inquiry unit 104 in FIG. 3 matches the URL with any one of the failure information DT2 stored in the failure information database 1D4. It is determined whether or not. If the URL matches any one of the URLs, the failure notification unit 105 transmits screen information for displaying the caution screen HG2 shown in FIG. 10 to the terminal device 3 together with the result information DT3. Then, the terminal device 3 displays the caution screen HG2 and stops accessing the Web page of the specified URL. If they do not match, the result information DT3 indicating that there is no defect is transmitted to the terminal device 3. Then, the terminal device 3 starts accessing the Web page of the specified URL.
[0044]
The money processing unit 106 includes a reward payment processing unit 161, a report fee processing unit 162, an inspection fee processing unit 163, and the like, and performs processing related to exchange of money performed between the provider 100, the user, and the WWW site 2. Do.
[0045]
The reward payment processing unit 161 performs a process for paying a reward to a user who has provided the defect information to the provider 100. When a large number of pieces of defect information on the same defect on the same Web page are received, a reward for the defect information is paid only to a predetermined number of persons (for example, the first ten persons) on a first-come-first-served basis. Further, among the predetermined number of users, a user who provides the defect information earlier is paid a higher reward (for example, 500 yen, 300 yen,..., On a first-come-first-served basis).
[0046]
That is, the bounty payment processing unit 161 counts the number of defects each time the defect information (defect report information DT1) indicating the same defect is received, and keeps the account of the information provider (user) until the number reaches the predetermined number. Is performed to transfer a predetermined amount of money.
[0047]
The report fee processing unit 162 performs a process for collecting a report fee from the WWW site 2, which is a report destination of the defect (a destination of the defect information DT2). For example, a process of deducting a fee from an account designated by the WWW site 2 is performed. Alternatively, an e-mail requesting the transfer of the charge to the account of the provider 100 is transmitted to the operator of the WWW site 2. These processes may be performed collectively for a predetermined period (for example, one month), or may be performed every time the defect information DT2 is transmitted. In addition, charging may be performed for each piece of defect information DT2 (a metered rate system) or may be performed according to a use period of the present service regardless of the number of the defect information DT2 (a fixed rate system).
[0048]
The inspection fee processing unit 163 performs a process for collecting from the user the provision fee of the inspection defect information DT2 distributed to the terminal device 3 by the defect information distribution unit 103 or the inspection fee performed by the defect inquiry unit 104. Do. As in the case of the reporting fee processing unit 162, the fee may be collected by withdrawing the account from the account designated by the user, and the fee may be charged on a pay-as-you-go or flat-rate basis.
[0049]
FIG. 11 is a flowchart illustrating a flow of a process of collecting defect information in the defect information management server 1, FIG. 12 is a flowchart illustrating an example of a flow of a process for a provider, and FIG. 13 is an example of a flow of a process for a WWW site. FIG. 14 is a flowchart for explaining an example of a flow of a process of giving the defect information to the subscriber's terminal device 3, and FIG. 15 is a flowchart of a process for giving the defect information to the non-subscriber terminal device 3. 6 is a flowchart for explaining an example of FIG.
[0050]
Next, the flow of processing of the defect information management server 1 and the terminal device 3 will be described with reference to flowcharts. As shown in FIG. 11, when the defect information management server 1 receives the defect information of the Web page found in the terminal device 3 (# 1), the defect information management server 1 notifies the terminal device 3 that the reception of the information has been completed. (# 2).
[0051]
It is confirmed whether or not the accepted defect information is already registered in the defect information database 1D4, and whether a reward for the defect information has already been paid to a predetermined number of persons (# 3). If both registration and payment have been made (Yes in # 3), the information provider (user) is notified of that fact (# 4), and the process ends.
[0052]
If the defect information is the information obtained for the first time (Yes in # 5), it is checked whether or not the content of the defect information is correct (# 6). As a result of the investigation, if the content is determined to be incorrect or cannot be confirmed (No in # 7), the fact is notified to the information provider (# 8), and the process is terminated. . If the contents are correct (Yes in # 7), the defect information is registered in the defect information database 1D4 (# 9).
[0053]
A process for a reward to be paid to the information provider and the like is performed according to a procedure as shown in FIG. 12 (# 10). First, the amount of the reward is determined based on the order in which the defect information was provided (# 101). As described above, when a plurality of pieces of defect information having the same content are received, the user who provides the earlier information is paid more reward. The information provider is notified of the result of the investigation on the defect information and the result of the evaluation of the reward (# 102). Then, a process for transferring the reward to the information provider's account is performed (# 103).
[0054]
In parallel with or before or after the process of step # 10, a process for a WWW site that publishes the Web page indicated in the defect information is performed according to a procedure as shown in FIG. 13 (# 11). By sending an e-mail as shown in FIG. 9 to the WWW site, a report is sent to the Web page having a problem (# 111). Then, a process for collecting a report fee from the WWW site is performed (# 112).
[0055]
Further, as shown in FIG. 14, when the defect information management server 1 requests the defect information DT2 for inspecting whether or not there is a defect in the Web page from the terminal device 3 (# 21), the terminal device 3 It is determined whether the user No. 3 has the right to use, that is, whether the user is a subscriber of the provider 100 (# 22). If there is a use right (Yes in # 22), the requested defect information DT2 is transmitted to the terminal device 3 (# 23). If there is no use right (No in # 22), the failure information DT2 is not transmitted, and the fact that there is no use right is notified (# 24).
[0056]
Note that a process as shown in FIG. 15 may be performed for a user who has not subscribed to the provider 100. That is, when a request for the defect information DT2 is received from the terminal device 3 together with information such as the user's name, contact information, and account number (# 31), a process for withdrawing the fee for the defect information DT2 from the account is performed (# 31). # 32). If the withdrawal is successful (Yes in # 33), the requested failure information DT2 is transmitted to the terminal device 3 (# 34). In the case of failure (No in # 33), the terminal device 3 is notified that charging could not be performed (# 35).
[0057]
According to the present embodiment, the operator of the WWW site can reduce the burden of monitoring the failure of his Web page. In addition, the provider that operates the defect information management server 1 increases a user's willingness to provide information by giving a reward to a user who has quickly provided defect information of a Web page, and effectively collects defect information. Can be collected. Further, the user of the terminal device can be efficiently prevented from accessing a defective Web page.
[0058]
FIG. 16 is a diagram illustrating an example of a functional configuration of the terminal device 3, and FIG. 17 is a flowchart illustrating an example of a processing flow of the terminal device 3 when the failure finding program is activated.
[0059]
In the present embodiment, the defect information is discovered by the user of the terminal device 3 and reported to the defect information management server 1 by the user inputting predetermined items in the defect report form HG1 shown in FIG. You may make it discover and report automatically, without depending on operation.
[0060]
In this case, a program (fault finding program) for realizing functions such as the pattern information database 301, the fault finding unit 302, and the fault reporting unit 303 as shown in FIG. 16 is installed in the terminal device 3. . In addition, the defect information management server 1 prepares pattern information DT4 indicating a characteristic pattern of various defects on the Web page. For example, pattern information DT4 indicating a word (keyword) frequently used in an adult Web page, or pattern information DT4 indicating a command or a command group frequently used in an attacking program is prepared. Further, every time a defect of a new Web page is found, the corresponding pattern information DT4 is prepared. Then, control is performed so that new pattern information DT4 is transmitted to each terminal device 3 periodically (for example, every week).
[0061]
In FIG. 16, the pattern information database 301 stores the pattern information DT4 received by the communication device 30a. When the user specifies the URL of the Web page, the Web page is realized from the WWW site
A source (code group written in a language such as hypertext or JavaScript) for downloading (constructing) is downloaded.
[0062]
The defect finding unit 302 checks whether or not the source of the Web page specified and downloaded by the user includes a pattern indicated by any of the pattern information DT4 stored in the pattern information database 301. . If the pattern is included, it can be determined that the Web page has a defect.
[0063]
When a defect is found, the defect reporting unit 303 notifies the user of the state of the defect, and checks whether the found defect matches the defect of any of the defect information DT2 stored in the defect information database 3D1. It is determined whether or not. If there is no match, after obtaining the permission of the user, information such as the URL of the Web page having the problem and its state is transmitted to the problem information management server 1 as the problem report information DT1 '. If there is a match, the fault is already registered in the fault information management server 1, and the process of transmitting the fault to the fault information management server 1 is not performed.
[0064]
That is, the terminal device 3 performs a process of automatically detecting a defect and reporting the defect to the defect information management server 1 according to the procedure shown in FIG. It is analyzed whether or not the Web page being viewed by the user has a problem (# 41). If no defect is found (No in # 42), the normal processing is performed (# 43). If a defect is found (Yes in # 42), it is determined whether or not the defect is already registered in the defect information management server 1 (# 44). If it is determined that it has not been registered yet (No in # 45), with the permission of the user (# 46), information on the found fault is reported to the fault information management server 1 (# 47). ).
[0065]
With such a configuration and processing, the trouble of providing the defect information for the user can be saved, and the efficiency of collecting the defect information for the WWW site can be increased. Further, by using the defect report form HG1 (see FIG. 7) described above in combination with the defect finding program, omission of collection of defect information can be reduced.
[0066]
In the case where the terminal device 3 does not have a large-capacity storage means (for example, a mobile phone device), the failure is determined based on the pattern information DT4 and the failure information DT2 stored in each database of the failure information management server 1. May be found and reported. In order to promote the use of the defect finding program, a reward (cooperation money) may be paid to a user who has installed the defect finding program on the terminal device 3. The defect information may be automatically transmitted to the defect information management server 1 without obtaining the permission of the user. In addition, the provision of the defect information may be performed by e-mail.
[0067]
Generally, when a program written in a language such as JavaScript is used to realize a Web page, a problem occurs depending on the use environment such as the model of the terminal device 3, the type and version of the browser, and the type of the OS. Or not. HTML has tags (codes) that are valid only for a specific type of WWW browser. Therefore, when a defect is found, the usage environment of the terminal device 3 may be reported to the defect information management server 1 together with the defect information.
[0068]
In the present embodiment, a higher reward is given to the user who provided the defect information earlier, but the same reward may be given to all the users. Points may be given instead of money as compensation for the failure information, and the accumulated points may be exchanged for prizes or services. A WWW site contracted with the provider 100 may be previously disclosed to each user.
[0069]
A person other than the provider 100 may manage the defect information management server 1. For example, even if a company having a large-scale in-house network installs the defect information management server 1 in its own computer center, and independently takes measures to prevent the terminal device 3 of the employee from being damaged by the defective Web page. Good.
[0070]
The defect information management server 1 can be used for collecting information other than the defect information of a Web page. For example, the WWW site 2 announces its desired information on a Web page and notifies the provider 100 (the defect information management server 1). Then, when the information is provided from the user of the terminal device 3 to the provider 100, the information is transferred to the WWW site 2.
[0071]
In addition, the configuration of the whole or each part of the defect information management server 1 and the terminal device 3, the configuration of the defect report form HG1, the configuration and contents of each database, the processing contents, the processing order, and the like are appropriately changed in accordance with the gist of the present invention. be able to.
[0072]
【The invention's effect】
ADVANTAGE OF THE INVENTION According to this invention, the burden of monitoring the malfunction of his Web page for the WWW site operator can be reduced. According to the fourth and fifth aspects of the present invention, it is possible to efficiently prevent a user from accessing a Web page having a problem. According to the sixth, seventh, and tenth aspects of the present invention, it is possible to automatically collect defects of a Web page found in a terminal device.
[Brief description of the drawings]
FIG. 1 is a diagram showing an example of the configuration of a defect information management system having a defect information management server and a terminal device according to the present invention.
FIG. 2 is a diagram illustrating an example of a hardware configuration of a defect information management server.
FIG. 3 is a diagram illustrating an example of a functional configuration of a defect information management server.
FIG. 4 is a diagram illustrating an example of a user information database.
FIG. 5 is a diagram showing an example of a site information database.
FIG. 6 is a diagram showing an example of a defect category database.
FIG. 7 is a diagram showing an example of a failure report form.
FIG. 8 is a diagram showing an example of a defect information database.
FIG. 9 is a diagram showing an example of an e-mail for reporting defect information.
FIG. 10 is a diagram illustrating an example of a caution screen.
FIG. 11 is a flowchart illustrating a flow of a process of collecting defect information in a defect information management server.
FIG. 12 is a flowchart illustrating an example of the flow of processing for a provider.
FIG. 13 is a flowchart illustrating an example of the flow of WWW site processing.
FIG. 14 is a flowchart illustrating an example of a flow of a process of giving defect information to a subscriber terminal device.
FIG. 15 is a flowchart illustrating an example of a flow of a process of providing defect information to a non-subscriber terminal device.
FIG. 16 is a diagram illustrating an example of a functional configuration of a terminal device.
FIG. 17 is a flowchart illustrating an example of a processing flow of a terminal device when a failure finding program is activated.
[Explanation of symbols]
1 Defect information management server
2 WWW site
3 Terminal device
101 Defect information acquisition unit (defect information acquisition means)
102 Defect reporting part (defect reporting means)
104 Defect Inquiry Unit (Defect Presence Determination Means)
105 Failure notification unit (result transmitting means)
161 Reward payment processing unit (reward giving means)
162 Report fee processing unit (report fee collection means)
163 Inspection fee processing unit (discrimination fee collecting means)
1D4 Bug information database (bug information database)
301 Pattern information database (pattern information storage means)
302 Defect finding unit (defect finding means)
303 Defect reporting part (defect reporting means)
30a communication device (defect information acquisition means)
DT1 bug report information (bug information)
DT3 result information (discrimination result)
DT4 pattern information

Claims (10)

A defect information management server that manages defect information relating to a defect of a Web page published on a WWW site,
Defect information acquisition means for acquiring, from the terminal device, the defect information of the defect of the Web page found when the user is browsing the Web page with the terminal device;
Reward providing means for performing a process for providing a reward for providing the defect information to a user of the transmission source of the defect information acquired by the defect information acquiring means,
Defect reporting means for reporting to a WWW site operator that publishes the Web page relating to the defect information acquired by the defect information acquiring means that there is a defect in the Web page;
A defect information management server comprising: The reward granting means, when the plurality of acquired defect information relate to the same defect on the same Web page, gives a reward only to a predetermined number of users who provided the defect information earlier.
The defect information management server according to claim 1. A report value collecting means for performing a process for collecting a price for reporting that there is a problem with the Web page from a WWW site that publishes the Web page;
The defect information management server according to claim 1 or 2. A defect information database that stores the defect information acquired by the defect information acquiring unit;
A failure presence / absence determination unit that determines whether there is a failure in a Web page requested by the terminal device user to browse, requested by the terminal device;
A result transmitting unit for transmitting a determination result by the defect presence / absence determining unit to the requesting terminal device,
The defect information includes a URL of a Web page related to the defect information,
The failure presence / absence determining means determines whether or not there is a failure in the Web page by comparing the URL of the Web page to be browsed with the URL of each failure information stored in the failure information database. Do
The fault information management server according to claim 1. Comprising a determination fee collecting means for performing processing for collecting a price for performing the determination from the user of the terminal device requesting the determination.
The defect information management server according to claim 4. A terminal device that can be connected to a defect information management server that manages defect information relating to a defect of a Web page,
Pattern information storage means for storing pattern information indicating the pattern for each defect pattern of the Web page;
By checking whether or not a code group for configuring a Web page being viewed by a user includes a pattern indicated by any of the pattern information, a defect included in the Web page is found. Bug finding means,
Defect reporting means for performing processing for reporting a defect found by the defect finding means to the defect information management server;
A terminal device comprising: Having a defect information acquisition means for acquiring the defect information managed by the defect information management server,
The defect reporting means, when the defect of the Web page found by the defect finding means is not shown in any of the defect information acquired by the defect information acquiring means, reports the defect to the defect information management. Perform processing to report to the server,
The terminal device according to claim 6. A defect reporting method for reporting defect information relating to a defect of a Web page published on a WWW site to the WWW site,
Acquiring from the terminal device the defect information of the defect of the Web page found when the user is browsing the Web page with the terminal device;
Performing a process for giving a reward of providing the defect information to the user of the transmission source of the obtained defect information,
Reporting to the operator of a WWW site that publishes the Web page related to the obtained defect information that there is a defect in the Web page;
A defect reporting method characterized by comprising: A computer program used for a computer that manages defect information related to a defect of a Web page published on a WWW site,
A process of acquiring, from the terminal device, the defect information on the defect of the Web page found when the user is browsing the Web page with the terminal device;
A process of performing a process for giving a reward of providing the defect information to a user of a source of the acquired defect information,
Processing for notifying the operator of the WWW site that publishes the Web page related to the acquired defect information that the Web page has a defect,
A computer program for causing a computer to execute. A computer program that can be connected to a defect information management server that manages defect information relating to a defect of a Web page, and is used for a computer having pattern information storage means that stores pattern information indicating the pattern for each defect pattern of the Web page. So,
By checking whether or not a code group for configuring a Web page being viewed by a user includes a pattern indicated by any of the pattern information, a defect included in the Web page is found. Processing,
A process of reporting a discovered defect to the defect information management server;
A computer program for causing a computer to execute.

Images