WO2023123400A1

WO2023123400A1 - Wireless communication methods and devices

Info

Publication number: WO2023123400A1
Application number: PCT/CN2021/143806
Authority: WO
Inventors: 茹昭
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-12-31
Filing date: 2021-12-31
Publication date: 2023-07-06

Abstract

Provided in the embodiments of the present application are wireless communication methods and devices, which may solve the problem of complicated setting in a permission handover process of a smart home system, and realizes, by providing a Copy Settings From Fabric command, that a setting device in a first Fabric network conveniently copies a functional unit which has been set by a second Fabric network. A wireless communication method comprises: a terminal device receives first information sent by a first setting device, wherein the first setting device is a setting device in a first Fabric network, the first information is used for generating private setting information of the first Fabric network for at least one device, the private setting information of the first Fabric network for the at least one device is obtained by copying private setting information of a second Fabric network for the at least one device, and the at least one device comprises the terminal device.

Description

Method and device for wireless communication

technical field

The embodiments of the present application relate to the field of the Internet of Things, and more specifically, to a method and device for wireless communication.

Background technique

In the cross-woven network (Fabric) permission sharing scenario, after the configuration device with administrator rights in A Fabric shares the smart home system with the configuration device in B Fabric, if the configuration device in B Fabric still wants to use the configuration device in A Fabric To configure the configuration that has been done by the device, you need to perform cumbersome operations, that is, to view each configuration made by the configuration device in A Fabric and re-do your own configuration according to the configuration of the configuration device in A Fabric. There are many devices in the smart home system, especially when the whole house is handed over, new users (that is, users in B Fabric) need to spend a lot of time and energy, which affects the user experience.

Contents of the invention

The embodiment of the present application provides a wireless communication method and device, which can solve the problem of cumbersome configuration in the smart home system authority transfer process, and realize the configuration in the first fabric network by adding the command CopySettingsFromFabric The device conveniently duplicates the configured functional units of the second weave network.

In a first aspect, a wireless communication method is provided, and the method includes:

The terminal device receives the first information sent by the first configuration device;

Wherein, the first configuration device is a configuration device in the first weave network, and the first information is used to generate private configuration information of the first weave network for at least one device, and the first weave network is for the private configuration information of the at least one device. The configuration information is obtained by duplicating private configuration information for the at least one device in the second woven network, where the at least one device includes the terminal device.

In a second aspect, a wireless communication method is provided, and the method includes:

the first configuration device sends first information to at least one device;

Wherein, the first configuration device is a configuration device in the first weave network, and the first information is used to generate private configuration information of the first weave network for at least one device, and the first weave network is for the private configuration information of the at least one device. The configuration information is obtained by duplicating the private configuration information for the at least one device in the second woven network.

In a third aspect, a terminal device is provided, configured to execute the method in the first aspect above.

Specifically, the terminal device includes a functional module for executing the method in the first aspect above.

In a fourth aspect, a configuration device is provided, configured to execute the method performed by the first configuration device in the second aspect above.

Specifically, the configuration device includes a functional module for executing the method performed by the first configuration device in the second aspect above.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to execute the method in the first aspect above.

In a sixth aspect, a configuration device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect above.

In a seventh aspect, an apparatus is provided for implementing the method in any one of the first aspect to the second aspect above.

Specifically, the device includes: a processor, configured to invoke and run a computer program from the memory, so that the device installed with the device executes the method in any one of the above first to second aspects.

In an eighth aspect, there is provided a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method in any one of the above-mentioned first aspect to the second aspect.

In a ninth aspect, a computer program product is provided, including computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above first to second aspects.

In a tenth aspect, a computer program is provided, which, when running on a computer, causes the computer to execute the method in any one of the above first to second aspects.

Through the above technical solution, the configuration device in the first woven network can instruct to copy the private configuration information for at least one device in the second woven network, thereby realizing the purpose of copying the private configuration information for at least one device in the second woven network. That is to say, it can solve the problem of cumbersome configuration in the smart home system authority transfer process. By adding the copy configuration command from the weaving network, the configuration device in the first weaving network can conveniently copy the configured functional units of the second weaving network.

Description of drawings

Fig. 1 is a flow chart of rights sharing provided by this application.

Fig. 2 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

Fig. 3 is a schematic interaction flowchart of a wireless communication method provided according to an embodiment of the present application.

Fig. 4 is a schematic interactive flowchart for generating a node identifier mapping table according to an embodiment of the present application.

FIG. 5 to FIG. 7 are schematic interaction flowcharts of copying a private configuration of another weaving network by one weaving network according to an embodiment of the present application.

Fig. 8 shows a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 9 shows a schematic block diagram of a configuration terminal according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.

Fig. 12 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. With regard to the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

The terms used in the embodiments of the present application are only used to explain specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a non-exclusive inclusion.

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

In this embodiment of the application, "predefined" or "preconfigured" can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The application does not limit its specific implementation. For example, pre-defined may refer to defined in the protocol.

In this embodiment of the application, the "protocol" may refer to a standard protocol in the field of the Internet of Things, which is not limited in this application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific examples. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the protection scope of the embodiments of the present application. The embodiment of the present application includes at least part of the following content.

In the field of the Internet of Things, different manufacturers can build different fabrics, and can control access to one or more smart devices (such as smart light bulbs, smart refrigerators, etc.) Access control to control light bulbs on or off etc. A user in a Fabric can share the smart home system with users in other Fabrics through a configuration device with administrator rights. For example, a configuration device with administrator rights in A Fabric can share the smart home system with a configuration device in B Fabric Afterwards, if the configuration device in Fabric B still wants to use the configuration already done by the configuration device in Fabric A, you need to perform cumbersome operations, that is, check each configuration made by the configuration device in Fabric A and follow the configuration in Fabric A. Configure the configuration of the device and redo your own configuration. There are many devices in the smart home system, especially when the whole house is handed over, new users (that is, users in B Fabric) need to spend a lot of time and energy, which affects the user experience.

Specifically, the configuration device can be a commissioner, which can be used to configure security credentials, network access information, access control list (Access Control List, ACL), binding, proxy, etc. of one or more devices. The control device is the controller (controller), which can control and read the state of one or more devices such as on and off. Usually the role of a terminal device (such as a mobile phone) includes both a commissioner and a controller.

For example, user A configures a smart home system using A-APP (A application) on his mobile phone. In this case, A-APP is an administrator (Admin), commissioner (Commissioner) and controller (Controller). User A transfers or shares this smart home system to user B, and user A uses the B-APP on user B's mobile phone as the second Admin and Controller of this smart home system. The following is the configuration process of smart light bulbs as an example. As shown in Figure 1, A-APP can specifically add B-APP as the administrator of smart light bulbs through S1-S16.

S1. User A triggers the configuration mode of turning on the smart light bulb;

S2. A-APP generates a configuration token OT, wherein the activation token (Onboarding Token, OT) may include a Discovery Capabilities Mask, a randomly generated configuration code (SetupCode), and a discriminator (Discriminator);

S3. A-APP sends an instruction to turn on the configuration to the smart light bulb, and the instruction carries OT;

S4. After the smart light bulb receives the instruction, it sends a confirmation feedback to the A-APP;

S5. The smart light bulb enters the configuration discovery mode, such as public domain name system service discovery (Domain Name System Service Discovery DNS-SD);

S6. A-APP shares OT with B-APP through mail, voice and other out-of-band methods;

S7.B-APP queries DNS-SD;

S8.B-APP discovers the smart light bulb and connects to the resolved Internet Protocol (Internet Protocol, IP) address/port;

S9. Use OT to establish a secure connection between the smart light bulb and the B-APP;

S10.B-APP certified smart bulb certification statement (Certification Declaration, CD);

S11. If the B Fabric has not been used in the home network, the B-APP creates a Fabric ID for the home network.

S12. The smart light bulb obtains the operation key;

S13. The smart bulb sends a device certificate request to the B-APP, such as a certificate signing request for the smart bulb (Certificate Signing Request of bulb, CSR.bulb);

S14.B-APP sends CSR.bulb and Fabric ID to B Fabric's certification center (Certificate Authority, CA) to request a device certificate;

S15. After the CA authentication of B Fabric, a smart light bulb operation certificate (B.OC.bulb) is generated and returned to B-APP;

S16.B-APP configures B.OC.bulb and access control authority ACL.Bulb.B.APP to the smart bulb.

After user A shares each device in the smart home system with user B according to the above configuration process, user B can configure the smart home system to meet his own needs. In addition, user B can also use the Remove Fabric command to delete all permissions and configurations of user A in the smart home system.

The above configuration mainly uses the Node Operation Credentials Cluster of the equipment in the smart home system. For example, the B-APP in B Fabric allows user B to obtain administrator authority through the Node Operation Credentials Function Unit; among them, Node Operation Credentials Cluster The credential functional unit may correspond to some or all of the functional units of the device, specifically, these functional units may be operated through the node operation credential. The attributes contained in the node operation credential functional unit may be shown in Table 1.

Table 1

Wherein, in Table 1, desc means refer to the detailed description part, and all means that all values are allowed in the numerical data type. Specifically, the node operation certificate, weave network, supported weave network, configured weave network, trust root certificate, current weave network index, etc., and the corresponding type, constraint, quality, accessibility, default value and consistency can be It is regarded as the attribute contained in the functional unit of the node operation credential.

In some embodiments, the Fabric description structure list corresponding to the woven network may be shown in Table 2 below.

Table 2

Wherein, in Table 2, fabric-idx represents a data type of a predefined weaving network index. vendor-id indicates a predefined vendor ID. The fabric-id represents a predefined fabric network identifier (Identity, ID). node-id indicates a predefined device node ID. Specifically, in Table 2, weaving network index, trust root public key, vendor identification, weaving network ID, node ID, label, etc., and the corresponding types, constraints, quality, accessibility, default values, and consistency can be seen in It is the attribute field included in the Fabric description structure list corresponding to the weaving network.

In some embodiments, the commands included in the node operation credential functional unit may be shown in Table 3 below.

table 3

Among them, A in the Accessibility column in Table 3 indicates that administrator (Admin) authority is required. The client can be the configuration device side, and the server can be the terminal device side, that is, ID 0 in Table 3 can be that the configuration device sends an authentication request to the terminal device, and others are similar, so I won't repeat them here.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, Wireless Fidelity (Wireless Fidelity, WiFi), Bluetooth Low Energy (Bluetooh Low Energy, BLE), Wireless Local Area Networks (Wireless Local Area Networks, WLAN), Mobile communication network, near field communication network (Near Field Communication, NFC), ultra wideband (Ultra Broadband, UWB) network, infrared network, microwave communication network, millimeter wave communication network, free space optical communication network. The embodiment of the present application can also be applied to device-to-device (Device to Device, D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle-to-vehicle (Vehicle to Vehicle, V2V) communication, or vehicle networking (Vehicle to everything, V2X) communication, etc.

Fig. 2 is a schematic diagram of a wireless communication system applied in an embodiment of the present application. As shown in FIG. 2 , the wireless communication system 100 may include: a first configuration device 110 , a second configuration device 120 and a terminal device 130 .

In some embodiments, the first configuration device 110 and/or the second configuration device 120 may be a terminal device, such as a mobile phone, a tablet computer, a computer, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, smart wearable devices, etc.

In some embodiments, the first configuration device 110 and/or the second configuration device 120 may also be a server.

In some embodiments, the first configuration device 110 and the second configuration device 120 belong to different Fabrics.

In some embodiments, the second configuration device 120 and the terminal device 130 belong to the same Fabric, and the second configuration device 120 has access rights (such as administrator rights) to the terminal device 130, through which the second configuration device 120 can The terminal device 130 is accessed and controlled.

In some embodiments, the first configuration device 110 and the second configuration device 120 can be connected in a wired or wireless manner, the second configuration device 120 can share the access right to the terminal device 130 with the first configuration device 110, and the second configuration device 120 can A configuration device 110 may copy the private configuration information of the second configuration device 120 for the terminal device 130 .

In some embodiments, the terminal device 130 is at least wired or wirelessly connected to the second configuration device 120, the terminal device 130 can be any of the above-mentioned terminal devices, moreover, the terminal device 130 can be a smart home product, such as Smart refrigerators, smart light bulbs, smart washing machines, smart TVs, smart wearables, and more.

In some embodiments, wearable devices can also be referred to as wearable terminal devices, which is a general term for intelligently designing daily wear and developing wearable devices by applying wearable technology, such as glasses, gloves, watches, clothing and shoes. wait. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable terminal devices include full-featured, large-sized, complete or partial functions without relying on smartphones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smartphones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In some embodiments, the terminal device 130 can also be connected to the first configuration device 110 with access rights to the terminal device 130 in a wired or wireless manner, and the first configuration device 110 can access the terminal device 130 and control.

In some embodiments, the number of terminal devices 130 may be one or more, which is not limited in this application.

The technical scheme of the present application is described in detail below through specific examples.

Fig. 3 is a schematic interaction flowchart of a wireless communication method 200 provided in an embodiment of the present application. As shown in Fig. 3, the wireless communication method 200 may at least include the following content:

S210, the first configuration device sends first information to at least one device; wherein, the first configuration device is a configuration device in the first weave network, and the first information is used to generate the private information of the first weave network for at least one device Configuration information, the private configuration information for the at least one device in the first woven network is obtained by copying the private configuration information for the at least one device in the second woven network;

S220, the terminal device receives the first information sent by the first configuration device; wherein the at least one device includes the terminal device.

In this embodiment of the present application, the terminal device may be any one of the at least one device. In addition, for the type of the at least one device, reference may be made to the relevant description about the terminal device above, which will not be repeated here.

In some embodiments, the first information may include an indication field, where the indication field is used to indicate to copy the private configuration information for the at least one device in the second woven network.

In some embodiments, the terminal device adds the private configuration information for the terminal device in the second weave network to the configuration information for the terminal device in the first weave network according to the first information. Or, the terminal device copies the private configuration information for the terminal device in the second woven network to the configuration information for the terminal device in the first woven network according to the first information.

In some embodiments, the terminal device determines that the first configuration device has administrator authority.

It should be noted that, for a terminal device, private configuration information for the terminal device is configured in the second woven network, and some public configuration information of the terminal device may also be included in the second woven network, where the first configuration device has the After obtaining the administrator authority of the terminal device, the first configuration device can obtain the public configuration information of the terminal device. And, after the first configuration device has the administrator authority of the terminal device, the first configuration device can obtain the private configuration information of the terminal device by sending the first information. It should be understood that other devices in the at least one device are also similar, and details are not described herein again.

In some embodiments, the first configuration device may send the first information to the at least one device in a multicast or broadcast manner. Of course, the first configuration device may also send the first information to the at least one device in a unicast manner. This application is not limited to this.

In some embodiments, the first information is a Copy Settings From Fabric (CopySettingsFromFabric) command. That is, the first configuration device may instruct to copy private configuration information for at least one device in the second fabric network by using a fabric network copy configuration (CopySettingsFromFabric) command. It can solve the problem of cumbersome configuration in the process of smart home system authority transfer. By adding the configuration command copied by the weaving network, the configuration device in the first weaving network can conveniently copy the configured functional units of the second weaving network.

In some embodiments, the at least one device may be part or all of the devices in the smart home system. Specifically, for example, the integrator uses the second configuration device to configure at least one device to the second woven network, and also configures functional units such as ACL, group, scene, binding, proxy, node operation certificate, OTA, etc., that is, for at least one The devices in the device can be configured with one or more of ACL, group, scenario, binding, proxy, node operation certificate, NOC, OTA, and the functional units configured by different devices can be the same or different. After the integrator debugs the smart home system, the smart home system is handed over to the homeowner, and the homeowner can send the command CopySettingsFromFabric to the at least one device through the first configuration device to copy the configuration in the second weave network. Private configuration information for at least one device.

Specifically, for example, a CopySettingsFromFabric command is added to the node operation credential functional unit of the terminal device, as shown in Table 4.

Table 4

Specifically, for example, for a terminal device, the functional unit "ACL" may include the ACL information corresponding to the terminal device, specifically, the ACL of the terminal device is configured in the second network, for example, the terminal device includes ACL 1 and ACL 3, at this time, the functional unit "ACL" can contain information about ACL 1 and ACL 3.

Specifically, for example, for a terminal device, the functional unit "group" may contain information about the group to which the terminal device belongs, specifically, the terminal device is grouped in the second organized network, for example, the terminal device belongs to group 1 and group 3. At this time, the functional unit "group" may contain related information of group 1 and group 3.

Specifically, for example, for a terminal device, the functional unit "scenario" may include the scene information applicable to the terminal device, specifically, the applicable scene of the terminal device is configured in the second organization network, for example, the terminal device may be applicable to Scenario 1 and Scenario 2. In this case, the functional unit "scene" may include relevant information of Scenario 1 and Scenario 2.

Specifically, for example, for a terminal device, the functional unit "binding" may include binding information corresponding to the terminal device, specifically, the terminal device is configured to establish a binding relationship with one or more other devices in the second network For example, the terminal device has established a binding relationship with the device 1 and the device 2. At this time, the functional unit "binding" may include information about the device 1 and the device 2.

Specifically, for example, for a terminal device, the functional unit "proxy" may include proxy information corresponding to the terminal device, specifically, the terminal device is configured in the second network as a proxy device for one or more other devices, For example, the terminal device may be a proxy device for Device 1 and Device 3 , and in this case, the functional unit "Proxy" may contain information about Device 1 and Device 3 .

Specifically, for example, for a terminal device, the functional unit "node operation credential" may include the node operation credential information corresponding to the terminal device, specifically, the node operation credential corresponding to the terminal device is configured in the second organization network, for example, The terminal device may correspond to the node operation credential 1 and the node operation credential 3. At this time, the functional unit "node operation credential" may include information about the node operation credential 1 and the node operation credential 3.

Specifically, for example, for a terminal device, the functional unit "OTA" may contain the OTA information corresponding to the terminal device, specifically, the OTA corresponding to the terminal device is configured in the second organization network, for example, the terminal device may correspond to the OTA 1 and OTA 3, at this time, the functional unit "OTA" can contain information about OTA 1 and OTA 3.

In this embodiment of the application, "identification" may also be expressed as "index", which is not limited in this application.

In some embodiments, the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second weave network includes the identifier of the second weave network. That is, the functional unit including the identifier of the second weaving network in the attribute or attribute field may be regarded as a private functional unit of the second weaving network. For example, FabricA:{FabricA,NOC},{FabricA,ACL},{FabricA,Group},{FabricA,Binding},{FabricA,Proxy}, that is, the node operation certificate (Node Operational Certificate, NOC), access control list ( The attributes or attribute fields of functional units such as Access Control Lists (ACL), Group (Group), Binding (Binding) and Proxy (Proxy) include the identification information of FabricA, and NOC, ACL, Group, Binding and Proxy can be regarded as It is a private functional unit of FabricA.

It should be noted that the Node Operational Certificate (NOC) can also be called Node Operational Credentials, which is not limited in this application.

In some embodiments, the private configuration information for the at least one device in the second woven network includes but is not limited to at least one of the following information: ACL information, group information, context information, binding information, proxy information, node operation Credentials (Node Operational Credentials) information, Over-the-Air (OTA) information.

In some embodiments, the first information includes weaving network identification information, wherein the weaving network identification information is used to indicate the second weaving network. That is, the first information may include identification information of the second woven network.

In some embodiments, the first information further includes a node identification mapping table; wherein, the node identification mapping table is used to indicate that the node identification information of a device among the M devices in the first weaving network is different from that in the second weaving network The mapping relationship between node identification information in the network, the M devices include the at least one device, or the M devices include the terminal device, or the M devices include the at least one device and the at least one device associated devices, or, the M devices include the terminal device and devices associated with the terminal device, and M is a positive integer.

It should be noted that, among the M devices, the device associated with the terminal device may be: a device associated with the terminal device through one or more functional units. It should be understood that other devices in the at least one device are similar to the terminal device, and reference may be made to relevant descriptions of the terminal device, and details are not repeated here.

For example, the M devices include: the terminal device and one or more devices associated with the terminal device through functional units. For another example, the M devices include: the terminal device and one or more devices associated with the terminal device through a functional unit "group". For another example, the M devices include: the terminal device and one or more devices associated with the terminal device through a functional unit "proxy". For another example, the M devices include: the terminal device and one or more devices associated with the terminal device through a functional unit "scene". Other functional units are also similar, and will not be repeated here.

In some embodiments, the first configuration device obtains node identification information of the at least one device and devices associated with the at least one device in the first weave network and node identification information in the second weave network; and The first configuration device generates a node identification mapping table according to node identification information of the at least one device and devices associated with the at least one device in the first woven network and node identification information in the second woven network. Specifically, the node identifier mapping table carried in the first information may be a complete list generated by the first configuration device, and the node identifier mapping table carried in the first information may also be a complete list generated by the first configuration device. The part of the extracted node ID mapping table is not limited in this application.

In some embodiments, the node identifier mapping table may be configured in the terminal device in advance through other means, and then the first information only needs to include the woven network identifier information.

In some embodiments, the type information corresponding to the node identifier mapping table is a node identifier structure list, and the M node identifier structures included in the node identifier structure list respectively correspond to the M devices.

In some embodiments, the node identification structure corresponding to the terminal device in the node identification structure list (List[NodeIdStruct]) includes target node identification information (TargetNodeID) and current node identification information (CurrentNodeID), wherein the target node identification information is the node identification information of the terminal device in the second woven network, and the current node identification information is the node identification information of the terminal device in the first woven network.

In some embodiments, the node identification structure corresponding to the terminal device in the node identification structure list further includes a target fabric ID (TargetFabricID) and a current fabric ID (CurrentFabricID), wherein the target fabric ID is the second fabric ID An identifier of a network, where the current weaving network identifier is the identifier of the first weaving network.

Specifically, for example, in a case where the first information includes woven network identification information and a node identification mapping table, the parameters contained in the first information may be as shown in Table 5 or Table 6.

table 5

Wherein, in Table 5, FabricIndex indicates the Fabric network to which the group session belongs, that is, FabricIndex may be index information of the second fabric network. fabric-idx indicates the data type of the weaving network index agreed by the protocol. all means that all values are allowed in the numeric data type. List[NodeIdStruct] is a list of NodeIdStruct types.

Table 6

Wherein, in Table 6, FabricID indicates the Fabric network to which the group session belongs, that is, the FabricID may be an identifier of the second fabric network. fabric-id indicates the data type of the weaving network index agreed by the protocol. all means that all values are allowed in the numeric data type. List[NodeIdStruct] is a list of NodeIdStruct types.

It should be noted that there is a fixed mapping relationship between FabricIndex and FabricID in the device, which can be converted through the mapping relationship.

Specifically, for example, in the case that the node identification structure includes target node identification information (TargetNodeID), current node identification information (CurrentNodeID), target weaving network identification information (TargetFabricID) and current weaving network identification information (CurrentFabricID), the node identification structure contains The parameters can be shown in Table 7.

Table 7

In some embodiments, when the first information includes the woven network identification information and the node identification mapping table, or, when the first information includes the woven network identification information and the node is pre-configured at the terminal device In the case of identifying a mapping table, the terminal device adds, according to the first information, the configuration information for the terminal device of the first weaving network corresponding to all private functional units corresponding to the terminal device and belonging to the second weaving network. Private configuration information.

In some embodiments, when the first information includes the woven network identification information and the node identification mapping table, or, when the first information includes the woven network identification information and the node is pre-configured at the terminal device In the case of identifying a mapping table, the terminal device can copy the private configuration information for the terminal device in the second weaving network to the first weaving network in the following manner:

The terminal device acquires all private functional units corresponding to the terminal device that belong to the second weaving network according to the first information;

The terminal device adds all private functional units belonging to the second weaving network to the functional units of the first weaving network;

For each added private function unit, the terminal device replaces its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.

Specifically, for example, after receiving the first information, the terminal device obtains all private functional units corresponding to the terminal device that belong to the second woven network by searching for the identifier of the second woven network.

In some embodiments, the attributes or attribute fields of all private functional units include the identifier of the second weaving network.

In some embodiments, the all private functional units include but are not limited to at least one of the following functional units:

ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.

In some embodiments, the first information further includes a functional unit list; wherein the functional unit list is used to indicate at least one functional unit that needs to be copied. That is, in this case, the first information includes the woven network identification information, the node identification mapping table and the functional unit list, which may be specifically shown in Table 8 or Table 9. Alternatively, the first information includes the woven network identification information and the functional unit list, and the terminal device is pre-configured with the node identification mapping table.

Table 8

Wherein, in Table 8, FabricIndex indicates the Fabric network to which the group session belongs, that is, FabricIndex may be an identifier of the second fabric network. fabric-idx indicates the data type of the weaving network index agreed by the protocol. cluster-id indicates the data type of the functional unit index agreed in the protocol. List[cluster-id] is a list of cluster-id types. all means that all values are allowed in the numeric data type. List[NodeIdStruct] is a list of NodeIdStruct types.

Table 9

Wherein, in Table 9, FabricID indicates the Fabric network to which the group session belongs, that is, the FabricID may be an identifier of the second fabric network. fabric-id indicates the data type of the weaving network index agreed by the protocol. cluster-id indicates the data type of the functional unit index agreed in the protocol. List[cluster-id] is a list of cluster-id types. all means that all values are allowed in the numeric data type. List[NodeIdStruct] is a list of NodeIdStruct types.

In some embodiments, the consistency corresponding to the "functional unit list" in the above-mentioned Table 8 and Table 9 can also be set to "optional". The functional units specified by the unit list; where the functional unit list is not included in the above Tables 8 and 9, all private functional units are copied.

In some embodiments, the functional units indicated by the functional unit list include but are not limited to at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential function Unit, OTA functional unit.

In some embodiments, the type information corresponding to the functional unit list is a functional unit identification list, wherein the functional unit identification list includes identification information of the at least one functional unit.

In some embodiments, when the first information includes the woven network identification information, the node identification mapping table, and the functional unit list, or, when the first information includes the woven network identification information and the functional unit list , and the terminal device is pre-configured with the node identifier mapping table, the terminal device adds the corresponding attribute of the terminal device to the configuration information of the terminal device in the first weaving network according to the first information. The private configuration information corresponding to the functional units indicated by the functional unit list among all private functional units of the second woven network.

In some embodiments, when the first information includes the woven network identification information, the node identification mapping table, and the functional unit list, or, when the first information includes the woven network identification information and the functional unit list , and the terminal device is pre-configured with the node identification mapping table, the terminal device can copy the private configuration information for the terminal device in the second weaving network to the first weaving network in the following manner:

The terminal device acquires the functional units indicated by the functional unit list among all private functional units belonging to the second weaving network corresponding to the terminal device according to the first information;

The terminal device adds the functional units indicated by the list of functional units belonging to the second weaving network to the functional units of the first weaving network;

Specifically, for example, after receiving the first information, the terminal device obtains the functional unit indicated by the functional unit list belonging to the second woven network corresponding to the terminal device by searching for the identifier of the second woven network .

In some embodiments, the first information further includes a target list; where the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or , the target list is used to indicate that at least one functional unit corresponding to the device type needs to be copied. That is, in this case, the first information includes the woven network identifier, the node identifier mapping table, and the target list, which may be specifically shown in Table 10 or 11. Alternatively, the first information includes the woven network identifier and the target list, and the terminal device is pre-configured with the node identifier mapping table.

Table 10

Table 11

In some embodiments, the consistency corresponding to the "target list" in the above-mentioned Table 10 and Table 11 can also be set to "optional". functional units; in cases where the target list is not included in Tables 10 and 11 above, all private functional units are copied.

Specifically, the TargetStruct may be as shown in Table 12.

Table 12

Wherein, Endpoint-no represents the data type of the endpoint number stipulated in the protocol. devtype-id indicates the data type of the device type index agreed by the protocol.

In some embodiments, the functional units indicated by the target list include but are not limited to at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit , OTA functional unit.

In some embodiments, the type information corresponding to the target list is a target structure list; wherein,

In the case where the target list is used to indicate the at least one functional unit that needs to be copied, at least one target structure included in the target structure list corresponds to at least one functional unit respectively, and one target structure in the target structure list includes at least the corresponding Identification information of the functional unit; or,

When the target list is used to indicate that the functional unit corresponding to the at least one endpoint needs to be copied, at least one target structure included in the target structure list corresponds to at least one endpoint respectively, and one target structure in the target structure list includes at least the endpoint number of the corresponding endpoint; or,

In the case where the target list is used to indicate that the functional unit corresponding to the at least one device type needs to be copied, at least one target structure included in the target structure list corresponds to the at least one device type, and one target structure in the target structure list At least including the identification information of the corresponding device type.

In some embodiments, when the first information includes the woven network identification information, the node identification mapping table, and the target list, or, when the first information includes the woven network identification information and the target list, and If the node identifier mapping table is pre-configured at the terminal device, the terminal device adds the corresponding information belonging to the second Private configuration information corresponding to the functional units indicated by the target list among all private functional units of the weaving network.

In some embodiments, when the first information includes the woven network identification information, the node identification mapping table, and the target list, or, when the first information includes the woven network identification information and the target list, and In the case where the node identifier mapping table is pre-configured at the terminal device, the terminal device may copy the private configuration information for the terminal device in the second weaving network to the first weaving network in the following manner:

The terminal device acquires the functional units indicated by the target list among all private functional units belonging to the second weaving network corresponding to the terminal device according to the first information;

The terminal device adds the functional units indicated by the target list belonging to the second weaving network to the functional units of the first weaving network;

In some embodiments, the first configuration device acquires private configuration information for the at least one device in the second weave network.

Specifically, for example, after receiving the first information, the terminal device obtains the functional unit indicated by the target list belonging to the second weaving network corresponding to the terminal device by searching for the identifier of the second weaving network.

For example, the first fabric network can be FabricB, the second fabric network can be FabricA, the first configuration device can be the Admin2 APP controlled by the house owner, and the second configuration device can be the Admin1 APP controlled by the integrator. The Admin1 APP used by the integrator is the original device administrator, which adds the homeowner's Admin2 APP as the administrator of the devices in the smart home system, and hands over the devices in the smart home system to the homeowner's Admin2 APP. As shown in Figure 4, the Admin2 APP can obtain administrator authority and generate a node identification mapping table (NodeIdMap) through at least some of the steps in the following S1-1 to S1-6.

S1-1, the integrator uses the Admin1 APP to configure the terminal devices in the room (such as smart light bulbs), configure the terminal devices to FabricA, and configure device-related NOC, binding, group, ACL, proxy, etc. Optionally, related settings of the terminal device after configuration are: FabricA:{FabricA,NOC1},{FabricA,ACL1},{FabricA,Group1},{FabricA,Binding1},{FabricA,Proxy1}.

S1-2. After the integrator debugs the terminal equipment, he hands over the terminal equipment to the homeowner. The integrator uses the Admin1 APP to open the multi-fabric network (Multi-Fabric) configuration window of the terminal equipment.

S1-3, the homeowner uses the Admin2 APP to configure the terminal device, configure the terminal device to FabricB, and configure the device certificate NOC of the terminal device on FabricB. Optionally, the relevant settings of the terminal device after configuration are: FabricA:{FabricA,NOC1},{FabricA,ACL1},{FabricA,Group1},{FabricA,Binding1},{FabricA,Proxy1}; FabricB:{FabricB,Proxy1}; NOC2}.

S1-4. The homeowner uses the Admin2 APP to send instructions to the terminal device to view the Fabrics attribute of the node operation credential functional unit, read the node ID (Node ID) of the terminal device in FabricA, and obtain NodeID_A.

S1-5, the homeowner uses Admin2 APP to read the Node ID of the terminal device in FabricB, or check, the homeowner uses Admin2 APP to find the Node ID of the terminal device in FabricB saved in the previous configuration, and obtains NodeID_B.

S1-6, the homeowner uses the Admin2 APP to add NodeID_A and NodeID_B to the target node ID and the current node ID of the node ID mapping table respectively. Optionally, the homeowner uses the Admin2 APP to add FabricA_ID and FabricB_ID to the target network ID and the current network ID of the node ID mapping table respectively.

Specifically, after performing the above S1-1 to S1-6 configurations for each device in the smart home system, Admin2 APP becomes the administrator of all devices in the smart home system, and Admin2 APP obtains the complete node identification mapping of all devices surface.

Embodiments 1 to 3 are used below to describe in detail how the first woven network in this application replicates the private configuration information for at least one device in the second woven network.

Embodiment 1, the first information (such as the CopySettingsFromFabric command) includes a fabric network ID and a node ID mapping table. For example, the first fabric network can be FabricB, the second fabric network can be FabricA, the first configuration device can be the Admin2 APP controlled by the house owner, and the second configuration device can be the Admin1 APP controlled by the integrator. As shown in Figure 5, the Admin2 APP can copy at least some of the steps in S10-1 to S10-8 as follows, all the configurations made by the Admin1 APP for the terminal device in FabricA.

S10-1. The homeowner checks the Fabric to which the terminal device belongs on the Admin2 APP.

S10-2, Admin2 APP sends an instruction to the terminal device to view the Fabrics attribute of the node operation credential functional unit.

S10-3, the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.

S10-4. The homeowner knows that FabricA is the Fabric configured by the integrator, so he operates and copies the configuration of FabricA on the Admin2 APP.

S10-5, the Admin2 APP sends the CopySettingsFromFabric command to the terminal device, wherein the CopySettingsFromFabric command carries the weaving network identifier and the node identifier mapping table, the weaving network identifier corresponds to the Index of FabricA, and the node identifier mapping table can be passed through the above S1-1 to S1-6 obtained from .

S10-6. After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.

S10-7. The terminal device finds all fabric-scoped private (Fabric-Scoped) functional units belonging to FabricA according to the fabric network identifier carried by the CopySettingsFromFabric command, such as binding, group, ACL, etc., and adds the corresponding functional units of FabricB.

S10-8, for each added functional unit of FabricB, the terminal device finds the corresponding NodeID_A in the node ID mapping table according to the node ID (NodeID) contained therein, and replaces it with the NodeID_B in the corresponding table.

Specifically, after copying the above S10-1 to S10-8 for each device in the smart home system, the Admin2 APP can obtain all configurations made in FabricA for all devices in the smart home system.

Embodiment 2, the first information (such as the CopySettingsFromFabric command) includes a fabric network identifier, a node identifier mapping table, and a list of functional units. For example, the first fabric network can be FabricB, the second fabric network can be FabricA, the first configuration device can be the Admin2 APP controlled by the house owner, and the second configuration device can be the Admin1 APP controlled by the integrator. As shown in Figure 6, the Admin2 APP can copy at least some of the steps in the following S20-1 to S20-8 for all configurations made by the Admin1 APP for the terminal device in FabricA.

S20-1. The homeowner checks the Fabric to which the terminal device belongs on the Admin2 APP.

S20-2, Admin2 APP sends an instruction to the terminal device to check the Fabrics attribute of the node operation credential functional unit.

S20-3, the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.

S20-4, the homeowner understands that FabricA is the Fabric configured by the integrator, so he operates and copies the configuration of FabricA on the Admin2 APP.

S20-5, the Admin2 APP sends the CopySettingsFromFabric command to the terminal device, wherein the CopySettingsFromFabric command carries the weaving network identifier, the node identifier mapping table and the list of functional units, the weaving network identifier corresponds to the Index of FabricA, and the node identifier mapping table can be passed through the above S1-1 To obtain in S1-6, the functional unit list is used to indicate at least one functional unit that needs to be copied.

S20-6. After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.

S20-7. The terminal device finds the functional units specified in the functional unit list belonging to FabricA according to the fabric network identifier carried by the CopySettingsFromFabric command, such as groups and ACLs, and adds corresponding functional units of FabricB.

S20-8, for each added functional unit of FabricB, the terminal device finds the corresponding NodeID_A in the node ID mapping table according to the node ID (NodeID) contained therein, and replaces it with the NodeID_B in the corresponding table.

Specifically, after copying the above S20-1 to S20-8 for each device in the smart home system, the Admin2 APP can obtain the configuration of the functional unit specified in the functional unit list for all devices in the smart home system in FabricA .

Embodiment 3, the first information (such as the CopySettingsFromFabric command) includes a fabric network identifier, a node identifier mapping table, and a target list. For example, the first fabric network can be FabricB, the second fabric network can be FabricA, the first configuration device can be the Admin2 APP controlled by the house owner, and the second configuration device can be the Admin1 APP controlled by the integrator. As shown in Figure 7, Admin2 APP can copy at least some of the steps in S30-1 to S30-8, all the configurations done by Admin1 APP for the terminal device in FabricA.

S30-1. The homeowner checks the Fabric to which the terminal device belongs on the Admin2 APP.

S30-2, the Admin2 APP sends an instruction to the terminal device to view the Fabrics attribute of the node operation credential functional unit.

S30-3, the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.

S30-4, the homeowner understands that FabricA is the Fabric configured by the integrator, so he operates and copies the configuration of FabricA on the Admin2 APP.

S30-5, the Admin2 APP sends the CopySettingsFromFabric command to the terminal device, wherein the CopySettingsFromFabric command carries the weaving network identifier, the node identifier mapping table and the target list, the weaving network identifier corresponds to the Index of FabricA, and the node identifier mapping table can be passed through the above S1-1 to Acquired in S1-6, the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to the endpoint needs to be copied, or the target list is used to indicate that at least one functional unit needs to be copied The functional unit corresponding to the device type.

S30-6. After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.

S30-7. The terminal device finds the functional units specified in the target list belonging to FabricA according to the fabric network identifier carried by the CopySettingsFromFabric command, such as groups and ACLs, and adds the corresponding functional units of FabricB.

S30-8, for each added functional unit of FabricB, the terminal device finds the corresponding NodeID_A in the node ID mapping table according to the node ID (NodeID) contained therein, and replaces it with the NodeID_B in the corresponding table.

Specifically, after copying the above S30-1 to S30-8 for each device in the smart home system, the Admin2 APP can obtain the configuration of the functional units specified in the target list for all devices in the smart home system in FabricA.

Therefore, in this embodiment of the present application, the configuration device in the first weave network may instruct to copy the private configuration information for at least one device in the second weave network, thereby realizing the copying of the private configuration information for at least one device in the second weave network Purpose of Information. That is to say, it can solve the problem of cumbersome configuration in the smart home system authority transfer process. By adding the copy configuration command from the weaving network, the configuration device in the first weaving network can conveniently copy the configured functional units of the second weaving network.

The method embodiment of the present application is described in detail above in conjunction with FIG. 3 to FIG. 7 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 8 to FIG. 9 . It should be understood that the device embodiment and the method embodiment correspond to each other, similar to The description can refer to the method embodiment.

Fig. 8 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in FIG. 8, the terminal device 300 includes:

a communication unit 310, configured to receive first information sent by the first configuration device;

In some embodiments, the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second weave network includes the identifier of the second weave network.

In some embodiments, the private configuration information for the at least one device in the second woven network includes at least one of the following information:

Access control list ACL information, group information, scene information, binding information, proxy information, node operation credential information, OTA information.

In some embodiments, the first information includes weaving network identification information, wherein the weaving network identification information is used to indicate the second weaving network.

In some embodiments, the first information further includes a node identification mapping table;

Wherein, the node identification mapping table is used to indicate the mapping relationship between the node identification information of the M devices in the first woven network and the node identification information in the second woven network, and the M devices The device includes the at least one device, or the M devices include the terminal device, or the M devices include the at least one device and a device associated with the at least one device, or the M The number of devices includes the terminal device and devices associated with the terminal device, and M is a positive integer.

In some embodiments, the node identification structure corresponding to the terminal device in the node identification structure list includes target node identification information and current node identification information, wherein the target node identification information is the terminal device in the second weaving network Node identification information, where the current node identification information is node identification information of the terminal device in the first woven network.

In some embodiments, the node identification structure corresponding to the terminal device in the node identification structure list further includes target weaving network identification information and current weaving network identification information, wherein the target weaving network identification information is the identification of the second weaving network Information, the identification information of the current weaving network is the identification information of the first weaving network.

In some embodiments, the terminal device 300 further includes: a processing unit 320;

The processing unit 320 is configured to add, according to the first information, all private functional units corresponding to the terminal device that belong to the second weaving network to the configuration information of the first weaving network for the terminal device Corresponding private configuration information.

The processing unit 320 is configured to obtain all private functional units corresponding to the terminal device and belonging to the second weaving network according to the first information;

The processing unit 320 is further configured to add all the private functional units belonging to the second weaving network to the functional units of the first weaving network;

For each added private function unit, the processing unit 320 is further configured to replace its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.

In some embodiments, the attributes or attribute fields of all private functional units include identification information of the second weaving network.

In some embodiments, the all private functional units include at least one of the following functional units:

In some embodiments, the first information also includes a list of functional units;

Wherein, the functional unit list is used to indicate at least one functional unit that needs to be copied.

In some embodiments, the functional units indicated by the functional unit list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.

The processing unit 320 is configured to add, according to the first information, all private functional units corresponding to the terminal device that belong to the second weaving network to the configuration information of the first weaving network for the terminal device The private configuration information corresponding to the functional units indicated in the functional unit list in .

The processing unit 320 is configured to obtain, according to the first information, the functional units indicated by the functional unit list among all private functional units belonging to the second weaving network corresponding to the terminal device;

The processing unit 320 is further configured to add, among the functional units of the first weaving network, the functional units indicated by the list of functional units belonging to the second weaving network;

In some embodiments, the first information further includes a target list; where the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or , the target list is used to indicate that at least one functional unit corresponding to the device type needs to be copied.

In some embodiments, the functional units indicated by the target list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA function unit.

The processing unit 320 is configured to add, according to the first information, all private functional units corresponding to the terminal device that belong to the second weaving network to the configuration information of the first weaving network for the terminal device The private configuration information corresponding to the functional units indicated in the target list in .

The processing unit 320 is configured to obtain, according to the first information, the functional units indicated by the target list among all private functional units belonging to the second weaving network corresponding to the terminal device;

The processing unit 320 is further configured to add, among the functional units of the first weaving network, the functional units indicated by the target list belonging to the second weaving network;

In some embodiments, the terminal device 300 also includes:

The processing unit 320 is configured to determine that the first configuration device has administrator authority.

In some embodiments, the first information is a copy configuration CopySettingsFromFabric command by the fabric network.

In some embodiments, the above-mentioned communication unit may be a communication interface or a transceiver, or an input-output interface of a communication chip or a system-on-chip. The aforementioned processing unit may be one or more processors.

It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 300 are to realize the For the sake of brevity, the corresponding flow of the terminal device in the shown method will not be repeated here.

Fig. 9 shows a schematic block diagram of a configuration device 400 according to an embodiment of the present application. The configuration device 400 is a first configuration device. As shown in FIG. 9, the configuration device 400 includes:

a communication unit 410, configured to send first information to at least one device;

Wherein, the first configuration device is a configuration device in the first weave network, and the first information is used to generate private configuration information of the first weave network for at least one device, and the first weave network is for the private configuration information of the at least one device. The configuration information is obtained by duplicating private configuration information for the at least one device in the second woven network, where the at least one device includes a terminal device.

In some embodiments, the private configuration information for the at least one device in the second woven network includes at least one of the following information: access control list ACL information, group information, scene information, binding information, proxy information, node operation Credential information, download OTA information over the air.

In some embodiments, the configuration device 400 further includes: a processing unit 420;

The communication unit 410 is also configured to acquire node identification information of the at least one device in the first woven network and the second woven network;

The processing unit 420 is configured to generate the node identifier mapping table according to the node identifier information of the at least one device in the first woven network and the second woven network.

In some embodiments, the communication unit 410 is further configured to acquire the private configuration information for the at least one device in the second woven network.

It should be understood that the configuration device 400 according to the embodiment of the present application may correspond to the first configuration device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the configuration device 400 are respectively in order to realize the For the sake of brevity, the corresponding flow of the first configuration device in the method shown in FIG. 7 will not be repeated here.

FIG. 10 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in FIG. 10 includes a processor 510, and the processor 510 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

In some embodiments, as shown in FIG. 10 , the communication device 500 may further include a memory 520 . Wherein, the processor 510 can invoke and run a computer program from the memory 520, so as to implement the method in the embodiment of the present application.

Wherein, the memory 520 may be an independent device independent of the processor 510 , or may be integrated in the processor 510 .

In some embodiments, as shown in FIG. 10 , the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, to send information or data to other devices, or Receive information or data from other devices.

Wherein, the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, and the number of antennas may be one or more.

In some embodiments, the communication device 500 may specifically be the configuration device of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the first configuration device in each method of the embodiment of the present application. For brevity, in This will not be repeated here.

In some embodiments, the communication device 500 may specifically be the terminal device in the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, the Let me repeat.

Fig. 11 is a schematic structural diagram of a device according to an embodiment of the present application. The apparatus 600 shown in FIG. 11 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

In some embodiments, as shown in FIG. 11 , the device 600 may further include a memory 620 . Wherein, the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.

Wherein, the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .

In some embodiments, the device 600 may further include an input interface 630 . Wherein, the processor 610 can control the input interface 630 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.

In some embodiments, the device 600 may further include an output interface 640 . Wherein, the processor 610 can control the output interface 640 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

In some embodiments, the apparatus 600 can be applied to the configuration device in the embodiment of the present application, and the apparatus 600 can implement the corresponding process implemented by the first configuration device in each method of the embodiment of the application. For the sake of brevity, here No longer.

In some embodiments, the apparatus 600 can be applied to the terminal device in the embodiment of the present application, and the apparatus 600 can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, the repeat.

In some embodiments, the device mentioned in the embodiment of the present application may also be a chip. For example, it may be a system-on-a-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.

Fig. 12 is a schematic block diagram of a communication system 700 provided by an embodiment of the present application. As shown in FIG. 12 , the communication system 700 includes at least a terminal device 710 , a first configuration device 720 and a second configuration device 730 .

Wherein, the terminal device 710 can be used to realize the corresponding functions realized by the terminal device in the above method, and the first configuration device 720 can be used to realize the corresponding functions realized by the first configuration device in the above method. For the sake of brevity, I won't repeat them here.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. The volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (Dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM ) and Direct Memory Bus Random Access Memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

In some embodiments, the computer-readable storage medium can be applied to the configuration device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first configuration device in the methods of the embodiments of the present application, in order It is concise and will not be repeated here.

In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, I won't repeat them here.

The embodiment of the present application also provides a computer program product, including computer program instructions.

In some embodiments, the computer program product can be applied to the configuration device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first configuration device in the various methods of the embodiments of the present application. For the sake of brevity , which will not be repeated here.

In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the terminal device in the methods of the embodiments of the present application. For brevity, the This will not be repeated here.

The embodiment of the present application also provides a computer program.

In some embodiments, the computer program can be applied to the configuration device in the embodiment of the present application. When the computer program is run on the computer, the computer executes the corresponding functions implemented by the first configuration device in the methods of the embodiment of the present application. For the sake of brevity, the process will not be repeated here.

In some embodiments, the computer program can be applied to the terminal device in the embodiment of the present application. When the computer program is run on the computer, the computer executes the corresponding process implemented by the terminal device in each method of the embodiment of the present application, For the sake of brevity, details are not repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. For such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for wireless communication, comprising:

The terminal device receives the first information sent by the first configuration device;

Wherein, the first configuration device is a configuration device in the first woven network, the first information is used to generate private configuration information for at least one device of the first woven network, and the first woven network is for the The private configuration information of the at least one device is obtained by duplicating the private configuration information for the at least one device in the second woven network, the at least one device including the terminal device.
The method according to claim 1, wherein the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second woven network includes the identification information of the second woven network .
The method according to claim 1 or 2, wherein the private configuration information for the at least one device in the second woven network includes at least one of the following information:

Access control list ACL information, group information, scene information, binding information, proxy information, node operation credential information, OTA information.
The method according to any one of claims 1 to 3, characterized in that,

The first information includes weaving network identification information, where the weaving network identification information is used to indicate the second weaving network.
The method of claim 4, wherein

The first information also includes a node identification mapping table;

Wherein, the node identifier mapping table is used to indicate the mapping relationship between the node identifier information of the M devices in the first woven network and the node identifier information in the second woven network, and the M The M devices include the at least one device, or, the M devices include the terminal device, or, the M devices include the at least one device and a device associated with the at least one device, or, the The M devices include the terminal device and devices associated with the terminal device, and M is a positive integer.
The method of claim 5, wherein,

The type information corresponding to the node identifier mapping table is a node identifier structure list, and the M node identifier structures included in the node identifier structure list correspond to the M devices respectively.
The method of claim 6, wherein

The node identification structure corresponding to the terminal device in the node identification structure list includes target node identification information and current node identification information, wherein the target node identification information is the node of the terminal device in the second woven network Identification information, where the current node identification information is node identification information of the terminal device in the first woven network.
The method of claim 7, wherein

The node identification structure corresponding to the terminal device in the node identification structure list further includes target weaving network identification information and current weaving network identification information, wherein the target weaving network identification information is the identification information of the second weaving network, The current weaving network identification information is the identification information of the first weaving network.
The method according to any one of claims 4 to 8, further comprising:

The terminal device adds, according to the first information, private information corresponding to all private functional units belonging to the second weaving network corresponding to the terminal device to the configuration information of the first weaving network for the terminal device. configuration information.
The method according to any one of claims 4 to 9, further comprising:

The terminal device acquires all private functional units corresponding to the terminal device that belong to the second weaving network according to the first information;

Adding, by the terminal device, all private functional units belonging to the second woven network to the functional units of the first woven network;

For each added private function unit, the terminal device replaces its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The method according to claim 10, wherein the attributes or attribute fields of all private functional units include identification information of the second weaving network.
The method according to claim 10 or 11, wherein said all private functional units include at least one of the following functional units:

ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
The method according to any one of claims 4 to 8, characterized in that,

The first information also includes a list of functional units;

Wherein, the functional unit list is used to indicate at least one functional unit that needs to be copied.
The method of claim 13, wherein,

The functional units indicated by the functional unit list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
The method according to claim 13 or 14, characterized in that,

The type information corresponding to the functional unit list is a functional unit identification list, wherein the functional unit identification list includes identification information of the at least one functional unit.
The method according to any one of claims 13 to 15, further comprising:

The terminal device adds, according to the first information, the configuration information of the first woven network for the terminal device, which is described in all the private functional units corresponding to the terminal device and which belong to the second woven network. Private configuration information corresponding to the functional units indicated in the functional unit list.
The method according to any one of claims 13 to 16, further comprising:

The terminal device obtains, according to the first information, the functional units indicated by the functional unit list among all private functional units belonging to the second weaving network corresponding to the terminal device;

Adding, by the terminal device, the functional units indicated by the list of functional units belonging to the second woven network to the functional units of the first woven network;

For each added private function unit, the terminal device replaces its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The method according to any one of claims 4 to 8, characterized in that,

The first information also includes a target list;

Wherein, the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or the target list is used to indicate that at least one device needs to be copied The functional unit corresponding to the type.
The method of claim 18, wherein,

The functional units indicated by the target list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
The method of claim 18 or 19, wherein,

The type information corresponding to the target list is a target structure list; wherein,

In the case where the target list is used to indicate the at least one functional unit that needs to be copied, at least one target structure included in the target structure list corresponds to the at least one functional unit respectively, and one of the target structure lists The target structure includes at least identification information of the corresponding functional unit; or,

In the case where the target list is used to indicate that the functional unit corresponding to the at least one endpoint needs to be copied, at least one target structure included in the target structure list corresponds to the at least one endpoint respectively, and the target structures in the target structure list an object structure includes at least the endpoint number of the corresponding endpoint; or,

When the target list is used to indicate that the functional unit corresponding to the at least one device type needs to be copied, at least one target structure included in the target structure list corresponds to the at least one device type, and the target structure list An object structure in includes at least identification information of the corresponding device type.
The method according to any one of claims 18 to 20, further comprising:

The terminal device adds, according to the first information, the configuration information of the first woven network for the terminal device, which is described in all the private functional units corresponding to the terminal device and which belong to the second woven network. The private configuration information corresponding to the functional units indicated in the target list.
The method according to any one of claims 18 to 21, further comprising:

The terminal device obtains, according to the first information, the functional units indicated by the target list among all private functional units belonging to the second weaving network corresponding to the terminal device;

Adding, by the terminal device, the functional units indicated by the target list belonging to the second weaved network to the functional units of the first weaved network;

For each added private function unit, the terminal device replaces its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The method according to any one of claims 1 to 22, further comprising:

The terminal device determines that the first configuration device has administrator authority.
The method according to any one of claims 1 to 23, wherein the first information is a command CopySettingsFromFabric configured by fabric network copy.
A method for wireless communication, comprising:

the first configuration device sends first information to at least one device;

Wherein, the first configuration device is a configuration device in the first woven network, the first information is used to generate private configuration information for at least one device of the first woven network, and the first woven network is for the The private configuration information of the at least one device is obtained by duplicating the private configuration information for the at least one device in the second woven network, and the at least one device includes a terminal device.
The method according to claim 25, wherein the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second woven network includes the identification information of the second woven network .
The method according to claim 25 or 26, wherein the private configuration information for the at least one device in the second woven network includes at least one of the following information:

Access control list ACL information, group information, scene information, binding information, proxy information, node operation credential information, OTA information.
A method according to any one of claims 25 to 27, wherein,

The first information includes weaving network identification information, where the weaving network identification information is used to indicate the second weaving network.
The method of claim 28, wherein,

The first information also includes a node identification mapping table;

Wherein, the node identifier mapping table is used to indicate the mapping relationship between the node identifier information of the M devices in the first woven network and the node identifier information in the second woven network, and the M The M devices include the at least one device, or, the M devices include the terminal device, or, the M devices include the at least one device and a device associated with the at least one device, or, the The M devices include the terminal device and devices associated with the terminal device, and M is a positive integer.
The method of claim 29, wherein,

The type information corresponding to the node identifier mapping table is a node identifier structure list, and the M node identifier structures included in the node identifier structure list correspond to the M devices respectively.
The method of claim 30, wherein,

The node identification structure corresponding to the terminal device in the node identification structure list includes target node identification information and current node identification information, wherein the target node identification information is the node of the terminal device in the second woven network Identification information, where the current node identification information is node identification information of the terminal device in the first woven network.
The method of claim 31, wherein,

The node identification structure corresponding to the terminal device in the node identification structure list further includes target weaving network identification information and current weaving network identification information, wherein the target weaving network identification information is the identification information of the second weaving network, The current weaving network identification information is the identification information of the first weaving network.
A method as claimed in any one of claims 28 to 32, wherein,

The first information also includes a list of functional units;

Wherein, the functional unit list is used to indicate at least one functional unit that needs to be copied.
The method of claim 33, wherein,

The functional units indicated by the functional unit list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
A method as claimed in claim 33 or 34, characterized in that,

The type information corresponding to the functional unit list is a functional unit identification list, wherein the functional unit identification list includes identification information of the at least one functional unit.
A method as claimed in any one of claims 28 to 32, wherein,

The first information also includes a target list;

Wherein, the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or the target list is used to indicate that at least one device needs to be copied The functional unit corresponding to the type.
The method of claim 36, wherein,

The functional units indicated by the target list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
A method as claimed in claim 36 or 37, characterized in that,

The type information corresponding to the target list is a target structure list; wherein,

In the case where the target list is used to indicate the at least one functional unit that needs to be copied, at least one target structure included in the target structure list corresponds to the at least one functional unit respectively, and one of the target structure lists The target structure includes at least identification information of the corresponding functional unit; or,

In the case where the target list is used to indicate that the functional unit corresponding to the at least one endpoint needs to be copied, at least one target structure included in the target structure list corresponds to the at least one endpoint respectively, and the target structures in the target structure list an object structure includes at least the endpoint number of the corresponding endpoint; or,

When the target list is used to indicate that the functional unit corresponding to the at least one device type needs to be copied, at least one target structure included in the target structure list corresponds to the at least one device type, and the target structure list An object structure in includes at least identification information of the corresponding device type.
The method according to any one of claims 29 to 38, further comprising:

The first configuration device acquires node identification information of the at least one device in the first woven network and the second woven network;

The first configuration device generates the node identifier mapping table according to the node identifier information of the at least one device in the first woven network and the second woven network.
The method according to any one of claims 25 to 39, further comprising:

The first configuration device acquires the private configuration information for the at least one device in the second woven network.
The method according to any one of claims 25 to 40, wherein the first information is a command CopySettingsFromFabric configured by fabric network copy.
A terminal device, characterized in that it includes:

a communication unit, configured to receive the first information sent by the first configuration device;

Wherein, the first configuration device is a configuration device in the first woven network, the first information is used to generate private configuration information for at least one device of the first woven network, and the first woven network is for the The private configuration information of the at least one device is obtained by duplicating the private configuration information for the at least one device in the second woven network, the at least one device including the terminal device.
The terminal device according to claim 42, wherein the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second weaving network includes the identifier of the second weaving network .
The terminal device according to claim 42 or 43, wherein the private configuration information for the at least one device in the second woven network includes at least one of the following information:

Access control list ACL information, group information, scene information, binding information, proxy information, node operation credential information, OTA information.
The terminal device according to any one of claims 42 to 44, characterized in that,

The first information includes weaving network identification information, where the weaving network identification information is used to indicate the second weaving network.
The terminal device according to claim 45, characterized in that,

The first information also includes a node identification mapping table;

Wherein, the node identifier mapping table is used to indicate the mapping relationship between the node identifier information of the M devices in the first woven network and the node identifier information in the second woven network, and the M The M devices include the at least one device, or, the M devices include the terminal device, or, the M devices include the at least one device and a device associated with the at least one device, or, the The M devices include the terminal device and devices associated with the terminal device, and M is a positive integer.
The terminal device according to claim 46, characterized in that,

The type information corresponding to the node identifier mapping table is a node identifier structure list, and the M node identifier structures included in the node identifier structure list correspond to the M devices respectively.
The terminal device according to claim 47, characterized in that,

The node identification structure corresponding to the terminal device in the node identification structure list includes target node identification information and current node identification information, wherein the target node identification information is the node of the terminal device in the second woven network Identification information, where the current node identification information is node identification information of the terminal device in the first woven network.
The terminal device according to claim 48, characterized in that,

The node identification structure corresponding to the terminal device in the node identification structure list further includes target weaving network identification information and current weaving network identification information, wherein the target weaving network identification information is the identification information of the second weaving network, The current weaving network identification information is the identification information of the first weaving network.
The terminal device according to any one of claims 45 to 49, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to add, according to the first information, the configuration information of the terminal device in the first weave network corresponding to all private function units belonging to the second weave network corresponding to the terminal device. private configuration information.
The terminal device according to any one of claims 45 to 50, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to acquire all private functional units corresponding to the terminal device and belonging to the second weaving network according to the first information;

The processing unit is further configured to add all the private functional units belonging to the second weaving network to the functional units of the first weaving network;

For each added private function unit, the processing unit is further configured to replace its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The terminal device according to claim 51, wherein the attributes or attribute fields of all the private functional units include the identification information of the second weaving network.
The terminal device according to claim 51 or 52, characterized in that,

All the private functional units include at least one of the following functional units:

ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit, node operation credential functional unit, OTA functional unit.
The terminal device according to any one of claims 45 to 49, characterized in that,

The first information also includes a list of functional units;

Wherein, the functional unit list is used to indicate at least one functional unit that needs to be copied.
The terminal device according to claim 54, wherein the functional units indicated by the functional unit list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy function unit, node operation credential functional unit, OTA functional unit.
The terminal device according to claim 54 or 55, characterized in that,

The type information corresponding to the functional unit list is a functional unit identification list, wherein the functional unit identification list includes identification information of the at least one functional unit.
The terminal device according to any one of claims 54 to 56, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to, according to the first information, add in the configuration information of the first weaving network for the terminal device to all private functional units corresponding to the terminal device that belong to the second weaving network Private configuration information corresponding to the functional units indicated in the functional unit list.
The terminal device according to any one of claims 54 to 57, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to obtain, according to the first information, the functional units indicated by the functional unit list among all private functional units belonging to the second weaving network corresponding to the terminal device;

The processing unit is further configured to add, among the functional units of the first woven network, the functional units indicated by the list of functional units belonging to the second woven network;

For each added private function unit, the processing unit is further configured to replace its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The terminal device according to any one of claims 45 to 49, characterized in that,

The first information further includes a target list; wherein, the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or, the The target list is used to indicate that at least one functional unit corresponding to the device type needs to be copied.
The terminal device according to claim 59, wherein the functional units indicated by the target list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit , node operation credential functional unit, OTA functional unit.
The terminal device according to claim 59 or 60, characterized in that,

The type information corresponding to the target list is a target structure list; wherein,

In the case where the target list is used to indicate the at least one functional unit that needs to be copied, at least one target structure included in the target structure list corresponds to the at least one functional unit respectively, and one of the target structure lists The target structure includes at least identification information of the corresponding functional unit; or,

In the case where the target list is used to indicate that the functional unit corresponding to the at least one endpoint needs to be copied, at least one target structure included in the target structure list corresponds to the at least one endpoint respectively, and the target structures in the target structure list an object structure includes at least the endpoint number of the corresponding endpoint; or,

When the target list is used to indicate that the functional unit corresponding to the at least one device type needs to be copied, at least one target structure included in the target structure list corresponds to the at least one device type, and the target structure list An object structure in includes at least identification information of the corresponding device type.
The terminal device according to any one of claims 59 to 61, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to, according to the first information, add in the configuration information of the first weaving network for the terminal device to all private functional units corresponding to the terminal device that belong to the second weaving network Private configuration information corresponding to the functional units indicated by the target list.
The terminal device according to any one of claims 59 to 62, characterized in that,

The terminal device also includes: a processing unit;

The processing unit is configured to obtain, according to the first information, the functional units indicated by the target list among all private functional units belonging to the second weaving network corresponding to the terminal device;

The processing unit is further configured to add, among the functional units of the first weaving network, the functional units indicated by the target list belonging to the second weaving network;

For each added private function unit, the processing unit is further configured to replace its corresponding node identification information in the second woven network with the corresponding node identification information in the first woven network.
The terminal device according to any one of claims 42 to 63, wherein the terminal device further comprises:

A processing unit, configured to determine that the first configuration device has administrator authority.
The terminal device according to any one of claims 42 to 64, wherein the first information is a copy configuration CopySettingsFromFabric command by the fabric network.
A configuration device, characterized in that the configuration device is a first configuration device, and the configuration device includes:

a communication unit, configured to send first information to at least one device;

Wherein, the first configuration device is a configuration device in the first woven network, the first information is used to generate private configuration information for at least one device of the first woven network, and the first woven network is for the The private configuration information of the at least one device is obtained by duplicating the private configuration information for the at least one device in the second woven network, and the at least one device includes a terminal device.
The configuration device according to claim 66, wherein the attribute or attribute field of the functional unit corresponding to the private configuration information of the at least one device in the second weave network includes the identifier of the second weave network .
The configuration device according to claim 66 or 67, wherein the private configuration information for the at least one device in the second weave network includes at least one of the following information:

Access control list ACL information, group information, scene information, binding information, proxy information, node operation credential information, OTA information.
A configuration device as claimed in any one of claims 66 to 68, characterized in that

The first information includes weaving network identification information, where the weaving network identification information is used to indicate the second weaving network.
Configuration device as claimed in claim 69, characterized in that,

The first information also includes a node identification mapping table;

Wherein, the node identifier mapping table is used to indicate the mapping relationship between the node identifier information of the M devices in the first woven network and the node identifier information in the second woven network, and the M The M devices include the at least one device, or, the M devices include the terminal device, or, the M devices include the at least one device and a device associated with the at least one device, or, the The M devices include the terminal device and devices associated with the terminal device, and M is a positive integer.
Configuration device as claimed in claim 70, characterized in that,

The type information corresponding to the node identifier mapping table is a node identifier structure list, and the M node identifier structures included in the node identifier structure list correspond to the M devices respectively.
Configuration device as claimed in claim 71, characterized in that,

The node identification structure corresponding to the terminal device in the node identification structure list includes target node identification information and current node identification information, wherein the target node identification information is the node of the terminal device in the second woven network Identification information, where the current node identification information is node identification information of the terminal device in the first woven network.
Configuration device as claimed in claim 72, characterized in that,

The node identification structure corresponding to the terminal device in the node identification structure list further includes target weaving network identification information and current weaving network identification information, wherein the target weaving network identification information is the identification information of the second weaving network, The current weaving network identification information is the identification information of the first weaving network.
A configuration device as claimed in any one of claims 69 to 73, characterized in that

The first information also includes a list of functional units;

Wherein, the functional unit list is used to indicate at least one functional unit that needs to be copied.
The configuration device according to claim 74, wherein the functional units indicated by the functional unit list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy function unit, node operation credential functional unit, OTA functional unit.
Configuration device as claimed in claim 74 or 75, characterized in that,

The type information corresponding to the functional unit list is a functional unit identification list, wherein the functional unit identification list includes identification information of the at least one functional unit.
A configuration device as claimed in any one of claims 69 to 73, characterized in that

The first information further includes a target list; wherein, the target list is used to indicate at least one functional unit that needs to be copied, or the target list is used to indicate that at least one functional unit corresponding to an endpoint needs to be copied, or, the The target list is used to indicate that at least one functional unit corresponding to the device type needs to be copied.
The configuration device according to claim 77, wherein the functional units indicated by the target list include at least one of the following functional units: ACL functional unit, group functional unit, scene functional unit, binding functional unit, proxy functional unit , node operation credential functional unit, OTA functional unit.
Configuration device as claimed in claim 77 or 78, characterized in that,

The type information corresponding to the target list is a target structure list; wherein,

In the case where the target list is used to indicate the at least one functional unit that needs to be copied, at least one target structure included in the target structure list corresponds to the at least one functional unit respectively, and one of the target structure lists The target structure includes at least identification information of the corresponding functional unit; or,

In the case where the target list is used to indicate that the functional unit corresponding to the at least one endpoint needs to be copied, at least one target structure included in the target structure list corresponds to the at least one endpoint respectively, and the target structures in the target structure list an object structure includes at least the endpoint number of the corresponding endpoint; or,

When the target list is used to indicate that the functional unit corresponding to the at least one device type needs to be copied, at least one target structure included in the target structure list corresponds to the at least one device type, and the target structure list An object structure in includes at least identification information of the corresponding device type.
A configuration device as claimed in any one of claims 70 to 79, characterized in that

The configuration device further includes: a processing unit;

The communication unit is further configured to acquire node identification information of the at least one device in the first woven network and the second woven network;

The processing unit is configured to generate the node identifier mapping table according to node identifier information of the at least one device in the first woven network and the second woven network.
A configuration device as claimed in any one of claims 66 to 80, characterized in that

The communication unit is further configured to obtain the private configuration information for the at least one device in the second woven network.
The configuration device according to any one of claims 66 to 81, wherein the first information is a copy configuration CopySettingsFromFabric command by the fabric network.
A terminal device, characterized in that it includes: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the computer program described in claims 1 to 24 any one of the methods described.
A configuration device, characterized in that it includes: a processor and a memory, the memory is used to store a computer program, the processor is used to invoke and run the computer program stored in the memory, and perform the tasks described in claims 25 to 41 any one of the methods described.
A chip, characterized by comprising: a processor, configured to invoke and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 24.
A chip, characterized by comprising: a processor, configured to invoke and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 25 to 41.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causes a computer to execute the method according to any one of claims 1 to 24.
A computer-readable storage medium, characterized by being used to store a computer program, the computer program causes a computer to execute the method according to any one of claims 25 to 41.
A computer program product, characterized by comprising computer program instructions, the computer program instructions cause a computer to execute the method according to any one of claims 1 to 24.
A computer program product, characterized by comprising computer program instructions, the computer program instructions cause a computer to execute the method according to any one of claims 25 to 41.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1-24.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 25 to 41.