Multipurpose Interface and Control System

• US 20060288101A1
• Filed: 06/01/2006
• Published: 12/21/2006
• Est. Priority Date: 08/19/2003
• Status: Abandoned Application

• Current Assignee: Key Systems Incorporated
• Original Assignee: Key Systems Incorporated
• Inventors: Anton, Robert, Morley, Benjamin, Mastrodonato, George, Rockwell, Thomas, Arrow, James, Eckerdt, George
• Application Number:
  US11/421,635
• Publication Number:
  US 20060288101A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

A multipurpose interface and control system includes a managing and/or monitoring device (an “effectuator”) capable of monitoring parameter(s) and/or controlling function(s) of an apparatus, and a server system coupled to a communication medium, where the server system allows the effectuator (and via it the apparatus it monitors and/or controls) to be accessed remotely via the communication medium. The communication medium allows the effectuator to be accessed from remote locations by other devices capable of accessing the communications medium and thereby accessing the effectuator(s). The communications medium can take numerous forms, such as a direct connection, ethernet connection, internet connection, intranet connection, and/or phone connection. Preferably, the system includes at least one remote device capable of communicating with at least one effectuator via the communications medium (generally a network). The remote network enabled device(s) can include at least one of: telephones, computers, PDAs, and Kiosks. Further, the web server based firmware of the system ideally allows programming of the effectuator via the remote network enabled device(s) without software other than said server based firmware. However, software based in computer(s) constituting at least one of the web enabled device(s) can also be used to manage said effectuator(s).

Claims

9-1. A system as described in claim 46, wherein CRC checksums are used in relation to the database to create a check sum field in each record that compares all the field contents of the current record with all the field contents of the previous record to prevent tampering with the database.

39. A system for monitoring and/or control, comprising:

a) at least one system effectuator for at least one of monitoring and controlling an apparatus, said at least one system effectuator including a server system coupled to a communications medium, wherein the server system is capable of storing programs related to operations of the at least one system effectuator and allows the at least one system effectuator to be accessed remotely via said communications medium;

b) at least one remote device capable of accessing said at least one system effectuator via the communications medium and the server system so as to at least one of;

monitor and control said apparatus via said effectuator;

c) wherein said server system includes server based firmware allowing at least one of programming and reprogramming of the system effectuator via said at least one remote device; and

d) wherein said apparatus is at least one of;

an access control apparatus, a sensor apparatus, and a system control apparatus.

1. A system for monitoring and/or control, comprising:

at least one system effectuator for at least one of monitoring and controlling an apparatus, said at least one system effectuator including a server system coupled to a communications medium, wherein the server system is capable of storing programs related to operations of the at least one system effectuator and allows the at least one system effectuator to be accessed remotely via said communications medium.

2. The system of claim 1, further comprising at least one remote device capable of accessing said at least one system effectuator via the communications medium and the server system so as to at least one of:

monitor and control said apparatus via said effectuator.

3. A system as described in claim 1, wherein said server system includes server based firmware allowing at least one of programming and reprogramming of the system effectuator via an at least one remote device.

4. A system as described in claim 1, wherein said communications medium is a network.

5. A system as described in claim 1, wherein said communications medium is at least one of:

internet, intranet, direct connection, ethernet connection, and phone connection.

6. A system as described in claim 2, wherein said at least one remote device capable of accessing said at least one system effectuator is at least one of a:

computer, PDA, telephone, pager, and kiosk.

7. A system as described in claim 2, wherein said at least one effectuator further includes an XML interface, which XML interface at least one of:

facilitates transfer of information in the at least one effectuator to said at least one remote device, and facilitates programming of the at least one effectuator by the at least one remote device.

8. A system as described in claim 2, further including software of a remote device for at least one of programming and reprogramming at least one of said firmware and said effectuator.

9. A system as described in claim 7, further including software of a remote device for at least one of programming and reprogramming at least one of said firmware and said effectuator.

10. A system as described in claim 1, wherein said apparatus is at least one of:

an access control apparatus, a sensor apparatus, and a system control apparatus.

11. A system as described in claim 10, wherein any such access control apparatus is an ingress/egress control apparatus.

12. A system as described in claim 7, further including a database, which database stores at least one of:

effectuator event information, effectuator command information, and system configuration information.

13. A system as described in claim 8, further including a database, which database stores at least one of:

effectuator event information, effectuator command information, and system configuration information.

14. A system as described in claim 9, further including a database, which database stores at least one of:

effectuator event information, effectuator command information, and system configuration information.

15. A system as described in claim 3, wherein said firmware allows the said at least one remote device to interact with said at least one effectuator to at least one of:

reprogram said at least one effectuator, obtain status reports and warnings related to operations of at least one of an effectuator and an apparatus, download transaction history related to at least one of an effectuator and an apparatus, establish or change user access criteria, and make and change rules related to an apparatus.

16. A system as described in claim 3, wherein said firmware allows a user to write or re-write rules governing operation of an apparatus of the at least one effectuator via a rules engine.

17. A system as described in claim 16, wherein said rules engine comprises at least one of a rule generation user interface, a rule parser and compiler, and a rule execution engine.

18. A system as described in claim 17, wherein any said rule generation user interface generates computer screens and forms that allow a user to add, edit or delete a rule.

19. A system as described in claim 17, wherein any said rule parser and compiler can receive a rule string and transform the string into a format that is most efficient for the rules execution engine.

20. A system as described in claim 17, wherein any said rules execution engine is responsible for execution of the rule.

21. A system as described in claim 17, wherein rules can be written or re-written by a user of the effectuator at runtime.

22. A system as described in claim 16, wherein a rule includes a rule name and a rule action and can also include at least one of a rule condition, rule action false, and rule action true statements.

23. A system as described in claim 16, wherein a common rule may be shared by other rules.

24. A system as described in claim 8, wherein said software enables a user at the remote device to at least one of:

perform effectuator asset audits, perform effectuator alarm audits, monitor and respond to events from an at least one effectuator, and obtain data from an effectuator related to at least one of asset status, alarm status, and hardware status.

25. A system as described in claim 8, wherein some portion of communication between an at least one effectuator and the at least one remote device can be at least one of password authenticated and encrypted.

26. A system as described in claim 25, wherein any such password can also be encrypted.

27. A system as described in claim 25, wherein encryption algorithms make use of a shared key that changes with each connection between the at least one effectuator and the at least one remote device.

28. A system as described in claim 1, wherein the system maintains live connection between the at least one effectuator and the at least one remote device with real-time command/event processing instead of polling.

29. A system as described in claim 8, wherein said software is capable of managing a plurality of effectuators.

30. A system as described in claim 29, wherein said software is capable of presenting maps of all effectuators that are part of the system, with representative icons on the maps that show where at least one of an effectuator and an apparatus is located.

31. A system as described in claim 30, wherein clicking on an icon on a map will produce at least one of a more localized map with icons, and a status screen displaying status of at least one of an effectuator and an apparatus at the icon location on the last map produced.

32. A system as described in claim 30, where a characteristic of an icon indicates status of at least one of an effectuator and an apparatus.

33. A system as described in claim 32, where said characteristic is icon color.

34. A system as described in claim 13, wherein CRC checksums are used in relation to the database to create a check sum field in each record that compares all the field contents of the current record with all the field contents of the previous record to prevent tampering with the database.

35. A system as described in claim 1, wherein said at least one effectuator is supplied with power via a Power Over Ethernet (POE) standard cable.

36. A system as described in claim 1, wherein ethernet cable is used for both communications and to provide power to at least one of the at least one effectuator and the at least one apparatus.

37. A system as described in claim 1, wherein said at least one apparatuses includes a lockbox, which lock box uses a solenoid pin as an emergency release mechanism.

38. A system as described in claim 37, wherein a said lockbox has a latch member for latching a lock box opening member closed, said latch member has a lock box frame connection portion whereby it is connected to the lock box frame via a solenoid pin that can be withdrawn to release the latch member from its connection to the lock box and allow opening of the lockbox.

40. A system as described in claim 39, wherein said communications medium is a network.

41. A system as described in claim 39, wherein said communications medium is at least one of:

internet, intranet, direct connection, ethernet connection, and phone connection.

42. A system as described in claim 39, wherein said at least one remote device capable of accessing said at least one system effectuator is at least one of a:

computer, PDA, telephone, pager, and kiosk.

43. A system as described in claim 39, wherein said at least one effectuator further includes an XML interface, which XML interface at least one of:

facilitates transfer of information in the at least one effectuator to said at least one remote device, and facilitates programming of the at least one effectuator by the at least one remote device.

44. A system as described in claim 43, further including software of a remote device for at least one of programming and reprogramming at least one of said firmware and said effectuator.

45. A system as described in claim 39, wherein any such access control apparatus is an ingress/egress control apparatus.

46. A system as described in claim 44, further including a database, which database stores at least one of:

effectuator event information, effectuator command information, and system configuration information.

47. A system as described in claim 39, wherein said firmware allows the said at least one remote device to interact with said at least one effectuator to at least one of:

reprogram said at least one effectuator, obtain status reports and warnings related to operations of at least one of an effectuator and an apparatus, download transaction history related to at least one of an effectuator and an apparatus, establish or change user access criteria, and make and change rules related to an apparatus.

48. A system as described in claim 39, wherein said firmware allows a user to write or re-write rules governing operation of an apparatus of the at least one effectuator via a rules engine.

49. A system as described in claim 48, wherein said rules engine comprises:

at least one of a rule generation user interface, a rule parser and compiler, and a rule execution engine;

wherein any said rule generation user interface generates computer screens and forms that allow a user to add, edit or delete a rule;

wherein any said rule parser and compiler can receive a rule string and transform the string into a format that is most efficient for the rules execution engine; and

wherein any said rules execution engine is responsible for execution of the rule.

50. A system as described in claim 48, wherein rules can be written or re-written by a user of the effectuator at runtime.

51. A system as described in claim 48, wherein a common rule may be shared by other rules.

52. A system as described in claim 44, wherein said software enables a user at the remote device to at least one of:

perform effectuator asset audits, perform effectuator alarm audits, monitor and respond to events from an at least one effectuator, and obtain data from an effectuator related to at least one of asset status, alarm status, and hardware status.

53. A system as described in claim 39, wherein some portion of communication between an at least one effectuator and the at least one remote device can be at least one of password authenticated and encrypted.

54. A system as described in claim 53, wherein any such password can also be encrypted.

55. A system as described in claim 53, wherein encryption algorithms make use of a shared key that changes with each connection between the at least one effectuator and the at least one remote device.

56. A system as described in claim 39, wherein the system maintains live connection between the at least one effectuator and the at least one remote device with real-time command/event processing instead of polling.

57. A system as described in claim 44, wherein said software is capable of presenting maps of all effectuators that are part of the system, with representative icons on the maps that show where at least one of an effectuator and an apparatus is located, and wherein clicking on an icon on a map will produce at least one of a more localized map with icons, and a status screen displaying status of at least one of an effectuator and an apparatus at the icon location on the last map produced.

58. A system as described in claim 57, where a characteristic of an icon indicates status of at least one of an effectuator and an apparatus.

60. A system as described in claim 1, wherein an effectuator is supplied with power via a Power Over Ethernet (POE) standard cable and wherein said cable is used for both communications and to provide power to at least one of the effectuator and an apparatus.

61. A system as described in claim 39, wherein a said lockbox has a latch member for latching a lock box opening member closed, said latch member has a lock box frame connection portion whereby it is connected to the lock box frame via a solenoid pin that can be withdrawn to release the latch member from its connection to the lock box and allow opening of the lockbox.

81. A system as described in claim 1, further including a Zigbee Network connecting apparatuses to each other and to an effectuator.

82. A system as described in claim 39, further including a Zigbee Network connecting apparatuses to each other and to an effectuator.

84. A system as described in claim 1, wherein at least one interface page of the firmware can be accessed by a remote device via the communications medium using only a browser.

62. A system for monitoring and/or control, comprising:

a) at least one system effectuator for at least one of monitoring and controlling an apparatus, said at least one system effectuator including a server system coupled to a communications medium, wherein the server system is capable of storing programs related to operations of the at least one system effectuator and allows the at least one system effectuator to be accessed remotely via said communications medium;

b) at least one remote device capable of accessing said at least one system effectuator via the communications medium and the server system so as to at least one of;

monitor and control said apparatus via said effectuator;

c) wherein said server system includes server based firmware allowing at least one of programming and reprogramming of the system effectuator via said at least one remote device; and

d) wherein said apparatus is at least one of;

an access control apparatus, a sensor apparatus, and a system control apparatus; and

e) wherein at least one effectuator is supplied with power via a Power Over Ethernet (POE) standard cable and said cable is used for both communications and to provide power to at least one of the effectuator and an apparatus.

63. A system as described in claim 62, wherein said communications medium is a network.

64. A system as described in claim 63, wherein said at least one remote device capable of accessing said at least one system effectuator is at least one of a:

computer, PDA, telephone, pager, and kiosk.

65. A system as described in claim 64, wherein said at least one effectuator further includes an XML interface, which XML interface at least one of:

facilitates transfer of information in the at least one effectuator to said at least one remote device, and facilitates programming of the at least one effectuator by the at least one remote device.

66. A system as described in claim 65, further including software of a remote device for at least one of programming and reprogramming at least one of said firmware and said effectuator.

67. A system as described in claim 66, wherein any such access control apparatus is an ingress/egress control apparatus.

68. A system as described in claim 67, further including a database, which database stores at least one of:

effectuator event information, effectuator command information, and system configuration information.

69. A system as described in claim 68, wherein said firmware allows the said at least one remote device to interact with said at least one effectuator to at least one of:

reprogram said at least one effectuator, obtain status reports and warnings related to operations of at least one of an effectuator and an apparatus, download transaction history related to at least one of an effectuator and an apparatus, establish or change user access criteria, and make and change rules related to an apparatus.

70. A system as described in claim 69, wherein said firmware allows a user to write or re-write rules governing operation of an apparatus of the at least one effectuator via a rules engine.

71. A system as described in claim 70, wherein said rules engine comprises:

at least one of a rule generation user interface, a rule parser and compiler, and a rule execution engine;

wherein any said rule generation user interface generates computer screens and forms that allow a user to add, edit or delete a rule;

wherein any said rule parser and compiler can receive a rule string and transform the string into a format that is most efficient for the rules execution engine; and

wherein any said rules execution engine is responsible for execution of the rule.

72. A system as described in claim 70, wherein rules can be written or re-written by a user of the effectuator at runtime.

73. A system as described in claim 70, wherein a common rule may be shared by other rules.

74. A system as described in claim 69, wherein said software enables a user at the remote device to at least one of:

perform effectuator asset audits, perform effectuator alarm audits, monitor and respond to events from an at least one effectuator, and obtain data from an effectuator related to at least one of asset status, alarm status, and hardware status.

75. A system as described in claim 69, wherein some portion of communication between an at least one effectuator and the at least one remote device can be at least one of password authenticated and encrypted.

76. A system as described in claim 69, wherein the system maintains live connection between the at least one effectuator and the at least one remote device with real-time command/event processing instead of polling.

77. A system as described in claim 69, wherein said software is capable of presenting maps of all effectuators that are part of the system, with representative icons on the maps that show where at least one of an effectuator and an apparatus is located, and wherein clicking on an icon on a map will produce at least one of a more localized map with icons, and a status screen displaying status of at least one of an effectuator and an apparatus at the icon location on the last map produced.

78. A system as described in claim 77, where a characteristic of an icon indicates status of at least one of an effectuator and an apparatus.

79. A system as described in claim 69, wherein CRC checksums are used in relation to the database to create a check sum field in each record that compares all the field contents of the current record with all the field contents of the previous record to prevent tampering with the database.

80. A system as described in claim 69, wherein said lockbox has a latch member for latching a lock box opening member closed, said latch member has a lock box frame connection portion whereby it is connected to the lock box frame via a solenoid pin that can be withdrawn to release the latch member from its connection to the lock box and allow opening of the lockbox.

83. A system as described in claim 62, further including a Zigbee Network connecting apparatuses to each other and to an effectuator.