這裡將詳細地對示例性實施例進行說明，其示例表示在圖式中。下面的描述涉及圖式時，除非另有表示，不同圖式中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本說明書相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本說明書的一些方面相一致的裝置和方法的例子。
在本說明書使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本說明書。在本說明書和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出項目的任何或所有可能組合。
應當理解，儘管在本說明書可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本說明書範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“回應於確定”。
在物流配送場景下，物流對象一次完整的物流生命週期可以包括攬件、轉運、派送等物流環節。物流配送的過程實際上就是將物流對象依次在各物流網點之間運輸傳遞的過程，並且通常每個物流網點需要由物流承運人參與。
在相關技術中，物流配送過程的安全性無法得到保證。例如，物流對象在運輸過程中被“調包”，即物流對象的發件方發送的是A物品，該A物品在運輸過程中被人調換為B物品，並且依然使用A物品的外包裝和物流單號等資訊。這種情況下，由於外包裝和物流單號依然是正確的，因此無法被識別，只能在物流對象的簽收方簽收時才可能被發現。如此，不僅對客戶造成的損失，而且由於無法追溯到底是哪個配送環節出現的問題，也無法確定最終的責任承運人；產生的損失通常都需要由物流平台來賠償。
本說明書中，為了方便描述將物流平台簡稱為系統，將物流網點稱為物流檢驗節點。該系統具體可以是指物流平台的伺服器、伺服器叢集或者雲端平台。
為了更好地保障客戶的權益，提高物流對象的安全性，同時也為了降低配送平台的風險，本說明書提供了一種基於區塊鏈的物流資訊溯源方案，通過將物流對象涉及到的各物流檢驗節點的物流承運人上傳的物流檢驗結果儲存到區塊鏈中；由於區塊鏈中儲存的資料存在不可竄改的特徵，因此，可以基於區塊鏈中儲存的物流檢驗結果追查導致物流對象出現異常的責任承運人。一方面通過準確定位與該物流異常對應的責任承運人，可以由定位的責任承運人承擔物流對象全部或部分損失，減少物流平台賠付比例；另一方面，對所有物流承運人起到警示作用，倒逼物流承運人履行保護物流對象安全的義務；綜合提升了物流對象在整個物流鏈路上的安全性。
本說明書提出了一種職能監督機制，是針對每個物流檢驗節點的物流承運人的一項硬性規定，必須要進行。具體地，對每個到達物流檢驗節點的物流對象均需要由物流承運人進行完整性檢查，檢查物流對象是否完整，並上傳物流檢驗結果。
在實現方式中，為了確保物流對象不會被“調包”，可以提供一種具有特殊紋路的指紋膠帶。通常，物流對象外包裝需要由封口膠帶封口。該指紋膠帶即是一種特製的封口膠帶。該指紋膠帶上的特殊紋路可以是一種身份標籤，該身份標籤即為物流對象唯一的對象標識。在實際應用中，物流承運人可以使用掃碼設備(例如掃碼槍、智慧型終端如手機等)掃描指紋膠帶上的身份標籤，從而解析出物流對象的對象標識。
如果解析出的對象標識屬於該物流對象，並且指紋膠帶完整沒有被拆開撕開，說明物流對象外包裝完整。如果解析出的對象標識不屬於該物流對象，即解析出的對象標識與原始的對象標識不一致，說明該原指紋膠帶被撕掉並用其它指紋膠帶重新封口，可以確定物流對象已經出現異常。如果解析出的對象標識屬於該物流對象，但出現其它異常情況，例如物流對象的外包裝出現破損、指紋膠帶明顯被撕開過，也可以確定物流對象已經出現異常。
一般的，該對象標識隨物流對象的物流生命週期開始或結束，例如當發件方下單物流對象的配送，或者當系統針對物流對象創建對應的物流訂單後即由系統分配一個唯一的對象標識並生效，在物流對象成功被簽收後對象標識失效。
在實現方式中，物流承運人可以在物流系統中進行實名認證，並獲得系統基於非對稱加密演算法產生的私鑰。該私鑰可以作為物流承運人的唯一標識，也可以對應物流承運人在系統中的資金帳戶。系統可以要求物流承運人簽署必要的協議，以確保物流承運人瞭解自身職責，需要承擔的義務、風險；以及保價相關的獎懲協議。
該保價可以是指物流對象的發件方提出的以一定保價資金保障物流對象安全的賠償機制。如果物流對象在配送過程中出現異常例如遺失、損壞、調包等導致簽收方無法正常收到原始物流對象的(即簽收失敗)，那麼基於保價機制，需要對發件方進行相應賠償。如果物流對象成功簽收，則發件方為保價提供的保價資金歸系統所有，並且保價協議在成功簽收後失效。
本說明書中，當系統分配給物流對象唯一的對象標識後，還可以相應在區塊鏈上提供一個對應該對象標識的對象帳戶地址，該對象帳戶地址用於寫入發件方提供的資源對象。在一實施例中，該資源對象可以是基於保價資金創建的。
同樣地，該物流承運人在實名認證後，也可以相應在區塊鏈上獲得一個對應私鑰的承運人帳戶地址，該承運人帳戶地址用於寫入分配到的資源對象。
在一實施例中，系統可以為對象標識創建一個對應的對象帳戶地址。即每個對象標識對應唯一的一個對象帳戶地址。
在另一實施例中，系統可以為對象標識關聯一個失效的對象帳戶地址，並初始化該失效的對象帳戶地址，以使該失效的對象帳戶地址處於有效狀態並且餘額為0(在發件方將保價資金注入後餘額即為注入的保價資金的金額)。該實施例與前不同的是，不同的對象標識可以對應相同的對象帳戶地址，但有效的對象帳戶地址僅對應一個對象標識。在對象標識失效後，關聯的對象帳戶地址執行相關操作後同樣會失效，以供其它有效的對象標識使用。
下面通過具體實施例並結合具體的應用場景對本說明書進行描述。
請參考圖1，圖1為本說明書一實施例提供的基於區塊鏈的物流資訊溯源方法的流程圖，該方法可以應用於前述系統，該方法可以包括以下步驟：
步驟110：獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
步驟120：將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
步驟130：在該物流對象發生物流異常時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的責任承運人。
在本說明書所描述的區塊鏈，具體可以包括私有鏈、共有鏈以及聯盟鏈等，在本說明書中不進行特別限定。
例如，在一個場景中，上述區塊鏈具體可以是由總部機構、分支機搆、代理機構、物流承運人設備等作為聯盟成員組成的一個聯盟鏈；該聯盟鏈的營運方可以依託於該聯盟鏈，來部署針對上述物流對象的物流資訊溯源業務；而以上所描述的作為聯盟成員的總部機構、分支機搆、代理機構、物流承運人設備都可以作為上述物流資訊溯源業務的一個業務節點。各個業務節點可以將自身所產生或者接收到的與上述物流對象相關的物流檢驗結果以交易的形式在聯盟鏈中進行發佈，並在該交易經過聯盟鏈中的共識節點的共識處理之後，在聯盟鏈中的分布式資料庫進行儲存，完成上述物流檢驗結果的“上鏈”存證。
其中，需要說明的是，在本說明書中所描述的交易(Transaction)，是指物流承運人通過區塊鏈的客戶端創建，並需要最終發佈至區塊鏈的分布式資料庫中的一筆資料。
區塊鏈中的交易，通常存在狹義的交易以及廣義的交易之分。狹義的交易是指用戶向區塊鏈發佈的一筆價值轉移；例如，在傳統的比特幣區塊鏈網路中，交易可以是用戶在區塊鏈中發起的一筆轉帳。而廣義的交易是指用戶向區塊鏈發佈的一筆具有業務意圖的業務資料；例如，營運方可以基於實際的業務需求搭建一個聯盟鏈，依託於聯盟鏈部署一些與價值轉移無關的其它類型的在線業務(比如，資訊溯源業務、資源對象分配業務、租房業務、車輛調度業務、保險理賠業務、信用服務、醫療服務等)，而在這類聯盟鏈中，交易可以是用戶在聯盟鏈中發佈的一筆具有業務意圖的業務消息或者業務請求。
上述客戶端，可以包括任意類型的以區塊鏈中儲存的底層業務資料作為資料支撐，來實現特定的業務功能的上層應用。
在一實施例中，該物流對象的外表面附著有基於該對象的對象標識產生的身份標籤；
該物流檢驗結果包括：該物流承運人掃描該身份標籤獲取到的該物流對象的對象標識；以及，該物流承運人對該物流對象的完整性檢驗結果。
上述完整性檢查可以包括物流承運人用手持設備掃描物流對象封口的指紋膠帶上的身份標籤，以確定該物流對象唯一的對象標識；用手持設備對物流對象進行拍照，確定物流對象的完整性。
在一實施例中，該完整性檢驗結果包括：該物流承運人對該物流對象進行三維拍照得到的三維圖片。通常三維圖片可以更為立體地全方位地瞭解物流對象是否完整。
系統在接收到物流承運人上傳的物流檢驗結果後，可以使用物流承運人認證的私鑰對物流檢驗結果進行加密後上傳區塊鏈存證。
在一實施例中，該身份標籤可以包括前述的封口膠帶。當然，也可以包括其他可以任意形式的載體，例如外包裝上黏貼的物流單，特製的外包裝等。
以下通過一個完整的物流配送過程加以說明：
一．攬件；攬件是指物流承運人收取發件方的物流對象。
物流承運人將物流對象的相關資訊上傳系統，以使系統創建該物流對象對應的物流訂單。該系統會分配該物流對象的對象標識，並將該對象標識推送給物流承運人。進而，物流承運人需要對物流對象進行上述的完整性檢查，並將物流檢驗結果上傳給系統。系統可以將該物流承運人該物流檢驗結果發佈至該區塊鏈進行儲存。
在一實施例中，系統可以接收發件方提供的針對物流對象完整性的確認資訊；將發件方提供的針對物流對象完整性的確認資訊發佈至該區塊鏈進行儲存。一般的，攬件環節中物流承運人除了需要上傳物流檢驗結果之外還需要上傳發件方的確定資訊。
在一種實現方式中，該確認資訊包括簽字圖片。具體地，發件人需要在物流承運人的手持設備上簽字，以確認物流對象是完整的、真實的、匹配的。待簽字確認後，物流承運人可以將簽字圖片連同對象標識、完整性檢驗結果作為物流檢驗結果上傳系統，由系統上鏈存證。當然，該確認資訊還可以是發件方在自己的移動終端上確認並上傳的。
二.轉運；轉運是指物流對象在各物流檢驗節點間運送的過程。
轉運過程中每個物流檢驗節點都需要對物流對象進行一次完整性檢查。具體地，當物流對象到達物流檢驗節點後，當前物流檢驗節點的物流承運人需要對物流對象進行上述的完整性檢查，並將物流檢驗結果上傳給系統。系統可以將該物流承運人上傳的物流檢驗結果發佈至該區塊鏈進行儲存。
三.簽收；簽收是物流配送過程的最後環節，將物流對象派送給簽收方，由簽收方簽收確認後結束物流配送。類似的，簽收也需要簽收人簽字確認。具體可以參考前述發件人簽字的示例。
簽收時，系統可以向物流對象的簽收方推送該物流對象的對象標識；簽收方通過掃描物流對象的身份標籤以解析出對象標識。為了便於區別，將物流對象分配到的對象標識稱為第一對象標識；將掃描身份標籤得到的對象標識稱為第二對象標識。通過將解析出的第二對象標識與推送的第一對象標識進行對比，可以確認物流對象的準確性。具體地，如果一致，說明該待簽收物流對象是發送方發送的原始物流對象，可以簽收確認。如果不一致，說明該待簽收物流對象存在異常，可能不是發送方發送的原始物流對象，此時簽收方可以向系統發起溯源請求。
相應地，該在該物流對象發生物流異常時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的物流檢驗節點以及物流承運人，具體包括：
接收該物流對象的簽收方在該物流對象發生物流異常時發起的溯源請求；
回應該溯源請求，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的物流檢驗節點以及物流承運人。
其中，該物流異常包括以下至少一種：
1、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識不一致；
2、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識一致，但物流對象的外包裝出現破損；
3、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識一致，指紋膠帶明顯被撕開過。
在一實施例中，該基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的責任承運人，具體包括：
將儲存在區塊鏈中的與各物流檢驗節點對應的物流檢驗結果，依次進行匹配；
如果各物流檢驗節點中任意兩個相鄰的物流檢驗節點對應的物流檢驗結果不匹配，將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人。
由於區塊鏈具有不可竄改的特性，通過查詢上鏈的每個物流承運人上傳的物流檢驗結果就可以追溯到最先檢驗出物流對象異常的責任承運人。
舉例說明，假設第一個物流承運人上傳的物流檢驗結果為正常，第二個物流承運人上傳的物流檢驗結果為正常，第三個物流承運人上傳的物流檢驗結果為異常，第四個物流承運人上傳的物流檢驗結果為異常，則可以記為正常(1)，正常(2)，異常(3)，異常(4)；
可以從後往前依次比對相鄰兩個物流檢驗結果：比對異常(4)與異常(3)，一致；然後比對異常(3)與正常(2)，不一致。此時，以最先檢驗出物流對象異常的物流承運人(示例中第三個物流承運人)為分界點，可以確定物流對象出現異常的時間點隻會由更早的物流承運人造成的(即示例中第一、第二物流承運人)，而之後的物流承運人(即示例中第四物流承運人)則可以排除嫌疑。並且，由於之前的檢驗結果均為正常，那麼說明只能是最先檢驗出物流對象異常的物流承運人之前的一個物流承運人(示例中第二個物流承運人)具有最大嫌疑。當然也不排除該最先檢驗出物流對象異常的物流承運人(示例中第三個物流承運人)。
在一種實現方式中，該將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人，具體包括：
在相鄰兩個物流檢驗結果不一致時，將其中上鏈順序在前的物流檢驗結果對應的物流承運人確定為與該物流異常對應的責任承運人。
該實施例是將最先檢驗出物流對象異常的物流承運人的前一個物流承運人確定為導致異常的責任承運人。
在一種實現方式中，該將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人，具體包括：
在相鄰兩個物流檢驗結果不一致時，將其中上鏈順序在後的物流檢驗結果對應的物流承運人確定為與該物流異常對應的責任承運人。
該實施例是將最早發佈檢驗結果為異常的物流承運人作為導致異常的責任承運人。
在一種實現方式中，該將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人，具體包括：
在相鄰兩個物流檢驗結果不一致時，將這兩個物流檢驗結果對應的物流承運人作為與該物流異常對應的責任承運人。
該實施例是在物流檢驗結果不一致時，將對應的2個物流承運人均作為與該物流異常對應的責任承運人。
在一實施例中，在確定了與該物流異常對應的責任承運人之後，就可以查詢該責任承運人所在的物流檢驗節點。也就是說，在該物流對象發生物流異常時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的物流檢驗節點以及責任承運人。
在一實施例中，該將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存，具體包括：
將該物流檢驗結果基於該物流承運人認證的私鑰進行簽名後發佈至該區塊鏈進行儲存。
由於區塊鏈技術具有全域性特徵，區塊鏈中每個節點均可以獲取全域資料，而物流檢驗結果一般會涉及敏感資訊(例如戶隱私資訊，姓名、地址、聯繫方式等)，如果採用明文上鏈，容易造成敏感資訊洩露；通過加密技術，以非明文的形式將資料上鏈，可以避免相關物流資訊洩露。
本說明書實施例，提供了一種基於區塊鏈的物流資訊溯源方案，通過將物流對象涉及到的各物流檢驗節點的物流承運人上傳的物流檢驗結果儲存到區塊鏈中；由於區塊鏈中儲存的資料存在不可竄改的特徵，因此，可以基於區塊鏈中儲存的物流檢驗結果追查導致物流對象出現異常的責任承運人。一方面通過準確定位與該物流異常對應的責任承運人，可以由定位的責任承運人承擔物流對象全部或部分損失，減少物流平台賠付比例；另一方面，對所有物流承運人起到警示作用，倒逼物流承運人履行保護物流對象安全的義務；綜合提升了物流對象在整個物流鏈路上的安全性。
相關物流行業中，物流承運人通常是計件收費，物流承運人與物流對象最終是否安全、完整並不相關；因此物流承運人對於確保物流對象的安全、完整的積極性不高。需要提供一個激勵機制，以調動物流承運人保障物流對象安全、完整的積極性。
如前所述，物流對象的發件方可以提出對物流對象的保價，並需要支付一定的保價資金。本說明書中，提出了一種利用該保價資金以提升物流承運人確保物流對象安全完整的積極性的方案。
下面通過具體實施例並結合具體的應用場景對本說明書進行描述。
請參考圖2，圖2為本說明書一實施例提供的基於區塊鏈的資源對象分配方法的流程圖，該方法可以應用於前述系統，該方法可以包括以下步驟：
步驟210：獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
步驟220：將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
步驟230：在該物流對象被確認簽收時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人；
步驟240：調用預設的智慧型合約，將預設的資源對象分配給所確定的物流承運人。
在本說明書所描述的區塊鏈，具體可以包括私有鏈、共有鏈以及聯盟鏈等，在本說明書中不進行特別限定。
例如，在一個場景中，上述區塊鏈具體可以是由總部機構、分支機搆、代理機構、物流承運人設備等作為聯盟成員組成的一個聯盟鏈；該聯盟鏈的營運方可以依託於該聯盟鏈，來部署針對上述物流對象的保價業務；而以上所描述的作為聯盟成員的總部機構、分支機搆、代理機構、物流承運人設備都可以作為上述保價業務的一個業務節點。各個業務節點可以將自身所產生或者接收到的與上述物流對象相關的物流檢驗結果以交易的形式在聯盟鏈中進行發佈，並在該交易經過聯盟鏈中的共識節點的共識處理之後，在聯盟鏈中的分布式資料庫進行儲存，完成上述物流檢驗結果的“上鏈”存證。
其中，需要說明的是，在本說明書中所描述的交易(Transaction)，是指物流承運人通過區塊鏈的客戶端創建，並需要最終發佈至區塊鏈的分布式資料庫中的一筆資料。
區塊鏈中的交易，通常存在狹義的交易以及廣義的交易之分。狹義的交易是指用戶向區塊鏈發佈的一筆價值轉移；例如，在傳統的比特幣區塊鏈網路中，交易可以是用戶在區塊鏈中發起的一筆轉帳。而廣義的交易是指用戶向區塊鏈發佈的一筆具有業務意圖的業務資料；例如，營運方可以基於實際的業務需求搭建一個聯盟鏈，依託於聯盟鏈部署一些與價值轉移無關的其它類型的在線業務(比如，資訊溯源業務、資源對象分配業務、租房業務、車輛調度業務、保險理賠業務、信用服務、醫療服務等)，而在這類聯盟鏈中，交易可以是用戶在聯盟鏈中發佈的一筆具有業務意圖的業務消息或者業務請求。
上述客戶端，可以包括任意類型的以區塊鏈中儲存的底層業務資料作為資料支撐，來實現特定的業務功能的上層應用。
在一實施例中，該物流對象的外表面附著有基於該對象的對象標識產生的身份標籤；
該物流檢驗結果包括：該物流承運人掃描該身份標籤獲取到的該物流對象的對象標識；以及，該物流承運人對該物流對象的完整性檢驗結果。
上述完整性檢查可以包括物流承運人用手持設備掃描物流對象封口的指紋膠帶上的身份標籤，以確定該物流對象唯一的對象標識；用手持設備對物流對象進行拍照，確定物流對象的完整性。
在一實施例中，該完整性檢驗結果包括：該物流承運人對該物流對象進行三維拍照得到的三維圖片。通常三維圖片可以更為立體地全方位地瞭解物流對象是否完整。
系統在接收到物流承運人上傳的物流檢驗結果後，可以使用物流承運人認證的私鑰對物流檢驗結果進行加密後上傳區塊鏈存證。
在一實施例中，該身份標籤可以包括前述的封口膠帶。當然，也可以包括其他可以任意形式的載體，例如外包裝上黏貼的物流單，特製的外包裝等。
以下通過一個完整的物流配送過程加以說明：
一．攬件；攬件是指物流承運人收取發件人的物流對象。
物流承運人將物流對象的訂單資訊上傳系統，以使系統創建該物流對象對應的物流訂單。該系統會分配該物流對象的對象標識，並將該對象標識推送給物流承運人。進而，物流承運人需要對物流對象進行上述的完整性檢查，並將物流檢驗結果上傳給系統。系統可以將該物流承運人該物流檢驗結果發佈至該區塊鏈進行儲存。
在一實施例中，系統可以接收發件方提供的針對物流對象完整性的確認資訊。一般的，攬件環節中物流承運人除了需要上傳物流檢驗結果之外還需要上傳發件方的確定資訊。
在一種實現方式中，該確認資訊包括簽字圖片。具體地，發件人需要在物流承運人的手持設備上簽字，以確認物流對象是完整的、真實的、匹配的。待簽字確認後，物流承運人可以將簽字圖片連同對象標識、完整性檢驗結果作為物流檢驗結果上傳系統，由系統上鏈存證。當然，該確認資訊還可以是發件方在自己的移動終端上確認並上傳的。
在一實施例中，該物流對象的資源對象是基於發件方提供的保價資金創建的；具體地可以是基於發件方提供的保價資金創建的資產對象。
該方法還包括：
獲取發件方提供的針對該物流對象的保價金額；
基於該保價金額創建該預設的資源對象；以及，
將該資源對象寫入在該區塊鏈中為該物流對象創建的帳戶對象，由該帳戶對象進行持有。
該實施例中，發件人同時還可以提出對物流對象的保價；並支付相應的保價資金。該保價資金可以根據物流對象的價值計算得到的。如前所述，在分配給物流對象的對象標識的同時，區塊鏈上可以分配對象標識對應的對象帳戶地址，因此該資源對象實際是寫入到區塊鏈中該物流對象的對象帳戶地址。
在一實施例中，該資源對象的數量可以等於或大於保價資金的金額。其中，在大於情況下，可以由物流公司補貼差額部分。
在一實施例中，該發件方提供的保價金額可以是由該物流承運人收取後，由物流承運人上傳至系統，再由系統將相應的資源對象寫入到區塊鏈中該物流對象的對象帳戶。也可以是由發件人直接將保價金額支付給系統，再由系統將相應的資源對象寫入到區塊鏈中該物流對象的對象帳戶。
二.轉運；轉運是指物流對象在各物流檢驗節點間運送的過程。
轉運過程中每個物流檢驗節點都需要對物流對象進行一次完整性檢查。具體地，當物流對象到達物流檢驗節點後，當前物流檢驗節點的物流承運人需要對物流對象進行上述的完整性檢查，並將物流檢驗結果上傳給系統。系統可以將該物流承運人上傳的物流檢驗結果發佈至該區塊鏈進行儲存。
三.簽收；簽收是物流配送過程的最後環節，將物流對象派送給簽收方，由簽收方簽收確認後結束物流配送。類似的，簽收也需要簽收人簽字確認。具體可以參考前述發件人簽字的示例。
簽收時，系統可以向物流對象的簽收方推送該物流對象的對象標識；簽收方通過掃描物流對象的身份標籤以解析出對象標識。為了便於區別，將物流對象分配到的對象標識稱為第一對象標識；將掃描身份標籤得到的對象標識稱為第二對象標識。通過將解析出的第二對象標識與推送的第一對象標識進行對比，可以確認物流對象的準確性。
以下介紹物流對象正常簽收後的分配方式：
在一實施例中，該在該物流對象被確認簽收時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人；
調用預設的智慧型合約，將預設的資源對象分配給所確定的物流承運人。
其中，該確認簽收條件包括：該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識一致。
對於正常簽收的情況下，可以每個物流對象涉及到的物流承運人均可以參與分配資源對象。通過上述實施例，在確定了可以分配資源對象的物流承運人之後，系統就可以實際分配資源對象了。
在一實施例中，該步驟240中將預設的資源對象分配給該物流對象的物流承運人，包括：
確定與該物流對象的物流承運人對應的資金分配比例，將預設的資源對象按照確定出的資金分配比例，分配給該物流承運人。
其中，智慧型合約(Smart contract)是一種旨在應用在可以部署在區塊鏈上的以資訊化方式傳播、驗證或執行合同的電腦協議。通過在智慧型合約中聲明業務邏輯可以實現執行相應操作。智慧型合約允許在沒有第三方的情況下進行可信交易。這些交易可追蹤且不可逆轉。智慧型合約能夠提供優於傳統合同方法的安全，並減少與合同相關的其他交易成本。
如前所述，區塊鏈中可以分配有物流對象的對象標識對應的對象帳戶地址，對象帳戶地址用於寫入發件人提供的保價資金；
相應地，將預設的資源對象分配給該物流承運人，包括：
將與該物流對象對應的帳戶對象持有的資源對象，轉移至在該區塊鏈中為該物流承運人創建的帳戶對象。
同樣地，區塊鏈中還可以分配有物流承運人的私鑰對應的物流承運人帳戶地址，物流承運人帳戶地址用於寫入分配到的資源對象。
該資源對象可以包括保價資金，即將保價資源分配給所確定的物流承運人。具體地，智慧型合約可以將對象帳戶地址中的保價資金轉移到所確定的物流承運人帳戶地址中。
至於如何分配資源對象或者保價資金，以保價資金為例例舉幾個示例：
在一實施例中，可以平分保價資金，即根據確定的物流承運人，等分保價資金；每個物流承運人均可以分配到相同的資金。
在一實施例中，該資金分配比例與該物流承運人承運的物流對象的歷史總數量成正比。也就是說系統可以根據物流承運人歷史完成的單量確定分配比例。
舉例說明，假設物流承運人有A和B；A歷史完成的單量為100件，B歷史完成的單量為50件；那麼可以確定A分配比例為2/3；B分配比例為1/3。即最終A可以分到2/3的保價資金，B可以分到1/3的保價資金。
以上介紹的是正常簽收的示例，以下介紹拒簽的示例：
在一實施例中，該在該物流對象被拒簽時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人中的責任承運人；
調用預設的智慧型合約，將預設的資源對象分配給該物流對象的物流承運人中，除該責任承運人以外的其他物流承運人。
其中，該物流異常包括以下至少一種：
1、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識不一致；
2、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識一致，但物流對象的外包裝出現破損；
3、該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識一致，指紋膠帶明顯被撕開過。
以第一對象標識與第二對象標識不一致為例加以說明，當不一致時說明該待簽收物流對象存在異常，可能不是發送方發送的原始物流對象，此時簽收方可以向系統發起溯源請求。需要說明的是，系統在接收到溯源請求後，除了可以執行前述實施例定位導致異常的物流承運人之外，還可以定位用於分配該物流對象的發件方提供的保價資金的物流承運人。
具體地，該基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定用於分配該資源對象的物流承運人，具體包括：
將儲存在區塊鏈中的與各物流檢驗節點對應的物流檢驗結果，依次進行匹配；
如果各物流檢驗節點中任意兩個相鄰的物流檢驗節點對應的物流檢驗結果不匹配，將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人。
該實施例，可以將預設的資源對象分配給該物流對象的物流承運人中，除該責任承運人以外的其他物流承運人，以保障他們工作，提升積極性。
在一實施例中，該將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存，具體包括：
將該物流檢驗結果基於該物流承運人認證的私鑰進行簽名後發佈至該區塊鏈進行儲存。
由於區塊鏈技術具有全域性特徵，區塊鏈中每個節點均可以獲取全域資料，而物流檢驗結果一般會涉及敏感資訊(例如戶隱私資訊，姓名、地址、聯繫方式等)，如果採用明文上鏈，容易造成敏感資訊洩露；通過加密技術，以非明文的形式將資料上鏈，可以避免相關物流資訊洩露。
本說明書實施例，提供了一種基於區塊鏈的資源對象分配方案，通過將物流對象涉及到的各物流檢驗節點的物流承運人上傳的物流檢驗結果儲存到區塊鏈中；由於區塊鏈中儲存的資料存在不可竄改的特徵，因此，可以基於區塊鏈中儲存的物流檢驗結果追溯經手過物流對象的物流承運人，從中確定用於分配該資源對象的物流承運人，並將資源對象分配給所確定的物流承運人。如此，將物流對象的安全、完整與物流承運人關聯，通過分配資源對象的方式調動物流承運人對於確保物流對象的安全、完整的積極性；進而提升物流對象在整個物流鏈路上的安全性。
與前述基於區塊鏈的物流資訊溯源方法實施例相對應，本說明書還提供了基於區塊鏈的物流資訊溯源裝置的實施例。該裝置實施例可以通過軟體實現，也可以通過硬體或者軟硬體結合的方式實現。以軟體實現為例，作為一個邏輯意義上的裝置，是通過其所在設備的處理器將非揮發性記憶體中對應的電腦業務程式指令讀取到內部記憶體中運行形成的。從硬體層面而言，如圖3所示，為本說明書基於區塊鏈的物流資訊溯源裝置所在設備的一種硬體結構圖，除了圖3所示的處理器、網路介面、內部記憶體以及非揮發性記憶體之外，實施例中裝置所在的設備通常根據基於區塊鏈的物流資訊溯源實際功能，還可以包括其他硬體，對此不再贅述。
請參見圖4，為本說明書一實施例提供的基於區塊鏈的物流資訊溯源裝置的模組圖，該裝置對應了圖1所示實施例，該裝置包括：
獲取單元310，獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
儲存單元320，將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
溯源單元330，在該物流對象發生物流異常時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的責任承運人。
可選的，該物流對象的外表面附著有基於該物流對象的對象標識產生的身份標籤；
該物流檢驗結果包括：該物流承運人掃描該身份標籤獲取到的該物流對象的對象標識；以及，該物流承運人對該物流對象的完整性檢驗結果。
可選的，該裝置還包括：
接收子單元，接收發件方提供的針對物流對象完整性的確認資訊；
儲存子單元，將該發件方提供的針對物流對象完整性的確認資訊發佈至該區塊鏈進行儲存。
可選的，該確認資訊包括簽字圖片。
可選的，該完整性檢驗結果包括：該物流承運人對該物流對象進行三維拍照得到的三維圖片。
可選的，該身份標籤包括封口膠帶。
可選的，該溯源單元330，具體包括：
接收子單元，接收該物流對象的簽收方在該物流對象發生物流異常時發起的溯源請求；
定位子單元，回應該溯源請求，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的物流檢驗節點以及物流承運人。
可選的，該物流異常包括：該簽收方通過掃描該物流對象的身份標籤所獲取到的對象標識與獲取的該物流對象的對象標識不一致。
可選的，該基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的責任承運人，具體包括：
將儲存在區塊鏈中的與各物流檢驗節點對應的物流檢驗結果，依次進行匹配；
如果各物流檢驗節點中任意兩個相鄰的物流檢驗節點對應的物流檢驗結果不匹配，將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人。
可選的，該區塊鏈為聯盟鏈。
與前述基於區塊鏈的資源對象分配方法實施例相對應，本說明書還提供了基於區塊鏈的資源對象分配裝置的實施例。該裝置實施例可以通過軟體實現，也可以通過硬體或者軟硬體結合的方式實現。以軟體實現為例，作為一個邏輯意義上的裝置，是通過其所在設備的處理器將非揮發性記憶體中對應的電腦業務程式指令讀取到內部記憶體中運行形成的。從硬體層面而言，如圖5所示，為本說明書基於區塊鏈的資源對象分配裝置所在設備的一種硬體結構圖，除了圖5所示的處理器、網路介面、內部記憶體以及非揮發性記憶體之外，實施例中裝置所在的設備通常根據基於區塊鏈的資源對象分配實際功能，還可以包括其他硬體，對此不再贅述。
請參見圖6，為本說明書一實施例提供的基於區塊鏈的資源對象分配裝置的模組圖，該裝置對應了圖2所示實施例，該裝置包括：
獲取單元410，獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
儲存單元420，將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
確定單元430，在該物流對象被確認簽收時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人；
分配單元440，調用預設的智慧型合約，將預設的資源對象分配給所確定的物流承運人。
可選的，該裝置還包括：
第二確定單元，在該物流對象被拒簽時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人中的責任承運人；
第二分配單元，調用預設的智慧型合約，將預設的資源對象分配給該物流對象的物流承運人中，除該責任承運人以外的其他物流承運人。
可選的，該基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定該物流對象的物流承運人中的責任承運人，具體包括：
將儲存在區塊鏈中的與各物流檢驗節點對應的物流檢驗結果，依次進行匹配；
如果各物流檢驗節點中任意兩個相鄰的物流檢驗節點對應的物流檢驗結果不匹配，將該兩個相鄰的物流檢驗節點對應的物流承運人，確定為與該物流異常對應的責任承運人。
可選的，將預設的資源對象分配給該物流對象的物流承運人，包括：
確定與該物流對象的物流承運人對應的資金分配比例，將預設的資源對象按照確定出的資金分配比例，分配給該物流承運人。
可選的，該資金分配比例與該物流承運人承運的物流對象的歷史總數量成正比。
可選的，將預設的資源對象分配給該物流承運人之前，還包括：
獲取發件方提供的針對該物流對象的保價金額；
基於該保價金額創建該預設的資源對象；以及，
將該資源對象寫入在該區塊鏈中為該物流對象創建的帳戶對象，由該帳戶對象進行持有；
將預設的資源對象分配給該物流承運人，包括：
將與該物流對象對應的帳戶對象持有的資源對象，轉移至在該區塊鏈中為該物流承運人創建的帳戶對象。
可選的，該物流對象的外表面附著有基於該物流對象的對象標識產生的身份標籤；
該物流檢驗結果包括：該物流承運人掃描該身份標籤獲取到的該物流對象的對象標識；以及，該物流承運人對該物流對象的完整性檢驗結果。
可選的，該完整性檢驗結果包括：該物流承運人對該物流對象進行三維拍照得到的三維圖片。
可選的，該區塊鏈為聯盟鏈。
可選的，該資源對象包括基於發件方提供的保價資源創建的資產對象。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、筆記型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放器、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
上述裝置中各個單元的功能和作用的實現過程具體詳見上述方法中對應步驟的實現過程，在此不再贅述。
對於裝置實施例而言，由於其基本對應於方法實施例，所以相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的單元可以是或者也可以不是物理上分開的，作為單元顯示的部件可以是或者也可以不是物理單元，即可以位於一個地方，或者也可以分佈到多個網路單元上。可以根據實際的需要選擇其中的部分或者全部模組來實現本說明書方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
以上圖4描述了基於區塊鏈的物流資訊溯源裝置的內部功能模組和結構示意，其實質上的執行主體可以為一種電子設備，包括：
處理器；
用於儲存處理器可執行指令的記憶體；
其中，該處理器被配置為：
獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
在該物流對象發生物流異常時，基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定與該物流異常對應的責任承運人。
以上圖6描述了基於區塊鏈的資源對象分配裝置的內部功能模組和結構示意，其實質上的執行主體可以為一種電子設備，包括：
處理器；
用於儲存處理器可執行指令的記憶體；
其中，該處理器被配置為：
獲取物流對象在各物流檢驗節點完成校驗後，由各物流檢驗節點的物流承運人上傳的物流檢驗結果；
將獲取到的該物流檢驗結果發佈至該區塊鏈進行儲存；
在該物流對象被簽收或拒簽時，獲取該物流對象的資源對象，以及基於儲存在該區塊鏈中的與該物流對象對應的物流檢驗結果，確定用於分配該資源對象的物流承運人；
調用資金分配的智慧型合約，將該資源對象分配給所確定的物流承運人。
在上述電子設備的實施例中，應理解，該處理器可以是中央處理單元(英文：Central Processing Unit，簡稱：CPU)，還可以是其他通用處理器、數位信號處理器(英文：Digital Signal Processor，簡稱：DSP)、專用積體電路(英文：Application Specific Integrated Circuit，簡稱：ASIC)等。通用處理器可以是微處理器或者該處理器也可以是任何常規的處理器等，而前述的記憶體可以是唯讀記憶體(英文：read-only memory，縮寫：ROM)、隨機存取記憶體(英文：random access memory，簡稱：RAM)、快閃記憶體、硬碟或者固態硬碟。結合本發明實施例所公開的方法的步驟可以直接體現為硬體處理器執行完成，或者用處理器中的硬體及軟體模組組合執行完成。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於電子設備實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
本領域技術人員在考慮說明書及實踐這裡公開的發明後，將容易想到本說明書的其它實施方案。本說明書旨在涵蓋本說明書的任何變型、用途或者適應性變化，這些變型、用途或者適應性變化遵循本說明書的一般性原理並包括本說明書未公開的本技術領域中的公知常識或慣用技術手段。說明書和實施例僅被視為示例性的，本說明書的真正範圍和精神由下面的申請專利範圍指出。
應當理解的是，本說明書並不局限於上面已經描述並在圖式中示出的精確結構，並且可以在不脫離其範圍進行各種修改和改變。本說明書的範圍僅由所附的申請專利範圍來限制。Exemplary embodiments will be described in detail here, examples of which are shown in the drawings. When the following description refers to drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with this specification. Rather, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the scope of the attached patent applications.
The terminology used in this specification is for the purpose of describing particular embodiments only, and is not intended to limit this specification. The singular forms "a", "said" and "the" used in this specification and the appended patent applications are also intended to include most forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "responsive to certainty".
In the logistics distribution scenario, a complete logistics life cycle of logistics objects can include logistics links such as package pickup, transshipment, and delivery. The process of logistics distribution is actually the process of transporting and transferring logistics objects among various logistics outlets in sequence, and usually each logistics outlet needs the participation of a logistics carrier.
In related technologies, the security of the logistics distribution process cannot be guaranteed. For example, the logistics object was "contracted" during the transportation process, that is, the sender of the logistics object sent the A item, which was replaced by the B item during the transportation process, and the A package and logistics were still used. Number and other information. In this case, because the outer packaging and logistics order numbers are still correct, they cannot be identified, and they can only be found when the signing party of the logistics object signs. In this way, not only the losses caused to the customer, but also because it is impossible to trace the problem of which distribution link occurred, it is also impossible to determine the ultimate responsible carrier; the resulting losses usually need to be compensated by the logistics platform.
In this specification, for the convenience of description, the logistics platform is simply referred to as a system, and the logistics outlets are referred to as logistics inspection nodes. The system may specifically refer to a server of a logistics platform, a server cluster, or a cloud platform.
In order to better protect the rights and interests of customers, improve the security of logistics objects, and at the same time, in order to reduce the risk of the distribution platform, this manual provides a blockchain-based logistics information traceability solution, through the logistics objects involved in the logistics inspection The logistics inspection results uploaded by the logistics carrier of the node are stored in the blockchain; since the data stored in the blockchain has the characteristics of non-tampering, the logistics object can be traced based on the logistics inspection results stored in the blockchain, resulting in abnormal logistics objects The responsible carrier. On the one hand, by accurately locating the responsible carrier corresponding to the logistics anomaly, the positioned responsible carrier can bear all or part of the loss of the logistics object and reduce the logistics platform compensation ratio; on the other hand, it plays a warning role for all logistics carriers. It forces logistics carriers to fulfill their obligations to protect the safety of logistics objects; it comprehensively improves the safety of logistics objects on the entire logistics link.
This manual proposes a functional supervision mechanism, which is a mandatory requirement for the logistics carrier of each logistics inspection node and must be carried out. Specifically, for each logistics object that reaches the logistics inspection node, the logistics carrier needs to perform an integrity check, check whether the logistics object is complete, and upload the logistics inspection result.
In the implementation mode, in order to ensure that the logistics object will not be "packaged", a fingerprint tape with special texture can be provided. Generally, the outer packaging of the logistics object needs to be sealed with sealing tape. The fingerprint tape is a special sealing tape. The special texture on the fingerprint tape may be an identity label, and the identity label is the unique object identifier of the logistics object. In practical applications, logistics carriers can use barcode scanning devices (such as barcode scanning guns, smart terminals such as mobile phones, etc.) to scan the identification labels on fingerprint tapes, so as to resolve the object identification of logistics objects.
If the parsed object ID belongs to the logistics object, and the fingerprint tape has not been disassembled and torn apart, it means that the logistics object is completely packaged. If the parsed object ID does not belong to the logistics object, that is, the parsed object ID is inconsistent with the original object ID, it means that the original fingerprint tape is torn off and resealed with other fingerprint tape, it can be determined that the logistics object has appeared abnormal. If the parsed object ID belongs to the logistics object, but other abnormal conditions occur, for example, the outer packaging of the logistics object is damaged, and the fingerprint tape is obviously torn, it can also be determined that the logistics object has occurred abnormally.
Generally, the object ID starts or ends with the logistics life cycle of the logistics object, for example, when the sender orders the delivery of the logistics object, or when the system creates a corresponding logistics order for the logistics object, the system assigns a unique object ID And take effect, after the logistics object is successfully signed for the object ID is invalid.
In the implementation mode, the logistics carrier can perform real-name authentication in the logistics system and obtain the private key generated by the system based on the asymmetric encryption algorithm. The private key can be used as the unique identifier of the logistics carrier, and can also correspond to the capital account of the logistics carrier in the system. The system can require the logistics carrier to sign the necessary agreements to ensure that the logistics carrier understands its responsibilities, obligations, risks, and reward-punishment agreements related to insured value.
The insured value may refer to a compensation mechanism proposed by the sender of the logistics object to guarantee the safety of the logistics object with a certain insured capital. If the logistics object has abnormalities in the delivery process, such as loss, damage, package adjustment, etc., which causes the signatory to fail to receive the original logistics object normally (that is, the signing fails), then based on the insured mechanism, the sender needs to be compensated accordingly. If the logistics object is successfully signed, the insured funds provided by the sender for the insured property will be owned by the system, and the insured agreement will become invalid after the successful signing.
In this specification, after the system assigns a unique object identifier to the logistics object, it can also provide an object account address corresponding to the object identifier on the blockchain, which is used to write the resource object provided by the sender. . In an embodiment, the resource object may be created based on insured funds.
Similarly, after real-name authentication, the logistics carrier can also obtain a carrier account address corresponding to the private key on the blockchain, and the carrier account address is used to write the allocated resource object.
In an embodiment, the system may create a corresponding object account address for the object identification. That is, each object ID corresponds to a unique object account address.
In another embodiment, the system may associate an invalid object account address for the object identification, and initialize the invalid object account address, so that the invalid object account address is in a valid state and the balance is 0 (the sender will After the insured capital is injected, the balance is the amount of insured capital injected). This embodiment differs from the previous one in that different object identifiers may correspond to the same object account address, but a valid object account address corresponds to only one object identifier. After the object ID is invalid, the associated object account address will also be invalid after performing related operations for other valid object IDs.
The following describes the specification through specific embodiments and specific application scenarios.
Please refer to FIG. 1. FIG. 1 is a flowchart of a blockchain-based logistics information traceability method provided by an embodiment of the present specification. The method can be applied to the foregoing system. The method can include the following steps:
Step 110: Obtain the logistics inspection result uploaded by the logistics carrier of each logistics inspection node after the logistics object has been verified at each logistics inspection node;
Step 120: Publish the obtained logistics inspection results to the blockchain for storage;
Step 130: When a logistics abnormality occurs in the logistics object, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, determine the responsible carrier corresponding to the logistics abnormality.
The blockchain described in this specification may specifically include private chains, shared chains, and alliance chains, which are not particularly limited in this specification.
For example, in a scenario, the above-mentioned blockchain may specifically be an alliance chain composed of headquarters organizations, branches, agencies, logistics carrier equipment, etc. as alliance members; the operator of the alliance chain may rely on the alliance chain To deploy the logistics information traceability service for the above logistics objects; the headquarters, branches, agencies, and logistics carrier equipment described above as members of the alliance can be used as a business node for the above logistics information traceability business. Each business node can publish the logistics inspection results related to the above logistics objects generated or received by itself in the form of a transaction in the alliance chain, and after the transaction has been processed by the consensus node of the consensus node in the alliance chain, the alliance The distributed database in the chain is stored to complete the "on-chain" deposit of the above logistics inspection results.
Among them, it should be noted that the transaction (Transaction) described in this specification refers to a piece of data that a logistics carrier creates through a client of the blockchain and needs to be finally released to the distributed database of the blockchain .
There are usually narrow transactions and broad transactions in the transactions in the blockchain. A narrow transaction refers to a value transfer issued by a user to the blockchain; for example, in the traditional Bitcoin blockchain network, a transaction can be a transfer initiated by the user in the blockchain. The generalized transaction refers to a piece of business data released by the user to the blockchain with business intent; for example, the operator can build an alliance chain based on actual business needs, relying on the alliance chain to deploy some other types of irrelevant value transfer Online services (for example, information traceability services, resource object allocation services, rental services, vehicle scheduling services, insurance claims services, credit services, medical services, etc.), and in this type of alliance chain, transactions can be issued by users in the alliance chain A business message or business request with business intent.
The above client may include any type of upper-layer application that uses the underlying business data stored in the blockchain as data support to implement specific business functions.
In an embodiment, an identification label generated based on the object identification of the object is attached to the outer surface of the logistics object;
The logistics inspection result includes: the object identification of the logistics object obtained by the logistics carrier scanning the identification tag; and the integrity inspection result of the logistics object by the logistics carrier.
The above integrity check may include that the logistics carrier scans the identification label on the fingerprint tape sealed by the logistics object with a handheld device to determine the unique object identification of the logistics object; photographs the logistics object with the handheld device to determine the integrity of the logistics object.
In an embodiment, the integrity check result includes: a three-dimensional picture obtained by the logistics carrier taking a three-dimensional photograph of the logistics object. Generally, the three-dimensional picture can be more comprehensive and comprehensive to understand whether the logistics object is complete.
After receiving the logistics inspection result uploaded by the logistics carrier, the system can use the private key authenticated by the logistics carrier to encrypt the logistics inspection result and upload it to the blockchain for certificate deposit.
In one embodiment, the identity tag may include the aforementioned sealing tape. Of course, it can also include other carriers that can be in any form, such as a logistics slip pasted on the outer packaging, a special outer packaging, and the like.
The following is explained through a complete logistics distribution process:
One. Package pickup; package pickup refers to the logistics object that the logistics carrier collects from the sender.
The logistics carrier uploads the relevant information of the logistics object to the system, so that the system creates the logistics order corresponding to the logistics object. The system will allocate the object identifier of the logistics object and push the object identifier to the logistics carrier. Furthermore, the logistics carrier needs to perform the aforementioned integrity check on the logistics object and upload the logistics inspection results to the system. The system can publish the logistics inspection results of the logistics carrier to the blockchain for storage.
In one embodiment, the system can receive confirmation information about the integrity of logistics objects provided by the sender; and publish the confirmation information about the integrity of logistics objects provided by the sender to the blockchain for storage. In general, in addition to the logistics inspection results, the logistics carrier also needs to upload the confirmation information of the sender.
In one implementation, the confirmation information includes a signature picture. Specifically, the sender needs to sign on the handheld device of the logistics carrier to confirm that the logistics objects are complete, true, and matched. After the signature is confirmed, the logistics carrier can upload the signature picture together with the object identification and the integrity inspection result as the logistics inspection result to the system, and the system will deposit the certificate on the chain. Of course, the confirmation information can also be confirmed and uploaded by the sender on his own mobile terminal.
2. Transshipment; transshipment refers to the process of transporting logistics objects between logistics inspection nodes.
During the transshipment process, each logistics inspection node needs to perform an integrity check on the logistics objects. Specifically, after the logistics object reaches the logistics inspection node, the logistics carrier of the current logistics inspection node needs to perform the above integrity check on the logistics object and upload the logistics inspection result to the system. The system can publish the logistics inspection results uploaded by the logistics carrier to the blockchain for storage.
3. Sign-off; sign-off is the last link in the logistics distribution process. The logistics object is sent to the sign-off party, and the sign-off party confirms the sign-off and ends the logistics delivery. Similarly, the signing requires the signatory's signature to confirm. For details, please refer to the aforementioned example of the sender's signature.
When signing, the system can push the object identification of the logistics object to the signing party of the logistics object; the signing party resolves the object identification by scanning the identification label of the logistics object. For the sake of distinction, the object identifier to which the logistics object is assigned is called the first object identifier; the object identifier obtained by scanning the identity label is called the second object identifier. By comparing the parsed second object identifier with the pushed first object identifier, the accuracy of the logistics object can be confirmed. Specifically, if they are consistent, it indicates that the logistics object to be signed is the original logistics object sent by the sender, which can be signed for confirmation. If they are inconsistent, it indicates that the logistics object to be signed has an exception, which may not be the original logistics object sent by the sender. At this time, the signer can initiate a traceability request to the system.
Accordingly, when a logistics abnormality occurs in the logistics object, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the logistics inspection node and the logistics carrier corresponding to the logistics anomaly are determined, specifically including:
The tracer request initiated by the signatory who received the logistics object when the logistics object has a logistics abnormality;
In response to the traceability request, based on the logistics inspection results corresponding to the logistics object stored in the blockchain, the logistics inspection node and the logistics carrier corresponding to the logistics anomaly are determined.
Among them, the logistics abnormalities include at least one of the following:
1. The object identification obtained by the signatory by scanning the identification label of the logistics object is inconsistent with the object identification of the acquired logistics object;
2. The object identification obtained by the signing party by scanning the identification label of the logistics object is consistent with the obtained object identification of the logistics object, but the outer packaging of the logistics object is damaged;
3. The object identification obtained by the signing party by scanning the identification label of the logistics object is consistent with the obtained object identification of the logistics object, and the fingerprint tape is obviously torn.
In one embodiment, the determination of the responsible carrier corresponding to the logistics anomaly based on the logistics inspection result corresponding to the logistics object stored in the blockchain includes:
Match the logistics inspection results corresponding to each logistics inspection node stored in the blockchain in sequence;
If the logistics inspection results corresponding to any two adjacent logistics inspection nodes in each logistics inspection node do not match, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics anomaly .
Due to the non-tamperable nature of the blockchain, by querying the logistics inspection results uploaded by each logistics carrier on the chain, it can be traced back to the responsible carrier that first detected the abnormality of the logistics object.
For example, suppose the logistics inspection result uploaded by the first logistics carrier is normal, the logistics inspection result uploaded by the second logistics carrier is normal, the logistics inspection result uploaded by the third logistics carrier is abnormal, and the fourth logistics carrier If the logistics inspection result uploaded by the carrier is abnormal, it can be recorded as normal (1), normal (2), abnormal (3), abnormal (4);
You can compare the results of two adjacent logistics tests in order from back to front: compare abnormality (4) and abnormality (3), consistent; then compare abnormality (3) and normal (2), inconsistent. At this time, taking the logistics carrier (the third logistics carrier in the example) that first detects the abnormality of the logistics object as the demarcation point, it can be determined that the time point at which the logistics object is abnormal will only be caused by the earlier logistics carrier ( That is, the first and second logistics carriers in the example), and subsequent logistics carriers (that is, the fourth logistics carrier in the example) can rule out the suspicion. In addition, since the previous inspection results are normal, it means that only the logistics carrier (the second logistics carrier in the example) before the logistics carrier that first detects the abnormal logistics object has the greatest suspicion. Of course, it should not be ruled out that the logistics carrier (the third logistics carrier in the example) that first detects the abnormal logistics object.
In an implementation manner, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics abnormality, which specifically includes:
When the results of two adjacent logistics inspections are inconsistent, the logistics carrier corresponding to the logistics inspection result with the highest winding order is determined as the responsible carrier corresponding to the logistics anomaly.
In this embodiment, the logistics carrier that is the first to check out the logistics carrier whose logistics object is abnormal is determined as the responsible carrier that caused the abnormality.
In an implementation manner, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics abnormality, which specifically includes:
When the results of the two adjacent logistics inspections are inconsistent, the logistics carrier corresponding to the logistics inspection result with the next highest chain order is determined as the responsible carrier corresponding to the logistics anomaly.
In this embodiment, the logistics carrier that issued the earliest inspection result as abnormal is the responsible carrier that caused the abnormality.
In an implementation manner, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics abnormality, which specifically includes:
When the adjacent two logistics inspection results are inconsistent, the logistics carrier corresponding to the two logistics inspection results is regarded as the responsible carrier corresponding to the logistics abnormality.
In this embodiment, when the logistics inspection results are inconsistent, the corresponding two logistics carriers are both regarded as responsible carriers corresponding to the logistics abnormality.
In an embodiment, after the responsible carrier corresponding to the logistics abnormality is determined, the logistics inspection node where the responsible carrier is located can be queried. In other words, when a logistics abnormality occurs in the logistics object, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the logistics inspection node and the responsible carrier corresponding to the logistics anomaly are determined.
In an embodiment, publishing the acquired logistics inspection results to the blockchain for storage includes:
The logistics inspection result is signed based on the private key authenticated by the logistics carrier and then released to the blockchain for storage.
Due to the global characteristics of blockchain technology, each node in the blockchain can obtain global data, and the results of logistics inspection generally involve sensitive information (such as household privacy information, name, address, contact information, etc.). If plain text is used On-chain, it is easy to cause the leakage of sensitive information; through encryption technology, the data is uploaded on the chain in the form of non-clear text, which can avoid the leakage of related logistics information.
The embodiment of this specification provides a blockchain-based logistics information tracing solution, by storing the logistics inspection results uploaded by the logistics carriers of each logistics inspection node involved in the logistics object into the blockchain; since the blockchain The stored data has the characteristics of non-tampering. Therefore, the responsible carrier that caused the abnormality of the logistics object can be traced based on the logistics inspection results stored in the blockchain. On the one hand, by accurately locating the responsible carrier corresponding to the logistics anomaly, the positioned responsible carrier can bear all or part of the loss of the logistics object and reduce the logistics platform compensation ratio; on the other hand, it plays a warning role for all logistics carriers. It forces logistics carriers to fulfill their obligations to protect the safety of logistics objects; it comprehensively improves the safety of logistics objects on the entire logistics link.
In the related logistics industry, logistics carriers usually charge by piece, and it is irrelevant whether the logistics carrier and the logistics object are ultimately safe and complete; therefore, the logistics carrier is not very enthusiastic about ensuring the safety and integrity of the logistics object. It is necessary to provide an incentive mechanism to adjust the animal flow carriers to ensure the safety and integrity of logistics objects.
As mentioned earlier, the sender of the logistics object can propose an insured value for the logistics object and need to pay a certain amount of insured funds. In this specification, a scheme is proposed to use the insured funds to enhance the enthusiasm of logistics carriers to ensure the safety and integrity of logistics objects.
The following describes the specification through specific embodiments and specific application scenarios.
Please refer to FIG. 2, which is a flowchart of a method for allocating resource objects based on a blockchain according to an embodiment of the present specification. The method may be applied to the foregoing system, and the method may include the following steps:
Step 210: Obtain the logistics inspection result uploaded by the logistics carrier of each logistics inspection node after the logistics object completes the inspection at each logistics inspection node;
Step 220: Publish the obtained logistics inspection results to the blockchain for storage;
Step 230: When the logistics object is confirmed and signed, determine the logistics carrier of the logistics object based on the logistics inspection result corresponding to the logistics object stored in the blockchain;
Step 240: Call the preset smart contract, and allocate the preset resource object to the determined logistics carrier.
The blockchain described in this specification may specifically include private chains, shared chains, and alliance chains, which are not particularly limited in this specification.
For example, in a scenario, the above-mentioned blockchain may specifically be an alliance chain composed of headquarters organizations, branches, agencies, logistics carrier equipment, etc. as alliance members; the operator of the alliance chain may rely on the alliance chain , To deploy the insured business for the above logistics objects; and the headquarters, branches, agencies, and logistics carrier equipment described above as members of the alliance can be used as a business node of the above insured business. Each business node can publish the logistics inspection results related to the above logistics objects generated or received by itself in the form of a transaction in the alliance chain, and after the transaction has been processed by the consensus node of the consensus node in the alliance chain, the alliance The distributed database in the chain is stored to complete the "on-chain" deposit of the above logistics inspection results.
Among them, it should be noted that the transaction (Transaction) described in this specification refers to a piece of data that a logistics carrier creates through a client of the blockchain and needs to be finally released to the distributed database of the blockchain .
There are usually narrow transactions and broad transactions in the transactions in the blockchain. A narrow transaction refers to a value transfer issued by a user to the blockchain; for example, in the traditional Bitcoin blockchain network, a transaction can be a transfer initiated by the user in the blockchain. The generalized transaction refers to a piece of business data released by the user to the blockchain with business intent; for example, the operator can build an alliance chain based on actual business needs, relying on the alliance chain to deploy some other types of irrelevant value transfer Online services (for example, information traceability services, resource object allocation services, rental services, vehicle scheduling services, insurance claims services, credit services, medical services, etc.), and in this type of alliance chain, transactions can be issued by users in the alliance chain A business message or business request with business intent.
The above client may include any type of upper-layer application that uses the underlying business data stored in the blockchain as data support to implement specific business functions.
In an embodiment, an identification label generated based on the object identification of the object is attached to the outer surface of the logistics object;
The logistics inspection result includes: the object identification of the logistics object obtained by the logistics carrier scanning the identification tag; and the integrity inspection result of the logistics object by the logistics carrier.
The above integrity check may include that the logistics carrier scans the identification label on the fingerprint tape sealed by the logistics object with a handheld device to determine the unique object identification of the logistics object; photographs the logistics object with the handheld device to determine the integrity of the logistics object.
In an embodiment, the integrity check result includes: a three-dimensional picture obtained by the logistics carrier taking a three-dimensional photograph of the logistics object. Generally, the three-dimensional picture can be more comprehensive and comprehensive to understand whether the logistics object is complete.
After receiving the logistics inspection result uploaded by the logistics carrier, the system can use the private key authenticated by the logistics carrier to encrypt the logistics inspection result and upload it to the blockchain for certificate deposit.
In one embodiment, the identity tag may include the aforementioned sealing tape. Of course, it can also include other carriers that can be in any form, such as a logistics slip pasted on the outer packaging, a special outer packaging, and the like.
The following is explained through a complete logistics distribution process:
One. Package pickup; package pickup refers to the logistics object that the logistics carrier collects from the sender.
The logistics carrier uploads the order information of the logistics object to the system, so that the system creates the logistics order corresponding to the logistics object. The system will allocate the object identifier of the logistics object and push the object identifier to the logistics carrier. Furthermore, the logistics carrier needs to perform the aforementioned integrity check on the logistics object and upload the logistics inspection results to the system. The system can publish the logistics inspection results of the logistics carrier to the blockchain for storage.
In one embodiment, the system may receive confirmation information provided by the sender regarding the integrity of the logistics object. In general, in addition to the logistics inspection results, the logistics carrier also needs to upload the confirmation information of the sender.
In one implementation, the confirmation information includes a signature picture. Specifically, the sender needs to sign on the handheld device of the logistics carrier to confirm that the logistics objects are complete, true, and matched. After the signature is confirmed, the logistics carrier can upload the signature picture together with the object identification and the integrity inspection result as the logistics inspection result to the system, and the system will deposit the certificate on the chain. Of course, the confirmation information can also be confirmed and uploaded by the sender on his own mobile terminal.
In an embodiment, the resource object of the logistics object is created based on the insured funds provided by the sender; specifically, it may be an asset object created based on the insured funds provided by the sender.
The method also includes:
Obtain the insured amount provided by the sender for the logistics object;
Create the preset resource object based on the insured amount; and,
Write the resource object to the account object created for the logistics object in the blockchain, and hold it by the account object.
In this embodiment, the sender can also propose an insured value to the logistics object; and pay the corresponding insured funds. The insured funds can be calculated based on the value of the logistics object. As mentioned above, while the object ID assigned to the logistics object can be assigned to the object account address corresponding to the object ID on the blockchain, the resource object is actually written to the object account address of the logistics object in the blockchain .
In an embodiment, the number of resource objects may be equal to or greater than the amount of insured funds. Among them, the logistics company can subsidize the difference if it is greater than the situation.
In an embodiment, the insured amount provided by the sender may be collected by the logistics carrier, uploaded by the logistics carrier to the system, and then the system will write the corresponding resource object to the logistics object in the blockchain Object account. It may also be that the sender directly pays the insured amount to the system, and then the system writes the corresponding resource object to the object account of the logistics object in the blockchain.
2. Transshipment; transshipment refers to the process of transporting logistics objects between logistics inspection nodes.
During the transshipment process, each logistics inspection node needs to perform an integrity check on the logistics objects. Specifically, after the logistics object reaches the logistics inspection node, the logistics carrier of the current logistics inspection node needs to perform the above integrity check on the logistics object and upload the logistics inspection result to the system. The system can publish the logistics inspection results uploaded by the logistics carrier to the blockchain for storage.
3. Sign-off; sign-off is the last link in the logistics distribution process. The logistics object is sent to the sign-off party, and the sign-off party confirms the sign-off and ends the logistics delivery. Similarly, the signing requires the signatory's signature to confirm. For details, please refer to the aforementioned example of the sender's signature.
When signing, the system can push the object identification of the logistics object to the signing party of the logistics object; the signing party resolves the object identification by scanning the identification label of the logistics object. For the sake of distinction, the object identifier to which the logistics object is assigned is called the first object identifier; the object identifier obtained by scanning the identity label is called the second object identifier. By comparing the parsed second object identifier with the pushed first object identifier, the accuracy of the logistics object can be confirmed.
The following describes the distribution method of logistics objects after normal sign-off:
In one embodiment, when the logistics object is confirmed and signed, the logistics carrier of the logistics object is determined based on the logistics inspection result corresponding to the logistics object stored in the blockchain;
Call the preset smart contract and assign the preset resource object to the determined logistics carrier.
Wherein, the confirmation signing condition includes: the signing object obtained by the signing party by scanning the identification label of the logistics object is consistent with the obtained object identification of the logistics object.
In the case of normal sign-off, the logistics carrier involved in each logistics object can participate in the allocation of resource objects. Through the above embodiment, after determining the logistics carrier that can allocate resource objects, the system can actually allocate resource objects.
In an embodiment, in step 240, the preset resource object is assigned to the logistics carrier of the logistics object, including:
Determine the capital allocation ratio corresponding to the logistics carrier of the logistics object, and allocate the preset resource object to the logistics carrier according to the determined capital allocation ratio.
Among them, the smart contract (Smart contract) is a computer protocol designed to be deployed on the blockchain to spread, verify or execute the contract in an information way. By declaring business logic in a smart contract, the corresponding operation can be performed. Smart contracts allow trusted transactions without third parties. These transactions are traceable and irreversible. Smart contracts can provide better security than traditional contract methods and reduce other transaction costs associated with contracts.
As mentioned above, the object account address corresponding to the object identifier of the logistics object can be allocated in the blockchain, and the object account address is used to write the insured funds provided by the sender;
Accordingly, the preset resource object is allocated to the logistics carrier, including:
The resource object held by the account object corresponding to the logistics object is transferred to the account object created for the logistics carrier in the blockchain.
Similarly, the logistics carrier account address corresponding to the logistics carrier's private key can also be allocated in the blockchain, and the logistics carrier account address is used to write the allocated resource object.
The resource object may include insured funds, that is, to allocate insured resources to the determined logistics carrier. Specifically, the smart contract may transfer the insured funds in the target account address to the determined logistics carrier account address.
As for how to allocate resource objects or insured funds, take insured funds as an example to give a few examples:
In one embodiment, the insured funds can be divided equally, that is, according to the determined logistics carrier, the insured funds can be divided equally; each logistics carrier can be allocated the same funds.
In one embodiment, the capital allocation ratio is proportional to the historical total number of logistics objects carried by the logistics carrier. That is to say, the system can determine the distribution ratio based on the unit quantity completed by the logistics carrier's history.
For example, suppose that the logistics carrier has A and B; the unit quantity completed by A in history is 100, and the unit quantity completed by B in history is 50; then it can be determined that the distribution ratio of A is 2/3; the distribution ratio of B is 1/3 . That is, in the end, A can be allocated to 2/3 of the insured funds, and B can be allocated to 1/3 of the insured funds.
The above describes an example of normal sign-off, and the following describes an example of refusal:
In one embodiment, when the logistics object is refused, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the responsible carrier of the logistics object of the logistics object is determined;
Call the preset smart contract to allocate the preset resource object to the logistics carrier of the logistics object, other than the responsible carrier, other logistics carriers.
Among them, the logistics abnormalities include at least one of the following:
1. The object identification obtained by the signatory by scanning the identification label of the logistics object is inconsistent with the object identification of the acquired logistics object;
2. The object identification obtained by the signing party by scanning the identification label of the logistics object is consistent with the obtained object identification of the logistics object, but the outer packaging of the logistics object is damaged;
3. The object identification obtained by the signing party by scanning the identification label of the logistics object is consistent with the obtained object identification of the logistics object, and the fingerprint tape is obviously torn.
Taking the inconsistency of the first object ID and the second object ID as an example to illustrate, when the inconsistency indicates that there is an abnormality in the logistics object to be signed, it may not be the original logistics object sent by the sender. It should be noted that, after receiving the traceability request, the system can locate the logistics carrier for allocating the insured funds provided by the sender of the logistics object in addition to performing the foregoing embodiment to locate the logistics carrier that caused the abnormality. .
Specifically, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the logistics carrier used to allocate the resource object is determined, specifically including:
Match the logistics inspection results corresponding to each logistics inspection node stored in the blockchain in sequence;
If the logistics inspection results corresponding to any two adjacent logistics inspection nodes in each logistics inspection node do not match, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics anomaly .
In this embodiment, the preset resource object can be allocated to the logistics carrier of the logistics object, other than the responsible carrier, to ensure their work and enhance their enthusiasm.
In an embodiment, publishing the acquired logistics inspection results to the blockchain for storage includes:
The logistics inspection result is signed based on the private key authenticated by the logistics carrier and then released to the blockchain for storage.
Due to the global characteristics of blockchain technology, each node in the blockchain can obtain global data, and the results of logistics inspection generally involve sensitive information (such as household privacy information, name, address, contact information, etc.). If plain text is used On-chain, it is easy to cause the leakage of sensitive information; through encryption technology, the data is uploaded on the chain in the form of non-clear text, which can avoid the leakage of related logistics information.
The embodiment of this specification provides a blockchain-based resource object allocation scheme, by storing the logistics inspection results uploaded by the logistics carrier of each logistics inspection node involved in the logistics object into the blockchain; since the blockchain The stored data has the characteristics of non-tampering. Therefore, based on the logistics inspection results stored in the blockchain, the logistics carrier that has handled the logistics object can be traced back, from which the logistics carrier used to allocate the resource object can be determined and the resource object can be allocated. To the identified logistics carrier. In this way, the safety and integrity of the logistics objects are associated with the logistics carrier, and the animal flow carrier is adjusted to ensure the safety and integrity of the logistics object by allocating resource objects; thereby improving the safety of the logistics object on the entire logistics link.
Corresponding to the foregoing embodiment of the blockchain-based logistics information tracing method embodiment, this specification also provides an embodiment of the blockchain-based logistics information tracing device. The device embodiment may be implemented by software, or by hardware or a combination of hardware and software. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer business program instructions in the non-volatile memory into the internal memory through the processor of the device where it is located. From the hardware level, as shown in Figure 3, it is a hardware structure diagram of the equipment where the blockchain-based logistics information traceability device is located in this specification, except for the processor, network interface, and internal memory shown in Figure 3 In addition to the non-volatile memory, the device where the device is located in the embodiment usually traces the actual function of the logistics information based on the blockchain, and may also include other hardware, which will not be repeated here.
Please refer to FIG. 4, which is a module diagram of a blockchain-based logistics information tracing device provided by an embodiment of the present specification. The device corresponds to the embodiment shown in FIG. 1. The device includes:
The obtaining unit 310 obtains the logistics inspection result uploaded by the logistics carrier of each logistics inspection node after the logistics objects are verified at each logistics inspection node;
The storage unit 320 publishes the obtained logistics inspection result to the blockchain for storage;
The traceability unit 330, when a logistics abnormality occurs in the logistics object, determines the responsible carrier corresponding to the logistics abnormality based on the logistics inspection result corresponding to the logistics object stored in the blockchain.
Optionally, an identity label generated based on the object identification of the logistics object is attached to the outer surface of the logistics object;
The logistics inspection result includes: the object identification of the logistics object obtained by the logistics carrier scanning the identification tag; and the integrity inspection result of the logistics object by the logistics carrier.
Optionally, the device also includes:
Receiving subunit, receiving confirmation information about the integrity of logistics objects provided by the sender;
The storage subunit publishes the confirmation information on the integrity of the logistics object provided by the sender to the blockchain for storage.
Optionally, the confirmation information includes a signature picture.
Optionally, the integrity check result includes: a three-dimensional picture obtained by the logistics carrier taking a three-dimensional photograph of the logistics object.
Optionally, the identification label includes sealing tape.
Optionally, the source tracing unit 330 specifically includes:
Receiving subunit, receiving the traceability request initiated by the signatory of the logistics object when the logistics object has a logistics abnormality;
The positioning subunit responds to the source tracing request, and determines the logistics inspection node and the logistics carrier corresponding to the logistics anomaly based on the logistics inspection result corresponding to the logistics object stored in the blockchain.
Optionally, the logistics abnormality includes: the object identifier obtained by the signing party by scanning the identity tag of the logistics object is inconsistent with the acquired object identifier of the logistics object.
Optionally, the determination of the responsible carrier corresponding to the logistics anomaly based on the logistics inspection result corresponding to the logistics object stored in the blockchain includes:
Match the logistics inspection results corresponding to each logistics inspection node stored in the blockchain in sequence;
If the logistics inspection results corresponding to any two adjacent logistics inspection nodes in each logistics inspection node do not match, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics anomaly .
Optionally, the blockchain is an alliance chain.
Corresponding to the foregoing embodiment of the method for allocating resource objects based on the blockchain, this specification also provides an embodiment of the device for allocating resource objects based on the blockchain. The device embodiment may be implemented by software, or by hardware or a combination of hardware and software. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer business program instructions in the non-volatile memory into the internal memory through the processor of the device where it is located. From the hardware level, as shown in Figure 5, this is a hardware structure diagram of the device where the resource object allocation device based on the blockchain is located, except for the processor, network interface, and internal memory shown in Figure 5. In addition to the non-volatile memory, the device where the device is located in the embodiment usually allocates actual functions according to the resource objects based on the blockchain, and may also include other hardware, which will not be repeated here.
Please refer to FIG. 6, which is a module diagram of a blockchain-based resource object allocation device according to an embodiment of the present specification. The device corresponds to the embodiment shown in FIG. 2. The device includes:
The obtaining unit 410 obtains the logistics inspection result uploaded by the logistics carrier of each logistics inspection node after the logistics objects have been verified at each logistics inspection node;
The storage unit 420 publishes the acquired logistics inspection results to the blockchain for storage;
The determining unit 430 determines the logistics carrier of the logistics object based on the logistics inspection result corresponding to the logistics object stored in the blockchain when the logistics object is confirmed and signed;
The allocation unit 440 calls the preset smart contract to allocate the preset resource object to the determined logistics carrier.
Optionally, the device also includes:
The second determination unit determines the responsible carrier of the logistics object of the logistics object based on the logistics inspection result corresponding to the logistics object stored in the blockchain when the logistics object is rejected;
The second allocation unit invokes the preset smart contract to allocate the preset resource object to the logistics carriers of the logistics object, other than the responsible carrier.
Optionally, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the responsible carrier among the logistics carriers of the logistics object is determined, specifically including:
Match the logistics inspection results corresponding to each logistics inspection node stored in the blockchain in sequence;
If the logistics inspection results corresponding to any two adjacent logistics inspection nodes in each logistics inspection node do not match, the logistics carrier corresponding to the two adjacent logistics inspection nodes is determined to be the responsible carrier corresponding to the logistics anomaly .
Optionally, the preset resource object is allocated to the logistics carrier of the logistics object, including:
Determine the capital allocation ratio corresponding to the logistics carrier of the logistics object, and allocate the preset resource object to the logistics carrier according to the determined capital allocation ratio.
Optionally, the capital allocation ratio is directly proportional to the historical total number of logistics objects carried by the logistics carrier.
Optionally, before assigning the preset resource object to the logistics carrier, it also includes:
Obtain the insured amount provided by the sender for the logistics object;
Create the preset resource object based on the insured amount; and,
Write the resource object to the account object created for the logistics object in the blockchain, and hold it by the account object;
Assign preset resource objects to the logistics carrier, including:
The resource object held by the account object corresponding to the logistics object is transferred to the account object created for the logistics carrier in the blockchain.
Optionally, an identity label generated based on the object identification of the logistics object is attached to the outer surface of the logistics object;
The logistics inspection result includes: the object identification of the logistics object obtained by the logistics carrier scanning the identification tag; and the integrity inspection result of the logistics object by the logistics carrier.
Optionally, the integrity check result includes: a three-dimensional picture obtained by the logistics carrier taking a three-dimensional photograph of the logistics object.
Optionally, the blockchain is an alliance chain.
Optionally, the resource object includes an asset object created based on the insured resource provided by the sender.
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, and the specific form of the computer may be a personal computer, a notebook computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet, wearable device, or any combination of these devices.
For the implementation process of the functions and functions of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details.
For the device embodiment, since it basically corresponds to the method embodiment, the relevant part can be referred to the description of the method embodiment. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement without paying creative labor.
Figure 4 above describes the internal functional modules and structural schematics of the blockchain-based logistics information traceability device. The actual execution subject may be an electronic device, including:
processor;
Memory for storing processor executable instructions;
Among them, the processor is configured as:
Obtain the logistics inspection results uploaded by the logistics carrier of each logistics inspection node after the logistics objects have completed the inspection at each logistics inspection node;
Publish the obtained logistics inspection results to the blockchain for storage;
When a logistics abnormality occurs in the logistics object, based on the logistics inspection result corresponding to the logistics object stored in the blockchain, the responsible carrier corresponding to the logistics anomaly is determined.
The above FIG. 6 describes the internal functional modules and structural schematics of the resource object allocation device based on the blockchain. The actual execution subject may be an electronic device, including:
processor;
Memory for storing processor executable instructions;
Among them, the processor is configured as:
Obtain the logistics inspection results uploaded by the logistics carrier of each logistics inspection node after the logistics objects have completed the inspection at each logistics inspection node;
Publish the obtained logistics inspection results to the blockchain for storage;
When the logistics object is signed or rejected, obtain the resource object of the logistics object, and determine the logistics carrier used to allocate the resource object based on the logistics inspection result corresponding to the logistics object stored in the blockchain;
Call the smart contract for fund allocation to allocate the resource object to the determined logistics carrier.
In the above embodiments of the electronic device, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor) , Referred to as: DSP), dedicated integrated circuit (English: Application Specific Integrated Circuit, referred to as: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc., and the aforementioned memory may be a read-only memory (English: read-only memory, abbreviation: ROM), random access memory Body (English: random access memory, RAM for short), flash memory, hard drive or solid state drive. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
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, and each embodiment focuses on the differences from other embodiments. In particular, for the embodiment of the electronic device, since it is 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 considering the description and practicing the invention disclosed herein, those skilled in the art will easily think of other embodiments of the description. This specification is intended to cover any variations, uses, or adaptive changes of this specification. These variations, uses, or adaptive changes follow the general principles of this specification and include common general knowledge or common technical means in the technical field not disclosed in this specification. . The description and examples are only to be considered exemplary, and the true scope and spirit of this description are indicated by the following patent application.
It should be understood that this specification is not limited to the precise structure that has been described above and shown in the drawings, and that various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the scope of the attached patent application.
