A device binding system, method and electronic device

Abstract

The application provides a device binding system, comprising: a first device, which is communicatively connected with a second device, obtains a physical address of the second device based on the communication connection, obtains first information from a cloud server based on the physical address, obtains a device serial number from a program component based on the first information, and sends a binding request carrying the physical address and the device serial number to the cloud server; the second device, which has the program component, and the program component is configured to send relevant data of the second device to the cloud server, and the relevant data comprises the first information of the program component, the physical address and the device serial number; the second device sends the device serial number to the first device based on the first information sent by the first device; and the cloud server, which verifies a matching relationship between the physical address and the device serial number sent by the first device based on the binding request, and establishes a binding relationship between an application account corresponding to the first device and the second device if the verification is successful. The application also simultaneously provides a device binding method and an electronic device.

Description

Technical Field

[0001] This invention relates to device bonding technology, specifically to a device bonding system, method, and electronic device. Background Technology

[0002] As smart gateways become increasingly feature-rich, operators are continuously launching various value-added services based on them, such as game acceleration, green internet access, and education acceleration. To use these services, users first need to download the operator's application on their devices and then establish a binding relationship between their user account and the smart gateway within that application. However, existing binding methods require users to manually enter or scan a QR code to obtain the smart gateway's physical address (MAC, Media Access Control Address) and serial number (SN) on their devices. The MAC address and SN are then uploaded to a cloud server to complete the binding. The QR code binding method requires a one-to-one correspondence between the SN and the device, placing high demands on device production management and increasing the complexity and cost of device manufacturing. The manual input method, due to the typically long MAC address and SN, is not only cumbersome for users but also prone to errors, resulting in low binding success rates and a poor user experience. Summary of the Invention

[0003] To address the existing technical problems, the technical solution of this application is implemented as follows:

[0004] According to one aspect of this application, a device binding system is provided, characterized in that the system comprises:

[0005] A first device is communicatively connected to a second device, and obtains the physical address of the second device based on the communication connection; and is used to obtain first information of a corresponding program component from a cloud server based on the physical address, the first information being used to communicate with the program component; and is used to obtain a corresponding device serial number from the program component based on the first information; and is used to send a binding request to the cloud server, the binding request carrying the physical address and the device serial number;

[0006] The second device has the program component, which is used to send relevant data of the second device to the cloud server, the relevant data including at least the first information of the program component, the physical address and the device serial number; and is used to send the device serial number to the first device based on the first information sent by the first device.

[0007] The cloud server is used to verify the matching relationship between the physical address and the device serial number sent by the first device based on the binding request. If the verification is successful, a binding relationship is established between the application account corresponding to the first device and the second device.

[0008] In the above scheme, the first device is also used to send a data acquisition request to the cloud server, and the data acquisition request carries the physical address;

[0009] The cloud server is also used to respond to the data acquisition request, query the first information of the program component corresponding to the physical address, and send the first information to the first device.

[0010] In the above scheme, the first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address;

[0011] The first device is also configured to send the authentication information to the program component based on the IP address and the port number;

[0012] The program component in the second device is also used to verify the authentication information. If the verification is successful, the device serial number is sent to the first device through the port number.

[0013] In the above scheme, the program component in the second device is further configured to listen to the data transmission port of the second device in a random manner, generate authentication information for the data transmission port if the data transmission port is currently in an idle state, and send the port number of the data transmission port, the authentication information and the Internet Protocol IP address of the second device as the first information to the cloud server.

[0014] In the above scheme, the cloud server is also used to store the relevant data of the second device; and is also used to update the historical relevant data to the relevant data when the relevant data is inconsistent with the historical relevant data stored in the cloud server for the second device.

[0015] In the above scheme, the cloud server is also used to send a notification message to the first device indicating whether the application account corresponding to the first device and the second device have been successfully bound.

[0016] In the above scheme, the program component of the second device is also used to acquire the relevant data of the second device; and is also used to save the relevant data.

[0017] According to a second aspect of this application, a device bonding method is provided, applied to a first device, characterized in that the method includes:

[0018] Send a data retrieval request to the cloud server, wherein the data retrieval request carries the physical address of the second device;

[0019] The cloud server receives first information corresponding to the program component of the second device based on the physical address, and the first information is used to obtain the corresponding device serial number from the program component.

[0020] A binding request is sent to the cloud server, the binding request carrying the physical address and the device serial number;

[0021] If the matching relationship between the physical address and the device serial number is verified by the cloud server, a notification message returned by the cloud server indicating that the application account corresponding to the first device has been successfully bound to the second device is received.

[0022] In the above scheme, the first information includes at least the port number of the data transmission port, authentication information, and the Internet Protocol (IP) address; the method further includes:

[0023] The authentication information is sent to the program component based on the IP address and the port number.

[0024] If the authentication information passes the verification by the program component, the device serial number sent by the program component is received.

[0025] According to a third aspect of this application, a device bonding method is provided, applied to a second device, characterized in that the method includes:

[0026] The program component on the second device sends relevant data of the second device to the cloud server. The relevant data includes at least the first information of the program component, the physical address of the second device, and the device serial number of the second device.

[0027] The device receives the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the second device.

[0028] The first information is compared with the authentication information stored in the program component;

[0029] If the comparison result indicates that the first information is the same as the authentication information, the device serial number is sent to the first device so that the first device can establish a binding relationship between the application account corresponding to the first device and the second device based on the physical address and the device serial number.

[0030] In the above scheme, before sending the relevant data of the second device to the cloud server through the program component on the second device, the method further includes:

[0031] The program component randomly listens to the data transmission port of the second device;

[0032] If the data transmission port being monitored is currently in an idle state, generate authentication information for the data transmission port;

[0033] The port number of the data transmission port, the authentication information, and the IP address of the second device are sent to the cloud server as the first information.

[0034] According to a fourth aspect of this application, a device binding method is provided, applied to a cloud server, characterized in that the method includes:

[0035] Receive a data acquisition request sent by a first device, wherein the data acquisition request carries the physical address of a second device;

[0036] Based on the physical address, send the first information of the program component of the corresponding second device to the first device;

[0037] The system receives a binding request sent by the first device, the binding request carrying the physical address and device serial number; the device serial number is obtained by the first device from the program component based on the first information.

[0038] If the matching relationship between the physical address and the device serial number is confirmed to be correct, a binding relationship is established between the application account corresponding to the first device and the second device.

[0039] The method in the above scheme further includes:

[0040] Send a notification message to the first device indicating whether the application account corresponding to the first device and the second device have been successfully bound.

[0041] According to a fifth aspect of this application, an electronic device is provided, characterized in that the electronic device comprises:

[0042] The sending unit is configured to send a data acquisition request to the cloud server, the data acquisition request carrying the physical address of the second device; and to send a binding request to the cloud server, the binding request carrying the physical address and the device serial number.

[0043] The receiving unit is configured to receive first information corresponding to the program component of the second device returned by the cloud server based on the physical address, wherein the first information is used to obtain the corresponding device serial number from the program component; and to receive a notification message returned by the cloud server indicating that the application account corresponding to the electronic device has been successfully bound to the second device if the matching relationship between the physical address and the device serial number is verified by the cloud server.

[0044] According to a sixth aspect of this application, an electronic device is provided, characterized in that the electronic device comprises:

[0045] A sending unit is configured to send relevant data of the electronic device to a cloud server through a program component of the electronic device, wherein the relevant data includes at least first information of the program component, the physical address of the electronic device, and the device serial number of the electronic device;

[0046] A receiving unit is configured to receive the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the electronic device;

[0047] An authentication unit is used to compare the first information with the authentication information stored in the program component;

[0048] The sending unit is further configured to send the device serial number to the first device if the comparison result indicates that the first information is the same as the authentication information, so that the first device establishes a binding relationship between the application account corresponding to the first device and the electronic device based on the physical address and the device serial number.

[0049] In the above solution, the electronic device further includes:

[0050] A monitoring unit is used to monitor the data transmission port of the electronic device in a random manner;

[0051] The generation unit is used to generate authentication information for the data transmission port if the monitored data transmission port is currently in an idle state.

[0052] The sending unit is further configured to send the port number of the data transmission port, the authentication information, and the IP address of the second device as the first information to the cloud server.

[0053] According to a seventh aspect of this application, an electronic device is provided, characterized in that the electronic device comprises:

[0054] A receiving unit is configured to receive a data acquisition request sent by a first device, the data acquisition request carrying the physical address of a second device; and to receive a binding request sent by the first device, the binding request carrying the physical address and a device serial number; the device serial number is obtained by the first device from the target program component based on the first information;

[0055] A sending unit is configured to send first information of the program component of the second device corresponding to the physical address to the first device.

[0056] The establishment unit is used to establish a binding relationship between the application account corresponding to the first device and the second device when the matching relationship between the physical address and the device serial number is correct.

[0057] The device binding system, method, and electronic device provided in this invention involve a first device obtaining first information about the program components of a second device from a cloud server using the MAC address of the second device. Based on this first information, the first device obtains the serial number (SN) of the second device from the program components. Then, the first device reports the MAC address and SN to the cloud server to complete the device binding process. Since the MAC address and SN are automatically obtained, the entire process is automatic, efficient, and secure, greatly improving the user experience and reducing the probability of device binding failure. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of the device binding system in this application;

[0059] Figure 2 This is a flowchart illustrating the device binding system in this application;

[0060] Figure 3 This is a flowchart illustrating the device binding method in this application. Figure 1 ;

[0061] Figure 4 This is a flowchart illustrating the device binding method in this application. Figure 2 ;

[0062] Figure 5 This is a flowchart illustrating the device binding method in this application. Figure 3 ;

[0063] Figure 6 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 1 ;

[0064] Figure 7 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 2 ;

[0065] Figure 8This is a schematic diagram of the structural composition of the electronic device in this application. Figure 3 ;

[0066] Figure 9 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 4 . Detailed Implementation

[0067] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0068] Figure 1 This is a schematic diagram of the device binding system in this application; as shown. Figure 1 As shown, the system includes a first device 10, a second device 20, and a cloud server 30, wherein both the first device 10 and the second device 20 are connected to the cloud server 30 via a network. Here, the first device 10 can be a terminal device such as a mobile phone, tablet, or watch; the second device 20 can be a network device (such as a smart gateway, router, or switch), and the second device 20 may have a communication component 201 and an additional program component 202; wherein the communication component 201 is used to provide internet access functionality for the first device 10, for example, the communication component 201 can be a WIFI component, and the first device 10 can access the internet via a wireless network by connecting to the communication component 201, and can also communicate with the second device 20 via the wireless network to obtain the physical address (MAC address) of the second device 20. The program component 202 may be a plug-in installed on the second device 20, used to start the data transmission service after the second device 20 is powered on, so that the first device 10 can access the program component 202 through the data output port in the wireless network, and provide the first device 10 with the device serial number (SN code) of the second device 20.

[0069] In this application, the first device 10 may have an application installed, which provides the first device 10 with an operation interface and business functions for binding the second device 20. The cloud server 30 can provide the application in the first device 10 with services such as account login, device binding, and business function operation. The program component 202 of the second device 20 can obtain and record the MAC address, SN code, IP address, and other information of the second device 20 after it is successfully powered on. In this way, each time the second device 20 is powered on, the program component 202 only needs to listen on a random port, without repeatedly obtaining the IP address, MAC address, SN code, etc. of the second device 20. At the same time, the program component 202 can also start the data transmission service of the second device 20.

[0070] Here, to avoid the problem of data transmission service startup failure due to fixed port occupancy, program component 202 can randomly listen to the data transmission port of the second device 20. If the listened data transmission port is currently occupied, it continues to listen to the next data transmission port randomly until the listened data transmission port is currently idle. If the listened data transmission port is currently idle, the service of the data transmission port is enabled, and authentication information for the data transmission port is generated; then, the port number of the data transmission port, the authentication information, and the IP address, MAC address, and SN code of the second device 20 are sent as relevant data of the second device 20 to the cloud server 30.

[0071] Here, when generating authentication information for the data transmission port, program component 202 can generate authentication information for the data transmission port based on the listening timestamp or system timestamp of the data transmission port; it can also generate authentication information for the data transmission port through a random string; or it can generate a universally unique identifier (UUID) by calculating the current timestamp, a random number, and the machine IP address, and use the UUID as the authentication information for the data transmission port.

[0072] After receiving data related to the second device 20 sent by the program component 202, the cloud server 30 stores the relevant data of the second device 20 in its database. This allows it to query the database for the first information of the program component 202 corresponding to the physical address carried in the data retrieval request when it receives a data retrieval request from the first device 10. Here, the first information includes the port number of the data transmission port of the program component 202, authentication information, and IP address.

[0073] In this application, after the first device 10 obtains the physical address (MAC address) of the second device 20 through the communication component 201 of the second device 20, it can also obtain the first information of the corresponding program component from the cloud server 30 based on the physical address.

[0074] In one implementation, after the first device 10 successfully logs into the application using the corresponding application account, it can send a data retrieval request to the cloud server 30 through the application's interface. The data retrieval request carries the physical address. Upon receiving the data retrieval request, the cloud server 30 responds by querying the first information of the program component corresponding to the physical address in its database and sending the first information to the first device 10.

[0075] Here, the first information is used for the first device 10 to communicate with the target program component, and based on this communication, the device serial number (SN code) of the corresponding device can be obtained from the target program component.

[0076] In this application, the first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address. When the first device 10 obtains the device serial number of the corresponding device from the target program component based on the first information, it can specifically communicate with the target program component based on the IP address and send the authentication information to the target program component through the port number. If the authentication information is verified by the target program component, the target program component can send the corresponding device's serial number (SN) to the first device 10.

[0077] Here, if the target program component is program component 202 of the second device 20, when program component 202 receives the authentication information sent by the first device 10 based on the first information, program component 202 can also compare the authentication information with the authentication information stored locally. If the comparison is consistent, it is determined that the authentication information has passed the verification, and then the SN code of the second device 20 is sent to the first device 10 through the corresponding data transmission port number.

[0078] Here, the data transmission port includes, but is not limited to, the User Datagram Protocol (UDP) port and the Transmission Control Protocol (TCP) port.

[0079] In this application, after obtaining the serial number (SN) of the second device 20, the first device 10 can also call the binding port of the cloud server 30 through the application installed on the first device 10 to send a binding request to the cloud server 30 through the binding port. The binding request carries the physical address (MAC address) and device serial number (SN) of the second device 20. The cloud server 30 responds to the binding request by verifying the matching relationship between the physical address (MAC address) and the device serial number (SN) carried in the binding request. If the verification is successful, a binding relationship is established between the application account corresponding to the first device 10 and the second device 20. After establishing the binding relationship, a notification message indicating successful binding of the application account corresponding to the first device 10 and the second device 20 is sent to the first device 10. If the verification fails, the binding relationship between the application account corresponding to the first device 10 and the second device 20 is refused, and a notification message indicating binding failure of the application account corresponding to the first device 10 and the second device 20 is sent to the first device 10. Thus, the first device 10 can know the binding result between the application account corresponding to the first device 10 and the second device 20 based on the notification message.

[0080] Here, the application account corresponding to the first device 10 includes, but is not limited to, mobile phone number, QQ number, WeChat account, email address, etc., and the application corresponding to the application account can be installed on different first devices.

[0081] In this application, since the program component 202 of the second device 20 listens to the data transmission port of the second device 20 again every time the second device 20 is powered on, and since it listens to a random port, the data transmission port listened to each time can be different. Therefore, the data transmission port and authentication information sent by the program component 202 to the cloud server 30 each time can also be different. After receiving the relevant data of the second device 20 sent by the program component 202, the cloud server 30 can also compare the relevant data with the historical relevant data stored in the cloud server 30 for the second device 20. If the comparison result indicates that the relevant data is inconsistent with the historical relevant data, the historical relevant data is updated to the relevant data to improve the binding success rate of the device this time.

[0082] This application involves setting up an additional program component on the second device. This component enables the data transmission port (UDP or TCP port) of the local area network (LAN) where the second device resides. The first device obtains the MAC address of the second device through the LAN and retrieves its serial number (SN) from the program component based on this data transmission port. This achieves automatic acquisition of the MAC address and SN. The entire process requires only a single click of a binding button in the application on the first device, eliminating the need for manual input of the device's MAC address and SN. This minimizes user intervention and avoids errors caused by manual input, which could lead to failed or incorrect binding of the application account on the first device to the second device, thus improving the success rate of device binding and the user experience. Furthermore, this solution uses a random method to listen to the data transmission port, preventing port service startup failures due to port occupancy. The randomly listened-to data transmission port and corresponding authentication information are reported to a cloud server, ensuring the availability of the device binding process.

[0083] Figure 2 This is a flowchart illustrating the device binding system in this application, such as... Figure 2 As shown, the system flow includes:

[0084] Step 2001: Power on the smart gateway to be bound and turn on the WiFi module on the smart gateway.

[0085] Here, it is necessary to ensure that the WiFi module is working properly and that the phone can access the internet normally while the WiFi module is working properly.

[0086] Step 2002: The plug-in on the smart gateway obtains and records information such as the smart gateway's MAC address, SN code, and local area network IP address;

[0087] Step 2003: The plug-in on the smart gateway simultaneously starts the UDP service on the smart gateway;

[0088] Here, to avoid the UDP service failing to start due to the fixed data transmission port being occupied, the smart gateway plugin will listen to the data transmission port of the smart gateway in a random manner; if the randomly listened port is occupied, it will switch to another random port until the UDP service starts successfully; if the data transmission port listened to by the plugin is currently in an idle state, it will generate the authentication information corresponding to the data transmission port (which can be the listening timestamp, system timestamp, random string, 32-bit UUID, etc.).

[0089] Step 2004: The smart gateway's plugin reports the relevant data of the smart gateway to the cloud server;

[0090] Here, the relevant data of the smart gateway includes, but is not limited to, the smart gateway's MAC address, SN code, gateway LAN IP address, data transmission port, and authentication information.

[0091] Step 2005: After receiving the relevant data from the smart gateway, the cloud server stores or updates the relevant data.

[0092] Step 2006: The user logs in using their user account on the mobile application (APP / mini-program) and then clicks the "Bind" button;

[0093] Step 2007: The mobile application (APP / mini-program) calls the mobile interface to obtain the MAC address of the currently connected WiFi.

[0094] Here, the phone interface can be provided by the phone's operating system.

[0095] Step 2008: The mobile application (APP / mini-program) uses the obtained MAC address to send a data retrieval request to the cloud server in order to query the UDP information of the plugin on the currently connected smart gateway in the cloud service.

[0096] Step 2009: The cloud server returns the gateway LAN IP, UDP port, and UDP authentication information corresponding to the MAC address to the mobile application (APP / mini-program).

[0097] Step 2100: The mobile application (APP / mini-program) sends a UDP request to the corresponding plugin within the local area network, carrying UDP authentication information.

[0098] Step 2110: The plugin compares the authentication information stored locally with the authentication information received by the UDP interface. If the comparison results are consistent, the SN code of the smart gateway is sent to the APP / mini-program on the mobile phone.

[0099] Step 2120: The mobile application (APP / mini-program) requests the device binding interface of the cloud server, carrying the MAC address and SN code of the smart gateway.

[0100] Step 2130: The cloud server verifies the correctness of the MAC address and SN code of the smart gateway sent by the mobile terminal through the device binding interface;

[0101] Step 2140: If the MAC address and SN code of the smart gateway match normally, the cloud server establishes a binding relationship between the login account of the mobile application APP / mini-program and the smart gateway.

[0102] Here, the login account for a mobile application (APP / mini-program) can typically be a user's mobile phone number, WeChat ID, QQ number, email address, etc., and the mobile application (APP / mini-program) can be installed on different devices, such as another mobile phone, tablet, watch, etc.

[0103] Step 2150: The cloud server returns the binding result to the mobile application (APP / mini-program).

[0104] Here, after the mobile app / mini-program receives the notification message indicating successful binding, it can control the smart gateway's business plugin by issuing commands through the cloud server. For example, if the plugin provides game acceleration services, the app / mini-program can control the plugin by issuing commands such as start acceleration and stop acceleration through the cloud server.

[0105] As can be seen, the entire binding process does not require users to manually enter the MAC address and SN code of the smart gateway, nor does it require the device manufacturer to provide additional information such as QR codes. This reduces the user's operations, improves the device binding success rate, and greatly enhances the user experience.

[0106] Figure 3 This is a flowchart illustrating the device binding method in this application. Figure 1 ,like Figure 3 As shown, the method includes:

[0107] Step 301: The first device sends a data acquisition request to the cloud server, and the data acquisition request carries the physical address of the second device;

[0108] Step 302: Receive first information corresponding to the program component of the second device returned by the cloud server based on the physical address. The first information is used to obtain the corresponding device serial number from the program component.

[0109] Step 303: Send a binding request to the cloud server, the binding request carrying the physical address and the device serial number;

[0110] Step 304: If the matching relationship between the physical address and the device serial number is verified by the cloud server, receive a notification message returned by the cloud server indicating that the first device and the second device have been successfully bound.

[0111] In this application, the method can be applied to a first device, such as a mobile phone, tablet, watch, or other terminal. The first device can connect to a second device via a wireless network to obtain the physical address (MAC address) of the second device. Here, the second device can refer to a network device, such as a router, smart gateway, switch, etc. The second device has a Wi-Fi component, and the first device can access the internet via the wireless network by connecting to the second device's Wi-Fi component. The second device also has an additional program component, used to start the second device's data transmission service after power-on, allowing the first device to access the program component within the wireless network and providing the first device with the second device's device serial number (SN code).

[0112] Here, the first device can also have an application installed. This application provides an interface and business functions for binding the login account corresponding to the application on the first device to the second device. The first device can send data retrieval requests to the cloud server through the application's interface. These requests carry the MAC address of the second device. Upon receiving the data retrieval request, the cloud server can query the database for the first information of the program component corresponding to the physical address carried in the request, and then send this first information to the first device. Based on this first information, the first device can obtain the SN code of the second device from the program component of the second device.

[0113] Here, the cloud server stores relevant data about the second device (including but not limited to MAC address, SN code, and first information of the program components). The first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address. When the first device can obtain the SN code of the second device from the program components of the second device based on the first information, it can send the authentication information to the program components of the second device based on the IP address and port number. If the authentication information passes the verification of the program components, the first device receives the device serial number (SN code) of the second device sent by the program components.

[0114] Here, after the second device is powered on, the program component can randomly listen to the data transmission port of the second device. When the listened data transmission port is in an idle state, it generates authentication information for that data transmission port, stores the authentication information locally, and reports the port number of the data transmission port, the authentication information, and the IP address of the program component as the first piece of information to the cloud server. When the program component receives the authentication information sent by the first device, it can compare the authentication information with the locally stored authentication information. If the comparison result is consistent, the authentication information is deemed to have been successfully verified, and the SN code of the second device is sent to the first device; if the comparison result is inconsistent, the authentication information is deemed to have failed, and the SN code of the second device is not sent to the first device.

[0115] In this application, after obtaining the MAC address and SN code of the second device, the first device can also send a binding request to the cloud server through its application. The binding request carries the MAC address and SN code of both devices. The cloud server verifies the matching relationship between the MAC address and SN code in the binding request. If the matching relationship matches the MAC address and SN code stored in the database, the cloud server determines that the matching relationship is correct, indicating successful verification. Then, it establishes a binding relationship between the application account corresponding to the first device and the second device, and sends a notification message to the first device indicating successful binding. Conversely, if the matching relationship does not match, the cloud server rejects the establishment of the binding relationship between the application account corresponding to the first device and the second device, and sends a notification message to the first device indicating failed binding.

[0116] Here, establishing the binding relationship between the application account on the first device and the second device can specifically mean establishing the binding relationship between the login account on the first device and the application on the second device. The login account for this application can typically be a user's mobile phone number, WeChat ID, QQ number, or email address.

[0117] This application establishes a network connection between a first device and a second device. The MAC address of the second device is obtained through this connection. Based on this MAC address, the application retrieves the first information of the corresponding device's program component from a cloud server. Communication with the second device's program component is then established using the data transmission port specified in this first information to send authentication information. If the authentication information passes the program component's verification, the SN code of the second device is obtained from the program component. The first device's application then reports the MAC address and SN code to the cloud server, thereby establishing a binding relationship between the first and second devices. The entire process requires only a single click of the binding button in the application on the first device, eliminating the need to manually input the MAC address and SN code of the second device (smart gateway). This minimizes user operations, avoids binding failures due to user errors, and improves the success rate of device binding and the user experience.

[0118] It should be noted that the device binding method provided in the above embodiments and the device binding system embodiments provided above belong to the same concept. For details of its specific implementation process, please refer to the system embodiments, which will not be repeated here.

[0119] Figure 4 This is a flowchart illustrating the device binding method in this application. Figure 2 As shown in Figure 4, the method includes:

[0120] Step 401: Send relevant data of the second device to the cloud server through the program component on the second device. The relevant data includes at least the first information of the program component, the physical address of the second device, and the device serial number of the second device.

[0121] Step 402: Receive the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the second device;

[0122] Step 403: Compare the first information with the authentication information stored in the program component;

[0123] Step 404: If the comparison result indicates that the first information is the same as the authentication information, send the device serial number to the first device so that the first device can establish a binding relationship between the application account corresponding to the first device and the second device based on the physical address and the device serial number.

[0124] In this application, the method can be applied to a second device, which can be a network device, such as a router, smart gateway, switch, etc. The second device has a Wi-Fi component and a program component. The Wi-Fi component enables a wireless connection with the first device, providing wireless internet access for the first device. The first device can obtain the MAC address of the second device from its platform via this wireless connection. The program component enables the second device's data transmission service to be started after power-on, allowing the first device to communicate with the program component through this data transmission service and providing the first device with the second device's serial number (SN code).

[0125] Here, the first device can be a mobile phone, computer, or other terminal device.

[0126] In this application, after the second device is successfully powered on, the program component can also listen to the data transmission port of the second device randomly. If the listened data transmission port is currently idle, authentication information for that data transmission port is generated. The port number of the data transmission port, the authentication information, and the IP address of the program component are then sent to the cloud server as the program component's first information. Thus, compared to using a fixed data transmission port, randomly listening to the data transmission port avoids the problem of port occupancy failure.

[0127] Here, the data transmission port includes, but is not limited to, UDP ports and TCP ports.

[0128] In this application, when the program component of the second device receives authentication information sent by the first device through the data transmission port, the program component can compare the authentication information with locally stored authentication information. If the comparison result indicates that the authentication information is consistent with the locally stored authentication information, the program component sends the SN code of the second device to the first device. This allows the first device to establish a binding relationship between the application account corresponding to the first device and the second device through the cloud server based on the MAC address and SN code of the second device.

[0129] Here, the program component of the second device stores the MAC address, IP address, SN code, and authentication information corresponding to the currently enabled data transmission port of the second device.

[0130] In this application, after successfully establishing the binding relationship between the application account corresponding to the first device and the second device through the cloud server, the second device can receive control instructions sent by the first device through the business component, and can control the business component accordingly based on the control instructions to realize the corresponding value-added services provided by the business component.

[0131] For example, if the service component provides a game acceleration service, the first device can send control commands such as start acceleration or stop acceleration to the service component of the second device through the cloud server, so that the service component can achieve target control based on the control commands.

[0132] Here, the program component in the second device can also provide business functions. That is, after the binding relationship between the first device and the second device is successfully established through the cloud server, the second device can receive control commands sent by the first device through the program component. Based on the control commands, the program component can be controlled accordingly to realize the corresponding value-added services provided by the program component.

[0133] In this application, the application (APP / mini-program) on the first device connects with the second device to obtain the second device's MAC address. It can then retrieve the second device's serial number (SN) from the second device's program components via the second device's UDP or TCP interface. The entire process requires only a single click of the binding button on the first device's application, eliminating the need for manual input of the device's MAC address and SN. This minimizes user intervention, avoids binding failures due to user input errors, and improves the success rate of device binding and the user experience. Furthermore, by having the program components randomly listen to the device's data transmission port, the problem of data transmission service startup failures due to port occupation by other applications can be avoided, thus ensuring the availability of the device binding process.

[0134] It should be noted that the device binding method provided in the above embodiments and the device binding system embodiments provided above belong to the same concept. For details of its specific implementation process, please refer to the system embodiments, which will not be repeated here.

[0135] Figure 5 This is a flowchart illustrating the device binding method in this application. Figure 3 ,like Figure 5 As shown, the method includes:

[0136] Step 501: Receive a data acquisition request sent by the first device, wherein the data acquisition request carries the physical address of the second device;

[0137] Step 502: Send the first information of the program component of the corresponding second device to the first device based on the physical address;

[0138] Step 503: Receive a binding request sent by the first device, the binding request carrying the physical address and device serial number; the device serial number is obtained by the first device from the program component based on the first information;

[0139] Step 504: If the matching relationship between the physical address and the device serial number is correct, establish the binding relationship between the application account corresponding to the first device and the second device.

[0140] In this application, the method can be applied to a cloud server, which can provide services such as account login, device binding, and business function operation to the application in the first device. The cloud server can receive relevant data about the second device sent by the program component in the second device. This relevant data includes, but is not limited to, the second device's MAC address, SN code, IP address, data transmission port number, authentication information, etc., and stores the relevant data of the second device in a database, establishing a correspondence between the MAC address, SN code, IP address, data transmission port number, and authentication information in the database. When the cloud server receives a data acquisition request from the first device, it can search the database for the data transmission port number, IP address, and authentication information corresponding to the MAC address carried in the data acquisition request, and send this data transmission port number, IP address, and authentication information as the first information of the program component of the second device to the first device. After receiving the first information sent by the cloud server, the first device can send the authentication information to the program component through the data transmission port number based on the IP address in the first information. If the authentication information passes the verification of the program component, the first device receives the SN code of the second device sent by the program component.

[0141] Here, the first device can be a terminal device such as a mobile phone, laptop, tablet, or watch. The second device can be a network device, including but not limited to smart gateways, switches, and routers.

[0142] In this application, after obtaining the MAC address and SN code of the second device, the first device can send a binding request to the cloud server, which carries the MAC address and SN code of the second device. Upon receiving the binding request from the first device, the cloud server can also search for the SN code corresponding to the MAC address in the database based on the MAC address and SN code carried in the binding request; or search for the MAC address corresponding to the SN code in the database. If the found MAC address and SN match the MAC address and SN code sent by the first device, the matching relationship is determined to be correct. The cloud server then establishes a binding relationship between the application account corresponding to the first device and the second device, and sends a notification message to the first device indicating successful binding of the application account and the second device. If the found MAC address and SN match is not found to be correct, the matching relationship is determined to be incorrect. The cloud server then fails to establish a binding relationship between the application account corresponding to the first device and the second device, and sends a notification message indicating binding failure of the application account and the second device.

[0143] In this application, the cloud server can also compare the relevant data of the second device with the historical relevant data of the second device stored in the database after receiving the relevant data of the second device sent by the program component of the second device. If the comparison result indicates that the currently received relevant data is inconsistent with the historical relevant data, the historical relevant data is updated to the relevant data.

[0144] Here, because the data transmission port number and corresponding authentication information reported by the program components of the second device to the cloud server are different each time, when the cloud server updates the historical data related to the second device in the database, it can specifically update the data transmission port number and corresponding authentication information of the second device. This ensures the feasibility of establishing a binding relationship between the application account corresponding to the first device and the second device.

[0145] In this application, when binding network devices (such as smart gateways), users only need to click the binding button in the mobile application to automatically report the MAC address and SN code of the smart gateway to the cloud server. Users do not need to manually enter or scan the MAC address and SN code of the smart gateway, which minimizes user operations, avoids binding failure due to user operation errors, and improves the success rate of device binding and user experience.

[0146] It should be noted that the device binding method provided in the above embodiments and the device binding system embodiments provided above belong to the same concept. The specific implementation process is detailed in the system embodiments and will not be repeated here. Furthermore, since the cloud server does not know whether the MAC address sent by the first device is automatically obtained, manually entered, or obtained through scanning, the corresponding device's SN code cannot be sent to the first device solely based on the MAC address. This is to avoid incorrect MAC address reports from the first device leading to device binding failure or errors. Instead, the first information of the corresponding device's program component is sent to the first device based on the MAC address. After the first device obtains the device's SN code from the target program component based on this first information, the matching relationship between the MAC address and SN code sent by the first device determines whether to establish a binding relationship between the application account corresponding to the first device and the second device. This can greatly reduce the probability of device binding failure or errors.

[0147] Figure 6 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 1 ,like Figure 6 As shown, the electronic device includes:

[0148] The sending unit 601 is configured to send a data acquisition request to the cloud server, the data acquisition request carrying the physical address of the second device; and to send a binding request to the cloud server, the binding request carrying the physical address and the device serial number.

[0149] The receiving unit 602 is configured to receive first information corresponding to the program component of the second device returned by the cloud server based on the physical address, wherein the first information is used to obtain the corresponding device serial number from the program component; and to receive a notification message returned by the cloud server indicating that the application account corresponding to the electronic device has been successfully bound to the second device if the matching relationship between the physical address and the device serial number is verified by the cloud server.

[0150] In this application, the electronic device can be the first device in the above-described scheme, such as a mobile phone, tablet computer, laptop computer, watch, or other terminal device. The electronic device can bind to the second device in a cloud server through its installed application. The second device can be a network device, such as a smart gateway, switch, or router. The first device can establish a communication connection with the second device through a local area network, and based on this communication connection, it can obtain the MAC address and serial number (SN) of the second device.

[0151] In a preferred embodiment, the electronic device further includes: an acquisition unit 603, configured to acquire the MAC address of the second device via the communication connection, and also configured to acquire first information about the program components of the second device from a cloud server based on the MAC address.

[0152] Here, the first information is used for communication between the first device and the program component. The first information includes at least the port number of the data transmission port, authentication information, and the Internet Protocol (IP) address.

[0153] In a preferred embodiment, the sending unit 601 is further configured to send the authentication information to the program component via the port number based on the IP address; if the authentication information passes the verification of the program component, the receiving unit 602 is triggered, and the receiving unit 602 receives the device serial number sent by the program component.

[0154] It should be noted that the above embodiments of the electronic device, when binding with the second device, are only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the electronic device provided in the above embodiments and the device binding system and method embodiments provided above belong to the same concept, and the specific implementation process can be found in the system and method embodiments, which will not be repeated here.

[0155] Figure 7 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 2 ,like Figure 7 As shown, the electronic device includes:

[0156] The sending unit 701 is used to send relevant data of the electronic device to the cloud server through the program component of the electronic device. The relevant data includes at least the first information of the program component, the physical address of the electronic device, and the device serial number of the electronic device.

[0157] The receiving unit 702 is configured to receive the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the electronic device;

[0158] The authentication unit 703 is used to compare the first information with the authentication information stored in the program component;

[0159] The sending unit 701 is further configured to send the device serial number to the first device if the comparison result indicates that the first information is the same as the authentication information, so that the first device establishes a binding relationship between the application account corresponding to the first device and the electronic device based on the physical address and the device serial number.

[0160] In this application, the electronic device can be the second device in the above-described scheme, including but not limited to network devices such as routers, smart gateways, and switches. The electronic device has a communication component that can provide wireless internet access to the first device. For example, the communication component can be a Wi-Fi component. The first device can establish a communication connection with the second device through the wireless internet access provided by the communication component, and obtain the MAC address of the second device based on this communication connection.

[0161] In a preferred embodiment, the electronic device further includes:

[0162] The monitoring unit 704 is used to monitor the data transmission port of the electronic device in a random manner through the program component;

[0163] The generation unit 705 is used to generate authentication information for the data transmission port if the monitored data transmission port is currently in an idle state.

[0164] The sending unit 701 is further configured to send the port number of the data transmission port, the authentication information, and the IP address of the second device as the first information to the cloud server.

[0165] It should be noted that the above embodiments of the electronic device, in implementing the binding relationship with the first device, are only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the electronic device provided in the above embodiments and the device binding system and method embodiments provided above belong to the same concept, and the specific implementation process can be found in the system and method embodiments, which will not be repeated here.

[0166] Figure 8 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 3 ,like Figure 8 As shown, the electronic device includes:

[0167] The receiving unit 801 is configured to receive a data acquisition request sent by a first device, the data acquisition request carrying the physical address of a second device; and to receive a binding request sent by the first device, the binding request carrying the physical address and a device serial number; the device serial number is obtained by the first device from the target program component based on the first information;

[0168] Sending unit 802 is used to send first information of the program component of the second device corresponding to the physical address to the first device;

[0169] Establishment unit 803 is used to establish a binding relationship between the application account corresponding to the first device and the second device when the matching relationship between the physical address and the device serial number is correct.

[0170] In this application, the electronic device can be the cloud server in the above scheme, which can provide services such as account login, device binding, and business function operation to the application in the first device.

[0171] In a preferred embodiment, the receiving unit 801 is further configured to receive relevant data of the second device sent by the program component in the second device. This relevant data includes, but is not limited to, the second device's MAC address, SN code, IP address, data transmission port number, and corresponding authentication information. Here, the IP address can be either the IP address of the second device or the IP address of the program component.

[0172] In a preferred embodiment, the electronic device further includes:

[0173] The storage unit 804 is used to store the relevant data of the second device sent by the program component.

[0174] In the preferred embodiment, the establishing unit 803 is also used to establish the correspondence between the MAC address, SN code, IP address, port number of the data transmission port, and the corresponding authentication information in the database.

[0175] In a preferred embodiment, the electronic device further includes:

[0176] The query unit 805 is used to query the database for the first information of the program component corresponding to the physical address in the data acquisition request based on the data acquisition request sent by the first device.

[0177] Here, the first piece of information can be the IP address of the program component, the port number of the data transmission port, and the corresponding authentication information.

[0178] In a preferred embodiment, the sending unit 802 is further configured to send a notification message to the first device indicating whether the application account corresponding to the first device has been successfully or unsuccessfully bound to the second device.

[0179] It should be noted that the above embodiments of the electronic device, in implementing the binding relationship with the first device, are only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the electronic device provided in the above embodiments and the device binding system and method embodiments provided above belong to the same concept, and the specific implementation process can be found in the system and method embodiments, which will not be repeated here.

[0180] This application also provides an electronic device, which includes: a processor and a memory for storing a computer program capable of running on the processor.

[0181] When the processor runs the computer program, it executes any one of the method steps in any of the above-described device binding methods.

[0182] Figure 9 This is a schematic diagram of the structural composition of the electronic device in this application. Figure 4 Electronic devices 900 can be terminals such as mobile phones, computers, digital broadcasting terminals, information transceivers, medical devices, fitness equipment, and personal digital assistants, as well as network devices such as routers, switches, and smart gateways. They can also be servers, including but not limited to physical servers and cloud servers. Figure 9 The illustrated electronic device 900 includes at least one processor 901, a memory 702, at least one network interface 904, and a user interface 903. The various components in the electronic device 900 are coupled together via a bus system 905. It is understood that the bus system 905 is used to implement communication between these components. In addition to a data bus, the bus system 905 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 9 The general labeled all buses as Bus System 905.

[0183] The user interface 903 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0184] It is understood that memory 902 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 902 described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0185] In this embodiment, the memory 902 is used to store various types of data to support the operation of the electronic device 900. Examples of such data include: any computer program used to operate on the electronic device 900, such as the operating system 9021 and application program 9022; contact data; phonebook data; messages; pictures; audio, etc. The operating system 9021 includes various system programs, such as the framework layer, core library layer, driver layer, etc., used to implement various basic services and handle hardware-based tasks. The application program 9022 may include various applications, such as a media player, browser, etc., used to implement various application services. Programs implementing the methods of this embodiment may be included in the application program 9022.

[0186] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 901. The processor 901 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 901 or by instructions in the form of software. The processor 901 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 901 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the memory 902. The processor 901 reads the information in the memory 902 and combines its hardware to complete the steps of the aforementioned method.

[0187] In an exemplary embodiment, the electronic device 900 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0188] In an exemplary embodiment, this application also provides a computer-readable storage medium, such as a memory 902 including a computer program, which can be executed by a processor 901 of an electronic device 900 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; it may also be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0189] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs any of the method steps of any of the above-described device binding methods.

[0190] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0191] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0192] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0193] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0194] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0195] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A device binding system, characterized in that, The system includes: A first device is communicatively connected to a second device, and obtains the physical address of the second device based on the communication connection; and is used to obtain first information of a corresponding program component from a cloud server based on the physical address, wherein the first information includes at least a data transmission port number, authentication information, and an Internet Protocol (IP) address, and is used to communicate with the program component; and is used to send the authentication information to the program component via the port number based on the IP address, and if the authentication information passes the verification of the program component, receive the device serial number sent by the program component; and is used to send a binding request to the cloud server, the binding request carrying the physical address and the device serial number; The second device includes the program component, which is used to send relevant data of the second device to the cloud server. The relevant data includes at least the first information of the program component, the physical address, and the device serial number. It is also used to verify the authentication information received from the first device based on the first information. If the verification is successful, it sends the device serial number to the first device via the port number. The authentication information is generated by the program component by randomly monitoring the data transmission port of the second device to obtain an idle data transmission port. The cloud server is used to verify the matching relationship between the physical address and the device serial number sent by the first device based on the binding request. If the verification is successful, a binding relationship is established between the application account corresponding to the first device and the second device.

2. The system according to claim 1, characterized in that: The first device is further configured to send a data acquisition request to the cloud server, wherein the data acquisition request carries the physical address; The cloud server is also used to respond to the data acquisition request, query the first information of the program component corresponding to the physical address, and send the first information to the first device.

3. The system according to claim 1, characterized in that: The program component in the second device is further configured to listen to the data transmission port of the second device in a random manner, generate authentication information for the data transmission port if the data transmission port is currently in an idle state, and send the port number of the data transmission port, the authentication information, and the Internet Protocol IP address of the second device as the first information to the cloud server.

4. The system according to claim 1, characterized in that, The cloud server is also used to store the relevant data of the second device; and to update the historical relevant data to the relevant data if the relevant data is inconsistent with the historical relevant data stored in the cloud server for the second device.

5. The system according to claim 1, characterized in that, The cloud server is also used to send a notification message to the first device indicating whether the application account corresponding to the first device and the second device have been successfully bound.

6. The system according to claim 1, characterized in that, The program component of the second device is further configured to acquire the relevant data of the second device; and also to save the relevant data.

7. A device bonding method, applied to a first device, characterized in that, The method includes: The first device sends a data acquisition request to the cloud server, and the data acquisition request carries the physical address of the second device; The cloud server receives first information corresponding to the program component of the second device based on the physical address, wherein the first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address. The first device sends the authentication information to the program component via the port number based on the IP address; if the authentication information passes the verification by the program component, it receives the device serial number sent by the program component; wherein, the device serial number is sent by the program component to the first device via the port number when it receives the authentication information sent by the first device based on the first information, verifies the authentication information, and if the verification is successful; the authentication information is generated by the program component by randomly monitoring the data transmission port of the second device to obtain an idle data transmission port; A binding request is sent to the cloud server, the binding request carrying the physical address and the device serial number; If the matching relationship between the physical address and the device serial number is verified by the cloud server, a notification message returned by the cloud server indicating that the application account corresponding to the first device has been successfully bound to the second device is received.

8. A device bonding method, applied to a second device, characterized in that, The method includes: The program component on the second device sends relevant data of the second device to the cloud server. The relevant data includes at least the first information of the program component, the physical address of the second device, and the device serial number of the second device. The first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address. The authentication information is generated by the program component by randomly listening to the data transmission port of the second device and obtaining the data transmission port in an idle state. The device receives the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the second device. Upon receiving the authentication information sent by the first device through the port number based on the IP address, the authentication information is verified. If the verification is successful, the device serial number is sent to the first device through the port number, so that the first device can establish a binding relationship between the application account corresponding to the first device and the second device based on the physical address and the device serial number.

9. The method according to claim 8, characterized in that, Before sending the relevant data of the second device to the cloud server via the program components on the second device, the method further includes: The program component randomly listens to the data transmission port of the second device; If the data transmission port being monitored is currently in an idle state, generate authentication information for the data transmission port; The port number of the data transmission port, the authentication information, and the IP address of the second device are sent to the cloud server as the first information.

10. A device binding method applied to a cloud server, characterized in that, The method includes: Receive a data acquisition request sent by a first device, wherein the data acquisition request carries the physical address of a second device; Based on the physical address, the program component of the corresponding second device sends first information to the first device; wherein, the first information includes at least the port number of the data transmission port, authentication information and Internet Protocol (IP) address; the authentication information is generated by the program component by randomly listening to the data transmission port of the second device to obtain the data transmission port in an idle state; The system receives a binding request sent by the first device, which carries the physical address and device serial number. The device serial number is obtained by the first device sending authentication information to the program component based on the IP address and through the port number. After receiving the authentication information, the second device verifies the authentication information. If the verification is successful, the second device sends the authentication information back to the first device through the port number. If the matching relationship between the physical address and the device serial number is confirmed to be correct, a binding relationship is established between the application account corresponding to the first device and the second device.

11. The method according to claim 10, characterized in that, The method further includes: Send a notification message to the first device indicating whether the application account corresponding to the first device and the second device have been successfully bound.

12. An electronic device, characterized in that, The electronic device includes: The sending unit is configured to send a data acquisition request to the cloud server, the data acquisition request carrying the physical address of the second device; and to send a binding request to the cloud server, the binding request carrying the physical address and the device serial number. A receiving unit is configured to receive first information corresponding to a program component of the second device returned by the cloud server based on the physical address, wherein the first information includes at least a data transmission port number, authentication information, and an Internet Protocol (IP) address; send the authentication information to the program component via the port number based on the IP address; if the authentication information passes the verification of the program component, receive the device serial number sent by the program component; wherein the device serial number is sent by the program component to the first device via the port number when the program component verifies the authentication information sent by the first device based on the first information, and if the verification is successful; the authentication information is generated by the program component by randomly monitoring the data transmission port of the second device to obtain an idle data transmission port; and if the matching relationship between the physical address and the device serial number passes the verification of the cloud server, receive a notification message returned by the cloud server indicating that the application account corresponding to the electronic device is successfully bound to the second device.

13. An electronic device, characterized in that, The electronic device includes: A sending unit is configured to send relevant data of the electronic device to a cloud server through a program component of the electronic device. The relevant data includes at least first information of the program component, the physical address of the electronic device, and the device serial number of the electronic device. The first information includes at least the port number of the data transmission port, authentication information, and Internet Protocol (IP) address. The authentication information is generated by the program component by randomly monitoring the data transmission port of a second device to obtain the idle data transmission port. A receiving unit is configured to receive the first information sent by the first device, wherein the first information is obtained by the first device from the cloud server based on the physical address of the electronic device; An authentication unit is used to verify the authentication information received from the first device based on the IP address and through the port number; The sending unit is further configured to, if the verification is successful, send the device serial number to the first device through the port number, so that the first device can establish a binding relationship between the application account corresponding to the first device and the electronic device based on the physical address and the device serial number.

14. The electronic device according to claim 13, characterized in that, The electronic device also includes: A monitoring unit is used to monitor the data transmission port of the electronic device in a random manner; The generation unit is used to generate authentication information for the data transmission port if the monitored data transmission port is currently in an idle state. The sending unit is further configured to send the port number of the data transmission port, the authentication information, and the IP address of the second device as the first information to the cloud server.

15. An electronic device, characterized in that, The electronic device includes: A receiving unit is configured to receive a data acquisition request sent by a first device, the data acquisition request carrying the physical address of a second device; and to receive a binding request sent by the first device, the binding request carrying the physical address and a device serial number; the device serial number is obtained by the first device sending authentication information to the program component based on the IP address and port number, and the second device verifying the authentication information after receiving it, and if the verification is successful, sending it back to the first device through the port number; The sending unit is configured to send first information of the corresponding program component of the second device to the first device based on the physical address; wherein, the first information includes at least the port number of the data transmission port, authentication information and Internet Protocol (IP) address; the authentication information is generated by the program component by randomly listening to the data transmission port of the second device to obtain the data transmission port in an idle state; The establishment unit is used to establish a binding relationship between the application account corresponding to the first device and the second device when the matching relationship between the physical address and the device serial number is correct.

Images