Blockchain resume center management method, resume management system, and storage medium

Abstract

The application provides a blockchain resume center management method, a resume management system and a computer readable storage medium. The method comprises the following steps: triggering a target delivery request of a target user resume by using a personal user node; generating a first target block of the target delivery request after the target delivery request is verified by a verification node using the target delivery request; broadcasting the first target block in the resume management system to upload the target user resume to the resume management system when the authenticity of the target user resume is verified; displaying job information according to the target user resume by using a recruitment platform node when the recruitment platform node obtains the display authorization of the target user resume; and sending the resume of the job information to the first enterprise user node by using the recruitment platform when the enterprise credit of the first enterprise user node is greater than a preset credit threshold. The application can reduce the resume forgery rate, improve the resume credibility and improve the resume confidentiality.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, specifically to a management method for a blockchain resume center, a resume management system, and a computer-readable storage medium. Background Technology

[0002] In the current recruitment process, most employers obtain applicants' resumes through specific recruitment websites. However, on the one hand, many applicants add excessive amounts of resume information to their resumes in order to stand out in the fierce competition, and some employers have limited resume verification capabilities, leading to a slowdown in the recruitment process. On the other hand, resumes on recruitment websites can be downloaded at will, resume security is poor, and personal information is easily leaked. Summary of the Invention

[0003] This application provides a management method for a blockchain resume center, a resume management system, and a computer-readable storage medium, which can reduce the resume forgery rate, improve resume credibility, enhance resume confidentiality, and to some extent increase the recruitment speed for employers.

[0004] Firstly, this application provides a management method for a blockchain-based resume center, applied to a resume management system. The resume management system includes individual user nodes, enterprise user nodes, third-party authentication nodes, a resume center management node, and a recruitment platform node. The method includes: The individual user node is used to trigger a target user resume submission request. After the target submission request is verified by the verification node of the target submission request, a first target block of the target submission request is generated. The verification node includes at least one of the enterprise user node, the third-party authentication node, the resume center management node, and the recruitment platform node. When the authenticity of the target user's resume is verified, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system. After obtaining authorization to display the target user's resume from the recruitment platform node, the job application information is displayed based on the target user's resume using the recruitment platform node. When a resume viewing request for the job application information is triggered using the first enterprise user node, if the enterprise points of the first enterprise user node are greater than a preset points threshold, the resume for the job application information is sent to the first enterprise user node using the recruitment platform node.

[0005] Secondly, this application also provides a resume management system, which includes personal user nodes, enterprise user nodes, third-party authentication nodes, resume center management nodes, and recruitment platform nodes. The resume management system executes any of the blockchain resume center management methods provided in this application.

[0006] Thirdly, this application also provides a computer-readable storage medium having a computer program stored thereon, the computer program being loaded by a processor to execute the management method of the blockchain resume center.

[0007] In this application, firstly, after verifying the target application request using a verification node, a first target block for the target application request is generated. When the authenticity of the target user's resume is verified, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system. Since the target user's resume is only uploaded to the resume management system when its authenticity is verified, the upload of forged resumes to the resume management system can be reduced, thereby lowering the resume forgery rate and improving resume credibility. This can prevent a large number of forged resumes from flowing to employers, and to some extent improve the recruitment speed of employers. Secondly, after the recruitment platform node obtains authorization to display the target user's resume, it uses the recruitment platform node to display job information based on the target user's resume. Display can be done only when authorization is obtained, improving resume confidentiality. Furthermore, the recruitment platform only sends job information resumes to the first enterprise user node when the enterprise's points are greater than a preset points threshold. Therefore, it can filter out the problem of unqualified enterprise user nodes viewing the target user's resume, preventing the problem of resumes on recruitment websites being downloaded arbitrarily, and improving resume confidentiality. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 This is a schematic block diagram of a resume management system provided in an embodiment of this application; Figure 2 This is a flowchart illustrating a management method for a blockchain resume center provided in an embodiment of this application; Figure 3 This is an illustrative diagram illustrating the node data uploading or synchronization provided in the embodiments of this application; Figure 4This is an illustrative diagram illustrating the integral flow provided in the embodiments of this application; Figure 5 This is a schematic diagram of an embodiment of enterprise user data uploading provided in this application. Figure 6 This is a schematic diagram of an embodiment of providing third-party data uploading in this application. Figure 7 This is a schematic diagram of an embodiment of the data uploading process provided in this application. Detailed Implementation

[0010] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the described order. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0012] In the description of the embodiments of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0013] To enable any person skilled in the art to implement and use this application, the following description is provided. In this description, details are set forth for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be implemented without using these specific details. In other instances, well-known processes will not be described in detail to avoid obscuring the description of the embodiments of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in the embodiments of this application.

[0014] This application provides a management method for a blockchain resume center, a resume management system, and a computer-readable storage medium.

[0015] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0016] Figure 1 This is a schematic block diagram of a resume management system provided in an embodiment of this application.

[0017] like Figure 1 As shown, the resume management system 100 includes multiple individual user nodes 101, multiple enterprise user nodes 102, at least one third-party authentication node 103, a resume center management node 104, and at least one recruitment platform node 105. (For brevity, ...) Figure 1 (Only one of the following nodes is shown: Individual User Node 101, Enterprise User Node 102, Third-Party Authentication Node 103, Resume Center Management Node 104, and Recruitment Platform Node 105) Individual user node 101 is used to trigger the target user's resume submission request, to verify the first upload request of the target enterprise information as the first consensus verification node, to verify the second upload request of the target third party information as the second consensus verification node, and to verify the third upload request of the target platform information as the third consensus verification node.

[0018] Enterprise user node 102 is used to trigger the first upload request of target enterprise information, to verify the target delivery request as a verification node of the target delivery request, to verify the second upload request of target third-party information as a second consensus verification node, and to verify the third upload request of target platform information as a third consensus verification node.

[0019] Third-party authentication node 103 is used to verify the authenticity of the resume information carried in the target application request, verify the authenticity of the target company information, verify the authenticity of the target platform information, trigger the second upload request of the target third-party information, verify the target application request as a verification node of the target application request, verify the first upload request of the target company information as a first consensus verification node, and verify the third upload request of the target platform information as a third consensus verification node. The resume center management node 104 is used to manage the resumes of target users, target platform information, target enterprise information, and target third-party information in the resume management system. It serves as a verification node for target submission requests, a first consensus verification node for the first upload request of target enterprise information, a second consensus verification node for the second upload request of target third-party information, and a third consensus verification node for the third upload request of target platform information. Recruitment platform node 104 is used to display job information based on the target user's resume after obtaining the target user's authorization to display the resume; Enterprise user node 102 is also used to trigger a resume viewing request for job application information displayed on recruitment platform node 105 based on the enterprise points of enterprise user node 102.

[0020] It is understandable that the description of each node in the resume management system 100 here is somewhat focused, and the specific working principle of each node in the resume management system 100 is not described in detail. For the part about the specific working principle of each node in the resume management system 100, please refer to the relevant description in the management method embodiment of the blockchain resume center later.

[0021] Those skilled in the art will understand that Figure 1 The structure shown is merely a block diagram of a portion of the structure related to the embodiments of this application, and does not constitute a limitation on the resume management system in the embodiments of this application.

[0022] The following will be based on Figure 1 Taking the resume management system shown as the implementing entity of the blockchain resume center management method as an example, this application provides a detailed description of the blockchain resume center management method provided in this embodiment. It should be noted that... Figure 1 The scenarios described are only used to explain the management method of the blockchain resume center provided in the embodiments of this application, but do not constitute a limitation on the application scenarios of the management method of the blockchain resume center provided in the embodiments of this application.

[0023] Please see Figure 2 , Figure 2 This is a flowchart illustrating a blockchain resume center management method provided in an embodiment of this application. The blockchain resume center management method includes steps 201-205, wherein: 201. Use the personal user node to trigger a target user resume submission request.

[0024] Among them, the users of individual user nodes can be job seekers.

[0025] Among them, the target user resumes are the resumes of users who are about to apply.

[0026] The content of the target delivery request includes, but is not limited to, the target user's resume signed using a personal user node.

[0027] For example, when a job seeker decides to submit their resume to the resume management system, the job seeker sends a target submission request to the personal user node through the user-side backend management program. At this time, the personal user node will use its own node's private key to sign the target user's resume submission request, and after signing, broadcast the target user's resume submission request to other nodes in the resume management system (such as third-party authentication nodes, first verification nodes, etc.) to ensure the legality and immutability of the target submission request. In this way, the personal user node can be used to trigger the target user's resume submission request in the resume management system.

[0028] 202. After the target delivery request is verified by the verification node of the target delivery request, the first target block of the target delivery request is generated.

[0029] The verification nodes include at least one of the enterprise user node, the third-party authentication node, the resume center management node, and the recruitment platform node.

[0030] Among them, the users of enterprise user nodes can be recruiters.

[0031] The first target block is a block generated in response to the target delivery request.

[0032] For example, step 202 may specifically include the following steps 2021-2023: 2021. When the first verification class node of the target delivery request is used to verify the legality of the target delivery request.

[0033] The first verification node is a node in the resume management system used to verify the legitimacy of target application requests. The first verification node includes at least one of the enterprise user node, the third-party authentication node, the resume center management node, and the recruitment platform node.

[0034] 2022. After the legality verification of the target delivery request is passed, the signature of the target delivery request is generated and the delivery request is delivered using the first verification class node.

[0035] The content of the delivery request after signing includes, but is not limited to, the target delivery request signed by the first verification node.

[0036] The verification nodes include at least one of the following: enterprise user nodes, third-party authentication nodes, resume center management nodes, and recruitment platform nodes.

[0037] For example, firstly, in step 2021, the first verification node performs legality verification on the target application request. Legality verification includes, but is not limited to, verifying whether the user has authorized uploading the target user's resume, verifying whether the target application request complies with network business rules, and verifying whether the individual user node has the right to access and modify relevant data. For instance, if the verification finds that the user has authorized uploading the target user's resume, the target application request complies with network business rules, and the individual user node has the right to access and modify relevant data, then the legality verification is deemed successful. Otherwise, if the verification finds that the user has not authorized uploading the target user's resume, or the target application request does not comply with network business rules, or the individual user node does not have the right to access and modify relevant data, then the legality verification is deemed unsuccessful. Then, when the first verification node successfully verifies the legality of the target application request, in step 2022, the first verification node signs the target application request, and the signed application request is then submitted. For example, the first verification node in the resume management system includes enterprise user node 1, third-party authentication node 2, resume center management node 3, and recruitment platform node 4. When enterprise user node 1 verifies the legality of the target application request, it signs the target application request to obtain signed application request 1. Similarly, when third-party authentication node 2 verifies the legality of the target application request, it signs the target application request to obtain signed application request 2. When resume center management node 3 verifies the legality of the target application request, it signs the target application request to obtain signed application request 3. When recruitment platform node 4 verifies the legality of the target application request, it signs the target application request to obtain signed application request 4.

[0038] 2023. The second verification node of the target delivery request is used to sort each of the signed delivery requests and generate blocks to obtain the first target block of the target delivery request.

[0039] The second verification node refers to the node in the resume management system that is used to sort the signed submission requests and generate blocks. The second verification node can be either the resume center management node or the recruitment platform node.

[0040] For example, such as Figure 3 As shown, Figure 3This is an illustrative diagram illustrating the on-chain or synchronization of node data provided in this application embodiment. The content of the (N+1)th block in the blockchain includes, but is not limited to: a version number (the version number is used to indicate the format and protocol version of the block, helping to distinguish different blockchain protocols and protocol upgrades), and the hash value of the Nth block (wherein, each block records the hash value of the previous block; the hash value is a fixed-length string calculated from the content of the previous block using a hash algorithm such as SHA-256. By recording the hash value of the previous block in the current block, it is ensured that each block in the blockchain is associated with the previous block, thus forming a linear link. If a block in the blockchain is tampered with, the previous block will also be linked). The hash value of each block will also change, causing the hash values ​​of all subsequent blocks to change, thus enabling discovery and achieving the security and immutability of the resume. Other features include: Merkle root node (a single hash value calculated using the Merkle tree algorithm from the hash values ​​of all transactions in a block, ensuring that all transaction requests in the block are included and that the integrity of transaction requests can be quickly verified); timestamps (used to record the time when a block was created, ensuring that blocks in the blockchain are arranged in chronological order); random numbers (used in the Proof-of-Work (PoW) mechanism to solve computational problems); and transaction data (such as the target user's resume).

[0041] There are several ways to implement step 2023, including, for example: ① In some embodiments, when the number of signed delivery requests received by an individual user node is greater than or equal to a preset threshold, a block for the target delivery request is generated. In this case, when the first verification node passes the legality verification of the target delivery request, step 2022 is entered. First, the first verification node signs the target delivery request to obtain a signed delivery request; then, the first verification node sends the signed delivery request to the individual user node, so that the first verification node sends the signed delivery request it obtained by signing itself to the individual user node. When the number of signed delivery requests received by the individual user node is greater than or equal to the preset threshold, step 2023 is entered. First, the individual user node sends all the signed delivery requests to the second verification node; then, the second verification node sorts each signed delivery request and generates a block to obtain the first target block of the target delivery request. For example, the first verification node in the resume management system includes Enterprise User Node 1, Enterprise User Node 2, Enterprise User Node 3, Third-Party Authentication Node 4, Third-Party Authentication Node 5, Resume Center Management Node 6, and Recruitment Platform Node 7. Assume that Enterprise User Node 1, Enterprise User Node 2, Third-Party Authentication Node 4, Third-Party Authentication Node 5, and Recruitment Platform Node 7 each sign the target application request, obtaining Signed Application Request 1, Signed Application Request 2, Signed Application Request 4, Signed Application Request 5, and Signed Application Request 7, which are then sent to Individual User Node 8. Individual User Node 8... The system receives the following post-signed delivery requests in sequence: Request 1, Request 2, Request 4, Request 5, and Request 7. At this point, the individual user node 8 has received 5 post-signed delivery requests. Since the number of post-signed delivery requests received by the individual user node 8 exceeds the preset threshold, the individual user node 8 will sort the post-signed delivery requests 1, 2, 4, 5, and 7 according to the sorting rules of the consensus algorithm and generate blocks to obtain the first target block of the target delivery request.

[0042] The specific value of the preset quantity threshold can be set according to the actual business scenario requirements, and there is no restriction on the specific value of the preset quantity threshold here.

[0043] ② In some embodiments, when the proportion of signed delivery requests received by the personal user node is greater than or equal to a preset proportion threshold, the block for the target delivery request is generated. In this case, when the first verification node passes the legality verification of the target delivery request, step 2022 is entered. First, the first verification node signs the target delivery request to obtain a signed delivery request; then, the first verification node sends the signed delivery request to the personal user node, so that the first verification node sends the signed delivery request it obtained by signing itself to the personal user node. When the proportion of signed delivery requests received by the personal user node is greater than or equal to the preset proportion threshold, step 2023 is entered. First, the personal user node sends all the signed delivery requests to the second verification node; then, the second verification node sorts each of the signed delivery requests and generates a block to obtain the first target block of the target delivery request. For example, a resume management system includes seven primary verification nodes: Enterprise User Node 1, Enterprise User Node 2, Enterprise User Node 3, Third-Party Authentication Node 4, Third-Party Authentication Node 5, Resume Center Management Node 6, and Recruitment Platform Node 7. Assume that Enterprise User Node 1, Enterprise User Node 2, Enterprise User Node 3, Third-Party Authentication Node 4, Third-Party Authentication Node 5, and Resume Center Management Node 6 each sign the target application request, obtaining Signed Application Request 1, Signed Application Request 2, Signed Application Request 3, Signed Application Request 4, Signed Application Request 5, and Signed Application Request 6, which are then sent to Individual User Node 8. Individual User Node 8 receives Signed Application Request 1, Signed Application Request 2, Signed Application Request 3, Signed Application Request 4, Signed Application Request 5, and Signed Application Request 6 sequentially. Request 2, Request 3, Request 4, Request 5, and Request 6 are sent. At this point, the number of sent requests after signing is 6, and the proportion of sent requests after signing received by personal user node 8 is 6 / 7. Since the proportion of sent requests after signing received by personal user node 8 (e.g., 6 / 7) is greater than the preset proportion threshold (e.g., 3 / 4), personal user node 8 will sort sent requests after signing according to the sorting rules of the consensus algorithm and generate blocks to obtain the first target block of the target sending request.

[0044] The percentage of signed delivery requests received by individual user nodes refers to the ratio of the number of signed delivery requests received by individual user nodes to the total number of nodes in the first verification category of the resume management system.

[0045] The specific value of the preset percentage threshold can be set according to the actual business scenario requirements, and there is no restriction on the specific value of the preset percentage threshold here.

[0046] ③ In some embodiments, when the number of signed delivery requests received by the second verification node is greater than or equal to a preset threshold, a block for the target delivery request is generated. At this time, when the first verification node passes the legality verification of the target delivery request, it signs the target delivery request to obtain a signed delivery request. Then, in step 2022, the first verification node broadcasts the signed delivery request to the second verification node; when the number of signed delivery requests received by the second verification node is greater than or equal to the preset threshold, in step 2023, the second verification node sorts each signed delivery request and generates a block to obtain the first target block of the target delivery request.

[0047] ④ In some embodiments, when the proportion of signed delivery requests received by the second verification node is greater than or equal to a preset proportion threshold, the block of the target delivery request is generated. At this time, when the first verification node passes the legality verification of the target delivery request, it signs the target delivery request to obtain a signed delivery request. Then, in step 2022, the first verification node broadcasts the signed delivery request to the second verification node; when the proportion of signed delivery requests received by the second verification node is greater than or equal to the preset proportion threshold, in step 2023, the second verification node sorts each signed delivery request and generates a block to obtain the first target block of the target delivery request.

[0048] 203. When the authenticity of the target user's resume is verified, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system.

[0049] There are several ways to implement step 203, including, for example: (1) In some embodiments, when the validity verification of the first target block passes, the first target block is broadcast in the resume management system. At this time, the management method of the blockchain resume center may further include: using a third verification node of the target submission request to verify the validity of the first target block, wherein the third verification node includes at least one of a personal user node, an enterprise user node, a third-party authentication node, a resume center management node, and a recruitment platform node. Step 203 may specifically include: when the validity verification of the first target block passes, broadcasting the first target block in the resume management system to upload the target user's resume to the resume management system.

[0050] For example, firstly, the third verification node of the target submission request confirms the first target block of the target submission request. For instance, the third verification node will confirm whether the submission request after signing conforms to the consensus protocol, whether the legality verification signature is valid, and whether the target submission request in the first target block conforms to the blockchain rules. If it is confirmed that the target submission request conforms to the consensus protocol, the legality verification signature is valid, and the target submission request in the first target block conforms to the blockchain rules, then the validity verification of the first target block is determined to be successful. If it is confirmed that the target submission request does not conform to the consensus protocol, the legality verification signature is invalid, or the target submission request in the first target block does not conform to the blockchain rules, then the validity verification of the first target block is determined to be unsuccessful. When the validity verification of the first target block is successful, the first target block is broadcast to add the first target block to the blockchain of the resume management system, thereby enabling the upload of the target user's resume to the resume management system. When the validity verification of the first target block is unsuccessful, further processing is abandoned.

[0051] (2) In some embodiments, when the authenticity verification of the resume information carried in the target application request passes, the first target block is broadcast in the resume management system. At this time, the management method of the blockchain resume center may further include: using a third-party authentication node to verify the authenticity of the target user's resume. Step 203 may specifically include: when the authenticity verification of the target user's resume passes, broadcasting the first target block in the resume management system to upload the target user's resume to the resume management system. When the authenticity verification of the target user's resume fails, broadcasting the first target block is refused to reduce the upload of forged resumes, and the personal points of the individual user node are deducted and updated. This allows for point penalties when the authenticity verification of the target user's resume fails, increasing the cost of submitting forged resumes and reducing resume forgery to some extent.

[0052] The third-party authentication nodes can be nodes belonging to educational institutions, professional qualification certificate issuing agencies, skills training institutions, business organizations, etc. In some embodiments, enterprise user nodes, resume center management nodes, or recruitment platform nodes can also act as third-party authentication nodes.

[0053] For example, when a third-party authentication node (such as the node where an educational institution or professional qualification certificate issuing authority is located) receives a target application request broadcast by an individual user node, the third-party authentication node compares the target user's resume with the data of the third-party authentication node. For example, it compares the educational information, basic personal information, and work experience in the target user's resume with the data of the third-party authentication node to verify the authenticity of the resume information. When the resume information passes verification, it is marked as "verified" so that the verified resume information can be updated to the blockchain later. This enables cross-chain interaction, allowing the resume chain based on the resume management system to communicate and automatically synchronize authoritative data with education chains, professional qualification chains, etc. This avoids the problem of low resume credibility caused by the inability to communicate with user data distributed across multiple platforms (such as recruitment websites, educational institutions, etc.), and improves the credibility of resume management to a certain extent.

[0054] (3) In some embodiments, when the validity verification of the first target block passes and the authenticity verification of the resume information carried in the target submission request passes, the first target block is broadcast in the resume management system. At this time, the management method of the blockchain resume center may further include: using a third verification node of the target submission request to verify the validity of the first target block, wherein the third verification node includes at least one of personal user node, enterprise user node, third-party authentication node, resume center management node, and recruitment platform node; using a third-party authentication node to verify the authenticity of the resume information carried in the target submission request. Step 203 may specifically include: when the validity verification of the first target block passes and the authenticity verification of the resume information passes, broadcasting the first target block in the resume management system to upload the target user resume to the resume management system.

[0055] 204. After obtaining authorization to display the target user's resume at the recruitment platform node, the job application information is displayed based on the target user's resume using the recruitment platform node.

[0056] For example, after uploading a target user's resume to the resume management system, a request to view the resume can be triggered using a recruitment platform node. The resume center management node then verifies the authorization of this request, such as verifying the authenticity of the recruitment platform node's business registration information and whether the target user's resume requests to block the recruitment platform node. This determines whether the recruitment platform node has the necessary conditions to view the target user's resume. If it is determined that the recruitment platform node has the necessary conditions, it is determined that the recruitment platform node has obtained authorization to display the target user's resume. After obtaining this authorization, the recruitment platform node downloads the target user's resume and displays job information based on it. This avoids the problem of easy leakage of personal information caused by any recruitment platform being able to arbitrarily download resumes, improves individuals' self-control over their resume data, and enhances resume confidentiality.

[0057] 205 When the first enterprise user node triggers a resume viewing request for the job information, if the enterprise points of the first enterprise user node are greater than a preset points threshold, the resume of the job information is sent to the first enterprise user node using the recruitment platform node.

[0058] Among them, the first enterprise user node refers to the enterprise user node that triggers the resume viewing request for job information among the enterprise user nodes of the resume management system.

[0059] In some embodiments of step 205, when a resume viewing request for the job application information is triggered using a first enterprise user node, if the enterprise points of the first enterprise user node are greater than a preset points threshold, the resume for the job application information is sent to the first enterprise user node using the recruitment platform node. If the enterprise points of the first enterprise user node are less than or equal to the preset points threshold, no further processing is performed, and the resume for the job application information is not sent to the first enterprise user node, thereby restricting enterprise user nodes with insufficient enterprise points from viewing resumes. This avoids the problem of easy leakage of resume holders' personal information caused by any enterprise being able to arbitrarily download resumes, improves individuals' autonomy over resume data, and enhances resume confidentiality.

[0060] In some embodiments of step 205, to further improve the confidentiality of the target user's resume, when a resume viewing request for the job application information is triggered using a first enterprise user node, if the enterprise score of the first enterprise user node is greater than a preset score threshold, then the confidential enterprise of the target user's resume is obtained; the information association ratio and historical interaction count between the second enterprise user node corresponding to the confidential enterprise and the first enterprise user node are obtained; the personal node characteristics of the personal user node and the first enterprise node characteristics between the first enterprise user nodes are obtained; the active interaction frequency between the personal user node and the first enterprise user node is obtained; based on the information association ratio, the historical interaction count, the active interaction frequency, the personal node characteristics, the first enterprise node characteristics, and a preset association simulation function, a first interest index value of the personal user node for the first enterprise user node is determined; if the enterprise score of the first enterprise user node is greater than a preset score threshold and the first interest index value is greater than a first preset index threshold, then the resume of the job application information is sent to the first enterprise user node using the recruitment platform node. If the enterprise points of the first enterprise user node are greater than the preset points threshold, but the first interest index value is less than or equal to the first preset index threshold, no further processing is performed, and the resume of the job application information is not sent to the first enterprise user node. This restricts enterprise user nodes with insufficient first interest index values ​​from viewing the target user's resume. In this way, the probability of the target user's resume being viewed by the confidential enterprise of the personal user node can be reduced, and the problem of the target user's resume being viewed by the enterprise that does not match the needs of the personal user node can be reduced, thereby improving the confidentiality of the target user's resume to a certain extent.

[0061] Among them, the frequency of proactive interaction refers to the frequency with which an individual user node initiates interaction with an enterprise user corresponding to the first enterprise user node, such as the frequency with which an individual user node sends a message to an enterprise user corresponding to the first enterprise user node.

[0062] The information association ratio is used to indicate the degree of overlap in business registration information between the second and first enterprise user nodes. For example, if five of the N business registration records uploaded by the second enterprise user node are identical to those of the first enterprise user node (e.g., identical company address, contact number), then the ratio of the number of identical records to the total number of records uploaded by the second enterprise user node can be used as the information association ratio. This allows for the identification of first enterprise user nodes that are directly associated with the confidential companies associated with the target user's resume (e.g., companies with the same manager). A preset association simulation function is used to determine the first interest index value of the individual user node towards the first enterprise user node based on the information association ratio. When the first interest index value is less than or equal to a first preset threshold, the target user's resume will not be sent to the first enterprise user node, thus preventing the target user's resume from being viewed by the enterprise user node that the individual user node wants to keep confidential, thereby improving the confidentiality of the target user's resume to some extent.

[0063] The historical interaction count is used to indicate the interaction between the second enterprise user node and the first enterprise user node. Thus, by using the historical interaction count, the first enterprise user node directly associated with the confidential enterprise in the target user's resume can be identified. Furthermore, a preset association simulation function is used to determine the first interest index value of the individual user node towards the first enterprise user node based on the historical interaction count. Since the historical interaction count N... C Total number of interactions with the first enterprise node N total The ratio can reflect, to some extent, that when the value of the first interest indicator is less than or equal to the first preset indicator threshold, the target user's resume will not be sent to the first enterprise user node, thereby avoiding the problem that the target user's resume may be viewed by the enterprise user node that the individual user node wants to keep confidential, and improving the confidentiality of the target user's resume to a certain extent.

[0064] The preset correlation simulation function is shown in Formula 1 below: Formula 1 In Formula 1, I represents the value of the first interest index, R represents the information association ratio, and N represents the information association ratio. C N represents the number of historical interactions. total C represents the total number of interactions of the first enterprise node, and V represents the frequency of proactive interactions. individual Representing individual node characteristics, V enterprise Let V represent the features of the first enterprise node, where w1, w2, and w3 are weight coefficients. The first enterprise node feature V enterprise The individual node feature V can be obtained by characterizing the demand information of the first enterprise user node. individual This can be obtained by representing the information of the target user's resume initiated by an individual user node.

[0065] Thus, in Formula 1 This reflects the probability that the first enterprise user node will not transmit the job information corresponding to the target user's resume to the confidential enterprise holding the target user's resume. Therefore, the first interest index value calculated using Formula 1 is used to determine whether to send the target user's resume to the first enterprise user node. This avoids the problem of the target user's resume being viewed by enterprise user nodes that the individual user node wants to keep confidential, thus improving the confidentiality of the target user's resume to a certain extent. In Formula 1... This can reflect the matching degree between individual user nodes and the first enterprise user node. The first interest index value is calculated using Formula 1 to determine whether to send the target user's resume to the first enterprise user node. This can make the target user's resume be recommended to the matching enterprise first, which can reduce the leakage of personal information and improve the recruitment speed of employers to a certain extent.

[0066] In some implementations, the method further includes: if the enterprise points of the first enterprise user node are less than or equal to a preset points threshold, then obtaining a second interest index value of the individual user node towards the first enterprise user node; determining an intent confidentiality index value of the individual user node towards the first enterprise user node based on the information association ratio and the number of historical interactions; if the enterprise points of the first enterprise user node are less than or equal to a preset points threshold, the second interest index value is greater than a second preset index threshold, and the intent confidentiality index value is less than a third preset index threshold, then sending a resume containing the job application information to the first enterprise user node using the recruitment platform node, wherein the second preset index threshold is greater than the first preset index threshold; thus, the problem of cold-start enterprise user nodes being unable to view resumes due to insufficient points can be avoided, thereby enabling cold-start enterprise user nodes with insufficient points but high interest levels to view the resumes of target users, which to some extent improves the recruitment speed of employers. If the enterprise points of the first enterprise user node are less than or equal to a preset points threshold, and the intent confidentiality index value is greater than a third preset index threshold, then the resume corresponding to the job application information will not be sent to the first enterprise user node. This restricts enterprise user nodes with higher intent confidentiality index values ​​from viewing the target user's resume, reducing the probability that the target user's resume will be viewed by the confidential enterprise of the individual user node, and improving the confidentiality of the target user's resume to some extent. If the enterprise points of the first enterprise user node are less than or equal to a preset points threshold, and the second interest index value is less than or equal to a second preset index threshold, then the resume corresponding to the job application information will not be sent to the first enterprise user node. This restricts enterprise user nodes with lower second interest index values ​​from viewing the target user's resume, reducing the problem of the target user's resume being viewed by enterprise user nodes whose needs do not match those of the individual user node, and improving the confidentiality of the target user's resume to some extent.

[0067] For example, a preset intent indicator generation function can be used to determine the intent confidentiality indicator value of the individual user node to the first enterprise user node based on the information association ratio and the number of historical interactions. For example, the preset intent indicator generation function is shown in Formula 2 below: Formula 2 In Formula 2, a and b are both coefficients; R represents the information association ratio; N C This indicates the number of historical interactions; p > 1 indicates that the magnitude of the influence is gradually increasing, resulting in a higher information association ratio and a larger intention confidentiality index value.

[0068] In formula 2 The higher the information association ratio, the larger the intention confidentiality index value. This allows us to combine the closeness of association between the second enterprise user node (corresponding to the confidentiality enterprise of the target user's resume) and the first enterprise user node to calculate the intention confidentiality index value of the individual user node to the first enterprise user node, thereby improving the accuracy of the intention confidentiality index value.

[0069] In formula 2 The more historical interactions there are, the higher the intent confidentiality index value becomes. By using a logarithmic function (log) to fit the relationship between the intent confidentiality index value and the number of historical interactions, the increase in intent after a large number of historical interactions can be reduced. This avoids the problem of excessive historical interactions affecting the final intent confidentiality index value, thus preventing the influence of excessive historical interactions on the information association ratio from being obscured, thereby improving the accuracy of the intent confidentiality index value.

[0070] The determination of the second interest index value is similar to that of the first interest index value. For details, please refer to the previous text and the relevant explanation of Formula 1. It will not be repeated here.

[0071] The specific values ​​of the first preset indicator threshold, the second preset indicator threshold, and the third preset indicator threshold can be set according to the actual business scenario requirements. There are no restrictions on the specific values ​​of the first preset indicator threshold, the second preset indicator threshold, and the third preset indicator threshold here.

[0072] Please refer to Figure 4 , Figure 4This is a schematic diagram illustrating the points transfer provided in this application embodiment. In this embodiment, resumes are transferred based on enterprise points of enterprise user nodes and personal points of individual user nodes. Transferring resumes based on points can improve resume confidentiality and reduce resume forgery rates to some extent. The management strategies for enterprise points and individual points (such as point allocation strategies and point deduction strategies) can be set according to actual business scenario requirements. When an enterprise user node performs point allocation actions (such as verifying the experience of departing employees or recharging points), points are allocated to the enterprise user node according to the point allocation strategy; when an enterprise user node performs point deduction actions, points are deducted from the enterprise user node according to the point deduction strategy. Similarly, when an individual user node performs point allocation actions (such as verifying the experience of departing employees or recharging points), points are allocated to the enterprise user node according to the point allocation strategy; when an enterprise user node performs point deduction actions, points are deducted from the enterprise user node according to the point deduction strategy. For example, the point allocation strategy for individual points can be shown in Table 1 below: Table 1

[0073] For example, the scoring strategy for corporate points can be shown in Table 2 below: Table 2

[0074] In the scoring strategies in Tables 1 and 2, ① actions not shown are considered as not having a scoring strategy enabled by default, and the default score is 0. ② For each resume, each scoring item is awarded only once, regardless of whether there are multiple certifications. For example, if a resume contains both university degree certification and postgraduate degree certification, only one point will be awarded for the degree certification item.

[0075] Furthermore, such as Figure 4 As shown, individual user nodes, enterprise user nodes, third-party authentication nodes, resume center management nodes, and recruitment platform nodes in the resume management system can use points to redeem services or items in the points mall, which can improve the activity of nodes in the resume management system.

[0076] Further, refer to Figure 4The management method of this blockchain resume center may further include: triggering an experience update request from a departing employee using the enterprise user node; after the experience update request is verified, uploading the personal experience information corresponding to the experience update request to the resume management system; and updating the enterprise points corresponding to the enterprise user node after the personal experience information of the experience update request is uploaded to the resume management system. In this way, on the one hand, since enterprise user nodes can receive point rewards for proactively updating the personal experience information of departing employees, their enthusiasm for updating this information is increased, thereby improving the completeness and authenticity of the resume information in the resume management system; on the other hand, the point rewards for updating the personal experience information of departing employees and the point deductions for viewing resumes create a closed-loop circulation of points, reducing the need for point recharge and the high cost of viewing resumes due to the need for points, thus increasing the stickiness of enterprise user nodes in resume circulation.

[0077] Further, refer to Figure 4 The management method of the blockchain resume center may further include: triggering a scoring request for a target user using the individual user node, wherein the scoring request includes at least one of an account registration request, an identity authentication request, and a resume upload request; after the scoring request is verified, uploading the individual user information corresponding to the scoring request to the resume management system; and updating the individual points of the individual user node after the individual user information corresponding to the scoring request is uploaded to the resume management system. Thus, by uploading the personal user information corresponding to the scoring request to the resume management system, and updating the personal points of the personal user nodes, on the one hand, since personal user nodes can receive points rewards for actively triggering scoring requests such as account registration requests, identity authentication requests, and resume upload requests, this increases the personal user nodes' enthusiasm for updating their personal experience information. This, in turn, improves the completeness of personal resume information in the resume management system, increases the number of personal users, and further improves the completeness of resume information in the resume management system. This allows personal user resume data to be centralized in the resume management system, thereby reducing the problem of low data completeness caused by personal user resume data being scattered across multiple platforms. On the other hand, by allowing personal user nodes to receive points rewards for making scoring requests and to impose points penalties when the authenticity verification of a target user's resume fails, the cost of submitting a forged resume can be increased, the authenticity of resume submissions can be improved, and resume forgery can be reduced to a certain extent, enabling enterprise user nodes (such as recruiters) to recruit quickly.

[0078] Furthermore, such as Figure 5 As shown, Figure 5This is a schematic diagram of an embodiment of enterprise user data uploading provided in this application. The management method of the blockchain resume center may also include the following steps 501-504: 501. Use the enterprise user node to trigger the first upload request for the target enterprise information.

[0079] The first upload request refers to the request to upload the target company's information.

[0080] For example, when a user of an enterprise user node (such as a recruiter) decides to submit target company information to the resume management system, the user of the enterprise user node (such as the recruiter) sends a first upload request to the enterprise user node through the enterprise-side backend management program. At this time, the enterprise user node will use its own node's private key to sign the first upload request for the target company information, and after signing, broadcast the first upload request for the target company information to other nodes in the resume management system (such as third-party authentication nodes, first consensus nodes, etc.) to ensure the legality and immutability of the first upload request. In this way, the enterprise user node can be used to trigger the first upload request for the target company information in the resume management system.

[0081] 502. Use the third-party authentication node to verify the authenticity of the target enterprise information.

[0082] For example, when a third-party authentication node (such as the node where a business registration authority or enterprise honor certification authority resides) receives the first upload request broadcast by the enterprise user node, the third-party authentication node compares the target enterprise information with the data of the third-party authentication node. For example, it compares the business registration information and honor certification information in the target enterprise information with the data of the third-party authentication node to verify the authenticity of the target enterprise information. When the target enterprise information passes the verification, it is marked as "verified" so that the verified target enterprise information can be updated to the blockchain in the future. This enables cross-chain interaction, allowing the enterprise information chain based on the resume management system to communicate and automatically synchronize authoritative data with the business registration information chain, enterprise honor information chain, etc. This avoids the problem of low credibility of the target enterprise information caused by the inability to communicate between enterprise data distributed on multiple platforms (such as business registration authorities, enterprise honor certification authorities, etc.), and improves the credibility of the target enterprise information to a certain extent.

[0083] 503. After the first upload request is verified by the first consensus node of the first upload request, the second target block of the first upload request is generated.

[0084] The first consensus-type node includes at least one of the individual user node, the third-party authentication node, the resume center management node, and the recruitment platform node.

[0085] The second target block is the block generated in response to the first upload request.

[0086] For example, the first consensus-type node includes a legitimacy verification node and a block generation node. Step 503 may specifically include: using the legitimacy verification node in the first consensus-type node to verify the legitimacy of the first upload request; after the legitimacy verification of the first upload request is passed, using the legitimacy verification node in the first consensus-type node to generate a signed upload request for the first upload request; using the block generation node in the first consensus-type node to sort the signed upload requests of each of the first upload requests and generate blocks to obtain the second target block of the first upload request.

[0087] 504. When the authenticity of the target company information is verified, the second target block is broadcast in the resume management system to upload the target company information to the resume management system.

[0088] For details on the specific implementation of "uploading enterprise user data" in steps 501-504 and the related explanations of "uploading personal user data" in steps 201-203, please refer to the previous explanations. They will not be repeated here.

[0089] Furthermore, such as Figure 6 As shown, Figure 6 This is a schematic diagram of an embodiment of third-party data uploading provided in this application. The management method of the blockchain resume center may also include the following steps 601-603: 601. Trigger a second upload request for the target third-party information using the third-party authentication node.

[0090] The second upload request refers to the upload request for the target third-party information.

[0091] For example, when a user of a third-party authentication node (such as an educational institution, a professional qualification certificate issuing authority, a skills training institution, or a business organization) decides to submit target third-party information to the resume management system, the user of the third-party authentication node (such as an educational institution, a professional qualification certificate issuing authority, a skills training institution, or a business organization) sends a second upload request to the third-party authentication node through the third-party backend management program. At this time, the third-party authentication node will use its own node's private key to sign the second upload request for the target third-party information, and after signing, broadcast the second upload request for the target third-party information to other nodes in the resume management system (such as the third-party authentication node, second consensus nodes, etc.) to ensure the legality and immutability of the second upload request. In this way, the second upload request for the target third-party information can be triggered in the resume management system by using the third-party authentication node.

[0092] 602. After the second consensus node of the second upload request verifies the second upload request, the third target block of the second upload request is generated.

[0093] The second consensus-type node includes at least one of the individual user node, the enterprise user node, the resume center management node, and the recruitment platform node.

[0094] The third target block is a block generated in response to the second upload request.

[0095] For example, the second consensus-type node includes a legitimacy verification node and a block generation node. Step 603 may specifically include: using the legitimacy verification node in the second consensus-type node to verify the legitimacy of the second upload request; after the legitimacy verification of the second upload request is passed, using the legitimacy verification node in the second consensus-type node to generate a signed upload request for the second upload request; using the block generation node in the second consensus-type node to sort the signed upload requests of each second upload request and generate a block to obtain the third target block of the second upload request.

[0096] 603. Broadcast the third target block in the resume management system to upload the target third-party information to the resume management system.

[0097] For details on the specific implementation of "uploading enterprise user data" in steps 601-603 and the related explanations of "uploading personal user data" in steps 201-203, please refer to the previous explanations. They will not be repeated here.

[0098] Furthermore, such as Figure 7 As shown, Figure 7 This is a schematic diagram of an embodiment of the data uploading method for a recruitment platform provided in this application. The management method of the blockchain resume center may also include the following steps 701-704: 701. Trigger a third upload request for target platform information using the recruitment platform node.

[0099] The third upload request refers to the upload request for information from the target platform.

[0100] For example, when a user of a recruitment platform node decides to submit target platform information to the resume management system, the user sends a third upload request to the recruitment platform node through the matchmaker backend management program. At this time, the recruitment platform node will use its own node's private key to sign the third upload request for the target platform information, and after signing, broadcast the third upload request for the target platform information to other nodes in the resume management system (such as third-party authentication nodes, third consensus nodes, etc.) to ensure the legality and immutability of the third upload request. In this way, the recruitment platform node can be used to trigger the third upload request for the target platform information in the resume management system.

[0101] 702. Use the third-party authentication node to verify the authenticity of the target platform information.

[0102] For example, when a third-party authentication node (such as the node where a business registration authority or platform honor certification authority resides) receives a third upload request broadcast by a recruitment platform node, the third-party authentication node compares the target platform information with its own data. For instance, it compares the business registration information and honor certification information in the target platform information with the data in the third-party authentication node to verify the authenticity of the target platform information. When the target platform information passes verification, it is marked as "verified" so that the verified target platform information can be updated to the blockchain later. This enables cross-chain interaction, allowing the platform information chain based on the resume management system to communicate and automatically synchronize authoritative data with the business registration information chain, platform honor information chain, etc. This avoids the problem of low credibility of target platform information caused by the inability to communicate between platform data distributed across multiple platforms (such as business registration authorities, platform honor certification authorities, etc.), and improves the credibility of target platform information to a certain extent.

[0103] 703. After the third consensus node of the third upload request verifies the third upload request, the fourth target block of the third upload request is generated.

[0104] The third consensus node includes at least one of the individual user node, the enterprise user node, the third-party authentication node, and the resume center management node.

[0105] The fourth target block is a block generated in response to the third upload request.

[0106] For example, the third consensus-type node includes a legitimacy verification node and a block generation node. Step 703 may specifically include: using the legitimacy verification node in the third consensus-type node to verify the legitimacy of the third upload request; after the legitimacy verification of the third upload request is passed, using the legitimacy verification node in the third consensus-type node to generate a signed upload request for the third upload request; using the block generation node in the third consensus-type node to sort the signed upload requests of each of the third upload requests and generate blocks to obtain the fourth target block of the third upload request.

[0107] 704. When the authenticity of the target platform information is verified, the fourth target block is broadcast in the resume management system to upload the target platform information to the resume management system.

[0108] For details on the specific implementation of "uploading enterprise user data" in steps 701-704 and the related explanations of "uploading personal user data" in steps 201-203, please refer to the previous explanations. They will not be repeated here.

[0109] Thus, through steps 201-203, 501-504, 601-603, and 701-704, the target user resume information, target company information, target third-party information, and target platform information are uploaded to the resume management system. This ensures that the target user resume information, target company information, target third-party information, and target platform information can be stored on the blockchain, guaranteeing their immutability. Furthermore, it allows the data of individual user nodes, enterprise user nodes, third-party authentication nodes, resume center management nodes, and recruitment platform nodes to be dynamically updated: for example, allowing individual user nodes to add new experiences, generating a new block each time an update is made, and retaining historical records.

[0110] Furthermore, access control can be implemented: for example, individual user nodes can authorize enterprise user nodes to access specific resume fields through private keys, such as disclosing only work experience but hiding personal privacy information such as name and contact information.

[0111] As can be seen from the above, firstly, by verifying the target application request using a verification node, a first target block for the target application request is generated. When the authenticity of the target user's resume is verified, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system. Since the target user's resume is only uploaded to the resume management system when its authenticity is verified, the number of forged resumes uploaded to the resume management system can be reduced, lowering the resume forgery rate and increasing resume credibility. This can prevent a large number of forged resumes from flowing to employers, and to some extent, improve the recruitment speed of employers. Secondly, after the recruitment platform node obtains authorization to display the target user's resume, it displays job information based on the target user's resume. Display can be done only when authorization is obtained, improving resume confidentiality. Furthermore, resumes with job information are only sent to the first enterprise user node through the recruitment platform when the enterprise user node's enterprise points are greater than a preset points threshold. Therefore, the problem of unqualified enterprise user nodes viewing the target user's resume can be filtered out, preventing the problem of resumes on recruitment websites being downloaded arbitrarily, and improving resume confidentiality.

[0112] Those skilled in the art will understand that all or part of the steps in the above-described management method of the blockchain resume center can be accomplished by instructions, or by controlling related hardware through instructions. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0113] Therefore, embodiments of this application provide a computer-readable storage medium storing multiple computer programs that can be loaded by a processor to execute any of the blockchain resume center management methods provided in embodiments of this application.

[0114] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0115] In the above embodiments of the computer-readable storage medium and resume management system, the descriptions of each embodiment have different focuses. For parts not detailed in a particular embodiment, please refer to the relevant descriptions of other embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes and beneficial effects of the computer-readable storage medium, resume management system, and their corresponding units described above can be referred to the description of the management method of the blockchain resume center in the above embodiments, and will not be repeated here.

[0116] The above provides a detailed description of a blockchain resume center management method, resume management system, and computer-readable storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A management method for a blockchain resume center, characterized in that, Applied to a resume management system, which includes individual user nodes, enterprise user nodes, third-party authentication nodes, a resume center management node, and a recruitment platform node, the method includes: The individual user node is used to trigger a target user resume submission request. After the target application request is verified by a verification node, a first target block is generated. The first verification node verifies the legality of the target application request; the first verification node includes at least one of the enterprise user node, the third-party authentication node, the resume center management node, and the recruitment platform node. A third verification node verifies the validity of the first target block; the third verification node includes at least one of the individual user node, the enterprise user node, the third-party authentication node, the resume center management node, and the recruitment platform node. When the authenticity of the target user's resume is verified, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system. After obtaining authorization to display the target user's resume from the recruitment platform node, the job application information is displayed based on the target user's resume using the recruitment platform node. When a resume viewing request for the job application information is triggered using the first enterprise user node, if the enterprise points of the first enterprise user node are greater than a preset points threshold, the resume of the job application information is sent to the first enterprise user node using the recruitment platform node, including: When a resume viewing request for the job information is triggered using the first enterprise user node, if the enterprise points of the first enterprise user node are greater than a preset points threshold, the confidential enterprise of the target user's resume is obtained. Obtain the information association ratio and historical interaction count between the second enterprise user node corresponding to the confidential enterprise and the first enterprise user node; Obtain the personal node characteristics of the personal user nodes and the first enterprise node characteristics among the first enterprise user nodes; Obtain the frequency of active interactions between the individual user node and the first enterprise user node; Based on the information association ratio, the number of historical interactions, the frequency of proactive interactions, the characteristics of individual nodes, the characteristics of the first enterprise node, and a preset association simulation function, the first interest index value of the individual user node to the first enterprise user node is determined. If the first interest index value is greater than the first preset index threshold, then the resume containing the job application information is sent to the first enterprise user node using the recruitment platform node. The preset correlation simulation function is as follows: Where I represents the first interest index value, R represents the information association ratio, and N represents the information association ratio. C N represents the number of historical interactions. total C represents the total number of interactions of the first enterprise node, and V represents the frequency of proactive interactions. individual Representing individual node characteristics, V enterprise The first enterprise node features are represented by w1, w2, and w3, which are weight coefficients; the method further includes: If the enterprise points of the first enterprise user node are less than or equal to a preset points threshold, then the second interest index value of the individual user node to the first enterprise user node is obtained; wherein, the association simulation function is also used to calculate and obtain the second interest index value; Based on the information association ratio and the number of historical interactions, the confidentiality index value of the individual user node's intent to the first enterprise user node is determined. If the second interest index value is greater than the second preset index threshold and the intent confidentiality index value is less than the third preset index threshold, then the resume of the job application information is sent to the first enterprise user node through the recruitment platform node, wherein the second preset index threshold is greater than the first preset index threshold.

2. The management method of the blockchain resume center according to claim 1, characterized in that, The method further includes: The enterprise user node is used to trigger an experience update request for departing employees. After the experience update request is verified, the personal experience information corresponding to the experience update request is uploaded to the resume management system. Once the personal experience information of the experience update request is uploaded to the resume management system, the enterprise points corresponding to the enterprise user node are updated by assigning points.

3. The management method of the blockchain resume center according to claim 1, characterized in that, The method further includes: The personal user node is used to trigger a score assignment request for the target user, wherein the score assignment request includes at least one of an account registration request, an identity authentication request, and a resume upload request; After the scoring request is verified, the personal user information corresponding to the scoring request is uploaded to the resume management system. Once the personal user information corresponding to the scoring request is uploaded to the resume management system, the personal points of the personal user node are updated by scoring. The authenticity of the target user's resume is verified using the third-party authentication node. When the authenticity verification of the target user's resume fails, the personal score of the individual user node is deducted and updated.

4. The management method of the blockchain resume center according to claim 1, characterized in that, After the target delivery request is verified by the verification node of the target delivery request, the first target block of the target delivery request is generated, including: Once the legality verification of the target delivery request is passed, the signature of the target delivery request is generated using the first verification class node and then the delivery request is sent. The second verification node of the target delivery request is used to sort each signed delivery request and generate a block to obtain the first target block of the target delivery request, wherein the second verification node is the resume center management node or the recruitment platform node.

5. The management method of the blockchain resume center according to claim 4, characterized in that, The method further includes: The step of broadcasting the first target block in the resume management system to upload the target user's resume to the resume management system includes: When the validity verification of the first target block is successful, the first target block is broadcast in the resume management system to upload the target user's resume to the resume management system.

6. The management method of the blockchain resume center according to claim 1, characterized in that, The method further includes at least one of uploading target company information to the resume management system, uploading target third-party information to the resume management system, and uploading target platform information to the resume management system; Uploading the target company information to the resume management system includes the following steps: The enterprise user node is used to trigger the first upload request for the target enterprise information; The authenticity of the target enterprise information is verified using the third-party authentication node. After the first upload request is verified by the first consensus node of the first upload request, a second target block of the first upload request is generated. The first consensus node includes at least one of the personal user node, the third-party authentication node, the resume center management node, and the recruitment platform node. When the authenticity of the target company information is verified, the second target block is broadcast in the resume management system to upload the target company information to the resume management system. Uploading the target third-party information to the resume management system includes the following steps: The second upload request for the target third-party information is triggered using the aforementioned third-party authentication node; After the second upload request is verified by the second consensus node of the second upload request, a third target block of the second upload request is generated. The second consensus node includes at least one of the personal user node, the enterprise user node, the resume center management node, and the recruitment platform node. The third target block is broadcast in the resume management system to upload the target third-party information to the resume management system; Uploading the target platform information to the resume management system includes the following steps: The recruitment platform node is used to trigger a third upload request for the target platform information; The authenticity of the target platform information is verified using the third-party authentication node. After the third upload request is verified by the third consensus node of the third upload request, the fourth target block of the third upload request is generated. The third consensus node includes at least one of the personal user node, the enterprise user node, the third-party authentication node, and the resume center management node. When the authenticity of the target platform information is verified, the fourth target block is broadcast in the resume management system to upload the target platform information to the resume management system.

7. A resume management system, characterized in that, The resume management system includes personal user nodes, enterprise user nodes, third-party authentication nodes, resume center management nodes, and recruitment platform nodes. The resume management system is used to execute the management method of the blockchain resume center as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, It stores a computer program, which is loaded by a processor to execute the management method of the blockchain resume center according to any one of claims 1 to 6.

Images