CN114679598A - Live broadcast pushing method and device - Google Patents

Live broadcast pushing method and device Download PDF

Info

Publication number
CN114679598A
CN114679598A CN202210295037.6A CN202210295037A CN114679598A CN 114679598 A CN114679598 A CN 114679598A CN 202210295037 A CN202210295037 A CN 202210295037A CN 114679598 A CN114679598 A CN 114679598A
Authority
CN
China
Prior art keywords
live
push
stream
live broadcast
anchor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202210295037.6A
Other languages
Chinese (zh)
Other versions
CN114679598B (en
Inventor
姜栋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Bilibili Technology Co Ltd
Original Assignee
Shanghai Bilibili Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Bilibili Technology Co Ltd filed Critical Shanghai Bilibili Technology Co Ltd
Priority to CN202210295037.6A priority Critical patent/CN114679598B/en
Publication of CN114679598A publication Critical patent/CN114679598A/en
Application granted granted Critical
Publication of CN114679598B publication Critical patent/CN114679598B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21Server components or server architectures
    • H04N21/218Source of audio or video content, e.g. local disk arrays
    • H04N21/2187Live feed
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/24Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
    • H04N21/2408Monitoring of the upstream path of the transmission network, e.g. client requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/2625Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for delaying content or additional data distribution, e.g. because of an extended sport event
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44204Monitoring of content usage, e.g. the number of times a movie has been viewed, copied or the amount which has been watched
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/478Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

The application provides a live broadcast pushing method and a live broadcast pushing device, wherein the live broadcast pushing method comprises the following steps: receiving a live broadcast request of a target anchor, and acquiring anchor attribute information of the target anchor according to the live broadcast request; determining push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for determining a live stream processing strategy by an anchor client of the target anchor, and the push stream mode information comprises a delay push mode and a normal push mode; and sending the push stream mode information to the anchor client. Through setting up two kinds of different plug flow modes, postpone the live stream that the propelling movement corresponds under the unmanned circumstances of watching in the live broadcast room, wait until really there is spectator to watch, just make live stream propelling movement to push away stream node server, let most have the anchor that the user watched no longer occupy the upstream bandwidth resource completely, save the bandwidth cost of live platform.

Description

Live broadcast pushing method and device
Technical Field
The application relates to the technical field of mutual interest network live broadcasting, in particular to a live broadcasting pushing method. The application also relates to a live broadcast push device, a computing device and a computer readable storage medium.
Background
With the growth of live platform services, users watching live broadcasts also increase, and the number of anchor broadcasts also continuously increases. According to the current live broadcast environment, most watching users are concentrated in some large anchor broadcasters or official rooms, through live broadcast data statistics, 80% of watching users are concentrated in 10% of live broadcast rooms, more than 50% of live broadcast rooms are not watched by users, but the live broadcast platform provides the same uplink edge node scheduling service for 50% of users, and therefore the problems of high cost and low benefit are caused. In summary, how to enable most of the live broadcasting rooms without audience to watch to no longer occupy the uplink bandwidth resource is a problem that needs to be solved urgently at present.
Disclosure of Invention
In view of this, the present application provides a live broadcast push method. The application also relates to a live broadcast pushing device, a computing device and a computer readable storage medium, which are used for solving the problem of resource waste caused by the fact that a live broadcast room where a user watches is unavailable in the prior art.
According to a first aspect of an embodiment of the present application, a live broadcast push method is provided, which is applied to a main broadcast client, and includes:
sending a live broadcast request to a scheduling server according to a received live broadcast instruction;
receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode;
determining a live streaming processing strategy according to the push streaming mode information;
and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
According to a second aspect of the embodiments of the present application, there is provided a live broadcast push method applied to a scheduling server, including:
receiving a live broadcast request of a target anchor, and acquiring anchor attribute information of the target anchor according to the live broadcast request;
determining push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for determining a live stream processing strategy by an anchor client of the target anchor, and the push stream mode information comprises a delay push mode and a normal push mode;
and sending the push stream mode information to the anchor client.
According to a third aspect of the embodiments of the present application, there is provided a live broadcast push method applied to a live broadcast scheduling system, the live broadcast scheduling system including a host client and a scheduling server, wherein,
the scheduling server receives a live broadcast request of a target anchor, acquires anchor attribute information of the target anchor according to the live broadcast request, and determines push flow mode information according to the anchor attribute information, wherein the push flow mode information is used for an anchor client of the target anchor to determine a live broadcast flow processing strategy, the push flow mode information comprises a delayed push mode and a normal push mode, and the push flow mode information is sent to the anchor client;
the anchor client sends a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
According to a fourth aspect of the embodiments of the present application, a live broadcast push device is provided, including: applied to an anchor client, comprising:
the sending module is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction;
a receiving module configured to receive push stream mode information returned by the scheduling server in response to the live broadcast request, wherein the push stream mode information includes a delayed push mode and a normal push mode;
a determining module configured to determine a live stream processing policy according to the stream pushing mode information;
and the processing module is configured to process the live stream corresponding to the live stream request based on the live stream processing strategy.
According to a fifth aspect of the embodiments of the present application, there is provided a live broadcast push device, including: applied to a scheduling server, comprising:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is configured to receive a live broadcast request of a target anchor and acquire anchor attribute information of the target anchor according to the live broadcast request;
a determining module configured to determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing policy, and the push stream mode information includes a delayed push mode and a normal push mode;
a sending module configured to send the push stream mode information to the anchor client.
According to a sixth aspect of the embodiments of the present application, there is provided a live broadcast push system, including: a host client, a dispatch server, wherein,
the scheduling server is configured to receive a live broadcast request of a target anchor, acquire anchor attribute information of the target anchor according to the live broadcast request, and determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing strategy, the push stream mode information comprises a delayed push mode and a normal push mode, and the push stream mode information is sent to the anchor client;
the anchor client is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
According to a seventh aspect of embodiments of the present application, there is provided a computing device, including a memory, a processor, and computer instructions stored on the memory and executable on the processor, where the processor implements the steps of the live push method when executing the computer instructions.
According to an eighth aspect of embodiments of the present application, there is provided a computer-readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the live push method.
The live broadcast push method provided by the application is applied to a main broadcast client and comprises the following steps: sending a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving stream pushing mode information returned by the scheduling server in response to the live broadcast request; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
According to the embodiment of the application, different live stream processing strategies are set for different live broadcast rooms, when the live stream processing strategy of the live broadcast room is a delay pushing strategy, live streams corresponding to the live broadcast room are not pushed, bandwidth resource occupation of an uplink server is reduced, and running cost of a live broadcast platform is reduced.
Drawings
Fig. 1 is a flowchart of a live broadcast push method applied to a host client according to an embodiment of the present application;
fig. 2 is a flowchart of a live broadcast push method applied to a scheduling server according to an embodiment of the present application;
fig. 3 is a flowchart of a live broadcast pushing method applied to a live broadcast scheduling system according to an embodiment of the present application;
fig. 4 is a processing flow diagram of a live push method applied to delayed push streaming according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a live broadcast push apparatus applied to a host client according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a live broadcast push apparatus applied to a scheduling server according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a live broadcast push system according to an embodiment of the present application;
fig. 8 is a block diagram of a computing device according to an embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the one or more embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the present application. As used in one or more embodiments of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present application refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments of the present application to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first aspect may be termed a second aspect, and, similarly, a second aspect may be termed a first aspect, without departing from the scope of one or more embodiments of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
First, the noun terms to which one or more embodiments of the present application relate are explained.
An edge node server: the user side server is close to the user physically, so that the transmission delay is low.
And uplink scheduling, namely when the anchor clicks the broadcast, scheduling according to the network condition, the geographic position and other information of the anchor at that time, and selecting a stream pushing node for the anchor.
Delaying plug flow: the anchor stream is not pushed to the edge node first, and the data is pushed when the user really watches the data.
At present, when an anchor is ready to start live broadcasting, the anchor can click to broadcast through an anchor client to acquire a streaming address, an uplink streaming scheduling server can return to a nearby streaming node server according to the current geographic position of the anchor so that the anchor pushes a stream to the streaming node server, and a related edge node server sends a broadcast callback to tell a live broadcast platform that the anchor starts live broadcasting. When a user refreshes a recommended page or a page of other live broadcast platforms through a user client, the user can see a picture of a live broadcast room of an initiated anchor broadcast, the user can click a related live broadcast room according to own interest to watch the picture, the user client can pull a live broadcast stream of the live broadcast room from a downlink edge node server at the moment, and the downlink edge node server inquires a stream pushing address of the initiated broadcast through a scheduling server of the live broadcast platform to return to a source so that the user can watch the live broadcast through the user client.
Along with the growth of live platform service, the number of live broadcasting rooms of a live broadcasting platform is continuously increased, through relevant data statistics, more than 50% of live broadcasting rooms are not watched by users, but the live broadcasting platform still provides the same uplink edge node scheduling service for the live broadcasting rooms, namely, the live broadcasting streams of the live broadcasting rooms which are not watched by people are pushed, the phenomenon of uplink bandwidth waste of the live broadcasting platform is caused, zero income is brought to the live broadcasting platform, and therefore, the main broadcasting of the live broadcasting rooms is not lost when the high uplink bandwidth cost of the live broadcasting platform is reduced, and the problem of solving at present is solved.
Based on this, in the present application, a live broadcast push method is provided for reducing the problem of high cost of the upstream bandwidth of the live broadcast platform, and the present application also relates to a live broadcast push apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.
Fig. 1 shows a flowchart of a live broadcast push method applied to a anchor client according to an embodiment of the present application, which specifically includes the following steps:
step 102: and sending a live broadcast request to a scheduling server according to the received live broadcast instruction.
The anchor client can be understood as a terminal for enabling live broadcasting by the anchor, and can be a mobile phone, a computer and the like; the live broadcasting instruction can be understood as a live broadcasting starting instruction sent by the anchor to the anchor client, and after the anchor client receives the live broadcasting instruction, the anchor client considers that the anchor is ready for live broadcasting, and then the anchor client sends a live broadcasting request to the scheduling server; the live broadcast request can be understood as a live broadcast starting request sent by a main broadcast client to a scheduling server, and after the scheduling server receives the live broadcast request sent by the main broadcast client, the scheduling server determines a stream pushing mode for the live broadcast request.
In practical application, the live broadcast instruction may be an instruction sent by an anchor through an anchor client clicking a live broadcast button, and the anchor client sends a live broadcast request to the scheduling server according to the received live broadcast instruction.
In a specific embodiment of the application, the anchor client a sends a live broadcast instruction to the anchor client when the anchor client a clicks to start live broadcast, and after receiving the live broadcast start instruction sent by the anchor client a, the anchor client sends a live broadcast request to the scheduling server according to the live broadcast instruction.
Specifically, sending a live broadcast request to a scheduling server according to a received live broadcast instruction includes:
generating a live broadcast request according to a received live broadcast instruction;
and sending the live broadcast request to a scheduling server.
In practical application, the anchor client generates information related to anchor live broadcast according to a live broadcast instruction, generates a live broadcast request according to the related information, and after the live broadcast request is sent to a scheduling server, the scheduling server can schedule according to the live broadcast request, and push node servers corresponding to the live broadcast request respectively to the anchor client.
In a specific embodiment of the present application, following the above example, the anchor client generates a live broadcast request related to the current live broadcast of the anchor a according to a received live broadcast instruction sent by the anchor a, and sends the live broadcast request to the scheduling server.
Step 104: and receiving push stream mode information returned by the scheduling server in response to the live broadcast request, wherein the push stream mode information comprises a delay push mode and a normal push mode.
The push stream mode information can be understood as information containing a push stream mode corresponding to the anchor, the push stream mode can be divided into two types, one type is a normal push stream mode, and in the normal push stream mode, the anchor client can directly push the live stream of the live broadcast to the upstream push stream node server; the other is a delayed stream pushing mode, and in the delayed stream pushing mode, the anchor client does not push the live stream of the live broadcast to the uplink stream pushing node server.
In practical application, in order to reduce bandwidth resources caused by stream pushing of live broadcast rooms watched by no one, different stream pushing modes are set for live broadcast rooms of different anchor broadcasters, live broadcast streams are pushed by live broadcast rooms watched by multiple persons according to a normal stream pushing mode, live broadcast screenshot pictures corresponding to the live broadcast streams are pushed by the live broadcast rooms watched by no one according to a delayed stream pushing mode, the live broadcast streams are really pushed when audiences watch the live broadcast streams, and therefore the uplink bandwidth cost of a scheduling server and a stream pushing node server is reduced.
In a specific embodiment of the present application, following the above example, the anchor client receives the push stream mode information returned by the scheduling server, and if the push stream mode information is delayed push, the anchor client performs a subsequent push process according to the push stream mode information.
Step 106: and determining a live stream processing strategy according to the stream pushing mode information.
In practical application, when the push flow mode information is normal push, the live flow processing strategy is to immediately push the live flow to a push flow node server; and when the push stream mode information is delayed push, the live stream processing strategy is not to push the live stream to the push stream node server.
In practical application, when the push streaming mode information is delayed push, the anchor client does not push the live streaming corresponding to the live broadcast room to the push streaming node server, but pushes a related live broadcast picture to the scheduling server in order to enable a user to see that the anchor is live broadcast through the live broadcast platform.
In a specific embodiment of the present application, following the above example, after receiving the push stream mode information, the anchor client determines, according to the push stream mode information, a live stream processing policy for pushing a live stream by the anchor client, so as to determine whether the live stream needs to be pushed immediately according to the live stream processing policy, after receiving that the push stream mode information is a normal push stream mode, and determines, according to the push stream mode information, that the live stream processing policy is to push the live stream to the push stream node server immediately, and then the subsequent anchor client pushes the live stream corresponding to the live broadcast room to the push stream node server.
In another embodiment of the present application, following the above example, when the anchor client receives the stream pushing mode information as the delayed stream pushing mode, the anchor client does not directly push the live stream corresponding to the live broadcast room to the stream pushing node server, and when a subsequent user enters the live broadcast room to watch, the anchor client pushes the live stream to the stream pushing node server.
Step 108: and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
In practical application, the anchor client can process the live stream according to different live stream processing strategies, and in a normal stream pushing mode, the anchor client can immediately push the live stream to a stream pushing node server; in the delayed stream pushing mode, the anchor client does not push the live stream to the stream pushing node server immediately, but collects some live frames to push to the scheduling server, so that the scheduling server can display the live frames of the anchor on the live platform.
Specifically, processing the live stream corresponding to the live request based on the live stream processing policy includes:
under the condition that the live stream processing strategy is delayed push, generating live heartbeat information according to a live stream corresponding to the live request, wherein the live heartbeat information comprises live screenshot information;
and sending the live heartbeat information to the scheduling server.
The delayed push can be understood that the anchor client does not immediately push the live stream corresponding to the live broadcast room to the push stream node server, but generates live broadcast heartbeat information of the live broadcast room according to the live stream corresponding to the live broadcast request; the live broadcast heartbeat information can be understood as information sent to the scheduling server at intervals, and can comprise live broadcast duration information, live broadcast screenshot information, live broadcast room titles and other information;
in practical application, for some live broadcast rooms which are not watched by people, the stream pushing mode is set to be delayed pushing, the corresponding anchor client side cannot push the live broadcast stream to the stream pushing node server, but can acquire audio and video data of the current live broadcast of the anchor, generate a corresponding live broadcast picture, and send the information of the live broadcast picture, the live broadcast duration and the like to the scheduling server, so that the scheduling server can know that the current anchor is being played, and then generate live broadcast recommendation information corresponding to the live broadcast of the anchor and display the live broadcast recommendation information to a user.
In a specific embodiment of the application, along the above example, if the anchor client determines that the live stream processing strategy is delayed push, the live stream is not pushed to the push node server, corresponding live heartbeat information is generated according to the live stream, the live heartbeat information carries an anchor picture, a live time and a live title of a current anchor, and the anchor client sends the generated live heartbeat information to the scheduling server.
Specifically, generating live broadcast heartbeat information according to a live broadcast stream corresponding to the live broadcast request includes:
generating live broadcast state information according to a live broadcast stream corresponding to the live broadcast request, and acquiring live broadcast screenshot information corresponding to the live broadcast stream;
and generating live heartbeat information according to the live state information and the live screenshot information.
The live broadcast state information can be understood as state information of whether a current anchor is live broadcast or not, the live broadcast state information can comprise information such as the live broadcast time length, anchor broadcast identification information and anchor broadcast popularity information, the live broadcast time length, the anchor broadcast identification information and the live broadcast title information in the live broadcast state information can be obtained according to a live broadcast request, and a scheduling server can judge whether a live broadcast room corresponding to the current anchor is live broadcast or not according to the live broadcast state information so as to show the live broadcast information of an audience to enable the audience to select to watch according to the live broadcast information; the live screenshot information can be understood as a live frame corresponding to a live broadcast room, and the live screenshot information is sent to the scheduling server, so that the scheduling server can display the corresponding live frame to be watched, and a user can be attracted to click to watch the live frame.
In practical application, the anchor client side currently sends that the anchor client side is in a delayed stream pushing mode, only acquires the current live audio and video data of the anchor and does not push the data to a stream pushing node server, but generates live broadcast state information according to a live stream corresponding to a live broadcast request, packs the live broadcast state information and live broadcast screenshot information to generate live broadcast heartbeat information, and sends the live broadcast heartbeat information to a scheduling server at regular time, so that the scheduling server displays information such as live broadcast pictures, live broadcast titles and the like of the current anchor room to each user on a live broadcast platform, and attracts the user to watch the live broadcast pictures. In an actual situation, the scheduling server receives live broadcast heartbeat information corresponding to all live broadcast rooms in live broadcast, collects information of all anchor broadcasts, pushes the information to a user when the user browses, and the live broadcast platform can judge whether live broadcast content of the corresponding anchor broadcasts violates rules or not according to live broadcast pictures.
In a specific embodiment of the application, following the above example, the live broadcast client generates live broadcast state information according to a live broadcast stream of the anchor a, acquires corresponding live broadcast screenshot information by adopting a current live broadcast stream of the anchor a, packages the live broadcast state information and the direct screenshot information to generate live broadcast heartbeat information, and sends the live broadcast heartbeat information to the scheduling server. And the anchor client side sends live heartbeat information to the scheduling server every 5 minutes so as to update the related information about the live broadcast room on the live broadcast platform.
Further, after generating live heartbeat information according to a live stream corresponding to the live request, the method further includes:
receiving a stream pushing instruction aiming at the live stream;
and responding to the stream pushing instruction, and sending the live stream to a target server.
After a user enters the live broadcast room to watch, the scheduling server sends a stream pushing instruction for the live broadcast stream corresponding to the live broadcast room, so that the anchor client pushes the live broadcast stream to a corresponding stream pushing node server for the user to watch by stream pulling; the target server can be understood as a streaming node server which is closer to the anchor, so that the time for a user to enter a live broadcast room to wait for watching a live broadcast picture is reduced.
In practical application, as long as one person enters a live broadcast room in a delayed stream pushing mode to watch, the scheduling server sends a stream pushing instruction for a corresponding live broadcast stream to the live broadcast room, and after receiving the stream pushing instruction, an anchor client corresponding to the live broadcast room sends the live broadcast stream server to a corresponding stream pushing node server.
In a specific embodiment of the present application, following the above example, the anchor client receives a stream pushing instruction for a live stream, prepares to push the live stream to a stream pushing node server, determines a target server according to the stream pushing instruction, and pushes the live stream to the target server.
Specifically, sending the live stream to a target server in response to the stream pushing instruction includes:
acquiring a target server identifier in the stream pushing instruction;
determining a target server according to the target server identification;
and sending the live stream to the target server.
The target server identifier can be understood as the identifier of the target streaming node server, and the target streaming node server can be determined according to the identifier, so that the live streaming is pushed to the target streaming node server.
In practical application, the anchor client pushes the live stream to a streaming node server near the anchor, so that a user can quickly watch the live stream.
In a specific embodiment of the present application, along with the above example, the anchor client obtains a target server identifier in a stream pushing instruction sent by the scheduling server, determines a target server a according to the target server identifier, and sends a live stream to the target server a.
In another streaming mode, a anchor client may normally push a live stream, and specifically, processing a live stream corresponding to the live request based on the live stream processing policy includes:
and under the condition that the stream pushing mode information is normally pushed, pushing the live stream corresponding to the live request to a target server.
In practical application, under the condition that the stream pushing mode information is normally pushed, the anchor client side can push the live stream to the target server according to a traditional live pushing flow after the anchor is played.
In a specific embodiment of the present application, following the above example, if the anchor client determines that the push stream mode information is normally pushed, the anchor client will immediately push the live stream corresponding to the live request to the target server.
The application provides a live broadcast push method applied to a main broadcast client, which comprises the following steps: sending a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving streaming mode information returned by the scheduling server in response to the live request, wherein the live heartbeat information comprises live screenshot information; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy. The live stream pushing strategy is determined by enabling the anchor client to obtain the own push stream mode, the live stream is processed according to the live stream pushing strategy, under the condition that the push stream mode of the anchor corresponding to the live room is the delayed push stream mode, the anchor client does not push the live stream to the push stream node server, but collects relevant live stream information and sends the relevant live stream information to the scheduling server, when audience watching really exists, the live stream is pushed to the push stream node server, most of the anchor which is not watched by the user does not occupy uplink bandwidth resources any more, and the bandwidth cost of a live platform is saved.
Fig. 2 shows a flowchart of a live broadcast push method applied to a scheduling server according to an embodiment of the present application, which specifically includes the following steps:
step 202: receiving a live broadcast request of a target anchor, and acquiring anchor attribute information of the target anchor according to the live broadcast request.
The live broadcast request can be understood as a request for a target anchor to accurately start live broadcast, and after receiving the live broadcast request of the anchor, the scheduling server considers that the anchor is about to start live broadcast. The anchor attribute information may be understood as some information related to the anchor, for example, the anchor attribute information may include an anchor identifier, anchor live content, historical live broadcast duration, anchor fan count, and the like, and the scheduling server may determine whether the anchor is watched by someone next live broadcast according to the anchor attribute information.
In practical application, a scheduling server receives live broadcast requests of a plurality of anchor broadcasters, determines one target anchor broadcaster, and after receiving the live broadcast request of the target anchor broadcaster, acquires attribute information of the target anchor, so as to judge whether the live broadcast of the target anchor is watched by people, and determine a stream pushing mode of the target anchor.
In a specific embodiment of the application, a scheduling server receives a live broadcast request of a target anchor A, and obtains attribute information of the target anchor according to the live broadcast request, wherein the anchor attribute information comprises an anchor ID, historical live broadcast duration, historical live broadcast viewing information and anchor fan number.
Step 204: and determining push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for determining a live stream processing strategy by an anchor client of the target anchor, and the push stream mode information comprises a delay push mode and a normal push mode.
Determining the stream pushing mode information according to the anchor attribute information can be understood as determining the stream pushing mode of the anchor live broadcast according to the anchor attribute information. In practical application, the stream pushing mode of the live broadcast at this time is judged according to the historical live broadcast duration of the anchor, the number of watching people and the number of fan of the anchor, for example, if the total number of people watching within 10 hours of the recent live broadcast of the anchor is less than 10 people and the number of fan is less than 20 people, the probability that the live broadcast at this time of the anchor is not watched by users is considered, delayed push information is sent to the anchor client corresponding to the live broadcast, and conversely, normal push information is sent to the anchor client.
In practical applications, the scheduling server may also obtain data related to the anchor in an anchor database according to the anchor ID, for example, the number of viewers in a live broadcast on the anchor, and the resource such as income information.
In a specific embodiment of the present application, the above example is used, and according to the anchor attribute information of the target anchor a: and if the historical live broadcast time is 100 hours, the total number of the viewers is 20 and the number of the anchor fans is 10, determining that the push stream mode information corresponding to the target anchor A is delayed push.
Specifically, determining the push stream mode information according to the anchor attribute information includes:
acquiring anchor identification information in the anchor attribute information;
acquiring historical live broadcast data corresponding to the target anchor according to the anchor identification information;
and determining push stream mode information according to the historical live broadcast data and the anchor attribute information.
The live broadcast identification information can be understood as the only identification information of the anchor, the historical live broadcast data corresponding to the anchor can be obtained according to the anchor identification information, and the corresponding stream pushing mode information is determined according to the historical live broadcast data and the anchor attribute information.
In practical application, the live broadcast request may only carry a broadcast request and anchor broadcast identification information, and at this time, the scheduling server may obtain corresponding historical live broadcast data from an anchor broadcast database according to the anchor broadcast identification information, where the historical live broadcast data may be historical watching people, historical live broadcast interaction information, and the like, and the scheduling server may determine push stream mode information according to the historical live broadcast data and the anchor broadcast attribute information.
In a specific embodiment of the application, along the above example, the scheduling server obtains anchor identification information in the anchor attribute information, obtains historical live broadcast data corresponding to the target anchor a from an anchor database according to the anchor identification information, where the historical live broadcast data is historical watching number, historical live broadcast duration, and last live broadcast income information, and determines that the push streaming mode information is delayed push according to the historical live broadcast data and the anchor attribute information.
Further, after acquiring the historical live broadcast data and the anchor attribute information, the scheduling server may calculate live broadcast score information of the target anchor according to the historical live broadcast data and the anchor attribute information, and determine whether a user watches the live broadcast according to the live broadcast score information, specifically, determine streaming mode information according to the historical live broadcast data and the anchor attribute information, including:
calculating live broadcast grading information corresponding to the target anchor according to the historical live broadcast data and the live broadcast attribute information;
determining that the push mode information corresponding to the target anchor is a delayed push mode under the condition that the live broadcast grading information is smaller than a preset push flow threshold value;
and determining that the push mode information corresponding to the target anchor is a normal push mode under the condition that the live broadcast grading information is greater than or equal to a preset push flow threshold value.
The live broadcast scoring information can be understood as scoring information for predicting whether the live broadcast is watched by people, whether the live broadcast is watched by people can be accurately predicted according to the live broadcast scoring information, and for example, if the live broadcast scoring information for the live broadcast is calculated to be lower than a preset threshold value, it is indicated that the live broadcast is not watched by people. The preset push stream threshold value can be understood as a preset live stream pushing threshold value, when the live broadcast grading information of the current live broadcast is lower than the preset push stream threshold value, the fact that the current live broadcast has a large probability of being watched by no people is represented, and the corresponding push mode information can be set to be a delayed push mode, so that the bandwidth cost of a live broadcast platform is saved; when the score information of the live broadcast is equal to or higher than the preset push flow threshold value, the fact that someone watches the live broadcast is represented, and the corresponding push mode information can be set to be a normal push mode, so that the normal live broadcast of the anchor broadcast and the normal watching of a user are guaranteed.
In practical application, the live broadcast scoring threshold of some anchor broadcasts with high popularity and long live broadcast time is generally higher than the preset push stream threshold, so that the process of calculating the live broadcast scoring information can be omitted, and the push stream mode information corresponding to the anchor broadcasts is directly set to be a normal push mode; for some anchor broadcasters with low popularity and live broadcast time periods, if no user watches the anchor broadcasters probably, the live broadcast scoring information of the anchor broadcasters can be calculated, the anchor broadcasters with high probability that no user watches the live broadcast can be screened out, and the push mode information is set to be the delayed push stream mode. It should be noted that, the judgment of whether the live broadcast of the anchor is watched by someone is only one of various prediction methods by calculating the live broadcast score information, prediction can be performed by an AI model in practical application, and the specific prediction mode can be determined according to actual conditions.
In a specific embodiment of the present application, the above example is used, live broadcast score information of the target anchor a is calculated to be 50 minutes according to the historical live broadcast data and the anchor attribute information corresponding to the target anchor a, and if the score information is smaller than a preset push stream threshold value of 60 minutes, it indicates that the current live broadcast of the target anchor a is not watched by anyone, and then push stream mode information corresponding to the target anchor a is set as delayed push stream information.
Step 206: and sending the push stream mode information to the anchor client.
In practical application, after the stream pushing mode information is determined, the scheduling server sends the stream pushing mode information to an anchor client corresponding to an anchor.
In a specific embodiment of the present application, following the above example, the scheduling server sends the push mode information to the anchor client corresponding to the target anchor a.
In addition, in the delayed push mode of the anchor client, the scheduling server may receive live heartbeat information sent by the anchor client, and the scheduling server may display live information corresponding to the anchor to a user according to the live heartbeat information, specifically, the method further includes:
receiving live broadcast heartbeat information sent by the anchor client;
generating live broadcast recommendation information according to the live broadcast heartbeat information;
and pushing the live broadcast recommendation information to a user client.
The live broadcasting recommendation information can be understood as information recommending a live broadcasting room, and a user can roughly know live broadcasting content after browsing the live broadcasting recommendation information.
In practical application, live broadcast heartbeat information comprises a live broadcast picture, a live broadcast title, anchor personal information and the like of a current anchor, a scheduling server can generate corresponding live broadcast recommendation information according to the live broadcast heartbeat information, the live broadcast recommendation information is displayed on a live broadcast platform or directly pushed to a user client side which is likely to watch live broadcast, and therefore the live broadcast recommendation information is used for pulling a user to watch in a live broadcast room, and popularity of the live broadcast room is improved.
In a specific embodiment of the present application, following the above example, the scheduling server, according to the live heartbeat information sent by the anchor client: current live broadcast picture, live broadcast room title: the method comprises the steps of 'new people take a lead and welcome', generating live broadcast recommendation information, wherein the live broadcast recommendation information is a preview live broadcast room picture, pushing the preview live broadcast room picture to a plurality of user clients which are likely to watch, and displaying the preview live broadcast room picture in a live broadcast platform.
Specifically, the live heartbeat information includes live screenshot information;
generating live broadcast recommendation information according to the live broadcast heartbeat information, wherein the live broadcast recommendation information comprises:
acquiring live screenshot information in the live heartbeat information;
and under the condition that the live screenshot information passes the audit, generating live recommendation information according to the live screenshot information.
The live screenshot information in the live heartbeat information is a live frame of the current anchor broadcast, the scheduling server can judge whether live content of the anchor broadcast is illegal according to the live screenshot information, under the condition that the live content of the anchor broadcast is illegal, the live content is not pushed, a corresponding live broadcast room is closed, and if the live content is not illegal, live broadcast recommendation information is generated according to the live screenshot information.
In a specific embodiment of the application, following the above example, the scheduling server performs content auditing for the live broadcast room according to live screenshot information in live heartbeat information, and only when the auditing is passed, live recommendation information is generated according to the live screenshot information and anchor attribute information.
Correspondingly, after a user enters a live broadcast room to watch, the scheduling server receives a live broadcast watching request sent by the user, and specifically, the method further includes:
receiving a live viewing request for the target anchor;
generating a live stream pushing instruction according to the live viewing request, and sending the live stream pushing instruction to the anchor client;
and switching the stream pushing mode information corresponding to the target anchor to a normal stream pushing mode.
The live broadcast watching request can be understood as a request of a user for watching a live broadcast room, and according to the live broadcast watching request, the scheduling server can generate a live broadcast stream pushing instruction to the anchor client if the current live broadcast room needs to be pushed.
In practical application, when audience watches in a delayed push live broadcast room, the scheduling server sends a live broadcast stream push instruction to an anchor client corresponding to the live broadcast room, so that the anchor client pushes a live broadcast stream to the push stream node server, a user can normally watch the live broadcast, and push mode information corresponding to the anchor broadcast is switched to a normal push stream mode, so that other subsequent users can quickly watch the live broadcast when entering the live broadcast room, and the watching delay caused by waiting for the anchor client to push the stream again in the delayed push mode is avoided.
In a specific embodiment of the present application, following the above example, the scheduling server receives a live viewing request of the user C for the target anchor a, and the scheduling server generates a live stream push instruction according to the live viewing request, and sends the live stream push instruction to the anchor client of the target anchor a, so that the anchor client can push the live stream to the corresponding streaming node server, and switch the delayed push mode of the target anchor a to the normal push mode.
The application provides a live broadcast pushing method applied to a scheduling server, which comprises the following steps: receiving a live broadcast request of a target anchor, and acquiring anchor attribute information of the target anchor according to the live broadcast request; determining push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for determining a live stream processing strategy by an anchor client of the target anchor, and the push stream mode information comprises a delay push mode and a normal push mode; and sending the push stream mode information to the anchor client. Through predicting to anchor historical live broadcast data, judge whether this live broadcast of anchor has someone watched, under the condition that the general probability is unmanned, send and delay the propelling movement mode information for the anchor client that this anchor corresponds, reach the purpose of saving the upstream bandwidth with this, and through receiving the live broadcast heartbeat information that the anchor client sent, make the live broadcast room that this anchor corresponds still can demonstrate in live broadcast platform, make the user can browse this live broadcast room in live broadcast platform, reached on the basis that does not influence the live broadcast of anchor, reduce the purpose of live broadcast platform cost.
Fig. 3 is a flowchart illustrating a live push method applied to a live scheduling system according to an embodiment of the present application, where the live scheduling system includes an anchor client and a scheduling server, where,
step 302: the method comprises the steps that a scheduling server receives a live broadcast request of a target anchor, acquires anchor attribute information of the target anchor according to the live broadcast request, and determines push flow mode information according to the anchor attribute information, wherein the push flow mode information is used for an anchor client of the target anchor to determine a live broadcast flow processing strategy, the push flow mode information comprises a delay push mode and a normal push mode, and the push flow mode information is sent to the anchor client.
In a specific embodiment of the application, a scheduling server receives a live broadcast request of a target anchor a, the scheduling server obtains anchor attribute information of the target anchor a according to the live broadcast request, the anchor attribute information is 50 of the total number of historical watching persons, the duration of the historical live broadcast is 100 hours, and the number of anchor fans is 10, the scheduling server judges that the current live broadcast of the anchor is not watched by any person at a high probability by calculating live broadcast score information of the target anchor a, determines that push streaming mode information is a delayed push mode, and sends the delayed push information to an anchor client of the target anchor a.
Step 304: the anchor client sends a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
In a specific embodiment of the present application, following the above example, the anchor client of the target anchor a sends a live broadcast request to the scheduling server according to the received live broadcast instruction, receives stream push mode information returned by the scheduling server based on the live broadcast request, determines that the live broadcast stream processing policy is a delayed stream push, and does not push the live broadcast stream to the stream push node server based on the delayed stream push policy.
The live broadcast pushing method applied to the live broadcast scheduling system comprises an anchor client and a scheduling server, wherein the scheduling server receives a live broadcast request of a target anchor, acquires anchor attribute information of the target anchor according to the live broadcast request, and determines push flow mode information according to the anchor attribute information, wherein the push flow mode information is used for the anchor client of the target anchor to determine a live broadcast flow processing strategy, the push flow mode information comprises a delay push mode and a normal push mode, and the push flow mode information is sent to the anchor client; the anchor client sends a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy. A delayed push mode is set for the live broadcast room which is watched by no one through the scheduling server, so that the corresponding anchor client does not push the live broadcast stream to the stream pushing node server, the uplink bandwidth is saved, and the cost of a live broadcast platform is reduced.
The following describes the live broadcast push method further by taking an application of the live broadcast push method provided in the present application in delayed push streaming as an example, with reference to fig. 4. Fig. 4 shows a processing flow chart of a live broadcast push method applied to delayed push streaming according to an embodiment of the present application, which specifically includes the following steps:
step 402: and sending a live broadcast request to a scheduling server according to the received live broadcast instruction.
In a specific embodiment of the application, the anchor client determines that the current anchor a is ready to start live broadcast according to a received live broadcast instruction, and sends a live broadcast request to the scheduling server, wherein the live broadcast request carries an anchor ID and live broadcast title information of the anchor a.
Step 404: and receiving the push stream mode information returned by the scheduling server in response to the live broadcast request.
In a specific embodiment of the present application, following the above example, the anchor client receives push stream mode information returned by the scheduling server in response to the live broadcast request, where the push stream mode information is a delayed push stream.
Step 406: and determining a live stream processing strategy according to the stream pushing mode information.
In a specific embodiment of the present application, following the above example, if the anchor client determines that the live broadcast processing strategy is delayed push according to the push stream mode information, the anchor client does not push the live broadcast stream to the push stream node server.
Step 408: and under the condition that the live stream processing strategy is delayed push, generating live heartbeat information according to the live stream corresponding to the live request, and sending the live heartbeat information to the scheduling server.
In a specific embodiment of the present application, the above example is continued, and when it is determined that the live stream processing policy is delayed push, the anchor client generates live heartbeat information according to the live request and the corresponding live stream, where the live heartbeat information includes a current live frame of the anchor, and sends the live heartbeat information to the scheduling server.
Step 410: and receiving a stream pushing instruction aiming at the live stream, and sending the live stream to a target server in response to the stream pushing instruction.
In a specific embodiment of the present application, following the above example, the anchor client receives a stream pushing instruction for a live stream of a current live broadcast room, and sends the live stream to a target stream pushing node server in response to the stream pushing instruction.
The application provides a live broadcast push method applied to delayed push stream, which comprises the following steps: sending a live broadcast request to a scheduling server according to a received live broadcast instruction, receiving push stream mode information returned by the scheduling server in response to the live broadcast request, determining a live broadcast stream processing strategy according to the push stream mode information, generating live broadcast heartbeat information according to a live broadcast stream corresponding to the live broadcast request under the condition that the live broadcast stream processing strategy is delayed push, sending the live broadcast heartbeat information to the scheduling server, receiving a push stream instruction aiming at the live broadcast stream, and sending the live broadcast stream to a target server in response to the push stream instruction. By setting a delayed push mode for the live broadcast room which is watched without people, when the live broadcast room is broadcasted, the live broadcast stream corresponding to the live broadcast stream is not pushed to the push node server, and when a user enters the live broadcast room, the live broadcast stream is pushed to the push node server, so that the uplink bandwidths of the scheduling server and the push node server are reduced, and the live broadcast cost of a live broadcast platform is reduced.
Corresponding to the above method embodiment, the present application further provides an embodiment of a live push device applied to a anchor client, and fig. 5 shows a schematic structural diagram of a live push device applied to an anchor client provided in an embodiment of the present application. As shown in fig. 5, the apparatus includes:
a sending module 502 configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction;
a receiving module 504 configured to receive push stream mode information returned by the scheduling server in response to the live broadcast request, wherein the push stream mode information includes a delayed push mode and a normal push mode;
a determining module 506 configured to determine a live stream processing policy according to the stream pushing mode information;
a processing module 508 configured to process a live stream corresponding to the live request based on the live stream processing policy.
Accordingly, the processing module 508 is further configured to:
under the condition that the live stream processing strategy is delayed push, generating live heartbeat information according to a live stream corresponding to the live request, wherein the live heartbeat information comprises live screenshot information;
and sending the live heartbeat information to the scheduling server.
Accordingly, the processing module 508 is further configured to:
generating live broadcast state information according to a live broadcast stream corresponding to the live broadcast request, and acquiring live broadcast screenshot information corresponding to the live broadcast stream;
and generating live heartbeat information according to the live state information and the live screenshot information.
Further, the processing module 508 is further configured to:
receiving a stream pushing instruction aiming at the live stream;
and responding to the stream pushing instruction, and sending the live stream to a target server.
Further, the processing module 508 is further configured to:
acquiring a target server identifier in the stream pushing instruction;
determining a target server according to the target server identification;
and sending the live stream to the target server.
Accordingly, the sending module 502 is further configured to:
generating a live broadcast request according to a received live broadcast instruction;
and sending the live broadcast request to a scheduling server.
Accordingly, the processing module 508 is further configured to:
and under the condition that the stream pushing mode information is normally pushed, pushing the live stream corresponding to the live request to a target server.
The application provides a live pusher for anchor customer end, includes: the sending module is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction; a receiving module configured to receive push stream mode information returned by the scheduling server in response to the live broadcast request, wherein the push stream mode information includes a delayed push mode and a normal push mode; a determining module configured to determine a live stream processing policy according to the stream pushing mode information; and the processing module is configured to process the live stream corresponding to the live stream request based on the live stream processing strategy. The live stream pushing strategy is determined by enabling the anchor client to obtain the own push stream mode, the live stream is processed according to the live stream pushing strategy, under the condition that the push stream mode of the anchor corresponding to the live room is the delayed push stream mode, the anchor client does not push the live stream to the push stream node server, but collects relevant live stream information and sends the relevant live stream information to the scheduling server, when audience watching really exists, the live stream is pushed to the push stream node server, most of the anchor which is not watched by the user does not occupy uplink bandwidth resources any more, and the bandwidth cost of a live platform is saved.
Corresponding to the foregoing method embodiment, the present application further provides an embodiment of a live broadcast push device applied to a scheduling server, and fig. 6 illustrates a schematic structural diagram of a live broadcast push device applied to a scheduling server provided in an embodiment of the present application. As shown in fig. 6, the apparatus includes:
an obtaining module 602, configured to receive a live request of a target anchor, and obtain anchor attribute information of the target anchor according to the live request;
a determining module 604, configured to determine push stream mode information according to the anchor attribute information, where the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing policy, and the push stream mode information includes a delayed push mode and a normal push mode;
a sending module 606 configured to send the push stream mode information to the anchor client.
Accordingly, the determination module 604 is further configured to:
acquiring anchor identification information in the anchor attribute information;
acquiring historical live broadcast data corresponding to the target anchor according to the anchor identification information;
and determining push stream mode information according to the historical live broadcast data and the anchor attribute information.
Accordingly, the determination module 604 is further configured to:
calculating live broadcast grading information corresponding to the target anchor according to the historical live broadcast data and the live broadcast attribute information;
determining that the push mode information corresponding to the target anchor is a delayed push mode under the condition that the live broadcast grading information is less than or equal to a preset push flow threshold value;
and under the condition that the live broadcast grading information is larger than a preset push flow threshold value, determining that the push mode information corresponding to the target anchor is a normal push mode.
The apparatus further comprises a push module configured to:
receiving live broadcast heartbeat information sent by the anchor client;
generating live broadcast recommendation information according to the live broadcast heartbeat information;
and pushing the live broadcast recommendation information to a user client.
Accordingly, the push module is further configured to:
acquiring live screenshot information in the live heartbeat information;
and under the condition that the live screenshot information passes the audit, generating live recommendation information according to the live screenshot information.
Further, the apparatus further comprises: a transmission submodule configured to:
receiving a live viewing request for the target anchor;
generating a live stream pushing instruction according to the live viewing request, and sending the live stream pushing instruction to the anchor client;
and switching the stream pushing mode information corresponding to the target anchor to a normal stream pushing mode.
The application provides a live broadcast pusher applied to scheduling server, include: the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is configured to receive a live broadcast request of a target anchor and acquire anchor attribute information of the target anchor according to the live broadcast request; a determining module configured to determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing policy, and the push stream mode information includes a delayed push mode and a normal push mode; a sending module configured to send the push stream mode information to the anchor client. Through predicting to anchor historical live broadcast data, judge whether this live broadcast of anchor has someone watched, under the condition that the general probability is unmanned, send and delay the propelling movement mode information for the anchor client that this anchor corresponds, reach the purpose of saving the upstream bandwidth with this, and through receiving the live broadcast heartbeat information that the anchor client sent, make the live broadcast room that this anchor corresponds still can demonstrate in live broadcast platform, make the user can browse this live broadcast room in live broadcast platform, reached on the basis that does not influence the live broadcast of anchor, reduce the purpose of live broadcast platform cost.
Corresponding to the above method embodiment, the present application further provides a live broadcast push system embodiment, and fig. 7 shows a schematic structural diagram of a live broadcast push system provided in an embodiment of the present application. As shown in fig. 7, the system includes: dispatch server 702, anchor client 704, where,
the scheduling server 702 is configured to receive a live broadcast request of a target anchor, obtain anchor attribute information of the target anchor according to the live broadcast request, and determine push stream mode information according to the anchor attribute information, where the push stream mode information is used by an anchor client of the target anchor to determine a live stream processing policy, the push stream mode information includes a delayed push mode and a normal push mode, and the push stream mode information is sent to the anchor client;
the anchor client 704 is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live stream processing strategy according to the stream pushing mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
The system comprises an anchor client and a scheduling server, wherein the scheduling server is configured to receive a live request of a target anchor, acquire anchor attribute information of the target anchor according to the live request, and determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for the anchor client of the target anchor to determine a live stream processing strategy, the push stream mode information comprises a delay push mode and a normal push mode, and the push stream mode information is sent to the anchor client; the anchor client is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy. By setting a delayed push mode for the live broadcast room which is watched without people, when the live broadcast room is broadcasted, the live broadcast stream corresponding to the live broadcast stream is not pushed to the push node server, and when a user enters the live broadcast room, the live broadcast stream is pushed to the push node server, so that the uplink bandwidths of the scheduling server and the push node server are reduced, and the live broadcast cost of a live broadcast platform is reduced.
The above is a schematic scheme of the live broadcast push apparatus of the present embodiment. It should be noted that the technical solution of the live broadcast push device and the technical solution of the live broadcast push method belong to the same concept, and details that are not described in detail in the technical solution of the live broadcast push device can be referred to in the description of the technical solution of the live broadcast push method.
Fig. 8 illustrates a block diagram of a computing device 800 provided according to an embodiment of the present application. The components of the computing device 800 include, but are not limited to, memory 810 and a processor 820. The processor 820 is coupled to the memory 810 via a bus 830, and the database 850 is used to store data.
Computing device 800 also includes access device 840, access device 840 enabling computing device 800 to communicate via one or more networks 860. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 840 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the application, the above-described components of the computing device 800 and other components not shown in fig. 8 may also be connected to each other, for example, by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 8 is for purposes of example only and is not limiting as to the scope of the present application. Those skilled in the art may add or replace other components as desired.
Computing device 800 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), a mobile phone (e.g., smartphone), a wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 800 may also be a mobile or stationary server.
Wherein, the steps of the live push method are implemented when the processor 820 executes the computer instructions.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the live broadcast push method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can all be referred to in the description of the technical solution of the live broadcast push method.
An embodiment of the present application further provides a computer readable storage medium, which stores computer instructions, and when executed by a processor, the computer instructions implement the steps of the live broadcast push method as described above.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the live broadcast push method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the live broadcast push method.
The foregoing description of specific embodiments of the present application has been presented. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art will appreciate that the embodiments described in this specification are presently considered to be preferred embodiments and that acts and modules are not required in the present application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present application disclosed above are intended only to aid in the explanation of the application. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the application and its practical applications, to thereby enable others skilled in the art to best understand and utilize the application. The application is limited only by the claims and their full scope and equivalents.

Claims (19)

1. A live broadcast pushing method is applied to a scheduling server and comprises the following steps:
receiving a live broadcast request of a target anchor, and acquiring anchor attribute information of the target anchor according to the live broadcast request;
determining push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for determining a live stream processing strategy by an anchor client of the target anchor, and the push stream mode information comprises a delay push mode and a normal push mode;
and sending the push stream mode information to the anchor client.
2. The method of claim 1, wherein determining push stream mode information based on the anchor attribute information comprises:
acquiring anchor identification information in the anchor attribute information;
acquiring historical live broadcast data corresponding to the target anchor according to the anchor identification information;
and determining push stream mode information according to the historical live broadcast data and the anchor attribute information.
3. The method of claim 2, wherein determining push streaming mode information based on the historical live data and the anchor attribute information comprises:
calculating live broadcast grading information corresponding to the target anchor according to the historical live broadcast data and the live broadcast attribute information;
determining that the push mode information corresponding to the target anchor is a delayed push mode under the condition that the live broadcast grading information is smaller than a preset push flow threshold value;
and determining that the push mode information corresponding to the target anchor is a normal push mode under the condition that the live broadcast grading information is greater than or equal to a preset push flow threshold value.
4. The method of claim 1, wherein the method further comprises:
receiving live broadcast heartbeat information sent by the anchor client;
generating live broadcast recommendation information according to the live broadcast heartbeat information;
and pushing the live broadcast recommendation information to a user client.
5. The method of claim 4, wherein the live heartbeat information includes live screenshot information;
generating live broadcast recommendation information according to the live broadcast heartbeat information, wherein the live broadcast recommendation information comprises:
acquiring live screenshot information in the live heartbeat information;
and under the condition that the live screenshot information passes the audit, generating live recommendation information according to the live screenshot information.
6. The method of claim 1, wherein the method further comprises:
receiving a live viewing request for the target anchor;
generating a live stream pushing instruction according to the live viewing request, and sending the live stream pushing instruction to the anchor client;
and switching the stream pushing mode information corresponding to the target anchor to a normal stream pushing mode.
7. A live broadcast pushing method is applied to a main broadcast client and comprises the following steps:
sending a live broadcast request to a scheduling server according to a received live broadcast instruction;
receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode;
determining a live streaming processing strategy according to the push streaming mode information;
and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
8. The method of claim 7, wherein processing the live stream corresponding to the live request based on the live stream processing policy comprises:
under the condition that the live stream processing strategy is delayed push, generating live heartbeat information according to a live stream corresponding to the live request, wherein the live heartbeat information comprises live screenshot information;
and sending the live heartbeat information to the scheduling server.
9. The method of claim 8, wherein generating live heartbeat information from a live stream corresponding to the live request comprises:
generating live broadcast state information according to a live broadcast stream corresponding to the live broadcast request, and acquiring live broadcast screenshot information corresponding to the live broadcast stream;
and generating live heartbeat information according to the live status information and the live screenshot information.
10. The method of claim 8, wherein after generating live heartbeat information according to a live stream corresponding to the live request, further comprising:
receiving a stream pushing instruction aiming at the live stream;
and responding to the stream pushing instruction, and sending the live stream to a target server.
11. The method of claim 10, wherein sending the live stream to a target server in response to the streaming instructions comprises:
acquiring a target server identifier in the stream pushing instruction;
determining a target server according to the target server identification;
and sending the live stream to the target server.
12. The method of claim 7, wherein sending a live request to a scheduling server in response to receiving a live command comprises:
generating a live broadcast request according to a received live broadcast instruction;
and sending the live broadcast request to a scheduling server.
13. The method of claim 7, wherein processing the live stream corresponding to the live request based on the live stream processing policy comprises:
and under the condition that the stream pushing mode information is normally pushed, pushing the live stream corresponding to the live request to a target server.
14. A live broadcast pushing method is applied to a live broadcast scheduling system, the live broadcast scheduling system comprises a main broadcast client and a scheduling server, wherein,
the scheduling server receives a live broadcast request of a target anchor, acquires anchor attribute information of the target anchor according to the live broadcast request, and determines push flow mode information according to the anchor attribute information, wherein the push flow mode information is used for an anchor client of the target anchor to determine a live broadcast flow processing strategy, the push flow mode information comprises a delayed push mode and a normal push mode, and the push flow mode information is sent to the anchor client;
the anchor client sends a live broadcast request to a scheduling server according to a received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live streaming processing strategy according to the push streaming mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
15. A live broadcast pushing device is applied to a main broadcast client, and comprises:
the sending module is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction;
a receiving module configured to receive push stream mode information returned by the scheduling server in response to the live broadcast request, wherein the push stream mode information includes a delayed push mode and a normal push mode;
a determining module configured to determine a live stream processing policy according to the stream pushing mode information;
and the processing module is configured to process the live stream corresponding to the live stream request based on the live stream processing strategy.
16. A live broadcast push device is applied to a scheduling server and comprises:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is configured to receive a live broadcast request of a target anchor and acquire anchor attribute information of the target anchor according to the live broadcast request;
a determining module configured to determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing policy, and the push stream mode information includes a delayed push mode and a normal push mode;
a sending module configured to send the push stream mode information to the anchor client.
17. A live broadcast push system is characterized in that the system comprises a main broadcast client and a scheduling server, wherein,
the scheduling server is configured to receive a live broadcast request of a target anchor, acquire anchor attribute information of the target anchor according to the live broadcast request, and determine push stream mode information according to the anchor attribute information, wherein the push stream mode information is used for an anchor client of the target anchor to determine a live stream processing strategy, the push stream mode information comprises a delayed push mode and a normal push mode, and the push stream mode information is sent to the anchor client;
the anchor client is configured to send a live broadcast request to the scheduling server according to the received live broadcast instruction; receiving push flow mode information returned by the scheduling server in response to the live broadcast request, wherein the push flow mode information comprises a delay push mode and a normal push mode; determining a live stream processing strategy according to the stream pushing mode information; and processing the live stream corresponding to the live stream request based on the live stream processing strategy.
18. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any one of claims 1-6 or 7-13 when executing the computer instructions.
19. A computer-readable storage medium storing computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1-6 or 7-13.
CN202210295037.6A 2022-03-24 2022-03-24 Live broadcast pushing method and device Active CN114679598B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210295037.6A CN114679598B (en) 2022-03-24 2022-03-24 Live broadcast pushing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210295037.6A CN114679598B (en) 2022-03-24 2022-03-24 Live broadcast pushing method and device

Publications (2)

Publication Number Publication Date
CN114679598A true CN114679598A (en) 2022-06-28
CN114679598B CN114679598B (en) 2023-11-21

Family

ID=82074902

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210295037.6A Active CN114679598B (en) 2022-03-24 2022-03-24 Live broadcast pushing method and device

Country Status (1)

Country Link
CN (1) CN114679598B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116567356A (en) * 2023-06-07 2023-08-08 佛山市炫新智能科技有限公司 Live broadcast display system based on multi-platform push stream and push method thereof

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106254311A (en) * 2016-07-15 2016-12-21 腾讯科技(深圳)有限公司 Live broadcasting method and device, live data streams methods of exhibiting and device
CN106603503A (en) * 2016-11-22 2017-04-26 腾讯科技(深圳)有限公司 Live streaming data processing method and device
CN107318044A (en) * 2017-06-30 2017-11-03 武汉斗鱼网络科技有限公司 A kind of live content intercept method and system
CN109068157A (en) * 2018-08-21 2018-12-21 北京潘达互娱科技有限公司 Method of adjustment, device and the server of plug-flow parameter in a kind of live streaming
CN110213330A (en) * 2019-04-28 2019-09-06 北京奇艺世纪科技有限公司 Pre- supplying system, method, apparatus, electronic equipment and computer-readable medium
CN110602518A (en) * 2019-09-18 2019-12-20 广州虎牙科技有限公司 Live broadcast recommendation method and device, electronic equipment and readable storage medium
CN110753237A (en) * 2019-11-05 2020-02-04 北京金和网络股份有限公司 Method and device for saving upstream bandwidth flow of streaming media server
CN110944217A (en) * 2019-12-12 2020-03-31 北京达佳互联信息技术有限公司 Live broadcast information processing method and device, server and storage medium
CN110996109A (en) * 2019-11-21 2020-04-10 北京达佳互联信息技术有限公司 Abnormal live broadcast room cleaning method and device, live broadcast server and storage medium
CN111355970A (en) * 2019-05-15 2020-06-30 深圳市鸿合创新信息技术有限责任公司 Live broadcast management method and device and electronic equipment
CN112532946A (en) * 2020-12-03 2021-03-19 南京智慧交通信息股份有限公司 Multi-protocol-based stream media system design method
CN112788357A (en) * 2020-12-30 2021-05-11 北京达佳互联信息技术有限公司 Network live broadcast method, device, server and computer readable storage medium
CN113556572A (en) * 2021-07-21 2021-10-26 云南腾云信息产业有限公司 Live broadcast starting method and device and electronic equipment
CN114070852A (en) * 2021-11-15 2022-02-18 上海哔哩哔哩科技有限公司 Live broadcast delay optimization method and device

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106254311A (en) * 2016-07-15 2016-12-21 腾讯科技(深圳)有限公司 Live broadcasting method and device, live data streams methods of exhibiting and device
CN106603503A (en) * 2016-11-22 2017-04-26 腾讯科技(深圳)有限公司 Live streaming data processing method and device
CN107318044A (en) * 2017-06-30 2017-11-03 武汉斗鱼网络科技有限公司 A kind of live content intercept method and system
CN109068157A (en) * 2018-08-21 2018-12-21 北京潘达互娱科技有限公司 Method of adjustment, device and the server of plug-flow parameter in a kind of live streaming
CN110213330A (en) * 2019-04-28 2019-09-06 北京奇艺世纪科技有限公司 Pre- supplying system, method, apparatus, electronic equipment and computer-readable medium
CN111355970A (en) * 2019-05-15 2020-06-30 深圳市鸿合创新信息技术有限责任公司 Live broadcast management method and device and electronic equipment
CN110602518A (en) * 2019-09-18 2019-12-20 广州虎牙科技有限公司 Live broadcast recommendation method and device, electronic equipment and readable storage medium
CN110753237A (en) * 2019-11-05 2020-02-04 北京金和网络股份有限公司 Method and device for saving upstream bandwidth flow of streaming media server
CN110996109A (en) * 2019-11-21 2020-04-10 北京达佳互联信息技术有限公司 Abnormal live broadcast room cleaning method and device, live broadcast server and storage medium
CN110944217A (en) * 2019-12-12 2020-03-31 北京达佳互联信息技术有限公司 Live broadcast information processing method and device, server and storage medium
CN112532946A (en) * 2020-12-03 2021-03-19 南京智慧交通信息股份有限公司 Multi-protocol-based stream media system design method
CN112788357A (en) * 2020-12-30 2021-05-11 北京达佳互联信息技术有限公司 Network live broadcast method, device, server and computer readable storage medium
CN113556572A (en) * 2021-07-21 2021-10-26 云南腾云信息产业有限公司 Live broadcast starting method and device and electronic equipment
CN114070852A (en) * 2021-11-15 2022-02-18 上海哔哩哔哩科技有限公司 Live broadcast delay optimization method and device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116567356A (en) * 2023-06-07 2023-08-08 佛山市炫新智能科技有限公司 Live broadcast display system based on multi-platform push stream and push method thereof

Also Published As

Publication number Publication date
CN114679598B (en) 2023-11-21

Similar Documents

Publication Publication Date Title
US20110184899A1 (en) Method and system for generating recommendations of content items
WO2011146898A2 (en) Internet system for ultra high video quality
US11259063B2 (en) Method and system for setting video cover
US20210368214A1 (en) Method and mobile terminal for processing data
US20160140618A1 (en) Targeting ads engaged by a user to related users
CN112752113B (en) Method and device for determining abnormal factors of live broadcast server
CN113055692A (en) Data processing method and device
CN114466216B (en) Live broadcast room display method, server side and live broadcast client side
CN105898395A (en) Network video playing method, device and system
CN113141522B (en) Resource transmission method, device, computer equipment and storage medium
CN113891175B (en) Live broadcast push flow method, device and system
CN113676754A (en) Live video transcoding method and device
US9338508B2 (en) Preserving a consumption context for a user session
CN114363703B (en) Video processing method, device and system
CN114679598A (en) Live broadcast pushing method and device
CN114173160B (en) Live broadcast push flow method and device
WO2015035934A1 (en) Methods and systems for facilitating video preview sessions
CN110784731B (en) Data stream transcoding method, device, equipment and medium
CN104901939A (en) Multimedia file play method, terminal and server
US20230179542A1 (en) Predictive network capacity scaling based on customer interest
CN111698261A (en) Video playing method, device, equipment and storage medium based on streaming media
CN114501053B (en) Live stream acquisition method and device
CN114363651B (en) Live stream processing method and device
CN115942007A (en) Live streaming scheduling method and device
JP2015027044A (en) Information processor, information processing method and program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant