WO2003103264A1 - Architecture a objets distribues conçu pour l'integration d'un systeme de securite - Google Patents
Architecture a objets distribues conçu pour l'integration d'un systeme de securite Download PDFInfo
- Publication number
- WO2003103264A1 WO2003103264A1 PCT/US2003/017308 US0317308W WO03103264A1 WO 2003103264 A1 WO2003103264 A1 WO 2003103264A1 US 0317308 W US0317308 W US 0317308W WO 03103264 A1 WO03103264 A1 WO 03103264A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ssds
- security system
- ssd
- ias
- processing logic
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
- G08B25/14—Central alarm receiver or annunciator arrangements
Definitions
- This invention relates to an integrated security system.
- this invention relates to integrating a plurality of
- SSDs Security System Devices
- a security system can use variant Security System Devices
- SSDs such as Access Control Systems, Closed Circuit Television (CCTV)
- CCTV Closed Circuit Television
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- DOMs Device Object Models
- IAS Integration Applications Server
- Figure 1 is a system diagram of one embodiment of an integrated security system.
- Figure 2 is a diagram illustrating one embodiment of a basic partition of a security system device object model.
- Figure 3 is a diagram illustrating one embodiment of interface partitions.
- Figure 4 is a diagram illustrating one embodiment of basic modules for an Integration Application Server.
- Figure 5 is a flow diagram illustrating one embodiment of relaying a command within an integrated security system.
- Figure 6 is a flow diagram illustrating one embodiment of updating a security system device status.
- Figure 7 is a diagram of a flow chart page of defining processing logic of an integrated security system.
- Figure 8 is a diagram of a system layout page of a graphical user interface.
- FIG. 1 is a system diagram of one embodiment of an integrated security system.
- an integrated security system 100 includes a plurality of Security System Devices (SSDs) 110.
- the SSD 110 is an Access Control System.
- 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.
- 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.
- 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.
- 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.
- the integrated security system 100 can execute certain commands and update SSD statuses.
- 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.
- 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.
- the IAS 140 executes processing logic to manage the interactions between the SSDs.
- the remote computer 120A can execute the processing logic based on the network user 160A's configuration.
- each SSD 110 is represented by a plurality of Device Object Models (DOMs).
- DOMs Device Object Models
- 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.
- the network user can selectively configure the SSDs 110 based on an event trigger condition.
- the DOMs can represent a physical SSD, such as door, camera, sensor, relay output, etc.
- the DOM can also represent logic events from the SSDs 110, such as alarm, logical process output, etc.
- 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.
- FIG. 2 is a diagram illustrating one embodiment of a basic partition of the security system device object model.
- the SSD is represented by one or a plurality of DOMs.
- 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.
- 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.
- 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.
- the IAS 240 provides a framework to interact and communicate with the Device Logic Object 240A.
- the Device Logic Object 240A maintains and caches current SSD statuses.
- the IAS 240 can execute processing logic of SSDs and update the Device Control Object 220A based on a new network user's selection.
- the IAS 240 can detect and monitor the Device Control Object 220A and provide event alarm information to the network user 260.
- 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.
- 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.
- Figure 3 is a diagram illustrating one embodiment of interface partitions.
- the integrated security system 300 includes an interface 330 to SSDs and an interface 350 to a DOM platform.
- 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.
- an IAS 440 includes some basic modules to execute processing logic of an SSD.
- 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.
- FIG. 5 is a flow diagram illustrating one embodiment of relaying a command within an integrated security system.
- the processing logic issues a command from a Device GUI object.
- processing logic transmits the command to an Action Dispatch Module.
- processing logic relays the command to a Device Control Object.
- 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.
- FIG. 6 is a flow diagram illustration and embodiment of updating an SSD status.
- processing logic informs a first SSD status update to a first Device Control Object.
- processing logic reports the status update information to a Device Logic Object.
- processing logic executes certain logic rules according to a Rule Module defined for the first SSD.
- the Action Dispatching Module transmits the execution to a second SSD Device Control Object.
- the Event Alarm Module executes an event modification.
- 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.
- FIG. 7 is a diagram of a flow chart page of defining logic rules and processing logic of an integrated security system.
- 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.
- 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.
- GUI graphical user interface
- 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.
Landscapes
- Business, Economics & Management (AREA)
- Emergency Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Alarm Systems (AREA)
Abstract
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003245379A AU2003245379A1 (en) | 2002-05-30 | 2003-05-30 | Distributed object architecture for security system integration |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16013202A | 2002-05-30 | 2002-05-30 | |
US10/160,132 | 2002-05-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003103264A1 true WO2003103264A1 (fr) | 2003-12-11 |
Family
ID=29709700
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/017308 WO2003103264A1 (fr) | 2002-05-30 | 2003-05-30 | Architecture a objets distribues conçu pour l'integration d'un systeme de securite |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2003245379A1 (fr) |
WO (1) | WO2003103264A1 (fr) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1659470A2 (fr) * | 2004-11-17 | 2006-05-24 | Rockwell Automation Technologies, Inc. | Systèmes et procédés de notification à plusieurs hôtes à partir d'un automate industriel |
SG131103A1 (en) * | 2005-09-30 | 2007-04-26 | Rockwell Automation Tech Inc | Hybrid user interface having base presentation information with variably prominent supplemental information |
US7721273B1 (en) | 2003-11-17 | 2010-05-18 | Rockwell Automation Technologies, Inc. | Controller equipment model systems and methods |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5134644A (en) * | 1990-08-17 | 1992-07-28 | Senses International | Data communication device |
US5568535A (en) * | 1992-06-01 | 1996-10-22 | Trackmobile, Inc. | Alarm system for enclosed area |
US5943394A (en) * | 1998-03-19 | 1999-08-24 | Detection Systems, Inc. | Event detection system with dialer intercept |
US5977871A (en) * | 1997-02-13 | 1999-11-02 | Avr Group Limited | Alarm reporting system |
US6104785A (en) * | 1999-01-20 | 2000-08-15 | Tempa Communication Inc. | Subscriber control unit for united home security system |
US6134303A (en) * | 1999-01-20 | 2000-10-17 | Tempa Communication Inc. | United home security system |
US6209101B1 (en) * | 1998-07-17 | 2001-03-27 | Secure Computing Corporation | Adaptive security system having a hierarchy of security servers |
US6580950B1 (en) * | 2000-04-28 | 2003-06-17 | Echelon Corporation | Internet based home communications system |
-
2003
- 2003-05-30 AU AU2003245379A patent/AU2003245379A1/en not_active Abandoned
- 2003-05-30 WO PCT/US2003/017308 patent/WO2003103264A1/fr not_active Application Discontinuation
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5134644A (en) * | 1990-08-17 | 1992-07-28 | Senses International | Data communication device |
US5568535A (en) * | 1992-06-01 | 1996-10-22 | Trackmobile, Inc. | Alarm system for enclosed area |
US5977871A (en) * | 1997-02-13 | 1999-11-02 | Avr Group Limited | Alarm reporting system |
US5943394A (en) * | 1998-03-19 | 1999-08-24 | Detection Systems, Inc. | Event detection system with dialer intercept |
US6209101B1 (en) * | 1998-07-17 | 2001-03-27 | Secure Computing Corporation | Adaptive security system having a hierarchy of security servers |
US6104785A (en) * | 1999-01-20 | 2000-08-15 | Tempa Communication Inc. | Subscriber control unit for united home security system |
US6134303A (en) * | 1999-01-20 | 2000-10-17 | Tempa Communication Inc. | United home security system |
US6580950B1 (en) * | 2000-04-28 | 2003-06-17 | Echelon Corporation | Internet based home communications system |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7721273B1 (en) | 2003-11-17 | 2010-05-18 | Rockwell Automation Technologies, Inc. | Controller equipment model systems and methods |
US8150959B1 (en) | 2003-11-17 | 2012-04-03 | Rockwell Automation Technologies, Inc. | Systems and methods for notifying multiple hosts from an industrial controller |
US8803667B2 (en) | 2003-11-17 | 2014-08-12 | Rockwell Automation Technologies, Inc. | Systems and methods for notifying multiple hosts from an industrial controller |
EP1659470A2 (fr) * | 2004-11-17 | 2006-05-24 | Rockwell Automation Technologies, Inc. | Systèmes et procédés de notification à plusieurs hôtes à partir d'un automate industriel |
EP1659470A3 (fr) * | 2004-11-17 | 2006-12-27 | Rockwell Automation Technologies, Inc. | Systèmes et procédés de notification à plusieurs hôtes à partir d'un automate industriel |
SG131103A1 (en) * | 2005-09-30 | 2007-04-26 | Rockwell Automation Tech Inc | Hybrid user interface having base presentation information with variably prominent supplemental information |
US7962229B2 (en) | 2005-09-30 | 2011-06-14 | Rockwell Automation Technologies, Inc. | Hybrid user interface having base presentation information with variably prominent supplemental information |
Also Published As
Publication number | Publication date |
---|---|
AU2003245379A1 (en) | 2003-12-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10650593B2 (en) | Holographic technology implemented security solution | |
US9984545B2 (en) | System and method of monitoring the video surveillance activities | |
US10613728B2 (en) | System and method for virtual region based access control operations using BIM | |
US8489065B2 (en) | Mobile device controller application for any security system | |
US20060179463A1 (en) | Remote surveillance | |
US20070226616A1 (en) | Method and System For Wide Area Security Monitoring, Sensor Management and Situational Awareness | |
EP1759304A2 (fr) | Procede et systeme du surveillance de la securite, de gestion des detecteurs et de connaissance de la situation dans des zones etendues | |
US20090002492A1 (en) | Method and system for spatio-temporal event detection using composite definitions for camera systems | |
US10541892B2 (en) | System and method for monitoring, sensing and analytics of collaboration devices | |
JP2009539182A (ja) | リモートサイトの分散監視のためのシステム及び方法 | |
WO2014089882A1 (fr) | Système d'écran publicitaire à led basé sur un service en nuage, et procédé de surveillance intelligent correspondant | |
CA2914597A1 (fr) | Systeme et methode de visualisation interactive d'une alarme contextuelle en format image et video | |
CN107211040A (zh) | 动态并自动创建用户界面的方法 | |
CN115578067A (zh) | 基于数字孪生的物流园区可视化管理方法及系统、设备 | |
US11785186B2 (en) | Centralized monitoring of confined spaces | |
WO2003103264A1 (fr) | Architecture a objets distribues conçu pour l'integration d'un systeme de securite | |
US7496212B2 (en) | Change detecting method and apparatus | |
US11985447B1 (en) | Analytics pipeline management systems for local analytics devices and remote server analytics engines | |
US12056005B2 (en) | Apparatus and method for detecting and correcting failures in kiosks and informational displays | |
EP3065398B1 (fr) | Dispositions dynamiques | |
JP2000151823A (ja) | ビル遠隔管理装置 | |
JP2019120998A (ja) | 制御システムおよび制御装置 | |
Musharaf Hussain et al. | IoT based smart human traffic monitoring system using raspberry Pi | |
KR102190658B1 (ko) | 텍스트에 기반하여 비디오를 검색하기 위한 전자 장치 및 방법 | |
JPH1117678A (ja) | 網管理装置の遠隔操作方式 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |