Device association method, electronic device and computer program product

Abstract

The invention discloses a device association method, an electronic device and a computer program product. The method comprises the following steps: acquiring capability attributes of new network access equipment, wherein the capability attributes comprise basic capability and capability types; retrieving the network-accessed equipment to search target equipment, wherein the capability attribute of the target equipment is matched with the capability attribute of the new network-accessed equipment; and based on the searched target device, establishing an association relationship between the new network access device and the target device. Through the mode, the convenience of the equipment association operation can be improved, and the efficiency of the equipment association operation is improved.

Description

Technical Field

[0001] This application relates to the field of equipment control, and in particular to a method for associating equipment, electronic equipment, and computer program products. Background Technology

[0002] With the development of science and technology, scenarios where devices are linked and work together are becoming increasingly common. In typical linkage scenarios, users need to first preset the linkage scenario, add the terminal to the scenario, and write the scenario's characteristics into the terminal's data structure. When a new terminal connects, linkage is determined based on the scenario and some identifiers of existing terminals. Furthermore, the new terminal and the terminals in the scenario must be preset devices that can be linked together; otherwise, linkage will still fail. This method requires multiple steps and is cumbersome and complex. Summary of the Invention

[0003] The main purpose of this application is to provide a device association method, electronic device, and computer program product that can improve the convenience and efficiency of device association operations.

[0004] This application provides a device association method. This method is applied to a gateway device, which has at least one already connected device connected to it. The method includes obtaining the capability attributes of the newly connected device, including basic capabilities and capability types; searching existing connected devices to find a target device, where the capability attributes of the target device match the capability attributes of the newly connected device; and establishing an association between the newly connected device and the target device based on the searched target device.

[0005] This application provides an electronic device. The electronic device includes a memory and a processor. The memory stores program data, which can be executed by the processor to implement the device association method as described in the first technical solution.

[0006] This application provides a computer program product. The computer program product stores program data and can be executed by a processor to implement the device association method as described in the first and / or second technical solutions.

[0007] The beneficial effects of this application include at least the following: after a device joins the network, the gateway device obtains its capability attributes and directly associates the newly joined device with the already joined device based on the device's basic capabilities and capability type in the capability attributes, making the association operation simple, convenient, fast and efficient, and improving the efficiency of device association operations. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 This is a flowchart illustrating the first embodiment of the device association method of this application;

[0010] Figure 2 This is a flowchart illustrating the second embodiment of the device association method of this application;

[0011] Figure 3 This is a schematic diagram of a display interface;

[0012] Figure 4 This is another schematic diagram of the display interface after the basic functions have been adjusted;

[0013] Figure 5 This is a flowchart illustrating the third embodiment of the device association method of this application;

[0014] Figure 6 This is a flowchart illustrating a specific embodiment of the device association method of this application;

[0015] Figure 7 This is a schematic diagram of the structure of the first embodiment of the electronic device of this application;

[0016] Figure 8 This is a schematic diagram of the structure of an embodiment of the computer program product of this application. Detailed Implementation

[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0018] The terms "first," "second," etc., used in this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0019] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0020] Reference Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the device association method of this application. This method can be applied to a gateway device that has at least one network-connected device connected to it. It includes, but is not limited to, the following steps.

[0021] S11: Obtain the capability attributes of newly joined devices. Capability attributes include basic capabilities and capability types.

[0022] The basic capabilities of a device are those required for it to perform normal associated operations. Capability types are attributes corresponding to each capability. Capability types can include server-side and client-side classes. Server-side and client-side classes are complementary capability types. Capabilities with complementary types are considered to be associated with each other, while capabilities with the same type are considered not to be associated with each other. Each capability in a device has its corresponding capability type. For example, for a switch capability, the capability type in device A can be a server-side class, while the capability type in device B can be a client-side class. Therefore, without other restrictions, the switch capabilities in device A and device B can be considered associative. The same device can have capabilities with different capability types. For example, device A has switch and temperature measurement capabilities; the switch capability in device A can be a server-side capability, while the temperature measurement capability in device A can be a client-side capability.

[0023] S12: Search for the target device by retrieving the network-connected devices, and match the capability attributes of the target device with the capability attributes of the newly connected device.

[0024] After a new device joins the network, the gateway device matches it with existing network-connected devices based on its capability attributes to find a target device that can be associated with the new device. Each device sends its capability attributes to the gateway device after joining the network. The gateway device stores these capability attributes for subsequent device association steps, allowing it to be retrieved directly when association operations require the new device's capability attributes. The gateway device can also request the new device to provide its capability attributes at any time after joining the network to update the device's capability attributes. After a new device joins the network, the gateway device matches its capability attributes with the stored capability attributes of existing network-connected devices. Alternatively, after a new device joins the network, the gateway device sends a capability attribute retrieval message to all existing network-connected devices to update their capability attributes. Or, after a new device joins the network, the gateway device sends a capability attribute retrieval message to existing network-connected devices in the list that do not yet have corresponding capability attributes to update their capability attributes.

[0025] S13: Based on the target devices obtained from the search, establish the association between the newly added network devices and the target devices.

[0026] The gateway device can establish an association between a newly connected device and a target device in the following two ways.

[0027] In one embodiment, after a target device is found, the gateway device sends an association notification to the newly joined device or the target device, so that the newly joined device or the target device can initiate an association operation with the other party.

[0028] In one embodiment, if a target device exists, the gateway sends an association notification to either the new network-entering device or the target device to establish an association between them. If multiple target devices exist, the new network-entering device establishes an association with each target device. If no target device exists, the new network-entering device only needs to complete the normal network entry process with the gateway device.

[0029] In one embodiment, after a target device is found, the gateway device controls the newly joined device to establish an association with the target device.

[0030] Specifically, the gateway device can send first control information to a newly joined device. This first control information may include the target device's identifier, its capability attributes, and other information, allowing the gateway device to add the target device to its association list. The gateway device also sends second control information to the target device, which may also include the newly joined device's identifier, its capability attributes, and other information, allowing the gateway device to add the newly joined device to its association list.

[0031] In this embodiment, after a device joins the network, the gateway device obtains its capability attributes and automatically associates the newly joined device with the existing device based on the device's basic capabilities and capability type in the capability attributes. This makes the association operation simple, convenient, fast, and efficient, thus improving the efficiency of the device association operation.

[0032] In one embodiment, the capability attributes of the target device are matched with the capability attributes of the newly joined device, including: the basic capabilities of the newly joined device and the basic capabilities of the target device are the same; the capability type of the same capability in the target device is complementary to the capability type in the newly joined device.

[0033] In yet another embodiment, the capability attribute also includes the capabilities supported by the device, which are the capabilities that the device has. If the capability attribute of the target device matches the capability attribute of the newly connected device, the following are included: the capabilities supported by the newly connected device meet the basic capability requirements of the target device; the capabilities supported by the target device meet the basic capability requirements of the newly connected device; and the capability type of the same capability in the target device is complementary to the capability type in the newly connected device.

[0034] As mentioned above, capability types can include server-side classes and client-side classes. These are complementary capability types. Complementarity indicates the correspondence between the two types in sending and receiving information. For example, suppose the switching capabilities in device A and device B are interconnected. Device A's switching capability is a server-side class, and device B's switching capability is a client-side class. This means that device A sends switching information, and device B receives the switching information sent by device A to perform the corresponding switching operation.

[0035] If an existing device is used as the target device to associate with a newly added device, the capabilities of the new device must include the basic capabilities of the existing device, and vice versa. Furthermore, identical capabilities must be complementary in type for the two devices to establish an association. If a capability is the same or not complementary in type in both devices, it cannot be associated. Between the new device and the target device, which must satisfy the association rules and capability attribute matching, their respective basic capabilities must be complementary in type in both devices.

[0036] In one embodiment, when determining whether the capabilities supported by a newly added network device meet the basic capability requirements of the target device, and whether the capabilities supported by the target device meet the basic capability requirements of the newly added network device, a basic capability can be selected from all the basic capabilities of the newly added network device. Based on this basic capability, already added network devices can be screened. Then, if the newly added network device possesses at least two basic capabilities, another basic capability can be selected from the remaining basic capabilities to screen the already screened already added network devices. This process continues until all basic capabilities of the newly added network device have been screened. Finally, based on the basic capabilities of the remaining already added network devices, it is determined whether the newly added network device meets the requirements.

[0037] In one embodiment, if a newly joined device does not need to be associated with other devices, its basic capabilities can be set to empty. If a device's basic capabilities are empty, it is assumed that no device can meet its basic capability requirements. The gateway device will then not associate it with any device.

[0038] The above embodiments will be described in more detail with a specific example. Suppose there is a gateway device, a switch device, and a light device. The switch device is already connected to the gateway and has completed network access. The light device is a newly connected device to the gateway.

[0039] When a new lighting device is added to the network, the gateway device obtains its capability attributes, adds it to the gateway's device list, and matches it with the capability attributes of devices already existing in the list. In other words, the gateway device performs capability attribute matching for both switching devices and lighting devices.

[0040] If a switching device has three capabilities: switching, brightness adjustment, and color adjustment, and all of these capabilities are of the server-side type, then its basic capability is switching. However, a lighting device only supports one capability: switching. And this capability's attribute is client-side. Its basic capability is also switching.

[0041] If the capabilities of the switching device meet the basic capability requirements of the lighting device, and the capabilities of the lighting device meet the basic capability requirements of the switching device, and the same capabilities that both the switching device and the lighting device have are complementary in type, then the gateway device determines that the switching device and the lighting device can be associated and sends an association notification to either of them to establish an association relationship.

[0042] Reference Figure 2 , Figure 2 This is a flowchart illustrating a second embodiment of the device association method of this application. This method is a further extension of the above embodiments and includes, but is not limited to, the following steps.

[0043] S21: Send a network access request to the newly joined device.

[0044] Before a gateway device can acquire the capability attributes of a newly joined device, it needs to connect the new device to its own network in order to provide it with a secure and stable communication channel with other devices.

[0045] S22: In response to receiving network access permission information sent by a new network access device based on a network access request, the new network access device is connected to the network.

[0046] Upon receiving a network access request from the gateway device, a newly added device determines whether it needs to join the network based on its own circumstances. If so, it replies with a network access permission message to the gateway device; otherwise, it replies with a network access denial message.

[0047] After receiving the network access permission message, the gateway device will connect the new network device to its own network.

[0048] In one embodiment, the gateway device may further provide a display interface for displaying association information of devices already connected to the network. The displayed devices include those already connected to the gateway device. This may include both existing devices and newly connected devices, which become existing devices upon joining the network. The association information can be displayed as a list, showing which devices each device has associated with and the basic capabilities of each associated device. Alternatively, it can be displayed as icons, showing which device icons are associated with which other device icons. A combination of both methods is also possible. The display interface includes a basic capability extension switch for adjusting the basic capabilities of the connected devices. In response to adjustments to the basic capabilities of the connected devices, the association relationships of the connected devices are redefined based on the adjusted basic capabilities.

[0049] The equipment is configured with preset basic capabilities at the factory, which are non-adjustable. The basic capability extension switch allows users to select any capability other than the preset basic capabilities as an extended basic capability, thus adjusting the equipment's basic capabilities. The preset basic capabilities can be set to empty.

[0050] Reference Figure 3 , Figure 3This is a schematic diagram of a display interface. After the basic capability extension switch (not shown) is turned on, the basic capability of switch 2—the on / off capability—is in the minimum capability set (equivalent to the basic capabilities described above in this application), and there is no corresponding switch, because the switch capability is its preset basic capability and cannot be adjusted. Brightness adjustment is a capability possessed by switch 2. After the extension switch is turned on, it is added to the minimum capability set, and a corresponding switch is provided for user triggering to adjust whether the brightness adjustment capability is used as an extended basic capability of switch 2. When the extended basic capability switch is on, it will be used as a basic capability; when the extended basic capability switch is off, it will not be used as a basic capability of the device.

[0051] In one embodiment, redetermining the association relationship of already networked devices based on the adjusted basic capabilities includes retaining the association relationship between the already networked devices and their associated devices in response to the fact that the associated devices of the already networked devices can meet the requirements of the adjusted basic capabilities; and / or terminating the association relationship between the already networked devices and their associated devices in response to the fact that the associated devices of the already networked devices cannot meet the requirements of the adjusted basic capabilities.

[0052] Further reference Figure 4 , Figure 4 This is another schematic diagram of the display interface after adjustments to the basic functions. From Figure 3 As can be seen, light #1 and light #2 are listed as associated devices for switch #2. Light #1's capabilities include switching and brightness adjustment, while light #2's capabilities also include switching. If the switch with the minimum capability of brightness adjustment in switch #2 is turned on, then switch #2's basic capabilities at this point are switching and brightness adjustment. The gateway device will then re-determine the association relationship of switch #2 based on the adjusted basic capabilities. Since light #2 does not have brightness adjustment capabilities, the association rule between light #2 and switch #2 is no longer satisfied, and the gateway will remove the association between switch #2 and light #2. Since light #1 has brightness adjustment capabilities, the association rule between light #1 and switch #2 is still satisfied, and therefore the association between light #1 and switch #2 is retained.

[0053] In the above embodiments, the relationship between various devices can be adjusted simply by adjusting the opening and closing of the switch, making the operation convenient and simple.

[0054] In one embodiment, after the target device and the newly connected device establish an association, the communication between them is a direct point-to-point communication, without the need for a gateway device.

[0055] After the gateway device determines that a relationship can be established between the new network access device and the target device, it sends a relationship notification to the target device or the new network access device. Then, the target device or the new network access device can perform the relationship operation according to the normal relationship process.

[0056] In one embodiment, the device's capability attributes can be further combined with the association process, by adding the device's capability attributes to the message sent to the other device to perform the association operation. The combination method can be referred to the description of the following embodiments.

[0057] Reference Figure 5 , Figure 5 This is a flowchart illustrating the third embodiment of the device association method of this application. This method is applied to either an existing network-connected device or a newly network-connected device that serves as the target device, and includes, but is not limited to, the following steps.

[0058] S31: Receive association notifications sent by the gateway device.

[0059] If the gateway detects the existence of a target device, it sends an association notification to either the target device or the newly joined device.

[0060] S32: Send an association request to a new network entrant device or target device that is the other party. The association request includes the capability attributes of the initiator, which include capability type and basic capabilities.

[0061] Capability attributes can further include the capabilities supported by the device.

[0062] S33: Receive feedback information returned by the other party based on the association request. The feedback information includes association termination information or the other party's capability attributes.

[0063] S34: Association binding rules for determining whether the other party's capability attributes meet its requirements based on feedback information.

[0064] S35: In response to the other party's capability attributes meeting the association binding rules required by it, write the other party's information into the association binding information list and send an association binding notification to the other party and / or the gateway device to notify the other party to write the initiator's information into its association binding information list and / or notify the gateway device to record the association binding information of the initiator and the other party.

[0065] Upon receiving an association notification, a newly added device or target device sends an association request to the other party, which includes its own capability attributes. The receiving party, upon receiving the association request, matches its own capability attributes with the newly added capability attributes to determine if the association binding rules are met. These rules are the capability attribute matching requirements mentioned above. If the requirements are met, the receiving party replies with feedback information including its own capability attributes; otherwise, it replies with feedback information including a termination of the association.

[0066] Upon receiving feedback, the sender terminates the association process if it includes information indicating termination of association. If the feedback includes the capabilities of the recipient (the other party), it matches these capabilities with its own to determine if the binding rules are met. If they are met, the recipient's relevant information is added to the association list. The sender also notifies the recipient of successful association. The sender can also send a successful association notification to the gateway device.

[0067] After receiving a message from the sender indicating successful association, the receiver adds the sender's relevant information to its own association list. The receiver can also further send a message confirming successful association to the gateway device.

[0068] At this point, the target device and the newly connected device have successfully established a connection.

[0069] In one embodiment, after the target device and the newly joined device successfully establish an association, they communicate directly point-to-point. Even if the gateway device fails, it will not affect the communication between the already associated devices.

[0070] In this embodiment, if the gateway device has already determined that the device's capability attributes match and conform to the association rules, the capability attributes of the newly joined device and the target device are matched again to determine whether they conform to the association rules. This increases the fault tolerance and accuracy of the association operation and can avoid or reduce association errors caused by certain uncontrollable factors. For example, situations where the capability attributes of the newly joined device or the target device change, and the change information is not promptly transmitted to the gateway device.

[0071] The device association method of this application will be described in more detail below with a specific embodiment. (Refer to...) Figure 6 , Figure 6 This is a flowchart illustrating a specific embodiment of the device association method of this application. In this actual situation, there is a switch device, a gateway device, and a light device. The switch device is already connected to the gateway device. The gateway device and the switch device are already in the same network.

[0072] S41: The gateway device requests the light device to join the network.

[0073] S42: The lighting device is allowed to be added to the network of the gateway device.

[0074] S43: The gateway device reads the capability attributes of the light device.

[0075] S44: Create a virtual device for the light device in the gateway device and write the light's capability attributes to the gateway device's device list.

[0076] S45: The gateway device retrieves existing devices from the device list and checks whether the device has the capabilities that match the association rules. The association rules are the capability attribute matching requirements mentioned above.

[0077] The gateway device detects whether the switch device has capabilities that are complementary to the capabilities of the lighting device; the gateway device detects whether the minimum set of capabilities (basic capabilities) required by the switch device exists in the capabilities of the lighting device; the gateway device detects whether the minimum set of capabilities (basic capabilities) required by the lighting device exists in the capabilities of the switch device.

[0078] S46: If the above rules are met, the gateway device will notify the switch device to initiate an association with the lamp device (or it can notify the lamp device, and subsequent steps can be adjusted accordingly, which is not shown here).

[0079] S47: The switching device initiates an association request to the lighting device, and the association request includes information such as the capability attributes of the switching device.

[0080] S48: After receiving the data sent by the switch device, the lighting device checks whether the capability attribute matches its own capability attribute and whether its own capabilities include the minimum capability set (basic capabilities) of the switch device. If not, it sends a termination of association request message to the lighting device.

[0081] S49: If the data detected by the lighting device from the switching device fully conforms to the binding rules, then send information such as the capability attributes of the lighting device to the switching device.

[0082] S50: After receiving the data from the lighting device, the switching device checks whether the capability attributes of the lighting device match the capability attributes of this device and comply with the binding rules. If they do, the switching device writes the capability attributes and other relevant information of the lighting device to the associated device list.

[0083] S51: And the switch equipment notification light device has completed the association operation on the switch equipment side.

[0084] S52: After receiving the association completion information sent by the switch device, the lighting device writes the relevant information such as the capability attributes of the switch device into the associated device list of the lighting device.

[0085] S53: The light device notifies the gateway that the device association is complete.

[0086] Subsequent communication between two already associated devices no longer goes through the server; it's direct point-to-point communication. Even if the server is unavailable, it won't affect communication between the already associated devices.

[0087] like Figure 7 As shown, Figure 7 This is a schematic diagram of the structure of the first embodiment of the electronic device of this application.

[0088] The electronic device includes a processor 110 and a memory 120. This electronic device can be a gateway device, such as a router, a switch, a firewall, an access server, a gateway server, etc.

[0089] Processor 110 controls the operation of electronic devices. Processor 110 may also be referred to as a CPU (Central Processing Unit). Processor 110 may be an integrated circuit chip with signal sequence processing capabilities. Processor 110 may also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

[0090] The memory 120 stores the instructions and program data required for the processor 110 to operate.

[0091] The processor 110 is used to execute instructions to implement the methods provided in any of the embodiments and possible combinations of the device association methods described above in this application.

[0092] like Figure 8 As shown, Figure 8 This is a schematic diagram of the structure of an embodiment of the computer program product of this application.

[0093] One embodiment of the computer program product of this application includes a memory 210, which stores program data that, when executed, implements the methods provided in any embodiment and possible combinations of the device association methods of this application.

[0094] The memory 210 may include a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, or other media that can store program instructions. Alternatively, it may be a server that stores the program instructions, which can send the stored program instructions to other devices for execution or execute the stored program instructions itself.

[0095] In summary, after a device joins the network, the gateway device obtains its capability attributes and directly associates the newly joined device with the existing device based on the device's basic capabilities and capability type in the capability attributes. Compared with traditional methods, this method no longer requires preset scenarios or relies on scenario information for matching operations, making the association operation simple, convenient, fast, and efficient, thus improving the efficiency of device association operations.

[0096] In the several embodiments provided in this application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of modules or units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

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

[0098] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

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

[0100] The above description is merely an embodiment of this application and does 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 protection scope of this application.

Claims

1. A device association method, characterized by, The application is applied to a gateway device, the gateway device accesses at least one networked device, and the device association method comprises the following steps: acquiring a capability attribute of a new networked device, the capability attribute comprising a basic capability and a capability type; searching for a target device from the networked devices, the capability attribute of the target device matching the capability attribute of the new networked device; based on the target device searched, establishing an association relationship between the new networked device and the target device.

2. The device association method of claim 1, wherein, The capability attribute of the target device matches the capability attribute of the new networked device, comprising: the basic capability of the new networked device is the same as the basic capability of the target device; the capability type of the same capability in the target device is complementary to the capability type in the new networked device.

3. The device association method of claim 1, wherein, The capability attribute further comprises a supported capability, and the capability attribute of the target device matches the capability attribute of the new networked device, comprising: the supported capability of the new networked device meets the requirement of the basic capability of the target device; the supported capability of the target device meets the requirement of the basic capability of the new networked device; the capability type of the same capability in the target device is complementary to the capability type in the new networked device.

4. The device association method of claim 1, wherein, Before the step of acquiring the capability attribute of the new networked device, comprising: sending a network access request to the new networked device; in response to receiving network access permission information sent by the new networked device based on the network access request, accessing the network with the new networked device.

5. The device association method of claim 1, wherein, The gateway device is further provided with a display interface for displaying association information of the networked device, and the display interface comprises a basic capability expansion switch for adjusting the basic capability of the networked device.

6. The device association method of claim 5, wherein, The device association method further comprises: in response to the basic capability of the networked device being adjusted, re-determining the association relationship of the networked device based on the adjusted basic capability.

7. The device association method of claim 6, wherein, The re-determining the association relationship of the networked device based on the adjusted basic capability, comprising: in response to the associated device of the networked device being able to meet the requirement of the adjusted basic capability, retaining the association relationship between the networked device and the associated device; and / or in response to the associated device of the networked device being unable to meet the requirement of the adjusted basic capability, canceling the association relationship between the networked device and the associated device.

8. The device association method of claim 1, wherein, After the step of establishing the association relationship between the new networked device and the target device, the communication mode between the target device and the new networked device is point-to-point direct communication.

9. An electronic device, comprising: The application comprises a memory and a processor, the memory is used for storing program data, and the program data can be executed by the processor to realize the device association method in any one of claims 1-8.

10. A computer program product, characterised in that, The program data stored can be executed by the processor to realize the device association method in any one of claims 1-8.

Images