Order monitoring method, system and equipment
Through real-time query and polling order status and generating alarm information, the order monitoring method is solved, and the unilateral account problem in financial transactions is inefficient and insufficient accuracy, automatic comparison is realized, transaction consistency and confirmation efficiency are improved, and transaction consistency and confirmation efficiency are reduced. operating costs and compliance risks.
Patent Information
- Application Number
- CN202410961837.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2024-11-08
AI Technical Summary
When handling unilateral accounting problems in financial transactions, the existing technology relies on manual verification, which is low efficiency, low accuracy, high resource consumption, and has compliance risks. It is difficult to deal with it in a timely manner when the transaction volume is large and the data is complex. , affecting the normal operation of the business.
Provide an order monitoring method, by querying the order status in real time, polling with preset frequency when the final status of the order is not obtained, and alarm information is generated, automatic comparison process, improve the confirmation efficiency of unilateral accounts, and promptly detect order abnormalities. Condition.
It realizes an automated comparison process, improves the confirmation efficiency of unilateral accounts, reduces manual intervention, improves transaction consistency and accuracy, and reduces operating costs and compliance risks.
Smart Images

Figure CN118917853A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an order monitoring method, system and device. Background Art
[0002] In financial transactions, especially payment, transfer, and other fund transfers involving both borrowers and lenders, ensuring the integrity and consistency of transactions is crucial. The problem of one-sided accounts, that is, the situation in which only one party successfully processes the transaction while the other party fails to successfully process it, will bring serious financial and reputation risks.
[0003] At present, the confirmation method for unilateral accounts is usually to manually check the bank system against the accounting data details of its own system background based on the reconciliation documents one by one. When there is an inconsistency, this part of the data is recorded as a unilateral account. First, the staff needs to collect transaction data from various systems involved in the transaction. Then, the staff uses software tools or manual operations to compare the collected data to find any mismatched or missing transaction records. Once a potential unilateral account is found (that is, a transaction that one party has a record but the other party does not), the staff will further review the detailed information of these transactions, including the transaction background, information of both parties to the transaction, transaction time, etc., to confirm whether a unilateral account really exists. Manual comparison and review of transaction data is a time-consuming process, especially when the transaction volume is large and the data is complex, and the efficiency of manual processing is low. Summary of the invention
[0004] Based on the above problems, the present application provides an order monitoring method, system and device to realize automated order monitoring and improve monitoring efficiency.
[0005] To solve the above problems, the technical solutions provided in the embodiments of the present application are as follows:
[0006] The first aspect of the present application provides an order monitoring method, comprising:
[0007] Query the order status of the target order in real time;
[0008] In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency, wherein the final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate querying the final status of the order once every first preset time;
[0009] In response to failure to query the final status of the order under preset conditions, a first warning message is generated.
[0010] In a possible implementation, in response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency includes:
[0011] In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency after a second preset time.
[0012] In a possible implementation, in response to failure to query the final status of the order under a preset condition, generating the first warning information includes:
[0013] In response to failure to obtain the final status of the order within a third preset time, a first warning message is generated.
[0014] In a possible implementation, in response to failure to query the final status of the order under a preset condition, generating the first warning information includes:
[0015] In response to failure to obtain the final status of the order after a preset number of pollings, a first warning message is generated.
[0016] In a possible implementation, the method further includes:
[0017] An alarm record is generated based on the order status of the target order and the first alarm information.
[0018] In a possible implementation, the method further includes:
[0019] The first alarm information is pushed to the target personnel so that the target personnel analyze the target order.
[0020] In a possible implementation, the method further includes:
[0021] In response to obtaining the final status of the order, determining whether the target order transaction is successful based on the final status of the order.
[0022] In response to the target order transaction being unsuccessful, second warning information is generated.
[0023] In a possible implementation, the method further includes:
[0024] Obtain first-party transaction information and second-party transaction information;
[0025] Comparing the first party's transaction information with the second party's transaction information;
[0026] In response to the first-party transaction information and the second-party transaction information being inconsistent, third warning information is generated.
[0027] The second aspect of the present application provides an order monitoring system, comprising:
[0028] A first query unit, used for querying the order status of a target order in real time;
[0029] a polling unit, configured to, in response to failure to obtain the final status of the order, poll the final status of the order at a first preset frequency, wherein the final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate that the final status of the order is queried once every first preset time;
[0030] The first generating unit is used to generate a first warning message in response to failure to query the final status of the order under a preset condition.
[0031] The third aspect of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the order monitoring method described in the first aspect is implemented.
[0032] A fourth aspect of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device executes the order monitoring method as described in the first aspect above.
[0033] Compared with the prior art, this application has the following beneficial effects:
[0034] By querying the order status of the target order in real time; in response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency, and generating a first alarm message in response to failure to query the final status of the order under preset conditions. In order to improve the efficiency of real-time investigation and the accuracy of real-time monitoring, when the final status of the order is not obtained by calling the upstream transaction, an asynchronous polling mechanism is added. If the final status is not obtained after multiple pollings under preset conditions, it indicates that the current target order is abnormal, and an alarm message is generated to inform manual analysis. When the final status of the order is not obtained, the final status of the order is queried at a first preset frequency. If the final status of the order is not polled under preset conditions, it indicates that the execution of the current order is abnormal, and an alarm message is generated to enable immediate manual intervention. Compared with manual comparison of whether the order status is correct, the automated comparison process provided by this application can promptly discover abnormal conditions of the order and improve the confirmation efficiency of the unilateral account. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0036] Figure 1 A flowchart of an order monitoring method provided in an embodiment of the present application;
[0037] Figure 2 A schematic diagram of a second order monitoring process provided in an embodiment of the present application;
[0038] Figure 3 A schematic diagram of a third order monitoring process provided in an embodiment of the present application;
[0039] Figure 4 A structural diagram of an order monitoring system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0040] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0041] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the professional terms involved in the embodiments of the present application will be explained below.
[0042] Unilateral accounting is a term used in bank transaction processing, which usually occurs during the clearing and reconciliation of bank accounts. It refers to the situation in which, when comparing the reconciliation documents (such as settlement information from payment systems, clearing centers or other financial institutions) with the accounting data details in the backend of the bank's own system, it is found that the records of certain transactions in the two systems are inconsistent. This inconsistency may be caused by a variety of reasons, including but not limited to data transmission errors, system failures, human operational errors or external system delays.
[0043] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the background technology involved in the embodiments of the present application will be described below.
[0044] Payment transaction is a financial transaction process involving at least two parties, usually including a debit party (such as a payer or consumer) and a credit party (such as a payee or service provider). Such transactions are intended to achieve the transfer of funds or payment of services and are an indispensable part of daily economic activities.
[0045] Ideally, transactions should be instant, accurate, and completed synchronously by both parties. However, in actual operations, due to various uncontrollable factors, such as network timeouts, system anomalies, or technical failures, inconsistent processing results may occur between the two parties. When the transaction request of one party (such as the borrower) is successfully accepted and processed by the system, but the other party (such as the lender) fails to respond or confirm the transaction in time due to the above reasons, the so-called "one-sided account" is generated.
[0046] The emergence of unilateral accounts poses serious risks to both financial institutions and customers. From the perspective of capital risk, unilateral accounts may lead to the misallocation or retention of funds, which in turn affects the liquidity and security of funds. For example, the debit party may have successfully deducted the money, but the creditor has not received the corresponding amount, which will cause a shortage of funds; conversely, if the creditor mistakenly records the receipt of funds but the debit party does not actually pay, it may cause the problem of unjust enrichment.
[0047] In addition, unilateral accounts may also damage the reputation of financial institutions. Customers' trust in financial institutions is based on the security, accuracy and efficiency of transaction processing. If unilateral account problems occur frequently, customers may question the service quality and professional ability of financial institutions, which in turn affects their brand image and market share.
[0048] As mentioned above, despite the rapid development of technology, in many organizations, the processing of one-sided accounts still relies on manual verification, especially for complex transaction scenarios or systems. First, staff will compare transaction records between two or more systems to find mismatched or missing transaction information, i.e., one-sided accounts. Once a potential one-sided account is found, staff can review the details of the relevant transaction in depth, including timestamps, amounts, transaction types, etc., to confirm whether there is indeed a one-sided account problem.
[0049] However, there are some obvious limitations and challenges in manually checking and processing unilateral accounts:
[0050] Low efficiency: Manual processing is slow, especially when the transaction volume is large and the data is complex. It may be difficult to process all unilateral accounts in a timely manner, affecting the normal operation of the business.
[0051] Low accuracy: Manual processing is easily affected by personal judgment, fatigue and other factors, which may lead to wrong judgments or omissions.
[0052] High resource consumption: Continuous manual intervention requires a lot of time and human resources, increasing the operating costs of the enterprise.
[0053] Compliance risks exist: Manual processing may lack standardization and transparency, increasing compliance risks, especially in industries involving cross-border transactions or strict regulatory requirements.
[0054] In order to solve this problem, an order monitoring method is provided in an embodiment of the present application. The method is applied to the query and payment system provided in the present application. The query and payment system is described below:
[0055] The embodiment of the present application provides a fee inquiry and payment system that supports the inquiry and payment of various fees. A fee inquiry and payment system can be decomposed into multiple subsystems, each of which performs independent functions and assumes specific responsibilities, such as an order management system and an order monitoring system. In the event of anomalies, the upstream and downstream can ensure transaction consistency and reduce the generation of unilateral accounts. Transaction management is a key means to ensure data consistency. In a distributed system, especially in the scenario where the fee inquiry and payment system is decomposed into multiple subsystems, it is necessary to ensure that all related operations are either completed successfully or completely revoked (rolled back) when any errors are encountered.
[0056] Transaction management is the first line of defense to solve the problem of unilateral accounts. In transaction management, all related subsystems are designed to either complete the transaction in full or roll back to the initial state when an error occurs. This "all or nothing" principle ensures data consistency and integrity. If any subsystem fails during the transaction, the entire transaction will be rolled back, thus avoiding the generation of unilateral accounts. Through transaction management, the system can automatically handle most transaction anomalies caused by system failures or network problems.
[0057] The verification and confirmation mechanism is the key to ensure that transactions flow correctly in the system. During the transaction process, each subsystem will send a confirmation message to the next node that should process the transaction after completing its specific function. This mechanism not only ensures the correct order of transactions as they flow through the entire system, but also allows the system to verify at each stage to confirm the accuracy and completeness of the transaction data. If the verification fails or the confirmation message is not received, the system can take immediate measures, such as retrying the transaction or notifying relevant personnel to handle it, thereby further reducing the risk of unilateral accounts.
[0058] Although transaction management and verification and confirmation mechanisms can greatly reduce the occurrence of unilateral accounts, human intervention is still required in some complex or special cases. When the system detects abnormal transactions or transactions that cannot be processed automatically, it will be handed over to human analysis and processing. Human analysis can not only help solve complex problems that the system cannot handle automatically, but also continuously optimize and improve system performance and stability. Through human analysis, potential problems in the system can be discovered and corrected in a timely manner, thereby further improving the consistency of transactions and reducing the occurrence of unilateral accounts.
[0059] In the order monitoring scenario provided by the embodiment of the present application, based on the above-mentioned query and payment system, an order monitoring method provided by the present application queries the order status of the target order in real time; in response to failure to obtain the final status of the order, poll the final status of the order at a first preset frequency, and in response to failure to query the final status of the order under preset conditions, generate a first alarm message. That is, after each subsystem has completed the execution of the order, it can generate and send the final status of the order to the order monitoring system. The final status of the order is used to characterize whether the current order transaction is successful. Only after confirming that each subsystem has executed successfully can the subsequent process be executed. When the final status of the order is not obtained, the final status of the order is queried at a first preset frequency. If the final status of the order is not polled under the preset conditions, it means that there is an abnormality in the execution of the current order, and an alarm message is generated to allow manual intervention.
[0060] It should be noted that the order monitoring method, system and device provided in the present application can be applied to the field of computer technology. The above is only an example and does not limit the application field of the order monitoring method, system and device provided in the present application. In addition, the embodiment of the present application may not limit the execution subject of order monitoring. For example, the order monitoring method of the embodiment of the present application can be applied to data processing devices such as terminal devices or servers. Among them, the terminal device can be an electronic device such as a computer, a personal digital assistant (PDA), a tablet computer, etc. The server can be a stand-alone server, a cloud server, or a cluster server composed of multiple servers.
[0061] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0062] The following is an example of an order monitoring method provided by the present application. Figure 1 ,Should Figure 1 A flowchart of an order monitoring method provided in an embodiment of the present application, the method comprising:
[0063] S101. Query the order status of the target order in real time.
[0064] The order monitoring system can send a request to the order management system to obtain the current status of the specified target order. This can be done by calling the API of the order management system, which will return the latest status information of the order, including but not limited to whether the order has been received, being processed, completed or failed.
[0065] S102: In response to failure to obtain the final status of the order, poll the final status of the order at a first preset frequency.
[0066] The final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate that the final status of the order is queried once every first preset time.
[0067] If the initial query fails to return the final order status of the order (for example, the order is still being processed), the system will initiate a polling mechanism, which means that the system will periodically re-query the order status at a pre-set time interval (first pre-set frequency) until the final status is obtained.
[0068] The selection of the first preset frequency can be adaptively set and adjusted according to actual needs, such as balancing resource consumption and response time. The preset frequency can range from a few seconds to a few minutes, depending on business needs and system performance.
[0069] In a high-concurrency environment, you can use message queues or asynchronous task processing frameworks (such as RabbitMQ, Celery, etc.) to queue polling requests to avoid direct execution in the main application thread, thereby improving the system's response speed and stability.
[0070] S103: In response to failure to query the final status of the order under preset conditions, generate a first warning message.
[0071] If the final status of the order is still not obtained after the preset conditions are met, the system will generate and send an alarm message.
[0072] Failure to query the final status of an order indicates that there is a possibility of a unilateral account in the current target order. The system can generate an alarm message based on the relevant information of the target order, which can be sent to the operation and maintenance personnel or the development team so that they can intervene in time, investigate the cause of the problem and take appropriate measures. At the same time, the alarm message can also notify customers to let them know that their order status query has encountered temporary difficulties, thereby improving customer experience.
[0073] In a possible implementation, in response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency includes:
[0074] In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency after a second preset time.
[0075] When the final status of the order cannot be obtained in the first query, you can wait for the second preset time before polling again. By introducing an initial delay (the second preset time), it helps to avoid frequent queries during the order execution process, because the order status may not have been updated to the final status at this time. Frequent queries are not only invalid, but may also cause unnecessary system load.
[0076] The length of this time can be determined based on historical data analysis, that is, the approximate time required from order creation to the first queryable status. For example, if most orders enter the queryable status within 30 seconds after the start of execution, the second preset time can be set to 30 seconds or slightly longer than 30 seconds.
[0077] In an actual application scenario, if the final status of the order is still not obtained after the second preset time, the polling mechanism is started to query at the first preset frequency (for example, every 5 minutes).
[0078] If the final status cannot be obtained after several consecutive polling attempts, an exponential backoff strategy can be used, that is, the polling interval is gradually increased after each failure (for example, wait 5 minutes after the first failure, 10 minutes for the second, 20 minutes for the third, and so on) until a certain maximum value is reached. This can avoid issuing a large number of invalid requests in a short period of time and give the system more time to handle potential abnormal situations.
[0079] In a possible implementation, in response to failure to query the final status of the order under a preset condition, generating the first warning information includes:
[0080] In response to failure to obtain the final status of the order within a third preset time, a first warning message is generated.
[0081] The third preset time represents the upper limit of the waiting time that the system considers reasonable. If the final status of the order cannot be obtained within this time, it is considered that there is an abnormality in the current order and the first alarm information is generated. Through the above mechanism, it is possible to effectively monitor the abnormality of order status query, respond in time, reduce the negative impact caused by information lag, and improve the overall operation efficiency and service quality.
[0082] In a possible implementation, in response to failure to query the final status of the order under a preset condition, generating the first warning information includes:
[0083] In response to failure to obtain the final status of the order after a preset number of pollings, a first warning message is generated.
[0084] The preset polling times refers to the maximum number of attempts set by the system when checking the order status. Once this number is reached, if the final status of the order is still not obtained, it is considered an exception.
[0085] The setting of the preset polling times needs to consider multiple factors, including but not limited to the average time of order processing, the response speed of the system, network stability and business needs. For example, it can be determined through analysis of historical data and performance testing in actual operations, aiming to balance query efficiency and resource consumption.
[0086] See also Figure 2 , Figure 2 The second order monitoring process diagram provided for the embodiment of the present application is that when the final status of the target order cannot be queried for the first time, the system queries the order status at a predetermined time interval (e.g., every 10 minutes) until a preset number of polling times (e.g., 10 times) is reached. When the system completes all attempts for the preset number of polling times but still fails to successfully obtain the final status of the order, the condition for triggering the alarm is met. Once the above conditions are met, the system will automatically generate a first alarm message.
[0087] In a possible implementation, an alarm record may be generated based on the order status of the target order and the first alarm information, which generally includes key data such as order details, polling start time, end time, and completed polling times, so as to quickly locate the problem.
[0088] In a possible implementation, the method further includes:
[0089] The first alarm information is pushed to the target personnel so that the target personnel analyze the target order.
[0090] The alarm information can then be sent to the target personnel, that is, the relevant responsible persons or systems, such as the technical operation and maintenance team, customer service department or integrated alarm management platform, to ensure that the problem can be paid attention to and handled in a timely manner. After receiving the alarm information, the relevant processing personnel can quickly analyze the first alarm information, determine the possible causes (such as system failure, network delay, data inconsistency, etc.), and take appropriate measures to solve it.
[0091] In a possible implementation, the method further includes:
[0092] In response to obtaining the final status of the order, determining whether the target order transaction is successful based on the final status of the order. In response to the target order transaction not being successful, generating second warning information.
[0093] like Figure 2As shown, the system continuously monitors and obtains status updates of the order until the order reaches its final status. The final status may include, but is not limited to, "completed", "cancelled", "refunded", etc. The system parses the final status information of the order, which involves checking the status code, status description, or other relevant metadata.
[0094] Based on the parsed status information, the system determines whether the order transaction is successful. For example, the "Completed" status is considered a sign of a successful transaction, while the "Canceled" or "Refunded" status means that the transaction failed.
[0095] When the system determines that the target order transaction is unsuccessful, that is, the order is in a "canceled", "refunded" or other unsuccessful state, the system can automatically generate a second alarm message, which should include the order ID, failure reason (such as cancellation, refund, etc.), occurrence time and any other details that help to quickly locate and solve the problem.
[0096] In one possible implementation, in order to increase scalability, the system collects daily loan flows, compares the total transaction amounts of the two parties, completes the end-of-day reconciliation, and if there is any inconsistency in the comparison, it will be transferred to manual analysis. The data analyzed by manual analysis is likely to produce one-sided accounts, so as to achieve the goal of timely processing. Figure 3 , Figure 3 The third order monitoring method provided in the embodiment of the present application includes:
[0097] Acquire first-party transaction information and second-party transaction information; compare the first-party transaction information and the second-party transaction information; and generate third alarm information in response to inconsistency between the first-party transaction information and the second-party transaction information.
[0098] Specifically, the system can periodically collect complete loan flow information from the first party (loan issuer) and the second party (loan receiver or repayer). This can be achieved through API interface calls or file transfer protocol (FTP).
[0099] Before comparison, necessary data cleaning and formatting can be performed on the collected flow information to ensure the consistency and accuracy of all data fields.
[0100] At the end of the day, the system automatically calculates the total transaction amount of both the borrower and the lender and compares them. This step is designed to quickly identify differences in total amount, thereby reducing the workload of subsequent detailed comparison.
[0101] If the total amount is found to be inconsistent, the system will immediately generate an alarm message and attach the specific difference data (such as total amount, transaction date, etc.) to the alarm message. In the case of inconsistency, the system will mark the relevant transaction information and transfer it to the manual review team. The manual reviewer will analyze the transaction details in depth based on the preliminary information provided by the system to find the specific reasons for the difference.
[0102] Therefore, through the combination of automation and manual work, effective management and monitoring of loan business flow information is achieved. Automated comparison reduces the burden of manual review and makes daily reconciliation work more efficient. Systematic data processing and comparison help to find problems early and avoid error accumulation. Timely detection and handling of unilateral account problems can reduce potential financial risks.
[0103] The above are some specific implementations of the order monitoring method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding system for order monitoring. The system provided in the embodiment of the present application will be introduced from the perspective of functional modularization. Figure 4 A structural diagram of an order monitoring system provided in an embodiment of the present application.
[0104] The system comprises:
[0105] The first query unit 110 is used to query the order status of the target order in real time;
[0106] A polling unit 111 is used for polling the final status of the order at a first preset frequency in response to failure to obtain the final status of the order, wherein the final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate that the final status of the order is queried once every first preset time;
[0107] The first generating unit 112 is configured to generate a first warning message in response to failure to query the final status of the order under a preset condition.
[0108] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the order monitoring method provided in the embodiments of the present application.
[0109] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the order monitoring method described in any embodiment of the present application.
[0110] The computer storage medium stores codes, and when the codes are executed, the device executing the codes implements the order monitoring method described in any embodiment of the present application.
[0111] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.
[0112] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0113] It should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.
[0114] It should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0115] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0116] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0117] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An order monitoring method, It is characterized in that include: Query the order status of the target order in real time; In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency, wherein the final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate querying the final status of the order once every first preset time; In response to failure to query the final status of the order under preset conditions, a first warning message is generated.
2. The method according to claim 1, It is characterized in that In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency includes: In response to failure to obtain the final status of the order, polling the final status of the order at a first preset frequency after a second preset time.
3. The method according to claim 1, It is characterized in that The generating of the first warning information in response to failure to query the final status of the order under the preset condition includes: In response to failure to obtain the final status of the order within a third preset time, a first warning message is generated.
4. The method according to claim 1, It is characterized in that The generating of the first warning information in response to failure to query the final status of the order under the preset condition includes: In response to failure to obtain the final status of the order after a preset number of pollings, a first warning message is generated.
5. The method according to claim 1, It is characterized in that The method further comprises: An alarm record is generated based on the order status of the target order and the first alarm information.
6. The method according to claim 1, It is characterized in that The method further comprises: The first alarm information is pushed to the target personnel so that the target personnel analyze the target order.
7. The method according to claim 1, It is characterized in that The method further comprises: In response to obtaining the final status of the order, determining whether the target order transaction is successful based on the final status of the order. In response to the target order transaction being unsuccessful, second warning information is generated.
8. The method according to claim 1, It is characterized in that The method further comprises: Obtain first-party transaction information and second-party transaction information; Comparing the first party's transaction information with the second party's transaction information; In response to the first-party transaction information and the second-party transaction information being inconsistent, third warning information is generated.
9. An order monitoring system, It is characterized in that The system comprises: A first query unit, used for querying the order status of a target order in real time; a polling unit, configured to, in response to failure to obtain the final status of the order, poll the final status of the order at a first preset frequency, wherein the final status of the order is used to indicate whether the current order transaction is successful, and the first preset frequency is used to indicate that the final status of the order is queried once every first preset time; The first generating unit is used to generate a first warning message in response to failure to query the final status of the order under a preset condition.
10. An electronic device, It is characterized in that include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the order monitoring method according to any one of claims 1 to 7 is implemented.
