Equipment binding method and device, storage medium, electronic device and computer program product
The device binding method verifies the binding status and requires a matching target string to secure IoT device binding, addressing security issues in multiple user access.
Patent Information
- Application Number
- CN202411213660.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-12-17
AI Technical Summary
Existing IoT device binding methods lack security, allowing multiple users to bind to a device without verification, leading to potential data loss and leakage.
A device binding method that verifies the binding status of a target device, sends a target string to a second account if already bound, and only establishes a binding relationship if the first account provides the same string, ensuring secure binding.
Ensures secure binding by verifying the same target string, preventing unauthorized access and maintaining data security.
Smart Images
Figure CN119155077A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of smart home technology, and more specifically, to a device binding method and apparatus, a storage medium, an electronic device, and a computer program product. Background Art
[0002] As the economy, society and living standards continue to improve, IoT technology is increasingly being applied to various devices. With the promotion of smart homes, more and more IoT devices such as smart air conditioners, washing machines, and automatic sweepers have entered ordinary households. IoT devices, especially smart homes, mostly need to be bound to users so that users can control smart homes.
[0003] In the related art, after a user actively discovers a device through a mobile phone, he or she immediately initiates a binding request to bind to the device. However, after one user binds to the device, other users can still bind to the device directly, and malicious binding cannot be determined. This can easily lead to the loss and leakage of data between the device and normal users, and lacks a certain degree of security.
[0004] With regard to the problem of poor security of devices when binding multiple people in related technologies, no effective solution has been proposed so far.
[0005] Therefore, it is necessary to improve the related technology to overcome the above-mentioned defects in the related technology. Summary of the invention
[0006] The embodiments of the present application provide a device binding method and apparatus, a storage medium, an electronic device, and a computer program product to at least solve the problem of poor security of a device when binding multiple people.
[0007] According to one aspect of an embodiment of the present application, a device binding method is provided, comprising: upon obtaining a binding request sent by a first account, verifying a binding status of a target device, wherein the binding request carries a device identification of the target device; upon indicating that the binding status is used to indicate that the target device has established a binding relationship with a second account, sending a target string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a string to be verified; upon obtaining the target string sent by the first account, establishing a binding relationship between the first account and the target device.
[0008] In an exemplary embodiment, the method further includes: sending a first request instruction to a second account when the binding status is used to indicate that the target device has established a binding relationship with a second account, wherein the first request instruction is used to determine from the second account whether to allow the establishment of a binding relationship between the first account and the target device, and the first request instruction carries an account identifier of the first account; and establishing a binding relationship between the first account and the target device when a first response instruction is obtained that is sent by the second account in response to the first request instruction and the first response instruction is used to indicate that the establishment of a binding relationship between the first account and the target device is allowed.
[0009] In an exemplary embodiment, the method further includes: sending a second indication message to the first account when the binding status is used to indicate that the target device has established a binding relationship with a second account, wherein the second indication message is used to instruct the first account to send image data of the target object corresponding to the first account; sending a second request instruction to the second account when the target image data sent by the first account is obtained, wherein the second request instruction is used to determine whether to allow the establishment of a binding relationship between the first account and the target device to the second account, and the second request instruction carries the target image data; establishing a binding relationship between the first account and the target device when a second response instruction sent by the second account in response to the second request instruction is obtained, and the second response instruction is used to indicate that the establishment of a binding relationship between the first account and the target device is allowed.
[0010] In an exemplary embodiment, after sending the first indication information to the first account, the method further includes: if a character string sent by the first account is obtained multiple times within a first preset time and none of the multiple obtained character strings is the target character string, prohibiting establishment of a binding relationship between the first account and the target device within a second preset time.
[0011] In an exemplary embodiment, before sending the target string to the second account, the method further includes: generating a first string based on the account identifier of the first account and the account identifier of the second account; and enhancing the first string through an artificial intelligence model to obtain the target string.
[0012] In an exemplary embodiment, the method further includes: when the binding status is used to indicate that the target device has established a binding relationship with a second account, determining whether the account identifier of the first account is located in a target list, wherein the target list is a list set for the second account, and the target list has multiple account identifiers, and the account corresponding to each account identifier is allowed to establish a binding relationship with the target device; when it is determined that the account identifier of the first account is located in the target list, not sending a target string to the second account, and not sending a first indication message to the first account, and establishing a binding relationship between the first account and the target device; wherein, when it is determined that the account identifier of the first account is not located in the target list, sending a target string to the second account, and sending a first indication message to the first account.
[0013] According to another aspect of an embodiment of the present application, a device binding apparatus is provided, comprising: a verification module, for verifying the binding status of a target device when a binding request sent by a first account is obtained, wherein the binding request carries a device identification of the target device; a sending module, for sending a target string to a second account when the binding status indicates that the target device has established a binding relationship with the second account, and for sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a string to be verified; a binding module, for establishing a binding relationship between the first account and the target device when the target string sent by the first account is obtained.
[0014] According to another aspect of the embodiments of the present application, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored program, wherein the computer program is configured to execute the above-mentioned device binding method when running.
[0015] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, wherein the processor is configured to execute the above-mentioned device binding method through the computer program.
[0016] According to another aspect of the embodiments of the present application, a computer program product is provided, including a computer program, and the computer program performs the above-mentioned device binding method when executed by a processor.
[0017] Through this application, when the first account initiates a device binding request, the device is verified. If the device has been bound to the second account, a target string is sent to the second account. If the same target string is received from the first account, the first account and the device are bound. Since the first account and the device are bound by verifying the same target string when the device is already bound, the problem of poor security when the device is bound to multiple people is solved. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0020] Figure 1 is a hardware environment schematic diagram of a device binding method according to an embodiment of the present application;
[0021] Figure 2 is a flow chart of a device binding method according to an embodiment of the present application;
[0022] Figure 3 is a timing diagram of an optional device binding process according to an embodiment of the present application;
[0023] Figure 4 is a structural block diagram of a device binding apparatus according to an embodiment of the present application;
[0024] Figure 5 It is a structural block diagram of another device binding apparatus according to an embodiment of the present application. DETAILED DESCRIPTION
[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.
[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0027] According to one aspect of an embodiment of the present application, a device binding method is provided. The device binding method is widely used in smart home (Smart Home), smart home, smart home device ecology, smart residential (IntelligenceHouse) ecology and other whole-house intelligent digital control application scenarios. Optionally, in this embodiment, the above-mentioned device binding method can be applied to Figure 1 In the hardware environment composed of the terminal device 102 and the server 104 shown in FIG. Figure 1 As shown, the server 104 is connected to the terminal device 102 via a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.
[0028] The network may include but is not limited to at least one of the following: wired network, wireless network. The wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal device 102 may be but is not limited to a PC, a mobile phone, a tablet computer, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing device, a smart dishwasher, a smart projection device, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart fresh air device, a smart kitchen and bathroom device, a smart bathroom device, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification device, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, etc.
[0029] In order to solve the above problems, a device binding method is provided in this embodiment, including but not limited to being applied to the whole house intelligent digital control application scenario. Figure 2 : is a flow chart of a device binding method according to an embodiment of the present application, the process includes the following steps S202-S206:
[0030] Step S202: upon obtaining a binding request sent by the first account, verifying the binding status of the target device, wherein the binding request carries a device identifier of the target device;
[0031] Optionally, when the device is an IoT device, it may support multiple ways of sending binding requests, including but not limited to: Wireless Fidelity (WiFi), Bluetooth, Zigbee, etc.
[0032] Optionally, when the device is a smart home device, the first account is an account used to log in to an application corresponding to the smart home device, wherein the application is used to control functions of the device (for example, turning on and / or off, gear speed, wind direction, etc.).
[0033] Optionally, when the binding status is used to indicate that the target device is not bound to an account, a binding relationship between the first account and the target device is directly established.
[0034] Step S204: When the binding state indicates that the target device has established a binding relationship with a second account, sending a target string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a string to be verified;
[0035] Optionally, the target character string may be a verification code, an authorization key, etc.
[0036] Optionally, the target string has a time limit. When the effective time of the target string is exceeded (for example, ten minutes), the target string sent by the acquired first account cannot be recognized, that is, the target string cannot be verified.
[0037] Step S206: when the target character string sent by the first account is obtained, a binding relationship between the first account and the target device is established.
[0038] It should be noted that since the server only sends the target string to the second account, if the target string sent by the first account is obtained, it means that the second account has informed the first account of the target string sent by the server, that is, the second account allows the first account to bind to the target device, thereby ensuring that only accounts allowed by the second account can be bound to the IoT device, and at the same time ensuring the security of the process of communication between the device and the IoT cloud.
[0039] In the above steps, when the first account initiates a device binding request, the device is verified, and if the device is already bound to the second account, the target string is sent to the second account, and if the same target string is received from the first account, the first account and the device are bound. Since the first account and the device are bound by verifying the same target string when the device is already bound, the problem of poor security when the device is bound to multiple people is solved.
[0040] In an exemplary embodiment, the method further comprises the following steps S11-S12:
[0041] Step S11: When the binding state indicates that the target device has established a binding relationship with a second account, sending a first request instruction to the second account, wherein the first request instruction is used to determine whether to allow the second account to establish a binding relationship between the first account and the target device, and the first request instruction carries an account identifier of the first account;
[0042] Optionally, the account identifier of the first account can be the username, mobile phone number, email address or other information used to uniquely identify the account. Through the account identifier, the second account can accurately confirm the identity of the first account that initiates the binding request, so as to make corresponding processing and decide whether to allow the binding relationship to be established.
[0043] Step S12: establishing a binding relationship between the first account and the target device when a first response instruction sent by the second account in response to the first request instruction is obtained and the first response instruction is used to indicate that establishment of a binding relationship between the first account and the target device is allowed.
[0044] It should be noted that, through the above steps, the account identification of the first account is sent to the second account, so that the second account verifies the identity of the first account, and returns the first response instruction if it is confirmed to be allowed, thereby binding the first account and the target device.
[0045] In an exemplary embodiment, the method further comprises the following steps S21-S23:
[0046] Step S21: When the binding state indicates that the target device has established a binding relationship with the second account, sending second indication information to the first account, wherein the second indication information is used to instruct the first account to send image data of the target object corresponding to the first account;
[0047] Optionally, the image data of the target object is a real-time facial image, which is used to display a real image of the current user of the first account.
[0048] Step S22: When the target image data sent by the first account is obtained, a second request instruction is sent to the second account, wherein the second request instruction is used to determine whether to allow the second account to establish a binding relationship between the first account and the target device, and the second request instruction carries the target image data;
[0049] Optionally, when it is detected that the image data of the target object corresponding to the first account sent by the first account is not real-time data, the second request instruction is stopped from being sent to the second account, and the establishment of a binding relationship between the first account and the target device is prohibited.
[0050] Step S23: establishing a binding relationship between the first account and the target device when a second response instruction sent by the second account in response to the second request instruction is obtained and the second response instruction is used to indicate that establishment of a binding relationship between the first account and the target device is allowed.
[0051] In an exemplary embodiment, after sending the first indication information to the first account, the method further includes the following steps: if the character string sent by the first account is obtained multiple times within the first preset time and the multiple obtained character strings are not the target character string, prohibiting the establishment of a binding relationship between the first account and the target device within a second preset time.
[0052] Optionally, if the verification code sent by the first account is received five times in succession within ten minutes, and none of the five verification codes is a verification code sent to the second account, then the binding relationship between the first account and the target device is prohibited from being established within the next thirty minutes.
[0053] Optionally, when the second preset time is thirty minutes, after thirty minutes, if the verification code sent by the first account is obtained ten times, the second preset time is extended to one hour for the second time.
[0054] In an exemplary embodiment, after prohibiting the establishment of a binding relationship between the first account and the target device within a second preset time, the method further includes the following steps: obtaining a third request instruction sent by the second account, wherein the third request instruction is used to instruct to lift the prohibition on establishing a binding relationship between the first account and the target device within the second preset time.
[0055] Optionally, when the first account is prohibited from establishing a binding relationship with the target device within the second preset time, a fourth request instruction is sent to the second account, wherein the fourth request instruction carries the account identifier of the first account, and the fourth request instruction is used to instruct the second account to send a third request instruction.
[0056] In an exemplary embodiment, before sending the target character string to the second account, the method further includes the following steps S31-S32:
[0057] Step S31: generating a first character string according to the account identifier of the first account and the account identifier of the second account;
[0058] Optionally, the account identifier of the first account and the account identifier of the second account may be combined to generate a first character string. For example, if the account identifier of the first account is XY4653 and the account identifier of the second account is MN5213, the generated first character string is XYMN46535213.
[0059] Step S32: Enhance the first character string through an artificial intelligence model to obtain the target character string.
[0060] Optionally, the artificial intelligence model can use natural language processing technology to enhance the first string, or use an encryption algorithm to encrypt the first string to obtain a target string, wherein the encryption algorithm includes but is not limited to: Advanced Encryption Standard encryption algorithm (Advanced Encryption Standard, referred to as AES), RSA public key encryption algorithm, etc.
[0061] In an exemplary embodiment, the method further includes the following steps S41 to S43:
[0062] Step S41: when the binding state indicates that the target device has established a binding relationship with the second account, determining whether the account identifier of the first account is located in a target list, wherein the target list is a list set by the second account, the target list has multiple account identifiers, and the account corresponding to each account identifier is allowed to establish a binding relationship with the target device;
[0063] Step S42: if it is determined that the account identifier of the first account is in the target list, not sending the target string to the second account, not sending the first indication information to the first account, and establishing a binding relationship between the first account and the target device;
[0064] That is, when the account identifier of the first account is in the target list, the binding relationship between the first account and the target device is directly established without re-verifying the first account through the second account;
[0065] Step S43: When it is determined that the account identifier of the first account is not in the target list, a target character string is sent to the second account, and first indication information is sent to the first account.
[0066] That is, when the account identifier of the first account is not in the target list, the first account needs to be verified through the second account to further determine whether to allow the first account to establish a binding relationship with the target device.
[0067] Optionally, the execution subject of the above steps is a server, and the server can be a server of the target device or a server of a cloud system corresponding to the target device.
[0068] Obviously, the above-described embodiments are only embodiments of a part of the present invention, rather than all embodiments. In order to better understand the above method, the above process is described below in conjunction with embodiments, but it is not intended to limit the technical solutions of the embodiments of the present invention, specifically:
[0069] Figure 3 The following is an example of an optional device binding process sequence:
[0070] It should be noted that, when the target device is not bound, user A (ie, the second account mentioned above) can be directly bound to the device.
[0071] First, user B (i.e., the first account mentioned above) discovers the target device through some means (such as the above-mentioned WiFi, Bluetooth, etc.) and initiates a device binding request;
[0072] Next, after receiving the device binding request, the server checks the binding status of the target device. If it is a bound device (bound to user A), it generates a verification code and notifies user A of the verification code through the message component. At the same time, it returns an error code indicating that the device is waiting for verification to user B.
[0073] Next, after user A receives the verification code for device binding, he learns that another user is binding a device. If user A agrees to user B binding the device, user A can tell user B the verification code. Otherwise, user A ignores the message.
[0074] Next, if user B obtains the verification code from user A, he can enter the verification code and continue the device binding process. After the server verification code is verified, the device binding is completed; if user B binds the device illegally, user B cannot obtain the verification code from user A, and cannot enter the verification code to continue the device binding process.
[0075] It should be noted that this application can protect bound devices from being bound by malicious accounts, avoid affecting the normal use of users, and avoid property losses for users.
[0076] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.
[0077] In this embodiment, a device binding device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0078] Figure 4 : is a structural block diagram of a device binding apparatus according to an embodiment of the present application, the apparatus comprising:
[0079] A verification module 42, configured to verify the binding status of the target device when a binding request sent by the first account is obtained, wherein the binding request carries a device identifier of the target device;
[0080] A sending module 44, configured to send a target string to a second account and send first indication information to the first account when the binding state indicates that the target device has established a binding relationship with the second account, wherein the first indication information is used to instruct the first account to send a string to be verified;
[0081] The binding module 46 is used to establish a binding relationship between the first account and the target device when the target character string sent by the first account is obtained.
[0082] The above device verifies the device when the first account initiates a device binding request, sends a target string to the second account if the device has been bound to the second account, and binds the first account to the device when the same target string is received from the first account. Since the first account and the device are bound by verifying the same target string when the device has been bound, the problem of poor security when the device is bound to multiple people is solved.
[0083] In an exemplary embodiment, the sending module 44 is further used to send a first request instruction to the second account when the binding status is used to indicate that the target device has established a binding relationship with the second account, wherein the first request instruction is used to determine from the second account whether to allow the establishment of a binding relationship between the first account and the target device, and the first request instruction carries an account identifier of the first account; the binding module 46 is further used to establish a binding relationship between the first account and the target device when a first response instruction sent by the second account in response to the first request instruction is obtained, and the first response instruction is used to indicate that the establishment of a binding relationship between the first account and the target device is allowed.
[0084] In an exemplary embodiment, the sending module 44 is further used to send a second indication message to the first account when the binding status is used to indicate that the target device has established a binding relationship with the second account, wherein the second indication message is used to instruct the first account to send image data of the target object corresponding to the first account; and to send a second request instruction to the second account when the target image data sent by the first account is obtained, wherein the second request instruction is used to determine whether to allow the establishment of a binding relationship between the first account and the target device to the second account, and the second request instruction carries the target image data; the binding module 46 is further used to establish a binding relationship between the first account and the target device when a second response instruction sent by the second account in response to the second request instruction is obtained, and the second response instruction is used to indicate that the establishment of a binding relationship between the first account and the target device is allowed.
[0085] In an exemplary embodiment, Figure 5 It is a structural block diagram of another device binding device according to an embodiment of the present application, and the above-mentioned device also includes: a prohibition module 52, which is used to prohibit the establishment of a binding relationship between the first account and the target device within a second preset time after sending a first indication information to the first account, if the character string sent by the first account is obtained multiple times within a first preset time, and the multiple obtained character strings are not the target character string.
[0086] In an exemplary embodiment, the above-mentioned device also includes: a generation module 54, which is used to generate a first character string according to the account identifier of the first account and the account identifier of the second account before sending the target character string to the second account; and enhance the first character string through an artificial intelligence model to obtain the target character string.
[0087] In an exemplary embodiment, the above-mentioned device also includes: a determination module 56, which is used to determine whether the account identifier of the first account is located in a target list when the binding state is used to indicate that the target device has established a binding relationship with the second account, wherein the target list is a list set for the second account, and the target list has multiple account identifiers, and the account corresponding to each account identifier is allowed to establish a binding relationship with the target device; the binding module 46 is also used to not send the target string to the second account and not send the first indication information to the first account when it is determined that the account identifier of the first account is located in the target list, and establish a binding relationship between the first account and the target device; the sending module 44 is also used to send the target string to the second account and send the first indication information to the first account when it is determined that the account identifier of the first account is not located in the target list.
[0088] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein the computer program is configured to execute the above-mentioned device binding method when running.
[0089] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:
[0090] S1, verifying the binding status of a target device when a binding request sent by a first account is obtained, wherein the binding request carries a device identifier of the target device;
[0091] S2, when the binding state is used to indicate that the target device has established a binding relationship with a second account, sending a target character string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a character string to be verified;
[0092] S3: When the target character string sent by the first account is obtained, a binding relationship between the first account and the target device is established.
[0093] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.
[0094] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.
[0095] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the above-mentioned device binding method through the computer program.
[0096] Optionally, in this embodiment, the electronic device may be configured to perform the following steps through a computer program:
[0097] S1, verifying the binding status of a target device when a binding request sent by a first account is obtained, wherein the binding request carries a device identifier of the target device;
[0098] S2, when the binding state is used to indicate that the target device has established a binding relationship with a second account, sending a target character string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a character string to be verified;
[0099] S3: When the target character string sent by the first account is obtained, a binding relationship between the first account and the target device is established.
[0100] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0101] According to another aspect of the embodiments of the present application, a computer program product is provided, including a computer program, and the computer program performs the above-mentioned device binding method when executed by a processor.
[0102] Optionally, in this embodiment, the computer program product may be configured to perform the following steps through a computer program:
[0103] S1, verifying the binding status of a target device when a binding request sent by a first account is obtained, wherein the binding request carries a device identifier of the target device;
[0104] S2, when the binding state is used to indicate that the target device has established a binding relationship with a second account, sending a target character string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a character string to be verified;
[0105] S3: When the target character string sent by the first account is obtained, a binding relationship between the first account and the target device is established.
[0106] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.
[0107] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.
[0108] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A device binding method, characterized in that: include: When a binding request sent by the first account is obtained, verifying the binding status of the target device, wherein the binding request carries a device identifier of the target device; In a case where the binding state is used to indicate that the target device has established a binding relationship with a second account, sending a target character string to the second account, and sending first indication information to the first account, wherein the first indication information is used to instruct the first account to send a character string to be verified; When the target character string sent by the first account is obtained, a binding relationship between the first account and the target device is established.
2. The device binding method according to claim 1, characterized in that: The method further comprises: In a case where the binding state is used to indicate that the target device has established a binding relationship with a second account, sending a first request instruction to the second account, wherein the first request instruction is used to determine whether to allow the second account to establish a binding relationship between the first account and the target device, and the first request instruction carries an account identifier of the first account; When a first response instruction sent by the second account in response to the first request instruction is obtained, and the first response instruction is used to indicate that establishment of a binding relationship between the first account and the target device is allowed, a binding relationship between the first account and the target device is established.
3. The device binding method according to claim 1, characterized in that: The method further comprises: In a case where the binding state is used to indicate that the target device has established a binding relationship with the second account, sending second indication information to the first account, wherein the second indication information is used to instruct the first account to send image data of the target object corresponding to the first account; In the case of acquiring the target image data sent by the first account, sending a second request instruction to the second account, wherein the second request instruction is used to determine whether to allow the second account to establish a binding relationship between the first account and the target device, and the second request instruction carries the target image data; When a second response instruction sent by the second account in response to the second request instruction is obtained, and the second response instruction is used to indicate that establishment of a binding relationship between the first account and the target device is allowed, a binding relationship between the first account and the target device is established.
4. The device binding method according to claim 1, characterized in that: After sending the first indication information to the first account, the method further includes: If the character strings sent by the first account are obtained multiple times within the first preset time, and the character strings obtained multiple times are not the target character strings, establishing a binding relationship between the first account and the target device is prohibited within the second preset time.
5. The device binding method according to claim 1, characterized in that: Before sending the target character string to the second account, the method further includes: generating a first character string according to the account identifier of the first account and the account identifier of the second account; The first character string is enhanced by using an artificial intelligence model to obtain the target character string.
6. The device binding method according to claim 1, characterized in that: The method further comprises: In a case where the binding state is used to indicate that the target device has established a binding relationship with the second account, determining whether the account identifier of the first account is located in a target list, wherein the target list is a list set by the second account, the target list has multiple account identifiers, and an account corresponding to each account identifier is allowed to establish a binding relationship with the target device; If it is determined that the account identifier of the first account is in the target list, not sending the target character string to the second account, not sending the first indication information to the first account, and establishing a binding relationship between the first account and the target device; Wherein, when it is determined that the account identifier of the first account is not located in the target list, the target character string is sent to the second account, and the first indication information is sent to the first account.
7. A device binding apparatus, characterized in that: include: a verification module, configured to verify the binding status of the target device when a binding request sent by the first account is obtained, wherein the binding request carries a device identifier of the target device; a sending module, configured to send a target character string to a second account and send first indication information to the first account when the binding state indicates that the target device has established a binding relationship with the second account, wherein the first indication information is used to instruct the first account to send a character string to be verified; The binding module is used to establish a binding relationship between the first account and the target device when the target character string sent by the first account is acquired.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method according to any one of claims 1 to 6 when executed.
9. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 6 through the computer program.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.