Business Processing Method, Apparatus, Electronic Device, and Storage Medium

Abstract

The present disclosure provides a service processing method, apparatus, electronic device, and storage medium, which relate to the field of computer technology. The method includes: generating a repayment service operation packet corresponding to a repayment request, and in response to determining that the repayment service corresponding to the repayment request is a non-real-time repayment service based on the repayment service operation packet and the repayment service has not changed, generating service timing lock information and account entry capacity lock information corresponding to the repayment service based on the repayment service operation packet, and performing account entry operation processing corresponding to the repayment service according to the service timing lock information and the account entry capacity lock information; the method, apparatus, electronic device, and storage medium of the present disclosure ensure the accuracy of the accounting entry timing depending on the service operation time through the timing lock information, and ensure that the account entry amount of the repayment service is neither overstated nor understated through the capacity lock information, and can prevent the problems of duplicate account entry and incorrect account entry from occurring.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and particularly to a service processing method, apparatus, electronic device, and storage medium. Background Art

[0002] Currently, for the posting of non-real-time repayment services, usually two methods are adopted to control the posting to prevent duplicate posting and incorrect posting. The first method is to control at the posting operation level, that is, when there are outstanding repayment funds in transit, or at the business operation level, it is not allowed to perform the repayment service operation again, or at the ledger level, the hanging account method is adopted to achieve a serial posting method that is imperceptible to customers. The second method is to make an advance provision based on the repayment funds in transit according to the expected arrival date, and when the funds actually arrive, post according to the pre-provisioned amount. From the perspective of the technical architecture, the conventional financial scenario generally relies on the T+0 withholding method for fund inflow. Therefore, for the construction of the conventional financial scenario system, when the repayment action is completed, it means that the repayment plan is completed. However, for a large number of non-real-time repayment business scenarios, the existing repayment service processing solutions cannot fully meet the customer's repayment experience while ensuring the timeliness and accuracy of the repayment posting operation. Summary of the Invention

[0003] To solve the above technical problems, the present disclosure is proposed. Embodiments of the present disclosure provide a service processing method, apparatus, electronic device, and storage medium.

[0004] According to a first aspect of an embodiment of the present disclosure, a service processing method is provided, including: Step 1, receiving a repayment request sent by a user, and generating a repayment service operation packet corresponding to the repayment request; Step 2, if it is determined based on the repayment service operation packet that the repayment service corresponding to the repayment request is a non-real-time repayment service and the repayment service has not changed, generating service timing lock information corresponding to the repayment service based on the repayment service operation packet; Step 3, generating posting capacity lock information corresponding to the repayment service based on the repayment service operation packet; Step 4, performing posting operation processing corresponding to the repayment service on the repayment service operation packet according to the service timing lock information and the posting capacity lock information.

[0005] Optionally, if the repayment service changes, generating service change timing lock information corresponding to the repayment service; determining based on the repayment service operation packet whether to perform a corresponding repayment operation on the repayment service, if so, performing Step 2 to Step 4; if not, performing corresponding service change operation processing on the repayment service according to the service change timing lock information.

[0006] Optionally, generating a repayment service operation package corresponding to the received repayment request sent by the user includes: receiving a repayment plan request initiated by the user at the system access layer, generating query information based on the repayment plan request and sending it to the repayment plan layer; returning the repayment calculation information obtained by the repayment plan layer based on the query information to the system access layer; receiving the repayment request submitted by the user at the system access layer according to the repayment plan information and transmitting it to the revenue and expenditure service layer; generating the repayment service operation package at the revenue and expenditure service layer; wherein, the information carried in the repayment service operation package includes: non-real-time repayment operation information, repayment amount, repayment date, arrival date of the designated repayment, and repayment method information; the repayment method information includes: early settlement, partial repayment information.

[0007] Optionally, generating service change time sequence lock information corresponding to the repayment service includes: sending the repayment service operation package to the repayment plan layer, and generating the service change time sequence lock information at the repayment plan layer based on the repayment service operation package; wherein, the service change time sequence lock information includes: service structure change operation application time, service type, first lock serial number, first service data; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique time stamp.

[0008] Optionally, performing corresponding service change operation processing on the repayment service includes: performing corresponding change operation processing on the repayment plan information at the repayment plan layer in the order of the first lock serial number; after the change operation processing is completed, performing corresponding release processing on the service change time sequence lock information; wherein, in the case of the same service type, the change operation processing starts from the final state of the repayment plan information after the previous change operation processing is completed.

[0009] Optionally, generating service time sequence lock information corresponding to the repayment service based on the repayment service operation package includes: sending the repayment service operation package to the repayment plan layer, and generating the service time sequence lock information at the repayment plan layer based on the repayment service operation package; wherein, the service time sequence lock information includes: structure change operation application time, repayment service operation application time, application for credit time, service type, second lock serial number, second service data; the second lock serial number is unique and continuous, and the repayment service operation application time is a unique time stamp.

[0010] Optionally, generating the bookkeeping capacity lock information corresponding to the repayment service based on the repayment service operation package includes: generating the bookkeeping capacity lock information based on the repayment service operation package at the repayment plan layer; wherein, the bookkeeping capacity lock information includes: the repayment service operation application time, the application bookkeeping time, the service type, the third lock serial number, the third service data, and the service amount data that needs to occupy the bookkeeping capacity; the third lock serial number is unique and continuous; if there are multiple attributes that need to occupy the bookkeeping capacity in the third service data, then set the corresponding bookkeeping capacity for each attribute, and when setting the bookkeeping capacity lock information, determine the bookkeeping capacity to be occupied based on the bookkeeping capacity information after the previous bookkeeping capacity lock information is generated.

[0011] Optionally, after generating the bookkeeping capacity lock information, lock the corresponding bookkeeping capacity quota for the repayment to be booked based on the bookkeeping capacity lock information.

[0012] Optionally, according to the service time sequence lock information and the bookkeeping capacity lock information, performing the bookkeeping operation processing corresponding to the repayment service on the repayment service operation package includes: in the order of the second lock serial number and the third lock serial number, when the application bookkeeping time arrives, perform the corresponding bookkeeping operation on the repayment service at the core ledger layer; wherein, when performing the bookkeeping operation, use the accounting status after the previous bookkeeping operation as the starting status.

[0013] Optionally, after the bookkeeping operation processing is completed, perform corresponding release processing on the service change time sequence lock information, the service time sequence lock information, and the bookkeeping capacity lock information corresponding to the bookkeeping operation processing.

[0014] Optionally, when the preset bookkeeping result acquisition time arrives, obtain the bookkeeping result data corresponding to the bookkeeping operation, and update the repayment plan information; return the bookkeeping result data and the repayment plan information to the system access layer.

[0015] According to the second aspect of the embodiments of the present disclosure, a service processing device is provided, including: an operation package generation module, configured to receive a repayment request sent by a user, and generate a repayment service operation package corresponding to the repayment request; a service lock processing module, configured to, if it is determined based on the repayment service operation package that the repayment service corresponding to the repayment request is a non-real-time repayment service and the repayment service has not changed, generate service time sequence lock information corresponding to the repayment service based on the repayment service operation package; a capacity lock processing module, configured to generate bookkeeping capacity lock information corresponding to the repayment service based on the repayment service operation package; and a bookkeeping operation module, configured to perform bookkeeping operation processing corresponding to the repayment service on the repayment service operation package according to the service time sequence lock information and the bookkeeping capacity lock information.

[0016] Optionally, a change lock processing module is configured to generate service change timing lock information corresponding to the repayment service if the repayment service changes; determine whether to perform corresponding repayment operations on the repayment service based on the repayment service operation package, and if so, execute the functions of the service lock processing module, the capacity lock processing module, and the posting operation module; if not, perform corresponding service change operation processing on the repayment service according to the service change timing lock information.

[0017] Optionally, the operation package generation module is specifically configured to receive a repayment plan request initiated by the user at the system access layer, generate query information based on the repayment plan request and send it to the repayment plan layer; return the repayment calculation information obtained by the repayment plan layer based on the query information to the system access layer; receive the repayment request submitted by the user at the system access layer according to the repayment plan information and transmit it to the revenue and expenditure service layer; generate the repayment service operation package at the revenue and expenditure service layer; wherein, the information carried in the repayment service operation package includes: non-real-time repayment operation information, repayment amount, repayment date, due date of designated repayment, and repayment method information; the repayment method information includes: early settlement and partial repayment information.

[0018] Optionally, the change lock processing module is configured to send the repayment service operation package to the repayment plan layer, and generate the service change timing lock information at the repayment plan layer based on the repayment service operation package; wherein, the service change timing lock information includes: service structure change operation application time, service type, first lock serial number, and first service data; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique timestamp.

[0019] Optionally, the change lock processing module is further configured to perform corresponding change operation processing on the repayment plan information at the repayment plan layer in the order of the first lock serial number; after the change operation processing is completed, perform corresponding release processing on the service change timing lock information; wherein, in the case of the same service type, the change operation processing starts from the final state of the repayment plan information after the previous change operation processing is completed.

[0020] Optionally, the service lock processing module is specifically configured to send the repayment service operation package to the repayment plan layer, and generate the service timing lock information based on the repayment service operation package in the repayment plan layer; wherein, the service timing lock information includes: structure change operation application time, repayment service operation application time, application for posting time, service type, second lock serial number, and second service data; the second lock serial number is unique and continuous, and the repayment service operation application time is a unique timestamp.

[0021] Optionally, the capacity lock processing module is specifically configured to generate the posting capacity lock information based on the repayment service operation package in the repayment plan layer; wherein, the posting capacity lock information includes: repayment service operation application time, application for posting time, service type, third lock serial number, third service data, and business amount data that needs to occupy the ledger capacity; the third lock serial number is unique and continuous; if there are multiple attributes that need to occupy the ledger capacity in the third service data, then the corresponding ledger capacity is set for each attribute, and when setting the posting capacity lock information, the ledger capacity information after the previous posting capacity lock information is generated is used to determine the ledger capacity to be occupied.

[0022] Optionally, the capacity lock processing module is further configured to lock the corresponding accounting capacity quota for the repayment to be posted based on the posting capacity lock information after generating the posting capacity lock information.

[0023] Optionally, the posting operation module is specifically configured to perform the corresponding posting operation on the repayment service in the core ledger layer when the application for posting time arrives, in the order of the second lock serial number and the third lock serial number; wherein, when performing the posting operation, the accounting status after the previous posting operation is completed is used as the starting status.

[0024] Optionally, the posting operation module is further configured to perform corresponding release processing on the service change timing lock information, service timing lock information, and posting capacity lock information corresponding to the posting operation processing after the posting operation processing is completed.

[0025] Optionally, the posting operation module is further configured to obtain the posting result data corresponding to the posting operation and update the repayment plan information when the preset posting result acquisition time arrives; and return the posting result data and the repayment plan information to the system access layer.

[0026] According to the third aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, and the storage medium stores a computer program, and the computer program is used to execute the above method.

[0027] According to a fourth aspect of the embodiments of the present disclosure, an electronic device is provided, which includes: a processor; a memory for storing executable instructions of the processor; and the processor for executing the above-mentioned method.

[0028] Based on the service processing method, device, electronic device, and storage medium provided in the above embodiments of the present disclosure, service timing lock information and entry capacity lock information corresponding to the repayment service are generated based on the repayment service operation package. According to the service timing lock information and the entry capacity lock information, entry operation processing corresponding to the repayment service is performed; the accuracy of the accounting entry timing depending on the service operation time is ensured through the timing lock information, and the non-duplication and non-omission of the repayment service entry amount are ensured through the entry capacity lock information, which can prevent duplicate entries and incorrect entries; the effective control of the entry timing and entry capacity is carried out through the timing lock information and the entry capacity lock information. At the system level, the multi-dimensional and high-concurrency problems between service operations and system interactions are effectively solved. At the data level, the high consistency of service operations, the fund collection link, and the underlying data flow of the system is strongly guaranteed.

[0029] The technical solution of the present disclosure will be further described in detail below with reference to the drawings and embodiments. Description of the Drawings

[0030] By describing the embodiments of the present disclosure in more detail in conjunction with the drawings, the above-mentioned and other objects, features, and advantages of the present disclosure will become more obvious. The drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation to the present disclosure. In the drawings, the same reference numerals generally represent the same components or steps.

[0031] Figure 1 It is a flowchart of an embodiment of the service processing method of the present disclosure;

[0032] Figure 2 It is a flowchart of generating a repayment service operation package in an embodiment of the service processing method of the present disclosure;

[0033] Figure 3 It is a flowchart of performing service change processing in an embodiment of the service processing method of the present disclosure;

[0034] Figure 4 It is a flowchart of performing an entry operation in an embodiment of the service processing method of the present disclosure;

[0035] Figure 5 It is a schematic diagram of the timing steps of an embodiment of the service processing method of the present disclosure;

[0036] Figure 6Structural schematic diagram of an embodiment of the service processing device of the present disclosure;

[0037] Figure 7 Structural schematic diagram of another embodiment of the service processing device of the present disclosure;

[0038] Figure 8 It is a structural diagram of an embodiment of the electronic device of the present disclosure. Detailed implementation manners

[0039] Hereinafter, exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all embodiments of the present disclosure. It should be understood that the present disclosure is not limited by the exemplary embodiments described herein.

[0040] It should be noted that: unless otherwise specifically stated, the relative arrangements, numerical expressions and values of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0041] Those skilled in the art can understand that the terms "first", "second", etc. in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc., and neither represent any specific technical meaning nor indicate an inevitable logical order between them.

[0042] It should also be understood that in the embodiments of the present disclosure, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0043] It should also be understood that for any component, data or structure mentioned in the embodiments of the present disclosure, unless clearly defined or given a contrary indication in the context, it can generally be understood as one or more.

[0044] In addition, the term "and / or" in the present disclosure is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present disclosure generally represents an "or" relationship between the associated objects before and after.

[0045] It should also be understood that the present disclosure emphasizes the differences between the various embodiments. Their similarities or similarities can be referred to each other. For the sake of brevity, they will not be described one by one.

[0046] At the same time, it should be understood that for the sake of description, the dimensions of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0047] The following description of at least one exemplary embodiment is actually only illustrative and in no way limits the present disclosure and its application or use.

[0048] Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods, and devices should be considered as part of the specification.

[0049] It should be noted that like reference numerals and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

[0050] Embodiments of the present disclosure can be applied to electronic devices such as terminal devices, computer systems, servers, etc., which can operate with many other general or special computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments, and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, or servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, minicomputer systems, mainframe computer systems, and distributed cloud computing technology environments including any of the above systems, etc.

[0051] Terminal devices, computer systems, servers, and other electronic devices can be described in the general context of computer system-executable instructions, such as program modules, executed by a computer system. Generally, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. The computer system / server can be implemented in a distributed cloud computing environment. In a distributed cloud computing environment, tasks can be executed by remote processing devices linked through a communication network. In a distributed cloud computing environment, program modules can be located on local or remote computing system storage media including storage devices.

[0052] Application Overview

[0053] In the process of implementing the present disclosure, the inventors found that for a large number of non-real-time repayment business scenarios, the existing repayment processing solutions cannot fully meet the customer repayment experience while ensuring the timeliness and accuracy of the repayment posting operation. Therefore, a new repayment business processing solution is needed.

[0054] The business processing method provided by the present disclosure generates a repayment business operation package corresponding to a repayment request. If it is determined based on the repayment business operation package that the repayment business corresponding to the repayment request is a non-real-time repayment business and the repayment business has not changed, then business timing lock information and account entry capacity lock information corresponding to the repayment business are generated based on the repayment business operation package. According to the business timing lock information and the account entry capacity lock information, account entry operation processing corresponding to the repayment business is performed; the accuracy of the accounting entry timing of the accounts depending on the business operation time is ensured through the timing lock information, and the non-duplication and non-omission of the repayment business account entry amount are ensured through the account entry capacity lock information, and the problems of duplicate account entry and incorrect account entry can be prevented.

[0055] Exemplary Method

[0056] The step numbers in the present disclosure, such as "Step 1", "Step 2", "S101", "S102", etc., are only for distinguishing different steps and do not represent the sequence of execution between steps. Steps with different numbers can be adjusted in order when executed.

[0057] In the technologies known to the inventors, for the account entry of non-real-time arrival repayment business, the following two methods are usually adopted to prevent duplicate account entry and incorrect account entry:

[0058] The first method: control at the account entry operation level, that is, when there is outstanding repayment funds in transit, or at the business operation level, no further repayment business operation is allowed, or the hanging account method is adopted at the ledger level to achieve a serial account entry method that is imperceptible to customers. These two methods essentially control the serialization of business operations through manual or system means, which will directly affect the customer experience. Moreover, due to the time difference between the repayment action at the business operation level and the account entry of funds, additional capital costs will be caused, resulting in customer complaints. In severe cases, when the customer's repayment is insufficient to balance the accounts, the business party has to make up the shortfall, resulting in capital losses.

[0059] The second method: based on the repayment funds in transit, make an advance provision according to the expected arrival date, and when the funds actually arrive, make an account entry according to the pre-provisioned amount. This method takes into account both the customer repayment business experience and the problem of avoiding incorrect account entry. However, the vast majority of repayment businesses are based on the amount that should be repaid but has not been repaid at the repayment time point, and it is usually clearly stated in the loan-related agreement that the repayment is based on the amount that should be repaid but has not been repaid, rather than the advance provision billing calculation based on the repayment funds in transit. Therefore, this repayment control method violates the actual business scenario and is difficult to match the requirements of the loan agreement. If the corresponding legal text agreement is modified, it is not only difficult to convince customers, but also does not conform to the industry's common agreed method, which is not conducive to business expansion and system backward compatibility; if it is not modified, there is a difference between the actual billing method and the contractually agreed method, and there are potential regulatory risks.

[0060] In terms of the technical architecture, the existing financial scenarios generally rely on the T+0 withholding method for fund inflow. From the perspective of the atomicity of the business, when the batch withholding is completed, the repayment business is completed. Therefore, for the construction of the existing financial scenario system, when the repayment action is completed, it means that the repayment plan has been completed. The system can manage the repayment behavior and the completion of the repayment plan in the same business transaction at the underlying level. However, due to the existence of a large number of non-real-time repayment business scenarios, and the two business scenarios of the repayment action and the repayment of the repayment plan cannot be managed within one atomic business transaction, and due to the existence of a large number of large-value payment scenarios, card limits are bound to occur.

[0061] The solution of the existing system for the above situation is to reverse-infer the result based on the action. Every time there is a repayment action, the associated scenario is reversely judged, and the amount is accumulated to reverse-infer the final state. However, for special scenarios, when the next action depends on the result of the previous time, the system has to perform serial processing, reject the business action behavior, or use special repayment channels. For example, for the scenario of combined use of the T+1 channel and the T+0 channel, the system has to roll back some T+0 fund inflow operations to ensure final consistency. Currently, non-real-time repayment services are increasing, but the existing solutions cannot fully meet the customer's repayment experience while ensuring the timeliness and accuracy of the system's repayment posting operations.

[0062] The present disclosure proposes a business processing method that provides an anti-duplication and anti-error mechanism based on a time sequence lock and a capacity lock, which can well solve the repayment business with a specified arrival date for non-real-time arrival. Figure 1 It is a flowchart of an embodiment of the business processing method of the present disclosure, as Figure 1 shown, the method includes steps: S101 - S104. Each step will be described separately below.

[0063] S101, receive a repayment request sent by a user, and generate a repayment business operation package corresponding to the repayment request.

[0064] S102, in response to determining that the repayment business corresponding to the repayment request based on the repayment business operation package is a non-real-time repayment business and the repayment business has not changed, generate business time sequence lock information corresponding to the repayment business based on the repayment business operation package.

[0065] In one embodiment, there are multiple repayment services, such as real-time repayment service, non-real-time repayment service, etc. The repayment service information includes repayment date, repayment operation, etc. All repayment service information is stored in advance. When a repayment service operation packet is received, based on information such as the user name and ID number of the service, the pre-stored repayment service information corresponding to the operation packet is determined. Based on the pre-stored repayment service information, it is judged whether attributes such as the repayment date and repayment operation of the repayment service corresponding to the repayment request have changed. If changed, it is determined that the repayment service has changed; if not changed, the repayment service has not changed. The non-real-time repayment service means that the amount repaid by the user needs to be recorded at the specified repayment arrival time. The repayment service data packet carries the repayment service information submitted by the user, including non-real-time repayment operation information, repayment date, specified repayment arrival date, etc.

[0066] When attributes such as the repayment date, repayment method, and repayment amount of the repayment service have not changed, it is determined that the repayment service has not changed; when at least one of the attributes such as the repayment date, repayment method, and repayment amount of the repayment service has changed, it is determined that the repayment service has changed.

[0067] When the repayment service has not changed, generate service time sequence lock information corresponding to the repayment service based on the repayment service operation packet. The service time sequence lock information corresponds one-to-one with the repayment service and includes information such as service type, lock serial number, service data, etc. The service data includes repayment operation information, repayment amount, repayment date, specified repayment arrival date, etc. After the service time sequence lock information is generated, it can be stored in a file or database, which plays the function of a time sequence lock for the recording operation of the repayment service and can control the execution time sequence of multiple recording operations of the repayment service.

[0068] S103, generate recording capacity lock information corresponding to the repayment service based on the repayment service operation packet.

[0069] In one embodiment, after the service time sequence lock information is generated, generate recording capacity lock information based on the information in the repayment service operation packet. The recording capacity lock information corresponds one-to-one with the repayment service and includes service type, lock serial number, recording time, service data, etc. The service data includes repayment date, repayment amount, specified repayment arrival date, etc.

[0070] The ledger capacity can be the amount that can still collect the user's repayment. For example, without considering fee items such as interest and overdue fees and only considering the principal, assuming that Customer A takes a loan of 100,000 yuan and has repaid 10,000 yuan, then the ledger capacity at this time is 90,000 yuan, that is, the maximum amount that can be collected from the user for repayment is 90,000 yuan. By setting an incoming capacity lock to control operations such as the occupation and release of the ledger capacity by the repayment business, it is possible to avoid overcharging or mischarging the user for the repayment amount. After the incoming capacity lock information is generated, it can be stored in a file or database, and it functions as an account capacity lock for the operations of the repayment business, and can control the order of operations such as the occupation and release of the ledger capacity by the repayment business.

[0071] S104. According to the service timing lock information and the incoming capacity lock information, perform incoming operation processing corresponding to the repayment service on the repayment service operation package.

[0072] In one embodiment, if the repayment service changes, corresponding service change timing lock information is generated. The service change timing lock information corresponds one-to-one with the repayment service and includes service type, lock serial number, service data, etc. The service data includes change information of attributes such as the repayment date, repayment method, and repayment amount of the repayment service. After the service change timing lock information is generated, it can be stored in a file or database, and it functions as a timing lock for controlling service changes for the operations of the repayment service, and can control the order of operations for the repayment service change (including changes in attributes such as service type, repayment date, repayment method, repayment amount, etc.).

[0073] Based on the repayment service operation package, determine whether to perform corresponding repayment operations on the repayment service. If so, execute steps 102 to 104; if not, perform corresponding service change operation processing on the repayment service according to the service change timing lock information.

[0074] In one embodiment, multiple methods can be used to generate a repayment service operation package corresponding to a repayment request. Figure 2 For an embodiment of the service processing method of the present disclosure, it is a flowchart for generating a repayment service operation package. As Figure 2 shown, the method includes steps: S201 - S204. Each step will be described separately below.

[0075] S201. Receive the repayment plan request initiated by the user at the system access layer, generate query information based on the repayment plan request, and send it to the repayment plan layer.

[0076] S202. Return the repayment calculation information obtained by the repayment plan layer based on the query information to the system access layer.

[0077] In one embodiment, the business operator initiates a business operation at the system access layer, submits a repayment plan request, a request for repayment information, or a trial repayment result, providing a basis for the formal repayment business operation; generates a query message based on the repayment plan request and sends it to the repayment plan layer. The repayment plan layer obtains or calculates the repayment plan information according to the query conditions and returns it to the system access layer.

[0078] The system access layer is a system interface directly facing users and can be in the form of an APP / website / client, etc. The system access layer is a logically virtual layer and can be deployed on different or the same hardware devices as other layers. The repayment plan layer is a layer that isolates the underlying ledger processing layer of the system from the upper-layer business operations. The upper-layer business operations can include repayment operations performed by users, etc. The repayment plan layer faces system functions rather than business, parses business requests into system functions, and performs necessary rule parsing, function reuse, and other processing. The repayment plan layer is a logically virtual layer and can be deployed on different or the same hardware devices as other layers.

[0079] S203, receives the repayment request submitted by the user at the system access layer according to the repayment plan information and transmits it to the revenue and expenditure service layer.

[0080] In one embodiment, the system access layer obtains the repayment request submitted by the user at the system access layer. The business data included in the repayment request includes the repayment amount, repayment date, arrival date of the specified repayment, and repayment method data such as early settlement, partial repayment, and overdue repayment, and transmits it to the revenue and expenditure service layer.

[0081] The revenue and expenditure service layer is an abstract layer for serving financial revenue and expenditure, is a logically virtual layer, and can be deployed on different or the same hardware devices as other layers. In system design, the revenue and expenditure service layer may be integrated with the repayment plan layer or the system access layer. The revenue and expenditure service layer creates a repayment business operation package based on the business data uploaded by the system access layer. The repayment business operation package contains various information related to the repayment business.

[0082] S204, generates a repayment business operation package at the revenue and expenditure service layer. The information carried by the repayment business operation package includes non-real-time repayment operation information, repayment amount, repayment date, arrival date of the specified repayment, and repayment method information, etc.; the repayment method information includes: early settlement, partial repayment information, etc.

[0083] In one embodiment, multiple methods can be used to generate service change time sequence lock information corresponding to the repayment service. For example, send the repayment service operation package to the repayment plan layer, and generate service change time sequence lock information based on the repayment service operation package at the repayment plan layer. The service change time sequence lock information includes: the service structure change operation application time, service type, first lock serial number, first service data, etc.; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique timestamp. The value of the service type can be loan repayment, etc., and the service data can include the repayment date, repayment method, repayment amount, etc.

[0084] Multiple methods can be used to perform corresponding service change operation processing on the repayment service. Figure 3 This is a flowchart of performing service change processing in an embodiment of the service processing method of the present disclosure, as Figure 3 shown in the method including steps: S301 - S302. Each step will be described separately below.

[0085] S301, according to the order of the first lock serial number, perform corresponding change operation processing on the repayment plan information at the repayment plan layer. For example, based on the order from small to large of the first lock serial number, perform corresponding change operation processing on the repayment plan information at the repayment plan layer to generate new repayment plan information.

[0086] S302, after the change operation processing is completed, perform corresponding release processing on the service change time sequence lock information; among them, in the case of the same service type, the change operation processing starts from the final state of the repayment plan information after the previous change operation processing is completed.

[0087] For example, at the repayment plan layer, according to the repayment service operation package data, determine whether there is a service structure change. A service structure change means that one or more attributes among the repayment date, repayment method, repayment amount, etc. have changed.

[0088] If there is a service structure change, generate service change time sequence lock information: generate service (structure) change time sequence lock lock-i <structure change operation application time CTime, service type Type, (first) lock serial number No, service data Links> according to information such as service type and time sequence; the smaller the serial number of the lock serial number No, the higher the priority, and it is unique and continuous; the service operation application time CTime is a unique timestamp, and when the service type Type is the same, the lock serial number No is unique and continuous; when the service types Type are different, the service locks lock-i are independent of each other to ensure multi-dimensions and high concurrency of the revenue and expenditure layer.

[0089] The business change time sequence lock is a lock generated based on the business request type and request time, which can ensure the same type of business requests and guarantee the efficient, orderly and concurrent processing of business according to the time sequence. After judging the business structure change, check whether there are subsequent business operations. If there are no subsequent business operations, change the repayment plan structure in sequence according to the lock serial number No of the time sequence lock lock-i.

[0090] Perform corresponding change operation processing on the repayment plan information at the repayment plan layer. When the business type Type is the same, each change starts from the final state after the previous change is completed. If there are subsequent business operations, execute the above steps S102 - S104.

[0091] In one embodiment, multiple methods can be used to generate business time sequence lock information corresponding to the repayment business. Send the repayment business operation package to the repayment plan layer, and generate business time sequence lock information at the repayment plan layer based on the repayment business operation package. The business time sequence lock information includes: structure change operation application time, repayment business operation application time, application posting time, business type, second lock serial number, second business data, etc.; the second lock serial number is unique and continuous, and the repayment business operation application time is a unique timestamp. If there is no change in the repayment business, the value of the structure change operation application time is empty, the value of the business type can be loan repayment, etc., and the second business data can include repayment date, repayment method, repayment amount, etc.

[0092] For example, generate a business time sequence lock: Generate a business time sequence lock lock-i << structure change operation application time CTime, business operation application time STime, application posting time ETime, business type Type, lock serial number (second lock serial number) No, business data (second business data) Links >> according to the structure change application time, business type, and time sequence; the smaller the serial number digit of the lock serial number No, the higher the priority, and it is unique and continuous; the business operation application time STime is a unique timestamp, and when the business type Type and the application posting time ETime are the same, the lock serial number No is unique and continuous; only when the applied posting dates are the same, the date attributes of the application posting time ETime are the same; when the business types Type are different, the business locks lock-j are independent of each other to ensure the multi-dimensionality and high concurrency of the revenue and expenditure layer.

[0093] In one embodiment, various methods can be used to generate the book entry capacity lock information corresponding to the repayment service. The book entry capacity lock is used in the business application process to pre-apply for the book entry capacity quota of the ledger. Once the application is approved, it is only used for this business application, and the remaining available capacity of the ledger is correspondingly reduced. According to the ledger capacity required for each business, before the business occurs and is officially recorded in the ledger, an application for the book entry capacity lock is made to lock in advance the ledger quota capacity required for the final book entry, and the available capacity of the ledger is correspondingly reduced. In the embodiments of the present application, the ledger capacity is the quota of the amount, for example, the amount that can be charged to the user for repayment.

[0094] Generate the book entry capacity lock information based on the repayment service operation package at the repayment plan layer. The book entry capacity lock information includes: the application time of the repayment service operation, the application time for book entry, the business type, the third lock serial number, the third business data, the business amount data of the business amount that needs to occupy the ledger capacity, etc. The third lock serial number is unique and continuous; the value of the business type can be loan repayment, etc., and the third business data can include the repayment date, repayment method, repayment amount, etc.

[0095] If there are multiple attributes that need to occupy the ledger capacity in the third business data (multiple remittance operations are required), then set the corresponding ledger capacity for each attribute. And when setting the book entry capacity lock information, determine the ledger capacity to be occupied based on the ledger capacity information after the generation of the previous book entry capacity lock information. After generating the book entry capacity lock information, lock the corresponding accounting capacity quota for the outstanding repayment book entry based on the book entry capacity lock information. The business financial data that needs to occupy the ledger capacity is the amount data that exists in the business data and is associated with the business and needs to occupy the ledger capacity. For example, the business amount data can be the amount data of the expense items required for handling loan business, handling early loan repayment and other businesses.

[0096] For example, generate the book entry capacity lock for the repayment service: Generate the book entry capacity lock lock-k << the application time of the structure change application, (repayment) business operation application time, application time for book entry, business type, third lock serial number, third business data, other business data that needs to occupy the ledger capacity >> according to the structure change application time, business type, and time sequence; the smaller the serial number digit of the third lock serial number No, the higher the priority, and it is unique and continuous; the business operation application time STime is a unique timestamp. When the business type Type and the application time for book entry ETime are the same, the lock serial number No is unique and continuous; when and only when the applied book entry dates are the same, the date attribute of the application time for book entry ETime is the same; when there are several attributes that need to occupy the ledger capacity in the third business data Links, there should be corresponding Size-k one by one, and each capacity lock lock-k takes the final state after the production of the previous lock-k as the initial state.

[0097] There are various methods to perform the posting operation processing corresponding to the repayment business on the repayment business operation package. Figure 4 It is a flowchart of performing the posting operation in an embodiment of the business processing method of the present disclosure, as Figure 4 shown, the method includes steps: S401 - S404. Each step will be described separately below.

[0098] S401, in the order of the first lock serial number and the second lock serial number, when the application posting time arrives, perform the corresponding posting operation on the repayment business in the core ledger layer; wherein, when performing the posting operation, the accounting status after the previous posting operation is used as the starting state.

[0099] For example, in the order from large to small of the first lock serial number and the corresponding second lock serial number, when the application posting time arrives, perform the corresponding posting operation on the repayment business in the core ledger layer.

[0100] S402, after the posting operation processing is completed, perform the corresponding release processing on the business change time sequence lock information, business time sequence lock information, and posting capacity lock information corresponding to the posting operation processing.

[0101] There are various release processing methods. For example, set the status flags of the business change time sequence lock information, business time sequence lock information, and posting capacity lock information to the released state, or delete the business change time sequence lock information, business time sequence lock information, and posting capacity lock information.

[0102] S403, when the preset posting result acquisition time arrives, obtain the posting result data corresponding to the posting operation and update the repayment plan information.

[0103] S404, return the posting result data and the repayment plan information to the system access layer.

[0104] For example, based on the lock serial number No order of the business time sequence lock lock - j, post in sequence. Each posting uses the final state after the previous posting as the starting state of the accounts receivable and received for accounting; after each posting is completed, perform the corresponding release processing on the business change time sequence lock information, business time sequence lock information, and posting capacity lock information corresponding to this repayment business.

[0105] After processing all the business to be posted on each posting day, there should be no business change time sequence lock information, business time sequence lock information, and posting capacity lock information for this posting day. For each posting day, there should be no business change time sequence lock information, business time sequence lock information, and posting capacity lock information with a posting day time attribute earlier than this posting day. At the end of the posting day, generate the posting result data information, update the repayment plan information, and return the posting result information to the system access layer according to the posting result and business operation conditions.

[0106] In one embodiment, as Figure 5 shown, in the repayment application stage, based on Steps 1 and 2, the business operator initiates a request to query the repayment plan / repayment trial calculation / repayment application through the system access layer; based on Steps 3, 4, and 5, the system revenue and expenditure service layer creates a repayment application package according to the business data and initiates a repayment application to the repayment plan layer.

[0107] In the repayment application business lock creation stage, based on Steps 6-10, the repayment plan layer selects to create a business change time sequence lock and a business time sequence lock according to the business type, and creates a repayment application record to confirm information such as the arrival date. In the repayment application capacity lock stage, based on Steps 11-13, the repayment plan layer splits the expense items according to the repayment data information, creates a capacity lock, locks the accounting capacity limit of the outstanding repayment to be recorded, and the core ledger layer detects the capacity lock and performs the hanging account process.

[0108] In the stage of performing the repayment operation, a request is sent through the system access layer to channels such as POS and cash registers for repayment. The revenue and expenditure service layer establishes a repayment payment order according to the request and returns payment voucher information such as the POS code and the cash register address. Based on Steps 14-17, the business operator completes the payment operation in the system access layer; in Step 18, the payment system completes the payment process according to the payment operation information and returns the payment completion notice information to the system access layer; in Step 19, the system revenue and expenditure service layer checks the final state of the payment business, and in Step 20, after the repayment is completed, the completion information is notified to the repayment plan layer.

[0109] In the repayment recording stage, in Steps 21-23, the repayment plan layer sequentially applies to the core ledger layer for write-off and recording according to the change situation of the repayment business structure, the business change time sequence lock, and the business time sequence lock; in Steps 24 and 25, the core ledger layer records in sequence according to the recording time sequence and the business capacity lock. After the recording is completed, the capacity lock is released and the recording confirmation is performed. In Steps 26 and 27, after the repayment plan layer obtains the successful recording information, it releases the structure change time sequence lock, the business time sequence lock, etc., and performs the repayment completion business operation confirmation, and sends the repayment information update notice to the system access layer.

[0110] The business processing method in the above embodiments generates business timing lock information and posting capacity lock information corresponding to the repayment business based on the repayment business operation package, and performs posting operation processing corresponding to the repayment business according to the business timing lock information and the posting capacity lock information. The accuracy of the accounting posting timing that depends on the business operation time is ensured through the business timing lock information, and the non-duplication and non-omission of the repayment business posting amount are ensured through the posting capacity lock information, which can prevent duplicate posting and incorrect posting; at the system level, it effectively solves the multi-dimensional and high-concurrency problems between business operations and system interactions, and at the data level, it strongly guarantees the high consistency of business operations, the capital collection link, and the underlying data flow of the system.

[0111] Exemplary Device

[0112] In one embodiment, as Figure 6 shown, the present disclosure provides a business processing apparatus, including: an operation package generation module 61, a business lock processing module 62, a capacity lock processing module 63, and a posting operation module 64. The operation package generation module 61 receives a repayment request sent by a user and generates a repayment business operation package corresponding to the repayment request.

[0113] If it is determined based on the repayment business operation package that the repayment business corresponding to the repayment request is a non-real-time repayment business and the repayment business has not changed, the business lock processing module 62 generates business timing lock information corresponding to the repayment business based on the repayment business operation package. The capacity lock processing module 63 generates posting capacity lock information corresponding to the repayment business based on the repayment business operation package. The posting operation module 64 performs posting operation processing corresponding to the repayment business on the repayment business operation package according to the business timing lock information and the posting capacity lock information.

[0114] In one embodiment, as Figure 7 shown, the business processing apparatus further includes a change lock processing module 65. If the repayment business changes, the change lock processing module 65 generates business change timing lock information corresponding to the repayment business. The change lock processing module 65 determines whether to perform a corresponding repayment operation on the repayment business based on the repayment business operation package. If so, it executes the functions of the business lock processing module 62, the capacity lock processing module 63, and the posting operation module 64; if not, the change lock processing module 65 performs corresponding business change operation processing on the repayment business according to the business change timing lock information.

[0115] The operation package generation module 61 receives a repayment plan request initiated by a user at the system access layer, generates query information based on the repayment plan request, and sends it to the repayment plan layer. The operation package generation module 61 returns the repayment calculation information obtained by the repayment plan layer based on the query information to the system access layer. The operation package generation module 61 receives a repayment request submitted by the user at the system access layer according to the repayment plan information and transmits it to the revenue and expenditure service layer. The operation package generation module 61 generates a repayment service operation package at the revenue and expenditure service layer. The information carried by the repayment service operation package includes: non-real-time repayment operation information, repayment amount, repayment date, arrival date of the designated repayment, and repayment method information, etc.; the repayment method information includes: early settlement, partial repayment information, etc.

[0116] The change lock processing module 65 sends the repayment service operation package to the repayment plan layer, and generates business change timing lock information at the repayment plan layer based on the repayment service operation package; among them, the business change timing lock information includes: business structure change operation application time, business type, first lock serial number, first business data, etc.; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique time stamp, etc.

[0117] The change lock processing module 65 performs corresponding change operation processing on the repayment plan information at the repayment plan layer in the order of the first lock serial number. After the change operation processing is completed, the change lock processing module 65 performs corresponding release processing on the business change timing lock information; among them, in the case of the same business type, the change operation processing uses the final state of the repayment plan information after the previous change operation processing as the starting state.

[0118] In one embodiment, the business lock processing module 62 sends the repayment service operation package to the repayment plan layer, and generates business timing lock information at the repayment plan layer based on the repayment service operation package; among them, the business timing lock information includes: structure change operation application time, repayment service operation application time, application for posting time, business type, second lock serial number, second business data, etc.; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique time stamp.

[0119] The capacity lock processing module 63 generates the book entry capacity lock information based on the repayment service operation package at the repayment plan layer. The book entry capacity lock information includes: the application time of the repayment service operation, the application book entry time, the service type, the third lock serial number, the third service data, and other service data that needs to occupy the ledger capacity, etc. The third lock serial number is unique and continuous; if there are multiple attributes in the third service data that need to occupy the ledger capacity, the capacity lock processing module 63 sets the corresponding ledger capacity for each attribute. Moreover, when setting the book entry capacity lock information, the capacity lock processing module 63 determines the ledger capacity to be occupied based on the ledger capacity information after the generation of the previous book entry capacity lock information. After generating the book entry capacity lock information, the capacity lock processing module 63 locks the corresponding bookkeeping capacity quota for the repayment to be entered into the account based on the book entry capacity lock information.

[0120] In one embodiment, the book entry operation module 64 performs the corresponding book entry operation on the repayment service at the core ledger layer in the order of the first lock serial number and the second lock serial number when the application book entry time arrives; wherein, when performing the book entry operation, the accounting status after the previous book entry operation is used as the starting status.

[0121] After the book entry operation processing is completed, the book entry operation module 64 performs corresponding release processing on the service change time sequence lock information, service time sequence lock information, and book entry capacity lock information corresponding to the book entry operation processing. When the preset book entry result acquisition time arrives, the book entry operation module 64 acquires the book entry result data corresponding to the book entry operation and updates the repayment plan information; the book entry operation module 64 returns the book entry result data and the repayment plan information to the system access layer.

[0122] The service processing device in the above embodiment generates the service time sequence lock information and book entry capacity lock information corresponding to the repayment service based on the repayment service operation package, and performs the corresponding book entry operation processing for the repayment service according to the service time sequence lock information and the book entry capacity lock information. The accuracy of the bookkeeping time sequence of the accounts depending on the service operation time is ensured through the service time sequence lock information, and the non-duplication and non-omission of the repayment service book entry amount are ensured through the book entry capacity lock information, which can prevent duplicate book entry and incorrect book entry; effectively solves the multi-dimensional and high-concurrency problems between service operations and system interactions; and strongly guarantees the high consistency of service operations, the capital collection link, and the underlying data flow of the system.

[0123] Figure 8 is a structural diagram of an embodiment of the electronic device of the present disclosure, as Figure 8 shown, the electronic device 81 includes one or more processors 811 and a memory 812.

[0124] The processor 811 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 81 to perform desired functions.

[0125] The memory 812 may include one or more computer program products, and the computer program products may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory, for example, may include: random access memory (RAM) and / or cache memory, etc. Non-volatile memory, for example, may include: read-only memory (ROM), hard disk, and flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage media, and the processor 811 may run the program instructions to implement the service processing methods of the various embodiments of the present disclosure above and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage media.

[0126] In one example, the electronic device 81 may further include: an input device 813 and an output device 814, etc., and these components are interconnected through a bus system and / or other forms of connection mechanisms (not shown). In addition, the input device 813 may further include, for example, a keyboard, a mouse, etc. The output device 814 may output various information to the outside. The output device 814 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0127] Of course, for simplicity, Figure 8 only some of the components in the electronic device 81 related to the present disclosure are shown, and components such as buses, input / output interfaces, etc. are omitted. In addition, according to specific application scenarios, the electronic device 81 may further include any other appropriate components.

[0128] In addition to the above methods and devices, the embodiments of the present disclosure may also be computer program products, which include computer program instructions that, when run by a processor, cause the processor to execute the steps in the service processing methods according to the various embodiments of the present disclosure described in the "Exemplary Methods" section above of this specification.

[0129] A computer program product may write program code for performing the operations of the embodiments of the present disclosure in any combination of one or more programming languages. The programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's device, executed as a stand-alone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0130] In addition, an embodiment of the present disclosure may also be a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are run by a processor, the processor is caused to execute the steps in the business processing methods according to various embodiments of the present disclosure described in the "Exemplary Methods" section above of this specification.

[0131] The computer-readable storage medium may adopt any combination of one or more readable media. The readable media may be a readable signal medium or a readable storage medium. The readable storage medium may, for example, include but is not limited to an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium may include: an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0132] The basic principles of the present disclosure have been described above in conjunction with specific embodiments. However, it should be noted that the advantages, benefits, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, benefits, and effects, etc. are essential for each embodiment of the present disclosure. In addition, the above-mentioned specific details are only for illustrative and easy-to-understand purposes and are not limitations. The above details do not limit the present disclosure to necessarily adopt the above specific details for implementation.

[0133] The business processing method, apparatus, electronic device, and storage medium in the above embodiments generate business timing lock information and posting capacity lock information corresponding to the repayment business based on the repayment business operation package, and perform posting operation processing corresponding to the repayment business according to the business timing lock information and the posting capacity lock information; the accuracy of the accounting posting timing dependent on the business operation time is ensured through the business timing lock information, and the non-duplication and non-omission of the repayment business posting amount are ensured through the posting capacity lock information, which can prevent duplicate posting and incorrect posting and perform effective control; at the system level, the multi-dimensional and high-concurrency problems between business operations and system interactions are effectively solved, and at the data level, the high consistency of business operations, the capital collection link, and the underlying data stream of the system is strongly guaranteed, effectively improving the customer experience.

[0134] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is the difference from other embodiments. The same or similar parts between each embodiment can be referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0135] The block diagrams of the devices, apparatuses, equipment, and systems involved in the present disclosure are only illustrative examples and do not intend to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any way. Words such as "including", "comprising", "having", etc. are open-ended words, meaning "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used herein refer to the word "and / or", and can be used interchangeably with it, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to", and can be used interchangeably with it.

[0136] The methods and apparatuses of the present disclosure can be implemented in many ways. For example, the methods and apparatuses of the present disclosure can be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of the steps for the method is only for illustration, and the steps of the method of the present disclosure are not limited to the specific order described above, unless otherwise specifically stated. In addition, in some embodiments, the present disclosure can also be implemented as a program recorded in a recording medium, and these programs include machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0137] It should also be noted that in the devices, equipment, and methods of the present disclosure, each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent solutions of the present disclosure.

[0138] The foregoing description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications etc. to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the aspects shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0139] The foregoing description has been presented for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although several example aspects and embodiments have been discussed above, those skilled in the art will recognize some variations, modifications, alterations, additions, and subcombinations thereof.

Claims

1. A business processing method, including: Step 1: Receive a repayment request sent by a user, and generate a repayment service operation package corresponding to the repayment request; Step 2: In response to determining that the repayment service corresponding to the repayment request is a non-real-time repayment service based on the repayment service operation package, and the repayment service has not changed, generate service timing lock information corresponding to the repayment service based on the repayment service operation package, where the service timing lock information is used to control the execution timing sequence of multiple posting operations of the repayment service, and the service timing lock information includes: service change operation application time, repayment service operation application time, application posting time, service type, second lock serial number, second service data, where service change means that one or more attributes among the repayment date, repayment method, and repayment amount change; Step 3: Generate posting capacity lock information corresponding to the repayment service based on the repayment service operation package, where the posting capacity lock information is used to control the order of operations of the repayment service on the ledger capacity, and the posting capacity lock information includes: repayment service operation application time, application posting time, service type, third lock serial number, third service data, and business amount data that needs to occupy the ledger capacity; Step 4: Perform posting operation processing corresponding to the repayment service on the repayment service operation package according to the service timing lock information and the posting capacity lock information; The performing posting operation processing corresponding to the repayment service on the repayment service operation package according to the service timing lock information and the posting capacity lock information includes: In the order of the second lock serial number and the third lock serial number, when the application posting time arrives, perform corresponding posting operations on the repayment service at the ledger layer; where, when performing the posting operation, use the accounting status after the previous posting operation as the starting status.

2. The method according to claim 1, further including: In response to the change of the repayment service, generate service change timing lock information corresponding to the repayment service; Based on the repayment service operation package, determine whether to perform corresponding repayment operations on the repayment service. If so, execute steps 2 to 4; If not, perform corresponding service change operation processing on the repayment service according to the service change timing lock information.

3. The method according to claim 2, where the receiving a repayment request sent by a user and generating a repayment service operation package corresponding to the repayment request includes: Receive a repayment plan request initiated by the user at the system access layer, generate query information based on the repayment plan request, and send it to the repayment plan layer; Return the repayment calculation information obtained by the repayment plan layer based on the query information to the system access layer; Receive the repayment request submitted by the user at the system access layer according to the repayment plan information, and transfer it to the revenue and expenditure service layer; Generate the repayment service operation package at the revenue and expenditure service layer; Among them, the information carried by the repayment service operation package includes: non-real-time repayment operation information, repayment amount, repayment date, arrival date of the designated repayment, and repayment method information.

4. The method as claimed in claim 3, wherein generating the service change time sequence lock information corresponding to the repayment service includes: Sending the repayment service operation package to the repayment plan layer, and generating the service change time sequence lock information in the repayment plan layer based on the repayment service operation package; Among them, the service change time sequence lock information includes: service change operation application time, service type, first lock serial number, and first service data; the first lock serial number is unique and continuous, and the repayment service operation application time is a unique timestamp.

5. The method as claimed in claim 4, wherein performing corresponding service change operation processing on the repayment service includes: Performing corresponding change operation processing on the repayment plan information in the repayment plan layer in the order of the first lock serial number; After the change operation processing is completed, performing corresponding release processing on the service change time sequence lock information; Among them, in the case where the service types are the same, the change operation processing starts from the final state of the repayment plan information after the previous change operation processing is completed.

6. The method as claimed in claim 3, wherein generating the service time sequence lock information corresponding to the repayment service based on the repayment service operation package includes: Sending the repayment service operation package to the repayment plan layer, and generating the service time sequence lock information in the repayment plan layer based on the repayment service operation package; Among them, the second lock serial number is unique and continuous, and the repayment service operation application time is a unique timestamp.

7. The method as claimed in claim 6, wherein generating the account entry capacity lock information corresponding to the repayment service based on the repayment service operation package includes: Generating the account entry capacity lock information in the repayment plan layer based on the repayment service operation package; Among them, the third lock serial number is unique and continuous; if there are multiple attributes that need to occupy the ledger capacity in the third service data, then set the corresponding ledger capacity for each attribute, and determine the ledger capacity to be occupied based on the ledger capacity information after the previous account entry capacity lock information is generated, so as to set the account entry capacity lock information.

8. The method as claimed in claim 7, further includes: After generating the account entry capacity lock information, locking the corresponding account entry capacity quota for the repayment to be made based on the account entry capacity lock information.

9. The method as claimed in claim 8, further includes: After the account entry operation processing is completed, performing corresponding release processing on the service change time sequence lock information, service time sequence lock information, and account entry capacity lock information corresponding to the account entry operation processing; and / or, When the preset account entry result acquisition time arrives, acquiring the account entry result data corresponding to the account entry operation, and updating the repayment plan information; Returning the account entry result data and the repayment plan information to the system access layer.

10. A computer-readable storage medium storing a computer program for executing the method according to any one of claims 1-9 above.

Images