This disclosure is related to the field of electrical wiring, and more particularly to systems, methods, and apparatus pertaining to an intelligent multi-way electric switch.
The era of home automation, sometimes also known as “domotics,” has arrived and homeowners and property managers are increasingly turning to “smart home” devices. Despite the name, smart home technologies have applications that range beyond dwellings, as they facilitate the automation and control of common home operating systems such as electrical, lighting, heating, ventilation, air conditioning (HVAC), security, as well as integration with smart appliances, such as washers/dryers, ovens, dishwashers, refrigerators and freezers.
Generally, these technologies use the now almost-ubiquitous wireless local access network (WLAN) found in most homes in combination with the also widespread availability of wireless network-enabled mobile computers, such as tablet PCs and smart phones, to connect to and manage “smart devices.” Obviously, participating smart home devices likewise comprise wireless transmitters for receiving instructions and transmitting status and other data, and computers for intelligent, programmatic management of the devices.
One common problem with implementing home automation, however, is that very few dwellings are constructed with home automation in mind. Even for new construction, homes are typically built in accordance with decades-old construction practices and using long-accepted conventional materials and components. Converting homes to use smart home devices is simple for certain types of home operating systems, but difficult for others.
For example, HVAC and security systems are typically operated via a main control, such as a thermostat or security panel. These main controls can simply be replaced with network-enabled smart device counterparts to enable home automation. This is easy to do even for an unskilled homeowner, as these remote panels usually operate on low-voltage circuits that pose little material risk to even the untrained homeowner, and have simpler configurations that can be easily transferred from an existing “dumb” device to a new smart device.
However, other home systems are more complicated. For example, electrical power enters a home usually through overhead or buried power lines. The home is connected to the power grid via a circuit breaker panel, which is usually located in a garage, basement, or electrical closet near the physical point where the power lines reach the dwelling. The circuit breaker then splits the incoming power into a plurality of different independent circuits, each of which is separately controllable at the panel by throwing a circuit breaker on or off.
Although certain high-load appliances may have dedicated circuits, typically an entire room or set of rooms with related functions are wired in parallel on a shared circuit. For example, an electric oven might receive its own circuit, but all lights and power outlets in a bedroom might all be wired together. This limits the degree of granularity by which circuits might be operable via the breaker. Moreover, unlike a low-voltage thermostat, most homeowners lack the knowledge, expertise, or equipment to safely alter a circuit breaker. Thus, implementing smart home technology in light and power fixtures is not practical at the breaker.
Instead, smart home technologies have focused on replacing individual power and light receptacles, a task which can be performed safely by a careful homeowner even if unskilled. However, this approach has certain inherent limitations and drawbacks, in that power may not always be available in certain applications, and such replacements generally do not integrate smoothly with conventional hardware.
This may be best understood through an example. Prior art
In a conventional smart home installation, the light receptacle (108) is simply replaced by a smart light (109), such as that depicted in
However, this configuration has a key shortcoming. While a holistic home automation strategy may involve replacing all components in a structure, it is more common to target key areas and rooms and upgrade over time. This means that most home automation deployments have a mixture of “dumb” and “smart” lights, outlets, switches, and other components. However, smart lights do not seamlessly integrate with mechanical switches.
This is because the computer (111) and transmitter (113) require power to operate, but if the original wall switch (107) is turned off, no current flows on the live wire (103) and there is thus no power to the computer (111) and transmitter (113), and they cannot operate. This can be partially solved by simply leaving the switch (107) in “on” position and exclusively using another device to power the switch. However, when guests, children, or even forgetful homeowners leave the room, they may reflexively turn off the light switch without recalling or appreciating that this effectively disables the smart light (109). Frustrating the situation further, the removal of power for a long enough period of time can cause smart devices to reset to factory settings or lose configuration data, requiring that they be reconfigured and retested once power is restored.
This could be solved by simply disabling the physical switch entirely so that it cannot be used to control power flow. This leaves a non-functional blank faceplate on the wall, which may be confusing to guests and visitors who do not understand how to use the smart light system, and it requires all such switches to be replaced or disabled. Moreover, it is desirable to retain the functionality of the physical switch in conjunction with the smart device so that the smart device can be operated both via the home automation system and via a conventional physical switch.
The following is a summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. The sole purpose of this section is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.
Because of these and other problems in the art, described herein, among other things, is a smart switch comprising: an electric power input adapted to receive electric power from an electric circuit; a measurement device in electric communication with the electric power input and adapted to measure at least one circuit characteristic of the electric circuit; and a transceiver in electric communication with the measurement device and adapted to receive from the measurement device a measure of power on the electric circuit; wherein the transmitter receives from the measurement device a reading of the power state of the electric circuit detected by the measurement device and transmits information about the reading.
In an embodiment, the circuit characteristic is selected from the group consisting of: power applied; current; voltage; and, phase.
In an embodiment, the transmitted information indicates whether power is available on the electric circuit.
In an embodiment, the reading is made at least in part using the circuit characteristics.
In an embodiment, the circuit characteristic is indicative of the power state based on a known mathematical relationship between the circuit characteristic and the power state.
In an embodiment, the smart switch is adapted to electrically connect to the electric circuit using a power receptacle.
In an embodiment, the smart switch further comprises a light-producing element.
In an embodiment, the load is selected from the group consisting of: light element, dimmer control circuit, ceiling fan, and wireless range extender.
In an embodiment, the smart switch further comprises a power converter adapted to draw power for the smart switch from the electric circuit.
In an embodiment, the smart switch further comprises an energy storage medium adapted to supply electric power to the transceiver.
In an embodiment, the energy storage medium is selected from the group consisting of: capacitor; inductor; battery; and, rechargeable battery.
In an embodiment, the smart switch further comprises at least one capacitor, battery, or rechargeable battery.
Also described herein, among other things, is a method for determining the state of electrical power comprising: providing an electric circuit operable among a plurality of power states by a control; providing a smart switch on the electric circuit; providing a computer server; operating the control to change the power state of the electric circuit; detecting, using the smart switch, the changed power state; and transmitting, using the smart switch, the changed power state to the computer server.
In an embodiment, the control comprises a mechanical switch.
In an embodiment, the changed power state is from powered to unpowered.
In an embodiment, the detecting further comprises the smart switch determining at least one characteristic of power to the smart switch.
In an embodiment, the at least one characteristic is selected from the group consisting of: power applied; current; voltage; and, phase.
In an embodiment, the method further comprises determining a state of the control based at least in part on the determined at least one characteristic.
In an embodiment, the transmitted changed power state includes a final power state of the electric circuit after the change in the power state.
In an embodiment, the transmitted changed power state includes an initial power state of the electric circuit before the change in the power state.
In an embodiment, the transmitted changed power state includes an amount of change between an initial power state of the circuit before the change in power state and a final power state of the circuit after the change in power state.
In an embodiment, the method further comprises controlling, using the computer server, a lighting system.
In an embodiment, smart switch further comprises a light-producing element.
In an embodiment, the method further comprises: providing one or more external devices in wireless communication with the computer server; receiving, at the computer server, the changed power state information; and transmitting, at the computer server, instructions to the one or more external devices, the instructions being determined at least in part based on the received changed power state.
In an embodiment, the transmitted instructions to the one or more external devices are further determined at least in part based on one or more of: day of the week; date; time; light sensors; user settings; knowledge of prior system state; and, states of other inputs.
The following detailed description and disclosure illustrates by way of example and not by way of limitation. This description will clearly enable one skilled in the art to make and use the disclosed systems and methods, and describes several embodiments, adaptations, variations, alternatives and uses of the disclosed systems and methods. As various changes could be made in the above constructions without departing from the scope of the disclosures, it is intended that all matter contained in the description or shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.
Throughout this disclosure, the term “computer” describes hardware which generally implements functionality provided by digital computing technology, particularly computing functionality associated with microprocessors. The term “computer” is not intended to be limited to any specific type of computing device, but it is intended to be inclusive of all computational devices including, but not limited to: processing devices, microprocessors, personal computers, desktop computers, laptop computers, workstations, terminals, servers, clients, portable computers, handheld computers, smart phones, tablet computers, mobile devices, server farms, hardware appliances, minicomputers, mainframe computers, video game consoles, handheld video game products, and wearable computing devices including but not limited to eyewear, wristwear, pendants, and clip-on devices.
As used herein, a “computer” is necessarily an abstraction of the functionality provided by a single computer device outfitted with the hardware and accessories typical of computers in a particular role. By way of example and not limitation, the term “computer” in reference to a laptop computer would be understood by one of ordinary skill in the art to include the functionality provided by pointer-based input devices, such as a mouse or track pad, whereas the term “computer” used in reference to an enterprise-class server would be understood by one of ordinary skill in the art to include the functionality provided by redundant systems, such as RAID drives and dual power supplies.
It is also well known to those of ordinary skill in the art that the functionality of a single computer may be distributed across a number of individual machines. This distribution may be functional, as where specific machines perform specific tasks; or, balanced, as where each machine is capable of performing most or all functions of any other machine and is assigned tasks based on its available resources at a point in time. Thus, the term “computer” as used herein, can refer to a single, standalone, self-contained device or to a plurality of machines working together or independently, including without limitation: a network server farm, “cloud” computing system, software-as-a-service, or other distributed or collaborative computer networks.
Those of ordinary skill in the art also appreciate that some devices which are not conventionally thought of as “computers” nevertheless exhibit the characteristics of a “computer” in certain contexts. Where such a device is performing the functions of a “computer” as described herein, the term “computer” includes such devices to that extent. Devices of this type include but are not limited to: network hardware, print servers, file servers, NAS and SAN, load balancers, and any other hardware capable of interacting with the systems and methods described herein in the matter of a conventional “computer.”
Throughout this disclosure, the term “software” refers to code objects, program logic, command structures, data structures and definitions, source code, executable and/or binary files, machine code, object code, compiled libraries, implementations, algorithms, libraries, or any instruction or set of instructions capable of being executed by a computer processor, or capable of being converted into a form capable of being executed by a computer processor, including without limitation virtual processors, or by the use of run-time environments, virtual machines, and/or interpreters. Those of ordinary skill in the art recognize that software can be wired or embedded into hardware, including without limitation onto a microchip, and still be considered “software” within the meaning of this disclosure. For purposes of this disclosure, software includes without limitation: instructions stored or storable in RAM, ROM, flash memory BIOS, CMOS, mother and daughter board circuitry, hardware controllers, USB controllers or hosts, peripheral devices and controllers, video cards, audio controllers, network cards, Bluetooth® and other wireless communication devices, virtual memory, storage devices and associated controllers, firmware, and device drivers. The systems and methods described herein are contemplated to use computers and computer software typically stored in a computer- or machine-readable storage medium or memory.
Throughout this disclosure, terms used herein to describe or reference media holding software, including without limitation terms such as “media,” “storage media,” and “memory,” may include or exclude transitory media such as signals and carrier waves.
Throughout this disclosure, the term “network” generally refers to a voice, data, or other telecommunications network over which computers communicate with each other. The term “server” generally refers to a computer providing a service over a network, and a “client” generally refers to a computer accessing or using a service provided by a server over a network. Those having ordinary skill in the art will appreciate that the terms “server” and “client” may refer to hardware, software, and/or a combination of hardware and software, depending on context. Those having ordinary skill in the art will further appreciate that the terms “server” and “client” may refer to endpoints of a network communication or network connection, including but not necessarily limited to a network socket connection. Those having ordinary skill in the art will further appreciate that a “server” may comprise a plurality of software and/or hardware servers delivering a service or set of services. Those having ordinary skill in the art will further appreciate that the term “host” may, in noun form, refer to an endpoint of a network communication or network (e.g., “a remote host”), or may, in verb form, refer to a server providing a service over a network (“hosts a website”), or an access point for a service over a network.
Throughout this disclosure, the term “embedded system,” “embedded computer,” and variants thereof distinguish special purpose computer hardware and software from general-purpose computer hardware and software. As used herein, an embedded system is a special-purpose system in which the computer is mostly or completely encapsulated by the device it controls. Unlike a general-purpose computer, such as a personal computer, an embedded system generally performs more limited, pre-defined tasks, usually with very specific requirements to accomplish a limited and pre-defined set of operational tasks. Since the system is dedicated to a specific task, it is more easily optimized for the task, reducing size and cost by eliminating unnecessary components found in general-purpose computers, and designing board circuitry and system geometry to improve operational efficiency, reduce manufacturing cost, and address operation-specific conditions, such as temperature extremes.
Throughout this disclosure, the term “mechanical switch” or “physical switch” refers to an electrical switch structure operable to an “on” or “off” position, in which the “on” position “makes” a circuit by providing a complete electrical path through the device, and the “off” position “breaks” the circuit by interrupting or diverting current flow. This is typically done by introducing a physical break in the path of sufficient width to form an insulating air gap. The term “contacts” refers to the physical components of the switch which create or remove this gap, such as the poles and throws in a conventional light switch. By contrast, the term “toggle” refers to a component of the switch that is (usually) electrically insulated from the current flow and physically manipulated to make or break the circuit. In a conventional dwelling, the toggle is the part colloquially referred to as the “light switch” and move up or down to turn lights on or off, but should be understood in the context of this disclosure as meaning any human-operable means for a user to place the contacts in the desired on/off state.
Throughout this disclosure, a “toggle event” means the changing of the position of a toggle from a first position to a second position. A person of ordinary skill in the art will appreciate that while toggles typically have only two functional positions, it is known in the art to have a multi-position toggle settable to three or more positions. A person of ordinary skill in the art will also appreciate that a continuous dimmer would appear to the system as a continuously variable set of toggle positions. Description is provided herein using the illustrative embodiment of a binary toggle, but a person of ordinary skill in the art will understand that the teachings of this disclosure may be easily adapted to implement the invention in a three-position toggle or more.
Described herein are devices, systems, and methods for modifying an existing electrical system to utilize the power state output of a physical switch as an indicator or signal for the operation of a smart home device or system or network of such devices. At the core of the problem solved by the present disclosure is the non-interoperability of physical switches with smart devices. As described in the background section, and shown in prior art
To solve this problem, the apparatus and methods described herein include a “smart switch” device. Generally speaking, the smart switch detects or determines the power state of a circuit and infers the corresponding state of a mechanical switch that operates the circuit. This information is then transmitted to associated smart devices, allowing a smart device that is not physically connected to the circuit controlled by the switch to nevertheless effectively operate as thought it was. Thus, when the mechanical switch is operated, it can control both an electrically attached load (e.g., a conventional light) and wirelessly operate electrically unconnected smart devices. Both an apparatus having a structure for these functions and methods, and the functions and methods themselves, are described herein.
Generally at a high level, described herein is a smart switch apparatus (117) attachable to, or integrated with, a conventional power circuit. An embodiment of such an apparatus (117) is depicted in
The smart switch apparatus (117) contains circuitry, components and/or software configured to detect that the circuit is on and that the circuit state is powered. This is done by measuring or detecting current flowing into the device (117). Based on this information, the apparatus (117) may then utilize a transceiver to broadcast or transmit a wireless signal to other smart devices, such as the depicted ceiling lamp (109A), and floor lamp (109B). As can be seen in
For example, as will be clear to a person of ordinary skill in the art, the ceiling lamp (109A) depicted in
As will also be clear, this configuration allows the floor lamp (109B) equipped with a smart bulb (109B) to be moved elsewhere in the room, to any available socket, without affecting the operation of the lamp (109B) via the depicted switch (107). The techniques and methods for pairing the apparatus (117) with the depicted smart devices (109A) and (109B) are by now familiar and well known to a person of ordinary skill in the art and need not be explained here.
The apparatus (117) may be enclosed in a housing and adapted to be plugged into a power receptacle (102A), or may be a power receptacle itself which integrates the features and functions described herein, while also providing a power outlet into which other electrical devices may be plugged.
As will be readily appreciated by a person of ordinary skill in the art, the particular circuit geometry and configuration of the apparatus (117) will vary from embodiment to embodiment depending upon factors such as the size and shape of the housing, components, and intended use case. By way of example, and not limitation, the program logic may be hard coded into a controller contained within the apparatus (117). Alternatively, the apparatus (117) may include a microprocessor, along with program instructions stored on a computer-readable memory disposed within the apparatus (117). These and other techniques for implementing the functionality described herein are known, and need not be further explained.
For example, when a smart bulb is first purchased and screwed into a floor lamp, and provided power, the bulb has no way of knowing what brightness level the user may desire, nor whether the user desires for the bulb to be on or off. Typically, the device will be pre-programmed by the manufacturer with a default setting, such as turning on at full-brightness. If the bulb is later provided with instructions to alter state, such as to switch to half-brightness, but the switch (107) is toggled off (cutting power), the bulb may reset to its default settings when power is restored. When the switch (107) is closed, the bulb (109) will thus re-illuminate at full brightness, even though the user had previously provided a half brightness setting.
The depicted embodiment solves this problem by integrating the apparatus (117) into a smart bulb (109), and communicating the state with a central controller (401). This configuration may be best understood with reference to a non-limiting, illustrative example. Suppose a user enters the room and turns on the light switch (107), closing the circuit. The bulb (109) then receives power, as does the apparatus (117) embedded therein. The apparatus (117), because it has power, infers the switch (107) state to be on, and transmits a signal to the central controller (401) that the associated light bulb (109) is toggled to a power state of “on.” The user then subsequently alters the power state of the bulb (109) by sending instructions to the bulb to switch to half-brightness. This signal is also detectable by the apparatus (117), which then relays to the central controller (401) this updated state information.
When the switch (107) is open, and power is removed, the bulb turns off, and the secondary power source of the apparatus (117) maintains power long enough for the apparatus (117) to transmit any needed instructions or messages concerning power state, including a message to the central controller (401) that the bulb state (109) is now off. When the switch (107) is once again closed, and power is restored to the bulb (109), the apparatus (117) can query the central controller (401) for the last known settings for the associated bulb (109). The central controller (401) may respond to this message with data indicating that the bulb (109) was set to half-brightness before power was removed, and the apparatus (117) can then set the bulb (109) to that same setting. This allows settings to be retained across power states by storing them externally via the central controller (401).
The “power state” of the switch may be determined directly or indirectly, and that state may be transmitted or relayed using direct or indirect measurements. For example, a measurement of current could be taken and transmitted, where a non-zero measurement indicates “on” and a zero measurement indicates “off.”
As will be clear to a person of ordinary skill in the art, the central controller (401) performs these functions by use of other component systems, such as a memory, and other circuitry and computer components necessary to receive the transmissions from the apparatus (117), and to respond to them. Thus, for example, the central controller (401) itself also comprises a transceiver, as well as other components.
This basic configuration can be expanded upon to use the central controller (401) as a central relay for instructions. That is, the central controller (401) may be a hub for additional inputs, which may be provided manually or by external data sources. For example, the central controller (401) may have access to date/time services (e.g., via a network time protocol server), and may be configured to use this information to vary the brightness upon power-up. When power is restored, and the apparatus (117) queries the central controller (401) for a power state to set the bulb (109) to, the central controller (401) may provide a power state corresponding to the time of day as determined via a network time service. For example, if the detected time is noon, the central controller may indicate that the lamp should be left off. However, if the detected time is midnight, then brightness may be set to maximum. Alternatively, the central controller (401) may maintain an archive of historical settings and use machine/earning/training to infer preferences. For example, the central controller (401) may note that at different times of day, and different times of year, the user prefers certain specific brightness settings. When the lamp is activated, the central controller (401) may consult the current time of day and of year, and return a default brightness setting consistent with prior user preferences. The example of time and day of year is exemplary only and should not be understood as limiting.
Additionally, other devices may be connected to the apparatus (117) via the controller (401), and controlled in the same fashion. In the depicted embodiment of
In an embodiment, the apparatus (117) does not have the optional secondary power source (131). Such an embodiment would still be capable of functioning when power was supplied, but will generally not function when power was removed. This would reduce the utility of the device, but would simplify construction/manufacturing and reduce cost.
A number of further interesting user interactions are possible. Described below is an illustrative example interaction implemented on smart light bulbs installed in a garage, where power is generally supplied to said smart light bulbs through a traditional 2-way electrical switch in said garage. When the switch is operated and those lights power up, an attached smart switch (117) may then send a signal to the central controller (401) indicating that power is on. Based on prior user configuration, the central controller (401) may then transmit a signal to other smart devices, such as those located throughout the attached dwelling, to reduce lighting in the home over a period of time (e.g., the next five minutes). In this way, turning on the garage lights indicates that the house has been emptied and that lights left on may be turned off in the remainder of the home. That is, this setting contains an implicit assumption that when the garage lights are turned on, the occupants are leaving. Similarly, when returning home, the user may turn off the lights in the garage before going into the house. Using these same principles, a signal could be used to turn on the lights in the rest of the home in anticipation of the occupants returning.
Because the power signal into the smart switch (117) indicates whether power was supplied to or removed from a circuit, the precise steps taken in response to a change in power signal depend upon the particular programming of the apparatus (117), and/or the central controller (401). A limitless variety of interactions and secondary effects are possible, depending upon user preferences and programming.
Thus, when the switch is turned “off,” power flows through the second circuit and powers the transceiver (125) and related components, which can then communicate the power state to the smart light (109B) or other connected smart devices to operate them in accordance with the switch (107) state. When the switch is turned back “on,” the second circuit breaks and the first circuit closes, providing power to the conventional load (109A) on the first circuit. The transmitter (125) communicates the new switch (107) state to the smart light (109B) before losing power. A secondary power supply can be included to ensure sufficient time to complete the transmission, as described elsewhere herein.
In this fashion, the outlet (102) may continue to be operated as a conventional outlet (102) on which electrical power is actually cut, removing electrical current from the load (109A) and thereby reducing power consumption from phantom loads. At the same time, smart devices (109B) can also be operated by the switch (107). All of this can be done without having to run new cabling or wiring, but rather by simply replacing a conventional wall switch. In an alternative embodiment, the second set of contacts (703) may be omitted and replaced with a wire, allowing power to be continuously supplied to the transceiver (125) and other components.
The detailed description is intended to be illustrative and should not be understood to limit the scope of the present disclosure. As would be understood by one of ordinary skill in the art, embodiments other than those described in detail herein are encompassed by the present invention. Modifications and variations of the described embodiments may be made without departing from the spirit and scope of the invention. These systems and methods are appropriate for use with smart devices and internet of things ecosystems.
This application is a Continuation-in-Part of U.S. Utility patent application Ser. No. 15/909,744, filed Mar. 1, 2018, and is a Continuation-in-Part of U.S. Utility patent application Ser. No. 15/449,172 filed Mar. 3, 2017. U.S. Utility patent application Ser. No. 15/909,744 is a Continuation-in-Part of U.S. Utility patent application Ser. No. 15/449,172, and is a Continuation-in-Part of U.S. Utility patent application Ser. No. 14/855,031 filed Sep. 15, 2015. U.S. Utility patent application Ser. No. 14/855,031 is a Continuation-in-Part of U.S. Utility patent application Ser. No. 14/698,690 and claims benefit of U.S. Provisional Pat. App. No. 62/074,902. U.S. Utility patent application Ser. No. 15/449,172 claims benefit of U.S. Provisional Pat. App. No. 62/331,220. U.S. Utility patent application Ser. No. 14/698,690 is a Continuation-in-Part of U.S. Utility patent application Ser. No. 14/606,881 filed on Jan. 27, 2015 and claims benefit of U.S. Provisional Pat. App. No. 62/074,902. U.S. Utility patent application Ser. No. 14/606,881 claims benefit of U.S. Provisional Pat. App. No. 61/932,085. The entire disclosures of all of the foregoing documents are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3813579 | Doyle et al. | May 1974 | A |
4054879 | Wright et al. | Oct 1977 | A |
4649388 | Atlas | Mar 1987 | A |
4740045 | Goodson et al. | Apr 1988 | A |
5065104 | Kusko et al. | Nov 1991 | A |
5270720 | Stove | Dec 1993 | A |
5563455 | Cheng | Oct 1996 | A |
5696514 | Nathanson et al. | Dec 1997 | A |
6075797 | Thomas | Jun 2000 | A |
6493380 | Wu et al. | Dec 2002 | B1 |
6539483 | Harrison et al. | Mar 2003 | B1 |
6573861 | Hommel et al. | Jun 2003 | B1 |
6693536 | Bauer Jr. et al. | Feb 2004 | B2 |
7047015 | Hawe | May 2006 | B2 |
7295109 | Kobayashi | Nov 2007 | B2 |
7317419 | Sugar et al. | Jan 2008 | B2 |
7423576 | Sahinoglu et al. | Sep 2008 | B2 |
7649727 | Elberbaum | Jan 2010 | B2 |
7652617 | Kurtz et al. | Jan 2010 | B2 |
7663325 | McDonough et al. | Feb 2010 | B2 |
7733220 | Libby | Jun 2010 | B2 |
8138918 | Habib et al. | Mar 2012 | B2 |
8193929 | Siu et al. | Jun 2012 | B1 |
8269376 | Elberbaum | Sep 2012 | B1 |
8274386 | Dea et al. | Sep 2012 | B1 |
8354925 | Libby et al. | Jan 2013 | B1 |
8402543 | Ranjan et al. | Mar 2013 | B1 |
8456304 | van Doom et al. | Jun 2013 | B2 |
8502666 | Tam et al. | Aug 2013 | B1 |
8531134 | Chemel et al. | Sep 2013 | B2 |
8536998 | Siu et al. | Sep 2013 | B1 |
8552664 | Chemel et al. | Oct 2013 | B2 |
8555388 | Wang et al. | Oct 2013 | B1 |
8593264 | Umezawa et al. | Nov 2013 | B2 |
8624734 | Inomata et al. | Jan 2014 | B2 |
8682812 | Ranjan | Mar 2014 | B1 |
8762298 | Ranjan et al. | Jun 2014 | B1 |
8766556 | Meyer | Jul 2014 | B2 |
8793790 | Khurana et al. | Jul 2014 | B2 |
8818288 | Patwari et al. | Aug 2014 | B2 |
8836344 | Habib et al. | Sep 2014 | B2 |
8842010 | Cehelnik | Sep 2014 | B2 |
8844038 | Niemela | Sep 2014 | B2 |
8849471 | Daniel et al. | Sep 2014 | B2 |
8984581 | Luna et al. | Mar 2015 | B2 |
9143413 | Manku et al. | Sep 2015 | B1 |
9143968 | Manku et al. | Sep 2015 | B1 |
9144041 | Curtis et al. | Sep 2015 | B2 |
9185121 | Chari et al. | Nov 2015 | B2 |
9245426 | Caicedo Fernandez et al. | Jan 2016 | B2 |
9369476 | Chekina et al. | Jun 2016 | B2 |
9378361 | Yen et al. | Jun 2016 | B1 |
9407663 | Pauley, Jr. et al. | Aug 2016 | B1 |
9413839 | Annan et al. | Aug 2016 | B2 |
9523760 | Kravets et al. | Dec 2016 | B1 |
9524628 | Omer et al. | Dec 2016 | B1 |
9575091 | Reeder, III | Feb 2017 | B2 |
9584974 | Omer et al. | Feb 2017 | B1 |
9743294 | Omer et al. | Aug 2017 | B1 |
9900794 | Plan et al. | Feb 2018 | B2 |
9955555 | Lark, Jr. | Apr 2018 | B2 |
20030090917 | Chan et al. | May 2003 | A1 |
20030108119 | Mohebbi et al. | Jun 2003 | A1 |
20040080415 | Sorensen | Apr 2004 | A1 |
20040196140 | Sid | Oct 2004 | A1 |
20050055568 | Agrawala et al. | Mar 2005 | A1 |
20050083199 | Hall et al. | Apr 2005 | A1 |
20060037077 | Gadde et al. | Feb 2006 | A1 |
20060089117 | Suzuki | Apr 2006 | A1 |
20060161270 | Luskin et al. | Jul 2006 | A1 |
20060217132 | Drummond-Murray et al. | Sep 2006 | A1 |
20070007826 | Mosebrook et al. | Jan 2007 | A1 |
20070225000 | Cleveland | Sep 2007 | A1 |
20070283002 | Bomhoevd et al. | Dec 2007 | A1 |
20080024074 | Mosebrook et al. | Jan 2008 | A1 |
20080119130 | Sinha | May 2008 | A1 |
20080148398 | Mezack et al. | Jun 2008 | A1 |
20080240008 | Backes et al. | Oct 2008 | A1 |
20080303655 | Johnson | Dec 2008 | A1 |
20090040952 | Cover et al. | Feb 2009 | A1 |
20090062696 | Nathan et al. | Mar 2009 | A1 |
20090079416 | Vinden et al. | Mar 2009 | A1 |
20090121842 | Elberbaum | May 2009 | A1 |
20090174569 | Smith et al. | Jul 2009 | A1 |
20090184804 | Seppa | Jul 2009 | A1 |
20090241283 | Loveless et al. | Oct 2009 | A1 |
20090256483 | Gehman et al. | Oct 2009 | A1 |
20090267632 | Rowe et al. | Oct 2009 | A1 |
20100070217 | Shimada et al. | Mar 2010 | A1 |
20100125897 | Jain et al. | May 2010 | A1 |
20100145545 | Mosebrook et al. | Jun 2010 | A1 |
20100278537 | Elberbaum | Nov 2010 | A1 |
20100301775 | Bella | Dec 2010 | A1 |
20100315284 | Trinza | Dec 2010 | A1 |
20110082599 | Shinde et al. | Apr 2011 | A1 |
20110109301 | Johnson et al. | May 2011 | A1 |
20110130092 | Yun et al. | Jun 2011 | A1 |
20110141647 | Garcia et al. | Jun 2011 | A1 |
20110153811 | Jeong et al. | Jun 2011 | A1 |
20110175553 | Sampsell | Jul 2011 | A1 |
20110211563 | Herrala et al. | Sep 2011 | A1 |
20110304205 | Lee | Dec 2011 | A1 |
20110309931 | Rose | Dec 2011 | A1 |
20120009882 | Patwari et al. | Jan 2012 | A1 |
20120046003 | Ying | Feb 2012 | A1 |
20120049639 | Besore et al. | Mar 2012 | A1 |
20120092060 | Ganesan | Apr 2012 | A1 |
20120115512 | Grainger et al. | May 2012 | A1 |
20120146788 | Wilson et al. | Jun 2012 | A1 |
20120181865 | Muthu | Jul 2012 | A1 |
20120184296 | Milosiu et al. | Jul 2012 | A1 |
20120207481 | Elberbaum | Aug 2012 | A1 |
20120207484 | Hunt | Aug 2012 | A1 |
20120262006 | Elberbaum | Oct 2012 | A1 |
20120280822 | Kuo | Nov 2012 | A1 |
20130090151 | Ngai et al. | Apr 2013 | A1 |
20130102264 | Nakane et al. | Apr 2013 | A1 |
20130162459 | Aharony et al. | Jun 2013 | A1 |
20130175863 | Pan | Jul 2013 | A1 |
20130201316 | Binder et al. | Aug 2013 | A1 |
20130260602 | German et al. | Oct 2013 | A1 |
20130283256 | Proud | Oct 2013 | A1 |
20130320769 | Sawyers | Dec 2013 | A1 |
20140004874 | Schwartz et al. | Jan 2014 | A1 |
20140005809 | Frei et al. | Jan 2014 | A1 |
20140015706 | Ishihara et al. | Jan 2014 | A1 |
20140097758 | Recker et al. | Apr 2014 | A1 |
20140105079 | Bengtsson et al. | Apr 2014 | A1 |
20140117780 | Buchheim et al. | May 2014 | A1 |
20140117871 | Swatsky et al. | May 2014 | A1 |
20140128778 | Chan et al. | May 2014 | A1 |
20140135042 | Buchheim et al. | May 2014 | A1 |
20140140231 | Haiut et al. | May 2014 | A1 |
20140165207 | Engel et al. | Jun 2014 | A1 |
20140169795 | Clough | Jun 2014 | A1 |
20140211345 | Thompson et al. | Jul 2014 | A1 |
20140214218 | Eldridge et al. | Jul 2014 | A1 |
20140247179 | Furuskog et al. | Sep 2014 | A1 |
20140265881 | Karc | Sep 2014 | A1 |
20140266171 | Mosser et al. | Sep 2014 | A1 |
20140286380 | Prager et al. | Sep 2014 | A1 |
20140330960 | Naga et al. | Nov 2014 | A1 |
20150005900 | Steele et al. | Jan 2015 | A1 |
20150022123 | Van De Sluis et al. | Jan 2015 | A1 |
20150022181 | Anderson et al. | Jan 2015 | A1 |
20150043377 | Cholas et al. | Feb 2015 | A1 |
20150049745 | Han et al. | Feb 2015 | A1 |
20150049792 | Han et al. | Feb 2015 | A1 |
20150059086 | Clough | Mar 2015 | A1 |
20150059248 | Iwata et al. | Mar 2015 | A1 |
20150069242 | Alameh et al. | Mar 2015 | A1 |
20150078295 | Mandyam et al. | Mar 2015 | A1 |
20150088331 | Fiedler et al. | Mar 2015 | A1 |
20150098377 | Amini et al. | Apr 2015 | A1 |
20150143454 | Lee et al. | May 2015 | A1 |
20150195100 | Imes et al. | Jul 2015 | A1 |
20150212205 | Shpater | Jul 2015 | A1 |
20150236848 | Ma et al. | Aug 2015 | A1 |
20150245164 | Merrill | Aug 2015 | A1 |
20150257167 | Chen et al. | Sep 2015 | A1 |
20150295808 | O'Malley et al. | Oct 2015 | A1 |
20150301173 | Vangeel et al. | Oct 2015 | A1 |
20150338507 | Oh et al. | Nov 2015 | A1 |
20160018508 | Chen et al. | Jan 2016 | A1 |
20160028763 | Cruz Mota et al. | Jan 2016 | A1 |
20160050182 | Edross | Feb 2016 | A1 |
20160050224 | Ricafort et al. | Feb 2016 | A1 |
20160126031 | Wootton et al. | May 2016 | A1 |
20160183059 | Nagy et al. | Jun 2016 | A1 |
20160187475 | Horng et al. | Jun 2016 | A1 |
20160210838 | Yan et al. | Jul 2016 | A1 |
20160234167 | Engel et al. | Aug 2016 | A1 |
20160241999 | Chin et al. | Aug 2016 | A1 |
20170146656 | Belsley et al. | May 2017 | A1 |
20170343658 | Ramirez et al. | Nov 2017 | A1 |
20180026484 | Ku et al. | Jan 2018 | A1 |
20180070431 | Charlton et al. | Mar 2018 | A1 |
20180131554 | Liu et al. | May 2018 | A1 |
Number | Date | Country |
---|---|---|
2834522 | May 2014 | CA |
2945702 | Aug 2015 | CA |
1909755 | Feb 2007 | CN |
101184353 | May 2008 | CN |
201319687 | Sep 2009 | CN |
201467534 | May 2010 | CN |
201639825 | Nov 2010 | CN |
201839492 | May 2011 | CN |
102131327 | Jul 2011 | CN |
202475882 | Oct 2012 | CN |
202738203 | Feb 2013 | CN |
202759621 | Feb 2013 | CN |
203241317 | Oct 2013 | CN |
203243557 | Oct 2013 | CN |
203251317 | Oct 2013 | CN |
1829003 | Nov 2013 | EP |
2005136532 | May 2005 | JP |
2006129098 | May 2006 | JP |
2007159370 | Jun 2007 | JP |
2008042998 | Feb 2008 | JP |
2008305800 | Dec 2008 | JP |
2011109784 | Jun 2011 | JP |
201552475 | Mar 2015 | JP |
100887425 | Mar 2009 | KR |
100912039 | Aug 2009 | KR |
20090113941 | Nov 2009 | KR |
101009613 | Jan 2011 | KR |
20130012996 | Feb 2013 | KR |
20130017298 | Feb 2013 | KR |
20140080755 | Jul 2014 | KR |
20140120748 | Oct 2014 | KR |
2008035322 | Mar 2008 | WO |
2011055199 | May 2011 | WO |
2011062445 | May 2011 | WO |
2012010170 | Jan 2012 | WO |
2014021574 | Feb 2014 | WO |
2014026226 | Feb 2014 | WO |
2014109486 | Jul 2014 | WO |
2014201574 | Dec 2014 | WO |
2015035830 | Mar 2015 | WO |
2015168700 | Nov 2015 | WO |
Entry |
---|
International Search Report, International Patent Application No. PCT/US20151013127, dated Apr. 24, 2015 (10 pages). |
International Search Report, International Patent Application No. PCT/US20151058019, dated Feb. 5, 2016 (10 pages). |
International Search Report, International Patent Application No. PCT/US20151057869, dated Feb. 5, 2016, 10 pages. |
International Search Report, International Patent Application No. PCT/US20171030864, dated Jul. 28, 2017 (13 pages). |
Supplementary European Search Report, European Application No. EP 15 74 0354.4, dated Sep. 20, 2017 (8 pages). |
Supplementary European Search Report, European Application No. EP 15 85 7587.8, dated Sep. 20, 2017 (12 pages). |
Using Encryption: Bluetooth Technology, http://www.brighthub.com/computing/smb-security/articles/106638.aspx, Feb. 15, 2011 (5 pages). |
Youssef, Moustafa, et al., “Challenges: Device-free Passive Localization for Wireless Environments”, Mobicom 2007 Proceedings of the 13th Annual ACM International Conference on Mobile Computing and Networking, held on Sep. 9-14, 2007, in Montreal, Quebec, Canada, pp. 222-229 (8 pages). |
NETGEAR®, “N600 WiFi Cable Modem Router, Model C3700 User Manual”, dated Mar. 2014 (101 pages). |
OpenWRT, “Wireless Configuration”, https://web.archive.org/web/20140402033233/http://wiki.openwrt.org/doc/uci/wireless (capture of URL http://wiki.openwrt.org/doc/uci/wireless on Apr. 2, 2014), printed on Jan. 25, 2018 (10 pages). |
Japan Radio Co., LTD; “26GHz FWA—Technology”; http://www.jrc.co.jp/eng/product/lineup/26ghz_wireless_ip_ access_system/tech.html, printed on Jan. 25, 2018 (3 pages). |
Apple Insider; “Intel to reportedly supply LTE chips for 2016 iPhone”; http://appleinsidercom/articles/15/03/11/intel-to-reportedly-supply-lte-chips-for-2016-iphone, printed on Jan. 25, 2018 (9 pages). |
CEVA; CEVA's DSP Cores Power the World's Leading Mobile Broadband and M2M Applications; http://www.ceva-dsp.com/Mobile-Broadband; May 15, 2016, printed on Jan. 28, 2018 (3 pages). |
quora.com; “What is the function of the baseband processor in wireless devices?”; https://www.quora.com/What-is-the-function-of-the-baseband-processor-in-wireless-devices; May 15, 2016, printed on Jan. 25, 2018 (2 pages). |
Wikipedia; “Baseband processor”, https://en.wikipedia.org/wiki/Bandband_processor; 2 pages; version dated Apr. 19, 2016, printed on Jan. 25, 2018 (1 page). |
International Search Report, International Patent Application No. PCT/US2015/013127, dated Apr. 24, 2015 (10 pages). |
International Search Report, International Patent Application No. PCT/US2015/058019, dated Feb. 5, 2016 (10 pages). |
International Search Report, International Patent Application No. PCT/US2015/057869, dated Feb. 5, 2016 (10 pages). |
International Search Report, International Patent Application No. PCT/US2016/016836, dated May 24, 2016 (12 pages). |
International Search Report, International Patent Application No. PCT/US2016/045611, dated May 16, 2017 (10 pages). |
Extended European Search Report, International Patent Application No. EP15857698, dated Jun. 5, 2018 (12 pages). |
Adib, Fadel et al., “See Through Walls with Wi-Fi” ACM SIGCOMM Computer Communication Review, Oct. 2013, vol. 43, Issue 4, pp. 75-86 (12 pages). |
Number | Date | Country | |
---|---|---|---|
20180324934 A1 | Nov 2018 | US |
Number | Date | Country | |
---|---|---|---|
62074902 | Nov 2014 | US | |
62074902 | Nov 2014 | US | |
62331220 | May 2016 | US | |
61932085 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15909744 | Mar 2018 | US |
Child | 16035141 | US | |
Parent | 15449172 | Mar 2017 | US |
Child | 15909744 | US | |
Parent | 14855031 | Sep 2015 | US |
Child | 15909744 | US | |
Parent | 14698690 | Apr 2015 | US |
Child | 14855031 | US | |
Parent | 15449172 | Mar 2017 | US |
Child | 14698690 | US | |
Parent | 14606881 | Jan 2015 | US |
Child | 15449172 | US | |
Parent | 15449172 | Mar 2017 | US |
Child | 15909744 | US | |
Parent | 14698690 | Apr 2015 | US |
Child | 14855031 | US | |
Parent | 14606881 | Jan 2015 | US |
Child | 14698690 | US |