JP2014096117A - Web browsing history acquisition system and web browsing history management device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a processing load in a user terminal or a proxy server upon acquiring a Web page browsing history.SOLUTION: According to the present invention, a user terminal is configured to: detect a page transition event generated by a Web browser and a click event; store event information in event generation storage means; and transmit the event information to a proxy server. A proxy server is configured to: acquire the event information from the user terminal; store a browsing history serving as a history providing a Web content to the user terminal and the event information in association with each other in browsing history storage means; store a HTML of the Web content as a HTML file; analyze the browser history of the browser history storage means; generate a history expressing a parental relation between frames; and add the history obtained by a browsing history analysis means to the browsing history storage means.

Description

  The present invention relates to a web browsing history acquisition system, a web browsing history management apparatus, and a program for acquiring a browsing history of a web page (including a web page divided into frames) browsed by a user, and in particular, a user browses a web page. The present invention relates to a Web browsing history acquisition system, a Web browsing history management apparatus, and a program that share a browsing history with a terminal and a proxy server.

  As a technique for acquiring a browsing history, there is a system that acquires a browsing history of a Web page (including a Web page divided into frames) in a terminal where a user browses a Web page (see, for example, Patent Document 1). In this system, the browser browsing history is accumulated in the user terminal, and the display content, display URL, display completion event, and the like are acquired.

  In addition, when a user browses a web page via a proxy server, there is a system that acquires a web browsing history in the proxy server (see, for example, Patent Document 2).

JP 2011-90384 A JP 2006-48505 A

  However, in the method of acquiring the browsing history in the user terminal as shown in Patent Document 1 described above, when acquiring the HTML of the Web page displayed as the browsing history, the processing load increases and the terminal has low processing performance. There was a problem that could not be applied.

  In addition, in the proxy server as shown in Patent Document 2, in the method of acquiring the browsing history, when the display using the cache of the web browser is performed on the user terminal, there is no problem that the proxy server records, and In order to grasp the transition of the frame page as accurately as possible, it is necessary to analyze the src attribute of <frame> tag and <iframe> tag by parsing HTML, and the processing load on the proxy server is heavy. There is a problem of becoming.

  The present invention has been made in view of the above points, and a Web browsing history acquisition system and a Web browsing history that can reduce the processing load on a user terminal or a proxy server when acquiring a Web page browsing history An object is to provide a management apparatus and a program.

In order to solve the above problems, the present invention (Claim 1) is a Web browsing history acquisition system for acquiring a browsing history of a Web page divided into frames having a parent-child relationship,
A user terminal and a proxy server,
The user terminal is
An event detection / transmission means for detecting a page transition event and a click event generated by the Web browser, storing event information in the event generation storage means, and transmitting the event information to the proxy server;
The proxy server is
The event information is acquired from the user terminal, and the browsing history, which is a history of providing the Web content to the user terminal, is stored in the browsing history storage unit in association with the event information, and the HTML of the Web content is converted into an HTML file. Browsing history acquisition means for storing;
Analyzing the browsing history of the browsing history storage means, generating a history representing a parent-child relationship of frames;
Browsing history recording means for additionally writing the history obtained by the browsing history analysis means to the browsing history storage means.

  Further, according to the present invention (Claim 2), in the browsing history analysis means of the proxy server according to Claim 1, the event information received from the user terminal and the browsing history of the browsing history storage means are Collation means for collating the event information with the URL of the browsing history by date and time is included.

  Further, according to the present invention (Claim 3), in the collation unit according to Claim 2, when the collation target is not found as a result of collation with the event information and the URL of the browsing history and the date and time, Includes means for searching backwards in time.

  Further, according to the present invention (Claim 4), in the browsing history appending means, the event information received from the user terminal by the collating means and the browsing history of the browsing history storage means are combined with the event information and the browsing history. If there is a browsing history that is not associated with the browsing history storage unit as a result of collating the URL with the date and time, the browsing history that is not associated is transmitted to the user terminal, and the event occurrence storage unit of the user terminal Includes means to add to

  According to the present invention, since the user terminal performs only a light process of acquiring a display completion event and does not perform an HTML acquisition process, the load on the user terminal can be reduced.

  When analyzing HTML on the proxy server, use the event generated by the Web browser on the user terminal. In other words, it is possible to perform analysis using the transition of the entire Web page, the difference of transition of only the child frame, and mouse click event. For this reason, it is not necessary to perform the analysis for creating the frame structure table or the link analysis table as in Patent Document 2 described above, and the processing in the proxy server can be reduced.

  Also, in the conventional technology, even when a display using a Web browser cache is performed, no record remains in the proxy server. However, in the present invention, an event occurring in the user terminal is recorded on the proxy server side. Therefore, the browsing history can be supplemented based on this.

  Furthermore, the occurrence of an event at the user terminal may occur in rare cases. Even in such a case, since the record remains in the proxy server, the browsing history on the user terminal side can be supplemented based on the record.

1 is a system configuration example according to an embodiment of the present invention. It is an example of the Web browser extended function in one embodiment of this invention. It is an example of the frame page in one embodiment of this invention. It is a display completion event that occurs in an embodiment of the present invention. It is an example of the page transition recording table in one embodiment of the present invention. It is an example of the click history recording table in one embodiment of the present invention. It is an example of the proxy server extended function in one embodiment of this invention. It is an example of the browsing history table in one embodiment of the present invention. It is an example of the browsing history table after additional writing in one embodiment of this invention. It is an example of the page transition recording table in one embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 shows a system configuration example according to an embodiment of the present invention.

  A user connects to the Internet via the proxy server 2 and browses a Web page. On the user terminal 1 where the user browses the web page, the web browser extended function 100 is incorporated in the web browser 10. Further, the proxy server 2 has a proxy server extended function 20 incorporated therein.

  FIG. 2 shows an example of the Web browser extension function in the embodiment of the present invention.

  The web browser 10 includes a web browser extension function 100 in addition to the web page request unit 11 and the web page reception unit 12 for browsing web pages. The Web browser extended function 100 includes a display completion detection unit 110, a frame transition determination unit 120, a click detection unit 130, a browsing history transmission unit 140, a page transition recording table 121, and a click history recording table 131.

  When the user browses the web page with the web browser 10 and the display of the web page is completed, the web browser 10 generates a display completion event. The display completion detection unit 110 detects this event.

The frame transition determination unit 120 determines and detects the transition of the entire web page and the transition of only the child frame, for example, by the method according to Patent Document 1. For example, consider a Web page having a frame structure as shown in FIG. In this case, example.html contains
<frame src = http: //xxx.co.jp/menu.html name = "left">
<frame src = http: //xxx.co.jp/chap1.html name = "right">
A description representing the frame structure is included.

  Assume that a transition of the entire web page first occurs and then only a child frame transition occurs for this web page. At this time, a display completion event as shown in FIG. 4 occurs. According to the method of Patent Document 1, it is possible to detect the transition of the entire Web page and the transition of only the child frame. Here, “2-3” is the transition of the entire Web page, and “2-4” is the child. Since it is detected as a frame-only transition, the result is recorded in the page transition recording table 121 as shown in FIG. Here, URL ID = 1 is a record corresponding to “2-3” in FIG. 4, and URL ID = 2 is a record corresponding to “2-4” in FIG. URL ID = 2 is a record of transition of only the child frame, and is recorded together with the URL of the top frame. After URL ID = 3, it is a Web page transition when browsing the Web page thereafter. The frame transition determination unit 120 outputs the information of the page transition recording table 121 to the browsing history transmission unit 140.

  When the mouse click is performed on the Web page, the click detection unit 130 detects the event, associates the event with the Web page transition event, and records it in the click history recording table 131 together with the clicked tag. FIG. 6 shows an example of recording in the click history recording table 131 by the click detection unit 130. The click history recording table 131 shown in the figure shows that the tag described in the tag column is clicked on the Web page described in the URL column.

  The click detection unit 130 outputs the information in the click history recording table 131 to the browsing history transmission unit 140.

  After the display completion is detected, the browsing history transmission unit 140 transmits the outputs of the frame transition determination unit 120 and the click detection unit 130 to the proxy server 2.

  FIG. 7 is an example of the proxy server extension function according to the embodiment of the present invention.

  The proxy server 2 has a proxy server extended function 20 in addition to the Web page request receiving unit 21, the Web page requesting unit 22, the Web page receiving unit 23, and the Web page providing unit 24.

  The proxy server extended function 20 includes a browsing history reception unit 210, a Web browsing history acquisition unit 220, a Web browsing history analysis unit 230, and a Web browsing history appending unit 240. A web browsing history storage unit 40 is connected to the web browsing history acquisition unit 220, the web browsing history analysis unit 230, and the web browsing history appending unit 240.

  The web browsing history acquisition unit 220 stores the content received by the browsing history receiving unit 210 from the web browser 10 in the browsing history table 41 of the web browsing history storage unit 40 as a web browsing history. The received HTML is stored in the HTML file 42 as a file. The browsing history table 41 records the date and time when the HTML is received, the URL, the referrer, and the local path of the saved HTML file 42. FIG. 8 shows an example of the browsing history table 41. Information in the browsing history table 41 is stored for each Web browser.

  The browsing history reception unit 210 receives data from the browsing history transmission unit 140 of the Web browser 10. The data to be received is data recorded by the user terminal 1 and is stored in the page transition recording table 121 and the click history recording table 131 shown in FIGS.

  The web browsing history analysis unit 230 uses the data from the browsing history reception unit 210 to analyze the web browsing history. The analysis is sequentially performed based on the received page transition record of the page transition record table 121 shown in FIG. The contents of the processing of the web browsing history analysis unit 230 and the web browsing history appending unit 240 are classified as follows.

(1) For the transition of the entire web page:
(A) When it exists in the browsing history table;
(B) When it does not exist in the browsing history table;
(2) For child frame transition:
(A) When it exists in the browsing history table;
(B) When it does not exist in the browsing history table;
(3) When the corresponding event does not occur;
Hereinafter, each case will be described.

(1) Processing for (a):
In this process, the event received from the Web browser 10 (the data in the page transition recording table in FIG. 5 and the data in the click history recording table in FIG. 6) and the browsing history table 41 of the proxy server 2 are collated with the URL and date / time. The analysis is performed.

  This will be described in detail below.

In the case of the transition of the entire Web page, the page transition recording table 121 in FIG. 5 records that the Top URL such as URL ID = 1 is blank. If the URL and date and time recorded here are URL1 and DATE1, the browsing history receiving unit 210
URL1 = http: //xxx.co.jp/example.html
DATE1 = 2012/08/23 15:00:01
To get. When the Web browsing history analysis unit 230 searches the browsing history table 41 in FIG. 8 for a row in which the URL column value matches URL1 and the date / time column value matches DATE1 within a certain range, URL ID = The second row is applicable. 5 and 6, the time difference between the corresponding lines is the difference between the time when the HTML file passes through the proxy server 2 and the time when the display of the Web page is completed on the user terminal 1. If an average size is specified, an average time difference can be set.

  If no matching line is found in this search, processing (1) and (a) described later are executed.

Next, the web browsing history analysis unit 230 analyzes the file written in the local path column of the URL ID = 3 row of the browsing history table 41. In this file,
http://xxx.co.jp/menu.html
http://xxx.co.jp/chap1.html
Is a URL indicating the display content in the frame. When URLs that match these URLs are retrieved from the browsing history table 41 of FIG. 8, they match the URL ID = 3 and 4 rows, respectively. Thus, it can be seen that the lines of URL ID = 2, 3, and 4 correspond to one web page browsing. In order to indicate this, in the web browsing history appending unit 240, as shown in FIG. 9, a page ID column is provided, and URL ID = 2, 3, and 4 are set to indicate that the same web page browsing is supported. The same page ID = 2 is recorded in the corresponding page ID.

(1) Processing in case of (a):
In the case of the transition of the entire web page, the processing matches the browsing history table 41 by going back in time when the received event and the contents of the browsing history table 41 do not match in the above (1) (a). It is a process of searching for things.

  When the browsing history table 41 is searched by URL and date and time, but the corresponding row is not found, the Web browser 10 displays using the browser cache, and it is considered that data does not flow to the proxy server 2. . In this case, since browsing corresponding to the URL has been performed before, if the browsing history table 41 is searched backwards, a row in which the URL column matches the URL should be found.

For example, in the page transition record table 121 of FIG.
URL2 = http: //yyy.co.jp/
DATE2 = 2012/08/23 15:02:18
It is. Using these values, the corresponding row is not found even if the browsing history table 41 in FIG. 8 is searched in the same manner as (1) and (a) above. In this case, the search is performed retroactively from the date 2 to the cases (1) and (a).

  If found, the Web browsing history appending unit 240 copies the information on the corresponding line to the date and time DATE2. Going back further than the date shown in FIG. 8, the browsing history table 41 is traced back to search for a URL column value that matches URL2, and the referrer of the found row is http://xxx.co Assume that the value of .jp / example.html and local path column is 9001.html. In this case, the web browsing history appending unit 240 appends the values of the referrer column and the local path column to the line of URL ID = 5-1 in FIG. Here, since URL ID is insertion between URL ID = 5 and URL ID = 6, URL ID = 5-1.

(2) Processing for (a):
In the case of child frame transition, this processing is performed by comparing the event received from the Web browser 10 and the browsing history table stored in the proxy server 2 by comparing the URL with the date and time.

In the case of a transition of a child frame, as shown in the line of URL ID = 2 in the page transition recording table 121 in FIG. 5, the top frame URL (Top URL) is recorded simultaneously with the URL indicating the content of the displayed frame. . Here, from the page transition record table 121 of FIG.
URL3 = http: //xxx.co.jp/chap2.html
Date3 = 2012/08/23 15:02:13
TOP3 = http: //xxx.co.jp/example.html
And

  When the browsing history table 41 is searched for URL3 and DATE3 in the same manner as (1) and (a), the line of URL ID = 5 corresponds. In addition, when a search is performed using the TOP3 as a URL and going back in the browsing history table 41 from DATE3, URL ID = 2 matches. Therefore, it can be understood that the browsing history table 41 corresponding to URL ID = 4 is a part of browsing when URL ID = 2 in the page transition recording table 121 has been replaced. Here, the range that goes back to the date and time is set to a maximum value that is assumed as the time during which only the child frame transitions without changing the parent frame without changing the Web page including the frame.

  Next, when the URL of the click history record table 131 shown in FIG. 6 matches TOP3 and the date and time is retrieved retroactively from DATE3, “2012/08/23 15:02:12” with URL ID = 2 is searched, It can be seen that the corresponding click tag is <a href=http://xxx.co.jp/chap1.html target=right">. Also, the URL of the browsing history table 41 in FIG. When the date and time are retrieved from DATE3, URL ID = 5 is extracted, and menu.html is obtained as the referrer information of the line.

  This shows the following.

  -You can see where the click was made from the referrer information. In this case, the click was made in menu.html.

  ・ The content of the clicked tag is known from the information of the clicked tag. In this case, a transition was made in the right frame.

  Therefore, the browsing of URL ID = 5 in the browsing history table 41 of FIG. 8 is the same as the browsing of URL ID = 2, 3 and 4, but the content of URL ID = 4 which is a right frame is replaced with chap2.html. . When the web browsing history appending unit 240 performs processing according to this content, URL ID = 4-1 and 4-2 are appended in the browsing history table 41 shown in FIG. Here, since the URL ID is inserted between URL ID = 4 and URL ID = 5, URL ID = 4-1 and 4-2 were set.

(2) Processing in case of (a):
In the case of a transition of a child frame, when the collation partner is not found in the above (2) and (a), the processing is performed by going back in time and searching the browsing history table 41 and analyzing it.

  Even in the case of the transition of only the child frame, if the content corresponding to the row of the page transition recording table 121 in FIG. 5 is not found in the browsing history table 41 in FIG. 8, the same processing as in the above (1) (a) is performed. is there.

Processing for (3):
This processing is processing when there is no corresponding event.

  In the page transition recording table 121 of FIG. 5, the URL with URL ID = 4 exists in the row of URL ID = 7 in the browsing history table 41 of FIG. 8, so these two rows correspond. Therefore, there is no corresponding row in the page transition recording table 121 in FIG. 5 for the row of URL ID = 6 in the browsing history table 41 in FIG. This is presumably because an event omission occurred in the user terminal. In this case, the web browsing history appending unit 240 appends to the page transition recording table 121. FIG. 10 shows an example of the event occurrence history of the page transition recording table 121 after being additionally written. An additional entry is made in the column of URL ID = 3-1.

  Note that the processing of each part of the components of the proxy server shown in FIG. 7 described above can be constructed as a program, installed on a computer used as a proxy server and executed, or distributed via a network. .

  The present invention is not limited to the above-described embodiments, and various modifications and applications are possible within the scope of the claims.

DESCRIPTION OF SYMBOLS 1 User terminal 2 Proxy server 3 Web server 10 Web browser 11 Web page request part 12 Web page reception part 20 Proxy server extended function 21 Web page reception part 22 Web page request part 23 Web page reception part 24 Web page provision part 30 Web resource 40 Web browsing history storage unit 41 Browsing history table 42 HTML file 100 Web browser extended function 110 Display completion detecting unit 120 Frame transition determining unit 121 Page transition recording table 130 Click detecting unit 131 Click history recording table 140 Browsing history transmitting unit 210 Browsing history Receiving unit 220 Web browsing history acquisition unit 230 Web browsing history analysis unit 240 Web browsing history appending unit

Claims (9)

A web browsing history acquisition system for acquiring browsing history of a web page divided into frames having a parent-child relationship,
A user terminal and a proxy server,
The user terminal is
An event detection / transmission means for detecting a page transition event and a click event generated by the Web browser, storing event information in the event generation storage means, and transmitting the event information to the proxy server;
The proxy server is
The event information is acquired from the user terminal, and the browsing history, which is a history of providing the Web content to the user terminal, is stored in the browsing history storage unit in association with the event information, and the HTML of the Web content is converted into an HTML file. Browsing history acquisition means for storing;
Analyzing the browsing history of the browsing history storage means, generating a history representing a parent-child relationship of frames;
Browsing history appending means for appending the history obtained by the browsing history analysis means to the browsing history storage means;
Web browsing history acquisition system characterized by having. The browsing history analysis means of the proxy server is
The Web browsing history acquisition system according to claim 1, further comprising: a matching unit that matches the event information received from the user terminal with the browsing history of the browsing history storage unit based on the date and time of the event information and the URL of the browsing history. The verification means includes
The Web browsing history acquisition system according to claim 2, further comprising means for searching backwards the time of the browsing history when a collation target is not found as a result of matching the event information with the URL of the browsing history and the date and time. The browsing history appending means is
As a result of collating the event information received from the user terminal and the browsing history of the browsing history storage unit by the date and time of the event information and the URL of the browsing history, the matching unit is associated with the browsing history storage unit. The Web browsing history acquisition system according to claim 2, further comprising: means for transmitting a browsing history that is not associated with the user terminal to be additionally recorded in the event generation storage unit of the user terminal when there is a browsing history that is not performed. A web browsing history management device that manages browsing history of web pages divided into frames having parent-child relationships viewed on a user terminal,
Event information acquisition means for acquiring event information including a page transition event and a click event that are detected by the user terminal and generated by the Web browser;
A browsing history acquisition unit that stores the browsing history, which is a history of providing Web content to the user terminal, and the event information in association with the browsing history storage unit, and stores the HTML of the Web content as an HTML file;
Analyzing the browsing history of the browsing history storage means, generating a history representing a parent-child relationship of frames;
Browsing history appending means for appending the history obtained by the browsing history analysis means to the browsing history storage means;
A Web browsing history management device characterized by comprising: The browsing history analysis means includes
The web browsing history management device according to claim 5, further comprising a collating unit that collates the event information received from the user terminal and the browsing history of the browsing history storage unit with a date and time of the event information and a URL of the browsing history. The verification means includes
The Web browsing history management device according to claim 6, further comprising means for searching backwards the time of the browsing history when a collation target is not found as a result of matching the event information with the URL of the browsing history and the date and time. The browsing history appending means is
As a result of collating the event information received from the user terminal and the browsing history of the browsing history storage unit by the date and time of the event information and the URL of the browsing history, the matching unit is associated with the browsing history storage unit. The web browsing history management device according to claim 6, further comprising means for transmitting a browsing history that is not associated to the user terminal when there is a browsing history that is not associated with the event occurrence storage unit of the user terminal. Computer
A web browsing history management program for causing each of the means of the web browsing history management apparatus according to any one of claims 5 to 8 to function.

Images