Method, device and server for automatic repricing

Abstract

The application provides an automatic tracing pricing execution method, device and server, relates to the technical field of computer application, and can obtain a tracing account range, then pull the pricing result data of the previous day of a tracing day back to a pricing result table for tracing, and place the position data of the tracing day in a preset position data table, so that after starting a pricing task engine, the tracing times of each FTP account within the tracing date range can be calculated according to the preset tracing date range and the tracing account range; and the tracing pricing task corresponding to each tracing time is sequentially submitted to the preset pricing engine for tracing pricing calculation through the pricing task engine. The whole tracing pricing process can realize process control, so that the risk and cost of tracing can be greatly reduced, and the efficiency of tracing is improved.

Description

Technical Field

[0001] This invention relates to the technical field of computer applications, and in particular to an automatic traceability pricing execution method, apparatus, and server. Background Technology

[0002] Internal funds transfer pricing (FTP) refers to an internal management model where a commercial bank's internal funds center and business operating units transfer funds in full and at a cost according to certain rules, aiming to calculate the cost or profit of business funds. Currently, the internal funds transfer pricing system implements daily pricing. However, due to changes in pricing rules, such as for floating-rate transactions, on the day the transaction occurs, the interest rate on the FTP yield curve corresponding to the repricing period of the transaction is used as the FTP price for that transaction. This can be understood as the client's actual interest rate potentially changing with each repricing, which is equivalent to renegotiating with the client. The business department then conducts the FTP transaction with the funds center after the renegotiated price, at which point the FTP price also needs to be re-determined.

[0003] In such situations, it is often necessary to reprice historical data. Previously, this was done by directly writing SQL (Structured Query Language) scripts, testing them in a pre-production environment, and then deploying them to the production environment. This involved directly manipulating the production database to trace historical data and reprice it. The drawbacks of this approach are: high risk, time-consuming and labor-intensive, lack of intelligence, and the need to repeat the process after rule adjustments, leading to significant rework. It also carries the risk of errors or mis-executions, potentially causing production data anomalies and reducing work efficiency. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide an automatic traceability pricing execution method, apparatus and server to alleviate the above-mentioned technical problems.

[0005] In a first aspect, embodiments of the present invention provide an automatic retrospective pricing execution method, comprising: obtaining a range of retrospective accounts; retrieving pricing result data from the previous day of the retrospective date to a pricing result table for retrospective purposes based on the range of retrospective accounts; and retrieving position data for the retrospective date based on the range of retrospective accounts and placing the position data in a preset position data table, wherein the range of retrospective accounts includes multiple internal funds transfer pricing (FTP) accounts; starting a pricing task engine; calculating the number of retrospective attempts for each FTP account within the retrospective date range based on a preset retrospective date range and the range of retrospective accounts; sequentially submitting a retrospective pricing task corresponding to each number of retrospective attempts to a preset pricing engine through the pricing task engine, so that the pricing engine performs retrospective pricing calculations, wherein the retrospective pricing task carries the pricing result table and the position data table; obtaining a pricing completion result returned by the pricing engine to the pricing task engine; and updating the retrospective final table based on the pricing completion result.

[0006] In conjunction with the first aspect, the present invention provides a first possible implementation of the first aspect, wherein the step of sequentially submitting the trace pricing task corresponding to each trace count to a preset pricing engine through the pricing task engine, so that the pricing engine performs trace pricing calculation, includes: submitting the trace pricing task corresponding to each trace count to a Redis database through the pricing task engine, distributing the trace pricing task to the pricing engine for trace pricing calculation through the Redis database; and receiving the completion result of each trace pricing calculation returned by the pricing engine through the pricing task engine, and automatically sending the next trace pricing task corresponding to the trace count to the pricing engine, until all trace pricing tasks corresponding to the trace count are completed.

[0007] In conjunction with the first possible implementation of the first aspect, this embodiment of the invention provides a second possible implementation of the first aspect, wherein the above method further includes: if it is detected that the Redis database distributes the retrospective pricing task to the pricing engine, starting a preset daemon thread; monitoring whether the pricing engine has completed the current retrospective pricing calculation task through the daemon thread, and returning a completion signal to the pricing task engine after the current retrospective pricing calculation task is completed, so that the pricing task engine submits the next retrospective pricing task to the Redis database.

[0008] In conjunction with the second possible implementation of the first aspect, this embodiment of the invention provides a third possible implementation of the first aspect, wherein the step of obtaining the pricing completion result returned by the pricing engine to the pricing task engine includes: obtaining the completion result of each retrospective pricing calculation returned by the pricing engine; merging the completion results of each retrospective pricing calculation to generate the pricing completion result.

[0009] In conjunction with the first aspect, this embodiment of the invention provides a fourth possible implementation of the first aspect, wherein the step of calculating the number of times each FTP account is traced within the traced date range based on a preset traced date range and the traced account range includes: obtaining the traced start date and traced end date included in the traced date range; and determining the number of days contained between the traced start date and the traced end date as the number of times each FTP account is traced within the traced account range.

[0010] In conjunction with the first aspect, this embodiment of the invention provides a fifth possible implementation of the first aspect, wherein, after pulling back the position data of the traceability date, the method further includes: confirming whether the position data requires repayment plan data; if so, pulling back the repayment plan data from the repayment plan history table corresponding to the position data to the repayment plan table in the position data table.

[0011] In conjunction with the first aspect, this invention provides a sixth possible implementation of the first aspect, wherein the step of obtaining the traceability account range includes: obtaining a pre-set information dimension; wherein the information dimension includes at least one of the following dimensions: subject, institution, currency, pricing unit, interest rate type, data date, interest accrual date, maturity date, system source; filtering FTP accounts that satisfy the information dimension from the account database based on the information dimension; and performing deduplication processing on the filtered FTP accounts to obtain a traceability account range containing at least one of the FTP accounts.

[0012] Secondly, embodiments of the present invention also provide an execution device for automatic retrospective pricing, comprising: an acquisition module, configured to acquire a range of retrospective accounts, retrieve pricing result data of the previous day for retrospective date to a pricing result table for retrospective purposes based on the range of retrospective accounts, and retrieve position data of the current day for retrospective date based on the range of retrospective accounts, and place the position data in a preset position data table, wherein the range of retrospective accounts includes multiple internal funds transfer pricing (FTP) accounts; a startup module, configured to start a pricing task engine, calculate the number of retrospective attempts for each FTP account within the range of retrospective dates based on a preset range of retrospective dates and the range of retrospective accounts; a calculation module, configured to sequentially submit the retrospective pricing task corresponding to each number of retrospective attempts to a preset pricing engine through the pricing task engine, so that the pricing engine performs retrospective pricing calculation, wherein the retrospective pricing task carries the pricing result table and the position data table; and an update module, configured to acquire the pricing completion result returned by the pricing engine to the pricing task engine, and update the retrospective final table based on the pricing completion result.

[0013] Thirdly, embodiments of the present invention also provide a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0014] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, performs the steps of the method described in the first aspect above.

[0015] The embodiments of the present invention bring the following beneficial effects:

[0016] The automatic traceability pricing execution method, apparatus, and server provided in this invention can obtain the traceability account range, then pull back the pricing result data of the previous day for traceability based on the traceability account range to a pricing result table for traceability, and place the position data of the traceability day in a preset position data table. After starting the pricing task engine, it can calculate the traceability count for each FTP account within the traceability date range based on the preset traceability date range and traceability account range. The pricing task engine sequentially submits the traceability pricing task corresponding to each traceability count to the preset pricing engine, and the traceability pricing task carries a pricing result table and a position data table. This allows the pricing engine to perform traceability pricing calculations. After the traceability pricing calculation is completed, the pricing completion result returned by the pricing engine to the pricing task engine can be obtained, thereby updating the traceability official table based on the pricing completion result. The entire traceability pricing process can be controlled, which can greatly reduce the risk and cost of traceability and improve traceability efficiency.

[0017] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0018] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0019] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0020] Figure 1 A flowchart illustrating an automatic traceability pricing execution method provided in an embodiment of the present invention;

[0021] Figure 2 A flowchart illustrating another method for implementing automatic traceability pricing as provided in an embodiment of the present invention;

[0022] Figure 3 A flowchart illustrating the distribution of a traceability pricing task is provided in this embodiment of the invention.

[0023] Figure 4 A schematic diagram of the structure of an automatic traceability pricing execution device provided in an embodiment of the present invention;

[0024] Figure 5 This is a schematic diagram of the structure of a server provided in an embodiment of the present invention. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0026] Currently, the retrospective pricing process for internal funds transfer pricing is mostly implemented through SQL scripts. After testing in the pre-production environment, it is released to the production environment, and the production database is directly manipulated to trace the historical pricing. This method has a high risk factor and is time-consuming and labor-intensive. When the rules are adjusted, the process needs to be repeated, which is not only prone to misoperation or misexecution, but also leads to low efficiency.

[0027] Based on this, the present invention provides an automatic traceability pricing execution method, apparatus and server, which can standardize the traceability process, reduce traceability risks and thus improve traceability efficiency.

[0028] To facilitate understanding of this embodiment, a method for implementing automatic traceability pricing disclosed in this embodiment of the invention will first be described in detail.

[0029] In one possible implementation, this invention provides an automatic trace pricing execution method. This method is applied to a server, for example, a server set up in the fintech industry, for performing automatic trace pricing, etc., so that the automatic trace pricing execution method provided by this invention can be executed during the trace pricing process, and an intelligent system can be formed to realize the automation of the trace pricing process.

[0030] Specifically, such as Figure 1 The flowchart shown illustrates an automatic traceability pricing implementation method, which includes the following steps:

[0031] Step S102: Obtain the range of traceable accounts, pull back the pricing result data of the previous day on the traceable date according to the range of traceable accounts to the pricing result table used for traceability, and pull back the position data of the traceable date according to the range of traceable accounts, and place the position data in the preset position data table.

[0032] In this embodiment of the invention, the scope of the traceability accounts includes multiple internal funds transfer pricing (FTP) accounts;

[0033] In practical use, when obtaining the traceability account range in step S102 above, it is generally necessary to filter FTP accounts that meet certain conditions from the account database. Therefore, it is usually necessary to obtain the pre-set information dimensions. The information dimensions include at least one of the following dimensions: subject, institution, currency, pricing unit, interest rate type, data date, value date, maturity date, system source, etc. Then, based on the selected information dimensions, FTP accounts that meet the above information dimensions are filtered from the account database. The filtered FTP accounts are deduplicated to obtain the traceability account range containing at least one FTP account.

[0034] For example, all pricing data is usually stored in a backend database table. If a data quality problem is found in the invoice system and pricing needs to be rerun, the pricing result data for the date that needs to be rerun can be retrieved from the database table. The information dimension is restricted to system source = 'invoice system'. At this time, the range of accounts to be traced can be obtained, and then deduplication can be performed to obtain the traceable account range mentioned above in this embodiment of the invention.

[0035] Once the range of traceable accounts is obtained, the FTP accounts included in the range of traceable accounts can be imported into the server executing the automatic traceable pricing execution method in this embodiment of the invention, so as to execute the above step S102, which pulls back the pricing result data of the previous day of the traceability date to the pricing result table used for traceability. Because some cumulative indicators are added on a daily basis, the pricing result data of the previous day of the traceability date needs to be pulled back to the pricing result table used for traceability rerun before traceability is performed, and then the subsequent steps are executed.

[0036] Furthermore, the retrospective pricing process often traces a continuous date range. After each pricing cycle, the pricing results for that day and beyond need to be recalculated. Therefore, after obtaining the aforementioned range of retrospective accounts, it is also necessary to retrieve the position data for the retrospective date and place the position data in a pre-defined position data table to facilitate subsequent retrospective pricing.

[0037] Step S104: Start the pricing task engine and calculate the number of times each FTP account is traced within the preset trace date range and trace account range.

[0038] Step S106: The pricing task engine submits the retrospective pricing task corresponding to each retrospective count to the preset pricing engine in sequence, so that the pricing engine can perform retrospective pricing calculation.

[0039] The aforementioned retrospective pricing task includes a pricing result table and a position data table;

[0040] Step S108: Obtain the pricing completion result returned by the pricing engine to the pricing task engine, and update the retrospective formal table based on the pricing completion result.

[0041] The automatic traceability pricing execution method provided in this invention can obtain the traceability account range, then pull back the pricing result data of the previous day for traceability based on the traceability account range to a pricing result table for traceability, and place the position data of the traceability day in a preset position data table. After starting the pricing task engine, it can calculate the traceability count for each FTP account within the traceability date range based on the preset traceability date range and traceability account range. The pricing task engine then sequentially submits the traceability pricing task corresponding to each traceability count to the preset pricing engine, and the traceability pricing task carries a pricing result table and a position data table. This allows the pricing engine to perform traceability pricing calculations. After the traceability pricing calculation is completed, the pricing completion result returned by the pricing engine to the pricing task engine can be obtained, thereby updating the traceability official table based on the pricing completion result. The entire traceability pricing process can be controlled, which can greatly reduce the risk and cost of traceability and improve traceability efficiency.

[0042] In practical use, the pricing task engine described in this embodiment of the invention is typically a pre-built engine for distributing retrospective pricing tasks. This engine can be a functional unit deployed on the server or a separate server for distributing retrospective pricing tasks. The pricing engine, on the other hand, is the engine for executing retrospective pricing algorithms. Similarly, it can be a functional unit deployed on the server or a separate server. The specific pricing task engine and pricing-related settings can be configured according to actual usage, and this embodiment of the invention does not impose any limitations on this.

[0043] Furthermore, for loan-related businesses, retrospective pricing typically requires obtaining repayment plan data. Therefore, after retrieving the position data for the retrospective date, it's necessary to further confirm whether the position data requires repayment plan data. If so, the repayment plan data is retrieved from the corresponding repayment plan history table in the position data and then retrieved to the repayment plan table in the position data table. Typically, the position data table has a "Repayment Method" field. For loan-related businesses, each loan transaction has a corresponding repayment method. If the repayment method is irregular (usually defined as the letter "G"), it can be confirmed that retrospective pricing for this transaction requires a repayment plan. In this case, the repayment plan data can be retrieved from the repayment plan history table and retrieved to the repayment plan table in the position data table, i.e., the table corresponding to the "Repayment Method" field, so that the repayment plan data can be retrieved for retrospective pricing.

[0044] Furthermore, after the pricing task engine is started, the process of calculating the number of tracebacks is usually automated. That is, the number of tracebacks is automatically calculated based on a preset traceback date range. Specifically, in step S104 above, the calculation of the number of tracebacks involves obtaining the traceback start date and traceback end date included in the traceback date range; then, the number of days contained between the traceback start date and the traceback end date is determined as the traceback count for each FTP account included in the traceback account range. For example, when traceback begins, the traceback start date and traceback end date are automatically extracted based on the traceback date range. For instance, if the start date is 2022 / 09 / 01 and the end date is 2022 / 09 / 07, since the number of days included is 7, the traceback count for each FTP account is 7 times when determining the number of tracebacks. That is, traceback is performed once a day. After the pricing task engine is started, this process can be automatically executed through the pricing task engine.

[0045] Furthermore, for ease of understanding, in Figure 1 On this basis, Figure 2 A flowchart of another method for implementing automated retrospective pricing is also shown, describing the automated execution process of the pricing task engine distributing retrospective pricing tasks, specifically, as follows: Figure 2 As shown, it includes the following steps:

[0046] Step S202: Obtain the range of traceable accounts, pull back the pricing result data of the previous day on the traceable date according to the range of traceable accounts to the pricing result table used for traceability, and pull back the position data of the traceable date according to the range of traceable accounts, and place the position data in the preset position data table.

[0047] Step S204: Start the pricing task engine and obtain the traceability start date and traceability end date included in the traceability date range;

[0048] Step S206: Determine the number of days included between the start date and the end date of the traceback as the traceback count for each FTP account included in the traceback account range;

[0049] Step S208: Submit the trace pricing task corresponding to each trace count to the Redis database through the pricing task engine, and distribute the trace pricing task to the pricing engine for trace pricing calculation through the Redis database;

[0050] Step S210: Receive the completion result of each retrospective pricing calculation returned by the pricing engine through the pricing task engine, and automatically send the retrospective pricing task corresponding to the next retrospective number to the pricing engine until all retrospective pricing tasks corresponding to the retrospective number are completed.

[0051] In practical use, in this embodiment of the invention, the Redis database is used to distribute retrospective pricing tasks. Specifically, when a retrospective pricing task for one day is submitted, the Redis database locks the task each time it is submitted to prevent multiple submissions.

[0052] Specifically, if Redis detects that it has distributed a retrospective pricing task to the pricing engine, a pre-defined daemon thread can be started. This daemon thread monitors whether the pricing engine has completed the retrospective pricing calculation task and returns a completion signal to the pricing engine after the current retrospective pricing calculation task is completed, so that the pricing engine can submit the next retrospective pricing task to Redis. In other words, Redis receives the task, distributes it to the pricing engine for retrospective pricing calculation, and does not submit a new task until the result of the current retrospective pricing task is returned successfully.

[0053] For ease of understanding, Figure 3 A flowchart illustrating the distribution of a traceability pricing task is shown, such as... Figure 3 As shown, the pricing task engine 30 and pricing engine 31, as well as the Redis database 32 and the server 33 of pricing engine 31, include the following steps in the process of distributing traceable pricing tasks:

[0054] Step S301: The pricing task engine submits the trace pricing task corresponding to each trace count to the Redis database;

[0055] In step S302, the Redis database distributes the retrospective pricing task to the pricing engine for retrospective pricing calculation;

[0056] In step S303, the Redis database starts a preset daemon thread to check whether the pricing engine server is still executing the retrospective pricing task. If it is still executing and is about to time out, a new expiration time will be set for the lock.

[0057] Step S304: After the trace pricing calculation task is completed, a completion signal is returned to the pricing task engine. This signal is then sent back to the pricing task engine via the Redis database, so that the pricing task engine can automatically send the next trace pricing task corresponding to the trace number to the pricing engine, until all trace pricing tasks corresponding to the trace number are completed.

[0058] After the pricing engine completes its retrospective pricing task, it returns the pricing completion result. At this point, the following steps S212 can be executed.

[0059] Step S212: Obtain the pricing completion result returned by the pricing engine to the pricing task engine, and update the retrospective formal table based on the pricing completion result.

[0060] Specifically, when obtaining the pricing completion result, it is necessary to obtain the completion result of each retrospective pricing calculation returned by the pricing engine; then, the completion results of each retrospective pricing calculation are merged to generate the pricing completion result, that is, retrospective accumulation is required. After the retrospective pricing is completed, the result is verified, and the retrospective historical position data and pricing result table are updated to the retrospective official table. Furthermore, in order to ensure the accuracy of the data, the retrospective official table can also be verified by total score. The specific verification process can be set according to the actual use case, and this embodiment of the invention does not limit it.

[0061] Furthermore, in this embodiment of the invention, the server executing the above-mentioned automatic traceability pricing method can also typically provide a graphical user interface for staff to operate. Specifically, the graphical user interface can include a traceability pricing page with function buttons, such as a function button for importing traceability account ranges, a function button for starting traceability pricing, and a function button for updating the traceability official table, etc. Based on this graphical user interface, staff can configure relevant parameters, such as setting information dimensions to filter traceability account ranges, and setting traceability date ranges to calculate traceability times, etc.

[0062] Furthermore, the server executing the above-mentioned automatic retrospective pricing method can also establish communication with relevant databases to present data tables related to the retrospective task in a graphical user interface. For example, staff can call the retrospective pricing result table through the graphical user interface: a table used to store the results of retrospective data pricing calculations; a retrospective pricing historical position table: specifically used to store the data that needs to be traced; a repayment plan history table: used to store data of all historical repayment plans; a pricing historical position table: used to store all historical position data; a pricing result table: used to store all historical pricing result data, etc. The specific data tables and the database storing the data tables can be set according to the actual usage situation, and the embodiments of the present invention do not impose any restrictions on this.

[0063] In summary, compared to related technologies that involve complex and time-consuming processes such as SQL script development, pre-production testing, historical data tracing on the release date, and repricing, resulting in delays of 1 to 2 weeks and uncertainties in timeliness and accuracy, this invention introduces an automated tracing method based on internal funds transfer pricing. This method requires only simple parameter configuration to determine the repricing range, time frame, business feedback, and pricing logic. Users can then directly reprice by clicking the relevant button. Furthermore, the tracing completion time is determined based on the data volume, typically within 0.5 to 2 hours, and operation and tracing records are retained, allowing for reversals as needed. This significantly improves tracing efficiency, reduces rework, lowers tracing risks, truly standardizes the tracing process, improves data quality, and enables better management.

[0064] Furthermore, based on the above embodiments, this invention also provides an automatic traceability pricing execution device, such as... Figure 4 The diagram shown illustrates the structure of an automatic traceability pricing execution device, which includes:

[0065] The acquisition module 40 is used to acquire the range of traceable accounts, pull back the pricing result data of the previous day of the traceable date to the pricing result table for traceability based on the range of traceable accounts, and pull back the position data of the traceable date based on the range of traceable accounts and place the position data in a preset position data table. The range of traceable accounts includes multiple internal funds transfer pricing (FTP) accounts.

[0066] Startup module 42 is used to start the pricing task engine and calculate the number of times each FTP account is traced within the preset trace date range and the trace account range.

[0067] The calculation module 44 is used to submit the retrospective pricing task corresponding to each retrospective number to the preset pricing engine in sequence through the pricing task engine, so that the pricing engine can perform retrospective pricing calculation, wherein the retrospective pricing task carries the pricing result table and the position data table;

[0068] The update module 46 is used to obtain the pricing completion result returned by the pricing engine to the pricing task engine, and update the retrospective formal table according to the pricing completion result.

[0069] Furthermore, the aforementioned calculation module 44 is also configured to: submit the trace pricing task corresponding to each trace count to the Redis database through the pricing task engine, distribute the trace pricing task to the pricing engine for trace pricing calculation through the Redis database; and receive the completion result of each trace pricing calculation returned by the pricing engine through the pricing task engine, and automatically send the next trace pricing task corresponding to the trace count to the pricing engine until all trace pricing tasks corresponding to the trace count are completed.

[0070] Furthermore, if it is detected that the Redis database distributes the retrospective pricing task to the pricing engine, a preset daemon thread is started; the daemon thread monitors whether the pricing engine has completed the current retrospective pricing calculation task, and returns a completion signal to the pricing task engine after the current retrospective pricing calculation task is completed, so that the pricing task engine submits the next retrospective pricing task to the Redis database.

[0071] Furthermore, the aforementioned update module 46 is also used to: obtain the completion result of each retrospective pricing calculation returned by the pricing engine; merge the completion results of each retrospective pricing calculation to generate the pricing completion result.

[0072] Furthermore, the aforementioned startup module 42 is also used to: obtain the trace start date and trace end date included in the trace date range; and determine the number of days contained between the trace start date and the trace end date as the trace count for each FTP account included in the trace account range.

[0073] Furthermore, the aforementioned acquisition module 40 is also used to: after pulling back the position data of the traceback date, confirm whether the position data requires repayment plan data; if so, pull back the repayment plan data from the corresponding repayment plan history table in the position data to the repayment plan table in the position data table.

[0074] Furthermore, the aforementioned acquisition module 40 is also used to: acquire a pre-set information dimension; wherein the information dimension includes at least one of the following dimensions: subject, institution, currency, pricing unit, interest rate type, data date, interest accrual date, maturity date, system source; filter FTP accounts that meet the information dimension from the account database based on the information dimension; and perform deduplication processing on the filtered FTP accounts to obtain a range of traceable accounts containing at least one of the FTP accounts.

[0075] The automatic traceability pricing execution device provided in this embodiment of the invention has the same technical features as the automatic traceability pricing execution method provided in the above embodiments, so it can also solve the same technical problems and achieve the same technical effects.

[0076] Furthermore, embodiments of the present invention also provide a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0077] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described method.

[0078] Furthermore, this embodiment of the invention also provides a schematic diagram of a server structure, such as... Figure 5 The diagram shows the structure of the server, which includes a processor 51 and a memory 50. The memory 50 stores computer-executable instructions that can be executed by the processor 51, and the processor 51 executes the computer-executable instructions to implement the above-described method.

[0079] exist Figure 5 In the illustrated embodiment, the server further includes a bus 52 and a communication interface 53, wherein the processor 51, the communication interface 53, and the memory 50 are connected via the bus 52.

[0080] The memory 50 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 53 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 52 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 52 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0081] Processor 51 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 51 or by instructions in software form. Processor 51 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. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor 51 reads the information in the memory and uses its hardware to complete the aforementioned method.

[0082] The computer program product of the automatic traceability pricing execution method, apparatus and server provided in the embodiments of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0083] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0084] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0085] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0086] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0087] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method of automatically tracing execution of a pricing, characterized by, A back pricing process for internal funds transfer pricing, comprising: obtaining pre-set information dimensions; wherein the information dimensions comprise at least one of the following dimensions: subject, institution, currency, pricing unit, interest rate type, data date, interest start date, expiration date, system source; filtering FTP accounts meeting the information dimensions from an account database based on the information dimensions; performing deduplication processing on the filtered FTP accounts to obtain a back account range containing at least one of the FTP accounts; pulling pricing result data of the day before the back date to a pricing result table for backtracking according to the back account range, and pulling position data of the day of the back date and placing the position data in a pre-set position data table according to the back account range, wherein the back account range comprises a plurality of FTP accounts; starting a pricing task engine to calculate the number of backtracking times of each FTP account within the back date range according to a pre-set back date range and the back account range; submitting a backtracking pricing task corresponding to each backtracking time to a pre-set pricing engine in sequence through the pricing task engine, so that the pricing engine performs backtracking pricing calculation, wherein the backtracking pricing task carries the pricing result table and the position data table; obtaining a pricing completion result returned by the pricing engine to the pricing task engine, and updating the backtracking official table according to the pricing completion result.

2. The method of claim 1, wherein, The step of submitting a backtracking pricing task corresponding to each backtracking time to a pre-set pricing engine in sequence through the pricing task engine, so that the pricing engine performs backtracking pricing calculation, comprises: submitting a backtracking pricing task corresponding to each backtracking time to a Redis database through the pricing task engine, and distributing the backtracking pricing task to the pricing engine for backtracking pricing calculation through the Redis database; and receiving a completion result of each backtracking pricing calculation returned by the pricing engine through the pricing task engine, automatically sending a backtracking pricing task corresponding to the next backtracking time to the pricing engine until the backtracking pricing tasks corresponding to the backtracking times are all completed.

3. The method of claim 2, wherein, The method further comprises: starting a pre-set daemon thread if it is monitored that the Redis database distributes the backtracking pricing task to the pricing engine; monitoring whether the pricing engine completes the current backtracking pricing calculation task through the daemon thread, and returning a completion signal to the pricing task engine after the current backtracking pricing calculation task is completed, so that the pricing task engine submits a next backtracking pricing task to the Redis database.

4. The method of claim 3, wherein, The step of obtaining a pricing completion result returned by the pricing engine to the pricing task engine, comprises: obtaining a completion result of each backtracking pricing calculation returned by the pricing engine; merging the completion results of each backtracking pricing calculation to generate the pricing completion result.

5. The method of claim 1, wherein, The step of calculating the number of backtracking times of each FTP account within the back date range according to a pre-set back date range and the back account range, comprises: obtaining a trace start date and a trace end date included in the trace date range; determining the number of days included in the trace start date and the trace end date as the trace number of each FTP account included in the trace account range.

6. The method of claim 1, wherein, After pulling the position data of the trace date, the method further comprises: determining whether the position data needs repayment plan data, and if so, pulling the repayment plan data from the corresponding repayment plan history table of the position data to the repayment plan table in the position data table.

7. An apparatus for automatically tracing execution of a pricing, characterized by, A trace pricing process for internal funds transfer pricing, comprising: an obtaining module, configured to obtain preset information dimensions; wherein the information dimensions include at least one of the following dimensions: account, institution, currency, pricing unit, interest rate type, data date, interest start date, maturity date, system source; filter FTP accounts meeting the information dimensions from an account database based on the information dimensions; perform deduplication processing on the filtered FTP accounts to obtain a trace account range containing at least one FTP account; pull pricing result data of the day before the trace date to a pricing result table for trace according to the trace account range, and pull position data of the trace date and place the position data in a preset position data table according to the trace account range, wherein the trace account range includes a plurality of internal funds transfer pricing (FTP) accounts; a starting module, configured to start a pricing task engine, calculate the trace number of each FTP account in the trace date range according to a preset trace date range and the trace account range; a calculation module, configured to submit a trace pricing task corresponding to each trace number to a preset pricing engine in sequence through the pricing task engine, so that the pricing engine performs trace pricing calculation, wherein the trace pricing task carries the pricing result table and the position data table; an updating module, configured to obtain a pricing completion result returned by the pricing engine to the pricing task engine, and update the trace official table according to the pricing completion result.

8. A server, characterized by The computer readable storage medium stores a computer program, and the computer program is run on the processor to perform the steps of the method of any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is run on the processor to perform the steps of the method of any one of claims 1-6.

Images