為使本發明的目的、技術方案和優點更加清楚，下面將結合本發明具體實施例及相應的附圖對本發明技術方案進行清楚、完整地描述。顯然，所描述的實施例僅是本發明一部分實施例，而不是全部的實施例。基於本發明中的實施例，本領域普通技術人員在沒有做出創造性勞動前提下所獲得的所有其他實施例，都屬於本發明保護的範圍。
本說明書實施例提供一種使用者終端、設備、伺服端及使用者終端和設備的綁定方法和系統，用於實現使用者終端和設備的綁定。本說明書實施例中，使用者終端，具體可以是手機、平板電腦、個人電腦等；設備，具體可以是語音播放裝置、智慧家電，如智慧電視、智慧音箱、智慧空調等。伺服端，可以是與多個上述使用者終端和多個上述設備相對應，可以為上述使用者終端和上述設備提供後臺伺服。
本說明書中提到的實現使用者終端和設備的綁定，主要是在伺服端建立使用者終端和設備的綁定關係，將使用者終端和設備關聯起來，進而便於實現伺服端、使用者終端和設備這三者的資訊互動，例如，使用者利用使用者終端通過伺服端向設備發送控制指令，從而控制設備的運行狀態；又例如，伺服端同時向使用者終端以及與使用者終端綁定的設備推送資訊等。
以下將結合附圖，詳細說明本說明書提供的各個實施例。
如圖1所示，本說明書的一個實施例提供了一種使用者終端和設備的綁定方法，用於實現使用者終端和設備的綁定。該方法應用在包括有使用者終端、設備和伺服端的系統中，該方法的具體流程示意圖如圖1所示，包括下述步驟：
步驟S101：使用者終端獲取關聯標識。其中，所述關聯標識是伺服端根據接收到的、所述使用者終端發送的關聯標識請求，而為該使用者終端唯一分配的。
如前所述，該實施例中的使用者終端可以是手機、平板電腦、個人電腦等，在上述使用者終端中可以安裝有應用程式，通過安裝的應用程式能夠實現與伺服端的資訊互動。
關聯標識，可以是會話標識，具體可以是一串唯一的數位編號，且伺服端可以為不同使用者標識的使用者終端分配不同的關聯標識。
使用者標識，可以是使用者終端內部安裝的應用程式中的使用者ID（如使用者帳號），也可以是使用者終端的終端ID（如使用者終端的設備序列號）等，本實施例不作具體限定。
在步驟S101之前，使用者終端還可以向伺服端發送關聯標識請求；這樣，伺服端根據接收到的關聯標識請求，即可根據使用者終端的使用者標識，為使用者終端分配唯一的關聯標識。
步驟S102：所述使用者終端將所述關聯標識發送至所述設備。
步驟S103：所述設備將所述關聯標識和所述設備的設備標識發送至所述伺服端。
該步驟之前，所述設備可以預先接收所述關聯標識。
設備標識，具體可以是設備的設備ID（如設備的設備序列號等）。
如前所述，該實施例中的設備，具體可以是語音播放裝置、智慧家電等。在上述設備中通常可以內置有通信模組，該通信模組具體可以是無線通信模組，因此，該實施例中，設備可以通過內置的無線通信模組與使用者終端、與伺服端進行通信，即：設備通過內置的無線通信模組接收使用者終端發送的關聯標識，並將所述關聯標識發送至所述伺服端。
在實際應用過程中，建立使用者終端和設備的綁定關係之前，設備還可能未配置網路，因此，設備還可能無法與使用者終端和伺服端進行通信，因此，在設備將所述關聯標識發送至所述伺服端之前，使用者終端還可以為設備配置網路，使設備能夠通過配置的網路與使用者終端和伺服端進行通信。
步驟S104：所述伺服端根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
本說明書實施例提供的上述使用者終端和設備的綁定方法，首先，使用者終端獲取關聯標識，並將所述關聯標識發送至設備，其中，所述關聯標識是伺服端為所述使用者終端分配的；然後，設備接收所述關聯標識，並將所述關聯標識和設備標識發送至伺服端，這樣，伺服端根據所述關聯標識和設備標識，即可建立所述使用者終端和所述設備的綁定關係，實現了使用者終端和設備的綁定。
優選地，作為本說明書的另一個實施例，上述步驟S104伺服端根據接收到的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係之後，伺服端還可以向所述使用者終端和所述設備發送綁定結果資訊，該綁定結果資訊可以包括綁定成功、綁定失敗等。當使用者終端和設備綁定失敗時，還可以按照上述實施例的執行步驟進行重新綁定。
優選地，作為本說明書的另一個實施例，上述步驟S104伺服端建立所述使用者終端和所述設備的綁定關係之後，伺服端還可以根據所述使用者終端的操作行為，向所述使用者終端和所述設備推送操作行為結果資訊。
例如，當上述設備具體為語音播報裝置，上述使用者終端具體為手機時，當手機上的即時通信軟體接收到資訊時，伺服端同樣可以將收到的資訊發送至語音播報裝置，從而使該語音播報裝置語音播放上述資訊內容，從而省略了使用者需要打開手機查看資訊的操作。
在上述幾個實施例的步驟S104中提到，所述伺服端可以根據關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係，其中，上述關聯標識，不僅可以是包括設備發送的關聯標識，還可以包括使用者終端發送的關聯標識，以下將結合兩個不同的實施方式來進行詳細說明：
實施方式一：使用者終端向伺服端發送關聯標識請求後，伺服端根據使用者終端的使用者標識為使用者終端分配關聯標識之後，可以同時儲存所述使用者標識與所述關聯標識的映射關係。這樣，在上述實施例的步驟S104中，伺服端在接收到設備發送的關聯標識和設備標識後，即可遍歷查找當前已經儲存的關聯標識，若查找得到相同的關聯標識，則根據與查找到的關聯標識相映射的使用者標識，以及所述設備的設備標識，即可建立所述使用者終端和所述設備的綁定關係。
實施方式二：伺服端在為使用者終端分配關聯標識之後，伺服端無需儲存使用者終端的使用者標識以及分配的關聯標識的映射關係，但是，上述實施例的步驟S103所述設備將所述關聯標識和所述設備的設備標識發送至所述伺服端的步驟之後，還可以包括如下步驟：
所述使用者終端將所述關聯標識和所述使用者終端的使用者標識發送至所述伺服端，這樣，
上述實施例的步驟S104：所述伺服端根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係，具體可以包括：
所述伺服端根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
上述實施方式二中，伺服端以接收到設備發送的關聯標識為准，對設備發送的關聯標識和設備標識進行儲存，當接收到使用者終端發送的關聯標識之後，即可遍歷查找已經儲存的關聯標識，若查找得到相同的關聯標識，則根據與查找到的關聯標識相對應的設備標識，以及所述使用者終端的使用者標識，即可建立所述使用者終端和所述設備的綁定關係。
該實施方式二以設備發送關聯標識為准（主要是指儲存設備標識和關聯標識），更加切合實際。因為在實際應用中，使用者終端可能會誤操作向設備發送關聯標識和使用者標識等，此時，可能沒有建立綁定的需求。當伺服端接收到設備發送的關聯標識和設備標識後，這在很大程度上有建立綁定的需求，避免伺服端儲存過多的資源（即：實施方式一中儲存的使用者標識和關聯標識），造成伺服端冗餘儲存，從而節約了儲存資源。
優選地，作為本說明書的另一個實施例，上述實施例的步驟S103中所述設備將所述關聯標識和所述設備的設備標識發送至所述伺服端的步驟之前，所述實施例還可以包括如下步驟：所述設備接收所述使用者終端發送的預定無線網路的使用者名和密碼；所述設備根據所述使用者名和密碼連接所述預定無線網路，即，使用者終端可以預先為設備配置無線網路。
通過上述使用者終端為設備配置無線網路的操作，使設備能夠通過連接的預定無線網路與伺服端進行互動，這樣，上述實施例的步驟S103所述設備將所述關聯標識和所述設備的設備標識發送至所述伺服端的步驟，具體可以是：所述設備根據連接的預定無線網路，通過所述預定無線網路將所述關聯標識和所述設備的設備標識發送至所述伺服端。
優選地，作為本說明書的另一個實施例，上述實施例的步驟S101中使用者終端獲取關聯標識的步驟之前，所述實施例還可以包括如下步驟：
所述使用者終端獲取所述設備的條碼標識；該處條碼標識可以包括二維條碼標識、一維條碼標識等，並且，多個所述設備的條碼標識可以相同；
根據獲取到的條碼標識，向所述伺服端發送關聯標識請求。
這樣，多個設備上可以印刷相同的二維條碼（或一維條碼），使用者終端通過掃描二維條碼即可打開配置頁面，從而向伺服端發送關聯標識請求。通過在多個設備上印刷相同的二維條碼的操作，簡化了設備的生產工藝，節約了設備的生產成本。
優選地，為詳細說明本說明書實施例提供的使用者終端和設備的綁定方法，以下將結合一具體的優選實施例為例進行說明，如圖2所示，該實施例包括如下步驟：
步驟S201：使用者終端掃描設備上的二維條碼。
該實施例中，多個不同的設備上可以包括有相同的二維條碼，使用者可以通過使用者終端掃描上述二維條碼從而自動觸發打開設備配置頁面。
步驟S202：使用者終端打開設備配置頁面；
在該配置頁面上，可以有特定功能的按鈕，例如關聯標識請求按鈕，這樣，當使用者點擊關聯標識按鈕則可以執行步驟S203。
當然，在打開配置頁面的同時，無需使用者操作，使用者終端也可以自動執行步驟S203。
步驟S203：使用者終端向伺服端發送關聯標識請求。
步驟S204：使用者終端獲取關聯標識。
該步驟中，使用者終端可以主動從伺服端獲取關聯標識；當然，使用者終端還可以是被動接收伺服端返回的關聯標識，即伺服端為使用者終端分配關聯標識後即將分配的關聯標識發送至使用者終端。
步驟S205：使用者終端向設備發送所述關聯標識。
該步驟之前，設備可能還未配置網路，因此，使用者終端向設備發送所述關聯標識的同時，使用者終端還可以通過smartConfig技術為設備配置網路，在一種具體的實施方式中：
使用者終端可以發送包含有預定無線網路的使用者名、密碼以及關聯標識的使用者資料報協議UDP廣播包；
所述設備的無線通信模組可以接收到該UDP廣播包，使用者終端和設備可以預先約定協議，協議中規定有UDP廣播包的格式，這樣，設備根據上述約定的協議，即可從接收到的UDP廣播包中解析出預定無線網路的使用者名和密碼、關聯標識等；
然後所述設備配置收到的預定無線網路的使用者名和密碼到預定無線網路上，即可連接無線網路。
步驟S206：設備向伺服端發送設備標識和關聯標識。
該處的設備標識可以是設備的設備ID。
設備具體可以是通過步驟S205中連接的預定無線網路向伺服端發送設備標識和關聯標識，當然，伺服端可以儲存設備發送的設備標識和關聯標識。
步驟S207：使用者終端向伺服端發送使用者標識和關聯標識；
該步驟中，使用者終端具體可以採用輪詢的方式，向伺服端發送綁定請求，綁定請求中可以包括有使用者標識和關聯標識。
步驟S208：伺服端建立綁定關係。
伺服端在接收到使用者終端發送的使用者標識和關聯標識時，可以查詢是否己經有設備發送過關聯標識和設備標識，如果是，即，己經有設備發送過關聯標識和設備標識，則伺服端即可將當前使用者標識和設備標識進行關聯，實現使用者終端和設備的綁定。
步驟S209：伺服端向設備發送綁定結果資訊。
步驟S210：伺服端向使用者終端發送綁定結果資訊。
在步驟S208中伺服端建立使用者終端和設備的綁定關係之後，伺服端還可以通過步驟S209和步驟S210分別向設備和使用者終端發送綁定結果資訊，該綁定結果資訊可以包括綁定成功或綁定失敗等。
優選地，作為本說明書的另一個實施例，當使用者終端和設備綁定成功後，伺服端還可以根據所述使用者終端的操作行為，向所述使用者終端和所述設備推送操作行為結果資訊。
如圖3所示，本說明書還提供了一種使用者終端和設備的綁定方法300，可以應用在使用者終端，如圖3所示，該方法300包括如下步驟：
步驟S301：獲取關聯標識，其中，所述關聯標識是伺服端為所述使用者終端分配的；
步驟S302：將所述關聯標識發送至設備，所述關聯標識用於所述設備將所述關聯標識和所述設備的設備標識發送至伺服端，以使所述伺服端建立所述使用者終端和所述設備的綁定關係。
本說明書實施例提供的上述使用者終端和設備的綁定方法，首先，使用者終端獲取關聯標識，並將所述關聯標識發送至設備，所述關聯標識用於所述設備將所述關聯標識和所述設備的設備標識發送至伺服端，以使所述伺服端建立所述使用者終端和所述設備的綁定關係，實現了使用者終端和設備的綁定。
優選地，作為一個實施例，步驟S302之後，還可以將所述關聯標識和所述使用者終端的使用者標識發送至所述伺服端，這樣，所述伺服端根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述關聯標識是伺服端基於所述使用者終端的使用者標識為所述使用者終端分配的，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；所述伺服端可以根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，步驟S302之後，還可以向所述設備發送的預定無線網路的使用者名和密碼；使所述設備根據所述使用者名和密碼連接所述預定無線網路。
優選地，作為一個實施例，步驟S301之前，還可以獲取所述設備的條碼標識；根據獲取到的條碼標識，向所述伺服端發送關聯標識請求。所述條碼標識包括二維條碼標識，並且，多個所述設備的所述二維條碼標識相同。
優選地，作為一個實施例，步驟S302之後，還可以接收伺服端發送的綁定結果資訊。
如圖4所示，本說明書還提供了一種使用者終端和設備的綁定方法400，可以應用在設備，如圖4所示，該方法400包括如下步驟：
步驟S401：接收使用者終端發送的關聯標識，其中，所述關聯標識是伺服端為所述使用者終端分配的；
步驟S402：將所述關聯標識和所述設備的設備標識發送至所述伺服端，以使所述伺服端根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
本說明書實施例提供的上述使用者終端和設備的綁定方法，首先，接收使用者終端發送的關聯標識，然後將所述關聯標識和所述設備的設備標識發送至所述伺服端，以使所述伺服端根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係實現了使用者終端和設備的綁定。
優選地，作為一個實施例，所述使用者終端還可以將所述關聯標識和所述使用者終端的使用者標識發送至所述伺服端，這樣，所述伺服端根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述關聯標識是伺服端基於所述使用者終端的使用者標識為所述使用者終端分配的，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；所述伺服端可以根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，步驟S401之前，還可以接收所述使用者終端發送的預定無線網路的使用者名和密碼；根據所述使用者名和密碼連接所述預定無線網路。
優選地，作為一個實施例，所述設備上還印刷有條碼標識；所述條碼標識包括二維條碼標識，並且，多個所述設備的所述二維條碼標識相同。
優選地，作為一個實施例，步驟S402之後，還可以接收伺服端發送的綁定結果資訊。
如圖5所示，本說明書還提供了一種使用者終端和設備的綁定方法500，可以應用在伺服端，如圖5所示，該方法500包括如下步驟：
步驟S501：為所述使用者終端分配關聯標識，以使所述使用者終端將所述關聯標識發送至所述設備；
步驟S502：接收所述設備發送的所述關聯標識和所述設備的設備標識；
步驟S503：根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
本說明書實施例提供的上述使用者終端和設備的綁定方法，首先，為使用者終端分配關聯標識，以使所述使用者終端將所述關聯標識發送至所述設備；然後接收所述設備發送的所述關聯標識和所述設備的設備標識；這樣，根據所述關聯標識和所述設備標識，即可建立所述使用者終端和所述設備的綁定關係，實現了使用者終端和設備的綁定。
優選地，作為一個實施例，步驟S502之後，還可以接收使用者終端發送的所述關聯標識和所述使用者終端的使用者標識，這樣，步驟S503，具體可以為：根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，步驟S501可以基於所述使用者終端的使用者標識為所述使用者終端分配關聯標識，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；這樣，步驟S503，具體可以為：根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，還可以向所述使用者終端和所述設備發送綁定結果資訊。
優選地，作為一個實施例，還可以根據所述使用者終端的操作行為，向所述使用者終端和所述設備推送操作行為結果資訊。
以上說明書部分詳細介紹了使用者終端和設備的綁定方法實施例，如圖6所示，本說明書還提供了一種使用者終端和設備的綁定系統600，如圖6所示，該系統600包括：
使用者終端601，可以用於獲取關聯標識，並將所述關聯標識發送至所述設備，其中，所述關聯標識是伺服端為所述使用者終端分配的；
設備602，可以用於接收所述關聯標識，並將所述關聯標識和所述設備的設備標識發送至所述伺服端；
伺服端603，可以用於根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
本說明書實施例提供的上述使用者終端和設備的綁定系統，首先，使用者終端獲取關聯標識，並將所述關聯標識發送至設備，其中，所述關聯標識是伺服端為所述使用者終端分配的；然後，設備接收所述關聯標識，並將所述關聯標識和設備標識發送至伺服端，這樣，伺服端根據所述關聯標識和設備標識，即可建立所述使用者終端和所述設備的綁定關係，實現了使用者終端和設備的綁定。
如圖7所示，本說明書還提供了一種使用者終端700，如圖7所示，該使用者終端700，包括：
獲取單元701，可以用於獲取關聯標識，其中，所述關聯標識是伺服端為所述使用者終端分配的；
發送單元702，可以用於將所述關聯標識發送至設備，所述關聯標識用於所述設備將所述關聯標識和所述設備的設備標識發送至伺服端，以使所述伺服端建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述發送單元702，還可以將所述關聯標識和所述使用者終端的使用者標識發送至所述伺服端，這樣，所述伺服端根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述關聯標識是伺服端基於所述使用者終端的使用者標識為所述使用者終端分配的，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；所述伺服端可以根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述發送單元702，還可以向所述設備發送的預定無線網路的使用者名和密碼；使所述設備根據所述使用者名和密碼連接所述預定無線網路。
優選地，作為一個實施例，獲取單元701，還可以獲取所述設備的條碼標識；根據獲取到的條碼標識，向所述伺服端發送關聯標識請求。所述條碼標識包括二維條碼標識，並且，多個所述設備的所述二維條碼標識相同。
優選地，作為一個實施例，獲取單元701，還可以接收伺服端發送的綁定結果資訊。
如圖8所示，本說明書還提供了一種設備800，如圖8所示，該設備800包括：
接收單元801，可以用於接收使用者終端發送的關聯標識，其中，所述關聯標識是伺服端為所述使用者終端分配的；
發送單元802，可以用於將所述關聯標識和所述設備的設備標識發送至所述伺服端，以使所述伺服端根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述使用者終端還可以將所述關聯標識和所述使用者終端的使用者標識發送至所述伺服端，這樣，所述伺服端根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述關聯標識是伺服端基於所述使用者終端的使用者標識為所述使用者終端分配的，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；所述伺服端可以根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，所述接收單元801，還可以接收所述使用者終端發送的預定無線網路的使用者名和密碼；根據所述使用者名和密碼連接所述預定無線網路。
優選地，作為一個實施例，所述設備上還印刷有條碼標識；所述條碼標識包括二維條碼標識，並且，多個所述設備的所述二維條碼標識相同。
優選地，作為一個實施例，接收單元801，還可以接收伺服端發送的綁定結果資訊。
如圖9所示，本說明書還提供了一種伺服端900，如圖9所示，該伺服端900，包括：
分配單元901，為使用者終端分配關聯標識，以使所述使用者終端將所述關聯標識發送至設備；
接收單元902，接收設備發送的所述關聯標識和所述設備的設備標識；
綁定單元903，根據所述關聯標識和所述設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，接收單元902還可以接收使用者終端發送的所述關聯標識和所述使用者終端的使用者標識，這樣，綁定單元903，根據所述設備發送的關聯標識和設備標識，以及所述使用者終端發送的關聯標識和使用者標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，分配單元901基於所述使用者終端的使用者標識為所述使用者終端分配關聯標識，且所述伺服端儲存有所述使用者標識與所述關聯標識的映射關係；這樣，綁定單元903根據所述使用者標識與所述關聯標識的映射關係，以及所述設備發送的關聯標識和設備標識，建立所述使用者終端和所述設備的綁定關係。
優選地，作為一個實施例，分配單元901，還可以向所述使用者終端和所述設備發送綁定結果資訊。
優選地，作為一個實施例，分配單元901，還可以根據所述使用者終端的操作行為，向所述使用者終端和所述設備推送操作行為結果資訊。
下面將結合圖10詳細描述根據本發明實施例的使用者終端、設備和伺服端（上述三者統稱為電子設備）。參考圖10，在硬體層面，電子設備包括處理器，可選地，包括內部匯流排、網路介面、記憶體。其中，如圖10所示，記憶體可能包含記憶體，例如高速隨機存取記憶體（Random-Access Memory，RAM)，也可能還包括非揮發性記憶體（non-volatile memory），例如至少1個磁碟記憶體等。當然，該電子設備還可能包括實現其他業務所需要的硬體。
處理器、網路介面和記憶體可以通過內部匯流排相互連接，該內部匯流排可以是工業標準體系結構 (Industry Standard Architecture，ISA）匯流排、週邊組件互連標準 (Peripheral Component Interconnect，PCI)匯流排或擴展工業標準結構 (Extended Industry Standard Architecture，EISA）匯流排等。所述匯流排可以分為地址匯流排、資料匯流排、控制匯流排等。為便於表示，圖10中僅用一個雙向箭頭表示，但並不表示僅有一根匯流排或一種類型的匯流排。
記憶體，用於存放程式。具體地，程式可以包括程式代碼，所述程式代碼包括電腦操作指令。記憶體可以包括記憶體和非揮發性記憶體，並向處理器提供指令和資料。
處理器從非揮發性記憶體中讀取對應的電腦程式到記憶體中然後運行，在邏輯層面上形成轉發聊天資訊的裝置。處理器，執行記憶體所存放的程式，並具體用於執行本說明書前文所述的方法實施例的操作。
上述圖6至圖9所示實施例揭示的系統、裝置執行的方法可以應用於處理器中，或者由處理器實現。處理器可能是一種積體電路晶片，具有信號的處理能力。在實現過程中，上述方法的各步驟可以通過處理器中的硬體的集成邏輯電路或者軟體形式的指令完成。上述的處理器可以是通用處理器，包括中央處理器（Central Processing Unit，CPU）、網路處理器（Network Processor，NP）等；還可以是數位信號處理器（Digital Signal Processor，DSP）、特殊應用積體電路（Application Specific Integrated Circuit，ASIC）、現場可程式閘陣列程式化（Field－Programmable Gate Array，FPGA）或者其他可程式化邏輯裝置、分散式閘極或者電晶體邏輯裝置、分立硬體組件。可以實現或者執行本發明實施例中的公開的各方法、步驟及邏輯方塊圖。通用處理器可以是微處理器或者該處理器也可以是任何常規的處理器等。結合本發明實施例所公開的方法的步驟可以直接體現為硬體譯碼處理器執行完成，或者用譯碼處理器中的硬體及軟體模組組合執行完成。軟體模組可以位於隨機記憶體，快閃記憶體、唯讀記憶體，可程式化唯讀記憶體或者電可抹除可程式化記憶體、暫存器等本領域成熟的儲存媒體中。該儲存媒體位於記憶體，處理器讀取記憶體中的資訊，結合其硬體完成上述方法的步驟。
圖10所示的電子設備還可執行圖1至圖5的方法，並實現使用者終端和設備的綁定方法在圖1至圖5所示實施例的功能，本發明實施例在此不再贅述。
當然，除了軟體實現方式之外，本發明的電子設備並不排除其他實現方式，比如邏輯裝置抑或軟硬體結合的方式等等，也就是說以下處理流程的執行主體並不限定於各個邏輯單元，也可以是硬體或邏輯裝置。
本說明書實施例還提供一種電腦可讀儲存媒體，電腦可讀儲存媒體上儲存有電腦程式，該電腦程式被處理器執行時實現上述各個方法實施例的各個過程，且能達到相同的技術效果，為避免重複，這裡不再贅述。其中，所述的電腦可讀儲存媒體，如唯讀記憶體（Read-Only Memory，簡稱ROM）、隨機存取記憶體（Random Access Memory，簡稱RAM）、磁碟或者光碟等。
本領域內的技術人員應明白，本發明的實施例可提供為方法、系統、或電腦程式產品。因此，本發明可採用完全硬體實施例、完全軟體實施例、或結合軟體和硬體態樣的實施例的形式。而且，本發明可採用在一個或多個其中包含有電腦可用程式代碼的電腦可用儲存媒體（包括但不限於磁碟記憶體、CD-ROM、光學記憶體等）上實施的電腦程式產品的形式。
本發明是參照根據本發明實施例的方法、設備（系統）、和電腦程式產品的流程圖和／或方方塊圖來描述的。應理解可由電腦程式指令實現流程圖和／或方方塊圖中的每一流程和／或方塊、以及流程圖和／或方方塊圖中的流程和／或方塊的結合。可提供這些電腦程式指令到通用電腦、專用電腦、嵌入式處理機或其他可程式化資料處理設備的處理器以產生一個機器，使得通過電腦或其他可程式化資料處理設備的處理器執行的指令產生用於實現在流程圖一個流程或多個流程和／或方方塊圖一個方塊或多個方塊中指定的功能的裝置。
這些電腦程式指令也可儲存在能引導電腦或其他可程式化資料處理設備以特定方式工作的電腦可讀記憶體中，使得儲存在該電腦可讀記憶體中的指令產生包括指令裝置的製造品，該指令裝置實現在流程圖一個流程或多個流程和／或方方塊圖一個方塊或多個方塊中指定的功能。
這些電腦程式指令也可裝載到電腦或其他可程式化資料處理設備上，使得在電腦或其他可程式化設備上執行一系列操作步驟以產生電腦實現的處理，從而在電腦或其他可程式化設備上執行的指令提供用於實現在流程圖一個流程或多個流程和／或方方塊圖一個方塊或多個方塊中指定的功能的步驟。
在一個典型的配置中，計算設備包括一個或多個處理器 (CPU)、輸入/輸出介面、網路介面和記憶體。
記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體 (RAM) 和/或非揮發性記憶體等形式，如唯讀記憶體 (ROM) 或快閃記憶體(flash RAM)。記憶體是電腦可讀媒體的示例。
電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體 (PRAM)、靜態隨機存取記憶體 (SRAM)、動態隨機存取記憶體 (DRAM)、其他類型的隨機存取記憶體 (RAM)、唯讀記憶體 (ROM)、電可抹除可程式化唯讀記憶體 (EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體 (CD-ROM)、數位多功能光碟 (DVD) 或其他光學儲存、磁盒式磁帶，磁帶式磁碟儲存器或其他磁性儲存設備或任何其他非傳輸媒體，可用於儲存可以被計算設備存取的資訊。按照本文中的界定，電腦可讀媒體不包括暫存電腦可讀媒體 (transitory media)，如調變的資料信號和載波。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括要素的過程、方法、商品或者設備中還存在另外的相同要素。
以上僅為本發明的實施例而已，並不用於限制本發明。對於本領域技術人員來說，本發明可以有各種更改和變化。凡在本發明的精神和原理之內所作的任何修改、等同替換、改進等，均應包含在本發明的申請專利範圍之內。In order to make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be described clearly and completely below in conjunction with specific embodiments of the present invention and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.
The embodiments of this specification provide a method and system for binding a user terminal, a device, a server, and a user terminal and a device, which are used to realize the binding of the user terminal and the device. In the embodiments of this specification, the user terminal may specifically be a mobile phone, a tablet computer, a personal computer, etc.; the device may specifically be a voice playback device, a smart home appliance, such as a smart TV, a smart speaker, and a smart air conditioner. The server end may correspond to a plurality of the aforementioned user terminals and a plurality of the aforementioned devices, and can provide a background server for the aforementioned user terminals and the aforementioned devices.
The realization of the binding between the user terminal and the device mentioned in this manual is mainly to establish the binding relationship between the user terminal and the device on the server side, and associate the user terminal and the device, so as to facilitate the realization of the server side and the user terminal Interact with the information of the three devices, for example, the user uses the user terminal to send control commands to the device through the server to control the operating state of the device; for example, the server simultaneously binds to and binds to the user terminal Device push information, etc.
Hereinafter, various embodiments provided in this specification will be described in detail with reference to the accompanying drawings.
As shown in FIG. 1, an embodiment of this specification provides a binding method of a user terminal and a device, which is used to realize the binding of the user terminal and the device. The method is applied in a system including user terminals, equipment and server. The specific flow diagram of the method is shown in Figure 1, including the following steps:
Step S101: The user terminal obtains the association identification. Wherein, the association identification is uniquely allocated by the server to the user terminal according to the received association identification request sent by the user terminal.
As mentioned above, the user terminal in this embodiment may be a mobile phone, a tablet computer, a personal computer, etc., an application program may be installed in the above user terminal, and information interaction with the server can be realized through the installed application program.
The association identifier may be a session identifier, specifically a string of unique digital numbers, and the server can assign different association identifiers to user terminals with different user identifiers.
The user ID can be the user ID in the application installed inside the user terminal (such as user account), or the terminal ID of the user terminal (such as the device serial number of the user terminal), etc., in this embodiment There is no specific limitation.
Before step S101, the user terminal can also send an association identification request to the server; in this way, the server can assign a unique association identification to the user terminal according to the user identification of the user terminal according to the received association identification request. .
Step S102: The user terminal sends the association identification to the device.
Step S103: The device sends the association identifier and the device identifier of the device to the server.
Before this step, the device may receive the association identifier in advance.
The device identification, which can be the device ID of the device (such as the device serial number of the device, etc.).
As mentioned above, the equipment in this embodiment may specifically be a voice playback device, smart home appliances, and so on. In the above-mentioned device, a communication module can usually be built in, and the communication module can be a wireless communication module. Therefore, in this embodiment, the device can communicate with the user terminal and the server through the built-in wireless communication module. That is, the device receives the associated identification sent by the user terminal through the built-in wireless communication module, and sends the associated identification to the server.
In the actual application process, before the binding relationship between the user terminal and the device is established, the device may not be configured with a network. Therefore, the device may not be able to communicate with the user terminal and the server. Therefore, the device associates the Before the identification is sent to the server, the user terminal can also configure a network for the device, so that the device can communicate with the user terminal and the server through the configured network.
Step S104: The server establishes a binding relationship between the user terminal and the device according to the association identifier and the device identifier.
In the above-mentioned binding method of the user terminal and the device provided by the embodiment of this specification, first, the user terminal obtains the association identification, and sends the association identification to the device, where the association identification is that the server is the user The terminal is assigned; then, the device receives the associated identification, and sends the associated identification and device identification to the server, so that the server can establish the user terminal and the user terminal based on the associated identification and device identification The binding relationship of the devices described realizes the binding of the user terminal and the device.
Preferably, as another embodiment of this specification, after the server establishes the binding relationship between the user terminal and the device according to the received association identifier and device identifier in step S104, the server may also send the The user terminal and the device send binding result information, and the binding result information may include binding success, binding failure, etc. When the binding between the user terminal and the device fails, the binding can also be performed according to the execution steps of the foregoing embodiment.
Preferably, as another embodiment of the present specification, after the server establishes the binding relationship between the user terminal and the device in step S104, the server may also send a notification to the user terminal according to the operation behavior of the user terminal The user terminal and the device push operation behavior result information.
For example, when the aforementioned equipment is specifically a voice broadcast device and the aforementioned user terminal is specifically a mobile phone, when the instant messaging software on the mobile phone receives information, the server can also send the received information to the voice broadcast device, so that the The voice broadcast device voice broadcasts the above information content, thereby omitting the operation of the user to open the mobile phone to view the information.
It is mentioned in step S104 of the above several embodiments that the server can establish a binding relationship between the user terminal and the device based on the association identifier and the device identifier. The above association identifier may not only include The association identification sent by the device may also include the association identification sent by the user terminal, which will be described in detail below in conjunction with two different implementation manners:
Embodiment 1: After the user terminal sends an association identification request to the server, the server assigns an association identification to the user terminal according to the user identification of the user terminal, and can store the mapping between the user identification and the association identification at the same time relationship. In this way, in step S104 of the foregoing embodiment, after receiving the association identification and device identification sent by the device, the server can traverse to find the currently stored association identification, and if the same association identification is found, it will find The user ID mapped to the associated ID and the device ID of the device can establish the binding relationship between the user terminal and the device.
Embodiment 2: After the server assigns the associated identifier to the user terminal, the server does not need to store the user identifier of the user terminal and the mapping relationship between the assigned associated identifier. However, the device described in step S103 of the above embodiment will After the step of sending the association identifier and the device identifier of the device to the server, it may further include the following steps:
The user terminal sends the association identification and the user identification of the user terminal to the server, so that,
Step S104 of the foregoing embodiment: the server establishing the binding relationship between the user terminal and the device according to the association identifier and the device identifier may specifically include:
The server establishes a binding relationship between the user terminal and the device according to the association identification and the device identification sent by the device, and the association identification and the user identification sent by the user terminal.
In the second embodiment above, the server stores the association identifier and the device identifier sent by the device based on the association identifier sent by the device. After receiving the association identifier sent by the user terminal, it can traverse to find the stored Association identification, if the same association identification is found, the binding between the user terminal and the device can be established based on the device identification corresponding to the found association identification and the user identification of the user terminal Definite relationship.
In the second embodiment, the device sends the associated identification (mainly refers to the storage device identification and the associated identification), which is more realistic. Because in actual applications, the user terminal may mistakenly send the associated identification and user identification to the device. At this time, there may be no need to establish a binding. When the server receives the association ID and the device ID sent by the device, there is to a large extent the need to establish a binding to avoid the server side storing too many resources (ie: the user ID and the association ID stored in the first embodiment ), resulting in redundant storage on the server side, thereby saving storage resources.
Preferably, as another embodiment of this specification, before the step of the device sending the association identifier and the device identifier of the device to the server in step S103 of the above embodiment, the embodiment may further include The steps are as follows: the device receives the user name and password of the predetermined wireless network sent by the user terminal; the device connects to the predetermined wireless network according to the user name and password, that is, the user terminal may be The device configures a wireless network.
Through the operation of configuring a wireless network for the device by the user terminal, the device can interact with the server through the connected predetermined wireless network. In this way, the device in step S103 of the above embodiment associates the associated identifier with the device The step of sending the device identifier of the device to the server may specifically be: the device sends the association identifier and the device identifier of the device to the server through the predetermined wireless network according to the predetermined wireless network connected end.
Preferably, as another embodiment of this specification, before the step of obtaining the association identifier by the user terminal in step S101 of the above embodiment, the embodiment may further include the following steps:
The user terminal obtains the barcode identification of the device; the barcode identification here may include a two-dimensional barcode identification, a one-dimensional barcode identification, etc., and the barcode identifications of multiple devices may be the same;
According to the obtained barcode identification, an association identification request is sent to the server.
In this way, the same two-dimensional bar code (or one-dimensional bar code) can be printed on multiple devices, and the user terminal can open the configuration page by scanning the two-dimensional bar code, thereby sending an associated identification request to the server. By printing the same two-dimensional bar code on multiple devices, the production process of the device is simplified, and the production cost of the device is saved.
Preferably, in order to explain in detail the binding method of the user terminal and the device provided in the embodiment of this specification, the following will be described with a specific preferred embodiment as an example. As shown in FIG. 2, this embodiment includes the following steps:
Step S201: The user terminal scans the two-dimensional barcode on the device.
In this embodiment, multiple different devices may include the same two-dimensional barcode, and the user can scan the two-dimensional barcode through the user terminal to automatically trigger the opening of the device configuration page.
Step S202: the user terminal opens the device configuration page;
On the configuration page, there may be buttons with specific functions, such as an associated identification request button, so that when the user clicks the associated identification button, step S203 can be executed.
Of course, when the configuration page is opened, no user operation is required, and the user terminal can also automatically execute step S203.
Step S203: The user terminal sends an association identification request to the server.
Step S204: The user terminal obtains the associated identification.
In this step, the user terminal can actively obtain the associated identification from the server; of course, the user terminal can also passively receive the associated identification returned by the server, that is, the server will send the associated identification to the user terminal after it allocates the associated identification. To the user terminal.
Step S205: The user terminal sends the association identifier to the device.
Before this step, the device may not have configured the network. Therefore, when the user terminal sends the associated identification to the device, the user terminal can also configure the network for the device through smartConfig technology. In a specific implementation:
The user terminal can send a user datagram protocol UDP broadcast packet containing the user name, password and associated identification of the predetermined wireless network;
The wireless communication module of the device can receive the UDP broadcast packet. The user terminal and the device can pre-appoint a protocol, and the protocol specifies the format of the UDP broadcast packet. In this way, the device can receive the UDP broadcast packet according to the above agreed protocol. Analyze the user name and password of the predetermined wireless network, associated identification, etc. in the UDP broadcast packet;
Then, the device configures the received user name and password of the predetermined wireless network to the predetermined wireless network to connect to the wireless network.
Step S206: The device sends the device identification and the associated identification to the server.
The device identification here can be the device ID of the device.
Specifically, the device may send the device identification and associated identification to the server through the predetermined wireless network connected in step S205. Of course, the server may store the device identification and associated identification sent by the device.
Step S207: the user terminal sends the user identification and the associated identification to the server;
In this step, the user terminal may specifically use a polling method to send a binding request to the server, and the binding request may include the user identification and the association identification.
Step S208: The server establishes a binding relationship.
When the server receives the user identification and associated identification sent by the user terminal, it can query whether any device has sent the associated identification and device identification. If so, that is, some device has sent the associated identification and device identification. Then the server can associate the current user ID with the device ID to realize the binding of the user terminal and the device.
Step S209: The server sends the binding result information to the device.
Step S210: The server sends the binding result information to the user terminal.
After the server establishes the binding relationship between the user terminal and the device in step S208, the server may also send binding result information to the device and the user terminal through step S209 and step S210, and the binding result information may include binding Success or binding failure, etc.
Preferably, as another embodiment of this specification, after the user terminal and the device are successfully bound, the server may also push the operation behavior to the user terminal and the device according to the operation behavior of the user terminal Results information.
As shown in FIG. 3, this specification also provides a method 300 for binding a user terminal and a device, which can be applied to a user terminal. As shown in FIG. 3, the method 300 includes the following steps:
Step S301: Obtain an association identifier, where the association identifier is allocated by the server to the user terminal;
Step S302: Send the association identifier to the device, and the association identifier is used by the device to send the association identifier and the device identifier of the device to the server, so that the server establishes the user terminal The binding relationship with the device.
In the above-mentioned binding method of the user terminal and the device provided by the embodiment of this specification, first, the user terminal obtains the association identification, and sends the association identification to the device, and the association identification is used by the device to associate the association identification The device identifier of the device and the device are sent to the server, so that the server establishes a binding relationship between the user terminal and the device, thereby realizing the binding of the user terminal and the device.
Preferably, as an embodiment, after step S302, the association identifier and the user identifier of the user terminal may also be sent to the server side, so that the server terminal is based on the association identifier sent by the device And the device identification, and the associated identification and user identification sent by the user terminal to establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, the association identifier is assigned by the server to the user terminal based on the user identifier of the user terminal, and the server stores the user identifier and the association The mapping relationship of the identification; the server can establish the binding of the user terminal and the device according to the mapping relationship between the user identification and the associated identification, and the associated identification and device identification sent by the device relationship.
Preferably, as an embodiment, after step S302, the user name and password of the predetermined wireless network may be sent to the device; the device is made to connect to the predetermined wireless network according to the user name and password.
Preferably, as an embodiment, before step S301, the barcode identification of the device may also be obtained; according to the obtained barcode identification, an association identification request is sent to the server. The barcode identifier includes a two-dimensional barcode identifier, and the two-dimensional barcode identifiers of multiple devices are the same.
Preferably, as an embodiment, after step S302, the binding result information sent by the server can also be received.
As shown in FIG. 4, this specification also provides a method 400 for binding a user terminal and a device, which can be applied to the device. As shown in FIG. 4, the method 400 includes the following steps:
Step S401: Receive an association identifier sent by a user terminal, where the association identifier is allocated by the server to the user terminal;
Step S402: Send the association identification and the equipment identification of the device to the server, so that the server establishes the connection between the user terminal and the equipment according to the association identification and the equipment identification. Binding relationship.
In the above-mentioned binding method of the user terminal and the device provided by the embodiment of this specification, firstly, the association identification sent by the user terminal is received, and then the association identification and the equipment identification of the device are sent to the server, so that The server establishes a binding relationship between the user terminal and the device according to the association identifier and the device identifier, thereby realizing the binding of the user terminal and the device.
Preferably, as an embodiment, the user terminal may also send the association identification and the user identification of the user terminal to the server, so that the server will perform the association according to the association sent by the device The identification and the device identification, as well as the associated identification and user identification sent by the user terminal, establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, the association identifier is assigned by the server to the user terminal based on the user identifier of the user terminal, and the server stores the user identifier and the association The mapping relationship of the identification; the server can establish the binding of the user terminal and the device according to the mapping relationship between the user identification and the associated identification, and the associated identification and device identification sent by the device relationship.
Preferably, as an embodiment, before step S401, the user name and password of a predetermined wireless network sent by the user terminal may also be received; and the predetermined wireless network is connected according to the user name and password.
Preferably, as an embodiment, a barcode identification is also printed on the device; the barcode identification includes a two-dimensional barcode identification, and the two-dimensional barcode identifications of multiple devices are the same.
Preferably, as an embodiment, after step S402, the binding result information sent by the server can also be received.
As shown in FIG. 5, this specification also provides a method 500 for binding a user terminal and a device, which can be applied to the server side. As shown in FIG. 5, the method 500 includes the following steps:
Step S501: Assign an association identifier to the user terminal, so that the user terminal sends the association identifier to the device;
Step S502: Receive the association identifier and the device identifier of the device sent by the device;
Step S503: Establish a binding relationship between the user terminal and the device according to the association identifier and the device identifier.
In the above-mentioned binding method of the user terminal and the device provided by the embodiment of this specification, first, the user terminal is assigned an association identifier, so that the user terminal sends the association identifier to the device; and then receives the device The associated identifier and the device identifier of the device are sent; in this way, based on the associated identifier and the device identifier, the binding relationship between the user terminal and the device can be established, thereby realizing the user terminal and Device binding.
Preferably, as an embodiment, after step S502, the association identifier and the user identifier of the user terminal sent by the user terminal may also be received. In this way, step S503 may specifically be: The association identification and device identification, as well as the association identification and user identification sent by the user terminal, establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, step S501 may assign an associated identifier to the user terminal based on the user identifier of the user terminal, and the server terminal stores a mapping between the user identifier and the associated identifier In this way, step S503 may specifically be: establishing a binding between the user terminal and the device according to the mapping relationship between the user ID and the association ID, and the association ID and device ID sent by the device Definite relationship.
Preferably, as an embodiment, binding result information can also be sent to the user terminal and the device.
Preferably, as an embodiment, it is also possible to push operation behavior result information to the user terminal and the device according to the operation behavior of the user terminal.
The above part of the manual describes in detail the embodiment of the binding method of the user terminal and the device, as shown in FIG. 6, this specification also provides a binding system 600 for the user terminal and the device, as shown in FIG. include:
The user terminal 601 may be used to obtain an association identification and send the association identification to the device, where the association identification is allocated by the server to the user terminal;
The device 602 may be configured to receive the association identifier, and send the association identifier and the device identifier of the device to the server;
The server 603 may be used to establish a binding relationship between the user terminal and the device according to the association identifier and the device identifier.
In the above-mentioned user terminal and device binding system provided by the embodiment of this specification, first, the user terminal obtains the association identification, and sends the association identification to the device, where the association identification is that the server is the user The terminal is assigned; then, the device receives the associated identification, and sends the associated identification and device identification to the server, so that the server can establish the user terminal and the user terminal based on the associated identification and device identification The binding relationship of the devices described realizes the binding of the user terminal and the device.
As shown in FIG. 7, this specification also provides a user terminal 700. As shown in FIG. 7, the user terminal 700 includes:
The obtaining unit 701 may be used to obtain an association identifier, where the association identifier is allocated by the server to the user terminal;
The sending unit 702 may be configured to send the association identifier to the device, and the association identifier is used by the device to send the association identifier and the device identifier of the device to the server, so that the server establishes the The binding relationship between the user terminal and the device.
Preferably, as an embodiment, the sending unit 702 may also send the association identification and the user identification of the user terminal to the server, so that the server sends the information according to the device The association identification and device identification, as well as the association identification and user identification sent by the user terminal, establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, the association identifier is assigned by the server to the user terminal based on the user identifier of the user terminal, and the server stores the user identifier and the association The mapping relationship of the identification; the server can establish the binding of the user terminal and the device according to the mapping relationship between the user identification and the associated identification, and the associated identification and device identification sent by the device relationship.
Preferably, as an embodiment, the sending unit 702 may also send the user name and password of the predetermined wireless network to the device; make the device connect to the predetermined wireless network according to the user name and password .
Preferably, as an embodiment, the obtaining unit 701 may also obtain the barcode identification of the device; according to the obtained barcode identification, send an association identification request to the server. The barcode identifier includes a two-dimensional barcode identifier, and the two-dimensional barcode identifiers of multiple devices are the same.
Preferably, as an embodiment, the acquiring unit 701 may also receive binding result information sent by the server.
As shown in Figure 8, this specification also provides a device 800. As shown in Figure 8, the device 800 includes:
The receiving unit 801 may be configured to receive an association identifier sent by a user terminal, where the association identifier is allocated by the server to the user terminal;
The sending unit 802 may be configured to send the association identification and the equipment identification of the device to the server, so that the server establishes the user terminal and the equipment identification according to the association identification and the equipment identification. The binding relationship of the device.
Preferably, as an embodiment, the user terminal may also send the association identification and the user identification of the user terminal to the server, so that the server will perform the association according to the association sent by the device The identification and the device identification, as well as the associated identification and user identification sent by the user terminal, establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, the association identifier is assigned by the server to the user terminal based on the user identifier of the user terminal, and the server stores the user identifier and the association The mapping relationship of the identification; the server can establish the binding of the user terminal and the device according to the mapping relationship between the user identification and the associated identification, and the associated identification and device identification sent by the device relationship.
Preferably, as an embodiment, the receiving unit 801 may also receive a user name and password of a predetermined wireless network sent by the user terminal; and connect to the predetermined wireless network according to the user name and password.
Preferably, as an embodiment, a barcode identification is also printed on the device; the barcode identification includes a two-dimensional barcode identification, and the two-dimensional barcode identifications of multiple devices are the same.
Preferably, as an embodiment, the receiving unit 801 may also receive binding result information sent by the server.
As shown in FIG. 9, this specification also provides a server terminal 900. As shown in FIG. 9, the server terminal 900 includes:
The allocating unit 901 allocates an association identifier to the user terminal, so that the user terminal sends the association identifier to the device;
The receiving unit 902 is configured to receive the association identifier and the device identifier of the device sent by the device;
The binding unit 903 establishes a binding relationship between the user terminal and the device according to the association identifier and the device identifier.
Preferably, as an embodiment, the receiving unit 902 may also receive the association identification and the user identification of the user terminal sent by the user terminal, so that the binding unit 903, according to the association identification and the user identification sent by the device The device identification, as well as the associated identification and user identification sent by the user terminal, establish a binding relationship between the user terminal and the device.
Preferably, as an embodiment, the assigning unit 901 assigns an associated identifier to the user terminal based on the user identifier of the user terminal, and the server terminal stores a mapping between the user identifier and the associated identifier Relationship; In this way, the binding unit 903 establishes a binding relationship between the user terminal and the device based on the mapping relationship between the user ID and the associated ID, and the associated ID and device ID sent by the device.
Preferably, as an embodiment, the allocation unit 901 may also send binding result information to the user terminal and the device.
Preferably, as an embodiment, the distribution unit 901 can also push operation behavior result information to the user terminal and the device according to the operation behavior of the user terminal.
The user terminal, device, and server according to the embodiment of the present invention will be described in detail below with reference to FIG. 10 (the above three are collectively referred to as electronic devices). Referring to FIG. 10, at the hardware level, the electronic device includes a processor, optionally, an internal bus, a network interface, and a memory. Wherein, as shown in FIG. 10, the memory may include memory, such as high-speed random-access memory (Random-Access Memory, RAM), and may also include non-volatile memory (non-volatile memory), such as at least 1 Disk memory, etc. Of course, the electronic device may also include hardware needed to implement other services.
The processor, network interface, and memory can be connected to each other through an internal bus, which can be an Industry Standard Architecture (ISA) bus or a Peripheral Component Interconnect (PCI) bus Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one double-headed arrow is used to indicate in FIG. 10, but it does not mean that there is only one busbar or one type of busbar.
Memory, used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include memory and non-volatile memory, and provide instructions and data to the processor.
The processor reads the corresponding computer program from the non-volatile memory to the memory and then runs it to form a device for forwarding chat information on a logical level. The processor executes the programs stored in the memory, and is specifically used to execute the operations of the method embodiments described earlier in this specification.
The methods executed by the systems and devices disclosed in the above-mentioned embodiments shown in FIGS. 6 to 9 may be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (DSP), special Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, distributed gate or transistor logic devices, discrete hardware Components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register and other mature storage media in the field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
The electronic device shown in FIG. 10 can also execute the methods shown in FIGS. 1 to 5, and implement the functions of the embodiments shown in FIGS. 1 to 5 of the binding method of the user terminal and the device, and the embodiments of the present invention will not be omitted here. Repeat.
Of course, in addition to the software implementation, the electronic equipment of the present invention does not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution body of the following processing flow is not limited to each logic unit , It can also be a hardware or logic device.
The embodiments of this specification also provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, each process of the above-mentioned method embodiments is realized and the same technical effect can be achieved. To avoid repetition, I won’t repeat them here. Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk, etc.
Those skilled in the art should understand that the embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention may be in the form of computer program products 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 codes. .
The present invention is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, dedicated computers, embedded processors, or other programmable data processing equipment to generate a machine that can be executed by the processors of the computer or other programmable data processing equipment Produce means for realizing the functions specified in one or more processes in the flowchart and/or one block or more in the block diagram.
These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including the instruction device , The instruction device realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to generate computer-implemented processing, so that the computer or other programmable equipment The instructions executed above provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
Memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash). RAM). Memory is an example of computer-readable media.
Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM) , Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only CD-ROM, digital multi-function Optical discs (DVD) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices, or any other non-transmission media, can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or they also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity or equipment that includes the element.
The above are only the embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the scope of the patent application of the present invention.
