JP2006260337A - Information processor and processing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate acquisition of interesting-sounding information on the Internet. <P>SOLUTION: A communication module 176 receives and records weighted article metadata transmitted from a client terminal device 11. A display ranking information tabulation part 231 generates display ranking tabulation information based on the recorded weighted article metadata. A display control part 232 displays, based on the generated display ranking tabulation information, a list of articles on a screen of a GUI 173 in the order of ranking. A report ranking information tabulation part 242 generates weighted article metadata based on an article point according to operation of a user 152 and the weighted article metadata. A communication module 176 transmits the generated weighted article metadata to a client terminal device 11 of the other user. According to this, acquisition of possibly interesting-sounding information on the Internet is facilitated. This invention is applicable to an information processor. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus and method, and a program, and more particularly, to an information processing apparatus and method, and a program capable of acquiring information that is likely to be interesting.

  In recent years, with the spread of the Internet, a service referred to as a weblog (so-called blog) has also spread. Weblogs, for example, journalistic articles dealing with social issues, personal news articles with interesting comments, personal diaries and essays, and photos taken by yourself There are various forms such as things, and it is generally a generic name for Web sites that are continuously updated.

  News sites that distribute news over the Internet by newspaper companies and portal sites are also widespread, and users are increasing because they can collect information in real time.

  These weblogs and news sites provide update information through RSS (Resource Description Framework Site Summary) format information (hereinafter also referred to as RSS information) that describes metadata such as website headings and summaries in a structured manner. Thus, it becomes possible to have more users browse the information. In other words, the user can acquire information on an updated site by using an RSS reader (RSS Reader) that reads information in the RSS format, and thus can efficiently browse web logs and news.

  In addition, it is possible to control the cache or log for each arbitrary client group, and automatically create a collection of URLs (Uniform Resource Locator) required by the group to share URL information. There is a URL information sharing system capable of self-regulating information browsing (see, for example, Patent Document 1).

  In addition, preference data composed of operation information (fast forward, pause, rewind, etc.) at the time of content playback and the content viewer's age group, gender, life pattern, etc. are transferred to the server via the network. , Statistically processing the preference data and generating value-added information for each viewer attribute such as age group, gender, life pattern, etc. On the content playback device, popular title search, only playback of popular scenes, bored scenes Some have added value reproduction services such as skip reproduction (for example, see Patent Document 2).

JP 2003-281021 A JP 2002-232823 A

  However, the update information that can be acquired by the user of the RSS reader is only that created by the sender of the web log or news site, and there is a problem that other information cannot be acquired.

  For example, the relationship between a web log or news site and an RSS reader is posted on the web log or news site. It is possible to obtain information filtered by the sender's values, but it is filtered by the value of other viewers. Information could not be obtained.

  Further, for example, the URL information sharing system disclosed in Japanese Patent Application Laid-Open No. 2003-281021 aggregates the content being browsed by a proxy server, so that users who want to share content can use the same proxy server. Had to use.

  Furthermore, for example, the communication apparatus disclosed in Japanese Patent Laid-Open No. 2002-232823 collects all user information and then executes the process. Therefore, the information obtained as a result of the process is averaged and generalized. Therefore, there is a problem that it is not necessarily the content user's preference.

  The present invention has been made in view of such a situation. When a user selects information on the Internet, not only the user's own values but also a person who has a personal exchange with the user himself / herself is selected. By adding values, information that seems to be of interest can be easily acquired with an information filter that only the user himself has.

  The first information processing apparatus of the present invention is an index indicating the frequency of browsing of articles published on a network in a plurality of other information processing apparatuses, and the other information processing apparatuses via the network Receiving means for receiving the indices transmitted from each of them, recording means for recording the received indices, and another information processing apparatus by counting the recorded indices when a predetermined time has elapsed Generating means for generating total information indicating the total browsing frequency for each article in the document, and display control means for controlling display so that the articles are displayed in the order of the total browsing frequency based on the total information. It is characterized by.

  The receiving means is a second user who belongs to the set defined by the first user via the network and is used by the second user who has permitted the first user to receive the indicator. An index including the content of each operation of the second user transmitted from each of the information processing apparatuses is received.

  The first information processing method of the present invention is an index indicating the frequency of browsing articles published on a network in a plurality of other information processing apparatuses, and the other information processing apparatuses A reception control step for controlling the reception of the indicators transmitted from each of them, a recording step for recording the received indicators, and, when a predetermined time has elapsed, by counting the recorded indicators, A generation step for generating aggregate information indicating a total of browsing frequency for each article in the information processing device; and a display control step for controlling display based on the total information so that articles are displayed in the order of the total of browsing frequency; It is characterized by including.

  The first program of the present invention is an index indicating the frequency of browsing articles published on a network in a plurality of other information processing apparatuses, and is transmitted from each of the other information processing apparatuses via the network. A reception control step for controlling reception of the transmitted index, a recording step for recording the received index, and other information processing by counting the recorded index when a predetermined time has elapsed. A generating step for generating total information indicating a total of browsing frequency for each article in the device; and a display control step for controlling display so that the articles are displayed in the order of the total browsing frequency based on the total information. It is characterized by that.

  The second information processing apparatus of the present invention is a first index indicating the frequency of browsing articles published on the network or the content of operations on articles in the first other information processing apparatus, The receiving means for receiving the first index received from the first other information processing apparatus, the recording means for recording the received first index, and the content of the operation on the article by the user The first generating means for generating the second index and the first index that has been recorded and the generated second index when the predetermined first time has elapsed, Second generation for generating a third index according to the frequency of browsing each article in the other information processing apparatus or the content of the operation on each article and the content of the operation on each article And stage, a third indicator which is generated via a network, characterized in that it comprises a transmitting means for transmitting to the first other information processing apparatus or the second other information processing device.

  When the second information processing apparatus has passed a predetermined second time, the second index generated by the first generation means is operated on the article with the passage of time. The reducing means for reducing and the second generating means are configured to calculate the first index by counting the first index and the reduced second index when a predetermined first time has elapsed. A third index is generated in accordance with the frequency of browsing each article in another information processing apparatus or the content of the operation on each article and the content of the operation on each article.

  The second generation means weights the recorded first index or second index when a predetermined first time has elapsed, and both or one of them is weighted By counting the first index and the second index, the frequency of browsing each article in the first other information processing apparatus or the contents of the operation for each article and the contents of the operation for each article in the user A third index corresponding to the above is generated.

  The receiving means is a second user belonging to the set defined by the first user via the network, and the second user who has permitted the first user to receive the first indicator A first index transmitted from each of the first other information processing apparatuses to be used is received.

  The transmitting means uses the generated third index as a first user used by a second user who belongs to the set and permits the transmission of the third index via the network. Transmitting to another information processing apparatus or a second other information processing apparatus used by a third user who belongs to the set and is permitted to transmit the third index. Features.

  The second information processing method of the present invention is a first index indicating the frequency of browsing articles published on the network or the contents of operations on articles in the first other information processing apparatus, A reception control step for controlling reception of the first index received from the first other information processing apparatus, a recording step for recording the received first index, and a user operation on the article. A first generation step for generating a second index indicating the content, and when a predetermined first time has elapsed, by counting the recorded first index and the generated second index The third finger corresponding to the frequency of browsing each article in the first other information processing apparatus or the content of the operation on each article and the content of the operation on each article And a transmission control step for controlling transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network, It is characterized by including.

  The second program of the present invention is a first index indicating the frequency of browsing articles published on the network or the contents of operations on articles in the first other information processing apparatus, via the network. The reception control step for controlling the reception of the first index received from the first other information processing apparatus, the recording step for recording the received first index, and the content of the operation on the article by the user. A first generation step for generating a second index to be shown, and when a predetermined first time has elapsed, the first index recorded and the generated second index are aggregated to The third index corresponding to the frequency of browsing each article on one other information processing apparatus or the content of the operation on each article and the content of the operation on each article A second generation step for generating, and a transmission control step for controlling transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network. It is characterized by including.

  In the first information processing apparatus, the first information processing method, and the first program of the present invention, an index indicating the frequency of browsing articles published on the network in a plurality of other information processing apparatuses. Then, an index transmitted from each of the other information processing apparatuses is received via the network, the received index is recorded, and when a predetermined time has elapsed, the recorded index is aggregated. Thus, total information indicating the total browsing frequency for each article in the other information processing apparatus is generated, and display is controlled so that the articles are displayed in the order of the total browsing frequency based on the total information.

  In the second information processing apparatus, the second information processing method, and the second program of the present invention, the frequency of browsing articles or articles published on the network in the first other information processing apparatus The first index indicating the content of the operation, the first index received from the first other information processing apparatus via the network is received, the received first index is recorded, and the user When the second index indicating the content of the operation on the article is generated and the predetermined first time has elapsed, the recorded first index and the generated second index are aggregated, The third index corresponding to the frequency of browsing each article in the first other information processing apparatus or the content of the operation on each of the articles and the content of the operation on each of the articles in itself is generated. Is a third indicator generated, via the network, is transmitted to the first other information processing apparatus or the second other information processing device.

  According to the present invention, information on the Internet can be collected. In addition, according to the present invention, when the user selects information on the Internet, not only the user's own values but also the values of a person who has personal interaction with the user can be added. Information that seems to be of interest can be obtained easily.

  BEST MODE FOR CARRYING OUT THE INVENTION The best mode of the present invention will be described below. The correspondence relationship between the disclosed invention and the embodiments is exemplified as follows. Although there are embodiments which are described in this specification but are not described here as corresponding to the invention, the embodiments correspond to the invention. It does not mean that it is not a thing. Conversely, even if an embodiment is described herein as corresponding to an invention, that means that the embodiment does not correspond to an invention other than the invention. It is not a thing.

  Further, this description does not mean all the inventions described in the specification. In other words, this description is for the invention described in the specification and not claimed in this application, i.e., for the invention that will be applied for in the future or that will appear as a result of amendment and added. It does not deny existence.

  According to the present invention, a first information processing apparatus is provided. The first information processing apparatus (for example, the client terminal apparatus 11 in FIG. 1) browses articles published on the network in a plurality of other information processing apparatuses (for example, the client terminal apparatus 11 in FIG. 1). The receiving means (for example, the communication module 176 in FIG. 3) that receives the index transmitted from each of the other information processing apparatuses via the network (for example, the network 12 in FIG. 1). 2, the communication unit 109 in FIG. 2 that executes the process of step S 321 in FIG. 31, a recording unit that records the received index (for example, the recording unit 108 in FIG. 2), and a predetermined time elapses. In such a case, a generating unit that generates total information indicating the total frequency of browsing for each article in another information processing apparatus by totaling the recorded indexes ( For example, the display ranking information totaling unit 231 in FIG. 3 and display control means (for example, the display control unit 232 in FIG. 3) that controls the display so that articles are displayed in the order of the total browsing frequency based on the total information. ).

  The receiving means is a second user who belongs to the set defined by the first user via the network and is used by the second user who has permitted the first user to receive the indicator. It is possible to receive an index including the content of each operation of the second user transmitted from each of the information processing apparatuses.

  According to the present invention, a first information processing method is provided. This information processing method is an index indicating the frequency of browsing articles published on the network in a plurality of other information processing devices, and is transmitted from each of the other information processing devices via the network. A reception control step (for example, the process of step S321 in FIG. 31) for controlling the reception of the incoming index, a recording step for recording the received index (for example, the process of step S322 in FIG. 31), and a predetermined time A generation step (for example, the process of step S324 in FIG. 31) that generates total information indicating the total frequency of browsing for each article in another information processing apparatus by totaling the recorded indexes when elapsed. And a display control step (for example, the step of FIG. 31) for controlling the display so that the articles are displayed in the order of the sum of the browsing frequencies based on the total information. And a processing of-flops S325).

  According to the present invention, a first program is provided. The first program is an index indicating the frequency of browsing articles published on the network in a plurality of other information processing apparatuses, and is transmitted from each of the other information processing apparatuses via the network. A reception control step (for example, the process of step S321 in FIG. 31) for controlling the reception of the incoming index, a recording step (for example, the process of step S322 in FIG. 31) for recording the received index, and a predetermined time When the number of times has elapsed, the generation step of generating total information indicating the total frequency of browsing for each article in another information processing apparatus by totaling the recorded indexes (for example, the process of step S324 in FIG. 31) And a display control step for controlling the display so that the articles are displayed in the order of the total frequency of browsing based on the total information (for example, FIG. 31). Processing of step S325) and a.

  This first program can be recorded on a recording medium (for example, the magnetic disk 121 of FIG. 2).

  According to the present invention, a second information processing apparatus is provided. This second information processing apparatus (for example, the client terminal apparatus 11 in FIG. 1) is used for the articles published on the network in the first other information processing apparatus (for example, the client terminal apparatus 11 in FIG. 1). The first index indicating the browsing frequency or the content of the operation on the article, and the first index received from the first other information processing apparatus via the network (for example, the network 12 in FIG. 1). Receiving means (for example, the communication unit 109 in FIG. 2 that executes the process of step S321 in FIG. 31 under the control of the communication module 176 in FIG. 3) and recording means (for example, recording the received first index) 2) and first generation means for generating a second index indicating the content of the operation on the article by the user (for example, the operation point conversion unit 241 in FIG. 3). When a predetermined first time elapses, the first index that has been recorded and the second index that has been generated are aggregated, thereby allowing the browsing of each article in the first other information processing apparatus. Second generation means (for example, the notification ranking information totaling unit 242 in FIG. 3) that generates a third index according to the frequency or the content of the operation for each of the articles and the content of the operation for each of the articles The transmission means for transmitting the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network (for example, under the control of the communication module 176 in FIG. And the communication unit 109 in FIG. 2 that executes the process of step S348 of 32.

  When a predetermined second time has elapsed, the second index generated by the first generation unit is reduced by a decrease unit (for example, FIG. 3) from when the article is operated to the second index. The article point attenuating unit 244) and the second generation unit add up the recorded first index and the reduced second index when a predetermined first time has elapsed. The third index can be generated according to the frequency of browsing each article in the first other information processing apparatus or the content of the operation on each article and the content of the operation on each article in the user. .

  The second generation means weights the recorded first index or second index when a predetermined first time has elapsed, and both or one of them is weighted By counting the first index and the second index, the frequency of browsing each article in the first other information processing apparatus or the contents of the operation for each article and the contents of the operation for each article in the user It is possible to generate a third index according to the above.

  The receiving means is a second user belonging to the set defined by the first user via the network, and the second user who has permitted the first user to receive the first indicator The first index transmitted from each of the first other information processing apparatuses to be used can be received.

  The transmitting means uses the generated third index as a first user used by a second user who belongs to the set and permits the transmission of the third index via the network. Sending to another information processing apparatus or a second other information processing apparatus used by a third user who belongs to the set and is permitted to transmit the third index. it can.

  According to the present invention, a second information processing method is provided. This information processing method is a first index indicating the frequency of browsing articles published on the network or the contents of operations on articles in the first other information processing apparatus. A reception control step (for example, the process of step S321 in FIG. 31) for controlling reception of the first index received from one other information processing apparatus, and a recording step (for example, for recording the received first index) , Processing in step S322 in FIG. 31), a first generation step (for example, processing in step S343 in FIG. 32) for generating a second index indicating the content of the operation on the article by the user, and a predetermined first Each of the articles in the first other information processing apparatus by aggregating the recorded first index and the generated second index. A second generation step (for example, the process of step S346 in FIG. 32) for generating a third index according to the browsing frequency or the content of the operation for each of the articles and the content of the operation for each of the articles The transmission control step for controlling the transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network (for example, the process of step S348 in FIG. 32) ).

  According to the present invention, a second program is provided. This second program is a first index indicating the frequency of browsing articles published on the network or the contents of operations on articles in the first other information processing apparatus, via the network, A reception control step (for example, the process of step S321 in FIG. 31) for controlling reception of the first indicator received from the first other information processing apparatus, and a recording step for recording the received first indicator ( For example, the processing in step S322 in FIG. 31), the first generation step for generating the second index indicating the content of the operation on the article by the user (for example, the processing in step S343 in FIG. 32), the predetermined first When one time has elapsed, the recorded first index and the generated second index are aggregated to obtain that of the article in the first other information processing apparatus. A second generation step (for example, the process of step S346 in FIG. 32) that generates a third index according to the frequency of browsing or the content of the operation on each of the articles and the content of the operation on each of the articles ) And the transmission control step for controlling the transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network (for example, step S348 in FIG. 32). Processing).

  This second program can be recorded on a recording medium (for example, the magnetic disk 121 of FIG. 2).

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

  FIG. 1 is a block diagram showing a configuration of an embodiment of a P2P (Peer to Peer) system 1 to which the present invention is applied.

  In the P2P system 1, client terminal devices 11-1 to 11 -N, a P2P server 13, and an RSS server 14 are connected to a network 12.

  The client terminal devices 11-1 to 11-N are devices connectable to the network 12, such as a personal computer or a PDA (Personal Digital Assistance). Each of the client terminal devices 11-1 to 11-N is an example of an information processing device of the present invention.

  The client terminal device 11-1 transmits various data to any one of the client terminal devices 11-2 to 11-N connected to the network 12 or the P2P server 13 via the network 12, or the client terminal device Various data transmitted from any of 11-2 to 11-N, the P2P server 13, or the RSS server 14 are received.

  For example, the client terminal apparatus 11-1 transmits information in the extended RSS format (hereinafter referred to as weighted article metadata) obtained by extending the RSS format including information such as article points via the network 12 to the client terminal apparatus 11-2. To 11-N. Further, the client terminal device 11-1 receives the weighted article metadata from any of the client terminal devices 11-2 to 11-N via the network 12. Furthermore, the client terminal device 11-1 receives RSS information from the RSS server 14 via the network 12.

  Here, the article point refers to a point that is aggregated for each article, and the articles can be displayed in the ranking order by aggregating the article points.

  The client terminal device 11-2 sends various data to the client terminal device 11-1, the client terminal devices 11-3 to 11-N connected to the network 12, or the P2P server 13 via the network 12. It transmits or receives various data transmitted from any of the client terminal device 11-1, the client terminal devices 11-3 to 11-N, the P2P server 13, or the RSS server 14.

  For example, the client terminal apparatus 11-2 transmits the weighted article metadata to either the client terminal apparatus 11-1 or the client terminals 11-3 to 11-N via the network 12. Further, the client terminal device 11-2 receives the weighted article metadata from either the client terminal device 11-1 or the client terminal devices 11-3 to 11-N via the network 12. Furthermore, the client terminal apparatus 11-2 receives RSS information from the RSS server 14 via the network 12.

  Each of the client terminal devices 11-3 (not shown) to 11-N transmits various data to a client terminal device other than itself or the P2P server 13 connected to the network 12, or a client other than itself. Various data transmitted from the terminal device, the P2P server 13 or the RSS server 14 are received.

  For example, each of the client terminal devices 11-3 (not shown) to 11-N transmits weighted article metadata to client terminals other than itself through the network 12. Each of the client terminal devices 11-3 (not shown) to 11-N receives weighted article metadata from the client terminal devices other than itself through the network 12. Further, each of the client terminal devices 11-3 (not shown) to 11 -N receives RSS information from the RSS server 14 via the network 12.

  The network 12 is, for example, a wireless LAN (Local Area Network), a wired LAN, or the Internet that conforms to standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11a, 802.11b, or 802.11g built in a building. Etc.

  The P2P server 13 is, for example, a dedicated server or a personal computer, and transmits various data to any of the client terminal devices 11-1 to 11-N, or the client terminal devices 11-1 to 11-. Various data transmitted from any one of N are received.

  For example, the P2P server 13 receives a login request (hereinafter referred to as a login request) to the P2P system 1 from the client terminal device 11-1, and executes login processing based on the received login request. Thus, the ID (Identification) (hereinafter referred to as peer ID) for uniquely identifying the user who uses the client terminal device 11-1 and the IP (Internet Protocol) address stored in the peer ID and IP It is registered in an address correspondence table (hereinafter referred to as a peer list). After registering the peer ID and the IP address in the peer list, the P2P server 13 transmits a notification indicating that the user has logged in to the P2P system 1 (hereinafter referred to as a login notification) to the client terminal device 11-1.

  For example, the P2P server 13 requests the client terminal device 11-1 to acquire the IP address of another client terminal device (hereinafter referred to as a name resolution request) (the name resolution request includes a peer ID). ), And by performing name resolution processing based on the peer ID included in the received name resolution request, the IP address corresponding to the received peer ID is obtained from the peer list, and the obtained IP address Is transmitted to the client terminal apparatus 11-1.

  The RSS server 14 is, for example, a dedicated server or a personal computer, and transmits RSS information to any of the client terminal devices 11-1 to 11-N.

  For example, if the RSS server 14 is a news site, the RSS server 14 transmits the news to be distributed to any of the client terminal devices 11-1 to 11-N as RSS information.

  Although the P2P server 13 has been described as executing the login process and the name resolution process, these processes can be executed by different servers. For example, a server (not shown) that performs name resolution processing may be provided separately, and by causing the server to execute name resolution processing, the P2P server 13 may execute only login processing. . In addition, a function for causing a server (for example, a DNS (Domain Name Server) server (not shown) or a SIP (Session Initiation Protocol) server (not shown)) to perform name resolution processing on the network. May be added to cause the server to execute name resolution processing.

  Hereinafter, when it is not necessary to individually distinguish the client terminal device 11-1 to the client terminal device 11-N, they are simply referred to as the client terminal device 11. In addition, any of the client terminal devices 11-1 to 11-N may be any of the client terminal device 11-i, the client terminal device 11-j, the client terminal device 11-k, and the client terminal device 11-n. Called.

  FIG. 2 is a block diagram illustrating a configuration example of the client terminal device 11.

  The CPU 101 executes various processes according to a program stored in the ROM 102 or a program recorded in the recording unit 108. The RAM 103 appropriately stores programs executed by the CPU 101 and data. These CPU 101, ROM 102, and RAM 103 are connected to each other via a bus 104.

  An input / output interface 105 is also connected to the CPU 101 via the bus 104. Connected to the input / output interface 105 are an input unit 106 such as a keyboard and a mouse, and an output unit 107 such as a display. The CPU 101 executes various processes in response to commands input from the input unit 106. Then, the CPU 101 outputs an image or sound obtained as a result of the processing to the output unit 107.

  The recording unit 108 connected to the input / output interface 105 is composed of, for example, a hard disk and records programs executed by the CPU 101 and various data. The communication unit 109 communicates with an external device via the network 12, the Internet, another network, or a communication medium.

  A program may be acquired via the communication unit 109 and recorded in the recording unit 108.

  The drive 110 connected to the input / output interface 105 drives a magnetic disk 121, an optical disk 122, a magneto-optical disk 123, or a semiconductor memory 124 when they are mounted, and programs and data recorded there. Get etc. The acquired program and data are transferred to the recording unit 108 and recorded as necessary.

  FIG. 3 is a diagram illustrating an example of a configuration of a program executed by the client terminal device 11 (an example of a functional configuration).

  The RSS reader 151 as a program is recorded in the recording unit 108 or the ROM 102, for example. The RSS reader 151 is appropriately loaded from the recording unit 108 or the ROM 102 to the RAM 103 and executed by the CPU 101. For example, the RSS reader 151 aggregates the article rankings based on the article points included in the weighted article metadata that is appropriately loaded from the recording unit 108 or the ROM 102 to the RAM 103 and transmitted from another client terminal device. Processing such as displaying article ranking information on a screen displayed by the GUI 173 of the RSS reader 151 is executed.

  The RSS reader 151 is an example of a P2P client program. That is, the P2P client program executed by the client terminal device 11 is not limited to the RSS reader 151, and may be, for example, a content browsing program such as an RSS aggregator (RSS Aggregator) or a Web browser using RSS.

  The login module 171 controls the communication unit 109 to cause the communication unit 109 to transmit a login request, which is a request for login to the P2P system 1, to the P2P server 13 via the network 12. For example, when the RSS reader 151 is activated by the operation of the user 152, the login module 171 causes the communication unit 109 to transmit a login request to the P2P server 13 via the network 12. The login module 171 controls the communication unit 109 to log in from the P2P server 13 via the network 12 to indicate that the P2P server 13 stores the peer ID and the IP address in the peer list in association with each other. The communication unit 109 receives the notification.

  Here, the login request includes at least a peer ID that uniquely identifies the user using the client terminal device 11 and the IP address of the client terminal device 11 used by the user 152.

  The article circulation module 172 controls the communication unit 109 to transmit RSS information provided by a device (for example, the RSS server 14 or a Web server (not shown)) connected to the Internet via the network 12. 109 to receive. The article circulation module 172 controls the communication unit 109 to cause the communication unit 109 to supply the received RSS information to a GUI (Graphical User Interface) 173 for display.

  For example, the article circulation module 172 controls the communication unit 109 to inquire whether or not the article has been updated to the site 153 (RSS server 14) on the Internet via the network 12, and thereby the site 153 on the Internet. The RSS information updated from the (RSS server 14) is received by the communication unit 109, and the received RSS information is supplied to the GUI 173 for display by the communication unit 109.

  The GUI 173 is a user interface of the RSS reader 151, displays an article and allows the user 152 to browse, or accepts an operation by the user 152. For example, the screen displayed by the GUI 173 includes a first pane that displays a peer list, a second pane that displays an article list, and a third pane that displays an article summary or text.

  For example, the GUI 173 displays an article on the display of the output unit 107 based on the RSS information supplied from the article circulation module 172. Further, the GUI 173 displays the articles in the ranking order on the display of the output unit 107 based on the display ranking aggregation information that is information for displaying the article list supplied from the display ranking aggregation module 178 described later in the ranking order.

  Further, the GUI 173 displays an arrow icon displayed at the head of the name of the peer displayed in the first pane based on the peer list display information that is information related to the display of the peer list supplied from the display control unit 202. Display (change).

  The GUI 173 is configured to include a user operation sensor 191 and a first pane peer list management unit 192.

  The user operation sensor 191 detects an operation on the GUI 173 (of the RSS reader 151) by the user 152, and supplies user operation information indicating the detected operation of the user 152 to the operation point conversion unit 241.

  For example, the user operation sensor 191 causes the user A to double-click an article that is “Today's Weather” in the article list displayed in the second pane of the screen displayed by the GUI 173 of the RSS reader 151, When the operation for displaying the text in the pane is performed, the user operation information including the operation of the user A who is “double click” and the information of the article which is “Today's weather” whose text is displayed in the third pane, This is supplied to the operation point conversion unit 241.

  The first pane peer list management unit 192 supplies a request corresponding to the operation of the user 152 to the peer list management unit 201.

  For example, the first pane peer list management unit 192 supplies a peer registration request to the peer list management unit 201 when an operation of newly registering a peer (connection with the other party) is performed by the operation of the user 152. In addition, the first pane peer list management unit 192 performs a peer permission request when an operation of permitting a peer (connection with a partner) is performed (as a providing destination for providing weighted article metadata) by an operation of the user 152. The data is supplied to the peer list management unit 201. Further, the first pane peer list management unit 192 makes a peer rejection request when an operation of rejecting a peer (connection with a partner) (as a providing destination for providing weighted article metadata) is performed by an operation of the user 152. The data is supplied to the peer list management unit 201. Further, the first pane peer list management unit 192 supplies a peer deletion request to the peer list management unit 201 when an operation of deleting a registered peer (connection with the other party) is performed by the operation of the user 152. .

  The peer list management module 174 performs various processes on the peer list 175. For example, the peer list management module 174 determines the peer ID of the peer to receive weighted article metadata from the peer channel list 211 of the peer list 175 based on the peer registration request supplied from the first pane peer list management unit 192. Execute the process such as storing in.

  The peer list management module 174 is configured to include a peer list management unit 201, a display control unit 202, and a peer determination unit 203.

  The peer list management unit 201 makes a request to the peer list 175 based on a request (for example, a peer registration request, a peer permission request, a peer rejection request, or a peer deletion request) supplied from the first pane peer list management unit 192. Then, a predetermined process is executed.

  For example, based on the peer registration request supplied from the first pane peer list management unit 192, the peer list management unit 201 assigns peer IDs of peers for which weighted article metadata is to be provided to the peer channel list 211 of the peer list 175. To store. For example, the peer list management unit 201 uses the peer registration request of the user B supplied from the first pane peer list management unit 192 as a peer ID of the user B who is a partner who wants to receive weighted article metadata. The peer ID of user B who is “bbb@bbb.ne.jp” is stored in the peer channel list 211 of the peer list 175.

  In addition, the peer list management unit 201 supplies the communication module 176 with a name resolution request that is a request for acquiring the IP address of the client terminal device 11 of the other party to whom the provision of weighted article metadata is desired. For example, when acquiring the IP address of the client terminal device 11 used by the user B, the peer list management unit 201 uses “bbb” as a name resolution request for acquiring the IP address of the client terminal device 11 used by the user B. The name resolution request including the peer ID of the user B who is “@ bbb.ne.jp” is supplied to the communication module 176.

  Furthermore, when the communication unit 109 receives the IP address corresponding to the name resolution request, the peer list management unit 201 determines the partner to receive weighted article metadata based on the IP address supplied from the communication unit 109. The peer ID and the IP address are associated with each other and stored in the peer cache 213 of the peer list 175 recorded in the recording unit 108. For example, the peer list management unit 201 is a partner who wants to receive weighted article metadata based on the IP address of the client terminal device 11 used by the user B who is “192.168.1.10” supplied from the communication unit 109. A peer ID “bbb@bbb.ne.jp” of a certain user B and an IP address of the client terminal device 11 used by the user B “192.168.1.10” are associated with each other and recorded in the recording unit 108. Stored in the peer cache 213 of the current peer list 175.

  In addition, the peer list management unit 201 supplies the communication module 176 with a recipe entry registration request that is a request for permission to a partner who wants to receive weighted article metadata. For example, the peer list management unit 201 uses the peer ID of the user A who is “aaa@aaa.ne.jp”, the IP address of the client terminal device 11 which the user A is using which is “172.31.2.3”, and “ A recipe entry registration request including the IP address of the client terminal device 11 used by the user B who is 192.168.1.10 ″ is supplied to the communication module 176.

  Here, the recipe entry list registration request includes the peer ID of the client and the IP address of the client terminal device 11 being used, and the IP address of the client terminal device 11 used by the other party who wants to receive weighted article metadata. At least.

  Further, the peer list management unit 201 determines the peer of the user who has transmitted the recipe entry registration request based on the response message “permitted” indicating that the weighted article metadata supplied from the peer determination unit 203 is provided. The ID is stored in the recipe entry list 212 of the peer list 175 recorded in the recording unit 108.

  Here, the response message is information indicating whether or not to provide weighted article metadata to the user who has transmitted the recipe entry list registration request. , If it is determined to provide the weighted article metadata to the party requesting the provision of the weighted article metadata, the response message “permitted” is supplied to the peer list management unit 201, When the peer determining unit 203 determines that the weighted article metadata is not provided to the other party who requests the provision of the weighted article metadata by the operation of the user 152, the peer determining unit 203 sends a response message “rejected”. The data is supplied to the peer list management unit 201.

  Further, the peer list management unit 201 obtains the IP address of the provision destination of the weighted article metadata (peer ID stored in the recipe entry list 212) from the peer cache 213 of the peer list 175 recorded in the recording unit 108. The IP address of the acquired weighted article metadata is supplied to the communication module 176 as destination information.

  For example, when a predetermined time elapses, the peer list management unit 201 retrieves the weighted article metadata from the peer cache 213 recorded in the recording unit 108 (“aaa @ stored in the recipe entry list 212”). The IP address of the client terminal device 11 used by the user A “172.31.2.3” is acquired as the IP address of the user A (peer ID of the user A “aaa.ne.jp”), and the acquired “172.31.2.3” A certain IP address is supplied to the communication module 176 as destination information.

  Under the control of the communication module 176, the display control unit 202 provides weighted article metadata to the other party who has transmitted the recipe entry registration request based on the recipe entry registration request supplied from the communication unit 109. A dialog box for determining whether or not is displayed on the GUI 173.

  For example, the display control unit 202 uses the communication module 176 to control the use of the user A peer ID “172.31.2.3” and the user A peer ID “aaa@aaa.ne.jp” supplied from the communication unit 109. Based on the recipe entry registration request that includes the IP address of the client terminal device 11 that is currently operating, the GUI 173 displays a dialog box for determining whether to provide weighted article metadata to the user A.

  Further, the display control unit 202 generates peer list display information based on a response message that is either “permitted” or “rejected” transmitted from the client terminal device 11. The display control unit 202 supplies the generated peer list display information to the GUI 173.

  The peer determination unit 203 determines whether or not to provide weighted article metadata to the partner who has transmitted the recipe entry registration request by the operation of the user 152, and “permit” or “permission” according to the determination result. A response message indicating any of “reject” is supplied to the peer list management unit 201.

  For example, when it is determined that the weighted article metadata is provided to the partner who has transmitted the recipe entry registration request by the operation of the user 152, the peer determination unit 203 has transmitted the recipe entry registration request. In response to this, a response message indicating “permitted” indicating that the weighted article metadata is provided is supplied to the peer list management unit 201, and in response thereto, weighting is performed on the partner who has transmitted the recipe entry registration request. If it is determined that the article metadata is not provided, a response message “reject” indicating that the weighted article metadata is not provided to the peer that has transmitted the recipe entry registration request to the peer list management unit 201. Supply.

  The peer list 175 is recorded in the recording unit 108, and includes information on peers who are providers or recipients of weighted article metadata, as well as peer IDs of the peers and IP addresses of the client terminal devices 11 used by the peers. Stored in correspondence.

  The peer list 175 includes a peer channel list 211, a recipe entry list 212, and a peer cache 213.

  The peer channel list 211 is a provider (peer) list of weighted article metadata recorded in the recording unit 108 and held by the side receiving the weighted article metadata, for example. For example, since the peer channel list 211 stores the peer ID of the provider (peer) of the weighted article metadata, the provider (peer) of the weighted article metadata is specified from the provider (peer) list. Can do.

  Also, the weighted article metadata provider (peer (peer ID)) stored in the peer channel list 211 is “requesting information from peer”, “provided by peer”, “peer The status of “Provision of information from refusal” or “Registration deletion requested” is stored in association with each other, and the weighted article metadata provider (peer) is in any status. Furthermore, the weighted article metadata provider (peer (peer ID)) stored in the peer channel list 211 stores a connection state of “online” or “offline” in association with the weighted article metadata. The provider (peer) of metadata is in any connection state.

  The connection state is determined by whether or not the RSS reader 151 is activated in the client terminal device 11 used by the weighted article metadata provider (peer) and communication with the P2P server 13 is possible. Is done. That is, when the client terminal device 11 can normally log in to the P2P server 13 and is registered in the peer list of the P2P server 13, the connection state is “online”, while the client terminal device 11 When the P2P server 13 cannot log in and is not registered in the peer list of the P2P server 13, the connection state is “offline”.

  When the connection state is a connection state of “online”, the name of the peer can be resolved, so that the weighted article metadata is received from the client terminal device 11 used by the weighted article metadata provider (peer). Can be provided. On the other hand, when the connection state is a connection state of “offline”, the name resolution of the peer is impossible. Therefore, the weighted article meta data is received from the client terminal device 11 used by the weighted article metadata provider (peer). Data cannot be provided.

  The recipe entry list 212 is, for example, a weighted article metadata recipient (peer) list recorded in the recording unit 108 and held by the weighted article metadata providing side. For example, since the recipe entry list 212 stores the peer ID of the recipient (peer) of the weighted article metadata, the receiver (peer) of the weighted article metadata is specified from the recipient (peer) list. Can do.

  In addition, the recipient of the weighted article metadata stored in the recipe entry list 212 (peer (peer ID)) is “requested information from peer”, “providing information to peer”, or “ The status “registration deletion requesting” is stored in association with each other, and the recipient (peer) of the weighted article metadata is in any status. Further, the connection state of “online” or “offline” is stored in association with the recipient (peer (peer ID)) of the weighted article metadata stored in the recipe entry list 212, and the weighted article is stored. The recipient (peer) of the metadata is in any connection state.

  Similarly to the connection status of the peer channel list 211, the RSS reader 151 is activated in the client terminal device 11 used by the receiver (peer) of the weighted article metadata, and the connection status is communicated with the P2P server 13. It is determined by whether or not this is possible. That is, when the client terminal device 11 can normally log in to the P2P server 13 and is registered in the peer list of the P2P server 13, the connection state is “online”, while the client terminal device 11 When the P2P server 13 cannot log in and is not registered in the peer list of the P2P server 13, the connection state is “offline”.

  When the connection state is a connection state of “online”, the name of the peer can be resolved. Therefore, the weighted article metadata is used by the client terminal device 11 used by the weighted article metadata recipient (peer). Can be provided. On the other hand, when the connection state is “offline”, the peer name cannot be resolved. Therefore, the weighted article metadata is used as the client terminal device used by the weighted article metadata recipient (peer). 11 can not be provided.

  In the above-described example, the peer channel list 211 and the recipe entry list 212 have been described separately, but can be combined into one list. In that case, store the “provider (sender) flag” in association with the weighted article metadata provider (peer (peer ID)), and the weighted article metadata recipient (peer (peer ID)) The “recipient flag” may be stored in association with ().

  The peer cache 213 is stored in the recording unit 108 or the RAM 103, for example, and stores the peer ID of the peer and the IP address of the client terminal device 11 used by the peer in association with each other.

  Although details will be described later, for peers for which the data corresponding to the peer ID and the IP address is not stored in the peer cache 213, the data corresponding to the peer ID and the IP address is obtained by inquiring the P2P server 13. The IP address of the client terminal device 11 used by the peer that is not stored in the peer cache 213 is acquired, and the acquired IP address and the peer ID are associated with each other and stored in the peer cache 213.

  The communication module 176 controls the communication unit 109 to cause the communication unit 109 to transmit various data to the other client terminal device 11 or the P2P server other than itself through the network 12. The communication module 176 controls the communication unit 109 via the network 12 to cause the communication unit 109 to receive various data from other client terminal devices 11 or the P2P server 13 other than itself.

  For example, the communication module 176 controls the communication unit 109 to send a recipe entry list registration request supplied from the peer list management module 174 to the client unit 11-i (RSS reader) via the network 12. 151-i) Send to address. The communication module 176 controls the communication unit 109 to communicate a response message indicating “permitted” or “denied” from the client terminal device 11-i (RSS reader 151-i) via the network 12. Unit 109 to receive.

  For example, the communication module 176 controls the communication unit 109 to cause the communication unit 109 to receive a recipe entry request from the client terminal device 11-j (RSS reader 151-j) via the network 12. The communication module 176 controls the communication unit 109 to send a response message indicating either “permitted” or “deny” supplied from the peer list management module 174 to the communication unit 109 via the network 12. It is transmitted to the terminal device 11-j (RSS reader 151-j).

  Further, for example, the communication module 176 controls the communication unit 109 to send weighted article metadata from the client terminal device 11-k (RSS reader 151-k) used by the peer to the communication unit 109 via the network 12. Receive. The communication module 176 controls the communication unit 109 to transmit the weighted article metadata to the communication unit 109 via the network 12 to the client terminal device 11-n (RSS reader 151-n) used by the peer. Let

  Further, for example, the communication module 176 controls the communication unit 109 to cause the communication unit 109 to transmit the name resolution request supplied from the peer list management module 174 to the P2P server 13 via the network 12. The communication module 176 controls the communication unit 109 to cause the communication unit 109 to receive an IP address from the P2P server 13 via the network 12.

  The weighted article metadata 177 is recorded in, for example, the recording unit 108, and includes the peer ID of the weighted article metadata provider and the client terminal used by the weighted article metadata provider as elements of general RSS information. Elements of extended RSS information such as the IP address of the apparatus 11 and article points of articles are added. Also, the weighted article metadata 177 recorded in the recording unit 108 is read from the display ranking information totaling unit 231, the notification ranking information totaling unit 242, or the metadata generation unit 243.

  For example, weighted article metadata transmitted from the RSS reader 151-k of the client terminal device 11-k is recorded in the recording unit 108 as weighted article metadata 177.

  The display ranking totaling module 178 totals the article points of the article list to be displayed on the screen (second pane) displayed by the GUI 173 of the RSS reader 151 of the client terminal device 11 used by the user 152 (self).

  The display ranking totaling module 178 is configured to include a display ranking information totaling unit 231 and a display control unit 232.

  The display ranking information totaling unit 231 is information of article points obtained by reading the weighted article metadata 177 recorded in the recording unit 108 and totaling the article points for each article included in the read weighted article metadata 177. Aggregate as display ranking aggregation information. The display ranking information totaling unit 231 supplies the display ranking totaling information to the display control unit 232.

  For example, the display ranking information totaling unit 231 reads and reads the weighted article metadata 177 received from the client terminal device 11 used by the user B and the client terminal device 11 used by the user C recorded in the recording unit 108. The article points for each article included in the weighted article metadata 177 are aggregated as display ranking aggregation information, and the aggregated display ranking aggregation information is supplied to the display control unit 232.

  Note that the display ranking information totaling unit 231 is not limited to the method of totalizing the display ranking totaling information from the weighted article metadata 177 recorded in the recording unit 108, and further includes, for example, articles by the operation of the user 152 (self). The display ranking total information may be totaled after adding article points to.

  The display control unit 232 displays the article list on the screen (second pane) displayed by the GUI 173 in order of ranking based on the display ranking total information supplied from the display ranking information totaling unit 231.

  The notification ranking aggregation module 179 is an RSS reader 151 of the client terminal device 11 used by the peer (the other party) (for example, an RSS reader 151-i of the client terminal device 11-i, an RSS reader 151-j of the client terminal device 11-j). The article points of the article list to be displayed on the screen (second pane) displayed by the GUI 173 of the RSS reader 151-k of the client terminal device 11-k or the RSS reader 151-n of the client terminal device 11-n) To do.

  The notification ranking totaling module 179 is configured to include an operation point conversion unit 241, a notification ranking information totaling unit 242, a metadata generation unit 243, and an article point attenuation unit 244.

  The operation point conversion unit 241 gives article points to an article viewed by the user 152 based on user operation information supplied from the user operation sensor 191. The operation point conversion unit 241 supplies information on an article to which an article point is given (hereinafter referred to as a user operation article point) to the notification ranking information totaling unit 242.

  For example, the operation point conversion unit 241 has the user's operation and subscription state (article executed by the user A) that is “double click” included in the user operation information supplied from the user operation sensor 191. Based on the above information, the user A can double-click the article that is “Today's weather” and the text is displayed in the third pane. Then, “+4 points” is given, and the user operation article points including the information of the article “Today's weather” to which the article points “+4 points” are given are supplied to the notification ranking information totaling unit 242.

  The notification ranking information totaling unit 242 is based on the user operation article points supplied from the operation point conversion unit 241 and the weighted article metadata 177 read out from the recording unit 108, and the article points collected for notifying the other party (peer) The notification ranking total information which is the information of the above is totaled. The notification ranking information totaling unit 242 supplies the totaled notification ranking totaling information to the metadata generation unit 243.

  For example, the notification ranking information totaling unit 242 includes information on the article “Today's weather” to which the article point “+4 points” supplied from the operation point conversion unit 241 is given, and the client terminal used by the user B Based on the weighted article metadata 177 received from the device 11 and the client terminal device 11 used by the user C, the notification ranking aggregation information is aggregated, and the aggregated notification ranking aggregation information is supplied to the metadata generation unit 243.

  Further, the notification ranking information totaling unit 242 weights the articles based on the user operation article points supplied from the operation point conversion unit 241 and the read weighted article metadata 177, and totals the notification ranking total information. The notification ranking information totaling unit 242 supplies the totaled notification ranking totaling information to the metadata generation unit 243.

  In other words, articles can be weighted, such as emphasizing article points given by their own operations, or neglecting (not emphasizing) article points given by their own operations.

  The metadata generation unit 243 (for providing to other users (peers) based on the notification ranking aggregation information supplied from the notification ranking information aggregation unit 242 and the weighted article metadata 177 read from the recording unit 108). Generate weighted article metadata. The metadata generation unit 243 supplies the generated weighted article metadata (for providing to the peer) to the communication module 176.

  Note that the processing for generating weighted article metadata (to be provided to other users (peers)) executed by the metadata generation unit 243 may be executed by the notification ranking information totaling unit 242.

  The article point attenuating unit 244 attenuates the article points of the user operation article supplied from the operation point conversion unit 241 (decreases as time elapses).

  For example, the article point attenuating unit 244 reduces the article point by “+1 point” every time a predetermined time elapses. More specifically, the article point attenuating unit 244 adds the article point “+4 points” supplied from the operation point conversion unit 241 every time one hour has passed to the article that is “Today's weather”. “+1 point” is subtracted from the user operation article point including the information. That is, the article point of the article that is “Today's weather” becomes “+3 points” after one hour.

  FIG. 4 is a block diagram illustrating a configuration example of the P2P server 13.

  The CPU 301 executes various processes according to a program stored in the ROM 302 or a program recorded in the recording unit 308. The RAM 303 appropriately stores programs executed by the CPU 301 and data. The CPU 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304.

  An input / output interface 305 is also connected to the CPU 301 via the bus 304. The input / output interface 305 is connected to an input unit 306 including a keyboard and a mouse and an output unit 307 including a display. The CPU 301 executes various processes in response to commands input from the input unit 306. Then, the CPU 301 outputs an image or sound obtained as a result of the processing to the output unit 307.

  The recording unit 308 connected to the input / output interface 305 includes, for example, a hard disk and records programs executed by the CPU 301 and various data. The communication unit 309 communicates with an external device via the network 12, the Internet, another network, or a communication medium.

  Alternatively, the program may be acquired via the communication unit 309 and recorded in the recording unit 308.

  A drive 310 connected to the input / output interface 305 drives a magnetic disk 321, an optical disk 322, a magneto-optical disk 323, a semiconductor memory 324, or the like when they are loaded, and programs and data recorded there. Get etc. The acquired program and data are transferred to the recording unit 308 and recorded as necessary.

  FIG. 5 is a diagram illustrating an example of a configuration of a program executed by the P2P server 13 (an example of a functional configuration).

  The server module 351 is recorded in the recording unit 308 or the ROM 302, for example. The server module 351 is appropriately loaded from the recording unit 308 or the ROM 302 to the RAM 303 and executed by the CPU 301. For example, the server module 351 is appropriately loaded from the recording unit 308 or the ROM 302 to the RAM 303 and recorded in the recording unit 308 in association with the peer ID and the IP address in the login request received from the client terminal device 11. Processing to be stored in the peer list 362 is executed.

  The server module 351 includes a registration deletion acceptance module 361, a peer list 362, and a name resolution module 363.

  The registration deletion acceptance module 361 controls the communication unit 309 to cause the communication unit 309 to receive the login request transmitted from the client terminal device 11 via the network 12. Also, the registration deletion accepting module 361 associates the peer ID with the IP address in the login request received from the client terminal device 11, and records the peer list 362 (the peer ID and the IP address) recorded in the recording unit 308. In the correspondence table). Furthermore, the registration deletion acceptance module 361 controls the communication unit 309 to notify the communication unit 309 via the network 12 that the user has successfully logged in (the peer ID and the IP address are in the peer list 362). A login notification that is stored) is transmitted to the client terminal device 11.

  Here, the login request refers to a request transmitted from the client terminal device 11 attempting to log in to the P2P system 1 and includes at least the peer ID and the IP address of the client terminal device 11. For example, in the case of a login request from the client terminal device 11 used by the user A, at least the peer ID of the user A “aaa@aaa.ne.jp” and the user “172.31.2.3” are included in the login request. The IP address of the client terminal device 11 used by A is included.

  For example, the registration deletion accepting module 361 controls the communication unit 309 to transmit the peer ID of the user A “aaa@aaa.ne.jp” and “172.31. 2.3 ”causes the communication unit 309 to receive a login request including at least the IP address of the client terminal device 11 used by the user A, and among the received login requests, the user A who is“ aaa@aaa.ne.jp ” Is associated with the IP address of the client terminal device 11 used by the user A who is “172.31.2.3” and stored in the peer list 362 recorded in the recording unit 308. Then, the registration deletion accepting module 361 controls the communication unit 309 so that the client terminal device 11 that uses the user A for a login notification indicating that the user A has successfully logged in to the communication unit 309 via the network 12. Send to address.

  When the registration deletion reception module 361 receives a request for deleting a user having a peer ID stored in the peer list 362 from the client terminal device 11 via the network 12, the registration deletion reception module 361 is recorded in the recording unit 308. Among the data stored in the existing peer list 362, data matching the received peer ID is deleted.

  The peer list 362 is recorded in the recording unit 308, and stores a peer ID and an IP address of a user (peer) logged in to the P2P system 1 in correspondence with each other.

  For example, the peer list 362 stores the IP address of the client terminal 11 used by the user A “172.31.2.3” for the peer ID of the user A “aaa@aaa.ne.jp”. , The IP address of the client terminal device 11 used by the user B “192.168.1.10” is stored for the peer ID of the user B “bbb@bbb.ne.jp”, and “ccc@ccc.ne The IP address of the client terminal device 11 used by the user C “192.168.2.7” is stored for the peer ID of the user C “.jp”. That is, in this case, user A, user B, and user C are logged in to the P2P system 1.

  The name resolution module 363 controls the communication unit 309 to cause the communication unit 309 to receive a name resolution request transmitted from the client terminal device 11 via the network 12. Further, the name resolution module 363 acquires the IP address stored corresponding to the peer ID from the peer list 362 recorded in the recording unit 308 based on the name resolution request received from the client terminal apparatus 11. . Further, the name resolution module 363 controls the communication unit 309 to cause the communication unit 309 to transmit the IP address acquired from the peer list 362 to the client terminal device 11 via the network 12.

  Further, as described above, the name resolution request is a request for the client terminal apparatus 11 to inquire of the P2P server 13 about the IP address when the client terminal apparatus 11 wants to obtain the IP address of another client terminal apparatus. It is. The name resolution request includes at least the peer ID of the peer that uses the client terminal device having the IP address to be acquired.

  For example, the name resolution module 363 controls the communication unit 309 to transmit the IP of the client terminal device 11 used by the user B transmitted from the client terminal device 11 used by the user A via the network 12. A client terminal used by the user A by causing the communication unit 309 to receive a name resolution request (for example, information including at least the peer ID of the user B “bbb@bbb.ne.jp”) for acquiring the address The name resolution request (for example, “bbb@bbb.ne.jp”) that is received from the device 11 and for acquiring the IP address of the client terminal device 11 used by the user B is included at least. Information), from the peer list 362 recorded in the recording unit 308, the use of user B who is “192.168.1.10” corresponding to the peer ID of user B who is “bbb@bbb.ne.jp”. The IP address of the client terminal device 11 being used is acquired.

  Then, the name resolution module 363 controls the communication unit 309 to acquire the IP address of the client terminal device 11 used by the user B from the peer list 362 to the communication unit 309 via the network 12. The IP address “192.168.1.10” is transmitted to the client terminal device 11 used by the user A (inquired).

  Next, a screen (user interface of the RSS reader 151 screen) displayed by the GUI 173 of the RSS reader 151 activated in the client terminal device 11 will be described with reference to FIGS.

  First, the overall configuration of the screen displayed by the GUI 173 of the RSS reader 151 will be described with reference to FIG.

  The screen displayed on the GUI 173 includes a first pane 401, a second pane 402, and a third pane 403.

  The first pane 401 is a title (hereinafter, referred to as a web log or a news site (a site where newspapers, portal sites, etc. distribute news over the Internet)) that provide articles to be circulated as described above. (Referred to as an article providing site) in a tree view format. The first pane 401 displays users (peers) belonging to the community defined by the user in a tree view format.

  Here, a community is a group (group) of users (peers) who have a common hobby, topic, work, etc. For example, a community that is a group of people who like soccer, A community which is a “development section” is arbitrarily defined by the user 152 as a group of people who work on software development.

  FIG. 7 is a diagram for explaining the concept of community in the present invention.

  In the example shown in FIG. 7, a community defined by each of user A and user B is shown. The left side in the figure is a community defined by user A, and the right side in the figure is a community defined by user B. In addition, user A and user B have a peer relationship (peer relationship) because they belong to a community defined by each other.

  As shown on the left side of the example shown in FIG. 7, the user A registers a community that is “company related” and “friend” as a community. In addition, as users belonging to the community “company related”, users “user B” and “user C” are registered, and as users belonging to the community “friend”, “user 1” is registered. ”And“ User 2 ”are registered.

  Therefore, the user A receives the weighted article metadata transmitted from the “user B” and the “user C” belonging to the “company related” community defined by the user A and defined by the user A. Weighted article metadata transmitted from “user 1” and “user 2” belonging to the community that is “friend” is received.

  Further, as shown on the right side of the example shown in FIG. 7, the user B registers a community that is “development section 1”, “development section 2”, and “friend” as the community. In addition, a user who is “User A” is registered as a user who belongs to the community that is “Development 1 Section”, and a user that is belonging to the community that is “Development 2 Section” is “User C”. A user is registered, and users who are “user α” and “user β” are registered as users who belong to the community that is “friend”.

  Accordingly, the user B receives the weighted article metadata transmitted from the “user A” belonging to the community which is the “development 1 section” defined by the user B, and the “development 2 section” defined by the user B The weighted article metadata transmitted from “user C” belonging to the community “” is received. In addition, the user B receives weighted article metadata transmitted from “user α” and “user β” belonging to the community that is the “friend” defined by the user B.

  In the example shown in FIG. 7, the user A associates the user who is “user B” as a member of the community which is “company related” in the community he / she defines. Further, the user B associates the user who is “user A” as a member of the community which is “development 1 section” in the community he / she defines.

  That is, since the community is defined by each user, for example, for user A, user B belongs to the company, but for user B, user A belongs to the development section 1. Even if the users are in peer relationships, the communities to which they belong may differ.

  In addition, in the example shown in FIG. 7, the user A associates the users who are “user 1” and “user 2” as members of the community who is “friend” in the community he / she defines. Further, the user B associates the users who are “user α” and “user β” as members of the community who is “friend” in the community he / she defines.

  That is, “User 1” and “User 2” belong to the community defined by the user A, but the community defined by the user B is “User α”. In addition, even if users who are in a peer relationship define the same community, such as “User β” belongs, the users belonging to the community may be different.

  Further, in the example shown in FIG. 7, the user A associates the user who is “user C” as a member of the community which is “company related” in the community he / she defines. In addition, the user B associates the user who is “user C” as a member of the community which is “development 2 section” in the community he / she defines.

  That is, for user A, “user C” belongs to “company related”, but for user B, “user C” belongs to “development 2 division”, and so on. However, the community to which they belong may be different.

  In this way, since the community is arbitrarily defined by each user, the defined community does not always match for each user, and even if the communities do not match, a peer relationship may be established. it can.

  The first pane 401 has a tab (hereinafter referred to as a feed tab) for displaying the title of the content to be circulated and a tab (hereinafter referred to as a peer tab) for displaying the names of users belonging to the community defined by the user. ), And the content displayed is switched by selecting each tab by the operation of the user 152.

  The second pane 402 displays an article list that is a list of obtained articles by visiting sites that provide articles of interest.

  In the display order of articles displayed in the second pane 402, when the feed tab of the first pane 401 is selected, the update date is displayed in order from the newest article, and the peer tab of the first pane 401 is selected. In this case, articles are displayed in order from the article with the highest article point.

For example, in the example shown in FIG. 6, when the feed tab of the first pane 401 is selected, the second pane 402 displays “DVD rental test at the store, Donal Macdo _... ”, “Japan Talecom Negotiation Negotiations / Bankso _… ”,“ Centre Technologies, U.S. territory _… ”,“ Banksoft considers acquisition of Japan Talecom _… ”,“ Buy shoplifting books, prevent use of IC tags _… ”,“ New Askry, encrypt email destinations _… ”, "Entering a printer in Japan / Dr. Chairman's statement", "English Darbophone, mobile music distribution oni _... ", "Ony, 2099 to launch" Ruse "built-in TV", "Small Nippon Printing, projector screen _... " , “News, wireless LAN connection, billing on the spot _… ” are displayed in the order of update date.

  Details of the case where the peer tab of the first pane 401 is selected will be described later (for example, FIG. 24 described later). However, by adding article points for each article and totaling them, the second pane 402 can be displayed in order from the article with the highest article point. As a result, the display order of the articles displayed in the second pane 402 is the ranking of the articles in the community to which the user 152 belongs, and the article displayed at the top of the article list is the user 152. This is the most popular (popular) article in the community to which.

  The second pane 402 is displayed when one of the article providing sites displayed on the first pane 401 is selected by the operation of the user 152 when the feed tab of the first pane 401 is selected. Only the articles provided from the selected article providing site are displayed.

  The third pane 403 displays an overview (summary) of the single-clicked article when any article in the article list displayed in the second pane 402 is single-clicked by the operation of the user 152. Let

  The third pane 403 displays the text of the double-clicked article when any article in the article list displayed in the second pane 402 is double-clicked by the operation of the user 152. .

  For example, in the example shown in FIG. 6, the title of the article that is “Ony,“ Lucce ”built-in TV in 2099” in the article list displayed in the second pane 402 by the operation of the user 152 is displayed. If double-clicked, the body of the article, “Oney, to launch“ Rusee built-in TV in 2099 ””, “Ony ’s chairman, according to the coverage of the Dainippon Keizai Shimbun on the 24th,“ by 2099 "Announced the policy to announce the TV equipped with. Is displayed in the third pane 403.

  Furthermore, when the third pane 403 is single-clicked by an operation of the user 152 in a state where the article summary (summary) is displayed in the third pane 403, the main text of the displayed article summary is displayed. .

  On the toolbar 404, buttons for performing various settings of the RSS reader 151 for the user 152 are arranged.

  For example, the toolbar 404 displays “File (F)”, “Feed (D)”, “Peer (P)”, “Tool (T)”, or “Help (H)” to the user 152. On the other hand, various settings are made. Further, for example, the toolbar 404 includes “feed addition”, “category addition”, “batch update”, “all read”, “peer registration”, “group addition”, “return”, “forward”, and the like. Displaying the icon causes the user 152 to execute various processes.

  In the above example, the GUI 173 of the RSS reader 151 provided with the three panes, ie, the first pane 401, the second pane 402, and the third pane 403 has been described. However, the number of panes is two. Or four or more may be sufficient. That is, the present invention is not limited by the number of panes displayed by the GUI 173 of the RSS reader 151.

  Further, the peer tab interface of the first pane 401 or the article point totaling function (function of the present invention) is used as a plug-in, for example, a general RSS reader (ie, having the function of the present invention). (Not RSS reader) or a content browsing program such as a Web browser. For example, by publishing the function of the present invention as a plug-in on the Internet, each user using a general RSS reader can download and install the plug-in quickly and easily. The function of the present invention can be added.

  Next, the details of the first pane 401 will be described with reference to FIGS. 8 and 9.

  FIG. 8 is a diagram illustrating an example of the first pane 401 when the feed tab 421 is selected.

  As described above, the tab 411 is provided in the first pane 401, and when the feed tab 421 is selected by the operation of the user 152, the article providing site to be visited is displayed in the first pane 401. When the peer tab 422 is selected, the first pane 401 displays the names of users (peers) belonging to the community defined by the user.

  That is, the example shown in FIG. 8 represents the first pane 401 when the feed tab 421 is selected by the operation of the user 152.

  In the first pane 401, the title of the article providing site is displayed in a tree view format for each category.

  For example, in the first pane 401, categories “web log” and “news site” are registered with “field route” as the root. Then, the title of the article providing site belonging to the category “Web log” and the title of the article providing site belonging to the category “News site” are displayed in a tree view format.

  Specifically, as an article providing site belonging to the category of “Web log”, “ABC in English”, “network style”, “SW's memo”, “[N]”, “TT White Report”, “ "Web log" with the title "Sync A World", "TellaJun", "next today", "Yuet", "Base Zero", or "Hot Hot Hot" is registered. That is, the client terminal apparatus 11 receives RSS information, which is information such as update information described in the RSS format, from these “web logs”.

  In addition, as article providing sites belonging to the category of “news site”, “CCC NET Japan”, “Dodd Slash”, “NEWS WIRED”, “INTERNET”, “ITs media”, “yuuhi.com”, “ "News site" with the title of "Daikei IT", "Dai Nikkei-RSS", "Dai Fami.com", "Digi Typhoon", "What PC" or "What AV" is registered. That is, the client terminal apparatus 11 receives RSS information, which is information such as update information described in the RSS format, from these “news sites”.

  FIG. 9 is a diagram illustrating an example of the first pane 401 when the peer tab 422 is selected.

  The example shown in FIG. 9 represents the first pane 401 when the peer tab 422 is selected by the operation of the user 152.

  In the first pane 401, the names of peers are displayed in a tree view format for each community (group).

  For example, in the first pane 401, communities that are “love soccer” and “development section” are registered with a peer route as a route. The peers of the users who belong to the community “I love soccer” and the peers of the users who belong to the community “development section” are displayed in a tree view format.

  Specifically, “user B” and “user C” are registered as users belonging to the community “I love soccer”.

  That is, the user 152 defines “user B” and “user C” as belonging to the community “I love soccer”, and “user B” who belongs to the community “I love soccer”. Also, weighted article metadata that is information obtained by adding article points and the like for the article to the RSS information is received from “user C”.

  In addition, “user W”, “user X”, “user Y”, and “user Z” are registered as users who belong to the community that is “development section”.

  That is, the user 152 defines that “user W”, “user X”, “user Y”, and “user Z” belong to the community which is “development section”, and “development section”. Weighted articles, which are information in which article points etc. for articles are added to RSS information from "User W", "User X", "User Y", and "User Z" who belong to the community Receive metadata.

  An arrow icon displayed at the top of the name of a peer belonging to the community indicates the relationship between the user 152 and the peer.

  Next, the relationship between the user 152 and the peer will be described with reference to FIG.

  In the example shown in FIG. 10, the user 152 and “user B” who belongs to the community “I love soccer” displayed in the first pane 401 when the peer tab 422 of FIG. 9 is selected. The relationship will be described as an example.

  In the example shown in FIG. 10, the first column shows information on the peer channel list 211, and the first row shows information on the recipe entry list 212. In the information of the peer channel list 211 in the first column, the item “not requesting information from user B” in the second line is “requesting information from user B” in the third line. A certain item, an item “information is supplied from user B” on the fourth line, and an item “information provision from user B has been refused” are shown on the fifth line.

  Further, in the information of the recipe entry list 212 in the first row, an item “information is not requested from user B” in the second column, “information from user B is requested in the third column” In the fourth column, an item “providing information to user B” is shown.

  More precisely, information is requested from the client terminal device 11 used by the user B. In the following description, “requesting information from user B” more precisely means “requesting information from client terminal device 11 used by user B”. The same applies to other operations.

  In addition, an arrow icon in FIG. 10 indicates a relationship between the user 152 and a peer of a user who belongs to the same community as the user 152 (for example, a “user B” peer). A white arrow icon in FIG. 10 indicates that information (weighted article metadata) is currently being supplied to the peer or information is being supplied from the peer. In addition, a hatched arrow icon in FIG. 10 indicates that information is currently being requested from the peer or that information has been requested from the peer. Furthermore, the black arrow icon in FIG. 10 indicates that the supply of information is now refused by the peer. If there is no arrow icon, it indicates that there is no relationship for exchanging information with the peer.

  If the direction of the arrow icon is facing the character side indicating the peer user (for example, “User B”), this indicates that information is being provided to the peer, and the peer user When facing the opposite side of the character indicating (for example, “User B”), it indicates that information is provided from the peer.

  In the example shown in FIG. 10, “non-display” in the second column from the left and the second from the top indicates that the user 152 and “Mr. User B” have no relationship to exchange information. In addition, the hatched arrow icon in the third column from the left and facing the second “user B” from the top is “no request for information from user B” and “from user B Indicates that information is requested. Furthermore, the white arrow icon pointing to “User B” in the fourth column from the left and pointing to the second from the top is “No information requested from User B” and “To User B”. "Information is being provided."

  In the example shown in FIG. 10, the hatched arrow icon pointing to the opposite side of “User B” in the second column from the left and the third from the top is “Requesting information from User B”. "And information is not requested from user B". In addition, the hatched arrow icon facing the opposite side of “User B” in the third column from the left and the third from the top, and the hatched arrow icon facing “User B” are “User "B is requesting information" and "user B is requesting information". Furthermore, the diagonal arrow icon facing the opposite side to “User B” in the fourth column from the left and the third from the top, and the white arrow icon facing “User B” are “User "Information is being requested from Mr. B" and "Information is being provided to user B".

  Further, in the example shown in FIG. 10, the white arrow icon facing the opposite side to the “user B” in the second row from the left and the fourth from the top is “information provided by the user B”. "And information is not requested from user B". In addition, a white arrow icon facing the opposite side to “User B” in the third column from the left and the fourth from the top, and a hatched arrow icon facing “User B” are “User” "Information is provided by Mr. B" and "Information is requested by user B". Furthermore, the white arrow icon facing the opposite side to “User B” in the fourth column from the left and the fourth from the top, and the white arrow icon facing “User B” “Information is provided from Mr. B” and “Information is being provided to user B”.

  In addition, in the example shown in FIG. 10, the black arrow icon facing the opposite side to the “user B” in the second column from the left and the fifth from the top indicates that “information provision from user B is denied. "And information is not requested from user B". Also, the black arrow icon facing the opposite side of “User B” in the third column from the left and the fifth from the top, and the hatched arrow icon facing “User B” are “User” "Providing information from Mr. B has been rejected" and "Information has been requested from user B". Furthermore, the black arrow icon facing the opposite side of “User B” in the fourth column from the left and the fifth from the top, and the hatched arrow icon facing “User B” are “User” “Information provision from Mr. B has been refused” and “Information is being provided to user B”.

  Note that the relationship between the user 152 and the peer is not always a fixed relationship, and is appropriately changed by an operation of the user 152 or the other user's peer. For example, if a hatched arrow icon is displayed in the second column from the left in FIG. 10 and facing the opposite side to the third “user B” from the top, “request information from user B” When the provision of information is permitted by the operation of “user B”, the side opposite to the “user B” in the second column from the left in FIG. It is changed to the white arrow icon that faces, and the state is “information is provided from user B”.

  Further, when a peer (for example, “User B”) withdraws from the community (when the peer is deleted), the second column from the left in FIG. (That is, the withdrawn peer is not displayed in the first pane 401).

  Furthermore, in the example shown in FIG. 10, in the state of “providing information to user B” in the fourth column, when provision of information is denied to “user B” (“user B” is When it is determined that the information of the user 152 is no longer necessary), the display of the first pane 401 is in a state of “no information is requested from user B” in the second column. Similarly, in the example shown in FIG. 10, when the user 152 stops receiving in the state of “Information provision from user B has been refused” on the fifth line, the display of the first pane 401 is The second line is in a state of “not requesting information from user B”.

  Thus, in the first pane 401, the arrow icon described above is displayed at the head of the peer name, so that the user 152 can instantly grasp the relationship with the peer.

  Next, the details of the RSS information and the weighted article metadata described above will be described with reference to FIGS.

  First, the relationship between RSS information transmitted and received between terminals and weighted article metadata will be described with reference to FIG.

  In the example shown in FIG. 11, each of the RSS server 14 that provides the news site A451, news site B452, and blog site 453 on the upper side in the figure has a structure of metadata such as a headline and a summary of the Web site that it provides. The RSS information, which is the information in the RSS format described in a converted form, is transmitted to the client terminal device 11.

  Also, the lower user A, user B, and user C in the figure indicate the client terminal devices 11 used by those users, and each of the news site A 451, news site B 452, and blog site 453 is shown. Receive the provided RSS information.

  Further, each of the client terminal devices 11 used by the user A, the user B, and the user C on the lower side in the figure is an article from the client terminal device 11 used by a user belonging to the community defined by the user. Receives weighted article metadata, which is information obtained by adding article points to the RSS information.

  That is, in the example shown in FIG. 11, among solid lines and dotted lines connecting terminals, the solid line indicates that RSS information is transmitted or received, and the dotted line indicates that weighted article metadata is transmitted or received. Indicates.

  In the following description of FIG. 11, it is assumed that the user A uses the client terminal device 11-i, the user B uses the client terminal device 11-j, and the user C uses the client terminal device 11-k. explain.

  The news site A451 is a news site that, for example, a newspaper company or a portal site distributes news over the Internet by providing the RSS server 14, and the client terminal device uses the headline or summary of the distributed news as RSS information. 11-i and the client terminal device 11-j.

  Similar to news site A451, news site B452 is a news site that distributes news over the Internet, and transmits RSS information to client terminal apparatus 11-k.

  The blog site 453 is, for example, a personal diary or an essay, a photograph taken by the user by using the RSS server 14 of a portal site or by using an RSS server 14 of a portal site by a certain user (individual). As RSS information to the client terminal device 11-k.

  For example, the user A has “user B” and “user C” belonging to a community defined by the user A. Therefore, the client terminal device 11-i used by the user A receives the weighted article metadata from the client terminal device 11-j used by the user B and the client terminal device 11-k used by the user C.

  User B, for example, makes “User A” and “User C” belong to a community that he / she defines. Accordingly, the client terminal device 11-j used by the user B receives weighted article metadata from the client terminal device 11-i used by the user A and the client terminal device 11-k used by the user C.

  For example, the user C makes “User B” belong to a community defined by the user C. Accordingly, the client terminal device 11-k used by the user C receives the weighted article metadata from the client terminal device 11-j used by the user B.

  As described above, the client terminal device 11 used by the user receives the RSS information from the RSS server 14 that provides the news site and the blog site, and the user belonging to the community defined (registered) by the user. The weighted article metadata transmitted from the client terminal device 11 to be used is received.

  In other words, the client terminal device 11 used by the user does not receive the weighted article metadata from the RSS server 14, and the RSS information is received from the client terminal device 11 used by the user belonging to the community defined by the user. It can be said that it does not receive.

  FIG. 12 is an example of elements of RSS information.

  RSS information is information composed of general elements described in the RSS format. In other words, the RSS information describes, for example, the page title, address, summary, update date and time of the website.

  In the example shown in FIG. 12, the first column shows the elements of the RSS information, and the second column shows the contents of the elements of the RSS information. The RSS information element in the first column includes an item “version information” as “RSS information” in the second row, an item “RSS site information” in the third to fifth rows, and 6 to 14. On the line, an item which is “item information” is shown.

  Furthermore, among the items “RSS site information” on the 3rd to 5th lines, the item “channel information” on the 3rd line, the item “title information” on the 4th line, the 5th line, An item which is “link information” is shown. Among items that are “item information” on the 6th to 14th rows, items that are “item information 1” on the 6th to 8th rows, items that are “item information 2” on the 9th to 11th rows, In the 12th to 14th lines, an item “item information N” is shown.

  Among the items of “Item Information 1” on the 6th to 8th lines, the item of “Title Information” on the 6th line, the item of “Link Information” on the 7th line, and the “Summary” on the 8th line. Items that are "" are shown. Among the items of “Item Information 2” on the 9th to 11th lines, the item of “Title Information” on the 9th line, the item of “Link Information” on the 10th line, Items that are “summary” are shown. Furthermore, among the items of “Item Information N” on the 12th to 14th rows, the item of “Title Information” on the 12th row, the item of “Link Information” on the 13th row, Items that are “summary” are shown.

  “1.0” in the second column from the top in the second column of FIG. 12 indicates that the RSS version is “1.0”. In the second row, the third from the top, “http://www.XXXX.com/rss.rdf”, is the URL for connecting to RSS information as “http://www.XXXX.com/rss.rdf”. XXXX.com/rss.rdf ”. Further, the fourth “XXXX dotcom” in the second row from the top indicates that the title of the RSS information is “XXXX dotcom”. In the second row, “http://www.XXXX.com/”, which is the fifth from the top, is the URL of the site that is the target of RSS information, such as a homepage or a new page. Indicates www.XXXX.com/ “.

  That is, in the second column of FIG. 12, the second to fifth items from the top indicate information related to the entire RSS information.

  In the second row, the sixth item “Olympic Nippon Judo Gold” from the top indicates that the title of the article in Item Information 1 is “Olympic Nippon Judo Gold”. In the second row, the seventh item from the top, “http://www.XXXX.com/news/YYYYMMDD_01.html”, is the URL of the article with item information 1 “http://www.XXXX.com/ Indicates news / YYYYMMDD_01.html “. Furthermore, in the second row, the 8th “Japan Judo XX player from the top defeated XX player on his back and won the championship.“ The summary of the item information 1 article was “Japan Judo XX player” Defeated XX player on his back and won the championship.

  That is, the sixth to eighth items from the top of the second column in FIG.

  In the second row, the ninth item “Victory Japan National Soccer Country A” from the top indicates that the title of the item information 2 article is “Victory Japan National Soccer Country A”. In the second row, the 10th item from the top, “http://www.XXXX.com/news/YYYYMMDD_02.html”, is the URL of the item information 2 article “http://www.XXXX.com/ Indicates news / YYYYMMDD_02.html “. Furthermore, in the second row, the 11th item from the top “Last 46 minutes, △△ player's shot was decided, and 2-1 was defeated in Country A.“ The summary of the item information 2 article ” △△ The player's shot was decided, and 2-1 was defeated in country A.

  That is, the ninth to eleventh items from the top of the second column in FIG.

  In the second column, the 12th “ZONY new service development” from the top indicates that the title of the article of item information N is “ZONY new service development”. In the second row, the 13th “http://www.XXXX.com/news/YYYYMMDD_0N.html” in the top row is the URL of the article with item information N “http://www.XXXX.com/ Indicates news / YYYYMMDD_0N.html “. In the second row, the 14th from the top, “ZONY Co., Ltd.” will start a new service nationwide on the month X. “There is a summary of the article on Item Information N” “ZONY Co., Ltd. New service will be rolled out nationwide from day X.

  That is, the 12th to 14th items from the top of the second column in FIG.

  The RSS server 14 describes the elements described with reference to FIG. 12 and the contents corresponding to the elements in the RSS format and publishes them as RSS information.

  Next, a description example of RSS information will be described with reference to FIG. The description example of the RSS information in FIG. 13 is described so as to correspond to the example of the elements of the RSS information in FIG.

  The RSS information is described in a format based on, for example, an XML (eXtensible Markup Language) format that is a markup language. In the XML format, an element is expressed by sandwiching element content data between a start tag and an end tag. Further, in the XML format, the tagged elements are described in a so-called nested structure, so that the inclusion relation of the elements is expressed, and the characteristics and properties of a certain element are expressed as attributes.

  The first line describes an XML declaration. The XML declaration declares the version of the XML standard that the XML document conforms to and the character code to be used. “<? Xml version =“ 1.0 ”encoding =“ UTF-8 ”?>” On the first line indicates that the XML version is “1.0” and the XML character code is “UTF-8”. .

  The second to fifth lines are namespace declaration statements. By declaring a namespace using the xmlns attribute, elements (vocabularies) defined in the URL of the namespace can be used.

  "<Channel rdf about =" http://www.XXXX.com/rss.rdf ">" on the 6th line and "</ channel>" on the 25th line belong to the channel element in the 7th to 24th lines Indicates that In the channel element, information about the entire RSS information is described.

  “<Title> XXXX.com </ title>” on the seventh line indicates that the title of the RSS information is “XXXX.com”.

  The “<link> http://www.XXXX.com/ </ link>” on the 8th line indicates that the URL of the site that is the target of RSS information, such as a homepage or a new page, is “http: // www Indicates that it is .XXXX.com / “.

  The 9th line "<description> XXXX.com's blog. </ Description>" indicates that the RSS information summary is "XXXX.com's blog."

  “<Dc: language> ja </ dc: language>” on the 10th line indicates that the language of the RSS information is “Japanese”.

  "<Dc: rights> Copyright 2004 XXXX Company. All rights reserved. No reproduction or republication without written permission. </ Dc: rights>" on the 11th to 12th lines is copyrighted by "XXXX Company". It shows that.

  “<Dc: date> 2004/09/06 10:15:45 </ dc: date>” on the 13th line indicates whether the date when the RSS information was created or the date when the RSS information was published is “2004 / 09/06 10:15:45 ”.

  “<Dc: publisher> XXXX company </ dc: publisher>” on the 14th line indicates that the site where the RSS information is published is “XXXX company”.

  “<Dc: creator> XXXX company </ dc: creator>” on the 15th line indicates that the creator of the RSS information is “XXXX company”.

  The 16th line "<syn: updatePeriod> hourly </ syn: updatePeriod>" and the 17th line "<syn: updateFrequency> 1 </ syn: updateFrequency>" update the RSS information once every hour. Indicates that

  “<Items>” on the 18th line and “</ items>” on the 24th line indicate that the 19th to 23rd lines belong to the items element. The items element corresponds to a table of contents of an article described by the item element described later, which is described after the channel element. Also, “<rdf: Seq>” on the 19th line and “</ rdf: Seq>” on the 23rd line indicate that articles described by the item element are arranged in a predetermined order (Sequence).

  "<Rdf: li rdf: resource =" http://www.XXXX.com/news/YYYYMMDD_01.html?ref=rss "/>" on the 20th line is the first article described in the item element The table of contents (lines 26 to 32) is shown. In addition, in “<rdf: li rdf: resource =“ http://www.XXXX.com/news/YYYYMMDD_01.html?ref=rss ”/>” on the 20th line, the rdf: resource attribute of the rdf: li element Corresponds to the rdf: about attribute of the item element on the 26th line.

  "<Rdf: li rdf: resource =" http://www.XXXX.com/news/YYYYMMDD_02.html?ref=rss "/>" on line 21 is the second article described in the item element The table of contents (lines 33 to 39) is shown. Also, in the line 21 <rdf: li rdf: resource = "http://www.XXXX.com/news/YYYYMMDD_02.html?ref=rss" /> ", the rdf: resource attribute of the rdf: li element Corresponds to the rdf: about attribute of the item element on the 33rd line.

  "<Rdf: li rdf: resource =" http://www.XXXX.com/news/YYYYMMDD_0N.html?ref=rss "/>" on the 22nd line is the Nth article described by the item element The table of contents (line 40 to 46) is shown. Also, in “<rdf: li rdf: resource =" http://www.XXXX.com/news/YYYYMMDD_0N.html?ref=rss "/>” on the 22nd line, the rdf: resource attribute of the rdf: li element Corresponds to the rdf: about attribute of the item element on the 40th line.

  "<Item rdf: about =" http://www.XXXX.com/news/YYYYMMDD_01.html?ref=rss ">" on the 26th line and "</ item>" on the 32nd line are the 20th line Indicates the specific content of the article shown as the table of contents in the rdf: resource attribute of the rdf: li element (table of contents). Also, in “<item rdf: about =" http://www.XXXX.com/news/YYYYMMDD_01.html?ref=rss ">” on line 26, the rdf: about attribute of the item element is the line 20 This corresponds to the rdf: resource attribute of the rdf: li element.

  “<Title> Olympic Japanese Judo Gold </ title>” on line 27 indicates that the title of the first article is “Olympic Japanese Judo Gold”.

  “<Link> http://www.XXXX.com/news/YYYYMMDD_01.html?ref=rss </ link>” on line 28 is the URL of the first article “http: //www.XXXX .com / news / YYYYMMDD_01.html? ref = rss “

  On line 29, “<description> Japan Judo XX player defeated XX player on his back and won the championship. </ Description>” is the summary of the first article, “Japan Judo XX player Xx Defeated one player on the back and won the championship. "

  “<Dc: subject> Sport </ dc: subject>” on the 30th line indicates that the category of the first article is “sports”.

  "<Dc: date> 2004/09/06 10:15:45 </ dc: date>" on line 31 is the date when the first article was created or the date when the first article was published One of them indicates “2004/09/06 10:15:45”.

  "<Item rdf: about =" http://www.XXXX.com/news/YYYYMMDD_02.html?ref=rss ">" on line 33 and "</ item>" on line 39 are on line 21 Indicates the specific contents of the article shown as the table of contents in the rdf: resource attribute of the rdf: li element (table of contents). In addition, in line 33 <item rdf: about = "http://www.XXXX.com/news/YYYYMMDD_02.html?ref=rss">, the rdf: about attribute of the item element is This corresponds to the rdf: resource attribute of the rdf: li element.

  “<Title> Japan national soccer team A victory </ title>” on the 34th line indicates that the title of the second article is “Japan national soccer team A victory”.

  “<Link> http://www.XXXX.com/news/YYYYMMDD_02.html?ref=rss </ link>” on the 35th line is the URL of the second article “http: //www.XXXX .com / news / YYYYMMDD_02.html? ref = rss “.

  In line 36, “<description> The latter half 46 minutes △△ The player's shot was decided and 2-1 was defeated by country A. </ Description>” △ The player's shot was decided, and the country A was defeated in 2-1 ”.

  “<Dc: subject> Sports </ dc: subject>” on the 37th line indicates that the category of the second article is “sports”.

  “<Dc: date> 2004/09/06 21:11:10 </ dc: date>” on line 38 is the date when the second article was created or the date when the second article was published One of them is “2004/09/06 21:11:10”.

  "<Item rdf: about =" http://www.XXXX.com/news/YYYYMMDD_0N.html?ref=rss ">" on the 40th line and "</ item>" on the 46th line are the 22nd line Indicates the specific contents of the article shown as the table of contents in the rdf: resource attribute of the rdf: li element (table of contents). In addition, in “<item rdf: about =" http://www.XXXX.com/news/YYYYMMDD_0N.html?ref=rss ">” on the 40th line, the rdf: about attribute of the item element is the 22nd line. This corresponds to the rdf: resource attribute of the rdf: li element.

  “<Title> ZONE new service development </ title>” on the 41st line indicates that the title of the Nth article is “ZONE new service development”.

  “<Link> http://www.XXXX.com/news/YYYYMMDD_0N.html?ref=rss </ link>” on line 42 is the URL of the Nth article “http: //www.XXXX Indicates that .com / news / YYYYMMDD_0N.html? ref = rss “.

  On line 43, “<description> ZONY Co., Ltd. will launch a new service nationwide from XX month x day. </ Description>” is a summary of the Nth article “ZONY KK "New service nationwide expansion will start on the day."

  “<Dc: subject> Economy </ dc: subject>” on the 44th line indicates that the category of the Nth article is “economy”.

  "<Dc: date> 2004/09/06 23:12:55 </ dc: date>" on the 45th line is the date when the Nth article was created or the date when the Nth article was published One of them is “2004/09/06 23:12:55”.

  As described above, RSS information is described.

  Next, an example of elements of weighted article metadata will be described with reference to FIG.

  The weighted article metadata is information obtained by extending RSS information described in the RSS format. In other words, the weighted article metadata is extended with, for example, general page elements such as website titles, addresses, summaries, and update dates, as well as peer IDs, IP addresses, and article points. Information is also described.

  In the example shown in FIG. 14, the first column shows elements of weighted article metadata, and the second column shows contents of elements of weighted article metadata. The elements of the weighted article metadata in the first column include the items “transmission peer information” in the second to fourth lines, the item “item information” in the fifth to fourteenth lines, and the fifteenth line. , Items that are “weighted article metadata” are shown.

  Furthermore, among the items of “transmission peer information” on the second to fourth lines, the item of “data type” on the second line, the item of “peer ID” on the third line, the fourth line , An item “transmission date and time” is shown. Among items that are “item information” on the 5th to 14th rows, items that are “item information 1” are on the 5th to 9th rows, and items that are “item information N” are on the 10th to 14th rows. It is shown.

  Of the items that are “Item Information 1” on the 5th to 9th lines, the item that is “URL” on the 5th line, the item that is “Article Point” on the 6th line, and “FeedURL” on the 7th line In the eighth line, the item “Title” is shown in the eighth line, and the item “Summary” is shown in the ninth line. Of the items of “Item Information N” on the 10th to 14th rows, the item of “URL” on the 10th row, the item of “Article Point” on the 11th row, The item “FeedURL”, the item “Title” on the 13th line, and the item “Summary” on the 14th line are shown.

  “Rss-send” in the second column from the top in FIG. 14 indicates that the data type of the weighted article metadata is “rss-send”. In the second column, “bbb@bbb.ne.jp” in the third row from the top indicates that the peer ID of the sender is “bbb@bbb.ne.jp”. Furthermore, in the second column, “2004/09/06 10:15:45”, which is the fourth from the top, the time when the weighted article metadata is transmitted is “2004/09/06 10:15:45” Indicates.

  That is, in the second column of FIG. 14, the second to fourth rows from the top indicate information related to the entire weighted article metadata.

  “Http://www.XXXX.com/news/YYYYMMDD_01.html” in the second row from the top is the URL of the item information 1 article “http://www.XXXX.com/news/ YYYYMMDD_01.html ". In the second column, the sixth “0.7” from the top indicates that the article point of the article of item information 1 is “0.7”. In the second row, the 7th “http://www.XXXX.com/rss.rdf” from the top is the FeedURL of the item information 1 article (the URL of the RSS information that contained the article). Indicates "http://www.XXXX.com/rss.rdf". In the second row, the eighth item “Olympic Japanese Judo Gold” from the top indicates that the title of the article in Item Information 1 is “Olympic Japanese Judo Gold”. In addition, the 9th “Japan Judo XX player from the top of the second row defeated XX player on his back and won the championship.“ Has a summary of item information 1 ”Japan Judo XX player × × Defeated the player with a single shoulder and won the championship.

  That is, the fifth to ninth rows from the top of the second column in FIG. 14 show specific information related to the item information 1.

  “Http://www.YYYY.com/sport/a.html”, the 10th item from the top of the second row, is the URL of the article information item http://www.YYYY.com/sport/a Indicates that it is .html. The eleventh “0.5” from the top of the second column indicates that the article point of the article of item information N is “0.5”. In addition, “http://www.YYYY.com/RSS/rss.rdf” in the 12th column from the top of the second row is the FeedURL of the article of item information N is “http://www.YYYY.com/ RSS / rss.rdf ”. The 13th “Japan National Soccer Team Training Camp” from the top of the second column indicates that the title of the item information N article is “Japanese National Soccer Training Camp Start”. Furthermore, the 14th “Japanese soccer team started training camp at the facility in Sakura City, Chiba Prefecture from the 6th” in the top of the second row is “summary of Japanese soccer team is 6 The training camp started at the facility in Sakura City, Chiba Prefecture from the day. "

  That is, the 10th to 14th rows from the top of the second column in FIG.

  “10000 ms” in the 15th row from the top of the second column indicates that the transmission interval of the weighted meta article data is 10000 milliseconds (ms).

  Next, a description example of weighted article metadata will be described with reference to FIG. The description example of the weighted article metadata in FIG. 15 is described so as to correspond to the example of the elements of the weighted article metadata in FIG.

  The weighted article metadata is described in, for example, an XML format that is a markup language.

  “<Rra>” on the first line and “</ rra>” on the 24th line indicate that the 2nd to 23rd lines belong to the rra element. Here, the rra element is an arbitrarily defined element, so other elements may be designated.

  “<Datatype> rss_send </ datatype>” on the second line indicates that the data type is “rss_send”.

  “<Peerid> bbb@bbb.ne.jp </ peerid>” in the third line indicates that the sender's peer ID is “bbb@bbb.ne.jp”.

  “<Date> 2004/09/06 10:15:45 </ date>” on the fourth line indicates that either the date when the weighted article metadata was created or the date when the weighted article metadata was published is “2004 / 09/06 10:15:45 ”.

  “<Message>” on the 5th line and “</ message>” on the 22nd line indicate that the 6th to 21st lines belong to the message element. “<Ranking>” on the 6th line and “</ ranking>” on the 21st line indicate that the 7th to 20th lines belong to the ranking element.

  “<Item>” on the 7th line and “</ item>” on the 13th line indicate that the 8th to 12th lines belong to the item element.

  “<Url> http://www.XXXX.com/news/YYYYMMDD_01.html </ url>” on the 8th line indicates that the URL of the first article is “http://www.XXXX.com/news /YYYYMMDD_01.html ”.

  “<Score> 0.7 </ score>” on the ninth line indicates that the article point of the first article is “0.7”.

  “<Feedurl> http://www.XXXX.com/rss.rdf </ feedurl>” on the 10th line indicates that the FeedURL of the first article is “http://www.XXXX.com/rss.rdf ".

  “<Title> Olympic Japanese Judo Gold </ title>” on the 11th line indicates that the title of the first article is “Olympic Japanese Judo Gold”.

  In the 12th line, “<description> Japan Judo XX player defeated XX player on his back and won the championship. </ Description>” is the summary of the first article “Japan Judo XX player Xx Defeated one player on the back and won the championship. "

  “<Item>” on the 14th line and “</ item>” on the 20th line indicate that the 15th to 19th lines belong to the item element.

  “<Url> http://www.YYYY.com/sports/a.html </ url>” on the 15th line indicates that the URL of the Nth article is “http://www.YYYY.com/sports /a.html ”.

  “<Score> 0.5 </ score>” on the 16th line indicates that the article point of the Nth article is “0.5”.

  The 17th line “<feedurl> http://www.YYYY.com/RSS/rss.rdf </ feedurl>” has the FeedURL of the Nth article “http://www.YYYY.com/RSS /rss.rdf ”.

  “<Title> Japan soccer camp start </ title>” on the 18th line indicates that the title of the Nth article is “Japan soccer camp start”.

  The 19th “<description> Japan Soccer Team has started a camp at a facility in Sakura City, Chiba Prefecture on the 6th. </ Description>” is a summary of the Nth article “ , We started a training camp at a facility in Sakura City, Chiba Prefecture on the 6th. "

  The weighted article metadata is described as described above.

  As described above, the client terminal apparatus 11 logged in the P2P system 1 adds the elements of the extended RSS information such as the peer ID, the IP address, and the article point to the elements of the general RSS information in FIG. 14 is transmitted to other peers, or the weighted article metadata transmitted from other peers is received. As a result, the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 activated on the client terminal device 11 can display articles in the ranking order.

  That is, by using the weighted article metadata described with reference to FIG. 14, not only updated articles can be displayed, but also articles can be displayed in order of ranking.

  In the above-described example, the elements of data type, peer ID, article point, FeedURL, and transmission interval have been described as elements for extending RSS information in FIG. 12, but elements for expanding RSS information are not limited to these. For example, the RSS information can be expanded, for example, by adding another element of the article point and counting the article points different from the first article point.

  Next, a case where the client terminal apparatus 11 logs in to the P2P system 1 of the present invention will be described with reference to FIGS. 16 and 17.

  16 and 17, the client terminal apparatus 11 that has not yet logged in to the P2P system 1 and is about to log in is referred to as the client terminal apparatus 11-i and has already logged in to the P2P system 1. Device 11 (client terminal device 11 surrounded by dotted line 501 in FIG. 16) will be described as client terminal device 11-j and client terminal device 11-k.

  A user who uses the client terminal device 11-i is referred to as user A, a user who uses the client terminal device 11-j is referred to as user B, and a user who is using the client terminal device 11-k. Is referred to as user C, and the user A using the client terminal device 11-i is assigned a peer ID “aaa@aaa.ne.jp” and an IP address “172.31.2.3”. User B using the terminal device 11-j is assigned a peer ID “bbb@bbb.ne.jp” and an IP address “192.168.1.10”, and uses the client terminal device 11-k. The user C is assigned a peer ID “ccc@ccc.ne.jp” and an IP address “192.168.2.7”.

  First, with reference to FIG. 16, an outline of processing when the client terminal apparatus 11 logs in to the P2P system 1 will be described.

  For example, when the RSS reader 151 is activated by the operation of the user A, the client terminal device 11-i sends a login request, which is a request for logging in to the P2P system 1, to the P2P server 13 via the network 12. Send.

  Note that the timing for transmitting the login request to the P2P server 13 is not limited to when the RSS reader 151 is activated. For example, a login button (not shown) on the screen displayed by the GUI 173 of the RSS 151 is pressed by the operation of the user A. When the RSS reader 151 is activated, a login dialog (not shown) is displayed, and the use of the service of the P2P system 1 is started when login is selected by the operation of the user A. What is necessary is just to make it transmit at a timing.

  The login request includes at least the peer ID and IP address of the user (for example, the client terminal device 11-i). For example, in the case of a login request from the user A using the client terminal apparatus 11-i, the login request includes at least the peer ID of the user A “aaa@aaa.ne.jp” and “172.31.2.3”. The IP address of a certain client terminal device 11-i is included.

  The P2P server 13 records the peer list 362 in the recording unit 308, and the peer list 362 stores the peer ID and IP address of the user who has logged into the P2P system 1 in correspondence with each other. For example, in the peer list 362 recorded by the P2P server 13, for the peer ID of the user B who is “bbb@bbb.ne.jp”, the client terminal device 11 -j which is “192.168.1.10”. The IP address is stored, and the IP address of the client terminal device 11-k that is “192.168.2.7” is stored for the peer ID of the user C that is “ccc@ccc.ne.jp”. That is, in this case, user B and user C are logged in to the P2P system 1.

  Here, the P2P server 13 receives the login request transmitted from the client terminal device 11-i via the network 12. At this time, the P2P server 13 stores the peer ID and the IP address in the peer list 362 recorded in the recording unit 308 in accordance with the login request transmitted from the client terminal device 11-i in association with each other.

  Specifically, in the peer list 362 recorded by the P2P server 13, the client terminal device 11 that is “192.168.1.10” is associated with the peer ID of the user B that is “bbb@bbb.ne.jp”. -J IP address is stored, the IP address of the client terminal device 11-k "192.168.2.7" is stored for the peer ID of the user B "ccc@ccc.ne.jp", and , The IP address of the client terminal device 11-i “172.31.2.3” is stored for the peer ID of the user A “aaa@aaa.ne.jp” (dotted line 502 in FIG. 16). The IP address of the client terminal device 11-i “172.31.2.3” is added to the peer ID of the user A who is “aaa@aaa.ne.jp” surrounded by “). That is, in this case, user A, user B, and user C are logged in to the P2P system 1.

  The P2P server 13 stores the peer ID of the user A and the IP address of the client terminal device 11-i in the peer list 362, and then sends the client terminal device 11-i to the P2P system 1 via the network 12. Send a login notification indicating that you are logged in.

  The client terminal device 11-i receives a login notification from the P2P server 13 via the network 12. The user A knows that the client terminal device 11-i has successfully logged in to the P2P system 1 by receiving the login notification from the P2P server 13.

  Thus, since the P2P server 13 holds the information of users who are logged in to the P2P system 1 by the peer list 362, for example, when the client terminal device 11 wants to acquire information of other users, By making an inquiry to the P2P server 13, information on other users can be acquired.

  Next, login processing of the P2P system 1 will be described with reference to the flowchart of FIG.

  In step S101, the CPU 101 of the client terminal device 11-i activates the RSS reader 151 when the icon of the execution file of the RSS reader 151 is double-clicked by the operation of the user A, for example.

  In step S <b> 102, the login module 171 of the client terminal device 11-i controls the communication unit 109 to cause the communication unit 109 to transmit a login request to the P2P server 13 via the network 12.

  For example, in step S <b> 102, when the RSS reader 151 is activated when the execution file icon of the RSS reader 151 is double-clicked by the operation of the user A, the login module 171 controls the communication unit 109 and performs the network 12. As a login request to the communication unit 109, the peer ID of the user A who is “aaa@aaa.ne.jp” and the IP address of the client terminal device 11-i which is “172.31.2.3” are addressed to the P2P server 13. To send to.

  As described above, the timing for transmitting the login request to the P2P server 13 is not limited to when the RSS reader 151 is activated by the user A's operation by double-clicking the icon of the executable file of the RSS reader 151. For example, when a login button (not shown) provided in the RSS reader 151 is pressed by the operation of the user A or when the RSS reader 151 is activated, a login dialog (not shown) is displayed. Thus, it may be transmitted at the timing when the use of the service of the P2P system 1 is started, for example, when login is selected by the user's operation.

  In step S121, the registration / deletion reception module 361 of the P2P server 13 controls the communication unit 309 to cause the communication unit 309 to receive the login request transmitted from the client terminal device 11-i via the network 12.

  For example, in step S121, the registration deletion reception module 361 controls the communication unit 309 to transmit “aaa@aaa.ne.jp” transmitted as a login request from the client terminal device 11-i via the network 12. The communication unit 309 receives the peer ID of the user A that is and the IP address of the client terminal device 11-i that is “172.31.2.3”.

  In step S122, the registration deletion accepting module 361 of the P2P server 13 associates the peer ID with the IP address as the login request received from the client terminal device 11-i, and records the peer list 362 recorded in the recording unit 308. (Peer ID and IP address correspondence table) For example, in step S122, the registration deletion accepting module 361 uses the peer ID of the user A “aaa@aaa.ne.jp” and “172.31.2.3” as the login request received from the client terminal device 11-i. The IP address of the client terminal apparatus 11-i is associated with the client terminal apparatus 11-i and stored in the peer list 362 recorded in the recording unit 308.

  In step S123, the registration deletion acceptance module 361 of the P2P server 13 controls the communication unit 309 to notify the communication unit 309 that the user A has logged in normally via the network (peer ID and IP address). Is sent to the client terminal device 11-i.

  In step S103, the login module 171 of the client terminal apparatus 11-i controls the communication unit 109 to cause the communication unit 109 to receive a login notification from the P2P server 13 via the network, and the process ends.

  For example, in step S103, the login module 171 controls the communication unit 109 to cause the communication unit 109 to receive a login notification from the P2P server 13 via the network 12. Based on the received login notification, the RSS reader 151 The name of the peer is displayed in a tree view format in the first pane 401 of the screen displayed on the GUI 173, or the article list in ranking order is displayed in the second pane 402.

  Next, with reference to FIGS. 18 to 22, processing when the client terminal device 11 requests other client terminal devices 11 to provide weighted article metadata (recipe entry list registration) will be described.

  As described above, in order to maintain the relationship with the peer, the client terminal device 11 of the P2P system 1 records the peer channel list 211, which is a list of senders recorded by the receiver side, and the sender side records it. A recipe entry list 212 that is a list of recipients that are present is recorded in the recording unit 108. Based on these two lists, the client terminal apparatus 11 transmits weighted article metadata to the client terminal apparatus 11 of another user or receives weighted article metadata from the client terminal apparatus 11 of another user.

  Also, the client terminal device 11 holds information in which peer IDs and IP addresses are associated with each other in the peer cache 213 and information on the other party is held in the peer cache 213. Information (for example, recipe entry list registration request or weighted article metadata) is transmitted to the other party based on the information that associates the other party's peer ID with the IP address.

  On the other hand, if the other party's information is not held in the peer cache 213, the peer's IP address is obtained and obtained by sending an inquiry to the P2P server 13 by sending the other party's peer ID. Based on the IP address, information (for example, recipe entry registration request or weighted article metadata) is transmitted to the other party.

  In the example shown in FIGS. 18 to 22, the client terminal device 11 that has already logged in to the P2P system 1 will be described as a client terminal device 11-i, a client terminal device 11-j, and a client terminal device 11-k.

  Similarly to the examples shown in FIGS. 16 and 17, the user using the client terminal device 11-i is referred to as user A, and the user using the client terminal device 11-j is referred to as user B. The user using the client terminal device 11-k is referred to as user C, and the user A using the client terminal device 11-i is given a peer ID “aaa@aaa.ne.jp” and “ The user B who is assigned the IP address “172.31.2.3” and uses the client terminal device 11-j has the peer ID “bbb@bbb.ne.jp” and the IP “192.168.1.10”. The user C who is assigned an address and uses the client terminal device 11-k is assigned a peer ID “ccc@ccc.ne.jp” and an IP address “192.168.2.7”.

  Further, the peer channel list 211 recorded by the recording unit 108 of the client terminal device 11-i is referred to as a peer channel list 211-i, and the recipe entry list 212 recorded by the recording unit 108 of the client terminal device 11-i. Is called the recipe entry list 212-i, and the peer cache 213 recorded by the recording unit 108 of the client terminal device 11-i is called the peer cache 213-i. The peer channel list 211 recorded by the recording unit 108 of the client terminal device 11-j is referred to as a peer channel list 211-j, and the recipe entry list 212 recorded by the recording unit 108 of the client terminal device 11-j. Is referred to as a recipe entry list 212-j, and the peer cache 213 recorded by the recording unit 108 of the client terminal device 11-j is referred to as a peer cache 213-j.

  First, with reference to FIG. 18, an outline of processing when the client terminal device 11 requests other client terminal devices 11 to provide weighted article metadata (recipe entry list registration) will be described. That is, FIG. 18 is a diagram illustrating an example of processing in which the user A using the client terminal device 11-i requests the user B using the client terminal device 11-j to provide weighted article metadata. is there.

  For example, when the user A performs an operation for receiving provision of weighted article metadata from the user B, the client terminal apparatus 11-i transmits a recipe entry registration request to the client terminal apparatus 11-j. At this time, since the peer cache 213-i recorded in its own recording unit 108 does not store the information of the peer ID of the user B and the IP address of the client terminal device 11-j, Then, a name resolution request for acquiring the IP address of the client terminal device 11-j is transmitted to the P2P server 13.

  Specifically, the client terminal apparatus 11-i transmits “bbb@bbb.ne.jp” stored in the peer channel list 211-i recorded in its own recording unit 108 via the network 12. A name resolution request including the peer ID of a certain user B is transmitted to the P2P server 13.

  The P2P server 13 records the peer list 362 in the recording unit 308, and the peer list 362 stores the peer ID and IP address of the user who has logged into the P2P system 1 in correspondence with each other.

  For example, in the peer list 362 recorded by the P2P server 13, since user B, user C, and user A are logged in to the P2P system 1, user B who is “bbb@bbb.ne.jp” The IP address “192.168.1.10” is stored for the peer ID, and the IP address “192.168.2.7” is stored for the peer ID of the user C “ccc@ccc.ne.jp”. Then, the IP address “172.31.2.3” is stored for the peer ID of the user A “aaa@aaa.ne.jp”.

  Here, the P2P server 13 receives the name resolution request transmitted from the client terminal device 11-i via the network 12. The P2P server 13 uses the peer list recorded in the recording unit 108 based on the peer ID of the user B “bbb@bbb.ne.jp” included in the name resolution request received from the client terminal device 11-i. The IP address “192.168.1.10” for the peer ID “bbb@bbb.ne.jp” stored in 362 is acquired, and the acquired IP “192.168.1.10” is obtained via the network 12. The address is transmitted to the client terminal device 11-i. That is, the P2P server 13 provides the IP address of the client terminal device 11-j in response to an inquiry from the client terminal device 11-i.

  The client terminal device 11-i receives the IP address of the client terminal device 11-j from the P2P server 13 via the network 12. The client terminal apparatus 11-i stores the received IP address of the client terminal apparatus 11-j in the peer cache 213-i recorded in the recording unit 108 in association with the peer ID of the user B (FIG. 18). The IP address of the client terminal device 11-j “192.168.1.10” is added to the peer ID of the user B “bbb@bbb.ne.jp” surrounded by the dotted line 511).

  The client terminal apparatus 11-i receives at least the recipe entry registration request (the peer ID of the user A who is “aaa@aaa.ne.jp” and his own IP address which is “172.31.2.3” via the network 12. Is transmitted to the IP address of the client terminal device 11-j corresponding to “192.168.1.10” corresponding to the peer ID of the user B stored in the peer cache 213-i recorded in the recording unit 108. .

  The client terminal apparatus 11-j receives the recipe entry registration request transmitted from the client terminal apparatus 11-i via the network 12. Based on the received recipe entry registration request, the GUI 173 of the client terminal device 11-j displays, for example, a dialog for allowing the user B to determine whether to provide the user A with weighted article metadata. As a result, the user B selects whether to provide the weighted article metadata to the user A by selecting a dialog on the screen displayed on the GUI 173.

  When the user B is instructed to provide the user A with the weighted article metadata, the client terminal device 11-j receives the peer ID of the user A that is “aaa@aaa.ne.jp” included in the recipe entry registration request. Is stored in the recipe entry list 212-j recorded in the recording unit 108 (the peer ID of the user A “aaa@aaa.ne.jp” surrounded by the dotted line 512 in FIG. 18 is added). The peer ID of the user A “aaa@aaa.ne.jp” included in the recipe entry registration request and the IP address of the client terminal device 11-i “172.31.2.3” corresponding thereto are associated with each other. And stored in the peer cache 213-j recorded in the recording unit 108 (the peer ID of the user A “aaa@aaa.ne.jp” surrounded by a dotted line 513 in FIG. 18 and “172.31” corresponding thereto. Client terminal device 11 that is “.2.3” -I IP address is added).

  Then, the client terminal apparatus 11-j transmits a response message “permitted” indicating that the weighted article metadata is provided to the user A to the client terminal apparatus 11-i via the network 12.

  On the other hand, when the user B is instructed not to provide the user A with the weighted article metadata, the client terminal apparatus 11-j is the user A who is “aaa@aaa.ne.jp” included in the recipe entry registration request. Is associated with the IP address of the client terminal device 11-i corresponding to “172.31.2.3” and stored in the peer cache 213-j recorded in the recording unit 108 (dotted line in FIG. 18). The peer ID of the user A who is “aaa@aaa.ne.jp” surrounded by 513 and the IP address of the client terminal device 11-i which is “172.31.2.3” are added). In this case, the peer ID of the user A who is “aaa@aaa.ne.jp” surrounded by the dotted line 512 in FIG. 18 is not stored in the recipe entry list 212-j.

  Then, the client terminal apparatus 11-j transmits a response message “rejection” indicating that the weighted article metadata is not provided to the user A to the client terminal apparatus 11-i via the network 12.

  The client terminal device 11-i receives the response message “permitted” or “denied” transmitted from the client terminal device 11-j via the network 12. The client terminal device 11-i displays a predetermined message on the screen displayed by the GUI 173 based on the response message “permitted” or “rejected” transmitted from the client terminal device 11-j. As a result, the user A can know whether or not the provision of weighted article metadata from the user B is permitted.

  Further, at this time, the client terminal 11-i makes an arrow in the first pane 401 of the screen displayed by the GUI 173 based on the response message “permitted” or “rejected” transmitted from the client terminal device 11-j. Change the icon.

  For example, in the first pane 401 when the peer tab 422 in FIG. 9 is selected, a response message “permitted” is received from “user B”, that is, the client terminal device 11-j used by the user B. In this case, in addition to the white arrow icon facing “User B” displayed in the first pane 401, a white arrow icon facing the opposite side to “User B” is also displayed. The That is, the state of the arrow icon shown in the fourth column from the left in FIG.

  On the other hand, in the first pane 401 when the peer tab 422 of FIG. 9 is selected, a response message “reject” from “user B”, that is, the client terminal device 11-j used by the user B. In addition to the white arrow icon facing “User B” displayed in the first pane 401, the black arrow icon facing the opposite side of “User B” is also added. Is displayed. That is, the state of the arrow icon shown in the fourth column from the left in FIG.

  Next, processing for providing weighted article metadata will be described with reference to the flowchart of FIG. That is, in the flowchart of FIG. 19, the user A who uses the client terminal device 11-i requests the user B who uses the client terminal device 11-j to provide weighted article metadata. It can be said that it is a process.

  In step S161, for example, the first pane peer list management unit 192 identifies a peer that is selected by the operation of the user A and wants to receive provision of weighted article metadata, and receives provision of the specified weighted article metadata. The peer list management unit 201 is supplied with a peer registration request for the specified peer.

  For example, in step S161, the first pane peer list management unit 192 requests the user B to provide weighted article metadata by the user A pressing the peer registration icon on the toolbar 404 displayed on the screen displayed by the GUI 173. When the operation is performed, the user B is specified as a peer for which weighted article metadata is to be provided, and a peer registration request for the specified user B is supplied to the peer list management unit 201.

  In step S162, the peer list management unit 201 of the client terminal device 11-i, based on the peer registration request supplied from the first pane peer list management unit 192, the peer ID of the partner who wants to receive weighted article metadata. Are stored in the peer channel list 211. The peer list management unit 201 supplies the communication module 176 with a name resolution request that is a request for acquiring the IP address of the client terminal device 11 of the other party that is desired to receive weighted article metadata.

  For example, in step S162, the peer list management unit 201 of the client terminal apparatus 11-i is provided with weighted article metadata based on the user B peer registration request supplied from the first pane peer list management unit 192. The name for storing the peer ID “bbb@bbb.ne.jp” in the peer channel list 211-i and acquiring the IP address of the client terminal device 11-j as the peer ID of the user B who is the other party A solution request (for example, including a peer ID “bbb@bbb.ne.jp”) is supplied to the communication module 176.

  In step S163, the communication module 176 of the client terminal device 11-i controls the communication unit 109 to send the name resolution request supplied from the peer list management unit 201 to the communication unit 109 via the network 12. 13 is sent to.

  For example, in step S163, the communication module 176 controls the communication unit 109, and the client terminal supplied to the communication unit 109 from the peer list management unit 201 via the network 12 (used by the user B). A name resolution request (for example, information including at least a peer ID “bbb@bbb.ne.jp”) for acquiring the IP address of the device 11-j is transmitted to the P2P server 13.

  In step S151, the name resolution module 363 of the P2P server 13 controls the communication unit 309 to cause the communication unit 309 to receive the name resolution request transmitted from the client terminal device 11-i via the network 12.

  For example, in step S151, the name resolution module 363 controls the communication unit 309 to transmit the client terminal device 11- (used by the user B) transmitted from the client terminal device 11-i via the network 12. The communication unit 309 receives a name resolution request (for example, including a peer ID “bbb@bbb.ne.jp”) for acquiring the IP address of j.

  In step S152, the name resolution module 363 of the P2P server 13 acquires the IP address stored corresponding to the peer ID from the peer list 362 recorded in the recording unit 308 based on the received name resolution request. To do.

  For example, in step S152, the name resolution module 363 obtains the IP address of the received client terminal device 11-j (for example, includes a peer ID “bbb@bbb.ne.jp”). From the peer list 362 recorded in the recording unit 308, the IP address of the client terminal apparatus 11-j is “192.168.1.10” corresponding to the peer ID “bbb@bbb.ne.jp”. Get an IP address.

  In step S153, the name resolution module 363 of the P2P server 13 controls the communication unit 309, and sends the IP address acquired from the peer list 362 to the client terminal device 11-i via the network 12 to the communication unit 309. Send it. For example, in step S 153, the name resolution module 363 controls the communication unit 309 to acquire “192.168” as the IP address of the client terminal apparatus 11-j from the peer list 362 via the network 12 to the communication unit 309. The IP address “1.10” is transmitted to the client terminal apparatus 11-i.

  In step S164, the communication module 176 of the client terminal apparatus 11-i controls the communication unit 109 so that the communication unit 109 receives the IP address transmitted from the P2P server 13 via the network 12. The communication module 176 of the client terminal device 11-i controls the communication unit 109 to cause the communication unit 109 to supply the received IP address to the peer list management unit 201.

  For example, in step S164, the communication module 176 of the client terminal apparatus 11-i controls the communication unit 109 to transmit the client terminal apparatus 11 that is “192.168.1.10” transmitted from the P2P server 13 via the network 12. The IP address of −j is received by the communication unit 109, and the IP address of the client terminal device 11 -j that is “192.168.1.10” is supplied to the peer list management unit 201.

  In step S165, the peer list management unit 201 of the client terminal apparatus 11-i associates the peer ID and IP address of the other party to which weighted article metadata is to be provided based on the IP address supplied from the communication unit 109. In addition, the data is stored in the peer cache 213 recorded in the recording unit 108. The peer list management unit 201 supplies the communication module 176 with a recipe entry registration request that is a request for permission to a partner who wants to receive weighted article metadata.

  Here, the recipe entry list registration request includes the peer ID of the client and the IP address of the client terminal device 11 being used, and the IP address of the client terminal device 11 used by the other party who wants to receive weighted article metadata. At least.

  For example, in step S165, the peer list management unit 201 of the client terminal device 11-i uses the weighted article meta data based on the IP address of the client terminal device 11-j that is “192.168.1.10” supplied from the communication unit 109. The peer ID “bbb@bbb.ne.jp” of the user B who is the recipient of the data provision and the IP address of the client terminal device 11-j “192.168.1.10” (used by the user B) Are stored in the peer cache 213 recorded in the recording unit 108.

  Further, the peer list management unit 201 of the client terminal device 11-i uses the peer ID of the user A who is “aaa@aaa.ne.jp” and the client terminal device which is used by the user A who is “172.31.2.3”. A recipe entry registration request including the IP address of 11-i and the IP address of the client terminal device 11-j used by the user B who is “192.168.1.10” is supplied to the communication module 176.

  In step S166, the communication module 176 of the client terminal apparatus 11-i controls the communication unit 109 to send a recipe entry list registration request supplied from the peer list management unit 201 to the communication unit 109 via the network 12. The client terminal device 11 of the other party who wants to receive weighted article metadata is transmitted.

  For example, in step S166, the communication module 176 of the client terminal apparatus 11-i controls the communication unit 109, and sends the recipe entry list registration request supplied from the peer list management unit 201 to the communication unit 109 via the network. (Including the peer ID of user A “aaa@aaa.ne.jp” and the IP address of the client terminal device 11-i used by user A “172.31.2.3”) It is transmitted to the IP address of the client terminal device 11-j used by the user B who is “192.168.1.10” included in the request.

  In step S171, the communication module 176 of the client terminal device 11-j controls the communication unit 109 to send the recipe entry registration request transmitted from the client terminal device 11-i via the network 12 to the communication unit 109. To receive. The communication module 176 of the client terminal device 11-j controls the communication unit 309 to cause the communication unit 309 to supply the received recipe entry list registration request to the display control unit 202.

  For example, in step S171, the communication module 176 of the client terminal device 11-j controls the communication unit 109 to transmit “aaa@aaa.ne.jp” transmitted from the client terminal device 11-i via the network. The recipe entry list registration request including the peer ID of the user A that is “IP” and the IP address of the client terminal device 11-i that is used by the user A that is “172.31.2.3” is received by the communication unit 109. A recipe entry registration request including the peer ID of the user A “aaa@aaa.ne.jp” and the IP address of the client terminal device 11-i used by the user A “172.31.2.3” The data is supplied to the display control unit 202.

  In step S172, the display control unit 202 of the client terminal apparatus 11-j controls the recipe entry list based on the recipe entry registration request supplied from the communication unit 109 under the control of the communication module 176 of the client terminal apparatus 11-j. A dialog box for instructing the user who has transmitted the registration request whether to provide weighted article metadata is displayed on the screen displayed by the GUI 173.

  For example, in step S172, the display control unit 202 of the client terminal device 11-j uses “aaa@aaa.ne.jp” supplied from the communication unit 109 under the control of the communication module 176 of the client terminal device 11-j. Weighting is given to user A based on a recipe entry registration request that includes the peer ID of a user A and the IP address of the client terminal device 11-i used by user A who is "172.31.2.3" A dialog box for instructing whether or not to provide article metadata is displayed on the screen displayed on the GUI 173.

  FIG. 20 is a diagram illustrating an example of a screen displayed by the GUI 173 of the RSS reader 151 of the client terminal device 11-j that displays a dialog box for determining whether to provide weighted article metadata.

  In the example shown in FIG. 20, a dialog box 521 for instructing whether to provide weighted article metadata is displayed on the GUI 173 of the RSS reader 151.

  In the dialog box 521, a message “A request for permission of weighted article metadata has been received from user A. Do you want to provide weighted article metadata to user A?” Is displayed, and yes A button 522 and a no button 523 are displayed.

  That is, the user B who uses the client terminal apparatus 11-j instructs to provide the weighted article metadata to the client terminal apparatus 11-i used by the user A by pressing the Yes button 522 of the dialog box 521. In response to this, pressing the No button 523 of the dialog box 521 instructs the client terminal apparatus 11-i used by the user A not to provide the weighted article metadata.

  Returning to FIG. 19, in step S173, the peer determination unit 203 of the client terminal device 11-j provides weighted article metadata to the partner who has transmitted the recipe entry list registration request by the user's operation. Determine whether.

  For example, in step S173, the peer determination unit 203 of the client terminal device 11-j determines whether the user A has pressed the Yes button 522 of the dialog box 521 or the No button 523 by the operation of the user B. On the other hand, it is determined whether to provide weighted article metadata.

  If it is determined in step S173 that weighted article metadata is provided to the user who has transmitted the recipe entry registration request by the user's operation, the process proceeds to step S174, and the peer determination unit of the client terminal device 11-j 203 supplies the peer list management unit 201 with a response message indicating “permitted” indicating that weighted article metadata is provided to the user who has transmitted the recipe entry registration request. Based on the response message “permitted” supplied from the peer determination unit 203, the peer list management unit 201 stores the recipe ID recorded in the recording unit 108 with the peer ID of the user who has transmitted the recipe entry registration request. Stored in the entry list 212.

  Here, as described above, the response message is information indicating whether or not weighted article metadata is provided to the user who has transmitted the recipe entry registration request. For example, in the process of step S173, The peer determination unit 203 supplies a response message “permitted” to the peer list management unit 201 when the Yes button 522 of the dialog box 521 in FIG. On the other hand, when the No button 523 of the dialog box 521 in FIG. 20 is pressed by the operation of the user B, the peer determination unit 203 supplies a response message “Reject” to the peer list management unit 201.

  For example, in step S173, when the Yes button 522 of the dialog box 521 in FIG. 20 is pressed by the operation of the user B, the peer determination unit 203 of the client terminal device 11-j sends a response message “permitted” to the peer. The peer list management unit 201 supplies “aaa @ aaa” of the user A who has transmitted the recipe entry registration request based on the response message “permitted” supplied from the peer determination unit 203. .ne.jp ”is stored in the recipe entry list 212-j recorded in the recording unit.

  On the other hand, if it is determined in step S173 that weighted article metadata is not provided to the user who has transmitted the recipe entry registration request by the user's operation, the peer determination unit 203 issues the recipe entry registration request. A response message of “rejection” indicating that the weighted article metadata is not provided is supplied to the peer list management unit 201 for the user who has transmitted the message. In this case, since it is not necessary to store the peer ID of the user who has transmitted the recipe entry registration request in the recipe entry list 212, the process of step S174 is skipped.

  In step S175, the peer list management unit 201 of the client terminal apparatus 11-j obtains the peer ID and IP address of the user who has transmitted the recipe entry registration request based on the response message supplied from the peer determination unit 203. The data is stored in the peer cache 213 correspondingly. The peer list management unit 201 of the client terminal apparatus 11-j supplies the communication module 176 with a response message indicating either “permitted” or “denied” supplied from the peer determination unit 203.

  That is, the peer list management unit 201 determines whether the response message supplied from the peer determination unit 203 is “permitted” or “rejected”, and the peer ID and IP address of the user who has transmitted the recipe entry registration request Are stored in the peer cache 213 in association with each other.

  For example, in step S175, the peer list management unit 201 of the client terminal apparatus 11-j transmits the peer ID “aaa@aaa.ne.jp” of the user A who has transmitted the recipe entry registration request, and the user A's The IP address “172.31.2.3” of the client terminal device 11-i being used is stored in the peer cache 213 in association with the IP address.

  Then, the peer list management unit 201 of the client terminal device 11-j responds “permitted” when the Yes button 522 of the dialog box 521 in FIG. 20 is pressed by the operation of the user B in the process of step S173. The message is supplied to the communication module 176. On the other hand, if the No button 523 of the dialog box 521 in FIG.

  In step S176, the communication module 176 of the client terminal device 11-j controls the communication unit 109 to “permit” or “reject” supplied from the peer list management unit 201 to the communication unit 109 via the network 12. Is sent to the client terminal device 11-i.

  For example, in step S176, the communication module 176 of the client terminal device 11-j determines that the peer list management unit when the yes button 522 of the dialog box 521 in FIG. Since the response message “permitted” is supplied from 201, the communication unit 109 is controlled to send the response message “permitted” to the client terminal device 11-i via the network 12 to the communication unit 109. Send it. On the other hand, if the communication module 176 of the client terminal device 11-j presses the No button 523 of the dialog box 521 in FIG. Since the response message “reject” is supplied, the communication unit 109 is controlled to cause the communication unit 109 to transmit the response message “reject” to the client terminal device 11-i via the network 12. .

  In step S167, the communication module 176 of the client terminal device 11-i controls the communication unit 109 to be either “permitted” or “rejected” from the client terminal device 11-j via the network 12. The communication unit 109 receives the response message. The communication module 176 of the client terminal device 11-i controls the communication unit 109 to cause the communication unit 109 to supply the received response message to the display control unit 202 via the network 12.

  For example, in step S167, when the communication module 176 of the client terminal device 11-i presses the yes button 522 of the dialog box 521 in FIG. By controlling, the communication unit 109 receives the response message “permitted” from the client terminal device 11-j via the network 12, and supplies the received response message “permitted” to the display control unit 202. . On the other hand, in step S167, the communication module 176 of the client terminal device 11-j, in the process of step S173, if the user B has pressed the No button 523 of the dialog box 521 in FIG. 109, the communication unit 109 receives the response message “reject” from the client terminal device 11-j via the network 12, and the received response message “reject” is displayed to the display control unit 202. Supply

  In step S168, the display control unit 202 of the client terminal device 11-i sends a predetermined message to the GUI 173 based on the response message that is either “permitted” or “denied” transmitted from the client terminal device 11-j. Is displayed on the screen displayed by, and the process ends.

  For example, in step S168, the display control unit 202 of the client terminal device 11-i notifies the user A based on the response message that is either “permitted” or “denied” transmitted from the client terminal device 11-j. On the other hand, either a message indicating that the provision of the weighted article metadata is permitted from the user B or a message indicating that the provision of the weighted article metadata is rejected from the user B is displayed on the screen displayed by the GUI 173. .

  FIG. 21 is a diagram illustrating an example of a screen displayed by the GUI 173 of the RSS reader 151 of the client terminal device 11-i including a dialog box indicating permission to provide weighted article metadata.

  In the example shown in FIG. 21, a dialog box 531 indicating permission to provide weighted article metadata is displayed on the screen displayed by the GUI 173 of the RSS reader 151.

  In the dialog box 531, a message “User B has been allowed to provide weighted article metadata” is displayed, and an OK button 532 is further displayed.

  That is, when the user B using the client terminal device 11-j presses the yes button 522 of the dialog box 521 in FIG. 20 in the process of step S173, the user B provides the weighted article metadata to the user A. When the client terminal apparatus 11-i receives the response message “permitted” and displays the message on the GUI 173 based on the response message “permitted”, the user A It can be known that user B has permitted the provision of weighted article metadata.

  On the other hand, FIG. 22 is a diagram illustrating an example of a screen displayed by the GUI 173 of the RSS reader 151 of the client terminal device 11-i including a dialog box indicating rejection of provision of weighted article metadata.

  In the example shown in FIG. 22, a dialog box 535 indicating rejection of provision of weighted article metadata is displayed on the screen displayed by the GUI 173 of the RSS reader 151.

  In the dialog box 535, a message “User B has refused to provide weighted article metadata” is displayed, and an OK button 536 is further displayed.

  That is, when the user B using the client terminal device 11-j presses the No button 523 of the dialog box 521 in FIG. 20 in the process of step S173, the user B provides the weighted article metadata to the user A. The client terminal device 11-i receives the response message “rejected” and displays the message on the GUI 173 based on the response message “rejected”. It can be known that the user B refuses to provide weighted article metadata.

  Further, for example, in step S168, in step S168, the display control unit 202 of the client terminal apparatus 11-i sends a response message that is either “permitted” or “denied” transmitted from the client terminal apparatus 11-j. Based on this, peer list display information is generated. The display control unit 202 is displayed at the head of the name of the peer displayed in the first pane 401 (when the peer tab 422 is selected) displayed by the GUI 173 of the RSS reader 151 based on the generated peer list display information. Display (change) the arrow icon.

Specifically, when a response message “permitted” is transmitted from the client terminal device 11-j, the display control unit 202 of the client terminal device 11-i controls the output unit 107 via the GUI 173. In the first pane 401 of FIG. 9 (when the peer tab 422 is selected), a white arrow icon facing the side opposite to “user B” is displayed. That is, in the first pane 401 of FIG. 9, the arrow icon displayed at the top of the name “user B” is changed to the above-described arrow icon of 4 rows and 4 columns of FIG.

  On the other hand, when a response message “reject” is transmitted from the client terminal apparatus 11-j, the peer list management module 174 of the client terminal apparatus 11-i controls the output unit 107 via the GUI 173. In the first pane 401 of FIG. 9 (when the peer tab 422 is selected), a black arrow icon facing the side opposite to “user B” is displayed. That is, in the first pane 401 of FIG. 9, the arrow icon displayed at the beginning of the name “user B” is changed to the above-described arrow icon of 5 rows and 4 columns of FIG.

  As described above, processing for requesting provision of weighted article metadata is performed.

  Next, with reference to FIG. 23 and FIG. 24, processing in which the client terminal device 11 provides weighted article metadata to other client terminal devices 11 will be described.

  In the example shown in FIGS. 23 and 24, the client terminal device 11 that has already logged in to the P2P system 1 will be described as a client terminal device 11-i, a client terminal device 11-j, and a client terminal device 11-k.

  Similarly to the examples shown in FIGS. 16 and 17, and FIGS. 18 to 22, the user who uses the client terminal device 11-i is referred to as user A, and the client terminal device 11-j is used. The user who is using the client terminal device 11-k is called user C, and the user A who is using the client terminal device 11-i is called “aaa@aaa.ne.jp”. The user B who is assigned the peer ID “172.31.2.3” and uses the client terminal apparatus 11-j is assigned the peer ID “bbb@bbb.ne.jp” and “ The user C who is assigned the IP address “192.168.1.10” and uses the client terminal device 11-k has the peer ID “ccc@ccc.ne.jp” and the IP “192.168.2.7”. An address is assigned.

  Further, the peer channel list 211 recorded by the recording unit 108 of the client terminal apparatus 11-j is referred to as a peer channel list 211-j, and the recipe entry list 212 recorded by the recording unit 108 of the client terminal apparatus 11-j. Is referred to as a recipe entry list 212-j, and the peer cache 213 recorded by the recording unit 108 of the client terminal device 11-j is referred to as a peer cache 213-j.

  23 and 24, the process of providing (transmitting) weighted article metadata will be described, and the details of the process of generating weighted article metadata will be described with reference to FIGS. 25 to 33 described later. . Accordingly, in FIGS. 23 and 24, the processing after the client terminal device 11-j generates weighted article metadata provided to the client terminal device 11-i, that is, the client terminal device 11-j A process of providing (transmitting) the weighted article metadata generated to the client terminal device 11-i will be described.

  First, with reference to FIG. 23, an outline of processing in which the client terminal device 11-j provides weighted article metadata to the client terminal device 11-i will be described.

  The client terminal apparatus 11-j sends the weighted article metadata provision destination (“aaa@aaa.ne.jp stored in the recipe entry list 212-j” from the peer cache 213-j recorded in the recording unit 108. The IP address of the client terminal device 11-i used by the user A, which is “172.31.2.3”, is acquired as the IP address of the “user A peer ID”. The client terminal apparatus 11-j uses the weighted article metadata generated by the client terminal apparatus 11-j via the network 12 to be used by the user A who is “172.31.2.3” acquired from the peer cache 213-j. Send to the IP address of.

  If the IP address of the provision destination of the weighted article metadata is not stored in the peer cache 213-j, the peer ID of the provision destination of the weighted article metadata is transmitted to the P2P server 13 as described above, and the weighting is performed. By inquiring about the IP address of the article metadata providing destination, the IP address is acquired from the P2P server 13, and then the weighted article metadata is transmitted to the acquired IP address.

  The client terminal apparatus 11-i receives the weighted article metadata transmitted from the client terminal apparatus 11-j, and records the received weighted article metadata in the recording unit 108. The client terminal device 11-i displays the article list on the second pane 402 of the screen displayed by the GUI 173 based on the weighted article metadata recorded in the recording unit 108. Further, the client terminal apparatus 11-i sends a confirmation packet (for example, ACK (ACKnowledgement)), which is a notification indicating that the weighted article metadata has been received, to the client terminal apparatus 11-j. Send.

  The client terminal device 11-j receives the confirmation packet (for example, ACK) transmitted from the client terminal device 11-i.

  Next, a process in which the client terminal device 11-j provides weighted article metadata to the client terminal device 11-i will be described with reference to the flowchart in FIG.

  In step S211, the peer list management unit 201 of the client terminal apparatus 11-j stores the weighted article metadata provision destination (recipe entry list 212) from the peer cache 213-j recorded in the recording unit 108. Get the IP address of the peer ID. The peer list management module 174 of the client terminal apparatus 11-j supplies the communication module 176 with the acquired IP address of the provided weighted article metadata as destination information.

  For example, in step S211, the peer list management unit 201 of the client terminal apparatus 11-j provides the weighted article metadata destination from the peer cache 213-j recorded in the recording unit 108 when a predetermined time has elapsed. The client terminal device 11 used by the user A who is “172.31.2.3” as the IP address of (the peer ID of the user A who is “aaa@aaa.ne.jp” stored in the recipe entry list 212-j) The IP address of -i is acquired, and the acquired IP address “172.31.2.3” is supplied to the communication module 176 as destination information.

  In step S212, the communication module 176 of the client terminal device 11-j controls the communication unit 109, and the weighted article metadata generated and supplied to the communication unit 109 via the network 12 by the metadata generation unit 243. Is transmitted to the destination information supplied from the peer list management unit 201.

  For example, in step S212, the communication module 176 of the client terminal device 11-j controls the communication unit 109, and the weighted article generated and supplied to the communication unit 109 via the network 12 by the metadata generation unit 243. The metadata is transmitted to the IP address of the client terminal device 11-i used by the user A who is “172.31.2.3” supplied from the peer list management unit 201.

  If the IP address of the provision destination of the weighted article metadata is not stored in the peer cache 213-j, the peer ID of the provision destination of the weighted article metadata is transmitted to the P2P server 13 as described above, and the weighting is performed. By inquiring about the IP address of the article metadata providing destination, the IP address may be acquired from the P2P server 13, and then the weighted article metadata may be transmitted to the acquired IP address.

  In step S201, the communication module 176 of the client terminal device 11-i controls the communication unit 109 to receive the weighted article metadata transmitted from the client terminal device 11-j via the network 12 to the communication unit 109. Let

  In step S202, the communication module 176 of the client terminal device 11-i causes the recording unit 108 to record the weighted article metadata received from the client terminal device 11-j.

  For example, the display control unit 232 of the client terminal device 11-i displays the weighted article metadata recorded in the recording unit 108 as an article list (for example, a list of titles included in the weighted article metadata) by the GUI 173. Displayed on the second pane 402 of the screen.

  In step S <b> 203, the communication module 176 of the client terminal device 11-i controls the communication unit 109 to receive the weighted article metadata to the communication unit 109 via the network 12 to the provision destination of the weighted article metadata. A confirmation packet, which is a notification indicating this, is transmitted to the client terminal apparatus 11-j. For example, the communication module 176 of the client terminal apparatus 11-i controls the communication unit 109 and transmits a confirmation packet “ACK” to the communication unit 109 via the network 12 to the client terminal apparatus 11-j. Let

  In step S213, the communication module of the client terminal device 11-j controls the communication unit 109 so that the communication unit 109 receives the confirmation packet transmitted from the client terminal device 11-i via the network 12. The process ends. For example, in step S213, the communication module of the client terminal apparatus 11-j controls the communication unit 109 to communicate the confirmation packet that is “ACK” transmitted from the client terminal apparatus 11-i via the network 12. Unit 109 to receive.

  In this way, the client terminal device 11 provides weighted article metadata to the client terminal device 11 used by the peer that is the peer ID stored in the recipe entry list 212.

  As described above, the client terminal device 11 performs processing for providing weighted article metadata to the other client terminal devices 11.

  Further, as described above, in the present invention, not only the weighted article metadata is received and displayed on the screen (second pane 402) displayed by the GUI 173 of the RSS reader 151, but also the received weighting is received. Based on the article metadata, the article points included in the received weighted article metadata are aggregated, and the articles are displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 in descending order of the aggregated article points. be able to.

  Hereinafter, referring to FIG. 25 to FIG. 35, based on the weighted article metadata received from other users (peers) belonging to the community, the article points included in the received weighted article metadata are aggregated and aggregated. Article points are assigned to articles according to the details of the processing for displaying the articles in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 and the method of browsing the articles by the user 152 in the order of articles with the highest article points. The added article points and the article points included in the received weighted article metadata are aggregated, weighted article metadata is generated based on the aggregated article points, and the generated weighted article metadata is transmitted via the network 12. Explains the details of the processing provided to other users (peers) belonging to the community. To.

  In the example shown in FIG. 25 to FIG. 35, the user A using the client terminal device 11-i, the user B using the client terminal device 11-j, and the client terminal device 11-k are used. Any user C who is logged in to the P2P system 1. Further, it is assumed that the RSS reader 151 is activated in each client terminal device 11 used by each user.

  First, with reference to FIG. 25, the outline | summary of the process of the article display by an article point is demonstrated.

  In the example shown in FIG. 25, user A, user B, and user C are each transmitting and receiving weighted article metadata via the network 12. However, hereinafter, in order to make the explanation easy to understand, here, a case where the user A receives weighted article metadata from the user B and the user C via the network 12 will be described. Furthermore, transmission / reception of data (weighted article metadata) between the client terminal devices 11 is performed by the processing as described above (for example, the example shown in FIGS. 23 and 24), but here the explanation is easy to understand. Therefore, detailed description will be omitted as appropriate.

  Further, the client terminal device 11-j used by the user B receives the weighted article metadata from users other than the user A and the user C via the network 12, and based on the received weighted article metadata. The article is displayed in descending order of the article points, the article points are given to the articles by the method of browsing the article by the user B, and the given article points and the article points included in the received weighted article metadata are displayed. The weighted article metadata including the collected article points is transmitted to the client terminal device 11-i used by the user A via the network 12.

  That is, the weighted article metadata transmitted from the client terminal device 11-j used by the user B to the client terminal device 11-i used by the user A via the network 12 is directly transmitted by the user A. Information from users other than the user who exchanges information (for example, information on articles) is included.

  Further, similarly, the client terminal device 11-k used by the user C receives the weighted article meta data from the user C other than the user A and the user B via the network 12, and the user C receives the weighted article meta data. Articles are displayed in descending order of article points based on the data, article points are assigned to the articles by the method of browsing articles by user C, and the article points included and the articles included in the received weighted article metadata The points are totaled, and the weighted article metadata including the totaled article points is transmitted to the client terminal device 11-i used by the user A via the network 12.

  That is, the weighted article metadata transmitted from the client terminal device 11-k used by the user C to the client terminal device 11-i used by the user A via the network 12 is directly transmitted by the user A. Information from users other than the user who exchanges information (for example, information on articles) is included.

  As described above, the client terminal device 11-i used by the user A is transmitted from the client terminal device 11-j used by the user B via the network 12 (the user A does not directly exchange information). A user who receives weighted article metadata (including information from the user), and also from the client terminal device 11-k used by the user C via the network 12 (the user A does not exchange information directly) Receive weighted article metadata (including information from).

  Here, as described above, an article point is given to an article by an article browsing method by an operation of the user 152, and an example of a definition for giving the article point will be described with reference to FIG.

  FIG. 26 is a diagram illustrating an example of an article point definition table that defines article points to be given to articles by the operation of the user 152.

  In the example shown in FIG. 26, “article points” are arranged in correspondence with “user operations”. In other words, the article point definition table stores article points corresponding to the contents of the operation of the user 152.

  In the example shown in FIG. 26, the article point is “+4” in response to the user operation “double-click the article list displayed in the second pane to display the text in the third pane”. Is stored. Further, an article point “+3” is stored for a user operation “single click on the article list displayed in the second pane to display a summary in the third pane”. Furthermore, an article point “+2” is stored in response to a user operation “click a link in the text of an article whose text is displayed in the third pane to move to another article”. ing. In addition, an article point “+1” is stored for a user operation “scroll an article whose text is displayed in the third pane”.

  That is, for example, by the operation of the user 152, double-clicking the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 activated in the client terminal device 11, the third pane When the text is displayed in 403, “+4 points” is added to the article whose text is displayed in the third pane 403. In addition, when an article whose text is displayed in the third pane 403 is scrolled by the operation of the user 152, “+1 point” is added to the article whose text is displayed in the third pane 403. The Further, when the user 152 moves to another article by single-clicking a link in the body of the article whose text is displayed in the third pane 403 by the operation of the user 152, the text is displayed in the third pane 403. "+2 points" is added to the article that is currently on. Further, for example, by the operation of the user 152, a single click on the list of articles displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 running on the client terminal device 11, and the third When the summary is displayed in the pane 403, “+3 points” is added to the article displayed in the second pane 402.

  These article point definition tables are recorded in the recording unit 108 of the client terminal device 11 used by each user. For example, the article point definition is also included in each recording unit 108 of the client terminal device 11-i used by the user A, the client terminal device 11-j used by the user B, and the client terminal device 11-k used by the user C. The table is recorded.

  The article point corresponding to the user operation in the article point definition table in FIG. 26 is an example, and is not limited to the example described above. For example, for an article that is viewed immediately after receiving weighted article metadata, Define the article points to be added or define the article points to be added to the printed article when the text of the article displayed in the third pane 403 is printed Article points can be defined in response to any user operation.

  Hereinafter, the state of an article for which a user operation defined in the article point definition table in FIG. 26 is executed will be referred to as a subscription state.

  Returning to FIG. 25, the client terminal device 11-i makes the article point given to the article in the subscription state by the operation of the user A (for example, the article point stored in the article point definition table in FIG. 26). The client terminal apparatus 11-j adds the article points (for example, article points stored in the article point definition table in FIG. 26) that are given to the article that has been subscribed by the operation of the user B. The client terminal device 11-k counts article points (for example, article points stored in the article point definition table in FIG. 26) given to the subscribed article by the operation of the user C. To do.

  That is, the client terminal device 11 used by each user counts article points for articles by respective user operations.

  FIG. 27 is a diagram illustrating an example of the article point totaling table of articles totaled by the operation of the user 152. FIG. 27A is a diagram illustrating an example of the article point totaling table of articles totaled by the operation of the user A.

  In the example shown in FIG. 27A, “article points” are arranged in association with “article names”. That is, the article point total table for each article aggregated by the operation of the user A is stored in the article point aggregation table of FIG. 27A.

  For example, the article point “10” is stored for the article name “Olympic Marathon”. Further, an article point “7” is stored for the article name “Today's weather”. Furthermore, an article point “7” is stored for the article name “Earthquake Early Warning”. In addition, an article point “6” is stored for the article name “Olympic swimming”. Furthermore, an article point “5” is stored for the article name “Semiconductor-related news”.

  That is, in the example shown in FIG. 27A, an article (subscription state) viewed by the user A in the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 by the operation of the user A is shown. 26), the article points for each article are tabulated based on the article point definition table of FIG. 26 described above.

  Specifically, for example, when an article point of “10” is stored for an article name of “Olympic Marathon”, an operation of User A is performed on an article of “Olympic Marathon” Single-click the article list that is “Olympic Marathon” displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 to display the summary in the third pane 403 (“+3 points”), Double-click the article list that is “Olympic Marathon”, display the text in the third pane 403 (“+4 points”), and scroll the article that is the “Olympic Marathon” with the text displayed in the third pane 403 ( "+1 point"), "Olympic marathon" with the text displayed in the third pane 403 By clicking on a link in the body of a thing, it is moved to another article ("+2 points"), etc., so that it becomes a point that is "10" (ie, "+3 points" + “+4 points” + “+ 1 points” + “+ 2 points” = “+ 10 points”).

  FIG. 27B is a diagram illustrating an example of the article point totaling table of articles totaled by the operation of the user B.

  In the example shown in FIG. 27B, “article points” are arranged in association with “article names”. That is, the article point total table for each article aggregated by the operation of the user B is stored in the article point aggregation table of FIG. 27B.

  For example, an article point “10” is stored for an article name “Olympic Judo”. Also, an article point “9” is stored for the article name “Today's Stock News”. Further, an article point “8” is stored for the article name “Earthquake Early Warning”. In addition, an article point “8” is stored for an article name “Olympic Marathon”. Further, an article point “4” is stored for the article name “Japanese music hit chart”.

  That is, in the example shown in FIG. 27B, the user B's operation allows the user B to browse the articles (subscription status and the browsing status) among the article lists displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. 26), the article points for each article are tabulated based on the article point definition table of FIG.

  FIG. 27C is a diagram illustrating an example of the article point totaling table totaled by the operation of the user C.

  In the example shown in FIG. 27C, “article points” are arranged in association with “article names”. That is, the article point total table stores the article points for each article that are totaled by the operation of the user C.

  For example, an article point “8” is stored for an article name “Today's weather”. Also, an article point “5” is stored for the article name “Today's Stock News”. Furthermore, the article point “5” is stored for the article name “Earthquake Early Warning”. Also, an article point “3” is stored for the article name “Middle East Situation News”. Furthermore, an article point “1” is stored for the article name “Olympic Marathon”.

  That is, in the example shown in FIG. 27C, the user C's operation allows the user C to view the article (subscription status and browsing status) among the article lists displayed on the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. 26), the article points for each article are tabulated based on the article point definition table of FIG.

  Returning to FIG. 25, the client terminal device 11-i used by the user A is connected to the client terminal device 11-j used by the user B and the client terminal device used by the user C via the network 12. The weighted article metadata is received from 11-k.

  The weighted article metadata received by the client terminal device 11-i used by the user A from the client terminal device 11-j used by the user B via the network 12 is, for example, the user B shown in FIG. It is described in the RSS format so as to include data stored in the article point totaling table (hereinafter referred to as user B's article point totaling table) totaled by the above operation. The weighted article metadata received by the client terminal device 11-i used by the user A from the client terminal device 11-k used by the user C via the network 12 is, for example, as illustrated in FIG. It is described in the RSS format so as to include data stored in an article point totaling table (hereinafter referred to as user C's article point totaling table) of articles totaled by the operation of the user C.

  Further, as described above, the weighted article metadata received from the client terminal device 11-j used by the user B via the network 12 by the client terminal device 11-i used by the user A is: Weighted article metadata information (for example, article information) received by the client terminal device 11-j used by the user B from the community to which the user B belongs (the community to which the user A does not belong) Also included. Further, the weighted article metadata received by the client terminal device 11-i used by the user A from the client terminal device 11-k used by the user C via the network 12 is used by the user C. The client terminal device 11-k includes weighted article metadata information (for example, article information) received from a community to which the user C belongs (a community to which the user A does not belong).

  That is, the data stored in the article point totaling table of the user B is information on the weighted article metadata received from the community to which the user B belongs (community to which the user A does not belong) via the network 12. The data stored in the article point totaling table of the user C (for example, article information) is the community to which the user C belongs (the user A does not belong) via the network 12. Information on weighted article metadata received from the community) (for example, article information).

  As a result, the weighted article metadata transmitted from the client terminal device 11-j used by the user B to the client terminal device 11-i used by the user A via the network 12 includes the user A Information from users other than the community to which they belong (for example, article information) is included. In addition, the user A belongs to the weighted article metadata transmitted from the client terminal device 11-k used by the user C to the client terminal device 11-i used by the user A via the network 12. Information from users other than the community that is doing this (for example, article information) is included.

  The client terminal device 11-i used by the user A uses the article points included in the weighted article metadata transmitted from other users (peers) in the community via the network 12. Perform aggregation.

  For example, the client terminal device 11-i used by the user A is weighted transmitted from the client terminal device 11-j used by the user B via the network 12 as the article point transmitted from the peer. Information related to the article point total table of user B described in the RSS format in the article metadata and weighted article metadata transmitted from the client terminal device 11-k used by the user C are described in the RSS format. Based on the information regarding the article point totaling table of the user C who is, the totaling of article points is executed. That is, the client terminal device 11-i used by the user A executes the aggregation of article points based on the article point aggregation tables of the users B and C.

  FIG. 28 is a diagram illustrating an example of an aggregate ranking information table in which article points are aggregated by the client terminal device 11-i used by the user A.

  In the example shown in FIG. 28A, “article points” are arranged in association with “article names”. In other words, the aggregate ranking information table stores article points for each article that are aggregated by the client terminal device 11-i used by the user A based on the article point aggregation tables of the user B and the user C. Yes.

  For example, an article point “14” is stored for an article name “Today's stock news”. Further, an article point “13” is stored for an article name “Earthquake Early Warning”. Further, an article point “10” is stored for the article name “Olympic Judo”. In addition, an article point “9” is stored for the article name “Olympic Marathon”. Further, an article point “4” is stored for the article name “Japanese music hit chart”. Also, an article point “3” is stored for the article name “Middle East Situation News”.

  Specifically, in the example shown in FIG. 28A, the article point “14” is stored for the article name “Today's stock news”. The article point total table stores an article point “9” for the article name “Today's stock news”, and the article point total table for user C in FIG. The article point “5” is stored for the article name “”. When the article points are aggregated (ie, “9 points” + “5 points” = “14 points”), “14” Article points that are "" are tabulated. In addition, the article points of other articles are also counted in the same way.

  Then, the client terminal device 11-i used by the user A displays the article list in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 based on the aggregated article points.

  FIG. 29 is a diagram illustrating an example of a screen displayed by the GUI 173 of the RSS reader 151 that displays an article list based on the aggregated article points.

  The article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 is displayed in order from the article with the highest article point since the peer tab of the first pane 401 is selected.

  For example, in the example shown in FIG. 29, the second pane 402 includes “Today's Stock News”, “Earthquake Bulletin”, “Olympic Judo”, “Olympic Marathon”, “Japanese Music Hit Chart”, and “Middle East Situation News”. An article is displayed in order from the article with the highest article point (that is, displayed in the order of article points in the aggregate ranking information table of FIG. 28A).

  In the example shown in FIG. 29, when the title of the article “Earthquake Bulletin” in the article list displayed in the second pane 402 is double-clicked by the operation of the user A, At around 3:29, there was an earthquake in Tokyo with a seismic intensity of 3. According to the Japan Meteorological Agency, the epicenter was Tokyo Bay and the depth of the epicenter was about 50 km, and the magnitude of the earthquake is estimated to be 4.6 magnitude. Is displayed in the third pane 403.

  In other words, by adding and collecting article points for each article, the second pane 402 can display the article list in order from articles with the highest article points. As a result, the display order of the articles displayed in the second pane 402 is the ranking of the articles in the community to which the user 152 belongs, and the article displayed at the top of the article list is the user 152. This is the most popular (popular) article in the community to which.

  Thus, when the user A selects information on the Internet, not only the values of the user A but also a person who has a personal exchange with the user A (user B, user C, community to which the user A belongs) The selection of information can be facilitated by adding values of other users.

  Further, the propagation (information relay) of information (articles or contents) from a person (user B, user C, a user other than the community to which the user A belongs) who has human interaction with the user A, the user A Does not realize that he wants, but can get information (articles and content) that he may potentially want.

  Furthermore, as described above, the client terminal device 11-i used by the user A is transmitted from the client terminal device 11-j used by the user B and the client terminal device 11-k used by the user C via the network 12. Based on the received weighted article metadata, the article points included in the received weighted article metadata are totaled, and the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 shows the articles in descending order of the totaled article points. After being displayed on the page, the article point is given to the article by the method of browsing the article by the user A, the added article points and the article points included in the received weighted article metadata are aggregated, and the article points are aggregated Generates weighted article metadata based on the generated weighted article metadata , Via the network 12, provides for other users belonging to the same community as the user A (peer) (transmission).

  That is, the article point corresponding to the operation of the user A is added to the article point of the article in the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. Specifically, this will be described with reference to FIG. 28B.

  In the example shown in FIG. 28B, “article points” are arranged in association with “article names”. That is, in the total ranking information table, article points for each article totaled by the client terminal device 11-i used by the user A are stored.

  For example, an article point “20” is stored for an article name “Earthquake Early Warning”. Also, an article point “19” is stored for the article name “Olympic Marathon”. Further, an article point “15” is stored for the article name “Today's weather”. Further, an article point “14” is stored for the article name “Today's stock news”. Further, an article point “10” is stored for the article name “Olympic Judo”. In addition, an article point “6” is stored for the article name “Olympic swimming”. Furthermore, an article point “5” is stored for the article name “Semiconductor-related news”. Also, an article point “4” is stored for the article name “Japanese music hit chart”. Further, an article point “3” is stored for the article name “Middle East News”.

  Specifically, in the example shown in FIG. 28B, the article point “20” is stored for the article name “Earthquake Early Warning”, which is the article point of user B in FIG. 27B. In the tabulation table, an article point “8” is stored for an article name “Earthquake Early Warning”, and an article name “Earthquake Early Warning” is stored in the article point tabulation table of the user C in FIG. 27C. On the other hand, the article point “5” is stored, and the article point “7” is stored for the article name “Earthquake bulletin” in the article point totaling table of the user A in FIG. 27A. When the article points are totaled (that is, “7 points” + “8 points” + “5 points” = “20 points”), the article points that are “20” are totaled.

  The article point totaling table for user A in FIG. 27A stores the article point “7” for the article name “Earthquake Early Warning”. Thus, for the article “Earthquake Bulletin”, the article list “Earthquake Bulletin” displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151 is single-clicked, and the third The summary is displayed in the pane 403 (“+3 points”), the article list that is “Earthquake Early Warning” is double-clicked, and the text is displayed in the third pane 403 (“+4 points”).

  That is, FIG. 28B shows the article points included in the weighted article metadata transmitted from the client terminal apparatus 11-j used by the user B and the client terminal apparatus 11-k used by the user C, and the article B viewed by the user A. This is a total of article points given to articles by a method.

  The client terminal device 11-i used by the user A generates weighted article metadata based on the aggregated article points (for example, the aggregate ranking information table in FIG. 28B), and the generated weighted article metadata is transmitted to the network 12. Through () to other users (peers) belonging to the same community as the user A.

  Thus, when user A provides (transmits) weighted article metadata to other users (such as user B and user C) belonging to the same community as user A, the values of user A are added. Therefore, other users (such as user B and user C) can select information on the Internet from information including a wider range of values (information including the values of user A). .

  In the above-described example, based on the article points included in the weighted article metadata transmitted from the peers (user B and user C), they are displayed on the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. In the above description, the article points of the articles in the article list are aggregated. However, the article points may be aggregated by adding article points by the operation of the user (user A). Specifically, for example, the client terminal device 11-i used by the user A is a screen displayed by the GUI 173 of the RSS reader 151 based on the article point aggregation table of the user A, the user B, and the user C. The article points of the articles in the article list displayed in the second pane 402 may be totaled. In this case, the operation of the user (user A) is also reflected in the display order of the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151.

  That is, the article point by the operation of the user A can be added to the article point of the article in the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151.

  In the above-described example, the top five articles are described as being transmitted together with the article points. However, the top five articles are not limited to the top five articles, and may be, for example, the top ten articles.

  Next, RSS information reception processing will be described with reference to the flowchart of FIG.

  In step S301, the article circulation module 172 controls the communication unit 109 to cause the communication unit 109 to receive RSS information provided by a device (for example, a Web server) connected to the Internet via the network 12. The article circulation module 172 controls the communication unit 109 to supply the received RSS information to the GUI 173 to be displayed on the second pane 402 of the screen displayed by the GUI 173.

  For example, in step S301, the article circulation module 172 controls the communication unit 109 to inquire whether or not the article has been updated to the site 153 (RSS server 14) on the Internet via the network 12. The communication unit 109 receives RSS information from the above site 153 (RSS server 14), supplies the received RSS information to the GUI 173, and supplies it to the second pane 402 of the screen displayed by the GUI 173 for display. That is, in the second pane 402 of the screen displayed by the GUI 173, an article updated by the site 153 (RSS server 14) on the Internet is displayed.

  Specifically, for example, the article list displayed in the second pane 402 (when the feed tab 421 of the first pane is selected) on the screen displayed by the GUI 173 of the RSS reader 151 in FIG. 6 described above is displayed. .

  In step S302, the article circulation module 172 determines whether a predetermined time has elapsed. If it is determined in step S302 that the predetermined time has elapsed, the process returns to step S301 and the above-described processing is repeated.

  Here, as the predetermined time, for example, 15 minutes, 1 hour or the like is set by a user operation. In other words, by setting the predetermined time short, the interval for circulating and receiving RSS information is shortened. On the other hand, by setting the predetermined interval long, the interval for circulating and receiving RSS information is increased. Become.

  On the other hand, if it is determined in step S302 that the predetermined time has not elapsed, the process of step S302 is repeated until the predetermined time has elapsed.

  In this way, the RSS reader 151 receives RSS information from the site 153 (RSS server 14) on the Internet via the network 12.

  Next, processing for displaying an article list in ranking order will be described with reference to the flowchart of FIG.

  In step S321, the communication module 176 controls the communication unit 109 to determine whether the communication unit 109 has received weighted article metadata from the client terminal device 11 used by other users belonging to the community via the network 12. Determine whether.

  If it is determined in step S321 that the communication unit 109 has not received the weighted article metadata from the client terminal device 11 used by another user, the communication module 176 controls the communication unit 109 to control the network 12. Then, the process of step S321 is repeated until the communication unit 109 receives weighted article metadata from the client terminal device 11 used by another user.

  On the other hand, if it is determined in step S321 that the communication unit 109 has received weighted article metadata from the client terminal device 11 used by another user, the process proceeds to step S322, and the communication module 176 receives the received weighted article metadata. Is recorded in the recording unit 108.

  For example, in step S322, the communication module 176 receives the weighted article metadata from the client terminal device 11-j used by the user B and the client terminal device 11- used by the user C when the communication unit 109 receives the weighted article metadata. Each weighted article metadata is recorded in the recording unit 108.

  At this time, in the weighted article metadata received from the user B, information stored in the article point totaling table of the user B in FIG. 27B is described in the RSS format, and the weighted article metadata received from the user C is included in the weighted article metadata. Suppose that the information stored in the article point totaling table of user C in FIG. 27C is described in the RSS format.

  In step S323, the display ranking totaling module 178 determines whether or not a predetermined time for totaling display ranking totaling information that is data for displaying articles in the order of article points on the GUI 173 has elapsed.

  If it is determined in step S323 that the predetermined time for counting the display ranking total information has not elapsed, the process returns to step S321 and the above-described processing is repeated. That is, by repeating the processes of steps S321 to S323 until a predetermined time for counting the weighted article metadata has elapsed, the recording unit 108 can receive the weighted articles transmitted from the client terminal devices 11 used by other users. Continue to record metadata (ie, article points for articles are accumulated).

  If it is determined in step S323 that the predetermined time for counting the display ranking total information has elapsed, the process proceeds to step S324, and the display ranking information totaling unit 231 reads the weighted article metadata recorded in the recording unit 108. The article points for each article included in the read weighted article metadata are totaled. The display ranking information totaling unit 231 supplies the totaled article points to the display control unit 232 as display ranking totaling information.

  For example, in step S324, the display ranking information totaling unit 231 displays the weighted article meta data from the client terminal device 11-j used by the user B and the client terminal device 11-k used by the user C recorded in the recording unit 108. The data is read, the article points for each article included in the read weighted article metadata are aggregated, and the aggregated article points are supplied to the display control unit 232 as display ranking aggregation information.

  Specifically, the display ranking information totaling unit 231 includes weighted article metadata in which information stored in the article point aggregation table of the user B in FIG. 27B is described in the RSS format and the article point of the user C in FIG. 27C. The weighted article metadata in which the information stored in the aggregation table is described in RSS format is read, and the article points for each article included in the read weighted article metadata are totaled. As a result, article points for articles stored in the aggregate ranking information table of FIG. 28A are aggregated.

  The number of weighted article metadata to be aggregated is not limited to the above two (weighted article metadata transmitted from the client terminal device used by user B and user C), Weighted article metadata transmitted from the client terminal device 11 used by the user may be included. That is, the number of weighted article metadata that the display ranking information totaling unit 231 counts is an arbitrary number.

  Further, when the weighted article metadata is not transmitted from the client terminal device 11 used by another user, the display ranking information totaling unit 231 performs aggregation using the weighted article metadata transmitted last time. For example, when the weighted article metadata is transmitted from the client terminal apparatus 11-j used by the user B, but the weighted article metadata is not transmitted from the client terminal apparatus 11-k used by the user C, The display ranking information totaling unit 231 includes the weighted article metadata transmitted from the client terminal device 11-j used by the user B recorded in the recording unit 108 and the previous user C recorded in the recording unit 108. Based on the weighted article metadata transmitted from the client terminal device 11-k to be used, the article points for each article included in the weighted article metadata are totaled.

  Further, as described above, the article points by the operation of the user (user A) (for example, the article point totaling table of the user A in FIG. 27A) are added and the article points are totaled (for example, the total ranking information table in FIG. 28B). You may do it.

  In step S325, the display control unit 232 causes the article list to be displayed in the second pane 402 of the screen displayed by the GUI 173 in order of ranking based on the display ranking total information supplied from the display ranking information totaling unit 231, and step S321. Returning to the process, the above-described process is repeated.

  For example, in step S325, the display control unit 232 displays the article list by the GUI 173 in order of ranking based on the display ranking total information including the information of the total ranking information table in FIG. 28A supplied from the display ranking information totaling unit 231. Displayed on the second pane 402 of the screen.

  Note that, as described above, the display control unit 232 includes the information of the total ranking information table of FIG. 28B that is totaled by adding article points by the operation of the user (user A) supplied from the display ranking information totaling unit 231. Based on the ranking summary information, the article list may be displayed in the second pane 402 of the screen displayed by the GUI 173 in order of ranking.

  Specifically, for example, the article list displayed in the second pane 402 (when the peer tab 422 in the first pane is selected) on the screen displayed by the GUI 173 of the RSS reader 151 in FIG. 29 described above is displayed.

  Thus, since the article list is displayed in the ranking order in the second pane 402 of the screen displayed by the GUI 173 based on the article points for the articles from the other peers (user B and user C), the user A Makes it easy to select information based not only on the values of the user A itself but also on the values of the person who has a personal exchange with the user A (user B and user C).

  Further, the weighted article metadata received by user A from user B reflects the article points included in the weighted article metadata received by user B, and the weighted article metadata received from user C is included in the weighted article metadata received from user C. The item points included in the weighted article metadata received by the user C are reflected. Accordingly, the user A is indirectly provided with the weighted article metadata from users other than the user B and the user C who have received the weighted article metadata directly.

  Next, processing for providing weighted article metadata will be described with reference to the flowchart of FIG.

  In step S341, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user 152 is detected. For example, in step S341, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user A is detected.

  If it is determined in step S341 that an operation on the GUI 173 by the user 152 is not detected, the user operation sensor 191 repeats the process in step S341 until an operation on the GUI 173 by the user 152 is detected.

  If it is determined in step S341 that an operation on the GUI 173 by the user 152 has been detected, the process proceeds to step S342, and the user operation sensor 191 sends the user operation information corresponding to the detected operation of the user 152 to the operation point conversion unit 241. Supply.

  For example, in step S342, the user operation sensor 191 causes the user A to double-click an article that is “Today's weather” in the article list displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. When an operation for displaying the text in the third pane 403 is performed, the user's operation that is “double click” and the article that is “Today's weather” in which the text is displayed in the third pane 403 (subscription status) User operation information including at least the information of the article) is supplied to the operation point conversion unit 241.

  In step S <b> 343, the operation point conversion unit 241 gives article points to an article viewed by the user 152 based on the user operation information supplied from the user operation sensor 191. The operation point conversion unit 241 supplies user operation article points, which are information of articles to which article points are given, to the notification ranking information totaling unit 242.

  For example, in step S343, the operation point conversion unit 241 determines the user operation based on the user's operation “double click” included in the user operation information supplied from the user operation sensor 191 and the information on the article in the subscription state. By the operation of A, it can be seen that the article that is “Today's weather” is double-clicked and the text is displayed in the third pane 403, so “+4 points” for the article that is “Today's weather” And the user-operated article point including the information of the article “Today's weather” to which the article point “+4 points” is assigned is supplied to the notification ranking information totaling unit 242.

  That is, it can be said that the operation point conversion unit 241 determines the points to be given by the article point definition table recorded in the recording unit 108.

  In step S344, the notification ranking aggregation module 179 determines whether or not a predetermined time for counting the notification ranking aggregation information has elapsed.

  If it is determined in step S344 that the predetermined time for counting the notification ranking total information has not elapsed, the process returns to step S341 and the above-described processing is repeated. That is, by repeating the processing from step S341 to step S344 until a predetermined time for totaling the notification ranking total information has elapsed, the notification ranking totalization module 179 accumulates user operation information by the operation of the user 152, and the article Continue to give article points to (ie, articles keep accumulating article points).

  If it is determined in step S344 that the predetermined time for counting the notification ranking total information has elapsed, the process proceeds to step S345, where the notification ranking information totaling unit 242 stores other client terminal devices 11 recorded in the recording unit 108. The weighted article metadata 177 received from is read.

  For example, in step S345, the notification ranking information totaling unit 242 weights the article metadata from the client terminal device 11-j used by the user B and the client terminal device 11- used by the user C recorded in the recording unit 108. 177 is read.

  At this time, in the weighted article metadata received from the user B, information stored in the article point totaling table of the user B in FIG. 27B is described in the RSS format, and the weighted article metadata received from the user C is included in the weighted article metadata. The information stored in the article point totaling table of user C in FIG. 27C is described in the RSS format.

  In step S346, the notification ranking information totaling unit 242 totals the notification ranking total information based on the user operation article points supplied from the operation point conversion unit 241 and the read weighted article metadata 177. The notification ranking information totaling unit 242 supplies the totaled notification ranking totaling information to the metadata generation unit 243.

  For example, the notification ranking information totaling unit 242 uses the user of FIG. 27A described above as the information on the article “Today's weather” provided with the article point “+4 points” supplied from the operation point conversion unit 241. Stored in the article point total table of A. That is, as a result of the user A's operation being double-clicked on an article that is “Today's weather” as stored in the third row from the top of the third column of the user A article point tabulation table in FIG. 27A. , The article point of the article “weather today” is changed from “6” to “10” (ie, “+4 points”).

  The notification ranking information totaling unit 242 describes the information stored in the user A's article point totaling table in FIG. 27A and the information stored in the user B's article point totaling table in FIG. 27B read from the recording unit 108 in RSS format. The notification ranking aggregation information is aggregated based on the weighted article metadata and the weighted article metadata in which the information stored in the article point aggregation table of the user C in FIG. 27C is described in the RSS format. As a result, article points for articles stored in the aggregate ranking information table of FIG. 28B are aggregated. The notification ranking information totaling unit 242 supplies the notification ranking totaling information to the metadata generation unit 243.

  In step S347, the metadata generation unit 243 (provides to other users based on the notification ranking aggregation information supplied from the notification ranking information aggregation unit 242 and the weighted article metadata 177 read from the recording unit 108). Generate weighted article metadata (for). The metadata generation unit 243 supplies the generated weighted article metadata (for providing to other users) to the communication module 176.

  For example, in step S347, the metadata generation unit 243, based on the notification ranking total information supplied from the notification ranking information totaling unit 242 and the weighted article metadata 177 read from the recording unit 108, displays the total ranking information table in FIG. 28B. The weighted article metadata in which the information stored in is described in the RSS format is generated, and the generated weighted article metadata is supplied to the communication module 176.

  Note that in step S347, the process of generating weighted article metadata (to be provided to other users) executed by the metadata generation unit 243 may be executed by the notification ranking information totaling unit 242. .

  In step S348, the communication module 176 controls the communication unit 109 so that the communication unit 109 receives the weighted article metadata (for providing to other users) supplied from the metadata generation unit 243 to the network. 12 is transmitted to the client terminal device 11 used by another user, the process returns to the process of step S341, and the above-described process is repeated.

  For example, in step S348, the communication module 176 controls the communication unit 109, and the information stored in the aggregate ranking information table of FIG. 28B supplied from the metadata generation unit 243 to the communication unit 109 is in RSS format. The described weighted article metadata (to be provided to the peer) is transmitted to the client terminal device 11-j used by the user B and the client terminal device 11-k used by the user C via the network 12. Send it.

  In this way, based on the article points for the article by the operation of the user A and the article points for the articles from other users (user B and user C), the article points are aggregated, and the aggregated article points are used as weighted article metadata. Since it can be provided to other users (user B and user C), it provides information based on the values of user A's own values and the values of people who interact with user A (users B and C). can do.

  In addition to the article point counting method, the content of the article is weathered over time in addition to adding the article point to the article and counting the article point by the above-described method of browsing the article by the user 152. Therefore (because the freshness of information falls), the ranking is lowered (the freshness of information is lowered) by reducing the number of article points given over time with respect to the article given article points. You can also.

  FIG. 33 is a graph for explaining the attenuation of article points over time.

  The vertical axis of the graph in FIG. 33 indicates the article point (P), and the larger the value on the vertical axis, the higher the value of the article point. The horizontal axis indicates time (t), and the value on the horizontal axis indicates A larger value indicates that more time has passed.

  Further, a time a is predetermined as a time for reducing the article points. That is, even if the article has not been operated by the user 152, the article points are not reduced until the time a has elapsed. Further, a time b is determined in advance as a time until the article point becomes “0 points” after the time a has elapsed. In other words, the reduction range of the article points is determined from the article points at the time a and the time b. Specifically, as the value of the article point is larger and the time b is shorter, the reduction range of the article point becomes larger (that is, the slope of the graph in FIG. 33 becomes larger), while the value of the article point becomes larger. The smaller the time b, the smaller the decrease in article points (that is, the slope of the graph in FIG. 33 becomes smaller).

  For example, the time a is set to “1 hour”, and the time b is set to “2 hours”.

  Hereinafter, increase / decrease of article points of an article (hereinafter referred to as article A) will be described with the passage of time.

  At time t0, the client terminal device 11 used by the user 152 receives the weighted article metadata from the client terminal device 11 used by the peer, and reads the article A based on the received weighted article metadata. The article list is displayed in the second pane 402 of the screen displayed by the GUI 173 of the RSS reader 151. At this time, the article point of the article A displayed in the second pane has not yet been browsed by the user 152 (since the article is not in a subscription state), and thus becomes “0 point”.

  Since the article A is single-clicked in the article list displayed in the second pane 402 and the summary of the article A is displayed in the third pane 403 by the operation of the user 152 at time t1, Article points increase (eg, “+3 points”).

  Further, at time t2, by the operation of the user 152, the article A is double-clicked in the article list displayed in the second pane 402, and the text of the article A is displayed in the third pane 403. The article point of A is further increased (for example, “+4 points”).

  After time t2, since the user 152 has not performed an operation on the article A, the article points of the article A do not increase / decrease and remain at a constant value.

  Then, at time t3, which is the time when time a has elapsed from time t2, since the time a for reducing the article point has elapsed, the article point of article A is reduced and determined by the article point and time b at time t3. The article points of the article A are reduced according to the reduction range.

  At time t4, by the operation of the user 152, the article A is double-clicked in the article list displayed in the second pane 402, and the text of the article A is displayed again in the third pane 403. Article points increase (for example, “+4 points”).

  After time t4, since the user 152 has not performed an operation on the article A, the article point again does not increase / decrease and remains at a constant value.

  Then, at time t5, which is the time when time a has elapsed from time t4, since the time a for reducing the article point has elapsed, the article point of article A is reduced and determined by the article point and time b at time t5. The article points of the article A are reduced according to the reduction range.

  Since the user 152 has not performed an operation on the article A after the time t5, the article points of the article A continue to decrease according to the decrease range determined by the article points and the time b at the time t5.

  Then, at time t6, which is the time when time b has elapsed from time t5, the article point becomes “0 point” when time b elapses after time a has elapsed, so the article point of article A is “0 point”. It becomes.

  That is, even if it is the article A to which the article point is given by the operation of the user 152, the information is weathered as time passes (because the freshness of the information is lowered). By reducing the article points of the article A given over time, the ranking of the article A can be lowered (freshness of information is lowered).

  For example, assuming that the Olympics are being held, the Olympics are mostly talked about during the Olympic period, for example, one month, three months, six months, one year,・ ・ As the time passes, the topicality will decrease, but as mentioned above, reducing the number of article points given over time may lower the ranking of Olympic articles over time it can. That is, for example, after one year, Olympic articles will not be ranked higher in the ranking.

  As a result, articles that are topical in the community are always positioned at the top of the ranking, so that the user 152 can easily acquire information that is likely to be interesting.

  Next, the article point attenuation process will be described with reference to the flowchart of FIG.

  In step S <b> 401, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user 152 is detected. For example, in step S401, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user A is detected.

  If it is determined in step S401 that an operation on the GUI 173 by the user 152 is not detected, the user operation sensor 191 repeats the process in step S401 until an operation on the GUI 173 by the user 152 is detected.

  If it is determined in step S401 that an operation on the GUI 173 by the user 152 has been detected, the process proceeds to step S402, and the user operation sensor 191 sends the user operation information corresponding to the detected operation of the user 152 to the operation point conversion unit 241. Supply. The operation point conversion unit 241 gives article points to an article viewed by the user 152 based on user operation information supplied from the user operation sensor 191. The operation point conversion unit 241 supplies the user operation article point, which is information on the article to which the article point is given, to the article point attenuation unit 244.

  For example, in step S401, the operation point conversion unit 241 determines the user operation based on the user operation “double click” included in the user operation information supplied from the user operation sensor 191 and the information on the article in the subscription state. By the operation of A, it can be seen that the article that is “Today's weather” is double-clicked and the text is displayed in the third pane 403, so “+4 points” for the article that is “Today's weather” The user operation article point including the information of the article “Today's weather” to which the article point “+4 points” is assigned is supplied to the article point attenuation unit 244.

  In step S402, the article point attenuation unit 244 determines whether or not a predetermined time has elapsed. For example, the article point attenuation unit 244 determines whether or not the time “1 hour” has elapsed.

  If it is determined in step S402 that the predetermined time has not elapsed, the process of step S402 is repeated until the predetermined time has elapsed.

  If it is determined in step S402 that the predetermined time has elapsed, the process proceeds to step S403, and the article point attenuation unit 244 attenuates the article point of the user operation article supplied from the operation point conversion unit 241.

  For example, when the article point attenuation unit 244 attenuates the article point by “+1 point” every time a predetermined time elapses, the article point attenuation unit 244 is supplied from the operation point conversion unit 241 in step S403. “+1 point” is attenuated from the user-operated article point including the information of the article that is “Today's weather” given the article point that is “+4 points”. That is, the article point of the article that is “Today's weather” is “+3 points”.

  In step S <b> 404, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user 152 is detected. For example, in step S401, the user operation sensor 191 determines whether an operation on the GUI 173 (of the RSS reader 151) by the user A is detected.

  If it is determined in step S404 that an operation on the GUI 173 by the user 152 has not been detected, the process returns to step S403, and the above-described process is repeated. In other words, the article point attenuation unit 244 continues to attenuate article points until the user operation sensor 191 detects an operation on the GUI 173 by the user 152 by the process of step S404.

  For example, the article point attenuating unit 244 attenuates the article points of articles that are “Today's weather” as “+3 points”, “+2 points”, and “+1 points” with the passage of time.

  If it is determined in step S404 that an operation on the GUI 173 by the user 152 has been detected, the process returns to step S402, and the user operation sensor 191 sends the user operation information corresponding to the detected operation of the user 152 to the operation point conversion unit 241. Supply. The operation point conversion unit 241 gives article points to an article viewed by the user 152 based on user operation information supplied from the user operation sensor 191. The operation point conversion unit 241 supplies the user operation article point, which is information on the article to which the article point is given, to the article point attenuation unit 244.

  The article point attenuating unit 244 increases the article point of the article in which the article point is attenuated based on the user operation article point supplied from the operation point conversion unit 241. The article point attenuation unit 244 supplies user operation article points to the notification ranking information totaling unit 242.

  For example, in step S <b> 404, the operation point conversion unit 241 again performs the operation of the user who is “double click” included in the user operation information supplied from the user operation sensor 191 and the information on the article in the subscription state. By the operation of the user A, it can be seen that the text “Today's weather” is double-clicked and the text is displayed in the third pane 403. Therefore, for the article “Today's weather”, “+4 The user-operated article point including the information of the article “Today's weather” to which the article point “+4 points” is assigned is supplied to the article point attenuating unit 244.

  The article point attenuation unit 244 is based on the user operation article point including the information of the article “Today's weather” to which the article point “+4 points” supplied from the operation point conversion unit 241 is added. Is attenuated, and “+4 points” is increased to the article point of the article that is “Today's weather” that became “+1 point”. That is, the article point of the article that is “Today's weather” is “+5 points”.

  Then, the notification ranking information totaling unit 242, when a predetermined time for totaling the notification ranking totaling information has elapsed, based on the user operation article point supplied from the article point attenuation unit 244 and the read weighted article metadata 177, Notification ranking total information can be totaled.

  As described above, even if the article A is given the article point by the operation of the user 152, the information is weathered over time (because the freshness of the information is lowered). Thus, the ranking of the article A can be reduced (the freshness of the information can be reduced) by reducing the article points of the article A given over time.

  In addition, in the example described above, in order to make the explanation easy to understand, in the above-described example, the article points calculated by yourself and the article points calculated by other users are simply added as they are. Although explained in the tabulation method, it is also possible to optimize and sum up those article points. That is, a weight can be given to a specific article point.

The article point R _A (a) of the article URL (a) included in the notification ranking total information can be obtained by, for example, Expression (1).

R _A (a) = α × P (a) + (1−α) × {β × F _A (a) + (1−β) × Average (F _i (a))} (1)

However, in Expression (1), P (a) is an article point by the user 152 (for example, the user A), and F _A (a) is an article point received from the peers (for example, the user B and the user C). F _i (a) is an article point received from other than the peer.

  Α (0 <α <1) is a self-taste information reflection coefficient that is a measure for reflecting article points by the user 152 (for example, user A), and β (0 <β <1) is a community (group ) Is an intra-community information reflection coefficient that is a measure for adjusting the propagation of information.

  In other words, if the user wants to emphasize the article points by his / her own operation, the self-taste information reflection coefficient α is set to a value closer to “1”, while the article points by his / her own operation are disregarded (not emphasized). In this case, the self preference information reflection coefficient which is α is set to a value closer to “0”.

  Also, if you want to focus on article points from peers belonging to the community, set the information reflection coefficient in the community, which is β, to a value closer to “1”, while on the other hand from users other than peers belonging to the community When it is desired to place importance on article points, the in-community information reflection coefficient β is set to a value closer to “0”.

For example, when “α = 0.8” is set as the self-taste information reflection coefficient α, the equation (1) is expressed as “R _A (a) = 0.8 × P (a) + 0.2 × {β × F _A ( a) + (1-β) × Average (F _i (a))} ”. Here, “P (a)” is “article point by own operation”, and “β × F _A (a) + (1−β) × Average (F _i (a))” is “others” It can be said that it is “the article points received from”, so the equation (1) can be expressed as “R _A (a) = 0.8 ד article points by own operation ”+ 0.2 ד article points received from others ” Can be described.

  At that time, the ratio of “article points by own operation” and “article points received from others” is “0.8: 0.2”, that is, “4: 1”, so “α = 0.8” is set. In this case, “article points by own operation” is counted as information that is four times (400%) more important than “article points received from others”.

For example, when “β = 0.8” is set as the intra-community information reflection coefficient β, the expression (1) is expressed as “R _A (a) = α × P (a) + (1−α) × { 0.8 × F _A (a) + 0.2 × Average (F _i (a))} ”. Here, looking at “article points received from others” which is “0.8 × F _A (a) + 0.2 × Average (F _i (a))”, “F _A (a)” Since “Average (F _i (a))” is the article point received from other than the peer (average), equation (1) can be expressed as “R _A (a) = α × P (a) + (1−α) × {0.8 × “article point received from peer” + 0.2 × “article point received from other than peer”} ”.

  At that time, the ratio of “article points received from peers” to “article points received from other than peers” is “0.8: 0.2”, that is, “4: 1”, so “β = 0.8” is set. In this case, “article points received from peers” are counted as information that is four times (400%) more important than “article points received from other than peers”.

  Next, a process for providing weighted article metadata obtained by weighting article points will be described with reference to the flowchart of FIG.

  The processing from step S441 to step S445 is the same as the processing from step S341 to step S345 in FIG. 32, and a description thereof will be omitted.

  In step S <b> 446, the notification ranking information totaling unit 242 weights the articles based on the user operation article points and the read weighted article metadata 177 supplied from the operation point conversion unit 241 and totals the notification ranking total information. To do. The notification ranking information totaling unit 242 supplies the totaled notification ranking totaling information to the metadata generation unit 243.

  For example, in the client terminal device 11 used by the user A, the notification ranking information totaling unit 242 includes the above formula (1), the user A's article point totaling table in FIG. 27A, and the user in FIG. Weighted article metadata in which information stored in the article point total table of B is described in RSS format, and information stored in the article point total table of user C in FIG. 27C is described in RSS format. Based on the weighted article metadata, the notice ranking aggregation information is aggregated.

That is, an expression of “R _A (a) = α × P (a) + (1−α) × {β × F _A (a) + (1−β) × Average (F _i (a))}” When the self-preference information reflection coefficient “α = 0.8” and the intra-community information reflection coefficient “β = 0.8” are set for (1), the equation (1) is expressed as “R _A (a) = 0.8 × P (a) + 0.2 × {0.8 × F _A (a) + 0.2 × Average (F _i (a))} ”.

  Here, of the article names in the article point aggregation table of FIG. 27, the aggregation of article points with the article name “Earthquake Bulletin” will be described as an example.

  In the article point totaling table of the user A in FIG. 27A, the article point “7” is assigned to the article name “Earthquake bulletin”. In addition, in the article point totaling table of the user B in FIG. 27B, the article point “8” is assigned to the article name “Earthquake bulletin”. Furthermore, the article point “5” is assigned to the article point totaling table of the user C in FIG. 27C.

In Expression (1), P (a) is an article point by the user 152, F _A (a) is an article point received from the peer, and F _i (a) is received from other than the peer. Article point. That is, P (a) is an article point by user A, F _A (a) is an article point received from user B and user C, and F _i (a) has no corresponding article point. .

Therefore, when these conditions are applied to the expression (1), “R _A (a) = 0.8 × 7 + 0.2 × {0.8 × (8 + 5) + 0.2 × 0} = 7.68”. That is, the article point for the article name “Earthquake Early Warning” is “7.68”.

  For other article names, the same calculation is performed to aggregate article points, and the notification ranking aggregate information is aggregated.

  The processing in step S447 and step S448 is the same as the processing in step S347 and step S348 in FIG. 32, and a description thereof will be omitted.

  Thus, since the weight can be given to the article point by one's own operation or the article point received from another user, the article list can be displayed in a more characteristic ranking order.

  As described above, when a user selects information on the Internet, not only the user's own values but also a person who has a personal interaction with the user (for example, a friend or family member, a business relationship) Etc.), the selection of information can be facilitated.

  In addition, information (articles and contents) that the user does not realize that he wants due to the propagation of information (articles and contents) from people who have human interaction with the user, but may want it. ) Can be obtained.

  In response to the privacy issue of leakage of personal preference information, the result of adding and processing the preference information of people who have personal interaction with the user is provided instead of propagating only the user preference information. By doing so, anonymity is given to preference information. In addition, since rankings (viewing rates) are not collected in a central server or the like but are collected in each terminal in a distributed manner, server addition or server traffic concentration can be reduced.

  The ranking (viewing rate) is not aggregated in the central server or the like, but is collected in each terminal in a distributed manner, so that the ranking is specialized for the user and the community related to the user. That is, not all users obtain the same audience rating calculation result, and the ranking (audience rating) calculated individually is different for each user.

  In addition, although it is a totaling method of notification ranking total information or display ranking total information, it is not restricted to the example mentioned above, For example, a high article point is provided with respect to the article of a user (peer) who provides a highly reliable article. You may make it total by a function etc.

  In addition, the present invention has application extensibility to all information (resources) expressed by a unique ID (for example, URL) on the Internet, and generally, for example, RDF (Resource Description Framework) Or it becomes easy to extend to programs that use metadata such as RSS.

  Furthermore, in the above-described example, the weighted article metadata is described as information obtained by extending the RSS information described in the RSS format. However, the weighted article metadata is not limited to the format described in the RSS format. For example, SGML (Standard Generalized Mark) -up Language) format or XML format, etc., can be described in a format that can describe the metadata of the content. In addition, the RSS reader that browses (processes) RSS information has been described as an example of software that browses (processes) weighted article metadata. Any software that can browse (process) data describing content metadata, such as software that can be processed.

  In addition, the above-described method of counting article points is not limited to the method of sequentially adding article points each time a user operates, but only the article points for the operation with the highest article point among the operations performed by the user. It is also possible to tabulate. For example, when the user performs an operation of “+1 point” after an operation of “+1 point”, an operation for obtaining the highest article point without adding article points as an aggregation method for the operation is performed. Only “+4 points” which are article points may be totaled.

  The series of processes described above can be executed by hardware, but can also be executed by software. When a series of processing is executed by software, a program constituting the software may execute various functions by installing a computer incorporated in dedicated hardware or various programs. For example, it is installed from a recording medium in a general-purpose personal computer or the like.

  As shown in FIG. 2, this recording medium is distributed to provide a program to a user separately from a computer, and includes a magnetic disk 121 (including a flexible disk) on which a program is recorded, an optical disk 122 (CD- ROM (compact disc-read only memory)), magneto-optical disc 123 (including MD (trademark)), or semiconductor memory 124, etc., and not only constituted by a package medium but also preinstalled in a computer And the ROM 102 on which a program is recorded, which is provided to the user.

  Further, as shown in FIG. 4, this recording medium is distributed to provide a program to the user separately from the computer, and a magnetic disk 321 (including a flexible disk) on which the program is recorded, an optical disk 322 ( (Including CD-ROM), magneto-optical disk 323 (including MD (trademark)), or a package medium composed of a semiconductor memory 324, etc., as well as being provided to the user in a pre-installed state in a computer , And ROM 302 in which a program is recorded.

  Furthermore, a program for executing the above-described series of processing is installed in a computer via a wired or wireless communication medium such as a local area network, the Internet, or digital satellite broadcasting via an interface such as a router or a modem as necessary. You may be made to do.

  In the present specification, the step of describing the program stored in the recording medium is not limited to the processing performed in chronological order according to the described order, but is not necessarily performed in chronological order. It also includes processes that are executed individually.

  Further, in this specification, the system represents the entire apparatus constituted by a plurality of apparatuses.

It is a block diagram which shows the structure of one Embodiment of the P2P system to which this invention is applied. It is a block diagram which shows the structural example of a client terminal device. It is a figure which shows the example of a structure of the program performed by a client terminal device. It is a block diagram which shows the structural example of a P2P server. It is a figure which shows the example of a structure of the program run by a P2P server. It is a figure explaining the structure of the whole screen displayed by GUI of an RSS reader. It is a figure explaining the concept of a community. It is a figure which shows the example of the 1st pane when the feed tab is selected. It is a figure which shows the example of the 1st pane when the peer tab is selected. It is a figure explaining the relationship between a user and a peer. It is a figure explaining the relationship between RSS information transmitted / received between each terminal, and weighted article metadata. It is a figure which shows the example of the element of RSS information. It is a figure explaining the example of description of RSS information. It is a figure explaining the element of weighted article metadata. A description example of weighted article metadata will be described. It is a figure explaining the outline | summary of a process in case a client terminal device logs in to a P2P system. It is a flowchart explaining the login process of a P2P system. It is a figure explaining the outline | summary of a process in case a client terminal device requests | requires provision of weighted article metadata to another client terminal device. It is a flowchart explaining the process of provision of weighted article metadata. It is a figure which shows the example of the screen displayed by GUI of the RSS reader of the client terminal device which displays the dialog box which determines whether weighted article metadata is provided. It is a figure which shows the example of the screen displayed by GUI of the RSS reader of the client terminal device which displays the dialog box which shows permission of provision of weighted article metadata. It is a figure which shows the example of the screen displayed by GUI of the RSS reader of the client terminal device which displays the dialog box which shows refusal of provision of weighted article metadata. It is a figure explaining the outline | summary of the process which a client terminal device provides weighted article metadata with respect to another client terminal device. It is a flowchart explaining the process in which a client terminal device provides weighted article metadata to other client terminal devices. It is a figure explaining the outline | summary of the process of the article display by an article point. It is a figure which shows the example of the article point definition table which defines the article point provided with respect to an article by a user's operation. It is a figure which shows the example of the article point total table of the articles totaled by the user's operation. It is a figure which shows the example of the total ranking information table by which the article point was totaled by the client terminal device which the user A is using. It is a figure which shows the example of the screen displayed by GUI of the RSS reader which displays an article list based on the totaled article points. It is a flowchart explaining the reception process of RSS information. It is a flowchart explaining the process of the display of the article list in ranking order. It is a flowchart explaining the process of transmission of weighted article metadata. It is a figure explaining attenuation of the article point by progress of time. It is a flowchart explaining the process of article point attenuation | damping. It is a flowchart explaining the weighted article metadata provision process which weighted article points.

Explanation of symbols

  1 P2P system 11, 11-1 to 11-N client terminal device, 12 network, 13 P2P server, 101 CPU, 102 ROM, 103 RAM, 106 input unit, 107 output unit, 108 recording unit, 109 communication unit, 110 Drive, 121 magnetic disk, 122 optical disk, 123 magneto-optical disk, 124 semiconductor memory, 151 RSS reader, 171 login module, 172 article circulation module, 173 GUI, 174 peer list management module, 175 peer list, 176 communication module, 177 weighting Article metadata, 178 display ranking aggregation module, 179 notification ranking aggregation module, 191 user operation sensor, 192 first pane peer list management section, 201 Peer list management unit, 202 display control unit, 203 peer determination unit, 211 peer channel list, 212 recipe entry list, 213 peer cache, 231 display ranking information aggregation unit, 232 display control unit, 241 operation point conversion unit, 242 notification ranking Information totaling unit, 243 metadata generation unit, 244 article point attenuation unit, 301 CPU, 302 ROM, 303 RAM, 306 input unit, 307 output unit, 308 recording unit, 309 communication unit, 310 drive, 321 magnetic disk, 322 optical disk , 323 magneto-optical disk, 324 semiconductor memory, 351 P2P server module, 361 registration deletion acceptance module, 362 peer list, 363 name resolution module

Claims (11)

In the information processing apparatus used by the first user connected to the network,
An index indicating the frequency of browsing articles published on the network in a plurality of other information processing apparatuses, and an index transmitted from each of the other information processing apparatuses via the network Receiving means for receiving;
Recording means for recording the received indicator;
When a predetermined time has elapsed, a generating unit that generates total information indicating a total frequency of browsing for each article in the other information processing apparatus by totaling the recorded indexes;
An information processing apparatus comprising: display control means for controlling display so that the articles are displayed in the order of the sum of browsing frequencies based on the total information. The receiving means is a second user belonging to a set defined by the first user via the network, the second user permitting the first user to receive the indicator. 2. The information processing according to claim 1, wherein the index including contents of each operation of the second user transmitted from each of the other information processing apparatuses used by the user is received. apparatus. In the information processing method of the information processing apparatus used by the first user connected to the network,
An index indicating the frequency of browsing of articles published on the network in a plurality of other information processing apparatuses, the index transmitted from each of the other information processing apparatuses via the network A reception control step for controlling reception;
A recording step for recording the received indicator;
When a predetermined time has elapsed, a generation step for generating total information indicating a total frequency of browsing for each article in the other information processing apparatus by totaling the recorded indexes,
A display control step for controlling display so that the articles are displayed in the order of the sum of browsing frequencies based on the total information. In a program for causing a computer of an information processing apparatus connected to a network and used by a first user to perform information processing,
An index indicating the frequency of browsing of articles published on the network in a plurality of other information processing apparatuses, the index transmitted from each of the other information processing apparatuses via the network A reception control step for controlling reception;
A recording step for recording the received indicator;
When a predetermined time has elapsed, a generation step for generating total information indicating a total frequency of browsing for each article in the other information processing apparatus by totaling the recorded indexes,
And a display control step for controlling the display so that the articles are displayed in the order of the sum of the browsing frequencies based on the total information. In the information processing apparatus used by the first user connected to the network,
In the first other information processing apparatus, a first index indicating the frequency of browsing articles published on the network or the content of operations on the articles, the first index via the network Receiving means for receiving a first index received from another information processing apparatus;
Recording means for recording the received first indicator;
First generation means for generating a second index indicating the content of the operation on the article by the user;
Each of the articles in the first other information processing apparatus is obtained by counting the recorded first index and the generated second index when a predetermined first time has elapsed. Second generation means for generating a third index according to the frequency of browsing or the content of the operation on each of the articles, and the content of the operation on each of the articles in itself,
An information processing apparatus comprising: a transmission unit configured to transmit the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network. A reduction means for reducing the second index generated by the first generation means when the predetermined second time has elapsed, when the article is operated on the article, with the passage of time;
When the predetermined first time has elapsed, the second generation means aggregates the recorded first index and the reduced second index to thereby calculate the first index. Generating a third index according to the frequency of each reading of the article in another information processing device or the content of the operation on each of the articles and the content of the operation on each of the articles in itself The information processing apparatus according to claim 5. The second generation unit weights the recorded first index or the second index when the predetermined first time has elapsed, and both or one of them is By summing up the weighted first index and the second index, the frequency of each browsing of the article in the first other information processing apparatus or the content of the operation on each of the articles, The information processing apparatus according to claim 5, wherein a third index corresponding to a content of an operation on each of the articles by the user is generated. The receiving means is a second user belonging to a set defined by the first user via the network and allows the first user to receive the first indicator. The information processing apparatus according to claim 5, wherein the first index transmitted from each of the first other information processing apparatuses used by the second user is received. The transmission means uses the generated second index to be the second user belonging to the set via the network and permits the transmission of the third index. The second other information processing device used by the user or the third user belonging to the set and used by the third user who is permitted to transmit the third indicator. The information processing apparatus according to claim 5, wherein the information processing apparatus is transmitted to another information processing apparatus. In the information processing method of the information processing apparatus used by the first user connected to the network,
In the first other information processing apparatus, a first index indicating the frequency of browsing articles published on the network or the content of operations on the articles, the first index via the network A reception control step for controlling reception of the first index received from another information processing apparatus;
A recording step of recording the received first indicator;
A first generation step of generating a second index indicating the content of the operation on the article by the user;
Each of the articles in the first other information processing apparatus is obtained by counting the recorded first index and the generated second index when a predetermined first time has elapsed. A second generation step of generating a third index according to the frequency of browsing or the content of the operation on each of the articles and the content of the operation on each of the articles in the user;
A transmission control step for controlling transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network. Information processing method. In a program for causing a computer of an information processing apparatus connected to a network and used by a first user to perform information processing,
In the first other information processing apparatus, a first index indicating the frequency of browsing articles published on the network or the content of operations on the articles, the first index via the network A reception control step for controlling reception of the first index received from another information processing apparatus;
A recording step of recording the received first indicator;
A first generation step of generating a second index indicating the content of the operation on the article by the user;
Each of the articles in the first other information processing apparatus is obtained by counting the recorded first index and the generated second index when a predetermined first time has elapsed. A second generation step of generating a third index according to the frequency of browsing or the content of the operation on each of the articles and the content of the operation on each of the articles in the user;
A transmission control step for controlling transmission of the generated third index to the first other information processing apparatus or the second other information processing apparatus via the network. program.

Images