Virtual resource configuration system, device and program product based on job hunting behavior

Abstract

The invention discloses a virtual resource configuration system and device based on job hunting behaviors, a program product and a computer readable storage medium. The system comprises an invitation ID generation module used for generating an invitation ID; the registration association module is used for responding to the condition that the first user uses the invitation ID to register an account, and storing the invitation relationship between the first user and the second user into the graph database based on the invitation ID; the position configuration module is used for issuing positions and configuring position reward information by enterprise users; the job-hunting behavior acquisition module is used for acquiring job-hunting behavior information of the first user; the enrollment resource allocation module is used for sending resource allocation information for the second user based on the position reward information configured by the enterprise user and the invitation relationship related to the first user when the first user is entered by the enterprise user; an enterprise resource allocation module; a user resource allocation module; and a virtual resource cancel-after-verification module. By utilizing the embodiment of the invention, the propagation effect can be improved by improving the utilization rate of the virtual resources.

Description

Technical Field

[0001] This application relates to the field of internet recruitment technology, and in particular to a virtual resource allocation system, device, program product and storage medium based on job-seeking behavior. Background Technology

[0002] Existing recruitment platforms typically offer tools such as job posting coupons to employers and service vouchers to job seekers to increase the success rate of job exposure, resume submission, and interview opportunities. However, the distribution and use of coupons and other benefits are mostly based on fixed, preset rules, making it difficult to dynamically intervene based on job seekers' job search behavior at different stages and the conversion rate of job postings. This results in poor actual effectiveness of the benefits.

[0003] In terms of user growth and dissemination, existing rights and benefits mechanisms often focus on the invitation or sharing behavior itself, and pay insufficient attention to the core business outcome of "whether or not the employee is actually hired". There is no binding relationship between the triggering of rights and benefits and the actual recruitment results, which affects the effectiveness of the use of virtual resources.

[0004] In terms of resource collaboration, the rights and interests systems of enterprises and job seekers are often set up independently and settled separately, which may lead to anomalies such as duplicate verification and partial success, affecting the accuracy of account data and user experience. Summary of the Invention

[0005] In view of this, embodiments of this application provide a virtual resource allocation system based on job-seeking behavior, an electronic device, a computer-readable storage medium, and a computer program product, solving at least one technical problem.

[0006] This application provides a virtual resource allocation system based on job-seeking behavior, comprising: an invitation ID generation module for generating an invitation ID, the invitation ID including at least a first user ID, a second user ID, and user level information, the user level information including the invitation relationship between the second user and the first user, wherein the invitation ID is generated in multiple independent segments, each segment being assigned an independent segment lock; a registration association module, in response to the first user registering an account using the invitation ID, saving the invitation relationship between the first user and the second user to a graph database based on the invitation ID; and a job configuration module for enterprise users to post jobs and configure job reward information, the job reward information including virtual resource type, virtual resource quantity, and virtual resource allocation mechanism, the virtual resources being stored in the enterprise account, wherein the virtual resources include at least a first virtual resource and a second virtual resource, the first virtual resource being used to redeem... The system comprises: a second virtual resource; a job-seeking behavior acquisition module, used to acquire job-seeking behavior information of the first user, including at least one of click information, page dwell time, resume submission, back-end communication, interview invitation, interview result, and hiring result; a hiring resource allocation module, used to issue resource allocation information to the second user when the first user is hired by the enterprise user, based on the job reward information configured by the enterprise user and the invitation relationship related to the first user; an enterprise resource allocation module, used to issue resource allocation information to the first user or the second user based on the enterprise's intention to send the second virtual resource in the enterprise account to the first user or the second user; a user resource allocation module, used to issue resource allocation information to the first user based on the second virtual resource in the user account to the first user; and a virtual resource verification module, used to synchronously verify the virtual resources of the enterprise account and the user account based on the resource allocation information and job-seeking behavior information.

[0007] Optionally, it also includes: an interview resource allocation module, which sends resource allocation information to the first user in response to the first user's resume submission failure rate falling below a preset threshold; and a dynamic threshold calculation module, which adjusts the preset threshold based on the first user's resume submission interview conversion rate being lower than the system average.

[0008] Optionally, the user hierarchy information further includes the invitation relationship between the third user and the second user, wherein the third user's user hierarchy is higher than that of the second user; the registration association module, in response to the first user registering an account using the invitation ID, saves the invitation relationship between the first user, the second user, and the third user to the graph database based on the invitation ID.

[0009] Optionally, when the first user is recruited by the enterprise user, the recruitment resource allocation module sends resource allocation information to the second user and the third user based on the job reward information configured by the enterprise user and the invitation relationship related to the first user, wherein the resource allocation ratio of the third user is lower than that of the second user.

[0010] Optionally, the virtual resource verification module includes: a dual-end verification submodule, which verifies the legitimacy of the enterprise and user identities respectively through RSA digital signatures and biometric information; and a distributed processing submodule, which performs synchronous verification of virtual resources of enterprise accounts and user accounts through a distributed transaction framework based on resource allocation information and job application behavior information.

[0011] Optionally, the synchronized cancellation of virtual resources between enterprise accounts and user accounts through a distributed transaction framework includes: attempting to reserve the rights corresponding to the value of the virtual resource in the enterprise account and recording the intention to use the virtual resource; if the reservation is successful, performing the actual resource deduction operation to deduct the corresponding resource from the enterprise account; at the same time, the corresponding rights in the user account will be unlocked; if an abnormality occurs during the reservation process, a cancellation operation will be triggered to roll back all executed steps and restore the data to its initial state.

[0012] Optionally, it further includes: a data feedback module, which, after virtual resource verification, returns the verification data to the enterprise user's backend to calculate and display the effect of virtual resource verification.

[0013] This application provides an electronic device, which includes a processor and a memory storing computer program instructions; the electronic device implements the system described above when executing the computer program instructions.

[0014] This application provides a computer program product, which includes computer program instructions that, when executed, implement the system described above.

[0015] This application provides a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the system described above.

[0016] Using the embodiments of this application, enterprises can set first and second virtual resources and their exchange ratios in job postings. The system generates an invitation ID for each invitation, containing user invitation relationships and hierarchical information. When the first user registers with this invitation ID, the invitation relationship between the second user and the first user is written into the graph database. Clicks, page dwells, resume submissions, backend communication, interview invitations, interview results, and hiring results are sent via event tracking. When actual conversion rates are weak, the threshold for sending virtual resources is adjusted. When a hiring occurs, the system settles accounts with the corresponding user according to the records in the graph database. During verification, the enterprise side uses RSA digital signatures, and the user side performs liveness detection. After successful verification, the enterprise account and user account are processed synchronously based on a distributed transaction framework.

[0017] The invitation relationships in this application can be entered once during registration and used for subsequent settlement, making it less likely to be missed or recalculated. Dynamic thresholds allow the second virtual resource to be used more effectively at key stages of the job search process, ensuring it reaches eligible job seekers as early as possible and avoiding unnecessary waste in some cases. The distribution of virtual resources is recorded and traceable. RSA and liveness detection reduce the risk of impersonation, and the distributed transaction framework for synchronous processing of enterprise and user accounts reduces the possibility of successful verification on only one end or duplicate verification. The distribution of some virtual resources is linked to the hiring results, reducing resource waste and ineffective dissemination. Kanban data directly displays the effectiveness of positions and stages, allowing for adjustments to subsequent thresholds, allocation ratios, and redemption ratios. This application integrates the virtual resource systems of enterprises and job seekers into a unified system, creating a synergistic effect and improving the efficiency and effectiveness of related processes. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings of the embodiments of this application will be briefly described below.

[0019] Figure 1 This is a schematic diagram of the system architecture of an embodiment of this application.

[0020] Figure 2 This is a flowchart of a virtual resource allocation system based on job-seeking behavior, according to an embodiment of this application.

[0021] Figure 3 This is a schematic diagram of an electronic device used to implement the virtual resource allocation system based on job-seeking behavior in the embodiments of this application. Detailed Implementation

[0022] The principles and spirit of this application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided to make the principles and spirit of this application clearer and more thorough. The exemplary embodiments provided herein are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application.

[0023] Embodiments of this application relate to terminal devices and / or servers. Implementations of this application can be a system, terminal, device, computer-readable storage medium, or computer program product, and can be specifically implemented as entirely hardware, entirely software, or a combination of hardware and software. Figure 1 This diagram illustrates a system architecture according to an embodiment of the present application, including a terminal device 102 and a server 104. The terminal device 102 may include at least one of the following: a smartphone, tablet computer, laptop computer, desktop computer, smart TV, various wearable devices, augmented reality (AR) devices, virtual reality (VR) devices, etc. A client application, such as an app, mini-program, or browser-based client, can be installed on the terminal device 102. Users can input commands through the client, and the terminal device 102 can send request information containing the commands to the server 104. Upon receiving the request information, the server 104 performs corresponding processing and returns the processing result information to the terminal device 102. The server 104 may be a local server or a cloud server, and may be a single server or a server cluster, etc.

[0024] In this document, the terms "first," "second," "third," etc., are used only to distinguish one entity (or operation) from another in textual description, and do not require or imply any sequential order between these entities (or operations).

[0025] Figure 2 This paper illustrates a flowchart of a virtual resource allocation system based on job-seeking behavior, according to an embodiment of this application. The system includes the following steps: S101: Generate an invitation ID, which includes at least a first user ID, a second user ID, and user hierarchy information. The user hierarchy information includes the invitation relationship between the second user and the first user. The invitation ID is generated in multiple independent segments, and each independent segment is assigned an independent segment lock.

[0026] S102: In response to the first user registering an account using the invitation ID, save the invitation relationship between the first user and the second user to the graph database based on the invitation ID.

[0027] S103: Enterprise users post job positions and configure job reward information. The job reward information includes virtual resource type, virtual resource quantity and virtual resource allocation mechanism. Virtual resources are stored in the enterprise account. The virtual resources include at least a first virtual resource and a second virtual resource. The first virtual resource is used to redeem the second virtual resource.

[0028] S104: Obtain job search behavior information of the first user, which includes at least one of the following: click information, page stay, resume submission, back-end communication, interview invitation, interview result and hiring result.

[0029] S105: When the first user is accepted by the enterprise user, resource allocation information for the second user is sent based on the job reward information configured by the enterprise user and the invitation relationship related to the first user.

[0030] S106: Based on the enterprise's intention to send the enterprise's second virtual resource to the first or second user, issue resource allocation information for the first or second user.

[0031] S107: Based on the fact that the second user wants to send the second virtual resource in the user account to the first user, send resource allocation information for the first user.

[0032] S108: Based on resource allocation information and job search behavior information, synchronize and cancel virtual resources of enterprise accounts and user accounts.

[0033] According to the processing method of this application embodiment, the system generates an invitation ID for each invitation, containing a first user ID, a second user ID, and hierarchical information. When the first user registers with this invitation ID, the invitation relationship between the second user and the first user is written into the graph database. Clicks, page dwells, resume submissions, backend communication, interview invitations, interview results, and hiring results are sent via event tracking. Enterprises can set the distribution ratio of virtual resources in job positions, and when a hiring occurs, the system settles accounts with the relevant users according to the method in the graph database.

[0034] The advantages of this approach are that the invitation relationship is written once during registration and can be used for subsequent settlement, reducing the likelihood of missed or recalculated settlements. For high-concurrency scenarios, segment locks are used to improve ID generation performance. The distribution of virtual resources is recorded and traceable. The distribution of some virtual resources is linked to the admission results, reducing resource waste and ineffective propagation.

[0035] Optionally, according to an embodiment of this application, the system further includes: an interview resource allocation module, which sends resource allocation information for the first user in response to the first user's resume submission failure rate being lower than a preset threshold; and a dynamic threshold calculation module, which adjusts the preset threshold based on the first user's resume submission interview conversion rate being lower than the system average.

[0036] For example, if a user's number of "not yet interviewed" applications falls below the platform's initial threshold for that position after submitting several resumes, the system will trigger resource allocation for that user. Simultaneously, based on the position's recent interview conversion rate being below the global average, the initial threshold will be dynamically lowered to allow for earlier intervention. The reason for this approach is that linking the "not yet interviewed" count to the position's real-time conversion rate allows for targeted virtual resource allocation to be triggered earlier when conversion rates weaken, reducing the lag caused by conventional methods and thus improving the conversion efficiency from application to interview without changing the position's configuration.

[0037] According to an embodiment of this application, optionally, the user hierarchy information further includes the invitation relationship between the third user and the second user, where the third user's user hierarchy is higher than that of the second user; the registration association module, in response to the first user registering an account using the invitation ID, saves the invitation relationship between the first user, the second user, and the third user to the graph database based on the invitation ID.

[0038] The invitation ID contains hierarchical information for "third user, second user, and first user." When the first user registers with this ID, the system writes the invitation relationship between the three users into the graph database at once. Subsequently, when admission is triggered, it can directly trace back to the second and third users in a predetermined direction. The reason for this approach is that synchronously solidifying multi-level relationships during registration avoids the need for subsequent cross-table splicing or supplementary entry of links, ensuring both the consistency and traceability of the path, and providing a stable data foundation for subsequent multi-level settlement.

[0039] According to an embodiment of this application, optionally, when a first user is recruited by an enterprise user, the recruitment resource allocation module sends resource allocation information to a second user and a third user based on the job reward information configured by the enterprise user and the invitation relationship related to the first user, wherein the resource allocation ratio of the third user is lower than that of the second user.

[0040] After the first user is selected, the system calculates and allocates rewards to the second and third users according to the configuration. The second user receives a base reward, while the third user receives a lower reward, thus decreasing the reward with each level. The reason for this approach is to strongly link the allocation result to the "actual recruitment," while setting a decreasing ratio for further levels. This highlights the weight of direct contributors and suppresses cost spillover caused by deep diffusion, allowing the budget to be more concentrated on the effective links.

[0041] According to an embodiment of this application, optionally, the virtual resource verification module includes: a dual-end verification submodule, which verifies the legitimacy of the enterprise and user identities respectively through RSA digital signature and biometric information; and a distributed processing submodule, which performs synchronous verification of virtual resources of enterprise accounts and user accounts through a distributed transaction framework based on resource allocation information and job search behavior information.

[0042] Enterprise-side reconciliation requests must pass RSA digital signature verification, while user-side requests must pass biometric liveness verification. After successful verification, the distributed transaction submodule executes "enterprise account deduction" and "user account unlocking" as a single process, synchronously. This approach reduces the risk of impersonation and forgery by performing dual-end legitimacy verification at the entry point, and the distributed transaction ensures synchronous updates on both ends, reducing inconsistencies and duplicate reconciliations caused by "only one end succeeding," thus improving the security and controllability of the reconciliation process.

[0043] According to an embodiment of this application, optionally, the synchronous cancellation of virtual resources between enterprise accounts and user accounts through a distributed transaction framework includes: attempting to reserve the rights corresponding to the value of the virtual resource in the enterprise account and recording the intention to use the virtual resource; if the reservation is successful, performing the actual resource deduction operation to deduct the corresponding resource from the enterprise account; at the same time, the corresponding rights in the user account will be unlocked; if an abnormality occurs during the reservation process, a cancellation operation will be triggered to roll back all executed steps and restore the data to its initial state.

[0044] Before executing the write-off, the system first "attempts" to reserve a credit limit for the enterprise account and records the intent. Only if the reservation is successful is the system "confirmed" to deduct and unlock user benefits. If any step fails, the system is "cancelled" and rolled back to the initial state, thus incorporating modifications from both ends into the same transaction process. The reason for this approach is that using a distributed transaction of "attempt-confirm-cancel" to make cross-end updates corresponding to commits or rollbacks maintains accuracy and reliability even during network fluctuations or service anomalies.

[0045] Optionally, according to an embodiment of this application, the system further includes: a data feedback module, which, after virtual resource cancellation, returns the cancellation data to the enterprise user backend to calculate and display the effect of virtual resource cancellation.

[0046] After the reconciliation is completed, the system feeds back the reconciliation details and related links to the enterprise backend, automatically summarizing and displaying the reconciliation effects and unit conversion costs for different positions and stages in the dashboard, for business review and parameter fine-tuning. The reason for this approach is that by structuring and visualizing the reconciliation results, the effectiveness of the distribution and bottlenecks in the process can be evaluated under the same standard, providing a direct basis for subsequent optimization of thresholds, ratios, and resource types, and improving the efficiency of auditing and problem identification.

[0047] The implementation methods and advantages of the embodiments of this application have been described above through multiple examples. The specific processing procedures of the embodiments of this application are described in detail below with reference to specific examples.

[0048] In this embodiment, user A is a job seeker or user of an invitation code (userId: u123), user B is an inviter or sharer of an invitation code (userId: u456), and company A is the job poster (enterpriseId: e789, company name "Xingchen Technology").

[0049] When User B clicks "Share Invitation Code" on the job details page, the system generates a distributed, unique invitation ID (e.g., inviteId="1:u456;2:u123") based on the Snowflake algorithm, containing hierarchical relationships. This ID explicitly identifies level 1 as the direct inviter u456 and level 2 as the user u123. The invitation ID and its hierarchical information, along with the timestamp and consistency verification field, are written to MongoDB for tracing the relationship chain. After User A enters this invitation ID on the registration page, the system writes the relationship "User B invites User A" into the graph database. If there are also superior inviters, the system also writes the invitation relationships between multiple users, forming an invitation graph. Subsequent settlements and traceability are based on this graph.

[0050] Company A publishes a job posting on the job configuration page, for example, "Java Development Engineer - P1" (positionId: p1001). It sets up job reward information, defining the first virtual resource as "points" and the second virtual resource as "service benefits," along with the point allocation ratio and decay parameters for each level of inviters. This configuration is then bound to the job and stored in the configuration repository. Job seeker behavior is collected: events such as user A's clicks on job P1, page dwell time, resume submission, backend communication, interview invitations, interview results, and hiring results are generated in real-time via frontend tracking. These events are entered into a Kafka topic and stored. The Flink job performs sliding or flipping window statistics based on event time for the application and interview stages. It also maintains a comparison between the "conversion rate in the last 7 days" and the "historical average of 30 days." When the conversion rate for a particular job is detected to be significantly lower than the system average, the trigger threshold for "continuous applications without an interview" is smoothly tightened from 5 times to 3 times. Once the conversion rate recovers to the set range, the original value is gradually restored to avoid threshold jumps caused by short-term fluctuations. In some embodiments, a dynamic adjustment strategy is executed through a rule-based decision engine to calculate thresholds in real time using the EWMA algorithm based on historical data (such as average job posting conversion rates).

[0051] If, within the effective period of this threshold, user A experiences three consecutive "no interview after application" events for position P1, and the cumulative number of such events reaches or exceeds the current threshold, the rule judgment is passed, and the system calls the coupon issuance service to issue a second virtual resource to user A's account, such as sending a mock interview coupon, to help the user conduct mock interviews and improve the user's interview success rate.

[0052] After User A is hired by Xingchen Technology, the enterprise-side system sends the hiring result back via API. The platform reads the job reward information and graph database in the hiring resource allocation module, calculates the points due according to the order of "u456 as the first level, and the second level if a third user exists," and allocates the rights and benefits to the second level and beyond according to the configuration. The allocation is only generated when the hiring event is established, forming a multi-level reward strongly bound to the hiring. The points are credited to the respective points accounts, recording the allocation details, level, proportion, and invitation ID to avoid over- or under-counting.

[0053] Enterprises can directly issue second virtual resources to user A or user B according to the configuration. User B can also transfer the second virtual resources in their personal center to user A. Alternatively, user A or user B can exchange their first virtual resources for second virtual resources and then transfer them to the corresponding user. Multiple channels are issued within the system using a unified command format and enter the verification process.

[0054] Enterprise-side reconciliation requests must include an RSA digital signature; the platform verifies the signature before proceeding. User A completes a liveness check at the reconciliation entry point; upon successful verification, the process enters consistency handling. Synchronous reconciliation: The system uses a TCC (Try, Confirm, Cancel) process to handle cross-platform changes. During the trial phase, an amount equivalent to the resource to be reconciled is reserved in the enterprise account, and the intended use is recorded. During the confirmation phase, the enterprise account deduction and user account unlocking are executed in pairs. If network jitter, storage unavailability, or conflict occurs at any step, the cancellation phase is initiated, revoking the reservation and rolling back executed modifications, returning both ends to their pre-reconciliation state. All reconciliation requests carry an identifier, which is used as a unique constraint during writes to prevent duplicate reconciliations. After successful verification, the system writes "Job P1, Invitation Relationship, Type and Quantity of Second Virtual Resources Issued, Points Changes and Redemption Details" back to the data processing system, calculates indicators for job and stage dimensions, and analyzes the results in the data analysis platform and displays them on the Kibana dashboard by job and stage. Company A observes the actual use and interview correlation of "Resume Optimization Service" and "Interview Training Card" based on this data, and fine-tunes the thresholds and allocation ratios according to the dashboard data.

[0055] Through the above processing, the data is written to the graph database upon registration and directly used for allocation during recruitment. Kafka+Flink tracks threshold adjustment and triggering processes to window statistics and event timing. The basis for coupon issuance and the issuance results are traceable through the link logs. RSA digital signatures and liveness detection ensure the legitimacy of the reimbursement entry point on both the requester and user sides. TCC makes "enterprise account deduction - user account unlocking" a paired submission / rollback. The details after reimbursement flow back to the dashboard to form a visual view of positions and stages. Based on this, the enterprise side continuously fine-tunes the job reward information and threshold settings to align "who receives it, when it is issued, and what it is issued" with the actual relationship of position P1. The inflows at both ends of the account are verified and traced under the same standard.

[0056] Based on at least one of the above embodiments, the electronic device in the embodiments of this application may be a user terminal device, a server, other computing devices, or a cloud server. Figure 3 The diagram shows the hardware structure of an electronic device according to an embodiment of this application. The electronic device may include a processor 601 and a memory 602 storing computer program instructions. The processor 601 reads and executes the computer program instructions stored in the memory 602 to implement the process or function of any of the systems in the above embodiments.

[0057] Specifically, processor 601 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. Memory 602 may include mass storage for data or instructions. For example, memory 602 may be at least one of the following: hard disk drive (HDD), read-only memory (ROM), random access memory (RAM), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, universal serial bus (USB) drive, or other physical / tangible memory storage device. Alternatively, memory 602 may include removable or non-removable (or fixed) media. Furthermore, memory 602 may be internal or external to the integrated gateway disaster recovery device. Memory 602 may be non-volatile solid-state memory. In other words, typically memory 602 includes a tangible (non-transitory) computer-readable storage medium (such as a memory device) encoded with computer-executable instructions, and when the software is executed (e.g., by one or more processors), it can perform the operations described in the system embodiments of this application.

[0058] As an example, Figure 3The illustrated electronic device may also include a communication interface 603 and a bus 610. The processor 601, memory 602, and communication interface 603 are connected via bus 610 and communicate with each other. Bus 610 may include hardware, software, or both, and may couple components of an online data traffic metering device together. The bus may include at least one of the following: Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) Interconnect, Industry Standard Architecture (ISA) bus, Infinite Bandwidth Interconnect, Low Pin Count (LPC) bus, memory bus, Microchannel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus, or other suitable bus. Bus 610 may include one or more buses. Although specific buses are described or shown in the embodiments of this application, any suitable bus or interconnection method is contemplated in the embodiments of this application.

[0059] In conjunction with the systems in the above embodiments, this application also provides a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the processes or functions of any of the systems in the above embodiments.

[0060] This application also provides a computer program product that stores computer program instructions, which, when executed by a processor, implement the process or function of any of the systems described above.

[0061] The flowcharts and / or block diagrams of systems, terminals, systems, and computer program products according to embodiments of this application have been exemplarily described above, and related aspects have been described. It should be understood that each block or combination thereof in the flowcharts and / or block diagrams may be implemented by computer program instructions, by dedicated hardware performing a specified function or action, or by a combination of dedicated hardware and computer instructions. For example, these computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to form a machine such that these instructions, executed via such processor, enable the implementation of the function / action specified in each block or combination thereof in the flowcharts and / or block diagrams. Such a processor may be a general-purpose processor, a dedicated processor, a special-purpose application processor, or a field-programmable logic circuit.

[0062] The functional blocks shown in the structural block diagrams of this application can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc.; when implemented in software, they are programs or code segments used to perform the required tasks. Programs or code segments can be stored in memory or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. Code segments can be downloaded via computer networks such as the Internet or intranets.

[0063] It should be noted that this application is not limited to the specific configurations and processes described above or shown in the figures. The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the described systems, devices, terminals, modules, or units can be referred to the corresponding processes in the system embodiments, and need not be repeated here. It should be understood that the scope of protection of this application is not limited thereto. Any equivalent modifications or substitutions that can be conceived by those skilled in the art within the scope of the technology disclosed in this application should be covered within the scope of protection of this patent application.

Claims

1. A virtual resource allocation system based on job-seeking behavior, characterized in that, include: An invitation ID generation module is used to generate an invitation ID, which includes at least a first user ID, a second user ID, and user hierarchy information. The user hierarchy information includes the invitation relationship between the second user and the first user. The invitation ID is generated in multiple independent segments, and each independent segment is assigned an independent segment lock. The registration association module is used to respond to the first user registering an account using the invitation ID, and save the invitation relationship between the first user and the second user to the graph database based on the invitation ID; The job configuration module is used by enterprise users to post jobs and configure job reward information. The job reward information includes virtual resource type, virtual resource quantity and virtual resource allocation mechanism. The virtual resources are stored in the enterprise account. The virtual resources include at least a first virtual resource and a second virtual resource. The first virtual resource is used to redeem the second virtual resource. The job search behavior acquisition module is used to acquire job search behavior information of the first user; The recruitment resource allocation module is used to issue resource allocation information to the second user when the first user is recruited by the enterprise user, based on the job reward information configured by the enterprise user and the invitation relationship related to the first user; The enterprise resource allocation module is used to send the second virtual resource of the enterprise account to the first or second user, and to issue resource allocation information for the first or second user. The user resource allocation module is used to send the second virtual resources in the user account of the second user to the first user, and to issue resource allocation information for the first user. The virtual resource verification module is used to synchronously verify virtual resources for enterprise accounts and user accounts based on resource allocation information and job search behavior information.

2. The system according to claim 1, characterized in that, Also includes: The interview resource allocation module is used to send resource allocation information to the first user when the number of times the first user has not been interviewed after submitting their resume is lower than a preset threshold. The dynamic threshold calculation module is used to adjust the preset threshold when the interview conversion rate of the first user's resume submission is lower than the system average.

3. The system according to claim 1, characterized in that, The user hierarchy information further includes the invitation relationship between the third user and the second user, wherein the third user's user hierarchy is higher than that of the second user; The registration association module is also used to respond to the first user registering an account using the invitation ID, and based on the invitation ID, save the invitation relationship between the first user, the second user, and the third user to the graph database.

4. The system according to claim 3, characterized in that, The recruitment resource allocation module is also used to issue resource allocation information to the second and third users after the first user is recruited by the enterprise user, based on the job reward information configured by the enterprise user and the invitation relationship related to the first user, wherein the resource allocation ratio of the third user is lower than that of the second user.

5. The system according to claim 1, characterized in that, The virtual resource verification module includes: The dual-end verification submodule verifies the legitimacy of the enterprise and user identities using RSA digital signatures and biometric information, respectively. The distributed processing submodule, based on resource allocation information and job search behavior information, synchronizes and verifies the virtual resources of enterprise accounts and user accounts through a distributed transaction framework.

6. The system according to claim 1, characterized in that, The process of synchronizing and resolving virtual resources between enterprise accounts and user accounts using a distributed transaction framework includes: Try reserving the corresponding rights in the enterprise account for the value of the virtual resource, and record the intended use of the virtual resource; If the reservation is successful, the actual resource deduction operation will be performed, and the corresponding resources will be deducted from the enterprise account; at the same time, the corresponding rights in the user account will be unlocked. If an exception occurs during the reservation process, a cancellation operation will be triggered, rolling back all executed steps and restoring the data to its initial state.

7. The system according to claim 1, characterized in that, Further includes: The data feedback module is used to send the verification data back to the enterprise user's backend after the virtual resource verification is completed, and to calculate and display the effect of the virtual resource verification.

8. The system according to claim 1, characterized in that, The job search behavior information includes at least one of the following: click information, page stay, resume submission, back-end communication, interview invitation, interview result, and employment result.

9. An electronic device, characterized in that, The electronic device is a terminal device or a server. The electronic device includes a processor and a memory storing computer program instructions. When the electronic device executes the computer program instructions, it implements the system as described in any one of claims 1-8.

10. A computer program product, characterized in that, It includes computer program instructions that, when executed, implement the system as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, It stores computer program instructions that, when executed, implement the system as described in any one of claims 1-8.

Images