System, method, program, and apparatus for providing content distribution services

Abstract

To support easy finding of content to be viewed.SOLUTION: A content delivery server 10 according to an embodiment of the present invention is communicably connected to a user terminal 30 via a communication network 20, and provides a content delivery service for delivering and viewing content to a user via the user terminal 30. The server 10 presents, to a viewing user, a screen displaying a list of a plurality of distributing users, and the screen displays a plurality of attribute values set for each distributing user such that the attribute values set for the viewing user and the attribute values not set for the viewing user can be distinguished from each other, so that the viewing user can know the attribute values of each distributing user including the attribute values common to the viewing user, which supports finding a suitable distributing user (and content provided by the distributing user).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for providing a content distribution service that enables content distribution and viewing. [Background technology]

[0002] Conventionally, various services have been provided for viewing and distributing content consisting of images and / or audio. In these services, users who wish to view content need to search for content they like. To support such content searches, for example, Patent Document 1 below discloses a system for associating tags entered by users viewing live videos with the live videos and presenting information about the live videos being distributed based on the associated tags. This system enables users to know the current content (topics) of the live videos being distributed based on information based on tags entered by actual viewers. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-019361 Summary of the Invention [Problem to be solved by the invention]

[0004] However, while the conventional technology described above makes it possible to learn the content of the content by the tags associated with the content, there is still a need to search for content associated with preferred tags, and some users may find the effort required for such searches burdensome.

[0005] One of the objects of the embodiments of the present invention is to help users easily find content to watch. Other objects of the embodiments of the present invention will become apparent by reading the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system for providing a content distribution service that includes one or more computer processors and enables content distribution and viewing, wherein the one or more computer processors execute the steps of setting multiple attribute values ​​for each of multiple users and presenting a first screen that lists a first plurality of distribution users to a viewing user, and the first screen displays the multiple attribute values ​​set for each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set for the viewing user and attribute values ​​not set for the viewing user.

[0007] A method according to one embodiment of the present invention is a method executed by one or more computers for providing a content distribution service that enables content distribution and viewing, and includes the steps of setting multiple attribute values ​​for each of multiple users, and presenting a first screen that lists a first plurality of distribution users to a viewing user, wherein the first screen displays the multiple attribute values ​​set for each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set for the viewing user and attribute values ​​not set for the viewing user.

[0008] A program according to one embodiment of the present invention is a program for providing a content distribution service that enables content distribution and viewing, and causes one or more computers to execute the steps of setting multiple attribute values ​​for each of multiple users, and presenting a first screen that lists a first plurality of distribution users to a viewing user, wherein the first screen displays the multiple attribute values ​​set for each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set for the viewing user and attribute values ​​not set for the viewing user.

[0009] An apparatus according to one embodiment of the present invention is an apparatus for providing a content distribution service that enables content distribution and viewing, and is equipped with a means for setting multiple attribute values ​​for each of multiple users, and a means for presenting a first screen that lists a first plurality of distribution users to a viewing user, wherein the first screen displays the multiple attribute values ​​set for each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set for the viewing user and attribute values ​​not set for the viewing user. [Effects of the Invention]

[0010] Various embodiments of the present invention help make it easier to find content to watch. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing a schematic configuration of a network including a content distribution server 10 according to an embodiment of the present invention. [Figure 2] FIG. 15 is a diagram illustrating an example of information managed by a user information table 1511. [Figure 3] FIG. 10 is a diagram for explaining the rank of broadcast users. [Figure 4] FIG. 15 is a diagram illustrating an example of information managed by a distribution management table 1512. [Figure 5] FIG. 15 is a diagram illustrating an example of information managed by a distribution user-specific viewing user management table 1513. [Figure 6] FIG. 10 is a diagram illustrating the conditions for each of a plurality of fan levels. [Figure 7] FIG. 15 is a diagram illustrating information managed by a topic tag information table 1514. [Figure 8] FIG. 15 is a diagram illustrating an example of information managed by a topic tag matching status management table 1515. [Figure 9] FIG. 2 is a diagram illustrating a top screen 50. [Figure 10] FIG. 10 is a diagram illustrating an example of display content in an individual display area 541. [Figure 11] FIG. 10 is a diagram illustrating a top screen 50 when "topic tag" is selected in a selection area 52. [Figure 12] FIG. 10 is a diagram illustrating an example of the display content of an individual display area 542. [Figure 13] FIG. 10 is a diagram illustrating a top screen 50 when "topic tag" is selected in a selection area 52, but no topic tag has been set for the corresponding user. [Figure 14] FIG. 2 is a diagram illustrating a topic tag setting screen 200. [Figure 15] A figure showing an example of the top screen 50 when "topic tag" is selected in the selection area 52, one or more topic tags are set for the corresponding user, but no distribution is being made by a distribution user to whom a common topic tag is set. [Figure 16] FIG. 2 is a diagram illustrating a tag-matching distribution user list screen 210. [Figure 17] FIG. 2 is a diagram showing an example of the display content of an individual display area 2121. [Figure 18] FIG. 6 is a diagram illustrating a distribution preparation screen 60. [Figure 19] FIG. 7 is a diagram illustrating a distribution screen 70. [Figure 20] FIG. 10 is a diagram illustrating an example of a viewing screen 80. [Figure 21] FIG. 10 is a diagram illustrating an example of a viewing screen 80 on which a gift selection screen 90 is superimposed. [Figure 22] FIG. 10 is a diagram illustrating a gift selection screen 90. [Figure 23] 10 is a flowchart illustrating a process executed by the server 10 when updating the rank of each user. [Figure 24] FIG. 10 is a diagram illustrating an example of an update rule for a rank meter value. [Figure 25] 10 is a flowchart illustrating a process executed by the server 10 when granting diamonds to each user. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same reference numerals may be used to designate the same or similar components.

[0013] FIG. 1 is a diagram illustrating a schematic configuration of a network including a content distribution server 10 according to an embodiment of the present invention. As illustrated, the server 10 is communicably connected to a user terminal 30 via a communication network 20 such as the Internet. Although only one user terminal 30 is illustrated in FIG. 1, the server 10 is communicably connected to a plurality of user terminals 30. The server 10 provides a content distribution service for distributing and viewing content to users via the user terminals 30. The content distribution server 10 is an example of a device that implements part or all of the system (or device) of the present invention.

[0014] First, we will explain the hardware configuration of the content distribution server 10. The content distribution server 10 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (storage device) 15, and these components are electrically connected via a bus or the like (not shown).

[0015] The computer processor 11 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 15 or the like into a main memory 12 and executes various instructions included in the programs. The main memory 12 is configured, for example, by a DRAM or the like.

[0016] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.

[0017] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to be able to realize wired or wireless communication via the communication network 20 or the like.

[0018] The storage 15 is configured, for example, by a magnetic disk, a flash memory, etc. The storage 15 stores various programs including an operating system, various data, etc. For example, the storage 15 has various tables 151 that store various information for providing a content distribution service. The storage 15 also stores, for example, a server-side program 40 according to an embodiment of the present invention. The program 40 is a program that causes the server 10 to function as all or part of a system for providing a content distribution service. At least a part of the server-side program 40 can be configured to be executed on the user terminal 30 via a terminal-side program 42, which will be described later.

[0019] In this embodiment, the content distribution server 10 may be configured using a plurality of computers each having the above-described hardware configuration. For example, the content distribution server 10 may be configured by one or a plurality of server devices.

[0020] The content distribution server 10 configured in this manner can be configured to function as a web server and an application server, and in this case, executes various processes in response to requests from a terminal-side program 42 installed in the user terminal 30, and transmits screen data (e.g., HTML data) and control data corresponding to the results of the processes to the user terminal 30. The user terminal 30 can output a web page or other screen based on the received data.

[0021] Next, we will explain the hardware configuration of the user terminal 30. The user terminal 30 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, and these components are electrically connected via a bus or the like (not shown).

[0022] The computer processor 31 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 35 or the like into the main memory 32 and executes various instructions included in the programs. The main memory 32 is configured, for example, by a DRAM or the like.

[0023] The input / output I / F 33 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 33 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), an audio input device such as a microphone, and an image input device such as a camera. The input / output I / F 33 also includes an image output device such as a display, and an audio output device such as a speaker.

[0024] The communication I / F 34 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to be able to realize wired or wireless communication via the communication network 20 or the like.

[0025] The storage 35 is configured, for example, by a magnetic disk or a flash memory. The storage 35 stores various programs including an operating system, various data, and the like. The programs stored in the storage 35 can be downloaded and installed from an application market or the like. The storage 35 also stores a terminal-side program 42. The program 42 can be configured as a web browser or other application (e.g., a terminal-side application for a content distribution service), and can be configured to execute at least a part of the server-side program 40, as described above.

[0026] In this embodiment, the user terminal 30 may be configured as a smartphone, a tablet terminal, a personal computer, a wearable device, or the like.

[0027] A user operating a user terminal 30 configured in this manner can use the content distribution service provided by the server 10 by communicating with the content distribution server 10 via a terminal-side program 42 installed in storage 35 or the like.

[0028] Next, we will explain the functions of the content distribution server 10 configured as above. As shown in Fig. 1, the computer processor 11 of the server 10 is configured to function as a management function control unit 111 and a service provision control unit 112 by executing instructions included in a program (for example, at least a part of the server-side program 40) loaded into the main memory 12.

[0029] The management function control unit 111 is configured to execute various processes related to the control of the management functions of the content distribution service. For example, the management function control unit 111 transmits screen data and control data of various screens related to the management functions to the user terminal 30, executes various processes in response to operation input by the user via the screens output on the user terminal 30, and transmits screen data and control data according to the results of the processes to the user terminal 30. The management functions controlled by the management function control unit 111 include, for example, login processing (user authentication), billing control, and user account management.

[0030] The service provision control unit 112 is configured to execute various processes for controlling the provision of content distribution services. For example, the service provision control unit 112 is configured to distribute content provided by a distribution user who distributes the content to multiple viewing users. For example, the service provision control unit 112 is configured to present a viewing screen to each of the multiple viewing users who view the content, and specifically, for example, to transmit screen data of the viewing screen, control data, etc. to the user terminal 30 (hereinafter sometimes referred to as viewing terminal 30) of each viewing user.

[0031] In this embodiment, the service provision control unit 112 is configured to set multiple attribute values ​​for each of multiple users. The attribute values ​​are values ​​of attributes possessed by the user, and the attributes include, but are not limited to, the user's preferences (hobbies, tastes, preferences, etc.) and interests. For example, the service provision control unit 112 may be configured to set multiple attribute values ​​selected by each user from multiple predetermined attribute values ​​for the corresponding user. The selection of such attribute values ​​is performed, for example, via a screen output on the user terminal 30.

[0032] The service provision control unit 112 is also configured to present a first screen displaying a list of multiple broadcast users to the viewing user. For example, the service provision control unit 112 transmits screen data and control data of the first screen to the corresponding viewing terminal 30.

[0033] In this embodiment, the first screen is configured to display a plurality of attribute values ​​set for each of a plurality of broadcast users in a manner that makes it possible to distinguish (e.g., in different manners) the attribute values ​​set for the viewing user to whom the screen is presented from the attribute values ​​not set for that viewing user. For example, on the first screen, of the plurality of attribute values ​​set for each broadcast user, the attribute values ​​set for the viewing user are displayed in a first manner, while the attribute values ​​not set for the viewing user are displayed in a second manner. The display manner includes, for example, the color and shape of the background, outline, etc.

[0034] In this way, content distribution server 10 in this embodiment presents a screen displaying a list of multiple distribution users to the viewing user, and this screen displays multiple attribute values ​​set for each distribution user in a manner that makes it possible to distinguish between attribute values ​​set for that viewing user and attribute values ​​not set for that viewing user, allowing the viewing user to know the attribute values ​​of each distribution user that include attribute values ​​in common with the viewing user, which helps to find a suitable distribution user (and content provided by that distribution user). In other words, server 10 helps to easily find content to view.

[0035] In this embodiment, the content distributed includes various types of digital content. For example, the content may consist of images (video or still images) and audio, or may consist of either one of these. Furthermore, the content may be transmitted in real time (live distribution) from a user terminal 30 (hereinafter, sometimes referred to as a distribution terminal 30) of a distribution user who provides the content, or may be provided in advance from the distribution terminal 30 and pre-stored in a storage device such as storage 15. The live distribution of content may involve a certain delay (time lag) depending on the settings of the distribution user or the network conditions. The live distribution of content is performed, for example, using a streaming method using a protocol such as HTTP Live Streaming (HLS). The distribution user of the content may include a business operator such as a broadcasting station.

[0036] Furthermore, the content transmitted from the broadcasting terminal 30 is composed of, for example, video and audio of the broadcasting user input (captured) via a camera and microphone possessed by the broadcasting terminal 30. Furthermore, such content is composed of, for example, video and audio corresponding to a screen output on the broadcasting terminal 30. Furthermore, such content is composed of, for example, video corresponding to a screen output by an application (e.g., a game) running on the broadcasting terminal 30, audio output by the application, and / or audio of the broadcasting user input via a microphone possessed by the broadcasting terminal 30.

[0037] Furthermore, in the present embodiment, the content to be distributed may be such that part of the data constituting the content is transmitted in real time from distribution terminal 30, while part of the data constituting the content is pre-stored in server 10 or viewing terminal 30. For example, audio constituting the content may be transmitted in real time from distribution terminal 30, while images constituting the content may be pre-stored in server 10 or viewing terminal 30, and the content may be generated in server 10 or viewing terminal 30 based on these data.

[0038] Furthermore, for example, in addition to the audio constituting the content, movement data (motion data) for moving objects such as characters may be transmitted in real time from the distribution terminal 30, while images constituting the content may be stored in advance in the server 10 or the viewing terminal 30, and the images may include model data of the objects. In this case, the movement data may be generated based on the movements of the distribution user (including, for example, head movements and changes in facial expressions) recognized via a camera in the distribution terminal 30. The content generated in the server 10 or the viewing terminal 30 may include objects such as characters that move based on the model data and movement data.

[0039] In this embodiment, the first screen may be configured to display a plurality of attribute values ​​set for each of a plurality of broadcast users in a manner that prioritizes the attribute values ​​set for the viewing user to whom the screen is presented. For example, on the first screen, of the plurality of attribute values ​​set for each broadcast user, the attribute values ​​set for the viewing user are positioned higher and / or have a larger display size than attribute values ​​not set for the viewing user. This configuration helps the viewing user easily recognize the attribute values ​​common to them among the attribute values ​​set for the broadcast users.

[0040] The first screen may be configured to display a list of users who are currently distributing content as multiple distributor users. In this case, the first screen may be said to be a screen that displays a list of multiple pieces of content that are respectively distributed by multiple distributor users. This configuration helps users find suitable distributor users who are currently distributing content.

[0041] The first screen may be configured to display a list of multiple broadcast users who are currently broadcasting content and who have at least one attribute value that matches the viewing user. This configuration helps users find suitable broadcast users who have a common attribute value and are currently broadcasting content.

[0042] In this case, the service provision control unit 112 can be configured to present to the viewing user a second screen that lists users who have at least one attribute value that matches the viewing user as multiple broadcast users, and the first screen can be configured to display a link to the second screen (including the object and text to which the link is set). The second screen can also be configured to list, for example, users who have at least one attribute value that matches the viewing user and who meet conditions related to content broadcast history (e.g., conditions related to the number of times content has been broadcast, the duration of broadcast, and the number of days of broadcast, etc.) as multiple broadcast users. This configuration helps find suitable broadcast users who have common attribute values, regardless of whether content is currently being broadcast.

[0043] Furthermore, in this case, the first screen may display a link to the second screen differently depending on whether or not there is a user (a broadcast user to be listed) who is currently broadcasting content and whose at least one attribute value matches the viewing user. For example, the first screen is configured so that the display size of the link is smaller (including not being displayed) when there is a broadcast user to be listed than when there is no broadcast user. This configuration assists in finding a suitable broadcast user who has a common attribute value when there are no broadcast users who have a common attribute value and are currently broadcasting content.

[0044] Furthermore, the first screen may be configured to list a plurality of broadcast users so that broadcast users with a higher degree of match between the set attribute values ​​and the viewing user are given priority. For example, on the first screen, broadcast users with a higher degree of match between the attribute values ​​and the corresponding viewing user (e.g., a larger number of matching attribute values) are placed higher and / or have a larger display size. This configuration helps to easily find suitable broadcast users with common attribute values.

[0045] Furthermore, the first screen may be configured to display the multiple attribute values ​​set for each of the multiple broadcast users in a manner that allows distinguishing between attribute values ​​whose setting frequency in the content distribution service is equal to or greater than a threshold and attribute values ​​whose setting frequency is less than the threshold (e.g., in different manners). The setting frequency of a specific attribute value is defined, for example, as the ratio of the number of users to which the specific attribute value is set to the number of users to which at least one attribute value is set. For example, on the first screen, of the multiple attribute values ​​set for each broadcast user, attribute values ​​whose setting frequency is equal to or greater than a threshold are displayed in a first manner, while attribute values ​​whose setting frequency is less than the threshold are displayed in a second manner. This configuration makes it possible to know the setting frequency in the content distribution service of the attribute values ​​set for the broadcast user.

[0046] In this embodiment, various other controls may be performed based on the degree of match between the attribute values ​​of the distribution user and the viewing user. For example, the service provision control unit 112 may be configured to accept an input of an item by a viewing user viewing content while the content is being distributed, and the input of the item may be controlled based on the degree of match between the attribute values.

[0047] For example, the price of the item will be cheaper the higher the degree of match of the attribute values, and further, the lower the setting frequency of the matching attribute values. Also, for example, a specific item (for example, set as a free item) will be inputtable when there is a common attribute value between the broadcasting user and the viewing user, but will not be inputtable when there is no common attribute value. Conversely, for example, another specific item will be inputtable when there is no common attribute value between the broadcasting user and the viewing user, but will not be inputtable when there is a common attribute value.

[0048] Furthermore, for example, the service provision control unit 112 may be configured to display comments (e.g., user comments and system comments, etc.) on the distribution screen and viewing screen during content distribution, and the display of the comments may be controlled based on the degree of match of the attribute values. For example, the display mode (e.g., color and shape of background and outline, etc.) of comments related to a specific viewing user (e.g., user comments entered by the specific viewing user, or system comments corresponding to actions performed by the specific viewing user, etc.) is determined based on the degree of match of attribute values ​​between the specific viewing user and the distribution user.

[0049] Next, a specific example of one aspect of the content distribution server 10 of this embodiment having such functions will be described. The content distribution service in this example is configured as a service for live distribution and viewing of content consisting of videos including characters provided by a broadcasting user and the voice of the broadcasting user. Model data for the characters is uploaded to the server 10 (storage 15) in advance by the broadcasting user, and, as will be described in detail later, is downloaded by the viewing terminal 30 of the viewing user when viewing the content of the broadcasting user. First, in this example, the information managed by each table included in the various tables 151 will be described.

[0050] 2 illustrates information managed by user information table 1511 in this example. User information table 1511 manages information about users of the content distribution service, and as shown, in association with a "user account" that identifies an individual user, manages information such as "basic information" including account name and date of birth, "distribution history information" that is information about the distribution history as a distribution user, "viewing history information" that is information about the viewing history as a viewing user, "following user information" that is information about other users that this user is following, "family information" that is information about families that this user is a family member of, a "rank" that indicates the rank as a distribution user, a "rank meter value" that indicates the value of a rank meter that is a parameter for determining whether the rank has increased or decreased, a "number of owned coins" that indicates the number of owned virtual coins that can be used in the content distribution service, a "number of owned diamonds" that is the number of owned virtual diamonds, and "topic tag information" that is information about topic tags (attribute values) set by the user themselves.

[0051] In this example, a family is a community of fans who support a broadcast user, and can be joined in response to an invitation from the broadcast user or a family manager (e.g., designated by the broadcast user), or in response to approval by the broadcast user or family manager of a user's application to join. Family information includes information identifying the broadcast user corresponding to each family (e.g., user account). In this example, a maximum limit (e.g., 100 people) is set for the number of subscribers to a family. In this example, a user can join (belong to) multiple families.

[0052] In this example, coins are given to users for free or for a fee at various times. For example, users can acquire coins for free as a reward such as a login bonus. Also, for example, users can purchase coins for a fee (with real currency). Diamonds, which will be described in more detail later, are given to broadcasting users as one type of reward.

[0053] In this example, topic tags are used to set information about the user's hobbies and preferences (specifically, favorite manga titles, artist names, game titles, etc.) for the user. In this example, up to a predetermined number (specifically, five) of topic tags can be set for each user from among multiple topic tags predetermined by the operator of the content distribution service. Topic tag information includes a topic tag ID, described below, that identifies each set topic tag.

[0054] 3 is a diagram for explaining the ranks of broadcast users in this example. As shown in the figure, in this example, there are six rank bands: "S," "A," "B," "C," "D," and "E." The "S" rank band is made up of six ranks: "S1" to "S6," and each of the four rank bands: "A," "B," "C," and "D" is made up of three ranks (for example, "A1" to "A3"). Furthermore, the "E" rank band is made up of one rank: "E1." In other words, in this example, there are 19 ranks (6 + 3 × 4 + 1 = 19).

[0055] Furthermore, the rank range is higher on the "S" side and lower on the "E" side. Furthermore, within the same rank range, the larger the number attached to the rank range, the higher the rank, and the smaller the number attached, the lower the rank. In this example, the user's rank is set to "D1" as the initial value. As will be described in more detail later, in this example, the rank is updated based on the daily content distribution performance.

[0056] 4 illustrates information managed by delivery management table 1512 in this example. Delivery management table 1512 manages information related to individual deliveries, and as shown, in association with a "delivery ID" that identifies an individual delivery (content), manages information such as a "delivery user account" that identifies the delivery user, a "delivery start date and time" that is the date and time the delivery started, a "delivery duration" that is the duration (elapsed time) since the delivery started, the "number of viewing users (current value and maximum value)", the "number of comments" that is the number of comments entered by viewing users while the content was being delivered, the "number of likes" that is the number of "likes" entered by viewing users while the content was being delivered, the "number of consumed coins" that is the number of coins consumed in response to gift item input by viewing users while the content was being delivered, and the "number of support points" that is the total number of support points granted for this delivery.

[0057] 5 illustrates information managed in this example by broadcast user-specific viewing user management table 1513. Broadcast user-specific viewing user management table 1513 manages information related to viewing users by broadcast user in a target year and month, and as shown, manages information such as the viewing user's "fan level" for the broadcast user in the target year and month, the viewing user's "number of coins consumed," "viewing time," "number of viewing days," and "number of comments entered" for the corresponding broadcast, in association with a combination of a "broadcast user account" that identifies the broadcast user, a "viewing user account" that identifies the viewing user, and a "target year and month."

[0058] In this example, a fan level is set for a distributor user based on the viewing user's monthly behavioral record for content distributed by the distributor user. FIG. 6 illustrates the conditions for each of the multiple fan levels in this example. As shown in the figure, in this example, two or three conditions are set for each fan level, and a user who meets any one of these conditions will be assigned the corresponding fan level (the level will increase). For example, for fan level "1," two conditions are set: condition 1, which states "spend 10 coins or more, watch for 1.5 hours or more, and enter 4 comments or more," and condition 2, which states "spend 100 coins or more," and a user who meets any one of these two conditions will be a viewing user with fan level "1." For example, for fan level "4," three conditions are set: condition 1, "consume more than 1,000 coins, watch for more than 5 hours, watch for more than 3 days, and enter more than 30 comments," condition 2, "consume more than 3,000 coins, watch for more than 2 hours, and enter more than 5 comments," and condition 3, "consume more than 5,500 coins." A user who meets any one of these three conditions becomes a viewing user with fan level "4."

[0059] This determination of fan level is performed in real time while content is being distributed. Specifically, while content is being distributed, server 10 updates the number of coins consumed, viewing time, number of viewing days, and number of comments entered in real time for each viewing user in viewing user management table by distributor 1513, and determines whether or not the fan level has been upgraded based on this information. When the fan level is upgraded, the fan level value of the corresponding record in viewing user management table by distributor 1513 is updated.

[0060] 7 illustrates information managed by topic tag information table 1514 in this example. Topic tag information table 1514 manages information related to topic tags that can be set for users, and as shown, manages information such as "name" and "genre type" that identifies the corresponding (classified) genre in association with a "topic tag ID" that identifies an individual topic tag. In this example, topic tag genres include "anime / manga," "music," and "games."

[0061] 8 illustrates information managed by the topic tag match status management table 1515 in this example. The topic tag match status management table 1515 manages the match status of topic tags between two users, and as shown, manages information such as the "number of matching topic tags" indicating the number of matching topic tags and "matching topic tag information" which is information about the matching topic tags, in association with a combination of a "first user account" that identifies a first user and a "second user account" that identifies a second user. The matching topic tag information includes a topic tag ID that identifies each of one or more topic tags.

[0062] In this example, the topic tag matching status for all combinations of users of the content distribution service is managed in topic tag matching status management table 1515. Specifically, when the topic tag information of any user (managed in user information table 1511) is updated, the topic tag matching status for each combination of that user and all other users is updated.

[0063] The information managed by each table has been explained above. Next, the processing executed by the content distribution server 10 of this example, and the screens output on the user terminal 30 will be explained.

[0064] 9 illustrates an example of a top screen (first screen) 50 of the content distribution service output on the user terminal 30. The screen 50 is the starting point when using the content distribution service, and as shown in the figure, has a selection area 52 displaying the text "Follow," "Popular," "Trending Tags," and "All," a list display area 54 located below the selection area 52, and a circular distribution button 56 located in the upper right corner of the screen.

[0065] The selection area 52 is an area for selecting the content to be displayed (tabs to be displayed) in the list display area 54. Specifically, when "Follow" is selected in the selection area 52, a list of broadcasts (content currently being broadcast) of other users the user is following is displayed in the list display area 54. Similarly, when "Popular" is selected in the selection area 52, a list of broadcasts with a large number of viewing users is displayed in the list display area 54. Furthermore, when "All" is selected in the selection area 52, all broadcasts are subject to list display in the list display area 54. It can also be said that the list display area 54 displays a list of broadcast users currently broadcasting content.

[0066] The top screen 50 in FIG. 9 corresponds to the case where "Popular" is selected in the selection area 52, and in this state, as shown in the figure, the list display area 54 has a plurality of individual display areas 541 arranged in two columns vertically, each displaying information about an individual broadcast. The individual display areas 541 are configured so that viewing of the corresponding broadcast can be started in response to a user selection (playback of the corresponding content is started). The list display area 54 is configured so that the displayed individual display areas 541 can be switched by a flick operation or a slide operation in an up or down direction. Note that, when "Follow" or "All" is selected in the selection area 52, a plurality of individual display areas 541 are similarly arranged in the list display area 54.

[0067] 10 illustrates an example of the display content of individual display area 541. As shown in the figure, individual display area 541 displays an image preset by the content distribution user, the distribution user's account name, the number of viewing users (current value), etc.

[0068] Furthermore, when "topic tag" is selected in the selection area 52, a list of other users' broadcasts with one or more matching topic tags between the user and the broadcasting user is displayed in the list display area 54. In this case, the more matching topic tags there are between the user and the broadcasting user, the higher the broadcast (content) is placed in the list display area 54. The number of matching topic tags between two users is managed in the topic tag matching status management table 1515, as described above.

[0069] FIG. 11 illustrates the top screen 50 when "topic tag" is selected in the selection area 52. In this state, as shown in the figure, the top screen 50 has a plurality of individual display areas 542 arranged vertically in the list display area 54, each displaying information about an individual broadcast. The individual display area 542 has a shape and size that resembles two individual display areas 541 arranged horizontally combined together. The area 542 is configured so that, in response to a user selection, viewing of the corresponding broadcast can be started (playback of the corresponding content is started). The list display area 54 is configured so that the displayed individual display areas 542 can be switched by a flick operation or a slide operation in the vertical direction, for example.

[0070] 12 illustrates an example of the display contents of individual display area 542. As shown in the figure, individual display area 542, like individual display area 541 described above, displays an image preset by the content distributor user, the distributor user's account name, the number of viewing users (current value), etc., and further includes, on the right side thereof, topic tag information display area 5421 that displays information related to topic tags.

[0071] Topic tag objects 5422 corresponding to one or more topic tags (identified by referencing topic tag information in user information table 1511) set for the corresponding distribution user are arranged vertically in topic tag information display area 5421. In this example, the number of topic tags that can be set for one user is five, and therefore, a maximum of five topic tag objects 5422 are arranged vertically in topic tag information display area 5421. Topic tag object 5422 displays the content of the corresponding topic tag.

[0072] In addition, in the topic tag information display area 5421, the topic tag object 5422A corresponding to the topic tag (topic tag common between the user and the distributor user) also set for the corresponding user (the user operating the user terminal 30 on which the top screen 50 is displayed) has a different appearance (for example, background color, etc.) from the topic tag object 5422B corresponding to the topic tag not set for the user. Furthermore, in the topic tag information display area 5421, the topic tag object 5422A corresponding to the topic tag also set for the corresponding user is preferentially arranged higher than the topic tag object 5422B corresponding to the topic tag not set for the user. The user can easily recognize the topic tag common to the user himself / herself from the position and appearance of the topic tag object 5422.

[0073] In another example of this embodiment, when there are multiple common topic tags, topic tag objects 5422A corresponding to topic tags that are set less frequently across the entire content distribution service (which can also be called niche topic tags) are preferentially arranged higher in the topic tag information display area 5421. Furthermore, the display of topic tag objects 5422 corresponding to topic tags whose set frequency is less than a threshold may be changed (for example, by adding a corresponding image or text, etc.).

[0074] 13 illustrates an example of the top screen 50 when "topic tag" is selected in the selection area 52, but no topic tag has been set for the corresponding user. In this state, the top screen 50 displays the text "No tags set" in the list display area 54, and also displays a tag setting button 543. The text "Set tag" is added to the button 543.

[0075] When the tag setting button 543 is selected, the topic tag setting screen 200 shown in Fig. 14 is output. The tag setting button 543 can also be said to be an object to which a link to the topic tag setting screen 200 is set. In this example, the topic tag setting screen 200 is output via various other screens, etc.

[0076] The topic tag setting screen 200 is a screen for setting topic tags for the user himself, and as shown in the figure, has a selection area 202, a list display area 204 located below the area 202 and displaying a list of topic tags to be set, a setting information display area 206 displaying the topic tags that have been set, and a done button 208. Between the list display area 204 and the setting information display area 206, the setting status of the topic tags is displayed; specifically, the number of topic tags that have been set (selected) and the number of topic tags that can be set (specifically, the upper limit of 5) are displayed in fractional form.

[0077] The selection area 202 is an area for selecting the content to be displayed in the list display area 204, and displays genres of topic tags such as "anime / manga," "music," and "games," for example. When a genre is selected in the selection area 202, the corresponding topic tags (classified into that genre) are displayed in a list in the list display area 204. The topic tags corresponding to each genre are identified by referencing the genre type in the topic tag information table 1514. In the list display area 204, the topic tags displayed can be switched by flicking or sliding vertically.

[0078] In the setting information display area 206, one or more tag objects 2061 corresponding to set topic tags (managed in the topic tag information of the user information table 1511) are arranged side by side in the horizontal direction. In the setting information display area 206, the tag objects 2061 displayed are switched by a left / right flick operation, a slide operation, or the like. When a new (unset) topic tag is selected via the list display area 204 while the number of set topic tags is less than the upper limit, a corresponding tag object 2061 is newly added in the setting information display area 206. A cancel object 2062 is arranged on the right end of the tag object 2061, and when the object 2062 is selected, the setting of the corresponding topic tag is canceled.

[0079] When the done button 208 is selected, the topic tag setting is updated, and specifically, the topic tag information of the corresponding user is updated in the user information table 1511.

[0080] 15 illustrates an example of the top screen 50 when "topic tag" is selected in the selection area 52, one or more topic tags are set for the corresponding user, but no broadcasts have been made by broadcasters with a common topic tag. In this state, the top screen 50 displays the text "No broadcasts with matching tags" in the list display area 54, as shown, along with a tag-matching broadcaster display button 544. Added to the button 544 is the text "View broadcasters with matching tags."

[0081] When the tag-matching broadcaster user display button 544 is selected, a tag-matching broadcaster user list screen 210 (second screen) as shown in FIG. 16 is output. This screen 210 is a screen for displaying broadcast users who have a common topic tag set with the corresponding user (the user operating the user terminal 30 on which this screen 210 is output), and as shown in the figure, has a list display area 212. In the list display area 212, multiple individual display areas 2121, each corresponding to an individual broadcast user, are arranged vertically. In the list display area 212, the displayed individual display areas 2121 are switched by a flick operation or slide operation in an up or down direction, etc. The list display area 212 displays, as target broadcast users, users who have a common topic tag set with the corresponding user and whose rank as a broadcast user is equal to or higher than a threshold value (e.g., "C1"). In the list display area 212, the more topic tags a broadcast user has that match with the corresponding user, the higher they are placed. As described above, the number of matching topic tags between two users is managed in the topic tag matching status management table 1515. Note that the broadcast users displayed in the list display area 212 may be filtered by scheduled broadcast date, etc.

[0082] 17 shows an example of the display content of individual display area 2121. As shown in the figure, individual display area 2121 displays the broadcasting user's profile picture, account name, etc., as well as having topic tag information display area 2122 that displays information related to the set topic tag, and follow button 2123. When follow button 2123 is selected, the corresponding broadcasting user is registered as a following user, and specifically, the following user information of the corresponding user is updated in user information table 1511.

[0083] The topic tag information display area 2122 displays one or more topic tags set for the corresponding distribution user, separated by a " / " (slash). Similar to the topic tag information display area 5421 described above, in the topic tag information display area 2122, the topic tags set for the corresponding user and the topic tags not set for that user have different appearances (e.g., background color, etc.). Furthermore, in the topic tag information display area 2122, the topic tags set for the corresponding user are preferentially arranged higher than the topic tags not set for that user. The user can easily recognize the topic tags common to the user himself or herself based on the position and appearance of the topic tags displayed in the topic tag information display area 2122.

[0084] The distribution button 56 on the top screen 50 is an object that allows the user to distribute content as a distributor user. When the distribution button 56 is selected by the user, a distribution preparation screen 60, as shown in FIG. 18, is output. As shown, the distribution preparation screen 60 has a distribution title input area 62 for inputting a distribution title, a secret distribution setting switch 64 for setting secret distribution mode, a post setting button 66 for setting the posts (posting messages to SNS) that are automatically made during distribution, and a distribution start button 68 with the text "Start!" added. Secret distribution is a content distribution mode that can only be viewed by new viewing users (specifically, viewing users whose total viewing time over a certain period of time for the corresponding distributor user is less than a predetermined value).

[0085] When distribution start button 68 is selected, distribution of the content begins, and specifically, operation data indicating head movements and facial expression changes of the broadcast user recognized via the camera of broadcast terminal 30, and voice data (voice data of the broadcast user) input via the microphone of broadcast terminal 30, begin to be transmitted to server 10. In addition, in response to the start of content distribution, a new record is inserted in distribution management table 1512.

[0086] 19 illustrates a distribution screen 70 that is output on distribution terminal 30 in response to the start of content distribution. As shown in the figure, screen 70 has a video display area 71 that covers the entire screen, a basic information display area 72 located in the upper left corner of the screen, a comment display area 73 located in the lower left corner of the screen, a viewer information display area 75 located in the upper right corner of the screen, and a circular distribution stop button 76 located in the center of the bottom edge of the screen.

[0087] The video display area 71 displays the content to be distributed. Specifically, a video including a character whose eyes and mouth move based on the above-mentioned motion data based on the head movements and facial expression changes of the distribution user and the character's model data is displayed. The video is generated and output by the distribution terminal 30.

[0088] The basic information display area 72 displays basic information about this broadcast, specifically, broadcast user information (profile image, etc.), the number of viewing users of this broadcast (current value), and the number of "likes" entered by viewing users for this broadcast.

[0089] The comment display area 73 is an area for displaying user comments input by each viewing user and system comments automatically input by the server 10. Specifically, in this area 73, a plurality of comment objects 731, each corresponding to an individual comment, are arranged vertically. The comment display area 73 is configured such that when a new comment is input, a corresponding comment object 731 is added to the bottom, and the existing comment objects 731 move sequentially upward. In the comment display area 73, the comment objects 731 displayed are switched by a flick operation or a slide operation in the vertical direction, for example.

[0090] The viewing user information display area 75 displays information about multiple viewing users who are viewing the content being distributed. Specifically, multiple icon objects 751, each corresponding to an individual viewing user, are arranged side by side in the horizontal direction in this area 75. Each object 751 has a circular shape and displays a profile image of the corresponding viewing user. The multiple icon objects 751 are arranged in an order that follows a predetermined rule (for example, in descending order of the number of coins consumed in the current month).

[0091] The distribution stop button 76 is an object that allows the distribution user to stop distribution of content. When the distribution stop button 76 is selected by the distribution user, distribution of the content (transmission of motion data and audio data from the distribution terminal 30 to the server 10) is stopped.

[0092] 20 illustrates a viewing screen 80 output on the viewing terminal 30. For example, when a viewing user selects an arbitrary distribution (content) via the list display area 54 of the top screen 50, a viewing screen 80 for viewing the selected distribution is output on the viewing terminal 30. As shown in the figure, the screen 80 has a video display area 81, a basic information display area 82, a comment display area 83, and a viewing user information display area 85, similar to the distribution screen 70 described above. Furthermore, the viewing screen 80 has, at the bottom of the screen, a comment input area 862, a "Like" button 863 with a heart mark, and a gift input button 864 with a gift design.

[0093] The video display area 81 displays a video including the broadcasting user's character, similar to the video display area 71 of the broadcasting screen 70. The video is generated and output in the viewing terminal 30 based on the action data transmitted from the broadcasting terminal 30 via the server 10, and the character model data downloaded from the server 10, etc.

[0094] The comment input area 862 is an area for viewing users to input comments. Specifically, when a character string is input into the comment input area 862 and a confirmation operation is performed, the character string is transmitted as a user comment, and comment objects 731, 831 corresponding to the user comment are added to the comment display areas 73, 83 of the distribution screen 70 and viewing screen 80 at the corresponding distribution terminal 30 (the user terminal 30 of the distribution user who distributes the content being viewed) and at each viewing terminal 30 (the user terminal 30 of each of multiple viewing users who view the same content). The comment objects 731, 831 corresponding to the user comment display the content of the comment (character string) together with the account name of the viewing user who input the comment. Furthermore, when a user comment is input, the server 10 updates (adds 1 to) the number of comments for the corresponding distribution in the distribution management table 1512.

[0095] The like button 863 is an object that allows the viewing user to input a "like" for the broadcasting user (or content). When the button 863 is selected by the viewing user, a "like" is input, and a comment object 731, 831 corresponding to a system comment notifying the input of a "like" is added to the comment display area 73, 83 of the corresponding broadcasting screen 70 and viewing screen 80. In the comment object 731, 831 corresponding to the system comment, text indicating the input of a "like" is displayed together with the account name of the viewing user who input a "like." Furthermore, when a "like" is input, a corresponding effect display (for example, the display of an animated video effect in which a heart-shaped object is displayed flowing from the bottom to the top of the screen) is performed in the video display area 71, 81 of the broadcasting screen 70 and viewing screen 80. Furthermore, when a "like" is input, the server 10 updates (adds 1 to) the "number of likes" for the corresponding broadcast in the broadcast management table 1512.

[0096] The gift input button 864 is an object for the viewing user to input a gift item. When the button 864 is selected, a gift selection screen 90 for selecting the gift item to input is displayed superimposed on the lower area of ​​the viewing screen 80, as shown in FIG.

[0097] 22 illustrates a gift selection screen 90. As shown in the figure, the screen 90 has a selection area 91, a list display area 94 located below the area 91 and displaying a list of one or more gift items, a price range selection area 96 located below the area 94 for selecting the price range of the gift items to be displayed, and a purchase button 97 located in the lower right corner of the screen as an object for purchasing coins. In addition, the number of coins owned by the corresponding user is displayed in the lower left corner of the gift selection screen 90.

[0098] The selection area 91 is an area for selecting (filtering) the content to be displayed in the list display area 94, and displays text such as "All," "History," "Popular," and "Limited Time Offer." When "All" is selected in the selection area 91, all gift items are displayed in a list in the list display area 94. When "History" is selected in the selection area 91, gift items previously entered by the corresponding user are displayed in a list in the list display area 94. When "Popular" is selected, gift items with a high number of entries across the entire content distribution service are displayed in a list in the list display area 94. When "Limited Time Offer" is selected, gift items that are offered for a limited time and that can be entered at that time (for example, gift items that can be entered for a limited-time event within the content distribution service) are displayed in a list.

[0099] In the list display area 94, a plurality of individual display areas 941, each displaying information about an individual gift item, are arranged in four columns in the vertical direction. The individual display areas 941 display an image corresponding to the gift item and the number of coins (price) required to input that item. The list display area 94 is configured so that the displayed individual display areas 941 can be switched by a flick operation or a slide operation in the vertical direction, for example. When a viewing user selects one of the individual display areas 941, the corresponding gift item is input.

[0100] The price range selection area 96 is an area for further selecting (filtering) the display content in the list display area 94 by the price range of the gift items. When a price range is selected in the price range selection area 96, gift items in the corresponding price range are displayed in the list display area 94.

[0101] When a gift item is input, a comment object 731, 831 corresponding to a system comment notifying the input of the gift item is added to the comment display area 73, 83 of the corresponding distribution screen 70 and viewing screen 80. The comment object 731, 831 corresponding to the system comment displays the name of the input gift item together with the account name of the viewing user who input the gift item. Furthermore, when a gift item is input, a visual effect corresponding to the input gift item is displayed in the video display area 71, 81 of the corresponding distribution screen 70 and viewing screen 80. The visual effect display includes the display of an image and video effects corresponding to the input gift item.

[0102] In addition, when a gift item is input, the server 10 subtracts the number of coins for the input gift item from the number of coins held by the corresponding user (the viewing user who input the gift item) in the user information table 1511, and adds the number of coins to the number of coins consumed for the corresponding distribution in the distribution management table 1512.

[0103] In this example, the input of gift items may be controlled based on the degree of matching of topic tags between the viewing user and the broadcasting user. For example, the greater the number of matching topic tags between the viewing user and the broadcasting user, the lower the price of the gift item for that viewing user. Furthermore, the lower the frequency with which matching topic tags are set across the entire content distribution service, the lower the price. Also, for example, a particular gift item may be inputtable by viewing users who share a common topic tag with the broadcasting user, but not inputtable by viewing users who do not share a common topic tag. Conversely, for example, a particular gift item may be inputtable by viewing users who do not share a common topic tag with the broadcasting user, but not inputtable by viewing users who share a common topic tag.

[0104] In this example, the number of support points in the distribution management table 1512 is updated in real time while the content is being distributed. In this example, the number of support points is calculated based on the number of likes, the number of comments, and the number of coins consumed, and the larger these values ​​are, the larger the number of support points will be. When the distribution user selects the distribution stop button 76 on the distribution screen 70, the distribution of the content ends.

[0105] Here, the process for determining a broadcast user's rank will be described. In this example, the rank for the day is determined (updated) based on the number of support points the user earned as a broadcast user on the previous day. FIG. 23 is a flowchart illustrating the process executed by server 10 when updating each user's rank. This process is executed late at night (e.g., 3:00 AM) every day.

[0106] As shown in the figure, the server 10 first calculates the number of support points that each user earned as a broadcast user on the previous day (step S100). The number of support points that each user earned on the previous day is calculated by referencing the broadcast user account, broadcast start date and time, and number of support points in the broadcast management table 1512. Note that if a user broadcasts multiple times in one day, the number of support points earned for each of the multiple broadcasts is added together.

[0107] After calculating the number of support points for each broadcast user on the previous day in this manner, the server 10 then updates the rank meter value for each user (step S110). FIG. 24 illustrates an example of a rule for updating the rank meter value. As shown in the figure, in this example, the rank meter value fluctuates based on the ranking of each user's number of support points for the previous day within the rank band to which that user belongs. The initial value of the rank meter value is "0."

[0108] Specifically, the update rule for the rank meter value is as follows: first, if the ranking in the number of support points within the rank band is in the top 10%, the rank meter value will fluctuate by "+2" (an increase of 2 points). Similarly, if the ranking is in the top 11 to 30% (the remaining 20% ​​after excluding the top 10% from the top 30%), the fluctuate will be "+1", if the ranking is in the middle 30% (the top 31 to 60%), the fluctuate will be "±0" (no increase or decrease), and if the ranking is in the bottom 40%, the fluctuate will be "-1" (a decrease of 1 point). Note that if no broadcast was made on the previous day, the fluctuate of the rank meter value will be "-1" regardless of the ranking within the rank band. In step S110, the rank meter value of each user is updated in the user information table 1511 according to the update rule illustrated in FIG. 24.

[0109] Returning to the flowchart of FIG. 23, once the rank meter value of each user has been updated, the server 10 then updates the rank based on the updated rank meter value (step S120). In this example, the rank meter value required to rank up is +3, and the rank meter value required to rank down is -3. When the rank meter value reaches these values, the user is ranked up / down. The rank meter value of the user whose rank has been updated (the user whose rank has been upgraded or downgraded) is cleared to 0. Note that in another example of this embodiment, in order to prevent a sudden rank upgrade / downgrade in a short period of time, for example, in the case of a rank upgrade / downgrade across rank bands, the absolute value of the required rank meter value may be made larger (for example, +6 or -6) compared to a rank upgrade / downgrade within the same rank band.

[0110] The above describes the processing when determining the broadcast user's rank. Next, the processing when granting diamonds to the broadcast user will be described. In this example, diamonds, which are one of the rewards, are granted to the broadcast user based on the broadcast time of the previous day and the rank on the previous day. Figure 25 is a flowchart illustrating the processing executed by server 10 when granting diamonds to each user. These processes are executed late at night every day, and are executed, for example, at a time (e.g., midnight) earlier than the processing executed when updating each user's rank as illustrated in Figure 23.

[0111] As shown in the figure, the server 10 first calculates the broadcast time of each user on the previous day (step S200). Specifically, the broadcast time of each user on the previous day is calculated by referring to the broadcast user account, broadcast start date and time, and broadcast duration in the broadcast management table 1512. If a user broadcasts multiple times in one day, the broadcast durations of each of the multiple broadcasts are added together.

[0112] Next, the server 10 grants each user a number of diamonds based on the calculated distribution time and the standard number of diamonds (step S210). Specifically, each user is granted a number of diamonds calculated by multiplying the calculated distribution time by the standard number of diamonds. The standard number of diamonds is preset for each rank so that the higher the rank, the greater the number, and the standard number of diamonds corresponding to each user's rank on the previous day is applied. When diamonds are granted to a user, the number of diamonds held by the corresponding user is updated in the user information table 1511. In this example, diamonds can be exchanged for coins or real currency.

[0113] In the above example, the matching status of topic tags between a viewing user who has started viewing content and a distributor user may be displayed on distribution screen 70 and viewing screen 80. For example, when a viewing user starts viewing content, if a common topic tag is set between the viewing user and the distributor user, comment objects 731, 831 corresponding to a system comment notifying the common topic tag may be added to comment display areas 73, 83 on distribution screen 70 and viewing screen 80. In this case, the viewing users who are the targets of such notification may be limited to viewing users who satisfy certain conditions (for example, first-time users who have viewed content distributed by the corresponding distributor user for the first time).

[0114] In the above example, when "topic tag" is selected in selection area 52 but no topic tag is set for the corresponding user, tag setting button 543 is arranged in list display area 54 of top screen 50. However, in other cases, tag setting button 543 may also be arranged in list display area 54. In this case, for example, reduced tag setting button 543 may be arranged at the bottom of multiple individual display areas 542 displayed in list display area 54.

[0115] In the above example, topic tags are used as attribute values ​​set for users, but in other examples of this embodiment, various information other than topic tags is applied as the attribute values.

[0116] In the above example, the display manner of comment objects 731, 831 may be determined based on the degree of similarity between the topic tags of the viewing user and the distributor user. For example, a user comment or system comment regarding a given viewing user is displayed in a first background color if there is a common topic tag between the viewing user and the distributor user, and is displayed in a second background color if there is no common topic tag between the viewing user and the distributor user.

[0117] The content distribution server 10 of the present embodiment described above presents a screen (e.g., top screen 50, etc.) that lists multiple distribution users to the viewing user, and this screen displays multiple attribute values ​​(e.g., topic tags, etc.) set for each distribution user in a manner that makes it possible to distinguish between attribute values ​​set for that viewing user and attribute values ​​not set for that viewing user (e.g., topic tag objects 5422 have different appearances, etc.), allowing the viewing user to know the attribute values ​​of each distribution user that include attribute values ​​in common with the viewing user, which helps the viewing user find a suitable distribution user (and content provided by that distribution user). In other words, server 10 helps make it easy to find content to view.

[0118] In other embodiments of the present invention, some or all of the functions of the content distribution server 10 in the above-described embodiments may be realized by cooperation between the server 10 and the user terminal 30, or may be realized by the user terminal 30. In other words, the system (or device) of the present invention may be configured not only by the content distribution server 10, but also by the content distribution server 10 and the user terminal 30, or may be configured by the user terminal 30.

[0119] The processes and procedures described herein, other than those explicitly described, may be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, and magnetic disks. The processes and procedures described herein may also be implemented as computer programs corresponding to the processes and procedures and executed by various computers.

[0120] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be implemented by combining them into fewer components or breaking them down into more components. [Explanation of symbols]

[0121] 10 Content distribution server 11. Computer Processor 111 Management function control section 112 Service provision control unit 15 Storage 151 various tables 1511 User Information Table 1512 Delivery Management Table 1513 Viewing user management table by distribution user 1514 Topic Tag Information Table 1515 Topic tag matching status management table 20. Communication Networks 30 User terminals 40 Server-side programs 42 Terminal side program 50 Top screen 60 Distribution preparation screen 70 Streaming Screen 80 viewing screen 90 Gift selection screen 200 Topic tag setting screen 210 Tag matching delivery user list screen

Claims

1. A system for providing a content distribution service that allows content to be distributed and viewed, the system comprising one or more computer processors, the one or more computer processors: setting a plurality of attribute values ​​for each of a plurality of users; presenting a first screen displaying a list of the first plurality of distribution users to the viewing user; the first screen displays a plurality of attribute values ​​set to each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set to the viewing user and attribute values ​​not set to the viewing user; system.

2. the first screen displays a plurality of attribute values ​​set for each of the first plurality of distribution users in such a manner that the attribute values ​​set for the viewing user have priority; The system of claim 1.

3. the first screen displays a list of first users currently distributing the content as the first plurality of distribution users; The system of claim 1.

4. the first screen displays a list of first users who are currently distributing the content and who have at least one attribute value that matches that of the viewing user, as the first plurality of distribution users; The system of claim 1.

5. the one or more computer processors further execute a step of presenting to the viewing user a second screen displaying a list of second users having at least one attribute value matching that of the viewing user as a second plurality of broadcast users; The system of claim 4.

6. the first screen displays a link to the second screen; The system of claim 5.

7. The first screen displays the link in a different manner depending on whether or not the first user is present. The system of claim 6.

8. a display size of the link on the first screen is smaller when the first user is present than when the first user is not present; The system of claim 7.

9. the second screen displays a list of the second users who have at least one attribute value that matches that of the viewing user and who satisfy a condition related to a distribution record of the content, as the second plurality of distribution users. The system of claim 5.

10. the first screen displays a list of the first plurality of distribution users such that higher degrees of match between the set attribute values ​​and the viewing users are given priority; The system of claim 1.

11. the first screen displays a plurality of attribute values ​​set for each of the first plurality of distribution users in such a manner that attribute values ​​whose setting frequency in the content distribution service is equal to or greater than a threshold value and attribute values ​​whose setting frequency is less than the threshold value can be distinguished. The system of claim 1.

12. the step of setting the plurality of attribute values ​​includes setting the plurality of attribute values ​​selected by each of the plurality of users from a plurality of predetermined attribute values ​​for each of the plurality of users; The system of claim 1.

13. the attribute values ​​are the user's preferences; The system of claim 1.

14. 1. A method executed by one or more computers for providing a content distribution service that enables content distribution and viewing, comprising: setting a plurality of attribute values ​​for each of a plurality of users; presenting a first screen displaying a list of the first plurality of broadcast users to the viewing user; the first screen displays a plurality of attribute values ​​set to each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set to the viewing user and attribute values ​​not set to the viewing user; method.

15. A program for providing a content distribution service that allows content to be distributed and viewed, the program comprising: setting a plurality of attribute values ​​for each of a plurality of users; presenting a first screen displaying a list of the first plurality of broadcast users to the viewing user; the first screen displays a plurality of attribute values ​​set to each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set to the viewing user and attribute values ​​not set to the viewing user; program.

16. A device for providing a content distribution service that allows content to be distributed and viewed, means for setting a plurality of attribute values ​​for each of a plurality of users; means for presenting a first screen displaying a list of a first plurality of broadcast users to a viewing user; the first screen displays a plurality of attribute values ​​set to each of the first plurality of distribution users in a manner that makes it possible to distinguish between attribute values ​​set to the viewing user and attribute values ​​not set to the viewing user; Device.

Images