WO2025230978A1 - Systems and methods for custom relay outputs for a thermostat - Google Patents

Abstract

Disclosed are systems and methods of a novel framework for automatically and dynamically activates, based on scheduled and/or application-controlled, custom relay outputs. The disclosed framework provides features, capabilities and/or functionality for enhanced and/or improved customization and integration of different home automation or climate control systems, which can provide enhanced/improved control over the location's operation and environment, while also improving energy efficiency and resource utilization. The disclosed framework can function to provide a thermostat, for example, with capabilities to operate certain connected devices/sensors according to controls that correlate to managing certain real-world, real-time events, which can effectuate an improved operational environment via the modified thermostat controls.

Description

SYSTEMS AND METHODS FOR CUSTOM RELAY OUTPUTS FOR A THERMOSTAT

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of, and priority to, U.S. Provisional Patent Application No. 63/639,929 filed April 29, 2024, the entire contents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

[0002] The present disclosure is generally related to climate control mechanisms, and more particularly, to a decision intelligence (Dl)-based computerized framework that automatically and dynamically activates, based on scheduled and/or application-controlled, custom relay outputs

SUMMARY OF THE DISCLOSURE

[0003] A custom relay output typically refers to a specific configuration or setup of a relay device tailored to meet particular requirements or specifications of a project or application. A relay is an electromechanical switch that is used to control the flow of electricity in a circuit. A relay typically consists of a coil and a set of contacts that open or close when the coil is energized.

[0004] Customizing a relay output could involve various modifications, such as. for example, adjusting the voltage or current rating, altering the timing or delay settings, adding additional features like surge protection or feedback mechanisms, integrating it into a larger control system, and the like. The customization can be usually performed to ensure that the relay performs optimally within the specific parameters of the intended use case

[0005] With regard to a thermostat and an Equipment Interface Module (EIM), a custom relay output refers to a feature that allows the thermostat to control external devices or systems beyond standard HVAC (Heating, Ventilation, and Air Conditioning) equipment. By way of discussion, a thermostat can communicate with an HVAC system through wires connected to terminals on the thermostat and the HVAC equipment and/or via wireless connectivity between such devices. However, some thermostats, particularly those with advanced features or capabilities, may also include additional relay outputs that can be programmed to control other devices, such as humidifiers, dehumidifiers, ventilation systems, and/or even non-HVAC equipment like lighting or security systems, and the like.

[0006] As discussed herein, an EIM serves as a bridge between the thermostat and the HVAC equipment, providing additional functionality and communication capabilities. When a thermostat has a custom relay output, the thermostat can send signals to the EIM, which then activates the appropriate relay to control the connected device or system.

[0007] As discussed herein, according to some embodiments, the disclosed systems and methods provide features related to capabilities and functionality for enhanced and/or improved customization and integration of different location (e.g., home, for example) automation and/or climate control systems, giving users more control over their indoor environment and improving energy efficiency and comfort.

[0008] As discussed herein, a location can be any type of building, structure or definable physical, geographic location, such as. but not limited to, a home, office, patio, garage, and the like.

[0009] It should be understood that while the discussion herein focuses on EIMs on and/or in connection with thermostats, and/or on and/or in connection with other types of connected sensors/devices within climate systems, it should not be construed as limiting, as other types of devices and/or systems (e.g.. security panels on security systems, for example) can be the basis of the disclosed framework’s operation without departing from the scope of the instant disclosure.

[0010] According to some embodiments, a method is disclosed that automatically and dynamically activates, based on scheduled and/or application-controlled, custom relay outputs. In accordance with some embodiments, the present disclosure provides a non-transitory computer-readable storage medium for carrying out the above-mentioned technical steps of the framework’s functionality. The non-transitory computer-readable storage medium has tangibly stored thereon, or tangibly encoded thereon, computer readable instructions that when executed by a device cause at least one processor to perform a method that automatically and dynamically activates, based on scheduled and/or application-controlled, custom relay outputs.

[0011] In accordance with one or more embodiments, a system is provided that includes one or more processors and/or computing devices configured to provide functionality in accordance with such embodiments. In accordance with one or more embodiments, functionality is embodied in steps of a method performed by at least one computing device. In accordance with one or more embodiments, program code (or program logic) executed by a processor(s) of a computing device to implement functionality in accordance with one or more such embodiments is embodied in, by and/or on a non-transitory computer-readable medium.

DESCRIPTIONS OF THE DRAWINGS

[0012] The features, and advantages of the disclosure will be apparent from the following description of embodiments as illustrated in the accompanying drawings, in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating principles of the disclosure:

[0013] FIG. 1 is a block diagram of an example configuration within which the systems and methods disclosed herein could be implemented according to some embodiments of the present disclosure;

[0014] FIG. 2 is a block diagram illustrating components of an exemplary' system according to some embodiments of the present disclosure;

[0015] FIG. 3 illustrates an exemplary workflow according to some embodiments of the present disclosure;

[0016] FIG. 4 depicts an exemplary implementation of an architecture according to some embodiments of the present disclosure;

[0017] FIG. 5 depicts an exemplary implementation of an architecture according to some embodiments of the present disclosure; and

[0018] FIG. 6 is a block diagram illustrating a computing device showing an example of a client or server device used in various embodiments of the present disclosure.

DETAILED DESCRIPTION

[0019] The present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show', by way of non-limiting illustration, certain example embodiments. Subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein; example embodiments are provided merely to be illustrative. Likewise, a reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, or systems. Accordingly, embodiments may, for example, take the form of hardw are, software, firmware or any combination thereof (other than software per se). The following detailed description is. therefore, not intended to be taken in a limiting sense.

[0020] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter include combinations of example embodiments in whole or in part.

[0021] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”, “or”, or “and/or,” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may. instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

[0022] The present disclosure is described below with reference to block diagrams and operational illustrations of methods and devices. It is understood that each block of the block diagrams or operational illustrations, and combinations of blocks in the block diagrams or operational illustrations, can be implemented by means of analog or digital hardware and computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer to alter its function as detailed herein, a special purpose computer, ASIC, or other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the functions/acts specified in the block diagrams or operational block or blocks. In some alternate implementations, the functions/acts noted in the blocks can occur out of the order noted in the operational illustrations. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functional ity/acts involved. [0023] For the purposes of this disclosure a non-transitory computer readable medium (or computer-readable storage medium/media) stores computer data, which data can include computer program code (or computer-executable instructions) that is executable by a computer, in machine readable form. By way of example, and not limitation, a computer readable medium may include computer readable storage media, for tangible or fixed storage of data, or communication media for transient interpretation of code-containing signals. Computer readable storage media, as used herein, refers to physical or tangible storage (as opposed to signals) and includes without limitation volatile and non-volatile, removable and nonremovable media implemented in any method or technology for the tangible storage of information such as computer-readable instructions, data structures, program modules or other data. Computer readable storage media includes, but is not limited to, RAM. ROM, EPROM, EEPROM, flash memory or other solid state memory technology, optical storage, cloud storage, magnetic storage devices, or any other physical or material medium which can be used to tangibly store the desired information or data or instructions and which can be accessed by a computer or processor.

[0024] For the purposes of this disclosure the term "‘server’ should be understood to refer to a service point which provides processing, database, and communication facilities. By way of example, and not limitation, the term “server” can refer to a single, physical processor with associated communications and data storage and database facilities, or it can refer to a networked or clustered complex of processors and associated network and storage devices, as well as operating software and one or more database systems and application software that support the services provided by the server. Cloud servers are examples.

[0025] For the purposes of this disclosure a “network” should be understood to refer to a network that may couple devices so that communications may be exchanged, such as between a server and a client device or other types of devices, including between wireless devices coupled via a wireless network, for example. A network may also include mass storage, such as network attached storage (NAS), a storage area network (SAN), a content delivery network (CDN) or other forms of computer or machine-readable media, for example. A network may include the Internet, one or more local area networks (LANs), one or more wide area networks (WANs), wire-line type connections, wireless type connections, cellular or any combination thereof. Likewise, sub-networks, which may employ differing architectures or may be compliant or compatible with differing protocols, may interoperate within a larger network.

[0026] For purposes of this disclosure, a '‘wireless network” should be understood to couple client devices with a network. A wireless network may employ stand-alone ad-hoc netw orks, mesh networks, Wireless LAN (WLAN) networks, cellular networks, or the like. A wireless network may further employ a plurality of network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router mesh, or 2nd, 3rd, 4^th or 5^th generation (2G, 3G, 4G or 5G) cellular technology, mobile edge computing (MEC), Bluetooth, 802.1 Ib/g/n, or the like. Network access technologies may enable wide area coverage for devices, such as client devices with varying degrees of mobility, for example.

[0027] In short, a wireless network may include virtually any type of wireless communication mechanism by which signals may be communicated between devices, such as a client device or a computing device, between or within a netw ork, or the like.

[0028] A computing device may be capable of sending or receiving signals, such as via a wired or wireless network, or may be capable of processing or storing signals, such as in memory as physical memory states, and may, therefore, operate as a server. Thus, devices capable of operating as a server may include, as examples, dedicated rack-mounted servers, desktop computers, laptop computers, set top boxes, integrated devices combining various features, such as two or more features of the foregoing devices, or the like.

[0029] For purposes of this disclosure, a client (or user, entity, subscriber or customer) device may include a computing device capable of sending or receiving signals, such as via a wired or a wireless network. A client device may, for example, include a desktop computer or a portable device, such as a cellular telephone, a smart phone, a display pager, a radio frequency (RF) device, an infrared (IR) device a Near Field Communication (NFC) device, a Personal Digital Assistant (PDA), a handheld computer, a tablet computer, a phablet, a laptop computer, a set top box, a wearable computer, smart watch, an integrated or distributed device combining various features, such as features of the forgoing devices, or the like.

[0030] A client device may vary in terms of capabilities or features. Claimed subject matter is intended to cover a wide range of potential variations, such as a web-enabled client device or previously mentioned devices may include a high-resolution screen (HD or 4K for example), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, global positioning system (GPS) or other location-identifying type capability, or a display with a high degree of functionality, such as a touch-sensitive color 2D or 3D display, for example.

[0031] Certain embodiments and principles will be discussed in more detail with reference to the figures. By way of discussion, conventional thermostats and EIMS support versions of user- configurable terminals (e.g., inputs and outputs); however, such thermostats and EIMS can currently only activate a generic output upon some hardware signal (e.g., a dry contact input, or maybe a sensor value outside of some range, for example).

[0032] Accordingly, as discussed herein, the disclosed systems and methods provide a novel computerized framework that provide functionality and/or features for thermostats and EIMs to be able to activate custom outputs, which can be dynamically determined, on a determined timed schedule (e.g., for example, holiday lighting, security (e.g., lamps turning on/off), and/or via application controlled instructions (e.g., unlocking a gate, for example), where the application can be on a user device and/or executing on the thermostat (and/or any other device on the network and/or within the thermostat associated system).

[0033] With reference to FIG. 1, a system is depicted for a location 100 which includes thermostat 102, user equipment (UE) 112 (e.g., a client device, as mentioned above and discussed below in relation to FIG. 10), sensors 110, network 104, cloud system 106, database 108 and EIM engine 200. It should be understood that while system 100 is depicted as including such components, it should not be construed as limiting, as one of ordinary skill in the art would readily understand that varying numbers of smoke detectors, UEs, sensors, cloud systems, databases and networks can be utilized; however, for purposes of explanation, system 100 is discussed in relation to the example depiction in FIG. 1.

[0034] According to some embodiments, thermostat 102 is a temperature-regulating device commonly used in heating, ventilation, and air conditioning (HVAC) systems to maintain a desired temperature within a space. Thermostat 102 includes several key components, including, but not limited to, a temperature sensor, control circuitry, user interface (UI) and the like. According to some embodiments, as discussed below, an EIM (e.g.. via EIM engine 200) can be provided and/or associated with thermostat 102.

[0035] According to some embodiments, a temperature sensor of thermostat 102 measures the ambient temperature of the environment, converting it into an electrical signal that is interpreted by the control circuitry. In some embodiments, such circuitry compares the measured temperature to the user-set target temperature and activates or deactivates the heating or cooling system accordingly to achieve the desired temperature. [0036] In some embodiments, a UI of thermostat 102, which can be controlled by the EIM, as discussed above and in more detail below, allows individuals to adjust the target temperature and configure other settings, such as scheduling and mode selection.

[0037] In some embodiments, thermostat 102 can incorporate advanced features like Wi-Fi connectivity for remote control and programmability for energy efficiency. As discussed herein, thermostat 102 plays a critical role in maintaining comfort and energy efficiency in residential, commercial, and industrial settings by regulating the temperature of climate systems based on user preferences and environmental conditions.

[0038] According to some embodiments, UE 112 can be any type of device, such as, but not limited to, a mobile phone, tablet, laptop, sensor, Internet of Things (loT) device, autonomous machine, and any other device equipped with a cellular or wireless or wired transceiver. In some embodiments, UE 112 can be a device associated with an individual (or set of individuals) for which climate control services are being provided. In some embodiments, UE 112 may correspond to a device of a climate service provider entity (e.g., a thermostat, whereby the device can be and/or can have corresponding sensors 110, as discussed herein).

[0039] In some embodiments, a peripheral device (not shown) can be connected to UE 112, and can be any type of peripheral device, such as, but not limited to, a wearable device (e.g., smart watch), printer, speaker, sensor, and the like. In some embodiments, a peripheral device can be any t pe of device that is connectable to UE 1 12 (and/or sensor 1 10 and/or thermostat 102) via any type of known or to be known pairing mechanism, including, but not limited to, Wi-Fi, Bluetooth™, Bluetooth Low Energy (BLE), NFC, and the like.

[0040] According to some embodiments, sensors 110 can correspond to sensors associated with a location of system 100. In some embodiments, the sensors 110 can be, but are not limited to, temperature sensors (e.g., thermocouples, resistance temperature detectors (RTDs), thermistors, semiconductor based integrated circuits (IC), thermometers, and the like, for example) cameras, glass break detectors, motion detectors, door and window contacts, heat and smoke detectors, carbon monoxide (CO) and/or carbon dioxide (CO2) detectors, passive infrared (PIR) sensors, time-of-flight (ToF) sensors, and the like. For example, sensor 110 can be a temperature sensor associated with and/or connected to thermostat 102.

[0041] In some embodiments, the sensors 110 can involve an loT environment and/or be associated with devices associated with the location of system 100, such as, for example, lights, smart locks, garage doors, smart appliances (e.g.. thermostat, refrigerator, television, personal assistants (e.g., Alexa®, Nest®, for example)), smart phones, smart watches or other wearables, tablets, personal computers, and the like, and some combination thereof. For example, the sensors 1 10 can include the sensors on UE 1 12 (e.g., smart phone) and/or peripheral device (e.g., a paired smart watch).

[0042] In some embodiments, network 104 can be any type of network, such as, but not limited to, a wireless network, cellular network, the Internet, and the like (as discussed above). Network 104 facilitates connectivity of the components of system 100, as illustrated in FIG. 1. [0043] According to some embodiments, cloud system 106 may be any type of cloud operating platform and/or network based system upon which applications, operations, and/or other forms of network resources may be located. For example, system 106 may be a service provider and/or network provider from where services and/or applications may be accessed, sourced or executed from. For example, system 106 can represent the cloud-based architecture associated with a security and/or climate-control system provider, which has associated network resources hosted on the internet or private network (e.g., network 104), which enables (via engine 200) the location management discussed herein.

[0044] In some embodiments, cloud system 106 may include a server(s) and/or a database of information which is accessible over network 104. In some embodiments, a database 108 of cloud system 106 may store a dataset of data and metadata associated with local and/or network information related to a user(s) of UE 112/ thermostat 102 and the UE 112/ thermostat 102, sensors 1 10, and the services and applications provided by cloud system 106 and/or EIM engine 200.

[0045] In some embodiments, for example, cloud system 106 can provide a private/proprietary management platform, whereby engine 200, discussed infra, corresponds to the novel functionality system 106 enables, hosts and provides to a network 104 and other devices/platforms operating thereon.

[0046] Turning to FIG. 4 and FIG. 5, in some embodiments, the exemplary' computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer- based components of the present disclosure may be specifically configured to operate in a cloud computing/architecture 106 such as, but not limiting to: infrastructure a service (laaS) 510, platform as a service (PaaS) 508, and/or softw are as a service (SaaS) 506 using a web brow ser, mobile app, thin client, terminal emulator or other endpoint 504. FIG. 4 and FIG. 5 illustrate schematics of non-limiting implementations of the cloud computing/architecture(s) in which the exemplary computer-based systems for administrative customizations and control of network-hosted APIs of the present disclosure may be specifically configured to operate. [0047] Turning back to FIG. 1, according to some embodiments, database 108 may correspond to a data storage for a platform (e.g., a network hosted platform, such as cloud system 106, as discussed supra), a plurality of platforms, and/or thermostat 102, UE 112 and/or sensors 110. Database 108 may receive storage instruct! ons/requests from, for example, engine 200 (and associated microservices), which may be in any type of known or to be known format, such as, for example, standard query language (SQL). According to some embodiments, database 108 may correspond to any type of known or to be known storage, for example, a memory or memory stack of a device, a distributed ledger of a distributed network (e.g., blockchain, for example), a look-up table (LUT), and/or any other type of secure data repository.

[0048] EIM engine 200, as discussed above and further below in more detail, can include components for the disclosed functionality'. According to some embodiments, EIM engine 200 may be a special purpose machine or processor, and can be hosted by a device on network 104, within cloud system 106, on UE 112, and/or thermostat 102 (and/or on sensors 110). In some embodiments, engine 200 may be hosted by a server and/or set of servers associated with cloud system 106.

[0049] According to some embodiments, as discussed in more detail below, EIM engine 200 may be configured to implement and/or control a plurality of services and/or microservices, where each of the plurality of services/microservices are configured to execute a plurality of workflows associated with performing the disclosed location (e.g., climate) management. Nonlimiting embodiments of such w orkflow s are provided below.

[0050] According to some embodiments, as discussed above, EIM engine 200 may function as an application provided by cloud system 106. In some embodiments, engine 200 may function as an application installed on a server(s). network location and/or other type of network resource associated with system 106. In some embodiments, engine 200 may function as an application installed and/or executing on UE 112 and/or thermostat 102. In some embodiments, such application may be a web-based application accessed by UE 112, thermostat 102 and/or devices associated with sensors 110 over network 104 from cloud system 106. In some embodiments, engine 200 may be configured and/or installed as an augmenting script, program or application (e.g., a plug-in or extension) to another application or program provided by cloud system 106 and/or executing on UE 112, sensors 110 and/or thermostat 102.

[0051] As illustrated in FIG. 2, according to some embodiments, EIM engine 200 includes identification module 202, analysis module 204. determination module 206 and control module 208. It should be understood that the engine(s) and modules discussed herein are non- exhaustive, as additional or fewer engines and/or modules (or sub-modules) may be applicable to the embodiments of the systems and methods discussed. More detail of the operations, configurations and functionalities of engine 200 and each of its modules, and their role within embodiments of the present disclosure will be discussed below.

[0052] Turning to FIG. 3, Process 300 provides non-limiting example embodiments of the disclosed framework that provides features, capabilities and/or functionality for enhanced and/or improved customization and integration of thermostat controls for a location (e.g., home). According to some embodiments, as discussed below, the disclosed framework can function to provide a thermostat, for example, with capabilities to operate certain connected devices/sensors according to controls that correlate to managing certain real-world, real-time events, which can effectuate an improved operational environment via the modified thermostat controls.

[0053] By way of discussion, athermostat with an EIM can support a set of custom relays (e.g., 3 custom relay outputs, for example), which can be used for any type of purpose (e.g.. turning on a device and/or system, opening a gate, turn on lights, and the like, for example). However, existing systems, as discussed herein, and understood by those of skill in the art, currently require a matched sensor terminal to activate such relay (e.g., the sensor connected to a dry contact).

[0054] As discussed herein, the disclosed framework can provide a more agile configuration, where, for example, a matched sensor for each terminal may not be required to activate certain functionality provided via the disclosed framework. For example, a matched sensor for light activation may not be required to trigger and execute light controls based on the disclosed computational analysis and understanding of a location’s operation, as executed via the engine 200 in accordance with a thermostat and/or EIM.

[0055] As discussed in more detail below, in some embodiments, the disclosed framework, via engine 200, can provide functionality related to, but not limited to: determining and scheduling options for a custom relay output where the custom relay output can be configured to turn on or off at a certain time of the day, for all days, certain days, just weekends, and the like; providing a “On/Off ’ activation on a mobile application (“App”) to dynamically turn the output on/off (e.g., for example, unlocking an electronic gate), and the like. As mentioned above, engine 200 can operate such functionality via any device that supports custom outputs and has timekeeping and/or App connectivity. [0056] According to some embodiments, Step 302 can be performed by identification module 202 of EIM engine 200; Steps 304 and 310 can be performed by analysis module 204; Steps 306, 308 and 314 can be performed by determination module 206; and Steps 312, 316 and 318 can be performed by control module 208.

[0057] According to some embodiments, Process 300 begins with Step 302 where engine 200 can monitor and collect sensor data related to a location. According to some embodiments, such monitoring can occur according to, but not limited to, periodically, continuously, a criteria, a detected event, request, and the like, or some combination thereof. In some embodiments, such criteria can correspond to, but is not limited to, measurements, a time period, date, user identity (ID), threshold values (e.g., measurements meet or satisfy a threshold - for example, a temperature is at or below a threshold, for example), mode/settings on the thermostat, and the like, or some combination thereof.

[0058] According to some embodiments, the collection can be specific to sensors and/or devices at the location, which can correspond to and/or indicate data related to the sensors/devices operations, detected measurements/values, modes, type, timestamps, and the like, or some combination thereof. In some embodiments, the collected sensor data can be stored in database 108, as discussed above.

[0059] In Step 304, engine 200 can analyze the collected sensor data. In some embodiments, the sensor data can be parsed, whereby data and/or metadata related to a detected event can be identified and/or extracted from the data. For example, event information can be identified, which can be related to, but not limited to, the sensor/ device collecting the data, position within the location (e.g.. which room, which floor, and the like) of the sensor/device, the measurement, time period, and the like, or some combination thereof.

[0060] Thus, in Step 306, engine 200 can determine information a type of event (e g., what activity occurred in the location - for example, did a user approach a gate or open a door, turn on lights, adjust the temperature on the thermostat, open a window, and the like, or some combination thereof). For example, in Step 306, engine 200 can determine that actions and/or ty pes of activities occurred at a portion/position within the location. And in Step 308, engine 200 can determine which actions correspond to the events. For example, in Step 306, engine 200 can determine that a door opened, and in Step 308, engine 200 can determination information related to which person (e.g., identity and/or action they performed (e.g., entered security code)) performed the actions to perform the event type. [0061] In some embodiments. Steps 306 and 308 can be performed in a single operational step by engine 200; and, in some embodiments, Steps 306 and 308 can be performed in any operational order.

[0062] In some embodiments, engine 200 can implement any type of known or to be known computational analysis technique, algorithm, mechanism or technology to perform the analysis and determination in Steps 304-308.

[0063] In some embodiments, engine 200 may include a specific trained artificial intelligence / machine learning model (AI/ML), a particular machine learning model architecture, a particular machine learning model type (e.g., convolutional neural network (CNN), recurrent neural network (RNN), autoencoder, support vector machine (SVM), and the like), or any other suitable definition of a machine learning model or any suitable combination thereof.

[0064] In some embodiments, engine 200 may be configured to utilize one or more AI/ML techniques chosen from, but not limited to, computer vision, feature vector analysis, decision trees, boosting, support-vector machines, neural networks, nearest neighbor algorithms, Naive Bayes, bagging, random forests, logistic regression, and the like. By way of a non-limiting example, engine 200 can implement an XGBoost algorithm for regression and/or classification to analyze the sensor data, as discussed herein.

[0065] According to some embodiments and. optionally, in combination of any embodiment described above or below, a neural network technique may be one of, without limitation, feedforward neural network, radial basis function network, recurrent neural network, convolutional network (e.g., U-net) or other suitable network. In some embodiments and, optionally, in combination of any embodiment described above or below, an implementation of Neural Network may be executed as follows: a. define Neural Network architecture/model, b. transfer the input data to the neural network model, c. train the model incrementally, d. determine the accuracy for a specific number of timesteps, e. apply the trained model to process the newly-received input data, f. optionally and in parallel, continue to train the trained model with a predetermined periodicity.

[0066] In some embodiments and, optionally, in combination of any embodiment described above or below, the trained neural network model may specify a neural network by at least a neural network topology, a series of activation functions, and connection weights. For example, the topology of a neural network may include a configuration of nodes of the neural network and connections between such nodes. In some embodiments and, optionally, in combination of any embodiment described above or below, the trained neural network model may also be specified to include other parameters, including but not limited to, bias values/functions and/or aggregation functions. For example, an activation function of a node may be a step function, sine function, continuous or piecewise linear function, sigmoid function, hyperbolic tangent function, or other type of mathematical function that represents a threshold at which the node is activated. In some embodiments and, optionally, in combination of any embodiment described above or below, the aggregation function may be a mathematical function that combines (e.g.. sum. product, and the like) input signals to the node. In some embodiments and. optionally, in combination of any embodiment described above or below, an output of the aggregation function may be used as input to the activation function. In some embodiments and, optionally, in combination of any embodiment described above or below, the bias may be a constant value or function that may be used by the aggregation function and/or the activation function to make the node more or less likely to be activated.

[0067] In some embodiments, the determined information from Step 306 and Step 308 can be stored in database 108, as discussed above.

[0068] In Step 310, engine 200 can analyze the determined information from Step 306 and Step 308, which can be performed via any of the known or to be known AI/ML model techniques discussed above. In Step 312, engine 200 can store the event and action information (from Steps 306-308, and analyzed in Step 310). Such storage can enable and/or facilitate training and/or updating the AI/ML models that perform the disclosed analysis steps, as discussed herein.

[0069] In Step 314, based on a computational and comparative analysis in Step 310. engine 200 can determine a set of controls related to a device at the location. For example, such controls can correspond to the device that i) triggered the collection of the sensor data and/or perform the action associated with the event type (from Step 306) and activity (from Step 308).

[0070] According to some embodiments, the set of controls can correspond to operations that include, but are not limited to, activating, deactivating, scheduling, setting to a time period, setting permissions (e.g., for particular users and/or times of day, for example), and the like. Such controls can correspond to a thermostat and/or any of the sensors/devices within the location. For example, the thermostat can be configured to trigger a mode according to the event type. In another example, a sensor can be triggered to open upon detection of an event (e.g.. detect to disarm the security panel upon detection of a particular user ID). [0071] According to some embodiments, information related to such set of controls can be stored in database 108, as discussed above.

[0072] In Step 316, engine 200 can compile the set of controls for presentation on a device (e.g., on thermostat 102 and/or UE 112, for example). In some embodiments, the presentation can occur via a notification and/or message communicated to and/or via an application, whereby the set of controls are actionable and/or enabled via the application (e.g., an App executing on a UE of the user). According to some embodiments, the set of controls can be configured as features and/or non-native functionality' to a system or device (e.g., HVAC system and/or thermostat 102, for example), where they can be presented as interactive interface objects (IOs). whereby upon interaction with them, either via user input and/or engine 200 instructions, corresponding controls and/or operations can be triggered or caused to be performed that manipulate and/or modify how the system/device was previously configured to perform.

[0073] And, in Step 318. engine 200 executes at least one of the set of controls. Such execution can be in response to, but not limited to, input from a user, input from a device (e.g., UE 112. thermostat 102, sensor(s) 110 and/or a device associated with cloud system 106), a determined schedule, detection of a future event that corresponds to the type of event in Step 306, for example, and the like, or some combination thereof. Accordingly, in some embodiments, the execution of a control(s) causes a device/sensor within the system associated with the device executing engine 200 to perform actions that are controlled via the executed instructions associated with the selected control. For example, thermostat 102 can cause a control to be executed that causes a damper to open within an HVAC system associated with the thermostat 102 when particular temperatures and/or air flow values are detected.

[0074] Thus, the disclosed framework can function to provide a thermostat, for example, with capabilities to operate certain connected devices/sensors according to controls that correlate to managing certain real-world, real-time events, which can effectuate an improved operational environment via the modified thermostat controls

[0075] FIG. 6 is a schematic diagram illustrating a client device showing an example embodiment of a client device that may be used within the present disclosure. Client device 600 may include many more or less components than those shown in FIG. 6. However, the components shown are sufficient to disclose an illustrative embodiment for implementing the present disclosure. Client device 600 may represent, for example, UE 112 discussed above at least in relation to FIG. 1. [0076] As shown in the figure, in some embodiments, Client device 600 includes a processing unit (CPU) 622 in communication with a mass memory 630 via a bus 624. Client device 600 also includes a power supply 626, one or more network interfaces 650, an audio interface 652, a display 654, a keypad 656, an illuminator 658, an input/output interface 660, ahaptic interface 662, an optional global positioning systems (GPS) receiver 664 and a camera(s) or other optical, thermal or electromagnetic sensors 666. Device 600 can include one camera/sensor 666, or a plurality of cameras/sensors 666, as understood by those of skill in the art. Power supply 626 provides power to Client device 600.

[0077] Client device 600 may optionally communicate with a base station (not shown), or directly with another computing device. In some embodiments, network interface 650 is sometimes known as a transceiver, transceiving device, or netw ork interface card (NIC).

[0078] Audio interface 652 is arranged to produce and receive audio signals such as the sound of a human voice in some embodiments. Display 654 may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), or any other type of display used with a computing device. Display 654 may also include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand.

[0079] Keypad 656 may include any input device arranged to receive input from a user. Illuminator 658 may provide a status indication and/or provide light.

[0080] Client device 600 also includes input/output interface 660 for communicating with external. Input/output interface 660 can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like in some embodiments. Haptic interface 662 is arranged to provide tactile feedback to a user of the client device.

[0081] Optional GPS transceiver 664 can determine the physical coordinates of Client device 600 on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver 664 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD. CI, SAI, ETA, BSS or the like, to further determine the physical location of client device 600 on the surface of the Earth. In one embodiment, however, Client device 600 may through other components, provide other information that may be employed to determine a physical location of the device, including for example, a MAC address, Internet Protocol (IP) address, or the like.

[0082] Mass memory 630 includes a RAM 632, a ROM 634, and other storage means. Mass memory 630 illustrates another example of computer storage media for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory 630 stores a basic input/output system (' BIOS’ ) 640 for controlling low-level operation of Client device 600. The mass memory also stores an operating system 641 for controlling the operation of Client device 600.

[0083] Memory' 630 further includes one or more data stores, which can be utilized by Client device 600 to store, among other things, applications 642 and/or other information or data. For example, data stores may be employed to store information that describes various capabilities of Client device 600. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header (e.g., index file of the HLS stream) during a communication, sent upon request, or the like. At least a portion of the capability information may also be stored on a disk drive or other storage medium (not shown) within Client device 600.

[0084] Applications 642 may include computer executable instructions which, when executed by Client device 600, transmit, receive, and/or otherwise process audio, video, images, and enable telecommunication with a server and/or another user of another client device. Applications 642 may further include a client that is configured to send, to receive, and/or to otherwise process gaming, goods/services and/or other forms of data, messages and content hosted and provided by the platform associated with engine 200 and its affiliates.

[0085] As used herein, the terms “computer engine" and "engine" identify at least one software component and/or a combination of at least one software component and at least one hardware component which are designed/programmed/configured to manage/control other software and/or hardware components (such as the libraries, software development kits (SDKs), objects, and the like).

[0086] Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s). and so forth. [0087] Computer-related systems, computer systems, and systems, as used herein, include any combination of hardware and software. Examples of software may include software components, programs, applications, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computer code, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance w ith any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

[0088] For the purposes of this disclosure a module is a software, hardware, or firmware (or combinations thereof) system, process or functionality, or component thereof, that performs or facilitates the processes, features, and/or functions described herein (with or without human interaction or augmentation). A module can include sub-modules. Software components of a module may be stored on a computer readable medium for execution by a processor. Modules may be integral to one or more servers, or be loaded and executed by one or more servers. One or more modules may be grouped into an engine or an application.

[0089] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores,” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Of note, various embodiments described herein may, of course, be implemented using any appropriate hardware and/or computing software languages (e.g., C++, Objective-C, Swift, Java, JavaScript, Python, Perl, QT, and the like).

[0090] For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may be downloadable from a network, for example, a website, as a stand-alone product or as an add-in package for installation in an existing software application. For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be available as a client-server software application, or as a web-enabled software application. For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be embodied as a software package installed on a hardware device.

[0091] For the purposes of this disclosure the term “user”, “subscriber” “consumer” or “customer” should be understood to refer to a user of an application or applications as described herein and/or a consumer of data supplied by a data provider. By way of example, and not limitation, the term “user” or “subscriber” can refer to a person who receives data provided by the data or sen-ice provider over the Internet in a browser session, or can refer to an automated software application which receives the data and stores or processes the data. Those skilled in the art will recognize that the methods and systems of the present disclosure may be implemented in many manners and as such are not to be limited by the foregoing exemplary embodiments and examples. In other words, functional elements being performed by single or multiple components, in various combinations of hardware and software or firmware, and individual functions, may be distributed among software applications at either the client level or server level or both. In this regard, any number of the features of the different embodiments described herein may be combined into single or multiple embodiments, and alternate embodiments having fewer than, or more than, all of the features described herein are possible. [0092] Functionality may also be, in whole or in part, distributed among multiple components, in manners now known or to become known. Thus, myriad software/hardware/firmware combinations are possible in achieving the functions, features, interfaces and preferences described herein. Moreover, the scope of the present disclosure covers conventionally known manners for carrying out the described features and functions and interfaces, as well as those variations and modifications that may be made to the hardware or software or firmware components described herein as would be understood by those skilled in the art now and hereafter.

[0093] Furthermore, the embodiments of methods presented and described as flowcharts in this disclosure are provided by way of example in order to provide a more complete understanding of the technology. The disclosed methods are not limited to the operations and logical flow presented herein. Alternative embodiments are contemplated in which the order of the various operations is altered and in which sub-operations described as being part of a larger operation are performed independently.

[0094] While various embodiments have been described for purposes of this disclosure, such embodiments should not be deemed to limit the teaching of this disclosure to those embodiments. Various changes and modifications may be made to the elements and operations described above to obtain a result that remains within the scope of the systems and processes described in this disclosure.

Claims

CLAIMS What is claimed is:

1. A method comprising: collecting, over a network, sensor data from a device, the device being part of a location control system at a location; analyzing the collected sensor data, and determining, based on the analysis, event information, the event information corresponding to activity' at the location associated with the sensor data from the device; analyzing the event information, and determining a set of controls for the device, the set of controls comprising a set of features that are non-native to the location control system, each set of control corresponds to an action taken by the device; and causing display, within a control device of the location control system, of the set of controls, the displayed set of controls being presented as interactive interface objects (IOs).

2. The method of claim 1, further comprising: communicating, over the network, a message to a user device, the user device comprising an application associated with the location control system, wherein the caused display further comprises displaying the IOs within an interface of the application on the user device.

3. The method of claim 1. further comprising: executing, in response to a detected input instruction, at least one of the set of controls, the execution comprising the device to perform a respective action related to a respective feature.

4. The method of claim 1. further comprising: determining, based on the analysis of the collected sensor data, a type of event, wherein the event information comprises information related to the type of event; and determining, based on the analysis of the collected sensor data, at least one action for an event, wherein the event information comprises information related to the at least one action.

5. The method of claim 1, further comprising: determining a schedule for an event that corresponds to the event information; and causing at least one of the set of controls to be performed according to the schedule.

6. The method of claim 1, wherein the event information is stored in a database, wherein the stored event information is utilized to train a computer model that performs the analysis of the collected sensor data and analysis of the event information.

7. The method of claim 1, wherein the device is a thermostat.

8. The method of claim 1. wherein the location comprises a definable physical area for the location control system is associated, wherein the location control system comprises functionality related to at least one of climate control and security-.

9. A system comprising: a processor configured to: collect, over a network, sensor data from a device, the device being part of a location control system at a location; analyze the collected sensor data, and determine, based on the analysis, event information, the event information corresponding to activity at the location associated with the sensor data from the device; analyze the event information, and determine a set of controls for the device, the set of controls comprising a set of features that are non-native to the location control system, each set of control corresponds to an action taken by the device; and cause display, within a control device of the location control system, of the set of controls, the displayed set of controls being presented as interactive interface objects (IOs).

10. The system of claim 9, wherein the processor is further configured to: communicate, over the network, a message to a user device, the user device comprising an application associated with the location control system, wherein the caused display further comprises displaying the IOs within an interface of the application on the user device.

11. The system of claim 9, wherein the processor is further configured to: execute, in response to a detected input instruction, at least one of the set of controls, the execution comprising the device to perform a respective action related to a respective feature.

12. The system of claim 9, wherein the processor is further configured to: determine, based on the analysis of the collected sensor data, a type of event, wherein the event information comprises information related to the type of event; and determine, based on the analysis of the collected sensor data, at least one action for an event, wherein the event information comprises information related to the at least one action.

13. The system of claim 9, wherein the processor is further configured to: determine a schedule for an event that corresponds to the event information; and cause at least one of the set of controls to be performed according to the schedule.

14. The system of claim 9, wherein the event information is stored in a database, wherein the stored event information is utilized to train a computer model that performs the analysis of the collected sensor data and analysis of the event information.

15. A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions that when executed by a processor, perform a method comprising: collecting, over a network, sensor data from a device, the device being part of a location control system at a location; analyzing the collected sensor data, and determining, based on the analysis, event information, the event information corresponding to activity at the location associated with the sensor data from the device; analyzing the event information, and determining a set of controls for the device, the set of controls comprising a set of features that are non-native to the location control system, each set of control corresponds to an action taken by the device; and causing display, within a control device of the location control system, of the set of controls, the displayed set of controls being presented as interactive interface objects (IOs).

16. The non-transitory computer-readable storage medium of claim 15, further comprising: communicating, over the network, a message to a user device, the user device comprising an application associated with the location control system, wherein the caused display further comprises displaying the IOs within an interface of the application on the user device.

17. The non-transitory' computer-readable storage medium of claim 15, further comprising: executing, in response to a detected input instruction, at least one of the set of controls, the execution comprising the device to perform a respective action related to a respective feature.

18. The non-transitory computer-readable storage medium of claim 15, further comprising: determining, based on the analysis of the collected sensor data, a type of event, wherein the event information comprises information related to the type of event; and determining, based on the analysis of the collected sensor data, at least one action for an event, wherein the event information comprises information related to the at least one action.

19. The non-transitory' computer-readable storage medium of claim 15, further comprising: determining a schedule for an event that corresponds to the event information; and causing at least one of the set of controls to be performed according to the schedule.

20. The non-transitory computer-readable storage medium of claim 15, wherein the event information is stored in a database, wherein the stored event information is utilized to train a computer model that performs the analysis of the collected sensor data and analysis of the event information.