Multi-device access management method and system, readable storage medium and program product

Abstract

The invention discloses a multi-device access management method and system, a readable storage medium and a program product, and relates to the technical field of device management, the multi-device access management method comprises the following steps: obtaining first networking information of each to-be-bound device and second networking information of a device logged in by a user account; screening out the to-be-bound devices with the same first networking information and second networking information from the to-be-bound devices, and taking the to-be-bound devices as target devices; and controlling the equipment logged in by the user account to display a confirmation key, wherein the confirmation key is used for indicating to establish the binding relationship between the user account and each piece of target equipment. According to the invention, the access efficiency of multiple devices can be improved, and the use experience of a user is improved.

Description

Technical Field

[0001] This application relates to the field of device management technology, and in particular to a multi-device access management method, system, readable storage medium, and program product. Background Technology

[0002] To enhance user experience and enable convenient and efficient control of existing home smart devices, each device needs to be connected to a user account. For example, each indoor unit of a multi-split air conditioner needs to be connected to a smart wired controller, serving as a bridge for interaction between the user and the indoor unit.

[0003] Currently, users typically manually connect each smart device to their account one by one. However, this process involves multiple repetitive connection operations, resulting in low efficiency and negatively impacting the user experience. Summary of the Invention

[0004] The main purpose of this application is to provide a multi-device access management method, system, readable storage medium, and program product, which aims to improve the access efficiency of multiple devices and enhance the user experience.

[0005] To achieve the above objectives, this application provides a multi-device access management method applied in the cloud, the method comprising:

[0006] Obtain the first network connection information of each device to be bound, and the second network connection information of the device logged into by the user account;

[0007] Select the devices whose first network information is the same as the second network information from the devices to be bound, and use them as the target devices.

[0008] The device logged into by the user account displays a confirmation button, which is used to indicate the establishment of a binding relationship between the user account and each of the target devices.

[0009] In one embodiment, after the step of controlling the device logged in by the user account to display a confirmation button, the method further includes:

[0010] If a confirmation button is received, a binding relationship is established between the user account and each of the target devices.

[0011] In one embodiment, the step of establishing the binding relationship between the user account and each of the target devices includes:

[0012] By associating the device information of each target device with the user account, a binding relationship between the user account and each target device is established.

[0013] In one embodiment, after the user account has been bound to each of the target devices, the method further includes:

[0014] Identify each device to be logged in from the target devices; the device to be logged in refers to a target device that has the ability to log in to the user account.

[0015] The device logged into by the user account is controlled to display a login authorization button, which is used to authorize each of the devices to be logged in to the user account.

[0016] In one embodiment, the step of determining each device to be logged in among the target devices includes:

[0017] Obtain the category information of each of the target devices;

[0018] Each target device whose category information is the target category information is designated as the device to be logged in; the target category information is used to indicate that the device has the ability to log in to the user account.

[0019] In one embodiment, after the step of controlling the device logged in by the user account to display the login authorization button, the method further includes:

[0020] If a login authorization button is received, the user account information is sent to each of the devices to be logged in, so that each device can log in to the user account based on the account information.

[0021] In one embodiment, after the user account has been bound to each of the target devices, the method further includes:

[0022] The device information of each target device is sent to the device logged into by the user account, so that each target device is displayed on the device management interface of the device logged into by the user account.

[0023] In addition, to achieve the above objectives, this application also provides a multi-device access management system, which includes a cloud and devices logged in by user accounts;

[0024] The cloud is used to obtain the first network information of each device to be bound and the second network information of the device logged in by the user account; to filter out each device to be bound whose first network information and second network information are the same as each target device; and to control the device logged in by the user account to display a confirmation button, the confirmation button being used to indicate the establishment of a binding relationship between the user account and each target device.

[0025] In addition, to achieve the above objectives, this application also provides an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the multi-device access management method described above.

[0026] In addition, to achieve the above objectives, this application also provides a readable storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the multi-device access management method described above.

[0027] In addition, to achieve the above objectives, this application also provides a program product, which is a computer program product. The computer program product includes a computer program, which, when executed by a processor, implements the steps of the multi-device access management method described above.

[0028] This application provides a multi-device access management method applied in the cloud. First, it obtains the first network information of each device to be bound and the second network information of the device logged into by the user account. Then, it filters out devices whose first and second network information match, designating them as target devices to quickly identify those that can be bound to the user account. Next, it controls the device logged into by the user account to display a confirmation button. Since the confirmation button indicates the establishment of the binding relationship between the user account and each target device, subsequent triggering of this confirmation button can complete the batch establishment of the binding relationship between each target device and the user account. Because the entire access process is basically automated by the cloud, and device access is also done in batches rather than one by one, this application not only improves the access efficiency of multiple devices but also enhances the user experience compared to conventional manual access methods. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0030] To more clearly illustrate the technical solutions in the embodiments of 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, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 A flowchart illustrating the multi-device access management method provided in the first embodiment of this application;

[0032] Figure 2 A schematic diagram illustrating an implementation scenario of the multi-device access management method provided in this application embodiment;

[0033] Figure 3 A schematic diagram of the module structure of the multi-device access management system provided in this application embodiment;

[0034] Figure 4 A schematic diagram illustrating the implementation process of the multi-device access management system provided in this application embodiment;

[0035] Figure 5 This is a schematic diagram of the hardware operating environment involved in the embodiments of this application.

[0036] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0037] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0038] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0039] To enhance user experience and enable convenient and efficient control of existing home smart devices, each device needs to be connected to a user account. For example, each indoor unit of a multi-split air conditioner needs to be connected to a smart wired controller, serving as a bridge for interaction between the user and the indoor unit.

[0040] Currently, users typically connect each smart device to their account manually, one by one. The connection process might involve: first, the smart device connects to Wi-Fi and logs into the cloud as a device; then, the smart device generates a QR code, which the device logged in with the user account scans to bind the user account to the smart device, or the device logged in with the user account binds the user account to the smart device via Bluetooth, or other methods; next, if the smart device is confirmed to be eligible to log into the user account, the device logged in with the user account can authorize the smart device to use appropriate means (such as entering the account name on the screen) to log into the user account, allowing the smart device to log in to the cloud as the user and control and manage other devices under the user account. However, users must repeat the above steps for each smart device connected to their account, resulting in low connection efficiency and negatively impacting the user experience.

[0041] Based on this, this application provides a multi-device access management method applied in the cloud. First, it obtains the first network information of each device to be bound and the second network information of the device logged into by the user account. Then, it filters out devices whose first and second network information are identical, designating them as target devices to quickly identify those that can be bound to the user account. Next, it controls the device logged into by the user account to display a confirmation button. Since the confirmation button indicates the establishment of the binding relationship between the user account and each target device, subsequent triggering of this confirmation button can complete the batch establishment of the binding relationship between each target device and the user account. Because the entire access process is basically automated by the cloud, and device access is also done in batches rather than one by one, compared to conventional manual access methods, this application not only improves the access efficiency of multiple devices but also enhances the user experience.

[0042] The execution subject of the multi-device access management method of this application can be an electronic device, such as a mobile phone, computer, tablet computer, etc.; it can also be a control device, control system, control circuit, etc. that can realize data processing, network communication and program operation functions. This embodiment does not specifically limit it.

[0043] The following description uses an electronic device as the execution subject to illustrate the various embodiments.

[0044] Based on this, this application proposes a multi-device access management method according to the first embodiment, which is applied in the cloud. Please refer to [link / reference]. Figure 1 The multi-device access management method may include steps S10 to S30:

[0045] Step S10: Obtain the first network information of each device to be bound and the second network information of the device logged into by the user account;

[0046] It should be noted that "multiple devices" refers to at least two smart devices. Network information refers to information about the local area network (LAN) to which the relevant devices are connected. This network information may include, but is not limited to, the LAN's BSSID (Basic Service Set Identifier) ​​and signal strength. The first network information refers to information about the LAN currently connected to by each device to be bound, and the second network information refers to information about the LAN currently connected to by the device logged into by the user account. The device logged into by the user account refers to the device logged into using the user account, such as an air conditioner.

[0047] Step S20: Select the devices to be bound from the devices to be bound whose first network information and second network information are the same, and use them as the target devices;

[0048] It should be noted that the target device refers to a device that can be bound to a user account.

[0049] Understandably, the second network information of the device logged into by the user account indicates which smart devices on the local area network the user account can bind to. If the first and second network information of the device to be bound are the same, it indicates that the device to be bound is connected to the same local area network as the device logged into by the user account. Therefore, devices with the same first and second network information can be considered as devices that can be bound to the user account.

[0050] Step S30: Control the device logged into by the user account to display a confirmation button. The confirmation button is used to indicate the establishment of a binding relationship between the user account and each target device.

[0051] This embodiment provides a multi-device access management method applied in the cloud. First, it acquires the first network information of each device to be bound and the second network information of the device logged into by the user account. Then, it filters out devices whose first and second network information match, designating them as target devices to quickly identify those that can be bound to the user account. Next, it controls the device logged into by the user account to display a confirmation button. Since the confirmation button indicates the establishment of the binding relationship between the user account and each target device, subsequent triggering of this confirmation button can complete the batch establishment of the binding relationship between each target device and the user account. Because the entire access process is basically automated by the cloud, and device access is also done in batches rather than one by one, this embodiment not only improves the access efficiency of multiple devices but also enhances the user experience compared to conventional manual access methods.

[0052] Based on the first embodiment described above, a second embodiment of the multi-device access management method of this application is proposed. In the second embodiment, after step S30, the multi-device access management method may further include step S40:

[0053] Step S40: If a confirmation button trigger command is received, the binding relationship between the user account and each target device is established.

[0054] It should be noted that after the device logged into the user account displays the confirmation button, if the user presses the confirmation button, the device logged into the user account will send a signal to the cloud, which is the trigger command for the confirmation button.

[0055] In one possible implementation, step S40 may include step S41:

[0056] Step S41: By associating the device information of each target device with the user account, a binding relationship between the user account and each target device is established.

[0057] It should be noted that device information may include, but is not limited to, device ID.

[0058] Understandably, after receiving the confirmation button's trigger command, the cloud can directly associate the device information of each target device with the user account, since it records the user account and the device information of each target device, thus establishing the binding relationship between each target device and the user account in batches.

[0059] Based on the first and / or second embodiments described above, a third embodiment of the multi-device access management method of this application is proposed. In the third embodiment, after the user account and each target device have been bound together, the multi-device access management method may further include steps S50 to S60:

[0060] Step S50: Determine each device to be logged in among the target devices; a device to be logged in refers to a target device that has the ability to log in to a user account.

[0061] It should be noted that not all smart devices have the ability to log in with a user account. For example, smart air conditioner remote controllers have the ability to log in with a user account, while air conditioner remote controllers with broken codes do not.

[0062] In one feasible implementation, step S50 may include steps S51 to S52:

[0063] Step S51: Obtain the category information of each target device;

[0064] It should be noted that category information is used to characterize the attributes and capabilities of the target device, and category information may include, but is not limited to, category ID.

[0065] Step S52: Each target device with the category information of the target category is designated as a device to be logged in; the target category information is used to indicate that the device has the ability to log in to a user account.

[0066] Understandably, if the target device's category information matches the target category information, it means that the target device has the ability to log in to a user account. Subsequently, the user can control and manage other devices under that user account by logging in.

[0067] Step S60: Control the device logged in by the user account to display the login authorization button. The login authorization button is used to authorize each device to log in to the user account.

[0068] In this embodiment, after the user account is bound to each target device, the cloud can automatically identify a batch of target devices capable of logging into the user account, as the devices to be logged in. Then, the device logged into by the user account displays a login authorization button. Since the login authorization button is used to authorize each device to log in to the user account, subsequent triggering of this button allows batch authorization for each device to log in to the user account. Therefore, since the user account login operation during the smart device access process is also automatically performed by the cloud without manual intervention, and the user account login operation for multiple smart devices is performed in batches rather than one by one, this embodiment further improves the access efficiency of multiple devices and enhances the user experience by simultaneously eliminating the manual binding and user account login operations involved in the smart device access process.

[0069] Based on the third embodiment described above, a fourth embodiment of the multi-device access management method of this application is proposed. In the fourth embodiment, after step S30, the multi-device access management method may further include step S70:

[0070] In step S70, if a login authorization button trigger command is received, the user account information is sent to each device to be logged in, so that each device can log in to the user account based on the account information.

[0071] It should be noted that user account information may include, but is not limited to, the user account ID, password, and basic user information. After the login authorization button is displayed on the device where the user account is logged in, if the user presses the login authorization button, the device will send a signal to the cloud, which is the trigger command for the login authorization button.

[0072] In one feasible implementation, to ensure that user account information is not leaked or tampered with during transmission, the cloud can send user account information to each device waiting to log in through an encrypted channel.

[0073] Based on the first, second, third, and / or fourth embodiments described above, a fifth embodiment of the multi-device access management method of this application is proposed. In the fifth embodiment, after the user account and each target device have been bound together, the multi-device access management method may further include step S80:

[0074] Step S80: Send the device information of each target device to the device logged in by the user account, so that each target device can be displayed on the device management interface of the device logged in by the user account.

[0075] It should be noted that the device management interface is used to manage related devices. The device management interface displays the various devices that can be managed by the user's logged-in account.

[0076] This embodiment sends the device information of each target device to the device logged into the user account, so that each target device can be displayed on the device management interface of the device logged into the user account. This allows management of each target device from the device logged into the user account.

[0077] In one feasible implementation, to ensure that the device information of each target device is not leaked or tampered with during transmission, the cloud can send the device information of each target device to the device logged into the user account through an encrypted channel.

[0078] In one feasible implementation, after step S40, certain identification methods (such as adding identifiers or changing the color of the device ID display font) can be used on the device management interface to identify each device to be logged in among the target devices. This allows users to intuitively understand which target devices are to be logged in, i.e., devices capable of logging in with a user account. Thus, users can flexibly select the devices from the list of devices to be logged in with their user account as candidate devices. After receiving the login authorization button trigger command, the cloud only needs to send the user account information to each candidate device, i.e., only to the devices selected by the user to log in with their user account, thereby enabling personalized user operations.

[0079] For example, to help understand the implementation scenario of the multi-device access management method obtained by combining the above embodiments, please refer to... Figure 2 , specifically:

[0080] After each device to be bound is connected to the local area network, it will automatically establish a connection with the cloud (for example, each device can log in to the cloud using its device ID). After the connection is established, the cloud will obtain the first network information of each device and compare it with the second network information of the device logged in by the user account. The cloud will then select the devices whose first and second network information match as the target devices. Next, the cloud will control the device logged in by the user account to display a confirmation button. After receiving the confirmation button's trigger command, the cloud will associate the device information of each target device with the user account, thus binding the user account to each target device.

[0081] After the user account is bound to each target device, the cloud will obtain the category information of each target device to filter out the target devices that have the ability to log in to the user account as the devices to be logged in. Then, the cloud will control the device logged in by the user account to display the login authorization button. After receiving the login authorization button trigger command, the cloud will send the user account information to each device to be logged in, so that each device can log in to the user account based on the account information.

[0082] It should be noted that this example is only for the purpose of assisting in understanding this application and does not constitute a limitation on the multi-device access management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0083] This application also provides a multi-device access management system; please refer to... Figure 3 and Figure 4 The multi-device access management system includes cloud 10 and devices logged in by user accounts 20;

[0084] Cloud 10 is used to obtain the first network information of each device to be bound and the second network information of the slave devices bound to the device 20 logged in by the user account; it filters out the devices to be bound that have the same first network information and second network information from the devices to be bound as the target devices; it controls the device 20 logged in by the user account to display a confirmation button, which is used to indicate the establishment of the binding relationship between the user account and each target device.

[0085] Optionally, Cloud 10 is also used for:

[0086] If a confirmation button is received, a binding relationship is established between the user account and each target device.

[0087] Optionally, Cloud 10 is also used for:

[0088] By associating the device information of each target device with the user account, a binding relationship between the user account and each target device is established.

[0089] Optionally, after the user account has been bound to each target device, Cloud 10 is also used for:

[0090] Identify each device to be logged in from among the target devices; a device to be logged in refers to a target device that has the ability to log in to a user account.

[0091] The device 20 that controls the user account displays a login authorization button, which is used to authorize each device to log in to the user account.

[0092] Optionally, Cloud 10 is also used for:

[0093] Obtain category information for each target device;

[0094] Each target device whose category information is the target category information is designated as a device to be logged in; the target category information is used to indicate that the device has the ability to log in to a user account.

[0095] Optionally, Cloud 10 is also used for:

[0096] If a login authorization button is received, the user's account information is sent to each device waiting to log in, so that each device can log in to the user's account based on the account information.

[0097] Optionally, after the user account has been bound to each target device, Cloud 10 is also used for:

[0098] The device information of each target device is sent to device 20 where the user account is logged in, so that each target device can be displayed on the device management interface of device 20 where the user account is logged in.

[0099] The multi-device access management system provided in this application adopts the multi-device access management method described in the above embodiments, which can improve the access efficiency of multiple devices and enhance the user experience. Compared with the prior art, the beneficial effects of the multi-device access management system provided in this application are the same as those of the multi-device access management method described in the above embodiments, and will not be repeated here.

[0100] This application also provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the multi-device access management method described above.

[0101] The following is for reference. Figure 5 It shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of this application. Figure 5 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0102] like Figure 5As shown, the electronic device may include a processing unit 101 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 102 or a program loaded from a storage device 103 into a random access memory (RAM) 104. The RAM 104 also stores various programs and data required for the operation of the electronic device. The processing unit 101, ROM 102, and RAM 104 are interconnected via a bus 105. An input / output (I / O) interface 106 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 106: input devices 107 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 108 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 103 including, for example, magnetic tapes, hard disks, etc.; and communication devices 109. The communication device 109 allows the electronic device to exchange data with other devices wirelessly or via wired communication. Although the diagrams show electronic devices with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented alternatively.

[0103] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 103, or installed from ROM 102. When the computer program is executed by processing device 101, it performs the functions defined in the methods of the embodiments of this application.

[0104] The electronic device provided in this application, employing the multi-device access management method described above, can improve the access efficiency of multiple devices and enhance the user experience. Compared with the prior art, the beneficial effects of the electronic device provided in this application are the same as those of the multi-device access management method described above, and other technical features of the electronic device are the same as those disclosed in the methods described above, and will not be repeated here.

[0105] It should be understood that various parts of the embodiments of this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

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

[0107] This application also provides a computer-readable storage medium storing a computer program that can run on a processor. The computer program is used to execute the multi-device access management method described in the above embodiments.

[0108] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0109] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0110] The aforementioned computer-readable storage medium carries one or more programs that, when executed by an electronic device, cause the electronic device to: acquire first network information of each device to be bound and second network information of the device logged in by the user account; select devices from the devices to be bound whose first network information and second network information are the same as each target device; and control the device logged in by the user account to display a confirmation button, the confirmation button being used to indicate the establishment of a binding relationship between the user account and each target device.

[0111] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0113] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0114] The computer-readable storage medium provided in this application embodiment stores computer-readable program instructions for executing the above-described multi-device access management method, which can improve the access efficiency of multiple devices and enhance the user experience. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application embodiment are the same as the beneficial effects of the multi-device access management method provided in the above embodiments, and will not be repeated here.

[0115] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the multi-device access management method described above.

[0116] The computer program product provided in this application can improve the access efficiency of multiple devices and enhance the user experience. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the multi-device access management method provided in the above embodiments, and will not be repeated here.

[0117] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A multi-device access management method, characterized by, Applied to the cloud, the method comprises: Obtaining the first networking information of each to-be-bound device, the second networking information of the device logged in by the user account; From each of the to-be-bound devices, each to-be-bound device with the same first networking information and the second networking information is selected as each target device; Control the device logged in by the user account to display a confirmation button, and the confirmation button is used to indicate the establishment of the binding relationship between the user account and each target device.

2. The multi-device access management method of claim 1, wherein, After the step of controlling the device logged in by the user account to display the confirmation button, the method further comprises: If a trigger instruction of the confirmation button is received, the binding relationship between the user account and each target device is established.

3. The multi-device access management method of claim 2, wherein, The step of establishing the binding relationship between the user account and each target device comprises: By associating the device information of each target device with the user account, the binding relationship between the user account and each target device is established.

4. The multi-device access management method according to any one of claims 1 to 3, wherein, After the binding relationship between the user account and each target device is established, the method further comprises: Determine each to-be-logged-in device in each target device; the to-be-logged-in device refers to a target device with the ability to log in the user account; Control the device logged in by the user account to display a login authorization button, and the login authorization button is used to authorize each to-be-logged-in device to log in the user account.

5. The multi-device access management method of claim 4, wherein, The step of determining each to-be-logged-in device in each target device comprises: Obtaining the category information of each target device; Each target device with target category information is used as each to-be-logged-in device; the target category information is used to represent the ability of the device to log in the user account.

6. The multi-device access management method of claim 5, wherein, After the step of controlling the device logged in by the user account to display the login authorization button, the method further comprises: If a trigger instruction of the login authorization button is received, the account information of the user account is sent to each to-be-logged-in device, so that each to-be-logged-in device logs in the user account based on the account information.

7. The multi-device access management method according to any one of claims 1 to 3, wherein After the binding relationship between the user account and each target device is established, the method further comprises: Send the device information of each target device to the device logged in by the user account, so as to display each target device on the device management interface of the device logged in by the user account.

8. A multi-device access management system, characterized by, The multi-device access management system comprises a cloud and a device logged in by a user account; The cloud is used to obtain the first networking information of each to-be-bound device, the second networking information of the device logged in by the user account; from each of the to-be-bound devices, each to-be-bound device with the same first networking information and the second networking information is selected as each target device; control the device logged in by the user account to display a confirmation button, and the confirmation button is used to indicate the establishment of the binding relationship between the user account and each target device.

9. A readable storage medium, characterized by, The readable storage medium is a computer readable storage medium, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to realize the steps of the multi-device access management method in any one of claims 1 to 7.

10. A program product, characterized by The program product is a computer program product, which comprises a computer program, and the computer program realizes the steps of the multi-device access management method in any one of claims 1 to 7 when executed by a processor.

Images