Device de-duplication between dwelling networks

By generating and managing unique identifiers in the Matter network, the duplicate identifier problem of devices between different vendor ecosystems is solved, achieving seamless conversion of devices and improving user experience.

CN118975216APending Publication Date: 2024-11-15GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031341.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-05-10
Filing Date
2023-05-09
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In Matter networks, devices may generate duplicate identifiers when they move from one vendor's ecosystem to another, resulting in poor user experience and difficulty in achieving interoperability between multiple vendor devices and services.

Method used

By generating a unique identifier when detecting a factory reset on an electronic device, sending it to the first cloud service and forwarding it to the second cloud service, ensuring that the hub device forwards the identifier to the second cloud service, thereby repetitioning in the Matter network Identifier, ensuring that the device has a unique identity under multiple network paths.

Benefits of technology

The seamless transition of devices between different vendor ecosystems is achieved, avoiding the problem of users seeing multiple identifiers for a single device, improving user experience and device availability while maintaining existing settings and configurations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975216A_ABST
    Figure CN118975216A_ABST
Patent Text Reader

Abstract

Techniques and devices are described for device deduplication between residence networks for generating a unique identifier in which an electronic device detects a factory reset and generates the unique identifier in response to the detection. The electronic device sends the unique identifier to the first cloud service, the sending being valid to cause the first cloud service to forward the unique identifier to the second cloud service, and the electronic device sends the unique identifier to a hub device in the Matter network, the sending being valid to cause the hub device to forward the unique identifier to the second cloud service.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] The use of wireless networks to connect devices to each other and to cloud-based services is becoming increasingly popular for sensing environmental conditions, controlling equipment, and providing information and alerts to users of residential and commercial buildings. Many devices on wireless networks are designed to operate on battery power for extended periods of time, which limits the computing, user interface, and radio resources available in the devices.

[0002] This growing popularity has resulted in an ecosystem of multiple vendor-specific devices and network protocols that may not interoperate. To improve the user experience of these devices and networks, standards such as the Matter standard are being developed to provide interoperability between devices and services from multiple vendors. When transitioning a Matter-enabled device from one vendor ecosystem to another vendor's Matter network fabric, there are situations where multiple (duplicate) identifiers may result from the device's previous identifier and the device's Matter identifier. Summary of the invention

[0003] This summary is provided to introduce simplified concepts for device deduplication between residential networks, generally involving generating unique identifiers for network devices. The simplified concepts are further described below in the detailed description.

[0004] In various aspects, methods, devices, systems and methods for device deduplication between residential networks are described, wherein the methods, devices, systems and methods are used to generate a unique identifier, wherein an electronic device detects a factory reset and generates a unique identifier in response to the detection. The electronic device sends the unique identifier to a first cloud service, the sending being effective to cause the first cloud service to forward the unique identifier to a second cloud service, and the electronic device sends the unique identifier to a hub device in a Matter network, the sending being effective to cause the hub device to forward the unique identifier to the second cloud service.

[0005] The details of one or more implementations are set forth in the drawings and the following description. Other features and advantages will be apparent from the description and drawings, and from the claims. This summary is provided to introduce subject matter that is further described in the detailed description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Aspects of device deduplication between residential networks are described with reference to the following drawings. The same numbers are used throughout the drawings to reference similar features and components: Figure 1 An example network environment is shown in which various aspects of device deduplication between residential networks may be implemented. Figure 2An example home area network system is shown in which various aspects of device deduplication between home networks may be implemented. Figure 3a and Figure 3b An example environment is shown in which aspects of device deduplication between residential networks may be implemented. Figure 4 An example method of device deduplication between residential networks according to aspects of the techniques described herein is shown. Figure 5 An example environment is shown in which a home area network may be implemented in accordance with aspects of the techniques described herein. Figure 6 An example wireless network apparatus is shown that can be implemented in a residential area network environment in accordance with one or more aspects of the techniques described herein. Figure 7 An example system with example devices that can implement aspects of device deduplication between residential networks is shown. DETAILED DESCRIPTION

[0007] This document describes techniques and apparatus for simplifying the deduplication of device identifiers in a Matter network. A Matter network may include devices from a single manufacturer that also provides a cloud service that supports those devices, or a Matter network may include devices from one or more partners (partner device manufacturers). In addition to connecting to the manufacturer's cloud service and / or the Matter network, each partner may also provide a partner cloud service that supports its devices. Additionally, a partner cloud service may be integrated with one or more additional partner cloud services. Due to the connection to multiple services, a single device may have multiple identifiers across multiple services. Techniques are described for avoiding multiple identifiers for a single device in a Matter network by deduplicating identifiers at the cloud service that provides the Matter structure. Example Environment

[0008] Figure 1 An example network environment 100 is shown in which aspects of device deduplication between residential networks may be implemented. The network environment 100 includes a residential area network (HAN), such as the one referenced below. Figure 2 HAN 200 is depicted. The HAN includes wireless network devices 102 arranged around a structure 104, such as a house, and connected via one or more wireless and / or wired network technologies, as described below. The HAN includes a border router 106, which connects the HAN to an external network 108, such as the Internet, via a residential router or access point 110.

[0009] To provide users with access to functionality implemented using wireless network devices 102 in the HAN, cloud services 112 connect to the HAN via secure tunnels 114 through external networks 108 and access points 110 via border routers 106. Cloud services 112 facilitate communication between the HAN and Internet clients 116, such as apps on mobile devices, using application programming interfaces (APIs) 118. Cloud services 112 also manage a home graph that describes the connections and relationships between wireless network devices 102, elements of fabric 104, and users. As described in more detail below, cloud services 112 host controllers that coordinate and arbitrate home automation experiences.

[0010] The HAN may include one or more wireless network devices 102 that act as hubs 120. The hub 120 may be a general home automation hub, a network-connected speaker, or an application-specific hub such as a security hub, an energy management hub, an HVAC hub, etc. The functionality of the hub 120 may also be integrated into any wireless network device 102, such as a smart thermostat device or a border router 106. In addition to hosting controllers on the cloud service 112, controllers may also be hosted on any hub 120 in the structure 104, such as a border router 106. Controllers hosted on the cloud service 112 may be dynamically moved to a hub 120 in the structure 104, such as moving an HVAC zone controller to a newly installed smart thermostat.

[0011] Hosting functionality on the hub 120 in the fabric 104 may improve reliability when a user's Internet connection is unreliable, may reduce latency for operations that would typically have to connect to the cloud service 112 , and may satisfy system and regulatory constraints surrounding local access between wireless network devices 102 .

[0012] The wireless network devices 102 in the HAN may be from a single manufacturer that also provides the cloud service 112, or the HAN may include wireless network devices 102 from partners. These partners may also provide partner cloud services 122 that provide services related to their wireless network devices 102 through partner APIs 124. The partner cloud services 122 may alternatively or additionally provide services to the Internet clients 116 via the APIs 118, the cloud services 112, and the secure tunnels 114.

[0013] The network environment 100 can be implemented on various hosts such as battery powered microcontroller based devices, line powered devices, and servers hosting cloud services. The protocols operating in the wireless network devices 102 and the cloud services 112 provide a number of services that support the operation of the home automation experience in the distributed computing environment 100. These services include, but are not limited to, real-time distributed data management and subscription, command and response control, real-time event notification, historical data logging and preservation, cryptographically controlled security groups, time synchronization, network and service pairing, and software updates.

[0014] Figure 2 An example residential area network system (e.g., Matter network, Weave network, fabric network) in which various aspects of device deduplication between residential networks can be implemented is shown. A residential area network (HAN) 200 (Matter network 200) includes a wireless mesh network 202 (e.g., Thread network) and Wi-Fi devices 210. HAN 200 may also include wired network devices (e.g., Ethernet devices 214). Wireless mesh network 202 includes router 206 and end device 208. Router 206 and end device 208 each include a mesh network interface for communicating through mesh network 202. Router 206 receives and transmits packet data through the mesh network interface. Router 206 also routes traffic across mesh network 202. End device 208 is a device that can communicate using mesh network 202, but lacks the ability to route traffic in mesh network 202 other than simply forwarding to its parent router 206. For example, a battery-powered sensor is a type of end device 208. Each Wi-Fi device 210 includes a Wi-Fi network interface for communicating over a Wi-Fi network. The Wi-Fi devices 210 and / or Ethernet devices 214 may include home automation devices and devices including applications for controlling Matter devices (e.g., smartphones, tablets, network-connected speakers).

[0015] The ecosystem controller 216a (e.g., Matter controller) may include a border router 106, which in turn is included in the wireless mesh network 202. The border router 106 includes a mesh network interface for communicating through the mesh network 202 and a Wi-Fi network interface for communicating through the Wi-Fi network 204, or the border router 106 uses the Wi-Fi network interface of the ecosystem controller 216a to communicate through the Wi-Fi network 204. The border router 106 routes packets between devices in the wireless mesh network 202 and the access point 110, which can forward the packets to other devices in the HAN 200. The border router 106 also routes packets between devices in the mesh network 202 and external network nodes (e.g., cloud services 112) via an external network 108 such as the Internet through a residential router or access point 110.

[0016] The HAN 200 includes one or more ecosystem controllers 216 that provide an interface between devices from an ecosystem provider and the access point 110. For example, the ecosystem controller 216a provides an interface between the mesh network 202 (Thread network) and the access point 110. Optionally, the HAN 200 may include other ecosystem controllers such as the ecosystem controller 216b to interface with devices from other ecosystem providers. Additionally, other devices from another IoT network 218 (e.g., non-Matter-compatible ecosystem devices) may be connected to the access point 110 via a Matter gateway 220 that provides Matter-enabled applications with connectivity to devices in the other IoT network 218.

[0017] Devices in mesh network 202, Wi-Fi devices 210, Ethernet devices 214, ecosystem controller 216, and Matter gateway 220 communicate with each other using standard IP routing configurations over a transport protocol such as User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). Device deduplication between residential networks

[0018] Partners that connect devices via both the manufacturer's cloud service 112 application programming interface (API) and / or the manufacturer's hub 120 API can also make Matter connections available to these same devices, including via a Matter bridge (e.g., Matter Gateway 220). In order to connect to both the manufacturer's structure (the manufacturer's cloud service 112 and / or the manufacturer's hub 120) and the Matter network, partners must provide a universal identifier (ID) so that these partner devices can be identified and incorporated into the residence graph (residence device graph) in the manufacturer's structure. Additionally, the first partner cloud service can integrate / interface with additional partner cloud services to generate additional identifiers for devices in the residence network. Device deduplication ensures that the user does not see multiple separate devices of a single device, but instead sees a single device that potentially has multiple network paths for command execution, which are hidden from the user but increase the usability of device availability and preserve existing settings and configurations within the manufacturer's ecosystem.

[0019] In various aspects, the UniqueID attribute is included in the Matter BasicInformation Cluster (and the Bridged BasicInformation Cluster for devices behind a bridge) and is included via the Device Description in the SYNC Response of the cloud service 112 or the Device Descriptor in the Device Configuration Response of the hub 120. The fields in the Matter BasicInformation Cluster (and the Bridged BasicInformation Cluster for devices behind a bridge) are: If the manufacturer of the bridge (e.g., Matter Gateway 220) and the bridged device (e.g., a device in other IoT network 218) is the same, then matterOriginalVendorId and matterOriginalProductId are optional. matterUniqueId is a 32-character string, and the value of matterUniqueId is generated each time the device is factory reset. matterUniqueId must contain the same string as in Matter BasicCluster and Matter BridgedBasicCluster. matterOriginalVendorId and matterOriginalProductId must be used in bridged scenarios where the original VendorID and / or ProductID of the device is different from the VendorID and / or ProductID provided by the bridge. For example, where a bridge provides access to other Matter devices, the original VendorID and / or ProductID can be used to dedupe two views of the same device, where one or more views are provided through the bridge. When the bridged device (e.g., a device in the other IoT network 218) is not a Matter bridge or has the same VendorID and / or ProductID as the bridged view, the matterOriginalVendorId and matterOriginalProductId fields are not required. Additionally, the matterOriginalVendorId and matterOriginalProductId fields support deduplication when multiple partner cloud services are integrated with each other, and any of those cloud services can create additional identifiers for the device and transmit the additional device identifiers to the cloud service 112. For example, the cloud service 112 can use the matterOriginalVendorId and matterOriginalProductId fields to uniquely identify a device for which multiple partner cloud services 122 have presented multiple (different) identifiers to the cloud service 112.

[0020] Figure 3a and Figure 3b Example environments 300 and 350 are shown in which aspects of device deduplication between residential networks can be implemented. The examples shown include cloud service 112, partner cloud service 122, hub 120, and a Matter-enabled partner device 302. However, for clarity of illustration, environments 300 and 350 may include such as Figure 1 Any number of additional devices shown in .

[0021] exist Figure 3a , before joining the Matter network, a Matter-enabled partner device 302 may communicate with a partner cloud service 122 using an identifier assigned by a partner of the Matter-enabled partner device 302, shown as ID1 at 310. A user may control the Matter-enabled partner device 302 using the partner cloud service 122. Additionally, a user may control the Matter-enabled partner device 302 using the cloud service 112. The cloud service 112 may communicate with the partner cloud service 122 using ID1 of the Matter-enabled partner device 302 at 312, thereby enabling the user to control the Matter-enabled partner device 302 through services provided by the cloud service 112.

[0022] Matter enables a Matter-enabled partner device 302 to be controlled directly from the hub 120 at 314, thereby bypassing the cloud service. When a Matter-enabled partner device 302 joins the Matter network of the hub 120, a new identifier, shown as ID2, may be assigned to the Matter-enabled partner device 302. When the hub 120 communicates with the cloud service 112 about the newly joined Matter-enabled partner device 302 using ID2, the cloud service now has duplicate identifiers (ID1 and ID2) for the same Matter-enabled partner device 302 because the Matter network does not have any knowledge of the cloud service 112.

[0023] exist Figure 3b In order to solve the problem of duplicate identifiers when a Matter-enabled partner device 302 joins the Matter network of the hub 120, the Matter-enabled partner device 302 generates a matterUniqueId associated with the Matter-enabled partner device 302 and transmits the matterUniqueId to the hub 120 at 360. Optionally, a bridging device (e.g., a Matter gateway 220) can provide a connection between a wireless network device 102 that cannot be upgraded to support the Matter communication protocol and the hub device 120, wherein the bridging device transmits the matterUniqueId of the bridged device to the hub 120.

[0024] At 362, the Matter-enabled partner device 302 transmits the matterUniqueId to the partner cloud service 122. Then, at 364, the partner cloud service 122 transmits the matterUniqueId to the cloud service 112. By knowing the matterUniqueId associated with the Matter-enabled partner device 302, when the cloud service 112 receives a message about the matterUniqueId from the hub 120 at 366, the cloud service 112 can correctly associate the matterUniqueId with the Matter-enabled partner device 302. For example, the cloud service 112 maintains a residence graph (residence device graph) that associates devices with properties of the building structure in which the devices are located. The cloud service 112 uses the matterUniqueId to maintain a representation of the state of the Matter-enabled partner device 302 and to manage any operations associated with the Matter-enabled partner device 302. Optionally or additionally, when multiple partner cloud services are integrated with each other and any of these cloud services creates additional identifiers for a device and transmits the additional device identifiers to cloud service 112, the additional partner cloud services also provide matterOriginalVendorId and matterOriginalProductId fields to enable cloud service 112 to de-duplicate any additional duplicate device identifiers.

[0025] To avoid storing traceable data, the serial number of the Matter-enabled partner device 302 is not used for matterUniqueId. matterUniqueId is unique, generated by the Matter-enabled partner device 302, and rotated each time a factory reset is performed on the Matter-enabled partner device 302. The Matter-enabled partner device 302 may generate the matterUniqueId using a permanent device identifier (such as a media access control (MAC) address or any similar identifier that is uniquely assigned to the Matter-enabled partner device and programmed into the device during manufacturing or commissioning) and using cryptographic techniques such as generating a cryptographic hash of the permanent device identifier and a random seed value to produce the matterUniqueId. The resulting matterUniqueId is a 32-character string. To ensure that matterUniqueId is unique within the Matter network, matterUniqueId exists within a range of vendor identifiers (e.g., matterOriginalVendorId) and product identifiers (e.g., matterOriginalProductId). Example Method

[0026] refer to Figure 4 , an example method 400 is described in terms of one or more aspects of device deduplication between residential networks. In general, any of the components, modules, methods, and operations described herein may be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on a computer-readable storage memory located locally and / or remotely from a computer processing system, and implementations may include software applications, programs, functions, and the like. Alternatively or in addition, any of the functionality described herein may be performed at least in part by one or more hardware logic components, such as, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a system on a chip (SoC), a complex programmable logic device (CPLD), and the like. The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks may be combined or skipped in any order to implement a method or an alternative method.

[0027] Figure 4 An example method 400 for device deduplication between residential networks is shown, which generally relates to the generation of unique identifiers for network devices. At block 402, an electronic device detects a factory reset. For example, an electronic device (e.g., a Matter-enabled partner device 302, a wireless network device 102) detects a factory reset, such as receiving an indication to perform a factory reset. The indication to perform a factory reset can be an indication received through a physical interaction with the electronic device (e.g., a user pressing a reset switch), a command received over a wireless network (e.g., from an application on a user device), a firmware update received over a wireless network, starting a new Matter-enabled device being added to the HAN 200, etc.

[0028] At block 404, in response to detecting the factory reset, the electronic device generates a unique identifier for the electronic device. For example, in response to detecting the factory reset, the electronic device generates a unique identifier for the electronic device using a permanent identifier of the electronic device, such as by performing a cryptographic hash of the permanent identifier to generate matterUniqueId.

[0029] In block 406, the electronic device sends the unique identifier to the first cloud service, which is effective to cause the first cloud service to forward the unique identifier to the second cloud service. For example, the electronic device sends the unique identifier to the first cloud service (e.g., partner cloud service 122), which in turn forwards the unique identifier to the second cloud service (e.g., cloud service 111).

[0030] At box 408, the electronic device sends the unique identifier to a hub device in the Matter network, which is effective to cause the hub device to forward the unique identifier to the second cloud service. For example, the electronic device sends the unique identifier to a hub device (e.g., hub device 120), which in turn forwards the unique identifier to the second cloud service. By sending the unique identifier to the second cloud service, the second cloud service can de-duplicate multiple device identifiers received by the cloud service for a single electronic device and communicate with the electronic device across multiple network paths using a single unique identifier. Example Environment and Setup

[0031] Figure 5 shows which can be implemented as reference Figure 2 An example environment 500 of aspects of a home area network 200 and device deduplication between home networks is described. In general, the environment 500 includes a home area network (HAN) 200 implemented as part of a home or other type of structure, which has any number of wireless network devices configured to communicate in a wireless network. For example, the wireless network devices may include a thermostat 502, a hazard detector 504 (e.g., for smoke and / or carbon monoxide), a camera 506 (e.g., indoors and outdoors), a lighting unit 508 (e.g., indoors and outdoors), and any other type of wireless network device 510 implemented inside and / or outside a structure 512 (e.g., in a home environment). In this example, the wireless network devices may also include any of the previously described devices such as the border router 106, as well as any device implemented as a router device 206, an end device 208, an ecosystem controller 216, and / or a Matter gateway 220.

[0032] In environment 500, any number of wireless network devices may be implemented to wirelessly interconnect to communicate and interact with each other wirelessly. The wireless network devices are modular, intelligent, multi-sensing, network-connected devices that can be seamlessly integrated with each other and / or with a central server or cloud computing system to provide any of a variety of useful automation goals and implementations. Figure 6 Examples of wireless network devices that can be implemented as any of the devices described herein are shown and described.

[0033] In an implementation, the thermostat 502 may include a Nest® learning thermostat that detects ambient climate characteristics (e.g., temperature and / or humidity) in a residential environment and controls an HVAC system 514. The learning thermostat 502 and other network-connected devices "learn" by capturing the occupant settings of the device. For example, the thermostat learns preferred temperature set points in the morning and evening, as well as when the occupants of the structure go to sleep or wake up, and when the occupants are typically away or at home.

[0034] The hazard detector 504 may be implemented to detect the presence of a hazardous substance or a substance indicative of a hazardous substance (e.g., smoke, fire, or carbon monoxide). In an example of wireless interconnection, the hazard detector 504 may detect the presence of smoke, which indicates a fire in a structure, in which case the hazard detector that first detects the smoke may broadcast a low-power wake-up signal to all connected wireless network devices. Other hazard detectors 504 may then receive the broadcasted wake-up signal and initiate a high-power state for hazard detection and receive wireless communications of alarm messages. In addition, the lighting unit 508 may receive the broadcasted wake-up signal and activate in the area of ​​the detected hazard to illuminate and identify the problem area. In another example, the lighting unit 508 may be activated with one illuminated color to indicate a problem area or zone in a structure, such as for a detected fire or intrusion, and activated with a different illuminated color to indicate a safe zone and / or an escape route from the structure.

[0035] In various configurations, the wireless network device 510 may include an entrance interface device 516 that works in coordination with a network-connected door lock system 518 and detects and responds to a person approaching or leaving a location such as an exterior door of a structure 512. The entrance interface device 516 may interact with other wireless network devices based on whether a person approaches or enters a smart home environment. The entrance interface device 516 may control doorbell functionality, announce the approach or departure of a person via audio or visual means, and control settings on a security system, such as to activate or deactivate a security system when a resident enters or exits. The wireless network device 510 may also include other sensors and detectors, such as to detect ambient lighting conditions, detect room occupancy status (e.g., using an occupancy sensor 520), and control the power and / or dimming state of one or more lights. In some cases, sensors and / or detectors may also control the power state or speed of a fan such as a ceiling fan 522. In addition, sensors and / or detectors may detect occupancy in a room or enclosure and control the power supply to an electrical outlet or device 524, such as if the room or structure is not occupied.

[0036] Wireless network devices 510 may also include connected appliances and / or controlled systems 526, such as refrigerators, stoves and ovens, washers, dryers, air conditioners, pool heaters 528, irrigation systems 530, security systems 532, etc., and other electronic and computing devices, such as televisions, network-connected televisions, network-connected media streaming devices, entertainment systems, computers, intercom systems, garage door openers 534, ceiling fans 522, control panels 536, etc. When plugged into a power source, the appliances, devices, or systems may announce themselves to a home area network as described above and may automatically integrate with controls and devices of a home area network, such as in a residence. It is noted that wireless network devices 510 may include devices physically located outside of a structure but within wireless communication range, such as devices controlling a pool heater 528 or an irrigation system 530.

[0037] As described above, the mesh network 202 includes a border router 106 that interfaces to communicate with an external network outside the mesh network 202. The border router 106 is connected to an access point 110, which is connected to a communication network 108 such as the Internet. A cloud service 112 connected via the communication network 108 provides services related to and / or using devices within the HAN 200. By way of example, the cloud service 112 may include applications for connecting end-user devices 538 such as smart phones, tablets, etc. to devices in a residence area network, processing data acquired in the HAN 200 and presenting the data to end users, linking one or more devices in the HAN 200 to a user account of the cloud service 112, configuring and updating devices in the HAN 200, etc. For example, a user may use a network-connected computer or a portable device such as a mobile phone or tablet device to control a thermostat 502 and other wireless network devices in a residence environment. In addition, the wireless network devices may communicate information to any central server or cloud computing system via the border router 106, the ecosystem controller 216, the Matter gateway 220, and / or the access point 110. Data communications may be performed using any of a variety of custom or standard wireless protocols (e.g., Wi-Fi, ZigBee for low power, 6LoWPAN, Thread, BLE, Matter, etc.) and / or by using any of a variety of custom or standard wired protocols (Ethernet, HomePlug, etc.).

[0038] Any of the wireless network devices in the HAN 200 can be used as a low power and communication node to create the HAN 200 in a residential environment. Individual low power nodes of the network can periodically send out messages about what they are sensing, and other low power nodes in the environment - in addition to sending out their own messages - can repeat the message, thereby transmitting the message from one node to another node (i.e., from one device to another) throughout the residential area network. The wireless network devices can be implemented to save power, especially when powered by batteries, so as to receive messages using low power communication protocols, convert messages to other communication protocols, and send the converted messages to other nodes and / or a central server or cloud computing system. For example, an occupancy and / or ambient light sensor can detect occupants in a room and measure ambient light, and activate a light source when the ambient light sensor 540 detects that the room is dark and when the occupancy sensor 520 detects that someone is in the room. In addition, the sensor may include a low-power wireless communication chip (e.g., an IEEE 802.15.4 chip, a Thread chip, a ZigBee chip) that periodically sends out messages about the occupancy of the room and the amount of light in the room, including instant messages that coincide with the occupancy sensor detecting the presence of a person in the room. As described above, these messages may be sent wirelessly from node to node (i.e., network-connected device to network-connected device) within a residential environment using a home area network, as well as to a central server or cloud computing system via the Internet.

[0039] In other configurations, various wireless network devices in the wireless network device can act as "tripwires" for the alarm system in the residential environment. For example, in the case where the criminal circumvents the detection of the alarm sensors located at the windows, doors and other entry points of the structure or environment, the alarm can still be triggered by receiving occupancy, motion, heat, sound, etc. messages from one or more mesh nodes in the low-power mesh node in the residential area network. In other implementations, the residential area network can be used to automatically turn on and off the lighting unit 508 when the personnel are transferred from room to room in the structure. For example, the wireless network device can detect the movement of the personnel through the structure and transmit corresponding messages via the nodes of the residential area network. Using the message indicating which rooms are occupied, other wireless network devices that receive the message can be activated and / or deactivated accordingly. As described above, the residential area network can also be used to provide exit lighting in an emergency, such as by turning on the appropriate lighting unit 508 leading to the safe exit. The lighting unit 508 can also be turned on to indicate the direction in which the personnel should travel along the exit route to safely leave the structure.

[0040] Various wireless network devices may also be implemented to integrate and communicate with wearable computing devices 542, such as may be used to identify and locate occupants of a structure and adjust temperature, lighting, sound systems accordingly, etc. In other implementations, RFID sensing (e.g., a person with an RFID bracelet, necklace, or keychain), synthetic vision technology (e.g., a video camera and facial recognition processor), audio technology (e.g., voice, sound pattern, vibration pattern recognition), ultrasonic sensing / imaging technology, and infrared or near field communication (NFC) technology (e.g., a person wearing an infrared or NFC-enabled smartphone), and rule-based inference engines or artificial intelligence technology to draw useful conclusions about the location of occupants in a structure or environment from the sensed information.

[0041] In other implementations, personal comfort zone networks, personal health zone networks, personal safety zone networks, and / or other such human-oriented functionality of service robots can be enhanced by logical integration with other wireless network devices and sensors in the environment based on rule-based inference techniques or artificial intelligence techniques to achieve better performance of these functionalities. In an example involving a personal health area, the system can detect whether a family pet is moving toward the current location of the resident (e.g., using any of the wireless network devices and sensors, as well as rule-based inference and artificial intelligence techniques. Similarly, a hazard detector service robot can be notified that the temperature and humidity levels in the kitchen are rising, and any small increase in the ambient smoke level will most likely be due to cooking activities rather than due to a real dangerous condition. The hazard detection threshold, such as the smoke detection threshold, can be temporarily increased. Any service robot configured for any type of monitoring, detection, and / or service can be implemented as a mesh node device on a residential area network, conforming to a wireless interconnection protocol for communicating on the residential area network.

[0042] The wireless network device 510 may also include a network-connected alarm clock 544 for each of the individual occupants of the structure in the residential environment. For example, the occupant may customize and set the alarm device for a wake-up time, such as for the next day or the next week. Artificial intelligence may be used to consider the occupant's reaction to the alarm when it sounds, and to make inferences about preferred sleep patterns over time. Individual occupants may then be tracked in the residential area network based on a person's unique signature, which is determined based on data obtained from sensors located in the wireless network device, such as sensors including ultrasonic sensors, passive IR sensors, etc. The occupant's unique signature may be based on a combination of movement patterns, voice, height, size, etc., as well as using facial recognition technology.

[0043] In an example of wireless interconnection, an individual's wake-up time can be associated with a thermostat 502 to control the HVAC system in an efficient manner to preheat or cool the structure to the desired sleeping and waking temperature settings. Preferred settings can be learned over time, such as by capturing the temperature set in the thermostat before the person falls asleep and when they wake up. The collected data can also include biometric indications of the person, such as breathing patterns, heart rate, movement, etc., based on which inferences are made in combination with data indicating when the person actually wakes up. Other wireless network devices can use this data to provide other automation goals, such as adjusting the thermostat 502 to preheat or cool the environment to the desired setting and turning lights 508 on or off.

[0044] In implementations, the wireless network devices may also be used for sound, vibration, and / or motion sensing, such as to detect running water and determine inferences about water usage in a residential environment based on algorithms and mapping of water usage and consumption. This may be used to determine the characteristics or fingerprints of each water source in a residence, and is also referred to as "audio fingerprint water usage." Similarly, the wireless network devices may be used to detect subtle sounds, vibrations, and / or motion of unwanted pests, such as mice and other rodents, as well as termites, cockroaches, and other insects. The system may then notify the occupants of suspected pests in the environment, such as with a warning message to help promote early detection and prevention.

[0045] Environment 500 may include one or more wireless network devices that act as a hub 546. Hub 546 may be a general home automation hub, or an application-specific hub such as a security hub, energy management hub, HVAC hub, etc. The functionality of hub 546 may also be integrated into any wireless network device such as a network-connected thermostat device or edge router 106. Hosting functionality on hub 546 in fabric 512 may improve reliability when a user's Internet connection is unreliable, may reduce latency for operations that would typically have to connect to cloud services 112, and may satisfy system and regulatory constraints around local access between wireless network devices.

[0046] Additionally, the example environment 500 includes a network-connected speaker 548. The network-connected speaker 548 provides voice assistant services, including providing voice control of network-connected devices. The functionality of the hub 546 may be hosted in the network-connected speaker 548. The network-connected speaker 548 may be configured to communicate via the wireless mesh network 202, the Wi-Fi network 204, or both.

[0047] Figure 6An example wireless network device 600 is shown, which can be implemented as any of the wireless network devices in a residential area network (Thread network, Matter network) according to one or more aspects of device deduplication between residential networks as described herein. The device 600 can be integrated with electronic circuit systems, microprocessors, memories, input-output (I / O) logic controls, communication interfaces and components, and other hardware, firmware, and / or software to implement the device in a residential area network. In addition, as described in reference Figure 7 As further described by the illustrated example apparatus, wireless network apparatus 600 may be implemented using a variety of components, such as any number and combination of different components.

[0048] In this example, the wireless network device 600 includes a low-power microprocessor 602 and a high-power microprocessor 604 (e.g., a microcontroller or a digital signal processor) that process executable instructions. The device also includes an input-output (I / O) logic control 606 (e.g., to include an electronic circuit system). The microprocessor may include components of an integrated circuit, a programmable logic device, a logic device formed using one or more semiconductors, and other implementations in silicon and / or hardware, such as a processor and memory system implemented as a system on a chip (SoC). Alternatively or additionally, the device may be implemented with any one or a combination of software, hardware, firmware, or fixed logic circuit systems that can be implemented with processing and control circuits. The low-power microprocessor 602 and the high-power microprocessor 604 may also support one or more different device functionalities of the device. For example, the high-power microprocessor 604 may perform computationally intensive operations, while the low-power microprocessor 602 may manage less complex processes such as detecting danger or temperature from one or more sensors 608. The low-power processor 602 may also wake up or initialize the high-power processor 604 to perform computationally intensive processes.

[0049] One or more sensors 608 may be implemented to detect various properties, such as acceleration, temperature, humidity, water, power supply, proximity, external motion, device motion, sound signals, ultrasonic signals, light signals, fire, smoke, carbon monoxide, global positioning satellite (GPS) signals, radio frequency (RF), other electromagnetic signals or fields, etc. Thus, the sensors 608 may include temperature sensors, humidity sensors, hazard-related sensors, safety sensors, other environmental sensors, accelerometers, microphones, optical sensors up to and including any one or combination of cameras (e.g., charge coupled devices or video cameras, active or passive radiation sensors, GPS receivers, and radio frequency identification detectors. In implementations, the wireless network device 600 may include one or more primary sensors, and one or more secondary sensors, for example, the primary sensors sense data that is most important to the core operation of the device (e.g., sensing temperature in a thermostat or sensing smoke in a smoke detector), while the secondary sensors may sense other types of data (e.g., motion, light, or sound) that may be used for energy saving or automation goals.

[0050] The wireless network device 600 includes a memory device controller 610 and a memory device 612, such as any type of non-volatile memory and / or other suitable electronic data storage device. The wireless network device 600 may also include various firmware and / or software, such as an operating system 614 maintained as computer executable instructions by the memory and executed by the microprocessor. The device software may also include an identifier generation application 616 that implements aspects of device deduplication between residential networks. The wireless network device 600 also includes a device interface 618 for interfacing with another device or peripheral component, and includes an integrated data bus 620 that couples the various components of the wireless network device for data communication between the components. The data bus in the wireless network device may also be implemented as any one or combination of different bus structures and / or bus architectures.

[0051] Device interface 618 can receive input from the user and / or provide information to the user (e.g., as a user interface), and the received input can be used to determine settings. Device interface 618 can also include mechanical or virtual components that respond to user input. For example, the user can mechanically move a sliding or rotatable component, or can detect motion along a touch pad, and such motion can correspond to the setting adjustment of the device. Physical and virtual movable user interface components can allow the user to set settings along a part of an obvious continuum. Device interface 618 can also receive input from any number of peripheral devices such as buttons, keyboards, switches, microphones, and imagers (e.g., camera devices).

[0052] The wireless network device 600 may include a network interface 622, such as a residential area network interface for communicating with other wireless network devices in a residential area network, and an external network interface for communicating over a network such as the Internet. The wireless network device 600 also includes a wireless radio system 624 for wirelessly communicating with other wireless network devices via the residential area network interface and for a plurality of different wireless communication systems. The wireless radio system 624 may include Wi-Fi, Bluetooth, TM , mobile broadband, BLE and / or point-to-point IEEE 802.15.4. Each of the different radio systems may include a radio device, antenna, and chipset implemented for a specific wireless communication technology. The wireless network device 600 also includes a power supply 626, such as a battery and / or connecting the device to line voltage. An AC power source may also be used to charge the battery of the device.

[0053] Figure 7 An example system 700 is shown that includes an example apparatus 702 that can be implemented to implement the above-mentioned Figures 1 to 6 Any of the wireless network devices of the described aspects of device deduplication between residence networks. Example device 702 can be any type of computing device, client device, mobile phone, tablet computer, communication, entertainment, gaming, media playback and / or other type of device. In addition, example device 702 can be implemented as any other type of wireless network device configured to communicate on a residence area network, such as a thermostat, hazard detector, camera, lighting unit, commissioning device, router, border router, join router, join device, terminal device, leader device, access point and / or other wireless network device.

[0054] The device 702 includes a communication device 704 that enables wired and / or wireless communication of device data 706, such as data transmitted between devices in a residential area network, data being received, data scheduled for broadcast, data packets of data, data synchronized between devices, etc. The device data may include any type of communication data, as well as audio, video, and / or image data generated by an application executed on the device. The communication device 704 may also include a transceiver for cellular telephone communications and / or network data communications.

[0055] The device 702 also includes an input / output (I / O) interface 708, such as a data network interface that provides a connection and / or communication link between the device, a data network (e.g., a home area network, an external network, etc.), and other devices. The I / O interface can be used to couple the device to any type of component, peripheral, and / or accessory device. The I / O interface also includes a data input port, via which any type of data, media content, and / or input can be received, such as user input to the device, as well as any type of communication data, and audio, video, and / or image data received from any content and / or data source.

[0056] The device 702 includes a processing system 710, which can be implemented at least partially in hardware, such as with any type of microprocessor, controller, etc. that processes executable instructions. The processing system can include components of integrated circuits, programmable logic devices, logic devices formed using one or more semiconductors, and other implementations in silicon and / or hardware, such as a processor and memory system implemented as a system on a chip (SoC). Alternatively or additionally, the device can be implemented with any one or a combination of software, hardware, firmware, or fixed logic circuit systems that can be implemented with processing and control circuits. The device 702 can also include any type of system bus or other data and command transmission system that couples various components within the device. The system bus can include any one or a combination of different bus structures and architectures as well as control lines and data lines.

[0057] The device 702 also includes computer-readable storage memory 712 (computer-readable storage medium 712), such as a data storage device that is accessible by a computing device and provides persistent storage of data and executable instructions (e.g., software applications, modules, programs, functions, etc.). The computer-readable storage memory described herein does not include propagating signals. Examples of computer-readable storage memory include volatile and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data storage that maintains data for access by a computing device. The computer-readable storage memory may include various implementations of random access memory (RAM), read-only memory (ROM), flash memory, and other types of storage memory in various memory device configurations.

[0058] The computer-readable storage memory 712 provides storage for device data 706 and various device applications 714, such as an operating system maintained as a software application with the computer-readable storage memory and executed by the processing system 710. The device applications may also include a device manager, such as any form of control application, software application, signal processing and control module, native code for a particular device, hardware abstraction layer for a particular device, etc. In this example, the device applications also include an identifier generation application 716 that implements aspects of a generic interface for multicast address subscriptions, such as when the example device 702 is implemented as any wireless network device described herein.

[0059] The device 702 also includes an audio and / or video system 718 that generates audio data for an audio device 720 and / or generates display data for a display device 722. The audio device and / or display device include any device that processes, displays, and / or otherwise renders audio, video, display, and / or image data such as image content of a digital photo. In an implementation, the audio device and / or display device are integrated components of the example device 702. Alternatively, the audio device and / or display device are external peripheral components of the example device. In various aspects, at least part of the technology described for the general interface for multicast address subscriptions can be implemented in a distributed system, such as in a platform 726 through a "cloud" 724. The cloud 724 includes and / or represents a platform 726 of services 728 and / or resources 730.

[0060] The platform 726 abstracts the underlying functionality of hardware such as server devices (e.g., included in services 728) and / or software resources (e.g., included as resources 730), and connects the example device 702 to other devices, servers, etc. The resources 730 may also include applications and / or data that can be utilized when performing computer processing on a server remote from the example device 702. Additionally, the services 728 and / or resources 730 may facilitate subscriber network services such as over the Internet, a cellular network, or a Wi-Fi network. The platform 726 may also be used to abstract and extend resources to meet needs for the resources 730 implemented via the platform, such as in terms of interconnected devices in which the functionality is distributed throughout the system 700. For example, the functionality may be implemented in part at the example device 702, and via the platform 726 that abstracts the functionality of the cloud 724.

[0061] Some examples are described below: Example 1: A method for generating a unique identifier by an electronic device, the method comprising: detecting a factory reset by the electronic device; responsive to said detecting, generating said unique identifier; sending the unique identifier to a first cloud service, the sending being effective to cause the first cloud service to forward the unique identifier to a second cloud service; and The unique identifier is sent to a hub device in the Matter network, the sending being effective to cause the hub device to forward the unique identifier to the second cloud service. Example 2: The method of Example 1, wherein performing a factory reset comprises: Join the Matter network including the hub device. Example 3. The method of Example 1 or Example 2, wherein the unique identifier is randomly rotated each time the electronic device performs a factory reset. Example 4: The method of any of the preceding examples, wherein generating the unique identifier comprises: The unique identifier is generated using a permanent identifier of the electronic device. Example 5: The method of Example 4, wherein generating the unique identifier using the permanent identifier of the electronic device comprises: A cryptographic hash of the permanent identifier and the random seed value is generated. Example 6: A method as described in any of the preceding examples, wherein sending the unique identifier to the first cloud service and sending the unique identifier to a hub device in a Matter network enables the second cloud service to de-dupe multiple device identifiers to uniquely identify the electronic device across multiple network connections using the unique identifier. Example 7: The method of any of the preceding examples, wherein sending the unique identifier to the hub device in the Matter network comprises: The unique identifier is sent to the hub device in the Matter network via a bridge device. Example 8: A method as described in any of the preceding examples, wherein the unique identifier is a 32-character string. Example 9: The method of any of the preceding examples, wherein the unique identifier is unique within a range of vendor identifiers and product identifiers of the electronic device. Example 10: A method as described in any of the preceding examples, wherein the unique identifier is matterUniqueld. Example 11: The method of Example 10, wherein the matterUniqueId is included in a Matter basic information cluster. Example 12: The method of Example 11, wherein the Matter basic information cluster includes: matterOriginalVendorId of the electronic device; and The matterOriginalProductId of the electronic device. Example 13: An electronic device comprising: Wireless network interface; Processor; and A computer-readable storage medium comprising instructions that, in response to being executed by the processor, direct the electronic device to perform a method as described in any one of Examples 1 to 12. Example 14: The electronic device of Example 13, wherein the electronic device is: Thermostat; Hazard detectors; camera; Lighting units; Inlet interface; Door locks; Occupancy sensors; ceiling fan; Electrical sockets; Safety sensors; Security hub; Garage door openers; control Panel; Border routers; Central; Network-connected speakers; television; Internet-connected TV; A network-connected media streaming device; or Any combination of them. Example 15: A computer-readable storage medium comprising instructions, which, in response to being executed by a processor, are used to direct a device to perform a method as described in any one of Examples 1 to 12.

[0062] Although device deduplication between residential networks has been described in language specific to features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, specific features and methods are disclosed as example implementations of device deduplication between residential networks, and other equivalent features and methods are intended to be within the scope of the appended claims. Additionally, various different aspects are described, and it should be understood that each described aspect may be implemented independently or in combination with one or more other described aspects.

Claims

1. A method for generating a unique identifier by an electronic device, the method comprising: detecting a factory reset by the electronic device; responsive to said detecting, generating said unique identifier; sending the unique identifier to a first cloud service, the sending being effective to cause the first cloud service to forward the unique identifier to a second cloud service; as well as The unique identifier is sent to a hub device in the Matter network, the sending being effective to cause the hub device to forward the unique identifier to the second cloud service.

2. The method of claim 1 , wherein performing the factory reset comprises: Join the Matter network including the hub device.

3. The method of claim 1 or claim 2, wherein the unique identifier is randomly rotated each time the electronic device performs a factory reset.

4. The method of any one of the preceding claims, wherein said generating said unique identifier comprises: The unique identifier is generated using a permanent identifier of the electronic device.

5. The method of claim 4, wherein generating the unique identifier using the permanent identifier of the electronic device comprises: A cryptographic hash of the permanent identifier and the random seed value is generated.

6. A method as described in any of the preceding claims, wherein sending the unique identifier to the first cloud service and sending the unique identifier to a hub device in a Matter network enables the second cloud service to de-duplicate multiple device identifiers to uniquely identify the electronic device across multiple network connections using the unique identifier.

7. The method of any one of the preceding claims, wherein sending the unique identifier to the hub device in the Matter network comprises: The unique identifier is sent to the hub device in the Matter network via a bridge device.

8. A method as claimed in any preceding claim, wherein the unique identifier is a 32-character string.

9. A method as claimed in any preceding claim, wherein the unique identifier is unique within a range of vendor identifiers and product identifiers of the electronic device.

10. A method as claimed in any preceding claim, wherein the unique identifier is matterUniqueld. The method of claim 10 , wherein the matterUniqueId is included in a Matter basic information cluster.

12. The method of claim 11, wherein the Matter basic information cluster comprises: matterOriginalVendorId of the electronic device; and The matterOriginalProductId of the electronic device.

13. An electronic device comprising: Wireless network interface; processor; as well as A computer-readable storage medium comprising instructions, wherein the instructions, in response to being executed by the processor, direct the electronic device to perform the method as claimed in any one of claims 1 to 12.

14. The electronic device according to claim 13, wherein the electronic device is: Thermostat; Hazard detectors; camera; Lighting units; Inlet interface; Door locks; Occupancy sensors; ceiling fan; Electrical sockets; Safety sensors; Security hub; Garage door openers; control Panel; Border routers; Central; Network-connected speakers; television; Internet-connected TV; A network-connected media streaming device; or Any combination of them.

15. A computer-readable storage medium comprising instructions, which in response to being executed by a processor are used to direct a device to perform the method of any one of claims 1 to 12.