The described embodiments relate generally to electronics within a structure. More particularly, the described embodiments relate to a distributed network of a structure that provides location-based human interaction and intelligence.
Lighting control of a structure can be used to automatically control lighting under certain conditions, thereby conserving power. However, lighting control, specifically advanced lighting controls have not been widely adopted in the general commercial market because the installation, setup related costs and complexity have made these lighting systems prohibitively expensive for most commercial customers. Additionally, if these systems include intelligence, they are centrally controlled.
Additionally, the management of the resources, control, and security of structures is not intelligent or location aware.
It is desirable to have a lighting method, system and apparatus for distributed network for providing intelligent location-based human interaction and intelligence.
One embodiment includes a distributed network of a structure. The distributed network includes a plurality of wireless transceivers distributed about the structure, a plurality of sensors distributed about the structure, and a controller electronically connected to the plurality of wireless transceivers, and the plurality of sensors. The plurality of wireless transceiver is operative to transmit time-based (varying) tokens through a low-power first network, wherein the low-power first network includes the plurality of wireless transceivers. A controller is operative to receive modified time-based tokens from a mobile device through a second network, wherein the modified time-based tokens include identification information of the mobile device that has been appended to the time-base tokens, and perform location-based intelligence based on the identification information and the time-based tokens.
Another embodiment includes a distributed network of a structure. The distributed network includes a plurality of wireless transceivers distributed about the structure, a plurality of sensors distributed about the structure, and at least one controller of the plurality of wireless transceivers electronically connected to at least a subset the plurality of wireless transceivers, and the plurality of sensors. The plurality of transceivers is operative to transmit time-based tokens through a low-power first network, wherein the low-power first network includes the plurality of wireless transceivers. The at least one controller is operative to receive modified time-based tokens from a mobile device through a second network, wherein the modified time-based tokens include identification information of the mobile device or the at least one asset tag that has been appended to the time-base tokens, and perform location-based intelligence based on the identification information and the time-based tokens.
Other aspects and advantages of the described embodiments will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the described embodiments.
The described embodiments are embodied in apparatuses and methods for a distributed network of a structure that provides location-based human interaction and intelligent use of the structure.
Further, as shown, for at least some embodiments the structure further includes sensor devices 111, 112. The sensors 111, 112 are operative to sense conditions within the structure 100. For an embodiment, the sensors 111, 112 are operative to sense at least one of motion, light, sound, temperature, humidity, and/or vibration within the structure. It is to be understood that the listed sensor types are by example, and that any other type of sensors can additionally or alternatively be utilized. While
For at least some embodiments, the structure 100 includes controlled devices 121, 122. For an embodiment, the controlled devices 121, 122 devices include appliances (also referred to as asset tags), such as, printers, coffee makers, refrigerators, copiers, fax machines, etc. The controlled devices 121, 122 can be controlled, and status information of the controlled devices 121, 122 can be checked. While
For at least some embodiments, the sensors 111, 112 and/or the controlled devices 121, 122 are electronically coupled to one or more of the wireless transceivers 101-110. For at least some embodiments, the sensors 111, 112 and/or the controlled devices 121, 122 are wirelessly coupled to one or more of the wireless transceivers 101-110, thereby allowing control information to be sent to the sensors 111, 112 and/or the controlled devices 121, 122, and sensor or device information to be retrieved from the sensors 111, 112 and/or the controlled devices 121, 122.
Further, for at least some embodiments, as will be shown and described, a lighting fixture includes at least one of the sensors (such as, sensor 111), and at least one of the transceivers (such as, transceiver 102). Further, for at least some embodiments, the lighting fixture includes at least a portion of the controller 130.
For an embodiment, the transceivers 101-110 are electronically connected to a controller 130. The controller 130 is operable to receive information from any of the wireless transceivers 101-110, the sensors 111, 112, and/or the controlled devices 121, 122. Further, the controller 130 is operative to store the received information. Further, the controller 130 is operative to provide location-based human interaction and intelligence based on the received information and the stored information.
While the controller 130 is depicted as a single standalone controller, it is to be understood that the control of the distributed network can include many distributed controllers. For an embodiment, the network control is distributed amongst at least the wireless transceivers 101-110 (which can be included within a light fixture). Distributed networks are more resilient to failure of portions of the network. For at least some embodiments, the communication links between the wireless transceivers 101-110 and the controller 130 includes one or more wireless communication links.
For at least some embodiments, the wireless transceivers 101-110 are low-power transceivers. That is, the transmission signals of the wireless transceivers 101-110 are low-power, and therefore, have a limited range. For at least some embodiments, the transmission power is limited to be less than a threshold, thereby ensuring that all devices receiving the transmission signals are within a threshold distance of the transmitting transceiver. Therefore, a mobile device 140 of a user within the structure can only communicate with one or more of the wireless transceivers 101-110 that are proximate enough to maintain a communication link. Due to the proximity of the mobile device 140 to the transceiver that the mobile device 140 is communicating with, a location of the mobile device 140 can be estimated. Additionally, the sensors 111, 112 of the structure 100 are operative to determine occupancy and motion of the user of the mobile device within the structure 100.
For at least some embodiments, the sensors 111, 112, and/or sensors associated with anyone of the wireless transceivers 101-110 sense motion and/or occupancy within the structure 100. Further, the sensors 111, 112, and/or sensors associated with anyone of the wireless transceivers 101-110 are utilized to sense motion of occupants within the structure 100.
For an embodiment, the mobile device 140 is operative to couple to the controller 130 through the wireless transceivers 101-110. For an embodiment, the downstream communication from the controller 130 to the mobile device is through the low-power or first network (such as, but not limited to, Bluetooth, Zigbee, or IEEE 802.15.4). For an embodiment, the upstream communication from the mobile device 140 to the controller 130 is through a second network (such as a WiFi network) that includes the wireless transceivers 101-110. That is, for an embodiment, the wireless transceivers 101-110 include both the first network and the second network that support downstream and upstream communication between the controller 130 and the mobile device 140. For another embodiment, the upstream communication from the mobile device 140 to the controller 130 is through an external network (such as, a cellular network).
For an embodiment, the wireless transceivers 101-110 are associated with lighting fixtures that additionally include lighting control and sensors.
For at least some embodiments, the described infrastructure is used to sense and identify occupants of the structure. For at least some embodiments, the described infrastructure is used to locate occupants within the structure. For at least some embodiments, the described infrastructure is used to provide real-time updates of identification/location to other occupants and resource allocation systems.
For at least some embodiments, the described infrastructure is used to provide real-time availability of resources of the structure. For at least some embodiments, the described infrastructure is used to provide resource location/availability. For at least some embodiments, the described infrastructure is used to provide real-time updates of resource location/availability to occupants and resource allocation systems. For at least some embodiments, the described infrastructure provides a user of a mobile device access and control to devices and resources (internet of things) within the structure 100.
A third step 330 includes the mobile device appending identification information to the received time-based token information with information related to the mobile device, time of token reception and a new period of validity for the appended token. The mobile device then transmits the identification information and the time-based token information back to a controller through a second network. For an embodiment, the second network includes a cellular network. For an embodiment, the second network includes a WiFi or IEEE 802.11 network associated with the transceiver and/or other transceivers of the distributed network of the structure 100.
A fourth step 340 includes the controller performing location-based intelligence based on the identification information and the time-based token information. For at least some embodiments, the controller tracks the mobile device movements within the building (structure). Further, for at least some embodiments, in real time, the controller verifies if a specific location of the mobile device is acceptable as per an access level assigned to mobile device and its user. If the location is identified to be outside of the access level, the controller sends command to one or more transceivers in the proximity of mobile device to, for example, blink the lights (or any other form of communication) as a warning. Also, the controller sends message to the mobile device with violation information and course of action to be taken by the user. In addition, controller also sends message to configured security authority on violation.
For at least some embodiments, location based intelligence includes identifying location of occupant/asset tag within the structure and providing specific services that are appropriate for the location at that time. Specific services include, but not limited to, a resource map, resource identification, resource status information, controlling of a resource, communication with occupants and/or assets in the proximity a user, and location specific tracking of occupants and/or assets. Examples of assets include, but are not limited to, lab equipment, health care equipment, movable machines, retail products and event tickets of specific type. These assets are equipment with communication tags that enable location identification and access check.
A first step 410 includes the controller identifying the location of the mobile device based on the communicated time of the at least one time-based token. For an embodiment, the location is estimated based on knowing the location of the transceiver that transmitted the time-based token. That is, because the time-based tokens are transmitted through a low transmission signal power first network, the location of the mobile device can be estimated by knowing the transceiver and the location of the transmitter that transmitted the time-based token. The time element allows for easy determination of when the time-based token was transmitted.
A second step 420 includes the controller sending a command to open the door if the mobile device is determined to be proximate to a door of the structure and the mobile device satisfies a criteria. An embodiment includes communicating a door-open request to the controller wherein the door-opening request is based on the door-token, and is communicated to the server through a second network. For an embodiment, the second network includes a WiFi network of the wireless transceivers (for example, the wireless transceivers 101-110) of the structure. At least some embodiments include the controller communicating with a control device of the structure that is operable to open a door of the structure, thereby allowing a user of the mobile device to enter the structure.
A third step 430 includes the controller managing access of the user of the mobile device through the structure. That is, the location(s) of the mobile user is determined as the user travels or navigates through the structure. Further, the controller can access a data source that includes where the user is to have access, and where the user is not to have access.
A fourth step 440 includes the controller tracking access/activity of the user of the mobile device through the structure. For at least some embodiments, this tracking includes recording of the pathways taken by the mobile user and the resources utilized by the mobile user throughout the structure.
A first step 510 includes the controller identifying the location of the asset tag based on the communicated time of the at least one time-based token. A second step 520 includes the controller determining whether asset tag is authorized to be in the identified location and performs any required actions. A third step 530 includes the controller tracking asset tag through the structure and performing any required actions.
For at least some embodiments, if the asset is not authorized to be at the identified location, the controller communicates with building management system on the violation, thereby allowing the building management system to take necessary action. In addition, for at least some embodiments, the controller communicates to configured facility and asset management personnel on violation with identified location.
For at least some embodiments, tracking of an asset includes, but is not limited to, historical and current location of assets within the structure, historical and current utilization of the asset and this information contextualized with other relevant structure specific information (meta data). Examples of meta data include a name of the space, conditions under which asset is used or moved and potentially the users/movers of the assets.
For at least some embodiments, the type of resources are wide ranging, and include, for example, conference rooms, hoteling spaces, printers/copiers, lab equipment, coffee machines, cafeteria, phone rooms etc. Access and control of specific configured resource is enabled by the communication between the mobile device, the server and the transceivers in the proximity of mobile devices. In the cases where the specific resource is configured to communicate with building management system, the server facilitates the additional communication needed to execute the access and control of resource. In some cases, given specific configuration of resources, the mobile device will be able to communicate and control resources via low power network such as Bluetooth or WiFi.
During emergency, if one or a group of the mobile devices is identified to be in the proximity of danger, the controller communicates course of action messages for the group of mobile devices for them to coordinate as a group to escape danger. The controller also sends the location and other relevant information on the user of mobile devices to facility and emergency management personnel.
For at least some embodiments, information of a plurality of mobile devices enables resource to occupant balancing actions in structures such as stadiums, retail environments and enterprise hoteling spaces. In addition, information of a plurality of mobile devices enable service improvement actions in structures such as cafeteria, retail environments etc. For at least some embodiments, actions that maximize service level and/or user experience is provided via software applications that use the location of plurality of mobile devices.
For at least some embodiments, information of a plurality of other mobile devices in proximity of a user of the mobile device is used to establish location aware enterprise social network. This social network enables individual occupant to instantaneously communicate with other occupants who are part of the network. Software applications that use this location of plurality of mobile devices enable real time communication that helps to achieve higher productivity.
In structures such as enterprise workplace environments, location of plurality of mobile devices enable real time communication to specific set of mobile users with location specific activities that could improve their knowledge, participation towards enterprise goals and thereby improving their contribution to company's vision. In structures such as stadium or retail environments, location of plurality of mobile devices enable delivering user group size specific services such as dispatch of service attendants for the group and delivering user specific services for subset of users such as proximate product/resource information.
For an embodiment, one or more of the sensor 111, 112 include acoustic sensors, such as, a microphone. The one or more microphones sense proximate sound. For an embodiment, the one or more microphones provide the sensed sound to the controller 130. For an embodiment, the controller tracks the sensed sound over time. Further, for an embodiment, the sensed sound is recorded over time, allowing for the determination of a base-line level of sound or characteristic of sound, which can be identified as a normal sound characteristic for the structure (at least proximate to the one or more acoustic sensors).
Further, for an embodiment, the sensed sound recorded over time is compared to later sensed sound. The comparison can be used to determine anomalies, suggesting an occurrence an atypical event. For example, an atypical event, such as, a fall of an occupant, a water leak, equipment not operating correctly, the presence of machinery in an unexpected place, sound (decibel) levels below or above expected thresholds, can exhibit sound that is difference from the baseline of “normal” operations and activities within the structure (proximate to the one or more acoustic sensors). Therefore, comparison of the base-line sound with the atypical event can be used to identify the occurrence of the atypical event.
For an embodiment, the controller is operative to receive sound sensed by the acoustic sensor, matched the sensed sound with at least one of a plurality of predetermined sounds, and execute a predetermine action based on matching of the sound with the at least one of a plurality of predetermined sounds.
Further, for an embodiment, once an atypical or anomaly event has been detected, an action is initiated. For at least some embodiments, the action includes communicating an action to a device within the structure. For example, the identification of an atypical or anomaly event can be used to initiate a visual sensor within the structure. Further, warnings can be communicated to particular users, or user devices.
For an embodiment, the acoustic sensor includes a microphone located in at least one of the transceivers that observes the sound signal and communicates to the controller.
For an embodiment, the controller processes the sound signal from each time point with historical signal to determine the change and to decide if the change is anomaly and/or matches with the defined fault signal.
For an embodiment, based on the historical data, controller has the baseline “normal” signal. Controller is provided with specific fault signals (such as fall of the occupant, water leak, equipment not operating correctly, presence of machinery in the unexpected space, decibel levels below or above expected threshold etc.). For each of these fault signals, controller is provided with action to be taken.
For an embodiment, the controller takes predefined action on communication in the case of specific anomaly/fault. The action may include communication to transceivers for visual signaling. The action may also include communicating to specific mobile devices on the occurrence of fault/anomaly.
For an embodiment, the one or more acoustic sensors are utilized to providing voice command capabilities. For example, a predetermined set of voice commands can be identified, and corresponding actions based on the voice commands identified.
For an embodiment, reception of a voice command by the controller causes the controller to initiate an action. For example, voice commands received by the one or more acoustic sensors and communicated to the controller can include light level control (voice command could include “on”, “off”, “brighter”, “dimmer”, etc.), scene control, plug load, temperature control, shades (up, down, in-between). For an embodiment, the voice command can be heard by the resource being controlled via low power network such as Bluetooth and the resource can respond to the command. In this case, the controller records the received command and actions are taken by resource for tracking purpose.
For an embodiment, the microphone of at least one of the transceivers observes a sound signal emanating from within the structure.
For an embodiment, each transceiver has specific list of predefined command verses and associated actions. The actions may include controlling the light level, selecting particular scene, controlling other resources such as plugload/AV/Shade etc, sending a specific message to controller for it to execute actions such as cry for help, fault reporting etc.
For at least some embodiments, the transceivers initiate action as appropriate for the command received. For at least some embodiments specific transceivers among the transceivers listening take action. For example, “light is not working” command makes the transceivers check the metering data and the one with faulty metering reading communicates that its associated light isn't working to the predefined mobile devices.
For at least some embodiments, all transceivers listening take action such as dimming light or going to a scene.
For at least some embodiments, all transceivers listening send a message to the controller, and the controller reconciles the messages and takes action. The action may include communicating specific action command to transceivers or communicating to mobile devices or communicating to building management systems or all of the above.
The described embodiments can be implemented using a light emitting diodes (LED) fixture that includes intelligence. The light fixture allows for intelligent control of the light of the light fixture. The light fixture can be networked with other light fixtures allowing for distributed control of multiple light fixtures. Additionally, embodiments of the light include network interfaces for additional or alternative light control.
For an embodiment, the LED Driver and Control Unit 1030 provides power to the sensor unit 1040, and the sensor unit 1040 provides control signals to the LED Driver and Control Unit 1030. This embodiment further includes a communications link being established between the sensor unit 1040 and a network or other devices. However, rather than being connected to a network, the sensor unit can connect to other sensor units and LED Driver and Control Units, allowing for decentralized control of a plurality of light fixtures. For a specific embodiment, the sensor unit 1040 includes at least one antenna 1050 and is wirelessly linked (through, for example, BLUETOOH® or ZIGBEE®) to the network, or other devices.
The wireless link can advantageously be located within the sensor unit 1040 rather than within the LED Driver and Control Unit 1030 because some configurations include the LED Driver and Control Unit 1030 being located within a common metal enclosure as the light fixture 1000. Locating the wireless link within the LED Driver and Control Unit 1030 could subject the wireless link to attenuation cause by the metal enclosure. By locating the antenna proximate to, but outside of the metal enclosure of the light fixture 1000, the quality of the wireless link can be sustained.
For an embodiment, the conductor providing power from the LED Driver and Control Unit 1030 to the sensor unit 1040, and the conductor(s) providing control signal(s) from the sensor unit 1040 to the LED Driver and Control Unit 1030 are located in a common cable. For an embodiment, the voltage provided to power the sensor unit 1040 is, for example, a low-power DC voltage. Being a low voltage, the sensor unit 1040 can be connected, and re-connected to the LED Driver and Control Unit 1030 by a lay-person (that is, a skilled, high-cost technician is not required for deploying the LED lighting system). That is, the voltage supply is low enough that, for example, replacement of the sensor unit is safe enough that an electrician is not required to make the replacement. For an embodiment, the sensor unit 1040 is attached to a ceiling proximate to the LED Driver and Control Unit 1030. The cable allows for easy installation of the retrofit LED Driver and Control Unit 1030 and retrofit sensor unit 1040. Exemplary cables include a flat cable with a RJ-45, RJ-50 like connector at either end. Flat cables can be desirable because that can easily slip easily between a guide-rail and a ceiling tile of a typical industrial ceiling, without requiring a hole in the tile.
Embodiments include all of the LED processing based on the sensed signals and any network input occurring all or partially within the sensor unit 1040. Other embodiments include varying amount of the driver control processing occurring within the LED Driver and Control Unit 1030. As indicated in
A manual switch, dimming control or timing dimming control unit 1060 can provide manual dimming control. Dimming control can be transferred from automated control provided by the LED Driver and Control Unit 1030 and the sensor unit 1040, to manual control provided by the dimming control unit 1060, by the dimming control unit 1060 communicating a transfer of control. The transfer of control can be communicated, for example, by the dimming control unit 1060 cycling power supplied by the dimming control unit 1060 according to a predetermined sequence. For example, the predetermined sequence can include manually power cycling by the dimming control unit 1060 three times within a predetermined amount of time. If the LED Driver and Control Unit 1030 and the sensor unit 1040 combination receives the power cycling according to the predetermined sequence (three cycles) then the manual over-ride is invoked, and the dimming control unit 1060 provides manual control until, for example, another sequence transfers dimming control back to the LED Driver and Control Unit 1030 and the sensor unit 1040 combination. Once in manual mode, the sensed signals no longer influence the dimming control.
An existing light fixture can be upgraded as shown in
The sensor and control unit 1040 includes sensors that sense conditions that are used for controlling the intensity of light emitted from the LED 1010. Such sensed signals include at least one of motion, light, temperature, images, etc. It is to be understood that this is not an exhaustive list of possible sensed conditions.
The power factor correction circuit 1191 receives AC voltage power, and adjusts the phase of the received AC voltage. The power factor correction circuit 1191 provides power factor correction.
The AC to DC transformer 1192 converts the received AC voltage to a DC voltage which is useable by the rest of the LED Driver and Control Unit 1130 and the sensor unit 1140. Sensor power circuit 1195 provides a low-power voltage to the sensor unit 1140.
The control logic and power metering circuitry 1193 amongst other things, receives sensed signals from the sensor unit 1140. For an embodiment, the control logic and power metering circuitry 1193 generates LED driver control signals for controlling an intensity of light of the LEDs 110, 112 based on the LED driver control signals.
As shown, LED string drivers 1194, 1196 receive the LED driver control signals and generate current drive signals (I, I′) for controlling the intensity of light emitted from the LEDs 1110, 1112.
For an embodiment, the LED Driver and Control Unit 1130 also monitors the power consumed by the LED Driver and Control Unit 1130, the sensor unit 31140 and the LEDs 1110, 1112.
The sensor unit 1202 additionally includes a sensor 1240 (which includes at least one of the previously described sensors, such as, sensors 111, 112). As indicated, the sensor 1240 can include one or more of a light sensor 1241, a motion sensor 1242, a temperature sensor 1243, a camera 1244, an air quality sensor 1248, a near field communication sensor 1246 and/or an RFID (radio frequency identification) sensor 1247. It is to be understood that this is not an exhaustive list of sensors. That is additional or alternate sensors can be utilized for lighting and/or environmental control of a structure that utilizes the lighting control sub-system 1200. The sensor 1240 is coupled to the sensor unit CPU 1245, and the sensor 1240 generates a sensed input.
According to at least some embodiments, the controllers (manager CPU 1220 and the sensor unit CPU 1245) are operative to control a light output of the light unit 1230 based at least in part on the sensed input, and communicate at least one of state or sensed information to the external device. Further, the controllers (manager CPU 1220 and the sensor unit CPU 1245) are operative to control a light output of the light unit 1230 based at least in part on control received from the external controller 130.
For at least some embodiments, the dimming controller 1204 receives the DC voltage and generates power control for the light unit 1230, and generates a low-voltage supply for the sensor unit 1202. As suggested, the dimming controller 1204 and the smart sensor unit 1202 interact to control a light output of the light unit 1230 based at least in part on the sensed input, and communicate at least one of state or sensed information to the external device. The dimming controller 1204 and the sensor unit 1202 can also receive state or control information from the external device (such as, the external controller 130), which can influence the control of the light output of the light unit 1230. While the manager CPU 1220 of the dimming controller 1204 and the sensor unit CPU 1245 of the sensor unit 1202 are shown as separate controllers, it is to be understood that for at least some embodiments the two separate controllers (CPUs) 1220, 1245 can be implemented as single controller or CPU.
For at least some embodiments, the transceiver 1250 provides a wireless link to external devices (for example, the external controller and/or other lighting fixtures).
At least one embodiment further includes affixing the at least one external sensor proximate to the light fixture. For at least one embodiment, the external electrically conductive line provides at least one of sensor and control information from the at least one external sensor to the retrofit controller.
For at least one embodiment, the at least one external sensor includes a second controller, and the at least one external sensor being wirelessly connected to a network. For at least one embodiment, the at least one external sensor provides dimming control information to the controller based on at least one of sensed information and control information received from the network.
For at least one embodiment, the controller receives sensed information from the at least one sensor, and adaptively controls dimming of the LED based on the sensed information.
Although specific embodiments have been described and illustrated, the described embodiments are not to be limited to the specific forms or arrangements of parts so described and illustrated. The embodiments are limited only by the appended claims.
This patent application is a continuation-in-part (CIP) of U.S. patent application Ser. No. 13/930,009, filed Jun. 28, 2013, which is a continuation patent application of U.S. patent application Ser. No. 12/849,081, filed Aug. 3, 2010, and granted as U.S. Pat. No. 8,508,149, all of which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5101141 | Warner et al. | Mar 1992 | A |
5179324 | Audbert | Jan 1993 | A |
5191265 | D'Aleo et al. | Mar 1993 | A |
5283516 | Lohoff | Feb 1994 | A |
5812422 | Lyons | Sep 1998 | A |
6057654 | Cousy et al. | May 2000 | A |
6188181 | Sinha et al. | Feb 2001 | B1 |
6342994 | Cousy et al. | Jan 2002 | B1 |
6548967 | Dowling et al. | Apr 2003 | B1 |
6763013 | Kennedy | Jul 2004 | B2 |
7309985 | Eggers et al. | Dec 2007 | B2 |
7348736 | Piepgras et al. | Mar 2008 | B2 |
7437596 | McFarland | Oct 2008 | B2 |
7382271 | McFarland | Dec 2008 | B2 |
7550931 | Lys et al. | Jun 2009 | B2 |
7566137 | Veskovic | Jul 2009 | B2 |
7623042 | Huizenga | Nov 2009 | B2 |
7792956 | Choong et al. | Sep 2010 | B2 |
7925384 | Huizenga et al. | Apr 2011 | B2 |
8344660 | Mohan et al. | Jan 2013 | B2 |
8457793 | Golding et al. | Jun 2013 | B2 |
8461778 | Mohan et al. | Jun 2013 | B2 |
8493209 | Mohan et al. | Jul 2013 | B2 |
8508149 | Mohan et al. | Aug 2013 | B2 |
8558466 | Basil et al. | Oct 2013 | B2 |
8587219 | Mohan et al. | Nov 2013 | B2 |
8587225 | Ashar et al. | Nov 2013 | B2 |
8787944 | Smith | Jul 2014 | B2 |
9345115 | Mohan | May 2016 | B2 |
9585227 | Mohan et al. | Feb 2017 | B2 |
20040002792 | Hoffknecht | Oct 2004 | A1 |
20050169643 | Franklin et al. | Aug 2005 | A1 |
20050231112 | Woo et al. | Oct 2005 | A1 |
20050278047 | Ahmed | Dec 2005 | A1 |
20060244387 | Park et al. | Nov 2006 | A1 |
20060275040 | Franklin | Dec 2006 | A1 |
20070057807 | Walters et al. | Mar 2007 | A1 |
20070061050 | Hoffknecht | Mar 2007 | A1 |
20070086128 | Lane et al. | Apr 2007 | A1 |
20070215794 | Cernasov et al. | Sep 2007 | A1 |
20080185597 | Veskovic et al. | Aug 2008 | A1 |
20080244104 | Clemente | Oct 2008 | A1 |
20080265796 | Null | Oct 2008 | A1 |
20090026966 | Budde et al. | Jan 2009 | A1 |
20090179596 | Willaert et al. | Jul 2009 | A1 |
20090195161 | Lane et al. | Aug 2009 | A1 |
20090267540 | Chemel et al. | Oct 2009 | A1 |
20090284366 | Haarten et al. | Nov 2009 | A1 |
20100026479 | Tran | Feb 2010 | A1 |
20100034386 | Choong et al. | Feb 2010 | A1 |
20100135186 | Choong et al. | Jun 2010 | A1 |
20100144314 | Sherkin | Jun 2010 | A1 |
20100264846 | Chemal et al. | Oct 2010 | A1 |
20100270933 | Chemal et al. | Oct 2010 | A1 |
20100280677 | Budike, Jr. | Nov 2010 | A1 |
20100295482 | Chemal et al. | Nov 2010 | A1 |
20100301777 | Chemal et al. | Dec 2010 | A1 |
20110031897 | Henig et al. | Feb 2011 | A1 |
20110199010 | Henig et al. | Aug 2011 | A1 |
20120108294 | Kaul | May 2012 | A1 |
20120316414 | Greene | Dec 2012 | A1 |
20130052946 | Chatterjee | Feb 2013 | A1 |
20130141554 | Ganick et al. | Jun 2013 | A1 |
20130278389 | Cristache | Oct 2013 | A1 |
20130285558 | Recker et al. | Oct 2013 | A1 |
20140187200 | Reitter et al. | Jul 2014 | A1 |
20140266585 | Chao | Sep 2014 | A1 |
20150043425 | Aggarwal | Feb 2015 | A1 |
20150103776 | Luther | Apr 2015 | A1 |
20160122157 | Keser | May 2016 | A1 |
20160142877 | Gural et al. | May 2016 | A1 |
Number | Date | Country |
---|---|---|
2320685 | May 2011 | EP |
2320685 | Mar 2014 | EP |
WO 2014-124405 | Aug 2014 | WO |
Entry |
---|
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, dated Jul. 1, 2016, PCT/US2016/021872. |
Number | Date | Country | |
---|---|---|---|
20150189068 A1 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12849081 | Aug 2010 | US |
Child | 13930009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13930009 | Jun 2013 | US |
Child | 14658154 | US |