System, method, and program for generating content

Abstract

To support content generation taking the relationship between users into consideration.SOLUTION: A moving image distribution server 10 according to one embodiment of the present invention is communicably connected to a user terminal 30 via a communication network 20, and provides a user with a moving image distribution service for distributing and viewing moving images via the user terminal 30. Since the server 10 generates message content including a plurality of messages to a distributor entered by a viewer based on a value of a relationship parameter relating to relationship between the viewer and the distributor, the generated message content takes the relationship between the viewer and the distributor into consideration.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a system, method, and program for generating content including multiple messages. [Background technology]

[0002] Conventionally, various services have been provided for generating content containing multiple messages. For example, the following Patent Documents 1 to 3 disclose systems for electronically generating a message book containing multiple messages from multiple participants. Such systems promote efficient generation of message books and improvement of the quality of the generated message books. In addition, such content such as message books can be used as a communication tool between owners (artists, creators, influencers, etc.) and participants (fans, etc.) in community services. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-297051 A [Patent Document 2] JP 2015-133000 A [Patent Document 3] JP 2017-138799 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned conventional systems do not take into account the characteristics of community services, and it may be difficult to apply them as they are as communication tools in such services. For example, conventional systems do not fully consider the relationship between the recipient of the message book (e.g., the community owner) and the participants who participate in the message book (e.g., the participants in the community).

[0005] One of the objects of the embodiment of the present invention is to support the generation of content that takes into account relationships between users. Other objects of the embodiment of the present invention will become apparent by referring to the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system for generating content including a plurality of messages, comprising one or more computer processors, wherein the one or more computer processors execute, in response to execution of readable instructions, a process of managing values ​​of predetermined parameters relating to a relationship with a first user, the predetermined parameters being associated with each of a plurality of second users, and a process of generating predetermined content including a plurality of messages for the first user input by at least some of the plurality of second users, wherein the process of generating the predetermined content includes generating the predetermined content based at least on values ​​of the predetermined parameters of at least some of the plurality of second users.

[0007] A method according to one embodiment of the present invention is a method executed by one or more computers for generating content including a plurality of messages, comprising the steps of: managing values ​​of predetermined parameters relating to relationships with a first user, the predetermined parameters being associated with each of a plurality of second users; and generating predetermined content including a plurality of messages to the first user input by at least some of the plurality of second users, wherein the step of generating the predetermined content includes generating the predetermined content based at least on values ​​of the predetermined parameters of at least some of the plurality of second users.

[0008] A program according to one embodiment of the present invention is a program for generating content including multiple messages, which causes one or more computers to execute a process of managing values ​​of predetermined parameters related to a relationship with a first user, the predetermined parameters being associated with each of multiple second users, and a process of generating predetermined content including multiple messages to the first user input by at least some of the multiple second users, wherein the process of generating the predetermined content includes generating the predetermined content based at least on the values ​​of the predetermined parameters of at least some of the multiple second users. Effect of the Invention

[0009] Various embodiments of the present invention support the generation of content that takes into account relationships between users. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a schematic configuration of a network including a video distribution server 10 according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing the functions of a video distribution server 10. [Diagram 3] 4 is a diagram illustrating an example of information managed in a user information table 411. [Figure 4] FIG. 13 is a diagram for explaining ranks. [Diagram 5] 4 is a diagram illustrating an example of information managed in a distribution management table 412. [Figure 6] 4 is a diagram illustrating an example of information managed in a relationship parameter management table 413. [Figure 7] FIG. 4 is a diagram illustrating an example of information managed in a content information table 414. [Figure 8] FIG. 11 is a diagram illustrating examples of types of messages and corresponding schedules. [Figure 9] 4 is a diagram illustrating an example of information managed in a message management table 415. [Figure 10] FIG. 4 is a diagram illustrating a top screen 60. [Figure 11] FIG. 13 is a diagram showing an example of the display content of an individual display area 641. [Figure 12] FIG. 13 is a diagram illustrating a top screen 60 when "Topic" is selected in a selection area 62. [Figure 13] FIG. 13 is a diagram showing an example of the display content of an individual display area 642. [Figure 14] FIG. 1 is a diagram illustrating a distribution preparation screen 100. [Figure 15] FIG. 7 is a diagram illustrating a distributor screen 70. [Figure 16] FIG. 13 is a diagram illustrating a viewer screen 80. [Figure 17] FIG. 2 is a diagram illustrating an example of an item selection screen 200. [Figure 18] FIG. 4 is a diagram for explaining each condition of a plurality of fan levels. [Figure 19] 4 is a flow diagram illustrating a process executed by the server 10 when updating a rank. [Figure 20] FIG. 13 is a diagram illustrating the correspondence between the number of special fans and a distribution point bonus (multiplier). [Figure 21] FIG. 4 is a diagram for explaining an update rule for a rank meter value. [Figure 22] 11 is a diagram for explaining the correspondence between update contents of rank and required rank meter value. [Figure 23] FIG. 4 is a flow diagram illustrating a process executed by the server 10 when awarding diamonds. [Figure 24] FIG. 3 is a diagram illustrating a fan letter screen 300. [Diagram 25] FIG. 5 is a diagram illustrating a message editing screen 500. [Figure 26] FIG. 6 is a diagram illustrating a preview screen 600. [Figure 27] FIG. 13 is a diagram illustrating a fan letter screen 300 in a state where a message has been made public. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] FIG. 1 is a diagram showing a schematic configuration of a network including a video distribution server 10 according to an embodiment of the present invention. As shown in the figure, the video distribution 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 shown in FIG. 1, the server 10 is communicably connected to a plurality of user terminals 30. The server 10 provides a video distribution service for distributing and viewing videos to a user via the user terminal 30. In this embodiment, a user who operates the user terminal 30 can distribute videos as a distributor, and can also view videos of other users as a viewer. The video distribution server 10 is an example of a device that implements a part or all of the system of the present invention, and has a function for generating content including a plurality of messages.

[0013] First, we will explain the hardware configuration of the video distribution server 10. The video distribution server 10 is configured as a general computer, and as shown in Fig. 1, 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 (not shown) or the like.

[0014] 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.

[0015] 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, an information input device such as a keyboard, 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 13 also includes an image output device such as a display, and an audio output device such as a speaker.

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

[0017] The storage 15 is configured by, for example, a magnetic disk, a flash memory, etc. The storage 15 stores various programs including an operating system, various data, and the like.

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

[0019] The video distribution server 10 thus configured can be configured to have the functions of a web server and an application server, in which case it executes various processes in response to requests from a web browser and other applications (e.g., applications for video distribution services) installed in the user terminal 30, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the user terminal 30. The user terminal 30 can display a web page or other screen based on the received data.

[0020] Next, a description will be given of the hardware configuration of the user terminal 30. The user terminal 30 is configured as a general computer, and as shown in Fig. 1, 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).

[0021] 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 a 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.

[0022] 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, an information input device such as a keyboard or 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.

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

[0024] The storage 35 is configured by, for example, a magnetic disk or a flash memory, etc. The storage 35 stores various programs including an operating system, various data, etc. The programs stored in the storage 35 can be downloaded from an application market, etc., and installed.

[0025] 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.

[0026] A user operating a user terminal 30 configured in this manner can use the video distribution service provided by the server 10 by communicating with the video distribution server 10 via a web browser or other application installed in storage 35, etc.

[0027] Next, the functions of the video distribution server 10 thus configured will be described. FIG. 2 is a block diagram showing the functions of the video distribution server 10. As shown in the figure, the server 10 has an information storage management unit 41 that stores and manages various information, a management function control unit 43 that controls the management function of the video distribution service, a video distribution service control unit 45 that controls the video distribution service, and a content generation control unit 47 that controls the generation of message content (predetermined content) including a plurality of messages. These functions are realized by the cooperation of hardware such as the computer processor 11 and the main memory 12, and various programs and data stored in the storage 15, etc., and are realized, for example, by the computer processor 11 executing instructions included in a program loaded into the main memory 12. In addition, some or all of the functions of the server 10 shown in FIG. 2 can be realized by the cooperation of the server 10 and the user terminal 30, or by the user terminal 30.

[0028] The information storage management unit 41 is configured to store and manage various information in the storage 15 etc. For example, as shown in Fig. 2, the information storage management unit 41 has a user information table 411 that manages information about users of a video distribution service, a distribution management table 412 that manages information about individual video distributions, a relationship parameter management table 413 that manages information about relationship parameters (predetermined parameters) related to the relationship between a distributor and a viewer, a content information table 414 that manages information about message contents, and a message management table 415 that manages information about individual messages included in the message contents.

[0029] The management function control unit 43 is configured to execute various processes related to the control of the management function of the video distribution service. For example, the management function control unit 43 transmits screen data and control data of various screens related to the management function to the user terminal 30, executes various processes in response to an operation input by a user via the screen displayed 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 43 include, for example, login processing (user authentication), billing control, and management of user accounts.

[0030] The video distribution service control unit 45 is configured to execute various processes related to the control of the video distribution service. For example, the video distribution service control unit 45 is configured to distribute a video provided by a distributor to a plurality of viewers. For example, in the case of real-time distribution (live distribution) of a video, the video distribution service control unit 45 receives a real-time video transmitted from a user terminal 30 of the distributor (hereinafter, sometimes referred to as a "distributor terminal 30") and transmits the video to each user terminal 30 of a plurality of viewers (hereinafter, sometimes referred to as a "viewer terminal 30"). In the viewer terminal 30, the video is displayed (played) on a viewer screen for viewing the video. The real-time video is, for example, composed of an image input via a camera of the distributor terminal 30 and an audio input via a microphone. The real-time video is, for example, composed of an image and an audio output via an application (for example, a game application, etc.) running on the distributor terminal 30. Such live distribution of the video may be performed by a streaming method using a protocol such as HTTP Live Streaming (HLS). Furthermore, the video distribution service control unit 45 can be configured to record videos provided by distributors in the storage 15 or the like, and distribute the videos in response to individual requests from viewers.

[0031] In this embodiment, the video distribution service control unit 45 is configured to manage the value of a relationship parameter related to the relationship with a distributor (first user) and associated with each of a plurality of viewers (second users). The value of the relationship parameter is managed in the relationship parameter management table 413 in association with, for example, a combination of a distributor and a viewer. The relationship parameter may be designed as a parameter indicating, for example, intimacy, friendship, or contribution.

[0032] The content generation control unit 47 is configured to execute various processes related to the control of the generation of message content. In this embodiment, the content generation control unit 47 is configured to generate message content including a plurality of messages to the distributor input by at least some of the plurality of viewers based at least on the value of the relationship parameter of each viewer. The message may be configured as, for example, any one of characters, images (still images or moving images), and sounds, or a combination of these. The message content may be configured as, for example, a "message book."

[0033] In this way, the video distribution server 10 in this embodiment generates message content including multiple messages to a distributor input by a viewer based on the value of a relationship parameter related to the relationship between the viewer and the distributor, so that the generated message content takes into account the relationship between the viewer and the distributor. In this way, the video distribution server 10 supports the generation of content that takes into account the relationship between users.

[0034] In this embodiment, when generating message content, a message from a viewer who has a strong relationship with the distributor may be prioritized. In other words, the content generation control unit 47 may be configured to generate message content such that a message input by a viewer who has a strong relationship indicated by the value of the relationship parameter is prioritized.

[0035] For example, in a case where the relationship parameter is designed to have a larger value as the relationship becomes stronger, messages from viewers with a larger value of the relationship parameter are prioritized. For example, in a case where the value of the relationship parameter is updated so that the more videos provided by the distributor are viewed, messages from viewers with a larger value of the relationship parameter are prioritized. Also, in a case where the relationship parameter is designed to have a smaller value as the relationship becomes stronger, messages from viewers with a smaller value of the relationship parameter are prioritized. Such a configuration makes it possible to generate content that prioritizes messages from viewers who have a stronger relationship with the distributor. As a result, it may be possible to encourage viewers to strengthen their relationships with the distributor.

[0036] In this embodiment, the priority of messages from viewers who have a strong relationship with the distributor can be realized in various ways. For example, the content generation control unit 47 can be configured to accept input of messages from viewers whose relationship parameter values ​​are within a predetermined range (e.g., a predetermined value or more), while not accepting input of messages from viewers whose relationship parameter values ​​are outside the predetermined range (e.g., less than a predetermined value). For example, messages from viewers are input via a screen displayed on the viewer terminal 30, and the screen is displayed on the user terminal 30 of the viewer whose relationship parameter value is within the predetermined range, while it is not displayed on the user terminal 30 of the viewer whose relationship parameter value is outside the predetermined range. Such a configuration enables the generation of content that includes only messages from viewers who have a strong relationship.

[0037] Furthermore, for example, the content generation control unit 47 may be configured to generate message content so that the amount of information (e.g., the number of characters, data capacity, or data size, etc.) of a message input by a viewer having a strong relationship indicated by the value of the relationship parameter is increased. For example, the upper limit of the amount of information of a message input by a viewer having a first value of the relationship parameter is set to a first quantity, while the upper limit of the amount of information of a message input by a viewer having a second value of the relationship parameter indicating a stronger relationship than the first value is set to a second quantity larger than the first quantity. Such a configuration enables the generation of content with a large amount of information of messages from viewers having a strong relationship.

[0038] Also, for example, the content generation control unit 47 may be configured to generate message content such that a message input by a viewer with a strong relationship indicated by the value of the relationship parameter is preferentially arranged. For example, a message input by a viewer with a strong relationship is arranged so as to be prominent in the content. For example, the message content is configured as an image or a page on which a plurality of messages are arranged, and a message input by a viewer with a strong relationship is arranged at a prominent position (e.g., at the top or center) of such an image or page and / or at a prominent size (e.g., the size (area) of the message is large). Also, when a message is configured as a video or sound and the message content is generated by combining a plurality of videos or sounds that are successive in time, a message input by a viewer with a strong relationship is arranged at a prominent time position (e.g., at the beginning or end) of such content (combination of videos or sounds). Such a configuration enables the generation of content in which a message from a viewer with a strong relationship is preferentially arranged.

[0039] In this embodiment, the number of messages that can be input by one viewer may be limited. For example, the content generation control unit 47 may be configured to limit the number of messages that can be input by one viewer to within a predetermined value (for example, within a value of 1 or 2 or more). Such a configuration may prevent one viewer from inputting an excessive number of messages.

[0040] In this embodiment, messages from specific viewers may be excluded. For example, the content generation control unit 47 may be configured to generate message content by excluding messages input by viewers who have been set to a predetermined state by the distributor (e.g., blocked viewers). For example, the content generation control unit 47 may be configured not to accept input of messages from viewers who have been set to a predetermined state, or may be configured to ignore the messages (not include them in the content) after accepting input of messages from such viewers. Such a configuration makes it possible to generate content excluding messages from specific viewers.

[0041] Furthermore, the content generation control unit 47 may be configured to present the generated message content at least to the distributor. For example, the message content is presented to the distributor via a screen displayed on the distributor terminal 30. Similarly, the message content may be presented to viewers (for example, limited to viewers who have input a message included in the content, or including viewers who have not input the message).

[0042] In this embodiment, if the number of viewers who have input messages is small, the message content may not be presented to the distributor. In other words, the content generation control unit 47 may be configured to stop presenting the message content to the distributor (for example, to stop creating the content itself, or to stop presenting the generated content, etc.) if the number of viewers who have input messages is equal to or less than a predetermined value. This configuration prevents content consisting of messages from a very small number of viewers from being presented to the distributor.

[0043] The content generation control unit 47 may be configured to start accepting message input by viewers in response to the start of a predetermined period, and generate content including a plurality of messages input by the end of the predetermined period. In this case, for example, the content generation control unit 47 may be configured to prompt viewers who have watched a video during the predetermined period to input a message to a distributor who provides the video. This configuration enables the generation of content including messages input by viewers during a certain period.

[0044] In this embodiment, when the number of viewers who have input messages is large, the message content may be divided and generated. That is, the content generation control unit 47 may be configured to divide and generate the message content when the number of viewers who have input messages is equal to or greater than a predetermined value. For example, the message content is generated by dividing it into a first content consisting of a plurality of messages from a first viewer group among the plurality of viewers who have input messages, and a second content consisting of a plurality of messages from a second viewer group (e.g., a viewer group having a stronger relationship with the distributor than the first viewer group). Also, for example, the message content is generated by dividing it into a first content consisting of a plurality of messages input during a first period, and a second content consisting of a plurality of messages input during a second period after the first period. Such a configuration prevents one piece of content from including an excessive number of messages from viewers.

[0045] Next, a specific example of one aspect of the video distribution server 10 of the present embodiment having such functions will be described. The video distribution service in this example is configured as a live distribution service that allows live distribution of videos composed of images input via the camera of the distributor terminal 30 and audio input via the microphone, and allows the live distribution service to be viewed.

[0046] First, the information managed by each table in this example will be described. Fig. 3 illustrates information managed in the user information table 411 in this example. The user information table 411 manages information about users of the live streaming service, and as shown in the figure, associates the information with a "user account" that identifies an individual user, and manages information such as "basic information" including account name, age, gender, residential area, and profile information, "delivery history information" that is information about the delivery history as a broadcaster, "viewing history information" that is information about the viewing history as a viewer, "following user information" that is information about other users followed by the user, "follower information" that is information about other users (followers) following the user, "blocked user information" that is information about other users blocked by the user, "family information" that is information about families to which the user belongs as a family member, a "rank" that indicates the user's rank as a broadcaster, a "rank meter value" that is a parameter value for determining whether the user has been ranked up or down, "number of coins held" that indicates the number of virtual coins that can be used in the live streaming service, "number of diamonds held" that indicates the number of virtual diamonds held, and "classification text" that is the classification as a broadcaster set by the user himself.

[0047] In this example, a user can set another user to a blocked state (predetermined state), and information (such as a user account) about the user who has been set to the blocked state (blocked) is set in the blocked user information. The actions that a blocked user can take with respect to the live distribution of the corresponding user are restricted, and for example, the user cannot enter comments while watching the live distribution.

[0048] In this example, a family is a community of fans who support a broadcaster, and a user can join in response to an invitation from the broadcaster or a family manager, or in response to approval by the broadcaster or a family manager of a user's application to join. Also, in this example, a maximum number of subscribers to a family is set (e.g., 100 people).

[0049] In this example, coins are given to users for free or for a fee in response to various triggers. For example, a user can obtain coins for free as a reward such as a login bonus. Also, for example, a user can purchase coins for a fee (with real currency).

[0050] FIG. 4 is a diagram for explaining the "rank" of a distributor in this example. As shown in the figure, in this example, there are six rank bands, "S", "A", "B", "C", "D", and "E", and the "S" rank band is made up of six ranks, and each of the four rank bands, "A", "B", "C", and "D", is made up of three ranks (for example, ranks with numbers added to letters indicating rank bands, such as "S1" and "A2"). In addition, the "E" rank band is made up of one rank, "E". In other words, in this example, there are 19 ranks (6+3×4+1=19).

[0051] The rank range is from the highest on the "S" side to the lowest on the "E" side. 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.

[0052] 5 illustrates information managed in the delivery management table 412 in this example. The delivery management table 412 manages information related to individual live delivery (video), and as shown in the figure, manages information such as a "delivery user account" identifying the deliverer, a "delivery start date and time", a "delivery duration" indicating the duration from the start time of the delivery, the number of viewers (current value and maximum value), a "comment count" which is the number of comments entered by the viewers, a "like count" which is the number of "likes" entered by the viewers, a "item point count" which increases according to the input of an item by the viewer, a "delivery point count" which is the points granted for this delivery, and "tag information" which is information related to tags granted for this delivery, in association with a "delivery ID" which identifies each live delivery.

[0053] 6 illustrates information managed in the relationship parameter management table 413 in this example. The relationship parameter management table 413 manages information on the fan level (relationship parameter) of the viewer (by distributor) with respect to the distributor in the target year and month, and as shown in the figure, manages information such as the "fan level" of the viewer with respect to the corresponding distributor in the target year and month, the "number of coins consumed," "viewing time," "number of days viewed," "number of comments entered," and "number of cheer points" (relationship parameters) of the viewer with respect to the live distribution by the distributor in the target year and month, in association with a combination of a "distributor user account" that identifies the distributor, a "viewer user account" that identifies the viewer, and a "target year and month." Thus, in this example, the fan level of the viewer with respect to the distributor is managed on a monthly basis.

[0054] The number of cheer points is calculated using a formula based on the number of coins consumed, viewing time, number of days viewed, and number of comments entered; the greater the value of each of these parameters, the greater the value of the cheer points.

[0055] 7 illustrates information managed in the content information table 414 in this example. The content information table 414 manages information related to a "message message" as the message content in this example, and as shown in the figure, manages information such as a "message acceptance start date and time" which is the date and time when acceptance of input of a message for the message message begins, a "message acceptance end date and time" which is the date and time when acceptance of input of a message for the message message ends, and "design information" which is information related to the design of the background of the message message, etc., in association with a "content ID" which identifies an individual type of message message.

[0056] FIG. 8 illustrates the types of message books provided in this example and the corresponding schedules (the start date and time of acceptance of message input and the end date and time of acceptance). In this example, the live distribution service holds an event four times a year to create message books for the broadcaster, and the message books have designs corresponding to each season. For example, as shown in the figure, types of message books corresponding to spring, summer, autumn, and winter of 2021 are set in advance, and a corresponding schedule is set for each of these message book types. For example, for the message book for "summer 2021", message input acceptance will start on September 15, 2021, and message input acceptance will end on September 30, 2021. Such information is set in the content information table 414.

[0057] 9 illustrates information managed in the message management table 415 in this example. The message management table 415 manages information related to messages for collection of messages input by each viewer, and as shown in the figure, manages information such as "message content" which is the content of the message input by the corresponding viewer as a message for the corresponding distributor as a message for the collection of messages, "character type" which is the type of character that decorates the message on the collection of messages, "confirmed flag" which indicates whether the message has been confirmed, and "confirmed date and time" which is the date and time when the message was confirmed, in association with a combination of a "distributor user account" which identifies the distributor, a "content ID" which identifies the type of message for the corresponding viewer, and a "viewer user account" which identifies the viewer.

[0058] The information managed by each table has been described above. Next, the basic operation of the live streaming service of this example will be described. Fig. 10 illustrates an example of a top screen 60 of the live streaming service displayed on the user terminal 30. The screen 60 is a starting point for users who use the live streaming service, and as shown in the figure, has a selection area 62 displaying "Follow", "Popular", "Trending", and "All", a list display area 64 located below the area 62, and a circular streaming button 66 located in the upper right corner of the screen.

[0059] The selection area 62 is an area for selecting the display contents in the list display area 64. Specifically, when "Follow" is selected in the selection area 62, live broadcasts (videos currently being broadcast) of other users whom the user is following are displayed in a list in the list display area 64. Similarly, when "Popular" is selected in the selection area 62, live broadcasts (for example, broadcasts with a number of viewers (current value) equal to or greater than a threshold value) extracted according to a predetermined extraction condition for extracting popular live broadcasts are displayed in a list in the list display area 64. Furthermore, when "Trending" is selected in the selection area 62, tags attached to live broadcasts are displayed in a chronological order (in the order of attachment time) together with the corresponding broadcasts in the list display area 64. Furthermore, when "All" is selected in the selection area 62, all live broadcasts are subject to list display in the list display area 64.

[0060] The top screen 60 in FIG. 10 corresponds to the case where "Popular" is selected in the selection area 62. In this case, as shown in the figure, the list display area 64 has a plurality of individual display areas 641, each of which displays information about an individual live broadcast, arranged vertically in two columns. The individual display areas 641 are configured so that viewing of the corresponding broadcast can be started (playback of the corresponding video is started) in response to a selection by the user. The list display area 64 is configured so that the displayed individual display areas 641 are switched by a flick operation or a slide operation in the vertical direction. The configuration of the list display area 64 when "Follow" or "All" is selected in the selection area 62 is the same as the above-mentioned configuration when "Popular" is selected.

[0061] 11 illustrates an example of the display contents of the individual display area 641. The individual display area 641 displays an image previously set by the distributor of the live distribution, the distributor's account name, the number of viewers (current value), and the like, and as illustrated, a first tag object 6411 and a second tag object 6412 are arranged side by side in the left-right direction at the bottom end. The first tag object 6411 displays classification text (managed in the user information table 411) that is the classification of the distributor set by the distributor himself / herself in the form of a hashtag (a format in which "#" is added to the beginning of the character string) (in the example of FIG. 11, "#big-eating distribution" is displayed). In addition, the second tag object 6412 displays the latest tag given by the viewer to the corresponding live distribution, also in the form of a hashtag (in the example of FIG. 11, "#curry" is displayed).

[0062] 12 illustrates an example of the top screen 60 when "Topics" is selected in the selection area 62. In this case, as shown in the figure, the top screen 60 displays tags assigned to any live broadcast in chronological order along with the broadcast in the list display area 64. In other words, when "Topics" is selected in the selection area 62, the list display area 64 displays a list of tags arranged in descending order of the time of assignment and the corresponding live broadcasts (broadcasts to which the tags are assigned).

[0063] In this case, a plurality of individual display areas 642, each of which displays an individual tag and information about the corresponding live broadcast, are arranged vertically in the list display area 64. When a new tag is added to any live broadcast, a corresponding individual display area 642 is added to the top of the list display area 64.

[0064] 13 illustrates an example of the display contents of the individual display area 642. As illustrated, the area 642 has a tag object 6421 arranged in the upper left corner, and displays a profile picture and account name of the broadcaster of the corresponding live broadcast (to which the tag is attached), etc. A link to the corresponding live broadcast is set in the individual display area 642, and the user can start viewing the corresponding broadcast by selecting any one of the multiple individual display areas 642 displayed in the list display area 64.

[0065] The broadcast button 66 on the top screen 60 is an object for a user to live broadcast a video as a broadcaster. When the broadcast button 66 is selected by a user, a broadcast preparation screen 100 illustrated in FIG. 14 is displayed superimposed on the top screen 60. As illustrated, the screen 100 has a broadcast title input area 102 for inputting a broadcast title, a secret broadcast setting switch 104 for setting a secret broadcast mode, a tweet setting button 106 for setting tweets (posting messages to SNS) that are automatically made during broadcasting, and a broadcast start button 108 that displays "START!". The secret broadcast is a broadcast mode of live broadcasting that can be viewed only by new viewers (specifically, viewers whose total viewing time for the corresponding broadcaster in a predetermined period is less than a predetermined value).

[0066] When the distribution start button 108 is selected, live distribution is started, and specifically, transmission of a video composed of an image input via the camera of the user terminal 30 and an audio input via the microphone of the user terminal 30 to the server 10 is started. In addition, in response to the start of live distribution, a new record is created in the distribution management table 412.

[0067] 15 illustrates a distributor screen 70 displayed on the distributor terminal 30 in response to selection of the distribution start button 108 (i.e., start of live distribution). As shown in the figure, the screen 70 has a video display area 71 corresponding to 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 tag display area 74 located above the area 73, 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.

[0068] The video display area 71 displays a live-streamed video, that is, an image input via the camera of the distributor terminal 30. The distributor usually captures himself / herself as a subject via the in-camera of the distributor terminal 30, and so the distributed video includes an image of the distributor himself / herself.

[0069] The basic information display area 72 displays basic information about this broadcast, specifically, broadcaster information (profile image, etc.), the number of viewers of this broadcast (current value), and the number of “likes” entered by viewers in response to this broadcast, etc.

[0070] The comment display area 73 is an area for displaying user comments input by a viewer or 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 existing comment objects 731 move in order upward. The comment display area 73 is configured such that the comment objects 731 displayed are switched by an upward or downward flick operation, slide operation, or the like.

[0071] The tag display area 74 displays information related to the tags assigned to this broadcast, and specifically, in this area 74, a plurality of tag objects 741, each of which corresponds to an individual tag, are arranged in the left-right direction.

[0072] The viewer information display area 75 displays information about a plurality of viewers who are viewing the corresponding live broadcast, and specifically, a plurality of icon objects 751, each corresponding to a viewer, are arranged side by side in the left-right direction in the viewer information display area 75. The object 751 has a circular shape and displays a profile image of the corresponding viewer. The plurality of icon objects 751 are arranged in an order that follows a predetermined rule, for example, such that a viewer with a large number of cheer points as described above is arranged on the left side.

[0073] The distribution stop button 76 is an object for the distributor to stop live distribution. When the distributor selects the distribution stop button 76, the live distribution (transmission of the video from the distributor terminal 30 to the server 10) is stopped.

[0074] 16 illustrates a viewer screen 80 displayed on the viewer terminal 30. For example, when a viewer selects a live broadcast via the list display area 64 of the top screen 60, the viewer screen 80 for viewing the selected broadcast is displayed on the viewer 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, a tag display area 84, and a viewer information display area 85, similar to the above-mentioned distributor screen 70. In addition, the viewer screen 80 has, at the bottom of the screen, an input mode switching button 86, a comment input area 87, a "Like" button 88 with a heart mark displayed, and an item input button 89 with a gift design displayed.

[0075] The comment input area 87 is an area for a viewer to input a comment or a tag. While the input mode switching button 86 is not selected, the comment input area 87 is in a normal comment input mode. In the comment input mode, when a transmission object 871 arranged at the right end of the comment input area 87 is selected, the character string input in the area 87 is transmitted as a user comment, and in the corresponding broadcaster terminal 30 (the user terminal 30 of the broadcaster of the live broadcast being viewed) and each viewer terminal 30 (the user terminal 30 of each of the multiple viewers of the live broadcast being viewed), a comment object 731, 831 corresponding to the user comment is added in the comment display area 73, 83 of the broadcaster screen 70 and the viewer screen 80. In the comment object 731, 831 corresponding to the user comment, the content of the comment (character string) is displayed together with the account name of the viewer who input the comment. In addition, when the user comment is transmitted, the server 10 updates (adds 1 to) the number of comments in the corresponding record in the broadcast management table 412. Furthermore, when a user comment is sent, the server 10 updates the number of input comments in the corresponding record in the relationship parameter management table 413 (by adding 1).

[0076] Furthermore, when the input mode switching button 86 is in a selected state, the comment input area 87 enters a tag input mode. In the tag input mode, when a transmission object 871 is selected, the character string input in the comment input area 87 is transmitted as a tag, and the tag is assigned to the live broadcast. In this example, viewers who can input tags are limited to family members of the corresponding broadcaster. Specifically, the input mode switching button 86 on the viewer screen 80 is selectable (enabled) when the viewer is a family member of the broadcaster, whereas it is not selectable (disabled) when the viewer is not a family member of the broadcaster. Also, in this example, the number of tags that can be assigned to one live broadcast in a predetermined period is limited; specifically, the number of tags that can be assigned in a five-minute period is limited to three.

[0077] When a tag is assigned, a corresponding tag object 741, 841 is added in the tag display area 74, 84 of the corresponding distributor screen 70 and viewer screen 80. In the tag display area 74, 84, the tag objects 741, 841 are arranged side by side in the left-right direction so that the tag on the left is newer (added later). Therefore, the tag object 741, 841 corresponding to the newly assigned tag is added to the left end of the tag display area 74, 84. Note that the tag object 741, 841 corresponding to a tag that has been assigned for more than five minutes is deleted (for example, disappears with an animation effect moving to the right).

[0078] In this example, tag objects 741, 841 display the tag content in the form of a hashtag with "#" added to the beginning of the string. For example, if the tag content is "Tokyo sightseeing", then "#Tokyo sightseeing" is displayed in tag objects 741, 841. The horizontal length of tag objects 741, 841 is automatically adjusted according to the length of the string to be displayed.

[0079] In addition, when a tag is added, a comment object 731, 831 corresponding to a system comment notifying the addition of the tag is added to the comment display area 73, 83 of the corresponding distributor screen 70 and viewer screen 80. The comment object 731, 831 corresponding to the system comment displays the content of the added tag along with the account name of the viewer who added (input) the tag, for example, a comment saying "xx tagged the broadcast with "#TokyoSightseeing"." In addition, when a tag is added, the tag information of the corresponding record in the broadcast management table 412 is updated.

[0080] The like button 88 is an object for a viewer to input a "like" to a distributor (live distribution). When the button 88 is selected by a viewer, a "like" is input, and a comment object 731, 831 corresponding to a system comment notifying the input of the "like" is added in the comment display area 73, 83 of the corresponding distributor screen 70 and viewer screen 80. In the comment object 731, 831 corresponding to the system comment, a text indicating the input of the "like" is displayed together with the account name of the viewer who input the "like". In addition, when a "like" is input, a corresponding visual effect (for example, an animation effect in which a heart-shaped object is displayed flowing from the bottom to the top of the screen) is added in the video display area 71, 81 of the distributor screen 70 and the viewer screen 80. In addition, when a "like" is input, the server 10 updates (adds 1) the "number of likes" of the corresponding record in the distribution management table 412.

[0081] The item input button 89 is an object that allows the viewer to input an item. When the button 89 is selected by the viewer, an item selection screen 200, as shown in FIG. 17, is displayed superimposed on the viewer screen 80. As shown in the figure, the screen 200 displays a list of multiple individual display areas 202, each of which displays information related to an item. The individual display areas 202 display an image corresponding to the item and the number of coins required to input the item.

[0082] In this example, a number of items that can be input by the viewer are determined in advance, and a number of coins is set in advance as the price (which can also be called value or compensation) of each item. The item selection screen 200 displays a list of these multiple items that can be input. When a viewer selects one of the items via the item selection screen 200, the selected item is input.

[0083] When an item is input, a comment object 731, 831 corresponding to a system comment notifying the input of the item is added in the comment display area 73, 83 of the corresponding distributor screen 70 and viewer screen 80. The name of the input item is displayed in the comment object 731, 831 corresponding to the system comment together with the account name of the viewer who input the item. When an item is input, a visual effect corresponding to the input item is added in the video display area 71, 81 of the corresponding distributor screen 70 and viewer screen 80. When an item is input, the server 10 grants a quantity of item points (for example, the more coins, the more points.) according to the number of coins of the input item to this distribution, and specifically, in the distribution management table 412, the server 10 adds the number of points according to the number of coins to the number of item points of the corresponding record. When an item is input, the server 10 subtracts the number of coins of the input item from the number of coins held in the corresponding record (record of the viewer who input the item) in the user information table 411. Furthermore, when an item is input, the server 10 adds the number of coins of the input item to the number of consumed coins of the corresponding record in the relationship parameter management table 413.

[0084] In addition, when a new viewer starts viewing (enters a live streaming room), a comment object 731, 831 corresponding to a system comment notifying the viewer of his / her entry is added to the comment display area 73, 83 of the corresponding distributor screen 70 and viewer screen 80. The account name of the user who started viewing (entered the room) is displayed in the comment object 731, 831 corresponding to the system comment. In addition, if this viewing is the first viewing of the day of the live streaming by the corresponding distributor, the server 10 updates the number of viewing days of the corresponding record in the relationship parameter management table 413 (adds 1).

[0085] The basic operation of the live distribution service has been described above. Next, the operation related to the management of the fan level of the viewer with respect to the distributor will be described. FIG. 18 is a diagram for explaining the conditions of 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 satisfies any one of these two to three conditions will have the corresponding fan level (the level will increase). For example, for fan level "1", two conditions are set: condition 1, "spend 10 coins or more, watch for 1.5 hours or more, and enter 4 comments or more", and condition 2, "spend 100 coins or more", and a user who satisfies any one of these two conditions will become a viewer with fan level "1". For example, three conditions are set for fan level "4": condition 1, "spend 1,000 coins or more, watch for 5 hours or more, watch for 4 days or more, and enter 35 comments or more," condition 2, "spend 3,000 coins or more, watch for 2 hours or more, and enter 5 comments or more," and condition 3, "spend 5,500 coins or more." A user who meets any one of these three conditions becomes a viewer of fan level "4."

[0086] In this example, the condition corresponding to the fan level may vary based on distributor information about the distributor, viewer information about the viewer, or combination information about a combination of a distributor and a viewer. For example, the condition corresponding to the fan level is easier to satisfy (e.g., the condition value is lower) the lower the rank of the distributor. Also, for example, the condition corresponding to the fan level varies depending on the residential area of ​​the viewer (e.g., the condition is easier to satisfy for viewers in a specific residential area). Also, for example, the condition corresponding to the fan level is easier to satisfy in the target year and month when a live broadcast by the corresponding distributor is viewed for the first time.

[0087] Such fan level determination is performed in real time during live distribution. Specifically, during live distribution, the server 10 updates the number of consumed coins, viewing time, number of days viewed, and number of input comments in real time for each viewer in the relationship parameter management table 413, and determines whether the fan level has been increased based on this information. When the fan level is increased, the fan level value of the corresponding record in the relationship parameter management table 413 is updated.

[0088] In this example, comment objects 731, 831 corresponding to the viewer's actions (specifically, entering a room (starting viewing) and inputting comments, tags, likes, and items) are decorated according to the viewer's fan level. For example, an icon corresponding to the viewer's fan level is added to such comment objects 731, 831, and a text color corresponding to the fan level is applied.

[0089] In this example, a certain higher fan level may be invalidated for a certain period from the start of each month, and may be valid from a specific timing in the middle. In this case, for example, a viewer who meets the conditions corresponding to a fan level that is valid at a specific timing (e.g., the 15th) of each month before the fan level is valid will not be promoted to that fan level until the fan level is valid (until the specific timing). In this way, it is possible to prevent a large number of viewers with higher fan levels from appearing early in each month, which may discourage other general viewers.

[0090] The above describes the operation related to managing the fan level of viewers for a broadcaster. Next, the operation when a broadcaster ends a live broadcast will be described. As described above, when a broadcaster selects the stop broadcast button 76 on the broadcaster screen 70, the live broadcast ends. When the live broadcast ends, the server 10 calculates and sets the number of broadcast points for that broadcast. In this example, the number of broadcast points is calculated based on the number of viewers (maximum value), the number of likes, the number of comments, and the number of item points. The number of broadcast points increases as the number of viewers (maximum value), the number of likes, the number of comments, and the number of item points increase. The calculated number of broadcast points is set in the corresponding record in the broadcast management table 412.

[0091] The above describes the operation performed when a broadcaster ends live broadcasting. Next, the operation performed when determining the rank of a broadcaster will be described. In this example, the rank for the day is determined (updated) based on the number of broadcast points acquired by the user on the previous day. FIG. 19 is a flow diagram illustrating the processing executed by the server 10 when updating the rank of each user. These processing operations are executed every night (for example, at 3:00 a.m. every day).

[0092] As shown in the figure, the server 10 first calculates the number of distribution points acquired by each user on the previous day (step S100). The number of distribution points acquired by a specific user on the previous day is calculated by referring to the distributor user account, distribution start date and time, and number of distribution points in the distribution management table 412. Note that if a user makes multiple distributions in one day, the number of distribution points acquired for each of the multiple distributions is added together.

[0093] After calculating the number of distribution points for each distributor on the previous day in this way, the server 10 then adds a bonus to the number of distribution points (step S110). Specifically, in this example, a bonus is added to the number of distribution points according to the number of "special fans" whose fan level is "4" or higher. FIG. 20 illustrates the correspondence between the number of special fans and the distribution point bonus (multiplication factor). In this example, as shown in the figure, when the number of special fans is 2 to 4, the number of distribution points is 101% (multiplied by 1.01) as the distribution point bonus. In other words, when the number of special fans is 2 to 4, 1% of the calculated number of distribution points is added as a bonus. Similarly, when the number of special fans is 5 to 9, the distribution point bonus (multiplication factor) is 102%, and thereafter, as the number of special fans increases, the distribution point bonus (multiplication factor) becomes larger, which is advantageous for the distributor.

[0094] In this example, a bonus is added to the distribution points according to the total value of the cheer points of each of the multiple viewers. For example, when the total value of the cheer points is 5000 points or more, a bonus of 500 points is added to the distribution points, and when the total value of the cheer points is 10000 points or more, a bonus of 1000 points is added to the distribution points. The bonus increases as the cheer points increase, which is advantageous for the distributor. In another example of this embodiment, the bonus of the distribution points based on the number of cheer points is not applied, and only the bonus of the distribution points based on the number of special fans may be applied. Instead of or in addition to the bonus of the distribution points based on the number of special fans, a bonus may be added to the distribution points according to the total value of the fan level values.

[0095] In addition, the addition of a bonus to the number of distribution points is one example of a reward for the distributor, and in another example of this embodiment, various rewards may be given to the distributor based on the fan level of each of the multiple viewers. For example, as a reward for the distributor, a bonus may be added to a reference number of diamonds, which will be described later, or the right to participate in a special event may be given.

[0096] After the bonus for the number of distribution points is thus added, the server 10 then updates the rank meter value of each user (step S120). Figure 21 is a diagram for explaining the update rule for the rank meter value. As shown in the figure, in this example, the rank meter value changes based on the ranking of each user's number of distribution points on the previous day within the rank band to which the user belongs.

[0097] Specifically, as shown in FIG. 21, the update rule for the rank meter value is that first, if the ranking in terms of the number of distribution points within the rank band is included in the top 10%, the change in the rank meter value is "+2" (an increase of 2 points). Similarly, if the ranking is included in the top 11-30% (the remaining 20% ​​after removing the top 10% from the top 30%), the change is "+1", if the ranking is included in the middle 30% (top 31-60%), the change is "±0" (no increase or decrease), and if the ranking is included in the bottom 40%, the change is "-1" (a decrease of 1 point). Note that if no distribution was performed on the previous day, the change in the rank meter value will be "-1" regardless of the ranking within the rank band.

[0098] In step S120, the rank meter value of each user is updated according to the update rule illustrated in FIG.

[0099] Returning to the flow diagram of FIG. 19, after updating the rank meter value of each user, the server 10 then updates the rank based on the updated rank meter value (step S130). FIG. 22 is a diagram for explaining the correspondence between the update contents of the rank and the required rank meter value. As shown in the figure, the required rank meter value is +3 whether the rank is increased across rank bands (in other words, when the rank is increased from the highest rank in each rank band) or when the rank is increased within the same rank band (in other words, when the rank is increased from a rank other than the highest rank in each rank band). That is, when the rank meter value of a user belonging to the highest rank (e.g., A3) in each rank band becomes +3, the user is increased to the lowest rank (e.g., S1) in the immediately upper rank band, and when the rank meter value of a user belonging to a rank other than the highest rank (e.g., B2 or B1) in each rank band becomes +3, the user is increased to the immediately upper rank (e.g., B3 or B2) in the same rank band.

[0100] Similarly, as illustrated in FIG. 22, the required rank meter value is -3 when ranking down within the same rank band (in other words, when ranking down from a rank other than the lowest rank in each rank band) and when ranking down across rank bands. That is, when a user who belongs to a rank other than the lowest rank in each rank band (e.g., B3 or B2) has a rank meter value of -3, the user will be ranked down to the next lower rank (e.g., B2 or B1) in the same rank band, and when a user who belongs to the lowest rank (e.g., A1) in each rank band has a rank meter value of -3, the user will be ranked down to the highest rank (e.g., B3) in the next lower rank band. In this example, the required rank meter value is set equal for ranking up / down across rank bands and ranking up / down within the same rank band, but as another example, in order to suppress abrupt ranking up / down in a short period of time, the absolute value of the required rank meter value may be set larger for ranking up / down across rank bands compared to ranking up / down within the same rank band.

[0101] In step S130, the rank is updated based on the rank meter value according to the correspondence relationship illustrated in Fig. 22. Note that the rank meter value of a user whose rank has been updated (a user whose rank has been upgraded / downgraded) is cleared to 0.

[0102] The above describes the operation when determining the rank of a distributor. Next, the operation when granting diamonds to a user will be described. In this example, diamonds are granted as a reward to a user as a distributor based on the distribution time of the previous day and the rank (rank on the previous day). FIG. 23 is a flow diagram illustrating the process executed by the server 10 when granting diamonds to each distributor. These processes are executed late at night every day, for example, at a time (for example, at midnight every day) before the process executed when updating the rank of each user illustrated in FIG. 19.

[0103] As shown in the figure, the server 10 first calculates the delivery time of each user on the previous day (step S200). Specifically, the delivery time of a specific user on the previous day is calculated by referring to the distributor user account, delivery start date and time, and delivery time in the delivery management table 412. If a user makes multiple deliveries in one day, the delivery times of each of the multiple deliveries are added together.

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

[0105] The above describes the operation when giving diamonds to users. Next, the operation when creating a message book as message content will be described. In this example, as described above, an event is held four times a year to create a message book for the distributor.

[0106] FIG. 24 illustrates a fan letter screen 300. In this example, the screen 300 is a screen for viewing a message (fan letter) to a specific broadcaster and for starting to edit a message for the message. For example, the fan letter screen 300 corresponding to a specific broadcaster is displayed via a profile screen of the specific broadcaster or a screen for family members of the specific broadcaster. Also, in this example, only special fans of the corresponding broadcaster (i.e., viewers with a fan level of "4" or higher) can enter messages, and the fan letter screen 300 is displayed on the user terminal 30 of the corresponding broadcaster itself and special fans of the broadcaster, but is not displayed on the user terminal 30 of other viewers who are not special fans.

[0107] As shown in the figure, the fan letter screen 300 has a selection area 310 for selecting the type of message (in this example, a combination of calendar year and season), and an information display area 320 located below the area 310 for displaying information corresponding to the message selected via the area 310.

[0108] The selection area 310 is configured to allow the selection of one message from among messages created so far and messages being created at that time (messages for which message input is being accepted). The display of selectable messages in the area 310 is switched by flicking or sliding left and right. In the fan letter screen 300 of FIG. 24, a message corresponding to "2021 SUMMER" is selected in the selection area 310. Note that in this example, the corresponding distributor can only select messages created so far (messages that have been published) in the selection area 310, and cannot select messages being created (they are not displayed in the selection area 310).

[0109] The fan letter screen 300 in Fig. 24 corresponds to a state in which the message (summer 2021) selected via the selection area 310 is being created (i.e., the state is midway through the period from the start date and time of message input acceptance to the end date and time of acceptance). In this case, a message object 330 being created is placed in the information display area 320 as shown in the figure.

[0110] As shown in the figure, the message-of-compilation object 330 displays the text "Send a fan letter to xxx" (where "xxx" is the distributor's account name) and information about the viewable date (the text "will be sent on October 1st"), and an object 332 displaying the number of viewers who have already entered is located in the lower right corner. The object 332 displays the number of messages entered at that time (30 in the example of FIG. 24). In this example, one viewer can enter one message, and the number of messages entered means the number of viewers who have entered messages. Note that in another example of this embodiment, one viewer may be allowed to enter multiple messages. In this example, the viewable date for the message-of-compilation is set to the day after the closing date and time for message entry.

[0111] When the message-in-progress object 330 is selected, a message editing screen 500 as shown in Fig. 25 is displayed in place of the fan letter screen 300. As shown in the figure, the screen 500 has a message input area 510 for inputting the contents of the message, a character selection area 520 for selecting the type of character to decorate the message on the message, a preview button 530, and a temporary save button 540.

[0112] In this example, an upper limit on the number of characters that can be included in a message is set for each fan level, and specifically, the upper limit on the number of characters increases as the fan level increases. The message input area 510 is configured to allow a message to be input within the upper limit on the number of characters that corresponds to the fan level of the corresponding viewer.

[0113] When temporary save button 540 is selected, the contents of the message entered via message input area 510 and the type of character selected via character selection area 520 are temporarily saved. Specifically, a new record is created in message management table 415, and values ​​corresponding to each field are set. In this case, the confirmed flag is set to a value indicating "unconfirmed." When temporary saving is performed, the temporarily saved contents are reflected on message editing screen 500 the next time that screen 500 is displayed.

[0114] When the preview button 530 is selected, a preview screen 600 as illustrated in FIG. 26 is displayed superimposed on the message editing screen 500. As illustrated, the screen 600 has a message object 610 and a post button 620 located below the object 610. The message object 610 is an object showing the appearance of the message reflected in the message collection, and reflects the contents inputted through the message editing screen 500 at that time. Specifically, the message object 610 reflects the contents of the message inputted at that time, and the selected character is arranged at the upper end of the message object 610. The message object 610 also displays the profile image and account name of the corresponding viewer. The viewer can check the appearance of the actual message reflected in the message collection through the object 610.

[0115] When the post button 620 is selected, the message input by the viewer is confirmed. Specifically, in the message management table 415, a value corresponding to each field is set for the corresponding record (a record created in response to temporary saving, or a newly created record if temporary saving has not been performed). In this case, the confirmed flag is set to a value indicating "confirmed." In this example, a message once confirmed cannot be edited, but the corresponding viewer can check the confirmed message via the message editing screen 500.

[0116] The reception of messages from viewers will continue until the end of the message reception period. When the reception period ends, a corresponding message book will be created and made public.

[0117] 27 illustrates a fan letter screen 300 in a state where a created and published message of messages is selected in the selection area 310. In this state, as shown in the figure, the fan letter screen 300 displays the published message of messages in the information display area 320, and more specifically, a header area 340 constituting the header of the published message of messages, and a body area 350 located below the area 340 and constituting the body of the message of messages are arranged.

[0118] A profile image of the distributor is placed in the center of the header area 340. The background image of the header area 340 has a design corresponding to the type of message.

[0119] A plurality of message objects 352, each corresponding to an individual message, are arranged vertically in two columns in main body area 350. Message objects 352 have the same appearance as message objects 610 in preview screen 600. The background image of main body area 350 has a design corresponding to the type of message.

[0120] The multiple message objects 352 arranged in the main body area 350 are arranged in descending order of the number of cheer points of the corresponding viewers. Specifically, in the main body area 350, the message object 352 corresponding to the viewer (the message input by) with the highest number of cheer points is arranged on the left side of the first row from the top, the message object 352 corresponding to the viewer with the second highest number of cheer points is similarly arranged on the right side of the first row from the top, the message object 352 corresponding to the viewer with the third highest number of cheer points is arranged on the left side of the second row from the top, and so on. Note that in this example, when a viewer who has input a message to a corresponding message book views the message book, the message object 352 corresponding to the viewer is arranged at the top position (left side of the top row) regardless of the number of cheer points of the viewer.

[0121] Note that such an arrangement of the message objects 352 is one example of a method of arranging the message objects 352 based on the number of cheer points of the corresponding viewer, and in other examples of this embodiment, various other methods are applied to arrange the message objects (control of position and size, etc.) based on the number of cheer points. For example, a plurality of message objects may be arranged in a predetermined area (e.g., a circular area, etc.), and the corresponding message objects may be arranged so that the greater the number of cheer points of the viewer, the closer to the center of the area. Also, for example, a plurality of message objects may be arranged in a 3D space (e.g., arranged in a reel shape), and the greater the number of cheer points of the viewer, the closer to the front the corresponding message objects are arranged.

[0122] In this example, if the number of messages entered (i.e., the number of viewers who entered messages) is equal to or greater than a predetermined value (e.g., 5), a collection of messages is created and published, whereas if the number of messages entered is less than the predetermined value, a collection of messages is not created or published (e.g., a predetermined image is displayed in the information display area 320 of the fan letter screen 300).

[0123] In this example, the created message book is made public to all special fans of the corresponding broadcaster as well as the broadcaster. In another example of this embodiment, the created message book is made public only to the viewers who entered the message among the special fans. In yet another example of this embodiment, the created message book may be made public to all users.

[0124] In the above example, the distributor may be allowed to edit the message book for himself / herself. For example, during a predetermined period before or after the created message book is published, the distributor may be allowed to delete (or hide) messages included in the message book, and may also be allowed to input comments or stamps (images) by the distributor himself / herself. Comments and the like input by the distributor himself / herself are placed, for example, in the header area 340 that constitutes the header of the message book.

[0125] In the above example, only special fans with a fan level of "4" or higher can input a message for the message, the upper limit of the number of characters included in the message is set based on the fan level, and the message object 352 is arranged based on the number of cheer points in the published message. However, the "fan level" and the "number of cheer points" are examples of relationship parameters related to the relationship between the distributor and the viewer, and in other examples of the present embodiment, the input of the message and the arrangement of the message may be controlled based on the values ​​of other parameters. For example, if a member of the family of the corresponding distributor, the message for the message may be allowed to be input. In addition, the control based on the value of the relationship parameter includes control other than the control of the input of the message and the control of the arrangement of the message, and various controls regarding the creation of the message may be performed based on the value of the relationship parameter.

[0126] In the above example, the message is decorated with characters, but instead of or in addition to this, various images (including photographs) may be used to create and edit the message object 352. For example, such images are used as message decoration, message background, and message body. Also, for example, such images are selected from images prepared in advance by the management side of the live distribution service, or selected from images owned by the viewer.

[0127] In the above example, the message for the message book is composed of characters, but it may be composed of video or audio. In this case, the format of the message content is not limited to the message book as described above, and may be composed of various types of content. For example, the message content is composed of a combination of time-sequential video or audio, and in this case, the time position of the corresponding message (video or audio) may be determined according to the number of cheer points of the viewer.

[0128] In the above example, when the number of viewers who have input messages is large, the collected messages may be divided and generated. For example, even during the message input acceptance period, each time the number of input messages reaches a predetermined value (e.g., 30), a divided collected message may be generated. Alternatively, when the message input acceptance period ends and the number of messages is equal to or greater than a predetermined value, the collected message may be divided and generated. In this case, the messages included in each of the collected messages are sorted, for example, according to the fan level of the viewers (divided into collected messages corresponding to viewers with a high fan level and collected messages corresponding to viewers with a low fan level). The divided collected messages may be individually selectable as different types of collected messages, for example, via the selection area 310 of the fan letter screen 300.

[0129] In the above example, messages from viewers who have been blocked by the distributor may not be displayed in the message book. For example, a message entered by a blocked viewer is included in the message book when the blocked viewer views it, but is not included when other users view it.

[0130] In the above example, during the message input acceptance period, special fan viewers who have not yet confirmed their message input may be prompted to input a message. For example, during the period, special fan viewers who have finished watching the live broadcast of the corresponding broadcaster may be guided to a message editing screen 500 for editing a message to be written to the broadcaster (displayed on the viewer terminal 30). In addition, such guidance to the message editing screen 500 may be performed when the live broadcast is watched to the end.

[0131] In the above example, for a broadcaster who has less than a certain number of special fans, the reception of message input may not be started. In this case, for example, even during the period when message input is being received, a predetermined image is displayed in the information display area 320 of the fan letter screen 300 corresponding to the broadcaster.

[0132] In the above-described example, a live streaming service is provided that allows live streaming of videos composed of images input via the camera of the distributor terminal 30 and audio input via the microphone, and that allows the videos to be viewed. However, in another example of this embodiment, an on-demand video streaming service is provided in which videos provided by distributors are stored in advance, and the videos are individually distributed in response to requests from viewers.

[0133] The video distribution server 10 of the present embodiment described above generates message content (messages) including multiple messages to the distributor input by the viewer based on the values ​​of relationship parameters (fan level and cheer points) related to the relationship between the viewer and the distributor, so the generated message content takes into account the relationship between the viewer and the distributor. In this way, the video distribution server 10 supports the generation of content that takes into account the relationship between users.

[0134] In the above-described embodiment, message content including a message from a viewer to a distributor in a video distribution service is generated, but in other embodiments of the present invention, a configuration may be made to generate message content including a message from a second user to a first user in other services. For example, message inputs by participants (second users) in a community in a community service (including online salons) to the owner (first user) of the community may be accepted, and message content including these messages may be generated. Then, message content is generated based on the values ​​of relationship parameters (rank, level, etc.) related to the relationship between the owner and participants of these communities.

[0135] The processes and procedures described herein may be realized by software, hardware, or any combination thereof, other than those explicitly described. For example, the processes and procedures described herein may be realized by implementing logic corresponding to the processes and procedures in a medium such as an integrated circuit, a volatile memory, a non-volatile memory, or a magnetic disk. In addition, the processes and procedures described herein may be implemented as a computer program corresponding to the processes and procedures, and executed by various computers.

[0136] 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 realized by combining them into fewer components or breaking them down into more components.

[0137] In this specification, even if a component of the invention is described as either singular or plural, or described without limitation to either singular or plural, the component may be either singular or plural unless the context requires otherwise. [Explanation of symbols]

[0138] 10 Video distribution server 11. Computer Processors 15 Storage 20. Communication Networks 30 User terminals 41 Information storage management department 411 User Information Table 412 Distribution Management Table 413 Relationship Parameter Management Table 414 Content Information Table 415 Message Management Table 43 Management function control section 45 Video distribution service control section 47 Content generation control section 60 Top screen 70 Streamer Screen 80 Viewer Screen 100 Delivery preparation screen 200 Item selection screen 300 Fan letter screen 500 Message editing screen 600 Preview Screens

Claims

1. 1. A system for generating content including a plurality of messages, comprising one or more computer processors, the system comprising: The one or more computer processors, in response to execution of the readable instructions, managing a value of a predetermined parameter related to a relationship with a first user, the predetermined parameter being associated with each of a plurality of second users; generating a predetermined content including a plurality of messages to the first user input by at least a portion of the plurality of second users; The process of generating the predetermined content includes: generating the predetermined content based at least on values ​​of the predetermined parameters of at least a portion of the plurality of second users; and presenting the generated predetermined content to the first user and at least a portion of the plurality of second users; system.

2. The process of generating the predetermined content includes generating the predetermined content such that a message input by a second user having a strong relationship indicated by a value of the predetermined parameter is given priority. The system of claim 1.

3. the process of generating the predetermined content includes accepting input of a message by a second user whose value of the predetermined parameter is within a predetermined range, and not accepting input of a message by a second user whose value of the predetermined parameter is outside the predetermined range. The system of claim 2.

4. The process of generating the predetermined content includes generating the predetermined content so that an amount of information of a message input by a second user having a strong relationship indicated by a value of the predetermined parameter is increased.

4. The system of claim 2 or 3.

5. the process of generating the predetermined content includes generating the predetermined content such that a message input by a second user having a strong relationship indicated by a value of the predetermined parameter is preferentially arranged.

5. A system according to any one of claims 2 to 4.

6. The process of generating the predetermined content includes limiting the number of messages that can be input by one second user to within a predetermined value.

6. A system according to any one of claims 1 to 5.

7. The process of generating the predetermined content includes generating the predetermined content by excluding a message input by a second user that has been set to a predetermined state by the first user.

7. A system according to any one of claims 1 to 6.

8. the process of generating the predetermined content includes starting to accept input of a message from each of the plurality of second users in response to a start of a predetermined period, and generating the predetermined content including the plurality of messages input by the end of the predetermined period.

8. A system according to any preceding claim.

9. the process of generating the predetermined content includes dividing and generating the predetermined content when the number of second users who input messages is equal to or greater than a first predetermined value; 9. A system according to any preceding claim.

10. The predetermined content is a collection of messages.

10. A system according to any preceding claim.

11. The first user is a broadcaster of a live video; Each of the plurality of second users is a viewer of a live video.

11. A system according to any preceding claim.

12. The process of managing the value of the predetermined parameter includes updating the value of the predetermined parameter for each of the plurality of viewers so that the value increases as the viewers watch more of the live video provided by the distributor; The process of generating the predetermined content includes generating the predetermined content such that a message input by a viewer having a larger value of the predetermined parameter is given priority. The system of claim 11.

13. 1. A method, executed by one or more computers, for generating content including a plurality of messages, comprising: managing a value of a predetermined parameter related to a relationship between the first user and each of a plurality of second users; generating a predetermined content including a plurality of messages to the first user input by at least some of the plurality of second users; The step of generating the predetermined content includes: generating the predetermined content based at least on values ​​of the predetermined parameters of at least a portion of the plurality of second users; and presenting the generated predetermined content to the first user and at least a portion of the plurality of second users; method.

14. A program for generating content including a plurality of messages, the program comprising: managing a value of a predetermined parameter related to a relationship with a first user, the predetermined parameter being associated with each of a plurality of second users; generating a predetermined content including a plurality of messages to the first user input by at least a portion of the plurality of second users; The process of generating the predetermined content includes: generating the predetermined content based at least on values ​​of the predetermined parameters of at least a portion of the plurality of second users; and presenting the generated predetermined content to the first user and at least a portion of the plurality of second users; program.

Images