Bank account hotspot identification upgrading serial processing method and device based on optimistic lock

Abstract

The invention provides a bank account hotspot identification upgrading serial processing method and device based on an optimistic lock, and relates to the field of financial science and technology, and the method comprises the steps: receiving an external bookkeeping request, and judging the hotspot state of an account corresponding to the bookkeeping request through a hotspot route; when the account is in a non-hotspot state, starting a hotspot serial identification process for the account; establishing a time window for account hotspot identification, and identifying whether the current accounting request falls into the time window; if the number falls into the time window, an optimistic lock mechanism is adopted to carry out cyclic self-increasing operation on the identification count; whether the counting result reaches a preset threshold value or not is judged, if the counting result reaches the preset threshold value, hotspot upgrading is triggered, the account is pre-marked as a hotspot account, and the account state is in hotspot upgrading; and after carrying out common account balance processing on the bookkeeping request, formally marking the account as a hotspot state. According to the invention, the real-time dynamic identification of the account hotspots is realized, the real-time hotspot upgrading of the accounts is realized, the processing stability of multiple concurrent accounts is improved, and the normal response of services is ensured.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and in particular to a method and apparatus for upgrading serial processing of bank account hotspot identification based on optimistic locking. Background Technology

[0002] With the development of internet finance businesses, centralized single-account direct debit and payment services initiated by channels such as UnionPay, NetsUnion, and SuperNet are becoming increasingly frequent. For example, if an online merchant opens a settlement account at a bank, multiple individual customers may simultaneously transfer funds into this settlement account, leading to account hotspots. Traditional financial account services require control over account balances and limits during the settlement account accounting process. High-frequency operations on the same account can trigger account locking issues due to account hotspots, thus giving rise to various solutions for handling hotspot accounts.

[0003] Hotspot account solutions generally require marking accounts as hotspots first, and then guiding the system to a different logical branch than ordinary accounting based on the hotspot markings, thereby avoiding the problems caused by hotspot accounts. For the hotspot marking in this process, the existing technical solutions are basically asynchronous, and there are usually two hotspot identification methods: (1) Before the hotspot, provide an independent hotspot account marking API service. The channel end (counter, online banking, etc.) packages the account opening or signing business, and the customer completes the account hotspot marking operation through the channel end through active business processing, thereby marking the account as a hotspot. (2) After the hotspot, provide post-analysis and prediction marking. Based on the analysis of a large amount of account business data, it is determined whether the account has been hotspot or may be hotspot at a certain time, thereby forming a list of hotspot accounts. After the business operation personnel confirm, the accounts in the system are marked as hotspots.

[0004] Existing methods for automatically identifying hotspots in bank accounts have the following problems: asynchronous hotspot identification, based on pre-signing or post-analysis, cannot cope with sudden hotspots and lacks real-time performance; for ordinary accounts that are not marked as hotspots, when they suddenly become hotspots, there may be a large number of processing failures, resulting in a poor user experience; for ordinary accounts that are not marked as hotspots, when they suddenly become hotspots, it may cause system paralysis, which is highly risky.

[0005] Based on the above problems, there is an urgent need for a method for real-time upgrading of bank account hotspot identification. When an ordinary account suddenly becomes a hotspot, the hotspot upgrade of the account can be implemented immediately to avoid the risk of a large number of failed responses or system paralysis. Summary of the Invention

[0006] To address the problems in the background technology, this invention provides a method and apparatus for serial processing of bank account hotspot identification and upgrade based on optimistic locking. By using a cyclic optimistic locking counting method, hotspot marking and identification are performed before ordinary account table locking processing. This can effectively prevent lock contention caused by pessimistic locking of ordinary accounts, while providing high-performance processing and identification capabilities to complete dynamic hotspot marking and identification processing. This guides the accounting processing of ordinary accounts to switch to hotspot account processing. For instantaneous high-concurrency account accounting, the version control provided by optimistic locking realizes serial counting control, providing security control and hotspot upgrade processing.

[0007] To achieve the above objectives, the present invention provides a method for upgrading serial processing of bank account hotspot identification based on optimistic locking, comprising: receiving an external accounting request and determining the hotspot status of the account corresponding to the accounting request through hotspot routing; When an account is not in a hotspot state, the hotspot serial identification process for the account is initiated. Establish a time window for account hotspot identification, and identify whether the current accounting request falls within the time window; If the time window is exceeded, an optimistic locking mechanism is used to continuously increment the recognition count. Determine whether the counting result has reached a preset threshold. If it has reached the preset threshold, trigger hotspot upgrade. First, pre-mark the account as a hotspot account, and the account status is hotspot upgrade in progress. After processing the accounting request using the normal account balance, the account is then officially marked as a hotspot.

[0008] As a further improvement of the present invention, when the account is undergoing a hotspot upgrade, the accounting request is routed to the service failure process.

[0009] As a further improvement of the present invention, the step of initiating a hotspot serial identification process when the account is in a non-hotspot state includes: The system checks the account status indicator; if the account is undergoing a hotspot upgrade, it returns a failure message. Query the validity of the account time window and match the time window according to the business time of the accounting request; The counting operation is performed using an optimistic locking mechanism, which includes version number verification and retry mechanisms.

[0010] As a further improvement of the present invention, the step of establishing a time window for account hotspot identification, and identifying whether the current accounting request falls within the time window, includes: When the first accounting request is triggered, the start time of the accounting request is recorded as the start time of the time window, and the start time plus a preset duration is used as the time window. For subsequent account operations, determine whether they fall within the aforementioned time window: If it falls within the time window, it participates in the hotspot counting of that time window; If the time window falls outside the specified time window, a new time window will be created. The account operation that triggers the creation of a time window will directly enter the normal account processing flow after the time window is created.

[0011] As a further improvement of the present invention, if the current accounting request does not fall within the time window, the accounting request will enter the ordinary account balance processing flow.

[0012] As a further improvement of the present invention, the method of using an optimistic locking mechanism to perform a cyclic increment operation on the identification count includes: Query the current counter value and version number; Update the counter value and version number using the query results as the update condition; If the update is successful, determine whether the counting result has reached the preset threshold; If the update fails, it will be retried repeatedly until the maximum number of retries is reached, at which point the accounting request will be responded to directly.

[0013] As a further improvement of the present invention, if the counting result does not reach the preset threshold, the accounting request will enter the ordinary account balance processing flow.

[0014] As a further improvement of the present invention, the step of marking the account as a hotspot after completing the current business process includes: Set the account's "Hotspot Upgrade in Progress" status in the current thread; Complete the original business logic processing; Persistentize account state and mark it as a hotspot.

[0015] The present invention also provides a bank account hotspot identification and upgrade serial processing device based on optimistic locking, including a hotspot routing module, a hotspot serial identification module, a hotspot window control module, a hotspot counting module based on optimistic locking, a hotspot counting control module, and a hotspot upgrade module; The hotspot routing module is used for: Receive external accounting requests and determine if the account has been marked as a hotspot; The hotspot serial identification module is used for: When an account is not marked as a hotspot, a circular optimistic locking counting mechanism is used to identify hotspots, and the account status is serially controlled during the identification process; when an account is detected to be in a hotspot upgrade state, the accounting request is routed to the service failure process. The hotspot window control module is used for: Set a time window for account hotspot identification, and identify whether the accounting request falls within the current time window based on the time of occurrence of the accounting request; The hotspot counting module based on optimistic locking is used for: An optimistic locking mechanism is used for identification counting and self-looping updates, including a version number verification mechanism; The hotspot counting control module is used for: Determine whether the count result exceeds a preset threshold to decide whether to trigger a hotspot upgrade; The hotspot upgrade module is used for: After confirming that a hotspot upgrade has been triggered, the account is marked as being in the hotspot upgrade state, and the account attribute is officially upgraded to hotspot status after the current accounting request is processed.

[0016] As a further improvement of the present invention, the hotspot upgrade module includes: The status flag unit sets a status flag for the account during the hotspot upgrade after confirming that the hotspot upgrade has been triggered. The asynchronous processing unit maintains the original accounting request processing flow of the account unchanged. The final marking unit marks the account status as a hotspot status after the accounting request is processed.

[0017] Compared with the prior art, the beneficial effects of the present invention are as follows: Compared with the existing technology that predicts or identifies hot accounts, this invention provides the ability to dynamically identify hot accounts, which can flexibly deal with any unmarked hot account suddenly becoming a hot account in an instant, ensuring normal system processing and normal business response.

[0018] Compared to rate limiting and pessimistic locking identification approaches, this invention does not introduce rate limiting technology, thus not increasing the overall complexity of the system.

[0019] The introduction of optimistic locking in this invention avoids lock waiting problems caused by multi-threaded exclusive lock contention through loop counting and version number control. To a certain extent, it solves the business timeout problem of accounts before being upgraded to hotspots under high concurrency, and can quickly respond to and handle failures to avoid the risk of system downtime.

[0020] This invention has a very low degree of intrusion into the existing processes of "normal account balance processing" and "hot account balance processing". Compared with parallel identification devices based on optimistic locking and identification devices based on flow control and optimistic locking, this device integrates into existing account systems more quickly and indirectly, without requiring modification to the existing balance processing flow.

[0021] This invention addresses the issue of high-concurrency accounting requests by using version control provided by optimistic locking to achieve serial counting control. This ensures high performance while constraining the hotspot upgrade process, reducing the complexity of processing different threads at different stages before, during, and after hotspot identification.

[0022] This invention focuses on the goal of dynamic hotspot identification and tagging. It takes into account both hotspot account accounting and ordinary account accounting to ensure the availability and reliability of the system during the switch from ordinary accounts to hotspot accounts. This is mainly reflected in accurate and rapid identification, no performance degradation, no overdraft risk, and no system crash risk. Attached Figure Description

[0023] Figure 1 This is a flowchart of a method for upgrading and serial processing of bank account hotspot identification based on optimistic locking, as disclosed in one embodiment of the present invention. Detailed Implementation

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

[0025] The present invention will now be described in further detail with reference to the accompanying drawings: like Figure 1 As shown, the present invention provides a method for upgrading and serial processing of bank account hotspot identification based on optimistic locking, comprising: S1. Receive external accounting requests and determine the hotspot status of the account corresponding to the accounting request through hotspot routing; When an account is undergoing a hotspot upgrade, the accounting request is routed to the service failure process. Specifically, an external third-party system proactively initiates a transaction recording request to the bank's account system. Before processing the transaction, the system needs to determine whether the current account is already a "hotspot." S2. When the account is not in a hotspot state, start the hotspot serial identification process for the account; This includes: Check the account status indicator; if it is in the process of hotspot upgrade, return failure directly. To check the validity of the account's time window, the time window is matched based on the business time of the accounting request. The counting operation is performed using an optimistic locking mechanism, which includes version number verification and retry mechanisms.

[0026] Specifically, to reduce the risk of overdraft caused by the parallel processing of account balance updates in different states before, during and after hotspot identification, namely "normal account balance processing" (real-time balance processing) and "hotspot account balance processing" (asynchronous processing), it is necessary to use "identification status" to process the identification process serially. If "hotspot is being upgraded", then route to the "service processing failed" process for the router.

[0027] Avoid the overdraw risk caused by a certain thread having reached the recognition threshold (but the transaction is not completed) and other threads selecting "normal" or "hotspot" in the process. Therefore, in this process, all other threads are subject to failure handling.

[0028] If "not a hotspot", then route to the hotspot window for inspection; S3. Establish a time window for account hotspot recognition and identify whether the current accounting request falls within the time window; Among them, it includes: When the first accounting request is triggered, record the start time of the accounting request as the start time of the time window, and use the start time plus a preset duration as the time window; For subsequent account operations, determine whether they fall within the time window: If it falls within the time window, participate in the hotspot counting of this time window; If it falls outside the time window, re-establish the time window; For the account operation that triggers the establishment of the time window, directly enter the ordinary account processing process after establishing the time window.

[0029] Specifically, the recognition process needs to strictly control the window period. For example, if a certain account has more than y concurrent transactions within x time units, this account needs to be regarded as a hotspot. However, the opening and closing periods of the x time units are uncertain. Record the start time of the first accounting request business trigger as m, and use the time slice of m + x as the time window. Therefore, there are the following three situations: (1) If the time window is empty, it means that this is the first accounting request trigger business. Register the time window as m~m + x. Since this is the first business, there is no need to participate in the recognition process and it can directly enter the ordinary account processing process.

[0030] (2) If the time window is not empty and the time of this business < m + x, it means that this business falls within the time window of the previous business, then enter S4 for judgment and counting (3) If the time window is not empty, but the time of this business > m + x, it means that this business falls outside the time window of the previous business and needs to re-record the time window. Then this business can directly enter the ordinary account processing and there is no need to participate in the recognition process.

[0031] S4. If it falls within the time window, use the optimistic lock mechanism to perform a cyclic increment operation on the recognition count; Among them, if the current accounting request does not fall within the time window, the accounting request enters the ordinary account balance processing process.

[0032] An optimistic locking mechanism is used to perform a cyclical increment operation on the recognition count; including: Query the current counter value and version number; Update the counter value and version number using the query results as the update condition; If the update result is 1, the update is considered successful, and then proceed to S5 to determine whether the count result has reached the preset threshold. If the update result is 0, the update is considered to have failed, and the loop will be entered to try querying and updating again. If the number of iterations exceeds the set limit, the business logic will directly respond to the accounting request and enter the normal account processing flow to avoid timeout.

[0033] S5. Determine whether the counting result has reached the preset threshold. If it has reached the preset threshold, trigger the hotspot upgrade. First, pre-mark the account as a hotspot account, and the account status is hotspot upgrade in progress. If the counting result does not reach the preset threshold, the accounting request will enter the ordinary account balance processing process.

[0034] Specifically, hotspot counting control determines whether the count exceeds the hotspot threshold. If it does not exceed the hotspot threshold, the process proceeds to the normal account balance processing flow; if it exceeds the hotspot threshold, the process proceeds to the S6 hotspot upgrade processing flow.

[0035] S6. After processing the accounting request using the ordinary account balance, officially mark the account as a hotspot.

[0036] This includes marking accounts as hotspots after completing the current business process; including: Set the account's hotspot upgrade status in the current thread; Complete the business logic processing of the current accounting request according to the real-time business processing flow; After completing the current task, persistently mark the account status as a hot account.

[0037] The present invention also provides a bank account hotspot identification and upgrade serial processing device based on optimistic locking, including a hotspot routing module, a hotspot serial identification module, a hotspot window control module, a hotspot counting module based on optimistic locking, a hotspot counting control module, and a hotspot upgrade module; Hotspot routing module, used for: Receive external accounting requests and determine if the account has been marked as a hotspot; Hotspot serial identification module, used for: When an account is not marked as a hotspot, a circular optimistic locking counting mechanism is used to identify hotspots, and the account status is controlled serially during the identification process; when an account is detected to be in a hotspot upgrade state, the accounting request is routed to the service failure process. The hotspot window control module is used for: Set a time window for account hotspot identification, and identify whether a posting request falls within the current time window based on the time it occurs. A hotspot counting module based on optimistic locking is used for: An optimistic locking mechanism is used for identification counting and self-looping updates, including a version number verification mechanism; Hotspot counting control module, used for: Determine whether the count result exceeds a preset threshold to decide whether to trigger a hotspot upgrade; The hotspot upgrade module is used for: After confirming the hotspot upgrade is triggered, the account is marked as being in a hotspot upgrade state, and the account attribute is officially upgraded to hotspot status after the current accounting request is processed. The hotspot upgrade module includes: a status marking unit, which sets a hotspot upgrade status flag for the account after confirming the hotspot upgrade is triggered; an asynchronous processing unit, which keeps the original accounting request processing flow of the account unchanged; and a final marking unit, which marks the account status as hotspot status after the accounting request is processed.

[0038] Example 1: The normal accounting process for a regular account includes: Step 1: Hotspot routing determination. When an external system initiates a transfer request to account A (such as Alipay topping up account A), the system queries the status identifier of account A and finds that it is not marked as a hotspot.

[0039] Step 2: Hotspot serial identification. Check if the account status is "hotspot upgrade in progress". If so, return "service processing failed" directly to avoid concurrent upgrade conflicts. If not, enter the time window for inspection.

[0040] Step 3: Hotspot window control. The first accounting request triggers the initialization of the time window, and records the window start time window_start_time=current_time. The preset window validity period is 5 seconds (x=5). Subsequent accounting requests check whether the timestamp is within the window. If the current time current_time < window_start_time+5s, continue counting; if it exceeds the window, reset the window and start counting again.

[0041] Step 4: Optimistic locking counting. Query the current count value count=0 and version number version=1, perform the counting operation, update the condition: version=1→ count=1, version=2, update is successful (returns 1), which is considered a successful count, and enter the counting control.

[0042] Step 5: Hotspot counting control. Determine if the count=1 exceeds the threshold (e.g., 5 transactions / second). If not, proceed to the normal account processing flow.

[0043] Step 6: For ordinary accounts, add a pessimistic lock to account A, perform a balance update (e.g., +100 yuan), commit the transaction, release the lock, and return success.

[0044] Example 2: A sudden hotspot occurs in a regular account. Account A receives the 6th request within 5 seconds (exceeding the threshold). The processing flow includes: Steps 1-3 are the same as in Example 1; Step 4: Optimistic locking count. During the 6th counting operation, the version number is 2 (not expired), and the update is successful (count=6).

[0045] Step 5: Hotspot counting control. If the count exceeds the threshold (5 counts / second), the hotspot upgrade process is triggered.

[0046] Step 6: Hotspot upgrade handling Step 6.1: Set the account status to "Hotspot Upgrade in Progress" and reject subsequent requests.

[0047] Step 6.2: Asynchronously execute hot account processing logic (such as asynchronous accounting).

[0048] Step 6.3: After completing the balance update for the current accounting request, persist the account status as a hotspot state.

[0049] Example 3: Application scenarios and processing procedures for optimistic locking conflict and retry mechanisms include: Steps 1-3 are the same as in Example 1; Step 4: Optimistic locking counting. Both accounting request thread A and accounting request thread B simultaneously query count=5 and version=3.

[0050] Request thread a first performs a counting operation: version=3 → count=6, which succeeds.

[0051] The accounting request thread b failed to count (version number mismatch), triggering a retry.

[0052] Retry process: Accounting request thread b re-queries the latest data: count=6, version=4.

[0053] The counting operation was executed again, version=4 → count=7, and it was successful.

[0054] When the final count reaches the threshold, a hotspot upgrade is triggered.

[0055] Example 4: In a concurrent control scenario in a distributed environment, account A receives requests simultaneously on node 1 and node 2, and duplicate marking needs to be avoided. The processing flow of this invention includes: Node 1 completes hotspot identification, sets the hotspot to upgrade status, asynchronously upgrades accounts to hotspot status, and updates the database status.

[0056] When Node 2 checks the account status, it finds that the account is in a hotspot upgrade state and directly returns a service processing failure without triggering duplicate marking, thus avoiding multi-node conflicts.

[0057] Version number synchronization: The database uses an optimistic locking mechanism to verify the version number and ensure the consistency of the state of multiple nodes. If node 2 attempts to update the state before node 1 commits, a version number conflict will occur, and node 2's update will fail.

[0058] Example 5: In timeout and failure handling scenarios, the processing flow of the present invention specifically includes: Optimistic locking timeout: If the loop count exceeds the maximum number of retries (e.g., 3 times), return failure directly, log and trigger alarm, and require manual intervention for investigation. The accounting request will then enter the service processing failure process.

[0059] Hotspot upgrade failure: If the system crashes during the asynchronous upgrade process, it will recover through the database transaction rollback mechanism, and the upgrade process will be re-executed when the next request triggers hotspot identification.

[0060] Advantages of this invention: This invention achieves millisecond-level smooth switching from ordinary accounts to hot accounts by using technologies such as real-time dynamic identification of sudden hot accounts, cyclic optimistic locking counting, hot window control, and distributed version synchronization (without central node conflict). While ensuring the safety of account balances, it solves the problems of poor real-time performance, high lock contention risk, and system avalanche risk in traditional asynchronous marking schemes. It is suitable for high-concurrency financial transaction scenarios (such as flash sales and cross-border payments) and has strong fault tolerance, low modification cost, and horizontal scalability.

[0061] The device of this invention provides real-time hotspot identification and marking capabilities, immediately identifying hotspots when they occur; it provides real-time hotspot upgrade and switching capabilities, immediately converting ordinary services to hotspot services after hotspot identification; it provides high-performance identification and processing capabilities with almost no impact on existing accounting processes and performance; it provides hotspot serial identification capabilities, which may result in brief service failure responses, but the failure rate can be reduced by adjusting parameters; and it supports concurrent hotspots of a single account across multiple system nodes in a distributed environment without introducing new central nodes or creating new hotspot problems.

[0062] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for upgrading serial processing of bank account hotspot identification based on optimistic locking, characterized in that, include: Receive external accounting requests and determine the hotspot status of the account corresponding to the accounting request through hotspot routing; When an account is not in a hotspot state, the hotspot serial identification process for the account is initiated. Establish a time window for account hotspot identification, and identify whether the current accounting request falls within the time window; If the time window is exceeded, an optimistic locking mechanism is used to continuously increment the recognition count. Determine whether the counting result has reached a preset threshold. If it has reached the preset threshold, trigger hotspot upgrade. First, pre-mark the account as a hotspot account, and the account status is hotspot upgrade in progress. After processing the accounting request using the normal account balance, the account is then officially marked as a hotspot.

2. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that: When the account is undergoing a hotspot upgrade, the accounting request is routed to the service failure process.

3. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that, When an account is not in a hotspot state, the hotspot serial identification process is initiated, including: The system checks the account status indicator; if the account is undergoing a hotspot upgrade, it returns a failure message. Query the validity of the account time window and match the time window according to the business time of the accounting request; The counting operation is performed using an optimistic locking mechanism, which includes version number verification and retry mechanisms.

4. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that: The establishment of a time window for account hotspot identification, and the identification of whether the current accounting request falls within the time window, includes: When the first accounting request is triggered, the start time of the accounting request is recorded as the start time of the time window, and the start time plus a preset duration is used as the time window. For subsequent account operations, determine whether they fall within the aforementioned time window: If it falls within the time window, it participates in the hotspot counting of that time window; If the time window falls outside the specified time window, a new time window will be created. The account operation that triggers the creation of a time window will directly enter the normal account processing flow after the time window is created.

5. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that: If the current accounting request does not fall within the specified time window, the accounting request will proceed to the ordinary account balance processing flow.

6. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that, The method of using an optimistic locking mechanism to perform a cyclical increment operation on the identification count includes: Query the current counter value and version number; Update the counter value and version number using the query results as the update condition; If the update is successful, determine whether the counting result has reached the preset threshold; If the update fails, it will be retried repeatedly until the maximum number of retries is reached, at which point the accounting request will be responded to directly.

7. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that: If the counting result does not reach the preset threshold, the accounting request will enter the ordinary account balance processing process.

8. The method for upgrading and serial processing of bank account hotspot identification based on optimistic locking according to claim 1, characterized in that, The step of marking the account as a hotspot after completing the current business process includes: Set the account's "Hotspot Upgrade in Progress" status in the current thread; Complete the original business logic processing; Persistentize account state and mark it as a hotspot.

9. A bank account hotspot identification and upgrade serial processing device based on optimistic locking, used to implement the method of any one of claims 1-5, characterized in that: It includes a hotspot routing module, a hotspot serial identification module, a hotspot window control module, a hotspot counting module based on optimistic locking, a hotspot counting control module, and a hotspot upgrade module; The hotspot routing module is used for: Receive external accounting requests and determine if the account has been marked as a hotspot; The hotspot serial identification module is used for: When an account is not marked as a hotspot, a circular optimistic locking counting mechanism is used to identify hotspots, and the account status is serially controlled during the identification process; when an account is detected to be in a hotspot upgrade state, the accounting request is routed to the service failure process. The hotspot window control module is used for: Set a time window for account hotspot identification, and identify whether the accounting request falls within the current time window based on the time of occurrence of the accounting request; The hotspot counting module based on optimistic locking is used for: An optimistic locking mechanism is used for identification counting and self-looping updates, including a version number verification mechanism; The hotspot counting control module is used for: Determine whether the count result exceeds a preset threshold to decide whether to trigger a hotspot upgrade; The hotspot upgrade module is used for: After confirming that a hotspot upgrade has been triggered, the account is marked as being in the hotspot upgrade state, and the account attribute is officially upgraded to hotspot status after the current accounting request is processed.

10. The bank account hotspot identification and upgrade serial processing device based on optimistic locking according to claim 9, characterized in that, The hotspot upgrade module includes: The status flag unit sets a status flag for the account during the hotspot upgrade after confirming that the hotspot upgrade has been triggered. The asynchronous processing unit maintains the original accounting request processing flow of the account unchanged. The final marking unit marks the account status as a hotspot status after the accounting request is processed.

Images