WO2023123400A1 - Procédés et dispositifs de communication sans fil - Google Patents

Procédés et dispositifs de communication sans fil Download PDF

Info

Publication number
WO2023123400A1
WO2023123400A1 PCT/CN2021/143806 CN2021143806W WO2023123400A1 WO 2023123400 A1 WO2023123400 A1 WO 2023123400A1 CN 2021143806 W CN2021143806 W CN 2021143806W WO 2023123400 A1 WO2023123400 A1 WO 2023123400A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
functional unit
network
terminal device
list
Prior art date
Application number
PCT/CN2021/143806
Other languages
English (en)
Chinese (zh)
Inventor
茹昭
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2021/143806 priority Critical patent/WO2023123400A1/fr
Publication of WO2023123400A1 publication Critical patent/WO2023123400A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • 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.
  • 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.
  • a wireless communication method includes:
  • the terminal device receives the first information sent by the first configuration device
  • the first configuration device is a configuration device in the first weave network
  • the first information is used to generate private configuration information of the first weave network for at least one device
  • 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.
  • a wireless communication method in a second aspect, includes:
  • the first configuration device sends first information to at least one device
  • the first configuration device is a configuration device in the first weave network
  • the first information is used to generate private configuration information of the first weave network for at least one device
  • 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.
  • a terminal device configured to execute the method in the first aspect above.
  • the terminal device includes a functional module for executing the method in the first aspect above.
  • a configuration device configured to execute the method performed by the first configuration device in the second aspect above.
  • the configuration device includes a functional module for executing the method performed by the first configuration device in the second aspect above.
  • a terminal device including 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 to execute the method in the first aspect above.
  • a configuration device including 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 to execute the method in the second aspect above.
  • an apparatus for implementing the method in any one of the first aspect to the second aspect above.
  • 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.
  • 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.
  • a computer program product 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.
  • a computer program which, when running on a computer, causes the computer to execute the method in any one of the above first to second aspects.
  • 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.
  • the configuration device in the first weaving network can conveniently copy the configured functional units of the second weaving network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • pre-defined may refer to defined in the protocol.
  • the "protocol” may refer to a standard protocol in the field of the Internet of Things, which is not limited in this application.
  • a user in a Fabric can share the smart home system with users in other Fabrics through a configuration device with administrator rights.
  • 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.
  • 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.
  • a terminal device such as a mobile phone
  • the role of a terminal device includes both a commissioner and a controller.
  • A-APP A application
  • 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.
  • A-APP can specifically add B-APP as the administrator of smart light bulbs through S1-S16.
  • User A triggers the configuration mode of turning on the smart light bulb
  • 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);
  • the activation token Onboarding Token, OT
  • the activation token may include a Discovery Capabilities Mask, a randomly generated configuration code (SetupCode), and a discriminator (Discriminator);
  • A-APP sends an instruction to turn on the configuration to the smart light bulb, and the instruction carries OT;
  • the smart light bulb After the smart light bulb receives the instruction, it sends a confirmation feedback to the A-APP;
  • the smart light bulb enters the configuration discovery mode, such as public domain name system service discovery (Domain Name System Service Discovery DNS-SD);
  • A-APP shares OT with B-APP through mail, voice and other out-of-band methods
  • S8.B-APP discovers the smart light bulb and connects to the resolved Internet Protocol (Internet Protocol, IP) address/port;
  • IP Internet Protocol
  • the B-APP creates a Fabric ID for the home network.
  • the smart light bulb obtains the operation key
  • 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;
  • S16.B-APP configures B.OC.bulb and access control authority ACL.Bulb.B.APP to the smart bulb.
  • user B can configure the smart home system to meet his own needs.
  • 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.
  • 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.
  • node operation certificate means refer to the detailed description part, and all means that all values are allowed in the numerical data type.
  • 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.
  • the Fabric description structure list corresponding to the woven network may be shown in Table 2 below.
  • 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.
  • 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.
  • the commands included in the node operation credential functional unit may be shown in Table 3 below.
  • a in the Accessibility column in Table 3 indicates that administrator (Admin) authority is required.
  • the client can be the configuration device side
  • 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.
  • Wireless Fidelity Wireless Fidelity
  • WiFi Wireless Fidelity
  • BLE Bluetooth Low Energy
  • Wireless Local Area Networks Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • 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.
  • NFC Near Field Communication
  • UWB Ultra Wideband
  • infrared network microwave communication network
  • millimeter wave communication network millimeter wave communication network
  • free space optical 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.
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • Vehicle to Vehicle V2V
  • vehicle networking Vehicle to everything, V2X
  • Fig. 2 is a schematic diagram of a wireless communication system applied in an embodiment of the present application.
  • the wireless communication system 100 may include: a first configuration device 110 , a second configuration device 120 and a terminal device 130 .
  • 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.
  • 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.
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the first configuration device 110 and/or the second configuration device 120 may also be a server.
  • the first configuration device 110 and the second configuration device 120 belong to different Fabrics.
  • 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.
  • 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 .
  • 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.
  • a smart home product such as Smart refrigerators, smart light bulbs, smart washing machines, smart TVs, smart wearables, and more.
  • 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.
  • 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.
  • the number of terminal devices 130 may be one or more, which is not limited in this application.
  • 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:
  • 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;
  • the terminal device receives the first information sent by the first configuration device; wherein the at least one device includes the terminal device.
  • the terminal device may be any one of the at least one device.
  • 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.
  • 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.
  • 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.
  • the terminal device determines that the first configuration device has administrator authority.
  • 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.
  • the first configuration device may send the first information to the at least one device in a multicast or broadcast manner.
  • 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.
  • 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.
  • the at least one device may be part or all of the devices in the smart home system.
  • 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.
  • the smart home system 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.
  • a CopySettingsFromFabric command is added to the node operation credential functional unit of the terminal device, as shown in Table 4.
  • 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.
  • 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.
  • 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.
  • the functional unit "scene” may include relevant information of Scenario 1 and Scenario 2.
  • 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.
  • 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,
  • 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 .
  • 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.
  • the functional unit "node operation credential” may include information about the node operation credential 1 and the node operation credential 3.
  • 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.
  • identity may also be expressed as “index”, which is not limited in this application.
  • 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.
  • 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.
  • Node Operational Certificate can also be called Node Operational Credentials, which is not limited in this application.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the M devices include: the terminal device and one or more devices associated with the terminal device through functional units.
  • the M devices include: the terminal device and one or more devices associated with the terminal device through a functional unit "group”.
  • the M devices include: the terminal device and one or more devices associated with the terminal device through a functional unit "proxy”.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the node identification structure corresponding to the terminal device in the node identification structure list 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.
  • TargetNodeID target node identification information
  • CurrentNodeID current node identification information
  • 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.
  • TargetFabricID target fabric ID
  • CurrentFabricID current fabric ID
  • the parameters contained in the first information may be as shown in Table 5 or Table 6.
  • 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.
  • 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.
  • 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.
  • the terminal device 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.
  • 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
  • the terminal device 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 terminal device after receiving the first information, 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.
  • the attributes or attribute fields of all private functional units include the identifier of the second weaving network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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 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 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;
  • the terminal device 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 terminal device after receiving the first information, 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • TargetStruct may be as shown in Table 12.
  • 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.
  • 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.
  • the type information corresponding to the target list is a target structure list
  • 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
  • one target structure in the target structure list includes at least the corresponding Identification information of the functional unit
  • 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;
  • 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
  • one target structure in the target structure list At least including the identification information of the corresponding device type.
  • the terminal device 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.
  • 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;
  • the terminal device 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 first configuration device acquires private configuration information for the at least one device in the second weave network.
  • the terminal device after receiving the first information, 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.
  • 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
  • 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.
  • 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.
  • NodeIdMap node identification mapping table
  • 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.
  • related settings of the terminal device after configuration are: FabricA: ⁇ FabricA,NOC1 ⁇ , ⁇ FabricA,ACL1 ⁇ , ⁇ FabricA,Group1 ⁇ , ⁇ FabricA,Binding1 ⁇ , ⁇ FabricA,Proxy1 ⁇ .
  • 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.
  • 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 ⁇ .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the first information (such as the CopySettingsFromFabric command) includes a fabric network ID and a node ID mapping table.
  • 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
  • the second configuration device can be the Admin1 APP controlled by the integrator.
  • 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.
  • the homeowner checks the Fabric to which the terminal device belongs on the Admin2 APP.
  • Admin2 APP sends an instruction to the terminal device to view the Fabrics attribute of the node operation credential functional unit.
  • the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.
  • 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 .
  • the terminal device After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.
  • 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.
  • FabricA 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.
  • 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.
  • the Admin2 APP can obtain all configurations made in FabricA for all devices in the smart home system.
  • the first information (such as the CopySettingsFromFabric command) includes a fabric network identifier, a node identifier mapping table, and a list of functional units.
  • 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
  • the second configuration device can be the Admin1 APP controlled by the integrator.
  • 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.
  • Admin2 APP sends an instruction to the terminal device to check the Fabrics attribute of the node operation credential functional unit.
  • the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.
  • 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
  • the functional unit list is used to indicate at least one functional unit that needs to be copied.
  • the terminal device After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.
  • 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.
  • 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.
  • 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 .
  • the first information (such as the CopySettingsFromFabric command) includes a fabric network identifier, a node identifier mapping table, and a target list.
  • 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
  • the second configuration device can be the Admin1 APP controlled by the integrator.
  • 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.
  • the Admin2 APP sends an instruction to the terminal device to view the Fabrics attribute of the node operation credential functional unit.
  • the terminal device returns to Fabrics, including the relevant information of FabricA and FabricB, which is presented to the homeowner by the Admin2 APP.
  • 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.
  • the terminal device After receiving the CopySettingsFromFabric command, the terminal device confirms that the sender Admin2 APP has Admin authority.
  • 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.
  • 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.
  • 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.
  • 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.
  • the configuration device in the first weaving network can conveniently copy the configured functional units of the second weaving network.
  • Fig. 8 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 includes:
  • a communication unit 310 configured to receive first information sent by the first configuration device
  • the first configuration device is a configuration device in the first weave network
  • the first information is used to generate private configuration information of the first weave network for at least one device
  • 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.
  • 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 private configuration information for the at least one device in the second woven network includes at least one of the following information:
  • the first information includes weaving network identification information, wherein the weaving network identification information is used to indicate the second weaving network.
  • the first information further includes a node identification mapping table
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 terminal device 300 further includes: a processing unit 320;
  • 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;
  • 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.
  • the attributes or attribute fields of all private functional units include identification information of the second weaving network.
  • the 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 first information also includes a list of functional units
  • the functional unit list is used to indicate at least one functional unit that needs to be copied.
  • 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 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 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 The private configuration information corresponding to the functional units indicated in the functional unit list in .
  • the terminal device 300 further includes: a processing unit 320;
  • 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;
  • 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.
  • 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.
  • 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 type information corresponding to the target list is a target structure list
  • 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
  • one target structure in the target structure list includes at least the corresponding Identification information of the functional unit
  • 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;
  • 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
  • one target structure in the target structure list At least including the identification information of the corresponding device type.
  • 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 The private configuration information corresponding to the functional units indicated in the target list in .
  • the terminal device 300 further includes: a processing unit 320;
  • 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;
  • 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.
  • the terminal device 300 also includes:
  • the processing unit 320 is configured to determine that the first configuration device has administrator authority.
  • the first information is a copy configuration CopySettingsFromFabric command by the fabric network.
  • 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.
  • terminal device 300 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.
  • the configuration device 400 includes:
  • a communication unit 410 configured to send first information to at least one device
  • the first configuration device is a configuration device in the first weave network
  • the first information is used to generate private configuration information of the first weave network for at least one device
  • 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.
  • 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 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.
  • the first information includes weaving network identification information, wherein the weaving network identification information is used to indicate the second weaving network.
  • the first information further includes a node identification mapping table
  • 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.
  • 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.
  • 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.
  • 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.
  • the first information also includes a list of functional units
  • the functional unit list is used to indicate at least one functional unit that needs to be copied.
  • 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 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 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.
  • 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 type information corresponding to the target list is a target structure list
  • 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
  • one target structure in the target structure list includes at least the corresponding Identification information of the functional unit
  • 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;
  • 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
  • one target structure in the target structure list At least including the identification information of the corresponding device type.
  • 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.
  • the communication unit 410 is further configured to acquire the private configuration information for the at least one device in the second woven network.
  • the first information is a copy configuration CopySettingsFromFabric command by the fabric network.
  • 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.
  • configuration device 400 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.
  • the communication device 500 may further include a memory 520 .
  • 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.
  • the memory 520 may be an independent device independent of the processor 510 , or may be integrated in the processor 510 .
  • 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.
  • 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.
  • 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.
  • 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.
  • the Let me repeat 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.
  • the device 600 may further include a memory 620 .
  • 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.
  • the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .
  • the device 600 may further include an input interface 630 .
  • 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.
  • the device 600 may further include an output interface 640 .
  • 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.
  • 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.
  • 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.
  • the repeat for the sake of brevity, the repeat.
  • the device mentioned in the embodiment of the present application may also be a chip.
  • 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 .
  • the terminal device 710 can be used to realize the corresponding functions realized by the terminal device in the above method
  • the first configuration device 720 can be used to realize the corresponding functions realized by the first configuration device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • 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.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • 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.
  • 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.
  • 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.
  • RAM Static Random Access Memory
  • SRAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • 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 Direct Memory Bus Random Access Memory
  • Direct Rambus RAM Direct Rambus RAM
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the configuration device in the embodiment of the present application.
  • the computer program 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.
  • the computer program can be applied to the terminal device in the embodiment of the present application.
  • the computer program 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.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • 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.
  • 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.
  • 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.
  • 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. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Facsimiles In General (AREA)

Abstract

Les modes de réalisation de la présente demande concernent des procédés et des dispositifs de communication sans fil, qui peuvent résoudre le problème posé par un réglage compliqué dans un processus de transfert d'autorisation d'un système domestique intelligent, et font en sorte, en fournissant une commande Copie de réglages d'un réseau de connexions, qu'un dispositif de réglage dans un premier réseau de connexions copie de manière pratique une unité fonctionnelle qui a été réglée par un second réseau de connexions. Un procédé de communication sans fil comprend l'étape suivante : un dispositif terminal reçoit des premières informations envoyées par un premier dispositif de réglage, le premier dispositif de réglage étant un dispositif de réglage dans un premier réseau de connexions, les premières informations étant utilisées pour générer des informations de réglage privées du premier réseau de connexions pour au moins un dispositif, les informations de réglage privées du premier réseau de connexions pour le ou les dispositifs étant obtenues par copie d'informations de réglage privées d'un second réseau de connexions pour le ou les dispositifs, et le ou les dispositifs comprenant le dispositif terminal.
PCT/CN2021/143806 2021-12-31 2021-12-31 Procédés et dispositifs de communication sans fil WO2023123400A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/143806 WO2023123400A1 (fr) 2021-12-31 2021-12-31 Procédés et dispositifs de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/143806 WO2023123400A1 (fr) 2021-12-31 2021-12-31 Procédés et dispositifs de communication sans fil

Publications (1)

Publication Number Publication Date
WO2023123400A1 true WO2023123400A1 (fr) 2023-07-06

Family

ID=86997276

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/143806 WO2023123400A1 (fr) 2021-12-31 2021-12-31 Procédés et dispositifs de communication sans fil

Country Status (1)

Country Link
WO (1) WO2023123400A1 (fr)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106211271A (zh) * 2016-06-30 2016-12-07 北京海尔广科数字技术有限公司 智能家居设备的入网方法、装置及智能家居设备
US20170324848A1 (en) * 2016-01-28 2017-11-09 Oracle International Corporation System and method for supporting shared multicast local identifiers (mild) ranges in a high performance computing environment
JP2017219930A (ja) * 2016-06-03 2017-12-14 日本電信電話株式会社 ＩｏＴデバイスシェアリング装置、ＩｏＴデバイスシェアリング方法およびプログラム
US20180219740A1 (en) * 2017-01-31 2018-08-02 Hewlett Packard Enterprise Development Lp Sharing policy and configuration information related to a configuration item
US20200336376A1 (en) * 2019-04-16 2020-10-22 Ciena Corporation Self-optimizing fabric architecture and self-assembling network
US20200344125A1 (en) * 2019-04-25 2020-10-29 Liqid Inc. Composed Computing Systems With Converged And Disaggregated Component Pool
CN113016001A (zh) * 2018-11-19 2021-06-22 三星电子株式会社 对基于内容的推荐进行预测的方法和系统
EP3846417A1 (fr) * 2019-12-31 2021-07-07 Bull Sas Procede de partage de fonctionnalites des iots et dispositif de partage
US20210385100A1 (en) * 2020-06-09 2021-12-09 Cisco Technology, Inc. Directed broadcast in network fabric

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170324848A1 (en) * 2016-01-28 2017-11-09 Oracle International Corporation System and method for supporting shared multicast local identifiers (mild) ranges in a high performance computing environment
JP2017219930A (ja) * 2016-06-03 2017-12-14 日本電信電話株式会社 ＩｏＴデバイスシェアリング装置、ＩｏＴデバイスシェアリング方法およびプログラム
CN106211271A (zh) * 2016-06-30 2016-12-07 北京海尔广科数字技术有限公司 智能家居设备的入网方法、装置及智能家居设备
US20180219740A1 (en) * 2017-01-31 2018-08-02 Hewlett Packard Enterprise Development Lp Sharing policy and configuration information related to a configuration item
CN113016001A (zh) * 2018-11-19 2021-06-22 三星电子株式会社 对基于内容的推荐进行预测的方法和系统
US20200336376A1 (en) * 2019-04-16 2020-10-22 Ciena Corporation Self-optimizing fabric architecture and self-assembling network
US20200344125A1 (en) * 2019-04-25 2020-10-29 Liqid Inc. Composed Computing Systems With Converged And Disaggregated Component Pool
EP3846417A1 (fr) * 2019-12-31 2021-07-07 Bull Sas Procede de partage de fonctionnalites des iots et dispositif de partage
US20210385100A1 (en) * 2020-06-09 2021-12-09 Cisco Technology, Inc. Directed broadcast in network fabric

Similar Documents

Publication Publication Date Title
US11936743B2 (en) Device management services based on restful messaging
US20220078616A1 (en) Method and apparatus for discussing digital certificate by esim terminal and server
US11362898B2 (en) Network policy configuration
JP7474302B2 (ja) 通信ネットワークにおける自動サービス登録
CN111787033B (zh) 基于权限的资源和服务发现
KR20210039721A (ko) 통신서비스를 위한 프로파일을 효율적으로 제공하는 방법 및 장치
US11989543B2 (en) Method for interoperating between bundle download process and eSIM profile download process by SSP terminal
US11206534B2 (en) Method and apparatus for managing bundles of smart secure platform
US20180212825A1 (en) Dynamic management of networks to facilitate storage device access
US11246174B2 (en) Methods and systems for connecting a wireless device to a wireless network
CN113711569A (zh) 建立物联网(iot)设备的云到云访问
KR102462366B1 (ko) eUICC 버전을 협상하는 방법 및 장치
WO2021142849A1 (fr) Procédé et appareil pour configurer, découvrir et joindre un domaine de sécurité, et dispositif électronique
WO2023123400A1 (fr) Procédés et dispositifs de communication sans fil
CN114286335A (zh) 一种服务器选择方法和装置
US11765226B2 (en) Method for provisioning internet of things device and internet of things device
WO2022042170A1 (fr) Dispositif de l'internet des objets et procédé d'autorisation associé
Schenk Matter and the Web of Things
WO2022261837A1 (fr) Procédé et appareil pour configurer un dispositif de l'internet des objets
WO2022061668A1 (fr) Procédé d'authentification d'accès à un dispositif bluetooth, ainsi que dispositif électronique et support de stockage
WO2022226807A1 (fr) Procédé et dispositif de communication sans fil
WO2022217561A1 (fr) Procédé et dispositif de communication sans fil
WO2022217602A1 (fr) Procédé permettant d'établir une relation de liaison de dispositifs, et dispositif
WO2022183381A1 (fr) Procédé et appareil de réglage de droit de contrôle d'accès par rapport à un dispositif, dispositif, et support de stockage
US20220377081A1 (en) Mutual device-to-device authentication method and device during device-to-device bundle or profile transfer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969747

Country of ref document: EP

Kind code of ref document: A1