CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application serial number 62/332,995, filed on May 6, 2016 and U.S. Non-Provisional Patent Application serial number 15385714, filed on December 20, 2016.

BACKGROUND

[0002] Existing air quality detection equipment generally drives air flow through an air quality sensor using a mechanism such as a fan. Over time, residue is trapped within the air path and affect the accuracy of the air quality measurement.

[0003] Because the sensing environments are varied and dynamic, the accuracy degradation may not be able to be predicted based on elapsed time or other such measures. For instance, in a very polluted area, sensor accuracy may degrade below an acceptable level within one month while a less polluted area, the sensor may maintain acceptable accuracy for a year or more.

[0004] Therefore there exists a need for a way to determine accuracy degradation of air quality sensors.

SUMMARY

[0005] Some embodiments provide ways to detect and/or correct for air quality detection inaccuracies. Such inaccuracies may be due to residue buildup along an air flow pathways that affects the ability of at least some air quality detection sensors to lose accuracy.

[0006] A smart residue avoidance and inaccuracy detection (SRAID) device of some embodiments may include a set of air quality measurement sensors. Measurements received from the sensors may be compared to other sensors in the set and/or to sensors associated with other SRAID devices.

[0007] Some embodiments may calculate a difference among the received measurements.

Such a difference may be compared to a threshold value. If the difference exceeds the threshold value, a notification may be generated indicating that there is a mismatch in received measurements. Such a notification may be sent to a server and/or relayed to an air flow control device such as a fan or turbine.

[0008] The notification may flag the mismatch (such that the flag may be indicated to a technician or other appropriate user) and/or provide (or direct) corrective action. For instance, some embodiments may increase fan speed or heat difference to attempt to dislodge residue associated with a measurement mismatch.

[0009] Some embodiments may operate using a local closed loop. In such cases, a single

SRAID device (and/or multiple local devices) may identify a mismatch and either flag the mismatch or attempt corrective action in the local environment (e.g., by directing a fan to increase flow speed along the measurement pathway).

[0010] Some embodiments may operate using a wide area closed loop. In such cases, measurements from one SRAID device may be compared to measurements from a number of associated SRAID devices. Such devices may be associated based on various relevant factors (e.g., geographic location, system association, device type, etc.). If a mismatch is identified, notification may be sent to the affected device(s) and/or users. Alternatively, a corrective action may be initiated by a server or other appropriate device associated with the wide area closed loop.

[0011] The preceding Summary is intended to serve as a brief introduction to various features of some exemplary embodiments. Other embodiments may be implemented in other specific forms without departing from the scope of the disclosure.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0012] The exemplary features of the disclosure are set forth in the appended claims.

However, for purpose of explanation, several embodiments are illustrated in the following drawings.

[0013] Figure 1A illustrates a schematic block diagram of a localized detection system according to an exemplary embodiment.

[0014] Figure IB illustrates a schematic block diagram of an alternative localized detection system according to an exemplary embodiment;

[0015] Figure 2 illustrates a schematic block diagram of a detection device according to an exemplary embodiment;

[0016] Figure 3 illustrates a schematic block diagram of a distributed system according to an exemplary embodiment;

[0017] Figure 4 illustrates a flow chart of an exemplary client-side process that monitors air quality detection equipment;

[0018] Figure 5 illustrates a flow chart of an exemplary server-side process that monitors air quality detection equipment; and

[0019] Figure 6 illustrates a schematic block diagram of an exemplary computer system used to implement some embodiments. DETAILED DESCRIPTION

[0020] The following detailed description describes currently contemplated modes of carrying out exemplary embodiments. The description is not to be taken in a limiting sense, but is made merely for the purpose of illustrating the general principles of some embodiments, as the scope of the disclosure is best defined by the appended claims.

[0021] Various features are described below that can each be used independently of one another or in combination with other features. Broadly, some embodiments generally provide ways to monitor, evaluate, and direct air quality detection equipment.

[0022] A first exemplary embodiment provides an automated method of detecting measurement inaccuracy in an air quality detection system, the method comprising: receiving an air quality measurement from at least two sensors; determining a difference among the received air quality measurements; and comparing the difference to a threshold value.

[0023] A second exemplary embodiment provides a system that detects measurement inaccuracy in an air quality detection, the system comprising: a plurality of smart residue avoidance and inaccuracy detection (SRAID) devices; and a server.

[0024] A third exemplary embodiment provides an SRAID device comprising: a plurality of air quality detection sensors; a controller able to: receive measurements from the plurality of air quality detection sensors; calculate a difference among the received measurements; and generate a notification if the difference exceeds a threshold value; and a communication module able to communicate with at least one of a server and an air flow controller device.

[0025] Several more detailed embodiments are described in the sections below. Section I provides a description of various hardware architectures used by some embodiments. Section II then describes various methods of operation used by some embodiments. Lastly, Section III describes a computer system which implements some of the embodiments.

I. HARDWARE ARCHITECTURE

[0026] Figure 1A illustrates a schematic block diagram of a localized detection system 100 according to an exemplary embodiment. Figure IB illustrates a schematic block diagram of an alternative localized detection system 190 according to an exemplary embodiment.

[0027] As shown, system 100 and system 190 may include a physical pathway 110 (e.g., a pipe, duct, etc.), air flow 120, a first sensor 130, a second sensor 140, a first turbulent generator 150, a second turbulent generator 160, a first mini turbulent 170, and a second mini turbulent 180. [0028] As shown, pairs of air quality sensors 130-140 may be arranged in various configurations relatively to an air flow pathway 110 (or other fluid pathway) such that measurements may be taken at different locations along the pathway. In system 100, the sensors 130-140 and associated generators 150-160 are arranged in series along the pathway 120. In system 190, the sensors 130-140 and associated generators 150-160 are arranged in parallel along the pathway 120.

[0029] Each sensor 130 or 140 may be able to perform various air quality measurements and generate an analog and/or digital output representing the measurements. Each sensor 130 or 140 in the pair of sensors may perform the same type of measurement in order to be able to compare measured values between the sensors in the pair. Some embodiments may calculate a weighted average across multiple sensors for detection. Some embodiments may include a single sensor and utilize network data for detection.

[0030] The air flow 120 may be provided by a fan or other appropriate air flow controller device. The flow may include creating mini air turbulences 170 and 180 throughout the pathway 120 and directed at the locations of sensors 130 and 140. Such mini air turbulences may be generated using changes in mechanical design of a smooth flow air pathway (e.g., a step up or step down feature), creating an air temperature difference (e.g., by heating a portion of the pathway), and/or other appropriate ways (e.g., using generators 150-160).

[0031] One of ordinary skill in the art will recognize that the systems 100 and/or 190 may be implemented in various different ways without departing from the scope of the disclosure. For instance, some embodiments may include various additional elements, omit various elements, and/or arrange the elements in various different ways. In addition, the relative positions of the various elements may vary depending on various relevant factors (e.g., air distribution type, application type, sensor type, geographic location, environmental conditions, etc.).

[0032] Figure 2 illustrates a schematic block diagram of an SRAID device 200 according to an exemplary embodiment. In this example, the device includes two sensors 130-140 and two mini turbulent generators 150-160 such as those described above, a controller 210, memory 220, and a communication module 230.

[0033] The device 200 may be distributed across multiple elements in some embodiments

(e.g., the sensors 130-140 and/or generators 150-160 may be wirelessly connected to the controller 210 via the communication module 230). In addition, some embodiments may include additional elements (e.g., additional pairs of sensors associated with various other pathways or locations along the pathway) or omit various elements.

[0034] Other components may include a fan or other component able to direct or otherwise affect airflow. Such a fan may be able to be controlled by the controller (e.g., a fan or other air flow element may be activated, the speed of a fan may be changed, etc.).

[0035] The controller 210 may include various electronic devices and/or circuitry that are able to receive messages, data, and/or instructions from other system elements. The controller may be able to send messages, data, commands, and/or instructions to other system elements. The controller may be able to execute various sets of instructions, including programs or applications.

[0036] The memory 220 may include data and/or instructions used by the controller 210 to interact with the sensors 130-140 and/or generators 150-160, control the fan or other resource, direct the communication module 230, and/or otherwise used by the controller 210 to implement the various features.

[0037] The communication module 230 may allow the device to communicate with various external components (e.g., sensors, fans, etc.) and/or various network-accessible components.

[0038] One of ordinary skill in the art will recognize that the device 200 may be implemented in various specific ways without departing from the scope of the disclosure. For instance, the device may include additional components, omit various components, and/or arrange the components in various different ways. As another example, some components (e.g., controller 210) may be shared across devices 200. In some embodiments, the device 200 may include various user interface elements (e.g., touchscreens, knobs, buttons, keypads, etc.) that may allow a user to enter various operating parameters (and/or to view various displayed parameters).

[0039] Figure 3 illustrates a schematic block diagram of a distributed system 300 according to an exemplary embodiment. As shown, the system may include multiple devices 200, a set of networks 310, and a server 320.

[0040] In this example, the server 320 is able to interact with the various SRAID devices 200 across one or more networks 310. The networks may include wired networks (e.g., Ethernet), wireless networks (e.g., Wi-Fi, Cellular, radio, etc.), distributed networks (e.g., the Internet), and/or other appropriate communication pathways.

[0041] The server 320 may be a computing device that is able to receive data from the

SRAID devices 200 and/or send data, commands, and/or instructions to the devices. The server 320 may be able to access various local and/or distributed storages and/or other accessible resources such as local resources or network accessible resources.

[0042] One of ordinary skill in the art will recognize that the system 300 may be implemented in various different ways without departing from the scope of the disclosure. For instance, some embodiments may include various additional elements, omit various elements, and/or arrange the elements in various different ways. In addition, various external servers, storages, etc. may be accessible to system 300. For instance, the server 320 may be able to direct and/or otherwise communicate with various external elements associate with the air quality detection systems (e.g., fans, heaters, etc.).

II. METHODS OF OPERATION

[0043] Figure 4 illustrates a flow chart of an exemplary client-side process 400 that monitors air quality detection equipment. Such a process may be executed by a device such as SRAID device 200 and/or other appropriate elements. The process may begin, for instance, when an SRAID device of some embodiments is powered on.

[0044] As shown, process 400 may receive (at 410) data from a server, if available. A server, such as server 320) may send data, such as operating parameters, event thresholds, messages or commands, etc. that may be utilized by the SRAID device during operation. If no server or connection is available, the process may use a set of default parameters, user specified parameters, a most recent update, and/or other appropriate settings.

[0045] Next, the process may retrieve (at 420) sensor data. Such data may be retrieved from a pair of sensors placed in close proximity as described above. The data may include analog and/or digital signals.

[0046] The process may then determine (at 430) whether there is a mismatch in the retrieved data by comparing the retrieved data from each sensor (e.g., by calculating a difference between two measurements taken at or near the same time). Some embodiments may identify mismatches based at least partly on data received from the server. The mismatch determination may include various other operations and the resulting value(s) may be compared to one or more threshold values to determine whether an observed mismatch is within specified limits. Such threshold values, along with other operating parameters, may be configured in various appropriate ways (e.g., by receiving such values from a server, via default settings, local settings at a device, etc.).

[0047] If the process determines there is a mismatch that exceeds a particular threshold (or some other appropriate criteria is met), the process may attempt (at 440) to correct the mismatch. Such an attempt may include, for instance, increasing fan speed or changing temperature in an attempt to dislodge residue from a pathway. In some embodiments, the attempted correction may utilize various appropriate pathways or components (e.g., server and network connection) in order to control the operation of a fan or heating element external to the SRAID device, for instance. Such corrections may involve various appropriate messages, commands, etc. that may be relayed among the various devices.

[0048] Finally, the process may send (at 450) data to the server and then may end.

Alternatively, the data may be stored locally for future transmission or other use. Such data may include, for instance, measurement data, correction data (including actions and results), device data (e.g., type of sensor, sensor ID, location, application setting, etc.), and/or other appropriate data.

[0049] In some embodiments, the SRAID devices and the server may form a two-way communication channel such that the server may receive data and send commands or other instructions to multiple devices as the system is operated.

[0050] Figure 5 illustrates a flow chart of an exemplary server-side process 500 that monitors air quality detection equipment. Such a process may be executed by a device such as server 320 described above and/or other appropriate elements. The process may begin, for instance, when a system of some embodiments is powered on.

[0051] As shown, process 500 may retrieve (at 510) sensor data (and/or other data) from one or more devices, such as device 200. The devices may provide data, such as measurements, messages, etc. that may be utilized by the server during operation. Such data may include previously stored information, such as measurements over time, previous messages, etc.

[0052] Next, the process may identify (at 520) associated sensors and/or sensor data. Sensors may be associated in various different ways. For instance, a pair of sensors may be associated with a single SRAID device of some embodiments. As another example, multiple devices (and sensors) may be associated with an air flow system (e.g., an HVAC system). As still another example, sensors may be grouped by geographic region, sensor type, measurement range, and/or other relevant factors.

[0053] Next, the process may determine (at 530) whether there is a mismatch or other issue with the retrieved associated data. Such a determination may be made based on various relevant criteria. For instance, some embodiments may compare a difference among the associated sensors to one or more threshold values. Such differences may be calculated in various appropriate ways such as subtraction, comparison to an average (e.g., a mean, median, weighted average, etc.) or other statistical measure (e.g., standard deviation, variance, etc.),

[0054] If the process determines there is a mismatch, the process may generate (at 540) and send one or more notifications, commands, and/or perform other appropriate actions to correct the mismatch. Such actions may include, for instance, directing a fan or other airflow control element to increase or decrease speed, directing a heating element or other appropriate environmental control element to increase a temperature, etc. In some cases, the actions may be directed by an element such as server 320 and carried out by one or more devices such as SRAID device 200. For instance, the server may send a command to an SRAID device which may, in turn, send a command to a local fan or other appropriate element. Alternatively, the server may communicate directly (i.e., without use of an intervening SRAID device) with the fan or other local element. As another example, a message or notification may be sent to a user device, such as "change filter", "replace unit", etc. Such notifications may be associated with mismatches beyond a correctable level, mismatches that persist after automated attempts at correction, and/or other appropriate conditions.

[0055] Finally, the process may store (at 550) data associated with the performed operations and then may end. Such data may include, for instance, measurement data, correction data (including actions and results), device data (e.g., type of sensor, sensor ID, location, application setting, etc.), and/or other appropriate data. Such data may be manipulated at the server and used to generate updates that may be sent to the SRAID devices.

[0056] In some embodiments, updates may be sent to one or more sensors under various appropriate conditions. For instance, the server may send update information when an SRAID device executes process 400. As another example, the server may send updates after execution of process 500. Such updates may include updates to threshold values, operating parameters, etc.

[0057] In some embodiments, the server and SRAID devices may form a two-way communication channel such that the server may receive data and send commands or other instructions to each device as the system is operated.

[0058] Processes 400 and 500 may be performed in various different ways without departing from the scope of the disclosure. For instance, the processes, and/or portions thereof, may be performed iteratively and/or based on some criteria. As another example, the operations may be performed in a different order, additional operations may be included, and/or various listed operations may be omitted.

III. COMPUTER SYSTEM

[0059] Many of the processes and modules described above may be implemented as software processes that are specified as one or more sets of instructions recorded on a non-transitory storage medium. When these instructions are executed by one or more computational element(s) (e.g., microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.) the instructions cause the computational element(s) to perform actions specified in the instructions. [0060] In some embodiments, various processes and modules described above may be implemented completely using electronic circuitry that may include various sets of devices or elements (e.g., sensors, logic gates, analog to digital converters, digital to analog converters, comparators, etc.). Such circuitry may be able to perform functions and/or features that may be associated with various software elements described throughout.

[0061] Figure 6 illustrates a schematic block diagram of an exemplary computer system 600 used to implement some embodiments. For example, the systems and/or devices described above in reference to Figures 1A-3 may be at least partially implemented using computer system 600. As another example, the processes described in reference to Figures 4-5 may be at least partially implemented using sets of instructions that are executed using computer system 600.

[0062] Computer system 600 may be implemented using various appropriate devices. For instance, the computer system may be implemented using one or more personal computers (PCs), servers, mobile devices (e.g., a smartphone), tablet devices, and/or any other appropriate devices. The various devices may work alone (e.g., the computer system may be implemented as a single PC) or in conjunction (e.g., some components of the computer system may be provided by a mobile device while other components are provided by a tablet device).

[0063] As shown, computer system 600 may include at least one communication bus 605, one or more processors 610, a system memory 615, a read-only memory (ROM) 620, permanent storage devices 625, input devices 630, output devices 635, audio processors 640, video processors 645, various other components 650, and one or more network interfaces 655.

[0064] Bus 605 represents all communication pathways among the elements of computer system 600. Such pathways may include wired, wireless, optical, and/or other appropriate communication pathways. For example, input devices 630 and/or output devices 635 may be coupled to the system 600 using a wireless connection protocol or system.

[0065] The processor 610 may, in order to execute the processes of some embodiments, retrieve instructions to execute and/or data to process from components such as system memory 615, ROM 620, and permanent storage device 625. Such instructions and data may be passed over bus 605.

[0066] System memory 615 may be a volatile read-and-write memory, such as a random access memory (RAM). The system memory may store some of the instructions and data that the processor uses at runtime. The sets of instructions and/or data used to implement some embodiments may be stored in the system memory 615, the permanent storage device 625, and/or the read-only memory 620. ROM 620 may store static data and instructions that may be used by processor 610 and/or other elements of the computer system.

[0067] Permanent storage device 625 may be a read-and-write memory device. The permanent storage device may be a non-volatile memory unit that stores instructions and data even when computer system 600 is off or unpowered. Computer system 600 may use a removable storage device and/or a remote storage device as the permanent storage device.

[0068] Input devices 630 may enable a user to communicate information to the computer system and/or manipulate various operations of the system. The input devices may include keyboards, cursor control devices, audio input devices and/or video input devices. Output devices 635 may include printers, displays, audio devices, etc. Some or all of the input and/or output devices may be wirelessly or optically connected to the computer system 600.

[0069] Audio processor 640 may process and/or generate audio data and/or instructions. The audio processor may be able to receive audio data from an input device 630 such as a microphone. The audio processor 640 may be able to provide audio data to output devices 640 such as a set of speakers. The audio data may include digital information and/or analog signals. The audio processor 640 may be able to analyze and/or otherwise evaluate audio data (e.g., by determining qualities such as signal to noise ratio, dynamic range, etc.). In addition, the audio processor may perform various audio processing functions (e.g., equalization, compression, etc.).

[0070] The video processor 645 (or graphics processing unit) may process and/or generate video data and/or instructions. The video processor may be able to receive video data from an input device 630 such as a camera. The video processor 645 may be able to provide video data to an output device 640 such as a display. The video data may include digital information and/or analog signals. The video processor 645 may be able to analyze and/or otherwise evaluate video data (e.g., by determining qualities such as resolution, frame rate, etc.). In addition, the video processor may perform various video processing functions (e.g., contrast adjustment or normalization, color adjustment, etc.). Furthermore, the video processor may be able to render graphic elements and/or video.

[0071] Other components 650 may perform various other functions including providing storage, interfacing with external systems or components, etc.

[0072] Finally, as shown in Figure 6, computer system 600 may include one or more network interfaces 655 that are able to connect to one or more networks 660. For example, computer system 600 may be coupled to a web server on the Internet such that a web browser executing on computer system 600 may interact with the web server as a user interacts with an interface that operates in the web browser. Computer system 600 may be able to access one or more remote storages 670 and one or more external components 675 through the network interface 655 and network 660. The network interface(s) 655 may include one or more application programming interfaces (APIs) that may allow the computer system 600 to access remote systems and/or storages and also may allow remote systems and/or storages to access computer system 600 (or elements thereof).

[0073] As used in this specification and any claims of this application, the terms "computer",

"server", "processor", and "memory" all refer to electronic devices. These terms exclude people or groups of people. As used in this specification and any claims of this application, the term "non- transitory storage medium" is entirely restricted to tangible, physical objects that store information in a form that is readable by electronic devices. These terms exclude any wireless or other ephemeral signals.

[0074] It should be recognized by one of ordinary skill in the art that any or all of the components of computer system 600 may be used in conjunction with some embodiments. Moreover, one of ordinary skill in the art will appreciate that many other system configurations may also be used in conjunction with some embodiments or components of some embodiments.

[0075] In addition, while the examples shown may illustrate many individual modules as separate elements, one of ordinary skill in the art would recognize that these modules may be combined into a single functional block or element. One of ordinary skill in the art would also recognize that a single module may be divided into multiple modules.

[0076] The foregoing relates to illustrative details of exemplary embodiments and modifications may be made without departing from the scope of the disclosure as defined by the following claims.