Systems, methods, programs, and apparatus for providing content distribution services

Abstract

This enables new effects associated with object input in content delivery services. [Solution] A content distribution server 10 according to one embodiment of the present invention is connected to a user terminal 30 via a communication network 20, and provides a content distribution service for distributing and viewing content to the user via the user terminal 30. The server 10 updates viewing history information of distribution users or viewing users managed in association with content, based on the viewing behavior of the viewing user, and changes the viewing history information based on the input of a specific object by the viewing user, separately from the update based on the viewing behavior, and such changes in viewing history information can be said to be a new effect associated with the input of the object.

Description

Technical Field

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

Background Art

[0002] Conventionally, various services for distributing content composed of images and / or sounds have been provided. In such services, objects such as items may be input (for example, gifting) by viewing users who view the content (see, for example, Patent Document 1 below). For example, when an item is input, various production displays are performed on the content, and various rewards are given to the content distribution user.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, although the conventional mechanism as described above enables supporting the distribution user through the input of an object, it can be said that the effects associated with such input of an object (for example, production display on the content and rewards for the distribution user) are uniform.

[0005] One object of an embodiment of the present invention is to realize a new effect associated with the input of an object in a content distribution service. Other objects of the embodiments of the present invention will become apparent by referring to the entire specification.

Means for Solving the Problems

[0006] A system according to 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 perform the following: updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user with respect to content provided by the distribution user; and changing the viewing history information of the viewing user, separately from the update based on the viewing behavior, based on the input of a specific object by the viewing user.

[0007] A method according to one embodiment of the present invention is a method for providing a content distribution service, which is performed by one or more computers, and comprises the steps of: updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user with respect to content provided by the distribution user; and changing the viewing history information of the viewing user, separately from the update based on the viewing behavior, based on the input of a specific object by the viewing user.

[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 perform the following processes: updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user with respect to content provided by the distribution user; and changing the viewing history information of the viewing user, separately from the update based on the viewing behavior, based on the input of a specific object by the viewing user.

[0009] An apparatus according to one embodiment of the present invention is an apparatus for providing a content distribution service, comprising: means for updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user with respect to content provided by the distribution user; and means for changing the viewing history information of the viewing user, separately from the update based on the viewing behavior, based on the input of a specific object by the viewing user. [Effects of the Invention]

[0010] Various embodiments of the present invention realize new effects associated with object input in content distribution services. [Brief explanation of the drawing]

[0011] [Figure 1] A schematic diagram showing the configuration of a network including a content distribution server 10 according to one embodiment of the present invention. [Figure 2] A diagram illustrating the information managed by user information table 1511. [Figure 3] A diagram illustrating the ranking of streaming users. [Figure 4] A diagram illustrating the information managed by the distribution management table 1512. [Figure 5] This diagram illustrates the information managed by the streaming user-specific viewing user management table 1513. [Figure 6] A diagram illustrating the behavioral conditions for various levels of fan engagement. [Figure 7] A diagram illustrating the information managed by the item management table 1514. [Figure 8] A diagram illustrating the top screen 50. [Figure 9] A diagram illustrating the display content of individual display area 541. [Figure 10] A diagram illustrating the distribution preparation screen 60. [Figure 11] A diagram illustrating the streaming screen 70. [Figure 12] A diagram illustrating viewing screen 80. [Figure 13] FIG. illustrating a viewing screen 80 on which an item selection screen 90 is superimposed and displayed. [Figure 14] FIG. illustrating an item selection screen 90. [Figure 15] FIG. illustrating an item selection screen 90 when "owned item" is selected in a selection area 91. [Figure 16] Flowchart illustrating the process executed by server 10 in response to an item input. [Figure 17] FIG. illustrating production objects 761, 861. [Figure 18] Flowchart illustrating the process executed by server 10 when updating the rank of each user. [Figure 19] FIG. illustrating the update rule of the rank meter value. [Figure 20] Flowchart illustrating the process executed by server 10 when awarding diamonds to each user. [Figure 21] FIG. illustrating a my page screen 200. [Figure 22] FIG. illustrating a mile exchange screen 210.

MODE FOR CARRYING OUT THE INVENTION

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

[0013] Figure 1 is a schematic diagram showing the configuration of a network including a content distribution server 10 according to one embodiment of the present invention. As shown in the figure, the server 10 is connected to a user terminal 30 via a communication network 20 such as the Internet. In Figure 1, only one user terminal 30 is shown, but the server 10 is connected to multiple user terminals 30. The server 10 provides a content distribution service to users via the user terminal 30 for the distribution and viewing of content. 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, the hardware configuration of the content distribution server 10 will be described. The content distribution server 10 is configured as a general-purpose computer and, as shown in Figure 1, includes a computer processor 11, main memory 12, input / output interface 13, communication interface 14, and storage (memory device) 15. These components are electrically connected via buses and the like (not shown).

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

[0016] The input / output interface 13 includes various input / output devices for exchanging information with the operator, etc. The input / output interface 13 includes, for example, information input devices such as keyboards and pointing devices (e.g., mice, touch panels, etc.), audio input devices such as microphones, and image input devices such as cameras. Furthermore, the input / output interface 13 includes image output devices such as displays and audio output devices such as speakers.

[0017] The communication interface 14 is implemented as hardware such as a network adapter, various communication software, and a combination thereof, and is configured to enable wired or wireless communication via the communication network 20, etc.

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

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

[0020] The content distribution server 10 configured in this way can be configured to function as both a web server and an application server. In this case, it performs various processes in response to requests from terminal-side programs 42 installed on the user terminal 30, and sends screen data (e.g., HTML data) and control data, etc., to the user terminal 30 according to the results of those processes. The user terminal 30 may then output a web page or other screen based on the received data.

[0021] Next, the hardware configuration of the user terminal 30 will be described. The user terminal 30 is configured as a general-purpose computer and, as shown in Figure 1, includes a computer processor 31, main memory 32, input / output interface 33, communication interface 34, and storage (memory device) 35. These components are electrically connected via buses and the like (not shown).

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

[0023] The input / output interface 33 includes various input / output devices for exchanging information with the operator, etc. The input / output interface 33 includes, for example, information input devices such as keyboards and pointing devices (e.g., mice, touch panels, etc.), audio input devices such as microphones, and image input devices such as cameras. Furthermore, the input / output interface 33 includes image output devices such as displays and audio output devices such as speakers.

[0024] The communication interface 34 is implemented as hardware such as a network adapter, various communication software, and a combination thereof, and is configured to enable wired or wireless communication via the communication network 20, etc.

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

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

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

[0028] Next, the functions of the content distribution server 10 configured in this way will be described. As shown in Figure 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 contained in a program loaded into the main memory 12 (for example, at least a part of the server-side program 40).

[0029] The management function control unit 111 is configured to perform 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 for various screens related to the management functions to the user terminal 30, performs various processes in response to user input via the screens output on the user terminal 30, and transmits screen data and control data corresponding to the results of those 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 perform various processes for controlling the provision of content distribution services. For example, the service provision control unit 112 performs various processes for controlling the distribution of content. For example, the service provision control unit 112 distributes content provided by a distribution user 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 of the multiple viewing users' user terminals 30 (hereinafter sometimes referred to as viewing terminals 30).

[0031] Here, viewing users include users who view content in the past, present, or future, and typically include all users of the content distribution service. Similarly, distributing users include users who distribute content in the past, present, or future, and typically include all users of the content distribution service. Users of the content distribution service can typically distribute content as distributing users and view content as viewing users.

[0032] In this embodiment, the service provision control unit 112 is configured to update viewing performance information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user towards the content provided by the distribution user. Viewing behavior includes, but is not limited to, the viewing of the content itself, input of input information (comments, likes, items, etc.), and billing. Viewing performance information includes, but is not limited to, viewing time, number of viewing days, number of inputs of input information (items, comments, and likes, etc.), and billing amount.

[0033] Furthermore, the service provision control unit 112 is configured to change the viewing performance information of a viewing user based on the input of a specific object by the viewing user, separately from the updates based on the viewing behavior described above. For example, the viewing performance information includes multiple items, and the service provision control unit 112 increases or decreases the values ​​of some or all of these items. For example, the service provision control unit 112 changes (for example, increases) the viewing time or number of viewing days included in the viewing performance information based on the input of a specific object.

[0034] In this embodiment, the specific object includes various electronic elements (items, etc.) that can be input by the viewing user. The specific object is input, for example, by the viewing user while viewing the content. For example, the service provision control unit 112 is configured to accept object input from the viewing user during content distribution, and changes the viewing performance information separately from updates based on viewing behavior when the object input by the viewing user is a specific object, while not changing the viewing performance information separately from updates based on viewing behavior when the input object is not a specific object.

[0035] Thus, in this embodiment, the content distribution server 10 updates viewing history information of distribution users or viewing users managed in association with content, based on the viewing behavior of the viewing user. Based on the input of a specific object by the viewing user, the viewing history information is changed separately from the update based on the viewing behavior, and such changes in viewing history information can be said to be a new effect associated with the input of an object. In other words, the server 10 realizes a new effect associated with the input of an object in the content distribution service.

[0036] In this embodiment, the content distributed includes various types of digital content. For example, the content consists of images (video or still images) and audio, or one of these. The content is transmitted in real time (live distribution) from, for example, the user terminal 30 of the distribution user providing the content (hereinafter sometimes referred to as the distribution terminal 30), or it is provided in advance from the distribution terminal 30 and stored in a storage device such as the storage 15. Live distribution of content may be accompanied by a certain delay (time lag) depending on the settings of the distribution user or the network conditions. Live distribution of content is performed using a streaming method that uses a protocol such as HTTP Live Streaming (HLS). The content distribution user includes businesses such as broadcasters.

[0037] Furthermore, the content transmitted from the distribution terminal 30 consists, for example, of video and audio of the distribution user input (captured) via the camera and microphone of the distribution terminal 30. This content also consists, for example, of video and audio corresponding to the screen output by the distribution terminal 30. Furthermore, this content also consists, for example, of video corresponding to the screen output by an application (e.g., a game) running on the distribution terminal 30, as well as audio output by the application and / or audio of the distribution user input via the microphone of the distribution terminal 30.

[0038] Furthermore, in this embodiment, the content distributed is such that a portion of the data constituting the content is transmitted in real time from the distribution terminal 30, while a portion of the data constituting the content can be pre-stored in the server 10 or the viewing terminal 30. For example, the audio constituting the content is transmitted in real time from the distribution terminal 30, while the images constituting the content are pre-stored in the server 10 or the viewing terminal 30, and the content is generated in the server 10 or the viewing terminal 30 based on this data.

[0039] Furthermore, for example, in addition to the audio that constitutes the content, motion data (e.g., motion data) for operating objects such as characters may be transmitted in real time from the distribution terminal 30, while images constituting the content may be pre-stored in the server 10 or viewing terminal 30, and these images may include model data of the objects. In this case, the motion data is generated based on the actions of the distribution user (including head movements and changes in facial expressions, etc.) recognized via the camera of the distribution terminal 30. The content generated in the server 10 or viewing terminal 30 then includes objects such as characters that operate based on the model data and motion data.

[0040] In this embodiment, various processes may be performed based on the viewing history information of the viewing user. For example, the service provision control unit 112 may be configured to determine the viewing user's level with respect to the corresponding distribution user (in which the viewing history information is directly or indirectly associated and managed) based on the viewing user's viewing history information. This level can also be set as a parameter indicating the degree of support the viewing user provides to the corresponding distribution user. This level may be expressed in other terms such as rank, grade, and class. Such a configuration makes it possible to influence the viewing user's level through object input.

[0041] Furthermore, the service provision control unit 112 may be configured to manage the achievement status of predetermined viewing performance conditions related to the viewing performance information of viewing users. For example, conditions may be set for each of multiple levels, and the viewing user's level to the distribution user may be determined based on the achievement status of those conditions. In this case, the service provision control unit 112 may be configured to change the viewing performance information in a direction that achieves the viewing performance conditions based on the input of the specific object. Such a configuration makes it possible to influence the achievement of viewing performance conditions through the input of an object.

[0042] In this embodiment, the amount of change in viewing performance information may differ depending on the type of specific object input. That is, the service provision control unit 112 may be configured to change the viewing performance information by a first amount of change based on the input of a first type of specific object by the viewing user, and to change the viewing performance information by a second amount of change based on the input of a second type of specific object by the viewing user. Such a configuration provides the viewing user with the enjoyment of selecting the type of specific object to input.

[0043] Furthermore, the items of the viewing performance information that change may differ depending on the type of specific object that is input. In other words, the service provision control unit 112 may be configured to change a first item (e.g., viewing time) included in the viewing performance information based on the input of a first type of specific object by the viewing user, while changing a second item (e.g., number of viewing days) included in the viewing performance information based on the input of a second type of specific object by the viewing user. Such a configuration provides the viewing user with the enjoyment of choosing the type of specific object to input.

[0044] Furthermore, the service provision control unit 112 may be configured to modify viewing performance information in such a way that viewing performance information to which changes based on input from a specific object are not applied (i.e., the effects of such changes are excluded) can be identified. For example, separate from viewing performance information updated based on viewing behavior, viewing performance information to which changes based on input from a specific object are applied (or the amount of such changes) is managed. This configuration makes it possible to use viewing performance information to which the effects of changes based on input from a specific object are excluded.

[0045] In this embodiment, changes in viewing performance information based on input of a specific object can be realized in various ways. For example, the service provision control unit 112 may be configured to add a predetermined amount (for example, set for the specific object) to the viewing performance information in response to input of a specific object. Alternatively, the service provision control unit 112 may be configured to change the viewing performance information at a specific point in time (for example, the end of the viewing performance information aggregation period) based on input of a specific object (for example, by multiplying by a predetermined multiplier). Such configurations can realize changes in viewing performance information based on input of a specific object in various ways.

[0046] In this embodiment, a specific object may be granted to a viewer at various times. For example, the service provision control unit 112 may be configured to grant a specific object to a viewer who has met predetermined granting conditions. The granting conditions include, but are not limited to, various conditions, including, for example, conditions relating to the input of items to content, or conditions relating to the consumption of a predetermined value (including coins, points, items, and real currency, etc.). In this case, the service provision control unit 112 may be configured to increase the value of a specific parameter in response to the input of items to content or the consumption of a predetermined value, and the granting condition may be a condition relating to the value of the specific parameter (for example, a condition that the value of the specific parameter becomes equal to or greater than a predetermined value). Furthermore, in this case, the specific object may be granted along with a decrease in the value of the specific parameter. Such a configuration provides users with the enjoyment of acquiring specific objects.

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

[0048] Figure 2 illustrates the information managed by the user information table 1511 in this example. The user information table 1511 manages information about users of the content distribution service and, as shown in the figure, associates with a "user account" that identifies an individual user, and manages information such as "basic information" including the 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, "followed user information" which is information about other users that this user follows, "family information" which is information about families that this user belongs to as a family member, "rank" which indicates the rank as a distribution user, "rank meter value" which indicates the value of the rank meter which is a parameter for determining rank up and down, "coin holdings" which indicates the number of virtual coins that can be used in the content distribution service, "diamond holdings" which indicates the number of virtual diamonds that are held, "classification text" which is the classification as a distribution user set by the user themselves, and "event mile holdings" which indicates the number of event miles held (specific parameter).

[0049] In this example, a family is a community of fans who support a streaming user, and can be joined by invitation from the streaming user or family administrator (e.g., designated by the streaming user), or by approval of a user's application to join by the streaming user or family administrator. Family information includes information that identifies the streaming user corresponding to each family (e.g., user account). In this example, there is an upper limit on the number of members in a family (e.g., 100). In this example, a user can join (belong to) multiple families.

[0050] In this example, coins are awarded to users both for free and for a fee under various circumstances. 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, as will be explained in more detail later, are awarded as one of the rewards for streaming users.

[0051] In this example, event miles are points awarded based on a viewer's viewing behavior. Specifically, they are awarded based on the number of coins (or items) consumed by viewers watching content streamed by participating broadcasters during a particular event. For example, the more coins consumed, the more event miles are awarded to the viewer.

[0052] Figure 3 is a diagram illustrating the rank of the delivery user in this example. As shown in the diagram, in this example there are six rank tiers: "S", "A", "B", "C", "D", and "E". The "S" rank tier consists of six ranks from "S1" to "S6", and each of the four rank tiers, "A", "B", "C", and "D", consists of three ranks (for example, "A1" to "A3"). The "E" rank tier consists of one rank, "E1". In other words, in this example there are 19 ranks (6 + 3 × 4 + 1 = 19).

[0053] Furthermore, in the rank tiers, "S" is higher and "E" is lower. Within the same rank tier, a higher number attached to the rank tier indicates a higher rank, and a lower number indicates a lower rank. In this example, the user's rank is initially set to "D1". As will be explained in more detail later, in this example, the rank is updated based on the daily content delivery performance.

[0054] Figure 4 illustrates the information managed by the distribution management table 1512 in this example. The distribution management table 1512 manages information related to individual distributions and, as shown in the figure, associates the "distribution ID" that identifies an individual distribution (content) with the "distribution user account" that identifies the distribution user, the "distribution start date and time" which is the date and time the distribution started, the "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 during the distribution of the content, the "number of likes" which is the number of "likes" entered by viewing users during the distribution of the content, the "number of coins consumed" which is the number of coins consumed in response to items entered by viewing users during the distribution of the content, the "number of support points" which is the total value of support points to be awarded for this distribution, and the "distribution tag information" which is information related to the distribution tags assigned to this distribution.

[0055] Figure 5 illustrates the information managed by the Viewer Management Table 1513 by Streaming User in this example. The Viewer Management Table 1513 manages information about viewers for each streaming user in the target month and year. As shown in the figure, it associates the viewer's "fan level" for the streaming user in the target month and year with a combination of "streaming user account" to identify the streaming user, "viewer user account" to identify the viewer, and "target month and year." It manages information such as the viewer's "coin consumption," "viewing time," "viewing days," and "number of comments entered" for the corresponding streaming, "additional viewing time" indicating viewing time added by level acceleration items, and "additional viewing days" indicating the number of viewing days added. Level acceleration items are items that accelerate the increase in fan level. Details on the addition of viewing time and viewing days by level acceleration items will be described later. The number of coins consumed, viewing time, viewing days, and number of comments entered can be said to be viewing performance information that is updated based on the viewing behavior of viewers towards the content provided by the corresponding streaming user.

[0056] In this example, a fan level for a broadcaster is determined based on the monthly viewing behavior of viewers of the content broadcast by that broadcaster. Figure 6 illustrates the behavioral conditions (viewing performance 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 as behavioral conditions for each fan level, and a user who satisfies any one of these conditions becomes the corresponding fan level (their level increases). For example, fan level "1" has two conditions: condition 1, "consume 10 coins or more, watch for 1.5 hours or more, and enter 4 comments or more," and condition 2, "consume 100 coins or more." A user who satisfies either of these two conditions becomes a viewer of fan level "1". Furthermore, for example, Fan Level "4" has three conditions: Condition 1, "Consume 1000 coins or more, watch for 5 hours or more, watch for 3 days or more, and enter 30 comments or more"; Condition 2, "Consume 3000 coins or more, watch for 2 hours or more, and enter 5 comments or more"; and Condition 3, "Consume 5500 coins or more". Users who satisfy any one of these three conditions become Fan Level "4" viewers. Note that these behavioral conditions are examples, and in other examples of this embodiment, various other conditions may be set as behavioral conditions. For example, instead of conditions related to the number of coins consumed, conditions related to the number of input items, or the degree of contribution to the support points awarded to the streaming user (stream), may be set.

[0057] This fan level determination is performed in real time during content distribution. Specifically, during content distribution, server 10 updates the number of coins consumed, viewing time, viewing days, number of comments entered, additional viewing time, and additional viewing days in the user-specific viewing user management table 1513 in real time for each viewing user, and determines whether the fan level has increased based on this information. When determining whether the action conditions have been met, the value obtained by adding the additional viewing time to the viewing time, and the value obtained by adding the additional viewing days to the viewing days, are used. When the fan level increases, the fan level value of the corresponding record in the user-specific viewing user management table 1513 is updated. Note that for purposes other than determining the fan level, viewing time and viewing days may be used without considering additional viewing time and additional viewing days.

[0058] In this example, viewers with a fan level of "4" or higher are recognized as special fans of the corresponding streaming user. When a viewer reaches a fan level of "4," the value of the special fan flag in the corresponding record in the streaming user-specific viewer management table 1513 is updated.

[0059] Figure 7 illustrates the information managed by the item ownership management table 1514 in this example. The item ownership management table 1514 manages information about the number of ownership-managed items owned by a user, and as shown in the figure, it manages information such as the "number owned," which is the number of ownership-managed items owned by the user, in association with a combination of a "user account" that identifies the user and an "item ID" that identifies the ownership-managed item. In this example, during content distribution, the items entered by viewing users who view the content include general items whose ownership count is not managed (assigned each time they are entered) and ownership-managed items whose ownership count is managed. Of these items, the item ownership management table 1514 manages the ownership count of ownership-managed items.

[0060] The above explains the information managed by each table. Next, we will explain the processes executed by the content distribution server 10 in this example, and the screens displayed on the user terminal 30.

[0061] Figure 8 illustrates the top screen 50 of the content distribution service displayed on the user terminal 30. This screen 50 is the starting point when using the content distribution service, and as shown in the figure, it has a selection area 52 that displays the text "Follow," "Popular," "Featured," and "All," a list display area 54 located below the area 52, and a circular distribution button 56 located in the upper right corner of the screen.

[0062] Selection area 52 is an area for selecting the content to be displayed in the list display area 54. Specifically, if "Follow" is selected in selection area 52, the list display area 54 will display a list of broadcasts (content currently being broadcast) from other users that the user is following. Similarly, if "Popular" is selected in selection area 52, the list display area 54 will display a list of broadcasts with a large number of viewers. Also, if "Featured" is selected in selection area 52, the list display area 54 will display a list of broadcasts that are generating a lot of buzz (for example, broadcasts with a large number of comments, likes, and coins consumed). Furthermore, if "All" is selected in selection area 52, all broadcasts will be included in the list display area 54.

[0063] As shown in the diagram, the list display area 54 has multiple individual display areas 541 arranged vertically in two columns, each displaying information about an individual distribution. The individual display areas 541 are configured so that the user can start watching the corresponding distribution (playback of the corresponding content begins) according to their selection. The list display area 54 is configured so that the displayed individual display areas 541 can be switched by flicking or sliding up or down.

[0064] Figure 9 illustrates the display content of the individual display area 541. The individual display area 541 displays an image pre-set by the content distribution user, the distribution user's account name, and the number of viewers (current value), etc. As shown in the figure, the first tag object 5411 and the second tag object 5412 are arranged side by side at its lower end. The first tag object 5411 displays the classification text (managed in the user information table 1511), which is the distribution user's classification set by the distribution user themselves, in hashtag format (a format in which "#" is added to the beginning of the string) (in the example in Figure 9, it displays "#eatingchallenge"). The second tag object 5412 also displays the latest distribution tag assigned by viewers to the corresponding distribution in hashtag format (in the example in Figure 9, it displays "#curry").

[0065] Returning to the top screen 50 in Figure 8, the distribution button 56 is an object for the user to distribute content as a distribution user. When the distribution button 56 is selected by the user, the distribution preparation screen 60 illustrated in Figure 10 is displayed. As shown in the figure, the distribution preparation screen 60 has a distribution title input area 62 for entering the distribution title, a secret distribution setting switch 64 for setting the secret distribution mode, a post setting button 66 for setting up posts (posting messages to SNS) that are automatically performed during distribution, and a distribution start button 68 with the text "Start!" attached to it. Secret distribution is a content distribution mode in which only new viewers (specifically, viewers whose total viewing time over a certain period for the corresponding distribution user is less than a predetermined value) can view the content.

[0066] When the distribution start button 68 is selected, content distribution begins. Specifically, content data consisting of video and audio input (recorded) via the camera and microphone of the distribution terminal 30 is sent to the server 10. In addition, a new record is inserted into the distribution management table 1512 in response to the start of content distribution.

[0067] Figure 11 illustrates a distribution screen 70 that is output on the distribution terminal 30 in response to the start of content distribution. As shown in the figure, the screen 70 has a video display area 71 that covers the entire screen, a basic information display area 72 located at the top of the screen, an operation area 73 located at the bottom of the screen, a comment display area 74 located to the upper left of the area 73, a tag display area 75 located above the area 74, and a performance display area 76 located to the upper left of the area 75.

[0068] The video display area 71 displays the content being streamed, that is, the image input via the camera of the streaming terminal 30. Typically, the streaming user uses the front camera of the streaming terminal 30, etc., to film themselves, and in this case, the streamed content includes the streaming user's own image.

[0069] The basic information display area 72 displays basic information about this distribution (specifically, distribution user information (profile picture, etc.), the number of users watching this distribution (current value), and the number of "likes" entered by users watching this distribution), and has a user viewing information display area 721. The area 721 displays information about multiple users watching the content being distributed, and specifically, multiple icon objects 722, each corresponding to an individual user, are arranged side by side in a horizontal direction. The object 722 has a circular shape and displays the profile picture of the corresponding user. The multiple icon objects 722 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).

[0070] The control area 73 includes a stop broadcast button 731, a microphone setting button 732, and a camera setting button 733.

[0071] The unsubscribe button 731 is an object used by the distribution user to stop the distribution of content. When the unsubscribe button 731 is selected by the distribution user, the distribution of content (transmission of content data from the distribution terminal 30 to the server 10) is stopped.

[0072] The microphone settings button 732 is an object used by the streaming user to mute the microphone. When the microphone settings button 732 is selected by the streaming user, the microphone's mute state is toggled.

[0073] The camera setting button 733 is an object used by the streaming user to set the active camera. When the camera setting button 733 is selected by the streaming user, the active camera (e.g., front camera or rear camera) is switched.

[0074] The comment display area 74 is an area for displaying user comments entered by each viewing user, as well as system comments automatically entered by the server 10. Specifically, multiple comment objects 741, each corresponding to an individual comment, are arranged vertically within the area 74. The comment display area 74 is configured such that when a new comment is entered, a corresponding comment object 741 is added to the bottom, and the existing comment objects 741 move upwards in sequence. The displayed comment objects 741 in the comment display area 74 can be switched by flicking or sliding up or down.

[0075] The tag display area 75 displays information about the distribution tags assigned to this distribution. Specifically, the area 75 contains multiple tag objects 751, each corresponding to an individual tag, arranged side by side in a horizontal direction.

[0076] The animation display area 76 is the area where animations are displayed in response to the input of gift items. Details of these animations will be described later.

[0077] Figure 12 illustrates a viewing screen 80 output on the viewing terminal 30. For example, when a user selects a streaming (content) via the list display area 54 of the top screen 50, a viewing screen 80 for viewing the selected streaming is output on the viewing terminal 30. As shown in the figure, the screen 80, like the streaming screen 70 described above, has a video display area 81, a basic information display area 82, an operation area 83, a comment display area 84, a tag display area 85, and a performance display area 86.

[0078] The basic information display area 82, like the basic information display area 72, has a viewer user information display area 821, in which multiple icon objects 822 are arranged side by side in the left-right direction.

[0079] The operation area 83 includes an input mode switching button 831, a comment input area 832, a "Like" button 833 with a heart mark, and a gift input button 834 with a gift image.

[0080] The comment input area 832 is an area for viewers to enter comments or distribution tags. While the input mode switching button 831 is not selected, the comment input area 832 is in normal comment input mode. In comment input mode, when a string is entered into the comment input area 832 and the confirmation operation is performed, the string is sent as a user comment, and on the corresponding distribution terminal 30 (the user terminal 30 of the distribution user distributing the content being viewed) and each viewing terminal 30 (each user terminal 30 of multiple viewing users viewing the same content), comment objects 741 and 841 corresponding to the user comment are added in the comment display areas 74 and 84 of the distribution screen 70 and viewing screen 80. The comment objects 741 and 841 corresponding to the user comment display the content of the comment (string) along with the account name of the viewing user who entered the comment. Also, when a user comment is entered, the server 10 updates (adds 1) the number of comments for the corresponding distribution in the distribution management table 1512.

[0081] Furthermore, when the input mode switching button 831 is selected, the comment input area 832 switches to tag input mode. In tag input mode, when a string is entered into the comment input area 832 and confirmed, that string is sent as a distribution tag, and that tag is attached to the distribution. In this example, only family members of the corresponding distribution user are allowed to enter tags. Specifically, the input mode switching button 831 on the viewing screen 80 becomes selectable (enabled) if the viewing user is a family member of the distribution user, while it becomes unavailable (disabled) if the viewing user is not a family member of the distribution user. In this example, the number of tags that can be attached to a single distribution over a certain period is limited; specifically, up to three tags can be attached every five minutes.

[0082] When a distribution tag is assigned, the corresponding tag objects 751 and 851 are added to the tag display areas 75 and 85 of the corresponding distribution screen 70 and viewing screen 80. In the tag display areas 75 and 85, the tag objects 751 and 851 are arranged horizontally so that the left side is newer (later assigned time). Therefore, the tag objects 751 and 851 corresponding to newly assigned tags are added to the leftmost part of the tag display areas 75 and 85. Tag objects 751 and 851 corresponding to tags that have been assigned for 5 minutes or more are deleted (for example, they disappear with an animation effect moving to the right).

[0083] In this example, tag objects 751 and 851 display the tag content in hashtag format, with a "#" prefix added to the beginning of the string. For example, if the tag content is "Tokyo sightseeing," tag objects 751 and 851 will display "#Tokyo sightseeing." The horizontal length of tag objects 751 and 851 is automatically adjusted according to the length of the string to be displayed.

[0084] Furthermore, when a tag is assigned, comment objects 741 and 841 corresponding to the system comment notifying the assignment of the tag are added to the comment display areas 74 and 84 of the corresponding streaming screen 70 and viewing screen 80. The comment objects 741 and 841 corresponding to the system comment display the content of the assigned tag along with the account name of the viewing user who assigned (entered) the tag. For example, a comment such as "xx tagged the stream with "#TokyoTourism"" will be displayed. In addition, when a tag is assigned, the streaming tag information for the corresponding stream is updated in the streaming management table 1512.

[0085] The "Like" button 833 is an object for viewers to input a "Like" for the broadcasting user (or content). When the button 833 is selected by a viewer, a "Like" is input, and comment objects 741 and 841 corresponding to a system comment notifying the input of a "Like" are added to the comment display areas 74 and 84 of the corresponding broadcasting screen 70 and viewing screen 80. The comment objects 741 and 841 corresponding to the system comment display the account name of the viewer who input the "Like," along with text indicating that a "Like" has been input. In addition, when a "Like" is input, a corresponding visual effect (for example, an animated video effect where heart-shaped objects flow from the bottom to the top of the screen) is displayed in the video display areas 71 and 81 of the broadcasting screen 70 and viewing screen 80. Furthermore, when a "Like" is input, the server 10 updates the "Like Count" of the corresponding broadcast in the broadcasting management table 1512 (incrementing by 1).

[0086] The item input button 834 is an object for the viewer to input an item. When this button 834 is selected, an item selection screen 90 for selecting the item to input is displayed overlaid on the lower area of ​​the viewing screen 80, as illustrated in Figure 13.

[0087] Figure 14 illustrates an item selection screen 90. As shown in the figure, the screen 90 includes a selection area 91, a list display area 94 located below the area 91 for displaying one or more items in a list, a price range selection area 96 located below the area 94 for selecting the price range of the items to display, and a purchase button 97 located in the lower right corner of the screen, which is an object for purchasing coins. The number of coins held by the corresponding user is displayed in the lower left corner of the item selection screen 90.

[0088] 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 "Popular," "History," "Limited Time," and "Owned Items." In this example, if any text other than "Owned Items" is selected in the selection area 91, general items that are not managed in terms of ownership quantity will be displayed in the list display area 94. In this example, general items include gift items, but not level-accelerating items. Specifically, if "Popular" is selected in the selection area 91, the list display area 94 will display a list of gift items that have been entered many times across the entire content distribution service; if "History" is selected, the list display area 94 will display a list of gift items that the corresponding user has entered in the past; and if "Limited Time" is selected, the list display area 94 will display a list of gift items that are offered for a limited time and are available for entry at that time (for example, gift items that can be entered in limited-time events within the content distribution service). On the other hand, if "Owned Items" is selected in the selection area 91, the list display area 94 will display items that are managed in terms of ownership quantity. In this example, the inventory management items include both gift items and level-accelerating items.

[0089] The price range selection area 96 is an area for further selecting (filtering) the displayed content in the list display area 94 based on the price range of the gift items. When any price range is selected in the price range selection area 96, the gift items in the corresponding price range will be included in the list display area 94.

[0090] The item selection screen 90 in Figure 14 corresponds to the case where "Popular" is selected in the selection area 91. If text other than "Owned Items" is selected in the selection area 91, the list display area 94 will have multiple individual display areas 941 arranged vertically in four columns, each displaying information about an individual general item (i.e., a gift item). Each individual display area 941 displays an image corresponding to the general 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 flicking or sliding up or down. When any of the individual display areas 941 are selected by the viewing user, the corresponding general item is input.

[0091] Figure 15 illustrates the item selection screen 90 when "Owned Items" is selected in the selection area 91. In this state, as shown in the figure, the list display area 94 has multiple individual display areas 942 arranged vertically in four columns, each displaying information about individual owned items. The individual display areas 942 display an image corresponding to the owned item and the number of that item owned by the corresponding user (managed in the owned item management table 1514). The list display area 94 is configured so that the displayed individual display areas 942 can be switched by flicking or sliding up or down. When any of the individual display areas 942 is selected by the viewing user, the corresponding owned item is entered.

[0092] In the item selection screen 90 illustrated in Figure 15, if the corresponding possession management item is a gift item, the corresponding individual display area 9421 displays the image corresponding to the gift item and the number of times the corresponding user possesses that item. If the corresponding possession management item is a level acceleration item, the corresponding individual display area 9422 displays the image corresponding to the level acceleration item (for items that add viewing time, an hourglass image; for items that add viewing days, a wristwatch image, etc.), the number of times the corresponding user possesses that item, and the amount of viewing time or viewing days added (6 hours, 12 hours, 1 day, and 2 days, etc.). In this example, level acceleration items add either viewing time or viewing days depending on their type. Furthermore, even when level acceleration items add the same item (viewing time or viewing days), the amount added differs depending on their type.

[0093] Figure 16 is a flowchart illustrating the processes that the server 10 executes in response to item input. When an item is input, the server 10 first adds a comment object corresponding to the system comment notifying the input of the item (step S100). Specifically, in the comment display areas 74 and 84 of the corresponding distribution screen 70 and viewing screen 80, comment objects 741 and 841 corresponding to the system comment notifying the input of the item are added. The comment objects 741 and 841 corresponding to the system comment display the name of the input item along with the account name of the viewing user who entered the item.

[0094] Next, if the input item is a gift item (YES in step S110), the server 10 displays a visual effect corresponding to the input gift item (step S120). Specifically, a visual effect corresponding to the input gift item is displayed in the visual effect display areas 76 and 86 of the corresponding distribution screen 70 and viewing screen 80. This visual effect display includes the display of a visual effect object corresponding to the input gift item.

[0095] Figure 17 illustrates the performance objects 761 and 861 displayed in the performance display areas 76 and 86. As shown in the figure, these objects 761 and 861 display the profile picture and account name of the viewer user who entered the gift item, as well as the name and image of the gift item. The performance objects 761 and 861 disappear after a predetermined time (for example, 3 seconds) has elapsed since they were displayed. Up to a predetermined number (for example, 3) of performance objects 761 and 861 are arranged vertically in the performance display areas 76 and 86.

[0096] In this example, some gift items (for example, general items whose price is above a threshold, and all items with a quantity management function) will, in response to their input, display not only the visual effects in the visual display areas 76 and 86, but also larger visual effects in the video display areas 71 and 81 (such as the display of corresponding video effects).

[0097] Returning to the flowchart in Figure 16, if the entered gift item is a general item (YES in step S130), the server 10 consumes the corresponding user's coins (step S140). Specifically, in the user information table 1511, the number of coins for the entered gift item is deducted from the number of coins held by the corresponding user (the viewing user who entered the gift item), and in the distribution management table 1512, that number of coins is added to the number of coins consumed for the corresponding distribution. If the entered gift item is not a general item (i.e., it is an item with a limited number of coins) (NO in step S130), this coin consumption is skipped.

[0098] On the other hand, if the entered item is a level-accelerating item (not a gift item) (NO in step S110), server 10 adds viewing time or viewing days (step S150). Specifically, in the viewing user management table 1513 per distribution user, the amount added to viewing time or viewing days corresponding to the entered level-accelerating item is added to the additional viewing time or additional viewing days of the corresponding record. As mentioned above, the amount added to viewing time or viewing days is set for the entered level-accelerating item.

[0099] Thus, in this example, by inputting level-accelerating items, viewers can efficiently acquire viewing time or viewing days used to determine their fan level. As a result, viewers can, for example, obtain special fan status from many streamers.

[0100] 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, comments, and coins consumed, and the higher these values ​​are, the more support points are awarded. When the distribution user selects the stop distribution button 731 on the distribution screen 70, the distribution of the content ends.

[0101] Here, we will explain the process for determining the rank of a streaming user. In this example, the user's rank for the day is determined (updated) based on the number of support points they earned as a streaming user the previous day. Figure 18 is a flowchart illustrating the processes that server 10 executes when updating each user's rank. These processes are executed every night (for example, at 3 a.m.).

[0102] Server 10 first calculates the number of support points each user earned as a broadcasting user the previous day, as shown in the diagram (step S200). The number of support points each user earned the previous day is calculated by referring to the broadcasting user account, broadcast start date and time, and number of support points in the broadcasting management table 1512. If a user broadcasts multiple times in one day, the number of support points earned from each broadcast is added together.

[0103] After calculating the number of support points for each streaming user from the previous day, the server 10 then updates the rank meter value for each user (step S210). Figure 19 illustrates the rules for updating the rank meter value. As shown in the figure, in this example, the rank meter value changes based on the user's ranking within the rank tier to which they belong, based on the number of support points for the previous day. The initial value of the rank meter value is "0".

[0104] The rules for updating the rank meter value are as follows: First, if the rank in the number of support points within a rank range falls within the top 10%, the rank meter value changes by "+2" (an increase of 2 points). Similarly, if the rank falls within the top 11-30% (the remaining 20% ​​after subtracting the top 10% from the top 30%), the change is "+1". If the rank falls within the middle 30% (top 31-60%), the change is "±0" (no change). If the rank falls within the bottom 40%, the change is "-1" (a decrease of 1 point). Note that if no broadcast took place the previous day, the rank meter value changes by "-1" regardless of the rank within the rank range. In step S210, the rank meter value for each user is updated in the user information table 1511 according to the update rules illustrated in Figure 19.

[0105] Returning to the flowchart in Figure 18, after updating each user's rank meter value, the server 10 then updates the rank based on the updated rank meter value (step S220). 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 ranks up or down. Specifically, the rank of the corresponding user is updated in the user information table 1511. The rank meter value of the user whose rank has been updated (the user who has been ranked up or down) is cleared to 0. In other examples of this embodiment, in order to suppress rapid rank ups and downs in a short period of time, for example, in the case of rank ups and downs across rank ranges, the absolute value of the required rank meter value may be made larger (for example, +6 or -6) compared to rank ups and downs within the same rank range.

[0106] The above explains the process for determining the rank of a streaming user. Next, we will explain the process for awarding diamonds to streaming users. In this example, diamonds, one of the rewards for streaming users, are awarded based on the streaming time and rank from the previous day. Figure 20 is a flowchart illustrating the processes that server 10 executes when awarding diamonds to each user. These processes are executed every night, at an earlier time (for example, midnight) than the process executed when updating each user's rank as illustrated in Figure 18.

[0107] Server 10 first calculates the delivery time for each user the previous day, as shown in the diagram (step S300). Specifically, the delivery time for each user the previous day is calculated by referring to the delivery user account, delivery start date and time, and delivery duration in the delivery management table 1512. If a user has made multiple deliveries in one day, the delivery durations of each of the deliveries are added together.

[0108] Next, server 10 grants each user a number of diamonds based on the calculated delivery time and the base number of diamonds (step S310). Specifically, each user is granted a number of diamonds equal to the calculated delivery time multiplied by the base number of diamonds. The base number of diamonds is predetermined for each rank, with higher ranks receiving more diamonds, and the base number of diamonds corresponding to each user's rank on the previous day is applied. When diamonds are granted to a user, the corresponding number of diamonds held by that user is updated in user information table 1511. In this example, diamonds can be exchanged for coins or real currency.

[0109] Here, we will explain the process when a user acquires an item for managing their possession count. Figure 21 illustrates the My Page screen 200 output on the user terminal 30. As shown in the figure, the screen 200 displays information about the corresponding user (profile picture, etc.) and has an event mile information display area 202 that displays information about the event miles the user possesses. The event mile information display area 202 displays the number of event miles the corresponding user possesses (managed in the user information table 1511) and has a mileage store button 204. This button 204 is an object for exchanging event miles for items. In this example, the items that can be exchanged for event miles are items for managing possession count.

[0110] When the Mileage Store button 204 is selected, the Mileage Exchange screen 210, as illustrated in Figure 22, is displayed. As shown in the figure, the screen 210 has a list display area 212 that displays a list of items that can be exchanged for event miles. The area 212 has a first area 214 that displays a list of gift items among the exchangeable items, and a second area 216 located below the first area 214 that displays a list of level acceleration items among the exchangeable items. The first area 214 and the second area 216 each have multiple individual display areas 218 arranged vertically in three columns, each displaying information about an individual item. The list display area 212 is configured so that the displayed individual display area 218 switches depending on whether the user flicks or slides up or down. The individual display area 218 displays an image of the corresponding item and the required number of miles (price). When the area 218 is selected, after final confirmation by the user via a screen not shown, the exchange of the corresponding item for event miles is performed. When the exchange takes place, the number of event miles held by the corresponding user is updated in the user information table 1511, and the number of records held by the corresponding user is updated in the owned item management table 1514.

[0111] In the example above, the number of times level-up items can be used may be limited. For example, a monthly limit (e.g., 4 times / month) may be set for the same distribution user to use level-up items. Additionally, an expiration date and time may be set for individual level-up items.

[0112] In the example above, the level-accelerating item was used to add viewing time or viewing days, but it could also be used to add other items in viewing performance information (for example, the number of coins consumed or the number of comments). Furthermore, the level-accelerating item could also be configured to directly increase the fan level (for example, by adding a predetermined value to the fan level determined upon fulfilling certain action conditions, thereby increasing the level by a predetermined number of stages).

[0113] In the example described above, the amount set for a level-accelerating item is added to the viewing time or viewing days in response to the input of that item. However, the values ​​of these items may be increased in other ways. For example, if a level-accelerating item is entered during a target month and year, a predetermined multiplier (for example, set based on the type and number of level-accelerating items entered during the period) may be multiplied at the end of that month or year by a predetermined multiplier (for example, set based on the type and number of level-accelerating items entered during the period).

[0114] In the example described above, level-accelerating items are entered by viewers while the content is being distributed, but they may be entered at other times. For example, level-accelerating items may be entered at times other than when the content is being distributed, or they may be entered via a user profile screen or similar that displays information about the distribution user.

[0115] In the example above, level-accelerating items were given to viewers in exchange for event miles, but the conditions for granting level-accelerating items are not limited to this, and various other conditions may apply. For example, level-accelerating items may be given to users as various rewards awarded upon fulfilling various conditions (e.g., login bonuses, rewards for watching recommended streams, event prizes, and anniversary commemorative items).

[0116] The content distribution server 10 of this embodiment, as described above, updates viewing history information (e.g., viewing time or number of viewing days) of a distribution user or a viewing user managed in association with the content, based on the viewing behavior of the viewing user. Based on the input of a specific object (e.g., a level acceleration item) by the viewing user, it changes the viewing history information separately from the update based on the viewing behavior (e.g., adding a set amount), and such changes in viewing history information can be said to be a new effect associated with the input of the object. In other words, the server 10 realizes a new effect associated with the input of an object in the content distribution service.

[0117] 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 the cooperation of the server 10 and the user terminal 30, or by the user terminal 30 alone. In other words, the system (or apparatus) of the present invention may consist of the content distribution server 10, or it may consist of the content distribution server 10 and the user terminal 30, or it may consist of the user terminal 30 alone.

[0118] The processes and procedures described herein can be implemented by software, hardware, or any combination thereof, in addition to those explicitly described herein. For example, the processes and procedures described herein can be implemented by implementing the logic corresponding to those processes and procedures on a medium such as an integrated circuit, volatile memory, non-volatile memory, or magnetic disk. Furthermore, the processes and procedures described herein can be implemented as computer programs corresponding to those processes and procedures and executed by various types of computers.

[0119] Even if a process or procedure described herein is described as being performed by a single device, software, component, or module, such process or procedure may be performed by multiple devices, multiple software programs, multiple components, and / or multiple modules. Furthermore, the software and hardware elements described herein can also be realized by integrating them into fewer components or by decomposing them into more components. [Explanation of Symbols]

[0120] 10. Content distribution server 11 Computer Processors 111 Management Function Control Unit 112 Service Provision Control Unit 15. Storage (mechanisms) 151 Various Tables 1511 User Information Table 1512 Distribution Management Table 1513 Viewer Management Table by Streaming User 1514 Item Management Table 20 Communication Networks 30 User terminals 40 Server-side programs 42 Terminal-side programs 50 Top screen 60. Streaming preparation screen 70 Streaming screen 80 Viewing screen 90 Item Selection Screen 200 My Page Screen 210 Miles Exchange Screen

Claims

1. A system comprising one or more computer processors for providing content distribution services, wherein the one or more computer processors are A process to update viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user towards the content provided by the distribution user, Based on the input of a specific object by the viewing user, a process is executed to change the viewing history information of the viewing user, separate from the update based on the viewing behavior. system.

2. The aforementioned viewing performance information includes viewing time or viewing days, The process of changing the aforementioned viewing performance information involves changing the viewing time or the number of viewing days. The system according to claim 1.

3. The one or more computer processors further perform a process to determine the level of the viewing user for the distribution user based on the viewing history information. The system according to claim 1.

4. The aforementioned specific object is input by the viewing user while viewing the content. The system according to claim 1.

5. The one or more computer processors further execute a process to accept object input from the viewing user during the distribution of the content. The process for changing the viewing performance information changes the viewing performance information separately from the update based on the viewing behavior when the object entered by the viewing user is the specific object, while not changing the viewing performance information separately from the update based on the viewing behavior when the object entered by the viewing user is not the specific object. The system according to claim 4.

6. The one or more computer processors further execute processes to manage the achievement status of viewing performance conditions related to the viewing performance information of the viewing user, The process of changing the aforementioned viewing performance information involves changing the aforementioned viewing performance information in a direction that achieves the aforementioned viewing performance conditions. The system according to claim 1.

7. The process for changing the viewing performance information involves changing the viewing performance information by a first amount of change based on the input of a first type of specific object by the viewing user, and changing the viewing performance information by a second amount of change based on the input of a second type of specific object by the viewing user. The system according to claim 1.

8. The process for changing the viewing history information involves changing a first item included in the viewing history information based on input of a first type of specific object by the viewing user, and changing a second item included in the viewing history information based on input of a second type of specific object by the viewing user. The system according to claim 1.

9. The process of changing the aforementioned viewing history information involves changing the viewing history information so that it becomes possible to identify the viewing history information to which the changes based on the input of the specific object do not apply. The system according to claim 1.

10. The process for changing the aforementioned viewing history information involves adding a predetermined amount to the aforementioned viewing history information in response to the input of the specific object. The system according to claim 1.

11. The process for changing the aforementioned viewing history information changes the aforementioned viewing history information at a specific point in time based on the input of the specific object. The system according to claim 1.

12. The one or more computer processors further execute a process to grant the specific object to the viewing user who has met the granting conditions. The system according to claim 1.

13. The aforementioned granting conditions include conditions relating to the input record of items for the aforementioned content, or conditions relating to the consumption record of a predetermined value. The system according to claim 12.

14. The one or more computer processors further perform a process to increase the value of a specific parameter in response to the input of the item to the content or the consumption of the predetermined value. The aforementioned conditions include conditions relating to the value of the specific parameter, The system according to claim 13.

15. The process of assigning the specific object involves assigning the specific object along with a decrease in the value of the specific parameter. The system according to claim 14.

16. A method for providing content distribution services, which is performed by one or more computers, A step of updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user towards the content provided by the distribution user. The process includes a step of changing the viewing history information of the viewing user based on the input of a specific object by the viewing user, separately from updates based on the viewing behavior. method.

17. A program for providing content distribution services, which can be installed on one or more computers. A process to update viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user towards the content provided by the distribution user, Based on the input of a specific object by the viewing user, a process is executed to change the viewing user's viewing history information, separate from the updates based on the viewing behavior. program.

18. A device for providing content distribution services, A means for updating viewing history information of a viewing user, which is managed in association with the distribution user or the content, based on the viewing behavior of the viewing user towards the content provided by the distribution user, The system includes means for changing the viewing history information of the viewing user, based on the input of a specific object by the viewing user, separately from updates based on the viewing behavior. Device.

Images