Computerized Systems and Methods for Compressed Data Communication Between Devices for a Specifically Configured Network

Disclosed are systems and methods that provide a communication framework that enables computerized functionality for a climate system's improved operation. The disclosed framework enables a location's climate system to be controlled via a centralized hub, which can be accessed remotely using a mobile application or web interface. The enabled communication network and functionality enables dynamic monitoring and control of the devices/components of a location's climate system, which can be effectuated from anywhere (e.g., at the location or away from the location), providing functionality for increased flexibility and convenience. The disclosed communication framework provides a reliable and secure wireless communication platform for climate system components, enabling improved energy efficiency, comfort and control for residential and commercial locations (e.g., buildings).

FIELD OF THE DISCLOSURE

The present disclosure is generally related to a thermostat control system, and more particularly, to a decision intelligence (DI)-based computerized framework for management and control of communications to/from devices of a specifically configured climate control system.

BACKGROUND

Conventional heating, cooling and ventilating (HVAC) systems and baseboard systems (referred to as climate or climate-control systems, used interchangeably) are tasked with performing climate control for a location (e.g., a building, home, office, and the like, for example). Such systems rely on communication networks at the location to rely data/metadata related to the devices operating as part of the climate system.

SUMMARY OF THE DISCLOSURE

Conventional communication networks such climate systems rely on, however, are devoid of the requisite technical capabilities the systems need to adequately detect, relay and/or store system data so as to properly and efficiently operate the climate system at the location. For example, current communication networks (or communication systems, used interchangeably) may not provide the necessary throughput needed to transmit data from one device to another. For example, an outdoor air conditioning (AC) unit may be unable to timely communicate with the indoor furnace and/or the thermostat(s) controlling the climate system at the location.

Therefore, the disclosed systems and methods provide an improved communication framework that enables computerized functionality for a climate system's improved operation. According to some embodiments, the disclosed framework enables a location's climate system to be controlled via a centralized hub, which can be accessed remotely using a mobile application or web interface. As discussed herein, the enabled communication network and functionality enables dynamic monitoring and control of the devices/components of a location's climate system, which can be effectuated from anywhere (e.g., at the location or away from the location), providing functionality for increased flexibility and convenience. Moreover, the disclosed communication framework provides a reliable and secure wireless communication platform for climate system components, enabling improved energy efficiency, comfort and control for residential and commercial locations (e.g., buildings).

Accordingly, while the discussion herein may focus on climate systems and such system's included components/devices, it should not be construed as limiting, as one of skill in the art would readily understand the disclosed systems and methods discussed herein are applicable to other types of systems operating at a location, such as, but not limited to, Internet of Things (IoT) systems, security systems, and the like, without departing from the scope of the instant disclosure.

According to some embodiments, a method is disclosed for management and control of communications to/from devices of a specifically configured climate control system. 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 for management and control of communications to/from devices of a specifically configured climate control system.

In accordance with some 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.

DETAILED DESCRIPTION

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.11b/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.

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.

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.

Certain embodiments and principles will be discussed in more detail with reference to the figures. With reference toFIG.1, system100is depicted which includes user equipment (UE)102(e.g., a client device, as mentioned above and discussed below in relation toFIG.7), Device A, Device B, network104, cloud system106, database108and communication engine200. It should be understood that while system100is 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, devices (e.g., Devices C, D, . . . n), cloud systems, databases and networks can be utilized; however, for purposes of explanation, system100is discussed in relation to the example depiction inFIG.1.

According to some embodiments, UE102can be any type of device, such as, but not limited to, a mobile phone, tablet, laptop, sensor, IoT device, autonomous machine, and any other device equipped with a cellular or wireless or wired transceiver. In some embodiments, UE102can be a device associated with an individual (or set of individuals) for which disclosed services are being provided. In some embodiments, UE102may correspond to a device of a HVAC or climate-control related entity (e.g., a HVAC provider, whereby the device can be and/or can have corresponding sensors110, as discussed herein). Thus, according to some embodiments, UE102can correspond to a thermostat operating at a location (e.g., a home or office).

In some embodiments, a peripheral device (not shown) can be connected to UE102, 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, peripheral device can be any type of device that is connectable to UE102via any type of known or to be known pairing mechanism, including, but not limited to, Bluetooth™, Bluetooth Low Energy (BLE), NFC, and the like.

According to some embodiments, Device A and Device B can each correspond to a device at a location that provide climate and/or security capabilities. For example, Device A can be an outdoor air conditioning (AC) unit, and Device B can be a furnace. In another non-limiting example, Device A can be a fan within a room of a home, and Device B can be a sensor (e.g., motion sensor associated with the room, for example). Accordingly, any type of known or to be known device that can be part of and/or utilized by a climate system (and/or security system) of a location can be represented by Device A and/or Device. B.

In some embodiments, for example, Device A and/or B can be a device associated with an HVAC system, such as, but not limited to, an AC unit, furnace, heat pump, air handler, humidifier, dehumidifier, ventilation system, zone control system, and the like.

In some embodiments, for example, Device A and/or Device B can correspond to sensors and/or activators at a location that can collect and/or provide data to the HVAC components. For example, such devices can include, but are not limited to, cameras, glass break detectors, motion detectors, door and window contacts, heat and smoke detectors, carbon monoxide (CO2) detectors, passive infrared (PIR) sensors, 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. Thus, the Device A and/or B can be, wholly or in part, associated with and/or part of an IoT sensor network.

In some embodiments, network104can be any type of network, such as, but not limited to, a wireless network, cellular network, the Internet, and the like (as discussed above). Network104facilitates connectivity of the components of system100, as illustrated inFIG.1. In some embodiments, network104can be a specifically configured and/or enabled communication network, such as, for example, RedLINK™ communication platform. For example, such specific network can enable communication between various devices and components within an HVAC system, thereby allowing for improved energy efficiency, comfort, and control.

In some embodiments, such specifically configured network can include UE102, Device A and Device B—for example, RedLINK devices can include, but are not limited to, thermostats, air sensors, and other HVAC components that can communicate wirelessly with each other using encrypted signals. As discussed herein, such enabled communication can allow the devices to exchange information and adjust their operation based on various factors such as occupancy, temperature, humidity, and outdoor weather conditions, and the like.

According to some embodiments, cloud system106may 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, system106may be a service provider and/or network provider from where services and/or applications may be accessed, sourced or executed from. For example, system106can represent the cloud-based architecture associated with a climate control system provider, which has associated network resources hosted on the internet or private network (e.g., network104), which enables (via engine200) the communication/climate management discussed herein.

In some embodiments, cloud system106may include a server(s) and/or a database of information which is accessible over network104. In some embodiments, a database108of cloud system106may store a dataset of data and metadata associated with local and/or network information related to a user(s) of UE102, Device A and/or Device B, UE102, Device A and Device B, and the services and applications provided by cloud system106and/or communication engine200.

In some embodiments, for example, cloud system106can provide a private/proprietary climate management platform, whereby engine200, discussed infra, corresponds to the novel functionality system106enables, hosts and provides to a network104and other devices/sensors/platforms operating thereon.

Turning toFIG.4andFIG.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/architecture106such as, but not limiting to: infrastructure a service (IaaS)510, platform as a service (PaaS)508, and/or software as a service (SaaS)506using a web browser, mobile app, thin client, terminal emulator or other endpoint504.FIG.4andFIG.5illustrate 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.

Turning back toFIG.1, according to some embodiments, database108may correspond to a data storage for a platform (e.g., a network hosted platform, such as cloud system106, as discussed supra), a plurality of platforms, and/or UE102and/or sensors110. Database108may receive storage instructions/requests from, for example, engine200(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, database108may 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.

Communication engine200, as discussed above and further below in more detail, can include components for the disclosed functionality. According to some embodiments, communication engine200may be a special purpose machine or processor, and can be hosted by a device on network104, within cloud system106and/or on UE102(and/or peripheral device112). In some embodiments, engine200may be hosted by a server and/or set of servers associated with cloud system106.

According to some embodiments, as discussed in more detail below, communication engine200may 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 communication and/or climate management. Non-limiting embodiments of such workflows are provided below in relation to at leastFIG.3.

According to some embodiments, as discussed above, communication engine200may function as an application provided by cloud system106. In some embodiments, engine200may function as an application installed on a server(s), network location and/or other type of network resource associated with system106. In some embodiments, engine200may function as application installed and/or executing on UE102. In some embodiments, such application may be a web-based application accessed by UE102and/or devices associated with sensors110over network104from cloud system106. In some embodiments, engine200may 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 system106and/or executing on UE102and/or sensors110.

As illustrated inFIG.2, according to some embodiments, communication engine200includes compression module202, decompression module204, storage module206and output module208. 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 engine200and each of its modules, and their role within embodiments of the present disclosure will be discussed below.

Turning toFIG.3, Process300provides non-limiting example embodiments for the disclosed communication management framework. In some embodiments, as discussed herein, the disclosed framework provides functionality for a reliable and secure wireless communication platform for an IoT system (e.g., climate system, for example).

According to some embodiments, Steps302-306of Process300can be performed by compression module202of communication engine200; Steps308and318can be performed by output module208; Steps310and316can be performed by storage module206; and Steps312-314can be performed by decompression module314.

According to some embodiments, Process300begins with Step302where engine200identifies a data set (e.g., a set of data). According to some embodiments, the data set can correspond to data and/or metadata associated with a climate system. In some embodiments, the data set can correspond to data collected and/or generated by a first device—for example, operational data of Device A within system100, as discussed above in relation toFIG.1. In some embodiments, the data set can correspond to data measurements of a first device, which can be performed according to a predetermined time period (e.g., during time x to time y, during operation of the first device, and the like).

In some embodiments, the data set can be sampled upon identification. In some embodiments, such sampling can be executed by engine200executing any type of known or to be known sampling algorithm or mechanism, for example, uniform random sampling, stratified sampling, importance sampling, Markov Chain Monte Carlo (MCM) sampling, and the like.

In Step304, engine200can perform data encoding. In some embodiments, such encoding can be performed based on the identified set, whereby the above mentioned data sampling can be performed therefrom; and in some embodiments, such encoding can be performed on the sampled data set.

According to some embodiments, prior to the compression (in Step306, discussed infra), the data set is first delta-encoded. According to some embodiments, delta encoding includes calculating the difference between consecutive values. These deltas can be the actual data that is compressed. Accordingly, delta encoding provides functionality for minimizing the number of bits required to represent a value when consecutive data values are comparable in magnitude.

According to some embodiments, engine200can implement any type of known or to be known delta encoding, which can include, but is not limited to, delta encoding with fixed-width integers, delta encoding with variable-width-integers, Golomb-Rice encoding, Elias delta encoding, binary delta encoding, and the like, for example.

In Step306, engine200can perform compression of the data set, which as discussed herein, can be based on the delta encoding performed in Step304. According to some embodiments, engine200can perform any type of known or to be known lossless or lossy compression algorithm or technique. In some embodiments, the compression can be based on the data value, whereby the configuration and sequence of the data set (or data samples) can be defined, which can enable a proper representation of the data for communication, as discussed below.

Thus, according to some embodiments, Step306can involve compressing the encoded data set (or data samples, in some embodiments) into a data value. In some embodiments, the data value and/or set of data values can be determined, which can include information related to, a configuration of a data set and/or data samples, a sequence of the data set and/or data samples, a size of the data set and/or data samples, a word/words size, and the like, or some combination thereof. In some embodiments, the compression can be in accordance with a variable storage element size and/or a static code word size, as discussed below.

By way of a non-limiting example, depicted below in Table 1 are compression results for the first 60 seconds of data. In the example, the encoding can correspond to 240 bytes while an original 16-bit samples required 496 bytes yielding a compression ratio of 51.6%.Sample: zero based sample numberFirst Device (e.g., Furnace, for example) Current: appliance current extracted from cloud data (e.g., cloud system106—for example, TwinThread)16-bit Values: calculated 16-bit value for Furnace CurrentDelta Encoding: the delta encoded 16-bit valuesRequired bits: minimum field width required to store Delta Encoding valueCompressed Bytes: number of bytes being used to encode value(s).Encoding Mode: compression mode encoded in “Code” fieldEncoded Sample: number of sample inside encoded Data field

In Step308, engine200can communicate the compressed data. For example, the communication can involve the determined data value. In some embodiments, the communication can be from a first device to a second device. In some embodiments, for example, the first device can be UE102in system100(where the data is associated with collected information from Device A), whereby the second device is Device B. In some embodiments, for example, the first device can be Device A, and the second device is Device B (and vice versa).

Accordingly, in some embodiments, such communication can be implemented via network104, which can be any type of network discussed above.

In Step310, engine200, upon communication of the compressed data set (e.g., in parallel or in sequence), can store the information related to the communicate data set (e.g., the compressed data, the data values, and the like). In some embodiments, such storage can be performed with respect to cloud storage (e.g., cloud system106and/or database108, as discussed above); and/or, in some embodiments, the first device (e.g., UE102and/or Device A) can store such data.

According to some embodiments, the storage operation performed in Step310can involve storage of the data value(s) (e.g., from Step306, discussed supra), where the storage can be based on and/or in accordance with information related to the variable storage element size and the static code word.

According to some embodiments, with reference to Steps302-310discussed supra, engine200can operate a compression algorithm(s) by packing multiple delta encoded data values into a single storage element. For example, a storage element can be a single storage word. For example, storage element sizes can be, for simple encodings: i) simple-8b: 64-bits; ii) simple-9, Simple-16:32-bits.

According to some embodiments, Simple-RL compression can be used to compress 16-bit signed data. As such, in some embodiments, storage element size can be either 16-bits or 32-bits; and in some embodiments, the code word size can be 4-bits regardless of the storage element size. In some embodiments, if the most significant bit of the code word is 0, then the storage element size can be 32-bits; and if the most significant bit of the code word is 1, then the storage element size can be 16-bits.

In some embodiments, for simple encodings, at least a portion of the bits in the storage element can be utilized to store a code that identifies the size of the data values that are stored in the remainder of the word. Accordingly, in some embodiments, compression can be achieved by storing multiple data values in the storage element using the minimum number of bits possible to represent the data values.

By way of a non-limiting example embodiments, according to some embodiment which can involve RedLINK™ specific components, Steps302-310can be executed in a similar, albeit, modified manner. According to some embodiments, as mentioned above, Simple-RL first uses delta encoding on the data to be compressed:

According to some embodiments, when an event occurs where the first input sample, data [0] has its most significant bit (b15) set to 1, then delta [0] will be a negative number.

According to some embodiments, each new packet to be sent can generate a new set of delta encoded data. In some embodiments, if data is being encoded every a predetermined number of samples (e.g., 60 samples), the new data can be encoded with delta [0]=data [0]. In some embodiments, for a 60 sample example, data may not be encoded as delta [0]=data [0]−data [59] where data [59] is the 60th sample from the previous message. This, among other benefits, enables the recovery of a message/data upon it being lost, deleted or corrupted, and enables subsequent, sequential messages/data to thereby recovered as well.

Accordingly, in some embodiments, in line with the storage of Step310, engine200can perform a signedness operation, where to be stored data values are stored as signed values using two's complement.

By way of a non-limiting example, for the following 32-bit Encoding:

Table 2 shows an example of how data fields can be allocated within the Data section for each Code value. In Table 2, greyed out cells indicate unused portions of the Data section for the individual Code values, the values are stored beginning with the most significant bits of the Data field, and any bits not used for a particular encoding are the least significant bits of the Data field.

According to some embodiments, for 32-bit storage elements, there are no exceptions to signedness, as a encoded data is stored as two's complement.

In another non-limiting example, according to some embodiments, for the following 16-bit Encoding:

In some embodiments, a primary use for 16-bit encoding is to store a sequence of multiple zero values. Multiple zero values can be encoded by setting the Code field to ‘1 0 0 0’ and then setting the data field to the number of zeroes to be encoded. For example, if there are 15 consecutive zeroes in the data, the data would be encoded as:

According to some embodiments, Table 3 below shows an example of how data fields can be allocated within the Data section for each Code value. In Table 3, greyed out cells indicate unused portions of the Data section for the individual Code values, values are stored beginning with the most significant bits of the Data field, and any bits not used for a particular encoding are the least significant bits of the Data field.

According to some embodiments, for 16-bit storage elements, exceptions to signedness may arise. For example, when code ‘1 0 0 0’ is used to encode some number of consecutive zeroes, since zero values are not signed, code ‘1 0 0 0’ does not encode signed values. In another non-limiting example, when code ‘1 0 0 1’ is used to encode 12 consecutive single bit values, since this code can only encode ‘0’ and ‘l’ values, engine200would not encode signed values.

Continuing with Process300, in Step312, the communicated compressed data can be received. For example, with reference toFIG.1discussed supra, the receiving device can be Device B or UE102for example. For example, if the first device sending the compressed data is Device A or UE102, then the second device can be Device B.

In Step314, upon reception of the compressed data, the second device, via execution of engine200, can decompress the compressed data. According to some embodiments, such decompression can be performed according to any known or to be known decompression technique for decompressing data that was compressed via Step306, as discussed above. For example, engine200can execute a decompression algorithm including, but not limited to, Huffman coding, Run-length encoding (RLE), Arithmetic coding, Lempel-Ziv-Welch (LZW) algorithm, Burrows-Wheeler Transform (BWT), Deflate algorithm, LZ77 algorithm, LZ78 algorithm, LZSS algorithm, Delta encoding, and the like.

According to some embodiments, Step314decompression can involve the received data value (from Step312) being decompressed by the second device upon receipt. Accordingly, in Step316, the decompressed data value is stored in a buffer associated with the second device. In some embodiments, Step316can further involve communicating the decompressed data to cloud storage, as in a similar manner as discussed above at least with respect to Step310.

In Step318, engine200can cause and/or facilitate operation of the second device based on the data. For example, the second device can operate based on measured data from the first device.

For example, if the second device can be caused to execute a program to offset the measurements of the first device. For example, a furnace (e.g., second device) can execute a heat program/mode for a room upon receiving temperature measurements from an AC unit (first device). In some embodiments, the temperature measurements can be collected and provided from a thermostat acting as the first device, as discussed above.

Accordingly, upon operation of the second device (e.g., Device B, for example), Process300can recursively operate to Step302so as to identify the data from the second device's operation, which can enable the identification of data related to such operation.

FIG.6is a schematic diagram illustrating a client device showing an example embodiment of a client device that may be used within the present disclosure. Client device600may include many more or less components than those shown inFIG.6. However, the components shown are sufficient to disclose an illustrative embodiment for implementing the present disclosure. Client device600may represent, for example, UE102discussed above at least in relation toFIG.1.

As shown in the figure, in some embodiments, Client device600includes a processing unit (CPU)622in communication with a mass memory630via a bus624. Client device600also includes a power supply626, one or more network interfaces650, an audio interface652, a display654, a keypad656, an illuminator658, an input/output interface660, a haptic interface662, an optional global positioning systems (GPS) receiver664and a camera(s) or other optical, thermal or electromagnetic sensors666. Device600can include one camera/sensor666, or a plurality of cameras/sensors666, as understood by those of skill in the art. Power supply626provides power to Client device600.

Client device600may optionally communicate with a base station (not shown), or directly with another computing device. In some embodiments, network interface650is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

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

Keypad656may include any input device arranged to receive input from a user. Illuminator658may provide a status indication and/or provide light.

Client device600also includes input/output interface660for communicating with external. Input/output interface660can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like in some embodiments. Haptic interface662is arranged to provide tactile feedback to a user of the client device.

Optional GPS transceiver664can determine the physical coordinates of Client device600on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver664can 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 device600on the surface of the Earth. In one embodiment, however, Client device 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.

Mass memory630includes a RAM632, a ROM634, and other storage means. Mass memory630illustrates another example of computer storage media for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory630stores a basic input/output system (“BIOS”)640for controlling low-level operation of Client device600. The mass memory also stores an operating system641for controlling the operation of Client device600.

Memory630further includes one or more data stores, which can be utilized by Client device600to store, among other things, applications642and/or other information or data. For example, data stores may be employed to store information that describes various capabilities of Client device600. 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 device600.

Applications642may include computer executable instructions which, when executed by Client device600, transmit, receive, and/or otherwise process audio, video, images, and enable telecommunication with a server and/or another user of another client device. Applications642may 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 engine200and its affiliates.

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 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.