System, method, and program for generating content

The system addresses the challenge of user relationships in content generation by managing relationship parameters and prioritizing messages from strongly related users, resulting in content that effectively engages and strengthens user relationships.

JP2025096445APending Publication Date: 2025-06-26DENA CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2025063630
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-04-08
Publication Date
2025-06-26

AI Technical Summary

Technical Problem

Conventional systems for generating content with multiple messages do not adequately consider the relationships between users, particularly in community services, making it difficult to apply them directly as communication tools in such contexts.

Method used

A system that includes computer processors managing values of predetermined parameters related to user relationships, generating content with multiple messages based on these values, and prioritizing messages from users with strong relationships with the content creator.

Benefits of technology

The system effectively generates content that takes into account user relationships, promoting engagement and strengthening relationships between content creators and their audience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025096445000001_ABST
    Figure 2025096445000001_ABST
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

Background Art

[0002] Conventionally, various services for generating content including a plurality of messages have been provided. For example, Patent Documents 1 to 3 below disclose a system for electronically realizing a collaborative writing including a plurality of messages from a plurality of participants. Such a system promotes efficient generation of collaborative writing and improvement of the quality of the generated collaborative writing. In addition, content such as such collaborative writing can also be used as a communication tool between an owner (artist, creator, influencer, etc.) and a participant (fan, etc.) in a community service.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the conventional system described above cannot be said to take into account the characteristics of community services, and it may be difficult to directly apply it as a communication tool in such services. For example, it cannot be said that the conventional system sufficiently considers the relationship between the recipient of a post-it note (e.g., the owner of a community) and the participants who participate in the post-it note (e.g., participants in the community).

[0005] One of the objectives of an embodiment of the present invention is to assist in generating content that takes into account the relationships between users. Other objectives of the embodiments of the present invention will become apparent by referring to the entire specification.

Means for Solving the Problems

[0006] A system according to an embodiment of the present invention includes one or more computer processors and is a system for generating content including a plurality of messages. The one or more computer processors, in response to the execution of readable instructions, perform a process of managing values of a predetermined parameter related to the relationship with a first user, the predetermined parameter 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 a part of the plurality of second users. 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 a part of the plurality of second users.

[0007] A method according to an embodiment of the present invention is a method for generating content including a plurality of messages, which is executed by one or more computers, and includes a step of managing values of predetermined parameters related to a relationship with a first user, the predetermined parameters being associated with each of a plurality of second users, and a step of generating predetermined content including a plurality of messages for the first user input by at least a part of the plurality of second users, wherein the step of generating the predetermined content includes generating the predetermined content based at least on the values of the predetermined parameters of at least a part of the plurality of second users.

[0008] A program according to an embodiment of the present invention is a program for generating content including a plurality of 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 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 a part of the plurality of 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 a part of the plurality of second users.

Advantages of the Invention

[0009] Various embodiments of the present invention assist in generating content in consideration of the relationships between users.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Embodiments for Carrying Out the Invention

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

[0012] FIG. 1 is a configuration diagram schematically showing the 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. In FIG. 1, only one user terminal 30 is shown, but the server 10 is communicably connected to a plurality of user terminals 30. The server 10 provides a user with a video distribution service for distributing and viewing videos via the user terminal 30. In the present 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 part or all of the system of the present invention and has a function for generating content including a plurality of messages.

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

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

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

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

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

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

[0019] The video delivery server 10 configured as described above can be configured to have functions as a web server and an application server. In this case, in response to requests from a web browser and other applications (for example, an application for a video delivery service) installed on the user terminal 30, it executes various processes and transmits screen data (for example, HTML data) and control data, etc. corresponding to the results of the processes to the user terminal 30. On the user terminal 30, a web page or other screen based on the received data can be displayed.

[0020] Next, the hardware configuration of the user terminal 30 will be described. The user terminal 30 is configured as a general computer and includes, as shown in FIG. 1, 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 or GPU, etc., reads various programs stored in the storage 35, etc. into the main memory 32, and executes various instructions included in the programs. The main memory 32 is configured by, for example, DRAM or the like.

[0022] The input / output I / F 33 includes various input / output devices for exchanging information with an operator or the like. The input / output I / F 33 includes, for example, information input devices such as a keyboard and a pointing device (for example, a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. Further, the input / output I / F 33 includes an image output device such as a display and a voice output device such as a speaker.

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

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

[0025] In the present embodiment, the user terminal 30 can be configured as a smartphone, a tablet terminal, a personal computer, a wearable device, or the like.

[0026] A user who operates the user terminal 30 configured as described above can utilize the video distribution service provided by the server 10 by executing communication with the video distribution server 10 via a web browser or other application installed in the storage 35 or the like.

[0027] Next, the functions of the video distribution server 10 configured as described above will be described. FIG. 2 is a block diagram schematically showing the functions of the video distribution server 10. As shown in the figure, the server 10 includes 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 a computer processor 11 and a main memory 12, and various programs and data stored in the storage 15 or the like. For example, the computer processor 11 executes instructions included in a program read into the main memory 12. Further, part 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 can be realized by the user terminal 30.

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

[0029] The management function control unit 43 is configured to execute various processes related to the control of the management functions of the video distribution service. For example, the management function control unit 43 transmits screen data, control data, etc. of various screens related to the management functions to the user terminal 30, executes various processes in response to operation inputs by the user via the screen displayed on the user terminal 30, and transmits screen data, control data, etc. corresponding 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, etc.

[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 videos provided by a distributor to a plurality of viewers. For example, when performing real-time distribution (live distribution) of a video, the video distribution service control unit 45 receives a real-time video transmitted from the user terminal 30 of the distributor (hereinafter sometimes referred to as the "distributor terminal 30"), and transmits the video to each user terminal 30 of a plurality of viewers (hereinafter sometimes referred to as the "viewer terminal 30"). At the viewer terminal 30, the video is displayed (played back) on a viewer screen for viewing the video. The real-time video is composed of, for example, an image input via the camera of the distributor terminal 30 and audio input via the microphone. Also, the real-time video is composed of, for example, an image and audio output via an application (for example, a game application, etc.) running on the distributor terminal 30. Such live distribution of a video can be performed by a streaming method using a protocol such as HTTP Live Streaming (HLS). Also, the video distribution service control unit 45 may be configured to record a video provided by a distributor in the storage 15 or the like, and distribute the video in response to an individual request from a viewer.

[0031] In the present embodiment, the video distribution service control unit 45 is configured to manage the values of relationship parameters related to the relationship with the distributor (first user), which are associated with each of a plurality of viewers (second users). The values of the relationship parameters are managed, for example, in a relationship parameter management table 413 in association with combinations of the distributor and the viewers. The relationship parameter can be designed as a parameter indicating, for example, intimacy, friendliness, or contribution degree.

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

[0033] As described above, since the video distribution server 10 in the present embodiment generates message content including a plurality of messages for a distributor input by viewers, based on the values of the relationship parameters related to the relationship between the viewers and the distributor, the generated message content takes into account the relationship between the viewers 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 the present embodiment, when generating the message content, messages from viewers with a strong relationship with the distributor may be prioritized. That is, the content generation control unit 47 can be configured to generate the message content such that messages input by viewers with a strong relationship indicated by the values of the relationship parameters are prioritized.

[0035] For example, when designed such that the value of the relationship parameter increases as the relationship becomes stronger, messages from viewers with a large value of the relationship parameter are prioritized. For example, when the value of the relationship parameter is updated to increase as the viewer watches the video provided by the distributor, messages from viewers with a large value of the relationship parameter are prioritized. Also, for example, when designed such that the value of the relationship parameter decreases as the relationship becomes stronger, messages from viewers with a small value of the relationship parameter are prioritized. Such a configuration enables the generation of content that prioritizes messages from viewers with a strong relationship with the distributor. As a result, it can promote viewers to strengthen their relationship with the distributor.

[0036] In the present embodiment, the prioritization of messages from viewers with 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 value of the relationship parameter is within a predetermined range (for example, equal to or greater than a predetermined value), while not accepting input of messages from viewers whose value of the relationship parameter is outside the predetermined range (for example, less than the 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 viewers whose value of the relationship parameter is within the predetermined range, while not being displayed on the user terminal 30 of viewers whose value of the relationship parameter is outside the predetermined range. Such a configuration enables the generation of content that includes only messages from viewers with a strong relationship.

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

[0038] Also, for example, the content generation control unit 47 may be configured to generate message content such that messages input by viewers with a strong relationship indicated by the value of the relationship parameter are preferentially arranged. For example, messages input by viewers with a strong relationship are arranged to be prominent in the content. For example, the message content is configured as an image or page where a plurality of messages are arranged, and the message input by a viewer with a strong relationship is arranged at a prominent position (e.g., the upper part or the center, etc.) and / or with a prominent size (e.g., the size (area) of the message becomes larger) of such an image or page. Also, when the message is configured as a video or audio and the message content is generated by combining a plurality of temporally continuous videos or audios, the message input by a viewer with a strong relationship is arranged at a prominent temporal position (e.g., the beginning or the end, etc.) of such content (the combination of videos or audios). Such a configuration enables the generation of content in which messages from viewers with a strong relationship are preferentially arranged.

[0039] In this embodiment, the number of messages that can be input by one viewer may be restricted. For example, the content generation control unit 47 may be configured to restrict 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 can suppress one viewer from inputting an excessive number of messages.

[0040] In this embodiment, messages from a specific viewer may be excluded. For example, the content generation control unit 47 may be configured to exclude messages input by a viewer (for example, a blocked viewer) set to a predetermined state by the distributor and generate message content. For example, the content generation control unit 47 may be configured not to accept input of messages from a viewer set to a predetermined state, or, after accepting input of a message from such a viewer, to ignore the message (not include it in the content). Such a configuration enables generation of content excluding messages from a specific viewer.

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

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

[0043] Further, the content generation control unit 47 may be configured to start accepting input of messages from 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 is configured to prompt viewers who have watched a video during the predetermined period to input messages to the distributor who provides the video. Such a configuration enables the generation of content including messages input from viewers over 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 divided and generated into first content consisting of a plurality of messages from a first group of viewers among the plurality of viewers who have input messages, and second content consisting of a plurality of messages from a second group of viewers (for example, a group of viewers with a stronger relationship with the distributor than the first group of viewers, etc.). Also, for example, the message content is divided and generated into first content consisting of a plurality of messages input in a first period, and second content consisting of a plurality of messages input in a second period later than the first period. Such a configuration suppresses the inclusion of messages from an excessive number of viewers in one piece of content.

[0045] Next, a specific example as an aspect of the video distribution server 10 of the present embodiment having such a function will be described. The video distribution service in this example is configured as a live distribution of a video composed of an image input via the camera of the distributor terminal 30 and audio input via the microphone, and a live distribution service that enables viewing thereof.

[0046] First, in this example, the information managed by each table will be described. FIG. 3 illustrates the information managed in the user information table 411 in this example. The user information table 411 manages information related to users of the live distribution service, and as shown in the figure, in association with a "user account" that identifies an individual user, it includes "basic information" such as an account name, age, gender, residential area, and profile information, "distribution history information" which is information related to the distribution history as a distributor, "viewing history information" which is information related to the viewing history as a viewer, "followed user information" which is information related to other users followed by this user, "follower information" which is information related to other users (followers) who follow this user, "blocked user information" which is information related to other users blocked by this user, "family information" which is information related to the family to which this user belongs as a family member, "rank" indicating the rank of the user as a distributor, "rank meter value" which is a parameter value for determining rank up / down, "coin holding amount" indicating the holding amount of virtual coins available in the live distribution service, "diamond holding amount" also indicating the holding amount of virtual diamonds, and "classification text" which is a classification as a distributor set by the user himself / herself, etc.

[0047] In this example, the user can set other users to a blocked state (predetermined state), and the blocked user information includes information (such as user accounts) about the users set to the blocked state (blocked users). Other blocked users have restricted actions that can be performed on the live broadcasts of the corresponding users. For example, they cannot enter comments while watching a live broadcast.

[0048] In this example, a family is a community of fans who support the broadcaster. They can join in response to an invitation from the broadcaster or the family administrator, or they can join in response to approval by the broadcaster or the family administrator for the user's application to join. Also, in this example, an upper limit value (for example, 100 people) is set for the number of family members.

[0049] Also, in this example, coins are given to users free of charge and for a fee on various occasions. For example, users can obtain coins for free as rewards such as login bonuses. Also, for example, users can purchase coins for a fee (with real currency).

[0050] FIG. 4 is a diagram for explaining the "ranks" of broadcasters in this example. As shown in the figure, in this example, there are six rank bands: "S", "A", "B", "C", "D", and "E". The "S" rank band has six ranks, and each of the four rank bands of "A", "B", "C", and "D" is composed of three ranks (for example, ranks such as "S1" and "A2" where numbers are added to the alphabets indicating the rank bands). Also, the "E" rank band is composed of one rank, "E". That is, in this example, there are 19 ranks (6 + 3×4 + 1 = 19).

[0051] Also, for the rank bands, the "S" side is the highest rank and the "E" side is the lowest rank. Also, within the same rank band, the rank is higher as the number added to the rank band is larger, and lower as the added number is smaller. In this example, the user's rank is set to "D1" as the initial value.

[0052] FIG. 5 illustrates the information managed in the distribution management table 412 in this example. The distribution management table 412 manages information regarding individual live distributions (videos), and as shown in the figure, in association with a "distribution ID" that identifies an individual live distribution, it manages a "distributor user account" that identifies the distributor, a "distribution start date and time", a "distribution time" indicating the duration from the start time of the distribution, a "number of viewers (current value and maximum value)", a "number of comments" which is the number of comments input by viewers, a "number of likes" which is the number of "likes" input by viewers, an "item point number" that increases in response to viewer input of items, a "distribution point number" which is the points given to this distribution, information regarding "tag information" which is information about the tags given to this distribution, and other information.

[0053] FIG. 6 illustrates the information managed in the relationship parameter management table 413 in this example. The relationship parameter management table 413 manages information regarding the fan level (relationship parameter) of viewers with respect to a distributor in a target year and month (by distributor), and as shown in the figure, 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", it manages the "fan level" of the corresponding viewer with respect to the corresponding distributor in the target year and month, the "number of coins consumed" by the viewer for the live distribution by the distributor in the target year and month, the "viewing time", the "number of viewing days", the "number of input comments", the "email point number" (relationship parameter), and other information. Thus, in this example, the fan level of viewers with respect to a distributor is managed on a monthly basis.

[0054] The number of e-mail points is calculated using a calculation formula based on the number of consumed coins, viewing time, number of viewing days, and number of input comments. The larger the value of each of these parameters, the larger the value of the number of e-mail points.

[0055] FIG. 7 illustrates the information managed in the content information table 414 in this example. The content information table 414 manages information regarding "doodle" as message content in this example. As shown in the figure, it manages information such as "message reception start date and time", which is the date and time to start receiving input of the message for the doodle, "message reception end date and time", which is the date and time to end receiving input of the message for the doodle, and "design information", which is information regarding the design of the background of the doodle, etc., in association with a "content ID" that identifies the type of each individual doodle.

[0056] FIG. 8 illustrates the types of doodles provided in this example and the corresponding schedules (message input reception start date and time and reception end date and time). In the live distribution service of this example, an event to create a doodle for the distributor is held four times a year, and the doodle has a design corresponding to each season. For example, as shown in the figure, the types of doodles corresponding to spring, summer, autumn, and winter in 2021 are preset, and a corresponding schedule is set for each of these types of doodles. For example, for the "summer 2021" doodle, the reception of message input starts on September 15, 2021, and ends on September 30, 2021. Such information is set in the content information table 414.

[0057] FIG. 9 illustrates the information managed in the message management table 415 in this example. The message management table 415 manages information regarding the messages for graffiti input by each viewer, and as illustrated, corresponds to a combination of a "distributor user account" for identifying the distributor, a "content ID" for identifying the type of graffiti, and a "viewer user account" for identifying the viewer, and manages information such as "message content", which is the content of the message input by the corresponding viewer as the corresponding graffiti message for the corresponding distributor, "character type", which is the type of character for decorating the message on the graffiti, "confirmed flag", which indicates whether the message is confirmed, and "confirmation date and time", which is the date and time when the message was confirmed.

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

[0059] The selection area 62 is an area for selecting the display content in the list display area 64. Specifically, when "Follow" is selected in the selection area 62, live broadcasts (videos being broadcast) of other users followed by the user are listed in the list display area 64. Similarly, when "Popular" is selected in the selection area 62, live broadcasts extracted according to a predetermined extraction condition for extracting popular live broadcasts (for example, broadcasts with the number of viewers (current value) equal to or greater than a threshold value, etc.) are listed in the list display area 64. Also, when "Topic" is selected in the selection area 62, the tags assigned to the live broadcasts are listed in chronological order (in the order of assignment time) together with the corresponding broadcasts in the list display area 64. Further, when "All" is selected in the selection area 62, all live broadcasts become the objects of 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 the list display area 64 in this case, as shown in the figure, a plurality of individual display areas 641 each displaying information related to an individual live broadcast are arranged in two columns vertically. The individual display area 641 is configured to be able to start viewing the corresponding broadcast (start playing the corresponding video) according to the user's selection. The list display area 64 is configured such that the displayed individual display areas 641 are switched by a flick operation or a slide operation in the vertical direction, etc. 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-described configuration when "Popular" is selected.

[0061] FIG. 11 illustrates the display content of the individual display area 641. The individual display area 641 displays an image preset by the distributor of the live distribution, the account name of the distributor, the number of viewers (current value), etc. As shown in the figure, at the lower end thereof, a first tag object 6411 and a second tag object 6412 are arranged side by side in the horizontal direction. The first tag object 6411 displays the 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 hash tag (a form in which "#" is added to the beginning of the character string). (In the example of FIG. 11, it is displayed as "#Big Eater Distribution".) Further, the second tag object 6412 displays the latest tag given by the viewer to the corresponding live distribution in the same form of a hash tag. (In the example of FIG. 11, it is displayed as "#Curry".)

[0062] FIG. 12 illustrates the top screen 60 when "Topic" is selected in the selection area 62. In this case, as shown in the figure, in the list display area 64 of the top screen 60, the tags given to any live distribution are list-displayed in time series together with the distribution. That is, in the list display area 64 when "Topic" is selected in the selection area 62, the tags arranged in descending order of the assignment time and the corresponding live distribution (the distribution to which the tag is given) are list-displayed.

[0063] In the list display area 64 in this case, a plurality of individual display areas 642 that each display information regarding an individual tag and the corresponding live distribution are arranged side by side in the vertical direction. When a new tag is given to any live distribution, the corresponding individual display area 642 is added to the topmost part of the list display area 64.

[0064] FIG. 13 illustrates the display content of the individual display area 642. As shown in the figure, a tag object 6421 is arranged at the upper left corner of the area 642, and the profile image and account name of the corresponding (tagged) live streamer are displayed. A link to the corresponding live stream is set in the individual display area 642. By selecting any one of the plurality of individual display areas 642 displayed in the list display area 64, the user can start viewing the corresponding live stream.

[0065] The live stream button 66 on the top screen 60 is an object for the user to perform a live stream of a video as a live streamer. When the live stream button 66 is selected by the user, the live stream preparation screen 100 illustrated in FIG. 14 is displayed overlaid on the top screen 60. As shown in the figure, the screen 100 has a live stream title input area 102 for inputting a live stream title, a stretch live stream setting switch 104 for setting a stretch live stream mode, a tweet setting button 106 for setting a tweet (posting a message to an SNS) automatically performed during the live stream, and a live stream start button 108 displayed as "Start!". The stretch live stream is a live stream distribution mode in which only new viewers (specifically, viewers whose total viewing time for a corresponding live streamer within a predetermined period is less than a predetermined value) can view.

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

[0067] FIG. 15 illustrates a distributor screen 70 displayed on the distributor terminal 30 in response to the selection of the distribution start button 108 (i.e., the start of live distribution). As shown in the figure, the screen 70 includes 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 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 at the center of the lower end of the screen.

[0068] The video display area 71 displays the video being live-distributed, that is, the image input via the camera of the distributor terminal 30. Usually, the distributor uses the in-camera of the distributor terminal 30, etc., with the distributor himself / herself as the subject, so the video being distributed includes the image of the distributor himself / herself.

[0069] The basic information display area 72 displays the basic information of this distribution. Specifically, it displays distributor information (profile image, etc.), the number of viewers of this distribution (current value), and the number of "likes" input by viewers for this distribution, etc.

[0070] The comment display area 73 is an area for displaying user comments input by viewers or system comments automatically input by the server 10. Specifically, a plurality of comment objects 731, each corresponding to an individual comment, are arranged side by side in the vertical direction in the area 73. When a new comment is input, the corresponding comment object 731 is added to the lower side in the comment display area 73, and the existing comment objects 731 move upward in order. The comment display area 73 is configured such that the displayed comment objects 731 can be switched by a flick operation or a slide operation in the vertical direction, etc.

[0071] The tag display area 74 displays information regarding the tags assigned to this distribution. Specifically, a plurality of tag objects 741, each corresponding to an individual tag, are arranged side by side in the horizontal direction in the area 74.

[0072] The viewer information display area 75 displays information about a plurality of viewers who are watching the corresponding live distribution. Specifically, in this area 75, a plurality of icon objects 751 each corresponding to a viewer are arranged side by side in the left-right direction. The object 751 has a circular shape and displays the profile image of the corresponding viewer. The plurality of icon objects 751 are arranged in an order according to a predetermined rule. For example, they are arranged such that the viewers with a larger number of the above-mentioned e-points are on the left side.

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

[0074] FIG. 16 illustrates a viewer screen 80 displayed on the viewer terminal 30. For example, when an arbitrary live distribution is selected by the viewer via the list display area 64 etc. of the top screen 60, a viewer screen 80 for watching the selected distribution is displayed on the viewer terminal 30. As shown in the figure, similar to the above-mentioned distributor screen 70, 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. Also, at the lower end of the viewer screen 80, there are an input mode switching button 86, a comment input area 87, a "like" button 88 with a heart mark displayed thereon, and an item input button 89 with a present symbol displayed thereon.

[0075] The comment input area 87 is an area for viewers to input comments or tags. While the input mode switching button 86 is in the unselected state, the comment input area 87 is in the normal comment input mode. In the comment input mode, when the 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 at the corresponding distributor terminal 30 (the user terminal 30 of the distributor of the live distribution being viewed) and each viewer terminal 30 (each user terminal 30 of a plurality of viewers of the live distribution being viewed), in the comment display areas 73 and 83 of the distributor screen 70 and the viewer screen 80, comment objects 731 and 831 corresponding to the user comment are added. In the comment objects 731 and 831 corresponding to the user comment, the content (character string) of the comment is displayed together with the account name of the viewer who input the comment. Also, when the user comment is transmitted, the server 10 updates (increments by 1) the comment count in the corresponding record of the distribution management table 412. Also, when the user comment is transmitted, the server 10 updates (increments by 1) the input comment count in the corresponding record of the relationship parameter management table 413.

[0076] Also, when the input mode switching button 86 is in the selected state, the comment input area 87 is in the tag input mode. In the tag input mode, when the 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 distribution. In this example, viewers who can input tags are limited to family members of the corresponding distributor. Specifically, the input mode switching button 86 on the viewer screen 80 can be selected (enabled) when the viewer is a family member of the distributor, while it cannot be selected (disabled) when the viewer is not a family member of the distributor. Also, in this example, the number of tags that can be assigned to one live distribution within a predetermined period is limited. Specifically, the number of tags that can be assigned within 5 minutes is up to 3.

[0077] When a tag is assigned, corresponding tag objects 741 and 841 are added to the tag display areas 74 and 84 of the corresponding distributor screen 70 and viewer screen 80. In the tag display areas 74 and 84, the tag objects 741 and 841 are arranged side by side in the left - right direction such that the left side is newer (the assignment time is later). Therefore, the tag objects 741 and 841 corresponding to the newly assigned tag are added to the left end in the tag display areas 74 and 84. Note that the tag objects 741 and 841 corresponding to tags for which 5 minutes have elapsed since assignment are deleted (for example, they disappear with an animation effect of moving to the right).

[0078] In this example, the tag objects 741 and 841 display the content of the tag in the form of a hashtag with a "#" added to the beginning of the character string. For example, when the content of the tag is "Tokyo tourism", it is displayed as "#Tokyo tourism" in the tag objects 741 and 841. The left - right length of the tag objects 741 and 841 is automatically adjusted according to the length of the character string to be displayed.

[0079] Also, when a tag is assigned, in the comment display areas 73 and 83 of the corresponding distributor screen 70 and viewer screen 80, comment objects 731 and 831 corresponding to system comments notifying the assignment of the tag are added. In the comment objects 731 and 831 corresponding to the system comments, the content of the assigned tag is displayed together with the account name of the viewer who assigned (input) the tag. For example, a comment such as "xx has tagged the live stream with '#Tokyo tourism'." is displayed. Also, when a tag is assigned, the tag information in the corresponding record of the distribution management table 412 is updated.

[0080] The like button 88 is an object for viewers to input "like" for the broadcaster (live streaming). When the button 88 is selected by a viewer, the "like" input is made, and in the comment display areas 73 and 83 of the corresponding broadcaster screen 70 and viewer screen 80, comment objects 731 and 831 corresponding to the system comment notifying the "like" input are added. In the comment objects 731 and 831 corresponding to the system comment, text indicating the "like" input is displayed together with the account name of the viewer who input the "like". Also, when "like" is input, corresponding visual effects (for example, an animation effect where a heart-shaped object is displayed flowing from the lower side to the upper side of the screen, etc.) are added to the video display areas 71 and 81 of the broadcaster screen 70 and viewer screen 80. Also, when "like" is input, the server 10 updates (increments by 1) the "number of likes" in the corresponding record of the distribution management table 412.

[0081] The item input button 89 is an object for viewers to input items. When the button 89 is selected by a viewer, the item selection screen 200 illustrated in FIG. 17 is displayed overlaid on the viewer screen 80. As shown in the figure, the screen 200 displays a list of a plurality of individual display areas 202 each of which displays information about an item. The individual display area 202 displays an image corresponding to the item and the number of coins required for the input of the item.

[0082] In this example, a plurality of items that can be input by viewers are predetermined, and for each item, the number of coins as its price (which can also be referred to as value or consideration) is preset. The item selection screen 200 displays a list of these plurality of inputtable items. When any item is selected by a viewer via the item selection screen 200, the input of the selected item is made.

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

[0084] Also, when a new viewer starts viewing (enters the live distribution room), in the comment display areas 73 and 83 of the corresponding distributor screen 70 and viewer screen 80, comment objects 731 and 831 corresponding to system comments notifying the entry of the viewer are added. In the comment objects 731 and 831 corresponding to the system comments, the account name, etc. of the user who started viewing (entered) are displayed. Also, when this viewing is the first viewing on the day of the corresponding distributor's live distribution, the server 10 updates (adds 1) the number of viewing days of the corresponding record in the relationship parameter management table 413.

[0085] The basic operations of the live streaming service have been described above. Next, the operations related to the management of the viewer fan levels for the streamer will be described. FIG. 18 is a diagram for explaining the conditions for each of the multiple fan levels in this example. As shown, 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 become the viewer of the corresponding fan level (the level goes up). For example, for the fan level "1", two conditions are set: condition 1, "consume 10 or more coins, watch for 1.5 hours or more, and enter 4 or more comments", and condition 2, "consume 100 or more coins". A user who satisfies any one of these two conditions will become a viewer at the fan level "1". Also, for example, for the fan level "4", three conditions are set: condition 1, "consume 1000 or more coins, watch for 5 hours or more, watch for 4 days or more, and enter 35 or more comments", condition 2, "consume 3000 or more coins, watch for 2 hours or more, and enter 5 or more comments", and condition 3, "consume 5500 or more coins". A user who satisfies any one of these three conditions will become a viewer at the fan level "4".

[0086] In this example, the conditions corresponding to the fan levels may vary based on the streamer information regarding the streamer, the viewer information regarding the viewer, or the combined information regarding the combination of the streamer and the viewer, etc. For example, the conditions corresponding to the fan levels become easier to satisfy as the rank of the streamer is lower (for example, the condition values become lower). Also, for example, the conditions corresponding to the fan levels vary according to the residential area of the viewer (for example, the conditions for viewers in a specific residential area are easier to satisfy). Also, for example, the conditions corresponding to the fan levels are easier to satisfy in the target year and month when the viewer watches the live stream of the corresponding streamer for the first time.

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

[0088] In this example, the comment objects 731 and 831 corresponding to the viewer's actions (specifically, entering the room (starting viewing), as well as inputting comments, tags, likes, and items) are decorated according to the viewer's fan level. For example, such comment objects 731 and 831 are added with icons corresponding to the viewer's fan level and the character colors corresponding to the fan level are applied.

[0089] In this example, for a predetermined upper fan level, it may be made invalid for a certain period from the beginning of each month and become valid from a specific timing in the middle. In this case, for example, the conditions corresponding to the fan level that becomes valid at a specific timing (e.g., the 15th) of each month are such that viewers who meet the conditions before the fan level becomes valid will not be upgraded to the fan level until the fan level becomes valid (until the specific timing). By doing so, it can be suppressed that a very large number of viewers with a high fan level occur at an early stage of each month and other general viewers decline.

[0090] The operations related to the management of the viewer's fan level for the broadcaster have been described above. Next, the operations when the broadcaster ends the live broadcast will be described. As described above, when the 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 distribution points for the corresponding broadcast. In this example, the number of distribution 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 distribution points increases as the number of viewers (maximum value), the number of likes, the number of comments, and the number of item points increases. The calculated number of distribution points is set in the corresponding record of the distribution management table 412.

[0091] The operations when the broadcaster ends the live broadcast have been described above. Next, the operations when determining the broadcaster's rank will be described. In this example, the rank for the current day is determined (updated) based on the number of distribution points obtained by the user on the previous day. FIG. 19 is a flowchart illustrating the processing executed by the server 10 when updating the rank of each user. These processes are executed every day at midnight (for example, 3:00 am every day).

[0092] First, as shown in the figure, the server 10 calculates the number of distribution points obtained by each user on the previous day (step S100). The number of distribution points obtained by a specific user on the previous day is calculated by referring to the broadcaster user account, the broadcast start date and time, and the number of distribution points in the distribution management table 412. Note that when a user conducts multiple broadcasts in one day, the number of distribution points obtained in each of the multiple broadcasts is totaled.

[0093] In this way, when the number of distribution points of each distributor for the previous day is calculated, subsequently, the server 10 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 (multiplier). In this example, as shown in the figure, when the number of special fans is 2 to 4, the distribution point bonus is such that the number of distribution points becomes 101% (multiplied by 1.01). 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 (multiplier) is 102%, and thereafter, as the number of special fans increases, the distribution point bonus (multiplier) becomes larger, which is advantageous for the distributor.

[0094] Also, in this example, a bonus is added to the distribution points according to the total value of the email points of each of the plurality of viewers. For example, when the total value of the email points reaches 5000 points or more, a bonus of 500 points is added to the distribution points, and when the total value of the email points reaches 10000 points or more, a bonus of 1000 points is added to the distribution points. The bonus becomes larger as the number of email points increases, which is advantageous for the distributor. Note that in other examples of this embodiment, the bonus for the distribution points based on the number of email points may not be applied, and only the bonus for the distribution points based on the number of special fans may be applied. Also, instead of, or in addition to, the bonus for the distribution points based on the number of special fans, a bonus may be added to the number of distribution points according to the total value of the fan level values.

[0095] In addition, the addition of the bonus based on the number of distribution points is an example of the reward for the distributor. In other examples of the present embodiment, various rewards can be given to the distributor based on the fan level of each of a plurality of viewers. For example, as the reward for the distributor, a bonus for the reference diamond number described later may be added, or the right to participate in a special event may be granted.

[0096] When the bonus for the number of distribution points is added in this way, next, the server 10 updates the rank meter value of each user (step S120). FIG. 21 is a diagram for explaining the update rule of the rank meter value. As shown in the figure, in this example, the rank meter value varies based on the rank within the rank band of the number of distribution points of each user on the previous day.

[0097] Specifically, as shown in FIG. 21, the update rule of the rank meter value is as follows. First, when the rank of the number of distribution points within the rank band is included in the top 10%, the variation of the rank meter value is "+2" (an increase of 2 points). Similarly, when the rank is included in the top 11 - 30% (the remaining 20% excluding the top 10% from the top 30%), the variation is "+1", when the rank is included in the middle 30% (the 31st - 60th), the variation is "±0" (no increase or decrease), and when the rank is included in the bottom 40%, the variation is "-1" (a decrease of 1 point). In addition, when no distribution was performed on the previous day, regardless of the rank within the rank band, the variation of the rank meter value is "-1".

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

[0099] Returning to the flowchart of FIG. 19, when updating the rank meter value for each user, next, the server 10 updates the rank based on the updated rank meter value (step S130). FIG. 22 is a diagram for explaining the correspondence between the updated rank content and the required rank meter value. As shown in the figure, whether ranking up across rank bands (in other words, ranking up from the top rank within each rank band) or ranking up within the same rank band (in other words, ranking up from a rank other than the top rank within each rank band), the required rank meter value is +3. That is, a user belonging to the top rank within each rank band (for example, A3) will rank up to the bottom rank within the immediately higher rank band (for example, S1) when the rank meter value becomes +3, and a user belonging to a rank other than the top rank within each rank band (for example, B2 or B1) will rank up to the immediately higher rank within the same rank band (for example, B3 or B2) when the rank meter value becomes +3.

[0100] Similarly, as illustrated in FIG. 22, whether ranking down within the same rank band (in other words, ranking down from a rank other than the bottom rank within each rank band) or ranking down across rank bands, the required rank meter value is -3. That is, a user belonging to a rank other than the bottom rank within each rank band (for example, B3 or B2) will rank down to the immediately lower rank within the same rank band (for example, B2 or B1) when the rank meter value becomes -3, and a user belonging to the bottom rank within each rank band (for example, A1) will rank down to the top rank within the immediately lower rank band (for example, B3) when the rank meter value becomes -3. In this way, in this example, the required rank meter value is made equal for ranking up / down across rank bands and ranking up / down within the same rank band. However, as another example, in order to suppress rapid ranking up / down in a short period, for the case of ranking up / down across rank bands, the absolute value of the required rank meter value may be made larger 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 the user for whom the rank has been updated (the user for whom rank up / down has occurred) is cleared to 0.

[0102] The operations for determining the rank of the distributor have been described above. Next, the operations for awarding diamonds to the user will be described. In this example, diamonds, which are the rewards for the user as a distributor, are awarded based on the previous day's distribution time and rank (the rank on the previous day). FIG. 23 is a flowchart illustrating the processing executed by the server 10 when awarding diamonds to each distributor. These processes are executed at midnight every day, for example, at a time earlier than the time when the ranks of each user illustrated in FIG. 19 are updated (for example, 0:00 am every day).

[0103] First, as illustrated, the server 10 calculates the previous day's distribution time of each user (step S200). Specifically, the previous day's distribution time of a specific user is calculated by referring to the distributor user account, distribution start date and time, and distribution time in the distribution management table 412. When a user has performed multiple distributions in one day, the distribution times of each of the multiple distributions are totaled.

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

[0105] The operation for assigning a diamond to a user has been described above. Next, the operation for creating a scribble as message content will be described. In this example, as described above, an event for creating a scribble for the distributor is held four times a year.

[0106] FIG. 24 illustrates a fan letter screen 300. In this example, the screen 300 is a screen for viewing a scribble (fan letter) for a specific distributor and starting to edit a message for the scribble. For example, the fan letter screen 300 corresponding to the specific distributor is displayed via the profile screen of the specific distributor or the screen for the family members of the specific distributor. Also, in this example, only the special fans of the corresponding distributor (that is, viewers with a fan level of "4" or higher) can input messages, and the fan letter screen 300 is displayed on the user terminal 30 of the corresponding distributor himself / herself and the special fans of the distributor, while it 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 scribble (in this example, the combination of the calendar year and season), and an information display area 320 located below the area 310 for displaying information corresponding to the scribble selected via the area 310.

[0108] The selection area 310 is configured to be able to select one piece of scribbling from the scribblings created so far and the scribbling being created at that time (the scribbling during the message input reception period). In the said area 310, the display of the selectable scribbling is switched by a flick operation or a slide operation in the left - right direction or the like. In the fan letter screen 300 of FIG. 24, in the selection area 310, the scribbling corresponding to "2021 SUMMER" (summer of 2021) is selected. In this example, the corresponding sender himself / herself can only select the scribblings created so far (published scribblings) in the selection area 310 and cannot select the scribbling being created (not displayed in the selection area 310).

[0109] The fan letter screen 300 of FIG. 24 corresponds to the state where the scribbling (summer of 2021) selected via the selection area 310 is being created (that is, the state in the middle of the period from the message input reception start date and time to the reception end date and time). In this case, in the information display area 320, as shown in the figure, the scribbling - in - progress object 330 is arranged.

[0110] As shown in the figure, the scribbling - in - progress object 330 displays the text "Let's send a fan letter to xxx" ("xxx" is the sender's account name) and information regarding the viewable date (the text "It will be sent on October 1st"), and at its lower right corner, the entered viewer number display object 332 is arranged. The said object 332 displays the number of message inputs at that time (30 in the example of FIG. 24). In this example, one viewer can input one message, and the number of message inputs means the number of viewers who have input messages. In other examples of this embodiment, one viewer may be able to input multiple messages. Also, in this example, the viewable date of the scribbling is set to the day after the message input reception end date and time.

[0111] When the in-production overlay object 330 is selected, instead of the fan letter screen 300, a message editing screen 500 illustrated in FIG. 25 is displayed. As shown in the figure, the screen 500 has a message input area 510 for inputting the content of the message, a character selection area 520 for selecting the type of character to decorate the message in the overlay, a preview button 530, and a temporary save button 540.

[0112] In this example, the upper limit of the number of characters included in the message is set for each fan level. Specifically, the upper limit of the number of characters increases as the fan level increases. The message input area 510 is configured to be able to input a message within the range of the upper limit of the number of characters corresponding to the fan level of the corresponding viewer.

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

[0114] When the preview button 530 is selected, the preview screen 600 illustrated in FIG. 26 is displayed overlaid on the message editing screen 500. As shown in the figure, 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 that shows the appearance of the message reflected in the caption, and the content input through the message editing screen 500 at that time is reflected. Specifically, the content of the message input at that time is reflected in the message object 610, and the selected character is arranged at its upper end. In addition, the corresponding viewer's profile image and account name are displayed on the message object 610. The viewer can confirm the appearance of the actual message reflected in the caption through the object 610.

[0115] When the post button 620 is selected, the input of the message by the viewer is finalized. Specifically, in the message management table 415, for the corresponding record (a record created according to temporary storage or a newly created record if temporary storage is not performed), values corresponding to each field are set. In this case, a value indicating "finalized" is set in the finalized flag. In this example, once the message is finalized, it cannot be edited, but the corresponding viewer can confirm the finalized message through the message editing screen 500.

[0116] The reception of the message input by the viewer is continuously performed until the message input reception period ends. Then, when the reception period ends, the corresponding caption is created and published.

[0117] FIG. 27 illustrates a fan letter screen 300 in a state where a created and published handwritten note is selected in a selection area 310. In the fan letter screen 300 in this state, as shown in the figure, the published handwritten note is displayed in an information display area 320. Specifically, a header area 340 that constitutes the header of the published handwritten note and a body area 350 that is located below the area 340 and constitutes the body of the handwritten note are arranged.

[0118] In the center of the header area 340, a profile image of the sender is arranged. The background image of the header area 340 has a design corresponding to the type of handwritten note.

[0119] In the body area 350, a plurality of message objects 352 each corresponding to an individual message are arranged side by side in two columns in the vertical direction. The message object 352 has the same appearance as the message object 610 on the preview screen 600. The background image of the body area 350 has a design corresponding to the type of handwritten note.

[0120] The plurality of message objects 352 arranged in the body area 350 are arranged in descending order of the number of email points of the corresponding viewers. Specifically, in the body area 350, the message object 352 corresponding to the viewer with the most email points (the message entered by the viewer) is arranged on the left side of the first row from the top, and the message object 352 corresponding to the viewer with the second most email points is also arranged on the right side of the first row from the top. The message object 352 corresponding to the viewer with the third most email points is arranged on the left side of the second row from the top, and then arranged in the same way. In this example, when a viewer who has entered a message for the corresponding handwritten note views the handwritten note, regardless of the number of email points of the viewer, the message object 352 corresponding to the viewer is arranged at the topmost position (the left side of the top row).

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

[0122] In this example, when the number of input messages (that is, the number of viewers who input messages) is equal to or more than a predetermined value (for example, 5), the creation and publication of the compilation are performed. On the other hand, when the number of input messages is less than the predetermined value, the creation and publication of the compilation are not performed (for example, a predetermined image is displayed in the information display area 320 of the fan letter screen 300).

[0123] Also, in this example, the created compilation is published not only to the corresponding distributor but also to all special fans of the distributor. Note that in other examples of this embodiment, the created compilation is published only to the viewers who input messages among the special fans. Also, in still other examples of this embodiment, the created compilation may be published to all users.

[0124] In the above example, the distributor may be able to edit the caption for himself / herself. For example, during a predetermined period before the created caption is published, or during a predetermined period after publication, the distributor can delete (or make invisible) the message included in the caption, and may also be able to input comments or stamps (images) by the distributor himself / herself. Comments etc. input by the distributor himself / herself are arranged, for example, in the header area 340 that constitutes the header of the caption.

[0125] In the above example, only special fans with a fan level of "4" or higher can input a message for the caption, the upper limit of the number of characters included in the message is set based on the fan level, and in the published caption, the message object 352 is arranged based on the number of email points. However, "fan level" and "number of email points" are examples of relational parameters regarding the relationship between the distributor and the viewer. In other examples of this embodiment, based on the values of other parameters, the input of the message can be controlled, and the arrangement of the message can be controlled. For example, if it is a family member of the corresponding distributor, they may be able to input a message for the caption. Also, the control based on the value of the relational parameter includes controls 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 caption can be performed based on the value of the relational parameter.

[0126] In the above example, the message was decorated by the character, but instead of or in addition to this, various images (including photos) may be used to create and edit the message object 352. For example, such images are used for decorating the message, as the background of the message, and as the main body of the message. Also, for example, such images are selected from images prepared in advance by the operation side of the live distribution service, or are selected from images held by the viewer.

[0127] In the above example, the message for the dedication is composed of characters, but it may also be composed of video or audio. In this case, the format of the message content is not limited to the dedication as described above, and it can be configured as various forms of content. For example, the message content is composed of the combination of temporally continuous videos or audios. In this case, according to the number of viewer's email points, the temporal position of the corresponding message (video or audio) can be determined.

[0128] In the above example, when the number of viewers who input messages is large, the dedication may be split and generated. For example, even during the reception period of message input, each time the number of input messages reaches a predetermined value (for example, 30), the split dedication may be generated. Or, when the reception period of message input ends and the number of messages is equal to or more than the predetermined value, the dedication may be split and generated. In this case, the messages included in each of the multiple dedications are distributed according to, for example, the viewer's fan level (split into a dedication corresponding to a viewer with a high fan level and a dedication corresponding to a viewer with a low fan level). The split dedication may be individually selectable as another type of dedication through, for example, the selection area 310 of the fan letter screen 300.

[0129] In the above example, the messages of viewers blocked by the distributor may not be displayed in the dedication. For example, the message input by the blocked viewer is included in the dedication when the viewer browses it, but not included in the dedication when other users browse it.

[0130] In the above example, during the reception period of message input, for viewers of special fans whose message input is undetermined, the input of messages may be encouraged. For example, during this period, viewers of special fans who have finished watching the live broadcast of the corresponding distributor may be guided to a message editing screen 500 for editing a message for writing on the corresponding distributor (displayed on the viewer terminal 30). Also, such guidance to the message editing screen 500 may be performed when the live broadcast is watched until the end.

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

[0132] In the above example, a live distribution service of a video composed of an image input via the camera of the distributor terminal 30 and a voice input via the microphone, and the viewing thereof is provided. However, in other examples of the present embodiment, a video provided by the distributor is stored in advance, and an on-demand type video distribution service that individually distributes the video in response to a request from a viewer is provided.

[0133] Since the video distribution server 10 of the present embodiment described above generates message content (writing on) including a plurality of messages for the distributor input by the viewer based on the values of relational parameters (fan level and number of email points) regarding the relationship between the viewer and the distributor, 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 considering the relationship between users.

[0134] In the above-described embodiments, message content including messages from viewers to distributors in a video distribution service was generated. However, in other embodiments of the present invention, it may be configured to generate message content including messages from a second user to a first user in other services. For example, in a community service (including an online salon), input from participants (second users) of a community to the owner (first user) of the community may be received, and message content including these messages may be generated. Then, based on the values of relational parameters (such as rank, level, etc.) regarding the relationship between the owners and participants of these communities, the generation of the message content is performed.

[0135] The processes and procedures described in this specification can be implemented by software, hardware, or any combination thereof, in addition to those explicitly described. For example, the processes and procedures described in this specification can be realized by implementing the logic corresponding to the processes and procedures in media such as integrated circuits, volatile memories, non-volatile memories, and magnetic disks. Also, the processes and procedures described in this specification can be implemented as a computer program corresponding to the processes and procedures and can be executed on various computers.

[0136] Even if it is described that the processes and procedures described in this specification are executed by a single device, software, component, or module, such processes or procedures can be executed by a plurality of devices, a plurality of software, a plurality of components, and / or a plurality of modules. Also, the software and hardware elements described in this specification can be realized by integrating them into fewer components or decomposing them into more components.

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

Explanation of Signs

[0138] 10 Video distribution server 11 Computer processor 15 Storage (memory device) 20 Communication network 30 User terminal 41 Information storage management unit 411 User information table 412 Distribution management table 413 Relational parameter management table 414 Content information table 415 Message management table 43 Management function control unit 45 Video distribution service control unit 47 Content generation control unit 60 Top screen 70 Distributor screen 80 Viewer screen 100 Distribution preparation screen 200 Item selection screen 300 Fan letter screen 500 Message editing screen 600 Preview screen

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 some of the 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 presenting the generated predetermined content to at least the first user.

8. A system according to any preceding claim.

9. The process of generating the predetermined content includes stopping presentation of the predetermined content to the first user when a number of second users who have input messages is equal to or less than a first predetermined value. The system of claim 8.

10. 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.

10. A system according to any preceding claim.

11. the process of generating the predetermined content includes, when a number of second users who input messages is equal to or greater than a second predetermined value, dividing and generating the predetermined content.

11. A system according to any preceding claim.

12. The predetermined content is a collection of messages.

12. A system according to any preceding claim.

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

13. A system according to any preceding claim.

14. 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 13.

15. 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; generating the predetermined content includes generating the predetermined content based at least on values ​​of the predetermined parameters of at least some of the second users; method.

16. 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 some of the second users. program.

Citation Information

Patent Citations

  • Information processing apparatus, information processing method, and program

    JP2013246682A

  • Social service server

    JP2014219853A

  • SNS server performing timeline display control and timeline display control method

    JP2015011660A

  • Server, method, and program for providing message collection system

    JP2015133000A

  • Device and method for letter written by plural persons with signature, device and method for supporting article presentation, and date managing device

    JP2001297051A