Patent Grant
10101717
Home computer systems contain a great deal of important information for the computer owner. Individuals often keep a wealth of important and personal information on their home computer system. For example, individuals often store personal finance information and other confidential personal information on their home computer as well as photos and videos of important people and life events relating to the individual. Using current systems, many computer owners do not back up or secure the important and personal data stored on the home computer system. Failure to back up data can lead to data loss in the event of a computer failure, fire, or theft of the computer. Individuals that back up their data often back the data up to a backup storage facility, often called “cloud storage.” Cloud storage, while convenient, can create potential security issues, which can allow the individual's data to be compromised by unscrupulous data hackers. Additionally, the data stored on a computer system, such as a home laptop, is unsecured on the laptop, and is lost and potentially compromised if the laptop is stolen.
In some embodiments, a system may be provided including a plurality of home automation components, each component from the plurality of home automation components including a storage device. The system may include a controller database for storing control data for the home automation system. The system may include an electronic device communicatively coupled to each component from the plurality of home automation components and to a computing device and to the controller database. The electronic device may include one or more processors and a memory coupled with and readable by the one or more processors and having stored therein a sequence of instructions which, when executed by the one or more processors, cause the one or more processors to receive data from the computing device; store at least a portion of the data in the storage device of a component from the plurality of home automation components; and store information associating the storage device of the component and the at least a portion of the data in the controller database.
Embodiments of such a system may include one or more of the following features: wherein the data includes a data file, and wherein the sequence of instructions that cause the one or more processors to store at least a portion of the data to the storage device of a component from the plurality of home automation components includes instructions that cause the one or more processors to split the data file into a plurality of data segments. Embodiments may also include storing a first data segment from the plurality of data segments to the storage device of a first component from the plurality of home automation components, and storing a second data segment from the plurality of data segments to the storage device of a second component from the plurality of home automation components.
The memory may further have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to: store information associating the first data segment with the storage device of the first component in the controller database, and store information associating the second data segment with the storage device of the second component in the controller database.
Embodiments of such a system may further include wherein the storage device of the component from the plurality of home automation components is a removable memory card. The system may further include wherein the storage device of the component from the plurality of home automation components is not removable. The system may further include wherein the computing device does not maintain a copy of the data at the computing device. The system may further include wherein the component from the plurality of home automation components is selected from the group consisting of light bulb, light switch, motion sensor, door sensor, and smoke detector. The system may further include wherein the electronic device is a home automation controller, the data is one digital data file, and the entire digital data file is stored on the storage device of the home automation component.
Embodiments of such a system may further include wherein the component from the plurality of home automation components is removed from the plurality of home automation components. The memory further may have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to: determine that the component from the plurality of home automation components was removed; identify the portion of the data stored on the storage device of the component; and rebuild the at least a portion of the data on a storage device of a different component from the plurality of home automation components.
The memory further may have stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to: receive a request for the data from the computing device; determine, using information stored in the controller database, that the data includes the first data segment and the second data segment. There may be further instructions that determine, using information stored in the controller database, that the first data segment is stored on the storage device of the first component and the second data segment is stored on the storage device of the second component. There may be further instructions that retrieve the first data segment from the storage device of the first component. There may be further instructions that retrieve the second data segment from the storage device of the second component. There may be further instructions that combine the first data segment and the second data segment to regenerate the data. There may be further instructions that send the data to the computing device.
In some embodiments, a method may be provided including receiving a data file at a home automation controller from a computing device communicatively coupled to the home automation controller. The method may also include storing, by the home automation controller, at least a portion of the data file to a storage device of a home automation component from a plurality of home automation components, the plurality of home automation components being communicatively coupled to the home automation controller. The method may further include storing, by the home automation controller in a controller database, information associating the at least a portion of the data file and the storage device of the component.
Embodiments of such a method may include one or more of the following features: splitting, by the home automation controller, the data file into a plurality of data segments. The method may further include storing, by the home automation controller, a first data segment from the plurality of data segments to the storage device of a first home automation component from the plurality of home automation components. The method may further include storing, by the home automation controller, a second data segment from the plurality of data segments to the storage device of a second component from the plurality of home automation components.
The method may further include storing, by the home automation controller, information associating the first data segment with the storage device of the first component in the controller database. The method may further include storing, by the home automation controller, information associating the second data segment with the storage device of the second component in the controller database.
The method may further include wherein the storage device of the component from the plurality of home automation components is a removable memory card. The method may further include wherein the storage device of the component from the plurality of home automation components is not removable. The method may further include wherein the computing device does not maintain a copy of the data at the computing device.
The method may further include wherein the component from the plurality of home automation components is selected from the group consisting of light bulb, light switch, motion sensor, door sensor, and smoke detector. The method may further include wherein the data file is one digital data file, and the entire digital data file is stored on the storage device of the home automation component.
The method may further include wherein the component from the plurality of home automation components is removed from the plurality of home automation components, and wherein the method further includes determining, by the home automation controller, that the component from the plurality of home automation components was removed. The method may further include identifying, by the home automation controller, the at least a portion of the data file stored on the storage device of the component. The method may further include rebuilding, by the home automation controller, the at least a portion of the data file on the storage device of a different component from the plurality of home automation components.
The method may further include receiving, by the home automation controller, a request for the data file from the computing device. The method may further include retrieving, by the home automation controller, the first data segment from the storage device of the first component. The method may further include retrieving, by the home automation controller, the second data segment from the storage device of the second component. The method may further include combining, by the home automation controller, the first data segment and the second data segment to regenerate the data file. The method may further include sending the data file to the computing device.
In the appended figures, similar components and/or features may have the same numerical reference label. Further, various components of the same type may be distinguished by following the reference label by a letter that distinguishes among the similar components and/or features. If only the first numerical reference label is used in the specification, the description is applicable to any one of the similar components and/or features having the same first numerical reference label irrespective of the letter suffix.
The ability to store data from a home computing device utilizing a home automation system can be useful to an individual. While many current home computing systems have local storage space, the amount of space and security of the data it holds can be questionable. Having a secure location to store or back up data in a home environment can be useful.
Embodiments detailed herein present a home automation data storage system that can utilize a home automation system that may or may not have been previously installed in a home. The system can store or back-up data from a home computing device. The system can utilize the storage space available on home automation components. Home automation components (e.g., motion sensors, glass breakage sensors, door bells, garage door openers, security cameras, light bulbs, light switches, contact sensors, power outlets, smoke detectors, carbon monoxide detectors, etc.) generally have some amount of persistent storage (e.g., non-volatile storage) within the component. In some cases, the components have only a very small amount of storage space (e.g., 8 kB) and in other cases, the components have a larger amount of storage space (e.g., 1 GB). The methods and systems described herein can utilize the existing storage capacity of home automation components or, in some embodiments, can utilize removable storage that expands a component's storage capacity (e.g., CompactFlash card, Secure Digital card, memory stick, etc.), or, in some embodiments, can use components that are designed to include larger storage devices within the component.
Television service provider system 110 and satellite transmitter equipment 120 may be operated by a television service provider. A television service provider may distribute television channels, on-demand programming, programming information, and/or other content/services to users. Television service provider system 110 may receive feeds of one or more television channels and content from various sources. Such television channels may include multiple television channels that contain at least some of the same content (e.g., network affiliates). To distribute television channels for presentation to users, feeds of the television channels may be relayed to user equipment via multiple television distribution satellites. Each satellite may relay multiple transponder streams. Satellite transmitter equipment 120 may be used to transmit a feed of one or more television channels from television service provider system 110 to one or more satellites 130. While a single television service provider system 110 and satellite transmitter equipment 120 are illustrated as part of satellite television distribution system 100, it should be understood that multiple instances of transmitter equipment may be used, possibly scattered geographically, to communicate with satellites 130. Such multiple instances of satellite transmitting equipment may communicate with the same or with different satellites. Different television channels may be transmitted to satellites 130 from different instances of transmitting equipment. For instance, a different satellite dish of satellite transmitter equipment 120 may be used for communication with satellites in different orbital slots.
Satellites 130 may be configured to receive signals, such as streams of television channels, from one or more satellite uplinks such as satellite transmitter equipment 120. Satellites 130 may relay received signals from satellite transmitter equipment 120 (and/or other satellite transmitter equipment) to multiple instances of user equipment via transponder streams. Different frequencies may be used for uplink signals 170 from downlink signals 180. Satellites 130 may be in geosynchronous orbit. Each of the transponder streams transmitted by satellites 130 may contain multiple television channels transmitted as packetized data. For example, a single transponder stream may be a serial digital packet stream containing multiple television channels. Therefore, packets for multiple television channels may be interspersed. Further, information used by television receiver 150 for home automation functions may also be relayed to a television receiver via one or more transponder streams.
Multiple satellites 130 may be used to relay television channels from television service provider system 110 to satellite dish 140. Different television channels may be carried using different satellites. Different television channels may also be carried using different transponders of the same satellite; thus, such television channels may be transmitted at different frequencies and/or different frequency ranges. As an example, a first and second television channel may be relayed via a first transponder of satellite 130a. A third, fourth, and fifth television channel may be relayed via a different satellite or a different transponder of the same satellite relaying the transponder stream at a different frequency. A transponder stream transmitted by a particular transponder of a particular satellite may include a finite number of television channels, such as seven. Accordingly, if many television channels are to be made available for viewing and recording, multiple transponder streams may be necessary to transmit all of the television channels to the instances of user equipment.
Satellite dish 140 may be a piece of user equipment that is used to receive transponder streams from one or more satellites, such as satellites 130. Satellite dish 140 may be provided to a subscriber for use on a subscription basis to receive television channels provided by the television service provider system 110, satellite transmitter equipment 120, and/or satellites 130. Satellite dish 140, which may include one or more low noise blocks (LNBs), may be configured to receive transponder streams from multiple satellites and/or multiple transponders of the same satellite. Satellite dish 140 may be configured to receive television channels via transponder streams on multiple frequencies. Based on the characteristics of television receiver 150 and/or satellite dish 140, it may only be possible to capture transponder streams from a limited number of transponders concurrently. For example, a tuner of television receiver 150 may only be able to tune to a single transponder stream from a transponder of a single satellite at a given time. The tuner can then be re-tuned to another transponder of the same or a different satellite. A television receiver 150 having multiple tuners may allow for multiple transponder streams to be received at the same time.
In communication with satellite dish 140 may be one or more television receivers. Television receivers may be configured to decode signals received from satellites 130 via satellite dish 140 for output and presentation via a display device, such as display device 160. A television receiver may be incorporated as part of a television or may be part of a separate device, commonly referred to as a set-top box (STB). Television receiver 150 may decode signals received via satellite dish 140 and provide an output to display device 160. On-demand content, such as PPV content, may be stored to a computer-readable storage medium.
Display device 160 may be used to present video and/or audio decoded and output by television receiver 150. Television receiver 150 may also output a display of one or more interfaces to display device 160, such as an electronic programming guide (EPG). In many embodiments, display device 160 is a television. Display device 160 may also be a monitor, computer, or some other device configured to display video and, possibly, play audio.
Uplink signal 170a represents a signal between satellite transmitter equipment 120 and satellite 130a. Uplink signal 170b represents a signal between satellite transmitter equipment 120 and satellite 130b. Each of uplink signals 170 may contain streams of one or more different television channels. For example, uplink signal 170a may contain a first group of television channels, while uplink signal 170b contains a second group of television channels. Each of these television channels may be scrambled such that unauthorized persons are prevented from accessing the television channels.
Downlink signal 180a represents a signal between satellite 130a and satellite dish 140. Downlink signal 180b represents a signal between satellite 130b and satellite dish 140. Each of downlink signals 180 may contain one or more different television channels, which may be at least partially scrambled. A downlink signal 180 may be in the form of a transponder stream. A single transponder stream may be tuned to at a given time by a tuner of a television receiver. For example, downlink signal 180a may be a first transponder stream containing a first group of television channels, while downlink signal 180b may be a second transponder stream containing a different group of television channels. In addition to or instead of containing television channels, a transponder stream can be used to transmit on-demand content to television receivers, including PPV content, which may be stored locally by the television receiver until output for presentation.
Network 190, which may include the Internet, may allow for bidirectional communication between television receiver 150 and television service provider system 110, such as for home automation related services provided by home automation service server 112. Although illustrated as part of the television service provider system, the home automation service server 112 may be provided by a third party in embodiments. In addition or in alternate to network 190, a telephone, e.g., landline, or cellular connection may be used to enable communication between television receiver 150 and television service provider system 110.
Television receiver 200 may be incorporated as part of a television, such as display device 160 of
Processors 210 may include one or more specialized and/or general-purpose processors configured to perform processes such as tuning to a particular channel, accessing and displaying EPG information from EPG database 230, and/or receiving and processing input from a user. It should be understood that the functions performed by various modules of
Control processor 210a may communicate with tuning management processor 210b. Control processor 210a may control the recording of television channels based on timers stored in DVR database 245. Control processor 210a may also provide commands to tuning management processor 210b when recording of a television channel is to cease. In addition to providing commands relating to the recording of television channels, control processor 210a may provide commands to tuning management processor 210b that indicate television channels to be output to decoder module 233 for output to a display device. Control processor 210a may also communicate with network interface 220 and remote control interface 250. Control processor 210a may handle incoming data from network interface 220 and remote control interface 250. Additionally, control processor 210a may be configured to output data via network interface 220.
Control processor 210a may include home automation engine 211. Home automation engine 211 may permit television receiver and control processor 210a to provide home automation functionality. Home automation engine 211 may have a JSON (JavaScript Object Notation) command interpreter or some other form of command interpreter that is configured to communicate with wireless devices via network interface 220 and a message server, possibly via a message server client. Such a command interpreter of home automation engine 211 may also communicate via a local area network with devices without using the Internet. Home automation engine 211 may contain multiple controllers specific to different protocols; for instance, a ZigBee® controller, a Z-Wave® controller, and/or an IP camera controller, wireless LAN, 802.11, may be present. Home automation engine 211 may contain a media server configured to serve streaming audio and/or video to remote devices on a local area network or the Internet. Television receiver may be able to serve such devices with recorded content, live content, and/or content recorded using one or more home automation devices, such as cameras.
Tuners 215 may include one or more tuners used to tune to transponders that include broadcasts of one or more television channels. Such tuners may be used also to receive for storage on-demand content and/or addressable television commercials. In some embodiments, two, three, or more than three tuners may be present, such as four, six, or eight tuners. Each tuner contained in tuners 215 may be capable of receiving and processing a single transponder stream from a satellite transponder or from a cable network at a given time. As such, a single tuner may tune to a single transponder stream at a given time. If tuners 215 include multiple tuners, one tuner may be used to tune to a television channel on a first transponder stream for display using a television, while another tuner may be used to tune to a television channel on a second transponder for recording and viewing at some other time. If multiple television channels transmitted on the same transponder stream are desired, a single tuner of tuners 215 may be used to receive the signal containing the multiple television channels for presentation and/or recording. Tuners 215 may receive commands from tuning management processor 210b. Such commands may instruct tuners 215 to which frequencies are to be tuned.
Network interface 220 may be used to communicate via an alternate communication channel with a television service provider, if such communication channel is available. A communication channel may be via satellite, which may be unidirectional to television receiver 200, and the alternate communication channel, which may be bidirectional, may be via a network, such as the Internet. Data may be transmitted from television receiver 200 to a television service provider system and from the television service provider system to television receiver 200. Information may be transmitted and/or received via network interface 220. For instance, instructions from a television service provider may also be received via network interface 220, if connected with the Internet. Besides the primary communication channel being satellite, cable network, an IP-based network, or broadcast network may be used. Network interface 220 may permit wireless communication with one or more types of networks, including using home automation network protocols and wireless network protocols. Also, wired networks may be connected to and communicated with via network interface 220. Device interface 221 may represent a USB port or some other form of communication port that permits communication with a communication device as will be explained further below.
Storage medium 225 may represent one or more non-transitory computer-readable storage mediums. Storage medium 225 may include memory and/or a hard drive. Storage medium 225 may be used to store information received from one or more satellites and/or information received via network interface 220. Storage medium 225 may store information related to on-demand programming database 227, EPG database 230, DVR database 245, home automation settings database 247, and/or home automation script database 248. Recorded television programs may be stored using storage medium 225 as part of DVR database 245. Storage medium 225 may be partitioned or otherwise divided, such as into folders, such that predefined amounts of storage medium 225 are devoted to storage of television programs recorded due to user-defined timers and stored television programs recorded due to provider-defined timers.
Home automation settings database 247 may allow configuration settings of home automation devices and user preferences to be stored. Home automation settings database 247 may store data related to various devices that have been set up to communicate with television receiver 200. For instance, home automation settings database 247 may be configured to store information on which types of events should be indicated to users, to which users, in what order, and what communication methods should be used. For instance, an event such as an open garage may only be notified to certain wireless devices, e.g., a cellular phone associated with a parent, not a child, notification may be by a third-party notification server, email, text message, and/or phone call. In some embodiments, a second notification method may only be used if a first fails. For instance, if a notification cannot be sent to the user via a third-party notification server, an email may be sent.
Home automation settings database 247 may store information that allows for the configuration and control of individual home automation devices which may operate using Z-wave® and ZigBee®—specific protocols. To do so, home automation engine 211 may create a proxy for each device that allows for settings for the device to be passed through a UI, e.g., presented on a television, to allow for settings to be solicited for and collected via a user interface presented by television receiver or overlay device. The received settings may then be handled by the proxy specific to the protocol, allowing for the settings to be passed on to the appropriate device. Such an arrangement may allow for settings to be collected and received via a UI of the television receiver or overlay device and passed to the appropriate home automation device and/or used for managing the appropriate home automation device. For example, a piece of exercise equipment that is enabled to interface with the home automation engine 211, such as via device interface 221, may be configured at the electronic device 211 in addition to on the piece of exercise equipment itself. Additionally, a mobile device or application residing on a mobile device and utilized with exercise equipment may be configured in such a fashion as well for displaying received fitness information on a coupled display device.
Home automation script database 248 may store scripts that detail how home automation devices are to function based on various events occurring. For instance, if stored content starts being played back by television receiver 200, lights in the vicinity of display device 160 may be dimmed and shades may be lowered by communicatively coupled and controlled shade controller. As another example, when a user shuts programming off late in the evening, there may be an assumption the user is going to bed. Therefore, the user may configure television receiver 200 to lock all doors via a lock controller, shut the garage door via garage controller, lower a heat setting of thermostat, shut off all lights via a light controller, and determine if any windows or doors are open via window sensors and door sensors, and, if so, alert the user. Such scripts or programs may be predefined by the home automation/television service provider and/or may be defined by a user.
In some embodiments, home automation script database 248 may allow for various music profiles to be implemented. For instance, based on home automation settings within a structure, appropriate music may be played. For instance, when a piece of exercise equipment is connected or is used, energizing music may be played. Conversely, based on the music being played, settings of home automation devices may be determined. If television programming, such as a movie, is output for playback by television receiver 150, a particular home automation script may be used to adjust home automation settings, e.g., lower lights, raise temperature, and lock doors.
EPG database 230 may store information related to television channels and the timing of programs appearing on such television channels. EPG database 230 may be stored using storage medium 225, which may be a hard drive or solid-state drive. Information from EPG database 230 may be used to inform users of what television channels or programs are popular and/or provide recommendations to the user. Information from EPG database 230 may provide the user with a visual interface displayed by a television that allows a user to browse and select television channels and/or television programs for viewing and/or recording. Information used to populate EPG database 230 may be received via network interface 220, via satellite, or some other communication link with a television service provider, e.g., a cable network. Updates to EPG database 230 may be received periodically. EPG database 230 may serve as an interface for a user to control DVR functions of television receiver 200, and/or to enable viewing and/or recording of multiple television channels simultaneously. EPG database 240 may also contain information about on-demand content or any other form of accessible content.
Decoder module 233 may serve to convert encoded video and audio into a format suitable for output to a display device. For instance, decoder module 233 may receive MPEG video and audio from storage medium 225 or descrambling engine 265 to be output to a television. MPEG video and audio from storage medium 225 may have been recorded to DVR database 245 as part of a previously-recorded television program. Decoder module 233 may convert the MPEG video and audio into a format appropriate to be displayed by a television or other form of display device and audio into a format appropriate to be output from speakers, respectively. Decoder module 233 may have the ability to convert a finite number of television channel streams received from storage medium 225 or descrambling engine 265, simultaneously. For instance, decoders within decoder module 233 may be able to only decode a single television channel at a time. Decoder module 233 may have various numbers of decoders.
Television interface 235 may serve to output a signal to a television or another form of display device in a proper format for display of video and playback of audio. As such, television interface 235 may output one or more television channels, stored television programming from storage medium 225, e.g., television programs from DVR database 245, television programs from on-demand programming 230 and/or information from EPG database 230, to a television for presentation. Television interface 235 may also serve to output a CVM.
Digital Video Recorder (DVR) functionality may permit a television channel to be recorded for a period of time. DVR functionality of television receiver 200 may be managed by control processor 210a. Control processor 210a may coordinate the television channel, start time, and stop time of when recording of a television channel is to occur. DVR database 245 may store information related to the recording of television channels. DVR database 245 may store timers that are used by control processor 210a to determine when a television channel should be tuned to and its programs recorded to DVR database 245 of storage medium 225. In some embodiments, a limited amount of storage medium 225 may be devoted to DVR database 245. Timers may be set by the television service provider and/or one or more users of television receiver 200.
DVR database 245 may also be used to record recordings of service provider-defined television channels. For each day, an array of files may be created. For example, based on provider-defined timers, a file may be created for each recorded television channel for a day. For example, if four television channels are recorded from 6-10 PM on a given day, four files may be created; one for each television channel. Within each file, one or more television programs may be present. The service provider may define the television channels, the dates, and the time periods for which the television channels are recorded for the provider-defined timers. The provider-defined timers may be transmitted to television receiver 200 via the television provider's network. For example, in a satellite-based television service provider system, data necessary to create the provider-defined timers at television receiver 150 may be received via satellite.
On-demand programming database 227 may store additional television programming. On-demand programming database 227 may include television programming that was not recorded to storage medium 225 via a timer, either user- or provider-defined. Rather, on-demand programming may be programming provided to the television receiver directly for storage by the television receiver and for later presentation to one or more users. On-demand programming may not be user-selected. As such, the television programming stored to on-demand programming database 227 may be the same for each television receiver of a television service provider. On-demand programming database 227 may include pay-per-view (PPV) programming that a user must pay and/or use an amount of credits to view. For instance, on-demand programming database 227 may include movies that are not available for purchase or rental yet.
Referring back to tuners 215, television channels received via satellite or cable may contain at least some scrambled data. Packets of audio and video may be scrambled to prevent unauthorized users, e.g., nonsubscribers, from receiving television programming without paying the television service provider. When a tuner of tuners 215 is receiving data from a particular transponder of a satellite, the transponder stream may be a series of data packets corresponding to multiple television channels. Each data packet may contain a packet identifier (PID), which can be determined to be associated with a particular television channel. Particular data packets, referred to as entitlement control messages (ECMs), may be periodically transmitted. ECMs may be associated with another PID and may be encrypted; television receiver 200 may use decryption engine 261 of security device 260 to decrypt ECMs. Decryption of an ECM may only be possible if the user has authorization to access the particular television channel associated with the ECM. When an ECM is determined to correspond to a television channel being stored and/or displayed, the ECM may be provided to security device 260 for decryption.
When security device 260 receives an encrypted ECM, security device 260 may decrypt the ECM to obtain some number of control words. In some embodiments, from each ECM received by security device 260, two control words are obtained. In some embodiments, when security device 260 receives an ECM, it compares the ECM to the previously received ECM. If the two ECMs match, the second ECM is not decrypted because the same control words would be obtained. In other embodiments, each ECM received by security device 260 is decrypted; however, if a second ECM matches a first ECM, the outputted control words will match; thus, effectively, the second ECM does not affect the control words output by security device 260. Security device 260 may be permanently part of television receiver 200 or may be configured to be inserted and removed from television receiver 200, such as a smart card, cable card, or the like.
Tuning management processor 210b may be in communication with tuners 215 and control processor 210a. Tuning management processor 210b may be configured to receive commands from control processor 210a. Such commands may indicate when to start/stop receiving and/or recording of a television channel and/or when to start/stop causing a television channel to be output to a television. Tuning management processor 210b may control tuners 215. Tuning management processor 210b may provide commands to tuners 215 that instruct the tuners which satellite, transponder, and/or frequency to tune to. From tuners 215, tuning management processor 210b may receive transponder streams of packetized data.
Descrambling engine 265 may use the control words output by security device 260 in order to descramble video and/or audio corresponding to television channels for storage and/or presentation. Video and/or audio data contained in the transponder data stream received by tuners 215 may be scrambled. Video and/or audio data may be descrambled by descrambling engine 265 using a particular control word. Which control word output by security device 260 to be used for successful descrambling may be indicated by a scramble control identifier present within the data packet containing the scrambled video or audio. Descrambled video and/or audio may be output by descrambling engine 265 to storage medium 225 for storage, in DVR database 245, and/or to decoder module 233 for output to a television or other presentation equipment via television interface 235.
In some embodiments, the television receiver 200 may be configured to periodically reboot in order to install software updates downloaded over the network 190 or satellites 130. Such reboots may occur for example during the night when the users are likely asleep and not watching television. If the system utilizes a single processing module to provide television receiving and home automation functionality, then the security functions may be temporarily deactivated. In order to increase the security of the system, the television receiver 200 may be configured to reboot at random times during the night in order to allow for installation of updates. Thus, an intruder is less likely to guess the time when the system is rebooting. In some embodiments, the television receiver 200 may include multiple processing modules for providing different functionality, such as television receiving functionality and home automation, such that an update to one module does not necessitate reboot of the whole system. In other embodiments, multiple processing modules may be made available as a primary and a backup during any installation or update procedures.
For simplicity, television receiver 200 of
While the television receiver 200 has been illustrated as a satellite-based television receiver, it is to be appreciated that techniques below may be implemented in other types of television receiving devices, such a cable receivers, terrestrial receivers, IPTV receivers or the like. In some embodiments, the television receiver 200 may be configured as a hybrid receiving device, capable of receiving content from disparate communication networks, such as satellite and terrestrial television broadcasts. In some embodiments, the tuners may be in the form of network interfaces capable of receiving content from designated network locations. The home automation functions of television receiver 200 may be performed by an overlay device. If such an overlay device is used, television programming functions may still be provided by a television receiver that is not used to provide home automation functions.
Computing device 305 can be any home computing device such as, for example, a desktop computer, a laptop computer, a tablet, a smartphone, or any other suitable computing device. The computing device 305 can be, for example, computer system 900 as described with respect to
Home automation controller 310 can be, for example, television receiver 150 as described with respect to
In some home automation systems there is a dedicated controller for controlling the home automation system, such as home automation controller 310, and a separate computing device 305 as depicted in
Home automation data storage system 300 can include any number of home automation components. In some embodiments, home automation data storage system 300 can include light switch 315, light bulb 320, smoke detector 325, door sensor 330, and security camera 340. In some embodiments home automation data storage system 300 can include one or more of each component. For example, home automation data storage system can include twenty-five (25) light switches 315. Additional components can be included that are not depicted in
Each home automation component (315, 320, 325, 330, 340) can be communicatively coupled to home automation controller 310. The home automation components can be coupled through a wired connection or through a wireless connection similar to computing device 305. The computing device 305 can communicate with home automation controller 310 using a different and/or the same communication protocol than each home automation component (315, 320, 325, 330, 340). For example, communication line A can be a wired connection utilizing TCP/IP, while communication line B can be Bluetooth, communication line C can be ZigBee, communication line D can be ZWave, communication line E can be Bluetooth, and communication line F can be a wired connection using TCP/IP. Light switch 315 can be coupled to home automation controller 310 as shown by the communication line B in
Each home automation component (315, 320, 325, 330, 340) can include a storage device. The storage device in each component can be a different size than the storage device in other components. For example, light switch 315 can include a storage device with a capacity of 100 kB and door sensor 330 can include a storage device with a capacity of 1 MB. In some embodiments, the home automation components can include a non-removable storage device that can be, for example, internally located in the component. In some embodiments, the home automation components can include a removable storage device, such as, for example, a secure digital memory card (“SD card”). As shown in
In some embodiments, the storage devices located on each home automation component 315, 320, 325, 330, 340 can be configured individually to store the data designated by the home automation controller 310. In some embodiments, some or all of the storage devices located on the home automation components 315, 320, 325, 330, 340 can be configured into a Redundant Array of Independent Disk (“RAID”)-type configuration. RAID arrays can be configured in several different ways including allowing for fault tolerance. The storage devices in the home automation components 315, 320, 325, 330, 340 can be configured to provide fault tolerance in the event that a home automation component 315, 320, 325, 330, 340 fails, which could otherwise result in loss of data. An example of this type of fault tolerance is RAID 5. In some embodiments, the storage device associated with any given home automation component 315, 320, 325, 330, 340 can be utilized as a single storage location or can be partitioned to provide several smaller storage locations. Additionally, the storage devices can be grouped into arrays of devices that optimize performance and utilization of disk space. Within a single home automation data storage system, the multiple storage devices can be configured into multiple arrays for providing fault tolerance and speed optimization of data. In a typical RAID array the drives are all identical high performance drives. The configuration in a home automation data storage system can be different than a standard RAID array in that the storage devices may not be large, identical, or high performance. In some embodiments, the home automation components 315, 320, 325, 330, 340 can be communicatively coupled with other home automation components 315, 320, 325, 330, 340. The home automation components 315, 320, 325, 330, 340 can be communicatively coupled with the home automation controller 310. The home automation controller 310 can control and configure the storage devices on each home automation component (315, 320, 325, 330, 340).
Data file 350 can be any data file used or generated on computing device 305. For example, data file 350 can be a word processing document (e.g., test.doc), an image file (e.g., image.jpg or image.gif), a video file (e.g., video.mp4), or any other file used on computing device 305. Data file 350 can be a single file or multiple files. Data file 350 can be encrypted at computing device 305, at home automation controller 310, or not at all. In some embodiments, data file 350 can be split into data segments 355, 360, and 365. Data segments can be equal sized segments of data file 350 or unequal sized segments. For example, if data file 350 is a 15 kB file, data segment 355 can include 5 kB of data from data file 350. Similarly, data segments 360 and 365 can also each include 5 kB of data from data file 350. Data segments 355, 360, and 365 can also include header file information or other overhead data necessary for identifying the data segment. In some embodiments, the data segments can be differing sized segments. For example, if data file 350 is a 15 kB file, data segment 355 can include 3 kB of data from data file 350, data segment 360 can include 10 kB of data from data file 350, and data segment 365 can include 2 kB of data from data file 350. The size of the data segment can depend on, for example, the number of segments the home automation controller 310 splits data file 350 into. While shown split into 3 data segments in
Home automation data storage system 300 can be used to store data from computing device 305. Computing device 305 can include a storage device and use the home automation data storage system 300 as backup storage or, in some embodiments, computing device 305 can use the home automation data storage system 300 as its primary storage device. When the home automation data storage system 300 is used as the primary storage for computing device 305, the theft or loss of computing device 305 need not result in the theft or loss of the data stored on the home automation data storage system 300. In some embodiments, the computing device 305 can include a storage device, yet still use the home automation data storage system 300 as its primary storage device.
In use, a user can develop data file 350. Once the data file 350 is to be saved (or backed up), computing device 305 can transmit the data file 350 over communication link A to home automation controller 310. The home automation controller 310 can split the data file 310 into one or more data segments 355, 360, and 365. In some embodiments, a data file 350 can be stored on a storage device without being split into data segments. In such embodiments, the data file 350 is stored as a single file on a storage device of a home automation component.
Once the data file 350 is split into data segments 355, 360, and 365, the data segments can be transmitted over communication links to the storage device associated with a home automation component. For example, as shown in
Additionally, as noted by the bi-directional arrows in
In some embodiments, security can be a function of the home automation data storage system 300. For example, access to data stored within the home automation data storage system 300 can be limited to devices that are connected to the home automation data storage network. Physical proximity, for example, can provide some security. In some embodiments, connection to the home automation data storage network can be provided utilizing, for example, a Bluetooth pairing operation performed between the home automation controller 310 and the computing device 305. In some embodiments, the computing device 305 can be added to the home automation data storage network by accessing a user interface on the home automation controller 310 that allows the addition of the computing device 305 using a unique ID, a username and password, or some other authentication method. The user interface can be an interface as described above with respect to
Controller database 410 can be stored on any suitable data storage device. In some embodiments, controller database 410 can be incorporated with home automation settings database 247 (
For example, as shown in
At 510, a home automation controller, such as home automation controller 310, can receive a data file from a computing device. The computing device can be any computing device, such as, for example, computing device 305 as described in
At 520, the home automation controller can store at least a portion of the data file to a storage device of a home automation component. The home automation component can be from home automation system that includes multiple components. The components can be home automation components as described above with respect to
At 530, the home automation controller can store information associating the portion of the data file with the storage device of the component. The information can be stored in, for example, a controller database, such as the controller database 410 of
At 610, the home automation controller can split the data file into a plurality of data segments. Because the data file may not be stored on a single storage device, the home automation controller can split the data file into segments. There are multiple reasons for storing the data file across multiple storage devices. For example, the storage on some devices may not be large enough to accommodate the complete storage file. As another example, the home automation data storage system owner may prefer a configuration that is similar to a Redundant Array of Independent Disks (“RAID”) to provide redundancy and/or rebuilding capability.
At 620, the home automation controller can store a first data segment from the plurality of data segments that the data file was split into to a first home automation component. For example, as shown in
At 630, the home automation component can store a second data segment from the plurality of data segments that the data file was split into to a second home automation component. This can be done similarly to storing the first data segment described at 620.
In some embodiments, a home automation component can fail or be removed from the overall home automation system.
At 710, the home automation controller can determine that the home automation component was removed from the home automation data storage system. As mentioned above, there can be several reasons for a home automation component to be removed from the system. If, for example, the component is a light bulb, the light bulb can burn out. That type of failure would typically result in that component being replaced with a new light bulb. Another reason the component can be removed is simply because the component is no longer needed in the system. For example, if the homeowner determines that a security camera is no longer desired within the house, the security camera can be removed from the system. Or, perhaps a newer model security camera can replace the old security camera. Additionally, as another example, a component (such as a smoke detector) can be removed to replace a battery. After replacement of the battery, the component can be reinserted into the system. In any of these scenarios, an existing home automation component in the system can be removed, and the associated storage device containing any data is also removed. When the home automation controller determines that a component is gone from the system, the component can be marked as removed in, for example, the controller database.
In some embodiments, when a home automation component is failing, the component can intermittently work. In such embodiments, if the home automation controller detects that the component works only intermittently, the home automation controller can mark the component as unreliable and not use the component's storage device. In some embodiments, a home automation component can be temporarily removed from the home automation data storage system to, for example, replace a battery. In some embodiments, the home automation controller can determine that the component is unreliable after it is missing from the system for a certain period of time and at that point mark the component as removed, missing, or unreliable. In some embodiments, for example, a missing delay timer can be configured to allow for a certain amount of time the component has to be missing from the system before it is marked as unreliable, missing, or removed. In some embodiments, the missing delay time can be configured based on the type of component. For example, a light bulb may have a very short period of time before being marked as missing (because once burned out the light bulb is no good) while a smoke detector can be missing for a longer period of time before being marked as missing (because a user might remove it to replace a battery). Settings such as a missing delay timer can be configured automatically by the home automation controller or can be configured through the user interface.
In some embodiments, the storage device can be a removable card, such as for example an SD card. In such embodiments, if the home automation component fails and is replaced, the SD card can be inserted into the replacement component, maintaining the data in the system. In such embodiments, if the home automation controller had marked the component unreliable, missing, or removed, as discussed above, the homeowner or administrator of the system can utilize a user interface to override the designation on the home automation component within the system. Such designation can be stored in the controller database, for example.
In some embodiments, when the home automation component is intended to be removed and replaced, such as for example, when the component is being upgraded, the homeowner or administrator of the system can utilize the user interface to prepare the system for removal of the component. In such embodiments, the home automation controller can, for example, temporarily copy the information from the component that will be removed from the system. In such embodiments, when the replacement component is added to the system, the home automation controller can utilize the space on the replacement component or any other available space on the system. If the component is to be removed without replacement, the home automation controller can relocate the data stored on the component to be removed to the storage device of a different component. In some embodiments, if the component is intermittently working, the home automation controller can also move the data before the component completely fails.
At 720, the home automation controller can identify the portion of the data file stored on the storage device of the component. As described with respect to
At 730, the home automation controller can rebuild the portion of the data file on the storage device of a different home automation component. The home automation controller can identify another home automation component storage device for storing the portion of the data file that was stored on the storage device of the component that was removed from the system. The home automation controller can rebuild the portion of the data file using any number of rebuilding techniques. For example, in some embodiments, a RAID-type configuration can be used with the available storage devices. In such embodiments, the portion of the file that was stored on the removed home automation component can also be stored on a second home automation component. The home automation controller can retrieve the data from the mirrored location and make a copy and place it in the storage device of a different home automation component.
In identifying the different home automation component for storing the data on at 730, the home automation controller can, for example, identify available space on any existing home automation component in the system. In some embodiments, a new home automation component will be added to the system to replace the removed home automation component. In such embodiments, the home automation controller can utilize the storage device on the new home automation component for storing the portion of the data file.
In some embodiments, the home automation controller can automatically begin the rebuild process to recover the data that was removed from the system. In such embodiments, the rebuilding can automatically occur after the home automation controller determines that the home automation component that had stored the data in its storage device is, for example, removed, missing, or unreliable. As discussed above, the designation of missing, removed, or unreliable can be made after a certain amount of time or immediately. In some embodiments in which the homeowner or administrator intentionally removes the device utilizing the user interface, the system can respond accordingly based on the entries into the user interface. In some embodiments, the home automation controller can notify the homeowner or administrator of the system that a component has failed. In some embodiments, the home automation controller can allow the homeowner or administrator to begin the rebuild process rather than launching the rebuild process automatically. When the homeowner or administrator is allowed to begin the rebuild process, the homeowner or administrator can be given options for specifying where the rebuilt data can be located, for example.
At 810, the home automation controller, such as home automation controller 310, can receive a request for a data file from a computing device, such as computing device 305. The request can be a result of using the home automation data storage system as the primary storage for the computing device or as a request to retrieve data from the backup.
At 820, the home automation controller can retrieve a first data segment from the storage device of a first home automation component. Prior to retrieving the data segment, the home automation controller may utilize a controller database, such as controller database 410 as described with respect to
At 830, the home automation controller can retrieve a second data segment from the storage device of a second home automation component, similar to retrieving the first data segment at 820. This process can continue as many times as necessary to obtain all the data segments of the data file.
At 840, the home automation controller can combine the data segments to regenerate the data file. In some embodiments, the entire data file can be stored on a single home automation component and, therefore, regeneration may not be needed. Once the data file is regenerated, at 850, the home automation controller can transmit the data file to the computing device.
The computer system 900 is shown comprising hardware elements that can be electrically coupled via a bus 905, or may otherwise be in communication, as appropriate. The hardware elements may include one or more processors 910, including without limitation one or more general-purpose processors and/or one or more special-purpose processors such as digital signal processing chips, graphics acceleration processors, and/or the like; one or more input devices 915, which can include without limitation a mouse, a keyboard, a camera, and/or the like; and one or more output devices 920, which can include without limitation a display device, a printer, and/or the like.
The computer system 900 may further include and/or be in communication with one or more non-transitory storage devices 925, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
The computer system 900 might also include a communications subsystem 930, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc., and/or the like. The communications subsystem 930 may include one or more input and/or output communication interfaces to permit data to be exchanged with a network such as the network described below to name one example, other computer systems, television, and/or any other devices described herein. Depending on the desired functionality and/or other implementation concerns, a portable electronic device or similar device may communicate image and/or other information via the communications subsystem 930. In other embodiments, a portable electronic device, e.g. the first electronic device, may be incorporated into the computer system 900, e.g., an electronic device or STB, as an input device 915. In many embodiments, the computer system 900 will further comprise a working memory 935, which can include a RAM or ROM device, as described above.
The computer system 900 also can include software elements, shown as being currently located within the working memory 935, including an operating system 940, device drivers, executable libraries, and/or other code, such as one or more application programs 945, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the methods discussed above, such as those described in relation to
A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 925 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 900. In other embodiments, the storage medium might be separate from a computer system e.g., a removable medium, such as a compact disc, and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system 900 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 900 e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc., then takes the form of executable code.
It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software including portable software, such as applets, etc., or both. Further, connection to other computing devices such as network input/output devices may be employed.
As mentioned above, in one aspect, some embodiments may employ a computer system such as the computer system 900 to perform methods in accordance with various embodiments of the technology. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 900 in response to processor 910 executing one or more sequences of one or more instructions, which might be incorporated into the operating system 940 and/or other code, such as an application program 945, contained in the working memory 935. Such instructions may be read into the working memory 935 from another computer-readable medium, such as one or more of the storage device(s) 925. Merely by way of example, execution of the sequences of instructions contained in the working memory 935 might cause the processor(s) 910 to perform one or more procedures of the methods described herein. Additionally or alternatively, portions of the methods described herein may be executed through specialized hardware.
The terms “machine-readable medium” and “computer-readable medium,” as used herein, refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer system 900, various computer-readable media might be involved in providing instructions/code to processor(s) 910 for execution and/or might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take the form of a non-volatile media or volatile media. Non-volatile media include, for example, optical and/or magnetic disks, such as the storage device(s) 925. Volatile media include, without limitation, dynamic memory, such as the working memory 935.
Common forms of physical and/or tangible computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.
Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 910 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system 900.
The communications subsystem 930 and/or components thereof generally will receive signals, and the bus 905 then might carry the signals and/or the data, instructions, etc. carried by the signals to the working memory 935, from which the processor(s) 910 retrieves and executes the instructions. The instructions received by the working memory 935 may optionally be stored on a non-transitory storage device 925 either before or after execution by the processor(s) 910.
The methods, systems, and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or components as appropriate. For instance, in alternative configurations, the methods may be performed in an order different from that described, and/or various stages may be added, omitted, and/or combined. Also, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves and, thus, many of the elements are examples and do not limit the scope of the disclosure or claims.
Specific details are given in the description to provide a thorough understanding of exemplary configurations including implementations. However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the configurations. This description provides example configurations only, and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations will provide those skilled in the art with an enabling description for implementing described techniques. Various changes may be made in the function and arrangement of elements without departing from the spirit or scope of the disclosure.
Also, configurations may be described as a process which is depicted as a flow diagram or block diagram. Although each may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure. Furthermore, examples of the methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. Processors may perform the described tasks.
Having described several example configurations, various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the technology. Also, a number of steps may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not bind the scope of the claims.
As used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise. Thus, for example, reference to “a user” includes a plurality of such users, and reference to “the processor” includes reference to one or more processors and equivalents thereof known to those skilled in the art, and so forth.
Also, the words “comprise”, “comprising”, “contains”, “containing”, “include”, “including”, and “includes”, when used in this specification and in the following claims, are intended to specify the presence of stated features, integers, components, or steps, but they do not preclude the presence or addition of one or more other features, integers, components, steps, acts, or groups.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3803575 | Gotanda | Apr 1974 | A |
| 4127966 | Schmidt | Dec 1978 | A |
| 4386436 | Kocher et al. | May 1983 | A |
| 4581606 | Mallory | Apr 1986 | A |
| 4694607 | Ishida et al. | Sep 1987 | A |
| 4728949 | Platte et al. | Mar 1988 | A |
| 4959713 | Morotomi et al. | Sep 1990 | A |
| 5400246 | Wilson et al. | Mar 1995 | A |
| 5770896 | Nakajima | Jun 1998 | A |
| 5805442 | Crater et al. | Sep 1998 | A |
| 5822012 | Jeon et al. | Oct 1998 | A |
| 5886638 | Tanguay | Mar 1999 | A |
| 5894331 | Yang | Apr 1999 | A |
| 5926090 | Taylor et al. | Jul 1999 | A |
| 5970030 | Dimitri et al. | Oct 1999 | A |
| 6081758 | Parvulescu | Jun 2000 | A |
| 6104334 | Allport | Aug 2000 | A |
| 6107918 | Klein et al. | Aug 2000 | A |
| 6107935 | Comerford et al. | Aug 2000 | A |
| 6111517 | Atick et al. | Aug 2000 | A |
| 6119088 | Ciluffo | Sep 2000 | A |
| 6142913 | Ewert | Nov 2000 | A |
| 6182094 | Humpleman et al. | Jan 2001 | B1 |
| 6225938 | Hayes et al. | May 2001 | B1 |
| 6286764 | Garvey et al. | Sep 2001 | B1 |
| 6330621 | Bakke et al. | Dec 2001 | B1 |
| 6337899 | Alcendor et al. | Jan 2002 | B1 |
| 6377858 | Koeppe | Apr 2002 | B1 |
| 6405284 | Bridge | Jun 2002 | B1 |
| 6415257 | Jungua et al. | Jul 2002 | B1 |
| 6445287 | Schofield et al. | Sep 2002 | B1 |
| 6502166 | Cassidy | Dec 2002 | B1 |
| 6529230 | Chong | Mar 2003 | B1 |
| 6543051 | Manson et al. | Apr 2003 | B1 |
| 6553375 | Huang et al. | Apr 2003 | B1 |
| 6663375 | Huang et al. | Aug 2003 | B1 |
| 6646676 | DaGraca et al. | Nov 2003 | B1 |
| 6662282 | Cochran | Dec 2003 | B2 |
| 6744771 | Barber et al. | Jun 2004 | B1 |
| 6748343 | Alexander et al. | Jun 2004 | B2 |
| 6751657 | Zothner | Jun 2004 | B1 |
| 6756998 | Bilger | Jun 2004 | B1 |
| 6792319 | Bilger | Sep 2004 | B1 |
| 6876889 | Lortz et al. | Apr 2005 | B1 |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6931104 | Foster et al. | Aug 2005 | B1 |
| 6976187 | Arnott et al. | Dec 2005 | B2 |
| 6989731 | Kawai et al. | Jan 2006 | B1 |
| 7009528 | Griep | Mar 2006 | B2 |
| 7010332 | Irvin et al. | Mar 2006 | B1 |
| 7081830 | Shimba | Jul 2006 | B2 |
| 7082359 | Breed | Jul 2006 | B2 |
| 7088238 | Karaoguz et al. | Aug 2006 | B2 |
| 7103545 | Furuta | Sep 2006 | B2 |
| 7143298 | Wells et al. | Nov 2006 | B2 |
| 7216002 | Anderson | May 2007 | B1 |
| 7234074 | Cohn et al. | Jun 2007 | B2 |
| 7260538 | Calderone et al. | Aug 2007 | B2 |
| 7346917 | Gatto et al. | Mar 2008 | B2 |
| 7372370 | Stults et al. | May 2008 | B2 |
| 7386666 | Beauchamp et al. | Jun 2008 | B1 |
| 7391319 | Walker | Jun 2008 | B1 |
| 7395369 | Sepez et al. | Jul 2008 | B2 |
| 7395546 | Asmussen | Jul 2008 | B1 |
| 7529677 | Wittenberg | May 2009 | B1 |
| 7574494 | Mayernick et al. | Aug 2009 | B1 |
| 7579945 | Richter et al. | Aug 2009 | B1 |
| 7590703 | Cashman et al. | Sep 2009 | B2 |
| 7640351 | Reckamp et al. | Dec 2009 | B2 |
| 7659814 | Chen et al. | Feb 2010 | B2 |
| 7694005 | Reckamp et al. | Apr 2010 | B2 |
| 7739718 | Young et al. | Jun 2010 | B1 |
| 7861034 | Yamamoto et al. | Dec 2010 | B2 |
| 7870232 | Reckamp et al. | Jan 2011 | B2 |
| 7945297 | Phillip | May 2011 | B2 |
| 7969318 | White et al. | Jun 2011 | B2 |
| 8013730 | Oh et al. | Sep 2011 | B2 |
| 8042048 | Wilson et al. | Oct 2011 | B2 |
| 8086757 | Chang | Dec 2011 | B2 |
| 8106768 | Neumann | Jan 2012 | B2 |
| 8156368 | Chambliss et al. | Apr 2012 | B2 |
| 8171148 | Lucas et al. | Apr 2012 | B2 |
| 8179248 | Eakle, Jr. | May 2012 | B2 |
| 8180735 | Ansari et al. | May 2012 | B2 |
| 8201261 | Barfield et al. | Jun 2012 | B2 |
| 8221290 | Vincent et al. | Jul 2012 | B2 |
| 8275143 | Johnson | Sep 2012 | B2 |
| 8289157 | Patenaude et al. | Oct 2012 | B2 |
| 8290545 | Terlizzi | Oct 2012 | B2 |
| 8310335 | Sivakkolundhu | Nov 2012 | B2 |
| 8316413 | Crabtree | Nov 2012 | B2 |
| 8320578 | Kahn et al. | Nov 2012 | B2 |
| 8335312 | Gerhardt et al. | Dec 2012 | B2 |
| 8350694 | Trundle et al. | Jan 2013 | B1 |
| 8355886 | Ollivier et al. | Jan 2013 | B2 |
| 8413204 | White et al. | Apr 2013 | B2 |
| 8436902 | Kuehnle | May 2013 | B2 |
| 8498572 | Schooley et al. | Jul 2013 | B1 |
| 8516087 | Wilson et al. | Aug 2013 | B2 |
| 8533144 | Reeser | Sep 2013 | B1 |
| 8539567 | Logue et al. | Sep 2013 | B1 |
| 8550368 | Butler et al. | Oct 2013 | B2 |
| 8619136 | Howarter et al. | Dec 2013 | B2 |
| 8620841 | Filson et al. | Dec 2013 | B1 |
| 8644525 | Bathurst et al. | Feb 2014 | B2 |
| 8645327 | Falkenburg et al. | Feb 2014 | B2 |
| 8667529 | Taxier | Mar 2014 | B2 |
| 8750576 | Huang et al. | Jun 2014 | B2 |
| 8780201 | Scalisi et al. | Jul 2014 | B1 |
| 8781508 | Blakely | Jul 2014 | B1 |
| 8786698 | Chen et al. | Jul 2014 | B2 |
| 8799413 | Taylor et al. | Aug 2014 | B2 |
| 8818898 | Schlossberg et al. | Aug 2014 | B2 |
| 8898709 | Crabtree | Nov 2014 | B2 |
| 8923823 | Wilde | Dec 2014 | B1 |
| 8930700 | Wielopolski | Jan 2015 | B2 |
| 8948793 | Birkhold et al. | Feb 2015 | B1 |
| 8965170 | Benea et al. | Feb 2015 | B1 |
| 9019111 | Sloo et al. | Apr 2015 | B1 |
| 9049567 | Le Guen et al. | Jun 2015 | B2 |
| 9191804 | Paczkowski et al. | Nov 2015 | B1 |
| 9237141 | Logue et al. | Jan 2016 | B2 |
| 9246921 | Vlaminck et al. | Jan 2016 | B1 |
| 9258593 | Chen et al. | Feb 2016 | B1 |
| 9286482 | Dumont et al. | Mar 2016 | B1 |
| 9338054 | Russell | May 2016 | B2 |
| 9347242 | Cregg et al. | May 2016 | B2 |
| 9353500 | Andreski | May 2016 | B1 |
| 9443142 | Reynolds, Jr. | Sep 2016 | B2 |
| 9462041 | Hagins et al. | Oct 2016 | B1 |
| 9495860 | Lett | Nov 2016 | B2 |
| 9511259 | Mountain | Dec 2016 | B2 |
| 9589448 | Schneider et al. | Mar 2017 | B1 |
| 9599981 | Crabtree | Mar 2017 | B2 |
| 9621959 | Mountain | Apr 2017 | B2 |
| 9628286 | Nguyen et al. | Apr 2017 | B1 |
| 9632746 | Keipert et al. | Apr 2017 | B2 |
| 9633186 | Ingrassia, Jr. et al. | Apr 2017 | B2 |
| 9729989 | Marten | Aug 2017 | B2 |
| 9769522 | Richardson | Sep 2017 | B2 |
| 9772612 | McCarthy et al. | Sep 2017 | B2 |
| 9798309 | Tirpak | Oct 2017 | B2 |
| 9824578 | Burton et al. | Nov 2017 | B2 |
| 9835434 | Sloo | Dec 2017 | B1 |
| 9838736 | Smith et al. | Dec 2017 | B2 |
| 9882736 | Lett | Jan 2018 | B2 |
| 9888129 | Russell | Feb 2018 | B2 |
| 9900177 | Holley | Feb 2018 | B2 |
| 9912492 | McCarthy et al. | Mar 2018 | B2 |
| 9967614 | McCarthy | May 2018 | B2 |
| 9977587 | Mountain | May 2018 | B2 |
| 9983011 | Mountain | May 2018 | B2 |
| 9989507 | Benn | Jun 2018 | B2 |
| 20010012998 | Jouet et al. | Aug 2001 | A1 |
| 20020003493 | Durst et al. | Jan 2002 | A1 |
| 20020019725 | Petite | Feb 2002 | A1 |
| 20020063633 | Park | May 2002 | A1 |
| 20020080238 | Ohmura | Jun 2002 | A1 |
| 20020193989 | Geilhufe et al. | Dec 2002 | A1 |
| 20030005431 | Shinohara | Jan 2003 | A1 |
| 20030052789 | Colmenarez et al. | Mar 2003 | A1 |
| 20030097452 | Kim et al. | May 2003 | A1 |
| 20030126593 | Mault | Jul 2003 | A1 |
| 20030133551 | Kahn | Jul 2003 | A1 |
| 20030140352 | Kim | Jul 2003 | A1 |
| 20030154242 | Hayes et al. | Aug 2003 | A1 |
| 20030192600 | Ford | Oct 2003 | A1 |
| 20030201900 | Bachinski et al. | Oct 2003 | A1 |
| 20040019489 | Funk et al. | Jan 2004 | A1 |
| 20040036579 | Megerle | Feb 2004 | A1 |
| 20040117038 | Karaoguz et al. | Jun 2004 | A1 |
| 20040117843 | Karaoguz et al. | Jun 2004 | A1 |
| 20040121725 | Matsui | Jun 2004 | A1 |
| 20040128034 | Lenker et al. | Jul 2004 | A1 |
| 20040143838 | Rose | Jul 2004 | A1 |
| 20040148419 | Chen et al. | Jul 2004 | A1 |
| 20040148632 | Park et al. | Jul 2004 | A1 |
| 20040260407 | Wimsatt | Dec 2004 | A1 |
| 20040266419 | Arling et al. | Dec 2004 | A1 |
| 20050038875 | Park | Feb 2005 | A1 |
| 20050049862 | Choi et al. | Mar 2005 | A1 |
| 20050106267 | Frykman et al. | May 2005 | A1 |
| 20050159823 | Hayes et al. | Jul 2005 | A1 |
| 20050166065 | Eytchison et al. | Jul 2005 | A1 |
| 20050188315 | Campbell et al. | Aug 2005 | A1 |
| 20050200478 | Koch et al. | Sep 2005 | A1 |
| 20050245292 | Bennett et al. | Nov 2005 | A1 |
| 20050252622 | Reid | Nov 2005 | A1 |
| 20050264698 | Eshleman | Dec 2005 | A1 |
| 20050289614 | Baek et al. | Dec 2005 | A1 |
| 20060011145 | Kates | Jan 2006 | A1 |
| 20060059977 | Kates | Mar 2006 | A1 |
| 20060087428 | Wolfe et al. | Apr 2006 | A1 |
| 20060115156 | Nakajima et al. | Jun 2006 | A1 |
| 20060136968 | Han et al. | Jun 2006 | A1 |
| 20060143679 | Yamada et al. | Jun 2006 | A1 |
| 20060155389 | Pessolano et al. | Jul 2006 | A1 |
| 20060186740 | Von Gunten | Aug 2006 | A1 |
| 20060192680 | Scuka et al. | Aug 2006 | A1 |
| 20060244624 | Wang et al. | Nov 2006 | A1 |
| 20060253894 | Bookman et al. | Nov 2006 | A1 |
| 20070044119 | Sullivan et al. | Feb 2007 | A1 |
| 20070078910 | Bopardikar | Apr 2007 | A1 |
| 20070129220 | Bardha | Jun 2007 | A1 |
| 20070135225 | Nieminen et al. | Jun 2007 | A1 |
| 20070142022 | Madonna et al. | Jun 2007 | A1 |
| 20070146545 | Iwahashi | Jun 2007 | A1 |
| 20070150460 | Evans | Jun 2007 | A1 |
| 20070157258 | Jung et al. | Jul 2007 | A1 |
| 20070192486 | Wilson et al. | Aug 2007 | A1 |
| 20070194922 | Nathan et al. | Aug 2007 | A1 |
| 20070256085 | Reckamp et al. | Nov 2007 | A1 |
| 20070271518 | Tischer et al. | Nov 2007 | A1 |
| 20070275670 | Chen et al. | Nov 2007 | A1 |
| 20070279244 | Haughawout et al. | Dec 2007 | A1 |
| 20070280504 | Badawy et al. | Dec 2007 | A1 |
| 20080019392 | Lee | Jan 2008 | A1 |
| 20080021971 | Halgas | Jan 2008 | A1 |
| 20080022322 | Grannan et al. | Jan 2008 | A1 |
| 20080046930 | Smith et al. | Feb 2008 | A1 |
| 20080062258 | Bentkovski et al. | Mar 2008 | A1 |
| 20080062965 | Silva et al. | Mar 2008 | A1 |
| 20080092199 | McCarthy et al. | Apr 2008 | A1 |
| 20080109095 | Braithwaite et al. | May 2008 | A1 |
| 20080114963 | Cannon et al. | May 2008 | A1 |
| 20080120639 | Walter et al. | May 2008 | A1 |
| 20080123825 | Abramson et al. | May 2008 | A1 |
| 20080140736 | Jarno | Jun 2008 | A1 |
| 20080144884 | Habibi | Jun 2008 | A1 |
| 20080163330 | Sparrell | Jul 2008 | A1 |
| 20080179053 | Kates | Jul 2008 | A1 |
| 20080236214 | Han | Oct 2008 | A1 |
| 20080278635 | Hardacker et al. | Nov 2008 | A1 |
| 20080284905 | Chuang | Nov 2008 | A1 |
| 20080288876 | Fleming | Nov 2008 | A1 |
| 20080297660 | Shioya | Dec 2008 | A1 |
| 20090023554 | Shim | Jan 2009 | A1 |
| 20090027225 | Farley | Jan 2009 | A1 |
| 20090033505 | Jones et al. | Feb 2009 | A1 |
| 20090040013 | Ebrom et al. | Feb 2009 | A1 |
| 20090066320 | Posey | Mar 2009 | A1 |
| 20090069038 | Olague et al. | Mar 2009 | A1 |
| 20090083374 | Saint Clair | Mar 2009 | A1 |
| 20090112541 | Anderson et al. | Apr 2009 | A1 |
| 20090138507 | Burckart et al. | May 2009 | A1 |
| 20090146834 | Huang | Jun 2009 | A1 |
| 20090165069 | Kirchner | Jun 2009 | A1 |
| 20090167555 | Kohanek | Jul 2009 | A1 |
| 20090190040 | Watanabe et al. | Jul 2009 | A1 |
| 20090235992 | Armstrong | Sep 2009 | A1 |
| 20090249428 | White et al. | Oct 2009 | A1 |
| 20090270065 | Hamada et al. | Oct 2009 | A1 |
| 20090271203 | Resch et al. | Oct 2009 | A1 |
| 20090286654 | Rice | Nov 2009 | A1 |
| 20090307715 | Santamaria et al. | Dec 2009 | A1 |
| 20100031286 | Gupta et al. | Feb 2010 | A1 |
| 20100045471 | Meyers | Feb 2010 | A1 |
| 20100046918 | Takao et al. | Feb 2010 | A1 |
| 20100066507 | Myllymaki | Mar 2010 | A1 |
| 20100083371 | Bennetts et al. | Apr 2010 | A1 |
| 20100097225 | Petricoin, Jr. | Apr 2010 | A1 |
| 20100102082 | Ebrom et al. | Apr 2010 | A1 |
| 20100122284 | Yoon et al. | May 2010 | A1 |
| 20100131280 | Bogineni | May 2010 | A1 |
| 20100138007 | Clark et al. | Jun 2010 | A1 |
| 20100138858 | Velazquez et al. | Jun 2010 | A1 |
| 20100146445 | Kraut | Jun 2010 | A1 |
| 20100161082 | Ebrom et al. | Jun 2010 | A1 |
| 20100164732 | Wedig et al. | Jul 2010 | A1 |
| 20100211546 | Grohman et al. | Aug 2010 | A1 |
| 20100277300 | Cohn et al. | Nov 2010 | A1 |
| 20100283579 | Kraus et al. | Nov 2010 | A1 |
| 20100309004 | Grundler et al. | Dec 2010 | A1 |
| 20100321151 | Matsuura et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110018693 | Lim et al. | Jan 2011 | A1 |
| 20110030016 | Pino, Jr. et al. | Feb 2011 | A1 |
| 20110032423 | Jing et al. | Feb 2011 | A1 |
| 20110093126 | Toba et al. | Apr 2011 | A1 |
| 20110119325 | Paul et al. | May 2011 | A1 |
| 20110139076 | Pu et al. | Jun 2011 | A1 |
| 20110140832 | Vinkenvleugel et al. | Jun 2011 | A1 |
| 20110150432 | Paul et al. | Jun 2011 | A1 |
| 20110156862 | Langer | Jun 2011 | A1 |
| 20110157468 | Dai | Jun 2011 | A1 |
| 20110167250 | Dicks et al. | Jul 2011 | A1 |
| 20110187928 | Crabtree | Aug 2011 | A1 |
| 20110187930 | Crabtree | Aug 2011 | A1 |
| 20110187931 | Kim | Aug 2011 | A1 |
| 20110202956 | Connelly et al. | Aug 2011 | A1 |
| 20110267180 | Ferringo et al. | Nov 2011 | A1 |
| 20110270549 | Jeansonne et al. | Nov 2011 | A1 |
| 20110282837 | Gounares et al. | Nov 2011 | A1 |
| 20110283311 | Luong | Nov 2011 | A1 |
| 20110285528 | Weinstein et al. | Nov 2011 | A1 |
| 20110295396 | Chinen et al. | Dec 2011 | A1 |
| 20110296463 | Suslov | Dec 2011 | A1 |
| 20120019388 | Kates | Jan 2012 | A1 |
| 20120047083 | Qiao et al. | Feb 2012 | A1 |
| 20120047532 | McCarthy | Feb 2012 | A1 |
| 20120059495 | Weiss et al. | Mar 2012 | A1 |
| 20120069246 | Thornberry et al. | Mar 2012 | A1 |
| 20120092183 | Corbett et al. | Apr 2012 | A1 |
| 20120094696 | Ahn et al. | Apr 2012 | A1 |
| 20120105724 | Candelore | May 2012 | A1 |
| 20120124245 | Reeves et al. | May 2012 | A1 |
| 20120124456 | Perez et al. | May 2012 | A1 |
| 20120124859 | May et al. | May 2012 | A1 |
| 20120154108 | Sugaya | Jun 2012 | A1 |
| 20120154138 | Cohn et al. | Jun 2012 | A1 |
| 20120164975 | Dodeja et al. | Jun 2012 | A1 |
| 20120167646 | Sharma et al. | Jul 2012 | A1 |
| 20120206269 | Wickman et al. | Aug 2012 | A1 |
| 20120226366 | Lee et al. | Sep 2012 | A1 |
| 20120226768 | Gaines et al. | Sep 2012 | A1 |
| 20120271472 | Brunner et al. | Oct 2012 | A1 |
| 20120271670 | Zaloom | Oct 2012 | A1 |
| 20120280802 | Yoshida et al. | Nov 2012 | A1 |
| 20120291068 | Khushoo et al. | Nov 2012 | A1 |
| 20120314713 | Singh et al. | Dec 2012 | A1 |
| 20120316876 | Jang et al. | Dec 2012 | A1 |
| 20120326835 | Cockrell et al. | Dec 2012 | A1 |
| 20130006400 | Caceres et al. | Jan 2013 | A1 |
| 20130013106 | Carelli et al. | Jan 2013 | A1 |
| 20130031037 | Brandt et al. | Jan 2013 | A1 |
| 20130046800 | Assi et al. | Feb 2013 | A1 |
| 20130049950 | Wohlert | Feb 2013 | A1 |
| 20130053063 | McSheffrey | Feb 2013 | A1 |
| 20130060358 | Li et al. | Mar 2013 | A1 |
| 20130070044 | Naidoo et al. | Mar 2013 | A1 |
| 20130074061 | Averbuch et al. | Mar 2013 | A1 |
| 20130090213 | Amini et al. | Apr 2013 | A1 |
| 20130120137 | Lehmann | May 2013 | A1 |
| 20130124192 | Lindmark et al. | May 2013 | A1 |
| 20130138757 | Ferron | May 2013 | A1 |
| 20130147604 | Jones, Jr. et al. | Jun 2013 | A1 |
| 20130152139 | Davis et al. | Jun 2013 | A1 |
| 20130158717 | Zywicki et al. | Jun 2013 | A1 |
| 20130166073 | Pine et al. | Jun 2013 | A1 |
| 20130179926 | White et al. | Jul 2013 | A1 |
| 20130185750 | Ayoub | Jul 2013 | A1 |
| 20130204408 | Thiruvengada et al. | Aug 2013 | A1 |
| 20130219482 | Brandt | Aug 2013 | A1 |
| 20130238326 | Kim et al. | Sep 2013 | A1 |
| 20130242074 | Sekiguchi et al. | Sep 2013 | A1 |
| 20130247117 | Yamada et al. | Sep 2013 | A1 |
| 20130249688 | Nguyen et al. | Sep 2013 | A1 |
| 20130267383 | Watterson | Oct 2013 | A1 |
| 20130278828 | Todd | Oct 2013 | A1 |
| 20130289788 | Gupta et al. | Oct 2013 | A1 |
| 20130300576 | Sinsuan et al. | Nov 2013 | A1 |
| 20130318559 | Crabtree | Nov 2013 | A1 |
| 20130321637 | Frank et al. | Dec 2013 | A1 |
| 20130324247 | Esaki et al. | Dec 2013 | A1 |
| 20130325150 | Bury | Dec 2013 | A1 |
| 20140022051 | Levien et al. | Jan 2014 | A1 |
| 20140025798 | Apte et al. | Jan 2014 | A1 |
| 20140028546 | Jeon et al. | Jan 2014 | A1 |
| 20140070959 | Bhargava et al. | Mar 2014 | A1 |
| 20140089671 | Logue et al. | Mar 2014 | A1 |
| 20140095684 | Nonaka et al. | Apr 2014 | A1 |
| 20140101465 | Wang et al. | Apr 2014 | A1 |
| 20140129006 | Chen et al. | May 2014 | A1 |
| 20140135993 | Kang et al. | May 2014 | A1 |
| 20140140575 | Wolf | May 2014 | A1 |
| 20140142724 | Park et al. | May 2014 | A1 |
| 20140160360 | Hsu et al. | Jun 2014 | A1 |
| 20140167969 | Wedig et al. | Jun 2014 | A1 |
| 20140168277 | Ashley et al. | Jun 2014 | A1 |
| 20140181855 | Fife et al. | Jun 2014 | A1 |
| 20140192197 | Hanko et al. | Jul 2014 | A1 |
| 20140192997 | Niu et al. | Jul 2014 | A1 |
| 20140201315 | Jacob et al. | Jul 2014 | A1 |
| 20140215505 | Balasubramanian et al. | Jul 2014 | A1 |
| 20140217905 | Clayton et al. | Aug 2014 | A1 |
| 20140218517 | Kim et al. | Aug 2014 | A1 |
| 20140222634 | Gordon et al. | Aug 2014 | A1 |
| 20140223548 | Wassingbo | Aug 2014 | A1 |
| 20140228062 | Rubowitz | Aug 2014 | A1 |
| 20140266669 | Fadell et al. | Sep 2014 | A1 |
| 20140266684 | Poder et al. | Sep 2014 | A1 |
| 20140282653 | Ariantaj et al. | Sep 2014 | A1 |
| 20140297001 | Silverman | Oct 2014 | A1 |
| 20140306833 | Ricci | Oct 2014 | A1 |
| 20140310075 | Ricci | Oct 2014 | A1 |
| 20140313014 | Huh et al. | Oct 2014 | A1 |
| 20140313032 | Sager et al. | Oct 2014 | A1 |
| 20140333529 | Kim et al. | Nov 2014 | A1 |
| 20140351832 | Cho et al. | Nov 2014 | A1 |
| 20140362201 | Nguyen et al. | Dec 2014 | A1 |
| 20140373074 | Hwang et al. | Dec 2014 | A1 |
| 20150008846 | Chen et al. | Jan 2015 | A1 |
| 20150015401 | Wedig et al. | Jan 2015 | A1 |
| 20150029096 | Ishihara | Jan 2015 | A1 |
| 20150054910 | Offen et al. | Feb 2015 | A1 |
| 20150061859 | Matsuoka et al. | Mar 2015 | A1 |
| 20150062343 | Hwang et al. | Mar 2015 | A1 |
| 20150066173 | Ellis et al. | Mar 2015 | A1 |
| 20150074259 | Ansari et al. | Mar 2015 | A1 |
| 20150082225 | Shearer | Mar 2015 | A1 |
| 20150084770 | Xiao et al. | Mar 2015 | A1 |
| 20150085184 | Vidal et al. | Mar 2015 | A1 |
| 20150097689 | Logue et al. | Apr 2015 | A1 |
| 20150100167 | Sloo et al. | Apr 2015 | A1 |
| 20150105880 | Slupik et al. | Apr 2015 | A1 |
| 20150106866 | Fujita | Apr 2015 | A1 |
| 20150113571 | Cholas et al. | Apr 2015 | A1 |
| 20150116113 | Caine et al. | Apr 2015 | A1 |
| 20150127712 | Fadell et al. | May 2015 | A1 |
| 20150131500 | Xie et al. | May 2015 | A1 |
| 20150137967 | Wedig et al. | May 2015 | A1 |
| 20150142991 | Zaloom | May 2015 | A1 |
| 20150143406 | Cho et al. | May 2015 | A1 |
| 20150143408 | Sallas | May 2015 | A1 |
| 20150145643 | Fadell et al. | May 2015 | A1 |
| 20150154850 | Fadell et al. | Jun 2015 | A1 |
| 20150156030 | Fadell et al. | Jun 2015 | A1 |
| 20150156031 | Fadell et al. | Jun 2015 | A1 |
| 20150156612 | Vemulapalli | Jun 2015 | A1 |
| 20150159401 | Patrick et al. | Jun 2015 | A1 |
| 20150160623 | Holley | Jun 2015 | A1 |
| 20150160634 | Smith et al. | Jun 2015 | A1 |
| 20150160635 | Schofield et al. | Jun 2015 | A1 |
| 20150160636 | McCarthy et al. | Jun 2015 | A1 |
| 20150160663 | McCarthy et al. | Jun 2015 | A1 |
| 20150160935 | Nye | Jun 2015 | A1 |
| 20150161452 | McCarthy et al. | Jun 2015 | A1 |
| 20150161882 | Lett | Jun 2015 | A1 |
| 20150162006 | Kummer | Jun 2015 | A1 |
| 20150163411 | McCarthy, III et al. | Jun 2015 | A1 |
| 20150163412 | Holley et al. | Jun 2015 | A1 |
| 20150163535 | McCarthy et al. | Jun 2015 | A1 |
| 20150172742 | Richardson | Jun 2015 | A1 |
| 20150180708 | Jacob et al. | Jun 2015 | A1 |
| 20150192914 | Slupik | Jul 2015 | A1 |
| 20150198941 | Pederson | Jul 2015 | A1 |
| 20150241860 | Raid | Aug 2015 | A1 |
| 20150260424 | Fadell et al. | Sep 2015 | A1 |
| 20150281824 | Nguyen et al. | Oct 2015 | A1 |
| 20150304689 | Warren | Oct 2015 | A1 |
| 20150309487 | Lyman | Oct 2015 | A1 |
| 20150325096 | Hatch | Nov 2015 | A1 |
| 20150334069 | Winston et al. | Nov 2015 | A1 |
| 20150341599 | Carey | Nov 2015 | A1 |
| 20150347910 | Fadell et al. | Dec 2015 | A1 |
| 20150365787 | Farrell | Dec 2015 | A1 |
| 20160029153 | Linn et al. | Jan 2016 | A1 |
| 20160041565 | Edwards | Feb 2016 | A1 |
| 20160047569 | Fadell et al. | Feb 2016 | A1 |
| 20160063854 | Burton et al. | Mar 2016 | A1 |
| 20160066046 | Mountain | Mar 2016 | A1 |
| 20160091471 | Benn | Mar 2016 | A1 |
| 20160098309 | Kim | Apr 2016 | A1 |
| 20160100696 | Palashewski et al. | Apr 2016 | A1 |
| 20160109864 | Lonn | Apr 2016 | A1 |
| 20160116914 | Mucci | Apr 2016 | A1 |
| 20160121161 | Mountain | May 2016 | A1 |
| 20160123741 | Mountain | May 2016 | A1 |
| 20160163168 | Brav et al. | Jun 2016 | A1 |
| 20160182249 | Lea | Jun 2016 | A1 |
| 20160189527 | Peterson et al. | Jun 2016 | A1 |
| 20160191912 | Lea et al. | Jun 2016 | A1 |
| 20160191990 | McCarthy | Jun 2016 | A1 |
| 20160195602 | Meadow | Jul 2016 | A1 |
| 20160195856 | Spero | Jul 2016 | A1 |
| 20160196731 | Aich et al. | Jul 2016 | A1 |
| 20160203700 | Bruhn et al. | Jul 2016 | A1 |
| 20160234034 | Mahar et al. | Aug 2016 | A1 |
| 20160248598 | Lin et al. | Aug 2016 | A1 |
| 20160256485 | Wager et al. | Sep 2016 | A1 |
| 20160260135 | Zomet et al. | Sep 2016 | A1 |
| 20160285644 | Lu et al. | Sep 2016 | A1 |
| 20160286327 | Marten | Sep 2016 | A1 |
| 20160323548 | Khot et al. | Nov 2016 | A1 |
| 20160334811 | Marten | Nov 2016 | A1 |
| 20160335423 | Beals | Nov 2016 | A1 |
| 20160338179 | Aliakseyeu et al. | Nov 2016 | A1 |
| 20160342379 | Keipert et al. | Nov 2016 | A1 |
| 20160366746 | van de Ven et al. | Dec 2016 | A1 |
| 20170005822 | Gao | Jan 2017 | A1 |
| 20170041886 | Baker et al. | Feb 2017 | A1 |
| 20170048476 | Freiin von Kapri et al. | Feb 2017 | A1 |
| 20170051925 | Stefanski et al. | Feb 2017 | A1 |
| 20170054615 | Wilson | Feb 2017 | A1 |
| 20170061750 | Eyring et al. | Mar 2017 | A1 |
| 20170065433 | Singh et al. | Mar 2017 | A1 |
| 20170082987 | Reddy et al. | Mar 2017 | A1 |
| 20170105190 | Logan et al. | Apr 2017 | A1 |
| 20170127124 | Wilson et al. | May 2017 | A9 |
| 20170146964 | Beals | May 2017 | A1 |
| 20170176961 | Tirpak | Jun 2017 | A1 |
| 20170187993 | Martch et al. | Jun 2017 | A1 |
| 20170191693 | Bruhn et al. | Jul 2017 | A1 |
| 20170191695 | Bruhn et al. | Jul 2017 | A1 |
| 20170195130 | Landow et al. | Jul 2017 | A1 |
| 20180027290 | Richardson | Jan 2018 | A1 |
| 20180038029 | Beals | Feb 2018 | A1 |
| 20180061158 | Greene | Mar 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 267 988 | Apr 1998 | CA |
| 702136 | May 2011 | CH |
| 105814555 | Jul 2016 | CN |
| 3707284 | Sep 1988 | DE |
| 4012253 | Apr 1991 | DE |
| 10 208 451 | Sep 2003 | DE |
| 10 2012 106 719 | Jan 2014 | DE |
| 720136 | Jul 1996 | EP |
| 743410 | Nov 1996 | EP |
| 2 736 027 | May 2014 | EP |
| 3 080 677 | Oct 2016 | EP |
| 3 080 710 | Oct 2016 | EP |
| 834856 | Dec 1938 | FR |
| 947943 | Jul 1949 | FR |
| 1445705 | Aug 1976 | GB |
| 2 304 952 | Mar 1997 | GB |
| 2008148016 | Jun 2008 | JP |
| 9320544 | Oct 1993 | WO |
| 2004068386 | Aug 2004 | WO |
| 2011095567 | Aug 2011 | WO |
| 2011149473 | Dec 2011 | WO |
| 2014068556 | May 2014 | WO |
| 2015179120 | Nov 2015 | WO |
| 2016034880 | Mar 2016 | WO |
| 2016066399 | May 2016 | WO |
| 2016066442 | May 2016 | WO |
| 2016182696 | Nov 2016 | WO |
| 2017116533 | Jul 2017 | WO |
| 2018039161 | Mar 2018 | WO |
| Entry |
|---|
| Notification of Publication of European Application No. 15763643.2 as EP 3189511 dated Jul. 12, 2017, 1 page. |
| Notification of Publication of Brazilian Application No. BR 11 2016 0112032 dated Aug. 8, 2017, 2 pages. |
| Notification of Publication of Brazilian Application No. BR 11 2016 010376 9 dated Aug. 8, 2017, 1 page. |
| Supplementary European Search Report for EP 14868928 dated Jul. 7, 2017, 11 pages. |
| Supplementary European Search Report for EP 14870507 dated Jun. 28, 2017, all pages. (Received in KTS FIP in Sep. 2017, all refs from SR already cited). |
| “Plug-In Carbon Monoxide & Natural Gas Alarm with Backup Battery Protection,” Universal Security Instruments, Inc. , 2011, 12 pages. |
| U.S. Appl. No. 14/553,763, filed Nov. 25, 2014 Preinterview first office action dated Oct. 6, 2017, all pages. |
| U.S. Appl. No. 14/584,075, filed Dec. 29, 2014, Final Rejection dated Sep. 9, 2017, all pages. |
| U.S. Appl. No. 14/952,580, filed Nov. 25, 2015, Non-Final Rejection dated Sep. 20, 2017, all pages. |
| U.S. Appl. No. 15/189,775, filed Jun. 22, 2016, Notice of Allowance dated Sep. 11, 2017, all pages. |
| U.S. Appl. No. 14/986,496, filed Dec. 31, 2015, Non-Final Rejection dated Sep. 26, 2017, all pages. |
| U.S. Appl. No. 14/710,331, filed May 12, 2015, Final Rejection dated Aug. 16, 2017, all pages. |
| Notification of Publication of European Application No. 162004220 as EP 3166308 dated May 10, 2017, 2 pages. |
| U.S. Appl. No. 14/567,765, filed Dec. 11, 2014, Notice of Allowance dated May 24, 2017, all pages. |
| U.S. Appl. No. 14/567,754, filed Dec. 11, 2014, Final Rejection dated May 26, 2017, all pages. |
| U.S. Appl. No. 14/567,770, filed Dec. 11, 2014, Final Rejection dated Jun. 1, 2017, all pages. |
| U.S. Appl. No. 14/476,377, filed Sep. 3, 2014, Notice of Allowance dated May 19, 2017, all pages. |
| U.S. Appl. No. 14/832,821, filed Aug. 21, 2015, Non-Final Rejection dated Apr. 24, 2017, all pages. |
| U.S. Appl. No. 14/981,501, filed Dec. 28, 2015, Preinterview first office action dated Apr. 20, 2017, all pages. |
| U.S. Appl. No. 14/709,791, filed May 12, 2015, Non Final Rejection dated May 31, 2017, all pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Notice of Allowance dated Nov. 8, 2016, all pages. |
| U.S. Appl. No. 14/567,765, filed Dec. 11, 2014, First Action interview dated Oct. 18, 2016, all pages. |
| U.S. Appl. No. 14/584,075, filed Dec. 29, 2014, Final Rejection dated Oct. 6, 2016, all pages. |
| U.S. Appl. No. 14/566,977, filed Dec. 11, 2014, Non Final Rejection dated Oct. 3, 2016, all pages. |
| U.S. Appl. No. 14/567,754, filed Dec. 11, 2014, Non Final Rejection dated Nov. 4, 2016, all pages. |
| U.S. Appl. No. 14/567,770, filed Dec. 11, 2014, Non Final Rejection dated Nov. 4, 2016, all pages. |
| U.S. Appl. No. 14/671,299, filed Mar. 27, 2015, Non Final Rejection dated Oct. 28, 2016, all pages. |
| U.S. Appl. No. 14/476,377, filed Sep. 3, 2014, Non-Final Rejection dated Nov. 7, 2016, all pages. |
| Office Action for EP14868928.4 dated Sep. 23, 2016, all pages. |
| International Preliminary Report on Patentability for PCT/US2016/028126 dated Nov. 14, 2017, all pages. |
| International Search Report and Written Opinion for PCT/US2017/047900 dated Nov. 24, 2017. |
| Ravindran, et al., “Information-centric Networking based Homenet,” 2013 IFIP/IEEE International Symposium on Integrated Network Management (IM 2013), Ghent, 2013, pp. 1102-1108. |
| Mantoro, et al., “Web-enabled Smart Home Using Wireless Node Infrastructure,” Proceedings of the 9th International Conference on Advances in Mobile Computing and Multimedia. ACM, 2011, pp. 72-79. |
| Shariqsuhail, et al., “Multi-Functional Secured Smart Home,” Advances in Computing, Communications and Informatics (ICACCI), 2016 International Conference on. IEEE, 2016, pp. 2629-2634. |
| U.S. Appl. No. 14/986,483, filed Dec. 31, 2015, Non-Final Rejection dated Dec. 1, 2017, all pages. |
| U.S. Appl. No. 14/832,821, filed Aug. 21, 2015, Notice of Allowance dated Dec. 18, 2017, all pages. |
| International Search Report and Written Opinion for PCT/US2016/028126 dated Jun. 3, 2016, all pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Non-Final Office Action dated Jun. 16, 2016, 30 pages. |
| U.S. Appl. No. 14/528,739, filed Oct. 30, 2014 Notice of Allowance dated Jun. 23, 2016, 34 pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014, Non-Final Rejection dated Jun. 17, 2016, 29 pages. |
| U.S. Appl. No. 14/710,331, filed May 12, 2015, Non-Final Rejection dated May 20, 2016, 42 pages. |
| International Search Report and Written Opinion for PCT/EP2011/051608 dated May 30, 2011, 13 pages. |
| International Preliminary Report on Patentability for PCT/EP2011/051608 dated Aug. 16, 2012, 8 pages. |
| International Search Report and Written Opinion for PCT/US2014/053876 dated Nov. 26, 2014, 8 pages. |
| International Search Report and Written Opinion for PCT/US2014/055441 dated Dec. 4, 2014, 10 pages. |
| International Search Report and Written Opinion for PCT/US2014/055476 dated Dec. 30, 2014, 10 pages. |
| Mexican Institute of Industrial Property Office Action dated Nov. 1, 2013, for Mex. Patent Appln No. MX/a/2012/008882 is not translated into English, 3 pages. |
| Mexican Institute of Industrial Property Notice of Allowance dated Feb. 10, 2014, for Mex. Patent Appln No. MX/a/2012/008882, 1 page. |
| U.S. Appl. No. 14/470,352, filed Aug. 27, 2014 Non Final Office Action dated Nov. 20, 2015, 28 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Office Action dated May 4, 2012, 15 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Final Office Action dated Oct. 10, 2012, 16 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Non-Final Office Action dated Apr. 1, 2013, 16 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Non-Final Office Action dated Oct. 15, 2013, 15 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Final Office Action dated Feb. 28, 2014, 17 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Non-Final Office Action dated Aug. 14, 2014, 18 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Non-Final Office Action dated Mar. 11, 2015, 35 pages. |
| U.S. Appl. No. 12/700,310, filed Feb. 4, 2010 Final Office Action dated Oct. 26, 2015, 19 pages. |
| U.S. Appl. No. 12/700,408, filed Feb. 4, 2010 Notice of Allowance dated Jul. 28, 2012, 8 pages. |
| U.S. Appl. No. 13/680,934, filed Nov. 19, 2012 Non-Final Office Action dated Oct. 2, 2013, 7 pages. |
| U.S. Appl. No. 13/680,934, filed Nov. 19, 2012 Final Office Action dated Feb. 10, 2014, 13 pages. |
| U.S. Appl. No. 13/680,934, filed Nov. 19, 2012 Notice of Allowance dated Apr. 30, 2014, 9 pages. |
| U.S. Appl. No. 13/680,934, filed Nov. 19, 2012 Notice of Allowance dated Jul. 25, 2014, 12 pages. |
| U.S. Appl. No. 14/107,132, filed Dec. 16, 2013 Non Final Office Action dated May 27, 2015, 26 pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014 Pre-Interview First Office Action dated Jul. 29, 2015, 20 pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014 Pre-Interview First Office Action dated Oct. 1, 2015, 10 pages. |
| Lamonica, M., “CES 2010 Preview: Green comes in many colors,” retrieved from CNET.com (http://ces.cnet.com/8301-31045_1-10420381-269.html), Dec. 22, 2009, 2 pages. |
| Author Unknown, “Voice Activated TV using the Amulet Remote for Media Center,” AmuletDevices.com, accessed on Jul. 14, 2014, 1 page. Retrieved from http://www.amuletdevices.com/index.php/Features/television.html. |
| Author Unknown, “App for Samsung Smart TV®,” Crestron Electronics, Inc., accessed on Jul. 14, 2014, 3 pages. Retrieved from http://www.crestron.com/products/smart tv television apps/. |
| Author Unknown, “AllJoyn Onboarding Service Frameworks,” Qualcomm Connected Experiences, Inc., accessed on Jul. 15, 2014, 9 pages. Retrieved from https://www.alljoyn.org. |
| Robbins, Gordon, Deputy Chief, “Addison Fire Department Access Control Installation,” 2006 International Fire Code, Section 1008.1.3.4, 4 pages. |
| “International Building Code Excerpts, Updated with recent code changes that impact electromagnetic locks,” Securitron, Assa Abloy, IBC/IFC 2007 Supplement and 2009, “Finally—some relief and clarification”, 2 pages.Retrieved from: www.securitron.com/Other/.../New_IBC-IFC_Code_Language.pdf. |
| “Do you want to know how to find water leaks? Use a Bravedo Water Alert Flow Monitor to find out!”, Bravedo.com, accessed Dec. 16, 2014, 10 pages. Retrieved from http://bravedo.com/. |
| “Flow Pulse®, Non-invasive clamp-on flow monitor for pipes,” Pulsar Process Measurement Ltd, accessed on Dec. 16, 2014, 2 pages.Retrieved from http://www.pulsar-pm.com/product-types/flow/flow-pulse.aspx. |
| “Acoustic/Ultrasound Ultrasonic Flowmeter Basics,” Questex Media Group LLC, accessed on Dec. 16, 2014, 4 pages. Retrieved from http://www.sensorsmag.corn/sensors/acoustic-ultrasound/ultrasonic-flowmeter-basics-842. |
| “Introduction to Ultrasonic Doppler Flowmeters,” OMEGA Engineering inc., accessed on Dec. 16, 2014, 3 pages. Retrieved from http://www.omega.com/prodinfo/ultrasonicflowmeters.html. |
| “Ultrasonic Flow Meters,” RS Hydro Ltd, accessed on Dec. 16, 2014, 3 pages. Retrieved from http://www.rshydro.co.uk/ultrasonic-flowmeter.shtml. |
| Wang et al., “Mixed Sound Event Verification on Wireless Sensor Network for Home Automation,” IEEE Transactions on Industrial Informatics, vol. 10, No. 1, Feb. 2014, 10 pages. |
| Fong A.C.M. et al, “Indoor air quality control for asthma patients using smart home technology,” Consumer Electronics (ISCE), 2011 IEEE 15th International Symposium on, IEEE, Jun. 14, 2011, pp. 18-19, XP032007803, DOI: 10.1109/ISCE.2011.5973774, ISBN: 978-1-61284-8433, Abstract and sections 3 and 4, 2 pages. |
| Shunfeng Cheng et al., “A Wireless Sensor System for Prognostics and Health Management,” IEEE Sensors Journal, IEEE Service Center, New York, NY, US, vol. 10, No. 4, Apr. 1, 2010, pp. 856-862, XP011304455, ISSN: 1530-437X, Sections 2 and 3, 7 pages. |
| International Search Report and Written Opinion for PCT/EP2015/070286 dated Nov. 5, 2015, 13 pages. |
| International Search Report and Written Opinion for PCT/GB2015/052544 dated Nov. 6, 2015, 10 pages. |
| International Search Report and Written Opinion for PCT/GB2015/052457 dated Nov. 13, 2015, 11 pages. |
| International Search Report and Written Opinion for PCT/EP2015/073299 dated Jan. 4, 2016, 12 pages. |
| International Search Report and Written Opinion for PCT/EP2015/073936 dated Feb. 4, 2016, all pages. |
| U.S. Appl. No. 14/107,132, filed Dec. 16, 2013, Final Rejection dated Dec. 16, 2015, 32 pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014, Final Rejection dated Feb. 23, 2016, 22 pages. |
| U.S. Appl. No. 14/567,348, filed Dec. 11, 2014, Preinterview first office action dated Jan. 20, 2016, 23 pages. |
| U.S. Appl. No. 14/470,352, filed Aug. 27, 2014 Final Office Action dated Mar. 17, 2016, all pages. |
| U.S. Appl. No. 14/567,765, filed Dec. 11, 2014, Preinterview first office action dated Apr. 8, 2016, 30 pages. |
| U.S. Appl. No. 14/577,717, filed Dec. 19, 2014, Preinterview first office action dated Apr. 4, 2016, 29 pages. |
| U.S. Appl. No. 14/584,075, filed Dec. 29, 2014, Non-Final Rejection dated Apr. 1, 2016, 40 pages. |
| U.S. Appl. No. 14/470,352, filed Aug. 27, 2014 Non Final Office Action dated Aug. 26, 2016, all pages. |
| U.S. Appl. No. 14/107,132, filed Dec. 16, 2013, Non Final Office Action dated Jul. 18, 2016, all pages. |
| U.S. Appl. No. 14/715,248, filed May 18, 2015, Non-Final Rejection dated Jul. 19, 2016, 34 pages. |
| U.S. Appl. No. 14/567,783, filed Dec. 11, 2014, Non Final Rejection dated Aug. 23, 2016, all pages. |
| International Preliminary Report on Patentability for PCT/US2014/053876 dated Jun. 14, 2016, 7 pages. |
| International Preliminary Report on Patentability for PCT/US2014/055441 dated Jun. 14, 2016, 8 pages. |
| International Preliminary Report on Patentability for PCT/US2014/055476 dated Jun. 14, 2016, 9 pages. |
| U.S. Appl. No. 14/470,352, filed Aug. 27, 2014 Notice of Allowance dated Dec. 2, 2016, all pages. |
| U.S. Appl. No. 15/050,958, filed Feb. 23, 2016 Notice of Allowance dated Dec. 6, 2016, all pages. |
| U.S. Appl. No. 15/289,395, filed Oct. 10, 2016 Non-Final Rejection dated Dec. 2, 2016, all pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014, Final Rejection dated Nov. 25, 2016, 22 pages. |
| U.S. Appl. No. 14/577,717, filed Dec. 19, 2014, Final Office Action dated Dec. 19, 2016, all pages. |
| U.S. Appl. No. 14/567,783, filed Dec. 11, 2014, Final Rejection dated Dec. 20, 2016, all pages. |
| U.S. Appl. No. 15/075,412, filed Mar. 21, 2016, Non Final Rejection dated Dec. 21, 2016, all pages. |
| Mark Edward Soper, “Absolute Beginner's Guide to Home Automation,” 2005, Que Publishing, p. 57, 121. |
| U.S. Appl. No. 14/982,366, filed Dec. 29, 2015, Non-Final Rejection dated Nov. 1, 2017, all pages. |
| U.S. Appl. No. 15/246,079, filed Aug. 24, 2016, Non-Final Rejection dated Oct. 19, 2017, all pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014, Final Rejection dated Oct. 25, 2017, all pages. |
| U.S. Appl. No. 14/485,038, filed Sep. 12, 2014, Notice of Allowance dated Nov. 13, 2017, all pages. |
| U.S. Appl. No. 14/528,402, filed Oct. 30, 2014, Final Rejection dated Oct. 31, 2017, all pages. |
| U.S. Appl. No. 14/981,501, filed Dec. 28, 2015, Final Office Action dated Oct. 10, 2017, all pages. |
| International Preliminary Report on Patentability for PCT/GB2015/052544 dated Mar. 7, 2017, all pages. |
| International Search Report and Written Opinion for PCT/US2016/057729 dated Mar. 28, 2017, all pages. |
| European Search Report for EP 16 20 0422 dated Jan. 13, 2017, all pages. |
| Bdejong_Cree, “Cannot remove last user of a group even though members still exist.” Microsoft Visual Studio forum site, Topic ID #58405. Response by Microsoft, Dec. 17, 2010) retrieved on Apr. 6, 2017 from: https://connect.microsoft.com/VisualStudio/feedback/details/580405/tfs-2010-cannont-remove-last-user-of-a-group-even-though-members-still-exists. |
| International Preliminary Report on Patentability for PCT/GB2015/052457 dated Feb. 28, 2017, all pages. |
| U.S. Appl. No. 14/107,132, filed Dec. 16, 2013, Notice of Allowance dated Jan. 18, 2017, all pages. |
| U.S. Appl. No. 14/485,188, filed Sep. 12, 2014, Non-Final Rejection dated Apr. 19, 2017, all pages. |
| U.S. Appl. No. 14/567,765, filed Dec. 11, 2014, Final Rejection dated Feb. 16, 2017, all pages. |
| U.S. Appl. No. 14/485,038, filed Sep. 12, 2014, Non Final Rejection dated Apr. 6, 2017, all pages. |
| U.S. Appl. No. 14/584,075, filed Dec. 29, 2014, Non-Final Rejection dated Mar. 10, 2017, all pages. |
| U.S. Appl. No. 14/710,331, filed May 12, 2015, Non-Final Rejection dated Mar. 10, 2017, all pages. |
| U.S. Appl. No. 14/566,977, filed Dec. 11, 2014, Final Rejection dated Feb. 10, 2017, all pages. |
| U.S. Appl. No. 14/671,299, filed Mar. 27, 2015, Notice of Allowance dated Apr. 17, 2017, all pages. |
| U.S. Appl. No. 14/565,853, filed Dec. 10, 2014, Non Final Rejection dated Mar. 10, 2017, all pages. |
| U.S. Appl. No. 15/075,412, filed Mar. 21, 2016, Final Rejection dated Apr. 17, 2017, all pages. |
| U.S. Appl. No. 14/497,130, filed Sep. 25, 2014, Non Final Rejection dated Feb. 8, 2017, all pages. |
| U.S. Appl. No. 14/528,402, filed Oct. 30, 2014, Non-Final Rejection dated Apr. 11, 2017, all pages. |
| U.S. Appl. No. 14/475,252, filed Sep. 2, 2014, Non-Final Rejection dated Apr. 12, 2017, all pages. |
| U.S. Appl. No. 15/289,395, filed Oct. 10, 2016 Non-Final Rejection dated Jun. 19, 2017, all pages. |
| U.S. Appl. No. 14/497,130, filed Sep. 25, 2014, Final Rejection dated Aug. 4, 2017, all pages. |
| U.S. Appl. No. 14/981,501, filed Dec. 28, 2015, First Action Interview—office action dated Jul. 19, 2017, all pages. |
| U.S. Appl. No. 14/567,502, filed Dec. 11, 2014, Final Rejection dated Aug. 7, 2017, all pages. |
| U.S. Appl. No. 14/986,483, filed Dec. 31, 2015, Notice of Allowance dated May 3, 2018, all pages. |
| U.S. Appl. No. 14/986,496, filed Dec. 31, 2015, Notice of Allowance dated May 18, 2018, all pages. |
| U.S. Appl. No. 15/246,259, filed Aug. 24, 2016 Non-Final Rejection dated May 30, 2018, all pages. |
| U.S. Appl. No. 15/672,997, filed Aug. 9, 2017 Non-Final Office Action dated May 15, 2018, all pages. |
| U.S. Appl. No. 15/230,155, filed Aug. 5, 2016, Non-Final Office Action dated May 16, 2018, all pages. |
| Office Action CN Appln No. 201480067003.5 dated Jan. 19, 2018, all pages. |
| U.S. Appl. No. 14/952,580, filed Nov. 25, 2015, Notice of Allowance dated Feb. 12, 2018, all pages. |
| U.S. Appl. No. 14/710,331, filed May 12, 2015, Notice of Allowance dated Dec. 7, 2017, all pages. |
| U.S. Appl. No. 14/528,402, filed Oct. 30, 2014, Notice of Allowance dated Jan. 29, 2018, all pages. |
| U.S. Appl. No. 14/553,763, filed Nov. 25, 2014 Notice of Allowance dated Mar. 27, 2018, all pages. |
| U.S. Appl. No. 15/246,079, filed Aug. 24, 2016, Notice of Allowance dated Apr. 10, 2018, all pages. |
| International Preliminary Report on Patentability for PCT/US2016/057729 dated Jul. 3, 2018, all pages. |
| U.S. Appl. No. 14/982,366, filed Dec. 29, 2015, Final Rejection dated Jun. 1, 2018, all pages. |
| U.S. Appl. No. 14/985,151, filed Dec. 30, 2015 Non-Final Rejection dated Nov. 16, 2017, all pages. |
| U.S. Appl. No. 14/985,151, filed Dec. 30, 2015 Notice of Allowance dated Jun. 7, 2018, all pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170168469 A1 | Jun 2017 | US |
