This patent document pertains generally to mattress systems and more particularly, but not by way of limitation, to an inflatable air mattress system.
Air bed systems, such as the one described in U.S. Pat. No. 5,904,172 which is incorporated herein by reference in its entirety, generally allow a user to select a desired pressure for each air chamber within the mattress. Upon selecting the desired pressure, a signal is sent to a pump and valve assembly in order to inflate or deflate the air bladders as necessary in order to achieve approximately the desired pressure within the air bladders.
In various examples, an air mattress control system allows a user to adjust the firmness or position of an air mattress bed. The mattress may have more than one zone thereby allowing a left and right side of the mattress to be adjusted to different firmness levels. Additionally, the bed may be adjustable to different positions. For example, the head section of the bed may be raised up while the foot section of the bed stays in place. In various examples, two separate remote controls are used to adjust the position and firmness, respectively.
A common problem experienced by many people is snoring. Snoring can not only result in poor sleep quality and potential health issues, but it can also disturb another person who is sleeping in the same room, such as a spouse sleeping in the same bed. Some people deal with the problem by waking the snorer up in order to stop the snoring. However, the snorer often begins snoring again after going back to sleep. Moreover, waking the snorer also interrupts the snorer's sleep.
Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:
As illustrated in
The pump 20 and the remote control 22 can be in two-way communication with the control box 24. The pump 20 can include a motor 42, a pump manifold 43, a relief valve 44, a first control valve 45A, a second control valve 45B, and a pressure transducer 46, and can be fluidly connected with the first air chamber 14A and the second air chamber 14B via a first tube 48A and a second tube 48B, respectively. The first and second control valves 45A and 45B can be controlled by the switching means 38, and can be operable to regulate the flow of fluid between the pump 20 and the first and second air chambers 14A and 14B, respectively.
In an example, the pump 20 and the control box 24 can be provided and packaged as a single unit. Alternatively, the pump 20 and the control box 24 can be provided as physically separate units.
In operation, the power supply 34 can receive power, such as 110 VAC power, from an external source and can convert the power to various forms required by certain components of the air bed system 10. The processor 36 can be used to control various logic sequences associated with operation of the air bed system 10, as will be discussed in further detail below.
The example of the air bed system 10 shown in
In the event that the processor 36 sends a decrease pressure command to one of the air chambers 14A or 14B, the switching means 38 can be used to convert the low voltage command signals sent by the processor 36 to higher operating voltages sufficient to operate the relief valve 44 of the pump 20 and open the control valves 45A or 45B. Opening the relief valve 44 can allow air to escape from the air chamber 14A or 14B through the respective air tube 48A or 48B. During deflation, the pressure transducer 46 can send pressure readings to the processor 36 via the A/D converter 40. The A/D converter 40 can receive analog information from the pressure transducer 46 and can convert the analog information to digital information useable by the processor 36. The processor 36 may send the digital signal to the remote control 22 to update the display 26 on the remote control in order to convey the pressure information to the user.
In the event that the processor 36 sends an increase pressure command, the pump motor 42 can be energized, sending air to the designated air chamber through the air tube 48A or 48B via electronically operating the corresponding valve 45A or 45B. While air is being delivered to the designated air chamber in order to increase the firmness of the chamber, the pressure transducer 46 can sense pressure within the pump manifold 43. Again, the pressure transducer 46 can send pressure readings to the processor 36 via the A/D converter 40. The processor 36 can use the information received from the A/D converter 40 to determine the difference between the actual pressure in the air chamber 14A or 14B and the desired pressure. The processor 36 can send the digital signal to the remote control 22 to update the display 26 on the remote control in order to convey the pressure information to the user.
Generally speaking, during an inflation or deflation process, the pressure sensed within the pump manifold 43 provides an approximation of the pressure within the air chamber. An example method of obtaining a pump manifold pressure reading that is substantially equivalent to the actual pressure within an air chamber is to turn off the pump 20, allow the pressure within the air chamber 14A or 14B and the pump manifold 43 to equalize, and then sense the pressure within the pump manifold 43 with the pressure transducer 46. Thus, providing a sufficient amount of time to allow the pressures within the pump manifold 43 and the chamber 14A or 14B to equalize may result in pressure readings that are accurate approximations of the actual pressure within the air chamber 14A or 14B. In various examples, the pressure of 48A/B is continuously monitored using multiple pressure sensors.
In an example, another method of obtaining a pump manifold pressure reading that is substantially equivalent to the actual pressure within an air chamber is through the use of a pressure adjustment algorithm. In general, the method can function by approximating the air chamber pressure based upon a mathematical relationship between the air chamber pressure and the pressure measured within the pump manifold 43 (during both an inflation cycle and a deflation cycle), thereby eliminating the need to turn off the pump 20 in order to obtain a substantially accurate approximation of the air chamber pressure. As a result, a desired pressure setpoint within the air chamber 14A or 14B can be achieved without the need for turning the pump 20 off to allow the pressures to equalize. The latter method of approximating an air chamber pressure using mathematical relationships between the air chamber pressure and the pump manifold pressure is described in detail in U.S. application Ser. No. 12/936,084, the entirety of which is incorporated herein by reference.
As illustrated in
In yet another example, central controller 302 listens to communications (e.g., control signals) between components even if the communication is not being relayed through central controller 302. For example, consider a user sending a command using remote 312 to temperature controller 308. Central controller 302 may listen for the command and check to determine if instructions are stored at central controller 302 to override the command (e.g., it conflicts with a previous setting). Central controller 302 may also log the command for future use (e.g., determining a pattern of user preferences for the components).
In other examples, different topologies may be used. For example, the components and the central controller 302 may be configured as a mesh network in which each component may communicate with one or all of the other components directly, bypassing the central controller 302. In various examples, a combination of topologies may be used. For example, the remote controller 312 may communicate directly to the temperature controller 308 but also relay the communication to the central controller 302.
In various examples, the controllers and devices illustrated in
In various examples, the network interface of the components may be configured to transmit and receive communications in a variety of wired and wireless protocols. For example, the network interface may be configured to use the 802.11 standards (e.g., 802.11a/b/c/g/n/ac), PAN network standards such as 802.15.4 or Bluetooth, infrared, cellular standards (e.g., 3G/4G etc.), Ethernet, and USB for receiving and transmitting data. The previous list is not intended to be exhaustive and other protocols may be used. Not all components of
Moreover, in various examples, the processor, storage device, and network interface of a component may be located in different locations than various elements used to effect a command. For example, as in
In various examples, the firmness controller 304 is configured to regulate pressure in an air mattress. For example, the firmness controller 304 may include a pump such as described with reference to
As illustrated in
In various examples, the articulation controller 306 is configured to adjust the position of a bed mattress (e.g., bed 301) by adjusting a foundation 307 that supports the bed mattress. In an example, the bed 301 can include a single foundation 307 configured to adjust the position of a bed having a single mattress. In another example, the bed 301 can include two side-by-side foundations 307 configured to operate in tandem to adjust the position of a bed having a single mattress. In yet another example, the bed 301 can include two side-by-side mattresses supported by two side-by-side foundations 307, wherein the foundations 307 are operable independently such that separate positions may be set for the two different mattresses of the bed 301. The foundation 307 may include more than one zone, e.g., a head portion 318 and a foot portion 320, which may be independently adjusted. The articulation controller 306 may also be configured to provide different levels of massage to a person on the bed.
In various examples, the temperature controller 308 is configured to increase, decrease, or maintain the temperature of a user. For example, a pad may be placed on top of or be part of the air mattress. Air may be pushed through the pad and vented to cool off a user of the bed. Conversely, the pad may include a heating element that may be used to keep the user warm. In various examples, the pad includes the temperature sensor 309 and the temperature controller 308 receives temperature readings from the temperature sensor 309. In other examples, the temperature sensor 309 can be separate from the pad, e.g., part of the air mattress or foundation. Alternatively or in addition, a blanket can be provided having similar functionality to the pad.
In various examples, additional controllers may communicate with the central controller 302. These controllers may include, but are not limited to, illumination controllers for controlling the power status (e.g., on or off) or intensity of light elements 311 and 322A-F placed on and around the bed, audio/visual controllers for controlling the power status or volume of one or more audio/visual components 313 located near the bed, thermostat controllers for controlling a temperature setting of a thermostat device 315, and outlet controllers for controlling power to one or more power outlets 336. In an example, the light elements 311 and 322A-F can be network controlled lights.
In various examples, the external network device 310, the remote controllers 312, 314 and the voice controller 316 may be used to input commands (e.g., from a user or remote system) to control one or more components of the system architecture 300. The commands may be transmitted from one of the controllers 312, 314, or 316 and received in the central controller 302. The central controller 302 may process the command to determine the appropriate component to route the received command. For example, each command sent via one of controllers 312, 314, or 316 may include a header or other metadata that indicates which component the command is for. The central controller 302 may then transmit the command via the central controller 302's network interface to the appropriate component.
For example, a user may input a desired temperature for the user's bed into the remote controller 312. The desired temperature may be encapsulated in a command data structure that includes the temperature as well as identifies the temperature controller 308 as the desired component to be controlled. The command data structure may then be transmitted via Bluetooth to the central controller 302. In various examples, the command data structure is encrypted before being transmitted. The central controller 302 may parse the command data structure and relay the command to the temperature controller 308 using a PAN. The temperature controller 308 may then configure its elements to increase or decrease the temperature of the pad depending on the temperature originally input into the remote controller 312.
In one example implementation, the central controller 302 can detect user presence using temperature changes detected in the mattress, e.g., using one or more temperature sensors positioned in or on the mattress. The temperature sensors and the central controller 302 can detect a rise in temperature, e.g., over a specified period of time, and determine that a user is present in the bed. For example, if the central controller 302 detects a rise in temperature and then determines that the detected rise in temperature was not caused by the system's temperature controller 308, the central controller 302 can determine that the user is present.
In various examples, data may be transmitted from a component back to one or more of the remote controllers. For example, the current temperature as determined by a sensor element of the temperature controller 308, e.g., the temperature sensor 309, the pressure of the bed, the current position of the foundation or other information may be transmitted to the central controller 302. The central controller 302 may then transmit the received information and transmit it to the remote controller 312 where it may be displayed to the user.
In various examples, multiple types of devices may be used to input commands to control the components of the architecture 300. For example, the remote controller 312 may be a mobile device such as a smart phone or tablet computer running an application. Other examples of the remote controller 312 may include a dedicated device for interacting with the components described herein. In various examples, the remote controllers 312/314 include a display device for displaying an interface to a user. The remote controller 312/314 may also include one or more input devices. Input devices may include, but are not limited to, keypads, touchscreen, gesture, motion and voice controls.
The remote controller 314 may be a single component remote configured to interact with one component of the mattress architecture. For example, the remote controller 314 may be configured to accept inputs to increase or decrease the air mattress pressure. The voice controller 316 may be configured to accept voice commands to control one or more components. In various examples, more than one of the remote controllers 312/314 and the voice controller 316 may be used.
With respect to the remote controller 312, the application may be configured to pair with one or more central controllers. For each central controller, data may be transmitted to the mobile device that includes a list of components linked with the central controller. For example, consider that the remote controller 312 is a mobile phone and that the application has been authenticated and paired with the central controller 302. The remote controller 312 may transmit a discovery request to the central controller 302 to inquire about other components and available services. In response, the central controller 302 may transmit a list of services that includes available functions for adjusting the firmness of the bed, position of the bed, and temperature of the bed. In various embodiments, the application may then display functions for increasing/decreasing pressure of the air mattress, adjusting positions of the bed, and adjusting temperature. If components are added/removed to the architecture under control of the central controller 302, an updated list may be transmitted to the remote controller 312 and the interface of the application may be adjusted accordingly.
In various examples, the central controller 302 is configured as a distributor of software updates to components in the architecture 300. For example, a firmware update for the temperature controller 308 may become available. The update may be loaded into a storage device of the central controller 302 (e.g., via a USB interface or using wireless techniques). In wireless applications, the central controller 302 may, for example, receive updates from the cloud either from wifi or from a mobile connection over Bluetooth. The central controller 302 may then transmit the update to the temperature controller 308 with instructions to update. The temperature controller 308 may attempt to install the update. A status message may be transmitted from the temperature controller 308 to the central controller 302 indicating the success or failure of the update.
In various examples, the central controller 302 is configured to analyze data collected by a pressure transducer (e.g., the transducer 46 with respect to
In various examples, the external network device 310 includes a network interface to interact with an external server for processing and storage of data related to components in the architecture 300. For example, the determined sleep data as described above may be transmitted via a network (e.g., the Internet) from the central controller 302 to the external network device 310 for storage. In an example, the pressure transducer data may be transmitted to the external server for additional analysis. The external network device 310 may also analyze and filter the data before transmitting it to the external server.
In an example, diagnostic data of the components may also be routed to the external network device 310 for storage and diagnosis on the external server. For example, if the temperature controller 308 detects an abnormal temperature reading (e.g., a drop in temperature over one minute that exceeds a set threshold) diagnostic data (sensor readings, current settings, etc.) may be wireless transmitted from the temperature controller 308 to the central controller 302. The central controller 302 may then transmit this data via USB to the external network device 310. The external network device 310 may wirelessly transmit the information to an WLAN access point where it is routed to the external server for analysis.
In one example, the bed system architecture 300 can include one or more bed lights 322A-322F (referred to collectively in this disclosure as “bed lights 322”) to illuminate a portion of a room, e.g., when a user gets out of the bed 301. The lights 322 can be attached around the foundation 307, e.g., affixed to the foundation around its perimeter. In
Example Machine Architecture and Machine-Readable Medium
The example computer system 400 includes a processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), ASIC or a combination), a main memory 404 and a static memory 406, which communicate with each other via a bus 408. The computer system 400 may further include a video display unit 410 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 400 also includes an alphanumeric input device 412 (e.g., a keyboard and/or touchscreen), a user interface (UI) navigation device 414 (e.g., a mouse), a disk drive unit 416, a signal generation device 418 (e.g., a speaker) and a network interface device 420.
Machine-Readable Medium
The disk drive unit 416 includes a machine-readable medium 422 on which is stored one or more sets of instructions and data structures (e.g., software) 424 embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 424 may also reside, completely or at least partially, within the main memory 404 and/or within the processor 402 during execution thereof by the computer system 400, the main memory 404 and the processor 402 also constituting machine-readable media.
While the machine-readable medium 422 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions or data structures. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including by way of example semiconductor memory devices, e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
Transmission Medium
The instructions 424 may further be transmitted or received over a communications network 426 using a transmission medium. The instructions 424 may be transmitted using the network interface device 420 and any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
Snoring Detection Techniques
In addition to the techniques described above, this disclosure is directed to techniques for detection of various aspects of a user of the system architecture 300. For example, and as described in further detail below, user snoring can be detected using various techniques described in this disclosure
In a first technique for snoring detection, the system architecture 300 can detect biometric parameters of a user such as motion, respiration, and heartbeat. These biometric parameters can be detected both while the user is awake and while the user is sleeping. In various examples, the biometric parameters can be used to determine a sleep state of the user and whether the user is snoring. Techniques for monitoring a user's sleep using heart rate information, respiration rate information, and other user information are disclosed in U.S. Patent Application Publication No. 20100170043 to Steven J. Young et al., titled “APPARATUS FOR MONITORING VITAL SIGNS,” the entire content of which is incorporated herein by reference. After snoring is detected, the system architecture 300 and, in particular, the central controller 302, can make one or more adjustments to the sleep environment or the bed 301 as will be discussed in further detail below. In an example, the user can instruct the system architecture 300 to monitor for snoring after the user falls asleep and to initiate specific changes to the sleep environment or the bed 301 upon detection of snoring. In another example, the system architecture 300 can automatically, e.g., without user instruction, monitor for snoring and determine what changes should be made, if any, to the sleep environment or the bed 301. In yet another example, when two users are lying on the bed 301 side-by-side, the system architecture 300 can determine which of the users is snoring and initiate the changes to that user's side of the bed.
In accordance with this disclosure, the central controller 302, or another processing means associated with the bed 301, can detect user sleeping motion, respiration, and heartbeat via pressure changes. For example, the pressure transducer 46 (of
In one example implementation, the central controller 302 can execute instructions that cause the pressure transducer 46 to measure air pressure values at a predefined sample rate. The central controller 302 can store the pressure signals in a memory device. Processing of the pressure signals can be performed by the central controller 302, or at a location remote from the bed 301, such as on a processor of a smartphone, a mobile device, or a cloud-based computing system.
As indicated above, the central controller 302 can determine a user's sleep state, e.g., rapid eye movement (“REM”) or non-rapid eye movement (“NREM”), by using one or more of the biometric parameters. In an example, the central controller 302 can execute instructions to monitor the snoring state of the user only after the user has reached a particular sleep state.
As previously mentioned, in some example implementations, the techniques for detecting the user's sleep state can be combined with the techniques for detecting snoring using biometric parameters. For example, prior to monitoring pressure changes using the pressure sensing means to determine whether the user is snoring, the central controller 302 can determine whether the user has reached a predetermined sleep state. Thus, determining that the user has reached the predetermined state of sleep can be a prerequisite to instructing the central controller 302 to perform the method 500 described above. Alternatively, the central controller 302 can execute instructions to monitor sleep state and pressure changes simultaneously or substantially simultaneously, and the combined results can be used to determine whether the user is snoring.
In another technique for snoring detection, the system architecture 300 can be configured to detect snoring by monitoring sound waves through a microphone, which can be included in the voice controller 316 as discussed above. In various examples, the system architecture 300 can also be configured to detect snoring by monitoring a combination of both sound waves and biometric parameters. In general, snoring sounds are formed when tissues in the user's throat vibrate as air if flowing through the throat during sleep. In one example implementation, the central controller 302 can execute instructions that cause the voice controller 316 to monitor sound waves generated by the user, and to store the corresponding sound wave signals in a memory device. Processing of the sound wave signals can be performed by the central controller 302, or at a location remote from the bed 301. A snoring state can be determined by monitoring parameters such as the audible level of the sound waves, the frequency of the sound waves, sound wave patterns, and the like. For example, sound waves generated during normal conversation levels of a user may be 40 decibels or less, while sound waves generated by the user's snoring may be in the range of 60-90 decibels or more. By analyzing the sound waves generated by the user, the presence, intensity, duration, and patterns of snoring can be determined.
Once again, in some example implementations, the techniques for detecting the user's sleep state can be combined with the techniques for detecting snoring using sound waves. For example, prior to monitoring sound waves using the voice controller 316 to determine whether the user is snoring, the central controller 302 can determine whether the user has reached a predetermined sleep state. Thus, determining that the user has reached the predetermined state of sleep can be a prerequisite to instructing the central controller 302 to perform the method 600 described above. Alternatively, the central controller 302 can execute instructions to monitor sleep state and sound waves simultaneously or substantially simultaneously, and the combined results can be used to determine whether the user is snoring.
Snoring Detection Response Techniques
In an example, the central controller 302 can execute instructions that cause the firmness controller 304 to adjust pressure in the air mattress of the bed 301 when snoring is detected (704). For example, the central controller 302 can provide commands to the firmness controller 304 to increase or decrease pressure in the air mattress, via the pump 305, to a level that can help relieve the snoring. If the system architecture 300 detects that snoring continues even after the pressure in the air mattress has been modified, the central controller 302 can provide additional commands to the firmness controller 304 to further adjust the pressure in the air mattress. Thus, the process of adjusting pressure in the air mattress of the bed 301 to relieve snoring can be iterative. Additionally, if the air mattress includes multiple bladders corresponding to separate zones as discussed above, the central controller 302 can execute instructions that cause the firmness controller 304 to adjust pressure in one or more selected zones, such as the zone corresponding to the head of the user.
In another example, the central controller 302 can execute instructions that cause an adjustment to be made to the foundation 307 when snoring is detected (704). As discussed above, the foundation 307 may include more than one zone, such as a head portion 318 and a foot portion 320, which may be independently adjusted. The user may fall asleep with the foundation 307 in a “flat” position, or with the head portion 318 and/or the foot portion 320 in a raised, articulated position. In various examples, the bed 301 can include a “snore” position defined by a predetermined articulation of the foundation 307. It has been found that, in some cases, snoring can be reduced or prevented by elevating the head of the snoring user by a small amount, which can reduce vibration of the soft tissue in the user's throat. The slight elevation of the snoring user's head can also induce the snorer to change his or her sleeping position, which can cause the snoring to stop. In an example, the snore position can include the head portion 318 being raised at a preset angle θ relative to horizontal. In an example, the angle θ can be from about 5° to about 15° from horizontal, such as about 7°. However, any angle θ that can help reduce or eliminate vibration of soft tissue within the throat of the user can be used. In various examples, the snore position can be customizable to a particular user based on the amount of articulation that is found to help relieve snoring in that user. For example, a large, heavy-set user may require a larger inclination angle than a thin, petite user. Thus, pre-programmed snore positions can be updated in accordance with user preferences and body types.
In another example, the central controller 302 can execute instructions that cause the temperature controller 308 to adjust a temperature of the bed 301 when snoring is detected (704). As discussed above, in various examples, the temperature of the bed 301 (and thus, the user) can be regulated using a pad placed on top of the mattress, a blanket placed on top of the user, or heating/cooling elements incorporated into the mattress, such as a heating/cooling pad integrated into the mattress. Certain users may tend to snore more or less depending on their body temperature and the temperature of the surroundings, such as the bed 301. Thus, heating up or cooling down the bed 301 can help some users find relief from snoring. For example, the temperature of the sleeping surface of the bed 301 could be lowered from 20° Celsius to 18° Celsius when snoring is detected. However, any temperature change, whether positive or negative, can be utilized. Similarly, the central controller 302 can execute instructions that cause the thermostat device 315 to adjust the temperature of the surrounding environment, such as the bedroom where the bed 301 is located, when snoring is detected (704). In view of the foregoing, user temperature can be regulated through use of the temperature controller 308, the thermostat device 315, or both.
The level of light and sound in a bedroom environment can affect the depth and quality of sleep for a user. Thus, when the goal is to alleviate snoring and provide a more restful night of sleep, light and sound can also be controlled to provide an ideal set of sleep conditions. In another example, the central controller 302 can execute instructions for controlling the power status (e.g., on or off) or intensity of light elements 311 or 322A-F placed on and around the bed, and/or for controlling the power status or volume of one or more audio/visual components 313 located near the bed, when snoring is detected (704).
Sleep Profile Reporting
In accordance with the present disclosure, the system architecture 300 can also enable feedback related to snoring to be provided to the user. In various examples, the snoring information processed and analyzed by the central controller 302 can be provided to the user in various formats and to various devices.
In an example, the central controller 302 can execute instructions that cause a sleep profile report to be generated and transmitted to one or more of the remote controller 312, the remote controller 314, or an external computing device such as, for example, a personal computer (PC), a tablet PC, a Personal Digital Assistant (PDA), or the like. The external computing device can be operably coupled to the bed 301 via any suitable network connection, including those previously described.
Sleep profile reports 800 can be stored in memory associated with the system architecture 300 for recall at a later time. In an example, the central controller 302 can execute instructions that cause the sleep profile report 800 to display the amount of sleep that a user has averaged over a specified number of days, and the amount of snoring that the user has averaged during that time. For example, the sleep profile report 800 shows average sleep and snoring over the previous 30 days. However, a number of days greater than or less than 30 can also be used.
Although various embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. As is common, the terms “a” and “an” may refer to one or more unless otherwise indicated.
This Application claims the benefit of priority to U.S. Provisional Application No. 61/782,394, filed on Mar. 14, 2013, the disclosure of which is incorporated herein in its entirety by reference. The subject matter described in this application is related to subject matter disclosed in the following applications: U.S. Application Ser. No. 61/781,266, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS ALARM AND MONITORING SYSTEM”; U.S. Application Ser. No. 61/781,503, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS SYSTEM ARCHITECTURE”; U.S. Application Ser. No. 61/781,541, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS AUTOFILL AND OFF BED PRESSURE ADJUSTMENT”; U.S. Application Ser. No. 61/781,571, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS SLEEP ENVIRONMENT ADJUSTMENT AND SUGGESTIONS”; U.S. Application Ser. No. 61/781,296, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS WITH LIGHT AND VOICE CONTROLS”; U.S. Application Ser. No. 61/781,311, filed on Mar. 14, 2013, entitled “INFLATABLE AIR MATTRESS SYSTEM WITH DETECTION TECHNIQUES.” The contents of each of the above-referenced U.S. patent applications are herein incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3727606 | Sielaff | Apr 1973 | A |
3998209 | Macvaugh | Dec 1976 | A |
4146885 | Lawson, Jr. | Mar 1979 | A |
4299233 | Lemelson | Nov 1981 | A |
4657026 | Tagg | Apr 1987 | A |
4662012 | Tarbet | May 1987 | A |
4766628 | Walker | Aug 1988 | A |
4788729 | Walker | Dec 1988 | A |
4829616 | Walker | May 1989 | A |
4890344 | Walker | Jan 1990 | A |
4897890 | Walker | Feb 1990 | A |
4908895 | Walker | Mar 1990 | A |
4982466 | Higgins et al. | Jan 1991 | A |
4991244 | Walker | Feb 1991 | A |
5020176 | Dotson | Jun 1991 | A |
5062169 | Kennedy et al. | Nov 1991 | A |
5144706 | Walker et al. | Sep 1992 | A |
5170522 | Walker | Dec 1992 | A |
5197490 | Steiner et al. | Mar 1993 | A |
5459452 | DePonte | Oct 1995 | A |
5487196 | Wilkinson et al. | Jan 1996 | A |
5509154 | Shafer et al. | Apr 1996 | A |
5515865 | Scanlon | May 1996 | A |
5551418 | Estes | Sep 1996 | A |
5564140 | Shoenhair et al. | Oct 1996 | A |
5642546 | Shoenhair | Jul 1997 | A |
5652484 | Shafer et al. | Jul 1997 | A |
5675855 | Culp | Oct 1997 | A |
5684460 | Scanlon | Nov 1997 | A |
5699038 | Ulrich et al. | Dec 1997 | A |
5724990 | Ogino | Mar 1998 | A |
5765246 | Shoenhair | Jun 1998 | A |
5771511 | Kummer et al. | Jun 1998 | A |
5796340 | Miller | Aug 1998 | A |
5844488 | Musick | Dec 1998 | A |
5848450 | Oexman et al. | Dec 1998 | A |
5903941 | Shafer et al. | May 1999 | A |
5904172 | Gifft et al. | May 1999 | A |
5948303 | Larson | Sep 1999 | A |
5964720 | Pelz | Oct 1999 | A |
5989193 | Sullivan | Nov 1999 | A |
6024699 | Surwit et al. | Feb 2000 | A |
6037723 | Shafer et al. | Mar 2000 | A |
6058537 | Larson | May 2000 | A |
6062216 | Corn | May 2000 | A |
6079065 | Luff et al. | Jun 2000 | A |
6094762 | Viard et al. | Aug 2000 | A |
6108844 | Kraft et al. | Aug 2000 | A |
6120441 | Griebel | Sep 2000 | A |
6146332 | Pinsonneault et al. | Nov 2000 | A |
6147592 | Ulrich et al. | Nov 2000 | A |
6161231 | Kraft et al. | Dec 2000 | A |
6202239 | Ward et al. | Mar 2001 | B1 |
6208250 | Dixon et al. | Mar 2001 | B1 |
6234642 | Bokaemper | May 2001 | B1 |
6272378 | Baumgart-Schmitt | Aug 2001 | B1 |
6386201 | Fard | May 2002 | B1 |
6396224 | Luff et al. | May 2002 | B1 |
6397419 | Mechache | Jun 2002 | B1 |
6438776 | Ferrand et al. | Aug 2002 | B2 |
6450957 | Yoshimi et al. | Sep 2002 | B1 |
6468234 | Ford et al. | Oct 2002 | B1 |
6483264 | Shafer et al. | Nov 2002 | B1 |
6485441 | Woodward | Nov 2002 | B2 |
6546580 | Shimada | Apr 2003 | B2 |
6547743 | Brydon | Apr 2003 | B2 |
6561047 | Gladney | May 2003 | B1 |
6566833 | Bartlett | May 2003 | B2 |
6643875 | Boso et al. | Nov 2003 | B2 |
6686711 | Rose et al. | Feb 2004 | B2 |
6698432 | Ek | Mar 2004 | B2 |
6708357 | Gaboury et al. | Mar 2004 | B2 |
6719708 | Jansen | Apr 2004 | B1 |
6763541 | Mahoney et al. | Jul 2004 | B2 |
6778090 | Newham | Aug 2004 | B2 |
6804848 | Rose | Oct 2004 | B1 |
6832397 | Gaboury et al. | Dec 2004 | B2 |
6840117 | Hubbard, Jr. | Jan 2005 | B2 |
6840907 | Brydon | Jan 2005 | B1 |
6847301 | Olson | Jan 2005 | B1 |
6878121 | Krausman | Apr 2005 | B2 |
6883191 | Gaboury et al. | Apr 2005 | B2 |
6993380 | Modarres | Jan 2006 | B1 |
7041049 | Raniere | May 2006 | B1 |
7077810 | Lange et al. | Jul 2006 | B2 |
7150718 | Okada | Dec 2006 | B2 |
7237287 | Weismiller et al. | Jul 2007 | B2 |
7253366 | Bhai | Aug 2007 | B2 |
7304580 | Sullivan et al. | Dec 2007 | B2 |
7314451 | Halperin et al. | Jan 2008 | B2 |
7321811 | Rawls-Meehan | Jan 2008 | B1 |
7330127 | Price et al. | Feb 2008 | B2 |
7389554 | Rose | Jun 2008 | B1 |
7396331 | Mack | Jul 2008 | B2 |
7429247 | Okada et al. | Sep 2008 | B2 |
7437787 | Bhai | Oct 2008 | B2 |
7465280 | Rawls-Meehan | Dec 2008 | B2 |
7480951 | Weismiller | Jan 2009 | B2 |
7506390 | Dixon et al. | Mar 2009 | B2 |
7520006 | Menkedick et al. | Apr 2009 | B2 |
7524279 | Auphan | Apr 2009 | B2 |
7532934 | Lee et al. | May 2009 | B2 |
7538659 | Ulrich | May 2009 | B2 |
7568246 | Weismiller et al. | Aug 2009 | B2 |
7631377 | Sanford | Dec 2009 | B1 |
7637859 | Lindback et al. | Dec 2009 | B2 |
7652581 | Gentry et al. | Jan 2010 | B2 |
7666151 | Sullivan et al. | Feb 2010 | B2 |
7669263 | Menkedick et al. | Mar 2010 | B2 |
7676872 | Block et al. | Mar 2010 | B2 |
7685663 | Rawls-Meehan | Mar 2010 | B2 |
7698761 | Neuenswander et al. | Apr 2010 | B2 |
7699784 | Wan et al. | Apr 2010 | B2 |
7717848 | Heruth et al. | May 2010 | B2 |
7749154 | Cornel | Jul 2010 | B2 |
7784128 | Kramer | Aug 2010 | B2 |
7785257 | Mack et al. | Aug 2010 | B2 |
7805785 | Rawls-Meehan | Oct 2010 | B2 |
7841031 | Rawls-Meehan | Nov 2010 | B2 |
7849545 | Flocard et al. | Dec 2010 | B2 |
7854031 | Rawls-Meehan | Dec 2010 | B2 |
7860723 | Rawls-Meehan | Dec 2010 | B2 |
7862523 | Ruotoistenmaki | Jan 2011 | B2 |
7865988 | Koughan et al. | Jan 2011 | B2 |
7868757 | Radivojevic et al. | Jan 2011 | B2 |
7869903 | Turner et al. | Jan 2011 | B2 |
7930783 | Rawls-Meehan | Apr 2011 | B2 |
7933669 | Rawls-Meehan | Apr 2011 | B2 |
7953613 | Gizewski | May 2011 | B2 |
7954189 | Rawls-Meehan | Jun 2011 | B2 |
7956755 | Lee et al. | Jun 2011 | B2 |
7967739 | Auphan | Jun 2011 | B2 |
7979169 | Rawls-Meehan | Jul 2011 | B2 |
8019486 | Rawls-Meehan | Sep 2011 | B2 |
8020230 | Rawls-Meehan | Sep 2011 | B2 |
8028363 | Rawls-Meehan | Oct 2011 | B2 |
8032263 | Rawls-Meehan | Oct 2011 | B2 |
8032960 | Rawls-Meehan | Oct 2011 | B2 |
8046114 | Rawls-Meehan | Oct 2011 | B2 |
8046115 | Rawls-Meehan | Oct 2011 | B2 |
8046116 | Rawls-Meehan | Oct 2011 | B2 |
8046117 | Rawls-Meehan | Oct 2011 | B2 |
8050805 | Rawls-Meehan | Nov 2011 | B2 |
8052612 | Tang | Nov 2011 | B2 |
8065764 | Kramer | Nov 2011 | B2 |
8069852 | Burton | Dec 2011 | B2 |
8073535 | Jung et al. | Dec 2011 | B2 |
8078269 | Suzuki et al. | Dec 2011 | B2 |
8078336 | Rawls-Meehan | Dec 2011 | B2 |
8078337 | Rawls-Meehan | Dec 2011 | B2 |
8083682 | Dalal et al. | Dec 2011 | B2 |
8090478 | Skinner et al. | Jan 2012 | B2 |
8092399 | Sasaki | Jan 2012 | B2 |
8094013 | Lee | Jan 2012 | B1 |
8096960 | Loree et al. | Jan 2012 | B2 |
8144001 | D'Souza | Mar 2012 | B1 |
8146191 | Bobey et al. | Apr 2012 | B2 |
8150562 | Rawls-Meehan | Apr 2012 | B2 |
8166589 | Hijlkema | May 2012 | B2 |
8181290 | Brykalski et al. | May 2012 | B2 |
8181296 | Rawls-Meehan | May 2012 | B2 |
8266742 | Andrienko | Sep 2012 | B2 |
8272892 | McNeely et al. | Sep 2012 | B2 |
8276585 | Buckley | Oct 2012 | B2 |
8279057 | Hirose | Oct 2012 | B2 |
8280748 | Allen | Oct 2012 | B2 |
8281433 | Riley et al. | Oct 2012 | B2 |
8282452 | Grigsby et al. | Oct 2012 | B2 |
8284047 | Collins, Jr. | Oct 2012 | B2 |
8287452 | Young et al. | Oct 2012 | B2 |
8336369 | Mahoney | Dec 2012 | B2 |
8341784 | Scott | Jan 2013 | B2 |
8341786 | Oexman et al. | Jan 2013 | B2 |
8348840 | Heit et al. | Jan 2013 | B2 |
8350709 | Receveur | Jan 2013 | B2 |
8375488 | Rawls-Meehan | Feb 2013 | B2 |
8376954 | Lange et al. | Feb 2013 | B2 |
8382484 | Wetmore et al. | Feb 2013 | B2 |
8386008 | Yuen et al. | Feb 2013 | B2 |
8398538 | Dothie | Mar 2013 | B2 |
8403865 | Halperin et al. | Mar 2013 | B2 |
8413274 | Weismiller et al. | Apr 2013 | B2 |
8421606 | Collins, Jr. et al. | Apr 2013 | B2 |
8428696 | Foo | Apr 2013 | B2 |
8444558 | Young et al. | May 2013 | B2 |
8491492 | Shinar et al. | Jul 2013 | B2 |
8517953 | Lange et al. | Aug 2013 | B2 |
8620615 | Oexman | Dec 2013 | B2 |
8672853 | Young | Mar 2014 | B2 |
8679034 | Halperin et al. | Mar 2014 | B2 |
8769747 | Mahoney et al. | Jul 2014 | B2 |
8840564 | Pinhas et al. | Sep 2014 | B2 |
8909357 | Rawls-Meehan | Dec 2014 | B2 |
8931329 | Mahoney et al. | Jan 2015 | B2 |
8966689 | McGuire et al. | Mar 2015 | B2 |
8973183 | Palashewski et al. | Mar 2015 | B1 |
8984687 | Stusynski et al. | Mar 2015 | B2 |
9370457 | Nunn | Jun 2016 | B2 |
20020124311 | Peftoulidis | Sep 2002 | A1 |
20020184711 | Mahoney et al. | Dec 2002 | A1 |
20020189621 | Ek | Dec 2002 | A1 |
20030045806 | Brydon | Mar 2003 | A1 |
20030128125 | Burbank et al. | Jun 2003 | A1 |
20030163874 | Boso et al. | Sep 2003 | A1 |
20030166995 | Jansen | Sep 2003 | A1 |
20030182728 | Chapman et al. | Oct 2003 | A1 |
20030221261 | Tarbet et al. | Dec 2003 | A1 |
20040049132 | Barron et al. | Mar 2004 | A1 |
20050022606 | Partin et al. | Feb 2005 | A1 |
20050038326 | Mathur | Feb 2005 | A1 |
20050115561 | Stahmann et al. | Jun 2005 | A1 |
20050190065 | Ronholm | Sep 2005 | A1 |
20050190068 | Gentry et al. | Sep 2005 | A1 |
20050283039 | Cornel | Dec 2005 | A1 |
20060020178 | Sotos et al. | Jan 2006 | A1 |
20060031996 | Rawls-Meehan | Feb 2006 | A1 |
20060047217 | Mirtalebi | Mar 2006 | A1 |
20060152378 | Lokhorst | Jul 2006 | A1 |
20060162074 | Bader | Jul 2006 | A1 |
20070049842 | Hill et al. | Mar 2007 | A1 |
20070118054 | Pinhas et al. | May 2007 | A1 |
20070149883 | Yesha | Jun 2007 | A1 |
20070179334 | Groves et al. | Aug 2007 | A1 |
20070180047 | Dong et al. | Aug 2007 | A1 |
20070180618 | Weismiller et al. | Aug 2007 | A1 |
20070276202 | Raisanen et al. | Nov 2007 | A1 |
20080052837 | Blumberg | Mar 2008 | A1 |
20080071200 | Rawls-Meehan | Mar 2008 | A1 |
20080077020 | Young et al. | Mar 2008 | A1 |
20080092291 | Rawls-Meehan | Apr 2008 | A1 |
20080092292 | Rawls-Meehan | Apr 2008 | A1 |
20080092293 | Rawls-Meehan | Apr 2008 | A1 |
20080092294 | Rawls-Meehan | Apr 2008 | A1 |
20080093784 | Rawls-Meehan | Apr 2008 | A1 |
20080097774 | Rawls-Meehan | Apr 2008 | A1 |
20080097778 | Rawls-Meehan | Apr 2008 | A1 |
20080097779 | Rawls-Meehan | Apr 2008 | A1 |
20080104750 | Rawls-Meehan | May 2008 | A1 |
20080104754 | Rawls-Meehan | May 2008 | A1 |
20080104755 | Rawls-Meehan | May 2008 | A1 |
20080104756 | Rawls-Meehan | May 2008 | A1 |
20080104757 | Rawls-Meehan | May 2008 | A1 |
20080104758 | Rawls-Meehan | May 2008 | A1 |
20080104759 | Rawls-Meehan | May 2008 | A1 |
20080104760 | Rawls-Meehan | May 2008 | A1 |
20080104761 | Rawls-Meehan | May 2008 | A1 |
20080109959 | Rawls-Meehan | May 2008 | A1 |
20080109964 | Flocard et al. | May 2008 | A1 |
20080109965 | Mossbeck | May 2008 | A1 |
20080115272 | Rawls-Meehan | May 2008 | A1 |
20080115273 | Rawls-Meehan | May 2008 | A1 |
20080115274 | Rawls-Meehan | May 2008 | A1 |
20080115275 | Rawls-Meehan | May 2008 | A1 |
20080115276 | Rawls-Meehan | May 2008 | A1 |
20080115277 | Rawls-Meehan | May 2008 | A1 |
20080115278 | Rawls-Meehan | May 2008 | A1 |
20080115279 | Rawls-Meehan | May 2008 | A1 |
20080115280 | Rawls-Meehan | May 2008 | A1 |
20080115281 | Rawls-Meehan | May 2008 | A1 |
20080115282 | Rawls-Meehan | May 2008 | A1 |
20080120775 | Rawls-Meehan | May 2008 | A1 |
20080120776 | Rawls-Meehan | May 2008 | A1 |
20080120777 | Rawls-Meehan | May 2008 | A1 |
20080120778 | Rawls-Meehan | May 2008 | A1 |
20080120779 | Rawls-Meehan | May 2008 | A1 |
20080120784 | Warner et al. | May 2008 | A1 |
20080122616 | Warner | May 2008 | A1 |
20080126122 | Warner et al. | May 2008 | A1 |
20080126132 | Warner | May 2008 | A1 |
20080127418 | Rawls-Meehan | Jun 2008 | A1 |
20080127424 | Rawls-Meehan | Jun 2008 | A1 |
20080147442 | Warner | Jun 2008 | A1 |
20080162171 | Rawls-Meehan | Jul 2008 | A1 |
20080189865 | Bhai | Aug 2008 | A1 |
20080262657 | Howell | Oct 2008 | A1 |
20080275314 | Mack et al. | Nov 2008 | A1 |
20080281611 | Rawls-Meehan | Nov 2008 | A1 |
20080281612 | Rawls-Meehan | Nov 2008 | A1 |
20080281613 | Rawls-Meehan | Nov 2008 | A1 |
20080288272 | Rawls-Meehan | Nov 2008 | A1 |
20080288273 | Rawls-Meehan | Nov 2008 | A1 |
20080306351 | Izumi | Dec 2008 | A1 |
20080307582 | Flocard et al. | Dec 2008 | A1 |
20090018853 | Rawls-Meehan | Jan 2009 | A1 |
20090018854 | Rawls-Meehan | Jan 2009 | A1 |
20090018855 | Rawls-Meehan | Jan 2009 | A1 |
20090018856 | Rawls-Meehan | Jan 2009 | A1 |
20090018857 | Rawls-Meehan | Jan 2009 | A1 |
20090018858 | Rawls-Meehan | Jan 2009 | A1 |
20090024406 | Rawls-Meehan | Jan 2009 | A1 |
20090037205 | Rawls-Meehan | Feb 2009 | A1 |
20090043595 | Rawls-Meehan | Feb 2009 | A1 |
20090064420 | Rawls-Meehan | Mar 2009 | A1 |
20090100599 | Rawls-Meehan | Apr 2009 | A1 |
20090121660 | Rawls-Meehan | May 2009 | A1 |
20090139029 | Rawls-Meehan | Jun 2009 | A1 |
20090203972 | Henehgan et al. | Aug 2009 | A1 |
20090275808 | DiMaio et al. | Nov 2009 | A1 |
20090314354 | Chaffee | Dec 2009 | A1 |
20100025900 | Rawls-Meehan | Feb 2010 | A1 |
20100090383 | Rawls-Meehan | Apr 2010 | A1 |
20100094139 | Brauers et al. | Apr 2010 | A1 |
20100099954 | Dickinson et al. | Apr 2010 | A1 |
20100152546 | Behan et al. | Jun 2010 | A1 |
20100170043 | Young | Jul 2010 | A1 |
20100170044 | Kao et al. | Jul 2010 | A1 |
20100174198 | Young et al. | Jul 2010 | A1 |
20100174199 | Young et al. | Jul 2010 | A1 |
20100191136 | Wolford | Jul 2010 | A1 |
20100199432 | Rawls-Meehan | Aug 2010 | A1 |
20100231421 | Rawls-Meehan | Sep 2010 | A1 |
20100302044 | Chacon et al. | Dec 2010 | A1 |
20100317930 | Oexman et al. | Dec 2010 | A1 |
20110001622 | Gentry | Jan 2011 | A1 |
20110010014 | Oexman et al. | Jan 2011 | A1 |
20110015495 | Dothie et al. | Jan 2011 | A1 |
20110041592 | Schmoeller et al. | Feb 2011 | A1 |
20110068935 | Riley et al. | Mar 2011 | A1 |
20110087113 | Mack et al. | Apr 2011 | A1 |
20110094041 | Rawls-Meehan | Apr 2011 | A1 |
20110115635 | Petrovski et al. | May 2011 | A1 |
20110138539 | Mahoney et al. | Jun 2011 | A1 |
20110144455 | Young et al. | Jun 2011 | A1 |
20110156915 | Brauers et al. | Jun 2011 | A1 |
20110163885 | Poulos et al. | Jul 2011 | A1 |
20110224510 | Oakhill | Sep 2011 | A1 |
20110239374 | Rawls-Meehan | Oct 2011 | A1 |
20110252569 | Rawls-Meehan | Oct 2011 | A1 |
20110258784 | Rawls-Meehan | Oct 2011 | A1 |
20110282216 | Shinar et al. | Nov 2011 | A1 |
20110283462 | Rawls-Meehan | Nov 2011 | A1 |
20110291795 | Rawls-Meehan | Dec 2011 | A1 |
20110291842 | Oexman | Dec 2011 | A1 |
20110295083 | Doelling | Dec 2011 | A1 |
20110302720 | Yakam et al. | Dec 2011 | A1 |
20110306844 | Young | Dec 2011 | A1 |
20120017371 | Pollard | Jan 2012 | A1 |
20120025992 | Tallent et al. | Feb 2012 | A1 |
20120053423 | Kenalty et al. | Mar 2012 | A1 |
20120053424 | Kenalty et al. | Mar 2012 | A1 |
20120056729 | Rawls-Meehan | Mar 2012 | A1 |
20120057685 | Rawls-Meehan | Mar 2012 | A1 |
20120090698 | Giori et al. | Apr 2012 | A1 |
20120110738 | Rawls-Meehan | May 2012 | A1 |
20120110739 | Rawls-Meehan | May 2012 | A1 |
20120110740 | Rawls-Meehan | May 2012 | A1 |
20120112890 | Rawls-Meehan | May 2012 | A1 |
20120112891 | Rawls-Meehan | May 2012 | A1 |
20120112892 | Rawls-Meehan | May 2012 | A1 |
20120116591 | Rawls-Meehan | May 2012 | A1 |
20120119886 | Rawls-Meehan | May 2012 | A1 |
20120119887 | Rawls-Meehan | May 2012 | A1 |
20120138067 | Rawls-Meehan | Jun 2012 | A1 |
20120154155 | Brasch | Jun 2012 | A1 |
20120186019 | Rawls-Meehan | Jul 2012 | A1 |
20120198632 | Rawls-Meehan | Aug 2012 | A1 |
20120204887 | Connor | Aug 2012 | A1 |
20120240340 | Driscoll et al. | Sep 2012 | A1 |
20120304391 | Driscoll et al. | Dec 2012 | A1 |
20120311790 | Nomura et al. | Dec 2012 | A1 |
20130160212 | Oexman et al. | Jun 2013 | A1 |
20130174347 | Oexman et al. | Jul 2013 | A1 |
20130227787 | Herbst et al. | Sep 2013 | A1 |
20140007656 | Mahoney | Jan 2014 | A1 |
20140047644 | Mossbeck | Feb 2014 | A1 |
20140137332 | McGuire et al. | May 2014 | A1 |
20140182061 | Zaiss | Jul 2014 | A1 |
20140250597 | Chen et al. | Sep 2014 | A1 |
20140257571 | Chen et al. | Sep 2014 | A1 |
20140259417 | Nunn et al. | Sep 2014 | A1 |
20140259418 | Nunn et al. | Sep 2014 | A1 |
20140259419 | Stusynski | Sep 2014 | A1 |
20140259431 | Fleury | Sep 2014 | A1 |
20140259433 | Nunn et al. | Sep 2014 | A1 |
20140259434 | Nunn et al. | Sep 2014 | A1 |
20140277611 | Nunn et al. | Sep 2014 | A1 |
20140277778 | Nunn et al. | Sep 2014 | A1 |
20140277822 | Nunn et al. | Sep 2014 | A1 |
20140313700 | Connell et al. | Oct 2014 | A1 |
20150007393 | Palashewski et al. | Jan 2015 | A1 |
20150025327 | Young et al. | Jan 2015 | A1 |
20150026896 | Fleury et al. | Jan 2015 | A1 |
20150136146 | Hood et al. | May 2015 | A1 |
20150157137 | Nunn et al. | Jun 2015 | A1 |
20150157519 | Stusynski et al. | Jun 2015 | A1 |
20150182033 | Brosnan et al. | Jul 2015 | A1 |
20150182397 | Palashewski et al. | Jul 2015 | A1 |
20150182399 | Palashewski et al. | Jul 2015 | A1 |
20150182418 | Zaiss | Jul 2015 | A1 |
20150290059 | Brosnan et al. | Oct 2015 | A1 |
20150374137 | Mahoney et al. | Dec 2015 | A1 |
20160100696 | Palashewski et al. | Apr 2016 | A1 |
Number | Date | Country |
---|---|---|
1557270 | Dec 2004 | CN |
101224149 | Jul 2008 | CN |
2007-283106 | Nov 2007 | JP |
Entry |
---|
International Search Report in International Application No. PCT/US2014/026568, dated May 26, 2014, 3 pages. |
International Search Report in International Application No. PCT/US2014/027752, dated Jul. 15, 2014, 5 pages. |
International Search Report in International Application No. PCT/US2014/028137, dated Jul. 7, 2014, 2 pages. |
Number | Date | Country | |
---|---|---|---|
20160338871 A1 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
61782394 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14206841 | Mar 2014 | US |
Child | 15159194 | US |