System, method, program and device for providing content distribution service

Abstract

To suppress the content distribution from becoming monotony.SOLUTION: A content distribution server 10 according to an embodiment of the present invention is communicably connected to a user terminal 30 via a communication network 20, and provides, to a user via the user terminal 30, a content distribution service for distributing and viewing content. This server 10 gives a first reward to a distributor user based on the activity record of the distributor user and the evaluation thereof in the content distribution service, and updates the evaluation for the distributor user based on the number of owing first rewards. This enables the distributor user to enjoy the obtainment of the first reward and the update of the evaluation based on the activities in the content distribution service.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 composed of images and / or audio, etc. In such services, content distribution users may participate in an event and receive rewards based on their ranking in the event (for example, rankings in points earned in response to gifting, etc., performed by content viewing users during the event period) (see, for example, Patent Document 1 below). Such a mechanism can prevent content distribution from becoming monotonous. [Prior art documents] [Patent documents]

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

[0004] However, even if a broadcast user participates in the above-mentioned event, if they end up ranked low, they may not be able to fully enjoy the event, and may be hesitant to participate in the event again.

[0005] One of the objects of the embodiments of the present invention is to prevent content distribution from becoming monotonous. 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 granting a first reward to a distribution user who distributes content based on the distribution user's behavioral track record in the content distribution service and an evaluation of the distribution user, and updating the evaluation of the distribution user based on the number of first rewards held.

[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: granting a first reward to a distributor user who distributes content based on the distributor user's behavioral performance in the content distribution service and an evaluation of the distributor user; and updating the evaluation of the distributor user based on the number of first rewards held.

[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 granting a first reward to a distribution user who distributes content based on the distribution user's behavioral record in the content distribution service and an evaluation of the distribution user, and updating the evaluation of the distribution user based on the number of first rewards held.

[0009] An apparatus according to one embodiment of the present invention is an apparatus for providing a content distribution service, and includes: means for granting a first reward to a distribution user who distributes content based on the distribution user's behavioral record in the content distribution service and an evaluation of the distribution user; and means for updating the evaluation of the distribution user based on the number of first rewards held. [Effects of the Invention]

[0010] Various embodiments of the present invention reduce monotony in content delivery. [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 prize 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. 2 is a diagram illustrating a top screen 50. [Figure 11] FIG. 10 is a diagram illustrating an example of display content in an individual display area 541. [Figure 12] FIG. 6 is a diagram illustrating a distribution preparation screen 60. [Figure 13] FIG. 7 is a diagram illustrating a distribution screen 70. [Figure 14] FIG. 10 is a diagram illustrating an example of a viewing screen 80. [Figure 15] FIG. 10 is a diagram illustrating an example of a viewing screen 80 on which a gift selection screen 200 is superimposed. [Figure 16] FIG. 2 is a diagram illustrating a gift selection screen 200. [Figure 17] 10 is a flowchart illustrating a process executed by the server 10 when updating the rank of each user. [Figure 18] FIG. 10 is a diagram illustrating an example of an update rule for a rank meter value. [Figure 19] 10 is a flowchart illustrating a process executed by the server 10 when granting diamonds to each user. [Figure 20] FIG. 3 is a diagram illustrating an example of an event participation registration screen 310. [Figure 21] 10 is a flowchart illustrating a process executed by the server 10 after the period in which a specific event is held ends. [Figure 22] FIG. [Figure 23] 10 is a flowchart illustrating the processing executed by server 10 when updating the grade of a broadcast user. [Figure 24] FIG. 2 is a diagram illustrating an example of promotion and demotion lines set for each grade. [Figure 25] FIG. 3 is a diagram illustrating a family information screen 320. [Figure 26] FIG. 10 is a diagram illustrating a prize exchange screen 330. 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 distribution control unit 112 is configured to execute various processes for controlling the distribution of content. For example, the distribution control unit 112 is configured to distribute content provided by a distribution user to multiple viewing users. For example, the distribution 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 of the user terminals 30 (hereinafter sometimes referred to as viewing terminals 30) of the multiple viewing users.

[0031] In this embodiment, the distribution control unit 112 is configured to grant a first reward to a distributor user who distributes content, based on the distributor user's behavioral track record in the content distribution service and the distributor user's evaluation. The distribution user's holdings of first rewards are managed, for example, in various tables 151. For example, a first reward is granted when conditions related to the behavioral track record and / or evaluation are met. Furthermore, for example, the quantity and / or type of first reward granted is determined based on the behavioral track record and / or evaluation.

[0032] In this embodiment, the first reward includes various types of rewards, such as items (including points, coins, characters, cards, in-service currency, etc.), parameter values ​​(such as experience points, etc.), etc.

[0033] The distribution control unit 112 is also configured to update the broadcast user's rating based on the number of first rewards held. For example, the more first rewards held, the higher the broadcast user's rating. The broadcast user's rating is managed, for example, in various tables 151. The number of first rewards held by the broadcast user may be cleared, for example, in response to an update to the broadcast user's rating.

[0034] In this way, the content distribution server 10 in this embodiment grants a first reward to a distributor user based on the distributor user's behavioral record and evaluation in the content distribution service, and updates the distributor user's evaluation based on the number of first rewards held, allowing the distributor user to enjoy earning a first reward based on their behavior in the content distribution service and updating their evaluation. In other words, the server 10 prevents content distribution from becoming monotonous.

[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 the user terminal 30 (hereinafter, sometimes referred to as the distribution terminal 30) of the 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).

[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, motion data (motion data) for moving objects such as characters is transmitted in real time from the distribution terminal 30, while images constituting the content are pre-stored in the server 10 or the viewing terminal 30, and the images include model data of the objects. In this case, the motion data is generated based on, for example, the motion of the distribution user recognized via the camera of the distribution terminal 30 (including changes in facial expressions, etc.). The content generated in the server 10 or the viewing terminal 30 includes objects such as characters that move based on the model data and motion data.

[0039] In this embodiment, the behavioral achievements used for granting the first reward include various behavioral achievements in the content distribution service, such as logging in, distributing content, and gifting.

[0040] Additionally, behavioral records may include a record of participation in events held in the content distribution service (including whether or not the broadcast user participated). Such events include, for example, events in which a ranking is set among participating broadcast users and a reward is awarded to each broadcast user according to that ranking. This configuration encourages broadcast users to participate in events.

[0041] In this case, the distribution control unit 112 may be configured to grant a first reward to a broadcast user based on the value of a parameter associated with the event, in addition to the behavioral record and evaluation. The parameters include, for example, the type of event, the length of the event, and the number of participating users. For example, the first reward is granted when a condition related to the parameter is met. Also, for example, the quantity and / or type of the first reward to be granted is determined based on the value of the parameter. This configuration enables the granting of a first reward based on the value of a parameter related to the event.

[0042] Alternatively, the first reward may be granted each time a recurring event is held. That is, the distribution control unit 112 may be configured to grant a first reward to a broadcast user in response to the broadcast user's participation in a first event, and then grant a first reward to the broadcast user in response to the broadcast user's participation in a second event. In this case, for example, the broadcast user's evaluation may be updated based on the number of first rewards held, which is the sum of the first reward earned in response to participation in the first event and the first reward earned in response to participation in the second event. This configuration encourages the broadcast user to participate in multiple events.

[0043] Furthermore, the distribution control unit 112 may be configured to grant a second reward to the broadcast user based on the broadcast user's behavioral record. In this case, the distribution control unit 112 may be configured to grant a third reward to the broadcast user, accompanied by consumption of the second reward. This configuration makes it possible to grant a second reward that can be exchanged for a third reward, based on the broadcast user's behavioral record in the content distribution service.

[0044] In this embodiment, the second reward includes various types of rewards, such as items (including points, coins, characters, cards, in-service currency, etc.), parameter values, etc.

[0045] In this embodiment, the third reward includes various types of rewards, such as items (including points, coins, characters, cards, in-service currencies, etc.), parameter values, etc. The third reward may also be the right to acquire real goods.

[0046] The distribution control unit 112 may also be configured to grant a third reward to a broadcast user based on the broadcast user's rating. For example, the quantity and / or type of third reward to be granted may be determined based on the broadcast user's rating. Furthermore, for example, the distribution control unit 112 may be configured to grant a third reward to a broadcast user selected by the broadcast user from one or more third rewards determined based on the broadcast user's rating out of multiple third rewards. In other words, the type of third reward that can be exchanged for a second reward may be determined based on the broadcast user's rating. This configuration allows the broadcast user to enjoy updating their rating even more.

[0047] Additionally, the distribution control unit 112 may be configured to, in response to the granting of the third reward to the broadcasting user, send a predetermined notification to related users associated with the broadcasting user (for example, by sending data of the notification to the related users' user terminal 30). Information regarding related users associated with the broadcasting user is managed, for example, in various tables 151. The predetermined notification typically notifies the broadcasting user that the third reward has been granted. This configuration may encourage communication between the broadcasting user and related users triggered by the granting of the third reward.

[0048] The distribution control unit 112 may also be configured to grant the second reward to a broadcast user based on the broadcast user's ranking in the event. In this case, the distribution control unit 112 may be configured to grant the second reward to the broadcast user so that the lower the ranking, the more advantageous the broadcast user. For example, if the ranking is lower than a predetermined ranking, the distribution control unit 112 may be configured to grant the broadcast user a second reward that is more advantageous (e.g., higher value or larger quantity) than one or more other broadcast users who are at or above the predetermined ranking. In this case, other rewards may be granted to each of the one or more other broadcast users who are at or above the predetermined ranking. This configuration encourages broadcast users who are at a lower ranking in the event to participate in the event again.

[0049] In this embodiment, the broadcast user's ranking in an event can be set based on the number of items (including points, parameter values, etc.) acquired by the broadcast user in response to content distribution during the event period. In this case, if the broadcast user's ranking is lower than a predetermined ranking, the broadcast control unit 112 can be configured to grant a second reward to the broadcast user based on a comparison of the number of items acquired by the broadcast user with the number of items acquired by at least some of the other broadcast users who are at or above the predetermined ranking. For example, the closer the number of items acquired by the broadcast user is to the number of items acquired by other users with a predetermined ranking, the more advantageous the quantity and / or type of second reward granted to the broadcast user may be. This configuration allows broadcast users who are ranked low in the event to enjoy acquiring the items.

[0050] The distribution control unit 112 may also be configured to present a predetermined screen displaying group information related to a group associated with the broadcast user to each of multiple users belonging to that group (for example, by sending screen data and control data for that screen to the corresponding user terminal 30). In this case, the group information may include the broadcast user's rating and / or the number of first rewards held by that broadcast user. This configuration may encourage communication between users belonging to groups related to that broadcast user, triggered by updates to the broadcast user's rating and acquisition of a first reward, etc.

[0051] In this embodiment, the distribution control unit 112 may be configured to grant a fourth reward to a viewing user who views content, based on the viewing user's behavioral record in the content distribution service and the viewing user's rating. The status of the viewing user's possession of the fourth reward is managed, for example, in various tables 151. For example, the fourth reward is granted when conditions related to the behavioral record and / or rating are satisfied. Furthermore, for example, the quantity and / or type of the fourth reward to be granted is determined based on the behavioral record and / or rating. The viewing user's behavioral record may include input records of comments, items, etc. on content.

[0052] In this embodiment, the fourth reward includes various types of rewards, such as items (including points, coins, characters, cards, and in-service currency, etc.), parameter values ​​(such as experience points, etc.), etc.

[0053] Furthermore, the delivery control unit 112 can be configured to update the rating of the viewing user based on the number of fourth rewards held. The rating of the viewing user is managed, for example, in various tables 151. The number of fourth rewards held by the viewing user can be cleared, for example, in response to an update of the rating of the viewing user.

[0054] This configuration allows the viewing user to enjoy earning a fourth reward and updating their rating based on their actions in the content distribution service.

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

[0056] FIG. 2 illustrates information managed by the user information table 1511 in this example. User information table 1511 manages information about users of the content distribution service, and as shown in the figure, associates information with a "user account" that identifies an individual user, such as "basic information" including account name and date of birth, "distribution history information" which is information about the distribution history as a distribution user, "viewing history information" which is information about the viewing history as a viewing user, "following user information" which is information about other users that the user is following, "family information" which is information about families that the user is a family member of, a "rank" which indicates the rank as a distribution user, a "rank meter value" which is the value of a rank meter which is a parameter for determining whether the rank has increased or decreased, "number of coins held" which indicates the number of virtual coins that can be used in the content distribution service, "number of diamonds held" which indicates the number of virtual diamonds held, "classification text" which is the classification as a distribution user set by the user themselves, "number of event miles held" which indicates the number of event miles (first reward) held that the user has acquired as a distribution user, "number of event tickets held" which indicates the number of event tickets (second reward) held that the user has acquired as a distribution user, and "grade" which indicates a grade (rating) that is updated according to the number of event miles held.

[0057] In this example, a family is a community of fans who support a broadcast user, and a user can join in response to an invitation from the broadcast user or a family manager, or in response to approval by the broadcast user or family manager of a user's application to join. 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.

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

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

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

[0061] In this example, event miles and event tickets, which will be described in more detail below, are items that can be acquired through participation in a specific event as a broadcast user.

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

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

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

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

[0066] 7 illustrates information managed by the prize information table 1514 in this example. The prize information table 1514 manages information related to prizes (third rewards) that can be exchanged for event tickets, and as shown, manages information such as a "name," a "minimum grade" indicating the minimum grade of the broadcast user that can exchange for this prize, and a "number of tickets required" that is the number of event tickets required to exchange for this prize, in association with a "prize ID" that identifies the individual prize.

[0067] 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 said period, "participation condition information" which is information related to the conditions for participating in the event, and "reward condition information" which is information related to rewards that can be obtained in the event, in association with an "event ID" which identifies each individual event. The participation condition information includes the rank of broadcast users who are eligible to participate in the event.

[0068] 9 illustrates information managed by the event-specific broadcast user management table 1516. The event-specific broadcast user management table 1516 manages information about broadcast users for each event, and as shown, manages information such as the "event points" which is the total number of event points acquired by the broadcast user during the event period, and the "rank" 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.

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

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

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

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

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

[0074] Returning to the top screen 50 of FIG. 10, 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. 12, 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).

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

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

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

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

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

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

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

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

[0083] 14 illustrates a viewing screen 80 output on the viewing terminal 30. For example, when a viewing user selects a desired 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] Here, the processing when a broadcasting user ends the broadcast of content will be explained. As described above, when the broadcasting user selects the broadcast stop button 76 on the broadcast screen 70, the broadcast of the content ends. When the broadcast ends, the server 10 calculates and sets the number of support points for that broadcast. In this example, the number of support points is calculated based on the number of viewing users (maximum value), the number of likes, the number of comments, and the number of consumed coins. The number of support points increases as the number of viewing users (maximum value), the number of likes, the number of comments, and the number of consumed coins increase. The calculated number of support points is registered for the corresponding broadcast in the broadcast management table 1512.

[0098] The above describes the processing when content distribution ends. Next, the processing when determining the rank of a broadcast user 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. Figure 17 is a flowchart illustrating the processing executed by server 10 when updating each user's rank. These processing steps are executed late at night (e.g., 3:00 AM) every day.

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

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

[0101] 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. 18.

[0102] Returning to the flowchart of FIG. 17, 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.

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

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

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

[0106] The above describes the process for awarding diamonds to a broadcast user. Next, we will explain an event held in the content distribution service of this example. FIG. 20 shows an example of an event participation registration screen 310 output on user terminal 30. This screen 310 is a screen for a broadcast user to register for participation in an individual event, and as shown, displays an overview of the event (including the event period and participation conditions) and reward conditions, and has a participant button 312 and a participation registration button 314 with the text "Enter event" added. When participant button 312 is selected, a screen (not shown) is output that displays a list of broadcast users (identified by referencing event-specific broadcast user management table 1516) who are registered to participate in the corresponding event.

[0107] Participation registration button 314 is an object for registering participation in the corresponding event. When this button 314 is selected, the participation of the corresponding broadcast user in the corresponding event is registered, and specifically, a new record is inserted in event-specific broadcast user management table 1516.

[0108] The events in this example include specific events for acquiring event miles and event tickets, which will be described below.

[0109] For a specific event, a ranking among broadcast users is set based on the number of event points earned during the event period. Like the number of support points, the number of event points is calculated and set in response to the end of content distribution. The calculated number of event points is registered for the corresponding combination of event and broadcast user in event-specific broadcast user management table 1516. In this example, the number of event points increases as the number of viewing users (maximum value), number of likes, number of comments, and number of coins consumed increases. The formula used to calculate the number of event points may be the same as the formula used to calculate the number of support points, or it may be a different formula.

[0110] 21 is a flowchart illustrating the processing executed by server 10 after the end of the period in which a specific event is held. As shown in the figure, server 10 first sets a ranking for each broadcast user based on the number of event points (step S300). Specifically, the ranking is set in descending order of the number of event points, and the ranking for each broadcast user is registered in event-specific broadcast user management table 1516.

[0111] Next, server 10 awards event rewards to the winners (step S310). Specifically, in accordance with the reward conditions for a specific event, predetermined event rewards are awarded to a predetermined number of broadcast users (winners) with the highest event point counts (e.g., the five users ranked from first to fifth place). The event rewards are virtual and electronic items (e.g., items that can be used in a content distribution service), and the possession status of these items is managed in user information table 1511 or another table. The items include the right to acquire real-world products, and in this case, the products are delivered separately to users who possess these rights.

[0112] Next, the server 10 awards event miles to the broadcast user (step S320). In this example, event miles are a reward awarded to all broadcast users who participate in a specific event. The number of event miles awarded is calculated using the following formula: Event Miles = Number of days the specific event is held x 1000 x Grade Multiplier In this way, the longer the number of days a specific event is held (calculated based on the start and end dates in event information table 1515), the more event miles will be awarded. Also, the grade multiplier is a multiplier set based on the grade of the broadcast user.

[0113] Figure 22 shows an example of a grade multiplier. As shown in the figure, in this example, there are five grades, from lowest to highest: "Bronze," "Silver," "Gold," "Platinum," and "Diamond." The higher the grade, the greater the grade multiplier, which is more advantageous for the user. When event miles are awarded, the number of event miles owned by the corresponding user is updated in user information table 1511.

[0114] Next, the server 10 grants event tickets to the broadcast user (step S330). In this example, event tickets, like event miles, are rewards granted to all broadcast users who participate in a specific event. The number of event tickets granted is calculated using the following formula: Event Tickets = Number of days the specific event is held x 1000 + Close Loser Bonus In this way, the number of event tickets awarded will increase the longer the specific event is held, just like the number of event miles described above. The close loss bonus is only awarded to broadcast users who do not receive the event reward (specifically, broadcast users who are not among the top certain number of broadcast users in terms of event point ranking), and is calculated using the following formula: Close loss bonus = number of days the specific event is held × 1000 × close loss rate Here, the narrow loss rate is calculated by dividing the number of event points earned by the target broadcaster by the number of event points earned by the broadcaster with the lowest event point ranking among the broadcasters who have earned an event reward. For example, if an event reward is awarded to broadcasters ranked 1st through 5th in terms of event points, the narrow loss rate (e.g., 0.8) is calculated by dividing the number of event points earned by the target broadcaster (e.g., 80,000 points) by the number of event points earned by the fifth-ranked broadcaster (e.g., 100,000 points).

[0115] In this example, the broadcast user's grade is updated at a predetermined timing (e.g., once every three months). FIG. 23 is a flowchart illustrating the processing executed by server 10 when updating the broadcast user's grade. As shown in the figure, server 10 first updates each user's grade based on the number of event miles held at that time (step S400). Specifically, a determination is made as to whether each user's grade will be promoted or demoted in accordance with the promotion line and demotion line set for each grade, and the grade of each user is updated in user information table 1511 in accordance with the result of this determination.

[0116] 24 illustrates the promotion and demotion lines set for each grade. As shown in the figure, for example, the promotion line for a bronze grade is "10,000." A bronze user is promoted (their grade is changed to silver) if they hold 10,000 or more event miles. If they hold fewer than 10,000 event miles, they maintain their current grade (bronze). Similarly, the promotion line for a gold grade is "50,000" and the demotion line is "25,000." A gold user is promoted (their grade is changed to platinum) if they hold 50,000 or more event miles. If they hold 25,000 or fewer event miles, they are degraded (their grade is changed to silver). If they hold 25,001 or more but fewer than 50,000 event miles, they maintain their current grade (gold).

[0117] Next, the server 10 clears the number of event miles owned by each user (step S410). Specifically, the number of event miles owned by each user is cleared in the user information table 1511.

[0118] 25 illustrates a family information screen 320 output on a user terminal 30. This screen 320 displays information about the family, and is output on the user terminals 30 of the users belonging to that family (the target broadcast user and family members) (only those users can view it). As shown, the family information screen 320 has a specific event information display area 322 that displays information about a specific event, and this area 322 displays the target broadcast user's grade, the number of event miles they own, and the number of event tickets they own, and has a prize button 324.

[0119] When the prize button 324 is selected, a prize exchange screen 330, as shown in Fig. 26, is output. This screen 330 is a screen for exchanging event tickets for prizes, and as shown in the figure, has a prize list display area 332 that displays a list of prizes, and an exchange button 334. The prize exchange screen 330 also displays the number of event tickets held by the target broadcast user between the prize list display area 332 and the exchange button 334.

[0120] The prize list display area 332 has four columns of individual display areas 3321 arranged vertically, each corresponding to a different prize. The areas 3321 display an image of the corresponding prize, the number of event tickets required to exchange it, and other information.

[0121] In this example, among the prizes displayed in the prize list display area 332, the individual display areas 3321 corresponding to prizes that the target broadcast user cannot exchange are marked as such and are disabled (cannot be selected). Specifically, prizes that cannot be exchanged are prizes whose minimum grade is higher than the grade of the target broadcast user, and prizes whose number of event tickets required to exchange them is greater than the number of event tickets the broadcast user owns.

[0122] When the exchange button 334 is selected, the prize selected via the prize list display area 332 is exchanged for an event ticket. Specifically, the corresponding prize is granted to the broadcast user, and the number of required tickets is deducted from the number of event tickets owned by the corresponding broadcast user in user information table 1511. In this example, the prize is a virtual or electronic item (e.g., an item usable in a content distribution service), and the ownership status of such item is managed in user information table 1511 or another table. The item includes the right to acquire a real product, and in this case, the product is delivered separately to the user who owns the right. Also, in this example, when a prize is granted to the broadcast user, the broadcast user's family members are notified that the prize has been granted to the broadcast user.

[0123] In this example, the exchange button 334 is configured so that it can only be selected by the target broadcast user, and cannot be selected by other users (i.e., family members). Specifically, the exchange button 334 is disabled on the prize exchange screen 330 output on the user terminal 30 of users other than the target broadcast user.

[0124] Thus, in this example, broadcast users who participate in a specific event, even if they are not ranked highly as prize winners, can earn the same number of event miles as prize winners and more event tickets than prize winners, and can exchange those event tickets for prizes. The more event miles they earn, the higher their grade becomes, and the higher their grade becomes, the more prizes they can exchange for. Therefore, even broadcast users who are not prize winners can feel a sense of accomplishment, which encourages them to participate in specific events.

[0125] In the example described above, event miles and event tickets are awarded to broadcast users who participate in a specific event, but it is also possible to award only event miles. In this case, the event miles may be exchangeable for prizes. Furthermore, in this case, the number of held event miles may not be cleared when updating the grade. Furthermore, event miles and event tickets are examples of rewards awarded to broadcast users, and in other examples of this embodiment, various items and the like may be applied as rewards instead.

[0126] In the example described above, event miles and event tickets were awarded to broadcast users who participated in a specific event, but rewards equivalent to event miles and event tickets may also be awarded based on other actions other than participating in the event. For example, miles may be awarded to a broadcast user based on the number of cheering points earned each day, and the broadcast user's grade may be updated and the number of tickets to be awarded to the broadcast user may be determined based on the number of miles earned within a predetermined period (e.g., three months).

[0127] In the above example, the number of event miles and event tickets awarded increases the longer the number of days the specific event is held, but the number of event miles and event tickets awarded may also be determined based on parameters other than the number of days the specific event is held (for example, the number of broadcast users registered to participate).

[0128] In the example described above, prizes with a minimum grade higher than the broadcast user's grade cannot be selected by the broadcast user, but the prizes eligible for exchange for event tickets may be automatically determined based on the broadcast user's grade.

[0129] In the above example, event miles and event tickets may be awarded to a viewing user based on the viewing user's behavioral record. For example, event miles and event tickets may be awarded based on the number of coins consumed in content distributed by distributors participating in a specific event during the event's duration. In this case, the number of event miles and event tickets awarded may be calculated, for example, using the following formula: Event miles = Coins consumed x Grade multiplier Number of event tickets = number of coins consumed In this case, the grade of the viewing user may be updated based on the number of event miles held, similar to the grade of the broadcast user described above.

[0130] The content distribution server 10 of the present embodiment described above grants a first reward (e.g., event miles) to a broadcast user based on the broadcast user's behavioral record in the content distribution service (e.g., participation in a specific event) and rating (e.g., grade), and updates the broadcast user's rating based on the number of first rewards the broadcast user has, allowing the broadcast user to enjoy earning first rewards based on their behavior in the content distribution service and updating their rating. In other words, server 10 prevents content distribution from becoming monotonous.

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

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

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

[0134] 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]

[0135] 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 Prize Information Table 1515 Event Information Table 1516 Event-specific distribution 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 80 viewing screen 200 Gift selection screen 310 Event registration screen 320 Family Information Screen 330 Prize exchange 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: granting a first reward to a distributor user who distributes content based on the distributor user's behavioral record in the content distribution service and an evaluation of the distributor user; and updating the rating of the broadcast user based on the number of first rewards held. system.

2. The behavioral record includes a record of participation in an event held in the content distribution service. The system of claim 1.

3. the step of granting the first reward grants the first reward to the broadcast user further based on a value of a parameter associated with the event; The system of claim 2.

4. The parameter is the duration of the event. The system of claim 3.

5. the step of granting the first reward includes granting the first reward to the broadcast user in response to the broadcast user's participation in a first event, and thereafter granting the first reward to the broadcast user in response to the broadcast user's participation in a second event; The system of claim 2.

6. The one or more computer processors further execute a step of clearing the number of first rewards held by the broadcast user in response to updating the rating of the broadcast user based on the number of first rewards held. The system of claim 1.

7. The one or more computer processors further: a step of granting a second reward to the broadcast user based on the behavioral record of the broadcast user; and granting a third reward to the distributor user by consuming the second reward. The system of claim 1.

8. the step of granting the third reward includes granting the third reward to the broadcaster user based on the evaluation of the broadcaster user; The system of claim 7.

9. the step of granting the third reward includes granting to the broadcaster user the third reward selected by the broadcaster user from one or more third rewards determined based on the evaluation of the broadcaster user; The system of claim 8.

10. The one or more computer processors further execute a step of sending a predetermined notification to related users associated with the broadcast user in response to the granting of the third reward. The system of claim 7.

11. the behavioral record is an event held in the content distribution service, and includes a participation record in the event in which a ranking of each of the plurality of distribution users is set; the step of granting the second reward grants the second reward to the broadcast user based on the ranking of the broadcast user in the event; The system of claim 7.

12. the step of granting the second reward grants the second reward to the broadcaster user in a manner that is more advantageous for the broadcaster user as the ranking decreases; The system of claim 11.

13. and when the ranking is lower than a predetermined ranking, the step of granting the second reward grants the broadcaster user the second reward that is more advantageous than one or more other broadcaster users that are at or above the predetermined ranking. The system of claim 12.

14. the ranking is set based on the number of items acquired by the broadcast user in response to the broadcast of the content during the event period; the step of granting the second reward grants the second reward to the broadcast user if the ranking is lower than the predetermined ranking, based on a comparison of the number of items acquired by at least some of the one or more other broadcast users with the number of items acquired by the broadcast user; The system of claim 13.

15. the one or more computer processors further execute a step of presenting a predetermined screen displaying group information related to the group associated with the broadcast user to each of a plurality of users belonging to the group; The group information includes the rating of the broadcast user and / or the number of first rewards held by the broadcast user, The system of claim 1.

16. 1. A method executed by one or more computers for providing a content distribution service, comprising: granting a first reward to a distributor user who distributes content based on the distributor user's behavioral record in the content distribution service and an evaluation of the distributor user; and updating the rating of the broadcast user based on the number of first rewards held. method.

17. A program for providing a content distribution service, the program being installed on one or more computers, granting a first reward to a distributor user who distributes content based on the distributor user's behavioral record in the content distribution service and an evaluation of the distributor user; updating the rating of the broadcast user based on the number of first rewards held; program.

18. An apparatus for providing a content distribution service, comprising: means for granting a first reward to a distributor user who distributes content based on the distributor user's behavioral record in the content distribution service and an evaluation of the distributor user; and means for updating the rating of the broadcast user based on the number of first rewards held. Device.

Images