Task management for content distribution

Abstract

To reduce the burden on content distributors related to content distribution. [Solution] A task management system is provided for content distributors. The task management system acquires distribution schedule information for the content distribution scheduled by the distributor, registers task information in a database indicating one or more tasks related to the content distribution based on the distribution schedule information, and executes or assists in the execution of at least one task according to the task information registered in the database. The at least one task includes a task of generating a message to be transmitted over a communication channel for communication between the distributor and the viewer. The execution control unit executes the task by inputting a generation command based on the theme or avatar-related information of the content distribution into a text generation model.

Description

Technical Field

[0001] This disclosure relates to task management for content delivery.

Background Art

[0002] Conventionally, a system for delivering content including video and audio from a distributor to one or more viewers via a network is known.

[0003] For example, the system of Patent Document 1 automatically generates candidates for a distributor's reaction to actions such as comments and gifts received from viewers during content delivery, and presents those candidates to the distributor. The system of Patent Document 2 automatically generates a highlight video including a lively scene in content delivery based on speech recognition, and posts the highlight video to the platform. The system of Patent Document 3 performs analysis of viewers' emotions based on comments from viewers and real-time monitoring of the number of comments.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0005] Generally, content creators need to perform various tasks to increase audience interest in their content and grow their audience numbers. For example, if a creator responds appropriately to actions from viewers during a live stream, the likelihood of those viewers joining the next live stream will increase. Furthermore, posting highlight videos of live streams is expected to attract new viewers to future live streams.

[0006] However, managing and / or performing the numerous tasks associated with content distribution is a burden for distributors.

[0007] Therefore, the technology disclosed herein aims to reduce the burden on content distributors related to content distribution. [Means for solving the problem]

[0008] From one perspective, a task management system for a content distributor is provided, comprising: an information acquisition unit that acquires distribution schedule information for the content distribution scheduled by the distributor; a task management unit that registers task information indicating one or more tasks related to the content distribution in a database in association with the content distribution based on the distribution schedule information; and an execution control unit that executes at least one of the one or more tasks, or assists in the execution of said at least one task, according to the task information registered in the database, wherein the distribution schedule information includes the theme of the content distribution, and the at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the distributor and the viewer via a network, and the execution control unit executes the message generation task by inputting a generation command based on the theme of the content distribution into a text generation model. From another perspective, a task management system for a content distributor is provided, comprising: an information acquisition unit that acquires distribution schedule information for the content distribution scheduled by the distributor; a task management unit that registers task information indicating one or more tasks related to the content distribution in a database in association with the content distribution based on the distribution schedule information; and an execution control unit that executes at least one of the one or more tasks, or assists in the execution of said at least one task, according to the task information registered in the database, wherein the distribution schedule information includes avatar-related information related to avatars used by the distributor in the content distribution, the at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the distributor and the viewer via a network, and the execution control unit executes the message generation task by inputting a generation command based on the avatar-related information into a text generation model. [Effects of the Invention]

[0009] According to this disclosure, the burden on content distributors related to content distribution can be reduced. [Brief explanation of the drawing]

[0010] [Figure 1] A flowchart illustrating an example of the general processing flow for content delivery from a broadcaster to a viewer. [Figure 2] An explanatory diagram showing an example of the layout of a content viewing screen. [Figure 3A] An explanatory diagram showing some examples of pre-delivery tasks. [Figure 3B] An explanatory diagram showing some examples of tasks currently being delivered. [Figure 3C] An explanatory diagram showing some examples of post-delivery tasks. [Figure 4] An explanatory diagram showing several examples of social media posts related to content distribution. [Figure 5]Schematic diagram showing an example of the general configuration of a task management system according to an embodiment. [Figure 6] Block diagram showing an example of the hardware configuration of a device constituting a task management system according to an embodiment. [Figure 7] Block diagram showing an example of the functional configuration of a management server according to an embodiment. [Figure 8A] Explanatory diagram showing an example of the configuration of a schedule registration screen according to an embodiment. [Figure 8B] Explanatory diagram showing an example of the configuration of a task setting screen according to an embodiment. [Figure 8C] Explanatory diagram showing an example of the configuration of a detailed setting screen according to an embodiment. [Figure 9] Explanatory diagram showing an example of the configuration of a customization screen according to an embodiment. [Figure 10] Explanatory diagram showing an example of the configuration of a submission confirmation screen according to an embodiment. [Figure 11] Explanatory diagram showing an example of the configuration of a reminder screen according to an embodiment. [Figure 12] Explanatory diagram showing an example of the configuration of a thumbnail selection screen according to an embodiment. [Figure 13] Explanatory diagram showing an example of a prompt that can be input to an image generation model for generating a thumbnail image. [Figure 14A] Explanatory diagram showing a first example of a prompt that can be input to a text generation model for generating a message for SNS posting. [Figure 14B] Explanatory diagram showing a second example of a prompt that can be input to a text generation model for generating a message for SNS posting. [Figure 14C] Explanatory diagram showing a third example of a prompt that can be input to a text generation model for generating a message for SNS posting. [Figure 15] Block diagram showing an example of the functional configuration of a distributor terminal according to an embodiment. [Figure 16] Sequence diagram showing an example of the flow of task management processing according to an embodiment. [Figure 17]A sequence diagram showing an example of the task management process flow related to the first modified example. [Figure 18] A schematic diagram showing an example of the general configuration of a task management system related to the second modified example. [Modes for carrying out the invention]

[0011] Embodiments of this disclosure will be described in detail below with reference to the attached drawings. In this specification, elements having the same or similar function are denoted by the same reference numeral, and redundant descriptions of such elements are omitted. Although the following embodiments describe specific combinations of two or more features, not all features relating to the described combinations are necessarily essential. Parts of one embodiment may be combined with parts of other embodiments.

[0012] <1. Overview of Content Distribution> First, we will explain the overview of content distribution related to the technology disclosed herein using Figures 1 to 4.

[0013] <1-1. General Processing Flow> Figure 1 is a flowchart illustrating an example of a general processing flow for content distribution from a distributor terminal 100 to a viewer terminal 150. The distributor terminal 100 is an information processing device operated by the distributor 10. The viewer terminal 150 is an information processing device operated by the viewer 15. The distributor 10 is an end-user who leads content distribution using a distribution application running on the distributor terminal 100. On the other hand, the viewer 15 is an end-user who views the distributed content using a viewing application running on the viewer terminal 150. The distribution application and the viewing application may be dedicated applications for content distribution and viewing, or they may be general-purpose web browsers.

[0014] This specification primarily describes embodiments relating to the distribution of video content based on video footage captured or acquired by a distributor terminal 100. In particular, one embodiment describes the distribution of video content featuring an avatar (virtual performer) that virtually represents the distributor 10. However, the technology described herein is also applicable to the distribution of other types of content, such as video content without avatars or audio content without video.

[0015] In the example shown in Figure 1, the content delivery process includes the steps of motion tracking S1, avatar generation S2, background overlay S3, synthesis S4, and object addition S5.

[0016] Motion tracking S1 is a process that detects the movements of the broadcaster appearing in the broadcaster video acquired by the broadcaster terminal 100. For example, for each frame of the broadcaster video, the position and orientation of parts of the broadcaster such as the head, eyes, mouth, torso, arms, and legs are detected in the image, and motion data indicating the detection results is generated. In particular, when targeting parts of the broadcaster's face, this process is also called face tracking.

[0017] Avatar generation S2 is a process of generating each frame of the avatar video based on the avatar configuration (for example, a set of types of parts that make up the avatar) that has been registered in advance by the broadcaster 10 and the motion data obtained as a result of motion tracking S1.

[0018] Background overlay S3 is the process of overlaying the avatar image onto a background layer that displays a background selected by the broadcaster 10. The background layer may be a still image or a video. A transparent layer or a green screen may also be set as the background layer.

[0019] Synthesis S4 is a process of generating video content by compositing additional content obtained from some external source with avatar footage including a background layer. The avatar footage may be placed in parallel with the additional content. Alternatively, the avatar footage may be inserted into the additional content by superimposing it on a transparent layer or green screen.

[0020] Object addition S5 is a process of adding supplemental objects to the video content generated as a result of synthesis S4 to generate an application screen. For example, when an action such as a comment or gift from a viewer 15 (hereinafter referred to as a viewer action) is received, a visual object representing the viewer action may be superimposed on the video content. Similarly, when an action such as a thank you for a comment or gift from a broadcaster 10 (hereinafter referred to as a broadcaster action) is received, a visual object representing the broadcaster action may be superimposed on the video content.

[0021] Ultimately, the video content, including the performance objects, is played on the content viewing screen of the viewing application on the viewer terminal 150. Although not shown in Figure 1, in parallel with the distribution of the video content, the audio from the distributor 10 (and sound effects, background music, etc.) is also distributed to the viewer terminal 150 and can be played on the viewer terminal 150. The viewer 15 then watches this content.

[0022] The video content, including the performance objects, is also played on the content distribution screen of the distribution application on the distributor terminal 100. The distributor 10 continues content distribution while checking the video content being played.

[0023] As shown by the dashed lines in Figure 1, motion tracking S1, avatar generation S2, background overlay S3, and synthesis S4 may be omitted from the content distribution process. For example, in the distribution of simple live video, the video from the distributor terminal 100, which is used as a shooting device, may be used as the video content as is.

[0024] <1-2. Example of a content viewing screen> Figure 2 shows an example of the configuration of a content viewing screen. Referring to Figure 2, the content viewing screen 20 is displayed on the display of the viewer terminal 150. The content viewing screen 20 includes a status area 21, a content area 22, an interaction area 23, and a menu button 24.

[0025] Status area 21 is an area that displays status information related to the ongoing content delivery. In the example in Figure 2, status area 21 contains two status objects A1 and A2. Status object A1 shows the icon and username of the viewer 15 currently watching the content on viewer terminal 150. Status object A2 shows the total number of viewers currently watching the same content.

[0026] Content area 22 is the area where video content is played. In the example in Figure 2, in content area 22, video content is played in which the avatar video of avatar V1 is superimposed with the performance object B1. Avatar V1 is rendered as computer graphics (CG) and changes its facial expressions and posture in accordance with the movements of the broadcaster. Performance object B1 is an object that is temporarily displayed in response to viewer actions (for example, providing a gift to broadcaster 10).

[0027] Interaction area 23 is the area for interaction between the broadcaster 10 and the viewer 15. In the example in Figure 2, interaction area 23 includes the timeline area R1, the comment input field B4, the gift button B5, and the exit button B6.

[0028] The timeline area R1 displays multiple objects, including comment objects M1, M2, and M3. The comment objects are arranged chronologically, for example, in order of the time the comments were received. Viewer 15 can view the comment objects chronologically by scrolling the timeline area R1 up and down.

[0029] Comment object M1 contains a comment sent by a viewer and the viewer's icon. Reaction buttons B2 and B3 are located to the right of comment object M1. Viewer 15 can react to comments from other viewers by operating reaction buttons B2 and B3 (for example, reaction button B2 is for "likes," and reaction button B3 is for replying to comments). Comment object M2 is an object for system notifications. In the example in Figure 2, comment object M2 contains text indicating that a viewer has joined the content distribution (started watching the content) and the viewer's icon. Comment object M3 contains a comment sent by the broadcaster 10 from the distribution application and the broadcaster 10's icon. In the example in Figure 2, broadcaster 10 is greeting a new viewer through the comment in comment object M3.

[0030] The comment input field B4 is an object for receiving comments from viewer 15. The gift button B5 is an object for receiving the selection of a gift (for example, a tip or other item) to be sent from viewer 15 to streamer 10. The exit button B6 is a button for viewer 15 to stop watching the content and exit the content stream.

[0031] The comments and gifts from the aforementioned viewer 15 are examples of viewer actions. Viewer actions also include reactions to actions from the broadcaster 10 or other viewers. In this specification, such viewer actions, as well as actions by viewers such as joining and leaving content distribution, are referred to as viewer activities. On the other hand, comments from the broadcaster, as well as actions such as avatar gestures and speech, are examples of broadcaster actions. Broadcaster actions also include reactions to actions from viewers.

[0032] The menu button 24 is a button for accessing various functions related to viewing content. For example, the system may provide the viewer 15 with various functions such as changing the profile (icon and username, etc.), changing the screen layout, adjusting the volume, and purchasing items that can be used as gifts.

[0033] The content distribution screen displayed on the broadcaster terminal 100 may have the same configuration as the content viewing screen described above, or it may have a different configuration. For example, the content distribution screen may display broadcaster video acquired by the broadcaster terminal 100 in parallel with the same video content distributed to the viewer terminal 150. In addition, information related to the distribution task described later may be displayed on the content distribution screen. The functions for broadcasters that can be called from the content distribution screen differ from the functions for viewers. For example, various functions such as changing the avatar configuration used for distribution, executing broadcaster-specific actions, and displaying the profile of a specified viewer may be provided to the broadcaster 10.

[0034] <1-3. Tasks of content distributors related to content distribution> As mentioned above, content distributors can interact with one or more viewers participating in the content distribution through various actions during the distribution. Even when content distribution is not taking place, distributors can use communication channels between the distributor and viewers to send information to or interact with viewers. For example, social networking services (SNS), online advertising, and email are examples of communication channels between distributors and viewers.

[0035] When content creators communicate with their audience in a timely and appropriate manner, the number of viewers participating in content distribution increases, and the loyalty (trust or attachment to the creator) of individual viewers improves. The increase in the number of viewers and the improvement in viewer loyalty motivate creators to distribute content and increase the economic benefits they can obtain depending on their revenue model (e.g., advertising revenue from the platform, tips from viewers, and sales of original merchandise). Platform providers also benefit from increased content distribution, as it leads to increased revenue from advertising fees from advertisers, application usage fees, and item sales.

[0036] Tasks that content distributors can perform to revitalize content distribution can be classified into three categories based on their temporal relationship to content distribution: pre-distribution tasks, in-distribution tasks, and post-distribution tasks.

[0037] Figure 3A shows some examples of pre-delivery tasks that may be performed before content delivery is carried out.

[0038] For example, the first task T1 is a task of transmitting information related to content distribution (hereinafter referred to as distribution-related information) to an unspecified or specific group of viewers 15 over a communication channel between the distributor 10 and the viewers 15. In pre-distribution tasks, the first task T1 is typically intended to notify viewers 15 of upcoming content distribution and encourage their participation in the content distribution.

[0039] For example, sending distribution-related information to one or more unspecified viewers 15 may include one or more of the following: • Posting information related to the broadcast on social media • Publication of information related to online advertising distribution. • Distribution of related information via email newsletter

[0040] Furthermore, the dissemination of distribution-related information to specific viewers 15 may include one or more of the following: • Sending distribution-related information via direct message on social media. • Sending a delivery notification email in email format A specific viewer 15 may be a viewer 15 that meets predetermined viewer selection criteria, or a viewer 15 designated or registered by the broadcaster 10. The viewer selection criteria may be, for example, a viewer who has registered broadcaster 10 as a favorite (a so-called "follower"), or a viewer whose number of past content distributions exceeds a certain threshold.

[0041] For example, distribution-related information may include a thumbnail image related to content distribution. The second task T2 is a task to generate a thumbnail image used when transmitting distribution-related information over a communication channel. The thumbnail image generated in the second task T2 may include at least one of the following: information indicating the distributor (e.g., nickname or avatar image), information indicating the date and time of distribution, and information indicating the content of the distribution. Additionally or alternatively, distribution-related information may include a message conveyed to the viewer 15 in relation to content distribution. The third task T3 is a task to generate a message transmitted over a communication channel. The message generated in the third task T3 may include at least one of the following: information indicating the distributor, information indicating the date and time of distribution, or information indicating the content of the distribution.

[0042] Figure 3B shows some examples of in-delivery tasks that may be performed during content delivery.

[0043] The distribution task may include a first task T1 that transmits distribution-related information about the ongoing content distribution to one or more unspecified or specific viewers 15 via a communication channel between the distributor 10 and the viewers 15. The distribution task may further include a second task T2 that generates a thumbnail image for the first task T1, and / or a third task T3 that generates a message for the first task T1.

[0044] Task 4, T4, is the task of performing broadcaster actions directed towards specific viewers 15a during ongoing content delivery. For example, broadcaster 10 can perform special broadcaster actions directed towards viewers 15a who are evaluated as highly loyal based on past activity, thereby maintaining or further improving the loyalty of viewers 15a.

[0045] Figure 3C shows some examples of post-delivery tasks that may be performed after content delivery has been completed.

[0046] The post-distribution task may include a first task T1 that transmits distribution-related information to one or more unspecified or specific viewers 15 via a communication channel between the distributor 10 and the viewers 15 for follow-up on the completed content distribution. The post-distribution task may further include a second task T2 that generates a thumbnail image for the first task T1, and / or a third task T3 that generates a message for the first task T1.

[0047] Task 5 (T5) is the task of generating a shortened version or archive of the content distributed in a completed content distribution. For example, by publishing a shortened version of a highlight video or highlight images (slideshow or single still image) containing highlight scenes from the content distribution on communication channels such as social media, it is possible to attract the interest of potential viewers and increase the number of viewers in the future. Task 6 (T6) is the task of publishing the generated shortened version or archive.

[0048] Figure 4 shows several examples of SNS posts related to content distribution. Referring to Figure 4, the SNS post viewing screen 25 is displayed on the viewer terminal 150's display. The post viewing screen 25 includes a status area 21, menu buttons 24, a post display area 26, and a post input field 27.

[0049] The post display area 26 is an area where posts from SNS users are displayed chronologically, for example, in order of posting time. In the example in Figure 4, posts P1 to P5 are displayed in the post display area 26. In particular, post P1 contains a message sent by a certain broadcaster 10 to an unspecified audience 15 as a follow-up about a completed content distribution. Such SNS posts may include a shortened version or archive of the distributed content. Post P2 contains a message from an audience 15 in response to the message in post P1. Posts P3 and P5 are posts from other audiences 15. Post P4 contains a message sent by a different broadcaster to announcing a future content distribution planned for an unspecified audience 15.

[0050] As mentioned above, there are various tasks that content creators should ideally perform to revitalize content distribution. However, managing and executing these numerous tasks is burdensome for content creators. Therefore, a mechanism to alleviate the burden on content creators related to content distribution will be incorporated into the task management system, which will be explained in detail in the following sections.

[0051] <2. Overview of the Task Management System> <2-1. Example of overall structure> Figure 5 is a schematic diagram showing an example of the general configuration of a task management system 1 according to one embodiment. Referring to Figure 5, the task management system 1 includes a network 5, a broadcaster terminal 100, one or more viewer terminals 150, and a management server 200.

[0052] Network 5 interconnects the broadcaster terminal 100, one or more viewer terminals 150, and the management server 200. Network 5 may be any type of communication network, such as the internet, an intranet, or a home network. Network 5 may also be a combination of multiple different communication networks. Each communication network may be a wired network or a wireless network.

[0053] As described above, the broadcaster terminal 100 is an information processing device operated by the broadcaster 10. The broadcaster terminal 100 may be, for example, a smartphone or a PC (personal computer). The viewer terminal 150 is an information processing device operated by the viewer 15. The viewer terminal 150 may also be, for example, a smartphone or a PC. Figure 5 shows three viewer terminals 150, but the task management system 1 may include more or fewer viewer terminals 150.

[0054] The management server 200 is an information processing device for managing content distribution from the distributor terminal 100 to the viewer terminal 150, and for managing tasks related to content distribution. The distributor 10 can access the management server 200 using the distribution application on the distributor terminal 100. The management server 200 may be any type of server device, such as an application server, web server, or cloud server. Although only one management server 200 is shown in Figure 5, the functions of the management server 200 described herein may be realized by the cooperation of multiple server devices.

[0055] As will be explained in more detail later, the management server 200 stores data used for task management and distribution control in the database 250. Figure 5 shows an example where the management server 200 has the database 250, but a database server physically separate from the management server 200 may also have the database 250.

[0056] <2-2. Hardware Configuration Examples> Figure 6 is a block diagram showing an example of the hardware configuration of the broadcaster terminal 100, viewer terminal 150, and management server 200 that constitute the task management system 1 shown in Figure 5.

[0057] (1) Distributor's device The broadcaster terminal 100 includes a camera 101, a microphone 102, a communication interface (I / F) 103, an input device 104, a display 105, a speaker 106, storage 107, memory 108, and a processor 109. These components are interconnected via an internal bus.

[0058] Camera 101 is a shooting device that photographs a subject. In this embodiment, camera 101 photographs the broadcaster 10 and outputs the broadcaster's video.

[0059] The microphone 102 is an audio input device that acquires sound. In this embodiment, the microphone 102 acquires the sound of the broadcaster 10 and outputs an audio signal.

[0060] The communication interface 103 is an interface for communication between the distributor terminal 100 and other devices. In this embodiment, the distributor terminal 100 communicates with the management server 200 via the communication interface 103.

[0061] The input device 104 is a device that accepts operations and information input from the broadcaster 10. For example, the input device 104 may be a combination of one or more of the following: a touch sensor, a mouse, a pointing device, a keypad, a keyboard, a button, and a switch.

[0062] The display 105 is a display device that displays images and information. In this embodiment, the display 105 displays the content distribution screen described above, and other screens for the user interface provided to the distributor 10 by the task management system 1.

[0063] Speaker 106 is an audio output device that outputs sound. In this embodiment, in addition to audio output during content distribution, speaker 106 may also be used for outputting sound effects related to the user interface.

[0064] Storage 107 is a high-capacity storage device that stores various data related to content distribution. Storage 107 may be, for example, a hard disk drive (HDD) or a solid-state drive (SSD).

[0065] Memory 108 is a storage device that stores one or more computer programs for realizing the functions of the broadcaster terminal 100. Memory 108 may be a combination of non-volatile memory (e.g., read-only memory (ROM)) and volatile memory (e.g., random-access memory (RAM)).

[0066] The processor 109 is a processing circuit that controls the overall functions of the distributor terminal 100. The processor 109 may be, for example, a combination of one or more central processing units (CPUs). In this embodiment, the processor 109 functions as an application module of the distribution application (AP) 110 by executing a computer program stored in the memory 108. The functions of the distribution application 110 will be described in detail later.

[0067] (2) Viewer terminal The viewer terminal 150 includes a communication interface 153, an input device 154, a display 155, a speaker 156, storage 157, memory 158, and a processor 159. These components are interconnected via an internal bus.

[0068] The communication interface 153 is an interface for the viewer terminal 150 to communicate with other devices. In this embodiment, the viewer terminal 150 communicates with the management server 200 via the communication interface 153.

[0069] The input device 154 is a device that accepts operation and information input from the viewer 15. For example, the input device 154 may be a combination of one or more of the following: a touch sensor, a mouse, a pointing device, a keypad, a keyboard, a button, and a switch.

[0070] The display 155 is a display device that displays images and information. In this embodiment, the display 155 displays the content viewing screen 20 described above, and other screens for the user interface provided to the viewer 15 by the task management system 1.

[0071] Speaker 156 is an audio output device that outputs sound. In this embodiment, in addition to audio output during content distribution, speaker 156 may also be used for outputting sound effects related to the user interface.

[0072] Storage 157 is a high-capacity storage device that stores various data related to content distribution. Storage 157 may be, for example, an HDD or an SSD.

[0073] Memory 158 is a storage device that stores one or more computer programs for realizing the functions of the viewer terminal 150. Memory 158 may be a combination of non-volatile memory and volatile memory.

[0074] The processor 159 is a processing circuit that controls the overall functions of the viewer terminal 150. The processor 159 may be, for example, a combination of one or more CPUs. In this embodiment, the processor 159 functions as an application module of the viewing application (AP) 160 by executing a computer program stored in the memory 158.

[0075] (3) Management Server The management server 200 includes a communication interface 203, storage 207, memory 208, processor 209, and database 250. These components are interconnected via an internal bus.

[0076] Communication I / F 203 is an interface for communication between the management server 200 and other devices. In this embodiment, the management server 200 communicates with the broadcaster terminal 100 and the viewer terminal 150 via communication I / F 203.

[0077] Storage 207 is a high-capacity storage device that stores various types of data. Storage 207 may be, for example, an HDD or an SSD. In this embodiment, storage 207 stores a trained model of artificial intelligence (AI) used for task execution or task assistance, as will be described later. In other embodiments, the trained model may be stored in an external server device.

[0078] Memory 208 is a storage device that stores one or more computer programs for implementing the functions of the management server 200. Memory 208 may be a combination of non-volatile memory and volatile memory.

[0079] The processor 209 is a processing circuit that controls the overall functionality of the management server 200. The processor 209 may be, for example, a combination of one or more CPUs. In this embodiment, the processor 209 functions as a management module 210 by executing a computer program stored in memory 208. The functions of the management module 210 will be described in detail later.

[0080] Database 250 is a storage device that stores data required for task management and distribution control by the management server 200. The specific configuration of the data stored in database 250 will be described in detail later.

[0081] <3. Details of the management server's functions> Figure 7 is a block diagram showing an example of the functional configuration of a management server 200 according to one embodiment. Referring to Figure 7, the management module 210 of the management server 200 includes a distribution control unit 211, an SNS provision unit 213, a task management unit 215, and an execution control unit 217. The storage 207 stores the image generation model 221 and the text generation model 223. Furthermore, the database 250 includes a user database (DB) 251 and a task DB 252.

[0082] Furthermore, the image generation model 221 and the text generation model 223 may be provided as SaaS (Software as a Service) by an external server device of the task management system 1. In that case, the storage 207 does not need to store these trained models.

[0083] <3-1. User Data Management> User DB251 is a database that holds user data related to broadcasters, who are users of the broadcast AP110, and viewers, who are users of the viewing AP160. In the example in Figure 7, User DB251 includes the parts table 261, the channel table 262, the broadcaster table 263, the avatar table 264, the background table 265, and the viewer table 266.

[0084] The parts table 261 is a table that holds master data related to parts, which are components of an avatar that can be used by the distributor. The parts table 261 may include, for example, one or more of the following information items: "Part ID" "Part Type" "Part Name" "Parts image" "price" "Part ID" is an identifier that uniquely identifies each part. "Part Type" indicates the category to which each part is classified. Each part of an avatar is classified into one of various categories, for example, depending on the body part ("eyes", "mouth", "torso", etc.) or the position where accessories are attached ("hair accessories", "glasses", "clothing", etc.). "Part Name" indicates the name of each part. "Part Image" is an information item that stores the image data used when rendering each part as a CG image. "Price" indicates the price charged to the distributor when providing each part to the distributor for a fee.

[0085] The channel table 262 is a table that holds master data related to candidate communication channels that a broadcaster can use to communicate with viewers. The channel table 262 may include, for example, one or more of the following information items: "Channel ID" "Channel Type" "Channel name" The "Channel ID" is an identifier that uniquely identifies each communication channel. The "Channel Type" indicates the type of each communication channel. For example, the "Channel Type" of one communication channel may be "SNS," while the "Channel Type" of another communication channel may be "Email." The "Channel Name" indicates the name of each communication channel.

[0086] The distributor table 263 is a table that holds distributor data related to the distributors who perform content distribution in the task management system 1. The distributor table 263 may include, for example, one or more of the following information items: "Streamer ID" "username" "Icon image" "email address" "Authentication Information" "Channel Settings" "balance" "Streamer ID" is an identifier that uniquely identifies each streamer. "Username" indicates the name or nickname of each streamer. "Icon Image" is an information item that stores image data of each streamer's icon displayed on the screen. "Authentication Information" is an information item that stores information used for user authentication of each streamer (e.g., password, email address for two-factor authentication, biometric data for biometric authentication, etc.). "Channel Settings" is configuration information that indicates one or more communication channels that each streamer can use to send out stream-related information, as an array of "Channel ID" values ​​in channel table 262. In addition to the "Channel ID" values, "Channel Settings" may further include account information and address information required to use the corresponding communication channel. "Balance" indicates the balance of in-system currency held by each streamer. In-system currency increases, for example, through charges made by streamers and donations received from viewers, and decreases through purchases of parts or other items by streamers.

[0087] The avatar table 264 is a table that holds avatar configuration data showing the configuration of the avatar that the broadcaster has pre-registered as their own avatar. The avatar table 264 may include, for example, one or more of the following information items: "Streamer" "Avatar ID" "Avatar Name" "Attribute 1" ~ "Attribute M" "Part 1" to "Part N" "Distributor" indicates the distributor who registered each avatar, using the value of "Distributor ID" in Distributor Table 263. "Avatar ID" is an identifier that uniquely identifies each avatar among multiple avatars of the same distributor. "Avatar Name" indicates the name of each avatar. "Attribute 1" to "Attribute M" indicate the values ​​of the attributes set for each avatar. For example, "Attribute 1" may be gender, "Attribute 2" may be age, and "Attribute 3" may be personality, with M (M being a natural number) attribute values ​​being set. "Part 1" to "Part N" indicate the parts that make up each avatar, using the values ​​of "Part ID" in Part Table 261. For example, "Part 1" may be the "eye" part, "Part 2" may be the "mouth" part, and "Part 3" may be the "body" part, with N (N being a natural number) parts making up the avatar being set. Furthermore, if viewers can also register their own avatars, the avatar table 264 may also hold avatar configuration data that shows the configuration of the viewer's avatar.

[0088] In the following explanation, the avatar configuration data stored in avatar table 264, and the data of parts associated with each avatar in avatar table 264, are collectively referred to as avatar-related information.

[0089] Background Table 265 is a table that holds master data related to background layers that may be used by distributors when distributing content. Background Table 265 may include, for example, one or more of the following information items: "Background ID" "name" "Background image" "Background ID" is an identifier that uniquely identifies each background. "Name" indicates the name of each background. "Background Image" is an information item that stores the image data used when drawing each background.

[0090] The viewer table 266 is a table that holds viewer data related to viewers who view content in the task management system 1. The viewer table 266 may include, for example, one or more of the following information items: "Viewer ID" "username" "Icon image" "email address" "Authentication Information" "balance" "Registered Streamer List" "Viewer ID" is an identifier that uniquely identifies each viewer. "Username" is the name or nickname of each viewer. "Icon Image" is an information item that stores the image data of each viewer's icon displayed on the screen. "Authentication Information" is an information item that stores the information used for user authentication of each viewer. "Balance" shows the balance of in-system currency held by each viewer. In-system currency increases, for example, through charges made by viewers, and decreases through tips or purchases of items by viewers. "Registered Streamer List" shows a list of streamers that each viewer has registered as favorites, as an array of "Streamer ID" values ​​from Streamer Table 263. For viewers who have not registered any favorite streamers, the "Registered Streamer List" may be empty.

[0091] The distribution control unit 211 provides the distributor terminal 100 with a data management screen that allows each distributor 10 to register, update, and delete distributor data and avatar configuration data. The distribution control unit 211 also provides the viewer terminal 150 with a data management screen that allows each viewer 15 to register, update, and delete viewer data. The data management screen can be accessed, for example, from a menu button on the application screen described in relation to Figure 2, and operated using the input devices of each terminal device.

[0092] Note that the structure of each table in User DB251 is not limited to the example described here. One table described may be split into multiple tables, and two or more tables described may be merged into one table. Also, some of the information items described as being included in a table may be omitted from that table, or included in other tables. The same applies to Task DB252, which will be described later. For example, above, an example was described in which the Viewer Table 266 includes a "Registered Broadcaster List," but the Broadcaster Table 263 may include a "Registered Viewer List" indicating one or more specific viewers.

[0093] <3-2. Controlling Content Distribution> The distribution control unit 211 works in conjunction with the distribution AP 110 of the distributor terminal 100 to control the distribution of content from the distributor terminal 100 to one or more viewer terminals 150. Here, we will describe an example in which, of the content distribution process steps S1 to S5 explained using Figure 1, the distribution AP 110 executes step S1, the distribution control unit 211 executes steps S2, S3 and S5, and step S4 is omitted.

[0094] Prior to content distribution, the distribution control unit 211 authenticates the distributor 10, who is a user of the distribution AP 110, using the "authentication information" in the distributor table 263. The distribution control unit 211 also receives the selection of the avatar and background to be used for content distribution from the distributor 10 via the distribution AP 110. The distribution control unit 211 identifies the configuration of the selected avatar based on the avatar configuration data in the avatar table 264.

[0095] When content distribution begins, the distribution AP110 acquires the distributor's video, performs motion tracking S1, and sends the motion data to the management server 200. The distribution control unit 211 generates each frame of the avatar video by performing avatar generation S2 based on the avatar configuration identified based on the avatar configuration data and the motion data received from the distribution AP110. The distribution control unit 211 also performs background overlay S3 to overlay the avatar video onto the background layer.

[0096] In parallel with the generation of avatar images, the distribution control unit 211 monitors notifications from the distribution AP 110 and the viewing AP 160. For example, when the distribution control unit 211 receives a request from the viewing AP 160 for a viewer 15 to participate in content distribution, it adds the address information of that viewing AP 160 to the destination of the content distribution. The distribution control unit 211 also notifies the distributor 10 and the viewers 15 who are already participating in the content distribution of the new viewer 15's participation via the content distribution screen of the distribution AP 110 and the content viewing screen of the viewing AP 160.

[0097] Furthermore, when the distribution control unit 211 receives a notification from the viewing AP 160 indicating that some viewer action has been taken, it executes processing corresponding to that viewer action. For example, if the distribution control unit 211 receives a comment from viewer 15, it inserts the corresponding comment object into the timeline area. Also, if the distribution control unit 211 receives a gift from viewer 15, it reflects the received gift in the broadcaster 10's account (for example, it increases the "balance" in the broadcaster table 263 according to the tip). Similarly, when the distribution control unit 211 receives a notification from the distribution AP 110 indicating that some broadcaster action has been taken, it executes processing corresponding to that broadcaster action. In addition, the distribution control unit 211 executes object addition S5 as needed to add performance objects to the video content, including the avatar video and background.

[0098] The distribution control unit 211 distributes video content, including performance objects, to the distribution AP 110 and to the viewing APs 160 of one or more viewers 15 participating in the content distribution. In parallel with the distribution of video content, the distribution control unit 211 distributes audio content representing the audio received from the distribution AP 110 to the viewing APs 160 (adding sound effects and background music as necessary).

[0099] The method of cooperation between the distribution control unit 211 and the distribution AP 110 is not limited to the examples described above. In one modified example, the distribution control unit 211 may perform motion tracking S1 instead of the distribution AP 110. In this case, the distribution AP 110 transmits the broadcaster's video to the distribution control unit 211. In another modified example, the distribution AP 110 may perform avatar generation S2. In this case, the distribution AP 110 generates an avatar video based on motion data and an avatar configuration previously obtained from the distribution control unit 211, and transmits the generated avatar video to the distribution control unit 211. In yet another modified example, the distribution AP 110 may perform background overlay S3 in addition to avatar generation S2.

[0100] In further modifications, the distribution AP110 and viewing AP160 may generate video content including avatar video (and background layer) based on motion data and avatar configuration (and background settings) received from the distribution control unit 211 when playing content. In this case, the addition of performance objects based on distributor actions and viewer actions may also be performed by the distribution AP110 and viewing AP160.

[0101] Furthermore, if the task management system 1 uses a third-party platform (for example, YouTube®, Twitch®, TikTok®, etc.) as a content distribution platform, the management server 200 does not need to include the distribution control unit 211. Also, content may be distributed in parallel on multiple content distribution platforms.

[0102] <3-3. Provision of SNS> The SNS provider unit 213 provides social networking services to the system's users, namely the broadcaster 10 and the viewer 15. For example, the SNS provider unit 213 receives SNS posts from the user's terminal device and displays the received posts in chronological order on a post viewing screen similar to the one shown in Figure 4. Posting to SNS is equivalent to sending information to an unspecified number of users. The SNS provider unit 213 may also provide a direct message (DM) function that allows users to exchange messages directly with each other by specifying a recipient. DM is equivalent to sending information to a specific user.

[0103] The task management system 1 may use a third-party platform as the SNS platform. In that case, the management server 200 does not need to include the SNS provider unit 213. The SNS platform can be used as one of the communication channels for communication between the broadcaster 10 and the viewer 15 via the network.

[0104] <3-4. Task Information Management> Task DB252 is a database that holds task information and related information indicating tasks that should be performed to activate content delivery. In the example in Figure 7, Task DB252 includes the delivery table 271, the first template table 272, the task table 273, the second template table 274, and the activity table 275.

[0105] Distribution table 271 is a table that holds distribution event information about content distribution carried out by the distributor. Distribution table 271 may include, for example, one or more of the following information items: "Streamer" "Event ID" "Release Date" "Start time" "theme" "Avatar used" "Streaming URL" "Task management flag" "Implementation Status" "Distributor" refers to the distributor who delivers each piece of content, as indicated by the "Distributor ID" value in Distributor Table 263. "Event ID" is an identifier that uniquely identifies the event for each piece of content delivery. "Delivery Date" indicates the date on which each piece of content delivery is carried out. Before a piece of content is delivered, the date indicated by "Delivery Date" is also referred to as the "Scheduled Date" for that piece of content delivery. "Start Time" indicates the time at which each piece of content delivery begins. In the following explanation, before a piece of content is delivered, the date and time of the content delivery indicated by "Delivery Date" and "Start Time" is also referred to as the scheduled timing for that piece of content delivery. "Theme" is a string representing the subject, title, or topic set by the distributor for each piece of content delivery. "Avatar Used" refers to the avatar used by the distributor in each piece of content delivery, as indicated by the "Avatar ID" value in Avatar Table 264. "Delivery URL" indicates the URL (Uniform Resource Locator) accessed to participate in each piece of content delivery. The "Task Management Flag" indicates whether the distributor wishes for Task Management System 1 to perform or assist in the performance of one or more tasks related to each content distribution. For content distributions where the distributor wishes for Task Management System 1 to perform or assist in the performance of tasks, the "Task Management Flag" is set to "True". For content distributions where the distributor does not wish for Task Management System 1 to perform or assist in the performance of tasks, the "Task Management Flag" is set to "False". The "Implementation Status" indicates the status related to the implementation of each content distribution (e.g., "Before Implementation", "In Progress", "Completed", or "Cancelled").

[0106] In this embodiment, the management server 200 acquires distribution event information for scheduled content distributions and registers it in the distribution table 271 before the content distribution is carried out. In the following description, the distribution event information acquired in this manner before the content distribution is carried out will be referred to as the scheduled distribution information.

[0107] The first template table 272 is a table that holds delivery schedule templates that define candidate delivery schedule information unique to each distributor. The first template table 272 may include, for example, one or more of the following information items: "Related streamers" "Template ID" "Template name" "Scheduling Patterns" "Default theme" "Default Avatar" "Default Task Management" "Associated Distributor" indicates the distributor associated with each distribution schedule template, as shown by the "Distributor ID" value in Distributor Table 263. "Template ID" is an identifier that uniquely identifies each distribution schedule template. One or more distribution schedule templates may be associated with a single distributor. "Template Name" indicates the name of each distribution schedule template determined by the distributor. "Scheduling Pattern" indicates the distribution pattern for scheduling content distribution. For example, "Scheduling Pattern" may be any temporal pattern related to the date and time of content distribution, such as "Every Sunday at 8 PM", "The 1st of every month", or "Once every three days". "Default Theme" indicates the default string for the theme of content distribution set by the distributor. "Default Avatar" indicates the default avatar used by the distributor, as shown by the "Avatar ID" value in Avatar Table 264. "Default Task Management" indicates the default value of the flag set in "Task Management Flag" in Distribution Table 271.

[0108] The task management unit 215 displays a schedule registration screen on the display 105 of the distributor terminal 100 via the distribution AP 110 to accept input of the above-mentioned information items of the distribution schedule information to be registered in the distribution table 271. The task management unit 215 pre-sets the default values ​​for each information item according to the distribution schedule template stored in the first template table 272. The distribution AP 110 sends the distribution schedule information, which indicates the values ​​of each information item entered or edited by the distributor, to the management server 200. The task management unit 215 acquires the distribution schedule information sent from the distribution AP 110 in this way and registers it in the distribution table 271. For content distributions for which the distribution date has not yet arrived, the task management unit 215 sets the "implementation status" to "before implementation". An example of the configuration of the schedule registration screen for accepting input of distribution schedule information will be described in detail later.

[0109] Task table 273 is a table that holds task information indicating one or more tasks related to content distribution that are performed (or planned) by the distributor. Task table 273 may include, for example, one or more of the following information items: "Related Events" "Task Type" "Execution timing" "Execution Type" "Channel used" "Execution Status" "Related Events" indicates the content distribution associated with each task, using the "Event ID" value in distribution table 271. "Task Type" indicates the type of each task, such as "SNS Post," "Direct Message," "Thumbnail Generation," "Message Generation," "Distributor Action," "Short Version Generation," "Archive Generation," "Short Version Publication," or "Archive Publication." More detailed task types may be adopted depending on the execution timing classification, such as "Message Generation - Before Distribution," "Message Generation - During Distribution," and "Message Generation - After Distribution." "Execution Timing" indicates the timing or deadline at which each task should be executed. "Execution Timing" may be an absolute date and time, or a relative time interval with respect to the start date and time of content distribution (e.g., one week before, one day before, one hour after, etc.).

[0110] The "Execution Type" indicates the degree to which the task management system 1 assists the distributor in the execution of each task. The "Execution Type" may be, for example, "Automatic Execution," "Execution with Confirmation," "Reminder," or "No Assistance." Tasks with an "Execution Type" of "Automatic Execution" are automatically executed by the execution control unit 217. Tasks with an "Execution Type" of "Execution with Confirmation" are executed by the execution control unit 217 after confirmation by the distributor before execution. Tasks with an "Execution Type" of "Reminder" are to be executed by the distributor, and the execution control unit 217 reminds the distributor of the execution of the task (for example, when the execution timing arrives or before). Tasks with an "Execution Type" of "No Assistance" are to be executed by the distributor, and the execution control unit 217 does not remind the distributor of the execution of the task.

[0111] "Channel Used" indicates the communication channel used for tasks executed using a communication channel, as defined by the "Channel ID" value in channel table 262. The value of "Channel Used" is limited to one of the values ​​associated with the distributor by the "Channel Settings" in distributor table 263. "Execution Status" indicates the status related to the execution of each task (e.g., "Not Executed", "Executed", or "Cancelled").

[0112] The second template table 274 is a table that holds task templates that define one or more sets of task candidates. The second template table 274 may contain one or more of the following information items, for example: "Related streamers" "Template ID" "Template name" "Task Type 1" ~ "Task Type K" "Execution timing 1" ~ "Execution timing K" "Associated Distributor" indicates the distributor associated with each task template, using the value of "Distributor ID" in Distributor Table 263. "Template ID" is an identifier that uniquely identifies each task template. One or more task templates may be associated with a single distributor. In this case, the first task template defines the first set of task candidates, and the second task template defines a second set of task candidates different from the first set. "Template Name" indicates the name of each task template determined by the distributor. "Task Type 1" to "Task Type K" indicate the types of the K (K is a natural number) task candidates defined by each task template. "Execution Timing 1" to "Execution Timing K" indicate the execution timings of the K task candidates defined by each task template. For example, each task template may define two or more task candidates of the same type, such as a SNS post from one week ago and an SNS post from one day ago as pre-distribution task candidates.

[0113] Here, we have described an example in which each task template is stored in association with a distributor (or a distributor ID that identifies the distributor). However, there may be one or more task templates (common templates) that are common to multiple distributors and are not associated with a specific distributor. In addition, the task management unit 215 may provide the distributor terminal 100 with a customization screen to accept customizations of task templates by the distributor, and register the customized templates as distributor-specific task templates in the second template table 274.

[0114] The task management unit 215 registers the distribution schedule information obtained from the distribution AP 110 into the distribution table 271, and then begins managing tasks related to content distribution indicated by the distribution schedule information. For example, based on the distribution schedule information, the task management unit 215 registers task information indicating one or more tasks related to content distribution into the task table 273.

[0115] More specifically, in this embodiment, the task management unit 215 displays one or more task candidates related to content distribution on the screen and allows the distributor 10 to select one or more tasks to be executed. The task management unit 215 then generates task information indicating the one or more tasks selected by the distributor 10 and registers the generated task information in the task table 273 in association with the content distribution (for example, the association can be achieved by the "related event" in the task table 273 indicating one of the values ​​of the "event ID" in the distribution table 271). For content distributions in which the distributor 10 does not wish to have the task management system 1 execute or assist in the execution of the task, the task management unit 215 does not need to register the corresponding task information in the task table 273.

[0116] The task management unit 215 determines the execution timing of each task based on the scheduled content delivery timing indicated by the delivery schedule information. For example, if the scheduled content delivery timing is 8:00 PM on December 25, 2025, and the relative execution timing of one of the pre-delivery tasks, an SNS post, is defined as one week before the scheduled timing, the task management unit 215 will determine that this SNS post should be executed at 8:00 PM on December 18, 2025, or by that time.

[0117] The task management unit 215 may determine the execution timing of each task based on the scheduled content delivery timing indicated by the delivery schedule information and the task type of the task. For example, the execution timing of a task of one task type may be determined as X days before the scheduled content delivery timing, and the execution timing of a task of another task type may be determined as Y hours before the scheduled content delivery timing.

[0118] In this embodiment, the task management unit 215 registers task information in the task table 273, associating it with content distribution, based on the task template and distribution schedule information obtained from the second template table 274. If multiple task templates stored in the second template table 274 are available to the distributor 10, the task management unit 215 may register task information in the task table 273 based on the template selected by the distributor 10 from among those multiple task templates and the distribution schedule information.

[0119] Specifically, the task management unit 215 displays a task setting screen for accepting the settings of tasks related to content distribution on the display 105 of the distributor terminal 100 via the distribution AP 110. The task management unit 215 proposes a list of desirable task candidates to the distributor 10 according to the definition of the selected task template. The distributor 10 sets the necessity of each task on the task setting screen (i.e., selects the tasks). The distribution AP 110 sends the list of tasks selected by the distributor 10 to the management server 200. The task management unit 215 registers task information indicating one or more tasks selected by the distributor 10 in the task table 273. The task management unit 215 may also display a detailed settings screen for each selected task on the display 105 of the distributor terminal 100 and accept the detailed settings for each task.

[0120] The following describes an example of the configuration of the user interface provided to the distributor 10 from the input of distribution schedule information to the registration of task information, using Figures 8A to 8C.

[0121] Figure 8A is an explanatory diagram showing an example of the configuration of the schedule registration screen 30. Referring to Figure 8A, the schedule registration screen 30 includes a schedule date selection field 31, a time selection field 32, a theme input field 33, an avatar selection field 34, an avatar display area 35, a checkbox 36, a cancel button 38, and an OK button 39.

[0122] The scheduled date selection field 31 is an object for accepting the selection of the scheduled date (delivery date) for content delivery. The time selection field 32 is an object for accepting the selection of the start time for content delivery. The theme input field 33 is an object for accepting the input of the theme for the scheduled content delivery. The avatar selection field 34 is an object for accepting the selection of the avatar to be used in the scheduled content delivery. The avatar display area 35 is an area where the image of the avatar selected in the avatar selection field 34 is displayed.

[0123] Checkbox 36 is an object that accepts the setting of whether or not to enable the execution or execution support of tasks related to scheduled content delivery (i.e., whether or not the distributor 10 wants the task management system 1 to execute or assist in the execution of tasks). In the example in Figure 8A, the function for executing or assisting in the execution of tasks by the task management system 1 is referred to as the "task management agent".

[0124] The Cancel button 38 is used to close the schedule registration screen 30 without sending the scheduled delivery information to the management server 200. The OK button 39 is used to send the scheduled delivery information entered or edited on the scheduled delivery registration screen 30 to the management server 200. When the scheduled delivery information is sent with the task management agent enabled in checkbox 36, the task management unit 215 registers the scheduled delivery information from the delivery AP 110 in the delivery table 271 and transitions the screen of the delivery AP 110 from the scheduled delivery registration screen 30 to the task setting screen 40, which will be described next.

[0125] The task management unit 215 may set default values ​​based on the distribution schedule template of the distributor 10 registered in the first template table 272 to one or more of the scheduled date selection field 31, time selection field 32, theme input field 33, and avatar selection field 34 on the schedule registration screen 30. This reduces the burden on the distributor 10 when entering distribution schedule information (distribution event information).

[0126] Figure 8B is an explanatory diagram showing an example of the configuration of the task setting screen 40. Referring to Figure 8B, the task setting screen 40 includes a header area that displays the delivery schedule information received via the schedule registration screen 30, as well as a task list setting area 41, a task template selection field 42, a back button 48, and a complete button 49.

[0127] The task list setting area 41 is an area for displaying a list of task candidates related to the scheduled content delivery and accepting selections of tasks to be performed. In the example in Figure 8B, the task candidates are grouped into pre-delivery tasks, in-delivery tasks, and post-delivery tasks. The triangular marks 43 in the task list setting area 41 are objects for expanding or collapsing the sublist of pre-delivery tasks. The triangular marks 44 are objects for expanding or collapsing the sublist of in-delivery tasks. The triangular marks 45 are objects for expanding or collapsing the sublist of post-delivery tasks.

[0128] In the example in Figure 8B, only the sublist of pre-distribution tasks is expanded, and each list item in the sublist indicates the task type and execution timing of the corresponding task candidate. For example, the task type of the task candidate in the first row is "Create Thumbnail," and the execution timing is "One week before." To the right of each list item are a checkbox 46 and an advanced settings button 47. The distributor 10 selects the corresponding task candidate as a task to be executed by checking the checkbox 46, or deselects the corresponding task candidate by unchecking the checkbox 46. The advanced settings button 47 is a button for calling up the advanced settings screen 50 for the corresponding task candidate. When the advanced settings button 47 is operated, the task management unit 215 transitions the screen of the distribution AP 110 from the task settings screen 40 to the advanced settings screen 50, which will be described next.

[0129] Figure 8C is an explanatory diagram showing an example of the configuration of the detailed settings screen 50. Here, we will explain an example of detailed settings for a task whose task type is SNS posting. Referring to Figure 8C, the detailed settings screen 50 includes a header area that displays the distribution schedule information, as well as a detailed settings area 51, a cancel button 58, and a settings button 59.

[0130] The detailed settings area 51 is an area for displaying detailed settings items related to the selected task. In the example in Figure 8C, the detailed settings area 51 includes a channel change button 52, a first radio button 53, a second radio button 54, and an execution type selection field 55. The channel change button 52 is a button for detailed settings items related to the first task T1, such as "SNS post" and "direct message". When the broadcaster 10 operates the channel change button 52, a selection of communication channels based on the "Channel Settings" in the broadcaster table 263 is displayed on the screen, and the broadcaster 10 selects the communication channel to which the SNS post will be posted from these options.

[0131] The first radio button 53 is an object for selecting whether to have the system generate the thumbnail image used in the SNS post (for example, using an AI-based image generation model) or to set it yourself. The second radio button 54 is an object for selecting whether to have the system generate the message used in the SNS post (for example, using an AI-based text generation model) or to enter it yourself. The execution type selection field 55 is an object for selecting the execution type of the task. In the example in Figure 8C, if "Full Auto" is selected in the execution type selection field 55, the "Execution Type" of the corresponding task becomes "Automatic Execution". If "User Confirmation Required" is selected in the execution type selection field 55, the "Execution Type" of the corresponding task becomes "Confirmation Required Execution". If "Reminder (Posted by User)" is selected in the execution type selection field 55, the "Execution Type" of the corresponding task becomes "Reminder".

[0132] The Cancel button 58 is used to cancel changes to the detailed settings on the detailed settings screen 50 and return to the task settings screen 40. The Set button 59 is used to reflect the changes to the detailed settings on the detailed settings screen 50 to the corresponding task and return to the task settings screen 40. Depending on the detailed settings of each task on the detailed settings screen 50, the execution or execution support operation of the task by the execution control unit 217, which will be described later, will change.

[0133] Referring again to Figure 8B, the back button 48 is used to cancel the task settings on the task setting screen 40 and return to the schedule registration screen 30. The complete button 49 is used to complete the task settings on the task setting screen 40. When the complete button 49 is pressed, the task management unit 215 generates task information based on the settings received on the task setting screen 40 and the detailed settings screen 50, and registers the generated task information in the task table 273.

[0134] Furthermore, as shown in the example in Figure 8C, if the system-driven generation of thumbnail images is enabled in the detailed settings of the first task T1, task information for the second task T2 for generating thumbnail images may be generated in addition to the task information for the first task T1. Similarly, if the system-driven generation of messages is enabled in the detailed settings of the first task T1, task information for the third task T3 for generating messages for information dissemination may be generated in addition to the task information for the first task T1.

[0135] The detailed settings items displayed in the detailed settings area 51 of the detailed settings screen 50 vary depending on the task type of the task for which the detailed settings are applied.

[0136] For example, the detailed settings for "direct messages" may include a list of 15 viewers to whom direct messages will be sent, in addition to the detailed settings for "SNS posts."

[0137] The detailed settings for "thumbnail generation" may include strings added to prompts entered into the image generation model (for example, keywords selected by broadcaster 10 or free strings). The detailed settings for "message generation" may include strings added to prompts entered into the text generation model (for example, keywords selected by broadcaster 10 or free strings).

[0138] The detailed settings for "Streamer Actions" may include the type of "Streamer Action" and, if a specific viewer 15 is the target of the action, the viewer ID or username of that viewer 15.

[0139] The detailed settings for "Generate Shortened Version" may include the length of the shortened version to be generated. The detailed settings for "Publish Shortened Version" may include the settings for the communication channel used for publication. The same applies to "Generate Archive" and "Publish Archive".

[0140] Figure 9 is an explanatory diagram showing an example of the configuration of a customization screen for accepting customization of task templates. Referring to Figure 9, the customization screen 60 includes a source selection field 61, a template name input field 62, a pre-delivery task editing area 63a, a delivery task editing area 63b, a post-delivery task editing area 63c, a cancel button 68, and a complete button 69.

[0141] The customization source selection field 61 is an object that accepts the selection of a task template to be used as the basis for customization. In the example in Figure 9, a task template named "Basic Template" is selected. This task template may be a common template or a registered template specific to the distributor. The template name input field 62 is an object that accepts the input of the name of the customized task template.

[0142] The pre-delivery task editing area 63a, the in-delivery task editing area 63b, and the post-delivery task editing area 63c are areas for editing the lists of pre-delivery tasks, in-delivery tasks, and post-delivery tasks, respectively. The pre-delivery task editing area 63a includes an add candidate button 64, as well as a delete candidate button 65, a type selection field 66, and a timing selection field 67 for each task candidate. The add candidate button 64 is a button for adding a task candidate to the list of pre-delivery tasks. The delete candidate button 65 is a button for removing an existing task candidate from the list. The type selection field 66 is an object for selecting or changing the task type of an existing task candidate. The timing selection field 67 is an object for selecting or changing the execution timing of an existing task candidate.

[0143] The distributor 10 can customize the list of task candidates for pre-delivery tasks defined by the task template by manipulating these objects in the pre-delivery task editing area 63a. Similarly, the distributor 10 can customize the list of task candidates for tasks being delivered in the in-delivery task editing area 63b, and the list of task candidates for post-delivery tasks in the post-delivery task editing area 63c.

[0144] The Cancel button 68 is used to cancel the customization of the task template on the customization screen 60 and close the customization screen 60. The Complete button 69 is used to complete the customization of the task template. When the Complete button 69 is pressed, the Task Management Unit 215 reflects the customization details received on the customization screen 60 into the second template table 274.

[0145] As explained here, by pre-storing task templates that define sets of task candidates, and generating a list of tasks to be performed based on the task templates and delivery schedule information, it is possible to easily and quickly provide a list of tasks necessary and sufficient for activating content delivery. Furthermore, by making the task templates customizable by the deliverers, it is possible to flexibly provide task templates that suit the needs of individual deliverers. In addition, by providing multiple options for task templates, deliverers can easily switch the list of tasks according to the positioning of the content delivery event. For example, the first task template may define more task candidates for important events, while the second task template may define fewer task candidates for ordinary events.

[0146] <3-5. Task Execution / Execution Support> The execution control unit 217 executes or assists in the execution of at least one task related to content distribution scheduled by the distributor 10, in accordance with the task information registered in the task DB 252.

[0147] For example, the execution control unit 217 compares the current date and time with the execution timing of each task indicated by the task information registered in the task table 273, and detects tasks whose execution timing has arrived or is approaching. If the execution type of the detected task (hereinafter referred to as the target task) indicates "automatic execution", the execution control unit 217 automatically executes the task. If the execution type of the target task indicates "execution with confirmation", the execution control unit 217 requests confirmation from the distributor 10 regarding the execution of the target task. The execution control unit 217 then executes the target task if approval is given by the distributor 10. Furthermore, if the execution type of the target task indicates "reminder", the execution control unit 217 reminds the distributor 10 via the distribution AP 110 that the time has come for the distributor 10 to execute the target task. The execution control unit 217 may repeat the reminder at predetermined time intervals until the distributor 10 indicates that they have executed the target task through user input to the distribution AP 110.

[0148] (1) First Example - Dissemination of Distribution-Related Information In the first embodiment, the target task is the first task T1. The "task type" of the target task is either "SNS post" or "direct message".

[0149] If the execution type of the first task T1 is "automatic execution", the execution control unit 217 automatically transmits distribution-related information to one or more viewers 15 on a pre-configured communication channel based on the communication channel settings indicated by the "channel used" of the target task.

[0150] For example, the execution control unit 217 can transmit distribution-related information to an unspecified audience 15 on a social networking service (SNS) by calling a function of the application program interface (API) for posting to the SNS and inputting the distribution-related information. The distribution-related information here may include one or both of the pre-generated thumbnail image and message related to content distribution. Alternatively, the execution control unit 217 may send the distribution-related information to a specific audience 15 via SNS direct message (DM) or email.

[0151] If the execution type of the first task T1 indicates "execution with confirmation", the execution control unit 217 generates distribution-related information to be transmitted on a pre-configured communication channel and requests confirmation of the generated distribution-related information from the distributor 10. Then, if the distributor 10 approves the transmission of the distribution-related information, the execution control unit 217 transmits the distribution-related information based on the communication channel settings.

[0152] Figure 10 is an explanatory diagram showing an example of the configuration of a post confirmation screen used to request confirmation from the sender 10 regarding the dissemination of distribution-related information via SNS posting. Referring to Figure 10, the post confirmation screen 70 includes a header area 71, an information confirmation area 72, a cancel button 73, and an execute button 74.

[0153] The header area 71 is an area that displays the delivery schedule information for the related content delivery. The information confirmation area 72 is an area that displays the content of the SNS post that the execution control unit 217 is about to execute. In the example in Figure 10, the information confirmation area 72 includes the message confirmation field B7, the thumbnail confirmation field B8, and the change button B9. The message displayed in the message confirmation field B7 may be a message automatically generated by the execution control unit 217 using the method described later. Here, an example of a message that may be proposed when the first task T1 is a pre-delivery task is illustrated, but if the first task T1 is a delivery task or a post-delivery task, a different message may be generated and proposed to the distributor 10. The distributor 10 is allowed to modify the message in the message confirmation field B7. The thumbnail image displayed in the thumbnail confirmation field B8 may be an image automatically generated by the execution control unit 217 using the method described later. The distributor 10 is allowed to change the thumbnail image by operating the change button B9 and selecting another image.

[0154] The cancel button 73 is used to cancel the execution of the SNS post. The execute button 74 is used to approve the SNS post with the content displayed on the post confirmation screen 70 and to instruct the posting to proceed. When the execute button 74 is pressed, the execution control unit 217 executes the SNS post.

[0155] If the execution type of the first task T1 indicates "reminder," the execution control unit 217 reminds the sender 10 that it should transmit distribution-related information via the communication channel.

[0156] Figure 11 is an explanatory diagram showing an example of the configuration of a reminder screen for reminding the sender 10 about sending distribution-related information. Referring to Figure 11, the reminder screen 75 includes a header area 71, a reminder message area 76, and a close button 79.

[0157] The reminder message area 76 displays a message to notify the distributor 10 that it is time to post on social media regarding the scheduled content distribution and to encourage them to post on social media. The reminder message area 76 also includes checkboxes B10 and B11. When the distributor 10 checks checkbox B10 and operates the close button 79, the execution control unit 217 updates the "execution status" of the target task to "completed" and does not send any further reminders for that task. When the distributor 10 checks checkbox B11 and operates the close button 79, the execution control unit 217 updates the "execution status" of the target task to "cancelled" and does not send any further reminders for that task.

[0158] Although not shown in Figure 11, in the case of a "reminder," the execution control unit 217 may also support the information transmission by the sender 10 by generating and proposing distribution-related information (e.g., a message and / or a thumbnail image) to be transmitted over the communication channel. Furthermore, if the task type is a "direct message," the execution control unit 217 may also support the information transmission by the sender 10 by selecting and proposing candidate recipients for the message from the viewer table 266.

[0159] As described above, in the first embodiment, the task management system 1 transmits distribution-related information on behalf of the distributor or assists the distributor in transmitting distribution-related information through the communication channel between the distributor and the viewer. This reduces the burden on the distributor associated with preparing and executing the task of disseminating information. In addition, by conveying distribution-related information to viewers in a timely manner, the number of viewers participating in content distribution increases, and the loyalty of individual viewers also improves.

[0160] (2) Second Example - Generation of Thumbnail Images In the second embodiment, the target task is the second task T2. The "task type" of the target task is "thumbnail generation".

[0161] If the execution type of the second task T2 is "automatic execution", the execution control unit 217 automatically generates a thumbnail image to be used when transmitting distribution-related information on the communication channel, based on the distribution schedule information acquired in advance.

[0162] For example, the execution control unit 217 may generate a thumbnail image by inputting a generation command based on the content distribution theme and / or avatar-related information to the image generation model 221. The generation command here may include a so-called prompt and the specification of one or more control parameters associated with the prompt. The prompt may include at least an instruction statement that triggers the generation process, and may further include a description of the conditions that the output image must satisfy. The control parameters may include, for example, the file path of a reference image to be referenced in the generation of the thumbnail image, the size of the thumbnail image, and the file format of the thumbnail image. Any known Text-to-Image (or Text-to-Video) model may be used as the image generation model 221, such as Stability AI's Stable Diffusion, OpenAI's Sora, or xAI's Grok®. The avatar-related information here may include text information such as avatar attributes or part types, or it may include image information representing the avatar image.

[0163] As a concrete example, Stable Diffusion has the functionality to generate new images according to conditions specified by prompts while maintaining the features of a reference image, using a library called ControlNet. When "Reference_Only" is set as a control parameter in ControlNet, a new image is generated in which the character's appearance in the reference image is maintained, but the character's expression and pose are changed. Therefore, the execution control unit 217 can specify a base avatar image as the reference image and provide prompts to the Stable Diffusion-based image generation model based on the content distribution theme, the date and time of distribution, or the names of the avatar parts to be used for distribution, thereby obtaining a thumbnail image as model output that includes an avatar image that displays an expression and pose suitable for that content distribution.

[0164] Alternatively, the execution control unit 217 may generate thumbnail images based on avatar-related information using a non-AI-based method that does not rely on the image generation model 221. For example, the execution control unit 217 can generate thumbnail images by superimposing avatar images (and any other objects) based on avatar configuration data and parts data onto a background image.

[0165] If the execution type of the second task T2 indicates "execution with confirmation," the execution control unit 217 requests the distributor 10 to confirm the thumbnail image generated based on the distribution schedule information. Then, if the distributor 10 approves the generated thumbnail image, the execution control unit 217 saves the thumbnail image for subsequent information distribution.

[0166] The execution control unit 217 may display multiple thumbnail image candidates on the screen of the distribution AP 110 and allow the distributor 10 to select one of these candidates. Figure 12 is an explanatory diagram showing an example of the configuration of a thumbnail selection screen for allowing the distributor 10 to select a thumbnail image. Referring to Figure 12, the thumbnail selection screen 80 includes a header area 71, a candidate display area 81, a hint input field 82, a candidate generation button 83, and an OK button 84.

[0167] The candidate display area 81 displays three candidate thumbnail images generated by the execution control unit 217. The candidate display area 81 also includes radio buttons B12 corresponding to the three candidates. The broadcaster 10 can select one of the displayed three candidates as the thumbnail image by operating the radio buttons B12.

[0168] Furthermore, when the broadcaster 10 operates the candidate generation button 83, the execution control unit 217 generates other candidate thumbnail images and displays them in the candidate display area 81. The hint input field 82 is a field for receiving input of a string to be used as a hint when the execution control unit 217 generates candidate thumbnail images. For example, the execution control unit 217 may generate a prompt to be input to the image generation model 221 based on the string (and other information such as distribution schedule information) entered by the broadcaster 10 into the hint input field 82. When the broadcaster 10 operates the OK button 84, the execution control unit 217 saves the candidate selected by radio button B12 as a thumbnail image to be used for disseminating information.

[0169] If the execution type of the second task T2 is "reminder," the execution control unit 217 reminds the distributor 10 that a thumbnail image for information dissemination should be generated. The configuration of the reminder screen for the second task T2 reminder may be the same as the configuration of the reminder screen 75 shown in Figure 11, so its explanation is omitted here.

[0170] As described above, in the second embodiment, the task management system 1 generates thumbnail images used in information dissemination from the distributor to the audience on behalf of the distributor, or assists the distributor in generating or selecting thumbnail images. This reduces the burden on the distributor in preparing information dissemination. Furthermore, since it is possible to easily prepare thumbnail images that attract viewers, it is possible to effectively increase viewers' interest in content distribution and increase the number of viewers participating in content distribution.

[0171] (3) Third embodiment - Message generation In the third embodiment, the target task is the third task T3. The "task type" of the target task is "message generation".

[0172] If the execution type of the third task T3 is "automatic execution", the execution control unit 217 automatically generates a message to be transmitted on the communication channel based on the distribution schedule information acquired in advance.

[0173] For example, the execution control unit 217 may generate a message by inputting a generation command based on the content distribution theme and / or avatar-related information to the text generation model 223. The generation command here may include a so-called prompt and the specification of control parameters associated with the prompt. The prompt may include at least an instruction that triggers the generation process and may further include a description of the conditions that the output message must satisfy. The control parameters may include, for example, the length of the message and the language of the message. Any known text-to-text model may be used as the text generation model 223, such as OpenAI's ChatGPT®, Anthropic's Claude®, or Google DeepMind's Gemini®.

[0174] The execution control unit 217 may change the generation instructions input to the text generation model 223 depending on whether the target task is a pre-delivery task, a delivery task, or a post-delivery task. For example, if the target task is a pre-delivery task, keywords encouraging participation in a future event may be inserted into the prompt. If the target task is a delivery task, keywords highlighting the appeal of the ongoing event may be inserted into the prompt. If the target task is a post-delivery task, keywords expressing gratitude for the completed event may be inserted into the prompt. This makes the content of the generated message more appropriate to the execution timing of the target task. The same applies to the input of prompts to the image generation model 221 in the second task T2.

[0175] If the execution type of the third task T3 indicates "execution with confirmation," the execution control unit 217 requests the sender 10 to confirm the message generated based on the distribution schedule information. Then, if the sender 10 approves the generated message, the execution control unit 217 saves the message for subsequent information transmission.

[0176] The execution control unit 217 may display multiple message candidates on the screen of the distribution AP 110 and allow the distributor 10 to select one of these candidates. The configuration of the selection screen for selecting a message in the third task T3 may be the same as the configuration of the thumbnail selection screen 80 shown in Figure 12, so its explanation is omitted here.

[0177] Furthermore, when generating messages for information dissemination, the execution control unit 217 may accept a string to be used as input to the text generation model 223 when generating the message via a UI object such as the hint input field 82 in Figure 12. Alternatively, the execution control unit 217 may present the sender 10 with several candidate strings useful as input to the text generation model 223 (for example, "invitation", "emotional", "excitement", etc.), and insert the string selected by the sender 10 into the prompt.

[0178] If the execution type of the third task T3 is "reminder," the execution control unit 217 reminds the sender 10 that it should generate a message for sending information. The configuration of the reminder screen for the third task T3 may be the same as the configuration of the reminder screen 75 shown in Figure 11, so its explanation is omitted here.

[0179] As described above, in the third embodiment, the task management system 1 generates messages used in information dissemination from the distributor to the audience on behalf of the distributor, or assists the distributor in generating or selecting messages. This reduces the burden on the distributor in preparing information dissemination. Furthermore, since it is possible to easily prepare messages that will attract audiences, it is possible to effectively increase audience interest in content distribution and increase the number of audiences participating in content distribution.

[0180] (4) Improving the performance of the trained model's output The execution control unit 217 may improve the output performance of the image generation model 221 used in the second embodiment and / or the text generation model 223 used in the third embodiment by additional training.

[0181] For example, the execution control unit 217 may update the image generation model 221 by providing feedback to the distributor 10 indicating whether or not a candidate thumbnail image presented to the distributor 10 has been selected for information dissemination. Similarly, the execution control unit 217 may update the text generation model 223 by providing feedback to the distributor 10 indicating whether or not a candidate message presented to the distributor 10 has been selected for information dissemination.

[0182] As another example, the execution control unit 217 may collect statistical data on reactions to posts on social media from the social media provision unit 213 and update the image generation model 221 or text generation model 223 so that it is easier to obtain model outputs that are similar to thumbnail images or messages that have received more positive reactions.

[0183] Additionally or alternatively, the execution control unit 217 may improve the performance of the output of the image generation model 221 and / or the text generation model 223 by incorporating a Search Enhanced Generation (RAG) mechanism. For example, the database 250 may additionally have a knowledge table referenced by the execution control unit 217 to enhance prompts in RAG. The knowledge table may hold, as knowledge for RAG, one or more of the thumbnail images, avatar images, part images, messages, phrases, and keywords that the distributor 10 has used for information dissemination in the past, in a searchable format using information such as the content distributor, distribution timing, theme, or avatar used as a key. The knowledge may be pre-selected to be referenced in future generation tasks (for example, those included in information dissemination that received more positive reactions). The execution control unit 217 can use the knowledge obtained through searching in these knowledge tables to extend the prompts when generating thumbnail images or messages, thereby obtaining a more appropriate model output that matches the characteristics of the broadcaster, or a model output that more effectively increases the interest of viewers.

[0184] Additionally or alternatively, the execution control unit 217 may improve the performance of the output of the image generation model 221 and / or the text generation model 223 using the fusion shot prompt technique. In the fusion shot prompt, the database 250 may also have additional tables similar to the knowledge table for RAG described above. The execution control unit 217 then provides the model with at least one preliminary prompt based on the knowledge obtained through searching in the table, and then inputs a prompt to the model for generating the final thumbnail image or message. This makes it possible to obtain a more appropriate model output that is suited to the characteristics of the broadcaster, or a model output that more effectively increases the interest of the audience.

[0185] (5) Fourth embodiment - Distributor actions during content distribution In the fourth embodiment, the target task is the fourth task T4. The "task type" of the target task is "distributor action".

[0186] If the execution type of the fourth task T4 is "automatic execution", the execution control unit 217 instructs the distribution control unit 211 to execute a pre-configured distributor action at the timing indicated by the "execution timing" of the target task during content distribution.

[0187] The execution control unit 217 may instruct the distribution control unit 211 to select a viewer 15 to whom the broadcaster action will be performed. For example, by performing a broadcaster action to express gratitude to a viewer 15 who participated in the previous content distribution for the first time, it is expected that the viewer 15 will be more likely to repeat the content distribution. Also, by displaying a special greeting comment to a viewer 15 who has sent gifts multiple times, it is expected that the viewer 15 will maintain a high level of loyalty.

[0188] If the execution type of the fourth task T4 indicates "execution with confirmation", the execution control unit 217 requests confirmation from the distributor 10 via the distribution AP 110 regarding the execution of the distributor action during content distribution. Then, if approval is given by the distributor 10, the execution control unit 217 instructs the distribution control unit 211 to execute the distributor action.

[0189] If the execution type of the fourth task T4 is "reminder," the execution control unit 217 reminds the distributor 10 to perform a distributor action via the distribution AP 110 during content distribution. In this case, the distributor 10, upon seeing the reminder, operates the distribution AP 110 to perform the distributor action. The execution control unit 217 may also suggest which viewer 15 should receive the distributor action on the screen that reminds the distributor to perform the distributor action.

[0190] As described above, in the fourth embodiment, the task management system 1 performs pre-configured distributor actions on behalf of the distributor or assists the distributor in performing distributor actions during content distribution. This reduces the burden on the distributor associated with the parallel tasks of content distribution and the execution of appropriate distributor actions. Furthermore, the interaction between the distributor and viewers on the distribution platform deepens, improving the repeat viewing rate and loyalty of viewers to the content distribution.

[0191] (6) Selecting action partners based on activity statistics The activity table 275 in task DB252 is a table that holds activity data to enable more effective distributor actions. The activity table 275 may include, for example, one or more of the following information items: "Streamer" "Viewers" "Total number of times participated" "Total number of actions" "Cumulative payment amount" "Previous participation flag" In this embodiment, the distribution control unit 211 aggregates activity data for each pair of distributor 10 and viewer 15. Therefore, the key of the activity table 275 is the combination of "distributor" indicating the distributor ID and "viewer" indicating the viewer ID. "Cumulative participation count" indicates the cumulative number of times that "viewers" have participated in past content distributions conducted by "distributors". "Cumulative action count" indicates the cumulative number of times that "viewers" have performed some kind of action in past content distributions conducted by "distributors". "Cumulative action count" may be aggregated separately for each type of action. "Cumulative payment amount" indicates the total amount of currency paid by "viewers" in past content distributions conducted by "distributors", for example, by tipping. "Previous participation flag" indicates whether or not "viewers" participated in the previous content distribution conducted by "distributors". In addition to the "Previous participation flag", or instead, the activity table 275 may include information items that indicate the participation status of "viewers" in past content distributions conducted by "distributors". The participation status here may include, for example, whether or not you have participated in any past content distribution, whether or not you have participated in any content distribution within a certain period in the past, and / or the number of days that have passed since your last participation in a content distribution.

[0192] The execution control unit 217 may select the audience 15 to be the recipient of the broadcaster action during each content distribution by referring to the activity data in the activity table 275.

[0193] Alternatively, the execution control unit 217 may support the broadcaster 10 in performing broadcaster actions by displaying activity data for each viewer 15 currently participating in the content broadcast on the screen of the broadcast AP 110. For example, a special mark may be placed on the icon or username of a viewer 15 who participated in the previous content broadcast for the first time on the screen of the broadcast AP 110. This would allow the broadcaster 10 to easily identify that viewer 15 and send them a special comment.

[0194] (7) Fifth Example - Generation of Shortened Version / Archive In the fifth embodiment, the target task is the fifth task T5. The "task type" of the target task is either "generate shortened version" or "generate archive".

[0195] If the execution type of the fifth task T5 is "automatic execution", the execution control unit 217 automatically generates a shortened version or archive of the distributed content after the content distribution is completed. The method for generating the shortened version of the content may be any known method, such as the method described in Patent Document 2. The execution control unit 217 may also generate the title of the shortened version or archive of the content by inputting a generation command based on the theme and / or avatar-related information of the content distribution to the text generation model 223.

[0196] If the execution type of Task 5 T5 indicates "Execution with Confirmation," the execution control unit 217 requests the distributor 10 to confirm the generated shortened version or archive. Then, if the distributor 10 approves the shortened version or archive, the execution control unit 217 saves the shortened version or archive for subsequent publication.

[0197] If the execution type of the fifth task T5 is "reminder," the execution control unit 217 reminds the distributor 10 that a shortened version or archive of the distributed content should be generated. The configuration of the reminder screen for the fifth task T5 reminder may be the same as the configuration of the reminder screen 75 shown in Figure 11, so its explanation is omitted here.

[0198] As described above, in the fifth embodiment, the task management system 1 generates a shortened version or archive of the content that is desirable to be published after content distribution on behalf of the distributor, or assists the distributor in generating such a version. This reduces the burden on the distributor associated with editing video content.

[0199] (8) Sixth Example - Publication of Shortened Version / Archive In the sixth embodiment, the target task is the sixth task, T6. The "task type" of the target task is either "short version release" or "archive release".

[0200] If the execution type of the sixth task T6 is "automatic execution", the execution control unit 217 publishes a shortened version or archive of the generated content, as described in the fifth embodiment, on a pre-configured communication channel based on the communication channel settings indicated by the "usage channel" of the target task.

[0201] For example, the execution control unit 217 can call an API function for posting to a social networking service (SNS) to publish a shortened version or archive of the content on that SNS. Alternatively, the execution control unit 217 may upload the shortened version or archive to the website of a pre-configured distributor 10.

[0202] If the execution type of Task 6 T6 indicates "Execution with Confirmation," the execution control unit 217 requests confirmation from the distributor 10 regarding the publication of the shortened version or archive. Then, if the distributor 10 approves the publication, the execution control unit 217 publishes the shortened version or archive.

[0203] If the execution type of Task 6 T6 is "Reminder", the execution control unit 217 reminds the distributor 10 that a shortened version or archive of the distributed content should be made public. The configuration of the reminder screen for Task 6 T6 may be the same as the configuration of the reminder screen 75 shown in Figure 11, so its explanation is omitted here.

[0204] As described above, in the sixth embodiment, the task management system 1 publishes a shortened version or archive of the content on behalf of the distributor after content distribution, or assists the distributor in publishing it. As a result, the shortened version or archive is reliably published, and more viewers 15 become aware of the content distribution by the distributor 10.

[0205] <3-6. Examples of prompts> The execution control unit 217 can utilize the generation AI for the execution of several tasks. The execution control unit 217 may choose whether or not to use the generation AI for the execution of a task depending on the task type. The execution control unit 217 may also switch the generation instructions input to the generation AI depending on the task type. The task DB 252 (for example, the second template table 274 or another table) may store predefined templates of generation instructions or prompts for each task type.

[0206] As described above, a generation command includes at least a prompt, which is an instruction that triggers the generation process. Depending on the specifications of the generation AI, a generation command may further include the specification of one or more control parameters. Note that conditions described herein as being specified by control parameters may be specified within the prompt, and conditions described herein as being specified within the prompt may be specified by control parameters separate from the prompt.

[0207] The following describes some examples of prompts (templates) that the execution control unit 217 can input to the generated AI.

[0208] Figure 13 is an explanatory diagram showing an example of prompts that may be input to the image generation model 221 for generating thumbnail images. In the example in Figure 13, prompt 91 is written using so-called Markdown notation and includes four segments: "background," "generation instructions," "DB data," and "conditions."

[0209] The "Background" segment describes the basic behavior required of the image generation model 221. The "Generation Instructions" segment describes the main instruction statements that trigger the generation process. The "DB Data" segment describes one or more input values ​​for the generation process that vary from task to task. The "Conditions" segment describes the conditions that the output thumbnail image must satisfy.

[0210] In "DB Data," strings enclosed in double brackets "{{" and "}}" represent variables whose values ​​change for each task. In the example in Figure 13, "DB Data" includes the following six variables: "Streamer: {{user_name}}" "Date and time: {{distribution_dateandtime}}" "Theme: {{distribution_theme}}" "Avatar appearance: {{avatar_appearance}}" "Tone: {{thumbnail_tone}}" "Target audience: {{target_viewers}}"

[0211] For example, the execution control unit 217 may set the username of the distributor obtained from the distributor table 263 as the value of the variable user_name. The execution control unit 217 may also set the date and time and theme of the content distribution obtained from the distribution table 271 as the values ​​of the variables distribution_dateandtime and distribution_theme, respectively. Furthermore, the execution control unit 217 may set the avatar configuration data of the avatar being used (e.g., a list of parts) obtained from the avatar table 264 as the value of the variable avatar_appearance. Alternatively, the file path of the avatar image data of the avatar being used may be set.

[0212] The variables thumbnail_tone and target_viewers are additional variables that may be specified for the task of generating thumbnail images. The variable thumbnail_tone may be a keyword that describes the atmosphere that the thumbnail image should express, such as "cute," "cool," or "lively." The variable target_viewers may be a keyword that identifies the audience that the thumbnail image is intended to attract, such as "followers," "general," or "young people." These keywords may be pre-selected by the broadcaster and stored in the broadcast table 271 as part of the broadcast event information, or they may be selected in the detailed settings screen 50 and stored in the task table 273 as part of the task's detailed settings.

[0213] In the example in Figure 13, the "generation instruction" includes a statement instructing the image generation model 221 to generate three different thumbnail images. The "conditions" include conditions regarding the format of these thumbnail images, as well as conditions regarding image features that the three options should commonly represent (the appearance of the avatar), and image features that should be represented differently (accessories, effects, and text within the image). This prompt configuration allows the generation AI to generate multiple thumbnail images that all feature the avatar used for content distribution, but which give different impressions to the viewer.

[0214] Figures 14A to 14C are explanatory diagrams showing three examples of prompts that can be input to the text generation model 223 for generating messages for SNS posting. In the first example in Figure 14A, prompt 92a is for message generation as a pre-delivery task. In the second example in Figure 14B, prompt 92b is for message generation as an in-delivery task. In the third example in Figure 14C, prompt 92c is for message generation as a post-delivery task. Naturally, thumbnail generation and other tasks may also be subdivided in a similar manner according to the classification of their execution timing.

[0215] In the first example in Figure 14A, prompt 92a includes four segments: "Background," "Generation Instructions," "DB Data," and "Conditions." The "DB Data" in prompt 92a includes the following six variables: "Streamer: {{user_name}}" "Date and time: {{distribution_dateandtime}}" "Theme: {{distribution_theme}}" "Avatar attribute: {{avatar_character}}" "URL:{{distribution_url}}" "Target audience: {{target_viewers}}"

[0216] For example, the execution control unit 217 may set the avatar attribute data of the avatar being used (e.g., gender, age, and personality) obtained from the avatar table 264 as the value of the variable avatar_character. The execution control unit 217 may also set the URL of the content distribution access destination obtained from the distribution table 271 as the value of the variable distribution_url.

[0217] The "generation instruction" in prompt 92a includes an instruction that tells the text generation model 223 to generate three message options. The "conditions" include conditions regarding the format of those messages, as well as conditions regarding message characteristics common to the three options (tone of voice that matches the avatar attributes) and different characteristics (strength of appeal). This prompt configuration allows the generation AI to generate multiple different text message options to increase viewer interest while maintaining consistency in the avatar character used for content distribution.

[0218] In the second example in Figure 14B, prompt 92b includes four segments: "Background," "Generation Instructions," "DB Data," and "Conditions." The "DB Data" in prompt 92b includes the following four variables: "Streamer: {{user_name}}" "Avatar attribute: {{avatar_character}}" "URL:{{distribution_url}}" "Topic: {{ongoing_topic}}"

[0219] For example, the execution control unit 217 may obtain audio data for currently ongoing content distribution from the distribution control unit 211 and set a string indicating the topic recognized from the audio data as the value of the variable ongoing_topic.

[0220] The "generation instruction" in prompt 92b includes an instruction that tells the text generation model 223 to generate two drafts of the message. The "conditions" include the conditions that the message generated by the text generation model 223 must satisfy. In particular, unlike prompt 92a described above, prompt 92b specifies that the generated message must satisfy the condition that it must include a phrase meaning "it's not too late," a URL for the broadcast, and a string indicating the topic currently being discussed. By automatically generating a message for SNS posting that satisfies these conditions, broadcasters do not have to bear a heavy workload of creating SNS posts aimed at attracting more viewers to the event in parallel with content distribution.

[0221] In the third example in Figure 14C, prompt 92c includes five segments: "background," "generation instructions," "DB data," "transcription data," and "conditions."

[0222] The "DB data" in prompt 92c includes the following two variables: "Streamer: {{user_name}}" "Avatar attribute: {{avatar_character}}"

[0223] The "transcription data" prompt 92c contains the file path required for the text generation model 223 to access the transcript data of the completed content distribution. The transcript data here may be text data that describes the content of the distribution as recognized based on the audio data of the content distribution in text format. Alternatively, instead of transcript data, the video data and / or audio data of the content distribution may be provided as data representing the content of the completed content distribution.

[0224] The "generation instruction" in prompt 92c includes an instruction that tells the text generation model 223 to generate a draft message. The "conditions" include the conditions that the message generated by the text generation model 223 must satisfy. In particular, prompt 92c specifies that the generated message should include a phrase expressing gratitude to the audience, the broadcaster's thoughts from their perspective, and a three-line summary based on the transcript data. By automatically generating a message for social media posting that meets these conditions, broadcasters are relieved of the burden of creating social media posts after the content distribution has ended, which are intended to maintain the loyalty of viewers who participated in the broadcast and to increase the interest of non-participants in the next broadcast.

[0225] The prompts described using Figures 13 to 14C may be modified in any way depending on the purpose of the task. For example, the execution control unit 217 may add an instruction to the prompt to include tags in the message generated by the text generation model 223 to improve the searchability of posts on social networking services. Alternatively, tags predetermined by the distributor and stored in the task DB 252 may be specified as "DB data" as tags to be included in the message.

[0226] As explained in this section, by adaptively switching the generation commands input to the generation AI according to the task type, it is possible to reduce the burden on the broadcaster while effectively communicating with viewers by utilizing the generation AI.

[0227] <4. Details of the broadcaster's device functions> Figure 15 is a block diagram showing an example of the functional configuration of a distributor terminal 100 according to one embodiment. Referring to Figure 15, the distributor terminal 100 includes a content acquisition unit 111, a motion tracking unit 113, a display control unit 115, and an information acquisition unit 117.

[0228] When the content acquisition unit 111 receives an instruction from the distributor 10 to start content distribution, it outputs video data of the distributor's video captured by the camera 101 to the motion tracking unit 113. The content acquisition unit 111 also transmits audio data of the voice acquired by the microphone 102 to the management server 200.

[0229] In this embodiment, the motion tracking unit 113 performs motion tracking S1 on the broadcaster video input from the content acquisition unit 111 to detect the broadcaster's movements and generates motion data indicating the detection results. The motion tracking unit 113 then transmits the motion data to the management server 200.

[0230] The display control unit 115 works in conjunction with the management module 210 of the management server 200 to control the display of various screens provided to the distributor 10 by the distribution AP 110. The information acquisition unit 117 acquires various information that is input or selected by the distributor 10 using the input device 104 on the screen displayed on the display 105 of the distributor terminal 100.

[0231] For example, the display control unit 115 displays the content distribution screen described in relation to Figure 2 on the display 105 from the start to the end of content distribution, and plays video content on the content distribution screen. In addition, when the SNS function is called by the distributor 10, the display control unit 115 displays the post viewing screen described in relation to Figure 4 on the display 105, and displays posts from SNS users on the post viewing screen.

[0232] Also, when the next content delivery is planned by the distributor 10, the display control unit 115 causes the display 105 to display the scheduled registration screen 30 described using FIG. 8A. The information acquisition unit 117 acquires distribution schedule information about the content delivery scheduled by the distributor 10 via the scheduled registration screen 30, and transmits the acquired distribution schedule information to the management server 200. The distribution schedule information here may be information edited by the distributor 10 based on the above-described distribution schedule template.

[0233] Also, when the task management agent is activated for content delivery by the distributor 10, the display control unit 115 causes the display 105 to display the task setting screen 40 described using FIG. 8B. Further, the display control unit 115 causes the display 105 to display the detailed setting screen 50 described using FIG. 8C in response to an operation by the distributor 10. The information acquisition unit 117 acquires setting information related to one or more tasks via the task setting screen 40 and the detailed setting screen 50. The setting information acquired here may indicate a list of tasks determined by the distributor 10 based on the above-described task template. Also, the setting information acquired here may indicate the setting of the communication channel to be used for the task of information transmission. The information acquisition unit 117 transmits the acquired setting information to the management server 200. Then, as described above, the task information generated by the management server 200 is registered in the task table 273.

[0234] Also, when executing a task whose execution type indicates "execution with confirmation", the display control unit 115 may cause the display 105 to display a confirmation screen that requests the distributor 10 for approval of the task execution, similar to that described using FIG. 10.

[0235] Also, in order to assist in the execution of a task whose execution type indicates "reminder", the display control unit 115 may cause the display 105 to display a reminder screen similar to that described using FIG. 11.

[0236] Note that the functional elements of the management server 200 shown in FIG. 7 and the functional elements of the distributor terminal 100 shown in FIG. 15 may be arranged among the devices constituting the task management system 1 in any manner. For example, the distribution AP 110 of the distributor terminal 100 may provide a task management function equivalent to the task management unit 215 or a subset thereof. Also, the distribution AP 110 may provide a task execution (execution support) function equivalent to the execution control unit 217 or a subset thereof. Further, a third-party SNS application installed in the distributor terminal 100 may be used for providing the SNS. Conversely, the functional elements of the management server 200 that receive arbitrary information from the distributor terminal 100 may be regarded as an information acquisition unit.

[0237] Also, part or all of the data described as being stored in the database 250 of the management server 200 may be stored in and used by the storage 107 or the memory 108 of the distributor terminal 100.

[0238] Furthermore, each of the image generation model 221 and the text generation model 223 described as being stored in the storage 107 of the management server 200 may be stored in and used by the storage 107 or the memory 108 of the distributor terminal 100 as a more lightweight learned model.

[0239] <5. Flow of Processing> In this section, the flow of processing in the task management system 1 will be described. FIG. 16 is a sequence diagram showing an example of the flow of task management processing according to an embodiment. The task management processing in FIG. 16 involves the distributor terminal 100, a plurality of viewer terminals 150a, 150b, and the management server 200. Note that in the sequence diagram described below, the initial 'S' of the reference numerals is an abbreviation for processing steps.

[0240] Referring to Figure 16, first, in S101, the task management unit 215 of the management server 200 displays the schedule registration screen 30 on the display 105 of the distributor terminal 100. For example, the task management unit 215 may display the schedule registration screen 30 in response to the distributor 10 calling up the schedule registration screen 30 by operating the function menu of the distribution AP 110. Alternatively, the task management unit 215 may display the schedule registration screen 30 based on the content distribution scheduling pattern pre-registered in the first template table 272.

[0241] Next, in S102, the information acquisition unit 117 of the distributor terminal 100 acquires the distribution schedule information entered by the distributor 10 on the schedule registration screen 30 (or edited based on the distribution schedule template).

[0242] Next, in S103, the information acquisition unit 117 transmits the acquired distribution schedule information to the management server 200. The task management unit 215 of the management server 200 receives the distribution schedule information.

[0243] Next, in S104, the task management unit 215 registers the distribution schedule information received in S103 into the distribution table 271.

[0244] Next, in S106, the task management unit 215 displays the task settings screen 40 on the display 105 of the distributor terminal 100. Although not shown in Figure 16, the task management unit 215 may also display the detailed settings screen 50 in response to a request from the distributor 10.

[0245] Next, in S107, the information acquisition unit 117 of the distributor terminal 100 acquires the settings for one or more tasks that are entered by the distributor 10 on the task setting screen 40 (or edited based on a task template).

[0246] Next, in S108, the information acquisition unit 117 sends the acquired task settings to the management server 200. The task management unit 215 of the management server 200 receives the task settings.

[0247] Next, in S109, the task management unit 215 generates task information indicating one or more tasks based on the distribution schedule information received in S103 and the task settings received in S108, and registers the generated task information in the task table 273 in association with the content distribution scheduled by the distributor 10.

[0248] Subsequently, in S111, when the scheduled timing for a pre-distribution task arrives before content distribution, the execution control unit 217 executes the pre-distribution task or assists the distributor 10 in executing the pre-distribution task. For example, in S112, information related to content distribution is transmitted to viewer terminals 150a and 150b.

[0249] Furthermore, in S121, when the scheduled timing for a task being delivered arrives during content delivery, the execution control unit 217 executes the task being delivered or assists the delivery person 10 in executing the task being delivered. For example, in S122, a specific delivery person action is performed on one or both of the viewers of viewer terminals 150a and 150b.

[0250] Furthermore, in S131, when the scheduled timing for a post-distribution task arrives after content distribution, the execution control unit 217 executes the post-distribution task or assists the distributor 10 in executing the post-distribution task. For example, in S132, an archive of the distributed content is made public on some communication channel.

[0251] Figure 16 shows one pre-delivery task, one in-delivery task, and one post-delivery task, but the number and type of tasks executed are not limited to the example described above.

[0252] <6. Summary> Up to this point, various embodiments, examples, and modifications of the technology relating to this disclosure have been described. In the embodiments described above, a task management system for content distributors is provided. The task management system acquires distribution schedule information for content distributions scheduled by the distributor, and based on the acquired distribution schedule information, registers task information indicating one or more tasks related to content distribution in a database, associating it with the content distribution. The task management system then executes at least one task according to the task information registered in the database, or assists in the execution of said at least one task. With such a configuration, the burden on distributors related to content distribution can be reduced, interaction between distributors and viewers can be facilitated, and content distribution can be revitalized.

[0253] Furthermore, in the embodiment described above, the task management system displays one or more task candidates related to content distribution on the screen and allows the distributor to select one or more tasks to be executed. Task information indicating the one or more tasks selected by the distributor is then registered in the database. Therefore, the distributor can flexibly determine a task execution plan suitable for each content distribution without missing any desirable task candidates.

[0254] Furthermore, in the above-described embodiment, the distribution schedule information indicates the scheduled timing of content distribution, the task information indicates the execution timing of each task, and the execution timing of each task is determined based on the scheduled timing of content distribution indicated by the distribution schedule information. Therefore, tasks can be managed so that each task is executed in a timely manner without the distributor having to individually determine the execution timing of each task. In particular, by determining the execution timing of each task based on the scheduled timing of content distribution and the type of task, numerous tasks related to content distribution can be appropriately scheduled according to the nature of each task.

[0255] In the above-described embodiment, the task management system can generate a thumbnail image or a message used when transmitting information related to the content distribution to the viewer by inputting a generation command based on the scheduled distribution information of the content distribution to the generation AI model. In this case, the distributor does not have to handle the generation AI model, which generally requires advanced technical knowledge or troublesome trial and error. Therefore, the burden on the distributor associated with executing tasks related to content distribution can be significantly reduced.

[0256] In the above-described embodiment, the content distribution is the distribution of a video in which an avatar that virtually represents the distributor appears. The task management system executes the at least one task or supports the execution of the at least one task based on the avatar-related information stored in the database. By considering the avatar-related information when executing or supporting the execution of the task in this way, the characteristics of the avatar can be reflected in the communication between the distributor and the viewer. Thereby, the interest of the viewer in the content can be increased by the appeal of the avatar, and the number of viewers can be effectively increased.

[0257] The above-described embodiment is typically realized by a processing circuit of an information processing apparatus accessed by a content distributor executing a computer program (a group of program instructions) stored in a memory. The memory here may include a non-temporary computer-readable storage medium. The information processing apparatus accessed by the distributor may include not only a terminal device directly operated by the distributor but also a server device remotely accessed via a network.

[0258] <7. Further Variants> Regarding the above-described embodiment, several further variants can be envisioned.

[0259] <7-1. First Variant> In the first modified example described in this section, instead of obtaining scheduled distribution information before content distribution takes place, distribution event information is obtained in response to the start of content distribution by the distributor 10.

[0260] Figure 17 is a sequence diagram showing an example of the task management process flow related to the first modified example. The task management process in Figure 17 involves a broadcaster terminal 100, multiple viewer terminals 150a, 150b, and a management server 200.

[0261] Referring to Figure 17, first, in S151, the task management unit 215 of the management server 200 obtains distribution event information from the distribution control unit 211 and registers the obtained distribution event information in the distribution table 271.

[0262] During content distribution, in S152, the distribution control unit 211 displays a visual object representing a viewer action on the distributor terminal 100 and the viewer terminal 150b, for example, in response to receiving a viewer action from the viewer terminal 150a. Although Figure 17 shows only one viewer action, multiple viewer actions may occur.

[0263] In S153, the execution control unit 217 aggregates viewer activities, including these viewer actions, and updates the activity data in the activity table 275.

[0264] Once content distribution is complete, at S154, the task management unit 215 displays the task settings screen 40 on the display 105 of the distributor terminal 100. Although not shown in Figure 17, the task management unit 215 may also display the detailed settings screen 50 in response to a request from the distributor 10.

[0265] Next, in S155, the information acquisition unit 117 of the distributor terminal 100 acquires the settings for one or more tasks entered by the distributor 10 (or edited based on a task template) on the task setting screen 40. The one or more tasks here are only post-distribution tasks.

[0266] Next, in S156, the information acquisition unit 117 transmits the acquired task settings to the management server 200. The task management unit 215 of the management server 200 receives the task settings.

[0267] Next, in S157, the task management unit 215 registers task information indicating one or more tasks in the task table 273, associating it with the completed content distribution, based on the distribution event information acquired in S151 and the task settings received in S156.

[0268] Subsequently, in S161 and S171, the execution control unit 217 executes a post-distribution task registered in the task table 273 when the scheduled timing for that task arrives, or assists the distributor 10 in executing the post-distribution task. For example, in S162, a direct message containing distribution-related information generated based on distribution event information is sent to the viewer terminal 150a of a viewer selected based on activity data. Also, in S172, an archive of the distributed content is made public on some communication channel.

[0269] Figure 17 shows an example where task settings are accepted from the distributor 10 on the task setting screen after content distribution is completed, but this modification is not limited to such an example. For example, the task management unit 215 may automatically register task information indicating post-distribution tasks in the task table 273 based on distribution event information, without accepting task settings from the distributor 10 after content distribution is completed. Also, the task DB 252 may store user settings in advance regarding whether or not to display the task setting screen after content distribution is completed. Furthermore, although this modification describes an example in which distribution event information is acquired in response to the start of content distribution by the distributor 10, this modification is not limited to such an example. For example, distribution event information may be acquired in response to the end of content distribution.

[0270] Furthermore, the various features described herein in relation to the task management system 1 are also applicable to the task management process in this modified example, as far as post-delivery tasks are concerned.

[0271] In this modified example, the task management system for content distributors acquires distribution event information about content distributions performed by the distributors, and based on the acquired distribution event information, registers task information indicating one or more tasks related to content distribution in the database, associating it with the content distribution. The task management system then executes or assists in the execution of at least one task according to the task information registered in the database. This configuration also reduces the burden on distributors related to content distribution and can revitalize content distribution.

[0272] <7-2. Second variation> In the second variant described in this section, content distribution is performed on a distribution platform separate from the management server 200.

[0273] Figure 18 is a schematic diagram showing an example of the general configuration of the task management system 2 according to the second modified example. Referring to Figure 18, the task management system 2 includes a network 5, a distributor terminal 100a, an integrated terminal 100b, one or more viewer terminals 150, a management server 200, a distribution server 300, and an SNS server 350.

[0274] The broadcaster terminal 100a and the integration terminal 100b are located within the broadcaster environment 6. The broadcaster terminal 100a and the integration terminal 100b are information processing devices operated by the broadcaster 10. For example, the broadcaster terminal 100a is a smartphone, and the integration terminal 100b is a PC. The broadcaster terminal 100a can communicate with the integration terminal 100b by wire or wireless connection, and can also communicate with other devices via the network 5. The integration terminal 100b can also communicate with other devices via the network 5.

[0275] The integrated terminal 100b is connected to the content source 7. The content source 7 outputs additional content that constitutes part of the content to the integrated terminal 100b. For example, the content source 7 may be a game console that outputs game video or a video camera that outputs live video.

[0276] The broadcaster terminal 100a has the broadcast AP110a installed. The broadcast AP110a may be an application with the same functionality as the broadcast AP110 described above. On the other hand, the integration terminal 100b has the integration AP110b installed, which has the function of integrating multiple content materials. For example, the open-source software OBS (Open Broadcaster Software) Studio can be used as the integration AP110b. The integration AP110b receives avatar video from the broadcast AP110a on the broadcaster terminal 100a, combines the received avatar video with additional content from the content source 7, and generates video content. Then, the integration AP110b transmits the generated video content to the broadcast server 300 via the network 5.

[0277] The distribution server 300 may be a server device that provides the third-party distribution platform exemplified above. The distribution server 300 distributes the video content received from the integrated AP 110b to viewer terminals 150 of one or more viewers 15.

[0278] The SNS server 350 is a server device that provides a third-party SNS platform to the broadcaster 10 and the viewer 15. The SNS server 350 exposes an API for receiving SNS posts and / or direct messages. Therefore, devices other than the SNS server 350 can transmit information on the SNS platform provided by the SNS server 350 by calling the SNS server 350's API.

[0279] In this modified example, the distributor terminal 100a or the integrated terminal 100b may have task management functions equivalent to those of the task management unit 215 described above. Similarly, the distributor terminal 100a or the integrated terminal 100b may have task execution / execution support functions equivalent to those of the execution control unit 217 described above. Generally speaking, the task management functions and task execution / execution support functions may be located in any one of the distributor terminal 100a, the integrated terminal 100b, and the management server 200, or they may be distributed among two or more of them.

[0280] Regardless of how task management and task execution / execution support functions are configured, content distributors can benefit from the reduced workload and increased content distribution achieved by the technology described herein. Platform providers for content distribution can also benefit from the increased content distribution.

[0281] The technical scope of this disclosure is not limited to the embodiments, examples, and modifications described herein. It will be apparent to any person with ordinary skill in the art of this disclosure that various modifications and variations can be conceived without departing from the scope of the technical idea set forth in the claims, and such modifications and variations will naturally fall within the technical scope of this disclosure. [Explanation of Symbols]

[0282] 1,2 Task management system, 10 Streamer, 15 Viewer, 20 Content viewing screen, 25 Post viewing screen, 30 Schedule registration screen, 40 Task settings screen, 50 Detailed settings screen, 60 Customization screen, 70 Post confirmation screen, 75 Reminder screen, 80 Thumbnail selection screen, 100 Streamer terminal, 117 Information acquisition unit, 150 Viewer terminal, 200 Management server, 211 Distribution control unit, 213 SNS provision unit, 215 Task management unit, 217 Execution control unit, 221 Image generation model, 223 Text generation model, 250 Database, 271 Distribution table (Distribution schedule information), 273 Task table (Task information), T1 1st task, T2 2nd task, T3 3rd task, T4 4th task, T5 5th task, T6 6th task, V1 Avatar

Claims

1. A task management system for content distributors, An information acquisition unit that acquires information about the planned content distribution by the aforementioned distributor, A task management unit registers task information indicating one or more tasks related to the content distribution in a database, associated with the content distribution, based on the distribution schedule information. An execution control unit that executes at least one of the one or more tasks, or assists in the execution of said at least one task, according to the task information registered in the database, Includes, The aforementioned scheduled distribution information includes the themes of the aforementioned content distribution, The at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the broadcaster and the viewer over a network, The execution control unit executes the message generation task by inputting a generation command based on the theme of the content distribution to the text generation model. Task management system.

2. A task management system for content distributors, An information acquisition unit that acquires information about the planned content distribution by the aforementioned distributor, A task management unit registers task information indicating one or more tasks related to the content distribution in a database, associated with the content distribution, based on the distribution schedule information. An execution control unit that executes at least one of the one or more tasks, or assists in the execution of said at least one task, according to the task information registered in the database, Includes, The aforementioned scheduled distribution information includes avatar-related information related to the avatar used by the distributor in the aforementioned content distribution, The at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the broadcaster and the viewer over a network, The execution control unit executes the message generation task by inputting generation commands based on the avatar-related information to the text generation model. Task management system.

3. The aforementioned task management unit, Display one or more task candidates related to the content distribution on the screen, and allow the distributor to select one or more tasks to be performed. The task information indicating one or more tasks selected by the distributor is registered in the database. A task management system according to claim 1 or 2.

4. The aforementioned distribution schedule information indicates the planned timing of the content distribution. The task information indicates the execution timing of each task among the one or more tasks, The task management unit determines the execution timing of each task based on the scheduled timing of content distribution indicated by the scheduled distribution information. A task management system according to claim 1 or 2.

5. The task management system according to claim 4, wherein the task management unit determines the execution timing of each task based on the scheduled timing of content distribution and the type of task.

6. The information acquisition unit acquires setting information indicating the setting of the communication channel, The at least one task further includes a message sending task that transmits the message to one or more unspecified or specific viewers on the communication channel, The execution control unit executes the message sending task based on the setting information. A task management system according to claim 1 or 2.

7. The database stores task templates that define one or more sets of task candidates, associated with identifiers that identify the distributor. The task management unit registers the task information in the database, associating it with the content distribution, based on the task template and the scheduled distribution information obtained from the database. A task management system according to claim 1 or 2.

8. The aforementioned database stores multiple task templates that define one or more different sets of task candidates. The task management unit registers the task information in the database, associating it with the content distribution, based on the template selected by the distributor from the multiple task templates and the scheduled distribution information. A task management system according to claim 1 or 2.

9. The database stores a distribution schedule template that defines a candidate distribution schedule information specific to the distributor, associated with an identifier that identifies the distributor. The information acquisition unit acquires the distribution schedule information edited by the distributor based on the distribution schedule template acquired from the database. A task management system according to claim 1 or 2.

10. The aforementioned task management system is A distributor terminal operated by the aforementioned distributor, comprising at least one of the information acquisition unit, the task management unit, and the execution control unit, A task management system according to claim 1 or 2, including the following:

11. A computer program stored in the memory of an information processing device accessed by a content distributor, When the computer program is executed by the processing circuit of the information processing device, the information processing device will: To obtain information on the planned distribution of the content as scheduled by the aforementioned distributor, Based on the aforementioned distribution schedule information, task information indicating one or more tasks related to the content distribution is registered in the database in association with the content distribution. To execute at least one of the one or more tasks, or to assist in the execution of said at least one task, in accordance with the task information registered in the database. Have them do it, The aforementioned scheduled distribution information includes the themes of the aforementioned content distribution, The at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the broadcaster and the viewer over a network, The message generation task is performed by inputting a generation command based on the theme of the content distribution into the text generation model. Computer program.

12. A computer program stored in the memory of an information processing device accessed by a content distributor, When the computer program is executed by the processing circuit of the information processing device, the information processing device will: To obtain information on the planned distribution of the content as scheduled by the aforementioned distributor, Based on the aforementioned distribution schedule information, task information indicating one or more tasks related to the content distribution is registered in the database in association with the content distribution. To execute at least one of the one or more tasks, or to assist in the execution of said at least one task, in accordance with the task information registered in the database. Have them do it, The aforementioned scheduled distribution information includes avatar-related information related to the avatar used by the distributor in the aforementioned content distribution, The at least one task includes a message generation task that generates a message to be transmitted over a communication channel for communication between the broadcaster and the viewer over a network, The message generation task is performed by inputting generation commands based on the avatar-related information into the text generation model. Computer program.

Images