TWI517106B - Method, system and apparatus for activation of a home security, monitoring and automation controller - Google Patents

Description

Method, system and device for initiating home security, monitoring and automation controllers Cross-references to related applications

This invention claims priority to the Provisional Patent Application Serial No. 61/174,366 filed on Apr. 30, 2009, which is entitled "REMOTE SECURITY STATION" and invented by Alan Wade Cohn. The entire contents of this provisional patent application are hereby incorporated herein by reference in its entirety for all purposes for all purposes.

Field of invention

Embodiments of the present invention are generally related to the field of home security, surveillance, and automation, and particularly to the initiation and provisioning of a user-configurable controller for security, surveillance, and automation.

Background of the invention

Home electronics and control standards offer opportunities to preserve, monitor, and automate homes. The wireless protocol used to transmit security information allows for the placement of a large number of security sensors throughout the home without the need to route the wires back to a central control panel. Cheap wireless cameras also allow cameras to be placed throughout the home for easy home surveillance. Various home automation control protocols have also been developed to allow for centralized remote control of lights, appliances, and environmental devices (eg, thermostats). Traditionally, each of these security, surveillance, and automation protocols requires a separate planning, control, and monitoring station. If the home automation and surveillance system is coupled to a home security system, such coupling requires the automation and surveillance system to be included as a subordinate to the existing home security system. This limits the flexibility and versatility of automation and monitoring systems and constrains these systems to the perimeter architecture.

In the case of a violation of a house secured by a security system, the security system alerts the occupants and emergency agencies. A typical security system includes a controller that is connected by wireless and wired connections to sensors disposed at various locations in a secured home. At home, sensors are typically placed at doorways, windows, and other entry points. Mobile sensors can also be strategically placed at home to detect unauthorized tampering while smoke and thermal sensors detect fire.

A home monitoring system provides the ability to monitor a state in a state so that a user is aware of any changes in the monitored state. For example, when a sensor is triggered, an immediate alert signal and associated data (such as a video or photo clip) can be transmitted to the user (eg, to a network connected computer or to a mobile device).

A home automation system enables automation and remote control of lifestyle amenities such as lighting, heating, air conditioning and appliances. Typically, these various lifestyle amenities are coupled to a controller via a wireless or wired communication protocol. A central device is then used to plan various lifestyle amenities.

What is expected is to have a centralized controller that can operate in each of the security, surveillance, and automation environments, rather than using multiple devices to control each environment, thereby reducing the number of devices required in the home. It is further anticipated that such a controller functions as a gateway for external network access to enable a user to control or monitor the device at a location remote from the home.

Traditional home security and surveillance systems require specialized technicians and equipment to install systems and sensors. It can take several hours to install these traditional systems. It is therefore expected that the security, monitoring and automation controller of the present invention will incorporate a start-up and provisioning workflow that allows the least trained end user or installer to install the controller and associated sensors.

Summary of invention

Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring, and automation, as well as providing an ability to function as a two-way Internet gateway. Embodiments of the present invention provide such functionality by virtue of a composable architecture that enables a user to adapt the system to meet the particular needs of the user. Embodiments of the present invention further provide a software-based installation workflow for enabling and providing controllers and associated sensors and networks.

In an embodiment of the invention, a method for assembling a security, monitoring and automation (SMA) controller is provided. The method includes assembling a network in a network including the SMA controller using an SMA controller, using the SMA controller to assemble one or more security sensors, monitoring devices, or having to be used with the SMA The controller communicates with an automated interface for the home area network device and tests a communication path between the SMA controller and a remote server.

In a level of the above embodiment, the method further includes assembling one or more zones associated with each of the security sensors and testing an alert communication path. In another aspect, a script is executed by the SMA controller, which directs a user of the SMA controller through various assembly steps. Executing the script causes the SMA controller to display a series of user interfaces on an associated display.

In yet another aspect, the alarm communication path includes a link between a security sensor and the SMA controller and a network link between the SMA controller and the remote server . Additionally, the alert communication path can include a link between the remote server and an alert center station. Testing the alarm communication path can include receiving, by the SMA controller, a sensor fault event signal from the security sensor when the SMA controller is in an armed state and then failing with the sensor through the network link Information about the event signal is transmitted to the remote server. The information related to the sensor fault event signal can include an identifier of the hold sensor.

In another aspect, assembling the full sensor to communicate with the SMA controller includes the SMA controller searching for each of the security sensors to display information corresponding to each of the found security sensors And pair each sensor that has been found. In yet another level, the SMA controller can be used to edit information about each zone.

In another level of the above embodiment, assembling the network in the domain including the SMA controller includes positioning for a network router in response to a command transmitted from the SMA controller to the network router To secure the network router and establish a secure network including the SMA controller and the network router. The assembly of the network can further include performing a connection test between the SMA controller and the remote server using the security network. The security network can be a WiFi (wireless fidelity) network. Assembling the network may also include performing a connection test for the cellular network associated with the SMA controller and performing a connection test between the SMA controller and the remote server using the cellular network.

In another aspect of the above embodiment, assembling the network in the domain including the SMA controller includes positioning for a power line network adapter and responding to transmission from the SMA controller to the power line network The route adapter command saves the power line network adapter.

In another aspect of the above embodiment, the method further includes executing, by the SMA controller, a script by assembling the network, the security sensors, the monitoring device, and the home having an automated interface The local area network device directs a user of the SMA controller and tests the communication path.

Simple illustration

The invention will be better understood and many of its objects, features and advantages will be apparent to those skilled in the art.

1 is a simplified block diagram showing an architecture including a set of logical domains and functional entities in which embodiments of the present invention interact.

FIG. 2 is a simplified block diagram showing a hardware architecture of an SMA controller in accordance with an embodiment of the invention.

Figure 3 is a simplified block diagram showing a logical stack of the firmware architecture of an SMA controller that can be used with embodiments of the present invention.

FIG. 4 illustrates an exemplary user interface of an SMA controller 120 in accordance with an embodiment of the present invention.

Figure 5 is a simplified flow diagram illustrating the steps performed in the assembly process of an SMA controller in accordance with an embodiment of the present invention.

Figure 6 is a simplified flow diagram showing an example of a general workflow for activating and providing an SMA controller in accordance with an embodiment of the present invention.

Figure 7 is a simplified flow diagram showing an embodiment of a flow of network settings that may be used in embodiments of the present invention.

Figure 8 is a simplified flow diagram showing an example of an account setup workflow that may be used by embodiments of the present invention.

Figure 9 is a simplified flow diagram showing a procedure for assembling a security sensor that can be used in embodiments of the present invention.

Figure 10 is a simplified flow diagram showing a procedure for adding a camera or other monitoring device during startup of an SMA controller that can be used in embodiments of the present invention.

Figure 11 is a simplified flow diagram showing an exemplary flow for an alarm path communication test that can be used in embodiments of the present invention.

Figure 12 is a simplified flow diagram showing a procedure for a post-launch workflow that can be used in embodiments of the present invention.

13A-R illustrate an example of a display provided by an SMA controller in accordance with an embodiment of the present invention.

Figure 14 is a block diagram of a computer system suitable for implementing the aspects of the present invention.

Figure 15 is a simplified block diagram of a network environment suitable for implementing aspects of the present invention.

Detailed description

Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring, and automation, as well as providing an ability to function as a two-way Internet gateway. Embodiments of the present invention provide such functionality by virtue of a composable architecture that enables a user to adapt the system to meet the particular needs of the user. Embodiments of the present invention further provide a software-based installation workflow for enabling and providing controllers and associated sensors and networks.

A typical security system installation requires a trained technician to spend several hours to perform the on-site process. One reason for this is that a typical security system uses a small keyboard with limited feedback capabilities, and only provides feedback for code that requires manual interpretation. Moreover, a typical installation procedure requires inputting hundreds of columns from the keypad to assemble the sensor and central control unit to interpret signals from such sensors. For example, an installation technician must provide information about the sensor type and sensor usage for each sensor. It takes several months of training to issue a certificate of competency to a technician performing such an installation. A security system provider requires significant investment funds to provide such training. In addition, the need to enter and interpret a large number of installation code on site requires that such technicians spend a lot of time on site. This is an additional resource investment for the provider.

Embodiments of the present invention address the resource intensive issues exhibited by installing legacy systems. The automated installation workflow provided by embodiments of the present invention enables a minimally trained technician or even an end user to install a security, surveillance, and automation system. A touch screen display provides detailed information about each step of the installation workflow and feedback on the results of each step. Thus, embodiments of the present invention enable installation to be performed while significantly reducing technicians' presence time, thereby saving both overhead and human resources for a provider of security, surveillance, and automation system services.

Architectural overview

Embodiments of the composable security, surveillance, and automation (SMA) controller of the present invention are used not only to communicate with signals from sensors and devices located in a home and for interpreting from a residence Signals from the sensors and devices, and are used to access and monitor such sensors and devices at locations remote from the home. Embodiments of the SMA controller provide this capability via an access network (such as the Internet, a provider network, or a cellular network) through a link to an external server. The external server provides an portal environment through which a user can, for example, instantly monitor the status of the sensor coupled to the SMA controller, assemble the controller, and control information Provided 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 conventional security central station that can be contacted if the SMA controller in the home detects an alarm condition.

1 is a simplified block diagram showing an architecture including a set of logical domains and functional entities in which embodiments of the present invention interact. A home domain 110 includes an embodiment of an SMA controller 120. The home domain is coupled via an access network 150 to an operator domain 160 that includes various servers. The servers are then coupled to a central station 190 and coupled to various remote user communication options.

The home domain refers to a collection of security, surveillance, and automation entities within a home or other location with SMA devices. The SMA controller 120 is a device that provides an end user SMA interface to various SMA entities (e.g., radio frequency sensors) within the home domain 110. The SMA controller 120 further acts as a gateway interface between the home domain 110 and the operator domain 160. The SMA gateway 120 provides such gateway access to the operator domain 160 via a network router 125. The network router 125 can be coupled to the SMA controller 120 and to a home network device, such as a home computer, via a wired or wireless connection (eg, WiFi, tethered Ethernet, and power line network). 127. A network router 125 coupled to a broadband data machine (e.g., a cable modem or DSL modem) acts as a link to the network in the access network 150.

The SMA device within the home network 110 can include various RF or wireless sensors 130 whose signals are received and interpreted by the SMA gateway 120. The RF sensor 130 can include, for example, a door or window sensor, a motion detector, a smoke detector, a glass break detector, an inertial detector, a water detector, a carbon dioxide detector, and a key chain device. The SMA gateway 120 can be configured to react to changes in the state of any of the detectors. In addition to acting and reacting to changes in the state of the RF sensor 130, the SMA controller 120 can also be coupled to an legacy security system 135. The SMA controller 120 controls the legacy security system by interpreting signals from sensors coupled to the legacy security system and reacting in a user-associated manner. The SMA gateway 120, for example, will provide alarm or sensor status information from the legacy security system 135 to a server in the operator's domain 160, which ultimately informs the central station 190 to take appropriate action.

The SMA gateway 120 can also be coupled to one or more monitoring devices 140. The monitoring device 140 can include, for example, a camera and a video camera that provide images viewable on a screen of the SMA gateway 120 or a remote connection device. The monitoring device 140 can be coupled to the SMA gateway 120 in a wireless manner (eg, via WiFi via router 125) or in other connections.

A home automation device 145 (eg, a home area network device with an automated interface) can also be coupled to and controlled by the SMA gateway 120. The SMA gateway 120 can be configured to interact with various home automation protocols such as, for example, Z-Wave and ZigBee.

Embodiments of the SMA controller 120 can be configured to communicate with various RF or wireless sensors and are not limited to the RF sensors, monitoring devices, and home automation devices discussed above. It will be appreciated by those skilled in the art that embodiments of the invention are not limited to the devices and sensors discussed above or are not limited by the devices and sensors discussed above, and are applicable to other Area and device.

Embodiments of the SMA controller 120 can be used to assemble and control home security devices (eg, 130 and 135), monitoring devices 140, and automation devices 145, either directly or by providing a gateway to the operator's domain. Remote control by the server in 160 is performed. The SMA controller 120 communicates with a server residing in the operator's domain 160 via a network in the access network 150. Broadband communication can be provided by coupling the SMA controller 120 to a network router 125, which in turn is coupled to a wide area network 152 via a suitable broadband data machine, such as a provider network or the Internet. road. The router can be coupled to the wide area network via cable broadband, DSL, and the like. The wide area network 152 is then coupled to servers in the operator domain 160 via a series of appropriate routers and firewalls (not shown). The SMA controller 120 can include an additional mechanism to provide a communication connection to communicate with the operator's domain. For example, the SMA controller 120 can be assembled using a cellular network transceiver that permits communication with a cellular network 154. Next, the cellular network 154 can access the servers in the operator domain 160 via routers and firewalls. Embodiments of SMA controller 120 are not limited to providing gateway functionality via cellular routers and modems and home based routers and modems. For example, SMA gateways 120 can be assembled using 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 network providing a terminal user interface (such as an portal accessible by SMA service users), the terminal user interface The SMA components in the home domain 110 can be configured, managed, and controlled. The servers in the operator domain 160 can be maintained by a provider (operator) of the subscriber-based service for SMA operations. Examples of providers include cable providers, telecommunications providers, and the like. An actual execution server architecture in the operator domain 160 can support SMA systems in millions of home domains 110.

The individual server architectures can be of various types, and in one embodiment, the server architecture is a one-tier Java 2 Enterprise Edition (J2EE) service oriented architecture. Such a tiered service oriented architecture can include an interface layer, a service layer, and a data access logic layer. The interface layer can provide entry points from outside the server program (including, for example, browser web applications, mobile web applications, web services, HTML, XHTML, SOAP, and the like). A service layer can provide a variety of optional functions that are passed from the operator to the end user. The service layer can be related to the end user subscription level provided by the operator (for example, the payment level corresponding to the "Gold" level service, the "Silver" level service, and the "Bronze" level service). Finally, the data access logic layer accesses a variety of sources, including database servers.

FIG. 1 depicts an exemplary set of servers that may be provided in the operator domain 160. Server 165 can support all non-alarm and alarm events, heartbeats, and command traffic between various servers and SMA controller 120. Server 165 can also manage end user email and SMS notifications, as well as integration with provider billing, provisioning, inventory, technical support systems, and the like.

An 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 application accessible to an end user that allows an end user to remotely access a corresponding SMA controller via a standard web-based application. Use this subscriber portal to access the same SMA functionality as would be provided by an interface directly coupled to the SMA controller, plus additional features such as alarm and contact management, historical data, interface toolset and camera Management, account management and similar. An action portal can provide all or part of the access rights that an end user can use via the subscriber portal. However, an action portal may be limited by the performance of an access device (eg, a touch screen or a non-touch screen cellular phone). A management portal provides an operator representative access to support and manage the SMA controllers and corresponding user accounts in the home domain 110 via a web-based application. The management portal can provide multiple management support so that the level of access to user information can be limited based on the permissions of a particular employee.

The telephony server 180 can process and transmit information related to alarm events received from the SMA controller 120 to alert the receiver located at the central monitoring station 190. A server 165 that handles the alarm event sends a request to the telephone server 180 to dial the receiver of the central station and transmit the corresponding contact information. Telephony server 180 can communicate with a plurality of central stations 190. The server 165 can determine and contact a correct central station based on the user account settings associated with the SMA controller that is transmitting. Thus, based on the user account, alerts can be scheduled to be routed to different central stations. Moreover, the account can be transferred from one central station to another by modifying user account information. The telephony server 180 can communicate with an alert receiver located at the central station 190 using, for example, a full-service standard contact identification protocol (e.g., dual tone multi-frequency [DTMF]) and broadband protocols.

A backup server 175 can be provided to ensure that an alert path is available when one or more servers 165 are unavailable or unreachable. A backup server 175 can be located at the same physical location as the server 165 to handle situations in which one or more of the servers have failed. Alternatively, a backup server 175 can be placed in a location remote from the server 165 to handle a network failure or power failure resulting in one or more of the plurality of servers 165 being unavailable. Happening. The SMA controller 120 can be configured to communicate such events to a backup server 175 when it is unable to successfully transmit an alert event to the server 165.

A database server 185 provides storage of all of the grouping and user information that can be accessed by other servers within the operator's domain 160. A library provided by the database server 185 can be selected based on various criteria including, for example, the adjustability and availability of the data. An embodiment of the invention uses a database service provided by an ORACLE database.

A server 165 located in the operator's domain 160 provides various functions. Logically speaking, a server 165 can be divided into the following functional modules: a broadband communication module, a cellular communication module, a notification module, a telephone communication module, and an integrated module.

The broadband communication module manages broadband connections and message traffic from a plurality of SMA controllers 110 to 165. Embodiments of the present invention provide a broadband channel as a primary communication channel between an SMA controller 120 and a server 165. The broadband communication module processes various communications on the wideband channel, including, for example, all non-alarm and alarm events, wideband heartbeats, and traffic commands between the server 165 and the SMA controller 120. Embodiments of the present invention provide a permanent TCP socket connection that maintains a continuous connection between each SMA controller and server 165. Various protocols are available for communication between the server 165 and the SMA controller 120 (e.g., TCP-based XML, and the like). This type of communication can be preserved using standard Transport Layer Preservation (TLS) technology. The server 165 provides approximate instant communication between the server and an SMA controller 120 by using a continuous connection socket connection. For example, if a user activates a subscriber portal and triggers a zone in the home domain 110, a zone failure will be reflected almost instantaneously on the subscriber portal website user interface.

The cellular communication module manages cellular connections and message traffic from the SMA controller 120 to a server 165. Embodiments of the present invention use a cellular channel as a backup communication channel for a wideband channel. Therefore, if a broadband channel is not available, communication between an SMA controller and a server is switched to the cellular channel. At this point, the cellular communication module running on the server processes all non-alert and alarm events from an SMA controller, as well as command traffic. When a broadband channel is active, a heartbeat message can be periodically transmitted on the cellular channel to monitor the cellular channel. When using a cellular protocol communication stack, a TCP socket connection can be established between the SMA controller and the server to ensure reliable delivery of critical messages (eg, alarm events and commands). Once the key messages have been exchanged, the TCP connection can be closed to reduce the cost of cellular communications. Like broadband communications, XMPP can be a messaging protocol for such communications. Similarly, TLS and SASL authentication protocols can be used to preserve such communications. UDP can be used to transfer non-critical messages between an SMA controller and a server. A compressed binary protocol can be used as a messaging protocol for such communications to minimize the cost of cellular communications for such traffic. This information can be preserved using an encryption algorithm such as the Micro Encryption Algorithm (TEA). Honeycomb communication can be established on two network segments: a network of GSM service providers providing a path between an SMA controller and a cellular access point, and between the access point and an operator network A VPN tunnel between domain data centers.

A notification module of the server 165 determines whether and how a user should be notified of an event generated by the corresponding SMA controller 120. A user can specify who to notify a particular event or type of event and how to notify the user (eg, phone call, email, text message, page, and the like), and this information is provided by a database The server 185 stores it. When an event such as an alarm or non-alarm event is received by a server 165, such events can be asynchronously communicated to the notification module, which is based on the user configuration to determine if, to whom, and how to transmit the event. Notice.

The telephone communication module provides communication between a server 165 and the telephone server 180. When a server 165 receives an alarm event and performs an initial process of an alarm event, the telephony module forwards the event to a telephony server 180, which in turn communicates with a central station 190, as described above Discussant.

The integrated module provides an architecture and interface for integrating a server 165 with an operator's commercial system, such as, for example, charging, provisioning, inventory, technical support, and the like. An integrated module can provide a web service interface for upstream integration such that the operator commercial system can invoke the website service interface to perform a database similar to creating and updating accounts and querying stored in the database server 185. The operation of the information in. An integrated module can also provide an event-driven architecture for downstream integration to inform operators of commercial systems of events occurring within the SMA system.

SMA controller architecture

FIG. 2 is a simplified block diagram showing a hardware architecture of an SMA controller in accordance with an embodiment of the invention. A processor 210 is coupled to a plurality of communication transceivers, interface modules, memory modules, and user interface modules. The processor 210 executing the firmware, which will be discussed below, performs various tasks related to interpreting the alarms and non-alert signals received by the SMA controller 120, depending on whether it is received or input from a server (e.g., server 165). The information provided by an interface (eg, a touch screen 220) provided by the SMA controller 120 is used to interpret the response to such signals. Embodiments of the invention may use various processors, such as an ARM core processor, such as the FREESCALE i.MX35 multimedia application processor.

The SMA controller 120 can provide user input and display via a touch screen 220 coupled to the processor 210. By using an audio processor 225, the processor 210 can also provide audio feedback to a user. The audio processor 225 can then be coupled to a speaker that provides sound in the home domain 110. The SMA controller 120 can be configured to provide various sounds for different events detected by sensors associated with the SMA controller. These sounds can be assembled by a user to distinguish between alarm and non-alert events.

As discussed above, an SMA controller 120 can communicate with a server 165 using different network access devices. The processor 210 can connect to the PHY 130 via an Ethernet broadband connection or via a WiFi transceiver 235 to access a router (eg, router 125). The router can then be coupled to or incorporated into an appropriate broadband data machine. The cellular network connection can be provided by a cellular transceiver 240 coupled to the processor 210. A set of rules can be utilized to assemble the SMA controller 120, which determines when the processor 210 will switch between a broadband connection to a carrier network 160 and a cellular connection.

To communicate with various sensors and devices in the home domain 110, the processor 210 can be coupled to one or more transceiver modules via, for example, a serial peripheral interface, such as the SPI bus 250. These transceiver modules permit communication in a configurable manner with sensors that use various protocols. Embodiments of the present invention may use a transceiver to communicate with various RF sensors 130 that use various communication protocols. Similarly, a home automation transceiver (eg, a home area network device with an automated interface) for communicating using, for example, a Z-Wave or ZigBee protocol, can be coupled to the processor 210 via the SPI 250. If the SMA controller 120 is coupled to an legacy security system 135, a module that is permitted to be coupled to the legacy security system can be coupled to the processor 210 via the SPI 250. Other protocols may be provided via such plug-in modules, including, for example, Digital Enhanced Wireless Telecommunications (DECT). In this manner, an SMA controller 120 can be configured to control various devices and protocols now known and future known. In addition, processor 210 can be coupled to other types of devices (eg, transceivers or computers) via a universal serial bus (USB) interface 255.

In order to store the combination information of the SMA controller 120 locally, a memory 260 is coupled to the processor 210. Additional memory may be coupled to processor 210 via, for example, a secure digital interface 265. A power source 270 is also coupled to the processor 210 and to other devices within the SMA controller 120 via, for example, a power management controller module.

The SMA controller 120 is configured as a client device device that cooperates with server counterparts in the operator domain 160 to perform the functions required for security monitoring and automation. Embodiments of SMA controller 120 provide a touch screen interface (e.g., 220) for all SMA features. The SMA controller bridges the sensor network, the control network, and the full-panel network to the broadband and cellular networks via various modules coupled to the processor 210. The SMA controller 120 further uses the protocols discussed above to bring alarms and activity events to servers located in the operator's domain for processing. These connections also carry grouping information, provisioning orders, management and reporting information, security authentication, and any instant media, such as video or audio.

Figure 3 is a simplified block diagram showing a logical stack of the firmware architecture of an SMA controller that can be used with embodiments of the present invention. Since the SMA controller 120 provides a security function for the home domain 110, the SMA controller should be a highly available system. High availability means that regardless of whether a component of the system fails, the SMA controller should be ready for an end user to interact with the SMA controller through a user interface and when an alarm and other non-critical system events occur. Provide services. To provide such high availability, the SMA controller 120 operates a micro-core operating system 310. An example of a micro-core operating system that can be used by embodiments of the present invention is a QNX instant operating system. Under the control of this micro-core operating system, drivers, applications, protocol stacks, and file systems operate in the user space protected by the memory outside the core of the operating system. This micro-core operating system provides fault resilience through features such as critical process monitoring and adaptive partitioning. As a result, components (including low-level drivers) can fail and auto-restart without affecting other components or the core and without having to reboot the system. A critical process monitoring feature allows the failed component to automatically restart because these components function in user space. An adaptive partitioning feature of the micro-core operating system provides CPU resource guarantees for specified components, thereby preventing one component from consuming all CPU resources to be detrimental to other system components.

A core layer 320 of the firmware architecture provides service/event libraries and client API library components. A client API library can register managers and drivers to handle events and tell other managers or drivers to perform certain actions. The service/event library maintains a list of listeners for events that are detected by each manager or driver and that perform allocations based on a list in the list.

Drive layer 330 interacts with the hardware peripheral devices of SMA controller 120. For example, the driver can be coupled to the touch screen 220, the broadband connection 230, the WiFi transceiver 235, the cellular transceiver 240, the USB interface 255, the SD interface 265, the audio processor 225, and the processor 210 via the SPI interface 250. Various modules are used. Management layer 340 provides business logic and control logic for use by other layers. The manager is available for alert activity, security agreements, keypad functions, communication functions, audio functions, and the like.

The keypad user interface layer 350 drives the touch screen user interface of the SMA controller 120. An example of the touch screen user interface consists of a header and a footer, an interface tool set icon, and a basic interface tool set user interface. The keypad user interface layer 350 drives the user interface elements by providing, for example, the indicator of the system Arm/Disarm interface button and the battery power information, the interface tool set icon in the standard Management of the position in the user interface area between the head and the footer and interaction with the interface tool set engine layer 360 when the interface tool set icon is selected to display the basic interface tool set user interface.

In an embodiment of the invention, a typical SMA controller function is represented in the touch screen user interface as an interface tool set (or activity icon). The interface toolset provides access to various security, monitoring, and automation control functions of the SMA controller 120 and provides support for multimedia functions through an interface tool set that provides, for example, news, sports, weather, and digital photo frame functions. A primary user interface screen can provide a set of icons, each of the set of icons representing an interface toolset. Select an interface toolset icon to launch the interface toolset. The interface toolset engine layer 360 includes, for example, an interface toolkit engine for native, HTML, and FLASH-style interface toolsets. The interface toolset engine is responsible for displaying a specific set of interface tools on the screen. For example, if an interface toolset is developed in HTML format, selecting such an interface toolset will cause the HTML interface toolset engine to display the selected interface toolset or touchscreen 220. Information related to various interface tool sets is provided in interface tool set layer 370.

FIG. 4 illustrates an exemplary user interface for an SMA controller 120 in accordance with an embodiment of the present invention. The depicted user interface provides a set of interface toolset icons 410 that provide access to the functionality of the SMA controller 120. As shown, the interface toolset is provided to access security functions, images captured with the camera, thermostat control, lighting control, and other settings of the SMA controller. An additional set of interface tools is provided to access web-based information such as weather, news, traffic, and digital photo frame functions. A header 420 provides access to an Arm/Disarm button 425 that allows the security system to be alerted or disarmed. This header provides additional information such as, for example, a network status message. A footnote 430 can provide additional status information, such as the time and date shown in the figure.

A user can select an interface tool set that corresponds to the desired function. Embodiments of the present invention are for providing access to an interface toolset via portal server 170. For all users or based on the user level (eg, the subscription level associated with the payment level), a provider of the operator's domain 160 can determine the functionality that can be accessed by the user. A user can then select from the set of accessible interface tools and the selected set of interface tools will be distributed and displayed on the user interface of the SMA controller 120. The composability of the SMA controller 120 is also driven by the actions and reactions determined by the user for sensor stimulation.

SMA controller's composability

In accordance with an embodiment of the present invention, SMA controller 120 can be assembled by a user to provide desired functionality in home network 110. In addition to the hardware composability options discussed above (eg, modules coupled to the SPI interface 250), the SMA controller 120 provides additional configuration through the use of software and/or firmware. For example, SMA controller 120 can be configured to receive signals from various security sensors (eg, RF sensor 130) and is configured to associate such sensors with the physical environment of home domain 110. In addition, the SMA controller 120 can be configured to receive photos and video information from one or more cameras, provide various programs and utilities to a user, and can be configured to work with various home automation devices. communication.

Figure 5 is a simplified flow diagram showing an example of the steps performed in the assembly process of an SMA controller in accordance with an embodiment of the present invention. An embodiment of an SMA controller will typically be assembled using security sensor information from RF sensor 130 or from an old security system 135. Accordingly, an SMA controller will be configured to access and interpret information related to such security sensors (step 510).

A determination can then be made as to whether a user has a security camera in the home domain 110 (step 520). If the camera is included in the home network, a series of steps associated with the camera unit are performed (step 530). Similarly, a determination can be made as to whether the home automation device is controlled by the SMA controller (step 540). If controlled, a series of steps are performed to assemble the SMA controller to access the home automation devices (step 550).

A user can then perform the steps necessary to assemble the set of interface tools accessible via the SMA controller (step 560). As discussed above, the user can pick up an portal server (e.g., 170) to select and assemble the set of interface tools that are desired to be accessed at the SMA controller 120. Once such assembly steps are performed, the SMA controller is available for performing tasks related to maintaining, monitoring the home domain 110, and providing automated control of the home domain 110.

The SMA controller 120 can be configured to receive and interpret signals from various security sensors. Such sensors may include, for example, a door/window sensor that detects opening and closing of a door or window, a motion detector that detects movement in a zone of interest, a smoke detector, a glass break detector, Inertial detector and key chain. To effectively interpret signals from such detectors, embodiments of SMA controller 120 may search for signals from such sensors and assemble using information related to the position and mission of such sensors.

SMA controller startup and supply

As discussed above, embodiments of the SMA controller 120 can be configured to monitor and control various security sensors, cameras, and automation devices. Embodiments of the SMA controller 120 can be further configured to provide an intuitive guided startup and provisioning mechanism for an end user and installer for the installation of the SMA controller. By using this bootstrapping and provisioning mechanism, the embodiment of the SMA controller will not require a technician to perform this setup. Rather, the embodiment of the SMA controller is equipped with an architecture based on an extensible software (e.g., firmware) for initiating a workflow that directs the terminal through each step of the boot process. The various installers and installers and the various network and sensor combinations that are not visible to the person implementing the launcher do not need to interact with the user.

Figure 6 is a simplified flow diagram showing an example of a general workflow for enabling and providing an SMA controller 120. The general workflow diagram includes high-level setup tasks, which will be described in more detail below. A network setup 610 can be implemented, wherein the SMA controller 120 is configured to assemble a home domain router (e.g., router 125) and to establish and maintain communications from the SMA controller and other SMA controllers. A dedicated WiFi network used by the device. Network setup tasks may also include, for example, testing connection and firmware updates from the home domain 110 to servers located in the operator domain 160. Using an interface coupled to the SMA controller 120, an account setup step 620 can be performed by which the implementer can provide subscriber information to a server located in the operator's domain. The security sensor and associated zones can be assembled (step 630) and the surveillance camera can be coupled to the network of the SMA controller (step 640). The general launch workflow may also include tasks associated with the alert path communication test 650, where a determination may be made as to whether the alert information was correctly received by the central station 190. Finally, various post-launch assembly tasks can be performed (step 660) including, for example, providing various security code and delay times.

The workflow illustrated in FIG. 6 is intended as an example of various high-level tasks that can be performed using an SMA controller 120 when executing a startup program. The various steps involved in the initiation may be subdivided or supplemented in various ways and the initiation workflow of embodiments of the present invention should not be construed as being limited to the steps illustrated in FIG. Moreover, the order of the steps illustrated in Figure 6 is intended to be an example but not a requirement, except that the steps of previously configuring a network for communication are required. Moreover, in some configurations, the SMA controller can be configured to provide one or more of security, monitoring, and automation controls, without necessarily including all three. Thus, steps associated with the combination of any of those functions not required for a particular home domain can be avoided.

FIG. 7 is a simplified flow diagram showing an embodiment of a process for network setup 610. By using this network setup process, an embodiment of the SMA controller 120 can perform tasks associated with maintaining a router 125 located in the home domain 110 to perform home security and monitoring communications using an secured network. Since the embodiment of the SMA controller 120 envisions the use of various home network connection options, the installer is provided with an opportunity to enter an appropriate network type through which the SMA controller is serious. The home network domain is configured to communicate (step 705). The opportunity to provide this information can be given by using a display coupled to the SMA controller 120 and a touch screen. Figure 7 illustrates the workflow associated with two different home network options (e.g., a wireless router or a power line network adapter (e.g., Home Power Line Network (HomePlug)), but the SMA controller 120 Embodiments are not limited to the use of such network options. Different network options may be provided for an SMA provider or a SMA provider may provide different workflows for them, and implementation of the SMA controller 120 The examples are not limited to those illustrated in Figure 7. For example, an SMA controller 120 can be coupled to a router 125 via a tethered Ethernet (e.g., a twisted pair connection) without necessarily requiring a group With a secured wireless or powerline network, a different workflow is available for this connection.

FIG. 13A illustrates an example of a display screen for providing a network connection option to a user of the SMA controller 120. A user can select one of these options by using a touch screen. A determination can then be made as to what type of network connection option the installer has selected (step 710). This selection determines the appropriate workflow to assemble the network.

FIG. 13B illustrates a router connection check list display screen, and the router connection check list may be provided to a user after selecting a wireless network type (step 720). Figure 13B shows the correct connection of a WiFi enabled router that can be used in conjunction with the SMA controller 120 for network connection in text and images. The installer executing the SMA controller can use the touch screen to confirm that the steps depicted in the router connection check list have been executed.

Figure 13C depicts a display screen requesting input of a router MAC address associated with router 125 (step 723). As shown, the display may include an image showing where the launcher may locate the router MAC address and what the router MAC address looks like. The installer can then use the displayed touchpad to enter the router MAC address (step 723). Once the input is complete, the SMA controller 120 can store the router MAC address in an appropriate memory location (e.g., memory 260). Once the installer confirms the router MAC address input, the SMA controller can perform tasks related to the location of the corresponding router (eg, using the WiFi transceiver 235 or the broadband module 230 to ping the MAC bit with a ping command) The address is detected) (step 725). Alternatively, the SMA controller can scan the routers available in the home domain 110 using the WiFi transceiver 235 and the broadband module 230. The SMA controller can then display the MAC address of the available router selected by the initiator of the execution.

Figure 13D illustrates a display screen whose content is provided on the SMA controller touch screen display during a positioning and provisioning process of the router associated with the entered MAC address. The SMA controller 120 will attempt to communicate with the router 125 by using, for example, a WiFi transceiver 235 or a broadband connection module 230. Once the router is located, the SMA controller can be used, for example, the Home Network Management Protocol (HNAP) to communicate with the router to preserve the router. Preserving the router can take a variety of forms including, for example, providing a randomly generated password and initiating a WEP2 security agreement (step 727). A determination can then be made as to whether the router has been located and secured (step 730). If the router is not properly located and not secured, the process can return to the router connection check list 720 and again attempt to enter the MAC address and locate and maintain the router for the router. Alternatively, the router and the provider of the SMA controller can use the remote access to secure the router before installing the SMA controller or while installing the SMA controller.

If the router has been located and secured, the process can continue to establish and maintain a private network (e.g., a dedicated WiFi network) on the router (step 733). Likewise, the HNAP protocol can be used to provide commands that are transmitted to the router to establish and maintain the dedicated WiFi network in accordance with appropriate commands stored in the firmware of the SMA controller 120. It should be noted that this procedure of securing a dedicated WiFi network can be combined with the maintenance of the router.

Once the router 125 is secured and the dedicated WiFi network is established and secured, the SMA controller 120 can interpret the strength of the radio signals received by the WiFi transceiver 235 and the cellular transceiver 240 (step 735). The SMA controller can then display the WiFi and cellular signal strengths using a display that displays a graphical representation of the radio signal strength, such as that depicted in Figure 13E. The installer can then choose to move the SMA controller 120 to a different location within the home domain to optimize the displayed WiFi and cellular signal strengths.

The SMA controller can be provided for a particular cellular (e.g., GSM) network pre-configured by a provider of the SMA controller. When the SMA controller communicates with a server located in the operator's network (discussed below), any configuration updates, including those related to GSM provisioning, will be downloaded from the server to the SMA control. In the device. The SMA controller will provide signal strength information about the cellular network in which the SMA controller is installed and will use the cellular network as an available communication path.

Figure 13F depicts an image that can be displayed when the SMA controller 120 performs a connectivity test on the broadband/WiFi and cellular networks (step 737). In this connection test, the SMA controller 120 can communicate with a server located in the operator's domain 160 via the router 125 or a cellular network 150. One or more signals may be transmitted between the SMA controller and a server located in the operator's domain to confirm connection and connection quality.

Once the connection is established through the available networks and the connection is confirmed, the SMA controller 120 can communicate with an operator domain server (e.g., server 165) to determine if a firmware or configuration update is It can be used by the SMA controller (step 740). If there is no update, the workflow can proceed to the next startup phase (e.g., account setup 620) (step 747). If an update is available, the SMA controller can download and store the update from the server (step 743). After completing the download update, the SMA controller can execute a program to install the update (eg, firmware) and reboot (step 745). Once the update installation is complete, the startup process can proceed to the next stage (step 747).

Figure 7 also depicts a similar startup procedure for a selected home network as a power line network environment (e.g., a home power line network). A power line network adapter check list can be displayed on a touch screen coupled to the SMA controller 120 (step 750). The SMA controller may attempt to locate the power line network adapter (step 753) and if successful, may transmit an appropriate command to the power line network adapter to secure the power line network adapter (step 755) ). Such commands may include providing a randomly generated password and the like. A determination can then be made as to whether the power line network adapter is successfully located and secured (step 757), and if not successfully located and secured, the program can return to display the power line network adapter Check the list for another attempt.

If the power line network adapter is successfully located and secured, the SMA controller can determine the cellular signal strength by using the cellular transceiver 240 and then use a display similar to that shown in Figure 13E. The screen displays this signal strength (step 760). A connectivity test can then be performed for both the wideband/powerline network and the cellular network (step 763). As discussed above, this connection test can include transmitting a signal to a server located in the operator network 160 via an available communication mode.

Once the connection to the servers is established, the SMA controller can determine if a firmware or configuration update is available (step 765), and if not available, the workflow can proceed to the next startup phase (step 747). ). If an update is available, the SMA controller 120 can download and store the update (step 743) and install the update (step 745). Once the update installation is complete, the SMA controller can proceed to the next startup phase (step 747).

It should be noted that in the absence of an available broadband communication path to the remote server, the SMA controller can still determine connectivity via the provided cellular network. A set of workflows can make this determination and provide appropriate signal strength and connectivity testing.

FIG. 8 is a simplified flow diagram showing an example of an account setup workflow 620 in accordance with an embodiment of the present invention. Once a network is configured and a connection to the operator network of the SMA service provider is established, an initiator may be required to provide account information to the provider to make the SMA controller available for access. Software and services used by terminal subscribers.

As illustrated, after the network program 610 is completed, the process of Figure 8 is entered (step 810). An opportunity to enter a subscriber order number or other identity certificate for the terminal subscriber (step 820) is provided. FIG. 13G illustrates an example of an order number input display screen for coupling to a touch screen of the SMA controller 120. The installer can use the displayed touchpad to enter the customer order number, and the order number can be stored by the SMA controller in a local memory (eg, memory 260). Similarly, the installer is provided with an opportunity to enter the subscriber's phone number (step 830) and the subscriber's time zone (step 840), which may also be stored. Considering that different SMA service providers may require additional or different information to be provided to identify a subscriber, the SMA controller may be configured to request this information and be configured to store this information for transmission to the operator. Prepare a server in the domain. Once all of the required account information has been provided, the SMA controller 120 can communicate the identification information to a server located in the operator's domain 160 via the assembled network (step 850). In addition, the SMA controller can provide information identifying the SMA controller hardware (eg, serial number or other hardware identification) along with the network address information, identifying the SMA controller hardware information may be associated with the operator. This account information in the domain (eg, in database server 185) is associated.

Using this information, the SMA service provider can verify the field settings of the SMA controller. In addition, the provider can also track the hardware installed in the home domain for the purpose of understanding the installation inventory and future firmware updates for the SMA controller.

FIG. 9 is a simplified flow diagram showing a procedure for assembling a full sensor (eg, step 510) in accordance with an embodiment of the present invention in accordance with a sensor setup stage 630. As illustrated, this sensor assembly phase begins with account setup phase 620 (step 905). A user of a security system incorporating the SMA controller 120 (eg, an installation technician or an occupant of the home domain 110) may decide to maintain the home domain based on needs in the home network domain. The type and number of security sensors required. The SMA controller, via, for example, a touch screen input device, can display a boot command associated with the sensor assembly process (step 910). The boot commands may include, for example, text and/or visual instructions for placing a standard sensor associated with the SMA controller in a seek mode. The SMA controller can then provide an input display for the performer to enter how many sensors the SMA controller should search during the process (step 915). Figure 13H depicts an exemplary display screen for selecting the number of sensors that the installer would like to add to the system. The displayed display also provides a seek time that can be automatically adjusted for the number of sensors selected.

The SMA controller can then search for all of the sensors in the seek mode (step 920). In addition, the SMA controller can display the remaining seek time indication. A link message from a sensor can provide information including, for example, a unique identification number and sensor type information corresponding to the sensor. An SMA controller touch screen interface can then display zone information associated with each of the discovered sensors (step 925). FIG. 13I is a diagram showing an example of a detection zone display screen that can be provided by the SMA controller. Each sensor can then be paired (eg, by triggering the sensor) (step 930). The search and pairing process provides detailed information about each sensor to the SMA controller.

Once the information relating to all of the positioned sensors is displayed, a user can then edit the information to provide details about the physical location or zone of the sensor within the home domain and with the sensor Other characteristics related to the defense zone. The execution launcher can select a sensor zone to edit it (step 935) and then define or edit information related to the sensor (step 940). Information about the sensor and the zone can then be stored in a local memory (eg, memory 260) of the SMA controller 120. The SMA controller can also transmit sensor zone information via a broadband connection to store it in a server located in the operator's domain 160.

Figure 13J illustrates a display screen that may be provided by embodiments of the present invention to permit editing of sensor information (e.g., sensor zone information). As shown, the display can provide information such as the unique identifier of the sensor (serial number 1310) and the type of sensor (sensor type 1320). As indicated above, unique identifier and sensor type information is provided by the sensor during the search and location process. A user performing a launch procedure through a display (such as the one shown in Figure 13J) can define additional zone characteristics associated with the sensor. For example, a user can define or select a zone name 1330 to associate it with the sensor. For example, the user can enter the zone name by using a touch screen based keyboard or by selecting the zone name from a list of common names displayed on the touch screen.

A zone function 1340 can also be provided to associate it with the sensor. A zone function determines the performance of the zone and depends on the type of zone. For example, a door/window sensor can function as an in/out zone or as a perimeter zone. Each zone type can have one or more zones that can be combined. For example, a motion detector may have a zone function of the indoor tracker, a smoke/heat detector may have a zone function for 24-hour fire monitoring, and a glass break detector may have a zone function of a perimeter zone, and The inertial detector can have an in/out zone function or a perimeter zone function.

The choice of a zone function definition can cause the security system to function and change the response to signals received from a sensor located in the zone. In accordance with an embodiment of the present invention, the following tables illustrate examples of zone functions and their associated action/reaction definitions.

By defining such zones, a user can control how the security functions of the SMA controller 120 react to various sensor triggers.

A user may also be associated with a display icon 1350 associated with the sensor zone. In many cases, the available icons will be limited to one type of icon whose graphics are related to the sensor type. However, for example, for a door/window sensor, an icon depicting a door or a window may be used. FIG. 13J further illustrates a signal strength button 1360 that, when the signal strength button 1360 is selected, can display the signal strength between the wireless hub positioned within the SMA controller 120 and the associated sensor. Alternatively, the signal strength can be displayed on the display of Figure 13J.

The sensor zone information input by using a display screen such as that shown in FIG. 13J can be stored in a local data table stored in the memory 260 of the SMA controller 120. In addition, sensor zone information may also be transmitted via the pick-up domain 150 to a server (eg, database server 185) located in the operator's domain 160 for storage. The information can be accessed by a user of an portal server 170 (e.g., to monitor sensor events) by storing sensor zone information in a server located in the operator's domain. Storing the grouping information in the operator domain may allow the remote to access the grouping information (eg, using an portal server server 170) and provide a replacement SMA controller when the original SMA controller experiences an event that is unavailable .

A user executing the activation/assembly procedure of the SMA controller can be given an opportunity to edit each of the discovered sensor zones (step 945). Once the user has completed the process of editing the sensor zone, the user is provided with an opportunity to add a keychain device (step 950). If the user chooses to add the keychain type device, the pairing command for the keychain can be displayed (step 955). Once the keychain device enters a search mode, the execution initiator can instruct the SMA controller to search for the keychain device (step 960). Once the keychain device is found, the user can edit the keychain information in a manner similar to editing the zone information (step 965). Information such as those associated with a particular keychain and similar information may be provided. Once a key chained device is added or a keychain is avoided, the launcher can proceed to the next stage (step 970). Similarly, information related to the added keychain can be transmitted by the SMA controller to the operator network for storage and monitoring.

Figure 10 is a simplified flow diagram showing a procedure for adding a camera or other monitoring device during startup of an SMA controller. Figure 10 depicts details relating to process step 640 of Figure 6. Although FIG. 10 and the accompanying description refer to a camera type monitoring device, it should be understood that other types of monitoring devices that are radio frequency coupled to the SMA controller can also be incorporated into the following discussion.

The program illustrated in FIG. 10 may be added after performing the procedure associated with step 630 (step 1005). The SMA controller 120 can display a general command associated with activating and installing a camera monitoring device on an associated touch screen display (step 1010). An opportunity to perform the launch procedure may then be provided to indicate whether one or more camera monitoring devices will be installed (step 1015). If the camera is not installed, the program can proceed to the next stage of the startup workflow (step 1075). If the user indicates that a camera is to be installed, the SMA controller can make a determination as to whether the assembled network supports a camera monitoring device (step 1020). For example, if the network being deployed does not support a WiFi connection but the designated camera monitoring device requires a WiFi network, the installation procedure of a camera monitoring device cannot continue. In this case, the SMA controller can display a message indicating lack of network support for the camera monitoring device (step 1025) and then the program can proceed to the next stage of the startup workflow (step 1075). Although in general the camera monitoring device installation workflow will not begin if the previously assembled network (eg, a power line network) does not support a camera monitoring device.

If the initiator is to install a camera and the network is configured to support a camera, the SMA controller can be configured to prepare for communication with the SMA controller's secure WiFi network. The camera monitors the instructions of the device (step 1030). For example, in order for the SMA controller to provide appropriate instructions for assembling the camera, an initial assembly of a wireless camera may require an initial wired connection to the router 125. Thus, the instructions displayed by the SMA controller can include how to couple the camera monitoring device to the router to complete the text and images of the process stages.

The SMA controller can also provide an opportunity for the user performing the launch procedure to indicate when the camera monitoring device is coupled to the router or ready for assembly. The SMA controller can then communicate with the router (e.g., using HNAP) to locate the camera and receive a MAC address of the camera from the router (step 1035).

FIG. 13K illustrates a display screen that can be provided on a touch screen of the SMA controller 120 when the camera monitoring device positioning program is executed and the found MAC address is displayed. As illustrated in Figure 13K, the SMA controller can give the initiator the opportunity to receive a found MAC address or perform a retry operation to search for another suitable MAC address (step 1040). Once confirmed, the SMA controller can then assemble the camera monitoring device to wirelessly communicate with the router using the secure WiFi network to wirelessly communicate the router with the SMA controller (step 1045). The SMA controller can use the display screen of Fig. 13K to explicitly notify the photographic unit of the process.

Once the camera assembly program is executed, the SMA controller can display additional instructions associated with reconfiguring the camera monitoring device hardware for wireless communication via the secured WiFi (step 1050). Figure 13L depicts an example of a display screen providing such instructions. In the illustrated example, the initiator executing the initiator is instructed to restart power to the camera monitoring device and disconnect the Ethernet cable connecting the camera to the router. When the camera is powered back on, the camera will obtain an IP address from the router via a secure secured WiFi network.

During the assembly process, the SMA controller can transmit various information to the camera, including, for example, a management user name and password, a camera name, a camera description, a time zone, a current time, a language, and permission to access the camera. User list name and password for the user list, network settings such as IP address and name server, protocol settings, motion detection settings, and desired camera image settings such as resolution and video adjustment. In addition, the camera can provide information, such as, for example, device type, manufacturer, model, and other control information to the SMA controller for storage. All of this information can be communicated between the SMA controller and the camera monitoring device without the need to interact with the user outside of the initial assembly process of the camera hardware.

Once the SMA controller and camera are assembled to communicate with each other, images produced by the camera can be displayed on a display device associated with the SMA controller. The process illustrated in FIG. 10 provides a test image that is received from the camera via the secure WiFi network (step 1055) and displayed on a display device coupled to the SMA controller (step 1060). . The SMA controller can then give the user executing the activation program an opportunity to acknowledge receipt of the image (step 1065). If no image is displayed, the process can return to the initial assembly command of the camera monitoring device (step 1030). ). If the image is successfully received and confirmed, the opportunity to match the next camera monitoring device can be given (step 1070). If the user chooses not to assemble the next camera monitoring device, then the flow can proceed to the next stage of the startup workflow (step 1075).

11 is a simplified flow diagram showing an exemplary flow for an alarm path communication test 650. As discussed above, the procedure of Figure 11 is performed after assembling the SMA controller network and various alarm sensors. The program illustrated in FIG. 11 can be used to confirm the communication path between the SMA controller 120 and the central station 190. The general communication path with the central station and the receipt and interpretation of events associated with a particular sensor coupled to the SMA controller can be tested.

As illustrated in Figure 11, the program for the alert path communication test can be added after the network is assembled (step 1105). To confirm that there is a communication path to an appropriate central monitoring station, the SMA controller can transmit a signal to the central station (step 1110). Figure 13M illustrates an example of a test alert display screen that can be displayed on a touch screen associated with the SMA controller 120 to begin an alert test procedure. As shown, a test button is displayed and the test button should be pressed to begin the alarm test sequence. FIG. 13N illustrates an exemplary display screen that can be used to prompt a user to execute a startup program to transmit a test signal. A central station will receive a message (eg, "Contact ID 601-Manual Trigger Test Report") and will not give the user the opportunity to bypass this screen until it is operational. An alert server (e.g., server 165) in the domain 160 receives a confirmation message.

Upon receipt of the confirmation message, the SMA controller can display the command to the user executing the activation program to contact the appropriate central station to acknowledge the alarm signal transmission (step 1115). Such instructions may include, for example, a central station's telephone number, which may be provided by a server located in the operator's domain after completion of the initial account setup step 620. The SMA controller can give the user executing the launching program an opportunity to enter a verification of successful communication with the central station (step 1120). In an alternate embodiment, the SMA controller can be configured to receive an automatic confirmation of communication with the central station from the central station 190 or from an operator domain server 165. The SMA controller can then display information about the automatic confirmation to a user executing the activation program on a display coupled thereto.

Once the communication path to communicate with the central station is confirmed, the SMA controller can display a checklist for testing each of the configured zones of the system (step 1125). Figure 13O illustrates an example of this alert test checklist, which may be displayed in accordance with an embodiment of the present invention. As illustrated, the checklist provides the user with an opportunity to alert the system to the test mode (step 1130). Upon entering the alert mode, the SMA controller performs an exit delay sequence (step 1135) during which a trigger is triggered if the alert is reset from a triggered state. An alarm signal is transmitted to the central station. The check list is then provided to the user executing the launch program to trigger an alert sensor, which will then transmit an alert signal to the SMA controller (step 1140).

When the alarm sensor is triggered, the SMA controller can display information related to the alarm trigger (step 1145). Figure 13P depicts an example of an alarm test display screen that may be provided by embodiments of the present invention. Each triggered zone is shown in the alarm test zone display. When the user triggers all desired alerts, the user can enter to proceed to the next step. The SMA controller can then determine if each of the configured zones has been tested (step 1150), and if not, the SMA controller can request confirmation from the user to not test the untested zones (steps) 1155). If the user wants to test an additional zone, the SMA controller can provide an opportunity to trigger an additional alert (step 1140).

If each zone has been tested or each desired zone has been tested, the SMA controller can display viewing information regarding various triggered alarms (step 1165). FIG. 13Q illustrates an example of a view alarm display screen that may be provided by an SMA controller in accordance with an embodiment of the present invention. In addition, instructions for contacting the central station to confirm that various alert messages have been received may also be displayed (step 1170). The user executing the launcher can confirm to the central station representative that all alarm information was correctly received through the alarm view list. Once this alert view program is completed, the program can proceed to the next stage of the assembly workflow (step 1175).

In an alternate embodiment, the SMA controller can be configured to receive an automatic confirmation of transmission of the alert information from the central station or from an operator domain server 165 to the central station 190. The SMA controller can then display information about the automatic confirmation to a user executing the activation program on a display coupled thereto. Such an alert information confirmation automation program reduces the time required to execute the installer and test the SMA controller settings.

Figure 12 is a simplified flow diagram showing a procedure for post-launch workflow 660. The program illustrated in Figure 12 provides the assembly steps that are performed without any other portion of the general workflow being performed, and the steps to complete the preservation of the SMA controller.

As depicted, the workflow of FIG. 12 enters after the alarm path communication test sequence 650 is completed (step 1210). The user executing the launch program can be given an opportunity to enter a master code of the SMA controller 120 (step 1220). Figure 13R depicts an exemplary display screen that can be provided by the SMA controller to set the master code. As shown, a keypad can be provided on the touch screen display and the user can enter a four digit number. The SMA controller then stores the master code for later use. Additionally, the user may be given an opportunity to enter an alarm event entry and exit delay time (step 1230). As discussed above, the entry and exit delay time and the SMA controller will wait after an alarm sensor is triggered to transmit an alarm event to a central station and an alarm located in the home domain 110 is alerted. How long is it relevant. A preset value of the entry and exit delay can be displayed and an adjustment button can be provided by which the user can adjust the delay time according to their preference. These ingress and egress delays can then be stored on the SMA controller for use in operation.

In an alternate embodiment, steps 1210-1230 may be avoided by specifying a preset value for the primary code, delay time, and the like during execution of the installation process. The end user can then set this value later by using an interface provided on a display coupled to the SMA controller. Using presets reduces the time required to install the SMA controller in the home domain.

The SMA controller can then be configured to provide any additional information that a provider of the operator's domain 160 would like to obtain from a subscriber (step 1240). The SMA controller provider can modify these process steps as needed or necessary. It is contemplated that any additional instructions provided to the user executing the launch program may be provided on a display associated with the SMA controller (step 1250) and then the system may be restarted in accordance with all settings provided during the startup workflow to initiate The SMA controller (step 1260).

The software architecture provided for the above startup/supply workflow can be tailored to the needs of the SMA service provider. Embodiments of the firmware architecture that provides a startup/supply workflow can be implemented, for example, using an XML-type control file that defines each step of the workflow and a display accompanying the steps of the workflow.

The boot/supply workflow described above is designed to be performed entirely using the SMA controller 120 without using any touch screen display associated with the SMA controller and any updates provided by a remote server. External computing resources or input devices. The displayed commands and input screens are combined with the SMA controller software (eg, firmware) so that a non-technical end user or an installation technician who is not professionally trained can perform the SMA controller along with the associated security sensor. Installation procedures for camera monitoring devices and network routing devices. In addition, since most of the network composition is automatically performed by the SMA controller, the number of times the address and other information are typed in, and the chance of error in the typing process is significantly reduced. Since the installation procedure is performed using only one display coupled to the SMA controller, there is no need for additional equipment such as a computer to execute the installation program, and the cost of executing the installation program is also reduced. Moreover, the serialization process used to execute the installer, combined with the omission of long-time typing of addresses and the like, results in faster setup and reduced installation interruptions compared to typical systems. Therefore, if a technician performs such an installation procedure, the cost per installation is reduced by the reduction in installation time required by the technician. It will be understood by those skilled in the art that all of these factors provide advantages over conventional systems for implementing the system of the present invention, as conventional systems require additional equipment to perform the installation process and require training of professional technicians to increase The cost of performing such an installer.

An exemplary computing and network environment

As indicated above, the present invention can be implemented using a variety of computer systems and networks. An example of such a computing and network environment is described below with reference to Figures 14 and 15.

Figure 14 depicts a block diagram of a computer system 1410 suitable for implementing aspects of the present invention (e.g., server 165, portal server 170, backup server 175, telephone server 180, and database server 185). Computer system 1410 includes a bus 1412 interconnecting the main subsystems of computer system 1410, such as a central processing unit 1414, a system memory 1417 (typically RAM, but may also include ROM, fast Flash RAM or the like), an input/output controller 1418, an external audio device (such as a speaker system 1420 via an audio output interface 1422), an external device (such as a display screen 1424 via display adapter 1426) ), a serial port 1428 and 1430, a keyboard 1432 (forming a interface with a keyboard controller 1433), a storage interface 1434, a floppy disk drive 1437 operable to receive a floppy disk 1438, operable to interface with a Fibre Channel network A host bus adapter (HBA) interface card 1435A connected to the road 1490, a host bus adapter (HBA) interface card 1435B operatively coupled to a SCSI bus 1439, and operable to receive a disc 1442 A CD player 1440. Also included is a mouse 1446 (or other pointing device coupled to the busbar 1412 via the serial port 1428), a modem 1447 (coupled to the busbar 1412 via the serial port 1430), and a network interface 1448 (directly coupled) To bus 1412).

Bus 1412 allows data to be communicated between central processor 1414 and system memory 1417. Memory 1417 may include read only memory (ROM) or flash memory (both of which are not shown) and random. Access memory (RAM) (not shown), as previously indicated. RAM is usually the main memory loaded by the operating system and applications. In addition to other code, the ROM or flash memory can include a basic input-output system (BIOS) that controls basic hardware operations, such as interactions with peripheral components. Applications residing in computer system 1410 are typically stored on a computer readable medium or other storage medium such as a hard disk drive (e.g., fixed disk 1044), a compact disk drive (e.g., optical disk drive 1440), floppy disk drive 1437. And accessed via a computer readable medium or other storage medium. In addition, when accessed via network modem 1447 or interface 1448, the application may be in the form of an electronic signal modulated in accordance with the application and data communication techniques.

The storage interface 1434, like other storage interfaces of the computer system 1410, can be coupled to a standard computer readable medium, such as a fixed disk drive 1444, for storing and/or capturing information. The fixed disk drive 1444 can be part of the computer system 1410 or can be a separate interface system or accessed through other interface systems. The modem 1447 can provide a direct connection to a remote server via a telephone link or a direct connection to the Internet via an Internet Service Provider (ISP). The network interface 1448 can provide a direct connection to the remote server via a direct network link or a direct connection to the Internet via a POP (network connection point). The network interface 1448 can provide this connection using wireless technology, including digital cellular connections, cellular digital packet data (CDPD) connections, digital satellite data connections, or the like.

Many other devices or subsystems (not shown) may be connected in a similar manner (eg, a document scanner, digital camera, etc.). Conversely, the invention may be practiced without all of the devices shown in FIG. The devices and subsystems may be interconnected in a different manner than that shown in FIG. The operation of a computer system such as that shown in Figure 14 is well known to those skilled in the art and will not be discussed in detail in this application. The code for implementing the present invention can be stored in a computer readable storage medium, such as one or more of system memory 1417, fixed disk 1444, optical disk 1442, or floppy disk 1438. The operating system provided by the computer system 1410 can be MS-DOS. , MS-WINDOWS , OS/2 UNIX Linux Or another known operating system.

Moreover, with respect to the signals described herein, those skilled in the art will recognize that a signal can be transmitted directly from a first block to a second block, or a signal can be modified between the blocks (eg, Amplify, attenuate, delay, latch, buffer, invert, filter, or otherwise modify). Although the signal of the above embodiment is characterized by being 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 information and/or functional level of the signal is in the block. Transfer between. To some extent, a signal input at a second block can be conceptualized as being derived from a first block due to the physical limitations of the circuitry involved (eg, there will inevitably be some attenuation and delay). The first signal outputs a second signal derived. Thus, as used herein, a second signal derived from a first signal includes the first, whether due to circuit limitations or through other circuit elements that do not change the information and/or final functional level of the first signal. A signal or any modification to the first signal.

15 is a block diagram depicting a network architecture 1500 in which client systems 1510, 1520, and 1530 and storage servers 1540A and 1540B (which may be implemented using computer system 1510) are coupled to a network 1550. . Storage server 1540A is further depicted as directly attached storage devices 1560A(1)-(N), and storage server 1540B is depicted as directly attached storage devices 1560B(1)-(N). Storage servers 1540A and 1540B are also coupled to a SAN fabric 1570, although the operation of the present invention does not require a connection to a storage area network. The SAN fabric 1570 supports access to the storage devices 1580(1)-(N) by the storage servers 1540A and 1540B, and also supports the storage device 1580 via the network 1550 via the client systems 1510, 1520, and 1530 ( 1) - (N) access. Smart storage array 1590 is also shown as an example of a particular storage device accessible via SAN fabric 1570.

Referring to computer system 1410, data machine 1447, network interface 1448, or some other method may be used to provide a connection from each of client computer systems 1510, 1520, and 1530 to network 1550. Client systems 1510, 1520, and 1530, for example, a web browser or other client software (not shown), can access information stored on storage server 1540A or 1540B. This client allows client systems 1510, 1520, and 1530 to be accessed by storage server 1540A or 1540B or storage devices 1560A(1)-(N), 1560B(1)-(N), 1580(1)-(N) One of them or the smart storage array 1590 managed data. Figure 15 depicts the use of a network such as the Internet for exchanging data, but the invention is not limited to the Internet or any particular network based environment.

Other embodiments

The invention is preferably adapted to achieve such advantages as mentioned and other advantages inherent therein. While the invention has been illustrated and described with reference to the specific embodiments of the invention Modifications, adaptations, and equivalent substitutions will be made to the invention in form and function. The embodiments depicted and described are merely exemplary and are not intended to cover the scope of the invention.

Embodiments including components included within other components (e.g., various components shown as components of computer system 1410) are described above. Such an architecture is merely an example, and in fact, many other architectures that implement the same functionality can be implemented. In an abstract but still clear sense, any configuration of components used to implement the same functionality is effectively "associated" to enable the desired functionality. Therefore, any two components herein combined to achieve a particular function can be seen as "associated" with each other to enable the desired functionality to be implemented. Likewise, any two components that are so related may also be considered "operably connected" or "operably coupled" to each other to perform the desired function.

The above detailed description refers to various embodiments of the present invention by using block diagrams, flowcharts, and examples. It will be understood by those skilled in the art that each block diagram component, flowchart step, operation, and/or component illustrated by the use of the example can be separately and/or widely available from a wide range of hardware, software, firmware, or any combination thereof. Implement together. For example, a particular electronic component can be utilized in a particular application integrated circuit or similar circuit or associated circuitry for performing the functions associated with one or more of the described functional blocks.

The present invention has been described in the context of a full-featured computer system; however, it will be appreciated by those skilled in the art that the present invention can be propagated in various forms as a program product, and the present invention is equally applicable without regard to actual use. A particular type of computer readable medium that performs the propagation. Examples of computer readable media include computer readable storage media and media storage and distribution systems that will be developed in the future.

The embodiments discussed above may be implemented by a software module that performs one or more tasks associated with the embodiments. The software modules discussed herein may include scripts, batch files, or other executable files. The software modules can be stored on a machine readable or computer readable storage medium such as a floppy disk, a hard disk, a semiconductor memory (eg, RAM, ROM, and flash media), a compact disk (eg, a CD-ROM) , CD-R and DVD) or other types of memory modules. In accordance with an embodiment of the invention, a storage device for storing a firmware or hardware module can further include a semiconductor-based memory that can be permanently, removably or remotely coupled to a Microprocessor/memory system. Therefore, the modules can be stored in a computer system memory to assemble the computer system to perform module functions. Other new types and types of computer readable storage media may be used to store the modules discussed herein.

The above description is intended to illustrate the invention and should not be considered as limiting. Other embodiments that are within the scope of the invention are also possible. Those skilled in the art will readily implement the steps necessary to provide the structures and methods disclosed herein, and it will be understood that the process parameters and the order of execution of the steps are given by way of example only and can be varied to obtain the desired structure and Modifications are made within the scope of the invention. Variations and modifications of the embodiments disclosed herein may be made based on the descriptions herein, without departing from the scope of the invention.

Accordingly, the invention is intended to be limited only by the scope of the appended claims.

110. . . Home domain

120. . . SMA controller / SMA gateway

125. . . Network router/router

127. . . Home computer

130. . . RF or wireless sensor / RF sensor / home security device

135. . . Old security system / home security device

140. . . Monitoring device

145. . . Home automation device / automation device

150. . . Access domain

152. . . Wide area network

154. . . Honeycomb network

160. . . Operator domain

165. . . server

170. . . Portal server

175. . . Backup server

180. . . Telephone server

185. . . Database server

190. . . Central station

210. . . processor

220. . . Touch screen interface / touch screen

225. . . Audio processor

230. . . Broadband connection / broadband module / broadband connection module

235. . . WiFi transceiver

240. . . Honeycomb transceiver

250. . . SPI bus / SPI / SPI interface

255. . . Universal Serial Bus (USB) Interface / USB Interface

260. . . Memory

265. . . Security digital interface / SD interface

270. . . power supply

310. . . Micro-core operating system

320. . . Core layer

330. . . Drive layer

340. . . Management

350. . . Keypad user interface layer

360. . . Interface tool set engine layer

370. . . Interface tool set

410. . . Set of interface toolset icons

420. . . Header

425. . . Arm/Disarm button

430. . . Footnote

510 ~ 560, 610 ~ 660, 705 ~ 747, 810 ~ 860, 905 ~ 970, 1005 ~ 1075, 1105 ~ 1175, 1210 ~ 1260. . . step

610. . . Network settings / network program

620. . . Account Setup Steps / Account Settings / Account Settings Workflow / Initial Account Setup Steps

630. . . Sensor setup phase

640. . . Process step

650. . . Alarm path communication test/alarm path communication test sequence

660. . . Post-start workflow

1310. . . Unique identifier (serial number)

1320. . . Sensor type

1330. . . Zone name

1340. . . Zone function

1350. . . Display icon

1410. . . computer system

1412. . . Busbar

1414. . . CPU

1417. . . System memory

1418. . . Input/output controller

1420. . . Speaker system

1422. . . Audio output interface

1424. . . Display screen

1426. . . Display adapter

1428, 1430. . . Tandem

1432. . . keyboard

1433. . . Keyboard controller

1434. . . Storage interface

1435A, 1435B. . . Host Bus Adapter (HBA) interface card

1437. . . Floppy disk player

1438‧‧‧ floppy

1439‧‧‧SCSI busbar

1440‧‧‧CD player

1442‧‧‧DVD

1444‧‧‧Fixed Disk

1446‧‧‧ Mouse

1447‧‧‧Data machine

1448‧‧‧Web Interface/Interface

1490‧‧‧Fibre Channel Network

1500‧‧‧Network Architecture

1510~1530‧‧‧Client System/Client Computer System

1540A~B‧‧‧ Storage Server

1550‧‧‧Network

1560A(1)~(N), 1560B(1)~(N), 1580(1)~(N)‧‧‧ Storage devices

1570‧‧‧SAN structure

1590‧‧‧Smart Storage Array

1 is a simplified block diagram showing an architecture including a set of logical domains and functional entities in which embodiments of the present invention interact.

FIG. 2 is a simplified block diagram showing a hardware architecture of an SMA controller in accordance with an embodiment of the invention.

Figure 3 is a simplified block diagram showing a logical stack of the firmware architecture of an SMA controller that can be used with embodiments of the present invention.

FIG. 4 illustrates an exemplary user interface of an SMA controller 120 in accordance with an embodiment of the present invention.

Figure 5 is a simplified flow diagram illustrating the steps performed in the assembly process of an SMA controller in accordance with an embodiment of the present invention.

Figure 6 is a simplified flow diagram showing an example of a general workflow for activating and providing an SMA controller in accordance with an embodiment of the present invention.

Figure 7 is a simplified flow diagram showing an embodiment of a flow of network settings that may be used in embodiments of the present invention.

Figure 8 is a simplified flow diagram showing an example of an account setup workflow that may be used by embodiments of the present invention.

Figure 9 is a simplified flow diagram showing a procedure for assembling a security sensor that can be used in embodiments of the present invention.

Figure 10 is a simplified flow diagram showing a procedure for adding a camera or other monitoring device during startup of an SMA controller that can be used in embodiments of the present invention.

Figure 11 is a simplified flow diagram showing an exemplary flow for an alarm path communication test that can be used in embodiments of the present invention.

Figure 12 is a simplified flow diagram showing a procedure for a post-launch workflow that can be used in embodiments of the present invention.

13A-R illustrate an example of a display provided by an SMA controller in accordance with an embodiment of the present invention.

Figure 14 is a block diagram of a computer system suitable for implementing the aspects of the present invention.

Figure 15 is a simplified block diagram of a network environment suitable for implementing aspects of the present invention.

110. . . Home domain

120. . . SMA controller

125. . . Network router

127. . . Home computer

130. . . RF or wireless sensor

135. . . Old security system

140. . . Monitoring device

145. . . Home automation device

150. . . Access domain

152. . . Wide area network

154. . . Honeycomb network

160. . . Operator domain

165. . . server

170. . . Portal server

175. . . Backup server

180. . . Telephone server

185. . . Database server

190. . . Central station

Claims (10)

A computer implementation method for assembling a security, monitoring and automation (SMA) system, the method comprising the steps of: assembling a network in a network domain including an SMA controller, wherein the grouping step uses the Executing by the SMA controller; assembling one or more of a full sensor, a monitoring device, and a home area network device having an automated interface to communicate with the SMA controller, wherein the step of assembling Performing using the SMA controller; assembling one or more zones, wherein each zone is associated with a security sensor of the one or more security sensors and causing a response of the SMA controller Linking to the one or more zones; and testing a communication path between the SMA controller and a remote server. The method of claim 1, further comprising the step of: executing, by the SMA controller, a script, wherein the script passes the step of configuring the network, the group is provided with a full sensor, a monitoring device And a step of the one or more of the home area network devices and the step of testing the alarm communication path to direct a user of the SMA controller, the step of executing the script being coupled to the SMA control A series of user interfaces are displayed on a display of the device. The method of claim 1, further comprising the step of assembling one or more zones, wherein each zone and the one zone Or associating a security sensor in one or more security sensors; and testing an alarm communication path, wherein the alarm communication path includes: a security sensor between the one or more security sensors a link between the SMA controller, a network link between the SMA controller and the remote server, and a network between the remote server and an alarm central station Road link. The method of claim 3, wherein the step of configuring the one or more security sensors to communicate with the SMA controller comprises the step of: searching for the one by the SMA controller Or each of the one or more security sensors; displaying, on a display coupled to the SMA controller, a security sensor corresponding to each of the one or more security sensors Information; and pairing each found sensor. An apparatus for use as a system controller, comprising: one or more communication interfaces, each for one or more of a security sensor, a monitoring device, and a home area network device having an automated interface Communicating; a network communication interface for communicating with the network router located in a network domain including the device and a network router; a processor coupled to the one or more communication interfaces and networks a communication interface and a memory, and configured to execute instructions stored in the memory; and the memory stored instructions are configured to provide a workflow for launching the device, wherein the workflow includes: Using the network communication interface to configure a network in the network domain, wherein the assembling step is performed by the device communicating with the network router, and the security sensors, the monitoring devices, and the monitoring device are assembled One or more of the home area network devices having an automated interface for communicating with the device using an individual communication interface and for assembling one or more zones, wherein each zone Associated with a security sensor in one or more security sensors, the group comprising one or more zones comprising a response to the device being coupled to the one or more zones; and using the network communication interface A communication path between the device and a remote server is tested. The apparatus of claim 5, wherein the instructions that are configured to provide the workflow include instructions for executing a script, wherein the script passes the step of configuring the network, the combination And the step of testing the one or more of the security sensors, the monitoring device, and the home area network device and the step of testing the alarm communication path to guide a user of the device; and the device further includes a a display coupled to the processor, And being configured to display a series of user interfaces in response to the step of executing the script. The apparatus of claim 5, wherein the instructions that are configured to provide the workflow include instructions for assembling one or more zones, wherein each zone and the one or more zones A security sensor in the security sensor is associated with the network communication interface to test an alarm communication path, wherein the alarm communication path includes: a security in the one or more security sensors a link between the sensor and the device, a network link between the device and the network server, and a network between the network server and a remote server A link, and a link between the remote server and an alarm central station. The device of claim 7, further comprising: a display coupled to the processor; and wherein the one or more security sensors are configured to communicate with the device The workflow of the steps further includes searching for each of the one or more security sensors, displaying on the display a security sensor that has been found with each of the one or more security sensors Corresponding information and pairing each found sensor. The apparatus of claim 7, wherein the workflow for the step of assembling the one or more zones further comprises: Selecting one of the one or more zones; and editing the information associated with the selected zone. The apparatus of claim 5, wherein the workflow for the step of assembling the network in the domain further comprises: locating the network router; preserving the network router; and establishing a A security network, wherein the security network includes the device and the network router, and the step of maintaining the network router and establishing the security network is performed in response to a command transmitted from the device to the network router.