Source: http://www.google.com/patents/US7331517?dq=6008737
Timestamp: 2016-12-05 00:58:51
Document Index: 571956402

Matched Legal Cases: ['art 161', 'art 163', 'art 161', 'art 161', 'art 163', 'art 163', 'art 153', 'art 161', 'art 163', 'art 161', 'art 153', 'art 159']

Patent US7331517 - Article reader program, article management method and article reader - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsAn article reader program of this invention comprises: detecting that a display of data concerning a first article is instructed by a user; calculating an article relevance degree between the first article and a second article; extracting the second article whose article relevance degree with the first...http://www.google.com/patents/US7331517?utm_source=gb-gplus-sharePatent US7331517 - Article reader program, article management method and article readerAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS7331517 B2Publication typeGrantApplication numberUS 11/182,941Publication dateFeb 19, 2008Filing dateJul 15, 2005Priority dateMar 23, 2005Fee statusPaidAlso published asUS20060213976Publication number11182941, 182941, US 7331517 B2, US 7331517B2, US-B2-7331517, US7331517 B2, US7331517B2InventorsHiroya Inakoshi, Seishi Okamoto, Tatsuya AsaiOriginal AssigneeFujitsu LimitedExport CitationBiBTeX, EndNote, RefManPatent Citations (7), Non-Patent Citations (1), Referenced by (7), Classifications (7), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetArticle reader program, article management method and article reader
US 7331517 B2Abstract
An article reader program of this invention comprises: detecting that a display of data concerning a first article is instructed by a user; calculating an article relevance degree between the first article and a second article; extracting the second article whose article relevance degree with the first article satisfies a predetermined condition in relation to the first article; assigning a top priority to the first article; assigning a priority lower than the top priority of the first article to the extracted second article; and displaying the data concerning the first article and data concerning the extracted second article according to the assigned priorities of the first article and the extracted second article.
The present invention relates to a technique for efficiently managing article data provided in a network.
Conventionally, an information offerer in the Internet was only one who had an advanced computer technique. However, by using a dedicated information providing program having templates and a plain user interface, a general Internet user has also come to be able to easily provide information on the Internet. As a result, in recent years, information provision via the Internet has started to become popular among general Internet users. One of triggers by which the number of general information offerers has increased as stated above is a system called a Weblog or a Blog. The Weblog is a system to write sentences and to manage sentence data in a simple operation. The Weblog was first recognized as a system for a personal use or a narrow use, for example, to write a diary and to allow familiar friends to browse it. However, journalists, writers, and experts in various fields open their Weblogs to the public widely and use them in order to disclose and exchange their opinions. Thus, at present, the Weblog is being recognized as a system having a wide use and being highly useful. Further, the Weblog is expected as an information providing medium with higher readiness.
In view of the above problems, an object of the invention is to provide a technique enabling a user to efficiently acquire articles provided on a network.
FIG. 1 is a functional block diagram showing the outline of a first embodiment of the invention;
The outline of a first embodiment of the invention will be described with reference to FIGS. 1 to 4. A computer 1 in the first embodiment of the invention is an apparatus to execute a ticker type RSS reader program 3, and further includes an article display unit 5, an operation unit 7, and a classification result display unit 9 as an input and output interface. The computer 1 is connected to article providing sites 13 through a network 11 such as, for example, the Internet. The RSS reader program 3 executed by the computer 1 is the program of acquiring data called an RSS document from the article providing site 13, managing article summaries included therein, and integrating one or plural article summaries into one group as the need arises. That is, the RSS reader program 3 carries out grouping of one or plural article summaries into one set and manages them. The RSS reader program 3 includes an article collector 15, a bookmark 17, a display candidate queue 19, which is, for example, a FIFO, a display article extractor 21, an event receiver 23, a topic extractor 25, a topic database 27, a deletion unit 29, a topic reconstructor 31, a topic classifier 33, and a classification result extractor 35.
Here, “grouping” means constructing one set by plural article summaries relevant to each other or by only one article summary. In the first embodiment of the invention, such a set is called a “topic set”. FIG. 2 shows a relationship between article summaries and a topic set. In FIG. 2, 200 a denotes a topic set concerning a topic “A”, and includes an article summary 201 a concerning a topic “a1”, an article summary 202 a concerning a topic “a2”, an article summary 203 a concerning a topic “a3”, and an article summary 204 a concerning a topic “a4”.
When the topic set 200 a is the set of article summaries relating to the topic “Christmas”, the topic set 200 a can include:
the article summary 201 a=article summary concerning “USB Christmas tree, on sale also this year”,
the article summary 202 a=article summary concerning “nightmare, before Christmas”,
the article summary 203 a=article summary concerning “Christmas sales battle does not warm up”, and
the article summary 204 a=article summary concerning “where does Santa Claus comes from?”.
Besides, the topic set 200 b is similar to the topic set 200 a, and when the topic set 200 b is the set of article summaries concerning the topic “desktop retrieval”, the topic set 200 b can include:
an article summary 201 b=article summary concerning “Ask Jeeves opens a beta edition to the public”,
an article summary 202 b=article summary concerning “M*S search desktop retrieval is . . . ”, and
an article summary 203 b=article summary concerning “Go**le is the first to arrive desktop retrieval”.
The RSS reader program 3 gives specific data to the article summaries 201 a to 204 a, and 201 b to 203 b in order to differentiate the article summaries 201 a to 204 a, and 201 b to 203 b as the grouped topic sets from other article summaries, and in order to efficiently manage these article summaries. One of the specific data is called a “marker” described later, and another is called a “topic element”. For example, the data concerning “Christmas” is included in the article summaries 201 a to 204 a, and in addition to this, the topic element relating to the topic “Christmas” is given to the article summaries 201 a to 204 a. Similarly, the data concerning “desk top retrieval” is included in the article summaries 201 b to 203 b, and in addition to this, the topic element relating to the topic “desktop retrieval” is given to the article summaries 201 b to 203 b. Here, the structure of an RSS document and elements included in the RSS document will be described with reference to FIGS. 3A and 3B. As roughly shown in FIG. 3A, an RSS document 300 acquired from the article providing site 13 is written in XML (extensible Markup Language) format. In the XML, various data can be written by using a pair of tags of a start tag < . . . > and an end tag </ . . . >. In the RSS, as illustrated in FIG. 3A, an <item/> tag, a <title/> tag, a <link/> tag, a <description/> tag, a <content: encoded/> tag, a <dc:subject/> tag, a <dc:creator/> tag, and a <dc:date/> tag are described in the RSS document 300. These tags are tags generally used in the RSS.
Besides, in the RSS document 300, for example, the content “XYZ news publishing company” of an element is described to be interposed between a pair of the <dc:creator> tag and the </dc:creator> tag.
FIG. 3B shows the classification of an example of elements in the RSS document in use. However, in FIG. 3B, only kinds of tags are illustrated. The elements of the RSS document 300 acquired from the article providing site 13 are roughly classified into two kinds of article elements. One includes a link element 301 a (i.e. <link/> tag) and an update date element 301 b (i.e. <dc:date/> tag), and the RSS reader program 3 can uniquely specify the RSS document by using these as a compound key 301. The other includes one called “article extraction element” or “article extraction tag” for convenience, and the <item/> tag, the <title/> tag and the like shown in FIG. 3A are classified into the article extraction element. Tags classified as the article extraction tag 303 are tags other than the <link/> tag, the <dc:date/> tag, and a <topic/> tag described below.
On the other hand, a topic element 305 (<topic/> tag) is an element given to, when the RSS documents are grouped, the grouped RSS documents. That is, the RSS reader program 3 recognizes, as one of RSS documents constituting a topic set, an RSS document 307 in which the topic element 305 is further given to the RSS document 300 including only the two kinds of the article elements 301 and 303. Incidentally, in the RSS reader program 3, in the case where the RSS document 300 is managed as the XML file, the topic element 305 may be described in a predetermined area of the XML file. Besides, in the case where the RSS document 300 is managed as a list or a relational database, data relating to the topic element may be stored in a specific area of a record corresponding to the RSS document, for example, data “Christmas” or “desktop retrieval” may be stored on an area of “topic column”.
The content of the <title/> element “yen rate in Tokyo, one dollar=102 Yen 05 to 07 Sen (at 15:00)” is a hyperlink 51 whose link destination is the content of the <link/> element. When the user selects this hyperlink 51, for example, clicks it by a mouse, the RSS reader program 3 activates a Web browser. The Web browser acquires the whole article relating to the article summary being displayed from the link destination, and displays it. In addition to the activation of the Web browser, the RSS reader program 3 executes a series of topic extraction processings by the topic extractor 25. The button 45 provides a function comparable to the hyperlink 51, and when the user clicks the button 45, the Web browser is activated, and the series of topic extraction processings are executed.
(a) In the case where the occurring event is the event relating to “site patrol” (step S3: Yes route), the article collector 15 executes an “article download processing” (step S5). When the article download processing is ended, the event receiver 23 watches and waits for the occurrence of an event (step S1).
(b) In the case where the occurring event is the event relating to “deletion of article summary” (step S7: Yes route), the deletion unit 29 executes an “article summary delete processing” (step S9). When the article summary delete processing is ended, the event receiver 23 watches and waits for the occurrence of an event (step S1).
(c) In the case where the occurring event is the event relating to “opening of article” or “display of article” (step S11: Yes route), the topic extractor 25 executes a “topic extraction processing” (step S13). When the topic extraction processing is ended, the event receiver 23 watches and waits for the occurrence of an event (step S1).
(d) The occurring event is the event relating to “deletion of topic” (step S15: Yes route), the deletion unit 29 executes a “topic delete processing” (step S17). When the topic delete processing is ended, the event receiver 23 watches and waits for the occurrence of an event (step S1).
The article download processing by the article collector 15 is executed when the event receiver 23 detects the event relating to “site patrol” and notifies a processing execution instruction of the “site patrol” to the article collector 15. Here, in the ticker type RSS reader, it is desirable that the event concerning the “site patrol” is a timer event on account of its user interface. Specifically, the event is for causing the event receiver 23 to instruct the article collector 15 to carry out the patrol of predetermined sites.
The article summary delete processing by the deletion unit 29 is executed when the event receiver 23 detects the event relating to “deletion of the article summary” and notifies a processing execution instruction of the article summary deletion to the deletion unit 29. Here, the event relating to the “deletion of the article summary” includes two events. One is an event by a user instruction, for example, an event generated when the user clicks the button 47 as described in the explanation of FIG. 4. The other is a kind of timer event generated by the event receiver 23 itself, and is an event generated to periodically update the content displayed on the article display unit 5.
The topic extraction processing by the topic extractor 25 is executed when the event receiver 23 detects the event relating to “opening of article” or “display of article” and notifies a processing execution instruction to the topic extractor 25. Here, the event relating to “opening of article” or “display of article” is, for example, an event generated when the user clicks the hyperlink 51 or the button 45 as described in the explanation of FIG. 4. When issuing the processing execution instruction to the topic extractor 25, the event receiver 23 acquires data relating to the article summary displayed on the article display unit 5, that is, data of the article summary being displayed from the display article extractor 21, and transmits the data of the article summary being displayed to the topic extractor 25.
Similarity Degree Function by Article Attribute Value
The article summary includes article elements such as a title, a URL, an update date, and an author, and as shown in FIG. 3B, these article elements belong to one of the compound key 301 and the article extraction element 303. These article elements are for expressing the feature of the article relating to the article summary. Then, with respect to two article summaries x and y, the similarity degree (i.e. partial similarity degree) with respect to the same article element is calculated, and after the partial similarity degree is multiplied by a predetermined weight, the total sum of the weighted partial similarity degrees with respect to all article elements is calculated. The value calculated in this way is defined as the similarity degree between the article summaries x and y. This is expressed by a following expression (2).
Sx(y)=Σ{wi×δi(x, y)} (2)
Similarity Degree Function Based on Link Reference
When the article body is downloaded from the URL included in the <link/> tag of the article summary, a hyperlink to refer to another document is often included in the downloaded article body. Then, a similarity degree function using a hyperlink is defined by a following expression (3).
L (i)(X)=L(X)
L (n)(X)=L(L n−1)(n≧1)
As another method, it is possible to adopt a method in which a cited portion by a partial copy from another Web page or article in an article body x is used as a key to identify a Web page or an article as the origin of the citation, and this is made to be included in L (x), or a method of handling a reference created by using a truck back function characteristic of the Weblog.
The deletion unit 29 performs not only the article delete processing described above but also the topic delete processing. The topic delete processing is executed when the event receiver 23 detects the event relating to “deletion of topic”, and notifies a processing execution instruction of a topic delete alarm to the deletion unit 29. Here, the event relating to “deletion of topic” is the event generated in the case where the user clicks the button 49 as described in the explanation of FIG. 4. That is, when the user clicks the button 49, the topic delete processing is executed.
(g) In the case where the occurring event is the event relating to “site periodic patrol” (step S75: Yes route), the article collector 15 and the topic classifier 33 execute a series of article classification processings (step S77 to S91). When the series of article classification processings are ended, the event receiver 23 watches and waits for the occurrence of an event (step S73).
(h) In the case where the occurring event is the event relating to “return to normal mode” (step S75: No route), the classification result extractor 35 executes a classification result display processing (step S93). This processing will be described later in detail. Next, the RSS reader program 3 carries out the second switching of the operation mode. In detail, the event receiver 23 notifies the article collector 15 that the operation mode is switched to the normal mode, and the article collector 15 switches the operation mode in response to the notification. That is, the operation of the article collector 15 in which the acquired article summary is delivered to the topic classifier 33 is switched to the operation to store the acquired article summary into the display candidate queue 19. Then, the procedure proceeds to the processing of the normal mode shown in FIG. 5 through terminal 2.
FIG. 12 schematically shows the topic set reconstruction processing. Many topic sets are stored in the topic database 27 by the topic extraction processing described in the explanation of FIG. 8. Then, when the operation of the RSS reader program 3 shifts to the sleep mode, the topic reconstructor 31 carries out the reconstruction of the topic sets. FIG. 12 shows a state in which a topic set A (200 a) and a topic set B (200 b) become a topic set D (200 d) by the topic set reconstruction processing. For example, in the case where the topic set A is the set of articles concerning the topic of “Sumatra offshore earthquake”, and the topic set B is the set of articles concerning the topic of “Niigata earthquake”, these topic sets have the commonality of “earthquake” or “disaster”. Then, topic elements of articles included in the topic sets A and B are changed. That is, the topic element “Sumatra offshore earthquake” given to the article summary included in the topic set A and the topic element “Niigata earthquake” given to the article summary included in the topic set B are changed to a new topic element “disaster”. Thus, the plural topics are condensed into one topic. FIGS. 14A and 14B show a state in which the topic elements 305 of the first and the second records are changed to “disaster” by the topic set reconstruction processing. In addition, there is shown a state in which by the topic set reconstruction processing, the topic elements 305 of the third and the fourth records are changed to “sport”, and the topic elements 305 of the fifth and the sixth records are changed to “economy”. The method of collecting the topic sets into the topic set of an upper conception as stated above is generally known as a clustering technique.
Besides, a technique to construct the classifier function f(x) from the topic database 27 is known. For example, in an NN method (Nearest Neighbor Method), by using the similarity degree function Sx(y) described above, the article summary x is assigned to the topic set to which the article summary y with the highest similarity degree belongs. With respect to the NN method, please refer to “S. Chakrabarti, Mining the Web-Discovering knowledge from Hypertext Data-, pp. 133-136, Morgan Kaufmann Pub. (2003)”, the contents of which are incorporated herein by reference.
[p1,p2, . . . , pk]=f(x)
C∈{Ck|k=1, 2, . . . ,n} (5)
The classification result display processing by the classification result extractor 35 is carried out when the event receiver 23 detects the event relating to “return to normal mode” and notifies a processing execution instruction to the classification result extractor 35. The event relating to “return to normal mode” is a user event generated when the user uses the operation unit 7 to issue some instruction, for example, an event generated when the user gives an instruction to display an article, or an event generated when the user gives an instruction to return the minimized program window to the original size.
FIG. 15 shows the details of the classification result display processing. In response to the processing execution instruction from the event receiver 23, the classification result extractor 35 acquires all article summaries from the topic database 27 (step S111). In accordance with the topic elements given to the acquired article summaries, they are grouped for each topic, and further, the article summaries are arranged into newly-arrived articles and relevant articles for each of the topics. The “newly-arrived article” here is the article summary registered in the topic database 27 in the sleep mode. Besides, the “relevant article” is the article summary registered in the topic database 27 before the shift to the sleep mode. When a judgment is made as to whether the article summary is the newly-arrived article or the relevant article, a system may be such that the judgment is made by referring to the date of the shift to the sleep mode stored in the predetermined area of the topic database 27, or a system may be such that reference is made to the newly-arrived flag given to the article summary. At this time, the classification result extractor 35 may sort the article summaries by the update date element of the article summary (<dc:date/> tag) (step S113). It displays the result on the classification result display unit 9 (step S115).
Modified Example of the First Embodiment of the Invention
When the topic extractor 25 registers the article summary being displayed and the article summary relevant to this into the topic database 27, instead of registering them as a new topic set into the topic database 27, a judgment may be made as to the similarity degree to the topic set already defined on the topic database 27, and they are additionally registered in the existing topic set.
Next, a second embodiment of the invention will be described with reference to FIGS. 17 to 27. As shown in FIG. 17, a computer 101 in the second embodiment of the invention is an apparatus to execute a mail-client type RSS reader program 103, and includes an RSS reader program 103 and, as an input and output interface, an article list display unit 105 a, a selected article display unit 105 b, an operation unit 107, and a classification result display unit 109. The computer 101 is connected to article providing sites 113 through a network 111 such as, for example, the Internet. The RSS reader program 103 executed by the computer 101 is the program which acquires RSS documents from the article providing sites 113, manages article summaries relating to the acquired RSS documents, and integrates one or plural article summaries into one group as the need arises. That is, the RSS reader program 103 groups one or plural article summaries into one set and manages them. The RSS reader program 103 includes an article collector 115, a bookmark 117, a display article extractor 121 (an article list extractor 121 a, a selected article extractor 121 b) an event receiver 123, a topic extractor 125, a topic database 127, a reference recorder 129, a topic reconstructor 131, a topic classifier 133, a classification result extractor 135, an article database 137, a display candidate spool 139, a filtering unit 141 and a folder information 143. Incidentally, because the meanings of “grouping”, “topic set”, “topic element” and the like are the same as those described in the first embodiment of the invention, their description will be omitted.
FIG. 18 shows a state in which the user selects the bookmark site folder 165 x “xyz.com”, and further selects the article summary at the uppermost stage listed on the article list display part 161, and as a result, a part of the details of the article summary selected by the user is displayed on the selected article display part 163. Besides, element names of article elements are displayed at the upper part of the article list display part 161 so that the user can easily visually identify the article summary. In FIG. 18, the element names of “update date” (171 a), “topic” (171 b), “title” (171 c), “channel” (171 d), and “category” (171 e) are displayed. Portions displaying these article element names are buttons to receive user instructions, and when the user clicks one of the buttons 171 a to 171 e, the article summaries displayed on the article list display part 161 are sorted by the article element relating to the button click. FIG. 18 shows the state in which sorting is made by the update date and in order of arrival. Besides, in the case where the topic element is given to the article data, the content is displayed.
The content of the RSS document 300 shown in FIG. 3A is displayed as the details of the article summary on the selected article display part 163. Reference numeral 175 denotes the content of the <title/> element of the RSS document 300, which is hyperlink displayed, and the link destination is the content of the <link/> element. When the user clicks the hyperlink 175, the whole of the article document acquired from the link destination is displayed on the selected article display part 163. Reference numeral 177 denotes the content of the <dc:date/> element, and 179 denotes the content of the <description/> element. In the case where the topic element (<topic/> element) is given to the RSS document 300, as denoted by 173, words such as “stock market price” are displayed as the topic information.
Incidentally, in FIG. 18, partial user interfaces, such as an output interface relating to the display of the program window 151, an input interface for performing “selection of folder” with respect to the folders displayed on the folder display part 153, and an input interface for performing “selection of article summary” with respect to the article summary displayed on the article list display part 161, are merely explained. It is also possible to provide a user interface such as a button to realize a function comparable to the button 49 for performing “deletion of topic”.
When the event receiver 123 detects the occurrence of the event relating to “selection of folder” and notifies a processing execution instruction relating to the occurring event to the filtering unit 141, the filtering unit 141 refers to the folder information 143 in response to the notification, extracts the article summary belonging to the bookmark folder under the selected folder from the article database 137, and stores it in the display candidate spool 139.
When the event receiver 123 detects the occurrence of the event relating to “opening of article” or “display of article” and notifies a processing execution instruction relating to the occurring event to the topic extractor 125, the topic extractor 125 uses the article summary already stored in the display candidate spool 139 to carry out the topic extraction processing. The topic extraction processing here is basically the same as the topic extraction processing described in the first embodiment of the invention, and the topic extractor 125 registers the generated topic set in the topic database 127, and stores the data of the article summaries included in the topic set at the head of the display candidate spool 139 so that the article summaries included in the topic set are displayed on the article list display unit 105 a in order from the article summary selected by the user. Incidentally, the event relating to “opening of article” or “display of article” in the second embodiment of the invention will be described later.
(i) In the case where the occurring event is the event relating to “site patrol” (step S123: Yes route), the article collector 115 carries out “a second article download processing” (step S125). When the second article download processing is ended, the event receiver 123 watches and waits for the occurrence of an event (step S121).
(j) In the case where the occurring event is the event relating to “selection of folder” (step S126: Yes route), the filtering unit 141 carries out “an article filtering processing” (step S127). When the article filtering processing is ended, the event receiver 123 watches and waits for the occurrence of an event (step S121).
(k) In the case where the occurring event is the event relating to “setting of already-read flag for selected article summary” (step S128: Yes route), the reference recorder 129 carries out “an already-read flag setting processing for article summary” (step S129). When the already-read flag setting processing for the article summary is ended, the event receiver 123 watches and waits for the occurrence of an event (step S121).
(l) In the case where the occurring event is the event relating to “opening of article” or “display of article” (step S131: Yes route), the topic extractor 125 carries out “a second topic extraction processing” (step S133). When the second topic extraction processing is ended, the event receiver 123 watches and waits for the occurrence of an event (step S121).
(m) In the case where the occurring event is the event relating to “setting of already-read flag for selected topic” (step S135: Yes route), the reference recorder 129 carries out “already-read flag giving processing to topic” (step S137). The already-read flag setting processing to the topic is ended, the event receiver 123 watches and waits for the occurrence of an event (step S121).
The second article download processing in the article collector 115 is carried out when the event receiver 123 detects the event relating to “site patrol”, and notifies a processing execution instruction of the site patrol to the article collector 115. Here, the event relating to “site patrol” in the first embodiment of the invention is only the timer event, whereas the event relating to “site patrol” in the second embodiment of the invention includes the user event generated as a result that the user uses the operation unit 107 to give an instruction of the site patrol.
As shown in the flowchart of FIG. 20A, in response to the event relating to the site patrol from the event receiver 123, the article collector 115 acquires a URL from the bookmark 117, downloads an RSS document from the article providing site 113 based on the acquired URL (step S141), and adds an article summary relating to the downloaded RSS document to the database 137 (step S143). In the case where there are plural article providing sites 113 to be patrolled, the steps S141 and S143 are repeated. When the download processing of the RSS document from the article providing site 113 and the addition processing of the article summary relating to the RSS document to the article database 137 are ended, the event receiver 123 resets the occurrence timing of the event relating to the site patrol (step S145). Incidentally, in the resetting processing, the article collector 115 may carry out the resetting processing, and may notify the result of the resetting processing to the event receiver 123. Because the event relating to the site patrol has been described in detail in “(a) article download processing”, its description will be omitted.
FIG. 20B shows the article filtering processing carried out by the filtering unit 141. When the event receiver 123 detects the event relating to “selection of folder”, and notifies a processing execution notification including data relating to the article summary selected by the user and the selected folder, the filtering unit 141 refers to the folder information 143, and acquires the bookmark folder under the selected folder (step S146). The filtering unit 141 acquires the article summary belonging to the acquired bookmark folder from the article database 137 (step S147). And then, the filtering unit 141 stores the acquired article summary in the display candidate spool 139 (step S148).
FIG. 21 shows an example, as the already-read flag setting processing for the article summary, in which the “already-read flag” for the article summary so that the article summary is set to ON, is managed. In response to the processing execution instruction relating to the setting of the already-read flag for the selected article summary from the event receiver 123, the reference recorder 129 sets ON to the already-read flag for the article summary selected by the user. In this case, the already-read flag is set to ON for the article summary in the display candidate spool 139, and as the need arises, the already-read flag is set to ON also for the article summary in the article database 137 (step S181). When the setting of the already-read flag is ended, in order to update (refresh) the content displayed on the article list display unit 105 a, the reference recorder 129 instructs the article list extractor 121 a to list the article summaries stored in the display candidate spool 139 (step S183). In response to the instruction from the reference recorder 129, the article list extractor 121 a displays the article summaries stored in the display candidate spool 139 on the article list display unit 105 a. The refresh of the article list display unit 105 a is the effective processing procedure in the case where for example, an icon indicating the state of already-read or not-read is displayed for each of the article summaries displayed on the article list display unit 105 a, or in the case where the unread article summaries displayed on the article list display unit 105 a are listed in thick letters, while the read article summaries are listed in thin letters.
The second topic extraction processing by the topic extractor 125 is carried out when the event receiver 123 detects the event relating to “opening of article” or “display of article” and notifies a processing execution instruction relating to the event to the topic extractor 125. Here, the event relating to “opening of article” or “display of article” in the second embodiment of the invention is a user event generated as a result that the user uses the operation unit 107 to give an instruction similarly to the first embodiment of the invention, for example, a user event generated as a result that the user double-clicks the article summary displayed on the article list display unit 161, or a user event generated as a result that the user clicks an article title included in the article summary being displayed on the selected article display part 163.
The topic extractor 125 extracts an article summary relevant to the article summary being displayed among the remaining article summaries (step S155). Because the details of the processing at the step S155 is similar to what is described in the first embodiment of the invention (that is, what is described in detail in the description of the step S33 of FIG. 8), the description will be omitted. When the article summary relating to the article summary being displayed is extracted, the topic extractor 125 gives the topic element <topic/> as described in FIGS. 2 and 3 to generate the topic set with the article summary being displayed and the relevant article summary (step S157), and additionally registers the generated topic set in the topic database 27 (step S159). Further, the topic extractor 125 disposes the article summary included in the topic set at the head of the display candidate spool 139 so that the article summary included in the topic set is displayed at an upper position in the list display (step S161), and in order to update (refresh) the content displayed on the article list display unit 105 a, the topic extractor instructs the article list extractor 121 a to list and display the article summaries stored in the display candidate spool 139 (step S163). In response to the instruction from the topic extractor 125, the article list extractor 121 a displays the article summaries stored in the display candidate spool 139 on the article list display unit 105 a. Here, data flow in which a relevant article summary is extracted will be described with reference to FIGS. 23A to 23C. FIG. 23A shows the structure of the article summaries before the second topic extraction processing is executed. At this time point, the topic element is not given to any article summaries. In the second topic extraction processing, first, in response to the instruction to select an article summary from the user, the article summary in the first line of FIG. 23A is specified. On the basis of this article summary in the first line, relevant article summaries are extracted. FIG. 23B shows a state in which the article summary having similarity degree A1 with respect to the article summary in the first line is extracted. The order of arrangement of the article summaries shown in FIG. 23B is also the order of arrangement of the article summaries displayed on the article list display part 161 of FIG. 18. As shown in FIGS. 23A and 23B, the topic element 305 (<topic/>) “Sumatra offshore earthquake” is given to the article summary in the first line and the article summary having the similarity degree A1, and these article summaries are displayed at the uppermost position of the list. With respect to the article summaries irrelevant to the topic set of “Sumatra offshore earthquake”, the order of arrangement is not changed.
The reference recorder 129 executes not only the foregoing already-read flag setting processing for the article summary, but also the already-read flag setting processing for the topic. The already-read flag setting processing for the topic described here is carried out when the event receiver 123 detects the event relating to “already-read flag setting processing for selected topic”, and notifies a processing execution instruction relating to the event to the reference recorder 129. The event relating to “already-read flag setting processing for selected topic” is the user event generated by user's instruction similarly to the event relating to “deletion of topic” described in the first embodiment of the invention.
(p) The topic reconstructor 131 executes “second topic set reconstruction processing” (step S201). This processing will be described later in detail. When the second topic set reconstruction processing is ended, the event receiver 123 watches and waits for the occurrence of an event (step S203). When the event occurs, the event receiver 123 judges the content of the occurring event, and instructs, according to the content, the respective processing units in the RSS reader program 103 to carry out processing. The processing executed by the respective processing units having received the processing execution instruction is the following processing described in (q) or (r).
(q) In the case where the occurring event is the event relating to “site periodic patrol” (step S205: Yes route), the article collector 115 and the topic classifier 133 carry out a series of second article classification processings (step S207 to S221). When the series of second article classification processings are ended, the event receiver 123 watches and waits for the occurrence of an event (step S203).
(r) In the case where the occurring event is the event relating to “return to normal mode” (step S205: No route), the classification result extractor 135 executes “second classification result display processing” (step S223). Incidentally, because the details of the second classification result display processing are quite the same as the classification result display processing of the first embodiment of the invention described in the description of FIGS. 15 and 16, the description will be omitted. Next, the RSS reader program 103 carries out the second switching of the operation mode. In detail, the event receiver 123 notifies the article collector 115 that the operation mode is switched to the normal mode, and the article collector 115 switches the operation mode according to the notification. That is, the operation of the article collector 115 in which the article summary relating to the acquired RSS document is delivered to the topic classifier 133 is switched to the operation in which the article summary relating to the acquired RSS document is stored in the article database 137. Then, the procedure proceeds to the processing of the normal mode shown in FIG. 19 through terminal 4.
Here, “topic folder” is one of the folders displayed on the folder display part 153 as shown in FIG. 18, and folders denoted by 169 c and 169 d are the topic folders. In the processing to generate the topic folder, the topic folder is initialized, reference is made to the topic set stored in the topic database 127, and the folder corresponding to the topic set is generated as shown in FIG. 18. Specifically, data relating to the topic folder of the folder information 143 is initialized, the content of the topic element of the topic set stored in the topic database 127 is acquired, and the content of the acquired topic element is registered in the storage area of data relating to the topic folder of the folder information 143. Besides, the folder corresponding to the topic element registered in the folder information 143 is made to be displayed on the topic folder display part 159. In FIG. 18, the topic folders concerning a topic C and a topic D are generated and displayed. In FIG. 18, the topic folders are recited as “topic C” and “topic D” in order to distinguish them from the user definition folder. Actually, based on the content of the topic element, a word such as, for example, “disease”, “sport”, or “economy” is displayed.
Modified Example of the Second Embodiment of the Invention
The series of processings executed when the RSS reader program 103 shifts to the sleep mode, that is, the second topic set reconstruction processing of the topic database 127 carried out by the topic set reconstructor 131, and the classification processing of the article summaries into the topic set carried out by the topic classifier 133 are not limited to be executed in the sleep mode, but may be executed by the instruction from the user in the normal mode. Alternatively, when the RSS reader program is activated, the series of processings may be carried out.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5442561 *May 10, 1993Aug 15, 1995Nippon Telegraph And Telephone CorporationProduction management system and its application methodUS6727930May 18, 2001Apr 27, 2004Hewlett-Packard Development Company, L.P.Personal digital assistant with streaming information displayUS6772160 *Dec 8, 2000Aug 3, 2004Ingenuity Systems, Inc.Techniques for facilitating information acquisition and storageUS20030014383 *Dec 8, 2000Jan 16, 2003Ingenuity Systems, Inc.Techniques for facilitating information acquisition and storageUS20040133342 *Dec 18, 2003Jul 8, 2004Banker Shailen VLinked information systemUS20050044071 *Jun 8, 2004Feb 24, 2005Ingenuity Systems, Inc.Techniques for facilitating information acquisition and storageUS20060213976 *Jul 15, 2005Sep 28, 2006Fujitsu LimitedArticle reader program, article management method and article reader* Cited by examinerNon-Patent CitationsReference1S. Chakrabarti; "Mining the Web-Discovering Knowledge from Hypertext Data"; Morgan Kaufman, Pub. 2003; pp. 81-89; 133-136; 147-152.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8037403 *Jan 11, 2007Oct 11, 2011Kabushiki Kaisha ToshibaApparatus, method, and computer program product for extracting structured documentUS8180778 *Feb 5, 2010May 15, 2012Google Inc.Generating action trails from web historyUS8560549 *May 14, 2012Oct 15, 2013Google Inc.Generating action trails from web historyUS9361130May 3, 2010Jun 7, 2016Apple Inc.Systems, methods, and computer program products providing an integrated user interface for reading contentUS20070179937 *Jan 11, 2007Aug 2, 2007Kabushiki Kaisha ToshibaApparatus, method, and computer program product for extracting structured documentUS20080162507 *Dec 28, 2006Jul 3, 2008Theodore PapaioannouReally simple syndication (RSS) and database integrationUS20110271228 *May 3, 2010Nov 3, 2011Zumobi, Inc.Systems, Methods, and Computer Program Products Providing an Article Selection Structure* Cited by examinerClassifications U.S. Classification235/380, 235/375International ClassificationG06K5/00Cooperative ClassificationG06F17/30675, G06F17/30716European ClassificationG06F17/30T2P4, G06F17/30T5Legal EventsDateCodeEventDescriptionJul 15, 2005ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:INAKOSHI, HIROYA;OKAMOTO, SEISHI;ASAI, TATSUYA;REEL/FRAME:016786/0328;SIGNING DATES FROM 20050623 TO 20050624Jul 21, 2011FPAYFee paymentYear of fee payment: 4Aug 5, 2015FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services