IL305587A - System and method for self-monitoring access control - Google Patents

Description

SELF-MONITORING ACCESS CONTROL SYSTEM AND METHOD FIELD and BACKGROUND of the INVENTION id="p-1" id="p-1" id="p-1" id="p-1" id="p-1" id="p-1" id="p-1"

[001] The invention relates to access control and specifically to a self- monitoring access control system and method. id="p-2" id="p-2" id="p-2" id="p-2" id="p-2" id="p-2" id="p-2"

[002] In the specification and claims that follow, the terms "access control unit" and "access controller" are used interchangeably and are intended to mean a device that controls electric gates, doors, electrical switches, and the like (hereinafter in the description and claims: "gate" or "gates"), inter alia, as known in the art. In the specification and claims that follow, the terms "service person" and "service personnel" are intended to mean any individual or organization responsible for technical follow up for maintenance/repair of an access controller. Examples of a "service person" are a technician located close to the access controller and responsible for installation and/or maintenance/repair of the controller; and a technician/access controller manufacturer person located remotely from the access controller. id="p-3" id="p-3" id="p-3" id="p-3" id="p-3" id="p-3" id="p-3"

[003] Additionally, in the specification and claims that follow, the terms "cellphone", "smartphone", "phone", and "telephone" are used interchangeably to mean a "mobile device" and are intended to mean any mobile device, such as, but not limited to: a cellphone; a tablet; and a mobile computer, having a cellular connection to a cellular network including a data connection. id="p-4" id="p-4" id="p-4" id="p-4" id="p-4" id="p-4" id="p-4"

[004] Most access controllers are in communication with a user and one or more servers by exemplary LAN or wireless connections, such as, but not limited to: cellular; Bluetooth; and NFC-based technology (Near-Field Communication) to enable the user to interact with and operate the access controller remotely. In virtually all cases, the access controller is located remotely from the user and from the service person, as known in the art. id="p-5" id="p-5" id="p-5" id="p-5" id="p-5" id="p-5" id="p-5"

[005] FIG. 1 shows a prior art process of access controller malfunction repair. Today, when there is an access controller malfunction, the service person can deal 30 with the malfunction if the malfunction is noticed by the user and/or by the service person. Upon a malfunction, a technical log of the access controller can be obtained according to a manufacturer's software design and available either locally and/or remotely. The technical log includes "raw data" 3 - meaning a time-log including exemplary data, such as but not limited to: signals 4; voltage 5; and a bit error ratio (BER) 6, which reflect access controller operation/activity over a given period of time, usually over a number of hours and up to a few days, during which the malfunction occurred. Once the technical log is reviewed 8, maintenance and/or repair support can usually be provided either remotely or locally to the local service person to repair the controller 9. id="p-6" id="p-6" id="p-6" id="p-6" id="p-6" id="p-6" id="p-6"

[006] In certain cases, an (apparent) access controller malfunction may be the result of a local communications network problem, such as, but not limited to a cellular network problem, in which case personnel do not necessarily need to repair the access controller itself, but rather wait for the local communications network to be reestablished. id="p-7" id="p-7" id="p-7" id="p-7" id="p-7" id="p-7" id="p-7"

[007] The following prior art disclosures are relevant to access control, in general, and in managing access control systems. id="p-8" id="p-8" id="p-8" id="p-8" id="p-8" id="p-8" id="p-8"

[008] US Patent Application 2015/227284 (Tehranchi et al.) describes a diagnostic tool for a mobile device such as a smartphone or laptop, which helps a user to control, monitor, diagnose and troubleshoot a movable barrier operator. In some examples, software is downloadable by the user from the user’s phone service provider, or from an operator manufacturer's website. The software includes a graphical user interface that allows a user to execute various diagnostic and monitoring functions. The operator is configured with a network interface for communicating with the mobile device wirelessly. Such an interface may include Bluetooth, Wi-Fi, NFC or any other available wireless communication technologies. id="p-9" id="p-9" id="p-9" id="p-9" id="p-9" id="p-9" id="p-9"

[009] Chinese Patent 105575180B (Wang Ming et al.) describes an intelligent unmanned remote garage management system based on the Internet of things. The system includes a cloud center, an operation and maintenance center console, a plurality of intelligent garage control terminals and a plurality of clients who are connected through a network. Subsystems and terminals in the system are in data connection through the network, and the purposes of the unmanned management and information sharing are achieved though cloud storage and big data analysis. Human-friendly car parking and fetching is achieved by high-speed passing and convenient payment. id="p-10" id="p-10" id="p-10" id="p-10" id="p-10" id="p-10" id="p-10"

[010] Chinese Utility Model CN 211472293 (Hong Hengyuan et al.) describes a self-detection vehicle barrier system including a main machine box, a rod handle, and a railing arranged on the rod handle. The rod handle is fixedly connected with the main machine box through a driving shaft, a power mechanism rotates the driving shaft, and a monitoring controller controls the power mechanism in the main machine box. The monitoring controller is in communication connection with the monitoring server and the plurality of monitoring sensors. The monitoring sensors monitor the position, the working environment, and the running state of the barrier system. The monitoring server receives and stores monitoring data of the monitoring sensors, and is in communication with the monitoring terminal. The monitoring terminal checks the monitoring data. The barrier system is capable of self-detection and remote monitoring of the barrier system. Operation and maintenance management personnel can rapidly obtain information from the barrier system when it breaks down and faults are timely determined. id="p-11" id="p-11" id="p-11" id="p-11" id="p-11" id="p-11" id="p-11"

[011] US Patent Application 2019/039400 (Ikeler et al.) describes a system for moving a barrier and includes a motor with an integrated encoder, operative to generate pulses as a function of rotation of the motor’s shaft. A preferred form of encoder is a rotary optical encoder to generate optical pulses as a function of rotational movement of the rotatable shaft. Both a microcontroller to determine gate status and a controller to control gate movement, receive the pulses and separately execute methods in response thereto. id="p-12" id="p-12" id="p-12" id="p-12" id="p-12" id="p-12" id="p-12"

[012] The prior art does not address problems of monitoring and maintaining a large number (usually in excess of 1,000) of access controllers/access control systems located over a large geographical area (including in different countries). Furthermore, very little has been done to automate/streamline the manually-intensive process of dealing with malfunctions outlined hereinabove in FIG. 1 . 30 id="p-13" id="p-13" id="p-13" id="p-13" id="p-13" id="p-13" id="p-13"

[013] There is therefore a need for a robust monitoring access control system capable of not only monitoring a large number of access controllers/access control systems located over a large geographical area, but also including capabilities to self-monitor and to solve most malfunction problems, and thereby to minimize involvement of local and remote service personnel, in addition to providing advanced analysis information.

SUMMARY OF THE INVENTION id="p-14" id="p-14" id="p-14" id="p-14" id="p-14" id="p-14" id="p-14"

[014] The presently disclosed subject matter relates to a self-monitoring access control system and method. The system and method refer to controlling electric gates, in which the term gate(s) may include electric gates, doors, electrical switches, and the like (as noted above), id="p-15" id="p-15" id="p-15" id="p-15" id="p-15" id="p-15" id="p-15"

[015] The system includes: (a) a plurality of access controllers located at each gate, each of the plurality of access controllers configured, when in operation, to generate a plurality of technical and command data over time, the plurality of technical and command data and associated time values, being input; (b) at least one server remotely connected to the plurality of access controllers, and (c) at least one database associated with the at least one server, the at least one server and the at least one database, being a server-database - wherein the input of the plurality of technical and command data and associated time values is received by the at least one server and stored in the at least one database; (d) a plurality of request-and-programmed instructions (RPI) associated with the server-database, the plurality of RPI, being an algorithm; wherein the algorithm is configured to interact with the server-database and to serve to identify and locate potential sources of malfunction of each of the plurality of access controllers and to serve to repair the sources of the malfunction. id="p-16" id="p-16" id="p-16" id="p-16" id="p-16" id="p-16" id="p-16"

[016] In some examples, the system includes: a voltage; a cellular signal level; a current consumption; a data consumption, including a number of resets; system outages/wiring disconnects; a motor load; a noise parameter; a relay status, indicative of gate open/gate closed; a relay operation status, indicative of proper functioning or malfunctioning; an accelerometer indication; and a sensor input. id="p-17" id="p-17" id="p-17" id="p-17" id="p-17" id="p-17" id="p-17"

[017] In some examples, the system further includes technical data and command data, wherein command data includes a first user status-versus time log and a second user-status-versus time log. id="p-18" id="p-18" id="p-18" id="p-18" id="p-18" id="p-18" id="p-18"

[018] In some examples, the system the plurality of access controllers ranges from hundreds to thousands. id="p-19" id="p-19" id="p-19" id="p-19" id="p-19" id="p-19" id="p-19"

[019] In some examples, each of the plurality of access controllers has parameters including at least: a plurality of users; a corresponding user cellular signal; and a geographical location; the parameters included in the input. id="p-20" id="p-20" id="p-20" id="p-20" id="p-20" id="p-20" id="p-20"

[020] In some examples, the plurality of users includes: users/customers; managers; and service personnel. id="p-21" id="p-21" id="p-21" id="p-21" id="p-21" id="p-21" id="p-21"

[021] In some examples, the server-database and the algorithm are configured to perform a big data analysis of the plurality of access controllers, the big data analysis being directed to provide a malfunction analysis and an operational analysis. id="p-22" id="p-22" id="p-22" id="p-22" id="p-22" id="p-22" id="p-22"

[022] In some examples, the malfunction analysis includes at least one of: a cellular network feedback/analysis; a location-related analysis; and a server-related analysis. id="p-23" id="p-23" id="p-23" id="p-23" id="p-23" id="p-23" id="p-23"

[023] In some examples, the operational analysis includes at least one of: a traffic analysis; a safety analysis; and a varied statistical analysis. id="p-24" id="p-24" id="p-24" id="p-24" id="p-24" id="p-24" id="p-24"

[024] In some examples, the malfunction analysis and the operational analysis are configured to be displayed online and exported on demand. id="p-25" id="p-25" id="p-25" id="p-25" id="p-25" id="p-25" id="p-25"

[025] In some examples, the system further includes one or more translation units, which are integrated into the access controller, from sources devices via a dry contact switch). id="p-26" id="p-26" id="p-26" id="p-26" id="p-26" id="p-26" id="p-26"

[026] In some examples, the translation unit includes a plurality of contact blocks, which are connected to a processing / programming unit. id="p-27" id="p-27" id="p-27" id="p-27" id="p-27" id="p-27" id="p-27"

[027] In some examples, the processing/programming unit has processing, memory, clock, relay, and communication functionality therein. id="p-28" id="p-28" id="p-28" id="p-28" id="p-28" id="p-28" id="p-28"

[028] In some examples, the plurality of contact blocks are connected to corresponding dry contacts of a plurality of source devices. id="p-29" id="p-29" id="p-29" id="p-29" id="p-29" id="p-29" id="p-29"

[029] The subject matter also provides a method of using a self-monitoring access control system that controls electric gates. The method includes: (a) generating a plurality of technical and command data over time from a plurality of operating access controllers located at respective gates, the plurality of technical and command data and associated time values from each of the plurality of access controllers being referred to as input; (b) remotely connecting at least one server to the plurality of access controllers, and (c) associating at least one database with the at least one server, the at least one server and the at least one database being a server-database - wherein the at least one server receives the input, and the input is stored in the at least one database; (d) associating a plurality of request-and-programmed instructions (RPI), with the server-database, the plurality of RPI being an algorithm - wherein the algorithm interacts with the server-database to identify and locate sources of malfunction of each of the plurality of access controllers and to repair the sources of the malfunction. id="p-30" id="p-30" id="p-30" id="p-30" id="p-30" id="p-30" id="p-30"

[030] In some examples of the method, the input includes using at least one of: a voltage; a cellular signal level; a current consumption; a data consumption, including a number of resets; system outages/wiring disconnects; a noise parameter; a relay status, indicative of gate open/gate closed; a relay operation status, indicative of proper functioning or malfunctioning; an accelerometer indication; and a sensor input. id="p-31" id="p-31" id="p-31" id="p-31" id="p-31" id="p-31" id="p-31"

[031] In some examples of the method, the input further includes using technical data and command data, wherein the command data includes a first user status-versus time log and a second user-status-versus time log. id="p-32" id="p-32" id="p-32" id="p-32" id="p-32" id="p-32" id="p-32"

[032] In some examples of the method, the plurality of access controllers ranges from hundreds to thousands. id="p-33" id="p-33" id="p-33" id="p-33" id="p-33" id="p-33" id="p-33"

[033] In some examples of the method, each of the plurality of access controllers has parameters including at least: a plurality of users; a corresponding user cellular signal; and a geographical location, and the parameters are included in the input. id="p-34" id="p-34" id="p-34" id="p-34" id="p-34" id="p-34" id="p-34"

[034] In some examples of the method, the plurality of users includes: users/customers; managers; and service personnel. id="p-35" id="p-35" id="p-35" id="p-35" id="p-35" id="p-35" id="p-35"

[035] In some examples, the method includes performing, by the server-database and the algorithm, a big data analysis of the plurality of access controllers, the big data analysis directed to provide a malfunction analysis and an operational analysis. id="p-36" id="p-36" id="p-36" id="p-36" id="p-36" id="p-36" id="p-36"

[036] In some examples of the method, the malfunction analysis includes at least: a cellular network feedback/analysis; a location-related analysis; and a server-related analysis. id="p-37" id="p-37" id="p-37" id="p-37" id="p-37" id="p-37" id="p-37"

[037] In some examples of the method, operational analysis includes at least: a traffic analysis; a safety analysis; and a varied statistical analysis. id="p-38" id="p-38" id="p-38" id="p-38" id="p-38" id="p-38" id="p-38"

[038] In some examples of the method, includes displaying and exporting the malfunction analysis and the operational and exported on demand.

LIST OF DRAWINGS id="p-39" id="p-39" id="p-39" id="p-39" id="p-39" id="p-39" id="p-39"

[039] The invention is described herein, by way of example only, with reference to the accompanying drawings, wherein: id="p-40" id="p-40" id="p-40" id="p-40" id="p-40" id="p-40" id="p-40"

[040] FIG 1 is a diagram showing a prior art process of access controller malfunction repair. id="p-41" id="p-41" id="p-41" id="p-41" id="p-41" id="p-41" id="p-41"

[041] FIG 2 is an access controller monitoring process and system block diagram, in accordance with the presently disclosed subject matter. id="p-42" id="p-42" id="p-42" id="p-42" id="p-42" id="p-42" id="p-42"

[042] FIG 3 is a block diagram showing input, technical data, and operational data of an access controller, in accordance with the presently disclosed subject matter. id="p-43" id="p-43" id="p-43" id="p-43" id="p-43" id="p-43" id="p-43"

[043] FIG 4 is a diagram of data flow from the access controller and a big data process diagram, in accordance with the presently disclosed subject matter. id="p-44" id="p-44" id="p-44" id="p-44" id="p-44" id="p-44" id="p-44"

[044] FIG 5 is a block diagram of an exemplary translation unit, in accordance with the presently disclosed subject matter.

DETAILED DESCRIPTION id="p-45" id="p-45" id="p-45" id="p-45" id="p-45" id="p-45" id="p-45"

[045] FIG. 2 shows an access controller monitoring process and system block diagram 20, in accordance with the presently disclosed subject matter. Over time, during operation of an access controller 21, a plurality of technical and command data from the access controllers 21, called "input" 23 is generated (and forwarded to a server 30), including associated time, location, users, and the like values. Input 23 includes: a voltage 24; a cellular signal level 25 (via a cellular provider); a current consumption 26; a data consumption 27 (resets); and other parameters 28, such as, but not limited to: system outages/wiring disconnects; a motor load; a noise parameter; a relay status (gate open/gate closed); a relay operation status indication (proper or faulty/relay, which is related to the relay itself (e.g. of other parameters 28, FIG. 2 ) when it is damaged and knowing that there is a malfunction in access controller 21); an accelerometer indication (for example, to serve against vandalism); and a sensor and/or camera input to detect traffic, including identification of vehicles. id="p-46" id="p-46" id="p-46" id="p-46" id="p-46" id="p-46" id="p-46"

[046] Input 23 is transferred to the server 30 (the term "server" is intended to mean one or more servers, as known in the art, including a database, as described hereinbelow) during operation of access controller 21. Server 30 is shown in the current figure having a "cloud" representation, signifying that input 23 is uploaded to the cloud, as known in the art. Input 23 is collected and stored in server/database for technical/malfunction and operational support, as described hereinbelow. id="p-47" id="p-47" id="p-47" id="p-47" id="p-47" id="p-47" id="p-47"

[047] Access controller 21 includes a collection of processing rules 32 (also referred to hereinbelow as "algorithm" 32, or operational algorithm 32) directed to review the input 23 provided to server/database 30, and to execute maintenance, trouble-shooting, and repair instructions for the access controller. Processing rules (aka algorithm 32) include a plurality of request-and-programmed-instructions (RPI) that serve to review input 23 and to specify one or more desired actions, as further described hereinbelow. Algorithm 32 serves to not only self-monitor access controller 21 (by reviewing inputs 23 received from the controller), but to also rapidly identify and locate sources of controller malfunction and thereby serve to repair faulty/malfunctioning access controllers 21. id="p-48" id="p-48" id="p-48" id="p-48" id="p-48" id="p-48" id="p-48"

[048] When installing access controllers 21, the installer in the installation process, connects the serial number of the access controller 21 with the location, and a name (e.g. office gate or home gate, etc.) that the installer can provide, usually according to the customer preference. Each access controller 21 provides inputs 23 to the server 30 online. As a result, the system may receive new data from a large number of locations. This is a particular feature of the system, wherein the access controllers 21 collect and process online (data streaming) information according to time, user, and locations. id="p-49" id="p-49" id="p-49" id="p-49" id="p-49" id="p-49" id="p-49"

[049] The flow logic of the process of block diagram 20 continues with the question: Controller malfunction 34. If there is a controller malfunction (= "yes") then action/information 36 is forwarded. The action/information 36 can include: an alert for action, such as, but not limited to: repairing or replacing the access controller 21; instructions to solve the source of the problem (malfunction) such as an incorrect power supply; and to deal with a low signal by adding an external antenna and/or replacing a cellular sim card and/or cellular provider, or an automatic action. An automatic action occurs if the parameters that collected online from the access controller 21, do not meet the criteria programmed, algorithm 32. Then algorithm sends an action command message according to the received parameter, which for example, may be a command to shut down the access controller 21. The algorithm 32 of the server 30 is configured to collect information and instruct an action according to the parameters collected. All information is collected by the server 30, preferably continually (online streaming data), and any action (e.g. malfunction correction) can be programed to perform a corrective that action when it is known from where the information comes and what the identified problem (malfunction) is. The data collection and corrects are performed according to programed instructions to solve, or to avoid a potential controller malfunction. If there is not a controller malfunction (= "no") then the malfunction event is closed. id="p-50" id="p-50" id="p-50" id="p-50" id="p-50" id="p-50" id="p-50"

[050] As noted hereinabove with regard to FIG. 2 , during operation of access controller 21, technical and command data is generated, which is collectively called input 23. id="p-51" id="p-51" id="p-51" id="p-51" id="p-51" id="p-51" id="p-51"

[051] FIG. 3 is a block diagram showing input 23, technical data 35, and command data 40, in accordance with some examples of the presently disclosed subject matter. Apart from differences described below, input 23 of FIG. 3 is identical in notation, configuration, and functionality as shown in FIG. 2 hereinabove and elements indicated by the same reference numerals and/or letters are generally identical in configuration, operation, and functionality as described hereinabove.

Technical Data id="p-52" id="p-52" id="p-52" id="p-52" id="p-52" id="p-52" id="p-52"

[052] The following discussion deals with technical data 35 of the input from access controller 21. As noted hereinabove, technical data includes information collected on an ongoing basis regarding the operation of access controller 21 and activity as follows: id="p-53" id="p-53" id="p-53" id="p-53" id="p-53" id="p-53" id="p-53"

[053] - a measurement of voltage 24 of the power supply (not shown) through an on-board Analog-to-Digital (A/D) measurement; id="p-54" id="p-54" id="p-54" id="p-54" id="p-54" id="p-54" id="p-54"

[054] - a measurement of cellular signal level 25, obtained by an indication and/or reading of the cellular network, through an on onboard modem and installed software (neither shown); id="p-55" id="p-55" id="p-55" id="p-55" id="p-55" id="p-55" id="p-55"

[055] - a current consumption 26, obtained by measuring the current of the controller; id="p-56" id="p-56" id="p-56" id="p-56" id="p-56" id="p-56" id="p-56"

[056] - a number of data resets/disconnections (data consumption 27) may occur, for example, due to a power consumption issue, for example, if the sim card or the access controller 21 is damaged, etc., for example if the access controller resets many times, it consumes more data (consumption 27). In each access controller 21 there is a sim card installed on each access controller 21. Each one of the sim cards has megabytes of data consumption and what the average data consumption should be is known. If the data consumption is above a certain threshold, it means the access controller 21 has reset itself many times, because when the access controller 21 powers up after reset, there is a higher data consumption 27. Note, many resets occur when the data consumption 27 has exceeded the average (or exceeds a predetermined deviation value from the average data consumption). obtained by counting/recording the number of disconnections by an onboard modem and installed software (neither shown in the current figure); id="p-57" id="p-57" id="p-57" id="p-57" id="p-57" id="p-57" id="p-57"

[057] - a Bit Error Ratio (BER), represented by other parameters 28, obtained by a measurement of electro-magnetic interfering (EMI) noise through an antenna, cellular modem, or installed software (none shown). Such noise may exceed the cellular signal level 25 whereby the access controller 21 does not operate. To overcome this noise issue, the installer can move the access controller 21 to a different location to avoid/reduce the noise; id="p-58" id="p-58" id="p-58" id="p-58" id="p-58" id="p-58" id="p-58"

[058] - a relay state (also represented by other parameters 28) – closed or open. When a relay (not shown, but represented by other parameters 28) is connected to access controller 21, the current should increase, as the relay is active during access controller use. If the current is not present and/or not increasing, installed software can detect the current and determine if the relay is damaged. id="p-59" id="p-59" id="p-59" id="p-59" id="p-59" id="p-59" id="p-59"

[059] Although not identified in the current figure, additional readings and measurements may be included in the technical data to give further indications of proper controller functioning or malfunctioning. id="p-60" id="p-60" id="p-60" id="p-60" id="p-60" id="p-60" id="p-60"

[060] One example of a technical issue/consideration is when access controller 21 is installed to control a gate. If the power supply of access controller 21 exhibits a current and/or a voltage outside of acceptable limits/levels, the access controller may resultantly reset frequently - significantly more frequently than a normal reset rate. This frequent reset (technical data) can indicate a malfunction of access controller 21, which could be damaged due to incorrect voltage and/or current levels supplied by the power supply.

Command Data: id="p-61" id="p-61" id="p-61" id="p-61" id="p-61" id="p-61" id="p-61"

[061] In addition to technical data associated with access controller 21, the following discussion deals with command data 40 ( FIG. 3 ). When a gate is opened or closed (i.e., following a specific user command) a first user status-versus-time log 42 (including a username, whether authorized or not, and successful or not to open/close a gate) reflects such status. Additionally, a second user-status-versus time log 44 reflects which gate administrator (e.g. human resource manager) identified the corresponding user authorization status at a certain access controller 21. Both logs 42 and 44 may be displayed on a user-interface (not shown in the current figure). id="p-62" id="p-62" id="p-62" id="p-62" id="p-62" id="p-62" id="p-62"

[062] FIG. 4 shows data flow from access controller 21 and a big data process diagram, in accordance with examples of the presently disclosed subject matter. Apart from differences described below, access controller 21, input 23, and server/database 30 of FIG. 4 are identical in notation, configuration, and functionality as illustrated in FIG. 2 and hereinabove, and elements indicated by the same reference numerals and/or letters are generally identical in configuration, operation, and functionality as described hereinabove. id="p-63" id="p-63" id="p-63" id="p-63" id="p-63" id="p-63" id="p-63"

[063] Access controller 21 is indicated as "access controller 1" and as "access controller n" to signify a plurality of access controllers, the plurality of access controllers typically ranging from hundreds to thousands of individual access controllers. Each access controller 21 has parameters including, but not limited to: a plurality of users 54; a corresponding user cellular signal 55; and a geographical location 56. The plurality of users 54 (which can include users/customers; managers; and service personnel); the associated user cellular signal 55; and the geographical location 56 of each access controller 21 are included in input 23, which is communicated to server 30. 30 id="p-64" id="p-64" id="p-64" id="p-64" id="p-64" id="p-64" id="p-64"

[064] Input 23 is collected and stored in server/database 30, and algorithm is directed to review input 23 obtained from the server to execute maintenance, trouble-shooting, and repair instructions - all as described with reference to FIG. 2 hereinabove. id="p-65" id="p-65" id="p-65" id="p-65" id="p-65" id="p-65" id="p-65"

[065] With continued reference to FIG. 4 , a big data analysis 132 is likewise directed to review input 23 from the server/database 30. For such purpose, big data analysis 132 is directed to provide a malfunction analysis 134 and operational analysis 136 of an installed base of a large number of access controllers 21. Whereas individual access controllers 21 and controller installation can be monitored and the big data analysis 132 can be directed to execute maintenance, trouble-shooting, and repair instructions, using big data analysis 132. id="p-66" id="p-66" id="p-66" id="p-66" id="p-66" id="p-66" id="p-66"

[066] Malfunction analysis 134 includes, but is not limited to, a cellular network feedback/analysis 141 (where, for example, cellular signals 55 fail from the same location and by the same provider for many controllers 21). Access controllers 21 are installed at various geographical areas and identify and provide informative automatic messages to each service provider, as a result of the cellular network feedback/analysis 141. If the access controller 21 is experiencing a malfunction (e.g. identified by a "no signal" in this geographical area from any access controllers; a location-related analysis 142 (where, for example, user activity time is excessive and/or there are slow responses or no response at all from the same location of controllers); and a server-related analysis 143 identifies a problem (where, for example, user activity is average/typical but access controller responses from server 30 are indicative as above). id="p-67" id="p-67" id="p-67" id="p-67" id="p-67" id="p-67" id="p-67"

[067] The system’s access controllers 21 are installed at each gate to analyze the data stored in server/database 30 by big data analysis 132. Analysis of the data allows identification of several parameter issues, such as malfunctions relating to location, users, and time. FIG. 4 also shows operational analysis 136, wherein, for example, administrators are provided analysis on the arrival of factory workers (arriving early, on time, or late) whereby an alert will be sent to the administrator. 30 id="p-68" id="p-68" id="p-68" id="p-68" id="p-68" id="p-68" id="p-68"

[068] The system can also provide operational analysis 136, which includes but is not limited to, a traffic analysis 145. For example, knowing the hour that workers leave their workplaces can provide input for "smart cities", which can use this information on the hour of workers leaving, to control their traffic lights. Knowing changes in driving patterns, including those depending on the day of the week, derived from a large number of controllers 21, provides data that can be analyzed by driving analysis 147. The capability provided by operational analysis 136, may also be used for additional purposes, represented by statistical analysis 149. id="p-69" id="p-69" id="p-69" id="p-69" id="p-69" id="p-69" id="p-69"

[069] Any set or individual analysis of malfunction analysis 134 and operational analysis 136 may be displayed and/or exported on demand 160. id="p-70" id="p-70" id="p-70" id="p-70" id="p-70" id="p-70" id="p-70"

[070] In the following description, the term "algorithm" means a collection of processing rules for both "big data analysis" , as described with reference to FIG. 4 , and for more limited maintenance, trouble-shooting, and repair instructions, as described with reference to FIG. 2 .

Data Calculation and Actions Taken by the Algorithm id="p-71" id="p-71" id="p-71" id="p-71" id="p-71" id="p-71" id="p-71"

[071] Data in the database, which is streamed from server 30, can be analyzed and displayed by the algorithm 32 on demand. Optionally or additionally, the algorithm 32 serves to automatically generate instructions and/or actions to be performed by an administrative user or an end user after each is informed about the necessary action. Also, the algorithm 32 (according to user restrictions) serves to automatically generate commands to access one or more of access controller when necessary. One example is when voltage supply to access controller exceeds allowed limits. In this case, the algorithm 32 serves to shut down the access controller 21 to prevent permanently damage thereto. id="p-72" id="p-72" id="p-72" id="p-72" id="p-72" id="p-72" id="p-72"

[072] The algorithm 32 serves to monitor gate hardware associated with the controller in two modes, as noted below. id="p-73" id="p-73" id="p-73" id="p-73" id="p-73" id="p-73" id="p-73"

[073] (1) Access controller setup mode and setup test run. This mode is operated typically for about 10 minutes after setup of access control 21, in testing mode, and serves to sample all input technical issues related to installation.

Example: During installation and shortly thereafter, a trouble-shooting module of the algorithm 32 serves to sample and measure and generate warnings related to: voltage 24; cellular signal level 25; and all measured input abnormalities in the installed access controller 21. The algorithm 32 also serves to update the installer, or user, regarding installation quality and can further indicate a failure of the access controller 21, which can be displayed in real time and update the installer for corrections. The update can be provided via an email or computer/mobile application. An exemplary computer/mobile application is PALGATE®, developed by the assignee of the current patent application. Access controllers 21 are connected to server 30 using the cellular internet (otherwise known as "internet of things"- IOT) to the server, thereby enabling visibility of any action / technical data streaming to the server, which can be displayed on a user interface (UI). id="p-74" id="p-74" id="p-74" id="p-74" id="p-74" id="p-74" id="p-74"

[074] (2) Ongoing inspection/operational status – This is an ongoing/after installation mode and serves to monitor and identify if access controller 21 is having malfunctions or an abnormal status of technical inputs 23 measured in the access controller and forwarded to server 30. Alerts related to such malfunctions/abnormal status are sent to the user by notification methods such as a push notification to a computer application and/or email, or the like. Such notifications provide the user with a positive user experience and a quick support ability for the service provider. id="p-75" id="p-75" id="p-75" id="p-75" id="p-75" id="p-75" id="p-75"

[075] Example: If there are changes in cellular signal level 25 (changes ranging from varying sensitivity levels to loss of signal, for example) such changes are updated regularly (via communication networks) on server 30. Data stored in the database of server 30 is used for future/continued analysis and control of a given access controller 21, as well as for an entire base of installed access controllers, to detect anomalies and malfunctions and to optimize overall service and to provide advanced alerts to users. id="p-76" id="p-76" id="p-76" id="p-76" id="p-76" id="p-76" id="p-76"

[076] Example: Action taken by the algorithm 32: When a power supply of access controller 21 is not within allowed operational levels, a notification may be sent via a push notification to the installer’s App or by any communication method. The notification serves to alert the installer to take action and remotely shut down controller 21 to avoid permanent damage. Alternatively or optionally, the installer can choose to perform an auto shut-down (an operational action by algorithm 32) or simply be notified. id="p-77" id="p-77" id="p-77" id="p-77" id="p-77" id="p-77" id="p-77"

[077] Example: Another ability of the operational algorithm 32 is a trace and alert functionality. An administrative user (i.e., a user with access controller installed on his property) may choose to receive operational alerts of interest, such as, but not limited to, alerts on specified users who have accessed a gate at selected hours and dates. Specifically, the algorithm 32 can focus on a worker/user’s habits, for example, at an entrance gate, with the algorithm performing continuous statistical analysis. The analysis can provide to an administrative manager/user at the location an insight on arrival/departure times of a worker (i.e., late arrival and/or leaving at an unusual time), based on date from access controller 21. id="p-78" id="p-78" id="p-78" id="p-78" id="p-78" id="p-78" id="p-78"

[078] Example: Another ability of the operational algorithm includes a multiple step verification option to determine an authorized user. When one access controller 21 is used to activate a relay to open a gate (or any activated action by a relay, for example) one or more activation requests are triggered by a second access controller such as, but not limited to, an App; a remote control; and a face recognition, to activate the relay. Using the second access controller 21 serves to reduce vehicle or equipment theft (for example, when a user phone is stolen, and a non-authorized person can control the access controller as an impostor). id="p-79" id="p-79" id="p-79" id="p-79" id="p-79" id="p-79" id="p-79"

[079] Alternatively or optionally, big data capabilities are employed to match between a user and his triggering methods. For example, when an open-gate request is sent using an App, a verification is requested to complete the action by the user entering a passcode in the App. Alternatively, the same verification/authorization method can be affected by a connected remote control by entering a passcode. Additionally, in license plate recognition (LPR), a code sent to a second controller 21 or a request to activate the relay sent to the user App by cellular communication or NFC-based technology is employed to serve as the verification authorization to open the gate. id="p-80" id="p-80" id="p-80" id="p-80" id="p-80" id="p-80" id="p-80"

[080] Example: Additional operational diagnostic options: An error entering a single number or prefix and identifying a system on the error (wrong known user phone number). The identification capability is based upon the user number being part of the system database as part of controller identification. Such an identification can serve to perform an automatic phone number correction or to update an administrator who may subsequently manually make the correction himself. id="p-81" id="p-81" id="p-81" id="p-81" id="p-81" id="p-81" id="p-81"

[081] Example: A monitored access controller 21 provides a "last missing indicator" to the server, which is an indication of a last missing parameter. The "last missing parameter" is one of the parameters such as voltage level or cellular signal quality, received in server 30, which exhibited problems /abnormal status at the last moments when it was connected and was working satisfactorily. The "last missing parameter" serves to direct field service personnel to identify the source of the problem with higher probability. id="p-82" id="p-82" id="p-82" id="p-82" id="p-82" id="p-82" id="p-82"

[082] Example: Voltage-drop alerts cause high data consumption. Voltage drop alerts come about when there are multiple resets during functioning of access controller 21. Upon startup and reconnecting to the cellular network (following a shutdown) data consumption (typically measured in megabytes) is increased and is detected by server 30. id="p-83" id="p-83" id="p-83" id="p-83" id="p-83" id="p-83" id="p-83"

[083] The algorithm can additionally serve to identify existing software bugs, with the information being stored in the database of server 30 and then serving as a basis for receiving alerts and identifying future failures.

Cloud Server and Big Data id="p-84" id="p-84" id="p-84" id="p-84" id="p-84" id="p-84" id="p-84"

[084] In some examples, there are cloud server and big data capabilities, wherein the algorithm serves to calculate and provide many solutions for malfunction and operational needs, based on a large base of data streaming and corresponding database storage. id="p-85" id="p-85" id="p-85" id="p-85" id="p-85" id="p-85" id="p-85"

[085] With reference to FIG. 3 , big data analysis can be made according to technical and command data, which are collected and are part of the data base stored in server 30. Many of the big data analyses 132 ( FIG. 4 ) take advantage of respective mobile device phone numbers, which yield the user identity, the location of the access controller 21 in use at the time of receiving commands, and the time of use - all included in input 23, as noted above with reference to FIG. 4 . Additionally, the location of access controller 21 is known by a known installed location address and/or by a user location indicator, such as by an App and/or mobile device GPS. The following are non-limiting examples of big data analyses 132. id="p-86" id="p-86" id="p-86" id="p-86" id="p-86" id="p-86" id="p-86"

[086] Example – Traffic guidance: The system, taking advantage of big data, identifies when a user is operating access controller 21 for opening the gate. Based on location/geographical abilities, the system identifies the physical address of access controllers 21 and their operation during a given time frame. For example, assuming users are using a dedicated App such as the PALGATE® service, opening the gate to leave and arrive to work and open the gate. If many users are using the PALGATE® service, traffic alerts and guidance may be provided to drivers, and/or traffic lights can be prioritized accordingly to reduce traffic jams. id="p-87" id="p-87" id="p-87" id="p-87" id="p-87" id="p-87" id="p-87"

[087] Example – Another example of big data availability/use is to provide cellular providers geographic area malfunction alerts. Because each access controller 21 is connected to a plurality of SIM’s (identifying the mobile devices of respective users versus a plurality of cellular providers) the alerts can be determined in a specific geographical area if there is a common communication problem detected controllers using a given cellular provider. In such a case, an alert can be sent to the corresponding cellular provider to assist to identify the malfunction location and to possibly reduce the time to detect the source of the cellular station problem. This alert service can be offered as part of big data services of the system. id="p-88" id="p-88" id="p-88" id="p-88" id="p-88" id="p-88" id="p-88"

[088] Example – An additional aspect of big data availability/use is to use access controller 21 to trigger payment services, to receive payments and to provide payments. One example, based on time and identification, is where access controller 21 and a corresponding App are in communication to provide access per payment. Examples include, but are not limited to, entrance to: any paid public service; a country club; rental housing; and conventional parking lots with access control. 30 id="p-89" id="p-89" id="p-89" id="p-89" id="p-89" id="p-89" id="p-89"

[089] Example – A similar example is a mobile device having wallet services. Based on elapsed time at the location and input 23 to access controller 21, the algorithm serves to calculate the total time at the location and a corresponding cost can be calculated. Communications between server 30, the algorithm 32, and the user’s mobile device having wallet services, enables near-field communication (NFC) payment by the user’s wallet on his mobile device.

Amplifying Capabilities of the Algorithm and Server/Database id="p-90" id="p-90" id="p-90" id="p-90" id="p-90" id="p-90" id="p-90"

[090] The presently disclosed subject matter can take advantage of existing input sockets 240 (discussed below with reference to FIG. 5 ) of respective access controllers 21, coupled with one or more translation units 200 (as described further hereinbelow) which are integrated into the access controller monitoring system ( FIG. 2 ), to amplify capabilities of the Algorithm and Server/Database (as described hereinabove) and to provide additional alert/monitoring of local sources and local source malfunction, all as described hereinbelow. id="p-91" id="p-91" id="p-91" id="p-91" id="p-91" id="p-91" id="p-91"

[091] FIG. 5 shows an exemplary translation unit 200, in accordance with the currently disclosed subject matter. Exemplary translation unit 200 includes: a plurality of contact blocks 205 (indicated as "1", "2", "3"… "n"), which are connected to a processing/programming unit 210. Processing/programming unit 210 has processing, memory, clock, relay, and communication functionality therein, as described further hereinbelow. Contact blocks 205 are connected to corresponding so-called dry contacts of a plurality of source devices 220 (indicated as "source device 1" , "source device 2", "source device 3", and "source device n"). Source devices 220 include, but are not limited to, a gate contact; a camera; a sensor: and a gate motor dry contact, as known in the art. Source devices 220 are typically sub-components of a gate, and the source devices are controlled by access controller 21. id="p-92" id="p-92" id="p-92" id="p-92" id="p-92" id="p-92" id="p-92"

[092] A power unit 225 supplies power to the processing/program unit 210. Power unit 225 may be an on-board power source (such as but not limited to batteries) or an external power source. Processing/programming unit 210 is typically programmed upon installation of translation unit 200 and upon connection of processing/programming unit 210 to access controller input socket 240. In this way, access controller 21 receives respective time-relay signals ("translated" by translation unit 200) representative of each source device 220. id="p-93" id="p-93" id="p-93" id="p-93" id="p-93" id="p-93" id="p-93"

[093] Translation unit 200 functions as an additional maintenance/service device, which is integrated into the access controller monitoring system. Because translation unit 200 is typically hard-wire-connected to the access controller input socket 240 (and therefore connected to access controller 21, as shown in FIG. 2 and FIG. 4 ) signals from the translation unit are "visible" to server/database 30, thereby providing additional information regarding respective source devices 2and its operation. id="p-94" id="p-94" id="p-94" id="p-94" id="p-94" id="p-94" id="p-94"

[094] The following discussion focuses on how translation unit 200 interacts with the plurality of source devices 220 (e.g. gate motor, gate control panel, gate, electrical wire fray, etc.), via respective connections to the plurality of contact blocks 205; and, utilizing the server capabilities described hereinabove, provides additional malfunction assistance/indications from additional sources and send alerts accordingly. The discussion below refers to one of plurality of source devices 220 as "the source device" and a corresponding one of the plurality of contact blocks 205 as "the contact block", for purposes of simplicity. id="p-95" id="p-95" id="p-95" id="p-95" id="p-95" id="p-95" id="p-95"

[095] During operation, a status of access controller 21 changes from a first status of "normally open to normally closed" to a second status of "normally closed to normally open" and the status is sensed in contact block 205. Respective source devices 220 have respective time assignments (having typical values ranging from to 60 seconds) characteristic of a typical time following a change in the status (first-to-second or second-to-first). The respective time assignment, identification of respective source device 220, and the respective contact block 205 are set in processing/programming unit 210 upon installation (i.e., connection/installation of translation unit 200) so that each source device (as sensed by each contact block) has an associated time assignment. id="p-96" id="p-96" id="p-96" id="p-96" id="p-96" id="p-96" id="p-96"

[096] During typical operation, upon a change in the status of source device 220 (from either: first-to-second status or from second-to-first status) sensed in the contact block 205, the processing/programming unit 210 indicates the change to access controller 21 (by way of access controller input socket 240) and the processing/programming unit clock is simultaneously started. When the clock has run a time value = "time assignment", the processing/programming unit changes the status of source device 220 and again indicates the change to the controller input socket 240. During operation, as the plurality of source devices 220 change their respective status, translation unit 200 receives signals indicative of the respective status changes and this information is transferred to the database/server 30. id="p-97" id="p-97" id="p-97" id="p-97" id="p-97" id="p-97" id="p-97"

[097] Typically, signals transferred from translation unit 200 to access controller input socket 240 (and therefore to access controller 21) are in analog form (i.e., "dry contact"). As noted hereinabove, translation unit 200 functions as an analog translator, transferring respective signals indicative of the respective status (and thus functionality/malfunctional operation) of respective source devices 220. This information serves to enable the system, through server/database 30, to perform big data analysis 132 ( FIG. 4 ). id="p-98" id="p-98" id="p-98" id="p-98" id="p-98" id="p-98" id="p-98"

[098] Translation unit 200 can transfer commands from access controller 21 to respective source devices 220, by reversing respective output and input signals. id="p-99" id="p-99" id="p-99" id="p-99" id="p-99" id="p-99" id="p-99"

[099] It will be appreciated that the above descriptions are intended only to serve as examples, and that many other examples are possible within the scope of the present invention and as defined in the appended claims.

Claims (24)

1. A self-monitoring access control system that controls electric gates, the system comprising: a plurality of access controllers located at each gate, each of the plurality of access controllers configured, when in operation, to generate a plurality of technical and command data over time, the plurality of technical and command data and associated time values, being input; at least one server remotely connected to the plurality of access controllers, and at least one database associated with the at least one server, the at least one server and the at least one database, being a server-database; wherein the input of the plurality of technical and command data and associated time values is received by the at least one server and stored in the at least one database; a plurality of request-and-programmed instructions (RPI) associated with the server-database, the plurality of RPI, being an algorithm; wherein the algorithm is configured to interact with the server-database and to serve to identify and locate potential sources of malfunction of each of the plurality of access controllers and to serve to repair the sources of the malfunction.

2. The system according to claim 1, wherein the input includes: a voltage; a cellular signal level; a current consumption; a data consumption, including a number of resets; system outages/wiring disconnects; a motor load; a noise parameter; a relay status, indicative of gate open/gate closed; a relay operation status, indicative of proper functioning or malfunctioning; an accelerometer indication; and a sensor input.

3. The system according to claim 2, wherein the input further comprises technical data and command data, wherein command data includes a first user status-versus time log and a second user-status-versus time log.

4. The system according to claim 1 , wherein the plurality of access controllers ranges from hundreds to thousands.

5. The system according to claim 1 , wherein each of the plurality of access controllers has parameters including at least: a plurality of users; a corresponding user cellular signal; and a geographical location; the parameters included in the input.

6. The system according to claim 5, wherein the plurality of users includes: users/customers; managers; and service personnel.

7. The system according to claim 1 , wherein the server-database and the algorithm are configured to perform a big data analysis of the plurality of access controllers, the big data analysis being directed to provide a malfunction analysis and an operational analysis.

8. The system according to claim 7, wherein the malfunction analysis includes at least one of: a cellular network feedback/analysis; a location-related analysis; and a server-related analysis.

9. The system according to claim 7 , wherein the operational analysis includes at least one of: a traffic analysis; a safety analysis; and a varied statistical analysis.

10. The system according to claim 7, wherein the malfunction analysis and the operational analysis are configured to be displayed online and exported on demand.

11. The system according to claim 1, further comprising one or more translation units, which are integrated into the access controller, from sources devices via a dry contact switch).

12. The system according to claim 11, wherein the translation unit comprises a plurality of contact blocks, which are connected to a processing / programming unit.

13. The system according to claim 12, wherein the processing/programming unit has processing, memory, clock, relay, and communication functionality therein.

14. The system according to claim 12, wherein the plurality of contact blocks are connected to corresponding dry contacts of a plurality of source devices.

15. A method of using a self-monitoring access control system that controls electric gates, the method comprising: generating a plurality of technical and command data over time from a plurality of operating access controllers located at respective gates, the plurality of technical and command data and associated time values from each of the plurality of access controllers being referred to as input; remotely connecting at least one server to the plurality of access controllers, and associating at least one database with the at least one server, the at least one server and the at least one database being a server- database; wherein the at least one server receives the input, and the input is stored in the at least one database; associating a plurality of request-and-programmed instructions (RPI), with the server-database, the plurality of RPI being an algorithm; wherein the algorithm interacts with the server-database to identify and locate sources of malfunction of each of the plurality of access controllers and to repair the sources of the malfunction.

16. The method according to claim 15, wherein the input includes using at least one of: a voltage; a cellular signal level; a current consumption; a data consumption, including a number of resets; system outages/wiring disconnects; a noise parameter; a relay status, indicative of gate open/gate closed; a relay operation status, indicative of proper functioning or malfunctioning; an accelerometer indication; and a sensor input.

17. The method according to claim 16, wherein the input further comprises using technical data and command data, wherein the command data includes a first user status-versus time log and a second user-status-versus time log.

18. The method according to claim 15, wherein the plurality of access controllers ranges from hundreds to thousands.

19. The method according to claim 16, wherein each of the plurality of access controllers has parameters including at least: a plurality of users; a corresponding user cellular signal; and a geographical location, and the parameters are included in the input.

20. The method according to claim 19, wherein the plurality of users includes: users/customers; managers; and service personnel.

21. The method according to claim 15, comprising performing, by the server-database and the algorithm, a big data analysis of the plurality of access controllers, the big data analysis directed to provide a malfunction analysis and an operational analysis.

22. The method according to claim 21, wherein the malfunction analysis includes at least: a cellular network feedback/analysis; a location-related analysis; and a server-related analysis.

23. The method according to claim 21, wherein the operational analysis includes at least: a traffic analysis; a safety analysis; and a varied statistical analysis.

24. The method according to claim 21, comprising displaying and exporting the malfunction analysis and the operational and exported on demand.