為了使本技術領域的人員更好地理解本說明書一個或多個實施例中的技術方案，下面將結合本說明書一個或多個實施例中的圖式，對本說明書一個或多個實施例中的技術方案進行清楚、完整地描述，顯然，所描述的實施例僅僅是本說明書一部分實施例，而不是全部的實施例。基於本說明書一個或多個實施例，本領域普通技術人員在沒有作出創造性勞動前提下所獲得的所有其他實施例，都應當屬於本公開保護的範圍。
在物聯網系統中，可以由物聯網伺服器來對物聯網設備進行操作控制，如果一個使用者想要使用一個物聯網設備，可以向設備對應的物聯網伺服器申請對該設備的操作許可權。可以參見圖1示例的物聯網系統，如圖1所示，該系統可以包括：物聯網設備11、物聯網設備12、物聯網設備1n等設備，這些設備的操作控制可以都由物聯網伺服器21管理。
如果一個使用者22想要使用其中一個物聯網設備11，他可以向物聯網伺服器21申請對這個設備的使用授權。例如，當物聯網伺服器21授權使用者22使用物聯網設備11之後，相當於建立了物聯網設備11與使用者22之間的綁定關係，其他使用者可以不再具有對該設備的操作使用權限。而假如物聯網伺服器21解除了物聯網設備11與使用者22之間的綁定關係，相當於該物聯網設備11不存在與之綁定的使用者，則該設備將可以不回應任何使用者的操作指令，設備處於鎖定狀態。
本說明書一個或多個實施例提供了一種使用智慧設備進行支付的方法，該方法將上述的物聯網系統應用於支付。
假設上述的物聯網設備11是所述的智慧設備，使用者22可以透過自己的控制設備(如，使用者的手機)來對智慧設備進行控制，其中，所述的控制可以包括“支付控制”。例如，智慧設備可以應用於支付(如，付款或者收款)，而使用者22可以控制智慧設備在支付時的限額、限次等支付條件。
如下示例一種應用於支付的物聯網系統的場景：
請參見圖2的示例，一個家長A和小孩B，為了對小孩B進行財商教育，培養孩子的存錢、花錢等意識，家長A可以給小孩B買一個智慧儲蓄罐C。但是，需要注意的是，本實施例的智慧儲蓄罐C並不儲存現金，而是關聯至雲端的一個子帳戶D，儲蓄罐有多少錢是由子帳戶D中的虛擬貨幣決定。
進一步的，還有一個主帳戶E，該主帳戶E是家長A的帳戶，例如，家長A的支付寶帳戶。家長A可以透過手機F管理自己的主帳戶E中的資金。但是，小孩B由於年齡較小，不能像家長A那樣自己來控制子帳戶D中的資金，而是由家長A同樣透過手機F來控制小孩B的子帳戶，包括子帳戶的產生和使用，都可以由家長A控制。
而子帳戶D的餘額、使用結果等資訊可以由智慧儲蓄罐C顯示，小孩B可以方便的透過智慧儲蓄罐C進行查看。如此一來，智慧儲蓄罐C的使用，既使得小孩B能夠透過實體設備直觀的看到自己的資金的使用情況，更有利於培養財商，並且又使得小孩不會脫離家長A的控制，保證資金安全使用。
再者，如圖2所示，雲端的主帳戶E和子帳戶D之間的聯動(如，轉帳等)和管理，都可以由伺服器G控制。
如上是以智慧儲蓄罐為例，說明物聯網系統的支付場景的應用，當然，實際使用中並不局限於此，其他的應用場景或者其他類型的智慧設備也可以使用該方法。比如，智慧設備也可以不是智慧儲蓄罐，而是小孩隨身佩戴的手環、手錶等可攜式設備。
接著仍以智慧設備是智慧儲蓄罐為例，描述如何根據本說明書實施例的方法使用該智慧儲蓄罐進行支付。描述將分為幾個場景進行：
設備綁定
假設圖2中的家長A剛剛給小孩B買了一個智慧儲蓄罐C(當然，實際的儲蓄罐外觀不局限於圖2所示，可以自由設計各種外觀)，家長A想要培養小孩B的理財意識。那麼，家長首先要做的事情，可以是將自己的手機F(即控制設備，以手機為例)與智慧儲蓄罐C綁定，以使得自己可以控制智慧儲蓄罐C的支付或者資訊顯示等處理。
圖3示例了家長的手機與智慧儲蓄罐綁定的流程，可以包括：
在步驟300中，家長手機獲取智慧儲蓄罐的設備標識。
例如，智慧儲蓄罐上可以貼有二維碼，家長手機可以掃描該二維碼獲取智慧儲蓄罐的設備標識。在一個例子中，家長的手機上可以安裝有支付應用，可以打開該支付應用，透過支付應用中的“掃一掃”功能掃描上述二維碼。
在其他的例子中，也可以由家長直接在手機的支付應用中手動輸入智慧儲蓄罐的設備標識。該設備標識能夠唯一標識一個智慧儲蓄罐。
在步驟302中，家長手機向伺服器發送設備綁定請求，所述設備綁定請求中攜帶：智慧儲蓄罐的設備標識、主帳戶的帳戶標識以及子帳戶。
例如，示例一個應用場景的形式可以是，家長手機的支付應用在註冊時已經綁定了家長自己的主帳戶，並且家長已經預先為小孩產生了一個子帳戶，並且該子帳戶已經預先建立了與所述主帳戶之間的對應關係。
當家長為小孩購買了智慧儲蓄罐後，可以將該智慧儲蓄罐與小孩已有的上述的子帳戶綁定。在操作時，家長可以在支付應用的業務介面上點擊為小孩的子帳戶“添加設備”，接著，可以透過步驟300中的“掃一掃”獲取到設備標識。家長可以繼續點擊業務介面中的“確定添加設備”，則家長手機可以向伺服器(例如，該伺服器可以同時是支付應用的伺服器，也是用於管理智慧設備的伺服器)發送設備綁定請求，請求中攜帶：智慧儲蓄罐的設備標識、主帳戶以及子帳戶。
在另一個例子中，也許家長還尚未為小孩創建子帳戶，而是先購買了一個智慧儲蓄罐。這種情況下，掃碼添加設備時，家長可以選擇為哪個小孩添加設備，設備綁定請求中可以攜帶智慧儲蓄罐的設備標識和主帳戶，而由伺服器側根據該請求為上述小孩創建一個子帳戶，並將該子帳戶與小孩的智慧儲蓄罐的設備標識進行綁定。
或者，家長也可以先只綁定主帳戶和智慧儲蓄罐，而暫時未產生對應智慧儲蓄罐的子帳戶。但是，在子帳戶產生以前，智慧儲蓄罐是不能用於支付的，智慧儲蓄罐的支付實現要透過子帳戶。當後續家長為小孩產生子帳戶後，可以將該子帳戶與智慧儲蓄罐綁定，此時智慧儲蓄罐才可以使用。
在步驟304中，伺服器建立主帳戶、設備標識以及子帳戶之間的對應關係。
如下表1所示，伺服器可以建立三者之間的綁定關係：
表1 綁定關係
綁定關係的建立表明，一方面，智慧儲蓄罐已經具有了對應的子帳戶，可以進行後續的子帳戶餘額顯示、支付等操作，另一方面，家長已經可以透過自己的手機來控制子帳戶的支付和顯示。
在步驟306中，伺服器可以在綁定完成後，可以向家長手機返回一個綁定成功的回應。例如，家長手機的業務介面上可以顯示“添加設備成功！您可以有自己的儲蓄罐了，快去試試吧”。
此外，智慧儲蓄罐可以進行聯網配置，以方便接收伺服器下發的資訊，比如，子帳戶餘額、支付時的支付結果。例如，當智慧儲蓄罐使用RTOS(Real-time Operation System，即時操作系統)時，可以啟動智慧儲蓄罐的配網模式，由儲蓄罐監聽家長手機連接WiFi時廣播的帳戶和密碼，從而進行WiFi聯網。又例如，當智慧儲蓄罐使用Android作業系統時，可以直接在儲蓄罐上設置WiFi時的帳戶和密碼進行聯網。
支付條件設置
在完成了上述的設備綁定操作後，家長為了實現對小孩使用智慧儲蓄罐進行支付交易的控制，可以透過手機對子帳戶進行支付條件設置。
圖4示例了家長手機對智慧儲蓄罐的支付設置的流程，可以包括：
在步驟400中，家長手機向所述伺服器發送對所述子帳戶設置的支付條件。
本步驟中的支付條件，可以包括如下至少一項：支付限額和支付限次。例如，所述的支付限額可以是每次付款時的最高額度，或者一段時間內的最高付款總和。所述的支付限次，可以是預設時間段內(如，一天)的最高支付次數。
在步驟402中，伺服器儲存所述支付條件。
例如，伺服器儲存支付條件後，表1可以變更為如表2所示：
表2 綁定關係
在步驟404中，伺服器可以向家長手機返回支付設置成功的回應。
經過上述設置，智慧儲蓄罐在應用於支付時，將受到上述支付條件的約束。
應用智慧儲蓄罐進行支付
在使用智慧儲蓄罐支付前，得確保智慧儲蓄罐對應的子帳戶中尚有餘額。如果沒有餘額，則家長可以向小孩的子帳戶中轉入一部分金額，比如，家長手機可以透過業務介面向伺服器發送向所述子帳戶轉帳的轉帳請求，攜帶轉帳金額，伺服器可以根據該請求，由家長的主帳戶向小孩的子帳戶轉帳。此外，在智慧儲蓄罐聯網的情況下，伺服器可以在轉帳成功後，向智慧儲蓄罐發送子帳戶的最新餘額，以使得小孩可以在智慧儲蓄罐上查看自己有多少錢。
在一個示例性的場景中，假設小孩要進行購物付款，小孩可以拿自己的智慧儲蓄罐來支付。圖5示例了儲蓄罐支付的流程，其中，該流程以付款為例，當然，在其他的場景中，儲蓄罐也可以用來收款。
在步驟500中，智慧儲蓄罐獲取付款碼，付款碼中包括：智慧儲蓄罐的設備標識。
本步驟中，付款碼可以是由智慧儲蓄罐離線產生。或者，還可以是，在智慧儲蓄罐聯網的情況下，由伺服器產生並發送給智慧儲蓄罐。
付款碼產生的觸發，例如，可以是透過儲蓄罐螢幕上的觸控鍵觸發，或者儲蓄罐的實體鍵觸發，或者還可以是聲波語音觸發，或者圖像識別手勢觸發等。儲蓄罐在接收到上述的聲波、按鍵等方式觸發時，可以開始獲取付款碼。
此外，上述的多種觸發方式也不僅可以應用於觸發付款碼的產生，也可以觸發儲蓄罐的其他處理。例如，儲蓄罐可以檢測控制指令，並根據指令執行相應的控制處理，該指令的觸發方式包括但不限於上述的手勢、實體按鍵、觸控螢幕、聲波等方式。所執行的控制處理也可以是例如查詢子帳戶餘額、查看最新任務顯示等其他處理，示例性的，以手勢為例，儲蓄罐可以透過感測器或者攝影鏡頭，識別使用者的多種手勢並進行對應處理，比如，如果使用者揮手兩下表示查詢餘額。
例如，支付碼中可以攜帶智慧儲蓄罐的設備標識。
在步驟502中，智慧儲蓄罐展示付款碼。
例如，智慧儲蓄罐可以將付款碼顯示在螢幕上，這樣支付請求發起端(即收款方)可以掃描該付款碼，發起向伺服器的支付請求，並在支付請求中攜帶付款碼中的智慧儲蓄罐的設備標識。或者，收款方也可以將二維碼發送至伺服器進行解析，由伺服器解析獲得設備標識。
在步驟504中，伺服器接收到支付請求，所述支付請求中包括：智慧儲蓄罐的設備標識。該支付請求中還可以包括本次付款的付款金額。
在步驟506中，伺服器根據所述設備標識，將所述子帳戶作為付款帳戶，判斷本次支付請求是否滿足預設的支付條件。
例如，伺服器可以根據表2，得到設備標識對應的子帳戶以及支付條件。以支付條件為限額為例，伺服器可以判斷本次支付的付款金額是否在所述的限額以內，假設限額是100元，付款金額是50元，則滿足支付條件。
若支付條件不滿足，則伺服器可以向收款方返回本次支付不符合支付條件，支付失敗等回應資訊。若智慧儲蓄罐聯網，伺服器也可以將回應資訊發送至儲蓄罐，以在儲蓄罐的螢幕上顯示供小孩查看。或者，即使智慧儲蓄罐當前未聯網，可以待儲蓄罐聯網時，伺服器再將回應資訊發送至儲蓄罐。
若支付條件滿足，則伺服器可以繼續執行步驟508。
在步驟508中，伺服器以子帳戶作為付款帳戶，向收款帳戶轉帳預設的付款金額。
在步驟510中，伺服器可以向智慧儲蓄罐回饋支付結果，例如支付成功。
此外，上述例子是以付款碼為例，智慧儲蓄罐也可以用於收款，可以產生收款碼，收款碼中也可以包括智慧儲蓄罐的設備標識，伺服器可以根據請求由所述子帳戶進行收款的支付請求，將所述子帳戶作為收款帳號，由付款帳戶向所述子帳戶轉帳預設的收款金額。
在上述的支付場景之外，智慧儲蓄罐還可以有多種培養小孩財商的方式。比如，家長可以為小孩創建“任務”和“心願”，小孩可以在自己的智慧儲蓄罐側查看任務和心願是否達成。
其中，所述的“任務”可以是家長指示一個事情讓小孩去做，如，洗碗，待小孩做完事情後，由家長給予小孩一定的獎勵。這個任務場景中，小孩就可以透過智慧儲蓄罐的螢幕顯示來查看家長創建的任務是什麼，以及本次任務能夠得到的獎勵金額是多少，還可以在儲蓄罐的螢幕顯示看到任務完成後的子帳戶金額變動，從而使得小孩有一個非常直觀的賺錢體驗。
其中，所述的“心願”可以是小孩自己的一個心裡願望，只是這個願望可以由家長幫小孩創建，並顯示在小孩的智慧儲蓄罐的螢幕上。小孩可以透過儲蓄罐的螢幕顯示即時的查看自己的心願達成進度。比如，假設小孩的願望是有一個布娃娃，而這個布娃娃需要100元購買，那麼“心願”就可以是“買布娃娃，100元”。並且，儲蓄罐還可以顯示小孩子帳戶的當前金額是70元，尚未達成心願。這種心願場景也有助於培養小孩的存錢意識，為了自己的願望實現去存錢。
上述的任務和心願只是兩個例子，實際實施中不局限於此，可以根據具體的業務設定，形成多種豐富的理財場景，並結合智慧儲蓄罐的顯示，實現家長和小孩之間的理財互動。如下簡單說明“任務”和“心願”場景下的互動：
智慧儲蓄罐顯示任務
圖6示例了任務顯示的流程，可以包括：
在步驟600中，家長手機創建任務資訊，所述任務資訊包括如下至少一項：任務名稱、任務金額。
例如，創建的任務的任務名稱可以是“洗碗”，這個任務是需要小孩去做的。待小孩完成任務後，獎勵的金額可以是10元。那麼任務資訊可以包括：“洗碗，10元”。
在步驟602中，家長手機將任務資訊發送至伺服器。
例如，伺服器可以儲存任務資訊，如下表3所示。並且，伺服器可以對任務進行管理，比如，管理任務的狀態，以及在任務完成時進行轉帳。
表3 任務資訊
在步驟604中，伺服器將任務資訊發送至智慧儲蓄罐顯示。
例如，智慧儲蓄罐可以顯示任務名稱、任務金額、任務狀態等資訊。小孩透過儲蓄罐的顯示螢幕就可以知道自己有一個未完成的任務是洗碗，並且知道該任務完成後可以得到獎勵10元。
此外，任務資訊還可以設置的較複雜一些，比如，“在今天內洗碗”、或者“洗碗兩次”。家長可以和小孩協商創建任務資訊。
在步驟606中，伺服器接收到所述任務名稱對應的任務完成指令。
本步驟中，任務完成指令可以是由家長手機發送至伺服器，比如，家長在手機的業務介面點擊“任務完成”。或者還可以由小孩在智慧儲蓄罐發起，比如，小孩在洗碗後，可以在智慧儲蓄罐上點擊任務完成。圖6以家長發起為例。
在步驟608中，伺服器根據指令，由主帳戶向子帳戶轉入任務金額。
例如，在任務完成後，伺服器可以由家長的主帳戶向小孩的子帳戶轉帳10元，完成對小孩的獎勵。此時，小孩的子帳戶有了更新餘額，比如，原來的餘額是50，現在的更新餘額是60元。
在步驟610中，伺服器向智慧儲蓄罐發送子帳戶的更新餘額。
本步驟中，智慧儲蓄罐可以顯示子帳戶的更新餘額，還可以顯示出“您的帳戶增加了10元，更新餘額是60元”，使得小孩有個較為直觀的賺錢體驗。
智慧儲蓄罐顯示心願
圖7示例了心願顯示的流程，可以包括：
在步驟700中，家長手機創建心願資訊，所述任務資訊包括如下至少一項：心願名稱、目標金額、當前金額、心願達成狀態。
例如，創建的心願名稱可以是“買一個布娃娃”，實現該心願需要的目標金額可以是100元。小孩當前的子帳戶餘額是70元，心願達成狀態是“未實現”。所述心願達成狀態可以用於表示所述當前金額是否達到目標金額。
在步驟702中，家長手機將心願資訊發送至伺服器。
例如，伺服器可以儲存心願資訊，如下表4所示。並且，伺服器可以對心願進行管理，比如，根據目標金額和當前金額的比較管理心願達成狀態。
表4 心願信息
在步驟704中，伺服器將心願資訊發送至智慧儲蓄罐顯示。
例如，智慧儲蓄罐可以顯示心願名稱、心願狀態等資訊。小孩透過儲蓄罐的顯示螢幕就可以知道自己有一個未實現的心願。此外，伺服器可以定期或者即時的比較子帳戶的當前餘額和目標餘額，並更新心願達成狀態，將更新後的心願達成狀態發送至儲蓄罐顯示。
此外，上述的例子中，是以一個主帳戶對應一個子帳戶為例。但是具體實施中並不局限於此，比如，一個主帳戶可以對應多個子帳戶，這種情況可以是一個家長有多個小孩，每個小孩都可以各自有一個對應自己的子帳戶，家長的主帳戶都可以向這些子帳戶轉帳。一個子帳戶也可以對應多個主帳戶，比如，一個孩子多個家長，這些家長的主帳戶都可以分別向小孩的子帳戶轉帳。再比如，一個小孩的子帳戶還可以對應多個智慧儲蓄罐，只要由不同的設備標識區分即可，每一個儲蓄罐的綁定和支付使用都可以使用上述的方法。
智慧儲蓄罐的情緒管理
儲蓄罐還可以有擬人化的情緒，以增強互動體驗。儲蓄罐可以根據檢測到的情緒依據資訊，調整設備情緒畫面的顯示。所述的設備情緒畫面的顯示可以是顯示一個笑臉或者哭臉，或者眼睛呈高興狀或者傷心狀等。所述的情緒依據資訊可以有多種，例如，可以依據設備互動頻次，如果小孩經常與儲蓄罐互動，則儲蓄罐可以展現笑臉。又例如，還可以依據任務完成狀態，如果小孩完成任務了，可以展示一個大大的笑臉。再例如，還可以依據心願完成狀態。
圖8示例了智慧儲蓄罐的一個示例性的產品架構圖，如圖8所示，該儲蓄罐可以具有多種功能，例如，可以具有天線以接收信號，可以具有螢幕以顯示相關資訊，可以具有揚聲器、觸感區等多種功能，還可以具有支付相關的安全性群組件。儲蓄罐還可以支援與手機之間的雙離線近場通訊，使得手機和儲蓄罐在沒有網路的情況下可以互動，比如，用手機靠近儲蓄罐碰一下，可以交換資料。
此外，上述的本說明書一個或多個實施例，是以智慧設備顯示的支付碼中攜帶設備標識為例描述。在其他的例子中，還可以有其他的支付方式：
例如，智慧設備產生的支付碼中可以攜帶子帳戶的帳戶標識。支付請求發起端可以掃描支付碼得到該帳戶標識，並將帳戶標識攜帶在向伺服器發送的支付請求中。伺服器在接收到支付請求後，可以根據帳戶標識確定智慧設備對應的子帳戶，並對該子帳戶進行支付處理。
又例如，智慧設備產生的支付碼中還可以是同時攜帶子帳戶的帳戶標識和智慧設備的設備標識。支付請求發起端可以掃描支付碼得到該帳戶標識和設備標識，並且根據帳戶標識確定子帳戶。此時，設備標識可以應用於安全驗證，比如，伺服器可以根據在根據帳戶標識確定子帳戶後，查看預先建立的“主帳戶——設備標識——子帳戶”的綁定關係中，子帳戶對應的設備標識是否是支付請求中攜帶的設備標識。如果是，則表明支付碼支付的智慧設備是正確的，的確是該子帳戶綁定的智慧設備，則伺服器可以繼續允許使用該子帳戶進行支付。否則，如果判斷結果為否，則可能是調換了設備，智慧設備和子帳戶並不具有對應關係，伺服器可以拒絕本次支付。
此外，需要說明的是，上述示例的兩種情況，同樣適用於圖1至圖8的例子中描述的支付方法，比如，伺服器也還是可以建立主帳戶、子帳戶和設備標識的綁定關係，控制設備也同樣可以設置子帳戶的支付條件，伺服器也可以向智慧設備發送任務和心願資訊，等。詳細的可以參見圖1至圖8的實施例中所述，不再贅述。
本實施例的方法，透過設置子帳戶基於主帳戶產生，並且將子帳戶綁定實體的智慧設備，不僅可以實現對子帳戶的控制，而且實現了使用智慧設備進行支付。
此外，在其他的至少一個實施例中，也可以並不設置智慧設備對應的子帳戶，而是由伺服器根據設備綁定請求，建立主帳戶和設備標識的對應關係。並且，設置支付條件時，可以是將支付條件與設備標識對應，而在實際支付時，可以根據支付條件對主帳戶進行支付處理，即支付條件是對應於智慧設備設置的，而支付時由主帳戶按照該支付條件進行處理也是可以的。例如，設置的小孩的儲蓄罐每次支付時最高限額100元，那麼當小孩用儲蓄罐付款時，從小孩家長的主帳戶進行扣款，但是由於是小孩用儲蓄罐顯示支付碼付款，所以此時家長的主帳戶扣款的數額將受到限制，最多100元。而如果家長自己用自己的設備付款時，可以不受該限制。
當不設置子帳戶時，該使用智慧設備進行支付的方法可以包括如下處理：
首先，控制設備向伺服器發送設備綁定請求，所述設備綁定請求中包括：智慧設備的設備標識、以及所述控制設備對應的主帳戶。
接著，伺服器根據設備綁定請求，建立所述主帳戶與設備標識的對應關係。例如，建立大人的主帳戶和小孩的儲蓄罐的設備標識的對應關係。
然後，伺服器接收所述控制設備設置的對應所述設備標識的支付條件，並儲存所述支付條件和所述設備標識的對應關係。這個步驟也相當於為小孩使用儲蓄罐進行支付設置了支付條件，例如，限額或者限次等條件。
在實際進行支付時，智慧設備可以顯示支付碼，以使得支付請求發起端掃描所述支付碼向所述伺服器發起支付請求，所述支付碼中包括：所述智慧設備的設備標識，所述支付請求中攜帶所述設備標識。例如，支付碼可以是付款碼，商家可以掃描該付款碼請求伺服器進行扣款，攜帶設備標識。
最後，所述伺服器在接收到支付請求時，根據所述支付請求中攜帶的設備標識找到對應的支付條件，並在所述支付請求滿足所述支付條件時，對所述主帳戶進行支付處理。例如，伺服器可以判斷是否滿足限額或者是否滿足限次，若滿足，則對大人的主帳戶進行扣款。
為了實現上述方法，本說明書一個或多個實施例提供了一種使用智慧設備進行支付的裝置。如圖9所示，該裝置可以應用於伺服器，該裝置可以包括：請求接收模組91、支付處理模組92。
請求接收模組91，用於接收支付請求，所述支付請求中包括：智慧設備的設備標識；
支付處理模組92，用於根據所述設備標識，對所述設備標識對應的子帳戶進行支付處理；所述子帳戶是基於控制設備對應的主帳戶產生，所述控制設備用於對所述子帳戶進行支付控制。
在一個例子中，如圖10所示，該裝置還可以包括：綁定處理模組93。
所述請求接收模組91，還用於接收所述控制設備發送的設備綁定請求，所述設備綁定請求中包括：所述智慧設備的設備標識以及所述主帳戶的帳戶標識；
綁定處理模組93，用於根據所述設備綁定請求，建立所述主帳戶、所述子帳戶以及所述設備標識三者之間的對應關係。
在一個例子中，支付處理模組92，還用於接收所述控制設備發送的對所述子帳戶設置的支付條件；儲存所述支付條件；在所述支付請求滿足所述支付條件時，對所述子帳戶進行支付處理。
為了實現上述方法，本說明書一個或多個實施例提供了一種使用智慧設備進行支付的裝置。如圖11所示，該裝置可以應用於智慧設備，該裝置可以包括：碼獲取模組1101、碼展示模組1102。
碼獲取模組1101，用於獲取支付碼，所述支付碼是付款碼或者收款碼；
碼展示模組1102，用於展示所述支付碼，以使得支付請求發起端根據所述支付碼請求伺服器對所述智慧設備對應的子帳戶進行支付處理，所述子帳戶是基於控制設備對應的主帳戶產生且由所述控制設備進行支付控制。
如圖12所示，該裝置還包括如下至少一項：
任務顯示模組1103，用於接收並顯示所述伺服器發送的任務資訊，所述任務資訊由所述控制設備創建並發送至伺服器，且所述任務資訊包括如下至少一項：任務名稱、任務金額；接收並顯示所述伺服器發送的子帳戶的更新餘額，所述更新餘額是所述伺服器在接收到所述任務名稱對應的任務完成指令時，由所述主帳戶向所述子帳戶轉入所述任務金額後得到；
心願顯示模組1104，用於接收並顯示所述伺服器發送的心願資訊，所述心願資訊由所述控制設備創建並發送至伺服器，且所述心願資訊包括如下至少一項：心願名稱、目標金額、當前金額以及心願達成狀態，所述心願達成狀態用於表示所述當前金額是否達到目標金額。
為了實現上述方法，本說明書一個或多個實施例提供了一種使用智慧設備進行支付的裝置。如圖13所示，該裝置可以應用於控制設備，該裝置可以包括：標識獲取模組1301、綁定請求模組1302。
標識獲取模組1301，用於獲取智慧設備的設備標識；
綁定請求模組1302，用於向伺服器發送設備綁定請求，所述設備綁定請求中攜帶：所述智慧設備的設備標識、以及主帳戶的帳戶標識；以使得伺服器建立所述主帳戶、所述設備標識以及設備標識對應的子帳戶三者之間的對應關係。
在另一個例子中，如圖14所示，該裝置還可以包括：支付設置模組1303，用於向所述伺服器發送對所述子帳戶設置的支付條件，以使得所述伺服器根據所述支付條件進行支付處理；所述支付條件，包括如下至少一項：支付限額和支付限次。
圖15提供了一種使用智慧設備支付的裝置，該裝置可以應用於伺服器，如圖15所示，可以包括：請求接收模組1501、綁定處理模組1502、條件接收模組1503和支付設置模組1504。
請求接收模組1501，用於控制設備發送的設備綁定請求，所述設備綁定請求中包括：智慧設備的設備標識、以及所述控制設備的主帳戶；
綁定處理模組1502，用於根據所述設備綁定請求，建立所述主帳戶、所述設備標識以及所述智慧設備對應的子帳戶的對應關係；
條件接收模組1503，用於接收所述控制設備發送的子帳戶設置的支付條件；
支付設置模組1504，用於建立所述支付條件和所述子帳戶的對應關係，以在支付請求滿足支付條件時，對所述子帳戶進行支付處理。
上述實施例闡明的裝置或模組，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
為了描述的方便，描述以上裝置時以功能分為各種模組分別描述。當然，在實施本說明書一個或多個實施例時可以把各模組的功能在同一個或多個軟體和/或硬體中實現。
上述圖中所示流程中的各個步驟，其執行順序不限制於流程圖中的順序。此外，各個步驟的描述，可以實現為軟體、硬體或者其結合的形式，例如，本領域技術人員可以將其實現為軟體程式碼的形式，可以為能夠實現所述步驟對應的邏輯功能的電腦可執行指令。當其以軟體的方式實現時，所述的可執行指令可以儲存在記憶體中，並被設備中的處理器執行。
例如，對應於上述方法，本說明書一個或多個實施例同時提供一種智慧設備，該設備可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器透過執行所述指令，用於實現如下步驟：
獲取支付碼，所述支付碼是付款碼或者收款碼；
展示所述支付碼，以使得支付請求發起端根據所述支付碼請求伺服器對所述設備標識對應的子帳戶進行支付處理，所述子帳戶是基於控制設備對應的主帳戶產生且由所述控制設備進行支付控制。
例如，該智慧設備可以是智慧儲蓄罐。
以智慧設備是智慧儲蓄罐為例，該智慧儲蓄罐可以包括：檢測元件，該檢測元件可以用於檢測請求顯示支付碼的觸發。
例如，所述的觸發可以是：
透過手勢做出的所述觸發；
或者，透過所述智慧儲蓄罐上的實體按鍵發出的觸發；
或者，透過所述智慧儲蓄罐上的觸控螢幕發出的所述觸發；
或者，透過聲波發送的所述觸發。
上述的觸發相當於是對智慧儲蓄罐的控制指令，該指令可以是指示智慧儲蓄罐獲取和展示支付碼。則智慧儲蓄罐的處理器可以根據該觸發，展示支付碼。例如，檢測元件可以是攝影鏡頭或者感測器等。此外，上述多種方式的控制指令，也可以是控制智慧儲蓄罐執行其他類型的控制處理。
此外，智慧儲蓄罐展示的支付碼，可以展示在顯示幕上。
在一個例子中，當智慧儲蓄罐產生攜帶設備標識的支付碼時，可以是由智慧儲蓄罐的記憶體儲存唯一標識所述智慧儲蓄罐的設備標識。處理器，分別與所述記憶體和檢測元件連接，可以在所述檢測元件檢測到所述觸發時，根據所述記憶體儲存的設備標識，離線產生攜帶所述設備標識的所述支付碼。
在一個例子中，智慧儲蓄罐可以是透過通信元件與伺服器進行通信連接，該通信元件例如可以是WiFi元件、2G、3G、4G等模組。通信元件可以透過無線和/或有線鏈路與伺服器進行通信，並接收所述伺服器向所述智慧儲蓄罐發送的資料。例如，所述接收的資料可以是任務資訊和心願資訊，該資料可以展示在智慧儲蓄罐的顯示幕上供小孩查看。
在一個例子中，智慧儲蓄罐的檢測元件，還用於檢測情緒依據資訊；處理器可以根據所述感測器元件檢測的情緒依據資訊，調整設備情緒畫面的顯示，並將設備情緒畫面展現在顯示幕上。具體可以參見上面的智慧儲蓄罐的情緒管理的部分描述。
此外，智慧儲蓄罐還可以透過近場通訊元件，與另一個設備進行近場通訊以傳輸資料，比如，用手機靠近儲蓄罐碰一下，可以交換資料。
例如，對應於上述方法，本說明書一個或多個實施例同時提供一種伺服器，該設備可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器透過執行所述指令，用於實現如下步驟：
接收控制設備發送的設備綁定請求，所述設備綁定請求中包括：智慧設備的設備標識、以及所述控制設備的主帳戶；
根據所述設備綁定請求，建立所述主帳戶、所述設備標識以及所述智慧設備對應的子帳戶的對應關係；
接收所述控制設備發送的所述子帳戶設置的支付條件；
建立所述支付條件和所述子帳戶的對應關係，以在支付請求滿足支付條件時，對所述子帳戶進行支付處理。
例如，對應於上述方法，本說明書一個或多個實施例同時提供一種控制設備，該設備可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令，所述處理器透過執行所述指令，用於實現如下步驟：
獲取智慧設備的設備標識；
向伺服器發送設備綁定請求，所述設備綁定請求中攜帶：所述智慧設備的設備標識、以及主帳戶的帳戶標識；以使得所述伺服器建立所述主帳戶、所述設備標識以及所述設備標識對應的子帳戶三者之間的對應關係。
本說明書一個或多個實施例還提供了一種應用於支付的物聯網系統，該系統可以包括：智慧設備、控制設備和伺服器。該系統也可以稱為電子儲蓄系統。
所述伺服器，用於建立所述控制設備對應的主帳戶、所述智慧設備對應的子帳戶和所述智慧設備的設備標識之間的對應關係；並用於根據支付請求，在所述支付請求滿足所述控制設備設置的支付條件時，對所述設備標識對應的子帳戶進行支付處理；
所述智慧設備，用於展示支付碼，以使得支付請求發起端根據所述支付碼向伺服器發送支付請求以請求對所述設備標識對應的子帳戶進行支付處理；
所述控制設備，用於對所述子帳戶設置支付條件，以對所述智慧設備的支付進行控制。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
本領域技術人員應明白，本說明書一個或多個實施例可提供為方法、系統或電腦程式產品。因此，本說明書一個或多個實施例可採用完全硬體實施例、完全軟體實施例或結合軟體和硬體方面的實施例的形式。而且，本說明書一個或多個實施例可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、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. One or more embodiments of this specification provide a payment method using a smart device, which applies the aforementioned Internet of Things system to payment. Assuming that the aforementioned Internet of Things device 11 is the smart device, the user 22 can control the smart device through his own control device (eg, the user's mobile phone), where the control may include "payment control" . For example, the smart device may be used for payment (for example, payment or collection), and the user 22 may control the payment conditions such as the limit and limit of the smart device when paying. The following is an example of a scenario applied to an IoT system for payment: Please refer to the example in FIG. 2, a parent A and a child B. In order to educate the child B in financial and business education, and cultivate the child’s awareness of saving and spending money, parent A can Buy a smart piggy bank C for kid B. However, it should be noted that the smart piggy bank C of this embodiment does not store cash, but is associated with a sub-account D in the cloud. The amount of money in the piggy bank is determined by the virtual currency in the sub-account D. Further, there is a master account E, which is the account of parent A, for example, the Alipay account of parent A. Parent A can manage the funds in his main account E through mobile phone F. However, because child B is young, he cannot control the funds in sub-account D like parent A, but parent A also controls the sub-account of child B through mobile phone F, including the generation and use of sub-accounts. Can be controlled by Parent A. The information such as the balance of the sub-account D and the use result can be displayed by the smart piggy bank C, and the child B can conveniently view it through the smart piggy bank C. In this way, the use of the smart piggy bank C not only allows the child B to visually see the use of his own funds through the physical device, but also is more conducive to cultivating financial quotients, and also prevents the child from leaving parent A’s control Safe use of funds. Furthermore, as shown in FIG. 2, the linkage (eg, transfer, etc.) and management between the main account E and the sub-account D in the cloud can be controlled by the server G. The above uses a smart piggy bank as an example to illustrate the application of the payment scenario of the Internet of Things system. Of course, the actual use is not limited to this, and other application scenarios or other types of smart devices can also use this method. For example, a smart device may not be a smart piggy bank, but a portable device such as a bracelet or a watch worn by children. Next, taking the smart device as a smart piggy bank as an example, how to use the smart piggy bank for payment according to the method of the embodiment of the present specification will be described. The description will be divided into several scenarios: The device binding assumes that parent A in Figure 2 has just bought a smart piggy bank C for child B (of course, the actual piggy bank appearance is not limited to that shown in Figure 2, and you can freely design various Appearance), Parent A wants to develop child B's financial awareness. Then, the first thing parents should do is to bind their mobile phone F (ie, control device, taking mobile phone as an example) to the smart piggy bank C, so that they can control the payment or information display processing of the smart piggy bank C. . FIG. 3 illustrates a process of binding a parent’s mobile phone to a smart piggy bank, which may include: In step 300, the parent’s mobile phone obtains a device identifier of the smart piggy bank. For example, a QR code can be posted on the smart piggy bank, and the parent's mobile phone can scan the QR code to obtain the device ID of the smart piggy bank. In one example, a payment application can be installed on the parent's mobile phone, and the payment application can be opened, and the above-mentioned QR code can be scanned through the "scan" function in the payment application. In other examples, parents can also manually enter the device ID of the smart piggy bank directly in the mobile phone payment application. The device identification can uniquely identify a smart piggy bank. In step 302, the parent mobile phone sends a device binding request to the server, where the device binding request carries: the device ID of the smart piggy bank, the account ID of the main account, and the sub-account. For example, an application scenario may take the form that the parent’s mobile payment application has been bound to the parent’s own main account during registration, and the parent has previously created a sub-account for the child, and the sub-account has been pre-established with The correspondence between the master accounts. After the parents purchase the smart piggy bank for the child, they can bind the smart piggy bank to the child account already mentioned by the child. During operation, the parent can click "add device" for the child's sub-account on the business interface of the payment application. Then, the device identification can be obtained by "scanning" in step 300. Parents can continue to click "OK to add device" in the business interface, then the parent's mobile phone can send the device binding to the server (for example, the server can be both the server of the payment application and the server for managing smart devices) The request carries: the device identification, the main account and the sub-account of the smart piggy bank. In another example, perhaps the parent has not yet created a sub-account for the child, but first purchased a smart piggy bank. In this case, when adding a device by scanning the code, the parent can choose which child to add the device to. The device binding request can carry the device ID and the main account of the smart piggy bank, and the server side creates one for the above child according to the request Sub-account, and bind the sub-account with the device identification of the child's smart piggy bank. Or, the parent may only bind the main account and the smart piggy bank first, and no sub account corresponding to the smart piggy bank has been generated for the time being. However, before the sub-account is created, the smart piggy bank cannot be used for payment, and the payment of the smart piggy bank is realized through the sub-account. When the subsequent parent generates a sub-account for the child, the sub-account can be bound to the smart piggy bank, and then the smart piggy bank can be used. In step 304, the server establishes the correspondence between the main account, the device identification, and the sub-account. As shown in Table 1 below, the server can establish a binding relationship between the three: Table 1 Binding relationship The establishment of the binding relationship shows that on the one hand, the smart piggy bank already has a corresponding sub-account, which can be used for subsequent sub-account balance display and payment operations. On the other hand, parents can already control the sub-account through their own mobile phones. Payment and display. In step 306, after the binding is completed, the server may return a response that the binding is successful to the parent's mobile phone. For example, the business interface of the parent’s mobile phone can display "Add device successfully! You can have your own piggy bank, go and try it." In addition, the Smart Piggy Bank can be networked to facilitate the reception of information sent by the server, such as sub-account balances and payment results at the time of payment. For example, when the Smart Piggy Bank uses RTOS (Real-time Operation System), the network mode of the Smart Piggy Bank can be activated, and the Piggy Bank can monitor the account and password broadcast when the parent’s mobile phone is connected to WiFi, thereby performing WiFi networking . For another example, when the smart piggy bank uses the Android operating system, the account and password for WiFi can be directly set on the piggy bank for networking. Payment condition setting After completing the above device binding operation, parents can set the payment condition of the sub-account through the mobile phone in order to control the payment transaction of the child using the smart piggy bank. FIG. 4 exemplifies the process of setting the payment of the smart piggy bank by the parent mobile phone, which may include: In step 400, the parent mobile phone sends the payment conditions set for the sub-account to the server. The payment conditions in this step may include at least one of the following: payment limit and payment limit. For example, the payment limit may be the highest amount for each payment, or the sum of the highest payment within a period of time. The payment limit may be the highest number of payments within a preset time period (for example, one day). In step 402, the server stores the payment conditions. For example, after the server stores the payment conditions, Table 1 can be changed as shown in Table 2: Table 2 Binding Relationship In step 404, the server may return a response to the parent mobile phone that the payment setting is successful. After the above settings, when the smart piggy bank is used for payment, it will be subject to the above payment conditions. Use Smart Piggy Bank for Payment Before using Smart Piggy Bank for payment, you must ensure that there is a balance in the sub-account corresponding to Smart Piggy Bank. If there is no balance, the parent can transfer part of the amount to the child’s sub-account. For example, the parent’s mobile phone can send a transfer request to the server through the service agent to the server, carrying the transfer amount, and the server can use the request , From the parent’s main account to the child’s sub-account. In addition, when the smart piggy bank is connected to the Internet, the server can send the latest balance of the sub-account to the smart piggy bank after the transfer is successful, so that the child can check how much money he has on the smart piggy bank. In an exemplary scenario, assuming that a child wants to make a payment for shopping, the child can pay with his own smart piggy bank. Figure 5 illustrates the payment process of the piggy bank. The payment process is used as an example. Of course, in other scenarios, the piggy bank can also be used to collect money. In step 500, the smart piggy bank obtains a payment code, and the payment code includes: the device identifier of the smart piggy bank. In this step, the payment code can be generated offline by the smart piggy bank. Or, it may be generated by the server and sent to the smart piggy bank when the smart piggy bank is networked. The trigger generated by the payment code may be, for example, a touch key on the screen of the piggy bank, or a physical key of the piggy bank, or a sonic voice trigger, or an image recognition gesture trigger. The piggy bank can start to obtain the payment code when it receives the above sound wave, key press and other triggers. In addition, the above-mentioned multiple triggering methods can not only be applied to trigger the generation of payment codes, but also trigger other processing of the piggy bank. For example, the piggy bank can detect the control instruction and execute the corresponding control processing according to the instruction. The triggering methods of the instruction include but are not limited to the above-mentioned gestures, physical keys, touch screen, sound wave and other methods. The executed control process can also be other processes such as querying the sub-account balance, viewing the latest task display, etc. Exemplarily, taking gestures as an example, the piggy bank can recognize various user gestures and perform them through sensors or camera lenses Corresponding processing, for example, if the user swipes twice to query the balance. For example, the payment code can carry the device identification of the smart piggy bank. In step 502, the smart piggy bank displays the payment code. For example, the smart piggy bank can display the payment code on the screen, so that the payment request originator (that is, the payee) can scan the payment code, initiate a payment request to the server, and carry the wisdom in the payment code in the payment request Equipment identification of piggy bank. Alternatively, the beneficiary can also send the QR code to the server for analysis, and the server can obtain the device identification through analysis. In step 504, the server receives the payment request, and the payment request includes the device identification of the smart piggy bank. The payment request may also include the payment amount of this payment. In step 506, the server uses the sub-account as a payment account according to the device identification, and determines whether the current payment request meets the preset payment conditions. For example, the server may obtain the sub-account corresponding to the device identification and payment conditions according to Table 2. Taking the payment condition as a limit, for example, the server can determine whether the payment amount for this payment is within the limit. Assuming the limit is 100 yuan and the payment amount is 50 yuan, the payment condition is met. If the payment conditions are not met, the server can return to the payee the response information that the payment does not meet the payment conditions and the payment fails. If the smart piggy bank is networked, the server can also send the response information to the piggy bank to display on the piggy bank screen for children to view. Or, even if the smart piggy bank is not currently connected to the Internet, the server can send the response information to the piggy bank when the piggy bank is online. If the payment condition is satisfied, the server may continue to perform step 508. In step 508, the server uses the sub-account as the payment account and transfers the preset payment amount to the collection account. In step 510, the server may return the payment result to the smart piggy bank, for example, the payment is successful. In addition, the above example takes the payment code as an example. The smart piggy bank can also be used for collection, and a collection code can be generated. The collection code can also include the device identification of the smart piggy bank. The account makes a payment request for payment, uses the sub-account as the collection account, and the payment account transfers the preset collection amount to the sub-account. In addition to the above payment scenarios, smart piggy banks can also have a variety of ways to train children's financial merchants. For example, parents can create "tasks" and "wishes" for children, and children can check whether the tasks and wishes are fulfilled on the side of their smart piggy bank. Among them, the "task" may be that the parent instructs a child to do something, such as washing dishes, and after the child finishes the work, the parent gives the child a certain reward. In this task scenario, the child can use the screen display of the Smart Piggy Bank to check what the task created by the parent is, and how much the reward amount can be obtained for this task, and can also see the completion of the task on the screen of the Piggy Bank. The amount of the sub-account changes, so that the child has a very intuitive money-making experience. Among them, the "wish" can be a child's own desire, but this desire can be created by the parent to help the child, and displayed on the screen of the child's smart piggy bank. Children can view the progress of their wish through real-time display on the screen of the piggy bank. For example, suppose the child's wish is to have a rag doll, and this rag doll requires 100 yuan to buy, then the "wish" can be "buy doll, 100 yuan." Moreover, the piggy bank can also show that the current amount of the child's account is 70 yuan, has not yet reached the wish. This kind of wishing scene also helps to cultivate children's sense of saving money and save money for their own wishes. The above tasks and aspirations are just two examples. The actual implementation is not limited to this. A variety of rich financial scenarios can be formed according to specific business settings, and combined with the display of a smart piggy bank to achieve financial interaction between parents and children. The following is a brief description of the interaction between the "task" and "wish" scenarios: Smart Piggy Bank Display Task Figure 6 illustrates the task display process, which may include: In step 600, the parent's mobile phone creates task information, the task information includes at least the following One item: task name, task amount. For example, the task name of the created task can be "Dishwashing". This task requires children to do it. After the child completes the task, the reward amount can be 10 yuan. Then the mission information can include: "Dishwashing, 10 yuan". In step 602, the parent's mobile phone sends the task information to the server. For example, the server can store task information, as shown in Table 3 below. And, the server can manage the tasks, for example, manage the status of the tasks and transfer funds when the tasks are completed. Table 3 Task information In step 604, the server sends the task information to the smart piggy bank for display. For example, the smart piggy bank can display information such as task name, task amount, and task status. Through the display screen of the piggy bank, children can know that they have an unfinished task to wash dishes, and know that they can get a reward of 10 yuan after completing the task. In addition, the task information can also be set more complicated, for example, "wash the dishes today" or "wash the dishes twice". Parents can negotiate task information with children. In step 606, the server receives a task completion instruction corresponding to the task name. In this step, the task completion instruction may be sent from the parent's mobile phone to the server, for example, the parent clicks "task completion" on the business interface of the mobile phone. Or it can be initiated by the child in the smart piggy bank. For example, after the child has washed the dishes, he can click the task on the smart piggy bank to complete. Figure 6 takes the parent initiative as an example. In step 608, the server transfers the task amount from the main account to the sub-account according to the instruction. For example, after the task is completed, the server can transfer 10 yuan from the parent's main account to the child's sub-account to complete the reward for the child. At this time, the child's sub-account has an updated balance, for example, the original balance is 50, and now the updated balance is 60 yuan. In step 610, the server sends the updated balance of the sub-account to the smart piggy bank. In this step, the Smart Piggy Bank can display the updated balance of the sub-account, and it can also display "Your account is increased by 10 yuan, and the updated balance is 60 yuan", so that the child has a more intuitive money-making experience. Wisdom Piggy Bank Display Wish Figure 7 illustrates the process of wish display, which may include: In step 700, the parent mobile phone creates wish information, and the task information includes at least one of the following: wish name, target amount, current amount, and wish fulfillment status . For example, the created wish name may be "buy a rag doll", and the target amount required to realize the wish may be 100 yuan. The child's current sub-account balance is 70 yuan, and the wish fulfillment status is "unrealized". The wish fulfillment status may be used to indicate whether the current amount has reached the target amount. In step 702, the parent's mobile phone sends the desired information to the server. For example, the server can store the wish information, as shown in Table 4 below. And, the server can manage the wish, for example, according to the comparison of the target amount and the current amount to manage the wish fulfillment status. Table 4 Wish information In step 704, the server sends the wish information to the smart piggy bank for display. For example, the smart piggy bank can display information such as the wish name and wish status. Children can know that they have an unfulfilled wish through the display screen of the piggy bank. In addition, the server can periodically or instantly compare the current balance and the target balance of the sub-account, update the wish fulfillment status, and send the updated wish fulfillment status to the piggy bank for display. In addition, in the above example, a main account corresponds to a sub-account as an example. However, the specific implementation is not limited to this. For example, a main account can correspond to multiple sub-accounts. In this case, a parent has multiple children, and each child can have its own sub-account. Accounts can transfer funds to these sub-accounts. A sub-account can also correspond to multiple main accounts, for example, a child with multiple parents, the main accounts of these parents can be transferred to the child's sub-account. As another example, a child's sub-account can also correspond to multiple smart piggy banks, as long as they are distinguished by different device identifiers, the binding and payment of each piggy bank can use the above method. Emotional management of smart piggy banks can also have anthropomorphic emotions to enhance the interactive experience. The piggy bank can adjust the display of the device's emotional picture based on the detected emotional basis information. The display of the emotional picture of the device may be a smile face or a cry face, or the eyes are happy or sad. There can be many kinds of emotion-based information, for example, it can be based on the frequency of device interaction. If a child often interacts with a piggy bank, the piggy bank can show a smiling face. For another example, it can also be based on the task completion status. If the child completes the task, he can show a big smile. As another example, the state of completion can also be based on wish. FIG. 8 illustrates an exemplary product architecture diagram of a smart piggy bank. As shown in FIG. 8, the piggy bank can have multiple functions, for example, an antenna to receive signals, a screen to display related information, and a speaker , Touch-sensitive area and other functions, can also have payment-related security group components. The piggy bank can also support dual offline near-field communication with the mobile phone, so that the mobile phone and the piggy bank can interact without the Internet. For example, by touching the mobile phone near the piggy bank, you can exchange data. In addition, the above one or more embodiments of the specification are described by taking the device identifier carried in the payment code displayed by the smart device as an example. In other examples, there may be other payment methods: For example, the payment code generated by the smart device may carry the account ID of the sub-account. The payment request originator may scan the payment code to obtain the account identification, and carry the account identification in the payment request sent to the server. After receiving the payment request, the server may determine the sub-account corresponding to the smart device according to the account identifier and perform payment processing on the sub-account. For another example, the payment code generated by the smart device may also be an account identification that carries both the sub-account and the device identification of the smart device. The initiator of the payment request may scan the payment code to obtain the account identification and device identification, and determine the sub-account according to the account identification. At this time, the device ID can be used for security verification. For example, after determining the sub-account based on the account ID, the server can view the pre-established binding relationship between the "main account-device ID-sub-account". Whether the corresponding device identifier is the device identifier carried in the payment request. If it is, it indicates that the smart device paid by the payment code is correct, and indeed the smart device bound to the sub-account, then the server may continue to allow the use of the sub-account for payment. Otherwise, if the judgment result is no, it may be that the device is exchanged, the smart device and the sub-account do not have a corresponding relationship, and the server may reject the payment. In addition, it should be noted that the two cases of the above example are also applicable to the payment methods described in the examples of FIGS. 1 to 8, for example, the server can still establish the binding relationship between the main account, the sub account and the device ID. The control device can also set the payment terms of the sub-account, and the server can also send tasks and wish information to the smart device, etc. For details, please refer to the description in the embodiments of FIG. 1 to FIG. 8, which will not be repeated here. In the method of this embodiment, by setting the sub-account to be generated based on the main account, and binding the sub-account to the entity's smart device, not only can the sub-account be controlled, but also the smart device can be used for payment. In addition, in at least one other embodiment, the sub-account corresponding to the smart device may not be set, but the server may establish the correspondence between the main account and the device identification according to the device binding request. In addition, when setting the payment conditions, the payment conditions can be corresponding to the device identification, and in actual payment, the main account can be processed according to the payment conditions, that is, the payment conditions are set corresponding to the smart device, and the payment is determined by the main It is also possible that the account is processed according to the payment conditions. For example, if the child’s piggy bank has a maximum limit of 100 yuan per payment, then when the child pays with the piggy bank, the child’s parent’s main account will be deducted, but because the child uses the piggy bank to display the payment code for payment, so this The amount of the parent’s main account deduction will be limited to a maximum of 100 yuan. And if the parents pay with their own devices, they can be exempted from this restriction. When no sub-account is set up, the method of using a smart device for payment may include the following processing: First, the control device sends a device binding request to the server. The device binding request includes: the device identification of the smart device, and all Describe the master account corresponding to the control device. Next, the server establishes the correspondence between the master account and the device identification according to the device binding request. For example, the correspondence between the main account of an adult and the device identification of a child's piggy bank is established. Then, the server receives the payment condition set by the control device corresponding to the device identification, and stores the correspondence relationship between the payment condition and the device identification. This step is also equivalent to setting payment conditions for children to use a piggy bank for payment, for example, a limit or a limit. During actual payment, the smart device may display a payment code, so that the payment request originator scans the payment code to initiate a payment request to the server, and the payment code includes: the device identification of the smart device, the The payment request carries the device identification. For example, the payment code may be a payment code, and the merchant may scan the payment code to request the server to debit and carry the device identification. Finally, when receiving the payment request, the server finds the corresponding payment condition according to the device identifier carried in the payment request, and performs payment processing on the master account when the payment request meets the payment condition . For example, the server can determine whether the limit is met or whether the limit is met, and if so, the master account of the adult is deducted. In order to implement the above method, one or more embodiments of this specification provide an apparatus for payment using a smart device. As shown in FIG. 9, the device can be applied to a server, and the device can include a request receiving module 91 and a payment processing module 92. The request receiving module 91 is used to receive a payment request, and the payment request includes: a device identifier of a smart device; and a payment processing module 92 is used to pay a sub-account corresponding to the device identifier according to the device identifier Processing; the sub-account is generated based on the main account corresponding to the control device, and the control device is used to perform payment control on the sub-account. In an example, as shown in FIG. 10, the device may further include: a binding processing module 93. The request receiving module 91 is further configured to receive a device binding request sent by the control device, where the device binding request includes: the device identifier of the smart device and the account identifier of the master account; binding The processing module 93 is configured to establish a correspondence between the main account, the sub-account, and the device identification according to the device binding request. In one example, the payment processing module 92 is further configured to receive the payment condition set for the sub-account sent by the control device; store the payment condition; when the payment request meets the payment condition, The sub-account performs payment processing. In order to implement the above method, one or more embodiments of this specification provide an apparatus for payment using a smart device. As shown in FIG. 11, the device can be applied to smart devices. The device can include a code acquisition module 1101 and a code display module 1102. The code obtaining module 1101 is used to obtain a payment code, and the payment code is a payment code or a collection code; the code display module 1102 is used to display the payment code, so that the payment request originating terminal requests the payment code The server performs payment processing on the sub-account corresponding to the smart device, the sub-account is generated based on the main account corresponding to the control device and the payment control is performed by the control device. As shown in FIG. 12, the device further includes at least one of the following: a task display module 1103, configured to receive and display task information sent by the server, and the task information is created by the control device and sent to the server , And the task information includes at least one of the following: task name, task amount; receiving and displaying the updated balance of the sub-account sent by the server, the updated balance corresponds to the server receiving the task name The task completion instruction is obtained from the main account to the sub-account after transferring the task amount; the wish display module 1104 is used to receive and display the wish information sent by the server, the wish information is The control device creates and sends to the server, and the wish information includes at least one of the following: a wish name, a target amount, a current amount, and a wish fulfillment state, the wish fulfillment state is used to indicate whether the current amount reaches a goal Amount. In order to implement the above method, one or more embodiments of this specification provide an apparatus for payment using a smart device. As shown in FIG. 13, the apparatus can be applied to a control device. The apparatus can include: an identification acquisition module 1301 and a binding request module 1302. The identifier obtaining module 1301 is used to obtain a device identifier of a smart device; the binding request module 1302 is used to send a device binding request to a server, and the device binding request carries: the device identifier of the smart device, And the account identification of the main account; so that the server establishes a correspondence between the main account, the device identification, and the sub-account corresponding to the device identification. In another example, as shown in FIG. 14, the device may further include: a payment setting module 1303, configured to send the payment condition set for the sub-account to the server, so that the server may determine The payment conditions are used for payment processing; the payment conditions include at least one of the following: a payment limit and a payment limit. FIG. 15 provides an apparatus for payment using a smart device. The apparatus can be applied to a server. As shown in FIG. 15, it can include: a request receiving module 1501, a binding processing module 1502, a conditional receiving module 1503, and payment settings Module 1504. The request receiving module 1501 is used to control the device binding request sent by the device. The device binding request includes: the device identification of the smart device and the master account of the control device; the binding processing module 1502 is used to According to the device binding request, establish a correspondence between the main account, the device identification, and the sub-account corresponding to the smart device; the conditional receiving module 1503 is configured to receive the sub-account settings sent by the control device Payment conditions; The payment setting module 1504 is used to establish the corresponding relationship between the payment conditions and the sub-accounts, so as to perform payment processing on the sub-accounts when the payment request meets the payment conditions. 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 e-mail sending and receiving device, a game A console, 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 a smart 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: acquiring a payment code, the payment code is a payment code or a collection code; displaying the payment code, so that the payment request originating end requests the server according to the payment code Performing payment processing on the sub-account corresponding to the device identifier, the sub-account is generated based on the main account corresponding to the control device and the control device performs payment control. For example, the smart device may be a smart piggy bank. Taking an example in which the smart device is a smart piggy bank, the smart piggy bank may include: a detection element, and the detection element may be used to detect a trigger requesting to display a payment code. For example, the trigger may be: the trigger made by a gesture; or the trigger issued by a physical key on the smart piggy bank; or, the trigger issued by a touch screen on the smart piggy bank The trigger; or, the trigger sent through the sound wave. The above trigger is equivalent to a control instruction for the smart piggy bank. The instruction may be to instruct the smart piggy bank to obtain and display the payment code. Then, the processor of the smart piggy bank can display the payment code according to the trigger. For example, the detection element may be a photographic lens or a sensor. In addition, the control commands in the above various ways may also be used to control the smart piggy bank to execute other types of control processing. In addition, the payment code displayed by the Smart Piggy Bank can be displayed on the display screen. In one example, when the smart piggy bank generates the payment code carrying the device identification, the smart piggy bank may store the device identifier that uniquely identifies the smart piggy bank. The processor is respectively connected to the memory and the detection element, and when the detection element detects the trigger, the payment code carrying the device identification can be generated offline according to the device identification stored in the memory. In one example, the smart piggy bank may be connected to the server through a communication element, for example, the communication element may be a WiFi element, 2G, 3G, 4G or other modules. The communication element may communicate with the server through wireless and/or wired links and receive data sent by the server to the smart piggy bank. For example, the received data may be task information and wish information, and the data may be displayed on a display screen of a smart piggy bank for children to view. In one example, the detection element of the smart piggy bank is also used to detect emotional basis information; the processor may adjust the display of the device's emotional picture based on the emotional basis information detected by the sensor element, and display the device's emotional picture in On the display. For details, please refer to the above description of the emotional management of the smart piggy bank. In addition, the smart piggy bank can also communicate with another device through near field communication components to transmit data. For example, a mobile phone can be used to exchange data by touching it near the piggy bank. For example, corresponding to the above method, one or more embodiments of the present specification simultaneously provide a server, the device may include a processor, a memory, and computer instructions stored on the memory and executable on the processor, the The processor is used to implement the following steps by executing the instruction: receiving a device binding request sent by a control device, where the device binding request includes: a device identification of a smart device and a master account of the control device; The device binding request, establishing the correspondence between the main account, the device identification, and the sub-account corresponding to the smart device; receiving the payment condition set by the sub-account sent by the control device; establishing the payment condition The corresponding relationship with the sub-account is to process the sub-account when the payment request meets the payment conditions. For example, corresponding to the above method, one or more embodiments of this specification simultaneously provide a control 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 instructions: acquiring the device identification of the smart device; sending a device binding request to the server, the device binding request carrying: the device identification of the smart device and the master account Account identification; so that the server establishes a correspondence between the main account, the device identification, and the sub-account corresponding to the device identification. One or more embodiments of this specification also provide an Internet of Things system applied to payment. The system may include: a smart device, a control device, and a server. The system can also be called an electronic savings system. The server is used to establish a correspondence between the main account corresponding to the control device, the sub-account corresponding to the smart device, and the device identification of the smart device; and according to the payment request, in the payment request When the payment condition set by the control device is satisfied, payment processing is performed on the sub-account corresponding to the device identifier; the smart device is used to display a payment code, so that the payment request originator sends the payment code to the server according to the payment code A payment request to request payment processing for a sub-account corresponding to the device identification; the control device is used to set payment conditions for the sub-account to control the payment of the smart device. 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.
