Systems and methods for triggering events based on license plate recognition

Abstract

Example implementations include aspects for triggering events in a building management system. An indication of a read, by a license plate recognition (LPR) sensor, of a license plate of a vehicle at an endpoint of a parking area can be received from the LPR sensor. An event can be triggered in the building management system based on the indication of the read.

Description

Docket No.: SAC-24-8430-WO (039636.08176)SYSTEMS AND METHODS FOR TRIGGERING EVENTS BASED ON LICENSE PLATE RECOGNITIONCROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U. S Provisional Application No. 63 / 712,100, entitled “SYSTEMS AND METHODS FOR TRIGGERING EVENTS BASED ON LICENSE PLATE RECOGNITION”, filed October 25, 2024. The entirety’ of the application is incorporated by references herein.TECHNICAL FIELD

[0002] The described aspects relate to license plate recognition.BACKGROUND

[0003] License plate recognition (LPR) sensors (also referred to as cameras) exist for detecting license plates on vehicles and reading the alphanumeric characters on the license plate. LPR sensors can employ one or more cameras to capture an image of a license plate, and / or optical character recognition (OCR) to read the characters in the image. An LPR sensor can notify a software driver of the license plate read, including the characters discerned from the image. An LPR sensor can be coupled to a computing device for communicating license plate reads to the software driver executing on the computing device. The LPR sensor can couple to the computing device via a wired or wireless communications interface, such as a communications port (e.g., a serial port, universal serial bus (USB) port, a Bluetooth connection, etc.). The driver can receive license plate reads from the LPR sensor, and the computing device can include an application that processes or stores the license plate reads based on information from the driver.

[0004] Commercial or residential buildings can include vehicle parking areas, such as parking lots or parking garages, which can utilize LPR sensors to log license plate information of vehicles entering and / or exiting the parking areas. The logs of license plate information can be analyzed after the fact by security personnel for investigations involving vehicles that entered or exited the parking areas at certain times. In addition, commercial or residential buildings can include building management systems that manage automated features of the buildings or parking areas, such as access control, power consumption, security event detection and alerting, etc.Docket No.: SAC-24-8430-WO (039636.08176)SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later,

[0006] According to an aspect, a method for triggering events in a building management system is provided that includes receiving, from a license plate recognition (LPR) sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area, and triggering, in the building management system and based on the indication, an event in the building management system.

[0007] In another aspect, an apparatus for triggering events in a building management system is provided including one or more memories; and one or more processors communicatively coupled with the one or more memories and configured to perform one or more methods described herein. In another aspect, a computer-readable medium is provided herein that stores computer executable instructions for performing one or more methods described herein.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of tire various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example aspects of the present disclosure and, together with the detailed description, serve to explain their principles and implementations.

[0010] Fig. 1 is a diagram of an example of a computing device that provides a building management system for monitoring sensors and activating automated devices or alertingDocket No.: SAC-24-8430-WO (039636.08176)other systems for a building area and / or an associated parking area, in accordance aspects described herein.

[0011] Fig. 2 is a flowchart illustrating a method of triggering events based on license plate recognition (LPR) sensor read counts, in accordance aspects described herein.

[0012] Fig. 3 is a flowchart illustrating a method of triggering events based on a license plate number watchlist, in accordance aspects described herein.

[0013] Fig. 4 is a flowchart illustrating a method of separately authorizing access for vehicles and persons, in accordance aspects described herein.

[0014] Fig. 5 is a block diagram of examples components of a computer device that may implement one or more of the features of the building management system of Fig. 1.DETAILED DESCRIPTION

[0015] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in tire art that these concepts may be practiced without these specific details. In some instances, well known components may be shown in block diagram form in order to avoid obscuring such concepts.

[0016] Aspects described herein relate to using a license plate recognition (LPR) sensor, or information from an LPR sensor, to trigger events in a building management system, For example, the LPR sensor can generate a read event when a license plate is read. The LPR sensor can provide the read event to the building management system, to which the LPR sensor can be communicatively coupled. Based on the read event, the building management system can maintain associated information, such as a count of read events by die LPR sensor and / or can trigger one or more events within the building management system based on the maintained information and / or the read event, e.g., to facilitate access control, security operations, automated control of various devices, etc,

[0017] In one example, the LPR sensor can detect and read a license plate of a vehicle within a monitoring area monitored by (e.g., within a view of) a camera of the LPR sensor. Tire LPR sensor can provide an indication of a read event or occurrence, along with associated read data, to the building management system. Tire building management system can store information based on the indication and / or can trigger one or more eventsDocket No.: SAC-24-8430-WO (039636.08176)to control certain features of one or more parking areas based on the read occurrence data without necessarily exposing other information within or outside of the building management system (such as the alphanumeric value of the read license plate). In one example, indication of the read event from the LPR sensor can include the alphanumeric license plate number, which can also be provided to the building management system. In some examples, the building management system can compare a license plate number, from a read performed at the LPR sensor, to one or more watchlists, and / or the building management system can trigger one or more events if the license plate number is present on the one or more watchlists. In another example, the building management system can track activity of license plate numbers based on the reads performed at the LPR sensor to potentially add a license plate number to a watchlist (e.g,, if the license plate number frequently enters and exits tire parking area, or enters the parking area without a corresponding exit within a threshold period of time, or enters and exits the parking area within a threshold period of time, etc.). In yet another example, the building management system can create vehicle profiles for vehicles based on license plate number, w here the vehicle profile and associated access control at tlie parking area can be separate from a person profile and associated access control at the building.

[0018] As described further herein, monitoring license plate read events from the LPR sensor to trigger one or more events in a building management system can provide multiple possible advantages. For example, the building management system can achieve smart parking area management and alerting by subscribing to LPR sensor read events to maintain counts of vehicles in one or more vehicle parking areas. In addition, for example, the building management system can achieve additional or more refined access control based on vehicle entry (or attempted entry) to a parking area before an associated person is able to access the building. Also, for example, the building management system can achieve more intelligent access control by separating a person profile from a vehicle profile in an access control system.

[0019] Turning now to the figures, example aspects are depicted with reference to one or more modules or components described herein, where modules or components in dashed lines may be optional.

[0020] Fig. 1 is a diagram of an example of a computing device 100 that provides a building management system 102 for monitoring sensors and activating automated devices or alerting other systems, such as an access control system 104, security operation control system 106, etc., for a building area 108 and / or an associated parking area 110.Docket No.: SAC-24-8430-WO (039636.08176)The building area 108 can define a physical area around and / or including a building or other structure. The building area 108 can include indoor and / or outdoor portions of the building. Hie parking area 110 can include a vehicle parking area (e.g., a one or more parking garages or parking lots, etc.) at or near (e.g., attached to or detached from) the building, where vehicles of persons accessing the building can be assigned to park their vehicle. For example, the building area 108 and / or associated parking area 110 can include one or more sensors 112 that can be monitored by the building management system 102 and / or automation devices 114 that can be controlled by the building management system 102, access control system 104, security operation control system 106, etc. For example, the one or more sensors 112 can include one or more cameras, motion detectors, smoke or fire alarms or detectors, air quality detectors, temperature sensors, biometric sensors, audible sensors, such as microphones, that can identify certain sounds, safety stations, light sensors (e.g., for monitoring for power outage), heating, ventilation, and air conditioning (HVAC) operational sensors, or substantially any sensor that can monitor a condition within a building area 108 or parking area 110. For example, the one or more automation devices 114 can include automated access control devices (e.g., parking lot access barriers, automated door or window locks, turnstiles, elevators, etc,), camera control devices (e.g., point-tilt-zoom or other motorized devices to control camera position, zoom, etc.), ventilation devices (e.g., HVAC units, fans, etc.), lighting or other electrical devices, and / or the like.

[0021] In an example, parking area 110 can also include one or more LPR sensors 116 for reading license plates of vehicles entering and / or exiting the parking area 110. In an example, LPR sensor 116, or an associated software driver can provide license plate read information to the building management system 102 (or the building management system 102 can monitor the LPR sensor 116 or an associated software driver for license plate read information). For example, the LPR sensor 116 can include a camera for capturing images of license plates of vehicles. The LPR sensor 116 can include or can be coupled with a computing device, which is not shown and can include one or more processors or memories, for executing a software driver that can communicate with the camera. The driver can perform optical character recognition (OCR) of the image to obtain a license plate alphanumeric value, and / or notify one or more applications of the license plate read and / or the alphanumeric value. In this regard, for example, building management sy stem 102 can communicate with the LPR sensor 116 and / or the associated software driver to receive license plate read information.Docket No.: SAC-24-8430-WO (039636.08176)

[0022] The LPR sensor 116 can be or can include an edge camera and / or a recorder device, which can be communicatively coupled to the building management system 102. In any case, for example, the LPR sensor 116 (e.g., via the computing device executing the software driver or otherwise) can send the actual notification that an LPR event has occurred (e.g., the detection of a license plate) to the building management system 102 and / or can send the contents of the license plate (the license plate number) to the building management system 102, For example, the LPR sensor 116 can publish a meta stream that includes the notification and / or the contents to the building management system 102 or the building management system 102 can subscribe to the meta stream published by the LPR sensor 116 to receive the notification of read events and / or contents.

[0023] For example, building management system 102 can include one or more of a LPR monitoring component 130 for monitoring license plate read information provided or published by the LPR sensor 116, which may include a count or occurrence of a read event, an alphanumeric value of the license plate being read, etc. For example, building management system 102 can also include an event triggering component 132 for triggering one or more events (e.g., alerts or events on one or more devices, such as one or more automation devices 114) based on the license plate read information. For example, building management system 102 can also include a watchlist managing component 134 for managing one or more watchlists 136 of license plate numbers that can cause certain events to be triggered by the building management system 102 when the license plate number is received from LPR sensor 116.

[0024] Computing device 100 can include a processor 120 (and / or multiple processors) and / or a memory 122 (or multiple memories) configured to execute or store instructions or other parameters related to performing one or more processes, executing the building management system 102 and / or its associated components, etc. For example, one or more processors 120 and one or more memories 122 may be separate components communicatively coupled by a bus (e.g., on a motherboard or other portion of a computing device, on an integrated circuit, such as a system on a chip (SoC), etc.), components integrated within one another (e.g., one or more processors 120 can include the one or more memories 122 as an on-board component), and / or the like. One or more memories 122 may store instructions, parameters, data structures, etc. for use / execution by one or more processors 120 to perform functions described herein. In addition, for example, computing device 100 can include multiple computing devices distributedDocket No.: SAC-24-8430-WO (039636.08176)across a network (e.g., in a network or cloud-based deployment), where each of the computing devices can include one or more functions described herein.

[0025] In one example, LPR monitoring component 130 can facilitate monitoring of license plate read events or associated information from one or more LPR sensors 116 for triggering other events in the building management system 102. For example, LPR monitoring component 130 can define, or can allow for defining (e.g., via a provided user interface), one or more events attached to the LPR sensor 116 information. In one example, LPR monitoring component 130 can monitor a count of license plates read by a first LPR sensor 116 for vehicles entering the parking area 110 and a count of license plates read by a second LPR sensor 116 for vehicles exiting the parking area 110. In this example, LPR monitoring component 130 can maintain (e.g., in one or more memories 122) a total count of vehicles in the parking area 110, which can include incrementing the total count by the count of license plates read by the first LPR sensor 116 (e.g., when a notification of a read event is received from the first LPR sensor 116) and decrementing the total count by the count of license plates read by the second LPR sensor 116 (e.g., when a notification of a read event is received from the second LPR sensor 116). In an example, event triggering component 132 can define, or allow for defining (e.g., via a user interface), one or more events for certain values of the total count. For example, the total count can be defined specifically for the parking area 110 and can change based on a number of reserved parking spots, a temporary change in the number of available spots due to construction or other maintenance, etc.

[0026] For example, the one or more events can correspond to not opening (e.g,, keeping closed or activated) a parking area barrier for a vehicle where the total count achieves a threshold, opening the parking area barrier for a vehicle where the total count is decremented and no longer achieves the threshold, opening a parking area barrier for a second parking area for a vehicle w here the total count for the parking area 110 achieves a threshold, etc. In an example, event triggering component 132 can trigger the events in the building management system 102, which may cause building management system 102 to communicate with access control system 104 to grant or deny access to a vehicle via the parking area barrier (which can be a controllable automation device 114 in one or more parking areas). In other examples, other automation devices 114 can be operated based on the total count of vehicles in the parking area, as determined from LPR sensors 116. For example, when event triggering component 132 detects that the total vehicle count maintained by LPR monitoring component 130 achieves a threshold, eventDocket No.: SAC-24-8430-WO (039636.08176)triggering component 132 can trigger an event to control a ventilation system in the parking area 110. This can conserve power by operating the ventilation system only when the total count achieves the threshold (and ventilation of exhaust fumes may be useful to prevent or mitigate human contact with vehicle exhaust).

[0027] In another example, the one or more events can correspond to a security alert communicated to security operation control system 106 to alert security or other building personnel of the parking area 110 status. For example, this can allow the security personnel to redirect vehicles to other lots when the parking area 110 is at a certain capacity or status (e.g., full, near full, empty, etc., or at least at a desired capacity given a number of reserved parking spaces, etc.).

[0028] For example, leveraging LPR, each unique plate can generate a count of vehicles for both inbound and outbound to a parking lot / structure. Tire counts can be maintained both in persisted and volatile memory enabling fast decision making while having the ability to persist counts through any loss of application or service with an ability to recover to an accurate count of cars. A sendee can monitor the coun ts looking for one or more user definable trigger points for the definition of when a lot is empty, near full, full, reserved empty, reserved near full, reserved full. Upon one of these user defined count thresholds being reached, an event in the security system can be activated enabling the ability to notify and / or change the behavior of security profile of a building and / or parking lot / structure.

[0029] In another example, LPR monitoring component 130 can monitor the LPR sensor(s) 116 for license plate read events for access control operations for the building area 108 and / or parking area 110. For example, LPR monitoring component 130 can obtain one or more watchlists 136 from one or more memories 122, which can include license plate numbers for which to trigger certain events when encountered. In this regard, for example, LPR monitoring component 130 can monitor one or more watchlists associated with one or more events, and event triggering component 132 can trigger an associated event when a license plate number from a watchlist is encountered. For example, the watchlist(s) 136 stored in one or more memories 122 can include a watchlists generated or managed by watchlist managing component 134, watchlist(s) received from other sources, such as a criminal database, etc.

[0030] In a specific example, when LPR monitoring component 130 detects LPR sensor 116 reading a license plate from a watchlist of vehicles for which to deny entry'-, event triggering component 132 can trigger various events via access control system 104, suchDocket No.: SAC-24-8430-WO (039636.08176)as not opening the barrier to the parking area 110 (via automation device(s) 114), locking additional doors of the building area 108 (via automation device(s) 114), and / or events via security operation control system 106, such as notifying security personnel of presence of the vehicle. In another specific example, watchlist managing component 134 can manage one or more watchlists 136 based on license plate read events received by LPR monitoring component 130. For example, watchlist managing component 134 can detect frequent reads of the same license plate at LPR monitoring component 130 (e.g., a number of reads within a threshold period of time) indicating frequent parking area 110 access by the vehicle, which may cause the license plate to be added to a watchlist for causing an event upon subsequent reading of the license plate. In another example, watchlist managing component 134 can detect read of a license plate at LPR monitoring component 130 by a first LPR sensor 116 at an entrance to the parking area 110 without a corresponding read at a second LPR sensor 116 at an exit of the parking area 110 within a threshold period of time, which may indicate the vehicle has not left the parking area 110 for extended periods of time. This may cause the license plate to be added to a watchlist for causing an event upon subsequent reading of the license plate. In another example, watchlist managing component 134 can detect read of a license plate at LPR monitoring component 130 by a first LPR sensor 116 at an entrance to the parking area 110 and a corresponding read at a second LPR sensor 116 at an exit of the parking area 110 within a threshold period of time, which may indicate normal activity, and the vehicle may be removed from a watchlist.

[0031] In this regard, for example, real-time (or near real-time) detection can be provided with access control management to proactively manage potential violations of vehicles that conduct undesired behavior or are part of a potential watch list. For example, event triggering component 132 can utilize a vehicle watch list rules engine to enable real time alerting to unwanted vehicle behaviors such as multiple reentries, immediate entry / exit, entry without exit in same day, etc. Watchlist managing component 134 can perform such operations by tracking the specific date / time by license plate number for any entry and exit and then using processing to compare against a user definable rule with the ability to trigger an event with user definable response actions in the access control system.

[0032] In another example, LPR monitoring component 130 can monitor the LPR sensor(s) 116 for license plate read events for access control operations for the vehicle in the parking area 110 separately from access control operations for persons in the building area 108. For example, building management system 102 can separately store profilesDocket No.: SAC-24-8430-WO (039636.08176)for vehicle and persons to allow separate access control or other events to be generated for vehicles and persons. For example, access control applications can have support for LPR and parking, but the vehicles can sometimes be treated as an attribute of the person that result in the assumption that a vehicle when present also means the person is present. This is not always true and results in inaccuracy of access con trol managemen t.

[0033] Accordingly, for example, separate objects can be created for vehicles in access control enabling the independent issuance of access levels or clearances to a vehicle. Vehicles can be associated or linked to a person, but the access control permission, level, clearances can be separate for the person and the vehicle. This can enable a car to gain access to a parking area 110 without automatically checking the person in for access to the building area 108, as the vehicle could be borrowed or more than one person be in a vehicle, etc.

[0034] Referring to Fig. 2, in operation, computing device 100, or the associated building management system 102, may perform a method 200 for triggering events based on LPR read counts, such as via execution of certain instructions by one or more processors 120 and / or memory / memories 122, which may execute or implement components of the building management system 102, as described above.

[0035] At block 202, the method 200 includes receiving, by a building management system and from a LPR sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can receive, from the LPR sensor (e.g., LPR sensor 116 of the parking area 110), the indication of the read, by the LPR sensor, of the license plate of the vehicle at the endpoint of the parking area (e.g,, parking area 110). For example, LPR monitoring component 130 may receive the indication as a notification of a read event, which may or may not include additional information, such as the alphanumeric license plate value (e.g., as OCRed or otherwise determined from the image of the license plate). In one example, LPR monitoring component 130 can store a count value for vehicles in the parking area 110 in memoiy 122 where the count value may be initialized to a value (e.g., value), and LPR monitoring component 130 can increment the count value 'hen a read event is received by a first LPR sensor (e.g., a sensor at an entrance of the parking area 110) and / or can decrement the count value when a read event is received by a second LPR sensor (e.g., a sensor at an exit of the parking area 110).Docket No.: SAC-24-8430-WO (039636.08176)

[0036] At block 204, the method 200 can optionally include incrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an entrance to the parking area. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can increment the count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an entrance (or other ingress) to the parking area. At block 206, the method 200 can optionally include decrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an exit to the parking area. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can decrement the count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an exit (or other egress) from the parking area. In this regard, LPR monitoring component 130 can maintain a count of vehicles in memory based on receiving indications of reads from LPR sensors.

[0037] At block 208, the method 200 includes triggering, by the building management system and based on the indication, an event in the building management system. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger, based on the indication, an event (e.g., in the building management system or one or more components or systems associated or communicatively coupled therewith). For example, event triggering component 132 can trigger an event based on the indication when the indication causes the total count of vehicles to achieve a threshold (when incremented) or no longer achieve a threshold (when decremented). For example, event triggering component 132 can allow for defining various thresholds for a parking area to indicate near full, full, reserved, full, near empty, empty, etc. conditions. Based on the total count achieving a certain condition, event triggering component 132 can trigger an associated event.

[0038] For example, triggering the event at block 208 can include, at block 210, triggering an access control event. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger the access control event, which can include triggering the event via an access control system 104. This can include activating one or more automation devices 114 in the parking area 110 or a correspondingDocket No.: SAC-24-8430-WO (039636.08176)building area 108, as described above. For example, event triggering component 132 can trigger an access control event to close or lock or maintain a barrier of the parking area 110 when the total count indicates a full condition and / or an access control event to unlock or open a barrier of a different parking area when the total count indicates a full condition for parking area 110.

[0039] In another example, triggering the event at block 208 can include, at block 212, triggering a security and operations control event. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger the security and operations control event, which can include a notification related to the condition or status or the parking area 110, For example, a notification related to the parking area 110 being full can allow security personnel to supervise the parking area, setup signs indicating the parking area is full and / or directions to a different parking area, etc.

[0040] Referring to Fig. 3, in operation, computing device 100, or the associated building management system 102, may perform a method 300 for triggering events based on a license plate number watchlist, such as via execution of certain instructions by one or more processors 120 and / or memory / memories 122, which may execute or implement components of the building management system 102, as described above.

[0041] At block 302, the method 300 includes receiving, by a building management system and from a LPR sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can receive, from the LPR sensor (e.g,, LPR sensor 116 of the parking area 110), the indication of the read, by the LPR sensor, of the license plate of the vehicle at the endpoint of the parking area (e.g., parking area 110). For example, LPR monitoring component 130 may receive the indication a read event occurrence, which may include information associated with the license plate read, such as the alphanumeric license plate value OCRed from the image of the license plate.

[0042] At block 304, the method 300 can optionally include detecting a license plate number, identified in the read, in a watchlist. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can detect the licenseDocket No.: SAC-24-8430-WO (039636.08176)plate number, identified by the read, in the watchlist (e.g., one or more watchlists 136). For example, LPR monitoring component 130 can detect presence of the license plate number in the one or more watchlists 136, which may be associated with triggering an event by event triggering component 132. For example, the one or more watchlists 136 can correspond to license plates for which entry' to the parking area 110 is to be denied, or other access is to be denied, or security notification is to occur. As described, for example, the one or more watchlists 136 can include a criminal database, and detecting the license plate in the watchlist can result in event triggering component 132 triggering locking of a barrier preventing entering the parking area 110 (e.g., by controlling an associated automation device 114), locking one or more doors of the building area 108 (e.g., by controlling an associated automation device 114), notifying security personnel to report to the entrance of the parking area 110, etc.

[0043] Accordingly, for example, at block 306, the method 300 includes triggering, by the building management system and based on the indication, an event in the building management system. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger, based on the indication (e.g., based on receiving the indication and detecting the associated license plate number in a watchlist), an event. For example, event triggering component 132 can trigger the event based on detecting the license plate number in the watchlist 136 and determining the event or multiple events associated with the watchlist.

[0044] For example, as described above for triggering the event at block 208, triggering the event at block 306 can include, at block 308, triggering an access control event, or at block 310, triggering a security and operations control event. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger the access control event and / or security and operations control event.

[0045] At block 312, the method 300 can optionally include adding the license plate number to, or removing the license plate number from, the watchlist based on the indication. For example, watchlist managing component 134, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can add the license plate number to, or remove the license plate number from, the watchlist (e.g., watchlist 136) based on the indication. In an example, watchlist managing component 134 can add the license plate number to theDocket No.: SAC-24-8430-WO (039636.08176)watchlist 136 based on detecting (or LPR monitoring component 130 detecting) certain features of the license plate number in multiple indications received from one or more LPR sensors 116. For example, watchlist managing component 134 can add the license plate number to the watchlist 136 based on detecting the license plate number being read by multiple LPR sensors 116 within a threshold period of time, based on detecting the license plate number being read by one or more LPR sensors 116 a threshold number of times within a time period, based on detecting the license plate number being read by a first LPR sensor 116 at an entrance to the parking area 110 without a corresponding read at an exit of the parking area 110 by a threshold time, etc.

[0046] Referring to Fig. 4, in operation, computing device 100, or the associated building management system 102, may perform a method 400 for separately authorizing access for vehicles and persons, such as via execution of certain instructions by one or more processors 120 and / or memory / memories 122, which may execute or implement components of the building management system 102, as described above.

[0047] At block 402, the method 400 includes receiving, by a building management sy stem and from a LPR sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area. For example, LPR monitoring component 130, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can receive, from the LPR sensor (e.g., LPR sensor 116 of the parking area 110), the indication of the read, by the LPR sensor, of the license plate of the vehicle at the endpoint of the parking area (e.g., parking area 110). For example, LPR monitoring component 130 may receive the indication a read event occurrence, which may include information associated with the license plate read, such as the alphanumeric license plate value OCRed from the image of the license plate.

[0048] At block 404, the method 400 includes triggering, by the building management system and based on the indication, an event in the building management system. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can trigger, based on the indication, an event. For example, event triggering component 132 can trigger the event based on the license plate number, where events can be associated with certain license plate numbers, such as allowing or denying access to the parking area 110. This can be based on detecting the license plate number in one or more lists (e.g., a list of authorized vehicles), in this regard, for example, event triggeringDocket No.: SAC-24-8430-WO (039636.08176)component 132 can trigger a barrier of the parking area 110 to open for authorized vehicles (e.g., based on communicating with access control system 104 to operate the automation device 114 corresponding to the barrier).

[0049] In this regard, for example, the event at block 404 can include, at block 406, authorizing access for the vehicle to the parking area based on a license plate number identified in the read. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., can authorize access for the vehicle to the parking area based on the license plate number identified in the read. For example, event triggering component 132 can verify the license plate number in a list of allowed license plate numbers for accessing the parking area 110, or can otherwise forward the license plate number to the access control system 104 for determining whether to allow access to the parking area 110 for the license plate number. In any case, as described, building management system 102 and / or access control system 104 can separately store profiles for persons and vehicles for accessing parking areas and building areas.

[0050] In this regard, for example, at block 408, the method 400 can optionally include separately authorizing access for a person to a building associated with the parking area based on credentials of the person read at a sensor at an endpoint of the building. For example, event triggering component 132, e.g., in conjunction with computing device 100, one or more processors 120, memory / memories 122, building management system 102, etc., or a component of the access control system 104, can separately authorize access for the person to a building (e.g., building area 108) based on credentials of the person read at a sensor at the endpoint of the building. For example, event triggering component 132, or a component of the access control system 104, can authorize access for the person at a card reader that reads an access card or other access control device, where the credentials and authorization profile for the person can be separate from access for the vehicle. Thus, as described above, the building management system 102 and / or access control system 104 can perform access control to allow the vehicle to enter the parking area 110 separately from performing access control for the person driving the vehicle.

[0051] Referring to Fig. 5, a computing device 500 may implement all or a portion of the functionality described in Fig. 1-4, in accordance with aspects described herein. For example, the computing device 500 may be or may include at least a portion of the building management system 102, access control system 104, security operation control system 106, or any other module or component described herein with reference to Figs.Docket No.: SAC-24-8430-WO (039636.08176)1-4. The computing device 500 may include one or more processors 502 which may be configured to execute or implement software, hardware, and / or firmware modules that perform some or all of the functionality described herein with reference to Figs. 1-4. For example, the processor(s) 502 may be configured to execute or implement software, hardware, and / or firmware modules that perform some or all of the functionality described herein with reference to the building management system 102, access control system 104, security operation control system 106, or any other module or component described herein with reference to Figs. 1-2.

[0052] The processor(s) 502 may be a micro-controller, an application-specific integrated circuit (ASIC), or a field-programmable gate array (FPGA), and / or may include a single or multiple set of processors or multi-core processors. Moreover, the processor(s) 502 may be implemented as an integrated processing system and / or a distributed processing system, The computing device 500 may further include memory / memories 504, such as for storing local versions of applications being executed by the processor(s) 502, related instructions, parameters, etc. The memory / memories 504 may include a type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. Additionally, the processor(s) 502 and the memory / memories 504 may include and execute an operating system executing on the processor(s) 502, one or more applications, display drivers, etc., and / or other modules or components of the computing device 500.

[0053] Further, the computing device 500 may include a communications module 506 that provides for establishing and maintaining communications with one or more other devices, parties, entities, etc. utilizing hardware, software, and sendees. lire communications module 506 may carry’ communications between modules on the computing device 500, as well as between the computing device 500 and external devices, such as devices located across a communications network and / or devices serially or locally connected to the computing device 500. In an aspect, for example, the communications module 506 may include one or more buses, and may further include transmit chain modules and receive chain modules associated with a wireless or wired transmitter and receiver, respectively, operable for interfacing with external devices.

[0054] Additionally, the computing device 500 may include a data store 508, which can be any suitable combination of hardware and / or software, that provides for mass storage of information, databases, and programs. For example, the data store 508 may be or mayDocket No.: SAC-24-8430-WO (039636.08176)include a data repository for applications and / or related parameters not currently being executed by processor(s) 502. In addition, the data store 508 may be a data repository for an operating system, application, display driver, etc., executing on the processor 502, and / or one or more other modules of the computing device 500.

[0055] The computing device 500 may also include a user interface module 510 operable to receive inputs from a user of the computing device 500 and further operable to generate outputs for presentation to the user (e.g,, via a display interface to a display device). The user interface module 510 may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition module, or any other mechanism capable of receiving an input from a user, or any combination thereof. Further, the user interface module 510 may include one or more output devices, including but not limited to a display interface, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.

[0056] Some further example aspects are provided below.

[0057] Clause 1 is a method for triggering events in a building management system including receiving, from a license plate recognition (LPR) sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area, and triggering, in the building management system and based on the indication, an event in the building management system.

[0058] In Clause 2, the method of Clause 1 includes incrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an entrance to the parking area, and wherein the event corresponds to the count of vehicles in the parking area being greater than or equal to a threshold.

[0059] In Clause 3, the method of Clause 2 includes wherein the event corresponds to controlling, based on the count of vehicles in the parking area being greater than or equal to a threshold, access to the endpoint as an entrance to the parking area.

[0060] In Clause 4, the method of any of Clauses 1 to 3 includes decrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an exit from the parking area, and wherein the event corresponds to the count of vehicles in the parking area being less than a threshold.

[0061] In Clause 5, the method of Clause 4 includes wherein the event corresponds to controlling, based on the count of vehicles in the parking area being less than the threshold, access to an entrance to the parking area.Docket No.: SAC-24-8430-WO (039636.08176)

[0062] In Clause 6, the method of any of Clauses 1 to 5 includes wherein the event corresponds to a notification to a security control operations system associated with tlie parking area based on a count of vehicles computed based on the indication of the read.

[0063] In Clause 7, the method of any of Clauses 1 to 6 includes wherein triggering the event is based on detecting a license plate number, identified by the read, in a watchlist.

[0064] In Clause 8, the method of Clause 7 includes wherein the event corresponds to an access control function controlling an automation device based on detecting the license plate number in the watchlist.

[0065] In Clause 9, the method of any of Clauses 7 or 8 includes further comprising adding the license plate number to the watchlist based on at least one of detecting multiple reads of the license plate number by the LPR sensor within a threshold period of time, or detecting the read of the license plate number by the LPR sensor without a corresponding read of the license plate number by a different LPR sensor in the parking area within a threshold period of time,

[0066] In Clause 10, the method of any of Clauses 7 to 9 includes wherein the event corresponds to a notification to a security control operations system associated with tlie parking area.

[0067] In Clause 11, the method of any of Clauses 1 to 10 includes wherein the event corresponds to an access control function authorizing, based on a license plate number identified by the read, access to the vehicle at the endpoint, and wherein the building management system also includes a person access control function to control access to another area of the building based on access credentials of a person.

[0068] Clause 12 is an apparatus including one or more processors, one or more memories coupled with tire one or more processors, and instructions stored in the one or more memories and operable, when executed by the one or more processors, to cause the apparatus to perform any of the methods of Clauses 1 to 11.

[0069] Clause 13 is an apparatus including means for performing any of the methods of Clauses 1 to 11.

[0070] Clause 14 is one or more computer-readable media including code executable by one or more processors, the code including code for performing any of the methods of Clauses 1 to 11.

[0071] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over asDocket No.: SAC-24-8430-WO (039636.08176)one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0072] Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry’ or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0073] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Tire 'ord “exemplar}7” is used herein to mean “serving as an example, instance, or illustration.” Any aspectDocket No.: SAC-24-8430-WO (039636.08176)described herein as “exemplar is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, (. or any combination thereof ’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0074] As used herein, a processor, at least one processor, and / or one or more processors, individually or in combination, configured to perform or operable for performing a plurality of actions is meant to include at least two different processors able to perform different, overlapping or non-overlapping subsets of the plurality actions, or a single processor able to perform all of the plurality of actions. In one non-limiting example of multiple processors being able to perform different ones of the plurality of actions in combination, a description of a processor, at least one processor, and / or one or more processors configured or operable to perform actions X, Y, and Z may include at least a first processor configured or operable to perform a first subset of X, Y, and Z (e.g., to perform X) and at least a second processor configured or operable to perform a second subset of X, Y, and Z (e.g,, to perform Y and Z). Alternatively, a first processor, a second processor, and a third processor may be respectively configured or operable to perform a respective one of actions X, Y, and Z. it should be understood that any combination of one or more processors each may be configured or operable to perform any one or any combination of a plurality of actions.Docket No.: SAC-24-8430-WO (039636.08176)

[0075] As used herein, a memory, at least one memory, and / or one or more memories, individually or in combination, configured to store or having stored thereon instructions executable by one or more processors for performing a plurality of actions is meant to include at least two different memories able to store different, overlapping or nonoverlapping subsets of the instructions for performing different, overlapping or nonoverlapping subsets of the plurality actions, or a single memory able to store the instructions for performing all of the plurality of actions. In one non-limiting example of one or more memories, individually or in combination, being able to store different subsets of the instructions for performing different ones of the plurality of actions, a description of a memory, at least one memory, and / or one or more memories configured or operable to store or having stored thereon instructions for performing actions X, Y, and Z may include at least a first memory configured or operable to store or having stored thereon a first subset of instructions for performing a first subset of X, Y, and Z (e.g., instructions to perform X) and at least a second memory’ configured or operable to store or having stored thereon a second subset of instructions for performing a second subset of X, Y, and Z (e.g., instructions to perform Y and Z). Alternatively, a first memory, and second memory, and a third memory may be respectively configured to store or have stored thereon a respective one of a first subset of instructions for performing X, a second subset of instruction for performing Y, and a third subset of instructions for performing Z. it should be understood that any combination of one or more memories each may be configured or operable to store or have stored thereon any one or any combination of instructions executable by one or more processors to perform any one or any combination of a plurality of actions. Moreover, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute the instructions to perform the plurality of actions. For instance, in the above non-limiting example of the different subset of instructions for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, and at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first processor and the second processor may, in combination, execute the respective subset of instructions to accomplish performing actions X, Y, and Z. Alternatively, three processors may access one of three different memories each storing one of instructions for performing X, Y, or Z, and the three processor may in combination execute the respective subset of instruction to accomplish performing actions X, Y, and Z. Alternatively, a single processor mayDocket No.: SAC-24-8430-WO (039636.08176)execute the instructions stored on a single memory, or distributed across multiple memories, to accomplish performing actions X, Y, and Z.

Claims

Docket No.: SAC-24-8430-WO (039636.08176)CLAIMSWhat is claimed is:

1. A computer-implemented method for triggering events in a building management system, comprising:receiving, from a license plate recognition (LPR) sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area; and triggering, in the building management system and based on the indication, an event in the building management system.

2. The computer-implemented method of claim 1, further comprising incrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint as an entrance to the parking area, and wherein the event corresponds to the count of vehicles in the parking area being greater than or equal to a threshold.

3. The computer-implemented method of claim 2, wherein the event corresponds to controlling, based on the count of vehicles in the parking area being greater than or equal to a threshold, access to the endpoint, wherein the endpoint is an entrance to the parking area.

4. The computer-implemented method of claim 1, further comprising decrementing a count of vehicles in the parking area where the indication is from the LPR sensor at the endpoint, wherein the endpoint is an exit from the parking area, and wherein the event corresponds to the count of vehicles in the parking area being less than a threshold.

5. The computer-implemented method of claim 4, wherein the event corresponds to controlling, based on the count of vehicles in the parking area being less than the threshold, access to an entrance to the parking area.

6. The computer-implemented method of claim 1, wherein the event corresponds to a notification to a security control operations system associated with the parking area based on a count of vehicles computed based on the indication of the read.Docket No.: SAC-24-8430-WO (039636.08176)7. The computer-implemented method of claim 1, wherein triggering the event is based on detecting a license plate number, identified by the read, in a watchlist.

8. The computer-implemented method of claim 7, wherein the event corresponds to an access control function controlling an automation device based on detecting the license plate number in the watchlist.

9. The computer-implemented method of claim 7, further comprising adding the license plate number to the watchlist based on at least one of detecting multiple reads of the license plate number by the LPR sensor within a threshold period of time, or detecting the read of the license plate number by the LPR sensor without a corresponding read of tire license plate number by a different LPR sensor in the parking area within a threshold period of time.

10. The computer-implemented method of claim 7, wherein the event corresponds to a notification to a security control operations system associated with tlie parking area.

11. The computer-implemented method of claim 1, wherein the event corresponds to an access control function authorizing, based on a license plate number identified by the read, access to the vehicle at the endpoint, and wherein the building management system also includes a person access control function to control access to another area of a building associated with the parking area based on access credentials of a person.

12. An apparatus for triggering events in a building management system, comprising:one or more memories; andone or more processors communicatively coupled with the one or more memories and configured to:receive, from a license plate recognition (LPR) sensor, an indication of a read, by the LPR sensor, of a license plate of a vehicle at an endpoint of a parking area; andDocket No.: SAC-24-8430-WO (039636.08176)trigger, in the building management system and based on the indication, an event in the building management system.

13. The apparatus of claim 12, wherein the one or more processors are configured to increment a count of vehicles in tire parking area where the indication is from the LPR sensor at the endpoint as an entrance to the parking area, and wherein the event corresponds to the count of vehicles in the parking area being greater than or equal to a threshold.

14. The apparatus of claim 12, wherein the event corresponds to a notification to a security control operations system associated with the parking area based on a count of vehicles computed based on the indication of the read.

15. A computer-readable medium storing instructions for triggering events in a building management system, wherein the instructions are executable by a processor to perform any of the methods of claims 1 to 11.

Images