Program, method, and system

Abstract

To provide a program, a method and a system that allow preferred information to be easily identified.SOLUTION: A program for providing a user with contents of multiple kinds that are associated with attributes stores an attribute preselected according to a user's operation, from a first attribute of multiple kinds and a second attribute of multiple kinds, in a manner that allows specification. Further, in accordance with establishment of predetermined conditions, the program displays contents by switching to one display state of multiple kinds including: a first display state in which the user can identify content information related to contents associated with the first attribute preselected by the user and stored; and a second display state in which the user can identify content information related to contents associated with both the first attribute and the second attribute preselected by the user and stored.SELECTED DRAWING: Figure 16

Description

Technical Field

[0001] The present invention relates to a program, a method, and a system.

Background Art

[0002] In fan activities (so-called oshi activities) to support favorite support targets such as people like talents or things, for example, by checking posts from the talent himself / herself who is the support target on SNS or the like, or posts from the accounts of agencies to which the supported talent belongs, it has become the mainstream to collect the latest information of the support target (see, for example, Non-Patent Document 1 and Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional information collection method, not only goods information and distribution information related to the support target but also various posts such as daily posts and information unrelated to the support target are mixed, so it may be difficult for users to immediately reach the target information. Also, even if there is a post of information related to the user's support target by an account that the user does not follow, since it is a post of a non-followed account, the user may overlook it. In addition, it causes the trouble of setting conditions manually every time for searching.

[0005] The present invention has been conceived in view of such circumstances, and provides a program, a method, and a system that can easily identify preferred information.

Means for Solving the Problems

[0006] (1) A program according to an aspect of the present invention is a program (for example, a program stored in a storage unit 120, a program for providing content, etc.) that can provide a user with a plurality of types of content (for example, news articles, posted articles, videos, etc.) associated with attributes, The attributes include a plurality of types of first attributes (for example, community A, community B, etc. in FIG. 6(A) corresponding to the affiliated group 1 of the talent information database in FIG. 5) and a plurality of types of second attributes (for example, a talent stored in the talent information database in FIG. 5, or a unit of the affiliated group 2, etc.), A computer (for example, a distribution server 100, a user terminal 300) is Storage means for storing in a specifiable manner an attribute (e.g., the participating community and favorite talent selected in steps S103 and S107 of FIG. 9 on the attribute selection screen of FIG. 6, etc.) pre-selected according to an operation from the user, from among the plurality of types of first attributes and the plurality of types of second attributes (e.g., the account management unit 133 stores the participating community and favorite talent ID in association with the user ID in the user information database of FIG. 7 as account information 125 in steps S104 and S108 of FIG. 9), and Content information regarding content associated with a first attribute pre-selected and stored by the user (e.g., the content headings (60, 70, 90) of content posted within the participating community pre-selected by the user stored in the user information database of FIG. 7) is made to be in a first display state (e.g., by step S203 of FIG. 16, the home screen of FIG. 10 and the community screen of FIG. 11 are displayed in a state where the favorite filter 20 is off as shown in FIG. 15(B)) that allows the user to identify it, in response to the fulfillment of a predetermined condition (e.g., an on / off operation for the favorite filter 20 displayed on the home screen of FIG. 10, the community screen of FIG. 11, and the distribution schedule screen of FIG. 27), and content information regarding content associated with both a first attribute and a second attribute pre-selected and stored by the user (e.g., the content headings (60, 70, 90) of the article of FIG. 14 in which the talent ID of the favorite talent pre-selected by the user is associated, which is content posted within the participating community pre-selected by the user and stored in the user information database of FIG. 7) is made to be in a second display state (e.g., a screen in which the favorite filter 20 of FIG. 15(A) is on, by step S204 of FIG. 16 by an operation of turning on the favorite filter 20) that allows the user to identify it, and a display switching means (e.g., the content management unit 132, the account management unit 133, the input information transmission unit 353, the display control unit 352) is made to function to switch and display to any one of a plurality of types of display states including these. 、 Each of the plurality of types of first attributes is a group including at least any one of the plurality of types of second attributes, and each of the plurality of types of second attributes is an attribute that can belong to at least any one of the plurality of groups corresponding to the plurality of types of first attributes. be.

[0007] According to such a configuration, it is possible to switch and display content information regarding content associated with a first attribute preselected by a user and content information regarding content associated with a first attribute and a second attribute preselected by the user. Thereby, the user can easily identify preferred information.

[0008] (2) In the above (1), the predetermined condition is an operation different from a series of operations when the user preselects an attribute (for example, the operations in the attribute selection process of FIG. 9), and includes a condition that is established in response to a switching operation from the user (for example, a selection operation to the push filter 20).

[0009] According to such a configuration, it is possible to switch and display the content information regarding the content associated with the preselected attribute without requiring the user to perform an operation of selecting an attribute again when displaying, thereby improving the operability and user convenience.

[0010] (3) In the above (2), the display switching means displays an icon that accepts the switching operation in both the first display state and the second display state (for example, the push filter 20 is displayed whether it is in the on state (A) or the off state (B) in FIG. 15), and switches to the second display state (for example, the on state of the push filter 20 in FIG. 15(A), step S204 in FIG. 16) in response to an operation on the icon in the first display state (for example, an operation on the push filter 20 in the off state of the push filter 20 in FIG. 15(B), step S201 in FIG. 16), and switches to the first display state in response to an operation on the icon in the second display state and displays (for example, in the on state of the push filter 20 in FIG. 15(A), by operating the push filter 20, in steps S202 and S203, it is displayed in the off state of the push filter in FIG. 15(B)).

[0011] According to such a configuration, the switching can be simplified and facilitated.

[0012] (4) In the above (1), among the plurality of types of content, there is content (for example, the content posted in the community P that is always in the participating state, as illustrated in FIG. 6(A), or the feature 61 that is displayed regardless of the community in which the user is participating on the home screen of FIG. 10) in which a third attribute different from the first attribute and the second attribute is associated. Regarding the content information regarding the content associated with the third attribute, the display switching means is configured to be able to be specified in either the first display state or the second display state regardless of the attribute preselected and stored by the user (for example, the content posted in the community P and the feature 61 are displayed regardless of which participating community the user has preselected and which favorite talent the user has selected).

[0013] According to such a configuration, by enabling the display of content information regarding an attribute different from the attribute preselected by the user, it becomes possible to notify the user, for example, of information that the operator wants to notify all users regardless of the switching state.

[0014] (5) In the above (1), among the plurality of types of content, there is content (for example, the article a99 in FIGS. 14 and 25, etc., content for which no related talent is associated) in which only the first attribute among the first attribute and the second attribute is associated. The second display state is a display state that does not include the display of content information regarding the content associated with only the first attribute (for example, even for the content posted in the participating community, the content heading of the content for which no related talent is associated is not displayed).

[0015] According to such a configuration, in the second display state, since content information regarding content not associated with the second attribute is not displayed, it becomes easy for the user to identify information associated with the preferred first and second attributes.

[0016] (6) In the above (1), the plurality of types of second attributes are a plurality of types of characters (for example, each talent in FIG. 5), The plurality of types of first attributes are a plurality of types of groups (for example, the affiliated groups 1 (group A, group B, etc.) that classify the characters that are the second attributes) that classify the characters that are the second attributes.

[0017] According to such a configuration, it becomes possible to specify information further narrowed down to information on characters preferred by the user from information regarding the groups that classify the characters.

[0018] (7) In the above (1), the plurality of types of second attributes include an attribute composed of a plurality of characters (for example, a unit (first-generation students, second-generation students, etc.) such as affiliated group 2 in FIG. 5).

[0019] According to such a configuration, it becomes possible to specify information further narrowed down to information on an attribute composed of a plurality of characters preferred by the user from information regarding the groups that classify the characters.

[0020] (8) In the above (1), the plurality of types of content can be classified into any of a plurality of types of categories (for example, popular user posts 63, commemorative distributions 64, goods 65, etc. in FIG. 10) including a specific type of category (for example, recommended topic 62 on the home screen in FIG. 10), The display switching means can classify content information related to the content for each of the plurality of types of categories and display it (for example, the home screen in FIG. 10). In a specific type of category, in either the first display state or the second display state, content information regarding a predetermined number of contents among the contents associated with both the first attribute and the second attribute preselected and stored by the user can be displayed so that the user can identify it (for example, regardless of whether the push filter 20 is on or off, in the push topic 62, a predetermined number of content headings 60 of the content posted in the community preselected by the user and associated with the push talent preselected by the user can be displayed). In categories other than the specific type of category, content information regarding the content corresponding to whether it is in the first display state or the second display state is displayed so that the user can identify it (for example, for categories other than the push topic 62, the displayed content headings 60 are switched by the on / off operation of the push filter 20).

[0021] According to such a configuration, since a part of the content associated with the first attribute and the second attribute preselected by the user can be displayed without performing the switching operation of the display state, the user can identify the content associated with the preferred first attribute and second attribute without the trouble of the switching operation.

[0022] (9) In the above (8), the display switching means can display, in either the first display state or the second display state, the content information regarding the content classified into the specific type of category (for example, the content heading 60 displayed in the push topic 62) with priority over the content information regarding the content classified into other categories (for example, as illustrated in FIG. 10, the display order is higher than that of other categories).

[0023] According to such a configuration, it becomes easy for the user to identify the content associated with the preferred first attribute and second attribute.

[0024] (10) In the above (1), the first display state is among the first attributes that have been preselected and stored by the user (for example, among the communities preselected by the user stored in the user information database in FIG. 7 through the attribute selection process in FIG. 9), and is a display state in which the user can identify the content information regarding the content associated with the first attribute selected in response to an operation from the user (for example, if community A and community B are selected as participating communities, further select the communities individually from the channel list screen in FIG. 12, and the screens of the individual communities (community screens exemplified in FIG. 11) are displayed. Alternatively, by a selection operation on the community icon 14, the screen of the community in which the community bar 81 is selected in the channel list screen in FIG. 12 is displayed).

[0025] According to such a configuration, since the user can select a more preferred first attribute from among the first attributes preselected by the user and display the content information for each of the further selected first attributes, the user can further extract arbitrary information as needed even from among the preferred information, improving convenience.

[0026] (11) In the above (1), the second display state is a display state that can be switched to and displayed as a display state in which the user can identify the content information regarding the content associated with the attribute selected in response to an operation from the user among the first attributes and the second attributes that have been preselected and stored by the user (for example, among the favorite talents stored in the user information database in FIG. 7 through the attribute selection process in FIG. 9) (for example, even if multiple favorite talents are selected, it is possible to further narrow down to each individual talent (such as the most favorite talent, etc.). Refer to the modified example (regarding the attribute extraction process)).

[0027] According to such a configuration, since the user can further select a second attribute of preference from among the second attributes preselected by the user and display content information for each of the further selected second attributes, the user can further extract arbitrary information as needed even from among the information of preference, improving convenience.

[0028] (12) In the above (1), the computer is caused to function as means for performing a reception effect (for example, the appearance of an icon or a fan mark in FIG. 24(A), a luxurious effect in FIG. 24(B), a tap action effect process in FIG. 26) each time a favorable action from the user with respect to the content (for example, a tap action on an icon 708 such as FIG. 24) is received. The reception effect includes an effect related to the second attribute associated with the content that has received the action (for example, if a related talent is associated with the content on which the tap action has been performed, an effect of a fan mark corresponding to each talent (such as the fan mark 42 in FIG. 24) or a talent effect as illustrated in article a1 of FIG. 25).

[0029] According to such a configuration, since the reception effect includes an effect related to the second attribute, it is possible to prompt the user to take an action.

[0030] (13) In the above (12), the means for performing the reception effect performs a special reception effect (for example, the luxurious effect, talent effect in FIGS. 24(B), 25, steps S508 to S513 in FIG. 26, etc.) when the action has been received a predetermined number of times (for example, 100 tap times).

[0031] According to such a configuration, since a special reception effect is performed when the action is performed a predetermined number of times, it is possible to prompt the user to take an action.

[0032] (14) In the above (1), the plurality of types of content includes second-attribute-related content associated with any of the plurality of types of second attributes (for example, content associated with the related talent in FIG. 14), the display switching means is configured to display content information regarding the second-attribute-related content in such a manner that the second attribute associated with the second-attribute-related content can be specified in both the first display state and the second display state (for example, regardless of whether the push filter 20 is on or off, related talents 88 (performing-related talents 94) are displayed in content headings (60, 70, 90), etc.).

[0033] According to such a configuration, the user can specify the second attribute associated with the second-attribute-related content in both the first display state and the second display state, thus improving the convenience for the user.

[0034] (15) In the above (1), the plurality of types of content includes contributed content contributed by a user (for example, an article of a user with posting authority in FIG. 14), the computer is means (for example, content management unit 132, input information transmission unit 353) for generating content information regarding contributed content according to posting information from the user (for example, posting information for specifying text, image, category, related talent, user ID, etc. transmitted in step S313 of FIG. 18), and when the posting information includes information for designating a second attribute (for example, an operation on the related talent bar 40 in FIG. 17, step S310 and step S311 in FIG. 18), the contributed content is generated as content information regarding content associated with the designated second attribute (for example, in the content database of FIG. 14, the talent ID of the talent selected for the related talent is associated and stored, and in the home screen of FIG. 10 and the community screen of FIG. 11, content headings (60, 70) are displayed), and is made to function as means (for example, content management unit 132, input information transmission unit 353).

[0035] According to such a configuration, since the second attribute can also be associated with user posts, it becomes easy to share preference information among users.

[0036] (16) In the above (1), the plurality of types of content includes post content posted by a user (for example, an article of a user with posting authority in FIG. 14), the user includes a plurality of specific users, the computer is functioned as means (for example, content management unit 132, input unit 330) for receiving an action (for example, a comment or a tap action) on content information regarding the post content, the plurality of types of second attributes are a plurality of types of characters corresponding to each of the plurality of specific users (for example, a specific user corresponds to each of the talents in FIG. 5), the display switching means changes the display mode of the content information regarding the post content to a different display mode and displays it in response to receiving an action from the specific user on the content information regarding the post content (for example, when there is an action from a user corresponding to a talent, a special action 79 is displayed on the content headings (60, 70, 90)).

[0037] According to such a configuration, the user can easily identify that the post content is the one on which a specific user has taken an action. Therefore, the convenience is improved for a user who seeks information regarding the second attribute. Also, if there is an action from a specific user on the post content posted by the user, the user can obtain a special feeling.

[0038] (17) In the above (16), in response to receiving an action from the specific user with respect to the content information regarding the posted content, the display switching means changes the display mode of the content information regarding the posted content to a different display mode according to whether the specific user is a specific user corresponding to a second attribute that has been pre-selected and stored by the user. (For example, if the talent who has taken an action on the content is the favorite talent, the display mode is changed from when it is not the favorite talent. Refer to the modification example (regarding the display mode of special actions on the home screen, community screen, etc.).

[0039] According to such a configuration, the user can easily identify that the posted content is the one on which the specific user corresponding to the second attribute pre-selected by the user has taken an action. Therefore, the convenience is improved for the user who seeks information regarding the second attribute. In addition, the user can recognize that the specific user who has taken an action on the posted content made by the user is the specific user corresponding to the second attribute pre-selected by the user, and the user can obtain a further sense of specialness.

[0040] (18) In the above (16), in response to receiving an action from the specific user with respect to the content information regarding the posted content, the display switching means changes the display mode of the content information regarding the posted content to a different display mode according to whether the specific user is a specific user corresponding to a second attribute associated with the posted content. (For example, if the talent who has taken an action on the content is the relevant talent himself / herself associated with the content, the display mode is changed from when it is not the relevant talent. Refer to the modification example (regarding the display mode of special actions on the home screen, community screen, etc.).

[0041] According to such a configuration, the user can easily identify the posted content on which a specific user corresponding to the second attribute associated with the posted content has taken an action. Therefore, the convenience is improved for the user who requests information regarding the second attribute. In addition, the user can recognize that the specific user who has taken an action on the posted content made by the user is the specific user associated with the posted content, and the user can obtain a further sense of specialness.

[0042] (19) In the above (1), when making the computer enable the user to identify the content information associated with the second attribute preselected and stored by the user (for example, when content in which a favorite talent is associated as a related talent is posted), make the computer function as means (for example, control unit 130, control unit 350) for notifying the user that the content information associated with the second attribute can be identified (for example, push notification indicating that information regarding the favorite talent has been posted). In the above (1), when making the computer enable the user to identify the content information associated with the second attribute preselected and stored by the user (for example, when content in which a favorite talent is associated as a related talent is posted), make the computer function as means (for example, control unit 130, control unit 350) for notifying the user that the content information associated with the second attribute can be identified (for example, push notification indicating that information regarding the favorite talent has been posted). First In the above (1), when making the computer enable the user to identify the content information associated with the second attribute preselected and stored by the user (for example, when content in which a favorite talent is associated as a related talent is posted), make the computer function as means (for example, control unit 130, control unit 350) for notifying the user that the content information associated with the second attribute can be identified (for example, push notification indicating that information regarding the favorite talent has been posted).

[0043] According to such a configuration, it becomes easier for the user to identify the content information regarding the second attribute preselected.

[0044] (20) In the above (1), make the computer obtain external posting information (for example, a distribution video in a video distribution service) provided by an external service (for example, external web service 400), which is information (for example, information obtainable through a WebAPI) for identifying the external posting, and includes attribute identification information (for example, channel account attribute identification information 96a illustrated in FIG. 27(C) or handle attribute identification information 96b input in summary column 95) for identifying an attribute (for example, a channel account corresponding to belonging group 1 in FIG. 5 or each talent in FIG. 5 belonging to belonging group 1) among the plurality of types of first attributes and the plurality of types of second attributes associated with the external posting information, by means (for example, communication unit 110). In the above (1), make the computer obtain external posting information (for example, a distribution video in a video distribution service) provided by an external service (for example, external web service 400), which is information (for example, information obtainable through a WebAPI) for identifying the external posting, and includes attribute identification information (for example, channel account attribute identification information 96a illustrated in FIG. 27(C) or handle attribute identification information 96b input in summary column 95) for identifying an attribute (for example, a channel account corresponding to belonging group 1 in FIG. 5 or each talent in FIG. 5 belonging to belonging group 1) among the plurality of types of first attributes and the plurality of types of second attributes associated with the external posting information, by means (for example, communication unit 110). Means (for example, content management unit 132) for generating content information regarding externally submitted content according to the externally submitted information (for example, content headings 90 of FIGS. 27(A) and 27(B) that can transition to the distribution video of FIG. 27(C) according to the upload of the distribution video of FIG. 27(C)), and when the externally submitted information includes attribute identification information, the externally submitted content (for example, when the distribution video information obtained by WebAPI includes attribute identification information 96 related to the participating community and the favorite talent) is generated as content information regarding the externally submitted content associated with the attribute identified from the attribute identification information (for example, generating content headings 90 that associate the community (corresponding to the affiliated group 1) and the talent ID of each talent by the attribute identification information 96), and function as such means (for example, content management unit 132). The first display state is a display state including the display of content information regarding the externally submitted content associated with the first attribute preselected and stored by the user among the externally submitted content (for example, the distribution schedule screen of the affiliated group 1 corresponding to the participating community preselected by the user is displayed). The second display state is a display state including the display of content information regarding the externally submitted content associated with both the first attribute and the second attribute preselected and stored by the user among the externally submitted content (for example, by operating to turn on the favorite filter 20, further display the content heading 90 of the distribution (such as a distributor or a scheduled co-star) associated with the favorite talent from the distribution schedule screen of the group corresponding to the participating community preselected by the user (FIG. 27, etc.)).

[0045] According to such a configuration, even for externally submitted content provided by an external service, it can be optimized to the user's favorite information, making it easier for the user to identify.

[0046] (21) A method according to an aspect of the present invention is a method of controlling a computer (e.g., a distribution server 100, a user terminal 300) to enable a user to be provided with a plurality of types of content (e.g., news articles, posted articles, videos, etc.) associated with attributes, The attributes include a plurality of types of first attributes (e.g., Community A, Community B, etc. in FIG. 6(A) corresponding to Group 1 of the talent information database in FIG. 5) and a plurality of types of second attributes (e.g., talents stored in the talent information database in FIG. 5, or units of Group 2, etc.), Steps (e.g., steps S104 and S108 in FIG. 9) for storing in a specifiable manner an attribute (e.g., the participating community and favorite talent selected in steps S103 and S107 in FIG. 9 on the attribute selection screen in FIG. 6) preselected according to an operation from the user, from among the plurality of types of first attributes and the plurality of types of second attributes, In response to the establishment of predetermined conditions (for example, an on / off operation on the favorite filter 20 displayed on the home screen of FIG. 10, the community screen of FIG. 11, or the distribution schedule screen of FIG. 27), content information regarding content associated with a first attribute preselected and stored by the user (for example, content headings (60, 70) of content posted in a community preselected by the user and stored in the user information database of FIG. 7) is presented to the user in a first display state that enables identification (for example, as shown in FIG. 15(B), the home screen of FIG. 10 or the community screen of FIG. 11 is displayed with the favorite filter 20 turned off according to step S203 of FIG. 16). And content information regarding content associated with both a first attribute and a second attribute preselected and stored by the user (for example, content headings (60, 70, 90) of the article of FIG. 14, where the talent ID of the favorite talent is associated, among the content posted in the community preselected by the user and stored in the user information database of FIG. 7) is presented to the user in a second display state that enables identification (for example, by an operation to turn on the favorite filter 20, according to step S204 of FIG. 16, the screen with the favorite filter 20 turned on as shown in FIG. 15(A)). A step (for example, steps S201 to S204 of FIG. 16) is provided for switching and displaying in any of a plurality of types of display states including these. 、 Each of the plurality of types of first attributes is a group including at least any one of the plurality of types of second attributes, and each of the plurality of types of second attributes is an attribute that can belong to at least any one of the plurality of groups corresponding to the plurality of types of first attributes. This is the case.

[0047] According to such a configuration, the user can identify, by means of the display switching means, content information regarding content associated with a first attribute preselected by the user and content information regarding content associated with both a first attribute and a second attribute preselected by the user. As a result, the user can easily identify preferred information.

[0048] (22) A system (e.g., communication system 1) according to an aspect of the present invention is a system having a computer (e.g., distribution server 100, user terminal 300) that performs processing for enabling a user to be provided with a plurality of types of content (e.g., news articles, posted articles, videos, etc.) associated with attributes, The attributes include a plurality of types of first attributes (e.g., community A, community B, etc. in FIG. 6(A) corresponding to the affiliated group 1 of the talent information database in FIG. 5) and a plurality of types of second attributes (e.g., talents stored in the talent information database in FIG. 5, or units of the affiliated group 2, etc.), Storage means for storing in a specifiable manner an attribute (e.g., the participating community and favorite talent selected in steps S103, S107, etc. in FIG. 9 on the attribute selection screen in FIG. 6) preselected according to an operation from the user among the plurality of types of first attributes and the plurality of types of second attributes (e.g., the account management unit 133 stores the participating community and favorite talent ID in association with the user ID in the user information database in FIG. 7 as account information 125 in steps S104, S108 in FIG. 9), In response to the fulfillment of predetermined conditions (for example, an on / off operation on the favorite filter 20 displayed on the home screen of FIG. 10, the community screen of FIG. 11, or the distribution schedule screen of FIG. 27), content information regarding content associated with a first attribute preselected and stored by the user (for example, content headings (60, 70) of content posted in a participating community preselected by the user and stored in the user information database of FIG. 7) is presented to the user in a first display state that enables the user to identify it (for example, as shown in FIG. 15(B), the home screen of FIG. 10 or the community screen of FIG. 11 can be displayed with the favorite filter 20 turned off according to step S203 of FIG. 16). And content information regarding content associated with both the first attribute and the second attribute preselected and stored by the user (for example, content headings (60, 70, 90) of the article of FIG. 14 in which the talent ID of the favorite talent is associated, which is content posted in a participating community preselected by the user and stored in the user information database of FIG. 7) is presented to the user in a second display state that enables the user to identify it (for example, by an operation to turn on the favorite filter 20, according to step S204 of FIG. 16, the screen with the favorite filter 20 turned on as shown in FIG. 15(A)). There is provided display switching means (for example, content management unit 132, account management unit 133, input information transmission unit 353, display control unit 352) for switching and displaying in any one of a plurality of types of display states including these 、 Each of the plurality of types of first attributes is a group including at least any one of the plurality of types of second attributes, and each of the plurality of types of second attributes is an attribute that can belong to at least any one of the plurality of groups corresponding to the plurality of types of first attributes. .

[0049] According to such a configuration, the user can identify, by means of the display switching means, content information regarding content associated with the first attribute preselected by the user and content information regarding content associated with both the first attribute and the second attribute preselected by the user. As a result, the user can easily identify the information according to their preference.

Brief Description of the Drawings

[0050]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Embodiments for Carrying Out the Invention

[0051] Hereinafter, embodiments of the communication system according to the present invention will be described with reference to the drawings. It should be noted that the present invention is not limited to the following examples, but is defined by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included in the present invention. In the following description, the same reference numerals are assigned to the same elements in the description of the drawings, and duplicate descriptions will not be repeated.

[0052] In the communication system according to the present invention, it is possible to provide a plurality of types of content associated with attributes to a user. The attributes include a plurality of types of first attributes (e.g., communities) and a plurality of types of second attributes (e.g., talents), and content information (e.g., the title of a news post, etc.) regarding the content (e.g., a news post related to a talent) associated with the attributes can be displayed. The content information can be switched and displayed in any of a plurality of types of display states including a first display state (push filter off) in which the user can identify the content information associated with a community or the like preselected by the user by a switching operation from the user for a predetermined icon or the like, and a second display state (push filter on) in which the user can identify the content information associated with both a community or the like and a talent or the like preselected by the user.

[0053] In addition, the plurality of types of content provided in the communication system according to the present invention are provided via a fan community that is a gathering of users who support a specific target (e.g., a talent, etc.). In the community space of the fan community, communication between users can be promoted by reflecting the actions taken by each user so that other users can recognize them. The users who use the community are associated with an evaluation history status that varies according to an external evaluation that is an evaluation from outside the user himself / herself. When an external evaluation is made on an action taken by a user in the community (e.g., content or comments posted by the user), the actions that the user can take in the community are controlled.

[0054] FIG. 1 is a diagram showing an example of the hardware configuration of the communication system 1. The communication system 1 includes a distribution server 100, an administrator terminal 200, a plurality of user terminals 300a, 300b, 300c..., and an external web service system 400. The plurality of user terminals 300a, 300b, 300c... are terminals owned by each of the plurality of users, and are hereinafter also collectively referred to as the user terminal 300.

[0055] The distribution server 100, the administrator terminal 200, and the user terminal 300 can each be communicatively connected via the network 2 and can transmit and receive information (data) bidirectionally. The network 2 is, for example, the Internet and is composed of access networks such as LAN (Local Area Network), WAN (Wide Area Network), mobile communication networks (e.g., 5G, wireless network, etc.), wired telephone networks, FTTH (Fiber To The Home), and CATV (Cable Television) networks.

[0056] Also, the distribution server 100, the administrator terminal 200, and the user terminal 300 can be communicatively connected to an external web service system 400 via the network 2. The external web service system 400 is, for example, a sharing service (e.g., Youtube (registered trademark)) for videos, texts, images, etc. by user submissions, and provides a Web API (Application Programming Interface) that can supply information (e.g., text, image, video, posting date and time, account name, etc.) corresponding to access from other terminals such as the distribution server 100, the administrator terminal 200, and the user terminal 300 to the terminal. The external web service system 400 is a system operated and managed by a third party other than the administrator and operator of this communication system 1.

[0057] The distribution server 100 is a computer such as a workstation or a personal computer having a communication function, for example. The distribution server 100 manages a plurality of contents that can be provided to users and manages the communities where the contents are provided. The distribution server 100 provides the contents in response to requests from users via the network 2.

[0058] The content provided by the distribution server 100 is managed and set for each type, as will be described later with reference to FIG. 14. Content is something that notifies viewers of predetermined information and includes the content of information such as videos, audio, and text. The content managed by the distribution server 100 includes, for example, news and announcements articles by an operator (administrator), user submissions, and distribution videos provided by external web services obtained by using a Web API. The said content can be provided to users by being displayed on a user terminal 300 via a medium such as a browser or a dedicated application for a smartphone. Also, the medium through which the said content is provided also functions as a fan community that supports a predetermined support target.

[0059] The distribution server 100 stores in the storage unit 120 information such as text and images corresponding to the content that can be provided to users for display on the user terminal, and sound information for outputting sound. Also, in response to an access from the user terminal 300, the distribution server 100 distributes content data including display information for displaying text, images, etc. of the corresponding content and sound information for outputting sound, thereby providing content (service) to the user.

[0060] The administrator terminal 200 is used by an operator of a service providing company or the like. The administrator terminal 200 is, for example, a computer having an operation input function and a communication function such as a personal computer. The operator creates content (hereinafter also referred to as submission information) managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200, and constructs, modifies, and updates display information related to the display of the content. For example, generation and construction of images for displaying new content etc. on the user terminal 300, and change and modification of images of already provided content etc. are performed. Also, the operator performs setting and updating of information managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200. Also, in the administrator terminal 200, it is also possible to perform settings such as permission and restriction regarding actions on various contents of users.

[0061] In the present embodiment, the distribution server 100 and the administrator terminal 200 are each an independent computer (device), but they may also be realized by a single computer, or the function of one of these computers (for example, the distribution server 100) may be realized by a plurality of computers (for example, a plurality of servers).

[0062] The user terminal 300 is used by a user who views and experiences content, etc. The user terminal 300 may be, for example, a computer having operation input functions and communication functions such as a personal computer, a tablet terminal, or a smartphone.

[0063] The user terminal 300 communicates with the distribution server 100 in response to an operation on the terminal and receives the content data of the content selected by the user. Further, based on the received content data, the user terminal 300 constructs, in the storage area of the user terminal 300, the posting information of the content selected by the user among the content managed in the distribution server 100, and displays the image and text of the posting information. Thereby, through the user terminal 300, the user can identify and recognize the information of the content.

[0064] In addition, the user terminal 300 accepts action operations on the displayed content and content posting operations by the user himself / herself. The user terminal 300 transmits information corresponding to the operations on the terminal (for example, information for specifying actions and posted content) to the distribution server 100, and can reflect actions and posted content to a plurality of user terminals via the distribution server 100. Action operations include, for example, tap actions indicating favorable expressions of intention such as liking or empathizing with the content (so-called "like" functions, etc.), and comment posting. Hereinafter, actions by the user such as content posting operations by the user himself / herself are also collectively referred to as actions. Further, it is also referred to as a favorable action including tap actions by the user and favorable comments.

[0065] Users in the present embodiment include consumers who are general consumers (also referred to as general users or simply users), talents, famous people, etc. Talents include, for example, talents belonging to a service providing company (operating company), entertainers, actors / actresses, comedians, multi-talents, emcees, newscasters, singers, musicians, models, etc., including various genres of capable people. Famous people include, for example, famous company managers or employees, sports players, e-sports players, famous scholars / cultural figures / tutoring teachers, famous students, etc., including various genres of famous people. Hereinafter, talents other than general users, or famous people, etc. are also referred to as special users.

[0066] Note that a special user may be a general user who browses content distributed using a terminal with the same configuration as the user terminal 300, or may be a general user using a separate terminal with a different configuration from the user terminal 300. Therefore, the user terminal used by a special user and the user terminal 300 used by a general user may be the same terminal or different terminals in terms of configuration.

[0067] <Configuration of the distribution server> Next, the configuration of the distribution server 100 will be described. As shown in FIG. 2, the distribution server 100 includes a communication unit 110 that communicates with other computers, a storage unit 120 that stores various data, and a control unit 130 that controls the entire computer. The communication unit 110, the storage unit 120, and the control unit 130 are interconnected by a bus line.

[0068] The communication unit 110 is a communication interface including a NIC (Network Interface Card controller) for performing wired communication or wireless communication. The communication unit 110 communicates with other computers via the network 2.

[0069] The storage unit 120 is composed of a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an HDD (Hard Disk Drive), and the like. The storage unit 120 stores programs for executing various control processes (for example, programs for managing and providing content), various data, and the like. The various data stored in the storage unit 120 includes posting information provided for each type of content, information regarding attributes, user information regarding users, and the like.

[0070] The control unit 130 is composed of a CPU (Central Processing Unit) and the like. The control unit 130 controls the overall operation of the distribution server 100 by executing the programs stored in the storage unit 120.

[0071] Hereinafter, the functional configuration of the control unit 130 will be described. The control unit 130 functions as at least a data transmission / reception unit 131, a content management unit 132, and an account management unit 133.

[0072] The data transmission / reception unit 131 receives various types of information transmitted from the user terminal 300 and transmits various types of information to the user terminal 300. The data transmission / reception unit 131 refers to various management tables stored in the storage unit 120. The various types of information for which the data transmission / reception unit 131 performs transmission and reception include, for example, information regarding the content managed by the content management unit 132 and various notifications.

[0073] The content management unit 132 stores and updates, in the storage unit 120, information for specifying text, images, etc. corresponding to the content posted by the administrator terminal 200 or the user terminal 300 via the communication unit 110. The content management unit 132 stores, as the attribute information 121 in the storage unit 120, for example, information regarding attributes that can be associated with the content provided to the user. The content management unit 132 stores and updates, as the content data 122 in the storage unit 120, information for specifying information such as the category of the content posted by the administrator terminal 200 or the user terminal 300, the poster, and the attributes associated with each content. Further, the content management unit 132 stores and updates, as the action information 123, information for specifying the type, etc. regarding the actions performed on the content, and stores, as the action permission information 124 in the storage unit 120, information regarding the permissions regarding the actions that can be taken on the content.

[0074] The account management unit 133 stores and updates, in the storage unit 120, user information regarding users who can use the content managed by the distribution server 100, for example, as the account information 125. The user information regarding the user includes, for example, an ID for identifying the user, a user name, permission action information regarding the actions that the user can take, etc. The user information managed by the account management unit 133 includes not only the accounts of general users but also the accounts of special users and the account information for identifying posts by the administrator terminal 200, etc.

[0075] <Configuration of the administrator terminal> Next, the configuration of the administrator terminal 200 will be described. As shown in FIG. 3, the administrator terminal 200 includes a communication unit 210 that communicates with other computers, a storage unit 220 that stores various data, an input unit 230 for inputting operations, etc., an output unit 240 for outputting images, sounds, etc., and a control unit 250 that controls the entire computer. The communication unit 210, the storage unit 220, the input unit 230, the output unit 240, and the control unit 250 are interconnected by a bus line.

[0076] The communication unit 210 is a communication interface including a NIC for performing wired or wireless communication. The communication unit 210 mainly communicates with the distribution server 100 via the network 2. The storage unit 220 is composed of a RAM, a ROM, etc. The storage unit 220 stores programs for executing various control processes (for example, a program for managing content provided to users by the distribution server 100), various data, etc.

[0077] The input unit 230 includes an input device for receiving input operations from the administrator (for example, a pointing device such as a touch panel, a touch pad, a mouse, etc., a keyboard, etc.). The output unit 240 includes an output device (a display, a speaker, etc.) for presenting information to the administrator.

[0078] The control unit 250 is composed of a CPU, etc. The control unit 250 controls the overall operation of the administrator terminal 200 by executing the programs stored in the storage unit 220.

[0079] Hereinafter, the functional configuration of the control unit 250 will be described. The control unit 250 functions as at least a content setting unit 251, an attribute setting unit 252, an action authority setting unit 253, and a user evaluation information update unit 254.

[0080] The content setting unit 251 stores and updates information regarding the content managed by the content management unit 132 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, information for specifying content, categorization of content, and information such as settings and editing regarding effects when the content is provided can be stored and updated in the storage unit 120 of the distribution server 100.

[0081] The attribute setting unit 252 stores and updates attribute information regarding attributes stored as the attribute information 121 of the distribution server 100 in response to an operation on the administrator terminal 200. Thereby, for example, information regarding attributes when a new attribute is added or when there is a change in the composition of attributes can be stored and updated in the storage unit 120.

[0082] The action restriction setting unit 253 stores and updates information regarding the authority to perform actions such as content posting actions and actions indicating reactions to content within the provided community space, which are managed as the action information 123 and action authority information 124 of the distribution server 100, in response to an operation on the administrator terminal 200. Thereby, for example, addition and change of actions (actions) set for each evaluation history status of a user described later, and setting of individual action restrictions for users by the operator can be stored and updated in the storage unit 120.

[0083] The user evaluation information update unit 254 can perform external evaluations on users that can affect the evaluation history status for each user stored as the account information 125 of the distribution server 100, or store and update the evaluation history status itself for each user, in response to an operation on the administrator terminal 200. Thereby, the evaluation history status for each user is varied by the evaluation from the operator, and the actions (actions) that the user can take based on the action authority information 124 are controlled.

[0084] <Configuration of the user terminal> Next, the configuration of the user terminal 300 will be described in detail. As shown in FIG. 4, the user terminal 300 includes a communication unit 310 that communicates with other computers including the distribution server 100, a storage unit 320 that stores various data, an input unit 330 for inputting operations and the like, an output unit 340 for outputting images and the like, and a control unit 350 that controls the entire computer. The communication unit 310, the storage unit 320, the input unit 330, the output unit 340, and the control unit 350 are interconnected by a bus line.

[0085] The communication unit 310 is a communication interface including a NIC for performing wired or wireless communication. The communication unit 310 communicates with other computers including the distribution server 100 via the network 2. The storage unit 320 is composed of a RAM, a ROM, and the like. The storage unit 320 stores programs for executing various control processes (for example, programs for browsing content and the like), various data, and the like.

[0086] The input unit 330 includes input devices (for example, pointing devices such as touch panels, touch pads, mice, keyboards, microphones, etc.) for receiving input operations and voices from the user.

[0087] The output unit 340 includes output devices (displays, speakers, etc.) for presenting and outputting information (text, images, voices, etc.) to the user. The control unit 350 is composed of a CPU and the like. The control unit 350 controls the overall operation of the user terminal 300 by executing the programs stored in the storage unit 320.

[0088] Hereinafter, the functional configuration of the control unit 350 will be described. The control unit 350 functions as an information acquisition unit 351, a display control unit 352, an input information transmission unit 353, and a user management unit 354.

[0089] The information acquisition unit 351 acquires content data and the like from the distribution server 100 via the communication unit 310, and stores in the storage unit 320 information for displaying text and images (posting information) related to the content based on the content data. The posting information includes information for causing the user terminal 300 to display actions performed on the content by other user terminals 300.

[0090] The display control unit 352 causes the content information (for example, the title of the content article, etc.) related to the content stored in the storage unit 320 to be displayed so that the user can identify it based on the content data acquired by the information acquisition unit 351. For example, by displaying the title of a news article related to a talent on the user terminal 300, the user can recognize that it is content of news related to the talent.

[0091] Also, the display control unit 352 displays a UI (User Interface) image (including, for example, a menu image that the user can select and an operation image that accepts operations) in a manner corresponding to the content being distributed based on the program stored in the storage unit 320.

[0092] The input information transmission unit 353 transmits voice information and operation input information acquired by the input unit 330 to the distribution server 100. The operation input information includes actions on various contents in the displayed community space (for example, comments and tap actions), posting information of contents into the community space by the user himself / herself, and selection operations on various icons displayed on the user terminal 300.

[0093] The user management unit 354 stores and updates user information related to the user in the storage unit 320. The user information related to the user includes, for example, an ID for identifying the user, a user name, information related to attributes pre-selected by the user, and information related to actions that the user can take (permitted or restricted) within the community.

[0094] <Regarding the content providing function of the fan community> (Overview of the fan community) Hereinafter, the fan community that enables viewing of the content provided by the distribution server 100 according to the present embodiment will be described in more detail. The content provided by the distribution server 100 is provided by a dedicated application (program (for example, a program for a native application, etc.)) that operates on a terminal such as a smartphone or a tablet. The dedicated application functions as a so-called fan community used by users who support a common target (for example, a talent, a character, a good, etc.). In the fan community, in addition to facilitating the fan activities of users by providing content related to the common target (making it viewable by users), not only can users who are fans communicate with each other, but also the user's support target and the user can communicate with each other. Note that the content may be provided not only by a dedicated application but also via a browser by a web application. Further, the content may be provided via a fan community provided via a browser by a web application.

[0095] The support target in the present embodiment can be various targets such as characters or objects as long as the user can have affection, interest, concern, etc. For example, the character includes real people such as talents and famous people (3D), and fictional existences such as anime characters and mascot characters (2D, 2.5D). In addition, the support target includes objects such as railways and animals.

[0096] (Specific examples of attributes in the fan community) Hereinafter, in this embodiment, an example will be described in which the target of support by the user is a talent, and the fan community is the fan community of the talent. In this embodiment, the talents are classified into a large group (also referred to as the first attribute) consisting of a plurality of talents. Further, the talents classified into the large group can also be divided into small groups (also referred to as the second attribute) composed of a smaller number of people than the large group. For example, the small group is a unit group composed of a part of the talents belonging to the large group.

[0097] As a unit (attribute) that the user who uses the fan community supports, there may be cases where the user supports not only one talent but also multiple talents, in units of small groups (units), or in units of large groups. For example, supporting (becoming a fan) in units of a large group is also called so-called box pushing. In the fan community in this embodiment, the user can set (select) in advance the target to be supported by the user for each preferred unit (each attribute).

[0098] Referring to FIG. 5, an example of the talent information database stored as the attribute information 121 in this embodiment will be used to describe the talents in the fan community in this embodiment. In this embodiment, the talents are classified into groups classified as "affiliated group 1". The affiliated group 1 is a large group, and is classified into, for example, group A, group B, and so on.

[0099] For each affiliated group 1, "talent ID", "talent name", etc. are associated as information for identifying the talents belonging to the group. Further, for each talent, information for identifying the "affiliated group 2" to which each talent belongs is associated. The affiliated group 2 is a small group composed of a smaller number of people than the affiliated group 1. For example, it is "first-generation students", "second-generation students", etc. classified in units of the time of joining the group, or a group composed of a predetermined concept (for example, "Gamers" composed of talents centered on live game broadcasts).

[0100] Regarding the affiliated group, some talents may belong to multiple affiliated groups. Also, the affiliated group 1 may include talents who belong to affiliated group 1 but do not belong to any affiliated group 2. Additionally, there may be an affiliated group 2 composed of talents belonging to different affiliated groups 1 (constituted across different affiliated groups 1. For example, group A and group B, etc.).

[0101] For example, a talent with talent ID "t1" and talent name "AAA" belongs to affiliated group 1 "group A" and affiliated group 2 "A - 1st generation students". On the other hand, a talent with talent ID "t6" and talent name "FFF" belongs to affiliated group 1 "group A", but belongs to two groups, "A - 3rd generation students" and "A - Gamers", in affiliated group 2.

[0102] <Specific examples of attribute selection processing> (Screen example for attribute selection) Next, with reference to FIGS. 6 to 9, an example of a screen and a processing flow in which a user using a fan community selects an attribute (group or talent) to support will be described. The selection (setting) screen for the attribute to support illustrated in FIG. 6 is displayed on the user terminal 300 when starting to use the fan community application or by requesting a setting change from the my page or the like. In the fan community in the present embodiment, it is possible to participate in a community (first attribute) corresponding to the talent's affiliated group 1 (first attribute) described with reference to FIG. 5. FIG. 6(A) is an example of a participation community setting screen, and the user can select (set) a community (first attribute) to participate in from among a plurality of types of first attributes. For example, the participation community setting screen in FIG. 6(A) includes a participation community selection area 50. In the participation community selection area 50, icons for each community that the user can participate in are displayed. The user can select a participation community by selecting the icon of the community that the user wishes to participate in. Also, a check mark or the like is displayed for the community for which the selection of participation has been made.

[0103] "Community A" corresponds to "Group A" in FIG. 5, and "Community B" corresponds to "Group B" in FIG. 5. That is, the plurality of types of first attributes include Group A, or Community A corresponding to Group A, Group B, or Community B corresponding to Group B. Note that, as displayed in FIG. 6(A) as "※ Always participating in Community P.", there may be a community that always participates regardless of the user's selection. For example, "Community P" does not correspond to the talent's affiliated group and is a community for making announcements for the entire fan community and the like.

[0104] FIG. 6(B) is an example of a favorite talent setting screen, where the user can select (set) a favorite talent (second attribute). The favorite talent setting screen in FIG. 6(B) includes, as an example, a search window 51, an affiliated group selection area 52, a talent selection area 53, and the like. The search window 51 enables searching for talents by inputting keywords. In the affiliated group selection area 52, icons of groups (affiliated groups 1, corresponding to communities) that can be supported in the fan community application are displayed. By selecting an icon, for example, talents can be displayed for each affiliated group 1. Note that in the affiliated group selection area 52, it may be possible to select all groups. Also, icons that can be selected and displayed for each unit may be displayed.

[0105] In the talent selection area 53, icons and names of each talent are displayed. However, as illustrated in FIG. 6(B), they may be displayed, for example, in the order of each unit. By performing a selection operation on the icon or the like of each talent, a favorite talent can be selected. Also, a check mark or the like is displayed on the icon of the selected talent.

[0106] Note that it may be possible to select all the talents of a group as favorite talents by operating the icon in the group selection area 52. Alternatively, an icon of "select all" may be displayed, and all the talents displayed by the selection operation may be selectable. Also, not only for each talent, but it may be possible to select favorite talents in unit units (affiliated group 2 units), and it may be possible to select the most favorite (the most favored talent among the favorite talents).

[0107] (Example of user information database regarding the selected attribute) FIG. 7 is an example of a user information database stored as account information 125. In the user information database, for each user, a "user ID" for identifying the user, a "level", "cumulative points", "communities participated in", "favorite talent ID", etc. are associated. For the "communities participated in" and "favorite talent ID", information for identifying the attributes selected by the user on the setting screen illustrated in FIG. 6 is associated. For example, if the setting screen in FIG. 6 is the setting screen for user ID "u1" in FIG. 7, and the user ID "u1" has selected "Community A" as the community participated in in FIG. 6(A) and has selected talents "AAA", "BBB", and "EEE" in FIG. 6(B), then for user ID "u1", the affiliated community is "Community A" and the favorite talent IDs are "t1", "t2", and "t5" corresponding to each talent. Hereinafter, the user ID will also be simply referred to as the user. Note that the "level" and "cumulative points" vary depending on the actions of the user within the fan community, and the details will be described later.

[0108] (Example of My Page for Each User) FIG. 8 is an example of a My Page screen for each user in the fan community. For example, due to a selection operation from the user for the My Page icon 16, the user terminal 300 acquires the information of the corresponding user stored as account information 125 and displays it on the user terminal 300. On the My Page screen, as an example, a name area 54, a user evaluation history status 55, favorite talent information 56, community participation settings 57, notification settings 58, settings and app information 59, etc. are displayed, and editing operations such as various setting changes can be performed.

[0109] The my page screen in Fig. 8 is a screen displayed on the user terminal 300 of the user "u1". In the name area 54, the name "userA" used within the fan community of the user "u1" and an icon image are displayed. The icon image can be, for example, the fan mark of a talent. A fan mark is something like a symbol used by a talent to represent themselves, and by fans using the same fan mark, it is possible to publicly indicate which talent's fans they are. For example, it can be edited by tapping the image editing icon displayed in the lower right of the icon image or selected and set on the initial setting screen.

[0110] In the user evaluation history status 55, the "level" and "cumulative points" associated with each user in the user information database in Fig. 7 are displayed so that the user himself / herself can confirm them. Details of the evaluation history status will be described later.

[0111] In the favorite talent information 56, the talents pre-selected by the user are displayed so that the user himself / herself can identify (confirm / recognize) them. For example, the icons and names of each talent are displayed so that the user "u1" can confirm the talents "AAA", "BBB", and "EEE" selected and set on the favorite talent setting screen in Fig. 6(B). Also, the favorite talents can be appropriately changed by operating the editing icon displayed in the favorite talent information 56 to display the screen in Fig. 6(B).

[0112] Also, when there is a selection operation for the participating community setting 57, the participating community setting screen in Fig. 6(A) is displayed, and the participating community can be appropriately changed.

[0113] When operations are performed on the notification settings 58 or the settings and app information 59, it is possible to perform operations such as push notification settings and various setting operations for the fan community app. Note that the my page in FIG. 8 only needs to be able to display and edit the user's own information. For example, regarding the participating communities, a list of the participating communities may be displayed on the initial screen of the my page (such as the screen displayed when the my page icon 16 is operated), similar to the favorite talent information 56. Also, the change screens for the participating communities and the favorite talents (FIG. 6) may be collectively displayed by operating a single edit icon.

[0114] (Example of the flow of attribute selection processing) Next, with reference to FIG. 9, the flow of the attribute selection processing will be described. FIG. 9 is a diagram for explaining the flowchart of the attribute selection processing described with reference to FIG. 6. The attribute selection processing is repeatedly executed in the account management unit 133 in response to receiving a request (such as operation information) from the user terminal 300 in the distribution server 100.

[0115] In step S101, it is determined whether it is the first login. The first login is, for example, when the user first downloads and launches the fan community app in this embodiment, or when the user first uses the fan community app in this embodiment via a web browser, etc., which is the timing for performing attribute settings in the fan community for the first time. When it is determined in step S101 that it is the first login, in step S102, information for displaying an attribute selection screen is transmitted to the display unit of the user terminal 300. The attribute selection screen is, for example, the setting screen for selecting the participating communities and the favorite talents exemplified in FIG. 6, and may be incorporated into the flow of the tutorial at the first login (such as the basic explanation at the first login).

[0116] Next, in step S103, at the user terminal 300, it is determined whether an operation of selecting and confirming a participating community and a favorite talent has been performed. For example, among the participating communities displayed in the participating community selection area 50 in FIG. 6(A), the user performs a selection operation on the community that the user wishes to participate in. Also, in FIG. 6(B), among the talents displayed in the talent selection area 53, the user selects a favorite talent. Note that, on the attribute selection screen in FIG. 6, an icon for performing a confirmation operation, such as a determination icon, may be displayed. When information (including information capable of specifying the selected participating community and favorite talent) transmitted by operating the determination icon or an icon such as "Next" is received, it may be determined that a confirmation operation has been performed. When it is not determined in step S103 that the selection and confirmation of the participating community and the favorite talent have been made, the determination is repeatedly made in step S103 until a selection and confirmation operation is performed.

[0117] On the other hand, when it is determined that the selection and confirmation of attributes have been made due to a selection operation on the determination icon or the like at the user terminal 300, the process proceeds to step S104, and the selected participating community and the selected favorite talent are stored as the selected attributes based on the information received from the user terminal 300. For example, the account management unit 133 associates the selected participating community and the selected favorite talent ID with the user "u1" and stores them as account information 125 to end the process.

[0118] Return to step S101. When it is not determined in step S101 that it is the first login, in step S105, it is determined whether there is a request to edit the participating community setting or the favorite talent setting. For example, when there is an operation on the edit icon of the favorite talent information 56 on the my page illustrated in FIG. 8 or an operation on the participating community setting 57 at the user terminal 300, it is determined that there is a request to edit.

[0119] In step S105, when it is determined that there is an editing request, in step S106, information for displaying a participating community setting or a setting editing screen for a favorite talent on the user terminal 300 is transmitted. As a result, for example, an attribute selection (setting) screen illustrated in FIG. 6 is displayed. On the other hand, in step S105, when it is not determined that there is an editing request for the participating community setting or the favorite talent setting, the process ends.

[0120] After the setting editing screen is displayed in step S106, in step S107, it is determined whether a participating community or a favorite talent has been selected. For example, when a selection operation is performed on the display of each participating community in FIG. 6(A) or the display of each talent in FIG. 6(B) on the user terminal 300, information (including information capable of specifying the selected participating community and favorite talent) is transmitted, and it is determined that a selection has been made by receiving the information.

[0121] In step S107, when it is determined that a participating community or a favorite talent has been selected, in step S109, the selected participating community or the selected favorite talent is updated and stored as the selected attribute, and the process ends. For example, in the distribution server 100, based on the information corresponding to the attribute selection operation received from the user terminal 300, the user information database in FIG. 7 stored as the account information 125 is updated and stored.

[0122] Return to step S107. When it is determined that the selection of the participating community or the favorite talent has not been made, it is determined whether the selection to return is made in step S109. For example, on the attribute selection screen of FIG. 6, a return icon 10 is displayed, and it is determined whether there is a selection operation on the return icon 10. When it is determined that there is a selection operation on the return icon 10, the process ends. Alternatively, the process may end by moving to another screen by operating the home icon 13 or the like displayed at the bottom of the application. On the other hand, when it is not determined in step S107 that the selection to return is made, return to step S107.

[0123] As a result, as will be described later, it becomes possible to extract and display information regarding the attributes preselected by the user in the fan community, so that the user can extract and obtain information regarding the favorite affiliated group 1 (first attribute) and further information regarding each talent (second attribute). Although an example in which the attribute selection process is executed by the distribution server 100 has been described, it may be executed by the user terminal 300.

[0124] <Example of content provision mode> (Overview of the content list screen) Next, an example of the content provision mode provided by the distribution server 100 via the fan community will be described with reference to FIGS. 10 to 14. FIG. 10 is an example of the home screen in the fan community application (hereinafter also simply referred to as the application) of the present embodiment. The home screen is displayed, for example, on the user terminal 300 when logging in to the application (for example, when the application is started) or when a selection operation is performed on the home icon 13 displayed at the bottom of the application. Information (title of the content article) for specifying the content displayed on the home screen of FIG. 10 mainly displays information for specifying the content posted in the community in which the user participates.

[0125] Note that the channel icon 12 displayed at the top of the app can display a list of channels for each participating community as illustrated in FIG. 12, can be displayed on any screen of the app, and may be hidden on a predetermined screen (for example, when the content is displayed as in FIG. 13). A channel is, for example, classified by the type of topic (theme). The search icon 17 displayed at the top of the app is an icon for searching for content. The search icon 17 may be displayed, for example, on the home screen of FIG. 10 or on a screen for each community such as FIG. 11(A) described later when a list of content headings is displayed.

[0126] Also, the home icon 13, community icon 14, notification icon 15, and my page icon 16 displayed at the bottom of the app may be displayed on any screen within the app, and may be hidden on a predetermined screen (for example, when the content is displayed as in FIG. 13). As described above, the home icon 13 is an icon for displaying the home screen of FIG. 10 when a selection operation is performed, and the community icon 14 is an icon for displaying a screen for each community such as FIG. 11(A) described later when a selection operation is performed. The notification icon 15 is an icon for displaying a screen where various notifications can be confirmed, such as when there is a post related to the selected attribute (for example, the talent set by the user as the favorite talent), a reply comment to the user's own post, or a mention to the user. The my page icon 16 is an icon for displaying the my page illustrated in FIG. 8 when a selection operation is performed.

[0127] (Overview of the Home Screen) At the upper part of the home screen in FIG. 10, a favorite filter 20, a language switching icon 21, etc. are displayed. The favorite filter 20 is a filter icon that can narrow down the displayed list of content headings so that only the headings of the content associated with the favorite talents preselected by the user are displayed. Details will be described later with reference to FIGS. 15, 16, etc. The language switching icon 21 is an icon that enables switching of the displayed language when a selection operation is performed, such as switching from Japanese to English.

[0128] The content provided by the distribution server 100 can be classified into any of multiple types of categories, and on the home screen, the content can be displayed for each classified category. On the content list (heading) screen of the home screen, for example, content headings 60 (content information) of content (also referred to as articles / threads) are displayed for each category such as a feature 61, a favorite topic 62, popular user posts 63, commemorative distribution 64, goods 65, etc. For example, the feature 61 displays notice articles or the like that the content setting unit 251 has set to inform all users, such as notices from the operator. The content displayed in the feature 61 is displayed regardless of which participating community and which favorite talents the user has selected. Also, when a selection operation is performed on the headings, images, etc. displayed in the feature 61, it may be configured to transition to a screen showing detailed information or an external website, etc.

[0129] Regarding the categories after the favorite topic 62, the content posted within the participating communities is displayed. The "community" in the app in this embodiment refers to the communities A to C corresponding to each affiliated group to which the talent belongs, exemplified in FIG. 6, and the community P in which the user is always in a participating state, etc.

[0130] (Regarding the community channel list screen) Referring to FIGS. 11 to 14, the details of the "Community" of the application in this embodiment will be described. FIG. 11(A) is an example of a content list (heading) screen of "Community" (hereinafter, also referred to as a community screen or a channel screen). Each community is classified into channels for each type of topic as shown in FIG. 12. For example, the community screen in FIG. 11(A) is a screen of the "Official Channel" of the community "Community A" (corresponding to group A exemplified in FIG. 5), and the channel screen displayed in FIG. 11(A) is switched by a selection operation of a channel in the channel list screen in FIG. 12.

[0131] The channel list screen illustrated in FIG. 12 is displayed by, for example, a tap operation on the channel icon 12 displayed at the upper part of the application screen (for example, FIG. 10), or a flick operation (for example, a flick operation from the left side to the right side of the application screen). When the channel list screen in FIG. 12 is being displayed, the list screen can be closed by performing an operation when it was displayed (such as a selection operation on the channel icon 12 or a flick operation to return from the right side to the left side of the application screen).

[0132] On the channel list screen in FIG. 12, a community bar 81, a favorite confirmation icon 31, one's own post icon 32, a start icon 33, a notification setting icon 34, etc. are displayed. The communities displayed on the community bar 81 include the communities that the user has joined (selected). By performing a selection operation on the open / close icon displayed on the community bar 81, a channel list 82 for each community is displayed. For example, each channel name is displayed in the channel list 82 corresponding to Community A. The selection bar 83 displayed beside each channel name indicates which channel is selected.

[0133] For example, FIG. 12 shows a screen displayed on the user terminal 300 of the user "u2" illustrated in FIG. 7. Since the communities that the user "u2" belongs to are "Community A" and "Community B", the channel screen list in FIG. 12 displays the channel bar 81a of "Community A", the channel bar 81b of "Community B", and the channel bar 81c of "Community P" that the user always participates in. Since the selection bar 83 is displayed next to the "Official Channel" of "Community A", it indicates that the community screen shown in FIG. 11(A) is the "Official Channel" of "Community A". For example, by performing a selection operation on the channel name displayed in the channel list 802, the selection bar 802b moves. As a result, the "Official Channel" of "Community A" in FIG. 11(A) is displayed on the app screen.

[0134] When there is a selection operation on the channel list screen in FIG. 12, it may switch to the community screen in FIG. 11(A). Also, as shown in FIG. 12, the channel list screen can be displayed so as to be superimposed on another screen. By closing the channel list screen in FIG. 12 after the screen displayed below the channel list screen switches to the screen of the selected channel, the community screen in FIG. 11(A) may be displayed in its entirety. Further, when a selection operation is performed on the community icon 14 displayed at the bottom of the app screen when a channel is selected on the channel list screen in FIG. 12, the selected channel is also displayed as the community screen in FIG. 11(A).

[0135] The favorite confirmation icon 31 in FIG. 12 is an icon that enables the user to confirm the content (also referred to as a post) registered as a favorite in the account information 125 or stored in the storage unit 320 when a selection operation is performed. The self-post icon 32 is an icon that enables the user to confirm the content (thread created) posted by the user himself / herself in the community, or comments made by the user himself / herself on the content (thread created) when a selection operation is performed. First, the icon 33 is an icon that enables the reconfirmation of the tutorial displayed at the first login, the usage method of the application, the precautions, etc. when a selection operation is performed. The notification setting icon 34 is an icon that enables the display of a screen for setting various notifications (such as the selection of information for which push notifications are sent) when a selection operation is performed. For example, the same screen as when the notification setting icon 58 illustrated in the my page of FIG. 8 is selected may be displayed.

[0136] (Regarding the community screen) On the community screen in FIG. 11(A), similar to the home screen illustrated in FIG. 10, a recommended filter 20, a language switching icon 21, a sorting icon 22, a post icon 23, etc. are displayed. The sorting icon 22 is an icon that enables the sorting of the order of the headings of the displayed content in the order of new arrivals, popularity order (for example, the order with more like actions, etc.) when a selection operation is performed. The post icon 23 is an icon that enables the user to post content (create a thread) in the community when a selection operation is performed.

[0137] Each content posted in the community is partially displayed by the content heading 70 (content information) on the community screen in FIG. 11(A). For example, content headings 70a, 70b, 70c... etc. are displayed. On each content heading 70, a poster 71, a report icon 72, a favorite icon 73, content information 74, etc. are displayed.

[0138] The contributor 71 is displayed with the icon, name, etc. of the contributor of the corresponding content. For example, if the contributor is an operator or a special user described later, it is displayed together with an official mark or the like.

[0139] When the report icon 72 is selected, a screen as shown in FIG. 11(B) is displayed (for example, pop-up displayed on the current screen). By selecting the characters displayed in FIG. 11(B), the user can, for example, report content that makes the user feel uncomfortable to the operator, hide it on the user terminal 300, or block the content contributor itself within the fan community app (prevent actions such as posts of the user who has been blocked from being displayed on the user's own user terminal 300 after the operation). Note that operations such as hiding and blocking may not be performed on operators or special users (content they posted), and may be operations that can only be performed on other general users.

[0140] The favorite icon 73 is an icon that enables saving so that the user can check the posts they like later. For example, when the favorite icon 73 is selected, the user information database of FIG. 7 stored as the account information 125 is updated and stored in association with the article ID of the post on which the favorite icon 73 was operated. As a result, the user can check the favorite posts when the favorite confirmation icon 31 in FIG. 12 is selected.

[0141] The content information 74 displays part of the title and description of the content posted.

[0142] Furthermore, for the content heading 70, if the posted content is posted together with an image, the image 75 is displayed. If there are comments on the content, comments (for example, the latest comments or a part of the most popular comments, etc.) are displayed in the picked-up comment 76. Also, the number of comments on the content is displayed as the comment number 77, and the number of tap actions on the content is displayed as the tap action number 78. The number of tap actions on the content is, for example, the total number of tap actions made by all users on the heart icon 708 displayed together with the tap action number 78 in the content headings (60, 70), or the icon 708 displayed together with the tap action number 78 on the content screen of FIG. 13 described later.

[0143] Also, users who use the fan community app include special users. When there are comments or tap actions from special users, it is possible to display that there have been comments or tap actions from special users as a special action 79 together with the icons of special users within the content heading 70. Special users are, for example, users corresponding to the talent themselves exemplified in FIG. 5. Therefore, by the display of the special action 79, users can recognize that there have been actions such as comments or tap actions from the talent themselves. As a result, in the fan community app, it is possible to promote communication with the object of support and improve user satisfaction.

[0144] Special Action 79 includes an icon corresponding to each talent, an icon that can be presumed to have a comment such as a speech bubble when there is a comment by the talent, and an icon that can be presumed to have a tap action such as a heart mark when there is a tap action by the talent. For example, in the content heading 70a on the community screen of FIG. 11, a special action 79 indicating that there has been an action from three talents is displayed. Since speech bubbles and heart marks are displayed on the icons of the talents shown on the left and in the center, it is shown that there have been comments and tap actions. On the other hand, for the talent shown on the right, only a heart mark is displayed along with the icon, indicating that only a tap action has been performed without a comment.

[0145] Also, the special action 79 to be displayed on the content heading 70 may be displayed within the content heading 60 on the home screen of FIG. 10.

[0146] FIG. 13 is an example of a content screen displayed when the content heading 70a among the contents displayed in FIG. 11(A) is selected, and is an example of a display screen of the content itself (the post itself) which is the content of the content heading 70a. In addition, in the home screen of FIG. 10, when the same content is displayed, the content screen of FIG. 13 is displayed by a selection operation on the corresponding content heading 60 on the home screen.

[0147] On the content screen of FIG. 13, a return icon 10b is displayed at the top, and the poster 71, the report icon 72, the favorite icon 73, the number of tap actions 78, the category 85, the content 74b, the related talents 88, and the special action 79, etc. are displayed. Also, when there is a comment on the content, a list of comments is displayed at the bottom. For the list display of comments, a comment number 77b indicating the number of comments, a comment 87 which is each comment, a comment posting field 84 for the user to post a comment, etc. are displayed.

[0148] When there is a selection operation for the return icon 10b, return to the screen that the user was displaying until immediately before. For example, if on this content screen, when transitioning from the community screen in Fig. 11(A), return to the community screen in Fig. 11(A), and when transitioning from the home screen in Fig. 10, return to the home screen in Fig. 10.

[0149] Category 85 is displayed with the associated category name when a category is associated with the content. In content 74b, posted text information such as the title and description of the content is displayed.

[0150] Related talent 88 is displayed when a talent in Fig. 5 is associated with the content, and displays the icon and name of the associated talent, etc. Special action 79 is a display for indicating that there has been an action from a special user corresponding to the talent in Fig. 5 for the content when there is an action from the special user for the content.

[0151] Each comment 87 displays a poster 71b who displays the comment poster, a report icon 72b that enables reporting, hiding, etc. of the comment as shown in Fig. 11(B), a reply icon 86 that enables replying to the comment, a reply list 89 that displays a list of replies, etc. Note that the user's own icon may be displayed in the comment posting field 84.

[0152] Each comment 87 may have its display mode changed by the poster. For example, comment 87a is a comment by a special user (AAA himself) corresponding to the talent "AAA" illustrated in Fig. 5. For example, the display order of the comment list at the bottom of the content screen in Fig. 13 may be set to be displayed at the top, or the color may be changed to be distinguishable from comments by other users (the display mode may be made different). Thereby, in the fan community, communication between the user and the talent can be promoted, and the user's satisfaction can be improved.

[0153] Next, with reference to FIG. 14, an example of a database of content in each community stored as content data 122 in the distribution server 100 will be described. For example, FIG. 14 shows the content database of "Community A". The content database stores information such as "channels", "posting permissions" for each channel, and "article IDs" for each piece of content.

[0154] "Channels" are classifications by topic, and the screens of each channel can be selected and displayed by a selection operation on the channel list 82 illustrated in FIG. 12. For example, the "official channel" is a channel where official announcements from the operator are posted, and the "Group A chat" is a channel themed on chat about "Group A" in the affiliated group 1 in FIG. 5 corresponding to "Community A". Also, "Highlights" is a channel themed on sharing links to recommended highlight videos of users (for example, videos posted on a video distribution site, where a part of a video already posted on the video distribution site has been clipped). "Past recommendations" is a channel themed on, for example, recommending videos related to Group A (for example, past posted videos of affiliated talents). When a selection operation is performed on "All channels" in the channel list 82 in FIG. 12, all the channel content in FIG. 14 will be displayed together. Also, these channels are just examples, and for example, a temporary special channel may be provided.

[0155] "Posting Permission" is information regarding users who have the permission to post content in each "channel". For example, for the "Official Channel" and "Past Recommendations", only official accounts (such as special users like operators or talents) can post. Posts from official accounts can be made using a user ID that can be identified as an official account, even if they are posts from an administrator terminal 200 or a terminal with the same configuration as the user terminal 300. Also, for "Group A Chat" and "Clip", all users can post. For example, in the channel list 82 of Figure 12, channels that can only be posted from official accounts are marked with an official mark, and channels that all users can post to are marked with a speech bubble mark or the like. This allows users to easily identify whether a channel allows posting or not.

[0156] "Article ID" is an ID that identifies each piece of content and is assigned to each piece of content. Also, for each "Article ID", a "Category", "Poster ID", and "Talent ID" are associated.

[0157] "Category" is a category that can be associated when content is posted. For example, it can be associated to easily recognize what kind of theme the content itself is, such as "Event", "Goods", "Distribution / Video", "Fan Art", "Clip", "Music", "Special Distribution", etc. When a "Category" is associated, the category name will be displayed in the category 85 of the content screen example in Figure 13.

[0158] "Poster ID" is an ID that identifies the poster of the content.

[0159] The "Talent ID" is the Talent ID of the related talent associated at the time of content posting among the Talent IDs stored in the talent information database of FIG. 5. Thus, in this embodiment, when posting content, the poster can associate related talents according to the content of the content, and can store the "Talent ID" associated for each content. That is, each content data is stored together with the meta information of the talent.

[0160] For example, to the article ID "a1", the category "Event" is associated, the poster is "ou1", and the Talent IDs "t1", "t2", "t6", "t14" are associated. The aforementioned FIG. 13 is a display example of the article ID "a1", and for the poster 71, the name "Staff S" corresponding to the user ID "ou1" and the official mark indicating that it is an official account are displayed. Also, in the category 85, the category "Event" associated with the article ID "a1" is displayed.

[0161] In the related talent 88, the icons and names of the talents "AAA", "BBB", "FFF", "MMM" corresponding to the Talent IDs "t1", "t2", "t6", "t14" associated with the article ID "a1" are respectively displayed. Thus, since related talents can be set at the time of posting, related talents can be displayed for the content, and the user can easily identify for which talent the posting is. Note that the related talent 88 may also be displayed in the content heading 70 of the community screen illustrated in FIG. 11(A).

[0162] In this way, related talents can be associated with the content. Therefore, if the related talents include the favorite talent preselected by the user, the distribution server 100 can notify the user of a post related to the favorite talent by push notification based on the information in the user information database stored as the account information 125. For example, when there is a post of content in which the favorite talent is associated with the related talent, or at regular intervals (for example, every 5 minutes, every 15 minutes, etc.), the user is pushed a notification that there is a post of content in which the favorite talent is associated with the related talent. When a push notification is received, by performing an operation on the push notification from the user, it is possible to transition to the content screen (such as FIG. 13) of the content associated with the favorite talent. When there is a post of content in which the favorite talent is associated with the related talent means when the content heading (60, 70) of the content is displayed on the home screen of FIG. 10 or the community screen of FIG. 11(A).

[0163] Note that the category and the related talent can be arbitrarily set by the poster at the time of content posting, and the content can be posted without association. For example, a content without a related talent associated, such as article ID "a99", may be posted within community A. In this case, only community A (the first attribute) is associated with the content.

[0164] (Specific example of the home screen) Returning to FIG. 10, the details of the content displayed on the home screen will be described. On the home screen for each user terminal 300, among the content databases illustrated in FIG. 14 stored as content data 122, the content stored in the content database corresponding to the "communities participated in" associated in the user information database illustrated in FIG. 13 stored as account information 125 is displayed. That is, for the categories after the recommended topic 62 on the home screen for each user, only the content headings of the content posted within the communities the user has participated in are displayed. For example, if the communities preselected in FIGS. 6, 9, etc. are "Community A" and "Community B", the content posted in "Community A", "Community B", and "Community P" which is always in the participating state is collectively displayed on the home screen. If there is no community that is always in the participating state, the content posted within the communities preselected by the user is displayed on the home screen. On the other hand, the content posted in "Community C" which the user has not participated in is not displayed. Also, for the categories after the recommended topic 62, the content headings 60 to be displayed change according to the on / off operation of the recommended filter 20 described later.

[0165] Note that, in any category, the number of contents that can be displayed on the home screen may be one, or the content headings 60 of the latest predetermined number (e.g., 2, 5, 7, etc.) of contents may be displayed. Alternatively, the content headings 60 of a predetermined number of contents in the order of popularity may be displayed. Also, the content headings 60 for each category may be configured such that, by performing a left or right slide operation or the like on the touch panel of the user terminal 300, the displayed headings can be switched. For example, by performing an operation (such as a flick operation) to slide the content heading 60 (e.g., with the latest date) displayed in the commemorative distribution 64 of FIG. 10 to the left, content headings 60 with older dates may appear from the right side of the screen. Further, for example, they may be displayed only halfway on the right side of the screen and may not appear without a slide operation.

[0166] Note that, in the content headings 60 of any category on the home screen, when a talent in FIG. 5 is associated with the content, a related talent 88 that displays the icon or name of the associated talent may be displayed.

[0167] Also, in the favorite topic 62, a predetermined number of contents associated with a preselected favorite talent exemplified by the user in FIGS. 6, 9, etc. among the contents posted within the community that the user participates in are displayed. For example, in the favorite topic 62 of a user who participates in "Community A" and has selected the talent "AAA" as the favorite talent, among the contents stored in the content database of Community A in FIG. 14, the contents associated with the talent ID "t1" corresponding to the talent "AAA" are extracted and displayed.

[0168] Among the popular user posts 63, a predetermined number of the contents posted by general users other than the official accounts of the communities the users belong to and considered to be popular are displayed. For example, they may be in the order of the most frequent like actions (tap actions and / or comments), or in the order of the highest engagement rate (such as contents with a high ratio of like actions to the number of views).

[0169] In addition, among the contents displayed on the home screen, there may be a category in which the contents associated with a specific category among the contents stored in the content database are displayed. For example, in the commemorative distribution 64, the contents associated with the category "commemorative distribution" among the contents stored in the content database are displayed, and in the goods 705, the contents associated with the category "goods" are displayed. Note that there may be a category in which only the posts of a specific channel of a predetermined community are displayed. For example, there may be a category in which the latest predetermined number of content headings 60 posted to a specific channel of "Community P" are displayed. Also, these categories displayed on the home screen are just examples, and a temporary special category may be provided.

[0170] Note that the recommended topic 62 on the home screen is preferentially displayed at the top among the categories that can be displayed on the home screen, excluding the feature 61. This makes it easier for the user to identify the information of the recommended talent. However, it is not limited to this, and the recommended topic 62 may be preferentially displayed at the top including the feature 61. Alternatively, there may be other categories that are preferentially displayed over the recommended topic 62. The operator can display them in the order of the categories that the operator wants the user to recognize.

[0171] Also, the content displayed in the content heading 60 of the recommended topic 62 may overlap with the content displayed in the content headings 60 of other categories after the recommended topic 62, or it may be such that if it is displayed in the recommended topic 62, it is not displayed in the content headings 60 of other categories. Note that the recommended topic 62 is not displayed for users who have not selected any talent as a recommended talent in advance.

[0172] (Specific example of content attribute extraction process for selected attributes) Next, with reference to FIGS. 15 and 16, a filter function for narrowing down the display of content associated with the recommended talent (second attribute) preselected by the user will be described. In the fan community app in this embodiment, the content displayed on the user terminal 300, in addition to being narrowed down to the communities (first attribute) that the user has preselected to participate in, each content data is stored together with the meta information of the talent, so further narrowing down to the recommended talent (second attribute) preselected by the user can be performed when a predetermined condition based on the user's intention is satisfied.

[0173] Narrowing down to the content associated with the recommended talent is performed by a predetermined switching operation on the user terminal 300. The predetermined switching operation is an operation such as selecting a predetermined icon. For example, it is a selection operation on the recommended filter 60 on the home screen of FIG. 10 and the content screen of FIG. 11(A).

[0174] FIG. 15 is an example screen when the recommended filter 20 is in the on state and the off state on the content screen of FIG. 11(A). FIG. 15(A) is an example screen when the recommended filter 20 is on and the narrowing down to the recommended talent preset by the user is effective. FIG. 15(B) is an example screen when the recommended filter 20 is off and the narrowing down to the recommended talent preset by the user is not effective.

[0175] Fig. 15 is assumed to be an example of a screen displayed on the user terminal 300 of the user "u1" in Fig. 7, for example. In Fig. 15(A), since the favorite filter 20 is on, only the content associated with the talents previously selected by the user "u1" as favorite talents is extracted. That is, in the user information database stored as the account information 125, the talent IDs associated with the user "u1" are the talent ID "t1" of the talent "AAA", the talent ID "t2" of the talent "BBB", and the talent ID "t5" of the talent "EEE". Therefore, only the content associated with any of the talent IDs in the content information database stored as the content data 122 is extracted. For example, the content of the article ID "a1" associated with the talent IDs "t1" and "t2" and the content of the article ID "a7" associated with "t5" (content headings 60 and 70) in the content information database of community A in Fig. 14 are displayed.

[0176] On the other hand, the article ID "a4" with which none of the talents selected by the user "u1" is associated is not displayed. For example, even for the content posted within the participating community, the content headings (60 and 70) of the content that is not associated with any relevant talent in the first place are not displayed. On the contrary, when the favorite filter 20 is turned off, as shown in Fig. 15(B), the content headings 70d of the content related to the talent "DDD", the content headings 70e of the content related to the talent "FFF", or the content headings 70 of the content not associated with any talent, which are the content not associated with the favorite talents selected by the user "u1", are displayed.

[0177] (Example of the flow of attribute extraction processing) Next, with reference to FIG. 16, the flow of the attribute extraction process for extracting content related to attributes preselected by the user will be described. FIG. 16 is a diagram for explaining the flowchart of the attribute extraction process described with reference to FIG. 15. The attribute selection process is repeatedly executed by the content management unit 132 in the distribution server 100 in response to receiving a request from the user terminal 300 (for example, operation information to the push filter 20, etc.).

[0178] In step S201, it is determined whether there has been a content display request operation from the user terminal 300. The display request operation includes an operation to cause the user terminal 300 to read display data, and a selection operation to turn the push filter 20 on or off when a predetermined condition is satisfied. The operation to cause the user terminal 300 to read display data includes, for example, logging in to the application (inquiring to the server at the timing of opening the application), a reload operation (re-reading operation), or a selection operation to a home icon 13 of the application screen, a community icon 14, a channel displayed in the channel list 82 of FIG. 12, etc. The satisfaction of the predetermined condition is, for example, that the user switches the icon of the push filter 20 displayed on the user terminal 300 by a tap operation.

[0179] If it is determined in step S201 that there has been no display request operation, the process ends. On the other hand, when it is determined in step S201 that there has been a display request operation from the user terminal 300, it is determined in step S202 whether the push filter is on. In this embodiment, the default setting of the push filter 20 is off. Therefore, at the timing of logging in when the application is started, etc., or on the content screen or home screen of the channel that is displayed for the first time after the application is started, the push filter 20 is off. In this case, since it is not determined in step S202 that the push filter 20 is on, the process proceeds to step S203.

[0180] In step S203, information about the participating communities selected by the user of the user terminal 300 that is the source of the display request operation is extracted, transmitted to the user terminal 300, and the process ends. The selected participating communities refer to the "affiliated communities" for each user that are stored as account information 125 by being pre-selected by the user illustrated in FIG. 6(A) or FIG. 9, and if there is a community that is always in a participating state, the community that is always in a participating state is included. For example, for the user "u2" in FIG. 7, the user participates in "Community A" and "Community B". Therefore, in step S203, on the home screen of the user terminal 300 of the user "u2", the content posted within "Community A", "Community B", and the always-participating "Community P" is displayed, and on the channel list screen in FIG. 12, the community bars 81 of "Community A", "Community B", and "Community P" are displayed.

[0181] Return to step S202. When it is determined that the push filter is on, proceed to step S204. For example, when a selection operation to turn on the push filter 20 is performed, it is determined that there is a display request operation in step S201, and it is determined that the push filter is on in step S202. Also, after the application is started, when a reload operation is performed on the community screen or the home screen of a channel for which an operation to turn on the push filter 20 has already been performed, or when returning to the community screen or the home screen where the push filter 20 is on after displaying the content screen in FIG. 13 with the push filter 20 on, the state where the push filter 20 is on is stored (stored in the storage unit 120 or the storage unit 320), it is determined that there is a display request operation in step S201, and it is determined that the push filter is on in step S202.

[0182] In step S204, among the selected participating communities, information regarding the selected favorite talent is extracted and transmitted to the user terminal 300 to end the process. For example, if the user is "u2", only the content associated with talent IDs "t2", "t3", "t4", "t7", "t8" among the content posted in "Community A", "Community B", and "Community P" is extracted and will be displayed on the content screen of the channel or the home screen. On the home screen, for categories after the favorite topic 62 (feature 61 in FIG. 10 and categories other than the favorite topic 62), the content headings 60 of the content associated with the favorite talent pre-selected by the user through the participating communities and the selection operation on the favorite filter 20 will be displayed.

[0183] Although an example where the attribute extraction process is executed by the distribution server 100 has been described, it may also be executed by the user terminal 300. For example, information regarding the favorite talent for each user may be stored in the storage unit 320 of the user terminal 300, and information regarding the content obtained from the distribution server 100 (for example, every 10 items) may be extracted by the user terminal 300.

[0184] In addition, even for content posted by a talent different from the favorite talent or content with a talent different from the favorite talent as the main subject (main character), if the favorite talent pre-selected by the user is associated with the talent associated with the content, by turning on the favorite filter 20, content headings (60, 70) regarding a talent different from the favorite talent will be displayed on the home screen of FIG. 10 or the community screen of FIG. 11(A). For example, assume that the content posted by the talent "AAA" corresponding to the content heading 70c in FIG. 11(A) is content regarding the event of the birthday of the talent "AAA". However, assume that the talent "BBB" is scheduled to participate in the birthday event of "AAA" as a celebration (also referred to as a collaboration), and thus "BBB" is set as the related talent. Then, in the content database, the talent ID "t2" corresponding to the talent "BBB" will be associated with the article corresponding to the content heading 70c. As a result, even when the favorite filter 20 is turned on in the user terminal 300 of a user who has not selected the talent "AAA" as the favorite talent, the content heading 70c regarding the birthday event of the talent "AAA" will be displayed. As a result, even if it is information that might otherwise be overlooked as not being related to the favorite talent at first glance, the user will not miss information regarding the favorite talent.

[0185] Note that even if the favorite filter 20 is not in the on state (regardless of whether the favorite filter is on or off), the related talent 88 can be displayed on the home screen of FIG. 10, the community screen of FIG. 11(A), or the content screen itself of FIG. 13. Therefore, even without individually setting the favorite talent, the user can recognize who in the group is related to the content, and the interest will be improved.

[0186] (Specific examples of association of categories, talents, etc. by user posts) Next, with reference to FIGS. 17 and 18, a specific example of user posting processing when content is posted by a user will be described. FIG. 17 shows an example of a user posting screen. For example, when the content screen of a channel in the community content database of FIG. 16 where the “posting permission” is set to “user” is displayed, it is displayed by selecting the posting icon 23 illustrated in FIG. 11(A). For channels where the posting permission, such as official channels, allows only official accounts to post, posting icon 23 may not be selectable by users without permission on the content screen. For example, the display mode may be changed, such as being displayed in gray, or posting icon 23 itself may not be displayed.

[0187] FIG. 17(A) is a screen displayed when the posting icon 23 is selected on the content screen of the channel “Group A Chat”. FIG. 17(A) shows a title, input fields such as the main text, an image icon 37, a next icon 38, etc. When the image icon 37 is selected, an image saved on the user terminal 300 can be uploaded. When the next icon 38 is selected, the screen transitions to the screen of FIG. 17(B). Note that it may not be necessary to proceed to the next step if the title and the main text have not been input. Instead of inputting the main text, if an image has been uploaded, it may be possible to proceed to the next step. This is to avoid a proliferation of empty posts.

[0188] On the screen of FIG. 17(B), it is possible to select categories associated with the content to be posted and related talents. For example, when the category bar 39 is selected, as illustrated in FIG. 17(C), a category list 39b is opened. The user can select any category from the category list. Note that it may be possible to select only one category, or multiple categories may be selectable. When the related talent bar 40 in FIG. 17(B) is selected, a list of talents, such as in FIG. 6(B), is displayed, and any talent (the talent to be associated) can be selected. Note that the selection of related talents is not limited to one person, and multiple people can be selected. If a selection operation is performed on the posting icon 41, the content is posted to "Group A Chat".

[0189] (Flow of user posting process) Next, with reference to FIG. 18, the flow of the user posting process when the user posts content will be described. FIG. 18 is a diagram for explaining the flowchart of the user posting process described with reference to FIG. 17. The user posting process is repeatedly executed by the control unit 350 of the user terminal 300.

[0190] In step S301, it is determined whether a posting icon has been selected. For example, it is determined whether a selection operation has been performed on the posting icon 23 on the content screen such as FIG. 11(A). When it is determined that the posting icon 23 has not been selected, the process ends. On the other hand, when it is determined that the posting icon 23 has been selected, in step S302, it is determined whether the channel to which the content is to be posted is a channel in which user posting is permitted. For example, for the channels "Group A Chat" and "Clip" in FIG. 14, since posting is permitted for all users, in step S303, the posting screen of FIG. 17(A) is displayed. Thereby, for example, text information can be input and an image can be attached by operating on the image icon 37.

[0191] On the other hand, when "All Channels" is selected in the channel list 802 of FIG. 12, or when the content screens of the channels "Official Channel" and "Past Recommendations" are being displayed, since posting is only permitted for official accounts, it is not determined in step S302 that it is a user posting permission channel, and the process ends.

[0192] In step S303, after the posting screen is displayed, in step S304, it is determined whether "Next" has been selected. For example, in the posting screen of FIG. 17(A), it is determined whether the Next icon 38 has been selected as the operation to proceed to the next page. When it is determined in step S303 that "Next" has been selected, in step S305, it is determined whether character input has been completed. If no character input has been made, the process returns to step S304.

[0193] On the other hand, when it is not determined in step S304 that "Next" has been selected, in step S306, it is determined whether "Close" has been selected. For example, it is a selection operation to the Close icon 35. When it is determined in step S306 that "Close" has been selected, the process ends. On the other hand, when it is not determined in step S306 that "Close" has been selected, the process returns to step S304.

[0194] When it is determined in step S305 that character input has been completed, in step S307, a category selection screen is displayed. For example, it is a screen where categories and related talents in FIG. 17(B) can be selected.

[0195] After the category selection screen is displayed in step S307, in step S308, it is determined whether a category has been selected. If it is determined in step S308 that a category has been selected, in step S309, the category is associated with the posting information. For example, in the category list 39b of FIG. 17(C), if "Event" is selected, the category "Event" is associated with the posting information.

[0196] When it is not determined that a category has been selected in step S308, or after a category has been associated in step S309, it is determined in step S310 whether a related talent has been selected. When it is determined in step S310 that a related talent has been selected, the related talent is associated with the post information in step S311. For example, in FIG. 17(B), when the related talent bar 40 is selected and the talent "AAA" is selected, the talent ID "t1" is associated with the post information.

[0197] When it is not determined that a related talent has been selected in step S309, or after the related talent has been associated in step S310, it is determined in step S312 whether a post confirmation operation has been performed. For example, it is determined whether a selection operation has been performed on the post icon 41 in FIG. 17(B). When it is determined in step S312 that a post confirmation operation has been performed, the post information (for example, information specifying the input character information, attached image information, selected category, selected related talent, ID of the poster, etc.) is sent to the distribution server 100 for processing. Thereby, for example, in "Group A Chat", when the category "Event" is selected and the related talent "DDD" is selected, it is stored in the distribution server 100 like the article ID "a4" illustrated in FIG. 14.

[0198] Returning to step S312, when it is not determined that a post confirmation operation has been performed, it is determined in step S314 whether a close selection has been made. The close selection is, for example, a selection operation on the close icon 35 on the screen in FIG. 17(B). When it is determined in step S314 that the close selection has been made, the process ends.

[0199] On the other hand, when it is not determined that "close" is selected in step S314, it is determined whether "return" is selected in step S315. For example, it is a selection operation for the "return" icon 36 in FIG. 17(B). In step S315, when it is determined that "return" is selected, the process returns to step S303, and the display returns to the character input posting screen in FIG. 17(A). As a result, it is possible to re-edit the characters and image information input on the posting screen before the selection of "next" in step S304. On the other hand, when it is not determined that "return" is selected in step S315, in step S307, the category selection screen or the like is continuously displayed. Although an example in which the user posting process is executed on the user terminal 300 has been described, it may be executed on the distribution server 100 and the display information may be transmitted to the user terminal 300.

[0200] <Action control function based on user evaluation in the fan community> (Overview of the action control function) Next, the action control function based on user evaluation in the fan community of the present embodiment will be described. In the fan community of the present embodiment, the user himself / herself can also post content in the community and share it with other users. In this way, while the community is activated by promoting communication with other users, if no restrictions are imposed on the actions that the user can take, there is a risk that the security and atmosphere within the community will deteriorate because users who post content that may make other users feel uncomfortable will run wild. Therefore, a level serving as an index such as a credit level and an honesty level is determined for each user, and the actions that can be taken within the community are changed according to the level. In the present embodiment, according to the actions taken by the user within the community, an evaluation from an external source different from the user himself / herself is made, so that the evaluation history status of the user is updated, and according to the evaluation history status, the actions that can be taken within the community are changed. As a result, the actions that a user with a high index such as a credit level and an honesty level can take increase, and restrictions are imposed on the actions that a user with a low index can take. That is, by taking actions acceptable within the fan community, the evaluation history status fluctuates.

[0201] (Overview of User Level Changes) The "level" of each user is stored in association with the user ID as exemplified in the user information database of FIG. 7. The "level" varies according to the "cumulative points". The "cumulative points" vary according to the external evaluation described later. For example, if the user's initial level is 1 and the cumulative points reach 10, the level becomes 2. To go from level 2 to level 3, more points are required than those needed to go from level 1 to 2. For example, when the cumulative points reach 21, the level becomes 3. Thus, as the level increases, the required number of points increases, making it more difficult to increase the level. Also, since the "cumulative points" may decrease according to the external evaluation, for example, when the cumulative points of a user at level 2 drop below 20, the level drops from 2 to 1.

[0202] In addition, each user can check their own "level" and "cumulative points" in the user evaluation history status 55 on the my page exemplified in FIG. 8. Thereby, the user can try to take actions to increase the level. On the other hand, the "levels" and "cumulative points" of other users cannot be checked. In this way, by not publishing one's own level to other users, it is possible to prevent users with a low level in the community from feeling ashamed and users with a high level from acting arrogantly. Note that either the "level" or the "cumulative points" may be displayed on the my page.

[0203] (Actions Available by Level) Referring to FIGS. 19, 20, and 21, actions that can be taken according to the user level in this embodiment will be described. FIG. 19 is a table showing examples of action contents permitted (obtainable) according to levels. For example, it is divided into levels "1 to 49", "50 to 59", "60 to 69", "70 to 79", "80 to 89", "90 to 99", and "100". Actions permitted for each level are stored as action permission information 124 of the distribution server 100 and the like.

[0204] "Specific actions", which are actions whose execution is controlled according to the level, include, for example, "no restriction on posting links", "creating a plan", "inviting a moderator", "creating a community", etc. "No restriction on posting links" means that when a user posts content in a community, there is no restriction on the URLs that can be posted, and the restriction is lifted for users with a level of 60 or higher. Also, the content posted by a user without a posting link restriction is reflected on the user terminal 300 of users with a level of 59 or lower. That is, for users with a level of 59 or lower, even if the content contains a link whose posting is restricted, if it is content posted by a user with a level of 60 or higher, the user with a level of 59 or lower can view (including the operation of accessing the link) the content including the link.

[0205] "Creating a plan" is the right to start a plan (event) within a community, and can be created by users with a level of 80 or higher. For example, it is possible to start an event plan such as a so-called offline meeting where people gather in a real or virtual space at a predetermined date and time, or a questionnaire plan. That is, it becomes possible to take actions as a leader. Also, users with a level of 79 or lower can participate in a plan created by a user with a level of 80 or higher.

[0206] "Moderator invitation" means becoming able to serve as an administrator of the content posted within the community, which can be achieved by becoming a user with a level of 90 or higher. For example, it involves performing actions such as deleting inappropriate posts and comments that are visually identified by regular operators, or setting them to non-display (also referred to as restriction). It may also be a privilege that allows taking measures to suspend accounts of malicious users, etc. (for example, for a certain period). Content restricted by users with a level of 90 or higher will not be displayed on the user terminals 300 of users with a level of 89 or lower either.

[0207] "Community creation" means being able to newly create a community that users can participate in, as exemplified in Fig. 6(A), etc., and is an action content that is only permitted for users with the highest credibility level of 100. For example, as a community that supports Group A created by fans of Group A (corresponding to Community A), a community such as "Community A2" can be created. The created Community A2 will be displayed in the community selection area 50 for participating communities on the participating community setting screen in Fig. 6(A). Alternatively, it may be possible to create a new "channel". For example, a new theme channel can be added to the channels of "Community A". The newly added channel will be displayed in the channel list display 82 in Fig. 12. Communities and channels created by users with a level of 100 can also be participated in and selected by users with a level of 99 or lower.

[0208] In addition, the user level in this embodiment can not only increase but also decrease. Therefore, the specific actions illustrated in FIG. 19, even if they are specific actions permitted due to an increase in level, may be restricted and become unavailable due to a decrease in level. For example, users with a level of 80 or higher can create plans within the community, but if the level drops to 79, they can no longer create plans. Also, if a created plan or community is deemed inappropriate in the fan community app and reports from other users are made on the display screen of the created plan or community, etc., this can be an external evaluation that may cause the level of the user who created the plan or community to decrease.

[0209] FIG. 20 is an example of a posting screen on the user terminal 300 of a user who does not have "no posting link restriction". In this embodiment, assume that for a user with a posting link restriction up to level 59, only the links to "Video Sharing Site A" and "SNS-B" are permitted for the URLs that can be posted. In this case, if a URL other than "Video Sharing Site A" and "SNS-B" is entered in the text to be posted, a message such as "Currently, only the URLs of 'Video Sharing Site A' and 'SNS-B' can be posted" is displayed as exemplified in FIG. 20. Also, when the Next icon 38 is to be displayed in different modes depending on whether it can be posted or not, it may be displayed in a mode where the Next icon 38 cannot be posted so that a selection operation cannot be performed. In this way, for an uploaded image or the like, it is relatively easy to hide an inappropriate image (an image that may give an unpleasant feeling such as violence) by automatic determination using image recognition. On the other hand, for a URL, even if the destination is a malicious website (for example, a fake site, a fraud site, or a page where unpleasant content is posted), it is not easy to make a determination, and it is necessary for the operator to perform a hiding setting or the like, which is time-consuming. Therefore, for content (here, a URL link) for which it is difficult to determine whether it is an inappropriate posting, by allowing only users with a high level (users with high reliability) to post, the burden on the operator can be reduced, and at the same time, the security within the community can be stabilized by suppressing inappropriate postings.

[0210] Note that "Video Sharing Site A" and "SNS-B", etc., which can be posted even by a user who does not have "no posting link restriction", are, for example, websites where distribution videos of talents to be supported are posted in a fan community app, and relatively safe link destinations, etc., are defined.

[0211] Referring to FIG. 21, the flow of the determination process for post link restrictions in the user post process will be described. Since FIG. 21 is a flowchart of the user post process described with reference to FIG. 18 with the addition of the determination (the process enclosed by the dotted line) as to whether the user has post link restrictions, the description of the same processes as in FIG. 18 will be omitted.

[0212] When the post screen in FIG. 17(A) is displayed in step S303, in step S316, it is determined whether a link other than the predetermined link has been pasted. If it is not determined that a link other than the predetermined link has been pasted, the process proceeds to step S304, and it is determined whether "Next" has been selected.

[0213] On the other hand, if it is determined that a link other than the predetermined link has been pasted, the process proceeds to step S317, and it is determined whether the user is a user who is permitted to paste a link other than the predetermined link. For example, the user terminal 300 determines whether the level is 80 or higher based on the "level" and "cumulative points" for each user acquired from the distribution server 100 and stored in the storage unit 320.

[0214] In step S317, when it is determined that the user is a user who is permitted to paste a link other than the predetermined link, the process proceeds to step S304, and it is determined whether "Next" has been selected. On the other hand, in step S317, when it is not determined that the user is a user who is permitted to paste a link other than the predetermined link, in step S318, it is notified that the post is not permitted, and the process returns to step S316. For example, for a user with a level of 10, since pasting a link other than the predetermined link is not permitted, as illustrated in FIG. 20, it is notified that a link other than the predetermined link cannot be pasted.

[0215] Returning to FIG. 19, the "Report Count" is a privilege that can affect whether to make specific content invisible to all users. In this embodiment, content that has been hidden or reported by users with a level of 70 or higher, or for which the number of reported people has reached a predetermined number, can be made invisible to all users. For example, content that has been hidden or reported by 5 or more users with a level of 70 or higher can be made invisible to all users.

[0216] In addition, content and comments posted by users for whom the number of times hidden or reported by users with a level of 70 or higher has reached a predetermined number, which are subject to the "Report Count", can be made invisible to all users. For example, content and comments posted by a user who has been hidden or reported by 5 or more users with a level of 70 or higher can be made invisible to all users.

[0217] Note that the users to be made invisible may not include the user himself / herself who posted the comment or content. In this way, although the content and comments posted by the user himself / herself are reflected on the user's own terminal, for example, it can be made known (noticed) that the user has become a regulated target due to no action from other users.

[0218] For the "Benefits", different benefits are associated according to the level. For example, when there is a gift plan or the like, more beneficial items such as more rare items can be given according to the level. For example, when the benefit is a stamp that can be used for posting comments or an item that can be used at a talent's live show, the benefit D given to users with a level of 60 - 69 is more expensive than the benefit E given to users with a level of 50 - 59 when purchasing stamps or items, and the equivalent amount of the benefit given increases as the level goes up.

[0219] (Regarding examples of fluctuations in evaluation values) Next, referring to FIG. 22, an example of the variation in the cumulative point count (evaluation value) will be described. FIG. 22 is a table for explaining an example of an external evaluation that varies the "cumulative points" of a user and an example of the relationship between the external evaluation and the number of variations. When there is any action from a user (including the operator) with respect to content (posted articles), comments, etc., the account management unit 133 varies and updates the cumulative points of the user according to whether it is an external evaluation stored as action information 123. If the level varies in response to the variation in the cumulative points, the account management unit 133 performs a process of permitting or restricting the action authority stored as action authority information 124 for the user.

[0220] The external evaluation is an evaluation from other users other than the user himself / herself. For example, when there is a "like" from another user for the content or comment posted by the user, 5 points are added for each like (1 tap action).

[0221] Alternatively, there may be points given by a high evaluation from the operation, such as when the operator has a good impression that the user is highly reliable based on the content of the content or comment posted by the user. The points given by the operation may be a predetermined number of points, or may be changed appropriately by the operation of the operator.

[0222] Points may also be awarded according to the evangelism level of the supported target. That is, points are awarded according to the degree of benefit contribution to the supported target by the act of promoting content (such as videos and goods) related to the supported target. For example, the promotional acts include the act of spreading the link of the distribution video of the talent who is the supported target, and the act of introducing the goods of the talent who is the supported target. For example, when a video link of a distribution video related to a talent or a group to which the talent belongs is posted on the content posted by the user, points are awarded according to the number of video views from the posted content. In addition, when a link to a goods page related to a talent or a group to which the talent belongs is posted, points can also be awarded according to the number of clicks on the goods page link. The goods page is, for example, the official goods page of the talent who is the target of support in the fan community, or the sales page of the collaborative planning products with other companies, etc., and a dedicated URL for community submission may be issued for aggregation. Alternatively, when a product is purchased through the dedicated URL for community submission of the goods page on the official website, points may be awarded to the user who posted the URL.

[0223] On the other hand, points will be reduced if there are reports or non-displays from other users. For example, each time there is one report, 5 points can be deducted by operating on the screen shown in Fig. 11(B). Alternatively, when there is a concern that a user may deteriorate the atmosphere within the community as seen by the operator due to the content of the content or comments posted by the user, etc., the user may be negatively evaluated (points are deducted) by the operation. The points deducted by the operation may be a predetermined number of points, or may be changed appropriately by the operation of the operator.

[0224] Also, as an example of external evaluation, the text of comments made on content is judged. If it contains positive words predetermined by an operator or the like, points may be increased, and if it contains negative words predetermined by an operator or the like, points may be decreased. Also, the text judgment may be performed by automatic judgment using AI. For example, for the content itself posted by the user himself / herself or comments from other users made on the content posted by the user, after automatically judging the ratio of positive words or negative words, points may be given or not given depending on which element is more. Positive words and negative words are not determined by the user, but are based on external factors (for example, the criteria of the operation side (including AI judgment)).

[0225] (Regarding the flow of evaluation history status update process) Next, with reference to FIG. 23, the flow of the user's evaluation history status update process will be described. FIG. 23 is a diagram for explaining a flowchart of a process for updating the user's evaluation history status that varies according to the external evaluation described with reference to FIG. 22. The evaluation history status update process is repeatedly executed by the account management unit 133 in the distribution server 100 when there is some action (for example, actions subject to external evaluation such as tap actions, comments, reports, and hiding) on the content, comments, etc. posted by each user in the fan community app. Note that the evaluation history status indicates the result of the user being evaluated by external factors other than the user himself / herself, including "level" and "cumulative points" in the user information database of FIG. 7 stored as account information.

[0226] In step S401, it is judged whether there is an external evaluation. For example, it is judged whether there is an external evaluation exemplified in FIG. 22 for the content, comments, etc. posted by the user. When it is judged that there is no external evaluation, the process ends.

[0227] On the other hand, when it is determined that there has been an external evaluation, in step S402, it is determined whether the external evaluation was a "point increase" evaluation. For example, if the external evaluation is a "like from another user" (tap action from another user) illustrated in FIG. 22, since the number of points increases by 5, in step S402, it is determined that it was a "point increase" evaluation.

[0228] In step S402, when it is determined that the external evaluation was a "point increase" evaluation, in step S403, the number of points is added for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, consider a user at level 59 who reaches level 60 because 5 points are added to the cumulative points due to an external evaluation. At this time, in the user information database, the level is updated to 60 and the cumulative number of points is stored as the value after the 5 - point addition.

[0229] Next, in step S404, it is determined whether the level has been increased due to the change in the number of points. In step S404, when it is determined that the level has been increased due to the change in the number of points, in step S405, specific actions corresponding to the level after the level - up are permitted to the user, and the user's permitted action information stored as account information 125 is updated and stored. For example, when the level reaches 60, as illustrated in FIG. 19, assume that the restriction on the posting link is removed. Then, for example, in the user information database stored as account information 125, information indicating that there is no restriction on the posting link for the user is stored in association. Note that there may be cases where there are no newly permitted actions even if the level has been increased, and in such cases, the permitted action information is not updated particularly and the process ends.

[0230] In step S405, after the permission action information is updated and stored, in step S406, information for notifying the user that a specific action has been permitted is transmitted to end the process. For example, a push notification of a message such as "The restriction on the post link has been lifted due to level up" is sent to the user terminal 300, a notification is made within the application, or a pop-up is displayed at the next post time, etc.

[0231] Return to step S402. When it is not determined that the external evaluation is "increase in the number of points", proceed to step S407 to determine whether the external evaluation is an evaluation of "decrease in the number of points". For example, if the external evaluation is "report from other users" exemplified in FIG. 22, since the number of points decreases by 5, in step S407, it is determined that the evaluation is "decrease in the number of points".

[0232] In step S407, when it is determined that the external evaluation is an evaluation of "decrease in the number of points", in step S408, the number of points is decreased for each user according to the external evaluation, and the evaluation history status is updated and stored. For example, if the user was at level 60, but the cumulative points are decreased by 5 due to the external evaluation, and the cumulative points no longer meet the number of points required for level 60, assuming the level drops to level 59. At this time, in the user information database, the level is updated to 59 and the cumulative points are updated and stored to the value after subtracting 5.

[0233] Next, in step S409, it is determined whether or not the level has been downgraded due to the change in the number of points. When it is determined in step S409 that the level has been downgraded, in step S410, according to the level after the downgrade, the specific actions that were permitted before the downgrade are restricted, and the permitted action information is updated and stored. For example, if the level becomes 59, as illustrated in FIG. 19, it is assumed that restrictions are imposed on the posting link. Then, for example, in the user information database stored as account information 125, information indicating that there are restrictions on the posting link for the user is stored in association. Note that there may be cases where there are no actions to be restricted even if the level is downgraded, and in such cases, the process ends without particularly updating the permitted action information.

[0234] After the permitted action information is updated and stored in step S410, in step S411, information for notifying the user that a specific action has been restricted is transmitted, and the process ends. For example, on the user terminal 300, a push notification of a message such as "Due to the level downgrade, restrictions have been imposed on the posting link", a notification within the application, or a pop-up display at the time of the next posting is made.

[0235] Returning to step S407, when it is not determined that the external evaluation is a "point decrease" evaluation, the process ends. For example, this is the case when there is an action that is not defined as affecting the change in the number of points. Although an example where the evaluation history status update process is executed by the distribution server 100 has been described, it may be the case that after being executed by the user terminal 300, information is transmitted to the distribution server 100.

[0236] <Regarding the production display by the tap action> (Example of the display screen of the tap action production process) Next, with reference to FIGS. 24, 25, and 26, the production display when a tap action is received from a user with respect to content, comments, etc. will be described. In the present embodiment, when an operation (for example, a click operation or a tap operation from the user terminal 300) is performed on the icon 708 displayed in the content described with reference to FIGS. 10, 11, and 13 or the number of tap actions 78 (78b) displayed in the heading of the content, the number of tap actions is incremented. Further, when the number of tap actions is incremented, a production display can be performed on the user terminal 300. For example, each time an operation is performed on the icon 708, an effect is produced in which a predetermined mark pops out from the icon 708.

[0237] FIG. 24 is an example of a production display (reception production) when a tap action from a user is received. FIG. 24(A) is an example of a screen for each channel for each community exemplified in FIG. 11(A) or the like, and is an example when an operation is performed on the icon 708 of the number of tap actions 78 displayed in the content heading 70 displayed at the top. In this case, since the number of tap operations has reached 50, "50" is displayed in the individual tap action number 48. Therefore, the user can recognize the number of times they have performed a tap action.

[0238] In FIG. 24(A), the case of three consecutive taps (rapid-fire tapping) is illustrated. In the first tap (the 48th tap), an effect is produced such that the thumbs-up mark 41a pops out from the icon 708 with a tap action number of 78. Next, in the second tap (the 49th tap), an effect is produced such that the thumbs-up mark 41b pops out from the icon 708. Also, in the third tap (the 50th tap), an effect is produced such that the fan mark 42 pops out from the icon 708. The fan mark 42 is the fan mark of a related talent associated with the content on which the icon 708 has been operated. In this way, when the display times (from popping out to disappearing) of the marks that popped out in the previous tap overlap with the display times of the marks that popped out in the next tap due to consecutive taps, a state where a plurality of marks are being displayed is reached. In this way, due to consecutive taps, an effect is produced where marks pop out one after another, so that the user can obtain a sense of comfort (operability) in the tap action and can be prompted to perform further tap actions. Note that the effect where the marks pop out may be such that, as illustrated in FIG. 24(A), a plurality of marks are not displayed simultaneously, and the marks to be displayed may be one by one.

[0239] FIG. 24(B) shows a special effect (special reception effect) that is displayed when the number of tap actions from the user reaches a predetermined number. For example, when the operation on the icon 708 reaches 100, an effect is produced where various marks pour down over the entire screen. Note that the predetermined number may be the upper limit value at which the user can perform a tap action on each action target. That is, when the predetermined number is reached, no effect is produced or the individual tap action number 48 is not updated by operating the icon 708. Alternatively, it may be something that is performed every time a predetermined number of times is reached (for example, every 10 times). Also, it is not necessary to set an upper limit value.

[0240] Note that the predetermined number of times is not limited to the number of individual tap actions 48, which is the number of individual tap actions performed by the user on the content. Instead of this, or in addition to this, each time the number displayed as the number of tap actions 78, which is the number of tap actions of all users in the fan community, reaches a predetermined value (for example, 100 times), an effect may be performed on the user who performed the 100th action.

[0241] Next, with reference to FIG. 25, an example of the type of effect executed by receiving a tap action will be described. FIG. 25 is an example of a content-specific effect data table for effect display by tap action stored in the storage unit 320 of the user terminal 300 based on the content data 122 stored in the distribution server 100 or the content data 122 acquired from the distribution server 100. Information regarding the effect display is associated with each content (posted article).

[0242] In the content-specific effect data table, an effect type is determined for each article ID. In addition, a lottery probability used for the effect is associated with each effect type. The effect type is determined according to whether the number of times a tap action has been performed is less than the predetermined number of times or has reached the predetermined number of times. If the predetermined number of times is the upper limit value 100 at which a tap action is possible, then 1 to 99 are less than the predetermined number of times.

[0243] For performances less than the specified number of times, the default performance is defined, and when related talents are set for the content, the fan mark performance is defined. For the default performance, marks such as applause, thumbs up, heart, and rare mark are defined, for example. For the fan mark, a mark corresponding to the related talent is associated. For example, for article ID "a1", as illustrated in FIG. 14, the related talents are associated with talent IDs "t1", "t2", "t6", and "t14". Therefore, "mark_t1", "mark_t2", "mark_t6", and "mark_t14", which are fan marks corresponding to each of the related talents, are associated. Regarding the lottery probability for each mark to be used in the performance, the same probability may be uniformly defined, or the appearance probability may be set to be low for the fan mark or the rare mark. In this way, when related talents are associated with the content, the fan mark appears by performing a tap action. As a result, it is possible to encourage the user to perform a tap action, and furthermore, when the user posts content, it is possible to encourage the user to select the related talent and then post. As a result, it is possible to easily obtain the information of the favorite talent by other users, and the fan community can be activated by the user's actions.

[0244] For the performance when the specified number is reached, a luxurious performance is defined, and when related talents are set for the content, the talent performance is defined. The talent performance is the same as the fan mark when the number is less than the specified number, and "special_t1", "special_t2", "special_t6", and "special_t14", which are performances corresponding to each of the related talents associated with article ID "a1", are defined. For example, an animation display that reminds the user of the talent, such as the fan mark popping out, is shown.

[0245] Also, when no related talent is set for the content, as exemplified by the article ID "a99" in FIG. 25, no fan mark or talent performance is defined for the production type. A default production is performed when the number is less than a predetermined number, and a luxurious production is performed when the predetermined number is reached.

[0246] Note that for each production, for example, multiple production patterns may be defined for the luxurious production, and there may be only one default production when the number is less than the predetermined number. Also, either only the fan mark production when the number is less than the predetermined number or only the talent production when the predetermined number is reached may be defined. For example, even if a related talent is selected for the content, the production when the predetermined number is reached may be only the luxurious production.

[0247] (Example of the flow of tap action production processing) Referring to FIG. 26, an example of the flow of tap action production processing will be described. FIG. 26 is a diagram for explaining the flowchart of the tap action production processing described with reference to FIGS. 24, 25, etc. The tap action production processing is repeatedly executed by the control unit 350 of the user terminal 300 in response to an operation by the user based on the content information acquired by the distribution server 100.

[0248] In step S501, it is determined whether there is a tap action operation. For example, in the home screen of FIG. 10, the community screen of FIG. 11(A), and the content screen of FIG. 13, it is a tap operation by the user on the icon 708 displayed on the content or comment. In step S501, when it is determined that there is no tap action operation, the process ends.

[0249] On the one hand, in step S501, when it is determined that there has been a tap action operation, in step S502, it is determined whether the total number of tap action operations by the user on the content or the like is less than a predetermined number. For example, assume that the predetermined number is 100, which is the upper limit value for the user to perform tap action operations on each action target. In that case, if the total number of tap actions stored in the storage unit 320 (or stored as action information 123 in the distribution server 100) is 100, in step S502, it is not determined that the total number of tap actions is less than the predetermined number, and the process ends.

[0250] In step S501, for example, if the total number of tap actions is 50, it is determined that the total number of actions is less than the predetermined number. In step S503, the tap action counter (a counter for specifying the total number of tap actions) stored in the storage unit 320 is incremented by 1. When the tap action counter is incremented in step S503, in step S504, it is determined whether the total number of tap actions after the addition is equal to the predetermined number. For example, if the total number of tap actions is 50, by adding 1 in step S503, the total number of tap actions becomes 51, and in step S504, it is not determined that the number is 100, which is the predetermined number.

[0251] When it is not determined in step S504 that the total number of tap actions is equal to the predetermined number, in step S505, it is determined whether related talents are associated with the content on which the tap action operation has occurred. For example, assume that the content on which the tap action operation has occurred is the article "a1" in FIG. 14. Then, it is determined that there are related talents.

[0252] In step S505, when it is determined that there is relevant talent, in step S506, based on the content-specific production table in FIG. 25, less than a predetermined number of tap actions are randomly selected and determined. After the production is determined in step S506, in step S507, the production of the determined tap action is executed, and the tap action number update information is sent to the distribution server 100 to end the process. For example, when "mark_t1" of the production type fan mark with the article ID "a1" in FIG. 25 is determined by random selection, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production where the fan mark corresponding to "mark_t1" pops out is executed.

[0253] Return to step S505. When it is determined that no relevant talent is associated with the content where the tap action operation occurred, proceed to step S508, and randomly select and determine less than a predetermined number of default tap actions. In step S509, the production of the default tap action determined in step S508 is executed, and the tap action number update information is sent to the distribution server 100 to end the process. For example, for the article ID "a99" in FIG. 25, since it is content with no associated relevant talent, a production is randomly selected from the defaults. For example, if "Summarize" is determined by random selection, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production where the mark corresponding to "Summarize" pops out is executed.

[0254] Return to step S504. When it is determined that the total number of tap actions is a predetermined number, proceed to step S510. For example, this is when the number of individual tap actions becomes 100 due to the tap action counter being incremented in step S503.

[0255] In step S510, it is determined whether or not related talents are associated with the content on which the tap action operation was performed. For example, if the content on which the tap action operation was performed is the article "a1" in FIG. 14, it is determined that there are related talents.

[0256] In step S510, when it is determined that there are related talents, in step S511, a tap action effect for when a predetermined number is reached is selected and determined by lottery. In step S512, the tap action effect for when the predetermined number is reached determined in step S511 is executed, and tap action number update information is transmitted to the distribution server 100 to end the process. For example, when "special_t1" of the production type talent production of article ID "a1" in FIG. 25 is determined by lottery, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production corresponding to "special_t1" is executed.

[0257] Return to step S508. When it is determined that no related talents are associated with the content on which the tap action operation was performed, in step S513, the tap action effect for when the predetermined number is reached is executed, and tap action number update information is transmitted to the distribution server 100 to end the process. For example, if it is the article ID "a99" in FIG. 25, since it is content with no associated related talents, the number of tap actions 78 and the number of individual tap actions 48 are updated, and the production corresponding to the "luxury production" is executed.

[0258] In steps S507, S509, S512, and S513, tap action update information (for example, information specifying that a tap action has been executed) is transmitted to the distribution server 100, whereby the total number of tap actions for each piece of content or comment stored as content data 122 is updated and reflected in the number of tap actions 78 (78b) of the user terminal 300 of other users. Although an example in which the tap action effect process is executed on the user terminal 300 has been described, it may be executed on the distribution server 100 and display information may be transmitted to the user terminal 300.

[0259] In addition, when related talents are associated with the content, an example in which a fan mark corresponding to each associated talent or a talent effect is executed by lottery has been described. However, when a user's favorite talent pre-selected for the related talent is associated, the lottery probability (winning probability) of the fan mark corresponding to the favorite talent may be increased compared to other fan marks.

[0260] <Use of API provided by external service> Next, with reference to FIG. 27, an example will be described in which content provided by the external web service system 400 is made available to the user by using an API provided by the external web service system 400. The external web service system 400 is, for example, a video distribution site. It is assumed that the talent who is the support target of the fan community in this embodiment is distributing videos on the video distribution site. In this embodiment, the user can easily confirm the distribution schedule of the talent distributing videos on the video distribution site.

[0261] In this embodiment, by using the API provided by the external web service system 400, information on the video distributor and the information of the co-distributor (also referred to as a collaboration partner) with the distributor is obtained, and information associated with the talent ID of the corresponding talent is generated and can be displayed on the user terminal 300. By associating the talent ID with the information to be displayed to the user, it is possible to extract the distributions of the communities (first attribute) and favorite talents (second attribute) preselected by the user so that the user can be identified.

[0262] FIGS. 27(A) and (B) are examples of a distribution schedule screen displayed on the user terminal 300. For example, the distribution schedule icon 18 may be displayed at the lower part of the application screen and may be displayed due to a selection operation on the distribution schedule icon 18. Alternatively, it may be possible to select it on the channel list screen illustrated in FIG. 12, or it may be displayed in the channel list display 82 for each community.

[0263] FIG. 27(C) is an example of a screen of video content provided by the external web service 400, and by performing a predetermined operation from the screen of FIG. 27(A) or FIG. 27(B), it is possible to transition to the video content screen.

[0264] On the distribution schedule screens of FIGS. 27(A) and 27(B), a favorite filter 20, a distribution period selection area 91, a group selection area 92, a distribution date and time 93, a content heading 90, a channel account 98, a talent related to the performance 94, etc. are displayed. For example, by performing a selection operation on the content heading 90, the user transitions to the distribution page on the external web service in FIG. 27(C). The destination of the transition is the video distribution channel of the account displayed in the channel account 98. In the talent related to the performance 94, an icon of the talent who appears in the corresponding distribution is displayed. For example, it is displayed in the content heading 90a of FIG. 27(A) that there is a distribution by the account of the official channel of Group A, and it is displayed in the content heading 90b that there is a distribution by the channel of the talent BBB.

[0265] In the distribution period selection area 91, for example, an icon of "Recent Distribution" for displaying a list of content headings 90 (content information) that identify the most recent past distribution (content), an icon of "Currently Distributing" for displaying a list of content headings 90 that identify the currently distributed distribution (content), and an icon of "Future Schedule" for identifying the future scheduled distribution (content) are displayed. By a selection operation from the user for each icon, the list of content headings 90 to be displayed can be switched. FIG. 27(A) is an example of a distribution schedule screen when the icon of "Currently Distributing" is selected, and a list of content headings 90 for identifying the currently distributed distribution is displayed. FIG. 27(B) is an example of a distribution schedule screen when the icon of "Future Schedule" is selected, and a list of content headings 90 for identifying the future scheduled distribution is displayed.

[0266] In the group selection area 92, icons for selecting the affiliated group 1 to which the talents illustrated in FIG. 5 belong are displayed. The groups displayed in the group selection area 92 are only the groups corresponding to the communities in which the user participates. For example, FIGS. 27(A) and 27(B) are the screens displayed on the user terminal 300 of the user "u2" in FIG. 7. In FIGS. 27(A) and 27(B), the icons of "Group A" and "Group B" corresponding to community A and community B in which the user "u2" participates are displayed. By operating on each icon, the content headings 90 of the distribution related to the talents belonging to any (or both may be selectable) group are displayed. In FIGS. 27(A) and 27(B), since the icon of "Group A" is selected, the content heading 90 for specifying the distribution in which the talents belonging to Group A appear is extracted and displayed. Whether it is a distribution in which the talents belonging to Group A appear or not can be specified by the user because the appearance-related talent 94 (talent ID in FIG. 5) is associated with the distribution server 100 in the content heading 90. Although an example is shown in which the groups displayed in the group selection area 92 are only the groups corresponding to the communities in which the user participates, it is not limited to this, and all groups may be displayed regardless of the communities in which the user participates.

[0267] Also, as described above with reference to FIG. 9, in the distribution schedule screen as well, by performing a selection operation on the favorite filter 20, it is possible to extract and display the distributions in which the favorite talents preselected by the user appear.

[0268] The talents displayed in the appearance-related talent 94 in FIGS. 27(A) and 27(B) are displayed based on information obtained by using the API of the video distribution site. For example, in the distribution screen of FIG. 27(C) (including posts during distribution, after distribution, and before distribution), a summary column 95 is provided, and the poster of the distribution can appropriately edit the text in the summary column 95. By embedding the attribute identification information 96 in the summary column 95, the distribution server 100 acquires the attribute identification information 96 and generates the content heading 90. The attribute identification information 96 is, for example, a channel account on the video distribution site. Since FIG. 27(C) is a distribution by the channel account corresponding to the talent "CCC", the distribution server 100 can acquire the attribute identification information 96a which is a channel account. In the appearance-related talent 94, in addition to the icon of the talent, the name of the talent may also be displayed. Also, the appearance-related talent 94 may be displayed as the related talent 88 described with reference to FIG. 13 and the like.

[0269] Also, in the summary column 95, the attribute identification information 96b (also referred to as a handle), which is information (identifier) for identifying the channel account corresponding to the talent "AAA", is input. The handle is also a URL that leads to the corresponding channel account. For example, when a co-distribution is made with a talent different from the talent corresponding to the channel account that performs the distribution, the handle for identifying the co-distribution partner is input. This input action is also said to mention another channel by adding an @ mark before the other channel and inputting character information. For example, when the distribution by the channel of the talent "CCC" is a so-called collaboration distribution with the talent "AAA", the handle for identifying the channel account of the talent "AAA" is embedded in the summary column 95 of the distribution. By the handle, which is the attribute identification information 96b, being input in the summary column 95, the server 100 can acquire the attribute identification information 96b, which is information on the collaboration partner, in addition to the account itself that performs the distribution.

[0270] As described above, by acquiring the attribute identification information 96, the distribution server 100 generates the content heading 90 in which the talent ID of the talent corresponding to the channel account (attribute identification information 96a) for distribution and the talent ID of the talent corresponding to the co-distribution partner input in the handle (attribute identification information 96b) are associated. For example, assume that the information acquired from the external web service 400 includes the attribute identification information 96 corresponding to the talents "CCC" and "AAA". In this case, in the database that manages the content heading 90 that can be displayed on the distribution schedule screen stored as the content data 122, the information for specifying the content heading 90 in which the talent IDs "t3" and "t1" of the talents "CCC" and "AAA" are associated is generated and stored by the content management unit 132, thereby generating the content heading 90. Further, the distribution server 100 acquires the text information (for example, "Co-distribution with AAA") of the title 97 of the distribution screen in FIG. 27(C) and the thumbnail image information 99, and causes the text information and the thumbnail image to be displayed in the content heading 90. As a result, since it is possible to specify which of the talents in the talent information database stored as the attribute information 121 illustrated in FIG. 5 is the talent who appears in the distribution, it is possible to cause the user to specify the distribution associated with the attribute pre-selected by the user.

[0271] For example, in the following, FIG. 27(B) will be described as being the screen of user "u1" in FIG. 7. Note that when FIG. 27(B) is the screen of user "u1", user "u1" has not participated in community B. However, as shown in FIG. 27(B), the icon of community B may be displayed in the group selection area 92, and the distribution schedule screen of group B may be displayed by selection, or only the icons of the communities the user has participated in may be displayed (the icon of community B is not displayed). The talents selected by user "u1" as favorite talents are talents "AAA", "BBB", and "EEE" corresponding to talent IDs "t1", "t2", and "t5", but talent "CCC" is not selected as a favorite talent. However, even if there is a co-distribution with the channel account of "CCC", which is not a favorite talent, the information of the co-distribution partner can also be obtained by the attribute identification information 96b. Therefore, even when the favorite filter 20 is on, the content heading 90 for identifying the distribution of talent "CCC" is displayed, and the performing talent 94 is displayed, so that the user will not overlook the information of the favorite talents.

[0272] Also, for example, if a co-distribution suddenly occurs during the distribution and there is an edit in which new attribute identification information 96b (handle) is added to the summary column 95 of the distribution screen in the external web service 400, it will be extracted at any time. Therefore, even if a co-distribution suddenly starts, the content heading 90 of the distribution will be displayed in the currently distributing distribution schedule in FIG. 27(A). Also, if the favorite talent pre-selected by the user is associated with the content heading 90, a push notification can be sent, so that the user will not overlook the sudden distribution of the favorite talent.

[0273] Note that although the content heading 90 displayed in the distribution schedule of FIG. 27 has been described as an example automatically generated using the API of the external web service 400, it is not limited to this. For example, it may be manually set from the administrator terminal 200. For example, the content heading 90 may be generated by associating a link to the destination and related talents. Even when the API cannot be used, it is possible to guide the user to a link destination outside the fan community app related to the talent.

[0274] Also, when the channel account in the external web service is the official channel of the group corresponding to the affiliated group 1 in FIG. 5, the content heading 90 generated may have no talents associated (no related talents are associated). Even in this case, although no individual talent is associated with the content heading 90, the participating communities and groups of the group corresponding to the channel account are associated. Therefore, if one participates in the community corresponding to the group, the content heading 90 will be displayed on the distribution schedule screen, and it will be displayed as the content heading 90 extracted for each group by operating the icon for each group in the group selection area 92.

[0275] <Examples of specific configurations and effects> (1-1) In the above-described embodiment, as described with reference to FIGS. 1 to 18 and the like, the distribution server 100 included in the communication system 1 can provide a user with a plurality of types of content associated with attributes (for example, communities, groups, units, talents, etc.) based on the stored program and the method of controlling a computer by the program (hereinafter simply referred to as a program). Further, the attributes include a plurality of types of groups A such as the communities displayed in the list of participating communities 50 in FIG. 6(A), a community (first attribute) corresponding to groups B, etc., and a plurality of types of talents (talent ID, talent name) and units (affiliated group 2) stored in the talent information database in FIG. 5 (second attribute). Further, as described with reference to FIGS. 6, 7, 9, etc., in order to be able to identify the participating community and the favorite talent pre-selected according to the operation from the user among the community corresponding to the plurality of types of groups and the plurality of types of talents, etc., it is stored as account information 125 in the user information database, or stored in the storage unit 320 of the user terminal 300.

[0276] Furthermore, as described with reference to FIGS. 10, 11, 14 to 16, 27, etc., the distribution server 100 or the user terminal 300, in response to an operation on the recommendation filter 20, displays on the display unit of the user terminal 300, in a first display state, content headings (60, 70, 90) such as those illustrated in FIG. 15(B) for content in which communities pre-selected and stored by the user are associated (for example, content stored in the content database of community A in FIG. 14), in a state where the recommendation filter 20 is off, so that the user can identify them. The display is switched to any one of a plurality of types of display states including a second display state as shown in FIG. 15(A), etc., in which content headings (60, 70, 90) related to content associated with both the communities and recommended talents pre-selected and stored by the user are extracted and displayed so that the user can identify them. As a result, it is possible to switch between the content headings displayed regardless of whether a recommended talent is associated with the content posted in the (participating) community pre-selected by the user, and the content headings related to the content posted in the (participating) community pre-selected by the user and associated with the recommended talent. As a result, the user can easily identify the information they like. For example, for a user who has joined community A and selected the talent "AAA" with talent ID "t1" as the recommended talent, among the content stored in the content database of community A in FIG. 14, the content headings of the content associated with "t1" in the talent ID are extracted and displayed on the home screen in FIG. 10, the community screen in FIG. 11(A), the distribution schedule screen in FIG. 27, etc. Note that the recommendation filter 20 can be turned on and off regardless of the level of the evaluation history status of each of the plurality of users stored in the user information database illustrated in FIG. 7.

[0277] (1-2) Also, the on / off operation of the favorite filter 20 is an operation different from a series of operations when the user pre-selects a participating community or favorite talent, and is established according to an operation on the icon of the favorite filter 20 displayed on the user terminal 300 from the user. As a result, when displaying the home screen in FIG. 10, the community screen in FIG. 11(A), the distribution schedule screen in FIG. 27, etc., there is no need for the user to perform an operation of selecting a participating community or favorite talent again, or an operation of transitioning to a screen for selection. Instead, it is possible to switch and display so that a content heading related to the pre-selected community, or the content related to both the community and the talent associated therewith, is displayed, thereby improving the operability and convenience for the user.

[0278] (1-3) As exemplified in FIG. 15 etc., the favorite filter 20 is always displayed regardless of whether the favorite filter 20 is in an on display state or an off display state. Thereby, the switching to a display screen that extracts the content associated with the favorite talent can be simplified and facilitated.

[0279] (1-4) Among the multiple types of content that can be provided to the user, there are communities corresponding to Group A, Group B, etc. of the affiliated group 1 in FIG. 5, and Community P that is always in a participating state regardless of the user's selection, which has an attribute (third attribute) different from that of a talent (or a unit of the affiliated group 2, etc.), and content associated with Feature 61 in FIG. 10 that is displayed to all users regardless of the community in which the user participates. The content title 60 of the content posted in Community P and the content title 60 of Feature 61 are displayed on the home screen of FIG. 10 regardless of whether the push filter 20 is on or off, regardless of the participating community or the favorite talent pre-selected by the user. In addition, since Community P is displayed on the channel list screen of FIG. 12, if the user selects the community bar 81c of Community P, the community screen of Community P (FIG. 11(A)) can be displayed. Thereby, by enabling the display of content titles related to attributes different from the attributes pre-selected by the user, it becomes possible to notify the user of information that, for example, the operator wants to notify all users regardless of the switching state.

[0280] (1-5) Among the multiple types of content that can be provided to the user, there is content (for example, Article ID a99 in FIGS. 14 and 25) that is not associated with a related talent and is only associated with the participating community. When the push filter 20 is in the on display state, the content title of the content that is only associated with the participating community and not associated with a related talent is not displayed. Thereby, when the push filter 20 is in the on state, since the content title of the content not associated with the favorite talent is not displayed, it becomes easy for the user to identify information associated with the favorite community and the talent.

[0281] As described with reference to FIGS. 5 and 6 etc. in (1-6), the favorite talents that can be pre-selected by the user are a plurality of talents belonging to (classified into) any of a plurality of groups A, group B, etc. in group 1 of the belonging group in FIG. 5. Thereby, it becomes possible to specify information further narrowed down to the information of the talents preferred by the user from the information regarding the groups for classifying the talents.

[0282] As described with reference to FIGS. 5 and 6 etc. in (1-7), the favorite talents that can be pre-selected by the user can be selected for each belonging group 2 which is a unit smaller than the belonging group 1. That is, it can be selected in unit units composed of a plurality of talents. Thereby, it becomes possible to specify information further narrowed down to the information of a unit composed of a plurality of characters preferred by the user from the information regarding the groups for classifying the talents.

[0283] (1-8) As described with reference to the home screen example in FIG. 10, the plurality of types of content that can be provided to the user can be classified into any of a plurality of types of categories including the recommended topic 62, and as illustrated in FIG. 10, it can be classified for each of the plurality of types of categories and displayed on the user terminal 300. Further, in the recommended topic 62, regardless of whether the recommendation filter 20 is in the on state or the off state, the content headings 60 for a predetermined number of contents among the contents associated with any of the participating communities and recommended talents preselected and stored by the user are displayed so that the user can identify them. Also, in categories such as popular user posts 63, commemorative distributions 64, and goods 65 other than the recommended topic 62, as described with reference to FIG. 16, the content headings 60 corresponding to whether the recommendation filter 20 is in the on or off state are displayed so that the user can identify them. By displaying the recommended topic 62, a part of the contents associated with the participating communities and recommended talents preselected by the user can be displayed without performing a switching operation of the display state. Therefore, the user can identify the contents associated with the preferred communities and talents without the trouble of the switching operation.

[0284] (1-9) Also, the content headings 60 of the recommended topic 62 on the home screen illustrated in FIG. 10 can be preferentially displayed, such as being displayed above the content headings 60 for the contents classified into other categories regardless of whether the recommendation filter 20 is in the on or off state. Thereby, it becomes easy for the user to identify the contents associated with the preferred communities and talents.

[0285] (1-10) As described with reference to FIG. 12, among the communities preselected by the user, by the user performing a selection operation on the community bar 81 on the channel list screen of FIG. 12, it is possible to display the content screen for each community illustrated in FIG. 11(A). Thereby, since it is possible to select a more preferred community from among the communities preselected by the user and display the content heading 70 for each selected community, the user can further extract arbitrary information as needed even from among the information of preference, improving convenience.

[0286] (1-11) As described with reference to FIGS. 24 to 26, each time the distribution server 100 and the user terminal 300 receive a tap action from the user with respect to the content icon 708, a reception effect such as that shown in FIG. 24(A) or FIG. 24(B) is performed. For the reception effect, as illustrated in the content-specific effect table of FIG. 25, a fan mark or a talent effect display corresponding to the related talent associated with the content (article ID) that has received an action from the user is performed. Thereby, since the reception effect by the tap action includes an effect related to the talent, it is possible to prompt the user to take a tap action.

[0287] (1-12) Further, the reception effect of the tap action performs a special effect such as a luxurious effect or a talent effect as illustrated in FIG. 24(B) when the tap action from the user is received a predetermined number of times (for example, 100 times). Thereby, since a special effect is performed when the tap action is performed a predetermined number of times, it is possible to prompt the user to take a tap action.

[0288] (1-13) Among multiple types of content that can be provided to the user, there is content associated with a talent ID in the content database of FIG. 14 because related talents are associated with it. Regarding the content with related talents, regardless of whether the push filter 20 is on or off, the related talent 88 that displays the icon and name of the talent associated with the content is displayed. As a result, the user can identify the related talents associated with the content regardless of whether the push filter 20 is on or off, improving the convenience for the user. Also, it can provide an opportunity to learn about new talents and the like.

[0289] (1-14) As described with reference to FIGS. 14, 17, and 18, multiple types of content that can be provided to the user include posted content posted by the user. When a selection operation is performed on the related talent bar 40 in FIG. 17 at the time of posting from the user, if a related talent is associated with the posting information in steps S310 and S311 of FIG. 18, the content generated by the posting information is associated with a talent ID as illustrated in the content database of FIG. 14. As a result, talents can also be associated with user posts, facilitating the sharing of favorite information among users.

[0290] (1-15) The plurality of types of content includes the posted content (such as the article with the posting permission of "user" in FIG. 14) posted by the user through the user posting process described with reference to FIGS. 17 and 18. The users include a plurality of specific users corresponding to each of the talents in FIG. 5. For the posted content with actions such as tap actions or comments from the specific users, the content headings (60, 70) on the home screen in FIG. 10, or the community screen in FIG. 11(A), or the special action 79 is displayed together with the icon of the special user on the content screen in FIG. 13. Thus, the user can easily identify that the content is the posted content on which the specific user has taken an action. Therefore, the convenience is improved for the users who seek information about the talents.

[0291] (1-16) When the content associated with the favorite talent pre-selected and stored by the user is posted based on the user information database in FIG. 7 and the content database in FIG. 14, the distribution server 100 and the user terminal 300 send a push notification to the user indicating that the content associated with the favorite talent has been posted. Thus, it becomes easier for the user to identify the content information regarding the favorite talent. Also, if there is an action from a specific user for the posted content made by the user, the user can obtain a special feeling.

[0292] (1-17) As described with reference to FIG. 27, the distribution server 100 uses an API provided by the external web service 400 to obtain attribute identification information 96a of the channel account to be distributed, attribute identification information 96b of the handle included in the summary column 95 of the distribution screen in the external web service 400 in FIG. 27(C), information such as the title 97, and the thumbnail image 99. Since the obtained information includes the attribute identification information 96, the talent ID corresponding to the attribute identification information 96 is specified, and the distribution schedule screens in FIGS. 27(A) and 27(B) including the content heading 90 generated based on the specified talent ID are displayed on the user terminal 300. For example, if the information obtained from the external web service 400 includes the attribute identification information 96 corresponding to the talent "AAA", the content heading 90 associated with the talent ID "t1" of the talent "AAA" is generated. The information for specifying the content heading 90 is generated and stored by the content management unit 132. Therefore, among the groups corresponding to the channel accounts, the content headings 90 of the distributions related to the communities (groups) preselected by the user are displayed. Further, by a selection operation on the favorite filter 20, it is possible to narrow down and display the content headings 90 of the distributions in which the favorite talents appear. As a result, for external submissions such as distributions provided by the external web service 400, it is possible to optimize them according to the user's preference information and make it easier for the user to identify them.

[0293] (2-1) In the above-described embodiment, as described with reference to FIGS. 1 to 4, FIGS. 7 and 8, FIGS. 19 to 23, etc., the distribution server 100 included in the communication system 1 reflects the actions received from the user terminals 300 operated by each of the plurality of users stored therein to the user terminals 300 of each of the plurality of users so that each of the plurality of users can recognize them. Based on a program or a method of controlling a computer by the program (hereinafter simply referred to as a program), in response to an external evaluation, which is an evaluation from outside the user himself / herself such as that illustrated in FIG. 22, of actions such as content and comments posted by the user, the evaluation history status such as the level and cumulative points of the user himself / herself is updated. Further, as illustrated in FIG. 19, the actions that a user whose evaluation history status is at a predetermined level can take are controlled so that a user who is not at the predetermined level cannot take them. Further, for example, even if a user who is at a predetermined level 80 or higher, which is a specific situation, performs a specific action of posting content in which a link that is restricted for users at level 59 or lower is embedded, the content in which the link is embedded can also be displayed on the user terminal 300 of a user at level 59 or lower who is not in the specific situation. Thereby, the actions that a user can take are controlled in response to an external evaluation, which is an evaluation from outside the user who has taken the action. Moreover, since the specific actions received from a user in a specific situation can be reflected to a plurality of users (even when users not in the specific situation are included), it is possible to maintain good public order within the community.

[0294] (2-2) As described in steps S402 to S406 of FIG. 23, etc., the account management unit 133 allows a user whose level has increased and who has become in a specific situation to be able to take a specific action according to the level. Thereby, by allowing a user who has become in a specific situation in response to an external evaluation to be able to take a specific action, the actions that a user who is not in the specific situation can take are restricted, so that it is possible to encourage the user to take an action that will result in a specific situation in which the user can take a specific action, and the public order within the community can be maintained in a good state.

[0295] (2-3) As described with reference to FIG. 19, specific actions that can be taken are defined step by step according to the level. For example, if the level is 60 or higher, there is no restriction on the link to the content to be posted as a specific action, and if the level is 80 or higher, a project can be created as a specific action. These specific actions, as exemplified in steps S404 to S406 of FIG. 23, by increasing the level, allow the user whose level has changed from 59 to 60 to have no restriction on the link to the content to be posted, and by increasing the level, allow the user whose level has changed from 79 to 80 to create a plan. Therefore, a user who has not reached a predetermined level is restricted from performing a specific action. Thereby, by allowing specific actions permitted to users who have reached a predetermined level and are in a specific situation step by step according to the level, it is possible to encourage actions aiming for a higher level, and the public order within the community can be maintained in a good state.

[0296] (2-4) As described in steps S407 to S411 of FIG. 23, etc., the account management unit 133 restricts a user whose level has decreased and is no longer in a specific situation from being able to take a specific action permitted according to the level. Thereby, since a user who is no longer in a specific situation according to an external evaluation is restricted from being able to take a specific action, it is possible to encourage taking actions that can maintain and improve the specific situation, and the public order within the community can be stabilized.

[0297] (2-5) As described with reference to FIG. 19, specific actions that can be taken according to the level are defined step by step. For example, if the level is 59 or lower, there is a restriction on the link for the content to be posted, which is a specific action, because it is not allowed to remove the link restriction for the content to be posted. If the level is 79 or lower, there is a restriction on creating a plan because creating a plan, which is a specific action, is not allowed. These specific actions, as illustrated in steps S409 to S411 of FIG. 23, restrict the link for the content to be posted that was allowed for a user whose level has been downgraded from 60 to 59 by downgrading the level. Also, by downgrading the level, for a user whose level has been changed from 80 to 79, the creation of a plan that was allowed is restricted, so that a user who is no longer at a predetermined level is restricted from performing a specific action. Thereby, by gradually restricting the specific actions allowed for a user who is no longer in a specific situation, it is possible to prevent the actions that can be taken extremely from decreasing, while promoting actions that can maintain and improve the specific situation, and the security within the community can be maintained in a good state.

[0298] (2-6) As described with reference to FIG. 8, the user history status 55 in which the level and cumulative points, which are information regarding the evaluation history status of the user, are displayed is not publicly disclosed to other users, while the user himself / herself can confirm it on the my page screen. Thereby, since the information related to the evaluation history status updated according to the external evaluation can be notified to the user himself / herself, it is possible to encourage the user to try to improve the security of the community while grasping his / her own situation.

[0299] (2-7) As described with reference to FIG. 22 and the like, the external evaluation that can update the evaluation history status of the user includes point assignment due to a good impression from the operator and negative evaluations. In this way, since the external evaluation includes the evaluation from the operator, who is a third party different from the user, it is difficult for personal feelings to intervene in the external evaluation, and the external evaluation can be fair.

[0300] (2-8) As described with reference to FIG. 22 and the like, external evaluations that can update the user's evaluation history status include evaluations such as favor actions and reports from other users different from the user who took the action among multiple users who use the community app. In this way, since the external evaluation includes evaluations from other users different from the user who took the action, the public order within the community can be in line with the intentions of all users.

[0301] (2-9) As described with reference to FIG. 19 and the like, for content and comments subject to restrictions such as hiding and reporting, restriction processing such as hiding is performed on each user terminal 300 of multiple users from users who are allowed a specific action of "moderator invitation" with a level of 90 or higher or users who are allowed a specific action of "report count" with a level of 70 or higher. As a result, since the restriction processing for the user's action is performed on the action subject to restriction by a user whose evaluation history status is a predetermined status, it is possible to suppress the situation where the restriction processing for the user's action is performed arbitrarily.

[0302] (2-10) Also, the reflection of the action subject to restriction from a predetermined number of users who are allowed the specific action of "report count" described with reference to FIG. 19 and the like is restricted on each user terminal 300 of multiple users. As a result, since the action received as the action subject to restriction by a predetermined number of users whose evaluation history status is a predetermined status is regarded as a nuisance action and the reflection of the action is restricted, it is possible to efficiently restrict nuisance actions and the like without hindering free communication and communication.

[0303] (2-11) As described with reference to FIG. 19 etc., according to the level which is the evaluation history status of each of a plurality of users, for example, if it is level 50 to 59, privilege E is granted, and if it is level 100, a privilege S etc. with a higher rarity than privileges A to E can be granted. According to such a configuration, since a privilege can be granted according to the evaluation history status, it is possible to prompt the user to be conscious so as to achieve an evaluation history status to which a privilege is granted.

[0304] (2-12) A plurality of users belong to the same fan community, and actions that a user can take include, for example, a publicity act of posting about a group to be supported, or a distribution video or goods etc. which are content related to a talent belonging to the group. The distribution server 100 has an external evaluation fluctuate according to the number of views of the distribution video by the said publicity act or the degree of contribution to profits such as goods sales, and the evaluation history status of the user is updated. Thereby, since it can be a motivation for the user to perform a publicity act, the community is activated.

[0305] <Modification example> Modification examples etc. for the embodiment described above are listed below.

[0306] (Regarding content information) In the embodiment described above, as content information regarding content (for example, news articles, posting information from users, etc.), content headings (60, 70, 90) such as those in FIGS. 10, 11, and 27 were exemplified. However, it is not limited to this, and the content information regarding the content may be, for example, explanatory information on the screen of the content itself exemplified in FIG. 13. For example, it includes a poster 71, content 74b, related talent 88, special action 79, number of tap actions 78 etc. which are various information displayed on the content screen itself of FIG. 13.

[0307] (Regarding attribute selection processing) In the above-described embodiment, an example in which at the time of the first login, in steps S102 to S104 of FIG. 9, the participating communities and the favorite talents can be selected was described. At the time of the first login, it is not necessary to select all of them in step S103, and an operation of not selecting any of them (the selected attributes are zero) may be possible. Also, only one of the participating communities or the favorite talents may be selected, or it may be necessary to select one of them. For example, even if a favorite talent is selected, if the user has not joined the participating community corresponding to the group to which the favorite talent belongs, information about the favorite talent may not be extracted and displayed on the content screen. That is, even if the favorite filter 20 is turned on, the content headings of talents belonging to a group corresponding to a community that the user has not joined are not displayed. Alternatively, it may be possible to select a favorite talent only after selecting a participating community. For example, if none of the participating communities are selected, it may not be possible to proceed to the screen for selecting a favorite talent.

[0308] In the above-described embodiment, an example in which at step S101 of FIG. 9, when it is determined that it is the first login, the selection screen for the participating communities and the favorite talents illustrated in FIG. 6 is displayed at step S102 was described. At this time, for the participating community setting in FIG. 6(A) or the favorite talent setting in FIG. 6(B), all selections may be made in advance (by default).

[0309] In the above-described embodiment, an example in which at steps S101 and S102 of FIG. 9, if it is the first login, the attribute selection screen is displayed on the user terminal 300 at step S102 was described. However, it may not be displayed on the screen at the time of the first login, and the first attributes may be selected later from the my page or the like. Also, until the user edits it later on the my page or the like, at the time of the first login, the user may be in a state of having joined all communities.

[0310] In the above-described embodiment, in the case where it is not the first login (NO in step S101 in FIG. 9), after the setting edit screen in FIG. 6 is displayed, the determination that the participating community or the favorite talent has been selected in step S107 has been described with an example where it is the timing when a selection operation is performed on an icon or the like. However, it is not limited to this. By operating the home icon 13 or the like displayed at the bottom of the app screen to move to another screen, the information is transmitted and received as if the attribute selected on the attribute selection screen in FIG. 6 has been determined, and it may be regarded as being selected and proceed to step S108. Alternatively, on the attribute selection screen in FIG. 6, instead of or in addition to an operation on the display of each participating community or the display of each talent, a determination icon or the like may be displayed, and it may be determined that the selection has been made when an operation is performed on the determination icon (when the information transmitted in response to the operation is received). Also, when an operation is performed on the determination icon, a special effect may be performed on the user terminal 300.

[0311] (Regarding the display mode of special actions on the home screen, community screen, etc.) In the above-described embodiments, as described with reference to FIG. 11(A) and the like, for the content with comments or tap actions from special users corresponding to talents, an example was described in which a special action 79 is displayed together with the icon of the special user within the content heading 70. When the talent who performed an action on the content is the favorite talent preset by the user, the display mode of the special action 79 displayed within the content heading 70 and the like may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent, and the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the favorite talent. Alternatively, when the talent who performed an action on the content is the person of the related talent associated with the content, the display mode of the special action 79 displayed within the content heading 70 may be displayed in a mode different from the case where the talent who performed the action is not the person of the related talent, and the content heading 70 itself may be displayed in a mode different from the case where the talent who performed the action is not the person of the related talent. The different modes are, for example, modes with different colors, modes with different message contents, modes with different presence or absence of messages, and the like.

[0312] (Regarding the display mode of comments on the content screen) In the above-described embodiments, in the content screen described with reference to FIG. 13 and the like, when each comment 87 is a comment from a special user corresponding to a talent, an example in which a change in the display mode or a change in the display order can be made was described. Instead of this, or in addition, when the talent (special user) who commented on the content is a favorite talent preset by the user, the display mode of the comment 87 of the favorite talent may be displayed in a mode different from the case where the talent who performed the action is not a favorite talent. Or, it may be displayed at the top of each comment 87. Or, when the talent who commented on the content is the person of the related talent associated with the content, the display mode of the comment 87 of the person of the related talent may be displayed in a mode different from the case where the talent who performed the action is not the person of the related talent. The different modes are, for example, modes with different colors, modes with different message contents, modes with different presence or absence of messages, etc. Or, it may be displayed at the top of each comment 87.

[0313] (Regarding the categories displayed on the home screen) In the above-described embodiments, an example of being displayed in the feature 61 that is displayed on the home screen described with reference to FIG. 10 regardless of whether the user has selected any participating communities and any favorite talents was described. However, it is not limited to this, and the feature 61 may not be displayed. For example, only the content posted in the participating community preselected by the user (including the community that is always in the participating state regardless of the selection) may be displayed on the home screen. Or, the feature 61 may be displayed on a different screen from the home screen where the content headings 60 are displayed for each category.

[0314] In the above-described embodiments, an example has been described in which, for a user who has selected a favorite talent, the favorite topic 62 is displayed on the home screen of FIG. 10. However, this is not the only case. Even if a user has selected a favorite talent, the favorite topic 62 may not be displayed. For example, in the home screen of FIG. 10, unless a selection operation is performed on the favorite filter 20, the extraction of content headings 60 associated with a favorite talent may not be performed in any category. Alternatively, the favorite topic 62 may be displayed on a different screen from the home screen on which the content headings 60 are displayed for each category.

[0315] (Notification to User) In the above-described embodiments, an example has been described in which a push notification is sent when there is a post of content associated with a favorite talent preselected by the user. In addition to this, when there is a comment from the talent himself / herself, who is a special user, to the content, a notification (display on the notification screen or push notification, etc.) may be sent to the general user. Alternatively, the notification may be sent only when there is a comment from the talent himself / herself. Alternatively, when there is a comment from the talent who is the favorite talent pre-set by the user, the notification mode may change compared to when there is a comment from a talent who is not the favorite talent. The change in the notification mode means that, for example, if it is a notification from the favorite talent, the notification icon 15 displayed at the bottom of the app screen may be emphasized.

[0316] Also, when a favorable action such as a comment or a tap action from another user including a special user is taken on a post (content or comment) made by the user, a notification (display on the notification screen or push notification, etc.) may be sent to the user who made the post. At this time, for example, normally, the notifications are sent together once an hour, but when an action is taken by a special user who is a talent or a special user who is a favorite talent, the notification may be sent in real time.

[0317] In addition, when the user selects the favorite talent for each unit, a push notification may be sent when content associated with any of the talents included in the unit is posted, or when content associated with the unit is posted.

[0318] (Regarding attribute extraction processing) In the above embodiment, when the favorite filter 20 is turned on, an example was described in which content headings (60, 70) associated with the favorite talents preselected by the user are extracted and displayed. However, when multiple people are selected as favorite talents, it may be possible to further narrow down the talents individually for each favorite talent. For example, if talents with talent IDs "t1", "t2", and "t3" are selected, when turning on the favorite filter 20, it may be possible to select them individually with "t1", "t2", and "t3". Alternatively, when the favorite talents are preselected in units in advance, it may be possible to select them individually in units. Furthermore, by preselecting a more special talent (the most favorite talent) from among the favorite talents in advance, it may be possible to create a further filter with the most favorite talent. In this way, after extracting all the favorite talents with the favorite filter 20, it may be possible to perform filtering in multiple stages such as the first, second, third, etc., where individual selection (further narrowing down) can be performed by operating a predetermined icon or the like.

[0319] Also, when the favorite talents are preselected in units in advance, if content associated with any of the talents included in the unit is posted, by turning on the favorite filter 20, it may be possible to extract and display the content headings of the content associated with any of the talents of the unit preselected by the user.

[0320] Even between communities that are different from the community corresponding to the affiliated group to which the talent belongs, it may be possible to associate any talent. For example, the talent ID "t1" belongs to "Group A" of affiliated group 1, but it may be associated with the content posted within "Community B" corresponding to "Group B". Therefore, for a user who has selected the talent ID "t1" and also participates in "Community B", if they perform an operation to turn on the favorite filter 20 on the home screen or the content screen within "Community B", the content associated with the talent ID "t1" will be extracted and displayed. As a result, even in the case of a collaboration plan between different groups where posts have only been made within the community corresponding to one of the groups, users can obtain information on their favorite talents without missing it. Note that even if they do not participate in "Community B", the content associated with their favorite talents may be displayed on the home screen.

[0321] (Regarding the predetermined conditions in the attribute extraction process) In the above embodiment, as an example of the predetermined conditions for turning the favorite filter 20 on or off, which was described with reference to FIGS. 15 and 16, it was explained that when a user taps the icon of the favorite filter 20 displayed on the user terminal 300, the predetermined conditions are satisfied when it is turned on. However, this is not the only case. The predetermined conditions may be anything as long as the on / off of the favorite filter 20 can be switched according to the user's intention. For example, it may be possible to switch by voice instruction or by vibrating the user terminal 300 itself (such as shaking).

[0322] (Regarding the storage state of the favorite filter 20 in the attribute extraction process) In the above embodiment, regarding the on memory state of the push filter 20 after the operation on the push filter 20, after the content screen of FIG. 13 is displayed after the application is launched, even when returning to the content screen or the home screen where the push filter 20 was on, an example in which the on state of the push filter 20 is stored and maintained has been described. However, it is not limited to this, and when moving to a different screen, the push filter 20 may always be in either the on or off state. For example, after displaying the community screen of FIG. 13 from the community screen (or the home screen of FIG. 10) in which the push filter 20 is in the on or off state, when returning to the community screen (or the home screen of FIG. 10) of FIG. 11, the push filter 20 may be off or on. Alternatively, when the push filter 20 is turned on on the home screen of FIG. 10 (or the community screen of FIG. 11) and the community screen of FIG. 11 (or the home screen of FIG. 10) is displayed and then returned to the home screen of FIG. 10 (or the community screen of FIG. 11), the push filter 20 may be in the off or on state.

[0323] (Regarding user submission processing) In the above embodiment, in the example of the user submission screen of FIG. 17, an example in which the submission screen for character input and image upload in FIG. 17(A) and the screen for selecting categories and related talents in FIG. 17(B) are separated has been described. However, it is not limited to this, and FIG. 17(A) and FIG. 17(B) may be displayed on one screen for input or selection or the like. For example, scrolling or the like may be possible, and it may not be necessary to transition to another screen. Also, it may be possible to submit without character input or image submission. Alternatively, even if there is no title, it may be possible to submit if character input or an image has been uploaded.

[0324] Also, although examples where the selection of categories and related talents is optional have been described, any of them may be made mandatory. Alternatively, it may be possible to select "no category" or "no related talent", or it may be possible to make selections for each unit in the belonging group 2 of FIG. 5. Also, when selections are made for each unit, the talent ID of each individual talent belonging to the unit and the unit ID for identifying the unit may be associated with the content. Alternatively, only the unit ID may be associated.

[0325] (Regarding the evaluation history status update process) In the above-described embodiments, in step S406 and step 411 of FIG. 23, examples of notifying that permission or restriction of a specific action has been made have been described. However, it is not limited to this, and the notification to the user in step S406 and step S411 may not be made. Alternatively, when an action is permitted in step S406, it may be notified, but when an action is restricted in step S411, only one of them, such as not notifying, may be notified. For example, by not notifying when a restriction is imposed, it is possible to avoid disturbing the user.

[0326] (Regarding other examples of the evaluation history status) In the above-described embodiments, as described with reference to FIG. 19, the user's level rises step by step according to external evaluation from the initial setting level, and every time a specific situation (for example, level 60, level 80, etc.) is reached, examples where specific actions that can be taken are permitted according to the level have been described. However, it is not limited to this. For example, for all users, the specific actions in FIG. 19 may be permitted in the initial setting, and as the level decreases, it may gradually disappear in a specific situation, and the ability to take specific actions may be restricted. Also, the initial setting level is not limited to the lower limit of 1 or the upper limit of 100, and may start from 80, etc., and the ability to take specific actions may be gradually permitted or restricted according to the change in the level.

[0327] In the above-described embodiments, an example has been described in which changes in the user's level and cumulative points are due to external evaluations from outside the user himself / herself. However, in addition to this, the cumulative point count may increase when the user performs a tap action on the posts or comments of other users, or when the user comments on other users in addition to this. As a result, the user becomes more active within the community, and the community becomes activated.

[0328] In the above-described embodiments, an example has been described in which when there is a hide or report on the content or comment posted by the user, the points decrease, and the behavior is gradually restricted. Instead of this, or in addition to this, apart from the points (fluctuating cumulative points) that affect the level, a reflection restriction point that is a standard for regulating the reflection of actions within the community application may be defined in the evaluation history status. For example, for a user whose posts, comments, etc. have received a predetermined number (for example, 20 when any one or all are totaled) of hides or reports from other users, the behavior may be restricted (reflection restricted). For example, the content and comments posted by a user subject to reflection restriction may not be displayed to other users for a certain period, or the posting of content and comments themselves may not be possible for a certain period.

[0329] Note that the said reflection restriction may be executed according to the level that fluctuates according to the number of points in FIGS. 22, 23, etc. described above. For example, a negative level lower than 1 may be provided, and reflection restriction may be performed on a user who has reached a negative level. Alternatively, the default level at the start of the community application may be set to 10, and restrictions may be imposed as the level becomes lower than 10.

[0330] (Regarding the like action from a user in a predetermined situation) In the above-described embodiments, an example in which the action contents such as special actions that can be taken for each level described with reference to FIG. 19 vary has been described. Instead of or in addition to this, it may be possible for other users to recognize that the user is a high-level user. For high-level users, it is considered that they tend to take actions that make the atmosphere within the community positive and have a high level of reliability. Therefore, the display mode of the content for which a high-level user (for example, level 90 or above) has performed a favorable action (including a tap action or a favorable comment) may be changed. Alternatively, the display mode may be changed only when favorable actions are received from a plurality of highly reliable users (for example, a predetermined number such as 5 people). For example, the display mode of the content heading 60 on the home screen of FIG. 10, the content heading 70 in FIG. 11(A), or the mode of the number of tap actions 78, etc., may be changed in color or a mark (for example, a special action 79, etc.) indicating that an action has been taken from a highly reliable user may be displayed. Alternatively, on the content screen illustrated in FIG. 13, a display that makes the comment prominent (top display or color change) etc. may be performed. Also, when there are comments or content that have received favorable actions from a plurality of highly reliable users, push notifications or displays in announcements may be made.

[0331] In addition, for the user who has posted the content or comment for which a favorable action has been taken from the highly reliable user, it may be possible to notify that an action has been taken from the highly reliable user. For example, it may be possible to send a push notification to the user terminal of the corresponding user, or it may be possible to display it in a notification within the application.

[0332] In the above-described embodiment, from a predetermined number (for example, five) of users at level 70 or higher who are the targets of "report count" in FIG. 19, for the content or comment itself that is subject to restrictions such as non-display or reporting, or for the user, an example of non-displaying the content itself to each of the user terminals 300 of a plurality of users, or non-displaying the content posted by the restricted user, etc. was explained. For the restriction processing of the content etc. that is the target of these restrictions itself and the restriction processing of the user who posted the content etc. that is the target of the restrictions, the conditions of the number of users in a predetermined situation (for example, level 70 or higher) where non-display or reporting was performed may be made different. For example, a restriction process of making the content and comments etc. that are the targets of restrictions non-display to all users is performed from the first number (for example, five) of users at level 70 or higher who are the targets of "report count", and for users who have had non-display or reporting etc. done to the content etc. they posted from the second number (for example, twenty) that is more than the first number, a restriction process of making all the content etc. posted by the user who has had such reporting etc. done non-display to all users may be performed.

[0333] Also, the content and comments posted by a user who has accumulated a predetermined number of users who have been non-displayed or reported from users at level 70 or higher who are the targets of "report count" can be made non-display to all users. For example, the content and comments posted by a user who has been non-displayed or reported from five users at level 70 or higher can be made non-display to all users.

[0334] Note that the user to be made non-display may not include the user himself / herself who posted the comment or content. Thereby, although the content and comments posted by oneself are reflected on the user's own terminal, for example, without an action from other users, it is possible to let the user notice (become aware) that they have become a target of restrictions.

[0335] (Regarding notification of information related to the evaluation history status) In the above-described embodiments, an example has been described in which each user can check their own "level" and "accumulated points" in the user evaluation history status 55 on the my page illustrated in FIG. 8. However, not limited to this, the level and accumulated points, which are information regarding the user's evaluation history status, may not be notified to any other user than the user himself / herself, while only the operator can check them on the administrator terminal 200 or the like. Thereby, while not notifying any user of the information related to the evaluation history status updated according to the external evaluation, the operator can be notified, so that it is possible to prevent the user's actions from being overly restricted, and the operator can grasp the information related to the user's evaluation history status and utilize it for operation. Also, the user can use the fan community more comfortably without being overly concerned about their own "level".

[0336] In the above-described embodiments, information related to the evaluation history status described with reference to FIG. 23 or the like may be notified to the user as feedback. For example, the increase or decrease in points updated according to the external evaluation during a predetermined period (for example, one day or one week), or the up or down of the level, etc., may be fed back to the user as the result of today's (or this week's) actions. Alternatively, instead of or in addition to this, for the text of the content or comment (action taken by the user) posted by the user during a predetermined period, for example, sentiment analysis by AI may be performed, and the ratio of positive words, the ratio of negative words, or the ratio of words not classified into either may be notified to the user (for example, displayed on a pop-up screen at a predetermined time or displayed on a notification page). Thereby, the user can objectively know the tendency of the actions they have taken, and can be encouraged to take actions to improve the security within the community.

[0337] (Regarding external evaluation) In the above-described embodiments, an example in which a user's points decrease when there are actions such as hiding or reporting on content or comments posted by the user has been described. In addition to this, for example, when hiding, the reason for hiding may be selectable on a screen such as Fig. 11(B), or input may be possible. This is because, as a reason for a user to hide or the like for another user's action, an action that has no risk of giving an adverse impact within the community and deteriorating public order due to personal reasons such as being a rival user may be hidden. Therefore, hiding or the like that has substantially no adverse impact within the community may not affect the user's point count, and only hiding or the like that has a substantial adverse impact may affect the point count. For example, options for hiding that affect points and those that do not may be predetermined, and the operator may check the reason for hiding and perform an operation to affect the point count for hiding determined to have an adverse impact.

[0338] In the above-described embodiments, an example in which a user's points fluctuate according to external evaluations such as tap actions or comments on actions such as content or comments posted by the user has been described. Regarding the content posted by this user, a limit may be imposed on the number of posts. For example, as an example of external evaluation that increases points, the number of views of a distribution video through the content posted by the user, the number of purchases of goods, etc., the degree of contribution to the benefit of the supported target are exemplified. However, since there is a risk that the posting of content will become chaotic in an attempt to increase points, for example, a limit such as once a day may be imposed on the posting of content. Also, for users with a high level and high reliability, the upper limit of the number of content posts per day may be increased.

[0339] 〔Example of implementation by software〕 In the above-described embodiments, the various control blocks of the control unit included in computers such as servers and terminals may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be realized by software using a CPU (Central Processing Unit). When realized by software using a CPU, a computer provided with a control unit includes a CPU that executes instructions of a program, which is software that realizes each function, a ROM (Read Only Memory) or a storage device (collectively referred to as a "recording medium") in which the program and various data are recordable in a readable manner by the computer (or the CPU), and a RAM (Random Access Memory) that expands the program. Then, when the computer (or the CPU) reads and executes the program from the recording medium, the object of the present invention is achieved. As the recording medium, a "non-transitory tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. Further, the program may be supplied to the computer via any transmission medium (such as a communication network or a broadcast wave) capable of transmitting the program. Note that one aspect of the present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.

[0340] The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of this invention is shown not by the above description but by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included.

Explanation of Reference Numerals

[0341] 1 Communication system, 2 Network, 100 Distribution server, 200 Administrator terminal, 300 User terminal, 400 External web service system

Claims

1. A program that enables a user to be provided with multiple types of content associated with attributes, wherein the attributes include multiple types of first attributes and multiple types of second attributes, causing a computer, storage means for storing in a specifiable manner an attribute preselected according to an operation from the user from among the multiple types of first attributes and the multiple types of second attributes, in response to the satisfaction of a predetermined condition, a first display state in which the user can specify content information regarding content associated with a first attribute preselected and stored by the user, and a second display state in which the user can specify content information regarding content associated with both a first attribute and a second attribute preselected and stored by the user, and functioning as display switching means for switching and displaying to any of a plurality of types of display states including these, wherein each of the multiple types of first attributes is a group including at least any one of the multiple types of second attributes, and each of the multiple types of second attributes is an attribute that can belong to at least any one of a plurality of types of groups corresponding to the multiple types of first attributes. A program.

2. The program according to claim 1, wherein the predetermined condition is an operation different from a series of operations when the user preselects an attribute, and includes a condition that is satisfied according to a switching operation from the user.

3. The display switching means displays an icon that accepts the switching operation in both the first display state and the second display state, switches and displays to the second display state according to an operation on the icon in the first display state, and switches and displays to the first display state according to an operation on the icon in the second display state. The program according to claim 2.

4. The multiple types of content include content associated with a third attribute different from the first attribute and the second attribute, and the display switching means displays, regarding content information regarding content associated with the third attribute, in such a manner that it can be specified in both the first display state and the second display state regardless of the attributes preselected and stored by the user. The program according to claim 1.

5. Among the plurality of types of content, there is content associated with only the first attribute out of the first attribute and the second attribute. The second display state is a display state that does not include the display of content information regarding content associated with only the first attribute. The program according to claim 1.

6. The plurality of types of second attributes are a plurality of types of characters. The plurality of types of first attributes are a plurality of types of groups that classify the characters that are the second attributes. The program according to claim 1.

7. Among the plurality of types of second attributes, there is an attribute consisting of a plurality of characters. The program according to claim 6.

8. The plurality of types of content can be classified into any one of a plurality of types of categories including a specific type of category. The display switching means can classify and display content information regarding content for each of the plurality of types of categories. In a specific type of category, in either the first display state or the second display state, the user can identify content information regarding a predetermined number of contents among the contents associated with both the first attribute and the second attribute that have been pre-selected and stored by the user. In categories other than the specific type of category, the user can identify content information regarding content according to whether it is in the first display state or the second display state. The program according to claim 1.

9. The display switching means can display, in either the first display state or the second display state, content information regarding content classified into the specific type of category with priority over content information regarding content classified into other categories. The program according to claim 8.

10. The first display state includes a display state in which the user can identify content information regarding content associated with a first attribute selected in response to an operation from the user among the first attributes pre-selected and stored by the user. The program according to claim 1.

11. The second display state is a display state including a display mode that can be switched to a display state in which the user can identify content information regarding content associated with an attribute selected according to an operation from the user among a first attribute and a second attribute preselected and stored by the user, and can be displayed, according to the program of claim 1.

12. The computer is caused to function as means for performing a reception effect each time a favorable action from the user with respect to the content is received, wherein the reception effect includes an effect regarding the second attribute associated with the content that has received the action, according to the program of claim 1.

13. The means for performing the reception effect performs a special reception effect when the action has been received a predetermined number of times, according to the program of claim 12.

14. The plurality of types of content includes second-attribute-related content associated with any one of the plurality of types of second attributes, and the display switching means displays, for content information regarding the second-attribute-related content, the second attribute associated with the second-attribute-related content so as to be identifiable in both the first display state and the second display state, according to the program of claim 1.

15. The plurality of types of content includes posted content posted by the user, and the computer is caused to function as means for generating content information regarding posted content according to posted information from the user, and when information for designating a second attribute is included in the posted information, generating the posted content as content information regarding content associated with the designated second attribute, according to the program of claim 1.

16. The plurality of types of content includes posted content posted by the user, the user includes a plurality of specific users, and the computer is caused to function as means for receiving an action with respect to content information regarding the posted content, wherein the plurality of types of second attributes are a plurality of types of characters corresponding to each of the plurality of specific users. The program according to claim 1, wherein the display switching means changes the display mode of the content information regarding the posted content to a different display mode and displays it in response to receiving an action from the specific user with respect to the content information regarding the posted content.

17. The program according to claim 16, wherein the display switching means changes the display mode of the content information regarding the posted content to a different display mode and displays it according to whether the specific user is a specific user corresponding to a second attribute that has been preselected and stored by the user in response to receiving an action from the specific user with respect to the content information regarding the posted content.

18. The program according to claim 16, wherein the display switching means changes the display mode of the content information regarding the posted content to a different display mode and displays it according to whether the specific user is a specific user corresponding to a second attribute associated with the posted content in response to receiving an action from the specific user with respect to the content information regarding the posted content.

19. The computer is functioned as means for notifying the user that the content information associated with the second attribute can be specified by the user when the user can specify the content information associated with the second attribute preselected and stored by the user, according to the program of claim 1.

20. The computer is means for acquiring external posting information including attribute specifying information for specifying an attribute associated with the external posting information among the plurality of types of first attributes and the plurality of types of second attributes, the external posting information being information for specifying an external posting provided by an external service, and means for generating content information regarding the externally posted external posting content according to the external posting information, and functioning as means for generating, when the external posting information includes attribute specifying information, the content information regarding the external posting content associated with the attribute specified from the attribute specifying information as the content information regarding the external posting content, The first display state is a display state including display of content information regarding external posted content associated with a first attribute that has been preselected and stored by the user among the external posted content. The second display state is a display state including display of content information regarding external posted content associated with both a first attribute and a second attribute that have been preselected and stored by the user among the external posted content. The program according to claim 1.

21. A method for controlling a computer to enable a user to provide a plurality of types of content associated with attributes, comprising: The attributes include a plurality of types of first attributes and a plurality of types of second attributes. Steps for storing in a specifiable manner an attribute preselected according to an operation from the user from among the plurality of types of first attributes and the plurality of types of second attributes. Steps for switching and displaying in any one of a plurality of types of display states including a first display state in which the user can identify content information regarding content associated with a first attribute preselected and stored by the user in response to the establishment of a predetermined condition, and a second display state in which the user can identify content information regarding content associated with both a first attribute and a second attribute preselected and stored by the user. Each of the plurality of types of first attributes is a group including at least any one of the plurality of types of second attributes, and each of the plurality of types of second attributes is an attribute that can belong to at least any one of a plurality of types of groups corresponding to the plurality of types of first attributes. The method.

22. A system having a computer that performs processing for enabling a user to provide a plurality of types of content associated with attributes, comprising: The attributes include a plurality of types of first attributes and a plurality of types of second attributes. Storage means for storing in a specifiable manner an attribute preselected according to an operation from the user from among the plurality of types of first attributes and the plurality of types of second attributes. Display switching means for switching and displaying the content information related to the content associated with the first attribute preselected and stored by the user to any one of a plurality of types of display states including a first display state in which the user can identify the content information, and a second display state in which the user can identify the content information related to the content associated with both the first attribute and the second attribute preselected and stored by the user, in response to the establishment of predetermined conditions. The system, wherein each of the plurality of types of first attributes is a group including at least any one of the plurality of types of second attributes, and each of the plurality of types of second attributes is an attribute that can belong to at least any one of the plurality of types of groups corresponding to the plurality of types of first attributes.

Images