Method and system for task distribution

[0031] Preferred embodiments of the present invention will be specifically described below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of the application and are used together with the embodiments of the present invention to explain the principle of the present invention. For the sake of clarity and simplicity, detailed descriptions of known functions and constructions in the devices described herein will be omitted when it may obscure the subject matter of the present invention.

[0032] The present invention provides a method and system for task allocation, which implements inter-domain task distribution management through the task distribution of the control server to each distributed control sub-server; completes the task allocation within the domain through the task server inside each distributed control sub-server Distribution management: In order to ensure the success and accuracy of task completion, the control server distributes a single task to multiple distributed verification servers to complete the decision verification task after submitting the results, so as to realize the verification management of inter-domain tasks. The timeliness and efficiency of task assignment are improved, thereby improving the operating efficiency of the server. The present invention will be described in further detail below in conjunction with the accompanying drawings and several embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

[0033] An embodiment of the present invention provides a task allocation method, see figure 1 , the method includes:

[0034] S102. After receiving the task, the control server assigns the task to each of the control sub-servers according to the first task request sent by the control sub-server;

[0035]S104. According to the second task request sent by the task server, the control sub-server assigns the task assigned by the control sub-server to each of the task servers for processing.

[0036] That is to say, the present invention realizes inter-domain task distribution management through the task distribution of the control server to each distributed control sub-server; completes the task distribution management in the domain through the task server inside each distributed control sub-server; in order to ensure the task The success and accuracy of the completion, the control server distributes a single task to multiple distributed verification servers to complete the decision verification task after submitting the results, and realizes the verification management of inter-domain tasks. The timeliness and efficiency of task assignment are improved, thereby improving the operating efficiency of the server.

[0037] That is, the present invention obtains tasks from the database through the control server, and after receiving the first task request from the control sub-server, sends the above-mentioned tasks to the control sub-server according to the type of the first task request; After the second task request, according to the above tasks issued by the control server, a new distribution task is generated based on the task distribution algorithm, and the distribution task is assigned to the above task server according to the type of the above second task request, which solves the problem in the related technology The allocation method does not allocate tasks reasonably enough, which improves the timeliness and efficiency of task allocation, and improves the operating efficiency of the server.

[0038] figure 2 is a flow chart of a task allocation method according to an embodiment of the present invention, which will be combined below figure 2 Detailed explanation and specification are carried out to the method described in the present invention:

[0039] Step S202, the control server acquires task information from the database; wherein, the task information carries tasks;

[0040] Step S204, after receiving the first task request from the control sub-server, the control server sends the above-mentioned task to the control sub-server according to the type of the above-mentioned first task request;

[0041] Step S206, after the control sub-server receives the second task request from the task server, it generates a new distribution task based on the task distribution algorithm according to the above-mentioned tasks issued by the control server; assigns the distribution task to the task server.

[0042] Through the above method, the control server obtains the task from the database, and after receiving the first task request from the control sub-server, sends the above-mentioned task to the control sub-server according to the type of the first task request; the control sub-server receives the first task request from the task server After the second task request, according to the above tasks issued by the control server, a new distribution task is generated based on the task distribution algorithm, and the distribution task is assigned to the above task server according to the type of the above second task request, which solves the problem of task distribution in related technologies The method solves the problem that the allocation of tasks is not reasonable enough, improves the timeliness and efficiency of task allocation, and improves the operating efficiency of the server.

[0043] Step S204 of this embodiment realizes the distribution management of inter-domain tasks. In step S204 of this embodiment, before the control server receives the first task request from the control sub-server, the two should first establish a connection, and the control sub-server should register with the control server, so as to provide a basis for subsequent task allocation. Therefore, this embodiment provides a preferred implementation manner, that is, before the control server receives the first task request from the control sub-server, the above method further includes: the control server receives the TCP connection request from the control sub-server, and the control server and the control sub-server establish TCP link; the control sub-server sends a registration message to the control server through the above-mentioned TCP link; wherein, the registration message carries the field and the identification number ID of the control sub-server; the control server controls the identity of the control sub-server according to the above-mentioned fields Confirmation, after the confirmation is successful, the above-mentioned ID is parsed from the registration message; wherein, the ID is used to identify the control sub-server that receives the task issued by the control server.

[0044] In step S204 of this embodiment, the control server sends the task to the control sub-server according to the type of the first task request. Generally, the types of the first task requests are divided into two categories: full task requests and incremental task requests. For the two types of first task requests, different task delivery operations are performed respectively. The following is a detailed introduction:

[0045] If the type of the first task request is a full task request, the control server parses the full task request to obtain the ID of the control sub-server; check whether the ID is in the task list, and if so, the control server sends the current task corresponding to the above ID Send it to the control sub-server; wherein, the task list records the corresponding relationship between the ID and the task;

[0046] If the type of the first task request is an incremental task request, the control server parses the incremental task request to obtain the above-mentioned ID of the control sub-server; check whether the ID is in the above-mentioned task list, and if so, the control server will newly add The task is delivered to the control sub-server, and/or, a task deletion message is sent to the control sub-server; wherein, the task deletion message is used to instruct the control sub-server to delete the task to be deleted.

[0047] Through the above preferred implementation manner, when the first task requests are of different types, corresponding task delivery operations are respectively taken, which improves the efficiency of inter-domain task distribution management and expands the scope of application of task allocation.

[0048] Step S206 of this embodiment realizes the distribution management of tasks in the domain. In step S206 of this embodiment, before the control sub-server receives the second task request from the task server, the two should first establish a connection, and the task server should register with the control sub-server, so as to provide a basis for subsequent task allocation. Therefore, this embodiment provides a preferred implementation manner, that is, before the control sub-server receives the second task request from the task server, the above method further includes: controlling the sub-server to receive the TCP connection request from the task server, and controlling the sub-server to establish a connection with the task server. TCP connection; the task server sends a registration message to the control sub-server through the above-mentioned TCP link; the control sub-server distributes an ID for the task server according to the registration message, and sends the ID to the task server in a reply message; wherein, the above-mentioned ID uses Used to identify the task server that receives distribution tasks assigned by the control subserver.

[0049] In step S206 of this embodiment, the control sub-server generates a new distribution task based on the task distribution algorithm according to the task issued by the control server, and then assigns the distribution task to the task server according to the type of the second task request. Generally, there are two types of second task requests: full task requests and incremental task requests. For the two types of first task requests, different task delivery operations are performed respectively. The following is a detailed introduction:

[0050] If the type of the second task request is a full task request, the control sub-server parses the full task request to obtain the above-mentioned ID of the task server; the control sub-server assigns the currently managed task corresponding to the ID to the task server;

[0051] If the type of the second task request is an incremental task request, the control sub-server parses the above incremental task request to obtain the above ID of the task server; query the status of the task currently controlled by the TD, if the above status is the task server When there is a newly added task, the control sub-server assigns the above newly added task to the task server, and if the above state is that the task server has a task to be deleted, it sends a task deletion message to the task server; wherein, the above task deletion message is used to instruct the task server Delete pending tasks.

[0052] Through the above preferred implementation manner, when the second task requests are of different types, corresponding task delivery operations are respectively taken, which improves the efficiency of task distribution management in the domain and expands the scope of application of task allocation.

[0053] That is to say, when the first task request is a full task request, the control server parses the full task request, obtains the ID of the corresponding control sub-server, and queries the ID in the task list, if the ID In the task list, the control server sends the current task corresponding to the above-mentioned ID to the control sub-server; wherein, the task list records the corresponding relationship between the ID of the control sub-server and the task; when the first task When the request is an incremental task request, the control server parses the incremental task request, obtains the ID of the control sub-server, and queries the ID in the task list. If the ID is in the task list, the control server The server sends the newly added task to the control sub-server, and/or sends a task deletion message to the control sub-server; wherein, the task deletion message is used to instruct the control sub-server to delete the task to be deleted;

[0054] When the second task request is a full task request, the control sub-server parses the full task request, obtains the ID of the corresponding task server, and queries the ID in the task list. list, the control sub-server sends the current task corresponding to the above-mentioned ID to the task server; wherein, the task list records the correspondence between the ID of the task server and the task; when the second task request is an incremental task When requesting, the control sub-server parses the incremental task request, obtains the ID of the task server, and queries the ID in the task list, if the ID is in the task list, the control sub-server will newly add The task is sent to the task server, and/or, a task deletion message is sent to the task server; wherein, the task deletion message is used to instruct the task server to delete the task to be deleted.

[0055] The embodiment of the present invention also provides the following preferred implementation manners, specifically, verifying the task assigned by the control sub-server through the verification server, and triggering the task assigned by the control sub-server when the verification is passed to process. And the verification server generates a task verification result message from the verification result, and reports the task verification result message to the control server.

[0056] That is to say, in the present invention, the task of the control server is verified by the verification server.

[0057] Before the verification server verifies the tasks of the control server, it is necessary to establish a connection between the verification server and the control sub-server, and then the verification server can interact with the control server through the control sub-server. Therefore, this embodiment provides a preferred implementation manner, that is, before the verification server verifies the task of the control server, the above method further includes: the control sub-server receives the TCP connection request of the verification server, and the control sub-server establishes a TCP link with the verification server way; after the control sub-server receives the registration message sent by the verification server through the above-mentioned TCP link, it sends a registration reply message to the verification server; wherein, the registration reply message carries the ID allocated by the control sub-server for the verification server. Through this preferred embodiment, the verification server is connected to the control server through the control sub-server, and the verification server is registered on the control sub-server, which provides a basis for subsequent task verification.

[0058] Preferably, the verification server's verification of the task of the control server includes: the verification server sends a verification task request to the control server through the control sub-server, and the control server parses the verification task request to obtain the above-mentioned ID of the verification server; Send a verification reply message to the verification server corresponding to the above ID; wherein, the verification reply message carries the task to be verified in the control server; the verification server verifies the above task to be verified. Through this preferred implementation manner, the verification management of inter-domain tasks is realized.

[0059] Preferably, after the verification server verifies the task of the control server, the method further includes: the verification server generates a task verification result message according to the verification result, and reports the task verification result message to the control server. This provides a consideration basis for the control server to generate a corresponding distribution strategy.

[0060] image 3It is a structural diagram of a network distributed multi-task distribution management system according to an embodiment of the present invention, such as image 3 As shown, the system includes a database, a control server, a control sub-server, a task server and an authentication server. The system can realize the distribution management of inter-domain tasks, the distribution management of intra-domain tasks and the verification management of inter-domain tasks introduced in the above embodiments. Introduce them separately below.

[0061] The control server is configured to assign the task to each of the control sub-servers according to the first task request sent by the control sub-server after receiving the task; The second task request is to assign the task assigned by the control sub-server to each of the task servers; the task server is configured to process the task assigned from the control sub-server.

[0062] That is to say, the present invention realizes inter-domain task distribution management through the task distribution of the control server to each distributed control sub-server; completes the task distribution management in the domain through the task server inside each distributed control sub-server; in order to ensure the task The success and accuracy of the completion, the control server distributes a single task to multiple distributed verification servers to complete the decision verification task after submitting the results, and realizes the verification management of inter-domain tasks. The timeliness and efficiency of task assignment are improved, thereby improving the operating efficiency of the server.

[0063] The type of the first task request in the embodiment of the present invention includes a full task request and an incremental task request; the type of the second task request includes a full task request and an incremental task request.

[0064] The control server is further configured to, when the first task request is a full task request, analyze the full task request to obtain the ID of the corresponding control sub-server, and query the ID in the task list, if the ID In the task list, the current task corresponding to the above-mentioned ID is sent to the control sub-server; wherein, the task list records the corresponding relationship between the ID of the control sub-server and the task; when the first task request is an increment When a task request is requested, the incremental task request is parsed to obtain the ID of the control sub-server, and the ID is queried in the task list. If the ID is in the task list, the newly added task is issued to the control sub-server The server, and/or, sends a task deletion message to the control subserver; where the task deletion message is used to instruct the control subserver to delete the task to be deleted;

[0065] The control sub-server is further configured to, when the second task request is a full task request, analyze the full task request to obtain the ID of the corresponding task server, and query the ID in the task list, if the ID In the task list, the current task corresponding to the above-mentioned ID is sent to the task server; wherein, the task list records the correspondence between the ID of the task server and the task; when the second task request is an incremental task request , parse the incremental task request to obtain the ID of the task server, and query the ID in the task list, and if the ID is in the task list, send the newly added task to the task server, and/ Or, send a task deletion message to the task server; where the task deletion message is used to instruct the task server to delete the task to be deleted.

[0066] The embodiment of the present invention also provides a preferred embodiment, the system further includes: a verification server;

[0067] The verification server verifies the tasks assigned by the control sub-server, and when the verification is passed, triggers the control sub-server to process the assigned tasks, and generates a task verification result message with the verification results, and sends The task verification result message is reported to the control server.

[0068] (1) Inter-domain task distribution management, that is, the process in which the control server assigns tasks to the control sub-servers.

[0069] Step 1: The control server listens to a fixed TCP port, obtains task information from a database, and stores the task information after receiving the task information, which carries a task.

[0070] Specifically, the control server monitors the TCP port, parses the TCP message after receiving the TCP message, and discards the message if an error occurs in the parsing; otherwise, the parsed information is processed as follows (full amount, increase, delete) according to the message type, and Acknowledge the TCP message.

[0071] Step 2, the control server waits for the TCP connection of each control sub-server, and sends tasks to the control sub-servers for interaction according to the task request type of the control sub-servers.

[0072] Specifically, the control sub-server monitors task request information from the control sub-servers in each domain on the configured TCP port. If a control sub-server initiates a TCP connection, the control server independently establishes a session with the control sub-server, and initializes the task information of the control sub-server. Before requesting a task, the first message of the control sub-server needs to be a registration message, which contains fields and its own ID. After receiving the message, the control server compares the above fields to confirm the control sub-server Identity, if the identity confirmation is successful, the ID in the registration message will be parsed out, and the corresponding data structure will be established for the control sub-server for subsequent use, otherwise, the connection will be disconnected.

[0073] Then the control sub-server can initiate a task request message to the control server. There are two types of messages: full request and incremental request. After receiving the full request message from the control sub-server, the control server parses out the ID in it and queries it in the task list. This ID, if the task corresponding to the ID is found, all current tasks will be assigned to the control sub-server; after the control server receives the incremental request message from the control sub-server, it will parse out the ID and query the task in the task list. ID, if the task corresponding to the ID is found, an incremental message will be generated according to the final status of all tasks from the last request of this domain, that is, the task message that needs to be added or deleted. If a new task message needs to be added, it will be added The task is assigned to the control sub-server. If the task message needs to be deleted, a task deletion message is sent to the control sub-server. The task deletion message is used to instruct the control sub-server to delete the task to be deleted.

[0074] Of course, for the above-mentioned task distribution process, the control server adopts a passive response mode, that is, the control sub-server makes a timing request, and the control server performs passive reception, processing and reply.

[0075] Step 3, the system generates log file records. The system saves the process, results, and error recovery and other related information of inter-domain task distribution management in log files, providing a distribution basis for the control server and control sub-servers.

[0076] (2) Intra-domain task distribution management, that is, the process of controlling sub-servers to assign tasks to task servers.

[0077] Step 1, the control sub-server waits for the TCP connection of each task server in the domain. Wherein, the task is different from the task assigned by the control server to the control sub-server, but a new distribution task generated by the control sub-server based on the task distribution algorithm according to the task issued by the control server.

[0078] Specifically, the control sub-server monitors the task request information from the task server in the domain on the configured TCP port. If a certain task server initiates a TCP connection, the control sub-server independently establishes a session with the task server. Before requesting a task, the first message of the task server must be a registration message, so that the control sub-server will assign a unique ID in the domain to the task server, and encapsulate the ID in a message to reply to the task server, and the subsequent communication will be Tag the task server with this ID.

[0079] Step 2: After the control sub-server listens to the task request initiated by the task server in the domain on a specific TCP port, according to the task request type of the task server, assign tasks to each task server in the domain according to a specific task distribution algorithm. In order to achieve fast and efficient task completion, avoid repeated tasks and inefficient completion of tasks.

[0080] Specifically, the task server sends a task request message to the control sub-server. There are two types of messages: full request and incremental request. All managed tasks are encapsulated in a specific message and replied to the task server. After receiving the incremental request message from the task server, the control sub-server parses out the ID and queries the status of the current control task. If there is a new task for the task server in the current task, the control sub-server will encapsulate the new task in a specific message and assign it to the task server; if there is a task that needs to be deleted for the task server in the current task, Then the control sub-server sends a specific message to the task server to instruct the task server to delete the corresponding task.

[0081] In the above process, the control sub-server monitors the task request information from the task server in the domain on the configured TCP port. When a distribution request is received, a new distribution task object is generated. After the control sub-server receives the task distribution initialization message, it parses the message to generate a relevant data structure for storing the distribution task information; and generates a task ID for the task as an identifier for the later task distribution, and finally encapsulates the ID in the reply message, Reply to the node machine that sent the distribution task initialization message. If the message received by the control sub-server is a task request message, it parses out the task ID in the message, queries according to the task ID, assigns a task to the requesting node machine, and encapsulates it into a task reply message for message reply.

[0082] Step 3, the system generates log file records. The system saves the process, results, and error recovery and other related information of the task distribution management in the domain in the log file, which provides the distribution basis for the control sub-server and task server.

[0083] (3) Inter-domain task verification management, that is, the process in which the verification server verifies the tasks of the control server.

[0084] Step 1. The verification server initiates a TCP connection to the control sub-server. After the connection is successful, it needs to send an initialization message to register with the control sub-server before sending other messages. Only after receiving the initialization reply message from the control sub-server can the following messages be carried out Send, the verification server obtains its own ID through the initialization reply message, and in the subsequent communication process, the control server uses this ID to identify which verification server it is.

[0085] Step 2, the verification server can periodically send a verification task request message to the control server through the control sub-server, and the control server will send a verification task reply message after receiving the request message. Send it to the control sub-server, the control sub-server sends the verification task to each verification server that needs to perform the verification task, and the verification server executes the verification task after receiving the verification task sent by the control server through the control sub-server In the verification operation, a verification result is obtained according to the verification situation analysis, a task verification result message is generated, and the task verification result message is reported to the control server through the control sub-server. The control server finally makes a task allocation decision, which provides a consideration basis for subsequent task allocation.

[0086] Corresponding to the task allocation method introduced in the above embodiment, this embodiment provides a task allocation device for implementing the above embodiment. Figure 4 is a structural block diagram of a task allocation device according to an embodiment of the present invention, such as Figure 4 As shown, the device includes a database, a control server, a control sub-server and a task server, and the above-mentioned control server includes:

[0087] A task information acquiring module 10, configured to acquire task information from the database; wherein, the task information carries tasks;

[0088]A task delivery module 12, connected to the task information acquisition module 10, configured to deliver the task to the control sub-server according to the type of the first task request after receiving the first task request from the control sub-server;

[0089] The above-mentioned control sub-server includes: a task distribution module 20, configured to generate a new distribution task based on a task distribution algorithm according to the above-mentioned task issued by the above-mentioned control server after receiving the second task request from the above-mentioned task server; Allocate to the task server according to the type of the second task request.

[0090] Through the above device, the problem of unreasonable assignment of tasks by the task assignment method in the related art is solved, the timeliness and efficiency of task assignment are improved, and the operating efficiency of the server is improved.

[0091] Before the control server receives the first task request from the control sub-server, the two should establish a connection first, and the control sub-server should register with the control server, so as to provide a basis for subsequent task assignment. Therefore, this embodiment provides a preferred implementation manner, that is, the above-mentioned control server further includes: a link establishment module, configured to establish a TCP link with the above-mentioned control sub-server after receiving the TCP connection request from the above-mentioned control sub-server; The above-mentioned control sub-server also includes: a registration module, which is used to send a registration message to the above-mentioned control server through the above-mentioned TCP link; wherein, the above-mentioned registration message carries fields and the identification number ID of the above-mentioned control sub-server; the above-mentioned control server includes: The above-mentioned control server confirms the identity of the above-mentioned control sub-server according to the above-mentioned field, and parses the above-mentioned ID from the above-mentioned registration message after the confirmation is successful; wherein, the above-mentioned ID is used to identify the above-mentioned control sub-server that receives the above-mentioned task issued by the above-mentioned control server .

[0092] The control server delivers the task to the control sub-server according to the type of the first task request. Generally, the types of the first task requests are divided into two categories: full task requests and incremental task requests. For the two types of first task requests, different task delivery operations are performed respectively. Details are given below. The above task delivery modules include:

[0093] The first task issuing unit is used to analyze the above-mentioned full-scale task request when the type of the above-mentioned first task request is a full-scale task request, and obtain the above-mentioned ID of the above-mentioned control sub-server; query whether the above-mentioned ID is in the task list, if If yes, then send the current task corresponding to the above-mentioned ID to the above-mentioned control sub-server; wherein, the above-mentioned task list records the corresponding relationship between the above-mentioned ID and the task;

[0094] The second task issuing unit is used to analyze the above-mentioned incremental task request when the type of the above-mentioned first task request is an incremental task request, and obtain the above-mentioned ID of the above-mentioned control sub-server; query whether the above-mentioned ID is in the above-mentioned task list , if yes, send the newly added task to the control sub-server, and/or send a task deletion message to the control sub-server; wherein, the task deletion message is used to instruct the control sub-server to delete the task to be deleted.

[0095] Through the above preferred implementation manner, when the first task requests are of different types, corresponding task delivery operations are respectively taken, which improves the efficiency of inter-domain task distribution management and expands the scope of application of task allocation.

[0096] Before the control sub-server receives the second task request from the task server, the two should establish a connection first, and the task server should register with the control sub-server, so as to provide a basis for subsequent task allocation. Therefore, this embodiment provides a preferred implementation manner, that is, the above-mentioned control sub-server further includes: a connection module, configured to receive a TCP connection request from the above-mentioned task server, and the above-mentioned control sub-server establishes a TCP link with the above-mentioned task server; A module, configured to receive a registration message sent by the above-mentioned task server through the above-mentioned TCP link; assign an ID to the above-mentioned task server according to the above-mentioned registration message, and carry the ID in a reply message and send it to the above-mentioned task server; wherein, the above-mentioned ID is used for Identify the task server that receives the distribution task assigned by the control sub-server.

[0097] The control sub-server generates a new distribution task based on the task distribution algorithm according to the task issued by the control server, and then assigns the distribution task to the task server according to the type of the second task request. Generally, there are two types of second task requests: full task requests and incremental task requests. For the two types of first task requests, different task delivery operations are performed respectively. Details are given below. The above task assignment modules include:

[0098] The first task allocation unit is configured to analyze the above-mentioned full-scale task request when the type of the above-mentioned second task request is a full-scale task request, and obtain the above-mentioned ID of the above-mentioned task server; assign the currently managed task corresponding to the ID to the above-mentioned task server;

[0099] The second task allocation unit is configured to analyze the above-mentioned incremental task request when the type of the above-mentioned second task request is an incremental task request, and obtain the above-mentioned ID of the above-mentioned task server; query the ID of the currently managed and controlled task corresponding to the TD state, if the above state is that there is a newly added task in the above task server, assign the above newly added task to the above task server, and if the above state is that there is a task to be deleted in the above task server, send a task deletion message to the above task server; wherein, The task deletion message is used to instruct the task server to delete the task to be deleted.

[0100] Through the above preferred implementation manner, when the second task requests are of different types, corresponding task delivery operations are respectively taken, which improves the efficiency of task distribution management in the domain and expands the scope of application of task allocation.

[0101] The distribution management of inter-domain tasks and the distribution management of intra-domain tasks have been introduced respectively, and the verification management of inter-domain tasks will be introduced below. In this embodiment, the above-mentioned device further includes: a verification server, configured to verify the above-mentioned tasks of the above-mentioned control server.

[0102] Before the verification server verifies the tasks of the control server, it is necessary to establish a connection between the verification server and the control sub-server, and then the verification server can interact with the control server through the control sub-server. Therefore, this embodiment provides a preferred implementation manner, that is, the above-mentioned control sub-server also includes: a link establishment module, configured to receive the TCP connection request of the above-mentioned verification server, and establish a TCP link with the above-mentioned verification server; register the verification server A module configured to send a registration reply message to the verification server after receiving the registration message sent by the verification server through the TCP link; wherein, the registration reply message carries the ID assigned by the control sub-server to the verification server. Through this preferred embodiment, the verification server is connected to the control server through the control sub-server, and the verification server is registered on the control sub-server, which provides a basis for subsequent task verification.

[0103] Preferably, the above-mentioned control server further includes: a verification request module, configured to receive a verification task request sent by the above-mentioned verification server through the above-mentioned control sub-server, analyze the above-mentioned verification task request, and obtain the above-mentioned ID of the above-mentioned verification server; The server sends a verification reply message to the verification server corresponding to the ID; wherein, the verification reply message carries the task to be verified in the control server; the verification server includes a verification module for verifying the task to be verified.

[0104] The method of the present invention can at least bring the following beneficial effects:

[0105] The present invention realizes inter-domain task distribution management by distributing tasks from the control server to each distributed control sub-server; completes the task distribution management in the domain through the task server inside each distributed control sub-server; in order to ensure the success of task completion and accuracy, the control server realizes the verification management of inter-domain tasks by distributing a single task to multiple distributed verification servers to complete the decision verification task after submitting the results. The timeliness and efficiency of task assignment are improved, thereby improving the operating efficiency of the server.

[0106] The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present invention can easily think of changes or Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.