CN114885219B - Task execution state monitoring method and device, electronic equipment and storage medium - Google Patents
Task execution state monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114885219B CN114885219B CN202210481036.0A CN202210481036A CN114885219B CN 114885219 B CN114885219 B CN 114885219B CN 202210481036 A CN202210481036 A CN 202210481036A CN 114885219 B CN114885219 B CN 114885219B
- Authority
- CN
- China
- Prior art keywords
- target
- user account
- time period
- task
- heartbeat message
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
- H04N21/2408—Monitoring of the upstream path of the transmission network, e.g. client requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64784—Data processing by the network
- H04N21/64792—Controlling the complexity of the content stream, e.g. by dropping packets
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a task execution state monitoring method, a device, an electronic device and a storage medium, wherein the method comprises the following steps: determining at least one target user account in at least two user accounts entering a target virtual space; the target user account is a user account associated with a target task issued by the target virtual space; receiving a heartbeat message sent by a client side where a target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client; storing a piece of heartbeat messages received in each second time period respectively in the process of executing the target task by the target user account; determining the actual state of the target user account for executing the target task according to the stored heartbeat message and the period length of the second time period; the period length of the second time period is greater than the period length of the first time period. By adopting the method and the device, the task execution state can be effectively monitored while the data traffic is reduced.
Description
Technical Field
The disclosure relates to the technical field of internet, and in particular relates to a task execution state monitoring method, a device, electronic equipment and a storage medium.
Background
With the continuous development of internet technology, more and more people enrich their amateur lives by watching live contents of a live broadcasting room and executing tasks issued by the live broadcasting room.
However, during a live broadcast peak period, millions of audience accounts usually watch live broadcast and execute tasks issued by a live broadcast room, and when monitoring task execution states, the conventional technology often needs to process millions of message events, which also causes a background server to bear huge data storage pressure, and meanwhile, needs to consume a large amount of data traffic to forward stored messages, so that the operation cost of the background server is not reduced.
However, the conventional method has a problem in that a large amount of data traffic is consumed for the server to monitor the task execution state.
Disclosure of Invention
The disclosure provides a task execution state monitoring method, a device, an electronic device and a storage medium, so as to at least solve the problem that a large amount of data traffic is required to be consumed for monitoring the task execution state in the related art. The technical scheme of the present disclosure is as follows:
According to a first aspect of an embodiment of the present disclosure, there is provided a task execution state monitoring method, including:
determining at least one target user account in at least two user accounts entering a target virtual space; the target user account is a user account associated with a target task issued by the target virtual space;
receiving a heartbeat message sent by a client side where the target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client;
storing a heartbeat message received in each second time period during the process of executing the target task by the target user account;
determining an actual state of the target user account for executing the target task according to the stored heartbeat message and the period length of the second time period; the period length of the second time period is greater than the period length of the first time period.
In one possible implementation manner, if the state is a duration, the storing, during the process of executing the target task by the target user account, a heartbeat message received in each second time period includes:
Each time one of the heartbeat messages is received, determining the duration of the target user account executing the target task when the heartbeat message is sent;
determining a target time period in which the duration is located in each second time period;
and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
In one possible implementation, the determining, according to the stored heartbeat message and the period length of the second time period, an actual state of the target user account to perform the target task includes:
pulling heartbeat messages corresponding to any target user account from the stored heartbeat messages aiming at any target user account;
and determining the actual time length of executing the target task by any target user account according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
In one possible implementation, after the step of determining a duration of the target user account performing the target task when sending the heartbeat message, the method further includes:
if the duration corresponding to the heartbeat message is smaller than a preset first time duration threshold value, discarding the heartbeat message;
If the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold, executing the step of determining a target time period in which the time length is located in each second time period; wherein the first time period threshold is equal to a period length corresponding to the second time period.
In one possible implementation manner, after the step of determining, in each of the second time periods, a target time period in which the duration is located, the method further includes:
and if the heartbeat message is stored in the target time period, discarding the heartbeat message.
After the step of determining the actual state of the target user account to perform the target task according to the stored heartbeat message and the cycle length of the second time period, in one possible implementation, the method further includes:
if the actual time length of the target task of any target user account is greater than a preset second time length threshold, judging that any target user account has completed the target task;
and issuing a broadcast message that the target task has been completed by any target user account in the target virtual space.
In one possible implementation manner, the determining at least one target user account in the at least two user accounts entering the target virtual space includes:
determining at least one user account to be filtered in at least two user accounts entering a target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task;
and filtering the user account to be filtered from the at least two user accounts to obtain the at least one target user account.
According to a second aspect of the embodiments of the present disclosure, there is provided a task execution state monitoring device, including:
a screening unit configured to perform determining at least one target user account among at least two user accounts entering the target virtual space; the target user account is a user account associated with a target task issued by the target virtual space;
the receiving unit is configured to receive heartbeat messages sent by the client side where the target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client;
A storage unit configured to store a piece of heartbeat messages received in each second time period during execution of the target task by the target user account, respectively;
a monitoring unit configured to perform determining an actual state of the target user account for performing the target task based on the stored heartbeat message and a cycle length of the second time period; the period length of the second time period is greater than the period length of the first time period.
In one possible implementation, if the state is a duration, the storage unit is specifically configured to perform determining, each time one of the heartbeat messages is received, a duration of the target user account performing the target task when the one heartbeat message is sent; determining a target time period in which the duration is located in each second time period; and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
In a possible implementation manner, the monitoring unit is specifically configured to perform the determining, according to the stored heartbeat message and the cycle length of the second time period, an actual state of the target user account for performing the target task, including: pulling heartbeat messages corresponding to any target user account from the stored heartbeat messages aiming at any target user account; and determining the actual time length of executing the target task by any target user account according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
In one possible implementation manner, the task execution state monitoring device is specifically further configured to execute discarding the heartbeat message if a duration corresponding to the heartbeat message is less than a preset first time threshold; if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold, executing the step of determining a target time period in which the time length is located in each second time period; wherein the first time period threshold is equal to a period length corresponding to the second time period.
In a possible implementation manner, the task execution state monitoring device is specifically further configured to execute discarding the heartbeat message if the heartbeat message has been stored within the target time period.
In one possible implementation manner, the task execution state monitoring device is specifically further configured to execute, if the actual time length of the target task of the any target user account is greater than a preset second time length threshold, determining that the any target user account has completed the target task; and issuing a broadcast message that the target task has been completed by any target user account in the target virtual space.
In one possible implementation manner, the filtering unit is specifically configured to determine at least one user account to be filtered among at least two user accounts entering the target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task; and filtering the user account to be filtered from the at least two user accounts to obtain the at least one target user account.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device comprising a memory storing a computer program and a processor implementing the task execution status monitoring method according to the first aspect or any one of the possible implementations of the first aspect when the computer program is executed.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the task execution status monitoring method according to the first aspect or any one of the possible implementations of the first aspect.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, such that the device performs the task execution status monitoring method according to any one of the possible implementations of the first aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: determining at least one target user account associated with a target task issued by the target virtual space in at least two user accounts entering the target virtual space; receiving a heartbeat message sent by a client side where a target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client; storing a piece of heartbeat messages received in each second time period respectively in the process of executing the target task by the target user account; the period length of the second time period is longer than that of the first time period; finally, determining the actual state of the target user account for executing the target task according to the stored heartbeat message and the period length of the second time period; in this way, at least one target user account associated with a target task issued by the target virtual space is determined in at least two user accounts entering the target virtual space, so that primary data peak clipping is realized, and a piece of heartbeat message received in each second time period is stored, wherein the second time period is greater than the sending period of the heartbeat message, so that secondary data peak clipping is realized; by adopting the progressive peak clipping mode, the task execution state of the user account with the task monitoring requirement is effectively monitored, the data flow consumed by message forwarding is reduced, and the data storage and data processing pressure of the server is effectively reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is an application environment diagram illustrating a method of task execution status monitoring according to an exemplary embodiment.
FIG. 2 is a flowchart illustrating a method of task execution status monitoring, according to an exemplary embodiment.
FIG. 3 is a flowchart illustrating another method of task execution status monitoring, according to an example embodiment.
FIG. 4 is a timing diagram illustrating a method of task execution status monitoring according to an exemplary embodiment.
FIG. 5 is a block diagram illustrating a task execution status monitoring device according to an exemplary embodiment.
Fig. 6 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure.
It should be further noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for presentation, analyzed data, etc.) related to the present disclosure are information and data authorized by the user or sufficiently authorized by each party.
The task execution state monitoring method provided by the disclosure can be applied to an application environment as shown in fig. 1. Wherein the client 120 communicates with the server 110 through a network. The data storage system may store data that the server 110 needs to process. The data storage system may be integrated on the server 110 or may be located on a cloud or other network server.
The server 110 determines at least one target user account among the at least two user accounts entering the target virtual space; the target user account is a user account associated with a target task issued by the target virtual space; receiving a heartbeat message sent by the client 120 where the target user account is located according to a first time period; the heartbeat message is obtained by the client 120 monitoring the state of the target user account executing the target task; the server 110 stores a heartbeat message received in each second time period during the target user account executing the target task; the server 110 determines the actual state of the target user account executing the target task according to the stored heartbeat message and the period length of the second time period; the period length of the second time period is greater than the period length of the first time period.
The client 120 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 110 may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers.
Fig. 2 is a flowchart illustrating a method of monitoring a task execution state according to an exemplary embodiment, and as shown in fig. 2, the method is also used in the server 120 of fig. 1, and includes the following steps.
In step S210, at least one target user account is determined among at least two user accounts entering the target virtual space.
In the live broadcast application scene, the target virtual space can refer to a live broadcast room where a host broadcast initiates live broadcast; in an online shopping scenario, the target virtual space may refer to an online store, or the like; in an instant chat scenario, the target virtual space may refer to a chat group in a group chat function.
The target user account is a user account associated with a target task issued by the target virtual space.
Wherein different target tasks have different task completion conditions.
For example, in a live application scenario, the target user account may refer to a viewer account having a viewing task. The task completion condition of the viewing task may refer to the viewing time period being greater than a preset time period threshold.
In a specific implementation, taking a target task as a viewing task in a live broadcast application scenario as an example, a server may determine an audience account that needs to monitor the execution state of the viewing task (i.e., a target audience account having the viewing task) from at least two audience accounts entering a live broadcast room.
Because the number of audience accounts of the live broadcast platform is numerous, in practical application, an account ID tail number slicing (splitting) mode can be adopted in advance, and the audience accounts of the live broadcast platform are divided into a plurality of groups by using a bitmap algorithm (a data storage algorithm) and stored in a Memcache (a cache system). And then, the server acquires bitmaps (bitmaps) corresponding to all users participating in the watching task and the corresponding bitmaps (bitmaps) of the users completing the watching task by monitoring the message queue of the watching task to construct a local cache, so as to filter out the users not in possession of the watching task (namely, realize first-stage peak clipping) and obtain a target user account.
In step S220, a heartbeat message sent by a client where the target user account is located according to a first time period is received; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client.
In a specific implementation, a client where a target user account is located monitors the state of the target user account for executing a target task according to a first time period, generates a heartbeat message from a result obtained by monitoring the state of the target user account for executing the target task, and sends the heartbeat message to a server, so that the server receives the heartbeat message. For example, in the process of watching the live broadcast room, the client side where the target user account a is located establishes a heartbeat connection with the server, and sends a heartbeat message to the service network every 10 seconds (the first time period) indicating that the target user account a is watching the live broadcast room (i.e. the client side where the target user account a is located is playing video content in the live broadcast room).
In step S230, during the process of executing the target task by the target user account, a heartbeat message received in each second time period is stored.
Wherein the period length of the second time period is greater than the period length of the first time period. For example, the cycle length of the second time period may be set to 1 minute.
In a specific implementation, during the process that the target user account performs the target task, the server may store a heartbeat message received in each second time period.
Specifically, during each second time period when the target user account performs the target task, each time a heartbeat message is received, the server may determine whether a heartbeat message has been stored during the second time period when the heartbeat message is located (e.g., whether a heartbeat message has been sent to the target message queue during the second time period when the heartbeat message is located), and if the server does not send a heartbeat message to the target message queue during the second time period when the heartbeat message is located, the server forwards the heartbeat message to the target message queue to implement storing the heartbeat message. If the server has sent the heartbeat message to the target message queue within the second time period in which the heartbeat message is located, the server discards the heartbeat message.
For example, assuming that the period duration of the second time period is 1 minute, when the server receives the heartbeat message a (the heartbeat message a is used to represent an event that the viewer account a has watched the live room for 1 minute and 20 seconds), the server determines whether the heartbeat message has been sent to the target message queue within the second time period (1 minute to 2 minutes) in which the heartbeat message a is located; when the server has sent a heartbeat message B (heartbeat message B is used to characterize the event that the viewer account a has watched the live room for 1 minute and 10 seconds) to the target message queue, the server discards this heartbeat message a. And when the server does not send the heartbeat message to the target message queue within the second time period of the heartbeat message A, the server sends the heartbeat message A to the target message queue. In practical applications, the server may use the user ID of the viewer account, the live room ID, and the number of minutes corresponding to the heartbeat message (for example, the number of minutes corresponding to the heartbeat message a is 1) as the unique key; and judging whether the current minutes (namely, the time interval in which the current minutes are located) have forwarded the heartbeat message according to the unique key, if so, not forwarding the heartbeat message any more, otherwise, forwarding the heartbeat message. Therefore, only one heartbeat message can be ensured to be forwarded to the target message queue in a second time period, and the forwarding quantity of the heartbeat message is further reduced.
In step S240, the actual state of the target user account for performing the target task is determined based on the stored heartbeat message and the period length of the second time period.
In a specific implementation, the server may determine an actual state of the target user account executing the target task according to the stored heartbeat message and the period length of the second time period.
Taking the target task as a watching task as an example, the server can count the number of the stored heartbeat messages and the period length of the second time period to obtain the actual time length of the target user account for executing the target task. In practical application, the downstream terminal may pull the stored heartbeat message from the target message queue; and then, the downstream terminal determines the actual time length of the target user account for executing the target task according to the number of the pulled heartbeat messages and the period length of the second time period.
For example, the period length of the second time period is known to be 1 minute, and each time a heartbeat message corresponding to the target user account is successfully pulled from the target message queue, the number of minutes corresponding to the actual time period for the target user account to execute the target task is increased by 1.
According to the task execution state monitoring method, at least one target user account associated with a target task issued by a target virtual space is determined in at least two user accounts entering the target virtual space; receiving a heartbeat message sent by a client side where a target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client; storing a piece of heartbeat messages received in each second time period respectively in the process of executing the target task by the target user account; the period length of the second time period is longer than that of the first time period; finally, determining the actual state of the target user account for executing the target task according to the stored heartbeat message and the period length of the second time period; in this way, at least one target user account associated with a target task issued by the target virtual space is determined in at least two user accounts entering the target virtual space, so that primary data peak clipping is realized, and a piece of heartbeat message received in each second time period is stored, wherein the second time period is greater than the sending period of the heartbeat message, so that secondary data peak clipping is realized; by adopting the progressive peak clipping mode, the task execution state of the user account with the task monitoring requirement is effectively monitored, the data flow consumed by message forwarding is reduced, and the data storage and data processing pressure of the server is effectively reduced.
In one embodiment, if the status is a duration, during the process of executing the target task by the target user account, storing a heartbeat message received in each second time period, respectively, including: each time a heartbeat message is received, determining the duration of time for the target user account to perform the target task when the heartbeat message is sent; determining a target time period in which the duration is located in each second time period; if the heartbeat message is not stored in the target time period, storing the heartbeat message.
If the heartbeat message is forwarded to the target message queue within the target time period, the heartbeat message is abandoned.
In the specific implementation, if the state is the duration, the server stores a piece of heartbeat message received in each second time period in the process of executing the target task by the target user account, and determines the duration of executing the target task by the target user account when the piece of heartbeat message is sent every time the server receives the piece of heartbeat message; determining a target time period in which the duration is located in each second time period; if the heartbeat message is not stored in the target time period, storing the heartbeat message; if the heartbeat message is not stored in the target time period, storing the heartbeat message.
For example, when the server receives a heartbeat message (e.g., heartbeat information C) sent by the client where the target user account is located, the server determines that the duration of the target user account performing the target task when the heartbeat information C is sent is 2 minutes and 30 seconds; the server determines the target time period of the duration in each second time period (for example, the second time period is 1:0 min to 1 min, the second time period is 2:1 min to 2 min, the second time period is 3:2 min to 3 min, …, and the second time period n is n-1 min to n min) as the second time period 2; the server judges whether heartbeat messages are sent in the second time period 2; if the heartbeat message is not stored in the target time period, storing the heartbeat message; if the heartbeat message is not stored in the target time period, storing the heartbeat message.
According to the technical scheme of the embodiment, the time length for executing the target task by the target user account when the heartbeat message is sent is determined every time the heartbeat message is received; determining a target time period in which the duration is located in each second time period; if the heartbeat message is not stored in the target time period, the heartbeat message is stored, so that the task execution state of the user account with the task monitoring requirement is effectively monitored, the data flow consumed by message forwarding is reduced, and the data storage and data processing pressure of the server is effectively reduced.
In one embodiment, determining the actual state of the target user account to perform the target task based on the stored heartbeat message and the cycle length of the second time period includes: pulling heartbeat messages corresponding to any target user account from the stored heartbeat messages aiming at any target user account; and determining the actual time length of any target user account for executing the target task according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
In specific implementation, for any target user account, the heartbeat message corresponding to any target user account can be pulled from the stored heartbeat messages; and then, determining the actual time length of any target user account for executing the target task according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
In practical application, the downstream end can pull the stored heartbeat message from the target message queue; and then, the downstream end determines the actual time length of the target user account for executing the target task according to the number of the pulled heartbeat messages and the period length of the second time period. For example, the period length of the second time period is known to be 1 minute, and each time a heartbeat message corresponding to the target user account is successfully pulled from the target message queue, the number of minutes corresponding to the actual time period for the target user account to execute the target task is increased by 1.
According to the technical scheme of the embodiment, heartbeat messages corresponding to any target user account are pulled from stored heartbeat messages by aiming at any target user account; according to the number of the pulled heartbeat messages and the period length corresponding to the second time period, the actual time length of any target user account for executing the target task is determined, and the purpose of accumulating the effective watching time length to achieve the purpose of counting whether the target user account completes the task is achieved.
In one embodiment, after the step of determining the length of time the target user account performs the target task at the time the heartbeat message is sent, the method further includes: if the duration corresponding to the heartbeat message is smaller than a preset first time duration threshold value, discarding the heartbeat message; and if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold value, executing the step of determining the target time period in which the time length is located in each second time period.
Wherein the first time period threshold is equal to a period length corresponding to the second time period. For example, assuming that the period length corresponding to the second time period is 1 minute, the first time period threshold is 1 minute.
In a specific implementation, after determining the time length of the target user account executing the target task when the heartbeat message is sent, the server may determine the time length corresponding to the heartbeat message and a preset first time length threshold; and discarding the heartbeat message when the duration corresponding to the heartbeat message is smaller than a preset first time duration threshold value.
And if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold value, executing the step of determining the target time period in which the time length is located in each second time period. Namely, aiming at the user account with the watching task, the server discards all heartbeat messages corresponding to events which are watched for less than 1 minute, so that errors are avoided when the actual time length of the target user account for executing the target task is calculated later.
In one embodiment, after the step of determining the actual state of the target user account for performing the target task based on the stored heartbeat message and the cycle length of the second time period, the method further comprises: if the actual time length of the target task of any target user account is greater than a preset second time length threshold, judging that any target user account has completed the target task; and issuing a broadcast message that any target user account has completed the target task in the target virtual space.
The second time threshold may be determined according to a condition for completing the target task.
In a specific implementation, assuming that the target task is a watching task and the condition for completing the watching task is that the watching duration exceeds 10 minutes, the second duration threshold value can be set to be 10 minutes; after determining the actual time length of the target user account for executing the target task, the server can determine whether the actual time length of the target user account for executing the target task (for example, the time length of watching the live broadcasting room) is greater than a second time length threshold (10 minutes), and if the actual time length is greater than a preset second time length threshold, the server determines that the target user account has completed the watching task; a broadcast message is issued in the living room that the target user account has completed the target task. In practical application, the server may further store the tail number fragments of the account ID of the target user account in the target database, so as to realize marking that the target user account has completed the viewing task.
If the time length of the target user account watching the live broadcasting room is less than 10 minutes, the server continues to monitor the state of the target user account watching the live broadcasting room.
It should be noted that, the specific limitation of monitoring the state of the target user account watching the live broadcast room may be referred to above, and will not be described herein.
According to the technical scheme, when the actual time length of the target task of any target user account is larger than the preset second time length threshold, the target task of any target user account is judged to be completed, and a broadcast message that the target task of any target user account is finished is issued, so that the target user account which is finished is timely judged, and the condition monitoring of the user account which is finished with the target task is avoided.
In one embodiment, determining at least one target user account from among at least two user accounts that enter the target virtual space comprises: determining at least one user account to be filtered in at least two user accounts entering a target virtual space; filtering user accounts to be filtered from at least two user accounts to obtain at least one target user account.
The user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task.
In a specific implementation, in the process that the server determines at least one target user account in at least two user accounts entering the target virtual space, the server may determine the user account that has completed the target task from the at least two user accounts, and use the user account that has completed the target task as the user account to be filtered. Then, the server filters the user accounts to be filtered from at least two user accounts to obtain at least one target user account.
Taking a target task as a viewing task for example, knowing that at least two user accounts entering a living broadcast room A comprise a spectator account A and a spectator account B, when determining a target spectator account needing to monitor whether the viewing task is completed from the spectator account A and the spectator account B, the server can judge whether the spectator account has completed the viewing task; if the viewing task has been completed by the viewer account a, the server does not monitor whether the viewing task is completed by the viewer account a, and only takes the viewer account B as the target user account.
According to the technical scheme, the user accounts which have completed the target task are filtered out from at least two user accounts which enter the target virtual space, so that redundant state monitoring of the user accounts which have completed the target task is avoided, invalid data flow is reduced, and data flow generated by monitoring the target task is reduced.
Fig. 3 is a flowchart illustrating another task execution status monitoring method, as shown in fig. 3, for use in the server 110 of fig. 1, according to an exemplary embodiment, including the following steps.
In step S310, at least one user account to be filtered is determined among at least two user accounts entering the target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task.
In step S320, the user account to be filtered is filtered out from the at least two user accounts, so as to obtain at least one target user account.
In step S330, a heartbeat message sent by the client where the target user account is located according to the first time period is received; each time one of the heartbeat messages is received, determining the duration of the target user account executing the target task when the heartbeat message is sent; determining a target time period in which the duration is located in each second time period; and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
In step S340, for any one of the target user accounts, a heartbeat message corresponding to the any one of the target user accounts is pulled from the stored heartbeat messages.
In step S350, according to the number of the pulled heartbeat messages and the period length corresponding to the second time period, an actual duration of executing the target task by the any target user account is determined.
In step S360, if the actual time length of the target task of any target user account is greater than the preset second time length threshold, it is determined that any target user account has completed the target task.
In step S370, a broadcast message is issued in the target virtual space that the target task has been completed by any of the target user accounts.
It should be noted that, the specific limitation of the above steps may be referred to the specific limitation of a task execution status monitoring method, which is not described herein.
It should be understood that, although the steps in the flowcharts of fig. 2 and 3 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in fig. 2 and 3 may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the execution of the steps or stages is not necessarily sequential, but may be performed in rotation or alternatively with at least a portion of the steps or stages in other steps or steps.
For ease of understanding by those skilled in the art, FIG. 4 illustratively provides a timing diagram of a method of task execution status monitoring; the account ID tail number slicing (splitting) mode may be adopted in advance, and the account of the audience of the live broadcast platform is divided into a plurality of groups by using a bitmap algorithm (a data storage algorithm) and stored in a Memcache (a cache system). And then, the server acquires bitmaps (bitmaps) corresponding to all users participating in the watching task and the corresponding bitmaps (bitmaps) of the users completing the watching task by monitoring the message queue of the watching task to construct a local cache, so as to filter out the users not in possession of the watching task (namely, realize first-stage peak clipping) and obtain a target user account.
And then, generating a heartbeat message from a result obtained by monitoring the state of the target user account for executing the target task, and sending the heartbeat message to the server so as to be received by the server. For example, in the process of watching the live broadcast room, the client side where the target user account a is located establishes a heartbeat connection with the server, and sends a heartbeat message to the service network every 10 seconds (the first time period) indicating that the target user account a is watching the live broadcast room (i.e. the client side where the target user account a is located is playing video content in the live broadcast room).
Assuming that the period duration of the second time period is 1 minute, when the server receives the heartbeat message a (the heartbeat message a is used for representing an event that the audience account a has watched the live broadcast room for 1 minute and 20 seconds), the server judges whether the heartbeat message is sent to the target message queue in the second time period (1 minute to 2 minutes) in which the heartbeat message a is located; when the server has sent a heartbeat message B (heartbeat message B is used to characterize the event that the viewer account a has watched the live room for 1 minute and 10 seconds) to the target message queue, the server discards this heartbeat message a. And when the server does not send the heartbeat message to the target message queue within the second time period of the heartbeat message A, the server sends the heartbeat message A to the target message queue.
In practical applications, the server may use the user ID of the viewer account, the live room ID, and the number of minutes corresponding to the heartbeat message (for example, the number of minutes corresponding to the heartbeat message a is 1) as the unique key; and judging whether the current minutes (namely, the time interval in which the current minutes are located) have forwarded the heartbeat message according to the unique key, if so, not forwarding the heartbeat message any more, otherwise, forwarding the heartbeat message. Therefore, only one heartbeat message can be ensured to be forwarded to the target message queue in a second time period, and the forwarding quantity of the heartbeat message is further reduced.
Every time a heartbeat message corresponding to the target user account is successfully pulled from the target message queue, the number of minutes corresponding to the actual time period of the target user account executing the target task is increased by 1.
It should be understood that the same/similar parts of the embodiments of the method described above in this specification may be referred to each other, and each embodiment focuses on differences from other embodiments, and references to descriptions of other method embodiments are only needed.
FIG. 5 is a block diagram illustrating a task execution status monitoring device according to an exemplary embodiment. Referring to fig. 5, the apparatus includes:
a screening unit 510 configured to perform determining at least one target user account among at least two user accounts entering the target virtual space; the target user account is a user account associated with a target task issued by the target virtual space;
a receiving unit 520, configured to perform receiving a heartbeat message sent by a client where the target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client;
a storage unit 530 configured to store a heartbeat message received in each second time period during execution of the target task by the target user account, respectively;
A monitoring unit 540 configured to perform determining an actual state of the target user account performing the target task based on the stored heartbeat message and a cycle length of the second time period; the period length of the second time period is greater than the period length of the first time period.
In an exemplary embodiment, if the state is a duration, the storage unit 530 is specifically configured to determine, each time one of the heartbeat messages is received, a duration for the target user account to perform the target task when the one heartbeat message is sent; determining a target time period in which the duration is located in each second time period; and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
In an exemplary embodiment, the monitoring unit 540 is specifically configured to perform the determining, according to the stored heartbeat message and the cycle length of the second time period, an actual state of the target user account performing the target task, including: pulling heartbeat messages corresponding to any target user account from the stored heartbeat messages aiming at any target user account; and determining the actual time length of executing the target task by any target user account according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
In an exemplary embodiment, the task execution state monitoring device is specifically further configured to execute discarding the heartbeat message if a duration corresponding to the heartbeat message is less than a preset first time threshold; if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold, executing the step of determining a target time period in which the time length is located in each second time period; wherein the first time period threshold is equal to a period length corresponding to the second time period.
In an exemplary embodiment, the task execution state monitoring device is specifically further configured to execute discarding the heartbeat message if the heartbeat message has been stored within the target time period.
In an exemplary embodiment, the task execution state monitoring device is specifically further configured to execute, if the actual time length of the target task of the any target user account is greater than a preset second time length threshold, determining that the any target user account has completed the target task; and issuing a broadcast message that the target task has been completed by any target user account in the target virtual space.
In an exemplary embodiment, the filtering unit 510 is specifically configured to determine at least one user account to be filtered among at least two user accounts entering the target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task; and filtering the user account to be filtered from the at least two user accounts to obtain the at least one target user account.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 6 is a block diagram of an electronic device 600 for performing the task execution status monitoring method described above, according to an example embodiment. For example, the electronic device 600 may be a server. Referring to fig. 6, electronic device 600 includes a processing component 620 that further includes one or more processors and memory resources represented by memory 622 for storing instructions, such as applications, executable by processing component 620. The application program stored in memory 622 may include one or more modules each corresponding to a set of instructions. Further, the processing component 620 is configured to execute instructions to perform the methods described above.
The electronic device 600 may further include: the power component 624 is configured to perform power management of the electronic device 600, the wired or wireless network interface 626 is configured to connect the electronic device 600 to a network, and an input output (I/O) interface 628. The electronic device 600 may operate based on an operating system stored in memory 622, such as Windows Server, mac OS X, unix, linux, freeBSD, or the like.
In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 622, including instructions executable by a processor of electronic device 600 to perform the above-described method. The storage medium may be a computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, comprising instructions therein, which are executable by a processor of the electronic device 600 to perform the above-described method.
It should be noted that the descriptions of the foregoing apparatus, the electronic device, the computer readable storage medium, the computer program product, and the like according to the method embodiments may further include other implementations, and the specific implementation may refer to the descriptions of the related method embodiments and are not described herein in detail.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (16)
1. A method for monitoring a task execution state, comprising:
determining at least one target user account in at least two user accounts entering a target virtual space; the target user account is a user account associated with a target task issued by the target virtual space;
receiving a heartbeat message sent by a client side where the target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client;
Storing a heartbeat message received in each second time period during the process of executing the target task by the target user account; the period length of the second time period is longer than the period length of the first time period;
and determining the actual state of the target user account for executing the target task according to the stored number of the heartbeat messages and the period length of the second time period.
2. The method according to claim 1, wherein if the status is a duration, the step of storing a heartbeat message received in each second time period during the target user account executing the target task includes:
each time one of the heartbeat messages is received, determining the duration of the target user account executing the target task when the heartbeat message is sent;
determining a target time period in which the duration is located in each second time period;
and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
3. The task execution state monitoring method according to claim 2, wherein the determining the actual state of the target user account to execute the target task according to the stored heartbeat message and the cycle length of the second time period includes:
Pulling heartbeat messages corresponding to the target user accounts from the stored heartbeat messages aiming at any target user account;
and determining the actual time length of the target user account for executing the target task according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
4. The task execution state monitoring method according to claim 2, wherein after the step of determining a duration of execution of the target task by the target user account when the heartbeat message is sent, the method further comprises:
if the duration corresponding to the heartbeat message is smaller than a preset first time duration threshold value, discarding the heartbeat message;
if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold, executing the step of determining a target time period in which the time length is located in each second time period; wherein the first time period threshold is equal to a period length corresponding to the second time period.
5. The task execution state monitoring method according to claim 2, wherein after the step of determining a target time period in which the duration is located in each of the second time periods, the method further comprises:
And if the heartbeat message is stored in the target time period, discarding the heartbeat message.
6. The task execution state monitoring method according to claim 2, wherein after the step of determining the actual state of the target user account to execute the target task based on the stored heartbeat message and the cycle length of the second time period, the method further comprises:
if the actual time length of the target task of any target user account is greater than a preset second time length threshold value, judging that the target user account has completed the target task;
and issuing a broadcast message that the target user account has completed the target task in the target virtual space.
7. The task execution status monitoring method according to any one of claims 1 to 6, wherein the determining at least one target user account among at least two user accounts entering the target virtual space includes:
determining at least one user account to be filtered in at least two user accounts entering a target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task;
And filtering the user account to be filtered from the at least two user accounts to obtain the at least one target user account.
8. A task execution state monitoring device, characterized by comprising:
a screening unit configured to perform determining at least one target user account among at least two user accounts entering the target virtual space; the target user account is a user account associated with a target task issued by the target virtual space;
the receiving unit is configured to receive heartbeat messages sent by the client side where the target user account is located according to a first time period; the heartbeat message is obtained by monitoring the state of the target user account executing the target task by the client;
a storage unit configured to store a piece of heartbeat messages received in each second time period during execution of the target task by the target user account, respectively;
a monitoring unit configured to perform determining an actual state of the target user account performing the target task according to the number of stored heartbeat messages and a period length of the second time period; the period length of the second time period is greater than the period length of the first time period.
9. The task execution state monitoring device according to claim 8, wherein if the state is a duration, the storage unit is specifically configured to perform determining a duration of the target task being executed by the target user account when sending one of the heartbeat messages each time the one heartbeat message is received; determining a target time period in which the duration is located in each second time period; and if the heartbeat message is not stored in the target time period, storing the heartbeat message.
10. The task execution status monitoring device of claim 9, wherein the monitoring unit, in particular configured to perform the determining the actual status of the target user account to execute the target task based on the stored heartbeat message and the cycle length of the second time period, comprises: pulling heartbeat messages corresponding to the target user accounts from the stored heartbeat messages aiming at any target user account; and determining the actual time length of the target user account for executing the target task according to the number of the pulled heartbeat messages and the period length corresponding to the second time period.
11. The task execution state monitoring device according to claim 9, wherein the task execution state monitoring device is specifically further configured to discard the heartbeat message if a duration corresponding to the heartbeat message is less than a preset first time threshold; if the time length corresponding to the heartbeat message is greater than or equal to the first time length threshold, executing the step of determining a target time period in which the time length is located in each second time period; wherein the first time period threshold is equal to a period length corresponding to the second time period.
12. The task execution state monitoring device of claim 9, wherein the task execution state monitoring device is further specifically configured to execute discarding a heartbeat message if the heartbeat message has been stored within the target time period.
13. The task execution state monitoring device of claim 9, wherein the task execution state monitoring device is specifically further configured to determine that any one of the target user accounts has completed the target task if an actual time period of the target task is greater than a preset second time period threshold; and issuing a broadcast message that the target user account has completed the target task in the target virtual space.
14. Task execution status monitoring device according to any one of claims 8 to 13, wherein the screening unit is specifically configured to perform determining at least one user account to be filtered among at least two user accounts entering the target virtual space; the user accounts to be filtered comprise user accounts which have completed the target task and user accounts which are not associated with the target task; and filtering the user account to be filtered from the at least two user accounts to obtain the at least one target user account.
15. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the task execution state monitoring method of any one of claims 1 to 7.
16. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of a server, enable the server to perform the task execution status monitoring method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210481036.0A CN114885219B (en) | 2022-05-05 | 2022-05-05 | Task execution state monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210481036.0A CN114885219B (en) | 2022-05-05 | 2022-05-05 | Task execution state monitoring method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114885219A CN114885219A (en) | 2022-08-09 |
| CN114885219B true CN114885219B (en) | 2023-08-29 |
Family
ID=82673702
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210481036.0A Active CN114885219B (en) | 2022-05-05 | 2022-05-05 | Task execution state monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114885219B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106961364A (en) * | 2017-04-24 | 2017-07-18 | 努比亚技术有限公司 | Heartbeat detecting method and application server |
| CN110808874A (en) * | 2019-10-25 | 2020-02-18 | 北京大米科技有限公司 | Cross-machine-room service monitoring method and device, storage medium and server |
| CN111901617A (en) * | 2020-07-17 | 2020-11-06 | 北京达佳互联信息技术有限公司 | Method and device for calculating live broadcast watching time length |
| CN112311629A (en) * | 2020-10-30 | 2021-02-02 | 广州华多网络科技有限公司 | Data processing method, device, server and computer readable storage medium |
| WO2021244087A1 (en) * | 2020-06-02 | 2021-12-09 | 华为技术有限公司 | Long connection apparatus and network system |
| CN113949894A (en) * | 2021-10-18 | 2022-01-18 | 上海哔哩哔哩科技有限公司 | Live broadcast related duration recording method and device |
-
2022
- 2022-05-05 CN CN202210481036.0A patent/CN114885219B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106961364A (en) * | 2017-04-24 | 2017-07-18 | 努比亚技术有限公司 | Heartbeat detecting method and application server |
| CN110808874A (en) * | 2019-10-25 | 2020-02-18 | 北京大米科技有限公司 | Cross-machine-room service monitoring method and device, storage medium and server |
| WO2021244087A1 (en) * | 2020-06-02 | 2021-12-09 | 华为技术有限公司 | Long connection apparatus and network system |
| CN111901617A (en) * | 2020-07-17 | 2020-11-06 | 北京达佳互联信息技术有限公司 | Method and device for calculating live broadcast watching time length |
| CN112311629A (en) * | 2020-10-30 | 2021-02-02 | 广州华多网络科技有限公司 | Data processing method, device, server and computer readable storage medium |
| CN113949894A (en) * | 2021-10-18 | 2022-01-18 | 上海哔哩哔哩科技有限公司 | Live broadcast related duration recording method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114885219A (en) | 2022-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018059353A1 (en) | Message processing method and apparatus | |
| JP6127150B2 (en) | Send notifications to multiple devices associated with a user | |
| US9686329B2 (en) | Method and apparatus for displaying webcast rooms | |
| CN105635180B (en) | Information push method and device | |
| CN106993234A (en) | Barrage display methods and device | |
| CN111669438B (en) | Live broadcast message transmission method and device, electronic equipment and medium | |
| CN110996109A (en) | Abnormal live broadcast room cleaning method and device, live broadcast server and storage medium | |
| CN111935536B (en) | Live broadcast room request response method, device, equipment and storage medium | |
| CN109547511A (en) | A kind of real-time method for pushing of WEB message, server, client and system | |
| WO2017181601A1 (en) | Live broadcast streaming processing method, apparatus, electronic device and system | |
| CN110580188A (en) | multithreading network distribution method and storage medium | |
| CN108965932A (en) | A kind of even wheat window methods of exhibiting and device | |
| CN112752113B (en) | Method and device for determining abnormal factors of live broadcast server | |
| CN111787345A (en) | Interactive resource processing method and device based on network live broadcast room, server and storage medium | |
| CN106254954A (en) | A kind of method and apparatus sending live notice | |
| CN114928758A (en) | Live broadcast abnormity detection processing method and device | |
| CN113346973B (en) | Event prompting method and device, electronic equipment and computer readable storage medium | |
| CN104468248B (en) | Service performance monitoring method, reverse proxy server, statistical analysis server and system | |
| CN114885219B (en) | Task execution state monitoring method and device, electronic equipment and storage medium | |
| CN112764988B (en) | Data segment acquisition method and device | |
| CN105898596B (en) | Direct broadcasting room display control method and device | |
| CN115379253B (en) | Live content anomaly determination and restoration method and device, equipment and medium thereof | |
| CN114884924B (en) | Audio and video channel selection method and device, electronic equipment and storage medium | |
| CN113271474B (en) | Method, device, equipment and storage medium for testing streaming media server | |
| CN114301812B (en) | Method, device, equipment and storage medium for monitoring message processing result |
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 |