US 9,426,720 B2Grant
Controller and interface for home security, monitoring and automation having customizable audio alerts for SMA events
Issue Date:2016-08-23
•20 Claims
•12 Drawing Sheets
Abstract
A single platform for controller functionality for each of security, monitoring and automation, as well as providing a capacity to function as a bidirectional Internet gateway, is provided. Embodiments of the present invention provide such functionality by virtue of a configurable architecture that enables a user to adapt the system for the user's specific needs. Such configurability includes associating selected audio event tones with selected events associated with sensors and zones coupled to the system.
Metadata
Assignee
- iControl Networks, Inc.
Inventors
- Alan Wade Cohn
- John Degraffenreid Dial, IV
- Gary Robert Faulkner
- James Edward Kitchen
- David Leon Proft
- Corey Wayne Quain
Application Information
Application Number:US 12/771,471
Filing Date:2010-04-30
Priority Date:2009-04-30
Art Unit:2689
Classifications
IPC:
G08B13/00H04W40/28H04L12/28G08B25/00G08B25/14G08B29/08H04L29/08H04L29/06G06F11/07H04W40/34H04W76/00
Field of Search:
G08B 25/14G08B 13/19691B60R 25/104B60R 2025/1013
Patent Drawings (12 sheets)
Description
Cross Reference to Related Applications
[0001] This invention claims priority from Provisional Patent Application Ser. No. 61/174,366, entitled “REMOTE SECURITY STATION,” filed Apr. 30, 2009, and naming Alan Wade Cohn as inventor. This provisional patent application is incorporated herein by reference in its entirety and for all purposes.
Field of the Invention
[0002] Embodiments of the present invention relate generally to the field of home security, monitoring and automation, and specifically to a user-configurable controller for security, monitoring and automation with customizable audio alerts.
Background of the Invention
[0003] Residential electronics and control standards provide an opportunity for a variety of options for securing, monitoring, and automating residences. Wireless protocols for transmission of security information permit placement of a multitude of security sensors throughout a residence without a need for running wires back to a central control panel. Inexpensive wireless cameras also allow for placement of cameras throughout a residence to enable easy monitoring of the residence. A variety of home automation control protocols have also been developed to allow for centralized remote control of lights, appliances, and environmental apparatuses (e.g., thermostats). Traditionally, each of these security, monitoring and automation protocols require separate programming, control and monitoring stations. To the extent that home automation and monitoring systems have been coupled to home security systems, such coupling has involved including the automation and monitoring systems as slaves to the existing home security system. This limits the flexibility and versatility of the automation and monitoring systems and ties such systems to proprietary architectures.
[0004] A security system alerts occupants of a dwelling and emergency authorities of a violation of premises secured by the system. A typical security system includes a controller connected by wireless or wired connections to sensors deployed at various locations throughout the secured dwelling. In a home, sensors are usually deployed in doorways, windows, and other points of entry. Motion sensors can also be placed strategically within the home to detect unauthorized movement, while smoke and heat sensors can detect the presence of fire.
[0005] A home monitoring system provides an ability to monitor a status of a home so that a user can be made aware of any monitored state changes. For example, when a sensor is tripped, real-time alerts and associated data such as video or photo clips can be sent to the user (e.g., to a network-connected computer or to a mobile device).
[0006] A home automation system enables automation and remote control of lifestyle conveniences such as lighting, heating, cooling, and appliances. Typically these various lifestyle conveniences are coupled to a controller via wireless or wired communications protocols. A central device is then used to program the various lifestyle conveniences.
[0007] Rather than having multiple devices to control each of the security, monitoring and automation environments, it is desirable to have a centralized controller capable of operating in each environment, thereby reducing the equipment needed in a dwelling. It is further desirable for such a combined controller and gateway to provide configurable flexibility in how devices in the various environments are monitored and controlled.
Summary of the Invention
[0008] Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring and automation, as well as providing a capacity to function as a bidirectional Internet gateway. Embodiments of the present invention provide such functionality by virtue of a configurable architecture that enables a user to adapt the system for the user's specific needs.
[0009] One embodiment of the present invention includes memory for storing configuration information for security sensors, monitoring devices and automation devices, communication interfaces for communicating with one or more of these devices and a remote server, and a processor for interpreting event signals from the security sensors. One aspect of this embodiment of the present invention provides for the interpretation of the event signals to be performed in accordance with the configuration information of the associated security sensor. A further aspect of this embodiment of the present invention provides for selected audio signals to be played when a corresponding event signal is received.
[0010] One embodiment of the present invention includes a memory storing configuration information for one or more devices and mapping information associating one or more device events with corresponding event tone identifiers, an interface to communicate with the one or more devices, an audio processor coupled to a speaker, and a processor coupled to the memory, the interface and the audio processor. In the above embodiment, the processor is configured to interpret an event signal received from a device of the one or more devices, determine if a first event tone identifier is associated with the interpreted event signal by using the mapping information, play a first event tone associated with the first event tone identifier if there is an association, or play a default event tone if there is no association.
[0011] An aspect of the above embodiment includes a display coupled to the processor and the processor further configured to display the mapping information. In another aspect of the above embodiment, an input device is coupled to the processor and the processor can receive additional mapping information associating a selected event tone identifier with a selected device event, modify the mapping information with the received mapping information, and store the modified mapping information in the memory.
[0012] In a further aspect, the memory stores event tone files that correspond to event tone identifiers, and the processor displays a list of event tone identifiers corresponding to the event tone files on a display. In still a further aspect, the device incorporates a communication interface for communicating with a remote server, and the processor is further configured to download a selected event tone file from the remote server, store the selected event tone file in the memory, and add an event tone identifier for the selected event tone file to the list of event tone identifiers. Further, the device can download a list of available event tone identifiers corresponding to available event tone files from the remote server, display the list of available event tone identifiers, and provide for selection of an available event tone identifier. The list of available event tone identifiers can be populated according to a service tier associated with a user of the device, services provided to the device, and programs installed on the device.
[0013] In another aspect of the above embodiment, the device can incorporate a communication interface to communicate with a remote server, and the processor can transmit the mapping information to the remote server, where that mapping information can be stored.
[0014] Embodiments of the above invention include not only a device, but also a method for performing the steps and means for performing the steps.
[0015] The foregoing is a summary and thus contains, by necessity, simplifications, generalizations, and omissions of detail. Consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. As will also be apparent to one of skill in the art, the operations disclosed herein may be implemented in any number of ways, and such changes and modifications may be made without departing from this invention and its broader aspects. Other aspects, inventive features, and advantages of the present invention, as defined solely by the claims, will become apparent in the non-limiting detailed description set forth below.
Brief Description of the Drawings
[0016] The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.
[0017] FIG. 1 is a simplified block diagram illustrating an architecture including a set of logical domains and functional entities within which embodiments of the present invention interact.
[0018] FIG. 2 is a simplified block diagram illustrating a hardware architecture of an SMA controller, according to one embodiment of the present invention.
[0019] FIG. 3 is a simplified block diagram illustrating a logical stacking of an SMA controller's firmware architecture, usable with embodiments of the present invention.
[0020] FIG. 4 is an illustration of an example user interface for an SMA controller 120, according to an embodiment of the present invention.
[0021] FIG. 5 is a simplified flow diagram illustrating steps performed in a configuration process of an SMA controller, in accord with embodiments of the present invention.
[0022] FIG. 6 is a simplified flow diagram illustrating steps performed in configuring security sensors (e.g., 510), in accord with embodiments of the present invention.
[0023] FIG. 7 is an illustration of a display that can be provided by embodiments of the present invention to permit editing of sensor information (e.g., sensor zone information).
[0024] FIG. 8 is a simplified flow diagram illustrating steps performed to configure a home domain monitoring device, in accord with embodiments of the present invention.
[0025] FIG. 9 is a simplified flow diagram illustrating steps performed in selecting widgets for use by an SMA controller, in accord with embodiments of the present invention.
[0026] FIG. 10 is a simplified flow diagram illustrating an example of a process for associating event tones with events, in accord with embodiments of the present invention.
[0027] FIG. 11 depicts a block diagram of a computer system suitable for implementing aspects of the present invention.
[0028] FIG. 12 is a block diagram depicting a network architecture suitable for implementing aspects of the present invention.
Detailed Description
[0029] Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring and automation, as well as providing a capacity to function as a bidirectional Internet gateway. Embodiments of the present invention provide such functionality by virtue of a configurable architecture that enables a user to adapt the system for the user's specific needs. Those needs can include customized audio signals corresponding to security events received by the controller.
Architectural Overview
[0030] Embodiments of the configurable security, monitoring and automation (SMA) controller of the present invention provide not only for communicating with and interpreting signals from sensors and devices within a dwelling, but also for accessing and monitoring those sensors and devices from locations remote to the dwelling. Embodiments of the SMA controller provide such capability through linkages to external servers via access networks such as the Internet, provider network, or a cellular network. The external servers provide a portal environment through which a user can, for example, monitor the state of sensors coupled to the SMA controller in real-time, configure the controller, and provide controlling information to the SMA controller. The servers can further automatically provide information to a user via remote devices such as mobile phones 192, computers 197, and pagers 195. The servers further provide a connection to a traditional security central station, which can then contact authorities in the event of an alarm condition being detected by the SMA controller in the dwelling.
[0031] FIG. 1 is a simplified block diagram illustrating an architecture including a set of logical domains and functional entities within which embodiments of the present invention interact. A home domain 110 includes an embodiment of the SMA controller 120. The home domain is coupled via an access domain 150 to an operator domain 160 that includes various servers. The servers are in turn coupled to a central station 190 and to various remote user communication options (e.g., Mobile 192, Pager 195, Computer 197).
[0032] The home domain refers to a collection of security, monitoring and automation entities within a dwelling or other location having SMA devices. SMA controller 120 is a device that provides an end-user SMA interface to the various SMA entities (e.g., radio-frequency sensors) within home domain 110. SMA controller 120 further acts as a gateway interface between home domain 110 and operator domain 160. SMA controller 120 provides such gateway access to operator domain 160 via a network router 125. Network router 125 can be coupled to SMA controller 120 and to home network devices such as home computer 127 via either hard wired or wireless connections. A network router 125 coupled to a broadband modem (e.g., a cable modem or DSL modem) serves as one link to networks in access domain 150.
[0033] SMA devices within home domain 110 can include a variety of RF or wireless sensors 130 whose signals are received and interpreted by SMA controller 120. RF sensors 130 can include, for example, door or window sensors, motion detectors, smoke detectors, glass break detectors, inertial detectors, water detectors, carbon dioxide detectors, and key fob devices. SMA controller 120 can be configured to react to a change in state of any of these detectors. For example, the SMA controller can sound an audio alert upon a detector state change. In addition to acting and reacting to changes in state of RF sensors 130, SMA controller 120 also can be coupled to a legacy security system 135. SMA controller 120 controls the legacy security system by interpreting signals from sensors coupled to the legacy security system and reacting in a user-configured manner. SMA controller 120, for example, will provide alarm or sensor state information from legacy security system 135 to servers in operator domain 160 that may ultimately inform central station 190 to take appropriate action.
[0034] SMA controller 120 can also be coupled to one or more monitoring devices 140. Monitoring devices 140 can include, for example, still and video cameras that provide images that are viewable on a screen of SMA controller 120 or a remotely connected device. Monitoring devices 140 can be coupled to SMA controller 120 either wirelessly (e.g., WiFi via router 125) or other connections.
[0035] Home automation devices 145 can also be coupled to and controlled by SMA controller 120. SMA controller 120 can be configured to interact with a variety of home automation protocols, such as, for example, Z-Wave and ZigBee.
[0036] Embodiments of SMA controller 120 can be configured to communicate with a variety of RF or wireless sensors and are not limited to the RF sensors, monitoring devices and home automation devices discussed above. A person of ordinary skill in the art will appreciate that embodiments of the present invention are not limited to or by the above-discussed devices and sensors, and can be applied to other areas and devices.
[0037] Embodiments of SMA controller 120 can be used to configure and control home security devices (e.g., 130 and 135), monitoring devices 140 and automation devices 145, either directly or by providing a gateway to remote control via servers in operator domain 160. SMA controller 120 communicates with servers residing in operator domain 160 via networks in access domain 150. Broadband communication can be provided by coupling SMA controller 120 with a network router 125, which in turn is coupled to a wide area network 152, such as a provider network or the Internet, via an appropriate broadband modem. The router can be coupled to the wide area network through cable broadband, DSL, and the like. Wide area network 152, in turn, is coupled to servers in operator domain 160 via an appropriate series of routers and firewalls (not shown). SMA controller 120 can include additional mechanisms to provide a communication with the operator domain. For example, SMA controller 120 can be configured with a cellular network transceiver that permits communication with a cellular network 154. In turn, cellular network 154 can provide access via routers and firewalls to servers in operator domain 160. Embodiments of SMA controller 120 are not limited to providing gateway functionality via cellular and dwelling-based routers and modems. For example, SMA controller 120 can be configured with other network protocol controllers such as WiMAX satellite-based broadband, direct telephone coupling, and the like.
[0038] Operator domain 160 refers to a logical collection of SMA servers and other operator systems in an operator's network that provide end-user interfaces, such as portals accessible to subscribers of the SMA service, that can configure, manage and control SMA elements within home domain 110. Servers in operator domain 160 can be maintained by a provider (operator) of subscriber-based services for SMA operations. Examples of providers include cable providers, telecommunications providers, and the like. A production server architecture in operator domain 160 can support SMA systems in millions of home domains 110.
[0039] Individual server architectures can be of a variety of types, and in one embodiment, the server architecture is a tiered Java2 Enterprise Edition (J2EE) service oriented architecture. Such a tiered service oriented architecture can include an interface tier, a service tier, and a data access logic tier. The interface tier can provide entry points from outside the server processes, including, for example, browser web applications, mobile web applications, web services, HTML, XHTML, SOAP, and the like. A service tier can provide a variety of selectable functionality passed along by the operator to the end user. Service tiers can relate to end user subscription levels offered by the operator (e.g., payment tiers corresponding to “gold” level service, “silver” level service and “bronze” level service). Finally the data access logic tier provides access to various sources of data including database servers.
[0040] FIG. 1 illustrates an example set of servers that can be provided in operator domain 160. Servers 165 can support all non-alarm and alarm events, heartbeat, and command traffic between the various servers and SMA controllers 120. Servers 165 can also manage end-user electronic mail and SMS notification, as well as integration with provider billing, provisioning, inventory, tech support systems, and the like.
[0041] A portal server 170 can provide various user interface applications, including, for example, a subscriber portal, a mobile portal, and a management portal. A subscriber portal is an end-user accessible application that permits an end-user to access a corresponding SMA controller remotely via standard web-based applications. Using such a subscriber portal provides access to the same SMA functions that an interface directly coupled to the SMA controller would provide, plus additional functions such as alert and contact management, historical data, widget and camera management, account management, and the like. A mobile portal can provide all or part of the access available to an end-user via the subscriber portal. A mobile portal can be limited, however, to capabilities of an accessing mobile device (e.g., touch screen or non-touch screen cellular phones). A management portal provides an operator representative access to support and manage SMA controllers in home domains 110 and corresponding user accounts via a web-based application. The management portal can provide tiers of management support so that levels of access to user information can be restricted based on authorization of a particular employee.
[0042] Telephony server 180 can process and send information related to alarm events received from SMA controllers 120 to alarm receivers at central monitoring station 190. A server 165 that processes the alarm event makes a request to telephony server 180 to dial the central station's receiver and send corresponding contact information. Telephony server 180 can communicate with a plurality of central stations 190. Server 165 can determine a correct central station to contact based upon user account settings associated with the transmitting SMA controller. Thus, alarms can be routed to different central stations based upon user accounts. Further, accounts can be transferred from one central station to another by modifying user account information. Telephony server 180 can communicate with alarm receivers at central station 190 using, for example, a security industry standard contact identification protocol (e.g., dual-tone multi-frequency [DTMF]) and broadband protocols.
[0043] A backup server 175 can be provided to guarantee that an alarm path is available in an event that one or more servers 165 become unavailable or inaccessible. A backup server 175 can be co-located to the physical location of servers 165 to address scenarios in which one or more of the servers fail. Alternatively, a backup server 175 can be placed in a location remote from servers 165 in order to address situations in which a network failure or a power failure causes one or more of servers 165 to become unavailable. SMA controllers 120 can be configured to transmit alarm events to a backup server 175 if the SMA controller cannot successfully send such events to servers 165.
[0044] A database server 185 provides storage of all configuration and user information accessible to other servers within operator domain 160. Selection of a type of database provided by database server 185 can be dependent upon a variety of criteria, including, for example, scalability and availability of data. One embodiment of the present invention uses database services provided by an ORACLE database.
[0045] A server 165 in operator domain 160 provides a variety of functionality. Logically, a server 165 can be divided into the following functional modules: a broadband communication module, a cellular communication module, a notification module, a telephony communication module, and an integration module.
[0046] The broadband communication module manages broadband connections and message traffic from a plurality of SMA controllers 110 coupled to server 165. Embodiments of the present invention provide for the broadband channel to be a primary communication channel between an SMA controller 120 and servers 165. The broadband communication module handles a variety of communication, including, for example, all non-alarm and alarm events, broadband heartbeat, and command of traffic between server 165 and SMA controller 120 over the broadband channel. Embodiments of the present invention provide for an always-on persistent TCP socket connection to be maintained between each SMA controller and server 165. A variety of protocols can be used for communications between server 165 and SMA controller 120 (e.g., XML over TCP, and the like). Such communication can be secured using standard transport layer security (TLS) technologies. Through the use of an always-on socket connection, servers 165 can provide near real-time communication between the server and an SMA controller 120. For example, if a user has a subscriber portal active and a zone is tripped within home domain 110, a zone fault will be reflected in near real-time on the subscriber portal user interface.
[0047] The cellular communication module manages cellular connections and message traffic from SMA controllers 120 to a server 165. Embodiments of the present invention use the cellular channel as a backup communication channel to the broadband channel. Thus, if a broadband channel becomes unavailable, communication between an SMA controller and a server switches to the cellular channel. At this time, the cellular communication module on the server handles all non-alarm and alarm events, and command traffic from an SMA controller. When a broadband channel is active, heartbeat messages can be sent periodically on the cellular channel in order to monitor the cellular channel. When a cellular protocol communication stack is being used, a TCP socket connection can be established between the SMA controller and server to ensure reliable message delivery for critical messages (e.g., alarm events and commands). Once critical messages have been exchanged, the TCP connection can be shut down thereby reducing cellular communication costs. As with broadband communication, XMPP can be the messaging protocol used for such communications. Similarly, such communication can be secured using TLS and SASL authentication protocols. Non-critical messages between an SMA controller and a server can be sent using UDP. A compressed binary protocol can be used as a messaging protocol for such communications in order to minimize cellular costs for such message traffic. Such messages can be secured using an encryption algorithm, such as the tiny encryption algorithm (TEA). Cellular communication can be established over two network segments: the GSM service provider's network that provides a path between an SMA controller and a cellular access point, and a VPN tunnel between the access point and an operator domain data center.
[0048] A notification module of server 165 determines if and how a user should be notified of events generated by their corresponding SMA controller 120. A user can specify who to notify of particular events or event types and how to notify the user (e.g., telephone call, electronic mail, text message, page, and the like), and this information is stored by a database server 185. When events such as alarm or non-alarm events are received by a server 165, those events can be past asynchronously to the notification module, which determines if, who and how to send those notifications based upon the user's configuration.
[0049] The telephony communication module provides communication between a server 165 and telephony server 180. When a server 165 receives and performs initial processing of alarm events, the telephony communication module forwards those events to a telephony server 180 which in turn communicates with a central station 190, as discussed above.
[0050] The integration module provides infrastructure and interfaces to integrate a server 165 with operator business systems, such as, for example, billing, provisioning, inventory, tech support, and the like. An integration module can provide a web services interface for upstream integration that operator business systems can call to perform operations like creating and updating accounts and querying information stored in a database served by database server 185. An integration module can also provide an event-driven framework for downstream integration to inform operator business systems of events within the SMA system.
SMA Controller Architecture
[0051] FIG. 2 is a simplified block diagram illustrating a hardware architecture of an SMA controller, according to one embodiment of the present invention. A processor 210 is coupled to a plurality of communications transceivers, interface modules, memory modules, and user interface modules. Processor 210, executing firmware discussed below, performs various tasks related to interpretation of alarm and non-alarm signals received by SMA controller 120, interpreting reactions to those signals in light of configuration information either received from a server (e.g., server 165) or entered into an interface provided by SMA controller 120 (e.g., a touch screen 220). Embodiments of the present invention can use a variety of processors, for example, an ARM core processor such as a FREESCALE i.MX35 multimedia applications processor.
[0052] SMA controller 120 can provide for user input and display via a touch screen 220 coupled to processor 210. Processor 210 can also provide audio feedback to a user via use of an audio processor 225. Embodiments of the present invention can use a variety of audio processors. For example, one embodiment includes a stereo CODEC such as a CIRRUS LOGIC CS42L52 low power stereo CODEC. Audio processor 225 can, in turn, be coupled to one or more speakers that provide sound in home domain 110. As will be discussed more fully below, SMA controller 120 can be configured to provide a variety of sounds for different events detected by sensors and particular zones and other devices associated with the SMA controller. Such sounds can be configured by a user so as to distinguish between different types of events.
[0053] As discussed above, an SMA controller 120 can communicate with a server 165 using different network access means. Processor 210 can provide broadband access to a router (e.g., router 125) via an Ethernet broadband connection PHY 130 or via a WiFi transceiver 235. The router can then be coupled to or be incorporated within an appropriate broadband modem. Cellular network connectivity can be provided by a cellular transceiver 240 that is coupled to processor 210. SMA controller 120 can be configured with a set of rules that govern when processor 210 will switch between a broadband connection and a cellular connection to operator domain 160.
[0054] In order to communicate with the various sensors and devices within home domain 110, processor 210 can be coupled to one or more transceiver modules via, for example, a serial peripheral interface such as a SPI bus 250. Such transceiver modules permit communication with sensors of a variety of protocols in a configurable manner. Embodiments of the present invention can use a Bosch transceiver to communicate with a variety of RF sensors 130. Similarly, home automation transceivers that communicate using Z-Wave or ZigBee protocols can be coupled to processor 210 via SPI 250. If SMA controller 120 is coupled to a legacy security system 135, then a module permitting coupling to the legacy security system can be coupled to processor 210 via SPI 250. Other protocols can be provided for via such plug-in modules including, for example, digital enhanced cordless telecommunication devices (DECT). In this manner, an SMA controller 120 can be configured to provide for control of a variety of devices and protocols known both today and in the future. In addition, processor 210 can be coupled to other types of devices (e.g., transceivers or computers) via a universal serial bus (USB) interface 255.
[0055] In order to locally store configuration information for SMA controller 120, a memory 260 is coupled to processor 210. Additional memory can be coupled to processor 210 via, for example, a secure digital interface 265. A power supply 270 is also coupled to processor 210 and to other devices within SMA controller 120 via, for example, a power management controller module.
[0056] SMA controller 120 is configured to be a customer premises equipment device that works in conjunction with server counterparts in operator domain 160 in order to perform functions required for security monitoring and automation. Embodiments of SMA controller 120 provide a touch screen interface (e.g., 220) into all the SMA features. Via the various modules coupled to processor 210, the SMA controller bridges the sensor network, the control network, and security panel network to broadband and cellular networks. SMA controller 120 further uses the protocols discussed above to carry the alarm and activity events to servers in the operator domain for processing. These connections also carry configuration information, provisioning commands, management and reporting information, security authentication, and any real-time media such as video or audio.
[0057] FIG. 3 is a simplified block diagram illustrating a logical stacking of an SMA controller's firmware architecture, usable with embodiments of the present invention. Since SMA controller 120 provides security functionality for home domain 110, the SMA controller should be a highly available system. High availability suggests that the SMA controller be ready to serve an end-user at all times, both when a user is interacting with the SMA controller through a user interface and when alarms and other non-critical system events occur, regardless of whether a system component has failed. In order to provide such high availability, SMA controller 120 runs a micro-kernel operating system 310. An example of a micro-kernel operating system usable by embodiments of the present invention is a QNX real-time operating system. Under such a micro-kernel operating system, drivers, applications, protocol stacks and file systems run outside the operating system kernel in memory-protected user space. Such a micro-kernel operating system can provide fault resilience through features such as critical process monitoring and adaptive partitioning. As a result, components can fail, including low-level drivers, and automatically restart without affecting other components or the kernel and without requiring a reboot of the system. A critical process monitoring feature can automatically restart failed components because those components function in the user space. An adaptive partitioning feature of the micro kernel operating system provides guarantees of CPU resources for designated components, thereby preventing a component from consuming all CPU resources to the detriment of other system components.
[0058] A core layer 320 of the firmware architecture provides service/event library and client API library components. A client API library can register managers and drivers to handle events and to tell other managers or drivers to perform some action. The service/event library maintains lists of listeners for events that each manager or driver detects and distributes according to one of the lists.
[0059] Driver layer 330 interacts with hardware peripherals of SMA controller 120. For example, drivers can be provided for touch screen 220, broadband connection 230, WiFi transceiver 235, cellular transceiver 240, USB interface 255, SD interface 265, audio processor 225, and the various modules coupled to processor 210 via SPI interface 250. Manager layer 340 provides business and control logic used by the other layers. Managers can be provided for alarm activities, security protocols, keypad functionality, communications functionality, audio functionality, and the like.
[0060] Keypad user interface layer 350 drives the touch screen user interface of SMA controller 120. An example of the touch screen user interface consists of a header and a footer, widget icons and underlying widget user interfaces. Keypad user interface layer 350 drives these user interface elements by providing, for example, management of what the system Arm/Disarm interface button says and battery charge information, widget icon placement in the user face area between the header and footer, and interacting with widget engine layer 360 to display underlying widget user interface when a widget icon is selected.
[0061] In embodiments of the present invention, typical SMA controller functions are represented in the touch screen user interface as widgets (or active icons). Widgets provide access to the various security monitoring and automation control functions of SMA controller 120 as well as providing support for multi-media functionality through widgets that provide, for example, news, sports, weather and digital picture frame functionality. A main user interface screen can provide a set of icons, each of which represents a widget. Selection of a widget icon can then launch the widget. Widget engine layer 360 includes, for example, widget engines for native, HTML and FLASH-based widgets. Widget engines are responsible for displaying particular widgets on the screen. For example, if a widget is developed in HTML, selection of such a widget will cause the HTML widget engine to display the selected widget or touch screen 220. Information related to the various widgets is provided in widget layer 370.
[0062] FIG. 4 is an illustration of an example user interface for an SMA controller 120, according to an embodiment of the present invention. The illustrated user interface provides a set of widget icons 410 that provide access to functionality of SMA controller 120. As illustrated, widgets are provided to access security functionality, camera images, thermostat control, lighting control, and other settings of the SMA controller. Additional widgets are provided to access network-based information such as weather, news, traffic, and digital picture frame functionality. A header 420 provides access to an Arm/Disarm button 425 that allows for arming the security system or disarming it. Additional information can be provided in the header, such as, for example, network status messages. A footer 430 can provide additional status information such as time and date, as displayed.
[0063] A user can select widgets corresponding to desired functionality. Embodiments of the present invention provide for access to widgets via portal server 170. A provider of operator domain 160 can determine functionality accessible to users, either for all users or based upon tiers of users (e.g., subscription levels associated with payment levels). A user can then select from the set of accessible widgets and the selected widgets will be distributed and displayed on the user interface of SMA controller 120. Configurability of SMA controller 120 is also driven by user determined actions and reactions to sensor stimulus.
SMA Controller Configurability
[0064] In accord with embodiments of the present invention, SMA controller 120 can be configured by a user in order to provide desired functionality in home domain 110. In addition to the hardware configurable options discussed above (e.g., modules coupled to SPI interface 250), SMA controller 120 provides for additional configuration through the use of software and/or firmware. For example, SMA controller 120 can be configured to receive signals from a variety of security sensors (e.g., RF sensors 130) and to associate those sensors with the physical environment of home domain 110. In addition, SMA controller 120 can be configured to receive still and video information from one or more cameras, provide a variety of programs and utilities to a user, and is configurable to communicate with a variety of home automation devices.
[0065] FIG. 5 is a simplified flow diagram illustrating steps performed in a configuration process of an SMA controller, in accord with embodiments of the present invention. Embodiments of an SMA controller will typically be configured with security sensor information, either from RF sensors 130 or from a legacy security system 135. Therefore, an SMA controller will be configured to access and interpret information related to those security sensors (510).
[0066] A determination can then be made as to whether or not a user is including security cameras in home domain 110 (520). If cameras are included in the home domain, then a series of steps related to camera configuration is performed (530). Similarly, a determination can be made as to whether or not home automation devices are to be controlled by the SMA controller (540). If so, then a series of steps can be performed to configure the SMA controller to access those home automation devices (550).
[0067] A user can then perform steps necessary to configuring widgets accessible via the SMA controller (560). As discussed above, the user may access a portal server (e.g., 170) to select and configure those widgets that are desirable to be accessed at SMA controller 120. Once these configuration steps are performed, the SMA controller can be made available to perform tasks related to securing, monitoring, and providing automation control to home domain 110.
[0068] SMA controller 120 can be configured to receive and interpret signals from a variety of security sensors. Such sensors can include, for example, door/window sensors that can detect opening and closing of a door or window, motion detectors that can detect movement in an area of interest, smoke detectors, glass break detectors, inertia detectors, and key fobs. In order to usefully interpret signals from such detectors, embodiments of SMA controller 120 can search for signals from such sensors and be configured with information related to the location and tasks of those sensors.
[0069] FIG. 6 is a simplified flow diagram illustrating steps performed in configuring security sensors (e.g., 510), in accord with embodiments of the present invention. A user of a security system incorporating SMA controller 120 (e.g., an owner or resident of home domain 110) can decide, based upon the needs within the home domain, the types and number of security sensors needed to secure the home domain. SMA controller 120, via a touch screen input device, for example, can be told how many such sensors to search for (610). The SMA controller can then search for all activated sensors providing a linking message to the SMA controller (620). Such a linking message can provide sensor information including, for example, a unique identification number for the sensor and sensor type information. A touch screen interface for SMA controller 120 can then provide to the user a display indicating information related to all sensors found during the search (630).
[0070] Once presented with information related to all the located sensors, a user can then edit that information to provide specifics as to physical, or zone, location of the sensor within the home domain and other characteristics related to the zone of the sensor (640). For example, a touch screen display 220 coupled to SMA controller 120 can provide a list of all located sensors from which the user can select a specific sensor to define or edit information related to that sensor. The information related to the sensors and zones is then stored in a local memory of the SMA controller 120 (e.g., memory 260) (650). The SMA controller can also transmit the sensor zone information to be stored in a server in operator domain 160 via an available broadband connection (660).
[0071] FIG. 7 is an illustration of a display that can be provided by embodiments of the present invention to permit editing of sensor information (e.g., sensor zone information). As illustrated, the display can provide information such as the unique identifier of the sensor (serial number 710) and the sensor type (sensor type 720). As indicated above, unique identifier and sensor type information is provided by the sensor during the search and location process. Through a display such as that illustrated in FIG. 7 , a user can define additional zone characteristics related to the sensor. For example, a user can define or select a zone name 730 to associate with the sensor. Such a zone name can be entered by a user through the use of a touch screen-based keyboard or selected from a list of common names displayed on the touch screen.
[0072] A zone function 740 can also be provided to be associated with the sensor. A zone function determines behavior of the zone and is dependent on the zone type. For example, a door/window sensor can function as an entry/exit zone or as a perimeter zone. Each zone type can have one or more configurable zone functions. For example, a motion detector can have a zone function of interior follower, a smoke/heat detector can have a zone function of 24-hour fire monitoring, a glass break detector can have a zone function of a perimeter zone, and an inertia detector can have an entry/exit zone function or a perimeter zone function.
[0073] Selection of a zone function definition alters how the security system acts and reacts to signals received from a sensor in that zone. The following table illustrates examples of zone functions and their associated action/reaction definitions.
[0074]
| TABLE 1 | |
|---|---|
| Zone | |
| Function | Definition |
| Entry/Exit | Allow exiting the home domain when the system is arming and |
| will begin an entry delay when opened if the system is armed. | |
| Zone can be bypassed and can have specific tones assigned for | |
| open and close events. | |
| Perimeter | Generate an alarm immediately if tripped while the system is |
| armed. Can be bypassed and can have specific tones assigned | |
| for open and close events. | |
| Interior | Protect the internal spaces of the home domain and trigger an |
| Follower | immediate alarm if the system is armed in away mode. Zone is |
| not armed when the system is in armed stay mode. Can be | |
| bypassed and can have specific activity/non activity tones | |
| assigned. | |
| 24-Hour | Generate an immediate fire alarm if triggered. Zone cannot be |
| Fire | bypassed. |
| 24-Hour | Generate notifications in the home and will beep the keypad |
| Monitor | but will not sound the full alarm. Can be bypassed. |
| 24-Hour | Generates notifications, beeps keypads, and sounds the siren to |
| Environ- | let people within the home domain know to evacuate the |
| mental | premises. Cannot be bypassed. |
| 24-Hour | Will never generate an alarm, even if the system is armed. |
| Inform | Upon triggering of the sensor will make the configured sound |
| and send events to the operator domain. Can be bypassed. | |
[0075] By defining such zones, a user can control how the security functions of SMA controller 120 react to various sensor triggers.
[0076] A user can also configure a display icon 750 associated with the sensor zone. In many cases, the available icons will be limited to one type of icon that graphically relates to the sensor type. But, for example, with a door/window sensor, icons can be made available that illustrate a door or a window as appropriate. FIG. 7 further illustrates a signal strength button 760 that, when selected, can illustrate strength of the signal between the wireless hub located within SMA controller 120 and the associated sensor.
[0077] The sensor zone information entered through the use of a display such as that illustrated in FIG. 7 , can be stored in local data tables that are stored in memory 260 of SMA controller 120 (650). In addition, sensor zone information can also be transmitted via access domain 150 to servers in operator domain 160 for storage (e.g., database server 185) (660). By storing the sensor zone information in servers in the operator domain, the information is available to a user accessing a portal server 170. A user could then edit the sensor zone information through use of the portal rather than the SMA controller interface. Further, sensor zone information stored on database server 185 is retained even if an SMA controller suffers from an event that makes the SMA controller unusable. In such an event, a new SMA controller can be installed in home domain 110 and the information stored in operator domain 160 can be provided to the new SMA controller. This eliminates a need to manually reconfigure the new SMA controller with all sensor information.
[0078] FIG. 8 is a simplified flow diagram illustrating steps performed to configure a home domain monitoring device, in accord with embodiments of the present invention. As discussed above, SMA controller 120 can communicate with home domain monitoring devices 140, such as cameras and audio monitors. For example, a wireless camera can be activated and can communicate with SMA controller 120 via a router 125. During configuration, the SMA controller can detect the presence of a camera by receiving an MAC address of the camera from the router (810). The SMA controller can then configure the camera to communicate wirelessly with the router and the SMA controller (820). The SMA controller can pass a variety of information to the camera during a configuration phase, including, for example, an administrative user name and password, camera name, camera description, time zone, current time, language, user session name and password for list of users allowed to access the camera, network settings such as IP address and name servers, protocol settings, motion detection settings, and desired camera image settings such as resolution and video adjustments. In addition, the camera can provide information to the SMA controller for storage, such as, for example, device type, manufacturer, model number, and other control information.
[0079] Once the SMA controller and camera are configured, then images generated by the camera can be displayed on a display device associated with SMA controller 120 (830) or can be communicated to a portal server in operator domain 160 via a network in access domain 150 for display on a computer or mobile devices communicating with the portal server (840). SMA controller 120 can also store information related to the camera, such as, for example, a camera name, location of the camera, and relationship of the camera with a defined sensor zone. Embodiments of the present invention can provide both still and video images either on the SMA controller display or a portal display. An SMA controller can be configured to communicate with more than one monitoring device.
[0080] SMA controller 120 also has a capability of providing access to a variety of functionality through the use of widget programs. FIG. 4 , discussed above, illustrates an example of a home screen display of SMA controller 120, showing a set of icons having associated widget programs (410). Some of the widgets provide for SMA controller functionality, such as, for example, security access, camera monitoring, and setting modification. Additionally, widgets can be provided to access SMA controller automation functionality such as thermostat control and lighting control. In addition, an SMA controller can provide display of user-selectable widgets (e.g., calendar, weather, news, traffic, and photos).
[0081] FIG. 9 is a simplified flow diagram illustrating steps performed in selecting widgets for use by an SMA controller, in accord with embodiments of the present invention. A user can select those user selectable widget programs that are desired by accessing a portal server 170 (910). The user can view those widget programs that are available to the user and select those that the user wishes to install on the SMA controller (920). A user can also configure how the widget icons are displayed on the home screen (e.g., position of each icon) as well as provide any individual widget configuration information (e.g., zip code information for weather and traffic widgets) (930). Depending upon the purpose of a widget, a user may have a variety of options in configuring that widget.
[0082] By making widgets available on a portal server in the operator domain, the operator can control the nature and types of widgets available to a user. For example, an operator can define a series of option tiers for their users, with each tier having increasing numbers of available widgets or different type of widget functionality. Further, by making the widgets available through the portal, an operator can control the quality of the available widgets and ensuring that widgets will not affect the operability of SMA controller under the operator's control.
[0083] Once selected, code related to the widgets and widget setup information is transferred from servers in operator domain 160 to the associated SMA controller 120 in home domain 110 (940). That code information is stored in SMA controller 120, for example, in memory 260.
[0084] SMA controller 120 can also be configured to provide home automation functionality. As discussed above, a variety of hardware modules can be coupled to the SMA controller, allowing the SMA controller to communicate using protocols associated with those modules. In addition to the hardware configurability, SMA controller 120 is configured to communicate with a variety of devices selected to be controlled by the SMA controller. In a manner similar to that discussed above with regard to configuration of security sensors, SMA controller 120 is configured to detect available automated devices and display information regarding those devices. A user can then edit information about those devices and behavior of those devices through, for example, a touch screen interface coupled to SMA controller 120. In addition, a user can provide automation commands via accessing portal server 170 to modify those settings, or take immediate control of an automated device. Similarly, a user can take immediate control of automated devices from the touch screen of the SMA controller (e.g., through use of widgets such as “lights” and “thermostat,” illustrated in FIG. 4 ). Configuration information related to the automated devices can be stored in a memory of SMA controller 120 or in a server located in operator domain 160.
[0085] In this manner, embodiments of the present invention provide configurable control over a variety of SMA devices in the home domain using a single controller. A variety of different device protocols can be provided for through the use of plug-in modules. Further flexibility is provided through configurable set up and control of security and automation devices. Additional functionality is provided through the use of user-selectable and user-configurable widgets.
[0086] As mentioned above, an SMA controller 120 can be configured to provide a variety of sounds for different events triggered by sensor state changes. A typical home security system provides only a piezoelectric speaker that emits a series of beeps in response to all sensor events. Embodiments of the SMA controller associated with the present invention can emit a wide range of sounds that can be associated with sensor events due, in part, to inclusion of audio processor 225 and one or more associated speakers.
[0087] FIG. 10 is a simplified flow diagram illustrating an example of a process for associating event tones with events, in accord with embodiments of the present invention. During an initial configuration of the SMA controller, or subsequently, a user can select a zone or a device (e.g., individual sensors within a zone or a home automation device) to which an event tone will be associated (1010). Selection can be performed using a user interface displayed on a touchscreen display associated with the SMA controller. As discussed above, a zone can be a collection of one or more sensors related in some manner (e.g., upstairs windows, front door, and the like). The zone can have one or more events associated with state changes of individual sensors associated with that zone (e.g., door open and door close). In addition, an event can be associated with state changes of individual devices, such as a sensor or a home automation device.
[0088] An event can be selected for which an event tone will be associated (1015). A listing of available event tones can then be displayed and the user can determine whether a desired event tone is available on the list (1020). If the desired event tone is not available, then the user can be given the opportunity to download the desired event tone to the SMA controller (1025). For example, the user can access additional event tones from a server 165 in the operator domain, or access an event tone store or depository through WAN 152. In one embodiment, event tones are recorded in waveform audio file format (.wav) files. Such files can be downloaded to the SMA controller and then be made available to the user for association with the event.
[0089] A provider that makes event tones available in the operator domain or other repository can restrict access to those event tones. For example, an operator can divide customers having SMA controllers among service tiers associated with subscription rates. Customers who pay more for services may have access to a larger number of event tones through the provider. As another example, a provider can choose to restrict event tones according to those services the customer pays for. Thus, a customer will only have access to event tones associated with services the customer uses. Alternatively, a provider can use a combination of such methods to restrict access to event tones.
[0090] Once the desired event tone is selected, and downloaded, if necessary, then the event tone is associated with the selected event (1030). For example, logic in the SMA controller can make the association through a mapping file that provides a mapping between the selected event and the selected event tone file. Once the association has been made by the association logic, the associations can be saved in a memory of the SMA controller (e.g., the mapping file saved in memory 260) (1035). In addition, the event/event tone mappings can be stored on a server in the operator domain (e.g., database server 185).
[0091] After event tones have been associated with events, the SMA controller can monitor sensors for state changes (1040). If there is a sensor state change event (1045), then the SMA controller determines if there is an event tone that is associated with the sensor state change event (e.g., referencing the mapping file) (1050). If there is an associated event tone (1055), then the associated event tone is played on a speaker in the SMA controller or attached to the SMA controller, either directly or through a wireless connection (1060). If there is no associated event tone, then a default event tone can be played on the speaker (1065). An event tone is played on the speaker by the processor locating an event tone file associated with an event tone identifier. Event tone files are stored in a memory local to the SMA controller (e.g., memory 260). The processor interprets the digital data in the event tone file (e.g., a .wav file) and provides that interpreted data to the audio processor. The audio processor performs additional processing and provides the appropriate wave forms to the speaker.
[0092] Through such associations of event tones with events, a user of an SMA controller can customize the device to provide event alerts that are meaningful to the user and others in home domain 110. Thus, it can be made easier to distinguish between location and urgency of sensor events.
An Example Computing and Network Environment
[0093] As shown above, the present invention can be implemented using a variety of computer systems and networks. An example of one such computing and network environment is described below with reference to FIGS. 11 and 12 .
[0094] FIG. 11 depicts a block diagram of a computer system 1110 suitable for implementing aspects of the present invention (e.g., servers 165, portal server 170, backup server 175, telephony server 180, and database server 185). Computer system 1110 includes a bus 1112 which interconnects major subsystems of computer system 1110, such as a central processor 1114, a system memory 1117 (typically RAM, but which may also include ROM, flash RAM, or the like), an input/output controller 1118, an external audio device, such as a speaker system 1120 via an audio output interface 1122, an external device, such as a display screen 1124 via display adapter 1126, serial ports 1128 and 1130, a keyboard 1132 (interfaced with a keyboard controller 1133), a storage interface 1134, a floppy disk drive 1137 operative to receive a floppy disk 1138, a host bus adapter (HBA) interface card 1135A operative to connect with a Fibre Channel network 1190, a host bus adapter (HBA) interface card 1135B operative to connect to a SCSI bus 1139, and an optical disk drive 1140 operative to receive an optical disk 1142. Also included are a mouse 1146 (or other point-and-click device, coupled to bus 1112 via serial port 1128), a modem 1147 (coupled to bus 1112 via serial port 1130), and a network interface 1148 (coupled directly to bus 1112).
[0095] Bus 1112 allows data communication between central processor 1114 and system memory 1117, which may include read-only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown), as previously noted. The RAM is generally the main memory into which the operating system and application programs are loaded. The ROM or flash memory can contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with peripheral components. Applications resident with computer system 1110 are generally stored on and accessed via a computer-readable medium, such as a hard disk drive (e.g., fixed disk 1144), an optical drive (e.g., optical drive 1140), a floppy disk unit 1137, or other storage medium. Additionally, applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 1147 or interface 1148.
[0096] Storage interface 1134, as with the other storage interfaces of computer system 1110, can connect to a standard computer-readable medium for storage and/or retrieval of information, such as a fixed disk drive 1144. Fixed disk drive 1144 may be a part of computer system 1110 or may be separate and accessed through other interface systems. Modem 1147 may provide a direct connection to a remote server via a telephone link or to the Internet via an internet service provider (ISP). Network interface 1148 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence). Network interface 1148 may provide such connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection or the like.
[0097] Many other devices or subsystems (not shown) may be connected in a similar manner (e.g., document scanners, digital cameras and so on). Conversely, all of the devices shown in FIG. 11 need not be present to practice the present invention. The devices and subsystems can be interconnected in different ways from that shown in FIG. 11 . The operation of a computer system such as that shown in FIG. 11 is readily known in the art and is not discussed in detail in this application. Code to implement the present invention can be stored in computer-readable storage media such as one or more of system memory 1117, fixed disk 1144, optical disk 1142, or floppy disk 1138. The operating system provided on computer system 1110 may be MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, Linux®, or another known operating system.
[0098] Moreover, regarding the signals described herein, those skilled in the art will recognize that a signal can be directly transmitted from a first block to a second block, or a signal can be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified) between the blocks. Although the signals of the above described embodiment are characterized as transmitted from one block to the next, other embodiments of the present invention may include modified signals in place of such directly transmitted signals as long as the informational and/or functional aspect of the signal is transmitted between blocks. To some extent, a signal input at a second block can be conceptualized as a second signal derived from a first signal output from a first block due to physical limitations of the circuitry involved (e.g., there will inevitably be some attenuation and delay). Therefore, as used herein, a second signal derived from a first signal includes the first signal or any modifications to the first signal, whether due to circuit limitations or due to passage through other circuit elements which do not change the informational and/or final functional aspect of the first signal.
[0099] FIG. 12 is a block diagram depicting a network architecture 1200 in which client systems 1210, 1220 and 1230, as well as storage servers 1240A and 1240B (any of which can be implemented using computer system 1110), are coupled to a network 1250. Storage server 1240A is further depicted as having storage devices 1260A(1)-(N) directly attached, and storage server 1240B is depicted with storage devices 1260B(1)-(N) directly attached. Storage servers 1240A and 1240B are also connected to a SAN fabric 1270, although connection to a storage area network is not required for operation of the invention. SAN fabric 1270 supports access to storage devices 1280(1)-(N) by storage servers 1240A and 1240B, and so by client systems 1210, 1220 and 1230 via network 1250. Intelligent storage array 1290 is also shown as an example of a specific storage device accessible via SAN fabric 1270.
[0100] With reference to computer system 1110, modem 1147, network interface 1148 or some other method can be used to provide connectivity from each of client computer systems 1210, 1220 and 1230 to network 1250. Client systems 1210, 1220 and 1230 are able to access information on storage server 1240A or 1240B using, for example, a web browser or other client software (not shown). Such a client allows client systems 1210, 1220 and 1230 to access data hosted by storage server 1240A or 1240B or one of storage devices 1260A(1)-(N), 1260B(1)-(N), 1280(1)-(N) or intelligent storage array 1290. FIG. 12 depicts the use of a network such as the Internet for exchanging data, but the present invention is not limited to the Internet or any particular network-based environment.
Other Embodiments
[0101] The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.
[0102] The foregoing describes embodiments including components contained within other components (e.g., the various elements shown as components of computer system 1110). Such architectures are merely examples, and, in fact, many other architectures can be implemented which achieve the same functionality. In an abstract but still definite sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.
[0103] The foregoing detailed description has set forth various embodiments of the present invention via the use of block diagrams, flowcharts, and examples. It will be understood by those within the art that each block diagram component, flowchart step, operation and/or component illustrated by the use of examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof. For example, specific electronic components can be employed in an application specific integrated circuit or similar or related circuitry for implementing the functions associated with one or more of the described functional blocks.
[0104] The present invention has been described in the context of fully functional computer systems; however, those skilled in the art will appreciate that the present invention is capable of being distributed as a program product in a variety of forms, and that the present invention applies equally regardless of the particular type of computer-readable media used to actually carry out the distribution. Examples of computer-readable media include computer-readable storage media, as well as media storage and distribution systems developed in the future.
[0105] The above-discussed embodiments can be implemented by software modules that perform one or more tasks associated with the embodiments. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage media such as magnetic floppy disks, hard disks, semiconductor memory (e.g., RAM, ROM, and flash-type media), optical discs (e.g., CD-ROMs, CD-Rs, and DVDs), or other types of memory modules. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention can also include a semiconductor-based memory, which may be permanently, removably or remotely coupled to a microprocessor/memory system. Thus, the modules can be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein.
[0106] The above description is intended to be illustrative of the invention and should not be taken to be limiting. Other embodiments within the scope of the present invention are possible. Those skilled in the art will readily implement the steps necessary to provide the structures and the methods disclosed herein, and will understand that the process parameters and sequence of steps are given by way of example only and can be varied to achieve the desired structure as well as modifications that are within the scope of the invention. Variations and modifications of the embodiments disclosed herein can be made based on the description set forth herein, without departing from the scope of the invention.
[0107] Consequently, the invention is intended to be limited only by the scope of the appended claims, giving full cognizance to equivalents in all respects.
Claims
What is claimed is:
1. An apparatus comprising:
a memory storing configuration information for one or more devices comprising one or more security sensors, a security system, and monitoring devices, and mapping information associating the one or more devices, at least one zone, a state change of the one or more devices, and one or more device events with corresponding event tone identifiers, wherein a device event of the one or more device events comprises an action corresponding to a device, wherein a zone comprises a set of the one or more devices having a common characteristic, wherein the configuration information includes a zone function assigned to each security sensor and configuring actions and reactions of the corresponding security sensor and the security system;
an audio processor coupled to a speaker; and
a processor coupled to the memory and the audio processor, and configured to interpret an event signal corresponding to the one or more device events, the interpreting performed in accord with the configuration information, determine if a first event tone identifier is associated with the interpreted event signal, the determining performed using the mapping information, play a first event tone associated with the first event tone identifier using the audio processor, if the first event tone identifier is associated with the interpreted event signal, and play a default event tone using the audio processor, if no first event tone identifier is associated with the interpreted event signal.
2. The apparatus of claim 1, comprising a display coupled to the processor, wherein the processor is configured to display the mapping information associating the device events with the corresponding event tone identifier, using the display.
3. The apparatus of claim 1, comprising an input device coupled to the processor, wherein the processor is configured to receive, from the input device, mapping information associating a selected event tone identifier with a selected device event, modify the mapping information associating the device events with corresponding event tone identifiers, using the received mapping information, and store the modified mapping information in the memory.
4. The apparatus of claim 3, comprising a display coupled to the processor, wherein the memory stores one or more event tone files, wherein each of the one or more event tone files has a corresponding event tone identifier, wherein the processor is configured to provide a list of event tone identifiers corresponding to the one or more event tone files stored in the memory, using the display, wherein the selected event tone identifier is selected from the list of event tone identifiers.
5. The apparatus of claim 4, comprising a communication interface, coupled to the processor, and configured to communicate with a remote server, wherein the processor is configured to download a selected event tone file from the remote server using the communication interface, store the selected event tone file in the memory, and add an event tone identifier for the selected event tone file to the list of event tone identifiers.
6. The apparatus of claim 5, wherein the processor is configured to:
download a list of available event tone identifiers each corresponding to an available event tone file accessible through the remote server;
display the list of available event tone identifiers using the display; and
provide for selection of an available event tone identifier from the list of available event tone identifiers, wherein the selected event tone file corresponds to the selected available event tone identifier, and the list of available event tone identifiers is populated according to one or more of a service tier associated with a user of the apparatus, services provided to the apparatus, and programs installed on the apparatus.
7. The apparatus of claim 1, comprising a communication interface, coupled to the processor, and configured to communicate with a remote server, wherein the processor is configured to transmit the mapping information associating the device events with the corresponding event tone identifiers to the remote server, using the communication interface, wherein the remote server stores the mapping information.
8. A method comprising:
interpreting an event signal corresponding to one or more device events and received from the one or more devices, wherein the one or more devices comprise one or more of security sensors, a security system, and monitoring devices, and the interpreting is performed in accord with configuration information for the one or more devices, wherein the configuration information includes a zone function assigned to each security sensor and configuring actions and reactions of the corresponding security sensor and the security system;
determining whether a first event tone identifier is associated with the interpreted event signal, wherein the determining is performed using mapping information associating the one or more devices, at least one zone, a state change of the one or more devices, and the one or more device events with corresponding event tone identifiers, wherein a device event of the one or more device events comprises an action corresponding to a device, wherein a zone comprises a set of the one or more devices having a common characteristic, the one or more device events including defining an event of the one or more device events using state information of a plurality of the one or more devices;
playing a first event tone associated with the first event tone identifier, if the first event tone identifier is associated with the interpreted event signal;
playing a default event tone, if no first event tone identifier is associated with the interpreted event signal.
9. The method of claim 8, comprising displaying the mapping information associating the device events with the corresponding event tone identifier.
10. The method of claim 8, comprising:
receiving mapping information associating a selected event tone identifier with a selected device event;
modifying the mapping information associating the device events with corresponding event tone identifiers with the received mapping information; and
storing the modified mapping information.
11. The method of claim 10, comprising selecting the selected event tone identifier from a list of event tone identifiers, wherein each event tone identifier corresponds to an event tone file stored in a memory.
12. The method of claim 11, comprising:
downloading a selected event tone file from a remote server;
storing the selected event tone file in the memory; and
adding an event tone identifier for the selected event tone file to the list of event tone identifiers.
13. The method of claim 12, comprising:
downloading a list of available event tone identifiers each corresponding to an available event tone file accessible from the remote server;
displaying the list of available event tone identifiers; and
selecting an available event tone identifier from the list of available event tone identifiers, wherein the selected event tone file corresponds to the selected available event tone identifier, and the list of available event tone identifiers is populated according to one or more of a service tier associated with a user of a device executing the method, services provided to the device executing the method, and programs installed on the device executing the method.
14. The method of claim 8, comprising transmitting the mapping information associating the one or more device events with corresponding event tone identifiers to a remote server, wherein the remote server stores the mapping information.
15. An apparatus comprising:
means for storing configuration information for one or more devices comprising one or more security sensors, a security system, and monitoring devices, and mapping information associating the one or more devices, at least one zone, a state change of the one or more devices, and one or more device events with corresponding event tone identifiers, wherein a device event of the one or more device events comprises an action corresponding to a device, wherein a zone comprises a set of the one or more devices having a common characteristic, wherein the configuration information includes a zone function assigned to each security sensor and configuring actions and reactions of the corresponding security sensor and the security system;
an audio processor coupled to a speaker;
means for interpreting an event signal corresponding to the one or more device events, the interpreting performed in accord with the configuration information;
means for determining if a first event tone identifier is associated with the interpreted event signal, the determining performed using the mapping information;
means for playing a first event tone associated with the first event tone identifier using the audio processor, if the first event tone identifier is associated with the interpreted event signal;
means for playing a default event tone using the audio processor, if no first event tone identifier is associated with the interpreted event signal.
16. The apparatus of claim 15, comprising means for displaying the mapping information associating the device events with the corresponding event tone identifier.
17. The apparatus of claim 15, comprising:
means for receiving mapping information associating a selected event tone identifier with a selected device event;
means for modifying the mapping information associating the device events with corresponding event tone identifiers, using the received mapping information; and
means for storing the modified mapping information.
18. The apparatus of claim 17, comprising:
means for storing one or more event tone files, wherein each of the one or more event tone files has a corresponding event tone identifier; and
means for providing a list of event tone identifiers corresponding to the one or more event tone files stored in the memory, wherein the selected event tone identifier is selected from the list of event tone identifiers.
19. The apparatus of claim 18, comprising:
means for communicating with a remote server;
means for downloading a selected event tone file from the remote server using the means for communicating with the remote server;
means for storing the selected event tone file; and
means for adding an event tone identifier for the selected event tone file to the list of event tone identifiers.
20. The apparatus of claim 15, comprising:
means for communicating with a remote server; and
means for transmitting the mapping information associating the device events with the corresponding event tone identifiers to the remote server, using the means for communicating with the remote server, wherein the remote server stores the mapping information.
Patent Citations (841)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4141006(A) | 1979-02-01 | Braxton | Applicant |
| US4257038(A) | 1981-03-01 | Rounds et al. | Applicant |
| US4363031(A) | 1982-12-01 | Reinowitz | Applicant |
| US4520503(A) | 1985-05-01 | Kirst et al. | Applicant |
| US4559526(A) | 1985-12-01 | Tani et al. | Applicant |
| US4574305(A) | 1986-03-01 | Campbell et al. | Applicant |
| US4581606(A) | 1986-04-01 | Mallory | Applicant |
| USD284084(S) | 1986-06-01 | Ferrara, Jr. | Applicant |
| US4641127(A) | 1987-02-01 | Hogan et al. | Applicant |
| US4652859(A) | 1987-03-01 | Van Wienen | Applicant |
| US4694282(A) | 1987-09-01 | Tamura et al. | Applicant |
| US4730184(A) | 1988-03-01 | Bach | Applicant |
| US4754261(A) | 1988-06-01 | Marino | Applicant |
| US4779007(A) | 1988-10-01 | Schlanger et al. | Applicant |
| US4801924(A) | 1989-01-01 | Burgmann et al. | Applicant |
| US4812820(A) | 1989-03-01 | Chatwin | Applicant |
| US4833449(A) | 1989-05-01 | Gaffigan | Applicant |
| US4855713(A) | 1989-08-01 | Brunius | Applicant |
| US4860185(A) | 1989-08-01 | Brewer et al. | Applicant |
| US4897630(A) | 1990-01-01 | Nykerk | Examiner |
| US4918623(A) | 1990-04-01 | Lockitt et al. | Applicant |
| US4951029(A) | 1990-08-01 | Severson | Applicant |
| US4959713(A) | 1990-09-01 | Morotomi et al. | Applicant |
| US4993059(A) | 1991-02-01 | Smith et al. | Applicant |
| US4994787(A) | 1991-02-01 | Kratt et al. | Applicant |
| US5023901(A) | 1991-06-01 | Sloan et al. | Applicant |
| US5086385(A) | 1992-02-01 | Launey et al. | Applicant |
| US5091780(A) | 1992-02-01 | Pomerleau | Applicant |
| US5132968(A) | 1992-07-01 | Cephus | Applicant |
| US5134644(A) | 1992-07-01 | Garton et al. | Applicant |
| US5159315(A) | 1992-10-01 | Schultz et al. | Applicant |
| US5160879(A) | 1992-11-01 | Tortola et al. | Applicant |
| USD337569(S) | 1993-07-01 | Kando | Applicant |
| US5227776(A) | 1993-07-01 | Starefoss | Applicant |
| US5237305(A) | 1993-08-01 | Ishikuro et al. | Applicant |
| US5319394(A) | 1994-06-01 | Dukek | Applicant |
| US5319698(A) | 1994-06-01 | Glidewell et al. | Applicant |
| US5334974(A) | 1994-08-01 | Simms et al. | Applicant |
| US5438607(A) | 1995-08-01 | Przygoda, Jr. et al. | Applicant |
| US5446445(A) | 1995-08-01 | Bloomfield et al. | Applicant |
| US5465081(A) | 1995-11-01 | Todd | Applicant |
| US5471194(A) | 1995-11-01 | Guscott | Applicant |
| US5486812(A) | 1996-01-01 | Todd | Applicant |
| US5499014(A) | 1996-03-01 | Greenwaldt | Applicant |
| US5499196(A) | 1996-03-01 | Pacheco | Applicant |
| US5519878(A) | 1996-05-01 | Dolin, Jr. | Applicant |
| US5578989(A) | 1996-11-01 | Pedtke | Applicant |
| US5579197(A) | 1996-11-01 | Mengelt et al. | Applicant |
| USD377034(S) | 1996-12-01 | Matsushita | Applicant |
| US5587705(A) | 1996-12-01 | Morris | Applicant |
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5625338(A) | 1997-04-01 | Pildner et al. | Applicant |
| US5630216(A) | 1997-05-01 | McEwan | Applicant |
| US5651070(A) | 1997-07-01 | Blunt | Applicant |
| USD389501(S) | 1998-01-01 | Mascarenas, Sr. et al. | Applicant |
| US5715394(A) | 1998-02-01 | Jabs | Applicant |
| US5717379(A) | 1998-02-01 | Peters | Applicant |
| US5717578(A) | 1998-02-01 | Afzal | Applicant |
| US5731756(A) | 1998-03-01 | Roddy | Applicant |
| US5777551(A) | 1998-07-01 | Hess | Applicant |
| US5874952(A) | 1999-02-01 | Morgan | Applicant |
| US5886894(A) | 1999-03-01 | Rakoff | Applicant |
| US5892442(A) | 1999-04-01 | Ozery | Applicant |
| US5907279(A) | 1999-05-01 | Bruins et al. | Applicant |
| US5909183(A) | 1999-06-01 | Borgstahl et al. | Applicant |
| US5914655(A) | 1999-06-01 | Clifton et al. | Applicant |
| US5943394(A) | 1999-08-01 | Ader et al. | Applicant |
| US5955946(A) | 1999-09-01 | Beheshti et al. | Applicant |
| US5958053(A) | 1999-09-01 | Denker | Applicant |
| US5959528(A) | 1999-09-01 | Right et al. | Applicant |
| US5963916(A) | 1999-10-01 | Kaplan | Applicant |
| USD416910(S) | 1999-11-01 | Vasquez | Applicant |
| US5991795(A) | 1999-11-01 | Howard et al. | Applicant |
| US6032036(A) | 2000-02-01 | Maystre et al. | Applicant |
| US6037991(A) | 2000-03-01 | Thro et al. | Applicant |
| US6038289(A) | 2000-03-01 | Sands | Applicant |
| US6040770(A) | 2000-03-01 | Britton | Applicant |
| US6049272(A) | 2000-04-01 | Lee et al. | Applicant |
| US6049273(A) | 2000-04-01 | Hess | Applicant |
| US6052052(A) | 2000-04-01 | Delmonaco | Applicant |
| US6060994(A) | 2000-05-01 | Chen | Applicant |
| US6067346(A) | 2000-05-01 | Akhteruzzaman et al. | Applicant |
| US6067440(A) | 2000-05-01 | Diefes | Applicant |
| US6078253(A) | 2000-06-01 | Fowler | Applicant |
| US6078257(A) | 2000-06-01 | Ferraro | Applicant |
| US6085030(A) | 2000-07-01 | Whitehead et al. | Applicant |
| US6104785(A) | 2000-08-01 | Chen | Applicant |
| US6134591(A) | 2000-10-01 | Nickles | Applicant |
| US6138249(A) | 2000-10-01 | Nolet | Applicant |
| US6140987(A) | 2000-10-01 | Stein et al. | Applicant |
| US6181341(B1) | 2001-01-01 | Shinagawa | Applicant |
| US6192418(B1) | 2001-02-01 | Hale et al. | Applicant |
| US6198475(B1) | 2001-03-01 | Kunimatsu et al. | Applicant |
| US6198479(B1) | 2001-03-01 | Humpleman et al. | Applicant |
| US6208247(B1) | 2001-03-01 | Agre et al. | Applicant |
| US6211783(B1) | 2001-04-01 | Wang | Applicant |
| US6219677(B1) | 2001-04-01 | Howard | Applicant |
| US6246320(B1) | 2001-06-01 | Monroe | Applicant |
| US6271752(B1) | 2001-08-01 | Vaios | Applicant |
| US6281790(B1) | 2001-08-01 | Kimmel et al. | Applicant |
| US6282569(B1) | 2001-08-01 | Wallis et al. | Applicant |
| US6286038(B1) | 2001-09-01 | Reichmeyer et al. | Applicant |
| US6288716(B1) | 2001-09-01 | Humpleman et al. | Applicant |
| US6289382(B1) | 2001-09-01 | Bowman-Amuah | Applicant |
| US6295346(B1) | 2001-09-01 | Markowitz et al. | Applicant |
| US6320506(B1) | 2001-11-01 | Ferraro | Applicant |
| USD451529(S) | 2001-12-01 | Vasquez | Applicant |
| US6331122(B1) | 2001-12-01 | Wu | Applicant |
| US6351829(B1) | 2002-02-01 | Dupont et al. | Applicant |
| US6353891(B1) | 2002-03-01 | Borella et al. | Applicant |
| US6363417(B1) | 2002-03-01 | Howard et al. | Applicant |
| US6363422(B1) | 2002-03-01 | Hunter et al. | Applicant |
| US6369695(B1) | 2002-04-01 | Horon | Applicant |
| US6369705(B1) | 2002-04-01 | Kennedy | Applicant |
| US6370436(B1) | 2002-04-01 | Howard et al. | Applicant |
| US6374079(B1) | 2002-04-01 | Hsu | Applicant |
| US6377861(B1) | 2002-04-01 | York | Applicant |
| US6385772(B1) | 2002-05-01 | Courtney | Applicant |
| US6400265(B1) | 2002-06-01 | Saylor et al. | Applicant |
| USD460472(S) | 2002-07-01 | Wang | Applicant |
| US6418037(B1) | 2002-07-01 | Zhang | Applicant |
| US6433683(B1) | 2002-08-01 | Robinson | Applicant |
| USD464328(S) | 2002-10-01 | Vasquez et al. | Applicant |
| USD464948(S) | 2002-10-01 | Vasquez et al. | Applicant |
| US6462507(B2) | 2002-10-01 | Fisher et al. | Applicant |
| US6462663(B1) | 2002-10-01 | Wilson et al. | Applicant |
| US6467084(B1) | 2002-10-01 | Howard et al. | Applicant |
| US6480901(B1) | 2002-11-01 | Weber et al. | Applicant |
| US6493020(B1) | 2002-12-01 | Stevenson et al. | Applicant |
| US6496927(B1) | 2002-12-01 | McGrane et al. | Applicant |
| US6529723(B1) | 2003-03-01 | Bentley | Applicant |
| US6542075(B2) | 2003-04-01 | Barker et al. | Applicant |
| US6553336(B1) | 2003-04-01 | Johnson et al. | Applicant |
| US6563800(B1) | 2003-05-01 | Salo et al. | Applicant |
| US6574234(B1) | 2003-06-01 | Myer et al. | Applicant |
| US6580950(B1) | 2003-06-01 | Johnson et al. | Applicant |
| US6587455(B1) | 2003-07-01 | Ray et al. | Applicant |
| US6587736(B2) | 2003-07-01 | Howard et al. | Applicant |
| US6591094(B1) | 2003-07-01 | Bentley | Applicant |
| US6597703(B1) | 2003-07-01 | Li et al. | Applicant |
| US6601086(B1) | 2003-07-01 | Howard et al. | Applicant |
| US6603488(B2) | 2003-08-01 | Humpleman et al. | Applicant |
| US6609127(B1) | 2003-08-01 | Lee et al. | Applicant |
| US6615088(B1) | 2003-09-01 | Myer et al. | Applicant |
| US6621827(B1) | 2003-09-01 | Rezvani et al. | Applicant |
| US6624750(B1) | 2003-09-01 | Marman et al. | Applicant |
| US6631416(B2) | 2003-10-01 | Bendinelli et al. | Applicant |
| US6636893(B1) | 2003-10-01 | Fong | Applicant |
| US6643652(B2) | 2003-11-01 | Helgeson et al. | Applicant |
| US6643669(B1) | 2003-11-01 | Novak et al. | Applicant |
| US6648682(B1) | 2003-11-01 | Wu | Applicant |
| US6658091(B1) | 2003-12-01 | Naidoo et al. | Applicant |
| US6661340(B1) | 2003-12-01 | Saylor et al. | Applicant |
| US6686838(B1) | 2004-02-01 | Rezvani et al. | Applicant |
| US6690411(B2) | 2004-02-01 | Naidoo et al. | Applicant |
| US6693530(B1) | 2004-02-01 | Dowens et al. | Applicant |
| US6693545(B2) | 2004-02-01 | Brown et al. | Applicant |
| US6697103(B1) | 2004-02-01 | Fernandez et al. | Applicant |
| US6704786(B1) | 2004-03-01 | Gupta et al. | Applicant |
| US6721689(B2) | 2004-04-01 | Markle et al. | Applicant |
| US6721747(B2) | 2004-04-01 | Lipkin | Applicant |
| US6738824(B1) | 2004-05-01 | Blair | Applicant |
| US6754717(B1) | 2004-06-01 | Day, III et al. | Applicant |
| US6756896(B2) | 2004-06-01 | Ford | Applicant |
| US6756998(B1) | 2004-06-01 | Bilger | Applicant |
| US6762686(B1) | 2004-07-01 | Tabe | Applicant |
| US6778085(B2) | 2004-08-01 | Faulkner et al. | Applicant |
| US6781509(B1) | 2004-08-01 | Oppedahl et al. | Applicant |
| US6785542(B1) | 2004-08-01 | Blight et al. | Applicant |
| US6789147(B1) | 2004-09-01 | Kessler et al. | Applicant |
| US6795322(B2) | 2004-09-01 | Aihara et al. | Applicant |
| US6798344(B2) | 2004-09-01 | Faulkner et al. | Applicant |
| US6810409(B1) | 2004-10-01 | Fry et al. | Applicant |
| US6826233(B1) | 2004-11-01 | Oosawa | Applicant |
| US6850252(B1) | 2005-02-01 | Hoffberg | Applicant |
| US6856236(B2) | 2005-02-01 | Christensen et al. | Applicant |
| US6865690(B2) | 2005-03-01 | Kocin | Applicant |
| US6873256(B2) | 2005-03-01 | Lemelson et al. | Applicant |
| USD504889(S) | 2005-05-01 | Andre et al. | Applicant |
| US6891838(B1) | 2005-05-01 | Petite et al. | Applicant |
| US6912429(B1) | 2005-06-01 | Bilger | Applicant |
| US6918112(B2) | 2005-07-01 | Bourke-Dunphy et al. | Applicant |
| US6928148(B2) | 2005-08-01 | Simon et al. | Applicant |
| US6930599(B2) | 2005-08-01 | Naidoo et al. | Applicant |
| US6930730(B2) | 2005-08-01 | Maxon et al. | Applicant |
| US6931445(B2) | 2005-08-01 | Davis | Applicant |
| US6943681(B2) | 2005-09-01 | Rezvani et al. | Applicant |
| US6956477(B2) | 2005-10-01 | Chun | Applicant |
| US6959341(B1) | 2005-10-01 | Leung | Applicant |
| US6959393(B2) | 2005-10-01 | Hollis et al. | Applicant |
| US6963981(B1) | 2005-11-01 | Bailey et al. | Applicant |
| US6965313(B1) | 2005-11-01 | Saylor et al. | Applicant |
| US6970183(B1) | 2005-11-01 | Monroe | Applicant |
| US6972676(B1) | 2005-12-01 | Kimmel et al. | Applicant |
| US6975220(B1) | 2005-12-01 | Foodman et al. | Applicant |
| US6977485(B1) | 2005-12-01 | Wei | Applicant |
| US6990591(B1) | 2006-01-01 | Pearson | Applicant |
| US7015806(B2) | 2006-03-01 | Naidoo et al. | Applicant |
| US7016970(B2) | 2006-03-01 | Harumoto et al. | Applicant |
| US7020697(B1) | 2006-03-01 | Goodman et al. | Applicant |
| US7020701(B1) | 2006-03-01 | Gelvin et al. | Applicant |
| US7024676(B1) | 2006-04-01 | Klopfenstein | Applicant |
| US7030752(B2) | 2006-04-01 | Tyroler | Applicant |
| US7032002(B1) | 2006-04-01 | Rezvani et al. | Applicant |
| US7034681(B2) | 2006-04-01 | Yamamoto et al. | Applicant |
| US7035907(B1) | 2006-04-01 | Decasper et al. | Applicant |
| US7039391(B2) | 2006-05-01 | Rezvani et al. | Applicant |
| US7043537(B1) | 2006-05-01 | Pratt | Applicant |
| US7047088(B2) | 2006-05-01 | Nakamura et al. | Applicant |
| US7047092(B2) | 2006-05-01 | Wimsatt | Applicant |
| US7053764(B2) | 2006-05-01 | Stilp | Applicant |
| US7072934(B2) | 2006-07-01 | Helgeson et al. | Applicant |
| US7075429(B2) | 2006-07-01 | Marshall | Applicant |
| US7079020(B2) | 2006-07-01 | Stilp | Applicant |
| US7080046(B1) | 2006-07-01 | Rezvani et al. | Applicant |
| US7081813(B2) | 2006-07-01 | Winick et al. | Applicant |
| US7082460(B2) | 2006-07-01 | Hansen et al. | Applicant |
| US7085937(B1) | 2006-08-01 | Rezvani et al. | Applicant |
| US7099944(B1) | 2006-08-01 | Anschutz et al. | Applicant |
| US7099994(B2) | 2006-08-01 | Thayer et al. | Applicant |
| US7103152(B2) | 2006-09-01 | Naidoo et al. | Applicant |
| US7106176(B2) | 2006-09-01 | La et al. | Applicant |
| US7107322(B1) | 2006-09-01 | Freeny, Jr. | Applicant |
| US7110774(B1) | 2006-09-01 | Davis et al. | Applicant |
| US7113090(B1) | 2006-09-01 | Saylor et al. | Applicant |
| US7113099(B2) | 2006-09-01 | Tyroler et al. | Applicant |
| US7114554(B2) | 2006-10-01 | Bergman et al. | Applicant |
| US7119674(B2) | 2006-10-01 | Sefton | Applicant |
| US7120232(B2) | 2006-10-01 | Naidoo et al. | Applicant |
| US7120233(B2) | 2006-10-01 | Naidoo et al. | Applicant |
| US7130383(B2) | 2006-10-01 | Naidoo et al. | Applicant |
| US7130585(B1) | 2006-10-01 | Ollis et al. | Applicant |
| US7148810(B2) | 2006-12-01 | Bhat | Applicant |
| US7149798(B2) | 2006-12-01 | Rezvani et al. | Applicant |
| US7149814(B2) | 2006-12-01 | Neufeld et al. | Applicant |
| US7164907(B2) | 2007-01-01 | Cochran et al. | Applicant |
| US7166987(B2) | 2007-01-01 | Lee et al. | Applicant |
| US7174564(B1) | 2007-02-01 | Weatherspoon et al. | Applicant |
| US7183907(B2) | 2007-02-01 | Simon et al. | Applicant |
| US7203486(B2) | 2007-04-01 | Patel | Applicant |
| US7209945(B2) | 2007-04-01 | Hicks et al. | Applicant |
| US7212570(B2) | 2007-05-01 | Akiyama et al. | Applicant |
| US7218217(B2) | 2007-05-01 | Adonailo et al. | Applicant |
| US7222359(B2) | 2007-05-01 | Freund et al. | Applicant |
| US7237267(B2) | 2007-06-01 | Rayes et al. | Applicant |
| US7248161(B2) | 2007-07-01 | Spoltore et al. | Applicant |
| US7249317(B1) | 2007-07-01 | Nakagawa et al. | Applicant |
| US7250854(B2) | 2007-07-01 | Rezvani et al. | Applicant |
| US7250859(B2) | 2007-07-01 | Martin et al. | Applicant |
| US7254779(B1) | 2007-08-01 | Rezvani et al. | Applicant |
| US7262690(B2) | 2007-08-01 | Heaton et al. | Applicant |
| US7298253(B2) | 2007-11-01 | Petricoin et al. | Applicant |
| US7305461(B2) | 2007-12-01 | Ullman | Applicant |
| US7310115(B2) | 2007-12-01 | Tanimoto | Applicant |
| US7313102(B2) | 2007-12-01 | Stephenson et al. | Applicant |
| USD558460(S) | 2008-01-01 | Yu et al. | Applicant |
| USD558756(S) | 2008-01-01 | Andre et al. | Applicant |
| US7337217(B2) | 2008-02-01 | Wang | Applicant |
| US7337473(B2) | 2008-02-01 | Chang et al. | Applicant |
| US7343619(B2) | 2008-03-01 | Ofek et al. | Applicant |
| US7349761(B1) | 2008-03-01 | Cruse | Applicant |
| US7349967(B2) | 2008-03-01 | Wang | Applicant |
| US7367045(B2) | 2008-04-01 | Ofek et al. | Applicant |
| US7370115(B2) | 2008-05-01 | Bae et al. | Applicant |
| US7383339(B1) | 2008-06-01 | Meenan et al. | Applicant |
| US7403838(B2) | 2008-07-01 | Deen et al. | Applicant |
| US7409045(B2) | 2008-08-01 | Naidoo et al. | Applicant |
| US7409451(B1) | 2008-08-01 | Meenan et al. | Applicant |
| US7412447(B2) | 2008-08-01 | Hilbert et al. | Applicant |
| US7425101(B2) | 2008-09-01 | Cheng | Applicant |
| US7428585(B1) | 2008-09-01 | Owens, II et al. | Applicant |
| US7430614(B2) | 2008-09-01 | Shen et al. | Applicant |
| US7437753(B2) | 2008-10-01 | Nahum | Applicant |
| US7440434(B2) | 2008-10-01 | Chaskar et al. | Applicant |
| US7457869(B2) | 2008-11-01 | Kernan | Applicant |
| US7469139(B2) | 2008-12-01 | Van | Applicant |
| US7469294(B1) | 2008-12-01 | Luo et al. | Applicant |
| US7469381(B2) | 2008-12-01 | Ording | Applicant |
| USD584738(S) | 2009-01-01 | Kim et al. | Applicant |
| USD585399(S) | 2009-01-01 | Hwang | Applicant |
| US7479949(B2) | 2009-01-01 | Jobs et al. | Applicant |
| US7480713(B2) | 2009-01-01 | Ullman | Applicant |
| US7480724(B2) | 2009-01-01 | Zimler et al. | Applicant |
| US7498695(B2) | 2009-03-01 | Gaudreau et al. | Applicant |
| US7506052(B2) | 2009-03-01 | Qian et al. | Applicant |
| US7509687(B2) | 2009-03-01 | Ofek et al. | Applicant |
| US7511614(B2) | 2009-03-01 | Stilp et al. | Applicant |
| US7512965(B1) | 2009-03-01 | Amdur et al. | Applicant |
| US7526539(B1) | 2009-04-01 | Hsu | Applicant |
| US7526762(B1) | 2009-04-01 | Astala et al. | Applicant |
| US7528723(B2) | 2009-05-01 | Fast et al. | Applicant |
| US7551071(B2) | 2009-06-01 | Bennett, III | Applicant |
| US7554934(B2) | 2009-06-01 | Abraham et al. | Applicant |
| US7558379(B2) | 2009-07-01 | Winick | Applicant |
| US7568018(B1) | 2009-07-01 | Hove et al. | Applicant |
| US7571459(B2) | 2009-08-01 | Ganesh et al. | Applicant |
| US7577420(B2) | 2009-08-01 | Srinivasan et al. | Applicant |
| US7587464(B2) | 2009-09-01 | Moorer et al. | Applicant |
| USD602014(S) | 2009-10-01 | Andre et al. | Applicant |
| USD602015(S) | 2009-10-01 | Andre et al. | Applicant |
| USD602017(S) | 2009-10-01 | Andre et al. | Applicant |
| USD602486(S) | 2009-10-01 | Andre et al. | Applicant |
| USD602487(S) | 2009-10-01 | Maskatia | Applicant |
| US7619512(B2) | 2009-11-01 | Trundle et al. | Applicant |
| US7620427(B2) | 2009-11-01 | Shanahan | Applicant |
| US7627665(B2) | 2009-12-01 | Barker et al. | Applicant |
| US7633385(B2) | 2009-12-01 | Cohn et al. | Applicant |
| US7634519(B2) | 2009-12-01 | Creamer et al. | Applicant |
| US7651530(B2) | 2010-01-01 | Winick | Applicant |
| US7653911(B2) | 2010-01-01 | Doshi et al. | Applicant |
| US7681201(B2) | 2010-03-01 | Dale et al. | Applicant |
| US7697028(B1) | 2010-04-01 | Johnson | Applicant |
| US7701970(B2) | 2010-04-01 | Krits et al. | Applicant |
| USD615083(S) | 2010-05-01 | Andre et al. | Applicant |
| US7711796(B2) | 2010-05-01 | Gutt et al. | Applicant |
| US7734020(B2) | 2010-06-01 | Elliot et al. | Applicant |
| US7734286(B2) | 2010-06-01 | Almeda et al. | Applicant |
| US7734906(B2) | 2010-06-01 | Orlando et al. | Applicant |
| US7739596(B2) | 2010-06-01 | Clarke-Martin et al. | Applicant |
| US7751409(B1) | 2010-07-01 | Carolan | Applicant |
| US7787863(B2) | 2010-08-01 | Groenendaal et al. | Applicant |
| USD624896(S) | 2010-10-01 | Park et al. | Applicant |
| USD626437(S) | 2010-11-01 | Lee et al. | Applicant |
| US7827252(B2) | 2010-11-01 | Hopmann et al. | Applicant |
| US7855635(B2) | 2010-12-01 | Cohn et al. | Applicant |
| US7859404(B2) | 2010-12-01 | Chul et al. | Applicant |
| US7882537(B2) | 2011-02-01 | Okajo et al. | Applicant |
| US7884855(B2) | 2011-02-01 | Ortiz | Applicant |
| US7890612(B2) | 2011-02-01 | Todd et al. | Applicant |
| US7911341(B2) | 2011-03-01 | Raji et al. | Applicant |
| USD636769(S) | 2011-04-01 | Wood et al. | Applicant |
| US7921686(B2) | 2011-04-01 | Bagepalli et al. | Applicant |
| USD637596(S) | 2011-05-01 | Akana et al. | Applicant |
| USD639805(S) | 2011-06-01 | Song et al. | Applicant |
| USD640663(S) | 2011-06-01 | Arnholt et al. | Applicant |
| US7956736(B2) | 2011-06-01 | Cohn et al. | Applicant |
| US7970863(B1) | 2011-06-01 | Fontaine | Applicant |
| USD641018(S) | 2011-07-01 | Lee et al. | Applicant |
| US7974235(B2) | 2011-07-01 | Ghozati et al. | Applicant |
| USD642563(S) | 2011-08-01 | Akana et al. | Applicant |
| US8001219(B2) | 2011-08-01 | Moorer et al. | Applicant |
| USD645015(S) | 2011-09-01 | Lee et al. | Applicant |
| USD645435(S) | 2011-09-01 | Kim et al. | Applicant |
| USD645833(S) | 2011-09-01 | Seflic et al. | Applicant |
| US8022833(B2) | 2011-09-01 | Cho | Applicant |
| US8028041(B2) | 2011-09-01 | Olliphant et al. | Applicant |
| US8042049(B2) | 2011-10-01 | Killian et al. | Applicant |
| US8046411(B2) | 2011-10-01 | Hayashi et al. | Applicant |
| USD650381(S) | 2011-12-01 | Park et al. | Applicant |
| US8073931(B2) | 2011-12-01 | Dawes et al. | Applicant |
| US8086702(B2) | 2011-12-01 | Baum et al. | Applicant |
| US8086703(B2) | 2011-12-01 | Baum et al. | Applicant |
| USD654460(S) | 2012-02-01 | Kim et al. | Applicant |
| USD654497(S) | 2012-02-01 | Lee | Applicant |
| US8122131(B2) | 2012-02-01 | Baum et al. | Applicant |
| US8125184(B2) | 2012-02-01 | Raji et al. | Applicant |
| USD656137(S) | 2012-03-01 | Chung et al. | Applicant |
| US8140658(B1) | 2012-03-01 | Gelvin et al. | Applicant |
| US8159519(B2) | 2012-04-01 | Kurtz et al. | Applicant |
| US8200827(B1) | 2012-06-01 | Hunyady et al. | Applicant |
| US8209400(B2) | 2012-06-01 | Baum et al. | Applicant |
| USD663298(S) | 2012-07-01 | Song et al. | Applicant |
| USD664540(S) | 2012-07-01 | Kim et al. | Applicant |
| US8214496(B2) | 2012-07-01 | Gutt et al. | Applicant |
| USD664954(S) | 2012-08-01 | Kim et al. | Applicant |
| USD666198(S) | 2012-08-01 | Van et al. | Applicant |
| US8239477(B2) | 2012-08-01 | Sharma et al. | Applicant |
| USD667395(S) | 2012-09-01 | Lee | Applicant |
| USD667396(S) | 2012-09-01 | Koh | Applicant |
| USD667397(S) | 2012-09-01 | Koh | Applicant |
| USD667398(S) | 2012-09-01 | Koh | Applicant |
| USD667399(S) | 2012-09-01 | Koh | Applicant |
| US8269623(B2) | 2012-09-01 | Addy et al. | Applicant |
| USD668650(S) | 2012-10-01 | Han | Applicant |
| USD668651(S) | 2012-10-01 | Kim et al. | Applicant |
| USD668652(S) | 2012-10-01 | Kim et al. | Applicant |
| USD669469(S) | 2012-10-01 | Kang | Applicant |
| USD670692(S) | 2012-11-01 | Akana et al. | Applicant |
| USD671514(S) | 2012-11-01 | Kim et al. | Applicant |
| US8311526(B2) | 2012-11-01 | Forstall et al. | Applicant |
| USD671938(S) | 2012-12-01 | Hsu et al. | Applicant |
| USD672344(S) | 2012-12-01 | Li | Applicant |
| USD672345(S) | 2012-12-01 | Li | Applicant |
| USD672739(S) | 2012-12-01 | Sin | Applicant |
| USD672768(S) | 2012-12-01 | Huang et al. | Applicant |
| US8335842(B2) | 2012-12-01 | Raji et al. | Applicant |
| US8335854(B2) | 2012-12-01 | Eldering | Applicant |
| USD673561(S) | 2013-01-01 | Hyun et al. | Applicant |
| USD673948(S) | 2013-01-01 | Andre et al. | Applicant |
| USD673950(S) | 2013-01-01 | Li et al. | Applicant |
| USD674369(S) | 2013-01-01 | Jaewoong | Applicant |
| USD675203(S) | 2013-01-01 | Yang | Applicant |
| USD675588(S) | 2013-02-01 | Park | Applicant |
| USD675612(S) | 2013-02-01 | Andre et al. | Applicant |
| USD676443(S) | 2013-02-01 | Canizares et al. | Applicant |
| USD676819(S) | 2013-02-01 | Choi | Applicant |
| USD677255(S) | 2013-03-01 | McManigal et al. | Applicant |
| USD677640(S) | 2013-03-01 | Kim et al. | Applicant |
| USD677659(S) | 2013-03-01 | Akana et al. | Applicant |
| USD677660(S) | 2013-03-01 | Groene et al. | Applicant |
| USD678271(S) | 2013-03-01 | Chiu | Applicant |
| USD678272(S) | 2013-03-01 | Groene et al. | Applicant |
| USD678877(S) | 2013-03-01 | Groene et al. | Applicant |
| USD679706(S) | 2013-04-01 | Tang et al. | Applicant |
| USD680151(S) | 2013-04-01 | Katori | Applicant |
| USD680524(S) | 2013-04-01 | Feng et al. | Applicant |
| USD681032(S) | 2013-04-01 | Akana et al. | Applicant |
| USD681583(S) | 2013-05-01 | Park | Applicant |
| USD681591(S) | 2013-05-01 | Sung | Applicant |
| USD681632(S) | 2013-05-01 | Akana et al. | Applicant |
| USD682239(S) | 2013-05-01 | Yeh et al. | Applicant |
| US8451986(B2) | 2013-05-01 | Cohn et al. | Applicant |
| USD684553(S) | 2013-06-01 | Kim et al. | Applicant |
| USD684968(S) | 2013-06-01 | Smith et al. | Applicant |
| US8473619(B2) | 2013-06-01 | Baum et al. | Applicant |
| USD685778(S) | 2013-07-01 | Fahrendorff et al. | Applicant |
| USD685783(S) | 2013-07-01 | Bryan et al. | Applicant |
| US8478844(B2) | 2013-07-01 | Baum et al. | Applicant |
| US8478871(B2) | 2013-07-01 | Gutt et al. | Applicant |
| US8483853(B1) | 2013-07-01 | Lambourne | Applicant |
| US8499038(B1) | 2013-07-01 | Vucurevich | Applicant |
| US8520068(B2) | 2013-08-01 | Naidoo et al. | Applicant |
| US8525664(B2) | 2013-09-01 | Hadizad et al. | Applicant |
| US8543665(B2) | 2013-09-01 | Ansari et al. | Applicant |
| US8584199(B1) | 2013-11-01 | Chen et al. | Applicant |
| US8612591(B2) | 2013-12-01 | Dawes et al. | Applicant |
| US8675071(B1) | 2014-03-01 | Slavin et al. | Applicant |
| US8730834(B2) | 2014-05-01 | Marusca et al. | Applicant |
| US8836467(B1) | 2014-09-01 | Cohn et al. | Applicant |
| US8902740(B2) | 2014-12-01 | Hicks, III | Applicant |
| US8914526(B1) | 2014-12-01 | Lindquist et al. | Applicant |
| US8935236(B2) | 2015-01-01 | Morita et al. | Applicant |
| US2001/0016501(A1) | 2001-08-01 | King | Applicant |
| US2001/0030597(A1) | 2001-10-01 | Inoue et al. | Applicant |
| US2001/0034754(A1) | 2001-10-01 | Elwahab et al. | Applicant |
| US2002/0004828(A1) | 2002-01-01 | Davis et al. | Applicant |
| US2002/0026476(A1) | 2002-02-01 | Miyazaki et al. | Applicant |
| US2002/0026531(A1) | 2002-02-01 | Keane et al. | Applicant |
| US2002/0027504(A1) | 2002-03-01 | Davis et al. | Applicant |
| US2002/0029276(A1) | 2002-03-01 | Bendinelli et al. | Applicant |
| US2002/0038380(A1) | 2002-03-01 | Brawn et al. | Applicant |
| US2002/0052913(A1) | 2002-05-01 | Yamada et al. | Applicant |
| US2002/0059637(A1) | 2002-05-01 | Rakib | Applicant |
| US2002/0083342(A1) | 2002-06-01 | Webb et al. | Applicant |
| US2002/0095490(A1) | 2002-07-01 | Barker et al. | Applicant |
| US2002/0099809(A1) | 2002-07-01 | Lee | Applicant |
| US2002/0099829(A1) | 2002-07-01 | Richards et al. | Applicant |
| US2002/0103898(A1) | 2002-08-01 | Moyer et al. | Applicant |
| US2002/0103927(A1) | 2002-08-01 | Parent | Applicant |
| US2002/0107910(A1) | 2002-08-01 | Zhao | Applicant |
| US2002/0109580(A1) | 2002-08-01 | Shreve et al. | Applicant |
| US2002/0111698(A1) | 2002-08-01 | Graziano et al. | Applicant |
| US2002/0112051(A1) | 2002-08-01 | Ullman | Applicant |
| US2002/0112182(A1) | 2002-08-01 | Chang et al. | Applicant |
| US2002/0114439(A1) | 2002-08-01 | Dunlap | Applicant |
| US2002/0116117(A1) | 2002-08-01 | Martens et al. | Applicant |
| US2002/0118107(A1) | 2002-08-01 | Yamamoto et al. | Applicant |
| US2002/0120790(A1) | 2002-08-01 | Schwalb | Applicant |
| US2002/0128728(A1) | 2002-09-01 | Murakami et al. | Applicant |
| US2002/0133539(A1) | 2002-09-01 | Monday | Applicant |
| US2002/0133578(A1) | 2002-09-01 | Wu | Applicant |
| US2002/0143923(A1) | 2002-10-01 | Alexander | Applicant |
| US2002/0147982(A1) | 2002-10-01 | Naidoo et al. | Applicant |
| US2002/0156564(A1) | 2002-10-01 | Preston et al. | Applicant |
| US2002/0163534(A1) | 2002-11-01 | Choi et al. | Applicant |
| US2002/0163997(A1) | 2002-11-01 | Bergman et al. | Applicant |
| US2002/0165006(A1) | 2002-11-01 | Haller et al. | Applicant |
| US2002/0174367(A1) | 2002-11-01 | Kimmel et al. | Applicant |
| US2002/0177428(A1) | 2002-11-01 | Menard et al. | Applicant |
| US2002/0180579(A1) | 2002-12-01 | Nagaoka et al. | Applicant |
| US2002/0184301(A1) | 2002-12-01 | Parent | Applicant |
| US2003/0005030(A1) | 2003-01-01 | Sutton et al. | Applicant |
| US2003/0009552(A1) | 2003-01-01 | Benfield et al. | Applicant |
| US2003/0009553(A1) | 2003-01-01 | Benfield et al. | Applicant |
| US2003/0023839(A1) | 2003-01-01 | Burkhardt et al. | Applicant |
| US2003/0030548(A1) | 2003-02-01 | Kovacs et al. | Examiner |
| US2003/0038849(A1) | 2003-02-01 | Craven et al. | Applicant |
| US2003/0041137(A1) | 2003-02-01 | Horie et al. | Applicant |
| US2003/0041167(A1) | 2003-02-01 | French et al. | Applicant |
| US2003/0051009(A1) | 2003-03-01 | Shah et al. | Applicant |
| US2003/0052923(A1) | 2003-03-01 | Porter | Applicant |
| US2003/0061344(A1) | 2003-03-01 | Monroe | Applicant |
| US2003/0062997(A1) | 2003-04-01 | Naidoo et al. | Applicant |
| US2003/0065757(A1) | 2003-04-01 | Mentze et al. | Applicant |
| US2003/0071724(A1) | 2003-04-01 | D'Amico | Applicant |
| US2003/0090473(A1) | 2003-05-01 | Joshi | Applicant |
| US2003/0103088(A1) | 2003-06-01 | Dresti et al. | Applicant |
| US2003/0115345(A1) | 2003-06-01 | Chien et al. | Applicant |
| US2003/0128115(A1) | 2003-07-01 | Giacopelli et al. | Applicant |
| US2003/0132018(A1) | 2003-07-01 | Okita et al. | Applicant |
| US2003/0137426(A1) | 2003-07-01 | Anthony et al. | Applicant |
| US2003/0147534(A1) | 2003-08-01 | Ablay et al. | Applicant |
| US2003/0158635(A1) | 2003-08-01 | Pillar et al. | Applicant |
| US2003/0159135(A1) | 2003-08-01 | Hiller et al. | Applicant |
| US2003/0174648(A1) | 2003-09-01 | Wang et al. | Applicant |
| US2003/0177236(A1) | 2003-09-01 | Goto et al. | Applicant |
| US2003/0182396(A1) | 2003-09-01 | Reich et al. | Applicant |
| US2003/0187920(A1) | 2003-10-01 | Redkar | Applicant |
| US2003/0189509(A1) | 2003-10-01 | Hayes et al. | Applicant |
| US2003/0197847(A1) | 2003-10-01 | Shinoda | Applicant |
| US2003/0200325(A1) | 2003-10-01 | Krishnaswamy et al. | Applicant |
| US2003/0201889(A1) | 2003-10-01 | Zulkowski | Applicant |
| US2003/0210126(A1) | 2003-11-01 | Kanazawa | Applicant |
| US2003/0217136(A1) | 2003-11-01 | Cho et al. | Applicant |
| US2003/0230934(A1) | 2003-12-01 | Cordelli et al. | Applicant |
| US2003/0236841(A1) | 2003-12-01 | Epshteyn | Applicant |
| US2004/0003241(A1) | 2004-01-01 | Sengodan et al. | Applicant |
| US2004/0015572(A1) | 2004-01-01 | Kang | Applicant |
| US2004/0024851(A1) | 2004-02-01 | Naidoo et al. | Applicant |
| US2004/0037295(A1) | 2004-02-01 | Tanaka et al. | Applicant |
| US2004/0054789(A1) | 2004-03-01 | Breh et al. | Applicant |
| US2004/0086088(A1) | 2004-05-01 | Naidoo et al. | Applicant |
| US2004/0086090(A1) | 2004-05-01 | Naidoo et al. | Applicant |
| US2004/0086093(A1) | 2004-05-01 | Schranz | Applicant |
| US2004/0103308(A1) | 2004-05-01 | Paller | Applicant |
| US2004/0117330(A1) | 2004-06-01 | Ehlers et al. | Applicant |
| US2004/0117462(A1) | 2004-06-01 | Bodin et al. | Applicant |
| US2004/0117465(A1) | 2004-06-01 | Bodin et al. | Applicant |
| US2004/0123149(A1) | 2004-06-01 | Tyroler | Applicant |
| US2004/0139227(A1) | 2004-07-01 | Takeda | Applicant |
| US2004/0143749(A1) | 2004-07-01 | Tajalli et al. | Applicant |
| US2004/0155757(A1) | 2004-08-01 | Litwin et al. | Applicant |
| US2004/0162902(A1) | 2004-08-01 | Davis | Applicant |
| US2004/0163073(A1) | 2004-08-01 | Krzyzanowski et al. | Applicant |
| US2004/0163118(A1) | 2004-08-01 | Mottur | Applicant |
| US2004/0169288(A1) | 2004-09-01 | Hsieh et al. | Applicant |
| US2004/0177163(A1) | 2004-09-01 | Casey et al. | Applicant |
| US2004/0189460(A1) | 2004-09-01 | Heaton et al. | Applicant |
| US2004/0189871(A1) | 2004-09-01 | Kurosawa et al. | Applicant |
| US2004/0196844(A1) | 2004-10-01 | Hagino | Applicant |
| US2004/0199645(A1) | 2004-10-01 | Rouhi | Applicant |
| US2004/0202351(A1) | 2004-10-01 | Park et al. | Applicant |
| US2004/0212503(A1) | 2004-10-01 | Stilp | Applicant |
| US2004/0215694(A1) | 2004-10-01 | Podolsky | Applicant |
| US2004/0215700(A1) | 2004-10-01 | Shenfield et al. | Applicant |
| US2004/0223605(A1) | 2004-11-01 | Donnelly | Examiner |
| US2004/0243835(A1) | 2004-12-01 | Terzis et al. | Applicant |
| US2004/0243996(A1) | 2004-12-01 | Sheehy et al. | Applicant |
| US2004/0246339(A1) | 2004-12-01 | Ooshima et al. | Applicant |
| US2004/0249922(A1) | 2004-12-01 | Hackman et al. | Applicant |
| US2004/0257433(A1) | 2004-12-01 | Lia et al. | Applicant |
| US2004/0260407(A1) | 2004-12-01 | Wimsatt | Applicant |
| US2004/0260427(A1) | 2004-12-01 | Wimsatt | Applicant |
| US2004/0267937(A1) | 2004-12-01 | Klemets | Applicant |
| US2005/0010866(A1) | 2005-01-01 | Humpleman et al. | Applicant |
| US2005/0015805(A1) | 2005-01-01 | Iwamura | Applicant |
| US2005/0023858(A1) | 2005-02-01 | Bingle et al. | Examiner |
| US2005/0024203(A1) | 2005-02-01 | Wolfe | Applicant |
| US2005/0038325(A1) | 2005-02-01 | Moll | Applicant |
| US2005/0038326(A1) | 2005-02-01 | Mathur | Applicant |
| US2005/0044061(A1) | 2005-02-01 | Klemow | Applicant |
| US2005/0052831(A1) | 2005-03-01 | Chen | Applicant |
| US2005/0060411(A1) | 2005-03-01 | Coulombe et al. | Applicant |
| US2005/0066045(A1) | 2005-03-01 | Johnson et al. | Applicant |
| US2005/0069098(A1) | 2005-03-01 | Kalervo et al. | Applicant |
| US2005/0079855(A1) | 2005-04-01 | Jethi et al. | Applicant |
| US2005/0086126(A1) | 2005-04-01 | Patterson | Applicant |
| US2005/0086211(A1) | 2005-04-01 | Mayer | Applicant |
| US2005/0091696(A1) | 2005-04-01 | Wolfe et al. | Applicant |
| US2005/0096753(A1) | 2005-05-01 | Arling et al. | Applicant |
| US2005/0102152(A1) | 2005-05-01 | Hodges | Applicant |
| US2005/0108091(A1) | 2005-05-01 | Sotak et al. | Applicant |
| US2005/0108369(A1) | 2005-05-01 | Sather et al. | Applicant |
| US2005/0120082(A1) | 2005-06-01 | Hesselink et al. | Applicant |
| US2005/0125083(A1) | 2005-06-01 | Kiko | Applicant |
| US2005/0128068(A1) | 2005-06-01 | Winick et al. | Applicant |
| US2005/0128083(A1) | 2005-06-01 | Puzio et al. | Applicant |
| US2005/0144312(A1) | 2005-06-01 | Kadyk et al. | Applicant |
| US2005/0149639(A1) | 2005-07-01 | Vrielink et al. | Applicant |
| US2005/0149746(A1) | 2005-07-01 | Lu et al. | Applicant |
| US2005/0156568(A1) | 2005-07-01 | Yueh | Applicant |
| US2005/0159823(A1) | 2005-07-01 | Hayes et al. | Applicant |
| US2005/0169288(A1) | 2005-08-01 | Kamiwada et al. | Applicant |
| US2005/0184865(A1) | 2005-08-01 | Han et al. | Applicant |
| US2005/0197847(A1) | 2005-09-01 | Smith | Applicant |
| US2005/0200474(A1) | 2005-09-01 | Behnke | Applicant |
| US2005/0204076(A1) | 2005-09-01 | Cumpson et al. | Applicant |
| US2005/0210532(A1) | 2005-09-01 | Winick | Applicant |
| US2005/0216302(A1) | 2005-09-01 | Raji et al. | Applicant |
| US2005/0216580(A1) | 2005-09-01 | Raji et al. | Applicant |
| US2005/0222820(A1) | 2005-10-01 | Chung et al. | Applicant |
| US2005/0231349(A1) | 2005-10-01 | Bhat | Applicant |
| US2005/0237182(A1) | 2005-10-01 | Wang | Applicant |
| US2005/0249199(A1) | 2005-11-01 | Albert et al. | Applicant |
| US2005/0256608(A1) | 2005-11-01 | King et al. | Applicant |
| US2005/0267605(A1) | 2005-12-01 | Lee et al. | Applicant |
| US2005/0273831(A1) | 2005-12-01 | Slomovich et al. | Applicant |
| US2005/0276389(A1) | 2005-12-01 | Hinkson et al. | Applicant |
| US2005/0280964(A1) | 2005-12-01 | Richmond et al. | Applicant |
| US2006/0009863(A1) | 2006-01-01 | Lingemann | Applicant |
| US2006/0010078(A1) | 2006-01-01 | Rezvani et al. | Applicant |
| US2006/0018328(A1) | 2006-01-01 | Mody et al. | Applicant |
| US2006/0045074(A1) | 2006-03-01 | Lee | Applicant |
| US2006/0051122(A1) | 2006-03-01 | Kawazu et al. | Applicant |
| US2006/0063534(A1) | 2006-03-01 | Kokkonen et al. | Applicant |
| US2006/0064305(A1) | 2006-03-01 | Alonso | Applicant |
| US2006/0064478(A1) | 2006-03-01 | Sirkin | Applicant |
| US2006/0067344(A1) | 2006-03-01 | Sakurai | Applicant |
| US2006/0067484(A1) | 2006-03-01 | Elliot et al. | Applicant |
| US2006/0075235(A1) | 2006-04-01 | Renkis | Applicant |
| US2006/0078344(A1) | 2006-04-01 | Kawazu et al. | Applicant |
| US2006/0088092(A1) | 2006-04-01 | Chen et al. | Applicant |
| US2006/0105713(A1) | 2006-05-01 | Zheng et al. | Applicant |
| US2006/0109113(A1) | 2006-05-01 | Reyes et al. | Applicant |
| US2006/0111095(A1) | 2006-05-01 | Weigand | Applicant |
| US2006/0129837(A1) | 2006-06-01 | Im et al. | Applicant |
| US2006/0132302(A1) | 2006-06-01 | Stilp | Applicant |
| US2006/0142880(A1) | 2006-06-01 | Deen et al. | Applicant |
| US2006/0142968(A1) | 2006-06-01 | Han et al. | Applicant |
| US2006/0143268(A1) | 2006-06-01 | Chatani | Applicant |
| US2006/0145842(A1) | 2006-07-01 | Stilp | Applicant |
| US2006/0161270(A1) | 2006-07-01 | Luskin et al. | Applicant |
| US2006/0161662(A1) | 2006-07-01 | Ng et al. | Applicant |
| US2006/0161960(A1) | 2006-07-01 | Benoit | Applicant |
| US2006/0167784(A1) | 2006-07-01 | Hoffberg | Applicant |
| US2006/0168178(A1) | 2006-07-01 | Hwang et al. | Applicant |
| US2006/0181406(A1) | 2006-08-01 | Petite et al. | Applicant |
| US2006/0182100(A1) | 2006-08-01 | Li et al. | Applicant |
| US2006/0187900(A1) | 2006-08-01 | Akbar | Applicant |
| US2006/0190458(A1) | 2006-08-01 | Mishina et al. | Applicant |
| US2006/0197660(A1) | 2006-09-01 | Luebke et al. | Applicant |
| US2006/0200845(A1) | 2006-09-01 | Foster et al. | Applicant |
| US2006/0206220(A1) | 2006-09-01 | Amundson | Applicant |
| US2006/0209857(A1) | 2006-09-01 | Hicks, III | Applicant |
| US2006/0218593(A1) | 2006-09-01 | Afshary et al. | Applicant |
| US2006/0220830(A1) | 2006-10-01 | Bennett, III | Applicant |
| US2006/0222153(A1) | 2006-10-01 | Tarkoff et al. | Applicant |
| US2006/0229746(A1) | 2006-10-01 | Ollis et al. | Applicant |
| US2006/0230270(A1) | 2006-10-01 | Goffin | Applicant |
| US2006/0242395(A1) | 2006-10-01 | Fausak | Applicant |
| US2006/0245369(A1) | 2006-11-01 | Schimmelpfeng et al. | Applicant |
| US2006/0246919(A1) | 2006-11-01 | Park et al. | Applicant |
| US2006/0258342(A1) | 2006-11-01 | Fok et al. | Applicant |
| US2006/0265489(A1) | 2006-11-01 | Moore | Applicant |
| US2006/0271695(A1) | 2006-11-01 | Lavian | Applicant |
| US2006/0282886(A1) | 2006-12-01 | Gaug | Applicant |
| US2007/0002833(A1) | 2007-01-01 | Bajic | Applicant |
| US2007/0005736(A1) | 2007-01-01 | Hansen et al. | Applicant |
| US2007/0005957(A1) | 2007-01-01 | Sahita et al. | Applicant |
| US2007/0006177(A1) | 2007-01-01 | Aiber et al. | Applicant |
| US2007/0052675(A1) | 2007-03-01 | Chang | Applicant |
| US2007/0055770(A1) | 2007-03-01 | Karmakar et al. | Examiner |
| US2007/0061266(A1) | 2007-03-01 | Moore et al. | Applicant |
| US2007/0063866(A1) | 2007-03-01 | Webb | Applicant |
| US2007/0079151(A1) | 2007-04-01 | Connor et al. | Applicant |
| US2007/0079385(A1) | 2007-04-01 | Williams et al. | Applicant |
| US2007/0096981(A1) | 2007-05-01 | Abraham | Applicant |
| US2007/0101345(A1) | 2007-05-01 | Takagi | Applicant |
| US2007/0106124(A1) | 2007-05-01 | Kuriyama et al. | Applicant |
| US2007/0130286(A1) | 2007-06-01 | Hopmann et al. | Applicant |
| US2007/0142022(A1) | 2007-06-01 | Madonna et al. | Applicant |
| US2007/0143440(A1) | 2007-06-01 | Reckamp et al. | Applicant |
| US2007/0146484(A1) | 2007-06-01 | Horton et al. | Applicant |
| US2007/0147419(A1) | 2007-06-01 | Tsujimoto et al. | Applicant |
| US2007/0155325(A1) | 2007-07-01 | Bambic et al. | Applicant |
| US2007/0162228(A1) | 2007-07-01 | Mitchell | Applicant |
| US2007/0162680(A1) | 2007-07-01 | Mitchell et al. | Applicant |
| US2007/0192486(A1) | 2007-08-01 | Wilson et al. | Applicant |
| US2007/0198698(A1) | 2007-08-01 | Boyd et al. | Applicant |
| US2007/0216783(A1) | 2007-09-01 | Ortiz et al. | Applicant |
| US2007/0223465(A1) | 2007-09-01 | Wang et al. | Applicant |
| US2007/0226182(A1) | 2007-09-01 | Sobotka et al. | Applicant |
| US2007/0230415(A1) | 2007-10-01 | Malik | Applicant |
| US2007/0245223(A1) | 2007-10-01 | Siedzik et al. | Applicant |
| US2007/0256105(A1) | 2007-11-01 | Tabe | Applicant |
| US2007/0265866(A1) | 2007-11-01 | Fehling et al. | Applicant |
| US2007/0271398(A1) | 2007-11-01 | Manchester et al. | Applicant |
| US2007/0286210(A1) | 2007-12-01 | Gutt et al. | Applicant |
| US2007/0286369(A1) | 2007-12-01 | Gutt et al. | Applicant |
| US2007/0287405(A1) | 2007-12-01 | Radtke | Applicant |
| US2007/0288849(A1) | 2007-12-01 | Moorer et al. | Applicant |
| US2007/0298772(A1) | 2007-12-01 | Owens et al. | Examiner |
| US2008/0001734(A1) | 2008-01-01 | Stilp et al. | Applicant |
| US2008/0013957(A1) | 2008-01-01 | Akers et al. | Applicant |
| US2008/0027587(A1) | 2008-01-01 | Nickerson et al. | Applicant |
| US2008/0042826(A1) | 2008-02-01 | Hevia et al. | Applicant |
| US2008/0048975(A1) | 2008-02-01 | Leibow | Applicant |
| US2008/0065681(A1) | 2008-03-01 | Fontijn et al. | Applicant |
| US2008/0072244(A1) | 2008-03-01 | Eker et al. | Applicant |
| US2008/0084296(A1) | 2008-04-01 | Kutzik et al. | Applicant |
| US2008/0091793(A1) | 2008-04-01 | Diroo et al. | Applicant |
| US2008/0104516(A1) | 2008-05-01 | Lee | Applicant |
| US2008/0109650(A1) | 2008-05-01 | Shim et al. | Applicant |
| US2008/0112405(A1) | 2008-05-01 | Cholas et al. | Applicant |
| US2008/0117029(A1) | 2008-05-01 | Dohrmann et al. | Applicant |
| US2008/0126535(A1) | 2008-05-01 | Zhu et al. | Applicant |
| US2008/0133725(A1) | 2008-06-01 | Shaouy | Examiner |
| US2008/0141303(A1) | 2008-06-01 | Walker et al. | Applicant |
| US2008/0141341(A1) | 2008-06-01 | Vinogradov et al. | Applicant |
| US2008/0147834(A1) | 2008-06-01 | Quinn et al. | Applicant |
| US2008/0163355(A1) | 2008-07-01 | Chu | Applicant |
| US2008/0168404(A1) | 2008-07-01 | Ording | Applicant |
| US2008/0170511(A1) | 2008-07-01 | Shorty et al. | Applicant |
| US2008/0180240(A1) | 2008-07-01 | Raji et al. | Applicant |
| US2008/0183842(A1) | 2008-07-01 | Raji et al. | Applicant |
| US2008/0189609(A1) | 2008-08-01 | Larson et al. | Applicant |
| US2008/0219239(A1) | 2008-09-01 | Bell et al. | Applicant |
| US2008/0235326(A1) | 2008-09-01 | Parsi et al. | Applicant |
| US2008/0235600(A1) | 2008-09-01 | Harper et al. | Applicant |
| US2008/0240372(A1) | 2008-10-01 | Frenette | Applicant |
| US2008/0253391(A1) | 2008-10-01 | Krits et al. | Applicant |
| US2008/0261540(A1) | 2008-10-01 | Rohani et al. | Applicant |
| US2008/0284587(A1) | 2008-11-01 | Saigh et al. | Applicant |
| US2008/0316024(A1) | 2008-12-01 | Chantelou et al. | Applicant |
| US2009/0019141(A1) | 2009-01-01 | Bush et al. | Applicant |
| US2009/0036142(A1) | 2009-02-01 | Yan | Applicant |
| US2009/0041467(A1) | 2009-02-01 | Carleton et al. | Applicant |
| US2009/0042649(A1) | 2009-02-01 | Hsieh et al. | Applicant |
| US2009/0049488(A1) | 2009-02-01 | Stransky | Applicant |
| US2009/0063582(A1) | 2009-03-01 | Anna et al. | Applicant |
| US2009/0066788(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0066789(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0067395(A1) | 2009-03-01 | Curtis et al. | Applicant |
| US2009/0070436(A1) | 2009-03-01 | Dawes et al. | Applicant |
| US2009/0070473(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0070477(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0070681(A1) | 2009-03-01 | Dawes et al. | Applicant |
| US2009/0070682(A1) | 2009-03-01 | Dawes et al. | Applicant |
| US2009/0070692(A1) | 2009-03-01 | Dawes et al. | Applicant |
| US2009/0074184(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0077167(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0077622(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0077623(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0077624(A1) | 2009-03-01 | Baum et al. | Applicant |
| US2009/0100329(A1) | 2009-04-01 | Espinoza | Applicant |
| US2009/0100492(A1) | 2009-04-01 | Hicks, III et al. | Applicant |
| US2009/0113344(A1) | 2009-04-01 | Nesse et al. | Applicant |
| US2009/0119397(A1) | 2009-05-01 | Neerdaels | Applicant |
| US2009/0125708(A1) | 2009-05-01 | Woodring et al. | Applicant |
| US2009/0128365(A1) | 2009-05-01 | Laskin | Applicant |
| US2009/0134998(A1) | 2009-05-01 | Baum et al. | Applicant |
| US2009/0138600(A1) | 2009-05-01 | Baum et al. | Applicant |
| US2009/0138958(A1) | 2009-05-01 | Baum et al. | Applicant |
| US2009/0146846(A1) | 2009-06-01 | Grossman | Applicant |
| US2009/0158189(A1) | 2009-06-01 | Itani | Applicant |
| US2009/0158292(A1) | 2009-06-01 | Rattner et al. | Applicant |
| US2009/0165114(A1) | 2009-06-01 | Baum et al. | Applicant |
| US2009/0177906(A1) | 2009-07-01 | Paniagua, Jr. et al. | Applicant |
| US2009/0204693(A1) | 2009-08-01 | Andreev et al. | Applicant |
| US2009/0221368(A1) | 2009-09-01 | Yen et al. | Applicant |
| US2009/0240787(A1) | 2009-09-01 | Denny | Applicant |
| US2009/0240814(A1) | 2009-09-01 | Brubacher et al. | Applicant |
| US2009/0240946(A1) | 2009-09-01 | Yeap et al. | Applicant |
| US2009/0256708(A1) | 2009-10-01 | Hsiao et al. | Applicant |
| US2009/0303100(A1) | 2009-12-01 | Zemany | Examiner |
| US2009/0313693(A1) | 2009-12-01 | Rogers | Applicant |
| US2009/0322510(A1) | 2009-12-01 | Berger et al. | Applicant |
| US2010/0008274(A1) | 2010-01-01 | Kneckt et al. | Applicant |
| US2010/0023865(A1) | 2010-01-01 | Fulker et al. | Applicant |
| US2010/0026487(A1) | 2010-02-01 | Hershkovitz | Applicant |
| US2010/0030578(A1) | 2010-02-01 | Siddique et al. | Applicant |
| US2010/0030810(A1) | 2010-02-01 | Marr | Applicant |
| US2010/0052612(A1) | 2010-03-01 | Raji et al. | Applicant |
| US2010/0066530(A1) | 2010-03-01 | Cohn et al. | Applicant |
| US2010/0074112(A1) | 2010-03-01 | Derr et al. | Applicant |
| US2010/0077111(A1) | 2010-03-01 | Holmes et al. | Applicant |
| US2010/0082744(A1) | 2010-04-01 | Raji et al. | Applicant |
| US2010/0095111(A1) | 2010-04-01 | Gutt et al. | Applicant |
| US2010/0095369(A1) | 2010-04-01 | Gutt et al. | Applicant |
| US2010/0121521(A1) | 2010-05-01 | Kiribayashi | Examiner |
| US2010/0153853(A1) | 2010-06-01 | Dawes et al. | Applicant |
| US2010/0159967(A1) | 2010-06-01 | Pounds et al. | Examiner |
| US2010/0185857(A1) | 2010-07-01 | Neitzel et al. | Applicant |
| US2010/0197219(A1) | 2010-08-01 | Issa et al. | Applicant |
| US2010/0210240(A1) | 2010-08-01 | Mahaffey et al. | Examiner |
| US2010/0212012(A1) | 2010-08-01 | Touboul et al. | Applicant |
| US2010/0218104(A1) | 2010-08-01 | Lewis | Examiner |
| US2010/0245107(A1) | 2010-09-01 | Fulker et al. | Applicant |
| US2010/0267390(A1) | 2010-10-01 | Lin et al. | Applicant |
| US2010/0280635(A1) | 2010-11-01 | Cohn et al. | Applicant |
| US2010/0280637(A1) | 2010-11-01 | Cohn et al. | Applicant |
| US2010/0298024(A1) | 2010-11-01 | Choi | Applicant |
| US2010/0321151(A1) | 2010-12-01 | Matsuura et al. | Applicant |
| US2010/0332164(A1) | 2010-12-01 | Aisa et al. | Applicant |
| US2011/0000521(A1) | 2011-01-01 | Tachibana | Applicant |
| US2011/0029875(A1) | 2011-02-01 | Milch | Examiner |
| US2011/0040415(A1) | 2011-02-01 | Nickerson et al. | Applicant |
| US2011/0040877(A1) | 2011-02-01 | Foisy | Applicant |
| US2011/0096678(A1) | 2011-04-01 | Ketonen | Applicant |
| US2011/0102588(A1) | 2011-05-01 | Trundle et al. | Applicant |
| US2011/0197327(A1) | 2011-08-01 | McElroy et al. | Applicant |
| US2011/0234392(A1) | 2011-09-01 | Cohn et al. | Applicant |
| US2011/0283006(A1) | 2011-11-01 | Ramamurthy | Applicant |
| US2012/0023151(A1) | 2012-01-01 | Bennett, III et al. | Applicant |
| US2012/0066608(A1) | 2012-03-01 | Sundermeyer et al. | Applicant |
| US2012/0081842(A1) | 2012-04-01 | Ewing et al. | Applicant |
| US2012/0154138(A1) | 2012-06-01 | Cohn et al. | Applicant |
| US2012/0182245(A1) | 2012-07-01 | Hutton | Applicant |
| US2012/0242788(A1) | 2012-09-01 | Chuang et al. | Applicant |
| US2012/0260184(A1) | 2012-10-01 | Dawes et al. | Applicant |
| US2012/0278877(A1) | 2012-11-01 | Baum et al. | Applicant |
| US2012/0327242(A1) | 2012-12-01 | Barley et al. | Applicant |
| US2014/0143695(A1) | 2014-05-01 | Sundermeyer et al. | Applicant |
| US2014/0143854(A1) | 2014-05-01 | Lopez et al. | Applicant |
| US2014/0153695(A1) | 2014-06-01 | Yanagisawa et al. | Applicant |
| US2015/0088982(A1) | 2015-03-01 | Johnson et al. | Applicant |
| AU2005223267(B2) | 2010-12-01 | Applicant | |
| AU2010297957(A1) | 2012-05-01 | Applicant | |
| AU2011250886(A1) | 2013-01-01 | Applicant | |
| AU2011305163(A1) | 2013-05-01 | Applicant | |
| CA2559842(C) | 2014-05-01 | Applicant | |
| EP295146(A2) | 1988-12-01 | Applicant | |
| EP308046(A2) | 1989-03-01 | Applicant | |
| EP591585(A1) | 1994-04-01 | Applicant | |
| EP978111(B1) | 2001-11-01 | Applicant | |
| EP2112784(A1) | 2009-10-01 | Applicant | |
| FR2584217 | 1987-01-01 | Applicant | |
| FR2661023(A1) | 1991-10-01 | Applicant | |
| FR2793334(A1) | 2000-11-01 | Applicant | |
| GB2222288(A) | 1990-02-01 | Applicant | |
| GB2273593(A) | 1994-06-01 | Applicant | |
| GB2319373(A) | 1998-05-01 | Applicant | |
| GB2324630(A) | 1998-10-01 | Applicant | |
| GB2335523(A) | 1999-09-01 | Applicant | |
| GB2349293(A) | 2000-10-01 | Applicant | |
| GB2370400(A) | 2002-06-01 | Applicant | |
| JP8227491(A) | 1996-09-01 | Applicant | |
| JP2002055895(A) | 2002-02-01 | Applicant | |
| JP2003085258(A) | 2003-03-01 | Applicant | |
| JP2003141659(A) | 2003-05-01 | Applicant | |
| JP2004192659(A) | 2004-07-01 | Applicant | |
| KR20060021605(A) | 2006-03-01 | Applicant | |
| WO-8907855(A1) | 1989-08-01 | Applicant | |
| WO-9403881(A1) | 1994-02-01 | Applicant | |
| WO-9636301(A1) | 1996-11-01 | Applicant | |
| WO-9849663(A1) | 1998-11-01 | Applicant | |
| WO99/34339 | 1999-07-01 | Applicant | |
| WO-0152478(A2) | 2001-07-01 | Applicant | |
| WO-0199078(A2) | 2001-12-01 | Applicant | |
| WO-0221300(A1) | 2002-03-01 | Applicant | |
| WO-02097584(A2) | 2002-12-01 | Applicant | |
| WO-03040839(A1) | 2003-05-01 | Applicant | |
| WO-2004004222(A1) | 2004-01-01 | Applicant | |
| WO2004/098127 | 2004-11-01 | Applicant | |
| WO-2004107710(A1) | 2004-12-01 | Applicant | |
| WO2005/091218 | 2005-09-01 | Applicant | |
| WO-2005091218(A3) | 2006-07-01 | Applicant | |
| WO-2007038872(A1) | 2007-04-01 | Applicant | |
| WO-2007124453(A2) | 2007-11-01 | Applicant | |
| WO2009/006670 | 2009-01-01 | Applicant | |
| WO-2009145747(A1) | 2009-12-01 | Applicant |
Non-Patent Literature (196)
- “Control Panel Standard—Features for False Alarm Reduction,” The Security Industry Association, © SIA 2009, pp. 1-48.Applicant
- Alarm.com—Interactive Security Systems, Elders [retrieved on Nov. 4, 2003], 1 page.Applicant
- Alarm.com—Interactive Security Systems, Frequently Asked Questions [retrieved on Nov. 4, 2003], 3 pages.Applicant
- Alarm.com—Interactive Security Systems, Overview [retrieved on Nov. 4, 2003], 2 pages.Applicant
- Alarm.com—Interactive Security Systems, Product Advantages [retrieved on Nov. 4, 2003], 3 pages.Applicant
- Australian Patent App. No. 2010297957.Applicant
- Australian Patent App. No. 2011250886.Applicant
- Australian Patent App. No. 2011305163.Applicant
- Canadian Patent App. No. 2559842.Applicant
- Chinese Patent App. No. 201080053845.7.Applicant
- Chinese Patent App. No. 201180034090.0.Applicant
- Co-pending U.S. Appl. No. 11/761,745, filed Jun. 12, 2007.Applicant
- Co-pending U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Co-pending U.S. Appl. No. 12/189,780, filed Aug. 11, 2008.Applicant
- Co-pending U.S. Appl. No. 12/189,785, filed Aug. 11, 2008.Applicant
- Co-pending U.S. Appl. No. 12/197,931, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/197,946, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/197,958, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/198,039, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/198,051, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/198,060, filed May 28, 2008.Applicant
- Co-pending U.S. Appl. No. 12/198,066, filed Aug. 25, 2008.Applicant
- Co-pending U.S. Appl. No. 12/269,735, filed Nov. 12, 2008.Applicant
- Co-pending U.S. Appl. No. 12/539,537, filed Aug. 11, 2009.Applicant
- Co-pending U.S. Appl. No. 12/568,718, filed Sep. 29, 2009.Applicant
- Co-pending U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Co-pending U.S. Appl. No. 12/691,992, filed Jan. 22, 2010.Applicant
- Co-pending U.S. Appl. No. 12/718,385, filed Mar. 5, 2010.Applicant
- Co-pending U.S. Appl. No. 12/732,879, filed Mar. 26, 2010.Applicant
- Co-pending U.S. Appl. No. 12/750,470, filed Mar. 30, 2010.Applicant
- Co-pending U.S. Appl. No. 12/770,253, filed Apr. 29, 2010.Applicant
- Co-pending U.S. Appl. No. 12/770,365, filed Apr. 29, 2010.Applicant
- Co-pending U.S. Appl. No. 12/771,071, filed Apr. 30, 2010.Applicant
- Co-pending U.S. Appl. No. 12/771,372, filed Apr. 30, 2010.Applicant
- Co-pending U.S. Appl. No. 12/771,471, filed Apr. 30, 2010.Applicant
- Co-pending U.S. Appl. No. 12/771,624, filed Apr. 30, 2010.Applicant
- Co-pending U.S. Appl. No. 12/892,303, filed Sep. 28, 2010.Applicant
- Co-pending U.S. Appl. No. 12/892,801, filed Sep. 28, 2010.Applicant
- Co-pending U.S. Appl. No. 12/952,080, filed Nov. 22, 2010.Applicant
- Co-pending U.S. Appl. No. 12/970,313, filed Dec. 16, 2010.Applicant
- Co-pending U.S. Appl. No. 12/971,282, filed Dec. 17, 2010.Applicant
- Co-pending U.S. Appl. No. 12/972,740, filed Dec. 20, 2010.Applicant
- Co-pending U.S. Appl. No. 13/099,293, filed May 2, 2011.Applicant
- Co-pending U.S. Appl. No. 13/104,932, filed May 10, 2011.Applicant
- Co-pending U.S. Appl. No. 13/104,936, filed May 10, 2011.Applicant
- Co-pending U.S. Appl. No. 13/153,807, filed Jun. 6, 2011.Applicant
- Co-pending U.S. Appl. No. 13/244,008, filed Sep. 23, 2011.Applicant
- Co-pending U.S. Appl. No. 13/311,365, filed Dec. 5, 2011.Applicant
- Co-pending U.S. Appl. No. 13/334,998, filed Dec. 22, 2011.Applicant
- Co-pending U.S. Appl. No. 13/335,279, filed Dec. 22, 2011.Applicant
- Co-pending U.S. Appl. No. 13/400,477, filed Dec. 22, 2011.Applicant
- Co-pending U.S. Appl. No. 13/406,264, filed Feb. 27, 2012.Applicant
- Co-pending U.S. Appl. No. 13/486,276, filed Jun. 1, 2012.Applicant
- Co-pending U.S. Appl. No. 13/531,757, filed Jun. 25, 2012.Applicant
- Co-pending U.S. Appl. No. 13/718,851, filed Dec. 18, 2012.Applicant
- Co-pending U.S. Appl. No. 13/725,607, filed Dec. 21, 2012.Applicant
- Co-pending U.S. Appl. No. 13/925,181, filed Jun. 24, 2013.Applicant
- Co-pending U.S. Appl. No. 13/929,568, filed Jun. 27, 2013.Applicant
- Co-pending U.S. Appl. No. 13/932,816, filed Jul. 1, 2013.Applicant
- Co-pending U.S. Appl. No. 13/932,837, filed Jul. 1, 2013.Applicant
- Co-pending U.S. Appl. No. 29/419,628, filed Apr. 30, 2012.Applicant
- Co-pending U.S. Appl. No. 29/420,377, filed May 8, 2012.Applicant
- European Patent App. No. 05725743.8.Applicant
- European Patent App. No. 08797646.0.Applicant
- European Patent App. No. 08828613.3.Applicant
- European Patent App. No. 09807196.2.Applicant
- European Patent App. No. 10819658.5.Applicant
- European Patent App. No. 11781184.4.Applicant
- European Patent App. No. 11827671.6.Applicant
- Examination Report under Section 18(3) re for UK Patent Application No. GB0620362.4, mailed on Aug. 13, 2007.Applicant
- Examination Report under Section 18(3) re for UK Patent Application No. GB0724248.0, mailed on Jun. 4, 2008.Applicant
- Examination Report under Section 18(3) re for UK Patent Application No. GB0724248.0, mailed on Jan. 30, 2008.Applicant
- Examination Report under Section 18(3) re for UK Patent Application No. GB0724760.4, mailed on Jan. 30, 2008.Applicant
- Examination Report under Section 18(3) re for UK Patent Application No. GB0800040.8, mailed on Jan. 30, 2008.Applicant
- Faultline, “AT&T Targets Video Home Security as Next Broadband Market,” The Register, Nov. 2, 2006, 2 pages.Applicant
- Final Office Action mailed Aug. 1, 2011 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Final Office Action mailed Jun. 1, 2009 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Final Office Action mailed Jun. 5, 2012 for U.S. Appl. No. 12/771,071, filed Apr. 30, 2010.Applicant
- Final Office Action mailed May 9, 2013 for U.S. Appl. No. 12/189,780, filed Aug. 11, 2008.Applicant
- Final Office Action mailed May 9, 2013 for U.S. Appl. No. 12/952,080, filed Nov. 22, 2010.Applicant
- Final Office Action mailed Jan. 10, 2011 for U.S. Appl. No. 12/189,785, filed Aug. 11, 2008.Applicant
- Final Office Action mailed Jun. 10, 2011 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Final Office Action mailed Jul. 12, 2010 for U.S. Appl. No. 12/019,554, filed Jan. 24, 2008.Applicant
- Final Office Action mailed Jan. 13, 2011 for U.S. Appl. No. 12/189,780, filed Aug. 11, 2008.Applicant
- Final Office Action mailed Sep. 14, 2011 for U.S. Appl. No. 12/197,931, filed Aug. 25, 2008.Applicant
- Final Office Action mailed Feb. 16, 2011 for U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Final Office Action mailed Oct. 17, 2012 for U.S. Appl. No. 12/637,671, filed Dec. 14, 2009.Applicant
- Final Office Action mailed Sep. 17, 2012 for U.S. Appl. No. 12/197,958, filed Aug. 25, 2008.Applicant
- Final Office Action mailed Mar. 21, 2013 for U.S. Appl. No. 12/691,992, filed Jan. 22, 2010.Applicant
- Final Office Action mailed Jul. 23, 2013 for U.S. Appl. No. 13/531,757, filed Jun. 25, 2012.Applicant
- Final Office Action mailed Jun. 29, 2012 for U.S. Appl. No. 12/539,537, filed Aug. 11, 2009.Applicant
- Final Office Action mailed Dec. 31, 2012 for U.S. Appl. No. 12/770,365, filed Apr. 29, 2010.Applicant
- Final Office Action mailed Oct. 31, 2012 for U.S. Appl. No. 12/771,624, filed Apr. 30, 2010.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US05/08766,” May 23, 2006, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US08/72831,” Nov. 4, 2008, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US08/74246,” Nov. 14, 2008, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US08/74260,” Nov. 13, 2008, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US09/53485,” Oct. 22, 2009, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US09/55559,” Nov. 12, 2009, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US10/50585,” Dec. 30, 2010, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US10/57674,” Mar. 2, 2011, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US11/34858,” Oct. 3, 2011, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US11/35994,” Sep. 28, 2011, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US11/53136,” Jan. 5, 2009, 2 pages.Applicant
- Form PCT/ISA/210, “PCT International Search Report for the Application No. PCT/US08/83254,” Jan. 14, 2009, 2 pages.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” 1 pg.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US05/08766,” May 23, 2006, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US08/72831,” Nov. 4, 2008, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US08/74246” Nov. 14, 2008, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US08/74260,” Nov. 13, 2008, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US09/53485,” Oct. 22, 2009, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US09/55559,” Nov. 12, 2009, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US10/50585,” Dec. 30, 2010, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US10/57674,” Mar. 2, 2011, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US11/35994,” Sep. 28, 2011, 1 page.Applicant
- Form PCT/ISA/220, “PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for the Application No. PCT/US08/83254,” Jan. 14, 2009, 1 page.Applicant
- Form PCT/ISA/237, “PCT Written Opinion ofthe International Searching Authority for the Application No. PCT/US05/08766,” May 23, 2006, 5 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority,” 6 pgs.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US08/72831,” Nov. 4, 2008, 6 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US08/74246,” Nov. 14, 2008, 6 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US08/74260,” Nov. 13, 2008, 6 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US09/53485,” Oct. 22, 2009, 8 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US09/55559,” Nov. 12, 2009, 6 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US10/50585,” Dec. 30, 2010, 7 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US10/57674,” Mar. 2, 2011, 6 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US11/34858,” Oct. 3, 2011, 8 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US11/35994,” Sep. 28, 2011, 11 pages.Applicant
- Form PCT/ISA/237, “PCT Written Opinion of the International Searching Authority for the Application No. PCT/US11/53136,” Jan. 5, 2012.Applicant
- Form PCT/ISA/237, “PCT Written Opinion ofthe International Searching Authority of the Application No. PCT/US08/83254,” Jan. 14, 2009, 7 pages.Applicant
- Gutierrez J.A., “On the Use of IEEE 802.15.4 to Enable Wireless Sensor Networks in Building Automation,” Personal, Indoor and Mobile Radio Communications (PIMRC), 15th IEEE International Symposium, 2004, vol. 3, pp. 1865-1869.Applicant
- Indian Patent App. No. 10698/DELNP/2012.Applicant
- Indian Patent App. No. 3687/DELNP/2012.Applicant
- International Patent Application No. PCT/US2013/048324.Applicant
- International Search Report for Application No. PCT/US13/48324, mailed on Jan. 14, 2014, 2 pages.Applicant
- International Search Report for Application No. PCT/US2014/050548, mailed on Mar. 18, 2015, 4 pages.Applicant
- Lagotek Wireless Home Automation System, May 2006 [retrieved on Aug. 22, 2012].Applicant
- Non-Final Office Action mailed Apr. 4, 2013 for U.S. Appl. No. 12/197,931, filed Aug. 25, 2008.Applicant
- Non-Final Office Action mailed Mar. 4, 2013 for U.S. Appl. No. 13/400,477, filed Feb. 20, 2012.Applicant
- Non-Final Office Action mailed Jan. 5, 2010 for U.S. Appl. No. 12/019,554, filed Jan. 24, 2008.Applicant
- Non-Final Office Action mailed May 5, 2010 for U.S. Appl. No. 12/189,780, filed Aug. 11, 2008.Applicant
- Non-Final Office Action mailed May 5, 2010 for U.S. Appl. No. 12/189,785, filed Aug. 11, 2008.Applicant
- Non-Final Office Action mailed Feb. 7, 2012 for U.S. Appl. No. 12/637,671, filed Dec. 14, 2009.Applicant
- Non-Final Office Action mailed Feb. 7, 2013 for U.S. Appl. No. 12/970,313, filed Dec. 16, 2010.Applicant
- Non-Final Office Action mailed Feb. 8, 2012 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Non-Final Office Action mailed Apr. 9, 2012 for U.S. Appl. No. 12/771,624, filed Apr. 30, 2010.Applicant
- Non-Final Office Action mailed Dec. 9, 2008 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Non-Final Office Action mailed Oct. 11, 2012 for U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Non-Final Office Action mailed Apr. 12, 2012 for U.S. Appl. No. 12/770,365, filed Apr. 29, 2010.Applicant
- Non-Final Office Action mailed Jul. 12, 2012 for U.S. Appl. No. 12/691,992, filed Jan. 22, 2010.Applicant
- Non-Final Office Action mailed Oct. 12, 2012 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Non-Final Office Action mailed Sep. 12, 2012 for U.S. Appl. No. 12/952,080, filed Nov. 22, 2010.Applicant
- Non-Final Office Action mailed Apr. 13, 2010 for U.S. Appl. No. 11/761,745, filed Jun. 12, 2007.Applicant
- Non-Final Office Action mailed Jul. 13, 2010 for U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Non-Final Office Action mailed Nov. 14, 2012 for U.S. Appl. No. 13/531,757, filed Jun. 25, 2012.Applicant
- Non-Final Office Action mailed Sep. 14, 2010 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Non-Final Office Action mailed Sep. 16, 2011 for U.S. Appl. No. 12/539,537, filed Aug. 11, 2009.Applicant
- Non-Final Office Action mailed Sep. 17, 2012 for U.S. Appl. No. 12/189,780, filed Aug. 11, 2008.Applicant
- Non-Final Office Action mailed Aug. 18, 2011 for U.S. Appl. No. 12/197,958, filed Aug. 25, 2008.Applicant
- Non-Final Office Action mailed Feb. 18, 2011 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Non-Final Office Action mailed Jan. 18, 2012 for U.S. Appl. No. 12/771,071, filed Apr. 30, 2010.Applicant
- Non-Final Office Action mailed Feb. 21, 2013 for U.S. Appl. No. 12/771,372, filed Apr. 30, 2010.Applicant
- Non-Final Office Action mailed Jul. 21, 2010 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Non-Final Office Action mailed Dec. 22, 2010 for U.S. Appl. No. 12/197,931, filed Aug. 25, 2008.Applicant
- Non-Final Office Action mailed Jul. 22, 2013 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Non-Final Office Action mailed May 23, 2013 for U.S. Appl. No. 13/104,932, filed May 10, 2011.Applicant
- Non-Final Office Action mailed May 23, 2013 for U.S. Appl. No. 13/104,936, filed May 10, 2011.Applicant
- Non-Final Office Action mailed Jan. 26, 2012 for U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Non-Final Office Action mailed Nov. 26, 2010 for U.S. Appl. No. 12/197,958, filed Aug. 25, 2008.Applicant
- Non-Final Office Action mailed Jun. 27, 2013 for U.S. Appl. No. 12/019,568, filed Jan. 24, 2008.Applicant
- Non-Final Office Action mailed Dec. 30, 2009 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Non-Final Office Action mailed May 30, 2008 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Notice of Allowance mailed May 14, 2013 for U.S. Appl. No. 12/637,671, filed Dec. 14, 2009.Applicant
- Notice of Allowance mailed Oct. 25, 2012 for U.S. Appl. No. 11/084,232, filed Mar. 16, 2005.Applicant
- Requirement for Restriction/Election mailed Jan. 22, 2013 for U.S. Appl. No. 13/104,932, filed May 10, 2011.Applicant
- Requirement for Restriction/Election mailed Jan. 22, 2013 for U.S. Appl. No. 13/104,936, filed May 10, 2011.Applicant
- Requirement for Restriction/Election mailed Oct. 24, 2012 for U.S. Appl. No. 12/750,470, filed Mar. 30, 2010.Applicant
- Security For The Future, Introducing 5804BD—Advanced two-way wireless remote technology, Advertisement, ADEMCO Group, Syosset, NY, circa 1997.Applicant
- South African Patent App. No. 2013/02668.Applicant
- Supplemental European Search Report for Application No. EP05725743.8 mailed on Sep. 14, 2010, 2 pages.Applicant
- Supplementary European Search Report for Application No. EP10819658, mailed on Mar. 10, 2015, 2 pages.Applicant
- Supplementary European Search Report for Application No. EP11827671, mailed on Mar. 10, 2015, 2 pages.Applicant
- Supplementary European Search Report for Application No. EP2191351, mailed on Jun. 23, 2014, 2 pages.Applicant
- Supplementary Non-Final Office Action mailed Oct. 28, 2010 for U.S. Appl. No. 12/630,092, filed Dec. 3, 2009.Applicant
- Supplementary Partial European Search Report for Application No. EP09807196, mailed on Nov. 17, 2014, 5 pages.Applicant
- Taiwanese Patent App. No. 99113848.Applicant
- Taiwanese Patent App. No. 99113853.Applicant
- Taiwanese Patent App. No. 99113855.Applicant
- Taiwanese Patent App. No. 99113856.Applicant
- Topalis E., et al., “A Generic Network Management Architecture Targeted to Support Home Automation Networks and Home Internet Connectivity, Consumer Electronics, IEEE Transactions,” 2000, vol. 46 (1), pp. 44-51.Applicant
- United Kingdom Patent No. 2428821.Applicant
- United Kingdom Patent No. 2442628.Applicant
- United Kingdom Patent No. 2442633.Applicant
- United Kingdom Patent No. 2442640.Applicant
- Wireless, Battery-Powered Smoke Detectors, Brochure, SafeNight Technology, Inc. Roanoke, VA, 1995.Applicant
- WLS906 Photoelectric Smoke Alarm, Data Sheet, DSC Security Products, Ontario, Canada, Jan. 1998.Applicant
- X10—ActiveHome, Home Automation Made Easy [retrieved on Nov. 4, 2003], 3 pages.Applicant