Patent Grant
9100446
Embodiments of the present invention relate generally to the field of home security, monitoring and automation, and specifically to activation and provisioning of a user-configurable controller for security, monitoring and automation using remotely-stored configuration data.
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.
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.
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).
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.
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 controller to function as a gateway for external network access so that a user can control or monitor devices in locations remote from the dwelling.
Traditional home security and monitoring systems require specialized technicians and equipment to install the system and sensors. These traditional systems can take many hours to install. It is thus desirable for the security monitoring and automation controller of the present invention to incorporate an activation and provisioning workflow that allows for end-users or installers with minimal training to install the controller and associated sensors. It is further desirable for a security, monitoring and automation controller to incorporate activation and provisioning workflow that facilitates downloading of previously-stored configuration information of a previous controller or controller configuration to the controller, in order to avoid a process of reconfiguring the controller from scratch.
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. Embodiments of the present invention further provide for a software-based installation workflow to activate and provision the controller and associated sensors and network. Embodiments of the present invention also provide for downloading of previously stored configuration data to the controller from a remote server.
One embodiment of the present invention provides for configuring a first security, monitoring and automation (SMA) controller by transmitting a unique identifier to a first remote computer over a network connection, wherein the unique identifier is associated with configuration data previously stored by a second remote computer, and the configuration data is compatible with the first SMA controller, receiving the configuration data, storing the configuration data in a memory of the first SMA controller, and configuring the first SMA controller with the stored configuration data.
In one aspect of this embodiment, the configuration data was provided to the second remote computer by a second SMA controller. In a further aspect, the configuration data was provided by the second SMA controller immediately subsequent to an initial configuration of the second SMA controller. In another further aspect, the configuration data was provided by the second SMA controller immediately subsequent to a modification of configuration data of the second SMA controller.
In another aspect of the above embodiment, the configuration data comprises one or more of configuration data for a home domain network, configuration data for a cellular network connection, configuration data for one or more security sensors and security zones, configuration data for one or more monitoring devices, configuration data for one or more home area network devices having an automation interface, configuration data for modular devices coupled to the first SMA controller, and widget programs and associated configuration data for those widget programs.
In another aspect of the above embodiment, the first SMA controller requests the unique identifier using a display device coupled to the first SMA controller. In another aspect of the above embodiment, the first SMA controller tests a communication path to a third remote computer subsequent to configuring the first SMA controller using the stored configuration data.
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. 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.
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.
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. Embodiments of the present invention further provide for a software-based installation workflow to activate and provision the controller and associated sensors and network. In embodiments of the present invention, this workflow includes activation and provisioning through use of configuration data stored by a remote server and downloaded to the controller.
A typical security system installation requires several hours of a trained technician performing on-site procedures. One reason for this is that a typical security system uses a key pad that has a limited feedback capability and then only provides feedback in codes that require a manual to interpret. Further, a typical install requires keypad entry of hundreds of field codes to configure sensors and the central control unit to interpret signals from those sensors. For example, an installation technician must provide information for each sensor as to the type of sensor and the sensor's purpose. Many months of training are required in order to certify a technician to perform such installs. Providing such training requires a significant investment in capital by a security system provider. In addition, the on-site necessity of entry and interpretation of the many installation codes requires a significant amount of on-site time by those technicians. This is an additional investment in resources by the provider.
Embodiments of the present invention address the resource intensive issues presented by installation of traditional systems. The automated installation workflow provided by embodiments of the present invention enables a minimally-trained technician or even an end user to perform an installation of the security, monitoring and automation system. A touch screen display provides detailed information about each step of the installation workflow, and feedback about the results of each step. Embodiments of the present invention thus enable an installation to be performed with significantly reduced on-site presence of a technician, thereby conserving both monetary and human resources of a provider of security, monitoring and automation system services.
In addition, if a typical security system suffers from a failure such that the controller of the system must be replaced, then an installer of the replacement system will need to repeat the entire installation process of providing keypad sequences and recoding all zone and sensor identification information. Embodiments of the present invention provide for remotely storing configuration data and using that remotely stored configuration data to configure a replacement of the original controller. The stored configuration data can also be used in other scenarios, such as reconfiguration after a factory reset of a controller.
Architectural Overview
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, computers, and pagers. 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.
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 gateway 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 (e.g., WiFi, tethered Ethernet, and power-line network). 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.
SMA devices within home domain 110 can include a variety of RF or wireless sensors 130 whose signals are received and interpreted by SMA gateway 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 gateway 120 can be configured to react to a change in state of any of these detectors. 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 gateway 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.
SMA gateway 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 gateway 120 or a remotely connected device. Monitoring devices 140 can be coupled to SMA gateway 120 either wirelessly (e.g., WiFi via router 125) or other connections.
Home automation devices 145 (e.g., home area network devices having an automation interface) can also be coupled to and controlled by SMA gateway 120. SMA gateway 120 can be configured to interact with a variety of home automation protocols, such as, for example, Z-Wave and ZigBee.
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.
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 gateway 120 can be configured with other network protocol controllers such as WiMAX satellite-based broadband, direct telephone coupling, and the like.
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.
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.
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 can provide 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.
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.
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.
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. As will be discussed more fully below, the SMA controller configuration information stored by database server 185 can include all zone and sensor information, and configuration data related to monitoring devices, automation devices, routers and the like.
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.
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.
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.
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.
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.
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
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. Audio processor 225 can, in turn, be coupled to a speaker that provides sound in home domain 110. SMA controller 120 can be configured to provide a variety of sounds for different events detected by sensors associated with the SMA controller. Such sounds can be configured by a user so as to distinguish between alarm and non-alarm events.
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.
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 transceiver to communicate with a variety of RF sensors 130 using a variety of communication protocols. Similarly, home automation transceivers (e.g., home area network devices having an automation interface) that communicate using, for example, 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.
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.
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.
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.
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.
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.
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.
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
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.
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).
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.
As each of these configuration steps are performed, the SMA controller can store the configuration data in a local memory (e.g., memory 260) and transmit the configuration data to an operator domain server 165 for storage (e.g., in database server 185). Alternatively, transmission of the configuration data can occur after all configuration steps in
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.
SMA Controller Activation and Provisioning
As discussed above, embodiments of SMA controller 120 can be configured to monitor and control a variety of security sensors, cameras and automation devices. Embodiments of SMA controller 120 can be further configured to provide an end-user and installer intuitive guided activation and provisioning mechanism for installation of the SMA controller. Through the use of such a guided activation and provisioning mechanism, embodiments of the SMA controller will not require specialized technicians to perform such an installation. Instead, embodiments of the SMA controller are provided with an extensible software-based (e.g., firmware) architecture for an activation workflow that guides the end-user or installer through each step of the activation process and which performs various network and sensor configuration tasks unseen to the person conducting the activation process and without need for user interaction.
The workflow illustrated in
If the router has been located and secured, then the process flow can continue to a creation and securing of a private network (e.g., private WiFi network) on the router (733). Again, commands transmitted to the router for creation and securing of the private WiFi network can be provided through use of the HNAP protocol in accord with appropriate commands stored in the firmware of SMA controller 120. It should be noted that this process of securing a private WiFi network can be combined with securing the router.
Once router 125 is secured and the private WiFi network has been created and secured, SMA controller 120 can interpret the strength of radio signals being received by WiFi transceiver 235 and cellular transceiver 240 (735). The SMA controller can then display the WiFi and cellular signal strengths using a display such as that illustrated in
The SMA controller can be provisioned for a particular cellular (e.g., GSM) network, as pre-configured by a provider of the SMA controller. When the SMA controller communicates with a server in the operator domain (as discussed below), any configuration updates, including those related to GSM provisioning, will be downloaded from the server to the SMA controller. The SMA controller will provide signal strength information regarding the cellular network for which the SMA controller is provisioned, and will use that cellular network as an available communication path.
Once connectivity has been established and confirmed through the available networks, SMA controller 120 can communicate with an operator domain server (e.g., server 165) to determine whether a firmware or configuration update is available for the SMA controller (740). If there are no updates, then the workflow can proceed to the next activation stage (e.g., account setup 620) (747). If an update is available, then the SMA controller can download and store the update from the server (743). Upon completion of the update download, the SMA controller can perform a process to install the update (e.g., firmware) and reboot (745). Once the update has been installed, the activation process flow can continue to the next stage (747).
If the power-line network adapter is successfully located and secured, then the SMA controller can determine cellular signal strength through the use of cellular transceiver 240 and then display that signal strength using a display similar to that illustrated in
Once connectivity to the servers has been established, the SMA controller can determine whether a firmware or configuration update is available (765), and if not can proceed to the next activation stage (747). If an update is available, then SMA controller 120 can download and store the update (743) and install the update (745). Once the update has been completed, then the SMA controller can continue to the next activation stage (747).
It should be noted that in the absence of the presence of an available broadband communication path to the remote servers, the SMA controller can still determine connectivity via the provisioned cellular network. A configuration workflow can make such a determination and provide the appropriate signal strength and connectivity testing.
As illustrated, the process of
Through the use of this information, the provider of SMA services can verify the on-site setup of the SMA controller. In addition, the provider can also track the hardware installed in the home domain for installation inventory purposes, as well as future firmware updates for the SMA controller.
The SMA controller can then search for all sensors that are in discovery mode (920). Additionally, the SMA controller can display a remaining search time indication. A linking message from a sensor can provide information including, for example, a unique identification number for the sensor and sensor type information. An SMA controller touch screen interface can then display zone information associated with each discovered sensor (925).
Once presented with the 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. The person performing the activation process can select a sensor zone to edit (935) and then define or edit the information related to that sensor (940). The information related to the sensors and zone can then be stored in a local memory of SMA controller 120 (e.g., memory 260). The SMA controller can also transmit the sensor zone information to be stored in a server in operator domain 160 via the broadband connection.
A zone function 1340 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.
Selection of a zone function definition can alter 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, according to one embodiment of the present invention.
By defining such zones, a user can control how the security functions of SMA controller 120 react to various sensor triggers.
A user can also configure a display icon 1350 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.
Sensor zone information, entered through the use of a display such as that illustrated in
A user performing an activation/configuration process of the SMA controller can be given an opportunity to edit each discovered sensor zone (945). Once the user has completed the process of editing sensor zones, the user can be provided an opportunity to add a key fob-type device (950). If the user chooses to add the key fob-type device, pairing instructions for key fobs can be displayed (955). Once the key fob-type device is put into a discovery mode, the person performing the activation can instruct the SMA controller to search for the key fob-type device (960). Once the key fob-type device has been found, the user can edit the key fob information in a manner similar to the zone information editing (965). Information such as a person to be associated with a particular key fob and the like can be provided. Once a key fob-type device has been added or addition of a key fob has been bypassed, the activation process can continue to the next stage (970). Again, the information related to the added key fobs can be transmitted by the SMA controller to the operator domain for storage and monitoring.
The process illustrated in
If the person performing the activation wishes to install a camera and the configured network supports such a camera, then the SMA controller can display instructions for preparing the camera monitoring device to be configured to communicate with the secure WiFi network of the SMA controller (1030). For example, an initial configuration of a wireless camera may require an initial hardwired connection to router 125 in order for the SMA controller to provide appropriate instructions for configuration of the camera. Thus, the instructions displayed by the SMA controller may include text and pictures of how to couple the camera monitoring device to the router for this stage of the process.
The SMA controller can also provide the user performing the activation process an opportunity to indicate when the camera monitoring device is coupled to the router or otherwise ready for configuration. The SMA controller can then communicate with the router (e.g., using HNAP) to locate the camera and to receive a MAC address of the camera from the router (1035).
Once the camera configuration process has been performed, the SMA controller can display additional instructions related to re-configuring the camera monitoring device hardware to communicate wirelessly over the secured WiFi (1050).
During the configuration process, the SMA controller can pass a variety of information to the camera, 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. All of this information can be passed between the SMA controller and the camera monitoring device without user interaction beyond the initial configuration of the camera hardware.
Once the SMA controller and camera are configured to communicate with one another, then images generated by the camera can be displayed on a display device associated with the SMA controller. The process flow illustrated in
As illustrated in
Once the acknowledgement is received, the SMA controller can display instructions to the user performing the activation process to contact the appropriate central station to confirm the alarm transmission (1115). Such instructions can include, for example, a phone number for the central station that can be provided by a server in the operator domain upon the initial account setup process 620. The SMA controller can give the user performing the activation process an opportunity to input a verification of a successful communication with the central station (1120). In an alternative embodiment, the SMA controller can be configured to receive an automated confirmation of communication to central station 190 from the central station or from an operator domain server 165. The SMA controller can then display information regarding the automated confirmation on a coupled display to the user performing the activation process.
Once the communication path with the central station has been confirmed, the SMA controller can display a check list for testing each configured zone of the system (1125).
When the alarm sensor is triggered, the SMA controller can display information related to the alarm trigger (1145).
If each zone has been tested or each desired zone has been tested, then the SMA controller can display review information for the various triggered alarms (1165).
In an alternative embodiment, the SMA controller can be configured to receive an automated confirmation of communication of alarm information to central station 190 from the central station or from an operator domain server 165. The SMA controller can then display information regarding the automated confirmation on a coupled display to the user performing the activation process. Such an automated process of alarm information confirmation decreases the time that is needed to perform an installation and testing of the SMA controller setup.
The workflow of
In an alternate embodiment, steps 1210-1230 can be avoided during the installation procedure by assigning default values for the master code, delay times, and the like. The end user can then at a later time set those values through use of interfaces provided on a display coupled to the SMA controller. Use of default values can reduce the amount of time needed for the install of the SMA controller in the home domain.
The SMA controller can then be configured to provide for any additional information that a provider of operator domain 160 wishes to acquire from a subscribing user (1240). A provider of SMA services can modify these process flow steps as desired or necessitated. Any additional instructions that are desired to be provided to the user performing the activation process can be provided on the display associated with the SMA controller (1250) and then the system can be rebooted to activate the SMA controller in accord with all the settings that have been provided during the activation workflow (1260).
The software architecture that provides for the above-described activation/provisioning workflow is customizable to the demands of a provider of the SMA services. Embodiments of the firmware architecture that provides the activation/provisioning workflow can be implemented, for example, using XML-type control files that define each step of the workflow and the display that accompanies that step of the workflow.
When an unconfigured SMA controller is intended to execute the configuration data restoration workflow, the SMA controller will be introduced into a home domain 110 that has previously been configured per
Once the SMA controller is in communication with router 125, the SMA controller can provide a query to a user of the SMA controller as to whether the present installation is a full installation or a restoration installation (e.g., an RMA installation) (1420). If the selection is for a full installation, then the process continues to a network setup workflow 610 (1425), discussed above. If the selection is for a restoration installation, then the system prompts for the user to provide one or more of a subscriber identifier and an alternative unique identifier (e.g., an RMA authorization code) to authenticate the SMA controller to a server in operator domain 160 (1430).
Once authentication of the SMA controller has occurred, a download is performed of SMA controller configuration data previously stored by a server in the operator domain (1440). The SMA controller can request a download of the previously stored configuration data from the operator domain server, or the operator domain server can automatically perform download operations to the SMA controller once the subscriber identifier is authenticated. The server in the operator domain can search for previously stored configuration data that is associated with the subscriber identifier/unique identifier. All the corresponding previously-stored configuration data is downloaded to the SMA controller and stored in the SMA controller memory in the same manner (e.g., formats and locations) as if it were entered on the SMA controller input device (1450). This previously stored configuration data includes not only information about security sensors and zone configurations, but also network configuration information (e.g., information about the previously configured private network), monitoring and home automation devices, as well as widget programs and their configurations.
Once all configuration data has been downloaded and stored on the SMA controller, the SMA controller can be decoupled from the router (if a tethered connection was used for communication between the router and the SMA controller and will not be used for operational communications) (1460) and begin operations using the downloaded configuration data (1470). The router can automatically reconfigure itself to use the downloaded configuration data or may need to be restarted to use the downloaded configuration data. Once the SMA controller is operating using the downloaded configuration data, the person performing the install can be given the option of testing the device communication path (e.g.,
The restoration installation workflow of
In another alternative embodiment, the SMA controller can be introduced to the home domain by resetting the router to factory defaults, rather than maintaining the previously configured settings. The SMA controller can then be coupled to the router using WiFi or tethered connection, as with the original installation detailed above. Once the configuration data has been provided to the SMA controller from the remote server, the SMA controller can use the data to automatically reconfigure the router to provision the secure network to the secured network's original configuration (i.e., corresponding to the network settings saved by the previous SMA controller in the home domain). In addition, the information needed for WiFi or other Ethernet-enabled monitoring devices to exchange data with the SMA controller is also provided when the router is reconfigured.
The result of a restoration installation is an install that bypasses the steps involved in an initial installation and results in an SMA controller that is provisioned in the same manner as a previous SMA controller, including network information, sensor and zone information, automation device information, monitoring device information, and widget program configuration.
With the exception of the restoration installation, the activation/provisioning workflow described above is designed to be performed entirely using SMA controller 120 without the use of any external computing resources or input device beyond a touch screen display associated with the SMA controller and any updates provided by a remote server. Displayed instructions and input screens are incorporated with the software (e.g., firmware) of the SMA controller such that a non-technical end-user or an installation technician without specialized training can perform an install of the SMA controller, along with the associated security sensors, camera monitoring devices, and network routing devices. In addition, since much of the network configuration is performed automatically by the SMA controller, the amount of typing of addresses and other information, and hence the opportunity for errors in such typing, is dramatically reduced. Since the installation process is performed using only a display coupled to the SMA controller, the need for additional equipment, such as a computer to perform the installation, is eliminated, and thereby the cost of performing installations is also reduced. Further, the streamlined process for performing the installation, coupled with the elimination of lengthy typing of addresses and the like, results in a faster installation process with less frustration than is found for typical systems. Thus, if a technician is performing such an installation, the cost for each installation is reduced due to the reduction in the need for installation technician time. Persons of ordinary skill in the art will understand that all of these factors provide advantages to systems embodying the present invention over traditional systems that require additional equipment to perform installations and specialized technician training, thereby increasing the costs for performing such installations.
An Example Computing and Network Environment
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
Bus 1512 allows data communication between central processor 1514 and system memory 1517, 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 1510 are generally stored on and accessed via a computer-readable medium, such as a hard disk drive (e.g., fixed disk 1044), an optical drive (e.g., optical drive 1540), a floppy disk unit 1537, 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 1547 or interface 1548.
Storage interface 1534, as with the other storage interfaces of computer system 1510, can connect to a standard computer-readable medium for storage and/or retrieval of information, such as a fixed disk drive 1544. Fixed disk drive 1544 may be a part of computer system 1510 or may be separate and accessed through other interface systems. Modem 1547 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 1548 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 1548 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.
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
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.
With reference to computer system 1510, modem 1547, network interface 1548 or some other method can be used to provide connectivity from each of client computer systems 1610, 1620 and 1630 to network 1650. Client systems 1610, 1620 and 1630 are able to access information on storage server 1640A or 1640B using, for example, a web browser or other client software (not shown). Such a client allows client systems 1610, 1620 and 1630 to access data hosted by storage server 1640A or 1640B or one of storage devices 1660A(1)-(N), 1660B(1)-(N), 1680(1)-(N) or intelligent storage array 1690.
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.
The foregoing describes embodiments including components contained within other components (e.g., the various elements shown as components of computer system 1510). 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.
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.
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.
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.
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.
Consequently, the invention is intended to be limited only by the scope of the appended claims, giving full cognizance to equivalents in all respects.
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6211783 | Wang | Apr 2001 | B1 |
| 6295346 | Markowitz et al. | Sep 2001 | B1 |
| 6369705 | Kennedy | Apr 2002 | B1 |
| 6756896 | Ford | Jun 2004 | B2 |
| 6873256 | Lemelson et al. | Mar 2005 | B2 |
| 7081813 | Winick et al. | Jul 2006 | B2 |
| 7113090 | Saylor et al. | Sep 2006 | B1 |
| 7262690 | Heaton et al. | Aug 2007 | B2 |
| 7437753 | Nahum | Oct 2008 | B2 |
| 7469139 | van de Groenendaal | Dec 2008 | B2 |
| 7568018 | Hove et al. | Jul 2009 | B1 |
| 7571459 | Ganesh et al. | Aug 2009 | B2 |
| 7751409 | Carolan | Jul 2010 | B1 |
| 7787863 | van de Groenendaal | Aug 2010 | B2 |
| 7890612 | Todd et al. | Feb 2011 | B2 |
| 7921686 | Bagepalli et al. | Apr 2011 | B2 |
| 8200827 | Hunyady et al. | Jun 2012 | B1 |
| 8239477 | Sharma et al. | Aug 2012 | B2 |
| 20020116117 | Martens et al. | Aug 2002 | A1 |
| 20030062997 | Naidoo et al. | Apr 2003 | A1 |
| 20030158635 | Pillar et al. | Aug 2003 | A1 |
| 20040117462 | Bodin et al. | Jun 2004 | A1 |
| 20040117465 | Bodin et al. | Jun 2004 | A1 |
| 20050149746 | Lu et al. | Jul 2005 | A1 |
| 20050216580 | Raji et al. | Sep 2005 | A1 |
| 20050276389 | Hinkson et al. | Dec 2005 | A1 |
| 20060051122 | Kawazu et al. | Mar 2006 | A1 |
| 20060067484 | Elliot et al. | Mar 2006 | A1 |
| 20060078344 | Kawazu et al. | Apr 2006 | A1 |
| 20060129837 | Im et al. | Jun 2006 | A1 |
| 20060209857 | Hicks, III | Sep 2006 | A1 |
| 20090066789 | Baum et al. | Mar 2009 | A1 |
| 20090070436 | Dawes et al. | Mar 2009 | A1 |
| 20090070477 | Baum et al. | Mar 2009 | A1 |
| 20090070681 | Dawes et al. | Mar 2009 | A1 |
| 20090070682 | Dawes et al. | Mar 2009 | A1 |
| 20090070692 | Dawes et al. | Mar 2009 | A1 |
| 20090074184 | Baum et al. | Mar 2009 | A1 |
| 20090077167 | Baum et al. | Mar 2009 | A1 |
| 20090077622 | Baum et al. | Mar 2009 | A1 |
| 20090077623 | Baum et al. | Mar 2009 | A1 |
| 20090077624 | Baum et al. | Mar 2009 | A1 |
| 20090134998 | Baum et al. | May 2009 | A1 |
| 20090138600 | Baum et al. | May 2009 | A1 |
| 20090138958 | Baum et al. | May 2009 | A1 |
| 20090165114 | Baum et al. | Jun 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 584 217 | Jan 1987 | FR |
| WO 9934339 | Jul 1999 | WO |
| WO 2004098127 | Nov 2004 | WO |
| WO 2005091218 | Sep 2005 | WO |
| WO 2009006670 | Jan 2009 | WO |
| Entry |
|---|
| “Control Panel Standard—Features for False Alarm Reduction,” The Security Industry Association, © SIA 2009, pp. 1-48. |
| Number | Date | Country | |
|---|---|---|---|
| 20100280635 A1 | Nov 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61174366 | Apr 2009 | US |
