Storage method, account cancellation method, device, equipment and medium for account contract relationship

Abstract

The present application relates to the technical field of data storage, and specifically to a storage method, account cancellation method, device, equipment and medium for account contract relationships, which are used to solve the problem that the existing contract relationship storage method occupies a large amount of memory and is not conducive to data maintenance. The method includes: determining the contract information of the target account, and the contract information at least includes the target contract type for which the target account has the signing authority and the number of contracts of each target contract type. The identification information of the target account is used as the primary key of the database form, and the identification information is associated with the contract information to establish a contract storage record for recording whether the target account has signed a contract. As a result, when the contract signed by the account is updated, the contract storage record can be updated according to the number of contracts to be updated. While fully recording the signed contracts of the account, there is no need to add new storage records, thereby reducing memory usage.

Description

Technical Field

[0001] The present application relates to the technical field of data storage, and in particular to a method for storing account contract relationships, a method for cancelling an account, a device, equipment and a medium. Background Art

[0002] The process of purchasing bank products by users is essentially the signing of a contract between the user account and the product. For example, when a user purchases a wealth management product, the wealth management product will bind the user's current deposit contract as the transaction account. Before the wealth management product is terminated, the bound current deposit contract cannot be cancelled. However, most banking systems have not established a unified and standardized contract relationship recording model. There are many cases where the account has been actively cancelled by the user before the signed product contract has been terminated, resulting in the inability to fully record the account's business information.

[0003] In addition, some banking systems store product contract relationships within a limited business scope, and their storage method mostly adopts a narrow table design to record user accounts and signed contract numbers. When a user cancels an account, it is possible to query whether there is a contract number that has not been terminated in the contract relationship of the account based on the user account, and cancel the account after confirming that there is no unterminated contract. The storage method of the above contract relationship is to generate a record of the account and the signed contract number after each contract signing behavior. However, as the number of product contracts continues to increase, the number of contracts signed by the account also increases. This method occupies a large amount of memory and is not conducive to data maintenance. Summary of the invention

[0004] The embodiments of the present application provide a method for storing account contract relationships, a method for canceling an account, an apparatus, a device, and a medium for storing account contract relationships to reduce memory usage.

[0005] In a first aspect, an embodiment of the present application provides a method for storing an account contract relationship, including:

[0006] Determine the contract information for which the target account has the signing authority, and associate the identification information of the target account with the contract information to establish a contract storage record for recording whether the target account has signed a contract; wherein the contract information includes the target contract types for which the target account has the signing authority and the number of contracts signed for each target contract type;

[0007] In response to a contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the same target contract type as the contract type to be updated.

[0008] The embodiment of the present application predetermines the contract information of the target account, and the contract information includes at least the target contract types for which the target account has the right to sign contracts and the number of contracts of each target contract type. The identification information of the target account is used as the primary key of the database form, and the identification information is associated with the contract information to establish a contract storage record for recording whether the target account has signed a contract. As a result, when the contract signed by the account is updated, the contract storage record can be updated according to the number of contracts to be updated. While fully recording the contracts that the account has signed, there is no need to add new storage records, thereby reducing memory usage.

[0009] In some possible embodiments, associating the identification information of the target account with the contract information to establish a contract storage record for determining whether the target account has a signed contract includes:

[0010] Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract signing quantity of the target contract type;

[0011] The identification information is used as a form primary key, and a database form is constructed based on the first association relationship and the second association relationship; and the database form is used as the contract storage record.

[0012] The embodiment of the present application uses the identification information of the target account as the primary key of the database form, establishes the association between the identification information and the target contract type, and the association between the target contract type and the corresponding contract quantity. Thus, each record generated in the database form represents the number of contracts currently signed by the target account.

[0013] In some possible embodiments, if the contract update indication indicates that the target account signs a new contract, updating the number of signed contracts of the pending contract type in the contract storage record according to the contract type to be updated includes:

[0014] For each contract type to be updated, determine the number of newly added contracts of the contract type to be updated;

[0015] Monitoring whether there is a pending contract type corresponding to the contract type to be updated in the contract storage record; if so, updating the number of signed contracts of the pending contract type according to the number of newly added contracts;

[0016] Otherwise, the contract type to be updated is added to the contract storage record as a designated contract type, and the number of newly added contracts of the contract type to be updated is used as the signed number of the designated contract type.

[0017] When the target account of the embodiment of the present application signs a new contract, the contract storage record can be queried according to the contract type of the newly added contract. Since the identification information of the target account is associated with the target contract type in the contract storage record, if there is a contract type that is the same as the newly added contract type in the contract storage record, the number of contracts of this type can be updated according to the number of newly added contracts. Otherwise, the newly added contract type can be added to the contract record as a specified contract type, without adding a new record for storing the newly added contract type, thereby reducing memory usage.

[0018] In some possible embodiments, if the contract update indication indicates that the target account terminates the signed contract, updating the number of signed contracts of the to-be-processed contract type in the contract storage record according to the to-be-updated contract type includes:

[0019] For each contract type to be updated, determining the number of contract terminations for the contract type to be updated;

[0020] The signing quantity of the pending contract type is updated according to the termination quantity.

[0021] When the target account of the embodiment of the present application terminates a signed contract, the contract storage record can be queried according to the contract type of the terminated contract. Since the identification information of the target account is associated with the target contract type in the contract storage record, if there is a contract type that is the same as the terminated contract type in the contract storage record, the number of contracts of this type can be updated according to the number of terminations. That is, when the number of contracts signed by the target account changes, only the number of contracts of the corresponding contract type in the contract storage record needs to be updated, without adding or deleting records, thereby reducing memory usage.

[0022] In a second aspect, an embodiment of the present application provides a method for canceling an account based on a contractual relationship, the method comprising:

[0023] In response to the target account cancellation instruction, determine the contract storage record of the target account according to the identification information of the target account; wherein the contract storage record is constructed based on the target contract type for which the target account has the signing authority, and the contract storage record is used to record whether the target account has signed the contract;

[0024] Monitor whether there is a specified contract type with a contract signing quantity greater than a preset threshold in the contract storage record; if so, determine that the target account does not have the account cancellation authority.

[0025] The embodiment of the present application queries the contract storage record of the target account through the identification information of the target account. The contract storage record is constructed based on the target contract type for which the target account has the signing authority, and stores the number of contracts corresponding to each target contract type. By querying the number of contracts in the contract storage record, it can be determined whether the target account has an unterminated contract. Through the above process, it can be determined whether the target account has the right to cancel the account based on the number of contracts in the contract storage record, and the contract storage record does not need to record the contract number of the specific contract signed by the target account, thereby reducing memory usage.

[0026] In a third aspect, an embodiment of the present application provides a storage device for an account contract relationship, the device comprising:

[0027] an information acquisition module, configured to determine the contract information for which the target account has the signing authority, and associate the identification information of the target account with the contract information to establish a contract storage record for recording whether the target account has signed the contract; wherein the contract information includes the target contract types for which the target account has the signing authority and the number of contracts signed for each target contract type;

[0028] The update module is configured to execute in response to a contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the target contract type that is the same as the contract type to be updated.

[0029] In some possible embodiments, the step of associating the identification information of the target account with the contract information to establish a contract storage record for determining whether the target account has a signed contract is performed, and the information acquisition module is configured to:

[0030] Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract signing quantity of the target contract type;

[0031] The identification information is used as a form primary key, and a database form is constructed based on the first association relationship and the second association relationship; and the database form is used as the contract storage record.

[0032] In some possible embodiments, if the contract update indication indicates that the target account signs a new contract, the updating module is configured to update the number of signed contracts of the pending contract type in the contract storage record according to the contract type to be updated:

[0033] For each contract type to be updated, determine the number of newly added contracts of the contract type to be updated;

[0034] Monitoring whether there is a pending contract type corresponding to the contract type to be updated in the contract storage record; if so, updating the number of signed contracts of the pending contract type according to the number of newly added contracts;

[0035] Otherwise, the contract type to be updated is added to the contract storage record as a designated contract type, and the number of newly added contracts of the contract type to be updated is used as the signed number of the designated contract type.

[0036] In some possible embodiments, if the contract update indication indicates that the target account has terminated the signed contract, the updating of the number of signed contracts of the to-be-processed contract type in the contract storage record according to the to-be-updated contract type is performed, and the updating module is configured to:

[0037] For each contract type to be updated, determining the number of contract terminations for the contract type to be updated;

[0038] The signing quantity of the pending contract type is updated according to the termination quantity.

[0039] In a fourth aspect, an embodiment of the present application provides an account cancellation device based on a contractual relationship, the device comprising:

[0040] A record calling module is configured to execute, in response to an account cancellation instruction of a target account, determine a contract storage record of the target account according to identification information of the target account; wherein the contract storage record is constructed based on a target contract type for which the target account has contract signing authority, and the contract storage record is used to record whether the target account has signed a contract;

[0041] The authority confirmation module is configured to monitor whether there is a specified contract type with a contract signing quantity greater than a preset threshold in the contract storage record; if so, it is determined that the target account does not have the authority to close the account.

[0042] In a fifth aspect, the present application provides an electronic device, including:

[0043] A memory for storing program instructions;

[0044] The processor is used to call the program instructions stored in the memory, and execute the steps included in the method of any one of the first aspect or the second aspect according to the obtained program instructions.

[0045] In a sixth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method described in any one of the first aspect or the second aspect.

[0046] In a seventh aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes the method described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1a A schematic diagram of a traditional wide table structure for recording contract relationships provided in an embodiment of the present application;

[0048] Figure 1b A schematic diagram of contractual relationships when a contract of the same type provided in an embodiment of the present application is signed multiple times;

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

[0050] Figure 3a A flow chart of a method for storing account contract relationships provided in an embodiment of the present application;

[0051] Figure 3b A schematic diagram of contract storage records provided in an embodiment of the present application;

[0052] Figure 3c A schematic diagram of contract storage record optimization provided in an embodiment of the present application;

[0053] Figure 3d A schematic diagram of prompt information provided in an embodiment of the present application;

[0054] Figure 3e A schematic diagram of updating a contract storage record based on a newly added contract provided in an embodiment of the present application;

[0055] Figure 4 A flow chart of an account cancellation method based on a contractual relationship provided in an embodiment of the present application;

[0056] Figure 5 A structural diagram of a storage device 500 for an account contract relationship provided in an embodiment of the present application;

[0057] Figure 6 A structural diagram of an account cancellation device 600 based on a contractual relationship provided in an embodiment of the present application;

[0058] Figure 7 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0060] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0061] In the technical solution of this application, the collection, dissemination, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0062] As mentioned above, the process of purchasing bank products by users is essentially the signing of contracts for products by user accounts. For example, when users purchase wealth management products, the wealth management products will bind the user's current deposit contract as the transaction account. Before the wealth management product is terminated, the bound current deposit contract cannot be cancelled. The existing contract relationship storage method mostly adopts a narrow table design to associate the user account with the signed contract number. Every time a user signs a new contract, a new contract record will be added. According to statistics, some large commercial banks have deposit contracts of up to hundreds of millions per year, and the amount of contract relationship data is nearly one billion, which takes up a lot of memory and is not conducive to data maintenance.

[0063] In addition, some banking systems use a wide table structure to record contractual relationships by adding a signing mark to the user account. This method pre-binds the contract relationship type field to the user account. When a user purchases a banking product, an effective mark is added under the contract type of the banking product in the contract relationship type field. The effective mark indicates that the user has signed a contract of this type. Accordingly, when the contract is terminated, the effective mark is replaced with an invalid mark. Figure 1aAs shown in the figure, it is assumed that the user account has purchased two fund financial services of different contract types, namely the full-trust investment advisory contract to which service 1 belongs, and the fund off-site scenario contract to which service 2 belongs. This method will bind the user account to the above two contract types and add effective marks to the above two contract types to indicate that the account has purchased these two services.

[0064] The problems with this method are as follows: When a new product has a binding requirement, the user account needs to modify the contract relationship data table and add a data field to record the new contract relationship type. If the contract relationship type is added frequently, the frequency of data table modification will also increase, increasing the workload of system development while also increasing system risks. In addition, this method does not record specific contract numbers to save memory, and therefore does not support multiple contracts of the same contract relationship type. Figure 1b As shown, when the user purchased the fund, he purchased the fixed investment service. The fixed investment service represents a contract type, and the fund corresponding to the fixed investment service is a specific financial product. Assuming that the user purchased funds 1-3 through the fixed investment service, it means that the user has signed three fund contracts 1-3 of the same contract type. When the user completes the purchase, the full-trust investment advisory contract corresponding to the fixed investment service in the contract relationship type field sets the effective flag. When the user terminates the contract with fund contract 1, the user still has a contractual relationship with funds 2 and 3, but the effective flag will be set to an invalid flag. If the user cancels the account at this time, the business information of the account cannot be fully recorded, affecting subsequent business, for example, the financial management funds of funds 2 and 3 cannot be delivered to the user's account.

[0065] To solve the above problems, the inventive concept of the present application is as follows: predetermine the contract information of the target account, and the contract information at least includes the target contract types for which the target account has the right to sign contracts and the number of contracts of each target contract type. Use the identification information of the target account as the primary key of the database form, associate the identification information with the contract information, and establish a contract storage record for recording whether the target account has signed a contract. As a result, when the contract signed by the account is updated, the contract storage record can be updated according to the number of contracts to be updated. While fully recording the contracts that the account has signed, there is no need to add new storage records, thereby reducing memory usage.

[0066] See also Figure 2 , is a schematic diagram of an application environment according to an embodiment of the present application.

[0067] like Figure 2 As shown, the application environment may include, for example, a network 10, an electronic device 20, a server 30, and a database 40. The electronic device 20 may be Figure 2The smart phone 20_1, smart computer 20_2 and laptop computer 20_n shown in the figure are smart devices with human-computer interaction functions; the database 40 can be a public database of the bank system, a local database of the bank's office computer, etc.

[0068] exist Figure 2 In the application scenario shown, a small program associated with a bank account can be installed on the electronic device 20. The user can send an account cancellation instruction to the server 30 through the electronic device 20. The server 30 queries the database 40 according to the identification information of the account to obtain the contract storage record of the account.

[0069] In some possible embodiments, the contract storage record stores each contract type for which the account has the right to sign contracts, and the number of contracts signed for each contract type. If the contract storage record contains a specified contract type with a contract number not equal to 0, it is determined that the account does not have the right to cancel the account. At this time, the server 30 can send a prompt message to the electronic device 20 through the network 10 indicating that the account currently has an unresolved contract and cannot cancel the account.

[0070] It should be noted that the above description only details a single server or terminal device, but those skilled in the art should understand that Figure 2 The server 30 and database 40 shown are intended to illustrate the operation of the server and storage system involved in the technical solution of the present application. The detailed description of a single server and storage system is at least for the convenience of explanation, and does not imply any limitation on the number, type, or location of the server and storage system. It should be noted that if additional modules are added to the illustrated environment or individual modules are removed from it, it will not change the underlying concepts of the example embodiments of the present application. In addition, although for the convenience of explanation, Figure 2 A bidirectional arrow from the database 40 to the server 30 is shown in the figure, but those skilled in the art will appreciate that the sending and receiving of the above data also needs to be implemented through the network 10.

[0071] Figure 3a The following is a schematic diagram showing a flow chart of a method for cancelling an account based on a contractual relationship provided in an embodiment of the present application. Figure 3a As shown, the following steps are included:

[0072] Step 301: Determine the contract information for which the target account has the signing authority, associate the identification information of the target account with the contract information, and establish a contract storage record for recording whether the target account has signed the contract; wherein the contract information includes the target contract types for which the target account has the signing authority and the number of contracts signed for each target contract type;

[0073] During implementation, the identification information of the target account is used as the primary key of the database form, and a first association relationship between the identification information and the target contract type, and a second association relationship between the identification information and the contract quantity are established to establish a contract storage record. It should be noted that the above identification information is the unique identification of the target account, such as the account's exclusive serial number (ID, Identity document)), account number, etc., and this application does not limit this.

[0074] The contract storage records constructed through the above process are as follows Figure 3b As shown, a wide table mode design is adopted, the primary key is the identification information of the target account, and the data field is the target contract relationship type and the corresponding contract quantity. In the contract storage record of the embodiment of the present application, only the association relationship between the identification information and the target contract relationship type is established, so there is no need to set the specific target contract relationship type, and dynamic writing is supported. In this way, when the target account signs a new contract, the data field "target contract type x" and the corresponding "contract quantity x" can be written into the record in sequence according to the timing of signing the contract.

[0075] like Figure 3b As shown in the figure, "target contract type x" represents the classification of contracts, which may include financial contracts, loan contracts, debit card contracts, etc. System operators can use the column to identify which product's contract the current contract is bound to. "Contract quantity x" is a contract counting mark. Each "target contract type x" corresponds to "contract quantity x", where x is a positive integer. "Contract quantity x" represents the number of "target contract type x" signed by the target account.

[0076] In addition, since the database form has a fixed size, there is a situation where the target contract type signed by the target account exceeds the maximum record length of a single form. In this embodiment of the application, the contract storage record is also provided with technical fields "#record number" and "#extension flag" to solve the above problem. Figure 3cAs shown in the figure, "#Record Sequence Number" is used to indicate how many forms exist in this contract storage record. Assuming that a single form allows recording of 5 types of contracts, and the target account has signed a total of 10 target contract types, 2 forms are required. At this time, the contract relationship type exceeds the record line of a single form. At this time, the "#Extended Flag" is set to 1 to indicate that there are multiple forms in this contract storage record. When recording, the signing data of these 10 target contract types are written in sequence. After the current 5 types are written, the "#Record Sequence Number" needs to be increased by one to add a blank form for writing the next 5 types. That is, the "#Record Sequence Number" of the first form is 1, and the "#Record Sequence Number" of the second form is 2. Correspondingly, when reading the contract storage record of the target account, first read whether the "#Extended Flag" is set to 1. If it is set to 1, it indicates that there are multiple forms in the contract storage record. At this time, the two forms of "#Record Sequence Number" 1 and 2 need to be called out to ensure that the complete contract storage record is obtained.

[0077] In the above process, by establishing the association between the identification information of the target account, the target contract type and the contract quantity, two dynamic fields supporting automatic writing, "target contract type x" and "contract quantity x", are set for the contract storage record. Based on the data structure of the original record contract sign, the contract storage record of the embodiment of the present application modifies the contract relationship type field from the original solidified form to the dynamic maintenance mode, and supports arbitrary expansion of the contract relationship type without changing the program and data table structure. It not only records the necessary information of the contract relationship, but also greatly reduces the amount of data, reduces the number of database reads, and improves system performance.

[0078] Step 302: In response to the contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the same target contract type as the contract type to be updated.

[0079] When the user's contractual relationship changes, the contract storage record needs to be updated synchronously. The user's contractual relationship changes include two situations: signing a new contract and terminating an already signed contract.

[0080] When a user signs a new contract, it is only necessary to automatically write to the dynamic field according to the relevant information of the newly signed contract, and no new storage records will be added, which reduces the memory usage. Specifically, when the target account signs a new contract, the contract type to be updated (i.e., the newly signed contract) is pre-determined. For each contract type to be updated, determine whether there is a pending contract type that is the same as the contract type to be updated in the contract storage record. It should be noted here that since the "target contract type x" in the contract storage record supports dynamic writing by the user, the target contract type stored each time is actually recorded as target contract type 1, target contract type 2, etc. The actual meaning of each target contract type is pre-marked in the data dictionary. For example, according to the classification of bank products, the contract type is pre-classified into financial management, lending, and debit card types. Then target contract type 1 represents the financial management type, target contract type 2 represents the lending type, and target contract type 3 represents the debit card type.

[0081] When the target account adds a new contract, the details are as follows Figure 3e As shown, the newly added contract is a financial contract, and the number of newly added contracts is 2. It is necessary to first determine whether the financial type is set in the data dictionary. Assuming that this type exists, and the contract type corresponding to the financial type is the target contract type 1, then the target contract type 1 is the pending contract type. Assuming that the current record of the contract quantity 1 of the target contract type 1 is 5. At this time, it is necessary to update the contract quantity 1 according to the number of newly added contracts, and add the current record of the contract quantity 1 to the number of newly added contracts. At this time, the record of the contract quantity 1 should be 7. Correspondingly, assuming that the new contract is a new product launched by the bank, the contract type of the product is not stored in the data dictionary, that is, there is no pending contract type with the same new contract type in the contract storage record. At this time, it is necessary to add the contract type to which the product belongs in the data dictionary, and add the relevant information of the new contract to the contract storage record. Specifically, for example, if the contract type to which the product belongs is insurance, it is necessary to add a target contract type 4 representing the insurance type and a contract quantity 4 corresponding to the target contract type 4 in the contract storage record. And fill the number of new contracts of the new contract type into the contract quantity 4.

[0082] Similarly, when a user cancels a signed contract, the relevant information of the contract to be cancelled needs to be obtained, and the dynamic column needs to be automatically written according to the relevant information of the contract to be cancelled. Specifically, when the target account cancels the contract, the contract type to be updated (i.e. the contract to be cancelled) is determined in advance, and for each contract type to be updated, the contract type to be processed that is the same as the contract type to be updated in the contract storage record is determined. And the signing quantity of the contract type to be processed is updated according to the savings quantity of the contract type to be updated.

[0083] Based on the same inventive concept, the embodiment of the present application provides an account cancellation method based on a contractual relationship, specifically as follows: Figure 4 As shown, including:

[0084] Step 401: In response to an account cancellation instruction of a target account, determine a contract storage record of the target account according to identification information of the target account; wherein the contract storage record is constructed based on a target contract type for which the target account has contract signing authority, and the contract storage record is used to record whether the target account has signed a contract;

[0085] As mentioned above, the contract storage record of the embodiment of the present application is constructed with the identification information of the target account as the primary key. Therefore, when the target account requests to be closed, the contract storage record used to record whether the target account has signed the contract can be retrieved by querying the identification information of the target account.

[0086] Step 402: Monitor whether there is a specified contract type with a contract signing quantity greater than a preset threshold in the contract storage record; if so, determine that the target account does not have the right to close the account.

[0087] Since the target account cannot be closed if there is a contractual relationship, after obtaining the contract storage record of the target account, it is necessary to check whether the "contract quantity x" in the contract storage record is greater than 0. If so, it means that the target account currently has a contract that has not been terminated. Figure 3d As shown, a prompt message is sent to the user indicating that the target account cannot be closed due to the existence of a contractual relationship, so that the user can terminate the signed contract in time.

[0088] Based on the same inventive concept, the present embodiment provides a storage device 500 for an account contract relationship, specifically as follows: Figure 5 As shown, including:

[0089] The information acquisition module 501 is configured to determine the contract information for which the target account has the signing authority, and associate the identification information of the target account with the contract information to establish a contract storage record for recording whether the target account has signed the contract; wherein the contract information includes the target contract types for which the target account has the signing authority and the number of contracts signed for each target contract type;

[0090] The update module 502 is configured to execute in response to a contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the target contract type that is the same as the contract type to be updated.

[0091] In some possible embodiments, the step of associating the identification information of the target account with the contract information to establish a contract storage record for determining whether the target account has a signed contract is performed, and the information acquisition module 501 is configured to:

[0092] Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract signing quantity of the target contract type;

[0093] The identification information is used as a form primary key, and a database form is constructed based on the first association relationship and the second association relationship; and the database form is used as the contract storage record.

[0094] In some possible embodiments, if the contract update indication indicates that the target account signs a new contract, the updating module 502 is configured to update the number of signed contracts of the pending contract type in the contract storage record according to the contract type to be updated:

[0095] For each contract type to be updated, determine the number of newly added contracts of the contract type to be updated;

[0096] Monitoring whether there is a pending contract type corresponding to the contract type to be updated in the contract storage record; if so, updating the number of signed contracts of the pending contract type according to the number of newly added contracts;

[0097] Otherwise, the contract type to be updated is added to the contract storage record as a designated contract type, and the number of newly added contracts of the contract type to be updated is used as the signed number of the designated contract type.

[0098] In some possible embodiments, if the contract update indication indicates that the target account has terminated the signed contract, the updating module 502 is configured to update the number of signed contracts of the to-be-processed contract type in the contract storage record according to the to-be-updated contract type:

[0099] For each contract type to be updated, determining the number of contract terminations for the contract type to be updated;

[0100] The signing quantity of the pending contract type is updated according to the termination quantity.

[0101] Based on the same inventive concept, the embodiment of the present application provides an account cancellation device 600 based on a contractual relationship, specifically as follows: Figure 6 As shown, including:

[0102] The record calling module 601 is configured to execute, in response to the target account cancellation instruction, determine the contract storage record of the target account according to the identification information of the target account; wherein the contract storage record is constructed based on the target contract type for which the target account has the signing authority, and the contract storage record is used to record whether the target account has signed the contract;

[0103] The authority confirmation module 602 is configured to monitor whether there is a specified contract type with a contract signing quantity greater than a preset threshold in the contract storage record; if so, it is determined that the target account does not have the authority to close the account.

[0104] Refer to the following Figure 7 The electronic device 130 according to this embodiment of the present application is described. Figure 6 The electronic device 130 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

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

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

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

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

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

[0110] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 132 including instructions, and the instructions can be executed by the processor 131 of the device 400 to complete the above method. Alternatively, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0111] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, which, when executed by the processor 131, implements any one of the methods for storing account contract relationships and canceling accounts provided in the present application.

[0112] In an exemplary embodiment, various aspects of a method for storing an account contract relationship and a method for canceling an account provided by the present application may also be implemented in the form of a program product, which includes a program code. When the program product is run on a computer device, the program code is used to enable the computer device to execute the steps of a method for storing an account contract relationship and a method for canceling an account according to various exemplary embodiments of the present application described above in this specification.

[0113] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

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

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

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

[0117] The program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "like" or similar programming languages. The program code may be executed entirely on the user electronic device, partially on the user device, as a separate software package, partially on the user electronic device and partially on a remote electronic device, or entirely on a remote electronic device or server. In cases involving remote electronic devices, the remote electronic device may be connected to the user electronic device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external electronic device (e.g., via the Internet using an Internet service provider).

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

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

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

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

[0122] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable image scaling device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0123] These computer program instructions may also be loaded onto a computer or other programmable image scaling device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

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

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

Claims

1. A method for storing account contract relationships, It is characterized in that The method comprises: Determine the contract information for which the target account has the signing authority; wherein the contract information includes the target contract types for which the signing authority is provided and the number of contracts signed for each target contract type; Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract quantity of the target contract type; Using the identification information as a form primary key, and constructing a contract storage record for recording whether the target account has signed a contract based on the first association relationship and the second association relationship; In response to a contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the same target contract type as the contract type to be updated.

2. The method according to claim 1, It is characterized in that If the contract update indication indicates that the target account signs a new contract, updating the number of signed contracts of the pending contract type in the contract storage record according to the contract type to be updated includes: For each contract type to be updated, determine the number of newly added contracts of the contract type to be updated; Monitoring whether there is a pending contract type corresponding to the contract type to be updated in the contract storage record; if so, updating the number of signed contracts of the pending contract type according to the number of newly added contracts; Otherwise, the contract type to be updated is added to the contract storage record as a designated contract type, and the number of newly added contracts of the contract type to be updated is used as the signed number of the designated contract type.

3. The method according to claim 1, It is characterized in that If the contract update indication indicates that the target account terminates the signed contract, updating the number of signed contracts of the pending contract type in the contract storage record according to the contract type to be updated includes: For each contract type to be updated, determining the number of contract terminations for the contract type to be updated; The signing quantity of the pending contract type is updated according to the termination quantity.

4. A method for canceling an account based on a contractual relationship. It is characterized in that The method comprises: In response to an account cancellation instruction of a target account, determining a contract storage record of the target account according to identification information of the target account; Monitoring whether there is a designated contract type with a contract quantity greater than a preset threshold in the contract storage record; if so, determining that the target account does not have the right to cancel the account; The contract storage record is determined by: determining the contract information for which the target account has the signing authority; wherein the contract information includes the target contract type for which the target account has the signing authority and the number of contracts signed for each target contract type; Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract signing quantity of the target contract type; Using the identification information as a form primary key, a contract storage record for recording whether the target account has signed a contract is constructed based on the first association relationship and the second association relationship.

5. A storage device for account contract relationships, It is characterized in that The device comprises: An information acquisition module is configured to determine the contract information of the target account with the signing authority, wherein the contract information includes the target contract type with the signing authority and the signing quantity of each target contract type; A storage module is configured to execute the establishment of a first association relationship between the identification information and the target contract type, and to establish a second association relationship between the identification information and the number of contracts signed for the target contract type; using the identification information as a form primary key, and constructing a contract storage record for recording whether the target account has signed a contract based on the first association relationship and the second association relationship; In response to a contract update indication, determine the contract type to be updated of the target account; update the signing quantity of the pending contract type in the contract storage record according to the contract type to be updated; wherein the pending contract type is the same target contract type as the contract type to be updated.

6. An account cancellation device based on a contractual relationship, It is characterized in that The device comprises: a record calling module, configured to execute, in response to an account cancellation instruction of a target account, determining a contract storage record of the target account according to identification information of the target account; The authority confirmation module is configured to monitor whether there is a specified contract type with a contract quantity greater than a preset threshold in the contract storage record; if so, determine that the target account does not have the right to cancel the account; The contract storage record is determined by: determining the contract information for which the target account has the signing authority; wherein the contract information includes the target contract type for which the target account has the signing authority and the number of contracts signed for each target contract type; Establishing a first association relationship between the identification information and the target contract type, and establishing a second association relationship between the identification information and the contract signing quantity of the target contract type; Using the identification information as a form primary key, a contract storage record for recording whether the target account has signed a contract is constructed based on the first association relationship and the second association relationship.

7. An electronic device, It is characterized in that include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in any one of claims 1-4 according to the obtained program instructions.

8. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 4.

9. A computer program product, It is characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 4.

Images