CN114745441A - Identify task scheduling methods and scheduling components - Google Patents

Abstract

The present disclosure provides an authentication task scheduling method, applied to a scheduling component, comprising: receiving a task acquisition request from at least one authenticator; acquiring at least one authentication task from a server according to the task acquisition request of the at least one authenticator, and obtaining the object to be authenticated associated with each of the authentication tasks; for each of the authenticators, according to a task claim request of the authenticator, assigning an authentication task to the authenticator, so that the authenticator is assigned an authentication task based on the The identification task is obtained, and the object to be identified associated with the assigned identification task is obtained from the scheduling component. The present disclosure also provides an authentication task scheduling component, an electronic device, and a computer-readable storage medium.

Description

Identify task scheduling methods and scheduling components

technical field

The present disclosure relates to the field of network security, and in particular, to an authentication task scheduling method, an authentication task scheduling component, an electronic device, a computer-readable storage medium, and a computer program product.

Background technique

With the rapid development of computer technology, network security issues have been paid more and more attention. Using an authenticator to authenticate network data is an important means to identify whether there is a security risk in network data.

In the process of realizing the inventive concept of the present disclosure, the inventor found that in the related art, when using an authenticator to perform an authentication task, multiple authenticators in the same machine obtain the authentication task from the server, and obtain the object to be authenticated associated with the authentication task. However, this identification task execution method has the problems of large consumption of bandwidth resources and low identification efficiency.

SUMMARY OF THE INVENTION

One aspect of the present disclosure provides an authentication task scheduling method, applied to a scheduling component, comprising: receiving a task acquisition request from at least one authenticator; and obtaining at least one task acquisition request from a server according to the task acquisition request of the at least one authenticator Identifying tasks, and obtaining the objects to be identified associated with each of the identifying tasks; for each of the identifying devices, assigning an identifying task to the identifying device according to the identifying device's task receiving request, so that the identifying device Based on the assigned authentication task, the to-be-authenticated object associated with the assigned authentication task is obtained from the scheduling component.

Optionally, when acquiring the object to be authenticated associated with each of the authentication tasks, it includes: determining whether there is an object that is the same as the object to be authenticated to be acquired in the local cache; if so, using the locally cached object as the Describe the object to be identified.

Optionally, the obtaining at least one appraisal task from the server according to the task claim request of the at least one appraiser includes: according to the data received within a preset time period since the previous obtaining of the appraisal task from the server. For the task acquisition request of the at least one authenticator, at least one authentication task is obtained from the server.

Optionally, obtaining at least one appraisal task from the server according to a task claim request of the at least one appraiser received within a preset time period since the appraisal task was obtained from the server last time, comprising: : Determine the number of appraisal tasks and the type of appraisal tasks requested by each of the appraisers according to the task claim requests of the appraisers received within the preset duration; The authentication task type is obtained, and at least one authentication task is obtained from the server.

Optionally, determining the number of appraisal tasks requested by each of the appraisers according to the task claim requests of the appraisers received within the preset time period includes: when receiving the request within the preset time period In the case of multiple task claim requests from the same appraiser, the maximum number of appraisal tasks indicated in the multiple task claim requests is taken as the number of appraisal tasks requested by the appraiser.

Optionally, the method further includes: establishing a memory instance associated with each of the appraisers; and assigning an appraisal task to the appraiser according to a task acquisition request of the appraiser, comprising: according to the appraiser's In the task acquisition request, the identification task to be allocated to the authenticator is determined; and the authentication task to be allocated is stored in a memory instance associated with the authenticator.

Optionally, the method further includes: receiving heartbeat information sent by the identifier at a preset frequency; and, when the heartbeat information of a certain identifier is not received within a preset time period, determining the identifier Exception; deletes the memory instance associated with the exception identifier.

Optionally, the method further includes: establishing a memory instance associated with each object to be authenticated; and when it is determined that the object to be authenticated has been scanned by all associated authenticators, or it is determined that the object to be authenticated is in the scheduler When the cache time in the component exceeds a preset threshold, the memory instance associated with the object to be authenticated is deleted.

Optionally, the method further includes: receiving the appraisal results returned by each of the appraisers; summarizing the appraisal results of each of the appraisers for the same appraisal task; returning the summarized appraisal results for each of the appraisal tasks to the all appraisal tasks. mentioned server.

Optionally, the authenticator and the scheduling component are located in the same operating environment.

Another aspect of the present disclosure provides an appraisal task scheduling method, applied to an appraiser, comprising: sending a task claim request to the scheduling component; acquiring from the scheduling component an appraisal task assigned based on the task claim request , and obtain the object to be authenticated associated with the assigned authentication task; perform an authentication operation on the object to be authenticated, and return the obtained authentication result to the scheduling component.

Optionally, the scheduling component establishes a memory instance associated with the authenticator; the obtaining, from the scheduling component, the authentication task assigned based on the task claim request includes: obtaining from the scheduling component associating with the authenticator The memory instance of the assigned authentication task is obtained.

Optionally, the scheduling component establishes a memory instance associated with the object to be authenticated; the acquiring the object to be authenticated associated with the assigned authentication task includes: from the memory associated with the object to be authenticated The object to be authenticated is obtained in an instance.

Optionally, heartbeat information is sent to the scheduling component at a preset frequency.

Another aspect of the present disclosure provides an authentication task scheduling component, comprising: an authenticator management module, an authentication task management module and an object to be authenticated management module, each of which is communicatively connected, wherein the authentication The appraiser management module is used for receiving the task claim request from at least one appraiser; the appraisal task management module is used for obtaining at least one appraisal task from the server according to the task claim request of the at least one appraiser, and for each appraiser The appraiser assigns an appraisal task to the appraiser according to the task receiving request of the appraiser; Based on the assigned identification task, the controller acquires the object to be authenticated associated with the assigned identification task from the object management module to be authenticated.

Optionally, the acquiring the object to be authenticated associated with each of the authentication tasks includes: the object to be authenticated management module determines whether there is a local cache of the same object as the to-be-authenticated object to be acquired; The cached object is used as the object to be authenticated.

Optionally, the obtaining at least one appraisal task from the server according to the task claim request of the at least one appraiser includes: the appraisal task management module according to the previous acquisition of the appraisal task from the server. The at least one authentication task is acquired from the server according to the task acquisition request of the at least one authenticator received by the authenticator management module within a preset time period.

Optionally, the appraiser management module determines the number of appraisal tasks and the appraisal task type requested by each appraiser according to the task claim request of each appraiser received within the preset duration; the appraisal task The management module acquires at least one authentication task from the server according to the number of authentication tasks and the type of authentication tasks requested by each authenticator determined by the authenticator management module.

Optionally, the determining the number of appraisal tasks requested by each of the appraisers according to the task claim request of each of the appraisers received within the preset time period includes: the appraiser management module is in the preset time period. When multiple task claim requests from the same appraiser are received within the set time period, the maximum number of appraisal tasks indicated in the multiple task claim requests is taken as the number of appraisal tasks requested by the appraiser.

Optionally, the authenticator management module is further configured to establish a memory instance associated with each of the authenticators; the assigning an authentication task to the authenticator according to a task claim request of the authenticator, including: the The appraisal task management module determines the appraisal task to be allocated to the appraiser according to the task claim request of the appraiser, and stores the appraisal task to be allocated in a memory instance associated with the appraiser.

Optionally, the identifier management module is further configured to: receive the heartbeat information sent by the identifier at a preset frequency; and, when the heartbeat information of a certain identifier is not received within a preset duration, The identifier is determined to be anomalous, and the memory instance associated with the anomaly identifier is deleted.

Optionally, the to-be-authenticated object management module is further configured to: establish a memory instance associated with each of the to-be-authenticated objects; When the cache time of the object to be authenticated exceeds a preset threshold, the memory instance associated with the object to be authenticated is deleted.

Optionally, the appraiser management module is further configured to: receive the appraisal results returned by the appraisers; summarize the appraisal results of the appraisers for the same appraisal task; The authentication result is returned to the server.

Optionally, the authenticator and the scheduling component are located in the same operating environment.

Another aspect of the present disclosure provides an authentication task processing system, including: a server, an authenticator, and a scheduling component of an embodiment of the present disclosure, wherein the authenticator and the scheduling component are located in the same operating environment.

Another aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more programs When executed by the processor, the one or more processors are caused to implement the methods of the embodiments of the present disclosure.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are used to implement methods of embodiments of the present disclosure.

Another aspect of the present disclosure provides a computer program product comprising computer-readable instructions, wherein the computer-readable instructions, when executed, are used to perform a method of an embodiment of the present disclosure.

Description of drawings

For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 schematically shows the system architecture of the method and apparatus for scheduling an authentication task according to an embodiment of the present disclosure;

FIG. 2 schematically shows a flowchart of a method for scheduling identification tasks according to an embodiment of the present disclosure;

FIG. 3 schematically shows a schematic diagram of an authentication task scheduling process according to an embodiment of the present disclosure;

FIG. 4 schematically shows a flowchart of a method for obtaining an authentication task according to an embodiment of the present disclosure;

FIG. 5 schematically shows a flowchart of another authentication task scheduling method according to an embodiment of the present disclosure;

6A schematically shows a schematic structural diagram of an identification task processing system in the related art;

FIG. 6B schematically shows a schematic structural diagram of an authentication task processing system according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a block diagram of an authentication task scheduling component according to an embodiment of the present disclosure; and

FIG. 8 schematically shows a block diagram of an electronic device according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood, however, that these descriptions are exemplary only, and are not intended to limit the scope of the present disclosure. In the following detailed description, for convenience of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It will be apparent, however, that one or more embodiments may be practiced without these specific details. Also, in the following description, descriptions of well-known structures and techniques are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. The terms "comprising", "comprising" and the like used herein indicate the presence of features, steps, operations and/or components, but do not preclude the presence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. It should be noted that terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly rigid manner.

Where expressions like "at least one of A, B, and C, etc.," are used, they should generally be interpreted in accordance with the meaning of the expression as commonly understood by those skilled in the art (eg, "has A, B, and C") At least one of the "systems" shall include, but not be limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc. ).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some of the blocks in the block diagrams and/or flowcharts, or combinations thereof, can be implemented by computer program instructions. The computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, when executed by the processor, may be created to implement the functions illustrated in the block diagrams and/or flow diagrams /Operating the device. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). Additionally, the techniques of the present disclosure may take the form of a computer program product on a computer-readable storage medium having stored instructions for use by or in conjunction with an instruction execution system.

Embodiments of the present disclosure provide a method for scheduling an authentication task and an operating device capable of applying the method. For example, the method may include the following operations. First, receive a task acquisition request from at least one authenticator, and, according to the task acquisition request from at least one authenticator, acquire at least one authentication task from the server, and acquire the object to be authenticated associated with each authentication task, and then, for each authentication task An appraiser assigns an appraisal task to the appraiser according to the appraiser's task receiving request, so that the appraiser obtains the object to be appraised associated with the assigned appraisal task from the scheduling component based on the assigned appraisal task.

FIG. 1 schematically shows a system architecture of an authentication task scheduling method and apparatus according to an embodiment of the present disclosure. It should be noted that FIG. 1 is only an example of a system architecture to which the embodiments of the present disclosure can be applied, so as to help those skilled in the art to understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used for other A device, system, environment or scene.

As shown in FIG. 1 , the system architecture 100 includes: at least one terminal (a plurality of terminals are shown in the figure, such as terminals 101 , 102 and 103 ), a network 104 and a server 105 . The network 104 is used to provide a communication link between the terminals (eg, terminals 101, 102, 103) and the server 105, and the network 104 may include various connection types including, for example, wireless communication links, wired communication links, fiber optic cables, and the like. The server 105 provides an authentication service in response to a user's service request. One server may provide one or more authentication services, and the same authentication service may also be performed by multiple servers. Exemplarily, the server 105 is a cloud server, and the authentication services it can provide include at least a cloud detection service, a malicious code authentication service, a file reputation determination service, and the like.

In the system architecture 100, terminals (eg, terminals 101, 102, 103) are provided with scheduling components (eg, scheduling components 101A) and identifiers (eg, identifiers 101B, 101C, 101D). The scheduling component (eg, scheduling component 101A) receives a task claim request from at least one appraiser (eg, appraiser 101B, 101C, 101D) in the same terminal, and obtains at least one from the server 105 according to the task claim request of the at least one appraiser Identifying tasks, and obtaining the objects to be identified associated with each identification task, and then for each appraiser, the scheduling component assigns the identification task to the appraiser according to the task receiving request of the appraiser, so that the appraiser is based on the assigned identification task, Obtain the object to be authenticated associated with the assigned authentication task from the scheduling component.

It should be noted that FIG. 1 is only an example of a system architecture to which the embodiments of the present disclosure can be applied, so as to help those skilled in the art to understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used for other system structure.

The present disclosure will be described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 2 schematically shows a flow chart of a method for scheduling an identification task according to an embodiment of the present disclosure, where the method is applied to a scheduling component.

As shown in FIG. 2, the method 200 may include operations S210-S230.

In operation S210, a task claim request from at least one authenticator is received.

In the embodiment of the present disclosure, specifically, the scheduling component and the authenticator are located in the same operating environment, and more specifically, the scheduling component and the authenticator are located in the same terminal. According to the different features based on the identification method, the identifiers can include static feature-based identifiers, dynamic feature-based identifiers, and comprehensive identifiers. The static features may include, for example, information such as file name, file version, file length, file type, program version, program form, and number of APIs (application programming interfaces). Dynamic features may include, for example, self-starting behavior, process hiding behavior, communication hiding behavior, registry automatic loading behavior, registry modification behavior, system file modification behavior, recording keyboard operation behavior, behavior of modifying web page content in the browser, modification of Execute the behavior of the application file, etc.

The scheduling component receives heartbeat information sent by each authenticator at a preset frequency, for example, receiving a ping request sent by each authenticator at a preset frequency. When the scheduling component receives a ping request from an authenticator for the first time, the scheduling component creates a memory instance for the authenticator, and the memory instance includes the same information as the actual operation information of the authenticator. When the heartbeat information of a certain authenticator is not received within a preset time period, the scheduling component determines that the authenticator is abnormal. In order to ensure that the memory instance in the scheduling component is consistent with the actual operation of the identifier, the scheduling component deletes the memory instance associated with the exception identifier.

Optionally, a Relay-Job component may be used to implement the scheduling component in this embodiment.

Next, in operation S220, at least one authentication task is acquired from the server according to the task acquisition request of the at least one authenticator, and the to-be-authenticated object associated with each authentication task is acquired.

In this embodiment, specifically, the task claim request of the appraiser indicates the number of appraisal tasks and the appraisal task type requested by the appraiser. The evaluator can generate a task claim request based on its own hardware parameters, operating parameters and current working status. The operating parameters can include, for example, information such as the running rate and the resource consumption occupied by the appraisal task. Information such as the number of identification tasks.

The server provides an authentication service in response to a user's request for an authentication service, and the authentication service may include, for example, a cloud detection service, a malicious code authentication service, a file reputation determination service, and the like. The database of the server aggregates and stores the dynamic identification task information, and stores the objects to be identified associated with the identification tasks. The objects to be identified are the objects that need to be identified by the identification device in the terminal, such as sample files to be identified, log data, Software code, program script, etc.

Exemplarily, when a user requests to authenticate a certain malicious code, an authenticator specifically needs to be used to identify the type of malicious code, and the type of malicious code may include, for example, viruses, Trojans, adware, and backdoors. The identifier can identify the named fields of the malicious code, and determine the operating system environment required for the execution of the malicious code, the family information of the malicious code, the variant information of the malicious code family, the infection length of the file-infecting virus, etc., so as to realize the judgment. Malicious code type.

The scheduling component acquires at least one authentication task from the server in response to the received task claim request of the at least one authenticator, and acquires the to-be-authenticated object associated with each authentication task. Specifically, the scheduling component acquires at least one authentication task from the server according to the number of authentication tasks and the type of authentication tasks requested by each authenticator. In addition, the acquisition operation for at least one authentication task can also be performed according to the task identifier of each authentication task, wherein the task identifier indicates the type of the authentication task and the authentication execution requirement, and the authentication execution requirement includes, for example, the execution of the authentication task instructed by the user. Information such as the type of authenticator required and the number of authenticators.

The scheduling component establishes a memory instance associated with the object to be authenticated, and the memory instance includes a set of attribute information such as the data structure, download address, message identifier, IP address, and storage location of the object to be authenticated. While establishing the memory instance associated with the object to be authenticated, the scheduling component starts the download logic to obtain the object to be authenticated from the server, and caches the object to be authenticated in the memory instance associated with the object to be authenticated. Optionally, when acquiring the to-be-authenticated object associated with each authentication task, the scheduling component determines whether the same object as the to-be-authenticated object to be acquired is cached locally, and if so, the locally cached object is used as the to-be-authenticated object. Specifically, the scheduling component determines whether there is a local memory instance for the to-be-authenticated object to be acquired, and if so, does not repeat the establishment of the memory instance, but directly informs the to-be-authenticated object that the download is complete.

The scheduling component is used to acquire the object to be authenticated associated with the authentication task from the server, and for the same authentication task, the scheduling component only needs to acquire the object to be authenticated from the server once. Compared with the multiple authenticators of the same terminal in the related art respectively obtaining the same object to be authenticated from the server, the present embodiment can effectively reduce the network resource consumption and save the cost of performing the authentication task by optimizing the number of downloads of the object to be authenticated. The terminal bandwidth consumption achieves the purpose of maximizing resource utilization. In addition, the established memory instance for the object to be authenticated is not repeatedly established. By avoiding repeated downloading of the object to be authenticated, it is beneficial to further reduce the bandwidth consumption of the terminal and further improve the utilization rate of network resources and the execution efficiency of the authentication task.

Next, in operation S230, for each appraiser, according to the task pick-up request of the appraiser, assign the appraiser task to the appraiser, so that the appraiser obtains and assigns the appraiser task from the scheduling component based on the assigned appraisal task. The associated object to be authenticated.

In this embodiment, specifically, the authenticator and the scheduling component are located in the same operating environment, and multiple authenticators may be set in the operating environment. For each appraiser, the scheduling component assigns an appraisal task to the appraiser according to the appraiser's task pickup request. Specifically, the scheduling component stores the appraisal task to be allocated to the appraiser in the memory instance for the appraiser according to the task claim request of the appraiser, and more specifically, stores the appraisal task in the to-be-claimed cache of the memory instance, To wait for the appraiser to pick up the assigned appraisal task from the buffer to be picked up. After receiving the assigned authentication task from the scheduling component, the authenticator downloads the to-be-authenticated object associated with the assigned authentication task from the scheduling component based on the assigned authentication task.

The objects to be authenticated in the scheduling component will not be allocated infinitely. When the objects to be authenticated are scanned by all associated authenticators, or the cache time of the objects to be authenticated in the scheduling component is determined to exceed the preset threshold, the association with the objects to be authenticated will be deleted. instance of memory. Exemplarily, the object to be authenticated is the sample file to be authenticated, and it is determined that the authenticators associated with the sample file include authenticator A1, authenticator A2 and authenticator A3, when it is determined that the sample file is identified by authenticator A1, authenticator A2 and authenticator A3 After the A3 scan is completed, the memory instance associated with the sample file is deleted; or, when the sample file is cached in the scheduling component for more than one hour, that is, the memory instance associated with the sample file remains in the scheduling component for more than one hour, then Delete the memory instance associated with the sample file. By optimizing the memory instance in the scheduling component, it is beneficial to improve the resource utilization of the scheduling component.

When an authenticator performs an authentication operation for an object to be authenticated, each authenticator generates an authentication result for the object to be authenticated. The identification result may include, for example, the credibility and reputation value of the object to be identified, and the credibility includes, for example, any of the following: black, white, gray, suspected black, and suspected white. Black indicates that the object to be identified is malicious, white indicates that the object to be identified is safe, gray indicates uncertainty, suspected black indicates that the object to be identified may be malicious, and white indicates that the object to be identified may be safe. The reputation value can be represented by numerical features. For example, when the credibility of an object to be identified is black, its credibility value is 100, and when the credibility of an object to be identified is gray, its credibility value is 5, and the credibility value Characterizes the reliability of the identification results for the object to be identified.

After the authenticator generates the authentication result for the object to be authenticated, different from the authenticator in the related art, the authenticator sends the obtained authentication result to the server. In this embodiment, the authenticator sends the obtained authentication result to the scheduling component. The scheduling component receives the appraisal results returned by each appraiser, and summarizes the appraisal results of each appraiser for the same appraisal task, that is, summarizes the appraisal results of each appraiser for the same object to be appraised, and summarizes the summarized appraisal results for each appraisal task. The authentication result of the task is returned to the server.

Exemplarily, an upstream user requests to authenticate a certain log data, which requires the use of 5 authenticators of type A, B, and C for authentication. The scheduling component aggregates the authentication results of the five authenticators of type A, B, and C, and returns the aggregated authentication results to the server. Among the 15 identification results for the log data, 13 identification results indicate that the log data is white, and 2 identification results indicate that the log data is suspected to be white. The server determines that the final identification result of the log data is white, and the final identification result Return to the upstream user.

With this embodiment, the scheduling component is used to receive a task acquisition request from at least one authenticator, and according to the task acquisition request from the at least one authenticator, at least one authentication task is acquired from the server, and the to-be-authenticated object associated with each authentication task is acquired , and then for each appraiser, according to the appraiser's task acquisition request, assign an appraisal task to the appraiser, so that the appraiser obtains the object to be appraised associated with the assigned appraisal task from the scheduling component based on the assigned appraisal task . Using the scheduling component to obtain the object to be authenticated associated with the authentication task from the server, and obtaining the object to be authenticated from the scheduling component by at least one authenticator, compared with the related art, at least one authenticator directly obtains the same object to be authenticated from the server In this embodiment, by optimizing the number of times of downloading the object to be authenticated from the server, network resource consumption for acquiring the object to be authenticated is effectively reduced, and the purpose of maximizing resource utilization is achieved by saving terminal bandwidth consumption.

FIG. 3 schematically shows a schematic diagram of an authentication task scheduling process according to an embodiment of the present disclosure. As shown in FIG. 3 , in the authentication task scheduling process 300 , the user sends an authentication request to the server 302 through the user terminal 301 for requesting treatment The authentication object is authenticated. After receiving the authentication request from the user, the server 302 generates an authentication task and obtains the to-be-authenticated object associated with the authentication task. Specifically, the to-be-authenticated object can be sent to the server 302 by the user through the user terminal 301, or by the server 302 through obtained by other means. The authentication terminal 303 (there may be multiple authentication terminals in the authentication system, FIG. 3 schematically shows the authentication terminal 303 ) includes a scheduling component and n authenticators, where n is an integer greater than 3. The scheduling component receives a task claim request from at least some of the authenticators of the n authenticators, and based on the received task claim request from at least some of the authenticators, the scheduling component obtains the authentication task from the server 302, and obtains the to-be-authenticated associated with the authentication task object. The scheduling component allocates an appraisal task to each appraiser according to the task receiving request of each appraiser, so that each appraiser obtains the object to be appraised associated with the assigned appraisal task from the dispatching component based on the assigned appraisal task and conducts appraisal , each appraiser returns the appraisal result obtained from the appraisal to the scheduling component, and the scheduling component summarizes the appraisal results for the same appraisal task, and returns the summarized appraisal results to the server 302 for the server 302 to return the summarized appraisal results User terminal 301 .

FIG. 4 schematically shows a flowchart of a method for acquiring an authentication task according to an embodiment of the present disclosure.

As shown in FIG. 4 , operation S220 may include, for example, operations S410 to S420.

In operation S410, according to the task claim request of at least one appraiser received within a preset time period since the last time the appraisal task was obtained from the server, determine the number of appraisal tasks and the appraisal task type requested by each appraiser.

In this embodiment, specifically, the scheduling component may acquire the authentication task from the server at a preset frequency, and acquire the object to be authenticated associated with the authentication task, for example, the scheduling component acquires the authentication task from the server every 1s . The evaluator can send a task acquisition request to the scheduling component at a preset frequency, or can send a task acquisition request to the scheduling component at any time as needed. Exemplarily, the evaluator sends a task acquisition request to the scheduling component every 100ms.

The scheduling component determines the number of appraisal tasks and the type of appraisal tasks requested by each appraiser according to the task claim request of at least one appraiser received within the preset time period since the appraisal task was obtained from the server last time, wherein the preset time period is determined by the scheduler Determines how often the component gets authentication tasks from the server. Exemplarily, the scheduling component determines the number of authentication tasks and the type of authentication tasks requested by each authenticator according to the task acquisition request of the authenticator received in every 1 s.

The scheduling component summarizes the task acquisition requests of at least one appraiser received within the preset time period. The summary principle includes that when multiple task acquisition requests of the same authenticator are received within the preset time period, the multiple task acquisition requests are included in the The indicated maximum number of appraisal tasks, as the number of appraisal tasks requested by the appraiser; when a task claim request from the appraiser is received within the preset time period, the number of appraisal tasks indicated by the task claim request is directly used as the appraiser request The number of identification tasks received.

Exemplarily, the scheduling component receives 3 task claim requests from the appraiser A1 within a certain 1s, and the 3 task claim requests request to claim 5, 10, and 5 appraisal tasks respectively. At this time, the three task claim requests are indicated in the The maximum number of identification tasks of , as the number of identification tasks requested by the appraiser A1, that is, it is determined that the number of identification tasks requested by the appraiser A1 is 10. At the same time, the scheduling component also receives a task pick-up request sent by the appraisers A2, A3, B1, and B2 within the 1s, and the number of appraisal tasks indicated by each task pick-up request is directly used as the appraisal task requested by the corresponding appraiser. quantity.

Optionally, the frequency at which the scheduling component obtains the appraisal tasks from the server may be adjusted, that is, the above-mentioned preset duration is adjusted, so that the scheduling component receives the task acquisition requests from all the appraisers in the terminal within the preset duration. The scheduling component summarizes the task acquisition requests received within the preset time period, and the aggregated task acquisition request package corresponds to the same identification task as much as possible, that is, the aggregated task acquisition request package corresponds to the same object to be identified as much as possible. This design can maximize the The number of downloads of the object to be identified is reduced to a certain extent, which is conducive to maximizing the optimization degree of network resources.

The task claim request of the appraiser also indicates the appraisal task type requested by the appraiser, and different appraisal task types correspond to different object types to be appraised. The scheduling component can determine the type of the object to be authenticated suitable for the authenticator according to the received request of the authenticator. The type of the to-be-authenticated object may include, for example, sample files, log data, software codes, program scripts, and the like.

Next, in operation S420, at least one authentication task is acquired from the server according to the number of authentication tasks and the type of authentication tasks requested by each authenticator.

In this embodiment, specifically, the scheduling component acquires at least one authentication task from the server according to the number of authentication tasks and the type of authentication tasks requested by each authenticator. After acquiring at least one authentication task from the server, the scheduling component puts the authentication task associated with each authenticator into the download cache for the memory instance of each authenticator. After downloading the object to be authenticated associated with the authentication task, the scheduling component puts the authentication task from the download cache into the receiving cache, waiting for the authenticator to receive the authentication task.

FIG. 5 schematically shows a flow chart of another authentication task scheduling method according to an embodiment of the present disclosure, and the method is applied to an authenticator.

As shown in FIG. 5, the method 500 may include operations S510-S530

In operation S510, a task claim request is sent to the scheduling component.

In operation S520, the authentication task assigned based on the task claim request is obtained from the scheduling component, and the to-be-authenticated object associated with the assigned authentication task is obtained.

In operation S530, an authentication operation for the object to be authenticated is performed, and the obtained authentication result is returned to the scheduling component.

The scheduling component establishes a memory instance associated with the authenticator, and when acquiring the assigned authentication task from the scheduling component, the assigned authentication task is specifically obtained from the memory instance associated with the authenticator. At the same time, the scheduling component also establishes a memory instance associated with the object to be authenticated. When acquiring the object to be authenticated associated with the assigned authentication task from the scheduling component, the object to be authenticated is obtained from the memory instance associated with the object to be authenticated. Optionally, the authenticator sends heartbeat information to the scheduling component at a preset frequency to indicate that the authenticator is in a normal running state.

An embodiment of the present disclosure provides an authentication task processing system, including a server, an authenticator, and a scheduling component, wherein the scheduling component can be used to execute the method of this embodiment, and the authenticator and the scheduling component are located in the same operating environment.

FIG. 6A schematically shows a schematic structural diagram of an authentication task processing system in the related art. As shown in FIG. 6A , the processing system includes a server, an authenticator 1 located in machine 1 , an authenticator 2 and an authentication device located in machine 2 Authenticator 3, Authenticator 4. When performing the authentication task, the authenticator 1 , the authenticator 2 , the authenticator 3 , and the authenticator 4 obtain the authentication task from the server, and obtain the object to be authenticated associated with the authentication task. Different authenticators in the same machine may acquire the same object to be authenticated from the server. Repeated acquisition of the object to be authenticated will cause additional consumption of network bandwidth, affect the processing efficiency of the authentication task, and even affect the normal operation of the machine.

FIG. 6B schematically shows a schematic structural diagram of an authentication task processing system according to an embodiment of the present disclosure. As shown in FIG. 6B , the processing system includes a server, a scheduling component 1 located in a machine 1 , an authenticator 1 , an authenticator 2 and Scheduling component 2, evaluator 3, evaluator 4 located in machine 2. When performing the authentication task, the scheduling component 1 and the scheduling component 2 acquire the authentication task from the server, and acquire the object to be authenticated associated with the authentication task. The evaluator in each machine obtains the identification task from the scheduling component located in the same machine, and obtains the object to be identified associated with the identification task. Since the scheduling component and the evaluator are located in the same machine, different evaluators obtain the object to be identified from the scheduling component. Authenticating objects does not cause additional consumption of network bandwidth. By setting the scheduling component in each machine, using the scheduling component to obtain the object to be authenticated from the server, and optimizing the number of times to download the object to be authenticated from the server, it is beneficial to reduce network bandwidth consumption, and it is beneficial to maximize resource utilization by saving terminal bandwidth consumption. purpose of transformation.

7 schematically illustrates a block diagram of an authentication task scheduling component according to an embodiment of the present disclosure.

As shown in FIG. 7 , the scheduling component 700 may include an authenticator management module 701 , an authentication task management module 702 and a to-be-authenticated object management module 703 , each of which is communicatively connected.

Wherein, the authenticator management module 701 is configured to receive a task claim request from at least one authenticator; the authentication task management module 702 is configured to obtain at least one authentication task from the server according to the task claim request of the at least one authenticator, and for each The appraiser assigns an appraisal task to the appraiser according to the task receiving request of the appraiser; the object to be appraised management module 703 is used to obtain the object to be appraised associated with each appraisal task, so that the appraiser can obtain the appraisal task from the appraiser based on the assigned appraisal task. The authentication object management module acquires the to-be-authenticated object associated with the assigned authentication task.

With this embodiment, the scheduling component is used to receive a task acquisition request from at least one authenticator, and according to the task acquisition request from the at least one authenticator, at least one authentication task is acquired from the server, and the to-be-authenticated object associated with each authentication task is acquired , and then for each appraiser, according to the appraiser's task acquisition request, assign an appraisal task to the appraiser, so that the appraiser obtains the object to be appraised associated with the assigned appraisal task from the scheduling component based on the assigned appraisal task . Using the scheduling component to obtain the object to be authenticated associated with the authentication task from the server, and obtaining the object to be authenticated from the scheduling component by at least one authenticator, compared with the related art, at least one authenticator directly obtains the same object to be authenticated from the server In this embodiment, by optimizing the number of times of downloading the object to be authenticated from the server, network resource consumption for acquiring the object to be authenticated is effectively reduced, and the purpose of maximizing resource utilization is achieved by saving terminal bandwidth consumption.

As an optional embodiment, acquiring the to-be-identified object associated with each authentication task includes: the to-be-authenticated object management module determines whether there is a local cache of the same object as the to-be-authenticated object to be acquired; object as the object to be identified.

As an optional embodiment, acquiring at least one authentication task from the server according to a task acquisition request of at least one authenticator includes: the authentication task management module authenticates the authentication task according to a preset time period since the previous acquisition of the authentication task from the server The at least one authentication task is obtained from the server according to the task acquisition request of at least one authenticator received by the authenticator management module.

As an optional embodiment, the appraiser management module determines the number of appraisal tasks and the appraisal task type requested by each appraiser according to the task claim request of each appraiser received within a preset duration; The management module determines the number of authentication tasks and the type of authentication tasks requested by each authenticator, and obtains at least one authentication task from the server.

As an optional embodiment, determining the number of appraisal tasks requested by each appraiser according to the task claim request of each appraiser received within a preset time period, including: when the appraiser management module receives the same When multiple tasks are requested by the appraiser, the maximum number of identification tasks indicated in the multiple task request requests is taken as the number of identification tasks requested by the appraiser.

As an optional embodiment, the authenticator management module is further configured to establish a memory instance associated with each authenticator; according to a task acquisition request of the authenticator, assigning an authentication task to the authenticator includes: the authentication task management module according to the authenticator , determine the authentication task to be assigned to the authenticator, and store the authentication task to be assigned in the memory instance associated with the authenticator.

As an optional embodiment, the authenticator management module is further configured to: receive heartbeat information sent by the authenticator at a preset frequency; Qualifier exception, and deletes the memory instance associated with the exception qualifier.

As an optional embodiment, the to-be-authenticated object management module is further configured to: establish a memory instance associated with each to-be-authenticated object; When the cache time exceeds the preset threshold, delete the memory instance associated with the object to be authenticated.

As an optional embodiment, the appraiser management module is further configured to: receive the appraisal results returned by each appraiser; summarize the appraisal results of the appraisers for the same appraisal task; return the summarized appraisal results for each appraisal task to the server.

As an optional embodiment, the authenticator and the scheduling component are located in the same operating environment.

It should be noted that, in the embodiments of the present disclosure, the embodiments of the apparatus part are similar to the embodiments of the method part, and the technical effects achieved are also correspondingly similar, which will not be repeated here.

Any of the modules according to the embodiments of the present disclosure, or at least part of the functions of any of the modules, may be implemented in one module. Any one or more of the modules according to the embodiments of the present disclosure may be split into multiple modules for implementation. Any one or more of the modules according to embodiments of the present disclosure may be implemented, at least in part, as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, A system-on-package, an application specific integrated circuit (ASIC), or any other reasonable hardware or firmware implementation that integrates or encapsulates a circuit, or in any one of software, hardware, and firmware implementations or It can be realized by any suitable combination of any of them. Alternatively, one or more of the modules according to embodiments of the present disclosure may be implemented at least in part as computer program modules that, when executed, may perform corresponding functions.

For example, any one of the authenticator management module 701 , the authentication task management module 702 and the to-be-authenticated object management module 703 may be combined in one module, or any one of the modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the authenticator management module 701, the authentication task management module 702, and the to-be-authenticated object management module 703 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a A programmed logic array (PLA), system-on-chip, system-on-substrate, system-on-package, application-specific integrated circuit (ASIC), or hardware or firmware that can be implemented in any other reasonable manner by integrating or packaging a circuit, or It can be implemented in any one of the three implementation manners of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the authenticator management module 701, the authentication task management module 702, and the object to be authenticated management module 703 may be implemented at least in part as a computer program module that, when executed, may perform corresponding functions.

FIG. 8 schematically shows a block diagram of an electronic device according to an embodiment of the present disclosure. The electronic device shown in FIG. 8 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 8 , the electronic device 800 includes a processor 810 and a computer-readable storage medium 820 . The electronic device 800 may execute the method according to the embodiment of the present disclosure.

Specifically, the processor 810 may include, for example, a general-purpose microprocessor, an instruction set processor and/or a related chipset, and/or a special-purpose microprocessor (eg, an application specific integrated circuit (ASIC)), and the like. The processor 810 may also include onboard memory for caching purposes. The processor 810 may be a single processing module or multiple processing modules for performing different actions of the method flow according to the embodiments of the present disclosure.

The computer-readable storage medium 820 can be, for example, a non-volatile computer-readable storage medium, and specific examples include but are not limited to: magnetic storage devices, such as magnetic tapes or hard disks (HDD); optical storage devices, such as compact disks (CD-ROMs) ; memory, such as random access memory (RAM) or flash memory; etc.

The computer-readable storage medium 820 may include a computer program 821, which may include code/computer-executable instructions that, when executed by the processor 810, cause the processor 810 to perform methods according to embodiments of the present disclosure or any variation thereof.

The computer program 821 may be configured with computer program code comprising, for example, computer program modules. For example, in an example embodiment, the code in computer program 821 may include one or more program modules, including, for example, 821A, module 821B, . . . It should be noted that the division method and number of modules are not fixed, and those skilled in the art can use appropriate program modules or combination of program modules according to the actual situation. When these combination of program modules are executed by the processor 810, the processor 810 can A method according to an embodiment of the present disclosure or any variation thereof is performed.

According to an embodiment of the present disclosure, at least one of the authenticator management module 701, the authentication task management module 702, and the to-be-authenticated object management module 703 may be implemented as a computer program module described with reference to FIG. 8, which when executed by the processor 810, The corresponding operations described above can be implemented.

The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the device/apparatus/system described in the above embodiments; it may also exist alone without being assembled into the device/system. device/system. The above-mentioned computer-readable storage medium carries one or more programs, and when the above-mentioned one or more programs are executed, implement the method according to the embodiment of the present disclosure.

The present disclosure also provides a computer program product, which includes a computer program, and the computer program includes program codes for executing the methods provided by the embodiments of the present disclosure. When the computer program product runs on an electronic device, the program code uses The method for scheduling the authentication task provided by the embodiment of the present disclosure is used for the electronic device.

According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure may be written in any combination of one or more programming languages, and specifically, high-level procedures and/or object-oriented programming may be used. programming language, and/or assembly/machine language to implement these computational programs. Programming languages include, but are not limited to, languages such as Java, C++, python, "C" or similar programming languages. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks 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 is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

It will be appreciated by those skilled in the art that although the present disclosure has been shown and described with reference to specific exemplary embodiments of the present disclosure, those skilled in the art will appreciate that the present disclosure is not deviated from the spirit of the present disclosure as defined by the appended claims and their equivalents. Various changes in form and detail may be made within the scope and scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the above-described embodiments, but should be determined not only by the appended claims, but also by their equivalents.

Claims (24)

1. A method for identifying task scheduling, applied to a scheduling component, comprising: receiving a task claim request from at least one authenticator; Acquire at least one authentication task from the server according to the task acquisition request of the at least one authenticator, and acquire the to-be-authenticated object associated with each of the authentication tasks; For each of the appraisers, according to the task claim request of the appraiser, assign an appraisal task to the appraiser, so that the appraiser obtains from the scheduling component based on the assigned appraisal task and the The object to be authenticated associated with the assigned authentication task. 2. The method according to claim 1, wherein, when acquiring the object to be identified associated with each of the identification tasks, comprising: Determine whether the local cache has the same object as the to-be-authenticated object to be acquired; If there is, the object cached locally is used as the object to be authenticated. 3. The method according to claim 1, wherein the acquiring at least one authentication task from the server according to the task receiving request of the at least one authenticator, comprises: Acquire at least one authentication task from the server according to a task acquisition request of the at least one authenticator received within a preset time period from the previous acquisition of the authentication task from the server. 4. The method according to claim 3, wherein said at least one appraiser's task claim request received within a preset period of time since the last time the appraisal task was obtained from the server is obtained from the said appraiser. Obtain at least one authentication task from the server, including: According to the task claim request of each of the appraisers received within the preset time period, determine the number of appraisal tasks and the appraisal task type requested by each of the appraisers; Acquire at least one authentication task from the server according to the number of authentication tasks and the type of authentication tasks requested by each of the authenticators. 5. The method according to claim 4, wherein determining the number of appraisal tasks requested by each of the appraisers according to the task claim request of each of the appraisers received within the preset duration, comprising: Within the preset time period, when multiple task claim requests from the same appraiser are received, the maximum number of appraisal tasks indicated in the multiple task claim requests is taken as the number of appraisal tasks requested by the appraiser. 6. The method of claim 1, further comprising: establishing a memory instance associated with each of said authenticators; The assigning an appraisal task to the appraiser according to the task claim request of the appraiser includes: According to the task claim request of the appraiser, determine the appraisal task to be assigned to the appraiser; The to-be-allocated authentication task is stored in a memory instance associated with the authenticator. 7. The method of claim 6, further comprising: receiving heartbeat information sent by the authenticator at a preset frequency; and, When the heartbeat information of a certain authenticator is not received within a preset time period, it is determined that the authenticator is abnormal; Deletes the memory instance associated with the exception identifier. 8. The method of claim 1, further comprising: establishing a memory instance associated with each of the objects to be authenticated; and, When it is determined that the object to be authenticated has been scanned by all associated authenticators, or it is determined that the cache time of the object to be authenticated in the scheduling component exceeds a preset threshold, the memory instance associated with the object to be authenticated is deleted. 9. The method of claim 1, further comprising: receiving the authentication result returned by each of the authenticators; Summarize the identification results of each of the authenticators for the same identification task; Return the aggregated authentication results for each of the authentication tasks to the server. 10. The method of any one of claims 1 to 9, wherein the authenticator is located in the same runtime environment as the scheduling component. 11. An identification task scheduling component, comprising: An authenticator management module, an authentication task management module and an object to be authenticated management module, each of which is communicatively connected between the management modules, wherein, The appraiser management module is configured to receive a task claim request from at least one appraiser; The appraisal task management module is configured to obtain at least one appraisal task from the server according to the task claim request of the at least one appraiser, and for each of the appraisers, according to the task claim request of the appraiser, to the The authenticator assigns authentication tasks; The to-be-authenticated object management module is used to acquire the to-be-identified objects associated with each of the authentication tasks, so that the appraiser obtains and distributes from the to-be-identified object management module based on the assigned authentication tasks The to-be-authenticated object associated with the authentication task. 12. The scheduling component according to claim 11, wherein the acquiring the to-be-identified object associated with each of the identification tasks comprises: The to-be-authenticated object management module determines whether the same object as the to-be-authenticated object to be acquired is cached locally; if so, the locally cached object is used as the to-be-authenticated object. 13. The scheduling component according to claim 11, wherein the acquiring at least one authentication task from the server according to the task acquisition request of the at least one authenticator comprises: The appraisal task management module selects the task claim request from the at least one appraiser received by the appraiser management module within a preset period of time since the appraiser management module obtained the appraisal task from the server. Get at least one authentication task. 14. The scheduling component of claim 13, wherein, The appraiser management module determines the number of appraisal tasks and the appraisal task type requested by each appraiser according to the task claim request of each appraiser received within the preset duration; The authentication task management module acquires at least one authentication task from the server according to the number of authentication tasks and the type of authentication tasks requested by each authenticator determined by the authenticator management module. 15. The scheduling component according to claim 14, wherein the determining the number of appraisal tasks requested by each appraiser according to the task claim request of each appraiser received within the preset time period comprises: When the appraiser management module receives multiple task pick-up requests from the same appraiser within the preset time period, the maximum number of appraisal tasks indicated in the multiple task pick-up requests is taken as the appraiser request for pick-up. number of identification tasks. 16. The scheduling component of claim 11, wherein, The authenticator management module is further configured to establish a memory instance associated with each of the authenticators; The assigning an appraisal task to the appraiser according to the task claim request of the appraiser includes: The appraisal task management module determines the appraisal task to be assigned to the appraiser according to the task claim request of the appraiser, and stores the appraisal task to be assigned in a memory instance associated with the appraiser . 17. The scheduling component of claim 16, wherein the authenticator management module is further configured to: receiving heartbeat information sent by the authenticator at a preset frequency; and, When the heartbeat information of a certain identifier is not received within a preset time period, it is determined that the identifier is abnormal, and the memory instance associated with the abnormal identifier is deleted. 18. The scheduling component according to claim 11, wherein the to-be-authenticated object management module is further used for: establishing a memory instance associated with each of the objects to be authenticated; and, When it is determined that the object to be authenticated has been scanned by all associated authenticators, or it is determined that the cache time of the object to be authenticated exceeds a preset threshold, the memory instance associated with the object to be authenticated is deleted. 19. The scheduling component of claim 11, wherein the authenticator management module is further configured to: receiving the authentication result returned by each of the authenticators; Summarize the identification results of each of the authenticators for the same identification task; Return the aggregated authentication results for each of the authentication tasks to the server. 20. The scheduling component of any one of claims 11 to 19, wherein the authenticator is located in the same runtime environment as the scheduling component. 21. An authentication task processing system, comprising: A server, an authenticator and a scheduling component as claimed in any one of claims 11 to 20, wherein the authenticator is located in the same operating environment as the scheduling component. 22. An electronic device comprising: one or more processors, and memory for storing one or more programs, Wherein, the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1 to 10. 23. A computer-readable storage medium storing computer-executable instructions which, when executed, are used to implement the method of any one of claims 1 to 10. 24. A computer program product comprising computer readable instructions, wherein the computer readable instructions, when executed, are used to perform the method of any one of claims 1 to 10.

Images