System and method for a smart thermostat

Abstract

Disclosed are systems and methods that provide a novel framework for a decision intelligence (DI)-based computerized framework for computationally controlling and outputting displayed climate information within a smart thermostat in a dynamic, real-time manner. The disclosed framework can be implemented, executed in association thereof and / or integrated into the operation of a smart thermostat enabling the deployment of a user-friendly interface (e.g., a user interface (UI)) that facilitates seamless scrolling through a wealth of data, providing users with comprehensive insights into its features, collected data, and controls. The thermostat interface enables swift compilation, consumption and adjustment of temperature settings, scheduling preferences and operational modes, empowering users to tailor their climate system operation to their exact preferences and lifestyle needs. This, among other benefits, ensures that users can delve into pertinent information and exercise precise control over their indoor climate management with unparalleled ease and efficiency.

Description

SYSTEM AND METHOD FOR A SMART THERMOSTATCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of, and priority to, U.S. Provisional Patent Application No. 63 / 573.848 filed April 3, 2024, its entirety of which is incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] The present disclosure is generally related to climate management at a location, and more particularly, to a decision intelligence (Dl)-based computerized framework for computationally controlling and outputting displayed climate information within a smart thermostat in a dynamic, real-time manner.BACKGROUND

[0003] A smart thermostat is a device that can control the heating, ventilation, and air conditioning (HVAC) system of a home or building based on user preferences, schedule, and environmental conditions.SUMMARY OF THE DISCLOSURE

[0004] Smart thermostats typically connect to the internet via a Wireless Fidelity (WiFi or WiFi network), allowing remote access and control through a smartphone app or a web interface. Smart thermostats often feature sensors to detect occupancy, temperature and humidity7, inter alia, enabling them to automatically adjust settings for energy efficiency and comfort. They may also incorporate advanced features such as learning algorithms to adapt to users’ behavior over time and integration with other smart home devices (e g., Internet of Things (loT) devices) for enhanced automation and convenience.

[0005] According to some embodiments, as discussed herein, the disclosed framework can be implemented, executed in association thereof and / or integrated into the operation of a smart thermostat enabling the deployment of a user-friendly interface (e.g., a user interface (UI)) that facilitates seamless scrolling through a wealth of data, providing users with comprehensive insights into its features, collected data, and controls. According to some embodiments, for example, as discussed in more detail below, such scrolling can be enabled via a ticker data structure that can be displayed and / or rendered on a display screen of the smart thermostat, which can embody and / or enable the disclosed functionality disclosed herein. Accordingly, insome embodiments, through the disclosed interactive display of the disclosed ticker data structure, users can navigate through various displays and / or screen implementations effortlessly, accessing real-time information such as current temperature readings, indoor humidity levels, and detailed breakdow ns of energy usage patterns.

[0006] In some embodiments, the disclosed thermostat interface enables swift adjustment of temperature settings, scheduling preferences and operational modes, empowering users to tailor their climate system operation to their exact preferences and lifestyle needs. Accordingly, whether accessing the thermostat from within the home or remotely via a smartphone app or web portal, the intuitive scrolling functionality provided via the disclosed UI capabilities ensures that users can delve into pertinent information and exercise precise control over their indoor climate management with unparalleled ease and efficiency.

[0007] Thus, the disclosed framework provides operational functionality and capabilities for the control and mapping of current within a furnace, inclusive of a mapping of a combination of electrical components working together to regulate and distribute power to the various systems responsible for heating and circulating air. Moreover, as discussed below in more detail, the mapped current values for the furnace and / or its components can be tracked and leveraged by a cloud system and / or cloud-based systems, so that virtual control of the furnace and / or the associated climate system can be effectuated therefrom.

[0008] It should be understood that while the discussion herein may focus on the implementation of a climate control system (e.g., HVAC, for example) that has and / or operates, in part, via a thermostat, it should not be construed as limiting, as any ty pe of climate control system / equipment and / or security equipment, for example, can implement the disclosed functionality to apprise a viewing user and / or connected devices as to the compiled, utilized and / or displayed information, as discussed herein, without departing from the scope of the instant disclosure.

[0009] Further, a location, as discussed herein, can refer to, but is not limited to, a building, home, office, and / or any other location for which a climate system can be applied to provide climate control for the location.

[0010] According to some embodiments, a method is disclosed for a Dl-based computerized framework for controlling and outputting displayed climate information within a smart thermostat in a dynamic, real-time manner. 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-transitorycomputer-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 for controlling and outputting displayed climate information within a smart thermostat in a dynamic, real-time manner.

[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 A 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. IB is a block diagram illustrating components of an exemplary system according to some embodiments of the present disclosure;

[0015] FIG. 2A, FIG. 2B and FIG. 2C depict non-limiting example embodiments according to some embodiments of the present disclosure;

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

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

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

[0019] 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

[0020] 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 hardware, 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.

[0021] 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.

[0022] 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, allow7for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

[0023] 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 functionality / acts involved.

[0024] 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.

[0025] 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, aswell as operating software and one or more database systems and application software that support the services provided by the server. Cloud servers are examples.

[0026] 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.

[0027] 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 networks, 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, 4thor 5thgeneration (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.

[0028] 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 network, or the like.

[0029] 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.

[0030] 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.

[0031] 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 fype capability’, or a display with a high degree of functionality, such as a touch-sensitive color 2D or 3D display, for example.

[0032] Certain embodiments and principles will be discussed in more detail with reference to the figures. With reference to FIG. 1A, system 100 is depicted which includes user equipment (UE) 102 (e.g.. a client device, as mentioned above and discussed below in relation to FIG. 6). network 104. cloud system 106. database 108, sensor(s) 110 and display 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 UEs, cloud systems, databases, computer sy stems and / or networks can be utilized; however, for purposes of explanation, system 100 is discussed in relation to the example depiction in FIG. 1A.

[0033] According to some embodiments, UE 102 can be any type of device, such as, but not limited to, a mobile phone, tablet, laptop, sensor, smart television (TV) Internet of Things (loT) device, autonomous machine, wearable device, and / or any other device equipped with a cellular or wireless or wired transceiver. For example, UE 102 can be a thermostat, sensor, control panel, and / or any other type of device that can provide functionality' related to operation of a climate control system. In some embodiments, as discussed below, UE 102, as a thermostat, for example, can display and render the disclosed ticker data structure.

[0034] In some embodiments, a peripheral device (not shown) can be connected to UE 102, and can be any type of peripheral device, such as, but not limited to, a wearable device (e.g., smart ring or smart watch), printer, speaker, sensor, and the like. In some embodiments, a peripheral device can be any type of device that is connectable to UE 102 via any ty pe of known or to be known pairing mechanism, including, but not limited to, WiFi, Bluetooth™, Bluetooth Low Energy (BLE), NFC, and the like.

[0035] According to some embodiments, sensors 110 (or sensor devices 110) can correspond to any type of device, component and / or sensor associated with a location of system 100 (referred to, collectively, as ‘’sensors”). In some embodiments, the sensors 110 can be any type of device that is capable of sensing and capturing data / metadata related to a user and / or activity of the location. For example, the sensors 110 can include, but not be limited to, cameras, motion detectors, door and window contacts, temperature, humidity, barometer, wind, rain, heat and smoke detectors, passive infrared (PIR) sensors, time-of-flight (ToF) sensors, and the like. In some embodiments, the sensors 110 can 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 rings, smart phones, smart watches or other wearables, tablets, personal computers, and the like, and some combination thereof.

[0036] 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. 1A.

[0037] 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 location monitoring and / or control system provider (e.g., Resideo®), which has associated network resources hosted on the internet or private network (e.g., network 104), which enables (via engine 200) the library and / or media management discussed herein.

[0038] 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 the components of system 100 and / or each of the components of system 100 (e.g., UE 102, and the services and applications provided by cloud system 106 and / or display engine 200).

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

[0040] 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 as a service (laaS) 510, platform as a service (PaaS) 508, and / or software as a service (SaaS) 506 using a web browser, 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 application program interfaces (APIs) of the present disclosure may be specifically configured to operate.

[0041] Turning back to FIG. 1A, 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) or a plurality of platforms. Database 108 may receive storage instructions / requests from, for example, engine 200 (and associated microservices), which may be in any type of known or to be know n 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

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

[0043] According to some embodiments, as discussed in more detail below, display engine 200 may be configured to implement and / or control a plurality of services and / or microservices, w here each of the plurality of services / microservices are configured to execute a plurality of workflows associated with performing the disclosed media management. Non-limiting embodiments of such w orkflows are provided below in relation to at least FIG. 3.

[0044] According to some embodiments, as discussed above, display engine 200 may function as an application provided by cloud system 106. In some embodiments, engine 200 mayfunction 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 102. In some embodiments, such application may be a web-based application accessed by UE 102 and / or other devices 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 102.

[0045] As illustrated in FIG. IB, according to some embodiments, display engine 200 includes identification module 202, analysis module 204, determination module 206 and output 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.

[0046] Turning to FIG. 2A, FIG. 2B and FIG. 2C. depicted are example embodiments for how a UI displayed on an example smart thermostat can provide scrolling features that indicate climate values from a set of climate sensors at a location (e.g., a home). According to some embodiments, as depicted in FIG. 2A, FIG. 2B and FIG. 2C, the scrolling ticker is displayed at the bottom portion of the UI displayed on the display of the thermostat, and scrolls along the x-axis at a rate from right to left. In some embodiments, the ticker may be along another axis (e g., y-axis, or in some embodiments, z-axis, for virtual reality and / or augmented reality (VR / AR) displays, for example). In some embodiments, the ticker may scroll at a rate proportional to the number of items being displayed (e.g., the rate of scroll may increase when more items are being displayed). In some embodiments, the rate of scroll may be at a predetermined rate and / or user set and / or adjustable rate. Such scrolling, as discussed herein, enables the items / values to be displayed for a predetermined time, and to be recursively displayed given a repetitive / cyclical nature of the scroll.

[0047] In some embodiments, the items displayed within the ticker may be interactive, such that upon user interaction with a displayed item, controls and / or further information related to that area within the location may be provided. For example, as in FIG. 2A, while the item for the “Hallway 74°” is displayed, it can be interacted with, which can lead to, but not be limited to, display of climate controls for the Hallway sensors at the location, provide controls for the HVAC components serving the Hallway, provide a display of other Hallway relatedinformation (e.g., activity in that location, scheduled controls, presets, humidity, air quality, carbon dioxide, light, radon, and the like), and the like.

[0048] Turning to FIG. 3, Process 300 provides non-limiting example embodiments for the disclosed climate and location management framework. According to some embodiments, Steps 302, 304 and 314 can be performed by identification module 202 of display engine 200; Step 306 can be performed by analysis module 204; Steps 308 and 310 can be performed by determination module 206; and Steps 312 and 316 can be performed by output module 208.

[0049] According to some embodiments, Process 300 begins with Step 302 where engine 200 can monitor a location via a set of devices. As discussed above, the set of devices can include, but are not limited to UE 102 and sensors 110, which can include, but are not limited to, a thermostat and a plurality of climate sensors at the location. In some embodiments, the sensors can be associated with devices in / around the location. Additional, non-limiting examples of sensors and the t pes of collectable data are discussed above at least in relation to FIG. 1.

[0050] In some embodiments, the set of devices can be connected to engine 200. According to some embodiments, engine 200 can operate as, and / or in conjunction with, a centralized “control panel’’ for a location (e.g., on and / or via UE 102, as discussed supra). Thus, in some embodiments, Step 302 can involve the configuration of each identified sensor and its pairing / connection with UE 102 / engine 200 and / or each other.

[0051] Accordingly, in some embodiments, with reference to FIG. 1, for example, sensors 110 can be paired with each other, with engine 200 and / or UE 102, which can be paired via connectivity protocols provided and / or enabled via engine 200. For example, a climate sensor 110 can be paired / connected with another climate sensor 110, engine 200 and / or UE 102 via BLE technology. In some embodiments, the sensors 110 can be paired and / or connected with another sensor 110, engine 200 and / or UE 102 via a physical wire connection (e.g., fiber, ethemet, coaxial, and / or any other type of known or to be known wiring to hardwire a home for network connectivity for devices operating therein). In some embodiments, the sensors 110 can be paired / connected with another sensor 110, engine 200 and / or UE 102 via a cloud-to-cloud (C2C) connection (e.g., establish connection with a third party cloud, which connects with cloud system 106, for example). In some embodiments, the sensors 110 can be paired / connected via a combination of network capabilities, hard wiring and / or C2C. In some embodiments, the sensors 110 can be paired so as to enable an extended reach of the sensor’s configuration to detect specific types of events and / or types of climate data.

[0052] In Step 304, data can be collected from each or the set of devices. In some embodiments, engine 200 can operate to trigger the identified devices to begin collecting sensor / climate data. According to some embodiments, the sensor (or climate, used interchangeably) data can be collected continuously and / or according to a predetermined period of time or interval. In some embodiments, sensor data may be collected based on detected events. In some embodiments, type and / or quantity of sensor data may be directly tied to the type of sensor. For example, a temperature sensor may collect temperature data.

[0053] In some embodiments, the collected sensor data in Step 304 can be stored in database 108 in association with an identifier (ID) of a user, sensor, location and / or account of the user / location.

[0054] In Step 306. engine 200 can analyze the collected sensor data. According to some embodiments, engine 200 can implement any type of known or to be known computational analysis technique, algorithm, mechanism or technology to analyze the collected sensor data from Step 306.

[0055] In some embodiments, engine 200 may include a specific trained artificial intelligence I 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.

[0056] In some embodiments, engine 200 may be configured to utilize one or more Al / 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.

[0057] In some embodiments and, optionally, in combination of any embodiment described above or below, a neural network technique may be one of, without limitation, feedforw ard neural network, radial basis function network, recunent 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.

[0058] 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 topology7of a neural netw ork 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.

[0059] In Step 308, based on the analysis from Step 306, engine 200 can determine a set of sensed values. For example, as depicted in FIG. 2A, FIG. 2B and FIG. 2C, temperature values for the Hall ay, Guest Bedroom and Dining Room can be collected, compiled and determined. Such values can be an aggregate or average of the collection period, or can be a real-time reflection of the temperature values for each location. In some embodiments, the values compiled and determined can be subject to a request (e.g., a user input a request for those specific values).

[0060] In some embodiments, the compilation and determination of such values can be based on a determination that a person (or other living thing, for example, a pet) is in that area, such that the climate / temperature value is of value to the viewing user. Thus, for example, in someembodiments, Step 308’s determination can leverage presence or activity data from the collected sensor data to determine where specific values are required within the location, and utilize such determination to compile the values that are to be used for the ticker, as discussed infra.

[0061] In Step 310, engine 200 can operate to compile a ticker, which can be a sequential order of the set of sensed values (from Step 308). The sensed values can be compiled and / or configured to be displayed with a label (or identifier (ID) that indicates a portion or area of the location for which the value corresponds. In some embodiments, the sequential order can be, but is not limited to, a ranking of the values from high to low or low to high, alphabetical, ordered based on which values have changed the most, ordered based on which values need to be remedied via the climate system’s activation (e.g.. turn on AC to lower the temperature in the Hallway, for example), based on a user preset and / or time of day, and the like.

[0062] In some embodiments, the ticker can be compiled and / or generated as a data structure, which can scroll, as depicted in FIG. 2A, FIG. 2B and FIG. 2C.

[0063] By way of a non-limiting example, with reference to Steps 302-310, a ticker data structure can be compiled, as discussed supra, from values by collecting real-time data from various sources, such as sensors at the location, and then organizing this data into a format suitable for display. In some embodiments, climate sensor data can be compiled into a scrolling ticker for display within a UI of and / or associated with a thermostat. As discussed above, engine 200 can collect data (e.g., integer values) representing different climate parameters such as temperature, humidity, air quality, and the like. Such sensor values can be continuously sampled and updated at regular intervals (e.g., in milliseconds or seconds, for example), depending on the required resolution and responsiveness of the climate system. Once collected, data can be compiled into a data structure that organizes them in a way that facilitates efficient retrieval and display. This data structure (e g., the ticker) can be an array, list, or other suitable data structure depending on the programming language and requirements of the UI and / or thermostat (e.g., UE 102). According to some embodiments, each value in the ticker corresponds to a specific climate parameter at a particular point in time, as depicted in and discussed above in relation to FIG. 2A, FIG. 2B and FIG. 2C.

[0064] According to some embodiments, the scrolling ticker can be fed to a UI that is capable of rendering scrolling text or numerical data, as discussed below. The UI component responsible for displaying the ticker continuously updates its content with the latest sensor values retrieved and compiled from the data structure (e.g., which is indicated via the recursiveline from Step 314 to Step 304). As new sensor data is collected and added to the data structure, older values are shifted or removed to make room for the new data, creating a scrolling effect. This process ensures that users can view the most recent climate information in real-time as it is being collected by the sensors.

[0065] According to some embodiments, the values compiled within the ticker can be compiled in other displayable data structure forms and / or formats, which one of skill in the art would readily understand. Accordingly, in some embodiments, the sequential compilation of climate values (e.g., temperature, for example) can correspond to, but are not limited to, displayable interface objects (IOs) or items that are capable of depicting at least one value, then another value to delineate that the values differ from the other values as to the information they are representing and an area of a location they are associated with. For example, a first value (for the Hallway) can be depicted, and the data structure of the values can be rendered such that another value (for the bedroom) can then be displayed. Accordingly, in some embodiments, the transitions between such values may not be limited to scrolling, as they can additionally include, but are not limited to. fade ins / fade outs, pixelations, replacements (e.g.. on / off), bouncing, gliding, and the like, and / or any other type of graphical transition that can indicate a differentiation between a displayed value and a newly displayed value.

[0066] Continuing with Process 300, in Step 312, engine 200 causes the output of the ticker to the UI. As discussed above, such output can produce the ticker to render in a manner that causes the scrolling discussed above and depicted in FIG. 2A, FIG. 2B and FIG. 2C. discussed supra.

[0067] Upon display of the ticker in Step 314, engine 200 can proceed to Step 314, where the sensors within the set of devices can be continuously monitored so that the values within the ticker can be updated to reflect the current values of the monitored climate system. Thus, as discussed above, can cause updated data to be collected, which can cause the process to revert back to Step 304.

[0068] In some embodiments, Step 314 can involve monitoring for input, which as discussed above, can be respective to the display of data, and / or display and / or rendering of controls via the thermostat.

[0069] In some embodiments. Process 300 can proceed to Step 316, where engine 200 can cause and / or execute a control operation(s) respective to at least a portion of the set of devices. Such controls can be based on the input detected from Step 314, discussed supra. For example, such controls can cause the thermostat and / or climate system (e.g., and / or sensors) to operate in a manner that is modified from a prior manner. For example, a user can double click on theitem for the “Hallway,” for example, as depicted in FIG. 2A, and this can cause the AC to turn on to lower the temperature for that zone in the house. Such AC execution can be automatic based on the input, or can be subject to controls presented in response to the input, which enable the AC to be turned on.

[0070] Thus, as discussed above, the disclosed framework enables efficient compilation, consumption and adjustment of temperature settings, scheduling preferences and operational modes, empowering users to tailor their climate system operation to their exact preferences and lifestyle needs. This, among other benefits, ensures that users can delve into pertinent information and exercise precise control over their indoor climate management with unparalleled ease and efficiency.

[0071] 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 102 discussed above at least in relation to FIG. 1 A.

[0072] 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. adisplay 654, akeypad 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.

[0073] 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 network interface card (NIC).

[0074] 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.

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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 tootherwise 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.

[0081] 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.

[0082] 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 with 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.

[0083] 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.

[0084] 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,’7may be stored on atangible, 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).

[0085] For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may be dow nloadable 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, exemplary7software 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 softw are specifically programmed in accordance w ith one or more principles of the present disclosure may also be embodied as a softw are package installed on a hardw are device.

[0086] 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 service 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 hardw are 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 few er than, or more than, all of the features described herein are possible.

[0087] Functionality may also be, in w hole or in part, distributed among multiple components, in manners now known or to become known. Thus, myriad so I tware / 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 firmwarecomponents described herein as would be understood by those skilled in the art now7and hereafter.

[0088] Furthermore, the embodiments of methods presented and described as flow charts 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 vanous operations is altered and in which sub-operations described as being part of a larger operation are performed independently.

[0089] 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

CLAIMSWhat is claimed is:

1. A method comprising: monitoring, over a network, a location via a set of devices, the set of devices comprising sensors of a system configured to monitor the location; collecting, based on the monitoring, sensor data via each of the sensor sensors; analyzing the sensor data, and determining, for each sensor, a sensed value, each sensed value corresponding to an area of the location that is respectively associated with a respective sensor; generating a ticker data structure, the ticker data structure comprising each sensed value in an order, the ticker data structure configured to scroll upon display so that each sensed value is viewable within a portion of a user interface (UI); and causing rendering of the ticker data structure, the rendering comprising a scrolled display of the ticker data structure.

2. The method of claim 1, further comprising: receiving, upon rendering of the UI, input related to at least one sensed value, wherein the ticker data structure displays the sensed values as interactive items, wherein the input is an interaction with the at least one sensed value.

3. The method of claim 2, further comprising: retrieving additional sensor data for an area related to the at least one sensed value, the additional sensor data being collected sensor data that provides different information from the at least one sensed value: and causing the UI to be updated to display such additional sensor data.

4. The method of claim 2. further comprising: displaying climate controls for an area related to the at least one sensed value, the climate controls enabling modification to a manner the system.

5. The method of claim 1, further comprising the ticker data structure comprising information related to at least one of an alert, reminder or control provided via the system.

6. The method of claim 1, wherein the ticker data structure scrolls at a rate proportional to a number of items being displayed within the rendering of the ticker data structure.

7. The method of claim 1, wherein the display of the UI is within a display of a thermostat, wherein the set of devices further comprises a thermostat.

8. The method of claim 1, wherein the display of the UI is within an application on a user device, wherein the UI enables control of the system via the user device.

9. A system comprising: a processor configured to: monitor, over a network, a location via a set of devices, the set of devices comprising sensors of a system configured to monitor the location; collect, based on the monitoring, sensor data via each of the sensors; analyze the sensor data, and determine, for each sensor, a sensed value, each sensed value corresponding to an area of the location that is respectively associated with a respective sensor; generate a ticker data structure, the ticker data structure comprising each sensed value in an order, the ticker data structure configured to scroll upon display so that each sensed value is viewable within a portion of a user interface (UI); and cause rendering of the ticker data structure, the rendering comprising a scrolled display of the ticker data structure.

10. The system of claim 9, wherein the processor is further configured to: receive, upon rendering of the UI, input related to at least one sensed value, wherein the ticker data structure displays the sensed values as interactive items, wherein the input is an interaction with the at least one sensed value.

11. The system of claim 10, wherein the processor is further configured to:retrieve additional sensor data for an area related to the at least one sensed value, the additional sensor data being collected sensor data that provides different information from the at least one sensed value; and cause the UI to be updated to display such additional sensor data.

12. The system of claim 10, wherein the processor is further configured to: display climate controls for an area related to the at least one sensed value, the climate controls enabling modification to a manner the system, wherein the climate controls correspond to the area.

13. The system of claim 9. wherein the ticker data structure scrolls at a rate proportional to a number of items being displayed within the rendering of the ticker data structure.

14. The system of claim 9, wherein the display of the UI is within a display of a thermostat, wherein the set of devices further comprises a thermostat.

15. A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions, that when executed by a processor, perform a method comprising: monitoring, over a network, a location via a set of devices, the set of devices comprising sensors of a system configured to monitor the location; collecting, based on the monitoring, sensor data via each of the sensors; analyzing the sensor data, and determining, for each sensor, a sensed value, each sensed value corresponding to an area of the location that is respectively associated with a respective sensor; generating a ticker data structure, the ticker data structure comprising each sensed value in an order, the ticker data structure configured to scroll upon display so that each sensed value is viewable within a portion of a user interface (UI); and causing rendering of the ticker data structure, the rendering comprising a scrolled display of the ticker data structure.

16. The non-transitory computer-readable storage medium of claim 15, further comprising: receiving, upon rendering of the UI, input related to at least one sensed value, wherein the ticker data structure displays the sensed values as interactive items, wherein the input is an interaction with the at least one sensed value.

17. The non-transitory computer-readable storage medium of claim 16, further comprising: retrieving additional sensor data for an area related to the at least one sensed value, the additional sensor data being collected sensor data that provides different information from the at least one sensed value; and causing the UI to be updated to display such additional sensor data.

18. The non-transitory computer-readable storage medium of claim 16, further comprising: displaying climate controls for an area related to the at least one sensed value, the climate controls enabling modification to a manner the system, wherein the climate controls correspond to the area.

19. The non-transitory computer-readable storage medium of claim 15, wherein the ticker data structure scrolls at a rate proportional to a number of items being displayed within the rendering of the ticker data structure.

20. The non-transitory computer-readable storage medium of claim 15, wherein the display of the UI is within a display of a thermostat, wherein the set of devices further comprises a thermostat.

Images