CN112084011A

CN112084011A - Processing method for changing task and related device

Info

Publication number: CN112084011A
Application number: CN202011023758.9A
Authority: CN
Inventors: 陈峥嵘
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2020-09-25
Filing date: 2020-09-25
Publication date: 2020-12-15
Anticipated expiration: 2040-09-25
Also published as: CN112084011B

Abstract

The method and the device for processing the change task, provided by the embodiment of the application, send a first notification to the client node cluster, where the first notification is used for instructing the client node cluster to process the change task. And receiving a candidate script of the task client responding to the change task. And sending a second notice to the consensus client, wherein the second notice is used for indicating the consensus client to audit the candidate scripts. And determining a change script according to the received feedback information. The feedback information is used for indicating the checking result of the consensus client to the candidate script, the change script is used for changing the operation object, and therefore the change script is obtained according to the checking result of at least one consensus client, accuracy of the change script is improved, and because the client node cluster comprises at least three distributed deployed clients, the risk that the change task assignment fails due to abnormal operation of a specific client, and therefore the change task processing process is interrupted, can be reduced.

Description

Processing method for changing task and related device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method for processing a change task, a platform for processing a change task, a client node cluster, a device for processing a change task, and a readable storage medium.

Background

In the current digital age, application scenes based on IT are changing day by day, and in order to adapt to the fast pace of the market, an IT system is continuously updated and upgraded, so that the frequency of data center change is higher and higher, and the potential risk of service interruption caused by change errors is higher and higher. In the related art, a change task is assigned to a specific client, and there is a risk that the processing procedure of the change task is interrupted due to an operation abnormality of the specific client (for example, an operator of the client may not process the change task in time or a feedback information transmission failure of the change task due to a network abnormality).

Disclosure of Invention

The application provides a processing method, a processing device, processing equipment and a readable storage medium for changing tasks, which are used for improving the accuracy of changing scripts and reducing the risk of assignment failure of the changing tasks as follows:

a change task processing platform comprising: a consensus component;

optionally, the consensus component is for:

sending a first notification to a cluster of client nodes, the first notification instructing the cluster of client nodes to process a change task, the cluster of client nodes comprising at least three distributively deployed client nodes;

receiving a candidate script sent by a task client, wherein the candidate script is a script responding to the change task, and the task client is the client node competing for the change task in the client node cluster;

sending a second notification to a consensus client, wherein the second notification is used for instructing the consensus client to audit the candidate script, and the consensus client is the client node in the client node cluster except the task client;

and determining a change script according to the received feedback information, wherein the feedback information is used for indicating the checking result of the consensus client to the candidate script, and the change script is a script for executing the change task.

Optionally, the consensus component is further configured to:

receiving first feedback information sent by the client node, wherein the first feedback information is used for competing for the change task;

selecting the task client from the client nodes sending the first feedback information;

and sending a confirmation notice to the task client, wherein the confirmation notice is used for indicating the task client to compete to the change task.

Optionally, the feedback information includes second feedback information sent by at least one of the consensus clients, where the second feedback information includes: any one of consent information, rejection information, or revision information; the agreement information indicates that the result of the review of the candidate script by the consensus client is passed, the rejection information indicates that the result of the review of the candidate script by the consensus client is not passed, and the revision information is used for indicating a revision script of the candidate script.

Optionally, the consensus component is configured to determine the change script according to the received feedback information, and includes: the consensus component is specifically configured to: executing a first consensus process;

the first consensus process comprises:

in response to receiving the rejection information, ending the first consensus process;

in response to receiving only the consent information, determining the candidate script as the change script;

in response to receiving the revision information, performing a second consensus process;

the second consensus process comprises:

sending a third notification to the task client, wherein the third notification is used for indicating the task client to check the revision script;

receiving third feedback information, wherein the third feedback information indicates that the task client side checks whether the checking result of the revision script passes or fails;

if the third feedback information indicates that the task client side passes the checking result of the revision script, determining that the revision script is the change script;

and if the third feedback information indicates that the task client side does not check the checking result of the revision script, ending the second consensus process.

Optionally, the task of changing comprises: changing operation and operation object;

optionally, the consensus component is further configured to:

after the first notification is sent to the client node cluster, state information of the operation object is generated, wherein the state information is used for indicating that the state of the operation object is a consensus waiting state; the state information is also used for indicating the time for the state of the operation object to keep the consensus waiting state;

after receiving the candidate script sent by the task client, updating the state information, wherein the updated state information is used for indicating that the state of the operation object is a primary consensus state;

the updated state information is also used for indicating the time for keeping the state of the operation object in the primary consensus state;

deleting the state information after the first consensus process is finished;

after the candidate script is determined to be the change script, updating the state information, wherein the updated state information indicates that the state of the operation object is a consensus completion state;

after the second consensus process is entered, updating the state information, wherein the updated state information indicates that the state of the operation object is a secondary consensus state;

and deleting the state information after the second consensus process is finished.

Optionally, the consensus component is further configured to:

and if the state information indicates that the time for the operation object to keep the consensus waiting state meets a preset first time, deleting the state information.

Optionally, the consensus component is further configured to:

and if the state information indicates that the time for the operation object to keep the primary consensus state meets a preset second time, ending the first consensus process.

Optionally, the change task processing platform further includes: an account component;

the account component is used for generating an account set, and the account set comprises at least three accounts having processing authority on the change task; the cluster of client nodes is a collection of clients bound for the account.

Optionally, the change task processing platform further includes: a work order component;

optionally, the work order assembly is for:

generating a required work order number in response to a received change application, wherein the change application comprises change required information, and the required work order number uniquely indicates the change required information;

and generating a change work order number in response to a received task generation instruction, wherein the task generation instruction is generated according to the change requirement information indicated by the requirement work order number, and the change work order number uniquely indicates the change task.

Optionally, the consensus component is further configured to: after the candidate script is determined to be the change script:

taking an account bound by the task client as a first accounting node, and adding the first accounting node to the change script; adding the account bound by the consensus client side with the earliest time for sending the agreement information as a second accounting node to the change script;

the consensus component is further configured to: after said determining that the revised script is the change script:

adding an account bound by the consensus client side for sending the revision information to the change script as a first accounting node; and taking the account bound by the task client as a second accounting node and adding the second accounting node to the change script.

Optionally, the change task processing platform further includes: a contract component;

the contract component is to: generating a change contract, the change contract comprising the demand work order number, the change operation, the operation object, and the account set.

Optionally, the contract component is further for:

calculating the integral of the accounting node according to the accounting node, the change contract and a preset integral rule; the integration rule indicates at least: the point of the first accounting node is larger than the point of the second accounting node.

A cluster of client nodes, comprising: at least three distributively deployed client nodes;

optionally, the client node is configured to: sending first feedback information in response to the received first notification, the first notification being used to instruct the client node to process a change task; the first feedback information is used for competing the change task;

optionally, the task client is configured to: sending a candidate script for responding to the change task, wherein the task client is the client node competing to the change task;

optionally, the consensus client is configured to: sending second feedback information in response to the received second notification, wherein the second notification is used for instructing the consensus client to audit the candidate script, and the consensus client is the client node in the client node cluster except the task client; the second feedback information indicates that the result of the audit of the consensus client on the candidate script is a pass script, a fail script or a revised script of the candidate script.

Optionally, the task client is further configured to:

in response to the received third notification, sending third feedback information; the third notification is used for instructing the task client to check the revision script; the third feedback information indicates that the auditing result of the task client to the revision script is passed or not passed.

A processing method for changing tasks comprises the following steps:

A processing device that alters a task, comprising: a memory and a processor;

the memory is used for storing programs;

the processor is configured to execute the program to implement the steps of the processing method for changing the task.

A readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of processing of change tasks as described above.

According to the technical scheme, the method and the related device for processing the change task send the first notification to the client node cluster, wherein the first notification is used for indicating the client node cluster to process the change task. And receiving a candidate script of the task client responding to the change task. And sending a second notice to the consensus client, wherein the second notice is used for indicating the consensus client to audit the candidate scripts. And determining a change script according to the received feedback information. Because the feedback information is sent after the consensus client side audits the candidate script, the feedback information is used for indicating the audit result of the consensus client side on the candidate script, the change script is the script for executing the change task, and the change script is obtained according to the audit result of at least one consensus client side, the accuracy of the change script is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a task change processing system according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a specific implementation of a processing method for changing tasks according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a method for processing a change task according to an embodiment of the present application;

fig. 4 is a schematic diagram of a preset integration rule according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a task change platform according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of a processing device for changing tasks according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The method for processing a change task according to the embodiment of the present application is applied to, but not limited to, the change task processing system shown in fig. 1, and in this embodiment, the change task processing system includes a change task processing platform 10 and a client node cluster 20.

Specifically, the change task processing platform is a control platform built on a server by using a Spring Cloud micro-service framework, the client node cluster comprises at least three Web clients and/or APP clients, and any client is bound with an account in advance. In this embodiment, an account is registered in advance in a change task processing platform by an operator (e.g., an operation and maintenance worker) of the account, the account accesses the change task processing platform through a client that logs in and is bound to the change task processing platform, as shown in fig. 1, the change task processing platform establishes communication with client nodes in a client node cluster, it should be noted that, in this embodiment, the number of clusters of the client node cluster may include a plurality of clusters, that is, the change task processing platform establishes communication with the plurality of client node clusters, and each client node cluster includes at least three client nodes.

In this embodiment, the change task processing platform communicates with the client node cluster, the MySQL database, the NAS (Network Attached Storage) database, the short message gateway, and the mail server through an API (Application Program Interface), respectively.

In this embodiment, the MySQL database is an external database of a preset change task processing platform, and the NAS is a preset external CMDB database. The short message gateway is used for sending the offline data by the task changing processing platform in a mobile phone short message mode, and the mail server is used for sending the offline data by the task changing processing platform in a mail mode.

It should be further noted that, an SSL (Secure socket Layer, Secure socket protocol) + account password authentication method is adopted between the client node and the change task processing platform to ensure security, and it should be noted that the change task processing platform needs to apply for a Certificate from a CA (Certificate Authority), and may invoke an external CA server, or may complete Certificate issue by a CA component built in the change task processing platform itself, and the account password authentication function component may be integrated inside the platform, or may be implemented by invoking an external authentication system.

It should be noted that fig. 1 is only one optional application scenario provided by the embodiment of the present application, and the embodiment of the present application may also be applied to processing of a change task in other scenarios, for example, in other optional application scenarios, the change task processing platform is not limited to building a control platform on a server in a Spring Cloud micro-service framework, and a change operation object is not limited to a CI object in the CMDB, or the change task processing platform may be associated with the CMDB through a built-in CMDB database.

Fig. 2 is a specific implementation of a change task processing method provided in an embodiment of the present application, and is applied to a process of processing a change task through information interaction between a change task processing platform and a client node cluster, where the change task refers to a change operation performed on a CI object in a CMDB. As shown in fig. 2, the method may specifically include: s201 to S216.

S201, the change task processing platform receives the change application and generates a required work order number.

In this embodiment, the change application includes change requirement information, the change application is uploaded to the change task processing platform by an operator (e.g., operation and maintenance staff) of the account through the bound client node (including the Web client and/or the APP client), and after receiving the change application, the change task processing platform generates a required work order number according to the change requirement information in the change application.

In this embodiment, the required work order number may be a code in a preset format, the required work order number uniquely indicates change requirement information in a change application, and the change task processing platform may store and display the required work order number.

S202, the change task processing platform receives the change task and generates a change work order number.

In this embodiment, an operator of the account checks change demand information in a change application indicated by the demand work order number through the bound client, analyzes the change demand information to obtain at least one change task, and uploads the change task of the demand work order number to the change task processing platform, wherein the change task of the demand work order number is used for completing the change application indicated by the demand work order number.

In this embodiment, the change task processing platform generates a change order number for each change task, where the change order number uniquely indicates the change task, and the change task includes a change operation and an operation object, where the change operation is an operation that needs to be performed to complete the change task, such as deleting a configuration item, adding a configuration item, and/or modifying a configuration item.

It should be noted that, in S201 to S202, a method for acquiring a change task and generating a change order number through information interaction between a client and a change task processing platform may also be included in practical application, and details are not described in this embodiment.

And S203, generating a change contract by the change task processing platform.

The change contract includes a requirement work order number, a change work order number of a change task, a change operation and operation object, and an account set, where the account set is a set of accounts having a processing right for the change task, that is, a set of accounts having an operation right for the operation object in the change task. Table 2 illustrates a schematic diagram of a change contract.

TABLE 2

Requirement work order number	S0032
		Number of change work order	T1001
Change operations	Route addition
		Operation object	CI-01
Account collection	Set			1

It should be noted that table 2 is only an exemplary illustration of the change contract, and in practical applications, the change contract is generated in a preset format, including but not limited to a table form.

In this embodiment, the account set may be selected from a preset account set according to the change task. Each preset account set comprises at least three accounts, and any account can belong to different preset account sets. In this embodiment, the registered accounts are divided into a preset account set in advance according to the operation authority of the operation object, and a schematic diagram of dividing the account set is illustrated in table 2.

TABLE 3

In table 3, "CMDB group" is a number of the CMDB group generated by grouping CI objects in the CMDB according to a preset rule, where "CI object" is an object name in the CMDB group, "account set" is a code or name of a set of accounts having an operation right to the object, and "account" is a name or code of an account included in the account set.

Taking group 1 as an example, the CI object in group 1 includes a router, a switch, or a transport, etc., the set of accounts consisting of the accounts having operation rights to the CI object in group 1 is set 1, and the numbers of the accounts included in set 1 are A, B, C, D and E, respectively.

S204, the change task processing platform sends a first notice to the client node cluster.

In this embodiment, the client node cluster includes at least three client nodes deployed in a distributed manner, the change task processing platform sends the first notification to the client nodes in the client node cluster in response to the task issuing instruction, and the triggering manner of the task issuing instruction may include multiple types, for example, may be triggered by generating a change contract, and for example, may be triggered by clicking an operation on a change work order number.

In this embodiment, the client node is an account-bound client having an operation right for an operation object in the change task, that is, the client node is an account-bound client in an account set recorded in the change contract.

In this embodiment, the first notification is used to notify the destination client to process a change task, where the change task is a change task indicated by the change job ticket number, and the change task includes a change operation and an operation object.

As shown in table 2, the change contract example includes a change order number T1001 in the first notification, and the change task indicated by T1001 includes: and the operation object is CI-01, the change operation is adding a route, and the change task processing platform sends a first notice to the client bound to each account in the n accounts included in the set 1.

In this embodiment, the method for sending the first notification to the client node cluster by the change task processing platform includes an offline mode and/or an online mode, the offline mode includes sending the first notification to a mobile phone number bound to the client node in an offline manner by calling a short message gateway in a mobile phone short message manner, or sending the first notification to a mailbox bound to the client node in an offline manner by calling a java mail component or calling a mail server in a mail manner, and the online mode includes sending the first notification to the client node in a b/s mode or a c/s mode.

S205, the client node sends first feedback information to the task change processing platform in response to the received first notification.

In this embodiment, the first feedback information is used for competing for the change task, and optionally, the first feedback information is a first packet in a preset format.

It should be noted that the preset format includes: the message type field comprises a preset number indicating the message type, the message content field at least comprises a change order number and an operation object, and the account information comprises an account (including but not limited to an account number or a name) bound by a client node sending the message.

Taking the client a bound to the account a as an example, table 4 illustrates a schematic diagram of a first packet sent by the client a, where a packet type field is 101 (application), and indicates that the first packet is used for applying for processing a change task. The message content field is: and CI-01 and T1001, wherein the CI-01 is an operation object, the T1001 is a change order number, and the account information is the name of an account bound by the client node.

TABLE 4

It should be noted that the client bound to the account a sends, to the change task processing platform, a first message shown in table 4, which is used to apply for processing the change task indicated by T1001, and perform a change operation on CI-01.

S206, the task changing processing platform selects a task client from the client nodes which send the first feedback information.

Specifically, the change task processing platform takes a first client node sending the first feedback information as a task client, and sends a confirmation message to the task client, where the confirmation message is used to instruct the task client to compete for the change task, optionally, the confirmation message includes a change order number and a preset first time, and is used to instruct the task client to compete for the change task, and prompt the task client to send the candidate script to the change task processing platform within the time indicated by the first time.

And S207, generating the state information of the operation object by the change task processing platform.

In this embodiment, the operation object state information includes a first information item, a second information item, and a third information item. The first information item comprises an object field, an object state field and a change work order number field, the second information item comprises a message field, an account field and a script field, and the third information item comprises a countdown field.

In this embodiment, after the task client is selected by the change task processing platform, in the generated state information of the operation object, the object field is the name of the operation object, the object state field is consensus waiting, the change work order number field is the change work order number, the message field is the message type of the first message, that is, 101 (application), the account field is an account (number or name) bound by the task client, the script field is null, and the countdown field is the preset first time. It should be noted that the countdown field is updated in real time in a countdown manner.

Table 5 illustrates status information indicating a consensus waiting status, as the above example.

TABLE 5

In table 5, the object field is CI-01, the object status field is consensus waiting, the change work order number field is T1001, the message field is 101, the account field is account a, the script field is null, and the countdown field is 30min (updated in real time in a countdown manner). It should be noted that the state information shown in table 5 indicates that CI-01 is locked by the 101 message submitted by the client bound to account a, waits for the client bound to account a to submit the candidate script within the first time, and does not accept the 101 message submitted by the client bound to another account until the first time count down is 0.

And S208, after the task client receives the confirmation message, sending the candidate script to the change task processing platform in the first time.

In this embodiment, the candidate script is a script that responds to a change task, and it should be noted that the candidate script is completed by an operator of an account bound by the task client and uploaded to the task client.

And S209, after receiving the candidate script sent by the task client, the change task processing platform updates the state information of the operation object.

In this embodiment, the method for updating the state information of the operation object by the task change processing platform in response to receiving the candidate script sent by the task client includes:

and modifying the object state field into one-time consensus, adding the number or name of the candidate script sent by the task client into the script field, and resetting the countdown field to a preset second time.

Table 6 illustrates a type of state information indicating a one-time consensus state.

TABLE 6

The change task processing platform updates the first time in the countdown field in a countdown manner, deletes the status information of the operation target if the change task processing platform does not receive the candidate script within the first time, marks the status of the operation target as the release status, and returns to the execution of S204.

And S210, the change task processing platform sends a second notice to the consensus client.

In this embodiment, the consensus client is a client in the client node cluster except the task client. The second notification is used for notifying the consensus client to audit the candidate scripts.

In this embodiment, the second notification is further configured to instruct the consensus client to send feedback information responding to the second notification within the second time. The manner in which the change task processing platform sends the second notification is referred to as S204 described above.

And S211, after receiving the second notification, the consensus client sends second feedback information to the task change processing platform within a second time.

In this embodiment, the second feedback information sent by the consensus client includes: the information processing method comprises the steps of obtaining agreement information, rejection information or revision information, wherein the agreement information comprises a second message in a preset format, the rejection information comprises a third message in the preset format and a revision script, and the rejection information comprises a fourth message in the preset format.

In this embodiment, the second message is used to indicate that the result of the audit on the candidate script is passed, the third message is used to indicate that the result of the audit on the candidate script is to be modified, the revised script is a script obtained after the candidate script is modified, and the fourth message is used to indicate that the result of the audit on the candidate script is not passed.

In the above example, table 7 illustrates a schematic diagram of a second message, where a message type field is 102, and the second message is used to indicate that the audit result is passed. The message content field is: and CI-01 and T1001, wherein the CI-01 is an operation object, the T1001 is a change work order number, the account information is an account bound by the consensus client sending the second message, and the embodiment takes account B as an example.

TABLE 7

Table 8 illustrates a schematic diagram of a third packet, where the packet type field is 103, and indicates that the third packet is used to indicate that the result is to be modified. The message content field is: and CI-01 and T1001, wherein the CI-01 is an operation object, the T1001 is a change work order number, the account information is an account bound by the consensus client sending the third message, and the embodiment takes account C as an example.

TABLE 8

It should be noted that, in this embodiment, the order of sending the third message and the revision script by the consensus client is not limited, and the third message and the revision script may be sent at the same time, or the revision script may be sent after the third message is sent.

Table 9 illustrates a schematic diagram of a fourth packet, where the packet type field is 104, and the fourth packet is indicated to indicate that the result is a fail result. The message content field is: and CI-01 and T1001, wherein the CI-01 is an operation object, the T1001 is a change work order number, the account information is an account bound by the consensus client sending the fourth message, and the embodiment takes account D as an example.

TABLE 9

And S212, if the task change processing platform does not receive the second feedback information sent by the consensus client within the second time, deleting the state information of the operation object, and returning to the S204.

And S213, if the change task processing platform receives second feedback information sent by at least one consensus client within a second time, determining a change script according to the received second feedback information, and updating the state information of the operation object.

In this embodiment, in the second time, the change task processing platform receives second feedback information from the at least one consensus client, and the second feedback information received by the change task processing platform includes agreement information, rejection information, and/or revision information.

It should be noted that, according to the second feedback information, the method for determining the change script may refer to the flow shown in fig. 3.

S214, the change task processing platform determines a first accounting node and a second accounting node in the account set according to a preset accounting rule, and writes the first accounting node and the second accounting node into a change script.

In this embodiment, the billing rule includes:

1. in the case of the candidate script as the change script, the account bound by the task client is determined as the first accounting node. And determining the account bound by the first consensus client side which sends the consent information to the change task processing platform as a second accounting node.

2. And in the case that the revision script is used as the change script, determining the account bound by the consensus client sending the revision script as a first accounting node, and determining the account bound by the task client as a second accounting node.

It should be noted that, when the state information of the operation object indicates that the state of the operation object is consensus completion, the first accounting node and the second accounting node may be determined according to the state information of the operation object.

S215, after the change script is successfully executed, the change task processing platform deletes the state information of the operation object.

It should be noted that the execution process of the change script can be referred to in the prior art.

S216, the change task processing platform determines the integral of the first accounting node and the integral of the second accounting node at least according to the change contract and a preset integral rule.

In this embodiment, the preset integral rule at least indicates that the integral of the first accounting node is greater than the integral of the second accounting node, the preset integral rule includes a corresponding relationship between a change operation, a task completion time, and an integral value, and may further include a corresponding relationship between a service evaluation and the integral value, and fig. 4 illustrates a preset integral rule.

In this embodiment, according to the preset integral rule, the corresponding relationship between the change operation and the integral value, the corresponding relationship between the task completion time and the integral value, and the corresponding relationship between the service evaluation and the integral value, the integral of the first accounting node is determined as the first integral value, and the integral of the second accounting node is determined as the second integral value, according to the change operation, the task completion time of the change task, and the service evaluation of the received change task in the target contract. Wherein the first integrated value is greater than the second integrated value.

It should be noted that, according to the preset integration rule, specific ways of determining the integration of the first accounting node and the integration of the second accounting node may be seen in the prior art.

It can be seen from the foregoing technical solutions that, in the method for processing a change task provided in this embodiment of the present application, processing of the change task is completed through information interaction between the change task processing platform and the client in the client node cluster, and as can be seen from the method for processing a change task shown in fig. 2, the method at least includes the following beneficial effects:

the method comprises the steps that a change task processing platform sends a first notification to a client node cluster for notifying a target client to process a change task, wherein the client node cluster is a client node bound to an account in an account set, and the account set at least comprises three accounts bound to an operation object and having authority.

And secondly, updating the state information of the operation object by the change task processing platform according to the feedback information (the first feedback information, the second feedback information or the third feedback information) sent by the client, wherein the state information of the operation object at least indicates the current state and the time for keeping the current state of the operation object.

And thirdly, the change task processing platform marks the time of the operation object in the current state in a countdown mode, so that excessive waiting time is avoided, and the timeliness of change task processing is improved.

And fourthly, the change task processing platform sends the first notification to the client bound with the account having the operation authority for the operation object (namely, the client bound with the account having the processing authority for the change task), so that the safety of processing the change task is ensured. Further, the mode of sending the notification (the first notification, the second notification or the third notification) to the client node by the change task processing platform comprises an off-line mode, the client node is not required to be on line in real time, and the timeliness of information interaction is ensured.

Fifthly, the candidate script is used as a change script after passing the audit of at least one consensus client, and the revision script of the candidate script is used as a change script after passing the audit of the task client.

And sixthly, the change task processing platform generates a change contract and determines integral values for the first accounting node and the second accounting node at least according to the change contract and a preset integral rule, wherein the first accounting node and the second accounting node are determined according to the preset accounting rule.

Fig. 3 is a specific implementation manner of determining a change script by a change task processing platform according to an embodiment of the present application, which specifically includes:

s301, the change task processing platform responds to the received rejection information, deletes the state information of the operation object, and returns to S204.

In this embodiment, the change task processing platform updates the second time in the countdown field in a countdown manner, and if the change task processing platform receives rejection information within the second time, deletes the state information of the operation object, marks the state of the operation object as a release state, and returns to execute S204.

S302, the change task processing platform responds to the received consent information and updates the state information of the operation object.

In this embodiment, the method for updating the state information of the operation object by the change task processing platform in response to receiving the approval information includes:

and adding the message type of a second message in the agreement information in the message field, and adding an account bound by the consensus client for sending the agreement information in the account field.

Table 8 illustrates yet another type of status information indicating a one-time consensus status.

Watch 10

It should be noted that, in table 10, the change task processing platform does not receive rejection information or revision information during the countdown of the second time, and when receiving a second message sent by the consensus client bound to the account B, the message type of the second message is added to the message field, and the account B is added to the account field.

And S303, the change task processing platform responds to the received revision information and updates the state information of the operation object.

In this embodiment, the updating the state information of the operation object by the change task processing platform in response to receiving the revision information includes:

and modifying the object state field into secondary consensus, adding the message type of a third message in the revision information into the message field, adding an account bound by a consensus client for sending the revision information into the account field, and adding a revision script in the revision information into the script field.

Table 11 illustrates status information indicating a secondary consensus status.

TABLE 11

It should be noted that table 11 illustrates that, during the countdown of the second time, the change task processing platform does not receive the rejection information, and when receiving the third message sent by the consensus client bound to the account C, the message type of the third message is added to the message field (i.e. 103), the account C is added to the account field, and after receiving the revision script, the name or number of the revision script is added to the script field (taking the script C as an example).

And S304, after receiving the revision information, the change task processing platform sends a third notification to the task client.

In this embodiment, the third notification is used to notify the task client to check the revision script, and the method for sending the third notification may refer to S204 described above.

And S305, the task client sends third feedback information to the task change processing platform.

In this embodiment, the third feedback information is used to indicate that the result of the review on the revision script passes or fails, and optionally, the third feedback information includes any one of revision approval information or revision rejection information, where the revision approval information is a fifth message in the preset format, the fifth message indicates that the result of the review on the revision script by the task client passes, the revision rejection information is a sixth message in the preset format, and the sixth message indicates that the result of the review on the revision script by the task client does not pass.

In this embodiment, the fifth packet includes a packet type field, a message content field, and account information. The message type field indicates that the fifth message is used for indicating that the checking result of the revision script is passed, and the message content field comprises an operation object, a number of a change worksheet and revision agreement.

Table 12 illustrates a schematic diagram of a fifth packet.

TABLE 12

In the fifth message shown in table 12, the message type field is 105, and the message content field includes: CI-01, T1001 and an approval revision, wherein the CI-01 is an operation object, the T1001 is a number of a change order, and the approval revision indicates that the task client passes the auditing result of the revision script. And the account information is that the account bound by the task client side sending the fifth message is an account A.

In this embodiment, the sixth packet includes a packet type field, a message content field, and account information. The message type field indicates that the sixth message is used for indicating that the checking result of the revision script does not pass, and the message content field comprises an operation object, a number of a change worksheet and revision refusal.

Table 13 illustrates a schematic diagram of a sixth packet.

Watch 13

In the fifth message shown in table 13, the message type field is 106, and the message content field includes: CI-01, T1001 and refusal revision, wherein, CI-01 is an operation object, T1001 is a number of a change order, and refusal revision indicates that the task client end does not pass the auditing result of the revision script. And the account information is that the account bound by the task client side sending the sixth message is an account A.

S306, if the third feedback information received by the change task processing platform is revision approval information, determining that the revision script is the change script, and updating the state information of the operation object.

In this embodiment, if the change task processing platform receives the revision approval information and indicates that the task client passes the review result of the revision script, determining that the revision script is the change script, and updating, by the change task processing platform, the state information of the operation object and updating the state information of the operation object, includes:

and modifying the object state field into a consensus completion, adding the message type of a fifth message in the third feedback information in the message field, adding an account bound by a task client for sending the third feedback information in the account field, adding a modification script in the script field, and deleting the second time in the countdown field.

Table 14 illustrates status information indicating a consensus completion status.

TABLE 14

It should be noted that, in table 14, when the result information in the received fifth message is that revision is approved, the change task processing platform modifies the object status field to be consensus-completed, adds the message type of the fifth message in the message field (i.e. 105), adds the account a in the account field, and adds the name or number of the revision script in the script field (taking the script C as an example).

And S307, if the third feedback information received by the change task processing platform is the revision refusing information, the change task processing platform updates the state information of the operation object.

In this embodiment, if the change task processing platform receives the revision refusing information, indicates that the result of checking the revision script by the task client is not passed, and indicates that the result of checking the revision script by the task client is not passed, the method for updating the state information of the operation object by the change task processing platform includes:

resetting the object state field to be in a first consensus state, deleting the message type of a third message in the message type field, deleting an account bound by a consensus client in the account field, and deleting the name or the number of a revision script in the script field.

In this embodiment, after the state information of the operation target is updated by the change task processing platform, the state information indicating the primary consensus state is shown in table 15.

Watch 15

Table 15 illustrates that, when the change task processing platform receives the sixth message, the object status field is modified to be a consensus, and "103", "account C", and "script C" in table 11 are deleted, that is, the record related to the rejection information (including the sender of the rejection information, the third message, and the revision script) is deleted, it should be noted that an optional specific implementation form for deleting the record related to the rejection information is as follows: deletion marks are added to the sender of the rejection message, the third message and the revision script, and the deletion marks of the data indicate that the data is deleted, for example, a diagonal mark on "103" shown in table 15 indicates that "103" is deleted. The present application does not limit the specific implementation form of deleting the record related to the rejection information.

It should be noted that, in the case that the third feedback information is the revision rejection information, the method for changing the state information of the task processing platform to update the operation object is not limited to the method illustrated in table 15, and may include other various optional methods. For example, the object status field is reset to a primary consensus status, the message type of the sixth message in the third feedback information is added to the message field, the account bound by the task client sending the third feedback information is added to the account field, and the candidate script is added to the script field.

It should be further noted that after the change task processing platform resets the object status field to the primary consensus status, the second feedback information sent by the consensus client is continuously received, and S213 is executed, that is, the change script is determined according to the second feedback information. This embodiment will not be described in detail.

And S308, if the change task processing platform only receives the agreement information in the second time, updating the state information of the operation object, and determining the candidate script as the change script.

In this embodiment, if only the approval information is received within the second time, the method for changing the state information of the task processing platform to update the operation object includes: the object field is modified to consensus completion.

It can be seen from the foregoing embodiment that, when the second feedback information includes only the agreement information, the change task processing platform determines that the candidate script is the change script, and thus, the audit result of the candidate script passing through the at least one consensus client is passed, and the audit result of the candidate script not passing through the consensus client is not passed or is to be revised, thereby improving the accuracy of the change script and avoiding a change error caused by inaccurate change script.

Furthermore, when the second feedback information comprises revision information, the revision script in the revision information is rechecked, and the rechecked revision script is used as the change script, so that the accuracy of the change script is further improved.

Fig. 5 illustrates a structure of a change task processing platform according to an embodiment of the present application, and as illustrated in fig. 5, the change task processing platform includes: a Web (World Wide Web) portal 501, a work order component 502, an account component 503, a consensus component 504, and a contract component 505, and the present embodiment specifically introduces the structure and function of the components in the change task processing platform.

In this embodiment, the web portal is an access entry of the client built by the tomcat server, and is configured to provide an API (Application Programming Interface) for the client.

Optionally, the web portal provides an API for the node client for data interaction between the client nodes in the client node cluster and the change task processing platform. The client node comprises a webpage client and/or a mobile phone client.

In this embodiment, the consensus component is configured to:

sending a first notification to the cluster of client nodes, the first notification instructing the cluster of client nodes to process the change task, the cluster of client nodes comprising at least three distributively deployed client nodes.

And receiving a candidate script sent by the task client, wherein the candidate script is a script responding to the change task, and the task client is a client node competing to the change task in the client node cluster.

And sending a second notice to the consensus client, wherein the second notice is used for indicating the consensus client to audit the candidate scripts, and the consensus client is a client node except the task client in the client node cluster.

And determining a change script according to the received feedback information, wherein the feedback information is used for indicating the consensus client to the audit result of the candidate script, and the change script is a script for executing the change task.

Optionally, the consensus component is further configured to:

and receiving first feedback information sent by the client node, wherein the first feedback information is used for competing for the change task.

And selecting a task client from the client nodes sending the first feedback information.

And sending a confirmation notice to the task client, wherein the confirmation notice is used for indicating the task client to compete to change the task.

Optionally, the feedback information includes second feedback information sent by at least one consensus client, and the second feedback information includes: any one of consent information, rejection information, or revision information. The agreement information indicates that the audit result of the consensus client to the candidate script is passed, the rejection information indicates that the audit result of the consensus client to the candidate script is not passed, and the revision information is used for indicating a revision script of the candidate script.

Optionally, the consensus component is configured to determine the change script according to the received feedback information, and includes: the consensus component is specifically configured to: a first consensus process is performed.

The first consensus process comprises:

and ending the first consensus process in response to receiving the rejection information.

In response to receiving only consent information, the candidate script is determined to be a change script.

And entering a second consensus process in response to receiving the revision information.

The second consensus process comprises:

and sending a third notice to the task client, wherein the third notice is used for instructing the task client to audit the revision script.

And receiving third feedback information, wherein the third feedback information indicates that the task client side checks whether the checking result of the revision script is passed or not passed.

And if the third feedback information indicates that the task client side passes the checking result of the checking and revising script, determining the revising script as the change script.

And if the third feedback information indicates that the task client side does not pass the auditing result of the auditing and revising script, ending the second consensus process.

Optionally, the task of changing comprises: change operations and operation objects.

Optionally, the consensus component is further configured to:

after sending the first notification to the cluster of client nodes, state information for the operands is generated, the state information indicating that the state of the operands is consensus waiting state. The state information is also used to indicate a time for which the state of the operation object remains in the consensus waiting state.

And after receiving the candidate script sent by the task client, updating the state information, wherein the updated state information is used for indicating that the state of the operation object is a primary consensus state.

Optionally, the updated state information is further used to indicate a time when the state of the operation object remains in the one-time consensus state.

And deleting the state information after finishing the first consensus process.

And after the candidate script is determined to be the change script, updating the state information, wherein the updated state information indicates that the state of the operation object is the consensus completion state.

And after entering a second consensus process, updating the state information, wherein the updated state information indicates that the state of the operation object is a secondary consensus state.

And deleting the state information after finishing the second consensus process.

Optionally, the consensus component is further configured to:

and if the state information indicates that the time for the operation object to keep the consensus waiting state meets the preset first time, deleting the state information.

The consensus component is further configured to:

and if the state information indicates that the time for the operation object to keep the primary consensus state meets the preset second time, ending the first consensus process.

In this embodiment, the account component is configured to generate an account set, where the account set includes at least three accounts having processing rights to the change task. The client node cluster is a collection of clients bound for an account.

In this embodiment, the work order assembly is used for:

and generating a required work order number in response to the received change application, wherein the change application comprises change requirement information, and the required work order number uniquely indicates the change requirement information.

And generating a change work order number in response to the received task generation instruction, generating the task generation instruction according to the change requirement information indicated by the requirement work order number, and uniquely indicating a change task by the change work order number.

Optionally, the consensus component is further configured to: after determining the candidate script as the change script:

and taking the account bound by the task client as a first accounting node, and adding the first accounting node to the change script. And adding the account bound by the consensus client with the earliest time for sending the agreement information as a second accounting node to the change script.

The consensus component is further configured to:

after determining that the revised script is the changed script: and taking the account bound by the consensus client sending the revision information as a first accounting node and adding the first accounting node to the change script. And taking the account bound by the task client as a second accounting node, and adding the second accounting node to the change script.

In this embodiment, the contract component is configured to: and generating a change contract, wherein the change contract comprises a demand work order number, a change operation, an operation object and an account set.

Optionally, the contract component is further for:

and calculating the integral of the accounting node according to the accounting node, the change contract and a preset integral rule. The integration rule indicates at least: the point of the first accounting node is larger than the point of the second accounting node.

An embodiment of the present application further provides a client node cluster, including: at least three distributively deployed client nodes.

The client node is configured to: in response to receiving the first notification, sending first feedback information, the first notification instructing the client node to process the change task. The first feedback information is used for competing for the change task.

The task client is used for: and sending a candidate script for responding to the change task, wherein the task client is a client node competing to the change task.

The consensus client is configured to: and sending second feedback information in response to the received second notification, wherein the second notification is used for indicating a consensus client to audit the candidate scripts, and the consensus client is a client node in the client node cluster except the task client. The second feedback information indicates that the result of the audit of the candidate script by the consensus client is a pass script, a fail script or a revised script of the candidate script.

Optionally, the task client is further configured to:

in response to the received third notification, third feedback information is transmitted. The third notification is used for instructing the task client to audit the revision script. And the third feedback information indicates that the auditing result of the task client to the revision script is passed or not passed.

Fig. 6 is a schematic structural diagram of a processing device for the change task, and the device may include: at least one processor 601, at least one communication interface 602, at least one memory 603, and at least one communication bus 604;

in the embodiment of the present application, the number of the processor 601, the communication interface 602, the memory 603, and the communication bus 604 is at least one, and the processor 601, the communication interface 602, and the memory 603 complete communication with each other through the communication bus 604;

the processor 601 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement embodiments of the present invention, or the like;

the memory 603 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory), etc., such as at least one disk memory;

the processor can execute the program stored in the memory, and implement the steps of the processing method for changing the task provided by the embodiment of the application, as follows:

An embodiment of the present application further provides a readable storage medium, where the readable storage medium may store a computer program suitable for being executed by a processor, and when the computer program is executed by the processor, the computer program implements the steps of the processing method for changing tasks provided in the embodiment of the present application, as follows:

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A change task processing platform, comprising: a consensus component;

the consensus component is to:

2. The change task processing platform of claim 1, wherein the consensus component is further configured to:

3. The change task processing platform according to claim 1 or 2, wherein the feedback information comprises second feedback information sent by at least one of the consensus clients, and the second feedback information comprises: any one of consent information, rejection information, or revision information; the agreement information indicates that the result of the review of the candidate script by the consensus client is passed, the rejection information indicates that the result of the review of the candidate script by the consensus client is not passed, and the revision information is used for indicating a revision script of the candidate script.

4. The change task processing platform of claim 3, wherein the consensus component is configured to determine a change script based on the received feedback information, comprising: the consensus component is specifically configured to: executing a first consensus process;

the first consensus process comprises:

the second consensus process comprises:

5. The change task processing platform of claim 4, wherein the change tasks comprise: changing operation and operation object;

the consensus component is further configured to:

deleting the state information after the first consensus process is finished;

6. The change task processing platform of claim 5, wherein the consensus component is further configured to:

if the state information indicates that the time for the operation object to keep the consensus waiting state meets a preset first time, deleting the state information;

the consensus component is further configured to:

7. The change task processing platform of claim 4, further comprising: an account component;

8. The change task processing platform of claim 7, further comprising: a work order component;

the work order assembly is used for:

9. The change task processing platform of claim 8, wherein the consensus component is further configured to: after the candidate script is determined to be the change script:

10. The change task processing platform according to claim 9, further comprising: a contract component;

11. The change task processing platform of claim 10, wherein the contract component is further configured to:

12. A cluster of client nodes, comprising: at least three distributively deployed client nodes;

the client node is configured to: sending first feedback information in response to the received first notification, the first notification being used to instruct the client node to process a change task; the first feedback information is used for competing the change task;

the task client is used for: sending a candidate script for responding to the change task, wherein the task client is the client node competing to the change task;

the consensus client is configured to: sending second feedback information in response to the received second notification, wherein the second notification is used for instructing the consensus client to audit the candidate script, and the consensus client is the client node in the client node cluster except the task client; the second feedback information indicates that the result of the audit of the consensus client on the candidate script is a pass script, a fail script or a revised script of the candidate script.

13. The client node cluster of claim 12, wherein the task client is further configured to:

14. A method for processing a change task, comprising:

15. A processing apparatus that changes tasks, comprising: a memory and a processor;

the memory is used for storing programs;

the processor is configured to execute the program to realize each step of the method for processing a change task according to any one of claims 14.

16. A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of processing a change task according to claim 14.