下面將結合本說明書實施例中的圖式,對本說明書實施例中的技術方案進行清楚、完整地描述,顯然,所描述的實施例僅僅是本說明書一部分實施例,而不是全部的實施例。基於本說明書中的實施例,本領域普通技術人員在沒有作出創造性勞動前提下所獲得的所有其他實施例,都應當屬於本說明書保護的範圍。
請參閱圖1和圖2。本說明書實施例提供一種基於區塊鏈的資料處理方法。
在本實施例中,所述區塊鏈(Block Chain),可以是一種按照時間先後順序,將多個區塊資料以鏈式結構進行組織,並以密碼學演算法保證安全、可追溯、且不可篡改的分散式帳本。所述區塊鏈可以包括公有區塊鏈、聯合區塊鏈(也稱為聯盟區塊鏈)、和私有區塊鏈等。所述區塊鏈可以基於區塊鏈網路來實現。所述區塊鏈網路可以包括P2P網路(peer-to-peer network)等。所述區塊鏈網路可以包括多個區塊鏈節點。各個區塊鏈節點之間共同維護統一的區塊鏈帳本。
在本實施例中,所述資料處理方法以匯出方伺服器為執行主體。所述匯出方伺服器可以作為一個區塊鏈節點加入區塊鏈網路。在所述匯出方伺服器中可以登錄有匯出方帳戶。所述匯出方帳戶可以為匯出方在所述區塊鏈中的帳戶。所述匯出方伺服器能夠與用戶端進行通信。所述用戶端例如可以為智慧手機、平板電子設備、可攜式電腦、個人數位助理(PDA)、或智慧穿戴設備等。所述資料處理方法可以包括以下步驟。
步驟S10:根據基準時刻和提交時間間隔,計算提交時刻。
在本實施例中,所述基準時刻可以包括以下至少一種:最近一次向區塊鏈提交合併交易資訊的時刻、最近一次向區塊鏈提交虛假交易資訊的時刻。關於所述合併交易資訊和所述虛假交易資訊在後續過程中會有詳細介紹。
在本實施例中,所述提交時間間隔的取值可以根據業務需要靈活設定。具體地,所述提交時間間隔的取值可以為一固定值;或者,也可以依據業務實際需求分時間段,每一時間段內設定為一固定值;又或者,還可以為一隨機值。例如,在交易高峰期提交時間間隔的取值可以設定為0.1秒鐘(還可以依據業務需求設置更短或更長);在交易低谷期提交時間間隔的取值可以設定為1分鐘(還可以依據業務需求設置更短或更長)。當然,還可以根據分佈函數設定所述提交時間間隔的取值,使得所述提交時間間隔的取值滿足所述分佈函數。所述分佈函數例如可以包括指數分佈函數和愛爾朗分佈(Erlang Distribution)函數。其中,所述指數分佈函數的運算式可以為;所述愛爾朗分佈函數的運算式可以為。這裡表示提交時間間隔的取值;表示到達率;表示愛爾朗分佈函數的階數。其中,所述到達率可以表示單位時間內事件發生的數量。在一些場景示例中,所述到達率具體可以表示單位時間內的交易數量。在實際業務中,例如,可以設定提交時間間隔的期望交易(包括真實交易和虛假交易)到達率D;可以統計真實交易的實際到達率E。那麼,在指數分佈函數和愛爾朗分佈函數中。當然,本領域技術人員應當能夠理解,上述根據分佈函數和愛爾朗分佈函數設定提交時間間隔的取值的方式僅為示例,實際上根據分佈函數和愛爾朗分佈函數還可以採用任意其它適當方式來設定提交時間間隔的取值。
在本實施例中,所述匯出方伺服器可以將基準時刻和提交時間間隔相加,得到提交時刻。具體地,所述匯出方伺服器可以將最近一次向所述區塊鏈提交交易資訊的時刻和提交時間間隔相加,得到提交時刻。這裡最近一次向所述區塊鏈提交交易資訊的時刻可以為提交合併交易資訊的時刻,或者,也可以為提交虛假交易資訊的時刻。
步驟S12:在所述提交時刻到達以後,對在所述提交時間間隔內接收到的至少一個原始交易資訊進行合併處理,得到至少一個合併交易資訊。
在本實施例中,所述原始交易資訊可以為來自所述用戶端的交易資訊。具體地,在所述提交時間間隔內,所述用戶端可以向所述匯出方伺服器發送交易資訊,所述匯出方伺服器可以接收交易資訊作為原始交易資訊。其中,所述原始交易資訊可以包括匯入方帳戶標識及其對應的原始交易金額。所述匯入方帳戶標識可以用於標識匯入方帳戶,例如可以為所述匯入方帳戶的名稱或地址等。在本實施例的一個實施方式中,所述原始交易資訊還可以包括真實業務資訊。所述真實業務資訊例如可以包括訂單號、用戶資訊等等。這裡所述原始交易資訊可以直接包括所述真實業務資訊,或者,還可以包括所述真實業務資訊的密文。進一步地,在本實施方式中,所述原始交易資訊還可以包括真實業務資訊的簽名資訊。
在本實施例中,所述合併交易資訊可以包括至少一個匯入方帳戶標識及其對應的合併交易金額。在所述合併交易資訊中,匯入方帳戶標識對應的合併交易金額可以根據該匯入方帳戶標識對應的原始交易金額計算得到,例如可以為該匯入方帳戶標識對應的原始交易金額之和。在本實施例的一個實施方式中,所述原始交易資訊可以包括真實業務資訊。相應地,所述合併交易資訊可以包括至少一個匯入方帳戶標識對應的真實業務資訊。匯入方帳戶標識在合併交易資訊中對應的真實業務資訊可以根據該匯入方帳戶標識在原始交易資訊中對應的真實業務資訊確定得到。這裡所述合併交易資訊可以直接包括所述真實業務資訊,或者,還可以包括所述真實業務資訊的密文。進一步地,在本實施方式中,所述合併交易資訊還可以包括真實業務資訊的簽名資訊。
在本實施例中,所述匯出方伺服器在所述提交時間間隔內接收到的原始交易資訊的數量可以為一個或多個。在接收到的原始交易資訊的數量為一個時,所述匯出方伺服器可以直接將該原始交易資訊作為合併交易資訊。在接收到的原始交易資訊的數量為多個時,所述匯出方伺服器可以將所述多個原始交易資訊合併為至少一個合併交易資訊。具體地,所述匯出方伺服器可以採用任意方式將所述多個原始交易資訊合併為至少一個合併交易資訊。例如,所述匯出方伺服器可以將所述多個原始交易資訊合併為一個合併交易資訊。另舉一例,所述匯出方伺服器可以將所述多個原始交易資訊中具有相同匯入方帳戶標識的原始交易資訊合併為一個合併交易資訊。
在一個場景示例中,所述匯出方伺服器在所述提交時間間隔內接收到的原始交易資訊可以包括A1、A2、A3、B1、B2等5個。所述5個原始交易資訊可以如下表1所示。
表1
所述匯出方伺服器可以將所述5個原始交易資訊合併為一個合併交易資訊。透過合併得到的合併交易資訊可以如下表2所示。
表2
在另一個場景示例中,所述匯出方伺服器在所述提交時間間隔內接收到的原始交易資訊可以包括A4、A5、A6、B3、B4等5個。所述5個原始交易資訊可以如下表3所示。
表3
所述匯出方伺服器可以將所述5個原始交易資訊合併為一個合併交易資訊。透過合併得到的合併交易資訊可以如下表4所示。
表4
當然,所述匯出方伺服器還可以將所述5個原始交易資訊合併為兩個合併交易資訊。透過合併得到的合併交易資訊可以分別如下表5和下表6所示。
表5
表6
步驟S14:向所述區塊鏈提交所述至少一個合併交易資訊。
在本實施例中,所述匯出方設備可以向所述區塊鏈提交所述至少一個合併交易資訊;以便所述區塊鏈中的共識區塊鏈節點能夠根據合併交易資訊中的合併交易金額更新匯出方帳戶的餘額和匯入方帳戶的餘額。例如,從匯出方帳戶的餘額中扣除所述合併交易金額;將合併交易金額記入匯入方帳戶的餘額。其中,所述匯出方設備可以同時向所述區塊鏈提交所述至少一個合併交易資訊,或者,也可以分別向所述區塊鏈提交所述至少一個合併交易資訊。
在本實施例的一個實施方式中,在向所述區塊鏈提交所述至少一個合併交易資訊之前,針對所述至少一個合併交易資訊中的每個合併交易資訊,所述匯出方伺服器還可以根據該合併交易資訊產生校驗資訊;可以在該合併交易資訊中添加該校驗資訊。例如,所述校驗資訊可以包括合併交易資訊的簽名資訊。
在本實施例的一個實施方式中,在向所述區塊鏈提交所述至少一個合併交易資訊之前,所述匯出方伺服器還可以對所述至少一個合併交易資訊中的合併交易金額進行加密處理。這樣可以實現合併交易金額的隱藏和保密。
在本實施例的一個實施方式中,所述匯出方伺服器可以提供有虛假業務資訊集合。所述虛假業務資訊集合可以包括至少一個虛假業務資訊。所述虛假業務資訊例如可以包括虛假的訂單號、虛假的用戶資訊等等。所述虛假業務資訊可以是預先設定的。如此,在向所述區塊鏈提交所述至少一個合併交易資訊之前,針對每個合併交易資訊中的每個匯入方帳戶標識,所述匯出方伺服器還可以從所述虛假業務資訊集合中選取至少一個虛假業務資訊,作為該匯入方帳戶標識在該合併交易資訊中對應的虛假業務資訊。這裡選取的虛假業務資訊的數量可以根據業務需要靈活設定,例如可以選取1個、2個、或5個虛假業務資訊。這樣透過在合併交易資訊中添加虛假業務資訊,可以隱藏合併交易資訊中真實業務資訊的數量,避免透過合併交易資訊中真實業務資訊的數量洩漏交易筆數。
進一步地,在本實施方式中,在所述虛假業務資訊集合中虛假業務資訊可以對應有簽名資訊。相應地,每個合併交易資訊還可以包括虛假業務資訊對應的簽名資訊。
進一步地,在本實施方式中,在所述虛假業務資訊集合中虛假業務資訊可以對應有匯入方帳戶標識。如此,針對每個合併交易資訊中的每個匯入方帳戶標識,所述匯出方伺服器可以從所述虛假業務資訊集合中選取該匯入方帳戶標識對應的虛假業務資訊,作為該合併交易資訊中的虛假業務資訊。
例如,所述虛假業務資訊集合可以包括虛假業務資訊AXJ1_D、AXJ2_D、AXJ3_D、BXJ1_D、BXJ2_D。其中,虛假業務資訊AXJ1_D、AXJ2_D、AXJ3_D可以與匯入方帳戶標識A相對應;虛假業務資訊BXJ1_D、BXJ2_D可以與匯入方帳戶標識B相對應。虛假業務資訊AXJ1_D、AXJ2_D、AXJ3_D、BXJ1_D、BXJ2_D的簽名資訊可以分別為AXJ1_QM、AXJ2_QM、AXJ3_QM、BXJ1_QM、BXJ2_QM。
透過合併得到的合併交易資訊可以前述表4所示。那麼,在添加虛假業務資訊以後,該合併交易資訊可以如下表7所示。
表7
在本實施例的一個實施方式中,在所述提交時間間隔內,所述用戶端有可能沒有向所述匯出方伺服器發送交易資訊。這樣在所述提交時間間隔內,所述匯出方伺服器便沒有接收到原始交易資訊。如此所述匯出方伺服器可以產生虛假交易資訊。所述虛假交易資訊可以包括匯入方帳戶標識及其對應的數值為零的交易金額。這裡所述匯出方伺服器可以採用任意方式獲取匯入方帳戶標識作為所述虛假交易資訊中的匯入方帳戶標識。例如,所述匯出方伺服器可以隨機選取區塊鏈中的帳戶標識,作為所述虛假交易資訊中的匯入方帳戶標識。
所述匯出方伺服器可以對所述虛假交易資訊中數值為零的交易金額進行加密處理;可以向所述區塊鏈提交所述虛假交易資訊。這樣在區塊鏈中的共識區塊鏈節點根據數值為零的交易金額更新匯出方帳戶的餘額和匯入方帳戶的餘額以後,匯出方帳戶的餘額和匯入方帳戶的餘額可以保持不變。
在本實施例中,所述匯出方伺服器可以對在提交時間間隔內接收到的原始交易資訊進行合併處理,使得第三方無法獲得實際向區塊鏈提交的原始交易資訊的數量,從而能夠實現隱藏匯出方帳戶在區塊鏈上的交易筆數。此外,透過對在提交時間間隔內接收到的原始交易資訊進行合併處理,還可以減少區塊鏈處理的交易資訊的數量,從而可以減少區塊鏈輸送量的負擔。
請參閱圖1和圖2。以下介紹本說明書實施例的一個場景示例。
在本場景示例中,所述匯出方設備可以預先在本機存放區有虛假業務資訊集合。所述虛假業務資訊集合可以包括至少一個虛假業務資訊。在所述虛假業務資訊集合中虛假業務資訊可以對應有匯入方帳戶標識和簽名資訊。其中,所述虛假業務資訊集合中的虛假業務資訊可以是由匯出方和匯入方提前約定好的。具體地,例如,匯出方可以提前產生虛假業務資訊併發送給匯入方。匯入方可以對虛假業務資訊進行簽名處理,得到虛假業務資訊的簽名資訊;可以將虛假業務資訊的簽名資訊回饋給匯出方。
在本場景示例中,所述匯出方伺服器可以將最近一次向區塊鏈提交交易資訊的時刻和提交時間間隔相加,得到提交時刻。這裡最近一次向區塊鏈提交交易資訊的時刻可以為提交虛假交易資訊的時刻,也可以為提交真實交易資訊的時刻。所述匯出方伺服器可以在所述提交時刻到達以後,對在所述提交時間間隔內接收到的至少一個原始交易資訊進行合併處理,得到至少一個合併交易資訊。
在本場景示例中,所述匯出方伺服器可以對所述至少一個合併交易資訊進行如下處理。
針對每個合併交易資訊中的匯入方帳戶標識,從所述虛假業務資訊集合中選取該匯入方帳戶標識對應的虛假業務資訊,作為該合併交易資訊中的虛假業務資訊。
對所述至少一個合併交易資訊中的合併交易金額進行加密處理。
對每個合併交易資訊進行簽名處理,得到簽名資訊;將該簽名資訊加入該合併交易資訊。
在本場景示例中,經過上述處理後,所述匯出方伺服器可以向所述區塊鏈提交所述至少一個合併交易資訊。
所述區塊鏈可以根據共識機制確定出共識區塊鏈節點。針對每個合併交易資訊,所述共識區塊鏈節點可以利用相關技術中的防雙花或防重放機制,驗證該交易是否已經執行過;如果已經執行過,可以拒絕該交易;如果未執行過,可以驗證該合併交易資訊中的簽名資訊是否正確;如果不正確,可以拒絕該交易;如果正確,可以根據該合併交易資訊中的合併交易金額更新匯出方帳戶的餘額和匯入方帳戶的餘額。
請參閱圖3。本說明書實施例提供一種基於區塊鏈的資料處理裝置。所述裝置可以包括以下單元。
計算單元20,用於根據基準時刻和提交時間間隔,計算提交時刻;
合併單元22,用於在所述提交時刻到達以後,對在所述提交時間間隔內接收到的至少一個原始交易資訊進行合併處理,得到至少一個合併交易資訊;
提交單元24,用於向所述區塊鏈提交所述至少一個合併交易資訊。
請參閱圖4。本說明書實施例還提供一種伺服器。所述伺服器可以包括儲存器和處理器。
在本實施例中,所述儲存器可以按任何適當的方式實現。例如,所述儲存器可以為唯讀記憶體、機械硬碟、固態硬碟、或USB記憶體等。所述儲存器可以用於儲存電腦指令。
在本實施例中,所述處理器可以按任何適當的方式實現。例如,處理器可以採取例如微處理器或處理器以及儲存可由該(微)處理器執行的電腦可讀程式碼(例如軟體或韌體)的電腦可讀媒體、邏輯閘、開關、專用積體電路(Application Specific Integrated Circuit,ASIC)、可程式設計邏輯控制器和嵌入微控制器的形式等等。所述處理器可以執行所述電腦指令實現以下步驟:根據基準時刻和提交時間間隔,計算提交時刻;在所述提交時刻到達以後,對在所述提交時間間隔內接收到的至少一個原始交易資訊進行合併處理,得到至少一個合併交易資訊;向所述區塊鏈提交所述至少一個合併交易資訊。
需要說明的是,本說明書中的各個實施例均採用遞進的方式描述,各個實施例之間相同或相似的部分互相參見即可,每個實施例重點說明的都是與其它實施例的不同之處。尤其,對於裝置實施例和伺服器實施例而言,由於其基本相似於方法實施例,所以描述的比較簡單,相關之處參見方法實施例的部分說明即可。
本領域技術人員在閱讀本說明書檔之後,可以無需創造性勞動想到將本說明書列舉的部分或全部實施例進行任意組合,這些組合也在本說明書公開和保護的範圍內。
在20世紀90年代,對於一個技術的改進可以很明顯地區分是硬體上的改進(例如,對二極體、電晶體、開關等電路結構的改進)還是軟體上的改進(對於方法流程的改進)。然而,隨著技術的發展,當今的很多方法流程的改進已經可以視為硬體電路結構的直接改進。設計人員幾乎都透過將改進的方法流程程式設計到硬體電路中來得到相應的硬體電路結構。因此,不能說一個方法流程的改進就不能用硬體實體模組來實現。例如,可程式設計邏輯裝置(Programmable Logic Device, PLD)(例如現場可程式設計閘陣列(Field Programmable Gate Array,FPGA))就是這樣一種積體電路,其邏輯功能由用戶對裝置程式設計來確定。由設計人員自行程式設計來把一個數位系統“整合”在一片PLD 上,而不需要請晶片製造廠商來設計和製作專用的積體電路晶片2。而且,如今,取代手工地製作積體電路晶片,這種程式設計也多半改用 “邏輯編譯器(logic compiler)”軟體來實現,它與程式開發撰寫時所用的軟體編譯器相類似,而要編譯之前的原始代碼也得用特定的程式設計語言來撰寫,此稱之為硬體描述語言(Hardware Description Language,HDL),而HDL也並非僅有一種,而是有許多種,如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等,目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)與Verilog2。本領域技術人員也應該清楚,只需要將方法流程用上述幾種硬體描述語言稍作邏輯程式設計並程式設計到積體電路中,就可以很容易得到實現該邏輯方法流程的硬體電路。
上述實施例闡明的系統、裝置、模組或單元,具體可以由電腦晶片或實體實現,或者由具有某種功能的產品來實現。一種典型的實現設備為電腦。具體的,電腦例如可以為個人電腦、膝上型電腦、行動電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任何設備的組合。
透過以上的實施方式的描述可知,本領域的技術人員可以清楚地瞭解到本說明書可借助軟體加必需的通用硬體平臺的方式來實現。基於這樣的理解,本說明書的技術方案本質上或者說對現有技術做出貢獻的部分可以以軟體產品的形式體現出來,該電腦軟體產品可以儲存在儲存媒體中,如ROM/RAM、磁碟、光碟等,包括若干指令用以使得一台電腦設備(可以是個人電腦,伺服器,或者網路設備等)執行本說明書各個實施例或者實施例的某些部分所述的方法。
本說明書可用於眾多通用或專用的電腦系統環境或配置中。例如:個人電腦、伺服器電腦、手持設備或可攜式設備、平板型設備、多處理器系統、基於微處理器的系統、機上盒、可程式設計的消費電子設備、網路PC、小型電腦、大型電腦、包括以上任何系統或設備的分散式運算環境等等。
本說明書可以在由電腦執行的電腦可執行指令的一般上下文中描述,例如程式模組。一般地,程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本說明書,在這些分散式運算環境中,由透過通信網路而被連接的遠端處理設備來執行任務。在分散式運算環境中,程式模組可以位於包括儲存設備在內的本地和遠端電腦儲存媒體中。
雖然透過實施例描繪了本說明書,本領域普通技術人員知道,本說明書有許多變形和變化而不脫離本說明書的精神,希望申請專利範圍包括這些變形和變化而不脫離本說明書的精神。The technical solutions in the embodiments of the present specification will be described clearly and completely in combination with the drawings in the embodiments of the present specification. Obviously, the described embodiments are only a part of the embodiments of the present specification, but not all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this specification. Please refer to Figure 1 and Figure 2. The embodiments of the present specification provide a blockchain-based data processing method. In this embodiment, the block chain (Block Chain) may be a chronological order, which organizes multiple block data in a chain structure, and uses cryptographic algorithms to ensure security, traceability, and A non-tamperable decentralized ledger. The blockchain may include a public blockchain, a joint blockchain (also called an alliance blockchain), and a private blockchain. The blockchain can be implemented based on a blockchain network. The blockchain network may include a peer-to-peer network and the like. The blockchain network may include multiple blockchain nodes. All blockchain nodes jointly maintain a unified blockchain ledger. In this embodiment, the data processing method uses the exporting server as an execution subject. The exporter server can join the blockchain network as a blockchain node. An exporter account may be registered in the exporter server. The exporter account may be an account of the exporter in the blockchain. The exporter server can communicate with the client. The user terminal may be, for example, a smart phone, a tablet electronic device, a portable computer, a personal digital assistant (PDA), or a smart wearable device. The data processing method may include the following steps. Step S10: Calculate the submission time according to the reference time and the submission time interval. In this embodiment, the reference time may include at least one of the following: the last time the merged transaction information was submitted to the blockchain, and the last time the false transaction information was submitted to the blockchain. The merged transaction information and the false transaction information will be introduced in detail in the subsequent process. In this embodiment, the value of the submission time interval can be flexibly set according to business needs. Specifically, the value of the submission time interval may be a fixed value; or, it may be divided into time periods according to actual business needs, and each time period is set to a fixed value; or, it may also be a random value. For example, the value of the submission time interval during the peak period of the transaction can be set to 0.1 seconds (you can also set a shorter or longer according to business needs); the value of the submission time interval during the low period of the transaction can be set to 1 minute (also can Set shorter or longer according to business needs). Of course, the value of the submission time interval may also be set according to a distribution function, so that the value of the submission time interval satisfies the distribution function. The distribution function may include, for example, an exponential distribution function and an Erlang distribution function. The expression of the exponential distribution function can be ; The formula for the Erlang distribution function can be . Here Represents the value of the submission interval; Represent the arrival rate; Represents the order of the Erlang distribution function. Wherein, the arrival rate may represent the number of events that occur in a unit of time. In some scenario examples, the arrival rate may specifically represent the number of transactions per unit time. In actual business, for example, the expected arrival rate D of the transaction (including real transaction and false transaction) at the submission interval can be set; the actual arrival rate E of the real transaction can be counted. Then, in the exponential distribution function and the Erlang distribution function . Of course, those skilled in the art should be able to understand that the above method of setting the value of the submission time interval according to the distribution function and the Erlang distribution function is only an example, and in fact, any other appropriate method may be used according to the distribution function and the Erlang distribution function. To set the value of the submission interval. In this embodiment, the exporting server may add the reference time and the submission time interval to obtain the submission time. Specifically, the remittance server may add the last time to submit transaction information to the blockchain and the submission time interval to obtain the submission time. Here, the latest time to submit transaction information to the blockchain may be the time to submit merged transaction information, or it may be the time to submit false transaction information. Step S12: After the submission time arrives, perform merge processing on the at least one original transaction information received within the submission time interval to obtain at least one merged transaction information. In this embodiment, the original transaction information may be transaction information from the user terminal. Specifically, within the submission time interval, the client may send transaction information to the exporter server, and the exporter server may receive the transaction information as original transaction information. Wherein, the original transaction information may include the account identification of the importer and its corresponding original transaction amount. The importer account identifier may be used to identify the importer account, for example, may be the name or address of the importer account. In an implementation manner of this embodiment, the original transaction information may further include real business information. The real business information may include, for example, order number, user information, and so on. Here, the original transaction information may directly include the real business information, or may also include a ciphertext of the real business information. Further, in this embodiment, the original transaction information may also include signature information of real business information. In this embodiment, the merged transaction information may include at least one importer account identifier and its corresponding merged transaction amount. In the merged transaction information, the merged transaction amount corresponding to the importer account ID can be calculated based on the original transaction amount corresponding to the importer account ID, for example, the sum of the original transaction amounts corresponding to the importer account ID . In one implementation of this embodiment, the original transaction information may include real business information. Accordingly, the merged transaction information may include real business information corresponding to at least one importer's account identifier. The real business information corresponding to the importer's account identifier in the merged transaction information can be determined based on the real business information corresponding to the importer's account identifier in the original transaction information. The merged transaction information here may directly include the real business information, or may also include a ciphertext of the real business information. Further, in this embodiment, the merged transaction information may also include signature information of real business information. In this embodiment, the amount of original transaction information received by the exporter server within the submission time interval may be one or more. When the number of received original transaction information is one, the exporter server may directly use the original transaction information as merged transaction information. When the number of received original transaction information is multiple, the exporter server may merge the multiple original transaction information into at least one merged transaction information. Specifically, the exporter server may merge the plurality of original transaction information into at least one merged transaction information in any manner. For example, the exporter server may merge the plurality of original transaction information into one merged transaction information. As another example, the exporter server may merge the original transaction information with the same importer account ID among the plurality of original transaction information into one merged transaction information. In an example of a scenario, the original transaction information received by the exporter server during the submission time interval may include five such as A1, A2, A3, B1, and B2. The five original transaction information can be shown in Table 1 below. Table 1 The exporter server may merge the five original transaction information into one merged transaction information. The merged transaction information obtained through the merger can be shown in Table 2 below. Table 2 In another scenario example, the original transaction information received by the exporter server within the submission time interval may include five such as A4, A5, A6, B3, and B4. The five original transaction information can be shown in Table 3 below. table 3 The exporter server may merge the five original transaction information into one merged transaction information. The merged transaction information obtained through the merger can be shown in Table 4 below. Table 4 Of course, the exporter server may also merge the five original transaction information into two merged transaction information. The merged transaction information obtained through the merger can be shown in the following Table 5 and Table 6 respectively. table 5 Table 6 Step S14: Submit the at least one merged transaction information to the blockchain. In this embodiment, the exporter device may submit the at least one merged transaction information to the blockchain; so that the consensus blockchain node in the blockchain can be based on the merged transaction in the merged transaction information The amount updates the balance of the remittance account and the balance of the remittance account. For example, the consolidated transaction amount is deducted from the balance of the remittance account; the consolidated transaction amount is charged to the balance of the remittance account. Wherein, the exporter device may submit the at least one merged transaction information to the blockchain at the same time, or may separately submit the at least one merged transaction information to the blockchain. In one implementation of this embodiment, before submitting the at least one merged transaction information to the blockchain, for each merged transaction information in the at least one merged transaction information, the exporter server Verification information can also be generated based on the merged transaction information; the verification information can be added to the merged transaction information. For example, the verification information may include signature information of merged transaction information. In one implementation of this embodiment, before submitting the at least one merged transaction information to the blockchain, the exporter server may also perform a merger transaction amount in the at least one merged transaction information Encryption processing. In this way, the hiding and secrecy of the combined transaction amount can be achieved. In an implementation of this embodiment, the exporter server may be provided with a collection of false business information. The set of false business information may include at least one false business information. The false business information may include, for example, a false order number, false user information, and so on. The false business information may be preset. In this way, before submitting the at least one merged transaction information to the blockchain, for each importer account identifier in each merged transaction information, the exporter server may also retrieve the false business information At least one false business information is selected from the collection as the corresponding false business information in the merged transaction information of the importer's account identifier. The number of false business information selected here can be flexibly set according to business needs, for example, 1, 2, or 5 false business information can be selected. In this way, by adding false business information in the merged transaction information, the amount of real business information in the merged transaction information can be hidden, and the number of transactions can be prevented from being leaked through the amount of the real business information in the merged transaction information. Further, in this embodiment, the false business information in the false business information set may correspond to signature information. Correspondingly, each merged transaction information may also include signature information corresponding to false business information. Further, in this embodiment, the false business information in the false business information set may correspond to the account identification of the importing party. In this way, for each importer account identifier in each merged transaction information, the exporter server may select the fake business information corresponding to the importer account identifier from the set of false business information as the merger False business information in transaction information. For example, the set of false business information may include false business information AXJ1_D, AXJ2_D, AXJ3_D, BXJ1_D, BXJ2_D. Among them, the false business information AXJ1_D, AXJ2_D, AXJ3_D can correspond to the importer account ID A; the false business information BXJ1_D, BXJ2_D can correspond to the importer account ID B. False business information AXJ1_D, AXJ2_D, AXJ3_D, BXJ1_D, BXJ2_D signature information can be AXJ1_QM, AXJ2_QM, AXJ3_QM, BXJ1_QM, BXJ2_QM. The merged transaction information obtained through the merger can be shown in Table 4 above. Then, after adding false business information, the merged transaction information can be shown in Table 7 below. Table 7 In an implementation manner of this embodiment, within the submission time interval, the client may not send transaction information to the exporter server. In this way, during the submission time interval, the exporter server does not receive the original transaction information. As described above, the exporter server can generate false transaction information. The false transaction information may include the account identification of the importing party and the corresponding transaction amount whose value is zero. Here, the exporter server may obtain the importer account identifier in any way as the importer account identifier in the false transaction information. For example, the exporter server may randomly select an account identifier in the blockchain as the importer account identifier in the false transaction information. The remittance server can encrypt the transaction amount with a value of zero in the false transaction information; it can submit the false transaction information to the blockchain. In this way, after the consensus blockchain node in the blockchain updates the balance of the exporter account and the balance of the importer account according to the transaction amount of zero, the balance of the exporter account and the balance of the importer account can be maintained constant. In this embodiment, the exporter server can merge the original transaction information received within the submission time interval, so that the third party cannot obtain the amount of the original transaction information actually submitted to the blockchain, so that Realize the number of transactions on the blockchain that hide the account of the exporter. In addition, by merging the original transaction information received within the submission time interval, the amount of transaction information processed by the blockchain can also be reduced, thereby reducing the burden of blockchain delivery. Please refer to Figure 1 and Figure 2. An example of a scenario of an embodiment of this specification is introduced below. In this scenario example, the exporter device may have a false collection of business information in the local storage area in advance. The set of false business information may include at least one false business information. The false business information in the false business information collection may correspond to the account identification and signature information of the importing party. Wherein, the false business information in the false business information collection may be agreed in advance by the exporter and the importer. Specifically, for example, the exporter may generate false business information in advance and send it to the importer. The importer can sign the false business information to obtain the signature information of the false business information; the signature information of the false business information can be fed back to the exporter. In this scenario example, the exporter server may add the time of the last transaction information submission to the blockchain and the submission time interval to obtain the submission time. Here, the last time to submit transaction information to the blockchain can be the time to submit false transaction information or the time to submit real transaction information. The exporter server may perform merge processing on at least one original transaction information received within the submission time interval after the submission time arrives to obtain at least one merged transaction information. In this scenario example, the exporter server may process the at least one merged transaction information as follows. For the importer account ID in each merged transaction information, the false business information corresponding to the importer account ID is selected from the set of false business information as the false business information in the merged transaction information. Encrypt the merged transaction amount in the at least one merged transaction information. Perform signature processing on each merged transaction information to obtain signature information; add the signed information to the merged transaction information. In this scenario example, after the above processing, the exporter server may submit the at least one merged transaction information to the blockchain. The blockchain can determine consensus blockchain nodes according to the consensus mechanism. For each merged transaction information, the consensus blockchain node can use the anti-double spending or anti-replay mechanism in the related technology to verify whether the transaction has been executed; if it has been executed, the transaction can be rejected; if it has not been executed After that, you can verify whether the signature information in the merged transaction information is correct; if it is incorrect, you can reject the transaction; if it is correct, you can update the balance of the exporter account and the importer account according to the merged transaction amount in the merged transaction information Balance. Please refer to Figure 3. Embodiments of this specification provide a data processing device based on blockchain. The device may include the following units. The calculation unit 20 is used to calculate the submission time according to the reference time and the submission time interval; the merging unit 22 is used to merge at least one original transaction information received within the submission time interval after the submission time arrives Processing to obtain at least one merged transaction information; a submission unit 24 is used to submit the at least one merged transaction information to the blockchain. Please refer to Figure 4. An embodiment of this specification also provides a server. The server may include a storage and a processor. In this embodiment, the storage can be implemented in any suitable manner. For example, the storage may be a read-only memory, a mechanical hard disk, a solid-state hard disk, or a USB memory. The memory can be used to store computer instructions. In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may adopt, for example, a microprocessor or a processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, a dedicated integrated body Circuit (Application Specific Integrated Circuit, ASIC), programmable logic controller and embedded microcontroller, etc. The processor may execute the computer instructions to implement the following steps: calculate the submission time according to the reference time and the submission time interval; after the submission time arrives, at least one original transaction information received within the submission time interval Perform merge processing to obtain at least one merged transaction information; submit the at least one merged transaction information to the blockchain. It should be noted that the embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Place. In particular, for the device embodiment and the server embodiment, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment. After reading this specification file, those skilled in the art can think of any combination of some or all of the embodiments listed in this specification without creative work, and these combinations are also within the scope of the disclosure and protection of this specification. In the 1990s, the improvement of a technology can be clearly distinguished from the improvement of hardware (for example, the improvement of the circuit structure of diodes, transistors, switches, etc.) or the improvement of software (for the process flow Improve). However, with the development of technology, the improvement of many methods and processes can be regarded as a direct improvement of the hardware circuit structure. Designers almost get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method and process cannot be achieved with hardware physical modules. For example, a programmable logic device (Programmable Logic Device, PLD) (such as a field programmable gate array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, and its logic function is determined by the user programming the device. It is up to the designer to program the “integration” of a digital system on a PLD without having to ask the chip manufacturer to design and manufacture a dedicated integrated circuit chip 2. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, this kind of programming is also mostly implemented with "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation must also be written in a specific programming language, which is called the hardware description language (Hardware Description Language, HDL), and HDL is not only one, but there are many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., Currently the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2. Those skilled in the art should also understand that it is easy to obtain the hardware circuit that implements the logic method flow by only slightly programming the method flow using the above hardware description languages and programming it into the integrated circuit. The system, device, module or unit explained in the above embodiments may be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a mobile phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, and a wearable device Or any combination of these devices. It can be known from the description of the above embodiments that those skilled in the art can clearly understand that this specification can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions of this specification can be embodied in the form of software products in essence or part of the contribution to the existing technology. The computer software products can be stored in storage media, such as ROM/RAM, disk, An optical disc, etc., includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of this specification or some parts of the embodiments. This manual can be used in many general or special computer system environments or configurations. Examples: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, small Computers, mainframe computers, distributed computing environments including any of the above systems or equipment, etc. This description can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification can also be practiced in distributed computing environments in which remote processing devices connected through a communication network perform tasks. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices. Although the description is described through the embodiments, those of ordinary skill in the art know that there are many variations and changes in the description without departing from the spirit of the description, and it is hoped that the scope of the patent application includes these variations and changes without departing from the spirit of the description.