JP5407874B2 - Blog posting image communication system, blog posting image communication method, server, program, storage medium - Google Patents

Description

  The present invention relates to a blog post image communication system and the like for communication between blog posters.

  Existing blog management systems usually have a text commenting function and a link trackback function. Blog authors (bloggers) use these functions to communicate with other blog authors and viewers.

In order to deepen such communication, there is a blog management program that makes it possible to search and link blogs related to blog authors' articles from a vast number of blogs on the Internet. (Patent Document 1)
The blog management program described in Patent Document 1 searches for blogs with similar article titles, image titles, and the like using search conditions based on similarity or matching of character strings.

JP2008-225696A

  On the other hand, with the spread of digital cameras and camera-equipped mobile phones, images are often added to blog articles. At present, images are used only to the extent that viewers comment on their impressions, and communication using the images themselves is not performed.

  The blog management program described in Patent Document 1 also uses the similarity or matching of character strings as a search condition, so even if the images posted on the blog are similar, a link between the blogs cannot be generated.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to provide a blog post image communication system that enables communication between blog posters using images.

In order to achieve the above-described object, the first invention is a blog post image communication system in which a server and a user terminal are connected via a network, wherein the server includes location information of a user's blog. And a usage registration database that stores the blog-specific identification information in association with each other, and a blog article page obtained from the location information of the user's blog stored in the usage registration database, and the usage described in the article page An image collecting means for collecting image data posted by a user, an image storage database for storing blog-specific identification information in association with the image data, and attribute information of the image data stored in the image storage database Image analysis means for calculating the similarity between the image data based on the attribute information The storage unit of the similar image data determined by the calculation unit and the similarity calculation unit to satisfy the similarity of the image data with a certain standard or more, and the location information of the blog from which the similar image data is collected, A blog post image communication system comprising: a first file held for each blog. By using the blog post image communication system according to the first invention, it is possible to automate a link with a blog posting a similar image. In addition, this makes it possible to collect images only from blogs registered for use. Collecting images without permission may cause copyright problems. In the present invention, images are collected only from the blog of the blog poster on the premise that the blog poster obtains consent from the blog poster at the time of use registration, so that a problem regarding the copyright does not occur.

  Further, the image collecting means acquires an update information file that provides update information of a blog article, accesses an blog article page described in the update information file, downloads the article page, and updates the update information file. The article page is searched using the character string in the article description tag in the file as the search character string, and the article from the block start tag that appears before the character string that matches the search character string to the corresponding block end tag It is desirable to save it as the body of the page. As a result, the body part of the blog article page can be specified, and advertisements that are not articles of the blog author can be excluded. Therefore, the similarity of the blog can be accurately determined.

  The image collecting means, when a part of the location information in the image location tag included in the body of the article page matches the location information of the blog, is specific to the blog as the image data posted by the user It is desirable to store it with identification information. Thereby, only the image posted by the user among the images posted on the article page can be stored. Depending on the blog management system, an image such as an advertisement may be posted in the article page. In the present invention, since the similarity is calculated using only the images posted by the user, the similarity of the blog can be accurately determined.

  The server further includes a second file that holds blog parts data and a third file that holds information for reading blog parts data, and displays the blog registered for use by the user terminal When the third file is called, the server acquires the location information of the blog that posts the similar image data and the similar image data from the first file together with the second file. Therefore, it is desirable to distribute to the user terminal. Thereby, it becomes possible to display the blog part including the similar image to which the link destination is set. The viewer can link to the blog that posted the similar image by clicking the similar image.

  In response to a user registration request from the user, the server registers the blog-specific identification information and the user's blog location information in association with the registration database, and includes the blog-specific identification information for the user. It is desirable to further include usage registration means for issuing part codes. This makes it possible to provide a similar image to a blog that has been registered for use.

According to a second aspect of the present invention, there is provided a blog post image communication method in which a server and a user terminal are connected via a network, wherein the server associates location information of a user's blog with identification information unique to the blog. The blog article page is acquired from the location information of the user's blog in the usage registration database stored, and the image data posted by the user described in the article page is collected, and the image data is blog-specific. Storing in the image storage database in association with the identification information, obtaining the attribute information of the image data stored in the image storage database, and calculating the similarity between the image data based on the attribute information A storage location of similar image data determined to satisfy a certain degree of similarity with the image data, And location information of collecting source blog similar image data, performs the steps of holding the first file for each blog, the server downloads the top page by accessing the user's blog, top The blog-specific identification information in the blog part code on the page is compared with the blog-specific identification information associated with the location information of the user's blog stored in the registration database. This is a blog post image communication method characterized in that collected image data is collected . By using the blog post image communication method according to the second invention, it is possible to automate links between blogs that post similar images. In addition, this makes it possible to collect images only from blogs registered for use. Collecting images without permission may cause copyright problems. In the present invention, images are collected only from the blog of the blog poster on the premise that the blog poster obtains consent from the blog poster at the time of use registration, so that a problem regarding the copyright does not occur.

A third invention is a server that stores user information and image data and distributes blog parts, a use registration database that stores and stores user blog location information and blog-specific identification information, An image collection means for acquiring an article page of a blog from the location information of the user's blog stored in the use registration database, and collecting image data posted by the user described in the article page; Image storage database for storing identification information and image data in association with each other, image analysis means for acquiring attribute information of the image data stored in the image storage database, similarity between the image data based on the attribute information Similarity calculation means for calculating the degree of similarity, and the similarity calculation means, the similarity between the image data and a certain standard or more And storage location of the similar image data determined as plus, and a collection source blog location information of the similar image data, comprising a first and a file to be stored for each blog, the image acquisition means, use Access the user's blog, download the top page, the blog-specific identification information in the blog part code on the top page, and the blog-specific information associated with the location information of the user's blog stored in the registration database The server is characterized by collating the identification information and collecting image data posted on the blog if they match . By using the server according to the third invention, it is possible to automate links between blogs that post similar images. In addition, this makes it possible to collect images only from blogs registered for use. Collecting images without permission may cause copyright problems. In the present invention, images are collected only from the blog of the blog poster on the premise that the blog poster obtains consent from the blog poster at the time of use registration, so that a problem regarding the copyright does not occur.

  A fourth invention is a program for causing a computer to function as a server according to the third invention. By using the program according to the fourth invention, it is possible to automate links between blogs that post similar images.

  A fifth invention is a computer-readable recording medium recording a program for causing a computer to function as a server according to the third invention. By using the recording medium according to the fifth aspect of the invention, it is possible to automate links between blogs that post similar images.

  According to the present invention, it is possible to provide a blog post image communication system or the like that enables communication between blog posters using images.

System configuration diagram showing the configuration of the blog post image communication system 101 Block diagram of server 105 The figure which shows an example of the display of the blog 301 Flow chart showing usage registration processing Diagram showing an example of blog parts code Flow chart showing image collection processing Flow chart showing similar image analysis processing Flow chart showing blog parts distribution processing Figure showing an example of links between blogs Figure showing an example of the similarity calculation table Diagram showing an example of RSS discovery Diagram showing an example of an RSS file The figure which shows an example of the source code containing an img tag

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

  The configuration of the blog post image communication system 101 according to the embodiment of the present invention will be described with reference to FIG. FIG. 1 is a system configuration diagram for explaining the overall configuration of an embodiment of the present invention.

  As shown in FIG. 1, the blog post image communication system 101 includes a plurality of user terminals 103 and a server 105. The user terminal 103 and the server 105 are communicably connected via the network 107.

The user terminal 103 is a terminal for a user to post a blog and for a viewer to browse the blog. The user terminal 103 includes, for example, a CPU that controls various devices, a RAM and storage unit that stores various data, an input device such as a keyboard and a mouse, a display device such as a liquid crystal display, and a communication interface with the network 107. It is also possible to capture image data. The user terminal 103 is not limited to a computer, and may be a mobile phone with a camera.
The server 105 stores, for example, registration information from the user, has a database that stores image data posted on the blog, and transmits a blog part code, a storage location of a similar image, and the like to the user terminal 103. . The server 105 is a computer having a CPU for controlling various devices, a RAM and storage unit for storing various data, an input device such as a keyboard and a mouse, a display device such as a liquid crystal display, and a communication interface with the network 107. .

FIG. 2 is a block diagram of the server 105.
The server 105 includes a use registration database 201 and an image accumulation database 203, and holds an xml (Extensible Markup Language) file 205, a swf (ShockWave Flash) file 207, and a js (Java (registered trademark) Script) file 209 held for each blog. And a storage unit (not shown) for storing and the like.

The usage registration database 201 is a database that stores a URL (Uniform Resource Locator) of a blog registered for usage and a blog identification ID that is identification information unique to the blog.
The image storage database 203 is a database that stores image data posted to a blog registered for use and a blog identification ID in association with each other.
The xml file 205 is a file for each blog registered for use, and is a blog identification ID, a storage location of image data determined to be similar by a similarity calculation function 217 described later, and a collection source of image data. Save the URL of the blog.
The swf file 207 is a file describing data of blog parts to be displayed on the blog.
The js file 209 is a file that holds information for reading blog parts data.

The server 105 also includes a use registration function 211, an image collection function 213, an image analysis function 215, a similarity calculation function 217, and a blog parts distribution function 219.
In response to a usage registration request from the user, the usage registration function 211 associates the URL of the user's blog with the blog identification ID, registers it in the usage registration database 201, and transmits the blog part code to the user terminal 103. To do.
The image collection function 213 accesses the URL of the blog in the usage registration database 201, collects images posted on the blog, and stores the images in the image accumulation database 203.
The image analysis function 215 reads the image data stored in the image accumulation database 203, analyzes the shape, color tone, and the like, and acquires attribute information of the image data.
The similarity calculation function 217 compares the attribute information such as shape and color tone acquired by the image analysis function 215 to calculate the similarity between the images, and stores the information on the similar images in an xml file.
The blog parts distribution function 219 obtains information for displaying blog parts from the swf file 207 and the xml file 205 by using the js file 209 when the viewer browses a blog that has been registered for use. To the user terminal 103.

FIG. 3 is a screen diagram illustrating an example of the top page of the blog displayed by the user terminal 103.
The blog top page 301 includes a blog title 303, an advertisement area 305 including an advertisement image 307, a body 309 describing an article of the blog, an image 311 displayed in the body, an advertisement 313 displayed in the body, and the like. .
In addition, there is a sidebar 315 on the right side of the body. The sidebar 315 includes a blog user profile 317, a link 319 to an article page described in the past, and a blog part 321. Images 323 and the like posted on the blog.

The top page 301 of the blog is described in html (HyperText Makeup Language).
The blog title 303 is a blog title, and the advertisement area 305 is an area for displaying an advertisement of a company providing the blog service. An advertisement image 307 may be displayed in the advertisement area 305.
The blog text 309 is an area for displaying the latest article. In the text 309, posted image data 311 such as photographs and illustrations may be displayed. Depending on the content of the text, the advertisement 313 may be displayed in the text 309, and an image that is not posted by the user may be used for the advertisement 313.

  On the right side of the top page 301, the user terminal 103 displays a side bar 315 and displays information related to the text of the blog. The profile 317 displays self-introduction information of the blog user. The latest article is displayed in the body 309 of the blog, but the article title is displayed side by side in the past article link area 319 of the sidebar 315 for linking to an article page written in the past. When the blog viewer clicks the article title in the link area 319, the user terminal 103 displays a past article page.

  Further, a blog part 321 is displayed on the side bar 315. An image determined by the server 105 to be similar to an image posted on the blog is pasted on the blog part 321. There may be one image or a plurality of images pasted on the blog part 321. Further, a plurality of images may be displayed at the same time, or may be displayed by replacing with time. When the image of the blog part 321 is clicked, it is possible to link to the blog where the image is posted.

Next, the use registration process when using the blog post image communication system 101 will be described with reference to FIG.
FIG. 4 is a flowchart showing the use registration process.

When the user clicks the URL for system usage registration by the user, the user terminal 103 accesses the URL of the usage registration page (S401). The server 105 receives the usage registration page acquisition request and transmits a usage registration screen to the user terminal 103 (S403). The user terminal 103 displays a use registration screen and transmits the URL of the blog input by the user to the server 105 (S405). The server 105 assigns a blog identification ID to the received URL of the blog and registers it in the usage registration database 201 (S407), and transmits a blog part code including the blog identification ID to the user terminal 103 (S409). The user terminal 103 sets the received blog part code as a blog template (S411). As a result, the blog identification ID is included in the source code (html file) of the blog registered for use, and the use registration can be identified by checking the source code (html file).
The server 105 performs use registration processing by online processing in response to a registration request from the user.

The blog part code set for the user's blog is shown in FIG.
The blog part code includes a location 501 of a js file having information for distributing the blog part, and a blog identification ID 503 determined for each blog registered for use. In the example shown in FIG. 5, the location 501 of the js file is “http://abc.blog.hoge.com/blogparts/xyz.js”, and the blog identification ID 503 is “A”. By having a blog part code including the blog identification ID 503 on the top page of the blog, it is determined that the blog is registered for use.

Next, the image collection process performed by the server 105 will be described with reference to FIG.
FIG. 6 is a flowchart showing the image collection process.

  The server 105 reads the URL of the blog registered in the usage registration database 201 (S601), accesses the URL, and downloads the top page of the blog. The blog identification ID is read out from the html source code of the top page and collated with the blog identification ID registered in the usage registration database 201 (S603). When collation is successful (Yes in S605), RSS (Rich Site) (Summary) The RSS of the blog is downloaded using the auto-discovery function (S607). RSS is an xml file in which history information of blog articles is described.

The server 105 accesses the URL of the blog article page described in the RSS and downloads the article page (S609). The article page is an html file.
The server 105 compares the character string in the description tag (article description tag) indicating the article description in the RSS with the article page (S611). Specifically, the server 105 performs a character string search of the article page using the character string in the description tag as a search character string, and a div tag (block start) indicating the start of a block that appears before the character string that matches the search character string. Tag) is specified, and the content within the div tag, that is, up to the corresponding / div tag (block end tag) is stored in the storage unit or RAM of the server 105 as the body of the blog (S613).
The server 105 performs the processing from S609 to S613 for all the article pages described in the RSS.
If the verification of the blog identification ID has failed (No in S605), the process skips to S615.

The server 105 repeatedly performs the processing from S601 to S613 for all blog URLs registered in the usage registration database 201 (No in S615). When the server 105 completes the process of specifying the text for all the registered blog URLs (Yes in S615), the server 105 selects an img tag indicating the location of the image from the saved text (S617).
If the beginning of the URL of the src attribute (image location information) indicating the storage location of the image in the img tag (image location tag) matches the blog URL (Yes in S619), the server 105 displays the image in the img tag. The file is recognized as an article image of a blog, is assigned a blog identification ID, and is stored in the image accumulation database 203 (S621). If the beginning of the URL of the src attribute indicating the image storage location matches the blog URL, it can be said that the image is an original image posted by the user.

If the beginning of the URL of the src attribute does not match the blog URL (No in S619), the process of S621 is skipped. The server 105 performs the processing from S617 to S621 for all the stored blog texts (No in S623), and when all the img tags are completed (Yes in S623), the image collection processing ends.
The server 105 performs image collection processing by batch processing.

Subsequently, similar image analysis processing in which the server 105 performs image analysis of the shape and color tone of each image data stored in the image storage database 203 and calculation of the similarity between images will be described with reference to FIG.
As attribute information for similarity calculation, shape, color tone, shooting date and time, shooting location, and the like are used.
The shape indicates the shape of the main subject in the image, and the shape information is acquired by detecting the contour of the subject. The color tone is the color tone most frequently used in the area ratio within the contour of the subject. For example, the color tone is digitized using an RGB color model. The shooting date and time is the date when the image was shot, and the shooting location is, for example, GPS (Global Positioning System) information of the shooting location. The shooting date and time and the shooting location are obtained from Exif (Exchangeable Image File) information to which image data is added.
Note that all of the above-described information may be used as attribute information for similarity calculation, or only a part of the information may be used. Further, information other than the information described above may be used.

FIG. 7 is a flowchart showing similar image analysis processing.
The server 105 selects one image from the image storage database 203 (S701), and extracts the shape of the subject of the image (S703). Next, the color tone of the image is calculated (S705). Further, the shooting date and time when the image held by the image data is shot and the shooting location of the image data are acquired (S707), and the acquired attribute information is associated with the image data and stored in the storage unit (S709).

  The server 105 performs the processing from S703 to S709 on all the images stored in the image accumulation database 203 (No in S711). When the storage of the attribute information is completed for all the images (Yes in S711), the similarity between the images is calculated.

The server 105 selects the first image from the image storage database 203 (S713), and similarly selects the second image (S715). At this time, an image having the same blog identification ID as the first image is not selected as the second image. Also, a combination of images that have already been compared is not selected.
When the server 105 compares the attribute information of each of the first image and the second image and determines that there is a similarity equal to or higher than a certain standard (Yes in S717), the server 105 matches the blog identification ID of the first image. In the xml file 205, the storage location of the second image and the URL of the blog from which the second image is collected are written. At the same time, the storage location of the first image and the URL of the blog from which the first image is collected are written into the xml file 205 that matches the blog identification ID of the second image (S719).

  In order to detect an image similar to the first image, the server 105 selects the next second image and performs the processing of S717 and S719 (No in S721). When similarities with all images have been calculated (Yes in S721), the next first image is selected, and the processing from S715 to S721 is repeated (No in S723). At this time, the first image and the second image are selected so that the combination of the already compared images is not selected again.

When the selection of all the first images is completed, that is, when the combination of all the images is completed (Yes in S723), the server 105 ends the similar image analysis process.
The server 105 performs similar image analysis processing by batch processing.

Next, a process until the user terminal 103 displays a blog part will be described with reference to FIG.
FIG. 8 is a flowchart showing the blog parts distribution process.

  The user terminal 103 accesses the URL of the registered blog and downloads the top page of the blog (S801). The user terminal 103 executes a script in the source code of the top page (S803), and transmits a blog identification ID to the server 105 for a blog part data transmission request. The server 105 acquires the xml file 205 that matches the received blog identification ID (S805), and transmits the acquired xml file 205 and the swf file 207 that is a data file of the blog part to the user terminal 103. The user terminal 103 displays the blog part 321 on the blog sidebar 315 based on the received swf file 207, and further displays similar image data from the storage location of the similar image described in the received xml file 205. The acquired image is displayed, and a similar image 323 of another blog is displayed in the blog part and a URL link of the blog where the similar image is posted is pasted (S809).

FIG. 9 shows an example of a link between blogs.
901 is a blog of a blogger A who is a user, 902 is a blog of a blogger B, and 903 is a top page of a blog of a blogger C. Blogger A pastes the blog part on the blog by registering for use.
When the latest article and a new image 311a are posted on A's blog 901, and the server 105 performs image collection processing by batch processing, the server 105 displays the storage location of the image 311a and the URL of A's blog as an image. Store in the accumulation database 203. Similarly, when the latest article and a new image 311b are posted on B's blog 903, the storage location of the image 311b and the URL of B's blog are stored in the image storage database 203. Similarly, for the C blog 905, the storage location of the image 311c and the URL of the C blog are stored in the image storage database 203.
The server 105 performs similarity calculation processing by batch processing, selects the image 311a as the first image, selects the image 311b as the second image, and calculates the similarity. As a result, it is determined that the similarity is high, the storage location of the image 311b and the URL of the B blog 903 are stored in the blog xml file of A, and the storage location of the image 311a and the A blog are stored in the blog file of B blog. Save the URL of your blog.
Next, the image 311c is selected as the second image, and the similarity is calculated. As a result, it is determined that the similarity does not exceed a certain standard, and the next image is selected.
The server 105 selects the image 311b as the first image, selects 311c as the second image, and calculates the similarity. As a result, it is determined that the degree of similarity is high, and the storage location of the image 311b and the URL of the B blog 903 are stored in the C blog xml file, and the storage location of the image 311c is stored in the B blog xml file. Save the URL of C's blog.
That is, the storage location of the image 311a and the URL of the blog A, and the storage location of the image 311c and the URL of the blog C are stored in the xml file of the blog B.

When the user terminal 103 next displays A's blog 901, the script is executed, and the blog identification ID 503 is transmitted to the server 105. The server 105 performs blog parts display processing by online processing, and transmits the xml file and swf file of A's blog to the user terminal 103. Then, the user terminal 103 acquires the data of the image 311b from the storage location of the image 311b described in the received xml file, and displays the blog part of the blog of A. When the image 311b is clicked, the URL link of the blog from which the image 311b is collected is pasted so as to access the blog B.
When the user terminal 103 displays the B blog 903, the server 105 performs the same processing, displays the image 311a and the image 311c on the B blog part, and links to the A blog 901 respectively. Put a link to C's blog 905.
When the user terminal 103 displays the C blog 905, the image 311b is displayed on the C blog part, and a link to the B blog 903 is pasted.
In this way, links between blogs of A, B, and C can be pasted.

  Next, a similarity calculation method will be described using the similarity calculation table shown in FIG.

  For example, the server 105 selects the image A as the first image and the image B as the second image. The similarity between the shapes of the images A and B greatly exceeds a certain standard, and the similarity of the color tone exceeds the certain standard. The shooting date and the shooting location of the two images are different. In this case, the server 105 determines that the image A and the image B are similar images.

  Next, the server 105 selects the image A as the first image and selects the image B as the second image. Both the similarity of the shapes of the images A and C and the similarity of the color tone are below a certain standard, and the shooting date and the shooting location of the two images are different. In this case, the server 105 does not regard the images A and C as similar images.

Next, the server 105 selects the image B as the first image and selects the image C as the second image. It is assumed that the similarity of the shapes of the images A and C and the similarity of the color tone are both below a certain standard, but the shooting dates of the two images are within a certain period and the shooting locations are the same. In this case, the server 105 determines that the image A and the image C are similar images.
The determination of whether or not they are similar may be performed by weighting the similarity of a plurality of attribute information.

Next, FIG. 11 shows an example of RSS auto-discovery.
FIG. 11 shows the html source code of the top page of A's blog, and 1101 is the source code designating the RSS file of A's blog.
In order to make A's blog correspond to the auto-discovery function, 1101 is described in the head tag of the source code of the top page. 1101 is automatically described by each blog management system.

FIG. 12 is an example of an RSS file.
In the xml source code of the RSS file, a word describing the contents of the blog of A is described in a description tag that is a tag explaining the contents of the article. Reference numeral 1103 denotes source code including a description tag.
Reference numeral 1105 describes the URL of the article page so far of A's blog.
The RSS file is automatically created by each blog management system.

FIG. 13 is an example of the source code of the img tag in the blog article page.
The img tag is a tag indicating the location of an image, and indicates a storage location of image data such as photos and illustrations posted on a blog. In order to acquire only the image posted by the user, the server 105 determines whether or not the beginning part of the URL of the src attribute in the img tag matches the URL of the registered blog. If so, the image is determined to be an image posted by the user. Sources that do not match include advertisement images and similar images included in blog parts.

As described above, according to the embodiment of the present invention, a similar image can be pasted on a blog, and a link with the blog where the similar image is located can be easily pasted. A similar image is an image posted by a user on his / her blog, and advertisement images, blog images that are not registered for use, and the like are excluded.
In the embodiment of the present invention, links between blogs are realized. However, the present invention is not limited to this, and for example, use in a social network service is also possible.
Moreover, according to the embodiment of the present invention, a blog post image communication system can be constructed independently of the blog management system. In particular, in the embodiment of the present invention, since it does not depend on the specification of a specific blog management system, a link can be realized between blogs managed by different blog management systems.

  The preferred embodiment of the blog post image communication system according to the present invention has been described above with reference to the accompanying drawings, but the present invention is not limited to such an example. It will be apparent to those skilled in the art that various changes or modifications can be conceived within the scope of the technical idea disclosed in the present application, and these naturally belong to the technical scope of the present invention. Understood.

101 ......... Blog-posted image communication system 103 ......... User terminal 105 ......... Server 201 ......... Use registration database 203 ......... Image storage database

Claims (9)

A blog post image communication system in which a server and a user terminal are connected via a network,
The server
A registration database that stores the location information of the user's blog in association with the identification information unique to the blog;
An image collecting means for acquiring an article page of a blog from location information of a user's blog stored in the use registration database, and collecting image data posted by the user described in the article page;
An image storage database for storing blog-specific identification information and the image data in association with each other;
Image analysis means for acquiring attribute information of the image data stored in the image storage database;
Similarity calculating means for calculating the similarity between the image data based on the attribute information;
The storage unit for storing similar image data determined by the similarity calculation unit to satisfy the similarity with the image data above a certain standard and the location information of the blog from which the similar image data is collected are stored for each blog. A first file to
Equipped with a,
The image collection means accesses the user's blog, downloads the top page, and identifies the blog-specific identification information in the blog part code on the top page and the location information of the user's blog stored in the use registration database. The blog post image communication system is characterized in that image data posted on the blog is collected if the identities are matched with the identification information unique to the blog and matched . The image collection means acquires an update information file that provides update information of a blog article, accesses a blog article page described in the update information file, downloads the article page, and stores the update information file in the update information file. The article page is searched using the character string in the article description tag as a search character string, and from the block start tag that appears before the character string that matches the search character string to the corresponding block end tag, The blog post image communication system according to claim 1 , wherein the blog post image communication system is stored as a text. The image collecting means, when a part of the location information in the image location tag included in the body of the article page matches the location information of the blog, is specific to the blog as the image data posted by the user The blog post image communication system according to claim 2 , wherein identification information is given and stored. The server further includes a second file that holds data of blog parts, and a third file that holds information for reading blog parts data,
When the third file is called when the user terminal displays a registered blog, the server, together with the second file, sends the similar image data and the similar image from the first file together with the second file. The blog post image communication system according to claim 1, wherein location information of a blog on which image data is posted is acquired and distributed to the user terminal.   In response to a user registration request from the user, the server registers the blog-specific identification information and the user's blog location information in association with the registration database, and includes the blog-specific identification information for the user. The blog post image communication system according to claim 1, further comprising usage registration means for issuing a part code. A blog post image communication method in which a server and a user terminal are connected via a network,
The server
The article described in the article page is obtained by acquiring a blog article page from the blog location information of the user registration database that stores the blog location information and the blog-specific identification information in association with each other. Collecting image data posted by and storing the image data in an image storage database in association with blog-specific identification information;
Obtaining attribute information of the image data stored in the image storage database;
The similarity between the image data is calculated based on the attribute information, the storage location of the similar image data determined to satisfy the similarity with the image data above a certain standard, and the blog from which the similar image data is collected Storing the location information in the first file for each blog,
The execution,
The server accesses the user's blog, downloads the top page, and associates the identification information unique to the blog in the blog part code on the top page with the location information of the user's blog stored in the usage registration database. The identification information peculiar to a given blog is collated, and if they match, image data posted to the blog is collected, and the blog post image communication method is characterized. A server that stores user information and image data and distributes blog parts,
A registration database that stores the location information of the user's blog in association with the identification information unique to the blog;
An image collecting means for acquiring an article page of a blog from location information of a user's blog stored in the use registration database, and collecting image data posted by the user described in the article page;
An image storage database for storing blog-specific identification information and the image data in association with each other;
Image analysis means for acquiring attribute information of the image data stored in the image storage database;
Similarity calculating means for calculating the similarity between the image data based on the attribute information;
The storage unit for storing similar image data determined by the similarity calculation unit to satisfy the similarity with the image data above a certain standard and the location information of the blog from which the similar image data is collected are stored for each blog. A first file to
Equipped with a,
The image collection means accesses the user's blog, downloads the top page, and identifies the blog-specific identification information in the blog part code on the top page and the location information of the user's blog stored in the use registration database. A server that collects image data posted on a blog when the identification information is matched with blog-specific identification information associated with the blog . A program for causing a computer to function as the server according to claim 7 . A computer-readable recording medium recording a program for causing a computer to function as the server according to claim 7 .

Images