Electronic lock control, and associated units, systems, methods, and devices

Abstract

Various embodiments relate to electronic lock control. In some embodiments, a system may include a mobile surveillance unit comprising at least one electronic locking device. The system may further include an application program to: receive, from a user device, a request to load a portal on the user device; provide, via the portal, a field for receiving a passcode associated with the mobile surveillance unit; receive the passcode; and cause a locking device of the at least one electronic locking device to unlock responsive to receipt of the passcode. Associated systems, methods, units, and computer-readable media are also disclosed.

Description

ELECTRONIC LOCK CONTROL, AND ASSOCIATED UNITS, SYSTEMS, METHODS, AND DEVICESPRIORITY CLAIM

[0001] This application claims the benefit of the filing date of United States Provisional Patent Application No. 63 / 776,810, filed March 24, 2025, for “ELECTRONIC LOCK CONTROL, AND ASSOCIATED UNITS, SYSTEMS, METHODS, AND DEVICES,” and of United States Provisional Patent Application Serial No. 63 / 778,189, filed March 26, 2025, for “ELECTRONIC LOCK CONTROL, AND ASSOCIATED UNITS, SYSTEMS, METHODS, AND DEVICES,” the disclosures of each of which are hereby incorporated herein in their entirety by this reference.TECHNICAL FIELD

[0002] This disclosure relates generally to electronic lock control, and more specifically to controlling one or more electronic locks, and to related units, systems, methods, and devices.BACKGROUND

[0003] With the advent of mobile technologies and the widespread adoption of smartphones, there has been a rapid increase in the number of devices and systems designed to be remotely controlled through mobile applications.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. l is a perspective view of an example mobile unit, in accordance with various embodiments of the disclosure.

[0005] FIG. 2 is a detailed view of an example storage box of a mobile unit, in accordance with various embodiments of the disclosure.

[0006] FIGS. 3A and 3B depict an example flow, according to various embodiments of the disclosure.

[0007] FIG. 3C depicts yet another example flow, in accordance with various embodiments of the disclosure.

[0008] FIG. 4 is a flowchart of an example method of controlling an electronic lock, according to various embodiments of the disclosure.1 Docket No. 54541-00053

[0009] FIG. 5 depicts an example system, in accordance with various embodiments of the disclosure.

[0010] FIG. 6 illustrates an example system that may be used to implement embodiments of the disclosure.DETAILED DESCRIPTION

[0011] Referring in general to the accompanying drawings, various embodiments of the disclosure are illustrated to show example embodiments related to electronic lock control. It should be understood that the drawings presented are not meant to be illustrative of actual views of any particular portion of an actual device, system, or structure, but are merely representations which are employed to more clearly depict various embodiments of the disclosure.

[0012] The following provides a more detailed description of the present disclosure and various representative embodiments thereof. In this description, functions may be shown in block diagram form to not to obscure the present disclosure in unnecessary detail. Additionally, block definitions and partitioning of logic between various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present disclosure may be practiced by numerous other partitioning solutions. For the most part, details concerning timing considerations and the like have been omitted where such details are not necessary to obtain a complete understanding of the present disclosure and are within the abilities of persons of ordinary skill in the relevant art.

[0013] In some conventional systems including a number of units (e.g., mobile units) (e.g., of a fleet of units) including mechanical locks, each unit may be associated with a universal physical key (i.e., for accessing various components (e.g., lock boxes, towing tongue, jack tool, etc.) of the unit). However, using physical keys is not ideal due to delays and costs associated with a missing key and the replacement thereof. Further, using a universal key poses a security risk. Also, in some conventional systems including electronic locks, a mobile application (i.e., installed on a mobile phone) and a local Bluetooth connection are required, even though a user (e.g., an individual shipping or serving a device (e.g., a mobile unit) may only need to unlock an electronic lock once.

[0014] Various embodiments of the disclosure relate to access control, and more specifically to controlling an electronic lock without the need or use of a mobile application. More specifically, various embodiments may include systems and methods 2 Docket No. 54541-00053for enabling a user to lock and / or unlock an electronic lock on a device (e.g., mobile unit) (e.g., of a fleet of devices (e.g., a fleet of mobile units)) without the need for a mobile application to be downloaded to a user device of the user.

[0015] Although various embodiments are described herein with reference to security and / or surveillance systems and / or mobile security and / or mobile surveillance units, the present disclosure is not so limited, and the embodiments may be generally applicable to any system and / or device that may or may not include security and / or surveillance systems and / or units. Further, although some embodiments are disclosed with reference to a mobile unit, the disclosure is not so limited, and a person having ordinary skill will understand that various embodiments may be applicable to other systems and devices, such as stationary units (e.g., a unit coupled to a stationary pole (e.g., a light pole), a structure (e.g., of a business or a residence), a tree, etc.). In other words, various embodiments may apply in any scenario and / or process and / or with any device and / or system including an electronic lock. Embodiments of the disclosure will now be explained with reference to the accompanying drawings.

[0016] FIG. 1 is a perspective view of an embodiment of an example unit 100, in accordance with various embodiments of the disclosure. Unit 100, which may also be referred to herein as a “mobile unit,” a “mobile surveillance unit,” a “mobile security unit,” an “MSU,” a “live unit,” a “physical unit,” or some variation thereof, may be configured to be positioned in an environment (e.g., a parking lot, a roadside location, a construction zone, a concert venue, a sporting venue, a school campus, without limitation). In some embodiments, unit 100 includes one or more sensors (e.g., cameras, weather sensors, motion sensors, noise sensors, without limitation) and one or more output devices (e.g., lights, speakers, electronic displays, without limitation). Unit 100 may also include at least one storage device (e.g., internal flash media, a network attached storage device, or any other suitable electronic storage device), which may be configured for receiving and storing data (e.g., video, images, audio, without limitation) captured by one or more sensors of unit 100.

[0017] In some embodiments, unit 100 includes a mobile security / surveillance unit. In these and other embodiments, unit 100 may include a portable trailer 102, a storage box 104, a head unit 106, and a mast 108 coupled to head unit 106, which may include for example, one or more batteries, one or more cameras, controllers / processors or other electronics, one or more lights, one or more speakers, and / or one or more microphones. According to some embodiments, a first end of mast 108 may be proximate 3 Docket No. 54541-00053to storage box 104 and a second, opposite end of mast 108 may be proximate, and possibly adjacent, to head unit 106. More specifically, in some embodiments, head unit 106 may be coupled to mast 108 at an end opposite to an end of mast 108 proximate to storage box 104.

[0018] In some examples, unit 100 may include one or more primary batteries (e.g., within storage box 104) and one or more secondary batteries (e.g., within head unit 106). In these embodiments, a primary battery positioned in storage box 104 may be coupled to a load and / or a secondary battery positioned within head unit 106 via, for example, a cord reel.

[0019] In some embodiments, unit 100 includes at least one computing device and / or other electronics powered by the one or more batteries. In some embodiments, valuable devices (e.g., hardware) may be securely housed in storage box 104 and in data communication with head unit 106. For example, head unit 106 may include one or more sensors or one or more output devices, and a computing device (e.g., in head unit 106 or storage box 104) may receive data from the one or more sensors and / or transmit instructions to the one or more output devices. As described above, in some embodiments, storage box 104 securely houses one or more hardware storage devices. The one or more storage devices may be in data communication with and / or integrated with the one or more computing devices.

[0020] In some embodiments, unit 100 may also include one or more power sources and / or power supplies. For example, unit 100 may include or be in electrical communication with one or more solar panels 109, which may provide power to one or more batteries of unit 100. More specifically, according to some embodiments, one or more solar panels 109 may provide power to a primary battery within storage box 104. In some embodiments, unit 100 may also include other power sources, such as one or more generators (e.g., fuel cell generator or other power generators). For example, storage box 104 may include a fuel cell generator and / or another power generator. As shown in FIG.1, unit 100 includes a scannable code (e.g., a QR code) 110 (e.g., affixed to any portion of unit 100, such as an exterior surface of storage box 104).

[0021] During transport or storage of unit 100, one or more components of unit 100 may be removed from unit 100, the mast 108, or head unit 106. In some embodiments, the mast 108 is an extendable or deployable mast and mast 108 is extended or deployed at the time of deployment of unit 100 in a field location. For example, mast 108 may be connected to trailer 102 and / or storage box 104 at a first end of mast 108, and 4 Docket No. 54541-00053head unit 106 may be positioned at an elevated position at the second end of mast 108 upon deployment of unit 100. In some embodiments, head unit 106 includes one or more sensors (e.g., cameras, weather sensors, motion sensors, noise sensors, without limitation) and one or more output devices (e.g., lights, speakers, electronic displays, without limitation) that are affixed to head unit 106 upon deployment. In some embodiments, head unit 106 is positioned on the second end of mast 108 prior to an electronic component (such as one or more sensors and / or one or more output devices) being connected thereto. In particular examples, unit 100 is deployed in a remote location, a poorly lit location, or at a location with limited assembly resources (such as ladders or other platforms from which a technician can work). In some examples, selected sensors (e.g., cameras and / or other sensor) and / or output devices may be stored in storage box 104 and / or remain in storage box 104 during storage, transport, and / or deployment.Security of storage box 104 is, therefore, paramount for unit 100.

[0022] FIG. 2 is a detailed view of an embodiment of an example storage box 204 (e.g., storage box 104 of FIG. 1) according to a least some embodiments of the present disclosure. Storage box 204 has a body 210 and a lid 212 that is moveable relative to body 210. As will be appreciated, storage box 212 may hold various components, such as a battery, a power generator, lights, sensors, cameras, control units (e.g., including control circuitry), without limitation. According to various embodiments, storage box 204 may include, and may be locked via, an electronic lock, which may be positioned internally (i.e., within body 210) (e.g., such that the electronic lock may not be visible while lid 212 is in a closed position). As shown in FIG. 2, code 110 is displayed on storage box 204. It is noted that in some examples, code 110 may be at least partially hidden but accessible to a user (e.g., on a back or bottom surface of body 210 or another portion of unit 100).

[0023] FIGS. 3A and 3B depict an example flow 300, in accordance with various embodiments of the disclosure. Flow 300 may include a process for managing access to and / or control of one or more electronic locks 301 of a device 302, such as a mobile surveillance unit or any other suitable device. Electronic lock 301 may include, for example, a trailer box lock (e.g., a lock for box 104 / 204; see FIGS. 1 and 2) (e.g., a lock to a box including one or more batteries, sensors (e.g., cameras), power generators, electronics, and / or other components) (a “battery box”), a tow bar lock, a mast lock, or any other suitable lock for a device. Electronic lock 301 may include any suitable electronic lock, which may be controlled in response to successful entry (e.g., remote entry) of a code.5 Docket No. 54541-00053

[0024] Flow may include an act 303 wherein a code (e.g., a scannable code, such as a QR code or a bar code) (e.g., code 110 of FIG. 1) for device (e.g., unit 100 of FIG. 1) 302 and a passcode (or login info) for one or more electronics locks 301 of device 302 may be generated.

[0025] In some embodiments, the passcode (or login info) may be a one-time passcode (e.g., only works once). Further, the scannable code may be affixed to device 302 (act 305) (e.g., such that the code may be accessible and scannable via a mobile device (e.g., smartphone, tablet, etc.). For example, the scannable code may be affixed to a base of device 302. Moreover, the generated passcode (or other login info) may be included and / or made part of documentation (e.g., transportation documentation) 304 (act 306), and the documentation may be provided to a user (e.g., a transportation partner, field or service partner, or other personnel or administrators). For example, each device (e.g., of a number of devices (e.g., unit 100 and / or device 302)) may include an identification number, wherein the scannable code may be associated with the identification number, and / or the associated documentation for each device may include the associated device identification number. Accordingly, device 302 includes the scannable code, and the passcode may be part of or included with the documentation 304. It is noted that some acts of flow 300 shown in FIG. 3A may occur at, for example, a manufacturing site.

[0026] In FIG. 3B, flow 300 may continue, for example, in the field (e.g., prior to, during, and / or after device 302 is transported, during service or maintenance of device 302, without limitation). Referring to FIG. 3B, the user, utilizing a user device (e.g., a mobile device such as a smartphone) 310, may scan the scannable code (e.g., QR code) (act 312) on device 302, which may cause, for example, a website 314 or other portal to launch (act 316) via user device 310. In some embodiments, website 314 may include prefilled information about the associated device (e.g., device 302). Further, the user may input an associated passcode (as provided in documentation 304) or other login information into website 316 (act 318). Upon entering the passcode, electronic lock 301 of device 302 may be controlled (e.g., unlocked). In some embodiments, electronic lock 301 may be unlocked via, for example, a cloud-to-cellular data connection (e.g., for one time use). In some embodiments, electronic lock 301 may automatically lock again after expiration of a time duration (e.g., 1 minute, 5 minutes, 1 hour, without limitation).Further, an alarm (e.g., an audible alarm) may sound (e.g., after a time duration) if6 Docket No. 54541-00053electronic lock 301 remains unlocked (e.g., if a lid / door of a box (e.g., box 104 / 204) remains open).

[0027] According to some embodiments, in response to one electronic lock (e.g., an electronic lock for a battery box) of a unit being unlocked, other electronic locks (e.g., a tow bar lock, a mast lock, without limitation) of the unit may also be unlocked.Moreover, in some embodiments, a system may track various information regarding users and / or devices (e.g., who unlocked what electronic locks, when were the electronic locks unlocked, how long were electronic locks unlocked, etc.). Moreover, according to some embodiments, tamper detection may be disabled when an electronic lock is unlocked (e.g., via embodiments described herein) and enabled when, for example, a lid to an unlocked enclosure is closed and / or the electronic lock is locked.

[0028] According to various embodiments, other personnel (e.g., an entity that owns or leases a device) may be able to unlock one or more electronic locks of a device remotely. Further, a system may be configured to query and report a lock state (e.g., locked or unlocked) of a selected device and / or the associated electronic locks of the selected device at a user or organization level. Additionally, alerts may be generated when any latch remains open (or electronic lock is unlocked) after an attempt is made to close a process (e.g., an associated ticket) or after a selectable time duration.

[0029] FIG. 3C depicts another example flow 350, in accordance with various embodiments of the disclosure. In flow 350, a pin (also referred to herein as a “passcode”) for an electronic lock may be generated (e.g., via PIN creation device 352). More specifically, for example, a trusted person 354 may cause the pin (e.g., an authorized pin or authorized passcode) to be generated. Further, trusted person 354 may provide the pin to another person 356, such as a 3rd party (e.g., a transportation partner, a field partner, a service partner, or any other person).

[0030] Further, person 356 (or another person having the pin), may scan (e.g., via a mobile device 357, such as a mobile phone, tablet, or other device) a scannable code on a device (e.g., a security / surveillance unit, such as a mobile surveillance unit) (e.g., including the electronic lock), which may cause an entry page (e.g., a website or other portal) to be accessible to person 356 (e.g., via the mobile device, such as a mobile phone or other device). Person 356 may enter a pin into the entry page (e.g., at block 358), and the entered pin may be compared to the generated (e.g., authorized) pin (e.g., at block 360).7 Docket No. 54541-00053

[0031] Associated data related to an operation (e.g., the generated pin, the entered pin, associated users (e.g., person 354, person 356, or other personnel), time, place (e.g., a location of the device (e.g., mobile surveillance unit), and / or other information) associated with flow 350 may be stored in a database 362. Further, responsive to a match between the generated pin and the entered pin, one or more application programming interfaces (APIs) may cause the electronic lock to unlock, as will be appreciated by a person having ordinary skill in the art. More specifically, for example, responsive to a match between the generated pin and the entered pin, a first API (e.g., a cloud API) 364 and / or a second API (e.g., edge unlock API) 366 (e.g., which may part of a mobile unit) may cause one or more electronic locks of the device (e.g., a unit, such as unit 100 of FIG. 1) to unlock. In the event the entered pin does not match the generated pin, the one or more electronic locks of the device may not be unlocked. It is noted that a pin validation act (e.g., at block 360) may also be performed at least partially via an API (e.g., a cloud API). Further, an API (e.g., a cloud API) may include a service that serves the entry page (e.g., portal and / or website) (e.g., for receiving a pin from person 356).

[0032] FIG. 4 is a flowchart of an example method 400 of controlling an electronic lock. Method 400 may be arranged in accordance with at least one embodiment described in the disclosure. Method 400 may be performed, in some embodiments, by a device or system, such as unit 100 (see FIG. 1), one or more components of flow 300 of FIGS. 3A-3B, one or more components of flow 350 of FIG.3C, a system 500 (see FIG. 5), a system 600 (see FIG. 6), or another device or system. Although illustrated as discrete blocks, various blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation.

[0033] Method 400 may begin at block 402, wherein a scannable code may be generated, and method 400 may proceed to block 404. For example, the scannable code, which may include, for example, a QR code or a bar code, may be generated. For example, the scannable code may be associated with an identification number for the device (e.g., mobile surveillance unit).

[0034] At block 404, a first passcode for the device (e.g., the surveillance unit) may be generated, and method 400 may proceed to block 406. For example, the generated passcode (i.e., a valid pin / passcode) may be included with information (e.g., documentation) that may include a specific identification number (e.g., for the device). In various embodiments, the information (e.g., transportation documentation) may be8 Docket No. 54541-00053provided to a user (e.g., a transportation, field or service partner or other personnel or administrators with a need to open one or more locks on the device).

[0035] At block 406, the scannable code may be displayed on the device, and method 400 may proceed to block 408. For example, the scannable code, which may include a bar code or a QR code may be displayed on (e.g., affixed to) the device such that a user may scan the scannable code via a mobile device.

[0036] At block 408, in response to the scannable code being scanned, a website or other portal may be opened (e.g., on a user device (i.e., of the user), and method 400 may proceed to block 412. For example, a technician may scan the scannable code (e.g., via a user device) on the device, and in response thereto, the website may open on the user device.

[0037] At block 410, a second passcode may be received, and method 400 may proceed to block 412. For example, the user may enter the second passcode (e.g., via the portal and / or website) and press (select) “enter” to cause the passcode to be submitted and received.

[0038] At block 412, upon the second passcode matching the first passcode, one or more electronic locks on the device may be unlocked. More specifically, for example, upon receipt of the passcode, the passcode may be authorized (e.g., via comparing the second passcode to the first (“valid”) passcode (e.g., passcode generated in block 404). Further, in response to authorization of the entered passcode (i.e., upon receipt of an authorized passcode), the one or more electronic locks may be unlocked (e.g., via one or more APIs (e.g., API 364 and / or API 366 of FIG. 3C)). It is noted that, in some examples, after a passcode is received (e.g., at block 410), the received passcode may be validated via a database lookup. For example, after the passcode is received, a database may be accessed to determine if the passcode is correct (e.g., the passcode exists in the database), that an expiration date has not passed (e.g., the passcode is still valid), and / or that access has not been revoked (e.g., access associated with the passcode and / or one or more associated locks has not been revoked).

[0039] Modifications, additions, or omissions may be made to method 400 without departing from the scope of the present disclosure. For example, the operations of method 400 may be implemented in differing order. Furthermore, the outlined operations and actions are only provided as examples, and some of the operations and actions may be optional, combined into fewer operations and actions, or expanded into additional operations and actions without detracting from the essence of the disclosed embodiment.9 Docket No. 54541-00053

[0040] Although embodiments described herein utilize a code (e.g., QR code), it is noted that any technology that confirms presence on-site, like a QR code, an NFC device, an RF tag, and / or other communication methods (e.g., RF communication) may be used for carrying out embodiments of the disclosure. One or more of these technologies may verify that a person is close to a designated unit and / or provide detailed, unique information for automating access. Options such as a web portal or temporary passcodes, which may enhance security, may or may not be used to complement one or more other technologies.

[0041] FIG. 5 depicts a system 500, in accordance with various embodiments of the disclosure. System 500 includes one or more mobile units 502, a server 504, and one or more devices 506. In one non-limiting example, each mobile unit 502 includes mobile unit 100 (see FIG. 1), server 504 may include a cloud server or any other server, and device(s) 506 may include an electronic device, such as a front-end device (e.g., a user device (e.g., mobile phone, tablet, etc.), a desktop computer, or any other suitable electronic device (e.g., including a display)). According to various embodiments, each of server 504 and device(s) 506 may be remote from mobile unit 502. Further, for example, server 504 may include a cloud-based processor.

[0042] According to various embodiments of the disclosure, each mobile unit 502, which may include a modem, may be within a first location (a “camera location” or a “remote location”), and server 504 may be within a second location, remote from the camera location. In addition, in at least some examples, electronic device 506 may be remote from the camera location and / or server 504. As will be appreciated by a person having ordinary skill in the art, system 500 may be modular, expandable, and / or scalable. It is noted that according to various embodiments, various devices of system 500 may be configured to communicate via one or more metered connections (e.g., cellular, satellite, etc.).

[0043] For example, one or more of mobile units 502 may include one or more electronic locks, which may be controlled via one or more embodiments disclosed herein. More specifically, for example, device 506 (e.g., a mobile device) may be used to scan a scannable code displayed on mobile unit 502, and a passcode may be entered via device 506. Further, in some embodiments, server 504 may include API 364 (see FIG. 3C) and / or mobile unit 502 may include API 366 (see FIG. 3).

[0044] FIG. 6 illustrates a system 600 that may be used to implement embodiments of the disclosure. System 600 may include a computer 602 that comprises a 10 Docket No. 54541-00053processor 604 and memory 606. For example only, and not by way of limitation, computer 602 may include a workstation, a laptop, or a hand-held device such as a cell phone or a personal digital assistant (PDA), a server (e.g., server 504), a computer of unit 100 (see FIG. 1), or any other processor-based device known in the art. In one embodiment, computer 602 may be operably coupled to a display (not shown in FIG. 6), which presents images to the user via a GUI. As will be appreciated, computer 602 may include one or controllers including one or more operating systems, which may be configured and / or updated in accordance with various embodiments disclosed herein.

[0045] Generally, computer 602 may operate under control of an operating system 608 stored in memory 606, and interface with a user to accept inputs and commands and to present outputs through a GUI module 610. Although GUI module 610 is depicted as a separate module, the instructions performing the GUI functions may be resident or distributed in the operating system 608, a program 612, or implemented with special purpose memory and processors. Computer 602 may also implement a compiler 614 that allows a program (e.g., code) 612 written in a programming language to be translated into processor 604 readable code. After completion, program 612 may access and manipulate data stored in memory 608 of computer 602 using the relationships and logic that are generated using compiler 614.

[0046] Further, operating system 608 and program 612 may include instructions that, when read and executed by computer 602, may cause computer 602 to perform the steps necessary to implement and / or use various embodiments of the disclosure. Program 612 and / or operating instructions may also be tangibly embodied in memory 606 and / or data communications devices, thereby making a computer program product or article of manufacture according to an embodiment of the present disclosure. As such, the term “program” as used herein is intended to encompass a computer program accessible from any computer readable device or media. Program 612 may exist on an electronic device (e.g., device 310 and / or device 506; see FIGS. 3B and 5), a server (e.g., server 504; see FIG. 5), a mobile unit (e.g., mobile unit 100 of FIG. 1 and / or mobile unit 502 of FIG. 5), and / or another device. Furthermore, portions of program 612 may be distributed such that some of program 612 may be included on a computer readable media within an electronic device (e.g., device 310 and / or device 506), some of program 612 may be included on a computer readable media on a server (e.g., server 504), some of program 612 may be included on a computer readable media on a surveillance unit (e.g., mobile unit 100 and / or mobile unit 502), and / or some of program 612 may be included on a computer 11 Docket No. 54541-00053readable media on another device. In some embodiments, program 612 may be configured to run on an electronic device, a server, a unit, another computing device, or any combination thereof. As a specific example, program 612 may exist on server 504 and / or unit 100 / 502 and may be accessible to a user via device 310 and / or device 506; see FIGS. 3B and 5.

[0047] In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. The illustrations presented in the disclosure are not meant to be actual views of any particular apparatus (e.g., circuit, device, system, etc.) or method, but are merely idealized representations that are employed to describe various embodiments of the disclosure. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may be simplified for clarity. Thus, the drawings may not depict all of the components of a given apparatus (e.g., circuit, device, or system) or all operations of a particular method.

[0048] Terms used herein and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including, but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes, but is not limited to,” etc.).

[0049] Additionally, if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. As used herein, “and / or” includes any and all combinations of one or more of the associated listed items.

[0050] In addition, even if a specific number of an introduced claim recitation is explicitly recited, it is understood that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other 12 Docket No. 54541-00053modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” or “one or more of A, B, and C, etc.” is used, in general such a construction is intended to include A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together, etc. For example, the use of the term “and / or” is intended to be construed in this manner.

[0051] Further, any disjunctive word or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” should be understood to include the possibilities of “A” or “B” or “A and B.”

[0052] As used herein, the term “substantially” in reference to a given parameter, property, or condition means and includes to a degree that one of ordinary skill in the art would understand that the given parameter, property, or condition is met with a degree of variance, such as within acceptable tolerances. By way of example, depending on the particular parameter, property, or condition that is substantially met, the parameter, property, or condition may be at least 90.0 percent met, at least 95.0 percent met, at least 99.0 percent met, at least 99.9 percent met, or even 100.0 percent met.

[0053] As used herein, the term “approximately” or the term “about,” when used in reference to a numerical value for a particular parameter, is inclusive of the numerical value and a degree of variance from the numerical value that one of ordinary skill in the art would understand is within acceptable tolerances for the particular parameter. For example, “about,” in reference to a numerical value, may include additional numerical values within a range of from 90.0 percent to 110.0 percent of the numerical value, such as within a range of from 95.0 percent to 105.0 percent of the numerical value, within a range of from 97.5 percent to 102.5 percent of the numerical value, within a range of from 99.0 percent to 101.0 percent of the numerical value, within a range of from 99.5 percent to 100.5 percent of the numerical value, or within a range of from 99.9 percent to 100.1 percent of the numerical value.

[0054] Additionally, the use of the terms “first,” “second,” “third,” etc., are not necessarily used herein to connote a specific order or number of elements. Generally, the terms “first,” “second,” “third,” etc., are used to distinguish between different elements as generic identifiers. Absence a showing that the terms “first,” “second,” “third,” etc., connote a specific order, these terms should not be understood to connote a specific order.13 Docket No. 54541-00053Furthermore, absence a showing that the terms “first,” “second,” “third,” etc., connote a specific number of elements, these terms should not be understood to connote a specific number of elements.

[0055] The embodiments of the disclosure described above and illustrated in the accompanying drawings do not limit the scope of the disclosure, which is encompassed by the scope of the appended claims and their legal equivalents. Any equivalent embodiments are within the scope of this disclosure. Indeed, various modifications of the disclosure, in addition to those shown and described herein, such as alternative useful combinations of the elements described, will become apparent to those skilled in the art from the description. Such modifications and embodiments also fall within the scope of the appended claims and equivalents.14 Docket No. 54541-00053

Claims

CLAIMSWhat is claimed:

1. A system including a surveillance unit, comprising:a surveillance unit comprising at least one electronic locking device;an application program to:receive, from a user device, a request to load a portal on the user device; provide, via the portal, a field for receiving an entered passcode associated with the surveillance unit;receive the entered passcode;verify the entered passcode; andcause the at least one electronic locking device to unlock responsive to verification of the entered passcode.

2. The system of claim 1, further comprising a server communicatively coupled to the surveillance unit and including at a portion of the application program stored thereon.

3. The system of claim 1, wherein the surveillance unit includes a scannable code, wherein the request to load the portal is responsive to a scan of the scannable code via the user device.

4. The system of claim 1, wherein the application program is further to: generate a passcode; andcompare the generated passcode to the entered passcode to verify the entered passcode.

5. The system of claim 1, further comprising a number of application programming interfaces (APIs) to cause the at least one electronic locking device to unlock responsive to verification of the entered passcode.

6. The system of claim 5, wherein the number of APIs includes a first cloud API and a second, edge API.15 Docket No. 54541-000537. The system of claim 1, further comprising a database for storing information related to at least one of the user device, a time that the entered passcode was received, a location of the surveillance unit, the entered passcode, or a time that the at least one electronic device was unlocked.

8. A method, comprising:generating a scannable code associated with a device including an electronic lock; generating an authorized passcode associated with the device;displaying the scannable code on the device;launching a portal responsive to a request from a user device, the portal including a field forreceiving an entered passcode;receiving the entered passcode via the field;comparing the entered passcode to the authorized passcode to validate the entered passcode;unlocking the electronic lock responsive to validation of the entered passcode.

9. The method of claim 8, wherein the scannable code comprises a QR code, wherein the request from the user device is responsive to the QR code being scanned by the user device.

10. The method of claim 8, wherein unlocking the electronic lock comprises unlocking the electronic lock via at least one application programming interface (API).

11. The method of claim 8, further comprising storing information related to at least one of the user device, a time that the entered passcode was received, a location of the device, the entered passcode, or a time that the electronic device was unlocked.

12. A non-transitory computer-readable media having computer instructions stored thereon that, in response to being executed, cause operations comprising:launching a website responsive to a request from a user device, the website including afield for receiving a passcode associated with a device including an electronic16 Docket No. 54541-00053lock;receiving the passcode;validating the received passcode; andunlocking the electronic lock responsive to validation of the passcode.

13. The non-transitory computer-readable media of claim 12, the operations further comprising:generating a scannable code associated with device; andgenerating an authorized passcode associated with the device.

14. The non-transitory computer-readable media of claim 13, wherein validating the received passcode comprises validating the received passcode responsive to the received passcode matching the authorized passcode.

15. The non-transitory computer-readable media of claim 13, wherein the scannable code is affixed to the device, and the request from the user device is responsive to the scannable code being scanned by a camera of the user device.

16. The non-transitory computer-readable media of claim 12, the operations further comprising receiving the request from the user device.

17. A system, comprising:a device comprising at least one electronic locking device;an application program to:receive, from a user device, a request to load a portal on the user device; provide, via the portal, a field for receiving a passcode associated with the mobile surveillance unit;receive the passcode;compare the passcode to an authorized passcode; andcause the at least one electronic locking device to unlock responsive to the passcode matching the authorized passcode.17 Docket No. 54541-0005318. The system of claim 17, wherein the application program includes at least one application programming interface (API) to cause the at least one electronic locking device to unlock.

19. The system of claim 17, wherein the device comprises a code, wherein the request is received responsive to the user device scanning the code.

20. The system of claim 17, further comprising a database for storing information related to the user device, a time that the passcode was received, a location of the device, or a time that the at least one electronic locking device was unlocked.18 Docket No. 54541-00053

Images