System, method, program and device for distributing contents

Abstract

To enhance fun accompanied by an input of objects by a viewing user of content.SOLUTION: A content 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 a content distribution service for distributing and viewing contents is provided for a user via the user terminal 30. The server 10 is configured to: implement a lottery in responce to an input of an object by a viewing user; give a remuneration to a distribution user on the basis of a result of the lottery, which in turn the viewing user and distribution user are enabled to enjoy the lottery in responce to the input of the object.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for distributing content. [Background technology]

[0002] Conventionally, various services have been provided for distributing content composed of images and / or audio. In some of these services, a gifting function has been introduced that enables content viewing users to input items (see, for example, Patent Document 1 below). With this function, for example, images and video effects according to the type of input item are displayed on the content, enabling viewing users to participate in the content. [Prior art documents] [Patent documents]

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

[0004] However, the gifting function described above only displays a predetermined item depending on the type of item entered, which can make the content progression monotonous. Therefore, it is desirable to realize a mechanism that improves the enjoyment of entering such items and other objects.

[0005] One object of the embodiment of the present invention is to improve the enjoyment that accompanies the input of objects by a user viewing content. Other objects of the embodiment of the present invention will become apparent by reading the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system for distributing content, comprising one or more computer processors, wherein the one or more computer processors perform the steps of accepting input of objects by viewing users who view the content, conducting a lottery in accordance with the input of the objects, and awarding a reward to a distribution user who distributes the content based on the results of the lottery.

[0007] A method according to one embodiment of the present invention is a method for distributing content that is executed by one or more computers and includes the steps of accepting input of an object by a viewing user who views the content, conducting a lottery in accordance with the input of the object, and awarding a reward to a distribution user who distributes the content based on the result of the lottery.

[0008] A program according to one embodiment of the present invention is a program for distributing content, which causes one or more computers to execute the steps of accepting input of an object by a viewing user who views the content, conducting a lottery in accordance with the input of the object, and granting a reward to a distribution user who distributes the content based on the results of the lottery.

[0009] An apparatus according to one embodiment of the present invention is an apparatus for distributing content, and includes means for accepting input of an object by a viewing user who views the content, means for conducting a lottery in accordance with the input of the object, and means for granting a reward to a distribution user who distributes the content based on the result of the lottery. [Effects of the Invention]

[0010] Various embodiments of the present invention enhance the enjoyment associated with inputting objects by users viewing content. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing a schematic configuration of a network including a content distribution server 10 according to an embodiment of the present invention. [Figure 2] FIG. 15 is a diagram illustrating an example of information managed by a user information table 1511. [Figure 3] FIG. 10 is a diagram for explaining the rank of broadcast users. [Figure 4] FIG. 15 is a diagram illustrating an example of information managed by a distribution management table 1512. [Figure 5] FIG. 15 is a diagram illustrating an example of information managed by a distribution user-specific viewing user management table 1513. [Figure 6] FIG. 10 is a diagram illustrating the conditions for each of a plurality of fan levels. [Figure 7] FIG. 15 is a diagram illustrating information managed by a gift item information table 1514. [Figure 8] FIG. 15 is a diagram illustrating an example of information managed by an event information table 1515. [Figure 9] FIG. 15 is a diagram illustrating an example of information managed by an event-specific distributor user management table 1516. [Figure 10] FIG. 15 is a diagram illustrating an example of information managed by an event-specific viewing user management table 1517. [Figure 11] FIG. 2 is a diagram illustrating a top screen 50. [Figure 12] FIG. 10 is a diagram illustrating an example of display content in an individual display area 541. [Figure 13] FIG. 6 is a diagram illustrating a distribution preparation screen 60. [Figure 14] FIG. 7 is a diagram illustrating a distribution screen 70. [Figure 15] FIG. 10 is a diagram illustrating an example of a viewing screen 80. [Figure 16] FIG. 10 is a diagram illustrating an example of a viewing screen 80 on which a gift selection screen 200 is superimposed. [Figure 17] FIG. 2 is a diagram illustrating a gift selection screen 200. [Figure 18] 10 is a flowchart illustrating a process executed by the server 10 when updating the rank of each user. [Figure 19] FIG. 10 is a diagram illustrating an example of an update rule for a rank meter value. [Figure 20] 10 is a flowchart illustrating a process executed by the server 10 when granting diamonds to each user. [Figure 21] FIG. 10 is a diagram illustrating a distribution screen 70 and a viewing screen 80 when a distributor user is participating in an event that is the subject of an event lottery. [Figure 22] 10 is a flowchart illustrating a process executed by the server 10 in response to an input of a gift item eligible for an event lottery. [Figure 23] FIG. 10 is a diagram illustrating an example of the box effects set for each reward and their appearance probability. [Figure 24] FIG. 2 is a diagram illustrating an example of an individual display area 2041 in which a consecutive miss count gauge 2042 is arranged. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0030] The delivery control unit 112 is configured to execute various processes for controlling the delivery of content. For example, the delivery control unit 112 is configured to deliver content provided by a delivery user who delivers the content to multiple viewing users. For example, the delivery control unit 112 presents a viewing screen for viewing the content to each of the multiple viewing users, and transmits, for example, screen data and control data of the viewing screen to each user terminal 30 (hereinafter sometimes referred to as viewing terminal 30) of the multiple viewing users.

[0031] In this embodiment, the distribution control unit 112 is configured to accept input of an object by a viewing user who is viewing content. The object may include, for example, an item, a like, a comment, etc., and the input may be made via the viewing screen. Typically, a display corresponding to the input object is made on the content.

[0032] The distribution control unit 112 is also configured to execute a lottery in response to the input of the object. The lottery is executed by, for example, determining one lottery object according to the probability set for each of a plurality of lottery objects.

[0033] Furthermore, the distribution control unit 112 is configured to grant a reward to the broadcast user based on the result of the lottery. For example, the distribution control unit 112 grants the broadcast user a reward corresponding to one lottery target selected from multiple lottery targets. For example, the multiple lottery targets may include a losing lottery target, and if the losing lottery target is selected, the distribution user may not be granted a reward.

[0034] In this way, the content distribution server 10 in this embodiment executes a lottery in response to the input of an object by a viewing user and grants a reward to the distribution user based on the result of the lottery, allowing the viewing user and the distribution user to enjoy the lottery in response to the input of an object. In other words, the server 10 improves the enjoyment associated with the input of an object by a content viewing user.

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

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

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

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

[0039] In this embodiment, rewards granted to broadcast users include various types of rewards, such as items (including points, coins, characters, cards, in-service currency, etc.), parameter values, etc. The rewards also include effects that occur on the content broadcast by the broadcast user (for example, effects that increase the number of points earned, etc.).

[0040] In this embodiment, if a predetermined condition is satisfied, a lottery may not be held even if an object is input. The condition may include, for example, a condition that is satisfied depending on the type of object input. In other words, the distribution control unit 112 may be configured to hold a lottery when the type of input object is a first type, but not to hold the lottery when the type of input object is a second type. This configuration prompts the viewing user to input a specific type of object.

[0041] Furthermore, the above conditions for not holding a lottery include, for example, a condition that is met when the number of times a lottery has been held reaches a threshold. For example, the distribution control unit 112 is configured to hold a lottery when the number of times a lottery has been held in a predetermined period is less than a threshold, but not hold a lottery when the number of times the lottery has been held reaches the threshold. The number of times a lottery has been held may be managed in association with a broadcast user, a viewing user, a combination thereof, or a distribution (in other words, whether or not a lottery needs to be held may be controlled based on the number of times a lottery has been held per broadcast user, per viewing user, a combination thereof, or per distribution). This configuration prevents items for holding a lottery from being entered excessively frequently.

[0042] In this embodiment, the lottery result may be a winning result when a predetermined condition is satisfied. For example, the lottery is executed by determining one lottery target from a plurality of lottery targets, and the distribution control unit 112 may be configured to determine a predetermined winning lottery target included in the plurality of lottery targets as the single lottery target when a predetermined condition is satisfied. This configuration encourages the viewing user to take an action that satisfies the condition for the lottery result to be a winning result.

[0043] In this case, the distribution control unit 112 can be configured to vary the value of the parameter in a predetermined direction in response to the execution of the lottery, and the above condition for the lottery result to be a winning one can be configured as a condition that is met in response to the value of the parameter reaching a threshold. For example, the parameter is incremented by a predetermined value (e.g., 1) in a positive direction in response to the execution of the lottery, and when the value of the parameter reaches the threshold, the distribution control unit 112 determines a winning lottery object from among multiple lottery objects. With this configuration, the lottery result can be a winning one by repeatedly executing the lottery, and the viewing user is prompted to input an object.

[0044] Furthermore, in this case, the distribution control unit 112 may initialize the value of the parameter when a winning lottery target is determined from among multiple lottery targets, and may vary the value of the parameter when a losing lottery target is determined. With this configuration, even after the lottery result is a winning lottery target, the value of the parameter may be determined to be a winning lottery target again if the value of the parameter reaches the threshold value, further encouraging the viewing user to input an object.

[0045] Furthermore, the distribution control unit 112 can be configured to execute a first lottery to determine whether the result of the first lottery is a win or a loss, and if the result of the first lottery is a win, execute a second lottery to determine a reward to be granted to the distribution user from among multiple rewards. Each lottery is conducted according to the probability set for each lottery item (win or loss, and each reward). This configuration allows the lottery to be conducted in two stages.

[0046] Furthermore, the multiple rewards to be granted to the broadcasting user may include a first reward that adds items accumulated in the reward pool (including points, coins, in-service currency, etc.), and a second reward that acquires all of the items accumulated in the reward pool. For example, the broadcasting control unit 112 is configured to add the number of items accumulated in the reward pool as the first reward, and to grant the number of items accumulated in the reward pool to the broadcasting user as the second reward. This configuration provides the user with the fun of adding items to the reward pool in response to the execution of a lottery and acquiring those items.

[0047] In this case, in response to the determination of the second reward (i.e., the granting of all items accumulated in the reward pool), the number of items accumulated in the reward pool may be set to an initial value greater than or equal to 1. This configuration prevents a situation in which the second reward is determined through a lottery but no items are granted.

[0048] Next, a specific example of one aspect of the content distribution server 10 of this embodiment having such functions will be described. In this example, the content distribution service provided by the server 10 is configured as a service for live distribution (live streaming) of content made up of video and audio of a distribution user input (captured) via a camera and microphone possessed by the distribution terminal 30. First, in this example, the information managed by each table included in the various tables 151 will be described.

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

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

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

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

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

[0054] 4 illustrates information managed by distribution management table 1512 in this example. Distribution management table 1512 manages information related to individual distributions, and as shown in the figure, manages information such as a "distribution user account" identifying the distribution user, a "distribution start date and time" which is the date and time the distribution started, a "distribution duration" which is the duration (elapsed time) since the distribution started, the "number of viewing users (current value and maximum value)", the "number of comments" which is the number of comments entered by viewing users while the content was being distributed, the "number of likes" which are the number of "likes" entered by viewing users while the content was being distributed, the "number of coins consumed" which is the number of coins consumed in response to gift item entries by viewing users while the content was being distributed, the "number of support points" which is the total number of support points granted for this distribution, and "distribution tag information" which is information related to distribution tags granted for this distribution, in association with a "distribution ID" which identifies an individual distribution (content).

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

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

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

[0058] 7 illustrates information managed by the gift item information table 1514 in this example. The gift item information table 1514 manages information related to gift items (objects) that can be input by viewing users, and as shown in the figure, manages information such as a "name," a "required number of coins" indicating the number of coins required for input, an "event ID" identifying the corresponding event, and an "event lottery target flag" indicating whether the item is eligible for an event lottery, in association with a "gift item ID" that identifies an individual gift item.

[0059] The event ID is set when the corresponding gift item is an event-exclusive item (an item that can only be entered for content distributed by broadcast users participating in the event during the event period). The event lottery, which will be described in more detail below, is held during the distribution of content by broadcast users participating in the event that is the subject of the event lottery.

[0060] FIG. 8 illustrates information managed by event information table 1515 in this example. Event information table 1515 manages information related to events held in the content distribution service of this example, and as shown, manages information such as a "name," a "start date" which is the first day of the period during which the event is held, an "end date" which is the last day of the period, "participation condition information" which is information related to the conditions for participating in the event, "reward condition information" which is information related to rewards that can be obtained in the event, an "event lottery winning probability" which is the probability of winning the event lottery, and an "initial value of the number of jackpot accumulated points" which is the initial value of the number of event points accumulated in the jackpot (reward pool), in association with an "event ID" which identifies each individual event. The event lottery winning probability and the initial value of the number of jackpot accumulated points are set when the event is subject to an event lottery. The participation condition information includes the rank of broadcast users who are eligible to participate in the event. The event lottery winning probability and the initial value of the number of jackpot accumulated points are set when the event is subject to an event lottery.

[0061] 9 illustrates information managed by event-specific broadcast user management table 1516. Event-specific broadcast user management table 1516 manages information about broadcast users for each event, and as shown, associates information such as the "event point count" which is the total number of event points acquired by the broadcast user during the event period, the "jackpot accumulated point count" which is the number of event points accumulated in the jackpot, "buff mode (level 1) remaining time" which is the remaining time when buff mode (level 1) has occurred, "buff mode (level 2) remaining time" which is the remaining time when buff mode (level 2) has occurred, "buff mode (level 3) remaining time" which is the remaining time when buff mode (level 3) has occurred, and "ranking" which is the broadcast user's ranking in the event, in association with a combination of an "event ID" which identifies the event and a "broadcast user account" which identifies the broadcast user participating in the event. The number of jackpot accumulated points, the remaining time in buff mode (level 1), the remaining time in buff mode (level 2), and the remaining time in buff mode (level 3) are set when the event is subject to an event lottery.

[0062] 10 illustrates information managed in this example by event-specific viewing user management table 1517. Event-specific viewing user management table 1517 manages information related to viewing users for combinations of events and broadcast users, and as shown, manages information such as the "number of event lottery wins," which is the number of times the event lottery run by the viewing user during the broadcast of the corresponding content has resulted in a win, and the "number of consecutive event lottery losses," which is the number of consecutive event lottery losses, in association with a combination of an "event ID" that identifies the event, a "distributor user account" that identifies the broadcast user, and a "viewing user account" that identifies the viewing user.

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

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

[0065] The selection area 52 is an area for selecting the content to be displayed in the list display area 54. Specifically, when "Following" is selected in the selection area 52, the list display area 54 displays a list of broadcasts (content currently being broadcast) of other users the user is following. Similarly, when "Popular" is selected in the selection area 52, the list display area 54 displays a list of broadcasts with a large number of viewing users. Furthermore, when "Featured" is selected in the selection area 52, the list display area 54 displays a list of popular broadcasts (for example, broadcasts with a large number of comments and likes). Furthermore, when "All" is selected in the selection area 52, all broadcasts are subject to list display in the list display area 54.

[0066] As shown in the figure, in the list display area 54, a plurality of individual display areas 541, each displaying information about an individual distribution, are arranged in two columns vertically. The individual display area 541 is configured so that viewing of the corresponding distribution can be started (playback of the corresponding content is started) in response to a user selection. The list display area 54 is configured so that the displayed individual display area 541 can be switched by a flick operation or a slide operation in an up or down direction, for example.

[0067] 12 illustrates an example of the display content of individual display area 541. Individual display area 541 displays an image preset by the content's distributor user, the distributor user's account name, the number of viewing users (current value), etc., and, as illustrated, a first tag object 5411 and a second tag object 5412 are arranged side by side in the left-right direction at the bottom edge. First tag object 5411 displays classification text (managed in user information table 1511) that is the distributor user's classification set by the distributor user themselves in the form of a hashtag (a format in which "#" is added to the beginning of the string) (in the example of FIG. 12, it is displayed as "#bigeaterdistribution"). Second tag object 5412 also displays the latest distribution tag assigned by the viewing user to the corresponding distribution, also in the form of a hashtag (in the example of FIG. 12, it is displayed as "#curry").

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

[0069] When the distribution start button 68 is selected, distribution of the content is started, specifically, content data consisting of video and audio input (captured) via the camera and microphone of the distribution terminal 30 is started to be transmitted to the server 10. In addition, in response to the start of content distribution, a new record is inserted in the distribution management table 1512.

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

[0071] The video display area 71 displays the content to be distributed, that is, the image input via the camera of the distribution terminal 30. The distribution user usually takes a picture of themselves via the in-camera of the distribution terminal 30, and in this case, the distributed content includes an image of the distribution user themselves.

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

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

[0074] The tag display area 74 displays information about the distribution tags assigned to this distribution, and specifically, in this area 74, multiple tag objects 741, each corresponding to an individual tag, are arranged side by side in the horizontal direction.

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

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

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

[0078] The comment input area 862 is an area where a viewing user can input a comment or a distribution tag. While the input mode switching button 861 is not selected, the comment input area 862 is in the normal comment input mode. In the comment input mode, when a character string is input into the comment input area 862 and a confirmation operation is performed, the character string is transmitted as a user comment, and a comment object 731, 831 corresponding to the user comment is added to the comment display area 73, 83 of the distribution screen 70 and the viewing screen 80 at the corresponding distribution terminal 30 (the user terminal 30 of the distribution user who distributes the content being viewed) and at each viewing terminal 30 (each user terminal 30 of multiple viewing users who view the same content). The comment object 731, 831 corresponding to the user comment displays the content of the comment (character string) along with the account name of the viewing user who entered the comment. In addition, when a user comment is input, the server 10 updates (increases by 1) the number of comments for the corresponding distribution in the distribution management table 1512.

[0079] Furthermore, when the input mode switch button 861 is selected, the comment input area 862 enters tag input mode. In tag input mode, when a character string is entered into the comment input area 862 and a confirmation operation is performed, the character string is sent as a distribution tag, and the tag is assigned to the distribution. In this example, viewing users who can input tags are limited to family members of the corresponding distribution user. Specifically, the input mode switch button 861 on the viewing screen 80 is selectable (enabled) if the viewing user is a family member of the distribution user, but is not selectable (disabled) if the viewing user is not a family member of the distribution user. Also, in this example, the number of tags that can be assigned to one distribution in a certain period of time is limited; specifically, the number of tags that can be assigned in a five-minute period is limited to three.

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

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

[0082] Furthermore, when a tag is assigned, a comment object 731, 831 corresponding to a system comment notifying the assignment of the tag is added to the comment display area 73, 83 of the corresponding distribution screen 70 and viewing screen 80. The comment object 731, 831 corresponding to the system comment displays the content of the assigned tag along with the account name of the viewing user who assigned (input) the tag, for example, a comment such as "xx tagged the distribution with "#TokyoSightseeing"." Furthermore, when a tag is assigned, distribution tag information for the corresponding distribution is updated in distribution management table 1512.

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

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

[0085] 17 illustrates a gift selection screen 200. As shown in the figure, the screen 200 has a selection area 201, a list display area 204 located below the area 201 and displaying a list of one or more gift items, a price range selection area 206 located below the area 204 for selecting the price range of the gift items to be displayed, and a purchase button 207 located in the lower right corner of the screen and serving as an object for purchasing coins. In addition, the number of coins owned by the corresponding user is displayed in the lower left corner of the gift selection screen 200.

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

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

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

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

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

[0091] In this example, the number of support points in the distribution management table 1512 is updated in real time while the content is being distributed. In this example, the number of support points is calculated based on the number of likes, the number of comments, and the number of consumed coins; the larger these values, the greater the number of support points. Also, if an event in which the broadcast user is participating is being held, in addition to the number of support points, the number of event points in the event-specific broadcast user management table 1516 is updated. The formula for calculating the number of event points may be the same as the formula for calculating the number of support points, or it may be different. When the broadcast user selects the stop distribution button 76 on the distribution screen 70, the distribution of the content ends.

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

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

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

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

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

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

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

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

[0100] The above describes the process for awarding diamonds to a broadcast user. Next, we will explain the event lottery in this example content distribution service. The event lottery is held for content distributed by broadcast users participating in the event during the event period that is the subject of the event lottery.

[0101] 21 illustrates a distribution screen 70 and a viewing screen 80 when a broadcast user is participating in an event that is the subject of an event lottery. On the screens 70 and 80 in this state, as shown in the figure, a jackpot object 77, 87 that displays the number of event points accumulated in the jackpot is placed below the viewing user information display area 75, 85. The number of event points accumulated in the jackpot is managed in an event-specific broadcast user management table 1516, and its initial value is managed in an event information table 1515. In this example, the initial value of the number of event points accumulated in the jackpot is set to the minimum value (e.g., 1,000 points) as a reward awarded when the jackpot is unlocked.

[0102] For content distributed by a broadcasting user participating in an event eligible for the event lottery, it is possible to input eligible gift items for the event lottery. Note that the eligible gift items for the event lottery (identified by referencing the event lottery eligible flag in the gift item information table 1514) may be displayed in a manner that allows them to be distinguished from other gift items in the list display area 204 of the gift selection screen 200 output on the user terminal 30 of the viewing user who is viewing the content.

[0103] 22 is a flowchart illustrating the process executed by the server 10 in response to the input of a gift item to be entered into the event lottery. As shown in the figure, the server 10 first executes a visual effect display corresponding to the input gift item on the content (step S300). As described above, the visual effect display includes the display of an image and video effect corresponding to the input gift item.

[0104] Next, if the number of times the viewing user has won the event lottery for this event and combination of distribution user is less than an upper limit (e.g., 5 times) (YES in step S310), and the number of consecutive losses in the event lottery for the viewing user is also less than an upper limit (e.g., 10 times) (YES in step S320), server 10 determines whether the user has won or lost (step S330). The number of wins and consecutive losses in the event lottery are managed in event-specific viewing user management table 1517.

[0105] Specifically, the determination of whether the event is a win or a loss is made according to the probability of winning the event lottery set for this event (managed in the event information table 1515). Note that if the number of times the viewing user has won the event lottery has reached the upper limit (NO in step S310), the process ends.

[0106] If the result of the determination is a loss (NO in step S340), the server 10 updates the number of consecutive losses in the event lottery for the viewing user (step S350). Specifically, 1 is added to the value of the number of consecutive losses in the event lottery for the corresponding record in the event-specific viewing user management table 1517.

[0107] On the other hand, if the result of the determination is a win (YES in step S340), or if the viewing user's number of consecutive losses in the event lottery has reached the upper limit (NO in step S320), the server 10 initializes the number of consecutive losses in the event lottery (step S360). Specifically, in the event-specific viewing user management table 1517, the value of the number of consecutive losses in the event lottery for the corresponding record is set to 0. In this way, in this example, when the viewing user's number of consecutive losses in the event lottery has reached the upper limit, the same process as when the result of the determination is a win is performed, that is, a win is always determined.

[0108] Next, the server 10 determines the reward to be granted to the broadcast user (step S370), and executes a reward determination effect display on the content (step S380). Specifically, in determining the reward, one reward is determined from among a plurality of rewards according to the winning probability set for each of the plurality of rewards.

[0109] FIG. 23 illustrates the correspondence between each reward and the box effect. As shown in the figure, in this example, there are three types of rewards: "Jackpot Release," which acquires all of the event points accumulated in the jackpot; "Jackpot Addition," which adds event points to the jackpot; and "Buff Mode," which increases the event points acquired. The "Jackpot Addition" reward has levels 1 to 3, and the higher the level, the more event points are added. Similarly, the "Buff Mode" reward has levels 1 to 3, and the higher the level, the stronger the effect of the buff mode and the longer its duration.

[0110] In this example, the reward determination effect display first displays a box effect in which a box-shaped box object appears, and then the box object is opened, and a reward effect in which a reward object corresponding to the determined reward appears is displayed. In this example, as illustrated in FIG. 23, the box effect to be displayed and its appearance probability are preset for each reward. For example, if "Jackpot Release," "Jackpot Addition (Level 3)," or "Buff Mode (Level 3)" is determined as the reward, there is an 80% chance that a "Red Box" box effect will appear, a 15% chance that a "Blue Box" box effect will appear, and a 5% chance that a "Green Box" box effect will appear. Furthermore, if "Jackpot Addition (Level 2)" or "Buff Mode (Level 2)" is determined as the reward, there is an 80% chance that a "Blue Box" box effect will appear, and a 20% chance that a "Green Box" box effect will appear. Additionally, when "Jackpot Addition (Level 1)" or "Buff Mode (Level 1)" is determined as a reward, a "Green Box" box effect will appear with a 100% probability. Therefore, users can predict the type of reward they will receive with different expectations depending on the type of box effect displayed, which helps to make the broadcast more exciting.

[0111] In this example, the reward determination effect display may be started in response to an operation input by the broadcasting user (for example, an operation input on the broadcasting screen 70, etc.).

[0112] Returning to the flowchart of FIG. 22, next, the server 10 grants the determined reward to the broadcast user (step S390). For example, if the reward is "jackpot release," the event points accumulated in the jackpot are granted to the broadcast user. Specifically, the value of the number of accumulated jackpot points in the event-specific broadcast user management table 1516 is added to the number of event points in the event-specific broadcast user management table 1516, and the initial value (managed in the event information table 1515) is set to the number of accumulated jackpot points. Also, for example, if the reward is "jackpot addition," event points are added to the jackpot. Specifically, a value according to the level of the reward is added to the number of accumulated jackpot points in the event-specific broadcast user management table 1516. Also, for example, if the reward is "buff mode," buff mode is set. Specifically, the corresponding remaining time is set to the buff mode (level 1) remaining time, buff mode (level 2) remaining time, or buff mode (level 3) remaining time in the event-specific broadcast user management table 1516. If there is any remaining time in the corresponding buff mode at that time, the remaining time will be overwritten with the initial value (for example, 6 hours).

[0113] In this example, if there is remaining time in a buff mode, the corresponding buff mode occurs, and specifically, the event points earned by the broadcasting user increase. If two or more buff modes out of levels 1 to 3 occur, the buff of the more effective buff mode (the one with the highest event point increase effect) is applied, and the buff of the less effective buff mode is not applied. For example, during a period when a level 2 buff mode and a level 3 buff mode are both occurring, a level 3 buff (e.g., 2.0x) is applied, and then, when the remaining time in the level 3 buff mode runs out, if there is still remaining time in the level 2 buff mode, a level 2 buff (e.g., 1.5x) is applied. Note that the content of the applied buff may be displayed in a predetermined position in the video display areas 71 and 81 of the broadcasting screen 70 and the viewing screen 80.

[0114] When the event period ends, each broadcast user is ranked based on the number of event points they have. Specifically, the ranking is set in descending order of the number of event points they have, and the ranking of each broadcast user is registered in event-specific broadcast user management table 1516.

[0115] In the above example, the number of times a viewing user has won the event lottery for a combination of an event and a broadcast user and / or the number of consecutive losses in the event lottery may be presented to the viewing user. For example, as illustrated in FIG. 24 , a consecutive loss count gauge 2042 displaying the number of consecutive losses in the event lottery may be placed in an individual display area 2041 corresponding to a gift item eligible for the event lottery among multiple gift items displayed in list display area 204 of gift selection screen 200. The gauge 2042 has a scale that counts up the number of consecutive losses in the event lottery for the viewing user for a combination of an event and a broadcast user up to an upper limit (e.g., 10 times), and the viewing user can know the number of consecutive losses in the event lottery and the number of times remaining until the upper limit (i.e., until the event lottery result is guaranteed to be a win) via the gauge 2042. Note that the number of times the viewing user has won the event lottery may also be displayed in the individual display area 2041.

[0116] In the above example, the event lottery is executed in response to the input of the target gift item for the event lottery, but in other examples of this embodiment, instead of or in addition to this, the event lottery may be executed in response to the input of a "like" or comment by the viewing user.

[0117] In the above example, an upper limit was set on the number of times a viewing user wins the event lottery for a combination of an event and a broadcasting user, but instead of or in addition to this, an upper limit may be set on the number of times an event lottery for another unit wins. For example, an upper limit may be set on the number of times an event lottery wins for each combination of an event and a broadcasting user, the number of times an event lottery wins for each event, or the number of times an event lottery wins for each broadcast.

[0118] In the example described above, an upper limit is set on the number of consecutive losses in the event lottery for a viewing user for a combination of an event and a broadcasting user, but instead of or in addition to this, an upper limit may be set on the number of consecutive losses in the event lottery for other units. For example, an upper limit may be set on the number of consecutive losses in the event lottery for each combination of an event and a broadcasting user, and if that upper limit is reached, it may always be determined to be a win.

[0119] In the above example, the winning probability of the event lottery is set for each event. However, instead of or in addition to this, the winning probability of the event lottery may be set based on the value of a parameter associated with the broadcasting user and / or the viewing user. For example, the winning probability of the event lottery may be set higher the higher the broadcasting user's rank, or the higher the viewing user's fan level. Furthermore, the winning probability of the event lottery may be set based on the value of a parameter associated with the broadcast. For example, the winning probability of the event lottery may be set higher the greater the number of viewing users, the number of comments, the number of likes, or the number of coins consumed (the more popular the broadcast). Furthermore, the winning probability of the event lottery may be set based on the value of a parameter associated with the input gift item. For example, the greater the number of coins required, the higher the winning probability of the event lottery.

[0120] In the above example, the target gift item for the event lottery may be changed. For example, the target gift item may be determined (for example, randomly) from among a plurality of gift items at a predetermined timing (for example, when the distribution starts, or when a predetermined time has elapsed since the distribution started, etc.). Also, the viewing user may not be notified that the target gift item for the event lottery is a target gift item (for example, the target gift item for the event lottery is not displayed in a distinguishable manner from other gift items in the list display area 204 of the gift selection screen 200). In this case, the event lottery is suddenly held, which can surprise the viewing user.

[0121] In the example described above, the remaining time in buff mode is managed for each broadcast user, but it may also be managed for each broadcast. In this case, the remaining time in buff mode is cleared upon completion of the broadcast, and the corresponding buff will not be applied to the next broadcast.

[0122] In the example described above, the number of event points accumulated in the jackpot is managed per broadcast user, but it may also be managed per event. In this case, multiple broadcast users participating in the event subject to the event lottery will share one jackpot, which may increase the enjoyment of unlocking the jackpot.

[0123] In the above example, the content distribution service is configured as a service for live distribution of content consisting of video and audio of the distribution user input via the camera and microphone of the distribution terminal 30. However, as described above, the content distributed in this embodiment includes various types of digital content, such as content from various types of distribution such as radio distribution, avatar distribution, television distribution, and game distribution.

[0124] The content distribution server 10 of the present embodiment described above executes a lottery in response to the input of an object (a gift item subject to an event lottery) by a viewing user, and grants a reward (for example, a jackpot release, an additional jackpot, a buff mode, etc.) to the broadcasting user based on the result of the lottery, thereby enabling the viewing user and the broadcasting user to enjoy the lottery in response to the input of an object. In other words, the server 10 improves the enjoyment associated with the input of an object by a content viewing user.

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

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

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

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

[0129] 10 Content distribution server 11. Computer Processor 111 Management function control section 112 Distribution control section 15 Storage 151 various tables 1511 User Information Table 1512 Delivery Management Table 1513 Viewing user management table by distribution user 1514 Gift Item Information Table 1515 Event Information Table 1516 Event-specific distribution user management table 1517 Event-specific viewing user management table 20. Communication Networks 30 User terminals 40 Server-side programs 42 Terminal side program 50 Top screen 60 Distribution preparation screen 70 Streaming Screen 77 Jackpot Object 80 viewing screen 87 Jackpot Object 200 Gift selection screen 2042 consecutive miss count gauge

Claims

1. 1. A system for distributing content, comprising one or more computer processors, the one or more computer processors comprising: receiving an input of an object by a viewing user who views the content; executing a lottery in response to an input of the object; and granting a reward to the distributor user who distributes the content based on the result of the lottery. system.

2. the step of executing the lottery does not execute the lottery if a first condition is satisfied even if the object is input; The system of claim 1.

3. the first condition is satisfied when the type of the object is a first type, but is not satisfied when the type of the object is a second type; The system of claim 2.

4. the first condition is satisfied when the number of times the lottery is executed reaches a threshold value; The system of claim 2.

5. The lottery determines one lottery object from a plurality of lottery objects, The step of executing the lottery includes determining a predetermined winning lottery object included in the plurality of lottery objects as the one lottery object when a second condition is satisfied. The system of claim 1.

6. the one or more computer processors further execute a step of varying a parameter value in a predetermined direction in response to execution of the lottery; the second condition is satisfied in response to the value of the parameter reaching a threshold value. The system of claim 5.

7. The step of varying the value of the parameter initializes the value of the parameter when the predetermined winning lottery object is determined as the one lottery object, and varies the value of the parameter in the predetermined direction when a predetermined losing lottery object included in the plurality of lottery objects is determined as the one lottery object. The system of claim 6.

8. The step of holding the lottery includes holding a first lottery to determine whether the result of the first lottery is a win or a loss, and holding a second lottery to determine the reward to be granted to the broadcast user from among a plurality of rewards if the result of the first lottery is a win. The system of claim 1.

9. the plurality of rewards includes a first reward that adds an item accumulated in a reward pool, and a second reward that acquires all of the items accumulated in the reward pool; The system of claim 8.

10. The step of executing the lottery sets the number of the items accumulated in the reward pool to an initial value of 1 or more in accordance with the determination of the second reward from among the plurality of rewards via the second lottery. The system of claim 9.

11. 1. A method for distributing content, executed by one or more computers, comprising: receiving an input of an object by a viewing user who views the content; executing a lottery in response to an input of the object; and a step of awarding a reward to the distributor user who distributes the content based on the result of the lottery. method.

12. A program for distributing content, comprising: receiving an input of an object by a viewing user who views the content; executing a lottery in response to an input of the object; and granting a reward to the distributor user who distributes the content based on the result of the lottery. program.

13. An apparatus for distributing content, comprising: means for receiving an input of an object by a viewing user who views the content; means for executing a lottery in response to an input of the object; and a means for awarding a reward to the distributor user who distributes the content based on the result of the lottery. Device.

Images