Resource connection method and device, equipment and storage medium

Abstract

The invention provides a resource connection method and device, equipment and a storage medium, and relates to the technical field of resource management. The method comprises the following steps: acquiring resource connection request information of a requester for a resource quota to be returned, wherein the resource connection request information comprises operation performance information, resource exchange contract information and credibility information; determining a resource connection qualification score based on the resource connection request information, and determining a verification result according to a preset verification rule when the score exceeds a threshold value; after the verification is passed, determining a connection resource quota based on the agreed return resource quota, and constructing a resource connection contract; and in response to confirmation of the requester on the contract, updating the resource quota state to complete resource connection. According to the invention, the automation of the resource connection process can be realized, and the verification and execution efficiency of resource connection is remarkably improved.

Description

Technical Field

[0001] This application relates to the field of resource management technology, and in particular to resource connection methods, apparatus, devices, and storage media. Background Technology

[0002] In business scenarios involving resource allocation to entity objects, there may be situations where the occupied resources cannot be returned after the initial resource usage phase ends. Therefore, there is a need to extend the currently occupied resources to subsequent phases for repayment.

[0003] Currently, mainstream resource succession solutions typically require entities to seek bridging resources to return the occupied resources first, and then reapply for new occupied resources to return to the bridging resource provider. In this process, the succession of occupied resources is achieved, reducing the risk of resource default for entities.

[0004] However, this solution effectively splits resource continuity into two separate resource requests, making it difficult to guarantee business continuity. Furthermore, the two separate resource requests involve multiple resource transfer and verification operations, resulting in low efficiency in resource continuity. Summary of the Invention

[0005] This application provides a resource connection method, apparatus, device, and storage medium for merging two independent resource requests into an automated resource connection process, eliminating dependence on bridging resources, and effectively improving the efficiency of resource connection.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions: Firstly, a resource continuation method is provided, which includes: First, the system obtains the resource continuation request information from the requesting party regarding the resources to be returned. This information includes the requester's operational information, resource exchange contract information, and credibility information. The resource exchange contract includes the agreed-upon return resources from the core enterprise to the requester. Second, based on the operational information, resource exchange contract information, and credibility information, the system determines the requester's resource continuation eligibility score. If the eligibility score exceeds a threshold, the system verifies the resource continuation request information according to preset resource continuation verification rules. Then, if the verification is successful, the system determines the requester's continuation resources based on preset resource conversion rules and the agreed-upon return resources, and constructs a resource continuation contract. This contract stipulates that the continuation resources will be returned as resources to be returned. Finally, in response to the requester's confirmation of the resource continuation contract, the status of the resources to be returned is changed to "returned," thus completing the resource continuation.

[0007] This application provides a resource continuation method. First, it determines the resource continuation eligibility score by using the requester's multi-dimensional information (operational information, credibility information, and resource exchange contract information), accurately assessing the requester's resource return capability. Second, it achieves automatic screening by setting eligibility score thresholds, effectively filtering requests that do not meet the basic conditions and significantly reducing the processing pressure of subsequent verification stages. Furthermore, it automatically verifies the filtered requests based on preset verification rules, ensuring the uniformity of verification standards and the efficiency of the process. Finally, it generates continuation resources and constructs continuation contracts through resource conversion rules, automatically updating the resource status upon confirmation, completing the fully automated process of resource continuation. Compared with the traditional "return first, then apply" resource continuation scheme, this application uses agreed-upon return resources as the basis and achieves the continuation of resources to be returned through an automated process, effectively solving the problems of low efficiency and high operating costs caused by fragmented processes in existing schemes, and effectively improving the efficiency of resource continuation.

[0008] In one possible implementation of the first aspect, the requester's operational information includes: the requester's total revenue resources, the requester's resource return rate, the requester's available resources, the requester's resource turnover rate, and the requester's own resource return rate; the requester's resource exchange contract information includes: the number of resource exchange contracts, the frequency of resource exchange contract creation, the frequency of resource exchange receipt by the requester, the duration of resource exchange contracts, and records of conflict events of resource exchange contracts; the requester's credibility information includes: the requester's historical default records, the requester's unreturned resources, the frequency of credibility queries by the requester, the requester's overdue resource return records, and the requester's records of regulatory issues.

[0009] It should be understood that this scheme specifies more detailed information, providing a more comprehensive data foundation for assessing the requester's eligibility for resource continuity, thus improving the accuracy and reliability of resource continuity eligibility scoring. Furthermore, this refined classification method supports different business scenarios, enhancing the scheme's scalability.

[0010] In another possible implementation of the first aspect, the requester's resource succession eligibility score is determined based on operational information, resource exchange contract information, and trust information, including: determining the requester's operational status score based on the requester's operational information; determining the requester's resource exchange contract stability score based on the requester's resource exchange contract information; determining the requester's trust score based on the requester's trust information; and determining the requester's resource succession eligibility score based on the operational status score, trust score, and resource exchange contract stability score.

[0011] It should be understood that this scheme decomposes the assessment of the requester's eligibility for resource continuation into multiple assessment dimensions, thereby achieving standardization and systematization of the assessment process. Specifically, this scheme ensures that the scoring of each dimension is completed independently based on its corresponding professional assessment perspective, while also ensuring the comprehensiveness and consistency of the final resource continuation eligibility score.

[0012] In another possible implementation of the first aspect, the requester's resource continuation eligibility score is determined based on the operational status score, credibility score, and resource exchange contract stability score. This includes: determining the requester's credibility enhancement score based on the preset security score of the requester's domain and the existence of security assurance resources in the resource continuation request information; the security assurance resources are used to provide performance guarantees for resource continuation; and the operational status score, credibility score, resource exchange contract stability score, and credibility enhancement score are weighted and summed to determine the requester's resource continuation eligibility score.

[0013] It should be understood that by introducing domain security assessment and security assurance resource verification, this solution can additionally consider domain security characteristics and assurance factors in the resource continuity eligibility assessment, thereby effectively identifying and filtering unreliable resource continuity requests in advance.

[0014] In another possible implementation of the first aspect, the resource succession eligibility score of the requester is determined by weighted summation of the operational status score, credibility score, resource exchange contract stability score, and credit enhancement score, including: determining the requester's resource succession eligibility score according to the following formula: ; in, Indicates the score for eligibility to continue receiving resources; Indicates operational status score, express The weights; Indicates credibility score, express The weights; Indicates the stability score of the resource exchange contract. express The weights; Indicates credit enhancement score, express The weights; , , as well as The sum of is 1.

[0015] It should be understood that this scheme, by introducing a weighted calculation formula, quantitatively integrates multi-dimensional scores into a unified resource continuation eligibility score. This not only ensures the transparency and repeatability of the scoring process but also reflects the relative importance of each evaluation dimension through the setting of weight coefficients. This formulaic approach provides a reliable algorithmic foundation for automated verification, ensuring good consistency and comparability of evaluation results, while also facilitating the adjustment of weight parameters according to actual business needs to optimize evaluation effectiveness.

[0016] In another possible implementation of the first aspect, based on preset resource continuity verification rules, the verification result of the resource continuity request information is determined, including: if the resource yield rate in the requester's operational information is greater than the yield rate threshold and the resource turnover rate is greater than the turnover rate threshold, the first verification result is determined to be passed; if the resource exchange contract information in the requester's resource exchange contract information is greater than the frequency threshold and the number of conflict event records is less than the quantity threshold, the second verification result is determined to be passed; if the historical default records in the requester's credibility information are less than the default number threshold and the quota of unreturned resources is less than the quota threshold, the third verification result is determined to be passed; if the first verification result, the second verification result, and the third verification result are all passed, the verification result of the resource continuity request information is determined to be passed.

[0017] It should be understood that this solution, by establishing structured, multi-level verification rules, clearly refines the verification conditions for resource continuity into quantitative indicators across three dimensions: operational efficiency, contract stability, and credibility. This rule-based verification mechanism not only achieves uniformity and transparency in verification standards but also ensures flexibility and adaptability through configurable threshold parameters. This design allows verification decisions to be based entirely on objective data indicators, effectively reducing the interference of subjective judgment, while also providing traceable decision-making evidence, significantly improving the efficiency and reliability of the verification process.

[0018] In another possible implementation of the first aspect, if the verification result is successful, the requester's successor resources are determined based on the preset resource conversion rules and the agreed-upon reward resources, and a resource succession contract is constructed. This includes: if the verification result is successful, sending a verification request for the resource exchange contract for the requester to the core enterprise's server; if the core enterprise's server returns a valid verification result, determining the requester's successor resources based on the preset resource conversion rules and the agreed-upon reward resources, and constructing a resource succession contract.

[0019] It should be understood that this solution, by introducing a verification interaction mechanism with the core enterprise's server, confirms the validity of the underlying contract before determining the resources to be transferred. This verification step effectively ensures the authenticity and validity of the resource exchange contract that forms the basis for the transfer, and identifies resource transfer operations based on invalid or abnormal contracts in advance. Furthermore, the design of making the core enterprise's confirmation a prerequisite not only ensures the compliance of the transfer process but also enhances the reliability of the overall process through a multi-party verification mechanism.

[0020] In another possible implementation of the first aspect, the method further includes: when the resource difference between the successor resource and the resource to be returned is negative, determining the new resource to be returned to the requester based on the sum of the absolute value of the resource difference and the successor resource.

[0021] It should be understood that this solution determines the extent to which the resource to be returned is to be returned by comparing the resource difference between the continuing resource and the resource to be returned. When the continuing resource is insufficient, the uncovered part is automatically transferred to the continuing resource as a new resource to be returned, thus realizing the integrity management of resource continuity.

[0022] Secondly, a resource connection device is provided, the device comprising: The acquisition module is used to obtain resource continuation request information from the requesting party regarding the return of resources. This resource continuation request information includes: the requester's operational information, the requester's resource exchange contract information, and the requester's credibility information. The resource exchange contract includes the agreed-upon return resources from the core enterprise to the requester.

[0023] The processing module determines the requester's resource continuation eligibility score based on operational information, resource exchange contract information, and credibility information. If the eligibility score exceeds a threshold, the module verifies the resource continuation request information according to preset resource continuation verification rules. If the verification is successful, the module determines the requester's continuation resources based on preset resource conversion rules and agreed-upon return resources, and constructs a resource continuation contract. The resource continuation contract stipulates that the continuation resources will be returned as resources to be returned. In response to the requester's confirmation of the resource continuation contract, the status of the resources to be returned is changed to "returned," thus completing the resource continuation.

[0024] Thirdly, a resource extension device is provided, the method comprising: a memory and at least one processor. The memory is communicatively connected to the processor. The memory is used to store computer program code, the computer program code including computer instructions. When the processor executes the computer instructions, it causes the resource extension device to perform the method as described in the first aspect and any possible implementation thereof.

[0025] Fourthly, a computer-readable storage medium is provided that stores computer instructions. When executed by a processor, the computer instructions are used to implement the method as described in the first aspect and any possible implementation thereof.

[0026] Fifthly, a computer program product is provided that, when run on a computer or executed by a processor of the computer, implements the method described in the first aspect and any possible design thereof. The computer may be the resource access device described in the third aspect and any possible implementation thereof.

[0027] It is understood that the beneficial effects achieved by the resource connection device described in the second aspect, the resource connection equipment described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect can be referred to as the beneficial effects in the first aspect and any possible implementation thereof, and will not be repeated here. Attached Figure Description

[0028] Figure 1 This application provides a schematic diagram of a data processing architecture for a computing device. Figure 2 A flowchart illustrating a resource continuation method provided in an embodiment of this application; Figure 3 A flowchart illustrating another resource continuation method provided in an embodiment of this application; Figure 4 A flowchart illustrating yet another resource continuation method provided in an embodiment of this application; Figure 5 A flowchart illustrating yet another resource continuation method provided in an embodiment of this application; Figure 6 A flowchart illustrating yet another resource continuation method provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a resource connection device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a resource connection device provided in an embodiment of this application. Detailed Implementation

[0029] Hereinafter, 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. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0030] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0031] The technical solutions provided in this application, including the collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data, comply with relevant laws and regulations and do not violate public order and good morals.

[0032] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0033] Related resource continuation schemes generally adopt a "return resources first, then apply for resources" process, which requires the return of previously used resources before new resource quotas can be applied for. This scheme can lead to low resource utilization efficiency due to fragmented processes, complex operations, and resource gaps.

[0034] For example, in supply chain finance scenarios, if a requester is unable to repay its order financing on time, the existing scheme requires it to first raise bridge financing through external channels to repay the loan before it can apply for new financing using accounts receivable as collateral. This "repay first, then borrow" process not only increases additional funding costs, but more importantly, it exposes the company to the risk of a broken cash flow during the bridge financing period, directly affecting the continuity of production and operation.

[0035] For example, in cloud computing resource allocation scenarios, if a user's current resource quota is exhausted and they cannot complete the settlement immediately, they need to interrupt business operations and apply for a new resource quota only after completing the payment of previous fees. This interruption in resource supply directly leads to business service stagnation, causing problems such as a decline in user experience and data transmission interruptions.

[0036] Therefore, how to automate resource continuity has become a pressing technical problem that needs to be solved.

[0037] In view of this, this application provides a resource succession method, which generates a resource succession eligibility score through multi-dimensional information evaluation, realizes automated decision-making based on intelligent verification rules, directly generates succession resources based on agreed reward resources, and finally completes resource succession through automatic status update, effectively solving the problem of low efficiency in resource succession caused by process fragmentation.

[0038] The resource connection method provided in this application can be applied to computing devices. Specifically, the computing device can be a single server, a server cluster consisting of multiple servers, a computer, or a processor or processing chip in a server or computer. This application does not limit the specific device form of the computing device.

[0039] like Figure 1 The diagram shown is a schematic representation of a data processing architecture for a computing device according to an embodiment of this application. Specifically, it includes the following: The request reception and verification stage. This stage receives resource access requests submitted by the requester and verifies the requester's identity and the validity of the request information. Specifically, this includes verifying the legitimacy of the requester's identity, checking the standardization of the request data format, verifying the authenticity of the resource exchange contract, and confirming the validity of the agreed-upon reward resources. This stage ensures the integrity and reliability of the data entering subsequent processes.

[0040] The data analysis and scoring stage involves in-depth analysis of verified multi-dimensional information. Based on operational information, an operational status score is determined; based on resource exchange contract information, a contract stability score is determined; and based on trustworthiness information, a trustworthiness score is determined. Simultaneously, the computing device can also combine domain security factors and security assurance resource verification results to calculate an enhanced trust score. Finally, a weighted summation is used to generate the final resource continuation eligibility score.

[0041] If the resource continuation eligibility score is greater than the resource continuation eligibility threshold, then the verification decision-making stage will begin.

[0042] If the resource continuation eligibility score is less than or equal to the resource continuation eligibility threshold, execution will be stopped and the request will be returned to the requester.

[0043] Verification Decision-Making Phase. This phase, based on a pre-defined verification rule system, sequentially performs three levels of conditional judgments: First, it assesses operational efficiency indicators, including a comparison of resource return rate and turnover rate thresholds; second, it verifies contract stability, including compliance with exchange resource reception frequency and conflict event records; and finally, it checks credibility, including the compliance of historical default records and unreturned resource quotas. If all three verification results are passed, the verification result is determined to be successful, and the process proceeds to the resource processing and status update phase. If at least one of the three verification results is failed, the verification result is determined to be unsuccessful, triggering a manual review phase.

[0044] The manual review process serves as a supplement and safeguard to automated decision-making. When the verification result is unsatisfactory, a human review is conducted.

[0045] If the manual review result is satisfactory, the process will proceed to the resource processing and status update stage.

[0046] If the manual review result is unsatisfactory, the process will be stopped and the request will be returned to the requesting party.

[0047] The resource processing and status update process begins by sending a contract verification request to the core enterprise. Upon valid confirmation, the system determines the amount of resources to be returned based on pre-defined resource conversion rules and agreed-upon return resources. A resource transfer contract is then constructed and awaits confirmation from the requesting party. Upon receiving confirmation, the system automatically updates the status of the resources to be returned to "returned." In cases of insufficient resources, the system automatically sets the shortfall as new resources to be returned, ensuring the complete continuation of the resource relationship.

[0048] Please refer to the following text for details. Figure 2 The specific details of this resource continuation method are not elaborated here.

[0049] like Figure 2 As shown in the embodiment of this application, a resource continuation method, when applied to the aforementioned computing device, specifically includes the following: S101. Obtain the resource continuation request information for the requested policy regarding the return of resources.

[0050] The resource succession request information includes: the requester's operational information, the requester's resource exchange contract information, and the requester's credibility information. Furthermore, the resource exchange contract includes the agreed-upon return resources from the core enterprise to the requester.

[0051] The requesting party refers to the entity that uses the resources allocated by the computing equipment for production activities and is obligated to return the used resources. Resources to be returned refer to the resources that the requesting party is required to return to the computing equipment at a specific future time or under certain conditions, according to the agreement. The core enterprise refers to the entity that, after establishing the aforementioned resource exchange contract with the requesting party, consumes the resources produced by the requesting party using the used resources and is obligated to return the agreed-upon return resources to the requesting party.

[0052] The occupied resources may be equal to the resources to be returned, or they may not be equal to the resources to be returned.

[0053] In addition, in this application embodiment, "resource" generally refers to a finite entity within a computing device (or other external system or device) that can be allocated, scheduled, and used to complete a specific activity or achieve a specific task. Resources take different forms in different application scenarios.

[0054] To better understand the above terminology, the following are specific application scenario examples of embodiments of this application: For example, in a supply chain scenario, the requester can be a product requester within the supply chain, the resources produced by the requester can be supply chain products (such as electronic products, agricultural products, etc.), the resources occupied can be the production materials of the products (such as raw materials, production equipment, etc.), and the resources to be returned can be currency. Furthermore, the core enterprise can be the core enterprise of the supply chain, and the resource exchange contract can be a product order contract.

[0055] For example, in a cloud computing service scenario, the requester could be a software company that rents cloud computing power to train an AI model. The resources it produces using the occupied resources (GPU computing power provided by the cloud service provider) are the trained AI model. The resources to be returned are the equivalent amount of GPU computing power resources that need to be returned to the cloud service provider (achieved by releasing instances). The core enterprise is the user using the AI ​​model. The agreed return resources are the model licensing fees paid by the enterprise customer to the software company. The resource exchange contract is a combination of computing power leasing agreements and model licensing agreements signed by the software company with the cloud service provider and the enterprise customer, respectively.

[0056] In some embodiments, the requester's operational information includes: the requester's total revenue resources, the requester's resource yield rate, the requester's available resources, the requester's resource turnover rate, and the requester's own resource return rate; the requester's resource exchange contract information includes: the number of resource exchange contracts, the frequency of resource exchange contract creation, the frequency of resource exchange receipt by the requester, the duration of resource exchange contracts, and records of conflict events of resource exchange contracts; the requester's credibility information includes: the requester's historical default records, the requester's unreturned resources, the frequency of credibility queries by the requester, the requester's overdue resource return records, and the requester's records of regulatory issues.

[0057] Specifically, the requester's resource return rate refers to the ratio of net revenue resources to total revenue resources, used to measure the net profitability of resource input. This indicator excludes the impact of costs and purely reflects the value-added capability of resource transformation.

[0058] For example, if the total revenue resource is 100 units and the net revenue after deducting costs is 30 units, then the resource rate of return is 30%.

[0059] The resource turnover rate of the requester refers to the ratio of total revenue resources to the average total amount of resources occupied, reflecting the flow speed and utilization efficiency of the resource pool.

[0060] For example, if the total annual revenue is 5 million and the average annual resource usage is 1 million, then the resource turnover rate is 5 times / year, indicating that the resources can be recycled 5 times per year.

[0061] The conflict event log for resource exchange contracts refers to the cumulative number of disputes, breaches, or arbitrations that occur during contract performance. This metric directly reflects the stability of contract execution.

[0062] For example, if a requesting party has three contractual disputes within a year, then its conflict events are recorded as three.

[0063] The credit query frequency of a requester refers to the number of times their credit record has been accessed by external agencies within a recent period. Unusually frequent queries may indicate that their creditworthiness is under considerable scrutiny or that there are potential security issues.

[0064] For example, if your credit record is checked 10 times by different financial institutions within a month, it may be considered a security issue.

[0065] In some embodiments, the way a computing device obtains resource continuation request information from a requester depends primarily on the design of the interaction interface between the computing device and the requesting device. This can be categorized as active acquisition or passive acquisition.

[0066] One possible implementation is that the computing device passively obtains the resource continuation request information from the requester. That is, the requester sends the resource continuation request information to the computing device through its application programming interface or user portal.

[0067] For example, when the requester fills in and submits resource connection request information on the front-end interface of the computing device, this action will send a structured request message to the back-end server of the computing device, thereby triggering the entire connection process.

[0068] In another possible implementation, the computing device can proactively acquire resource continuation requests from requesters. That is, the computing device periodically scans the requester list and resource status database, automatically filtering out requesters whose resources are about to expire but have not yet been returned, generating resource continuation request information for them, and thus initiating the subsequent verification and continuation process.

[0069] In addition, when a computing device actively generates a request, it also needs to collect information on the requester's operations, contracts, and credibility from its internal database and external data sources (such as credibility regulatory agencies) in accordance with the data authorization agreement with the requester, in order to obtain complete resource continuation request information.

[0070] S102. Based on operational information, resource exchange contract information, and credibility information, determine the requester's resource succession eligibility score.

[0071] The resource succession eligibility score is a comprehensive score derived by quantifying operational information, resource exchange contract information, and credibility information, which can reflect the requester's ability to return resources.

[0072] Specifically, this step integrates multiple dimensions of qualitative and quantitative information that may influence each other into a single comparable score using a standardized algorithm, thereby providing a clear and consistent basis for subsequent automated verification decisions.

[0073] In some embodiments, the computing device may employ a numerical scoring map to determine the requester’s resource access eligibility score.

[0074] One possible implementation is that the computing device is pre-configured with a mapping table of numerical ranges and scores for various types of information (parameters). By matching the actual parameter values ​​of the requester with the mapping table, scores for each dimension are obtained, and finally aggregated into a final score according to preset rules.

[0075] For example, regarding resource yield, a pre-configured mapping table might stipulate: 1 point for yield below 5%, 3 points for 5% to 10%, and 5 points for above 10%. The computing device compares the requester's actual yield with the mapping table to obtain the corresponding score. This process is repeated for all parameters in operational information, contract information, and credibility information. Finally, the scores of all parameters are weighted and summed according to preset weights to determine the resource continuation eligibility score.

[0076] In another possible implementation of the above embodiments, the computing device maintains multiple lookup tables for different types of requesters. For example, different scoring mapping relationships are configured for newly established requesters and mature requesters to adapt to their different development stages and security risk characteristics. The computing device automatically selects the appropriate lookup table for scoring calculation based on the requester's attribute characteristics.

[0077] In other embodiments, the computing device may also calculate an operational status score based on operational information, a contract stability score based on resource exchange contract information, and a credibility score based on credibility information; then, the three basic scores are weighted and fused with possible credibility enhancement scores (such as security guarantee resources, domain security, etc.).

[0078] This embodiment can be referred to below. Figure 3 This will not be elaborated upon here.

[0079] S103. If the resource connection qualification score is greater than the qualification score threshold, determine the verification result of the resource connection request information based on the preset resource connection verification rules.

[0080] The eligibility score threshold is used for initial screening of resource upkeep requests. Only when a requester's resource upkeep eligibility score exceeds this threshold is it considered to have the basic qualifications to proceed to the subsequent detailed verification process.

[0081] For example, the qualification scoring threshold can take many forms. Taking a percentage system as an example, the qualification scoring threshold can be 85, 90, or 95, etc. This application embodiment does not limit the specific value of the qualification scoring threshold.

[0082] In some embodiments, if the computing device has a resource continuity eligibility score greater than or equal to a qualification score threshold, it may continue to determine the verification result of the resource continuity request information based on preset resource continuity verification rules. This application embodiment does not limit the boundary conditions between the resource continuity eligibility score and the qualification score threshold.

[0083] In some embodiments, the qualification scoring threshold can be set using a combination of static configuration and / or dynamic calculation.

[0084] Specifically, static configuration refers to fixed thresholds set manually based on business rules. Dynamic calculation, on the other hand, refers to the process by which the system automatically adjusts and optimizes thresholds using machine learning models based on the final fulfillment results of historical resource continuation requests.

[0085] In some embodiments, the preset resource continuity verification rules are constructed by the computing device in the following manner: The computing device first receives basic verification conditions set by business personnel, including initial thresholds for key indicators; then, the computing device performs machine learning analysis on the stored historical verification data and corresponding performance results to automatically identify key verification features and their effective threshold ranges; finally, the computing device integrates the manually set conditions with the rules generated by machine learning to form an executable set of verification rules and establishes a rule update mechanism to continuously optimize the rule parameters based on subsequent verification results.

[0086] For a detailed explanation of how to determine the verification results of resource connection request information based on preset resource connection verification rules, please refer to the following text. Figure 5 This will not be elaborated upon here.

[0087] S104. If the verification result is successful, determine the requester's successor resources based on the preset resource conversion rules and agreed return resources, and construct a resource successor contract.

[0088] Among them, the resource succession contract is used to stipulate that the succession resources will be returned as resources to be returned.

[0089] The pre-defined resource conversion rules are used to convert uncertain, non-immediate agreed-upon return resources into currently certain, immediate follow-up resource amounts. Specifically, the realization of the value of agreed-upon return resources typically involves time delays and uncertainties. Through the conversion rules, the computing device can calculate the current value of this portion of future rights in advance, forming follow-up resources that can be immediately used to repay existing debts.

[0090] In some embodiments, the role of a resource succession contract is not limited to stipulating that the succession resources will be returned as resources to be returned. It also includes: clarifying the rights and obligations of both parties during the succession period, stipulating the handling of breaches of contract, and establishing a dispute resolution mechanism to ensure the smooth progress of the resource succession process.

[0091] In some embodiments, a resource succession contract may include elements such as: the specific amount and form of the succession resources, the method and time limit for resource transfer, guarantee and credit enhancement measures, the conditions for the contract to take effect and terminate, and the methods for handling defaults by both parties.

[0092] In some embodiments, after constructing a resource continuation contract, the computing device can notify the requester via push notifications, emails, or in-app messages to ensure that the requester is aware of the contract content and completes the confirmation process in a timely manner.

[0093] In one possible implementation, the process of determining the requester's successor resources based on preset resource conversion rules and agreed-upon return resources is as follows: The computing device first determines the original value of the agreed-upon return resources (such as value assessment of the resources), expected recovery time, and other parameters, and then calls the preset resource conversion rules (such as present value calculation models) to perform resource conversion, and finally outputs a successor resource (quota) that has been verified by security and time conversion.

[0094] For example, assuming the original value of the agreed-upon return resources is 1 million units, the expected recovery time is 180 days, the value guarantee factor is set at 0.98, and the annualized benchmark conversion rate is 5%, the calculation device first converts the time parameter into annual units (180 / 365≈0.493 years), and then performs the calculation: Successionary resource quota = 1,000,000 × 0.98 / (1 + 0.05)^0.493 ≈ 971,500 units of resources. Through this calculation, the resources worth 1 million units in the next 180 days are converted into approximately 971,500 units of successionary resources in the present.

[0095] S105. In response to the requester's confirmation of the resource continuation contract, change the status of the resource to be returned to the returned status to complete the resource continuation.

[0096] One possible implementation involves the computing device marking the requester's existing record of resources to be returned as "returned" in the resource status database and generating a new record of resources to be returned for a future cycle to complete the succession process. In this approach, the succession resource is a virtual resource quota that does not involve the transfer of physical resources; the transfer of the succession resource and the update of the obligation are only confirmed through updates to the database status.

[0097] Another possible implementation involves the computing device sending a resource allocation instruction to the resource scheduler. This instruction results in the actual allocation of a corresponding amount of physical resources (such as compute instances or storage volumes) from the resource pool to the requester's name, while simultaneously updating the status of that physical resource (i.e., the successor resource) to "pending return." The requester then returns these newly allocated resources as the original pending return resources. Subsequently, the computing device changes the status of the requester's pending return resources to "returned."

[0098] In some embodiments, if the requester's continuation resources can fully cover the resources to be returned, the computing device can directly transfer all or part of the continuation resources (up to the amount sufficient to cover the resources to be returned) to the resource pool with returned resources to complete the return of the requester's resources to be returned (i.e., change the status of the resources to be returned to the returned status). Simultaneously, the computing device will use the amount of the continuation resources as the requester's new resources to be returned. That is, the computing device will transfer the requester's resource obligations in the first resource usage phase to their resource obligations in the second resource usage phase.

[0099] In other embodiments, when the resource difference between the successor resource and the resource to be returned is negative, the computing device determines the new resource to be returned to the requester based on the absolute value of the resource difference and the sum of the successor resources.

[0100] Specifically, when the follow-up resources are insufficient to fully cover the resources to be returned, the absolute value (20 units) of the difference (e.g., if the follow-up resources are 80 units and the resources to be returned are 100 units, then the difference is -20 units) represents the portion of the resources that the requesting party needs to agree upon in return that are insufficient to return the resources to be returned. In this case, the computing device needs to use the absolute value of this difference, along with the follow-up resources, as the resources to be returned in the second resource usage phase.

[0101] It should be understood that this solution determines the extent to which the resource to be returned is to be returned by comparing the resource difference between the continuing resource and the resource to be returned. When the continuing resource is insufficient, the uncovered part is automatically transferred to the continuing resource as a new resource to be returned, thus realizing the integrity management of resource continuity.

[0102] For example, suppose the requester provides 100 units of security resources when receiving the initial resource quota. When the follow-up resources fully cover the resources to be returned, the computing device will completely deassociate and release all 100 units of security resources. When the follow-up resources can only cover 50% of the resources to be returned, the computing device will deassociate 50% proportionally, releasing 50 units of security resources, with the remaining 50 units continuing to serve as collateral for newly established resources to be returned (i.e., the uncovered portion).

[0103] In some embodiments, the computing device may also construct a resource receiving listener for the agreed-upon reward resources of the requesting party, for responding to the agreed-upon reward resource return operation of the core enterprise. When the core enterprise returns the agreed-upon reward resources for the resource exchange contract, the receiving listener captures the agreed-upon reward resources and notifies the requesting party to return the resources in accordance with the resource continuation contract.

[0104] In some embodiments, when a requester requests original resources (i.e., the initial resource quota in the first resource usage phase) from a computing device, there may be a security resource. This security resource serves as collateral for fulfilling the resource return obligation and is associated with the initial resource quota. After the requester completes the continuation of the resources to be returned, the computing device may, based on the coverage of the continuation resources with the resources to be returned, proportionally decouple the security resource from the resource debt, i.e., partially or completely release the security resource.

[0105] The following is a detailed description of the step S102 above, which involves determining the eligibility score for resource continuation.

[0106] In some embodiments, the specific process of determining the requester's resource succession eligibility score based on operational information, resource exchange contract information, and trust information in step S102 is as follows: Figure 3 As shown, step S102 specifically includes the following steps: S201. Based on the requester's operational information, determine the requester's operational status score.

[0107] The operational status score is an assessment of the requester's production capacity and resource utilization efficiency based on the resource revenue status dimension.

[0108] In some embodiments, the computing device can calculate an operational status score by constructing an operational evaluation function. This function takes key operational indicators such as resource yield, resource turnover rate, and return on equity resources as input, and outputs a standardized score through a multi-parameter fusion algorithm.

[0109] For example, the operational evaluation function can be expressed as:

[0110] in, This indicates the basic score of the operational status. Indicates the total revenue resources of the requesting party. Indicates the requester's resource turnover rate, Indicates the resource rate of return of the requester. Indicates the requester's available resources, This represents the requester's rate of return on its own resources. These are the adjustment functions for the corresponding indicators.

[0111] Specifically, the aforementioned adjustment function is used to uniformly map operational indicators of different dimensions and ranges into adjustment amounts for operational status scores.

[0112] For example, the adjustment function used in this embodiment includes: Total revenue resource adjustment function: 0.1×(rp / 1000), where 0.1 represents the resource conversion coefficient, used to convert the standardized resource value into the adjustment level of the scoring system, and 1000 represents the benchmark resource unit, used as the benchmark value for standardizing the total revenue resources.

[0113] Resource turnover rate adjustment function: 5×log10(ra); resource rate of return adjustment function: 15×(re-0.08); available resources adjustment function: 0.05×(rc / 100); self-owned resource return rate adjustment function: 10×(rg-0.10).

[0114] The resource return rate adjustment function is 15×(re-0.08), where 15 is the return rate adjustment weight, which is used to amplify the difference between the return rate and the benchmark to an appropriate level of score adjustment, and 0.08 is the industry benchmark return rate, which serves as a reference benchmark for assessing whether the company's profitability meets the standard.

[0115] The available resources adjustment function is 0.05×(rc / 100), where 0.05 is the liquidity impact factor, used to quantify the contribution of available resources to operational health, and 100 is the liquidity benchmark value, serving as a threshold standard for measuring the company's short-term solvency and operational safety.

[0116] The function for adjusting the rate of return on equity is 10×(rg-0.10), where 10 is the rate of return adjustment coefficient, used to convert the difference between the rate of return on equity and the qualification line into the corresponding score adjustment range, and 0.10 is the qualification rate of return threshold, representing the minimum capital return standard required by investors.

[0117] As can be seen from the above examples, the specific function form can be configured according to business needs, such as using a linear proportional function, a piecewise function, or a relative ranking function based on industry benchmarks. This application embodiment does not limit the specific content of the challenge function.

[0118] For example, suppose a requester's total revenue resources are 1200 base units, the resource turnover rate is 8 times / year, the resource return rate is 10%, the disposable resources are 150 base units, and the return on equity resources is 15%. The calculation process is as follows: Total revenue resource adjustment = 0.1 × (1200 / 1000) = 0.12 points, resource turnover rate adjustment = 5 × log10(8) ≈ 5 × 0.903 = 4.515 points, resource return rate adjustment = 15 × (0.10 - 0.08) = 0.3 points, disposable resources adjustment = 0.05 × (150 / 100) = 0.075 points, and return on equity resources adjustment = 10 × (0.15 - 0.10) = 0.5 points. Total adjustment = 0.12 + 4.515 + 0.3 + 0.075 + 0.5 = 5.51 points. Final operational status score = base score 60 points + 5.51 points = 65.51 points (rounded to 66 points).

[0119] S202. Based on the requester's resource exchange contract information, determine the stability score of the requester's resource exchange contract.

[0120] The resource exchange contract stability score assesses the stability of resource exchange between the requesting party and the core enterprise based on the dimensions of contract continuity, timely performance, and cooperation quality.

[0121] For example, the contract stability evaluation function can be expressed as:

[0122] in, This indicates the basic score for the stability of the resource exchange contract. Indicates the number of resource exchange contracts, This indicates the frequency of resource exchange contract creation. This indicates the agreed-upon frequency for receiving reporting resources. Indicates the duration of the resource exchange contract and This indicates a record of conflict events related to resource exchange contracts. These are the adjustment functions for the corresponding indicators.

[0123] Specifically, the specific function and manifestation of the adjustment function can be found in S201 above. The actual parameter values ​​of the adjustment function depend on the actual application process, and this application does not impose specific restrictions on them.

[0124] For example, suppose a requester has 15 contracts, a contract creation frequency of 6 times / quarter, a contract resource receiving frequency of 24 times / month, a contract duration (cd) of 18 months, and 2 conflict events recorded. The calculation process is as follows: Contract quantity adjustment = 0.3 × 15 = 4.5 points, Contract creation frequency adjustment = 2 × log10(6) ≈ 2 × 0.778 = 1.556 points, Resource receiving frequency adjustment = 0.4 × 24 = 9.6 points, Contract duration adjustment = 0.5 × 18 = 9 points, Conflict event penalty = -8 × 2 = -16 points. Total adjustment = 4.5 + 1.556 + 9.6 + 9 - 16 = 8.656 points, and the final resource exchange contract stability score = base score 60 points + 8.656 points = 68.656 points (rounded to 69 points).

[0125] S203. Based on the requester's credibility information, determine the requester's credibility score.

[0126] Credibility scoring assesses the creditworthiness of the requester based on their historical performance.

[0127] In some embodiments, the computing device calculates the score by constructing a credibility assessment function. This function takes as input parameters historical default records, the ratio of unreturned resources, the frequency of credibility queries, overdue resource returns, and regulatory issue records.

[0128] For example, the credibility evaluation function can be expressed as:

[0129] in, Indicates the basic credibility score, Indicates the number of historical default records, Indicates the percentage of resources not returned. Indicates the frequency of credibility queries, Indicates the number of overdue records for returning resources. This indicates the number of times regulatory issues have been recorded. These are the adjustment functions for the corresponding indicators.

[0130] Specifically, the specific function and manifestation of the adjustment function can be found in S201 above. The actual parameter values ​​of the adjustment function depend on the actual application process, and this application does not impose specific restrictions on them.

[0131] For example, suppose a requester has one historical default record, a non-returned resource ratio of 0.15, a credibility query frequency of 8 times / month, two overdue resource returns, and one regulatory issue. The calculation process is as follows: Historical default penalty = 20 × 1 = 20 points, non-returned resource penalty = 30 × 0.15 = 4.5 points, credibility query penalty = 2 × 8 = 16 points, overdue resource returns penalty = 10 × 2 = 20 points, regulatory issue penalty = 25 × 1 = 25 points. Total penalty = 20 + 4.5 + 16 + 20 + 25 = 85.5 points, final credibility score = base score 100 points - 85.5 points = 14.5 points (rounded to 15 points).

[0132] S204. Based on the operational status score, credibility score, and resource exchange contract stability score, determine the requester's resource succession eligibility score.

[0133] For example, the computing device can determine the requester's resource access eligibility score according to the following formula:

[0134] in, This indicates the score for eligibility to continue receiving resources. Indicates operational status score, This indicates the preset weights for the operational status score. Indicates the stability score of the resource exchange contract. This represents the preset weight for the stability score of the resource exchange contract. Indicates credibility score, This indicates the preset weight for the credibility score.

[0135] For example, as shown in examples S201-S203, suppose a requester has an operational status score of 66, a resource exchange contract stability score of 69, and a credibility score of 15. The weights for each dimension are set as follows: operational status weight 0.5, contract stability weight 0.3, and credibility weight 0.2. The calculation process is as follows: Operational status weighted score = 0.5 × 66 = 33 points, contract stability weighted score = 0.3 × 69 = 20.7 points, and credibility weighted score = 0.2 × 15 = 3 points. The final resource continuity eligibility score = 33 + 20.7 + 3 = 56.7 points (rounded to 57 points).

[0136] It should be understood that by introducing domain security assessment and security assurance resource verification, this solution can additionally consider domain security characteristics and assurance factors in the resource continuity eligibility assessment, thereby effectively identifying and filtering unreliable resource continuity requests in advance.

[0137] In some embodiments, in S204, in addition to the scoring of the three dimensions mentioned above, the computing device may also consider the impact of the systemic security level of the requester's domain and the guarantee resources provided for this continuation on the eligibility for resource continuation. This process is as follows: Figure 4 As shown, S204 specifically includes the following steps: S301. Based on the preset security score of the requester's domain and the existence of security resources in the resource continuation request information, determine the requester's credit enhancement score.

[0138] Among them, security resources are used to provide performance guarantees for resource continuity.

[0139] The pre-defined security score for the requester's domain refers to a quantitative score obtained by computing devices through analysis of macro-level data such as the domain's development potential, technological iteration risks, and resource return fluctuations. Introducing a domain security score allows for the identification of inherent security characteristics across different domains at a macro level. Furthermore, verifying security resources enables an assessment of the requester's resource mitigation capabilities in fulfilling their resource requests at a micro level. Combining these two approaches constructs a multi-dimensional credit enhancement assessment system covering both macro and micro-level transaction security, significantly improving the accuracy of the overall judgment on the requester's ability to fulfill their obligations.

[0140] In some embodiments, the preset security score of the requester's domain can be directly obtained from a pre-configured domain risk knowledge base in the computing device. This knowledge base pre-stores benchmark security scores for multiple different domains. When the computing device receives the resource continuation request from the current requester, it can query and match the corresponding preset security score from the knowledge base based on the domain identifier of the requester, thereby quickly completing the assessment for this dimension.

[0141] Specifically, the preset security rating can take various forms, including: a percentage score ranging from 0 to 100; a rating system based on the letter sequence A / B / C / D / E; a risk band division using 1-5 stars; a probability value mapped to the 0.0-1.0 range; a red / yellow / green three-color visual coding system; and a Z-score standard scoring system conforming to a normal distribution. Higher scores indicate higher security and stability in that area.

[0142] For example, the preset safety score for traditional manufacturing industries may be 80 points, while the score for emerging technology industries may be 60 points. The specific form and value of the preset safety score in this application embodiment are not limited.

[0143] In some embodiments, the computing device calculates the score by constructing a confidence-enhancing evaluation function.

[0144] For example, the confidence enhancement assessment function can be expressed as:

[0145] in, Indicates the basic credit enhancement score. This indicates the default security score for the domain to which the requester belongs. This represents the quantified value of security resources. These are the adjustment coefficients for the corresponding indicators.

[0146] For example, suppose a requester's domain has a preset security score of 0.85 (range 0-1), and the quantified value of its provided security resources is 500 base units. Set the base credit enhancement score to 70 points, with an adjustment factor of 20 (0.02). The calculation process is as follows: Domain security adjustment = 20 × 0.85 = 17 points, Security resource adjustment = 0.02 × 500 = 10 points. The final credit enhancement score = 70 + 17 + 10 = 97 points.

[0147] S302. The operational status score, credibility score, resource exchange contract stability score, and credit enhancement score are weighted and summed to determine the requester's resource succession eligibility score.

[0148] For example, the process by which a computing device performs a weighted summation of operational status scores, trust scores, resource exchange contract stability scores, and credit enhancement scores to determine the requester's resource succession eligibility score can be represented as follows:

[0149] in, This indicates the score for eligibility to continue receiving resources. Indicates operational status score, express The weight, Indicates credibility score, express The weight, Indicates the stability score of the resource exchange contract. express The weight, Indicates credit enhancement score, express The weight, , , as well as The sum of is 1.

[0150] For example, suppose a requester has an operational status score of 66, a credibility score of 15, a resource exchange contract stability score of 69, and a credit enhancement score of 97. We set weights α=0.4, β=0.3, γ=0.2, and δ=0.1. The calculation process is as follows: Weighted total score = 0.4×66 + 0.3×15 + 0.2×69 + 0.1×97 = 26.4 + 4.5 + 13.8 + 9.7 = 54.4 points. The final resource continuity eligibility score is determined to be 54 points.

[0151] For example, suppose a requester has an operational status score of 66, a credibility score of 15, a resource exchange contract stability score of 69, and a credit enhancement score of 97. We set weights α=0.4, β=0.3, γ=0.2, and δ=0.1. The calculation process is as follows: Weighted total score = 0.4×66 + 0.3×15 + 0.2×69 + 0.1×97 = 26.4 + 4.5 + 13.8 + 9.7 = 54.4 points. The final resource continuity eligibility score is determined to be 54 points.

[0152] In some embodiments, in S103, the computing device can determine the verification result by executing multi-level parallel verification rules, as detailed in the following process: Figure 5 As shown, S103 specifically includes the following steps: S401. If the resource yield rate is greater than the yield rate threshold and the resource turnover rate is greater than the turnover rate threshold in the requester's operational information, the first verification result is determined to be passed.

[0153] Among them, the resource return rate is the core indicator for measuring the requester's resource conversion capability. By setting the resource return rate to be greater than the return rate threshold, it is ensured that the requester has the basic ability to effectively convert the invested resources into revenue. The resource turnover rate reflects the speed of resource circulation and demonstrates the efficiency of the requester in recycling the occupied resources.

[0154] Specifically, the resource return rate threshold can be understood as the benchmark return rate level of the requester's field, and the turnover rate threshold refers to the minimum turnover standard required to maintain normal operation.

[0155] In some embodiments, S401 can also be implemented as follows: if the resource yield rate is greater than or equal to the yield rate threshold and the resource turnover rate is greater than or equal to the turnover rate threshold in the requester's operational information, the first verification result is determined to be passed. This application embodiment does not impose specific limitations on the boundary value judgment logic.

[0156] In some embodiments, in addition to judging the resource yield rate and resource turnover rate in the requester's operational information, the computing device can also verify the available resources, return on owned resources, and total revenue resource growth rate in the requester's operational information. Furthermore, if the verification results for multiple indicators are all passed, the first verification result is determined to be passed.

[0157] One possible implementation involves verifying the available resources, rate of return on owned resources, and growth rate of total revenue resources in the requester's operational information using the following specific rules: available resources must be greater than the resource quota threshold, the rate of return on owned resources must be greater than the rate of return threshold, and the growth rate of total revenue resources must be greater than the growth rate threshold.

[0158] It should be understood that this approach, by expanding the scope of review of operational metrics, establishes a more comprehensive assessment system for the operational health of the requester, thereby improving the completeness and accuracy of verification decisions.

[0159] In some embodiments, the various thresholds used for verification in the computing device are dynamically adjusted based on historical business data through a machine learning model to ensure that the threshold settings are kept in sync with the current domain development environment and business development needs.

[0160] For example, the yield threshold can be 8%, 10%, or 12%, and the turnover threshold can be 1.5, 2.0, or 2.5. This application does not limit the specific values ​​of the yield threshold, turnover threshold, or other resource allocation thresholds, return on investment thresholds, and growth rate thresholds.

[0161] S402. If the requester's resource exchange contract information stipulates that the frequency of receiving returned resources is greater than the frequency threshold and the number of conflict event records is less than the quantity threshold, the second verification result is determined to be passed.

[0162] The frequency of receiving agreed-upon reward resources is an indicator of the smoothness of resource flow between the requester and the core enterprise. By setting a receiving frequency greater than a threshold, the stability of the requester's receipt of agreed-upon reward resources is ensured. The number of conflict event records reflects the smoothness of contract performance and demonstrates the quality of cooperation of the requester in executing the resource exchange contract.

[0163] Specifically, the frequency threshold can be understood as the minimum reception frequency required to ensure the smooth operation of the resource connection process, while the quantity threshold refers to the maximum number of conflict events allowed to maintain a good contractual relationship.

[0164] In some embodiments, S402 can also be implemented as follows: if the resource exchange contract information of the requesting party stipulates that the frequency of receiving returned resources is greater than or equal to a frequency threshold and the number of conflict event records is less than or equal to a quantity threshold, then the second verification result is determined to be passed. This application embodiment does not impose specific limitations on the boundary value judgment logic.

[0165] In some embodiments, in addition to judging the frequency of receiving reward resources and the number of conflict event records agreed upon in the resource exchange contract information of the requester, the computing device can also verify the contract duration, number of contracts, and contract creation frequency in the resource exchange contract information of the requester. Furthermore, if the verification results of multiple indicators are all passed, the second verification result is determined to be passed.

[0166] One possible implementation involves verifying the contract duration, number of contracts, and contract creation frequency in the resource exchange contract information of the requester using the following specific rules: contract duration greater than the duration threshold, number of contracts greater than the number threshold, and contract creation frequency greater than the creation frequency threshold.

[0167] It should be understood that this approach, by expanding the scope of contract metrics review, establishes a more comprehensive assessment system for the stability of the requesting party's contract, thereby improving the completeness and accuracy of verification decisions.

[0168] For example, the frequency threshold can be 24 times / month, 36 times / month, or 48 times / month, and the quantity threshold can be 1 time, 2 times, or 3 times. This application does not limit the specific values ​​of the frequency threshold, quantity threshold, or more duration thresholds, quantity thresholds, or the creation frequency threshold.

[0169] S403. If the historical default records in the requester's credibility information are less than the default count threshold and the quota of unreturned resources is less than the quota threshold, the third verification result is determined to be passed.

[0170] Among them, historical default records are an indicator to measure the requester's historical performance. By setting a threshold for the number of historical default records to be less than the number of defaults, the basic credit reliability of the requester is ensured. The quota of unreturned resources reflects its current resource burden level and demonstrates the requester's capacity to take on new resources.

[0171] Specifically, the default threshold can be understood as the maximum allowed number of historical defaults, while the quota threshold refers to the highest proportion of unreturned resources in the total resource quota.

[0172] In some embodiments, S403 can also be implemented as follows: if the historical default records in the requester's credibility information are less than or equal to the default count threshold and the quota of unreturned resources is less than or equal to the quota threshold, the third verification result is determined to be passed. This application embodiment does not impose specific limitations on the boundary value judgment logic.

[0173] In some embodiments, in addition to judging the historical default records and unreturned resource quotas in the requester's credibility information, the computing device can also verify the credibility query frequency, overdue resource return records, and regulatory issue records in the requester's credibility information. Furthermore, if the verification results for multiple indicators are all passed, the third verification result is determined to be passed.

[0174] One possible implementation involves verifying the credibility query frequency, overdue resource return records, and regulatory issue records in the requester's credibility information using the following specific rules: the credibility query frequency is less than the query frequency threshold, the overdue resource return records are less than the overdue number threshold, and the regulatory issue records are less than the regulatory issue threshold.

[0175] It should be understood that this approach establishes a more comprehensive production credibility assessment system by expanding the scope of credibility index review, thereby improving the completeness and accuracy of verification decisions.

[0176] For example, the specific values ​​of the default frequency threshold can be 0 times, 1 time, and 2 times, and the specific values ​​of the quota threshold can be 15%, 20%, and 25%. This application embodiment does not limit the specific values ​​of the default frequency threshold, quota threshold, or more query frequency thresholds, overdue frequency thresholds, and regulatory issue thresholds.

[0177] S404. If the first verification result, the second verification result, and the third verification result are all passed, the verification result of the resource continuation request information is determined to be passed.

[0178] The first verification result (operational status), the second verification result (contract stability), and the third verification result (credibility) independently assessed the requester's eligibility for succession from different dimensions. Operational status reflects its ability to continue operating and utilize resources; contract stability reflects its external cooperation and performance reliability; and credibility characterizes its historical credibility performance. These three dimensions constitute a complete system for assessing the requester's eligibility for succession; the absence of any dimension will create an assessment blind spot. Only requesters who simultaneously meet the requirements of all dimensions are considered to have complete eligibility for resource succession.

[0179] In some embodiments, when any verification result fails, the computing device will also trigger a manual review process. Specifically, the computing device will automatically push relevant information about the failed verification result (including the specific indicators that did not meet the standards, the difference between the actual value and the threshold, etc.) to the manual verification terminal, whereby the verification personnel will make the final decision on the exception, thereby balancing the efficiency of automated verification with the flexibility of handling complex cases.

[0180] It should be understood that this solution, by establishing structured, multi-level verification rules, clearly refines the verification conditions for resource continuity into quantitative indicators across three dimensions: operational efficiency, contract stability, and credibility. This rule-based verification mechanism not only achieves uniformity and transparency in verification standards but also ensures flexibility and adaptability through configurable threshold parameters. This design allows verification decisions to be based entirely on objective data indicators, effectively reducing the interference of subjective judgment, while also providing traceable decision-making evidence, significantly improving the efficiency and reliability of the verification process.

[0181] In some embodiments, the computing device in S104 may also introduce a core enterprise verification mechanism to improve the reliability and security of the resource connection process, the specific process of which is as follows: Figure 6 As shown, S104 specifically includes the following steps: S501. If the verification result is successful, send a verification request for the resource exchange contract of the requester to the core enterprise's server.

[0182] Specifically, the computing device uses the identification identifier of the core enterprise recorded in the resource exchange contract to look up the corresponding network address in the pre-configured service routing table, thereby identifying and locating the server of the target core enterprise.

[0183] In some embodiments, a verification request may include the following information: the resource exchange contract number, the requester's identification identifier, details of the agreed-upon reward resource to be verified, and the timestamp and digital signature of this verification request.

[0184] One possible implementation involves sending a verification request for the resource exchange contract to the core enterprise's server. The specific process includes: the computing device first constructs a standardized verification request data packet based on the content of the resource exchange contract. This data packet follows a predefined interface protocol and contains an encrypted request payload. Then, the request is sent to the authentication interface of the core enterprise's server through a secure communication channel. Simultaneously, a timer is started and the response port is listened to. If no valid response is received within the timeout threshold, a retransmission mechanism or a degradation process is automatically triggered.

[0185] S502. If the core enterprise's server returns a valid verification result, the requester's successor resources are determined based on the preset resource conversion rules and agreed-upon reward resources, and a resource successor contract is constructed.

[0186] Specifically, after receiving a valid confirmation message containing a digital signature from the core enterprise server, the computing device parses and verifies the integrity and authenticity of the response. Then, it invokes a pre-defined resource conversion engine, takes the verified agreed-upon reward resources as input, executes the resource conversion rules, and outputs the subsequent resource quota.

[0187] In some embodiments, if the core enterprise's server returns an invalid verification result, or fails to return the verification result within a preset time, the computing device will automatically suspend the subsequent resource connection process. In this case, the computing device will send a notification to the requesting party, informing it that the connection process was interrupted due to the failure of the resource exchange contract verification. Simultaneously, the computing device will mark the resource connection request as pending and record the detailed reason for the verification failure, so that the requesting party can decide whether to re-initiate the request.

[0188] It should be understood that this solution, by introducing a verification interaction mechanism with the core enterprise's server, confirms the validity of the underlying contract before determining the resources to be transferred. This verification step effectively ensures the authenticity and validity of the resource exchange contract that forms the basis for the transfer, and identifies resource transfer operations based on invalid or abnormal contracts in advance. Furthermore, the design of making the core enterprise's confirmation a prerequisite not only ensures the compliance of the transfer process but also enhances the reliability of the overall process through a multi-party verification mechanism.

[0189] like Figure 7 This is a schematic diagram of a resource connection device provided in an embodiment of this application. Figure 7 As shown, the resource connection device includes: an acquisition module 701 and a processing module 702.

[0190] Module 701 is used to acquire resource continuation request information from the requesting entity regarding the return of resources. This resource continuation request information includes: the requester's operational information, the requester's resource exchange contract information, and the requester's credibility information. The resource exchange contract includes the agreed-upon return resources from the core enterprise to the requester.

[0191] Processing module 702 is used to determine the requester's resource continuation eligibility score based on operational information, resource exchange contract information, and credibility information. If the eligibility score exceeds a threshold, the module determines the verification result of the resource continuation request information based on preset resource continuation verification rules. If the verification result is successful, the module determines the requester's continuation resources based on preset resource conversion rules and agreed-upon return resources, and constructs a resource continuation contract. The resource continuation contract stipulates that the continuation resources will be returned as resources to be returned. In response to the requester's confirmation of the resource continuation contract, the status of the resources to be returned is changed to a returned status to complete the resource continuation.

[0192] In other embodiments, the requester's operational information includes: the requester's total revenue resources, the requester's resource yield rate, the requester's available resources, the requester's resource turnover rate, and the requester's own resource return rate; the requester's resource exchange contract information includes: the number of resource exchange contracts, the frequency of resource exchange contract creation, the frequency of resource exchange receiving, the duration of resource exchange contracts, and records of conflict events related to resource exchange contracts; the requester's credibility information includes: the requester's historical default records, the requester's unreturned resources, the frequency of credibility queries, the requester's overdue resource return records, and records of regulatory issues related to the requester.

[0193] In other embodiments, the processing module 702 is specifically used to determine the requester's operational status score based on the requester's operational information; determine the requester's resource exchange contract stability score based on the requester's resource exchange contract information; determine the requester's credibility score based on the requester's credibility information; and determine the requester's resource continuity eligibility score based on the operational status score, credibility score, and resource exchange contract stability score.

[0194] In other embodiments, the processing module 702 is specifically used to determine the requester's credit enhancement score based on a preset security score of the requester's domain and the existence result of security guarantee resources in the resource continuation request information; the security guarantee resources are used to provide performance guarantee for resource continuation; and the operation status score, credibility score, resource exchange contract stability score and credit enhancement score are weighted and summed to determine the requester's resource continuation qualification score.

[0195] In other embodiments, the processing module 702 is specifically configured to determine the requester's resource access eligibility score according to the following formula: ; in, Indicates the score for eligibility to continue receiving resources; Indicates operational status score, express The weights; Indicates credibility score, express The weights; Indicates the stability score of the resource exchange contract. express The weights; Indicates credit enhancement score, express The weights; , , as well as The sum of is 1.

[0196] In other embodiments, the processing module 702 is specifically configured to: determine a first verification result as passed if the resource yield rate is greater than the yield rate threshold and the resource turnover rate is greater than the turnover rate threshold in the requester's operational information; determine a second verification result as passed if the exchange resource receiving frequency is greater than the frequency threshold and the number of conflict event records is less than the quantity threshold in the requester's resource exchange contract information; determine a third verification result as passed if the historical default records are less than the default count threshold and the quota of unreturned resources is less than the quota threshold in the requester's credibility information; and determine the verification result of the resource continuation request information as passed if the first verification result, the second verification result, and the third verification result are all passed.

[0197] In other embodiments, the processing module 702 is specifically used to send a verification request for the resource exchange contract for the requester to the server of the core enterprise if the verification result is passed; if the server of the core enterprise returns a valid verification result, the processing module 702 determines the successor resources for the requester based on the preset resource conversion rules and the agreed return resources, and constructs a resource successor contract.

[0198] In other embodiments, the processing module 702 is further configured to determine the new resource to be returned to the requester based on the absolute value of the resource difference and the sum of the resources to be returned, when the resource difference between the successor resource and the resource to be returned is negative.

[0199] The resource connection device provided in this application embodiment can execute the method shown in the above method embodiment. Its implementation principle and beneficial effects can be referred to the relevant description in the method embodiment, and will not be repeated here.

[0200] Figure 8 This is a schematic diagram of the structure of a resource connection device provided in an embodiment of this application. Figure 8 As shown, the resource connection device includes: a memory 801, a transceiver 802, and at least one processor 803.

[0201] The transceiver 802 is used to interact with other devices to send and receive data.

[0202] For example, in this embodiment of the application, transceiver 802 can be used to obtain resource continuation request information of the requesting policy for the return of resources.

[0203] The memory 801 is used to store computer program code, which includes computer instructions. These computer instructions run in the aforementioned resource access device to implement the method shown in the above-described method embodiments. For example, the memory may include high-speed random access memory (RAM), and may also include non-volatile memory (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk, or optical disc, etc.

[0204] Processor 803 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. Processor 803 can also be other general-purpose processors. A general-purpose processor can be a microprocessor or any conventional processor.

[0205] The memory 801, transceiver 802, and processor 803 are communicatively connected. For example, the memory 801 and transceiver 802 can be connected to the processor 803 via a system bus and communicate with each other. The system bus can be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, an industry standard architecture (ISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0206] Optionally, the memory 801 can be either standalone or integrated with the processor 803. When the memory 801 is set up independently, it is connected to the processor 803 via the system bus.

[0207] This application also provides a chip for executing instructions, which is used to execute the resource continuation method described in the above embodiments.

[0208] This application also provides a computer-readable storage medium storing computer instructions. When these computer instructions are executed by a processor, they are used to implement the technical solution of the resource continuation method described in the above embodiments. Specifically, when the computer instructions are executed by a processor, the resource continuation device can execute the technical solution of the resource continuation method described in the above embodiments.

[0209] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the resource continuation method in the above embodiments.

[0210] The aforementioned computer-readable storage media can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as static random-access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The computer-readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0211] An exemplary computer-readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the computer-readable storage medium can also be a component of the processor. The processor and the computer-readable storage medium can reside in application-specific integrated circuits (ASICs). Alternatively, the processor and the computer-readable storage medium can exist as discrete components in an electronic control unit or main control device; this application does not limit this.

[0212] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0213] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0214] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0215] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0216] It should be understood that the steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

[0217] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0218] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A resource continuation method, characterized in that, include: Obtain the resource continuation request information for the requested policy regarding the return of resources; The resource succession request information includes: the requester's operational information, the requester's resource exchange contract information, and the requester's credibility information; the resource exchange contract includes the agreed-upon return resources that the core enterprise needs to return to the requester; Based on the operational information, resource exchange contract information, and credibility information, the resource succession eligibility score of the requester is determined; If the resource continuity eligibility score is greater than the eligibility score threshold, the verification result of the resource continuity request information is determined based on the preset resource continuity verification rules. If the verification result is successful, based on the preset resource conversion rules and the agreed return resources, the requester's follow-up resources are determined, and a resource follow-up contract is constructed; the resource follow-up contract is used to agree to return the follow-up resources as the resources to be returned. In response to the requester's confirmation of the resource continuation contract, the status of the resource to be returned is changed to the returned status to complete the resource continuation.

2. The method according to claim 1, characterized in that, include: The requester's operational information includes: the requester's total revenue resources, the requester's resource yield rate, the requester's available resources, the requester's resource turnover rate, and the requester's own resource return rate. The resource exchange contract information of the requesting party includes: the number of resource exchange contracts, the creation frequency of the resource exchange contracts, the frequency of the requesting party receiving exchanged resources, the duration of the resource exchange contracts, and the conflict event records of the resource exchange contracts. The credibility information of the requester includes: the requester's historical default records, the requester's unreturned resources, the frequency of credibility queries for the requester, the requester's overdue resource return records, and the requester's regulatory issue records.

3. The method according to claim 1 or 2, characterized in that, The determination of the requester's resource access eligibility score based on the operational information, resource exchange contract information, and credibility information includes: Based on the requester's operational information, determine the requester's operational status score; Based on the resource exchange contract information of the requesting party, determine the stability score of the resource exchange contract of the requesting party; Based on the credibility information of the requester, a credibility score for the requester is determined; Based on the operational status score, the credibility score, and the resource exchange contract stability score, the requester's resource succession eligibility score is determined.

4. The method according to claim 3, characterized in that, The determination of the requester's resource succession eligibility score based on the operational status score, the credibility score, and the resource exchange contract stability score includes: Based on the preset security score of the requester's domain and the existence result of security guarantee resources in the resource continuation request information, the credit enhancement score of the requester is determined; the security guarantee resources are used to provide performance guarantee for the resource continuation; The resource succession eligibility score of the requester is determined by weighted summation of the operational status score, the credibility score, the resource exchange contract stability score, and the credit enhancement score.

5. The method according to claim 4, characterized in that, The resource succession eligibility score of the requester is determined by weighted summation of the operational status score, the credibility score, the resource exchange contract stability score, and the credit enhancement score, including: The resource continuation eligibility score of the requester is determined according to the following formula: ； in, Indicates the score for eligibility to continue receiving resources; Indicates the operational status score, express The weights; Indicates the credibility score, express The weights; This indicates the stability score of the resource exchange contract. express The weights; The credit enhancement score indicates that... express The weights; , , as well as The sum of is 1.

6. The method according to claim 2, characterized in that, The step of determining the verification result of the resource connection request information based on preset resource connection verification rules includes: If the resource return rate is greater than the return rate threshold and the resource turnover rate is greater than the turnover rate threshold in the requester's operational information, the first verification result is determined to be passed. If the resource exchange contract information of the requesting party shows that the frequency of receiving exchanged resources is greater than the frequency threshold and the number of conflict event records is less than the quantity threshold, the second verification result is determined to be passed. If the historical default records in the requester's credibility information are less than the default count threshold and the quota of unreturned resources is less than the quota threshold, the third verification result is determined to be passed. If the first verification result, the second verification result, and the third verification result are all passed, the verification result of the resource continuation request information is determined to be passed.

7. The method according to claim 1, characterized in that, If the verification result is successful, the process involves determining the requester's successor resources based on preset resource conversion rules and the agreed-upon reward resources, and constructing a resource succession contract, including: If the verification result is successful, a verification request for the resource exchange contract of the requesting party is sent to the server of the core enterprise. If the core enterprise's server returns a valid verification result, the requester's successor resources are determined based on the preset resource conversion rules and the agreed-upon reward resources, and a resource successor contract is constructed.

8. The method according to claim 1, characterized in that, The method further includes: If the difference between the continuing resource and the resource to be returned is negative, the new resource to be returned to the requester is determined based on the sum of the absolute value of the resource difference and the continuing resource.

9. A resource connection device, characterized in that, include: The acquisition module is used to acquire resource continuation request information for the requested policy regarding the return of resources; The resource continuation request information includes: the requester's operational information, the requester's resource exchange contract information, and the requester's credibility information; the resource exchange contract includes the agreed-upon return resources from the core enterprise to the requester; The processing module is used to determine the requester's resource continuation eligibility score based on the operational information, resource exchange contract information, and credibility information; if the resource continuation eligibility score is greater than the eligibility score threshold, determine the verification result of the resource continuation request information based on preset resource continuation verification rules; if the verification result is passed, determine the requester's continuation resources based on preset resource conversion rules and the agreed return resources, and construct a resource continuation contract; the resource continuation contract is used to agree to return the continuation resources as the resources to be returned; in response to the requester's confirmation of the resource continuation contract, change the status of the resources to be returned to the returned status to complete the resource continuation.

10. A resource connection device, characterized in that, include: A memory and at least one processor; the memory is communicatively connected to the processor; the memory is used to store computer program code, the computer program code including computer instructions; when the processor executes the computer instructions, the resource connection device performs the method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

12. A computer program product, characterized in that, When the computer program product is run on a computer / executed by the computer's processor, it implements the method as described in any one of claims 1-8.

Images