JP7802483B2 - Program, information processing method, and information processing device - Google Patents

Description

This disclosure relates to a program, an information processing method, an information processing device, etc.

There are services that allow users to distribute videos using live streaming, etc. (e.g., Patent Document 1 and Patent Document 2).

Japanese Patent Application Laid-Open No. 2020-21464 Japanese Patent Application Laid-Open No. 2021-120900

According to a first aspect of the present invention, a program executed by an information processing device that communicates with a terminal of a broadcaster who broadcasts live video includes: a control unit of the information processing device controlling the awarding of points to the broadcaster based on the broadcast performance of the live video; a control unit controlling the improvement of the broadcaster's level based on an increase in the points awarded to the broadcaster; a control unit controlling the reduction of the points awarded to the broadcaster when a predetermined condition is met; and a control unit controlling the reduction of the broadcaster's level based on the reduction in the points awarded to the broadcaster.
According to a second aspect of the present invention, an information processing method of an information processing device that communicates with a terminal of a broadcaster who broadcasts live video includes: controlling, by a control unit of the information processing device, to award points to the broadcaster based on the broadcasting performance of the live video; controlling, by the control unit, to improve the level of the broadcaster based on an increase in the points awarded to the broadcaster; controlling, by the control unit, to reduce the points awarded to the broadcaster when a predetermined period of time has elapsed; and controlling, by the control unit, to lower the level of the broadcaster based on the decrease in the points awarded to the broadcaster.
According to a third aspect of the present invention, an information processing device that communicates with a terminal of a broadcaster who broadcasts live video includes a control unit that performs the following controls: granting points to the broadcaster based on the broadcasting performance of the live video; improving the broadcaster's level based on an increase in the points granted to the broadcaster; reducing the points granted to the broadcaster after a predetermined period of time has elapsed; and lowering the broadcaster's level based on a decrease in the points granted to the broadcaster.
According to a fourth aspect of the present invention, an information processing device that communicates with a terminal of a broadcaster who broadcasts live video includes a processor that reads a program stored in a memory and executes processing based on the program, and the processor performs the following controls: controlling the awarding of points to the broadcaster based on the broadcaster's performance in broadcasting the live video; controlling the upgrading of the broadcaster's level based on an increase in the points awarded to the broadcaster; controlling the decrement of the points awarded to the broadcaster when a predetermined condition is met; and controlling the decrement of the broadcaster's level based on the decrement of the points awarded to the broadcaster.

FIG. 1 is a diagram showing an example of a system configuration of a communication system according to an embodiment. FIG. 3 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. FIG. 3 is a diagram showing an example of the data configuration of account registration data according to the first embodiment. FIG. 3 is a diagram showing an example of the data configuration of an account management database according to the first embodiment. FIG. 3 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. 4 is a flowchart showing an example of the flow of processing executed by each device according to the first embodiment. 10 is a flowchart showing an example of the flow of a live viewing process according to the first embodiment. FIG. 10 is a diagram showing an example of a table for explaining user levels and a method for determining whether a user level has been increased according to the first embodiment. 10 is a flowchart showing an example of the flow of a live distribution process according to the first embodiment. FIG. 10 is a diagram showing an example of a table for explaining a live streamer level and a method for determining whether a live streamer level has increased according to the first embodiment. FIG. 10 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second embodiment. 10 is a flowchart showing an example of the flow of processing executed by each device according to the second embodiment. A figure showing an example of a table for explaining a method for determining season level rewards and the next season's liver level in the second embodiment. FIG. 11 is a diagram showing an example of a table for explaining a method for determining a season ranking reward from among season results according to the second embodiment. A figure showing an example of a table for explaining a method for determining season level rewards and liver levels for the next season in accordance with the second modified example. FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. 11 is a flowchart showing an example of the flow of processing executed by each device according to the third embodiment. A figure showing an example of a table for explaining a method for calculating a livery bonus in the third embodiment. FIG. 10 is a diagram showing an example of a table for explaining a display mode of an icon related to a user according to another embodiment.

<Compliance with legal matters>
It should be noted that the disclosures set forth herein are subject to compliance with the laws of the country of implementation, such as communications privacy, as required for the implementation of the disclosures.

<Embodiment>
In this specification, for ease of understanding, there are places where the phrase "by way of example and not limitation" is used, but please note that not only those places but also the entire embodiment described below are not limited to the contents of that description.

Embodiments for implementing the programs and the like related to this disclosure will be described with reference to the drawings.

A system may be, by way of example and not limitation, comprised of multiple devices.
The plurality of devices may be a combination of devices of the same type, a combination of devices of different types, or a combination of devices of the same type and devices of different types.
Note that a system can be thought of as, for example and not as a limitation, a plurality of devices working together to perform some kind of processing.

Furthermore, a system relating to a client (client device) and a server can be considered to be, by way of example and not limitation, at least one of the following:
(1) Terminal & Server (2) Server (3) Terminal

(1) is, by way of example and not limitation, a system that includes at least one terminal and at least one server. One example of this is a client-server system.

The server may be configured, by way of example and not limitation, with the following devices, which may be a single device or a combination of multiple devices:

Specifically, the server is configured to have at least one processor (for example, but not limited to, a CPU: Central Processing Unit, a GPU: Graphics Processing Unit, an APU: Accelerated Processing Unit, a DSP: Digital Signal Processor (for example, but not limited to, an ASIC: Application Specific Integrated Circuit, an FPGA: Field Programmable Gate Array), etc.), a computer device (processor + memory), a control device, an arithmetic device, a processing device, etc., and may be configured to have multiple of the same type of device (for example, but not limited to, a CPU + CPU, a homogeneous multi-core processor, etc.), or multiple of different types of device (for example, but not limited to, a CPU + DSP, a heterogeneous multi-core processor, etc.), or may be a combination of multiple devices (for example, but not limited to, a processor + computer device, a processor + arithmetic device, a heterogeneous combination of multiple devices, etc.).
The processor may be a virtual processor.

Furthermore, when a server performs some processing, if the server is configured with a single device, the processing described in the embodiments is performed by the single device. Furthermore, if the server is configured with multiple devices, some processing may be performed by one device, and other processing may be performed by another device. For example, and not by way of limitation, if the server is configured with a processor and an arithmetic device, the processor may perform a first processing, and the arithmetic device may perform a second processing.
Furthermore, when a plurality of devices are used, the devices may be located at positions physically separated from one another.

Furthermore, the server functions may be provided in the form of PaaS, IaaS, or SaaS in cloud computing, for example and without limitation.

Furthermore, the system control unit can be at least one of the terminal control unit and the server control unit. In other words, by way of example and not limitation, the system control unit can be any of the following: (1A) only the terminal control unit, (1B) only the server control unit, or (1C) both the terminal control unit and the server control unit.

In addition, the control and processing (hereinafter collectively referred to as "control, etc.") performed by the control unit of the system may be performed by (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server.
In addition, in (1C), as an example and not a limitation, some of the controls performed by the control unit of the system may be performed by the control unit of the terminal, and the remaining controls may be performed by the control unit of the server. In this case, the allocation (allocation) of the controls may be equal or may be allocated in different proportions.

Furthermore, when referring to the communication unit of a server, if the server is configured with a single device, it may refer to the communication unit itself that the single device has, or if the server is configured with multiple devices, it may be configured to include each communication unit that each device has.
As an example and not by way of limitation, if a server comprises a first device and a second device, the first device having a first communication unit and the second device having a second communication unit, the communication unit of the server may be conceptualized as including the first communication unit and the second communication unit.

(2) By way of example and not limitation, it can be a system consisting of multiple servers (hereinafter referred to as a "server system"). In this case, the configuration of each server can be similarly applied as described above.

The control etc. performed by the server system may be performed by only one of the multiple servers (2A), by only the other servers (2B), or by both the one server and the other servers (2C).
In addition, in (2C), as an example and not a limitation, one server may perform some of the control, etc., performed by the server system, and another server may perform the remaining control, etc. In this case, the allocation (allocation) of the control, etc. may be equal or may be allocated in different proportions.

(3) By way of example and not limitation, the system may be comprised of multiple terminals.
The system may be, by way of example and not limitation, a system such as the following:
A system that gives server functions to terminals (distributed system). This can be realized using blockchain technology, for example, but not limited to.
A system in which terminals communicate wirelessly with each other. This can be realized, for example and without limitation, by communicating in a P2P (peer-to-peer) manner using short-range wireless communication technology such as Bluetooth (registered trademark).

Note that the above applies not only to the control unit, but also to each functional unit that may be a component of the system, such as the input/output unit, communication unit, memory unit, clock unit, etc.

In the following embodiment, a system including a terminal and a server (a client-server system) is illustrated as an example and not as a limitation.
It is also possible to apply the server system described in (2) above as the server.

Furthermore, instead of a system including a terminal and a server, a system not including a server, such as the system (3) above, can also be applied, but is not limited to this.
In this case, the embodiment can be configured based on the above-mentioned blockchain technology. Specifically, by way of example and not limitation, data stored and managed in a server described in the following embodiment is stored on the blockchain. Then, a terminal can generate a transaction to the blockchain, and when the transaction is approved on the blockchain, the data stored on the blockchain can be updated.

It should be noted that even when the term "terminal" is used, this is not limited to the meaning of a terminal as a client device in a client server.
That is, a terminal may include the concept of a device that is not in a client-server context.

Furthermore, throughout this specification, the expression "through a communication I/F" is used where appropriate. This is not intended to be limiting, but may also mean, by way of example, that a device sends and receives various types of information and data through a communication I/F (through a communication unit) based on the control of a control unit (e.g., a processor).

Furthermore, in this specification, when the terms "related to" or "associated with" are used, such as "B related to A" or "B related to A," this may mean, by way of example and not limitation, that "B" has some kind of relationship with "A." Specific examples of this will be given later.

Furthermore, in this specification, when a device performs processing on two or more objects, such as "sending A and B" or "receiving A and B," this may include performing "A" and "B" at the same time (hereinafter referred to as "simultaneous"), and performing "A" and "B" at different times (hereinafter referred to as "non-simultaneous").
As an example and not a limitation, when referring to transmitting first information and second information, this may include both concepts of transmitting the first information and the second information at the same time, and transmitting the first information and the second information at different times.
In addition, taking into account the lag (time lag), "simultaneous" may include "almost simultaneously."

Note that even though "A" and "B" are performed at different times, this only needs to be done with "A" and "B" as the processing targets, and the purposes do not necessarily have to be the same.
As an example and not a limitation, when the first information and the second information are transmitted as described above, it is sufficient to transmit the first information and the second information, and this may include cases where the first information and the second information are transmitted for the same purpose, as well as cases where the first information and the second information are transmitted for different purposes.

An example of a service that allows users to chat (hereinafter referred to as a "chat service") is a messaging service.
Furthermore, an application for realizing a chat service is called a "chat application," and an application for realizing a messaging service is called a "messaging application."
By way of example and not limitation, a chat application may allow users to chat in chat rooms. Also, by way of example and not limitation, a chat application may or may not allow users to make calls (such as voice calls or video calls) to each other.

Messaging services (MS) (including instant messaging services (IMS)) can also be considered a form of social networking services (SNS). Therefore, a distinction may or may not be made between messaging services and social networking services. In other words, messaging services may be included in social networking services.

In addition, in the following embodiments, as an example of a messaging service, an instant messaging service (IMS) that sends and receives content in the form of simple messages between multiple devices (terminals, for example, but not limited to) via a server is exemplified.
By way of example and not limitation, an instant messaging application may allow users to talk in talk rooms, and may or may not allow users to make calls (such as voice calls or video calls) to each other, by way of example and not limitation.

A chat room (for example, but not limited to, a talk room) can be a UI (User Interface) or GUI (Graphical User Interface) that allows each user to view content sent and received between the terminals of multiple users.

In addition, chat rooms can include one-on-one user chat rooms (hereinafter referred to as "one-on-one chat rooms"), group chat rooms including multiple users (hereinafter referred to as "group chat rooms"), and chat rooms with official account users (hereinafter referred to as "OA chat rooms").

In terms of data management, one-to-one chat rooms may be managed as chat rooms for one user or one account, or as chat rooms for a group consisting of two users or two accounts.

An official account is an account of a business operator (an account of a business operator's user), not an account of a general user, and users of this official account can, for example and without limitation, use a device similar to that of a general user to send and receive content (messages) with other devices via the server.

In this specification, content may refer to information transmitted from a source to a destination. Content may also refer to one or more pieces of content.

The content may include, by way of example and not limitation, text content in text format, image content in image format (including at least one of still images and moving images), and sound content in sound format (including voice).
In addition, the content may also include operational content such as buttons and icons for user operation, and link content such as link information (including, but not limited to, URIs (Uniform Resource Identifiers)).

The text may include, by way of example and not limitation, at least one of national characters, extended characters, machine-dependent characters, numbers, symbols, graphics, and codes, all of which are represented by character codes.
The text does not have to include at least one of the above characters, extended characters, machine-dependent characters, numbers, symbols, figures, and signs, and may include other text.

The image may include, by way of example and not limitation, at least one of various types of image information, such as icons, buttons, stamps, emojis, and banner images.

In the following embodiments, a live streaming service is used as an example of a service that allows users to live stream live content such as video images and audio, and to view live streamed content. An application for realizing the live streaming service is referred to as a "live streaming application." The live streaming application is illustrated as a "Live Streaming App."

As a form for realizing a live streaming service, any of the following forms can be applied, by way of example and not limitation.
(A) A form in which a live streaming application is configured as a standalone application. (B) A form in which the live streaming service function is provided as one function of a messaging application. (C) A form in which an application (integrated application) having the functions of a live streaming service and a messaging service is configured. (D) A form in which a messaging application is configured as an application separate from the live streaming application.

In the embodiments (B) and (C), by way of example and not limitation, the live streaming service provider may be the same as the messaging service provider.
In this case, one method is to use a common account for the user's account in the messaging application and the user's account in the live distribution application.
In this case, as another method, the user's account in the messaging application and the user's account in the live distribution application can be automatically associated (linked).

In form (D), by way of example and not limitation, the live streaming service provider may be a different provider from the messaging service provider.
In addition, in the form (D), a process of associating a user's account in the messaging application with a user's account in the live distribution application (a linking process) can be performed.

In addition, unlike the above, it is also possible to have messaging service functionality as one of the functions of a live streaming application.

Furthermore, in this embodiment, expressions such as "information is transmitted and received between users" and "information is transmitted and received between terminals" may be used, but these may be considered to be essentially synonymous.
Furthermore, when a client-server system is applied, it is possible to configure the system so that information is transmitted and received between terminals via a server, but this may also be expressed as transmission and reception of information between users or terminals. Also, as mentioned above, information may be transmitted and received between terminals without applying a client-server system.

In the following embodiments, a live streaming example will be described in which a broadcaster (liver) broadcasts live video and a viewer watches the live video. The live streaming of live content may be simply referred to as "live streaming." A user who broadcasts live content may be referred to as a "liver," and a user who watches the broadcasted live content may be referred to as a "viewer."
In the following embodiments, live content may be simply referred to as "live."

Furthermore, any of the above-mentioned forms (A) to (D) may be applied as a form for realizing a live streaming service, but the following embodiment will mainly illustrate, by way of example and not limitation, the application of form (A) in which a live streaming application is configured as a standalone application.

First Example
The first embodiment relates to granting experience points to live streamers and viewers, and leveling up the live streamers and viewers. In this embodiment, by way of example and not limitation, the granting of experience points and leveling up are performed in real time during live streaming.

The contents described in the first embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<System Configuration>
FIG. 1A is a diagram illustrating an example of a system configuration of a communication system 1 according to an embodiment of the present disclosure.
In the communication system 1, for example and not by way of limitation, a server 10 and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) are connected via a network 30.

The server 10 has a function of providing predetermined services (for example, but not limited to, a live streaming service, a messaging service, etc.) to the terminal 20 owned by the user via the network 30. For example, but not limited to, the server 10 can also be expressed as a live streaming server, a messaging server, etc.
In this embodiment, a live streaming service provider (operator) and a messaging service provider (operator) are assumed to be users of the server 10.

Note that there is no limit to the number of servers 10 or terminals 20 connected to the network 30.

Terminal 20 (terminal 20A, terminal 20B, terminal 20C, etc.) may be any information processing terminal capable of implementing the functions described in each embodiment. Examples of terminal 20 include, but are not limited to, smartphones, mobile phones (feature phones), computers (including, but not limited to, desktops, laptops, tablets, etc.), media computer platforms (including, but not limited to, cable and satellite set-top boxes, digital video recorders), handheld computer devices (including, but not limited to, personal digital assistants (PDAs), email clients, etc.), wearable devices (glasses-type devices, watch-type devices, etc.), virtual reality (VR) terminals, smart speakers (voice recognition devices), or other types of computers or communication platforms. Terminal 20 may also be referred to as an information processing terminal.

For example, the configurations of terminals 20A, 20B, and 20C may be the same, but are not limited to these. Furthermore, as needed, the terminal used by user X may be referred to as terminal 20X, and user information in a predetermined service associated with user X or terminal 20X may or may not be referred to as user information X.
The user information is information of a user associated with an account used by the user in a predetermined service. The user information includes, but is not limited to, information associated with a user, such as the user's name, an icon image of the user, the user's age, the user's gender, the user's address, the user's hobbies and interests, and a user identifier, which is input by the user or assigned by the predetermined service, and may be any one of these, or a combination thereof, or may not be the same.

The network 30 serves to connect one or more terminals 20 with one or more servers 10. In other words, the network 30 refers to a communications network that provides connection paths so that the various devices mentioned above can connect and send and receive data.

One or more portions of network 30 may or may not be a wired network or a wireless network. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth (registered trademark), satellite communications, etc., or a combination of two or more thereof. Network 30 may include one or more networks 30.

The server 10 (which is an example, but not limited to, of a server, information processing device, or information management device) has the function of providing a predetermined service to the terminal 20. The server 10 may be any information processing device capable of implementing the functions described in each embodiment. Examples of the server 10 include, but are not limited to, a server device, a computer (such as, but not limited to, a desktop, laptop, or tablet), a media computer platform (such as, but not limited to, a cable or satellite set-top box or digital video recorder), a handheld computer device (such as, but not limited to, a PDA or email client), or other types of computers or communication platforms. The server 10 may also be referred to as an information processing device. If there is no need to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not each be referred to as an information processing device.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1 will be described.

(1) HW Configuration of Terminal FIG. 1A shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not as a limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not as a limitation, the terminal 20 may or may not be configured such that individual components or multiple components are detachable.

The communication I/F 22 sends and receives various data via the network 30. Communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication is possible. The communication I/F 22 has the function of communicating with various devices, such as the server 10, via the network 30. The communication I/F 22 transmits various data to various devices, such as the server 10, in accordance with instructions from the control unit 21. The communication I/F 22 also receives various data transmitted from various devices, such as the server 10, and transmits it to the control unit 21. The communication I/F 22 may also be simply referred to as a communication unit. Furthermore, if the communication I/F 22 is configured as a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20, a device for outputting the results of processing performed by the terminal 20, etc. The input/output unit 23 may be an integrated input unit and output unit, or the input unit and output unit may be separate, or it may not be the same.

The input unit is realized by any one or combination of devices of any type that can accept input from a user and transmit information related to the input to the control unit 21. Examples of input units include, but are not limited to, hardware keys such as a touch panel, touch display, and keyboard, pointing devices such as a mouse, a camera (for inputting operations via moving images), and a microphone (for inputting operations via voice).

The output unit may be any one of or a combination of any type of device capable of outputting the results of processing performed by the control unit 21. Examples of output units include, but are not limited to, touch panels, touch displays, speakers (audio output), lenses (for example, but not limited to, 3D (three dimensions) output and hologram output), printers, etc.

By way of example only, the input/output unit 23 includes, but is not limited to, a display unit 24, a sound input unit 25, a sound output unit 26, and an imaging unit 27.

The display unit 24 is realized by any one of or a combination of any type of device capable of displaying according to the display data written to the frame buffer. Examples of the display unit 24 include, but are not limited to, touch panels, touch displays, monitors (such as, but not limited to, liquid crystal displays and organic electroluminescence displays (ELDs)), head-mounted displays (HDMs), projection mapping, holograms, and devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

The sound input unit 25 is used to input sound data (including voice data; the same applies below). The sound input unit 25 includes a microphone and the like.
The sound output unit 26 is used to output sound data and includes a speaker and the like.
The imaging unit 27 is used to acquire image data (including still image data and moving image data; the same applies below). The imaging unit 27 includes a camera and the like.

If the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged facing each other and have approximately the same size and shape.

The clock unit 29A is a built-in clock of the terminal 20 and outputs time information (timekeeping information). The clock unit 29A is configured, for example and without limitation, with a clock that uses a quartz oscillator. The clock unit 29A can also be referred to, for example and without limitation, as a timekeeping unit or a time information detection unit.

Note that the clock unit 29A may or may not have a clock that conforms to the NITZ (Network Identity and Time Zone) standard or the like.

The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter referred to as "position calculation information") necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, for example and without limitation.

The position calculation information detection unit 29B includes, but is not limited to, a satellite positioning sensor (satellite positioning unit), which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System), an inertial measurement sensor (inertial measurement unit (IMU)), which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, a UWB positioning sensor (UWB positioning unit), which is a sensor or unit for calculating the position of the terminal 20 using UWB (Ultra Wide Band), and so forth.

The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts RF (Radio Frequency) signals, including positioning satellite signals transmitted from positioning satellites and received by an antenna (not shown), into digital signals, and a baseband processing circuit that performs correlation calculations on the digital signals output from the RF receiving circuit to capture the positioning satellite signals, and outputs information such as satellite orbit data and time data extracted from the positioning satellite signals as information for position calculation.

The inertial measurement unit has an inertial sensor that detects information necessary to calculate the position of the terminal 20 using inertial navigation calculations. Examples of inertial sensors include, but are not limited to, a three-axis acceleration sensor and a three-axis gyro sensor, and output the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as information for position calculation.

The UWB positioning unit includes, by way of example and not limitation, an ultra-wideband RF (Radio Frequency) receiving circuit that converts an ultra-wideband RF signal, including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon and received by an antenna (not shown), into a digital signal, and a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the ultra-wideband RF receiving circuit.
By way of example and not limitation, the UWB positioning unit may or may not cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including an ultra-wideband pulse signal for positioning from an antenna not shown.

By way of example and not limitation, the control unit 21 calculates the position of its own terminal 20 at regular intervals or specific intervals based on the position calculation information detected by the position calculation information detection unit 29B. The terminal position is referred to as the "terminal position," and the calculated terminal position is referred to as the "calculated terminal position." The control unit 21 may, but need not, associate the calculated terminal position with the date and time when the calculated terminal position was calculated and store it in the storage unit 28 as calculated terminal position history data.

The control unit 21 has circuits physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example and without limitation, by a data processing device built into hardware. As such, the control unit 21 may or may not be described as a control circuit.

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), or a field programmable gate array (FPGA).

The storage unit 28 has the function of storing various programs and data required for the operation of the terminal 20. The storage unit 28 includes, but is not limited to, various storage media such as a hard disk drive (HDD), a solid state drive (SSD), flash memory, random access memory (RAM), and read-only memory (ROM). Furthermore, the storage unit 28 may or may not be referred to as memory.

The terminal 20 stores the program P in the memory unit 28, and by executing this program P, the control unit 21 executes the processing of each unit included in the control unit 21. In other words, the program P stored in the memory unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

(2) HW Configuration of Server FIG. 1A shows an example of the HW configuration of the server 10. As shown in FIG.
The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I/F 14 (interface), an input/output unit 12, and a clock unit 19. The components of the HW of the server 10 are connected to each other via a bus B, for example and not as a limitation. Note that the HW of the server 10 does not necessarily have to include all components as a configuration of the HW of the server 10. For example and not as a limitation, the HW of the server 10 may or may not be configured such that individual components or multiple components are removable.

The control unit 11 has circuits physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example but not limited to, by a data processing device built into hardware.

The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, processor core, multiprocessor, ASIC, or FPGA, or may not be one of these. In this disclosure, the control unit 11 is not limited to these.

The storage unit 15 has the function of storing various programs and data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as an HDD, SSD, or flash memory. However, in this disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be referred to as memory.

The communication I/F 14 sends and receives various data via the network 30. Communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication is possible. The communication I/F 14 has the function of communicating with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 in accordance with instructions from the control unit 11. The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I/F 14 may also be simply referred to as a communication unit. If the communication I/F 14 is configured as a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 12 includes a device for inputting various operations to the server 10, a device for outputting the results of processing performed by the server 10, etc. The input/output unit 12 may be an integrated input unit and output unit, or may be separate input and output units, or may not be so.

The input unit is realized by any one or combination of devices of any type that can accept input from a user and transmit information related to the input to the control unit 11. The input unit is typically realized by hardware keys such as a keyboard, or a pointing device such as a mouse. Note that the input unit may or may not include, for example and without limitation, a touch panel, a camera (for inputting operations via video images), or a microphone (for inputting operations via voice).

The output unit may be any one or a combination of any type of device capable of outputting the results of processing performed by the control unit 11. Examples of output units include, but are not limited to, touch panels, touch displays, speakers (sound output), lenses (for example, but not limited to, 3D (three dimensions) output and hologram output), printers, etc.

By way of example only, the input/output unit 12 includes a display unit 13, by way of example and not limitation.

The display unit 13 is realized by a display or the like. The display is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)). The display may or may not be a head-mounted display (HDM) or the like. These displays may or may not be capable of displaying display data in 3D. In the present disclosure, displays are not limited to these.

The clock unit 19 is a built-in clock of the server 10 and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example and without limitation, a real time clock (RTC) as a hardware clock, a system clock, etc. The clock unit 19 can also be expressed as a timekeeping unit or a time information detection unit, for example and without limitation.
(3) Others The server 10 stores the program P in the storage unit 15, and by executing this program P, the control unit 11 executes the processes of each unit included in the control unit 11. In other words, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module.
The same applies to other devices.

In each embodiment of the present disclosure, the CPU of the terminal 20 and/or server 10 is described as executing the program P to achieve this.

The control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may, or may not, implement each process not only by a CPU with a control circuit, but also by a logic circuit (hardware) formed on an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), or a dedicated circuit. These circuits may, or may not, be implemented by one or more integrated circuits, and the multiple processes shown in each embodiment may, or may not, be implemented by a single integrated circuit. LSIs are also sometimes referred to as VLSIs, super LSIs, ultra LSIs, etc., depending on the level of integration. Therefore, the control unit 21 may, or may not, be referred to as a control circuit.

Furthermore, the program P (which may be, for example and not by way of limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may or may not be provided in a state stored on a computer-readable storage medium. The storage medium may store the program P on a "non-transitory tangible medium." Furthermore, the program P may or may not be intended to realize part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called differential file (differential program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded on a storage medium.

Furthermore, when referring to a system program (a program executed by a system), the system is as described above. The aforementioned system program is a program that can be executed by the entire system, and this program may be composed of individual programs for the devices that make up the system, for example and without limitation, and the programs stored in the individual devices that make up the system may be different from each other. In other words, it is not necessary for the programs to be common to the individual devices that make up the system.
As a non-limiting example, if a system is composed of a terminal and a server, and the system program is P1, then the system program P1 may be composed of a program P2 stored on the terminal and a program P3 stored on the server, and P2 and P3 may be different programs for executing the system program. As a non-limiting example, the program P2 stored on the terminal may be a program that executes a first process and transmits the results of the first process to the server, and the program P3 stored on the server may be a program that executes a second process on the received results of the first process and transmits the results of the second process to the terminal.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) (such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application-specific IC (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy diskette, a floppy disk drive (FDD), a magnetic tape, a solid-state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more thereof. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate. Note that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. Furthermore, the storage medium may or may not be referred to as memory.

The server 10 and/or terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading the program P stored on the storage medium and executing the read program P.

Furthermore, the program P of the present disclosure may or may not be provided to the server 10 and/or terminal 20 via any transmission medium capable of transmitting a program (such as a communications network or broadcast waves). By way of example and not limitation, the server 10 and/or terminal 20 executes the program P downloaded via the Internet or the like to realize the functions of the multiple functional units shown in each embodiment.

In addition, each embodiment of the present disclosure may be realized in the form of a data signal in which the program P is embodied by electronic transmission.
At least a part of the processing in the server 10 and/or the terminal 20 may or may not be realized by cloud computing configured by one or more computers.
At least a part or all of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part or all of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least a part or all of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part or all of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.

Unless explicitly stated, the determination configuration in the embodiments of the present disclosure is not essential, and a predetermined process may or may not be performed when the determination condition is met, or when the determination condition is not met.

The programs disclosed herein may be implemented using, for example and without limitation, scripting languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), and markup languages such as HTML Living Standard.

<Functional configuration>
(1) Functional Configuration of the Server FIG. 1B is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment.
The control unit 11 includes, as a functional unit, an application management processing unit 111 for executing application management processing in accordance with an application management processing program 151 stored in the storage unit 15, for example and not by way of limitation.

FIG. 1C is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment.
The storage unit 15 stores, by way of example and not limitation, an application management processing program 151 executed by the control unit 11 as application management processing, account registration data 153, and an account management database 155.

The account registration data 153 is registration data related to an account of an application (for example, but not limited to, a live distribution application), and an example of the data configuration is shown in FIG. 1-4.
In the account registration data 153, for example, but not by way of limitation, a user name, an application ID, and other registration information are stored in association with each other.

The user name is the name of the account of the terminal 20 that uses this application; by way of example and not limitation, the name registered by the user of the terminal 20 when using the application is stored.

The application ID is information used to identify an application account, or the account itself.
This application ID is preferably a value that is unique for each account, and as a non-limiting example, a unique value (proper value) is set and stored by the server 10 for each account.
The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information about the terminal or information about the user of the terminal.

Other registration information may include, but is not limited to, various types of information such as identification information for identifying the terminal 20, the telephone number (terminal telephone number) of the terminal 20, an email address (terminal email address), and authentication information such as passwords (login password, authentication password, etc.) used for various authentications in the application.

The identification information for identifying the terminal 20 may be, for example and not by way of limitation, a terminal ID (for example and not by way of limitation, an IMEI (International Mobile Equipment Identity)).
Furthermore, the identification information for identifying the user of the terminal 20 may be, for example and without limitation, an application ID for a general user or an application ID for an official user.

The application ID may or may not be replaced by a "user ID."
Furthermore, for an application that allows only one account to be registered per terminal 20, as an example and not a limitation, the following can be used: "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID."

Furthermore, by way of example and not limitation, it may or may not be possible to assign multiple terminal IDs to one application ID. In this case, it may or may not be possible to run applications in parallel (in parallel) on multiple terminals 20 using one application ID as the identification (login) target.

Furthermore, instead of various IDs such as application IDs, it is also possible to apply a method of managing accounts using information such as terminal telephone numbers.
In this case, instead of storing ID information such as an application ID in the account registration data 153, information such as a terminal telephone number can be stored in the account registration data 153. It is also possible to have ID information such as an application ID correspond one-to-one with information such as a terminal telephone number, without replacing ID information such as an application ID with information such as a terminal telephone number, but this is not necessary.

In the following various embodiments, for the sake of simplicity, it is assumed that one account is registered for one terminal 20.
Furthermore, in this case, as described above, "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID," so the term "user of the account" can be considered to be essentially synonymous with "terminal of the account."

Users who can register an account can be, by way of example and not limitation, general users (general users), and users (official users) who are expected to act as professional live streamers using so-called official accounts (official accounts), such as celebrities, can be excluded.
Official users may also be allowed to register accounts, but as a non-limiting example, the rules described in the following embodiment may not be applied to official users.

The account management database 155 is a database for managing information about the accounts stored in the account registration data 153, and an example of its data structure is shown in FIG.
The account management database 155 stores account management data as data for each account.

Each account management data may store, by way of example and not limitation, an application ID, user experience value, user level, live streamer experience value, and live streamer level.

The application ID is the application ID stored and registered in the account registration data 153.

The user experience value can be the user experience value granted by the server 10 to the user of this application ID. Details will be described later.

The user level is a level based on the user experience of the user of this application ID, and by way of example and not limitation, can be stored and updated by the server 10 based on the user experience. Details will be provided below.

By way of example and not limitation, the live streamer experience points can be the live streamer experience points granted by the server 10 to the user of this application ID. Details will be provided below.

The liver level is a level based on the liver experience value of the user of this application ID, and can be, for example and without limitation, a comprehensive list of the liver rank, which is the rank as a liver, and the level within that liver rank (level within rank). The liver level can be, for example and without limitation, stored and updated by the server 10 based on the liver experience value. Details will be provided below.

The user experience value and the user level can be examples of information about the user.
The liver experience value and liver level can be an example of information about the liver.

By way of example and not limitation, a user who wishes to act as a live streamer in a live streaming application may register with the server 10. For unregistered users, the live streamer experience points and live streamer level in the account management data may be set to N/A (Not Applicable).

As described above, in this embodiment, information about the user and information about the live streamer are stored in association with one account (common account).
In addition, activities as both a viewer and a live streamer are carried out using a common account.

(2) Functional Configuration of Terminal FIG. 1-6 is a diagram showing an example of functions realized by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes, as a functional unit, an application processing unit 211 for executing application processing in accordance with an application processing program 281 stored in the storage unit 28, for example and not by way of limitation.

FIG. 1-7 is a diagram showing an example of data stored in the storage unit 28 of the terminal 20 in this embodiment.
The memory unit 28 stores, by way of example and not limitation, an application processing program 281 executed as application processing by the control unit 21 and an application ID 283 corresponding to the terminal 20 or the account of the user of the terminal 20.

<Display screen>
In the following, as an example and not a limitation, a case will be illustrated in which the terminal 20 is a smartphone equipped with a display unit 24 having a portrait display.

For example, but not by way of limitation, a smartphone has a touch panel that functions as an input unit and is positioned opposite the display, thereby forming a touchscreen. When an element such as an icon, button, item, or input area is displayed on the display, and a user operates a part of the touch panel that faces the area where the element is displayed, a program associated with that element or a subroutine of that program is executed.

In the following, a tap operation (sometimes simply referred to as "tap") can be, by way of example and not limitation, an action in which a user lightly taps the display unit 24 (touch screen) that is integrally configured with a touch panel with a finger or the tip of a pen, and then releases the touch.
Furthermore, the scrolling operation may be, for example and without limitation, an operation (motion) for scrolling displayed information. For example and without limitation, the scrolling operation may be a "swipe operation" when input is made with a finger, a touch pen, or the like, and a "wheel operation" when input is made with a mouse, or the like.

Note that the display screen transitions described below are merely examples of display screen transitions for implementing the techniques of the present disclosure. In the display screen transitions illustrated below, some of the display screens may be omitted, or other display screens may be added.

Figure 1-8 shows an example of a live streaming application screen displayed on the display unit 24 of the terminal 20 in this embodiment. Here, the screen displayed on the display unit 24 of user A.A's terminal 20A is shown as an example.

The left side of Figure 1-8 is the My Page screen of the live streaming application, with the name of the live streaming application displayed at the top of the screen. Below that is an area showing the page currently being displayed within the live streaming application (hereinafter referred to as the "in-app position display area"). Since this screen is the My Page screen, it displays "My Page."

Below that is an area that displays various information about the live streaming application.

At the top of this area is a profile area related to User A.A.'s profile. By way of example and not limitation, the base image (hereinafter referred to as the "base image") set by User A.A. at the time of account registration or at some point thereafter is displayed in the profile area as User A.A.'s profile icon PI1. Also set in the profile area is a My Page background BG1, which is also set by User A.A. as a background image.

In addition to being used as a profile icon, the base image can also be used in various situations as an image to represent the user. For example, and not as a limitation, the base image can be displayed in association with a comment to make it clear that the comment is the user's own when posting it, or it can be used to display when the user or live streamer level is increased.

The base image and the background of the My Page may be changed by the user later.
Also, as a non-limiting example, the background of the My Page may be set only after registering as a live streamer.

By way of example and not limitation, an icon image of user A.A., the total number of users that user A.A. follows (hereinafter referred to as "following"), and the total number of users that follow user A.A. (hereinafter referred to as "followers") are displayed.

Also, in the upper right corner of this area, a ranking icon IC1 is displayed, which is an icon image for displaying ranking information. Rankings will be explained in a later example.

Below that, a user level information display area ULR that displays user level information of user A.A. and a live streamer level information display area LLR that displays live streamer level information of user A.A. are each formed by a frame.
In the following, the liver level is, by way of example and not limitation, assumed to include a liver rank and an in-rank level indicating the level within that liver rank.

In this example, the user level information display area ULR displays "User Lv59" as the user level of user A.A., along with an icon image of a badge (five stars) indicating that the user level is in the 50s.
In this example, the liver level information display area LLR displays an icon image of a character (rabbit character) corresponding to the liver rank "Legend" and also displays "Legend Lv10" as the liver level of user A.A.

Also, below these areas, information for watching the live broadcast is displayed.
Specifically, along with the video camera image and the words "Watch the broadcast," for example and without limitation, the icon image of the user currently broadcasting the live show and the name of the live show being broadcast are displayed in a list in the left-right direction as live broadcast information about the live show being broadcast. For example and without limitation, the user can scroll left and right to display live broadcast information that is not displayed on the screen.

Below that are buttons for displaying information about multiple functions, such as the "Stream" button for broadcasting your own live stream, the "Streaming History" button for checking your live stream history, the "Scheduled Streams" button for checking your upcoming live streams, and the "Viewing History" button for checking the history of live streams you have watched.

For example, but not by way of limitation, when the live level information display area LLR is tapped on the screen on the left side of Figure 1-8, the screen in the center of Figure 1-8 is displayed.
This screen is a live status screen showing the live status of user A.A., and the words "live status" are displayed in the in-app position display area.

Below that is an area where information about the live status is displayed.
Specifically, a display switching tab for switching between user level and live streamer rank (live streamer level) is displayed at the top, and in this example, live streamer rank is selected. With live streamer rank selected, the word "live streamer rank" on the display switching tab is highlighted (in this example, it is displayed in bold and underlined).

Based on the liver rank selection, a liver level detailed information display area LLDR is configured below it to display detailed information about user A.A's liver level. The liver level detailed information display area LLDR displays, by way of example and not limitation, a character icon image that changes depending on the liver rank (or liver rank and level within the rank), the liver level (liver rank and level within the rank), and the liver experience points (liver EXP) required to level up to the next level within the rank.

In this example, the liver rank of user A.A. is displayed as "Legend" and the level within the rank is "Lv10," and the icon image of a rabbit character is displayed as the character icon image corresponding to this liver level.

Additionally, below the display of the Liver Rank and the level within the rank, the Liver Experience Points required to level up to the next level within the rank are displayed in a gauge (Liver Experience Point Gauge LG1) and in text. In this example, it is displayed that 2,987 Liver EXP is required to level up to the next level within the rank.
In this example, by way of example and not limitation, every time the liver experience value increases by 14,000, the liver rank "Legend" increases in level.

Below the liver level detailed information display area LLDR, the liver rank is displayed in a carousel format running horizontally. In this example, the current liver rank is displayed in a bubble directly below the center of the liver level detailed information display area LLDR, and the liver rank one rank below this liver rank and the liver rank one rank above this liver rank are displayed to the left and right of the current liver rank bubble, respectively.

In this example, since user A.A.'s liver rank is "Legend," a rabbit character icon image and a speech bubble containing the words "Legend Driver" are displayed below the liver level detailed information display area LLDR. To the left of this, the next lower liver rank, "Superstar," is displayed, and to the right of this, the next higher liver rank, "God Liver," is displayed.
In addition, the icon for the next higher liver rank, "God Liver," has a lock icon attached to it, indicating that this liver rank has not yet been unlocked, and the icon is displayed in reverse.

Below that is a live streamer experience point acquisition information display area LER, which shows methods for acquiring live streamer experience points, etc. In this example, the methods for acquiring live streamer experience points are displayed, by way of example and not limitation, as follows: "Streaming time" which relates to the length of the live stream, "Number of views" which relates to the number of views of the live stream, "Support points" which relates to the support points acquired from viewers during the live stream, and "Number of pokes" which relates to the number of times the live streamer poked viewers using the poke function during the live stream.

The "poke function" refers, by way of example and not limitation, to a function that allows a live streamer to communicate with viewers by poking them during a live broadcast, for purposes such as increasing their fan base.

Specifically, in this example, it is possible to obtain "1 Liver Experience Point (Liver EXP)" per "1 minute" of streaming time, "1 Liver EXP" can be obtained for the number of views (viewing time x number of views x 0.01), "1 Liver EXP" can be obtained for cheering points (1 PT), and "1 Liver EXP" can be obtained for each "1 poke."

Furthermore, below that, information regarding the benefits granted according to User A.A.'s current liver rank is displayed. In this example, it is shown that three benefits associated with the liver rank "Legend" are granted, by way of example and not limitation: Rank Badge RB, Frame FM, and My Page Background BG. These can also be referred to as "objects (items)" that are benefits granted based on the liver level.

The rank badge RB is an example of an object, and can be used to highlight one's own rank, for example, by displaying it in association with the profile icon in the profile area of the My Page screen, but is not limited to this.

Frame FM is an example of an object, and by way of example and not limitation, it can be set as a frame surrounding a profile icon in the profile area of the My Page screen, making the profile icon stand out.

The My Page background BG is an example of an object, and by way of example and not limitation, it can be set as the background image for the profile area on the My Page screen, making the profile area stand out.

When the user level information display area ULR is tapped on the screen on the left side of Figure 1-8, or when the "User Level" display switching tab is tapped on the screen in the center of Figure 1-8, the screen on the right side of Figure 1-8 is displayed, for example and not by way of limitation.
This screen, like the screen in the center of Figure 1-8, is a live status screen showing the live status of user A. A. The words "Live Status" are displayed in the in-app position display area, and because the user level has been selected, "User Level" is highlighted (in this example, displayed in bold and underlined) in the display switching tab.

Based on the user level selection, a user level detailed information display area ULDR is configured below it to display detailed information about user A. A's user level. The user level detailed information display area ULDR displays, by way of example and not limitation, an icon image of a badge (different from the aforementioned "rank badge") serving as a user title corresponding to the user level (achieved user experience points) shown in the table in Figure 1-14, described below, as well as the user level and the user experience points (user EXP) required to level up to the next user level. Badges serving as user titles can also be considered as objects that provide benefits, similar to the rank badges described above.

In this example, "Level 59" is displayed as the user level of user A.A., and a badge icon image with the number of stars "5" (five stars) is displayed as the badge icon image corresponding to this user level. By way of example and not limitation, a badge icon image with a number of stars corresponding to the tens digit of the user level may be configured.
In addition, when a level of "100 or more" is allowed, the number of stars can be set to the same number as the first two digits, for example, but not limited to this.

Furthermore, below the user level, the user experience points required to level up to the next user level are displayed using a gauge (user experience point gauge UG1) and text. In this example, it is displayed that "67 user EXP" user experience points are required to level up to the next user level.

Below the user level detailed information display area ULDR, the user levels are displayed in a carousel format in the left-right direction, and in this example, the level band to which the current user level belongs (in this example, "Lv50 and up") is displayed in a balloon directly below the center of the user level detailed information display area ULDR. Also, in this example, a level band 20 levels below this level band (in this example, "Lv30 and up") and a level band 20 levels above this level band (in this example, "Lv70 and up") are displayed to the left and right of the balloon of the level band to which the current user level belongs.
It should be noted that the icon for the next higher level band is displayed in an unlocked manner similar to the display manner of the liver rank, by way of example and not limitation.

Below that is a user experience point acquisition information display area UER, which indicates how user experience points are acquired. In this example, the methods of acquiring user experience points are displayed, by way of example and not limitation, as follows: "Viewing time" related to the time spent watching the live stream, "Number of comments" related to the comments posted by the user during the live stream, "Support points" related to the support points sent by the user to the live stream, "Hearts" related to the hearts sent by the user to the live stream, "Sign in" related to the user's sign-in (or login) to the live streaming application, and "Subscribe" related to the channels to which the user is subscribed.

Specifically, in this example, it is shown that it is possible to obtain "1 user experience point (user EXP)" for every "10 minutes" of viewing time, "1 user experience point" for every "comment" (limited to 100 per day), and "2 user experience points" for every "1 support point." It is also shown that it is possible to obtain "1 user experience point" for every "10 hearts," "50 user experience points" for every "sign-in" (limited to once per day), and "1 user experience point" for every "subscription" to a channel.

Note that while the conditions for granting user experience points are illustrated here primarily based on behavior as a viewer (viewer behavior), as will be described in detail below, user experience points can also be granted based on behavior as a broadcaster (broadcaster behavior). For this reason, these conditions may also be displayed in the user experience point acquisition information display area UER.

1-9 is a diagram showing an example of a display screen when user A.A of terminal 20A shown on the screen of FIG. 1-8 is a viewer watching a live broadcast.
The screen on the left side of Figure 1-9 corresponds to the My Page screen on the left side of Figure 1-8, and shows a state in which "BB's Kitchen" broadcast by user B.B. is selected as the live broadcast to be viewed from among the live broadcast information. In this case, the live broadcast screen in the center of Figure 1-9 is displayed by way of example and not limitation.

On this live streaming screen, in the area below the area at the top of the screen where the name of the live streaming application is displayed, video of the live stream being streamed by user B.B. is displayed. Specifically, video of user B.B., the live streamer, is displayed.

In the upper left corner of the area where the live video is displayed, information such as the name of user B.B., the live streamer, the time elapsed since the start of the live broadcast, and the number of viewers watching the live broadcast is displayed. Also below that is an area showing user B.B.'s current live streamer level (live streamer rank and level within the rank), which is configured to display live streamer experience using a gauge (live streamer experience gauge LG2). In this example, it is shown that user B.B.'s live streamer rank is "Star" and his level within the rank is "Lv8."

In addition, a comment display area CDR is configured in the lower left corner of the area where the live video is displayed, where comments posted by viewer users and live streamer users are displayed. By way of example and not limitation, this comment display area CDR is configured to display posted comments in association with the icon image and username of that user.

Note that comments may be considered as the content described above. Furthermore, comments may be considered as one aspect of content.

By way of example and not limitation, the comment display area CDR can be configured as an area in which a set number of lines of comments (for example and not limitation, approximately 4 to 5 lines) are displayed. In this case, by way of example and not limitation, each time a comment is posted, it is displayed from the bottom, with older comments being pushed up, and comments displayed in the top line being hidden.

In addition, at the bottom of the area where the live video is displayed, there is provided a comment input area CIR for inputting comments that the user wishes to make. As a non-limiting example, when the comment input area CIR is tapped, a keyboard (not shown) is displayed at the bottom of the screen, allowing the user to input a comment using this keyboard. Then, by confirming the input comment and tapping the comment send button (not shown), the input comment can be transmitted via the server 10 to the live streamer's terminal 20 and each viewer's terminal 20.

In addition, the terminal 20 from which the comment was sent may control the display of the comment so that the comment of the user of the terminal 20 is positioned below the most recent comment in the comment display area CDR based on the tapping of the comment send button.
The server 10 also transmits the comment entered at the terminal 20 to the terminal 20 that sent the comment. Then, based on receiving the comment from the server 10, the terminal 20 that sent the comment may perform control to display the comment so that the comment of the user of its own terminal 20 is positioned below the most recent comment in the comment display region CDR.

In the screen in the center of Figure 1-9, a comment posted by user A.A. of user terminal 20A, "You'll soon be at star level 9," is displayed in the comment display area CDR. By way of example and not limitation, let us assume that upon posting this comment, user A.A. gains user experience points, which in turn increases user A.A.'s user level. In this case, by way of example and not limitation, the screen on the right side of Figure 1-9 is displayed.

On this screen, comment display area CDR displays comment CM1, which originates from user A.A. and includes the text "Your level has increased! Congratulations!" associated with user A.A.'s icon image and username, as well as an icon of the user's post-level increase user level, "User Lv. 60." Comment CM1 is different from ordinary comments based on user input, and, by way of example and not limitation, can be a comment generated by server 10 when it determines that the user's level has increased and sent to each terminal 20. In other words, this comment can be treated as a system message, so to speak.

Furthermore, comment CM1 is displayed in a different display format from other comments. In this example, the entire comment, including user A.A's icon image and username, is displayed in a frame. By displaying it in this manner, users of each terminal 20 can recognize that this comment is different from normal comments based on user input.

In the comment display area CDR, below comment CM1, a comment "Congratulations, A.A.", posted by viewer user E.E. who saw this comment, is displayed, congratulating user A.A. on her level up.

Additionally, above the comment display area CDR, user level up information UUI indicating that the user level has been increased is displayed. Specifically, in this example, the words "User Level Up!" and information indicating that the user level has been increased from "Level 59" to "Level 60" are displayed.
The user level upgrade information UUI may be displayed only on the terminal 20 of the user whose user level has been upgraded (terminal 20A in this case), or may be displayed on other terminals 20 as well.

FIG. 1-10 is a diagram showing an example of a display screen when user A.A of terminal 20A shown on the screen of FIG. 1-8 becomes a live streamer and broadcasts a live stream.
The screen on the left side of Figure 1-10 corresponds to the My Page screen on the left side of Figure 1-8, and shows the state when the "Stream" button at the bottom of the screen has been tapped. In this case, by way of example and not limitation, the live streaming screen in the center of Figure 1-10 is displayed.

On this live streaming screen, in the area below the area at the top of the screen where the name of the live streaming application is displayed, video of the live stream being streamed by user A.A. Specifically, video of user A.A., who is a live streamer, is displayed. User A.A.'s live stream level is displayed as a live streamer rank of "Legend" and a level within the rank of "Lv10."
In addition, in the upper left corner of the area where the live video is displayed, in addition to information such as the name of the live streamer, user A.A., live icon information is displayed, which is a camera icon with the word "Live" inside it, indicating that the device is currently live streaming.
Other configurations are the same as those shown in the center of Figure 1-9 and the right side of Figure 1-10.

As a result of User A.A.'s live streaming, User A.A. gains Liver Experience Points, which in turn increases User A.A.'s level within the rank. When User A.A.'s level within the rank reaches the maximum level, his or her Liver Rank is upgraded. In this case, the screen on the right side of Figure 1-10 is displayed, by way of example and not limitation.

On this screen, comment display area CDR displays comment CM2, which is a comment originating from user A.A., and includes the text "Your rank has increased! Congratulations!" associated with user A.A.'s icon image and username, as well as icons indicating the resulting liver rank of "God" and rank level of "Lv1." Similar to comment CM1 described above, comment CM2 is a different comment from a regular comment based on user input, and, by way of example and not limitation, can be a comment generated by server 10 when it determines that a liver's rank or rank level has increased and sent to each terminal 20.

Furthermore, comment CM2 is displayed in a different display format from other comments. In this example, the entire comment, including user A.A's icon image and username, is displayed in a frame. By displaying it in this manner, users of each terminal 20 can recognize that this comment is different from normal comments based on user input.

In the comment display region CDR, comments such as "God has descended!!!!!" and "A.A. is amazing!" congratulating user A.A. on his rank increase, which were sent by viewer users F.F. and E.E. who viewed this comment, are displayed below comment CM2.
Also, below that, a comment expressing gratitude, "Thanks everyone for your support," which was entered and sent by user A.A., a live streamer, in the comment input area CIR, is displayed.

Also, above the comment display area CDR, liver level up information LUI is displayed, indicating that the liver level has increased. Specifically, in this example, the text "Liver Rank Up!" and information including a character icon image and text indicating that the liver rank has increased from "Legend (Lv10)" to "God (Lv1)" are displayed. This information can also be considered information indicating that the liver rank has increased, and may therefore be referred to as liver rank up information.

Furthermore, the live streamer level-up information LUI is displayed in a more flashy manner than the user level-up information UUI shown on the screen on the right side of FIG. 1-9, by way of example and not limitation.
The liver level up information LUI may be displayed only on the terminal 20 (in this case, terminal 20A) of the user whose liver rank has been increased, or may be displayed on other terminals 20 as well.

Figure 1-11 is a diagram showing an example of a screen of a live streaming application displayed on the display unit 24 of the terminal 20A in this embodiment, and is a diagram showing an example of a screen displayed when the live streaming of Figure 1-10 has ended.
On the left and center of Figure 1-11, upon completion of the live broadcast, information is displayed about the live broadcast experience points acquired by user A.A. during the live broadcast (in this example, the message "Thank you for your hard work on the broadcast!") along with messages of appreciation for the live broadcast.

In addition, information including the Liver Experience Gauge LG1 is displayed below that. From the left side of Figure 1-11 to the center of Figure 1-11, the Liver Experience Gauge LG1 increases by the amount of Liver Experience Points acquired, indicating that User A.A.'s Liver Level has increased from "Legend (Lv10)" to "God (Lv1)." Also, on the screen in the center of Figure 1-11, below the information including the Liver Experience Gauge LG1, the details of the benefits acquired by User A.A. based on the increase in Liver Level are displayed; in this example, "Acquired Item: Rank Badge RB1 as a benefit (object) for reaching the intra-rank level "Lv1" within the Liver Rank "God"."

Furthermore, below that, information regarding the results of this live stream (streaming results) is displayed, including, but not limited to, the duration of the live stream ("Streaming Time"), the number of viewers of the live stream ("Viewers"), and the number of new followers ("New Followers").

Furthermore, below that are a "Thank you message" button for sending a thank you message to users who watched the live stream, and a "Broadcast again" button for broadcasting the live stream again.

The right side of Figure 1-11 is the My Page screen of the live distribution application, and is a diagram showing an example of the screen that is displayed when returning to My Page after the screen in the center of Figure 1-11 is displayed.
The configuration of this screen is the same as the screen on the left side of Figure 1-8, but the displayed content is partially different.

Specifically, as shown in the center screen of FIG. 1-11, the rank badge RB1 is displayed in association with the profile icon in the profile area based on the rank badge RB1 being acquired.
Furthermore, as shown in the center screen of Figure 1-11, the number of new followers increased by "102" due to the live broadcast, so "102" was added to the number of followers of "2,831" on the left screen of Figure 1-8, and the total number displayed is now "2,933."

Furthermore, as the user level has been raised to "Level 60" through the live broadcast, the user level information display area URL displays "User Level 60" as the user level of user A.A., along with an icon image of a badge (six stars) indicating that the level is in the 60s.
In addition, as a result of the live broadcast, the liver level has been raised to "God Lv1", and in addition to the icon image of the character (bear character) corresponding to the liver rank "God", the liver level information display area LLR displays "God Lv1" as the liver level of user A.A.

<Processing>
1-12 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. In this processing, the processing executed by the control unit 21 of the terminal 20A of user A.A, who is one of the viewers watching the distributed live broadcast, is shown on the left, and the processing executed by the control unit 11 of the server 10 is shown on the right.

Here, a case where user B.B. becomes a live streamer and performs live distribution will be illustrated.
Note that the process executed by the control unit 21 of the terminal 20 of a viewer other than user A is the same as that of terminal 20A, and therefore is not shown in the figure.

Note that the processes described below are merely examples of processes for realizing the method of the present disclosure, and are not limited to these.
Other steps may be added to the process described below, or some steps may be omitted (deleted) from the process described below.
The same applies to the various processes described in this specification.

First, the control unit 21 of terminal 20A determines whether or not to watch the live broadcast based on whether or not a request to watch the live broadcast has been made by user A.A via the input/output unit 23 (A110). If it is determined that the user will not watch the live broadcast (A110: NO), the control unit 21 of terminal 20A proceeds to A140.

On the other hand, if it is determined that the live broadcast will be viewed (A110: YES), the control unit 21 of terminal 20A sends live broadcast viewing request information, including, for example but not limited to, the application ID 283 of the terminal 20A, to the server 10 via the communication I/F 22 (A120).

The control unit 11 of the server 10 determines whether live viewing request information has been received from the terminal 20A via the communication I/F 14 (S110), and if it determines that it has not been received (S110: NO), the process proceeds to S130.

On the other hand, if it is determined that live viewing request information has been received (S110: YES), the control unit 11 of the server 10 executes live viewing processing with the terminal 20A (A130, S120).

Fig. 1-13 is a flowchart showing an example of the flow of the live viewing process, which should be read in the same way as Fig. 1-12.
Upon receiving live streaming information from terminal 20B of user B.B, who is a live streamer, via communication I/F 14, control unit 11 of server 10 transmits live information based on the live streaming information to terminal 20A via communication I/F 14 (S1210).

When live information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A displays the received live information on the display unit 24 (A1310).

After S1210, the control unit 11 of the server 10 performs a user experience value calculation process (S1220). Specifically, by way of example and not limitation, the user experience value of user A.A can be calculated based on at least one of the following conditions (viewer behavior, viewing record) and the assigned value (unit assigned value) of the user experience value set for each of the conditions shown in the example screen on the right side of FIG. 1-8.
(A1) While watching a live stream: Your live viewing time (A2) While watching a live stream: Number of comments you have sent (A3) While watching a live stream: Sending support points (support items) to the live streamer (A4) While watching a live stream: Sending hearts to the live streamer (A5) While watching a live stream: Following the live streamer (subscribing to the channel)
(A6) When not watching live: Sign in (or log in) to the live streaming application
(A7) When not watching live: Number of subscriptions to one's own channel However, the conditions are not limited to these, and other conditions may be included.

By way of example and not limitation, at least one of support points and hearts can be a "paid item." Furthermore, by way of example and not limitation, a live streaming service provider can impose a financial burden on a user, and by making a payment to the live streaming service provider, the user can send support points or hearts to a live streamer.

By way of example and not limitation, sending cheering points, sending hearts, subscribing to a channel, etc. may also be considered as evaluations of a live video.

Then, the control unit 11 of the server 10 updates the user experience value of the account management data corresponding to the application ID of user A.A. in the account management database 155.

Next, the control unit 11 of the server 10 makes a determination as to whether or not to increase the user level of user A.A. (hereinafter referred to as the "user level increase determination") (S1230).

FIG. 1-14 is a diagram showing an example of a table for explaining user levels and a method for determining whether a user level has been raised.
In this table, for example and not by way of limitation, user levels, achieved user experience points, and user titles are stored in association with each other.

User levels are subdivided into multiple levels, such as "LV1," "LV2," "LV3," etc., in ascending order, and the user experience points required to level up to each user level are associated with each user level and set as "achieved user experience points."

In addition, in this example, titles corresponding to some of the user levels (hereinafter referred to as "user titles") are set for those user levels. Specifically, by way of example and not limitation, the user title "Bronze Listener Badge" is set for user level "LV3," the user title "Bronze Listener Frame" is set for user level "LV7," and the user title "Silver Listener Badge" is set for user level "LV10."

At S1230, the control unit 11 of the server 10 determines whether to raise the user level of user A.A. from the current user level based on the latest user experience value of user A.A. and the achieved user experience value in the table of FIG. 1-14 (S1230). In other words, in this embodiment, during live streaming, viewers of the live stream may be granted user experience points, which may raise their user level.

If it is determined that the level should not be increased (S1230: NO), the control unit 11 of the server 10 advances the process to S1250.
On the other hand, if it is determined that the level should be increased (S1230: YES), the control unit 11 of the server 10 updates the user level of the account management data corresponding to the application ID of user A. A in the account management database 155. Then, the control unit 11 of the server 10 transmits information relating to the increase in the user level (for example, but not limited to, information that the user level has been increased, the user level, the user title, etc.) as user level increase information to the terminal 20A via the communication I/F 14 (S1240).

The control unit 11 of the server 10 may or may not transmit user level-up information to the terminal 20 of each viewer.
In addition, as user level up information, user level up comment information to be displayed within the comments being distributed may be sent to each viewer/distributor terminal 20, and the user level up information may be sent only to terminal 20A.

After A1310, the control unit 21 of terminal 20A determines whether user level-up information has been received from the server 10 via the communication I/F 22 (A1320), and if it determines that it has not been received (A1320: NO), the process proceeds to A1340.

On the other hand, if it is determined that user level upgrade information has been received (A1320: YES), the control unit 21 of terminal 20A displays the received user level upgrade information on the display unit 24 (A1330).

After S1240, the control unit 11 of the server 10 determines whether or not live streaming end request information has been received from the terminal 20B via the communication I/F 14 (S1250), and if it determines that it has not been received (S1250: NO), returns the processing to S1210.
On the other hand, if it is determined that the live distribution end information has been received (S1250: YES), the control unit 11 of the server 10 transmits the live distribution end information to the terminal 20A via the communication I/F 14 (S1260).
Then, the control unit 11 of the server 10 ends the live viewing process.

After A1330, the control unit 21 of the terminal 20A determines whether or not live streaming end information has been received from the server 10 via the communication I/F 22 (A1340), and if it determines that it has not been received (S1340: NO), returns processing to A1310.
On the other hand, if it is determined that the live distribution end information has been received (A1340: YES), the control unit 21 of the terminal 20A causes the display unit 24 to display the received live distribution end information (A1350). Then, the control unit 21 of the terminal 20A ends the live viewing process.

In A1350, the control unit 21 of terminal 20A may, for example and not by way of limitation, display information regarding the user experience points and user level acquired in relation to the viewed live show. As an example and not by way of limitation, the control unit 21 may display changes in the user experience points and user level acquired by user A.A through viewing the live show, similar to the live streaming end information displayed on the display unit 24 of the live streamer's terminal 20 shown in FIG. 1-11.

Returning to FIG. 1-12, after performing the live viewing process (A130), the control unit 21 of terminal 20A determines whether to perform live streaming (A140) based on whether user A.A. has made an input for performing live streaming via the input/output unit 23. If it is determined that live streaming will not be performed (A140: NO), the control unit 21 of terminal 20A proceeds to A170.

On the other hand, if it is determined that live streaming is to be performed (A140: YES), the control unit 21 of terminal 20A sends live streaming request information to the server 10 via the communication I/F 22 (A150).

After performing the live viewing process (S120), the control unit 11 of the server 10 determines whether live streaming request information has been received from the terminal 20A via the communication I/F 14 (S130), and if it determines that it has not been received (S130: NO), the process proceeds to S150.

On the other hand, if it is determined that live streaming request information has been received (S130: YES), the control unit 11 of the server 10 performs live streaming processing with the terminal 20A (A160, S140).

Fig. 1-15 is a flowchart showing an example of the flow of live distribution processing. The diagram should be read in the same way as Fig. 1-12.
The control unit 21 of the terminal 20A transmits the live distribution information to the server 10 via the communication I/F 22 (A1610).

When live streaming information is received from terminal 20A via communication I/F 14, the control unit 11 of the server 10 transmits live information based on the received live streaming information to terminal 20A and each viewer's terminal 20 via communication I/F 14 (S1410).

When the live information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received live information (A1620).
Although not shown in the figure, each viewer's terminal 20 displays the received live information on the display unit 24 .

After S1420, the control unit 11 of the server 10 performs a user experience value calculation process (S1420).
Here, user A.A. is a live streamer who is performing live distribution, but as a non-limiting example, not only can live streamer experience points be assigned to user A.A., but user experience points can also be assigned to user A.A.

In this case, by way of example and not limitation, the user experience value of user A.A can be calculated based on at least one of the following conditions (distribution history, distributor behavior) and the assigned value (unit assigned value) of the user experience value set for each:
(B1) During live streaming: the duration of the live streaming that you are streaming (B2) During live streaming: the number of support points you have received (B3) During live streaming: the number of hearts you have received (B4) During live streaming: the number of viewers of your live stream (B5) During live streaming: the number of comments you have made However, the conditions are not limited to these, and other conditions may also be included.

As just one example, the user experience points awarded based on conditions (B1) to (B5) above, for example and not limitation, can be set to be relatively smaller than the user experience points awarded based on conditions (A1) to (A7) above. In other words, the user experience points (user level) can be increased more easily by performing viewer behavior than by performing broadcaster behavior (viewer behavior is stronger than broadcaster behavior).

As an example and not a limitation, conditions not included in the above conditions may be applied among the conditions used in the liver experience value calculation process described below. Also, the exact same conditions as those used in the liver experience value calculation process described below may be applied.

Furthermore, as a non-limiting example, with regard to the relationship between (B1) the user experience points awarded based on the live streaming time and the user experience points awarded based on the aforementioned (A1) live viewing time, the same value of user experience points may be awarded for the same time (length of time). Also, a larger user experience point may be awarded for the live streaming time than for the live viewing time for the same time. In other words, as a non-limiting example, if a user of a terminal streams a live video for a predetermined time, the user may be awarded at least the same number of first points as if the user watched the live video for a predetermined time.

However, instead of this, a greater user experience value may be awarded for live viewing time than for live streaming time for the same period of time.

Then, the control unit 11 of the server 10 updates the user experience value of the account management data corresponding to the application ID of user A.A. in the account management database 155.

Next, the control unit 11 of the server 10 determines whether to increase the user level of user A.A. (S1430). Specifically, based on user A.A.'s latest user experience value and the achieved user experience value in the table of FIG. 1-14, it determines whether to increase user A.A.'s user level from the current user level. In other words, in this embodiment, during a live broadcast, user experience points may be awarded to the broadcaster of that live broadcast, and the user level may be increased.

If it is determined that the level should not be increased (S1430: NO), the control unit 11 of the server 10 advances the process to S1450.
On the other hand, if it is determined that the level should be increased (S1430: YES), the control unit 11 of the server 10 updates the user level of the account management data corresponding to the application ID of user A. A in the account management database 155. Then, the control unit 11 of the server 10 transmits information regarding the increase in the user level to the terminal 20A via the communication I/F 14 as user level increase information (S1440).

After A1620, the control unit 21 of the terminal 20A determines whether user level upgrade information has been received from the server 10 via the communication I/F 22 (A1630), and if it determines that it has been received (A1630: YES), it displays the received user level upgrade information on the display unit 24 (A1640).

After S1440, the control unit 11 of the server 10 performs a live streamer experience value calculation process (S1450). Specifically, by way of example and not limitation, the control unit 11 calculates the live streamer experience value of user A.A based on at least one of the following conditions (distribution history, broadcaster behavior) and the assigned live streamer experience value (unit assigned value) set for each of the conditions shown in the screen example in the center of FIG. 1-8.
(C1) During live streaming: Your live streaming time (C2) During live streaming: Number of viewers of your live stream (C3) During live streaming: Number of support points you received (C4) During live streaming: Number of times you performed a poke

However, the conditions are not limited to these and may include other conditions. For example, but not by way of limitation, the following conditions may be included:
(C5) During live streaming: Number of comments to you (C6) During live streaming: Number of hearts you received

Then, the control unit 11 of the server 10 updates the driver experience value of the account management data corresponding to the application ID of the user A.A. in the account management database 155.
Next, the control unit 11 of the server 10 makes a determination as to whether or not to increase the user A.A.'s liver rank or level within the rank (hereinafter collectively referred to as "liver level") (hereinafter referred to as "liver level increase determination") (S1460).

FIG. 1-16 is a diagram showing an example of a table for explaining a live streamer level and a method for determining whether a live streamer level has increased.
In this table, for example and not by way of limitation, liver rank, achieved liver experience points, and levels within the rank are stored in association with each other.

Liver ranks are subdivided into multiple ranks, such as, but not limited to, "Rookie," "Regular," "Star," "Superstar," "Legend," and "God," in ascending order of rank, and a numerical range of liver experience points corresponding to each liver rank is set as "Achieved Liver Experience Points." The highest liver rank is "God."

The lower limit of the numerical range of achieved liver experience points indicates the liver experience points required to achieve that liver rank, and the upper limit of the numerical range of achieved liver experience points indicates the maximum liver experience points within that liver rank.

In this example, each liver rank is assigned a level within that liver rank. Specifically, by way of example and not limitation, for the liver ranks of "Rookie,""Regular,""Star,""Superstar," and "Legend," the lower limit of the rank level is set to "1," and the upper limit of the rank level is set to "10," so that the rank level falls within a numerical range of "1 to 10."
The system is configured to have one of the following values:

For liver ranks lower than the highest liver rank "God," as an example and not a limitation, the level within the rank can be increased for each liver experience value obtained by dividing the range value indicated by the numerical range in the corresponding achieved liver experience value column by "10."
Furthermore, for the highest liver rank "God," for example and not by way of limitation, the level within the rank can be increased by "1" for each set value (for example and not by way of limitation, "20,000" liver experience points).

In addition, the benefits to be granted to the aforementioned live streamers may be set in this table in association with the live streamer rank and level within the rank, and the control unit 11 of the server 10 may grant benefits to the live streamers based on this.

At S1460, the control unit 11 of the server 10 determines whether to increase User A.A.'s current live streamer rank and level within the rank based on User A.A.'s latest live streamer experience points and the achieved live streamer experience points in the table of FIG. 1-16 (S1460). In other words, in this embodiment, during a live stream, the live streamer may be granted live streamer experience points, which may improve the live streamer level.

If it is determined that the level should not be increased (S1460: NO), the control unit 11 of the server 10 advances the process to S1480.
On the other hand, if it is determined that the level should be increased (S1460: YES), the control unit 11 of the server 10 updates the liver rank, etc. of the account management data corresponding to the application ID of user A.A. in the account management database 155. Then, the control unit 11 of the server 10 transmits information regarding the increase in the liver level (for example, but not limited to, that the liver rank has increased, that the level within the rank has increased, the liver rank, the level within the rank, etc.) as liver level increase information to the terminal 20A via the communication I/F 14 (S1470).

The control unit 11 of the server 10 may or may not transmit the live streamer level-up information to each viewer's terminal 20.
In addition, as liver level-up information, liver level-up comment information to be displayed within comments during broadcast may be sent to each viewer/broadcaster terminal 20, and the liver level-up information may be sent only to terminal 20A.

After A1640, the control unit 21 of the terminal 20A determines whether or not liver level-up information has been received from the server 10 via the communication I/F 22 (A1650), and if it determines that it has not been received (A1650: NO), the process proceeds to A1670.

On the other hand, if it is determined that liver level-up information has been received (A1650: YES), the control unit 21 of the terminal 20A displays the received liver level-up information on the display unit 24 (A1660).

After A1660, the control unit 21 of the terminal 20A determines whether to end the live streaming based on user input via the input/output unit 23 (A1670), and if it determines not to end it (A1670: NO), returns processing to A1610.
On the other hand, if it is determined that the live distribution should be ended (A1670: YES), the control unit 21 of the terminal 20A transmits live distribution end request information to the server 10 via the communication I/F 22 (A1680).

After S1470, the control unit 11 of the server 10 determines whether or not live streaming end request information has been received from the terminal 20A via the communication I/F 14 (S1480), and if it determines that it has not been received (S1480: NO), returns the processing to S1410.
On the other hand, if it is determined that the live distribution end information has been received (S1480; YES), the control unit 11 of the server 10 transmits the live distribution end information to the terminal 20A via the communication I/F 14 (S1490).
Then, the control unit 11 of the server 10 ends the live distribution process.

After A1680, when live streaming end information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A causes the received live streaming end information to be displayed on the display unit 24 (A1690). Specifically, by way of example and not limitation, the control unit 21 causes the display unit 24 to display a screen such as that shown in FIG. 1-11.
Then, the control unit 21 of the terminal 20A ends the live distribution process.

Returning to Figure 1-12, after performing the live distribution process (A160), the control unit 21 of the terminal 20A determines whether to terminate the process (A170), and if it determines not to terminate (A170: NO), returns the process to A110.
On the other hand, if it is determined that the process should be ended (A170: YES), the control unit 21 of the terminal 20A ends the process.

Similarly, after performing the live distribution process (S140), the control unit 11 of the server 10 determines whether or not to terminate the process (S150), and if it determines not to terminate (S150: NO), returns the process to S110.
On the other hand, if it is determined that the process is to be ended (S150: YES), the control unit 11 of the server 10 ends the process.

As shown in this process, while a user is live streaming, not only the live streamer experience points but also the user experience points are calculated. Not only will the live streamer level increase, but the user level may also increase.

<Effects of the First Embodiment>
In this embodiment, a server 10 (not limited to this, an example of an information processing device) that communicates with a terminal 20 of a broadcaster that broadcasts live video broadcasts controls, via a control unit 11, to grant a user experience value (not limited to this, an example of a first point) to the user of the terminal 20 when a viewer behavior is performed on the terminal 20. The server 10 then shows a configuration in which, based on an increase in the user experience value, the control unit 11 controls to improve the user level (not limited to this, an example of a first level) of the user of the terminal 20.
As an example of an effect of an embodiment obtained by such a configuration, when a viewer behavior is performed on a terminal, the user of the terminal can be awarded first points and the first level of the user of the terminal can be improved.

In this case, the control of granting user experience points can be performed by the control unit 11 while the live video is being viewed, and the control of improving the user level can be performed by the control unit 11 while the live video is being viewed.
As an example of the effect of an embodiment obtained by such a configuration, points can be awarded to the user of the terminal or the level can be increased while watching a live video, which means that points can be awarded and the level can be increased in real time, adding a new level of interest.

In this embodiment, a server 10 (not limited to, an example of an information processing device) that communicates with a terminal 20 of a broadcaster who broadcasts live videos controls, through a control unit 11, to grant live streamer experience points (not limited to, an example of second points) to the broadcaster based on the broadcast performance of the live videos. The server 10 then controls, through the control unit 11, to improve the live streamer level (not limited to, an example of the second level) of the broadcaster based on an increase in the live streamer experience points granted to the broadcaster.
As an example of an effect of an embodiment obtained by such a configuration, second points can be awarded to a user of a terminal based on the distribution performance of live video, and the second level of the user of the terminal can be improved.

In this case, the control of granting live streamer experience points can be performed by the control unit 11 while the live video is being distributed, and the control of improving the live streamer level can be performed by the control unit 11 while the live video is being distributed.
As an example of the effect of an embodiment obtained by such a configuration, points can be awarded to the broadcaster or the broadcaster's level can be improved while the live video is being broadcast, which means that points can be awarded and levels can be improved in real time.

<Second Example>
The second embodiment is an embodiment that, by way of example and not limitation, makes it possible to reduce a user's live streamer experience points, grant benefits to live streamers, pay rewards, etc., when certain conditions are met.

The contents described in the second embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

By way of example and not limitation, the fulfillment of the specified condition can be the passage of a specified period of time (the end of the specified period). By way of example and not limitation, the specified condition can be set by the server 10, and the specified period can also be set by the server 10.

In this embodiment, the predetermined period is referred to as a "season period" or simply as a "season" as a period for each season. The season period may be set in any manner, but as a non-limiting example, it may be set to a one-month period (from the 1st to the last day of the month). In other words, the season period may be set continuously in units of one month.
Other examples of the predetermined conditions will be described later.

As shown in Figure 1-16, live streamer ranks can be set from "Rookie" to "God." This is just one example, but from "Rookie" to "Legend," users can earn experience points and increase their live streamer rank, aiming for the "God" live streamer rank. In other words, it can be a game in which users aim to improve themselves by aiming for higher live streamer ranks.

On the other hand, for the highest liver rank "God," there is no upper limit on the level within the rank ("Lv1 - No Upper Limit" as shown in Figure 1-16), allowing users to play to see how far they can improve their liver experience points and level within the rank. In addition, in this embodiment, by way of example and not limitation, users with a liver rank of "God" compete for rankings every predetermined period. Also, in this embodiment, users with a liver rank of "God" are paid a reward every predetermined period according to their performance during that period. Furthermore, in this embodiment, at the end of each predetermined period, the liver experience points of users with a liver rank of "God" are reduced and their liver level is lowered, thereby slowing down the rate at which their liver level increases.

<Display screen>
FIG. 2A is a diagram showing an example of a screen of a live distribution application displayed on the display unit 24 of the terminal 20A in this embodiment.
The left side of Figure 2-1 is the My Page screen of the live streaming application. Continuing from Figure 1-11, this figure shows an example of the My Page screen when user A.A. has become a viewer or live streamer, watched live broadcasts, or streamed live broadcasts, and Season 2 has ended.

On this screen, the user level information display area ULR displays "Lv69" as the user level, and the liver level information display area LLR displays "God Lv12" (liver rank "God", rank level "Lv12") as the liver level.
In the following, the level within the rank of the liver rank "God" may be referred to as the "God level" for convenience.

Furthermore, since User A.A. achieved the "God" liver rank, he has continued his live streamer activities and his level within the rank has improved (he is currently at "Lv12"), and as a result, User A.A. has acquired Rank Badge RB2, which is higher than Rank Badge RB1 shown on the screen in the center right of Figure 1-11, and has also acquired Frame FM2 and My Page Background BG2. Accordingly, the Rank Badge RB2 is displayed in association with the profile icon in the profile area, Frame FM2 is set to the profile icon, and My Page Background BG2 is set as the background image.

Furthermore, with the end of Season 2, information indicating the end of the season is displayed in a speech bubble from the ranking icon IC1 at the top right of the area below the in-app location display area. In this example, a speech bubble containing the words "Season 2 has ended" is displayed in response to the end of "Season 2."

In this case, when the icon image showing the ranking is tapped, the screen shown in the center of FIG. 2-1 is displayed, for example and not by way of limitation.
This screen is an example of a season ranking screen that shows the ranking of users for each season period, and the words "season ranking" are displayed in the in-app position display area.

Also, at the top of the area below that, information indicating the most recent season period that has ended (in this example, "Season 2") (in this example, a box containing the words "Season 2 Ended") is displayed, and to the left of that is a button for displaying rankings for past season periods.

In this example, the user rankings for "Season 2" are shown as follows: 1st place is "User D.D.", 2nd place is "User A.A.", 3rd place is "User C.C.", and 4th place is "User B.B." In addition, for each ranking, the icon image and username of the user in that rank are displayed, and in association with these, the number of trophies that user has earned as a season ranking reward and the user's current liver level are displayed.

In addition, user rankings may be determined based on, for example and not by way of limitation, the total amount of Liver Experience Points each streamer has earned during the season, or the Liver Experience Points each streamer has at the end of the season (the final Liver Experience Points of the season).

By way of example and not limitation, when the "Get" button BT1 is tapped on the screen in the center of Figure 2-1, the screen on the right side of Figure 2-1 is displayed, which displays information about the season rewards that user A.A. has earned in that season.
For example, but not by way of limitation, the season reward may be a reward that is the sum of the season level reward and the season ranking reward (season level reward + season ranking reward).

Specifically, the top section displays information about the season level rewards granted based on User A.A.'s god level of "Lv12." Specifically, the season level rewards corresponding to the god level are displayed in a pyramid divided into god level bands. Because User A.A.'s god level is "Lv12," the god level band of "Lv11 to Lv20" in the pyramid is displayed in color, indicating that the corresponding season level reward of "10,000" trophies has been granted.

Also, below that, information regarding the season ranking reward awarded based on User A.A.'s season ranking of "second place" is displayed. Specifically, it is shown that User A.A.'s season ranking of "second place" has resulted in the awarding of the corresponding season ranking reward of "50,000" trophies.
Furthermore, in this example, it is shown that the season ranking title (earned title) "Eternal Second Place!" has been acquired based on the season ranking being "second place."

Furthermore, information about User A.A.'s season rewards is displayed below that. Specifically, it shows that User A.A. has earned a total of 60,000 trophies as a season reward, combining the above-mentioned season level reward of 10,000 trophies with the season ranking reward of 50,000 trophies.

Here, the above trophy can be, by way of example and not limitation, a benefit (which can also be considered a reward) given to a user who has achieved the highest liver rank of "God."

One way to think of trophies is that they can be considered as reward objects, similar to the aforementioned "rank badges," "frames," "my page backgrounds," and other objects.

Alternatively, the trophy may be a reward that can be converted into a valuable reward, such as, by way of example and not limitation, a predetermined number of points or cash.
The activities of live streamers can enable live streaming service providers to earn revenue through the aforementioned paid items from viewers, and a portion of that revenue can be returned to the live streamers based on season rewards.

By way of example and not limitation, the points can be used as valuable value in various services provided by businesses affiliated with the live streaming service provider, or in various services provided by the live streaming service provider itself.

The point here is that, by way of example and not limitation, it can be thought of as a type of corporate currency that is different from legal tender.
Electronic money may also be considered a type of corporate currency, and electronic money may be awarded instead of points.

Points can be used for a variety of purposes, including but not limited to, payments in a payment application (a wallet application may be configured as a comprehensive application that includes a payment application) for making payments (settlements) using electronic money, for purchasing stamps or costumes in a messaging application, or for purchasing music or exchanging for coupons in a music distribution application. In addition to these, points may also be used to exchange for goods and services at stores (affiliated stores) affiliated with the operators of the above services.

By way of example and not limitation, points may be awarded by the server 10 to the user of the terminal 20 in a payment application or wallet application that is downloaded to and executed on the terminal 20.

In addition, as a non-limiting example, cash payments can be made by having the server 10 communicate with the server of the financial institution to transfer the money to an account at the financial institution registered by the user. Payments can also be made in the form of electronic money using a payment application or wallet application that is downloaded to and executed on the terminal 20.

Furthermore, the above-mentioned various applications may be configured as an integrated application, and may be completed within this integrated application.
Also, by way of example and not limitation, a messaging application may have the functionality of the various applications described above, and the functionality may be completed within this messaging application.
In this case, the server 10 may have all the functions, or each function may be assigned to a separate server.

By way of example and not limitation, a user who has registered an account as a general user on a live streaming application and further registered as a live streamer can be broadly classified into the following two types of users, by way of example and not limitation.
(a) Independent users (users who are not affiliated with any agency)
(b) Users who belong to a live broadcasting agency

Furthermore, the users of (b) can be broadly divided into the following two groups, by way of example and not limitation.
(b1) A user who belongs to a live broadcaster agency operated by a live streaming service provider. (b2) A user who belongs to an external live broadcaster agency other than a live streaming service provider.

By way of example and not limitation, the server 10 may vary the type of reward paid to a user and the proportion of reward paid (payment rate) based on the above user classification.

By way of example and not limitation, users in (a) may be rewarded with points, and users in (b) may be rewarded with cash.

By way of example and not limitation, the server 10 may set the payment rate for user (a) to "20%" and pay "20%" of the season reward as points as reward.

Additionally, the server 10 may, for example and without limitation, impose different payment rates on users of (b1) and users of (b2).
By way of example and not limitation, user (b1) may have a payout rate of "40%" and be paid in cash an amount equivalent to "40%" of the season reward. In contrast, user (b2) may have a payout rate of "50%" and be paid in cash an amount equivalent to "50%" of the season reward. This example is by way of example and not limitation, where user (b2) has a higher payout rate than user (b1).
However, the relationship between the payment rates may be reversed.

It is also possible to provide both users (a) and users (b) with points or corporate currency such as electronic money, or to pay cash to both users without distinguishing between them.
Furthermore, the payment rate may be the same for both users (b1) and users (b2) without any distinction being made between them.
Also, the payout rates may differ from the above example.

The left side of FIG. 2-2 is a diagram showing an example of a screen that is displayed when the "OK" button BT2 is tapped on the screen on the right side of FIG. 2-1.
This screen is an example of a season ranking screen, and in this example, information is displayed indicating that the god level of user A.A. has decreased with the end of season 2.

Specifically, it is shown that the Liver Experience value of User A.A. at the beginning of Season 3 will decrease from "443,297" at the end of Season 2 to "321,649." The calculation method will be described in detail later.
Additionally, it is shown that, with the decrease in the liver experience points, the god level of user A.A. at the beginning of Season 3 will decrease from "Level 12" at the end of Season 2 to "Level 7."

When the "OK" button BT3 is tapped on the screen on the left side of FIG. 2-2, the screen on the right side of FIG. 2-2 is displayed, for example and not by way of limitation.
This screen is the My Page screen mentioned above, and in the profile area, in addition to the rank badge RB2, frame FM2, and My Page background BG2 mentioned above, as an example and not a limitation, the season ranking title AT2 (which may be considered the object mentioned above) for "Eternal Second Place!" shown on the screen on the right side of Figure 2-1 is displayed in association with the season period (in this example, "Season 2").

In addition, the liver level information display area LLR displays an icon image of the character (bear character) corresponding to the liver rank "God," along with "God Lv7," in accordance with the drop in God level from "LV12" to "LV7" as described above.

<Processing>
Fig. 2-3 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The diagram should be read in the same way as Fig. 1-12.

After S140, or if it is determined in S130 that the live streaming request information has not been received from the terminal 20A (S130: NO), the control unit 11 of the server 10 determines whether the season has ended (S210). The end of the season can be determined based on the timekeeping information of the clock unit 19, for example, but not by way of limitation.
If it is determined that the season has not ended (S210: NO), the control unit 11 of the server 10 returns the process to S110.

On the other hand, if it is determined that the season has ended (S210: YES), the control unit 11 of the server 10 performs a season result calculation process (S220).

FIG. 2-4 is a diagram showing an example of a table for explaining a method for determining the season level reward and the liver level for the next season from the season results calculated in the season result calculation process.
This table associates, by way of example and not limitation, god levels, season level rewards, and season reset experience loss rates.

In this table, the God level is the level within the rank of a user with a "God" liver rank at the end of this season, and in this example, a certain range of God level ranges has been defined.

In this table, the season level reward can be, by way of example and not limitation, a reward awarded to a user based on the god level band to which the user's god level belongs at the end of the current season. An example of a season level reward can be the trophy mentioned above.

In this table, the season reset experience point loss rate is a value used to calculate the initial liver experience points for the next season (hereinafter referred to as "initial liver experience points for the next season").

The initial liver experience value for the next season can be calculated, for example and not by way of limitation, according to the following formula (1):
Next season's initial liver experience points = this season's final liver experience points - (this season's final liver experience points - achieved liver experience points corresponding to God level Lv1) x season reset experience point loss rate ... (1)

The final liver experience points of the season may be, by way of example and not limitation, the liver experience points at the end of the current season.
The achieved liver experience value corresponding to God level Lv1 can be, by way of example and not limitation, the lower limit of the achieved liver experience value associated with the liver rank "God" in the table shown in Figure 1-16 ("200,000" in the example of Figure 1-16).

According to formula (1), the initial liver experience value for the next season will not fall below the achieved liver experience value corresponding to God level Lv1, so the liver rank will not fall from "God". This is because it may be cruel to the user if the liver rank falls from "God".
Unlike this embodiment, formula (1) may be modified so that the liver rank may fall from "God" in some cases.

Also, as a non-limiting example, if a liver's god level has increased this season, the season reset experience loss rate may be lower than the rate set in the table above.

The season level reward is set so that the higher the god level (god level range), the larger the value. In other words, the higher the user's god level at the end of this season, the more season level rewards will be awarded.

Also, in this example, the season reset experience loss rate is set to a value that decreases overall the higher the god level (god level band). In other words, the value is set so that the higher the user's god level at the end of the season, the smaller the rate at which liver experience points are reduced (the lower the loss rate). However, in the example of Figure 2-4, the same value may be set even for different god level bands.

By way of example and not limitation, in the example shown on the left side of FIG. 2-2, user A.A's god level in Season 2 is "Lv12" and his final liver experience value for this season is "443,297."
Also, in FIG. 2-4, the season reset experience loss rate corresponding to the god level "Lv12" is "50%."
Also, in Figure 1-16, the experience points of a liver who has achieved God level are "200,000".
In this case, when the initial live stream experience value of user A.A. for the next season is calculated according to formula (1),
Next season's initial liver experience = 443,297 - (443,297 - 200,000) x 50% = 321,649
The corresponding god level is calculated as "Lv7".

However, if the Liver's experience points after the reduction are within the range of their God level before the reduction, their God level will not change.

FIG. 2-5 is a diagram showing an example of a table for explaining a method for determining the season ranking reward from among the season results calculated in the season result calculation process.
This table associates God rankings with season ranking rewards by way of example and not limitation.

The God Ranking is, by way of example and not limitation, a ranking of users for this season, and is calculated as the ranking (position) of users whose Liver Rank is "God."

By way of example and not limitation, the season ranking reward may be a reward awarded to a user based on the user's god ranking for the current season. By way of example and not limitation, the season ranking reward may also be the trophy mentioned above.

The higher your God Ranking (season ranking), the greater the value of your season ranking rewards. In other words, the higher your ranking, the more season ranking rewards you will receive.

In this example, for a certain degree of high god ranking (for example, "1st to 3rd place" and not limited to this), the season ranking reward is set to a relatively larger value compared to the average season level reward set in Figure 2-4. In other words, in this example, aiming for a high season ranking makes it easier to obtain more rewards than aiming to increase your god level.
This increases users' motivation to obtain the season ranking rewards. While the God level at the end of the season is determined by a streamer's long-term performance regardless of the season period, the season ranking is determined by a streamer's short-term performance within the season period. Therefore, for new streamers, the season ranking rewards are easier to obtain than the season level rewards. Setting the season ranking rewards higher is expected to result in increased activity within the live streaming community, leading to an increase in the number of live streams and the quality of live streams within the live streaming service.

In addition, for somewhat higher god levels (for example, "Lv51+" and not limited to this), the season level reward may be set to a relatively larger value compared to the average season ranking reward set in Figure 2-5.

In addition, the aforementioned season ranking titles associated with the God rankings may be set in this table, and the control unit 11 of the server 10 may assign season ranking titles to live streamers based on this.

In this embodiment, as described above, seasonal ranking rewards are provided, and additional rewards are awarded depending on the ranking for the season. In this way, users who have reached the highest liver rank can be motivated to strive to achieve higher rankings.

When user A.A.'s liver level is "God," the control unit 11 of the server 10 determines the season level reward corresponding to this God level based on user A.A.'s God level at the end of the season, by referencing the table in Figure 2-4. Furthermore, the control unit 11 of the server 10 calculates user A.A.'s initial liver experience points for the next season based on the season reset experience point loss rate corresponding to that God level, for example but not by way of limitation, according to equation (1).

Furthermore, the control unit 11 of the server 10 determines the season ranking of user A.A. based on the god level of each user of the terminal 20. Then, the control unit 11 of the server 10 references the table in FIG. 2-5 and determines the ranking reward for user A.A. according to the determined season ranking. Then, the control unit 11 of the server 10 determines the season reward to be granted to user A.A. as "season level reward + season ranking reward."

After S220, the control unit 11 of the server 10 transmits the season result information to the terminal 20A via the communication I/F 14 (S230). The season result information may include, but is not limited to, the current season's liver level (if the liver rank is "God") calculated in S220 as described above, the season ranking (if the liver rank is "God"), the season reward (if the liver rank is "God"), the next season's God level (if the liver rank is "God"), etc. Then, the control unit 11 of the server 10 ends the processing.

If it is determined in A210 that the season has ended (A210: YES), the control unit 21 of the terminal 20A causes the display unit 24 to display the season result information received from the server 10 via the communication I/F 22 (A220). The control unit 21 of the terminal 20A then terminates the processing.

After the season ends, the control unit 11 of the server 10 performs payment processing to pay points or cash to the user according to the season reward, using the various methods described above. As a non-limiting example, if the closing date for tallying is the end of the month, payment processing is performed the following day (the first day of the month), and the season reward is reset. In this way, the user will not be able to continue to hold the season reward (trophy).

In the table of Figure 2-5, by way of example and not limitation, the table may be configured so that season ranking rewards are awarded only to live streamers whose god ranking is above a certain rank. By way of example and not limitation, season ranking rewards may be awarded only to the top five users in the season ranking.

Additionally, the aforementioned season level rewards and season ranking rewards may be considered as perks, as mentioned above.
Also, as mentioned above, the rewards (points, cash, etc.) associated with the above benefits may differ depending on the live streamer.

<Effects of the Second Example>
In this embodiment, a server 10 (not limited to, an example of an information processing device) that communicates with a terminal 20 of a broadcaster who broadcasts live videos uses a control unit 11 to control the broadcaster to grant live stream experience points (not limited to, an example of points) based on the broadcaster's live stream broadcast performance. The server 10 also uses the control unit 11 to control the broadcaster to improve its live stream level (not limited to, an example of a level) based on an increase in the live stream experience points granted to the broadcaster. The server 10 also uses the control unit 11 to control the broadcaster to decrease the live stream experience points granted to the broadcaster when a predetermined condition is met. The server 10 also uses the control unit 11 to control the broadcaster to lower its live stream level based on a decrease in the live stream experience points.
As an example of the effect of this configuration, the level of a broadcaster can be improved based on an increase in points awarded to the broadcaster, while the points awarded to the broadcaster can be reduced when a predetermined condition is met, and the broadcaster's level can be lowered based on the reduction in points. This can make the broadcaster aware of the risk of a level drop and motivate the broadcaster to make an effort to continue live broadcasting. It can also slow down the rate at which the broadcaster's level improves. Furthermore, it can provide a new interest.

In this case, the control of granting live streamer experience points can be performed by the control unit 11 while the live video is being distributed, and the control of improving the live streamer level can be performed by the control unit 11 while the live video is being distributed.
As an example of the effect of an embodiment obtained by such a configuration, points can be awarded to the broadcaster or the broadcaster's level can be improved while the live video is being broadcast, which means that points can be awarded and the level can be improved in real time, adding a new level of interest.

In this case, the server 10 can reduce the amount of reduction in the live stream experience points granted to the broadcaster when the broadcaster's live stream level exceeds a set level (not limited to this, but an example of a predetermined level) compared to when the set level is not exceeded.
As an example of the effect of an embodiment obtained by such a configuration, when a broadcaster's level exceeds a predetermined level, the amount of reduction in points awarded to the broadcaster is reduced more than when the level does not exceed the predetermined level, making it less likely that high-level broadcasters will lose motivation.

In this case, the fulfillment of the predetermined condition may include the passage of a season period (not limited to this, but an example of a predetermined period).
As an example of the effect of an embodiment obtained by such a configuration, when a predetermined period of time has elapsed, the points awarded to the distributor can be reduced based on the establishment of conditions that are easy for the distributor to understand.

In this case, the server 10 can control the control unit 11 to grant a season ranking reward (not a limitation, but an example of a benefit) to a broadcaster if the season ranking (not a limitation, but an example of a ranking based on points granted to a broadcaster within a specified period) based on the live streamer experience points granted to the broadcaster within the season period is higher than a specified ranking.
As an example of the effect of an embodiment obtained by such a configuration, if the ranking based on the points awarded to the broadcaster within a specified period is higher than a specified ranking, the broadcaster's motivation can be improved by being awarded a bonus.

In this case, the server 10 can control, via the control unit 21, to award a season level reward to the broadcaster based on the total live streamer experience value (or god level) (which is not limited to, but is an example of the sum of points awarded to the broadcaster within a specified period and points awarded to the broadcaster outside the specified period), whether the season ranking is higher than a specified rank or not.
As an example of the effect of an embodiment obtained by such a configuration, regardless of whether the above ranking is higher than a predetermined ranking, a bonus may be awarded to the broadcaster based on the sum of the points awarded to the broadcaster within a predetermined period and the points awarded to the broadcaster outside the predetermined period, thereby improving the broadcaster's motivation.

In this case, the season ranking reward awarded when the season ranking is higher than a predetermined rank can be set to be greater than the season level reward awarded to the broadcaster based on the sum of points awarded to the broadcaster within the season period and points awarded to the broadcaster outside the predetermined period.
As an example, but not by way of limitation, of an effect of this configuration, the higher the ranking of a broadcaster, the more rewards the broadcaster can receive than the rewards that would be given to the broadcaster based on the sum of points awarded to the broadcaster within a predetermined period and points awarded to the broadcaster outside the predetermined period. As a result, even if the total is low, this can motivate the broadcaster to strive to achieve a higher ranking.

Furthermore, in this embodiment, a plurality of liver ranks (not limited to, but an example of, a rank) for a broadcaster are provided, including at least a rank lower than God rank (not limited to, but an example of the first rank) and God rank (not limited to, but an example of the second rank higher than the first rank), and a plurality of in-rank levels are provided corresponding to the plurality of liver ranks, and the broadcaster's liver rank is improved to God rank based on the broadcaster experience points granted to the broadcaster exceeding the achieved liver experience points corresponding to the highest in-rank level in a rank lower than God rank. Furthermore, when a broadcaster's liver rank is God rank, the god level in the god rank is improved based on the broadcaster experience points granted to the broadcaster.
As an example of the effect of this embodiment obtained by such a configuration, it is possible to easily set a target for reaching from the first rank to the second rank.

In this case, the server 10 may not perform control to reduce the liver experience points granted to the broadcaster based on the fulfillment of a specified condition if the broadcaster's liver rank is lower than the God rank, and may perform control to reduce the liver experience points granted to the broadcaster based on the fulfillment of a specified condition if the broadcaster's liver rank is the God rank, and may also perform control to lower the broadcaster's God level based on the reduction in the liver experience points.
As an example of the effect of this configuration, if the broadcaster's rank is the first rank, which is lower than the second rank, the points awarded are not reduced, thereby motivating the broadcaster to aim for the second rank. On the other hand, after the broadcaster reaches the second rank, the points awarded are reduced and the broadcaster's level is lowered accordingly, thereby giving the broadcaster a sense of crisis.

In this case, when a predetermined condition is met, it is possible to prevent the broadcaster's live streamer rank from dropping from God rank to a rank lower than God rank.
As an example of the effect of an embodiment obtained by such a configuration, even if a predetermined condition is met, the rank of the distributor is prevented from dropping from the second rank to the first rank, thereby giving the distributor a sense of security.

In this embodiment, the server 10 controls the granting of a series to a broadcaster through the control unit 11. In this case, the reward associated with the benefit can be made different depending on the broadcaster.
As an example of an effect of the embodiment obtained by such a configuration, it is possible to give a special benefit to a distributor, and to vary the reward associated with the special benefit depending on the distributor.

<Second Modification Example (1)>
In the above example, the condition (not limited to, but an example of a predetermined condition) for reducing a user's liver experience points or liver level is the passage of a season period (not limited to, but an example of a predetermined period), but this is not limited to this.

By way of example and not limitation, the fulfillment of a predetermined condition may be when a user who was ranked number one last season has achieved a set amount of live streamer experience since the start of this season (or more than a set amount), or when a user who was ranked number one last season has increased their live streamer experience by a set percentage or more (or more than a set percentage) from their live streamer experience at the start of this season. This is a non-limiting example of a situation where a specific user has been in the lead since the start of this season.

The predetermined condition may be satisfied when the live streamer experience value of a user reaches or exceeds a set value. This is a non-limiting example of a case where a live streamer experience value that is the goal of the season is set in advance.
The predetermined condition can be freely set on the server 10 side, for example, but is not limited to this.

<Second Modification Example (2)>
In the above embodiment, a continuous season period is exemplified as the predetermined period, but the present invention is not limited to this.
The predetermined period is not limited to the above, and may be set to a discrete period. In other words, a season period may be set at regular time intervals.

Additionally, the length of the period may be variable, whether it is a continuous period or a discrete period.
As a non-limiting example, if the difference in next season live streamer experience value between the user with the highest next season live streamer experience value calculated according to formula (1) and the user with the second highest next season live streamer experience value is equal to or greater than a set value (or exceeds a set value), the period of the next season may be set to a period shorter than this season. In other words, if the live streamer experience value of the top-ranked user is particularly high, the period of the next season may be shortened to prevent an even greater difference.
Conversely, if the difference is less than the set value (or equal to or less than the set value), a period longer than this season may be set as the period of the next season.

As with the specified conditions, the specified period is not limited and can be freely set by the server 10, for example.

<Second Modification Example (3)>
The method of reducing the driver experience points described in the above embodiment is merely an example, and is not limited to this.

FIG. 2-6 is a diagram showing another example of the table in FIG. 2-4.
This table, like the table in Figure 2-4, associates and sets the god level, season level reward, and season reset experience point loss rate by way of example and not limitation, but is mainly different in the column for season reset experience point loss rate.

The Season Reset Experience Loss Rate column is divided into cases where this season is not a new record and cases where this season is a new record, by way of example and not limitation.
A case where this season is a new record may be, for example and without limitation, when the user's live stream experience points this season are the highest ever. Conversely, a case where this season is not a new record may be any other case.

However, instead of the above, if the user's season ranking this season is the highest ranking they have ever achieved, this may be considered a new record.

In both cases where this season is not a new record and where this season is a new record, the values are generally set so that the higher the god level, the smaller the season reset experience loss rate. However, in the example in Figure 2-6, the same value may be set even for different god level ranges.
On the other hand, when focusing on the same God level (God level range), the season reset EXP loss rate for a new record this season is set to be relatively smaller than the season reset EXP loss rate for a new record this season. In other words, for a live streamer who set a new record this season, the loss rate of live streamer EXP is reduced taking into account their performance.

The above is merely an example and is not limiting.
Regardless of the god level (god level range), the season reset experience loss rate in the event that this season is a new record may be set to a uniform value (for example, "30%" without any limitations).
Also, the season reset experience point loss rate may be set to "0%" so that new records can be recorded as history.

This modified example shows a configuration in which, when the liver experience points granted to a broadcaster within a season period (a predetermined period, not a limited period) exceed a set value (an example of a predetermined point, not a limited value), the server 10 reduces the amount of reduction in the liver experience points granted to the broadcaster compared to when the value does not exceed the set value.
As an example of the effect of the modified example obtained by such a configuration, when the points awarded to a distributor within a specified period exceed a specified number of points, the amount of reduction in the points awarded to the distributor is smaller than when the specified number of points are not exceeded. This makes it possible to prevent the distributor's points from decreasing too much in cases where the distributor has acquired a large number of points within a specified period.

<Second Modification Example (4)>
In the above embodiment, points or cash are paid to the user based on the season reward (season level reward + season ranking reward), but the present invention is not limited to this.

By way of example and not limitation, points or cash may be paid to the user based on the season level reward. In this case, the objects may be different; by way of example and not limitation, the object for the season level reward may be a "trophy" and the object for the "season ranking reward" may be a "medal." This allows the user to recognize that the season level reward can be converted into points or cash.

Conversely, points or cash may be paid to users based on their season ranking rewards.

<Third Example>
The third embodiment is an example, not a limitation, in which a user who has been using a live streaming application as a viewer makes his/her debut as a streamer (liver).
It is believed that there are dedicated viewers among live viewers, and that these viewers have the potential to become successful streamers as well. However, it can be more difficult to become a streamer than to become a viewer.

The contents described in the third embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
3A is a diagram showing an example of a live streaming application screen displayed on the display unit 24 of the terminal 20 in this embodiment. Here, a case where a user F.F., different from the above-mentioned user A.A., debuts as a live streamer is illustrated.
The screens described below are those displayed on the display unit 24 of the terminal 20F of this user F.F.

The left side of Figure 3-1 shows the My Page screen of the live streaming application. In this example, user F.F. is only using the live streaming application as a viewer and has not yet debuted as a live streamer (has not yet registered as a live streamer).

In the profile area, a base image set by user F.F. is displayed as a profile icon PI3.
Also, in this example, the My Page background BG3 is blank (unset) because user F.F. has not set a background himself or herself, or is not registered as a live streamer and is therefore unable to set a background.

Furthermore, since user F.F. is not registered as a live streamer, the live streamer level information display area LLR, which is configured in the same way as the screen shown on the left side of Figure 1-8, displays the words "Become a Live Streamer" as information for live streamer registration. When the live streamer level information display area LLR is tapped, the screen in the center of Figure 3-1 is displayed, by way of example and not limitation.

This screen is a live status screen configured similarly to the screen shown in the center of Figure 1-8, but is not limited to this screen. In the detailed liver level information display area LLDR, since user F.F. has made his debut as a liver, the liver rank "Rookie" and rank level "Lv1" are displayed, and a frog character icon image is displayed as the character icon image corresponding to this liver level.

Furthermore, just like the screen shown in the center of Figure 1-8, below the display of the liver rank and level within the rank, a liver experience gauge and text are displayed showing the amount of liver experience required to level up to the next level within the rank. However, in this example, the display related to this embodiment displays information about the liver bonus that user F.F. has acquired upon user F.F.'s debut as a liver.

Details will be provided below, but user F.F. is awarded a live streamer bonus based on at least one of the user experience points and user level he or she earned while acting as a viewer, and in this example, a speech bubble containing the words "LIVER EXP BONUS IN PROGRESS!" is displayed, along with the live streamer experience gauge LG1 increasing by the amount of live streamer experience points awarded as a live streamer bonus. In this example, the increase in this live streamer experience gauge LG1 continues until the screen on the right side of Figure 3-1.

Finally, the screen on the right side of Figure 3-1 is displayed. In this example, the liver bonus results in the user F.F.'s liver rank being raised to the second-lowest "Regular" rank, and his level within that rank being raised to "Lv2."
In this way, in this embodiment, a live streamer bonus is awarded upon debuting as a live streamer, and at the time of debuting as a live streamer, user A.A. can begin activities as a live streamer with their live streamer level increased by the amount of the live streamer bonus.

FIG. 3-2 is a diagram showing an example of a screen displayed when user F.F. performs live streaming after making his/her debut as a live streamer, unlike FIG. 3-1.
Here, an example is shown in which user F.F. is not granted a livery bonus when he/she debuts as a livery member, and starts with the lowest livery rank of "Rookie" and a level within that rank of "Lv1."

On the My Page screen on the left side of Figure 3-2, when the Liver Level Information Display Area LLR containing the words "Become a Liver" is tapped, and after being registered as a live streamer by the server 10, when user F.F. starts live streaming, the screen in the center of Figure 3-2 is displayed, by way of example and not limitation.

This screen is a live streaming screen by user F.F., and has a configuration similar to the screen for user A.A.'s live streaming shown in Figure 1-10. However, in this example, a live streamer bonus based on at least one of the user experience points and user level that user F.F. earned while acting as a viewer before his live stream debut is added to the live streamer experience points that user F.F. earned during the live stream. To indicate this, a speech bubble containing the words "Liver EXP 190% bonus!" is displayed below the live streamer experience gauge LG2 (a gauge containing the words "Rookie Lv1").

When user F.F. acquires Liver Experience Points, they accumulate Liver Experience Points equal to the Liver Bonus. When user F.F.'s Liver Level increases, the screen on the right side of Figure 3-2 will be displayed, as an example and not a limitation.

As a result of gaining experience points, the rank level has increased from "Lv1" to "Lv2," and the rank level "Lv2" is displayed next to the liver rank "Rookie" on the liver experience gauge LG2. The gauge amount on the liver experience gauge LG2 has also increased to the position corresponding to the rank level "Lv2."

In addition, based on the level within the rank having been upgraded to "Lv2," a Liver Level Up Information LUI pops up in the center of the screen. This Liver Level Up Information LUI is information indicating that the level within the rank has been upgraded, and may therefore also be referred to as Liver Level Up Information within the rank.

In addition, comment display area CDR displays comment CM3, which is a comment originating from user F.F., and includes the text "Your rank level has increased!" associated with user F.F.'s icon image and username, and an icon of the liver level after the level increase, "Rookie Lv2." Like comment CM1 and comment CM2 described above, comment CM3 is a different comment from ordinary comments based on user input, and, by way of example and not limitation, can be a comment generated by server 10 when it determines that a liver's rank or rank level has increased and sent to each terminal 20.

<Processing>
3-3 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The diagram should be read as described above.
In accordance with the flowchart described above, the process will be illustrated and explained as being executed by the control unit 21 of the terminal 20A.

After A130, the control unit 21 of terminal 20A determines whether user A.A. of terminal 20A will make their debut as a live streamer (A310). If it is determined that user A.A. will not make their debut as a live streamer (A310: NO), the control unit 21 of terminal 20A proceeds to A210.

On the other hand, if it is determined that the user will make their debut as a live streamer (A310: YES), the control unit 21 of the terminal 20A sends live streamer participation request information requesting participation as a live streamer to the server 10 via the communication I/F 22 (A320).

After S120, the control unit 11 of the server 10 determines whether or not live streamer participation request information has been received from the terminal 20A via the communication I/F 14 (S310), and if it determines that it has not been received (S310: NO), the process proceeds to S130.

On the other hand, if it is determined that live streamer participation request information has been received (S310: YES), the control unit 11 of the server 10 performs live streamer bonus calculation processing (S320).

Next, the control unit 11 of the server 10 transmits the liver bonus information to the terminal 20A via the communication I/F 14 based on the calculation results of the liver bonus calculation process (S330). The control unit 11 of the server 10 then proceeds to S130.

After A320, when the communication I/F 22 receives live streamer bonus information from the server 10, the control unit 21 of the terminal 20A displays the received live streamer bonus information on the display unit 24 (A330). The control unit 21 of the terminal 20A then proceeds to A140.

FIG. 3-4 is a diagram showing an example of a table for explaining a method for calculating a livery bonus.
In this table, as an example and not a limitation, a bonus award opportunity (bonus award timing), a live streamer bonus, a first example, a second example, and a third example are associated with each other.

The bonus grant opportunity is the opportunity (timing) at which the live streamer bonus is granted, and in this example, it is defined as "at the time of live streamer registration" (before broadcasting a live stream) and "at the time of live broadcasting" (during or after broadcasting a live stream).

A Liver Bonus is a bonus awarded to a Liver during the corresponding bonus awarding opportunity.

For the bonus grant opportunity "When registering as a live streamer," as an example and not a limitation, the live streamer bonus is set to "initial value of live streamer experience points = [user level x 50]." This means that when a viewer user wishes to become a live streamer and the server 10 registers them, the initial value of the live streamer experience points for that user is not set to "0," but rather the value obtained by multiplying the user's most recent user level by a set multiplier (50x in this example) is set as the initial value of the live streamer experience points. This makes it possible for a user to debut as a live streamer with the amount of live streamer experience points corresponding to their user level.

For the bonus grant opportunity "during live streaming," the liver bonus is set, by way of example and not limitation, as "(100 + [user level])% multiplied by [liver experience points based on streaming performance]." This means that after a viewer registers as a liver, while they are live streaming, or after the live stream has ended, the liver bonus will be a bonus experience points based on their user level added to the liver experience points they have earned based on their live streaming performance.

The first to third examples show combinations (patterns) to which the above is applied.
The first example is an example in which the "liver bonus at the time of liver registration" is applied, but the "liver bonus at the time of live streaming" is not applied.
The second example is an example in which the "liver bonus at the time of liver registration" is not applied, but the "liver bonus at the time of live streaming" is applied.
The third example is an example in which both the "liver bonus at the time of liver registration" and the "liver bonus at the time of live streaming" are applied.
The server 10 can freely set which combination to apply.
It should be noted that the user (terminal 20) may be able to set which combination to apply by charging a fee or the like.

When applying the "Liver Bonus at the Time of Liver Registration," the control unit 11 of the server 10 calculates the livery bonus based on the above formula in the livery bonus calculation process of S320 in FIG. 3-3, and can set this value as the initial value of the livery experience value of user A.A.
Furthermore, the control unit 11 of the server 10 can determine the user A.A.'s live streamer level based on the initial value of the user A.A.'s live streamer experience value, for example and without limitation, based on the table shown in FIG. 1-16, and set this as the initial value of the user A.A.'s live streamer level.

When applying the "live streaming live stream bonus," the control unit 11 of the server 10, by way of example and not limitation, calculates the live stream bonus based on the above formula in step S1450 of the live streaming process (FIG. 1-15) executed in step S140 of FIG. 3-3, and can update the live stream experience value of user A.A. with that value.
In addition, when calculating the live stream bonus after live streaming, the control unit 11 of the server 10, by way of example and not limitation, calculates the live stream bonus based on the above calculation formula after step S140 in FIG. 3-3 and can update the live stream experience value of user A.A. with that value.

<Effects of the Third Embodiment>
In this embodiment, a server 10 (not limited to, an example of an information processing device) that communicates with a terminal 20 to which live video is distributed performs control by a control unit 11 to grant a user experience value (not limited to, an example of a first point) to the user of the terminal 20 when a viewer behavior is performed on the terminal 20. The server 10 also performs control by a control unit 11 to improve the user level (not limited to, an example of a first level) of the user of the terminal 20 based on an increase in the user experience value. The server 10 also shows a configuration in which, when the user of the terminal 20 becomes a broadcaster of live video, the server 10 performs control by a control unit 11 to determine a live streamer level (not limited to, an example of a second level) of the user of the terminal 20 based on the user level.
As an example of the effect of an embodiment obtained by such a configuration, the second level at which the user of the terminal becomes a broadcaster of live video is determined based on the first level, which is based on an increase in first points awarded to the user of the terminal based on the viewer's behavior, thereby effectively motivating the user of the terminal to convert from a viewer to a broadcaster.

In this case, when the user of the terminal 20 broadcasts a live video, the server 10 controls the control unit 11 to grant the user of the terminal 20 a live streamer experience point (not limited to, an example of second points) different from the user experience point, based at least on the broadcasting performance of the live video. Furthermore, the server 10 controls the control unit 11 to improve the live streamer level (not limited to, an example of the second level) of the user of the terminal 20 based on an increase in the live streamer experience point. In this case, the live streamer experience point can be based on the broadcasting performance of the live video and the user level (not limited to, the first level).
As an example of an effect obtained by this configuration, second points different from the first points can be awarded to a terminal user based on the live video distribution performance, and the second level of the terminal user can be improved based on an increase in the second points. Meanwhile, since the second points are based on the live video distribution performance and the first level, the second points are awarded taking into consideration not only the live video distribution performance but also the first level, so that the terminal user can be more effectively motivated to convert from a viewer to a broadcaster.

In this case, if the liver level determined when the user of terminal 20 becomes a live video distributor is a higher level, the user of terminal 20 can be notified that the liver level corresponding to the lower level has been met by, for example and not by way of limitation, displaying the liver experience gauge displayed on display unit 24 of terminal 20 to increase to the higher level.
As an example of the effect of this embodiment, the user of the terminal can be made aware that he or she has already surpassed a lower level even before the user has started live video distribution after becoming a broadcaster. This can also improve the user's motivation as a broadcaster and support the activities of the user of the terminal.

In this embodiment, a server 10 (not limited to, an example of an information processing device) communicating with a terminal 20 to which a live video is distributed performs control via the control unit 11 to grant a user experience value (not limited to, an example of a first point) to the user of the terminal 20 when a viewer behavior is performed on the terminal 20. The server 10 also performs control via the control unit 11 to improve the user level (not limited to, an example of a first level) of the user of the terminal 20 based on an increase in the user experience value. The server 10 also performs control via the control unit 11 to grant a live streamer experience value (not limited to, an example of a second point) different from the user experience value to the user of the terminal 20 based at least on the distribution history of the live video when the user of the terminal 20 distributes a live video. The server 10 also performs control via the control unit 11 to improve the live streamer level (not limited to, an example of a second level) of the user of the terminal 20 based on an increase in the live streamer experience value. In this case, the live streamer experience value (not limited to, an example of a second point) can be based on the distribution history of the live video and the user level (not limited to, a first level).
As an example of the effect of this embodiment obtained by such a configuration, it is possible to effectively motivate terminal users to change from viewers to distributors.

In this case, when a user of the terminal 20 becomes a broadcaster of a live video, the server 10 can control the determination of the live streamer level (not limited, but an example of the second level) based on the user level (not limited, but an example of the first level) using the control unit 11.
As an example of an effect of an embodiment obtained by such a configuration, when a user of a terminal becomes a broadcaster of a live video, the second level of the user of the terminal can be appropriately determined based on the first level of the user of the terminal.

In this case, the viewer behavior may include viewing live video, and the user experience value awarded may vary depending on the viewing time of the live video.
As an example of an effect of the embodiment obtained by such a configuration, but not limited to, it is possible to give more first points to a user of a terminal as the viewing time of a live video is longer.

Also in this case, viewer behavior may include ratings or comments on the live video.
As an example of an effect of an embodiment obtained by such a configuration, a first point can be awarded to a user of a terminal based on the user's rating or comment on a live video as a viewer action.

In this case, viewer behavior may also include signing in or logging in to a live streaming application (an example of, but not limited to, authenticating a user to watch live video).
As an example of an effect of an embodiment obtained by such a configuration, first points can be awarded to a user of a terminal based on the user authentication performed by the user of the terminal to watch live video.

In this case, the server 10 can also control the control unit 11 to grant user experience points to the user of the terminal 20 when the user of the terminal 20 distributes live video.
As an example of an effect of the embodiment obtained by such a configuration, even if the user of the terminal acts as a distributor of live video, the first points can be awarded to the user of the terminal.

In this case, the server 10 may also be configured to grant the user of the terminal 20 at least the same user experience value when the user of the terminal 20 broadcasts live video for a predetermined period of time as when the user watches live video for a predetermined period of time.
As an example of the effect of an embodiment obtained by such a configuration, when a user of a terminal broadcasts a live video for a predetermined period of time, the user of the terminal can be awarded first points that are equal to or greater than the first points that would be awarded if the user watched the live video for the same predetermined period of time.

<Third Modification Example (1)>
The table in Figure 3-4 shows an example in which a live streamer bonus is awarded based on the user level, but this is not limited to this.

Specifically, by way of example and not limitation, a live streamer bonus may be awarded based on user experience points. In this case, by way of example and not limitation, the "user level" in the table in Figure 3-4 may be set as the "user experience point" and a multiplier or ratio may be appropriately set to award the live streamer bonus.

Alternatively, a live streamer bonus may be awarded based on both the user experience value and the user level. In this case, by way of example and not limitation, in the table of FIG. 3-4, the bonus awarding opportunity "at the time of live streamer registration" may be associated with a live streamer bonus "setting the live streamer experience value of [user level × C1 + user experience value × C2] as the initial value" (where C1 and C2 are non-dimensional parameters). Furthermore, the bonus awarding opportunity "during live streaming" may be associated with a live streamer bonus "multiplying [live streamer experience value according to streaming performance] by (100 + [user level] + [user experience value] × C3)%" (where C3 is a parameter that matches the user experience value to the user level dimension).
However, these are merely examples and the present invention is not limited to these calculation formulas.

Furthermore, for the bonus grant opportunity "at the time of liver registration," the liver level may be determined directly based on the user level. As a non-limiting example, if the user level is "Level 30," the initial value of the liver level may be set to "Level 10," which is the level within the liver rank "Rookie," and if the user level is "Level 60," the initial value of the liver level may be set to "Level 10," which is the liver rank "Regular."
In this case, the user may be given a live streamer experience value according to the determined live streamer level.

Similarly, for the bonus grant opportunity "during live streaming," the liver level may be determined directly based on the user level. As a non-limiting example, if the user level is "Level 100 or higher," the liver level may be increased by "1" when the liver level (level within the rank) increases during live streaming, and if the user level is "Level 200 or higher," the liver level may be increased by "2" when the liver level increases during live streaming.
In this case, the user may be given a live streamer experience value according to the determined live streamer level.

According to the above embodiment and this modified example, the server 10 (not limited to, an example of an information processing device) communicating with the terminal 20 to which the live video is distributed controls, via the control unit 11, to grant a user experience value (not limited to, an example of a first point) to the user of the terminal 20 when a viewer behavior is performed on the terminal 20. The server 10 also controls, via the control unit 11, to improve the user level (not limited to, an example of a first level) of the user of the terminal 20 based on an increase in the user experience value. When the user of the terminal 20 becomes a broadcaster of the live video, the server 10 can control, via the control unit 11, to determine the live streamer level (not limited to, an example of a second level) of the user of the terminal 20 based on at least one of the user experience value (not limited to, an example of a first point) and the user level (not limited to, an example of the first level).
As an example of an effect of an embodiment obtained by such a configuration, the second level at which a terminal user becomes a broadcaster of live video is determined based on at least one of the first points and the first level, thereby effectively motivating the terminal user to convert from a viewer to a broadcaster.

Furthermore, according to the above embodiment and this modified example, when a user of the terminal 20 broadcasts a live video, the server 10 controls, via the control unit 11, to grant the user of the terminal 20 a live streamer experience value (not limited to, an example of second points) different from the user experience value, based at least on the broadcasting performance of the live video. Furthermore, the server 10 controls, via the control unit 11, to improve the live streamer level (not limited to, an example of second level) of the user of the terminal 20 based on an increase in the live streamer experience value. The live streamer experience value can be based on the broadcasting performance of the live video and at least one of the user experience value (not limited to, an example of first points) and the user level (not limited to, first level).
As an example of an effect obtained by this configuration, second points different from the first points can be awarded to a terminal user based on the distribution record of live video content, and the second level of the terminal user can be improved based on an increase in the second points. Meanwhile, since the second points are based on the distribution record of live video content and at least one of the first points and the first level, the second points are awarded taking into consideration not only the distribution record of live video content but also the first points and the first level, which makes it possible to more effectively motivate the terminal user to convert from a viewer to a broadcaster.

Furthermore, according to the above-described embodiment and this modified example, the server 10 (not limited to, an example of an information processing device) communicating with the terminal 20 to which the live video is distributed controls, via the control unit 11, to grant a user experience value (not limited to, an example of a first point) to the user of the terminal 20 when a viewer behavior is performed on the terminal 20. The server 10 also controls, via the control unit 11, to improve the user level (not limited to, an example of a first level) of the user of the terminal 20 based on an increase in the user experience value. The server 10 also controls, via the control unit 11, to grant a live streamer experience value (not limited to, an example of a second point) different from the user experience value to the user of the terminal 20 based at least on the distribution performance of the live video when the user of the terminal 20 distributes a live video. The server 10 also controls, via the control unit 11, to improve the live streamer level (not limited to, an example of a second level) of the user of the terminal 20 based on an increase in the live streamer experience value. In this case, the live streamer experience points can be based on the live video distribution record and at least one of the user experience points (not limited, an example of the first point) and the user level (not limited, the first level).
As an example of the effect of this embodiment obtained by such a configuration, it is possible to effectively motivate terminal users to change from viewers to distributors.

According to this embodiment and this modified example, user experience points and user levels, which are configured separately from live streamer experience points and live streamer levels, can be used to convert viewers to live streamers. In other words, by awarding live streamer bonuses based on user experience points and user levels, it is possible to make it easier to improve the live streamer level of users who have converted to live streamers.

<Other Examples>
(1) Information Processing Device In the above embodiment, the information processing device in the present disclosure has been described as the server 10, but is not limited to this.

Instead of using a single server 10, the server 10 may be divided into multiple servers, each of which may serve as an information processing device according to the present disclosure.

In addition, instead of a server, a terminal such as a management computer or a management smartphone that communicates with the terminal performing live streaming (the terminal of the user performing live streaming) may also be used as the information processing device in this disclosure.

Furthermore, a system including multiple information processing devices may be configured, and this system may perform the various processes of the server 10 described in the above embodiment.

(2) Benefits and Rewards Similar to the benefits given to users based on their live streamer experience points and live streamer levels, users may be given benefits and rewards based on their user experience points and user levels.

By way of example and not limitation, in addition to the badges mentioned above as user titles, objects such as frames and personal page backgrounds may also be similarly assigned.

Furthermore, for liver ranks below the highest liver rank "God," the aforementioned seasonal rankings may be similarly constructed, and seasonal rewards may be awarded to users.

Similarly, seasonal rankings may be created for user levels, and seasonal rewards may be awarded to users.

In addition, the benefits and rewards granted to users based on their user experience points and user level may be relatively less than the benefits and rewards granted to live streamers.

(3) Display Mode of Icons FIG. 4A is a diagram showing an example of a table for explaining display modes of icons related to users.
The combinations shown here are only a few examples.

This table shows, by way of example and not limitation, associations between combinations, profile icons, user icons, and live streamer icons. In this example, nine combinations, from "1" to "9," are included.

Profile icons are as described above.

The "user icon" in this table may be, by way of example and not limitation, an icon of the user displayed in conjunction with an activity related to the user experience points or user level, or an icon of the user displayed when the user level is increased. By way of example and not limitation, this may include at least one of the following:
・An icon that is displayed in association with a user's comment when the user posts a comment while watching a live stream as a viewer. ・An icon that is displayed on the user level-up screen when the user level-up

The "liver icon" in this table can be, by way of example and not limitation, an icon of the user (liver) that is displayed in conjunction with their activities as a live streamer, or an icon of the user (liver) that is displayed when their live streamer level is increased. For example and not limitation, this can include at least one of the following:
・An icon that will be displayed in association with a comment sent by a user while streaming a live stream as a live streamer. ・An icon that will be displayed on the live stream screen while a user is streaming a live stream as a live streamer. ・An icon that will be displayed on the live stream level-up screen when a user levels up.

In this table, for each combination, a combination of a profile icon, a user icon, and each image to be displayed as a live streamer icon is set.
The "base image" in the table is as described above.

The "Base Image (Liver Experience Below Standard)" set as the Liver Icon for Combination "1" means that if the Liver Experience is below standard, the Liver's streaming performance as a Liver is poor, and therefore the "Base Image" will be displayed as the Liver Icon.

In this example, "objects according to user experience points" are objects that are given as benefits to users based on their user experience points (or user level), and can include, by way of example and not limitation, the aforementioned "badges as user titles" (which are different from the aforementioned "rank badges"), etc.

In addition, in this example, "objects according to liver experience points" are objects that are given as benefits to users based on their liver experience points (or liver level), and can include, by way of example and not limitation, the aforementioned "rank badges," "frames," "my page backgrounds," "earned titles," "trophies," etc.

Note that when a user icon is referred to as a "base image," it can mean either a case where an object corresponding to the user's experience level is not provided as a specification, or a case where an object corresponding to the user's experience level is provided as a specification, but the object is not added because the user's experience level is below a certain level.

Also, as mentioned above, a user's user level may increase as they engage in live streamer activities. In this case, the user icon shown in the "User Icon" column of the table in Figure 4-1 can be displayed.

Alternatively, none of the profile icon, user icon, or live streamer icon may be changed (all may remain as the base image).

(4) Experience Points Based on Live Streaming In the above embodiment, when a user of a terminal performs live streaming, user experience points may not be awarded.

(5) User Rank In the above embodiment, a user rank may be set similarly to the driver rank.
Furthermore, within each user rank, a corresponding intra-rank level may be provided.

(6) Level Reduction In the above embodiment, the information processing device may be configured to perform control to lower the level of the distributor when a predetermined condition is met. The points of the distributor may then be reduced in accordance with the reduced level. That is, the points reduction and the level reduction may be performed first, or they may be performed simultaneously.

It is also possible to prevent a streamer's points from decreasing when their level is lowered.

It may also be possible to reduce the streamer's points or lower the streamer's level, or both.

(7) Points In the above embodiment, experience points are used as an example of points, but other units may be used. In other words, any value that is given to a terminal user based on distribution or viewing may be used, and the value does not necessarily have to be in the unit of experience points.

(8) Others As mentioned above, the contents explained in the above-mentioned embodiments, modifications, other embodiments, etc. can be applied in combination with each other.

1 Communication system 10 Server 20 Terminal 30 Network

Claims (18)

A program executed by an information processing device that communicates with a terminal of a distributor who distributes live video,
controlling a control unit of the information processing device to award points to the distributor based on the distribution performance of the live video;
The control unit controls the level of the distributor to be improved based on an increase in points given to the distributor.
When a predetermined condition is met, the control unit controls to decrease the points given to the distributor;
performing control by the control unit to lower the level of the distributor based on a decrease in points granted to the distributor;
Includes
The program, wherein the predetermined condition includes at least one of the following: a user whose season ranking in the previous season was at or above a predetermined rank has acquired a liver experience value equal to or greater than a set value since the start of this season; and a user whose season ranking in the previous season was at or above a predetermined rank has increased in liver experience value by more than a set percentage from the liver experience value at the start of this season . A program executed by an information processing device that communicates with a terminal of a distributor who distributes live video,
controlling a control unit of the information processing device to award points to the distributor based on the distribution performance of the live video;
The control unit controls the level of the distributor to be improved based on an increase in points given to the distributor.
When a predetermined condition is met, the control unit controls to decrease the points given to the distributor;
performing control by the control unit to lower the level of the distributor based on a decrease in points granted to the distributor;
Including,
the control of awarding the points is performed by the control unit during distribution of the live video;
The control for increasing the level is performed by the control unit while the live video is being distributed . 3. The program according to claim 1 or 2,
When the level of the distributor exceeds a predetermined level, the amount of reduction in points given to the distributor is smaller than when the level does not exceed the predetermined level.
program. The program according to any one of claims 1 to 3,
The fulfillment of the predetermined condition includes the passage of a predetermined period of time.
program. 5. The program according to claim 4,
When the points granted to the distributor within the predetermined period exceed a predetermined number of points, the amount of reduction in the points granted to the distributor is smaller than when the points do not exceed the predetermined number of points.
program. 6. The program according to claim 4 or claim 5,
and performing control by the control unit to grant a benefit to the distributor when a ranking based on points granted to the distributor within the predetermined period is higher than a predetermined ranking.
program. 7. The program according to claim 6,
and performing control by the control unit to grant the benefit to the distributor based on the total of points granted to the distributor within the predetermined period and points granted to the distributor outside the predetermined period, in both cases where the ranking is higher than the predetermined ranking and where the ranking is not higher than the predetermined ranking.
program. 8. The program according to claim 7,
the reward granted when the ranking is higher than the predetermined ranking is greater than the reward granted to the distributor based on the total;
program. The program according to any one of claims 1 to 8,
a plurality of ranks including at least a first rank and a second rank higher than the first rank are provided as ranks of the distributors, and a plurality of levels are provided corresponding to the plurality of ranks, respectively;
The rank of the distributor is improved to the second rank based on the points granted to the distributor exceeding the points corresponding to the highest level in the first rank;
When the rank of the distributor is the second rank, the level of the distributor in the second rank is improved based on an increase in points granted to the distributor.
program. 10. The program according to claim 9,
When the rank of the distributor is the first rank, control to reduce the points granted to the distributor based on the establishment of the predetermined condition is not performed;
When the rank of the distributor is the second rank, a control is performed to decrease the points granted to the distributor based on the establishment of the predetermined condition, and a control is performed to lower the level of the distributor based on the decrease of the points granted to the distributor.
program. The program according to claim 10,
When the predetermined condition is met, the rank of the distributor does not drop from the second rank to the first rank.
program. The program according to any one of claims 1 to 11,
and controlling the control unit to grant a benefit to the distributor,
The reward associated with the benefit varies depending on the distributor.
program. An information processing method of an information processing device that communicates with a terminal of a distributor who distributes live video, comprising:
controlling a control unit of the information processing device to award points to the distributor based on the distribution performance of the live video;
The control unit controls the level of the distributor to be improved based on an increase in points given to the distributor.
When a predetermined condition is met , the control unit controls to decrease the points given to the distributor;
performing control by the control unit to lower the level of the distributor based on a decrease in points granted to the distributor;
Including,
The information processing method includes the predetermined condition including at least one of the following: a user whose season ranking in the previous season was at or above a predetermined rank has acquired a liver experience value equal to or greater than a set value since the start of this season; and a user whose season ranking in the previous season was at or above a predetermined rank has increased in liver experience value by more than a set percentage from the liver experience value at the start of this season. An information processing method of an information processing device that communicates with a terminal of a distributor who distributes live video, comprising:
controlling a control unit of the information processing device to award points to the distributor based on the distribution performance of the live video;
The control unit controls the level of the distributor to be improved based on an increase in points given to the distributor.
When a predetermined condition is met , the control unit controls to decrease the points given to the distributor;
performing control by the control unit to lower the level of the distributor based on a decrease in points granted to the distributor;
Including,
the control of awarding the points is performed by the control unit during distribution of the live video;
An information processing method, wherein the control to increase the level is performed by the control unit while the live video is being distributed. An information processing device that communicates with a terminal of a distributor that distributes live video,
a control unit that performs control to grant points to the broadcaster based on the broadcast performance of the live video, control to improve the level of the broadcaster based on an increase in the points granted to the broadcaster, control to decrease the points granted to the broadcaster when a predetermined condition is met , and control to lower the level of the broadcaster based on the decrease in the points granted to the broadcaster,
The specified condition includes at least one of the following: a user whose season ranking in the previous season was at or above a specified rank has acquired a liver experience value equal to or greater than a set value since the start of this season; and a user whose season ranking in the previous season was at or above a specified rank has acquired a liver experience value equal to or greater than a set percentage from the liver experience value at the start of this season. An information processing device that communicates with a terminal of a distributor that distributes live video,
a control unit that performs control to grant points to the broadcaster based on the broadcast performance of the live video, control to improve the level of the broadcaster based on an increase in the points granted to the broadcaster, control to decrease the points granted to the broadcaster when a predetermined condition is met , and control to lower the level of the broadcaster based on the decrease in the points granted to the broadcaster,
the control of awarding the points is performed by the control unit during distribution of the live video;
The control to increase the level is performed by the control unit while the live video is being distributed.

An information processing device that communicates with a terminal of a distributor that distributes live video,
A processor is provided to read a program stored in a memory and execute processing based on the program,
The processor:
Controlling the awarding of points to the distributor based on the distribution performance of the live video;
Controlling the level of the distributor to be improved based on an increase in points given to the distributor;
When a predetermined condition is met, control is performed to decrease the points given to the distributor;
performing control to lower the level of the distributor based on a decrease in the points granted to the distributor;
Run
The specified condition includes at least one of the following: a user whose season ranking in the previous season was at or above a specified rank has acquired a liver experience value equal to or greater than a set value since the start of this season; and a user whose season ranking in the previous season was at or above a specified rank has acquired a liver experience value equal to or greater than a set percentage from the liver experience value at the start of this season . An information processing device that communicates with a terminal of a distributor that distributes live video,
A processor is provided to read a program stored in a memory and execute processing based on the program,
The processor:
Controlling the awarding of points to the distributor based on the distribution performance of the live video;
Controlling the level of the distributor to be improved based on an increase in points given to the distributor;
When a predetermined condition is met, control is performed to decrease the points given to the distributor;
performing control to lower the level of the distributor based on a decrease in the points granted to the distributor;
Run
the control of awarding the points is performed by the processor during distribution of the live video;
An information processing device , wherein the control to increase the level is performed by the processor while the live video is being distributed .