WO2003103264A1

WO2003103264A1 - Distributed object architecture for security system integration

Info

Publication number: WO2003103264A1
Application number: PCT/US2003/017308
Authority: WO
Inventors: Albert Pan; Henry Jen; Minghwa Li
Original assignee: Ortega Infosystems, Inc.
Priority date: 2002-05-30
Filing date: 2003-05-30
Publication date: 2003-12-11
Also published as: AU2003245379A1

Abstract

A security system (360) is provided to integrate Security System Devices (SSDs) (330) and manage interactions between the SSDs (340a, 340b, 340c, 340d). The security system (360) represents each of a plurality of SSDs (330) with a plurality of Device Object Models (DOMs) (340a, 340b, 340c, 340d). The security system (360) integrates the plurality of SSDs (330) by executing processing logic of the DOMs (340a, 340b, 340c, 340d) within an Integration Applications Server (IAS) (360). The plurality of SSDs can be selectively configured.

Description

DISTRIBUTED OBJECT ARCHITECTURE FOR SECURITY SYSTEM

INTEGRATION

FIELD OF THE INVENTION

[0001] This invention relates to an integrated security system.

More specifically, this invention relates to integrating a plurality of

Security System Devices (SSDs) and managing the interactions between the SSDs.

BACKGROUND OF THE INVENTION

[0002] A security system can use variant Security System Devices

(SSDs), such as Access Control Systems, Closed Circuit Television (CCTV)

Matrix Switch, Pan/Tilt/Zoom (PTZ) Camera, Digital Video Recorder,

Burglar Alarm, and Fire Alarm, etc. It is necessary to integrate variant

SSDs to enhance the performance of the security system. The traditional method to integrate variant SSDs is to hardwire an output of one SSD to an input of another SSD.

[0003] However, the traditional method to integrate variant SSDs has certain disadvantages and limitations. One disadvantage of the traditional method is that the integration of SSDs is limited to a hardwired physical distance.

[0004] Another disadvantage of the traditional method is that a new SSD implementation to an integrated security system is costly and time consuming. The implementation may require a lot of modifications of the integrated security system to integrate the new SSD. [0005] Still another disadvantage of a traditional integrated security system is that the traditional integrated security system is Hmited to perform a simple data flow of input on/off. [0006] Still another disadvantage of the traditional integrated security system is that the traditional integrated security system cannot manage a large scale project with a large number of distributed SSDs. [0007] Therefore, it becomes necessary to provide interactions between the SSDs. It is also necessary to improve the integration of a new SSD into an integrated security system. It is also necessary to improve the managing ability of the integrated security system.

SUMMARY OF THE INVENTION

[0008] A system and method for integrating Security System

Devices (SSDs) and managing interactions between the SSDs is described. In one embodiment of the invention, the system and method comprises representing each of a plurality of SSDs with a plurality of Device Object Models (DOMs), integrating the plurality of SSDs by executing processing logic of the DOMs within an Integration Applications Server (IAS), and selectively configuring the plurality of SSDs. [0009] Other features and advantages of the present invention will be apparent from the accompanying drawings, and from the detailed description, which follows below.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The present invention is illustrated by way of example and not intended to be limited by the figures of the accompanying drawings in which Uke references indicate similar elements and in which:

[0011] Figure 1 is a system diagram of one embodiment of an integrated security system.

[0012] Figure 2 is a diagram illustrating one embodiment of a basic partition of a security system device object model.

[0013] Figure 3 is a diagram illustrating one embodiment of interface partitions.

[0014] Figure 4 is a diagram illustrating one embodiment of basic modules for an Integration Application Server.

[0015] Figure 5 is a flow diagram illustrating one embodiment of relaying a command within an integrated security system.

[0016] Figure 6 is a flow diagram illustrating one embodiment of updating a security system device status.

[0017] Figure 7 is a diagram of a flow chart page of defining processing logic of an integrated security system. [0018] Figure 8 is a diagram of a system layout page of a graphical user interface.

DETAILED DESCRIPTION

[0019] A method and apparatus for integrating Security System

Devices (SSDs) and managing interactions between the SSDs is described. In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, functional, and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims. [0020] Figure 1 is a system diagram of one embodiment of an integrated security system. Referring to Figure 1, an integrated security system 100 includes a plurality of Security System Devices (SSDs) 110. In one embodiment, the SSD 110 is an Access Control System. In another embodiment, the SSD 110 can be a CCTV Matrix Switch, a Pan/Tilt/Zoom (PTZ) Camera, a Digital Video Recorder, a Burglar Alarm System, etc. It will be apparent to one of ordinary skill in the art that many conventional types of system devices may be used as SSDs 110 with the present invention. The SSDs 110 are connected with remote computers. Referring to Figure 1, two remote computers 120A and 120B are connected with the SSDs 110, but the invention is not so limited. The SSDs 110 may be connected with only one remote computer or as many remote computers as necessary. Each of the SSDs 110 may be connected with only one remote computer or more than one remote computer. [0021] Referring to Figure 1, the remote computers 120A and 120B are connected with an Integration Application Server (IAS) 140 via a conventional data network, such as one using the well-known Transmission Control Protocol/Internet Protocol (TCP/IP), so that the IAS 140 and the remote computer 120A and 120B can communicate with each other via an Internet connection. In another embodiment, the IAS 140 can be connected with one remote computer or as many remote computers as necessary. The IAS 140 is connected with network users via TCP/IP network. In one embodiment, the IAS 140 is connected with network users 160A and 160B via TCP/IP network 150 so that the IAS 140 and the network users 160A and 160B can communicate with each other, but the invention is not so limited. The IAS 140 can be connected with only one network user or as many network users as necessary. [0022] Still referring to Figure 1, the integrated security system 100 can execute certain commands and update SSD statuses. In one embodiment, a command is sent from the network user 160 A to the IAS 140 via the TCP/IP network 150. The IAS 140 relays the command to the remote computer 120A via the TCP/IP network 130. The remote computer 120A then relays the command to the SSD 110. In another embodiment, a SSD status update is sent from the remote computer 120A to the IAS 140 via the TCP/IP network 130. The IAS 140 may notify the status update to the network user 160A. In one embodiment, the IAS 140 executes processing logic to manage the interactions between the SSDs. In another embodiment, the remote computer 120A can execute the processing logic based on the network user 160A's configuration. In one embodiment, each SSD 110 is represented by a plurality of Device Object Models (DOMs). When the SSD is represented by the DOMs, the security system can process the DOMs and provide a consistent method to manage event alarms for different SSDs instead of addressing the different SSDs respectively. In another embodiment, the network user can selectively configure the SSDs 110 based on an event trigger condition. In one embodiment, the DOMs can represent a physical SSD, such as door, camera, sensor, relay output, etc. In another embodiment, the DOM can also represent logic events from the SSDs 110, such as alarm, logical process output, etc. Thus, the integrated security system 100 can increase and enhance integration features between SSDs. The detailed description that follows illustrates the method to enhance and manage the interactions between the SSDs.

[0023] Figure 2 is a diagram illustrating one embodiment of a basic partition of the security system device object model. As discussed above, the SSD is represented by one or a plurality of DOMs. In one embodiment, the SSD is represented by a Device Control Object 220A, a Device Logic Object 240A, and a Device Graphical User Interface (GUI) Object 260A. The Device Control Object 220A can provide a remote computer 220 an interface with the SSD, collect statuses of the SSD, and relay commands to the SSD. When the security system deals with a large number of network transactions (e.g. status update), the Device Control Object 220A can be configured to aggregate the multiple network transactions into one transaction. The aggregation period can be configured based on a response time requirement and an available network bandwidth.

[0024] In one embodiment, the Device Logic Object 240A is run within an IAS 240. In another embodiment, the Device Logic Object 240A can be run on any computers that are appropriate and physically close to an integrated security system 200. Referring to Figure 2, the IAS 240 provides a framework to interact and communicate with the Device Logic Object 240A. In one embodiment, the Device Logic Object 240A maintains and caches current SSD statuses. In addition, the IAS 240 can execute processing logic of SSDs and update the Device Control Object 220A based on a new network user's selection. Furthermore, the IAS 240 can detect and monitor the Device Control Object 220A and provide event alarm information to the network user 260. The detailed description of Figures 4-6 illustrates the method and function of the IAS 240. [0025] In one embodiment, the Device GUI Object 260A can provide an interface for a network user 260. The Device GUI Object 260A can be dragged and dropped by a mouse or other conventional control device based on a configuration of the network user 260. In another embodiment, the Device GUI Object 260A is downloaded to an Internet browser page. The Device GUI Object 260A also presents an SSD status and accepts commands from the network user 260 to the SSD. [0026] Figure 3 is a diagram illustrating one embodiment of interface partitions. In one embodiment, the integrated security system 300 includes an interface 330 to SSDs and an interface 350 to a DOM platform. In one emboclim.ent, the interface 330 provides an interface between each SSD and each Device Control Object, for example, between Access Control System 320A and Device Control Object 340A, between CCTV Matrix Switch 320B and Device Control Object 340B, between Digital Video Recorder 320C and Device Control Object 340C, between Burglar Alarm System 320D and Device Control Object 340D, etc. The interface 350 provides an interface between an integrated security system framework 360 and the Device Control Object 340A, 340B, 340C, and 340D. When a new SSD is integrated into the security system 300, only the interface 350 to DOM platform is modified to incorporate the new SSD. The integrated Security System framework 360 is not to be modified. Thus, the integration ability of the integrated security system 300 is enhanced.

[0027] Referring to Figure 4, an IAS 440 includes some basic modules to execute processing logic of an SSD. In one embodiment, the LAS 440 includes a Device Logic Object Module 440A, a Rule Module 440B, an Event Alarm Module 440C, an Action Dispatching Module 440D, and a System Diagnosis and Recovery Module 440E, but the invention is not so limited, the IAS 440 can include as few or as many modules as long as the IAS 440 can manage interactions between the SSDs efficiently. For exemplary purposes, some functions of the modules are described. The Device Logic Object Module 440A can store and cache SSD statuses and interpret SSD actions. The Rule Module 440B can define logic processing rules, subscribe status update notification from Device Logic Objects, and execute rules based on the SSD status update. The Event Alarm 440C can define event alarm profiles, subscribe status update notification from Device Logic Objects, notify event alarm instances, and manage event alarm acknowledge. The Action Dispatching Module 440D can relay and dispatch the SSD actions to remote Device Control Objects. The System Diagnosis and Recovery Module 440E can monitor the status of Device Control Objects, and automatically cure malfunctions of the integrated security system.

[0028] Figure 5 is a flow diagram illustrating one embodiment of relaying a command within an integrated security system. At processing block 510, the processing logic issues a command from a Device GUI object. At processing block 520, processing logic transmits the command to an Action Dispatch Module. At processing block 530, processing logic relays the command to a Device Control Object. At processing block 540, processing logic relays the command from the Device Control Object to a physical SSD. Thus, the command can be relayed from a network user to the SSD.

[0029] Figure 6 is a flow diagram illustration and embodiment of updating an SSD status. At processing block 610, processing logic informs a first SSD status update to a first Device Control Object. At processing block 620_> processing logic reports the status update information to a Device Logic Object. At processing block 630, processing logic executes certain logic rules according to a Rule Module defined for the first SSD. At processing block 640, the Action Dispatching Module transmits the execution to a second SSD Device Control Object. At processing block 650, the Event Alarm Module executes an event modification. At processing block 660, the device Logic Objects notifies the Device GUI Object to present the status update. Therefore, a network user can be informed of an SSD status update.

[0030] In one embodiment, the processing logic is executed within an LAS. In another embodiment, the processing logic can be executed within a remote computer based on a network user's configuration. [0031] Figure 7 is a diagram of a flow chart page of defining logic rules and processing logic of an integrated security system. In particular, flow chart 720 illustrates processing logic of the integrated security system. Rule list 740 allows a network user to add, modify, delete, and copy logic rules. In one embodiment, the integrated security system can be automatically published on an Internet WEB Server and be presented in a graphical user interface (GUI) running on top of a conventional browser such as Microsoft Internet Explorer. [0032] Figure 8 is a diagram of a system layout page of a graphical user interface (GUI). In particular, an overview 820 of a monitored structure is displayed. A network user can drag and drop an SSD from a Device Catalog 840 to a floor map-window 850. Thus, the network user can selectively configure the integrated security system by mouse drag and drop.

[0033] In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

Claims

CLAIMSWhat is claimed is:

1. An apparatus comprising:

a plurality of Security System Devices (SSDs); and

an Integration Application Server (IAS) to integrate the plurality of

SSDs, wherein the IAS executes processing logic to manage interactions

between the SSDs, the IAS being connectable with a network user, wherein

the network user may selectively configure the plurality of SSDs.

2. The apparatus of claim 1, further comprising a remote computer to

execute the processing logic based on a configuration of the network user.

3. The apparatus of claim 1, wherein the SSD is represented by a

plurality of Device Object Models (DOMs).

4. The apparatus of claim 3, wherein the DOM represents logical security

alarms and events.

5. The apparatus of claim 3, wherein the DOM represents physical SSDs.

6. The apparatus of claim 1, wherein the IAS provides event alarm

information to the network user.

7. The apparatus of claim 1, wherein the SSD includes Access Control

System, Closed Circuit Television (CCTV) Matrix Switch, Pan/Tilt/Zoom

Camera, Digital Video Recorder, Burglar Alarm, and Fire Alarm.

8. The apparatus of claim 1, wherein the network user includes a single

graphical user interface.

9. The apparatus of claim 1, wherein the network user selectively

configures the SSD by mouse drag and drop.

10. A method comprising:

representing each of a plurality of Security System Devices (SSDs)

with a plurality of Device Object Models (DOMs); integrating the plurality of SSDs by executing processing logic of the

DOMs within an Integration Applications Server (IAS); and

selectively configuring the plurality of SSDs.

11. The method of claim 10, further comprising executing the processing

logic within a remote computer based on a configuration of a network user.

12. The method of claim 10, wherein the DOM represents logical security

alarms and events.

13. The method of claim 10, wherein the DOM represents physical SSDs.

14. The method of claim 10, wherein the IAS provides event alarm

information to a network user.

15. The method of claim 10, wherein the SSD includes Access Control

System, CCTV Matrix Switch, Pan/Tilt/Zoom Camera, Digital Video

Recorder, Burglar Alarm, and Fire Alarm.

16. The method of claim 10, wherein selectively configuring includes

using mouse drag and drop.

17. An integrated security system comprising:

means for representing each of a plurality of Security System Devices

(SSDs) with a plurality of Device Object Models (DOMs);

means for integrating the plurality of SSDs using the DOMs; and

means for selectively configuring the plurality of SSDs.

18. The integrated security system of claim 17, wherein the means for

integrating includes means for executing processing logic within an

Integration Application Server (IAS).

19. The integrated security system of claim 17, wherein the means for

integrating includes means for executing processing logic within a remote

computer based on a configuration of a network user.

20. The integrated security system of claim 17, wherein the DOM

represents physical SSDs and logical security alarms and events.

21. The integrated security system of claim 17, wherein the SSD includes

Access Control System, CCTV Matrix Switch, Pan/Tilt/Zoom Camera,

Digital Video Decoder, Burglar Alarm, and Fire Alarm.

22. The integrated security system of claim 17, further comprising a

network user providing a single graphical user interface.

23. A computer readable medium containing executable instruction

which, when executed in the process system, causes the system to perform a

method for managing a security system, the method comprising:

representing each of a plurality of Security System Devices (SSDs)

with a plurality of Device Object Model (DOMs);

integrating the plurality of SSDs by executing processing logic of the

DOMs within an Integration Applications Server (IAS); and

selectively configuring the plurality of SSDs.

24. The computer readable medium of claim 23, further comprising

executing the processing logic within a remote computer based on a

configuration of a network user.

25. The computer readable medium of claim 23, wherein the DOM

represents physical SSDs and logical security alarms and events.

26. The computer readable medium of claim 23, wherein the SSD includes

Access Control System, CCTV Matrix Switch, Pan/Tilt/Zoom Camera,

Digital Video Recorder, Burglar Alarm, and Fire Alarm.

27. The computer readable medium of claim 23, wherein selectively

configuring includes using mouse drag and drop.

28. A method for a status update, the method comprising:

informing a status data of a first Security System Device (SSD) to an

Integration Application Server (IAS);

executing processing logic within the IAS according to a logic rule

defined for the first SSD; and notifying the processing logic to a second SSD.

29. The method of claim 28, further comprising presenting the status

update in a graphical user interface.

30. The method of claim 28, wherein the SSD includes Access Control

System, CCTV Matrix Switch, Pan/Tilt/Zoom Camera, Digital Video

Recorder, Burglar Alarm, and Fire Alarm.