201131496 六、發明說明： 【發明所屬之技術領域】 本發明係關於網路領域，尤其關於帳戶開發處理方法 及帳戶開發處理系統。 【先前技術】 請參閱圖1，其爲現有帳戶處理系統的原理示意圖。 該帳戶處理系統包括帳戶處理中心11和若干用戶端12。 帳戶處理中心11可以通過專線連接用戶端12，也可以通 過網路（網際網路、內部網）等連接至用戶端12。用戶 端12可以是多個。用戶端12也可以是獨立終端，也可以 爲若千終端組成的區域網路。帳戶處理中心1 1至少包括 伺服器21和資料庫22。資料庫22用於儲存帳戶資訊及 各種處理資訊。伺服器2 1用於對帳戶進行各種操作.和管 理。 以帳戶處理中心11爲第三方支付平臺爲例，當用戶端 12向帳戶處理中心11發送指令，該指令是指將A帳戶中 的資金向若千其他帳戶（以帳戶Bl、B2、Β3·..Βη)支付 金額分別爲SI、S2、S3...SH，現有的支付流程爲： 首先，帳戶處理中心11接收到用戶端12發送的支付 操作； 接著，帳戶處理中心1 1先處理一次支付操作：201131496 VI. Description of the Invention: TECHNICAL FIELD OF THE INVENTION The present invention relates to the field of networking, and more particularly to an account development processing method and an account development processing system. [Prior Art] Please refer to FIG. 1, which is a schematic diagram of the principle of an existing account processing system. The account processing system includes an account processing center 11 and a number of client terminals 12. The account processing center 11 can be connected to the client terminal 12 through a dedicated line, or can be connected to the client terminal 12 via a network (internet, intranet) or the like. The number of clients 12 can be multiple. The client 12 can also be an independent terminal or a local area network composed of thousands of terminals. The account processing center 1 1 includes at least a server 21 and a database 22. The database 22 is used to store account information and various processing information. Server 2 1 is used to perform various operations and management on the account. Taking the account processing center 11 as a third-party payment platform as an example, when the client 12 sends an instruction to the account processing center 11, the instruction refers to transferring the funds in the A account to thousands of other accounts (by accounts B1, B2, Β3. The payment amount is SI, S2, S3...SH, respectively. The existing payment process is: First, the account processing center 11 receives the payment operation sent by the client 12; then, the account processing center 1 1 processes the payment first. operating:
伺服器21鎖住Α帳戶，判斷Α帳戶中的金額是否超 過S1金額，若帳戶中的金額大於等於S1金額’則將A -5- 201131496 帳戶的餘額扣除si金額後’釋放A帳戶的鎖’再鎖住B1 帳戶，在B1帳戶中增加S1金額’操作完畢後釋放B1帳 戶的鎖。 如此，帳戶處理中心1 1需要進行n次上述支付操作。 也就是說，爲了避免帳戶開發處理而有可能影響帳戶 內金額，需要保證在同一時刻只允許對帳戶進行一次操作 ，通常是通過對帳戶進行加鎖來實現的。即’每一個對帳 戶的操作，先判斷能否獲得這個帳戶的鎖’若能’則說明 對同一帳戶沒有其他操作正在處理，當前能對該帳戶進行 本操作。若不能，說明對同一帳戶有其他操作正在處理’ 需要等待。當等待的操作有多個時，就形成了等待進程佇 列。這個等待進程佇列中每一個操作都需要對帳戶進行加 鎖和釋放鎖的操作，並且伺服器只能串列處理該些操作， 佔用比較多的資源。特別是，當這樣的帳戶（即該帳戶有 等待進程佇列）有多個或者帳戶的等待進程佇列中需要處 理的操作個數龐大時，就造成整個系統的處理效率低下， 而且很容易造成系統的癱瘓。假設資料庫的最大連接數是 1 00個。也就是說，資料庫能承受最大開發訪問資料量爲 1 00個。當等待進程佇列中有1 00個操作時，整個系統就 不能接受新的帳戶操作請求，由此造成後續新帳戶操作的 效率低，甚至容易造成整個系統癱瘓》 然而’由於存在一些突發事件而導致某個或某些帳戶 的操作異常’比較常見的操作異常爲對帳戶的操作暴增， 使得帳戶的等待進程佇列中需要處理的操作個數暴增，由 -6- 201131496 此造成整個系統的處理效率降低。 這些突發事件有些是由於系統的不穩定或技術原因造 成的，有些是由於人爲造成的，比如，網上交易過程中商 戶都有本商戶的信用等級，信用等級是購買者或其他用戶 對商戶服務及其出售商品的滿意度評價的體現，網上交易 過程中無法真實感受到商品，因此信用等級對商戶來說非 常重要。以得到更高信用等級爲直接目的，而進行的一些 虛假交易，我們稱之爲信用炒作。當一些商戶組成信用炒 作團體時，這些商戶相關的帳戶就可能出現頻繁的操作， 由於出現某時刻發生在這些帳戶上的操作特別大，使得系 統需要消耗大量的資源來處理該些操作，由此也使其他帳 戶的正常操作受到影響。 也就是說，現有的帳戶處理中心的帳戶處理操作存在 以下的技術缺陷： 現有的支付流程需要對A帳戶進行頻繁操作，每一次 操作都需要鎖住A帳戶，並在處理完畢後釋放A帳戶。 不僅造成伺服器2 1的處理效率低，更爲重要的是造成伺 服器2 1的處理能力急劇下降，甚至不能接收其他用戶端 發出的處理請求，嚴重的造成整個伺服器21的癱瘓。 特別是，當接收到這類對帳戶進行批次處理請求個數 較多，或者這類對帳戶進行批次處理請求中需要處理帳戶 特別多時，對整個伺服器2 1造成的運行壓力非常大，容 易造成伺服器2 1請求處理的佇列堵塞，容易造成請求處 理的失敗率增加。同時，也影響其他用戶的體驗。 201131496 【發明內容】 本發明的第一目的在於提供一種帳戶開發處理方法， 以解決現有技術中由於突發事件引起同一帳戶上平行作業 增加而導致整個系統的處理效率低下的技術問題。 本發明的第二目的在於提供一種帳戶開發處理系統， 以解決現有技術中由於突發事件引起同一帳戶上平行作業 增加而導致整個系統的處理效率低下的技術問題。 —種帳戶開發處理方法，用於帳戶處理中心處理帳戶 操作，包括： (1) 將帳戶分成高開發帳戶和普通帳戶； (2) 當接收到某一帳戶處理操作請求時，先判斷該 帳戶是否是高開發帳戶，若是高開發帳戶則進行步驟（3 )，否則進行步驟（4 ); (3 )若帳戶被鎖定，則將當前操作進入等待進程佇 列等待，直到執行當前操作； (4)進一步判斷帳戶有沒有被鎖定，若帳戶已被鎖 定，則直接報錯後返回，否則執行當前操作。 步驟（4 )還包括’當帳戶已被鎖定時，延時預先設 定的時間後再次判斷當前操作是否被執行，若否，則直接 報錯後返回。 較優地，步驟（1 )進一步包括：A1 :根據高開發帳 戶所占總帳戶數的百分比來設定高開發帳戶的數量q ; A2 :統計預先設定的週期內各帳戶對應的本帳戶進行操作的 運算兀，並按照運算元依次進行排序；A3:取運算元高 -8- 201131496 的前Q位帳戶做爲高開發帳戶。並且，步驟（Ο最好還 包括，將所有高開發帳戶的帳戶號保存在記憶體中。 步驟（2)還包括通過將帳戶號和預先保存在記億體 中的所有高開發帳戶的帳戶號進行對比，如有相同，則該 帳戶爲高開發帳戶，否則，該帳戶爲普通帳戶。 執行當前操作進一步包括：鎖住帳戶；執行對帳戶的 操作；執行完畢後，釋放該帳戶對應的鎖。 一種帳戶開發處理系統，包括帳戶處理中心，該帳戶 處理中心進一步包括： 高開發帳戶庫：用於儲存所有高開發帳戶資訊； 帳戶性質判斷單元：用於接收到某一帳戶處理操作請 求時，根據高開發帳戶庫去判斷該帳戶是否是高開發帳戶 » 高開發帳戶處理單元：用於進一步判斷帳戶有沒有被 鎖定，若帳戶被鎖定，則將當前操作進入等待進程佇列等 待，直到執行當前操作，否則直接執行當前操作； 普通帳戶處理單元··用於進一步判斷帳戶有沒有被鎖 定，若帳戶已被鎖定，則直接報錯後返回，否則執行當前 操作。 所述高開發帳戶處理單元進一步包括： 高開發帳戶鎖定判斷子單元，用於判斷該高開發帳戶 當前是否被鎖； 執行操作子單元，用於鎖住帳戶，再執行對帳戶的操 作，後釋放該帳戶對應的鎖。 -9- 201131496 所述普通帳戶處理單元進一步包括： 普通帳戶鎖定判斷子單元，用於判斷該帳戶當前是否 被鎖； 執行操作子單元，用於鎖住帳戶，再執行對帳戶的操 作，後釋放該帳戶對應的鎖； 鎖定處理子單元，用於該帳戶被鎖後接收到對該帳戶 的操作，採用直接報錯後返回的處理。 一種帳戶開發處理方法，用於帳戶處理中心處理用戶 端發送的帳戶操作請求，包括： (1) 帳戶處理中心將帳戶分成若干種類型帳戶，每 —種類型設置對應的帳戶被鎖定後的處理操作； (2) 當接收到用戶端發送的某一帳戶處理操作請求 時，先確定該帳戶所屬的類型； (3 ) 帳戶處理中心進一步判斷帳戶有沒有被鎖定 ，若帳戶被鎖定，就按照該帳戶所屬類型對應的帳戶被鎖 定後的處理操作流程進行操作，否則執行當前操作。 步驟（1)中每一種類型設置對應的帳戶被鎖定後的 處理操作進一步包括： A1:帳戶被鎖定後，判斷μ的次數是否爲零，若是 ，則直接報錯後返回，若否，過等待時間Τ後判斷帳戶是 否被鎖定’如果被鎖定，則Μ的次數減一，再進行步驟 A1 ’如果未被鎖定’則執行當前操作， 其中’ Μ爲每一種類型設定的對應的等待次數’ Μ的 範圍可以爲〇至無限大。 -10· 201131496 與現有技術相比，本發明具有以下優點： 對於一個普通的帳戶，在帳戶上發生的業務是有規律 的，在一段時間內有個固定的模式。以某個商務平臺爲例 ，一個普通的買家一天的交易量是有限的，每天不會發生 太多的交易，也就是這個帳戶上的交易開發性不是很大， 如果某天在這個帳戶上發生了大量的交易，很可能就是一 些非法業務。而對於大的賣家，則在其上就可能有大量的 開發，會有很多買家買這個賣家的商品，從而產生大的開 發交易。根據以上特點，發明人把帳戶分爲兩類，高開發 帳戶和普通帳戶。對於高開發帳戶，當帳戶餘額發生變化 ’在鎖定帳戶時如果發現帳戶已經被鎖，那麼一直等待而 不報錯返回。而對於普通帳戶發生餘額變動，在鎖定帳戶 時如果發現帳戶被鎖，直接報錯返回，通過這種方式我們 可以對高開發帳戶提供更優質的服務，而對於普通客戶， 這樣一旦某天普通帳戶上發生了大量的開發，通過報錯可 以有效的控制開發量，防止這類帳戶對系統造成危害。 另外，本發明還可以對普通帳戶進行操作請求時，若 該帳戶已被鎖定時，延時預先設定的時間後再次判斷當前 操作是否被執行，若否，則直接報錯後返回。這種延時處 理，能夠降低普通帳戶可能存在的開發處理的報錯率。 【實施方式】 以下結合附圖，具體說明本發明。 請參閱圖1和圖2’其爲本發明的一種帳戶開發處理 -11 - 201131496 系統的原理結構示意圖。它包括帳戶處理中心1 1和用戶 端12。用戶端12提出對帳戶處理中心11上的某個帳戶 或某些帳戶的操作請求，並接收帳戶處理中心11返回的 處理結果。 該帳戶處理中心11進一步包括伺服器31和資料庫 32。資料庫32用於儲存帳戶資訊及各種處理資訊。伺服 器31用於對帳戶進行各種操作和管理。在本發明中，資 料庫32除了包括用於儲存帳戶資訊的帳戶儲存單元321 、用來儲存帳戶處理操作記錄資訊的帳戶操作記錄儲存單 元322之外，還包括： 高開發帳戶庫3 23:用於儲存所有高開發帳戶資訊。 高開發帳戶資訊主要是指能唯一識別高開發帳戶的帳戶號 。本發明可以按照各種規則來設定本中心的高開發帳戶， 比如，可以將重點帳戶設定爲高開發帳戶。也可以將帳戶 一定時間段內進行操作的運算元從高到低排序’取運算元 高的若千帳戶作爲高開發帳戶。 伺服器31進一步包括帳戶性質判斷單元3 1 1 '高開 發帳戶處理單元312和普通帳戶處理單元313。 帳戶性質判斷單元3 1 1 :用於接收到某一帳戶處理操 作請求時，根據高開發帳戶庫去判斷該帳戶是否是高開發 帳戶，如果是，就觸發高開發帳戶處理單元312’如果否 ，則觸發普通帳戶處理單元3 1 3。 高開發帳戶處理單元3 1 2 :用於進一步判斷帳戶有沒 有被鎖定，若帳戶被鎖定，則將當前操作進入等待進彳呈仔 -12- 201131496 列等待，直到執行當前操作，否則直接執行當前操作。 高開發帳戶處理單元3 1 2進一步包括： 高開發帳戶鎖定判斷子單元3 1 2 1，用於判斷該高開 發帳戶當前是否被鎖； 等待進程佇列管理子單元3 1 22，用於管理等待進程 佇列的操作，管理等待進程佇列包括對該些操作的進程如 何進行處理的，比如按照先來先處理的原則，或者採用優 先順序處理的原則等。有些系統自帶有這個管理子單元 3122，此時發明人就無需自設定該管理子單元。 執行操作子單元3 1 23，用於鎖住帳戶，再執行對帳 戶的操作，後釋放該帳戶對應的鎖。 普通帳戶處理單元313:用於進一步判斷帳戶有沒有 被鎖定，若帳戶已被鎖定，則直接報錯後返回，否則執行 當前操作。普通帳戶處理單元313進一步包括： 普通帳戶鎖定判斷子單元3131，用於判斷該帳戶當 前是否被鎖； 執行操作子單元3 1 3 2，用於鎖住帳戶，再執行對帳 戶的操作，後釋放該帳戶對應的鎖； 鎖定處理子單元3 1 3 3，用於該帳戶被鎖後接收到對 該帳戶的操作，採用直接報錯後返回的處理。 普通帳戶處理單元313還包括延時子單元3134，用 於當帳戶已被鎖定時，延時預先設定的時間後再次判斷當 前操作是否被執行，若否，則直接報錯後返回。 上述公開的是單元僅僅是指邏輯上的單元，通常是用 -13- 201131496 軟體來實現的，但本發明並不排除用硬體來實現。 請參閱圖3，其爲一種帳戶開發處理方法的流程圖。 它用於帳戶處理中心處理帳戶操作，包括： S 1 1 〇 :將帳戶分成高開發帳戶和普通帳戶。在本實例 中，現有的帳戶處理中心1 1已存在非常多的帳戶，由此 額外設置一高開發帳戶庫3 2 3，用以保存高開發帳戶資訊 。判斷某一帳戶是高開發帳戶還是普通帳戶，只需要査找 高開發帳戶庫323即可獲知。這種方式，無需要對現有的 帳戶資訊進行修改，減少對原有系統穩定性的影響。還有 一種方式是，對帳戶設定一性質屬性項，每一帳戶在性質 屬性項中保存本帳戶的屬性：高開發帳戶還是普通帳戶。 這種方式也是可以的，但是需要對現有帳戶進行修改’比 較費時間。 將帳戶分爲高開發帳戶和普通帳戶’可以通過以下步 驟完成： A 1 :根據高開發帳戶所占總帳戶數的百分比來設定 高開發帳戶的數量Q: A2:統計預先設定的週期內（如一周內）各帳戶進 行操作的運算元，並按照運算元依次進行排序； A3:取運算元高的前Q位帳戶做爲高開發帳戶’並 將高開發帳戶資訊保存在高開發帳戶庫323中° 並且，定週期根據運算元來更新高開發帳戶庫3 2 3中 的高開發帳戶資訊。通過這種方式，能將本來運算元比較 多的帳戶找出來。 -14- 201131496 爲了提高後續處理的效率，可以將高開發帳戶庫323 中的所有高開發帳戶的帳戶號保存在伺服器31的記憶體 中。 S 1 20 :當接收到某一帳戶處理操作請求時，先判斷該 帳戶是否是高開發帳戶，若是高開發帳戶則進行步驟 S 1 3 0，否則進行步驟S 1 4 0。 本發明是通過以下步驟判斷該帳戶是否是高開發帳戶 的： 將帳戶號和預先保存在記憶體或高開發帳戶庫323中 的所有高開發帳戶的帳戶號進行對比，如相同，則該帳戶 爲高開發帳戶，否則，該帳戶爲普通帳戶。 S 1 3 0 :判斷帳戶是否被鎖定，若是，則將當前操作進 入等待進程佇列等待，直到執行當前操作（S 1 3 1 )，若否 ，則對帳戶執行當前操作（S 1 3 2 )。 S140:進一步判斷帳戶有沒有被鎖定，若帳戶已被鎖 定，則直接報錯後返回（S 1 4 1 )，否則執行當前操作（ S 1 32 )。 S130 的步驟可以通過 oracle 語句來實現 “ select * from account where accountNo = 'xxxxx' for update 該語句表示：。對accountNo爲xxxxx的帳戶進行操 作，該命令隱含 “ select * from account where accountNo = 'xxxxx' for update wait” 即，若該帳戶被鎖後，一直等待’直到能執行該操作 -15- 201131496 si 40的步驟也可以通過JAVA語句來實現。 select * from account where accountNo = ’yyyyy pdate nowait 這條語句表示：如果對帳戶進行操作時發現該 經被鎖，則報錯。上述的僅是一種實現的範例，並 於此，任何實現本思想的實現方式，都應在本發明 範圍內。 執行當前操作進一步包括：鎖住帳戶；執行對 操作；執行完畢後，釋放該帳戶對應的鎖。 請參閱圖4，其爲另一種帳戶開發處理方法的 〇 本實例中的S240的實施步驟與圖3的Sl4〇的 驟不同，其他步驟與圖3中的步驟大致相同。 S 1 1 〇 :將帳戶分成高開發帳戶和普通帳戶。 S 1 20 :當接收到某一帳戶處理操作請求時，先 帳戶是否是高開發帳戶，若是高開發帳戶則進 S130，否則進行步驟S240。 S 1 3 0 :判斷帳戶是否被鎖定，若是，則將當前 入等待進程佇列等待，直到執行當前操作（S 1 3 1 ) ，則對帳戶執行當前操作（S 1 3 2 )。 S 240 :進一步判斷帳戶有沒有被鎖定，若帳戶 定，則等待預先設定的時間（S24 1 )，進一步判斷 作是否被執行（S 2 4 2 )，若否，直接報錯後返回（ 'for u 帳戶已 非局限 的保護 帳戶的 流程圖 實施步 判斷該 行步驟 操作進 ，若否 已被鎖 當前操 S243 ) -16- 201131496 ，若是，則執行當前操作（S 1 3 2 )。當帳戶未被鎖定時， 則也是執行當前操作（S 1 3 2 )。 對帳戶進行鎖住有很多種實現方式，比如’一個常見 的方式是，對帳戶設置一個標誌位元，標誌位元爲1，表 示這個帳戶是鎖住的，標誌位元爲0，表示這個帳戶未被 鎖住。檢測該帳戶是否被鎖住，就是檢測該標誌位元。 本實例中，在接收到對普通帳戶的操作請求時，發現 當前該帳戶有正在處理的操作，延時一預設時間再去判斷 能否進行處理。能夠降低普通帳戶可能存在的開發處理的 報錯率。 本發明實施例將帳戶劃分爲高開發帳戶和普通帳戶兩 種類型進行說明，當然在具體實施過程中，可以不受本發 明實施例的限制將帳戶劃分多種類型，例如：第一類型帳 戶、第二類型帳戶、第三類型帳戶……第N類型帳戶。具 體可以通過以下步驟完成： A 1 :根據第一類型帳戶所占總帳戶數的百分比來設 定第一類型帳戶的數量Q1，根據第二類型帳戶所占總帳 戶數的百分比來設定第二類型帳戶的數量Q2’以此類推 ，可設定第N類型帳戶的數量Qn; A2 :統計預先設定的週期內（如一周內）各帳戶進 行操作的運算元，並按照運算元由低到高依次進行排序； A3:取運算元最低的前Q1位帳戶做爲第一類型帳戶 ，取接下來的Q 2位帳戶做爲第二類型帳戶，以此類推可 獲得各種類型的帳戶資訊，並將各種類型的帳戶資訊保存 -17- 201131496 在資料庫中。 對帳戶劃分成多種類型，還可以通過以下步驟來實現 B1:預先設定第一類型帳戶、第二類型帳戶、···第N 類型帳戶各自在總帳戶數中所占的比例； B2 :統計預先設定的週期內（如一周內）各帳戶進行 操作的運算元，並按照運算元由低到高依次進行排序成帳 戶佇列； B3 :統計當前的總帳戶數Μ ; Β4 :按照各類型帳戶所占的比例和總帳戶數Μ ’計 算出各類型帳戶所占的數量； Β5:每一類型帳戶依次從帳戶佇列中取對應數量的帳 戶作爲本類型帳戶中的帳戶，並將該些帳戶資訊保存至對 應的資料庫中。 本實施例的處理思想爲：將帳戶劃分爲第一類型帳戶 、第二類型帳戶、第三類型帳戶……第Ν類型帳戶，針對 不同類型的帳戶設定不同的處理策略。比如，將不同的類 型帳戶分成不同的優先順序，優先順序越高，當帳戶被鎖 定時，則等待預先設定的時間也就越長。 舉個實例來說，所述處理策略可以爲：對於第一類型 的帳戶，若帳戶被鎖定時，則直接報錯返回；對於第二類 型的帳戶，當帳戶被鎖定時，則等待預先設定的時間t， 判斷該帳戶是否仍被鎖定，若仍被鎖定，則直接報錯返回 ;對於第三類型的帳戶，當帳戶被鎖定時，則等待預先設 -18- 201131496 疋的時間t進行判斷後，發現該帳戶仍被鎖定時，則再等 待一個預先設定的時間t，若仍被鎖定，則報錯返回，以 此類推可針對不同類型的帳戶設定不同的處理策略。 通過上述對帳戶分成若干種類型，爲每一種類型的帳 戶設定不同的處理策略，即， —種帳戶開發處理方法，用於帳戶處理中心處理用戶 端發送的帳戶操作請求，包括： (1) 帳戶處理中心將帳戶分成若干種類型帳戶，每 一種類型設置對應的帳戶被鎖定後的處理操作； (2) 當接收到用戶端發送的某—帳戶處理操作請求 時’先確定該帳戶所屬的類型； (3 ) 帳戶處理中心進一步判斷帳戶有沒有被鎖定 ’若帳戶被鎖定，就按照該帳戶所屬類型對應的帳戶被鎖 定後的處理操作流程進行操作，否則執行當前操作。 步驟（1)中每一種類型設置對應的帳戶被鎖定後的 處理操作進一步包括： K1:帳戶被鎖定後，判斷Μ的次數是否爲零，若是 ，則直接報錯後返回，若否，過等待時間Τ後判斷帳戶是 否被鎖定，如果被鎖定，則Μ的次數減一，再進行步驟 Κ 1，如果未被鎖定，則執行當前操作， 其中，Μ爲每一種類型設定的對應的等待次數，Μ的 範圍可以爲〇至無限大。 以上公開的僅爲本發明的幾個具體實施例’但本發明 並非局限於此，任何本領域的技術人員能思之的變化’都 -19- 201131496 應落在本發明的保護範圍內。 【圖式簡單說明】 圖1爲現有帳戶處理系統的原理示意圖； 圖2爲本發明的一種帳戶處理中心的原理結構示意圖 » 圖3爲帳戶處理方法的一種流程示意圖； 圖4爲帳戶處理方法的另一種流程示意圖。 【主要元件符號說明】 1 1 :帳戶處理中心 12 :用戶端 2 1 :伺服器 2 2 :資料庫 3 1 :伺服器 3 2 :資料庫 3 1 1 :帳戶性質判斷單元 3 1 2 :高開發帳戶處理單元 313:普通帳戶處理單元 321 :帳戶儲存單元 322 :帳戶操作記錄儲存單元 3 23 :高開發帳戶庫 3 1 2 1 :高開發帳戶鎖定判斷子單元 3 1 22 :等待進程佇列管理子單元 -20- 201131496 3 123 :執行操作子單元 3 1 3 1 :普通帳戶鎖定判斷子單元 3 1 3 2 :執行操作子單元 3133:鎖定處理子單元 3 1 3 4 :延時子單元 -21 -The server 21 locks the account and determines whether the amount in the account exceeds the S1 amount. If the amount in the account is greater than or equal to the S1 amount, the balance of the A-5-201131496 account is deducted from the si amount and the 'lock of the A account is released'. Relock the B1 account and add the S1 amount to the B1 account. After the operation is completed, release the lock of the B1 account. As such, the account processing center 11 needs to perform the above-described payment operation n times. That is to say, in order to avoid account development processing and possibly affect the amount in the account, it is necessary to ensure that only one operation of the account is allowed at the same time, usually by locking the account. That is, the operation of each account, first determine whether the lock of this account can be obtained, if it can, it means that no other operations are being processed for the same account, and the current operation can be performed on the account. If not, there are other operations on the same account that are being processed' need to wait. When there are multiple operations waiting, a wait queue is formed. Each operation in this waiting process queue needs to lock and release the lock on the account, and the server can only process the operations in series, occupying more resources. In particular, when there are multiple accounts in this account (that is, the account has a queue of waiting processes) or the number of operations to be processed in the waiting queue of the account is large, the processing efficiency of the entire system is low, and it is easy to cause The flaws of the system. Suppose the maximum number of connections in the database is 100. In other words, the database can withstand a maximum of 100 development visits. When there are 100 operations in the waiting process queue, the entire system cannot accept new account operation requests, which makes the subsequent new account operations inefficient, and even easy to cause the entire system. However, due to some emergencies The operation of one or some of the accounts is abnormal. The more common operation exception is the surge in the operation of the account, which makes the number of operations that need to be processed in the waiting process of the account increase, which is caused by -6-201131496. The processing efficiency of the system is reduced. Some of these emergencies are caused by system instability or technical reasons, and some are caused by humans. For example, in the process of online transactions, merchants have the credit rating of the merchant, and the credit rating is the purchaser or other users. The merchant service and the satisfaction evaluation of the products sold can not truly feel the goods during the online transaction process, so the credit rating is very important for the merchants. Some of the false transactions that are made with the direct purpose of getting a higher credit rating are called credit hype. When some merchants form a credit speculative group, these merchant-related accounts may have frequent operations. Due to the fact that the operations occurring on these accounts at a certain moment are particularly large, the system needs to consume a large amount of resources to handle the operations. It also affects the normal operation of other accounts. That is to say, the existing account processing center account processing operation has the following technical defects: The existing payment process requires frequent operations on the A account, and each operation requires locking the A account and releasing the A account after processing. Not only does the processing efficiency of the server 21 be low, but more importantly, the processing capability of the server 21 is drastically reduced, and even the processing request issued by other clients is not received, which seriously causes the flaw of the entire server 21. In particular, when receiving such a large number of batch processing requests for an account, or such a large number of processing accounts for batch processing requests, the operation pressure on the entire server 21 is very large. It is easy to cause the queue of the server 21 to request processing to be blocked, which tends to increase the failure rate of the request processing. At the same time, it also affects the experience of other users. SUMMARY OF THE INVENTION A first object of the present invention is to provide an account development processing method for solving the technical problem that the processing efficiency of the entire system is low due to an increase in parallel operations on the same account due to an unexpected event in the prior art. A second object of the present invention is to provide an account development processing system for solving the technical problem that the processing efficiency of the entire system is low due to an increase in parallel operations on the same account due to an unexpected event in the prior art. An account development processing method for an account processing center to process account operations, including: (1) dividing an account into a high development account and a normal account; (2) when receiving an account processing operation request, first determining whether the account is Is a high development account, if it is a high development account, proceed to step (3), otherwise proceed to step (4); (3) if the account is locked, the current operation enters the waiting process queue until the current operation is performed; (4) Further determine whether the account has been locked. If the account has been locked, return directly after the error, otherwise perform the current operation. Step (4) further includes 'when the account has been locked, it is judged again whether the current operation is executed after a predetermined time delay, and if not, the error is directly returned. Preferably, the step (1) further comprises: A1: setting the number q of the high development account according to the percentage of the total account of the high development account; A2: counting the account corresponding to each account in the preset period The operation is performed, and the operations are sequentially sorted according to the operation elements; A3: The first Q-bit account of the operation element high-8-201131496 is taken as the high development account. And, the step (better preferably includes storing the account numbers of all the high development accounts in the memory. Step (2) further includes by using the account number and the account number of all the high development accounts previously stored in the record. For comparison, if the account is the same, the account is a high development account, otherwise, the account is a normal account. Performing the current operation further includes: locking the account; performing an operation on the account; after the execution is completed, releasing the lock corresponding to the account. An account development processing system, including an account processing center, the account processing center further comprising: a high development account library: for storing all high development account information; an account property judgment unit: for receiving an account processing operation request, according to High development account library to determine whether the account is a high development account » High development account processing unit: used to further determine whether the account is locked, if the account is locked, the current operation enters the waiting process queue waiting until the current operation is performed Otherwise, the current operation is directly executed; the ordinary account processing unit is used for Steps to determine whether the account is locked, if the account has been locked, return directly after the error, otherwise perform the current operation. The high development account processing unit further includes: a high development account lock determination sub-unit for determining the high development account Whether the current account is locked; the operation subunit is used to lock the account, and then the operation of the account is performed, and then the lock corresponding to the account is released. -9- 201131496 The general account processing unit further includes: a common account lock determination subunit For determining whether the account is currently locked; performing an operation sub-unit for locking the account, and then performing an operation on the account, and then releasing the lock corresponding to the account; and locking the processing sub-unit for receiving the account after being locked To the operation of the account, the processing returned directly after the error is reported. An account development processing method for the account processing center to process the account operation request sent by the client, including: (1) The account processing center divides the account into several types of accounts. , each type of setting the corresponding account is locked after the processing operation; (2) when connected When an account processing operation request sent by the client sends an operation request, first determine the type to which the account belongs; (3) the account processing center further determines whether the account is locked, and if the account is locked, the account corresponding to the type of the account is The operation flow after the lock operation is performed, otherwise the current operation is performed. The processing operation after the account corresponding to each type setting in step (1) is locked further includes: A1: After the account is locked, it is determined whether the number of times of μ is zero. If yes, return directly after the error, if not, after the waiting time, judge whether the account is locked. If it is locked, the number of times is reduced by one, and then proceed to step A1 'If not locked', the current operation is performed, where '对应 The corresponding waiting times set for each type 'Μ can range from 〇 to infinity. -10· 201131496 Compared with the prior art, the present invention has the following advantages: For an ordinary account, the business occurring on the account It is regular and has a fixed pattern for a while. Take a business platform as an example. The average buyer's trading volume per day is limited. There will not be too many transactions every day, that is, the transaction development on this account is not very big, if one day is on this account. A lot of transactions have taken place, most likely some illegal business. For large sellers, there may be a lot of development on it, and many buyers will buy the seller's goods, which will lead to large development transactions. Based on the above characteristics, the inventors divided the accounts into two categories, a high development account and a general account. For high development accounts, when the account balance changes ‘If the account is already locked when the account is locked, then wait until no error is returned. For the balance change of the ordinary account, if the account is locked when the account is locked, the error will be returned directly. In this way, we can provide better service to the high development account, and for ordinary customers, once on a regular account. A lot of development has taken place, and the amount of development can be effectively controlled through error reporting to prevent such accounts from harming the system. In addition, the present invention can also perform an operation request for a normal account. If the account has been locked, it is determined whether the current operation is executed after a predetermined time delay. If not, the error is returned directly after the error is reported. This delay processing can reduce the error rate of development processing that may exist in a normal account. [Embodiment] Hereinafter, the present invention will be specifically described with reference to the accompanying drawings. Please refer to FIG. 1 and FIG. 2', which are diagrams showing the principle structure of an account development process -11 - 201131496. It includes account processing center 1 1 and client 12. The client 12 makes an operation request for an account or some accounts on the account processing center 11, and receives the processing result returned by the account processing center 11. The account processing center 11 further includes a server 31 and a database 32. The database 32 is used to store account information and various processing information. The server 31 is used to perform various operations and management on the account. In the present invention, the database 32 includes, in addition to the account storage unit 321 for storing account information, and the account operation record storage unit 322 for storing account processing operation record information, the high-definition account library 3 23: Store all high development account information. High development account information mainly refers to the account number that uniquely identifies a high development account. The present invention can set the high development account of the center according to various rules. For example, the key account can be set as a high development account. It is also possible to sort the operands that operate in the account for a certain period of time from high to low, and take the thousands of accounts with high operands as high development accounts. The server 31 further includes an account property judging unit 3 1 1 'high open account processing unit 312 and a normal account processing unit 313. The account property judging unit 3 1 1 is configured to judge whether the account is a high development account according to the high development account library when receiving an account processing operation request, and if so, trigger the high development account processing unit 312 ′′ if no, Then the ordinary account processing unit 3 1 3 is triggered. High development account processing unit 3 1 2: used to further determine whether the account is locked. If the account is locked, the current operation will enter the waiting queue -12- 201131496 column waiting until the current operation is performed, otherwise the current operation is directly executed. operating. The high development account processing unit 3 1 2 further includes: a high development account lock determination subunit 3 1 2 1 for determining whether the high development account is currently locked; waiting for the process queue management subunit 3 1 22 for managing wait The operation queue queue operation, management wait process queue includes how to process the operations of the operations, such as the principle of first-come first-served, or the principle of priority processing. Some systems have this management subunit 3122, and the inventor does not need to set the management subunit at this time. The operation sub-unit 3 1 23 is executed to lock the account, and then the operation of the account is performed, and then the lock corresponding to the account is released. Ordinary account processing unit 313: for further determining whether the account is locked. If the account has been locked, returning directly after the error is reported, otherwise the current operation is performed. The normal account processing unit 313 further includes: a normal account lock determination sub-unit 3131 for determining whether the account is currently locked; performing an operation sub-unit 3 1 3 2 for locking the account, and then performing an operation on the account, and then releasing The lock corresponding to the account; the lock processing sub-unit 3 1 3 3, for receiving the operation of the account after the account is locked, and adopting the process of returning directly after the error is reported. The normal account processing unit 313 further includes a delay sub-unit 3134 for re-determining whether the current operation is executed after a predetermined time delay when the account has been locked, and if not, returning directly after the error is reported. The above disclosure means that the unit is merely a logical unit, which is usually implemented by the software of -13-201131496, but the invention is not excluded by hardware. Please refer to FIG. 3, which is a flowchart of an account development processing method. It is used by the Account Processing Center to handle account operations, including: S 1 1 〇 : Divide accounts into high-development accounts and regular accounts. In this example, the existing account processing center 11 has a very large number of accounts, thereby additionally setting up a high development account library 3 2 3 for saving high development account information. To determine whether an account is a high development account or a normal account, you only need to find the high development account library 323 to know. In this way, there is no need to modify existing account information to reduce the impact on the stability of the original system. Another way is to set a property item for the account, and each account holds the attributes of the account in the property item: high development account or normal account. This is also possible, but it takes a lot of time to make changes to existing accounts. Dividing an account into a high-development account and a normal account can be done by the following steps: A 1 : Set the number of high-development accounts based on the percentage of the total number of accounts in the high-development account Q: A2: Statistics within a preset period (eg Within one week) the operands operated by each account are sorted in order according to the operands; A3: the first Q-bit account with the operand height is taken as the high development account' and the high development account information is saved in the high development account library 323. ° Also, the high-development account information in the high-development account library 3 2 3 is updated according to the operation unit. In this way, it is possible to find out an account with a relatively large number of original operands. -14- 201131496 In order to improve the efficiency of subsequent processing, the account numbers of all the high development accounts in the high development account library 323 can be saved in the memory of the server 31. S 1 20: When receiving an account processing operation request, first determine whether the account is a high development account, and if it is a high development account, proceed to step S 1 3 0, otherwise proceed to step S 1 4 0. The present invention determines whether the account is a high development account by the following steps: comparing the account number with the account number of all high development accounts previously stored in the memory or high development account library 323, if the same, the account is High development account, otherwise, the account is a normal account. S 1 3 0 : judge whether the account is locked, if yes, wait for the current operation to wait for the process queue until the current operation is performed (S 1 3 1 ), and if not, perform the current operation on the account (S 1 3 2 ) . S140: further determining whether the account is locked. If the account has been locked, returning directly after the error (S 1 4 1 ), otherwise performing the current operation (S 1 32). The step of S130 can be implemented by the oracle statement "select * from account where accountNo = 'xxxxx' for update. The statement indicates: the operation of the account with accountNo xxxxx, the command implies "select * from account where accountNo = 'xxxxx 'for update wait', that is, if the account is locked, it will wait until 'can perform this operation-15-201131496 si 40 steps can also be implemented by JAVA statement. select * from account where accountNo = 'yyyyy pdate nowait The statement indicates that if the account is operated and found to be locked, an error is reported. The above is only an example of implementation, and any implementation that implements the present idea should be within the scope of the present invention. The operation further includes: locking the account; performing the pair operation; releasing the lock corresponding to the account after the execution is completed. Please refer to FIG. 4, which is an implementation step of S240 in the example of another account development processing method and FIG. 3 The steps of Sl4 are different, and the other steps are roughly the same as those in Figure 3. S 1 1 〇: Divide the account into high Send account and normal account S 1 20: When receiving an account processing operation request, whether the first account is a high development account, if it is a high development account, proceed to S130, otherwise proceed to step S240. S 1 3 0 : determine whether the account is Is locked, if yes, waits for the current waiting process queue until the current operation is performed (S 1 3 1 ), then the current operation is performed on the account (S 1 3 2 ). S 240 : further determining whether the account is locked, If the account is fixed, it waits for a preset time (S24 1 ), and further determines whether the execution is performed (S 2 4 2 ). If not, it returns directly after the error is reported (the flow chart of the 'for u account's non-limited protection account is implemented. Step to judge the step operation, if it has been locked, currently operate S243) -16- 201131496, and if so, perform the current operation (S 1 3 2 ). When the account is not locked, the current operation is also performed (S 1 3 2) There are many ways to lock an account. For example, 'a common way is to set a flag bit for the account. The flag bit is 1, indicating that the account is locked. If the element is 0, it means that the account is not locked. If the account is locked, it is detected by the flag bit. In this example, when receiving an operation request for the ordinary account, it is found that the account is currently being processed. Operation, delay for a preset time and then judge whether it can be processed. It can reduce the error rate of development processing that may exist in a normal account. The embodiment of the present invention divides the account into two types: a high-development account and a common account. Of course, in the specific implementation process, the account may be divided into multiple types without being restricted by the embodiment of the present invention, for example, the first type of account, the first Two types of accounts, third type of accounts... Type N accounts. Specifically, the following steps can be completed: A1: The number Q1 of the first type of account is set according to the percentage of the total account number of the first type of account, and the second type of account is set according to the percentage of the total number of accounts of the second type of account. The number Q2' and so on, can be set to the number Qn of the N-type account; A2: Count the operands operated by each account within a preset period (such as one week), and sort according to the operands from low to high. A3: Take the lowest Q1 account with the lowest operand as the first type account, take the next Q 2 account as the second type account, and so on to get various types of account information, and various types of accounts. Account Information Save -17- 201131496 in the database. Dividing the account into multiple types, you can also implement B1 by pre-setting the first type account, the second type account, and the N-type account in the total number of accounts; B2: Statistics advance The operands operated by each account within the set period (such as one week), and sorted into account queues according to the operation elements from low to high; B3: statistics current total account number Μ; Β4: according to each type of account Proportion and total number of accounts Μ 'Calculating the number of accounts of each type; Β5: Each type of account in turn takes the corresponding number of accounts from the account queue as the account in this type of account, and the account information Save to the corresponding database. The processing idea of this embodiment is: dividing the account into a first type account, a second type account, a third type account, a third type account, and setting different processing strategies for different types of accounts. For example, different types of accounts are divided into different priorities, and the higher the priority, the longer the waiting time is set when the account is locked. For example, the processing policy may be: for the first type of account, if the account is locked, the error is directly returned; for the second type of account, when the account is locked, waiting for the preset time t, to determine whether the account is still locked, if it is still locked, return directly to the error; for the third type of account, when the account is locked, wait for the time t of -18-201131496 预先 pre-set to judge When the account is still locked, it waits for a preset time t. If it is still locked, it will return an error, and so on, it can set different processing strategies for different types of accounts. By dividing the account into several types, the different processing policies are set for each type of account, that is, an account development processing method for the account processing center to process the account operation request sent by the client, including: (1) Account The processing center divides the account into several types of accounts, and each type sets the processing operation after the corresponding account is locked; (2) When receiving the certain-account processing operation request sent by the client, 'determine the type to which the account belongs first; (3) The account processing center further determines whether the account is locked. If the account is locked, the operation operation flow is performed according to the account corresponding to the type of the account being locked, otherwise the current operation is performed. The processing operation after the corresponding account of each type setting in step (1) is locked further includes: K1: After the account is locked, it is determined whether the number of times is zero, and if yes, return directly after the error, if not, wait time After that, it is judged whether the account is locked. If it is locked, the number of times is reduced by one, and then step Κ 1, if it is not locked, the current operation is performed, where Μ is the corresponding waiting number set for each type, Μ The range can range from 〇 to infinity. The above disclosure is only a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variation that can be considered by those skilled in the art is -19-201131496, which falls within the protection scope of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram showing the principle of an existing account processing system; FIG. 2 is a schematic structural diagram of an account processing center according to the present invention. FIG. 3 is a schematic flowchart of an account processing method. FIG. Another schematic diagram of the process. [Main component symbol description] 1 1 : Account processing center 12: User terminal 2 1 : Server 2 2 : Database 3 1 : Server 3 2 : Database 3 1 1 : Account property judgment unit 3 1 2 : High development Account processing unit 313: ordinary account processing unit 321: account storage unit 322: account operation record storage unit 3 23: high development account library 3 1 2 1 : high development account lock judgment sub-unit 3 1 22: waiting process queue manager Unit-20- 201131496 3 123 : Execution operation subunit 3 1 3 1 : Normal account lock judgment subunit 3 1 3 2 : Execution operation subunit 3133: Lock processing subunit 3 1 3 4 : Delay subunit 21 -