有鑑於此，本說明書一個或多個實施例提供一種物聯網設備的登錄方法和裝置，以實現物聯網設備更加快速和安全的登錄。
In view of this, one or more embodiments of this specification provide a method and an apparatus for logging in an Internet of Things device, so as to realize a faster and safer login of the Internet of Things device.
具體地，本說明書一個或多個實施例是透過如下技術方案實現的：
Specifically, one or more embodiments of this specification are implemented through the following technical solutions:
第一方面，提供一種物聯網設備的登錄方法，所述方法包括：在檢測到登錄觸發時，獲取設備操作使用者輸入的驗證要素；對所述驗證要素進行本地校驗；若校驗通過，啟用登錄時的離線功能，並將所述驗證要素發送至物聯網伺服器進行二次校驗；當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，以開始與所述物聯網伺服器之間的業務通訊。
In a first aspect, a method for logging in an Internet of Things device is provided. The method includes: acquiring a verification element input by a device operation user when a login trigger is detected; performing local verification on the verification element; if the verification passes, Enable the offline function during login, and send the verification element to the IoT server for secondary verification; when the secondary verification of the IoT server passes, log in to the IoT server to start Business communication between the Internet of Things servers.
第二方面，提供了一種物聯網設備的登錄方法，所述方法包括：接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，以開始與所述物聯網設備進行業務通訊。
In a second aspect, a method for logging in an IoT device is provided. The method includes: receiving and storing a verification element sent by the IoT device, the verification element being set by a device operation user corresponding to the IoT device; When the secondary verification request sent by the IoT device is compared with the verification element carried in the secondary verification request and the stored verification element, if the two are the same, the secondary verification passes and the The Internet of Things device is in a login state to start business communication with the Internet of Things device.
第三方面，提供一種物聯網設備的登錄裝置，所述裝置包括：要素接收模組，用於在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；本地校驗模組，用於對所述驗證要素進行本地校驗；校驗結果模組，用於在所述本地校驗模組校驗通過時，將所述驗證要素發送至物聯網伺服器進行二次校驗；連接處理模組，用於當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊。
第四方面，提供一種物聯網設備的登錄裝置，所述裝置包括：
要素儲存模組，用於接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；
校驗處理模組，用於在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
第五方面，提供一種物聯網設備，所述設備包括記憶體、處理器，以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器執行指令時實現以下步驟：
在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；
對所述驗證要素進行本地校驗；
若校驗通過，啟用登錄時的離線功能，並將所述驗證要素發送至物聯網伺服器進行二次校驗；
當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊。
第六方面，提供一種物聯網伺服器，所述設備包括記憶體、處理器，以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器執行指令時實現以下步驟：
接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；
在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
第七方面，提供一種物聯網系統，所述系統包括：物聯網設備和物聯網伺服器；
所述物聯網設備，用於：獲取所述設備操作使用者設置的所述驗證要素，儲存所述驗證要素，並將所述驗證要素發送至物聯網伺服器儲存；在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；對所述驗證要素進行本地校驗；若校驗通過，啟用登錄時的離線功能，並將所述驗證要素發送至物聯網伺服器進行二次校驗；當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊；
所述物聯網伺服器，用於：接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；並在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
本說明書一個或多個實施例的物聯網設備的登錄方法和裝置，透過使用“雙重校驗”的方式，一方面的校驗是在物聯網設備的本地校驗，另一方面的校驗是在物聯網伺服器側的二次校驗，這種雙重校驗方式，能夠很好的保證“使用者和綁定設備之間對應關係的正確”，提高了IOT設備的安全性，保障IOT設備是由其真正的歸屬使用者在操作；並且，透過在本地校驗通過後，就預先啟用離線功能，使得物聯網設備更加快速的登錄。In a third aspect, a login device for an Internet of Things device is provided. The device includes: an element receiving module for acquiring a verification element of a user operating the device when a login trigger is detected; a local verification module for The verification element performs local verification; the verification result module is used to send the verification element to the Internet of Things server for secondary verification when the local verification module passes the verification; connection processing mode The group is used to log in to the IoT server and start business communication with the IoT server when the IoT server passes the second verification.
According to a fourth aspect, an apparatus for logging in an Internet of Things device is provided. The apparatus includes:
An element storage module for receiving and storing verification elements sent by the Internet of Things device, the verification elements being set by a device operation user corresponding to the Internet of Things device;
The verification processing module is used to compare the verification element carried in the secondary verification request with the stored verification element when receiving the secondary verification request sent by the Internet of Things device, if the two are the same , The second verification passes, the Internet of Things device is set to the login state, and business communication with the Internet of Things device is started.
According to a fifth aspect, an Internet of Things device is provided. The device includes a memory, a processor, and computer instructions stored on the memory and executable on the processor. When the processor executes the instructions, the following steps are implemented:
When the login trigger is detected, obtain the verification elements of the device operation user;
Perform local verification on the verification element;
If the verification passes, the offline function at the time of login is enabled, and the verification element is sent to the Internet of Things server for secondary verification;
When the second verification of the Internet of Things server passes, the Internet of Things server is registered, and business communication with the Internet of Things server is started.
According to a sixth aspect, an IoT server is provided. The device includes a memory, a processor, and computer instructions stored on the memory and executable on the processor. When the processor executes the instructions, the following steps are implemented:
Receiving and storing verification elements sent by the Internet of Things device, the verification elements being set by a device operation user corresponding to the Internet of Things device;
When receiving the secondary verification request sent by the Internet of Things device, compare the verification element carried in the secondary verification request with the stored verification element, if the two are the same, the secondary verification passes, The Internet of Things device is set to a login state, and business communication with the Internet of Things device is started.
In a seventh aspect, an IoT system is provided. The system includes: an IoT device and an IoT server;
The IoT device is used to: obtain the verification element set by the user of the device operation, store the verification element, and send the verification element to the IoT server for storage; when a login trigger is detected, Obtain the verification elements of the equipment operation user; perform local verification on the verification elements; if the verification passes, enable the offline function at login, and send the verification elements to the Internet of Things server for secondary verification; When the second verification of the IoT server passes, log in to the IoT server and start business communication with the IoT server;
The IoT server is used to: receive and store the verification element sent by the IoT device, the verification element is set by a device operation user corresponding to the IoT device; During the second verification request, compare the verification element carried in the second verification request with the stored verification element, if the two are the same, the second verification passes, and the Internet of Things device is set to the login state, And start business communication with the Internet of Things equipment.
In the method and device for logging in an IoT device according to one or more embodiments of this specification, by using the "double verification" method, the verification on the one hand is local verification on the IoT device, and the verification on the other hand is The secondary verification on the server side of the Internet of Things, this double verification method can well guarantee "the correct correspondence between the user and the bound device", improve the security of the IOT device, and protect the IOT device It is operated by its real attribution user; and, after passing the local verification, the offline function is enabled in advance, so that the IoT device can log in more quickly.
為了使本技術領域的人員更好地理解本說明書一個或多個實施例中的技術方案，下面將結合本說明書一個或多個實施例中的圖式，對本說明書一個或多個實施例中的技術方案進行清楚、完整地描述，顯然，所描述的實施例僅僅是本說明書一部分實施例，而不是全部的實施例。基於本說明書一個或多個實施例，本領域普通技術人員在沒有作出創造性勞動前提下所獲得的所有其他實施例，都應當屬於本公開保護的範圍。
在物聯網系統中，可以由物聯網伺服器來對物聯網設備進行操作控制，如果一個使用者想要使用一個物聯網設備，可以向設備對應的物聯網伺服器申請對該設備的操作許可權。可以參見圖1示例的物聯網系統，如圖1所示，該系統可以包括：物聯網設備11、物聯網設備12、物聯網設備1n等設備，這些設備的操作控制可以都由物聯網伺服器21管理。
如果一個使用者22想要使用其中一個物聯網設備11，他可以向物聯網伺服器21申請對這個設備的使用授權。例如，當物聯網伺服器21授權使用者22使用物聯網設備11之後，相當於建立了物聯網設備11與使用者22之間的綁定關係，其他使用者可以不再具有對該設備的操作使用權限。而假如物聯網伺服器21解除了物聯網設備11與使用者22之間的綁定關係，相當於該物聯網設備11不存在與之綁定的使用者，則該設備將可以不回應任何使用者的操作指令，設備處於鎖定狀態。
在物聯網設備的使用中發現，物聯網設備與其對應綁定的使用者，存在這種綁定關係被破壞的安全隱患。以物聯網設備是收款設備(如，銷售終端POS機，到賬播報設備，二維碼反掃器等)為例，商家可以使用收款設備來進行日常商業活動中的收款，並且商家和自己的收款設備之間存在綁定關係，這個收款設備可以專用於該綁定的商家收款，商家可以在收款設備上設置自己的收款帳戶。但是，有可能犯罪分子將商家的收款設備偷偷替換為另一個收款設備，且該另一個收款設備上設置了犯罪分子自己的收款帳戶，商家如果沒有發現，將造成資金損失。再例如，犯罪分子可以將商家的收款設備偷走，並變更了設備上的收款帳戶為自己的帳戶，如果不能及時發現，也會造成資金損失。
為了保證商家使用的收款設備一定是自己的設備，保障物聯網設備及其操作使用者之間的對應關係的正確性，本說明書一個或多個實施例提供了一種物聯網設備的登錄方法，該方法可以在物聯網設備與物聯網伺服器登錄連接的過程中進行校驗，確保在物聯網設備與物聯網伺服器業務通訊(即開始正常的業務通訊傳輸)之前，就預先校驗了是正確的綁定使用者在使用該物聯網設備。
圖2示例了本說明書一個或多個實施例的物聯網設備的登錄方法，這裡的“登錄”指的是物聯網設備登錄上物聯網伺服器，可以與物聯網伺服器進行正常的業務通訊，包括物聯網設備上不僅可以使用離線功能，也可以使用非離線功能。如圖2所示，完成上述登錄過程的方法可以包括如下處理。
在步驟200中，使用者終端獲取物聯網設備的設備資訊。
在一個例子中，物聯網設備上可以貼有二維碼，該二維碼中可以包括了物聯網設備的設備資訊，還可以包括設備對應的物聯網伺服器的伺服器位址。本例子中，可以將要操作使用物聯網設備的使用者稱為設備操作使用者。設備操作使用者可以使用自己的使用者終端(例如，手機)掃描上述二維碼，獲得設備資訊和伺服器位址。該設備資訊可以用於使得物聯網伺服器知曉是哪個物聯網設備。
在步驟202中，使用者終端向物聯網伺服器請求對物聯網設備的使用權限。
例如，設備操作使用者可以透過使用者終端，向伺服器位址對應的物聯網伺服器發送設備使用請求，該請求用於申請設備操作使用者對物聯網設備的使用權限。在分配許可權之前，可以認為各個物聯網設備都是處於鎖定狀態，處於鎖定狀態的物聯網設備可以不回應使用者輸入的操作指令，使用者無法使用設備。
其中，設備使用請求中可以攜帶：步驟200中獲得的設備資訊，以使得物聯網伺服器知曉使用者是在請求對哪個設備的使用權限。此外，設備使用請求中還可以攜帶設備操作使用者的使用者資訊，物聯網伺服器在授權設備操作使用者使用物聯網設備之前，可以根據該使用者資訊對使用者身份進行校驗，判斷這個使用者是否能夠具有使用所請求的物聯網設備的使用權限。比如，使用者是否是已經註冊的使用者，使用者是否是物聯網設備的預置使用者，等。
如果物聯網伺服器校驗使用者資訊通過，則可以繼續執行步驟204；否則，物聯網伺服器可以向使用者終端回饋“您沒有許可權使用該設備”等提示資訊。
在步驟204中，物聯網設備向使用者終端分配登錄帳號。
例如，物聯網設備可以分別向使用者終端和物聯網設備發送登錄帳號。設備操作使用者可以憑藉該登錄帳號，操作物聯網設備。即該登錄帳號可以由設備操作使用者在設備初始化時使用，比如，當物聯網設備是收款設備時，使用者可以在物聯網設備上設置收款帳戶；還可以在物聯網設備上設置指紋、密碼等驗證要素以供後續驗證使用。而對於物聯網設備來說，物聯網設備可以憑藉物聯網伺服器發送的登錄帳號，知曉可以回應該登錄帳號對應的設備操作使用者的使用者指令，接受該使用者的操作和使用。
此外，物聯網伺服器還可以管理物聯網設備的狀態，示例性的，可以包括：鎖定狀態、分配狀態。本步驟中，在分配了登錄帳號後，物聯網伺服器可以將物聯網設備的設備狀態更改為分配狀態。物聯網伺服器還可以儲存物聯網設備和設備操作使用者之間的對應關係，如表1所示，其中，設備操作使用者可以用上述分配的登錄帳號來標識，設備標識可以由設備資訊中獲得：
表1 設備和使用者的對應關係
上述表1的對應關係，表示物聯網伺服器建立了物聯網設備和設備操作使用者之間的綁定關係，該設備可以接受該設備操作使用者的使用者指令，所述的指令可以是使用者對設備的設置。
在步驟206中，使用者透過該登錄帳號使用物聯網設備，設置驗證要素。
本步驟中，使用者可以向物聯網設備設置驗證要素。例如，該驗證要素可以是密碼或者生物特徵，所述的密碼可以是數字和字母組合的密碼，或者還可以是圖案密碼、口令密碼；生物特徵可以是聲紋、指紋、人臉等。
此外，使用者向物聯網設備設置驗證要素的方式，可以是直接在設備上輸入；或者也可以是使用者透過使用者終端向物聯網設備發送。
還可能的方式是，設備操作使用者可以是在初次使用該物聯網設備時，在設備上設置驗證要素。或者，也可以是，在使用了一段時間後，想啟用驗證模式，再向物聯網設備設置驗證要素。
在步驟208中，物聯網設備儲存驗證要素，並將驗證要素發送至物聯網伺服器。本步驟中，物聯網設備一方面可以在本機存放區驗證要素，以供後續的本地校驗使用。並且，還可以將驗證要素發送至物聯網伺服器，以供後續的二次校驗使用。
此外，物聯網伺服器還可以在表1的對應關係的基礎上，添加驗證要素。如下面的表2所示，用於記錄登錄帳號對應的設備操作使用者設置的驗證要素。
表2 設備和使用者的對應關係
在步驟210中，物聯網設備檢測到登錄觸發。
例如，這裡的登錄觸發，可以是物聯網設備檢測到設備操作使用者離開後，再回來時要重新進行登錄驗證。作為設備操作使用者的離開依據，示例性的，可以是物聯網設備檢測到設備鎖屏後一段時間要重新開啟，或者檢測到設備關機後又重新開機。這些操作都可以觸發物聯網設備的重新登錄。
在步驟212中，物聯網設備獲取設備操作使用者的驗證要素。
例如，物聯網設備可以獲取設備操作使用者的指紋、密碼等要素，以待驗證。使用者可以設置至少一個驗證要素。
在步驟214中，物聯網設備對驗證要素進行本地校驗。
例如，物聯網設備可以將在步驟212中檢測到登錄觸發後獲取的驗證要素，與步驟208中本機存放區的驗證要素比較，若兩者相同，則確認本地校驗通過。
在步驟216中，在本地校驗通過後，物聯網設備本地啟用登錄時的離線功能。
例如，若一個物聯網設備完成了整個登錄過程，可以認為包括兩個方面，一個方面是物聯網設備本地具有的一些離線功能已經能夠開始使用，比如，電腦，這些離線功能不涉及設備操作使用者的關鍵資料，可以不需要聯網使用；另一方面是物聯網設備還能夠由物聯網伺服器獲取到設備操作使用者的關鍵資料，這些關鍵資料是透過聯網後，由物聯網伺服器獲得。關鍵資料獲得後，物聯網設備可以與物聯網伺服器開始業務通訊，比如，以物聯網設備是POS機為例，業務通訊後，POS機可以向物聯網伺服器發送交易請求，伺服器可以配合POS機一起完成轉帳交易，例如，交易請求中可以包括轉帳金額、設備操作使用者設置的收款帳戶等參數，物聯網伺服器可以根據這些參數實現轉帳處理。
本步驟中，物聯網設備在本地校驗通過後，本地啟用登錄時的離線功能，可以加快設備的登錄速度，這樣等到後續步驟的二次校驗通過，物聯網設備只需要由物聯網伺服器獲取其他關鍵資料即可開始進行業務互動。並且，離線功能的預先啟用，也使得設備操作使用者可以先將這些離線功能使用起來，不需要等到物聯網伺服器校驗通過後才使用，使用者體驗比較好。
在步驟218中，物聯網設備將驗證要素發送至物聯網伺服器進行二次校驗。
本步驟中，物聯網設備可以向物聯網伺服器發送二次校驗請求，該請求中可以攜帶驗證要素，將驗證要素發送至物聯網伺服器，可以在伺服器側再驗證一次。
在步驟220中，物聯網伺服器對驗證要素進行二次校驗。
例如，物聯網伺服器在接收到物聯網設備發送的驗證要素後，可以將該驗證要素與步驟208中儲存的驗證要素進行比較。其中，物聯網設備在向物聯網伺服器發送驗證要素時，可以攜帶設備標識，由此物聯網伺服器可以知曉表2中對應該設備標識的驗證要素，從而進行儲存的驗證要素與接收到的二次校驗請求中攜帶的驗證要素的比較。若兩者相同，則二次校驗通過。
如果二次校驗通過，則物聯網伺服器可以繼續執行步驟222；否則，如果二次校驗不通過，可以執行步驟224。
在步驟222中，物聯網伺服器與物聯網設備開始登錄後的業務通訊過程。
例如，在二次校驗通過後，物聯網伺服器可以設置所述物聯網設備的狀態為登錄狀態，並開始與所述物聯網設備進行業務通訊，比如，POS機可以透過物聯網伺服器進行轉帳交易的處理。
在步驟224中，物聯網伺服器中止與物聯網設備的通訊。
本步驟中，物聯網伺服器可以向物聯網設備發送提示，不再繼續與物聯網設備正常通訊。例如，可以提示登錄失敗。此外，物聯網伺服器也可以向使用者終端提示異常，表示物聯網設備不能繼續使用。
本例子的物聯網設備的登錄方法，使用了“雙重校驗”的方式，一方面的校驗是在物聯網設備的本地校驗，另一方面的校驗是在物聯網伺服器側的二次校驗。這種雙重校驗方式，能夠很好的保證“使用者和綁定設備之間對應關係的正確”，提高IOT設備的安全性，保障IOT設備是由其真正的歸屬使用者在操作。
例如，假設犯罪分子偷偷使用物聯網設備，那麼他將無法通過物聯網設備的本地校驗，比如，指紋識別失敗；或者，假設犯罪分子將真正的物聯網設備替換為了犯罪分子自己的物聯網設備，那麼同樣真正的使用者在假的設備上也無法成功進行本地校驗。在登錄之前本地校驗的失敗，可以保證“設備操作使用者”和“物聯網設備”其中之一被替換，都會發現。
又例如，假設物聯網設備直接被犯罪分子偷走，並且假設真正使用者的本地校驗的驗證要素也被知曉，那可能犯罪分子將更改物聯網設備中的收款帳戶，以透過該帳戶獲取非法資金。
這種情況下，真正的設備操作使用者已經知曉物聯網設備被偷走了，使用者可以透過使用者終端向物聯網伺服器發送驗證取消請求，該請求用於請求取消所述設備操作使用者設置的驗證要素。例如，驗證取消請求中可以攜帶登錄帳號、或者使用者資訊、或者驗證要素。物聯網伺服器根據驗證取消請求，就可以找到類似表2所示的對應關係，並將對應關係中的物聯網設備和設備操作使用者之間的綁定解除，比如，解除了使用者使用的登錄帳號和設備標識之間的對應關係，可以直接將該對應關係進行清除，也不再儲存對應關係中的驗證要素，並且可以將物聯網設備的狀態重新設置為鎖定狀態。
那麼對於犯罪分子來說，即使進行本地校驗通過，二次校驗也無法通過，因為，若物聯網伺服器在接收到所述物聯網設備發送的二次校驗請求時，將會無法查找到儲存有該驗證要素，即確定並未儲存所述二次校驗請求中攜帶的驗證要素，則二次校驗失敗。而且在真正的設備操作使用者通知物聯網伺服器取消綁定後，物聯網設備已經重新鎖定，不再回應任何人的使用者指令了，物聯網伺服器和物聯網設備不再進行正常通訊。如果犯罪分子想要使用該物聯網設備，只能重新執行步驟200和步驟202，重新驗證身份獲取該設備的使用權限。因此，通過“物聯網伺服器側的二次校驗”，進一步增強了IOT設備的安全性，防止犯罪分子隨意使用物聯網設備。
如上，透過本說明書一個或多個實施例提供的物聯網設備的登錄方法，可以有效保證物聯網設備是由其真正的歸屬使用者在使用，保障了IOT設備的安全性。
為了實現上述的物聯網設備的登錄方法，本說明書一個或多個實施例還提供了一種物聯網設備的登錄裝置，該裝置可以應用於物聯網設備。如圖3所示，該裝置可以包括：要素接收模組31、本地校驗模組32、校驗結果模組33、連接處理模組34。
要素接收模組31，用於在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；
本地校驗模組32，用於對所述驗證要素進行本地校驗；
校驗結果模組33，用於在所述本地校驗模組校驗通過時，將所述驗證要素發送至物聯網伺服器進行二次校驗；
連接處理模組34，用於當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊。
在一個例子中，要素接收模組31，還用於：在檢測到登錄觸發之前，獲取所述設備操作使用者設置的所述驗證要素；儲存所述驗證要素，並將所述驗證要素發送至物聯網伺服器儲存，以使得所述物聯網伺服器根據儲存的驗證要素執行二次校驗；
所述本地校驗模組32，具體用於：將在檢測到登錄觸發後獲取的驗證要素，與所述要素接收模組儲存的驗證要素比較，若兩者相同則確認本地校驗通過。
為了實現上述的物聯網設備的登錄方法，本說明書一個或多個實施例還提供了一種物聯網設備的登錄裝置，該裝置可以應用於物聯網伺服器。如圖4所示，該裝置可以包括：要素儲存模組41和校驗處理模組42。
要素儲存模組41，用於接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；
校驗處理模組42，用於在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
上述實施例闡明的裝置或模組，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、蜂窩電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
為了描述的方便，描述以上裝置時以功能分為各種模組分別描述。當然，在實施本說明書一個或多個實施例時可以把各模組的功能在同一個或多個軟體和/或硬體中實現。
上述圖中所示流程中的各個步驟，其執行順序不限制於流程圖中的順序。此外，各個步驟的描述，可以實現為軟體、硬體或者其結合的形式，例如，本領域技術人員可以將其實現為軟體程式碼的形式，可以為能夠實現所述步驟對應的邏輯功能的電腦可執行指令。當其以軟體的方式實現時，所述的可執行指令可以儲存在記憶體中，並被設備中的處理器執行。
例如，對應於上述方法，本說明書一個或多個實施例同時提供一種物聯網設備，該設備可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器透過執行所述指令，用於實現如下步驟：
在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；
對所述驗證要素進行本地校驗；
若校驗通過，啟用登錄時的離線功能，並將所述驗證要素發送至物聯網伺服器進行二次校驗；
當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊。
在一個例子中，所述驗證要素，包括如下至少一種：指紋、密碼、口令、人臉、聲紋。
在一個例子中，所述處理器還用於在執行電腦指令時實現以下步驟：
在檢測到登錄觸發之前，獲取所述設備操作使用者設置的所述驗證要素；
儲存所述驗證要素，並將所述驗證要素發送至物聯網伺服器儲存，以使得所述物聯網伺服器根據儲存的所述驗證要素執行所述二次校驗。
例如，對應於上述方法，本說明書一個或多個實施例同時提供一種物聯網伺服器，該伺服器可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器透過執行所述指令，用於實現如下步驟：
接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；
在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
在一個例子中，所述處理器還用於在執行電腦指令時實現以下步驟：
接收所述設備操作使用者的使用者終端發送的驗證取消請求，所述驗證取消請求用於請求取消所述設備操作使用者設置的驗證要素；
根據所述驗證取消請求，清除所述驗證要素；
若在接收到所述物聯網設備發送的二次校驗請求時，確定並未儲存所述二次校驗請求中攜帶的驗證要素，則二次校驗失敗。
本說明書一個或多個實施例還提供了一種物聯網系統，該系統可以包括：物聯網設備和物聯網伺服器。
所述物聯網設備，用於：獲取所述設備操作使用者設置的所述驗證要素，儲存所述驗證要素，並將所述驗證要素發送至物聯網伺服器儲存；在檢測到登錄觸發時，獲取設備操作使用者的驗證要素；對所述驗證要素進行本地校驗；若校驗通過，啟用登錄時的離線功能，並將所述驗證要素發送至物聯網伺服器進行二次校驗；當所述物聯網伺服器二次校驗通過時，登錄所述物聯網伺服器，開始與所述物聯網伺服器之間的業務通訊；
所述物聯網伺服器，用於：接收並儲存物聯網設備發送的驗證要素，所述驗證要素由所述物聯網設備對應的設備操作使用者設置；並在接收到所述物聯網設備發送的二次校驗請求時，比較所述二次校驗請求中攜帶的驗證要素與儲存的所述驗證要素，若兩者相同，則二次校驗通過，設置所述物聯網設備為登錄狀態，並開始與所述物聯網設備進行業務通訊。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
本領域技術人員應明白，本說明書一個或多個實施例可提供為方法、系統或電腦程式產品。因此，本說明書一個或多個實施例可採用完全硬體實施例、完全軟體實施例或結合軟體和硬體方面的實施例的形式。而且，本說明書一個或多個實施例可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。
本說明書一個或多個實施例可以在由電腦執行的電腦可執行指令的一般上下文中描述，例如程式模組。一般地，程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本說明書一個或多個實施例，在這些分散式運算環境中，由透過通信網路而被連接的遠端處理設備來執行任務。在分散式運算環境中，程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於資料處理設備實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
上述對本說明書特定實施例進行了描述。其它實施例在申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在圖式中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多工處理和並行處理也是可以的或者可能是有利的。
以上所述僅為本說明書一個或多個實施例的較佳實施例而已，並不用以限制本說明書一個或多個實施例，凡在本說明書一個或多個實施例的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本說明書一個或多個實施例保護的範圍之內。In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will be combined with the drawings in one or more embodiments of this specification. The technical solution is described clearly and completely. Obviously, the described embodiments are only a part of the embodiments of this specification, but not all the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present disclosure. In the IoT system, the IoT server can be used to control the operation of the IoT device. If a user wants to use an IoT device, he can apply for the operation permission of the device from the IoT server corresponding to the device . Please refer to the IoT system illustrated in FIG. 1, as shown in FIG. 1, the system may include: IoT devices 11, IoT devices 12, IoT devices 1n, etc. The operation control of these devices may all be controlled by IoT servers 21 management. If a user 22 wants to use one of the IoT devices 11, he can apply to the IoT server 21 for authorization to use the device. For example, after the Internet of Things server 21 authorizes the user 22 to use the Internet of Things device 11, it is equivalent to establishing a binding relationship between the Internet of Things device 11 and the user 22, and other users may no longer have operations on the device Use permissions. If the IoT server 21 releases the binding relationship between the IoT device 11 and the user 22, which means that there is no user bound to the IoT device 11, the device will not respond to any use. The user's operation instruction, the device is in a locked state. In the use of Internet of Things devices, it is found that the Internet of Things devices and their corresponding bound users have a hidden security risk that the binding relationship is broken. Taking the Internet of Things device as a collection device (for example, a sales terminal POS machine, an account reporting device, a QR code scanner, etc.) as an example, a merchant can use the collection device to collect money in daily business activities, and the merchant There is a binding relationship with its own collection device. This collection device can be used exclusively by the bound merchant to collect payments. The merchant can set up its own collection account on the collection device. However, it is possible that the criminals secretly replaced the merchant’s collection device with another collection device, and the criminal’s own collection account was set on the other collection device. If the merchant did not find it, it would cause financial losses. For another example, criminals can steal the merchant’s collection device and change the collection account on the device to their own account. If it cannot be found in time, it will also cause financial losses. In order to ensure that the payment device used by the merchant must be its own device, and to ensure the correctness of the correspondence between the IoT device and its operating users, one or more embodiments of this specification provide a login method for the IoT device, This method can be verified during the login connection between the IoT device and the IoT server, to ensure that the IoT device and the IoT server are pre-verified before the business communication (that is, the start of normal business communication transmission) The correct binding user is using the IoT device. FIG. 2 illustrates the login method of an IoT device according to one or more embodiments of this specification. “Login” refers to the IoT device logging into an IoT server, which can perform normal business communication with the IoT server. Including not only offline functions but also non-offline functions can be used on IoT devices. As shown in FIG. 2, the method for completing the above login process may include the following processing. In step 200, the user terminal obtains device information of the Internet of Things device. In one example, the IoT device may be pasted with a QR code, which may include device information of the IoT device, and may also include a server address of the IoT server corresponding to the device. In this example, the user who wants to operate and use the IoT device may be referred to as the device operation user. Device operation users can use their own user terminals (for example, mobile phones) to scan the QR code to obtain device information and server addresses. The device information can be used to make the IoT server know which IoT device. In step 202, the user terminal requests permission to use the Internet of Things device from the Internet of Things server. For example, a device operation user can send a device use request to an IoT server corresponding to the server address through a user terminal, and the request is used to apply for a device operation user's permission to use the IoT device. Before assigning the permission, it can be considered that each IoT device is in a locked state, and the IoT device in the locked state may not respond to the operation instruction input by the user, and the user cannot use the device. Among them, the device use request may carry: the device information obtained in step 200, so that the Internet of Things server knows which device the user is requesting the right to use. In addition, the device use request can also carry the user information of the device operation user. Before the IoT server authorizes the device operation user to use the IoT device, it can verify the user's identity based on the user information to determine this Whether the user can have the right to use the requested IoT device. For example, whether the user is a registered user, whether the user is a preset user of the IoT device, etc. If the IoT server verifies that the user information is passed, you can continue to perform step 204; otherwise, the IoT server can feed back prompt information such as "You do not have permission to use the device" to the user terminal. In step 204, the Internet of Things device allocates a login account to the user terminal. For example, the Internet of Things device may send a login account to the user terminal and the Internet of Things device, respectively. The device operation user can operate the Internet of Things device by virtue of the login account. That is, the login account can be used by the device operation user when the device is initialized. For example, when the IoT device is a payment device, the user can set a payment account on the IoT device; you can also set a fingerprint on the IoT device , Password and other verification elements for subsequent verification. As for the IoT device, the IoT device can know that it can respond to the user instruction of the device operation user corresponding to the login account by virtue of the login account sent by the IoT server, and accept the user's operation and use. In addition, the Internet of Things server can also manage the status of the Internet of Things devices. Exemplarily, the status may include: a locked state and an assigned state. In this step, after the login account is assigned, the IoT server can change the device state of the IoT device to the assigned state. The IoT server can also store the correspondence between the IoT device and the device operation user, as shown in Table 1, where the device operation user can be identified by the above assigned login account, and the device identification can be identified in the device information Obtained: Table 1 Correspondence between equipment and users The correspondence in Table 1 above indicates that the IoT server has established a binding relationship between the IoT device and the device operation user. The device can accept user instructions from the device operation user. The instructions may be used The settings of the device. In step 206, the user uses the IoT device through the login account to set authentication elements. In this step, the user can set authentication elements to the IoT device. For example, the verification element may be a password or a biological feature, and the password may be a combination of numbers and letters, or may also be a pattern password, a password password; the biological feature may be a voiceprint, a fingerprint, a human face, and so on. In addition, the method for the user to set the authentication element to the IoT device may be directly input on the device; or the user may send it to the IoT device through the user terminal. It is also possible that the user of the device operation may set the authentication element on the device when using the IoT device for the first time. Or, it may be that after using it for a period of time, you want to enable the verification mode and then set the verification element to the IoT device. In step 208, the IoT device stores the verification element and sends the verification element to the IoT server. In this step, on the one hand, the IoT device can verify the elements in the local storage area for subsequent local verification. In addition, the verification elements can also be sent to the IoT server for subsequent secondary verification. In addition, the IoT server can also add verification elements based on the correspondence in Table 1. As shown in Table 2 below, it is used to record the verification elements set by the device operation user corresponding to the login account. Table 2 Correspondence between equipment and users In step 210, the IoT device detects a login trigger. For example, the login trigger here may be that after the IoT device detects that the user of the device operation has left, it will have to perform login verification again when it comes back. As a basis for the user leaving the device operation, for example, it may be that the Internet of Things device restarts after detecting the device lock screen for a period of time, or detects that the device is turned off and then turned on again. These operations can trigger the re-login of IoT devices. In step 212, the Internet of Things device acquires the verification element of the user of the device operation. For example, the Internet of Things device can obtain fingerprints, passwords and other elements of the device operation user to be verified. The user can set at least one verification element. In step 214, the IoT device performs local verification on the verification element. For example, the IoT device may compare the verification element obtained after the login trigger is detected in step 212 with the verification element in the local storage area in step 208, and if the two are the same, confirm that the local verification is passed. In step 216, after the local verification is passed, the IoT device locally enables the offline function at login. For example, if an IoT device completes the entire login process, it can be considered to include two aspects. One aspect is that some offline functions that the IoT device has locally can already be used, such as a computer. These offline functions do not involve device operation users. The key data can be used without Internet connection; on the other hand, the IoT device can also obtain the key data of the device operation user from the IoT server. These key data are obtained by the IoT server after being connected to the Internet. After the key data is obtained, the IoT device can start business communication with the IoT server. For example, taking the IoT device as a POS machine for example, after the business communication, the POS machine can send a transaction request to the IoT server, and the server can cooperate The POS machine completes the transfer transaction together. For example, the transaction request may include the transfer amount, the collection account set by the user of the device operation, and other parameters. The IoT server can implement the transfer process according to these parameters. In this step, after the IoT device passes the local verification, the offline function at the time of login is enabled locally, which can speed up the device's login speed, so that until the second verification of the subsequent step passes, the IoT device only needs to be sent by the IoT server Get other key information to start business interaction. In addition, the offline function is enabled in advance, so that the device operation user can use these offline functions first, and does not need to wait until the IoT server passes the verification before using it. The user experience is better. In step 218, the IoT device sends the verification element to the IoT server for secondary verification. In this step, the IoT device can send a secondary verification request to the IoT server. The request can carry the verification element, and the verification element can be sent to the IoT server for verification once again on the server side. In step 220, the IoT server performs a second verification on the verification element. For example, after receiving the verification element sent by the IoT device, the IoT server may compare the verification element with the verification element stored in step 208. Among them, the IoT device can carry the device identification when sending the verification element to the IoT server, so that the IoT server can know the verification element corresponding to the device identification in Table 2, so that the stored verification element and the received Comparison of verification elements carried in the second verification request. If the two are the same, the second verification passes. If the second verification passes, the Internet of Things server may continue to perform step 222; otherwise, if the second verification fails, step 224 may be performed. In step 222, the IoT server and the IoT device start the business communication process after login. For example, after the second verification is passed, the IoT server can set the state of the IoT device to the login state, and start business communication with the IoT device, for example, a POS machine can perform through the IoT server Handling of transfer transactions. In step 224, the IoT server suspends communication with the IoT device. In this step, the Internet of Things server can send a prompt to the Internet of Things device, and will no longer continue normal communication with the Internet of Things device. For example, you can be prompted for login failure. In addition, the Internet of Things server can also prompt an abnormality to the user terminal, indicating that the Internet of Things device can no longer be used. The login method of the IoT device in this example uses the "double verification" method. On the one hand, the verification is on the local verification of the IoT device, on the other hand, the verification is on the IoT server side. Secondary verification. This double verification method can well guarantee the "correspondence between the user and the bound device is correct", improve the security of the IOT device, and ensure that the IOT device is operated by its truly attributable user. For example, if the criminal uses the IoT device secretly, he will not be able to pass the local verification of the IoT device, for example, fingerprint recognition fails; or, suppose the criminal replaces the real IoT device with the criminal's own IoT device , Then the same real user cannot successfully perform local verification on the fake device. The failure of the local verification before login can ensure that one of the "device operation user" and the "Internet of Things device" is replaced and will be discovered. For another example, if the IoT device is directly stolen by a criminal, and it is assumed that the verification element of the local verification of the real user is also known, then the criminal may change the collection account in the IoT device to obtain through the account Illegal funds. In this case, the real device operation user already knows that the IoT device has been stolen, and the user can send a verification cancellation request to the IoT server through the user terminal, the request is used to request the cancellation of the device operation user Set the verification elements. For example, the verification cancellation request may carry a login account, user information, or verification elements. According to the verification cancellation request, the IoT server can find the corresponding relationship similar to that shown in Table 2, and release the binding between the IoT device and the device operation user in the corresponding relationship, for example, the user’s The corresponding relationship between the login account and the device ID can be directly cleared, the verification elements in the corresponding relationship are no longer stored, and the state of the IoT device can be reset to the locked state. Then for criminals, even if the local verification is passed, the secondary verification will not pass, because if the IoT server receives the secondary verification request sent by the IoT device, it will not be able to find When the verification element is stored, that is, it is determined that the verification element carried in the secondary verification request is not stored, the secondary verification fails. Moreover, after the real device operation user informs the IoT server to cancel the binding, the IoT device has been locked again and no longer responds to any user's commands, and the IoT server and the IoT device no longer communicate normally. If criminals want to use the IoT device, they can only re-execute step 200 and step 202 to re-verify their identity and obtain the permission to use the device. Therefore, the "secondary verification on the server side of the Internet of Things" further enhances the security of the IOT device and prevents criminals from using the Internet of Things device at will. As mentioned above, through the login method of the IoT device provided by one or more embodiments of this specification, it can effectively ensure that the IoT device is used by its real attributive user, and the security of the IOT device is guaranteed. In order to implement the above method for logging in an Internet of Things device, one or more embodiments of this specification also provide an apparatus for logging in an Internet of Things device, which can be applied to an Internet of Things device. As shown in FIG. 3, the device may include: an element receiving module 31, a local verification module 32, a verification result module 33, and a connection processing module 34. The element receiving module 31 is used to obtain the verification element of the device operation user when the login trigger is detected; the local verification module 32 is used to perform local verification on the verification element; the verification result module 33, When the local verification module passes the verification, the verification element is sent to the IoT server for secondary verification; the connection processing module 34 is used for secondary verification of the IoT server When passing the verification, log in to the Internet of Things server and start business communication with the Internet of Things server. In one example, the element receiving module 31 is further configured to: before detecting the login trigger, obtain the verification element set by the user of the device operation; store the verification element and send the verification element to The IoT server stores, so that the IoT server performs a second verification according to the stored verification elements; the local verification module 32 is specifically used for: the verification elements obtained after the registration trigger is detected, Compared with the verification element stored in the element receiving module, if the two are the same, it is confirmed that the local verification is passed. In order to implement the above-mentioned login method of the Internet of Things device, one or more embodiments of this specification also provide a login device of the Internet of Things device, which can be applied to the Internet of Things server. As shown in FIG. 4, the device may include: an element storage module 41 and a verification processing module 42. The element storage module 41 is used to receive and store the verification element sent by the Internet of Things device, and the verification element is set by a device operation user corresponding to the Internet of Things device; the verification processing module 42 is used to receive When the secondary verification request sent by the Internet of Things device is compared, the verification element carried in the secondary verification request and the stored verification element are compared, and if the two are the same, the secondary verification passes and the object is set The networked device is in a login state and starts business communication with the Internet of Things device. The device or module explained in the above embodiments may be realized 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 laptop 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 convenience of description, when describing the above device, the functions are divided into various modules and described separately. Of course, when implementing one or more embodiments of this specification, the functions of each module may be implemented in one or more software and/or hardware. The execution order of each step in the flow shown in the above figure is not limited to the order in the flowchart. In addition, the description of each step can be implemented in the form of software, hardware, or a combination thereof. For example, those skilled in the art can implement it in the form of software code, which can be a computer capable of implementing the logical functions corresponding to the steps Executable instructions. When implemented in software, the executable instructions can be stored in memory and executed by the processor in the device. For example, corresponding to the above method, one or more embodiments of this specification simultaneously provide an Internet of Things device, which may include a processor, a memory, and computer instructions stored on the memory and executable on the processor. The processor is used to implement the following steps by executing the instruction: When a login trigger is detected, the verification element of the device operation user is obtained; the verification element is locally verified; if the verification passes, the Offline function, and send the verification element to the IoT server for secondary verification; when the secondary verification of the IoT server passes, log in to the IoT server and start to serve with the IoT server Business communication between devices. In one example, the verification element includes at least one of the following: fingerprint, password, password, face, voiceprint. In one example, the processor is further configured to implement the following steps when executing computer instructions: before detecting a login trigger, obtain the verification element set by the device operation user; store the verification element, and store The verification element is sent to an IoT server for storage, so that the IoT server performs the secondary verification according to the stored verification element. For example, corresponding to the above method, one or more embodiments of this specification simultaneously provide an Internet of Things server, which may include a processor, a memory, and computer instructions stored on the memory and executable on the processor , The processor is used to implement the following steps by executing the instruction: receiving and storing the verification element sent by the Internet of Things device, the verification element is set by a device operation user corresponding to the Internet of Things device; When the secondary verification request sent by the Internet of Things device is compared, the verification element carried in the secondary verification request and the stored verification element are compared, and if the two are the same, the secondary verification passes and the object is set The networked device is in a login state and starts business communication with the Internet of Things device. In one example, the processor is further configured to implement the following steps when executing computer instructions: receiving a verification cancellation request sent by a user terminal of the user who operates the device, and the verification cancellation request is used to request cancellation of the device Operate the verification element set by the user; clear the verification element according to the verification cancellation request; if the secondary verification request sent by the IoT device is received, determine that the secondary verification request is not stored The verification element carried in the second verification fails. One or more embodiments of this specification also provide an IoT system, which may include: an IoT device and an IoT server. The IoT device is used to: obtain the verification element set by the user of the device operation, store the verification element, and send the verification element to the IoT server for storage; when a login trigger is detected, Obtain the verification elements of the device operation user; perform local verification on the verification elements; if the verification passes, enable the offline function at login, and send the verification elements to the Internet of Things server for secondary verification; When the second verification of the IoT server passes, log in to the IoT server and start business communication with the IoT server; The IoT server is used to: receive and store the IoT server A verification element sent by the device, the verification element being set by a device operation user corresponding to the IoT device; and when receiving the secondary verification request sent by the IoT device, comparing the secondary verification request If the verification element carried in and the stored verification element are the same, the second verification is passed, the Internet of Things device is set to the login state, and business communication with the Internet of Things device is started. It should also be noted that the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device that includes a series of elements includes not only those elements, but also includes Other elements not explicitly listed, or include elements inherent to this process, method, commodity, or equipment. Without more restrictions, the element defined by the sentence "include one..." does not exclude that there are other identical elements in the process, method, commodity, or equipment that includes the element. Those skilled in the art should understand that one or more embodiments of this specification may be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of this specification can be implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code In the form of computer program products. One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification can also be practiced in a distributed computing environment 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. 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. In particular, for the embodiment of the data processing 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. The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of patent application. In some cases, the actions or steps described in the scope of the patent application may be performed in a different order than in the embodiment and still achieve the desired result. In addition, the processes depicted in the drawings do not necessarily require the particular order shown or sequential order to achieve the desired results. In some embodiments, multiplexing and parallel processing are also possible or may be advantageous. The above are only preferred embodiments of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. Anything within the spirit and principle of one or more embodiments of this specification, Any modifications, equivalent replacements, improvements, etc. made should be included within the scope of protection of one or more embodiments of this specification.
