Task execution method and device, equipment and storage medium

Abstract

The invention provides a task execution method and device, equipment and a storage medium, relates to the field of big data processing, and is used for improving the accuracy of a resource return value, and the specific scheme is as follows: determining a target update plan in a plurality of update plans of a parameter update plan table according to a target update date, when the target update date is consistent with the planned effective date and the update control identifier is the preset first identifier, reading the previous reference update date and taking the previous reference update date as the target effective date of the current parameter reference quantity, and determining the target value of the parameter reference quantity based on the target effective date, so that the accuracy of the value of the parameter reference quantity is ensured; and finally, a second resource use cost parameter is calculated according to the target value and the offset, and a resource return value is determined based on the second resource use cost parameter, so that a resource use cost parameter updating error possibly introduced by directly adopting latest parameter reference data is avoided, and the accuracy of the resource return value is improved while the flexible adjustment requirement is met.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of big data processing, and in particular to a task execution method and device, equipment and a storage medium. BACKGROUND

[0002] Resource processing related businesses include resource allocation, resource use, resource return and resource recycling, etc. Among them, the resource return business refers to the process of returning the occupied resources to the resource provider by the user according to the agreement. The size of the resource return value is related to the resource use cost parameter. The size of the resource use cost parameter is not fixed, but needs to be dynamically adjusted to ensure the accuracy of the calculated resource return value.

[0003] In the prior art, the resource use cost parameter is updated according to a fixed period using a preset fixed rule, which is likely to result in a parameter update result that does not match the actual situation, produce data deviation, affect the accuracy of the resource return value, and affect the normal development of the resource return business. SUMMARY

[0004] Embodiments of the present application provide a task execution method, device, equipment and storage medium for improving the accuracy of the resource return value and ensuring the normal development of the resource return business.

[0005] To achieve the above-mentioned purpose, embodiments of the present application adopt the following technical solutions: In a first aspect, a task execution method is provided, which comprises: Based on the first resource use cost parameter, a resource return value determination task corresponding to a target resource account is executed; A parameter update plan table corresponding to the target resource account is obtained; wherein the parameter update plan table includes at least one update plan for the first resource use cost parameter; the update plan is used to update the value of the first resource use cost parameter, and each update plan corresponds to a planned effective date, an update control identifier, a parameter reference quantity and a parameter offset quantity; According to the target update date, a target update plan is determined from the at least one update plan; If the target update date is consistent with the planned effective date corresponding to the target update plan, and the update control identifier corresponding to the target update plan is a preset first identifier, a previous reference update date is read from a parameter update record table corresponding to the target resource account, and the previous reference update date is determined as the target effective date of the parameter reference quantity used for this time parameter update; the previous reference update date is the most recent update date of the parameter reference quantity; Based on the target effective date, the target value of the parameter reference quantity is determined; According to the target value and the offset, a second resource use cost parameter corresponding to the target resource account is determined, and a resource return value determination task corresponding to the target resource account is executed based on the second resource use cost parameter; the resource return value is used to execute a resource return business corresponding to the target resource account.

[0006] The embodiment of the application provides a clear plan basis for parameter updating by obtaining the parameter update plan table of the target resource account, and then determines the target update plan in the multiple update plans according to the target update date, to ensure that the update is performed under the predetermined plan; when the target update date is consistent with the plan effective date and the update control identifier is a preset first identifier, the previous reference update date is read and used as the target effective date of the parameter reference quantity of this time, to realize the backtracking positioning of the parameter reference quantity value, so that it does not incorrectly rely on the current latest data; the target value of the parameter reference quantity is determined based on the target effective date, to ensure the accuracy of the parameter reference quantity value; finally, the second resource use cost parameter is calculated according to the target value and the offset, and the resource return value is calculated based on this, to complete the dynamic updating of the parameter and avoid the updating error of the resource use cost parameter that may be introduced by directly using the latest parameter reference data, thereby meeting the flexible adjustment requirement and improving the accuracy of the resource return value calculation, to ensure the normal development of the resource return business.

[0007] In a possible implementation manner of the first aspect, based on the target effective date, the target value of the parameter reference quantity is determined, including: obtaining a first information table; the first information table includes multiple values of the parameter reference quantity, each value corresponds to an effective date interval, and the effective date interval is composed of an effective start date and an effective end date; querying the first information table by taking the target effective date as a query condition; determining, as the target value of the parameter reference quantity, a value whose effective start date is less than or equal to the target effective date and whose effective end date is greater than or equal to the target effective date.

[0008] Based on the above technical content, the embodiment provides data support for the determination of the reference quantity by obtaining the first information table recording the multiple values of the parameter reference quantity and the corresponding effective date intervals; then, the target effective date is taken as a query condition to find the value whose effective start date is less than or equal to the target effective date and whose effective end date is greater than or equal to the target effective date, to accurately lock the effective reference quantity version matched with the preset effective date, thereby avoiding the data deviation caused by the incorrect selection of the reference quantity version and improving the accuracy of the parameter reference quantity value.

[0009] In a possible implementation manner of the first aspect, the method further includes: If the target update date is consistent with the effective date of the target update plan, and the update control identifier corresponding to the target update plan is the preset second identifier, then the target update date is determined as the target effective date of the parameter baseline quantity used in this parameter update; the preset first identifier and the preset second identifier are different. If the target update date is inconsistent with the effective date of the corresponding target update plan, then the target update date will be determined as the target effective date of the parameter baseline quantity used in this parameter update.

[0010] Here, when the update control identifier is the preset second identifier, or when the target update date is inconsistent with the planned effective date, the rule directly determines the target update date as the target effective date. This method provides an alternative path for determining the effective date, ensuring that under specific business conditions, the effective date of the parameter baseline quantity can be consistent with the update operation date, thereby associating it with the latest data baseline. This allows parameter updates to respond to changes in a timely manner, ensuring the timeliness and applicability of parameter updates.

[0011] In one possible implementation of the first aspect, obtaining the parameter update schedule table corresponding to the target resource account includes: Retrieve the parameter update record table and the current date; the parameter update record table also includes the previous update date and the next update date of the resource usage cost parameter corresponding to the target resource account; If the current date is the same as the next update date, then obtain the parameter update schedule table corresponding to the target resource account, and use the current date as the target update date.

[0012] This method automates the parameter update task by retrieving the parameter update record table and comparing the current date with the recorded next update date. When the current date matches, the process of retrieving the parameter update plan table and setting the current date as the target update date is automatically triggered. This reduces manual intervention, avoids update delays or omissions due to subjective negligence, ensures that the parameter update task can be started on time and accurately, and improves the efficiency and reliability of parameter update task execution.

[0013] In one possible implementation of the first aspect, each update plan also corresponds to a parameter update interval, a plan expiration date, and an initial parameter adjustment date; After determining the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, the method also includes: Use the target update date as the previous update date of the resource usage cost parameter in the parameter update record table, and use the target effective date as the previous baseline update date in the parameter update record table; Based on the parameter update interval corresponding to the target update plan, the target update dates are periodically superimposed to obtain candidate update dates; If the candidate update date is less than or equal to the expiration date of the target update plan, the candidate update date will be used as the next update date of the resource usage cost parameter in the parameter update record table. If the candidate update date is greater than the expiration date of the target update plan, then the next update plan after the target update plan in the parameter update plan table is determined, and the initial parameter adjustment date in the next update plan is used as the next update date of the resource usage cost parameter in the parameter update record table.

[0014] Based on the above technical content, after determining the second resource usage cost parameter, this embodiment updates the target update date and target effective date to the previous update date column and the previous baseline update date column in the parameter update record table, respectively, accurately recording the operation time and the baseline time on which the update is based; then, candidate update dates are calculated based on the parameter update interval in the target update plan, and it is determined whether to set it as the next update date or switch to the initial parameter adjustment date of the next plan based on the plan expiration date, thereby realizing the automatic update of the update plan on the timeline, ensuring that the parameter update system can operate continuously for a long time, and improving the level of automation of management and the stability of the system.

[0015] In one possible implementation of the first aspect, a target update plan is determined in at least one update plan based on the target update date, including: Iterate through multiple update plans in the parameter update plan table; Determine whether each update plan meets the preset conditions, and determine the update plan that meets the preset conditions as the target update plan; the preset conditions include that the effective date of the update plan is less than or equal to the target update date, and the expiration date of the update plan is greater than or equal to the target update date.

[0016] Here, by traversing the parameter update plan table and filtering based on the condition that the plan's effective date is less than or equal to the target update date and the plan's expiration date is greater than or equal to the target update date, the target update plan is determined. This ensures that the selected update plan is unique and valid under the current update date. This avoids rule application errors caused by plan overlap, expiration, or missing plans, and guarantees that the logic followed by each parameter update is clear and definite, thereby improving the accuracy of parameter update behavior and the predictability of results.

[0017] In one possible implementation of the first aspect, after determining the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, the method further includes: Based on the target resource account's identification information, the second resource usage cost parameters, and the target update date, a notification message is generated; Call the preset service interface to send the notification information to the user terminal bound to the target resource account.

[0018] In this embodiment, after determining the second resource usage cost parameter, a notification message containing the account identifier, the new parameter value, and the update date is generated and sent to the bound user terminal via a service interface, thus achieving automated push notification of parameter change information. This step improves the transparency of parameter updates, allowing users to promptly understand and verify parameter changes, while also leaving a traceable record of parameter updates, enhancing user experience and the auditability of update operations.

[0019] Secondly, a task execution device is provided, the device comprising: The first execution unit is used to execute the task of determining the resource return value corresponding to the target resource account based on the first resource usage cost parameter. The acquisition unit is used to acquire the parameter update plan table corresponding to the target resource account; wherein, the parameter update plan table includes at least one update plan for the first resource usage cost parameter; wherein, the update plan is used to update the value of the first resource usage cost parameter, and each update plan corresponds to a plan effective date, update control identifier, parameter baseline quantity and parameter offset quantity; The first determining unit is used to determine the target update plan in at least one update plan based on the target update date; The first processing unit is configured to read the previous baseline update date from the parameter update record table corresponding to the target resource account if the target update date is consistent with the plan effective date corresponding to the target update plan and the update control identifier corresponding to the target update plan is a preset first identifier, and determine the previous baseline update date as the target effective date of the parameter baseline quantity used in this parameter update; the previous baseline update date is the most recent update date of the parameter baseline quantity. The second determining unit is used to determine the target value of the parameter benchmark quantity based on the target effective date; The second execution unit is used to determine the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, and to execute the resource return value determination task corresponding to the target resource account based on the second resource usage cost parameter; the resource return value is used to execute the resource return business corresponding to the target resource account.

[0020] Thirdly, an electronic 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 electronic device to perform the method of the first aspect and any possible implementation thereof.

[0021] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer instructions. When these computer instructions are executed by a processor, they are used to implement the method as described in the first aspect and any possible implementation thereof.

[0022] Fifthly, embodiments of this application provide a computer program product that, when running on a computer / executed by the computer's processor, implements the method described in the first aspect and any possible design thereof. The computer may be an electronic device as described in the third aspect and any possible implementation thereof.

[0023] Understandably, the beneficial effects achieved by the task execution device of the second aspect, the electronic device of the third aspect, the computer-readable storage medium of the fourth aspect, and the computer program product of the fifth aspect provided above can be referred to as the beneficial effects of the first aspect and any possible implementation thereof, which will not be repeated here. Attached Figure Description

[0024] Figure 1 This is a flowchart illustrating a task execution method provided in an embodiment of this application; Figure 2 This is a flowchart illustrating another task execution method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating another task execution method provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a task execution device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] The calculation of resource return value depends on the resource usage cost parameter, which needs to be dynamically adjusted to ensure the accuracy of the calculation. Existing technologies mostly use preset fixed rules and update the parameter at fixed intervals, which can easily lead to the parameter not matching the actual situation, resulting in data deviation and affecting the accuracy of the calculation.

[0030] Taking bank loan business as an example, the resource usage cost parameter can be the loan interest rate. The loan interest rate is usually repriced and adjusted based on market benchmark interest rates such as the Loan Prime Rate (LPR) and contractual agreements. For example, for a floating-rate loan linked to the LPR, the contract stipulates that January 1st of each year is the repricing date and the spread remains unchanged during the loan term. Although the new interest rate will be calculated based on the latest LPR on the repricing date, this fixed spread and fixed adjustment cycle is difficult to adapt to market fluctuations and changes in the borrower's actual situation. Ultimately, it may lead to the loan interest rate adjustment result deviating from the actual needs and affecting the accuracy of the calculation of the relevant resource return value.

[0031] Taking cloud computing services as an example, the unit price of cloud servers, as a parameter of resource usage cost, cannot be flexibly optimized based on users' real-time resource utilization or sudden market promotions if it can only be adjusted with a fixed discount during a fixed renewal period. This results in users' payments (i.e., resource return value) potentially deviating from the optimal cost they should enjoy. This solution can address the problem of inaccurate resource return value calculation caused by a rigid parameter adjustment mechanism in such cross-industry and cross-business scenarios.

[0032] To improve the accuracy of resource return value calculation, the embodiments of this application first obtain the parameter update plan table of the target resource account, and then determine the target update plan from multiple update plans based on the target update date. When the target update date is consistent with the plan effective date and the update control identifier is a preset first identifier, the previous benchmark update date is read and used as the target effective date of the current parameter benchmark quantity. Based on this target effective date, the target value of the parameter benchmark quantity is determined, ensuring the accuracy of the parameter benchmark quantity value. Finally, the second resource usage cost parameter is calculated based on the target value and the offset, and the resource return value calculation is performed based on this. This avoids the resource usage cost parameter update error that may be introduced by directly using the latest parameter benchmark data, thereby improving the accuracy of resource return value calculation while meeting the need for flexible adjustment.

[0033] This application provides a task execution method that can be applied to electronic devices. The electronic device can be a single server or a server cluster consisting of multiple servers, or a cloud computing platform with data processing capabilities, an edge computing device, a chip, or a device with computing capabilities. This application does not limit the specific form of the electronic device.

[0034] Figure 1 This is a flowchart illustrating a task execution method provided in an embodiment of this application. Figure 1 As shown, the method in the embodiments of this application may include: S101. Based on the first resource usage cost parameter, execute the task of determining the resource return value corresponding to the target resource account.

[0035] The first resource usage cost parameter is the currently effective resource usage cost parameter used to calculate the resource return value. This parameter can be, for example, an interest rate, fee rate, or coefficient. The resource return value determination task refers to the process of calculating the return value for the target resource account based on the resource usage cost parameter, such as calculating interest or fee reductions.

[0036] For example, this embodiment uses the currently configured first resource usage cost parameter to perform resource return value calculation. For instance, the first resource usage cost parameter is a benchmark interest rate of "5%", and the repayment amount for the target resource account is calculated based on this interest rate.

[0037] This embodiment uses currently effective resource usage cost parameters for calculation, ensuring continuous and stable operation of services within the parameter update cycle or before specific adjustments are triggered. It also guarantees the stability and continuity of resource return values ​​when no update instruction is received.

[0038] S102. Obtain the parameter update plan table corresponding to the target resource account; wherein, the parameter update plan table includes at least one update plan for the first resource usage cost parameter; the update plan is used to update the value of the first resource usage cost parameter, and each update plan corresponds to a plan effective date, update control identifier, parameter baseline and parameter offset.

[0039] The parameter update plan table can be a pre-defined structured data table used to manage the update rules for resource usage cost parameters; the plan effective date refers to the effective date of the update plan; the update control identifier is used to control the update mode, for example, the first preset identifier indicates the "non-baseline update" mode, and the second preset identifier indicates the "baseline update" mode; the parameter baseline quantity is the basic value for calculating resource usage cost parameters, such as the benchmark interest rate, benchmark price, etc.; the parameter offset is the adjustment amount relative to the parameter baseline quantity, such as adding or subtracting points, percentage offset, etc.

[0040] For example, in this embodiment, the parameter update schedule is obtained by accessing the parameter update schedule storage module associated with the target resource account.

[0041] The preset parameter update schedule in this embodiment provides a structured basis for the dynamic adjustment of resource usage cost parameters. It realizes a shift from traditional fixed-term updates to on-demand, business-plan-based updates, freeing parameter updates from fixed time periods and allowing for flexible scheduling based on actual business needs, thus laying a data foundation for subsequent precise parameter adjustments.

[0042] S103. Based on the target update date, determine the target update plan in at least one update plan.

[0043] The target update date is the date that triggers the parameter update, which can be the current date, a manually specified date, or the event trigger date.

[0044] For example, in this embodiment, the target update date is matched with the planned effective date of each update plan in the parameter update plan table, and the update plan whose planned effective date is consistent with the target update date is selected as the target update plan.

[0045] This embodiment accurately identifies the update rule to be executed by date matching, ensuring that each update action is controlled by preset business logic and avoiding the arbitrariness of manual selection.

[0046] S104. If the target update date is consistent with the plan effective date corresponding to the target update plan, and the update control identifier corresponding to the target update plan is the preset first identifier, then read the previous baseline update date from the parameter update record table corresponding to the target resource account, and determine the previous baseline update date as the target effective date of the parameter baseline quantity used in this parameter update; the previous baseline update date is the most recent update date of the parameter baseline quantity.

[0047] The parameter update record table is used to record the historical parameter update information of the target resource account, which may include the date of the last or previous updates, the update type, the baseline value, etc.

[0048] The previous baseline update date refers to the date on which the parameter baseline quantity was last updated.

[0049] For example, in this embodiment, under the conditions that "the target update date is consistent with the planned effective date" and "the update control identifier is a preset first identifier (such as 'non-baseline update')," the corresponding update mode is triggered, such as non-baseline update: the parameter update record table is queried to obtain the date of the most recent baseline update, such as "2023-09-15," as the target effective date of the current parameter baseline quantity. This mechanism ensures that when temporarily adjusting parameters, the use of potentially changed baseline data is avoided, and instead, historically stable baselines are used.

[0050] S105. Based on the target effective date, determine the target value of the parameter benchmark quantity.

[0051] For example, in this embodiment, the parameter benchmark value corresponding to the determined target effective date is obtained from the parameter benchmark data source. For instance, if the target effective date is "2023-09-15", then the value of the benchmark interest rate on "2023-09-15" is "4.8%" as the target value of the parameter benchmark.

[0052] In one feasible implementation, the data source for the parameter baseline can be stored in a time series database or a parameter snapshot table, which can be accurately retrieved by date.

[0053] This embodiment ensures the accuracy of the parameter baseline values ​​from the data source, providing reliable data support for generating resource usage cost parameters that meet business requirements.

[0054] S106. Based on the target value and offset, determine the second resource usage cost parameter corresponding to the target resource account, and based on the second resource usage cost parameter, execute the resource return value determination task corresponding to the target resource account; the resource return value is used to execute the resource return business corresponding to the target resource account.

[0055] For example, this embodiment combines the target value of the parameter baseline with the parameter offset specified in the target update plan to calculate the second resource usage cost parameter. For instance, if the target value is "4.8%" and the offset is "+0.5%", then the second resource usage cost parameter = 4.8% + 0.5% = 5.3%. Subsequently, based on the second resource usage cost parameter, the resource return value calculation task for the target resource account is re-executed, for example, calculating the resource return value with an interest rate of 5.3%.

[0056] In one feasible implementation, this embodiment can also perform comprehensive calculations by combining the target resource account's loan cycle, loan amount, and other factors when calculating the resource return value.

[0057] In this embodiment, the calculation of resource return value can be accurately adapted to different business scenarios, taking into account both flexibility and accuracy.

[0058] In summary, this embodiment provides a structured execution basis for parameter updates by obtaining the parameter update plan table of the target resource account, realizing the transformation from fixed-term updates to on-demand and planned updates; and further, it determines the target update plan in the plan according to the target update date, ensuring that each update action is controlled by preset business rules. When specific conditions are met—namely, the target update date matches the planned effective date and the update control identifier is the preset first identifier—the mechanism backtracks and uses the previous baseline update date as the target effective date for the current parameter baseline quantity. The core of this mechanism is the implementation of a "non-baseline update" mode. This means that when temporary parameter adjustments are needed, such as adjusting only the addition or subtraction points, the use of potentially changed, latest baseline data can be avoided. Based on this target effective date, the target value of the parameter baseline quantity is determined, ensuring that the calculation baseline upon which this parameter adjustment relies remains stable and is not affected by daily fluctuations in external data. Finally, a second resource usage cost parameter is calculated based on this stable baseline and the offset, and resource return value calculation is performed accordingly. This allows the calculation of the resource return value to accurately distinguish between two different business scenarios: "temporary parameter adjustment" and "baseline data update." This satisfies business flexibility while eliminating calculation deviations caused by misuse of the baseline, thereby systematically improving the business compliance and numerical accuracy of resource return value determination and ensuring the normal operation of resource return business.

[0059] Figure 2 This is a flowchart illustrating another task execution method provided in an embodiment of this application. For example... Figure 2 As shown, the method in the embodiments of this application may include: S201. Based on the first resource usage cost parameter, execute the task of determining the resource return value corresponding to the target resource account.

[0060] The first resource usage cost parameter is the currently effective resource usage cost parameter, used to calculate the resource return value of the target resource account. For example, in a loan interest rate management scenario, the first resource usage cost parameter could be the current loan account's execution interest rate.

[0061] This embodiment performs resource return value calculation tasks based on this parameter, such as calculating interest return amount, fee reduction amount, etc.

[0062] In one feasible implementation, the resource return value calculation task can be triggered periodically, such as daily batch processing, or executed according to the account's agreed cycle, to ensure the timeliness of resource return accounting.

[0063] S202. Obtain the parameter update record table and the current date; wherein, the parameter update record table also includes the previous update date and the next update date of the resource usage cost parameter corresponding to the target resource account.

[0064] For example, the parameter update record table includes at least the "previous update date" and "next update date" fields, which represent the execution date of the most recent parameter update and the trigger date of the planned next parameter update, respectively.

[0065] The current date can be automatically obtained from the system clock or passed in by an external scheduled task. For example, the parameter update log table records: the previous update date is "2024-01-01", and the next update date is "2024-09-25". This embodiment realizes the automatic triggering and scheduling of parameter update tasks by comparing the current date with the next update date.

[0066] In one example, taking the loan interest rate as the resource usage cost parameter, the resource account is the loan account. Table 1 is a parameter update record table provided in this embodiment. As shown in Table 1, the parameter update record table includes the fields "Last Interest Rate Update Date" and "Next Interest Rate Update Date," which respectively represent the execution date of the most recent parameter update and the trigger date of the planned next parameter update. It also includes the last interest rate repricing date, indicating the date on which the interest rate was last updated based on the latest LPR.

[0067] Table 1 Parameter Update Record Table

[0068] See Table 2, which is the field description table corresponding to Table 1: First Field Description Table.

[0069] Table 2 Description of the First Field

[0070] S203. If the current date is the same as the next update date, obtain the parameter update plan table corresponding to the target resource account and use the current date as the target update date.

[0071] The parameter update schedule includes at least one update schedule for the first resource usage cost parameter. The update schedule is used to update the value of the first resource usage cost parameter. Each update schedule corresponds to a schedule effective date, update control identifier, parameter baseline value, and parameter offset value.

[0072] For example, in this embodiment, when the current date is detected to be the same as the next update date, all parameter update plans corresponding to the target resource account are automatically read from the parameter update plan table.

[0073] The parameter update plan table can be a structured data table. Each update plan record includes: the plan effective date (indicating the date the plan takes effect), an update control identifier (used to distinguish the update mode, such as "X" for non-benchmark update and "Y" for benchmark update), the parameter benchmark amount (such as the LPR benchmark interest rate), and the parameter offset (such as a spread). For example, the plan effective date is "2024-09-25", the update control identifier is "X", the parameter benchmark amount is "LPR", and the parameter offset is "-0.6%". In this embodiment, the current date is used as the target update date for the judgment and execution of subsequent update logic.

[0074] In one example, taking the resource usage cost parameter as the loan interest rate, the resource account is the loan account, the parameter benchmark is the LPR, and the parameter offset is the addition or subtraction of points. Table 3 is a parameter update plan table provided in this embodiment. As can be seen from Table 3, the value range of the update control flag in the table is [N], [X], and [Y]. Flag [N] indicates that this plan has expired, flag [X] indicates that the LPR on the last repricing date is used, and flag [Y] indicates that the latest LPR is used.

[0075] Table 3 Parameter Update Schedule

[0076] See Table 4, which is a description of the fields corresponding to Table 3: Second Field Description: In Table 3, the loan account is a unique identifier for the account; Start Date refers to the date this interest rate adjustment plan takes effect; End Date refers to the date this interest rate adjustment plan ceases to be effective; First Interest Rate Adjustment Date refers to the first interest rate adjustment date of this interest rate adjustment plan; Interest Rate Adjustment Interval refers to the interest rate adjustment interval, such as monthly, annually, etc.; Interest Rate Adjustment Date refers to the date of the month in which the interest rate adjustment occurs, such as the 1st, 2nd...31st; Interest Rate Index Code refers to the benchmark interest rate value for the interest rate adjustment; Add / Subtract Points refers to the difference between the benchmark interest rate value and the base rate value.

[0077] Table 4. Description of the Second Field

[0078] By adding an update control flag to the interest rate adjustment plan, this embodiment can merge multiple irregular interest rate adjustment plans into one, reducing storage space and optimizing the implementation logic. It also reduces the number of calls to the interest rate adjustment plan program, thus reducing system performance overhead.

[0079] This embodiment triggers the update process by automatically comparing the parameter update record table with the current date, achieving automated and precise scheduling of parameter update tasks. This method embeds the logic for determining the update time point, replacing error-prone manual monitoring or fixed-period scanning mechanisms. Whether it's a planned periodic update or a temporary update triggered by a special plan, the system can automatically start the corresponding process at the correct time. This fundamentally avoids update omissions or false triggers caused by human forgetfulness, operational delays, or complex rules, greatly improving the timeliness, accuracy, and overall system efficiency of parameter update task execution.

[0080] S204. Based on the target update date, determine the target update plan in at least one update plan.

[0081] In one feasible implementation, S204 includes the following steps: Iterate through multiple update plans in the parameter update plan table; Determine whether each update plan meets the preset conditions, and determine the update plan that meets the preset conditions as the target update plan; the preset conditions include that the effective date of the update plan is less than or equal to the target update date, and the expiration date of the update plan is greater than or equal to the target update date.

[0082] For example, this embodiment iterates through all update plans in the parameter update plan table, checking one by one whether their plan effective date and plan expiration date constitute a valid interval containing the target update date. For example, if the target update date is "2024-09-25", then update plans with a plan effective date ≤ "2024-09-25" and a plan expiration date ≥ "2024-09-25" are selected as target update plans. If multiple plans meet the conditions, a unique target plan can be further determined by priority of effective date or plan sequence number.

[0083] This embodiment ensures that the appropriate update plan can be uniquely and accurately located on any target update date by traversing the parameter update plan table and filtering according to strict date range conditions. This step solves the management challenge of multiple update plans that may have overlapping or gaps in time. Through explicit logical judgment, it eliminates the ambiguity and errors that may occur when manually selecting update plans, ensuring that the business rules followed by each parameter update (such as which baseline to use and what offset to adjust) are certain and consistent. This eliminates parameter calculation errors caused by chaotic rule application from the source, improving the accuracy and predictability of the entire parameter update process.

[0084] S205. If the target update date is consistent with the plan effective date corresponding to the target update plan, and the update control identifier corresponding to the target update plan is the preset first identifier, then read the previous baseline update date from the parameter update record table corresponding to the target resource account, and determine the previous baseline update date as the target effective date of the parameter baseline quantity used in this parameter update.

[0085] The previous baseline update date is the most recent update date of the parameter baseline quantity; For example, after S204, this embodiment further determines whether the target update date is completely consistent with the planned effective date of the target update plan, and whether the update control identifier is a preset first identifier (such as "X", representing "non-benchmark update" mode). If the conditions are met, the "previous benchmark update date" field is read from the parameter update record table, such as the last interest rate repricing date in Table 1, which records the date of the most recent benchmark update of the parameter benchmark quantity. For example, if the previous benchmark update date is "2024-01-01", it is determined as the target effective date of the parameter benchmark quantity in this parameter update.

[0086] S206. If the target update date is consistent with the effective date of the target update plan, and the update control identifier corresponding to the target update plan is the preset second identifier, then the target update date shall be determined as the target effective date of the parameter baseline quantity used in this parameter update.

[0087] The preset first identifier is different from the preset second identifier.

[0088] For example, after S204, if the target update date is consistent with the planned effective date, but the update control identifier is a preset second identifier (such as "Y", representing "baseline update" mode), then this embodiment directly uses the target update date as the target effective date of the parameter baseline quantity.

[0089] For example, if the target update date is "2024-01-01", then the target effective date is also "2024-01-01". This means that this update will use the baseline data on the target update date, which is applicable to standard periodic repricing scenarios.

[0090] S207. If the target update date is inconsistent with the effective date of the corresponding target update plan, the target update date shall be determined as the target effective date of the parameter baseline quantity used in this parameter update.

[0091] For example, after S204, if the target update date is inconsistent with the planned effective date—for instance, if the target update date is a periodic date calculated based on the interest rate adjustment interval rather than the start date of the planned period—this embodiment also directly uses the target update date as the target effective date. This ensures that the baseline data on the update date is always used in regular periodic updates.

[0092] This embodiment defines an alternative parameter update path: when the update control identifier is a preset second identifier, or when the target update date is inconsistent with the planned effective date, the target update date is directly determined as the target effective date. This corresponds to the standard, periodic benchmark data update (i.e., repricing) scenario. Under this path, the effective date of the parameter benchmark quantity is consistent with the current system date, enabling parameter calculation to automatically associate and use the latest benchmark data. This rule, together with the backtracking rule under the first identifier, constitutes a complete parameter update logic system that adapts to different business scenarios (temporary adjustments and periodic updates), ensuring that the parameter update mechanism is both flexible and standardized, comprehensively guaranteeing the timeliness and business adaptability of parameter updates in various scenarios.

[0093] S208. Based on the target effective date, determine the target value of the parameter benchmark quantity.

[0094] In one feasible implementation, S208 includes the following steps: Obtain the first information table; the first information table includes multiple values ​​of the parameter benchmark quantity, each value corresponds to an effective date range, the effective date range consists of the effective start date and the effective end date; use the target effective date as the query condition to query from the first information table; determine the values ​​whose effective start date is less than or equal to the target effective date and whose effective end date is greater than or equal to the target effective date as the target values ​​of the parameter benchmark quantity.

[0095] For example, this embodiment obtains the value of the benchmark parameter by accessing a first information table (such as an LPR parameter table). Each record in the first information table includes a value of the benchmark parameter (such as the LPR interest rate), the effective start date, and the effective end date.

[0096] For example, if the LPR parameter table records: LPR=4.2%, effective start date=“2023-06-21”, effective end date=“2024-02-20”, this embodiment uses the target effective date (e.g., “2024-01-01”) as the query key to filter records where the effective start date is ≤ “2024-01-01” and the effective end date is ≥ “2024-01-01”, and determines their LPR value “4.2%” as the target value of the parameter benchmark. This query mechanism ensures accurate backtracking of the benchmark value, especially in non-benchmark update scenarios, it can lock the benchmark value of a specific historical date.

[0097] In one example, Table 5 is an LPR parameter table provided in an embodiment of this application, see Table 5.

[0098] Table 5

[0099] See Table 6, which is a description table of the fields corresponding to Table 5, specifically the third field description table. In Table 5, LPR represents the market quoted interest rate; the effective start date represents the effective date of the market quoted interest rate; and the effective end date represents the effective end date of the market quoted interest rate.

[0100] Table 6. Description of the Third Field

[0101] This embodiment provides a reliable data source for benchmark quantity tracing by acquiring a first information table that records the historical versions and effective intervals of the benchmark quantity. Then, it performs a precise search using the target effective date as the query condition, determining the value corresponding to the effective interval covering that date as the target value. In loan interest rate adjustment scenarios, this step ensures that when interest rate adjustments are made on non-repricing dates, the system can accurately extract the historical LPR value corresponding to the last repricing date, rather than the latest LPR value. This operation cuts off the impact of unplanned benchmark fluctuations on parameter calculations at the data source, thereby directly improving the accuracy of the benchmark quantity values ​​and laying a solid foundation for subsequently generating resource usage cost parameters that conform to contractual agreements.

[0102] S209. Based on the target value and offset, determine the second resource usage cost parameter corresponding to the target resource account, and based on the second resource usage cost parameter, execute the resource return value determination task corresponding to the target resource account; the resource return value is used to execute the resource return business corresponding to the target resource account.

[0103] For example, this embodiment combines the target value of the parameter baseline with the parameter offset specified in the target update plan to calculate the second resource usage cost parameter. For instance, if the target value (LPR) is "4.2%" and the offset is "-0.6%", then the second resource usage cost parameter = 4.2% - 0.6% = 3.6%. Subsequently, based on the second resource usage cost parameter, the resource return value calculation task for the target resource account is re-executed, for example, calculating the interest return at a rate of 3.6%.

[0104] In one feasible implementation, each update plan also corresponds to a parameter update interval, a plan expiration date, and an initial parameter adjustment date. After determining the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, the method further includes: using the target update date as the previous update date of the resource usage cost parameter in the parameter update record table, and using the target effective date as the previous baseline update date in the parameter update record table; periodically superimposing the target update date based on the parameter update interval corresponding to the target update plan to obtain candidate update dates; if the candidate update date is less than or equal to the plan expiration date corresponding to the target update plan, then using the candidate update date as the next update date of the resource usage cost parameter in the parameter update record table; if the candidate update date is greater than the plan expiration date corresponding to the target update plan, then determining the next update plan after the target update plan in the parameter update plan table, and using the initial parameter adjustment date in the next update plan as the next update date of the resource usage cost parameter in the parameter update record table.

[0105] For example, in this embodiment, after the parameter update is completed, a parameter update record table is automatically maintained. First, the "previous update date" is updated to the target update date, and the "previous baseline update date" is updated to the target effective date. Then, candidate update dates are calculated according to the parameter update interval of the target update plan (such as "annual").

[0106] After completing the parameter update, this embodiment automatically maintains the core fields of the parameter update record table. By recording the operation date and the baseline effective date of this update separately, the behavioral characteristics and data basis of this update are accurately characterized. Subsequently, based on the rules of the current update plan (update interval, expiration date), the next update date is automatically calculated and set, or the system seamlessly switches to the next pending update plan when the current plan ends. This automated process ensures the continuity and integrity of the parameter update plan chain in the time dimension, achieving the management effect of "configuration once, automatic operation for a long time". It avoids the need for manual intervention due to plan gaps, and from a mechanism perspective, ensures the stable and reliable execution of long-term and complex parameter update strategies, significantly improving the system's automation level and operational stability.

[0107] In another feasible implementation, after determining the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, the method further includes: Based on the target resource account's identification information, the second resource usage cost parameters, and the target update date, a notification message is generated; a preset service interface is called to send the notification message to the user terminal bound to the target resource account.

[0108] For example, in this embodiment, after the parameter update is successful, a notification message is automatically generated, including: account number, updated resource usage cost parameters (such as the new interest rate), and the effective date of the update. For example, the notification message is: "Your loan account (account 01) interest rate was adjusted to 3.6% on 2024-09-25."

[0109] This embodiment sends the notification to the user's bound mobile phone or email address by calling a preset service interface (such as an SMS gateway, email server, or APP push interface).

[0110] After the parameters are updated, this embodiment establishes a feedback mechanism with users by automatically generating and pushing notifications containing key information. This step promptly informs users of parameter change events (such as adjustments to interest rate spreads or changes in benchmark interest rates). This not only improves the transparency of parameter updates, allowing users to verify the basis for their resource return value calculations, but more importantly, it provides an effective audit trail. All parameter change records (including the content of the change, the time of the change, and the rules on which it was based) are retained and traceable, greatly enhancing the compliance, credibility, and user satisfaction of business operations.

[0111] In summary, this embodiment utilizes the collaborative operation of parameter update record tables, plan tables, and the first information table, combined with multi-mode update logic (benchmark update and non-benchmark update), to achieve flexible, accurate, and automated management of resource usage cost parameters. In loan interest rate scenarios, it effectively supports the business requirement of adjusting only the spreads on non-repricing days without changing the benchmark LPR, resolving the issues of redundant multi-segment plan storage and logical complexity. Simultaneously, it enhances user experience and business compliance through a notification mechanism, thereby improving the system's overall adaptability and operational efficiency in complex market environments.

[0112] Taking the resource usage cost parameter as the loan interest rate as an example, the resource account is the loan account, the parameter benchmark is the LPR, and the parameter offset is the addition or subtraction of points. Figure 3This is a flowchart illustrating another task execution method provided in this application embodiment. First, the interest rate adjustment procedure is entered, the interest rate adjustment information table is read, and the next interest rate adjustment date is obtained from the table. It is determined whether the current day is the interest rate adjustment date for the account; if not, the interest rate adjustment procedure ends; if so, the next step is executed. Then, the interest rate adjustment plan table is read, the current interest rate adjustment plan is obtained, and it is determined whether the start date of the currently effective interest rate adjustment plan segment is equal to the current day. If this condition is met, the next step is executed. It is determined whether the "immediately effective" flag for the start date of the currently effective interest rate adjustment plan segment is "X"; if this condition is met, the next step is executed. The LPR effective date is set to the last interest rate repricing date. Afterwards, the LPR parameter table is read using the LPR effective date to obtain the LPR value. Then, the obtained LPR value is used and the execution interest rate for the account is calculated based on the spread. Subsequently, the last interest rate adjustment date in the interest rate adjustment information table is updated to the current date, and the last interest rate repricing date is updated to the set LPR effective date. Finally, the next interest rate adjustment date for the account is calculated.

[0113] Figure 4 This is a schematic diagram of the structure of a task execution device provided in an embodiment of this application. Figure 4 As shown, the task execution device includes a first execution unit 401, an acquisition unit 402, a first determination unit 403, a first processing unit 404, a second determination unit 405, and a second execution unit 406.

[0114] The first execution unit 401 is used to execute the task of determining the resource return value corresponding to the target resource account based on the first resource usage cost parameter.

[0115] The acquisition unit 402 is used to acquire the parameter update plan table corresponding to the target resource account; wherein, the parameter update plan table includes at least one update plan for the first resource usage cost parameter; wherein, the update plan is used to update the value of the first resource usage cost parameter, and each update plan corresponds to a plan effective date, update control identifier, parameter baseline and parameter offset.

[0116] The first determining unit 403 is used to determine a target update plan in at least one update plan based on the target update date.

[0117] The first processing unit 404 is configured to read the previous baseline update date from the parameter update record table corresponding to the target resource account if the target update date is consistent with the plan effective date corresponding to the target update plan and the update control identifier corresponding to the target update plan is a preset first identifier, and determine the previous baseline update date as the target effective date of the parameter baseline quantity used in this parameter update; the previous baseline update date is the most recent update date of the parameter baseline quantity.

[0118] The second determining unit 405 is used to determine the target value of the parameter benchmark quantity based on the target effective date.

[0119] The second execution unit 406 is used to determine the second resource usage cost parameter corresponding to the target resource account based on the target value and offset, and to execute the resource return value determination task corresponding to the target resource account based on the second resource usage cost parameter; the resource return value is used to execute the resource return business corresponding to the target resource account.

[0120] In other embodiments, the second processing unit 405 is specifically used for: Obtain the first information table; the first information table includes multiple values ​​of the parameter baseline quantity, each value corresponds to an effective date range, and the effective date range consists of the effective start date and the effective end date.

[0121] Use the target effective date as the query condition to perform a query from the first information table.

[0122] The value of the effective start date being less than or equal to the target effective date, and the effective end date being greater than or equal to the target effective date, is determined as the target value of the parameter baseline.

[0123] In other embodiments, the apparatus further includes a first processing unit for: If the target update date is consistent with the effective date of the target update plan, and the update control identifier corresponding to the target update plan is the preset second identifier, then the target update date is determined as the target effective date of the parameter baseline quantity used in this parameter update; the preset first identifier and the preset second identifier are different.

[0124] If the target update date is inconsistent with the effective date of the corresponding target update plan, then the target update date will be determined as the target effective date of the parameter baseline quantity used in this parameter update.

[0125] In other embodiments, the acquisition unit 402 is specifically used for: Retrieve the parameter update record table and the current date; the parameter update record table also includes the previous update date and the next update date of the resource usage cost parameter corresponding to the target resource account.

[0126] If the current date is the same as the next update date, then obtain the parameter update schedule table corresponding to the target resource account, and use the current date as the target update date.

[0127] In other embodiments, each update plan also corresponds to a parameter update interval, a plan expiration date, and an initial parameter adjustment date.

[0128] Following the second execution unit 406, the device further includes an update unit for: Use the target update date as the previous update date of the resource usage cost parameter in the parameter update record table, and use the target effective date as the previous baseline update date in the parameter update record table.

[0129] Based on the parameter update interval corresponding to the target update plan, the target update dates are periodically superimposed to obtain candidate update dates.

[0130] If the candidate update date is less than or equal to the expiration date of the target update plan, then the candidate update date will be used as the next update date for the resource usage cost parameter in the parameter update record table.

[0131] If the candidate update date is greater than the expiration date of the target update plan, then the next update plan after the target update plan in the parameter update plan table is determined, and the initial parameter adjustment date in the next update plan is used as the next update date of the resource usage cost parameter in the parameter update record table.

[0132] In other embodiments, the first determining unit 403 is specifically used for: Iterate through multiple update plans in the parameter update plan table.

[0133] Determine whether each update plan meets the preset conditions, and determine the update plan that meets the preset conditions as the target update plan; the preset conditions include that the effective date of the update plan is less than or equal to the target update date, and the expiration date of the update plan is greater than or equal to the target update date.

[0134] In other embodiments, after the second execution unit 406, the apparatus further includes a third processing unit for: A notification message is generated based on the target resource account's identification information, the second resource usage cost parameters, and the target update date.

[0135] Call the preset service interface to send the notification information to the user terminal bound to the target resource account.

[0136] The task execution 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.

[0137] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example... Figure 5 As shown, the electronic device includes a memory 501 and at least one processor 502.

[0138] The memory 501 is used to store computer program code, which includes computer instructions. These computer instructions run in the aforementioned electronic 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, or a USB flash drive, portable hard drive, read-only memory, magnetic disk, or optical disk, etc.

[0139] Processor 502 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 502 can also be other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor.

[0140] The memory 501 and processor 502 are communicatively connected. For example, the memory 501 can connect to the processor 502 via a system bus and communicate with it. 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, only one thick line is used in the figure, but this does not mean that there is only one bus or one type of bus.

[0141] Optionally, the memory 501 can be either standalone or integrated with the processor 502. When the memory 501 is set up independently, it is connected to the processor 502 via a system bus.

[0142] This application also provides a chip for executing instructions, which is used to execute the technical solution of the task execution method in the above embodiments.

[0143] 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 task execution method described in the above embodiments. Specifically, when the computer instructions are executed by a processor, the electronic device can execute the technical solution of the task execution method described in the above embodiments.

[0144] 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 task execution method in the above embodiments.

[0145] 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 media can be any available medium accessible to a general-purpose or special-purpose computer.

[0146] 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 an application-specific integrated circuit (ASIC). 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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 task execution method, characterized in that, The method includes: Based on the first resource usage cost parameter, execute the task of determining the resource return value corresponding to the target resource account; Obtain the parameter update plan table corresponding to the target resource account; wherein, the parameter update plan table includes at least one update plan for the first resource usage cost parameter; the update plan is used to update the value of the first resource usage cost parameter, and each update plan corresponds to a plan effective date, update control identifier, parameter baseline value and parameter offset value; Based on the target update date, determine a target update plan in at least one of the update plans; If the target update date is consistent with the effective date of the target update plan, and the update control identifier corresponding to the target update plan is a preset first identifier, then the previous baseline update date is read from the parameter update record table corresponding to the target resource account, and the previous baseline update date is determined as the target effective date of the parameter baseline quantity used in this parameter update; the previous baseline update date is the most recent update date of the parameter baseline quantity; Based on the target effective date, determine the target value of the parameter benchmark quantity; Based on the target value and the offset, a second resource usage cost parameter corresponding to the target resource account is determined, and based on the second resource usage cost parameter, a resource return value determination task corresponding to the target resource account is executed; the resource return value is used to execute the resource return business corresponding to the target resource account.

2. The task execution method according to claim 1, characterized in that, The step of determining the target value of the parameter benchmark quantity based on the target effective date includes: Obtain a first information table; the first information table includes multiple values ​​of the parameter baseline quantity, each value corresponds to an effective date range, the effective date range is composed of the effective start date and the effective end date; Using the target effective date as the query condition, query from the first information table; The value of the effective start date being less than or equal to the target effective date, and the effective end date being greater than or equal to the target effective date, is determined as the target value of the parameter benchmark quantity.

3. The task execution method according to claim 1, characterized in that, The method further includes: If the target update date is consistent with the planned effective date corresponding to the target update plan, and the update control identifier corresponding to the target update plan is a preset second identifier, then the target update date is determined as the target effective date of the parameter baseline quantity used in this parameter update; the preset first identifier is different from the preset second identifier; If the target update date is inconsistent with the planned effective date corresponding to the target update plan, then the target update date shall be determined as the target effective date of the parameter baseline quantity used in this parameter update.

4. The task execution method according to claim 1, characterized in that, The step of obtaining the parameter update schedule table corresponding to the target resource account includes: Obtain the parameter update record table and the current date; wherein, the parameter update record table also includes the previous update date and the next update date of the resource usage cost parameter corresponding to the target resource account; If the current date is the same as the next update date, then obtain the parameter update schedule table corresponding to the target resource account, and use the current date as the target update date.

5. The task execution method according to claim 4, characterized in that, Each update plan also corresponds to a parameter update interval, a plan expiration date, and an initial parameter adjustment date; After determining the second resource usage cost parameter corresponding to the target resource account based on the target value and the offset, the method further includes: The target update date is used as the previous update date of the resource usage cost parameter in the parameter update record table, and the target effective date is used as the previous baseline update date in the parameter update record table; Based on the parameter update interval corresponding to the target update plan, the target update dates are periodically superimposed to obtain candidate update dates; If the candidate update date is less than or equal to the plan expiration date corresponding to the target update plan, then the candidate update date will be used as the next update date for the resource usage cost parameter in the parameter update record table; If the candidate update date is greater than the expiration date of the target update plan, then the next update plan after the target update plan in the parameter update plan table is determined, and the initial parameter adjustment date in the next update plan is used as the next update date of the resource usage cost parameter in the parameter update record table.

6. The task execution method according to claim 1, characterized in that, The step of determining a target update plan in at least one of the update plans based on the target update date includes: Iterate through multiple update plans in the parameter update plan table; Determine whether each update plan meets preset conditions, and determine the update plan that meets the preset conditions as the target update plan; the preset conditions include that the effective date of the update plan is less than or equal to the target update date, and the expiration date of the update plan is greater than or equal to the target update date.

7. The task execution method according to claim 1, characterized in that, After determining the second resource usage cost parameter corresponding to the target resource account based on the target value and the offset, the method further includes: Based on the identification information of the target resource account, the second resource usage cost parameter, and the target update date, a notification message is generated; The preset service interface is invoked to send the notification information to the user terminal bound to the target resource account.

8. A task execution device, characterized in that, The device includes: The first execution unit is used to execute the task of determining the resource return value corresponding to the target resource account based on the first resource usage cost parameter. The acquisition unit is used to acquire the parameter update plan table corresponding to the target resource account; wherein the parameter update plan table includes at least one update plan for the first resource usage cost parameter; wherein the update plan is used to update the value of the first resource usage cost parameter, and each update plan corresponds to a plan effective date, update control identifier, parameter baseline value and parameter offset value; The first determining unit is configured to determine a target update plan in at least one of the update plans based on the target update date; The first processing unit is configured to, if the target update date is consistent with the plan effective date corresponding to the target update plan, and the update control identifier corresponding to the target update plan is a preset first identifier, read the previous baseline update date from the parameter update record table corresponding to the target resource account, and determine the previous baseline update date as the target effective date of the parameter baseline quantity used in this parameter update; the previous baseline update date is the most recent update date of the parameter baseline quantity; The second determining unit is used to determine the target value of the parameter benchmark quantity based on the target effective date; The second execution unit is used to determine the second resource usage cost parameter corresponding to the target resource account based on the target value and the offset, and to execute the resource return value determination task corresponding to the target resource account based on the second resource usage cost parameter; the resource return value is used to execute the resource return business corresponding to the target resource account.

9. An electronic device, characterized in that, include: The electronic device includes 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 electronic device performs the task execution method as described in any one of claims 1-7.

10. 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 task execution method as described in any one of claims 1-7.

11. A computer program product, characterized in that, When the computer program product is run on a computer / executed by the computer's processor, the task execution method as described in any one of claims 1-7 is implemented.

Images