Data processing method, device, equipment and medium

Abstract

The present application relates to the field of data verification technology, and proposes a data processing method, device, equipment and medium, which are used to solve the problem of low verification efficiency caused by post-verification verification data in related technologies. In the present application, for the data transfer request sent by the terminal device, it is first determined whether the data transfer request is verified based on the account type, business type and data volume threshold of the data transfer request. If it is determined to be verified, it is determined whether the remaining data volume of the institution is sufficient. If the remaining data volume of the institution is sufficient, the transfer data volume is deducted and the terminal device is notified of the successful deduction; if the remaining data volume of the institution is not sufficient, the transfer data volume is deducted centrally after the remaining data volume is sufficient. Therefore, the method provided by the present application is not to verify at any time, but to verify during each data transfer process, so as to achieve the method of in-process verification. Compared with post-verification, it can verify in time to improve the verification efficiency.

Description

Background Art

[0002] In the prior art, position management is usually calculated by post-verification or transaction-by-transaction reporting. Post-verification requires a lot of manpower and is inefficient. In addition, since the position is counted post-event, it is easy to generate intraday liquidity risk. Although transaction-by-transaction control avoids intraday liquidity risk, it has a poor customer experience and is easy to expose the problem of insufficient funds of the institution to customers, affecting customer satisfaction and possibly affecting the reputation of the institution. Therefore, how to improve customer experience while improving verification efficiency is a problem that needs to be solved. Summary of the invention

[0003] The purpose of this application is to provide a data processing method, device, equipment and medium to solve the problem in the prior art of how to improve customer experience while improving verification efficiency.

[0004] In a first aspect, the present application provides a data processing method, the method comprising:

[0005] receiving a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred;

[0006] If the remaining data amount needs to be verified for the first data transfer request, determining whether the remaining data amount corresponding to the organization identifier is sufficient;

[0007] If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device;

[0008] If the remaining data volume is insufficient, the data volume to be transferred is deducted after the remaining data volume is sufficient, and a deduction success message is sent to the terminal device.

[0009] Optionally, the first data transfer request further includes a business type and an account type, wherein the account type is an account type for paying the amount of data to be transferred, and determining whether the first data transfer request needs to verify the remaining amount of data specifically includes:

[0010] If the account type is the first account type and the amount of data to be transferred is greater than or equal to the data amount threshold, determining to verify the remaining data amount for the first data transfer request;

[0011] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the first business type, determining to verify the remaining data amount for the first data transfer request;

[0012] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the second business type, determining not to verify the remaining data amount for the first data transfer request, and notifying the terminal device to perform a data transfer operation;

[0013] If the account type is the second account type, it is determined not to check the remaining data amount for the first data transfer request.

[0014] Optionally, the step of waiting for the remaining data amount to be sufficient before deducting the amount of data to be transferred specifically includes:

[0015] If there is no second data transfer request, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

[0016] Optionally, the method further includes:

[0017] If the second data transfer request exists, adding the first data transfer request to the queue to be deducted according to the receiving time and marking it as a queued state;

[0018] Polling the queue to be deducted;

[0019] If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount;

[0020] If the deduction is successful, the state of the first data transfer request is changed to a deducted state and removed from the queue to be deducted, and a deduction success message is sent to the terminal device;

[0021] If the deduction fails, the first data transfer request is moved to the end of the queue to be deducted.

[0022] Optionally, if the deduction fails, the method further includes:

[0023] Sending a warning message to the terminal device, wherein the warning message is used to prompt that the remaining data amount is insufficient;

[0024] Based on the remaining data amount adjustment request sent by the terminal device, the remaining data amount is increased.

[0025] Optionally, the method further includes:

[0026] If the deduction fails multiple times within the preset time limit, the first data transfer request is returned to the terminal device.

[0027] Optionally, if the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device, the method further includes:

[0028] If it is monitored that the terminal device does not perform the data transfer operation for the data transfer request, determining that a transfer exception occurs in the processing operation for the first data transfer request;

[0029] The remaining data amount is corrected based on the amount of data to be transferred, and the terminal device is notified to process a transfer exception for the first data transfer request.

[0030] Optionally, the method further includes:

[0031] If the account type is the second account type, the first data transfer request is controlled transaction by transaction.

[0032] Optionally, the remaining data amount includes a first data amount and a second data amount, wherein the first data amount is greater than the second data amount;

[0033] The deducting the remaining data amount according to the amount of data to be transferred specifically includes:

[0034] deducting the amount of data to be transferred from the first amount of data;

[0035] The method further comprises:

[0036] If there is no need to verify the remaining data amount, the to-be-transferred data amount is deducted from the second data amount.

[0037] Optionally, adjusting the remaining data amount specifically includes:

[0038] The amount of the second data volume is adjusted to the amount of the first data volume.

[0039] In a second aspect, the present application further provides a data processing device, the device comprising:

[0040] A receiving module, configured to execute and receive a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred;

[0041] a verification module configured to determine whether the remaining data amount corresponding to the organization identifier is sufficient if the remaining data amount needs to be verified for the first data transfer request;

[0042] If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device;

[0043] If the remaining data volume is insufficient, the data volume to be transferred is deducted after the remaining data volume is sufficient, and a deduction success message is sent to the terminal device.

[0044] Optionally, the first data transfer request further includes a business type and an account type, wherein the account type is an account type for paying the amount of data to be transferred, and the device further includes:

[0045] The remaining amount checking module is configured to determine whether the first data transfer request needs to check the remaining data amount based on the following method:

[0046] If the account type is the first account type and the amount of data to be transferred is greater than or equal to the data amount threshold, determining to verify the remaining data amount for the first data transfer request;

[0047] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the first business type, determining to verify the remaining data amount for the first data transfer request;

[0048] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the second business type, determining not to verify the remaining data amount for the first data transfer request, and notifying the terminal device to perform a data transfer operation;

[0049] If the account type is the second account type, it is determined not to check the remaining data amount for the first data transfer request.

[0050] Optionally, the step of waiting for the remaining data amount to be sufficient before deducting the amount of data to be transferred is performed, and the verification module is specifically configured to perform:

[0051] If there is no second data transfer request, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

[0052] Optionally, the device further comprises:

[0053] A polling module is configured to execute, if the second data transfer request exists, adding the first data transfer request to a queue to be deducted according to a receiving time and marking it as a queued state;

[0054] Polling the queue to be deducted;

[0055] If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount;

[0056] If the deduction is successful, the state of the first data transfer request is changed to a deducted state and removed from the queue to be deducted, and a deduction success message is sent to the terminal device;

[0057] If the deduction fails, the first data transfer request is moved to the end of the queue to be deducted.

[0058] Optionally, if the deduction fails, the polling module is further configured to execute:

[0059] Sending a warning message to the terminal device, wherein the warning message is used to prompt that the remaining data amount is insufficient;

[0060] Based on the remaining data amount adjustment request sent by the terminal device, the remaining data amount is increased.

[0061] Optionally, the device further comprises:

[0062] The return processing module is configured to return the first data transfer request to the terminal device if multiple deductions fail within a preset time limit.

[0063] Optionally, if the remaining data amount is sufficient, after deducting the remaining data amount according to the amount of data to be transferred and sending a deduction success message to the terminal device, the apparatus further includes:

[0064] an exception handling module, configured to determine that a transfer exception occurs in the processing operation for the first data transfer request if it is monitored that the terminal device does not perform a data transfer operation for the data transfer request;

[0065] The remaining data amount is corrected based on the amount of data to be transferred, and the terminal device is notified to process a transfer exception for the first data transfer request.

[0066] Optionally, the device further comprises:

[0067] The transaction-by-transaction verification module is configured to perform transaction-by-transaction control on the first data transfer request if the account type is the second account type.

[0068] Optionally, the remaining data amount includes a first data amount and a second data amount, wherein the first data amount is greater than the second data amount;

[0069] Executing the deduction of the remaining data amount according to the amount of data to be transferred, the verification module is specifically configured to execute:

[0070] deducting the amount of data to be transferred from the first amount of data;

[0071] The verification module is further configured to perform:

[0072] If there is no need to verify the remaining data amount, the to-be-transferred data amount is deducted from the second data amount.

[0073] Optionally, the step of adjusting the amount of remaining data is performed, and the verification module is specifically configured to perform:

[0074] The amount of the second data volume is adjusted to the amount of the first data volume.

[0075] In a third aspect, the present application further provides an electronic device, including:

[0076] A memory for storing executable instructions of the processor;

[0077] A processor is used to execute the executable instructions to implement any one of the methods provided in the first aspect of the present application.

[0078] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any method provided in the first aspect of the present application.

[0079] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements any method provided in the first aspect of the present application.

[0080] The technical solution provided by the embodiments of the present application brings at least the following beneficial effects:

[0081] After receiving the first data transfer request, if the remaining data volume needs to be verified, the application determines whether the remaining data volume is sufficient. If it is sufficient, the amount of data to be transferred is deducted. Otherwise, the amount of data to be transferred is deducted after the remaining data volume is sufficient. After the deduction is successful, a message of successful deduction is sent to the terminal device. Therefore, the application can ensure the accuracy of the data transfer of the organization by verifying the data transfer request that needs to be verified, and will not expose the defect of insufficient remaining data volume of the organization to customers, thereby avoiding the impact on the reputation of the organization.

[0082] It should be understood that the above general description and the following detailed description are only exemplary and explanatory and cannot limit the present application. Based on the common sense in the art, the above preferred conditions can be combined arbitrarily to obtain the preferred embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. Obviously, the drawings introduced 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 creative work.

[0084] Figure 1A schematic diagram of an application scenario provided for an embodiment of the present application;

[0085] Figure 2 A schematic diagram of data processing provided in an embodiment of the present application;

[0086] Figure 3 A schematic diagram of determining whether data should be verified provided in an embodiment of the present application;

[0087] Figure 4 A schematic diagram of data verification provided in an embodiment of the present application;

[0088] Figure 5 Schematic diagram of the device provided in the embodiment of the present application;

[0089] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0090] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme 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. Among them, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0091] Furthermore, in the description of the embodiments of the present application, unless otherwise specified, “ / ” means or. For example, A / B can mean A or B. The “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0092] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood as suggesting or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more.

[0093] In related technologies, post-verification is to compare the pre-declared data transfer request with the actual data volume received or paid, and mark the two sets of data that match the transferred data volume, account type, institution and other elements to facilitate post-statistics and assessment by users. Post-verification requires a lot of manpower, has low work efficiency, and is prone to intraday liquidity risk due to post-statistics of positions.

[0094] The method of transaction-by-transaction control is to check whether the payment information is fully matched with the declared data transfer request, and not allow users to pay for unmatched data transfer requests, thereby achieving control over intraday liquidity risk. Although intraday liquidity risk is avoided, the customer experience is poor, and when users are not allowed to pay, the problem of insufficient funds of the institution is easily exposed to the customers, affecting customer satisfaction and possibly affecting the reputation of the institution.

[0095] In view of this, embodiments of the present application provide a data processing method, apparatus, device and medium for improving verification efficiency while improving customer experience.

[0096] The data processing method provided by the present application will be introduced below in conjunction with embodiments.

[0097] The present application proposes a data mathematical method. For a data transfer request sent by a terminal device, first determine whether the data transfer request is verified based on the account type, business type and data volume threshold of the data transfer request. If it is determined to be verified, then determine whether the remaining data volume of the institution is sufficient. If the remaining data volume of the institution is sufficient, deduct the transfer data volume and notify the terminal device that the deduction is successful; if the remaining data volume of the institution is insufficient, wait until the remaining data volume is sufficient before centrally deducting the transfer data volume. Therefore, the method provided by the present application is not to verify at any time, but to verify during each data transfer process, thus achieving an in-process verification method. Compared with post-verification, verification can be carried out in a timely manner to improve verification efficiency.

[0098] In addition, in the embodiment of the present application, if the deduction fails multiple times within the preset time limit, the data transfer request is returned to the terminal device for processing. Thus, the terminal device can promptly process the first data transfer request that failed to deduct, without having to wait until the subsequent verification to find that the deduction failed, thereby improving the verification efficiency.

[0099] The acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

[0100] After introducing the main inventive ideas of the embodiments of the present application, the following briefly introduces the application scenarios to which the technical solutions of the embodiments of the present application can be applied. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application and are not limited. In specific implementation, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.

[0101] like Figure 1 The figure shows a schematic diagram of an application scenario provided in an embodiment of the present application.

[0102] exist Figure 1 In the embodiment, the head office 100 controls each branch office 101 (and / or different departments of the head office). Assume that there are n branches (and / or different departments of the head office), namely, branch office 101-1, branch office 101-2, ..., branch office 101-n. The head office 100 is provided with a server 102, and the server 102 adjusts the remaining data volume of each branch office 101. Each branch office (and / or department of the head office) 101 is provided with a terminal device 103, such as Figure 1 It is shown that terminal devices 103-1, 103-2, ..., 103-n are included. The terminal device 103 may be one electronic device or multiple electronic devices, and a payment component 105 and a business component 104 are configured in the terminal device 103, and a payment management component 106 is configured in the server 102. The payment component 105 is used to initiate a data transfer request to the payment management component 106 of the server 102. The business component 104 can obtain the corresponding parameters included in the data transfer request, such as the business type, the account type (the account type refers to the account for the amount of data to be transferred for the payment data transfer request, such as the head office account or the branch account, or other bank account), the business type, the amount of data to be transferred, and at least one of the institution identification.

[0103] After the server 102 receives the first data transfer request sent by any terminal device 103, the business management component 106 of the server 102 selects different management methods according to the account type in the first data transfer request. If the account type is the first account type (such as a head office account), the first management method is selected, that is, whether to perform verification is determined based on the business type and the amount of data to be transferred; if the account type is the second account type (such as a branch account), the second management method is selected, and the second management method is, for example, to process the first data transfer request in a transaction-by-transaction control manner.

[0104] If the first management method is selected and the first data transfer request is determined to be verified, it is determined whether the remaining data volume of the branch office 101 is sufficient. If the remaining data volume is sufficient, the remaining data volume is deducted from the data volume to be transferred and a deduction success message is sent to the terminal device.

[0105] If the remaining data volume is insufficient, the server 102 waits until the remaining data volume is sufficient, deducts the remaining data volume according to the amount of data to be transferred, and sends a successful deduction message to the terminal device. If the deduction fails multiple times within the preset time limit, the server 102 sends a deduction failure message to the terminal device 103, and returns the first data transfer request to the terminal device 103. The terminal device 103 processes the returned data transfer request.

[0106] If the first management method is selected and it is determined that the first data transfer request is not to be verified, the terminal device 103 is notified to perform the transfer operation. After the terminal device 103 receives the information to perform the transfer operation, the user determines whether to perform the transfer operation on the business component 104 and notifies the server 102 to pay the amount of data to be transferred from the first account type.

[0107] If the server 102 detects a payment anomaly, then in the embodiment of the present application, if the terminal device 103 receives a returned data transfer request, the data transfer request will be revoked.

[0108] The terminal device 103 in the embodiment of the present application can be a server, a desktop computer, an intelligent terminal device, etc. The server 102 in the embodiment of the present application can be a server, a server cluster composed of several servers, or a cloud computing center. The server 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0109] Of course, the method provided in the embodiment of the present application is not limited to Figure 1 The application scenarios shown can also be used in other possible application scenarios, and the embodiments of the present application are not limited thereto. Figure 1 The functions that can be implemented by each device in the application scenario shown will be described in the subsequent method embodiments, and will not be described in detail here.

[0110] To further illustrate the technical solution provided by the embodiment of the present application, this is described in detail below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiment of the present application provides the method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or no creative labor. In the steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiment of the present application. The method may be executed or executed in parallel in the actual processing process or when the device is executed in accordance with the method sequence shown in the embodiment or drawings.

[0111] For ease of understanding, a data processing method provided by the present application is described in detail below through a specific embodiment. Figure 2 As shown, the following steps may be included:

[0112] Step 201: receiving a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred.

[0113] The organization identifier is, for example, a branch identifier, identifiers of various departments of the head office, etc. The amount of data to be transferred is the amount of data that needs to be transferred, and may be the amount of data that the branch needs to pay to other organizations.

[0114] After receiving the data transfer request, the server 102 determines whether verification is required based on the account type, amount of data to be transferred, and business type included in the data transfer request, such as Figure 3 As shown, the verification steps can be implemented as follows:

[0115] Step 301, determine whether the data transfer request is of the first account type, if the account type is the first account, execute step 302, if the account type is the second account type, execute step 306.

[0116] Among them, the first account type is, for example, a head office account and the second account type is, for example, a branch account. By dividing the first account type and the second account type, different management logics can be divided based on different account types, and the needs of different account types can be decoupled, making the processing of data transfer requests more flexible.

[0117] In addition, in the embodiment of the present application, large-amount payment verification can be implemented, while small-amount payment verification is not implemented, because each institution (including branches and / or departments of the head office) applies for positions in advance. Large amounts require more advance application, so large-amount payments may easily lead to deduction failure due to insufficient remaining data, while small amounts are less likely to lead to deduction failure. Therefore, the management logic of large-amount and small-amount payments can be implemented in combination with step 302.

[0118] Step 302, determine whether the amount of data to be transferred is greater than or equal to the data amount threshold corresponding to the organization identifier. If the amount of data to be transferred is greater than or equal to the data amount threshold corresponding to the organization identifier, execute step 304, otherwise execute step 303.

[0119] Among them, the first data transfer request for large-amount payment and the data transfer request for small-amount payment can be screened out through the data volume threshold, thereby realizing the different management logics of large-amount and small-amount payment mentioned above.

[0120] Step 303 , determining whether the data transfer request is of the first service type, if the service type of the data transfer request is of the first service type, executing step 304 , if the service type of the data transfer request is of the second service type, executing step 305 .

[0121] The first business type is, for example, over-the-counter settlement, cash transaction, etc., and the second business type is, for example, loan transfer, transaction in a fund management system, etc. By dividing the first and second business types, different businesses can be managed accurately.

[0122] Step 304, determining the remaining data amount for verifying the data transfer request.

[0123] Step 305: determine that the remaining data amount does not need to be checked, and notify the terminal device to perform a data transfer operation.

[0124] Step 306, after determining that the remaining data amount does not need to be checked, the first data request is processed according to a record-by-record control method.

[0125] In an embodiment of the present application, the order of determining whether to verify the first data transfer request according to the account type, the amount of data to be transferred, and the business type can be fixed. That is, first determine whether to manage the first data transfer request according to the data processing method of the present application or to manage the first data transfer request in a transaction-by-transaction control manner according to the account type. Then determine whether to verify the first data transfer request according to the amount of data to be transferred, wherein for the first data transfer request that is less than the data amount threshold, determine whether to verify the first data transfer request according to the business type, so as to prevent missing the verification of the first data transfer request that is less than the data amount threshold and is of the first business type.

[0126] In the present application, in order to facilitate data management, the data transfer requests of the terminal device are differentiated and managed in order of account type, business type and amount of data to be transferred, so as to prevent the verification of different types of data transfer requests at the same time, and the verification of data transfer requests that meet two or more types multiple times, resulting in inaccurate verification results.

[0127] Of course, it should be noted that, in another embodiment, Figure 3 The execution of each judgment may not be limited in order, as long as it can be determined based on each judgment condition whether to check the remaining data amount for the first data transfer request. This application does not impose any limitation on this.

[0128] Step 202: If the remaining data amount needs to be checked for the first data transfer request, then step 203 is executed.

[0129] Step 203, determine whether the remaining data amount corresponding to the organization identifier is sufficient, if the remaining data amount is sufficient, execute step 204, otherwise execute step 205.

[0130] Step 204, deduct the remaining data amount according to the amount of data to be transferred, and send a message indicating that the deduction is successful to the terminal device.

[0131] Step 205, wait until the remaining data volume is sufficient before deducting the amount of data to be transferred, and send a deduction success message to the terminal device.

[0132] In the embodiment of the present application, if each branch 101 (such as each branch and / or each department of the head office) needs to perform a data transfer operation on the data, for the first data transfer request greater than or equal to the data volume threshold in the second business type, the server 102 can apply for a position in advance according to the account type, the transfer data volume and the business type. After the server 102 matches the corresponding institution according to the institution identifier, it allocates the required data volume to the branch 101 in advance according to the data volume applied in the position. When different terminal devices or the same terminal device send data transfer requests to the server 102 multiple times, the time of sending the data transfer request is also different. If the data transfer request meets at least one of the second account type, the amount of data to be transferred is less than the data volume threshold or the second business type, the branch 101 does not need to apply for a position in advance to the server 102. It can be understood that when a large amount of payment is made, the server can be applied for a position in advance, and when a small amount of payment is made, it is not necessary to apply in advance. Therefore, when applying for a position, that is, when applying for a payment amount, the branch can determine whether to apply in advance according to its own needs. In order to ensure the smooth and reasonable execution of the data transfer business in the embodiment of the present application, the quota allocated to the branch is also divided into a first data volume and a second data volume. The first data volume is the data volume allocated based on the application of the branch, and the second data volume is the flexible data volume, that is, the head office flexibly allocates additional quotas to the branch based on the application of the branch and / or the business situation of the branch, so as to deal with small payments and emergencies.

[0133] The same branch office 101 can not only send the first data transfer request but also the second data transfer request to the server 102 through the terminal device 103. Similarly, the server 102 can not only receive the first data transfer request but also the second data transfer request sent by the same branch office 101. Of course, the second data transfer request can also be sent by other branches.

[0134] When processing the first data transfer request, if the remaining data amount of the first data transfer request is insufficient, it is also possible to determine how to process the first data transfer request by referring to whether there is a second data transfer request.

[0135] For example, if there is no second data transfer request, it is only necessary to wait until the remaining data amount corresponding to the first data transfer request is sufficient before deducting the amount of data to be transferred. Figure 4 As shown, the processing of the first data transfer request may include the following steps:

[0136] Step 401, add the first data transfer request to the queue to be deducted according to the receiving time and mark it as a queued state. By default, the processing method of the second data transfer request is the same as the first data transfer request, and the processing method of the second data transfer request is not repeated here.

[0137] Step 402: poll the queue to be deducted.

[0138] Step 403: If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

[0139] Step 404, determine whether the deduction is successful, if the deduction is successful, execute step 405, otherwise execute step 406.

[0140] Step 405: modify the state of the first data transfer request to a deducted state and remove it from the queue to be deducted, and send a deduction success message to the terminal device.

[0141] Step 406: Move the first data transfer request to the end of the queue to be deducted.

[0142] Step 407, determine whether there are still pending data transfer requests in the queue to be deducted, if yes, return to step 402, otherwise end the polling.

[0143] In the embodiment of the present application, if the server 102 receives the first data transfer request and the second data transfer request, the first data transfer request is added to the queue to be deducted according to the time of receipt, and the queue to be deducted is polled. At this time, for the first data transfer request in the queue to be deducted, after adjusting the remaining data amount of the corresponding organization, the amount of data to be transferred is deducted again, and then the second data transfer request is continued to be deducted until all data transfer requests in the queue to be deducted are polled.

[0144] In one embodiment of the present application, if the deduction of the amount of data to be transferred fails, the server 102 sends a warning message to the terminal device 103, wherein the warning message is used to prompt that the amount of remaining data is insufficient. At this time, after receiving the warning message, the terminal device 103 can display an operation interface, and the corresponding administrator or the adjustment strategy can apply to adjust the amount of remaining data, which can be implemented by the terminal device 103 sending a request for adjusting the amount of remaining data to the server 102, and the server 102 adjusts the amount of remaining data according to the request for adjusting the amount of remaining data.

[0145] In another embodiment of the present application, if multiple deductions fail within a preset time limit, the first data transfer request is returned to the terminal device. Thus, when multiple deductions fail, it indicates that there is an abnormality, and the abnormality can be notified to the terminal device for a corresponding processing strategy.

[0146] In another embodiment of the present application, after the server 102 sends a message of successful deduction to the terminal device 103, the terminal device 103 performs a data transfer operation. The data transfer operation can be implemented by prompting the terminal device 103 to prompt its corresponding administrator to send a confirmation transfer message to the server on the terminal device 103, and then the server deducts the data volume in the corresponding head office account according to the confirmation transfer message and transfers the amount of data to be transferred to the branch 101, and the data transfer operation is completed. During the data transfer operation, the operation of transferring the amount of data to be transferred from the branch account is performed through the participation of the server 102, so the server 102 can monitor whether the data transfer operation is successfully executed. If it is monitored that the terminal device does not perform the data transfer operation for the data transfer request, it is determined that the processing operation for the first data transfer request has a transfer exception. And notify the terminal device 103 to process the transfer exception for the first data transfer request. After receiving the abnormal information, the terminal device 103 cancels the information of the first data transfer request and notifies the server 102 to correct the remaining data volume of the institution according to the amount of data to be transferred. From this, it can be seen that during implementation, the server 102 can maintain two important data for the same branch 101. The first important data is the remaining data amount, which is used to verify the remaining data amount before actually transferring the data. When modifying the remaining data amount, that is, when verifying the remaining data amount, the deduction operation of the remaining data amount is rolled back; the second important data is the account limit of the head office 100, which is used to execute the data transfer operation to transfer the required data amount (that is, the data amount to be transferred) to the branch structure 101.

[0147] In the embodiment of the present application, the amount of data flows between the head office 100 and the branch office 101 in the form of data, and flows in the form of funds in the account when paying. For example, when the branch office 101 purchases goods, the account balance of the branch office is deducted when paying, and the funds in the account are transferred to the seller. The data transfer operation performed by the terminal device 103 is to transfer the amount of data in the payment account of the head office 100 to the branch office 101. The amount of data allocated by the server 102 to the branch office 101 is based on the remaining amount of data in the head office 100 and the application and business situation of the branch office.

[0148] In the present application, if the data transfer operation cannot be performed due to a malfunction of the server 102 or the terminal device 103, such as a power outage, network congestion, or other problems, the server 102 can also detect the transfer anomaly.

[0149] In the embodiment of the present application, as described above, the remaining data volume of the branch 101 includes a first data volume and a second data volume, wherein the first data volume is greater than the second data volume. The first data volume is allocated to the branch 101 in advance according to the position application sent by the terminal device 103 and received by the server 102, and the second data volume is flexibly allocated according to the situation of the branch 101. For data transfer requests that require verification, such as large-amount payment, the server 102 deducts the amount of data to be transferred from the first data volume; for data transfer requests that do not require verification, such as small-amount payment, the amount of data to be transferred is deducted from the second data volume.

[0150] In this application, the number of data transfer requests below the data volume threshold in one day is huge and there are many types of business. If each data transfer request in one day is managed, the business component 104 and the payment management component 106 will take a lot of time to process, which is easy to affect the customer experience and affect the management of data transfer requests greater than or equal to the data volume threshold. Therefore, if the data transfer request greater than or equal to the data volume threshold declares the position in advance, the business component 104 does not need to classify the account type and business type of the data transfer request on the same day, but classifies it in advance, and the server 102 allocates the position to the institution according to the declared amount on the same day. For the data transfer request that is lower than the data volume threshold and is the second business type on the same day, the business component 104 directly deducts the amount of data to be transferred from the second data volume, which improves the efficiency of the business component 104. That is, for large payments, the payment management component 106 can perform deduction transfer, and for small payments, the business component 104 can complete the deduction transfer.

[0151] In one embodiment of the present application, there are two ways to adjust the remaining data volume. One is that when the user sends a remaining data volume adjustment request to the server 102 through the terminal device 103 within the preset time limit, the server 102 increases the remaining data volume according to the remaining data volume adjustment request; the other is that if the administrator does not send a remaining data volume adjustment request to the server 102 through the terminal device 103 within the preset time limit, the server 102 adjusts the amount of the second data volume to the amount of the first data volume.

[0152] Based on the same inventive concept, the present application also proposes a data processing device 500, such as Figure 5 As shown, the device comprises:

[0153] The receiving module 501 is configured to execute and receive a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred;

[0154] A verification module 502 is configured to determine whether the remaining data amount corresponding to the organization identifier is sufficient if the remaining data amount needs to be verified for the first data transfer request;

[0155] If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device;

[0156] If the remaining data volume is insufficient, the data volume to be transferred is deducted after the remaining data volume is sufficient, and a deduction success message is sent to the terminal device.

[0157] Optionally, the first data transfer request further includes a business type and an account type, wherein the account type is an account type for paying the amount of data to be transferred, and the device further includes:

[0158] The remaining amount checking module is configured to determine whether the first data transfer request needs to check the remaining data amount based on the following method:

[0159] If the account type is the first account type and the amount of data to be transferred is greater than or equal to the data amount threshold, determining to verify the remaining data amount for the first data transfer request;

[0160] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the first business type, determining to verify the remaining data amount for the first data transfer request;

[0161] If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the second business type, determining not to verify the remaining data amount for the first data transfer request, and notifying the terminal device to perform a data transfer operation;

[0162] If the account type is the second account type, it is determined not to check the remaining data amount for the first data transfer request.

[0163] Optionally, the step of waiting for the remaining data amount to be sufficient before deducting the amount of data to be transferred is performed, and the verification module is specifically configured to perform:

[0164] If there is no second data transfer request, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

[0165] Optionally, the device further comprises:

[0166] A polling module is configured to execute, if the second data transfer request exists, adding the first data transfer request to a queue to be deducted according to a receiving time and marking it as a queued state;

[0167] Polling the queue to be deducted;

[0168] If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount;

[0169] If the deduction is successful, the state of the first data transfer request is changed to a deducted state and removed from the queue to be deducted, and a deduction success message is sent to the terminal device;

[0170] If the deduction fails, the first data transfer request is moved to the end of the queue to be deducted.

[0171] Optionally, if the deduction fails, the polling module is further configured to execute:

[0172] Sending a warning message to the terminal device, wherein the warning message is used to prompt that the remaining data amount is insufficient;

[0173] Based on the remaining data amount adjustment request sent by the terminal device, the remaining data amount is increased.

[0174] Optionally, the device further comprises:

[0175] The return processing module is configured to return the first data transfer request to the terminal device if multiple deductions fail within a preset time limit.

[0176] Optionally, if the remaining data amount is sufficient, after deducting the remaining data amount according to the amount of data to be transferred and sending a deduction success message to the terminal device, the apparatus further includes:

[0177] an exception handling module, configured to determine that a transfer exception occurs in the processing operation for the first data transfer request if it is monitored that the terminal device does not perform a data transfer operation for the data transfer request;

[0178] The remaining data amount is corrected based on the amount of data to be transferred, and the terminal device is notified to process a transfer exception for the first data transfer request.

[0179] Optionally, the device further comprises:

[0180] The transaction-by-transaction verification module is configured to perform transaction-by-transaction control on the first data transfer request if the account type is the second account type.

[0181] Optionally, the remaining data amount includes a first data amount and a second data amount, wherein the first data amount is greater than the second data amount;

[0182] Executing the deduction of the remaining data amount according to the amount of data to be transferred, the verification module is specifically configured to execute:

[0183] deducting the amount of data to be transferred from the first amount of data;

[0184] The verification module is further configured to perform:

[0185] If there is no need to verify the remaining data amount, the to-be-transferred data amount is deducted from the second data amount.

[0186] Optionally, the step of adjusting the amount of remaining data is performed, and the verification module is specifically configured to perform:

[0187] The amount of the second data volume is adjusted to the amount of the first data volume.

[0188] After introducing the data processing method and device according to the exemplary embodiment of the present application, next, an electronic device according to another exemplary embodiment of the present application is introduced.

[0189] Those skilled in the art will appreciate that various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to as "circuit", "module" or "system" herein.

[0190] In some possible implementations, the electronic device according to the present application may include at least one server and at least one memory. The memory stores program code, and when the program code is executed by the server, the server executes the operation data management method according to various exemplary implementations of the present application described above in this specification. For example, the server may execute the steps in the operation data management method.

[0191] Refer to the following Figure 6 The electronic device 130 according to this embodiment of the present application is described. Figure 6 The electronic device 130 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.

[0192] like Figure 6As shown, the electronic device 130 is in the form of a general electronic device. The components of the electronic device 130 may include but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 connecting different system components (including the memory 132 and the processor 131).

[0193] Bus 133 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.

[0194] The memory 132 may include a readable medium in the form of a volatile memory, such as a random access memory (RAM) 1321 and / or a cache memory 1322 , and may further include a read-only memory (ROM) 1323 .

[0195] The memory 132 may also include a program / utility 1325 having a set (at least one) of program modules 1324, such program modules 1324 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0196] The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboards, pointing devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 130, and / or communicate with any device that enables the electronic device 130 to communicate with one or more other electronic devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 135. Furthermore, the electronic device 130 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 136. As shown, the network adapter 136 communicates with other modules for the electronic device 130 via a bus 133. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0197] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 132 including instructions, and the instructions can be executed by the processor 131 to complete the above-mentioned operation data management method. Optionally, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0198] In an exemplary embodiment, a computer program product is also provided, including a computer program, and when the computer program is executed by the processor 131, any method of the operation data management method provided in the present application is implemented.

[0199] In an exemplary embodiment, various aspects of an operational data management method provided by the present application may also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to enable the computer device to execute the steps of the operational data management method according to various exemplary embodiments of the present application described above in this specification.

[0200] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable 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 thereof.

[0201] The program product for the operation data management method of the embodiment of the present application can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on an electronic device. However, the program product of the present application is not limited to this. In this document, the readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, device or device.

[0202] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, wherein readable program code is carried. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium other than a readable storage medium, which may transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0203] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0204] The program code for performing the operations of the present application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and also conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code can be executed entirely on the user electronic device, partially on the user device, as an independent software package, partially on the user electronic device and partially on the remote electronic device, or entirely on the remote electronic device or server. In the case of a remote electronic device, the remote electronic device can be connected to the user electronic device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external electronic device (for example, using an Internet service provider to connect through the Internet).

[0205] It should be noted that, although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided into multiple units to be embodied.

[0206] In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0207] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0208] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable image scaling device to produce a machine, so that the instructions executed by the processor of the computer or other programmable image scaling device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0209] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable image scaling device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, the instruction device being implemented in the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0210] These computer program instructions may also be loaded onto a computer or other programmable image scaling device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0211] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0212] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data processing method, characterized in that: The method comprises: receiving a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred; If the remaining data amount needs to be verified for the first data transfer request, determining whether the remaining data amount corresponding to the organization identifier is sufficient; If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device; If the remaining data volume is insufficient, wait until the remaining data volume is sufficient before deducting the amount of data to be transferred, and send a deduction success message to the terminal device; The first data transfer request also includes a business type and an account type, wherein the account type is an account type for paying the amount of data to be transferred, and determining whether the first data transfer request needs to verify the remaining amount of data specifically includes: If the account type is the first account type and the amount of data to be transferred is greater than or equal to the data amount threshold, determining to verify the remaining data amount for the first data transfer request; If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the first business type, determining to verify the remaining data amount for the first data transfer request; If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the second business type, determining not to verify the remaining data amount for the first data transfer request, and notifying the terminal device to perform a data transfer operation; If the account type is the second account type, it is determined not to check the remaining data amount for the first data transfer request.

2. The method according to claim 1, characterized in that The step of waiting for the remaining data amount to be sufficient before deducting the amount of data to be transferred specifically includes: If there is no second data transfer request, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

3. The method according to claim 2, characterized in that The method further comprises: If the second data transfer request exists, adding the first data transfer request to the queue to be deducted according to the receiving time and marking it as a queued state; Polling the queue to be deducted; If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount; If the deduction is successful, the state of the first data transfer request is changed to a deducted state and removed from the queue to be deducted, and a deduction success message is sent to the terminal device; If the deduction fails, the first data transfer request is moved to the end of the queue to be deducted.

4. The method according to claim 3, characterized in that If the deduction fails, the method further comprises: Sending a warning message to the terminal device, wherein the warning message is used to prompt that the remaining data amount is insufficient; Based on the remaining data amount adjustment request sent by the terminal device, the remaining data amount is increased.

5. The method according to claim 3 or 4, characterized in that: The method further comprises: If the deduction fails multiple times within the preset time limit, the first data transfer request is returned to the terminal device.

6. The method according to claim 1, characterized in that If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device, the method further includes: If it is monitored that the terminal device does not perform the data transfer operation for the data transfer request, it is determined that a transfer exception occurs in the processing operation for the first data transfer request. The remaining data amount is corrected based on the amount of data to be transferred, and the terminal device is notified to process a transfer exception for the first data transfer request.

7. The method according to claim 1, characterized in that The method further comprises: If the account type is the second account type, the first data transfer request is controlled transaction by transaction.

8. The method according to claim 1, characterized in that: The remaining data amount includes a first data amount and a second data amount, wherein the first data amount is greater than the second data amount; The deducting the remaining data amount according to the amount of data to be transferred specifically includes: deducting the amount of data to be transferred from the first amount of data; The method further comprises: If there is no need to verify the remaining data amount, the to-be-transferred data amount is deducted from the second data amount.

9. The method according to claim 8, characterized in that Adjusting the remaining data amount specifically includes: The amount of the second data volume is adjusted to the amount of the first data volume.

10. A data processing device, characterized in that: The device comprises: A receiving module, configured to execute and receive a first data transfer request sent by a terminal device, wherein the first data transfer request includes an organization identifier and an amount of data to be transferred; a verification module configured to determine whether the remaining data amount corresponding to the organization identifier is sufficient if the remaining data amount needs to be verified for the first data transfer request; If the remaining data amount is sufficient, deducting the remaining data amount according to the amount of data to be transferred, and sending a deduction success message to the terminal device; If the remaining data volume is insufficient, wait until the remaining data volume is sufficient before deducting the amount of data to be transferred, and send a deduction success message to the terminal device; The first data transfer request also includes a business type and an account type, wherein the account type is an account type for paying the amount of data to be transferred, and the device further includes: The remaining amount checking module is configured to determine whether the first data transfer request needs to check the remaining data amount based on the following method: If the account type is the first account type and the amount of data to be transferred is greater than or equal to the data amount threshold, determining to verify the remaining data amount for the first data transfer request; If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the first business type, determining to verify the remaining data amount for the first data transfer request; If the account type is the first account type, the amount of data to be transferred is lower than the data amount threshold corresponding to the institution identifier, and the business type is the second business type, determining not to verify the remaining data amount for the first data transfer request, and notifying the terminal device to perform a data transfer operation; If the account type is the second account type, it is determined not to check the remaining data amount for the first data transfer request.

11. The device according to claim 10, characterized in that The step of waiting for the remaining data amount to be sufficient before deducting the amount of data to be transferred is performed, and the verification module is specifically configured to execute: If there is no second data transfer request, the amount of data to be transferred is deducted again after adjusting the remaining data amount.

12. The device according to claim 11, characterized in that The device also includes: A polling module is configured to execute, if the second data transfer request exists, adding the first data transfer request to a queue to be deducted according to a receiving time and marking it as a queued state; Polling the queue to be deducted; If the first data transfer request is polled, the amount of data to be transferred is deducted again after adjusting the remaining data amount; If the deduction is successful, the state of the first data transfer request is changed to a deducted state and removed from the queue to be deducted, and a deduction success message is sent to the terminal device; If the deduction fails, the first data transfer request is moved to the end of the queue to be deducted.

13. The device according to claim 12, characterized in that If the deduction fails, the polling module is further configured to perform: Sending a warning message to the terminal device, wherein the warning message is used to prompt that the remaining data amount is insufficient; Based on the remaining data amount adjustment request sent by the terminal device, the remaining data amount is increased.

14. The device according to claim 12 or 13, characterized in that The device also includes: The return processing module is configured to return the first data transfer request to the terminal device if multiple deductions fail within a preset time limit.

15. The device according to claim 10, characterized in that If the remaining data amount is sufficient, the remaining data amount is deducted according to the amount of data to be transferred, and after sending a deduction success message to the terminal device, the apparatus further includes: The exception handling module is configured to determine that a transfer exception occurs in the processing operation of the first data transfer request if it is monitored that the terminal device does not perform a data transfer operation for the data transfer request. The remaining data amount is corrected based on the amount of data to be transferred, and the terminal device is notified to process a transfer exception for the first data transfer request.

16. The device according to claim 10, characterized in that The device also includes: The transaction-by-transaction verification module is configured to perform transaction-by-transaction control on the first data transfer request if the account type is the second account type.

17. The device according to claim 10, characterized in that The remaining data amount includes a first data amount and a second data amount, wherein the first data amount is greater than the second data amount; Executing the deduction of the remaining data amount according to the amount of data to be transferred, the verification module is specifically configured to execute: deducting the amount of data to be transferred from the first amount of data; The verification module is further configured to perform: If there is no need to verify the remaining data amount, the to-be-transferred data amount is deducted from the second data amount.

18. The device according to claim 17, characterized in that To perform the adjustment of the remaining data amount, the verification module is specifically configured to perform: The amount of the second data volume is adjusted to the amount of the first data volume.

19. An electronic device, characterized in that: include: A memory for storing executable instructions of the processor; A processor is used to execute the executable instructions to implement the method as described in any one of claims 1 to 9 of the present application.

20. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method as described in any one of claims 1 to 9 of the present application.

21. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the method as claimed in any one of claims 1 to 9 of the present application.

Images