CN114331704A - Income posting method, device and equipment and computer readable storage medium - Google Patents

Abstract

The application provides a income posting method, a device, equipment and a computer readable storage medium, which are applied to the technical field of cloud, and the method comprises the following steps: grouping the income information of the plurality of accounts to obtain at least one posting group; account income records corresponding to the account income information in each posting group are in the same data table of the database; calling an account-entering interface to carry out account-entering operation on each account-entering group; the posting operation is used for adjusting account resources corresponding to the income information of each account in the posting group; responding to the posting feedback of each posting group, and sending a posting record request of each posting group to a database; and the posting record request is used for indicating the database to update the account income record corresponding to each account income information in the posting group. Through the income posting method provided by the application, the income posting time can be reduced, and the income posting efficiency is improved.

Description

Income entry method, apparatus, device, and computer-readable storage medium

technical field

The present application relates to the field of computer technologies, and in particular, to a method, apparatus, device, and computer-readable storage medium for revenue entry.

Background technique

Monetary funds are daily earnings carried forward into shares. With the development of Internet finance, various Internet financial platforms have emerged, and more and more users are also choosing to hold financial products such as funds on Internet financial platforms. For Internet financial platforms, in the face of a large number of users, it is necessary to improve the security of their data. Therefore, distributed storage methods are often used to store users' income information to improve disaster tolerance.

The Internet financial platform also needs to complete the revenue entry operation according to a certain revenue cycle, and timely feedback the revenue information in the previous revenue cycle to the user. However, the revenue entry operation needs to access and modify the user revenue data in the database multiple times. In the process of improving the disaster recovery capability, the efficiency of revenue entry will be seriously affected, the revenue entry will take too long, and the user experience will be poor.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a method, apparatus, device, and computer-readable storage medium for revenue entry, which can reduce the time-consuming of revenue entry and improve the efficiency of revenue entry.

The technical solutions of the embodiments of the present application are implemented as follows:

An embodiment of the present application provides a method for entering income into an account, including: grouping multiple account income information to obtain at least one entry group; the account income record corresponding to each account income information in each entry group is located in the same data table of the database; Call the entry interface to perform entry operation for each entry group; the entry operation is used to adjust the account resources corresponding to the income information of each account in the entry group; in response to the entry feedback of each entry group, send the entry record request of each entry group to Database; the entry record request is used to instruct the database to update the account income records corresponding to the income information of each account in the entry group.

In some embodiments of the present application, the invoking an account entry interface to perform an entry operation for each entry group includes: generating at least one resource adjustment request according to the income information of each account in the entry group; the resource adjustment request carrying the account income information corresponds to The account identifier and resource change amount; send each resource adjustment request to the entry interface; the resource adjustment request is used to instruct the entry interface to adjust the virtual resources in the account corresponding to the account identifier according to the resource change amount.

In some embodiments of the present application, before generating the resource adjustment request corresponding to the at least one account income information according to the at least one account income information in the crediting group, the method further includes: generating the corresponding income information for each account in the crediting group Opening a transaction, the transaction includes: sending a new flow request corresponding to the income information of each account to the database; the new flow request is used to instruct the database to add a new bill number in the account income record corresponding to the account income information The corresponding flow record; in the case of receiving the new flow feedback corresponding to the income information of each account, submit the transaction.

In some embodiments of the present application, the generating at least one resource adjustment request according to the income information of each account in the account entry group includes: in response to submitting a transaction, generating each account income according to the income information of each account in the account entry group The resource adjustment request corresponding to the information; the resource adjustment request also carries the billing number corresponding to the account income information.

In some embodiments of the present application, the new flow request is also used to update the first total amount of resources corresponding to the account income information in the database; before at least one resource adjustment request is generated according to the income information of each account in the account group , the method further includes: obtaining the first total amount of resources corresponding to each account income information according to the newly added flow feedback corresponding to each account income information sent by the database; according to the first resource total amount corresponding to each account income information Updating the second total amount of resources corresponding to the income information of each account in the local cache; generating at least one resource adjustment request according to the income information of each account in the account group, including: comparing the first total amount of resources corresponding to the income information of the account with When the second total amount of resources is different, a resource adjustment request corresponding to the account income information is generated; the resource adjustment request also carries the billing number corresponding to the account income information.

In some embodiments of the present application, before sending a new flow request corresponding to each account income information to the database, the method further includes: locking the account income information corresponding to each account income information; Before, the method further includes: unlocking the account income information corresponding to each account income information.

In some embodiments of the present application, the method further includes: receiving resource adjustment feedback corresponding to each resource adjustment request sent by the billing interface; the resource adjustment feedback is used to indicate whether the adjustment operation corresponding to the resource adjustment request is successful; Resource transfer feedback to generate entry feedback; entry feedback is used to represent the entry operation result corresponding to the income information of each account in the entry group.

In some embodiments of the present application, the sending a request for an entry record of each entry group to the database in response to the entry feedback of each entry group includes: according to the entry operation result corresponding to the income information of each account in the entry group, Generating an entry record request for an entry group; sending the entry record request to a database; and generating an entry record request for an entry group according to the entry operation result corresponding to the income information of each account in the entry group, including: obtaining the entry operation result in the entry group: Obtain at least one piece of income information to be entered into the account income information that has been successfully entered into the account; generate an entry record request according to the at least one income information to be entered into the account; the entry record request is used to instruct the database to update the flow record corresponding to each income information to be entered into the account.

In some embodiments of the present application, the method further includes: obtaining the entry record feedback corresponding to each entry record request; the entry record feedback includes the entry result corresponding to the income information of each account in the entry group; The entry result corresponding to the income information of each account will generate a batch entry result.

An embodiment of the present application provides a revenue entry device, and the device includes:

The grouping module is used for grouping multiple account income information to obtain at least one entry group; the account income record corresponding to each account income information in each entry group is located in the same data table of the database.

The adjustment module is used to call the account entry interface to perform an entry operation for each entry group; the entry operation is used to adjust the account resources corresponding to the income information of each account in the entry group.

The account entry module is used for sending the entry record request of each entry group to the database in response to the entry feedback of each entry group; the entry record request is used to instruct the database to update the account income record corresponding to each account income information in the entry group.

The embodiment of the present application provides a revenue entry device, including:

memory for storing executable instructions;

The processor is configured to implement the revenue entry method provided by the embodiment of the present application when executing the executable instructions stored in the memory.

The embodiments of the present application provide a computer-readable storage medium, which stores executable instructions for causing the processor to execute the method to implement the revenue entry method provided by the embodiments of the present application.

The embodiment of the present application has the following beneficial effects:

In this embodiment of the present application, a plurality of user income information may be grouped according to a preset grouping rule to obtain at least one crediting group. In the process of crediting the income of the multiple user income information, an account crediting record may be used to request for the crediting group. At least one user income information is updated at the same time. Compared with the scheme of separately updating each user income information in the traditional technology, the present application divides multiple user income information corresponding to the same data table into the same account group, and based on the account The revenue entry operation of the group can reduce the overall time-consuming process of revenue entry and improve the entry efficiency of the overall revenue entry.

Description of drawings

FIG. 1 is an optional schematic structural diagram of a revenue entry system provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a revenue entry device provided by an embodiment of the present application;

Fig. 3 is an optional schematic flow chart of the revenue entry method provided by the embodiment of the present application;

FIG. 4 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application;

FIG. 5 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application;

Fig. 6 is an optional schematic flow chart of the revenue entry method provided by the embodiment of the present application;

FIG. 7 is an optional schematic flow chart of the revenue entry method provided by the embodiment of the present application;

FIG. 8 is an optional schematic flow chart of the revenue entry method provided by the embodiment of the present application;

FIG. 9 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings. All other embodiments obtained under the premise of creative work fall within the scope of protection of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" can be the same or a different subset of all possible embodiments, and Can be combined with each other without conflict.

In the following description, the term "first\second\third" is only used to distinguish similar objects, and does not represent a specific ordering of objects. It is understood that "first\second\third" Where permitted, the specific order or sequence may be interchanged, so that the embodiments of the present application described in this embodiment can be implemented in sequences other than those illustrated or described in this embodiment.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application, and are not intended to limit the present application.

First, briefly introduce the terms involved in the embodiments of the present application:

Batch run (batch update): The business team periodically/triggeredly updates the income records of each account based on the income information of each account.

Income: The amount of change that occurs after a user purchases financial products such as funds on the fund platform after a preset income cycle.

Referring to FIG. 1, FIG. 1 is an optional schematic diagram of the structure of the revenue entry system 100 provided by the embodiment of the present application. In order to support a revenue entry application, a terminal (exemplarily shows a terminal 400-1 and a terminal 400-2) The server 200 is connected through a network 300, and the network 300 may be a wide area network or a local area network, or a combination of the two. The server 200 is also connected to at least one database, which may be a database cluster, and is used for realizing distributed storage of revenue records and improving disaster tolerance. FIG. 1 also shows that the server 200 can be a server cluster, and the server cluster includes servers 200-1 to 200-3. Similarly, the servers 200-1 to 200-3 can be physical machines, and can also use virtualization technology ( For example, a virtual machine constructed by a container technology and a virtual machine technology, etc.) is not limited in this embodiment of the present application. Of course, in this embodiment, a single server may also be used to provide services.

In some embodiments of the present application, the terminal may receive an update operation of the revenue data by the administrator through a graphical interface (a graphical interface 410-1 and a graphical interface 410-2 are exemplarily shown), and the update operation may also be performed according to a preset The set revenue cycle is automatically executed. In response to the update operation, the terminal will send an income update request to the server 200, and the income update request is used to instruct the server 200 to group multiple account income information to obtain at least one entry group; the income of each account in each entry group The account income record corresponding to the information is in the same data table of the database; the account entry interface is called to perform an entry operation for each entry group; the entry operation is used to adjust the account resources corresponding to the income information of each account in the entry group; The account entry feedback sends the entry record request of each entry group to the database; the entry record request is used to instruct the database to update the account income record corresponding to the income information of each account in the entry group. The terminal can also receive the user's query request for earnings through a graphical interface, and send the query request to the server 200. The server 200 can generate a feedback message according to the updated account earnings record, and send the feedback message to the terminal. The terminal can The feedback message is presented through a graphical interface (graphical interface 410-1 and graphical interface 410-2 are illustratively shown).

The embodiments of the present application can be implemented with the help of cloud technology. Cloud technology refers to a kind of hosting that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize data computing, storage, processing, and sharing. technology.

Cloud technology is based on the general term of network technology, information technology, integration technology, management platform technology, and application technology applied in the cloud computing business model. Cloud computing technology will become an important support. Background services of technical network systems require a lot of computing and storage resources, for example, portal websites of educational systems.

As an example, the server 200 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or may provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, Cloud servers for basic cloud computing services such as cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal and the server 200 may be directly or indirectly connected through wired or wireless communication, which is not limited in this embodiment of the present application.

Referring to FIG. 2 , FIG. 2 is a schematic structural diagram of a revenue credit device 500 provided by an embodiment of the present application. The revenue credit device 500 shown in FIG. 2 includes: at least one processor 510 , memory 550 , at least one network interface 520 and user interface 530 . The various components in revenue posting device 500 are coupled together by bus system 540 . It can be understood that the bus system 540 is used to implement the connection communication between these components. In addition to the data bus, the bus system 540 also includes a power bus, a control bus and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 540 in FIG. 2 .

The processor 510 may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where a general-purpose processor may be a microprocessor or any conventional processor or the like.

User interface 530 includes one or more output devices 531 that enable presentation of media content, including one or more speakers and/or one or more visual display screens. User interface 530 also includes one or more input devices 532, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, and other input buttons and controls.

Memory 550 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory. The non-volatile memory may be a read only memory (ROM, Read Only Memory), and the volatile memory may be a random access memory (RAM, Random Access Memory). The memory 550 described in the embodiments of the present application is intended to include any suitable type of memory. Memory 550 optionally includes one or more storage devices that are physically remote from processor 510 .

In some embodiments of the present application, memory 550 is capable of storing data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.

The operating system 551 includes system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

A network communication module 552 for reaching other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: Bluetooth, Wireless Compatibility (WiFi), and Universal Serial Bus ( USB, Universal Serial Bus), etc.;

A display module 553 for enabling presentation of information (eg, a user interface for operating peripherals and displaying content and information) via one or more output devices 531 associated with the user interface 530 (eg, a display screen, speakers, etc.) );

An input processing module 554 for detecting one or more user inputs or interactions from one of the one or more input devices 532 and translating the detected inputs or interactions.

In some embodiments of the present application, the revenue crediting device provided by the embodiments of the present application may be implemented by a combination of software and hardware. As an example, the revenue crediting device provided by the embodiments of the present application may be processed in the form of a hardware decoding processor. The device is programmed to execute the revenue accounting method provided by the embodiments of the present application.

In some embodiments of the present application, the revenue credit device provided by the embodiments of the present application may be implemented in software. FIG. 2 shows the revenue credit device 555 stored in the memory 550, which may be software in the form of programs and plug-ins. , including the following software modules: grouping module 5551, adjustment module 5552 and account entry module 5553, these modules are logical, so any combination or further split can be performed according to the functions implemented.

The function of each module will be explained below.

In other embodiments, the apparatus provided by the embodiments of the present application may be implemented in hardware. As an example, the apparatus provided by the embodiments of the present application may be a processor in the form of a hardware decoding processor, which is programmed to execute the present application For the revenue entry method provided by the embodiment, for example, the processor in the form of a hardware decoding processor may adopt one or more Application Specific Integrated Circuits (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device) ), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array) or other electronic components.

With reference to the exemplary application and implementation of the server provided by the embodiment of the present application, in the embodiment of the present application, the server is used as the execution subject to describe the revenue entry method provided by the embodiment of the present application.

Referring to FIG. 3 , FIG. 3 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application, which will be described with reference to the steps shown in FIG. 3 .

In step 301, a plurality of account income information are grouped to obtain at least one entry group; the account income records corresponding to each account income information in each entry group are located in the same data table of the database.

In some embodiments of the present application, the server may obtain the multiple account income information by parsing the income file. Wherein, the income file may be an income file sent by the fund company, and the income file includes account income information of each account in the multiple accounts within the preset income cycle. Wherein, the account income information of an account may include the account identifier of the account, the amount of resource change, and the total amount of resources.

In some embodiments of the present application, after parsing the income file, the server can obtain multiple account income information included in the parsed file, and the server can modify the account corresponding to the account income information in the database according to each account income information Income record, that is, a new income stream is added to the account income record corresponding to the account income information. Therefore, the income records corresponding to the income information of each account can be obtained first, and the income records of the multiple accounts can be grouped according to the grouping rule that the income records are located in the same data table in the database to obtain at least one entry group.

In some embodiments of the present application, the grouping rule may be specified according to a storage rule for storing account income records of each account in the database. For example, in the database, at least one account income record with the same first/last N digits of the account identifier in the account income information is stored in the same data table of the same database. Correspondingly, in the process of grouping the plurality of account income records , at least one account income record with the same first and last N digits can be set as an account entry group according to the account identifier in each account income information.

In some embodiments of the present application, the grouping rule may further limit the number of account income records in each account group. Wherein, the maximum number within the group and/or the minimum number within the group can be set to limit the number of account income records in each account group.

In some embodiments of the present application, in the process of grouping multiple account income information, the number of account income records in each account group may be the same or different. In order to ensure the efficiency of income entry, in the process of grouping the income information of multiple accounts, it is necessary to ensure that the number of account income records in at least one account group is at least two, and the number of account income records in the account group is at least two. In this case, the application can perform batch entry operations for at least two account income records in the entry group, thereby improving the efficiency of income entry.

For example, for the existing 20 account income records, assuming that the 20 account income records are in the same data table, the 20 account income records can be divided into an account entry group through the grouping rules described above in this application; The 20 account income records are divided into 18 entry groups with only one account income record and 1 entry group with two account income records; if there are 10 maximum group numbers and 2 minimum group numbers, 20 Account income records are divided into one entry group with ten account income records and five entry groups with two account income records.

In step 302, the account entry interface is invoked to perform an entry operation for each entry group; the entry operation is used to adjust the account resources corresponding to the income information of each account in the entry group.

In some embodiments of the present application, the account entry interface is any type of interface that can provide account entry operation services. For example, the account entry interface can be an operation interface provided by a financial institution, such as a bank interface, a fund interface, and the like. The process of invoking the crediting interface to perform crediting operations for each account group includes adjusting the account resources corresponding to the income information of each account according to the income information of each account in the crediting group. If the account entry interface is a bank interface, the account resource is the account resource corresponding to the account income information in the banking system; if the account entry interface is a fund interface, the account resource is the account income information in the fund system. The corresponding account resources in .

In some embodiments of the present application, in the process of the entry operation of any entry group, that is, during the adjustment operation of the account resources corresponding to the income information of each account in the entry group, each entry in the entry group can be obtained. The entry operation result corresponding to the account income information, and then the entry operation feedback of the entry operation of the entry group can be obtained, and the entry operation feedback is used to represent the entry operation result corresponding to the income information of each account in the entry group.

In step 303, in response to the entry feedback of each entry group, the entry record request of each entry group is sent to the database; the entry record request is used to instruct the database to update the account income record corresponding to each account income information in the entry group.

In some embodiments of the present application, for any crediting group, after receiving the crediting feedback of the crediting group, the crediting operation result corresponding to the income information of each account in the crediting group can be obtained. An account entry record request for the account entry group can be generated according to the entry operation result corresponding to each account income information in the entry group, and the entry record request is used to instruct the database to update the account income record corresponding to each account income information in the entry group.

In some embodiments of the present application, for an account entry group, whether the entry operation result corresponding to the account income information in the entry group is successful or unsuccessful, the entry record request includes the account identifier and resource change corresponding to each account income information. , the total amount of resources and the result of the entry operation. After the database receives the entry record request corresponding to the entry group, it will update the corresponding account according to the account ID, resource change, total resource and entry operation result corresponding to the income information of each account. Earnings records.

In some embodiments of the present application, for an account entry group, the entry record request includes the account identifier, the resource change amount and the total amount of resources corresponding to the account income information whose entry operation result is that the entry is successful. After the account entry record request is made, the corresponding account income record will be updated according to the account ID, resource change amount and total resource amount corresponding to the account income information that is successfully entered into the account according to the result of each entry operation.

It can be seen from the above exemplary implementation of FIG. 3 in the embodiment of the present application that the embodiment of the present application can group multiple user income information according to a preset grouping rule, so as to obtain at least one credit group. In the process of entering the account, one entry record request can be used to simultaneously update the income information of at least one user in the account entry group. Compared with the scheme of separately updating the income information of each user in the traditional technology, this application will correspond to the same data table. The income information of multiple users is divided into the same entry group, and the income entry operation is performed based on the entry group, which can reduce the overall time-consuming process of income entry and improve the entry efficiency of the overall income entry.

Referring to FIG. 4, FIG. 4 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application. Based on FIG. 3, step 302 shown in FIG. 3 may be updated to steps 401 to 402, which will be shown in conjunction with FIG. 4 steps are explained.

In step 401, at least one resource adjustment request is generated according to the income information of each account in the account entry group; the resource adjustment request carries the account identifier and the resource change amount corresponding to the account income information.

In some embodiments of the present application, for each account income information in any one of the account entry groups, the account identifier and resource change in each account income information can be obtained, and according to the account identifier and the resource change in each account income information The resource delta generates the at least one resource adjustment request.

In some embodiments of the present application, in the process of generating the at least one resource adjustment request according to the account identifier and the resource change amount in each account benefit information, it may be determined whether the resource change amount in the account benefit information is 0, and then When the resource change amount corresponding to the account income information is 0, the resource adjustment request corresponding to the account income information is not generated.

For example, if there are 3 account income information in an account entry group, the account identifier and resource change amount are (user A, 20), (user B, 0.5) and (user C, 0) respectively. A resource adjustment request corresponding to each account income information can be generated, that is, three resource adjustment requests can be generated; it is also possible to not generate a resource adjustment request corresponding to the account income information when the resource change amount corresponding to the account income information is 0, That is, the resource adjustment request corresponding to the user C is not generated, and only the resource adjustment requests corresponding to the user A and the user B respectively are generated.

In step 402, each resource adjustment request is sent to the credit interface; the resource adjustment request is used to instruct the credit interface to adjust the virtual resources in the account corresponding to the account identifier according to the resource change amount.

In some embodiments of the present application, in the process of crediting an crediting group, at least one resource adjustment request generated in step 401 needs to be respectively sent to the crediting interface, and the crediting interface after receiving each resource adjustment request, According to the account identifier and resource change carried in each resource request, the virtual resources in the account corresponding to the account identifier are adjusted in the system corresponding to the account entry interface according to the resource change.

It can be seen from the above exemplary implementation of FIG. 4 in the embodiment of the present application that the embodiment of the present application adjusts the virtual resources of the accounts corresponding to the income information of each account by invoking the account entry interface, which can speed up the income entry speed and reduce the time consuming of income entry.

In some embodiments of the present application, referring to FIG. 5 , FIG. 5 is an optional schematic flow chart of the revenue entry method provided by the embodiment of the present application. Based on FIG. 4 , before step 401 , it further includes steps 501 to 503 , Step 401 can be updated to step 504 .

In step 501, a billing number corresponding to the income information of each account in the billing group is generated.

In some embodiments of the present application, for any crediting group, before calling the crediting interface to perform the crediting operation on the crediting group, that is, before generating at least one resource adjustment request corresponding to the crediting group, it is also necessary to generate each item in the crediting group. A billing number corresponding to the account income information.

In some embodiments of the present application, the billing number may be generated according to the system time, the measurement unit of the resource change in the account revenue information, and the transaction number. Wherein, the system time is the system time when the billing number is generated; the measurement unit of the resource change amount may be the currency number corresponding to the virtual resource. For one account income information, only one billing number can be generated within one day.

In step 502, a transaction is opened, and the transaction includes: sending a new flow request corresponding to each account income information to the database; the new flow request is used to instruct the database to add a new billing number in the account income record corresponding to the account income information The corresponding flow record.

In some embodiments of the present application, the billing number corresponding to each account income information in the billing group needs to be added to the income record corresponding to the account income information in the database. A transaction can be initiated for the account entry group. In this transaction, a new flow request corresponding to each account income information needs to be sent to the database, so that the database can add the new account income record corresponding to each account income information. The flow record corresponding to the billing number. During the execution of this transaction, it is necessary to complete the recording process of the billing number corresponding to the income of each account. If there is a failure to record the billing number corresponding to the income information of the account, the recording operation corresponding to the income information of other accounts in the billing group will be cancelled.

In some embodiments of the present application, since the database is a cross-city database, the request message needs to be sent to the database through the network to complete the process of recording the billing number. In order to ensure the success rate of recording, the new flow request corresponding to any account income information can be sent to the database multiple times to ensure that the database can receive the new flow request corresponding to each account income information. Since for any account income information, only one billing number will be generated in one day, so after the database receives multiple new flow requests corresponding to any account income information, it will only add one new flow corresponding to the billing number. Record.

In some embodiments of the present application, when the database performs the above process of adding a flow record corresponding to the billing number in the account income record corresponding to the account income information, the billing number corresponding to the new flow request has been After being added to the account income record corresponding to the account income information, a new flow feedback corresponding to the new flow request will be generated.

In step 503, in the case of receiving the new flow feedback corresponding to the income information of each account, the transaction is submitted.

In some embodiments of the present application, for N account income information in an account entry group, N new flow requests corresponding to the N account income information will be issued, and only when each of the N new flow requests is received In the case of new pipeline feedback corresponding to the new pipeline request, that is, when N new pipeline feedbacks are received, the transaction is submitted; otherwise, the transaction is rolled back.

In step 504, in response to submitting the transaction, a resource adjustment request corresponding to the income information of each account is generated according to the income information of each account in the billing group; the resource adjustment request also carries the billing number corresponding to the income information of the account.

In some embodiments of the present application, in response to submitting the transaction, a newly added flow record corresponding to the income information of each account in the account entry group already exists in the database, and the flow record corresponding to the income information of each account is recorded in the income of each account In the account income record corresponding to the information. At this point, the billing number recording operation of the billing group has been completed, and a resource adjustment request corresponding to the income information of each account can be generated. Each resource adjustment request also carries the billing number corresponding to the account income information.

For example, for an account entry group with 3 account income information, after generating 3 new transaction requests and sending them to the database, after receiving the 3 new transaction feedback feedbacks from the database, the income of each account in the account group will be generated. For the resource adjustment request corresponding to the information, three resource adjustment requests are generated, and each resource adjustment request carries a corresponding billing number.

In some embodiments of the present application, since each resource adjustment request also carries the billing number corresponding to the account revenue record, the billing interface will also judge the resource adjustment request according to the billing number after receiving the resource adjustment request. Whether it is a legal request or not, in the case of whether the resource adjustment request is a legal request, the virtual resource in the account corresponding to the account identifier is adjusted in the system corresponding to the account entry interface according to the resource change amount. In the case that the resource adjustment request is an illegal request, an alarm report is generated and saved. Wherein, at least one of the following methods can be used to judge whether the resource adjustment request is a legal request: according to the generation rule of the billing number, it is judged whether the billing number carried in the resource adjustment request is a legal billing number, and the billing number is In the case of a legal order number, the corresponding resource adjustment request is a legal request; the billing number corresponding to each account identifier is recorded, and the first resource adjustment request corresponding to the account identifier received within a revenue cycle is a legal request. The billing number corresponding to the first resource adjustment request is recorded, and other resource adjustment requests with the billing number received within the revenue period are illegal requests.

In some embodiments of the present application, before sending a new flow request corresponding to each account income information to the database, this embodiment further includes: locking the account income information corresponding to each account income information; Before, this embodiment further includes: unlocking the account income information corresponding to each account income information. With the method in this embodiment, it can be ensured that in the process of adding a revenue stream to the user revenue record, the user revenue record will not be changed by other processes or services, avoiding repeated operations and ensuring data consistency.

It can be seen from the above exemplary implementation of FIG. 5 in the embodiment of the present application that by generating a corresponding billing number for each account income information in the embodiment of the present application, it is possible to avoid the situation of repeatedly adding new income streams in the account income record, or It avoids the situation of repeatedly adjusting the virtual resources of the account corresponding to the account income information in the process of calling the account entry interface, and improves the security of the income entry process. In addition, in the embodiment of the present application, the recording operations of the billing numbers of the income information of multiple accounts in the same billing group are bound together by means of transactions, which can ensure that the billing numbers corresponding to the income information of each account can be completely recorded, preventing Entry errors caused by missing a billing number. In addition, the embodiment of the present application adopts a locking method in the process of adding a revenue stream to a user revenue record, so that the corresponding user revenue record will not be changed by other processes or services, avoiding repeated operations and ensuring data consistency.

In some embodiments of the present application, referring to FIG. 6 , FIG. 6 is an optional schematic flowchart of the revenue entry method provided by the embodiments of the present application. Based on FIG. 4 , before step 401 , it further includes steps 601 to 605 , Step 401 can be updated to step 606 .

In step 601, a billing number corresponding to the income information of each account in the billing group is generated.

In step 602, a transaction is opened, and the transaction includes: sending a new flow request corresponding to each account income information to the database; the new flow request is used to instruct the database to add a new account number corresponding to the account income record corresponding to the account income information. The corresponding flow record.

In step 603, in the case of receiving the new flow feedback corresponding to the income information of each account, the transaction is submitted.

In some embodiments of the present application, the above steps 601 to 603 are the same as the steps 501 to 503 in FIG. 5 , and details are not repeated here.

In step 604, the first total amount of resources corresponding to the income information of each account is acquired according to the newly added flow feedback corresponding to the income information of each account sent by the database.

In some embodiments of the present application, the new flow request corresponding to each account income information is also used to update the first total amount of resources in the database for each account income information. After the database receives the new flow request corresponding to the income information of each account, in addition to adding the income flow corresponding to the bill number in the account income record corresponding to the income information of each account, it also needs to update the income flow corresponding to the income information of each account. The total amount of the first resource. Correspondingly, the newly added flow feedback sent by the database also carries the latest total amount of first resources in the database for the account revenue information.

For example, for a new transaction request in an account entry group, the new transaction request carries "user 1, 30, order number 1". After the database receives the new transaction request, it needs to record in the account corresponding to user 1. A new revenue stream is added in the stream, and the revenue stream corresponds to the order number 1. At the same time, the database will also obtain the total historical resource M corresponding to user 1, and update the historical resource total M with the resource change in the new stream request. , the total amount of the first resource (M+30) is obtained. The new flow feedback corresponding to the new flow request sent by the database will carry the first total amount of resources (M+30) corresponding to the user 1.

In step 605, the second total amount of resources corresponding to each account income information in the local cache is updated according to the first total amount of resources corresponding to each account income information.

In some embodiments of the present application, the server stores the second total amount of resources for each account income information. The first total amount of resources corresponding to the information updates the second total amount of resources corresponding to each account revenue information in the local cache.

Based on the above example, if the total amount of first resources corresponding to user 1 is (M+30), in the server's local cache, the total amount of second resources corresponding to user 1 is M, and the total amount of first resources needs to be used to update the The second total amount of resources, after the update, the second total amount of resources corresponding to user 1 in the server is (M+30), which is consistent with that in the database.

In step 606, when the total amount of the first resource corresponding to the account income information is different from the total amount of the second resource, a resource adjustment request corresponding to the account income information is generated; the resource adjustment request also carries the billing number corresponding to the account income information .

In some embodiments of the present application, in step 605, in the process of updating the second total amount of resources corresponding to each account income information in the local cache according to the first total amount of resources corresponding to each account income information, in an account income information When the corresponding total amount of the first resource is the same as the total amount of the second resource, it means that the income of the account income information in this income cycle is 0, and the virtual resource amount corresponding to the account income information does not need to be adjusted, so it is not generated. The resource adjustment request corresponding to the income of this account. When the total amount of the first resource corresponding to the account revenue information is different from the total amount of the second resource, a resource adjustment request corresponding to the account revenue information is generated.

For example, if the account entry group includes the first account income information and the second account income information, the first resource total amount corresponding to the first account income information and the second resource total amount are the same, and the first resource corresponding to the second account income information The total amount is not the same as the total amount of the second resource. In the process of generating at least one resource adjustment request corresponding to the credit group, the resource adjustment request corresponding to the first account income information is not generated, and only the resources corresponding to the second account income information are generated. Adjustment request.

In some embodiments of the present application, since each resource adjustment request also carries the billing number corresponding to the account revenue record, the billing interface will also judge the resource adjustment request according to the billing number after receiving the resource adjustment request. Whether it is a legal request or not, in the case of whether the resource adjustment request is a legal request, the virtual resource in the account corresponding to the account identifier is adjusted in the system corresponding to the account entry interface according to the resource change amount. In the case that the resource adjustment request is an illegal request, an alarm report is generated and saved. Wherein, at least one of the following methods can be used to judge whether the resource adjustment request is a legal request: according to the generation rule of the billing number, it is judged whether the billing number carried in the resource adjustment request is a legal billing number, and the billing number is In the case of a legal order number, the corresponding resource adjustment request is a legal request; the billing number corresponding to each account identifier is recorded, and the first resource adjustment request corresponding to the account identifier received within a revenue cycle is a legal request. The billing number corresponding to the first resource adjustment request is recorded, and other resource adjustment requests with the billing number received within the revenue period are illegal requests.

It can be seen from the above exemplary implementation of FIG. 6 in the embodiment of the present application that the embodiment of the present application updates the first total amount of resources corresponding to the account revenue information in the database through the newly added flow request, and uses the first total amount of resources carried in the newly added flow feedback. The total amount of resources updates the second total amount of resources in the local cache, which can ensure that the total amount of resources corresponding to each user's revenue information in the server's local cache is consistent with the database. Going to the step of database query, while reducing the computational pressure of the database, can also improve the feedback efficiency of viewing requests and improve the user experience; and, because the total amount of the first resource and the total amount of the second resource are different, no generation The corresponding resource adjustment request can not only reduce the computing pressure of the bank interface, but also reduce the time-consuming of revenue entry and improve the efficiency of revenue entry.

In some embodiments of the present application, referring to FIG. 7 , FIG. 7 is an optional schematic flowchart of the revenue entry method provided by the embodiment of the present application. Based on the above embodiments, taking FIG. 4 as an example, before step 401, further It includes steps 701 to 703 , before step 303 , the method further includes steps 704 to 705 , step 303 may further include steps 706 to 707 , and the method may further include step 708 .

In step 701, a billing number corresponding to the income information of each account in the billing group is generated.

In step 702, a transaction is started, and the transaction includes: sending a new flow request corresponding to each account income information to the database; the new flow request is used to instruct the database to add a new billing number in the account income record corresponding to the account income information The corresponding flow record.

In step 703, in the case of receiving the newly added flow feedback corresponding to the income information of each account, the transaction is submitted.

In some embodiments of the present application, the above steps 701 to 703 are the same as the steps 501 to 503 in FIG. 5 , and details are not repeated here.

In step 704, a resource adjustment feedback corresponding to each resource adjustment request sent by the account entry interface is received; the resource adjustment feedback is used to indicate whether the adjustment operation corresponding to the resource adjustment request is successful.

In some embodiments of the present application, after each resource adjustment request is sent to the billing interface, a resource adjustment feedback generated by the billing interface for each resource adjustment request may be received. The resource adjustment feedback is used to represent whether the adjustment operation corresponding to the resource adjustment request is successful, for example, it may include two types of resource adjustment results: resource adjustment success and resource adjustment failure.

In step 705, according to each resource transfer feedback, a crediting feedback is generated; the crediting feedback is used to represent the crediting operation result corresponding to the income information of each account in the crediting group.

In some embodiments of the present application, based on the embodiment provided in FIG. 5 , a corresponding resource adjustment request is sent for each account income information in the credit group. Therefore, the corresponding resource adjustment request can be directly The resource adjustment feedback of , determines the result of the entry operation corresponding to the income information of each account.

For example, for a credit group with three account income information, a resource adjustment request corresponding to each account income information in the credit group will be generated, that is, three resource adjustment requests will be generated and sent to the credit interface. Correspondingly, it can receive The resource adjustment feedback corresponding to each account income information fed back by the account entry interface, that is, the resource adjustment feedback corresponding to the three account income information. At this time, the result of the entry operation corresponding to each of the three account income information can be determined according to the received three resource adjustment feedbacks, that is, when the resource adjustment result corresponding to the account income information is that the resource adjustment is successful, the The result of the entry operation corresponding to the account income information is that the entry is successful; if the resource adjustment result corresponding to the account income information is a resource adjustment failure, the result of the entry operation corresponding to the account income information is an entry failure.

In some embodiments of the present application, based on the embodiment provided in FIG. 6 , for at least one account income information in the crediting group, when the resource change amount of the account income information is 0, no generation And send the resource adjustment request corresponding to the account income information, and in the case that the resource change amount of the account income information is not 0, generate and send the resource adjustment request corresponding to the account income information. Therefore, the number of generated resource adjustment requests may be smaller than the amount of account income information in the crediting group, and accordingly, the number of received resource adjustment feedbacks may be smaller than the amount of account income information in the crediting group. Based on the above situation, the server determines that the resource adjustment feedback is the result of the entry operation corresponding to the account income information for which the resource adjustment fails as the entry failure; and the server feeds back the resource adjustment as the result of the entry operation corresponding to the account income information for which the resource adjustment is successful and the resource change amount is 0. It is determined that the entry is successful.

For example, if the account entry group includes the first account income information and the second account income information, the first resource total amount corresponding to the first account income information and the second resource total amount are the same, and the first resource corresponding to the second account income information The total amount is not the same as the total amount of the second resource. In the process of generating at least one resource adjustment request corresponding to the credit group, the resource adjustment request corresponding to the first account income information is not generated, and only the resources corresponding to the second account income information are generated. Adjustment request. After receiving the resource adjustment feedback corresponding to the income information of the second account, if the feedback of the resource adjustment is that the resource adjustment is successful, the results of the entry operation corresponding to the income information of the first account and the income information of the second account are both successful entry; In the case where the resource adjustment feedback is that the resource adjustment fails, the result of the entry operation corresponding to the income information of the first account is that the entry is successful, and the result of the entry operation corresponding to the income information of the second account is the entry failure.

In step 706, according to the result of the entry operation corresponding to the income information of each account in the entry group, the entry record request of the entry group is generated.

In some embodiments of the present application, the above-mentioned step 706 may be implemented in the following ways: acquiring the account income information in the account entry group whose entry operation result is successful entry into the account, and obtaining at least one piece of income information to be entered into the account; The income information generates the account entry record request; the account entry record request is used to instruct the database to update the flow record corresponding to each of the income information to be entered into the account. It should be noted that, because in the embodiment of the present application, the account income records corresponding to the account income records in the same data table are divided into the same entry group, therefore, in this step, multiple incomes to be entered into the account for one entry group are divided into the same entry group. information, an account entry record request may be used to simultaneously update the flow record corresponding to each of the income information to be entered into the account. The entry record request is a database operation statement.

In step 707, a request for an account entry record is sent to the database.

In step 708, the entry record feedback corresponding to each entry record request is obtained; the entry record feedback includes the entry result corresponding to the income information of each account in the entry group; according to the entry result corresponding to the income information of each account in each entry group Generate batch entry results.

In some embodiments of the present application, after the account entry record request corresponding to each account entry group is sent to the database, the account entry record feedback sent by the database for each account entry record request can be obtained. Wherein, after receiving each account entry record request, the database can save each account income information in the account entry record request in the corresponding account income record, which can be specifically stored in the entry number corresponding to each account income information in the corresponding flow record. Correspondingly, in the process of saving records, the database will generate the corresponding entry results according to the results of saving the income information of each account, and use the batch entry results to count the income information of the accounts that have been successfully entered and the incomes that have failed to enter the account through the batch entry results. Account earnings information.

For example, if there are 20 account income information, after grouping, the first entry group including the 1st to 10th account income information, and the second entry group containing the 11th to 20th account income information can be obtained. After the first entry record request corresponding to an entry group and the first entry record request corresponding to the second entry group are sent to the database, the feedback of the first entry record corresponding to the first entry group and the second entry record corresponding to the second entry group can be obtained. Feedback on account entry records, wherein the first entry record feedback includes the failure to enter the first account income information into the account, and the second to tenth account income information is successfully entered into the account; the second account entry record feedback includes the 20th account income information failed to enter into the account, and the 11th to 19th The account income information has been successfully entered into the account. At this time, the accounting results corresponding to the income information of each account can be counted, and batch entry results can be generated. The batch entry results include: the 2nd to 19th account income information has been successfully entered into the account, and the first and 20th account income information has been successfully entered into the account. Failed to enter account income information.

In some embodiments of the present application, the batch crediting result may be sent to the terminal device corresponding to the administrator, so as to remind the administrator to process the account income information that fails to be credited.

It can be seen from the above-mentioned exemplary implementation of FIG. 7 in the embodiment of the present application that, in the process of entering the income of multiple users’ income information in the embodiment of the present application, an account entry record request can be used to perform an account entry record request on at least one user’s income information in the account group. Simultaneous updating can reduce the overall time-consuming process of revenue entry and improve the entry efficiency of the overall revenue entry; in addition, since the batch entry results are generated based on the entry record feedback of each entry group, the entry status of the income information of each account can be visually displayed. The administrator experience has been improved.

Below, an exemplary application of the embodiments of the present application in a practical application scenario will be described.

Monetary funds are carried over from daily earnings into shares. With the development of Internet finance, various financial fund platforms have emerged, most of which are Internet platforms. More and more users hold funds, and many users of Internet platforms face the problem of large amount of processing data and tight processing time when they account for users' income. Serving hundreds of millions of users and improving city-level disaster tolerance and fault tolerance are the development trends of technology.

Since the fund company provides the income file relatively late, it is necessary to ensure that users can see the income before 7:00 in the morning. As the number of users increases, in order to improve the city-level disaster recovery capability, it is necessary to double-write the income data across cities. The data storage layer uses MGR group replication technology. This solution has a great impact on the entry performance. A single entry often requires at least 4 modification statements, and each modification statement takes an additional 30ms. The time-consuming of a single transaction increases by at least 120ms. The overall entry time will change from the previous 5 hours to 8 hours, which does not meet our goal of completing revenue entry before 7 o'clock.

In some embodiments of the present application, referring to FIG. 8 , FIG. 8 is an optional schematic flowchart of the revenue entry method provided by the embodiments of the present application.

In step 801, the account-entry batcher initiates a batch-account entry request for revenue, and sends it to the server.

In step 802, the server locks the revenue record in the database.

In step 803, the database starts the transaction, generates an invoicing number, and records the invoicing number in the user income record in the database.

In step 804, the database judges whether the request is repeated according to the billing number, and in the case of the repeated request, re-entry returns.

In step 805, the database updates the revenue summary table.

In step 806, the database unlocks the user revenue record and commits the transaction.

In step 807, the database updates the total revenue cached locally in the server.

In step 808, the server invokes the bank interface to increase profits for the user.

In step 809, the server receives the operation result fed back by the bank interface.

In step 810, the server updates the user income record in the database.

In step 811, the database sends the update result to the server.

In step 812, the server returns the execution result of revenue entry to the entry batch.

Wherein, steps 802, 803, 806 and 810 need to operate the database, that is, send an operation request carrying an operation statement to the database. In order to improve the disaster recovery capability of revenue information, the database in this application uses the MGR group replication technology to store the backup of the database in different cities. Therefore, the above steps 802, 803, 806 and 810 require cross-city operations. Cross-city operation will increase the original time consumption by 30ms, and the revenue entry process of a user's income information will increase by 120ms, which seriously affects the efficiency of entry. Among them, the cross-city operation refers to, for example, that a machine in Shenzhen sends an operation request carrying an operation statement to a database machine in Shanghai, and this process will be accessed across the network. The network transmission distance is relatively long, and the time-consuming will be relatively large.

After the applicant's research, it is found that the revenue entry process of a single user's revenue information in the related art is time-consuming, so a revenue entry method as shown in Figure 9 is proposed. By merging users with the same user ID tail number into the account, the number of cross-city transactions is reduced, the average time-consuming of a single account entry is greatly reduced, and the processing performance is improved.

In step 901, the account entry batcher sorts and groups the users who need to enter the account according to their user IDs.

In some embodiments of the present application, the revenue batch run sorts and groups the users who need to be credited according to the tail number of the user identifier (uid). Users with the same tail number are grouped for every N users. In the figure, the income batch run is a service module used to parse the income file, and can get the user account, the income amount of the day, and the latest total asset information of the user.

In step 902, the account entry batcher initiates an account entry request of the user group and sends it to the server. The user group is equivalent to the account entry group in the above embodiment.

In some embodiments of the present application, the account entry batch runs a group of N users with the same tail number and sends a request to the server; because the data storage layer (database) is divided into databases and tables according to the user's tail number, that is to say, only User data with the same end number is stored in a data table. Only the data in the same table can combine multiple statement operations into one operation.

In step 903, the server locks the income records of N users in the user group in the database.

In some embodiments of the present application, this step requires N cross-city operations.

In step 904, the serial number of user 1 (equivalent to the billing number in the above embodiment) is updated in the database.

In step 905, the total revenue of user 1 (equivalent to the total amount of resources in the above embodiment) is updated in the server.

In step 906, the server invokes the bank interface to increase the profit for User 1.

In step 907, the server receives the operation result fed back by the bank interface.

It should be noted that, between steps 907 to 908, the server may sequentially process the user 2 to the user N-1 in the same processing manner as the above-mentioned steps 904 to 907.

In step 908, the update serial number of user N is updated in the database.

In step 909, the total revenue of user N is updated in the server.

In some embodiments of the present application, in this step, only one cross-city operation is required to unlock the income records of N users in the user group.

In step 910, the server invokes the bank interface to increase income for user N.

In step 911, the server receives the operation result fed back by the bank interface.

In step 912, the server instructs the database to batch update the income records of the N users in the user group.

In some embodiments of the present application, in this step, only one cross-city operation is required to batch update the income records of N users.

In step 913, the database sends the update result to the server.

In step 914, the server returns the execution result of revenue crediting of each account of the N users to the crediting batch run.

Through the method provided by the above embodiment, in the case where N is 5, a single request to process the accounts of 5 users, a total of 5+5+1+1=12 cross-city operations, increases the time consumption by 12*30ms=360ms, On average, it takes 360ms/5=72ms for a user to enter the account. It is 40% less than the 120ms time taken by a single transaction in the related scheme.

The following continues to describe the exemplary structure of the revenue credit device 555 provided by the embodiments of the present application implemented as software modules. In some embodiments of the present application, as shown in FIG. 2 , the software stored in the revenue credit device 555 of the memory 550 Modules can include:

The grouping module 5551 is used for grouping multiple account income information to obtain at least one entry group; the account income record corresponding to each account income information in each entry group is located in the same data table of the database.

The adjustment module 5552 is used to call the account entry interface to perform an entry operation for each entry group; the entry operation is used to adjust the account resources corresponding to the income information of each account in the entry group.

The account entry module 5553 is used to send the entry record request of each entry group to the database in response to the entry feedback of each entry group; the entry record request is used to instruct the database to update the account income record corresponding to the income information of each account in the entry group.

In some embodiments of the present application, the adjustment module 5552 is further configured to generate at least one resource adjustment request according to the income information of each account in the account group; the resource adjustment request carries the account identifier and the resource change corresponding to the account income information; sending Each resource adjustment request is sent to the credit interface; the resource adjustment request is used to instruct the credit interface to adjust the virtual resources in the account corresponding to the account identifier according to the resource change amount.

In some embodiments of this application, the adjustment module 5552 is further configured to generate a billing number corresponding to the income information of each account in the billing group; to open a transaction, the transaction includes: sending a new flow request corresponding to the income information of each account to Database; the new flow request is used to instruct the database to add a flow record corresponding to the billing number in the account income record corresponding to the account income information; in the case of receiving the new flow feedback corresponding to each account income information, submit affairs.

In some embodiments of the present application, the adjustment module 5552 is further configured to, in response to submitting a transaction, generate a resource adjustment request corresponding to the income information of each account according to the income information of each account in the account group; the resource adjustment request also carries the income of the account The billing number corresponding to the information.

In some embodiments of the present application, the adjustment module 5552 is further configured to, before generating at least one resource adjustment request according to the income information of each account in the account group, feedback the newly added flow according to the income information of each account sent by the database , obtain the first total amount of resources corresponding to the income information of each account; update the total amount of resources corresponding to each account income information in the local cache according to the first total amount of resources corresponding to the income information of each account. The adjustment module 5552 is further configured to generate a resource adjustment request corresponding to the account income information when the first total amount of resources corresponding to the account income information is different from the second total amount of resources; the resource adjustment request also carries the entry corresponding to the account income information single number.

In some embodiments of the present application, the adjustment module 5552 is further configured to lock the account income information corresponding to each account income information before sending the new flow request corresponding to each account income information to the database; Before the transaction, unlock the account income information corresponding to each account income information.

In some embodiments of this application, the account entry module 5553 is further configured to receive resource adjustment feedback corresponding to each resource adjustment request sent by the account entry interface; the resource adjustment feedback is used to indicate whether the adjustment operation corresponding to the resource adjustment request is successful; 1. Resource transfer feedback to generate credit feedback; the credit feedback is used to represent the credit operation result corresponding to the income information of each account in the credit group.

In some embodiments of the present application, the account entry module 5553 is further configured to generate an account entry record request of the account entry group according to the entry operation result corresponding to the income information of each account in the account entry group; and send the entry record request to the database. The generating an account entry record request of the account entry group according to the entry operation result corresponding to the income information of each account in the entry group, includes: obtaining the account income information in the entry group whose entry operation result is successful entry into the account, and obtaining at least one income information to be entered into the account; An account entry record request is generated according to at least one piece of income information to be entered into the account; the entry record request is used to instruct the database to update the flow record corresponding to each income information to be entered into the account.

In some embodiments of the present application, the account entry module 5553 is further configured to obtain the entry record feedback corresponding to each entry record request; the entry record feedback includes the entry result corresponding to the income information of each account in the entry group; according to each entry group The account entry results corresponding to each account income information in the system generate batch entry results.

Embodiments of the present application provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the revenue crediting method described above in the embodiment of the present application.

The embodiments of the present application provide a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored, and when the executable instructions are executed by a processor, the processor will cause the processor to execute the revenue crediting method provided by the embodiments of the present application. , for example, the methods shown in FIGS. 3 to 9 .

In some embodiments of the present application, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; Various devices in any combination.

In some embodiments of the present application, executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages , and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

As an example, executable instructions may, but do not necessarily correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, in a Hyper Text Markup Language (HTML) document One or more scripts of a , stored in a single file dedicated to the program in question, or in multiple cooperating files (eg, files that store one or more modules, subroutines, or code sections).

As an example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or alternatively, distributed across multiple sites and interconnected by a communication network execute on.

To sum up, the following technical effects can be achieved through the embodiments of the present application:

(1) In this embodiment of the present application, a plurality of user income information can be grouped according to a preset grouping rule to obtain at least one entry group. At least one user's income information in the account group is updated at the same time. Compared with the scheme of separately updating the income information of each user in the traditional technology, the present application divides multiple user income information corresponding to the same data table into the same account group. The revenue entry operation based on the entry group can reduce the overall time-consuming process of revenue entry and improve the entry efficiency of the overall income entry.

(2) In the embodiment of the present application, by calling the account entry interface to adjust the virtual resources of the accounts corresponding to the income information of each account, the speed of income entry can be accelerated and the time-consuming of income entry can be reduced.

(3) In the embodiment of the present application, by generating a corresponding billing number for each account income information, it is possible to avoid the situation of repeatedly adding new income flow in the account income record, and also avoid repeatedly adjusting the account income information in the process of calling the account income interface. The situation of the virtual resources of the corresponding account improves the security in the process of revenue entry. In addition, in the embodiment of the present application, the recording operations of the billing numbers of the income information of multiple accounts in the same billing group are bound together by means of transactions, which can ensure that the billing numbers corresponding to the income information of each account can be completely recorded, preventing Entry errors caused by missing a billing number. In addition, the embodiment of the present application adopts a locking method in the process of adding a revenue stream to a user revenue record, so that the corresponding user revenue record will not be changed by other processes or services, avoiding repeated operations and ensuring data consistency.

(4) In this embodiment of the present application, the first total amount of resources corresponding to the account revenue information is updated in the database by adding a new flow request, and the second total amount of resources in the local cache is updated by using the first total amount of resources carried in the newly added flow feedback. It can ensure that the total amount of resources corresponding to each user's revenue information in the server's local cache is consistent with that in the database. After receiving the user's request for viewing the total amount of resources, the step of querying the database can be omitted and the computational pressure of the database can be reduced. At the same time, the feedback efficiency of viewing requests can also be improved, and the user experience can be improved; and, in the case where the total amount of the first resource and the total amount of the second resource are different, the corresponding resource adjustment request is not generated, which can not only reduce the cost of the bank interface The computing pressure can also reduce the time-consuming of revenue entry and improve the efficiency of revenue entry.

The above descriptions are merely examples of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements and improvements made within the spirit and scope of this application are included within the protection scope of this application.

Claims (10)

1. A method for recording income, comprising: Grouping multiple account income information to obtain at least one account entry group; the account income record corresponding to each of the account income information in each of the account entry groups is located in the same data table of the database; Calling the account entry interface to perform an entry operation for each of the entry groups; the entry operation is used to adjust the account resources corresponding to each of the account income information in the entry group; In response to the entry feedback of each of the entry groups, sending an entry record request of each of the entry groups to the database; the entry record request is used to instruct the database to update each of the accounts in the entry group The account income record corresponding to the income information. 2. The method according to claim 1, wherein the invoking an account entry interface performs an account entry operation for each of the account entry groups, comprising: Generate at least one resource adjustment request according to each of the account income information in the account entry group; the resource adjustment request carries an account identifier and a resource change amount corresponding to the account income information; Sending each resource adjustment request to the account entry interface; the resource adjustment request is used to instruct the account entry interface to adjust the virtual resource in the account corresponding to the account identifier according to the resource change amount. 3. The method according to claim 2, characterized in that, before generating at least one resource adjustment request corresponding to the at least one account income information according to the at least one account income information in the crediting group, the method further comprises: include: generating a billing number corresponding to each of the account income information in the billing group; Opening a transaction, the transaction includes: sending a new flow request corresponding to each of the account income information to the database; the newly added flow request is used to instruct the database to record in the account income corresponding to the account income information. Add a flow record corresponding to the billing number in ; In the case of receiving the newly added flow feedback corresponding to each of the account income information, the transaction is submitted. 4. The method according to claim 3, wherein the generating at least one resource adjustment request according to each of the account income information in the crediting group comprises: In response to submitting the transaction, a resource adjustment request corresponding to each of the account income information is generated according to each of the account income information in the account entry group; the resource adjustment request also carries the entry corresponding to the account income information. single number. 5. The method according to claim 3, characterized in that, the new running request is also used to update the first total amount of resources corresponding to the account income information in the database; Before generating at least one resource adjustment request, the method further includes: According to the new flow feedback corresponding to each of the account income information sent by the database, obtain the first total amount of resources corresponding to each of the account income information; Update the second total amount of resources corresponding to each of the account income information in the local cache according to the first total amount of resources corresponding to each of the account income information; The generating at least one resource adjustment request according to each of the account income information in the crediting group includes: In the case where the first total amount of resources corresponding to the account income information is different from the second total amount of resources, a resource adjustment request corresponding to the account income information is generated; the resource adjustment request also carries a resource adjustment request corresponding to the account income information Invoice number. 6. The method according to claim 3, characterized in that, before said sending a new flow request corresponding to each said account income information to said database, said method further comprises: for each said account The account income information corresponding to the income information is locked; Before submitting the transaction, the method further includes: unlocking account income information corresponding to each of the account income information. 7. The method according to claim 3, wherein the method further comprises: Receive resource adjustment feedback corresponding to each resource adjustment request sent by the account entry interface; the resource adjustment feedback is used to indicate whether the adjustment operation corresponding to the resource adjustment request is successful; According to each of the resource transfer feedbacks, the crediting feedback is generated; the crediting feedback is used to represent the crediting operation result corresponding to each of the account income information in the crediting group. 8. A revenue entry device, characterized in that it comprises: The grouping module is used for grouping multiple account income information to obtain at least one account entry group; the account income record corresponding to each of the account income information in each of the account entry groups is located in the same data table of the database; an adjustment module, configured to call an account entry interface to perform an entry operation on each of the entry groups; the entry operation is used to adjust the account resources corresponding to each of the account income information in the entry group; An account entry module, configured to send an entry record request of each of the account entry groups to the database in response to the entry feedback of each of the entry groups; the entry record request is used to instruct the database to update the entry in the entry group. The account income record corresponding to each said account income information. 9. A revenue entry device, characterized in that it comprises: memory for storing executable instructions; A processor, configured to implement the method of any one of claims 1 to 7 when executing the executable instructions stored in the memory. 10. A computer-readable storage medium, characterized in that it stores executable instructions for implementing the method of any one of claims 1 to 7 when executed by a processor.

Images