Systems and methods for notifications

Abstract

As a platform for providing live streaming services, a system and method for notifying users of the services they desire are provided. [Solution] The method includes sending a first notification related to a stream to a first viewer based on a first condition, and sending a second notification related to the stream to a second viewer based on a second condition, the first condition being different from the second condition.

Description

[Technical Field]

[0001] The present invention relates to streaming, and in particular to live streaming. [Background technology]

[0002] As exemplified by live streaming services, real-time online interactions have become a part of everyday life. A variety of platforms and providers offer live streaming services, creating fierce competition. It is important for platforms to provide the services users desire.

[0003] US Patent Application Publication No. 20230353653 discloses a system for notification. Summary of the Invention

[0004] A method according to one embodiment of the present invention is a method for notifications executed by one or more computers, comprising sending a first notification related to a stream to a first viewer based on a first condition, and sending a second notification related to the stream to a second viewer based on a second condition, wherein the first condition is different from the second condition.

[0005] In one embodiment of the present invention, a system for notifications includes one or more processors that execute machine-readable instructions to send a first notification related to a stream to a first viewer based on a first condition, and send a second notification related to the stream to a second viewer based on a second condition, wherein the first condition is different from the second condition.

[0006] A non-transitory computer-readable medium containing a program for notifications, the program causing one or more computers to send a first notification related to a stream to a first viewer based on a first condition, and a second notification related to the stream to a second viewer based on a second condition, wherein the first condition is different from the second condition. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a schematic diagram illustrating the configuration of a live streaming system 1 according to some embodiments of the present invention. [Figure 2] 2 is a block diagram illustrating the functionality and configuration of user terminal 30 of FIG. 1 in accordance with some embodiments of the present invention. [Figure 3] 2 is a block diagram illustrating the functionality and configuration of the server of FIG. 1 in accordance with some embodiments of the present invention. [Figure 4] 4 is a table illustrating an exemplary data structure of the stream DB 310 of FIG. 3. [Figure 5] 4 is a table illustrating an exemplary data structure of the user DB 312 of FIG. 3. [Figure 6] 4 is a table illustrating an example data structure of the gift DB 314 of FIG. 3. [Figure 7] 10 is a table illustrating an example data structure of a push notification DB 330. [Figure 8] 10 is a table illustrating an example data structure of a push notification DB 330. [Figure 9] 10 is a table illustrating an example data structure of a push notification DB 330. [Figure 10] 10 is a table illustrating an example data structure of a push notification strategy DB 332. [Figure 11] 10 is a table illustrating an example data structure of a push notification strategy DB 332. [Figure 12] 10 is a table illustrating an example data structure of a push notification strategy DB 332. [Figure 13] 1 illustrates an exemplary flow according to some embodiments of the present invention. [Figure 14] 10 is a table illustrating an example data structure of a push notification strategy DB 332. [Figure 15] 10 is a table illustrating an example data structure of a push notification DB 330. [Figure 16] FIG. 1 is a schematic diagram illustrating an exemplary notification in accordance with some embodiments of the present invention. [Figure 17] FIG. 1 is a schematic diagram illustrating an exemplary notification in accordance with some embodiments of the present invention. [Figure 18] 1 is a block diagram showing an example of a hardware configuration of an information processing device according to some embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the same or similar components, parts, steps, or signals shown in each drawing will be denoted by the same reference numerals in all drawings, and redundant explanations will be omitted as appropriate. In addition, some parts that are not important in the explanation of each drawing will be omitted.

[0009] Notifications on streaming platforms are an important feature to motivate or alert viewers to engage with the stream, so it is desirable for platforms to have efficient and optimal notification features.

[0010] FIG. 1 is a schematic diagram illustrating the configuration of a live streaming system 1 according to some embodiments of the present invention. The live streaming system 1 provides a live streaming service for streaming streamers (also referred to as livestreamers, anchors, distributors, or livestreamers) LV and viewers (also referred to as audiences) AU (AU1, AU2, ...) to interact or communicate in real time. As shown in FIG. 1, the live streaming system 1 includes a server 10, a user terminal 20, and a user terminal 30 (30a, 30b, ...). In some embodiments, the streamers and viewers may be collectively referred to as users. The server 10 may include one or more information processing devices connected to a network NW. The user terminals 20 and 30 may be, for example, mobile terminal devices such as smartphones, tablets, laptops, recorders, portable game consoles, and wearable devices, or stationary devices such as desktop PCs. The server 10, the user terminals 20, and the user terminals 30 are connected to each other so as to be able to communicate with each other via various wired or wireless networks NW.

[0011] The live streaming system 1 includes a broadcaster LV, a viewer AU, and an administrator (or app provider, not shown) who manages the server 10. The broadcaster LV records content on his / her user terminal 20 and directly or indirectly uploads it to the server 10, thereby broadcasting the content in real time. Examples of the content include the broadcaster's own singing, talking, performance, gameplay, or any other content. The administrator provides a platform for live streaming the content on the server 10 and mediates or manages real-time interactions between the broadcaster LV and the viewer AU. The viewer AU accesses the platform with his / her user terminal 30, selects and watches desired content, and performs operations such as leaving comments, cheering, or sending gifts via the user terminal 30 during the live streaming of the selected content. The broadcaster LV, who is broadcasting the content, may respond to the comments, cheers, or gifts. The response is transmitted to the viewer AU via video and / or audio, establishing two-way communication.

[0012] The term "live streaming" may refer to a data transmission mode that allows content recorded by a user terminal 20 of the distributor LV to be played back and viewed on a user terminal 30 of the viewer AU in substantially real time, or may refer to live broadcasting realized by such a transmission mode. The live streaming may be realized using existing live streaming technologies such as HTTP live streaming, CMAF (Common Media Application Format), WebRTC (Web Real-Time Communications), RTMP (Real-Time Messaging Protocol), etc. Live streaming includes a transmission mode that allows the viewer AU to view content simultaneously with a predetermined delay as the content is recorded by the distributor LV. The delay may be long enough to allow interaction between the distributor LV and the viewer AU. Note that live streaming is distinguished from so-called on-demand distribution, in which all recorded data of the content is stored on a server and then provided to users from the server upon their request.

[0013] The term "video data" as used herein refers to data including image data (also referred to as video data) generated using the imaging function of the user terminal 20 or 30 and audio data generated using the audio input function of the user terminal 20 or 30. The video data is played on the user terminal 20 or 30 so that the user can view the content. In some embodiments, it is assumed that processing to change the format, size, or data specifications of the video data, such as compression, decompression, encoding, decoding, or transcoding, is performed on the video data between the generation of the video data on the distributor's user terminal and the playback of the video data on the viewer's user terminal. However, since the content (e.g., video and audio) represented by the video data remains substantially unchanged before and after such processing, the video data after such processing is referred to herein as being identical to the video data before such processing. In other words, when video data is generated on the distributor's user terminal and then played on the viewer's user terminal via the server 10, the video data generated on the distributor's user terminal, the video data passing through the server 10, and the video data received and played on the viewer's user terminal are all the same video data.

[0014] In the example shown in Fig. 1, the distributor LV provides live streaming data. The user terminal 20 of the distributor LV records video and audio of the distributor LV to generate the streaming data, and the generated data is transmitted to the server 10 via the network NW. At the same time, the user terminal 20 displays the recorded video VD of the distributor LV on the display of the user terminal 20, allowing the user to check the live streaming content currently being produced by the distributor LV.

[0015] The user terminals 30a and 30b of the viewers AU1 and AU2 who have requested to view the live streaming of the distributor LV on the platform receive video data related to the live streaming (hereinafter, may be referred to as "live streaming video data") via the network NW, play the received video data, display the videos VD1 and VD2 on the display, and output audio from speakers. The videos VD1 and VD2 displayed on the user terminals 30a and 30b are substantially the same as the video VD captured by the user terminal 20 of the distributor LV, and the audio output from the user terminals 30a and 30b is substantially the same as the audio recorded by the user terminal 20 of the distributor LV.

[0016] The recording of video and audio on the user terminal 20 of the distributor LV and the playback of video data on the user terminals 30a and 30b of the viewers AU1 and AU2 are performed substantially simultaneously. When the viewer AU1 inputs a comment about the content provided by the distributor LV to the user terminal 30a, the server 10 displays the comment in real time on the user terminal 20 of the distributor LV and also displays the comment on the user terminals 30a and 30b of the viewers AU1 and AU2, respectively. When the distributor LV reads the comment and engages in a conversation corresponding to the comment, the video and audio of the conversation are displayed on the user terminals 30a and 30b of the viewers AU1 and AU2, respectively. This interactive behavior is recognized as a conversation between the distributor LV and the viewer AU1. This allows the live streaming system 1 to realize live streaming that enables two-way communication rather than one-way communication.

[0017] FIG. 2 is a block diagram illustrating the functions and configuration of the user terminal 30 of FIG. 1 according to some embodiments of the present invention. The user terminal 20 has the same or similar functions and configuration as the user terminal 30. Each block in FIG. 2 and the subsequent block diagrams may be realized by hardware elements such as a computer CPU or a mechanical device, or by software elements such as a computer program. The functional blocks may be realized by cooperative operations between these elements. Therefore, those skilled in the art will understand that these functional blocks may be realized in various forms using a combination of hardware and software.

[0018] The distributor LV and the viewer AU may download a live streaming application program (hereinafter referred to as a live streaming application) from a download site via the network NW and install it on the user terminals 20 and 30. Alternatively, the live streaming application may be pre-installed on the user terminals 20 and 30. When the live streaming application is executed on the user terminals 20 and 30, the user terminals 20 and 30 communicate with the server 10 via the network NW and implement or execute various functions. Hereinafter, functions implemented by the user terminals 20 and 30 (processors such as CPUs) on which the live streaming application is executed are described as functions of the user terminals 20 and 30. These functions are actually realized by the live streaming application on the user terminals 20 and 30. In some embodiments, these functions may be written in a programming language such as HTML (HyperText Markup Language), transmitted from the server 10 to a web browser on the user terminals 20 and 30 via the network NW, and implemented by a computer program executed by the web browser.

[0019] The user terminal 30 includes a distribution unit 100 and a viewing unit 200. The distribution unit 100 generates video data in which the video and audio of the user (or user side) are recorded, and provides the video data to the server 10. The viewing unit 200 receives the video data from the server 10 and plays the video data. The user starts the distribution unit 100 when performing live streaming, and starts the viewing unit 200 when viewing video. The user terminal on which the distribution unit 100 is started is the distributor's terminal, i.e., the user terminal that generates the video data. The user terminal on which the viewing unit 200 is started is the viewer's terminal, i.e., the user terminal on which the video data is reproduced and played.

[0020] The distribution unit 100 includes an imaging control unit 102, an audio control unit 104, a video transmission unit 106, and a distributor-side UI control unit 108. The imaging control unit 102 is connected to a camera (not shown in FIG. 2) and controls imaging performed by the camera. The imaging control unit 102 acquires image data from the camera. The audio control unit 104 is connected to a microphone (not shown in FIG. 2) and controls audio input from the microphone. The audio control unit 104 acquires audio data from the microphone. The video transmission unit 106 transmits video data including the image data acquired by the imaging control unit 102 and the audio data acquired by the audio control unit 104 to the server 10 via the network NW. The video data is transmitted in real time by the video transmission unit 106. That is, the generation of the video data by the imaging control unit 102 and the audio control unit 104 and the transmission of the generated video data by the video transmission unit 106 are performed substantially simultaneously. The distributor-side UI control unit 108 controls the UI (user interface) of the distributor. The distributor-side UI control unit 108 may be connected to a display (not shown in FIG. 2 ) and displays a video on the display by playing the video data transmitted by the video transmission unit 106. The distributor-side UI control unit 108 may display an operation object or an instruction permission object on the display and receive input from the distributor who taps on the object.

[0021] The viewing unit 200 includes a viewer-side UI control unit 202, an overlay information generation unit 204, and an input information transmission unit 206. The viewing unit 200 receives video data related to live streaming, in which the broadcaster, the viewer who is the user of the user terminal 30, and other viewers participate, from the server 10 via the network NW. The viewer-side UI control unit 202 controls the viewer's UI. The viewer-side UI control unit 202 is connected to a display and a speaker (not shown in FIG. 2 ) and plays the received video data, displays the video on the display, and outputs the audio from the speaker. The state in which the video is output to the display and the audio is output from the speaker can be referred to as a state in which the video data is being played. The viewer-side UI control unit 202 is also connected to an input means (not shown in FIG. 2 ), such as a touch panel, keyboard, or display, and acquires user input via the input means. The overlay information generation unit 204 overlays a predetermined frame image on an image generated from video data from the server 10. The frame image includes various user interface objects (hereinafter simply referred to as "objects") for receiving input from the user, comments entered by the viewer, and / or information acquired from the server 10. The input information transmission unit 206 transmits the user input acquired by the viewer-side UI control unit 202 to the server 10 via the network NW.

[0022] 3 is a block diagram illustrating the functions and configuration of the server 10 of FIG. 1 according to some embodiments of the present invention. The server 10 includes a distribution information providing unit 302, a relay unit 304, a gift processing unit 306, a payment processing unit 308, a stream DB 310, a user DB 312, a gift DB 314, an acquisition unit 320, a processing unit 322, a push notification DB 330, a push notification strategy DB 332, and a machine learning DB 334.

[0023] When receiving a notification or request to start live streaming from the user terminal 20 on the distributor side via the network NW, the distribution information providing unit 302 registers in the stream DB 310 a stream ID for identifying this live streaming and the distributor ID of the distributor performing the live streaming.

[0024] When the distribution information providing unit 302 receives a request for information about live streams from the viewing unit 200 of the user terminal 30 on the viewer side via the network NW, the distribution information providing unit 302 obtains or checks currently available live streams from the stream DB 310 and creates a list of available live streams. The distribution information providing unit 302 sends the created list to the requesting user terminal 30 via the network NW. The viewer-side UI control unit 202 of the requesting user terminal 30 generates a live stream selection screen based on the received list and displays it on the display of the user terminal 30.

[0025] When the input information sending unit 206 of the user terminal 30 receives the viewer's selection on the live stream selection screen, the input information sending unit 206 generates a delivery request including the stream ID of the selected live stream and sends the request to the server 10 via the network NW. The delivery information providing unit 302 starts providing the live stream specified by the stream ID included in the received delivery request to the requesting user terminal 30. The delivery information providing unit 302 updates the stream DB 310 so that the viewer ID of (or the corresponding) the stream ID includes the user ID of the viewer of the requesting user terminal 30.

[0026] The relay unit 304 relays the video data from the user terminal 20 on the broadcaster side to the user terminal 30 on the viewer side during the live streaming initiated by the broadcast information providing unit 302. The relay unit 304 receives a signal representing a user input by a viewer from the input information transmitting unit 206 during the live streaming or playback of the video data. The signal representing the user input may be an object designation signal that designates an object displayed on the display of the user terminal 30. The object designation signal may include the viewer ID of the viewer, the broadcaster ID of the broadcaster of the live stream being viewed by the viewer, and an object ID that identifies the object. When the object is a gift, the object ID is a gift ID. Similarly, the relay unit 304 receives a signal representing a user input made by a broadcaster during playback of the video data (or during live streaming) from the broadcast unit 100 of the user terminal 20. The signal may be an object designation signal.

[0027] Furthermore, the signal representing the user input may be a comment input signal containing a comment entered by the viewer into the user terminal 30 and the viewer ID of the viewer. Upon receiving the comment input signal, the relay unit 304 transmits the comment and the viewer ID contained in the signal to the user terminal 20 of the distributor and the user terminals 30 of other viewers. In these user terminals 20, 30, the viewer-side UI control unit 202 and the overlay information generation unit 204 display the received comment on a display associated with the received viewer ID.

[0028] The gift processing unit 306 increases the points of the broadcaster based on the points of the gift identified by the gift ID included in the object designation signal, and updates the user DB 312. Specifically, the gift processing unit 306 refers to the gift DB 314 to identify points to be assigned to the gift ID included in the received object designation signal. Then, the gift processing unit 306 updates the user DB 312 and adds the identified points to the points of the broadcaster ID (or corresponding to the broadcaster ID) included in the object designation signal.

[0029] In response to receiving the object designation signal, the payment processing unit 308 processes payment for the gift from the viewer. Specifically, the payment processing unit 308 refers to the gift DB 314 to determine the price points of the gift identified by the gift ID included in the object designation signal. Then, the payment processing unit 308 updates the user DB 312 and subtracts the determined price points from the points of the viewer identified by the viewer ID included in the object designation signal.

[0030] FIG. 4 is a table illustrating an exemplary data structure of the stream DB 310 in FIG. 3. The stream DB 310 holds information about currently running live streams. The stream DB 310 stores a stream ID, a broadcaster ID, and a viewer ID in association with each other. The stream ID is an ID for identifying a live stream in the live streaming platform provided by the live streaming system 1. The broadcaster ID is a user ID for identifying the broadcaster who provides the live stream. The viewer ID is a user ID for identifying a viewer of the live stream. In the live streaming platform provided by the live streaming system 1 according to some embodiments, when a user starts a live stream, the user becomes a broadcaster, and when the same user watches a live stream broadcast by another user, the user also becomes a viewer. Therefore, the distinction between a broadcaster and a viewer is not fixed, and a user ID registered as a broadcaster ID at one time may be registered as a viewer ID at another time.

[0031] FIG. 5 is a table illustrating an exemplary data structure of the user DB 312 of FIG. 3. The user DB 312 holds information about users. The user DB 312 stores user IDs and points in association with each other. The user ID identifies a user. The points correspond to points held by the corresponding user. The points are electronic value circulated within the live streaming platform. In some embodiments, when a streamer receives a gift from a viewer during a live broadcast, the streamer's points increase by a value corresponding to the gift. The points are used, for example, to determine the amount of compensation (e.g., money) that the streamer receives from an administrator of the live streaming platform. In some embodiments, when the streamer receives a gift from a viewer, an amount corresponding to the gift may be given instead of the points.

[0032] FIG. 6 is a table illustrating an exemplary data structure of the gift DB 314 of FIG. 3. The gift DB 314 stores information about gifts available to the viewer during the live streaming. Gifts are electronic data. Gifts may be purchased with points or money, or may be provided free of charge. Viewers may give gifts to the broadcaster. Giving a gift to a broadcaster is also referred to as using a gift, sending a gift, or throwing a gift. Some gifts can be used immediately upon purchase, while others can be used later by the viewer who purchased them. When a viewer gives a gift to a broadcaster, the broadcaster is awarded a number of points corresponding to the gift. When a gift is used, an effect associated with the gift may be generated. For example, an effect (such as a visual or auditory effect) corresponding to the gift may be displayed on the live streaming screen.

[0033] The gift DB 314 stores gift IDs, awarded points, and price points in association with one another. The gift ID is used to identify a gift. The awarded points are the amount of points awarded to a broadcaster when the gift is given to the broadcaster. The price points are the amount of points paid for using (purchasing) the gift. While watching a live stream, a viewer can give a desired gift to a broadcaster by paying the price points of the desired gift. The price points can be paid using an appropriate electronic payment method. For example, the viewer may pay the price points to the administrator. Alternatively, payment may be made by bank transfer or credit card. The administrator can arbitrarily set the relationship between the awarded points and the price points. For example, the awarded points may be set to equal the price points. Alternatively, the price points may be set to the points obtained by multiplying the awarded points by a predetermined coefficient such as 1.2, or the price points may be set to the points obtained by adding a predetermined fee to the awarded points.

[0034] 7 is a table showing an example data structure of the push notification DB 330. The push notification DB 330 stores push notification IDs, stream IDs, broadcaster IDs, viewer IDs, push notification attribute data, and viewer interaction data in mutually associated relation with each other. The push notification DB 330 stores the values / contents of push notification attributes and the interaction results of viewers who received those push notifications.

[0035] Each push notification ID identifies one push notification. The stream ID identifies the stream that the push notification notifies. The broadcaster ID identifies the broadcaster of the stream that the push notification notifies. The viewer ID identifies the viewer to whom the push notification was sent. The push notification attribute data includes attributes of the notification, such as the push notification topic, push notification format, push notification timing, viewer status tag, and broadcaster status tag. The push notification topic indicates the topic of the stream mentioned in the notification, and may be the topic of the stream detected in real time. The push notification format indicates the format in which the notification is presented to the viewer. The push notification timing indicates the timing (or time range) at which the push notification is sent to the viewer. The viewer status tag indicates the viewer's status at (or just before) receiving the push notification. The broadcaster status tag indicates the broadcaster's status for the stream at (or just before) sending the push notification.

[0036] The viewer interaction data includes the viewer's interaction results, such as click results and engagement results, related to the notification.

[0037] 8 is a table showing an example data structure of the push notification DB 330. Examples of attributes and their potential values ​​(or conditions / classifications / types / contents) for each push notification are specified. The values ​​may be recorded in the push notification DB 330 as shown in FIG. 7.

[0038] The push notification topic may record a topic detected from the stream corresponding to the notification. The topic may be detected at (or immediately before) the time of sending the notification. The topic may be detected or determined by the processing unit 322 and / or the machine learning DB 334. For example, the machine learning DB 334 may include an image detection model, a video detection model, or an audio detection model that can be used to analyze the topic of the stream.

[0039] For such push notification formats, the notifications may have text, image, or video formats. In some embodiments, the video and / or image formats may include text.

[0040] The push notification timing may be morning, noon, evening, etc. In some embodiments, the exact timing of the push notification transmission may be recorded. In some embodiments, whether the viewer receiving the notification is in a working or non-working time (which may be determined, for example, from the user's profile or history) may also be recorded.

[0041] The viewer status tag may record whether the notified viewer is in a live stream room when receiving the push notification. If the viewer is in a live stream room, the viewer's engagement level (or real-time engagement level at the time of receiving the push notification) may also be recorded. The engagement level may be analyzed by the processing unit 322 and / or the machine learning DB 334 using the viewer's behavior in the stream room (e.g., comments, gift giving, etc.). Whether the viewer is in a live stream room or engaged in a live stream room may affect the viewer's response to a newly received push notification.

[0042] The streamer status tag may record the streamer's mood (or engagement level). For example, the processing unit 322 may use the machine learning DB 334 to analyze real-time image / video / audio data from the stream room to determine the streamer's mood. This data may be used to determine the streamer's impact on each viewer who clicked on the push notification.

[0043] The push notification attribute data may include other attributes such as the length of the push notification content and the mood of the push notification. The value of the length of the push notification content may be short or long based on the length of the push notification content. The mood of the push notification may be classified / analyzed as "calm," "high-tension," "low-tension," etc. Mood classification may be performed by the processing unit 322 using the machine learning DB 334. For example, the mood of a push notification may be obtained by inputting the push notification content into the machine learning DB 334.

[0044] 9 is a table showing an example data structure of the push notification DB 330. Examples of each interaction data (or numerical value) and its possible values ​​(or conditions / categories / types / contents) are shown. The values ​​may be recorded in the push notification DB 330 as shown in FIG. 7.

[0045] The click result indicates or records whether the viewer clicked (or selected) the push notification. If the viewer clicked on the push notification, the retention result indicates or records the viewer's time spent in the stream corresponding to the push notification. In some embodiments, the retention result may store the exact length of time the viewer spent in the stream.

[0046] 10 is a table illustrating an exemplary data structure of the push notification strategy DB 332. The push notification strategy DB 332 stores viewer IDs and optimal push notification attribute conditions (or notification attribute conditions) in correlation with each other. The optimal push notification attribute conditions store optimal conditions for various push notification attributes for each viewer. "Optimal" refers to conditions that may result in the corresponding viewer tending to click on a notification and / or tending to stay in the stream room for a long time after clicking on the notification.

[0047] For example, in the case of viewer V1, a notification with the following conditions is more likely to be clicked or selected: [push notification topic = "game", push notification format = "image", push notification timing = "night", viewer status tag = "outside stream"]. For example, in the case of viewer V1, a notification with the following condition is more likely to result in the viewer staying in the stream room longer after being clicked or selected: [broadcaster status tag = "high tension"].

[0048] The optimal conditions in the push notification strategy DB 332 may be calculated by the processing unit 322 and / or the machine learning DB 334 based on data in the push notification DB 330. For example, for each viewer, the probability of each condition for each push notification attribute leading to a successful click may be calculated. The optimum condition for each push notification attribute may be determined as appropriate.

[0049] FIG. 11 is a table illustrating an exemplary data structure of the push notification strategy DB 332. For each viewer, a click rate for each condition of the push notification attribute "viewer status tag" may be calculated. This calculation may be performed using various known statistical methods based on the push notification DB 330. As shown in the figure, when viewer V1 is not in any live stream, the notification is most likely to be clicked by viewer V1 (click rate 76%). When viewer V1 is in a live stream, the viewer V1 is more likely to click the notification when his / her engagement in the stream is low (click rate 47%). When viewer V1's engagement in the live stream is high, viewer V1 tends to ignore the notification (click rate 14%).

[0050] 14 is a table showing an exemplary data structure of the push notification strategy DB 332. For each viewer, the click rate for each condition of the push notification attribute "push notification format" is calculated. This calculation may be performed using various known statistical methods based on the push notification DB 330. As shown in the figure, a video format notification is clicked by viewer V1 with an 81% probability. An image format notification is clicked by viewer V1 with a 58% probability. A text format notification is clicked by viewer V1 with a 38% probability.

[0051] 12 is a table showing an exemplary data structure of the push notification strategy DB332. For each viewer, the average retention time (after clicking the notification and joining the stream) for each condition of the push notification attribute "broadcaster status tag" is calculated. This calculation may be performed using various known statistical methods based on the push notification DB330. As shown in the figure, when viewer V1 clicks the notification to join the stream and the broadcaster is "high-energy," the average retention time is the longest (11 minutes). When viewer V1 clicks the notification to join the stream and the broadcaster is "low-energy," the average retention time is 6 minutes. When the broadcaster is "calm," viewer V1's retention time is the shortest (1 minute).

[0052] The machine learning DB 334 may store various machine learning models or AI models. For example, one or more large-scale language models (LLMs) may be included in the machine learning DB 334. Various topic detection models may be implemented in the machine learning DB 334.

[0053] FIG. 13 illustrates an exemplary flow according to some embodiments of the present invention.

[0054] In step S1300, the acquiring unit 320 acquires the push notification attribute data and viewer interaction data. According to different embodiments, these data may be acquired from within the server 10 or from a monitoring unit / service outside the server 10.

[0055] In step S1302, the processing unit 322 and / or the machine learning DB 334 determines optimal push notification attribute conditions for each viewer. The optimal push notification attribute conditions may include, for example, an optimal push notification topic, an optimal push notification format, an optimal push notification timing, an optimal viewer status tag, and / or an optimal publisher status tag for each viewer. This determination (or calculation) may be made based on the push notification DB 330 and may be stored in the push notification strategy DB 332.

[0056] In step S1304, the stream (or live stream) is started by the broadcaster.

[0057] In step S1306, the acquiring unit 320 acquires the latest attribute data of notifications (or candidate notifications or notifications in preparation) related to the stream and the viewer. The candidate notifications may be associated with the stream and the viewer, or may be associated with the viewer and the stream's broadcaster. For example, the viewer may be a follower of the broadcaster. For example, the stream platform determines that the viewer is a legitimate (or eligible) recipient of notifications related to the stream (or the broadcaster) based on a specific matching algorithm (such as affinity matching or topic matching). The attribute data may include, for example, the topic (or real-time topic) of the stream, the push notification format, the push notification timing, the viewer status tag, and / or the broadcaster status tag.

[0058] In step S1308, the processing unit 322 determines whether the attribute data of the candidate notification matches (or satisfies) one or more optimal notification conditions for the viewer. The definition of "satisfying the optimal conditions" may be defined in various ways depending on the actual operation. If "yes," the flow proceeds to step S1310. If not, the flow returns to step S1306 to continue monitoring the attribute data (or continue acquiring new attribute data).

[0059] In step S1310, the processing unit 322 generates the notification based on the optimal attribute conditions.

[0060] In step S1312, the processing unit 322 sends the notification to the viewer based on the optimal attribute conditions, after which the flow returns to step S1300.

[0061] For example, in step S1302, the optimal push notification attribute conditions for viewer V1 are determined as [push notification topic="Game", push notification format="Image", push notification timing="Night", viewer status tag="Off-Stream", broadcaster status tag="High Enthusiasm"]. The optimal push notification attribute conditions for viewer V2 are determined as [push notification topic="Vocal / Guitar", push notification format="Video", push notification timing="Night", viewer status tag="In-Stream, Low Engagement", broadcaster status tag="High Enthusiasm"]. In step S1304, stream S1 of broadcaster D1, who is followed by both viewer V1 and viewer V2, is started.

[0062] At timing (or time span) t1, in step S1306, the topic of the stream is detected as "Gaming" and the broadcaster status tag is detected as "High Tension." In step S1308, it is determined that sufficient optimal conditions are met for viewer V1 (but not for viewer V2). In step S1310, a notification is generated with the text "D1 is playing a game!" along with an image clipped from the stream room. In step S1312, the notification is sent to viewer V1 so that the image and text are displayed to viewer V1.

[0063] At timing (or time span) t2, in step S1306, the topic of the stream is detected as "guitar" (the stream topic has changed from "games" to "guitar"), and the viewer status tag of viewer V2 is detected as "in stream and low engagement." In step S1308, it is determined that sufficient optimal conditions are met for viewer V2. In step S1310, a notification having the text "D1 is playing guitar!" is generated along with the video clipped from the stream room. In step S1312, the notification is sent to viewer V2 so that the video and the text are displayed to viewer V2.

[0064] As mentioned above, the content (text content), format, and / or timing of notifications for different viewers can be customized for the same stream, and the timing may depend on the status of the broadcaster and / or the status of each viewer.

[0065] 15 is a table showing an example data structure of the push notification DB 330. The push notification DB 330 stores a stream ID, a distributor ID, a notification timing, a push notification topic, a push notification content, a viewer ID (recipient), and a click result in association with each other.

[0066] The push notification topic is the topic of the stream detected at the time of the notification. The push notification content is the content (e.g., text) displayed to the viewer in the notification and may be generated based on the push notification topic. The click result indicates whether the notification was clicked or selected by the viewer.

[0067] In this embodiment, the optimal push notification topics for viewer V1 include "guitar" and "games," and the optimal push notification topic for viewer V2 includes "singing." Therefore, when the topic "guitar" is detected at time t1, a notification with the content "D1 is playing guitar!" is sent to viewer V1. When the topic "singing" is detected at time t2, a notification with the content "D1 is singing!" is sent to viewer V2.

[0068] In some embodiments, the processing unit 322 checks the click results and determines whether to send an additional notification to a viewer who already received a previous notification (for the same stream). For example, a notification sent to viewer V1 at time t1 is not clicked. At time t4, the topic "Game" is detected, which meets the optimal push notification topic criteria for viewer V1, so an additional notification is sent to viewer V1 with the content "D1 is playing a game!". In some embodiments, if the processing unit 322 determines that (1) the previous notification was not successful and (2) the newly obtained attribute data (different from the previous one) meets the optimal push notification criteria for the viewer, the processing unit 322 may send the notification again.

[0069] FIG. 16 is a schematic diagram illustrating an exemplary notification according to some embodiments of the present invention. The notification includes a text portion that reads, "Judy is streaming." The notification may display an image clipped from a stream room, a video clip from the stream room, or a real-time display (or preview) of the stream room. The recipient may click a "Join" button to join the stream room. In some embodiments, the clipped image or video may correspond to the optimal push notification topic for the viewer receiving the notification. For example, if the processing unit 322 detects that a stream topic satisfies the viewer's optimal push notification topic, the processing unit 322 may use the machine learning DB 334 to extract images or video clips that are determined (by the machine learning DB 334) to closely reflect the topic and send the images or video clips to the viewer as part of the notification.

[0070] 17 is a schematic diagram illustrating an exemplary notification according to some embodiments of the present invention. At time t1, a stream from broadcaster D1 is detected to have the topic "guitar," which meets the optimal condition of viewer V1. Therefore, a notification is sent to viewer V1 in text format (which has a higher click-through rate for viewer V1). At time t2, the same stream from broadcaster D1 is detected to have the topic "singing," which meets the optimal condition of viewer V2. Therefore, a notification is sent to viewer V2 in image / video format (which has a higher click-through rate for viewer V2).

[0071] Some embodiments of the present invention provide customized push notifications for each viewer, increasing click-through rates and even retention time within the streamroom.

[0072] The hardware configuration of the information processing device will be described with reference to Fig. 18. Fig. 18 is a block diagram showing an example of the hardware configuration of an information processing device based on some embodiments of the present invention. The information processing device 900 shown in the figure can realize, for example, the server 10 and / or the user terminals 20 and 30 in some embodiments.

[0073] The information processing device 900 includes a CPU 901, a ROM (read-only memory) 903, and a RAM (random access memory) 905. The information processing device 900 may also include a host bus 907, a bridge 909, an external bus 911, an interface 913, an input device 915, an output device 917, a storage device 919, a drive 921, a connection port 925, and a communication device 929. The information processing device 900 also includes an imaging device such as a camera (not shown). The information processing device 900 may also include a DSP (digital signal processor) or an ASIC (application-specific integrated circuit) in addition to or instead of the CPU 901.

[0074] The CPU 901 functions as an arithmetic processing device and control device, controlling all or part of the operation of the information processing device 900 in accordance with various programs stored in the ROM 903, the RAM 905, the storage device 919, or the removable recording medium 923. For example, the CPU 901 controls the overall operation of each functional unit included in the server 10 and the user terminals 20 and 30 in some embodiments. The ROM 903 stores programs and calculation parameters used by the CPU 901. The RAM 905 functions as a main storage device that stores programs used during execution by the CPU 901 and parameters that change appropriately during execution. The CPU 901, ROM 903, and RAM 905 are interconnected by a host bus 907, which may be an internal bus such as a CPU bus. Furthermore, the host bus 907 is connected to an external bus 911, such as a PCI (Peripheral Component Interconnect / Interface) bus, via a bridge 909.

[0075] The input device 915 may be a device operated by a user, such as a mouse, keyboard, touch panel, button, switch, or lever, or a device that converts a physical quantity into an electrical signal, such as a sound sensor typified by a microphone, an acceleration sensor, a tilt sensor, an infrared sensor, a depth sensor, a temperature sensor, or a humidity sensor. The input device 915 may be, for example, a remote control device that uses radio waves such as infrared, or an external connection device 927 such as a mobile phone that supports operation of the information processing device 900. The input device 915 includes an input control circuit that generates an input signal based on information input by the user or a detected physical quantity and outputs the signal to the CPU 901. The user operates the input device 915 to input various data to the information processing device 900 and instruct it to operate.

[0076] The output device 917 is a device that can visually or audibly notify the user of acquired information. The output device 917 may be, for example, a display such as an LCD, PDP, or OLED, an audio output device such as a speaker or headphones, or a printer. The output device 917 outputs the processing results of the information processing device 900 as video such as text or an image, or audio such as voice.

[0077] The storage device 919 is a data storage device and is configured as an example of a storage unit of the information processing device 900. The storage device 919 is, for example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device. The storage device 919 stores programs executed by the CPU 901, various data, various data acquired from the outside, and the like.

[0078] The drive 921 is a reader / writer of a removable recording medium 923 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, and is built into or externally attached to the information processing device 900. The drive 921 reads information recorded on the attached removable recording medium 923 and outputs it to the RAM 905. Furthermore, the drive 921 writes information to the attached removable recording medium 923.

[0079] The connection port 925 is a port for directly connecting a device to the information processing device 900. The connection port 925 may be, for example, a USB (Universal Serial Bus) port, an IEEE 1394 port, or a SCSI (Small Computer System Interface) port. Furthermore, the connection port 925 may be an RS-232C port, an optical audio terminal, an HDMI (High-Definition Multimedia Interface) port, or the like. By connecting the external connection device 927 to the connection port 925, various data can be exchanged between the information processing device 900 and the external connection device 927.

[0080] The communication device 929 is, for example, a communication interface formed by a communication device for connecting to the network NW. The communication device 929 may be, for example, a communication card for a wired or wireless local area network (LAN), Bluetooth (trademark), or wireless USB (WUSB). Furthermore, the communication device 929 may be a router for optical communication, a router for ADSL (asymmetric digital subscriber line), or a modem for various communications. The communication device 929 transmits and receives signals, etc., over the Internet or with other communication devices using a predetermined protocol such as TCP / IP. The communication network NW connected to the communication device 929 is a wired or wireless network, such as the Internet, a home LAN, infrared communication, radio wave communication, or satellite communication. The communication device 929 functions as a communication device.

[0081] The imaging device (not shown) is a device that captures an image of real space using an imaging element such as a CCD (charge-coupled device) or a CMOS (complementary metal-oxide semiconductor), and various components such as a lens for controlling the formation of a subject image on the imaging element, and generates a captured image. The imaging device may capture either a still image or a moving image.

[0082] The above describes the configuration and operation of the live streaming system 1 according to this embodiment. This embodiment is merely an example, and it will be understood by those skilled in the art that various modifications are possible with respect to the combination of each component and each process, and that such modifications are also within the scope of the present invention.

[0083] The processes and procedures described in the present invention, in addition to those explicitly described, can be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein can be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, non-transitory computer-readable media, magnetic disks, etc. Furthermore, the processes and procedures described herein can be implemented as computer programs corresponding to the processes and procedures, and can be executed by various types of computers.

[0084] Furthermore, the system or method described in the above embodiments may be integrated into a program stored in a non-transitory computer-readable medium such as a solid-state storage device, an optical disk storage device, a magnetic disk storage device, etc. Alternatively, the program may be downloaded from a server via the Internet and executed by a processor.

[0085] Although the technical contents and features of the present invention have been described above, those skilled in the art can still make many variations and modifications without departing from the teachings and disclosure of the present invention. Therefore, the scope of the present invention is not limited to the embodiments already disclosed, but is within the scope of the claims, including other variations and modifications that do not depart from the present invention. [Explanation of symbols]

[0086] 1. Communication Systems 10 Servers 20 User terminal 30, 30a, 30b User terminal LV Streamer AU1, AU2 viewers VD, VD1, VD2 video NW Network 30 User terminals 100 delivery units 102 Imaging control unit 104 Audio control unit 106 Video Transmission Unit 108 Streamer UI Control Unit 200 viewing units 202 Viewer-side UI control unit 204 Superposition Information Generation Unit 206 Input information transmission unit 302 Distribution Information Provision Unit 304 Relay unit 306 Gift Processing Unit 308 Payment Processing Unit 310 Stream DB 312 User DB 314 Gift DB 320 Acquired Units 322 Processing Unit 330 Push Notification DB 332 Push Notification Strategy DB 334 Machine Learning DB 900 Information Processing Equipment 901 CPU 903 ROM 905 RAM 907 Host Bus 909 Bridge 911 External Bus 913 Interface 915 Input Device 917 Output Device 919 Storage Device 921 Drive 923 Removable Recording Media 925 connection port 927 External Connection Device 929 Communication Equipment

Claims

1. 1. A method for server-implemented notification, comprising: sending a first notification related to the stream to a first viewer based on a first condition; sending a second notification related to the stream to a second viewer based on a second condition; wherein the first condition is different from the second condition; 10. A method for notification, wherein the stream is a live stream and the first condition is related to a real-time mood level of a broadcaster providing the stream.

2. 1. A system for notification, comprising: one or more processors, the one or more processors executing machine-readable instructions to: sending a first notification related to the stream to a first viewer based on a first condition; sending a second notification related to the stream to a second viewer based on a second condition; wherein the first condition is different from the second condition; 10. A system for notifications, wherein the stream is a live stream, and the first condition is related to a real-time mood level of a broadcaster providing the stream.

3. A non-transitory computer-readable medium containing a program for notification, the program being configured to: sending a first notification related to the stream to a first viewer based on a first condition; sending a second notification related to the stream to a second viewer based on a second condition; wherein the first condition is different from the second condition; A non-transitory computer-readable medium containing a program for notification, wherein the stream is a live stream, and the first condition is related to a real-time mood level of a broadcaster providing the stream.

Images