This invention relates to the lockdown mechanism in an Access Control System ACS.
Embodiments described herein relate to the field of security system, access control, business process. The embodiments described herein relate to the door lock hardware, cryptographically secured wireless communication network, multi-tiered client-server software architecture. Some embodiments relate to comprehensive realization of intelligent, robust and secure methods to secure doors in the event of violent threat posed by a perpetrator who wants to harm people in a set of building and rooms.
Physical access control locks mounted on a door have existed for centuries. Lock state can be put in secure or open state by manipulating the lock with a specific key. Mechanical keys suffer from a small range of unique keying possibilities (for example a 7 lever lock has only approximately 20,000 unique key cuts) and it is easy to duplicate a key without the knowledge of the key's owner. Recently, electronic door locks (EDLs) have been invented that employ non-mechanical features to provide a very large range of possible keying options (For example a 20 bit code provides approximately one million unique keys) using an electronic key (“E-Key” or “Ekey”). Adding cryptographic protection further secures information privacy stored in EDLs and Ekeys. An Ekey is used in many situations to unlock doors or otherwise provide access to a secure area. Many new hotels and business places, residences and the like utilize such Ekeys, often in the form of electronically readable cards. Such Ekeys can be in the form of card keys, keyfobs, tokens and the like. Examples of Ekey technologies can include magnetic stripe cards, smart cards, near field radio frequency communications (“NFC”), radio frequency identification (“RFID”), passive RFID, active RFID, and so forth. Whichever technology is used, the Ekey typically communicates with an EDL or other suitable electronic lock or access device. The EDL or other electronic access device can then read a particular identification (“ID”) code on the Ekey (often supported by a cryptographic security means) and provide or deny access based upon whether the ID code is acceptable to the EDL.
Many types of Ekey and EDL technologies require that the card or key fob being used be physically placed into contact with the EDL, such as in the case of magnetic stripe cards, smart cards, memory chip cards and fobs. Of course, such applications tend to require the user to physically manipulate the Ekey, such as to insert a card into a slot in the EDL. Other types of technologies can allow for applications where no physical contact is required between the Ekey and EDL, such as in the case of NFC cards and readers. Unfortunately, NFC applications typically need the Ekey to be within a few centimeters of the EDL or other reader, such that users are usually required to handle or otherwise manipulate the Ekey to some degree.
Long range keys (“LR-Keys”) operate like Ekeys albeit at much greater distance. A typical challenge of long distance operation is avoiding inadvertently opening the EDL not just from outside the door but inside the door (the latter being a serious problem).
Recent shootings at school and university campuses have demonstrated the importance of protecting staff and students from harm in the event of a shooter on campus. One component of the protection strategy involves preventing the shooter from entering buildings and rooms that may be populated by potential victims.
One protection method is called ‘Lockdown’, where entrance through doors is limited by the door lock to a very small set of people, such as police and emergency responders. Even if the shooter possesses a valid Ekey (possibly obtained by threat of force from an innocent person having normal access), the shooter would not be able to unlock a door lock that is in ‘Lockdown’ mode. The shooter would thus be obstructed from entering a room full of innocent people (potential victims).
In a classical (prior art) access control system (also known as building security system), the lockdown command is issued centrally, for example by campus police, after an incident is reported. Campus police would initiate the lockdown on an access control system's control station that is connected to EDLs through a wired or wireless network, and the access control system would affect lockdown commands to the EDLs over that network. One disadvantage of this approach is a long response time: A person on campus has to call or by some means notify campus police. Police then have to manually activate the lockdown and the lockdown command has to propagate to the door readers. Another potential disadvantage is that this method has one or more single points of failure, including the access control system's server (central control station) and its network connections. To overcome this disadvantage, one has to invest in fail-safe or fault-tolerant:
a. Server computer hardware & storage sub-system
b. Server software system
c. Network switches and cabling
all of which is extremely expensive to build, maintain, certify and check system integrity at all times. It is rare to find an enterprise that is willing to invest so heavily in such a system, due to above mentioned difficulties.
A second prior art method that is sometimes employed is to allow users to initiate a lockdown manually on individual doors. While this has the advantage that it immediately protects the individual user who activates the lockdown, it does not protect people in other rooms who are not yet aware of the danger.
There are some prior art ACS that employ wireless EDLs that allow lockdown of all EDLs connected to a set of wireless routers (that provide wireless connectivity to the wireless EDLs). Such systems are inflexible because the need for locking down a specific set of EDLs can rarely be physically controlled such that a specific wireless router provides connectivity only to the desired set of EDLs (nothing more and nothing less).
In this disclosure we present methods and systems that help to overcome many disadvantages of the traditional methods that were described above, and other disadvantages, and we provide novel functionality.
Some embodiments of the invention use a special type of LR-Ekey called “Ukey”, available from SecureALL Corporation of California. A Ukey has many breakthrough technologies that enable a hands-free key to provide door access. A Ukey also has far field wireless communication capability allowing it to communicate with a compatible EDL or wireless router devices located at substantial distance. But the invention is not limited to such embodiments.
An Ekey and an EDL may have electronic components as described, for example, in US pre-grant publication US 2006/0164208 A1, incorporated herein by reference. The Ekey and EDL components can be modified to provide the functionality according to some embodiments of the present invention.
In the figures, elements based on the same reference number (E.g. 503, 503U, 503D, 503W, 503L, 503R; or 504, 504D, 504L) denote the same or similar parts, having the same or similar functionality.
Action buttons (AB) could be classified into two categories:
Various kinds of AB 503 allow an operator to raise an alarm message in response to a threat or emergency. Action buttons can be alternatively configured to unlock a set of doors, or some other action by sending a different message.
In some embodiments, action buttons have to be pressed for a certain period of time, while in other embodiments, action buttons have to be pressed and released a certain number of times (within a specific time interval) in order to be activated (this could be to reduce the possibility of accidental/un-intentional operation). ABs may also have other pressing sequences to execute a self-test procedure, and yet another pressing sequence to generate a test action button communication with the ASS (to facilitate periodic full system test/certification)
While action buttons can be implemented as push-buttons, this invention is not limited to any implementation or activation procedure of action buttons. Non limiting examples:
In a preferred embodiment of the invention all data network links are encrypted.
In a preferred embodiment of the invention all ACS devices and computers (E.g. EDL, Ekey, Router, AB, ASS, PAC etc) that want to communicate to each other use secured end-to-end encryption using symmetric keys that are securely established using asymmetric cryptography (E.g. PKI/Public Key Infrastructure). This ensures that intervening network devices can't decrypt communication that is not meant for them or spoof the communication. In particular all operative messages, commands and event notifications are end-to-end encrypted.
A spare computer could act as a fail-over computer 514 to provide higher system availability by mitigating the risk of a single point of failure (due to any reason, e.g. failed server computer or software, software maintenance) of the SS computer that is running core-application 521 and PSSC. The fail-over computer 514 acts as a proxy to SS server 502.
The fail-over computer 514 runs a software component 522 that provides either a full feature replacement of the software running on SS 502, or another type of software that provides lesser but gracefully degraded functionality. The latter option allows easy and robust method to only provide the sub-set of functionality that demands high-availability. Lockdown is one such function that many customers demand to be highly-available, asking for protection against a single point of failure due to the server going down. In an another embodiment the Failover computer could run an application 538 that implements the functionality of LCD described later (
The computer 201 uses the wireless transceiver 207 to send messages (to router 504, or to ASS via router 504). The computer 201 can also receive command messages via the wireless transceiver 207, whereby it authenticates and decrypts the communication, interprets the command and performs the needed action.
The computer 201 controls the LED 211 and audio speaker 212 to provide status information or feedback to the User 13. The EDL 501 operates using the power available from battery 205, although one can alternatively use other power sources like mains AC power or an energy harvester. Power management 204 converts the available power from battery 205 to operating voltage suitable to operate various electronics circuit in the EDL 501. The EDL further includes an electro-mechanical actuator 208 that is controlled by the processor and can put a lock mechanism 209 into locked or unlocked mode. The lock mechanism, when it is in a locked state, secures the lock to the door jamb 210 to prevent the door from opening.
The EDL 501 communicates to Ekey 11 (or a subclass of EKey like LR-Ekey 12, or UKey) using a transceiver (207, 206) that is compatible with Ekeys. In an embodiment it has NFC Radio transceiver 206 to allow it to communicate with and read NFC-based Ekeys, as well as UHF radio transceiver 207 to allow it to communicate with and read BLE (Bluetooth Low Energy) based LR-Ekey 12. Various types of cryptographic techniques (E.g. PKI and AES) are used to secure information exchange and/or authenticate each other. A communication protocol is used to identify and authenticate each other and evaluate rules (Access Control rules) related to Ekey's access permissions for the EDL (at that moment of time), as a result of which the EDL unlocks if the Access Control rules passes. It is to be understood for the access control to work the Ekey's access permissions could be stored on the EDL or on the Ekey.
In some embodiment Ekey's “Lockdown level” is stored in the EDL's 501 memory 223, while in other embodiment it is stored in Ekey's 11 memory 216.
Core Application 521 is a group of software components that are generally important software components or services to realize a functional system. It comprises:
GUI based access to various classes of operators is provided by Role based GUI 523. Roles define a collection of GUI actions that an operator has privileges to use; it prevents an operator from using other capabilities of the operator interface. Typical set of roles are Security Guard Zone monitor 523S, Facilities Employee 523F, Process Owner 523P, Resource owner 523R and Applications administrator 523A.
Distinct software functions and features of the system are collated as various vertical applications 525. Each vertical application is packaged as a collection of various functionalities that the system provides. Each functionality is delivered by a set of software modules that use:
Network and Messaging function layer 524 provides network data connectivity to ACS devices (E.g. EDL, Router, AB, Ekey). It could run on a dedicated computer or on a shared computer that also runs other software applications. It comprises:
An EDL could be configured to allow access to a set of Ekeys S in ‘Normal’ state, and to a set of Ekeys T in ‘Lockdown’ state where set T is a subset of S (I.e. T ⊆ S). SecureALL Corporation has an Access Control System with remote lockdown capability such that when a user puts an EDL in lockdown by pressing the AB on the EDL in a certain specific way (E.g. presses the AB three times within 5 seconds) to signal lockdown, the EDL changes its operating mode from ‘Normal’ to ‘Lockdown’. In ‘Normal’ mode the EDL allows access when a user manipulates an Ekey on the EDL where the Ekey is an element of set S (I.e. {x|x∈S}), while in ‘Lockdown’ mode the EDL allows access to only those Ekeys that are members of set T (I.e. {x|x∈T}). In a preferred embodiment T⊂S (T is a proper subset of S) as it is simpler to implement and provides a more systematic way to configure the EDL's Ekey access permissions. Ekeys of set T can be given, for example, to a very small group of trained and trustworthy first responders (E.g. Police). When anybody puts the EDL in ‘Lockdown’ mode the EDL ignores any built-in schedule that keeps the EDL in an unlocked/open state (e.g. any mode that allows access to visitors that do not have an Ekey) or allows access to a set of Ekeys, possibly depending on the time and date. (Non-limiting example: In ‘Office’ mode of operation the EDL stays in an unlocked state without requiring an Ekey; thus visitors can enter the door, say, during guest hours, without an Ekey. At other hours the EDL goes into ‘Normal’ mode whereby it would unlock only when a person manipulates on the EDL with an Ekey which is an element of set S. Different sets S may be defined to correspond to different times and dates. For example, a first set S can be defined for Fridays, and a different set S for Mondays.). This type of EDL lockdown capability gives immediate protection to a person who sees an active shooter nearby and secures herself in a room by putting the EDL(s) of the room into ‘Lockdown’ mode, in which the EDL(s) prevents anyone (but the first responders with a first responders' Ekeys) from entering the room to harm her. This is because the active shooter is unlikely to have in his possession an Ekey that is a member of set T; even if he obtains by force an Ekey from an innocent bystander, the bystander is unlikely to be a first responder, and the bystander's Ekey will not grant access through the EDL that is in ‘Lockdown’ state. (This is sometimes referred to as ‘Local Lockdown’ (LLD) as the Lockdown initiating person physically interacts with the EDL to put it into ‘Lockdown’ mode.)
An EDL optionally gives a visual and/or audible indication to indicate that the EDL is entering the ‘Lockdown’ mode; in some cases the indication continues for as long as the EDL is in ‘Lockdown’ mode. The EDL also sends a message to the ASS when the EDL transitions into and out of ‘Lockdown’ mode. Further, the ASS could be configured to send out emails to (a priori) designated addresses with necessary details about the lockdown occurrence. The GUI Application 505 on PAC 512 prominently notifies (visually and/or audibly) to the operator of the occurrence of one or more EDLs going into ‘Lockdown’ mode.
In an embodiment when an EDL is in ‘Lockdown’ mode, and the user presses the AB on the EDL in a specific way (E.g. button kept pressed for 5 seconds) to signal a request to remove the lockdown condition, the EDL changes its operating mode from ‘Lockdown’ to ‘Normal’ (or in some embodiments from ‘Lockdown’ mode to the mode it was in immediately before ‘Lockdown’ was issued).
The LLD function could be misused as a prank play in some applications (E.g. elementary school) where children could manipulate the Lock's AB 503L to put the EDL in ‘Lockdown’ mode. In an embodiment of this invention the EDL is configured such that it will accept its AB 503L input only if an Ekey with access permission to the EDL has been read preferably within a configured period of time (timeout period). E.g. if an Ekey has access permission to the EDL, and the EDL reads the Ekey, the EDL allows the use of the AB for the next 20 seconds to put the EDL into ‘Lockdown’ mode. In some embodiments, the EDL supports reading and authenticating access to the Ekeys for the lockdown purposes (allowing the use of AB 503L) if the Ekey is outside the room but not if the Ekey is inside, or if the Ekey is inside but not if the Ekey is outside, or regardless of the Ekey position. Recognizing only the Ekeys located inside for putting the EDL in ‘Lockdown’ mode facilitates enabling only the authorized users to initiate the Lockdown mode, as unauthorized users are less likely to be inside. Further, regardless of whether the Ekeys are recognized outside, recognizing the Ekeys inside protects the users located inside from having to open the door and become exposed to an active shooter to initiate the Lockdown, as would be the case if only the Ekeys located outside were recognized. In another embodiment an EDL that supports LR-Ekeys provides more enhanced capabilities whereby the EDL will allow the use of AB 503L only as long as the EDL to LR-Ekey RF communication path loss (which is related to distance between the EDL and the LR-Ekey) is less than a configured threshold (meaning as long as the Ekey is within a programmed distance of the EDL. E.g. 4 ft.). The EDL estimates the RF communication path loss as measured by the EDL and/or the LR-Ekey by:
In an embodiment of this invention the EDL is configured such that it will accept its AB 503L input to change operating mode to ‘Lockdown’ only if an Ekey that has permission to put EDL into lockdown mode has been recently read (E.g. Ekey read within last 10 seconds). In another embodiment of this invention the EDL is configured such that it will accept its AB 503L input to change its operating mode from ‘Lockdown’ to another mode, only if an Ekey that has permission to put EDL out of lockdown mode has been recently read (E.g. Ekey read within last 10 seconds). This is useful in situations where a teacher's Ekey is required to put a EDL into ‘Lockdown’ mode while her students can't put EDL into ‘Lockdown’ mode, and if the EDL is put into ‘Lockdown’ mode, only first responder's Ekey can put the EDL back into ‘Normal’ mode of operation. Often there is a requirement that people who have access to the EDL should also have capability to put the EDL into ‘Lockdown’ mode. So in an embodiment the EDL is configured such that the set of authorized users' Ekeys that are permitted to change EDL's operating mode to Lockdown mode is same as the set of Ekeys that have access permission to unlock the EDL when the EDL is in ‘Normal’ mode of operation.
In an embodiment of this invention the EDL is configured such that it will accept a ‘Lockdown’ signal message from AB 503R only if an Ekey with access permission to the EDL has been read within a configured period of time (timeout period) or EDL to LR-Ekey RF communication path loss (which is related to distance between the EDL and the LR-Ekey) is less than a configured threshold (indicating the teacher is close by to the EDL). This limits misuse of this functionality by miscreants after the user who unlocked the EDL with her Ekey had left the scene.
In another embodiment the Ekey may be packaged with AB 503R functionality with common electronics to implement both the Ekey & AB 503R functions.
In another embodiment the Ekey's ability to put an EDL into LLD may be constrained by a schedule (E.g. days of week and start-end time). The schedule may be downloaded by the ASS to the EDL and/or Ekey. This allows separation of scheduled access to the EDL (and ACS function) and the ability to perform LLD.
In another embodiment the Ekey's ability to put an EDL into LLD may be on lease that has an expiration date & time. The ASS may periodically extend the lease. This prevents the possibility of misuse of the Ekey when it is lost.
It is understood that in some embodiments the ASS and an Ekey (E.g. LR-Ekey like UKey) can communicate with each other via router 504, or via EDL 501 (which in turn may use a router to connect to the ASS).
In another embodiment, when an EDL is put into LLD the EDL sends a ‘Lockdown’ signal message to the ASS and the ASS may be configured to communicate with a camera system to steer a specific camera towards the EDL and/or the space near the EDL and then send a communication to the system operator (E.g. GUI or email notification that may optionally have a link that allows the recipient to quickly access a camera's video stream).
Remote Lockdown: If there is an active shooter on the prowl in a facility, an ACS operator (E.g. security staff, campus police) using the GUI Application 505 can remotely lock down a set of EDLs. The operator uses GUI Application 505 to select a set of EDLs and issues a lockdown command. The GUI Application communicates with the ASS, which in turn communicates with the respective EDLs (via the data network) sending ‘Lockdown’ command messages. This is sometimes referred to as ‘Remote Lockdown’ (RLD) as the initiating person could be far away from the EDL on which the ‘Lockdown’ is being performed. In a preferred embodiment each communication link is individually encrypted and the command message is end-to-end encrypted such that intervening nodes of the data network can't decrypt, modify or spoof it.
In an embodiment the GUI Application that has a secure communication link with the ASS, communicates with the ASS requesting to put a set of EDLs into ‘Lockdown’ mode; the ASS in turn communicates with respective EDLs (via the data network), sending a ‘Lockdown’ command message to the set of EDLs.
Some prior art ACS have provided capability to lock down a set of EDLs using an AB. They typically used dumb AB 503D that are wired to the ASS 502.
In an embodiment of the present disclosure an EDL's has many modes of operation and ‘Lockdown’ mode is graded by many levels. An exemplary system would be such that:
In a narrower embodiment of the above method an EDL has many modes of operation and ‘Lockdown’ mode could be graded by many levels. An exemplary system would be such that:
In another preferred embodiment the Lockdown command message to the EDL carries optional arguments such as Lockdown level, duration of the Lockdown, absolute (UTC time) time for expiry of the Lockdown.
In another preferred embodiment the EDL will accept an Unlock command message and, in response, will keep the EDL in ‘Open’ mode (also known as ‘Unlock’ mode) whereby the EDL's ability to control entry into room is inoperative (this is unlike ‘Normal’ mode, that requires Ekey to unlock it and EDL stays unlocked only for a short period thereafter). The Unlock command could carry optional arguments such as duration of the unlock, absolute (e.g. UTC time) time for expiry of the Unlock command.
When the EDL is in ‘Lockdown’ mode or ‘Normal’ mode or ‘Open’ mode it would accept and operate on a subsequent:
In an embodiment of the present invention the ASS is configured such that an AB's Lockdown signal message is mapped to a Zone (i.e. mapped to put all EDLs in the Zone into “Lockdown” mode). The ASS is further configured such that when it receives a Lockdown signal message from an AB, it communicates with all EDLs of the Zone (via the data network) sending ‘Lockdown’ command messages. After sending the messages the ASS provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual information (E.g. LED indication, text), audible information (E.g. beep, voice annunciation) or haptic (tactile) response. This tells the users that the Lockdown is in progress. In another embodiment, after the ASS has received the delivery confirmation of ‘Lockdown’ command messages from all EDLs it provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual information, audible information or haptic response, indicating that all the connected EDLs that are part of the Zone are in ‘Lockdown’ mode.
In another embodiment the ASS, EDL and AB are configured for ‘Verification Testing’ that allows customer to periodically verify proper lockdown operation (without disturbing user's normal use of the EDL). The ASS is configured to temporarily operate in a special test mode such that when it receives a Lockdown signal message from an AB, it sends a ‘Lockdown Test’ command message to all EDLs of the Zone (via the data network), the EDL processes the message identical to ‘Lockdown’ command message (i.e. simulating the ‘Lockdown’ mode and sending a response back to the ASS indicating successful execution of the command) except that the EDL does not change the operating mode to ‘Lockdown’ (i.e. simulating the ‘Lockdown’ mode). After sending the messages the ASS provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual, audible or haptic feedback. Similarly, after the ASS has received delivery confirmation of the ‘Lockdown Test’ command message from all EDLs it provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual, audible or haptic feedback indicating that all the connected EDLs that are part of the Zone processed the “Lockdown Test” command message. This scenario works similarly when the ASS is configured to temporarily operate in a special test mode and the operator uses GUI Application 505 to remotely lock down a set of EDLs.
In another embodiment the AB has an additional sensor input that is designed so that it can be engaged with conscientious effort that puts the AB into “Lockdown test” mode and causes the AB to send a “Lockdown test” signal message to the ASS; in addition the AB optionally provides a feedback signal to the user in the form of visual, audible or haptic feedback that it is in “Lockdown test” mode. Upon receiving a “Lockdown test signal message” from an AB the ASS sends a ‘Lockdown Test’ command message to all EDLs of the Zones corresponding to the AB (via the data network). An EDL processes the message identical to a ‘Lockdown’ command message (i.e. simulating the ‘Lockdown’ mode and sending a response back to the ASS indicating successful execution of the command) except that it does not change the operating mode to ‘Lockdown’ (i.e. simulating the ‘Lockdown’ mode). After sending the messages to EDLs the ASS provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual, audible or haptic feedback. Similarly after the ASS has received delivery confirmations of ‘Lockdown Test’ command messages from all EDLs it provides a status update to the AB (that was the source of the Lockdown signal message) so that the AB can optionally provide a feedback signal to the user in the form of visual, audible or haptic feedback indicating that all the connected EDLs that are part of the Zone have processed the “Lockdown Test” command message.
In another embodiment the ASS periodically communicates (E.g. every 90 seconds) with all ABs to make sure the AB communication links are healthy and operational. The ASS is configured to generate an alarm (for display on GUI Application 505 and/or email notification) if it finds that an AB communication link is down beyond a configured amount of time. In another embodiment the AB is configured such that if it senses that a communication link is down beyond a configured amount of time, it generates a visual, audible or haptic response indicating that the AB is not usable.
In an embodiment an AB has a seismic sensor, such that when earthquake stronger than certain magnitude occurs the AB generates a seismic signal message to the system to unlock a set of EDLs, allowing trapped people to rapidly egress the building via doors that normally require an Ekey with access permission, while allowing rescue workers easier access.
In an embodiment, devices such as ABs and/or EDLs (E.g. AB 503Q imbedded in EDL) include vibration sensors and report vibration events to the server. In the event that the server software application receives reports with an intensity above a certain threshold from a large enough number of devices indicating earthquake (e.g. a number larger than a predefined value), the server can issue a command to a set of EDLs and configure them to be in open mode or unlocked state for a configured duration.
Reflex Lockdown
Of the many disadvantages of prior art lockdown solution are:
An embodiment of the present invention is automatic ‘Reflex Lockdown’, whereby ASS is configured to require the receipt of two or more ‘Lockdown’ signal message from AB s within temporal and/or spatial proximity resulting in an automatic recognition of an Active Shooter scenario and triggering an Active Shooter workflow. It is to be understood that this capability could also be used to perform other automatic actions like
In a non-limiting example of ‘Reflex Lockdown’, the ASS, upon receipt of at least two lockdown signal messages from separate Door ABs 503L located in a building within 5 minutes, may be configured to send lockdown command messages to all EDLs in a building or collection of EDLs (referred to as Zone) and alert security personnel (via a GUI Application, text, email, automated telephone call, invocation of applications like the “Pager duty” Alert management and notification system). When a Zone is in Reflex Lockdown, if the ASS additionally receives another AB lockdown signal message from a second building, the ASS may also be configured to send lockdown command messages to all EDLs in an expanded set of buildings or expanded set of Zones or even all campus.
In an embodiment the ASS uses a rule-based evaluation to determine whether to trigger a Reflex lockdown based on the time sequence of lockdown signal messages and/or the proximity of physical locations of the AB that generated the lockdown signal message. In another evaluation variant the different types of AB (E.g. AB 503L that only puts a single EDL into ‘Lockdown’ mode, versus other types of AB that can put many EDLs into ‘Lockdown’ mode) are given a weightage based on their importance (non-limiting example: number of EDL's that an AB can put in ‘Lockdown’ mode, or if an AB 503L belongs to an EDL that is a gateway to large number of susceptible victims). In another evaluation variant if the room has more than one door-locks, a lockdown signal from a Door AB 503L in the room, results in sending a lockdown command message to all other EDLs in the room.
In another embodiment, Artificial Intelligence 544 (E.g. machine learning, Artificial Neural Network based cognition method) is used to recognize conditions necessary to trigger a Reflex-lockdown and determine the scope (the set of doors) of the Reflex-lockdown. Machine learning is automatically performed over a period of time, reducing cost of developing and maintaining very complex rule-based logic function. Machine learning allows the system to automatically learn over period of time ‘what is NOT an active shooter condition’. This helps reduce type-1 errors in identifying active shooter situation. Machine learning could further be supplemented to learn to recognize an active shooter situation by conducting active shooter drill in the campus, which reduces type-2 errors.
In an embodiment, a facility, building, or zone may be defined with an activation-threshold that triggers automatic lockdown of some or all its constituent EDLs, when an activation function exceeds activation threshold. For the purpose of triggering, a user defined activation function is used that is evaluated according to the following expression (1):
Function (time, Set of EDLs with integrated AB 503L that sent ‘Lockdown’ signal message, Spatial density of EDLs with integrated AB 503L that sent ‘Lockdown’ signal message) (1)
In this expression,
A statement that a function “increases” or “decreases” in some selected argument (as the other arguments are held constant) does not mean strict increasing or decreasing at every value of the selected argument. For example, an increasing function may stay constant for some adjacent values of the selected argument or in a sub-range of selected argument's values. Strict increasing or decreasing occurs in at least a sub-range of the selected argument's values, but may or may not occur at every value of the argument. In some embodiments, there is a set of fixed values of the other arguments for which the function stays constant in the selected argument over the entire range of the selected argument's values. In other embodiments, there is no such set of fixed values.
In an embodiment, a facility, building, or zone may be provided with multiple progressively increasing activation function threshold values that result in automatic lockdowns of progressively larger sets of EDLs when the activation function exceeds a minimum threshold.
Another possible activation function, defined for a facility, building, or zone, is as in the following expression (2):
Function (time, Set of EDLs with integrated AB 503L that sent ‘Lockdown’ signal message, Spatial density of EDLs with integrated AB 503L that sent ‘Lockdown’ signal message, Set of ABs that sent ‘Lockdown’ signal message with associated Zone comprising many EDLs) (2)
Here “time”, “Set of EDLs”, and “Spatial Density” are as for Function (1) above. Function (2) increases or decreases in these arguments the same as Function (1).
The “Set of ABs” argument indicates an importance of the ABs within the Zone. The activation function value increases when the importance increases. For example, each AB can be assigned an importance parameter, and “Set of ABs” can be calculated as the sum of the importance parameters of the ABs that sent the Lockdown” signal message from the associated Zone. See also the discussion of
The remaining properties of Function (2) can be as described above for Function (1).
Other activation types are possible; some are described below in connection with
The system can thus be configured such that:
In an embodiment, the activation function value is derived from Center of Activation function pressure (CoAFP). CoAFP is a useful concept similar to Fluid-Mechanic's center of pressure, whereby the constituent AB's weighted impulse 600 (
In an embodiment the above method of evaluating Center of Activation function pressure is first calculated to determine the CoAFP vector location 603 on the floor plan and then the CoAFP magnitude is calculated as above (sum of impulses 600) except that a correction factor is given to an AB's weighted impulse 600 (each impulse 600 is weighted with its correction factor), where the correction factor is higher for an AB with a shorter distance to the CoAFP vector location 603 (E.g. correction factor of 1.6 for an AB located at a shorter distance, compared to correction factor of 0.7 for an AB located at a longer distance). This methodology allows realization of Activation functions that are sensitive to spatial density of ABs that had generated ‘Lockdown’ signal messages in response to an active shooter scenario.
In an embodiment, the higher is the magnitude of the activation function the greater is its range coverage, i.e. the distance from the Center of Activation function vector location 603 to the EDLs that should be locked down, i.e. put into ‘Lockdown’ mode. The distance could be measured along a straight line, or in some other way, E.g. as the shortest walking distance. The distance may include weighted lengths, e.g. the shortest working distance can provide a greater weight compared to a segment with a staircase or elevator.
In another embodiment
In some embodiments AB 503L could generate a ‘Lockdown’ signal message irrespective of its host EDL's 501 ‘Lockdown’ mode. This allows the system to know where potential victims have taken refuge as well as their desire to inform others of potential personal harm. AB will generate ‘Lockdown’ signal message only once; repeatedly pressing the AB will not result in sending the signal again, the signal sending capability will be armed again when the host's EDL operating mode changes to a non-Lockdown mode.
In an embodiment, a facility, building, or zone may be defined with an activation threshold that triggers automatic lockdown of some or all its constituent EDLs. The activation function is continuously evaluated such that if more EDLs become eligible to be put in ‘Lockdown’ mode due to changing activation threshold and location of the ABs that generate ‘Lockdown’ signal messages, those additional EDLs are put in ‘Lockdown’ mode.
In an embodiment of the present disclosure the EDL has a sensor that measures its own temperature and optionally the temperature nearby (for example by using a pyroelectric sensor). The temperature information could be used to build a temperature map (also called a heat map) of the building floors. It is understood that instead of an EDL one can also have a dedicated device (with communication and processing capability similar to that of an EDL) that measures temperature.
The “Hot” signal message and/or “Heating” signal message could be used similar to the Reflex-Lockdown system describer earlier to generate an alarm for the system operator (E.g. email alert), unlock a set of EDLs (so people in the building can save themselves by exiting through doors that would normally be locked) and possibly interface with the building's fire control system to proactively contain the spread of fire.
Similar to the Center of Activation function described earlier one can also generate ‘Center of Temperature-differential’ function whose value exceeding a defined threshold could result in generating an alarm message.
Reflex-Lockdown—Failover
The system described thus far is still centrally controlled and dependent on the availability of the ASS which is impacted by unscheduled (E.g. hardware failure, software failure) and scheduled down time (hardware & software maintenance, software upgrade etc). While customers can live with the temporary unavailability of some aspects of ACS functionality (like programming access updates for certain keys for certain EDLs, access log reports), other functionalities (like Lockdown, Reflex lockdown, remotely executing an EDL-Unlock or Lockdown command) are so critical that only a short downtime on the order of a minute is acceptable.
One embodiment of this disclosure is provisioned with a Fall-back application 522 that provides a subset of the functionality of the ASS 502, resulting in graceful degradation of service instead of complete failure. Fall-back application 522 typically runs on a separate computer host 514.
Fall-back application 522 is typically configured to maintain a copy of the critical information 543 that is required for its autonomous operation, such that the information is current (or nearly current) to the information in Core Application 521. When the ASS comes back on line, it synchronizes the critical information that Fall-back application 522 might have modified.
One embodiment of this disclosure is provisioned with a Fall-back application 522 comprising a software application referenced herein as “LCD” 538 (
The Network and Messaging function layer 524 (
The ASS 502 is normally in a state 1021, waiting to receive Lockdown Signal Messages from EDLs or ABs. After receiving the Lockdown Signal Message from EDL 501a, the ASS enters state 1022 and stores information about the lockdown event, such as location, time, and a weight based on importance. In state 1023 the ASS evaluates rules or functions (such as the function described above) to determine whether or not a reflex lockdown should be triggered and on what set of EDLs. State 1024 represents the decision point: If the requirements for a reflex lockdown are not met, the ASS goes back to state 1021 where it waits for further events. If the requirements are met, the ASS transitions to state 1025 where it sends Lockdown Command Messages to the set of EDLs that was determined in 1023. Then, in state 1026 the ASS sends notifications to security personnel by email, text message, or similar methods.
In this example, EDLs 501c and 501d receive the Lockdown Command Messages in states 1030a and 1030b, respectively. As a response they enter lockdown mode and states 1031a and 1031b.
Distributed—Lockdown
The system described thus far is still centrally controlled and the ASS or its network connection is still a single point of failure. To overcome this limitation requires expensive fault-tolerance computer, network and application software.
This disclosure presents a Distributed-Lockdown (DL) mode of operation that is resilient to failure of the ASS and operates gracefully even if the network system breaks down into multiple disconnected portions of network. This greatly enhances the robustness of AB-initiated lockdown functionality, without entailing cost and complexity of building and maintaining a system that requires fail-safe ASS hardware, ASS software and network. It should be understood that in the DL mode not only lockdown functions but also other AB commands or functions could be performed using the methodology of this disclosure.
An embodiment of Router 504 is capable of performing the additional function of a Distributed-Lockdown executor when operating in the Distributed-Lockdown (DL) mode of operation. It has additional control execution functions to implement a distributed operation business logic, where it coordinates and controls downstream network devices (like ABs, Ekeys and EDLs to which it provides network connectivity) and other peer routers that are reachable via the available data network. It is to be understood that the router can in DL mode also perform other functions apart from lockdown related functions. It also accepts information or command requests from other Routers.
It is to be understood that all communication messages are encrypted. In a preferred embodiment PKI-based encryption methodology is used for mutual authentication and key distribution as explained earlier.
In another embodiment the Router 504 has the ability to detect the loss of communication with the ASS host (or the Backup core application 522), as a result of which it reconfigures itself to change its operating mode to DL mode. It also has ability to detect re-establishment of communication with the ASS host (or the Backup core application 522), as a result of which it reconfigures itself and changes its operating mode as per ASS instructions.
An AB's other messages (E.g. a Request-Unlock signal message) may similarly have an associated AB-Job object whose operation code may for example be ‘Unlock’ that results in the list of doors being Unlocked for a configured duration of time.
An exemplary relationship between AB 503, Zone 550 and EDL 501 is shown as per earlier description for
When AB 503 generates a ‘Lockdown’ signal message the AB sends a message containing a corresponding AB-Job (with Operation code=Lockdown) to the router that the AB is currently connected to (let us call that router as Head router). The Head router, when receiving the AB's message 551:
When ABs and Routers have network connectivity with the ASS they synchronize their AB-Job objects with the information in the ASS (recall that some Routers may be implemented as hardwired AB 503. See
An example of graceful degradation can be seen using
Generally during network failure the network system breaks down into multiple disconnected network portions, where routers of each portion (e.g. routers located in a building) continue to have connectivity with each other. A network portion may include multiple buildings, so in some cases the routers in one building are able to connect to routers in some other buildings. Distributed Lockdown capability described in this disclosure is able to provide valuable albeit restricted service in such network failure scenarios.
Activity 1120 represents the activation of AB 503W by user 13. After activation, the AB transmits its job description (message 1121a) to router 504a which is the router that the AB is connected with (head router). Router 504a reads the AB Job and determines that it has connectivity with EDL 501a, which is one of the EDLs included in the job. The router sends lockdown command message 1122a to that EDL.
Router 504a further determines that more EDLs need to be locked down that are not directly connected, but may be connected to router 504b which is also included in the AB Job. Therefore router 504a sends a message 1121b, including the AB Job description, to router 504b (tail router). Router 504b sends lockdown command messages 1122b and 1122c to EDLs 501b and 501c, respectively.
After successful transmission of the lockdown command messages, router 504b sends acknowledgment 1123b to router 504a, which in turn sends acknowledgment 1123a back to the originating AB 503W. In 1130, the AB notifies the user of the successful execution of the lockdown.
Distributed Reflex Lockdown
The Reflex-Lockdown system described thus far is still centrally controlled and the ASS or its network connection is still a single point of failure. To overcome this limitation requires expensive fault-tolerance computer, network and application software.
This disclosure provides a Distributed-Reflex-Lockdown (DRL) mode of operation that is resilient to failure of ASS and operates gracefully even if the network system breaks down into multiple disconnected portions. This greatly enhances the robustness of the AB-initiated Reflex-lockdown function, without entailing cost and complexity of building and maintaining a system that requires fail-safe ASS hardware, ASS software and network.
An embodiment, Router 504 is capable of performing the additional function of a Local Coordinator when operating in Local Coordinator Device (LCD) mode of operation. It has additional control execution functions to implement a distributed operation business logic, where it supervises, coordinates and controls routers that are reachable via the available data network and operating in Distributed-Lockdown (DL) mode of operation. Routers in DL mode of operations negotiate among themselves such that one amongst them take on the additional function of Local Coordinator and operate in ‘LCD’ mode. The Local Coordinator also provides the regular functionality of router's DL mode (i.e. for the hosting router).
A router 504L in LCD mode provides Reflex lockdown functions for all EDLs that are reachable via the connectivity provided by the current state of the network (E.g. Network section-1 in
In an embodiment, the Routers 504 have ability to detect loss of communication with the ASS host (or the Backup core application 522) as a result of which it reconfigures itself to change its operating mode to DL mode. It also has ability to detect re-establishment of communication with the ASS host (or the Backup core application 522) as a result of which it reconfigures and change its operating mode as per ASS instruction.
After all Routers 504 in an island network section change their operating mode to ‘DL’ mode, they perform the following operations:
The LCD router 504L performs the function of Reflex Lockdown using similar function and methodology as the ASS as described in the section titled “REFLEX LOCKDOWN” above, except that:
An Ekey and an EDL may have electronic components as described, for example, in US pre-grant publication US 2006/0164208 A1, incorporated herein by reference, or US 2013/0247153 A1, incorporated herein by reference. The Ekey and EDL components can be modified to provide the functionality according to some embodiments of the present invention. For example, the EDL may have a memory that stores its normal operation schedule, i.e. the various times at which circuit Ekeys, identified by IDs in the memory, have access to the EDL, i.e. can unlock the EDL. The EDL memory may store a different set of Ekey identifiers that have access in the lockdown mode, or at each grade of lockdown as described above.
When an AB and/or a Router have network connectivity with the ASS they periodically synchronize their AB-Job objects as well as the information model for Reflex-Lockdown. Routers may further download from the ASS the operative programming for analyzing, processing and operating on AB signal messages.
Some embodiments are defined by the following numbered clauses:
Refer to
This disclosure teaches a method to greatly increase the speed of execution of time critical communication/commands. The following description uses “Lockdown” as example but it is understood that the method could be used for other operations and scenarios.
A two phase communication scenario between ASS and EDL is taught (although it could be also applicable for three or more phase communication scenario without altering the spirit of the disclosure). Let us consider
In the first phase the ASS sends individual messages to all routers in set B where each message comprises:
In the second phase the ASS sends individual messages to all EDLs in set A.
Upon receiving the first phase message from the ASS, the router in turn sends a suitable message to all EDLs to which it is providing connectivity, to execute the ASS requested operation. This could use communication broadcast method and/or individual point-to-point communication with the EDL. Typically, the Router to EDL communication is cryptographically secure (using prior art methods to authenticate and establish cryptographically secure communication). The EDLs are configured to accept such request message from the Router. To further increase security the EDL may optionally require a valid ASS provided token. As an example, the First phase message from ASS to router could be to lockdown EDL1, EDL2, EDL3 for 5 minutes.
As part of the second phase, when the EDL receives message from the ASS (via the Router), it executes the ASS requested operation (that could supersede the execution of command received from the router during the first phase). As an example, the second phase message from ASS to EDL could be to lockdown for 120 minutes.
The net effect is that the ASS has to do far less processing to quickly generate and send messages to a fewer number of routers in set B (compared to the number of EDLs), and each router can immediately take action to communicate with its respective set of EDLs as soon as possible, so that it has desired effect on the EDLs quickly. Later the ASS sends a suitable end-to-end message to all EDLs asking to perform desired action. A well-designed system has most robust cryptographic security for end-to-end messages. Between the time an EDL receives the first phase message and the second phase message the overall security may be a little less robust compared to end-to-end encryption. With this method the system gets the benefit of speed as well as cryptographic security.
Embodiments of the disclosure described above are exemplary only. One skilled in the art may recognize various alternative embodiments from those specifically disclosed. Those alternative embodiments are also intended to be within the scope of this disclosure. As such, the disclosure is limited only by the following claims.
The present application claims priority of U.S. provisional patent application No. 62/524,907, filed Jun. 26, 2017, incorporated herein by reference. This application is also a continuation-in-part of U.S. patent application Ser. No. 16/019,503, filed on Jun. 26, 2018, incorporated herein by reference, which is a continuation-in-part of U.S. patent application Ser. No. 15/473,224 (published as US 2017/0338848 A1) filed on Mar. 29, 2017, incorporated herein by reference, which is a continuation-in-part of U.S. patent application of Ser. No. 14/444,949 filed Jul. 28, 2014 (now U.S. Pat. No. 9,642,089 B2), which application is incorporated herein by reference. The aforementioned application Ser. No. 14/444,949 is also: 1. A continuation-in-part (CIP) of U.S. patent application Ser. No. 13/747,362 filed on Jan. 22, 2013, incorporated herein by reference, which is a continuation of U.S. patent application of U.S. patent application Ser. No. 12/500,587 filed Jul. 9, 2009 (now U.S. Pat. No. 8,472,507), which application is incorporated herein by reference, which claims priority of U.S. provisional patent application 61/079,435 filed Jul. 9, 2008, incorporated herein by reference. 2. A continuation-in-part of U.S. patent application Ser. No. 13/340,520, filed Dec. 29, 2011, incorporated herein by reference, which claims priority of U.S. provisional patent application No. 61/428,155 filed Dec. 29, 2010, incorporated herein by reference. 3. A continuation-in-part of U.S. patent application Ser. No. 13/691,626 filed Nov. 30, 2012, incorporated herein by reference, which claims priority of U.S. provisional patent application No. 61/565,450 filed Nov. 30, 2011, incorporated herein by reference. 4. A continuation-in-part of U.S. patent application Ser. No. 13/843,757 filed Mar. 15, 2013, incorporated herein by reference, which claims priority of U.S. provisional patent application No. 61/611,577 filed Mar. 16, 2012, incorporated herein by reference. 5. A continuation-in-part of U.S. patent application Ser. No. 13/841,079 filed Mar. 15, 2013, incorporated herein by reference, which claims priority of U.S. provisional patent application No. 61/611,575 filed Mar. 16, 2012, incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3097301 | Sharpe et al. | Jul 1963 | A |
| 4036178 | Lee et al. | Jul 1977 | A |
| 4071713 | Sencer | Jan 1978 | A |
| 4200871 | Roeder et al. | Apr 1980 | A |
| 4839640 | Ozer et al. | Jun 1989 | A |
| 4853704 | Diaz et al. | Aug 1989 | A |
| 4855749 | Defonzo | Aug 1989 | A |
| 4898010 | Futami et al. | Feb 1990 | A |
| 4936316 | Jewett | Jun 1990 | A |
| 4978965 | Mohuchy | Dec 1990 | A |
| 5023597 | Salisbury | Jun 1991 | A |
| 5036335 | Ram | Jul 1991 | A |
| 5187489 | Whelan et al. | Feb 1993 | A |
| 5252960 | Duhame | Oct 1993 | A |
| 5293087 | Hamano et al. | Mar 1994 | A |
| 5387993 | Heller et al. | Feb 1995 | A |
| 5473318 | Martel | Dec 1995 | A |
| 5485577 | Eyer et al. | Jan 1996 | A |
| 5515036 | Waraksa et al. | May 1996 | A |
| 5519408 | Schnetzer | May 1996 | A |
| 5530839 | Komoto | Jun 1996 | A |
| 5557291 | Chu et al. | Sep 1996 | A |
| 5586121 | Moura et al. | Dec 1996 | A |
| 5602535 | Boyles et al. | Feb 1997 | A |
| 5649099 | Theimer et al. | Jul 1997 | A |
| 5719564 | Sears | Feb 1998 | A |
| 5774064 | Lambropoulos et al. | Jun 1998 | A |
| 5815811 | Pinard et al. | Sep 1998 | A |
| 5878134 | Handelman et al. | Mar 1999 | A |
| 5922049 | Radia et al. | Jul 1999 | A |
| 5933074 | Settles et al. | Aug 1999 | A |
| 5940510 | Curry et al. | Aug 1999 | A |
| 5973611 | Kulha et al. | Oct 1999 | A |
| 6002332 | King | Dec 1999 | A |
| 6007338 | Dinunzio et al. | Dec 1999 | A |
| 6008727 | Want et al. | Dec 1999 | A |
| 6020733 | Bradley | Feb 2000 | A |
| 6041411 | Wyatt | Mar 2000 | A |
| 6043785 | Marino | Mar 2000 | A |
| 6064309 | Sellers et al. | May 2000 | A |
| 6097301 | Tuttle | Aug 2000 | A |
| 6107934 | Andreou et al. | Aug 2000 | A |
| 6111977 | Scott et al. | Aug 2000 | A |
| 6219439 | Burger | Apr 2001 | B1 |
| 6225950 | Johansson et al. | May 2001 | B1 |
| 6236335 | Goodwin, III | May 2001 | B1 |
| 6304168 | Ohta et al. | Oct 2001 | B1 |
| 6304226 | Brown | Oct 2001 | B1 |
| 6308181 | Jarvis | Oct 2001 | B1 |
| 6329909 | Siedentop et al. | Dec 2001 | B1 |
| 6337628 | Campana, Jr. | Jan 2002 | B2 |
| 6518882 | Johnson et al. | Feb 2003 | B2 |
| 6570487 | Steeves | May 2003 | B1 |
| 6690259 | Aslanidis et al. | Feb 2004 | B2 |
| 6713895 | Krapfl | Mar 2004 | B1 |
| 6816083 | Brandt | Nov 2004 | B2 |
| 6837427 | Overhultz et al. | Jan 2005 | B2 |
| 6873703 | Enriquez | Mar 2005 | B1 |
| 6876334 | Song et al. | Apr 2005 | B2 |
| 6888459 | Stilp | May 2005 | B2 |
| 6967587 | Snell et al. | Nov 2005 | B2 |
| 6972660 | Mongomery, Jr. et al. | Dec 2005 | B1 |
| 6975202 | Rodriguez et al. | Dec 2005 | B1 |
| 6989732 | Fisher | Jan 2006 | B2 |
| 7012503 | Nielsen | Mar 2006 | B2 |
| 7019617 | Pratt et al. | Mar 2006 | B2 |
| 7106246 | Lindell | Sep 2006 | B1 |
| 7142838 | Rotzol | Nov 2006 | B2 |
| 7149849 | Wall et al. | Dec 2006 | B2 |
| 7183897 | Tang et al. | Feb 2007 | B2 |
| 7199634 | Cho et al. | Apr 2007 | B2 |
| 7227506 | Lewis, Jr. | Jun 2007 | B1 |
| 7301437 | Sasaki et al. | Nov 2007 | B2 |
| 7366812 | Lambourn et al. | Apr 2008 | B2 |
| 7446644 | Schaffzin et al. | Nov 2008 | B2 |
| 7463134 | Stilley | Dec 2008 | B1 |
| 7487538 | Mok | Feb 2009 | B2 |
| 7499283 | De Los Santos et al. | Mar 2009 | B2 |
| 7526934 | Conforti | May 2009 | B2 |
| 7577496 | Walker et al. | Aug 2009 | B2 |
| 7617522 | Schmidt et al. | Nov 2009 | B2 |
| 7652632 | Shtrom | Jan 2010 | B2 |
| 7668830 | Hakala | Feb 2010 | B2 |
| 7688179 | Kurpinski et al. | Mar 2010 | B2 |
| 7689196 | Hutchinson et al. | Mar 2010 | B2 |
| 7755482 | Hubbard | Jul 2010 | B2 |
| 7792861 | Kudoh et al. | Sep 2010 | B2 |
| 7804458 | Montgomery et al. | Sep 2010 | B2 |
| 7805169 | Hicks, III | Sep 2010 | B2 |
| 7844377 | Oota | Nov 2010 | B2 |
| 7856448 | Sheehan | Dec 2010 | B2 |
| 7894810 | Feher | Feb 2011 | B2 |
| 7898382 | Berstis et al. | Mar 2011 | B2 |
| 7933835 | Keane et al. | Apr 2011 | B2 |
| 7933925 | Sreedhar | Apr 2011 | B2 |
| 7953823 | Rider et al. | May 2011 | B2 |
| 3005777 | Owen et al. | Aug 2011 | A1 |
| 3031725 | Calin | Oct 2011 | A1 |
| 8044797 | Brommer et al. | Oct 2011 | B2 |
| 8059628 | Bradley et al. | Nov 2011 | B2 |
| 8102239 | Woo | Jan 2012 | B2 |
| 8141296 | Bem | Mar 2012 | B2 |
| 8149087 | Brillon | Apr 2012 | B2 |
| 8194571 | Herrmann et al. | Jun 2012 | B2 |
| 8224313 | Howarter | Jul 2012 | B2 |
| 8228165 | Marchetto et al. | Jul 2012 | B2 |
| 8233420 | Choi et al. | Jul 2012 | B2 |
| 8244762 | Cimino | Aug 2012 | B2 |
| 8245291 | Kumar et al. | Aug 2012 | B2 |
| 8249910 | Wellman et al. | Aug 2012 | B2 |
| 8251287 | Kochevar | Aug 2012 | B2 |
| 8258920 | Crucs | Sep 2012 | B2 |
| 8271336 | Mikurak | Sep 2012 | B2 |
| 8279077 | Liff et al. | Oct 2012 | B1 |
| 8310340 | Sikora et al. | Nov 2012 | B2 |
| 8319605 | Hassan et al. | Nov 2012 | B2 |
| 8340975 | Roseberger | Dec 2012 | B1 |
| 8391260 | Kopikare et al. | Mar 2013 | B1 |
| 8428079 | Lambert et al. | Apr 2013 | B1 |
| 8473192 | Hannah et al. | Jun 2013 | B2 |
| 8682347 | Hepo-Oja | Mar 2014 | B2 |
| 8693453 | Priyantha et al. | Apr 2014 | B2 |
| 8717923 | Vedantham et al. | May 2014 | B2 |
| 9007173 | McIntyre et al. | Apr 2015 | B2 |
| 20020013909 | Baumeister et al. | Jan 2002 | A1 |
| 20020034321 | Saito et al. | Mar 2002 | A1 |
| 20020091944 | Anderson | Jul 2002 | A1 |
| 20020099945 | Mclintock et al. | Jul 2002 | A1 |
| 20020111919 | Weller et al. | Aug 2002 | A1 |
| 20030034877 | Miller et al. | Feb 2003 | A1 |
| 20030046578 | Brown et al. | Mar 2003 | A1 |
| 20030119568 | Menard | Jun 2003 | A1 |
| 20030142737 | Tarng | Jul 2003 | A1 |
| 20030174095 | Sievenpiper | Sep 2003 | A1 |
| 20030214450 | Lynch et al. | Nov 2003 | A1 |
| 20040174271 | Welles et al. | Sep 2004 | A1 |
| 20040192222 | Vaisanen et al. | Sep 2004 | A1 |
| 20040227656 | Asakura et al. | Nov 2004 | A1 |
| 20040229560 | Maloney | Nov 2004 | A1 |
| 20040259544 | Amos | Dec 2004 | A1 |
| 20050040933 | Huntzicker | Feb 2005 | A1 |
| 20050063348 | Donovan | Mar 2005 | A1 |
| 20050138046 | Miettinen et al. | Jun 2005 | A1 |
| 20050215274 | Matson et al. | Sep 2005 | A1 |
| 20060008085 | Matsuo | Jan 2006 | A1 |
| 20060018139 | Kilomeitsev et al. | Jan 2006 | A1 |
| 20060030373 | Park | Feb 2006 | A1 |
| 20060100000 | Marples et al. | May 2006 | A1 |
| 20060129847 | Pitsos | Jun 2006 | A1 |
| 20060132284 | Murphy et al. | Jun 2006 | A1 |
| 20060136390 | Zhao et al. | Jun 2006 | A1 |
| 20060154708 | Bogner | Jul 2006 | A1 |
| 20060156018 | Lauer et al. | Jul 2006 | A1 |
| 20060164208 | Schaffzin et al. | Jul 2006 | A1 |
| 20060222118 | Murthy et al. | Oct 2006 | A1 |
| 20070001816 | Lindley et al. | Jan 2007 | A1 |
| 20070038344 | Oota | Feb 2007 | A1 |
| 20070073694 | Picault et al. | Mar 2007 | A1 |
| 20070103367 | Wang | May 2007 | A1 |
| 20070105548 | Mohan et al. | May 2007 | A1 |
| 20070111746 | Anderson | May 2007 | A1 |
| 20070149257 | Cheresh et al. | Jun 2007 | A1 |
| 20070176739 | Raheman | Aug 2007 | A1 |
| 20070183449 | Beagley et al. | Aug 2007 | A1 |
| 20070188305 | Drucker | Aug 2007 | A1 |
| 20070273478 | Chevalier | Nov 2007 | A1 |
| 20070286136 | Rittle et al. | Dec 2007 | A1 |
| 20070296545 | Clare | Dec 2007 | A1 |
| 20080031208 | Abhishek et al. | Feb 2008 | A1 |
| 20080062120 | Wheeler et al. | Mar 2008 | A1 |
| 20080084836 | Baird et al. | Apr 2008 | A1 |
| 20080088514 | Su et al. | Apr 2008 | A1 |
| 20080129446 | Vader | Jun 2008 | A1 |
| 20080129448 | Reichling | Jun 2008 | A1 |
| 20080191009 | Gressel et al. | Aug 2008 | A1 |
| 20080231522 | Montgomery et al. | Sep 2008 | A1 |
| 20080290990 | Schaffzin et al. | Nov 2008 | A1 |
| 20080303601 | Young | Dec 2008 | A1 |
| 20080316128 | Apostolos | Dec 2008 | A1 |
| 20090007274 | Martinez et al. | Jan 2009 | A1 |
| 20090110035 | Sutton et al. | Apr 2009 | A1 |
| 20090238308 | Weiner et al. | Sep 2009 | A1 |
| 20090262036 | Thevenard et al. | Oct 2009 | A1 |
| 20090267734 | Kwon | Oct 2009 | A1 |
| 20090267747 | Rivest et al. | Oct 2009 | A1 |
| 20090287827 | Horn et al. | Nov 2009 | A1 |
| 20090303131 | Schano | Dec 2009 | A1 |
| 20090305628 | Vavik | Dec 2009 | A1 |
| 20100035539 | Koshida et al. | Feb 2010 | A1 |
| 20100036861 | Srihari et al. | Feb 2010 | A1 |
| 20100040120 | Sharma | Feb 2010 | A1 |
| 20100052931 | Kolpasky et al. | Mar 2010 | A1 |
| 20100075655 | Howarter et al. | Mar 2010 | A1 |
| 20100077474 | Yacoub et al. | Mar 2010 | A1 |
| 20100141381 | Bliding et al. | Jun 2010 | A1 |
| 20100164683 | Sharma et al. | Jul 2010 | A1 |
| 20100167783 | Alameh et al. | Jul 2010 | A1 |
| 20100260114 | Vermani et al. | Oct 2010 | A1 |
| 20100283579 | Kraus | Nov 2010 | A1 |
| 20110001606 | Charych | Jan 2011 | A1 |
| 20110069649 | Gobriel et al. | Mar 2011 | A1 |
| 20110161697 | Qi et al. | Jun 2011 | A1 |
| 20110221565 | Ludlow et al. | Sep 2011 | A1 |
| 20110289124 | Denison | Nov 2011 | A1 |
| 20120030733 | Andrews et al. | Feb 2012 | A1 |
| 20120045989 | Suumaki et al. | Feb 2012 | A1 |
| 20120096564 | Li | Apr 2012 | A1 |
| 20120170751 | Wurm | Jul 2012 | A1 |
| 20120221189 | Konet et al. | Aug 2012 | A1 |
| 20120274444 | Micali et al. | Nov 2012 | A1 |
| 20120296685 | Nishimura et al. | Nov 2012 | A1 |
| 20120305340 | Wu | Dec 2012 | A1 |
| 20130006680 | O'Sullivan | Jan 2013 | A1 |
| 20130028293 | Makh et al. | Jan 2013 | A1 |
| 20130054976 | Brown et al. | Feb 2013 | A1 |
| 20130109313 | Kneckt et al. | May 2013 | A1 |
| 20130109314 | Kneckt et al. | May 2013 | A1 |
| 20130155925 | Priyantha et al. | Jun 2013 | A1 |
| 20130237193 | Dumas et al. | Sep 2013 | A1 |
| 20140175875 | Newman, Jr. | Jun 2014 | A1 |
| 20140281566 | Narendra et al. | Sep 2014 | A1 |
| 20150102904 | Oh et al. | Apr 2015 | A1 |
| 20150135310 | Lee | May 2015 | A1 |
| 20150263663 | Lazo et al. | Sep 2015 | A1 |
| 20180316381 | Sharma | Nov 2018 | A1 |
| 20190103966 | Zimny | Apr 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2597684 | Jul 2006 | CA |
| 19614362 | Jul 1997 | DE |
| 0808971 | Nov 1997 | EP |
| 1184236 | Mar 2002 | EP |
| 1450312 | Aug 2004 | EP |
| 1841630 | Oct 2007 | EP |
| 1003612007 | Oct 2007 | KR |
| 200626782 | Aug 2006 | TW |
| 2005059752 | Jun 2005 | WO |
| 2006078362 | Jul 2006 | WO |
| Entry |
|---|
| Notification of Transmittal of International Search Report and Written Opinion by the International Searching Authority, International Search Report, Written Opinion, in PCT application PCT/US2013/032669; dated Jul. 10, 2013. |
| European Search Report dated Feb. 9, 2010, in European Application No. 05849475.8. |
| Fischetti, M. titled Keyless Entry, Scientific American, 3 pages, (Jan. 2005). |
| Written Opinion of the International Searching Authority, International Application No. PCT/US05/044250, dated Aug. 24, 2007, 5 pages. |
| International Preliminary Report on Patentability, International Application No. PCT/US05/044250, dated Sep. 18, 2007, 2 pages. |
| International Search Report issued by the International Searching Authority for PCT application No. PCT/US05/044250, dated Nov. 14, 2007, 2 pages. |
| John Long titled SiGe Radio Frequency ICs for Low-Power Portable communication; Proceedings of the IEEE, vol. 93, No. 9, Sep. 2005. 26 pages. |
| International Search Report and Writtenn Opinion issued by the International Searching Authority dated Feb. 19, 2010 for PCT application No. PCT/US2011/067981. 10 pages. |
| International Search Report and Written Opinion issued by the International Searching Authority, dated Feb. 19, 2010 for PCT application. No. PCT/US2009/050180. |
| Liapine, A., titled Resonant Cavities as Beam Position Monitors, Part 3. Analog Signal Processing. Accelerator Physicist, Department of Physics, University of London, UK. Received Apr. 10, 2012. http://www.hep.ucl.ac.uk/˜liapine. 6 pages. |
| Barry, John R., titled Carrier Synchronization for Homodyne and Heterodyne Detection of Optical Quadriphase-Shift Keying. Department of EECS, University of California, issued Jul. 2, 1992. 36 pages. |
| Mirabbasi, Shahriar et al. titled Classical and Modem Receiver Architectures. IEEE Communications Magazines issued Nov. 2008. 8 pages. |
| Office Action dated Jul. 2, 2013 in Japanese patent application No. 2011-517638 based on PCT application No. PCT/US2009/050180. |
| English Translation of Office Action dated Jul. 2, 2013 in Japanese patent application No. 2011-517638. |
| Partial English Translation of Japanese application No. 2005-286745. |
| Polastre, Joseph et al. titled Versatile Low Power Media Access for Wireless Sensor Networks. SenSys '04, Nov. 3-5, 2004. Baltimore, Maryland. |
| A. El-Hoiydi et al., titled Low Power MAC Protocols for Infrastructure Wireless Sensor Networks. Nov. 15, 2012. |
| Ye, Wei et al., titled An Energy-Efficient MAC Protocol for Wireless Sensor Networks, (2002), 7 pages. |
| CMPE 25: Wireless and Mobile Networking SEI 3p: Medium Access Control Protocols, 2004. |
| Buettner, Michael et al., titled X-MAC: A Short Preamble MAC Protocol for Duty-Cycled Wireless Sensor Networks. SenSys '06, Nov. 1-3, 2006. |
| Chao, Chih-Min et al., titled A Quorum-Based Energy-Saving MAC Protocol Design for Wireless Sensor Networks. IEEE Transactions on Vehicular Technology, vol. 59, No. 2, Feb. 2010. |
| Tseng, Yu-Chee et al., titled Power-Saving Protocols for IEEE 802.1 1-Based Multi-Hop Ad Hoc Networks. IEEE INFOCOM 2002. |
| Li, Yuan et al., titled Energy and Latency Control in Low Duty Cycle MAC Protocols. USC/ISI Technical Report ISI-TR-595, Aug. 2004. |
| Dutta, Prabal et al., titled Practical Asynchronous Neighbor Discovery and Rendezvous for Mobile Sensing Applications. SenSys '08, Nov. 5-7, 2008, Raleigh, NC, USA (ACM). |
| Kandhalu, Arvind et al., titled U-Connect: A Low-Latency Energy-Efficient Asynchronous Neighbor Discovery Protocol. IPSN '10, Apr. 12-16, 2010, Stockholm, Sweden (ACM). |
| Lai, Shouwen, titled Heterogeneous Quorum-Based Wakeup Scheduling for Duty-Cycled Wireless Sensor Networks, Dissertation. May 5, 2009, 71 pages. |
| Meier, Andreas titled Analyzing MAC Protocols for Low Data-Rate Applications. May 16, 2006. Computer Engineering and Networks Laboratory. 16 pages. |
| International Search Report and Written Opinion issued by the International Searching Authority, dated Mar. 14, 2013 for PCT application No. PCT/US2012/067478. 7 pages. |
| International Search Report and Written Opinion issued by the International Searching Authority dated Jul. 8, 2013 for PCT application No. PCT/US2013/032620. 16 pages. |
| United States Patent and Trademark Office, International Search Report and Written Opinion for PCT/US2020/55515, dated Mar. 19, 2021, 23 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200044682 A1 | Feb 2020 | US | |
| 20200358471 A9 | Nov 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62524907 | Jun 2017 | US | |
| 61858821 | Jul 2013 | US | |
| 61611577 | Mar 2012 | US | |
| 61611575 | Mar 2012 | US | |
| 61565450 | Nov 2011 | US | |
| 61079435 | Jul 2008 | US | |
| 61428155 | Dec 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12500587 | Jul 2009 | US |
| Child | 13747362 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16019503 | Jun 2018 | US |
| Child | 16601304 | US | |
| Parent | 15473224 | Mar 2017 | US |
| Child | 16019503 | US | |
| Parent | 14444949 | Jul 2014 | US |
| Child | 15473224 | US | |
| Parent | 13843757 | Mar 2013 | US |
| Child | 14444949 | US | |
| Parent | 13841079 | Mar 2013 | US |
| Child | 13843757 | US | |
| Parent | 13747362 | Jan 2013 | US |
| Child | 13841079 | US | |
| Parent | 13691626 | Nov 2012 | US |
| Child | 14444949 | US | |
| Parent | 13340520 | Dec 2011 | US |
| Child | 13691626 | US |