Financial product transaction monitoring method and device and storage medium

Abstract

The invention relates to the technical field of timed transaction monitoring, and discloses a financial product transaction monitoring method and device and a storage medium, and the method comprises the steps: obtaining an execution result of a timed transaction task of a financial product; performing error code analysis according to the execution result to obtain target error code information; and performing abnormity monitoring according to the target error code information to obtain an abnormity reason so as to realize abnormity monitoring of financial product timing transaction. According to the invention, the monitoring efficiency and accuracy of the abnormal transaction of the financial product can be effectively improved.

Description

Technical Field

[0001] The present application relates to the technical field of timed transaction monitoring, and in particular to a method, device and storage medium for monitoring financial product transactions. Background Art

[0002] For the fund fixed investment and bulk purchase business, the background processing procedures are relatively complex and connected to multiple business systems. Some unknown errors may occur during the execution of the program, resulting in the process not ending normally, or some unknown error causes, affecting the correct development of the business. Therefore, testers need to find problems in the business system in a timely manner to ensure business quality. However, the cost of manual monitoring is high, and it is necessary to log in to the system every day to check the results. The transaction volume is large, and there are hundreds of errors a day. The efficiency of identifying error codes that need to be analyzed is low, and it cannot automatically notify the analysis, which is easy to be untimely and missed. The monitoring work is urged by a dedicated person and weekly reports are issued. Fragmented work interferes with the work rhythm and cannot form fixed constraints. In addition, there are some scenarios that cannot be reached in the automation case, which makes it impossible to timely discover and efficiently analyze some problems through the automation case, resulting in poor monitoring efficiency and accuracy of abnormal transactions of financial products.

[0003] Therefore, how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products is a problem that needs to be solved urgently.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a financial product transaction monitoring method, device and storage medium, aiming to solve the technical problem of how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products.

[0006] To achieve the above objectives, the present application proposes a method for monitoring financial product transactions, the method comprising:

[0007] Get the execution results of scheduled trading tasks of financial products;

[0008] Perform error code analysis according to the execution result to obtain target error code information;

[0009] Exception monitoring is performed according to the target error code information to obtain the cause of the exception, so as to realize the exception monitoring of the scheduled transaction of the financial product.

[0010] In one embodiment, the step of obtaining the execution result of the scheduled transaction task of the financial product includes:

[0011] Obtaining a first execution status of a scheduled transaction task of a financial product at a first moment and a second execution status at a second moment;

[0012] An execution result of the scheduled transaction task of the financial product is determined according to the first execution status and the second execution status.

[0013] In one embodiment, determining the execution result of the scheduled transaction task of the financial product according to the first execution status and the second execution status includes:

[0014] When both the first execution situation and the second execution situation are incomplete, determining that the execution result is that the scheduled transaction task is incomplete;

[0015] When the first execution status is that the execution is not completed and the second execution status is that the execution is completed, or when the first execution status is that the execution is completed, it is determined that the execution result is that the scheduled transaction task has been completed.

[0016] In one embodiment, performing error code analysis according to the execution result to obtain target error code information includes:

[0017] When the execution result is that the scheduled transaction task has been completed, obtaining the update date of each error code information in the database;

[0018] The error code information is analyzed according to the update date of each error code information to obtain the target error code information.

[0019] In one embodiment, performing error code analysis according to the update date of each error code information to obtain target error code information includes:

[0020] Perform error code analysis according to the update date of each error code information and the specific content of each error code information to obtain reference error code information;

[0021] The reference error code information is deduplicated to obtain target error code information.

[0022] In one embodiment, performing abnormal monitoring according to the target error code information to obtain the abnormal cause includes:

[0023] Get the error code information whitelist;

[0024] Exception monitoring is performed according to the error code information whitelist and the target error code information to obtain the cause of the exception.

[0025] In one embodiment, performing abnormal monitoring according to the error code information whitelist and the target error code information to obtain the abnormal cause includes:

[0026] Matching the target error code information with the error code information in the error code information whitelist to obtain a matching result;

[0027] When the matching result is that there is no matching error code information, the target error code information is monitored for abnormalities to obtain the abnormal reason for the scheduled transaction of the financial product.

[0028] In one embodiment, after obtaining the execution result of the scheduled transaction task of the financial product, the method further includes:

[0029] When the first execution status is that the execution is not completed, a message notification is sent to the user and the incomplete information is registered in the database, so that the user processes the message notification and feeds back reply information according to a preset template, and the database is updated according to the reply information;

[0030] When both the first execution status and the second execution status are incomplete, sending a message notification to the user and updating the inspection record;

[0031] When the first execution status is that the execution is completed, a message notification is sent to the user and completion information is registered in the database.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a financial product transaction monitoring device, the financial product transaction monitoring device comprising:

[0033] An acquisition module is used to acquire the execution result of the scheduled transaction task of the financial product;

[0034] An analysis module, used to perform error code analysis according to the execution result to obtain target error code information;

[0035] The monitoring module is used to perform abnormal monitoring according to the target error code information and obtain the abnormal cause to realize abnormal monitoring of scheduled transactions of financial products.

[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a financial product transaction monitoring device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the financial product transaction monitoring method described above.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the financial product transaction monitoring method described above are implemented.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the financial product transaction monitoring method described above are implemented.

[0039] The present application provides a method for monitoring transactions of financial products. The present application first obtains the execution result of a scheduled transaction task of a financial product; performs error code analysis based on the execution result to obtain target error code information; performs abnormality monitoring based on the target error code information to obtain the cause of the abnormality, so as to realize abnormal monitoring of scheduled transactions of financial products, and can effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products.

[0040] In summary, the present application can simply and efficiently determine the target error code information by performing error code analysis based on the execution results of the scheduled trading tasks of financial products, thereby performing abnormal monitoring of scheduled transactions of financial products, overcoming the technical defects of poor monitoring efficiency and accuracy of abnormal transactions of financial products, and can effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0043] Figure 1 A flowchart of the first embodiment of the financial product transaction monitoring method of the present application is provided;

[0044] Figure 2 The overall flow chart provided for the first embodiment of the financial product transaction monitoring method of the present application;

[0045] Figure 3 A flowchart of the second embodiment of the financial product transaction monitoring method of the present application is provided;

[0046] Figure 4 This is a schematic diagram of the module structure of the financial product transaction monitoring device according to an embodiment of the present application;

[0047] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the financial product transaction monitoring method of the embodiment of the present application.

[0048] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0049] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0050] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0051] The main solution of the embodiment of the present application is: obtaining the execution result of the scheduled transaction task of the financial product; performing error code analysis based on the execution result to obtain target error code information; performing exception monitoring based on the target error code information to obtain the cause of the exception, so as to realize exception monitoring of the scheduled transaction of the financial product.

[0052] For the fund fixed investment and bulk purchase business, the background processing procedures are relatively complex and connected to multiple business systems. Some unknown errors may occur during the execution of the program, resulting in the process not ending normally, or some unknown error causes, affecting the correct development of the business. Therefore, testers need to find problems in the business system in a timely manner to ensure the quality of the business. However, the cost of manual monitoring is high, and it is necessary to log in to the system every day to check the results. The transaction volume is large, and there are hundreds of errors a day. The efficiency of identifying error codes that need to be analyzed is low, and it cannot automatically notify the analysis, which is easy to be untimely and missed. The monitoring work is urged by a dedicated person and weekly reports are issued. Fragmented work interferes with the work rhythm and cannot form fixed constraints. In addition, there are some scenarios that cannot be reached in the automation case, which makes it impossible to timely discover and efficiently analyze some problems through the automation case, resulting in poor monitoring efficiency and accuracy of abnormal transactions of financial products. Therefore, how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products is a problem that needs to be solved urgently.

[0053] The present application performs error code analysis based on the execution results of the scheduled trading tasks of financial products, and can simply and efficiently determine the target error code information, thereby performing abnormal monitoring of the scheduled trading of financial products, overcoming the technical defects of poor monitoring efficiency and accuracy of abnormal trading of financial products, and can effectively improve the monitoring efficiency and accuracy of abnormal trading of financial products.

[0054] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a financial product transaction monitoring device, etc. The following takes the financial product transaction monitoring device as an example to illustrate this embodiment and the following embodiments.

[0055] Based on this, the present application embodiment provides a financial product transaction monitoring method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the financial product transaction monitoring method of the present application.

[0056] In this embodiment, the financial product transaction monitoring method includes steps S10 to S30:

[0057] Step S10, obtaining the execution result of the scheduled transaction task of the financial product.

[0058] It should be noted that financial products refer to tools used to increase the value of assets, including but not limited to stocks, bonds, funds, futures, options, etc. This embodiment does not impose specific restrictions on this. This embodiment uses funds as an example for explanation. A fund is a collective investment tool that allows investors to jointly invest in a series of assets by purchasing fund shares. The management of the fund is usually the responsibility of professional fund managers, who perform asset allocation and management according to established investment strategies.

[0059] It can be understood that a scheduled trading task refers to a trading instruction that is automatically executed at a specific time point, for example, automatically buying or selling a certain number of fund units at a specific time on each working day, which is also called fund fixed investment. Fund fixed investment is the abbreviation of regular fixed amount investment fund, which means investing a fixed amount (such as 500 yuan) in a designated open-end fund at a fixed time (such as the 8th of each month).

[0060] In a feasible implementation, step S10 may include: obtaining a first execution status of the scheduled transaction task of the financial product at a first moment and a second execution status at a second moment; and determining an execution result of the scheduled transaction task of the financial product according to the first execution status and the second execution status.

[0061] It should be noted that in this embodiment, the fixed investment system monitoring content is divided into two stages through the scheduled task program, and the scheduled tasks are triggered at the first moment and the second moment respectively. The first moment can be 8:00 and the second moment can be 14:00. This embodiment does not impose specific restrictions on this.

[0062] It is understandable that the execution of the scheduled trading task at different times can be compared and analyzed to evaluate the execution effect of the scheduled trading task. For example, if the execution at the first moment shows that the fund fixed investment successfully purchased the predetermined number of fund units, and the execution at the second moment shows that no transaction occurred or the purchase quantity did not meet the expectation, then it can be determined that the scheduled trading task was completed at the first moment, but not completed at the second moment. The execution result of the financial product scheduled trading task on the day can be determined based on the execution of the scheduled trading task at different times.

[0063] In the specific implementation, the scheduled task program of the fund fixed investment batch purchase program of the fixed investment system is monitored to see whether it is completed. The monitoring is mainly carried out by calling the existing interface (to determine whether the program of the day has been executed), and judging whether the fixed investment execution task of the day has been completed according to whether the interface outputs the completion mark, that is, the execution result of the scheduled trading task.

[0064] In a feasible implementation manner, determining the execution result of the scheduled trading task of the financial product based on the first execution status and the second execution status includes: when the first execution status and the second execution status are both incomplete execution, determining that the execution result is incomplete execution of the scheduled trading task; when the first execution status is incomplete execution and the second execution status is completed execution, or the first execution status is completed execution, determining that the execution result is completed timing The transaction task.

[0065] It should be noted that, in this embodiment, two scheduled tasks are set every day, that is, fund fixed investment is automatically performed at the first moment and the second moment, and whether the scheduled trading task of the day is completed is determined based on the execution status of the two fixed investment tasks.

[0066] It is understandable that if both the first and second scheduled tasks of the day are not completed, that is, when both the first execution situation and the second execution situation are not completed, the scheduled trading task of the day is deemed to be incomplete. On the contrary, if the first scheduled task is not completed but the second scheduled task is completed, or as long as the first scheduled task is completed, then the scheduled trading task can be deemed to be completed. This mechanism ensures that the execution of the scheduled trading tasks of financial products can be evaluated in a timely and accurate manner, thereby providing investors with more reliable fixed investment services.

[0067] In the specific implementation, if the first scheduled task of the day is not completed, a message notification is sent to the test leader and a message is registered in the database. After processing, the test leader replies to the message notification according to the template, and the reply message will fall into the database. If both the first and second scheduled tasks of the day are not completed, the message will continue to be sent to the test leader, and the inspection record of the day will be updated. If the first scheduled task of the day is not completed, but the second scheduled task is completed, the second stage will be entered to check whether the error code information exists in the whitelist. If the first scheduled task of the day is completed, a message notification is sent to the test leader and a completed message is registered in the database, and then the second stage will be entered to check whether the error code information exists in the whitelist.

[0068] In one embodiment, after step S10, it also includes: when the first execution situation is incomplete execution, sending a message notification to the user and registering the incomplete information in the database, so that the user processes according to the message notification and feedback reply information according to a preset template, and updating the database according to the reply information; when the first execution situation and the second execution situation are both incomplete execution, sending a message notification to the user and updating the inspection record; when the first execution situation is completed execution, sending a message notification to the user and registering the completed information in the database.

[0069] It should be noted that if it is not completed for the first time on the day, a message notification will be sent to the test leader and an unfinished information will be registered in the database. After processing, the test leader will reply to the message notification according to the preset template. The reply message will fall into the database. The preset template can be "[Reason why the fund fixed investment bulk purchase program is not completed]: XXX". Message notification, for example, XX environment sub-database AAAAAAA, the fund fixed investment bulk purchase program is not completed on the day, please analyze the reason in time and re-execute the program. After completion, please reply in the following format, [Reason why the fund fixed investment bulk purchase program is not completed]: XXX. Reply information fed back by users, for example, [Reason why the fund fixed investment bulk purchase program is not completed]: The downstream CCC system is abnormal, causing the program to be blocked and unable to end normally.

[0070] It is understandable that if the first and second tasks of the day are not completed, continue to send messages to the test leader and update the inspection records of the day. For example, XX environment sub-database AAAAAAA, the fund fixed investment bulk purchase procedure of the day, the second monitoring results are still not completed, please analyze the reasons in time.

[0071] It is worth mentioning that if the test is completed for the first time on the day, a message will be sent to the test leader and a completed message will be registered in the database.

[0072] Step S20, performing error code analysis according to the execution result to obtain target error code information.

[0073] It should be noted that error code analysis includes classifying and identifying error information generated during the execution of financial product scheduled trading tasks to obtain target error code information. Error information may include unsuccessful transactions, insufficient funds, network connection failure, etc.

[0074] In a feasible implementation, step S20 may include: when the execution result is that the scheduled transaction task has been completed, obtaining the update date of each error code information in the database; performing error code analysis according to the update date of each error code information to obtain target error code information.

[0075] It should be noted that, according to the update date of each error code information, the records with the update date of the day are queried from the database, and the target error code information is determined therefrom.

[0076] It is understandable that the error code information updated on the same day can reflect the latest transaction status, and thus can quickly identify the error codes that may affect the execution of transactions, and record and report them as target error code information.

[0077] In a feasible implementation manner, the error code analysis is performed according to the update date of each error code information to obtain target error code information, including: performing error code analysis according to the update date of each error code information and the specific content of each error code information to obtain reference error code information; deduplicating the reference error code information to obtain target error code information.

[0078] It should be noted that the records whose update date is today and whose specific content of error code information is unsuccessful are queried from the database, and their corresponding error code information is used as reference error code information, and then deduplication processing is performed, so as to effectively improve the accuracy of the target error code information.

[0079] It can be understood that deduplication refers to filtering repeated error code information to ensure that each error code is recorded only once, avoiding analysis confusion caused by repeated error information. Through this process, the accuracy and reliability of error code analysis results can be ensured, providing effective data support for subsequent error processing and system optimization.

[0080] In the specific implementation, during the deduplication process, all error code information is sorted according to the update time point to ensure that the latest error code information is at the front. Then, by comparing adjacent error code information, if the content is found to be the same, the duplicate error code information is deleted and only one is retained. In this way, it can be ensured that the target error code information does not contain duplicate error codes, thereby improving the accuracy and efficiency of error code analysis. The target error code information after deduplication processing is recorded in the database, and a detailed error code analysis report is generated. The report not only contains the target error code information, but also includes the frequency of occurrence of the error code, the number of transactions affected and other key indicators, so that the test leader and relevant team members can quickly understand the current transaction task execution status and existing problems. In this way, the stability and reliability of the scheduled trading tasks of financial products can be effectively improved.

[0081] Step S30, performing abnormal monitoring according to the target error code information to obtain the abnormal cause, so as to realize abnormal monitoring of scheduled transactions of financial products.

[0082] It should be noted that by receiving and processing the target error code information from the database in real time, the error code information is analyzed according to the preset rules and logic to identify potential abnormal patterns and trends. The frequency and distribution of error code information and their correlation with transaction execution are analyzed in real time. In this way, abnormal trading behavior can be quickly discovered, such as frequently occurring error codes, sudden increases in error codes, or abnormal patterns within a specific time period. It can also be combined with other data sources, such as transaction volume, user behavior data, etc., for comprehensive analysis to more fully understand the cause of the abnormality. For example, if an error code appears at the same time as a specific transaction volume peak or abnormal user behavior, the monitoring system will be able to identify potential system vulnerabilities or external attacks.

[0083] It is understandable that after identifying the cause of the abnormality, an abnormality report is generated and the relevant test leader and team members are notified in a timely manner. The report will describe the abnormal situation in detail, including the abnormal error code, occurrence time, possible impact range, and recommended response measures. According to the results of the abnormality report, the monitoring strategy and rules are automatically adjusted to adapt to the changing trading environment and potential risks. In this way, continuous optimization can be achieved to improve the ability to identify and respond to abnormal situations, thereby ensuring the stability and security of the scheduled trading tasks of financial products.

[0084] like Figure 2 As shown, Figure 2 This is the overall flow chart of financial product transaction monitoring. It determines whether the batch purchase procedure of the day has been completed according to the scheduled task. If completed, it determines whether there is an error code that is not in the whitelist. If so, it registers the database error code information and sends a pending message notification. If not, it registers the database batch completion information of the day and sends a message notification. If not completed, it registers the database failure of the day, sends a message notification that needs to be analyzed, and initiates the check again.

[0085] The present embodiment provides a financial product transaction monitoring method. The present embodiment first obtains the execution result of the scheduled transaction task of the financial product; performs error code analysis according to the execution result to obtain target error code information; performs abnormality monitoring according to the target error code information to obtain the cause of the abnormality, so as to realize abnormal monitoring of the scheduled transaction of the financial product, and can effectively improve the monitoring efficiency and accuracy of abnormal transactions of the financial product.

[0086] In summary, this embodiment can determine the target error code information simply and efficiently by performing error code analysis based on the execution results of the scheduled trading tasks of the financial products, thereby performing abnormal monitoring of the scheduled transactions of the financial products, overcoming the technical defects of poor monitoring efficiency and accuracy of abnormal transactions of financial products, and can effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products.

[0087] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , the step S30 further includes steps S301-S302:

[0088] Step S301, obtaining an error code information whitelist.

[0089] It should be noted that the error code information whitelist is a mechanism for distinguishing normal from abnormal behaviors. It contains a series of error codes that are deemed harmless or expected. By maintaining such a whitelist, the monitoring system can filter out common error codes that do not require attention, thereby reducing false alarms and focusing on abnormal behaviors that really require attention.

[0090] It is understandable that the error code information whitelist is pre-configured and stored in the database. The error code information contained in the error code information whitelist can be updated regularly to adapt to changes in the financial product trading environment. For example, when new financial products are launched or the trading rules of existing products change, the corresponding error code information also needs to be adjusted. In this way, the monitoring system can continue to maintain adaptability to new situations and ensure the accuracy and effectiveness of monitoring.

[0091] Step S302: perform abnormal monitoring according to the error code information whitelist and the target error code information to obtain the abnormal cause.

[0092] It should be noted that each target error code information is looped through in turn and compared with each entry in the error code information whitelist to determine whether there is a match. If a match is found, it indicates that the error code is within the normal range and no further processing is required. On the contrary, if no match is found, it indicates that the error code is abnormal and further analysis and processing are required to determine the cause of the abnormality.

[0093] It is understandable that, according to the abnormal reason obtained, corresponding abnormal handling measures are executed. This may include but is not limited to recording logs, sending alarm notifications, automatically restarting services, or executing specific fault recovery procedures. Through these measures, the impact of system failures on business can be effectively reduced to ensure the stable operation of the system.

[0094] In a feasible implementation, step S301 may include: matching the target error code information with the error code information in the error code information whitelist to obtain a matching result; when the matching result is that there is no matching error code information, performing abnormal monitoring on the target error code information to obtain the abnormal cause of the scheduled transaction of the financial product.

[0095] It should be noted that preliminary screening can be performed by determining whether the target error code information is in the error code information whitelist, which can quickly exclude those common, known normal error codes and improve the efficiency of anomaly detection. The error code information whitelist is usually maintained and updated by system administrators or maintenance personnel based on historical data and experience to ensure that it contains all error codes that may occur under normal circumstances.

[0096] It is understandable that once it is determined that the target error code does not belong to the whitelist, it is considered to be an abnormal situation, and the abnormal monitoring mechanism will be automatically triggered. During the abnormal monitoring process, various log information and operation data related to the target error code are collected to analyze the root cause of the problem. For example, the system may record the system status, user operation records, network status and other information when the target error code occurs. These data will be sent to the analysis module to find possible abnormal patterns or known error cases through data mining and pattern recognition technology.

[0097] It is worth noting that in some cases, machine learning algorithms may be used to classify and predict current abnormal situations based on models trained with historical abnormal data. In this way, the system can more intelligently identify the cause of the abnormality and give corresponding treatment suggestions or automatically perform some repair measures. In addition, the abnormality monitoring module can also be integrated with the monitoring platform of the system administrator or maintenance personnel. When an abnormal situation is detected, the system will automatically send an alarm to notify the relevant personnel. In this way, even when the system automatically handles the abnormality, it can ensure that professionals intervene to deal with complex situations that require manual intervention.

[0098] It is worth noting that in this application, for the scenario where the fund fixed investment batch purchase program process has not ended, a scheduled task is initiated to determine whether the program state has reached the final state. If it has not reached the final state, a notification is sent to the test person in charge through a communication tool, which can timely discover problems and save manual time required to log in to the system every day to check. For failure scenarios that occur during program execution, the error code information is identified to determine whether the error code information is known. If the error code information is not in the error code whitelist, a notification is sent to the test person in charge through a communication tool to promptly remind the test person in charge to analyze and give a conclusion, and automatically register the conclusion in the database file, which can solve the problems of large amounts of data, low accuracy and low efficiency in manually identifying error codes.

[0099] In this embodiment, by performing abnormal monitoring based on the error code information whitelist and the target error code information, the cause of the transaction abnormality can be quickly and accurately located, and the monitoring efficiency and accuracy of abnormal transactions of financial products can be effectively improved.

[0100] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the financial product transaction monitoring method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0101] This application also provides a financial product transaction monitoring device, please refer to Figure 4 , the financial product transaction monitoring device comprises:

[0102] The acquisition module 10 is used to acquire the execution result of the scheduled transaction task of the financial product.

[0103] The analysis module 20 is used to perform error code analysis according to the execution result to obtain target error code information.

[0104] The monitoring module 30 is used to perform abnormal monitoring according to the target error code information and obtain the abnormal cause to achieve abnormal monitoring of scheduled transactions of financial products.

[0105] The present embodiment provides a financial product transaction monitoring device. The present embodiment obtains the execution result of the scheduled transaction task of the financial product; performs error code analysis based on the execution result to obtain target error code information; performs abnormality monitoring based on the target error code information to obtain the cause of the abnormality, so as to realize abnormal monitoring of the scheduled transaction of the financial product, which can effectively improve the monitoring efficiency and accuracy of abnormal transactions of the financial product.

[0106] In summary, this embodiment can determine the target error code information simply and efficiently by performing error code analysis based on the execution results of the scheduled trading tasks of the financial products, thereby performing abnormal monitoring of the scheduled transactions of the financial products, overcoming the technical defects of poor monitoring efficiency and accuracy of abnormal transactions of financial products, and can effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products.

[0107] Optionally, the acquisition module 10 is further used to acquire a first execution status of the scheduled transaction task of the financial product at a first moment and a second execution status at a second moment; and determine an execution result of the scheduled transaction task of the financial product according to the first execution status and the second execution status.

[0108] Optionally, the acquisition module 10 is further used to determine that the execution result is that the scheduled transaction task is not completed when the first execution situation and the second execution situation are both incomplete execution; when the first execution situation is incomplete execution and the second execution situation is completed execution, or the first execution situation is completed execution, determine that the execution result is that the scheduled transaction task is completed.

[0109] Optionally, the analysis module 20 is further configured to obtain an update date of each error code information in the database when the execution result is that the scheduled transaction task has been completed; perform error code analysis according to the update date of each error code information to obtain target error code information.

[0110] Optionally, the analysis module 20 is further used to perform error code analysis according to the update date of each error code information and the specific content of each error code information to obtain reference error code information; and perform deduplication processing on the reference error code information to obtain target error code information.

[0111] Optionally, the monitoring module 30 is further used to obtain an error code information whitelist; perform abnormality monitoring according to the error code information whitelist and the target error code information to obtain the cause of the abnormality.

[0112] Optionally, the monitoring module 30 is also used to match the target error code information with the error code information in the error code information whitelist to obtain a matching result; when the matching result is that there is no matching error code information, the target error code information is monitored for abnormalities to obtain the abnormal cause of the scheduled transaction of the financial product.

[0113] Optionally, the acquisition module 10 is also used to send a message notification to the user and register the incomplete information in the database when the first execution status is incomplete, so that the user can process according to the message notification and feedback reply information according to a preset template, and update the database according to the reply information; when the first execution status and the second execution status are both incomplete, send a message notification to the user and update the inspection record; when the first execution status is completed, send a message notification to the user and register the completed information in the database.

[0114] The financial product transaction monitoring device provided by the present application adopts the financial product transaction monitoring method in the above embodiment, which can solve the technical problem of how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products. Compared with the prior art, the beneficial effects of the financial product transaction monitoring device provided by the present application are the same as the beneficial effects of the financial product transaction monitoring method provided by the above embodiment, and the other technical features in the financial product transaction monitoring device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0115] The present application provides a financial product transaction monitoring device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the financial product transaction monitoring method in the above-mentioned embodiment one.

[0116] Reference below Figure 5 , which shows a schematic diagram of the structure of a financial product transaction monitoring device suitable for implementing the embodiment of the present application. The financial product transaction monitoring device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The financial product transaction monitoring device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0117] like Figure 5 As shown, the financial product transaction monitoring device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the financial product transaction monitoring device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the financial product transaction monitoring device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a financial product transaction monitoring device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0118] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0119] The financial product transaction monitoring device provided by the present application adopts the financial product transaction monitoring method in the above embodiment, which can solve the technical problem of how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products. Compared with the prior art, the beneficial effects of the financial product transaction monitoring device provided by the present application are the same as the beneficial effects of the financial product transaction monitoring method provided by the above embodiment, and the other technical features in the financial product transaction monitoring device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0120] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0121] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0122] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the financial product transaction monitoring method in the above-mentioned embodiment.

[0123] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0124] The computer-readable storage medium may be included in the financial product transaction monitoring device; or may exist independently without being assembled into the financial product transaction monitoring device.

[0125] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the financial product transaction monitoring device, the financial product transaction monitoring device: obtains the execution result of the scheduled transaction task of the financial product; performs error code analysis based on the execution result to obtain target error code information; performs exception monitoring based on the target error code information to obtain the cause of the exception, so as to realize exception monitoring of the scheduled transaction of the financial product.

[0126] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0127] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0128] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0129] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned financial product transaction monitoring method, and can solve the technical problem of how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the financial product transaction monitoring method provided in the above-mentioned embodiment, and will not be repeated here.

[0130] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned financial product transaction monitoring method when executed by a processor.

[0131] The computer program product provided by this application can solve the technical problem of how to effectively improve the monitoring efficiency and accuracy of abnormal transactions of financial products. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the financial product transaction monitoring method provided by the above embodiment, which will not be repeated here.

[0132] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A financial product transaction monitoring method, characterized in that: The method comprises: Get the execution results of scheduled trading tasks of financial products; Perform error code analysis according to the execution result to obtain target error code information; Exception monitoring is performed according to the target error code information to obtain the cause of the exception, so as to realize the exception monitoring of the scheduled transaction of the financial product.

2. The method according to claim 1, characterized in that The execution result of the timed transaction task of obtaining the financial product includes: Obtaining a first execution status of a scheduled transaction task of a financial product at a first moment and a second execution status at a second moment; An execution result of the scheduled transaction task of the financial product is determined according to the first execution status and the second execution status.

3. The method according to claim 2, characterized in that The determining the execution result of the scheduled transaction task of the financial product according to the first execution condition and the second execution condition includes: When both the first execution situation and the second execution situation are incomplete, determining that the execution result is that the scheduled transaction task is incomplete; When the first execution status is that the execution is not completed and the second execution status is that the execution is completed, or when the first execution status is that the execution is completed, it is determined that the execution result is that the scheduled transaction task has been completed.

4. The method according to claim 1, characterized in that The performing error code analysis according to the execution result to obtain target error code information includes: When the execution result is that the scheduled transaction task has been completed, obtaining the update date of each error code information in the database; The error code information is analyzed according to the update date of each error code information to obtain the target error code information.

5. The method according to claim 4, characterized in that The error code analysis is performed according to the update date of each error code information to obtain the target error code information, including: Perform error code analysis according to the update date of each error code information and the specific content of each error code information to obtain reference error code information; The reference error code information is deduplicated to obtain target error code information.

6. The method according to claim 1, characterized in that The abnormality monitoring is performed according to the target error code information to obtain the abnormality cause, including: Get the error code information whitelist; Exception monitoring is performed according to the error code information whitelist and the target error code information to obtain the cause of the exception.

7. The method according to claim 6, characterized in that The performing abnormal monitoring according to the error code information whitelist and the target error code information to obtain the abnormal cause includes: Matching the target error code information with the error code information in the error code information whitelist to obtain a matching result; When the matching result is that there is no matching error code information, the target error code information is monitored for abnormalities to obtain the abnormal reason for the scheduled transaction of the financial product.

8. The method according to claim 1, characterized in that After obtaining the execution result of the scheduled transaction task of the financial product, the method further includes: When the first execution status is that the execution is not completed, a message notification is sent to the user and the incomplete information is registered in the database, so that the user processes the message notification and feeds back reply information according to a preset template, and the database is updated according to the reply information; When both the first execution status and the second execution status are incomplete, sending a message notification to the user and updating the inspection record; When the first execution status is that the execution is completed, a message notification is sent to the user and completion information is registered in the database.

9. A financial product transaction monitoring device, characterized in that: The financial product transaction monitoring device comprises: An acquisition module is used to acquire the execution result of the scheduled transaction task of the financial product; An analysis module, used to perform error code analysis according to the execution result to obtain target error code information; The monitoring module is used to perform abnormal monitoring according to the target error code information and obtain the abnormal cause to realize abnormal monitoring of scheduled transactions of financial products.

10. A storage medium, characterized in that: The storage medium stores a financial product transaction monitoring program, and when the financial product transaction monitoring program is executed by the processor, the financial product transaction monitoring method according to any one of claims 1 to 7 is implemented.

Images