A method, device, equipment and medium for contract termination

Abstract

This application relates to the field of data processing technology, and in particular to a method, apparatus, device, and medium for contract termination. In this embodiment, a termination application instruction can be sent to a target device based on a received processing instruction for terminating a contract with a dormant customer in a target transaction. This causes the target device to modify the customer contract status corresponding to each dormant customer whose identification information to be terminated is carried in the termination application instruction to a termination status. When the number of dormant customer identification information whose status has been modified to termination sent by the target device exceeds a preset threshold, the termination is determined to be complete. This achieves automatic batch termination of contracts with dormant customers in a target transaction, eliminating the need for dormant customers to terminate the contract themselves, thus improving the efficiency of contract termination and enhancing the user experience.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device and medium for unwinding. Background Technology

[0002] According to the requirements of transaction supervision, it is necessary to gradually and orderly suspend investment transactions of personal bank accounts, such as precious metal transactions, and clear dormant customers. Dormant customers refer to customers who have signed contracts but do not have related transactions within a fixed statistical period, that is, inactive customers who have signed contracts but meet certain conditions.

[0003] Terminating dormant customers' contracts is the first and crucial step in the liquidation process. In current technology, dormant customers are usually notified manually so that they can terminate the contract themselves. However, since the number of dormant customers with investment transactions in their personal bank accounts is in the tens of millions, relying on dormant customers to terminate the contract themselves would be too inefficient and would require manual operation by users, affecting the user experience. Summary of the Invention

[0004] This application provides a cancellation method, apparatus, device, and medium to solve the problem that the cancellation efficiency in the prior art is too low, which affects the user experience.

[0005] This application provides a method for terminating a contract, the method comprising:

[0006] Receive processing instructions to terminate contracts with dormant customers for the target transaction;

[0007] For the dormant customers of the target transaction that are to be terminated and are stored in advance, a termination application instruction is sent to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; the target device sends the identification information of the dormant customers whose contract status has been changed to termination status.

[0008] If the number of received identification information of dormant customers whose status has been modified to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0009] Furthermore, before determining that the cancellation is complete if the number of received identifiers of dormant customers whose status has been modified to cancel exceeds a preset threshold, the method further includes:

[0010] Determine whether the time interval since the last quantity count has reached a preset time interval. If so, count the number of the received identification information of dormant customers whose status has been changed to cancellation.

[0011] Furthermore, after sending the termination request instruction to the target device, the method further includes:

[0012] If a termination stop processing instruction is received, a termination application stop instruction is sent to the target device so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identified information.

[0013] Furthermore, before receiving the processing instruction to terminate the contract for the dormant customer of the target transaction, the method further includes:

[0014] According to the preset grouping rules, the dormant customers of the target transaction are divided into multiple groups;

[0015] Sending a termination request instruction to the target device for the dormant customers whose pre-saved target transactions are pending termination includes:

[0016] For each group of dormant customers to be terminated in the pre-saved target transaction, a termination request instruction is sent to the target device for that group of dormant customers, wherein the termination request instruction carries the identification information of each dormant customer in that group.

[0017] Further, determining that the cancellation is complete if the number of received identifiers of dormant customers whose status has been modified to cancel is greater than a preset threshold includes:

[0018] If the number of identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold for each group, then the termination is determined to be complete.

[0019] This application also provides a method for terminating the contract, the method comprising:

[0020] In response to the target transaction to be terminated selected by the target user, for the dormant customers to be terminated in the pre-saved target transaction, the customer contract status corresponding to each dormant customer with identification information is modified to termination status; the identification information of the dormant customers whose termination status has been modified is obtained;

[0021] If the number of identified dormant customers whose status has been changed to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0022] This application also provides a cancellation device, the device comprising:

[0023] The receiving module is used to receive processing instructions for canceling contracts with dormant customers of the target transaction;

[0024] The first processing module is used to send a termination application instruction to the target device for the dormant customers of the target transaction that are to be terminated in a pre-saved list, so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; and receives the identification information of the dormant customers whose termination status has been changed by the target device.

[0025] The first determining module is used to determine that the cancellation is completed if the number of received identification information of dormant customers whose status has been modified to be cancelled is greater than a preset number threshold.

[0026] Furthermore, the device also includes:

[0027] The judgment module is used to determine whether the time interval since the last quantity statistics has reached a preset time interval. If so, it counts the number of the received identification information of the dormant customers whose status has been changed to cancellation.

[0028] Furthermore, the first processing module is also configured to send a termination application stop instruction to the target device if a termination stop instruction is received, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identification information.

[0029] Furthermore, the device also includes:

[0030] The grouping module is used to divide the dormant customers of the target transaction into multiple groups according to preset grouping rules;

[0031] The first processing module is specifically used to send a cancellation request instruction to the target device for each group of dormant customers to be cancelled in the pre-saved target transaction, wherein the cancellation request instruction carries the identification information of each dormant customer in the group to be cancelled.

[0032] Furthermore, the first determining module is specifically used to determine that the cancellation is completed if the number of identification information of the dormant customers whose status has been modified to be cancelled for each group is greater than a preset number threshold.

[0033] This application also provides a cancellation device, the device comprising:

[0034] The second processing module is used to respond to the target transaction to be terminated selected by the target user, and for the dormant customers to be terminated in the pre-saved target transaction, modify the customer contract status corresponding to each dormant customer with identification information to the termination status; and obtain the identification information of the dormant customers whose termination status has been modified.

[0035] The second determining module is used to determine that the cancellation is completed if the number of the obtained identification information of the dormant customers whose status has been modified to be cancelled is greater than a preset number threshold.

[0036] This application also provides an electronic device, which includes at least a processor and a memory, wherein the processor is configured to implement the steps of any of the above-described unwinding methods when executing a computer program stored in the memory.

[0037] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above-described unwinding methods.

[0038] This application also provides a computer program product, which includes: computer program code, and steps that, when the computer program code is run on a computer, cause the computer to perform any of the above-described unwinding methods.

[0039] In this application, a processing instruction to terminate dormant customers for a target transaction is received. For a pre-saved list of dormant customers awaiting termination for a target transaction, a termination application instruction is sent to a target device. This causes the target device to change the customer's contract status for each dormant customer with identified information to a termination status. The termination application instruction carries the identifier information of each dormant customer to be terminated. The application receives the identifier information of dormant customers whose termination status has been changed from the target device. If the number of received identifier information of dormant customers whose termination status has been changed exceeds a preset threshold, the termination is considered complete. In this embodiment, by sending a termination application instruction to the target device based on the received processing instruction to terminate dormant customers for a target transaction, the target device can change the customer's contract status for each dormant customer with identified information carried in the termination application instruction to a termination status. Furthermore, the termination is considered complete when the number of received identifier information of dormant customers whose termination status has been changed exceeds a preset threshold. This achieves automatic batch termination of dormant customers for a target transaction, eliminating the need for dormant customers to manually terminate their contracts, thus improving termination efficiency and user experience. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1A schematic diagram of a contract termination process provided for some embodiments of this application;

[0042] Figure 2 This application provides a schematic diagram illustrating the task status update process of a task status table in a database during the cancellation process, as shown in some embodiments of the application.

[0043] Figure 3 A schematic diagram illustrating a process for determining whether a contract termination is successful, provided for some embodiments of this application;

[0044] Figure 4 A schematic diagram of a contract termination process provided for some embodiments of this application;

[0045] Figure 5 A schematic diagram of a release device structure provided for some embodiments of this application;

[0046] Figure 6 A schematic diagram of a release device structure provided for some embodiments of this application;

[0047] Figure 7 This application provides a schematic diagram of the structure of an electronic device according to some embodiments;

[0048] Figure 8 This application also provides a schematic diagram of the structure of an electronic device in some embodiments. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0050] In this application, a processing instruction is received to terminate the contract of a dormant customer for a target transaction. For the dormant customers to be terminated in the pre-saved target transaction, a termination application instruction is sent to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated. The target device receives the identification information of dormant customers whose termination status has been changed. If the number of dormant customer identification information whose termination status has been changed received is greater than a preset number threshold, the termination is determined to be completed.

[0051] To improve the efficiency of contract termination and reduce the risk of contract termination, this application provides a contract termination method, apparatus, device and medium.

[0052] Example 1:

[0053] Figure 1 A schematic diagram of a contract termination process is provided for some embodiments of this application. The process includes the following steps:

[0054] S101: Receive processing instructions to terminate contracts for dormant customers of the target transaction.

[0055] The cancellation method provided in this application is applied to electronic devices, such as smart terminals, PCs, or servers.

[0056] In this embodiment, to determine which dormant customer in a transaction should be terminated, the target user can first log in to their account via an application on an electronic device, select the target transaction to be terminated, and then the electronic device will receive a processing instruction to terminate the dormant customer in that target transaction. This target user is typically an administrator with termination decision authority. Generally, the target user can choose when to terminate the transaction, but the timing of the termination of the dormant customer under the target transaction often depends on specific regulatory requirements and operational conditions. This method, where the target user voluntarily chooses the timing of termination for the dormant customer under the target transaction, replaces the end-of-day batch processing method, ensuring that the target user can randomly choose whether to terminate the dormant customer according to their own needs. This method can respond promptly to transaction processing requirements.

[0057] The target transaction involved in the embodiments of this application may be account commodity trading, account foreign exchange trading, and account precious metal trading, etc. In the embodiments of this application, there is no limitation on the target transaction.

[0058] The dormant customers involved in this application embodiment refer to customers who have signed contracts but do not have related transactions within a fixed statistical period, that is, inactive customers who have signed contracts but meet certain conditions.

[0059] For ease of description, the specific embodiments described below will use account-based precious metal trading as an example. Account-based precious metal trading refers to a transaction in which investors establish long or short positions using margin trading based on the precious metal buy / sell prices quoted by banks, in order to achieve the purpose of hedging and increasing value. In the process of account-based precious metal trading, investors use currency to pay the trading margin and open a position to establish a certain ratio of account-based precious metal positions. This position is different from the account-based precious metal positions formed by investors' actual trading. It can only be used for closing out positions and cannot be used to open margin trading again, nor can it be physically settled.

[0060] If the target transaction is account precious metals trading, then dormant clients of account precious metals trading refer to clients who signed contracts before the specified date of account precious metals trading, whose account precious metals trading positions are 0 after the specified date, and who have not conducted any account precious metals opening or closing transactions.

[0061] S102: For the dormant customers of the target transaction to be terminated that are pre-saved, send a termination application instruction to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated. Receive the identification information of the dormant customers whose termination status has been changed by the target device.

[0062] In this embodiment of the application, the electronic device pre-stores dormant customers to be terminated under each transaction. The dormant customers under different transactions may be the same or different.

[0063] After receiving a processing instruction to cancel a dormant customer's contract for a target transaction, the electronic device sends a cancellation request instruction to the target device for the dormant customers whose contracts for the target transaction are to be canceled, based on a pre-saved list. This cancellation request instruction carries the identification information of each dormant customer whose contract for the target transaction is to be canceled. The identification information of the dormant customer can be the customer's name, account, etc., or a pre-set one-hot code, etc. Specifically, in this embodiment, the identification information of the dormant customer is not limited, as long as it can distinguish the dormant customer.

[0064] To terminate contracts with dormant customers in a target transaction, upon receiving a termination request instruction from an electronic device, the target device, based on the identification information of each dormant customer to be terminated carried in the termination request instruction, modifies the customer's contract status to a terminated status for each identified dormant customer and sends the modified identification information of the dormant customers to the electronic device. The customer contract status includes both a signed-up status and a terminated status, etc., and before any termination operation is performed on a dormant customer, the customer's contract status is generally a signed-up status.

[0065] Specifically, the target device can send the identification information of the dormant customer whose contract status has been changed to a cancelled status to the electronic device after each time it changes the contract status of a dormant customer to a cancelled status. In other words, the electronic device can receive the identification information of the dormant customers whose contract status has been changed to a cancelled status from the target device one by one. The target device can also change the contract status of a preset number of dormant customers to a cancelled status and simultaneously send the identification information of the preset number of dormant customers whose contract status has been changed to a cancelled status from the target device to the electronic device. In other words, the electronic device receives the identification information of the dormant customers whose contract status has been changed to a cancelled status from the target device in preset units.

[0066] S103: If the number of received identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold, then the termination is determined to be completed.

[0067] In this embodiment of the application, the electronic device gradually accumulates the identification information of dormant customers whose status has been modified to cancel each time it receives the target device. If the accumulation reaches a certain level, that is, if the number of dormant customers whose cancellation has been determined meets the condition, then the cancellation is determined to be completed.

[0068] In this embodiment, to facilitate the measurement of whether the number of dormant customer identification information that has been modified to a canceled status received by the electronic device meets the conditions, a preset quantity threshold can be set in the electronic device. This preset quantity threshold is the number of dormant customers that the cancellation task requires to cancel. The preset quantity threshold can be 100, 200, 500, etc., specifically set according to requirements. Each time the electronic device receives a processing instruction to cancel a dormant customer's contract for a target transaction, it determines to perform a cancellation task.

[0069] To determine whether the cancellation is complete, the electronic device can compare the number of dormant customer identification information that has been changed to a cancellation status with a preset threshold in real time to determine whether the required number of dormant customers for cancellation has been reached, and thus determine whether the cancellation is complete.

[0070] Specifically, if the number of dormant customer identification information that has been changed to a cancelled status received by the electronic device is greater than the preset threshold, it is determined that the number of dormant customers to be cancelled for this cancellation task has been reached, and therefore the cancellation is confirmed to be complete. If the number of dormant customer identification information that has been changed to a cancelled status received is not greater than the preset threshold, it is determined that the number of dormant customers to be cancelled for this cancellation task has not been reached, and therefore the cancellation is confirmed to be incomplete and waiting is required.

[0071] To increase the flexibility of contract termination, in this embodiment, the preset quantity threshold can be a pre-set and fixed value, or it can be a proportion value stored in the electronic device for determining the quantity threshold. The electronic device can determine the preset quantity threshold based on the total number of dormant customers to be terminated for the target transaction and the proportion value stored in the pre-stored data. Alternatively, the preset quantity threshold stored in the electronic device can be updated each time a contract termination task is executed, based on the target quantity threshold selected by the target user. Specifically, when the target user logs into their account using the application on the electronic device and selects the target transaction to be terminated, they can also select the number of dormant customers to be terminated, i.e., select the corresponding first target quantity threshold. At this time, the electronic device will receive a second threshold change instruction carrying the first target quantity threshold, and subsequently update the preset quantity threshold in the electronic device based on the first target quantity threshold carried in the second threshold change instruction. Then, based on the updated preset quantity threshold, it is determined whether the contract termination is completed.

[0072] In this embodiment, a cancellation request instruction can be sent to the target device based on the received processing instruction for canceling dormant customers of the target transaction. This causes the target device to modify the customer contract status corresponding to each dormant customer whose identification information to be canceled is carried in the cancellation request instruction to a cancellation status. When the number of dormant customer identification information whose status has been modified to cancellation sent by the target device exceeds a preset threshold, the cancellation is determined to be completed. This achieves automatic batch cancellation of dormant customers of the target transaction without requiring dormant customers to cancel themselves, thus improving the efficiency of cancellation and enhancing the user experience.

[0073] Example 2:

[0074] To facilitate the counting of the number of dormant customer identification information that has been modified to a cancelled status received by the electronic device, based on the above embodiments, in this embodiment of the application, before determining that the cancellation is completed if the number of received dormant customer identification information that has been modified to a cancelled status is greater than a preset threshold, the method further includes:

[0075] Determine whether the time interval since the last quantity count has reached a preset time interval. If so, count the number of the received identification information of dormant customers whose status has been changed to cancellation.

[0076] In this embodiment, to facilitate the counting of the number of dormant customer identification information messages received by the electronic device that have been changed to a cancelled status, in one possible implementation, the electronic device can count the number of such messages in real time. To reduce the workload of the electronic device, in another possible implementation, the electronic device can also count the number of such messages at preset time intervals. These preset time intervals can be 1 minute, 2 minutes, etc., and can be set according to requirements.

[0077] In this embodiment, it is preferable to count the number of dormant customer identification information that has been changed to a cancelled status at preset time intervals. Specifically, after receiving dormant customer identification information that has been changed to a cancelled status from the target device, the electronic device, in order to determine when to count the number of received dormant customer identification information that has been changed to a cancelled status, can first determine whether the time interval between the current time and the last time the count was performed reaches the preset time interval. If so, it determines that the number of received dormant customer identification information that has been changed to a cancelled status can be counted at this time. Because the electronic device counts the number of received dormant customer identification information that has been changed to a cancelled status at each time interval, the electronic device can only count the number of dormant customer identification information that has been changed to a cancelled status received within the time interval between the current time and the time interval before the last time the count was performed, and then update the number of received dormant customer identification information that has been changed to a cancelled status based on this number and the previously counted number.

[0078] Example 3:

[0079] To ensure that the contract termination operation can be stopped urgently when necessary, based on the above embodiments, in this embodiment, after sending the contract termination request instruction to the target device, the method further includes:

[0080] If a termination stop processing instruction is received, a termination application stop instruction is sent to the target device so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identified information.

[0081] In this embodiment of the application, in order to improve the flexibility of cancellation, the target user can also control in real time when to perform the cancellation operation for dormant customers and when to stop the cancellation operation for dormant customers. Specifically, the target user can log in to the target user's account based on the application on the electronic device and choose whether to stop the cancellation operation for dormant customers. If the target user chooses to stop the cancellation operation for dormant customers, the electronic device will receive the cancellation stop processing instruction.

[0082] Upon receiving a termination request, the electronic device can send a termination request stop instruction to the target device. This causes the target device to cease modifying the customer contract status corresponding to each dormant customer whose identity information is pending termination, thereby stopping further termination of dormant customers. This method can urgently stop the termination operation for dormant customers when necessary, demonstrating strong emergency handling capabilities.

[0083] Example 4:

[0084] To further improve the efficiency of contract termination, based on the above embodiments, in this embodiment of the application, before receiving the processing instruction to terminate the contract for the dormant customer of the target transaction, the method further includes:

[0085] According to the preset grouping rules, the dormant customers of the target transaction are divided into multiple groups;

[0086] Sending a termination request instruction to the target device for the dormant customers whose pre-saved target transactions are pending termination includes:

[0087] For each group of dormant customers to be terminated in the pre-saved target transaction, a termination request instruction is sent to the target device for that group of dormant customers, wherein the termination request instruction carries the identification information of each dormant customer in that group.

[0088] To further improve the efficiency of contract termination, in this embodiment of the application, the electronic device can also group the dormant customers of each target transaction, and perform multi-task concurrency for multiple groups, wherein one group corresponds to one task, and the contract termination operation is performed on each group simultaneously.

[0089] To enable concurrent multitasking, before receiving the processing instruction to cancel the contract of a dormant customer for the target transaction, that is, before canceling the contract of a dormant customer for the target transaction, the electronic device can randomly divide the dormant customers of the target transaction into multiple groups. The number of dormant customers in each group can be the same or different, and each group contains at least one dormant customer.

[0090] In this embodiment of the application, in order to ensure the uniformity of the division of dormant customers, the dormant customers of the target transaction can be divided into multiple groups according to the preset grouping rules.

[0091] In one possible implementation, sleep customers of different age groups can be divided into corresponding groups based on their age. For example, sleep customers under 20 years old can be grouped into one group, sleep customers aged 20-40 years old into another group, sleep customers aged 40-60 years old into another group, and sleep customers over 60 years old into another group, etc.

[0092] In another possible implementation, dormant customers with different contract durations for the target transaction can be grouped into corresponding groups based on the duration of their contract. For example, dormant customers with a contract duration of less than one year can be grouped into one group, dormant customers with a contract duration of one to two years can be grouped into another group, and dormant customers with a contract duration of more than two years can be grouped into another group, and so on.

[0093] The following is an illustration using a specific example:

[0094] If the target transaction is account precious metals trading, then dormant clients with different holdings can be divided into corresponding groups based on their holdings. For example, dormant clients with holdings of less than 10g can be grouped into one group, those with holdings of 10g-100g into another group, and those with holdings of more than 100g into yet another group.

[0095] In this embodiment of the application, after dividing the dormant customers of the target transaction into multiple groups according to the preset grouping rules, if the electronic device receives a processing instruction to terminate the contract for the dormant customers of the target transaction, it sends a termination application instruction for each group of dormant customers to be terminated in the target transaction to the target device. The termination application instruction carries the identification information of each dormant customer in the group to be terminated.

[0096] For each group, after receiving a cancellation request instruction from a dormant customer in that group, the target device modifies the customer's contract status to a cancellation status for each dormant customer in that group and sends the identification information of the dormant customers whose status has been changed to cancellation to the electronic device. Specifically, the target device can perform cancellation operations concurrently for each group.

[0097] Because this method can achieve multi-task synchronous processing and complete the cancellation of a large number of dormant customers in the shortest possible time, it effectively improves the efficiency of cancellation.

[0098] To determine whether the contract termination is complete, based on the above embodiments, in this embodiment, determining that the termination is complete if the number of received identifiers of dormant customers whose status has been modified to terminate is greater than a preset threshold includes:

[0099] If the number of identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold for each group, then the termination is determined to be complete.

[0100] In this embodiment of the application, after receiving the number of identification information of dormant customers whose status has been changed to cancellation for each group, the electronic device can preset a quantity threshold in order to determine whether the cancellation is completed. The preset quantity threshold is the number of dormant customers that need to be cancelled for each cancellation task corresponding to each group. The preset quantity threshold can be 100, 200, 500, etc. Specifically, the preset quantity threshold is set according to the needs.

[0101] To determine whether the cancellation is complete, the electronic device can compare the number of dormant customer identification information groups that have been modified to cancel status with a preset threshold in real time to determine whether the required number of dormant customers for cancellation has been reached, and thus determine whether the cancellation is complete.

[0102] Specifically, if the number of dormant customer identification information groups that have been modified to cancel their contracts received by the electronic device is greater than the corresponding preset threshold, then it is determined that the required number of dormant customers to be canceled for each cancellation task has been reached, and the cancellation is considered complete. If the number of dormant customer identification information groups that have been modified to cancel their contracts received is not greater than the preset threshold, then it means that some groups have not yet reached the required number of dormant customers to be canceled for this cancellation task, and therefore it is necessary to wait.

[0103] To increase the flexibility of contract termination, in this embodiment of the application, the preset quantity threshold for each group can also be different. When the electronic device determines whether the contract termination is completed, it can compare the number of sleep customers whose status has been changed to termination in real time with the preset quantity threshold corresponding to the group for each group. Based on the comparison results of each group, it can determine whether the number of sleep customers who need to be terminated has been reached, and then determine whether the contract termination is completed.

[0104] To further increase the flexibility of contract termination, in this embodiment, the preset quantity threshold for each group can be a pre-set and fixed value, or it can be a proportion value stored in the electronic device for determining the quantity threshold for that group. The electronic device can determine the preset quantity threshold for that group based on the pre-stored total number of dormant customers to be terminated for the target transaction in that group and the corresponding proportion value. The proportion values ​​for determining the quantity threshold for different groups can be the same or different. Alternatively, each time a contract termination task is executed, the preset quantity threshold stored in the electronic device is updated based on the second target quantity threshold selected by the target user for each group. Specifically, when the target user logs into their account through the application on the electronic device and selects the target transaction to be terminated, they can also select the number of dormant customers to be terminated in that group, i.e., select the second target quantity threshold for that group. At this time, the electronic device will receive a first threshold change instruction carrying the second target quantity threshold, and subsequently update the preset quantity threshold for that group in the electronic device based on the second target quantity threshold carried in the first threshold change instruction. Then, based on the updated preset quantity threshold for each group, it is determined whether the contract termination is completed.

[0105] Figure 2 This application provides a schematic diagram illustrating the task status update process of a task status table in a database during the cancellation process, based on some embodiments of the present application. Figure 2 Please provide an explanation.

[0106] To facilitate real-time statistics on task status in electronic devices, a task execution status table is pre-stored in the database within the electronic device.

[0107] If an electronic device receives a processing instruction to cancel a dormant customer's contract for a target transaction, it first obtains the task execution status table pre-stored in the database. Then, it updates the value corresponding to the task status code in the task execution status table for each group of this task to the value corresponding to "in execution". Specifically, various values ​​can be pre-set for various types of task status codes, such as 0 for "in execution", 1 for "execution completed", 2 for "manual termination", etc. There are no specific restrictions.

[0108] For each group of dormant customers awaiting cancellation in a pre-saved target transaction, the electronic device sends a cancellation request instruction to the target device, causing the target device to change the customer's contract status to a cancellation status for each identified dormant customer. If the electronic device does not receive a cancellation stop instruction during this period, and it is determined that the number of identified customers whose status has been changed to cancellation for each group is greater than a preset threshold, then the cancellation is considered complete, and the value corresponding to the task status code in the task execution status table for this task is updated to the value corresponding to "execution completed".

[0109] If the electronic device receives a termination stop instruction during the process, it sends a termination request stop instruction to the target device, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each identification information, and updates the value of the task status code corresponding to each group of tasks in the task execution status table to the value corresponding to "manual termination".

[0110] Table 1 shows the pre-saved task execution status table in the electronic device. The following is a detailed explanation of the task execution table:

[0111]

[0112] Table 1

[0113] In addition to recording the numerical values ​​corresponding to the task status codes, the task execution status table also records multiple fields such as scheduling execution sequence number, job number, task start date and time, task end date and time, number of successful tasks, number of failed tasks, total number of records, sleep customer grouping rules, and remarks. It also records the attributes and field lengths of these multiple fields. For example, the attribute corresponding to the job number field is VARCHAR2, and the field length is 12.

[0114] Figure 3 This application provides a schematic diagram of a process for determining whether a contract termination was successful, based on some embodiments. Figure 3 Please provide an explanation.

[0115] The electronic device receives a processing instruction to terminate the contracts of dormant customers for the target transaction. For each group of dormant customers to be terminated in the pre-saved target transaction, it sends a termination application instruction to the target device, so that the target device changes the customer contract status corresponding to each dormant customer with identification information to the termination status. The termination application instruction carries the identification information of each dormant customer in the group to be terminated. The electronic device updates the value of the task status code corresponding to each group in the task execution status table of this task to the value corresponding to "in execution".

[0116] If the electronic device receives a termination stop processing instruction, it sends a termination application stop instruction to the target device, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each identification information. The electronic device updates the value of the task status code corresponding to each group of tasks in this task execution status table to the value corresponding to "manual termination".

[0117] If the electronic device does not receive a termination instruction during the process, the target device continues to change the contract status of the dormant customer corresponding to each identifier in each group to a termination status. The electronic device receives the identifier information of each group of dormant customers whose contract status has been changed to termination from the target device. If the number of dormant customer identifier information groups whose contract status has been changed to termination received is greater than a preset threshold, the termination is determined to be complete, and the value of the task status code in the task execution status table corresponding to each group of this task is updated to the value corresponding to "execution completed".

[0118] Example 5:

[0119] In this embodiment of the application, task execution may also encounter problems. In order to facilitate subsequent query of task execution anomalies and enable business and maintenance personnel to understand the task processing progress in real time, the electronic device also pre-stores a task execution anomaly table, which records the record number, scheduling execution number, etc., corresponding to the task anomaly.

[0120] The process by which electronic devices determine whether task execution is abnormal is existing technology and will not be elaborated here.

[0121] Table 2 shows a pre-saved table of task execution exceptions in electronic devices. The following is a detailed explanation of the task execution exception table:

[0122]

[0123]

[0124] Table 2

[0125] The task execution exception table records multiple fields such as record number, scheduling execution number, job number, customer number (identification information corresponding to the customer), account opening institution number, processing serial number, and remarks. It also records the attributes and field lengths of these fields. For example, the scheduling execution number field has the attribute VARCHAR2 and a field length of 15.

[0126] In addition, the electronic device also pre-stores information on sleeping customers, as shown in Table 3. The following is a detailed explanation of the sleeping customer information table:

[0127]

[0128] Table 3

[0129] The dormant customer information table records multiple fields such as the contract agreement number and the account opening institution number, as well as the corresponding attributes and field lengths of these fields. For example, the contract agreement number field has the attribute VARCHAR2 and a field length of 32.

[0130] Example 6:

[0131] Figure 4 A schematic diagram of a contract termination process is provided for some embodiments of this application. The process includes the following steps:

[0132] S401: In response to the target transaction to be terminated selected by the target user, for the dormant customers to be terminated in the pre-saved target transaction, change the customer contract status corresponding to each dormant customer with identification information to the termination status; obtain the identification information of the dormant customers whose termination status has been changed.

[0133] S402: If the number of the obtained identification information of the dormant customers whose status has been modified to terminate is greater than the preset number threshold, then the termination is determined to be completed.

[0134] The cancellation method provided in this embodiment of the invention can be used to execute the cancellation method provided in any of the above embodiments, and has the corresponding functions and beneficial effects.

[0135] Example 7:

[0136] Figure 5 A schematic diagram of a release device provided in some embodiments of this application is shown. The device includes:

[0137] The receiving module 501 is used to receive processing instructions for canceling contracts with dormant customers of the target transaction;

[0138] The first processing module 502 is used to send a termination application instruction to the target device for the dormant customers to be terminated in the pre-saved target transaction, so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status, wherein the termination application instruction carries the identification information of each dormant customer to be terminated; and to receive the identification information of the dormant customers whose termination status has been changed by the target device.

[0139] The first determining module 503 is used to determine that the cancellation is completed if the number of received identification information of dormant customers whose status has been modified to be cancelled is greater than a preset number threshold.

[0140] In one possible implementation, the device further includes:

[0141] The judgment module 504 is used to determine whether the time interval since the last quantity statistics has reached a preset time interval. If so, it counts the number of the received identification information of the dormant customers whose status has been changed to cancellation.

[0142] In one possible implementation, the first processing module 502 is further configured to send a termination application stop instruction to the target device if a termination stop instruction is received, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identification information.

[0143] In one possible implementation, the device further includes:

[0144] Grouping module 505 is used to divide the dormant customers of the target transaction into multiple groups according to preset grouping rules;

[0145] The first processing module 502 is specifically used to send a cancellation application instruction to the target device for each group of dormant customers to be cancelled in the pre-saved target transaction, wherein the cancellation application instruction carries the identification information of each dormant customer in the group to be cancelled.

[0146] In one possible implementation, the first determining module 503 is specifically configured to determine that the cancellation is complete if the number of identification information of the dormant customers whose status has been modified to be cancelled for each group is greater than a preset number threshold.

[0147] Example 8:

[0148] Figure 6 A schematic diagram of a release device provided in some embodiments of this application is shown. The device includes:

[0149] The second processing module 601 is used to respond to the target transaction to be terminated selected by the target user, and for the dormant customers to be terminated in the pre-saved target transaction, modify the customer contract status corresponding to each dormant customer with identification information to the termination status; and obtain the identification information of the dormant customers whose termination status has been modified.

[0150] The second determining module 602 is used to determine that the cancellation is completed if the number of the obtained identification information of the dormant customers whose status has been modified to be cancelled is greater than a preset number threshold.

[0151] Example 9:

[0152] Based on the above embodiments, some embodiments of this application also provide an electronic device, such as... Figure 7As shown, it includes: processor 701, communication interface 702, memory 703 and communication bus 704, wherein processor 701, communication interface 702 and memory 703 communicate with each other through communication bus 704.

[0153] The memory 703 stores a computer program, which, when executed by the processor 601, causes the processor 701 to perform the following steps:

[0154] Receive processing instructions to terminate contracts with dormant customers for the target transaction;

[0155] For the dormant customers of the target transaction that are to be terminated and are stored in advance, a termination application instruction is sent to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; the target device sends the identification information of the dormant customers whose contract status has been changed to termination status.

[0156] If the number of received identification information of dormant customers whose status has been modified to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0157] Furthermore, the processor 701 is also used to determine whether the time interval between the last time the quantity statistics were performed has reached a preset time interval, and if so, to count the number of the received identification information of the dormant customers whose status has been changed to cancellation.

[0158] Furthermore, the processor 701 is also configured to send a termination application stop instruction to the target device if a termination stop instruction is received, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identification information.

[0159] Furthermore, the processor 701 is also configured to divide the dormant customers of the target transaction into multiple groups according to a preset grouping rule; and to send a termination application instruction to the target device for each group of dormant customers to be terminated in the target transaction, wherein the termination application instruction carries the identification information of each dormant customer to be terminated in the group.

[0160] Furthermore, the processor 701 is also configured to determine that the cancellation is completed if the number of identification information of the dormant customers whose status has been modified to be cancelled for each group is greater than a preset number threshold.

[0161] The communication bus mentioned in the above server can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0162] The communication interface 702 is used for communication between the above-mentioned electronic device and other devices.

[0163] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0164] The processors mentioned above can be general-purpose processors, including central processing units, network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0165] Example 10:

[0166] Based on the above embodiments, some embodiments of this application also provide an electronic device, such as... Figure 8 As shown, it includes: processor 801, communication interface 802, memory 803 and communication bus 804, wherein processor 801, communication interface 802 and memory 803 communicate with each other through communication bus 804.

[0167] The memory 803 stores a computer program, which, when executed by the processor 801, causes the processor 801 to perform the following steps:

[0168] In response to the target transaction to be terminated selected by the target user, for the dormant customers to be terminated in the pre-saved target transaction, the customer contract status corresponding to each dormant customer with identification information is modified to termination status; the identification information of the dormant customers whose termination status has been modified is obtained;

[0169] If the number of identified dormant customers whose status has been changed to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0170] The communication bus mentioned in the above server can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0171] Communication interface 802 is used for communication between the above-mentioned electronic device and other devices.

[0172] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0173] The processors mentioned above can be general-purpose processors, including central processing units, network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0174] Example 11:

[0175] Based on the above embodiments, some embodiments of this application also provide a computer-readable storage medium storing a computer program executable by an electronic device. When the program is run on the electronic device, the electronic device performs the following steps:

[0176] The memory stores a computer program that, when executed by the processor, causes the processor to perform the following steps:

[0177] Receive processing instructions to terminate contracts with dormant customers for the target transaction;

[0178] For the dormant customers of the target transaction that are to be terminated and are stored in advance, a termination application instruction is sent to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; the target device sends the identification information of the dormant customers whose contract status has been changed to termination status.

[0179] If the number of received identification information of dormant customers whose status has been modified to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0180] Furthermore, before determining that the cancellation is complete if the number of received identifiers of dormant customers whose status has been modified to cancel exceeds a preset threshold, the method further includes:

[0181] Determine whether the time interval since the last quantity count has reached a preset time interval. If so, count the number of the received identification information of dormant customers whose status has been changed to cancellation.

[0182] Furthermore, after sending the termination request instruction to the target device, the method further includes:

[0183] If a termination stop processing instruction is received, a termination application stop instruction is sent to the target device so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identified information.

[0184] Furthermore, before receiving the processing instruction to terminate the contract for the dormant customer of the target transaction, the method further includes:

[0185] According to the preset grouping rules, the dormant customers of the target transaction are divided into multiple groups;

[0186] Sending a termination request instruction to the target device for the dormant customers whose pre-saved target transactions are pending termination includes:

[0187] For each group of dormant customers to be terminated in the pre-saved target transaction, a termination request instruction is sent to the target device for that group of dormant customers, wherein the termination request instruction carries the identification information of each dormant customer in that group.

[0188] Further, determining that the cancellation is complete if the number of received identifiers of dormant customers whose status has been modified to cancel is greater than a preset threshold includes:

[0189] If the number of identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold for each group, then the termination is determined to be complete.

[0190] Example 12:

[0191] Based on the above embodiments, some embodiments of this application also provide a computer-readable storage medium storing a computer program executable by an electronic device. When the program is run on the electronic device, the electronic device performs the following steps:

[0192] The memory stores a computer program that, when executed by the processor, causes the processor to perform the following steps:

[0193] In response to the target transaction to be terminated selected by the target user, for the dormant customers to be terminated in the pre-saved target transaction, the customer contract status corresponding to each dormant customer with identification information is modified to termination status; the identification information of the dormant customers whose termination status has been modified is obtained;

[0194] If the number of identified dormant customers whose status has been changed to terminated exceeds a preset threshold, then the termination is determined to be complete.

[0195] Example 13:

[0196] This application also provides a computer program product that, when executed by a computer, implements the unfreezing method described in any of the method embodiments applied to electronic devices.

[0197] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof, or in whole or in part, as a computer program product. The computer program product includes one or more computer instructions, which, when loaded and executed on a computer, generate, in whole or in part, the processes or functions described in the embodiments of this application.

[0198] Example 14:

[0199] This application also provides a computer program product that, when executed by a computer, implements the unfreezing method described in any of the method embodiments applied to electronic devices.

[0200] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof, or in whole or in part, as a computer program product. The computer program product includes one or more computer instructions, which, when loaded and executed on a computer, generate, in whole or in part, the processes or functions described in the embodiments of this application.

[0201] In this embodiment, a cancellation request instruction can be sent to the target device based on the received processing instruction for canceling dormant customers of the target transaction. This causes the target device to modify the customer contract status corresponding to each dormant customer whose identification information to be canceled is carried in the cancellation request instruction to a cancellation status. When the number of dormant customer identification information whose status has been modified to cancellation sent by the target device exceeds a preset threshold, the cancellation is determined to be completed. This achieves automatic batch cancellation of dormant customers of the target transaction without requiring dormant customers to cancel themselves, thus improving the efficiency of cancellation and enhancing the user experience.

[0202] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0203] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0204] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

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

[0206] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for canceling a contract, characterized in that, The method includes: Receive processing instructions to terminate contracts with dormant customers for the target transaction; For the dormant customers of the target transaction that are to be terminated and are stored in advance, a termination application instruction is sent to the target device so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; the target device sends the identification information of the dormant customers whose contract status has been changed to termination status. If the number of received identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold, then the termination is determined to be complete. Before receiving the processing instruction to terminate the contract for the dormant customer of the target transaction, the method further includes: According to the preset grouping rules, the dormant customers of the target transaction are divided into multiple groups, so that multiple tasks can be performed concurrently for multiple groups. Each group corresponds to one task, and the cancellation operation is performed simultaneously for each group. Sending a termination request instruction to the target device for the dormant customers whose pre-saved target transactions are pending termination includes: For each group of dormant customers to be terminated in the pre-saved target transaction, a termination request instruction is sent to the target device for that group of dormant customers, wherein the termination request instruction carries the identification information of each dormant customer in that group.

2. The method according to claim 1, characterized in that, If the number of received identifiers of dormant customers whose status has been modified to terminated exceeds a preset threshold, the method further includes the following steps before determining that the termination is complete: Determine whether the time interval since the last quantity count has reached a preset time interval. If so, count the number of the received identification information of dormant customers whose status has been changed to cancellation.

3. The method according to claim 1, characterized in that, After sending the termination request instruction to the target device, the method further includes: If a termination stop processing instruction is received, a termination application stop instruction is sent to the target device so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identified information.

4. The method according to claim 1, characterized in that, The step of determining that the cancellation is complete if the number of received identifiers of dormant customers whose status has been modified to cancel is greater than a preset threshold includes: If the number of identification information of dormant customers whose status has been modified to terminated is greater than a preset threshold for each group, then the termination is determined to be complete.

5. A method for canceling a contract, characterized in that, The method includes: In response to the target transaction to be terminated selected by the target user, for the dormant customers to be terminated in the pre-saved target transaction, the customer contract status corresponding to each dormant customer with identification information is modified to termination status; the identification information of the dormant customers whose termination status has been modified is obtained; If the number of dormant customers whose status has been modified to terminated is greater than a preset threshold, then the termination is determined to be complete. Prior to responding to the target transaction to be cancelled selected by the target user, the method further includes: According to the preset grouping rules, the dormant customers of the target transaction are divided into multiple groups, so that multiple tasks can be performed concurrently for multiple groups. Each group corresponds to one task, and the cancellation operation is performed simultaneously for each group. The step of modifying the contract status of each dormant customer with identification information to a termination status for the pre-saved dormant customers of the target transaction includes: For each group of dormant customers awaiting termination of the target transaction that has been pre-saved, the customer contract status corresponding to each dormant customer in that group is changed to termination status.

6. A release device, characterized in that, The device includes: The receiving module is used to receive processing instructions for canceling contracts with dormant customers of the target transaction; The first processing module is used to send a termination application instruction to the target device for the dormant customers of the target transaction that are to be terminated in a pre-saved list, so that the target device changes the customer contract status corresponding to each dormant customer with identification information to a termination status. The termination application instruction carries the identification information of each dormant customer to be terminated; and receives the identification information of the dormant customers whose termination status has been changed by the target device. The first determining module is used to determine that the cancellation is completed if the number of received identification information of dormant customers whose status has been modified to be cancelled is greater than a preset number threshold. The device further includes: The grouping module is used to divide the dormant customers of the target transaction into multiple groups according to preset grouping rules, so that multiple tasks can be performed concurrently for multiple groups, wherein one group corresponds to one task, and the cancellation operation is performed simultaneously for each group. The first processing module is specifically used to send a cancellation request instruction to the target device for each group of dormant customers to be cancelled in the pre-saved target transaction, wherein the cancellation request instruction carries the identification information of each dormant customer in the group to be cancelled.

7. The apparatus according to claim 6, characterized in that, The device further includes: The judgment module is used to determine whether the time interval since the last quantity statistics has reached a preset time interval. If so, it counts the number of the received identification information of the dormant customers whose status has been changed to cancellation.

8. The apparatus according to claim 6, characterized in that, The first processing module is further configured to send a termination application stop instruction to the target device if a termination stop instruction is received, so that the target device stops modifying the customer contract status corresponding to the dormant customer to be terminated for each of the identification information.

9. The apparatus according to claim 8, characterized in that, The first determining module is specifically used to determine that the cancellation is completed if the number of identification information of the dormant customers whose status has been modified to cancel is greater than a preset number threshold for each group.

10. A release device, characterized in that, The device includes: The second processing module is used to respond to the target transaction to be terminated selected by the target user, and for the dormant customers to be terminated in the pre-saved target transaction, modify the customer contract status corresponding to each dormant customer with identification information to the termination status; and obtain the identification information of the dormant customers whose termination status has been modified. The second determining module is used to determine that the cancellation is completed if the number of the obtained identification information of the dormant customers whose status has been modified to be cancelled is greater than a preset number threshold. The device further includes: The grouping module is used to divide the dormant customers of the target transaction into multiple groups according to preset grouping rules, so that multiple tasks can be performed concurrently for multiple groups, wherein one group corresponds to one task, and the cancellation operation is performed simultaneously for each group. The second processing module is specifically used to modify the customer contract status of each dormant customer in each group of dormant customers to be terminated in the pre-saved target transaction to a termination status.

11. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory being used to store program instructions, and the processor being used to execute the computer program stored in the memory to implement the steps of the unfreezing method as described in any of claims 1-4 or the unfreezing method as described in claim 5.

12. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the steps of the unrestriction method as described in any one of claims 1-4 or the unrestriction method as described in claim 5.

13. A computer program product, characterized in that, Its computer program product includes: computer program code, which, when the computer program code is run on a computer, causes the computer to perform the steps of the unfreezing method as described in any one of claims 1-4 or the unfreezing method as described in claim 5.

Images