CN114598664A - Task execution method and related device - Google Patents
Task execution method and related device Download PDFInfo
- Publication number
- CN114598664A CN114598664A CN202011407769.7A CN202011407769A CN114598664A CN 114598664 A CN114598664 A CN 114598664A CN 202011407769 A CN202011407769 A CN 202011407769A CN 114598664 A CN114598664 A CN 114598664A
- Authority
- CN
- China
- Prior art keywords
- task
- request
- network
- target
- executed
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
- H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/484—Precedence
Abstract
The invention provides a task execution method and related equipment, belongs to the technical field of computers, and aims to realize the function of automatically re-executing unfinished tasks or failed tasks after network recovery and solve the problem that in the prior art, task operation needs to be manually performed after the network is recovered every time. The method comprises the following steps: when the network state is a network-free state or a weak network state, acquiring a target task, wherein the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is the network state when the network connection quality is lower than a preset connection quality threshold value, and the network state is obtained by monitoring the network operation condition; adding a target task into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priorities; and when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a task execution method and a related apparatus.
Background
With the development and popularization of networks, people increasingly depend on the networks. Through the network, people can realize shopping, chatting, working and even various leisure and entertainment. In the process of using the network, the situation of network condition deterioration or network disconnection often occurs, and particularly, with the rise of the mobile terminal, the situation of no network or weak network caused by poor network coverage and the like is more likely to occur in the process of the mobile terminal position change. That is, when a user performs operations such as shopping and watching videos through a network, tasks corresponding to the operations may be interrupted or failed to be executed due to the network.
At present, for the situation that task execution is interrupted or failed under the influence of a network state, when the device network state of a user returns to normal, for example, a mobile terminal moves from inside to outside of an elevator, the task that is interrupted or failed to be executed also needs to be manually operated by the user to be executed again, and especially when the network repeatedly occurs the situation of "network interruption-network recovery", the task execution mode in the prior art needs to be manually operated by the user repeatedly, which leads to a complicated operation mode in the task execution process and seriously affects user experience.
Disclosure of Invention
The invention aims to provide a task execution method, which can add tasks which are not completed or failed into a task queue to be executed and execute the tasks in sequence through the task queue to be executed when a network is recovered to be normal, thereby realizing the function of automatically re-executing the tasks which are not completed or the tasks which are failed after the network is recovered, avoiding the need of manually operating after the network is recovered in the prior art each time, simplifying the operation process of task execution and improving the user experience.
In a first aspect, the present invention provides a task execution method including the steps of:
when the network state is a network-free state or a weak network state, acquiring a target task, wherein the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is the network state when the network connection quality is lower than a preset connection quality threshold, and the network state is obtained by monitoring the network operation condition;
adding the target task into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priority;
and when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
Optionally, when the network status is no network or a weak network, acquiring the target task includes:
monitoring an operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface, wherein the attribute information comprises a request identifier, request header information and request body information, and the request identifier is information preset for distinguishing the request;
the adding the target task to the task queue to be executed comprises:
and generating target task information according to the attribute information, and adding the target task information into the task queue to be executed.
Optionally, before monitoring the operation interface through the preset interface to obtain the attribute information corresponding to the request in the operation interface, the method further includes:
the method comprises the steps of judging a request source of a request in the operation interface, and adding a request identifier corresponding to the request source for the request, wherein the request identifier comprises a page identifier and a module identifier, the page identifier is used for representing that the request is sent based on page operation, the module identifier is used for representing that the request is sent based on a program module, and the program module comprises a live program module.
Optionally, each target task corresponds to at least one request;
before monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further comprises the following steps:
and setting an association list for each request, wherein the association list is used for storing request identifiers with association relations, and the association relations are determined based on the target tasks corresponding to the requests.
Optionally, monitoring the operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface includes:
setting a page attribute Class as Class PageInfo, wherein the page attribute Class is used for recording the page attribute of the request;
defining a request identity for each of said requests as Uint64_ t identifiyd;
calling a constructor of the page attribute class to execute assignment operation as PageInfo (Uint64_ t IdentityId) and IdentityId (IdentityId), wherein PageInfo (Uint64_ t IdentityId) is a caller, IdentityId (IdentityId) is used for representing assignment to a member variable PageInfo (Uint64_ t IdentityId) as a caller, and IdentityId (IdentityId) is used for representing assignment to the member variable, and the assignment operation is used for adding the defined request identifier to the constructor so as to update an initial value to a value corresponding to the request identifier.
Optionally, the adding the target task to the to-be-executed task queue includes:
and generating a task list according to the request attribute, and adding the task list into the to-be-executed task queue, wherein the task list specifically comprises the request header information RequestHeader, the request body information RequestBody and the request identifier IdentifyId.
Optionally, before the target task is added to the to-be-executed task queue, the method further includes:
determining a task priority of each target task according to an operation behavior in the operation interface, wherein the task priority is determined according to a task type of the target task, the task type corresponds to the requested operation corresponding to the target task, and the task type comprises a page task, a module task, a video stream task and an associated request task;
when the operation behavior is page operation, determining that the task priority of the target task corresponding to the page task is the highest;
when the operation behavior is module operation, determining that the task priority of the target task corresponding to the module task is the highest;
when the operation behavior is video stream operation, determining that the task priority of the target task corresponding to the video stream task is the highest;
when the operation behavior is an operation corresponding to a plurality of requests, determining that the priority of a target task corresponding to the association request task having an association relation with the operation is the highest;
the adding the target task to a task queue to be executed includes:
and arranging a plurality of the target tasks according to the task priorities and adding the target task information into the task queue to be executed, wherein the sequencing order in the task queue to be executed is positively correlated with the task priorities.
A second aspect of the embodiments of the present application provides a task execution device, including:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a target task when a network state is a network-free or weak network, the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is a network state when the network connection quality is lower than a preset connection quality threshold value, and the network state is obtained by monitoring the network operation condition;
the adding unit is used for adding the target tasks into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priority;
and the execution unit is used for executing the target tasks of the task queue to be executed according to the task priority sequence when the network state is the network normal state.
According to the task execution method and the related device, when the network state is no network or weak network, the target task is obtained; then, adding the target task into a task queue to be executed; and finally, when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence. In the above scheme, the target tasks are uncompleted tasks and failed tasks under the influence of network factors, the weak network is a network state when the network connection quality is lower than a preset connection quality threshold, the network state is obtained by monitoring the network operation condition, the task queue to be executed contains a plurality of the target tasks, and the target tasks in the task queue to be executed are sorted according to task priority. Based on the method of the scheme, when the network state is no network or weak network, the task which is not executed or failed due to network influence can be added into the task queue to be executed, and when the network state is recovered to be network normal, the task in the task queue to be executed is executed, so that the task which is not executed originally can be automatically re-executed after the network is recovered from poor condition to normal condition, the effect of automatically re-executing the task which is influenced by the network and is not normally executed can be realized without manual operation after the network is recovered, the task execution process can be simplified, and the user experience is improved. In addition, in the above scheme, since the target tasks can be executed according to the order of the priorities when the network state is normal, it can be ensured that the target tasks are executed in the order of the priorities when a plurality of target tasks need to be executed, so that when the task in the interface operated by the user is the highest priority, the network state can be preferentially executed once the network state is recovered to the normal state, the user can know that the network state is recovered at the first time, and then the effect of laterally reminding the user of the change situation of the network state is achieved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a task execution method according to an embodiment of the present invention;
FIG. 2 is a diagram of a task execution device according to an embodiment of the present invention;
fig. 3 is a schematic diagram of an embodiment of an electronic device according to an embodiment of the present application;
fig. 4 is a schematic diagram of an embodiment of a computer-readable storage medium provided in an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "comprising" and "having," and any variations thereof, as referred to in embodiments of the present invention, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
As shown in fig. 1, a task execution method provided in an embodiment of the present invention includes the following steps:
101. and when the network state is no network or weak network, acquiring the target task.
The target tasks are tasks which are not completed and failed under the influence of network factors, the weak network is a network state when the network connection quality is lower than a preset connection quality threshold value, and the network state is obtained by monitoring the network operation condition.
In some examples, since the obtaining process of the target task actually needs to be monitored by a monitoring program, the method of this step may be specifically executed as follows: monitoring the operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface, wherein the attribute information comprises a request identifier, request header information and request body information, and the request identifier is information preset for distinguishing the request.
In the above example, the request header information and the request body information can be used to determine the data source and the data content corresponding to the request, that is, what the data source corresponding to the request issued by each user is and what the requested content is can be determined by the attribute information.
In addition, the normal request is to obtain the return data after the current page sends out the request, and the request for the return data can directly fill the information of the page because the request is at the current page. However, in some cases, the request may have left the page corresponding to the request when being sent, and if data fed back by the request is received, the data may be discarded because the page does not exist. Therefore, for practical applications, after determining the request header information and the request body information, it is necessary to set an identifier to determine which page each request corresponds to.
For the above reasons, in some examples, before the monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method may further include: and judging the request source of the request in the operation interface, and adding a request identifier corresponding to the request source for the request.
The request identification comprises a page identification and a module identification, the page identification is used for representing that the request is sent based on page operation, the module identification is used for representing that the request is sent based on a program module, and the program module comprises a live program module.
It should be noted that the setting of the request identifier may be a unique character or a character string, so that each request can be distinguished. For the page identifier, due to the special property of the page, the page content actually required by the request corresponding to each page is the same, so the request identifier of the same page at each time may be the same, and the request identifiers of different pages are different. The specific setting rule may add an incremental datum as a unique identifier based on the class name of the page, or set a unique identifier for each page request, or a hash value of the class name, etc., which is not specifically limited herein, as long as the uniqueness of the request identifier can be ensured to distinguish each request.
In some examples, since a target task needs to correspond to a plurality of requests, each of the target tasks corresponds to at least one of the requests, in this case, since several requests can only implement execution of one target task, that is, when any one of the requests fails to be executed in time, a situation that the entire target task cannot be executed due to the failure of the request may occur, in order to cope with this situation, in this embodiment, an association relationship may be further set in the process of acquiring the attribute information, so that several requests having the association relationship can be subsequently executed at the same time or within the same time period, and therefore, before monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method may further include:
and setting an association list for each request, wherein the association list is used for storing request identifiers with association relations, and the association relations are determined based on the target tasks corresponding to the requests.
Specifically, the process of setting the association list may be: list < Uint64_ t > getidentificyidilist () -0; wherein, the aforementioned List < Uint64_ t > is the association List identifier, and getidentifiyidlist () is the interface of the request identifier, so that association based on the request identifier of each request can be realized to ensure that the execution is performed with the same priority.
The process of acquiring the request information in the operation page is actually executable through an existing monitoring program, so in some examples, monitoring the operation interface through a preset interface monitoring event, and acquiring the attribute information corresponding to the request in the operation interface may be specifically executed in the following manner, including:
firstly, setting a page attribute Class as Class PageInfo, wherein the page attribute Class is used for recording the page attribute of the request. Where this class may be inherited later when all pages or modules are monitored. Therefore, the setting of the page attribute Class is realized through the Class PageInfo, a foundation can be laid for subsequent monitoring, a corresponding monitoring script or function does not need to be constructed during each monitoring, and inheritance can be carried out based on the Class, so that the monitoring can be directly carried out.
Then, a request identification is defined for each of the aforementioned requests as Uint64_ t identifiyd.
Since the request identifier based on the request source is determined only for each request in the foregoing example, the request identifier may be defined by Uint64_ t identifiyd specifically at the function level in this step, which in turn facilitates attribute information marking of each request with the request identifier subsequently.
Finally, the unique identification of the current page must be passed in based on the constructor to achieve the effect of assigning values to the member variables. Therefore, calling the constructor of the page attribute class to execute assignment operation as PageInfo (Uint64_ t identifiyid): identifiyid _ (identifiyid), where PageInfo (Uint64_ t identifiyid) is the caller and identifid _ (identifid) is used to characterize assignment to member variables, and the function of the above statement can be to add the defined request identifier to the constructor to update the initial value to the value corresponding to the request identifier.
In the method, the target task which is influenced by the network and cannot be completed or fails to be executed can be directly obtained when the weak network or no network is detected in the process of changing the network state, so that the function of automatically obtaining the task with problems in the process of deteriorating the network state is realized, the operation process of obtaining the task which is not completed or fails to be executed due to the network reason does not need to be manually executed in the prior art, the operation process is simplified, and the user experience is improved.
In a specific embodiment, the event notification function is inherited and realized according to the previously set PageInfo class, and when an event exists in a page, a network library component is notified. That is, first the inheritance of the class, then the method Event that implements the class and notifies the web library in the method by acquiring a single instance object of the web library.
Class PlayerPage:public PageInfo{
The player page inherits from the previously defined page PageInfo class, so that the event notification function therein can be realized.
PlayerPage(Uint64_t IdentifyId):PageInfo(IdentifyId){}
The calling constructor passes in the unique identification of the current page (request identification). While the constructor of the base class is called to initialize the member variables.
Void Event(EventType e，Uint64_t IdentifyId){
Each page may then implement the event notification functionality therein. Event notification then includes page creation and page destruction, and notifies the web library.
EventType e＝CreateType；
And sets the event type to a create event type.
NetWork::Instance()->Notify(e,IdentifyId)；
Based on the above exemplary embodiment, since the playpage class of the player page is inherited to the page PageInfo class previously set in advance, based on the principle of the class, the inheritance of the previously preset class can directly call the related services and functions existing in the preset class, for example, the call of the function of Event notification can be directly performed by setting the vod Event. Therefore, it can be ensured that in the process of implementing the code deployment of the above functions, the related functions can be directly invoked through the code without considering code compilation such as specific monitoring, notification and the like, and the effect of reducing the workload of service personnel such as software engineers and the like can be realized in the implementation process of the embodiment.
102. And adding the target task to a task queue to be executed.
The task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priority.
In some examples, the method of this step may be embodied as: and generating target task information according to the attribute information, and adding the target task information into the task queue to be executed.
The steps are as follows: generating target task information and adding the target task information into a task queue to be executed, wherein the specific form can be as follows: generating a task list according to the request attribute, and adding the task list into the to-be-executed task queue, wherein the task list specifically comprises:
Struct Task{
RequestHeader；
RequestBody；；
IdentifyId；}
wherein the RequestHeader is the request header information, the RequestBody is the request body information, and the identifiyd is the request identifier.
According to the method, the effect of automatically adding the target task to the task queue to be executed can be achieved, and the task queue to be executed is a queue capable of executing the task when the network is recovered to be normal, so that a foundation can be laid for continuously executing the target task when the network is recovered in the follow-up process. Meanwhile, the process is automatically realized, so that manual adding operation for executing the target task is not needed, the operation process is simplified, and the user experience in the task execution process is better.
In fact, the task priority degrees of different tasks are different, for example, when a user operates the chat software on the interface, the task of the chat software has the highest priority, that is, the user operates the interface to influence the sequence of the subsequent steps in the task queue to be executed.
Based on this, in some examples, before the generating the target task information according to the attribute information and adding the target task information to the to-be-executed task queue, the method further includes:
and determining the task priority of each target task according to the operation behavior in the operation interface, wherein the task priority is determined according to the task type of the target task, the task type corresponds to the request operation of the request corresponding to the target task, and the task type comprises a page task, a module task, a video stream task and an associated request task.
Specifically, when the operation behavior is page operation, determining that the task priority of the target task corresponding to the page task is the highest;
when the operation behavior is module operation, determining that the task priority of the target task corresponding to the module task is the highest;
when the operation behavior is video stream operation, determining that the task priority of the target task corresponding to the video stream task is the highest;
and when the operation behavior is an operation corresponding to a plurality of the requests, determining that the priority of a target task corresponding to the association request task which has an association relation with the operation is the highest.
In this way, in this step, the generating target task information according to the attribute information and adding the target task information to the to-be-executed task queue may include: and arranging a plurality of target tasks according to the task priorities and adding the target tasks into the task queue to be executed, wherein the sequencing order in the task queue to be executed is positively correlated with the task priorities.
It should be noted that, the method described in this embodiment may be implemented by setting a task rearrangement interface, specifically: for example, set Class TaskAlgorithm { for interface implementations that need to define task re-ordering, so that other customized orderings can be implemented based on this interface. Then setting the Virtual void SortTask (List < Task > queue, stack < IdentifyId > pageid) to 0; this interface is then a function for implementing task re-ordering. The parameter queue is all tasks in the task queue, and the stack < identify id > pageid records all request identifiers stored in the network library, and in addition, a stacked storage request identifier may be used in the storage process. Based on the foregoing, the task rearrangement interface can implement the call of the task rearrangement function, that is, when it is determined that a plurality of target tasks need to be executed after the network is restored to normal, the ordering effect of the whole rearrangement of the order of the priority can be implemented, and the above manner is more efficient compared with the manner of "queue insertion" ordering in the original queue according to the task priority.
In addition, when determining which task has the highest priority according to different interface operation behaviors, the following process may be specifically performed:
for example, when the page task has the highest priority, that is, the page content is displayed in the current operation interface of the user, the target task information may be distinguished according to the type of the request identifier, and the target task corresponding to the page identifier may be selected from the target task information. Since there may be a case where the user operates multiple pages, the multiple target tasks with the highest priority may be sorted according to the page order in the operation interface. Because the pages are generally stored in a stack mode in the storage process, when the pages exit to the previous page, the requests corresponding to the pages are also sorted according to the exit mode of the pages, namely, in the process of utilizing the page identifiers stored in the stack mode, the page identifiers of the previous page are stored, then new page identifiers are stored, and when the current page is deleted, the next page identifier is the previous page identifier, so that the page identifiers are consistent with the sequence of the operation pages of the user.
Then, adding the target task in the to-be-executed task queue according to the priority order is executed through the following processes:
List<Task>*newqueue＝new List<Task>()；
this step is used to create a new task queue and initialize the empty queue.
For(id:pageid){
This step is used to traverse the page identification stack of the current stack.
For(task:queue){
This step is used to traverse the current task queue.
If(id＝＝task.IdentifyId){
This step is used to store the inter-task to the new queue, embed _ back (task), and it should be noted that the task needs to be put to the tail of the new queue, thereby ensuring that the task of the first page of the stack page is put to the head of the queue.
For(task:queue){newqueue.insert(newqueue.begin(),task)；}
The step is used for setting the target task corresponding to the non-page identification behind the target task corresponding to the first page identification and before the target tasks corresponding to other pages.
In addition, when the Task priority of the target Task corresponding to the module Task is the highest, it indicates that there is no page currently, when the program is started, the page element itself is not changed, or the Task priority of the module is higher, in this case, the Task sorting function can be implemented by setting a Task re-arrangement interface Class modular Task { void software Task (List < Task >) queue, stack < identify > page id }. Meanwhile, when the task priority of the target task corresponding to the video stream task is the highest and the priority of the target task corresponding to the association request task having an association relation with the operation is the highest, the target task sorting based on the priority can be performed by using the above method.
103. And when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
Because the network state is recovered to be normal and the target tasks in the task queue to be executed are arranged according to the priority sequence before the process of executing the target tasks, the task in the user operation interface can be preferentially executed in the sequence with the highest priority, the user can know that the current network is recovered to be normal through the execution of the target tasks when the network is recovered, the function of automatically executing the target tasks is not required to be operated by the user, and the task execution process is simplified.
When the network state is no network or weak network, acquiring a target task; then, adding the target task into a task queue to be executed; and finally, when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence. In the above scheme, the target tasks are uncompleted tasks and failed tasks under the influence of network factors, the weak network is a network state when the network connection quality is lower than a preset connection quality threshold, the network state is obtained by monitoring the network operation condition, the task queue to be executed contains a plurality of the target tasks, and the target tasks in the task queue to be executed are sorted according to task priorities. Based on the method of the scheme, when the network state is no network or weak network, the task which is not executed or failed due to network influence can be added into the task queue to be executed, and when the network state is recovered to be network normal, the task in the task queue to be executed is executed, so that the task which is not executed originally can be automatically re-executed after the network is recovered from poor condition to normal condition, the effect of automatically re-executing the task which is influenced by the network and is not normally executed can be realized without manual operation after the network is recovered, the task execution process can be simplified, and the user experience is improved. In addition, in the above scheme, since the target tasks can be executed according to the order of the priorities when the network state is normal, it can be ensured that the target tasks are executed in the order of the priorities when a plurality of target tasks need to be executed, so that when the task in the interface operated by the user is the highest priority, the network state can be preferentially executed once the network state is recovered to the normal state, the user can know that the network state is recovered at the first time, and then the effect of laterally reminding the user of the change situation of the network state is achieved.
The task execution method in the embodiment of the present application is described above, and the task execution device in the embodiment of the present application is described below.
Referring to fig. 2, in an embodiment of the task performing device of the present application, the task performing device includes:
the acquiring unit 21 may be configured to acquire a target task when a network state is a network-free state or a weak network state, where the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is a network state when network connection quality is lower than a preset connection quality threshold, and the network state is obtained by monitoring a network operation condition;
the adding unit 22 may be configured to add the target task to a to-be-executed task queue, where the to-be-executed task queue includes a plurality of target tasks, and the target tasks in the to-be-executed task queue are sorted according to task priorities;
the executing unit 23 may be configured to execute the target tasks of the to-be-executed task queue according to the task priority order when the network status is network normal.
Referring to fig. 3, fig. 3 is a schematic view of an embodiment of an electronic device according to an embodiment of the present disclosure.
As shown in fig. 3, an electronic device according to an embodiment of the present application includes a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor 320, where the processor 320 executes the computer program 311 to implement the following steps: when the network state is a non-network or weak network, acquiring a target task, wherein the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is the network state when the network connection quality is lower than a preset connection quality threshold, and the network state is obtained by monitoring the network operation condition; adding the target tasks into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priorities; and when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
Optionally, in some embodiments, the processor 320 is specifically configured to: when the network state is no network or weak network, the target task is obtained, including:
monitoring the operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface, wherein the attribute information comprises a request identifier, request header information and request body information, and the request identifier is information preset for distinguishing the request;
the adding the target task to the to-be-executed task queue includes:
and generating target task information according to the attribute information, and adding the target task information into the task queue to be executed.
Optionally, in some embodiments, the processor 320 is specifically configured to: before the monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further includes:
the method comprises the steps of judging a request source of a request in the operation interface, and adding a request identifier corresponding to the request source for the request, wherein the request identifier comprises a page identifier and a module identifier, the page identifier is used for representing that the request is sent based on page operation, the module identifier is used for representing that the request is sent based on a program module, and the program module comprises a live program module.
Optionally, in some embodiments, the processor 320 is specifically configured to: each of the aforementioned target tasks corresponds to at least one of the aforementioned requests;
before the monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further includes:
and setting an association list for each request, wherein the association list is used for storing request identifiers with association relations, and the association relations are determined based on the target tasks corresponding to the requests.
Optionally, in some embodiments, the processor 320 is specifically configured to: the monitoring of the operation interface through the preset interface monitoring event, and the obtaining of the attribute information corresponding to the request in the operation interface includes:
setting a page attribute Class as Class PageInfo, wherein the page attribute Class is used for recording the page attribute of the request;
defining a request identification for each of the aforementioned requests as Uint64_ t identifiyd;
calling the constructor of the page attribute class to execute assignment operation as PageInfo (Uint64_ t IdentityId) and IdentityId (IdentityId), wherein PageInfo (Uint64_ t IdentityId) is a caller, IdentityId (IdentityId) is used for representing assignment to the member variable PageInfo (Uint64_ t IdentityId) as a caller, and IdentityId (IdentityId) is used for representing assignment to the member variable, and the assignment operation is used for adding the defined request identifier to the constructor so as to update the initial value to the value corresponding to the request identifier.
Optionally, in some embodiments, the processor 320 is specifically configured to: the adding the target task to the to-be-executed task queue includes:
generating a task list according to the request attribute, and adding the task list into the to-be-executed task queue, wherein the task list specifically comprises:
Struct Task{
RequestHeader；
RequestBody；；
IdentifyId；}
wherein the RequestHeader is the request header information, the RequestBody is the request body information, and the identifiyd is the request identifier.
Optionally, in some embodiments, the processor 320 is specifically configured to: before the aforementioned target task is added to the task queue to be executed, the aforementioned method further includes:
determining a task priority of each target task according to the operation behavior in the operation interface, wherein the task priority is determined according to a task type of the target task, the task type corresponds to the requested operation of the request corresponding to the target task, and the task type comprises a page task, a module task, a video stream task and an associated request task;
when the operation behavior is page operation, determining that the task priority of the target task corresponding to the page task is the highest;
when the operation behavior is module operation, determining that the task priority of the target task corresponding to the module task is the highest;
when the operation behavior is video stream operation, determining that the task priority of the target task corresponding to the video stream task is the highest;
when the operation behavior is an operation corresponding to a plurality of the requests, determining that the priority of a target task corresponding to the association request task which has an association relation with the operation is the highest;
the adding the target task to the to-be-executed task queue includes:
and arranging a plurality of target tasks according to the task priorities and adding the target tasks into the task queue to be executed, wherein the sequencing order in the task queue to be executed is positively correlated with the task priorities.
As shown in fig. 4, the present embodiment provides a computer-readable storage medium 400, on which a computer program 411 is stored, the computer program 411 implementing the following steps when executed by a processor: when the network state is a non-network or weak network, acquiring a target task, wherein the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is the network state when the network connection quality is lower than a preset connection quality threshold, and the network state is obtained by monitoring the network operation condition; adding the target tasks into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priorities; and when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
Optionally, in a possible embodiment, the computer program 411 is specifically adapted to, when executed by a processor: when the network state is no network or weak network, the target task is obtained, including:
monitoring the operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface, wherein the attribute information comprises a request identifier, request header information and request body information, and the request identifier is information preset for distinguishing the request;
the adding the target task to the to-be-executed task queue includes:
and generating target task information according to the attribute information, and adding the target task information into the task queue to be executed.
Optionally, in a possible embodiment, the computer program 411 is specifically adapted to, when executed by a processor: before the monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further includes:
the method comprises the steps of judging a request source of a request in the operation interface, and adding a request identifier corresponding to the request source for the request, wherein the request identifier comprises a page identifier and a module identifier, the page identifier is used for representing that the request is sent based on page operation, the module identifier is used for representing that the request is sent based on a program module, and the program module comprises a live program module.
Alternatively, in a possible embodiment, the computer program 411 is specifically adapted, when executed by a processor, to: each of the aforementioned target tasks corresponds to at least one of the aforementioned requests;
before the monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further includes:
and setting an association list for each request, wherein the association list is used for storing request identifiers with association relations, and the association relations are determined based on the target tasks corresponding to the requests.
Optionally, in a possible embodiment, the computer program 411 is specifically adapted to, when executed by a processor: the monitoring of the operation interface through the preset interface monitoring event, and the obtaining of the attribute information corresponding to the request in the operation interface includes:
setting a page attribute Class as Class PageInfo, wherein the page attribute Class is used for recording the page attribute of the request;
defining a request identification for each of the aforementioned requests as Uint64_ t identifiyd;
calling the constructor of the page attribute class to execute assignment operation as PageInfo (Uint64_ t IdentityId) and IdentityId (IdentityId), wherein PageInfo (Uint64_ t IdentityId) is a caller, IdentityId (IdentityId) is used for representing assignment to the member variable PageInfo (Uint64_ t IdentityId) as a caller, and IdentityId (IdentityId) is used for representing assignment to the member variable, and the assignment operation is used for adding the defined request identifier to the constructor so as to update the initial value to the value corresponding to the request identifier.
Optionally, in a possible embodiment, the computer program 411 is specifically adapted to, when executed by a processor: the adding the target task to the to-be-executed task queue includes:
generating a task list according to the request attribute, and adding the task list into the to-be-executed task queue, wherein the task list specifically comprises:
Struct Task{
RequestHeader；
RequestBody；；
IdentifyId；}
wherein the RequestHeader is the request header information, the RequestBody is the request body information, and the identifiyd is the request identifier.
Optionally, in a possible embodiment, the computer program 411 is specifically adapted to, when executed by a processor: before the aforementioned target task is added to the task queue to be executed, the aforementioned method further includes:
determining a task priority of each target task according to the operation behavior in the operation interface, wherein the task priority is determined according to a task type of the target task, the task type corresponds to the requested operation of the request corresponding to the target task, and the task type comprises a page task, a module task, a video stream task and an associated request task;
when the operation behavior is page operation, determining that the task priority of the target task corresponding to the page task is the highest;
when the operation behavior is module operation, determining that the task priority of the target task corresponding to the module task is the highest;
when the operation behavior is video stream operation, determining that the task priority of the target task corresponding to the video stream task is the highest;
when the operation behavior is an operation corresponding to a plurality of the requests, determining that the priority of a target task corresponding to the association request task which has an association relation with the operation is the highest;
the aforementioned adding the target task to the to-be-executed task queue includes:
and arranging a plurality of target tasks according to the task priorities and adding the target tasks into the task queue to be executed, wherein the sequencing order in the task queue to be executed is positively correlated with the task priorities.
It should be noted that, steps of the task execution method executed by the apparatus, the processor, and the electronic device are all consistent with those of the method and steps corresponding to fig. 1 in the foregoing method embodiment, and are not described in detail herein.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
For another example, the division of the above-mentioned units is only one logical function division, and there may be other division manners in actual implementation, and for another example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some communication interfaces, indirect coupling or communication connection between devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments provided by the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The above functions, if implemented in the form of software functional units and sold or used as a separate product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above-mentioned embodiments are merely specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; and the modifications, changes or substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention. Are intended to be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method of task execution, comprising the steps of:
when the network state is a network-free state or a weak network state, acquiring a target task, wherein the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is the network state when the network connection quality is lower than a preset connection quality threshold, and the network state is obtained by monitoring the network operation condition;
adding the target task into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priority;
and when the network state is the network normal state, executing the target tasks of the task queue to be executed according to the task priority sequence.
2. The task execution method of claim 1, wherein the obtaining the target task when the network status is no network or weak network comprises:
monitoring an operation interface through a preset interface monitoring event, and acquiring attribute information corresponding to a request in the operation interface, wherein the attribute information comprises a request identifier, request header information and request body information, and the request identifier is preset information for distinguishing the request;
the adding the target task to a task queue to be executed comprises:
and generating target task information according to the attribute information, and adding the target task information into the task queue to be executed.
3. The task execution method according to claim 2, wherein before the monitoring of the operation interface through the preset interface and the acquisition of the attribute information corresponding to the request in the operation interface, the method further comprises:
the method comprises the steps of judging a request source of a request in the operation interface, and adding a request identifier corresponding to the request source for the request, wherein the request identifier comprises a page identifier and a module identifier, the page identifier is used for representing that the request is sent based on page operation, the module identifier is used for representing that the request is sent based on a program module, and the program module comprises a live program module.
4. The task execution method of claim 2, wherein each of the target tasks corresponds to at least one of the requests;
before monitoring the operation interface through the preset interface monitoring event and acquiring the attribute information corresponding to the request in the operation interface, the method further comprises the following steps:
and setting an association list for each request, wherein the association list is used for storing request identifiers with association relations, and the association relations are determined based on the target tasks corresponding to the requests.
5. The task execution method according to claim 1, wherein the monitoring of the operation interface through the preset interface event, and the obtaining of the attribute information corresponding to the request in the operation interface, comprises:
setting a page attribute Class as Class PageInfo, wherein the page attribute Class is used for recording the page attribute of the request;
defining a request identity for each of said requests as Uint64_ t identifiyd;
and calling the constructor of the page attribute class to execute assignment operation, wherein the assignment operation is PageInfo (Uint64_ t IdentityId) and IdentityId (IdentityId), the PageInfo (Uint64_ t IdentityId) is a caller, the IdentityIdentityId (IdentityId) is used for representing assignment to member variables, and the assignment operation is used for adding the defined request identifier to the constructor so as to update the initial value to the value corresponding to the request identifier.
6. The task execution method according to claim 4, wherein the generating target task information according to the attribute information and adding the target task information to the to-be-executed task queue comprises:
and generating a task list according to the request attribute, and adding the task list into the to-be-executed task queue, wherein the task list specifically comprises the request header information RequestHeader, the request body information RequestBody and the request identifier IdentifyId.
7. The task execution method according to claims 2 to 6, wherein before the generating target task information according to the attribute information and adding the target task information to the to-be-executed task queue, the method further comprises:
determining a task priority of each target task according to an operation behavior in the operation interface, wherein the task priority is determined according to a task type of the target task, the task type corresponds to the requested operation corresponding to the target task, and the task type comprises a page task, a module task, a video stream task and an associated request task;
when the operation behavior is page operation, determining that the task priority of the target task corresponding to the page task is the highest;
when the operation behavior is module operation, determining that the task priority of the target task corresponding to the module task is the highest;
when the operation behavior is video stream operation, determining that the task priority of the target task corresponding to the video stream task is the highest;
when the operation behavior is an operation corresponding to a plurality of requests, determining that the priority of a target task corresponding to the association request task having an association relation with the operation is the highest;
generating target task information according to the attribute information, and adding the target task information to the to-be-executed task queue, wherein the generating of the target task information according to the attribute information comprises the following steps:
and arranging a plurality of target tasks according to the task priorities and adding the target task information into the to-be-executed task queue, wherein the sequencing order in the to-be-executed task queue is positively correlated with the task priorities.
8. A task execution apparatus, comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a target task when a network state is a network-free or weak network, the target task is an uncompleted task and a failed task under the influence of network factors, the weak network is a network state when the network connection quality is lower than a preset connection quality threshold value, and the network state is obtained by monitoring the network operation condition;
the adding unit is used for adding the target tasks into a task queue to be executed, wherein the task queue to be executed comprises a plurality of target tasks, and the target tasks in the task queue to be executed are sorted according to task priority;
and the execution unit is used for executing the target tasks of the task queue to be executed according to the task priority sequence when the network state is the network normal state.
9. An electronic device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor is adapted to carry out the steps of the task execution method according to any of claims 1 to 7 when executing the computer program stored in the memory.
10. A computer-readable storage medium having stored thereon a computer program, characterized in that: the computer program realizing the steps of the task execution method according to any of claims 1-7 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011407769.7A CN114598664A (en) | 2020-12-03 | 2020-12-03 | Task execution method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011407769.7A CN114598664A (en) | 2020-12-03 | 2020-12-03 | Task execution method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114598664A true CN114598664A (en) | 2022-06-07 |
Family
ID=81802948
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011407769.7A Pending CN114598664A (en) | 2020-12-03 | 2020-12-03 | Task execution method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114598664A (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6252681B1 (en) * | 1997-04-14 | 2001-06-26 | Xerox Corporation | Multifunctional printing system with queue management |
| US20070291647A1 (en) * | 2006-06-19 | 2007-12-20 | Harris Corporation | Method and System for Fault-Tolerant Quality of Service |
| WO2008037161A1 (en) * | 2006-09-29 | 2008-04-03 | Huawei Technologies Co., Ltd. | A service restoring method and device |
| CN101410803A (en) * | 2006-01-24 | 2009-04-15 | 思杰系统有限公司 | Methods and systems for providing access to a computing environment |
| CN101888603A (en) * | 2010-03-22 | 2010-11-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, device and mobile terminal for sending and receiving multimedia message |
| CN102571568A (en) * | 2011-12-27 | 2012-07-11 | 北京奇虎科技有限公司 | Method and device for processing task |
| CN103139307A (en) * | 2013-02-27 | 2013-06-05 | 广东欧珀移动通信有限公司 | Recovery method for network resource downloading after interruption and downloading system |
| CN103403631A (en) * | 2011-03-15 | 2013-11-20 | 欧姆龙株式会社 | CPU of PLC, system program for PLC, and recording medium storing system program for PLC |
| CN103516796A (en) * | 2013-09-26 | 2014-01-15 | 深圳酷派技术有限公司 | Data processing method and system in weak signal situation |
| JP2017098894A (en) * | 2015-11-27 | 2017-06-01 | 日本電信電話株式会社 | Network management device, recovery procedure determination method and program |
| CN107040816A (en) * | 2017-03-17 | 2017-08-11 | 北京潘达互娱科技有限公司 | A kind of client application operation exception analysis method and device |
| CN107360207A (en) * | 2017-05-26 | 2017-11-17 | 腾讯科技（深圳）有限公司 | Submit method, interface issuing means, storage medium and electronic installation in interface |
| CN110413390A (en) * | 2019-07-24 | 2019-11-05 | 深圳市盟天科技有限公司 | Thread task processing method, device, server and storage medium |
| CN110839055A (en) * | 2018-08-17 | 2020-02-25 | 菜鸟智能物流控股有限公司 | Task processing method, device and system |
| CN110895483A (en) * | 2018-09-12 | 2020-03-20 | 北京奇虎科技有限公司 | Task recovery method and device |
| CN111757037A (en) * | 2020-06-19 | 2020-10-09 | 杭州海康威视数字技术股份有限公司 | Video file reading and writing method and device |
| US20200364179A1 (en) * | 2019-05-16 | 2020-11-19 | Commvault Systems, Inc. | Fast recall of large archived files |
| US20200374180A1 (en) * | 2019-05-20 | 2020-11-26 | Samsung Electronics Co., Ltd. | Methods and systems for recovery of network elements in a communication network |
-
2020
- 2020-12-03 CN CN202011407769.7A patent/CN114598664A/en active Pending
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6252681B1 (en) * | 1997-04-14 | 2001-06-26 | Xerox Corporation | Multifunctional printing system with queue management |
| CN101410803A (en) * | 2006-01-24 | 2009-04-15 | 思杰系统有限公司 | Methods and systems for providing access to a computing environment |
| US20070291647A1 (en) * | 2006-06-19 | 2007-12-20 | Harris Corporation | Method and System for Fault-Tolerant Quality of Service |
| WO2008037161A1 (en) * | 2006-09-29 | 2008-04-03 | Huawei Technologies Co., Ltd. | A service restoring method and device |
| CN101888603A (en) * | 2010-03-22 | 2010-11-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, device and mobile terminal for sending and receiving multimedia message |
| CN103403631A (en) * | 2011-03-15 | 2013-11-20 | 欧姆龙株式会社 | CPU of PLC, system program for PLC, and recording medium storing system program for PLC |
| CN102571568A (en) * | 2011-12-27 | 2012-07-11 | 北京奇虎科技有限公司 | Method and device for processing task |
| CN103139307A (en) * | 2013-02-27 | 2013-06-05 | 广东欧珀移动通信有限公司 | Recovery method for network resource downloading after interruption and downloading system |
| CN103516796A (en) * | 2013-09-26 | 2014-01-15 | 深圳酷派技术有限公司 | Data processing method and system in weak signal situation |
| JP2017098894A (en) * | 2015-11-27 | 2017-06-01 | 日本電信電話株式会社 | Network management device, recovery procedure determination method and program |
| CN107040816A (en) * | 2017-03-17 | 2017-08-11 | 北京潘达互娱科技有限公司 | A kind of client application operation exception analysis method and device |
| CN107360207A (en) * | 2017-05-26 | 2017-11-17 | 腾讯科技（深圳）有限公司 | Submit method, interface issuing means, storage medium and electronic installation in interface |
| CN110839055A (en) * | 2018-08-17 | 2020-02-25 | 菜鸟智能物流控股有限公司 | Task processing method, device and system |
| CN110895483A (en) * | 2018-09-12 | 2020-03-20 | 北京奇虎科技有限公司 | Task recovery method and device |
| US20200364179A1 (en) * | 2019-05-16 | 2020-11-19 | Commvault Systems, Inc. | Fast recall of large archived files |
| US20200374180A1 (en) * | 2019-05-20 | 2020-11-26 | Samsung Electronics Co., Ltd. | Methods and systems for recovery of network elements in a communication network |
| CN110413390A (en) * | 2019-07-24 | 2019-11-05 | 深圳市盟天科技有限公司 | Thread task processing method, device, server and storage medium |
| CN111757037A (en) * | 2020-06-19 | 2020-10-09 | 杭州海康威视数字技术股份有限公司 | Video file reading and writing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109873804A (en) | Service identification method, device, equipment and the readable storage medium storing program for executing of Behavior-based control | |
| CN108762911A (en) | Timing task management method, apparatus, computer equipment and storage medium | |
| CN110826799B (en) | Service prediction method, device, server and readable storage medium | |
| CN110442502B (en) | Point burying method, device, equipment and storage medium | |
| CN104199654A (en) | Open platform calling method and device | |
| CN111258913A (en) | Automatic algorithm testing method and device, computer system and readable storage medium | |
| CN107818028A (en) | A kind of computer data backup and restoring method | |
| CN112799925A (en) | Data acquisition method and device, electronic equipment and readable storage medium | |
| CN111259382A (en) | Malicious behavior identification method, device and system and storage medium | |
| CN107526636B (en) | Resource identification method and device | |
| CN111597553A (en) | Process processing method, device, equipment and storage medium in virus searching and killing | |
| CN112691365B (en) | Cloud game loading method, system, device, storage medium and cloud game system | |
| CN111639316B (en) | Information processing method and device for WEB page | |
| CN111913743B (en) | Data processing method and device | |
| CN110119429B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN115640066A (en) | Security detection method, device, equipment and storage medium | |
| CN114598664A (en) | Task execution method and related device | |
| CN111277626A (en) | Server upgrading method and device, electronic equipment and medium | |
| CN115237441A (en) | Upgrade test method, device and medium based on cloud platform | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN114328196A (en) | Method, device and equipment for testing data leakage prevention system and storage medium | |
| CN112256295A (en) | Application program updating method, device, equipment and storage medium | |
| CN108650544B (en) | Media playing method, device and system | |
| CN108829824B (en) | Resource processing method and device in internet operation activity |
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 |