Method and process for configuring a premises for monitoring

- Vivint, Inc.

A system and method for configuring an integrated information system through a common user interface are provided. A user accesses a graphical user interface and selects client, premises, location, monitoring device, and processing rule information. The graphical user interface transmits the user selection to a processing server, which configures one or more monitoring devices according to the user selections.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCES TO RELATED APPLICATION(S)

Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 7,016,813. The present application is a continuation reissue application and claims the benefit of application number 12/053,503, filed Mar. 21, 2008, now RE43,598, issued Aug. 21, 2012, both of which are broadening reissues of U.S. Pat. No. 7,016,813.

This application U.S. Pat. No. 7,016,813 is a divisional of U.S. patent application Ser. No. 09/967,485, filed Sep. 28, 2001, now U.S. Pat. No. 6,748,343, which claims the benefit of U.S. Provisional Application No. 60/236,282, filed Sep. 28, 2000, entitled SYSTEM AND METHOD FOR IMPLEMENTING AN INTEGRATED INFORMATION SYSTEM, and U.S. Provisional Application No. 60/281,256, filed Apr. 3, 2001, entitled METHOD AND PROCESS FOR CONFIGURING A PREMISES FOR MONITORING, which are hereby incorporated by reference.

FIELD OF THE INVENTION

In general, the present invention relates to electronic hardware and computer software, and in particular, to a method and process for configuring a premises for the installation of monitoring devices.

BACKGROUND OF THE INVENTION

Generally described, electronic security systems are configured to provide a wide range of security services in both residential and commercial settings. The types of monitoring devices utilized by a particular security system to perform the system service depend greatly on the sophistication of the security system configuration and the overall function of the security system. A majority of conventional security systems include intrusion detecting devices, such as door or window contacts, glass break detectors, motion detectors and the like. In a commercial setting, closed-circuit television (“CCTV”), badging systems, asset tracking, and access control devices and sensors are also utilized.

The configuration of the security system is based on the function the system will serve. For example, in one aspect, a typical electronic security system may be used to provide smoke, fire, and/or carbon monoxide detection. Accordingly, the system would utilize one or more smoke, fire and/or carbon monoxide detectors within one or more locations on the premises. In another aspect, the security system may also be utilized to provide motion or access detection as well as general video and audio monitoring of the premises. Accordingly, the system would utilize ingress or egress sensors and/or video cameras within the premises.

While the conventional art generally discloses utilizing multiple monitoring devices to perform various functions, conventional systems are deficient in data management functionality and integration. Security data from different monitoring device types is generally not integrated to affect the system reporting and control. Instead, the conventional security system is built around independent stand-alone devices that require human control and interpretation.

In one security configuration, contract or in-house security guard and patrol services are employed in a range of industrial commercial, public and private settings. The primary functions of the security guard may include direct visual surveillance, the monitoring of security cameras or other security devices, a reception or access control and authorization function, and incident response. A security guard may also be used to monitor a number of CCTV screens arranged in a bank formation. Accordingly, the security guard accepts the variety of inputs and makes a determination of a security alert, such as an unauthorized entrance.

The use of dedicated monitoring services, such as security guards, is generally prohibitively expensive and unavailable for a majority of individuals and businesses. Additionally, if the guard is distracted, absent or inattentive, a security event may go unreported. Furthermore, the monitoring device data, such as the CCTV data, is typically available only to the dedicated premises monitor and cannot be utilized concurrently by additional users, such as a remote monitor, a quality control supervisor, the owner of the premises, or emergency or public safety authorities. Moreover, a single security guard may not be capable of processing all of the possible monitoring data sources simultaneously, thereby reducing the effectiveness of multiple monitoring devices.

Another security system configuration utilizes external monitors to provide the security services. Generally described, external monitoring systems are more cost effective than a dedicated on-premises monitor. However, most external monitoring systems have a limited effectiveness in being unable to extensively provide and/or review detailed security information. For example, most conventional external monitoring systems cannot incur the expense of providing a sufficient amount of communication bandwidth to transmit continuous video/audio feeds from every monitored premises. Accordingly, if the external monitoring service detects an unauthorized entry into a premises, such as through a signal from a detecting device, the monitoring service typically dispatches emergency or public safety authorities to investigate and determine the extent of the detected event. In a vast majority of cases, the alarm is false and the premises owner incurs a fine for having the authorities verify the incident. Additionally, in the event of an actual emergency, the monitoring service cannot provide the public safety authorities with sufficient information to assess the situation with monitoring devices, thereby putting the authorities at greater risk.

Similar to the dedicated on-premises monitoring, the remote monitoring service also cannot concurrently process the device information to multiple authorized users for various purposes. For example, a premises owner may need to access video data to locate a pet within the premises, while emergency or public safety personnel would need to access the same video data to identify the location of a victim. In both cases, the monitoring service likely cannot provide the information to the user on a wide scale basis.

Some conventional security system configurations attempt to integrate at least some security monitoring devices to better detect alarm conditions from a remote user. For example, a security system monitor (either remote or on-premises) may detect an unauthorized entry from a motion detector and confirm it by utilizing a video camera. Generally, however, these systems are directed towards a combination of video surveillance and are limited into being processed solely for the detection of an intrusion or the verification of an intrusion. These systems generally cannot accept additional non-security information inputs that relate generally to the management of the premises and that are outside of the scope of conventional security monitoring. Moreover, these systems are deficient in that the data cannot be processed concurrently or distributed to multiple authorized users. Additionally, the monitoring devices used for these functions are often produced by different manufacturers and employ manufacturer-specific communications protocols. The monitoring devices are typically not configured to be accessible through a common access point for reporting and control. Accordingly, most of the monitoring devices are installed within a premises as independent sub-systems of a security system. The configuration of each of these systems, and often of each of the devices within a system, requires a separate configuration and installation process.

In addition to the lack of integration, the sub-systems generally have minimal operability as such, and any updates or modifications to the system typically require the removal and replacement of a wiring panel connected to the monitoring device. Accordingly, the costs associated with cumbersome installations and modifications are formidable. Security end-users desiring a system upgrade or modification are generally faced with the cost of removing an old system so that a change can be made. The replacement cost is further scaled for enterprise type monitoring systems that could require an update of a large number of monitoring devices.

Thus, there is a need for a system and method for communicating configuration and installation information to a diversified group of monitoring devices through a common access point of an integrated information system.

SUMMARY OF THE INVENTION

A system and method for configuring an integrated information system through a common user interface are provided. A user accesses a graphical user interface and selects client, premises, location, monitoring device, and processing rule information. The graphical user interface transmits the user selection to a processing server, which configures one or more monitoring devices according to the user selections.

In accordance with an aspect of the present invention, a method for configuring monitoring devices through a central interface is provided. The method can be implemented in an integrated information system in communication with a number of monitoring devices. A central server obtains a selection of at least one client associated with the integrated information system, a selection of at least one premises associated with the selected client, within the integrated information system, a selection of at least one location wherein the selected location is associated with an identifiable attribute of a premises, a selection of one or more monitoring devices associated with the selected location, and a selection of one or more processing rules associated with one or more selected monitoring devices. The central server configures the integrated information system according to the selected client, premises, location, monitoring device and processing rule data. The client, premises, location, monitoring device and processing rule data selections are obtained from a common user interface.

In accordance with another aspect of the present invention, a method for configuring monitoring devices through a central interface is provided. The method may be implemented in an integrated information system in communication with a number of monitoring devices and including a computer system having a display and user input device. A computing device displays on the computer system display a set of available integrated information system clients and obtains a selection from the user input device of at least one client associated with the integrated information system. The computing device then displays on the computer system display a set of available premises corresponding to the selected client and obtains a selection from the user input device of at least premises associated with the selected client. The computing device also displays on the computer system display a set of available locations corresponding to the selected premises, wherein the selected location defines an identifiable attribute of the selected premises and obtains a selection from the user input device of at least one location corresponding to the selected premises. The computing device further displays on the computer system display a set of available monitoring devices corresponding to the selected locations and obtains a selection from the user input device of one or more monitoring devices corresponding to the selected location. The computing device then displays on the computer system display a set of processing rules associated with each selected monitoring device and obtains a selection from the user input device of one or more processing rules associated with each selected monitoring device, wherein the selected processing rule can include a default processing rule. The computing device transmits the selected client, premises, location, monitoring device and processing rule data for configuration of the integrated information system. The selected client, premises, location, monitoring device and processing rule data is obtained from a common user interface.

In accordance with a further aspect of the present invention, an integrated information system is provided. The integrated information system includes one or more monitoring devices operable to obtain and transmit monitoring data corresponding to a specified premises. The integrated information system also includes at least one processing server operable to communicate with the one or more monitoring devices. The processing server is further operable to configure each monitoring device. The integrated information system further includes a computer display operable to generate a user interface for obtaining a user selection of client, premises, location, monitoring device, and processing rule data and to transmit the data to the processing server. The processing server configures the monitoring devices according to the client, premises, location, monitoring device and processing rule data obtained from the user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of a prior art illustration of a representative portion of the Internet;

FIG. 2 is a block diagram of an integrated information system utilized to configure or install monitoring devices through a common access point in accordance with the present invention;

FIG. 3 is a block diagram depicting an illustrative architecture for a premises server in accordance with the present invention;

FIG. 4 is a block diagram depicting an illustrative architecture for a central server in accordance with the present invention;

FIGS. 5A and 5B are flow diagrams illustrative of a premises configuration routine implemented by an integrated information system in accordance with the present invention;

FIG. 6 is a flow diagram illustrative of a create or modify users sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 7 is a flow diagram illustrative of a process user data entry sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 8 is a flow diagram illustrative of a create or modify clients sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 9 is a flow diagram illustrative of a process client data entry sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 10 is a flow diagram illustrative of a create or modify premises sub-routine implemented by an integrated information system in accordance with the present invention;

FIGS. 11A and 11B are flow diagrams illustrative of a process premises data entry sub-routine implemented by an integrated information system in accordance with the present invention;

FIGS. 12A and 12B are flow diagrams illustrative of a create or modify locations sub-routine implemented by an integrated information system in accordance with the present invention;

FIGS. 13A and 13B are flow diagrams illustrative of process monitoring device and monitoring device rules a sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 14 is a flow diagram illustrative of a process auxiliary locations sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 15 is a flow diagram illustrative of a process location attributes sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 16 is a flow diagram illustrative of a process device rules sub-routine implemented by an integrated information system in accordance with the present invention;

FIG. 17 is a block diagram representative of a screen display illustrating an integrated information system location selection interface in accordance with the present invention;

FIG. 18 is a block diagram representative of a screen display illustrating an integrated information system device selection interface having a tree-structure in accordance with the present invention; and

FIG. 19 is a block diagram representative of a screen display illustrating an integrated information system monitoring device processing rules selection interface in accordance with the present invention.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As described above, aspects of the present invention are embodied in a World Wide Web (“WWW” or “Web”) site accessible via the Internet. As is well known to those skilled in the art, the term “Internet” refers to the collection of networks and routers that use the Transmission Control Protocol/Internet Protocol (“TCP/IP”) to communicate with one another. A representative section of the Internet 20 is shown in FIG. 1, where a plurality of local area networks (“LANs”) 24 and a wide area network (“WAN”) 26 are interconnected by routers 22. The routers 22 are special purpose computers used to interface one LAN or WAN to another. Communication links within the LANs may be twisted wire pair, coaxial cable, or optical fiber, while communication links between networks may utilize 56 Kbps analog telephone lines, 1 Mbps digital T-1 lines, 45 Mbps T-3 lines, or other communications links known to those skilled in the art.

Furthermore, computers 28 and other related electronic devices can be remotely connected to either the LANs 24 or the WAN 26 via a modem and temporary telephone or wireless link. It will be appreciated that the Internet 20 comprises a vast number of such interconnected networks, computers, and routers and that only a small, representative section of the Internet 20 is shown in FIG. 1.

The Internet has recently seen explosive growth by virtue of its ability to link computers located throughout the world. As the Internet has grown, so has the WWW. As is appreciated by those skilled in the art, the WWW is a vast collection of interconnected or “hypertext” documents written in HyperText Markup Language (“HTML”) or other markup languages, which are electronically stored at “WWW sites” or “Web sites” throughout the Internet. Other interactive hypertext environments may include proprietary environments, such as those provided in America Online or other online service providers, as well as the “wireless Web” provided by various wireless networking providers, especially those in the cellular phone industry. It will be appreciated that the present invention could apply in any such interactive hypertext environments; however, for purposes of discussion, the Web is used as an exemplary interactive hypertext environment with regard to the present invention.

A Web site is a server/computer connected to the Internet that has massive storage capabilities for storing hypertext documents and that runs administrative software for handling requests for those stored hypertext documents. Embedded within a hypertext document are a number of hyperlinks, i.e., highlighted portions of text that link the document to another hypertext document possibly stored at a Web site elsewhere on the Internet. Each hyperlink is assigned a Uniform Resource Locator (“URL”) that provides the exact location of the linked document on a server connected to the Internet and describes the document. Thus, whenever a hypertext document is retrieved from any Web server, the document is considered retrieved from the World Wide Web. Known to those skilled in the art, a Web server may also include facilities for storing and transmitting application programs, such as application programs written in the JAVA® programming language from Sun Microsystems, for execution on a remote computer. Likewise, a Web server may also include facilities for executing scripts and other application programs on the Web server itself.

A consumer or other remote access user may retrieve hypertext documents from the World Wide Web via a Web browser program. A Web browser, such as Netscape's NAVIGATOR® or Microsoft's Internet Explorer, is a software application program for providing a graphical user interface to the WWW. Upon request from the consumer via the Web browser, the Web browser locates and retrieves the desired hypertext document from the appropriate Web server using the URL for the document and the HTTP protocol. HTTP is a higher-level protocol than TCP/IP and is designed specifically for the requirements of the WWW. HTTP runs on top of TCP/IP to transfer hypertext documents between server and client computers. The WWW browser may also retrieve programs from the Web server, such as JAVA applets, for execution on the client computer.

Referring now to FIG. 2, an integrated information system 200 for use with the present invention will be described. Generally described, an integrated information system 200 is a subscriber-based system allowing a number of monitoring devices within one or more premises to be monitored from a single control location. Additionally, the data from the monitoring devices is processed according to one or more rules. The control location customizes output of the processed data to a number of authorized users dependent on the preferences and rights of the user. While the system of the present invention is utilized to integrate traditional security monitoring functions, it is also utilized to integrate any information input in a like manner.

In an illustrative embodiment of the present invention, the integrated information system 200 includes one or more premises servers 202 located on any number of premises 204. The premises server 202 communicates with one or more monitoring devices 206. In an illustrative embodiment, the monitoring devices 206 can include smoke, fire and carbon monoxide detectors. The monitoring devices 206 can also include door and window contacts, glass break detectors, motion sensors, audio detectors and/or infrared detectors. Still further, the monitoring devices 206 can include computer network monitors, voice identification devices, card readers, video cameras, still cameras, microphones and/or fingerprint, facial, retinal, or other biometric identification devices. Still further, the monitoring devices 206 can include conventional panic buttons, global positioning satellite (“GPS”) locators, other geographic locators, medical indicators, and vehicle information systems. The monitoring devices 206 can also be integrated with other existing information systems, such as inventory control systems, accounting systems, or the like. The premises server 202 can also maintain a device interface database for translating standard protocol-encoded tasks into device specific commands as will be explained in greater detail below. Alternatively, the premises server 202 may be in communication with a separate device server that maintains the device interface database. It will be apparent to one skilled in the relevant art that additional or alternative monitoring devices 206 may be practiced with the present invention.

The premises server 202 also communicates with one or more output devices 208. In an illustrative embodiment, the output devices 208 can include audio speakers, display or other audio/visual displays. The output devices 208 may also include electrical or electro-mechanical devices that allow the system to perform actions. The output devices 208 can include computer system interfaces, telephone interfaces, wireless interfaces, door and window locking mechanisms, aerosol sprayers, and the like. As will be readily understood by one skilled in the art, the type of output device 208 is associated primarily with the type of action the system produces. Accordingly, additional or alternative output devices 208 are considered to be within the scope of the present invention.

The premises server 202 is in communication with a central server 210. Generally described, the central server 210 obtains the various monitoring device data, processes the data, and outputs the data to one or more authorized users. In an illustrative embodiment, the communication between the central server 210 and the premises server 202 is remote and two-way. One skilled in the relevant art will understand that the premises server 202 may be remote from the premises or may omitted altogether. In such an alternative embodiment, the monitoring devices 206 transmit the monitoring data to a remote premises server 202 or alternatively, they transmit the monitoring data directly to the central server 210. Alternatively, one skilled in the relevant art will also appreciate that the premises server 202 may also perform one or more of the functions illustrated for the central server 210.

Also in communication with the central server 210 is a central database 212. In an illustrative embodiment, the central database 212 includes a variety of databases including an event logs database 214, an asset rules database 216, a resource rules database 218, an asset inventory database 220, a resource inventory database 222, an event rules database 224, and an active events database 226. The utilization of some of the individual databases within the central database will be explained in greater detail below. As will be readily understood by one skilled in the relevant art, the central database may be one or more databases that may be remote from one another. In an alternative embodiment, the central server 210 also maintains a device interface database for translating standard protocol-encoded tasks into device specific commands as will be explained in greater detail below. Accordingly, the central server 210 may perform some or all of the translation actions in accordance with the present invention.

With continued reference to FIG. 2, the central server 210 communicates with one or more notification acceptors 228. In an illustrative embodiment, the notification acceptors 228 can include one or more authorized users who are associated with the notification acceptor 228. Each authorized user has a preference of notification means and rights to the raw and processed monitoring data. The authorized users include premises owners, security directors or administrators, on-site security guards, technicians, remote monitors (including certified and non-certified monitors), customer service representatives, emergency personnel, and others. Moreover, the notification acceptor 228 may be a centralized facility/device that can be associated with any number of authorized users. As will be readily understood by one skilled in the art, various user authorizations may be practiced with the present invention. Additionally, it will be further understood that one or more of the rules databases may be maintained outside of the central server 210.

In an illustrative embodiment of the present invention, the central server 210 communicates with the notification acceptors 228 utilizing various communication devices and communication mediums. The devices include personal computers, hand-held computing devices, wireless application protocol enabled wireless devices, cellular or digital telephones, digital pagers, and the like. Moreover, the central server 210 may communicate with these devices via the Internet utilizing electronic messaging or Web access, via wireless transmissions utilizing the wireless application protocol, short message services, audio transmissions, and the like. As will be readily understood by one skilled in the art, the specific implementation of the communication mediums may require additional or alternative components to be practiced. All are considered to be within the scope of practicing the present invention.

In an illustrative embodiment of the present invention, the central server 210 may utilize one or more additional server-type computing devices to process incoming data and outgoing data, referred to generally as a staging server. The staging server may be a separate computing device that can be proximate to or remote from the central server 210, or alternatively, it may be a software component utilized in conjunction with a general-purpose server computing device. One skilled in the relevant art will appreciate communications between the central server 210 and the staging server can incorporate various security protocols known to those skilled in the relevant art.

FIG. 3 is a block diagram depicting an illustrative architecture for a premises server 202 formed in accordance with the present invention. Those of ordinary skill in the art will appreciate that the premises server 202 includes many more components than those shown in FIG. 3. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 3, the premises server 202 includes a network interface 300 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN. Those of ordinary skill in the art will appreciate that the network interface 300 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol or other protocols, such as Internet Inter-ORB Protocol (“IIOP”). The premises server 202 may also be equipped with a modem for connecting to the Internet through a point-to-point protocol (“PPP”) connection or a serial-line Internet protocol (“SLIP”) connection as known to those skilled in the art.

The premises server 202 also includes a processing unit 302, a display 304, a device interface 306 and a mass memory 308, all connected via a communication bus, or other communication device. The device interface 306 includes hardware and software components that facilitate interaction with a variety of the monitoring devices 206 via a variety of communication protocols including TCP/IP, X10, digital I/O, RS-232, RS-485 and the like. Additionally, the device interface facilitates communication via a variety of communication mediums including telephone landlines, wireless networks (including cellular, digital and radio networks), cable networks, and the like. In an actual embodiment of the present invention, the I/O interface is implemented as a layer between the server hardware and software applications utilized to control the individual digital image devices. One skilled in the relevant art will understand that alternative interface configurations may be practiced with the present invention.

The mass memory 308 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 308 stores an operating system 310 for controlling the operation of the premises server 202. It will be appreciated that this component may comprise a general-purpose server operating system as is known to those skilled in the art, such as UNIX, LINUX™, or Microsoft WINDOWS NT®. The memory also includes a WWW browser 312, such as Netscape's NAVIGATOR® or Microsoft's Internet Explorer, for accessing the WWW.

The mass memory also stores program code and data for interfacing with various premises monitoring devices 206, for processing the monitoring device data and for transmitting the data to a central server. More specifically, the mass memory stores a device interface application 314 in accordance with the present invention for obtaining standard protocol-encoded commands and for translating the commands into device specific protocols. Additionally, the device interface application 314 obtains monitoring device data from the connected monitoring devices 206 and manipulates the data for processing by a central server 210, and for controlling the features of the individual monitoring devices 206. The device interface application 314 comprises computer-executable instructions which, when executed by the premises server, obtains and transmits device data as will be explained below in greater detail. The mass memory also stores a data transmittal application program 316 for transmitting the device data to the central server and to facilitate communication between the central server and the monitoring devices 206. The operation of the data transmittal application 316 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server 202 using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network interface 300.

FIG. 4 is a block diagram depicting an illustrative architecture for a central server 210. Those of ordinary skill in the art will appreciate that the central server 210 includes many more components then those shown in FIG. 4. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 4, the central server 210 includes a network interface 400 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN. Those of ordinary skill in the art will appreciate that the network interface 400 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol or other protocols, such as Internet Inter-ORB Protocol (“IIOP”). The central server 210 may also be equipped with a modem for connecting to the Internet through a PPP connection or a SLIP connection as known to those skilled in the art.

The central server 210 also includes a processing unit 402, a display 404, and a mass memory 406, all connected via a communication bus, or other communication device. The mass memory 406 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 406 stores an operating system for controlling the operation of the central server 210. It will be appreciated that this component may comprise a general-purpose server operating system as is known to those skilled in the art, such as UNIX, LINUX™, or Microsoft WINDOWS NT®. In an illustrative embodiment of the present invention, the central server 210 may also be controlled by a user through use of a computing device, which may be directly connected to or remote from the central server 210.

The mass memory 406 also stores program code and data for interfacing with the premises devices, for processing the device data, and for interfacing with various authorized users. More specifically, the mass memory 406 stores a premises interface application 410 in accordance with the present invention for obtaining data from a variety of monitoring devices 206 and for communicating with the premises server 202. The premises interface application 410 comprises computer-executable instructions that when executed by the central server 210, interface with the premises server 202 as will be explained below in greater detail. The mass memory 406 also stores a data processing application 412 for processing monitoring device data in accordance with rules maintained within the central server 210. The operation of the data processing application 412 will be described in greater detail below. The mass memory 406 further stores an authorized user interface application 414 for outputting the processed monitoring device data to a variety of authorized users in accordance with the security process of the present invention. The operation of the authorized user interface application 414 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the central server 210 using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network interface 400.

Generally described, the present invention provides an integrated computerized system and method utilizing a software interface to install one or more networked hardware monitoring and output devices into an integrated information system. Specifically, aspects of the present invention will be described in relation to a system and method for managing monitoring devices 206 within a common network architecture. In an actual embodiment of the present invention, an application program interface (“API”) screen display may be generated by a computing device and utilized to collect the data from a user to configure a premises for monitoring. In accordance with this embodiment, a user accesses an installation or account setup page using a Web browser on a browser computer. The Web page may be a standard screen display generated by a browser application executing a markup language, such as hypertext markup language (“HTML”), extensible markup language (“XML”), or other languages conforming to the standard general markup language (“SGML”) information management standard. In an illustrative embodiment of the present invention, the browser computer may connect to the integrated information system 200 through the central server 210. Alternatively, the browser computer may connect directly to the integrated information system 200. By entering, reviewing and or modifying data on the screen interface, the user can perform a variety of installation, configuration and modification functions relating to the integrated information system.

Prior to discussing the implementation of the present invention, a general overview of an integrated information system 200 in which the present invention can be implemented will be described. In an actual embodiment of the present invention, the monitoring device data is categorized as asset data, resource data or device data. Asset data is obtained from a monitoring device 206 corresponding to an identifiable object that is not capable of independent action. For example, asset data includes data obtained from a bar code or transponder identifying a particular object, such as a computer, in a particular location. Resource data is obtained from a monitoring device corresponding to an identifiable object that is capable of independent action. For example, resource data includes data from a magnetic card reader that identifies a particular person who has entered the premises. Event data is obtained from a monitoring device corresponding to an on/off state that is not correlated to an identifiable object. Event data is a default category for all of the monitoring devices. As will be readily understood by one skilled in the relevant art, alternative data categorizations are considered to be within the scope of the present invention.

The monitoring device data is obtained by the monitoring devices 206 on the premises server 202 and transmitted to the central server 210. The central server 210 receives the monitoring device data and processes the data according to a rules-based decision support logic. In an actual embodiment of the present invention, the central server 210 utilizes the databases 212 to store logic rules for asset data, resource data and event data. Moreover, because the monitoring device data is potentially applicable to more than one authorized user, multiple rules may be applied to the same monitoring device data. In an alternative embodiment, the databases 212 may be maintained in locations remote from the central server 210.

In the event the processing of the monitoring device rules indicates that action is required, the central server 210 generates one or more outputs associated with the rules. The outputs include communication with indicated notification acceptors 228 according to the monitoring device data rules. For example, an authorized user may indicate a hierarchy of communication mediums (such as pager, mobile telephone, land-line telephone) that should be utilized in attempting to contact the user. The rules may also indicate contingency contacts in the event the authorized user cannot be contacted. Additionally, the rules may limit the type and/or amount of data the user is allowed to access. Furthermore, the outputs can include the initiation of actions by the central server 210 in response to the processing of the rules. A more detailed description of an implementation of an integrated information system may be found in commonly assigned U.S. application Ser. No. 09/825,506 entitled SYSTEM AND METHOD FOR PROVIDING CONFIGURABLE SECURITY MONITORING UTILIZING AN INTEGRATED INFORMATION SYSTEM, filed Apr. 3, 2001, which is incorporated by reference herein.

Turning now to FIGS. 5A and 5B, a routine 500 for processing a premises configuration in an integrated information system 200 will be described. More specifically, in accordance with the present invention, the routine 500 relates to a process for obtaining user, client, premises, location, monitoring device, and processing rule data from a user by utilizing a common user interface.

With reference to FIG. 5A, at decision block 502, a test is conducted to determine whether the user wishes to create or modify a number of users to the integrated information system 200. In accordance with the present invention, a user may be selected to have access to the configurations system of the integrated information system 200. Alternatively, a user may be selected to have access as a notified user of the integrated information system. In an illustrative embodiment of the present invention, block 502 may be executed in the user selects to modify or create a user, such as by manipulating a user input device. Alternatively, the user interface application 414 of the central server 210 may prompt a user to determine whether the action is desired. If the user does not select a create or modify an integrated information system user option, the routine 500 proceeds to decision block 506, which will be described in greater detail below. Alternatively, if the user wishes to create or modify a user, the routine processes the create or modify user request at block 504.

FIGS. 6 and 7 are flow diagrams illustrative of a create or modify user sub-routine implemented by the central server 210 in accordance with the present invention. With reference to FIG. 6, at block 602, the central server 210 obtains a list of available integrated information system users. At decision block 604, a test is conducted to determine whether a particular user is on the list. In an illustrative embodiment of the present invention, the user interface application 414 of the central server 210 may display a list of available system users and allow the user to select from the list. If a desired user is on the list, the central server 210 retrieves user data. In an illustrative embodiment, the central server 210 may recall the user data from the database 212. If the user is not on the displayed list, or once the selected user data has been retrieved, at block 608, the central server 210 processes the input of user data. Once the central server 210 has processed the user data entry at block 608, at block 610, the central server stores the updated user data, and the sub-routine 600 returns to routine 500 at block 612.

FIG. 7 is a flow diagram illustrative of a process user data entry sub-routine 700 implemented by the central server 210 in accordance with the present invention. At block 702, the central server 210 attempts to obtain the stored user data from the database 212. At decision block 704, a test is conducted to determine whether the stored user data is available. If the data is available, the central server retrieves the user data values. Alternatively, if the data is not available, or once the central server 210 has retrieved the stored user data values, at block 708 the central server 210 obtains additional user values from the user. In an illustrative embodiment of the present invention, the user interface application 414 of the central server 210 obtains additional user values by accepting inputs. For example, the user interface application 414 may import data files, obtain keyboard or computer mouse entries, obtain voice inputs, and the like. In one aspect, the user data entry can include data modifying an existing user data record. In another aspect, the user data entry can include data defining new user data records.

At decision block 710, a test is conducted to determine whether more data entries are desired. For example, the central server 210 may process data entries for a number of integrated information users. If more data entries are requested, the routine 700 returns to block 702. Alternatively, if no more data entries are requested, the sub-routine 700 returns to sub-routine 600 at block 712.

Returning to FIG. 5A, at decision block 506, a test is done to determine whether the user wishes to create or modify integrated information system 200 clients. Similar to decision block 502, decision block 506 may be executed by obtaining the initiation of a user action or by prompting a user. If the user does not wish to create or modify clients, the routine 500 proceeds to decision block 510, which will be described in detail below. Alternatively, if the user wishes to create or modify clients, the central server 210 processes the create or modify client request at block 508.

FIGS. 8 and 9 are flow diagrams illustrative of various process create or modify client data sub-routines implemented by the central server 210 in accordance with the present invention. With reference to FIG. 8, at block 802, the central server 210 obtains a list of available system clients. At block 804, a test is conducted to determine whether a desired client, is on the list of available system clients. In an illustrative embodiment of the present invention, the user interface application 414 of the central server 210 may display a list of available system users and allow the user to select from the list. If the client is on the list, at block 806 the central server 210 retrieves the existing client data values. If the client is not on the list, or once the existing client values have been retrieved, at block 808, the central server 210 process the client data entry. Once the central server 210 has processed the client data entry at block 808, the central server stores the updated user data at block 810. At block 812, the sub-routine 800 returns to routine 500.

FIG. 9 is a flow diagram of a process client data entry sub-routine 900 implemented by the central server 210 in accordance with the present invention. At block 902, the central server 210 attempts to obtain the stored client data. At decision block 904, a test is conducted to determine whether the client data is available. If the data is available, the central server 210 retrieves the client data values at block 906. If the client data is not previously stored, or once the client has been retrieved, at block 908, the user interface 414 application of the central server 210 obtains client data values inputs from the user. For example, the user interface application 414 may import data files, obtain keyboard or computer mouse entries, obtain voice inputs, and the like. In one aspect, the user data entry can include data modifying an existing user data record. In another aspect, the user data entry can include data defining new user data records.

Once the client data values have been obtained by the user interface application 414, at decision block 910, a test is conducted to determine whether more client data entries are desired. If more data entries are available, the sub-routine 900 returns to block 902. Alternatively, if no more data entries are available, the routine 900 returns to sub-routine 800 at block 912.

Returning to FIG. 5A, at decision block 510, a test is conducted to determine whether the user wishes to create or modify one or more premises associated with the selected integrated information system client. In accordance with the present invention, the integrated information system 200 provides monitoring services for a client that may be associated with one or more premises to be monitored, such as multiple buildings within one or more geographic locations. Similar to the other decision blocks of FIG. 5A, in an illustrative embodiment of the present invention, decision block 510 may be executed in the user selects to modify or create a user, such as by manipulating a user input device. Alternatively, the user interface application 414 of the central server 210 may prompt a user to determine whether the action is desired. If the user does not wish to create or modify a premises on the integrated information system 200, the routine 500 proceeds to decision block 514, which will be explained in greater detail below. Alternatively, if the user wishes to create or modify locations, the central server 210 processes the create or modify locations request at block 508.

FIGS. 10, 11A and 11B are flow diagrams illustrative of various process create or modify premises sub-routines implemented by the central server 210 of an integrated information system 200 in accordance with the present invention. With reference to FIG. 10, at block 1002, the central server 210 obtains a list of available premises for current system clients. At decision block 1004 a test is conducted to determine whether a desired premises is on the list. If the premises is on the list, the central server 210 retrieves existing premises values at block 1006. For example, the central server 210 may obtain the data values from the databases 212. If the desired premises is not on the list, or once the central server 210 has obtained the premises data, at block 1008, the central server 210 processes the user entry of the premises data. In an illustrative embodiment of the present invention, the user interface application 414 utilizes block 1008 to obtain client contact data, such as client address and communication information. Additionally, the user interface application 414 obtains premises user data related to the selected premises. Once the central server 210 obtains the premises data entry, at block 1010, the central server stores the updated premises data and the sub-routine 1000 returns to sub-routine 500 at block 1012.

Turning now to FIGS. 11A and 11B, a process premises user data entry sub-routine will be described. In an illustrative embodiment of the present invention, the premises data can include user premises assignment data, user group assignment data, and user process assignment data. With reference to FIG. 11A, at block 1102, the central server 210 obtains user premises assignment data. At decision block 1104, a test is conducted to determine whether user process assignment data is available. If the user premises assignment data is available, at block 1106, the central server 210 retrieves the user premises data values. If the data is not available, or once the user premises data values have been retrieved at block 1108, the central server 210 obtains user premises assignment data values from the user input. For example, the user interface application 414 may import data files, obtain keyboard or computer mouse entries, obtain voice inputs, and the like. In one aspect, the user data entry can include data modifying an existing user data record. In another aspect, the user data entry can include data defining new user data records.

At block 1110, the central server obtains a list of the user group assignment data. At decision block 1112, a test is conducted to determine whether the user group data is available. If the data is available, the central server 210 retrieves the user premises data values at block 1114. With reference to FIG. 11B, if the group assignment data is not available, or once the central server 210 has retrieved the user group assignment data, at block 1116, the user interface application 414 of the central server obtains the user entry of the group assignment data. As described above, the user interface application 414 can obtain the group assignment data entry in a variety of manners.

At block 1118, the central server 210 obtains user process assignment data. At decision block 1120, a test is conducted to determine whether the user process assignment data is available. If the user process assignment data is available, the central server 210 retrieves the user process data values at block 1122. For example, the central server 210 may retrieve the data from the databases 212. If the data is not available, or once the central server 210 has retrieved the user process data values, at block 1124, the central server 210 obtains the user process data values. At decision block 1126, a test is conducted to determine whether there are more user premises assignments. If there are more user premises assignments, the routine 1100 returns to block 1108. Alternatively, if there are no more assignments, the sub-routine 1100 returns to sub-routine 1000 at block 1128.

Returning to FIG. 5A, at decision block 514, a test is conducted to determine whether the user wishes to create or modify one or more locations corresponding to the selected client and premises. If the user does not wish to create or modify one or more locations, the routine 500 proceeds to decision block 518 (FIG. 5B), which will be explained in greater detail below. Alternatively, if the user wishes to create or modify locations, the central server 210 processes the create or modify location request at block 516.

FIGS. 12A and 12B are flow diagrams illustrative of a create or modify location sub-routine 1200 implemented by the central server 210 in accordance with the present invention. In an illustrative embodiment of the present invention, the location data can include premises location data and location group data. With reference to FIG. 12A, at block 1202, the central server 210 obtains premises location data. At decision block 1204, a test is conducted to determine whether the desired premises location data is available. If the premises location data is available, at block 1206, the central server 210 retrieves existing location values. In an illustrative embodiment of the present invention, the user interface application 414 of the central server 210 may generate a list of available locations for the selected premises. If the premises location data is not available, or once the premises location data has been retrieved, at block 1208, the central server obtains location data values.

FIG. 17 is a block diagram representative of a screen display 1700 illustrating a an integrated information system location selection interface generated by the central server 210 in accordance with the present invention. As illustrated in FIG. 17, the screen display includes a user selection portion 1702 for selecting the modification or creation of location data. The screen display also includes an identification portion 1704 for informing a user of which data is currently being modified or created. Additionally, the screen display further includes data entries portions 1706 and 1708 for displaying to the user the available location data and for facilitating the entry of additional data. One skilled in the relevant art will appreciate that alternative screen displays may be utilized in accordance with the present invention.

Returning to FIG. 12A, at block 1210, the central server 210 obtains location group data. At decision block 1212, a test is conducted to determine whether the group location data is available. If the group location data is available, at block 1214, the central server 210 routine retrieves location group data values. With reference to FIG. 12B, if the location group data values are not available, or once the central server 210 has retrieved the location group data, at block 1216, the central server 210 obtains location group assignment data. At decision block 1218, a test is conducted to determine whether there are more location groups. If there are more location groups, the central server retrieves additional location group data values at block 1214 (FIG. 12A). Alternatively, if there are no more location groups, at decision block 1220, a test is conducted to determine whether there are more locations to be modified. If there are more locations, the sub-routine 1200 returns to block 1208. Alternatively, if there are no more locations, the sub-routine 1200 returns at block 1222. One skilled in the relevant art will appreciate that the central server 210 may implement the various decision blocks of sub-routine 1200 in a single action or series of actions.

Turning now to FIG. 5B, at decision block 518 a test is conducted to determine whether the user wishes to create or modify devices and rules. If the user does not wish to create or modify devices and rules, the process 500 proceeds to block 522, which will be described in greater detail below. Alternatively, if the user wishes to create or modify devices and rules, the central server 210 processes the create or modify devices and rules sub-routine at block 520.

FIGS. 13A, 13B, 14, 15, 16 and 17 are flow diagrams illustrative of various sub-routines implemented by the central server 210 to create or modify devices and rules in accordance with the present invention. With reference to FIGS. 13A and 13B, a create or modify devices and rules sub-routine 1300 will be described. At block 1302, the central server 210 lists all installed monitoring devices 206 and/or output devices 208 that are found within a previously selected premises. In accordance with the present invention, the user interface application 414 can generate a screen display to facilitate the selection of installed devices within the premises. More specifically, in an actual embodiment of the present invention, the user interface application 414 may utilize tree-structures and data tables to facilitate the selection of devices and the management of device attributes.

FIG. 18 is a block diagram representative of a screen display 1800 illustrating a an integrated information system device selection interface having a tree-structure in accordance with the present invention. The screen display 1900 includes a user selection portion 1802 for selecting the modification or creation of location data. As illustrated in FIG. 18, the user can select to manipulate various devices by selecting the corresponding tab of the user selection portion 1802. The screen display further includes a tree-structure portion 1804 for hierarchically displaying which monitoring device has been installed into the premises. In an actual embodiment of the presentation, the data processing application 412 of the central server 210 may configure the tree-structure portion 1904 based on the authorization of the user, a most recently utilized list, or a combination thereof. Moreover, the data processing application 412 may utilize additional information inputted by the user, such as specific device, to determine device compatibility and adjust the tree-structure accordingly. One skilled in the relevant art will appreciate that a user can select a specific device, through the manipulation of the elements of a graphical user interface, or of peripheral devices linked to a graphical user interface, such as a mouse or touch pad.

Returning to FIG. 13A, at decision block 1304, a test is conducted to determine whether a desired device is listed. If the desired device is not listed, the routine 1300 proceeds to block 1322 (FIG. 13B), which will be explained in detail below. If the desired device is listed and selected, at decision block 1306, a test is conducted to determine whether the selected device has any auxiliary locations. In accordance with the present invention, an auxiliary location includes one or more areas or zones within a premises with which a monitoring device 206 is associated. For example, a pan-tilt-zoom (“PTZ”) camera may monitor a door as a primary location and a portion of a hallway as an auxiliary location. If the device has auxiliary locations, the central server 210 processes the auxiliary location selection at block 1308.

FIG. 14 is a flow diagram illustrating a process auxiliary device locations sub-routine 1400 implemented by the central server 210 in accordance with the present invention. At block 1402, the central server 210 obtains a list of all known auxiliary locations corresponding to the selected monitoring device. At decision block 1404, a test is conducted to determine whether a desired auxiliary location is found in the list. If the desired auxiliary location is not found, at block 1406, the user interface application 414 obtains a user selection of an auxiliary location desired. For example, the user may define an auxiliary location by naming the location and defining some parameters of the location. At block 1408, the data processing application 412 of the central server 210 stores the selected auxiliary location. At decision block 1410, a test is conducted to determine whether the user wishes to select additional auxiliary locations. If the user wishes to select additional auxiliary locations, the sub-routine 1400 returns to block 1402. Alternatively, the sub-routine returns to sub-routine 1300 at block 1412.

Returning to FIG. 13A, once the auxiliary locations have been processed, or if no auxiliary locations are selected/exist, at block 1310, the central server 210 obtains the device location and communication attributes. In an illustrative embodiment of the present invention, the device location and communication attributes can include an Internet protocol (“IP”) address, a unique name, computing device port settings, zone settings for monitoring, and the like. At decision block 1312, a test is conducted to determine whether a selected device includes device attributes. If the selected device does not include attributes, the sub-routine proceeds to decision block 1316, which will be explained in greater detail below. Alternatively, if the selected device includes device attributes, the central server 210 processes the device attributes at block 1314.

FIG. 15 is a flow diagram illustrative of a process device location attributes sub-routine 1500 implemented by the central server 210 in accordance with the present invention. At block 1502, the central server obtains the device location attribute data. At decision block 1504, a test is conducted to determine whether the device location attribute data exists. If the device location attribute data exists, at block 1506, the central server 210 obtains and displays the listed device location attributes. At block 1508, the user interface application 414 of the central server 210 obtains any user edits to the device location attribute data. Referring again to FIG. 18, the screen display 1800 further includes a data table portion 1806 for displaying to the user various device location attributes of a device selected in the tree-structure portion 1804. The data table portion 1806 allows the user to review the various device attributes and modify them by manipulating a user interface.

Referring again to FIG. 15, if at decision block 1504 the device location attribute data does not exist, at block 1510, the data processing application 412 retrieves any default device attributes for use with the device. For example, the device manufacturer may include some default settings for a device, or an integrated information system 200 administrator may designate default values. At decision block 1512, a test is conducted to determine whether the user wishes to edit the default device location attributes. If the user selects to edit the default attributes, the sub-routine 1500 proceeds to block 1508 as described above.

Once the user has completed editing the device location attributes, or if the user does not wish to edit the default attributes at decision block 1512, at decision block 1514, a test is conducted to determine whether there are additional device location attributes that are to be edited. If there are additional device location attributes, the sub-routine 1500 returns to block 1502. Alternatively, the sub-routine 1500 returns to sub-routine 1300 at block 1516.

Returning to FIG. 13A, at decision block 1316, a test is conducted to determine whether the user wishes to create a device rule for the selected device. If the user wishes to create or modify a device rule, the central server 210 processes the device rule at block 1318. If the user does not wish to create or modify a device rule or once the device rule has been processed, the sub-routine 1300 returns to routine 500 at block 1320.

FIG. 16 is a flow diagram of a process device rules sub-routine 1600 implemented by the central server 210 in accordance with the present invention. At block 1602, the central server 210 obtains a list of installed device rules. At decision block 1604, a test is conducted to determine whether a desired device rule is listed. If no device rule is listed, at block 1606, the central server 210 obtains default rule data for the device. In an illustrative embodiment of the present invention, the default data may be set by the user or by an integrated information system administrator. Alternatively, if the desired device rule is found, at block 1608, the central server 210 obtains the existing device rule data.

FIG. 19 is a block diagram representative of a screen display 1900 illustrating a an integrated information system monitoring device processing rules selection interface generated by the user interface application 414 of the central server 210 in accordance with the present invention. The screen display 1900 includes a user selection portion 1902 for selecting the modification or creation of location data and a display portion 1904 for informing the user what data is being edited. As illustrated in FIG. 19, the user can select to manipulate various devices by selecting the corresponding tab of the user selection portion 1902. The screen display 1900 further includes a rules display portion 1906 for displaying and editing rule details, as will be explained in better detail below.

Returning to FIG. 16, at block 1610, the user interface application 414 obtains device rule data from the user. In an illustrative embodiment of the present invention, the user interface application 414 can obtain device rule data relating to a rule name, rule purpose, effective date ranges, severity of a violation, and corresponding device/location information. At block 1612, the user interface application 414 obtains notification information from the user. In an illustrative embodiment of the present invention, the notification information can include a selection of a set of user, notification routing information, and timing information. At decision block 1614 a test is conducted to determine whether there are more users to add to the notification. If so, the sub-routine 1600 returns to block 1612. If no additional users are to be added, the sub-routine 1600 returns at block 1616.

Turning now to FIG. 13B, if at decision block 1304, the desired device is not listed, at block 1322, the central server 210 obtains a list of all available devices to be installed. In an illustrative embodiment of the present invention, the central server 210 databases 212 may maintain a list and attributes of a number of devices that may be installed in the integrated information system 200. With reference to FIG. 18, the user interface application 414 may generate a tree-structure screen interface to facilitate a user selection. At decision block 1324, a test is conducted to determine whether the desired device is found in the list of available devices. If the device is not available, the sub-routine 1300 returns to block 1322 to obtain an indication of another device. Alternatively, the user may provide configuration information for a specific device, such as by downloading information via the user interface application 414.

Once the device has been selected, at block 1326 the central server obtains a primary location for the device. At decision block 1328, a test is conducted to determine whether the specified location is recognized by the integrated information system. If the location is not recognized, at block 1330, the user inputs the desired location to be recognized. If the location is recognized or once the location has been entered, the sub-routine returns to decision block 1306 (FIG. 13A), which was previously explained.

Returning to FIG. 5B, at block 522, the central server 210 configures the integrated information system 200 in accordance with the user inputs. In an illustrative embodiment of the present invention, the premises interface application 412 of the central server 210 may transmit the necessary configuration data for each monitoring device 206. Additionally, the data processing application 412 may provide any necessary translation processes that allow the central server 210 to communication communicate with the one or more premises servers 204. In an alternative embodiment, the central server 210 may implement the configuration changes as they are received from the user, and block 522 may be omitted. Additionally, the central server 210 may generate a confirmation report at block 522. At block 524, the routine 500 terminates.

While illustrative embodiments of the invention have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention.

Claims

1. In an integrated information system in communication with a number of monitoring devices, a method for configuring the monitoring devices through a central interface, the method comprising:

obtaining a user selection of at least one client associated with the integrated information system;
obtaining a user selection of at least one premises associated with the user selection of at least one client, within the integrated information system;
obtaining a user selection of at least one location wherein the user selection of at least one location is associated with an identifiable attribute of the user selection of at least one premises;
obtaining a user selection of at least one monitoring device associated with the user selection of at least one location;
obtaining a user selection of at least one processing rule associated with the user selection of at least one monitoring device; and
configuring the integrated information system according to the user selection of at least one client, premises, location, monitoring device and processing rule data;
wherein the user selection of at least one client, premises, location, monitoring device and processing rule data is obtained from a common user interface.

2. The method as recited in claim 1, wherein obtaining the user selection of at least one client, premises, location, monitoring device, or processing rule data includes obtaining data modifying a previous selection.

3. The method as recited in claim 1, wherein the user selection of at least one monitoring device includes a selection of monitoring device setting information related to the operation of the user selection of at least one monitoring device.

4. The method as recited in claim 3 further comprising displaying a current monitoring device setting information prior to obtaining the selection of monitoring device setting information.

5. The method as recited in claim 1 further comprising obtaining a user selection of at least one user associated with the integrated information system.

6. The method as recited in claim 5, wherein the user selection of at least one user is authorized to provide configuration information to the integrated information system.

7. The method as recited in claim 6, where the user selection of at least one user authorized to obtain information regarding the user selection of at least one premises is dynamically generated in response to the processing of the user selection of at least one processing rule in accordance with the integrated information system.

8. The method as recited in claim 5, wherein the user selection of at least one user is associated with the user selection of at least one client or premises and is authorized to accept a notification of a processing rule violation.

9. The method as recited in claim 1, wherein the user selection of at least one client is associated with a plurality of premises, and wherein the user selection of at least one premises includes a selection of all the plurality of premises associated with the user selection of at least one client.

10. The method as recited in claim 1, wherein the user selection of at least one premises includes obtaining a user selection of users authorized to obtain information regarding the user selection of at least one premises.

11. The method as recited in claim 1, wherein the user selection of at least one location corresponds to a zone or area within a premises.

12. The method as recited in claim 1, wherein the user selection of at least one location corresponds to a plurality of monitoring devices, and wherein the user selection of at least one monitoring device includes a user selection of all the plurality of monitoring devices associated with the user selection of at least one location.

13. The method as recited in claim 1, wherein the user selection of at least one monitoring device includes a user selection of at least one primary or auxiliary location associated with the monitoring device.

14. The method as recited in claim 13, wherein the user selection of at least one primary or auxiliary location is based on a default setting for the user selection of at least one monitoring device.

15. The method as recited in claim 1, wherein the user selection of at least one monitoring device includes a user selection of at least one monitoring device attribute, wherein the user selection of at least one monitoring device attribute can include a default value.

16. The method as recited in claim 1, wherein the user selection of at least one processing rule includes a user selection of a threshold indicating a violation of the user selection of at least one processing rule.

17. The method as recited in claim 1, wherein the user selection of at least one processing rule includes a specification of a comparison of collected data to information stored in a database.

18. The method as recited in claim 1, wherein the user selection of at least one processing rule includes a specification of Boolean operators for creating associations between the user selection of at least one rule for the user selection of at least one monitoring device.

19. The method as recited in claim 1, wherein the user selection of at least one processing rule includes a specification of two or more processing rules that are considered as a single processing event.

20. The method as recited in claim 1, wherein the user selection of at least one processing rule includes a selection of one or more notification acceptors corresponding to the evaluation of the user selection of at least one processing rule.

21. The method as recited in claim 1, wherein configuring the integrated information system includes inserting default values for the client, premises, location, monitoring device and processing rule data.

22. The method as recited in claim 1, wherein the common user interface is a graphical user interface displayed on a computing device.

23. The method as recited in claim 22, wherein the common user interface is a graphical user interface accessible through the World Wide Web.

24. The method as recited in claim 1, wherein the common user interface includes a plurality of hyperlinks for any of the client, premises, location, monitoring device, or processing rule data selections.

25. In an integrated information system in communication with a number of monitoring devices and including a computer system having a display and user input device, a method for configuring the monitoring devices through a central interface, the method comprising:

generating a common user interface, wherein the common user interface receives a plurality of input from a user;
obtaining a user selection of at least one client associated with the integrated information system from the common user interface;
obtaining a user selection of at least one premises associated with the user selection of at least one client from the common user interface;
obtaining a user selection of at least one location from the common user interface, wherein the user selection of at least one location is associated with an identifiable attribute of a premises;
obtaining a user selection of at least one monitoring device associated with the user selection of at least one location from the common user interface;
obtaining a user selection of at least one processing rule associated with the user selection of at least one monitoring device from the common user interface; and
transmitting the user selection of at least one client, premises, location, monitoring device and processing rule to a server, wherein the server configures the integrated information system according to the user selection of at least one client, premises, location, monitoring device and processing rule.

26. A system for configuring monitoring devices through a central interface, the system comprising:

a computing device in communication with the one or more data stores, the computing device configured to: cause a user interface to be presented on a computing device associated with a user; obtain a user selection of at least one client associated with an integrated information system; obtain a user selection of at least one premises associated with the user selection of at least one client, within the integrated information system; obtain a user selection of a location, wherein the user selection of at least one location is associated with an identifiable attribute of the user selection of at least one premises; obtain a user selection of at least one monitoring device associated with the location; obtain a user selection of at least one processing rule associated with the user selection of at least one monitoring device, configure the integrated information system according to the user selection of the at least one client, premises, location, monitoring device and processing rule, wherein the user selection of the at least one client, premises, location, monitoring device, and processing rule obtained from the computing device associated with the user.

27. The system of claim 26, wherein to obtain a user selection of at least one monitoring device, the computing device is configured to obtain a threshold that establishes when a violation of the at least one processing rule will occur.

28. The system of claim 26, wherein to obtain a user selection of the at least one client, the computing device is configured to authorize the at least one client to accept a notification of a processing rule violation.

29. The system of claim 26, wherein to obtain the user selection of at least one monitoring device, the computing device is configured to identify an attribute associated with the user selection of the location.

30. The system of claim 26, wherein to obtain the user selection of the location, the computing device is configured to identify an attribute associated with the at least one processing rule.

31. The system of claim 26, wherein the user selection of at least one monitoring device includes a user selection of all monitoring devices associated with the location.

32. The system of claim 26, wherein the user selection of at least one processing rule includes a specification of a comparison of collected data to information stored in a database.

33. A computer-readable, non-transitory storage medium having one or more computer-executable modules for configuring monitoring devices through a central interface, the one or more computer-executable modules comprising:

a first module configured to: cause a user interface to be presented on a computing device associated with a user; obtain a user selection of at least one client associated with an integrated information system; obtain a user selection of at least one premises associated with the user selection of at least one client, within the integrated information system; obtain a user selection of a location, wherein the user selection of at least one location is associated with an identifiable attribute of the user selection of at least one premises; obtain a user selection of at least one monitoring device associated with the location; obtain a user selection of at least one processing rule associated with the user selection of at least one monitoring device, configure the integrated information system according to the user selection of the at least one client, premises, location, monitoring device and processing rule, wherein the user selection of the at least one client, premises, location, monitoring device, and processing rule obtained from the computing device associated with the user.

34. The computer readable storage medium of claim 33, wherein to obtain a user selection of at least one monitoring device, the first module is configured to obtain a threshold that establishes when a violation of the at least one processing rule will occur.

35. The computer readable storage medium of claim 33, wherein to obtain a user selection of the at least one client, the first module is configured to authorize the at least one client to accept a notification of a processing rule violation.

36. The computer readable storage medium of claim 33, wherein to obtain the user selection of at least one monitoring device, the first module is configured to identify an attribute associated with the user selection of the location from one of multitude of locations at multiple premises.

37. The computer readable storage medium of claim 33, wherein to obtain the user selection of the location, the first module is configured to identify an attribute associated with the at least one processing rule.

38. The computer readable storage medium of claim 33, wherein the user selection of at least one monitoring device includes a user selection of all monitoring devices associated with the location.

39. The computer readable storage medium of claim 33, wherein the user selection of at least one processing rule includes a specification of a comparison of collected data to information stored in a database.

Referenced Cited
U.S. Patent Documents
3757039 September 1973 Brewer
4216375 August 5, 1980 Ulch et al.
4218690 August 19, 1980 Ulch et al.
4581634 April 8, 1986 Williams
4714995 December 22, 1987 Materna et al.
4721954 January 26, 1988 Mauch
4816658 March 28, 1989 Khandwala et al.
4837568 June 6, 1989 Snaper
4839640 June 13, 1989 Ozer et al.
4962473 October 9, 1990 Crain
4998279 March 5, 1991 Weiss
5086385 February 4, 1992 Launey et al.
5097505 March 17, 1992 Weiss
5204670 April 20, 1993 Stinton et al.
5210873 May 11, 1993 Gay et al.
5266944 November 30, 1993 Carroll et al.
5367624 November 22, 1994 Cooper et al.
5465358 November 7, 1995 Blades et al.
5475375 December 12, 1995 Barrett et al.
5475378 December 12, 1995 Kaarsoo et al.
5491511 February 13, 1996 Odle et al.
5499356 March 12, 1996 Eckert et al.
5506986 April 9, 1996 Healy
5541911 July 30, 1996 Nilakantan et al.
5544062 August 6, 1996 Johnston, Jr.
RE35336 September 24, 1996 Ulch et al.
5600368 February 4, 1997 Matthews
5614890 March 25, 1997 Fox
5619183 April 8, 1997 Ziegra et al.
5629981 May 13, 1997 Nerlikar
5654696 August 5, 1997 Barrett et al.
5664186 September 2, 1997 Bennett et al.
5675738 October 7, 1997 Suzuki et al.
5678039 October 14, 1997 Hinks et al.
5680328 October 21, 1997 Skorupski et al.
5682142 October 28, 1997 Loosmore et al.
5717379 February 10, 1998 Peters et al.
5729471 March 17, 1998 Jain et al.
5732232 March 24, 1998 Brush et al.
5742286 April 21, 1998 Kung et al.
5758340 May 26, 1998 Nail
5768119 June 16, 1998 Havekost et al.
5771354 June 23, 1998 Crawford
5810747 September 22, 1998 Brudny et al.
5813009 September 22, 1998 Johnson et al.
5821855 October 13, 1998 Lewis
5828848 October 27, 1998 MacCormack et al.
5838368 November 17, 1998 Masunaga et al.
5838682 November 17, 1998 Dekelbaum et al.
5844501 December 1, 1998 El-Ibiary
5848143 December 8, 1998 Andrews et al.
5870733 February 9, 1999 Bass et al.
5872594 February 16, 1999 Thompson et al.
5879163 March 9, 1999 Brown
5903455 May 11, 1999 Sharpe, Jr. et al.
5903730 May 11, 1999 Asai et al.
5905436 May 18, 1999 Dwight et al.
5917405 June 29, 1999 Joao
5923264 July 13, 1999 Lavelle et al.
5937415 August 10, 1999 Sheffield et al.
5943673 August 24, 1999 Felouzis et al.
5960174 September 28, 1999 Dew
5963131 October 5, 1999 D'angelo et al.
5982362 November 9, 1999 Crater et al.
5987519 November 16, 1999 Peifer et al.
5990885 November 23, 1999 Gopinath
6002994 December 14, 1999 Lane et al.
6011547 January 4, 2000 Shiota et al.
6012100 January 4, 2000 Frailong et al.
6023223 February 8, 2000 Baxter
6031455 February 29, 2000 Grube et al.
6041347 March 21, 2000 Harsham et al.
6041350 March 21, 2000 Takimoto
6064316 May 16, 2000 Glick et al.
6064723 May 16, 2000 Cohn et al.
6070228 May 30, 2000 Belknap et al.
6075553 June 13, 2000 Freeman et al.
6076111 June 13, 2000 Chiu et al.
6085227 July 4, 2000 Edlund et al.
6091771 July 18, 2000 Seeley et al.
6092078 July 18, 2000 Adolfsson
6105122 August 15, 2000 Muller et al.
6115040 September 5, 2000 Bladow et al.
6133941 October 17, 2000 Ono
6157935 December 5, 2000 Tran et al.
6157956 December 5, 2000 Jensen et al.
6166729 December 26, 2000 Acosta et al.
6167358 December 26, 2000 Othmer et al.
6182142 January 30, 2001 Win et al.
6185316 February 6, 2001 Buffam
6188973 February 13, 2001 Martinez et al.
6215405 April 10, 2001 Handley et al.
6219439 April 17, 2001 Burger
6226031 May 1, 2001 Barraclough et al.
6229429 May 8, 2001 Horon
6233588 May 15, 2001 Marchoili et al.
6239833 May 29, 2001 Ozaki et al.
6243129 June 5, 2001 Deierling
6250452 June 26, 2001 Partyka et al.
6271752 August 7, 2001 Vaios
6271805 August 7, 2001 Yonezawa
6281790 August 28, 2001 Kimmel et al.
6289380 September 11, 2001 Battat et al.
6297746 October 2, 2001 Nakazawa et al.
6298474 October 2, 2001 Blowers et al.
6304857 October 16, 2001 Heindel
6308205 October 23, 2001 Carcerano et al.
6311210 October 30, 2001 Foladare et al.
6314463 November 6, 2001 Abbott et al.
6324647 November 27, 2001 Bowman-Amuah
6356949 March 12, 2002 Katsandres et al.
6362836 March 26, 2002 Shaw et al.
6366686 April 2, 2002 Schroeder et al.
6369695 April 9, 2002 Horon
6393387 May 21, 2002 Adriaans et al.
6412359 July 2, 2002 Zborowski et al.
6429893 August 6, 2002 Xin
6430712 August 6, 2002 Lewis
6430740 August 6, 2002 Hart
6446200 September 3, 2002 Ball et al.
6460141 October 1, 2002 Olden
6483878 November 19, 2002 Yonezawa
6498987 December 24, 2002 Kelly et al.
6499054 December 24, 2002 Hesselink et al.
6504479 January 7, 2003 Lemons et al.
6519540 February 11, 2003 Salandro
6529475 March 4, 2003 Wan et al.
6529936 March 4, 2003 Mayo et al.
6542075 April 1, 2003 Barker et al.
6553336 April 22, 2003 Johnson et al.
6560557 May 6, 2003 Carnahan et al.
6564380 May 13, 2003 Murphy
6567536 May 20, 2003 McNitt et al.
6580451 June 17, 2003 Yonezawa et al.
6583720 June 24, 2003 Quigley
6598090 July 22, 2003 Champlin
6606304 August 12, 2003 Grinter et al.
6611206 August 26, 2003 Eshelman et al.
6625812 September 23, 2003 Abrams et al.
6631271 October 7, 2003 Logan
6646675 November 11, 2003 Tang et al.
6654060 November 25, 2003 Kurosawa et al.
6686838 February 3, 2004 Rezvani et al.
6697103 February 24, 2004 Fernandez et al.
6697341 February 24, 2004 Roy
6698021 February 24, 2004 Amini et al.
6704284 March 9, 2004 Stevenson et al.
6714977 March 30, 2004 Fowler et al.
6721391 April 13, 2004 McClelland et al.
6738811 May 18, 2004 Liang
6741171 May 25, 2004 Palka et al.
6748343 June 8, 2004 Alexander et al.
6748446 June 8, 2004 Sato et al.
6754546 June 22, 2004 Hindus et al.
6839850 January 4, 2005 Campbell et al.
6889264 May 3, 2005 Clough et al.
6891566 May 10, 2005 Marchese
6904458 June 7, 2005 Bishop et al.
6938022 August 30, 2005 Singhal et al.
6947988 September 20, 2005 Saleh
6954701 October 11, 2005 Wolfe
6954859 October 11, 2005 Simerly et al.
6960998 November 1, 2005 Menard et al.
6970167 November 29, 2005 Kumamoto et al.
6970183 November 29, 2005 Monroe
6990591 January 24, 2006 Pearson
7000014 February 14, 2006 Poisson et al.
7003670 February 21, 2006 Heaven et al.
7013334 March 14, 2006 Toyoshima et al.
7035332 April 25, 2006 He et al.
7039205 May 2, 2006 Carter et al.
7053767 May 30, 2006 Petite et al.
7069234 June 27, 2006 Cornelius
7123700 October 17, 2006 Weaver, III et al.
7124427 October 17, 2006 Esbensen
7143153 November 28, 2006 Black et al.
7190292 March 13, 2007 Bizjak
7269625 September 11, 2007 Willhide et al.
7299276 November 20, 2007 Strawn
7627665 December 1, 2009 Barker et al.
20010033330 October 25, 2001 Garoutte
20010034586 October 25, 2001 Ewert et al.
20010034754 October 25, 2001 Elwahab et al.
20020019945 February 14, 2002 Houston et al.
20020029263 March 7, 2002 Toyoshima et al.
20020031230 March 14, 2002 Sweet et al.
20020051061 May 2, 2002 Peters
20020087289 July 4, 2002 Halabieh
20020103898 August 1, 2002 Moyer et al.
20020120727 August 29, 2002 Curley et al.
20020138663 September 26, 2002 Ladwig
20020171551 November 21, 2002 Eshelman et al.
20020188854 December 12, 2002 Heaven et al.
20020191639 December 19, 2002 Norby
20020198990 December 26, 2002 Bradfield et al.
20030131065 July 10, 2003 Neufeld et al.
20030167153 September 4, 2003 Alexander
20030172138 September 11, 2003 McCormack et al.
20040098623 May 20, 2004 Scheidell
20040132432 July 8, 2004 Moores et al.
20050222820 October 6, 2005 Chung
20050248474 November 10, 2005 Wiser et al.
20060041616 February 23, 2006 Ludwig et al.
20060277299 December 7, 2006 Baekelmans et al.
20070150955 June 28, 2007 Murase
20070226796 September 27, 2007 Gilbert
20070296817 December 27, 2007 Ebrahimi et al.
20080091490 April 17, 2008 Abrahams
20080109879 May 8, 2008 Bhagwat
Foreign Patent Documents
0804031 October 1997 EP
0804031 July 2004 EP
1997007486 February 1997 WO
WO 97/07486 February 1997 WO
2001028251 April 2001 WO
WO 01/28251 April 2001 WO
Other references
  • Axis 200+ Web Camera, Axis Communications brochure NE001/US/R2: 15924, 1998, 2 pages.
  • Axis 240 Camera Server, Axis Communications brochure NE002/US/R1: 15925, 1998, 2 pages.
  • Eyecast.com, EyeCast Announces EyeCapture Services, Press Release, Jul. 8, 1998, Sterling, Virginia, www.eyecast.com/news/releases/070898.asp.
  • EyeCast Secures Deals: Security Companies to Use Firm's Off-Site Video Surveillance Technology, Washington Business Journal, Aug. 13-19, 1999, Tech Section, p. 16, www.eyecast.com/news/washbiz.asp, 2 pages.
  • EyeCast.com Adds 360-Degree Continuous Pan Rotation Cameras to it's EyeView Service, Press Release, Mar. 15, 1999, Sterling, Virginia, www.eyecast.com/news/releases/031599.asp, 2 pages.
  • EyeCast.com Announces EyeView Control, Press Release, Oct 12, 1998, Sterling, Virginia, www.eyecast.com/news/releases/101298.asp, 2 pages.
  • EyeCast.com Introduces School/Cast Services for School Safety Officials and Law Enforcement Agencies, Press Release, Apr. 28, 1999, Sterling, Virginia, www.eyecast.com/news/releases/090798.asp, 2 pages.
  • Take a Step into the Future/Digital Security System, www.RemoteCams.com, www.remotecams.com/DISSpage1a.htm; /DISSpage2a.htm; /DISSconfiguration.htm; /DISSsystem.htm, retrieved Sep. 17, 1999, 7 pages.
  • Axis Communications www.axis.se/products/cam-240/, “30 Frames/Second”, printed Sep. 28, 1999, 2 pages.
  • Axis Communications, www.axis.se/products/camera-servers/cam-app-sol.htm, “Network Cameras Applications and Solutions”, printed Sep. 28, 1999, 8 pages.
  • Axis Communications www.axis.se/products/camera-servers/cam-fb.html, “Features and Benefits”, printed Sep. 28, 1993, 3 pages.
  • Bertsch, L.A., Development Tools for Home Automation, IEEE Transactions on Consumer Electronics 36 (4):854-858, Nov. 1990.
  • Corcoran, P.M., and J. Desbonnet, Browser-Style Interfaces to a Home Automation Network, IEEE Transactions on Consumer Electronics 43(4):1063-1069, Nov. 1997.
  • Corcoran, P.M., at al,, User Interface Technologies for Home Appliances and Networks, IEEE Transactions on Consumer Electronics 44(3):689-685, Aug. 1998.
  • Leeb, G., et al., A Configuration Tool for HomeNet, IEEE Transactions on Consumer Electronics 42(3):387-394, Aug. 1996.
  • Muller N.J., Focus on Openview: A Guide to Hewlett-Packard's Network and Systems Management Platforms, CBM Books, Fort Washington, Pennsylvania, 1995, pp. 123-133.
  • Tsai, S.-M., et al., A Service of Home Security on an Intelligent Network, IEEE Transactions on Consumer Electronics 44(4):1360-1366, Nov. 1998.
  • Williams, T., Tools and Protocols Link Embedded Systems Over the Internet, Electronic Design 45(17):91-98, Aug. 18, 1997.
  • EyeCast.com, Inc., Providing Live Interactive Video for Surveillance & Monitoring Over the Internet, 27 pages. (No date).
Patent History
Patent number: RE45649
Type: Grant
Filed: Aug 20, 2012
Date of Patent: Aug 11, 2015
Assignee: Vivint, Inc. (Provo, UT)
Inventors: Karen Grose (Seattle, WA), Christoph Schebel (Suquamish, WA), David Antal (Silverdale, WA), Julie D. Alexander (Portland, OR)
Primary Examiner: Mohamed Charioui
Application Number: 13/590,076
Classifications
Current U.S. Class: Permitting Access (235/382)
International Classification: G06F 11/30 (20060101); G08B 13/00 (20060101);