JP4921991B2 - Information presentation server - Google Patents

Description

  The present invention relates to an information presentation server such as an electronic bulletin board, a user review, and a vote.

  Affiliate advertisements (When a website or the like links to a company site and a viewer registers as a member or purchases a product on the company's site via the link, a reward is paid to the organizer of the link source site. With the widespread use of structured advertisements, consumers who can create high-quality content can create their own blogs (Web logs: diary-like sites) and post advertisements on them to get rewards. .

  On the other hand, conventional electronic bulletin boards, user reviews, and voting systems basically provide information on a free volunteer basis.

  Therefore, it is expected that high-quality content will flow from electronic bulletin boards to blogs in the future.

  The applicant has not been able to find published prior art documents related to the present invention by the time of filing. Therefore, prior art document information is not disclosed.

  As described above, there is a concern about the decline of electronic bulletin boards in the future, but on the other hand, a certain number of accesses is required to get rewards for advertising on blogs. A handful of bloggers (blog organizers) can earn a significant amount of access from only the content produced by one blog, and how to increase the number of accesses for other bloggers is a challenge.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to collect high-quality contents on an electronic bulletin board or the like, and to guide browsing to the blog from the electronic bulletin board or the like. An object of the present invention is to provide an information presentation server that can be used to solve both problems.

In order to solve the above-described problems, in the present invention, as described in claim 1, address generation means for generating an address serving as a trackback destination in response to a request from a client, and another server Trackback receiving means for receiving a trackback addressed to the above address, trackback analyzing means for analyzing the received trackback and storing posted contents including the address of the server of the trackback source in a database, and in response to a request from a client Display means for displaying the stored contents of the database on the client, and means for delivering the blog module generated from the posted contents in response to a request for the blog module from the client, the address generating means For generation of destination address To, and summarized as log information presentation server for generating a tag for embedding for obtaining the blog module.

In addition, as described in claim 2, in the information presentation server according to claim 1, the address generation means may include information that is part of the posted content by the information presenting server and the posted content by the server of the trackback source. It is possible to generate an included address.

In addition, as described in claim 3, in the information presentation server according to claim 2, the address generation means may include information that is a part of the posted content by the information presenting server and the posted content by the server of the trackback source. It can be added as a parameter to the address.

In addition, as described in claim 4, in the information presentation server according to claim 1 , the address generation means may include information that is part of the posted content by the information presenting server and the posted content by the trackback source server. In addition to saving in the parameter saving database, an ID for identifying the information can be added to the address as a parameter.

According to a fifth aspect of the present invention, the step of generating an address as a trackback destination in response to a request from the client, the step of receiving a trackback destined for the address from another server, and the received Analyzing the trackback, storing the posted contents including the address of the server that is the trackback source in the database, displaying the stored contents of the database on the client in response to a request from the client, and the blog module from the client A blog module generated from the posted content in response to a request of the blog, and the step of generating the address includes embedding a blog for acquiring the blog module when generating an address as a trackback destination Information to generate tags for use It can be configured as a control method.

According to a sixth aspect of the present invention, a function for generating an address as a trackback destination in response to a request from a client, a function for receiving a trackback whose destination is the address from another server, and A function to analyze the trackback and store the posted contents including the address of the server of the trackback source in the database, a function to display the stored contents of the database on the client in response to a request from the client, and a blog module from the client The function of distributing the blog module generated from the posted content in response to the request of the computer is realized by the computer, and the function of generating the address is for acquiring the blog module when generating the address to be the trackback destination. Tags for embedding blogs It can be configured as a generation information presentation control program.

  In the information presentation server of the present invention, since a part of the contents of the blog can be posted on the electronic bulletin board etc. using the track back function of the blog, high-quality content can be collected on the electronic bulletin board etc. At the same time, it is possible to induce browsing of the blog from the electronic bulletin board or the like, or to secure a blog guidance opening, and it is possible to simultaneously improve the quality of the electronic bulletin board and increase the number of accesses to the blog.

  Hereinafter, preferred embodiments of the present invention will be described.

<System configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, a bulletin board server 2 and a blog server 3 are connected to a network 1 such as the Internet, and a bulletin board poster client 4A, a bulletin board browser client 4B, a blogger client 4C, a blog viewer client 4D, and the like. Is connected.

  FIG. 2 is a diagram showing a configuration example of the bulletin board server 2, and a bulletin board DB 21 for storing data necessary for processing in the bulletin board server 2 and registration of articles in the bulletin board DB 21 in response to a request from the client 4 A of the bulletin board poster ( And a bulletin board posting unit 22 for performing (posting). Note that some bulletin boards set a plurality of parameters such as scoring evaluation, radar chart, vote selection, etc. in addition to the title and text, and these inputs are also performed.

  The bulletin board server 2 also includes a trackback URL / tag generator 23 that generates and returns a tag for embedding a blog for acquiring a trackback URL and a blog module to be described later in response to a request from the blogger client 4C. The trackback URL / tag generation unit 23 uses the parameter storage DB 28 as necessary.

  The bulletin board server 2 also analyzes the trackback receiving unit 24 that receives the trackback from the blog server 3 and the destination URL (trackback URL) of the received trackback, and the trackback URL that stores the analysis result (bulletin board parameter) in the bulletin board DB 21. And an analysis unit 25.

  In addition, the bulletin board server 2 returns a bulletin board content from the bulletin board DB 21 in response to a request from the bulletin board browser client 4B, and a bulletin board in response to a request from the blog browser client 4D. A blog module distribution unit 27 that generates and returns a blog module from the bulletin board parameters of the DB 21;

  FIG. 3 is a diagram illustrating an example of the bulletin board DB 21, which includes a bulletin board master table 211, a posting data table 212, and a poster table 213. The bulletin board master table 211 includes fields such as a bulletin board ID, a bulletin board type, a bulletin board name, a bulletin board creation date and time, and a creator ID. The post data table 212 includes fields such as a post ID, bulletin board ID, contributor ID, post date, title, text, overall work evaluation, screenplay evaluation, music evaluation, performer evaluation, other additional parameters, trackback source URL, blog name, etc. Is included. The contributor table 213 includes fields such as contributor ID, password, e-mail address, nickname, real name, date of birth, and other personal information. The bulletin board master table 211 and the posting data table 212 are associated with each other by the bulletin board ID, and the posting data table 212 and the poster table 213 are associated with each other by the poster ID.

  FIG. 4 is a diagram showing an example of the parameter storage DB 28, which includes fields such as ID, parameter name, and value.

<Operation>
FIG. 5 is a diagram showing an outline of the operation of the above embodiment.

  In FIG. 5, when an article is posted from the bulletin board poster client 4A to the bulletin board server 2 (step S1), the bulletin board posting unit 22 of the bulletin board server 2 stores the posted content in the bulletin board DB 21 (step S2). Posting to the bulletin board server 2 is performed by an HTTP (Hyper Text Transfer Protocol) GET request or POST request. Articles are described in HTML (Hyper Text Markup Language), etc., and the contents of postings are the <input> tag in the HTML <form> tag. 2 is sent.

  On the other hand, when there is a trackback URL acquisition request from the blogger client 4C, the trackback URL / tag generation unit 23 of the bulletin board server 2 responds to the operation of a trackback URL generation screen, which will be described later, and the parameters unique to the bulletin board not included in the trackback. (Evaluation content of the work, etc.) is received, a trackback URL to which the parameters are added and a tag for embedding a blog are generated and transmitted to the client 4C (step S11). The URL generation screen is for dealing with a bulletin board that requires setting of a plurality of parameters such as scoring evaluation, radar chart, and vote selection in addition to the title and text. Trackback does not have a function to send these parameters. However, by adding these parameter information at the time of trackback URL generation and having them trackback there, the same information as when posting on the bulletin board is added. .

  When the blogger acquires the trackback URL and the tag for embedding the blog, the blogger sets the trackback URL (with parameters) from the client 4C to his / her blog server 3 and posts the blog article in which the tag is embedded (step S12). 3 sends a trackback (with parameters) to the bulletin board server 2 (step S13).

  When the trackback receiving unit 24 of the bulletin board server 2 receives this trackback, the trackback URL analyzing unit 25 analyzes the trackback URL and stores the extracted parameters in the bulletin board DB 21 as post contents (step S14).

  Thereafter, when there is a browsing request from the bulletin board browser client 4B to the bulletin board server 2, the posting contents display unit 26 posts the contents of the title list, posting contents details (text, evaluation, etc.) from the bulletin board DB 21 (submission by track back). In this case, a link to the trackback source and the blog name are acquired (step S21), and transmitted to the client 4B for display (step S22).

  When there is a browsing request from the blog viewer client 4D to the blog server 3, the blog server 3 transmits and displays the article content to the client 4D (step S31). The client 4D requests the blog module from the bulletin board server 2 by executing the tag embedded in the process of displaying the blog article content, and the blog module distribution unit 27 acquires the bulletin board parameters from the bulletin board DB 21 (step S32). A blog module is generated and transmitted to the client 4D for display (step S33).

  FIG. 6 is a diagram showing an example of a trackback from a blog to a bulletin board and a link from the bulletin board to the blog. By performing a trackback from an article on the blog server 3 to the bulletin board server 2, an outline of the blog article on the bulletin board server 2 is shown. And bulletin board parameters are reflected as post contents. In addition, a link to the blog server 3 is made from the outline of the blog article on the bulletin board server 2. As a result, high-quality content can be collected on the bulletin board server 2 side, and browsing on the bulletin board server 2 can be expected on the blog server 3 side.

  FIG. 7 is a diagram showing an example of a link from the bulletin board to the blog / detail page. For a link from the posting list page of the bulletin board server 2, a link is made to the blog article of the blog server 3 in the case of posting in the trackback. In the case of normal posting, a link is made to the posted content detail page in the bulletin board server 2.

  Hereinafter, the operation will be described in more detail.

  FIG. 8 is a sequence diagram showing an example of processing related to track back.

  In FIG. 8, when a trackback URL generation request is sent from the blogger client 4C to the bulletin board server 2 (step S101), the bulletin board server 2 returns a trackback URL generation screen to the client 4C (step S102). FIG. 9 is a diagram showing an example of a trackback URL generation screen, which is an example of a bulletin board that evaluates a movie. An evaluation setting column 41 that answers a questionnaire item and a button for instructing trackback URL generation 42, a trackback URL display field 43 for displaying the generated trackback URL, and a button 44 for instructing to copy the generated trackback URL to the clipboard. The parameters set in the evaluation setting column 41 vary depending on the type of bulletin board to be posted, and are defined in advance on the bulletin board server 2 side. For example, in the user review of a movie, the evaluation score for the whole work, the script, music, performers, etc. is used as a parameter.

  Returning to FIG. 8, the posting content (evaluation) is input on the trackback URL generation screen in the client 4C (step S103), and the bulletin board parameter indicating the posting content is transmitted to the bulletin board server 2 by instructing the generation of the trackback URL (step S103). S104). The bulletin board parameters are sent from the client 4C to the bulletin board server 2 by an <input> tag in an HTML <form> tag.

  The bulletin board server 2 generates a trackback URL to which the bulletin board parameter is added based on a predetermined rule based on the bulletin board parameter acquired from the client 4C, and generates a tag for embedding a blog for acquiring the blog module (step). S105), and transmits to the client 4C (step S106).

  FIG. 10 is a diagram showing an example of the trackback URL. If the original trackback URL is (a), when there is one parameter, “rate = 5” or the like is added as shown in FIG. In the case of a plurality, “rate = 5 & story = 3 & cast = 5 & music = 4” is added as shown in (c). In order to prevent tampering or the like, the parameter portion can be reversibly encrypted using Crypt-DES or the like as shown in (d) to obtain “qawsedrftgyhujikolp / azzzsxdcfvgbhnjmk”. Further, if there are many parameters to be added and it is difficult to add them to the URL, the contents of the parameters are temporarily stored with a unique ID in the parameter storage DB 28 (FIG. 2), and the ID is stored as shown in FIG. 10 (e). Can be added as a parameter such as “id = 1234567890”.

  FIG. 11 is a diagram showing an example of a tag for embedding a blog, which is an example using IFRAME (Inline Frame), but the URL of the blog module “http://movies.yahoo.co.jp/module/325438/module. The blog module is acquired from “htm”, and the content is displayed in the blog page without any screen transition. In addition, it can change to IFRAME and a tag can also be comprised by JavaScript.

  Returning to FIG. 8, the blogger who has acquired the trackback URL and the tag for embedding the blog from the bulletin board server 2 submits the article in which the tag is embedded from the client 4C to his blog server 3, and sets the trackback URL ( Step S107).

  The blog server 3 reflects the article on the blog (step S108), and transmits a trackback Ping to the set trackback URL of the bulletin board server 2 (step S109). FIG. 12 is a diagram showing an example of a trackback ping. By using the POST method of HTTP, “title (blog article title)” “url (blog article permalink)” “excerpt (summary)” “blog_name (blog name)” Is to send.

  Returning to FIG. 8, the bulletin board server 2 that has received the trackback Ping converts the parameter of the trackback URL into the bulletin board parameter (step S110), and the contents (trackback information) of “title”, “url”, “excerpt”, and “blog_name” The bulletin board parameters are stored in the bulletin board DB 21 as posted contents (step S111). When the ID as shown in FIG. 10E is used for conversion to the bulletin board parameter, the parameter is acquired based on the ID from the parameter storage DB 28 (FIG. 2), and is stored in the bulletin board DB 21 after predetermined conversion.

  FIG. 13 is a sequence diagram showing a processing example when browsing a blog.

  In FIG. 13, when a blog browsing request is made from the blog viewer client 4D to the blog server 3 (step S201), the blog server 3 delivers a blog page (HTTP) to the client 4D (step S202).

  The tag embedded in the process of displaying the blog page is executed in the client 4D, and a blog module is requested from the bulletin board server 2 (step S203).

  The bulletin board server 2 acquires bulletin board parameters from the bulletin board DB 21 based on the posting ID (steps S204 to S206), generates a blog module from the acquired bulletin board parameters (step S207), and distributes it to the client 4D (step S208). As a result, the blog module is displayed in the blog page on the client 4D (step S209). FIG. 14 is a diagram showing an example of the blog screen, and shows a state where the blog module 45 is displayed in the blog page. The blog module complements the fact that parameter information when a trackback is submitted is not saved on the blog side.

<Summary>
The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the structural example of a bulletin board server. It is a figure which shows the example of bulletin board DB. It is a figure which shows the example of parameter storage DB. It is a figure which shows the operation | movement outline | summary of embodiment. It is a figure which shows the example of the track back from a blog to a bulletin board, and the link from a bulletin board to a blog. It is a figure which shows the example of the link from a bulletin board to a blog / detail page. It is a sequence diagram which shows the process example concerning a track back. It is a figure which shows the example of a track back URL production | generation screen. It is a figure which shows the example of track back URL. It is a figure which shows the example of a tag. It is a figure which shows the example of track back Ping. It is a sequence diagram which shows the process example at the time of blog browsing. It is a figure which shows the example of a blog screen.

Explanation of symbols

1 Network 2 Bulletin Board Server 21 Bulletin Board DB
211 Bulletin Board Master Table 212 Posting Data Table 213 Contributor Table 22 Bulletin Board Posting Unit 23 Trackback URL / Tag Generation Unit 24 Trackback Reception Unit 25 Trackback URL Analysis Unit 26 Posting Content Display Unit 27 Blog Module Distribution Unit 28 Parameter Storage DB
3 Blog server 4A-4D client

Claims (6)

Address generating means for generating an address as a trackback destination in response to a request from a client;
Trackback receiving means for receiving a trackback addressed to the address from another server;
Trackback analysis means for analyzing the received trackback and storing the posted content including the address of the server of the trackback source in the database;
Display means for causing the client to display the stored contents of the database in response to a request from the client;
A means for distributing the blog module generated from the posted content in response to the blog module request from the client,
The information presenting server, wherein the address generating means generates a tag for embedding a blog for acquiring the blog module when generating an address as a trackback destination. In the information presentation server according to claim 1,
The address generation means generates an address including information that is part of the posted content by the information presenting server and the posted content by the server of the trackback source. In the information presentation server according to claim 2,
The address generating means adds information as a parameter to the address as a part of the posted content by the information presenting server and the posted content by the trackback source server. In the information presentation server according to claim 1,
The address generation means stores the information posted by the information presentation server and the information that becomes a part of the content posted by the server of the trackback in the parameter storage database, and adds an ID for identifying the information as a parameter to the address. An information presentation server characterized by Generating a trackback destination address in response to a request from a client;
Receiving a trackback addressed to the address from another server;
Analyzing the received trackback and accumulating the posted content including the address of the trackback source server in the database;
Displaying the stored contents of the database on the client in response to a request from the client;
And a step of distributing the blog module generated from the posted content in response to the request of the blog module from the client,
The method for generating an address includes generating a blog embedding tag for acquiring the blog module when generating an address as a trackback destination. A function for generating an address as a trackback destination in response to a request from a client;
A function of receiving a trackback addressed to the above address from another server;
A function to analyze the received trackback and store the posted content including the server address of the trackback in the database,
A function to display the contents stored in the database in response to a request from the client;
In response to a request for a blog module from the client, the computer realizes the function of distributing the blog module generated from the posted content ,
An information presentation control program, wherein the address generating function generates a blog embedding tag for acquiring the blog module when generating an address as a trackback destination.

Images