JP2003157210A - Method for collecting data and implementation device therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique capable of supporting an analysis taking into consideration a control rule at the time when a response page is prepared in analyzing an access status to a server form a client. SOLUTION: This technique has a step for acquiring and outputting contents definition data according to a control rule that corresponds to a page preparation request received from the client, a step for outputting control rule information showing the control rule used in acquiring the contents definition data, a step for transmitting to the client a response page obtained by attaching page category data and additional information data showing the contents of the control rule information to page text data; and a step for transmitting the additional information data in the transmitted response page to a collection server from the client.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data collection system that collects data indicating the access status of a client in an Internet environment such as WWW, and more particularly to a data collection system that collects data indicating the category and characteristics of a page accessed by a client. It is related to the technology effectively applied to.

[0002]

2. Description of the Related Art Currently, WWW (World Wide Web) is provided in a network called the Internet. The web client sends HTML (Hyper T
It is a client that receives data described in ext Markup Language), and HTTP (Hypert
ext Transfer Protocol), FTP (File Transfer Protoco
A protocol such as l) is used. Resources on the WWW are U
It can be referenced by RI (Uniform Resource Identifiers), and HTML data can include URIs to other resources.

W3C for HTML, HTTP, FTP, URI, etc.
It is described in various documents provided by (World Wide Web Consortium). In addition, general Internet technology is IE
SG (The Internet Engineering Steering Group), IETF (I
RFC (R
equest for Comment). RFC2396, 1866, 2080, 2396, etc. for HTML and URI, RFC2068, 2069, etc. for HTTP, and RFC765, etc. for FTP.

Many Web servers have a function of accumulating requests from clients as log data, and the access log of the Web server has a host name, IP address, time stamp, URI, etc. of the accessing client. Is accumulated. In addition, the Web server can specify the client that has repeatedly accessed by using the cookie, and thus the access status of each client can be recorded in the data separately from the Web server log. Such a method of accumulating the access situation based on the URI will be referred to as "prior art 1" below.

As another method of accumulating data on access status, pages are classified into typical categories according to the meaning and the corresponding categories are recorded when a page is accessed. There is a way.
Hereinafter, a method capable of accumulating page categories in this way will be referred to as "prior art 2". By using the conventional technique 2, log data can be aggregated for each accessed category.

Further, by sharing the client identification information by the cookie and the definition of the page category, the access statuses to a plurality of Web servers are accumulated in the log by using the conventional technique 2, and all the log data are recorded later. Can be aggregated into one and aggregated. A well-known application method is to include a URI for sending data to a server that stores log data in the HTML data that the client receives.

A hypertext analysis device and method for presenting the cause / improvement measure of the page structure problem of the hypertext system and easily improving the page structure is described in Japanese Patent Laid-Open No. 2001-166981. There is. Further, JP-A-2001-154777 describes a hypertext browsing device, a display control method thereof, and a recording medium capable of obtaining document data of a link destination by following a hypertext link.

[0008]

DISCLOSURE OF THE INVENTION Problems to be Solved by the Invention
URI is just a resource identifier expressed as a character string, and U
It does not directly represent the content of the resource pointed to by RI. Therefore, in Conventional Technique 1, there is a problem that it is difficult to perform analysis based on page contents using the accumulated data itself.

In the prior art 2, by embedding the page category in the page to be sent to the client, it is possible to store in the log what page the client accessed. However, there is a problem that the log data accumulated in the related art 2 does not retain details of what information was provided to the user of the client who accessed the server. For example, when the client user selects one search result in the situation where a list of some search results is displayed on the client, in the prior art 2, which selection remains as log data, but how many There is no information such as whether it was selected from among.

Further, in recent WWW-based information systems, a technique called personalization has been used in which different page contents are assigned to the same URI for each user or each client. The related art 2 has a problem that information regarding page customization does not remain. The lack of such information makes it difficult to assess the impact of personalization on user behavior, and will give appropriate results when performing some analysis using log data. May not be. For example, assume that the tendency of the hobby and preference of the client user is extracted from the log data of Conventional Technique 2. Even if the page category frequently seen by a certain user is found, it may indicate that this result represents the user's original taste or preference, or that the page of a specific category was preferentially presented by personalization. I can't tell if they are there.

The object of the present invention is to solve the above problems and to support the analysis in consideration of the control rule when the response page is generated when analyzing the log data representing the access status from the client to the server. To provide. Another object of the present invention is to provide a technique capable of supporting an analysis in consideration of the status of each item at the time of generating a response page when analyzing log data representing the access status from a client to a server. is there.

[0012]

SUMMARY OF THE INVENTION The present invention relates to a control rule used when a response page corresponding to a page generation request is created in a data collection system that collects data representing the access status from a client to a server. The information is stored in the action history database in the collection server.

In the data collection system of the present invention, when a page generation request is received from a client, the page category definition database is referenced, and page category data indicating a category corresponding to the received page generation request is read from the page category definition database. And outputs it to the page generation processing unit.

Further, after the content ID corresponding to the argument of the received page generation request is read from the control rule database, the content definition database is referred to by the content ID, and the response page corresponding to the page generation request is constructed. Content definition data indicating the content of each item is acquired and output to the page generation processing unit, and the page generation processing unit creates page text data using the content of each item in the output content definition data. The control rule information indicating the control rule used when the content definition data is acquired is also output to the page generation processing unit.

When both the page category data and the control rule information are output, the page generation processing unit generates additional information data indicating their contents by the additional information data generation processing unit, and then the generated page body. The additional information data is added to the data to generate output page data, and the output page data is transmitted to the client as a response page.

The client receives and displays the transmitted response page, and the additional information data therein is transmitted from the client to the collecting server. The collection server stores the page category data and the control rule information in the additional information data received from the client in the action history database in the collection server, and when analyzing the access status from the client to the server, the control rule The contents of the log data are corrected in consideration of the influence on the, and the accurate analysis is supported.

As described above, according to the data collection system of the present invention, the information of the control rule used when creating the response page corresponding to the page generation request is stored in the action history database in the collection server. When analyzing the log data indicating the access status from the client to the server, it is possible to support the analysis in consideration of the control rule when the response page is generated.

[0018]

BEST MODE FOR CARRYING OUT THE INVENTION A data collection system of one embodiment for collecting data representing the access status from a client to a server will be described below.

FIG. 1 is a diagram showing a schematic configuration and a data flow of the data collection system of this embodiment. As shown in FIG. 1, the data transmission / reception device 100 of the present embodiment includes a page generation processing unit 101, a page category output processing unit 102,
The content generation processing unit 103, the control rule output processing unit 104, the component output processing unit 105, the tag generation processing unit 106, and the feature amount extraction processing unit 107 are included.

The page generation processing unit 101 creates page body data using the contents of each item in the content definition data acquired by the content generation processing unit 103, and the tag generation processing unit 106 generates the page body data. It is a processing unit that adds the additional information data to generate output page data and transmits the output page data as a response page 113 to the client.

The page category output processing unit 102 is a processing unit which reads out from the page category definition database 108 the page category data indicating the category corresponding to the page generation request 112 received from the client and outputs it.

The content generation processing unit 103 refers to the content definition database 110 according to the control rule corresponding to the received page generation request 112 or executes the processing corresponding to the page generation request 112, and responds to the page generation request 112. It is a processing unit that acquires and outputs content definition data indicating the content of each item that constitutes the response page 113.

The control rule output processing unit 104 is a processing unit that outputs control rule information indicating a control rule used when the content definition data is acquired. The component output processing unit 105 is a processing unit that outputs the feature amount of each item in the acquired content definition data to the feature amount extraction processing unit 107.

When the page category data and at least either the control rule information or the page summary data are output, the tag generation processing unit 106 generates the additional information data indicating the content of the page category data as a tag, and the additional information data generation processing. It is a department. The feature amount extraction processing unit 107 is a processing unit that extracts the feature amount of each item output from the component output processing unit 105 and outputs it as page summary data.

The data transmission / reception device 100 includes a page generation processing unit 101, a page category output processing unit 102, a content generation processing unit 103, a control rule output processing unit 104, a component output processing unit 105, a tag generation processing unit 106, and a feature amount extraction. The program for functioning as the processing unit 107 is recorded on a recording medium such as a CD-ROM and stored in a magnetic disk or the like, and then loaded into a memory and executed. The recording medium for recording the program is C
A recording medium other than the D-ROM may be used. The program may be installed in the information processing apparatus from the recording medium and used, or the recording medium may be accessed through the network to use the program.

The data transmission / reception device 100 has a page category definition database 108, a feature definition database 109, a content definition database 110, and a control rule database 111.

Page category definition database 108
Is the page generation request 1 received from the client
12 is a database that stores page category definition data indicating a category of a response page 113 that is responded to.

The feature definition database 109 is a database that stores the contents of the calculation used when calculating the feature amount of each item in the content definition data. The content definition database 110 is a database that stores content definition data that defines the content of the content that forms the response page 113 to the page generation request 112. Control rule database 1
Reference numeral 11 is a database that stores information indicating control rules when generating the response page 113 for the page generation request 112.

The collection server 120 includes the data reception processing unit 1
21, a data storage processing unit 122, and an analysis support processing unit 1
And 23. The data reception processing unit 121 controls the page category 116 indicating the category corresponding to the page generation request 112 by the client and the control rule for acquiring each item constituting the response page 113 corresponding to the page generation request 112. Rule information 117 or its page generation request 112
Additional information 11 representing any one of page summaries 118 showing the feature amount of each item constituting the response page 113 corresponding to
4 is a processing unit that receives 4 from the client.

The data storage processing unit 122 uses the page category 1 in the additional information 114 received from the client.
16 and control rule information 117 or page summary 118
Is a processing unit that stores the action history database.

The analysis support processing unit 123 corrects the data in the action history database according to the contents of the control rule information 117 to support the analysis of the action history and presents the collected page summary 118. It is a processing unit that supports analysis of action history.

The collection server 120 is replaced by the data reception processing unit 12
1. Data storage processing unit 122 and analysis support processing unit 123
The program for functioning as is recorded on a recording medium such as a CD-ROM and stored in a magnetic disk or the like, and then loaded into a memory and executed. The recording medium for recording the program may be a recording medium other than the CD-ROM. The program may be installed in the information processing apparatus from the recording medium and used, or the recording medium may be accessed through the network to use the program. In this embodiment, the page generation request 112 is a URI and the response page 113 is HTML data.

FIG. 2 shows the data transmitting / receiving apparatus 10 of this embodiment.
It is a figure which shows the example of internal data of 0. The page category definition data 201 in FIG. 2 represents the structure of data stored in the page category definition database 108 and is in a table format. URI 205, page category 206,
The page category ID 207 represents an item of the table included in the page category definition data 201.

The feature definition data 202 represents the structure of data stored in the feature definition database 109,
The data item 208, the operation content 209, and the operation ID 210 are
The items of the table included in the feature definition data 202 are shown.

The content definition data 203 represents the structure of data stored in the content definition database 110, and has a content ID 211 and a content name 21.
2, price 213, inventory 214, and image file name 215 represent the items of the table included in the content definition data 203.

The control rule information 204 represents the structure of the data stored in the control rule database 111, the condition 216 indicating the argument of the page generation request to which the control rule is applied, and the page generation based on the control rule. Content ID 217 for identifying the content used in the, and the rule ID for identifying the control rule
218 and 218.

FIG. 3 shows a data transmission / reception device 10 of this embodiment.
It is a figure which shows the input / output data example of 0. The page generation request data 301 in FIG. 3 represents an example of the page generation request 112 input to the data transmitting / receiving apparatus 100. "?" In page generation request data 301 is U
It is a delimiter in the RI definition, and the page generation request data 301 is the calling program 305 and the argument 30.
It consists of 6. The calling program 305 uses the argument 30 to refer to the program called by the client.
6 represents an argument to the program.

The output page data 302 represents the content of the response page 113 output from the data transmitting / receiving apparatus 100. Additional information data 303 and page body data 3
Reference numeral 04 is a component of the output page data 302, additional information data 303 represents the additional information 114, and page body data 304 represents the page body 115. “?” And “&” in the additional information data 303 are delimiters in the URI definition, and the additional information data 303 includes the HTML tag 307,
Collection program name 308, page category data 30
9, control rule information 310, average price data 311, product number data 312, and out-of-stock number data 313.

The page category data 309 is the page category obtained from the page category output processing unit 102, the control rule information 310 is the control rule information output from the control rule output processing unit 104, and the average price data 311.
The product number data 312 and the out-of-stock number data 313 are summary information from the feature amount extraction processing unit 107.

"IMG" in the HTML tag 307 is a keyword for including an image in the page, and "SRC" is a keyword for specifying the URI of the image resource. When a general client device capable of processing HTML receives an HTML tag such as the HTML tag 307, the collection program name 308
Requesting an image resource from the collection server 120 indicated by
In this embodiment, at that time, the page category data 30
9. The process of transmitting the control rule information 310, the average price data 311, the product number data 312, and the out-of-stock data 313 is performed.

As described above, the feature amount of the page received by the client device and the control rule used for page generation are included in the received data in advance so that they can be collected. There are features. This makes it possible to collect, as log data, information about what content the user of the client device was looking at and what control rule the page was created for. However, in the present embodiment, it is not necessary to always store the control rule information and the summary information in a pair in the additional information data 303, and it is possible to selectively store them. Therefore, the additional information data 303 includes page category data 309, control rule information 310, average price data 311, product number data 312, and out-of-stock number data 313.
You can store and operate what you need.

FIG. 4 shows a data transmission / reception device 10 of this embodiment.
It is a flow chart which shows the processing procedure of 0. Step 4
The page generation processing unit 10 of the data transmitting / receiving device 100
When accepting the access from the client device, 1 requests the input of the user ID and password of the user and accepts the login of the user.

At step 402, the menu page is added by referring to the personal information of the user who has accepted the login and adding an argument corresponding to the control rule for generating a page according to the hobby and preference of the user to the URI. Is generated and the generated menu page is transmitted to the client device.

When the user clicks a specific URI on the transmitted menu page, a page generation request 11 is sent from the client device to the data transmitting / receiving device 100.
2 is transmitted.

As shown in FIG. 1 (1), the page generation processing unit 101 receives the page generation request 112 transmitted from the client device in step 403 and is included in the page generation request 112 as shown in FIG. 1 (2). The calling program 305 is output to the page category output processing unit 102.

When the page category output processing unit 102 receives the calling program 305 in step 404,
By referring to the page category definition data 201 stored in the page category definition database 108, record data whose URI 205 value matches the calling program 305 is searched for. If matching data is found, the process proceeds to step 405, and the value of the page category ID 207 and the item name of the page category ID 207 included in the found record data are output to the page generation processing unit 101. If no match is found, proceed to step 406,
The page generation processing unit 101 displays a value indicating that the search has failed.
Notify to. When the page generation processing unit 101 receives the value of the page category ID 207 and the notification indicating that the item name or the search has failed, the page generation processing unit 101 starts generating the additional information data 303 as the data indicating the page category 116 by the tag generation processing unit 106. Holds the value.

Next, in step 407, the page generation processing unit 1
01 checks whether or not the argument 306 for designating the control rule is designated in the page generation request 112, and if the request uses the control rule, the page generation request 112 is designated as shown in FIG. 1 (3). The included argument 306 is output to the content generation processing unit 103 and the process proceeds to step 408.

In step 408, the content generation processing unit 1
03 receives the argument 306, refers to the control rule information 204 stored in the control rule database 111, and searches for record data in which the value of the condition 216 matches the argument 306. If no match is found, the process proceeds to step 413, a value indicating that the search has failed is output to the page generation processing unit 101, and if a match is found, the process proceeds to step 409.

In step 409, the content definition data 203 stored in the content definition database 110 is referred to by using the value of the content ID 217 of the found record data, and the record data having the matching value of the content ID 211 is searched. If no match is found, the process proceeds to step 413, a value indicating that the search has failed is output to the page generation processing unit 101, and if a match is found, the process proceeds to step 410.

In step 410, the name and value of the content name 212, the price 213, the inventory 214, and the image file name 215 that the record data found by searching the content definition data 203 have are output to the page generation processing unit 101.

In step 411, the page generation processing unit 101
Receives the name and value of the content name 212, the price 213, the inventory 214, and the image file name 215, the page body data 304 is created.

In step 412, the control rule output processing unit 1
In the processing of the content generation processing unit 103 of (3), when there is record data in which the value of the condition 216 matches the argument 306 in the control rule information 204, 04 matches as in (1) of FIG. The value of the rule ID 218 included in the record data and the item name are output to the page generation processing unit 101. Upon receiving the name and value of the rule ID 218, the page generation processing unit 101 holds the value as data representing the control rule information 117 until the tag generation processing unit 106 starts to create the additional information data 303.

As a result of checking in step 407, when the argument 306 for designating the control rule is not designated in the page generation request 112, the process proceeds to step 421, and the processing requested by the request, such as product search processing. To execute.

In step 422, the processing result is acquired from the processing unit that has executed the processing, such as a product search engine,
In step 423, the content definition data 203 indicating the contents of each item for displaying the processing result such as the search processing result is generated, and the process proceeds to step 414.

In step 414, the component output processing unit 10
5 shows a case where there is matching record data in the process of searching the content definition data 203 of the content generation processing unit 103 of (3) or when the content definition data 203 is generated by executing the request process. Content ID 211, price 21 as in 1 (5)
3. The item name and value of each item in the content definition data 203 such as inventory 214 are output to the feature amount extraction processing unit 107.

In step 415, the feature quantity extraction processing unit 107
When receiving the item name and value such as the content ID 211, the price 213, the inventory 214, etc., performs the process for each received item. First, referring to the data item 208 of the feature definition data 202 stored in the feature definition database 109, the record item whose value of the data item 208 matches the item name of the content ID 211, the price 213, the inventory 214, etc. is searched and the record data is matched. If found, go to step 416.

In step 416, the value of the matched item among the items such as the content ID 211, the price 213, and the stock 214 is calculated based on the value of the calculated content 209 of the matched record data, and the calculated value is compared with the value of the calculated ID 210. The combination is output to the page generation processing unit 101. For example, in the case of processing for the content ID 211, the number of contents included in the page is calculated, and the page generation processing unit 10
It is output to 1.

In step 417, it is checked whether the feature amount calculation processing has been completed for all items, and if the processing of all items has not been completed, step 415
Then, similar processing is performed for other items such as the price 213 and the stock 214.

In step 418, the page generation processing unit 101
Receives the value of the operation ID 210 and the operation result, and holds the value as data representing the page summary 118 until the tag generation processing unit 106 starts to create the additional information data 303.

As shown in FIG. 1 (6), in step 419, the page generation processing unit 101 calls the tag generation processing unit 106 when the data representing the page category 116, the control rule information 117, and the page summary 118 is complete, and calls the additional information. Instruct to create the data 303.

The tag generation processing unit 106 creates page category data 309 from the data representing the page category 116 output by the page category output processing unit 102, and represents the control rule information 117 output from the control rule output processing unit 104. The control rule information 310 is created from the data, and the average price data 311, the product quantity data 312, and the out-of-stock quantity data 313 are created from the data representing the page summary output from the feature quantity extraction processing unit 107, and the additional information data 303 is created. To generate.

Next, at step 420, the page generation processing unit 1
01 adds additional information data 303 to the generated page body data 304 to form output page data 302, and then transmits this as response page 113 to the client device.

The control rule information 117 of this embodiment is the internal state of the content generation processing unit 103, the page summary 1
Reference numeral 18 represents a summary of the content generation result. The feature of this embodiment lies in embedding information relating to content generation in a page in this way.

On the other hand, when the transmitted response page 113 is received and displayed by the client device, the tag process in the additional information data 303 is executed by the client device and is indicated by the collection program name 308 in the additional information data 303. The requested processing of the image resource to the collection server 120 is executed, and at that time, the page category data 309, the control rule information 310, the average price data 311, the product number data 312, and the out-of-stock number data 313 are transmitted to the collection server 120. .

The data reception processing unit 12 of the collection server 120
1 receives a request for an image resource from a client device, reads page category data 309, control rule information 310, average price data 311, product number data 312, and out-of-stock number data 313 from the arguments of the request, and the client device The page category request 116 corresponding to the page generation request 112, the control rule information 117, and the additional information 114 indicating the page summary 118 are received from the client device.

Then, the data storage processing unit 122 of the collection server 120 receives the page category data 309, the control rule information 310, the average price data 311, and the product number data 31 in the additional information 114 received from the client device.
2. The process of storing the out-of-stock data 313 in the action history database is performed.

Analysis support processing unit 123 of the collection server 120
Processing for correcting the data in the action history database according to the content of the control rule information 117 to support the analysis of the action history, or presenting the collected page summary 118 to support the analysis of the action history. I do.

As described above, in this embodiment, the collection server 1
Average price data 31 in the behavior history database in 20
1. Since the information of the page summary 118 indicating the features of the page such as 1, the number-of-products data 312, the out-of-stock number data 313, etc. is accumulated, the analysis support processing unit 123 of the collection server 120 stores the data in the collected page summary 118. It can be presented to support the analysis of the action history, and the analysis can be performed based on the page content. For example, when a list of search results is displayed on the client device and the user of the client device selects one search result, the number of products selected is analyzed, and the product is out of stock. It is possible to analyze the relationship between the number of out-of-stock items and the frequency of visits, such as whether or not the frequency of visits is decreasing due to the large number of items.

Since the analysis support processing unit 123 of the collection server 120 of this embodiment stores the control rule information 310 in the action history database in the collection server 120, it differs for each user or client for the same URI. When a technology called personalization for allocating different page contents is used, it is possible to analyze log data in consideration of the effect of personalization on customization of the page on the user's behavior. For example, when extracting the tendency of the hobby and preference of the client user from the behavior history database in the collection server 120, after correcting the log data in consideration of the influence of the control rule used in the customization of the page, a certain use By examining the page categories that people frequently look at, it is possible to eliminate the influence that the pages of a specific category are preferentially presented by personalization, and obtain the user's original hobbies and tastes as an analysis result.

Here, when the log data is modified in consideration of the influence of the control rule, the page generation is performed using the control rule and the page generation is performed without using the control rule. By checking the difference in the selection frequency of the items in the generated page, the expected value indicating the expected increase in the selection frequency when using the control rule is obtained in advance, and the control rule is used. When analyzing the log data, it is possible to support more accurate analysis of the action history by making a correction corresponding to the expected value of the control rule.

In the processing procedure shown in FIG. 4, the control rule is specified by the argument 306 of the page generation request 112. However, when a predetermined item in the response page 113 is selected by the client, the control rule is set. May be changed to a control rule for generating a response page corresponding to the predetermined item, and the dynamically changed content of the control rule may be collected. For example, as a result of presenting the product list of furniture in step 420 by the response page 113 generated by the control rule corresponding to the argument 306 of the page generation request 112, as a result, "chair" which is the product in the product list is put in the shopping cart. When the operation is performed by the user, the control rule is changed to present a product such as a "desk" which is expected to be purchased as a set with the product in the shopping cart, and the process proceeds to step 408. Response page 113 in which the processing flow is changed and the additional information data 303 indicating the dynamically changed control rule information is added
To be sent to the client device. By this processing, it becomes possible to support the analysis of the action history in consideration of the dynamically changed control rule.

FIG. 5 is a diagram showing an application example of the product search system of this embodiment. The product search system 400 of FIG.
Represents an embodiment in which the data transmission / reception device 100 is applied to a product search, and the page generation processing unit 101
It is a component of the Web server 402. The product search engine 403 is a search engine for searching for products,
The product search result output processing unit 404 is a product search engine 40.
It is a component of 3.

Here, the product search engine 403 is the content generation processing unit 103 of FIG. 1, the product search result output processing unit 404 is the component output processing unit 105 of FIG. 1, and the product management database 406 is the content definition database 110 of FIG. Respectively correspond to. The operation of the product search system 400 will be described below with reference to FIGS. 3 and 5 in the order of parenthesized numbers in FIG.

First, as shown in FIG. 5A, the Web browser 4
01 is a page generation request 1 for using HTTP to perform a product search without using a control rule on the Web server 402.
12 is transmitted. Next, when the Web server 402 receives the page generation request 112, the page generation processing unit 10
The page generation request 112 is output to 1. Next, the page generation processing unit 101 generates the response page 113, and HT
Send to Web browser 401 using TP.

As shown in FIG. 5B, the web browser 401
Receives the response page 113, processes the additional information 114 included in the response page 113, and uses HTTP to acquire the collection program name 30 included in the additional information data 303.
8 to page category data 309, average price data 311, product number data 31 obtained by the product search process
2 and the summary information such as the out-of-stock data 313 are transmitted. Here, the "collector included in the request
“Ver” is the collection server 405.

As shown in FIG. 5C, the data reception processing section 121 of the collection server 405 uses the page category data 30.
9 and the summary information such as the average price data 311, the number-of-goods data 312, the number-of-stock data 313, etc., and the data storage processing unit 122 saves them in the action history database 407. Web browser 4 if cookies are available
Specify 01 and record it so that the received data can be distinguished for each Web browser. A typical recording method is to associate each received item with the identifier of the Web browser.

As described above, the feature of this example is that the page feature amount, which summarizes the search results such as the average price, the number of products, and the number of sold items, is transmitted to the Web browser 401 in advance in addition to the page category. This allows the web browser 40
It becomes possible to collect what kind of information was displayed for one user as log data.

FIG. 6 is a diagram showing an application example of the product recommendation system of this embodiment. The product recommendation system 500 in FIG. 6 illustrates an embodiment in which the data transmitting / receiving apparatus 100 is applied to product recommendations, and the page generation processing unit 101 is a component of the Web server 502.
The recommendation engine 503 represents an engine that selects products recommended to the user, and the recommendation rule output processing unit 504 and the recommendation result output processing unit 505 are components of the recommendation engine 503.

Here, the recommendation engine 503 is shown in FIG.
1, the recommendation rule output processing unit 504 is the control rule output processing unit 104 of FIG. 1, the recommendation result output processing unit 505 is the component output processing unit 105 of FIG. 1, and the product management database 507 is the content of FIG. The definition database 110 and the recommendation rule database 508 are the control rule database 111 of FIG.
Respectively correspond to. Hereinafter, referring to FIG. 3 and FIG.
The operation of the product recommendation system 500 will be described in the order of the parenthesized numbers inside.

As shown in FIG. 6A, the Web browser 501
Sends a page generation request 112 specifying a control rule as an argument to the Web server 502 using HTTP. Next, the web server 502 is the page generation processing unit 101.
The page generation request 112 received is output. Next, the page generation processing unit 101 outputs the output page data 302.
Web page 501 using HTTP
Send to.

As shown in FIG. 6B, the Web browser 501
Receives the output page data 302, processes the additional information data 303 included in the output page data 302,
Page category data 3 to the URI of the collection program name 308 included in the additional information data 303 using HTTP
09, control rule information 310, and average price data 31
1, summary information such as the product quantity data 312 and the out-of-stock quantity data 313 are transmitted. Here, the “collect server” included in the request is the collection server 506.

As shown in FIG. 6 (3), the data reception processing section 121 of the collection server 506 uses the page category data 30.
9, control rule information 310, and average price data 31
1, the summary information such as the product quantity data 312 and the out-of-stock quantity data 313 are received, and the data storage processing unit 122 saves the summary information in the action history database 509. When the cookie can be used, the Web browser 501 is specified and recorded so that the received data can be distinguished for each Web browser. A typical recording method is to associate each received item with the identifier of the Web browser.

As described above, in addition to the same page category and page feature amount as in the case of the product search process, the control rule indicating the page generation condition is transmitted to the Web browser 501 in advance. is there. This makes it possible to collect, as log data, how the information displayed to the user of the web browser 501 was generated.

As described above, according to the data collection system of this embodiment, the information of the control rule used when creating the response page corresponding to the page creation request is stored in the action history database in the collection server. So
When analyzing the log data indicating the access status from the client to the server, it is possible to support the analysis in consideration of the control rule when the response page is generated.

According to the data collection system of this embodiment, the summary information of each item used when creating the response page corresponding to the page generation request is stored in the action history database in the collection server. When analyzing log data representing the access status from the server to the server, it is possible to support the analysis in consideration of the status of each item when the response page is generated.

[0086]

According to the present invention, since the information of the control rule used when creating the response page corresponding to the page generation request is stored in the action history database in the collecting server, the access status from the client to the server is stored. It is possible to support the analysis in consideration of the control rule at the time of generating the response page when analyzing the log data representing the.

[Brief description of drawings]

FIG. 1 is a diagram showing a schematic configuration and a data flow of a data collection system of this embodiment.

FIG. 2 is a diagram showing an example of internal data of the data transmission / reception device 100 of the present embodiment.

FIG. 3 is a diagram showing an example of input / output data of the data transmission / reception device 100 of the present embodiment.

FIG. 4 is a flowchart showing a processing procedure of the data transmission / reception device 100 of the present embodiment.

FIG. 5 is a diagram showing an application example of the product search system of the present embodiment.

FIG. 6 is a diagram showing an application example of the product recommendation system of the present embodiment.

[Explanation of symbols]

100 ... Data transmitting / receiving device, 112 ... Page generation request, 113 ... Response page, 114 ... Additional information, 115
... page body, 116 ... page category, 117 ... control rule information, 118 ... page summary, 120 ... collection server, 101 ... page generation processing section, 102 ... page category output processing section, 103 ... content generation processing section, 104
Control rule output processing unit 105, component output processing unit 106, tag generation processing unit 107, feature amount extraction processing unit 108, page category definition database 109
... Feature definition database, 110 ... Content definition database, 111 ... Control rule database, 121 ...
Data reception processing unit, 122 ... Data storage processing unit, 123
... analysis support processing unit, 200 ... data transmission / reception device internal data, 201 ... page category definition data, 202 ... feature definition data, 203 ... content definition data, 204 ...
Control rule information, 205 ... URI, 206 ... Page category, 207 ... Page category ID, 208 ... Data item,
209 ... Operation content, 210 ... Operation ID, 211 ... Content ID, 212 ... Content name, 213 ... Price, 214 ...
Inventory, 215 ... Image file name, 216 ... Conditions, 217
... content ID, 218 ... rule ID, 300 ... data transmitting / receiving device input / output data, 301 ... page generation request data, 302 ... output page data, 303 ... additional information data, 304 ... page body data, 305 ... calling program, 306 ... Argument, 307 ... HTML tag, 308
… Collection program name, 309… Page category data,
310 ... Control rule information, 311 ... Average price data, 3
12 ... Product number data, 313 ... Out-of-stock data, 400
… Product search system, 401… Web browser, 402… W
eb server, 403 ... Product search engine, 404 ... Product search result output processing unit, 405 ... Collection server, 406 ... Product management database, 407 ... Behavior history database, 5
00 ... Merchandise recommendation system, 501 ... Web browser, 502 ... Web server, 503 ... Recommendation engine, 504 ... Recommendation rule output processing unit, 505 ... Recommendation result output processing unit, 506 ... Collection server, 507
... commodity management database, 508 ... recommendation rule database, 509 ... action history database.

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Toyohisa Morita             1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture             Ceremony company Hitachi Systems Development Laboratory

Claims (16)

[Claims] 1. A data collection method for collecting data indicating a status of access from a client to a server, the step of reading out and outputting page category data indicating a category corresponding to a page generation request received from a client from a page category definition database. A step of referring to the content definition database according to the control rule corresponding to the received page generation request, and acquiring and outputting content definition data indicating the contents of each item constituting the response page corresponding to the page generation request; A step of creating page body data using the contents of each item in the output content definition data, and a step of outputting control rule information indicating a control rule used when the content definition data is acquired. , Previous A step of generating additional information data indicating the contents of the page category data and the control rule information, and adding the additional information data to the generated page body data to generate output page data, and outputting the output page data to a response page. And a step of transmitting the additional information data in the transmitted response page from the client to a collection server as a data collection method. 2. The data according to claim 1, further comprising a step of storing page category data and control rule information in the additional information data transmitted from the client in an action history database in a collection server. Collection method. 3. The process of reading the content definition data according to the control rule is to read the content definition data identified by the content ID corresponding to the argument of the page generation request from the content definition database. The data collection method according to claim 1 or claim 2. 4. When a predetermined item in the response page is selected by a client, the control rule is changed to a control rule for generating a response page corresponding to the predetermined item. The data collection method according to any one of claims 1 to 3. 5. The method according to claim 1, wherein the data transmitted from the client is corrected according to the content of the control rule to support the analysis of the action history. Data collection method. 6. A data collection method for collecting data representing a status of access from a client to a server, wherein page category data indicating a category corresponding to a page generation request received from a client is read out from a page category definition database and output. And a step of executing a process corresponding to the received page generation request and acquiring and outputting content definition data indicating the contents of each item forming a response page corresponding to the page generation request, and the output Creating page body data using the contents of each item in the content definition data; extracting feature quantities of each item in the acquired content definition data and outputting as page summary data; Data and page summary Generating additional information data indicating the contents of the data, adding the additional information data to the generated page body data to generate output page data, and transmitting the output page data to the client as a response page. And a step of transmitting the additional information data in the transmitted response page from the client to the collection server. 7. The data collection method according to claim 6, further comprising the step of storing page category data and page summary data in the additional information data transmitted from the client in an action history database. 8. The feature amount is extracted by performing a predetermined operation on each item in the acquired content definition data. Data collection method. 9. The data collecting method according to claim 6, wherein the collected page summary data is presented to support analysis of a behavior history. 10. A response page to which a tag for transmitting additional information data is transmitted to the collection server is transmitted to the client, and the client executes the processing of the tag to transmit the additional information data from the client to the collection server. The data collection method according to any one of claims 1 to 9, wherein 11. A page for reading and outputting page category data indicating a category corresponding to a page generation request received from a client from a page category definition database in a data transmission / reception device for transmitting / receiving data indicating a status of access from a client to a server. According to the category output processing unit and the content definition database according to the control rule corresponding to the received page generation request, the content definition data indicating the contents of each item constituting the response page corresponding to the page generation request is acquired. A content generation processing unit for outputting, a control rule output processing unit for outputting control rule information indicating a control rule used at the time of acquisition of the content definition data, and contents of the page category data and the control rule information. An additional information data generation processing unit that generates additional information data, and page body data is created using the contents of each item in the output content definition data, and the additional information data is added to the body data. A data transmission / reception device, comprising: a page generation processing unit that generates output page data and transmits the output page data as a response page to a client. 12. A page for reading and outputting page category data indicating a category corresponding to a page generation request received from a client from a page category definition database in a data transmission / reception device for transmitting / receiving data indicating a status of access from a client to a server. A category output processing unit, and a content generation process for executing a process corresponding to the received page generation request and acquiring and outputting content definition data indicating the contents of each item forming a response page corresponding to the page generation request. Section, a feature quantity extraction processing section that extracts the feature quantity of each item in the acquired content definition data and outputs it as page summary data, and additional information data indicating the content of the page category data and page summary data Additional information day Data generation processing section and page text data is created using the contents of each item in the output content definition data, the additional information data is added to the text data to generate output page data, and the output A data transmission / reception device, comprising: a page generation processing unit that transmits page data to a client as a response page. 13. A data collection method for collecting data representing a status of access from a client to a server, comprising page category data indicating a category corresponding to a page generation request by a client, and a response page corresponding to the page generation request. A step of receiving additional information data indicating control rule information indicating a control rule for acquiring each item from the client, and page category data and control rule information in the additional information data received from the client. And a step of correcting the data in the action history database according to the content of the control rule to support the analysis of the action history. 14. A data collection method for collecting data representing a status of access from a client to a server, comprising page category data indicating a category corresponding to a page generation request by a client, and a response page corresponding to the page generation request. Receiving additional information data representing page summary data indicating the feature amount of each item from the client, and storing page category data and page summary data in the additional information data received from the client in the action history database. A method for collecting data, comprising: a step of presenting the collected page summary data to support analysis of a behavior history. 15. A collection server that collects data indicating a status of access from a client to a server, and configures page category data indicating a category corresponding to a page generation request by the client and a response page corresponding to the page generation request. A data reception processing unit that receives additional information data indicating control rule information indicating a control rule for acquiring each item from the client, and page category data and control rule information in the additional information data received from the client. A data storage processing unit that stores the action history database in the collection server,
A collection server, comprising: an analysis support processing unit that corrects data in the action history database according to the content of a control rule to support analysis of an action history. 16. A collection server that collects data indicating a status of access from a client to a server, and configures page category data indicating a category corresponding to a page generation request by the client and a response page corresponding to the page generation request. A data reception processing unit that receives additional information data representing page summary data indicating the feature amount of each item from the client, and page category data and page summary data in the additional information data received from the client in an action history database. A collection server, comprising: a data storage processing unit that stores the data; and an analysis support processing unit that presents the collected page summary data to support the analysis of the action history.