Project process processing method and device, storage medium and computer equipment

Abstract

The invention relates to the technical field of computers, in particular to a project process processing method and device, a storage medium and computer equipment. The method comprises the following steps: acquiring project original data; inputting the project original data into a preset project type identification model, and determining a target project type of the project original data; based on a preset project flow processing link corresponding to the target project type, determining a target processing link required for processing the project original data; creating a corresponding alliance chain node for the target processing link so as to construct an alliance chain according to the alliance chain node; and publishing the project original data to an alliance chain, so that alliance chain nodes process the project original data in sequence to obtain a project processing result. According to the method, automatic and intelligent operation of the project process is realized, and credibility, traceability and tampering resistance of data in the whole process can be ensured.

Description

Project process handling methods, devices, storage media, and computer equipment Technical Field

[0001] This application relates to the field of computer technology, and in particular to a project workflow processing method, apparatus, storage medium, and computer equipment. Background Technology

[0002] In the field of project process management, various enterprises, universities, and organizations generally face the dual challenges of low management efficiency and insufficient credibility. Projects typically involve a series of unique, complex, and interconnected activities that must achieve a final goal within specific time, budget, and resource constraints, according to established standards. However, in the process of handling project workflows using relevant technologies, key stages such as project initiation, multi-departmental review, execution, and archiving still rely heavily on manual methods for advancement and coordination. This highly manual operation mode results in a low overall level of intelligence, and due to the inherent subjectivity of human operation, errors are easily introduced in process judgment and execution. Furthermore, limitations in individual mastery of complex process knowledge further increase management uncertainty and risk. Moreover, traditional project data storage often adopts centralized database solutions, which pose a single point of failure risk, concentrate data management pressure, and make it difficult to guarantee security and transparency. In addition, due to the numerous stages, approval nodes, and complex processing steps throughout the project process, it is difficult to assign responsibility after project materials are modified. Summary of the Invention

[0003] In view of this, this application provides a project process processing method, apparatus, storage medium and computer equipment to realize the automated and intelligent operation of the project process, and to ensure that the data throughout the process is reliable, traceable and tamper-proof.

[0004] According to one aspect of this application, a project workflow processing method is provided, comprising: acquiring raw project data; inputting the raw project data into a preset project type identification model to determine the target project type of the raw project data; determining a target processing step required to process the raw project data based on a preset project workflow processing step corresponding to the target project type; creating a corresponding consortium blockchain node for the target processing step, so as to construct a consortium blockchain based on the consortium blockchain node; and publishing the raw project data to the consortium blockchain, so that the consortium blockchain nodes process the raw project data sequentially to obtain a project processing result.

[0005] According to another aspect of this application, a project workflow processing apparatus is provided, comprising: an acquisition module for acquiring raw project data; a construction module for inputting the raw project data into a preset project type identification model to determine a target project type of the raw project data; and, based on a preset project workflow processing step corresponding to the target project type, determining a target processing step required to process the raw project data; and, creating a corresponding consortium blockchain node for the target processing step to construct a consortium blockchain based on the consortium blockchain node; and a processing module for publishing the raw project data to the consortium blockchain so that the consortium blockchain nodes process the raw project data sequentially to obtain a project processing result.

[0006] According to another aspect of this application, a readable storage medium is provided having a program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described project flow processing method.

[0007] According to another aspect of this application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the steps of the above-described project process handling method.

[0008] By employing the above technical solutions, this application provides a project workflow processing method, apparatus, storage medium, and computer equipment. First, it processes raw project data using a project type identification model to determine the target project type and corresponding target processing steps, achieving intelligent matching and automated initialization of the project workflow, thus improving the accuracy and efficiency of workflow planning. Then, it creates consortium blockchain nodes for each target processing step and constructs a consortium blockchain, thereby publishing the raw project data to the consortium blockchain. This allows the consortium blockchain nodes to process the raw project data sequentially, ensuring strict sequential execution of the workflow, non-repudiation of operations, and tamper-proof data. Finally, through full-process data on-chaining, it achieves intelligent matching, orderly execution, reliable evidence storage, and complete traceability of the entire project workflow.

[0009] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0010] The accompanying drawings, which are included to provide a further understanding of this application and constitute a part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 shows a schematic flowchart of a project workflow processing method provided in an embodiment of this application; Figure 2 shows a schematic flowchart of a project workflow processing method provided in another embodiment of this application; Figure 3 shows a structural block diagram of a project workflow processing apparatus provided in an embodiment of this application. Detailed Implementation

[0011] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0012] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0013] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “attached” to another element, it can be directly connected or attached to the other element, or there may be intermediate elements. Furthermore, “connected” or “attached” as used herein can include wireless connections or wireless interconnections. The term “and / or” as used herein includes all or any unit and all combinations of one or more associated listed items.

[0014] Exemplary embodiments according to this application will now be described in more detail with reference to the accompanying drawings. However, these exemplary embodiments may be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein. It should be understood that these embodiments are provided so that the disclosure of this application is thorough and complete, and that the concept of these exemplary embodiments is fully conveyed to those skilled in the art.

[0015] This application provides a project workflow processing method, as shown in Figure 1. The method includes: step 101, obtaining the original project data.

[0016] Step 102: Input the original project data into the preset project type recognition model to determine the target project type of the original project data.

[0017] Step 103: Based on the preset project process processing steps corresponding to the target project type, determine the target processing steps required to process the project's original data.

[0018] Step 104: Create corresponding consortium blockchain nodes for the target processing stage, so as to build a consortium blockchain based on the consortium blockchain nodes.

[0019] Step 105: Publish the original project data to the consortium blockchain so that the consortium blockchain nodes can process the original project data in sequence to obtain the project processing results.

[0020] The project workflow processing method provided in this application can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the project workflow processing method, but is not limited to the above forms.

[0021] This embodiment first processes the raw project data using a project type identification model to determine the target project type and its corresponding target processing stage. Then, it creates consortium blockchain nodes for each target processing stage and constructs the consortium blockchain. Trigger codes are configured for the consortium blockchain nodes based on a hash chain structure, and asymmetric encryption is used to generate public-private key pairs for the consortium blockchain nodes. During project execution, the raw project data flows between consortium blockchain nodes based on the trigger codes. After each consortium blockchain node completes its processing, it digitally signs the result and broadcasts the trigger code of the consortium blockchain node corresponding to the next target processing stage to the consortium blockchain. Internal control within the consortium blockchain nodes is achieved through participating nodes and their internal trigger codes. Simultaneously, all nodes are divided into full nodes and light nodes according to their functions for distributed storage. When processing fails, the process is rolled back sequentially, and the rolled-back data is synchronously stored, thereby achieving intelligent matching, orderly execution, trusted storage, and complete traceability throughout the entire project process.

[0022] In another embodiment of this application, a project workflow processing method is provided, as shown in Figure 2. The method includes: step 201, obtaining raw project data; inputting the raw project data into a preset project type identification model; determining a first candidate project type matching the raw project data based on the project leader information in the raw project data and through a first type judgment unit in the project type identification model; determining a second candidate project type matching the raw project data based on project feature words in the raw project data and through a second type judgment unit in the project type identification model; identifying the project types that are the same in the first and second candidate project types as the target project type; and determining the target processing step required to process the raw project data based on the preset project workflow processing step corresponding to the target project type.

[0023] In this step, raw project data is obtained through a data interface. Then, the raw project data is input into a preset project type identification model to determine the target project type that matches the raw project data. Based on the preset project workflow processing steps corresponding to the target project type, the target processing steps required to process the raw project data are determined.

[0024] Specifically, the project type identification model includes a first type judgment unit and a second type judgment unit. After the raw project data is input into the model, it first enters the first type judgment unit. This unit matches the project leader information in the raw data with the preset project personnel information corresponding to multiple preset project types stored internally. The preset project type corresponding to the preset project personnel information that matches the project leader information is identified as the first candidate project type. Next, the raw project data is input into the second type judgment unit. This unit matches the project feature words in the raw data with the preset feature words corresponding to multiple preset project types stored internally. If a project feature word in the raw data is contained in a preset project type, that preset project type is identified as the second candidate project type. Finally, the project type identification model identifies the project types that are identical between the first and second candidate project types as the target project type matched with the raw project data. Simultaneously, the project type identification model internally stores the preset project process steps corresponding to each preset project type, multiple preset processing nodes included in each preset project process step, a first preset processing order among all preset project process steps corresponding to each preset project type, and a second preset processing order among all preset processing nodes included in each preset project process step. Therefore, the preset project process step corresponding to the target project type is determined as the target processing step required to process the project's original data. Here, if multiple identical project types exist between the first and second candidate project types, any one of them can be randomly selected.

[0025] For example, the raw project data includes structured data such as basic project information, project leader information, project budget, project timeline, and project keywords. Basic project information may include project name, project completion time, main project content, and whether it is a research and development project. Project keywords describe the project field, the technologies used, etc. For example, a chemical synthesis research project corresponds to keywords such as chemistry, synthesis, research, and scientific research. The first and second type judgment units can be constructed based on a classifier.

[0026] Step 202: Create corresponding consortium blockchain nodes for the target processing stage to build a consortium blockchain based on the consortium blockchain nodes; configure public and private keys generated based on asymmetric encryption algorithms for the consortium blockchain nodes; sort the consortium blockchain nodes according to the first preset processing order between the target processing stages to determine the first node order; configure the trigger code of the first consortium blockchain node in the first node order as a preset first initial public value; configure the trigger codes of the other consortium blockchain nodes in the first node order (excluding the first one) as the hash value of the trigger code of the previous consortium blockchain node of the other consortium blockchain nodes.

[0027] In this step, a corresponding consortium blockchain node is deployed for each target processing stage, with a one-to-one correspondence between the target processing stage and the consortium blockchain node. These nodes collectively manage the consortium blockchain, thus building it based on a distributed network. Furthermore, according to the project flow formed by all target processing stages, corresponding smart contracts are created within the consortium blockchain. Additionally, each consortium blockchain node is configured with a key pair generated using an asymmetric encryption algorithm: a public key and a private key. The private key of each consortium blockchain node is possessed only by the node itself and is used to encrypt the data it owns, generating a digital signature for the node. The public key of each node can be broadcast within the consortium blockchain to all other consortium blockchain nodes.

[0028] It's worth noting that this step configures a trigger code for each consortium blockchain node based on hash calculation. This trigger code is used to initiate the consortium blockchain node's processing. Specifically, the consortium blockchain nodes corresponding to the target processing stages are sorted according to a first preset processing order to determine the first node order. Next, the trigger code of the first consortium blockchain node in the first node order is configured as a first initial public value. This first initial public value can be a random number and is broadcast throughout the consortium blockchain. The trigger codes of other consortium blockchain nodes in the first node order, excluding the first node, are hash values ​​obtained by hashing the trigger code of their predecessor consortium blockchain node; only the other consortium blockchain nodes themselves know these hash values. For example, the trigger code of the first consortium blockchain node in the first node order is H1, where H1 is the first initial public value, and the trigger code of the second consortium blockchain node in the first node order is Hash(H1), where Hash() represents a hash function, and so on.

[0029] Step 203: Configure a preset first initial public value trigger code for the project's original data, and package the project's original data carrying the trigger code into a data packet and publish it to the consortium blockchain; the current consortium blockchain node whose trigger code matches the data packet processes the data packet to obtain the processing result of the current consortium blockchain node; the current consortium blockchain node uses its private key to digitally sign the processing result of the current consortium blockchain node, and performs a hash calculation on the trigger code of the current consortium blockchain node; the current consortium blockchain node updates the data packet according to the signed processing result, and configures the hashed trigger code as the trigger code of the updated data packet; the current consortium blockchain node broadcasts the updated data packet on the consortium blockchain, so that the next consortium blockchain node whose trigger code matches the updated data packet processes the data packet using the public key of the current consortium blockchain node, until all consortium blockchain nodes have completed processing and the project processing result is obtained.

[0030] In this step, the project initiator first publishes the original project data to the consortium blockchain in the form of data packets. At this time, the data packet carries the trigger code (i.e., the first initial public value) of the first consortium blockchain node in the public first node sequence and is transmitted on the consortium blockchain. Each consortium blockchain node checks whether the trigger code carried in the data packet matches its own trigger code. Only the trigger code of the first consortium blockchain node in the first node sequence matches the trigger code carried in the data packet. Therefore, the first consortium blockchain node in the first node sequence is authorized to process the data packet as the current consortium blockchain node. After the first consortium blockchain node completes its processing, it digitally signs the processing result with its private key and hashes its trigger code. The signed processing result and its hashed trigger code are then packaged into a data packet and broadcast on the consortium blockchain. It can be understood that the data packet broadcast on the consortium blockchain is now updated. Similarly, each consortium blockchain node checks whether the trigger code carried in the updated data packet matches its own trigger code. At this point, only the trigger code of the second-ranked consortium blockchain node in the first node sequence matches the trigger code carried in the updated data packet. Therefore, the second-ranked consortium blockchain node in the first node sequence is authorized to process the data packet. This node first uses the public key of the previous consortium blockchain node (i.e., the first-ranked node in the first node sequence) to decrypt the signed processing result in the updated data packet, verifying that the data packet indeed comes from the legitimate previous consortium blockchain node, and then processes the updated data packet. This process continues until the last consortium blockchain node in the first node sequence has finished processing, at which point the final project processing result is output.

[0031] In this embodiment, each consortium blockchain node only knows its own trigger code beforehand. Only after the current consortium blockchain node completes its processing work will it calculate and broadcast the trigger code of the next consortium blockchain node, thereby triggering the next target processing stage. Due to the one-way nature of the hash function, no consortium blockchain node can extract and predict the trigger codes of other consortium blockchain nodes, thus preventing skipping the current target processing stage to prematurely trigger the next target processing stage. If an attacker attempts to tamper with the data of a target processing stage in the past, it will cause the trigger code of that target processing stage to change, thereby invalidating the trigger codes of all subsequent target processing stages and being immediately detected, thus preventing data tampering.

[0032] Step 204: Based on the multiple preset processing nodes included in the target processing stage, create multiple participating nodes for the consortium blockchain node corresponding to the target processing stage; configure internal trigger codes for the participating nodes within the consortium blockchain node based on hash calculation; and control the participating nodes within the consortium blockchain node to process the original project data sequentially based on the internal trigger codes.

[0033] In this step, based on the multiple pre-defined processing nodes included in the target processing stage, multiple participating nodes are deployed within the consortium blockchain node corresponding to the target processing stage. It should be noted that since different target processing stages may include the same pre-defined processing node, a participating node may belong to multiple consortium blockchain nodes simultaneously.

[0034] This step configures an internal trigger code for each participating node in each consortium blockchain node based on hash calculation. The internal trigger code is used to trigger the processing work of the participating nodes within the consortium blockchain node. Specifically, according to the second preset processing order among the preset processing nodes within the target processing stage, the participating nodes in the consortium blockchain node are sorted to determine the second node order. The internal trigger code of the participating node at the first position in the second node order is the second initial public value. The internal trigger codes of other participating nodes in the second node order, excluding the first position, are hash values ​​obtained by hashing the internal trigger code of their predecessor, and are known only to the other participating nodes themselves. For example, the internal trigger code of the first participating node in the second node order is H2, where H2 is the second initial public value, while the internal trigger code of the second participating node in the second node order is Hash(H2), and so on.

[0035] Once the current consortium blockchain node is authorized for processing, its internal processing flow begins. At this point, the current consortium blockchain node adds a second initial public value (based on the second node sequence) to the data packet broadcast by the previous consortium blockchain node. This ensures that the first participating node in the second node sequence is authorized for processing. Similar to how consortium blockchain nodes are authorized sequentially based on trigger codes, each participating node within the current consortium blockchain node is also authorized sequentially based on its internal trigger code. This will not be elaborated further in this embodiment.

[0036] Here, the processing result of the consortium blockchain node can be the processing result of the last participating node in the second node sequence corresponding to the consortium blockchain node, or it can be the processing result of each participating node within the consortium blockchain node. This embodiment does not impose any specific restrictions.

[0037] It should be noted that the processing results of consortium blockchain nodes or participating nodes include operational metadata and business content data. Operational metadata includes the processing entity and processing time, indicating who performed the action and when. Business content data includes the processing content and processing result, indicating what was done and what the result was. Furthermore, the same hash function is used for all hash calculations in this embodiment.

[0038] Step 205: Divide the consortium blockchain nodes and participating nodes into full nodes and light nodes; configure full nodes to store all data generated in the consortium blockchain; configure light nodes to store the portion of data generated in the consortium blockchain that is related to themselves.

[0039] In this step, the consortium blockchain stores all the data it generates, such as the processing results of consortium blockchain nodes or participating nodes. Further, this step categorizes consortium and participating nodes into full nodes and light nodes based on their functions. Full nodes store all the data generated in the consortium blockchain, while light nodes store the relevant portion of the data generated in the consortium blockchain. Specifically, if a consortium or participating node's function requires a global perspective, it is designated as a full node, storing a copy of the consortium blockchain's data. If a consortium or participating node's function only needs to focus on data related to its own business, it is designated as a light node, storing only the data relevant to itself to conserve resources.

[0040] Step 206: If the processing result of the consortium node or participating node is not passed, a rollback operation is performed in the consortium chain node or participating node according to the first node order or the second node order; the data generated by the rollback operation is stored in the consortium chain.

[0041] In this step, if the processing result of a certain consortium node or participating node is "not approved," the processing flow needs to roll back to the previous node in the first or second node sequence. At this time, the consortium blockchain will retrieve all data generated after the rollback and store it within the consortium blockchain as well. This ensures the complete traceability of the project lifecycle. Therefore, in the event of anomalies such as approval rollbacks, the operation records of the rolled-back portion can be completely and immutably retained, providing a foundation for subsequent accountability and auditing.

[0042] In another embodiment of this application, the original project data includes the blockchain identity information of the project leader, processing completion time, project name, project department, main project content, responsible person, project category, budget, total project investment (including tax), project outsourcing budget (including tax), and whether it is a research and development project. The target project type matched with the original project data is a tender preparation project.

[0043] Optionally, the target processing steps and preset processing nodes corresponding to the bidding preparation project are shown in Table 1.

[0044] Table 1

[0045] The processing results of the alliance nodes corresponding to the preparation of the bidding plan include: (1) The processing results of the participating nodes corresponding to the preparation of the procurement plan: blockchain identity information of the project leader, processing completion time, list of target items, basic project information, selection of standard contract text, qualification requirements (general qualification requirements, special qualification requirements, reasons for adopting the bidding method), preliminary review item settings, evaluation method settings, expert selection, generation of bidding plan, form printing, PDF viewing, attachments, bidding plan details, etc.; (2) The processing results of the participating nodes corresponding to the pre-review of the procurement plan of the agency: blockchain identity information of the procurement service department handler 1, processing completion time, review opinions of the procurement service department handler 1, revised project bidding plan, revised Project bidding scheme version number; review opinions of the head of the procurement service department, review opinions of the manager of the procurement service department, etc.; (3) Review results of the corresponding participating nodes by the leader of the undertaking department: blockchain identity information of the leader of the undertaking department, processing completion time, review opinions of the head of the department where the project leader is located, revised project bidding scheme, revised project bidding scheme version number, etc.; (4) Review results of the corresponding participating nodes by the person in charge of the procurement management department: blockchain identity information of the person in charge of the procurement management department, processing completion time, review opinions of the person in charge of the procurement management department, revised project bidding scheme, revised project bidding scheme version number, etc.; (5) Review results of the corresponding participating nodes by the manager of the procurement management department: (6) The legal department (legal affairs) reviews the processing results of the corresponding participating nodes: the blockchain identity information of the head of the legal department (legal affairs), the processing completion time, the review opinion of the head of the legal department (legal affairs), the revised project bidding plan, the revised project bidding plan version number, etc.; (7) The department in charge reviews the processing results of the corresponding participating nodes: the blockchain identity information of the department in charge of the project leader, the processing completion time, the review opinion of the department in charge of the project leader, the revised project bidding plan, the revised project bidding plan version number, etc.; (8) The bidding leadership group reviews the processing results of the corresponding participating nodes: the blockchain identity information of the bidding unit's leadership team, the processing completion time, the review opinion of the bidding unit's leadership team in OA document, the review opinion of the bidding unit's leadership team, etc.; (9) The procurement service department receives the processing results of the corresponding participating nodes: the blockchain identity information of the head of the procurement service department, the processing completion time, the receiving opinion of the head of the procurement service department, etc.; (10) The personnel who complete the procurement documents designate the processing results of the corresponding participating nodes: the blockchain identity information of the procurement service department's handler 1, the processing completion time, the personnel designated by the procurement service department's handler 1, etc.; Note: After rollback, the processing steps are increased, but the information included in each step remains unchanged;The processing results of the consortium blockchain nodes corresponding to the preparation of bidding documents include: (1) the processing results of the participating nodes corresponding to the setting of procurement service fees: blockchain identity information of the procurement service department handler 2, processing completion time, procurement service fees set by the procurement service department handler 2, etc.; (2) the processing results of the participating nodes corresponding to the improvement of procurement documents according to the plan: blockchain identity information of the procurement service department handler 1, processing completion time, revised project bidding plan, revised project bidding plan version number, etc.; (3) the processing results of the participating nodes corresponding to the review by the procurement service department: blockchain identity information of the procurement service department head 1, processing completion time, review opinions of the procurement service department head 1, etc.; (4) the processing results of the participating nodes corresponding to the review by the procurement service department manager: blockchain identity information of the procurement service department manager, processing completion time, review opinions of the procurement service department manager, etc.; (5) the processing results of the procurement management department manager The processing results of the participating nodes corresponding to the review of the person in charge: blockchain identity information of the person in charge of the procurement management department, processing completion time, review opinion of the person in charge of the procurement management department, etc.; (6) The processing results of the participating nodes corresponding to the review of the person in charge: blockchain identity information of the project leader, processing completion time, review opinion of the project leader, etc.; (7) The processing results of the participating nodes corresponding to the review of the legal department (legal affairs): blockchain identity information of the person in charge of the legal department (legal affairs) 2, processing completion time, review opinion of the person in charge of the legal department (legal affairs) etc.; (8) The processing results of the participating nodes corresponding to the transfer of the procurement project leader: blockchain identity information of the person in charge of the procurement service department 2, processing completion time, review opinion of the person in charge of the procurement service department 2, etc.; (9) The processing results of the participating nodes corresponding to the signing of documents / announcements: blockchain identity information of the person in charge of the procurement service department 1, processing completion time, review opinion of the person in charge of the procurement service department 1, etc.;

[0046] The processing results of the consortium blockchain nodes corresponding to contract preparation include: (1) the processing results of the participating nodes corresponding to contract generation: blockchain identity information of the project leader, processing completion time, review opinions of the project leader, etc.; (2) the processing results of the participating nodes corresponding to the review of the leaders of the undertaking department: blockchain identity information of the department head of the project leader, processing completion time, review opinions of the department head of the project leader, etc.; (3) the processing results of the participating nodes corresponding to the review of the procurement management department: blockchain identity information of the procurement management department staff, processing completion time, review opinions of the procurement management department staff, etc.; (4) the processing results of the participating nodes corresponding to the review of the finance department: blockchain identity information of the finance department staff, processing completion time, review opinions of the finance department staff, etc.; (5) the processing results of the participating nodes corresponding to the review of the leaders in charge of the undertaking department: blockchain identity information of the leaders in charge of the department of the project leader, processing completion time, review opinions of the leaders in charge of the department of the project leader, etc.

[0047] Optionally, alliance chain nodes and participating nodes can also be set up in the following ways: (1) Alliance chain node of procurement management department; including participating nodes with the identity of department handler and participating nodes with the identity of department head; (2) Alliance chain node of the unit where the project leader is located: including participating nodes with the identity of project leader, participating nodes with the identity of department head of project leader, participating nodes with the identity of department head of project leader, participating nodes with the identity of the department leader in charge of project leader, participating nodes with the identity of the financial department handler of the unit where the project leader is located; (3) Alliance chain node of procurement service department: including participating nodes with the identity of department handler 1, participating nodes with the identity of department handler 2, participating nodes with the identity of department head 1, participating nodes with the identity of department head 2, participating nodes with the identity of department manager, participating nodes with the identity of legal department (legal affairs) (including the identity of department head 1 and the identity of department head 2); (4) Alliance chain node of bidding unit (including the identity of the leadership team).

[0048] Note 1: Each identity includes information such as the identity's public key.

[0049] Note 2: In the procurement service department's consortium chain node, Department Manager 1 and Department Manager 2 have different identities and responsibilities, distinguished by the symbols 1 and 2. Similarly, Department Head 1 and Department Head 2 have different identities and responsibilities, distinguished by the symbols 1 and 2. In the legal department (legal affairs) participating node, Department Head 1 and Department Head 2 have different identities and responsibilities, distinguished by the symbols 1 and 2.

[0050] Note 3: When the project manager's organization and the tendering entity are the same organization, the two nodes can be merged into one node.

[0051] Optionally, nodes can be set as full nodes or lightweight nodes as needed. Considering the different functions of the nodes, the alliance chain nodes of the procurement management department and the alliance chain nodes of the procurement service department can be set as full nodes to store all project information, which facilitates the management and tracking of the entire project process. The alliance chain nodes of the project leader's unit and the bidding unit's alliance chain nodes can be set as lightweight nodes. The alliance chain node of the project leader's unit only stores project information related to the unit, and the alliance chain node of the bidding unit only stores project information tendered by the unit.

[0052] Optionally, by uploading project material data to the blockchain when all processes are rolled back, the rolled-back portion can be stored while the processing flow remains unaffected.

[0053] It should be noted that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0054] Furthermore, as shown in Figure 3, as a specific implementation of the above-mentioned project process processing method, this application embodiment provides a project process processing device 300, which includes: an acquisition module 301, a construction module 302, and a processing module 303.

[0055] The module includes: an acquisition module 301 for acquiring raw project data; a construction module 302 for inputting the raw project data into a preset project type identification model to determine the target project type of the raw project data; and, based on the preset project process processing steps corresponding to the target project type, determining the target processing steps required to process the raw project data; and, creating corresponding consortium blockchain nodes for the target processing steps to construct a consortium blockchain based on the consortium blockchain nodes; and a processing module 303 for publishing the raw project data to the consortium blockchain so that the consortium blockchain nodes process the raw project data sequentially to obtain the project processing results.

[0056] Optionally, the construction module 302 is specifically used to determine the first candidate project type matching the original project data based on the project leader information in the original project data and through the first type judgment unit in the project type identification model; to determine the second candidate project type matching the original project data based on the project feature words in the original project data and through the second type judgment unit in the project type identification model; and to determine the project type that is the same in the first candidate project type and the second candidate project type as the target project type.

[0057] Optionally, the project process processing device 300 further includes: a first configuration module, used to configure trigger codes for consortium blockchain nodes based on hash calculation; configuring trigger codes for consortium blockchain nodes based on hash calculation specifically includes: sorting the consortium blockchain nodes according to a first preset processing order between target processing stages to determine a first node order; configuring the trigger code of the first consortium blockchain node in the first node order as a preset first initial public value; configuring the trigger codes of other consortium blockchain nodes in the first node order excluding the first one as the hash value of the trigger code of the previous consortium blockchain node of the other consortium blockchain nodes.

[0058] Optionally, the processing module 303 is specifically used to configure public and private keys generated based on asymmetric encryption algorithms for consortium blockchain nodes; configure a preset trigger code for the project's original data with a first initial public value, and package the project's original data carrying the trigger code into a data packet and publish it to the consortium blockchain; the current consortium blockchain node that matches the trigger code of the data packet processes the data packet to obtain the processing result of the current consortium blockchain node; the current consortium blockchain node uses its private key to digitally sign the processing result of the current consortium blockchain node, and performs a hash calculation on the trigger code of the current consortium blockchain node; the current consortium blockchain node updates the data packet according to the signed processing result, and configures the hashed trigger code as the trigger code of the updated data packet; the current consortium blockchain node broadcasts the updated data packet on the consortium blockchain, so that the next consortium blockchain node that matches the trigger code of the updated data packet processes the data packet using the public key of the current consortium blockchain node, until all consortium blockchain nodes in the consortium blockchain have completed processing and obtained the project processing result.

[0059] Optionally, the project process processing device 300 further includes: a second configuration module, used to create multiple participating nodes for the consortium blockchain node corresponding to the target processing stage according to the multiple preset processing nodes included in the target processing stage; configure internal trigger codes for the participating nodes within the consortium blockchain node based on hash calculation; and control the participating nodes within the consortium blockchain node to process the original project data sequentially based on the internal trigger codes.

[0060] The partitioning module is used to divide consortium blockchain nodes into full nodes and light nodes; configure full nodes to store all data generated in the consortium blockchain; and configure light nodes to store the portion of data generated in the consortium blockchain that is related to themselves.

[0061] The rollback module is used to perform a rollback operation in the consortium blockchain node if the processing result of the consortium node is not passed, according to the first preset processing order between the target processing links; and to store the data generated by the rollback operation in the consortium blockchain.

[0062] Specific limitations regarding the project workflow processing device can be found in the limitations of the project workflow processing method described above, and will not be repeated here. Each module in the aforementioned project workflow processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0063] Based on the methods shown in Figures 1 and 2, this application also provides a readable storage medium storing a computer program that, when executed by a processor, implements the project flow processing method shown in Figures 1 and 2.

[0064] Based on this understanding, the technical solution of this application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, or portable hard drive), and includes several instructions to cause a computer device (such as a personal computer, server, or network device) to execute the methods described in the various implementation scenarios of this application.

[0065] Based on the methods shown in Figures 1 and 2, and the virtual device embodiment shown in Figure 3, in order to achieve the above objectives, this application embodiment also provides a computer device, which may be a personal computer, a server, a network device, etc. The computer device includes a storage medium and a processor; the storage medium is used to store computer programs; the processor is used to execute the computer programs to implement the project flow processing method shown in Figures 1 and 2.

[0066] Optionally, the computer device may also include a user interface, a network interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB ports, card reader ports, etc. The network interface may optionally include standard wired interfaces, wireless interfaces (such as Bluetooth interfaces, Wi-Fi interfaces), etc.

[0067] Those skilled in the art will understand that the computer device structure provided in this embodiment does not constitute a limitation on the computer device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0068] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages and stores the hardware and software resources of a computer device, supporting the operation of information processing programs and other software and / or programs. The network communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software within the physical device.

[0069] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platform, or the embodiments of this application can be implemented by hardware.

[0070] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application. Those skilled in the art will understand that the modules in the apparatus of the embodiment can be distributed within the apparatus of the embodiment as described, or can be modified to be located in one or more apparatuses different from this embodiment. The modules of the above-described embodiment can be combined into one module, or further divided into multiple sub-modules.

[0071] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of any particular implementation scenario. The above disclosures are merely a few specific implementation scenarios of this application; however, this application is not limited thereto, and any variations conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A project workflow processing method, characterized in that, The method includes: acquiring raw project data; inputting the raw project data into a preset project type identification model to determine the target project type of the raw project data; determining the target processing step required to process the raw project data based on the preset project process processing step corresponding to the target project type; creating a corresponding consortium blockchain node for the target processing step, so as to construct a consortium blockchain based on the consortium blockchain node; and publishing the raw project data to the consortium blockchain so that the consortium blockchain nodes process the raw project data sequentially to obtain the project processing result.

2. The project workflow processing method according to claim 1, characterized in that, The step of inputting the original project data into a preset project type recognition model to determine the target project type of the original project data specifically includes: based on the project leader information in the original project data, determining a first candidate project type matching the original project data through a first type judgment unit in the project type recognition model; based on the project feature words in the original project data, determining a second candidate project type matching the original project data through a second type judgment unit in the project type recognition model; and determining the project type that is the same in the first candidate project type and the second candidate project type as the target project type.

3. The project workflow processing method according to claim 1, characterized in that, The method further includes: configuring trigger codes for the consortium blockchain nodes based on hash calculation; the configuration of trigger codes for the consortium blockchain nodes based on hash calculation specifically includes: sorting the consortium blockchain nodes according to a first preset processing order between the target processing stages to determine a first node order; configuring the trigger code of the consortium blockchain node that is first in the first node order as a preset first initial public value; configuring the trigger codes of the other consortium blockchain nodes in the first node order (excluding the first one) as the hash value of the trigger code of the previous consortium blockchain node of the other consortium blockchain nodes.

4. The project workflow processing method according to claim 1, characterized in that, The step of publishing the project's original data to the consortium blockchain, so that the consortium blockchain nodes can process the project's original data sequentially to obtain the project processing result, specifically includes: configuring a public key and a private key generated based on an asymmetric encryption algorithm for the consortium blockchain nodes; configuring a preset trigger code for a first initial public value for the project's original data, and packaging the project's original data carrying the trigger code into a data packet and publishing it to the consortium blockchain; the current consortium blockchain node in the consortium blockchain that matches the trigger code of the data packet processing the data packet to obtain the processing result of the current consortium blockchain node; and the current consortium blockchain node using its private key. The processing result of the current consortium blockchain node is digitally signed, and the trigger code of the current consortium blockchain node is hashed. The current consortium blockchain node updates the data packet according to the signed processing result and configures the hashed trigger code as the trigger code of the updated data packet. The current consortium blockchain node broadcasts the updated data packet on the consortium blockchain so that the next consortium blockchain node in the consortium blockchain that matches the trigger code of the updated data packet processes the data packet using the public key of the current consortium blockchain node, until all consortium blockchain nodes in the consortium blockchain have completed processing and the project processing result is obtained.

5. The project workflow processing method according to claim 1, characterized in that, The method further includes: creating multiple participating nodes for the consortium blockchain node corresponding to the target processing stage according to the multiple preset processing nodes included in the target processing stage; configuring internal trigger codes for the participating nodes within the consortium blockchain node based on hash calculation; and controlling the participating nodes within the consortium blockchain node to process the original project data sequentially based on the internal trigger codes.

6. The project workflow processing method according to claim 1, characterized in that, The method further includes: dividing the consortium blockchain nodes into full nodes and light nodes; configuring the full nodes to store all data generated in the consortium blockchain; and configuring the light nodes to store some data related to themselves generated in the consortium blockchain.

7. The project workflow processing method according to claim 1, characterized in that, The method further includes: if the processing result of the consortium node is not passed, performing a rollback operation in the consortium chain node according to the first preset processing order between the target processing links; and storing the data generated by the rollback operation in the consortium chain.

8. A project workflow processing device, characterized in that, The device includes: an acquisition module for acquiring raw project data; a construction module for inputting the raw project data into a preset project type identification model to determine the target project type of the raw project data; and, based on a preset project process processing step corresponding to the target project type, determining the target processing step required to process the raw project data; and, creating a corresponding consortium blockchain node for the target processing step to construct a consortium blockchain based on the consortium blockchain node; and a processing module for publishing the raw project data to the consortium blockchain so that the consortium blockchain nodes process the raw project data sequentially to obtain project processing results.

9. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the project flow processing method as described in any one of claims 1 to 7.

10. A computer device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the program, it implements the project workflow processing method as described in any one of claims 1 to 7.

Images