Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
SYSTEMS AND METHODS FOR CONFIGURATION AND CONTROL OF HOME NETWORK DEVICES
Document Type and Number:
WIPO Patent Application WO/2018/187625
Kind Code:
A1
Abstract:
Systems and method for configuration and control of network nodes is disclosed. A control node can collect information from a network node. The collected information can be used to determine a region associated with the network node. The control node can correlate human-related activities to the network node using the collected information. A moment can be created based on the correlation. User-settings of the network node can be adjusted using the created moment.

Inventors:
LAMARCHE DAVID (CA)
SALISBURY BRIAN (US)
Application Number:
PCT/US2018/026331
Publication Date:
October 11, 2018
Filing Date:
April 05, 2018
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
SCHNEIDER ELECTRIC BUILDINGS (US)
International Classes:
H04L12/24; H04W4/02
Foreign References:
US20090106542A12009-04-23
US20100141602A12010-06-10
US8655307B12014-02-18
Attorney, Agent or Firm:
WILSON, Susanne (US)
Download PDF:
Claims:
IN THE CLAIMS

1 . A network system, the network system comprising:

a network node; and

a control node coupled to the network node, the control node being configured to:

collect information from the network node, the collected information being used to determine a region associated with the network node,

correlate, using the first information, human-related activities to the network node, and

create a moment based on the correlation, the created moment being used to adjust user-settings of the network node.

2. The system of claim 1 , wherein the collected information further includes a unique identifier of the network, the unique identifier being at least one of a registration code, label, and/or value.

3. The system of claim 1 , wherein the control node includes a user interface.

4. The system of claim 3, wherein the control node is further configured to: prompt, at the user interface, an end-user to select the region from a digital, topographic study, the topographic study.

6. The system of claim 1 , further comprising: a moments module, the moments module being used to create the moment, wherein the moments module is hosted at and/or distributed among the network node and/or control node.

7. A method for control at a network node, the method comprising:

collecting, at a control node, information from a network node, the collected information being used to determine a region associated with the network node;

correlating, at the control node, using the information, human-related activities to the network node; and

creating, at the control node, a moment based on the correlation, the created moment being used to adjust user-settings of the network node.

8. A control system, the control system comprising:

a moments module;

a network node, the network node including an identity; and

a control node logically coupled to the network node, the control node configured to:

receive, at an interface, a region selection from an end-user, the region being selected from a topographic study of an environment displayed at the interface to the end-user,

determine that the network node is installed in the selected region; generate, at the moments module, a moment based on the network node identity, the selected region, and/or common activities of the environment; and

integrate the network node to the generated moment, the integration being used to control the network node.

Description:
SYSTEMS AND METHODS FOR CONFIGURATION AND CONTROL OF

HOME NETWORK DEVICES

CROSS-REFERENCE TO RELATED APPLICATIONS

[001] This application claims priority to and benefit from U.S. Provisional Application No. 62/481 ,971 , filed April 5, 2017, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[002] The present disclosure is generally directed to systems and methods of communication and configuration of consumer electronics. More particularly, aspects of the present disclosure relate to systems and methods for configuring and controlling home automation network nodes and systems.

INTRODUCTION

[003] The Internet of Things (loT) promises to communicatively interconnect automation network nodes and/or systems together on a massive scale. Such amalgamation creates unique opportunities for complex interaction and/or collaboration among loT network nodes and/or systems. For example, these interactions and/or collaborations can be used to complete pre-defined automation tasks, which automation tasks can be defined or manipulated based on context and environment. The pre-defined automation tasks can range from sensing and/or monitoring of an environmental characteristic (e.g., temperature and/or humidity of a room, etc.) to controlling and/or optimizing a facility and/or home automation network to attain an objective such as a desired energy management strategy. [004] In a facility and/or home automation network, interconnected automation network nodes and/or systems can include various heterogeneous and/or homogenous network elements (e.g., software, hardware, etc.). Using loT, these network elements can be used to facilitate the pre-defined automation tasks (e.g., adjusting a thermostat, etc.) for an end-user. But, due to the complexity of the interactions and/or collaborations among the network elements, the automation network nodes and/or systems may require repeated

configuration and control, in concert, which can prove problematic. In other words, efficiently configuring and controlling such interactions and/or

collaborations among the automation network nodes (including the network elements) and/or systems to manage either a facility or a home automation network becomes a serious challenge.

SUMMARY

[005] The present disclosure solves one or more of the above-mentioned problems and/or demonstrates one or more of the above-mentioned desirable features. Other features and/or advantages may become apparent from the description that follows.

[006] In accordance with at least one exemplary embodiment, the present disclosure contemplates a method for control at a network node.

Information can be collected from a network node at a control node. The collected information can be used to determine a region associated with the network node. Using the information, the control node can correlate human- related activities to the network node. A moment can be created at the control node based on the correlation. The moment can be used to adjust user-settings of the network node.

[007] In accordance with at least another exemplary embodiment, the present disclosure contemplates a network system including a network node and a control node. The network node can be coupled to the control node. The control node can collect information from the network node, the collected information being used to determine a region associated with the network node. Further, the control node can correlate human-related activities to the network node using the collected information. A moment can be created based on the correlation. The created moment can be used to adjust user-settings of the network node.

[008] In accordance with at least another exemplary embodiment, the present disclosure contemplates a control system including a moments module, network node, and control node. The network node can include an identity and is logically coupled to the control node. At an interface, the control node can receive a region selection from an end-user. The region can be selected from a topographic study of an environment displayed at the interface to the end-user. Further, the control node can determine that the network node is installed in the selected region. Using the network node identity, the selected region, and/or common activities, the control node can generate a moment at the moments module. The control node can integrate the network node to the generated moment, the integration being used to control the network node. [009] Additional objects and advantages will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the present disclosure and/or claims. At least some of these objects and advantages may be realized and attained by the elements and combinations particularly pointed out in the appended claims.

[010] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as disclosed or claimed. The claims should be entitled to their full breadth of scope, including equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[011] The present disclosure can be understood from the following detailed description either alone or together with the accompanying drawings. The drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments of the present disclosure and, together with the description, explain certain principles and operation. In the drawings,

[012] FIG. 1 A is a schematic view of an exemplary automation network system configured to enable configuration and control at a network node in accordance with an exemplary embodiment of the present disclosure;

[013] FIG. 1 B is a schematic diagram that shows a portion of the exemplary automation network system of FIG. 1 A in accordance with an exemplary embodiment of the present disclosure; [014] FIG. 2 is a flow diagram depicting a method for configuration and control of a facility and/or home automation network at a network node in accordance with an exemplary embodiment of the present disclosure;

[015] FIG. 3 is a flow chart diagram that shows a portion (i.e., a moment creation engine) of the exemplary method of FIG. 2 in accordance with an exemplary embodiment of the present disclosure;

[016] FIG. 4 is a flow chart diagram that shows another portion (i.e., assignment of moments) of the exemplary method of FIG. 2 in accordance with an exemplary embodiment of the present disclosure;

[017] FIG. 5A is another flow diagram depicting a method for

configuration and control of a facility and/or home automation network at a network node in accordance with an exemplary embodiment of the present disclosure;

[018] FIG. 5B is a flow chart diagram that shows a portion (i.e., adjustment of a moments library) of the exemplary method of FIG. 5A in accordance with an exemplary embodiment of the present disclosure;

[019] FIG. 5C is a flow chart diagram that shows another portion (i.e., proposal of popular moments) of the exemplary method of FIG. 5A in accordance with an exemplary embodiment of the present disclosure;

[020] FIG. 5D is a flow chart diagram that shows another portion (i.e., proposal of popular moments) of the exemplary method of FIG. 5A in accordance with an exemplary embodiment of the present disclosure;

[021] FIG. 6 is an exemplary processing node. DETAILED DESCRIPTION

[022] This description and the accompanying drawings illustrate exemplary embodiments and should not be taken as limiting, with the claims defining the scope of the present disclosure, including equivalents. Various mechanical, compositional, structural, electrical, and operational changes may be made without departing from the scope of this description and the claims, including equivalents. In some instances, well-known structures and techniques have not been shown or described in detail so as not to obscure the disclosure. Like numbers in two or more figures represent the same or similar elements. Furthermore, elements and their associated aspects that are described in detail with reference to one embodiment may, whenever practical, be included in other embodiments in which they are not specifically shown or described. For example, if an element is described in detail with reference to one embodiment and is not described with reference to a second embodiment, the element may

nevertheless be claimed as included in the second embodiment.

[023] It is noted that, as used in this specification and the appended claims, the singular forms "a," "an," and "the," and any singular use of any word, include plural referents unless expressly and unequivocally limited to one referent. As used herein, the term "include" and its grammatical variants are intended to be non-limiting, such that recitations of items in a list is not to the exclusion of other like items that can be substituted or added to the listed items.

[024] In accordance with various exemplary embodiments, the present disclosure contemplates systems and methods for smart, network configuration of and control at multiple network-connected nodes deployed in a region and/or zone of a facility and/or smart-home environment. In one embodiment, for example, on installation of network nodes in a region and/or zone of a facility and/or smart-home environment, the installed network nodes can be configured to report and/or enable flows of data (e.g., that indicate a current operational state, status, and/or value associated with the network node) at/to a control node. The control node can isolate and/or query the reported data flows. Using the isolated and/or queried data flows, the control node can automatically and/or autonomously (e.g., without instruction from an end-user) configure, modify, and/or control, in real-time, user-settings of the network nodes. Further, the control node can deploy the user-settings (e.g., based on common human- related activities occurring in the region and/or zone of the facility and/or smart- home environment, etc.) to the installed network nodes. The deployed user- settings can enable interaction and/or collaboration among the installed network nodes.

[025] Human-related activities occurring in the facility and/or smart-home environment can be monitored at an interface hosted at the control node and/or at a network device via a facility and/or smart-home application. Further, the control node and/or the network device (e.g., which can alert an end-user of the hosted facility and/or smart-home application) can be alerted on detection of a change in human-related activities occurring in the region and/or zone of the facility and/or smart-home environment. Depending on the deployed user- settings (e.g., including the enabled interactions and/or collaborations among the installed network nodes), in response to the alert, the control node and/or network device can further adapt the deployed user-settings. In one exemplary embodiment, the control node and/or network device can use machine-learning to propose bundled user-settings for deployment to the installed network nodes. The bundled user-settings can be use used to enable interaction and/or collaboration among the installed network nodes based on, for example, common human-related activities occurring in the region and/or zone of the facility and/or smart-home environment.

[026] With reference now to FIG. 1 A, a schematic view of an exemplary automation network system 100 of a facility and/or smart-home environment is depicted. System 100 includes network-connected nodes 102 (e.g., smart equipment, furniture, and/or systems such as, for example, smart accessories or fittings, smart wall-like switches, smart utility interfaces, smart wall-plug interfaces, smart appliances including refrigerators, televisions, washers, dryers, lights, blinds, audio systems, intercom systems, mechanical actuators, wall air conditioners, thermostats, pool-heating units, irrigation systems, etc.) installed in a region and/or zone (e.g., office, plant, operating room, classroom, kitchen, bathroom, outdoor area, indoor area, garage, levels, floors, living room, gym room, bedroom, and/or any other area or room) of a smart facility (e.g., an apartment building, duplex, commercial structure(s), industrial facility, university campus, hospital, and/or other multi-family, dwelling-type environment, etc.) and/or single-family, dwelling-type environment 1 10. Network-connected nodes 102 can include, for example, a processing node 600 (shown in FIG. 6), smart sensors, and/or smart actuators, etc., that enable interaction and/or collaboration among network nodes 102, control node 104, network devices 1 14, 1 16, access point 106, network 108, and/or network hub node 1 12. On installation, the network-connected nodes 102 can be coupled (communicatively or otherwise) to the control node 104 (e.g., a facility control hub, smart-home control hub, etc.) and/or network device 1 14, 1 16 (e.g., a remote terminal unit, cell phone, smart phone, computing platform, and/or other internet access device, etc.).

[027] System 100 further includes access point 106. Access point 106 can be configured as a wired and/or wireless router and/or other gateway node that facilitates receipt, routing, and/or forwarding of data flows among network nodes 102, control node 104, network devices 1 14, 1 16, network 108, and/or network hub node 1 12 using a variety of communication media and protocols including, for example, wireless network protocols such as Wi-Fi, IrDA, Bluetooth, Zigbee, Z-Wave, 6L0WPAN, Long Term Evolution (LTE) and/or wired network protocols such as CAT6 Ethernet, Ethernet, Fast Ethernet, Gigabit Ethernet, Local Talk (such as Carrier Sense Multiple Access with collision Avoidance), Token Ring, TCP/IP, Fiber Distributed Data Interface (FDDI), and Asynchronous Transfer Mode (ATM), etc.

[028] Network 108 can be a wired and/or wireless communication network that uses, for example, physical and/or wireless data links to carry data flows among network nodes 102, control node 104, network devices 1 14, 1 16, access point 106, and/or network hub node 1 12. Network 108 can include a Local Area Network (LAN), a Wide Area Network (WAN), and an internetwork (including the Internet). Network 108 can support push-to-talk (PTT), broadcast video, and/or data flows among network nodes 102, network devices 1 14, 1 16, control node 104, access point 106, and/or network hub node 1 12 using, for example, the wireless and/or wired network protocols.

[029] Network hub node 1 12 can be a standalone computing device, computing system, or network component that uses, for example, physical and/or wireless data links to carry data flows among network nodes 102, network devices 1 14, 1 16, control node 104, access point 106, and/or network 108.

Network hub node 1 12 can retrieve user-settings, bundled user-settings (e.g., moments), reported and/or crowdsourced data flows, usage models, historical market research information (e.g., about common human-related activities), etc., from a central datastore (e.g., a moments module, machine-learning module, detection module, tool libraries, etc.) hosted at and/or distributed among network- connected nodes 102, control node 104, network devices 1 14, 1 16, access point 106, network 108, and/or network hub node 1 12 or at an external network and/or control module. The network hub node 1 12 can use the retrieved information to, for example, adapt and/or create interactions and/or collaborations among the network-connected nodes 102, control node 104, and/or network devices 1 14, 1 16. Further, the network hub node 1 12 can apply machine-learning to the retrieved information to propose moments to the network-connected nodes 102, control node 104, and/or network devices 1 14, 1 16 (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at the network device).

Network hub node 1 12 can include a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a Policy Control and Charging Rules Function (PCRF), an Authentication, Authorization, and Accounting (AAA) node, a Rights Management Server (RMS), a Subscriber Provisioning Server (SPS), a policy server, etc.

[030] With reference now to FIG. 1 B, a schematic view that shows a portion of the exemplary automation network system 100 is depicted. As noted above, system 100 is used to enable smart, network configuration of and control at multiple network-connected nodes 102, 102A in a region and/or zone of a smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C.

[031] An end-user 1 17A, 1 17B can install network-connected nodes 102A in a smart facility and/or single-family, dwelling-type environment 1 10A, 1 10B, 1 10C to control, for example, an operating mode of a utility (e.g., efficient, peak-usage hour, brownout condition, etc.), an operating condition of lights (e.g., bright, ambient, dim, on, off, etc.), an operating condition of blinds (e.g., shutters open, shutters closed, blinds-up, blinds-down, etc.), an operating condition of an audio system, intercom system, and/or television (e.g., mute, loud, soft, sound- up, sound-down, on, off, etc.), an operating condition of a smart wall-plug interface, smart wall-like switch, and/or smart appliance (e.g., efficient, on, off, etc.), an operating condition of a smart thermostat (e.g., too-hot, too-cold, on, off, etc.), etc., in a region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10A, 1 10B, 1 10C. [032] In one exemplary embodiment, on installation of the network- connected nodes 102A, the network-connected nodes 102A can automatically and/or autonomously integrate (or couple) to other network-connected nodes, control node 104A, 104B, 104C, network device 1 16A, access point 106, and/or network 108 using a unique identifier (e.g., registration code, label, and/or value that identifies the network-connected node as a unique object and/or as belonging to a unique class of objects, etc.) stored at or otherwise associated with the network-connected node 102A. On and/or after integration, the network- connected nodes 102A can report data flows at the control node 104A, 104B, 104C and/or network device 1 16A. In an alternative embodiment, the network- connected nodes 102A can be configured with minimal intelligence such that, on installation, the minimally-intelligent, network-connected nodes 102A are commissioned (e.g., using an interface of a facility and/or smart-home application 1 18 hosted at, for example, the control node 104A, 104B, 104C and/or network device 1 16A) to integrate (or couple) the network-connected nodes 102A to other network-connected nodes, control node 104A, 104B, 104C, network device 1 16A, access point 106, and/or network 108.

[033] The control node 104A, 104B, 104C and/or network device 1 16A, on receipt of data flows from the network-connected nodes 102A, and using a machine-learning module hosted at, for example, a central datastore, can correlate data flows of the network-connected nodes 102A to similar data flows received from the and/or other network-connected nodes 102A, control node 104A, 104B, 104C, network device 1 16A, access point 106, and/or network 108. The machine-learning module can use the correlations to create unique usage models for the network-connected nodes 102A, which unique usage models can be aggregated and/or combined in multiple ways (e.g., based on collected, crowdsourced data flows, common human-related activities, historical market research information, etc.). Further, the machine-learning module can use the aggregated and/or combined usage models to generate a base usage model for the smart facility and/or single-family, dwelling-type environment 1 10A, 1 10B, 1 10C. For example, the base usage model for smart facility and/or single-family, dwelling-type environment 1 10A can indicate that common human-related activities do not occur in the environment 1 10A on Monday - Friday from 9:00 a.m. until 5:00 p.m. and/or that end-users 1 17A, 1 1 7B adjust a temperature of a smart-home thermostat from 72°C to 63°C in the single-family, dwelling-type environment 1 10A on Monday - Friday at 9:00 a.m. and, then, at 5:00 p.m.

readjust the temperature to 72°C. In addition, the machine-learning module can create an end-user usage model for each end-user 1 1 7A, 1 17B associated with the smart facility and/or single-family, dwelling-type environment 1 10A, 1 10B, 1 10C. The end-user usage model (e.g., a usage model that tracks and/or maps an end-user's interaction with network-connected nodes installed in the smart- home environment) can be correlated to the other usage model(s). The control node 104A, 104B, 104C and/or network device 1 16A can use the usage model(s) to configure, modify, propose, and/or control user-settings, bundled user-settings (e.g., moments), and/or historical market research information for the network- connected nodes 102A. [034] With reference now to FIG. 2, a flow diagram of an exemplary method for configuration and control of a facility and/or smart-home environment is depicted. The method can be implemented in the exemplary automation network system 100 shown in FIGS. 1 A and 1 B, or with any suitable automation network system. The method for configuration and control of a facility and/or smart-home environment shown in FIG. 2 is discussed with reference to the network system 100 shown in FIGS. 1 A and 1 B. In addition, while FIG. 2 depicts steps performed in a particular order for purposes of illustration, the method should not be taken as limiting to any particular order or arrangement. One skilled in the art, together with the description, will appreciate that various steps of the method can be omitted, rearranged, combined, and/or adapted in various ways.

[035] At step 202, network-connected nodes 102, 102A can be installed in a smart facility and/or single-family, dwelling-type environment 1 10A, 1 10B, 1 10C. On installation of the network-connected nodes 102, 102A, an end-user 1 17A, 1 17B can commission (e.g., using an interface of a facility and/or smart- home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A) the network-connected nodes 102, 102A such that the network-connected nodes 102, 102A integrate (or couple) to other network-connected nodes 102, 102A, control node 104A, 104B, 104C, network device 1 14, 1 16, 1 16A, access point 106, and/or network 108. On and/or after integration, the network-connected nodes 102, 102A can report data flows at the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A.

[036] At step 204, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can detect a unique identifier (e.g., registration code, label, and/or value that identifies the network-connected node as a unique object and/or as belonging to a unique class of objects, etc.) of the network- connected nodes 102, 102A. The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can run a verification process to validate, authenticate, and/or otherwise substantiate on the detected unique identifier. Using the verified unique identifier, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can retrieve information (e.g., user- settings, bundled user-settings, reported and/or crowdsourced data flows, usage models, historical market research information, etc.) from, for example, a moments module hosted at a central datastore based on the unique object and/or unique class of objects to which the network-connected node 102, 102A belongs.

[037] At step 206, the control node 104, 104A, 104B, 104C and/or network node 1 14, 1 16, 1 16A can alert an end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) that additional network-connected nodes 102, 102A were installed in the smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C. Further, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can display, at an interface, the information retrieved from the moments module and/or historical digital, topographic studies (e.g., a graphic delineation, in detail, on a map and/or chart, of, for example, aspects of the network-connected nodes and/or the smart-home environment, including objects, class of objects, function, relative positions, elevations, and/or structural relationships) for the smart facility and/or single-family, dwelling-type

environment 1 10, 1 10A, 1 10B, 1 10C.

[038] At step 208, the control node 104, 104A, 104B, 104C and/or end- user 1 17A, 1 17B (e.g., via the interface of the network device 1 14, 1 16, 1 16A) can select a region and/or zone (e.g., structural relationship) from the displayed digital, topographic studies for the smart facility and/or single-family, dwelling- type environment 1 10, 1 10A, 1 10B, 1 10C. Alternatively, the control node 104, 104A, 104B, 104C and/or the end-user 1 17A, 1 17B can select a region and/or zone from a location list and/or table stored at, for example, the central datastore. If, at step 210, the selected region and/or zone exists, then, at step 214, the control node 104, 104A, 104B, 104C and/or the end-user 1 17A, 1 17B can assign the network-connected node 102, 102A to the selected region and/or zone in the smart facility and/or dwelling-type environment 1 10, 1 10A, 1 10B, 1 1 OC. If, at step 210, the selected region and/or zone does not exist, then, at step 212, the control node 104, 104A, 104B, 104C and/or the end-user 1 17A, 1 17B can create a new region and/or zone in the smart facility and/or dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C and assign the network-connected node 102, 102A to the new region and/or zone in the smart facility and/or dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C. The control node 104, 104A, 104B, 104C and/or end-user 1 17A, 1 17B (e.g., via an interface of the network node 1 14, 1 16, 1 16A) can update the location list and/or table to include the new region and/or zone.

[039] If, at step 216, other network-connected nodes 102, 102A are detected, then steps 202 - 216 are repeated. If, at step 216, other network- connected nodes 102, 102A are not detected, then the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, at step A (shown in FIG. 3), can use the moments module to apply moments to the installed network- connected nodes 102, 102A. If, at step 218, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A elects to apply customized moments to the network-connected nodes 102, 102A then, at step B (shown in FIG. 4), the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can use the moments module to customize moments. If, however, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 1 6, 1 16A elects, at step 218, to apply default moments to the network-connected nodes 102, 102A then, at step 220, the configuration and/or installation of the network-connected nodes 102, 102A is complete.

[040] With reference now to FIG. 3, a flow chart diagram of a portion A of the exemplary method for configuration and control of a facility and/or smart- home environment shown in FIG. 2 is depicted. The portion A of the method of FIG. 2 can be implemented in the exemplary automation network system 100 shown in FIGS. 1 A and 1 B, or with any suitable automation network system. The portion A of the method of FIG. 2 is discussed with reference to the automation network system 100 shown in FIGS. 1 A and 1 B. In addition, while FIG. 3 depicts steps performed in a particular order for purposes of illustration, the portion A of the method of FIG. 2 should not be taken as limiting to any particular order or arrangement. One skilled in the art, together with the description, will appreciate that various steps of the portion A of the method of FIG. 2 can be omitted, rearranged, combined, and/or adapted in various ways.

[041] At step 302, on installation of network-connected nodes 102, 102A in regions and/or zones of a smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C, the network-connected nodes 102, 102A can report data flows at a control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A. The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A can isolate and/or query (e.g., for type, historical use, location, user-settings, operating mode, operating condition, intelligence, usage models, applied moments, etc.) the reported data flows using a unique identifier (e.g., registration, code, label, and/or value that identifies the network-connected node as a unique object and/or as belonging to a unique class of objects, etc.) of the network-connected nodes 102, 102A. Further, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, using the isolated (or queried) data flows, can produce digital, topographic studies (e.g., graphic delineation, in detail, on a map and/or chart, of, for example, aspects of the network-connected nodes and/or the smart-home environment, including objects, class of objects, function, relative positions, elevations, and/or structural relationships) for the smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C. The digital, topographic studies can be stored at the central datastore. The control node 104, 104A, 104B, 104C and/or an end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A) can retrieve the digital, topographic studies from the central datastore.

[042] At step 304, in one exemplary embodiment, the control node 104, 104A, 104B, 104C and/or the end-user 1 17A, 1 17B (e.g., via an interface of network device 1 14, 1 16, 1 16A) can use the digital, topographic studies to assign the network-connected nodes 102, 102A to single and/or multiple regions and/or zones (e.g., using a layering technique) of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C. Alternatively, at step 304, the control node 104, 104A, 104B, 104C and/or the end-user 1 17A, 1 17B can select a region and/or zone from a location list and/or table stored at, for example, the central datastore. Region and/or zone selection can trigger the control node 104, 104A, 104B, 104C and/or the network device 1 14, 1 16, 1 16A to automatically and/or autonomously isolate and/or query for network-connected nodes 102, 102A installed in the selected region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C.

[043] At steps 306 and 308, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can retrieve information (e.g., user- settings, bundled user-settings, reported and/or crowdsourced data flows, usage models, historical market research information, etc.) of similar network-connected nodes 102, 102A and/or smart facility and/or single-family, dwelling-type environments 1 10, 1 10A, 1 10B, 1 10C from a central data store (e.g., a moments module, machine-learning module, detection module, tool libraries, etc.) hosted at and/or distributed among network-connected nodes 102, 102A, control node 104, 104A, 104B, 104C, network devices 1 14, 1 16, 1 16A, access point 106, network 108, and/or network hub node 1 12 or at an external network and/or control module. The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can use the information to propose moments (e.g., that include action values set based on an interaction and/or collaboration of the network nodes 102, 102A) to and end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.).

[044] For example, in a temperature scenario, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can propose application of a moment to a network-connected thermostat 102A. The proposed moment can include default action values (e.g., on Monday - Friday from 10:00 a.m. to 6:00 p.m. the temperature is set at 68°C, then, at 6:00 p.m. the temperature is adjusted to 72°C) configured, for example, based on reported and/or crowdsourced data flows and historical market research information of thermostats. Depending on usage models, the control node 104, 104A, 104B, 104C and/or an end-user 1 17A, 1 17A (e.g., at an interface of network device 1 14, 1 16, 1 16A) can adjust the default action values of the moment. For example, the end-user 1 17A, 1 17B can indicate that on Monday - Friday from 10:00 a.m. to 4:00 p.m. the temperature is set at 63°C, then, at 4:00 p.m. the temperature is adjusted to 71 °C. The adjusted moment can be stored at the moments module and/or tagged to the end-user 1 17A, 1 17B.

[045] Similarly, in a movie scenario, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can propose application of a moment to a group of network-connected nodes 102, 102A (e.g., smart wall-like switches, smart wall-plug interfaces, lights, blinds, thermostats, audio systems, etc.) to achieve a desired movie watching ambieance. The proposed moment can include default action values (e.g., dim lights, close blinds, volume-up, turn- on television, set temperature at 68°C, etc.) configured, for example, based on reported and/or crowdsourced data flows and historical market research information of thermostats. Depending on usage models, the control node 104, 104A, 104B, 104C and/or an end-user 1 17A, 1 17A (e.g., at an interface of network device 1 14, 1 16, 1 16A) can adjust the default action values of the moment. For example, the end-user 1 17A, 1 17B can indicate that the desired temperature is 71 °C and the lights should be off. The adjusted moment can be stored at the moments module and/or tagged to the end-user 1 17A, 1 17B.

[046] At step 312, steps 304 - 308 can be repeated. At step 318, the moments creation stops.

[047] With reference now to FIG. 4, a flow chart diagram of a portion B of the exemplary method for configuration and control of a facility and/or smart- home environment shown in FIG. 2 is depicted. The portion B of the method of FIG. 2 can be implemented in the exemplary automation network system 100 shown in FIGS. 1 A and 1 B, or with any suitable automation network system. The portion B of the method of FIG. 2 is discussed with reference to the automation network system 100 shown in FIGS. 1 A and 1 B. In addition, while FIG. 4 depicts steps performed in a particular order for purposes of illustration, the portion B of the method of FIG. 2 should not be taken as limiting to any particular order or arrangement. One skilled in the art, together with the description, will appreciate that various steps of the portion B of the method of FIG. 2 can be omitted, rearranged, combined, and/or adapted in various ways.

[048] At step 402, an uninstalled network-connected node 102, 102A can be installed in a region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C. The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A can display a list and/or table of possible moments (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) the installed network-connected node 102, 102A can be integrated with to an end-user 1 17A, 1 17B. If, at step 404, the moment was previously deleted from the moments module, then, at step 406, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A automatically detects the deleted moment and removes it from the moments list and/or table. Alternatively, at step 404, the end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) can indicate that the moment was previously deleted and, then, at step 406, reject the proposed moment. [049] If, at step 408, the moment was not previously created at the moments module, then, at step 410, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B can automatically create the moment and store it at the moments module. Alternatively, at step 410, the end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) can elect to create the moment and store it at the moments module. The control node 104, 104A, 104B, 1 04C and/or network device 1 14, 1 16A, 1 16B can apply the newly created moment to the installed, network-connected node 102, 102A.

[050] If, at step 412, the moment exists (e.g., default moment), then, at step 414, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B looks for similar network-connected nodes 102, 102A installed in the region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C that are associated with the default moment. If, at step 416, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B does not find similar network-connected nodes 102, 102A installed in the region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 1 OB, then, at step 416, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A prompts the end- user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) to accept integration of the installed network- connected node 102, 102A using the default moment. If, at step 418, the end- user 1 17A, 1 17B accepts the prompt, then, at step 420, the installed network- connected node 102, 102A is added to the default moment. If, at step 418, the end-user 1 17A, 1 17B does not accept the prompt, then, at step 428, the installed network-connected node 102, 102A is not added to the default moment.

[051] If, at step 412, the moment exists (e.g., default moment), then, at step 414, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B looks for similar network-connected nodes 102, 102A installed in the region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C that are associated with the default moment. If, at step 422, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B finds similar network-connected nodes 102, 102A installed in the region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C, then, at step 422, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A prompts the end-user 1 17A, 1 17B (e.g., at an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) to accept integration of the installed network-connected node 102, 102A using an adjusted moment (e.g., using adjusted action values). If, at step 424, the end-user 1 17A, 1 17B accepts the prompt, then, at step 426, the installed network-connected node 102, 102A is added to the adjusted moment. If, at step 424, the end-user 1 17A, 1 17B does not accept the prompt, then, at step 428, the installed network-connected node 102, 102A is not added to the adjusted moment.

[052] With reference now to FIGS. 5A - 5D, flow diagrams of an exemplary method for configuration and control of a facility and/or home automation network at a network node is depicted. The method can be enabled in the exemplary automation network system 100 shown in FIGS. 1 A and 1 B, or with any suitable network system. The method for configuration and control of a facility and/or home automation network shown in FIG. 5 is discussed with reference to the network system 100 shown in FIGS. 1 A and 1 B. In addition, while FIG. 5 depicts steps performed in a particular order for purposes of illustration, the method should not be taken as limiting to any particular order or arrangement. One skilled in the art, together with the description, will appreciate that various steps of the method can be omitted, rearranged, combined, and/or adapted in various ways.

[053] At step 502, a moments module can be stored at a central data store and/or tool library hosted at and/or distributed among network nodes 102, 102A, network devices 1 14, 1 16, 1 16A, control node 104, 104A, 104B, 104C, access point 106, network 108, and/or network hub node 1 12 or at an external network and/or control module. The moments module can include a moments tool library (e.g., which includes lists and/or tables of network nodes, regions and/or zones, digital topologies, operating modes and/or conditions of the network nodes, activities, moments generated based on common human-related activities such as, for example, bathing A, sleeping B, cooking C, working out D, reading E, watching movies F, etc.) and/or be integrated another tool library. The moments module can be configured to collect data flows from, for example, similarly situated network-connected nodes and/or control nodes compared to network-connected nodes 102, 102A and/or control node 104, 104A, 104B, 104C using, for example, crowdsourcing. Further, the moments module, using the collected, crowdsourced data flows and/or historical market research information about common human-related activities performed in specific regions and/or zones of smart facilities and/or single-family, dwelling-type environments can create default moments (e.g., a list and/or table of user-settings to be applied to the installed network nodes). By combining the crowdsourced data flows and/or historical market research information about human-related activities, the default moments can be created such that, on commissioning and/or installation of a network-connected node 102, 102A in a smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C, the default moments can be automatically and/or autonomously applied to and/or used to adjust out-of-the- box user-settings of the network-connected nodes 102, 102A.

[054] Using machine-learning, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B can update the applied default moments based on, for example, end-user 1 17A, 1 17B preferences and/or behaviors. For example, human-related activities occurring in the region and/or zone of the smart facility and/or single-family dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C can be monitored at an interface hosted at the control node 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B. Further, the control node 104, 104A, 104B, 104C and/or an end-user 1 17A, 1 17B can be alerted on detection of a change in human-related activities occurring in the region and/or zone of the smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C.

[055] At step 504, the collected user preferences and/or behaviors can be analyzed at the control node. For example, using machine-learning, the control node 104, 104A, 104B, 104C and/or the network device 1 14, 1 16A, 1 16B can generate a usage model that indicates that human-related activities do not occur in the smart facility and/or single-family, dwelling-type environment 1 10, 1 10A, 1 10B, 1 10C on Monday - Friday from 9:00 a.m. until 5:00 p.m. and/or that the end-users 1 17A, 1 17B watch television on Friday evenings from 8:00 p.m. to 10:00 p.m., etc. The generated usage model can be updated for multiple end- users 1 17A, 1 17B using a usage model specific to the end-user 1 17A, 1 17B. For example, based on end-user 1 17A's usage model, the generated default usage model may be updated for end-user 1 17A to indicate that end-user 1 17A watches television on every other Friday evening from 6:00 p.m. to 7:00 p.m.

[056] At step 506, the default moment can be updated and/or adjusted based on the collected user preferences and behaviors. For example, referring to FIG. 5B, at steps 506A - 506E, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine-learning module, can collect usage models for multiple end-users and generate default usage models for the moments (e.g., based on an aggregation of the unique network usage models of all of the end-users) at set intervals. The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine-learning module, can use the generated default usage models to further generate usage models for the moments, which usage models can be used at the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B to adjust default moments applied to newly added network-connected nodes 102, 102A. For example, at steps 506F - 506H, on installation of a network-connected node 102, 102A in a smart facility and/or single-family, dwelling-type environment 1 10, 1 1 OA, 1 10B, 1 10C, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 14A, 1 16B (e.g., using the moments module) can automatically and/or autonomously apply the adjusted default moments to the network-connected node 102, 102A and/or alert an end-user 1 17A, 1 17B (e.g., using an interface of a facility and/or smart-home application 1 18 hosted at, for example, control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16, 1 16A, etc.) of the adjusted default moments such that, for example, fewer end-users 1 17A, 1 17B adjust (or change) the moments (e.g., user-settings associated with the moments). The moment tool library can be updated to include the adjusted default moments.

[057] At step 508, popular moments using the adjusted default moment can be proposed. For example, referring to FIG. 5C, at steps 508A - 508G, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine-learning module, can collect usage models for multiple end-users and generate default usage models for the moments (e.g., based on an aggregation of the usage models of all of the end-users). The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine- learning module, can use the generated default usage models to delete user- settings of the moments that are rarely used by end-users 1 17A, 1 17B from the moments tool library (e.g., updated default usage models). The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B can use the updated default usage models to further generate usage models for the moments (e.g., that do not include the deleted, rarely used user-settings). The usage model can be used at the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B to further adjust default moments applied to newly-added network- connected nodes 102, 102A such that the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B does not apply unpopular moments to the network-connected node 102, 102A on installation. The moment tool library can be updated to include the adjusted default moments.

[058] Alternatively, referring to FIG. 5D, at steps 508H - 508N, the control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine-learning module, can collect usage models for multiple end-users and generate default usage models for the moments (e.g., based on an aggregation of the unique network usage models of all of the end-users). The control node 104, 104A, 104B, 104C and/or network device 1 14, 1 16A, 1 16B, via the machine-learning module, can use the generated default usage models to determine that user-settings of the moments already exist (or are duplicated) in the moments tool library. The machine-learning module can combine the user- settings of duplicated moments and update the default usage models. Thus, newly installed network-connected nodes 102, 102A receive the updated usage models.

[059] FIG. 6 illustrates an exemplary processing node 600 in a network system. Processing node 600 can include a communication interface 602, user interface 604, and processing system 606 in communication with communication interface 602 and user interface 604. Processing system 606 includes storage 608, which can comprise a disk drive, flash drive, memory circuitry, or other memory device. Storage 608 can store software 610, which is used in the operation of processing node 600. Storage 608 includes a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Software 610 can include computer programs, firmware, or some other form of machine-readable instructions, including an operating system, utilities, drivers, network interfaces, applications, or some other type of software. Processing system 606 can include a microprocessor and other circuitry to retrieve and execute software 610 from storage 608. Processing node 600 can further include other components such as a power management unit, a control interface unit, etc., which are omitted for clarity. Communication interface 602 permits processing node 600 to

communicate with other network elements. User interface 604 permits the configuration and control of the operation of processing node 600.

[060] Examples of processing node 600 can include network-connected nodes 102, 102A, control nodes 104, 104A, 104B, 104C, access point 106, and/or network hub node 1 12. Processing node 600 can also be a component of a network element, such as a component of network-connected nodes 102, 102A, control nodes 104, 104A, 104B, 104C, network devices 1 14, 1 16, 1 16A, access point 106, and/or network hub node 1 12. Processing node 600 can also be another network element in a network system. Further, the functionality of processing node 600 can be distributed over multiple network elements of the network system.

[061] The exemplary methods and systems described can be performed under the control of a processing system executing computer-readable codes embodied on a computer-readable recording medium or signals sent through a transitory medium. The computer-readable recording medium can be any data storage device that can store data readable by a processing system and includes both volatile and nonvolatile media, removable and non-removable media, and contemplates media readable by a database, a computer, and various other network devices.

[062] Examples of the computer-readable recording medium include, but are not limited to, read-only memory (ROM), random-access memory (RAM), erasable electrically programmable ROM (EEPROM), flash memory or other memory technology, holographic media or other optical disc storage, magnetic storage including magnetic tape and magnetic disk, and solid state storage devices. The computer-readable recording medium can also be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. The signals transmitted through a transitory medium may include, for example, modulated signals transmitted through wired or wireless transmission paths.