Equipment communication method and device, equipment, storage medium and program product

Abstract

The invention relates to the technical field of communication, and provides an equipment communication method and device, equipment, a storage medium and a program product, and the method applied to a cloud server comprises the steps: carrying out the binding management of a user and to-be-bound intelligent equipment based on a binding request of the user and an information matching result of a preset database; the binding request comprises equipment information of the intelligent equipment to be bound and user information corresponding to a user; the binding request is used for indicating to bind a user with a to-be-bound intelligent device; the preset database comprises device information of at least one intelligent device and user information of a user to which each intelligent device belongs; the device information of each intelligent device in the preset database is obtained and reported based on a built-in soft probe of the corresponding intelligent device; and after the user is bound with the to-be-bound intelligent equipment, carrying out equipment communication with the to-be-bound intelligent equipment by using user equipment through gateway equipment connected with the to-be-bound intelligent equipment. According to the invention, the availability of equipment communication can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a device communication method, apparatus, device, storage medium and program product. Background Technology

[0002] With the popularization of the Internet of Things (IoT) concept, the number of smart terminals in home scenarios is exploding. Devices such as mobile phones, smart speakers, smart TVs, and home appliance controllers no longer work in isolation, but need to complete collaborative services within the same home network or across networks, such as projecting from a small screen to a large screen, remote control, status synchronization, and multi-device linkage. These services place higher demands on communication links that are "always accessible, low-latency, and secure and reliable." Therefore, how to achieve efficient, secure, and direct communication between devices across networks without increasing user costs and maintenance burdens has become a core technical problem that urgently needs to be solved in the smart home field.

[0003] In existing home scenarios, device communication solutions fall into two categories: One is local area network (LAN) communication, where mobile phones, speakers, TVs, etc., are all connected to the home gateway or router. The mobile phone uses Wi-Fi, and the devices communicate via an internet protocol (e.g., Internet Protocol version 4, IPv4) within the LAN to perform interactive tasks, such as projecting data from the mobile phone screen to the TV screen or using the mobile phone to control the TV. This solution has limitations: both communicating devices must be on the same Wi-Fi network; communication is not possible using cellular or different Wi-Fi networks. Other methods, such as Bluetooth, are also available, but these require close proximity. The other solution is an internet-based solution, where various smart home devices establish a long-term, two-way communication connection with a cloud server via the internet, maintaining a heartbeat. The mobile phone accesses the internet via cellular or Wi-Fi, sending network data to the cloud server, which then forwards requests to the connected devices to complete the communication. This solution requires a cloud relay server, which involves business and data storage issues, as well as routing selection. This directly leads to high software development costs, high service maintenance costs, decreased routing performance, and data security problems.

[0004] This results in insufficient availability when conducting device communication. Summary of the Invention

[0005] This application aims to at least address one of the technical problems existing in the related art. To this end, this application proposes a device communication method, apparatus, device, storage medium, and program product to solve the problem of insufficient availability in current device communication, thereby improving the availability of device communication.

[0006] The device communication method according to the first aspect of this application, applied to a cloud server, includes: Based on the matching results between the user's binding request and the information in the preset database, the binding management is performed between the user and the smart device to be bound; the binding request includes the device information of the smart device to be bound and the user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0007] According to one embodiment of this application, the binding management of the user and the smart device to be bound based on the matching result of the user's binding request and the information in the preset database includes: If the preset database contains device information that matches the user's binding request, then determine the user information of the user to which the matching device information belongs; If the user information of the user to which the user belongs matches the user information of the user, then the user's smart device information is verified, and after the user passes the smart device information verification, the user is bound to the smart device to be bound. If the user information of the user to which the user belongs does not match the user information of the user to which the user belongs, a confirmation message is sent to the user to which the user belongs. Based on the confirmation result of the confirmation message, the user is bound to the smart device to be bound or the user is not bound to the smart device to be bound. The confirmation message is used to instruct the user to request management authorization of the smart device.

[0008] According to one embodiment of this application, the device information of the smart device to be bound is obtained through the nameplate diagram of the smart device to be bound.

[0009] According to one embodiment of this application, the device information of each smart device in the preset database includes at least one of the following: device public Internet Protocol IP address, device internal IP address, device name, device type, device media access control MAC address, and device serial number (SN).

[0010] The device communication method according to the second aspect of this application, applied to a gateway device, includes: The system receives a control request from a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the gateway device's device identifier, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information for at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. If the control request passes the verification, the control request is forwarded to the target smart device.

[0011] A device communication apparatus according to a third aspect embodiment of this application includes: The binding module is used to manage the binding of a user to a smart device based on the matching results of the user's binding request and the information in a preset database; the binding request includes the device information of the smart device to be bound and the user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0012] A device communication apparatus according to a fourth aspect embodiment of this application includes: A receiving module is used to receive control requests sent by a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the device identifier of the gateway device, user information of the user to whom the target smart device belongs, and device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes device information of the target smart device and user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information of at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. The forwarding module is used to forward the control request to the target smart device if the control request passes the verification.

[0013] An electronic device according to a fifth aspect of this application includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement any of the device communication methods described above.

[0014] According to a sixth aspect of this application, the storage medium is a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the device communication method as described above.

[0015] A computer program product according to a seventh aspect of this application includes a computer program that, when executed by a processor, implements a device communication method as described above.

[0016] The above-described one or more technical solutions in the embodiments of this application have at least the following technical effects: By storing the device information of smart devices and the user information of their respective users, obtained and reported by the built-in soft probes of smart devices, in a preset database, a binding request from a user can be received. This database is then used to match the device information of the smart device to be bound and the user's information with relevant information. Based on the matching results, the binding management between the user and the smart device can be performed quickly and accurately. After binding, the user can use their device and the gateway device connected to the smart device to communicate with it. This eliminates the limitations of local area network (LAN) communication and eliminates the need for a cloud relay server during device communication. Therefore, it avoids the limitations of LAN communication and solves problems such as high software development costs, high service maintenance costs, degraded routing performance, and data security, effectively improving the availability of device communication.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is one of the flowcharts illustrating the device communication method provided in the embodiments of this application.

[0020] Figure 2 This is a schematic diagram of the tree structure in the device communication method provided in the embodiments of this application.

[0021] Figure 3 This is a schematic diagram of the binding process in the device communication method provided in the embodiments of this application.

[0022] Figure 4 This is the second flowchart illustrating the device communication method provided in the embodiments of this application.

[0023] Figure 5 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] It's important to note that communication between home devices or IoT devices in the current home environment requires addressing two issues. First, there's the network connectivity. Since home network devices lack public IP addresses, a cloud proxy server is used. This involves establishing a persistent connection between the home device and the cloud, then the user's phone sends messages to the cloud, which performs security verification before forwarding the messages to the home device, thus completing trusted communication between the phone and the home device. Second, there's the issue of security authentication. Home devices are private, and their data is confidential. Therefore, security authentication is essential when a phone sends messages from the internet to smart home devices.

[0026] Based on this, this application proposes a device communication method, apparatus, device, storage medium, and program product, aiming to solve the communication and interaction problems between multiple network devices in smart home scenarios, enhance user stickiness, and enrich the smart home industry.

[0027] It should be noted that all actions involving the acquisition of signals, information, or data in this application are carried out in compliance with the relevant data protection laws and regulations of the locality and with authorization from the owner of the relevant device.

[0028] Figure 1 This is a flowchart illustrating the device communication method provided in an embodiment of this application, as shown below. Figure 1 As shown, the communication method of this device includes: Step 110: Based on the matching results between the user's binding request and the information in the preset database, perform binding management between the user and the smart device to be bound; the binding request includes the device information of the smart device to be bound and the user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound.

[0029] The preset database contains device information for at least one smart device and user information for the user to which each smart device belongs. The device information for each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device.

[0030] After a user binds to a smart device, the user's device communicates with the smart device through the gateway device connected to the smart device.

[0031] It should be noted that the device communication method provided in this application embodiment can be executed by a cloud server. Users can access this cloud server through applications, mini-programs, and web pages.

[0032] Specifically, the smart devices in this application may include, but are not limited to, gateway devices, smart speakers, set-top boxes, routers, and cameras.

[0033] It should be noted that each smart device in this application has a built-in software probe. A software probe is a specialized tool used to monitor, collect, and analyze system or network status information. It is typically deployed on the target system as a lightweight agent, continuously collecting various operational data and sending it to a central monitoring system.

[0034] Therefore, the built-in soft probes in each smart device can report device information to the cloud server after the device is started or periodically collect and report device information during operation. The reported device information may include one or more of the following: device serial number (sn), device media access control (mac) address, device public Internet Protocol (IP) address (required for home gateway devices), device internal IP address, device name, and device type (e.g., brand and model).

[0035] For example, the device information reported in this application may include basic device information such as device SN, device MAC address, device public IP address, device private IP address, device name, and device type.

[0036] Therefore, the cloud server can obtain device information of each smart device based on the above network path design.

[0037] Furthermore, the cloud server in this application can also associate user information such as the home broadband account, subscription mobile number (i.e., master_phone), and province / city with the home smart device from home broadband installation and maintenance data or subscription data via the device's SN or MAC address. The province / city information can also be obtained by resolving the public IP address of the home gateway device.

[0038] Since the collected data only involves the user's home broadband account and mobile phone number, and does not involve the user's personal information and privacy data such as the MAC address, SN, name, and brand of other smart home devices, the data is safe and reliable.

[0039] Furthermore, cloud servers can store the aforementioned data and information.

[0040] Specifically, Redis or other storage engines capable of storing tree structures can be used as the default database for data storage.

[0041] Redis is an open-source, in-memory key-value store that can store keys and five associated data types: strings, lists, sets, sorted sets, and hash tables. Redis is characterized by storing all data in memory, providing very fast read and write performance, and also supports data persistence to disk for long-term storage. Redis can be used to cache data, reducing the burden on the database and improving system performance; it can also be used for message passing and shared lock control in distributed systems; it can be used to implement distributed computing; and it supports semi-structured data types and graph theory operations for more complex data computations and processing.

[0042] More specifically, a tree structure can be used to store data. Figure 2 This is a schematic diagram of the tree structure in the device communication method provided in the embodiments of this application, such as... Figure 2 As shown, the tree structure has the following layers: the first layer represents provinces (e.g., province 1 to province N); the second layer represents cities (e.g., city 1 to city N); the third layer represents households (this layer can also be a household identifier, more specifically a household broadband account, which can carry the user's mobile phone number, e.g., household 1 to household N); the fourth layer represents the device serial numbers of the smart devices under each household (e.g., device 1 to device N serial numbers); and the fifth layer represents the basic device information of the smart devices. This data is stored in the cloud, which is the device home topology, defined as HTree. Each smart device belongs to one and only one user (or described as belonging to only one household), and a household can have multiple smart devices. Each household node and all its leaf nodes form the device home topology for that household.

[0043] It should be noted that in the tree structure of this application, each leaf node has only one parent node; each parent node can have multiple leaf nodes. The device information of the smart home devices in the leaf nodes can be stored using JSON, including the device SN, device MAC address, device public IP address, device private IP address, device name, device type, and other information. JSON is an open standard file format and data exchange format.

[0044] By classifying and storing the massive amounts of home smart device data reported by the soft probe in a tree-like structure, a large HTree can be constructed by sequentially expanding the tree structure according to province, city, home broadband account, and home smart device. This facilitates data partitioning and edge computing, and helps improve the performance of subsequent matching and authorization.

[0045] Furthermore, its tree-structured, key-value data storage approach is suitable for both large-scale distributed storage and computing, as well as edge distributed computing, offering strong compatibility with future technology upgrades. It can also leverage in-memory middleware storage like Redis, significantly improving system performance.

[0046] In addition, the amount of data within each group is controllable, making it suitable for handling big data scenarios as well as for distributed deployment based on provinces or cities. It is also conducive to edge computing, with good scalability and adaptability.

[0047] Furthermore, the data for constructing the home device home topology comes from soft probe collection, installation and maintenance data, and order data of smart home devices. The data sources are abundant, giving it a certain competitive advantage and barriers to entry.

[0048] Based on this, when a user wants to communicate with a smart device for the first time, or wants to bind themselves to a smart device in advance, they need to first send a binding request (i.e., device home topology binding request) between the user (specifically, the user's account or mobile phone number) and the specified smart device (which can be defined as the smart device to be bound in this application) to the cloud server. This instructs the user to be bound to the corresponding smart device's home topology, so that the user can communicate with each smart device in the home topology through the user device.

[0049] Specifically, users can access the cloud server through their devices, such as smartphones (specifically through smartphone applications, mini-programs, or web pages). Then, following the cloud server's requirements or instructions, users can enter the device information of the smart device to be bound (such as the device serial number or device MAC address) and their own user information (such as their mobile phone number). After submitting the information, a binding request is initiated to the cloud server.

[0050] The device information of the smart device to be bound can be obtained by the user scanning the nameplate image of the smart device with the user's device camera and extracting the information from the nameplate image through Optical Character Recognition (OCR) technology. After extracting the device information from the nameplate image, the user can manually correct the device information if there is an error in the recognition. Alternatively, the user can directly input the information based on the content in the nameplate image or use other effective methods to input the information.

[0051] OCR technology can reduce user input, thereby improving the user experience.

[0052] Upon receiving a binding request, the cloud server compares the device information in the binding request with the device information in the preset database, and also compares the user information in the binding request with the user information in the preset database. Based on the results of these two comparisons, the matching information is determined.

[0053] Furthermore, based on the information matching results, binding management between the user and the smart device to be bound can be performed.

[0054] Specifically, binding management includes not binding users to smart devices that need to be bound.

[0055] Binding management specifically includes binding a user to the smart device to be bound and activating the user's administrator privileges. This means binding the user to the household where the smart device to be bound resides, designating the user as the administrator (i.e., the primary user), and activating administrator privileges so that the user can subsequently authorize other users to join the household to communicate (control) the smart devices within that household.

[0056] Binding management also includes binding users only to the smart devices to be bound, that is, binding users to other users' households.

[0057] After the user completes the binding with the smart device to be bound (i.e., the user returns home), the user can use the user device to communicate with any smart device in the household through the gateway device connected to the smart devices in that household.

[0058] Specifically, for any household, users in that household (including the main user and other users who have joined) can access the cloud server through their user terminals and query the device home topology under that household, and can choose to initiate control requests for any smart device under that device home topology.

[0059] When a user selects to initiate a control request for any smart device (where the control request contains at least the device information of the selected smart device), the control request can be sent via the Internet to the gateway device (i.e., the home gateway device) to which the selected smart device is connected.

[0060] After receiving a control request, the home gateway device can verify the information. If the control request passes the verification, it will be forwarded to the corresponding smart device. In this way, the user can communicate (control) the selected smart device with the user device.

[0061] According to the device communication method of this application embodiment, the device information of the smart device and the user information of the user to which each smart device belongs, obtained and reported by the built-in soft probe of the smart device, are stored in a preset database. Upon receiving a user's binding request, the device information of the smart device to be bound and the user's user information in the binding request are matched with relevant information in the preset database. Based on the matching results, the binding management of the user and the smart device to be bound can be performed quickly and accurately. After the binding of the user and the smart device is completed, the user can use the user device and the gateway device connected to the smart device to achieve communication with the smart device. Therefore, it is not limited to local area network communication, and no cloud relay server is required during the device communication process. This avoids the limitations of local area network communication and solves problems such as high software development costs, high service maintenance costs, degraded routing performance, and data security, effectively improving the availability of device communication.

[0062] In one embodiment, based on the matching results between the user's binding request and the information in a preset database, binding management is performed between the user and the smart device to be bound, including: If the preset database contains device information that matches the user's binding request, then determine the user information of the user to which the matching device information belongs; If the user's information matches the user's information, the user's smart device information will be verified, and after the user passes the smart device information verification, the user will be bound to the smart device to be bound. If the user information of the user to be bound does not match the user information of the user to be bound, a confirmation message will be sent to the user to be bound. Based on the confirmation result of the confirmation message, the user will be bound to the smart device to be bound or the user will not be bound to the smart device to be bound. The confirmation message is used to instruct the user to request management authorization of the smart device.

[0063] Specifically, Figure 3 This is a schematic diagram of the binding process in the device communication method provided in the embodiments of this application, such as... Figure 3 As shown in this application, after receiving a binding request, the cloud server can match the device information (specifically, the device SN or device MAC address) of the smart device to be bound in the binding request with the information in the preset database (specifically, querying whether there is a matching device SN or device MAC address). If the preset database does not contain device information that is the same as the device information of the smart device to be bound, the binding can be directly determined to have failed, and the corresponding prompt information can be output.

[0064] If it is determined that there is device information in the preset database that is the same as the device information of the smart device to be bound in the user's binding request, then the inverted index technology can be used to query the family to which the smart device to which the matching device information belongs (specifically, the family bandwidth account can be queried), and the main mobile phone number of the family can be queried as the user information of the user to which the matching device information belongs.

[0065] Furthermore, the user information in the binding request (specifically, the user's mobile phone number) can be compared with the queried user information (specifically, the main user's mobile phone number) to determine whether the two sets of user information match (whether the mobile phone number provided by the user is the main mobile phone number).

[0066] If the two user information matches, it can be determined that the user to be bound is the primary user. Therefore, the cloud server can output partially obfuscated device information to this user and instruct the user to supplement the obfuscated portion. After the user supplements the information, the cloud server compares the supplemented device information with the original device information. If they do not match, the user has failed the smart device information verification. In this case, the user is prompted to re-enter the information. If the re-entry matches, the user has passed the smart device information verification; otherwise, a binding error or failure message is displayed after a specified number of attempts. If they match, the supplementation is correct, and the user has passed the smart device information verification. At this point, the user can be bound to the smart device to be bound. Specifically, the user can be bound to the household where the smart device is located, and the user's administrator privileges can be activated.

[0067] The obfuscated device information can be the device information of the smart device to be bound under the device home topology of the household (e.g., device SN), or it can be other device information of the smart device to be bound (e.g., device name or device brand).

[0068] If it is determined that the two user information do not match, it means that another user wants to join the family. Therefore, the cloud server can send a confirmation message to the main user of the family (that is, the user to whom the smart device to be bound belongs) indicating that a user (specifically, the user's name, account information, or mobile phone number may be displayed) wants to join the family to obtain management authorization for the smart devices under the family. After receiving the confirmation message, the main user of the family can choose whether to add the user as a family member.

[0069] If the primary user confirms adding the user as a family member, the cloud server can bind the user to the smart device to be bound based on the confirmation result. In other words, the user (specifically the user's mobile phone number) is bound to the device home topology of the family where the smart device to be bound is located, so that the user can communicate with the smart devices under the family through the user's device.

[0070] If the primary user refuses to add the user as a family member, the cloud server can, based on the confirmation result, not bind the user to the smart device to be bound, and can output a message to the user indicating that the request was rejected or the binding failed.

[0071] This application stores device information of smart devices and user information of their respective users, obtained and reported by built-in soft probes, in a preset database. Upon receiving a user's binding request, the device information of the smart device to be bound and the user's information are matched against relevant information in the preset database. Based on the matching results, the binding management of the user and the smart device can be performed quickly and accurately. After binding, the user can use their device and the gateway device connected to the smart device to communicate with it. This eliminates the limitations of local area network (LAN) communication and the need for a cloud relay server during device communication. Therefore, it avoids the limitations of LAN communication and solves problems such as high software development costs, high service maintenance costs, degraded routing performance, and data security, effectively improving the availability of device communication.

[0072] Furthermore, Figure 4 This is a second schematic flowchart of the device communication method provided in the embodiments of this application, as shown below. Figure 4 As shown, the communication method of this device also includes: Step 410: Receive a control request sent by the user. The control request is used to request control of the target smart device, which is a smart device that has been bound to the user. The control request includes the device identifier of the gateway device, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on the matching result of the user's binding request and the information in the preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request is used to instruct the user to bind to the target smart device. The preset database contains the device information of at least one smart device and the user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device.

[0073] Step 420: If the control request passes the verification, the control request is forwarded to the target smart device.

[0074] It should be noted that the device communication method provided in this application embodiment can be executed by a gateway device.

[0075] Specifically, for any user bound to any household, when they need to control any smart device within that household, they can access the cloud server through their account to view the device home topology for that household. This application assumes that the mobile phone number used to subscribe to the household broadband (i.e., the primary mobile phone number) has this permission. Furthermore, after activating administrator privileges, the primary user corresponding to the primary mobile phone number can authorize other mobile phone numbers to bind device home topology relationships.

[0076] Therefore, any user in this household can initiate a control request to a smart device. Specifically, they can send a remote control message. This message uses the device number (SN) of the gateway device (specifically the home gateway device, i.e., the gateway device to which the specified smart device is connected) as the key, and a string composed of the home broadband account and timestamp as the content. After symmetric encryption, this string is used as a token and sent to the public IP address of the home gateway device along with the remote control message. The remote control message must contain the latitude and longitude address information of the current user device (such as a mobile phone) and the internal IP address of the smart device to be communicated.

[0077] Specifically, a remote control message consists of two parts: a header (token field) and a body (message body). The token is used for security authentication, while the body is used for auxiliary security authentication and actual message communication.

[0078] The token generation rule is as follows: use the home gateway device identifier (SN) as the key, perform symmetric encryption on the home broadband account and the current system timestamp in the device's home topology, and use the encrypted ciphertext as the token.

[0079] The rules for generating the body are: the internal network IP address of the smart home device that needs to communicate, the current location latitude and longitude of the user device, and the specific remote communication service message.

[0080] Subsequently, the home gateway device's built-in soft probe receives the control request, i.e., the remote control message, and decrypts the token using its own device number (SN) to verify whether the home broadband account belongs to the home network and whether the timestamp is within a valid time range (which is configurable). After successful verification, the latitude and longitude within the remote control message are parsed to calculate the distance between the user's device (e.g., the user's mobile phone) and the home gateway device. If the distance is within a trusted range (configurable, e.g., requiring them to be within the same city), authentication is successful.

[0081] Specifically, the home gateway device receives a remote control message from the user device via the internet. The message format is key-value, for example, {"header":"tokenXXXXX", "body":{"key1":"value1", "key2":"value2"...}}. The home gateway device verifies the token in the header, decrypts the token using its own device number (SN), and obtains the home broadband account and timestamp. The first step verifies the home broadband account's correctness; the second step verifies the timestamp's real-time accuracy (e.g., within N seconds, where N is configurable); the third step calculates the distance between the latitude and longitude in the message and the latitude and longitude of the home gateway device, ensuring the distance is within a reasonable range (N kilometers, where N is configurable or at least within the same city). The first step is mandatory; the user can configure whether the second and third steps are verified and their accuracy. This determines whether authentication is successful. If authentication fails, the remote control message will not be sent to the designated smart device's internal IP address, preventing communication with the smart device, and an error or exception message can be returned to the user.

[0082] After successful authentication, the home gateway device can send remote control messages to the internal IP address of the designated smart device, thereby completing the trusted communication process.

[0083] This application's trusted communication design utilizes multiple verification methods, including the device ID of the home smart device, the home broadband account, timestamps, and latitude and longitude, and these verifications are configurable. This ensures security while also enhancing flexibility. Furthermore, it employs a public network point-to-point communication method using a home gateway, simplifying the communication architecture and saving on setup and operation costs.

[0084] Furthermore, this application achieves point-to-point internet communication based on user equipment and home gateway, abandoning cloud relay, which is an inevitable trend after the explosive growth of smart home services. Relay servers become extremely expensive when the number of devices is large, and are one of the bottlenecks restricting the development of smart home and smart home services.

[0085] The device communication apparatus provided in this application is described below. The device communication apparatus described below and the device communication method described above can be referred to in correspondence.

[0086] Furthermore, this application also provides a device communication apparatus.

[0087] The device communication apparatus includes: The binding module is used to manage the binding of a user to a smart device based on the matching results of the user's binding request and the information in a preset database; the binding request includes the device information of the smart device to be bound and the user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0088] The device communication apparatus of this application stores device information of smart devices and user information of users associated with each smart device, obtained and reported by the built-in soft probes of the smart devices, in a preset database. Upon receiving a user's binding request, it matches the device information of the smart device to be bound and the user's user information in the binding request with relevant information in the preset database. Based on the matching results, it can quickly and accurately manage the binding between the user and the smart device to be bound. After binding, the user can use their device and the gateway device connected to the smart device to communicate with it. Therefore, it avoids the limitations of local area network communication and eliminates the need for a cloud relay server during device communication. This solves problems such as high software development costs, high service maintenance costs, degraded routing performance, and data security, effectively improving the availability of device communication.

[0089] In one embodiment, the binding module is specifically used for: If the preset database contains device information that matches the user's binding request, then determine the user information of the user to which the matching device information belongs; If the user information of the user to which the user belongs matches the user information of the user, then the user's smart device information is verified, and after the user passes the smart device information verification, the user is bound to the smart device to be bound. If the user information of the user to which the user belongs does not match the user information of the user to which the user belongs, a confirmation message is sent to the user to which the user belongs. Based on the confirmation result of the confirmation message, the user is bound to the smart device to be bound or the user is not bound to the smart device to be bound. The confirmation message is used to instruct the user to request management authorization of the smart device.

[0090] In one embodiment, the device communication apparatus further includes: A receiving module is used to receive control requests sent by a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the device identifier of the gateway device, user information of the user to whom the target smart device belongs, and device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes device information of the target smart device and user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information of at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. The forwarding module is used to forward the control request to the target smart device if the control request passes the verification.

[0091] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include a processor 510, a communications interface 520, a memory 530, and a communication bus 540, wherein the processor 510, communications interface 520, and memory 530 communicate with each other via the communication bus 540. The processor 510 can call logical instructions in the memory 530 to execute the following method: based on the matching result of a user's binding request and information in a preset database, perform binding management between the user and the smart device to be bound; the binding request includes device information of the smart device to be bound and user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0092] Alternatively, you can use the following method: The system receives a control request from a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the gateway device's device identifier, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information for at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. If the control request passes the verification, the control request is forwarded to the target smart device.

[0093] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0094] In another aspect, embodiments of this application also provide a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program is implemented to perform the methods provided in the above embodiments, such as: binding management of the user and a smart device to be bound based on a user's binding request and the information matching result of a preset database; the binding request includes device information of the smart device to be bound and user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0095] Or, including: The system receives a control request from a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the gateway device's device identifier, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information for at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. If the control request passes the verification, the control request is forwarded to the target smart device.

[0096] In another aspect, embodiments of this application also provide a computer program product, on which a computer program is stored. When executed by a processor, the computer program is implemented to perform the methods provided in the above embodiments, such as: binding management of the user and the smart device to be bound based on the matching result of the user's binding request and the information in the preset database; the binding request includes device information of the smart device to be bound and user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

[0097] Or, including: The system receives a control request from a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the gateway device's device identifier, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information for at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. If the control request passes the verification, the control request is forwarded to the target smart device.

[0098] The device embodiments described above are merely illustrative. The units described 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0099] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of software products. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0100] Finally, it should be noted that the above embodiments are only used to illustrate this application and are not intended to limit this application. Although this application has been described in detail with reference to the embodiments, those skilled in the art should understand that various combinations, modifications, or equivalent substitutions of the technical solutions of this application do not depart from the spirit and scope of the technical solutions of this application.

Claims

1. A device communication method, characterized in that, Applications in cloud servers, including: Based on the matching results between the user's binding request and the information in the preset database, the binding management is performed between the user and the smart device to be bound; the binding request includes the device information of the smart device to be bound and the user information corresponding to the user; the binding request is used to instruct the user to be bound to the smart device to be bound. The preset database contains device information of at least one smart device and user information of the user to which each smart device belongs; the device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device. After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

2. The device communication method according to claim 1, characterized in that, The process of binding and managing the user with the smart device to be bound, based on the matching results between the user's binding request and the information in the preset database, includes: If the preset database contains device information that matches the user's binding request, then determine the user information of the user to which the matching device information belongs; If the user information of the user to which the user belongs matches the user information of the user, then the user's smart device information is verified, and after the user passes the smart device information verification, the user is bound to the smart device to be bound. If the user information of the user to which the user belongs does not match the user information of the user to which the user belongs, a confirmation message is sent to the user to which the user belongs. Based on the confirmation result of the confirmation message, the user is bound to the smart device to be bound or the user is not bound to the smart device to be bound. The confirmation message is used to instruct the user to request management authorization of the smart device.

3. The device communication method according to claim 1, characterized in that, The device information of the smart device to be bound is obtained from the nameplate image of the smart device to be bound.

4. The device communication method according to claim 1, characterized in that, The device information of each smart device in the preset database includes at least one of the following: device public Internet Protocol IP address, device internal IP address, device name, device type, device media access control MAC address, and device serial number (SN).

5. A device communication method, characterized in that, Applied to gateway devices, including: The system receives a control request from a user. The control request requests control of a target smart device, which is a smart device already bound to the user. The control request includes the gateway device's device identifier, the user information of the user to whom the target smart device belongs, and the device information of the target smart device. The binding between the target smart device and the user is based on a matching result between the user's binding request and information in a preset database. The binding request includes the device information of the target smart device and the user information of the user. The binding request instructs the user to bind to the target smart device. The preset database contains device information for at least one smart device and user information of the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on a soft probe built into the corresponding smart device. If the control request passes the verification, the control request is forwarded to the target smart device.

6. A device communication apparatus, characterized in that, include: The binding module is used to bind and manage the user and the smart device to be bound based on the user's binding request and the information matching result of the preset database; The binding request includes the device information of the smart device to be bound and the user information corresponding to the user; The binding request is used to instruct the user to be bound to the smart device to be bound; The preset database contains device information for at least one smart device and user information for the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device; After the user binds to the smart device to be bound, the user device communicates with the smart device to be bound through the gateway device connected to the smart device to be bound.

7. A device communication apparatus, characterized in that, include: The receiving module is used to receive control requests sent by users; The control request is used to request control over a target smart device, which is a smart device that has been bound to the user; the control request includes the device identifier of the gateway device, the user information of the user to whom the target smart device belongs, and the device information of the target smart device; The binding between the target smart device and the user is based on the binding request of the user and the information matching results of a preset database; the binding request includes the device information of the target smart device and the user information of the user. The binding request is used to instruct the user to be bound to the target smart device; The preset database contains device information for at least one smart device and user information for the user to whom each smart device belongs. The device information of each smart device in the preset database is obtained and reported based on the soft probe built into the corresponding smart device; The forwarding module is used to forward the control request to the target smart device if the control request passes the verification.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the device communication method as described in any one of claims 1 to 5.

9. A storage medium, said storage medium being a non-transitory computer-readable storage medium, wherein a computer program is stored thereon, characterized in that, When executed by a processor, the computer program implements the device communication method as described in any one of claims 1 to 5.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the device communication method according to any one of claims 1 to 5.

Images