Systems and methods for parking enforcement

Abstract

A computer-implemented method can include receiving an object identifier through an object identification device. The method can also include, based upon the received object identifiers, identifying (i) an associated parking permission of an object, (ii) an object location as viewed by the object identification device, (iii) a parking validity status of an object. In addition, the method can include prompting a user of parking violations through a user interface. Still further, the method can include upon confirmation from the parking monitor, assigning a parking citation to an object or an operator of the object.

Description

SYSTEMS AND METHODS FOR PARKING ENFORCEMENTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 667,078, filed on July 2, 2024, entitled SYSTEMS AND METHODS FOR PARKING ENFORCEMENT, which is incorporated herein in its entirety by reference.BACKGROUND1. Field

[0002] The present disclosure relates to devices, computer-implemented methods, and systems for enforcing parking lot use and access.2. Background

[0003] Parking lot monitoring operations generally monitor a number of vehicles parking on premises, and may restrict which spots are available to which persons or which vehicles. For example, a university' may have employees that are allowed to use some spots or "stalls," while the entity may allow' students to park in other parking spots. In some cases, the entity may govern the use of stalls by specific authorizations that the entity provides to the employee or student, which the student or employee may prove by displaying a physical parking pass on their respective vehicle, or by associating their license plate with some authority to park in the designated area. Whereas other universities may employ a digital pass system associated with a vehicle's license plate. In general, conventional monitoring systems employ parking officials to monitor vehicles parked in lots and determine whether the vehicle is associated with appropriate authorization.

[0004] The monitoring and employment of parking enforcers assigned to patrol lots can be expensive and inefficient. The sheer number of parking spaces and associated vehicles can create monitoring problems for parking enforcement officials, and often results in large expenditures. For example, a parking enforcer may enter a parking area looking for violations and find few if any violations while another lot concurrently has one or more violations. In some cases, the authorization is vehicle specific, such as in the case of size-limited stalls, or in the case of stalls designated for electric vehicle charging. In other cases, authorizations can be difficult to manage because the authorizations may be more appropriately assigned to an individual instead of a vehicle, such as in the case of a handicap parking pass. While these enforcement issues can be challenging, such enforcement issues may be particularly difficult for entities monitoring very' large parking spaces with different lots in the order of hundreds tothousands of stalls, which may have a larger faculty' and student population and a greater number of potential lots to be monitored.

[0005] Accordingly, there are a number of difficulties in the art of parking monitoring and enforcement that can be addressed. SUMMARY

[0006] The present disclosure provides systems, methods, and computer program products that enable efficient parking lot enforcement and management. For example, the present disclosure includes a computer-implemented method that, in tandem with an identification device, can track object permissions and location. The end user (i.e., a parking monitor or parking attendant) can then receive and view object parking information, using the provided details to simplify and reduce costs associated with the parking monitoring and enforcement process.

[0007] For example, a computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking can include identifying, by a computer system in connection with one or more stationary' cameras, an object within a parking area and receiving, by a first camera of the one or more cameras, an object identification attribute corresponding to the object within the parking area. The method may further include identifying by the computer system, based upon the received object identification attribute from the first camera, a permission associated with at least one of the object, or an operator of the object as well as determining, by the computer system, based upon the received identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object. Upon request, the method may further include displaying through a digital display device a parking authorization metric associated with the object.

[0008] In another implementation, a computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking may include receiving, by a first identification device, a first object identification attribute corresponding to an object. The first object identification attribute can include image data corresponding to the object from at least a first view. The method may further include receiving, by a second identification device, a second object identification attribute corresponding to the object. The second object identification attribute can include image data corresponding to the object from at least a second view. The method may also include determining, by a computer system, based upon the received first object identification attribute and the second object identification attribute, a characterization of the object sufficient to identify the object and whether any permissions are associated with the object and / or an operator of the object. Further, the method may include determining, by the computer system, based upon the received first object identificationattribute and second identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object. Upon request, the method may include displaying through a digital display device a parking authorization metric associated with the object. The method may still include sending print instructions for a citation associated with the object upon request through a user interface.

[0009] In yet another implementation, a computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking may include receiving, by one or more cameras, a first image data corresponding to a plurality of parking spots within a parking area and receiving, by the one or more cameras, a second image data that comprises a list of objects within the parking area. The method may include determining, by a computing system, based on the received first image data and second image data, an occupancy status for each of the plurality of parking spots. The method may also include generating, by the computing system, a real-time digital map of the parking area, the digital map comprising an indicator of which of the plurality of parking spots are occupied, and which of the plurality of parking spots are available. The method may further include updating, by the computing system, the realtime digital map in response to changes in occupancy detected by the one or more cameras as well as displaying, through a digital display, the real-time digital map to indicate a current parking capacity7and available parking spots within the parking area, if any.

[0010] Additional features and advantages will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice. The features and advantages may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features will become more fully apparent from the following description and appended claims, or may be learned by the practice of the examples as set forth hereinafter. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To describe the manner in which the above-recited and other advantages and features can be obtained, a more particular description of the subject matter briefly described above will be rendered by reference to specific examples which are illustrated in the appended drawings. Understanding that these drawings depict only typical examples and are not therefore to be considered to be limiting in scope, examples will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

[0012] Figure 1 depicts a schematic of a system for use in accordance with an implementation of the present disclosure.

[0013] Figure 2 depicts a user interface login screen for use in accordance with an implementation of the present disclosure.

[0014] Figure 3 depicts a dashboard showing statistical parking trends and analytics for use in accordance with an implementation of the present disclosure.

[0015] Figure 4 is a schematic of a parking lot displaying parking status, in accordance with an implementation of the present disclosure.

[0016] Figure 5 A is a schematic displaying to the parking monitor of current parking violations specific to the entity, in accordance with an implementation of the present disclosure.

[0017] Figure 5B is a schematic displaying a database of vehicles that have parked in stalls monitored by the entity, in accordance with an implementation of the present disclosure.

[0018] Figure 5C is a schematic displaying the history of a specific object, in accordance with an implementation of the present disclosure.

[0019] Figure 6 is a schematic displaying information pertaining to the entity’ and initial setup in accordance with an implementation of the present disclosure.

[0020] Figure 7A is a schematic of a vehicle violation and accompanying fields for use in accordance with an implementation of the present disclosure.

[0021] Figure 7B illustrates a pop-up user interface that allows the system to export a citation for use in accordance with an implementation of the present disclosure.

[0022] Figure 7C illustrates a manual citation system in accordance with an implementation of the present disclosure.

[0023] Figure 8 is a schematic displaying permissions granted to specific individuals for use in accordance with an implementation of the present disclosure.

[0024] Figure 9 depicts a dashboard displaying to the parking monitor the permissions associated with specific parking lots and / or passes, for use in accordance with an implementation of the present disclosure.

[0025] Figure 10A depicts a schematic displaying parking privileges associated with different parking passes, for use in accordance with the present disclosure.

[0026] Figure 10B depicts a schematic displaying parking durations associated with different parking passes, for use in accordance with the present disclosure.

[0027] Figure 11 depicts a user interface help screen for use in accordance with an implementation of the present disclosure.

[0028] Figure 12 depicts a mobile user interface settings screen for use in accordance with the present disclosure.

[0029] Figure 13 A depicts a mobile user interface displaying parking violations for use in accordance wi th the present disclosure.

[0030] Figure 13B depicts a mobile user interface displaying a listing of lots for use in accordance with the present disclosure.

[0031] Figure 14A depicts a mobile user interface displaying parking citation information for use in accordance with the present disclosure.

[0032] Figure 14B depicts a mobile pop-up user interface displaying a user with flagged image data for use in accordance with the present disclosure.

[0033] Figure 15 depicts a mobile user interface displaying an interactive parking map for use in accordance with the present disclosure.

[0034] Figure 16 depicts a user interface displaying a user information screen for use in accordance with an implementation of the present disclosure.

[0035] Figure 17 depicts a user interface displaying a vehicle information screen for use in accordance with an implementation of the present disclosure.

[0036] Figure 18 depicts a user interface displaying a parking lot information screen for use in accordance with an implementation of the present disclosure.

[0037] Figure 19 depicts a user interface displaying a violations information screen for use in accordance with an implementation of the present disclosure.

[0038] Figure 20 depicts a schematic of a parking lot and associated parking spots for use in accordance with an implementation of the present disclosure.

[0039] Figure 21 is a schematic of a parking area and designated camera regions, queues, and lots, in accordance with an implementation of the present disclosure.

[0040] Figure 22 depicts a schematic of a license plate queue system in accordance with an implementation of the present disclosure.

[0041] Figure 23 is a flowchart of a series of acts in a computerized method in accordance with the implementations of the present disclosure.DETAILED DESCRIPTION

[0042] The present disclosure provides systems, methods, and computer program products that enable efficient parking lot enforcement and management. For example, the present disclosure includes a computer-implemented method that, in tandem with an identification device, can track object permissions and location. The end user can then receive and view object parking data, using the provided information to simplify and reduce costs associated with the parking monitoring and enforcement process.

[0043] In particular, the present disclosure provides one or more solutions for parking enforcement and monitoring, which enable the parking monitor (e.g., parking enforcement or monitoring personnel) to monitor parking lots remotely, accurately, and efficiently. This can enable, among other things, the ability to provide more timely and accurate parking enforcement without the need to assign a large number of employees to continually canvas parking lots in search of parking violations. Additionally, because the parking authorization and enforcement can be done essentially in real-time, parking enforcement activities can be handled more efficiently and in a timely manner, thereby avoiding a lot of the typical back- and-forth of appealing tickets and parking data on the backend that might happen in conventional systems.

[0044] Turning to the Figures, Figure 1 illustrates a schematic of a system 100 for parking monitoring and enforcement, delivering a response to an end user (i.e., a parking monitor, parking attendant, or other enforcement personnel) of parking status in accordance with the present disclosure. For example, Figure 1 illustrates that system 100 comprises a server 110, which can include a rules component 105, an identification module 115, and an artificial intelligence object identification component or Al object identification component 125. Figure 1 also shows that the server 110 can communicate over a network 130. By way of explanation, references to an end user are interchangeable with a parking monitor or parking enforcement personnel, as such users will normally be the primary operators of either a desktop or mobile app version of the user interfaces denoted herein. Generally speaking, end users will be a parking lot owner or its contracted or employed monitoring and enforcement personnel. In some implementations, however, aspects of the present disclosure may also include one or more user interfaces that enable object operators (e.g., vehicle drivers, students, employees using a parking lot, etc.) to login and view the status of their own parking activities, download and pay citations, find available parking spaces, or the like.

[0045] Returning to Figure 1, one of ordinary skill will appreciate that server 110 may communicate via a wireless connection interface and can additionally or alternatively be configured for a hardwired network communication. Figure 1 further depicts that the server 110 can communicate over a network 130 with an object identification device 120, in this case. one or multiple cameras (still or motion-based), represented by the single identification device 120 (camera) in system 100. The object identification device 120 views an object 140, in this case a vehicle, and communicates with the server 110 to assign it a unique Al object identification component 125 (ID). The object identification device 120 can also identify anobject identification attribute associated with the object 140, in this case, a vehicle license plate number.

[0046] As shown in Figure 1, the object identification device 120 (or multiples thereof can observe the object 140 at different angles and viewpoints as it proceeds to the parking area 160. The object identification device 120 will view the object’s 140 location, and pass the identified object data (e.g., shown as ID 125 in Figure 1) and location information via message 170a to server 110. Server 110 can then parse the image and object data (shown as ID 125 in Figure 1) passed from the camera (or multiple cameras) 120 to translate the information into various text values. For example, the server can use ID module 115 to use one or more forms of image segmentation in connection with Al object identification component 125 to identify, classify', and otherwise process the image to determine that the received image for the object 140 represents a car of a particular make, model, and color.

[0047] The ID module 115 can also perform other image recognition tasks in connection with Al object identification component 125 to determine a particular value, such as by using optical character recognition to identify a license plate value, on either the front or rear side of the object 140 (or elsewhere on the object), or a parking indicium present through a front, side, or rear window. The server can further determine from the received image and location information that the object 140 is positioned in a particular parking stall location (e.g., spot 165a. spot 165b) having various ordinal coordinates, or other types of mapping coordinates. ID module 115 at server 110 can then coordinate with Al object identification component 125 and rules component 105 to determine what permissions should be attached to object 140. Figure 1 shows this permission, which is represented by the identification attribute 135 passed to mobile device 150 via message 170b. It should also be known that implementations of the present disclosure may determine that a vehicle is unauthorized even when it's not visible to an identification device. For example, in garages with blind comers or pillars where vehicles are not directly viewable in certain spots, system 100 can infer the invalid objects based on entry to the blind "zone" without a corresponding exit. In these cases, system 100 can display a count of inferred invalid objects alongside license plates and descriptions for the blind "‘zone" that identification objects cannot directly see.

[0048] Server 110 can then verify the validity of the parking spot 165a (meaning its association with a particular permission of object 140) through ID module 115. The server 110 can then communicate over network 130 with mobile device 150 to relay associations and other data. Thus, for example, the parking monitor interface 200 (Figure 2) can display an object list 145 and the associated parking status 155. For example, object list 145 may indicate acomprehensive list of all objects (e.g., 140, or others) located in the parking area 160, or it may provide a filtered view of objects that are parked in impermissible areas. Either way, the parking status 155 confirms or alerts the parking monitoring enforcement personnel through mobile device 150 if object 140 is parked in an invalid location or otherwise confirms that it is permitted at its current location. The mobile device 150 display can then indicate that the object passes parking validation, as shown for any number of one or more additional objects in object list 145, along with the associated parking status 155 for each one.

[0049] The following Figures show various displays and interactions provided through one or both of the server 110 display, or a display on mobile device 150. For example, Figure 2 illustrates an exemplary' login screen displayed via user interface 200 when a user accesses the parking monitoring application (or service) for the first time. For example, the system may prompt the parking monitor to provide login information generated by the system. The system may prompt the parking monitor to create a unique password if they are logging in for the first time. The system can then grant the parking monitor access to additional schematics and information after the system has received the appropriate credentials from the parking monitor.

[0050] Figure 3 shows that, upon logging in, the digital display can provide a dashboard 205 through a user interface 200. The dashboard 205 can display statistical trends and various analytics (e.g., items 202) that parking monitoring or enforcement personnel may select for further review. The dashboard 205 enables the parking monitor to track parking occupancy (item 202a) and violations of the entity through the user interface 200, as well as other filterable and selectable data on a per-object, per-person, or per-parking4ot basis. The parking monitor can then view the system dashboard to see the typical occupancy of certain parking lots (item 202b) and other related information. Figure 3 further illustrates that the parking monitor can view a percentage occupancy (item 202a) as well as a summary of parking violations for any given lot. For example, in Figure 3, system 100 allows the parking monitor to select the view of data associated with a specific lot or the lots of the identified parking I ot-owning or managing entity 210 (e.g., a university, business, etc.) as a whole. This data may be viewed as configurable items 202 that can be pinned to the dashboard 205, allowing for quick access and customization by the parking monitor. Any number of items 202 can be pinned or viewed by a parking monitor on the dashboard 205. Items 202 can include, but are not limited to, real-time occupancy heatmaps, violation ty pe breakdowns, historical occupancy trends, revenue from fines, top-violated lots, license plate recognition alerts, permit usage statistics, peak-hour analysis, enforcement officer activity logs, and custom threshold alerts. Items 202 can be staticor moving graphics. Items 202 can also be self-contained widgets capable of pinning to the dashboard at various locations.

[0051] Figure 4 illustrates that the user interface 200 can display a bird’s-eye view of a particular parking area 160 monitored by the system 100. In particular, Figure 4 shows that the system 100 can provide a live view of parking area 160, the status of various associated spots165 (e.g.. spot 165a, spot 165b, etc.), and the location of the one or more identification devices 120. The system 100 can then differentiate a parking spot 165 and the associated object 140 occupying the spot 165 according to parking permission, which can then be displayed to the parking monitor through a user interface. The parking monitor interface can then differentiate the status of each spot 165 using colors associated with different parking statuses. A difference in color (or pattems / gradient, as shown in Figure 4) of the spots 165 indicates whether a current parking violation is associated with that spot 165. Spots 165 that are legally occupied are depicted in green. In contrast, those depicted in red are incorrectly occupied, meaning that the given stall is occupied by an obj ect that does not have the applicable authorization for that stall. Additional colors or visual indicators may represent other parking statuses such as temporarily reserved spots, spots under maintenance, time-limited event parking, electric vehicle-only zones, handicap-designated spaces, loading / unloading zones, and spots pending verification or under dispute.

[0052] Figure 5A illustrates the user interface 200, which may be displayed to the parking monitor, showing current parking violations 204 specific to the entity 210. For example, Figure5A shows that user interface 200 allows the parking monitor to organize and sort violations 204 by various metrics. For example, Figure 5 A (and Figure 5B) illustrates that, for entity 210, various violations 204 can be shown and sorted by the system 100 upon request, such as sorting by license plate number, recency of the violation, the user or entity tied to the violating vehicle, or other metrics of interest, according to the time the corresponding vehicles were parked.Through the user interface 200, the parking monitor may sort the violations 204 according to the time parked, the violation time, or the associated parking lot.

[0053] Along these lines, Figure 5B illustrates a scenario in which the user interface 200 is updated to show that object 140 has parked in spots 165, which are monitored by the entity 210. In particular, Figure 5B shows that objects can be displayed on the user interface 200 as identified by a vehicle license plate. The user interface 200 can also allow the parking monitor to search for a license plate in a designated and Tillable search field. For example, the system 100 may record the number of times a vehicle / object 140 has been parked, as well as the number of parking citations associated with a vehicle / object 140. The user interface 200 canalso show the date of the most recent known time that the vehicle / object 140 was recognized on the parking area 160. and store that information so that it can be retrieved at a later point and displayed through user interface 200.

[0054] Figure 5C further shows that the user interface 200 can be updated by server 110 to provide a history' of a specific object identifier, in this case, a vehicle license plate, such as through a pop-up interface 200a, or other navigation tool. The system 100 allows the parking monitor to select a specific license plate and can then display violations received by a specific vehicle through the user interface 200 through the pop-up interface 200a. The system allows the parking monitor to edit a violation as well as to adjust corresponding information through editable fields 206 in the user interface 200, as shown in Figure 5C.

[0055] Figure 6 illustrates a schematic of user information specific to the entity 210 and the corresponding initial setup of the system. The system 100 can prompt the parking monitor through the user interface 200 to provide information in the appropriate fields (e.g., fields 206). For example, user interface 200 of Figure 6 allows entity 210 to change the entity name, fees (e.g., field 206a), logo, and payment information (e.g.. field 206b). Depending on the organization or entity, there may be more or fewer editable fields. Fields 206 can be togglable, selectable, fillable, or otherwise interactive portions of user interface 200 that allow the parking monitor to customize or change characteristics of system 100. Additionally, the system 100 allows the entity 210 to edit previously provided information through the user interface 200. The system 100 can provide still further pop-up screens, fields 206, items 202. or other navigation tools for additional information.

[0056] For example, Figure 7A illustrates a user interface that can be displayed as a pop-up interface 200b containing parking citation information for an object or operator of the object 140. In some implementations, pop-up interfaces can be more traditional user interfaces, like the dashboard. Through the pop-up interface 200b, system 100 allows the parking monitor to select spots 165 to issue a citation or delete the associated violation. The pop-up interface 200b displays items 202c and 202d. For example, items 202c and 202d can provide essential contextual information to assist the parking monitor in making informed enforcement decisions directly from the pop-up interface 200b. Item 202c displays a list of active permits associated with object 140, including permit types, expiration dates, and any applicable restrictions or assigned zones. This allows the monitor to quickly verify whether the object is authorized to occupy the selected spot. Item 202d can present a history of past and present citations linked to object 140, offering a view of various violation types, their statuses (e.g., paid, disputed, unresolved), and any patterns of repeat offenses.

[0057] Figure 7B shows that the system also allows the parking monitor, through pop-up interface 200c. to send a citation to be printed, such as on a mobile print device. In addition to printing, the pop-up interface 200c provides multiple export options, allowing citation data to be saved or transmitted in various formats, such as PDF, CSV, EXCEL, or any other suitable format. These options can enable seamless integration with external systems, record-keeping platforms, or reporting tools. The interface may also include filters and customization settings, allowing the parking monitor to select specific data fields, time ranges, or citation types to include in the export.

[0058] Figure 7C illustrates that the manual citation system 100 can include a user interface 200 configured to streamline the citation decision-making process for a parking monitor. The manual citation system 208 may be implemented through user interface 200 and is designed to present flagged image data 212 and associated parking information 214 in a sequential, reviewable format. The system 100 can receive from one or more object identification devices 120, a plurality of flagged image data 212 (e.g., 212a. 212b, 212c) corresponding to an object 140 (represented herein as a license plate or flagged image data 212a) suspected of a parking violation. The flagged image data 212 may include still images or video frames captured from a plurality of different views of the object 140, such as from multiple overhead or angled cameras positioned throughout the parking area 160. These views may be selected to provide the parking monitor with sufficient visual context to assess the validity of the parking behavior. The flagged image data 212 can be transmitted to server 110 and processed by the identification module 115 and the Al object identification component 125. The system 100 may automatically populate fields 206 (e.g., 206c) based on the received data, including the object identification attribute (e.g., license plate number), the associated parking spot 165, the time of the violation, violation characteristics (e.g. cost / fees) and any applicable permissions retrieved from rules component 105.

[0059] As shown in Figure 7C, the user interface 200 can display the flagged image data 212 in one or more review panels positioned adjacent to each other, similar to the items 202 discussed above, along with associated parking information 214. The parking monitor can also be presented with a selectable citation decision interface 216. which includes options to either assign a citation or dismiss (pass) the citation for the object 140. The system 100 can also allow the parking monitor to confirm or update the automatically populated citation fields, such as violation ty pe, citation fee, issuing personnel, etc. Once the parking monitor confirms or dismisses the citation, the system 100 can automatically advance to the next flagged object 140 and display the corresponding image data and parking information for review. This sequentialreview process allows the parking monitor to efficiently process multiple potential violations in a streamlined, user-guided workflow. In some implementations, the system 100 may also include a feedback mechanism allowing the parking monitor to flag uncertain cases for further review or escalate them to a supervisor. Furthermore, the confirmation and dismissal information can be fed into an artificial intelligence algorithm, a large language model, a neural network, a machine learning algorithm, etc., to further refine the detection of violations within the systems of the present disclosure. This manual citation interface can enhance the efficiency and accuracy of parking enforcement by enabling real-time, image-based decision-making while reducing the cognitive load on the parking monitor.

[0060] Figure 8 illustrates another iteration of the user interface 200, corresponding to an operator list (e.g., a driver corresponding to a given object 140), which can further display the names of individuals 218 and their associated permissions 220. For example, in Figure 8, the system 100 enables a university employee to view employees who can then use the system, including those authorized to issue citations (e g., supervisors, parking enforcement, and security administrators). Depending on the individual permission selected, the system 100 can then allow the parking monitor to view and edit specific system data through the user interface 200. For example, among other things, user interface 200 can provide the parking monitor (or other system users, as applicable) with the ability7to add or delete employees or change current employee information stored by the system.

[0061] Figure 9 illustrates that user interface 200 can also provide a display of multiple parking lots and their associated permissions. For example, the system 100 can allow parking areas 160 to have unique permissions and enforcement rules 222. These unique permissions and enforcement rules 222 can include grace period times, camera operations, active days, and / or various other permissions or rules. The system 100 can receive requests from the parking monitor to edit parking area requirements and permissions. The system 100 can then also allow the parking monitor to add additional parking areas and parking passes as needed.

[0062] Figure 10A illustrates a list of parking permits registered by the parking monitor. The parking monitor (generally located at the backend) can edit the permit type (usually represented by a letter, number, identifying object, color, etc.) and the description of the permit to be stored by the system. For example, the parking monitor may want to edit the '‘Used At” section 224 illustrated in Figure 10A. A single lot may be accessible by more than one permit type, or it can only allow a single type of permit, depending on the input of the parking monitor. The parking monitor can adjust any characteristic of a permit, such as activity status, cost, description, etc., through system 100. The system 100 allows the parking monitor to removepermit types or add anew one if necessary. The system 100 also can allow the parking monitor to associate more than one object with a single permit (e.g.. one permit can cover two or more vehicles if permitted).

[0063] Figure 10B illustrates permit durations that are adjustable by the parking monitor. User interface 200 can allow the parking monitor to adjust the duration or activity time 226 (e.g., a characteristic of a permit) based on the calendar year, academic year, or any suitable timeline. For example, a university may have some permits that are only active during the academic year, while other permits are active at all times, allowing staff to access certain parking lots, but not students during the summer months.

[0064] Figures 11 through 16 illustrate various mobile screens that can be implemented with mobile device 150 in accordance with one or more implementations of the present disclosure. For example. Figure 11 depicts the user interface 200 help screen, where the system may prompt the parking monitor for feedback or allow the parking monitor to submit a request for help. It should be appreciated that any of the user interfaces described herein can be formatted for use on a mobile device or a more static computer. Unless explicitly stated otherwise, any user interface described herein can be adapted for various formats (e.g., phones, computers, tablets, etc.).

[0065] Figure 12 depicts a mobile user interface 200 profile screen displayed by the system.The system 100 can then prompt the parking monitor to input defining characteristics such as name, profile picture, and email address. The system 100 can then also allow the parking monitor to select customization settings or preferences 228 provided by the system. Preferences 228 can include things such as selecting their preferred home page based on their role or workflow. System 100 can also allow users to set a default sorting method for parking data, such as sorting by time parked, violation severity, or alphabetical order. The mobile user interface 200 may also include navigation options 230, allowing a user to navigate through the various screens or interfaces of system 100.

[0066] Figure 13A depicts a mobile user interface 200 parking violation screen as may be displayed on device 150. For example, Figure 13A shows that mobile device 150 can display the license plate number and for an object (shown as a listed item 141). as well as the location of the object as viewed by the camera. The system may also display a list of violations, prompting the parking monitor to sort the violations in a variety of ways, and / or print out a citation, as needed.

[0067] Figure 13B depicts a mobile user interface 200 that is displaying a listing of lots 142 for a given entity. The listing of lots 142 can provide overview information to a parking monitorat a quick glance, such as the number of current violations or the lot's current capacity. A parking monitor may select any of the lots from the listing of lots 142, wherein the system 100 can direct them to a pop-up or similar new page / user interface that provides more detailed information or accessibility.

[0068] Figure 14A depicts a mobile user interface 200 updated for issuing a parking citation146. The system may alert the parking monitor of previous citations associated with an object and provide information 144 such as the date and time of previous citations, to the parking monitor. The system 100 can then prompt the parking monitor to input data into corresponding fields, such as the citation fee amount and employee name. As shown in Figure 15, the parking monitor can have an option to adjust the fee of a ticket, to see history for the associated object ID license plate), mark a ticket as issued, edit who is issuing the ticket, and view this all on an interactive map of the parking area 160. Figure 14A further provides selectable buttons on the lower portion of the mobile user interface 200 for printing the ticket / citation from the mobile device, approving the citation, or deleting the citation.

[0069] Figure 14B illustrates the pop-up interface 200d. Pop-up interface 200d can provide a user with flagged image data 212d and additional relevant information that corroborates a given violation or ticket. For example, system 100 may cause pop-up interface 200d to display after a user interacts with the interactive map of the parking area 160, as show n in Figure 14A. A user may swipe or navigate through the relevant information to confirm the violation / tickethas been correctly issued.

[0070] Figure 1 depicts a mobile user interface 200 schematic of an interactive parking area 160 map with different colors indicating the status of the associated parking spot 165, as previously shown in other interfaces herein. The system 100 can then assign different colors to a parking spot 165 according to the status of the spot 165. The system 100 can then associate a color with a parking spot 165 (the colors herein are represented by varied gradients and patterns). For example, the color red can be associated with a parking spot 1 5 with a current violation. The system 100 can then prompt the parking monitor to select a spot 165 to provide the parking monitor with information corresponding to the spot 165. The system 100 can then display violation information, such as the violation type and the time of the violation, when selected by the parking monitor. The system can also display the current location of the mobile device being used to access the mobile user interface 200 to provide a user with a real-time location of their device within the bounds of the parking area 160 map (should it be located there).

[0071] Figures 16, 17, and 18 depict alternative or additional views of user interface 200 and relevant user information screens for entering operator information for vehicles, as well as available lots for parking of interest to the operator. System 100 can utilize the information input through these user interface 200 screens so that permissions associated with the user can be associated with one or more objects (e.g., various vehicles owned or used by the user). For example, Figure 16 shows that user interface 200 can prompt the parking monitor to input user information, such as name, user ID, permissions, and photo, into one or more fields 206 (e.g.. 206d and 206e). The system 100 can then allow the parking monitor to update user permissions as well as to alter the number of authorized users. Similarly, Figure 17 depicts the user interface 200 vehicle information screen. The system 100 can then prompt the parking monitor to input entity vehicle information as applicable. The system 100 can then store information such as vehicle make, model, color, and license plate (such as in field 2061) so that this is associated with the operator thereof.

[0072] Furthermore, Figure 18 depicts a user interface 200 parking area information screen. The system 100 can then prompt the parking monitor to input the number of parking areas and the associated parking permissions into field 206 (e.g., 206g). The system 100 can then allow the parking monitor to assign certain parking permissions, parking periods, and grace periods to a parking area. In at least one implementation, the end user can be associated with multiple vehicles or objects and multiple different lots, such as through payment of various levels of access, or other forms of permission granting through system 100.

[0073] Figure 19 depicts a user interface 200 violaton information screen for use by a parking monitor to assign a particular violation. The screen of Figure 19 allows the parking monitor to make adjustments where it may be appropriate through one or more editable / fillable fields 206 (e.g., field 206h). For example, the system 100 can prompt the parking monitor to select a number of violation types designated by the entity and filter through them using one or more pop-up interfaces 200 (e.g., 200e). The system 100 can then prompt the parking monitor to input associated information with the violation t pe, including the method desired to determine the citation severity’ and associated fee, into fields 206.

[0074] Figure 20 depicts a schematic of a parking area 160 and associated parking spots 165. Figure 20 illustrates a component of the system’s object recognition and tracking. The Figure shows green and red icons associated with each parking spot 165, displaying to the parking monitor the status of each parking spot 165. The colors of each parking spot 165 can indicate vacancy, a valid parking, and invalid parking, or various other identifiable / indicatable statuses. A parking lot summary 166 is also shown, sorting vehicle license plates by valid and invalidparking passes. One or more identification devices (overhead and / or non-elevated cameras / sensors) can communicate with each other to provide complete coverage over parking area 160 to ensure real-time updates for each parking spot 165 are continuously generated.

[0075] In some implementations, the systems of the present disclosure can operate in a capacity -monitoring mode that tracks stall / spot occupancy without identifying specific vehicles or determining parking permissions. In this mode, one or more object identification devices 120 (e.g., one or more overhead cameras, as described in Figure 21) can capture top- down or aerial image data of parking spots 165 within a parking area 160. The cameras can be positioned over or above the parking spots 165 while also within the bounds of the parking area 160. For example, the cameras may be positioned on poles, posts, walls, or other elevated structures to advantageously allow them to see past multiple rows or columns of objects. In at least one embodiment, the cameras may only be positioned adjacent to any given parking spot (i.e. outside of the area that defines a given parking spot). This implementation can reduce the number of required identification devices, sensors, or cameras needed to maintain its real-time capacity map. System 100, through server 110, can process image data gathered from the identification devices 120 using the identification module 115 and Al object identification component 125 to determine whether each parking spot 165 is occupied or unoccupied.

[0076] As shown in Figure 20, an interactive map can then display which spots are occupied and which are available. In some embodiments, the system does not utilize license plate recognition or any other object identification attribute beyond vehicle recognition to perform this analysis. Further, this implementation may not include any sensors or devices besides one or more cameras to gather parking information. This implementation can generate a real-time digital map of the parking area 160 based solely on stall / spot occupancy. It can display this map through a user interface (i.e., a mobile device user interface or a screen located at the parking location), using visual indicators (e.g., color-coded or shape overlays) to show which parking spots are currently available or occupied. The system can update the map continuously or at defined intervals, allowing parking monitors or end users to view current availability without requiring manual inspection by the user or the enforcement personnel. This overhead- only configuration supports lightweight, scalable deployment in environments where privacy concerns, infrastructure limitations, or regulatory constraints preclude the use of license plate recognition. It also enables the system 100 to provide real-time parking availability data for public lots, commercial garages, or event venues, where enforcement is not required but occupancy tracking remains valuable.

[0077] Figure 21 is a schematic of a parking area, such as previously shown herein, which further shows designated camera regions, queues 162, and lots, in accordance with an implementation of the present disclosure. As vehicles move throughout a parking area 160, the vehicles will move into and out of the view of any given camera or set of cameras. The cameras may include ground-mounted License Plate Recognition (“LPR”) cameras, which maybe used, for example, for the purpose of identifying and reading vehicle license plates. The cameras can also include other higher-view cameras, such as security cameras mounted at higher levels (’‘Overhead Cameras"), which can have a wider view of a larger region of a parking area 160. Through the combination of LPR and Overhead camera systems, the system 100 can maintain identification of any given set of one or more vehicles on a continuous basis, whether monitoring one or hundreds or thousands of vehicles at a time, moving in and out of a particular camera’s field of view. In particular, the system 100 can continuously monitor any number of vehicles in the area, regardless of their location within a parking lot, by actively switching cameras as the vehicle enters and exits a given camera’s (or a set of multiple cameras') field of view. To facilitate the handoff between cameras, the system 100 may subdivide a given parking area into Camera Regions, Queues, and Lots, as illustrated in the diagram below. In another embodiment, the system 100 may not use queues but rather a set of rules or a neural network to interpolate and predict the camera regions through which the object would travel.

[0078] Parking areas (i.e., parking lots) 160 can be divided into one or more Camera Regions, each of which represents the field of view of one overhead camera of various parking spots 165. Each Camera Region has one or more parking spots 165 within its field of view . While overhead camera views may overlap, in at least one implementation, any particular parking spot may be assigned to a specific one or multiple cameras, such as the camera(s) that has / have the clearest view of the spot. In at least one implementation, therefore, the system 100 can be configured such that every spot within a given parking area 160 is assigned to a single Camera Region, which in turn may consist of one or multiple cameras servicing the region.

[0079] In addition, in at least one implementation, the system 100 can assign one or a plurality of localities in a parking area 160 a unique ID. For example, the system 100 can assign one or more (or all) of the parking spots within a Camera Region an ID number that is unique within the given Camera Region. The system, in turn, monitors the occupancy status of the each assigned parking spot 165(a. b, etc.) such that, if queried, the Camera Region is able to return a list of occupied spots as well as the license plate numbers of the vehicles occupying the given spots in the assigned Camera Region. When the system 100 detects a vehicle entering a CameraRegion through any of its assigned queue regions, the Camera Region queries the associated queue to get the track ID and license plate of the vehicle that it detects (see "Queueing System” below for more details).

[0080] By way of explanation, a “queue” in this example represents the areas where vehicles can move from one Camera Region to another. In at least one implementation, Figure 21 shows that there can be at least two types of queues, namely an Entrance Queue and an Internal Queue. For purposes of this disclosure and claims, an “Entrance Queue” contains an LPR camera, and represents a region where a vehicle may enter or exit a lot (or parking area 160); meanwhile, an “Internal Queue” represents a location where a vehicle can move from one Camera Region to another. Because parking lots / areas frequently have constraints regarding camera placement, particularly when it comes to LPR cameras, a FIFO (first in, first out) queueing system can be implemented by system 100 to provide flexibility with regard to the maximum distance between the LPR camera and its corresponding overhead camera.

[0081] Figure 22 depicts a schematic of a license plate queue system in accordance with an implementation of the present disclosure. In at least one implementation, one or more LPR cameras may be located some distance away from the field of view of overhead cameras. As such, a queue system can be implemented to resolve any discrepancies. Accordingly, when a vehicle is detected on the LPR camera, the license plate that is read by system 100 can be pushed into a first-in-first-out (FIFO) queue of vehicles awaiting identification by the overhead camera, as shown in Figure 22. As new vehicles are detected by the overhead camera, the oldest license plate in the queue can be read and assigned to the identified vehicle.

[0082] In addition, Figure 22 illustrates an exemplar}' parking lot / area 160 in its entirety', comprising one or more Camera Regions, alongside one or more Queues representing the pass- off regions within the lot. A valid lot in accordance with one or more implementations of the present disclosure may contain at least one Camera Region, and have at least as many Queues as it has Camera Regions. In addition, a valid lot can also contain at least one Entrance Queue equipped with an LPR camera, and generally should not contain any entrances that do not contain an Entrance Queue equipped with an LPR camera. Every’ parking spot (165) yvithin a lot / area 160 has an ID number that is unique within the organization (university, business, etc.) that the lot belongs to the particular organization. This unique ID is separate from the number assigned to the parking spot 165 by the Camera Region.

[0083] To determine lot occupants, the system 100 can query each Camera Region yvithin the lot. and build a list of vehicles in the lot / area 160. The system can then check the license plate of each vehicle against the organization’s database of parking permits to determine the validityof the vehicle residing in the particular parking spot 165. The vehicles parking without authorization (e.g.. illegally) can then be recorded, and the system can pass the information through internal representational state transfer application program interfaces (or REST APIs) to the enforcement application and administrator portal for system 100.

[0084] In an alternative or additional embodiment, when compared to the process shown inFigure 22, the system 100 can process image data received from one or more object identification devices 120 using various temporal and asynchronous techniques. For example, the system 100 may receive a set of image frames or short video segments corresponding to an object 140 as it enters, moves through, or occupies a parking area 160. These image frames may be captured from multiple angles or camera regions and may be processed either sequentially, in parallel, or at varied times.

[0085] Thus, the system 100 may employ a timeline-based processing approach, wherein image data is analyzed in chronological order to track the movement and behavior of an object 140 over time. This may include identifying entry and exit timestamps, spot occupancy duration, or changes in object position across camera regions. The server 110 may use the identification module 115 in conjunction with the Al object identification component 125 to correlate image frames and generate a temporal profile of the objecf s activity. Alternatively, or in addition, the system 100 may utilize an event-based or asynchronous neural network architecture to process image data. In this implementation, the system 100 may analyze image frames or video segments in a non-linear or unordered fashion, allowing for real-time or near- real-time inference without requiring continuous live tracking. For example, the Al object identification component 125 may include or interface with a neural network trained to detect parking violations based on discrete visual cues, such as stall markings, object boundaries, or signage, regardless of the order in which the image data is received. This asynchronous processing model enables the system 100 to operate efficiently in environments with limited bandwidth or intermittent connectivity, as image data can be queued and processed as it becomes available. Furthermore, the system 100 may prioritize flagged image data (e.g., suspected violations) for immediate review by a parking monitor, while deferring non-critical data for batch processing. This enables the computer systems implementing the systems of the present disclosure to optimize processing capabilities and utilize multiple cores or threads simultaneously, thereby increasing the speed of image processing.

[0086] These flexible image processing capabilities enhance the adaptability and scalability of the system 100, allowing it to support a wide range of deployment scenarios, from small lotswith limited infrastructure to large-scale, multi-lot environments with complex camera networks.

[0087] To further illustrate the asynchronous and temporal processing capabilities of system 100, one example can be described as including a blue hatchback with license plate ABC 123. A license plate recognition (LPR) identification device (camera) can detect the blue hatchback as it enters a parking area and record the license plate. Camera A observes the vehicle entering the lot and tracks it as it moves across the field of view. As the vehicle exits Camera A’s view. Camera B detects the same blue hatchback entering its own field of view and subsequently parking in spot number 27.

[0088] In alternative implementations, a queue-based system could be used to associate vehicles across camera regions. For example, when a vehicle exited Camera A’s view, it would be added to a queue, and Camera B would attempt to match the next vehicle it detected with the oldest entry in the queue.

[0089] In this implementation, however, system 100 can incorporate a vehicle re-identification (Vereid) module. This module can generate a unique embedding (a vector of numerical features) for each detected vehicle based on visual characteristics such as size, color, and shape. For instance, when Camera A detects the blue hatchback, it generates an embedding (an alphanumeric or similar string) such as xa987fd. When Camera B detects what appears to be the same vehicle, it generates a similar embedding, such as xa967fb. The Vereid system can then compare these embeddings and determine that they are sufficiently similar to represent the same vehicle, even if the license plate data is not immediately available or the video segments currently gathered by the cameras are processed out of order.

[0090] This embedding-based matching enables the system to operate without FIFO queueing and can provide robust cross-camera tracking. Furthermore, the system 100 can include an event manager component that ingests discrete events (e.g., '‘vehicle entered lot,” “license plate read,” “vehicle exited camera view,” “vehicle parked in stall 27”) along with timestamps. These events are generated by the tracking software, which can process short (e.g., 15-second) video clips from each camera stream. For example, the following events might be generated from the scenario videoO-cameraLPR: “Blue hatchback license plate ABC 123 read”; video 1- cameraA: “Blue hatchback enters parking lot”; video2-cameraA: “Blue hatchback driving in parking lot” and “Blue hatchback leaves Camera A view”; video3-cameraB: “Blue hatchback enters Camera B view”; video4-cameraB: “Blue hatchback parks in spot 27”

[0091] An event manager component can then process these events in chronological order, regardless of the order in which the video clips are processed or received. This allows thesystem to maintain a coherent timeline of vehicle activity, even in environments with limited bandwidth or asynchronous processing constraints. By combining Vereid embeddings with event-based processing, system 100 can achieve high accuracy in vehicle tracking and parking validation across complex camera networks. This architecture supports scalable deployment in environments such as university7campuses, where hundreds of cameras and thousands of vehicles may be monitored simultaneously.

[0092] The present disclosure can also be described in terms of one or more methods comprising a series of acts for accomplishing a particular result. For example, Figure 23 illustrates that a method 300 for identifying and tracking an object for monitoring and / or enforcing parking can include an act 310 of receiving an object identification attribute. Act 310 includes receiving, by an identification device, an object identification attribute corresponding to an object. For example, an identification device 120 (e.g., a camera or a set of one or multiple cameras) can take images of an object 140 entering a parking area 160.

[0093] Figure 23 also shows that method 300 can comprise an act 320 of identifying a permission associated with the object. Act 320 includes identifying by the computer system, based upon the received object identification attribute: a permission associated with at least one of the object, or an operator of the object. For example, the device 120 sends its scanning information to server 110, which then processes the object to determine whether the vehicle / object 140 has identifying information that can be found in a rules component 105 (e.g., set of permissions known for various users and / or vehicles).

[0094] In addition, Figure 23 shows that method 300 can comprise an act 330 of determining a parking validator corresponding to the object. Act 330 includes determining, by the computer system, based upon the received identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object. For example, ID module 115 in connection with object identification component 125 and rules component 105 determine that the object and / or an operator thereof corresponds to a record that has information that validates the object’s presence at a parking area 160, or whether it is not found in the database with any permissions.

[0095] Furthermore. Figure 23 shows that method 300 can comprise an act 340 of displaying a parking authorization associated with the object. Act 340 includes upon request, displaying through a digital display device, a parking authorization metric associated with the object. For example, a parking monitor can open a digital display, such as at a desktop location, or on a mobile device 150 and see whether the object is determined as authorized for the given parking area 160 spot 165a, spot 165b, etc. If an error is returned, the parking monitor might manuallyenter the data corresponding to the object into a user interface to ensure that the information is accurate as received at server 110, or to pull up other information associated with the object or user. As noted herein, the parking monitor can provide citations, look up historical information for the object, edit information, and even print out a citation to be applied to the object, as appropriate. The parking monitor may be even able to adjust or clear out a citation if merited (e.g., an error in the object identification system).

[0096] Accordingly, the present disclosure provides a number of components and methods. For example, when a user desires to monitor and enforce parking, the parking monitor is provided with potential violations and object data on-demand. This can allow the parking monitor to focus resources on awarding citations without accompanying the need to employ enforcement individuals to continually search parking lots for violations.

[0097] The following discussion is intended to provide a brief, general description of a suitable computing environment in which the present disclosure may be implemented. Although not required, the present disclosure will be described in the general context of computer-executable instructions, such as program modules, being executed by computers in network environments.Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computerexecutable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

[0098] Those skilled in the art will appreciate that the present disclosure may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor- based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The present disclosure may also be practiced in distributed computing environments where local and remote processing devices perform tasks and are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0099] The present disclosure may comprise or utilize a special-purpose or general-purpose computer system that includes computer hardware, such as, for example, a processor and system memory, as discussed in greater detail below. The scope of the present disclosure also includes physical and other computer-readable media for cartying or storing computer-executable instructions and / or data structures. Such computer-readable media can be any available media that can be accessed by a general -purpose or special-purpose computer system. Computer-readable media that store computer-executable instructions and / or data structures are computer storage media. Computer-readable media that carry computer-executable instructions and / or data structures are transmission media. Thus, by way of example, and not limitation, the present disclosure can comprise two distinctly different kinds of computer- readable media: computer storage media and transmission media.

[0100] Computer storage media are physical storage media that store computer-executable instructions and / or data structures. Physical storage media include computer hardware, such as RAM, ROM, EEPROM, solid state drives (“SSDs”), flash memory, phase-change memory (“PCM”), optical disk storage, magnetic disk storage or other magnetic storage devices, or any other hardware storage device(s) which can be used to store program code in the form of computer-executable instructions or data structures, which can be accessed and executed by a general-purpose or special-purpose computer system to implement the disclosed functionality of the present disclosure.

[0101] Transmission media can include a network and / or data links which can be used to carry program code in the form of computer-executable instructions or data structures, and which can be accessed by a general-purpose or special-purpose computer system. A “network” is defined as data links that enable the transport of electronic data between computer systems and / or modules and / or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer system, the computer system may view the connection as transmission media. Combinations of the above should also be included within the scope of computer-readable media.

[0102] Further, upon reaching various computer system components, program code in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa). For example, computerexecutable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module ,and then eventually transferred to computer system RAM and / or to less volatile computer storage media at a computer system. Thus, it should be understood that computer storage media can be included in computer system components that also (or even primarily) utilize transmission media.

[0103] Computer-executable instructions comprise, for example, instructions and data w hich, when executed at a processor, cause a general-purpose computer system, special-purposecomputer system, or special-purpose processing device to perform a certain function or group of functions. Computer-executable instructions may be, for example, binaries, reagent format instructions such as assembly language, or even source code.

[0104] Those skilled in the art will appreciate that the present disclosure may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. The present disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. As such, in a distributed system environment, a computer system may include a plurality of constituent computer systems. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

[0105] Those skilled in the art will also appreciate that the present disclosure may be practiced in a cloud-computing environment. Cloud computing environments may be distributed, although this is not required. When distributed, cloud computing environments may be distributed internationally within an organization and / or have components possessed across multiple organizations. In this description and the following claims, “cloud computing7’ is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.

[0106] A cloud-computing model can be composed of various characteristics, such as on- demand self-service, broad network access, resource pooling, rapid elasticity, measured sendee, and so forth. A cloud-computing model may also come in the form of various service models such as, for example, Software as a Sen ice (“SaaS”), Platform as a Service (“PaaS"), and Infrastructure as a Service (“laaS”). The cloud-computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth.

[0107] A cloud-computing environment, or cloud-computing platform, may comprise a system that includes a host that is capable of running virtual machines. During operation, virtual machines emulate an operational computing system, supporting an operating systemand perhaps other applications as well. Each host may include a hypervisor that emulates virtual resources for the virtual machines using physical resources that are abstracted from view of the virtual machines. The hypervisor also provides proper isolation between the virtual machines. Thus, from the perspective of any given virtual machine, the hypervisor provides the illusion that the virtual machine is interfacing with a physical resource, even though the virtual machine interfaces with the appearance (e.g., a virtual resource) of a physical resource. Examples of physical resources including processing capacity, memory, disk space, network bandwidth, media drives, and so forth.

[0108] Aspects of the present disclosure can be described in terms of various different configurations and alternates thereof. For example, one configuration includes a first aspect, computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking, comprising; identifying, by a computer system in connection with one or more stationary cameras, an object within a parking area; receiving, by a first camera of the one or more cameras, an object identification attribute corresponding to the object within the parking area; identifying by the computer system, based upon the received object identification attribute from the first camera: a permission associated with at least one of the object, or an operator of the object; determining, by the computer system, based upon the received identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object; and upon request, displaying through a digital display device, a parking authorization metric associated with the object.

[0109] In a second aspect, the computer-implemented method as recited in any of the preceding aspects, wherein the obj ect comprises a vehicle. In a third aspect, the computer-implemented method as recited in any of the preceding aspects, wherein the object identification attribute comprises a license plate number. In a fourth aspect, the computer-implemented method as recited in any of the preceding aspects, further comprising: identifying previous data corresponding to the object (vehicle).

[0110] In a fifth aspect, the computer-implemented method as recited in any of the preceding aspects, wherein: the digital display device is a personal or portable digital device.

[0111] In a sixth aspect, the computer-implemented method as recited in the fifth aspect. further comprising: conveying rendering instructions of the display to the personal or portable digital device.

[0112] In a seventh aspect, the computer-implemented method as recited in any of the preceding aspects, wherein the digital display comprises: a digital dashboard, generated by the computer system, wherein the digital dashboard comprises one or more configurable items,wherein each configurable item comprises a graphical representation of data gathered from the one or more cameras; one or more user interfaces, generated by the computer system, that are accessible by way of the digital dashboard, wherein: a first user interface of the one or more user interfaces comprises a real-time interactive map of the parking area, the real-time interactive map comprises an indicator for spots that comprise a violation.

[0113] In an eighth aspect, the computer-implemented method as recited in any of the preceding aspects, further comprising: determining that the object is not permitted to be in the parking area; and determining a violation to be associated with the object.

[0114] In a ninth aspect, the computer-implemented method as recited in the ninth aspect, further comprising a manual citation system comprising: receiving, by the computer system, a plurality of flagged image data corresponding to the object comprising the violation, the flagged image data captured by the object identification devices; displaying, through a user interface, the flagged image data and associated parking information for review within automatically populated fields; providing, through the user interface, a selectable citation decision to assign a citation or to dismiss the citation for the object; receiving, through the user interface, an input to either assign or dismiss the citation, wherein the input completes the selectable citation decision; and upon completion of the selectable citation decision, automatically displaying a next associated image data and parking information that corresponds to another object.

[0115] In a tenth aspect, the computer-implemented method as recited in any of the preceding aspects, wherein: the identification attribute corresponding to the object comprises an externally displayed permit.

[0116] In an eleventh aspect, the computer-implemented method as recited in any of the preceding aspects, wherein: upon user request, displaying at least one vehicle and citation history of the vehicle on the digital display device by way of a different user interface.

[0117] In a twelfth aspect, the computer-implemented method as recited in any of the preceding aspects, wherein identifying the permission further comprises: sending the object identification attribute to a database; and receiving the parking validator from the database.

[0118] In a thirteenth aspect, the computer-implemented method as recited in the twelfth aspect, wherein: the parking validator comprises an indication that the object or operator thereof is not authorized for a location in which the object has been viewed by the identification device.

[0119] In a fourteenth aspect, the computer-implemented method as recited in the thirteen aspect, further comprising: sending display instructions to a mobile device; wherein the displayinstructions include an alert that indicates one or more of (i) lack of authorization for the object and / or operator thereof, or (ii) a fee associated with the object and / or operator thereof.

[0120] In a fifteenth aspect, a computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking, comprising; receiving, by a first identification device, a first object identification attribute corresponding to an object, wherein the first object identification attribute comprises image data corresponding to the object from at least a first view; receiving, by a second identification device, a second object identification attribute corresponding to the object, wherein the second object identification attribute comprises image data corresponding to the object from at least a second view; determining, by a computer system, based upon the received first object identification attribute and the second object identification attribute, a characterization of the object sufficient to identify the object and whether any permissions are associated with the object and / or an operator of the object; determining, by the computer system, based upon the received first object identification attribute and second identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object; upon request, displaying through a digital display device, a parking authorization metric associated with the object; and sending print instructions for a citation associated with the object upon request through a user interface.

[0121] In a sixteenth aspect, the computer-implemented method as recited in the fifteenth aspect, wherein: the first object identification attribute is gathered by the first identification devices before the second identification attribute is gathered by the second identification device, and the computer system processes the second identification attribute before it processes the first identification attribute.

[0122] In a seventeenth aspect, the computer-implemented method as recited in the fifteenth or sixteen aspect, further comprising transmitting a real-time notification to a user device associated with the operator of the object, the notification comprising the parking authorization metric and any associated violation information.

[0123] In an eighteenth aspect, a computer-implemented method for identifying and tracking an object for monitoring and / or enforcing parking, comprising; receiving, by one or more cameras, a first image data corresponding to a plurality of parking spots within a parking area; receiving, by the one or more cameras, a second image data that comprises a list of objects within the parking area; determining, by a computing system, based on the received first image data and second image data, an occupancy status for each of the plurality of parking spots; generating, by the computing system, a real-time digital map of the parking area, the digitalmap comprising an indicator of which of the plurality of parking spots are occupied, and which of the plurality of parking spots are available; updating, by the computing system, the real-time digital map in response to changes in occupancy detected by the one or more cameras: and displaying, through a digital display, the real-time digital map to indicate a current parking capacity and available parking spots within the parking area, if any.

[0124] In a nineteenth aspect, the computer-implemented method as recited in the eighteenth aspect, wherein the one or more cameras are only positioned over or above the parking area.

[0125] In a twentieth aspect, the computer-implemented method as recited in the eighteen or nineteenth aspect, wherein the occupancy status is determined without using license plate recognition.

[0126] The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described examples are to be considered in all respects only as illustrative and not restrictive. The scope of the present disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

CLAIMSWe claim:

1. A computer-implemented method for identifying and tracking an obj ect for monitoring and / or enforcing parking, comprising; identifying, by a computer system in connection with one or more stationary cameras, an object within a parking area; receiving, by a first camera of the one or more cameras, an object identification attribute corresponding to the object within the parking area; identifying by the computer system, based upon the received object identification attribute from the first camera: a permission associated with at least one of the object, or an operator of the object; determining, by the computer system, based upon the received identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object; and upon request, displaying through a digital display device, a parking authorization metric associated with the object.

2. The computer-implemented method as recited in claim 1 , wherein: the object comprises a vehicle.

3. The computer-implemented method as recited in claim 1, wherein: the object identification attribute comprises a license plate number.

4. The computer-implemented method as recited in claim 1 , further comprising: identify ing previous data corresponding to the object (vehicle).

5. The computer-implemented method as recited in claim 1, wherein: the digital display device is a personal or portable digital device.

6. The computer-implemented method as recited in claim 5, further comprising: conveying rendering instructions of the display to the personal or portable digital device.

7. The computer-implemented method as recited in claim 1, wherein the digital display comprises: a digital dashboard, generated by the computer system, wherein the digital dashboard comprises one or more configurable items, wherein each configurable item comprises a graphical representation of data gathered from the one or more cameras; one or more user interfaces, generated by the computer system, that are accessible by way of the digital dashboard.wherein: a first user interface of the one or more user interfaces comprises a realtime interactive map of the parking area, the real-time interactive map comprises an indicator for spots that comprise a violation.

8. The computer-implemented method as recited in claim 1, further comprising: determining that the object is not permitted to be in the parking area; and determining a violation to be associated with the object.

9. The computer-implemented method as recited in claim 8, further comprising a manual citation system comprising: receiving, by the computer system, a plurality of flagged image data corresponding to the object comprising the violation, the flagged image data captured by the object identification devices; displaying, through a user interface, the flagged image data and associated parking information for review within automatically populated fields; providing, through the user interface, a selectable citation decision to assign a citation or to dismiss the citation for the object; receiving, through the user interface, an input to either assign or dismiss the citation, wherein the input completes the selectable citation decision; and upon completion of the selectable citation decision, automatically displaying a next associated image data and parking information that corresponds to another object.

10. The computer-implemented method as recited in claim 1, wherein: the identification attribute corresponding to the object comprises an externally displayed permit.

11. The computer-implemented method as recited in claim 1 , wherein: upon user request, displaying at least one vehicle and citation history of the vehicle on the digital display device by way of a different user interface.

12. The computer-implemented method as recited in claim 1, wherein identifying the permission further comprises: sending the object identification attribute to a database; and receiving the parking validator from the database.

13. The computer-implemented method as recited in claim 12, wherein:the parking validator comprises an indication that the object or operator thereof is not authorized for a location in which the object has been viewed by the identification device.

14. The computer-implemented method as recited in claim 13, further comprising: sending display instructions to a mobile device; wherein the display instructions include an alert that indicates one or more of (i) lack of authorization for the object and / or operator thereof, or (ii) a fee associated with the object and / or operator thereof.

15. A computer-implemented method for identifying and tracking an obj ect for monitoring and / or enforcing parking, comprising; receiving, by a first identification device, a first object identification attribute corresponding to an object, wherein the first object identification attribute comprises image data corresponding to the object from at least a first view-; receiving, by a second identification device, a second object identification attribute corresponding to the object, wherein the second object identification attribute comprises image data corresponding to the object from at least a second view ; determining, by a computer system, based upon the received first object identification attribute and the second object identification attribute, a characterization of the object sufficient to identify the object and whether any permissions are associated with the object and / or an operator of the object; determining, by the computer system, based upon the received first object identification attribute and second identification attribute and the associated permission, a parking validator or authorization of: (i) the object and / or (ii) the operator of the object; upon request, displaying through a digital display device, a parking authorization metric associated with the object; and sending print instructions for a citation associated with the object upon request through a user interface.

16. The computer-implemented method as recited in claim 15, wherein: the first object identification attribute is gathered by the first identification devices before the second identification attribute is gathered by the second identification device, and the computer system processes the second identification attribute before it processes the first identification attribute.

17. The computer-implemented method as recited in claim 15, further comprising transmitting a real-time notification to a user device associated with the operator of the object, the notification comprising the parking authorization metric and any associated violation information.

18. A computer-implemented method for identifying and tracking an obj ect for monitoring and / or enforcing parking, comprising; receiving, by one or more cameras, a first image data corresponding to a plurality of parking spots within a parking area; receiving, by the one or more cameras, a second image data that comprises a list of objects within the parking area; determining, by a computing system, based on the received first image data and second image data, an occupancy status for each of the plurality of parking spots; generating, by the computing system, a real-time digital map of the parking area, the digital map comprising an indicator of which of the plurality of parking spots are occupied, and which of the plurality of parking spots are available; updating, by the computing system, the real-time digital map in response to changes in occupancy detected by the one or more cameras; and displaying, through a digital display, the real-time digital map to indicate a current parking capacity and available parking spots within the parking area, if any.

19. The computer-implemented method as recited in claim 18, wherein the one or more cameras are only positioned over or above the parking area.

20. The computer-implemented method as recited in claim 18, wherein the occupancy status is determined without using license plate recognition.

Images