Program, method, and system

Abstract

To provide a program, a method, and a system that can efficiently restrict trouble-making activities without impeding free interchange and communication.SOLUTION: A distribution server receives muting-specification information transmitted from a user terminal of a certain user by an operation being performed at the user terminal to specify another user as an object of muting, whereby muted history of the other user that has been specified is updated, and when a comment is posted by a user out of a plurality of users participating in a virtual space of the same content who is a user satisfying restriction conditions on the basis of muted history and an all-mute flag is set to on, the posting user is deemed to be a user with tendencies to make trouble-making comments, and reflection of the comment can be restricted at user terminals of a plurality of users participating in the virtual space, including users who have not specified the user as the object of muting.SELECTED DRAWING: Figure 17

Description

[Technical field]

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

[0002] In a system in which comments and other information posted by users can be shared within a group, after a request to hide a comment from a certain user (here referred to as the first user) in a group is received from another user (here referred to as the second user), the comment from the first user is hidden on the terminal of the second user who made the request (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-91065 A Summary of the Invention [Problem to be solved by the invention]

[0004] Nuisance posts that are designated to be hidden tend to be made repeatedly by malicious users. However, in conventional systems, unless a designation to hide is made, comments posted by malicious users who repeatedly make nuisance posts are displayed. On the other hand, if a designation to hide is accepted from any user, and comments posted by the designated user are made invisible to all users in the group, for example, there is a risk that comments from the specific user will be maliciously designated to be hidden in order to deprive the specific user of the right to post (to frame the specific user), or that excessive regulation will hinder free exchange and communication.

[0005] The present invention has been devised in light of the above circumstances, and provides a program, method, and system that can efficiently regulate nuisance behavior without impeding free interaction and communication. [Means for solving the problem]

[0006] (1) A program that enables actions (e.g., comments, behaviors, etc.) received from multiple user terminals operated by multiple users having a specific relationship (e.g., users participating in a virtual space of the same content, users whose user characters exist within a predetermined range, etc.) to be reflected in the multiple user terminals so that each of the multiple users can recognize the actions, Computer, An update means (e.g., step S81 in FIG. 16 ) for updating a restriction history for a specific user by receiving restriction information (e.g., mute designation information) for designating the specific user as a restricted user (e.g., mute designation) from the user terminal; When an action is received from a user terminal operated by a user (e.g., a user for which all mute flags are set on) who satisfies the restriction conditions based on the restriction history among multiple user terminals operated by each of multiple users having the specific relationship, the device functions as a restriction means (e.g., does not execute steps S97 and S98 when NO is determined in steps S91, S92, S94, etc.) that performs processing to enable restriction of the reflection of the action in multiple user terminals including user terminals operated by users who have not designated the user as a restricted user.

[0007] According to this configuration, a user who is designated as a restricted user and who is likely to perform nuisance actions by satisfying the restriction conditions based on the restriction history updated by the user's designation as a restricted user can be restricted from reflecting actions from the user who satisfies the restriction conditions on the user terminals of multiple users who have a specific relationship with the user, including users who are not designated as restricted users. This makes it possible to efficiently restrict nuisance behavior without impeding free exchange and communication.

[0008] (2) In the above (1), the process performed by the regulating means includes a process of not reflecting an action from a user who satisfies the regulating condition in the plurality of user terminals (for example, when NO in step S99 in FIG. 17).

[0009] According to this configuration, actions from users who meet the restriction conditions based on the restriction history are not reflected, thereby preventing actions from users who tend to perform nuisance actions from being reflected and causing adverse effects on other users.

[0010] (3) In the above (1), the process performed by the regulating means includes a process of not reflecting actions from users who satisfy the regulating conditions in the plurality of user terminals in accordance with a predetermined ratio. According to such a configuration, the reflection of actions from users who satisfy the restriction conditions based on the restriction history is thinned out, thereby preventing all actions from users who tend to perform nuisance actions from being reflected, which would have a negative impact on other users.

[0011] (4) In the above (3), the actions that are to be processed not to be reflected in the plurality of user terminals according to the predetermined ratio are the same predetermined actions that are continuously received from users who satisfy the restriction conditions during a predetermined period of time.

[0012] With this configuration, it is possible to prevent other users from feeling uncomfortable due to the same predetermined action being performed consecutively for a predetermined period of time.

[0013] (5) In the above (1), the computer functioning as a setting information storage means (e.g., step S84 in FIG. 16 ) for storing in a storage unit setting information (e.g., an all mute off flag) for specifying whether or not to restrict the reflection of actions from users who satisfy the restriction condition in response to information (e.g., all mute selection information) from a user terminal for setting whether or not to restrict the reflection of actions from users who satisfy the restriction condition in correspondence with the user of the user terminal; When the regulating means receives an action from a user terminal operated by a user who satisfies the regulating conditions, the regulating means performs processing to enable regulating the reflection of the action on the user terminal operated by a user who is identified as regulating the reflection of the action from a user who satisfies the regulating conditions based on the setting information stored in the memory unit (e.g., NO in step S99 of Figure 17).

[0014] According to this configuration, restrictions on reflecting actions from users who satisfy the restriction conditions can be set for each user, thereby improving convenience.

[0015] (6) In the above (1), the restriction condition is a condition that is determined as to whether or not it is satisfied based on a restriction history updated by the update means for a predetermined period (for example, a first period, a second period, etc.).

[0016] With this configuration, even if a user has changed his / her ways and improved his / her actions, the user's history from before a specified period is taken into account and the user is determined to still satisfy the restriction conditions, which can prevent the user from being restricted more than necessary.

[0017] (7) In the above (6), the predetermined period includes a first period (e.g., 24 hours) and a second period (e.g., one week) that is longer than the first period, The restriction condition is satisfied when the number of times restriction information is received within the first period reaches a first number based on the restriction history, and is also satisfied when the number of times restriction information is received within the second period reaches a second number, which is greater than the first number, even if the number of times restriction information is received within the first period has not reached the first number (e.g., see FIG. 15).

[0018] According to this configuration, the period for which it is determined whether or not the restriction condition is satisfied and the number of times that the restriction information is received are determined in stages, so that appropriate restriction can be achieved.

[0019] (8) In the above (7), the second period is at least twice as long as the first period, The second number of times is less than twice the first number of times (see FIG. 15, for example).

[0020] According to this configuration, the second number of times determined to satisfy the restricted condition in the second period is less than twice the first number of times determined to satisfy the restricted condition in the first period. Therefore, even if a user is designated as a restricted user to the extent that the user is not determined to satisfy the restricted condition in the first period, the user may be determined to satisfy the restricted condition in the long period of the second period and restricted. This makes it possible to restrict the reflection of actions from a user designated as a restricted user on a daily basis for a long period of time.

[0021] (9) In the above (1), the update means updates the restriction history for a specific user by receiving, from a user who has transmitted restriction information for designating the specific user as a restricted user, cancellation information (e.g., mute cancellation information) for canceling the designation of the specific user as a restricted user (e.g., step S81 in FIG. 16 ); The regulating means is A means for determining whether or not a regulatory condition is satisfied based on the regulatory history (for example, steps S92 to S95 in FIG. 17), Even when removal information is received for a user who has been determined to satisfy the restriction conditions based on the restriction history and the restriction history is updated to a restriction history that does not satisfy the restriction conditions, the determination that the user satisfies the restriction conditions is maintained for the user who has been determined to satisfy the restriction conditions (for example, even if the determination is YES in step S83 of Figure 16, all mute flags are not set to off).

[0022] According to this configuration, even if the removal information is received, the determination that the restrictive conditions are satisfied is maintained, so that it is possible to prevent the restrictive conditions from being removed improperly through an operation on the user side.

[0023] (10) In the above (1), the computer When a lifting condition for a user who is subject to restriction by the restriction means is satisfied (e.g., YES in step S87 of FIG. 16), the restriction means functions as a lifting means (e.g., step S88 of FIG. 16) for lifting the restriction imposed by the restriction means on the user, The update means updates a release history (e.g., a total mute history) for a user whose restriction has been released by the release means, The criteria for determining whether the restrictive conditions are satisfied vary depending on the release history of each user.

[0024] According to this configuration, the criteria for determining whether the restriction condition is satisfied can be varied according to the release history. Therefore, the strength of the restriction can be adjusted according to the release history. For example, the more the release history, the fewer the number of times the user is designated as a restricted user, the more the restriction condition can be satisfied.

[0025] (11) In the above (10), the computer An action history update means (e.g., a log management unit 131) for updating an action history (e.g., a total comment history) for identifying actions accepted from a user terminal for each user; It functions as a notification means (for example, step S86 in FIG. 16) for notifying the administrator of the action history so that the administrator can view the action history.

[0026] With this configuration, the administrator can understand the action history.

[0027] (12) In the above (1), the update means updates a transmission history (e.g., a designated frequency) of the restriction information from a user who has received the restriction information, Whether or not the restriction condition is satisfied is determined based on the transmission history of a user who has designated a particular user as a restricted user (for example, the frequency of designation of a user to be muted becomes the number of mutes).

[0028] According to this configuration, it is possible to vary the degree of influence when a user is designated as a restricted user depending on the transmission history.

[0029] (13) In the above (1), the computer The device functions as a means for displaying specific information (for example, user characters) that can identify a plurality of users having the specific relationship, and for displaying specific information that can identify a user who satisfies the restrictive condition.

[0030] According to this configuration, specific information that can identify a user who satisfies the restrictive conditions is also displayed, making it difficult for the user to notice that the restrictive conditions are met and that the reflection of actions is restricted.

[0031] (14) In (1) above, when the regulating means receives an action from a user terminal operated by any of the special users belonging to a special type (for example, a user who is not subject to all muting set by an SP user, etc.), the regulating means performs processing to enable the action to be reflected in a user terminal operated by a user who has not designated the special user as a regulated user among the multiple users having the specific relationship, regardless of the regulating history for the special user, while performing processing to enable the reflection of the action to be regulated in a user terminal operated by a user who has designated the special user as a regulated user (for example, steps S96 to S98 in FIG. 17).

[0032] With this configuration, even if an action comes from a special user, its reflection is restricted on the user terminal of a user who has designated the special user as a regulated user, thereby respecting the user's wishes and preventing any adverse effects on that user.

[0033] (15) In the above (1), when the regulating means receives a regulated action set as an action whose reflection is regulated, it performs a process for enabling the regulating of the reflection of the action in a plurality of user terminals operated by each of a plurality of users having the specific relationship, regardless of the regulating history of the user who originated the action (e.g., Figs. 8 to 13 ); Even when the update means receives the restricted action, the update means does not update the restriction history for the user who has performed the restricted action (for example, step S81 in FIG. 16).

[0034] According to such a configuration, restricted actions and restriction history can be managed separately, which makes it possible to prevent one from affecting the other, resulting in excessive restriction.

[0035] (16) In the above (1), the specific relationship is a relationship associated with a common group (see, for example, FIG. 6 ); The update means receives restriction information from users in a common group, and updates the restriction history within the group for a specific user designated by the restriction information.

[0036] According to this configuration, the restriction history of a specific user designated by restriction information from a user associated with a common group can be immediately updated, and comments from the specific user can be prevented from being reflected in the user terminal of the designated user. In addition, since whether or not the restriction conditions are satisfied is determined for users associated with a common group, the effect of the restriction can be improved.

[0037] (17) In the above (1), the update means makes the information identifying the user who designated the restricted user based on the updated restriction history and the user designated as a restricted user unidentifiable for the multiple users.

[0038] According to such a configuration, it is possible to prevent a user from being identified and misused (for example, a specific user being designated as a restricted user by multiple users, thereby selectively satisfying the restricted conditions).

[0039] (18) A method for allowing actions (e.g., comments, behaviors, etc.) received from multiple user terminals operated by multiple users having a specific relationship (e.g., users participating in a virtual space of the same content, users whose user characters exist within a predetermined range, etc.) to be reflected in the multiple user terminals so that each of the multiple users can recognize the actions, A step of updating a restriction history for a specific user by receiving restriction information (e.g., mute designation information) for designating the specific user as a restricted user (e.g., mute designation) from the user terminal (e.g., step S81 in FIG. 16 ); When an action is received from a user terminal operated by a user (e.g., a user whose all mute flags are set to on) who satisfies the restriction condition based on the restriction history among multiple user terminals operated by each of multiple users having the specific relationship, a step of performing processing to enable restriction of reflection of the action in multiple user terminals including user terminals operated by users who have not designated the user as a restricted user (e.g., not executing steps S97 and S98 when NO is determined in steps S91, S92, S94, etc.).

[0040] According to this configuration, a user who is designated as a restricted user and who is likely to perform nuisance actions by satisfying the restriction conditions based on the restriction history updated by the user's designation as a restricted user can be restricted from reflecting actions from the user who satisfies the restriction conditions on the user terminals of multiple users who have a specific relationship with the user, including users who are not designated as restricted users. This makes it possible to efficiently restrict nuisance behavior without impeding free exchange and communication.

[0041] (19) A system that allows actions (e.g., comments, behaviors, etc.) received from multiple user terminals operated by multiple users having a specific relationship (e.g., users participating in a virtual space of the same content, users whose user characters exist within a predetermined range, etc.) to be reflected in the multiple user terminals so that each of the multiple users can recognize the actions, An update means (e.g., step S81 in FIG. 16 ) for updating a restriction history for a specific user by receiving restriction information (e.g., mute designation information) for designating the specific user as a restricted user (e.g., mute designation) from the user terminal; The system is provided with a regulating means (for example, not executing steps S97 and S98 when a NO decision is made in steps S91, S92, S94, etc.) that performs processing to enable regulating the reflection of an action in multiple user terminals including user terminals operated by users who have not designated the user as a regulated user, when an action is received from a user terminal operated by a user (for example, a user whose all mute flags are set on) who satisfies the regulating conditions based on the regulating history, among multiple user terminals operated by each of multiple users having the specific relationship.

[0042] According to this configuration, a user who is designated as a restricted user and who is likely to perform nuisance actions by satisfying the restriction conditions based on the restriction history updated by the user's designation as a restricted user can be restricted from reflecting actions from the user who satisfies the restriction conditions on the user terminals of multiple users who have a specific relationship with the user, including users who are not designated as restricted users. This makes it possible to efficiently restrict nuisance behavior without impeding free exchange and communication. [Brief description of the drawings]

[0043] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a communication system. [Diagram 2] FIG. 2 is a diagram for explaining the configuration of a distribution server. [Diagram 3] FIG. 2 is a diagram illustrating a configuration of an administrator terminal. [Figure 4] FIG. 2 is a diagram for explaining in detail the configuration of a user terminal (user terminal and broadcasting user terminal). [Diagram 5] FIG. 2 is a diagram for explaining an example of the types of content provided by a distribution server. [Figure 6] 10 is a diagram illustrating an example of log information stored in a storage unit of a distribution server. FIG. [Figure 7] 11 is a diagram showing an example of NG information stored in a storage unit of a distribution server. FIG. [Figure 8]FIG. 11 is a diagram for explaining a flowchart of a comment control process during content distribution according to the first embodiment. [Figure 9] 11 is a diagram for explaining a display example of a user terminal during content distribution in the first embodiment. FIG. [Figure 10] FIG. 11 is a diagram for explaining a flowchart of a comment control process during content distribution according to a second embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a display on a user terminal during content distribution in a second embodiment. [Figure 12] FIG. 13 is a diagram illustrating a flowchart of a comment control process during content distribution according to a third embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a display on a user terminal during content distribution in the third embodiment. [Figure 14] 11 is a diagram illustrating an example of mute-related information stored in a storage unit of a distribution server. FIG. [Figure 15] 10 is a diagram for explaining an example of the content of a restrictive condition among the mute-related information stored in the storage unit of the distribution server. FIG. [Figure 16] FIG. 13 is a diagram for explaining a flowchart of a mute-related information update process for updating mute-related information. [Figure 17] FIG. 11 is a diagram for explaining a flowchart of a comment distribution process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0044] Hereinafter, an embodiment of a communication system according to the present invention will be described with reference to the drawings. Note that the present invention is not limited to the following examples, but is indicated by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included in the present invention. In the following description, the same elements in the description of the drawings are given the same reference numerals, and redundant descriptions will not be repeated.

[0045] [First embodiment] FIG. 1 is a diagram showing an example of a hardware configuration of a communication system 1. The communication system 1 includes a distribution server 100, an administrator terminal 200, a plurality of user terminals 300a, 300b, 300c, etc., and a plurality of broadcast user terminals 400a, 400b, 400c, etc. The plurality of user terminals 300a, 300b, 300c, etc. are terminals owned by a plurality of users, and are collectively referred to as user terminals 300 below. The plurality of broadcast user terminals 400a, 400b, 400c, etc. are terminals owned by a plurality of broadcast users who are users who can independently broadcast content, and are collectively referred to as broadcast user terminals 400 below. The user terminals 300 and broadcast user terminals 400 are both used by users, and are collectively referred to as user terminals below.

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

[0047] The distribution server 100 is, for example, a computer such as a workstation or a personal computer having a communication function. The distribution server 100 manages a plurality of virtual spaces, which are virtual worlds constructed on a computer, and provides a service (content) using a virtual space selected by a user via the network 2.

[0048] The users in this embodiment include general consumers, talents, famous people, etc. Talent includes, for example, talents belonging to a service provider (operating company), entertainers, actors / actresses, comedians, multi-talents, presenters, news anchors, singers, musicians, models, and other talented people in various genres. Celebrities include, for example, famous company executives or employees, athletes, e-sports athletes, famous scholars, cultural figures, cram school instructors, famous students, and other famous people in various genres.

[0049] The virtual space is managed and set for each type of content to be provided. The content that can be provided includes, but is not limited to, content that allows users to view and experience games, live performances, events, and programs, and content that allows users to interact and communicate with each other using chats and emotes. Users can seamlessly participate in (roam) the content by accessing the distribution server 100 using the user terminal 300 or the distribution user terminal 400 and selecting the desired content, and can view and experience the virtual space corresponding to the content.

[0050] The virtual space includes three-dimensional space (space constructed based on three-dimensional data) generated by CG (Computer Graphics) and two-dimensional space (space constructed based on two-dimensional data) depending on the type of content. In addition, virtual characters (avatar objects), objects showing backgrounds and virtual objects depending on the type of content, menu objects selectable by the user, etc. are placed in the virtual space. The virtual characters placed in the virtual space include user characters that are set in advance corresponding to each user participating in the virtual space and can act according to operations from the user, and non-player characters that act based on a program.

[0051] As an example of objects to be placed in the virtual space, in the case of game content, a character object corresponding to the game and a user character of a user playing the game content are placed on a field object corresponding to the game field. In the case of live content, for example, a stage object, an audience seat object, a lighting object, etc. are placed, and a user character of a performer who is performing the live show is placed on the stage object, and a user character of a participating user is placed on the audience seat object. In the case of content that aims for communication, for example, a user character of each of the multiple participating users and an item object that can be used for communication are placed.

[0052] The distribution server 100 stores information for displaying images in a plurality of virtual spaces corresponding to the distributable contents on a user terminal and sound information for outputting sounds in the storage unit 120. In addition, the distribution server 100 provides contents (services) to users by distributing content data including display information for displaying images in the virtual space of the corresponding contents and sound information for outputting sounds in response to access from the user terminal.

[0053] The content data includes, for example, information for identifying information relating to objects placed within the virtual space (e.g., the type of object, placement position, orientation, posture, appearance, etc.), information relating to the user characters of each user participating in the virtual space (e.g., the type of user character, placement position, orientation, posture, appearance, motion data, audio data, etc.), objects representing backgrounds and virtual objects according to the type of content, and information for identifying menu objects selected by the user.

[0054] The posture, position, and expression of objects in the virtual space change in response to operations from the user terminal, etc., and the state of the placed objects changes with the passage of time, etc. Therefore, by distributing content data at predetermined time intervals (for example, every 0.016 seconds, which is about 60 fps), it becomes possible to display images in the virtual space that change from moment to moment on the user terminal.

[0055] The administrator terminal 200 is used by the operator of the service provider company, etc. The administrator terminal 200 is, for example, a computer having an operation input function and a communication function such as a personal computer. The administrator creates, builds, modifies, and updates the content and images in the virtual space managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200. For example, new content and images in the virtual space are generated and built, and existing content and images in the virtual space are changed and modified. The administrator also sets and updates the information managed in the storage unit 120 of the distribution server 100 via the administrator terminal 200.

[0056] In this embodiment, the distribution server 100 and the administrator terminal 200 are each an independent computer (device), but they may be realized by a single computer, or the function of one of these computers (e.g., the distribution server 100) may be realized by multiple computers (e.g., multiple servers).

[0057] The user terminal 300 is used by a user who wants to view and experience the content. The user terminal 300 may be, for example, a computer having an operation input function and a communication function, such as a personal computer, a tablet terminal, or a smartphone. The user terminal 300 may have a motion capture function for capturing the user's movements, similar to the broadcasting user terminal 400 described later.

[0058] The user terminal 300 communicates with the distribution server 100 in response to an operation on the terminal, and receives content data of the content selected by the user. Based on the received content data, the user terminal 300 constructs a virtual space of the content selected by the user from among the virtual spaces constructed in the distribution server 100 in a storage area of ​​the user terminal 300, and displays images in the virtual space and outputs sounds. This makes it possible to view and experience the virtual space of the content via the user terminal 300.

[0059] Furthermore, the user terminal 300 accepts operations on the displayed virtual space and objects. The user terminal 300 transmits information corresponding to the operations on the terminal to the distribution server 100, and can cause the user's character to act, move, etc. in the virtual space of the content in which the user is participating. As described above, based on the content data transmitted from the distribution server 100 at predetermined time intervals, the movement of the user's character can be reflected (synchronized) in the virtual space of each user terminal 300 of the users participating in the same content.

[0060] Furthermore, the user terminal 300 allows the user to view and experience the virtual space of the content, and can post a comment including an arbitrary message as an example of an action for the virtual space of the content in which the user is participating, in response to an operation on the terminal. By posting a comment, the comment can be reflected on each user terminal 300 so that the user participating in the content can confirm the comment.

[0061] The broadcasting user terminal 400 is used by a broadcasting user who can broadcast content. The broadcasting user terminal 400 has a motion capture function that captures the broadcasting user's movements, in addition to an operation input function and a communication function (for example, a head-mounted device (HMD), a device equipped with an imaging device and analyzing the user's movements from images captured by the imaging device). The HMD is worn on the user's head, and the user holding a controller capable of communicating with the HMD can operate the displayed virtual space and virtual characters by moving the head or hand or by operating buttons on the controller.

[0062] The broadcast user terminal 400 acquires motion information for identifying the broadcast user's head or hand movements and controller operations, and audio information for identifying the broadcast user's voice, and transmits them to the broadcast server 100, thereby reflecting the movements and audio of the broadcast user's user character in the participating virtual space. This allows the broadcast user's user character to operate in the virtual space as if it were an alter-ego of the broadcast user. As described above, based on the content data transmitted from the broadcast server 100 at predetermined time intervals, the movements and audio of the broadcast user's user character in the virtual space in each user terminal of the users (including the broadcast user) participating in the virtual space can be reflected (synchronized).

[0063] In addition, a broadcast user may be a general user (simple viewer / participant) who uses a terminal with the same configuration as the broadcast user terminal 400 as the user terminal 300 to view and experience the broadcast content, or may be a general user who uses a separate terminal with a different configuration from the broadcast user terminal 400 as the user terminal 300. The broadcast user terminal 400 and the user terminal 300 may be terminals with the same configuration or different terminals. Also, a broadcast user may participate in a virtual space in the position of a broadcaster who broadcasts content, or in the position of a general user (simple viewer / participant) rather than in the position of a broadcaster. For this reason, a broadcast user is included in the user. A broadcast user can select or change which position he / she is in at a specific timing (for example, when logging in, when starting content broadcasting, when displaying the broadcast user's user character in the broadcast content, etc.).

[0064] <Distribution server configuration> 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.

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

[0066] 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), etc. The storage unit 120 stores programs for executing various control processes (for example, a program for managing and providing content using a virtual space), various data, etc. The various data stored in the storage unit 120 includes information for identifying an image of the virtual space provided for each type of content, user information about users, NG information about NG words, log information about access from users, mute-related information about muting, etc.

[0067] The control unit 130 is configured with a CPU (Central Processing Unit) etc. The control unit 130 controls the overall operation of the distribution server 100 by executing the programs stored in the storage unit 120.

[0068] The following describes the functional configuration of the control unit 130. The control unit 140 functions as at least a log management unit 131, a content management unit 132, a data delivery unit 133, a user management unit 134, an NG management unit 135, a comment control unit 136, and a mute management unit 137.

[0069] In response to access from a user terminal, the log management unit 131 stores in the memory unit 120 as log information, participating user information for identifying users participating in each content / virtual space, related user information for identifying related users who are associated with the content, such as those who actively distribute the content, and action information (comment history, described below) for identifying the action history of users in the virtual space (for example, the content of posted comments and the history of users who posted the comments, etc.).

[0070] The content management unit 132 stores and updates information for identifying an image in a virtual space corresponding to the content set by the administrator terminal 200 in the storage unit 120 via the communication unit 110. The content management unit 132 stores, for example, information for identifying the type of content set by the administrator terminal 200, information for identifying an image in the virtual space for each piece of content, and, for content (program) distributed at a predetermined date and time, information for identifying the date and time of distribution in the storage unit 120. The information for identifying an image in a virtual space includes information on objects arranged in the virtual space and user characters corresponding to users participating in the virtual space.

[0071] The data distribution unit 133 distributes content data to the accessing user terminal at predetermined time intervals for displaying images within the virtual space of the content selected on each terminal and managed by the content management unit 132.

[0072] The user management unit 134 stores and updates user information relating to users in the storage unit 120. The user information relating to users includes, for example, an ID for identifying the user, a user name, and the like.

[0073] The NG management unit 135 stores and updates NG information related to NG words in the storage unit 120. NG words are defined words (messages) whose reflection can be regulated or restricted in chats in a virtual space. The NG information related to NG words includes, for example, information for identifying NG words defined for each user and default NG words defined in advance.

[0074] The comment control unit 136 receives comments posted by each user and transmits comment information for identifying the comment to a user terminal of a user participating in the same content as the user who posted the comment, thereby reflecting the comment in the virtual space of the content. The comment control unit 136 also determines whether or not the posted comment contains NG words, and in a situation where the comment contains NG words and should be restricted, restricts the transmission of the comment information so that at least the NG words contained in the comment are not reflected in the virtual space. In this embodiment, a posted message (comment) is shown as an example of an action on the virtual space and an action to be restricted, but is not limited to a posted message (comment) as described later.

[0075] The mute management unit 137 stores and updates mute-related information related to muting in the storage unit 120. Muting is a function that does not reflect comments posted by other specific users designated by the user among other users in the user terminal of the user. In this embodiment, for a user who satisfies a regulation condition that is predetermined according to the mute reception history that has been designated as a mute, control is performed so that the reflection of the posted comments can be regulated and limited not only in the user terminal of the user who has designated the user as a mute but also in the user terminal of the user who has not designated the user as a mute (hereinafter, also referred to as full mute control). The mute-related information includes, for example, information for identifying the mute reception history of the user that has been designated as a mute, the mute designation history of the user that has designated other users as a mute, history related to full mute control, and information for identifying the content that satisfies the regulation condition.

[0076] The comment control unit 136 restricts the transmission of comment information to the user terminal of the designated user who has designated the user who posted the comment as a mute based on the mute related information so that the comment is not reflected in the user terminal of the designated user. In addition, when the user who posted the comment satisfies the restriction condition according to the mute history and is a user who is a target of the full mute control, the comment control unit 136 restricts the transmission of comment information so that the comment is not reflected in the user terminal of not only the designated user who has designated the user as a mute but also the user terminal of the user who has not designated the user. In this embodiment, a posted message (comment) is shown as an example of an action on the virtual space and an action to be muted or to be subject to full mute control, but is not limited to a posted message (comment) as described later.

[0077] <Administrator terminal configuration> 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 connected to each other by a bus line.

[0078] The communication unit 210 is a communication interface equipped with 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, and the like. The storage unit 220 stores programs for executing various control processes (e.g., programs for managing content using a virtual space), various data, and the like.

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

[0080] The control unit 250 is configured with 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.

[0081] The following describes the functional configuration of the control unit 250. The control unit 250 functions as at least a content setting unit 251, a user setting unit 252, an NG setting unit 253, and a mute-related setting unit 254.

[0082] The content setting unit 251 stores and updates information about the content and virtual space managed by the content management unit 132 of the distribution server 100 in response to an operation on the administrator terminal 200. This allows, for example, information for identifying the content, information for identifying an image in the virtual space for each piece of content, information for identifying the date and time of distribution, information for setting and identifying a user having relevance to the content (a related SP user, described later) and the like to be stored and updated in the storage unit 120.

[0083] The user setting unit 252 sets user information on users managed by the user management unit 134 of the distribution server 100 in response to an operation on the administrator terminal 200. The setting of user information includes, for example, a distribution user setting in which the user is set as a distribution user capable of content distribution in response to an application from the user, and an SP user setting in which a special user (hereinafter also referred to as an SP user) can set NG words in response to an application from the user. For example, when an application is made from a user belonging to a talent or a famous person and the user meets certain criteria (requirements), the administrator sets the user as a distribution user or an SP user. The SP user is set from among talents and famous people. Note that the administrator may set a specific user as a distribution user or an SP user even when there is no application.

[0084] In addition to the SP user setting, the SP user setting also includes the setting of a type (for example, a type of idol group A, a type of young actor, a type of big-name comedian, a type of professional baseball player, a type of professional shogi player, etc., hereinafter referred to as SP1, SP2, SP3, etc.) that is classified based on various parameters such as the genre, group, age group, and gender of the user. In addition, a user set as a distribution user is able to distribute content independently, and is also set as an SP user who can set NG words. For this reason, in the distribution user setting, the type is also set when setting the distribution user, just like the SP user. In the following, the SP user includes the distribution user. By setting user information about the user, for example, information for identifying the type of the user (general user, distribution user, SP user, etc.) is stored and updated in the storage unit 120 in correspondence with a user ID for identifying the user. In addition, the broadcast user setting and SP user setting (including type setting) are shown as an example performed in response to the operation of the administrator terminal 200 by the administrator, but the present invention is not limited to this, and instead of or in addition to this, they may be performed in response to the operation of the user terminal by the user himself. In this case, the administrator may transmit a setting form screen for performing broadcast user setting and SP user setting or a URL that can be connected to said screen to the user who is the target of broadcast user setting and SP user setting from among the talents and famous people via the administrator terminal 200, thereby making it possible to set in response to the operation of the user who is the target of setting. This makes it possible to prevent broadcast user setting and SP user setting from being performed by general users.

[0085] The NG setting unit 253 sets NG information on NG words managed by the NG management unit 135 of the distribution server 100 in response to an operation on the administrator terminal 200. The setting of NG information on NG words includes individual NG settings for setting NG word candidates requested in response to an application from an SP user (including a distribution user) as NG words of the requesting user, and removing words requested for removal from NG words as NG words, and default NG settings for setting / removing default NG for each type of SP user or default NG common to all users.

[0086] For example, when an NG word candidate applied by an SP user meets a certain standard (requirement), such as low risk of leading to excessive restrictions, the administrator sets the NG word candidate as the NG word of the user. Note that an NG word candidate applied by an SP user may be set as the NG word of the SP user without waiting for the administrator to set it. For example, an NG word candidate applied by an SP user who is participating in a virtual space of a certain content (including the user himself / herself distributing) may be set as the NG word of the SP user without waiting for the administrator to set it. In this case, the NG word candidate may be set as the NG word of the SP user only in the content in which the SP user is participating, and after the distribution of the content is completed, the word may be removed from the NG word and set as an NG word candidate, and may be in a state of waiting for the administrator to set it. This allows the word candidate to be immediately set as an NG word in response to an application from the SP user only in the content in which the SP user is participating, and subsequently restricts the word from being reflected in the content in which the SP user is participating.

[0087] Furthermore, the administrator sets words that are determined to be restricted in consideration of, for example, the trends and fashions of the time, as default NG words. By setting NG information related to NG words, for example, information for identifying NG words in association with a user ID for identifying a user, information for identifying NG words predetermined for all users, and information for identifying NG words predetermined for each type of SP user are stored and updated in the storage unit 120.

[0088] The mute-related setting unit 254 sets the cancellation of all mute control, the compulsory activation of all mute control, special users who are excluded from the all mute control regardless of their mute history, and the contents of the restriction conditions, etc., in response to an operation on the administrator terminal 200. For example, in response to an operation on the administrator terminal 200, the administrator performs a setting to cancel all mute control when it is determined that the current mute history and comment history in a recent fixed period are showing signs of improvement, triggered by a cancellation request from a user who is a target of the all mute control, and a setting to compulsorily activate all mute control for a user who is determined to be immediately subject to all mute control based on the mute history of the user and comment history in a recent fixed period. In addition, in response to an operation on the administrator terminal 200, the administrator performs a setting to, for example, set special users (hereinafter also referred to as users not subject to all mute) who are excluded from the all mute control regardless of their mute history, such as SP users, and to change and update the contents of the restriction conditions. In response to a request from the administrator, the administrator terminal 200 can request the distribution server 100 for mute-related information including the mute history of the specified user and past comment history, and can display the mute-related information including the mute history of the specified user and the comment history for a fixed period of time based on the information in response to the request. In addition, the administrator terminal 200 can transmit information that can identify the setting contents to the distribution server 100 in response to a setting operation from the administrator, and can update the information stored in the storage unit 120 in accordance with the setting contents. The contents of all users not subject to mute and the restriction conditions set by the administrator are stored in the storage unit 120 of the distribution server 100. The administrator may set all users not subject to mute in response to a request from an SP user or the like to be not subject to all mute.

[0089] <User terminal configuration> Next, the configuration of the user terminal (user terminal 300 and broadcast user terminal 400) will be described in detail. As shown in Fig. 4, the user terminal comprises a communication unit 310 that communicates with other computers including the broadcast server 100, a storage unit 320 that stores various data, an input unit 330 for inputting operations, etc., an output unit 340 for outputting images, etc., and a control unit 350 that controls the entire computer. The communication unit 310, storage unit 320, input unit 330, output unit 340, and control unit 350 are connected to each other by a bus line.

[0090] The communication unit 310 is a communication interface equipped with a NIC for 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, a program for viewing content using a virtual space, a program for distributing content using a virtual space via the distribution server 100 in a distribution user terminal, etc.), various data, and the like.

[0091] The input unit 330 includes an input device (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, a microphone, etc.) for receiving input operations and voices from the user. The distributor user terminal 400 is equipped with an input device such as an HMD with a motion capture function, and includes a motion input unit as the input unit 330 that acquires the user's movements as motion information. In this way, the distributor user terminal 400 used by the distributor user for content distribution has different hardware and functions from the user terminal 300 used for participating as a general user.

[0092] The output unit 340 includes an output device (display, speaker, etc.) for presenting and outputting information (text, image, sound, etc.) to the user. The control unit 350 is composed of a CPU, etc. The control unit 350 controls the overall operation of the user terminal 300 by executing programs stored in the storage unit 320.

[0093] The following describes the functional configuration of the control unit 350. The control unit 350 functions as an information acquisition unit 351, a virtual camera control unit 352, a display control unit 353, an audio output control unit 354, a participation information transmission unit 355, and an input information transmission unit 356.

[0094] The information acquisition unit 351 acquires content data and comment information, etc. from the distribution server 100 via the communication unit 310, and stores in the memory unit 320 information for displaying an image in a virtual space in which various objects are arranged based on the content data, and also stores in the memory unit 320 information for displaying comments posted based on the comment information.

[0095] Virtual camera control unit 352 is placed in the virtual space stored in storage unit 320 and controls a virtual camera for specifying an area (visible area) of an image in the virtual space to be displayed on user terminal 300. Virtual camera control unit 352 controls the position, direction, inclination, etc. of the virtual camera in response to an operation on input unit 330.

[0096] The display control unit 353 displays on the display unit (such as a display) an image corresponding to a field of view area, which is a field of view from a virtual camera, in the virtual space stored in the storage unit 320 based on the content data acquired by the information acquisition unit 351. In other words, the user can change the position, direction, inclination, etc. of the virtual camera arranged in the virtual space in response to an operation on the input unit 330, thereby displaying on the user terminal 300 an image within the field of view of the virtual camera among the images in the virtual space and visually confirming it.

[0097] In this embodiment, an example has been shown in which information for displaying an image in a virtual space based on content data is stored in memory unit 320, a virtual camera is placed in the virtual space stored in memory unit 320, and the field of view displayed on user terminal 300 is varied by controlling the virtual camera. However, this is not limited to this, and for example, a virtual camera of the user may be placed in a virtual space stored in memory unit 120 of distribution server 100, the virtual camera may be controlled by virtual camera control unit 352 to vary the field of view of the virtual camera, and data for identifying an image within the field of view may be received and displayed on user terminal 300.

[0098] Furthermore, the display control unit 353 causes the display unit (such as a display) to display the posted comment history stored in the storage unit 320 based on the comment information acquired by the information acquisition unit 351. The audio output control unit 354 causes the audio output unit (such as a speaker) to output audio based on the content data acquired by the information acquisition unit 351.

[0099] In addition, the display control unit 353 displays a UI (User Interface) image (including, for example, a menu image selectable by the user and an operation image for accepting an operation) in a manner corresponding to the content being distributed based on the program stored in the storage unit 320. In this embodiment, different UI images are displayed on the user terminal 300 used to participate as a general user and the distributor user terminal 400 used by the distributor user for content distribution. For example, a UI image for posting a comment may be displayed on the user terminal 300 (when the program is executed when viewing / experienced) but not on the distributor user terminal 400 (when the program is executed when distributing content) for mainly communicating by voice. In addition, since the menu items required during viewing / experienced and during content distribution are different, the UI image for selecting a menu may be different between the user terminal 300 (when the program is executed when viewing / experienced) and the distributor user terminal 400 (when the program is executed when distributing content).

[0100] When a user wishes to participate in a screen showing a list of content being distributed, the participation information transmission unit 355 transmits participation information to the distribution server 100. The participation information is information indicating that the user will participate in the content input (selected) via the input unit 330. The participation information includes information for identifying the content to be participated in, the user ID of the user, and the like.

[0101] The input information transmitting unit 356 transmits the voice information and the operation input information acquired by the input unit 330 to the distribution server 100. The operation input information includes various information such as operation information (including, for example, motion information acquired by the motion input unit 260 (HMD, etc.)) for specifying an operation for an object in a displayed virtual space or a user character arranged in the virtual space, comment posting information for specifying a comment input by a user to post a comment to a participating content, user application information for specifying a setting application / cancellation application to a distribution user or SP user or an application for setting / cancellation of an NG word, mute designation information for specifying a user designated as a mute target and a designated user who designates the user as a mute target, mute cancellation information for specifying a user who cancels the mute target among users designated as a mute target and a canceling user who is going to cancel the designation of the mute target, all mute cancellation application information for requesting cancellation of all mute control, and all mute selection information for a user to select whether to reflect comments from users subject to all mute control without censoring or to restrict reflection.

[0102] For example, instead of or in addition to inputting a message to be a candidate for a NG word, the application for setting a NG word may be accepted by dragging and highlighting the message portion to be a candidate for a NG word among the comments reflected as a comment history in the virtual space of the content in which the SP user himself / herself participates. This reduces the effort required for applying for a candidate for a NG word.

[0103] In this embodiment, regardless of whether a comment input by a user to post a comment contains an NG word, the comment is reflected in the virtual space of the content displayed on the user terminal of the user at the time of input (posting). On the other hand, if the posted comment contains an NG word and is therefore restricted from being reflected, the comment is restricted from being reflected in the virtual space of the content displayed on the user terminal of other users than the user who posted the comment.

[0104] <Content type> Next, an example of the type of content provided by the distribution server 100 will be described. The types of content provided can be broadly divided into content for communicating with other users who are participating and have no association with any of the SP users (including the distribution user) set by, for example, celebrities or famous people, and content that has an association with any of the SP users. Content that has no association with any of the SP users refers to, for example, content that is not distributed proactively by any of the SP users, content in which it has been previously determined that any of the SP users will participate, and content that does not assume that communication will be made regarding any of the SP users (for example, content in which fans of a specific celebrity who is an SP user gather). On the other hand, content that has an association with any of the SP users refers to, for example, content that is distributed proactively by any of the SP users, content in which it has been previously determined that an SP user will participate at some timing before the content starts, and content that assumes that communication will be made regarding any of the SP users as a subject (for example, content in which fans of a specific celebrity who is an SP user gather).

[0105] As shown in Fig. 5, communication content is provided as content for communicating with other participating users who are not related to any SP user, and includes, for example, community content for exchanging information about a specific region, athletic content for controlling a user character to play an athletic game together with other users, and battle content for controlling a user character to battle other users. Content for communicating with other participating users who are not related to any SP user is also referred to as the first type of content below.

[0106] In the first mode of content, the user can participate in the desired content at any time, and the SP user, a talent or a famous person, can also participate in the desired content at any time. Therefore, the first mode of content is content in which the SP user may or may not participate, and content in which a topic about any SP user may or may not come up, and can be said to be content that does not involve the SP user.

[0107] In contrast, as the contents related to any of the SP users, there are provided program distribution contents that are distributed periodically and event contents that are distributed as events. The program distribution contents include, for example, talent contents that a specific talent set in the SP user appears and distributes independently, celebrity contents that a specific celebrity set in the SP user appears and distributes independently, and fan social gathering contents in which fans of a specific talent or a specific celebrity set in the SP user do not appear and the specific talent or celebrity itself gathers and communicates with each other. Among the contents related to any of the SP users, the program distribution contents that are distributed periodically are also referred to as the second type of content below.

[0108] Event content includes, for example, live content that broadcasts a live performance by a specific talent (e.g., a specific singer or a specific idol group) set by the SP user, and fan meeting (also called fan service) content in which a specific talent interacts with their fans.

[0109] It is expected that the number of users participating in event content will be relatively larger than that of program distribution content. Therefore, the frequency of comments posted by many users will increase, and the period during which each comment is displayed will become shorter, making it difficult to grasp, and in live content, the possibility that SP users will not be able to recognize the comments and will have difficulty reacting to them will increase. For this reason, when distributing event content, multiple rooms (corresponding to multiple virtual spaces) will be prepared for the event content, and participating users will be assigned to one of the multiple rooms to enter, and only comments from users in the room they are in will be displayed on the user terminal of the participating user, and comments from users entering other rooms will not be displayed.

[0110] In addition, an SP user who distributes a live broadcast selects a room that the SP user will enter from among multiple rooms, and displays an image of the selected room (in the virtual space) on the user terminal of the SP user, while allowing the SP user to check comments from users who will enter the room. This allows comments posted by many users participating in the event content to be distributed across multiple rooms, preventing the period during which each comment is displayed from becoming too short, and preventing the SP user, who plays the leading role in a live broadcast, from easily recognizing comments and being unable to react to them. On the other hand, the actions and voices of a user character such as a specific talent related to the event content may be reflected only in a room selected by a specific talent, etc. (only users who enter the room selected by a specific talent, etc. can view them) depending on the type of content, or may be mirrored in each of multiple rooms corresponding to the content and reflected in each room (all users who enter the multiple rooms can view them regardless of the room selected by a specific talent, etc.). Among the contents related to any SP user, event content distributed as an event is also referred to as third mode content below.

[0111] In both the second and third mode contents, the event is essentially started when users who wish to participate can participate (enter) at a predetermined date and time, or when the user character of the SP user who is the main character is displayed. However, in the second and third mode contents, except for the fan social gathering contents, the user character of the SP user is displayed in the virtual space at the timing determined by the operator or the timing of the SP user who is the main distributor. In addition, the fan social gathering contents among the second mode contents are contents where fans of a specific SP user gather, and are not participated in by the specific SP user himself. For this reason, the second and third mode contents can be said to be contents in which a specific SP user always participates or a topic about a specific SP user always comes up, and can be said to be contents related to any of the SP users. However, even during a period in which general users, etc. participate in the content, there may be a period in which the user character of the SP user who is the main character or subject of the content does not actually appear (is not displayed) in the virtual space.

[0112] As described above, the contents of the first to third modes are managed in the content management unit 132 of the distribution server 100 in response to operations on the administrator terminal 200. A user terminal can participate in the content by accessing the distribution server 100 and selecting any of the contents on a screen for selecting the content the user wishes to view or the like from among a plurality of types of content. The distribution server 100 stores and updates log information for each content in the storage unit 120 by the log management unit 131.

[0113] FIG. 6 is a diagram for explaining an example of log information stored in the storage unit 120 of the distribution server 100. FIG. 6(a) shows items of log information stored when participating in any of the contents of the first mode. For the contents of the first mode, the user IDs of participating users participating in the content, comments posted to the content, and comment history for identifying the users who posted are stored for each content. Participating users (users participating in a group of a certain content) who participate in a common content among the contents of the first mode and are associated with the content (group) as shown in FIG. 6(a) can be said to be users having a specific relationship.

[0114] FIG. 6(b) shows items of log information stored when participating in any of the second mode contents. For the second mode contents, the user ID of a specific SP user (e.g., a distribution user who actively distributes the content, a talent who has gathered fans, etc., hereinafter also referred to as a related SP user) having a relationship with the content, the user ID of a participating user participating in the content, and comments posted on the content and a comment history for identifying the user who posted the comments are stored for each content. The related SP users and participating users who participate in a common content among the second mode contents and are associated with the content (group) as shown in FIG. 6(b) can be said to be users having a specific relationship.

[0115] FIG. 6(c) shows items of log information stored when a user participates in any of the contents of the third mode. In the contents of the third mode, a related SP user having a relationship with the content is determined for each content. In addition, in the contents of the third mode, a plurality of virtual spaces are associated with one content. In the contents of the third mode, a plurality of rooms corresponding to each of the plurality of virtual spaces are provided, and a user who participates in the content is assigned to one of the rooms, and a related SP user having a relationship with the content (for example, a broadcasting user who broadcasts a live performance, a talent who has gathered fans, etc.) can select a room to enter and check images and comments in the room. Therefore, for the contents of the third mode, for each content, the user ID of the related SP user having a relationship with the content, the selected room selected by the related SP user from among the plurality of rooms, the user ID of the participating user assigned to room 1 of the plurality of rooms and the comment history posted to room 1, and the user ID of the participating user assigned to room 2 of the plurality of rooms and the comment history posted to room 2 are stored for each of the plurality of rooms, such that the user ID and comment history of the participating user are stored for each of the plurality of rooms. The related SP users and participating users who participate in a common content among the third mode contents and are associated with the content (group, multiple rooms, etc.) as shown in FIG. 6(c) can be said to be users who have a specific relationship.

[0116] It should be noted that during the first mode of content distribution, it can be said that the special conditions for the SP user, such as the period during which the SP user is actively distributing or the period during which the SP user is gathering fans, are not met. In contrast, during the second mode of content distribution and the third mode of content distribution, it can be said that the special conditions for the SP user, such as the period during which the SP user is actively distributing or the period during which the SP user is gathering fans, are met.

[0117] By participating in any of the contents, the user can post and check a comment, which is one of the actions, while viewing images and the like in a virtual space corresponding to the content. However, in this embodiment, in a situation where an NG word is included and should be restricted, the NG word is restricted so that the NG word is not reflected in the virtual space of the content. As described above, the SP user can apply for a NG word candidate in response to an operation on the user terminal. In addition, the administrator can check the application contents from the user by connecting to the distribution server 100 via the administrator terminal 200, and can set and update NG information related to NG words managed by the NG management unit 135 of the distribution server 100 by the NG setting unit 253 in response to an operation on the administrator terminal 200.

[0118] Fig. 7 is a diagram showing an example of NG information stored in the storage unit 120 of the distribution server 100. The NG information stored in the storage unit 120 includes information for specifying default NG words commonly applied to all users. As shown in Fig. 7(a), the default NG words commonly applied to all users are set by the administrator, for example, words that violate public order and morals or the law, words that are linked to criminal acts, words that may cause discomfort or disadvantage to other users, or words that may slander.

[0119] The NG information stored in the storage unit 120 includes information for identifying default NG words to be applied to each type of SP user. The words to be set as NG words by the SP user vary depending on the genre, group, age group, etc. of the SP user, while the same words are included for the same type and the same word setting application is likely to be made by SP users of the same type. For this reason, the administrator sets default NG words to be applied to each type in advance, taking into account the type of SP user. This reduces the effort required for each SP user to set their own NG words from the very beginning. Note that the default NG words set for each type differ depending on the content of the type, and therefore may include different NG words for each type. As shown in FIG. 7(b), the words to be set as NG words for a type are stored in NG information for identifying default NG words for each type of SP user.

[0120] The NG information stored in the storage unit 120 also includes NG information stored for each user. Fig. 7(c) shows the NG information stored for each user. The NG information for each user is stored in association with user information including, for example, a user ID and a user name. In association with a user ID, a user name and the type of the user (general user: nom, SP user: SP1, SP2..., distribution user: SP1α, SP2α..., etc.) are stored, and further, as the NG information, user application information, individual NG information, NG related information, and prohibited condition information are stored.

[0121] The application information is information for identifying the contents of an application from a user. The application information includes, for example, information indicating a desire to set up a distribution user or an SP user, or a desire to cancel the setting, information for identifying NG word candidates applied for registration by the SP user, NG words applied for cancellation, etc. The administrator connects to the distribution server 100 via the administrator terminal 200, and confirms and considers the contents of the application based on the application information, and sets and cancels distribution users, etc., and sets and cancels NG words for each user. When a distribution user, etc. is set or canceled, the type shown in FIG. 7(c) is updated. Also, when an NG word is set or canceled for each user, the individual NG information shown in FIG. 7(c) is updated.

[0122] The individual NG information shown in Fig. 7(c) is information for identifying NG words set for each user. For example, when the administrator sets NG words for a user, information for identifying the NG words is additionally stored in the individual NG information for that user, and when the administrator cancels the NG words for the user, information for identifying the NG words is deleted from the individual NG information for that user. Note that the NG words set individually differ depending on the SP user, and therefore may include different NG words for each SP user.

[0123] The NG-related information shown in Fig. 7(c) is information for identifying the history of NG words that have been restricted from being reflected because they are included in comments posted by a user. When a comment contains an NG word and is restricted from being reflected in the virtual space, the comment control unit 136 of the distribution server 100 stores and updates information that can identify the NG word (message) included in the comment and the SP user (SP user who triggered the restriction) who set the NG word as the NG word to be restricted (including the case of setting the type NG) as NG-related information of the user who posted the comment. The NG-related information is updated every time a user posts an NG word and is restricted.

[0124] In this embodiment, for a user who satisfies the prohibition condition based on the NG related information for each user, control is performed to prohibit the user from posting comments regardless of whether the comment contains an NG word. For example, when the number of times that an NG word is posted to a certain SP user reaches a predetermined number (for example, 5 times), it is determined that the prohibition condition is satisfied, and the user is prohibited from posting comments to the content to which the certain SP user is related.

[0125] In addition, a user who repeatedly uses NG words also tends to repeatedly use NG words against SP users of the same type as the SP user who set the NG words. For this reason, comments posted by a user who satisfies the prohibition condition based on the NG-related information for a certain SP user are prohibited not only from content related to the certain SP user, but also from content related to SP users of the same type as the certain SP user.

[0126] The prohibited condition information shown in Fig. 7(c) is information for identifying the type of SP user who satisfies the prohibited condition, information for identifying the SP user, etc. When a comment is posted by a user who satisfies the prohibited condition in content related to an SP user of the prohibited type, the comment control unit 136 of the distribution server 100 prohibits the content from being reflected in the virtual space, regardless of whether the comment contains an NG word or not.

[0127] <Specific example of comment control in content of the first aspect> Next, the comment control during the content distribution of the first aspect will be described in more detail. The content of the first aspect has no relation to any SP user, and users can participate at any time regardless of whether they are SP users, talents, or celebrities. Therefore, in a content in which a general user has participated and already engaged in exchanges, a situation may occur in which an SP user who has set an NG word from the middle of the content participates as a general user, not as a distributor. However, it is not possible to predict whether an SP user will participate in the content or at what timing. In addition, there is a possibility that a comment containing an NG word set by an SP user who is about to participate has already been posted in the virtual space of the content. Therefore, during the content distribution of the first aspect in this embodiment, it is determined whether or not the SP user is included in the users participating in the same content, and comment control is performed according to the determination result. In addition, when an SP user participates in any of the contents of the first aspect, a control is performed to delete and update a comment containing an NG word set by the SP user from the comment history and reflect it in the virtual space.

[0128] 8 is a diagram for explaining a flowchart of the comment control process during content distribution of the first mode. The comment control process during content distribution of the first mode is a process executed for each piece of content, and is repeatedly executed at predetermined time intervals by the control unit 130 of the distribution server 100. The distribution server 100 performs various processes including the comment control process during content distribution of the first mode based on a program stored in the storage unit 120.

[0129] First, in step S10, it is determined whether or not participation information has been received from a user terminal. If it is determined that the participation information has not been received, the process proceeds to step S14. On the other hand, if it is determined that the participation information has been received, it is determined in step S11 whether or not the new participating user is an SP user who can set NG words. In step S11, it is determined based on the user information shown in FIG. 7(c) whether or not the type of the user ID identified from the received participation information is SP rather than nom.

[0130] If it is not determined in step S11 that the newly participating user is an SP user, in step S12, a user character corresponding to the newly participating user is placed at a predetermined position in the virtual space of the participated content, and comment history information for identifying the comment history of the participated content (see FIG. 6(a)) is output to the user terminal of the newly participating user. As a result, content data in which the user character of the newly participating user is placed in the virtual space is distributed from the distribution server 100, so that the user character can be reflected and displayed in the virtual space on the user terminal of the user participating in the content. In addition, the user terminal of the newly participating user can identify and display the comment history posted in the participated content by receiving the comment history information.

[0131] On the other hand, when it is determined in step S11 that the user is an SP user, if the comment history of the participated content in step S13 contains a NG word (e.g., individual NG, type NG) set for the newly participating SP user, the comment containing the NG word is deleted from the comment history and updated, and the process proceeds to step S12. As a result, even if the comment history contains a comment containing a NG word set for the SP user at the time the SP user participates, comment history information from which the comment containing the NG word has been deleted is output, so that it is possible to prevent a comment containing a NG word from being displayed on the user terminal of the SP user.

[0132] In step S13, when a comment including a NG word set for the newly participating SP user is deleted from the comment history, the comment history information is output only to the SP user, but it is not limited to this, and may be output to the user terminals of other users participating in the content in addition to the SP user, and the comment including the SP user's NG word may be updated so that it is not displayed in the comment history on the user terminals of the other users. Also, in step S13, an example has been described in which a comment including a NG word set for the newly participating SP user is deleted from the comment history, but it is not limited to this, and the comment including the NG word set for the newly participating SP user may be updated to a comment in which the NG word portion is converted to obscured characters as described below.

[0133] In step S14, it is determined whether or not a comment has been posted on the content from any of the participating users, i.e., whether or not comment posting information has been received. If it is determined that comment posting information has not been received, the comment control process is terminated. On the other hand, if it is determined that comment posting information has been received, it is determined in step S15 whether or not the content includes an SP user. Specifically, it is determined whether or not the SP user ID is included in the participating user IDs shown in FIG. 6(a).

[0134] If it is not determined in step S15 that the SP user is included, it is determined in step S18 whether or not the comment (received comment) identified from the comment posting information includes the default NG common to all users shown in FIG. 7(a). If it is not determined in step S18 that the default NG common to all users is included, the received comment is added to and updated in the comment history of the content in step S19. In step S20, comment information for identifying the received comment is distributed to the user terminals of the participating users (excluding the user terminal of the comment posting source). This makes it possible to reflect the posted comment in the virtual space. As described above, in the user terminal of the comment posting source, the comment is reflected in the virtual space displayed on the user terminal of the user at the time the comment is entered.

[0135] Returning to step S18, when it is determined that the comment contains a default NG common to all users, the comment in which the message portion corresponding to the default NG is converted to obscured characters (for example, by replacing one character with "*") in step S21 is added and updated to the comment history of the content. In step S22, comment information for identifying the comment in which the default NG portion is converted to obscured characters among the received comments is distributed to the user terminals of the participating users (excluding the user terminal of the comment poster). This makes it possible to reflect the comment in which the default NG portion of the comment posted in the virtual space is converted to obscured characters. In the content of the first aspect, since the main or subject user is not specified, it is highly likely that the comment will become a conversation (interaction) between the participating users, so the default NG portion is obscured so that the rest can be confirmed. This makes it possible to prevent the occurrence of a problem in which a conversation does not take place and a sense of incongruity occurs if the entire comment including the default NG is not reflected. Note that, as described above, even if the comment contains an NG in the user terminal of the comment poster, the comment including the default NG is reflected in the virtual space displayed on the user terminal of the user at the time the comment is entered.

[0136] In step S23, notification information is sent to the user terminal of the user who posted the comment to notify that the comment contained a default NG common to all users. As a result, a message such as "The posted comment contained a default NG common to all users, so some of it was not reflected" is displayed on the user terminal of the user who posted the comment. As a result, the user who posted the comment can know that the posted comment contained a default NG common to all users.

[0137] Returning to step S15, if it is determined that the content includes an SP user, in step S16, it is determined whether or not the comment posting user is a user who satisfies the prohibition conditions for the type of the SP user (SP user participating in the same content) based on the NG related information in Fig. 7(c). If it is determined in step S16 that the comment posting user is a user who satisfies the prohibition conditions for the type of the SP user, the comment control process is terminated. This prohibits comment posting from users who satisfy the prohibition conditions for the type of SP users participating in the same content.

[0138] On the other hand, if it is not determined in step S16 that the user posting the comment is a user who satisfies the prohibition conditions for the SP user type, then in step S17 it is determined whether the received comment includes a default NG for the SP user type shown in Figure 7(b) or an individual NG for the SP user shown in Figure 7(c).

[0139] When it is not determined in step S17 that the received comment contains neither the default NG for the SP user type nor the individual NG for the SP user, the process proceeds to step S18. Note that, when it is not determined in the above-mentioned step S15 that the SP user is included, step S17 etc. are not executed, and even if the comment contains an NG word set for any non-participating SP user, the comment containing the NG word is reflected in the virtual space.

[0140] On the other hand, when it is determined in step S17 that the received comment contains the default NG for the SP user type or the individual NG for the SP user, the NG-related information of the comment posting user is updated in step S24. This makes it possible to identify the NG word contained in the comment and the SP user who set the NG word as a NG word that restricts the NG word (including the case of setting NG for a type) as a NG history from the NG-related information of the comment posting user.

[0141] Between step S16 and step S17, it may be determined whether or not the content includes multiple SP users. In this case, when it is not determined that the content includes multiple SP users, the process proceeds to step S17. When it is determined that the content includes multiple SP users, the process proceeds to step S17. When it is determined that the content includes multiple SP users, the process proceeds to step S18 to determine whether or not the received comment includes a type NG for each of the multiple SP users. When the type NG is not included, the process proceeds to step S18. When the type NG is included, the reflection is restricted and the process proceeds to step S24. This can prevent the number of reflected comments from becoming too small when multiple SP users are included. In addition, when the types of the multiple SP users included in the content are different, it may be determined whether or not a common type NG is included among the default NGs of each type, or it may be determined whether or not one of the type NGs is included among the default NGs of each type.

[0142] In step S25, it is determined whether or not the prohibition condition for the SP user is satisfied based on the NG-related information of the comment posting user. For example, it is determined whether or not the number of times that NG words have been posted for the SP user has reached a predetermined number. If it is determined in step S25 that the prohibition condition is not satisfied, the comment control process is terminated. On the other hand, if it is determined in step S25 that the prohibition condition is satisfied, the prohibited condition information is updated in step S26 to specify the type of SP user that satisfies the prohibition condition. As a result, in the virtual space of the content that is related to the SP user of the same type as the type specified from the prohibited condition information, the comment posting from the comment posting user is prohibited even if the SP user has not posted the NG word set by the SP user.

[0143] FIG. 9 is a diagram for explaining a display example of a user terminal during content distribution of the first aspect. FIG. 9 shows a display example of a user terminal participating in a community content among the content of the first aspect. FIGS. 9(a) to (b2) show a situation in which the SP user is not included in the users participating in the community content. As shown in FIG. 9(a), the user terminal of the user participating in the community content displays a field in which the user characters of the users participating in the community content can freely move and emote from the center area to the right area of ​​the screen, and a predetermined number of comments most recently posted to the community content are displayed in the left area of ​​the screen. Note that the comment history may be such that, in addition to displaying the most recent predetermined number of comments, comments posted before the predetermined number of comments can also be displayed retroactively in response to an operation.

[0144] In FIG. 9(a), user characters A to E corresponding to users A to E are displayed on the field, and comments are posted in the order of users B, D, E, and A from the comment history, and a comment such as "I'll try it next time!" is posted by user C. When a comment is posted, the comment content is displayed next to the user name in a speech bubble object from user character C in FIG. 9(a), and the comment content is also displayed next to the user name in the comment history. This allows users to easily see the most recently posted comment.

[0145] FIG. 9(b1) shows an example of a display on the user terminal E of user E when user E posts a comment such as "Celebrity Y came the other day!" following the comment posted by user C, and FIG. 9(b2) shows an example of a display on a user terminal of a user other than the user E who posted the comment. As described above, on the user terminal E of the user E who posted the comment, the posted comment is reflected in the virtual space regardless of whether or not the comment contains NG words. On the other hand, on the user terminals of users other than the user who posted the comment, the posted comment is reflected in the virtual space by receiving the comment information transmitted in step S20 or S22 in FIG. 8.

[0146] 9(b1) and (b2) show a situation where the participating users do not include an SP user, and even if a comment including an NG word set by any SP user is posted, the posted comment is reflected in the virtual space. Therefore, as shown in FIG. 9(b1) and FIG. 9(b2), a comment from user E is reflected in the virtual space not only in user terminal E but also in user terminals other than user terminal E.

[0147] On the other hand, as described above, in the first mode of content, users including celebrities and famous people can participate in the content they want at any time, so even if a celebrity is not participating at the start of distribution, he or she may join in midway. Figure 9(c) shows an example of a situation where the comment posting situation is the same as Figure 9(a), but the users participating in the community content include SP users.

[0148] In FIG. 9(c), in addition to user characters A to E corresponding to users A to E, user character X corresponding to SP user X corresponding to the SP user is displayed on the field, comments are posted in the order of users B, D, E, and A from the comment history, and a comment such as "I'll go there next time!" is posted by user C. As shown in FIG. 9(c), the user character of SP user X is displayed, and when a comment is posted, the user name of SP user X is displayed. Therefore, other users participating in the content can understand that the SP user is participating, and the possibility of posting a comment related to the SP user increases. Note that the user name of the user character may be always displayed near the user character (for example, above the head) in correspondence with the user character, and in addition to this, a unique icon according to the type of SP user may be displayed at the beginning of the line of the user name displayed in correspondence with the user character. Note that "I'll go there next time!" from user C does not include the NG word set by SP user X or the NG word common to all types of SP user X. Therefore, the comment from user C is reflected in the virtual space of the content.

[0149] Following the comment posted by user C shown in Fig. 9(c), when user E posts a comment such as "Talent Y came the other day!", a display example on user terminal E of user E is shown in Fig. 9(d1), and a display example on a user terminal of a user other than user E who posted the comment (including SP user X) is shown in Fig. 9(d2). Note that SP user X is, for example, a celebrity, and does not want the names of other celebrities who are rivals to be posted, so it is assumed that the SP user X has set the names of several celebrities as NG words, and that "Talent Y" is included in those NG words.

[0150] Even in this case, as described above, the posted comment is reflected in the virtual space on the user terminal E that posted the comment, regardless of whether the comment contains an NG word when posted. Therefore, as shown in Fig. 9(d1), even if the participating users include SP user X and a comment containing an NG word set by SP user X is posted, the posted comment is reflected as is on the user terminal E.

[0151] On the other hand, in the user terminals other than the user who posted the comment, the posted comment is reflected in the virtual space by receiving the comment information transmitted in step S20 or S22 in Fig. 8. However, since the comment posted by user E includes the NG word set by SP user X, it is determined as YES in step S17 in Fig. 8 and the comment information is not transmitted in step S20 or S22 in Fig. 8. For this reason, in Fig. 9(d2) showing a display example in a user terminal other than user terminal E, the comment from user E shown in Fig. 9(b2) is not displayed or reflected at all in the virtual space of the content.

[0152] <Specific examples of comment control in the second and third aspects of the content> Next, the comment control during the content distribution of the second or third aspect will be described in more detail. The content of the second and third aspects is related to a specific talent or famous person, and is the content in which the specific talent always participates or the specific talent always talks about. However, even during the content distribution period (for example, the period during which general users participate in the content), there may be a period in which the related SP user, such as the user character of the specific talent who is the main character or subject of the content, does not actually appear (is not displayed) in the virtual space, and in the case of a social gathering between fans, it may not appear from start to finish. During such a period, if the NG words set by the related SP user are reflected in the virtual space, there is a risk that further NG words will be encouraged among the participating users, which is not a desirable situation for the related SP user. For this reason, in this embodiment, during the distribution of the content of the second and third aspects, comment control is performed to restrict the reflection of the NG words set for the related SP user, regardless of whether the related SP user who is related to the content is actually included in the participating users of the content.

[0153] 10 is a diagram for explaining a flowchart of the comment control process during content distribution in the second mode. The comment control process during content distribution in the second mode is a process executed for each content, and is repeatedly executed at predetermined time intervals by the control unit 130 of the distribution server 100. The distribution server 100 performs various processes including the comment control process during content distribution in the second mode based on a program stored in the storage unit 120.

[0154] First, in step S30, it is determined whether or not participation information has been received from the user terminal. If it is determined that the participation information has not been received, the process proceeds to step S34. On the other hand, if it is determined that the participation information has been received, it is determined in step S31 whether or not the new participating user is a related SP user (e.g., a distribution user, an SP user) who is the main or subject of the content being distributed and has relevance to the content. In step S31, it is determined whether or not the user ID is that of a related SP user stored for each content shown in FIG. 6(b).

[0155] When it is not determined in step S31 that the newly participating user is not a related SP user, in step S32, a user character corresponding to the newly participating user is placed at a first position (e.g., in the spectator seats, etc.) in the virtual space of the participated content, and comment history information for identifying the comment history (see FIG. 6(b)) of the participated content is output to the user terminal of the newly participating user. As a result, content data in which the user character of the newly participating user is placed in the virtual space is distributed, and the user character is reflected and can be displayed at the first position (e.g., in the spectator seats, in front of the podium, in the outfield, etc.) in the virtual space on the user terminal of the user participating in the content. In addition, the user terminal of the newly participating user can identify and display the comment history posted in the participated content by receiving the comment history information. The first position is determined to be a position according to the type of content of the second aspect. In addition, a user character corresponding to a user who is not a related SP user is displayed in a manner (e.g., size, color, etc.) according to the type of content of the second aspect, and may not be displayed depending on the type of content.

[0156] On the other hand, when it is determined in step S31 that the user is a related SP user, the user character corresponding to the related SP user who has participated in step S33 is placed at a second position (for example, on a stage or a podium) in the virtual space of the participated content, and comment history information for identifying the comment history of the participated content (see FIG. 6(b)) is output to the user terminal of the newly participated user, and the process proceeds to step S34. As a result, content data in which the user character of the newly participated related SP user is placed in the virtual space is distributed, and the user character of the related SP user who is the main character or subject is reflected and can be displayed at the second position in the virtual space on the user terminal of the user participating in the content. In addition, the user terminal of the newly participated related SP user (in this case, the distribution user terminal 400) can identify and display the comment history posted in the participated content by receiving the comment history information. The second position is determined to be a position according to the type of the content of the second aspect. In addition, the user character corresponding to the related SP user is displayed in a manner (for example, size, color, etc.) according to the type of the content of the second aspect.

[0157] In step S34, it is determined whether or not a comment has been posted on the content from any of the participating users, that is, whether or not comment posting information has been received. If it is determined that the comment posting information has not been received, the comment control process is terminated. On the other hand, if it is determined that the comment posting information has been received, in step S35, it is determined whether or not the comment posting user is a user who satisfies the prohibition condition for the type of related SP user related to the content, based on the NG related information in FIG. 7(c). If it is determined in step S35 that the comment posting user is a user who satisfies the prohibition condition for the type of related SP user, the comment control process is terminated. On the other hand, if it is determined in step S35 that the comment posting user is not a user who satisfies the prohibition condition for the type of related SP user, in step S36, it is determined whether or not multiple related SP users related to the content are defined. In step S36, it is determined not whether or not the related SP user is participating, but whether or not multiple related SP users are defined to be related to the content.

[0158] If it is not determined in step S36 that multiple related SP users have been defined, it is determined in step S37 whether the received comment includes a default NG for the type of related SP user shown in Fig. 7(b) or an individual NG for the related SP user shown in Fig. 7(c). In step S37, it is determined whether the comment includes an NG set for the related SP user, regardless of whether the related SP user is participating.

[0159] When it is not determined in step S37 that the comment identified from the comment posting information includes neither the default NG for the type of the related SP user nor the individual NG for the related SP user, it is determined in step S38 whether the comment identified from the comment posting information (received comment) includes the default NG common to all users shown in FIG. 7(a). When it is not determined in step S38 that the default NG common to all users is included, the received comment is added to and updated in the comment history of the content. In step S40, comment information for identifying the received comment is distributed to the user terminals of the participating users (excluding the user terminal of the comment posting source). This allows the posted comment to be reflected in the virtual space. As described above, in the user terminal of the comment posting source, the comment is reflected in the virtual space of the content displayed on the user terminal of the comment posting source at the time the comment is entered.

[0160] On the other hand, when it is determined in step S38 that the content includes a default NG common to all users, the comment control process is terminated. This is because the related SP user who is the main character or subject of the second aspect content is determined, and the topic of the comment is unlikely to be a topic for the related SP user or a topic about the related SP user, which is unlikely to become a conversation (interaction) between participating users, and in this case, even if the comment including the default NG is not reflected, there is a high possibility that it will not cause discomfort. This reduces the processing load. Note that, depending on the type of content of the second aspect, for example, when it is determined in step S38 that the content includes a default NG common to all users, the same process as steps S21 to S23 in FIG. 8 may be performed to reflect the comment with the message part corresponding to the default NG converted to obscured characters, and to notify the posting user, etc.

[0161] Returning to step S37, when it is determined that the comment identified from the comment posting information contains the default NG of the related SP user's type or the individual NG of the related SP user, the NG-related information of the comment posting user is updated in step S44, regardless of whether the related SP user actually participates in the content (even if he / she does not participate). This makes it possible to identify, from the NG-related information of the comment posting user, the NG words contained in the comment and the related SP users who set the NG words as NG words that restrict those NG words (including the case of setting NG by type) as NG history.

[0162] Depending on the type of content of the second aspect, for example, when it is determined in step S37 that the comment identified from the comment posting information includes the default NG for the type of related SP user or the individual NG for the related SP user, the restriction control may be varied depending on whether or not the related SP user actually participates in the content. For example, when the related SP user does not actually participate in the content, the same process as steps S21 to S22 in Fig. 8 may be performed to reflect the comment in which the message portion corresponding to the NG word is converted to obscured characters, and then the process may proceed to step S44, whereas when the related SP user actually participates in the content, the comment itself may not be reflected and the process may proceed to step S44. This allows the degree of restriction or limitation to be varied depending on whether or not the related SP user actually participates.

[0163] In step S45, it is determined whether or not the prohibition condition for the related SP user is satisfied based on the NG related information of the comment posting user. For example, it is determined whether or not the number of times that NG words have been posted to the related SP user has reached a predetermined number. If it is determined in step S45 that the prohibition condition is not satisfied, the comment control process is terminated. On the other hand, if it is determined in step S45 that the prohibition condition is satisfied, the prohibited condition information is updated in step S46 to specify the type of the related SP user that satisfies the prohibition condition. As a result, in the virtual space of the content related to the type of SP user specified from the prohibited condition information, the comment posting user is prohibited from posting a comment.

[0164] Returning to step S36, when it is determined that a plurality of related SP users are defined, in step S43, it is determined whether or not the comment identified from the comment posting information includes the default NG of the type of the related SP user shown in FIG. 7(b). When a plurality of related SP users are defined, the individual NG of the related SP user shown in FIG. 7(c) is excluded from the restriction target in the determination, for example, in consideration of the possibility that even if a word is an NG word for one related SP user, the other related SP user may want it reflected in order to liven up the atmosphere in the content, or the number of individual NGs increases, and the number of comments reflected in the virtual space may be too small if strict restriction is applied. When the types of the plurality of related SP users are different, in step S43, it is determined whether or not any of the default NGs of each type is included. Note that, without being limited to this, in step S43, when the types of the plurality of related SP users are different, it may be determined whether or not a common default NG is included among the default NGs of each type, or it may be determined whether or not a default NG of either type is included among the default NGs of each type.

[0165] If it is not determined in step S43 that the comment identified from the comment posting information includes a default NG for the related SP user type, the process proceeds to step S38, and if it is determined that a default NG for the related SP user type is included, the process proceeds to step S44. Note that step S43 is not limited to this as long as it performs regulation control different from that when there is only one related SP user in order to prevent the number of NGs from becoming too large, and may, for example, exclude the NG for the related SP user type shown in Fig. 7(b) from the regulation targets and determine whether or not individual NGs set for each of multiple related SP users are included.

[0166] Fig. 11 is a diagram for explaining a display example of a user terminal during content distribution in the second mode. Fig. 11 shows a display example of a user terminal participating in program content of a talent X among the contents in the second mode. The program content is composed of, for example, a first part in which fans of the talent X gather and exchange information about the talent X before the talent X appears, and a second part in which the talent X appears at a certain timing (such as a timing determined in advance by the administrator or a timing of the talent X's choice) to further liven up the atmosphere. The talent X is a user who is determined to be related to the program content.

[0167] 11(a) to (b2) show display examples during the first part in which celebrity X does not appear. On the user terminal of a user participating in the program content, as shown in FIG. 11(a), a podium object on which celebrity X stands when he appears is displayed from the center region to the right region of the screen, and a predetermined number of comments most recently posted to the program content are displayed in the left region of the screen. Note that, although FIG. 11(a) shows an example in which the user character of the participating user is not displayed in the virtual space, the user character may be displayed in the virtual space depending on the type of content.

[0168] FIG. 11(a) shows that comments are posted in the order of users B, D, E, and A from the comment history, and user C posts a comment such as "I wonder if he'll appear soon?" When a comment is posted, the comment content is displayed in the comment history after the user's name. This allows users to easily see the most recently posted comment.

[0169] FIG. 11(b1) shows a display example on the user terminal F of user F when user F posts a comment such as "I threw away the item I got last time..." following the comment posted by user C, and FIG. 11(b2) shows a display example on a user terminal of a user other than user F who posted the comment. As described above, in user terminal F that posted the comment, the posted comment is reflected in the virtual space regardless of whether or not the comment contains NG words. On the other hand, in user terminals other than the user who posted the comment, the posted comment is reflected in the virtual space by receiving the comment information transmitted in step S40 of FIG. 10. However, it is assumed that talent X sets words that give a negative or negative impression as NG words, and that "throw away" and "throw away" are included in the NG words. In addition, regardless of whether talent X participates in the content (even if he has not yet participated), when a comment is posted, a determination such as step S37 in FIG. 10 is made. In addition, the comment posted by user F contains NG words set by talent X. Therefore, the determination in step S37 in Fig. 10 is YES, and the comment information is not transmitted in step S40 in Fig. 10. Therefore, the comment from user F is not displayed in user terminals other than user terminal F, as shown in Fig. 11(b2).

[0170] 11(c) to (d2) show display examples during the second part in which celebrity X appears. On the user terminal of a user participating in the program content, as shown in FIG. 11(c), a user character of celebrity X standing at a podium is displayed from the center to the right area of ​​the screen, and a history of several comments most recently posted to the program content is displayed in the left area of ​​the screen. FIG. 11(c) shows that comments are posted in the order of users B, D, E, and A from the comment history, and that user C posted a comment such as "Good, good job."

[0171] FIG. 11(d1) shows a display example on the user terminal F of user F when a comment such as "It looks boring..." is posted by user F following the comment posted by user C, and FIG. 11(d2) shows a display example on a user terminal of a user other than the user F who posted the comment. In the user terminal F that posted the comment, the posted comment is reflected in the virtual space regardless of whether or not the comment contains an NG word. On the other hand, in the user terminals of users other than the user who posted the comment, the posted comment is reflected in the virtual space by receiving the comment information transmitted in step S40 of FIG. 10. However, it is assumed that the talent X sets words that give a negative or negative impression as NG words, and that "boring" and "it looks boring" are included in the NG words. In addition, regardless of whether the talent X participates in the content, when a comment is posted, a judgment such as step S37 in FIG. 10 is made. In addition, the comment posted by the user F contains an NG word set by the talent X. For this reason, the comment from user F is not displayed on user terminals other than user terminal F, as shown in FIG. 11(d2).

[0172] 12 is a diagram for explaining a flowchart of the comment control process during content distribution of the third aspect. The comment control process during content distribution of the third aspect is a process executed for each piece of content, and is repeatedly executed at predetermined time intervals by the control unit 130 of the distribution server 100. The distribution server 100 performs various processes including the comment control process during content distribution of the third aspect based on a program stored in the storage unit 120.

[0173] First, in step S50, it is determined whether or not participation information has been received from the user terminal. If it is determined that the participation information has not been received, the process proceeds to step S56. On the other hand, if it is determined that the participation information has been received, it is determined in step S51 whether or not the new participating user is a related SP user (e.g., a distribution user, an SP user) who is the main or subject of the content being distributed and has relevance to the content. In step S51, it is determined whether or not the user ID is that of a related SP user stored for each content shown in FIG. 6(c).

[0174] If it is not determined in step S51 that the user is a related SP user, in step S32, a room to which the user is to enter among a plurality of rooms corresponding to the content is set and stored (see FIG. 6(c)), and a user character corresponding to the user is placed at a first position (e.g., an audience seat, etc.) in the virtual space of the room, and comment history information for identifying the comment history of the room (see FIG. 6(c)) is output to the user terminal of the newly participating user. As a result, content data in which the user character of the newly participating user is placed in the virtual space of the room is distributed, and the user character is reflected and can be displayed at the first position in the virtual space of the same room on the user terminal of the user who has entered (participated in) the room of the content. In addition, the user terminal of the newly participating user can identify and display the comment history posted in the content in which the user has participated by receiving the comment history information. The first position is determined to be a position according to the type of content of the third aspect. Furthermore, a user character corresponding to a user who is not a related SP user is displayed in a manner (eg, size, color, etc.) according to the type of content of the third manner, and may not be displayed depending on the type of content.

[0175] On the other hand, when it is determined in step S51 that the user is a related SP user, it is determined in step S53 whether or not the user should enter the selected room (i.e., whether or not the user should make a final selection). In the content of the third aspect, an example is shown in which the related SP user can select the room to enter, but more specifically, the user provisionally selects one of the rooms, checks the state of the room including the comment history, and then makes a final selection to enter the room.

[0176] If it is not determined in step S53 that the selection is final, the selection is provisional for checking the state of the room, etc., so in step S55, comment history information for identifying the comment history (see FIG. 6(c)) of the provisionally selected room is output to the user terminal of the associated SP user, and the process proceeds to step S56. As a result, the user terminal of the provisionally selected associated SP user (in this case, the broadcast user terminal 400) can identify and display the comment history posted in the provisionally selected room by receiving the comment history information. Also, in the state where the provisionally selected room is being checked, the user character of the associated SP user is not displayed in the room. Therefore, the associated SP user can check the state of each of the multiple rooms by provisionally selecting the room without displaying the user character of the associated SP user. The room to be provisionally selected first may be selected by the associated SP user, or may be selected by the distribution server 100. When selected by the distribution server 100, the room with the largest number of users present may be selected, or may be selected randomly from rooms with a predetermined number (e.g., 20) or more of users present. This makes it easier to understand the degree of interaction and excitement in the provisionally selected room from the status of comment posting, etc. After provisionally selecting a room and checking the room, the related SP user may provisionally select another room and change the room to be checked.

[0177] When it is determined in step S53 that the selection is definite, the user character corresponding to the definite selected related SP user is placed in a second position (e.g., on a stage or a podium) in the virtual space of the specified room in step S54, and the process proceeds to step S56. As a result, by distributing the content data in which the user character of the related SP user who has newly joined is placed in the virtual space of the specified room, the user character of the main or subject related SP user is reflected and can be displayed in the second position in the virtual space of each room on the user terminal of the user who has entered the specified room.

[0178] By the related SP user finally selecting the provisionally selected room, the user character of the related SP user is displayed in the predetermined room as described above. The predetermined room in which the user character of the related SP user is displayed is determined according to the type of content. For example, in the case of live content, all of the multiple rooms corresponding to the live content are determined as the predetermined room, and the user character of the related SP user is mirrored in each of the multiple rooms and reflected in each room. In addition, in the case of fan meeting content, for example, the room finally selected by a specific talent is determined as the predetermined room, and the user character of the related SP user is reflected only in the room. In addition, even after the final selection, the final selection may be cancelled and another room may be provisionally selected to make the final selection (change the selected room). After the final selection, the final selection may be cancelled, and during the period from the provisional selection to the final selection, in the case of live content, the display of the user character of the related SP user may be maintained, and in the case of fan meeting content, for example, the user character of the related SP user may be hidden by canceling the final selection, and then reflected in the finally selected room.

[0179] The comment history of the selected room has already been displayed on the user terminal of the related SP user in step S55. The second position is determined to be a position according to the type of the content of the third aspect. The user character corresponding to the related SP user is displayed in a manner (e.g., size, color, etc.) according to the type of the content of the third aspect. The configuration shown in steps S53 to S55 of FIG. 12 may be such that the related SP user tentatively selects the content after the content starts, checks the state including the comment history in the virtual space of the content, and then makes the content appear in the virtual space by making a final selection, and is not executed (cannot be selected again). The configuration shown in steps S53 to S55 of FIG. 12 may be applied to the content of the second aspect described above. In the content of the second aspect, for example, the related SP user tentatively selects the content, checks the state including the comment history in the virtual space of the content, and then makes the content appear in the virtual space by making a final selection.

[0180] In step S56, it is determined whether a comment has been posted in any room, i.e., whether comment posting information has been received, regardless of whether the room is one selected and entered by a related SP user. If it is determined that the comment posting information has not been received, the comment control process is terminated. On the other hand, if it is determined that the comment posting information has been received, in step S57, it is determined whether the comment posting user is a user who satisfies the prohibition condition for the type of related SP user related to the content, based on the NG related information in FIG. 7(c). If it is determined in step S57 that the comment posting user is a user who satisfies the prohibition condition for the type of related SP user, the comment control process is terminated. On the other hand, if it is determined in step S57 that the comment posting user is not a user who satisfies the prohibition condition for the type of related SP user, in step S58, it is determined whether multiple related SP users related to the content are defined.

[0181] If it is not determined in step S58 that multiple related SP users have been defined, it is determined in step S59 whether the received comment includes a default NG for the type of related SP user shown in Figure 7(b) or an individual NG for the related SP user shown in Figure 7(c).

[0182] When it is not determined in step S59 that the comment identified from the comment posting information includes neither the default NG for the type of the related SP user nor the individual NG for the related SP user, it is determined in step S60 whether the received comment includes the default NG common to all users shown in FIG. 7(a). When it is not determined in step S60 that the default NG common to all users is included, the received comment is added to and updated in the comment history of the room in which the comment posting user enters in step S61. In step S62, comment information for identifying the received comment is distributed to the user terminals (excluding the user terminal of the comment posting user) of users participating in the same room (the room in which the comment posting user enters). This allows the posted comment to be reflected in the virtual space of the same room as the comment posting user. As described above, in the user terminal of the comment posting user, the comment is reflected in the virtual space of the room displayed on the user terminal of the comment posting user at the time the comment is entered.

[0183] On the other hand, when it is determined in step S60 that the comment contains a default NG common to all users, the comment control process is terminated. This is for the same reason as explained in step S38 of Fig. 10. Depending on the type of content in the third mode, for example, when it is determined in step S60 that the comment contains a default NG common to all users, the same process as steps S21 to S23 of Fig. 8 may be performed to reflect the comment with the message portion corresponding to the default NG converted to obscured characters, and to notify the posting user of the comment.

[0184] Returning to step S59, when it is determined that the received comment contains the default NG for the related SP user type or an individual NG for the related SP user, the NG-related information of the comment posting user is updated in step S66, regardless of whether the related SP user is actually participating in the content, and regardless of whether the comment is posted by a user who is in the same room as the related SP user even if the related SP user is participating. This makes it possible to identify, from the NG-related information of the comment posting user, the NG words contained in the comment and the related SP users who set the NG words as NG words that restrict those NG words (including when they are set as NG by type) as NG history.

[0185] Depending on the type of content of the third aspect, for example, when it is determined in step S59 that the comment identified from the comment posting information includes the default NG for the type of related SP user or the individual NG for the related SP user, the restriction control may be varied depending on whether or not the related SP user actually participates in the content. For example, when the related SP user does not actually participate in the content, the same process as steps S21 to S22 in Fig. 8 may be performed to reflect the comment in which the message portion corresponding to the NG word is converted to obscured characters, and then the process may proceed to step S66, whereas when the related SP user actually participates in the content, the comment itself may not be reflected and the process may proceed to step S66. This allows the degree of restriction or limitation to be varied depending on whether or not the related SP user actually participates.

[0186] In step S67, it is determined whether or not the prohibition condition for the related SP user is satisfied based on the NG related information of the comment posting user. If it is determined in step S67 that the prohibition condition is not satisfied, the comment control process is terminated. On the other hand, if it is determined in step S67 that the prohibition condition is satisfied, the prohibited condition information is updated in step S68 to specify the type of the related SP user that satisfies the prohibition condition. As a result, in the virtual space of the content related to the type of SP user specified from the prohibited condition information, the comment posting user is prohibited from posting a comment.

[0187] Returning to step S58, if it is determined that multiple related SP users have been defined, then in step S65 it is determined whether or not the received comment includes the default NG for the related SP user type shown in Fig. 7(b). This is for the same reason as explained in step S43 of Fig. 10. If it is not determined in step S65 that the received comment includes the default NG for the related SP user type, then the process proceeds to step S60, and if it is determined that the received comment includes the default NG for the related SP user type, then the process proceeds to step S66.

[0188] Fig. 13 is a diagram for explaining a display example of a user terminal during content distribution in the third mode. Fig. 13 shows a display example of the user terminals of multiple users participating in live content of a talent X among the content in the third mode. In the live content, for example, as shown in Fig. 13(a1), a user character of the talent X who is the main character is placed in the central region of the screen, and a predetermined number of comment histories posted most recently to the room in which the user of the user terminal is currently present are displayed in the left region of the screen. In the live content, the user character of the talent X and the like are mirrored and reflected in all of the multiple rooms corresponding to the content.

[0189] Fig. 13(a1) shows an example of a display on a user terminal of a user A1 who has entered the same room as the room selected by the talent X, and Fig. 13(a2) shows an example of a display on a user terminal of a user G1 who has entered the same room as the room selected by the talent X. It is assumed that users A1 to Z1 have entered the room selected by the talent X, and the comment history shown in Fig. 13(a1) shows that comments were posted in the order of users A1, B1, C1, D1, and E1.

[0190] On the other hand, Fig. 13(a3) and Fig. 13(a4) show examples of displays on user terminals of users who have entered a room different from the room selected by the talent X. As shown in Fig. 13(a3), it is assumed that users A2 to Z2 have entered Room 1, which is different from the room selected by the talent X, and the comment history shows that comments have been posted in the order of users A2, B2, C2, D2, and E2. Also, as shown in Fig. 13(a4), it is assumed that users A3 to Z3 have entered Room 2, which is different from the room selected by the talent X, and the comment history shows that comments have been posted in the order of users A3, B3, C3, D3, and E3.

[0191] In such a situation, as shown in FIG. 13(a2), a case will be described in which a comment containing an NG word set by the talent X is posted from a user G1 who is in the same room as the room selected by the talent X. As described above, in the user terminal of the user G1 who posted the comment, the posted comment is reflected in the virtual space regardless of whether or not the comment contains an NG word when posted. On the other hand, in the user terminals of users (including the talent X) who are in the same room as the user who posted the comment, the posted comment is reflected in the virtual space by receiving the comment information transmitted in step S62 of FIG. 12. However, since the comment posted by the user G1 contains the NG word set by the talent X, the determination is YES in step S59 of FIG. 12, and the comment information is not transmitted in step S62 of FIG. 12. For this reason, even in the user terminals of users who are in the same room as the user G1, the comment from the user G1 is not displayed as shown in FIG. 13(a1). Furthermore, for user terminals of users who are in a room other than that of user G1, comments from user G1 will not be displayed, as shown in Figures 13(a3) and 13(a4), regardless of whether the comment posted by user G1 contains NG words.

[0192] Figures 13(b1) to 13(b4) explain a situation immediately before the comment from user G1 shown in Figure 13(a2) is posted, where user G2, who is in room 1 different from the room selected by talent X, posts a comment containing NG words set by talent X. As shown in Figure 13(b3), in the user terminal of user G2 who posted the comment, the posted comment is reflected in the virtual space regardless of whether the comment contains NG words or not.

[0193] On the user terminal of a user who enters the same room as the user who posted the comment but is not the one who posted the comment, by receiving the comment information transmitted in step S62 of FIG. 12, the posted comment will be reflected in the virtual space. However, since the comment posted by user G2 contains the NG words set by talent X, it is determined as YES in step S59 of FIG. 12 and the comment information is not transmitted in step S62 of FIG. 12. Therefore, even on the user terminals of users who have entered the same room as user G2, the comment from user G2 is not displayed as shown in FIG. 13(b4). Regarding the user terminals of users who have entered a room different from user G2, regardless of whether the comment posted by user G2 contains NG words, the comment from user G2 is not displayed as shown in FIGS. 13(b1) and 13(b2).

[0194] <Examples of Specific Configurations and Effects Regarding NG Word Regulations> (1-1) In the above-described embodiment, during the distribution of any content in the first aspect, when it is determined in step S15 of FIG. 8 that no SP user is participating in the virtual space of the content, even if the posted comment contains an NG word set for any SP user, the received comment is reflected in the virtual space in step S20 of FIG. 8. On the other hand, during the distribution of any content in the first aspect, when it is determined in step S15 of FIG. 8 that an SP user is participating in the virtual space of the content (including after changing from a situation where no SP user is participating to a situation where an SP user is participating), when the posted comment contains an NG word set for the participating SP user, it is determined as YES in step S17 of FIG. 8 and the reflection of the received comment in the virtual space is restricted. Thereby, it is possible to appropriately restrict the reflection of comments containing NG words set for the SP user according to whether the SP user is included in the virtual space of the content.

[0195] (1-2) In the above-mentioned embodiment, comments posted in content are added to and updated in the comment history in step S19 in Fig. 8, when a new user joins the content in step S12 in Fig. 8, comment history information is output to the user terminal of the new user to make the comment history displayable, and when an SP user who has not participated in the content newly joins, comments including NG words set for the SP user are deleted from the comment history in step S13 in Fig. 8, and the comment history information after deletion and update is output. This makes it possible to prevent a comment history including NG words from being reflected and displayed on the user terminal of the SP user when the new SP user joins.

[0196] (1-3) In the above-described embodiment, an example was shown in which the NG setting unit 253 sets a NG word candidate requested by an SP user participating in the virtual space of a certain content (including the SP user himself / herself distributing) as the NG word of the SP user without waiting for the setting from the administrator. Also, an example was shown in which the input information sending unit 356 applies for setting an NG word by dragging and inverting a message part to be a NG word candidate among comments reflected as a comment history in the virtual space of the content in which the SP user himself / herself participates. This reduces the effort required for setting NG words and improves the convenience of the SP user.

[0197] (2-1) In the above-described embodiment, when a comment including an NG word set for an SP user is posted from a plurality of users participating in the content of the first mode, who are not related to the SP user and do not satisfy the special condition for the SP user, if the SP user is not actually participating, the comment is reflected in the virtual space of the content in step S20 of Fig. 8. On the other hand, when a comment including an NG word set for the SP user is posted from a plurality of users participating in the content of the second mode and third mode, who are related to the SP user and satisfy the special condition for the SP user, the reflection of the comment including the NG word in the virtual space of the content is restricted by, for example, YES being determined in step S37 of Fig. 10, regardless of whether the SP user is actually participating. This makes it possible to appropriately restrict the reflection of the NG word set for the SP user depending on the type of content.

[0198] (2-2) In the above-mentioned embodiment, as examples of content that satisfies the special condition, content that the related SP user appears in and distributes independently, and content that the related SP user does not appear in but that the fans of the related SP user gather to communicate with each other are given. In either case, it is possible to prevent a situation in which NG words are reflected before the related SP user is included in the content, or in the case of content that is previously determined as related to the SP user, it is possible to prevent a situation in which NG words are reflected.

[0199] (2-3) In the above-described embodiment, for example, the content related to the SP user belonging to SP1 and the content related to the SP user belonging to SP2 include different words as NG words. This makes it possible to appropriately differentiate NG words according to the type of related SP user and the type of content.

[0200] (3-1) In the above-described embodiment, when it is determined that the answer is YES in step S37 in Fig. 10, the reflection of the received comment is restricted, and the NG-related information for each user is updated in step S44 in Fig. 10. Also, when it is determined that the comment posting user is a user who satisfies the prohibition condition for the type of related SP user based on the NG-related information in step S35 in Fig. 10, the reflection of the comment is restricted regardless of whether the comment contains an NG word or not, and whether the SP user who caused the prohibition condition to be satisfied is participating or not. In this way, the NG-related information updated for each user is utilized in content related to SP users belonging to the same type, and it is possible to restrict the reflection of comments from prohibited users who satisfy the prohibition condition according to the NG-related information.

[0201] (3-2) In the above-described embodiment, for example, in a situation where a prohibited user who satisfies the prohibition conditions for SP1 is included among users participating in content related to SP users belonging to SP2, when a comment is posted from the prohibited user, the comment from the prohibited user can be reflected if the prohibition conditions for SP2 are not satisfied. This prevents the NG-related information updated for each user from being utilized or used for content related to SP users belonging to different types, and prevents excessive restrictions on reflection.

[0202] (4-1) In the above-described embodiment, when a comment including an NG word set for an SP user is posted to content that satisfies a special condition for the SP user, the reflection of the comment is restricted, and the type NG preset for the type of SP user includes different words for an SP user belonging to the type SP1 and an SP user belonging to the type SP2, for example. This makes it possible to appropriately restrict words according to the type of SP user without the trouble of setting NG words.

[0203] (4-2) In the above-described embodiment, for example, in a situation where SP users belonging to the SP1 type and SP users belonging to the SP2 type are defined as related SP users having relevance to the content, reflection is restricted based on the NG type, unlike the individual NG words set individually by each of the multiple SP users, as illustrated in step S43 of Fig. 10. In this way, the process (restriction control) for restricting reflection can be made different depending on whether multiple related SP users are included.

[0204] (5-1) In the above-mentioned embodiment, in the third aspect of the content in which multiple rooms (multiple virtual spaces) are prepared to provide one piece of content, when a comment containing a NG word is posted in any of the rooms, the reflection of the comment is restricted regardless of whether the comment was posted in a room selected by the SP user related to the content. This makes it possible to appropriately restrict the reflection of comments containing NG words even in the third aspect of the content.

[0205] (5-2) In the case of live content in the above-mentioned embodiment, an example was shown in which a user character corresponding to a related SP user is displayed in all of the multiple rooms corresponding to the live content, regardless of whether the room is selected by the related SP user. This allows users entering any of the rooms to recognize and confirm the user character corresponding to the related SP user, creating a sense of unity in all the rooms.

[0206] (5-3) In the case of the fan meeting content in the above-mentioned embodiment, an example was shown in which a user character corresponding to a related SP user is displayed in a room selected by the related SP user. This can increase the sense of expectation and premium feeling for the user character corresponding to the related SP user to be displayed.

[0207] (5-4) In the above-described embodiment, as shown in step S55 of Fig. 12, the related SP user can check the state of the provisionally selected room, including the comment history. Also, as shown in step S54 of Fig. 12, the user character corresponding to the related SP user is not displayed until the related SP user makes a definite selection. This allows the user character to understand the state of the room without being recognized by the user who has entered the room, and can use this as a reference for deciding whether or not to make a definite selection and enter the room.

[0208] (5-5) In the above-described embodiment, when distribution server 100 selects the room to be provisionally selected first, it may select the room with the largest number of users who are currently in the room, or may randomly select the room from among rooms with a predetermined number of users (e.g., 20) or more. This makes it easier to grasp the degree of interaction and excitement in the provisionally selected room from the status of comment postings, etc.

[0209] (5-6) In the above embodiment, an example was shown in which a certain room is provisionally selected, and after checking the inside of the room, another room is provisionally selected to change the room to be checked, or even after a certain room is finally selected, the final selection can be cancelled and another room is provisionally selected to make a final selection (change the selected room). This allows the rooms to be checked to be changed one after another, improving the convenience of related SP users.

[0210] (6) In the above embodiment, the users having a specific relationship are exemplified as participating users (users who participate in a group of a certain content) associated with a common content (group). This makes it possible to restrict the reflection of NG words between users associated with the common content.

[0211] (7) In the above-mentioned embodiment, during the content distribution of the first mode, when a received comment includes a default NG common to all users, the default NG in the comment is obscured in step S22 of Fig. 8 to reflect anything other than the default NG, and when the received comment includes an NG word set for an SP user participating in the comment, the result of the determination in step S17 of Fig. 8 is YES, and the reflection of the comment itself including the NG word is restricted. In this way, by restricting the reflection of the predetermined default NG common to all users to a minimum extent, it is possible to prevent the occurrence of inconveniences such as restricting the reflection of comments themselves including words that are not set as restricted by the SP user, which makes it impossible to hold a conversation.

[0212] (8) In the above-described embodiment, during the second and third aspects of content distribution, when it is determined in step S37 of FIG. 10 that a comment identified from the comment posting information contains a default NG for the type of related SP user or an individual NG for the related SP user, and when the related SP user is not actually participating in the content, a process similar to steps S21 to S22 of FIG. 8 is performed to reflect the comment in which the message portion corresponding to the NG word is converted to obscured characters, and then the process proceeds to step S44. Also, when it is determined in step S37 of FIG. 10 that a comment identified from the comment posting information contains a default NG for the type of related SP user or an individual NG for the related SP user, and when the related SP user is actually participating in the content, the process proceeds to step S44 without reflecting the comment itself. This allows the degree of restriction to be varied depending on whether the related SP user is actually participating during the second and third aspects of content distribution.

[0213] (9) In the above-described embodiment, an application for setting a new NG word is made in response to an operation from an SP user, and if the application is approved by the administrator, the candidate is set as an individual NG word for the SP user by the NG setting unit 253. This prevents a proliferation of NG words, since words approved by the administrator are set as NG words.

[0214] (10) In the above-described embodiment, as shown in Fig. 8 and the like, the NG words include a default NG common to all users that notifies a user who posted a comment containing the word that its reflection has been restricted when its reflection has been restricted, and an individual NG that does not notify the user that its reflection has been restricted, and in step S23 of Fig. 8, a process is performed to notify a user who posted a comment containing the default NG common to all users that its reflection has been restricted because it is NG. This makes it possible to prevent the default NG common to all users from being posted repeatedly.

[0215] (11) In the above-described embodiment, the user terminal of the user who posted the comment reflects the comment regardless of whether the comment contains NG words and outputs the comment posting information (e.g., see FIG. 9(d1) etc.), and the distribution server 100 outputs comment information for comments that do not contain NG words and reflects them in the virtual space of the content, while restricting the reflection of comments that contain NG words by not outputting comment information (e.g., see FIG. 9(d2) etc.). This prevents the user who posted the comment from identifying whether the comment was actually reflected or not, and prevents the NG words from being identified and the comment from being posted in a way that circumvents the restrictions.

[0216] (12) In the above-described embodiment, a common default NG is preset for each type of SP user as shown in Fig. 7(b), and for example, between step S16 and step S17 in Fig. 8, it may be determined whether or not the content contains multiple SP users. In this case, when it is determined that the content does not contain multiple SP users, the process proceeds to step S17. When it is determined that the content contains multiple SP users, it is further determined whether or not the received comment contains a type NG for each of the multiple SP users. When a type NG is not included, the process proceeds to step S18. When a type NG is included, the reflection is restricted and the process proceeds to step S24. This can prevent the number of reflected comments from becoming too small when multiple SP users are included.

[0217] (13) In the above-described embodiment, when a related SP user is included among the participating users, the actions that the related SP user can take are different from the actions (e.g., posting a comment) that other users other than the related SP user (general users or other SP users) can take. For example, the related SP user cannot post a comment when he or she is actively distributing content, but can output the movement and sound of a corresponding user character in the virtual space, like an alter ego of the related SP user. This can create cases where the actions that the related SP user and other users can take are different, and each user can take an action appropriate to their position.

[0218] <About mute restrictions> In the explanation of Figs. 5 to 13, there is no user who is specified as a mute by any user and there is no user who is the target of the total mute control, and for example, in steps S20 and S22 of Fig. 8, step S40 of Fig. 10, and step S62 of Fig. 12 (hereinafter collectively referred to as the comment delivery step), comment information is delivered to the user terminal 300 of each user to reflect the posted comment. However, when a user is specified as a mute, as described above, in the user terminal 300 of the designated user who has specified the user who posted the comment as a mute target, the comment information is not delivered to the user terminal 300 of the designated user in the comment delivery step, for example, in order to prevent the posted comment from being reflected. Also, when the user who posted the comment satisfies the restriction conditions and is the target of the total mute control, basically, in order to prevent the posted comment from being reflected not only in the designated user who has specified the user as a mute target but also in the user terminal 300 of the user who has not specified the user as a mute target, the comment information is not delivered in the comment delivery step, for example. Below, technical matters related to muting will be explained.

[0219] FIG. 14 is a diagram for explaining an example of mute-related information stored in storage unit 120 of distribution server 100. FIG. 14 shows mute-related information stored for each user. Like NG information, mute-related information for each user is stored in association with user information including, for example, a user ID and a user name. A user name and a type of the user are stored in association with a user ID, and further, mute-received history information, mute specification history information, and total mute-related information are stored as mute-related information. Note that mute-related information may be stored together with NG information in association with user information including a user ID and a user name.

[0220] The mute history information is a history of the user being designated to be muted, and includes information for identifying the designated user who designated the user to be muted and the date and time of designation. The mute history information is updated based on mute designation information and mute cancellation information from the user. The mute history information includes a current reception history in which a user is designated to be muted at the current timing, and a past reception history in which a user was designated to be muted in the past but the mute designation was subsequently cancelled (history in which the user is not currently muted). Muting is determined based on the current reception history, and the past reception history is not referenced. The restriction conditions are also determined based on the current reception history. However, even if a user's mute designation is cancelled after it has been determined that the restriction conditions are met, and the current reception history becomes a history that does not meet the restriction conditions, this alone does not release all mute control, but the control is maintained thereafter.

[0221] The mute designation history information includes information for identifying other users designated by the user as muted, the date and time of designation, and the designation frequency indicating the frequency (frequency) of the user designating other users as muted. The mute designation history information is updated based on mute designation information and mute release information from the user. The mute designation history information includes a current designation history of users designated as muted at the current timing, and a past designation history of users designated as muted in the past but subsequently released (history of users not currently designated as muted). The designation frequency is, for example, a value calculated according to the time during which the user participates in any content during a predetermined period (e.g., one year) and the number of times other users have been designated as muted during that period, and is "1" when the number of designations is 0, and approaches a lower limit value (e.g., "0.1") as the number of designations increases. The designation frequency may be a value calculated based on the following formula, for example. Formula: Specified frequency = 0.1 + 0.9 x (1 - specified number / hour) Note that time is, for example, the total number of "minutes" spent participating in the content. If the value of (1 - number of designations / time (minutes)) is negative (e.g., if designation is made more than once per minute), it is calculated as "0."

[0222] When calculating the designation frequency based on such a formula, for example, a user with "0" designations will have a designation frequency of "1", and the more the designation number increases, the smaller the designation frequency will be, so that a user who designates more than once per minute will have a designation frequency of "0.1", which is the lower limit. Note that the designation frequency is calculated according to the number of designations based on the current designation history in a predetermined period (for example, one year), but it is not limited to this and may be calculated taking into account not only the number of designations based on the current designation history but also past designation history.

[0223] The full mute related information includes information for identifying the user, such as a full mute flag indicating that the user meets the regulating conditions and is subject to full mute control, a full mute history indicating the history of past full mute control for the user (the number of times the full mute control was released, the date it was released, etc.), and a full mute off flag indicating that comments from users who are subject to full mute control will be reflected without being regulated based on the full mute selection information from the user.

[0224] Fig. 15 is a diagram for explaining an example of the contents of the restrictive conditions among the mute-related information stored in the storage unit 120 of the distribution server 100. In Fig. 15, a first restrictive condition for determining whether a muting occurred in a first period is a target for each type of content, and a second restrictive condition for determining whether a muting occurred in a second period longer than the first period is a target for each type of content. The second period is set to be a period longer than twice the first period, and for example, the most recent 24 hours may be set as the first period and the most recent one week (24 hours x 7) as the second period, or the most recent one week may be set as the first period and the most recent one month (24 hours x 30) as the second period.

[0225] 15 shows A1, A2, B1, B2, C1, and C2 as the number of mutes that satisfy the restriction condition. For example, for a user participating in content of the first mode, the first restriction condition is satisfied when the number of mutes received during a first period reaches A1, and the second restriction condition is satisfied when the number of mutes received during a second period reaches A2. A2 is set to a value that is larger than A1 but smaller than twice A1, and for example, A1 may be set to "20" and A2 to "35."

[0226] Furthermore, for a user participating in the content of the second mode, the first restriction condition is determined to be satisfied when the number of mutes received during the first period reaches B1, and the second restriction condition is determined to be satisfied when the number of mutes received during the second period reaches B2. B2 is set to a value larger than B1 but smaller than twice the value of B1, and for example, B1 may be set to "50" and A2 to "90".

[0227] Furthermore, for a user participating in content of the third mode, the first restriction condition is determined to be satisfied when the number of mutes received during a first period reaches C1, and the second restriction condition is determined to be satisfied when the number of mutes received during a second period reaches C2. C2 is set to a value larger than C1 but smaller than twice C1, and for example, C1 may be set to "100" and C2 to "180".

[0228] Here, the number of mutes determined to satisfy the regulation conditions defined for each type of content is set such that the content of the second mode has a larger value than the content of the first mode, and the content of the third mode has a larger value than the content of the second mode. Specifically, it is defined such that the relationships are A1 < B1 < C1 and A2 < B2 < C2. This is because, for example, as described above, the content of the first mode is content that has no relevance to any SP user and aims to communicate with other participating users. In contrast, the content of the second and third modes is content that has relevance to any SP user and does not mainly aim to communicate with other participating users. For this reason, compared to the content of the second and third modes, the content of the first mode has a higher degree of attention to comments and a greater influence on comments from other users, so it is set to satisfy the regulation conditions with a smaller number of mutes. Also, when focusing on the content of the second mode and the content of the third mode, it is expected that the number of participants in the content of the third mode will be larger than that of the content of the second mode. Since the content of the second mode has a higher degree of attention to comments and a greater influence on comments from other users than the content of the third mode, it is set to satisfy the regulation conditions with a smaller number of mutes.

[0229] In addition, the number of mutes used to determine whether or not the regulatory condition is satisfied is calculated taking into account the designation frequency of each user. Whether or not a certain user satisfies the regulatory condition is determined, for example, by calculating the total value of the designation frequency (a value between 0.1 and 1 as described above) of all users who have designated the user as a mute target, and determining whether or not the total value reaches the number of mutes that satisfies the regulatory condition. Specifically, if there are 50 other users who have designated user A as a mute target, including 10 users with a designation frequency of 0.5 and 10 users with a designation frequency of 0.1, and the designation frequency of the other users is 1, the number of mutes for user A is 36 (=0.5×10+0.1×10+1×30), and when it is determined that this 36 reaches the number of mutes that satisfies the regulatory condition, user A is determined to satisfy the regulatory condition and is subject to full mute control.

[0230] Note that FIG. 15 shows an example in which a first restriction condition for judging the number of mutes in a first period and a second restriction condition for judging the number of mutes in a second period longer than the first period are defined for each type of content, but this is not limited to the above and restriction conditions may be set regardless of the type of content, and restriction conditions may be set for one period or for each of three or more periods.

[0231] In addition, while Figures 14 and 15 show examples of muting-related information and restrictive conditions for each user, this information can only be viewed and identified by the administrator by communicating with the distribution server 100 via the administrator terminal 200, and cannot be viewed or identified by any user via a user terminal.

[0232] 16 is a diagram for explaining a flowchart of a mute-related information update process for updating mute-related information. The mute-related information update process is repeatedly executed at predetermined time intervals by the control unit 130 of the distribution server 100. The distribution server 100 executes the mute-related information update process based on a program stored in the storage unit 120.

[0233] First, in step S80, it is determined whether mute specification information or mute undo information has been received from the user terminal. If it is determined that neither mute specification information nor mute undo information has been received, the process proceeds to step S83. On the other hand, if it is determined that mute specification information or mute undo information has been received, steps S81 and S82 are performed. In the user terminal, for example, an operation is performed by a user participating in the content to specify a comment history as a target for muting, or an operation is performed on a setting screen or the like to search and extract a user name to be muted and specify the user name as a target for muting, thereby transmitting mute specification information for identifying the user specified as a target for muting or information for identifying the specified user. In addition, in the user terminal, for example, an operation is performed to cancel the mute specification for a user participating in the content, or an operation is performed on a setting screen or the like to search and extract a user name to cancel the mute specification for the user name, thereby transmitting mute undo information for identifying the user whose mute specification has been canceled or the user who specified the cancellation.

[0234] When it is determined in step S80 that mute designation information has been received, in step S81, the mute history information of the user specified from the mute designation information and designated as a mute user is updated. That is, as the mute history information of the user specified as the mute target (the user who received the mute designation), the user who specified it (the designated user who specified the user as the mute target) and the designated date and time are stored as the current designation history. Note that, although an example in which the reflection of comments including NG words is restricted is described in FIG. 8 to FIG. 13, the mute history information is not updated by restricting the reflection of comments including NG words. Also, in step S82, the mute designation history information of the user specified from the mute designation information and designated as a mute user is updated. That is, as the mute designation history information of the user who specified the mute (the designated user who specified the mute), the user who is the mute target (the user who received the mute designation) and the designated date and time are stored as the current designation history.

[0235] On the other hand, when it is determined in step S80 that mute undo information has been received, in step S81, the mute history information of the user identified from the mute undo information who has been designated to be muted is updated. That is, the mute history information of the user who has been designated to be muted is updated to include the user who specified the mute and the date and time of the designation in the past designation history. In addition, in step S82, the mute history information of the user identified from the mute undo information who has requested the undo is updated. That is, the mute history information of the user who requested the undo is updated to include the user who specified the mute and the date and time of the designation in the past designation history.

[0236] In step S83, it is determined whether or not all mute selection information has been received. In the user terminal, for example, during participation in the content or on a setting screen, it is possible to select whether to reflect comments from a user who is the target of the all mute control without censoring or to restrict their reflection in response to an operation from the user, and all mute selection information for identifying the user and the selection result is transmitted. If it is determined that the all mute selection information has not been received, the process proceeds to step S85. On the other hand, if it is determined that the all mute selection information has been received, in step S84, the all mute off flag of the user who transmitted the information is updated based on the all mute selection information. For example, when all mute selection information indicating that the comments are to be reflected without censoring is received, the all mute off flag is set to on, whereas when all mute selection information indicating that the comments are to be restricted from being reflected is received, the all mute off flag is set to off. In the initial state, the all mute off flag is set to off.

[0237] In step S85, it is determined whether or not the all-mute cancellation application information has been received. In the user terminal, when it is felt that the user's own comments are not reflected from the reactions of other users and that the user may be subject to the all-mute control, for example, in response to the all-mute control cancellation operation from the user, the all-mute cancellation application information for canceling the all-mute control for the user is transmitted. When it is determined that the all-mute cancellation application information has not been received, the process proceeds to step S87. On the other hand, when it is determined that the all-mute cancellation application information has been received, if the all-mute flag is set to ON for the user who transmitted the all-mute cancellation application information in step S86, the cancellation application information is transmitted to the administrator terminal 200 to indicate that the user has requested cancellation, and to specify the mute history of the user in the most recent predetermined period (for example, one month), the total comment history received from the user, the total mute history, and the like. The total comment history received from the user refers not only to the history of comments posted in the content (including the room) in which the user participates, but also to the history of all comments posted by the user in various contents and the like in the most recent predetermined period (for example, one month). The overall comment history is also assumed to be managed by the log management unit 131 described above.

[0238] By receiving the cancellation request information, the administrator terminal 200 can notify (display) that a cancellation request has been made from a user who is a target of the total mute control, and the user's mute history, total comment history, total mute history, etc. for a predetermined period. As a result, the administrator can decide whether to cancel the total mute control by considering various histories of the user. For example, if the mute history and total comment history indicate a change of heart, it is more likely to move in the direction of cancellation, and the degree to which the mute history and total comment history indicate a change of heart is higher the more times the user has been muted in the past based on the total mute history (for example, the number of times mute is specified is smaller, the content of the comments is more subdued, etc.). When the administrator performs the cancellation operation, cancellation request approval information is transmitted from the administrator terminal 200 to identify the user who is the source of the all mute cancellation request information and who will cancel the all mute control.

[0239] By receiving the cancellation request information, the administrator can view the mute history, total comment history, and total mute history via the administrator terminal 200, but this is not limiting, and the administrator can also view the mute history, total comment history, and total mute history of a specified user by making a total comment history request to the distribution server 100. This allows the administrator to forcibly activate total mute control depending on the history via the administrator terminal 200. Note that the mute history, total comment history, and total mute history are only viewable by the administrator, and are not viewable by users via user terminals.

[0240] In step S87, it is determined whether or not release request approval information has been received. If it is determined that the release request approval information has not been received, the mute-related information update process is terminated. On the other hand, if it is determined that the release request approval information has been received, in step S88, the all mute flag of the user identified from the release request approval information (the user who sent the all mute release request information and is the target of release of all mute control) is set to off, the all mute history is updated (for example, the number of times all mute control has been performed is added), and the mute-related information update process is terminated.

[0241] 17 is a diagram for explaining a flowchart of a comment delivery process for reflecting the mute function and the full mute control function when a posted comment is delivered to a user terminal. The comment delivery process is executed when the control unit 130 of the delivery server 100 performs the above-mentioned comment delivery step (or is executed within each comment delivery step). The delivery server 100 performs the comment delivery process based on a program stored in the storage unit 120.

[0242] First, in step S90, it is determined whether or not the posting user who posted the comment to be distributed in each comment distribution step is a user not subject to all muting. A user not subject to all muting is a user who is set by the administrator via the administrator terminal 200 from among SP users, for example, so that the user is not subject to all muting control, regardless of the user's muting history (even if the history satisfies the regulatory conditions).

[0243] When it is determined in step S90 that the user is not a target user for all muting, the process proceeds to step S96. On the other hand, when it is not determined in step S90 that the user is not a target user for all muting, it is determined in step S91 whether or not the all mute flag is set on for the posting user. When it is not determined in step S91 that the all mute flag is set on for the posting user, it is determined in step S92 whether or not the first regulatory condition is satisfied based on the posting user's muting history for a first period. When it is not determined in step S92 that the first regulatory condition is satisfied, it is determined in step S94 whether or not the second regulatory condition is satisfied based on the posting user's muting history for a second period. When it is not determined in step S94 that the second regulatory condition is satisfied, the process proceeds to step S96.

[0244] In step S96, it is determined whether users participating in the same content as the posting user (users who may receive comments posted by the posting user) include a user who has specified the posting user as a muted target. Specifically, it is determined whether users who have specified the posting user as a muted target are included in the same content (same room in the case of the content of the third mode) based on the posting user's mute history (current mute history) shown in Fig. 14 and the participating user IDs shown in Fig. 6.

[0245] When it is determined in step S96 that the users participating in the same content as the posting user do not include a user who has designated the posting user as a target for muting, the posting user's comment is distributed to the user terminals of the users to whom the comment is to be distributed in the comment distribution step. On the other hand, when it is determined in step S96 that the users participating in the same content as the posting user include a user who has designated the posting user as a target for muting, the posting user's comment is distributed to the user terminals of users other than the designated user who has designated the posting user as a target for muting, among the users to whom the comment is to be distributed in the comment distribution step. This restricts the reflection of the comment from the posting user in the user terminals of the designated users who have designated the posting user as a target for muting.

[0246] On the other hand, if it is determined in step S91 that the all mute flag is set to on for the posting user, the process proceeds to step S99. Even if the all mute flag is not set to on, if it is determined in step S92 that the first restrictive condition is met, the process sets a first all mute flag to on as the all mute flag in step S93 and proceeds to step S99. If it is determined in step S94 that the second restrictive condition is met, the process sets a second all mute flag to on as the all mute flag in step S95 and proceeds to step S99.

[0247] In step S99, it is determined whether or not the users participating in the same content as the posting user include a user who has set the all mute off flag to on. Specifically, it is determined whether or not the users who have set the all mute off flag to on are included in the same content (the same room in the case of the content of the third mode) based on the participating user IDs shown in Fig. 6 and the setting states of the all mute off flags of the participating users shown in Fig. 14.

[0248] If it is determined in step S99 that the users participating in the same content do not include a user who has set the all mute off flag to on, the comment distribution process is terminated without distributing the comment of the posting user to any user terminal. On the other hand, if it is determined in step S99 that the users participating in the same content include a user who has set the all mute off flag to on, the comment of the posting user is distributed to the user terminal of the user who has set the all mute off flag to on in step S100, and the comment distribution process is terminated.

[0249] <Examples of specific configurations and effects of mute restrictions> (1) In the above-mentioned embodiment, when a user performs an operation on a user terminal of a certain user to designate another user as a muted user (a restricted user), the distribution server 100 receives the mute designation information transmitted from the user terminal, and updates the mute history for the designated other user as shown in step S81 of Fig. 16. When a comment is posted from a user who satisfies the restriction condition based on the mute history among multiple users participating in the virtual space of the same content (room) and has all mute flags set to on, the posting user is considered to be a user who tends to make annoying comments, and NO is determined in steps S91, S92, S94, etc. of Fig. 17, so that the reflection of the comment can be restricted in the user terminals of multiple users participating in the virtual space, including users who have not designated the user as a muted user. This makes it possible to efficiently restrict nuisance behavior without impeding free exchange and communication.

[0250] (2) In the embodiment described above, when the determination in step S99 in Fig. 17 is NO, comments from users who satisfy the regulating conditions are not reflected in multiple user terminals. This makes it possible to prevent comments from users who tend to perform nuisance actions from being reflected and thus causing adverse effects on other users.

[0251] (3) In the above-described embodiment, in a user terminal participating in a content or displaying a setting screen, the user can select whether to reflect comments from users who are subject to the all-mute control on the user terminal without censoring them, or to restrict their reflection. In addition, in response to the all-mute selection information transmitted in response to the selection, as shown in step S84 of Fig. 16, an all-mute off flag is updated to specify whether or not to restrict the reflection of comments posted by users whose all-mute flags are set to on and satisfy the restriction conditions corresponding to the user of the user terminal, and when a comment posted by a user whose all-mute flag is set to on is accepted, the reflection of the comment is restricted for the user terminal of the user whose all-mute off flag is set to off by determining NO in step S99 of Fig. 17. This allows the restriction of the reflection of actions from users who satisfy the restriction conditions to be set for each user, thereby improving convenience.

[0252] (4) In the above-mentioned embodiment, whether or not a user satisfies the restriction conditions is judged based on the user's muting history updated during a predetermined period (e.g., first period, second period, etc.). This prevents a user from being judged to satisfy the restriction conditions forever because of the history from before the predetermined period, even if the user has changed his / her mind and improved his / her actions, resulting in excessive restriction.

[0253] As the predetermined period, a first period (e.g., 24 hours) and a second period (e.g., one week) longer than the first period are defined, and as shown in Fig. 15, the restriction condition is satisfied when the number of mutes during the first period reaches a first number based on the mute history, and even if the number of mutes during the first period does not reach the first number, the restriction condition is also satisfied when the number of mutes during the second period reaches a second number that is greater than the first number. As a result, the period that is the subject of the determination as to whether or not the restriction condition is satisfied and the number of times that mute designation has been received are defined in stages, allowing for appropriate restriction.

[0254] In addition, the second period is set to a period of at least twice the first period, and the second number is set to a number less than twice the first number. As a result, even if a user is designated as a muting target to the extent that he / she is not determined to satisfy the restriction condition in the first period, he / she may be determined to satisfy the restriction condition when viewed over the long period of time that is the second period, and may be restricted. This makes it possible to restrict the reflection of comments from users who are designated as muting targets on a daily basis for a long period of time.

[0255] (5) In the above-described embodiment, by receiving mute unblocking information from a user terminal for unblocking a specific user designated as a muting target from the muting target, the mute history for the specific user is updated to a past mute history as shown in step S81 of Fig. 16, and whether or not the restriction condition is satisfied is determined based on the current mute history among the mute history as shown in steps S92 to S95 of Fig. 17. Even when mute unblocking information for a user determined to satisfy the restriction condition is received and the current mute history is updated to a history that does not satisfy the restriction condition, the determination that the restriction condition is satisfied is maintained for the user determined to satisfy the restriction condition (for example, even if the determination is YES in step S83 of Fig. 16, all mute flags are not set to OFF). As a result, the determination that the restriction condition is satisfied is maintained even when mute unblocking information is received, so that it is possible to prevent the restriction condition from being illegally released by a user's operation.

[0256] (6) In the above-described embodiment, the log management unit 131 manages the total comment history for each user, and when all-mute undo request information is received, undo request information for identifying the total comment history, etc. is sent to the administrator terminal 200 (step S86 in FIG. 16), and the total comment history, etc. can be notified (displayed) on the administrator terminal 200 based on the undo request information, making it visible to the administrator. This allows the administrator to grasp, for example, the total comment history of the user who has requested undo, and use this as a basis for deciding whether or not to undo the all-mute control.

[0257] (7) In the above-mentioned embodiment, when mute specification information is received, the mute specification history including the specification frequency of the user who sent the mute specification information is updated in step S82 of Fig. 16, and whether or not a specific user satisfies the restriction condition is determined based on the specification frequency of the specified user who specified the specific user as a mute target. This makes it possible to adjust the degree of influence when the specific user is specified as a mute target according to the specification frequency.

[0258] (8) In the above-described embodiment, for example, when a comment is received from an SP user or the like from a user terminal operated by one of the all-muting-excluded users (special users belonging to a special category) set by the administrator, the user terminal of a user who has not designated the all-muting-excluded user as a muting target among multiple users participating in the same content determines YES in step S90 of Fig. 17, and the comment can be reflected regardless of the muting history of the all-muting-excluded user, whereas the user terminal of a user who has designated the all-muting-excluded user as a muting target restricts the reflection of the comment in step S98 of Fig. 17. As a result, even if the comment is from a all-muting-excluded user, the reflection is restricted in the user terminal of the user who has designated the user as a muting target, so that the user's intention is respected and adverse effects on the user can be prevented.

[0259] (9) In the above-described embodiment, as shown in Figures 8 to 13, when a comment containing a NG word that is restricted from being reflected is received, the reflection of the comment is restricted regardless of the muting history of the user who posted the comment. On the other hand, even if a comment containing a NG word is posted and restricted, the muting history of the user who posted the comment is not updated. This makes it possible to manage NG words and muting history separately, and prevents one from affecting the other, resulting in excessive restriction.

[0260] (10) In the above-described embodiment, the mute-related information including the updated mute reception history and mute designation history is displayed on the administrator terminal 200 so that the administrator can check it, but it is not displayed on the user terminal 300, so that the user cannot be identified. This makes it possible to prevent a user from being identified and misused (for example, multiple users designating a specific user as a restricted user and selectively making them satisfy the restriction conditions).

[0261] <Modification> Modifications to the above-described embodiment are listed below.

[0262] (1) In the above embodiment, an example of restricting the reflection of comments posted by a user with all mute flags set to ON on the user terminals of other users, except for users with all mute off flags set to ON, has been described. However, the restriction process is not limited to restricting all comments posted by users with all mute flags set to ON, and may be a process of restricting the reflection according to a predetermined ratio. The process of restricting the reflection according to a predetermined ratio may be, for example, a process of restricting the reflection of comments posted by user A with all mute flags set to ON at a ratio of 50%. Specifically, when user A posts five comments such as comments 1 to 5 over time, when comments 1 to 5 are each received, whether or not to restrict the reflection of the comment may be determined by lottery, and the reflection may be restricted at a ratio of 50%. Also, the reflection of comment 1 may be restricted, the next comment 2 may be reflected, and the reflection of the next comment 3 may be restricted according to the order of posting so that the ratio of the reflection restriction is 50%, for example. This allows comments from users who meet the regulating conditions based on their muting history to be thinned out, preventing all comments from users who tend to perform nuisance actions from being reflected, which could have a negative impact on other users.

[0263] The process of restricting reflection according to a predetermined ratio may be such that, when a user posts the same or similar comments (including comments containing the same or similar words; hereinafter, simply referred to as the same or similar comments, etc.) consecutively within a predetermined period (for example, one minute), the reflection of the posted same or similar comments, etc. is restricted at a ratio of 50%. This makes it possible to prevent other users from feeling uncomfortable due to the same or similar comments, etc. being posted consecutively within a predetermined period.

[0264] (2) In the above embodiment, an example was described in which it was determined whether the restriction condition was satisfied based on the number of devices designated as muting targets and the frequency of designation by the designated user in FIG. 15. However, the criterion for determining whether the restriction condition is satisfied may be only the number of devices designated as muting targets (one designation is calculated as the number of muting targets regardless of the frequency of designation) without taking into account the frequency of designation by the designated user. In addition, the criterion for determining whether the restriction condition is satisfied is not limited to this as long as it includes the number of devices designated as muting targets, and may be different depending on the total mute history updated in step S88 in FIG. 16 in addition to the number of devices designated as muting targets. This allows the strength of the restriction to be adjusted depending on the number of times that the device has been released based on the total mute history. More specifically, the criterion for determining whether the restriction condition is satisfied may be set lower so that the number of devices designated as muting targets (the number of mutings) can be satisfied with a smaller number as the number of times that the device has been released after the total mute control has been performed in the past is larger according to the total mute history (for example, the values ​​of A1 to C2 are set to be relatively smaller as the number of times that the device has been released is larger). In this way, the more the number of releases, the fewer the number of mutes required to satisfy the restrictive condition, and the more likely it is that the device will be subject to full mute control.

[0265] (3) In the above-described embodiment, an example was shown in which the user characters of each user participating in the content are placed in the virtual space, making it possible to grasp the user characters of the users participating in the content, but the placed user characters include not only the user characters of users who are not subject to the total mute control, but also the user characters of users who are subject to the total mute control. This makes it impossible to determine whether a user is subject to the total mute control based on whether a user character is placed, making it difficult for a user to notice that the restriction conditions are met and the reflection of comments is restricted. Note that if a user who is subject to the total mute control meets other conditions (for example, meets a prohibition condition), the user character of that user may not be placed in the virtual space and may be hidden.

[0266] (4) In the above-described embodiment, an example was described in which the comment delivery process shown in FIG. 17 is performed based on the mute-related information (for example, history accumulated across multiple contents) accumulated for each user. However, by receiving mute specification information from a participating user associated with a certain content (hereinafter referred to as content A), the mute-related information in the content A may be updated, and the comment delivery process in the content A may be performed based on the mute-related information. That is, the mute-related information may be managed for each type of content, and, for example, the mute control in the content A or the total mute control may be performed based on the mute-related information updated in the content A. In addition, in the case where the content A is a content that is performed consecutively, the mute control in the content A or the total mute control may be performed based on the mute-related information updated in the content A that is performed consecutively. This allows the mute reception history of a specific user designated by the mute specification information from a user associated with a common content to be immediately updated, and prevents comments from the specific user from being reflected in the user terminal of the user who designated the content. In addition, it is possible to determine whether or not the regulatory conditions are satisfied for users participating in the same content, thereby improving the effectiveness of the mute and full mute controls.

[0267] In the above embodiment, the users having a specific relationship are participating users (users participating in a group of a certain content) associated with a common content (group), and an example has been described in which all mute flags are set to on based on the mute history accumulated for each user, but all mute flags may be set to on based on the number of mutes designated as muted targets by participating users associated with the common content. Also, mute control may be performed based on the mute target designation by participating users associated with the common content.

[0268] Also, the users having the specific relationship may be all users currently logged in, in which case the all mute flag may be set to on based on the number of mutes designated as muting targets by all users currently logged in. Also, mute control may be performed based on the designation of muting targets by all users currently logged in.

[0269] Furthermore, the user having a specific relationship may be a user whose corresponding user character is located within a predetermined range in a content in which a user character corresponding to the user located in a virtual space is moved according to the operation of the user. In this case, the all mute flag may be set to on based on the number of mutes designated as a mute target by the user whose corresponding user character is located within the predetermined range. Note that the predetermined range may be, for example, a circle with a radius of 10 m in the virtual space, or a range that changes each time to include a predetermined number of users (for example, 20 people, 100 people, etc.), and may be determined to be different depending on the type of content or virtual space. This allows the reflection of comments between users who participate in the same content and whose user characters are located within a predetermined range to be restricted, so that the restricted range can be prevented from becoming too large. Also, the mute control may be performed based on the mute target designation by the user whose corresponding user character is located within a predetermined range.

[0270] (5) In the above-described embodiment, as an example of a restricting means for performing processing to restrict the reflection of comments from users designated as muted by other users or users who satisfy the restrictive conditions, an example was shown in which, in the distribution server 100, comments from users designated as muted are not distributed to users who have designated the user as a muted target, and comments from users who satisfy the restrictive conditions are not distributed to users who have designated the user as a muted target or to users who have not been designated as muted, as shown in Fig. 17. However, in the distribution server 100, comments from users who do not satisfy the restrictive conditions may be uniformly distributed to multiple users including the user who has designated the user as a muted target, while the distributed comments may not be displayed on the user terminal of the user who has designated the user as a muted target, and only comments from users who satisfy the restrictive conditions may not be distributed to users who have designated the user as a muted target or to users who have not been designated as muted, or information that can identify that the comment is from a user who satisfies the restrictive conditions may be distributed, and the distributed comments may not be displayed depending on the setting state of the user terminal (for example, an all mute off flag).

[0271] (6) In the above-described embodiment, FIG. 5 shows an example in which multiple types of content (rooms) are provided, and mute control and full mute control are performed for each type of content. However, for special content among the multiple types of content, at least one of mute control and full mute control may not be performed. The special content may be, for example, content that is set by the administrator or creator (organizer) as not to be muted, or predetermined content that is not primarily intended for communication with other participating users (for example, talent content of the second type, celebrity content, and live content of the third type). This allows effective use / disabling of muting to be adjusted according to the content.

[0272] (7) In the above-described embodiment, as shown in FIG. 17, when the restrictive conditions are satisfied, the user is automatically subject to the full mute control. However, the present invention is not limited to this. Information for identifying the user's mute-related information, total comment history, etc., along with the notification that the restrictive conditions are satisfied may be delivered to the administrator terminal 200, and whether or not the user is subject to the full mute control may be set at the discretion of the administrator who has confirmed the information. In addition, when the user is participating in a content other than a specific content among a plurality of types of content, the user is automatically subject to the full mute control when the restrictive conditions are satisfied. Meanwhile, when the user is participating in a specific content, information for identifying the user's mute-related information, total comment history, etc., along with the notification that the restrictive conditions are satisfied may be delivered to the administrator terminal 200, and whether or not the user is subject to the full mute control may be set at the discretion of the administrator who has confirmed the information. The specific content may be, for example, a content that is set by the administrator or creator (host) to be subject to the full mute control at the administrator's discretion, or a predetermined content (for example, the first aspect of the content) that is mainly intended to facilitate communication with other participating users. This allows the start trigger of the full mute control to be adjusted according to the content of the content.

[0273] (8) In the embodiment described above, an example was described in which it was determined whether the all mute flags were set to on while participating in content as shown in step S91 in Fig. 17, but this is not limiting. For a user whose all mute flags are set to on, it may be determined that the all mute flags are set to on when logging in or participating in any content, and thereafter, when a comment is posted from that user, the process may proceed to step S99 without making the determination in step S91. This reduces the processing load.

[0274] (9) In the above-described embodiment, an example has been described in which the all mute flag is released at the discretion of the administrator, as shown in Fig. 16. However, the condition for releasing the all mute flag may be automatically met when a user exits a content for which the all mute flag is set to on, when the day after the day on which the all mute flag is set to on comes (when the date crosses), when a predetermined period of time (e.g., 24 hours) has passed since the all mute flag was set to on, when a user has participated in any content for a predetermined period of time since the all mute flag was set to on, or the like. In the above-mentioned embodiment, an example of restricting the reflection of comments from users designated as muting targets or users with all mute flags set to on has been described, but the present invention is not limited to this. Comments containing specific words from users designated as muting targets or users with all mute flags set to on may be reflected on the user terminals of all users even if the user is designated as muting targets or the all mute flags are set to on. The specific words may be, for example, catchphrases of SP users or words indicating one-liners, or words preset by the administrator.

[0275] (10) In the above-described embodiment, an example was described in which, when an SP user newly participates in the virtual space of the content of the first aspect, if a NG word (e.g., individual NG, type NG) set for the SP user is included in the comment history in step S13 of Fig. 8, the comment including the NG word is deleted from the comment history and comment history information for identifying the updated comment history is output in step S12. However, this is not limited to the above, and when an SP user newly participates in the virtual space of the content of the first aspect, the comment history may be updated to one in which comments corresponding to actions belonging to the first type are maintained while comments corresponding to actions belonging to the second type are deleted, depending on the type of NG word set for the SP user, and comment history information for identifying the updated comment history may be output. For example, among the NG words set for an SP user, the type NG set for the type of the SP user may be set as a first type NG word, and the individual NG set by the SP user may be set as a second type NG word, and when the SP user newly participates in the virtual space of the content of the first aspect, the comments including the type NG word of the first type may be maintained, while the comments including the individual NG word of the second type may be updated to a deleted comment history, and comment history information for identifying the updated comment history may be output. This allows for more detailed discrimination between reflecting or restricting according to the type of NG word when the SP user newly participates in the virtual space of the content of the first aspect. Note that the first type NG word and the second type NG word are not limited to this, and for example, a first rank and a second rank may be set for each NG word according to the meaning of the word when the NG word is set, and the NG word set to the first rank may be set to the first type NG word, and the NG word set to the second rank may be set to the second type NG word.

[0276] (11) In the above-described embodiment, an example was described in which users who participate in a group of content that can be viewed, experienced, etc. are users who have a specific relationship. However, this is not limited to this, and for example, instead of a virtual space or user characters being displayed, users who participate in a message sending / receiving group (e.g., a group chat, mailing list, etc.) that is set up so that messages can be sent and received between multiple people may be considered to be users who have a specific relationship.

[0277] (12) In the above embodiment, the distribution server 100 restricts the reflection of individual NGs set for SP users, whereas an example has been described in which individual NG words for general users who are not SP users, etc. cannot be set or restricted. However, it is also possible to allow general users who are not SP users, etc. to set individual NG words for the general users upon request from the general users to set NG words. In this case, the distribution server 100 may restrict the reflection of individual NG words for general users only in host rooms (virtual spaces) that are related to the general users, such as rooms opened (hosted) by the general users themselves, and in which other users (e.g., friend users, etc.) can participate. This makes it possible to prevent NG words set for general users from being excessively restricted from being reflected even when they are not related to the general users.

[0278] (13) In the above-mentioned embodiment, as shown in step S18 of Fig. 8, step S35 of Fig. 10, step S57 of Fig. 12, etc., it is determined whether or not the comment posting user is a user who satisfies the prohibition condition for the type of related SP user (hereinafter referred to as SP1) based on the NG related information of Fig. 7(c), and if the user satisfies the prohibition condition (hereinafter referred to as a prohibited user), reflection of the comment posted by the prohibited user is restricted regardless of whether or not the comment contains an NG word or whether or not an SP user who triggers the satisfaction of the prohibition condition (for example, an SP user whose number of restrictions has reached a predetermined number, hereinafter referred to as a prohibited SP user) participates. On the other hand, an example has been described in which, when a related SP user who is related to the content viewed, experienced, etc. is a user of a type (hereinafter referred to as SP2) different from the type that satisfies the prohibition condition, reflection of the comment posted by the prohibited user is not restricted just by satisfying the prohibition condition. In this case, it is possible to notify the related SP user of SP2, which is related to the content that the prohibited user is viewing or experiencing, of information that enables the prohibited SP user to identify the prohibited SP user who has satisfied the prohibited condition (for example, the distribution server 100 may output information to display a message such as "This user has a predetermined number of NGs against prohibited SP users belonging to SP1" on the user terminal of the related SP user). It is also possible to notify the related SP user of SP2, which is related to the content that the prohibited user is viewing or experiencing, of information that enables the prohibited word that has satisfied the prohibited condition and is restricted from being reflected, to be identified (for example, the distribution server 100 may output information to display a message such as "The following are NG words posted by the prohibited user..." on the user terminal of the related SP user). This makes it possible to call attention to the related SP user of SP2.

[0279] In addition, if the above-mentioned prohibited user satisfies the prohibited conditions for a predetermined number or more (e.g., two, three, etc.) of types by participating in content related to the related SP users of SP2 and posting NG words, thereby satisfying the prohibited conditions for the related SP users of SP2, it is possible to restrict the reflection of comments posted by the prohibited user in the related content of a type that does not satisfy the prohibited conditions. In this way, if the prohibited conditions are satisfied for a predetermined number or more types, the user is recognized as clearly malicious, and the prohibited user is prevented from posting comments regardless of the type of related SP user, thereby preventing the damage from spreading.

[0280] In addition, the prohibited conditions satisfied by the prohibited user may be lifted (for example, the number of restrictions may be reset) in response to an operation by the prohibited SP user or the administrator that triggers the satisfaction of the prohibited conditions. This prevents the situation in which the prohibited conditions are satisfied indefinitely from continuing, thereby preventing the prohibited user from continuing to be restricted from posting comments.

[0281] (14) In the above embodiment, an example was described in which an individual NG can be set based on a request to set a NG word in response to an operation from the SP user, while a type NG that is the default for each type of SP user cannot be changed. This allows individual NG to be customized according to the SP user's will, improving convenience, while making type NG unchangeable, making it easier for the administrator to manage the restriction level by type NG. However, this is not limited to this, and type NG that is the default for each type of SP user may also be set for each SP user according to an operation from the SP user. In this case, for example, after the type NG that is the default for each type of SP user set by the administrator is uniformly reflected as NG information for each SP user (for example, type NG is stored in correspondence with each user information in FIG. 7(c)), not only individual NG but also type NG stored in correspondence with each user information may be customized (such as setting to be not subject to restriction) based on a request to set a NG word in response to an operation from the SP user. This allows not only individual NG but also type NG to be customized according to the SP user's will, improving convenience.

[0282] (15) In the above-described embodiment, a comment posting is given as an example of an action that a user can take and an action that is subject to regulation. However, the actions that a user can take and the actions that are subject to regulation (including, for example, NG word regulation, mute regulation, full mute regulation, etc.) are not limited to this, and instead of or in addition to this, for example, an action of moving the position, direction, and tilt of a virtual camera that is placed in a virtual space and can be operated by a user, an action of changing a decorative object (for example, a costume object) of a user character placed in a virtual space, an action of emoting, an action of discarding an owned object, an action of providing money, a game value, a privilege, etc. may be appropriately set.

[0283] Regarding the act of changing the position, direction, and inclination of the virtual camera, the action to be restricted is, for example, restricting the entry position of the virtual camera to be outside a predetermined range (stage), restricting it to a predetermined direction, etc. Regarding the act of changing the decorative objects (e.g., clothing objects) of the user character placed in the virtual space, the action to be restricted is, for example, changing to a clothing object that stands out more than the content distributor, changing to a clothing object that is more revealing, etc.

[0284] For the act of emoting, the actions to be restricted are, for example, an action of attacking a fallen user object, or an action of repeating the same action. For the act of discarding a owned object, the actions to be restricted are, for example, an action of discarding an object provided by an SP user in content in which the SP user is a related SP user. For the act of providing money, play value, benefits, etc., the actions to be restricted are, for example, an action of providing a benefit to only one SP user in content in which multiple SP users participate. Note that the actions to be restricted are not limited to these, as they are appropriately set by the user who sets them, as in the above-mentioned embodiment.

[0285] (16) In the above-described embodiment, as an example of satisfying the prohibition condition in step S25 of Fig. 8, the number of times that NG words are posted to the SP user reaches a predetermined number of times, but the present invention is not limited to this as long as the judgment is based on NG-related information. For example, a rank according to the degree of influence on NG words (for example, NG words that satisfy the prohibition condition in one posting, or NG words that satisfy the prohibition condition in three postings, etc.) may be set, and whether or not the prohibition condition is satisfied may be judged based on other parameters such as NG-related information and rank. In addition, in the above-described embodiment, an example of judging whether or not the prohibition condition is satisfied based on NG-related information for one SP user is shown, but the present invention is not limited to this, and the judgment may be based on NG-related information for SP users of the same type (for example, the judgment is based on the total number of NG posts for SP user SP1) or the judgment is based on NG-related information for all SP users regardless of the type (for example, the judgment is based on the total number of NG posts for all SP users).

[0286] In addition, in the above-described embodiment, an example was described in which NG-related information is updated in step S24 when a type NG or individual NG is included in step S17 of Figure 8, etc., but this is not limited to the above, and NG-related information may be updated in step S24 only when a type NG or individual NG is included in step S17 of Figure 8, etc.

[0287] (17) In the above-described embodiment, an example of determining whether or not a set NG word is included in step S17 in FIG. 8 or the like has been described. In determining whether or not a NG word is included, it may be determined whether or not the set NG word itself is included, or alternatively or in addition to this, it may be determined whether or not a word related to the set NG word (action related to the set action) is included. Words related to the set NG word may include, for example, words that partially match the set NG word, words that have the same meaning as the set NG word, words that utilize the set NG word (for example, words that have been changed such as 5-step conjugation), and words that do not care about the difference between full-width and half-width.

[0288] (18) In the above-described embodiment, an example was described in which distribution server 100 is capable of providing content of the first to third aspects, but this is not limited thereto, and distribution server 100 may be capable of providing content of any one aspect, or of providing content of two aspects, or of providing content of another aspect as well.

[0289] In the above-mentioned embodiment, an example was described in which, during any of the content distributions of the first aspect, when the SP user changes from not participating to participating, the reflection of NG words set for the SP user is restricted. Here, when the participating SP user exits, the restriction on the reflection of NG words set for the SP user may be lifted. Also, assuming a temporary exit, the restriction on the reflection of NG words set for the SP user may be continued. In this case, the restriction on the reflection of NG words set for the SP user may be continued until a predetermined period (e.g., 5 minutes) has elapsed since the SP user exited, and the restriction may be lifted after the predetermined time has elapsed.

[0290] In the above-mentioned embodiment, an example was described in which the reflection of NG words set for a related SP user is restricted during content distribution in either the second or third mode, regardless of whether the related SP user is participating or not. Here, even if the related SP user leaves after participating, the restriction on the reflection of NG words set for the related SP user may be continued. In addition, in the case of a complete exit, the restriction on the reflection of NG words set for the related SP user may be lifted, and in this case, the restriction on the reflection of NG words set for the SP user may be continued until a predetermined period (e.g., 5 minutes) has elapsed since the related SP user left, and the restriction may be lifted after the predetermined time has elapsed.

[0291] [Software implementation example] The various control blocks of the control unit of a computer such as a server or a terminal in the above-mentioned embodiment 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). In the case where the control block is realized by software using a CPU, the computer equipped with the 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 (these are referred to as "recording medium") in which the program and various data are recorded so as to be readable by the computer (or CPU), and a RAM (Random Access Memory) in which the program is expanded. The object of the present invention is achieved by the computer (or CPU) reading and executing the program from the recording medium. As the recording medium, a "non-transient tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, etc., can be used. 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 may also be realized in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

[0292] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0293] 1 communication system, 2 network, 100 distribution server, 200 administrator terminal, 300 user terminal, 400 distribution user terminal

Claims

1. a program that enables an action accepted from a plurality of user terminals operated by a plurality of users having a specific relationship to be reflected in the plurality of user terminals so as to be recognizable by each of the plurality of users; Computer, an update means for updating a restriction history for a specific user by receiving restriction information for designating the specific user as a restricted user from the user terminal; A program that functions as a regulating means that, when an action is received from a user terminal operated by a user who satisfies the regulating conditions based on the regulating history, among multiple user terminals operated by each of multiple users having the specific relationship, performs processing to enable regulating the reflection of the action in multiple user terminals, including user terminals operated by users who have not designated the user as a regulated user.

2. A method for reflecting actions received from a plurality of user terminals operated by a plurality of users having a specific relationship on the plurality of user terminals in a manner that each of the plurality of users can recognize the actions, receiving restriction information for designating a specific user as a restricted user from a user terminal, thereby updating a restriction history for the specific user; When an action is received from a user terminal operated by a user who satisfies the restriction conditions based on the restriction history, among multiple user terminals operated by each of multiple users having the specific relationship, a processing step is performed to enable restriction of reflection of the action in multiple user terminals, including a user terminal operated by a user who has not designated the user as a restricted user.

3. A system that can reflect actions received from a plurality of user terminals operated by a plurality of users having a specific relationship on the plurality of user terminals in a manner that each of the plurality of users can recognize the actions, an update means for updating a restriction history for a specific user by receiving restriction information for designating the specific user as a restricted user from the user terminal; The system is provided with a regulating means that, when an action is received from a user terminal operated by a user who satisfies the regulating conditions based on the regulating history, among multiple user terminals operated by each of multiple users having the specific relationship, performs processing to enable regulating the reflection of the action in multiple user terminals, including user terminals operated by users who have not designated the user as a regulated user.

Images