Method and system for account parallel processing

• US 8,788,374 B2
• Filed: 07/14/2010
• Issued: 07/22/2014
• Est. Priority Date: 08/07/2009
• Status: Active Grant

• Current Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Yu, Xinlin, Lou, Fangxin
• Primary Examiner(s): Zeender, Ryan
• Assistant Examiner(s): Haider, Fawaad
• Application Number:
  US12/918,033
• Publication Number:
  US 20120123912A1
• Time in Patent Office: 1,469 Days
• Field of Search: 705/30, 3 3/0
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A method for account parallel processing used by an account processing center to process a request for account operation is disclosed. The method comprises: (1) categorizing accounts as high parallel occurrence accounts and common accounts; (2) when receiving the request from the client for processing operation of an account, firstly determining whether the account is a high parallel occurrence account; and if the account is a high parallel occurrence account, continuing to a step (3), otherwise, conducting a step (4); (3) if the account is locked, queuing a current operation to wait until implementation of the current operation; and (4) further determining, by the account processing center, whether the account is locked and outputting an error message when the account is locked, otherwise implementing the current operation. Such method provides more high quality services to the high parallel occurrence accounts. As for the common accounts, when there is a high volume of parallel transactions on the common accounts, the volume of parallel processing can be effectively controlled by outputting an error message to prevent comment accounts from causing damage the system.

Claims

1. A method comprising:

under a control of a server;

categorizing a plurality of accounts as high parallel occurrence accounts and common accounts at least according to a number of operations of each of the plurality of accounts in a period of time;

saving account identifications of the high parallel occurrence accounts into one or more memories;

determining whether an account is a high parallel occurrence account upon receiving a request from a client for processing the account, the determining including;

comparing an account identification of the account with account identifications of all high parallel occurrence accounts stored in the one or more memories; and

when there is a match between the account identification of the account and one of the account identifications of all the high parallel occurrence accounts, determining that the account is the high parallel occurrence account, otherwise determining that the account is a common account;

when the account is determined to be the high parallel occurrence account, queuing a current operation on the account to wait until an implementation of the current operation;

further determining whether the account is locked;

when the account is determined to be locked, outputting an error message; and

when the account is determined not to be locked, implementing the current operation, the implementation of the current operation including;

locking the account; and

implementing an operation on the account.

2. The method as recited in claim 1, further comprising:

when the account is determined to be locked, delaying a pre-determined period of time and then re-determining whether the current operation is implemented.

3. The method as recited in claim 1, wherein the categorizing further comprises:

setting up a number of high parallel occurrence accounts according to a percentage of high parallel occurrence accounts among the one or more accounts.

4. The method as recited in claim 1, wherein the implementation of the current operation further comprises:

releasing a corresponding lock of the account after the current operation is implemented.

9. The method as recited in claim 1, wherein categorizing accounts as high parallel occurrence accounts and common accounts comprises:

calculating a respective number of operations of each account of the one or more accounts in a predetermined period, and ranking accounts according to their respective number of operations; and

designating a number of accounts with highest number of operations as the high parallel occurrence accounts.

19. The method as recited in claim 1, further comprising saving the account identification of the account into the one or more memories in response to determining that the account is the high parallel occurrence account.

5. A system for account parallel processing comprising:

an account processing center, the account processing center comprising;

a high parallel occurrence account database that stores information of one or more high parallel occurrence accounts, including identifications of the high parallel occurrence accounts, that are determined from one or more accounts based on an importance of each of the one or more accounts into one or more memories;

an account characterization determination unit that determines whether an account is a high parallel occurrence account according to the high parallel occurrence account database when receiving a request for processing the account by;

comparing an account identification of the account with account identifications of all high parallel occurrence accounts stored in the high parallel occurrence account database; and

when there is a match between the account identification of the account and one of the account identifications of all the high parallel occurrence accounts, determining that the account is the high parallel occurrence account, otherwise determining that the account is a common account;

a high parallel occurrence account processing unit that determines whether the account is locked, queues a current operation to wait until implementation of the current operation when the account is locked, and implements the current operation when the account is not locked; and

a common account processing unit that determines whether the account is locked, outputs an error message when the account is locked, and implements the current operation when the account is not locked, the implementation of the current operation including;

locking the account; and

implementing an operation on the account.

6. The system as recited in claim 5, wherein the high parallel occurrence account processing unit comprises:

a high parallel occurrence account lock determination sub-unit that determines whether the high parallel occurrence account is locked; and

an operation implementation sub-unit that locks the account, implements one or more operations on the account, and releases a corresponding lock on the account.

7. The system as recited in claim 5, wherein the common account processing unit comprises:

a common account lock determination sub-unit that determines whether the account is locked;

an operation implementation sub-unit that locks the account, implements one or more operations on the account, and releases a corresponding lock on the account; and

a lock determination sub-unit that receives an operation of the account after the account is locked, and outputs an error message.

8. The system as recited in claim 7, wherein common account processing unit further comprises:

a time delay sub-unit that postpones a pre-determined period of time when the account is locked, re-determines whether the current operation is implemented, and, if negative, outputs an error message.

10. The system as recited in claim 5, wherein the high parallel occurrence account database saves account identifications of high parallel occurrence accounts into memory.

11. A method comprising:

under a control of a server;

categorizing accounts into different types of accounts, the different types of accounts including high parallel occurrence accounts;

saving account identifications of the high parallel occurrence accounts into one or more memories;

establishing processing operations for accounts of each type after a respective account is locked;

determining a type of an account in response to receiving a request for processing the account from the client, the determining including;

comparing an account identification of the account with account identifications of all high parallel occurrence accounts stored in the one or more memories; and

when there is a match between the account identification of the account and one of the account identifications of all the high parallel occurrence accounts, determining that the account is the high parallel occurrence account, otherwise determining that the account is a common account;

determining whether the account is locked;

when the account is locked, processing the account according to a respective processing operation corresponding to the type of the account; and

when the account is not locked, implementing a current operation on the account, the implementation of the current operation including;

locking the account; and

implementing an operation on the account.

12. The method as recited in claim 11, wherein establishing processing operations for accounts of each type after a respective account is locked comprises:

after the account is locked, outputting an error message when M is zero and waiting for time T before further determining if the account is locked;

when the account is further determined to be locked, decrementing M by 1, otherwise implementing the current operation, wherein;

M is a number of waiting times set up for a respective type account, and M can be a number between zero and infinity inclusively.

13. The method as recited in claim 11, wherein categorizing accounts into different types of accounts comprises categorizing accounts as high parallel occurrence accounts and common accounts.

14. The method as recited in claim 13, wherein the categorizing accounts as high parallel occurrence accounts and common accounts comprises setting up a number of high parallel occurrence accounts according to a percentage of high parallel occurrence accounts among all accounts.

15. The method as recited in claim 13, wherein the categorizing accounts as high parallel occurrence accounts and common accounts comprises:

calculating a respective number of operations of each account of the one or more accounts in a predetermined period, and ranking accounts according to their respective number of operations; and

designating a number of accounts with highest number of operations as the high parallel occurrence accounts.

16. The method as recited in claim 13, wherein the categorizing accounts as high parallel occurrence accounts and common accounts comprises saving account identifications of high parallel occurrence accounts into the one or more memories.

17. The method as recited in claim 11, wherein the implementation of the current operation further comprises releasing a corresponding lock of the account after the operation is implemented.

18. The method as recited in claim 11, further comprising saving the account identification of the account into the one or more memories in response to determining that the account is the high parallel occurrence account.