JP2008198008A - Feed storage system, feed storage method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To construct a communication infrastructure for circulating and distributing feed. <P>SOLUTION: A container resource common to members stores a common specification feed containing feed delivery control data for determining the reproduction of metadata of a website (such as a web page and a blog) and a member who receives an object of delivery according to website designation by the member in a database apparatus on a server device. A service container provided at each member stores the feed containing a URL of common specification feed, and the reproduction of metadata contained in the common specification feed on a database apparatus in one of the server device, an Internet connection device and a radio communication apparatus. In a user portal provided at each member, the feed is displayed by the service container which stores the feed based on the feed delivery control data. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a feed storage system, and more particularly to a feed storage system for circulating and distributing RSS feeds.

  Currently, RSS (Rich Site Summaries (also known as Real Simple Syndication) or RDF Site Summaries) is attracting attention as a new medium following Web pages (Web sites) and e-mails.

  RSS is an XML-based format that describes metadata such as Web page headings and summaries in a structured manner, and is mainly used to publish page update information. Web pages that support RSS provide RSS data called RSS feeds. A feed is information described by metadata on a format such as RSS or Atom provided from a Web page. A feed described in the RSS format is called an RSS feed.

  An RSS reader is known as software for browsing the RSS feed. There are two types of RSS readers: an application type that is installed on a PC (personal computer) and an online type that uses a service on the Internet that manages RSS distribution. The RSS reader circulates the web page, receives the update information in the RSS format, and displays it in the form of a link list. For example, RSS information of a specified page is automatically downloaded at regular intervals, and when there is an update, a link to an article is displayed to notify the user. When the link is clicked, a web browser window opens and the target article is displayed. Also for RSS feeds, there are crawlers (search robots) similar to Web pages, and RSS feeds may be collected periodically.

  Furthermore, the number of prominent portal sites, blogs, and news sites that support RSS is gradually increasing.

  As described above, the use and spread of RSS at the user level are progressing, and business use such as advertisement distribution and marketing using RSS is also expected.

As a related technique, Japanese Unexamined Patent Application Publication No. 2006-252227 (Patent Document 1) discloses an Internet WEB page update information (headline summary, etc.) real-time distribution supply system.
In this conventional technology, when an Internet WEB page can create RSS data, the RSS data is supplied and distributed to a portal site (complex commercial WEB site) or the like via an RSS server in almost real time, and the latest RSS data is used. The latest update information on the WEB page can be browsed. If the Internet WEB page cannot create RSS data, the RSS server connects to the WEB site every minute, creates RSS data, supplies it to a portal site (commercial commercial WEB site), etc., distributes the latest The latest update information on the WEB page can be browsed with RSS data.

Japanese Patent Laying-Open No. 2006-316278 (Patent Document 2) discloses an information generation apparatus.
The information generation device includes a drop reception device that receives a drop event of an item dragged by a user, a data reading device that acquires data from an item, a feed generation device that generates a feed of this data from the acquired data, A feed registration device for registering a feed generated by the feed generation device.

JP-A-2006-221388 (Patent Document 3) discloses an advertisement distribution system.
In this prior art, an RSS feed for advertisement created for advertisement is transmitted from each advertiser server to the management server, the management server distributes the RSS feed for advertisement to each predetermined affiliate server, and the affiliate server An advertisement based on the RSS feed for advertisement is displayed on the information terminal device of the net visitor. This RSS feed is XML summary data that describes metadata such as website headings and summaries in a structured manner, and is text data that is enumerated in time series, so that its contents can be easily updated as needed. For this reason, the advertisement in each advertiser can be distributed in real time to the website of each affiliate.

  However, under the present circumstances, RSS, like Web pages, does not have an active approach to viewers and relies on search engine hits.

  Even if a page is generated by CGM (Consumer Generated Media) such as Blog (blog) or SNS (Social Networking Service), only one-way access from a viewer is possible.

  Furthermore, even if the Web page is updated, there is no notification means to anyone other than the viewer who has browsed before and is interested.

JP 2006-252227 A JP 2006-318278 A JP 2006-221388 A

An object of the present invention is to provide a feed storage system serving as a communication infrastructure (infrastructure) for distributing a public notice or a generation notice.
Another object of the present invention is to provide a feed storage system that provides a two-way communication infrastructure for Web contacts.

  In the following, means for solving the problem will be described using the numbers used in [Best Mode for Carrying Out the Invention] in parentheses. These numbers are added to clarify the correspondence between the description of [Claims] and [Best Mode for Carrying Out the Invention]. However, these numbers should not be used to interpret the technical scope of the invention described in [Claims].

  The feed storage system of the present invention includes a container resource (20) for storing a common specification feed including metadata of a website and feed distribution control data for determining a member to be distributed, and for each member. A service container for providing a feed to a user portal (user page) provided for each member, storing a feed including a URL of the common specification feed and a copy of metadata included in the common specification feed. (40) and a feed generation engine (10) that creates a common specification feed and stores it in a container resource, creates a feed, and stores it in a service container (40) of a member to be distributed based on the feed distribution control data It comprises. The website metadata mainly indicates metadata included in the RSS feed of the website. However, when there is no RSS feed on the website, “data corresponding to metadata” extracted from the website itself is indicated. Web sites indicate existing and newly created Web pages, blogs, news sites, and the like.

  When the feed generation engine (10) determines the update of the website by comparing the update information of the website and the update information of the common specification feed, the feed generation engine (10) updates the common specification feed. At this time, the feed generation engine (10) automatically scans the website, checks the date and time when the website was created or updated, and the size of the page of the website, and looks for an update. Alternatively, when the creator of the website updates the website, the feed generation engine (10) is activated to acquire the metadata of the website, and if the RSS feed does not exist, the metadata is manually acquired. Then, the metadata of the common specification feed is updated, and each item of the feed delivery control data is changed. Here, the update information indicates “Date (date and time)”. For example, when the RSS feed of the website exists, “Date” included in the RSS feed is indicated, and when the RSS feed of the website does not exist, “date” included in the source code of the website is indicated. When “date” is not included in the website source code, the website metadata, the position (layout) in which a predetermined tag or keyword included in the website source code is described, or the website page Can be used as update information. In this case, information related to “metadata”, “layout”, and “data size” of the Web site before the update is stored in the common specification feed, and the “metadata”, “layout”, “ The information regarding “data size” is compared to determine whether to update the website.

  The feed generation engine (10) creates a common specification feed based on the RSS feed of the website if the website has an RSS feed, and from the website itself if the website does not have an RSS feed. Get the metadata used for the feed and create a common specification feed. The metadata used for the RSS feed indicates “URL”, “Title”, “Desc (Description)”, and “Date”.

  The common specification feed includes metadata used for the RSS feed of the website, an attribute code indicating whether the website is Web 1.0 or Web 2.0, and the genre and category of the website, which constitute the feed distribution control data. Information indicating a user device suitable for browsing the website, position information related to the contents of the website, a feed copy counter that specifies the upper limit of the number of feeds delivered, and a feed delivery time Information, a URL of a QR code image obtained by converting a URL uniquely indicating the location information of the common specification feed, and information indicating a user profile (region, age, gender, hobby, occupation) to which the feed is to be distributed .

  The feed generation engine (10) determines a common specification feed in the container resource (20) based on the feed distribution control data designated for each member, and if the distribution condition is met, the metadata and the common specification used for the RSS feed. The feed URL is acquired to create a feed, which is stored in the service container (40) of the member to be distributed.

  The feed generation engine (10) converts the URL uniquely indicating the location information of the common specification feed in the container resource (20) into a QR code image, and stores the QR code image together with the common specification feed in the container resource (20). To do.

  The feed storage system of the present invention may further include a feed update engine (30) for updating the feed when the update information of the common specification feed and the update information of the feed are compared to determine the update of the common specification feed. . The update information is basically as described above, but here, the update information may be a common specification feed and a date when the feed is created or updated.

Common specification feed and system configuration of storage device that stores feed 1) Container resource (server device), service container (server device)
2) Container resource (server device), service container (Internet connection device)
3) Container resource (server device), service container (wireless communication device)
The case can be considered.
That is, the container resource may be a server device, and the service container may be a server device, an Internet connection device, or a wireless communication device. Here, the container resource and the service container indicate a database device (storage device) included in each device. In the case of a container resource (server device) and a service container (server device), the case where both the container resource and the service container exist in the same server device is included. The Internet connection device is a communication device compatible with wired communication that can be connected to the Internet. For example, relay devices such as personal computers (PCs), televisions compatible with the Internet, routers, and switching hubs are conceivable. The wireless communication device is a wireless communication compatible communication device that can be connected to the Internet. The wireless communication device is preferably a mobile phone. However, actually, it is not limited to a mobile phone. For example, a wireless LAN switch, a wireless IP phone terminal, or a wireless communication compatible communication apparatus such as a PDA (Personal Digital Assistant) or a portable music player may be used.

  The feed storage method of the present invention includes a step of creating a common specification feed including metadata of a website and feed distribution control data for determining members to be distributed and storing them in a container resource (20); Creating a feed including the URL of the common specification feed and a copy of the metadata included in the common specification feed and storing the feed in the service container (40) of the member to be distributed based on the feed distribution control data; Providing a feed to a member's user portal (user page).

  The feed storage method of the present invention may further include a step of updating the common specification feed when update information is determined by comparing the update information of the website and the update information of the common specification feed. At this time, the feed generation engine (10) automatically scans the website, checks the date and time when the website was created or updated, and the size of the page of the website, and looks for an update. Alternatively, when the website creator updates the website, the feed generation engine (10) is activated to acquire the metadata of the website, and if the RSS feed does not exist, the metadata is manually acquired. Then, the metadata of the common specification feed is updated, and each item of the feed delivery control data is changed. Here, the update information indicates “Date (date and time)”. For example, when the RSS feed of the website exists, “Date” included in the RSS feed is indicated, and when the RSS feed of the website does not exist, “date” included in the source code of the website is indicated. When “date” is not included in the website source code, the website metadata, the position (layout) in which a predetermined tag or keyword included in the website source code is described, or the website page Can be used as update information. In this case, information related to “metadata”, “layout”, and “data size” of the Web site before the update is stored in the common specification feed, and the “metadata”, “layout”, “ The information regarding “data size” is compared to determine whether to update the website.

  The feed storage method of the present invention determines the common specification feed in the container resource (20) based on the feed distribution control data designated for each member, and if it matches the distribution conditions, the metadata used for the RSS feed and the common specification are used. In some cases, the method further includes a step of acquiring a feed URL to create a feed and storing the feed in a service container (40) of a member to be distributed.

  The feed storage method of the present invention converts a URL that uniquely indicates the location information of a common specification feed in a container resource (20) into a QR code image, and stores the QR code image together with the common specification feed in the container resource (20). In some cases, the method further includes the step of:

  When the feed storage method of the present invention compares the update information of the common specification feed with the update information of the feed and determines the update, the feed is stored in the service container (40) of the member to be distributed based on the feed distribution control data. There may be a further step of updating the feed. The update information is basically as described above, but here, the update information may be a common specification feed and a date when the feed is created or updated.

  The program of the present invention causes a computer to execute any one of the above feed storage methods.

  It becomes possible to circulate and distribute the feed on the network.

A first embodiment of the present invention will be described below with reference to the accompanying drawings.
As shown in FIG. 1, the feed storage system 100 of the present invention includes a feed generation engine 10, a container resource 20, a feed update engine 30, and a service container 40.

  The feed storage system 100 provides a service for members using an RSS feed. For example, it may be an ASP server or a PING server. The ASP server starts an application on the server and provides the processing result to the user via the network. The PING server notifies the user of the update of the RSS feed by transmitting a PING (Packet Internet Grouper). However, in practice, the feed storage system 100 is not limited to a single server. For example, a system in which each component is distributed to a plurality of servers may be used.

  The feed generation engine 10 creates a common specification feed based on the original page by a member such as a creator of a new content such as a company (corporate) or a viewer of the content, and stores it in the container resource 20. As an example of the original page, a blog (blog) or a web page can be considered. However, actually, it is not limited to these examples. The common specification feed will be described later.

  At this time, if the original page has an RSS feed, the feed generation engine 10 generates a common specification feed based on the RSS feed of the original page. If the original page does not have an RSS feed, metadata used for the RSS feed is acquired (extracted) from the original page to generate a common specification feed. The metadata used for the RSS feed indicates “URL”, “Title”, “Desc”, and “Date”. “URL”, “Title”, “Desc”, and “Date” are XML tags, respectively. “URL” indicates location information of the original page. “Title” indicates the title of the resource. “Desc (Description)” indicates an outline description of the contents and functions of the resource. “Date” indicates the creation date of the original page.

  The feed generation engine 10 also copies the metadata of the Web site included in the common specification feed and the URL of the common specification feed from the service container 40 provided for each member. It is stored as a feed in the service container 40 of the member who is the browsing target. The partial information indicates “URL”, “Title”, “Desc”, and “Date”. Whether or not the member is a person to be browsed is determined based on whether or not there is a request for browsing from the member and the user profile (region, age, gender, hobby, occupation) input at the time of member registration.

  Also, the feed generation engine 10 converts a URL uniquely indicating the location information of the common specification feed in the container resource 20 into a QR code image, and stores the QR code image in the container resource 20 together with the common specification feed. When the delivery time (publication time) is specified for the common specification feed, at the time when the delivery time comes, a copy of the metadata of the Web site included in the common specification feed and the URL of the common specification feed are provided. Store in container 40.

  Furthermore, the feed generation engine 10 compares the date of the original page such as a blog (blog) or a web page with the “Date” in the cache (container resource 20) as needed based on the common specification feed stored in the container resource 20. Scan. That is, the update information of the original page is compared with the update information of the common specification feed. In this way, the feed generation engine (10) automatically scans the original page, checks the date and time when the original page was created or updated, and the size of the original page, and looks for an update. Alternatively, when the creator of the original page updates the original page, the feed generation engine (10) is activated to acquire the metadata of the original page, and if the RSS feed does not exist, the metadata is manually acquired. Then, the metadata of the common specification feed is updated, and each item of the feed delivery control data is changed. Here, the update information indicates “Date (date and time)”. For example, when the RSS feed of the original page exists, “Date” included in the RSS feed is indicated, and when the RSS feed of the original page does not exist, “Date” included in the source code of the original page is indicated. When “date” is not included in the source code of the original page, the metadata of the original page, the position (layout) of the specified tag or keyword included in the source code of the original page, and the size of the original page It is also possible to use (data size) as update information. In this case, information related to the “metadata”, “layout”, and “data size” of the original page before the update is stored in the common specification feed, and the “metadata”, “layout”, “ The information on “data size” is compared to determine whether the original page is updated. At this time, if the update of the original page is determined, “URL”, “Title”, “Desc”, and “Date” of the common specification feed in the container resource 20 are updated.

  The feed generation engine 10 corresponds to the update information of the original page of the container resource 20 when the original page does not exist when scanned or when the original page has not been updated for a predetermined period (for example, one month). Delete the common specification feed. If it is considered that there is a problem if it is deleted immediately, if the original page does not exist or has not been updated when scanning again after waiting for a predetermined period (for example, one week), delete it. Also good.

  The container resource 20 is a storage device for storing the original page in the form of a common specification feed by a member such as a creator of a new content such as a company or a viewer of the content, and the stored common specification feed includes a plurality of members. (Everyone can do it). That is, it functions as a cache.

  The feed update engine 30 compares and scans the update of “Date” of the common specification feed in the container resource 20 based on the “Date” of the feed stored in each service container 40 for each member. That is, the update information of the common specification feed is compared with the update information of the feed. At this time, if the update of the common specification feed is confirmed, the “URL”, “Title”, “Desc”, ““ of the feed in the service container 40 of the member to be distributed based on the feed distribution control data in accordance with the distribution time. Update “Date”. The feed update engine 30 is posted and activated when the user portal is opened, and automatically updates the service container 40. The user portal is a Web page provided for each member. Further, the feed update engine 30 deletes the corresponding feed in each service container 40 when the common specification feed is deleted.

  The service container 40 (40-i, i = 1 to n: n is the number of members) is a storage device that can be used by the member who registered the common specification feed based on the original page, and the container resource 20 has the common specification feed. When stored, the metadata copy of the Web site included in the common specification feed and the URL of the common specification feed are stored as a feed. Each member is provided with a user portal for using the service. At this time, the feed stored in the service container 40 is displayed as self-registration information in the user portal.

Next, the common specification feed will be described in detail with reference to FIGS. 2A and 2B.
The common specification feed is generated by the member based on the RSS feed of the original page. When a member registers a feed, a desired original page is registered in the feed generation engine 10. For example, the URL of a Web page including an RSS feed is input to the feed generation engine 10. Alternatively, the original page is copied (copied) or dragged and dropped onto the feed generation engine 10.

  The feed generation engine 10 collects “URL”, “Title”, “Desc”, and “Date” from the RSS feed if there is an RSS feed in a blog (blog) or web page registered by the member. If there is no RSS feed, information corresponding to “URL”, “Title”, “Desc”, “Date” is collected from a blog or a web page. A common specification feed is generated by using the collected information.

  The format of the common specification feed includes the following “attribute code”, which constitutes the feed distribution control data, in addition to the metadata used for a normal RSS feed such as “URL”, “Title”, “Desc”, and “Date”. “Genre / Category”, “User Device”, “Position Information of Feed Information”, “Distribution Option (User Profile (Region, Age, Gender, Hobby, Occupation))”, “URL of QR Code Image”, “Distribution Time” "including.

  “Attribute code” indicates a content attribute. Here, the content attribute indicates Web 1.0 or Web 2.0. Web 1.0 relates to a channel such as a market information where the caller is limited to corporations. Web 2.0 relates to a network in which an individual is a sender, such as CGM (Consumer Generated Media) such as Blog (blog) and SNS (Social Networking Service).

  “Genre / category” is a content classification code. For example, the category is classified into a genre / category such as “news”, “movie”, “travel”, and its small classification.

  The “user device” indicates a device (apparatus) on the user side that is preferable for content browsing. For example, it indicates “mobile phone” or “PC (personal computer)”.

  “Position information of feed information” indicates position information based on GIS (Geographic Information System) related to feed information such as article contents of a common specification feed. For example, when the feed information is information about a store, the location information of the location of the store is shown.

  “Distribution option” indicates setting information for distribution and update. For example, if Web 1.0 is the target, options such as “feed copy counter”, “selective distribution of user profile”, and “restriction of distribution to Neg evaluation users” can be set. The “feed copy counter” indicates an upper limit value of the number of members (viewers) who copied the common specification feed. For companies that have created a common specification feed and companies that have added advertisements to the common specification feed, depending on the number of members that have copied the common specification feed, it is possible to charge more than necessary by enabling the Max restriction. Can be prevented. “Selected distribution of user profile” indicates an attribute of a user who is a distribution destination of a feed, that is, a browsing target. Here, a tag indicating each attribute is provided. As a result, it is possible to register the availability of feed distribution and copying according to attributes such as region, age, gender, hobby, and occupation. “Distribution restriction to Neg-evaluated user” indicates information for restricting delivery to a member who has made a low evaluation with respect to a feed once distributed. The Neg evaluation user indicates a member who has made a negative evaluation. Based on this information, members who have a low rating for a once-distributed feed are not notified of feed updates for the preferential campaign. Here, the member who acquired the feed sets a tag and evaluates it.

  “URL of QR code image” indicates a QR code image generated from a URL with a feed ID. In other words, the QR code image indicates the URL with the feed ID that is the original. The feed ID is identification information of a common specification feed in the container resource 20.

A configuration example of a URL with a feed ID is shown below.
“Http://www.portal.ne.jp/rss.html?ref=id001”
Here, “http://www.portal.ne.jp” is a URL indicating a general portal for member registration. The QR code image is stored in the container resource 20. “Id001” is a feed ID indicating identification information of the common specification feed in the container resource 20.

The feed ID can be set as follows.
“Feed ID = | Attribute Code | + | Genre Code | + | Category Code | + | Generator Code | + ItemID”
Each code is information of a predetermined number of bits. For example, if “attribute code” is “0”, “Web1.0 (channel)” is set, and if “1”, “Web2.0 (network)” is set. The “genre code” and “category code” are information indicating the classification code by a predetermined number of bits. The “generator code” is information indicating the identification information (member number) of the generator with a predetermined number of bits. “ItemID” is information indicating an identification number (rank number) of a common specification feed created by a specific member by a predetermined number of bits. Thus, it is possible to add a lot of information to the feed ID.

  “Delivery time” indicates the time when the feed is published. For example, when a company creates a feed related to its own product, it is possible to set the distribution time so that the feed is released in accordance with the broadcast of the TV CM of the company's product or magazine publication.

With reference to FIG. 3, the operation at the time of generating the feed will be described.
(1) Step S101
The feed generation engine 10 accepts registration of the original page from the member. For example, it accepts submission of web pages and blogs related to new products or their RSS feeds from member companies. In addition, it accepts input of feed distribution control data for determining a member to be a service providing target, that is, a member to be a feed distribution target. The feed distribution control data may be input later. By not delivering the feed until the feed delivery control data is input, the delivery time can be further controlled.
(2) Step S102
The feed generation engine 10 collects “URL”, “Title”, “Desc”, and “Date” from the RSS feed if there is an RSS feed on the original page registered by the member. If there is no RSS feed, information corresponding to “URL”, “Title”, “Desc”, “Date” is collected from a blog or a web page. A common specification feed is generated by using the collected information.
(3) Step S103
The feed generation engine 10 stores this common specification feed in the container resource 20. In addition, a URL that uniquely indicates the location information of the common specification feed in the container resource 20 is converted to create a QR code image, which is stored in the container resource 20.
(4) Step S104
If feed delivery control data is input, the feed generation engine 10 refers to the feed delivery control data and determines a member to be a feed delivery target. For example, it is determined whether or not the distribution conditions included in the feed distribution control data are met for all members, and the members that match the distribution conditions are set as “members to be distributed”. At this time, if there is no member to be distributed, the distribution process may be terminated. Further, based on the feed distribution control data designated by each member, the common specification feed in the container resource 20 is determined, and if the distribution condition is met, the metadata used for the RSS feed and the URL of the common specification feed are acquired and fed. Is stored in the service container 40 of the member to be distributed (5) Step S105
The feed generation engine 10 creates a feed including a copy (copy) of the metadata of the Web site included in the common specification feed stored in the container resource 20 and the URL of the common specification feed.
(6) Step S106
The feed generation engine 10 registers a common specification feed in the service container 40 provided for each member with a copy including the metadata of the Web site included in the common specification feed and the URL of the common specification feed. It is stored as a feed in the service container 40 of the member who is the user and the service container 40 of the member to be distributed.

With reference to FIG. 4, the operation at the time of updating the feed will be described.
(1) Step S201
The feed generation engine 10 periodically scans the date of the original page such as a blog or a web page and the “Date” of the common specification feed based on the common specification feed stored in the container resource 20.
(2) Step S202
The feed generation engine 10 determines the update of the original page based on the result of the comparison scan.
(3) Step S203
When the feed generation engine 10 determines to update the original page, it updates “URL”, “Title”, “Desc”, and “Date” of the common specification feed in the container resource 20. When there is no original page, the common specification feed in the corresponding container resource 20 is deleted.
(4) Step S204
The feed update engine 30 is posted and activated when a user portal (service container 40) is opened by a member.
(5) Step S205
The feed update engine 30 compares and scans the update of “Date” of the common specification feed in the container resource 20 based on the “Date” of the feed stored in each service container 40 for each member.
(6) Step S206
The feed update engine 30 confirms the update of the common specification feed based on the result of the comparison scan.
(7) Step S207
When the feed update engine 30 confirms the update of the common specification feed, the “URL”, “Title”, “Desc” of the corresponding feed in the service container 40 of the member to be distributed based on the feed distribution control data in accordance with the distribution time. , “Date” is updated. When there is no common specification feed, the feed in the corresponding service container 40 is deleted.

Next, utilization examples of the present invention will be described.
With reference to FIG. 5A and FIG. 5B, production and update of a Web page on which a blog is posted will be described. Note that “Blog (blog), Web page” indicates the original page. “My Portal” indicates a user portal.

  The registration of the original page is as described above. Here, when creating a common specification feed, a member designates a delivery time. The feed generation engine 10 may store a feed that is a copy (copy) of partial information at the time when the common specification feed is created in the service container 40-1 of the member who is the creator of the original page. The service container 40-2 of another member who becomes a viewer of the original page is permitted to store the feed when the distribution time comes.

  In addition, after the member who is the creator of the original page updates the original page, he / she designates a self-produced feed in the service container 40-1, and the “genre / category”, “ It is possible to perform operations of updating “user device”, “position information of feed information”, “distribution option (user profile (region, age, gender, hobby, occupation))”, and “distribution time”. In this case, the feed update engine 30 sends the feeds in the service containers 40-2 of other members according to the update contents of the common specification feed (distribution option in the case of Web 1.0) at the time when the distribution time comes. Update.

With reference to FIG. 6A and FIG. 6B, the case where feed promotion is implemented is demonstrated.
For example, when a member who is a viewer or a user who is not registered as a member uses the wireless communication device 50, a brochure or business card with a QR code image added thereto, or a QR code using the wireless communication device 50 A QR code image is acquired from another wireless communication device 50 on which the image is displayed, and the URL indicated by the QR code image is accessed. The wireless communication device 50 is preferably a mobile phone. However, actually, it is not limited to a mobile phone. In this QR code image, the URL of the general portal for member registration that uniquely indicates the location information in the container resource 20 of the common specification feed as a parameter is converted and recorded. In addition, the URL of the general portal for member registration posted on the Web page or e-mail is accessed. In this case, a PC (personal computer) may be used instead of the wireless communication device 50. When a user who accesses these URLs does not register as a member, the member registration comprehensive portal displays a member registration screen and prompts the user to input attribute information necessary for providing the service. After that, a new My portal (service container 40) for the registered user is created. The My portal is a user portal. Then, a feed based on the common specification feed is stored in the service container 40 from the container resource 20. In the case of an existing member, authentication is performed using the individual identification number, fixed IP address, or user ID and password of the wireless communication device 50, and if the confirmation is obtained, the member's existing My portal (service container 40) is accessed. Thus, the feed based on the common specification feed is stored in the service container 40 of the member.

  Here, the My portal includes items “My network”, “My channel”, and “My area”. Each item is classified into a genre and a category, and the content of the feed and a QR code image are displayed.

  “My network” corresponds to Web 2.0, and displays a feed indicating an item page in a blog in the consumer market network. Here, items of “My Item” and “Featured Item” are included. “My Item” displays a copy feed of a blog common specification feed registered by the member. “Featured Item” displays a feed indicating a page of an Item in the blog that the member desires to browse. For example, when the blog page corresponding to the QR code image acquired by the member using the wireless communication device 50 is Web 2.0, this page is displayed in “Featured Item”.

  The “My channel” corresponds to Web 1.0, and displays a feed indicating a company-originating Web page or Blog page on the market Web channel. For example, when the blog page corresponding to the QR code image acquired by the member using the wireless communication device 50 is Web 1.0, this page is displayed in the “My channel”. Moreover, you may make it display the feed based on the common specification feed which made the said member distribution object among the common specification feeds in the container resource 20. FIG. Common specification feeds targeted for the member include common specification feeds related to the member's own user profile (region, age, gender, hobby, occupation) entered by the member at the time of membership registration, A common specification feed related to the company that delivered the feed stored in the container 40 can be considered.

  The “My area” corresponds to both Web 1.0 and Web 2.0, and based on the location information of the wireless communication device 50 used by the member, among the common specification feeds in the container resource 20, A feed based on the common specification feed related to this position information is displayed. Here, a feed including GIS (Geographic Information System) information within a specific range with respect to GPS (Global Positioning System) information of the wireless communication device 50 is displayed. For example, a feed whose GIS information indicates the Kanto region is displayed on the wireless communication device 50 indicating that the GPS information is the Kanto region, and is not displayed on the other wireless communication devices 50. If the GIS information is a Blog feed created by a company such as Web 1.0, the GIS information indicates location information of the store or sales office of the company. In addition, in the case of a blog feed created by an individual like Web 2.0, position information related to the contents of the blog item is shown.

  In the My portal, buttons for “update” and “delete” are prepared for each of “My network”, “My channel”, and “My area”. Here, a button “update / delete” is displayed for each item. When a member designates a feed and presses the “update” button, the member who becomes a viewer of the feed selects an arbitrary tag and inputs an evaluation. At this time, a processing device (not shown) provided in the service container 40 displays an evaluation input screen and displays an evaluation axis for the tag selected by the member. The tag update aggregation is performed by the feed update engine 30. In addition, “update” and “delete” buttons are prepared separately, and when the “delete” button is pressed, the feed is deleted. The feed update engine 30 does not update a feed for which a negative evaluation is input. Moreover, when the member inputs a negative evaluation, the feed may be deleted. As a result, a member of a company or the like who is the creator of the original page can restrict distribution to a member who has made a negative evaluation (Neg evaluation user).

Referring to FIGS. 7A, 7B, and 7C, “feed” displayed on a standby screen of a wireless communication device (for example, a mobile phone) or a top page of a PC (personal computer) as feed navigation to a user portal. The Navi ”function will be described.
The feed generation engine 10 grasps the update contents of the original page and updates the common specification feed in the container resource 20. Note that the addition of advertisements and comments on the original page is not determined to be an update. In order to notify a new arrival of a new common specification feed or an updated common specification feed, a feed that is a partial copy of the common specification feed is automatically distributed to the feed Navi. The feed generation engine 10 classifies newly arranged feeds into genres and categories and arranges them to create a Navi distribution table. When “Feed Navi” is activated, the Navi distribution table in the container resource 20 is accessed and the feed is automatically distributed. Here, the Navi distribution table is created by the feed generation engine 10 based on the distribution request from the member and the user profile (region, age, gender, hobby, occupation) input at the time of member registration. 20 is stored. Further, it may be updated by the feed update engine 30 according to the evaluation input to the feed. In addition, feed distribution time can be specified in the Navi distribution table.

  In the feed Navi, keywords indicating genres and categories are displayed. When any of the displayed keywords is selected, a list of feeds (feed list) corresponding to the selected keyword in the Navi distribution table in the container resource 20 is displayed. At this time, feeds that have already been acquired and viewed may be displayed in gray, and other feeds may be highlighted in color. Each feed displayed in the feed list is provided with an area (check box) for inputting a check mark indicating that the feed has been selected. In addition, a button “acquisition” is displayed in the feed list, and when the “acquisition” button is pressed, the feed update engine 30 stores the feed in which the mark is input in the service container 40, Display on My Portal. There may be a plurality of feeds to which a check mark is input.

  When the feed to which the check mark is input corresponds to Web 1.0, the feed is displayed in “My channel”. If the feed is newly registered, “new” indicating that it is newly arrived information is displayed in the vicinity of the feed. In addition, it may be highlighted with a color. Each feed is displayed in the order of the creator ID and production date. The generator ID indicates the ID of the member who generated the common specification feed. The production date and time indicates the date and time when the common specification feed is produced or updated. Alternatively, the display order may be determined according to the advertisement fee paid by the creator.

With reference to FIG. 8A and FIG. 8B, the style sheet of “My channel” will be described.
First, the heading “New Feed Program” indicating that the feed is a new arrival is displayed. Below that, genres, categories, and feeds are displayed hierarchically in this order. Furthermore, a banner (banner area) such as a map display icon (MAP display icon) or a corporate advertisement is displayed in a part of the display space of “My channel”. If you drag the feed by operating the map display icon, a map of the location related to the contents of the feed will be displayed. When a banner such as a corporate advertisement is operated, an introduction page for companies and products related to the content of the feed is displayed.

  When accessing any feed of a channel page within the displayed category, a separate window of “channel page” is automatically generated. If the feed is for the purpose of promoting a new product, the “channel page” displays a company name, a campaign title, a video / image advertising space, a product banner, and a campaign message. The moving image / image advertisement space is, for example, a TV material, and a video advertisement used in a TV commercial or the like. The product banner is an image of an actual product. When the product banner is operated, the Web page of the product may be accessed. The campaign message is a message presented by the company during the campaign.

  The “channel page” includes items such as service information and a consumer column, and a corresponding feed is displayed in each item. In the service information, information on services performed by the company is displayed. In the consumer column, customer opinions regarding the product are displayed. Furthermore, items such as an actual store handling the product and a consumer's voice for the actual store are prepared, and a corresponding feed is displayed for each item. Similarly, items such as a Net store handling the product and a consumer's voice for the Net store are prepared, and a corresponding feed is displayed for each item. A Net store is a virtual store that sells products on a Web page.

  When the “channel page” is displayed, the company (corporation) is confirmed based on the creator ID, and if new, a distribution template for the company (corporation) is created and displayed. If not new, the distribution template already created is displayed. The distribution template includes each item described above. Further, when displaying the feed in the “channel page”, the company (corporate) or the store is confirmed based on the creator ID, and the feed is displayed in the display space. Also for the store, the actual store or the Net store is confirmed based on the creator ID, and the feed is displayed in the display space.

The features of the feed storage system of the present invention will be described with reference to FIG.
In addition, the following cases can be considered as the system configuration of the common specification feed and the storage device for storing the feed.
1) Container resource (server device), service container (server device)
2) Container resource (server device), service container (Internet connection device)
3) Container resource (server device), service container (wireless communication device)
Here, the container resource 20 and the service container 40 indicate database devices (storage devices) included in each device. In the case of a container resource (server device) and a service container (server device), the case where both the container resource and the service container exist in the same server device is included. The Internet connection device is a communication device compatible with wired communication that can be connected to the Internet. For example, relay devices such as personal computers (PCs), televisions compatible with the Internet, routers, and switching hubs are conceivable. The wireless communication device is preferably a mobile phone. However, actually, it is not limited to a mobile phone. For example, a wireless LAN switch, a wireless IP phone terminal, or a wireless communication compatible communication apparatus such as a PDA (Personal Digital Assistant) or a portable music player may be used. At this time, for example, the update notification of the common specification feed can be received by a mobile phone (wireless communication device), and the actually updated content (feed) can be browsed by a personal computer (Internet connection device). .

  As shown in FIG. 9, the container resource 20 has an XML-based “common specification feed”. The “common specification feed” includes “feed distribution control data” and “RSS feed metadata”. “Feed delivery control data” is data registered by a member, and includes “attribute code”, “genre / category”, “user device”, “position information of feed information”, “delivery option (user profile (region, Age, sex, hobby, occupation)) ”,“ URL of QR code image ”,“ delivery time ”. The “RSS feed metadata” is an automatic copy of the metadata in the RSS feed of the website according to the designation of the website by the member. The feed generation engine 10 creates a feed including the URL of the common specification feed and a copy of the metadata included in the common specification feed based on the determination made with reference to the “feed delivery control data”. Here, “RSS feed metadata” becomes “metadata included in the common specification feed”. Then, the feed is stored in each member service container 40 to which the created feed is to be distributed. In FIG. 9, as an example, the container resource 20 is a database device on the server device. The service container 40-1 is a database device on the server device. The container resource 20 and the service container 40-1 may exist on the same server device. The service container 40-2 is a database device on the Internet connection device. The service container 40-3 is a database device on a wireless communication device. However, actually, it is not limited to the above example.

  As described above, by using the feed storage system of the present invention, it is possible to construct a communication infrastructure (Infrastructure) that circulates and circulates the feed as blood of the network.

  Furthermore, if the feed storage system of the present invention functions as a communication infrastructure, not only corporate advertisement distribution but also individual advertisement distribution becomes possible. For example, it becomes possible for an individual member who has exhibited in an online auction to create a blog for promoting the exhibited product, and to notify other members of a feed related to the blog.

FIG. 1 is a block diagram showing the configuration of the feed storage system of the present invention. FIG. 2A is a diagram for illustrating an example of a common specification feed. FIG. 2B is a diagram for illustrating an example of a common specification feed. FIG. 3 is a sequence diagram showing an operation when generating a feed. FIG. 4 is a sequence diagram showing an operation when updating a feed. FIG. 5A is a conceptual diagram showing creation and update of a Web page. FIG. 5B is a conceptual diagram showing creation and update of a Web page. FIG. 6A is a diagram for explaining an example of feed promotion. FIG. 6B is a diagram for explaining an example of feed promotion. FIG. 7A is a diagram for explaining the feed Navi. FIG. 7B is a diagram for explaining the feed Navi. FIG. 7C is a diagram for explaining the feed Navi. FIG. 8A is a diagram for explaining a My channel style sheet. FIG. 8B is a diagram for explaining a My channel style sheet. FIG. 9 is a conceptual diagram for explaining the configuration of the feed storage system of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Feed generation engine 20 ... Container resource 30 ... Feed update engine 40 (-i, i = 1-n) ... Service container 50 ... Wireless communication apparatus 100 ... Feed storage system

Claims (14)

A container resource for storing a common specification feed including metadata of a website and feed distribution control data for determining members to be distributed;
A feed provided for each member and including a URL of the common specification feed and a copy of metadata included in the common specification feed is stored, and the feed is provided in a user portal (user page) provided for each member. A service container to provide,
A feed generation engine that creates the common specification feed and stores it in the container resource, creates the feed, and stores it in a service container of a member to be distributed based on the feed distribution control data; system. The feed storage system according to claim 1,
The feed generation system updates the common specification feed when the update information of the website is compared with the update information of the common specification feed to determine the update of the website. A feed storage system according to claim 2,
The feed generation engine creates the common specification feed based on the RSS feed of the website if the website has an RSS feed, and the website if the website does not have an RSS feed. A feed storage system that obtains metadata used for an RSS feed from itself and creates the common specification feed. A feed storage system according to claim 3,
The common specification feed is
Metadata used for RSS feeds of the website;
The following constituting the feed delivery control data:
An attribute code indicating whether the Web site is Web 1.0 or Web 2.0;
A classification code indicating the genre and category of the website;
Information indicating a user device suitable for browsing the website;
Location information related to the content of the website;
A feed copy counter that specifies an upper limit on the number of deliveries of the feed;
Information indicating the delivery time of the feed;
A URL of a QR code image obtained by converting a URL uniquely indicating the location information of the common specification feed;
A feed storage system including information indicating a user profile (region, age, gender, hobby, occupation) to which the feed is distributed. A feed storage system according to claim 3 or 4,
The feed generation engine determines the common specification feed in the container resource based on the feed distribution control data designated by each member. If the distribution condition is met, metadata used for the RSS feed and the common specification are determined. A feed storage system that acquires a URL of a feed, creates the feed, and stores the feed in a service container of a member to be distributed. A feed storage system according to any one of claims 1 to 5,
The feed generation engine converts a URL uniquely indicating the location information of the common specification feed in the container resource into a QR code image, and stores the QR code image in the container resource together with the common specification feed. . A feed storage system according to any one of claims 1 to 6,
When the update of the common specification feed is determined by comparing the update information of the common specification feed and the update information of the feed, the feed stored in the service container of the member to be distributed based on the feed distribution control data A feed storage system further comprising a feed update engine for updating the feed. A feed storage system according to any one of claims 1 to 7,
The container resource is a server device,
The service container is any one of a server device, an Internet connection device, and a wireless communication device. Creating a common specification feed including website metadata and feed delivery control data for determining members to be delivered and storing them in a container resource;
Creating a feed including a URL of the common specification feed and a copy of metadata included in the common specification feed, and storing the feed in a service container of a member to be distributed based on the feed distribution control data;
Providing the feed to a user portal (user page) of the member to be distributed. The feed storage method according to claim 9,
The feed storing method further comprising the step of updating the common specification feed when update information is determined by comparing the update information of the Web site and the update information of the common specification feed. The feed storage method according to claim 9 or 10,
Based on the feed delivery control data designated by each member, the common specification feed in the container resource is determined, and if the delivery condition is met, the metadata used for the RSS feed and the URL of the common specification feed are acquired. The feed storage system further comprises the step of creating the feed and storing the feed in a service container of the member to be distributed. The feed storage method according to any one of claims 9 to 11,
A feed storing method, further comprising: converting a URL uniquely indicating the location information of the common specification feed in the container resource into a QR code image, and storing the QR code image together with the common specification feed in a container resource. The feed storage method according to any one of claims 9 to 12,
When the update information of the common specification feed and the update information of the feed are compared to determine update, the step of updating the feed stored in the service container of the member to be distributed based on the feed distribution control data; A feed storage method further provided.   A program for causing a computer to execute the feed storage method according to any one of claims 9 to 13.

Images