CN113134231A

CN113134231A - Live broadcast processing method and device, electronic equipment and storage medium

Info

Publication number: CN113134231A
Application number: CN202110510283.4A
Authority: CN
Inventors: 张艳军; 武斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2021-07-20
Anticipated expiration: 2041-05-11
Also published as: CN113134231B

Abstract

The application provides a live broadcast processing method, a live broadcast processing device, electronic equipment and a computer readable storage medium; the method comprises the following steps: responding to a trigger operation aiming at a task entrance in a live scene, and displaying a task aggregate prop; acquiring a plurality of tasks issued by an account of a live broadcast platform, and displaying the tasks in the task aggregation prop; displaying at least one task selected from the plurality of tasks and a corresponding task execution entry in response to a selection operation received in the task aggregate item; and the task execution inlet is used for displaying a corresponding task execution page when being triggered. Through the method and the device, the interaction efficiency can be improved by expanding the interaction mode in the live scene, so that the live communication resources and the display resources are saved.

Description

Live broadcast processing method and device, electronic equipment and storage medium

Technical Field

The present application relates to internet technologies, and in particular, to a live broadcast processing method and apparatus, an electronic device, and a computer-readable storage medium.

Background

With the rapid development of internet technology, live webcasting has been widely popularized to have the advantages of intuition, rich content, strong interactivity, unlimited region and the like, and through live webcasting technology, a main webcasting can be live webcast in a live webcasting room, and audiences can enter the live webcasting room where the main webcasting is located to watch the performance of the main webcasting.

At present, in the live broadcast process, audiences and a main broadcast can only interact in a mode of presenting gifts, asking questions for live broadcast contents or publishing viewpoints and the like, and the problem of poor live broadcast effect caused by single interaction mode and low efficiency can occur, so that communication resources and display resources used in the live broadcast process are wasted. For this reason, the related art has not yet made an effective solution.

Disclosure of Invention

The embodiment of the application provides a live broadcast processing method and device, electronic equipment and a computer readable storage medium, which can improve interaction efficiency by expanding an interaction mode in a live broadcast scene, thereby saving communication resources and display resources used in a live broadcast process.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a live broadcast processing method, which comprises the following steps:

responding to a trigger operation aiming at a task entrance in a live scene, and displaying a task aggregate prop;

acquiring a plurality of tasks issued by an account of a live broadcast platform, and displaying the tasks in the task aggregation prop;

displaying at least one task selected from the plurality of tasks and a corresponding task execution entry in response to a selection operation received in the task aggregate item;

and the task execution inlet is used for displaying a corresponding task execution page when being triggered.

receiving a transfer notification message sent by a viewer account of a live broadcast platform;

the transmission notification message is used for prompting the audience account to transmit virtual resources to a main broadcasting account based on a virtual role, and the virtual role has a virtual resource transmission function;

displaying the delivery notification message;

displaying the virtual resource in response to a sign-in operation for the virtual resource.

An embodiment of the present application provides a live broadcast processing apparatus, including:

the display module is used for responding to triggering operation aiming at a task entrance in a live scene and displaying the task aggregate prop;

the acquisition module is used for acquiring a plurality of tasks issued by an account of a live broadcast platform and displaying the tasks in the task aggregation prop;

a selection module, configured to display at least one task selected from the plurality of tasks and a corresponding task execution entry in response to a selection operation received in the task aggregate item;

In the above scheme, the obtaining module is further configured to display a plurality of barrage in the task aggregate prop, where each barrage includes at least part of content of one task; wherein the at least part of the content comprises at least one of: and issuing the account number, the task content and the task keywords of the task.

In the above scheme, the obtaining module is further configured to determine a matching degree between a login account and each task, where the login account is an account for logging in the live broadcast scene; determining a display parameter associated with the degree of matching for each of the tasks; wherein the display parameter is used to characterize at least one of: the significance degree of the barrage, the content integrity degree of the barrage and the sequencing of the barrage; and displaying the plurality of barrages in the task aggregation prop according to the display parameters.

In the foregoing solution, when the selection operation is a somatosensory operation, the selection module is further configured to, in response to the somatosensory operation received in the task aggregation prop, obtain an operation parameter of the somatosensory operation, select at least one task from the plurality of tasks displayed in the task aggregation prop according to the operation parameter, and display details of the selected at least one task and a corresponding task execution entry.

In the above scheme, the operating parameters include direction and magnitude; the selection module is further configured to determine at least one task that is adapted to the direction and the magnitude, among the plurality of tasks displayed in the task aggregate prop.

In the above scheme, the obtaining module is further configured to screen out, from a task set issued by an account of the live broadcast platform, a plurality of tasks that satisfy the following conditions: tasks issued by accounts having an interactive relationship with the login account, tasks belonging to the same type as the tasks executed by the login account and tasks within the capability range of the login account; and the login account is an account for logging in the live broadcast scene.

In the above scheme, the selection module is further configured to display a virtual resource selected from a virtual resource library and granted to a login account, and a virtual resource transfer entry corresponding to the virtual resource; responding to a trigger operation aiming at the virtual resource transfer entry, and sending the virtual resource to a target account, wherein the type of the target account comprises: audience account numbers and anchor account numbers; and the login account is an account for logging in the live broadcast scene.

In the above scheme, the selection module is further configured to display at least one candidate account in response to a trigger operation for the virtual resource transfer entry; wherein the type of the candidate account includes at least one of: an account number in a live broadcast room watched by the login account number, an account number having an interaction relationship with the login account number, and an account number having an interaction frequency exceeding an interaction frequency threshold value with the login account number; and responding to account selection operation, taking the selected at least one candidate account as the target account, and sending the virtual resource to the target account.

In the above scheme, the selection module is further configured to determine to perform, when the login account satisfies a virtual resource granting condition, an operation of displaying a virtual resource selected from a virtual resource library and granted to the login account and a virtual resource transfer entry corresponding to the virtual resource; wherein the virtual resource grant condition includes at least one of: the activity of the login account number participating in the interaction based on the task aggregation prop exceeds an activity threshold; the number of days that the login account continuously releases or executes tasks exceeds a threshold number of days.

In the above scheme, the selection module is further configured to, when the virtual resource granted to the login account is not used within a preset time period, retrieve the virtual resource to the virtual resource library.

In the above scheme, the live broadcast scene includes a live broadcast room page, when a login account of the live broadcast room page is a anchor account, the display module is further configured to respond to a live broadcast room creation operation of the anchor account and display a task configuration page in response to a trigger operation of a task entry in the live broadcast scene; responding to task configuration operation received in the task configuration page, and acquiring at least one task configured by the task configuration operation aiming at the anchor account; or when the task configuration operation is not received within the waiting time, acquiring at least one task configured by the live broadcast platform for the anchor account; and issuing at least one task configured for the anchor account to the live broadcast platform, creating a live broadcast room, and displaying the live broadcast room comprising the task entry.

In the above scheme, the display module is further configured to respond to a live broadcast room creation operation of the anchor account, and display a task configuration page matched with the level according to the level of the anchor account; the anchor account is capable of configuring a plurality of tasks in the task configuration page, and is positively correlated with the level.

In the above scheme, when the login account is the audience account, the obtaining module is further configured to display a task issuing entry in the task aggregation item; responding to the triggering operation of the audience account aiming at the task publishing entry, displaying a task publishing page, and acquiring at least one task to be published by the audience account through the task publishing page; and responding to the task issuing operation received in the task issuing page, and issuing at least one task to be issued by the audience account to the live broadcast platform.

In the above scheme, the obtaining module is further configured to obtain the number of tasks that the viewer account has issued to the live broadcast platform; when the number is not less than the threshold value of the number of the tasks allowed to be issued, locking the permission of the audience account to issue the new tasks; and when the number is smaller than the threshold value of the number of the tasks allowed to be published, determining that the operation of displaying the task publishing page is to be executed.

In the above scheme, the obtaining module is further configured to display at least one task that has been issued by the viewer account and a corresponding task editing entry; in response to a triggering operation aiming at the task editing entry, deleting or modifying at least one task issued by the audience account; and when the number of the tasks published by the audience account is smaller than the threshold value of the number of the tasks allowed to be published, unlocking the permission of the audience account to publish the new tasks.

In the above scheme, the selection module is further configured to display a task abandoning entry in the task aggregate prop; and in response to the triggering operation aiming at the task abandoning entrance, stopping displaying the selected at least one task and the corresponding task execution entrance, and recovering the selected at least one task to the task aggregation prop.

In the above scheme, the selection module is further configured to display a list entry; responding to a triggering operation aiming at the list entry, and displaying a list page, wherein the list page comprises descending order of the plurality of accounts of the live broadcast platform according to the corresponding task scores; wherein the task points are positively correlated with the number of tasks executed by the account.

An embodiment of the present application provides an electronic device, including:

a memory for storing computer executable instructions;

and the processor is used for realizing the live broadcast processing method provided by the embodiment of the application when executing the computer executable instructions stored in the memory.

The embodiment of the application provides a computer-readable storage medium, which stores computer-executable instructions and is used for realizing the live broadcast processing method provided by the embodiment of the application when being executed by a processor.

An embodiment of the present application provides a computer program product, where the computer program product includes computer executable instructions, and is used for implementing a live broadcast processing method provided in the embodiment of the present application when being executed by a processor.

The embodiment of the application has the following beneficial effects:

the tasks issued by the account number of the live broadcast platform are displayed through the task aggregation props in the live broadcast scene, so that the user can intuitively know the requirements of other users in the live broadcast, and the interaction diversity is improved; and the user is supported to select the task through the task aggregation prop, and the user is promoted to finish the task so as to enhance interactivity, so that the interactive efficiency is improved, and further, the live broadcast communication resources and display resources are saved.

Drawings

Fig. 1 is a schematic architecture diagram of a live broadcast processing system 100 provided in an embodiment of the present application;

fig. 2 is a schematic structural diagram of a terminal 400 provided in an embodiment of the present application;

fig. 3 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application;

fig. 4 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application;

fig. 5 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application;

fig. 6 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application;

fig. 7A, fig. 7B, fig. 7C, and fig. 7D are schematic application scenarios of a live broadcast processing method provided in an embodiment of the present application;

fig. 8 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application;

fig. 9 is a flowchart illustrating a live broadcast processing method according to an embodiment of the present application

Fig. 10 is a schematic view of an application scenario of a live broadcast processing method provided in an embodiment of the present application;

fig. 11 is a schematic view of an application scenario of a live broadcast processing method provided in an embodiment of the present application;

fig. 12 is a schematic view of an application scenario of a live broadcast processing method provided in an embodiment of the present application;

fig. 13 is a schematic view of an application scenario of a live broadcast processing method provided in an embodiment of the present application;

fig. 14 is an application scenario diagram of a live broadcast processing method according to an embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

In the following description, references to the terms "first/second" are only to distinguish similar items and do not denote a particular order, but rather the terms "first/second" may, where permissible, be interchanged with a particular order or sequence so that embodiments of the application described herein may be practiced in other than the order shown or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

Before further detailed description of the embodiments of the present application, terms and expressions referred to in the embodiments of the present application will be described, and the terms and expressions referred to in the embodiments of the present application will be used for the following explanation.

1) In response to the condition or state on which the performed operation depends, one or more of the performed operations may be in real-time or may have a set delay when the dependent condition or state is satisfied; there is no restriction on the order of execution of the operations performed unless otherwise specified.

2) Live broadcast, which is to make and release information synchronously with the occurrence and development process of events on site, and has an information network release mode of bidirectional circulation process. Specifically, the data of the broadcasting party can be collected by the equipment, and subjected to a series of processing, such as video encoding, compression, and output to the watching user terminal.

3) Virtual resources, which refer to any form of resource that can be transmitted in a network, are measured as "amounts". The virtual resource may be electronic money corresponding to the receipt and payment, and the amount may be an amount of the receipt and payment (i.e., a value of the electronic money included in the receipt and payment), which enables transfer of the electronic money between the users based on the mobile payment technology. The virtual resource may also be a virtual article (or gift), such as a digital flower, a digital cake, etc., and a user of the live platform purchases the virtual resource with legal currency in the live platform and the virtual resource can be given to the host.

4) Tasks, or wishes, are events or activities issued by accounts (e.g., anchor account, audience account) in a live platform that are intended to be performed or implemented by the remaining participants.

5) The task aggregation prop, or a wish wall, a task wall, or a wishing wall, refers to a prop having functions of task display, task selection, task publishing, and the like, and is not limited to any form, such as a blackboard, a wall, a bulletin board, and the like, and a user (such as an anchor or audience) can view and execute a task published by an account in a live broadcast platform through the task aggregation prop.

The embodiment of the application provides a live broadcast processing method, which can improve the interaction efficiency and the live broadcast effect by expanding the interaction mode in a live broadcast scene, thereby saving communication resources and display resources used in the live broadcast process. An exemplary application of the live broadcast processing method provided by the embodiment of the present application is described below, and the live broadcast processing method provided by the embodiment of the present application can be implemented by various electronic devices, for example, can be applied to various types of user terminals (hereinafter also referred to as terminals for short) such as smart phones, tablet computers, vehicle-mounted terminals, and smart wearable devices.

Next, taking an electronic device as an example, an exemplary application system architecture of a terminal for implementing the live broadcast processing method provided in the embodiment of the present application is described, referring to fig. 1, where fig. 1 is an architecture schematic diagram of a live broadcast processing system 100 provided in the embodiment of the present application. The live broadcast processing system 100 includes: the server 200, the network 300, and the terminal 400 will be separately described.

The server 200 is a background server of the client 410, and is used for sending a plurality of tasks issued by an account of a live platform to the client 410.

The network 300, which is used as a medium for communication between the server 200 and the terminal 400, may be a wide area network or a local area network, or a combination of both.

The terminal 400, which is attributed to a user (e.g., a main broadcast or a viewer), is used to operate a client 410, and the client 410 is a live broadcast-enabled client. The client 410 is configured to display a task aggregation prop in response to a trigger operation for a task entry in a live broadcast scene, receive a plurality of tasks issued by an account of a live broadcast platform and sent by the server 200, and display the plurality of tasks in the task aggregation prop; and the task execution system is also used for responding to the selection operation received in the task aggregation prop, and displaying at least one task selected from the plurality of tasks and a corresponding task execution inlet.

In some embodiments, applicable to a live game scene, in response to a trigger operation of a host or a viewer for a task entry in the live scene (e.g., a live game room page or a live platform home page), the client 410 displays a task aggregate item, receives a plurality of game tasks sent by the server 200, and displays the plurality of game tasks in the task aggregate item, where the types of the game tasks include: performing countermeasure actions (for example, killing enemies) aiming at the virtual character, performing assistance actions (for example, rescuing teammates) aiming at the virtual character, acquiring virtual props and the like; displaying at least one task selected from a plurality of game tasks and a corresponding task execution entry in response to a selection operation received in the task aggregate item; when the anchor or the audience triggers the task execution entrance, displaying a game interface corresponding to the game task, so that the anchor or the audience executes the game task in the game interface, for example, attacking a virtual object, acquiring a virtual item and the like; and after the anchor or the audience executes the game task, sending corresponding task credits or virtual resources to the anchor account or the audience account.

In some embodiments, the terminal 400 implements the live broadcast processing method provided in the embodiments of the present application by running a computer program, for example, the computer program may be a native program or a software module in an operating system; can be a local (Native) Application program (APP), i.e. a program that needs to be installed in an operating system to run, such as a live APP; or an applet, i.e. a program that can be run only by downloading it to a browser environment, such as a live applet; but also a live applet that can be embedded into any APP. In general, the computer programs described above may be any form of application, module or plug-in.

The embodiments of the present application may be implemented by means of Cloud Technology (Cloud Technology), which refers to a hosting Technology for unifying series resources such as hardware, software, and network in a wide area network or a local area network to implement data calculation, storage, processing, and sharing.

The cloud technology is a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied based on a cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources.

As an example, the server 200 may be an independent physical server, may be a server cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform. The terminal 400 and the server 200 may be directly or indirectly connected through wired or wireless communication, and the embodiment of the present application is not limited thereto.

The structure of the terminal 400 in fig. 1 is explained next. Referring to fig. 2, fig. 2 is a schematic structural diagram of a terminal 400 provided in an embodiment of the present application, where the terminal 400 shown in fig. 2 includes: at least one processor 410, memory 450, at least one network interface 420, and a user interface 430. The various components in the terminal 400 are coupled together by a bus system 440. It is understood that the bus system 440 is used to enable communications among the components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 440 in fig. 2.

The Processor 410 may be an integrated circuit chip having Signal processing capabilities, such as a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like, wherein the general purpose Processor may be a microprocessor or any conventional Processor, or the like.

The user interface 430 includes one or more output devices 431, including one or more speakers and/or one or more visual displays, that enable the presentation of media content. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 450 optionally includes one or more storage devices physically located remote from processor 410.

The memory 450 includes either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile memory may be a Read Only Memory (ROM), and the volatile memory may be a Random Access Memory (RAM). The memory 450 described in embodiments herein is intended to comprise any suitable type of memory.

In some embodiments, memory 450 is capable of storing data, examples of which include programs, modules, and data structures, or a subset or superset thereof, to support various operations, as exemplified below.

The operating system 451, which includes system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., is used for implementing various basic services and for processing hardware-based tasks.

A network communication module 452 for communicating to other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: bluetooth, wireless compatibility authentication (WiFi), and Universal Serial Bus (USB), among others.

A presentation module 453 for enabling presentation of information (e.g., user interfaces for operating peripherals and displaying content and information) via one or more output devices 431 (e.g., display screens, speakers, etc.) associated with user interface 430.

An input processing module 454 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.

In some embodiments, the live broadcast processing apparatus provided in the embodiments of the present application may be implemented in software, and fig. 2 illustrates a live broadcast processing apparatus 455 stored in the memory 450, which may be software in the form of programs and plug-ins, and includes the following software modules: a display module 4551, an acquisition module 4552 and a selection module 4553, which are logical and thus may be arbitrarily combined or further split depending on the functions implemented. The functions of the respective modules will be explained below.

In the following, a live broadcast processing method provided in the embodiment of the present application is separately executed by the terminal 400 in fig. 1 as an example. Referring to fig. 3, fig. 3 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application, and will be described with reference to the steps shown in fig. 3.

It should be noted that the method shown in fig. 3 can be executed by various forms of computer programs executed by the terminal 400, and is not limited to the above-mentioned client 410, such as the above operating system 451, software modules, scripts and applets, so that the following example of the client should not be construed as limiting the embodiments of the present application.

It should be noted that, hereinafter, the anchor account is attributed to the anchor and the viewer account is attributed to the viewer, and for convenience of description, the anchor account and the anchor are not specifically distinguished, and the viewer account and the viewer are not specifically distinguished. For example, the operation of the viewer account is specifically the operation of the viewer holding the viewer account.

In step S101, in response to a trigger operation for a task entry in a live scene, a task aggregate item is displayed.

In some embodiments, the types of live scenes include: a live broadcast platform home page and a live broadcast room page. The use permission of the task aggregation prop can be opened to any anchor account or audience account in the live broadcast platform, wherein the use permission comprises task issuing permission, task selecting permission, task execution permission and the like.

In some embodiments, when the live scene is a live room page and the login account of the live room page is a main account, before step S101, the method may further include: responding to the creation operation of a live broadcast room of the anchor account, and displaying a task configuration page; responding to task configuration operation received in a task configuration page, and acquiring at least one task configured by the task configuration operation aiming at the anchor account; or, when the task configuration operation is not received within the waiting time (which may be a default value or a value set by the anchor, the client or the server), acquiring at least one task configured by the live broadcast platform for the anchor account; and releasing at least one task configured for the anchor account to a live broadcast platform, creating a live broadcast room, and displaying the live broadcast room comprising a task entrance.

As an example, step S101 may include: and responding to the triggering operation of the task entrance aiming at the live broadcast room page, and displaying the task aggregate prop.

As an example, in response to a live broadcast room creation operation of a anchor account, displaying a task configuration page matched with a level according to the level of the anchor account; the number of tasks which can be configured by the anchor account in the task configuration page is multiple, and the anchor account is positively correlated with the level.

For example, the level of the anchor account is positively correlated with the interaction parameters of the anchor account, which include at least one of: the number of tasks executed by the anchor account, the live broadcast duration of the anchor account, and the number of times that the anchor account establishes a live broadcast room.

For example, in fig. 12, the anchor may create a live broadcast room carrying the task entry 123 by triggering the task live broadcast room creation entry 121, when the user triggers the task live broadcast room creation entry 121, the task configuration page 122 is displayed, the task configuration page 122 includes the number of tasks allowing the anchor account to configure, the number of tasks allowing the anchor account to configure is positively correlated with the level of the anchor account, and the live broadcast room carrying the task entry 123 may be created after the anchor account configures the task. When the anchor triggers task entry 123 in the live room, the task aggregate prop is displayed.

The embodiment of the application supports the anchor to establish the live broadcast room carrying the task entrance, can enable the anchor or audiences who join in the live broadcast room to execute the task, and compared with a common live broadcast room, the interactivity of the live broadcast room carrying the task entrance is stronger, so that the interactive efficiency and the live broadcast effect can be improved in the live broadcast process.

In some embodiments, when the login account is a viewer account, when displaying the task aggregate item, may include: displaying a task issuing entrance in the task aggregation prop; responding to the triggering operation of the audience account aiming at the task issuing entrance, displaying a task issuing page, and acquiring at least one task to be issued by the audience account through the task issuing page; and responding to the task issuing operation received in the task issuing page, and issuing at least one task to be issued by the audience account to the live broadcast platform.

For example, in fig. 7C, when the viewer triggers the task issue portal 704, a task issue page is displayed, and the viewer can fill in the desire (i.e., the task) through the task issue page and can issue the desire to fill in the desire to live broadcast to the live broadcast platform by triggering the "delivery desire" button after the completion of the filling in.

By way of example, prior to displaying the task publication page, may include: acquiring the number of tasks which are issued to a live broadcast platform by a viewer account; when the number is not less than the threshold value of the number of the tasks allowed to be issued, locking the permission of issuing a new task by the audience account; and when the number is less than the threshold value of the number of the tasks allowed to be published, determining that the operation of displaying the task publishing page is to be performed.

For example, the threshold value of the number of allowed tasks to be issued may be a default value or a value set by a viewer, a client, or a server. Certainly, the threshold of the number of tasks allowed to be issued corresponding to different audience accounts may be different, for example, the threshold of the number of tasks allowed to be issued corresponding to the audience accounts may be positively correlated with the level of the audience accounts, the level of the audience accounts is positively correlated with the interaction parameter of the audience accounts, and the interaction parameter includes at least one of the following: the number of tasks executed by the audience account, the time length of the audience account watching the live broadcast and the number of tasks issued by the audience account.

For example, when the permission of the audience account to issue the new task is locked, the first prompt information may be further displayed, where the first prompt information is used to prompt that the number of issued tasks reaches the number of tasks allowed to be issued, and the new task cannot be issued continuously, so as to prompt the audience that the new task cannot be issued.

For example, after locking the right of the viewer account to issue a new task, it may include: displaying at least one task issued by a viewer account and a corresponding task editing entry; in response to a triggering operation aiming at the task editing entry, deleting or modifying at least one task issued by the audience account; and when the number of the tasks published by the audience account is less than the threshold value of the number of the tasks allowed to be published, unlocking the permission of the audience account to publish the new tasks.

For example, when the right of the viewer account to issue a new task is unlocked, second prompt information can be displayed, wherein the second prompt information is used for prompting that the viewer account is allowed to continue to issue the new task.

For example, in fig. 13, the tasks published by the viewer account and the corresponding task editing entry 131 can be viewed through the task viewing page, and the viewer can modify or delete the published tasks through a "modify" button or a "delete" button in the task editing entry 131, so that the viewer can be helped to adjust the tasks published before, and the human-computer interaction efficiency is improved.

In some embodiments, when displaying task aggregate props, the method may include: displaying the list entry; responding to triggering operation aiming at the list entry, and displaying a list page, wherein the list page comprises descending order of the plurality of accounts of the live broadcast platform according to the corresponding task scores; the task integration is positively correlated with the number of tasks executed by the account.

As an example, in fig. 7D, when the task aggregation item is displayed, a list entry 705 may be further displayed, when the audience triggers the list entry 705, a wish list is displayed on a list page, each account in the wish list is sorted in a descending order according to a corresponding wish value (i.e., the above-mentioned task score), and some accounts (e.g., the first three accounts) in the wish list are displayed with a dedicated nameplate, and the wish list may be refreshed at a fixed frequency, for example, every two hours, or updated when the ranking in the wish list changes.

In step S102, a plurality of tasks issued by the account of the live platform are acquired.

In some embodiments, a plurality of tasks issued by any account of the live platform can be directly acquired from the server; a plurality of tasks meeting the following conditions can also be screened out from a task set issued by an account of a live broadcast platform: tasks issued by the account number having an interactive relationship with the login account number belong to the same type of tasks as the tasks executed by the login account number, and are within the capability range of the login account number.

As an example, the account having an interaction relationship with the login account may be an account concerned, commented or praised by the login account, an account having an interaction frequency exceeding an interaction frequency threshold with the login account, or an account having an interaction duration exceeding an interaction duration threshold with the login account, where the interaction frequency threshold and the interaction duration threshold may be default values or values set by a host, a viewer, a client or a server.

By way of example, task types include: a type of attention (e.g., task "XXX request attention", etc.), a type of gift giving (e.g., task "can give me a flower gift", etc.), a type of viewing (e.g., task "watch me anchor 20 minutes bar", etc.), and so forth.

As an example, the task within the capability of the login account may be a task within the payment capability of the login account, for example, the task "can send me a flower gift" consumes 1 virtual currency when executed, the task "can send me a diamond gift" consumes 50 virtual currencies when executed, and at this time, only 10 virtual currencies are in the electronic wallet of the login account, so the task "can send me a flower gift" is a task within the capability of the login account, and the task "can send me a diamond gift" is not a task within the capability of the login account. Therefore, the login account can be helped to filter tasks which cannot be completed by the login account, and therefore computing resources consumed in task selection are saved.

In step S103, a plurality of tasks are displayed in the task aggregate item.

In some embodiments, at least part of the content of the plurality of tasks is displayed in the task aggregate prop, wherein the at least part of the content of the tasks may be brief description content of the tasks, for example, account numbers for issuing the tasks, task keywords, or detail content of the tasks, that is, the whole content of the tasks.

As an example, the brief introduction content or the detailed content of the task displayed in the task aggregation prop may be set by the login account, or may be automatically adapted according to the number of tasks or the size of the display screen of the terminal, for example, when the number of tasks to be displayed exceeds the maximum number of tasks that can be presented by the size of the display screen of the terminal, the brief introduction content of the task is automatically displayed; and when the number of the tasks to be displayed does not exceed the maximum task number which can be presented by the size of the display screen of the terminal, automatically displaying the detailed contents of the tasks.

In some embodiments, a plurality of barrages are displayed in the task aggregate prop, each barrage including at least a portion of the content of one task; wherein at least part of the content comprises at least one of: and issuing the account number, the task content and the task keywords of the task.

As an example, the task keyword is obtained by performing a keyword recognition process on the detailed content of the task, for example, the detailed content of the task is "hope many people to pay attention to me", and the extracted task keyword may be "pay attention to me".

For example, in fig. 7A, when a anchor or audience triggers task entry 701, task aggregation prop 702 is displayed, and a plurality of barrages 706 are displayed in task aggregation prop 702, where each barrage 706 includes at least part of the content of a task, such as "focus me", "watch me anchor 20 minutes bar", and "wish to have a guard", etc.

As an example, determining a matching degree between a login account and each task, wherein the login account is an account for logging in a live broadcast scene in a client; determining a display parameter related to the matching degree of each task; wherein the display parameter is used to characterize at least one of: the degree of prominence of the barrage; the completeness of the task content in the bullet screen; sequencing bullet screens; and displaying a plurality of barrages in the task aggregation prop according to the display parameters.

For example, determining the degree of match between the login account and each task may include: the following processing is performed for each task by the neural network model: extracting a characteristic vector of the task and extracting a characteristic vector of the login account; and determining the similarity degree between the characteristic vector of the task and the characteristic vector of the login account as the matching degree between the login account and the task.

Here, the neural network model is obtained by training, as a sample, a sample login account, a task that has been executed by the sample login account, and a degree of similarity between tasks that have been executed by the sample login account and the sample login account, where for example, the degree of similarity between tasks that have been executed by the sample login account and the sample login account is denoted by 100%, and the degree of similarity between tasks that have not been executed by the sample login account and the sample login account is denoted by 0%. The Neural Network model may include various types, such as a Convolutional Neural Network (CNN) model, a Recurrent Neural Network (RNN) model, a multi-layer feedforward Neural Network model, and the like. The neural network model can be trained in a supervision mode, wherein a loss function used for training the neural network model is used for representing the difference between the predicted value and the actual labeled data, and the loss function can be a 0-1 loss function, a perception loss function, a cross entropy loss function or the like. According to the method and the device, the matching degree between the login account and each task is determined through the neural network model, and the accuracy and the matching performance when the bullet screen is displayed according to the matching degree can be improved.

For example, the degree of saliency of the bullet screen can be embodied by the movement speed of the bullet screen, the size of the bullet screen, the color of the bullet screen, the thickness of the font in the bullet screen, and the like, wherein the degree of saliency of the bullet screen is positively correlated with the matching degree, for example, the slower the movement speed of the bullet screen, the higher the matching degree of the task corresponding to the bullet screen and the login account is, the larger the size of the bullet screen, the higher the matching degree of the task corresponding to the bullet screen and the login account is, and the sharper the color of the bullet screen, the higher the matching degree of the task corresponding to the bullet screen and the login account is (for example, the matching degree of the task corresponding to the red bullet screen and the login account is higher than the matching degree of the task corresponding to the black bullet screen and the login account), and the thicker the font in the bullet screen, the higher the matching degree of the task corresponding to the login account is characterized. The completeness of the task content in the bullet screen is positively correlated with the matching degree, for example, the more complete the task content in the bullet screen represents the higher the matching degree between the task corresponding to the bullet screen and the login account. The order of the barrage is positively correlated with the matching degree, for example, the barrage corresponding to the task with the highest matching degree appears first in the task aggregate props.

For example, in fig. 10, the bullet screen 102 and the bullet screen 103 are included in the task aggregate prop 101, and the bullet screen 102 and the bullet screen 103 have a greater degree of significance in the color of the bullet screen 103 than in the bullet screen 103, so that the task "focus me" in the bullet screen 103 matches the login account more than the task "wish to have a guard" in the bullet screen 102 matches the login account.

According to the embodiment of the application, the plurality of tasks are displayed in the task aggregation prop in a bullet screen mode, and the plurality of bullet screens are displayed in a personalized mode according to the matching degree between the login account and each task, so that the anchor or audiences can conveniently and visually know the tasks related to the anchor or audiences, the enthusiasm of the anchor or audiences in participating in interaction is improved, and the interaction efficiency is further improved.

In some embodiments, a task list is displayed in the task aggregate prop, and a plurality of task types are displayed in the task list; wherein each task type comprises at least one task.

As an example, determining a degree of matching between the login account and each task; displaying the matched task type in a display mode different from a non-matched task type in a plurality of task types in the task list; the matching task types comprise tasks with the matching degree exceeding a matching degree threshold value, and the non-matching task types comprise tasks with the matching degree exceeding the matching degree threshold value.

For example, the threshold of the degree of matching may be a default value, or may be a value set by a broadcaster, a viewer, a client, or a server. In fig. 11, task list 112 is displayed in task aggregation prop 111, and a plurality of task types 113 are displayed in task list 112, where the task type of "gift type" includes a task whose matching degree exceeds a matching degree threshold, and therefore, the task type of "gift type" is displayed in a manner that is distinguished from the remaining two task types ("focus type" and "view type"), for example, with a bold font.

As an example, determining the degree of match between the login account and each task may include: the following processing is performed for each task by the neural network model: extracting a characteristic vector of the task and extracting a characteristic vector of the login account; and determining the similarity degree between the characteristic vector of the task and the characteristic vector of the login account as the matching degree between the login account and the task.

Here, the neural network model is obtained by training, as a sample, a sample login account, a task that has been executed by the sample login account, and a degree of similarity between tasks that have been executed by the sample login account and the sample login account, where for example, the degree of similarity between tasks that have been executed by the sample login account and the sample login account is denoted by 100%, and the degree of similarity between tasks that have not been executed by the sample login account and the sample login account is denoted by 0%. According to the embodiment of the application, the matching degree between the login account and each task is determined through the neural network model, and the accuracy and the matching performance when the task type is displayed according to the matching degree can be improved.

According to the method and the device, the tasks are displayed in the task aggregation props in a list mode, the task types are displayed in an individualized mode according to the matching degree between the login account and each task, and therefore the anchor or audiences can conveniently and visually know the task types related to the anchor or audiences, the enthusiasm of the anchor or audiences in interaction is improved, and interaction efficiency is further improved.

In step S104, in response to a selection operation received in the task aggregate item, at least one task selected from the plurality of tasks and a corresponding task execution entry are displayed.

In some embodiments, in response to a selection operation received by the anchor account or the viewer account in the task aggregate item, details of at least one selected task from the plurality of tasks displayed by the task aggregate item and a corresponding task execution entry are displayed in a popup manner, wherein the task execution entry is used for displaying a corresponding task execution page when triggered.

In some embodiments, when the selection operation is a motion sensing operation, step S104 may include: and responding to the somatosensory operation received in the task aggregation prop, acquiring an operation parameter of the somatosensory operation, selecting at least one task from a plurality of tasks displayed in the task aggregation prop according to the operation parameter, and displaying the detailed content of the selected at least one task and a corresponding task execution entry.

As an example one, at least one task may be randomly selected from a plurality of tasks displayed in the task aggregate prop according to the operating parameter. Taking the motion sensing operation as an example of shaking the terminal, in fig. 7B, after the human-computer interaction interface displays the task aggregation prop 702, the anchor or the audience can randomly select one task from a plurality of tasks by shaking the terminal, and after shaking is finished, details of the randomly selected task 703 and a corresponding task execution entry 707 are displayed in the human-computer interaction interface.

As example two, the operating parameters include direction and magnitude; selecting at least one task from the plurality of tasks displayed in the task aggregate prop according to the operating parameter may include: at least one task adapted to a direction and a magnitude is determined among a plurality of tasks displayed in the task aggregate prop.

Taking the motion sensing operation as an example of an operation of shaking the terminal, when the anchor or the audience shakes the terminal to the left, selecting the task left from the plurality of tasks displayed in the task aggregate prop, and determining how many tasks to traverse to the left in the plurality of displayed tasks according to the amplitude of shaking the terminal, for example, the larger the amplitude of shaking the terminal is, the more the number of tasks representing traversal to the left is, the smaller the amplitude of shaking the terminal is, and the less the number of tasks representing traversal to the left is.

For example, when the anchor or the audience shakes the terminal to the left, the tasks displayed in the task aggregate prop are sequentially preselected to the left, the preselected tasks are displayed in the task aggregate prop in a display mode different from the rest tasks, such as highlight display, and when a new shaking operation of the anchor or the audience is not received within a preset waiting time, the tasks displayed in the display mode different from the rest tasks are determined as the tasks finally selected by the anchor or the audience.

For example, task 1, task 2, and task 3 are arranged in sequence from right to left, and when the anchor or the viewer shakes the terminal to the left, the preselection is performed in sequence to the left in the order of task 1- > task 2- > task 3, when task 2 is preselected, task 2 is highlighted, and when task 2 is highlighted and no new shaking operation by the anchor or the viewer is received within a preset waiting time period, task 2 is determined as the task finally selected by the anchor or the viewer. Therefore, the anchor or audiences can intuitively know the task to be selected corresponding to the somatosensory operation, the problem of wrong task selection caused by difficulty in mastering the somatosensory operation is avoided, and the task selection efficiency is improved.

For example, the magnitude in the operation parameters may be replaced by parameters such as speed, acceleration, etc., so that at least one task adapted to the direction and adapted to the speed or acceleration may be determined as at least one task for display in the task aggregate prop, among the plurality of tasks displayed in the task aggregate prop.

Taking the motion sensing operation as an example of an operation of shaking the terminal, when the anchor or the audience shakes the terminal to the left, selecting the task left from the plurality of tasks displayed in the task aggregate, and determining how many tasks to traverse to the left in the plurality of displayed tasks according to the speed or acceleration of the shaking terminal, for example, the larger the speed or acceleration of the shaking terminal is, the larger the number of tasks representing the traversal to the left is, the smaller the speed or acceleration of the shaking terminal is, and the smaller the number of tasks representing the traversal to the left is.

For example, the somatosensory operation may be replaced by a sliding operation, wherein the operation parameters include a sliding direction and a sliding distance, for example, when the anchor or the viewer slides to the left, the left is selected from a plurality of tasks displayed in the task aggregation prop, and it is determined how many tasks are traversed to the left in the plurality of tasks displayed according to the sliding distance, for example, the larger the sliding distance is, the larger the number of tasks characterized by being traversed to the left is, the smaller the sliding distance is, the smaller the number of tasks characterized by being traversed to the left is. The somatosensory operation may also be replaced by a voice operation, wherein the operation parameters include a direction of a sound source (i.e., a direction of the sound source relative to the terminal) and a voice intensity, for example, when the anchor or the viewer utters a voice in a left direction relative to the terminal, selecting to the left among the plurality of tasks displayed in the task aggregation prop, and determining how many tasks to traverse to the left among the plurality of tasks displayed according to the voice intensity, for example, the greater the voice intensity, the greater the number of tasks characterizing the traversal to the left, the smaller the voice intensity, and the fewer the number of tasks characterizing the traversal to the left.

As an example three, selecting at least one task from the plurality of tasks displayed in the task aggregate prop according to the operating parameter may include: and calculating at least one random number according to the operation parameters, traversing in a plurality of tasks according to the random number, and taking the corresponding task when the traversed count reaches the random number as a selected task.

The embodiment of the application provides various types of selection operation, at least one task for displaying in the task aggregation prop is selected from a plurality of tasks, so that the man-machine interaction efficiency can be improved, and the operation resources of the terminal can be saved.

In some embodiments, the types of selection operations may include a random selection operation and a specific selection operation (e.g., a touch operation for a task displayed in the task aggregate prop or other specific gesture operation that may be recognized as selected), which will be described in detail below.

As an example one, in response to a random selection operation received in the task aggregate prop, at least one task for display in the task aggregate prop is randomly selected from a plurality of tasks, and at least part of the content of the randomly selected at least one task and a corresponding task execution entry are displayed; the random selection operation includes a motion sensing operation, a touch operation for a random selection button (for example, an operation of clicking the random selection button 708 in fig. 7B), and a voice operation indicating random selection (for example, when a microphone of the terminal collects voice information about "random selection", at least one task for display in the task aggregation item may be randomly selected from the plurality of tasks).

For example, the motion sensing operation may be an operation of shaking the terminal, in fig. 7B, taking the terminal as a mobile phone as an example, after the human-computer interaction interface displays the task aggregation prop 702, the anchor or the audience may shake the mobile phone to "shake one" to randomly select one task from the multiple tasks, and after shaking is finished, the details of the randomly selected task 703 and the corresponding task execution entry 707 may be displayed in the human-computer interaction interface, and since the task 703 is a gift-type task, when the anchor or the audience triggers the task execution entry 707, the corresponding task execution page, that is, a page for transmitting virtual resources, is presented, so that the anchor or the audience executes the gift-type task 703.

As an example two, in response to a specific selection operation received in the task aggregation prop, determining a specific task selected by the specific selection operation from the plurality of tasks, and displaying at least part of the content of the specific task and a corresponding task execution entry; wherein the specific selection operation comprises: the motion sensing operation, wherein parameters of the motion sensing operation are used for indicating a specific task; a touch operation for touching a specific task; for instructing the selection of a voice operation of a specific task.

For example, the parameters of the somatosensory operation include at least one of: the direction, the amplitude, and the motion sensing operation parameters may be used to indicate a specific task, for example, in fig. 7B, the task "hope to have a daemon" is located at the upper right of the task aggregation prop 702, at this time, the anchor or the audience may shake or move the mobile phone to the upper right, that is, the task "hope to have a daemon" may be selected. The anchor or viewer may also select a task "wish to have a guard" by clicking on it in task aggregate prop 702. Of course, the anchor or viewer may also select this by speaking a voice message similar to "select a desired task for daemon".

In some embodiments, displaying at least one task selected from the plurality of tasks and the corresponding task execution entry may include: and displaying the task abandoning entrance in the task aggregation prop, stopping displaying the selected at least one task and the corresponding task execution entrance in response to the triggering operation aiming at the task abandoning entrance, and recycling the selected at least one task into the task aggregation prop.

As an example, the stopping of displaying the selected at least one task and the corresponding task execution entry may be hiding the selected at least one task and the corresponding task execution entry, displaying a corresponding hidden appearing button, and displaying the selected at least one task and the corresponding task execution entry again when the hidden appearing button is triggered.

For example, in fig. 7B, after the details of the selected task 703 are presented, a corresponding task abandonment portal 709 is also presented, and when the anchor or viewer does not want to perform the task, the task 703 can be abandoned by triggering the task abandonment portal 709, i.e., the task 703 is recycled into the task aggregation prop 702, and after the anchor or viewer abandons the task, a different task can be selected again by the task aggregation prop 702.

In some embodiments, referring to fig. 4, fig. 4 is a flowchart illustrating a live broadcast processing method provided in an embodiment of the present application, based on fig. 3, step S104 may be replaced with step S105, and step S106 may be further included after step S105.

In step S105, in response to the selection operation received in the task aggregate item, a virtual resource selected from the virtual resource library and granted to the login account, and a virtual resource delivery entry corresponding to the virtual resource are displayed.

As an example, in fig. 7B, a broadcaster or a viewer may obtain and display a virtual resource 710 by performing a selection operation on task aggregate prop 702, and display a corresponding virtual resource delivery entry 711 while displaying virtual resource 710.

In some embodiments, step S104 and step S105 may also be performed in parallel, that is, step S105 may include: in response to the selection operation received in the task aggregation prop, displaying at least one task selected from the plurality of tasks and a corresponding task execution entry, and displaying a virtual resource selected from the virtual resource library and granted to the login account and a virtual resource delivery entry corresponding to the virtual resource, which is equivalent to displaying the selected task and the virtual resource at the same time.

In some embodiments, before displaying the virtual resource selected from the virtual resource library and granted to the login account, and the virtual resource delivery entry of the corresponding virtual resource, the method may further include: when the login account meets the virtual resource granting condition, determining to execute and display the operation of selecting and granting the virtual resource of the login account from the virtual resource library and the virtual resource transfer entry corresponding to the virtual resource; wherein the virtual resource granting condition includes at least one of: the activity of the login account participating in the interaction based on the task aggregation prop exceeds an activity threshold; the number of days that the login account continuously releases or performs tasks exceeds a threshold number of days.

As an example, the activity of the login account to engage in the task-aggregation-prop-based interaction exceeding the activity threshold may include at least one of: the number of the tasks executed by the login account exceeds the threshold value of the number of the executed tasks; the frequency of submitting selection operation in the task aggregation prop by the login account exceeds a selection frequency threshold; the number of tasks issued by the login account exceeds the threshold value of the number of issued tasks; the frequency of the tasks issued by the login account exceeds the task issuing frequency threshold.

For example, the threshold value of the number of tasks to be executed, the threshold value of the selection frequency, the threshold value of the number of tasks to be released, the threshold value of the frequency of tasks to be released, and the threshold value of the number of days may be default values, or may be values set by a host, a viewer, a client, or a server.

Whether the login account number meets the virtual resource granting condition or not needs to be confirmed before the virtual resource is displayed, the expectation values of the anchor and the audience in the participation process can be improved, the enthusiasm of the anchor and the audience in the interaction can be improved, and therefore the interaction efficiency is improved.

In some embodiments, after step S105, the method may further include: and when the virtual resource granted to the login account is not used by the login account within the preset time, the virtual resource is recovered to the virtual resource library.

As an example, the preset duration may be a default value, or may be a value set by a main broadcasting, a viewer, a client, or a server. In fig. 7B, when the virtual resource 710 is presented, a corresponding prompt message is also presented, that is, the prompt message is used to prompt that the virtual resource has been sent to a backpack (corresponding to an electronic wallet) of the login account, and the virtual resource expires after 3 days.

According to the embodiment of the application, the validity period of the virtual resources is limited, the login account can be promoted to send the obtained virtual resources to the target account as soon as possible, and therefore the interaction probability and the interaction rate between the login account and the target account can be improved.

In step S106, in response to a trigger operation for the virtual resource transfer entry, the virtual resource is sent to the target account.

In some embodiments, the types of target account numbers include: a viewer account, a home cast account.

In some embodiments, in response to a triggering operation for the virtual resource transfer portal, displaying at least one candidate account; the type of the candidate account comprises at least one of the following types: an account (such as a main account or a viewer account) in a live broadcast room watched by the login account, an account (such as a main account or a viewer account) having an interaction relationship with the login account, and an account (such as a main account or a viewer account) having an interaction frequency exceeding an interaction frequency threshold with the login account; and responding to the account selection operation, taking the selected at least one candidate account as a target account, and sending the virtual resources to the target account.

As an example, in fig. 14, when the anchor or viewer triggers the virtual resource delivery portal 142, a plurality of candidate accounts 143 and corresponding "select" buttons are displayed, the anchor or viewer can select the corresponding candidate account as the target account by triggering the "select" button, and when the anchor or viewer completes the selection, the virtual resource 141 can be sent to the target account by triggering the "complete" button.

According to the embodiment of the application, the interaction between the anchor and the audience is promoted to enhance through expanding the transmission mode of the virtual resources, so that the transmission efficiency of the virtual resources is improved.

In the following, taking an example that the live scene is a live room page, the live processing method provided by the embodiment of the present application is cooperatively executed by the anchor terminal, the audience terminal, and the server. Referring to fig. 5, fig. 5 is a schematic flowchart of a live broadcast processing method provided in an embodiment of the present application, and will be described with reference to the steps shown in fig. 5.

In step S501, the anchor terminal displays a task configuration page in response to a live view creation operation of the anchor account.

In step S502, the anchor terminal obtains at least one task configured for the anchor account by the task configuration operation in response to the task configuration operation received on the task configuration page.

In some embodiments, step S502 may further include: and when the task configuration operation is not received within the waiting time, acquiring at least one task configured by the live broadcast platform for the anchor account.

In step S503, the anchor terminal sends at least one task configured for the anchor account and a live broadcast room creation request to the server.

In step S504, the server creates a live room.

In step S505, the viewer terminal displays a live room including a task entry.

In step S506, the audience terminal displays the task aggregate item in response to the trigger operation for the task entry.

In step S507, the audience terminal obtains a plurality of tasks issued by the account of the live broadcast platform from the server, and displays the plurality of tasks in the task aggregate item.

In step S508, the viewer terminal displays at least one task selected from the plurality of tasks and a corresponding task execution entry in response to the selection operation received in the task aggregate item.

It should be noted that the specific implementation manner in steps S501 to S508 is similar to that in the above embodiment, and will not be described again here.

According to the method and the device, the tasks issued by the account number of the live broadcast platform are displayed through the task aggregation props in the live broadcast room, so that the user can intuitively know the requirements of other users in live broadcast, and the interaction diversity is improved; and the user is supported to select the task through the task aggregation prop, and the user is promoted to finish the task so as to enhance interactivity, so that the interactive efficiency and the live broadcast effect are improved, and communication resources and display resources used in the live broadcast process are saved.

The live broadcast processing method provided by the embodiment of the present application is described below by taking a specific application scenario as an example.

The embodiment of the application combines live broadcasting with rocking wish (namely the above-mentioned selection task), specifically, after the anchor makes a wish (namely the above-mentioned release task), the audience can help the anchor to realize the wish (namely the above-mentioned execution task), and in the process of realizing the wish, the anchor not only can improve the interactivity between the anchor and the audience, but also can help the anchor to convert more core fans and obtain more gifts (namely the above-mentioned virtual resources). The audience can not only shake the wish in the wish wall (namely the task aggregation prop) to help the anchor to realize the wish, but also make a wish, the wish is converged in the wish wall, and other participants can help the audience to realize the wish. The identities of the volunteers and the volunteers can be varied, the volunteers can become the volunteers, and the volunteers can also become the volunteers, so that the diversity of the interactive forms can be improved.

The embodiment of the application also supports the reward of virtual resources (such as gifts or virtual currency), and participants can obtain the virtual resources besides drawing wishes, so that the diversity and interestingness of participation results are increased, wherein the obtained virtual resources can be given to the anchor broadcast selectively, and the probability that audiences enter a live broadcast room can be improved. The method and the system for realizing the interaction between the anchor and the audience have the advantages that the anchor and the audience are closely associated through mutual realization of a desirable form, so that the viscosity and loyalty of the audience to the anchor can be improved.

Next, an implementation manner of the live broadcast processing method provided in the embodiment of the present application is described with reference to fig. 6, where fig. 6 is a schematic flow diagram of the live broadcast processing method provided in the embodiment of the present application.

In some embodiments, in fig. 6, the viewer enters the wish wall through the wish entrance (i.e., the task entrance described above), and may choose to "rock" to pan the wishes of the remaining participants and then help the remaining participants fulfill the wishes, which may indicate whether it is a direct wish or the wishes of the viewer, or the viewer may give up fulfilling the wishes or re-rocking the wishes. After the audience helps the rest participants to realize the desire, the own wish value is increased, the higher the wish value is, the more forward the position of the wish list (namely the list) is, wherein, the front part of the participants (such as the first three participants) in the wish list have exclusive nameplates for display, and the wish list is refreshed at a fixed frequency. In addition, if the audience participates in the "shaking wish" for a plurality of days (for example, 7 days), the audience can also obtain the virtual resource in a "shaking" mode, wherein the obtained virtual resource has a valid period, for example, the obtained virtual resource is invalid if the obtained virtual resource is not sent to the main broadcasting within 3 days, the virtual money obtained by the audience can also be used for purchasing the virtual object, and the obtained virtual money can be deposited into the electronic wallet. The viewer may also display a wish page (i.e., the task posting page described above) by triggering a wish button (i.e., the task posting entry described above) in the wish wall, and after the viewer fills out the wish list, wishes will be sent to the wish wall, waiting for the remaining participants to help themselves fulfill the wishes, wherein the default viewer may set a wish, and after the wish to be filled in is fulfilled, the wish may be filled in again, and the wishes may be changed or deleted. For audiences, the function of shaking wish can make audiences interact with other anchor broadcasters or audiences fast, and the conversion rate of converting the audiences into fans is improved, so that the viscosity of the audiences to a live broadcast platform is improved.

In some embodiments, when the anchor starts to play directly, the anchor can choose to add a "wag wish" function in the live broadcast room, so as to enter a wish setting page (i.e. the task configuration page mentioned above), and the anchor can set 5 wishes by default once, or can automatically set 5 wishes by directly using a wish template of the live broadcast platform. Wherein the wish setting page allows the anchor to set the number of wishes in relation to the anchor level, the higher the anchor level the greater the number of wishes can be set, for example, an anchor above 10 may set 10 wishes, an anchor above 20 may set 15 wishes, and so on. After the wish setting page of the anchor completes the wish, when the anchor starts to broadcast directly, the released wish is converged on the wish wall, the entrance of the rocking wish is displayed in the direct broadcasting room, and the audience can rock out the wish of the anchor through the entrance and help the anchor to realize the anchor. Of course, the anchor may also participate in shaking wishes to help the audience or other anchor achieve a wish. For the anchor, the function of shaking will not only improve the interaction between oneself and audience, but also improve the number of fans of oneself and the number of virtual resources obtained.

Next, an implementation of the live broadcast processing method provided in the embodiment of the present application is described with reference to fig. 7A, 7B, 7C, 7D, 8 and 9, where fig. 7A, 7B, 7C and 7D are application scenario diagrams of the live broadcast processing method provided in the embodiment of the present application, and fig. 8 and 9 are flow diagrams of the live broadcast processing method provided in the embodiment of the present application.

In some embodiments, the terminal is mainly responsible for displaying the entrance of the wish, the wish wall, the wish page, the wish list and the like, and simultaneously needs to support the interactive operation of the wish of shaking, the delivery wish and the like. The background server mainly provides various services for the functions of the volunteers, such as a volunteer storage service, a volunteer ranking service, a volunteer random drawing service and the like. The rocking function allows the anchor to participate with the audience, who may have the identities of both the volunteer and the volunteer.

Taking the anchor terminal as an example, before the anchor starts live broadcasting, the anchor terminal can select and set the function of the rocking wish, and after setting the wish, the anchor terminal requests the background server to create the live broadcasting room, and after the creation of the live broadcasting room is successful, the anchor terminal can automatically load the entrance of the rocking wish. The anchor can make the anchor terminal display the wish wall by triggering the entrance of the rocking wish, and can participate in the rocking wish process by using the rocking-rocking function, when the anchor does not want to participate in the rocking wish process, normal live broadcast can be continued in the live broadcast room, which will be described below with reference to fig. 8.

In step S801, in response to the wish setting operation, and after the wish setting is completed, a live view creation request is sent to the background server.

In some embodiments, before the anchor starts live broadcasting, the anchor terminal can select the function of setting a rocking wish, and after setting the own wish, the anchor terminal sends a live broadcasting room creation request to the background server, and the background server creates a live broadcasting room carrying an entrance of the rocking wish.

In step S802, when the creation of the live broadcast room is successful, a joyful entry is displayed in the live broadcast room, and when the creation of the live broadcast room is failed, a prompt message indicating that the creation failed is displayed.

In some embodiments, in fig. 7A, when the creation of the live broadcast room is successful, a rocking input (i.e., the task input 701 in fig. 7A) may be displayed on the right side of the live broadcast room, and when the creation of the live broadcast room fails, the anchor terminal displays a prompt message indicating that the background server failed to create the live broadcast room.

In step S803, when the anchor triggers the entrance of the rocking wish, a wish wall is displayed, the wish is extracted through the wish wall, and it is determined whether the wish is completed; and when the anchor does not trigger the swinging wish entrance, normally broadcasting live through the live broadcasting room.

In some embodiments, the rocking wisdom portal may be triggered when the anchor wants to turn on the rocking wisdom function, at which point the anchor terminal will request wisdom service data from the back-end server to present the contents of the current wisdom pool in a barrage.

In some embodiments, in fig. 7B, the anchor may extract a wish through a wish wall (i.e., task aggregation prop 702 in fig. 7B), when the anchor performs a motion sensing operation of "shake", the anchor terminal initiates a request to a wish random extraction service in the backend server, the backend server returns a wish message to the anchor terminal, and when the motion sensing operation of "shake" is finished, the anchor terminal displays the wish content in a popup window (i.e., task 703 in fig. 7B).

In step S804, when the anchor determines that the wish is completed, the wish value is increased.

In some embodiments, in FIG. 7B, when the anchor wants to help the volunteer to complete the wish, the "go to volunteer" button is clicked. When the anchor gives up the wishes, the anchor terminal can automatically hide the popup window by clicking the give-up button, and the anchor can extract the wishes again through the somatosensory operation of shaking once again.

In some embodiments, the live platform may periodically update the wish list, and if the wish value of the anchor wish is higher, the live platform may display the wish list. For example, in FIG. 7D, when the anchor clicks on the leaderboard entry 705, a favorites leaderboard is presented.

Taking audience terminals as an example, audiences enter the live broadcast room with the function of shaking wish through the cover mark of the live broadcast room, the audience terminals can display the entrance of the shaking wish on the right side of the live broadcast room, and the audiences can participate by triggering the entrance of the shaking wish. After the audience executes the motion sensing operation of 'shaking', the audience terminal randomly shows a piece of wish content, when the audience selects to realize the wish, the wish value is increased, the audience can give up the wish, and other wishes are extracted by using the motion sensing operation of 'shaking'. In addition, the audience can also enter the wishing page through the wishing button in the wishing wall, and after inputting the wish, the wish can be stored in the background server and then displayed on the wishing wall, which will be described below with reference to fig. 9.

In step S901, after the viewer enters the live broadcast room with the rocking wish function, when the viewer triggers the entrance of the rocking wish, the wish wall is displayed, and it is determined whether a new wish is added, and when the viewer determines the new wish, the new wish is released.

In some embodiments, for the live broadcast room with the rocking wish function, when the live broadcast home page of the audience terminal pulls the cover information of the live broadcast room, the content returned by the background server will contain the corresponding function field, when the audience terminal reads the field, the function icon of the corresponding rocking wish is displayed, and the audience can enter the live broadcast room with the rocking wish function through the function icon.

In some embodiments, the right side of the live broadcast room may show the entrance of the rocking wish, and after the viewer triggers the entrance of the rocking wish, the viewer terminal pulls the background server data, shows the content of the wish wall, and simultaneously shows the entrance of the list and the entrance of the wish (i.e., the task publishing entrance 704 in fig. 7C) in the wish wall.

In step S902, when the viewer confirms that no new desire is added, the desire is extracted through the desire wall and it is determined whether the desire is completed.

In some embodiments, when the audience draws the wish through the wish wall, the audience terminal initiates a request to a wish random drawing service in the background server, the background server returns wish information to the audience terminal, the wish information comprises the information of the volunteer and the content of the wish, and the audience terminal displays the wish information in a popup window form and provides an abandon button and a cancel button.

In step S903, when the viewer determines that the wish is completed, the wish value is increased.

In some embodiments, when the viewer completes the wish, the background server increases the wish value of the corresponding viewer account, and when the viewer chooses to give up the wish, the viewer terminal may extract other wishes by using the "pan-and-shake" somatic sense operation, i.e., the viewer terminal re-initiates a request to the wish random extraction service in the background server.

In some embodiments, in FIG. 7C, when the viewer triggers the wish button (i.e., task publishing portal 704 in FIG. 7C), the viewer terminal will present a wish page that allows the viewer to enter wishes and submit the wishes for storage by the back-office server for subsequent presentation at the wish wall and extraction and fulfillment by the remaining participants.

In some embodiments, when the audience clicks on the wish list entry (i.e., the list entry 705 in fig. 7D), the audience terminal initiates a request to the wish list ranking service in the background server to return the background server to the list order to display the wish list, wherein the information of the first three audiences with higher wish values in the live platform can be displayed in the form of nameplates.

The embodiment of the application combines live broadcasting and rocking wish and promotes participation of a main broadcasting and audiences in a wish form. The difference from the conventional live broadcast room is that the function of shaking wish has no obvious distinction between the identities of the anchor and the audience, and the anchor and the audience can be both volunteers and volunteers, so that the contact between the anchor and the audience is strengthened, and the communication between the anchor and the anchor is strengthened in the process of wishing. Meanwhile, the function of shaking the wish can extract not only the wish but also virtual resources, and adds surprise and expectation to the anchor and audiences in the participation process. For the live broadcast platform, the function improves the popularity of the live broadcast room and also improves the richness of the content of the live broadcast platform.

An exemplary structure of a live broadcast processing apparatus implemented as a software module according to an embodiment of the present application is described below with reference to fig. 2.

In some embodiments, as shown in fig. 2, the software modules stored in the live processing device 455 of the memory 450 may include: the display module 4551 is configured to display a task aggregate item in response to a trigger operation for a task entry in a live broadcast scene; an obtaining module 4552, configured to obtain multiple tasks issued by an account of a live broadcast platform, and display the multiple tasks in a task aggregation item; a selection module 4553, configured to display at least one task selected from the plurality of tasks and a corresponding task execution entry in response to a selection operation received in the task aggregate item; and the task execution inlet is used for displaying a corresponding task execution page when being triggered.

In the above scheme, the obtaining module 4552 is further configured to display a plurality of barrage in the task aggregate prop, where each barrage includes at least part of content of one task; wherein at least part of the content comprises at least one of: and issuing the account number, the task content and the task keywords of the task.

In the above scheme, the obtaining module 4552 is further configured to determine a matching degree between a login account and each task, where the login account is an account for logging in a live broadcast scene; determining a display parameter related to the matching degree of each task; wherein the display parameter is used to characterize at least one of: the significance degree of the bullet screens, the content integrity degree of the bullet screens and the sequencing of the bullet screens; and displaying a plurality of barrages in the task aggregation prop according to the display parameters.

In the foregoing solution, when the selection operation is a motion sensing operation, the selection module 4553 is further configured to, in response to the motion sensing operation received in the task aggregation item, acquire an operation parameter of the motion sensing operation, select at least one task from a plurality of tasks displayed in the task aggregation item according to the operation parameter, and display details of the selected at least one task and a corresponding task execution entry.

In the above scheme, the operating parameters include direction and magnitude; and a selecting module 4553, further configured to determine at least one task adapted to the direction and the magnitude among the plurality of tasks displayed in the task aggregate prop.

In the above scheme, the obtaining module 4552 is further configured to screen out, from a task set issued by an account of a live platform, a plurality of tasks that meet the following conditions: tasks issued by accounts having an interactive relationship with the login account, tasks belonging to the same type as the tasks executed by the login account and tasks within the capability range of the login account; the login account is an account for logging in a live scene.

In the above scheme, the selecting module 4553 is further configured to display a virtual resource selected from the virtual resource library and granted to the login account, and a virtual resource transfer entry corresponding to the virtual resource; responding to a trigger operation aiming at a virtual resource transfer entry, and sending the virtual resource to a target account, wherein the type of the target account comprises: audience account numbers and anchor account numbers; the login account is an account for logging in a live scene.

In the above scheme, the selecting module 4553 is further configured to display at least one candidate account in response to a triggering operation for a virtual resource transfer entry; the type of the candidate account comprises at least one of the following types: an account number in a live broadcast room watched by a login account number, an account number having an interaction relationship with the login account number, and an account number having an interaction frequency exceeding an interaction frequency threshold value with the login account number; and responding to the account selection operation, taking the selected at least one candidate account as a target account, and sending the virtual resources to the target account.

In the foregoing solution, the selecting module 4553 is further configured to determine to perform, when the login account satisfies the virtual resource granting condition, an operation of displaying a virtual resource selected from the virtual resource library and granted to the login account and a virtual resource transfer entry corresponding to the virtual resource; wherein the virtual resource granting condition includes at least one of: the activity of the login account participating in the interaction based on the task aggregation prop exceeds an activity threshold; the number of days that the login account continuously releases or performs tasks exceeds a threshold number of days.

In the foregoing solution, the selecting module 4553 is further configured to, when the virtual resource granted to the login account is not used within the preset time duration, retrieve the virtual resource into the virtual resource pool.

In the above scheme, the live broadcast scene includes a live broadcast room page, and when the login account of the live broadcast room page is the anchor account, the display module 4551 is further configured to respond to a trigger operation for a task entry in the live broadcast scene, and display a task configuration page; responding to task configuration operation received in a task configuration page, and acquiring at least one task configured by the task configuration operation aiming at the anchor account; or when the task configuration operation is not received within the waiting time, acquiring at least one task configured by the live broadcast platform for the anchor account; and releasing at least one task configured for the anchor account to a live broadcast platform, creating a live broadcast room, and displaying the live broadcast room comprising a task entrance.

In the foregoing solution, the display module 4551 is further configured to respond to a live broadcast room creation operation of a anchor account, and display a task configuration page matched with a level according to the level of the anchor account; the number of tasks which can be configured by the anchor account in the task configuration page is multiple, and the anchor account is positively correlated with the level.

In the above scheme, when the login account is a viewer account, the obtaining module 4552 is further configured to display a task issuing entry in the task aggregation item; responding to the triggering operation of the audience account aiming at the task issuing entrance, displaying a task issuing page, and acquiring at least one task to be issued by the audience account through the task issuing page; and responding to the task issuing operation received in the task issuing page, and issuing at least one task to be issued by the audience account to the live broadcast platform.

In the above scheme, the obtaining module 4552 is further configured to obtain the number of tasks that the viewer account has issued to the live platform; when the number is not less than the threshold value of the number of the tasks allowed to be issued, locking the permission of issuing a new task by the audience account; and when the number is less than the threshold value of the number of the tasks allowed to be published, determining that the operation of displaying the task publishing page is to be performed.

In the above scheme, the obtaining module 4552 is further configured to display at least one task issued by the viewer account and a corresponding task editing entry; in response to a triggering operation aiming at the task editing entry, deleting or modifying at least one task issued by the audience account; and when the number of the tasks published by the audience account is less than the threshold value of the number of the tasks allowed to be published, unlocking the permission of the audience account to publish the new tasks.

In the scheme, the selection module 4553 is further configured to display a task abandoning entry in the task aggregation prop; and in response to the triggering operation aiming at the task abandoning entrance, stopping displaying the selected at least one task and the corresponding task execution entrance, and recycling the selected at least one task into the task aggregation prop.

In the above scheme, the selection module 4553 is further configured to display a list entry; responding to triggering operation aiming at the list entry, and displaying a list page, wherein the list page comprises descending order of the plurality of accounts of the live broadcast platform according to the corresponding task scores; the task integration is positively correlated with the number of tasks executed by the account.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the live broadcast processing method described in the embodiment of the present application.

The embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are stored, and when being executed by a processor, the computer-executable instructions will cause the processor to execute a live broadcast processing method provided in the embodiment of the present application, for example, the live broadcast processing methods shown in fig. 3, fig. 4, fig. 5, fig. 6, fig. 8, and fig. 9, and a computer includes various electronic devices including an intelligent terminal and a server.

In some embodiments, the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

In some embodiments, the computer-executable instructions may be in the form of programs, software modules, scripts or code written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and they may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

By way of example, computer-executable instructions may correspond, but do not necessarily have to correspond, to files in a file system, and may be stored in a portion of a file that holds other programs or data, e.g., in one or more scripts in a hypertext markup language document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

By way of example, computer-executable instructions may be deployed to be executed on one electronic device or on multiple electronic devices located at one site or distributed across multiple sites and interconnected by a communication network.

In summary, according to the embodiment of the application, the tasks issued by the account number of the live broadcast platform are displayed through the task aggregation prop in the live broadcast scene, so that the user can intuitively know the requirements of other users in the live broadcast, and the interaction diversity is improved; and the user is supported to select the task through the task aggregation prop, and the user is promoted to finish the task so as to enhance interactivity, so that the interactive efficiency and the live broadcast effect are improved, and communication resources and display resources used in the live broadcast process are saved.

The above description is only an example of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A live broadcast processing method, characterized in that the method comprises:

2. The method of claim 1, wherein said displaying the plurality of tasks in the task aggregate prop comprises:

displaying a plurality of barrage in the task aggregation prop, wherein each barrage comprises at least part of content of one task;

wherein the at least part of the content comprises at least one of: and issuing the account number, the task content and the task keywords of the task.

3. The method of claim 2, wherein the displaying a plurality of barrages in the task aggregate prop comprises:

determining the matching degree between a login account and each task, wherein the login account is an account for logging in the live broadcast scene;

determining a display parameter associated with the degree of matching for each of the tasks;

wherein the display parameter is used to characterize at least one of: the significance degree of the bullet screens, the integrity degree of the task contents in the bullet screens and the sequencing of the bullet screens;

and displaying the plurality of barrages in the task aggregation prop according to the display parameters.

4. The method of claim 1,

when the selection operation is a somatosensory operation, the displaying at least one task selected from the plurality of tasks and a corresponding task execution entry in response to the selection operation received in the task aggregate item, including:

and responding to the somatosensory operation received in the task aggregation prop, acquiring an operation parameter of the somatosensory operation, selecting at least one task from the plurality of tasks displayed in the task aggregation prop according to the operation parameter, and displaying the detailed content of the selected at least one task and a corresponding task execution entry.

5. The method of claim 4,

the operating parameters include direction and magnitude;

selecting at least one task from the plurality of tasks displayed in the task aggregate prop according to the operating parameters, including:

determining at least one task adapted to the direction and the magnitude among the plurality of tasks displayed in the task aggregate prop.

6. The method of claim 1, wherein the obtaining of the plurality of tasks published by the account of the live platform comprises:

screening a plurality of tasks meeting the following conditions from a task set issued by the account of the live broadcast platform:

tasks issued by accounts having an interactive relationship with the login account, tasks belonging to the same type as the tasks executed by the login account and tasks within the capability range of the login account;

and the login account is an account for logging in the live broadcast scene.

7. The method of claim 1, wherein, in response to the selection operation received in the task aggregate prop, the method further comprises:

displaying virtual resources selected from a virtual resource library and granted to a login account and a virtual resource transfer entrance corresponding to the virtual resources;

responding to a trigger operation aiming at the virtual resource transfer entry, and sending the virtual resource to a target account, wherein the type of the target account comprises: audience account numbers and anchor account numbers;

and the login account is an account for logging in the live broadcast scene.

8. The method of claim 7, wherein sending the virtual resource to a target account in response to the triggering operation for the virtual resource transfer entry comprises:

responding to a triggering operation aiming at the virtual resource transfer entry, and displaying at least one candidate account;

wherein the type of the candidate account includes at least one of: an account number in a live broadcast room watched by the login account number, an account number having an interaction relationship with the login account number, and an account number having an interaction frequency exceeding an interaction frequency threshold value with the login account number;

and responding to account selection operation, taking the selected at least one candidate account as the target account, and sending the virtual resource to the target account.

9. The method of claim 7, wherein prior to displaying the virtual resource selected from the virtual resource pool and granted to the login account, and the virtual resource delivery entry corresponding to the virtual resource, the method further comprises:

when the login account meets the virtual resource granting condition, determining to execute the operation of displaying the virtual resource selected from the virtual resource library and granted to the login account and the virtual resource transfer entry corresponding to the virtual resource;

wherein the virtual resource grant condition includes at least one of: the activity of the login account number participating in the interaction based on the task aggregation prop exceeds an activity threshold; the number of days that the login account continuously releases or executes tasks exceeds a threshold number of days.

10. The method of claim 7, further comprising:

and when the virtual resource granted to the login account is not used within a preset time length, the virtual resource is recovered to the virtual resource library.

11. The method of claim 1,

the live broadcast scene comprises a live broadcast room page, and when a login account of the live broadcast room page is a main broadcast account, before a task aggregation prop is displayed in response to a trigger operation aiming at a task entry in the live broadcast scene, the method further comprises the following steps:

responding to the creation operation of the live broadcast room of the anchor account, and displaying a task configuration page;

responding to task configuration operation received in the task configuration page, and acquiring at least one task configured by the task configuration operation aiming at the anchor account; or when the task configuration operation is not received within the waiting time, acquiring at least one task configured by the live broadcast platform for the anchor account;

and issuing at least one task configured for the anchor account to the live broadcast platform, creating a live broadcast room, and displaying the live broadcast room comprising the task entry.

12. The method of claim 11, wherein displaying a task configuration page in response to a live-room creation operation of the anchor account comprises:

responding to the creation operation of the live broadcast room of the anchor account, and displaying a task configuration page matched with the level according to the level of the anchor account;

the anchor account is capable of configuring a plurality of tasks in the task configuration page, and is positively correlated with the level.

13. The method of claim 1, wherein when the login account is a viewer account, when the displaying task aggregate items, the method further comprises:

displaying a task issuing entrance in the task aggregation prop;

responding to the triggering operation of the audience account aiming at the task publishing entry, displaying a task publishing page, and acquiring at least one task to be published by the audience account through the task publishing page;

and responding to the task issuing operation received in the task issuing page, and issuing at least one task to be issued by the audience account to the live broadcast platform.

14. The method of claim 13, wherein prior to said displaying a task post page, the method further comprises:

acquiring the number of tasks which are issued to the live broadcast platform by the audience account;

when the number is not less than the threshold value of the number of the tasks allowed to be issued, locking the permission of the audience account to issue the new tasks;

and when the number is smaller than the threshold value of the number of the tasks allowed to be published, determining that the operation of displaying the task publishing page is to be executed.

15. The method of claim 14, wherein after the locking the viewer account's right to issue a new task, the method further comprises:

displaying at least one task issued by the audience account and a corresponding task editing entry;

in response to a triggering operation aiming at the task editing entry, deleting or modifying at least one task issued by the audience account;

and when the number of the tasks published by the audience account is smaller than the threshold value of the number of the tasks allowed to be published, unlocking the permission of the audience account to publish the new tasks.

16. The method of claim 1, wherein in said displaying at least one task selected from the plurality of tasks and a corresponding task execution entry, the method further comprises:

displaying a task abandoning entrance in the task aggregation prop;

and in response to the triggering operation aiming at the task abandoning entrance, stopping displaying the selected at least one task and the corresponding task execution entrance, and recovering the selected at least one task to the task aggregation prop.

17. The method of claim 1, wherein, when displaying the task aggregate prop, the method further comprises:

displaying the list entry;

responding to a triggering operation aiming at the list entry, and displaying a list page, wherein the list page comprises descending order of the plurality of accounts of the live broadcast platform according to the corresponding task scores;

wherein the task points are positively correlated with the number of tasks executed by the account.

18. A live broadcast processing apparatus, comprising:

19. An electronic device, comprising:

a memory for storing computer executable instructions;

a processor for implementing the live processing method of any of claims 1-17 when executing computer-executable instructions stored in the memory.

20. A computer-readable storage medium having stored thereon computer-executable instructions for implementing the live processing method of any of claims 1-17 when executed.