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

Abstract

To provide a system, a method, a program and a device for providing a content distribution service for promoting continuous distribution of content.SOLUTION: A content delivery server 10, which is a device for providing a content delivery service, is communicably connected to a user terminal 30 via a communication network 20, and provides a content delivery service for delivering and viewing content to a user via the user terminal 30. The service providing control unit 112 of the server 10 sets the value of the second parameter on the basis of the value of the first parameter set on the basis of the distribution result of the content, and after setting the value of the second parameter, gives a reward based on the value of the second parameter to the distributing user according to the satisfaction of the reward giving condition. The server prompts the distribution user to continue to use the content distribution service from when the reward is given until the reward giving condition is satisfied and the reward is acquired.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for providing a content distribution service. [Background technology]

[0002] Conventionally, various services have been provided for distributing content consisting of images and / or audio. In these services, a reward may be given to a broadcaster who distributes content. For example, Patent Document 1 below discloses that a quantity of reward (e.g., virtual and electronic items, or real currency, etc.) is given to a broadcaster based on the broadcast time of a live video and a standard reward quantity. Such a mechanism for providing rewards can encourage broadcasters to distribute content. [Prior art documents] [Patent documents]

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

[0004] However, with the conventional system described above, it cannot be said that a distributor user who has earned a reward based on distribution time, etc., is sufficiently motivated to continue distributing content thereafter.

[0005] One object of the embodiments of the present invention is to facilitate continuous delivery of content. Other objects of the embodiments of the present invention will become apparent by reading the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system for providing a content distribution service, comprising one or more computer processors, wherein the one or more computer processors execute the steps of: setting a value of a first parameter associated with a distribution user based on the distribution user's content distribution performance; setting a value of a second parameter associated with the distribution user based on one or more values ​​of the first parameters set in a first period; and, after setting the value of the second parameter, granting a reward to the distribution user based on the value of the second parameter in accordance with satisfaction of a first condition.

[0007] A method according to one embodiment of the present invention is executed by one or more computers and is a method for providing a content distribution service, comprising the steps of: setting a value of a first parameter associated with a distributor user based on the distributor user's content distribution performance; setting a value of a second parameter associated with the distributor user based on one or more values ​​of the first parameters set in a first period; and, after setting the value of the second parameter, granting a reward to the distributor user based on the value of the second parameter in response to satisfaction of a first condition.

[0008] A program according to one embodiment of the present invention is a program for providing a content distribution service, which causes one or more computers to execute the steps of: setting a value of a first parameter associated with a distribution user based on the distribution user's content distribution performance; setting a value of a second parameter associated with the distribution user based on one or more values ​​of the first parameters set in a first period; and, after setting the value of the second parameter, granting a reward to the distribution user based on the value of the second parameter in accordance with satisfaction of a first condition.

[0009] An apparatus according to one embodiment of the present invention is an apparatus for providing a content distribution service, comprising: means for setting a value of a first parameter associated with a distribution user based on the distribution record of the content by the distribution user; means for setting a value of a second parameter associated with the distribution user based on one or more values ​​of the first parameters set in a first period; and means for granting a reward based on the value of the second parameter to the distribution user after setting the value of the second parameter in accordance with satisfaction of a first condition. [Effects of the Invention]

[0010] Various embodiments of the present invention facilitate the continuous delivery of 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 an example of information managed by a daily delivery performance management table 1514. [Figure 8] FIG. 15 is a diagram illustrating an example of information managed by a savings schedule management table 1515. [Figure 9] FIG. 2 is a diagram illustrating a top screen 50. [Figure 10] FIG. 10 is a diagram illustrating an example of display content in an individual display area 541. [Figure 11] FIG. 6 is a diagram illustrating a distribution preparation screen 60. [Figure 12]FIG. 7 is a diagram illustrating a distribution screen 70. [Figure 13] FIG. 10 is a diagram illustrating an example of a viewing screen 80. [Figure 14] FIG. 10 is a diagram illustrating an example of a viewing screen 80 on which a gift selection screen 90 is superimposed. [Figure 15] FIG. 10 is a diagram illustrating a gift selection screen 90. [Figure 16] 10 is a flowchart illustrating a process executed by the server 10 when updating the rank of each user. [Figure 17] FIG. 10 is a diagram illustrating an example of an update rule for a rank meter value. [Figure 18] 10 is a flowchart illustrating a process executed by the server 10 when granting daily diamonds to each user. [Figure 19] 10 is a flowchart illustrating a process executed by the server 10 when setting a savings schedule for each user. [Figure 20] FIG. 10 is a diagram illustrating the setting of a savings timetable. [Figure 21] 10 is a flowchart illustrating a process executed by the server 10 when unlocking the reserved diamonds of each user. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0030] The service provision control unit 112 is configured to execute various processes for controlling the provision of a content distribution service. For example, the service provision control unit 112 executes various processes for controlling the distribution of content, and is configured to distribute content provided by a distribution user who distributes content to multiple viewing users. For example, the service provision 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 service provision control unit 112 is configured to set the value of a first parameter associated with a broadcast user based on the broadcast user's content distribution history. The first parameter includes various types of parameters based on the content distribution history (including, for example, the distribution time, the number of broadcasts, the number of viewing users, and the number of input elements (comments, items, etc.) entered by viewing users), and includes, for example, the number of items, points, meter value, etc. granted to the broadcast user based on such distribution history. The first parameter may be indirectly associated with the broadcast user, and may be associated, for example, with the content (broadcast) itself that the broadcast user distributes, or with a community of fans who support the broadcast user.

[0032] Furthermore, the service provision control unit 112 is configured to set the value of a second parameter associated with the broadcast user based on the values ​​of one or more first parameters set during a specific period. For example, the value of the second parameter is set based on the values ​​of multiple first parameters that are repeatedly set during a specific period. For example, the service provision control unit 112 sets a portion (e.g., a predetermined percentage) of the total value of the values ​​of one or more first parameters as the value of the second parameter.

[0033] Furthermore, after setting the value of the second parameter, the service provision control unit 112 is configured to grant a reward based on the value of the second parameter to the broadcast user in accordance with whether the reward granting condition (first condition) is met. For example, the right to earn a reward is granted to the broadcast user in accordance with the setting of the value of the second parameter, and the reward is granted to the broadcast user based on that right. For example, the type of reward and / or the quantity of the reward granted to the broadcast user is determined based on the value of the second parameter. It can also be said that the second parameter is a parameter used to grant a reward to the broadcast user. Note that the same value as the first parameter may be used as the value of the second parameter.

[0034] In this way, the content distribution server 10 in this embodiment sets the value of the second parameter based on the value of the first parameter, which is set based on the content distribution record, and after setting the value of the second parameter, grants a reward based on the value of the second parameter to the distributor user in accordance with satisfaction of the reward granting condition, thereby encouraging the distributor user to continue using the content distribution service until the reward granting condition is satisfied and the distributor user obtains the reward. In other words, the server 10 promotes continuous content distribution.

[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 may be composed of either one of these. Furthermore, the content may be transmitted in real time (live distribution) from a user terminal 30 (hereinafter, sometimes referred to as a distribution terminal 30) of a distribution user who provides the content, or may be provided in advance from the distribution terminal 30 and pre-stored in a storage device such as storage 15. The live distribution of content may involve a certain delay (time lag) depending on the settings of the distribution user or the network conditions. The live distribution of content is performed, for example, 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 (e.g., 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 head movement, changes in facial expression, etc.) recognized via a camera in the distribution terminal 30. 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, the reward granting condition described above may be configured as various conditions. For example, the reward granting condition may be configured to be satisfied based on the broadcaster user's content distribution performance (e.g., broadcast performance after setting the value of the second parameter). This configuration encourages the broadcaster user to continue distributing content until the reward granting condition is satisfied and the broadcaster user receives a reward.

[0040] Furthermore, the reward condition may be satisfied when, after the value of the second parameter is set, the number of times a period unit condition (second condition), the satisfaction of which is determined in a predetermined period unit, is satisfied (i.e., the number of period units for which the condition is satisfied) reaches a threshold. The period unit may include, for example, one hour, one day, one week, one month, or a specific period. The period unit condition is configured to be satisfied, for example, based on the distributor user's content distribution performance over a predetermined period unit. This configuration provides the distributor user with the enjoyment of repeatedly satisfying the period unit condition.

[0041] In this embodiment, the service provision control unit 112 can be configured to set a rating (including, for example, rank and level) for a broadcaster user based on the broadcaster user's content distribution performance, and in this case, the period unit condition described above can be configured as a condition that is met if the broadcaster user's rating for the corresponding period unit is above a threshold. This configuration encourages the broadcaster user to continually obtain a rating above the threshold.

[0042] In this embodiment, rewards may be granted in stages depending on the number of times the above-described period-unit condition is satisfied. That is, the service provision control unit 112 may be configured to grant the distributor user a reward based on a first portion of the value of the second parameter when the number of times the period-unit condition is satisfied reaches a first threshold, and to grant the distributor user a reward based on a second portion of the value of the second parameter (which may be a portion larger than the first portion, for example) when the number of times the period-unit condition is satisfied reaches a second threshold that is larger than the first threshold. This configuration makes it possible to repeatedly encourage the distributor user to continue using the content distribution service in stages.

[0043] Furthermore, the reward based on the value of the second parameter may not be granted after a limited period of time has elapsed since the value of the second parameter was set. For example, the reward granting condition may be configured so that it is not satisfied after the limited period has elapsed, or the value of the second parameter may be configured so that it expires (becomes invalid) after the limited period has elapsed. This configuration may encourage the broadcast user to take action to quickly satisfy the reward granting condition.

[0044] In this embodiment, satisfaction of the reward granting condition may be determined at the end of each of a plurality of predetermined periods. For example, the service provision control unit 112 may be configured to grant the distributor user a reward based on a first portion of the value of the second parameter if the reward granting condition is satisfied at the end of a first period after the value of the second parameter is set, and to grant the distributor user a reward based on a second portion of the value of the second parameter if the reward granting condition is satisfied at the end of a second period after the value of the second parameter is set, the second period being longer than the first period. This configuration makes it possible to repeatedly encourage the distributor user to continue using the content distribution service in stages.

[0045] Furthermore, the service provision control unit 112 can be configured to grant a reward of the same type as the reward granted based on the value of the second parameter to a distributor user based on the distributor user's content distribution performance, in which case at least a portion of the quantity of the reward granted based on the content distribution performance may be set as the value of the first parameter. This configuration makes it possible to grant an additional reward of the same type as the reward granted based on the content distribution performance in response to satisfaction of the reward granting conditions.

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

[0047] 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 (rating) as a distribution user, a "rank meter value" that indicates the value of a rank meter that is a parameter for determining whether the rank has increased or decreased, a "number of owned coins" that indicates the number of owned virtual coins that can be used in the content distribution service, a "number of owned diamonds" that is the number of owned virtual diamonds, and "classification text" that is the classification as a distribution user set by the user themselves.

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

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

[0050] 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).

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

[0052] 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).

[0053] 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."

[0054] 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."

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

[0056] 7 illustrates information managed by daily distribution performance management table 1514 in this example. Daily distribution performance management table 1514 manages information related to content distribution performance on a daily basis (every day), and as shown, manages information such as "distribution time," which is the total time spent distributing content on that day, "rank," which is the rank of the distributor user on that day, "excitement level value," which is a parameter indicating the degree (level) of excitement for the distribution of content on that day, and "number of excitement diamonds acquired" (first parameter), which is the number of excitement diamonds acquired on that day, in association with a combination of a "user account" that identifies the user and a "year, month, and day." Excitement diamonds, which will be described in more detail below, are diamonds that are awarded to distributor users according to the level of excitement for their distribution.

[0057] 8 illustrates information managed by the savings diagram management table 1515 in this example. The savings diagram management table 1515 manages information related to savings diagrams held by users, and as shown in the figure, manages information such as the "number of savings diagrams set" (second parameter), which is the number of savings diagrams set, in association with a combination of a "user account" that identifies the user and a "savings diagram setting date," which is the date on which the savings diagram was set, the "cumulative number of days with S4 rank or higher," which is the cumulative total of days on which the user's rank was S4 or higher (i.e., any of S4 to S6) from the day after the savings diagram setting date, and an "invalidation flag," which indicates that the set savings diagram has been invalidated. Saving diagrams, which will be described in detail later, are set at regular intervals based on the total number of excitement diagrams acquired during that period, and are then actually granted to the corresponding user depending on whether the reward granting conditions are met.

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

[0059] 9 shows an example of a top screen 50 of the content distribution service output on the user terminal 30. The screen 50 is the starting point when using the content distribution service, and as shown in the figure, has a selection area 52 displaying the text "Follow," "Popular," "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.

[0060] 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 that 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, likes, and consumed coins). Furthermore, when "All" is selected in the selection area 52, all broadcasts are subject to list display in the list display area 54.

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

[0062] 10 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. 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. 10, 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. 10, it is displayed as "#curry").

[0063] Returning to the top screen 50 of FIG. 9, 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. 11, 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 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).

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

[0065] 12 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.

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

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

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

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

[0070] 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).

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

[0072] 13 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.

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

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

[0075] 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).

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

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

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

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

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

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

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

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

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

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

[0086] In this example, the number of support points in the distribution management table 1512 is updated in real time while the content is being distributed. In this example, the number of support points is calculated based on the number of likes, the number of comments, and the number of coins consumed, and the larger these values, the larger the number of support points. When the broadcasting user selects the stop distribution button 76 on the distribution screen 70, the content distribution ends. Furthermore, in response to the end of the distribution, the distribution time of the corresponding broadcasting user for that day and the excitement level value are updated in the daily distribution performance management table 1514. The greater the number of likes, the number of comments, and the number of coins consumed, the larger the value added to the excitement level value.

[0087] 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. 16 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.

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

[0089] After calculating the number of support points for each broadcast user on the previous day in this manner, the server 10 then updates the rank meter value for each user (step S110). FIG. 17 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."

[0090] 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. 17.

[0091] Returning to the flowchart of FIG. 16, 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's rank is increased / decreased. Specifically, the rank in the user information table 1511 is updated. The rank meter value of the user whose rank has been updated (the user whose rank has been increased or decreased) is cleared to 0. Note that in another example of this embodiment, in order to prevent a sudden increase / decrease in rank in a short period of time, for example, in the case of an increase / decrease in rank across rank ranges, the absolute value of the required rank meter value may be made larger (for example, +6 or -6) compared to an increase / decrease in rank within the same rank range.

[0092] Next, the server 10 sets a rank for each day (step S130). Specifically, in the daily delivery performance management table 1514, the latest rank for each user for that day is set.

[0093] The above describes the processing when determining the rank of a broadcast user. Next, the processing when granting daily diamonds to a broadcast user that are granted every day will be described. FIG. 18 is a flowchart illustrating the processing executed by the server 10 when granting daily diamonds to each user. These processing steps are executed late at night every day, and are executed, for example, at a time (for example, midnight) before the processing executed when updating each user's rank as illustrated in FIG. 16.

[0094] As shown in the figure, the server 10 first grants an hourly dial to each user (step S200). Specifically, each user is granted an hourly dial with a number of diamonds calculated by multiplying the delivery time of each user on the previous day (managed in the daily delivery performance management table 1514) by a standard number of diamonds. The standard number of diamonds is preset for each rank so that the higher the rank, the greater the number of diamonds, and the standard number of diamonds corresponding to each user's rank on the previous day is applied. When an hourly dial is 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.

[0095] Next, the server 10 grants excitement diamonds to each user (step S210). Specifically, a number of diamonds based on each user's excitement level value for the previous day (managed in the daily distribution performance management table 1514) are granted to each user as excitement diamonds. In this example, the total number of excitement diamonds granted to each user each day across the entire content distribution service is set in advance, and these excitement diamonds are distributed based on each user's excitement level value (the larger the excitement level value, the more excitement diamonds are granted). When excitement diamonds are granted to a user, the number of diamonds owned by the corresponding user is updated in the user information table 1511, and the number of excitement diamonds acquired by the corresponding distribution user for that day is updated in the daily distribution performance management table 1514.

[0096] The above describes the processing when granting a daily diamond to a distribution user. Next, the processing related to the savings diamond in this example will be described. Figure 19 is a flowchart illustrating the processing executed by the server 10 when setting a savings diamond for each user. These processes are executed at a predetermined time (for example, 1:00 AM on Monday) every week (on a predetermined day of the week).

[0097] First, as shown in the figure, the server 10 calculates the total number of excitement diamonds acquired in the previous week (step S300). Specifically, the number of excitement diamonds acquired in the seven days of the previous week (for example, from Monday to Sunday) is added up. The number of excitement diamonds acquired each day is managed in the daily distribution performance management table 1514.

[0098] Next, the server 10 sets a savings diagram based on the total number of excitement diamonds acquired in the previous week (step S310). Specifically, 10% of the total number of excitement diamonds acquired in the previous week is set as the savings diagram. When the savings diagram is set, a new record is generated in the savings diagram management table 1515, and the number of savings diagrams set is registered.

[0099] For example, as illustrated in Figure 20, if the number of excitement diamonds acquired each day of the previous week (Monday, February 5th to Sunday, February 11th) was "5000," "10000," "0," "7000," "10000," "5000," and "3000," then 10% of the total value of "40000," or "4000," will be set as the accumulated diamonds for the current day (Monday, February 12th).

[0100] In this example, the unlocking of the reserve diamonds held (actual granting to the user) is determined every day. Figure 21 is a flowchart illustrating the processing executed by the server 10 when unlocking the reserve diamonds of each user. These processing are executed at a predetermined time every day (for example, 1:00 AM).

[0101] First, as shown in the figure, the server 10 invalidates a savings schedule for which one year (365 days) has passed since the setting date (step S400). Specifically, in the savings schedule management table 1515, the invalidation flag of a savings schedule (identified by the combination of the user account and the savings schedule setting date) for which 365 days have passed since the setting date is updated.

[0102] Next, the server 10 updates the cumulative number of days for which the savings schedule is ranked S4 or higher (step S410). Specifically, in the savings schedule management table 1515, among the savings schedules set for users whose rank on the previous day was S4 or higher, the cumulative number of days for which the savings schedule is ranked S4 or higher that has not been invalidated is updated (incremented by 1).

[0103] Next, the server 10 grants (unlocks) a portion of the reserve diamonds to the user based on the updated cumulative number of days of S4 rank or higher (step S420). Specifically, in this example, when the cumulative number of days of S4 rank or higher reaches 90 days, 30% of the corresponding reserve diamonds are unlocked, and when the cumulative number of days of S4 rank or higher reaches 180 days, the remaining 70% of the corresponding reserve diamonds are unlocked. For example, if the set number of reserve diamonds is 4000, when the cumulative number of days of S4 rank or higher reaches 90 days, 1200 reserve diamonds are unlocked, and then when the cumulative number of days of S4 rank or higher reaches 180 days, the remaining 2800 reserve diamonds are unlocked. When the reserve diamonds are unlocked, the number of diamonds owned by the corresponding user is updated in the user information table 1511. Note that after the reserve diamonds are unlocked, diamonds may actually be granted in accordance with the distribution of content that satisfies a predetermined condition (for example, the rank of the distribution user is S4 or higher).

[0104] In the above example, information about the reserve diamonds may be notified to each user at a predetermined timing (for example, every week). The information includes, for example, the unlock status of the reserve diamonds (the last unlock date of the reserve diamonds and the number of unlocks, the total number of diamonds unlocked so far, and the schedule for future unlocks, etc.), the setting status of the reserve diamonds (the last setting date of the reserve diamonds and the number of settings), and the total number of (uninvalidated) reserve diamonds, etc.

[0105] In the above example, 10% of the total number of excitement diamonds acquired in the previous week is set as the accumulated diamonds, but the accumulated diamonds may also be set based on the total number of excitement diamonds acquired in the previous week on days with a rank of a threshold (e.g., S4) or higher (i.e., excluding the number of excitement diamonds acquired on days with a rank of less than the threshold).

[0106] In the above example, the savings diamond is invalidated if one year has passed since the set date, but various other conditions can be applied as conditions for invalidating the savings diamond. For example, the savings diamond may be invalidated if the cumulative number of days since the set date on which a specified condition (for example, the distribution user's rank is S4 or higher) is not met reaches a threshold value.

[0107] In the above example, when the cumulative number of days at S4 rank or higher reaches a threshold (90 days and 180 days), the corresponding reserve diamond is unlocked, but the conditions for unlocking the reserve diamond (reward granting conditions) are not limited to this. For example, the corresponding reserve diamond may be unlocked when the content distribution time or number of distributions after a set date reaches a threshold. Also, for example, the corresponding reserve diamond may be unlocked when the number of days elapsed since a set date reaches a threshold. In another example of this embodiment, the reward granting conditions may be configured by a single condition based on the values ​​of various parameters such as distribution time, number of distributions, rank, and support points, or a combination of multiple conditions.

[0108] In the above example, 10% of the total number of excitement diamonds acquired in the previous week is set as the reserve diamond, but the reserve diamond may be set based on the value of another parameter, for example, at least a portion of the total number of time diamonds acquired in the previous week may be set as the reserve diamond. Furthermore, the reserve diamond may be set based on the number of support points acquired in a specific period. Furthermore, the object of accumulation does not have to be diamonds; for example, reserve points may be set based on the total number of support points acquired in a specific period or the user's rank, and when the reserve points are unlocked, specific points may be awarded to the user.

[0109] In the example described above, 10% of the total number of excitement diamonds acquired in the previous week is set as the reserve diamond, but the number of reserve diamonds set may vary based on the values ​​of various parameters. For example, the greater the number of viewing users whose fan level for the corresponding broadcast user in the current month is above a threshold, or the greater the number of new viewing users in the previous week, the greater the number of reserve diamonds set for that broadcast user.

[0110] In the above example, when the cumulative number of days of S4 rank or higher reaches a threshold, the corresponding reserve diamond is unlocked, but the condition of being S4 or higher is an example of a period unit condition whose fulfillment is determined on a daily basis, and in other examples of this embodiment, various other conditions are applied. For example, when the cumulative number of days in which the delivery time is equal to or greater than a threshold reaches a threshold, the corresponding reserve diamond may be unlocked, or when the cumulative number of weeks in which the delivery count is equal to or greater than a threshold reaches a threshold, the corresponding reserve diamond may be unlocked.

[0111] In addition, at the end of a predetermined period after the setting of the reserve diamond, if the reward granting conditions are met, the reserve diamond may be unlocked. For example, when 90 days have passed since the reserve diamond was set, if the cumulative number of days of S4 rank or higher is 81 days (90%) or more, 30% of the reserve diamond may be unlocked, and when 180 days have passed since the reserve diamond was set, if the cumulative number of days of S4 rank or higher is 162 days (90%) or more, the remaining 70% of the reserve diamond may be unlocked.

[0112] The content distribution server 10 of the present embodiment described above sets the value of a second parameter (e.g., the set number of reserve diamonds, etc.) based on the value of a first parameter (e.g., the number of excitement diamonds acquired in the previous week, etc.) which is set based on the content distribution record, and after setting the value of the second parameter, grants a reward (e.g., diamonds, etc.) to the distributor user based on the value of the second parameter in response to satisfaction of the reward granting condition (e.g., when the cumulative number of days of S4 rank or higher reaches a threshold), thereby encouraging the distributor user to continue using the content distribution service until the reward granting condition is satisfied and the reward is acquired. In other words, the server 10 promotes continuous distribution of content.

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

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

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

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

Claims

1. 1. A system for providing a content distribution service, comprising one or more computer processors, the one or more computer processors comprising: setting a value of a first parameter associated with the distributor user based on the distributor user's content distribution performance; setting a value of a second parameter associated with the broadcast user based on the value of one or more of the first parameters set during a first period; After setting the value of the second parameter, if the first condition is satisfied, a reward based on the value of the second parameter is granted to the broadcast user. system.

2. the step of setting the value of the second parameter includes setting a part of a total value of the one or more first parameters as the value of the second parameter; The system of claim 1.

3. the first condition is satisfied based on the distribution performance of the content by the distribution user; The system of claim 1.

4. the first condition is satisfied when the number of times a second condition, the satisfaction of which is determined in a predetermined time unit after the value of the second parameter is set, is satisfied reaches a threshold value; The system of claim 1.

5. The one or more computer processors further execute a step of setting an evaluation of the distributor user based on the distributor user's performance in distributing the content; the second condition is satisfied when the rating of the broadcast user during the predetermined period is equal to or greater than a threshold; The system of claim 4.

6. the step of granting the reward includes granting the reward to the broadcast user based on a first portion of the value of the second parameter in response to the number of times the second condition is satisfied reaching a first threshold, and granting the reward to the broadcast user based on a second portion of the value of the second parameter in response to the number of times the second condition is satisfied reaching a second threshold that is greater than the first threshold; The system of claim 4.

7. The second portion is larger than the first portion. The system of claim 6.

8. the step of granting the reward does not grant the reward based on the value of the second parameter after a second period has elapsed since the value of the second parameter was set; The system of claim 1.

9. the step of granting the reward includes granting the reward to the broadcast user in an amount based on the value of the second parameter; The system of claim 1.

10. the step of granting the reward includes granting the reward to the broadcast user based on a first portion of the value of the second parameter if the first condition is satisfied at the end of a third period after the value of the second parameter is set, and granting the reward to the broadcast user based on a second portion of the value of the second parameter if the first condition is satisfied at the end of a fourth period after the value of the second parameter is set, the fourth period being longer than the third period; The system of claim 1.

11. the step of setting the value of the first parameter includes setting, as the value of the first parameter, at least a portion of the quantity of the reward to be granted to the distributor user based on the distributor user's performance in distributing the content; The system of claim 1.

12. 1. A method, executed by one or more computers, for providing a content distribution service, comprising: setting a value of a first parameter associated with the distributor user based on the distributor user's content distribution performance; setting a value of a second parameter associated with the broadcast user based on the value of one or more of the first parameters set during a first period; and after setting the value of the second parameter, granting a reward based on the value of the second parameter to the broadcast user in response to satisfaction of a first condition. method.

13. A program for providing a content distribution service, the program being installed on one or more computers, setting a value of a first parameter associated with the distributor user based on the distributor user's content distribution performance; setting a value of a second parameter associated with the broadcast user based on the value of one or more of the first parameters set during a first period; and after setting the value of the second parameter, granting a reward based on the value of the second parameter to the broadcast user in response to satisfaction of the first condition. program.

14. An apparatus for providing a content distribution service, comprising: means for setting a value of a first parameter associated with a distributor user based on the distributor user's content distribution performance; means for setting a value of a second parameter associated with the broadcast user based on the value of one or more of the first parameters set during a first period; and a means for granting a reward based on the value of the second parameter to the broadcast user in response to satisfaction of a first condition after setting the value of the second parameter. Device.

Images