JP5270781B1 - Information provision system - Google Patents

Abstract

A content providing system capable of supporting content creation by the creator without burdening the creator of the user content more than the creation of the content.
An information providing system acquires a user content support unit that stores user content received from a terminal device of a first user via a network and a support request for the user content from a terminal device of a second user. A support request acquisition unit 53, a system content storage unit 52 that stores a plurality of system contents prepared by a person different from both the first user and the second user, and a plurality of system contents stored in the system content storage unit 52 A content specifying unit 54 that specifies content for a supporter corresponding to the support request from among, and a content providing unit 58 for supporter that provides the supporter content specified by the content specifying unit 54 to a second user .
[Selection] Figure 3

Description

  The present invention relates to an information providing system, and more particularly to an information providing system that provides user generated content created by a user.

  Posting-type community sites that publish user-generated content created by users to other users are operated by various entities. A user of a contribution-type community site can browse content created by other users from a terminal device. One of the features of a post-type community site is the ability to add comments to posted content. The user can interact with the content creator and other users by using the comment function. For example, “E * Everysta” (“Everysta” is a registered trademark) (see Non-Patent Document 1) operated by the present applicant is an example of this type of contribution-type community site.

  Such a post-type community site is characterized in that the appeal of the community site itself is enhanced by improving the number and quality of content created and published by the user. Therefore, a method of supporting the creator of content on the contribution-type community site in terms of funds is being studied. One example is crowdfunding. Crowdfunding is a mechanism for providing a fundraiser with a relatively small amount of funds provided by a funding provider using a payment function on the web (see Non-Patent Document 2). Non-Patent Document 2 classifies crowdfunding into three types: “donation type”, “investment type”, and “purchase type”, paying attention to the kind of rewards received and the types of funding received. .

  “Donation-type” crowdfunding is distinguished from other types in that it does not have a mechanism for rewarding fund providers. As an example of “donation-type” crowdfunding, a service called “Pochi” operated by NEC Bigrobe Co., Ltd. is known (see Non-Patent Document 3).

  “Investment-type” crowdfunding pays the funder a part of the profits obtained from the content created by the fundraiser, and is another type in that it gives the funder a monetary return. Distinguished from In “CAMPFIRE” operated by Hyper Internets Inc., “investment-type” crowdfunding is performed (see Non-Patent Document 4).

  “Purchasing” crowdfunding is distinguished from other types in that the fundraiser gives the funder a return other than money. Non-monetary rewards include, for example, tangible items such as badges, stickers, and seals, and digital content such as electronic badges, stickers, and stickers. Intangible events such as social participation may be provided. In “Kickstarter” operated by Kickstarter, Inc., “purchase-type” crowdfunding is provided (see Non-Patent Document 5).

“E ★ Everysta”, [online], Everyista, Inc. [Search April 18, 2012], Internet <URL: http://estar.jp/.pc/> Haruka Yonera and Masahiko Inagi, “Crowd Funding: A Form of a New Community on the Web”, July 2011, Journal of Japanese Society for Artificial Intelligence Vol. 26, No. 4, pp. 385-381 “Pochi”, [online], NEC Bigrobe Co., Ltd., [April 18, 2012 search], Internet <URL: http://po-chi.jp/> "CAMPFIRE", [online], Hyper Internets, Inc. [Search April 18, 2012], Internet <URL: http://camp-fire.jp/> “Kickstarter”, [online], Kickstarter, Inc., [Search April 18, 2012], Internet <URL: http://www.kickstarter.com/>

  As a mechanism for supporting content creators of contribution-type community sites, it is conceivable to use the above-mentioned “purchase-type” crowdfunding. However, in the case of funding by “purchasing” crowdfunding on a contribution-type community site, the content creator must prepare the content to be “purchased” by the fund provider separately from the posted content. Don't be. In this way, applying “purchase-type” crowdfunding to a contribution-type community site may impose a burden on the creator of the content beyond creating the contribution content.

  Therefore, the present invention aims to provide a system capable of supporting content creation by the creator without forcing the creator of the user content more than the creation of the user content through various embodiments. And Other objects of the present invention will become apparent by referring to the entire specification.

  An information providing system according to an embodiment of the present invention includes a user content storage unit that stores user content received via a network from a terminal device operated by a first user, and a terminal device operated by a second user. , A support request acquisition unit that acquires a support request for the user content, a system content storage unit that stores a plurality of system contents prepared by a person different from both the first user and the second user, and the plurality of A content identifying unit for identifying content for a supporter corresponding to the support request from system content; a content providing unit for a supporter for providing the second user with the content for supporter identified by the content identifying unit; Information for determining a reward for the first user based on the support request. Comprising a determining unit.

  In one aspect of the present invention, the reward for the first user may be money determined based on the support request or a convertible point, and is associated with the user content determined based on the support request. It may be a non-convertible point or virtual currency. An information providing system according to another embodiment of the present invention includes a support history storage unit that stores the supporter content in association with the user content. An information providing system according to still another embodiment of the present invention can store one or a plurality of system contents in the plurality of system contents and the user contents in association with each other.

  An information providing system according to another embodiment of the present invention includes a content page providing unit that provides a content page including at least a part of the user content to the terminal device operated by the second user, and the support When the request is generated in response to an operation of an operation button displayed as a part of the content page in the terminal device operated by the second user, the content page is identified in association with the supporter content. A support request generation page information storage unit for storing content page identification information to be stored. An information providing system according to still another embodiment of the present invention provides an acquisition number storage unit that stores the number of times a support request for the user content is acquired by the support request acquisition unit, and the second number based on the support request. A billing processing unit for determining a billing amount for the user, and the billing processing unit sets the billing amount for the second user to 0 when the number of acquisitions stored in the acquisition number storage unit is zero. Configured to be a circle.

  An information providing program according to an embodiment of the present invention includes a user content storage unit that stores a user content received via a network from a terminal device operated by a first user, and a terminal operated by a second user. Support request acquisition means for acquiring a support request for the user content from a device, system content storage means for storing a plurality of system contents prepared by a person different from both the first user and the second user, Content identifying means for identifying supporter content corresponding to the support request from system content, supporter content providing means for providing supporter content identified by the content identifying unit to the second user, and Based on the support request, the first user Compensation determining means for determining a compensation against, to function as a.

  According to various embodiments of the present invention, it is possible to provide a content providing system that can support content creation by the creator without burdening the creator of the user content more than the creation of the content.

The block diagram which shows roughly the architecture of the server apparatus with which the information provision system which concerns on one Embodiment of this invention was equipped The block diagram which shows notionally the architecture of the terminal device with which the information provision system which concerns on one Embodiment of this invention was equipped The block diagram which shows the function of the server apparatus with which the information provision system which concerns on one Embodiment of this invention was equipped. Example of user content management table provided in information providing system according to one embodiment of the present invention Example of display on terminal device of top page of community site provided by information providing system according to one embodiment of the present invention An example of a support content management table in the information providing system according to an embodiment of the present invention An example of a point number management table provided in an information providing system according to an embodiment of the present invention An example of a support history management table provided in an information providing system according to an embodiment of the present invention Example of user page management table provided in information providing system according to one embodiment of the present invention Display example of a user content ranking display screen in a terminal device provided in an information providing system according to an embodiment of the present invention Display example of content page in terminal device provided in information providing system according to one embodiment of the present invention Display example of support content specifying page in terminal device provided in information providing system according to one embodiment of the present invention Display example of user page in terminal device provided in information providing system according to one embodiment of the present invention Another display example of a user page in a terminal device provided in an information providing system according to an embodiment of the present invention Another display example of a user page in a terminal device provided in an information providing system according to an embodiment of the present invention Display example of web page including support point ranking for user content C in terminal device provided in information providing system according to one embodiment of the present invention 6 is a flowchart illustrating a support providing method for a user content creator according to an embodiment of the present invention. Display example of content page in terminal device provided in information providing system according to one embodiment of the present invention Example of a support request generation page management table provided in an information providing system according to an embodiment of the present invention Display example of web page for voting in terminal device provided in information providing system according to one embodiment of the present invention Display example of voting web page in terminal device provided in information providing system according to another embodiment of the present invention Display example of system content purchase page in terminal device provided in one embodiment of the present invention

  Hereinafter, various embodiments of the present invention will be described with reference to the drawings as appropriate. In addition, the same referential mark is attached | subjected to the same component in drawing.

  FIG. 1 is a block diagram schematically showing the architecture of a content providing system according to an embodiment of the present invention. As shown in FIG. 1, in one embodiment of the present invention, a content providing server device 10 (hereinafter simply referred to as “server device 10”) has a communication function via a network 20 such as the Internet. The terminal devices 30-1, 30-2,..., 30-N (hereinafter, may be collectively referred to as “terminal device 30”) may be communicably connected.

  The server device 10 includes a CPU 11, a main memory 12, a user I / F 13, a communication I / F 14, an external memory 15, and a disk drive 16, as shown in the figure. Are electrically connected to each other. The CPU 11 loads various programs such as an operating system from the external memory 15 into the main memory 12, and executes instructions included in the loaded program. The main memory 12 is used for storing a program executed by the CPU 11, and is constituted by a DRAM, for example.

  The user I / F 13 includes, for example, an information input device such as a keyboard and a mouse that accepts operator input, and an information output device such as a liquid crystal display that outputs the calculation results of the CPU 11. The communication I / F 14 is implemented as hardware, firmware, communication software such as a TCP / IP driver or a PPP driver, or a combination thereof, and is configured to be able to communicate with the terminal device 30 via the network 20.

  The external memory 15 is composed of, for example, a magnetic disk drive, and stores various programs such as an operating system and files for displaying web pages on the terminal device 30. A file for displaying a web page is typically an HTML file. The external memory 15 also stores content received from the terminal device 30. . In the present specification, content created by the user of the terminal device 30 may be referred to as “user generated content” or simply “user content”. Each user content is stored in the external memory 15 as a plurality of web pages associated with each other, for example, including a part of the contents of the user content. For example, when the user content is a novel, each web page constituting the user content includes a part of the novel. For example, the contents of one novel are distributed and described in 100 web pages, and these web pages are stored in association with each other, whereby the user content corresponding to the novel is stored. Thus, the user content is composed of a plurality of hierarchical web pages. In the present specification, some or all of a plurality of hierarchical web pages constituting user content may be referred to as “content page” of the user content.

  The disk drive 16 reads data stored in various storage media such as CD-ROM, DVD-ROM, and DVD-R, or writes data to these storage media. Data stored in the storage medium can be read by the disk drive 16 and installed in the external memory 15.

  The terminal device 30 is an arbitrary information processing device that is stored in the server device 10 and executes a game displayed on a web browser and can be operated. For example, a mobile phone, a smartphone, a game console, a personal computer, a touch Including but not limited to pads and e-book readers.

  The architecture of the terminal device 30 will be described with reference to FIG. FIG. 2 is a block diagram conceptually showing the architecture of the terminal device 30 according to an embodiment of the present invention. The terminal device 30 includes a CPU 31, a main memory 32, a user I / F 33, a communication I / F 34, and an external memory 35, as shown in the figure, and these components are electrically connected to each other via a bus 36. Connected.

  The CPU 31 loads various programs such as an operating system from the external memory 35 into the main memory 32, and executes instructions included in the loaded program. The main memory 32 is used for storing a program executed by the CPU 31, and is constituted by a DRAM, for example.

  The user I / F 33 includes, for example, an information input device such as a touch panel that accepts an input from a player (user), a keyboard, a button, and a mouse, and an information output device such as a liquid crystal display that outputs a calculation result of the CPU 31. The communication I / F 34 is implemented as hardware, firmware, communication software such as a TCP / IP driver or PPP driver, or a combination thereof, and is configured to be able to communicate with the server device 10 via the network 20.

  The external memory 35 is composed of, for example, a magnetic disk drive or a flash memory, and stores various programs such as an operating system. Further, when various contents are received from the server device 10 via the communication I / F 34, the received contents can be stored in the external memory 35.

  The terminal device 30 includes, for example, browser software for interpreting an HTML format file and displaying it on the screen. This browser software may typically have a function of executing a script such as Javascript (registered trademark). Also, the browser software can incorporate plug-in software such as Flash Player provided by Adobe Systems. The terminal device 30 can analyze the HTML file acquired from the server device 10 using such browser software functions, and display a web page based on the analysis result. If a script is described in the HTML file, the browser software executes the script and executes processing according to the instruction of the script. For example, when a script in an HTML file refers to a content file stored in the external memory 15 of the server device 10, the browser software acquires the referenced file from the server device 10 and acquires it. The embedded content can be displayed in a web page.

  Next, functions of the server device 10 realized by the components shown in FIG. 1 will be described with reference to FIG. FIG. 3 is a block diagram illustrating functions of the server device 10 according to an embodiment of the present invention. As shown in FIG. 3, the server device 10 according to the present embodiment includes a user content storage unit 51, a support content storage unit 52, a support request acquisition unit 53, a supporter content specifying unit 54, and a point number storage. A unit 55, a reward determination unit 56, a content ranking generation unit 57, a support content providing unit 58, a user page information management unit 59, and a user page generation unit 60 are included. These functions are realized by loading a predetermined program into the main memory 12 under the control of the CPU 11, and the CPU 11 executing an operation based on a command of the program.

  The server device 10 provides, for example, a posting-type community site that provides user content to other users. In this community site, user content created by the user can be published by the server device 10 and viewed from the terminal device 30 of another user of the community site. The user content is transmitted from the user terminal device 30 and received by the server device 10 via the communication I / F 14. The user content storage unit 51 assigns a content ID for identifying the content to each received user content, and stores each received user content in association with the content ID assigned to the user content.

  The user content includes various types of content such as novels, photographs, and comics. The user content may be an application program such as a computer game program. In the present invention, the type of user content is not limited to a specific type. The user content is stored in a predetermined file format corresponding to the type of the content. For example, a novel created by a user can be stored in the user content storage unit 51 in a text format. Also, photos can be stored in GIF format or JPEG format, and moving images can be stored in MPEG-4 format.

  The user content storage unit 51 is realized by, for example, a user content management table provided in the external memory 15 or an external database server. FIG. 4 shows an example of a user content management table generated and updated by the user content storage unit 51 and used for managing user content. As shown in the figure, in the user content management table, a user ID for identifying a user who is the creator of each user content, a title of the user content, and a storage of the user content are associated with a content ID for identifying the user content. A URI that identifies the location is stored. In the user content management table, the number of support points described later can be managed. The user content management table shown in FIG. 4 is merely an example of a user content management method, and the user content management method in the present invention is not limited to the one using the user content management table of FIG. For example, it is possible to store the author name and description of the content included in the data received from the terminal device 30 in association with the content ID.

  The user of the terminal device 30 can transmit the user content to the server device 10 by using a predetermined web page for posting user content displayed on the terminal device 30. The content posting web page includes, for example, input fields for the title, author name, and description of the user content to be posted. The information input in these input fields is transmitted to the server device 10 together with the user content or in association with the user content.

  The user content stored in the user content storage unit 51 is disclosed to users of the community site. The user can use the terminal device 30 to access the server device 10 and browse desired user content stored in the user content storage unit 51. FIG. 5 is a display example in which the top page of the community site is displayed on the terminal device 30. The terminal device 30 can display the top page illustrated in FIG. 5 by accessing the server device 10, acquiring HTML data corresponding to the top page, and analyzing the acquired HTML data. As shown in the figure, the top page includes display fields representing “recommended”, “ranking”, “voting”, “setting”, and “user page”, respectively. A link is set in each display field, and when the user of the terminal device 30 selects one of the display fields using a predetermined input interface, the display screen of the terminal device 30 displays the link set in the display field. Transition to the web page specified by. For example, when an area represented as “ranking” is selected, the ranking of user content calculated by a predetermined method is displayed.

  The server device 10 can be equipped with a function of receiving various support for the user who created the user content from other users. In order to realize such a function, the support content storage unit 52 stores a plurality of support content information indicating the support content for the user who created the user content. The support content storage unit 52 is realized by, for example, a support content management table provided in the external memory 15 or an external database server. FIG. 6 conceptually shows an example of the support content management table. As illustrated, in the support content management table, “support point”, “price”, and “system content” are stored in association with the support content ID. The “support point” indicates the amount, degree, or magnitude of support for the user content. As described later, the support content for the creator of the user content based on the support point, for example, the support amount and the support point Is determined. “Price” indicates the amount of money paid by the user who performs the support in order to support the predetermined content.

  “System content” is content prepared in advance by an operator of a community site provided by the server device 10. The term “system” is used to distinguish content prepared by a community site operator from “user content” posted by a user of the community site. In other words, “system content” is content prepared by a person other than the user of the community site, typically an operator of the community site, whereas “user content” is created by the user of the community site. The two are distinguished in that they are content to be processed.

  As is clear from this definition, “system content” in this specification includes various digital contents such as icons, decorative frames, and electronic badges prepared by the operator of the community site provided by the server device 10. It is. As will be described later, when the user provides support for predetermined user content, the “system content” is provided to the user who has provided the support according to the content of the support. As described above, the system content is stored in the support content storage unit 52 in association with the support content ID. Therefore, when paying attention to the system content, the support content storage unit may be referred to as a system content storage unit.

  It should be noted that the term “community site” is intended to include any website that has a function of publishing user-generated content created by a user to other users or a service provided through the website. ing. In order to use a community site, user registration is often requested prior to use. In this specification, the term “user” may refer to a person who performs user registration for using the community site provided by the server device 10 and can use the community site. Although not shown, the server device 10 may include a user management table that issues a user ID to each user and stores the mail address, nickname, and the like of each user in association with the user ID.

  Further, the other function of the support content storage unit 52 or the server device 10 is to display a web page including information such as “support point” and “price” stored in the support content management table on the terminal device 30. Support content display HTML data including the data stored in the support content management table can be generated. The terminal device 30 can display a display screen for prompting the user to select the support content by interpreting the HTML data for displaying the support content using browser software.

  As will be described later, a user who provides support for a predetermined user content can operate the terminal device 30 to generate a support request for the user content, and transmit the generated support request to the server device 10. The support request includes, for example, a content ID for identifying the user content to be supported, a support content ID for specifying the support content, and a user ID of the user of the terminal device 30 that transmits the support request. The support request transmitted from the terminal device 30 is received by the server device 10 via the communication I / F 14. The received support request is acquired by the support request acquisition unit 53.

  Based on the support request acquired by the support request acquisition unit 53, the supporter content specifying unit 54 provides the terminal device 30 that has transmitted the support request from the system content stored in the support content storage unit 52. Select system content for. The system content provided to the terminal device 30 that has transmitted the support request may be referred to as “supporter content” in this specification. In one embodiment, the supporter content identification unit 54 extracts the support content ID included in the support request acquired by the support request acquisition unit 53 and associates it with the support content ID in the support content management table of FIG. The system content stored in this manner is specified as supporter content. For example, when the support content ID “S0000001” is included in the support request from the terminal device 30, the supporter uses “icon 1” associated with the support content ID “S0000001” in the support content management table. Identified as content for use. The supporter content specified by the supporter content specifying unit 54 is provided to the terminal device 30 by the supporter content providing unit 58 as described later.

  Further, the supporter content specifying unit 54 or a separate billing processing unit (not shown) sets the price “200 yen” associated with the support content ID “S000001” in the support content management table, A billing process for billing the user of the terminal device 30 that has transmitted the support request is performed. In one embodiment, only when each user makes a support request for a predetermined user content for the first time, regardless of the charge amount managed in the support content management table, for each user who made the first support request. The charging process may not be performed (or 0 yen is charged). In one embodiment of the present invention, the server device 10 stores an acquisition count storage unit that stores, for each user ID included in the support request, the acquisition count of the support request for the predetermined user content acquired by the support request acquisition unit 53. Can be provided. The content identifying unit for supporter 54 or a charging processing unit different from this can determine whether or not to perform the charging process with reference to the number of acquisitions stored in the acquisition number storage unit. Accordingly, when the user of the terminal device 30 makes a support request for the first time with respect to predetermined user content, the support request can be made free of charge. Can do. In another embodiment, when each user makes a support request for a predetermined user content for the first time, writing related to the user content (sometimes referred to as “review posting” in a contribution-type community site). It is possible to prevent the charging process for the user who makes the support request from being performed on the condition that the process is performed. Thereby, it is possible to provide the user with an incentive to post a review regarding the user content.

  The point number storage unit 55 can update the “point number” in the user content management table shown in FIG. 4 based on the acquired support request. For example, when the support request from the terminal device 30 includes “S000001” as the support content ID and “C0000021” as the content ID for identifying the user content to be supported, as shown in FIG. The number of points of the user content (user content C) associated with the content ID “C0000021” in the user content management table and the support point associated with the support content ID “S000001” in the support content management table of FIG. Increase by "20". As a result, the point number of the user content C is updated to “5045”.

  The point number of support points may be managed in the point number management table shown in FIG. 7 separately from or in addition to the user content management table. In this case, the point number storage unit 55 can update the point number management table based on the acquired support request. The point number storage unit 55 stores, for example, the content ID and user ID included in the support request in association with each other, and the number of points corresponding to the support content ID included in the support request is stored in the content ID and user ID. Store it in association with. The point number storage unit 55 can perform the same process and update the point number management table every time the support request acquisition unit 53 acquires a support request.

  Based on the total number of support points stored in association with each content ID in the user content management table, the reward determination unit 56 sums the number of support points stored in the point number management table for each content ID. Based on the total number of support points obtained in this way, the reward for the creator of the user content identified by the content ID can be determined. The process of summing the number of points is periodically performed at a predetermined time interval, for example. In one embodiment, the reward is money, and the money calculated by multiplying the total number of support points of each content ID by a predetermined coefficient is determined as the reward. For example, when the coefficient is 20, the reward for the creator of the user content to which the total support points of 1000 points are given is determined as 20000 yen by multiplying 1000 points by the coefficient 20. The reward in the present invention is, for example, an evaluation point for user content, a user point that can be used within a community site, or a creator of the user content in the form of a virtual currency that can be used within or outside the community site. May be provided. These points and virtual currency may be exchangeable or non-convertible. Further, by providing the total number of support points associated with a predetermined content ID to the user who created the user content corresponding to the content ID, the total number of support points can be used as a reward. For example, as shown in the user content management table of FIG. 4, the total number of support points provided for the content ID is stored in association with the content ID, thereby corresponding to the content ID. This means that the total number of support points is provided to the user who created the user content.

  In another embodiment, the server device 10 stores a support history storage that correlates and stores the content ID extracted from the support request and the support content ID when the support request is acquired by the support request acquisition unit 53. Part (not shown) can be provided. This support history storage unit is realized by, for example, a support history management table provided in the external memory 15 or an external database server. The support history management table is provided in the external memory 15 or an external database server in place of the point number management table shown in FIG. 7 or in addition to the point number management table shown in FIG. FIG. 8 shows an example of the support history management table. The reward determination unit 56 can determine the reward for the creator of the user content identified by the content ID for each content ID with reference to the support history management table and the support content management table of FIG. For example, in the embodiment shown in FIG. 8, since the support content IDs “S000001” and “S000002” are stored in association with the content ID “C0000021”, the reward determining unit 56 in FIG. “700 yen”, which is the sum of “200 yen” associated with “S000001” and “500 yen” associated with support content ID “S000002”, is used as a reward for the creator of this content ID “C0000021”. Can be determined.

  The in-contents ranking generation unit 57 can rank the users in descending order of the provided support points for each user content with reference to the point number management table. For example, for a given user content, a user identified by user ID “00001” (hereinafter referred to as “user 1”) makes a support request for 200 points, and user 2 makes a support request for 50 points. If the user 3 makes a support request for 20 points, the content ranking generation unit 57 ranks the user content in the order of the number of support points, that is, in the order of user 1, user 2, and user 3. Attach. In one embodiment of the present invention, a web page including ranking information indicating the determined ranking is created by the server device 10. The created web page is provided to the terminal device 30. The ranking information generated by the in-content ranking generation unit 57 for the predetermined content ID may be displayed together with the content related information of the user content on the web page (content page) for the user content corresponding to the content ID. . FIG. 16 is a display example of a web page created for user content C. As illustrated, on the ranking page of the user content C, a plurality of users are displayed in the descending order of the provided support points at the bottom of the image representing the user content C. In the example of FIG. 16, since the support of 1000 points with the largest number of users L was performed, it was ranked first.

  In another embodiment of the present invention, the supporter content providing unit 58 transmits the support request to the system content (supporter content) specified based on the support request by the supporter content specifying unit 54. It can be provided to the terminal device 30 of the user. For example, when a support request including the support content ID “S0000001” is acquired, an image file representing an icon corresponding to the support content ID “S0000001” is transmitted to the terminal device 30 that transmitted the support request. be able to. An image file representing an icon is an example of system content, and various other system content can be provided to the user.

  The supporter content providing unit 58 provides the supporter content specified based on the support request from the terminal device 30 by the supporter content specifying unit 54 to the terminal device 30 by various methods. Can do. For example, the supporter content providing unit 58 is embedded with a hyperlink (hereinafter also simply referred to as “link”) indicating the storage location of the supporter content specified by the supporter content specifying unit 54. The e-mail and web page can be transmitted to the terminal device 30. When the user performs an operation for selecting the hyperlink on the terminal device 30, the supporter content specified by the hyperlink is downloaded to the terminal device 30 by the communication function of the terminal device 30.

  The supporter content need not necessarily be downloaded to the terminal device 30. For example, a web page specific to each user is prepared in the community site, and the supporter specified by the support content specifying unit 54 based on the support request from the user in the web page specific to the user who has provided support. The display of the content for the user also corresponds to the provision of the content for the supporter to the user. In this specification, a web page unique to each user provided in the community site may be referred to as a “user page”. In one embodiment, the user page is managed by the user page information management unit 59. The user page information management unit 59 stores the content ID of one or a plurality of user contents supported by the user and the support content ID included in the support request for the user content in association with the user ID of each user. be able to. The user page information management unit 59 is realized by, for example, a user page management table provided in the external memory 15 or an external database server. An example of the user page management table is shown in FIG.

  When the user supports new user content, the user operates the terminal device 30 to transmit an addition request for adding the user content to the user page management table from the terminal device 30 to the server device 10. . Here, an example of a method for generating an addition request for adding user content to the user page management table will be described. First, when the server device 10 is accessed from the terminal device 30, the above-described top page (see FIG. 5) is displayed, and the display area displayed as “ranking” on this top page is selected, the display screen of the terminal device 30 is displayed. , Transition to the user content ranking display screen of FIG. For example, the user content ranking display screen ranks and displays the user content in descending order of the number of support points stored in the user content management table of FIG. In FIG. 10, the display image 81 of the user content (user content D) corresponding to the content ID “C0000008” with the largest support point number in the user content management table is displayed at the top, and then the support point number is large. In sequence, a display image 82 of user content (user content E) corresponding to the content ID “C0000134” and a display image 83 of user content (user content C) corresponding to the content ID “C0000021” are displayed.

  Each of the display images 81 to 83 is provided with a link for specifying the content page of each user content. When any of these display images is selected by the user, the display screen is specified by the link. Transition to the content page. FIG. 11 is a display example of a content page displayed on the terminal device 30 when the display image 83 is selected on the ranking display screen. The content page illustrated in FIG. 11 includes content related information of the user content C, an operation button 91 for reading the user content C, an operation button 92 for reading the author profile, and the user content C for adding to the user page. And an operation button 94 for making a support request for the user content C.

  When the user 1 operates the input interface of the terminal device 30 and selects the operation button 93, an addition request for adding the displayed user content C to the user page management table is transmitted to the server device 10. This addition request includes a content ID that identifies the user content C and a user ID “00001” that identifies the user 1. Upon receiving this addition request, the server device 10 stores the content ID “C0000021” included in the received addition request in the user page management table in association with the user ID “00001”.

  The user page management table is also updated when a support request is acquired by the support request acquisition unit 53. For example, when the support request includes the user ID “00001”, the content ID “C0000015”, and the support content ID “S000003”, the user ID “00001” and the content ID “C0000015” in the user page management table The support content ID “S000003” is stored in the area of the support content ID 1 corresponding to. If the content ID included in the support request is not stored in the user page management table in association with the user ID included in the support request, the content ID is associated with the user ID. Remember. For example, when the support request includes the user ID “00001”, the content ID “C0000020”, and the support content ID “S000001”, the content ID corresponding to the user ID “00001” in the user page management table is set. The content ID “C0000020” is stored in the area, and the support content ID “S000001” is stored in the area of the support content ID1 corresponding to the content ID “C0000020”. The user page information management unit 59 updates the user page management table in the same manner every time the support request acquisition unit 53 acquires a support request.

  Next, an example of a method for generating a support request in the terminal device 30 will be described. In the content page of FIG. 11, when the user 1 operates the terminal device 30 and selects the operation button 94, the display screen of the terminal device 30 transitions to the support content specifying page illustrated in FIG. As shown in FIG. 12, the support content specifying page includes a plurality of operation buttons 101, 102, 103, and 104 provided for each support content. Each operation button displays the contents of the system content provided to the supporter who has provided support along with the support points given to the user content creator and the price required for the support. For example, since “add star” and “20 points, 200 yen” are displayed on the operation button 101, when the user operates the terminal device 30 and selects the operation button 101, the operation button 101 corresponds to the operation button 101. A support request is generated. In the server device 10 that has acquired this support request, the point number storage unit 55 gives 20 support points to the creator of the user content C, and the charge processing unit charges the user 1 with 200 yen, and the user 1 is supported. The system content corresponding to “add star” is provided by the content providing unit 58 for the person. As described above, when the user 1 supports user content C for the first time, the charging processing unit does not have to perform the charging process. As a result, the user 1 can make a support request for the user content C free of charge.

  Specifically, when the user 1 operates the terminal device 30 and selects one of the operation buttons 101, 102, 103, and 104, the terminal device 30 displays a content ID “C0000021” that identifies the user content C, A support request including the user ID “00001” for identifying the user 1 and the support content ID “S000001” associated with the selected operation button is generated, and the generated support request is transmitted to the server device 10. This support request is acquired by the support request acquisition unit 53 in the server device 10. The user page information management unit 59 updates the user page management table based on the acquired support request. Specifically, in the user page management table, a content ID “C0000021” and a support content ID “S000001” are stored in association with the user ID “00001”.

  Next, user page generation processing in the user page generation unit 60 will be described. The user page generation unit 60 can generate a user page unique to each user for each user of the community site provided by the server device 10. This user page is generated with reference to the user page management table illustrated in FIG. 9, for example. Specifically, the user page of a predetermined user is associated with the content related information of the user content corresponding to the content ID associated with the user ID of the user and the user ID in the user page management table. It is generated so as to include the system content corresponding to the supported support content ID. The user page of each user is stored in the server device 10 so that it can be viewed from the terminal device 30 of another user.

  The content related information of the predetermined user content may include various information related to the user content attribute or the user content input or set by the creator of the user content. The content related information can include, for example, a title of the user content, a description of the user content, an author name of the user content, and an image representing the user content. The content-related information of each user content is stored in association with the content ID of the user content in the above-described user content management table, for example.

  FIG. 13 shows a display example of the user page on the terminal device 30. FIG. 13 is a display example of the user page of user 1 created based on the data stored in the user page management table of FIG. In the user page management table of FIG. 9, the content ID “C0000001” and the content ID “C0000015” are associated with the user ID “00001”. A display image 111 corresponding to “C0000001” and a display image 112 corresponding to the content ID “C0000015” are included.

  The display image 111 corresponding to the content ID “C0000001” includes the image 113 set in relation to the user content corresponding to the content ID, the title of the user content, the support point of the user content, and “recommended” ”Is displayed. Further, the outer edge of the display area of the display image 111 is surrounded by an emphasized frame line 115. The image 113, the title, and the support point are examples of the content related information of the user content corresponding to the content ID “C0000001”. On the other hand, the icon 114 is an example of the system content identified by the support content ID “S000002”, and the frame 115 is an example of the system content identified by the support content ID “S000005”.

  Similarly, the display image 112 corresponding to the content ID “C0000015” includes an image 116 set in association with the user content corresponding to the content ID, a title of the user content, a support point of the user content, and , An icon 117 displayed as “Attention!” Is included. The image 116, the title, and the support point are examples of the content related information of the user content corresponding to the content ID “C0000015”. On the other hand, the icon 117 is an example of the system content identified by the support content ID 1 “S000003”.

  As described above, when the user page management table is updated based on the addition request or the support request, the user page generation unit 60 generates a user page based on the updated user page management table. For example, as described above, when the content ID “C0000021” for identifying the user content C is added in association with the user ID “00001” in the user page management table in accordance with the addition request, as shown in FIG. , The display image 121 of the user content C corresponding to the added content ID “C0000021” is additionally displayed. In addition, when the support content ID “S000001” is added in association with the user ID “00001” and the content ID “C0000021” in the user page management table in accordance with the support request, the information is added as shown in FIG. System content (star icon) 132 corresponding to the support content ID “S000001” is superimposed on the display image 121.

  In another embodiment of the present invention, the user page generation unit 60 can change the display mode of the content related information of the user content displayed on the user page in response to the support request. For example, when the operation button 102 is selected on the support content identification page of FIG. 12, a support request including the support content ID “S000004” is generated and transmitted to the server device 10. The user page generation unit 60 can change the display color of characters included in the display image 121 of the user content C to be supported based on the acquired support request. For example, the display color of the portion “Title: C's success” included in the display image 121 is changed to a more prominent color. For example, the user page generation unit 60 changes the value of the color attribute of the font element for a predetermined character in the HTML file describing the user page based on the acquired support request, thereby changing the color of the character. , The color can be changed according to the value of the changed color attribute. In addition to changing the character color, the user page generation unit 60 can use various methods such as changing the background color of the display area of the user content to be supported, and highlighting the outer frame of the image 142 representing the user content. The display mode (including the display mode of the display area) of the content related information of the user content can be changed. Changing the display mode of the content related information of the user content displayed on the user page unique to the user is included in providing system content (supporter content) to the user. In the support content management table of FIG. 6, the fact that “color character” is stored in association with the support content ID “S0000004” indicates that “color character” is a type of system content. The “decoration frame” stored in association with the support content ID “S0000005” is also a type of system content. When the “color character” is provided to the user, for example, as described above, the display color of the content related information and other display elements included in the user page of the user is changed to a predetermined color. When the “decoration frame” is provided to the user, a frame decorated or emphasized is displayed outside the display area of the user content included in the user page of the user. As described above, the function of changing the display mode of the content related information of the user content displayed on the user page in response to the support request can be regarded as a function of providing the system content (supporter content) to the user. . Therefore, the function for changing the display mode of the content related information of the user content displayed on the user page in response to the above-described support request may be provided by the supporter content providing unit 58.

  Next, an operation example of the server device 10 will be described with reference to FIG. FIG. 17 shows an example of a method for providing support to a user content creator in a community site provided by the server device 10. When processing is started, in step 1704, system content is first prepared by the operator of the community site. The prepared system content is stored in the support content management table in association with the support content ID.

  Subsequently, in step 1706, the user content transmitted from the terminal device 30 of the user of the community site is received by the server device 10, and the received user content is stored in the user content management table. Subsequently, in step 1708, the support request acquisition unit 53 acquires the support request transmitted from the terminal device 30 of the user 1 among the plurality of users of the community site.

  When the support request is acquired by the support request acquisition unit 53, the process proceeds to Step 1710, and among the system contents stored in the support content management table, the system content corresponding to the support content ID included in the acquired support request (Supporter content) is identified. Subsequently, in step 1712, the content for the supporter specified based on the support request is provided to the user 1 who transmitted the support request. The supporter content can be provided to the user 1 in various modes. For example, in one aspect, the supporter content is included in a user page unique to the user 1 by the supporter content providing unit 58 or the user page generating unit 60. In another aspect, the supporter content is transmitted to the terminal device 30 of the user 1 by the supporter content providing unit 58.

  Subsequently, in step 1714, the point number management table is updated based on the number of support points corresponding to the support request acquired by the support request acquisition unit 53. Subsequently, the process proceeds to step 1716, and a reward is determined for each user content based on the number of points in the point number management table.

  In the support providing method of FIG. 17, the user content and the support request are transmitted from time to time from the terminal device 30 of the user of the community site, and therefore step 1706 may be executed before step 1704. If step 1716 is executed at a predetermined time interval, the processing from step 1704 to step 1714 is repeated until the execution time arrives. Various modifications described in this specification can be used as a specific method for providing supporter content and a specific method for determining rewards.

  As described above, in various embodiments of the present invention, the user can be urged to support the user content by providing the system content prepared by the community site operator in return. . Therefore, a system capable of supporting the creation of the user content without forcing the creator of the user content more than the burden of creating the user content is provided.

  Next, another embodiment of the present invention will be described with reference to FIGS. In another embodiment of the present invention, advertisement images for displaying advertisements for various products or services are included in the content page. FIG. 18 is a display example of a content page including an advertisement image displayed on the terminal device 30. The content page whose display example is shown in FIG. 18 is, for example, when the user operates the terminal device 30 and selects the display image 83 corresponding to the user content C on the user content ranking display screen of FIG. Obtained from the server device 10.

  As described above, the user content C is composed of a plurality of hierarchical web pages. The display example of FIG. 18 is a display example of a web page corresponding to the second page of the novel among the web pages constituting the content C. As shown in the figure, on the display screen of the content page of the user content C, an advertisement image 181, a content display image 182 in which a part of the content of the user content C is displayed, and a support request for the displayed user content are generated An operation button 183, a link 184 for displaying a web page corresponding to the content of the previous page of the user content C (first page in the example of FIG. 18), and the next page of the user content C (FIG. 18). In the example, a link 185 for displaying a web page corresponding to the content of the third page) is included.

  In the web page illustrated in FIG. 18, when the user operates the terminal device 30 and selects the operation button 183, the screen shifts to the support content identification page illustrated in FIG. As described above, the user operates the terminal device 30 to select the support content from the options presented on the support content specifying page.

  For example, when the operation button 101 is selected by the user, a support request corresponding to the operation button 101 is generated. In the embodiment illustrated in FIG. 18, in the support request, the content ID for identifying the user content to be supported, the support content ID for specifying the support content, the user ID of the user of the terminal device 30 that transmits the support request, and , Support request generation page identification information for identifying a web page including an operation button for generating the support request (the operation button 183 in the example of FIG. 18) is included. The support request generation page identification information can identify individual web pages constituting the content page. The support request generation page identification information may be, for example, a URL of a web page including an operation button for generating the support request.

  The generated support request is transmitted to the server device 10. In the server device 10, a support request is acquired by the support request acquisition unit 53. In addition to the functions shown in FIG. 3 or in place of some of the functions shown in FIG. 3, the server device 10 according to the present embodiment includes a content ID, a support content ID, and a support request included in the support request. A support request generation page information storage unit (not shown) that stores the generation page identification information in association with each other can be provided. This support request generation page information storage unit is realized by, for example, a support request generation page management table provided in the external memory 15 or an external database server. FIG. 19 shows an example of the support request generation page management table. With the support request generation page management table, it is possible to specify a web page for which an instruction for generating a support request acquired by the support request acquisition unit 53 has been made, among the content pages. For example, in the support request generation page management table, the content ID “C0000021” and the support content ID “S000001” are stored in association with the support request generation page identification information “C0000P45”. It is possible to specify that the support request including the support content ID “S000001” for the user content C specified by “” is generated in the user page identified by the support request generation page identification information “C0000P45”. The table shown in FIG. 19 is merely an example, and various changes can be made to the support request generation page management table. For example, the support request generation page management table may store support request generation page identification information in association with either a content ID or a support request ID.

  In addition to the functions shown in FIG. 3 or in place of some of the functions shown in FIG. 3, the server device 10 according to the present embodiment can receive user content from the advertiser of the advertisement image displayed on the content page. An advertisement fee determining unit (not shown) that determines an advertisement fee to be paid to the creator of the document can be provided. For example, the advertising fee determining unit refers to the support request generation page management table in FIG. 19 and determines the advertising fee to be paid to the creator of the user content specified by the content ID stored in the support request generation page management table. decide. For example, the server device 10 in the present embodiment includes an advertisement fee management table (not shown) that stores advertisement fees to be paid to the user in association with support request generation page identification information, and the advertisement fee determination unit The advertisement fee is determined by referring to the management table. Specifically, the advertising fee management table stores an advertising fee of 10 yen per support request in association with the support request generation page identification information “C0000P02”, and associates it with the support request generation page identification information “C0000P45”. An advertising fee of 5 yen per request for support is available. In the example of FIG. 19, since the content ID “C0000021” is stored in association with each of the support request generation page identification information “C0000P02” and “C0000P45”, the advertising fee determination unit performs the support request generation page identification information. Advertising fee paid to the creator of the user content corresponding to the content ID “C0000021” for 15 yen, which is the sum of the advertising fee of 10 yen corresponding to “C0000P02” and the advertising fee of 5 yen corresponding to “C0000P45” Can be determined as

  In one aspect of the present invention, the advertising fee determining unit is identified by the content ID based on the support request generation page identification information and the support content ID stored in association with the content ID in the support request generation page management table. The advertising fee to be paid to the creator of the user content can be determined. The advertisement fee is determined, for example, according to the price stored in association with the support content ID in the support content management table of FIG. In the example of FIG. 19, since the support content ID “S0000001” is associated with the support request generation page identification information “C0000P02”, the price of the support content ID “S0000001” in the support content management table of FIG. For example, “2 yen”, which is 1 / 100th of “200 yen” stored as, can be determined as the advertising fee. Also, since the support content ID “S0000002” is associated with the support request generation page identification information “C0000P45”, it is stored as the price of the support content ID “S0000002” in the support content management table of FIG. For example, “5 yen” which is 1/100 of “500 yen” can be determined as the advertising fee. As described above, since the support content ID is stored in association with the support request generation page identification information in the support request generation page management table, it is possible to set the advertisement fee for each individual web page constituting the content page. it can.

  As described above, in the embodiment of the present invention illustrated in FIG. 18 and FIG. 19, the content page provided to the terminal device 30 includes an operation button and an advertisement for generating a support request. The support request generated by operating the operation button identifies support request generation page identification information for identifying the content page, the content ID of the user content displayed on the content page, and the support content selected by the user. Support content ID is included. Therefore, the server device according to the present embodiment, for each individual web page constituting the content page, based on the support content ID associated with the support request generation page identification information for identifying the web page, Can be determined.

  In addition to the above, various modifications can be made to the embodiments of the present invention. For example, the server device 10 according to an embodiment of the present invention can include a support content setting unit (not shown) that stores a support content ID in association with a content ID that identifies user content. This support content setting unit is realized, for example, by storing a support content ID in association with each content ID in the user content management table of FIG. For example, when the support content setting unit receives a user content post from the user of the terminal device 30, the support content setting unit assigns a support content ID to the user content based on a predetermined algorithm, and identifies the support content ID by identifying the user content. By storing in association with the content ID to be performed, the support content ID can be stored in association with the content ID in the user content management table.

  The server device 10 according to the present embodiment can generate a voting web page with reference to the user content management table. Specifically, the voting web page includes a plurality of user contents and the contents of the system contents (see FIG. 6) corresponding to the support content ID stored in association with the user contents in the user content management table. A voting web page including the displayed operation buttons can be created. A display example in which the voting web page is displayed on the terminal device 30 is shown in FIG. The display screen of FIG. 20 is displayed on the display screen of the terminal device 30, for example, when the user operates the terminal device 30 and selects the area displayed as “voting” on the top page shown in FIG. . The voting web page display screen shown in FIG. 20 includes display images 211 and 212 corresponding to a plurality of user contents, respectively. Also, on this display screen, a plurality of operation buttons 213 and 214 corresponding to the support content IDs associated with each of these user contents in the user content management table are associated with the corresponding display images 211 and 212, respectively. Is displayed. When the user operates the terminal device 30 to select the operation button 213 or the operation button 214, a support request corresponding to the selected operation button is generated. For example, when the operation button 213 is selected, a support request for the user content C corresponding to the display image 211 associated with the operation button 213 is generated. The support request is transmitted to the server device 10. Since the support request processing in the server device 10 has already been described, the description thereof is omitted here.

  As described above, the server device 10 displays the plurality of user contents on the terminal device 30 in association with the operation buttons for generating a support request for each user content, so that the plurality of user contents are displayed. It is possible to provide a function for voting on favorite user content. That is, the user supports the favorite user content by operating the terminal device 30 to select an operation button associated with the favorite user content among the plurality of user contents displayed on the terminal device 30. The request can be transmitted to the server device 10. In place of the display images 213 and 214 representing the contents of the system content shown in FIG. 20, operation buttons 221 and 222 represented as “to vote” may be displayed as shown in FIG. FIG. 21 is another display example in which the voting web page is displayed on the terminal device 30. In this case, when the user selects the operation buttons 221 and 222, the display screen transits to, for example, the support content specifying page shown in FIG. As described above, when an operation button for displaying desired system content is selected on the support content identification page, a support request including the support content ID assigned to the operation button is generated. It is transmitted to the server device 10.

  In still another embodiment, a system content purchase page that can purchase system content (for example, an image or icon representing a bouquet) without associating it with specific user content is provided from the server device 10 to the terminal device 30. FIG. 22 is a display example in which the system content purchase page is displayed on the terminal device 30 according to the embodiment of the present invention. As illustrated, the system content purchase page includes operation buttons 201 and 202 for purchasing system content. The player can purchase system content corresponding to the selected operation button by selecting one of the operation buttons 201 and 202. For example, when the operation button 201 is selected, “Bouquet 1” associated with the selection button 201 can be purchased for 200 yen. As described above, system content purchased without being associated with specific user content may be referred to as “specific system content” in this specification, and a support content ID for identifying a predetermined specific system content is referred to as “specific system content”. It may be referred to as “identification information”. The specific system content is provided to the terminal device 30 of the player who purchased the specific system content in the same manner as the supporter content. For example, an image file representing the specific system content may be transmitted to the terminal device 30, or the specific system content may be displayed on the user page of the player.

  The player can support the user content using the purchased specific system content. For example, when the operation button 183 is selected on the content page shown in FIG. 18, a list of system contents (specific system contents) purchased by the player is displayed on the terminal device 30 of the player, and the player selects the list from the list. A support request is generated so as to include a support content ID (specific system content identification information) for identifying the selected specific system content. In addition to the specific system content identification information, the support request may include a content ID for identifying the user content to be supported and a user ID of the user of the terminal device 30 that transmits the support request. As described above, the reward determination unit 56 of the server device 10 that has acquired the support request may determine a reward amount for the creator of the user content to be supported based on various types of information included in the support request. it can. For example, the reward determination unit 56 calculates the reward amount based on the price associated with the support content ID (specific system content identification information) included in the acquired support request in the support content management table of FIG. Can be determined.

  Thus, according to the present embodiment, it is possible to make a support request for user content using the specific system content purchased before determining the user content to be supported.

  The processes and procedures described in the present specification are realized by software, hardware, or any combination thereof other than those explicitly described in the embodiments. More specifically, the processes and procedures described in this specification are performed by mounting logic corresponding to the processes on a medium such as an integrated circuit, a volatile memory, a nonvolatile memory, a magnetic disk, or an optical storage. Realized. Further, the processes and procedures described in the present specification can be implemented as various computer programs by implementing the processes and procedures as computer programs.

  Even if it is described that the processes and procedures described herein are performed by a single device, software, component, or module, such processes or procedures may involve multiple devices, multiple software, multiple Component and / or multiple modules. Also, even though the data, tables, or databases described herein are described as being stored in a single memory, such data, tables, or databases are provided on a single device. Alternatively, the data can be distributed and stored in a plurality of memories or a plurality of memories arranged in a plurality of devices. Furthermore, the software and hardware elements described herein can be implemented by integrating them into fewer components or by disassembling them into more components.

  In this specification, when the constituent elements of the invention are described as one or more, or when they are described without being limited to one or more, they should be interpreted separately in context. The component may be either singular or plural.

10 Server device
30 Terminal equipment
51 User content storage
52 Support content storage
53 Support Request Acquisition Department
54 Supporter Content Identification Department
55 Point number storage
56 Remuneration decision section
57 In-content ranking generator
58 Supporting content provider
59 User Page Information Management Department
60 User page generator

Claims (11)

An information providing system for providing a website that provides user content posted from one user to other users,
A user content storage unit for storing user content posted via a network from a terminal device operated by a first user of the website ;
A support request acquisition unit for acquiring a support request for the user content from a terminal device operated by a second user of the website ;
A system content storage unit for storing a plurality of system contents prepared by a person different from both the first user and the second user;
A content specifying unit for specifying content for a supporter corresponding to the support request from the plurality of system contents;
A supporter content providing unit that provides the supporter content specified by the content specifying unit to the second user;
A reward determination unit for determining a reward for the first user based on the support request;
A page generation unit for generating a web page provided on the website, including a display corresponding to the user content and a display corresponding to the supporter content;
Information provision system with The web page is viewable by a user other than the first user and the second user.
The information providing system according to claim 1. The web page includes an indication identifying the second user;
The information providing system according to claim 1. The web page is a web page unique to the second user;
The information providing system according to claim 1.   The information providing system according to claim 1, wherein the reward is money determined based on the support request or a cashable point.   2. The information providing system according to claim 1, wherein the reward is a non-cashable point or virtual currency associated with the user content, which is determined based on the support request. Information providing system according to any one of claims 1 to 6 comprising a support history storage unit that stores content for the supporters in association with the user content. Information providing system according to any claims 1 to 7 to one or more system content with the associating and user content storage in said plurality of system content. A content page providing unit that provides a content page including at least a part of the user content to the terminal device operated by the second user;
When the support request is generated in response to an operation of an operation button displayed as a part of the content page in the terminal device operated by the second user, the content page is associated with the supporter content. A support request generation page information storage unit for storing content page identification information for identifying
The information provision system according to any one of claims 1 to 8 , further comprising: An acquisition number storage unit that stores the number of times the support request for the user content is acquired by the support request acquisition unit;
A charging processing unit for determining a charging amount for the second user based on the support request;
Further comprising
The accounting processing unit, when the acquisition number 0 times the acquisition count storage unit stores, according to any one of claims 1 to 9 and 0 yen billing amount for the second user Information provision system. An information providing system for providing a website that provides user content posted from one user to other users,
A user content storage unit for storing user content posted via a network from a terminal device operated by a first user of the website ;
A system content storage unit for storing a plurality of system contents prepared by a different person from both the first user and the second user of the website ;
A support content providing unit that provides the second user with specific system content selected from the plurality of system content;
A support request acquisition unit for acquiring a support request for the user content, including specific system content identification information for identifying the specific system content, from a terminal device operated by the second user;
A reward determining unit for determining a reward for the first user based on the specific system content identification information for identifying the content for the supporter included in the support request;
A page generation unit for generating a web page provided on the website, including a display corresponding to the user content and a display corresponding to the supporter content;
Information provision system with

Images