Access control, and associated systems, devices, mobile units, and methods
Mobile surveillance units with automated access control systems address the inefficiencies of human-dependent systems by using digital security methods to manage access control, improving efficiency and reducing costs while ensuring reliable and scalable operations.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- LIVEVIEW TECHNOLOGIES LLC
- Filing Date
- 2025-08-08
- Publication Date
- 2026-06-25
AI Technical Summary
Current access control systems for secured properties rely heavily on human personnel, which are economically inefficient and costly, especially for large or round-the-clock operations, and lack scalability and consistency.
Implementing mobile surveillance units equipped with automated access control systems, including lift gates and interface devices, that utilize digital security systems such as license plate recognition and biometric verification to manage access without human presence, integrating with centralized access logs and enabling remote control via Bluetooth or web applications.
Reduces reliance on human security guards, enhances operational efficiency, lowers costs, and provides reliable, scalable access control by automating identity verification and gate operations.
Smart Images

Figure US2025041353_25062026_PF_FP_ABST
Abstract
Description
[0001] ACCESS CONTROL, AND ASSOCIATED SYSTEMS, DEVICES, MOBILE UNITS, AND METHODS
[0002] PRIORITY CLAIM
[0003] This application claims the benefit of the filing date of United States Provisional Patent Application Serial No. 63 / 734,960, filed December 17, 2024, for "ACCESS CONTROL, AND ASSOCIATED SYSTEMS, DEVICES, MOBILE UNITS, AND METHODS,” the disclosures of each of which are hereby incorporated herein in their entirety by this reference.
[0004] TECHNICAL FIELD
[0005] This disclosure relates generally to access control and, more specifically, to mobile units including lift gates and / or interface devices, and to related units, devices, systems, and methods.
[0006] BACKGROUND
[0007] Mobile units, such as mobile surveillance units, which may include a number of input devices (e.g.. cameras and / or sensors) and / or a number of output devices (e.g., lights, speakers, and / or displays), may be positioned in a remote environment for providing surveillance and / or security in and / or around the remote environment.
[0008] BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIG. 1 depicts an example system including a mobile unit, in accordance with one or more embodiments of the disclosure.
[0010] FIGS. 2A-2C illustrate examples of a mobile unit, in accordance with various embodiments of the disclosure.
[0011] FIGS. 3-8 depict various embodiments of an example gate system of a mobile unit, in accordance with various embodiments of the disclosure.
[0012] FIG. 9 depicts a mobile unit including an example interface device in a deployed configuration, according to various embodiments of the disclosure.
[0013] FIG. 10 depicts a mobile unit including an example interface device in a retracted and secure configuration, according to various embodiments of the disclosure.
[0014] FIGS. 11 and 12 are additional illustrations of a mobile unit including an interface device and a lift gate system, according to various embodiments of the disclosure. FIG. 13 depicts a mobile unit including another example of an interface device, in accordance with various embodiments of the disclosure.
[0015] FIG. 14 depicts an example mobile unit including a gate system and an interface device including an interface positioned proximately to a vehicle, according to various embodiments of the disclosure.
[0016] FIGS. 15-19 depict various user interfaces related to a gate system utilized with a mobile unit, according to various embodiments of the disclosure.
[0017] FIG. 20 illustrates a mobile unit including an example gate system, according to various embodiments of the disclosure.
[0018] FIG. 21 depicts example components of a gate system, in accordance with various embodiments of the disclosure.
[0019] FIGS. 22-24 illustrate a mobile unit including an arm of a gate system, according to various embodiments of the disclosure.
[0020] FIG. 25 depicts an arm of a gate system in both a deployed state and in a transport and / or storage state.
[0021] FIG. 26 depicts an arm of a gate system in a transport and / or storage state, according to various embodiments of the disclosure.
[0022] FIG. 27 depicts an arm of a gate system in a deployed state, according to various embodiments of the disclosure.
[0023] FIG. 28 depicts a cut-out of a telescoping arm including a base plate and a number of sections configured for telescoping functionality, in accordance with various embodiments of the disclosure.
[0024] FIG. 29 is another illustration of a telescoping arm, according to various embodiments of the disclosure.
[0025] FIG. 30 is a side view of a telescoping arm including a base plate and a number of sections, according to various embodiments of the disclosure.
[0026] FIG. 31 further depicts a number of parts of a telescoping arm, in accordance with various embodiments of the disclosure.
[0027] FIG. 32 depicts an example joint of an interface device, according to various embodiments of the disclosure.
[0028] FIG. 33 depicts an example system including a mobile unit, in accordance with various embodiments of the disclosure. FIG. 34 depicts an example system including a mobile unit, a serv er, and one or more devices, in accordance with various embodiments of the disclosure.
[0029] FIG. 35 illustrates another example system, according to one or more embodiments of the disclosure.
[0030] MODE(S) FOR CARRYING OUT THE INVENTION
[0031] Referring in general to the accompanying drawings, various embodiments of the present disclosure are illustrated to show example embodiments related to access control, and more specifically to mobile units including access lift gates, associated interface devices, or both. 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.
[0032] 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 in order not to obscure the present disclosure in unnecessary detail. Additionally, block definitions and partitioning of logic betw een various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary7skill 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.
[0033] Controlling access to secured properties, such construction zones, storage yards, commercial facilities, industrial zones, access roads, parking lots, etc., often requires human security' personnel or on-site operators. These individuals are responsible for verifying identities, authorizing access, and physically opening or closing gates or barriers.
[0034] While this approach provides a human judgment element in access control, it suffers from several significant disadvantages. As an example, employing human personnel entails substantial ongoing costs, which scale with the number of access points and the hours of required coverage, making it economically inefficient, particularly for large or round-the-clock operations. Various embodiments may provide for security, surveillance, and / or access control. In at least some example scenarios, various embodiments may enable for security, surveillance, and / or access control to be performed within an environment (e.g., a storage yard, distribution facility, a parking lot, or an access road) without a human (e.g., security guard or other personnel) being present in the environment.
[0035] Various embodiments may reduce or eliminate reliance on human security guards or gate operators, and thus various embodiments may improve operational efficiency, reduce costs, enhance security, and provide reliable, consistent, and scalable access control capabilities. Various embodiments may be configured to be integrated with digital security systems, such as license plate recognition, biometric verification, or centralized access logs.
[0036] As will be appreciated, various embodiments of the disclosure, as described more fully herein, provide a technical solution to one or more problems that arise from technology that could not reasonably be performed by a person, and various embodiments disclosed herein are rooted in computer technology in order to overcome the problems and / or challenges described below. Further, at least some embodiments disclosed herein may improve computer-related technology by allowing computer performance of a function not previously performable by a computer.
[0037] 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.). Further, units for use indoors and / or outdoors are within the scope of the disclosure. Embodiments of the disclosure will now be explained with reference to the accompanying drawings.
[0038] FIG. 1 illustrates an example system 100, according to one or more embodiments of the disclosure. System 100, which may include a security' and / or surveillance system, includes a unit 102, which may also be referred to herein as a “mobile unit.” a “mobile security unit.” a “mobile surveillance unit,” a “physical unit,” or some variation thereof. According to various embodiments, unit 102 may include one or more input devices (e.g.. interfaces, electronic readers, cameras, weather sensors, motion sensors, noise sensors, chemical sensors, without limitation) 104 and one or more output devices 106 (e.g., lights (e.g., pan / tilt spotlight), speakers, interfaces, electronic displays, without limitation). For example only, input devices 104 may include one or more cameras, such as thermal cameras, infrared cameras, optical cameras, PTZ cameras, bi-spectrum cameras, any other camera, or any combination thereof. Further, for example only, output devices 106 may include one or more lights (e.g., flood lights, strobe lights (e g., LED strobe lights), and / or other lights), one or more speakers (e.g., loud speaker, two-way public address (PA) speaker, and / or other speaker), any other suitable output device (e.g., a digital display), or any combination thereof.
[0039] In some embodiments, unit 102 may also include one or more storage devices 108. Storage device 108, which may include any suitable storage device (e.g., a memory card, hard drive, a digital video recorder (DVR) / network video recorder (NVR), internal flash media, a network attached storage device, or any other suitable electronic storage device), may be configured for receiving and storing data (e.g., video, images, and / or i-frames) captured by input devices 104. In some embodiments, during operation of unit 102, storage device 108 may continuously record data (e.g., video, images, i-frames, and / or other data) captured by one or more input devices 104 (e.g., cameras, lidar, radar, environmental sensors, acoustic sensors, without limitation) of unit 102 (e.g., 24 hours a day, 7 days a week, or any other time scenario).
[0040] Unit 102 may further include a computer 110, which may include memory and / or any suitable processor, controller, logic, and / or other processor-based device known in the art. Moreover, although not shown in FIG. 1, unit 102 may include one or more additional devices including, but not limited to, one or more microphones, one or more solar panels, one or more power generators (e.g., fuel cell generators), or any combination thereof. Unit 102 may also include a communication device (e.g., a modem (e.g., a cellular modem, a satellite modem, a Wi-Fi modem, etc.)) 112 that may comprise any suitable and known communication device, which may be coupled to input devices 104, output devices 106, storage device 108, and / or computer 110 via wired connections, wireless connections, or a combination thereof. In some embodiments, communication device 112 may include one or more radios and / or one or more antennas. System 100 may further include one or more electronic devices 113, which may comprise, for example only, a mobile device (e.g., mobile phone, tablet, laptop, etc.), a desktop computer, or any other suitable electronic device including a display. Electronic device 113 may be accessible to one or more end-users. Additionally, system 100 may include a server 116 (e.g., a cloud server), which may be remote from unit 102. Communication device 112, electronic devices 113. and server 116 may be coupled to one another via the Internet 114. For example, unit 102. electronic devices 113. and server 116 may be coupled to one another via one or more metered connections (e.g., cellular and / or satellite connections).
[0041] According to various embodiments of the disclosure, unit 102 may be within a first location (a “remote location / ’ “camera location” or a “unit location”), and server 116 may be within a second location, remote from the first location. In addition, each electronic device 113 may or may not be remote from unit 102 and / or server 116. As will be appreciated by a person having ordinary skill in the art, system 100 may be modular, expandable, and / or scalable.
[0042] As noted above, in some embodiments, unit 102 may include a mobile unit (e.g., a mobile security / surveillance unit). In these and other embodiments, unit 102 may include a portable trailer (not shown in FIG. 1), a storage box (e.g., including one or more batteries and / or a power generator) (not shown in FIG. 1), and a mast (not shown in FIG. 1) coupled to a head unit (e.g., including, for example, one or more cameras, one or more lights, one or more speakers, and / or one or more microphones) (not shown in FIG. 1 ). According to various examples, in addition to input devices (e.g., input devices 104) and output devices (e.g., output devices 106), a head unit of unit 102 may include and / or may be coupled to storage device 108, computer 110. and / or communication device 112.
[0043] Non-limiting examples of unit 102 are show n in FIGS. 2A-2C. More specifically, FIG. 2A illustrates a mobile unit 202 including a trailer, a storage box, a mast, and a head unit; FIG. 2B illustrates a head unit 210 (i.e., of a mobile unit) including a number of lights, a number of cameras, and a speaker: and FIG. 2C is another depiction of a head unit 220 (i.e., of a mobile unit) including a number of lights, a number of cameras, and a speaker. As an example, a mobile unit may be configured to be positioned in an environment (e.g., a parking lot, a roadside location, a storage yard, a construction zone, a concert venue, a sporting venue, a school campus, a property entrance, or another environment, without limitation). According to various embodiments, a mobile unit (e.g., unit 102) may include an access control system including a lift gate (also referred herein as an “access lift gate." “access control gate,’’ “access gate,” a “barrier lift gate,” a “barrier gate,” or some variation thereof), which may be coupled to and powered by the mobile unit. Thus, in these examples, a system (including one or more mobile units) may provide one or more mobile barrier gates for remote access control. As a non-limiting example, a lift gate may include LIFTMASTER® MAT barrier gate.
[0044] For example, FIGS. 3-8 illustrate examples of a mobile unit 300 including an example lift gate having a gate (also referred to herein as an “arm”) 302 and a device (e.g., a box) 304 (e.g., operator box including a motor, control device, and other associated devices), which may be attached to mobile unit 300. As will be appreciated, a device (e.g., device 304) may be attached to a mobile unit in any suitable manner. For example, arm 302 may be coupled to device 304, which is coupled to (e.g., secured to) mobile unit 300. More specifically, device 304 may be coupled to a storage box of mobile unit 300. As will be appreciated, arm 302 may rotate about device 304 (e.g., from a closed position (e.g., extending substantially horizontally) to an open position (e.g., extending substantially vertically), and vice versa).
[0045] According to various embodiments, a lift gate and / or any associated devices may be controlled via any suitable manner, such as via a remote (e.g., RF remote), BLUETOOTH® (e.g.. BLUETOOTH® Low Energy (BLE) controller / app), and / or a custom web application (e.g., running through a mobile unit (e.g., cellular / edge)) (e g., to trigger from anywhere in the world). In some embodiments, an associated mobile unit, and more specifically, a processing unit of mobile unit may control an associated lift gate and / or any associated devices.
[0046] In one specific example, as a vehicle approaches a mobile unit (e.g., mobile unit 300), the mobile unit (e.g., via one or more cameras or other sensors of the mobile unit, such as one or more input devices 104 of FIG. 1) may detect and / or read a license plate or other identifier (e.g., DOT number) of the vehicle to determine whether or not the lift gate should be opened (e.g., whether to trigger the gate to grant access to an area, for example). If the vehicle is an authorized vehicle (e.g., scheduled, preapproved, approved on the spot), the lift gate may open. Otherwise, the lift gate may remain in a closed position.
[0047] FIGS. 6 and 8 depict an example user interface 600 showing a detected license plate 602 and a vehicle ID 604 (i.e., of a vehicle approaching or near mobile unit 300). Further, in some embodiments, access events may be logged (e.g., automated logging) (e.g.. with contextual information) (e.g.. and stored locally, stored at a server (e.g., cloud server, such as server 116 of FIG. 1)), sent to a user device (e.g., mobile phone) (e.g., device 113 of FIG. 1). For example, a system (i.e., including one or more mobile units) may audit and / or manage a fleet of vehicles based on timestamps (e.g., based on vehicles entering and / or leaving an area).
[0048] Other embodiments relate to an interface device, which may be used for driver and / or vehicle identification. In some embodiments, the interface device may include an integrated articulating arm that can be used to mount a variety of user authorization / identification devices (also referred to herein as “interface’') (e g., electronic reader (e.g., badge reader), intercom, keypad, without limitation) to a mobile unit.
[0049] According to various embodiments, the interface device may be configured in a number of states. For example, the interface device may be configured in a deployed state (e.g., unfolded and / or ready for use). In the deployed state, an interface (e.g., reader, intercom, keypad, digital display, etc.) of the interface device may be in an accessible location from a vehicle driver's window to allow efficient interaction without the driver exiting the vehicle, and with sufficient space between the interface and an arm (e.g., arm 302) to accommodate most cars and commercial vehicles. According to some embodiments, a height of an interface of the interface device may be adjusted to the height of a typical personal vehicle, a commercial truck, or any other desirable height. In another embodiment, an interface device may include one interface (i.e., fixed or adjustable) at one height (e.g., for cars) and another interface (i.e., fixed or adjustable) at another height (e.g., for trucks).
[0050] Further, the interface device may be configured in a stowed state. In the stowed state, the articulating arm of the interface device may be folded down and the interface device may be secured to a mobile unit (e.g., along the back of the mobile unit) allowing for standard towing and / or transportation of the mobile unit including the interface device.
[0051] FIG. 9 depicts a mobile unit 900 including an interface device 902, in accordance with various embodiments of the disclosure. Interface device 902 includes an interface 904 and an arm 906, which, in some embodiments, may be a modular (e.g., adjustable and / or foldable) arm. In other embodiments, interface device 902 may include a fixed arm.
[0052] For example, arm 906 may include a number of sections, wherein each section may be physically coupled to another section via a joint (e.g., pivot or swivel joint) 907. Arm 906 may be physically atached to a portion of a base of mobile unit 900 (e.g., a trailer of mobile unit 900). In some examples, arm 906 may be supported by one or more legs 908 (e.g., while mobile unit 900 is in a deployed state).
[0053] As a non-limiting example, interface 904 may be configured for audio communication (e.g., two-way audio communication) and / or video communication (e.g., one-way video communication). More specifically, for example, interface 904 may include an intercom (e.g., for audio communication), a camera, a keypad, a reader (e.g., a badge and / or a card reader), and / or an electronic display (e.g., for video and / or digital communication).
[0054] As will be appreciated, arm 906 may be configured such that a position of interface 904 may be adjusted such that a user may easily engage with interface 904 (e.g., while standing, siting in a vehicle, etc.). As will also be appreciated, interface 904, which may be configured to receive power and / or communication (e.g., via POE), may enable for visual and / or audio verification (e.g., driver and / or passenger verification). According to various examples, site personnel and / or a third party (e.g., a remote party) may monitor events via an associated mobile unit (e.g., via interface 904, an input device (e.g., camera and / or other sensor) of unit 900) and / or may engage with a driver, for example, via interface 904.
[0055] It is noted that FIG. 9 depicts interface device 902 in a deployed position and FIG. 10 depicts interface device 902 in a retracted (e.g.. secure) position (e.g., for transport). FIGS. 1 1 and 12 are additional illustrations of mobile unit 900 including trailer 901, interface device 902, interface 904, a lift gate arm 903, and a lift gate box 905. It is noted, however, that FIGS. 9 and 12 do not include a lift gate arm.
[0056] FIG. 13 depicts a mobile unit 1300 including another example of an interface device 1302 including an interface 1304, an arm 1306, and a leg 1308. In some embodiments, arm 1306 may include a fixed arm. FIG. 14 is another illustration of a mobile unit 1400 including an interface device 1402, an interface 1404, and an interface arm 1406. Mobile unit 1400 further includes a lift gate arm 1403 and a lift gate box 1405. As shown in FIG. 14, interface 1404 is positioned near a driver's side window of a vehicle (e.g., a truck) 1410. According to various embodiments, lift gate box 1405 may be coupled to mobile unit 1400 (e.g., a storage box of mobile unit 1400), and lift gate arm 1403 may be coupled to lift gate box 1405 (e.g., via a mount 2102; see FIG. 21). As will be appreciated, vehicle 1410 may pull up near interface device 1402 such that a driver of the vehicle may interact with interface 1404. Further, based on some verification or other action, for example, gate arm 1403 may rise, allowing vehicle 1410 to pass. Further, images and / or video of the event may be captured via one or more cameras of mobile unit 1400. Data associated with event may be logged and / or provided to personnel.
[0057] As will be appreciated, control and / or scheduling associated with an access gate may be automated. In some embodiments, during one time period (e.g., between 9 AM- 5PM), a gate may be programmed to be in an open state, and in another time period (e.g., between 5PM-9AM), the gate may be programmed to be in a closed state.
[0058] Other embodiments of the disclosure include systems and / or programs
[0059] (e.g., application programs) for scheduling events (e.g., for when gate 302 / 903 / 1403 should raise or lower, what times gate 302 / 903 / 1403 should be in a raised (i.e., open position) or lowered (i.e., closed) position), controlling gate 302 / 903 / 1403 (e.g., manually raising or lowering gate 302 / 903 / 1403) (e.g., via a mobile app, web app, remote device, or other device), integrating with other systems (e.g., command / control center, management system), and providing automated logging of events (when arm 302 / 903 / 1403 was opened, what passed through an area (e.g., via license plate reader, or other vehicle identification)).
[0060] It some embodiments, a system (e.g., an access control system of the mobile unit) may be configured to detect vehicle identifications (e.g., license plates via LPR, or other vehicle identification (e.g., numbers, bar codes, and / or other identification)). An access control system may provide access (e.g., raise an arm of a gate) based on some verification (e.g., based on vehicle identification or user (e.g., driver or passenger) identification).
[0061] As will be appreciated, an access control system (i.e., including a lift gate) may work in conjunction with other components of a mobile unit (e.g., a controller, an interface, camera, sensors, LPR device, lights, speakers, without limitation). Further, according to various embodiments, an access control system (e.g., of a mobile unit) may be configured to integrate with other access control systems, such as those developed and / or sold by, for example, Lenel, Honeywell, and others.
[0062] FIG. 15 depicts an example user interface 1500, in accordance with various embodiments of the disclosure. User interface 1500 includes data related to an access point, a state of an access lift gate, a video player interface, a button for controlling the access lift gate, and various associated images and / or camera views. FIG. 16 depicts an example user interface 1600 for a mobile application, in accordance with various embodiments of the disclosure. User interface 1600 includes various associated camera views (e.g., including live stream video data).
[0063] FIG. 17 depicts an example user interface 1700 depicting an activity log 1702 associated with an access control system including an access lift gate. Activity log 1702 may further include image data, timing data (e.g., associated with images and / or actions), status data, and / or action data (e.g., current state of one or more lift gates, past operations of the lift gates, etc.). Activity log 1702 may further include event data, data regarding, for example, a user and / or a system (e.g., property, customer, location, without limitation).
[0064] FIG. 18 depicts another example user interface 1800 showing example alert data 1802 associated with an access control system including an access lift gate. Alert data 1802 may include alert data, image data, timing data (e.g., associated with images, incidents, and / or actions), status data, and / or action data (e.g., incoming call, person detected, etc.). User interface 1800 may also include selectable components (e.g., buttons) for performing an action, such as responding to a call, viewing an incident, without limitation. User interface 1800 may further include event / incident data, priority indicators, without limitation.
[0065] FIG. 19 depicts yet another example interface 1900 including camera view options, video player, and other data and / or options associated with an access lift gate system (e.g., of a mobile unit).
[0066] FIG. 20 includes another illustration of a mobile unit 2000 including an access lift gate system 2001 including a box 2002, which may include various components, such as a mount (e.g., for coupling to a mobile unit), a motor, a control device, a gear box, and / or other associated devices. According to various embodiments, box 2002 may be coupled to a storage box 2003 of mobile unit 2000. Access lift gate system 2001 further includes an arm 2004, which is attached to box 2002.
[0067] FIG. 21 illustrates example components of an access gate system 2100 including a mount 2102 (e.g., for receiving a gate arm (e.g., arm 2004; see FIG. 20)) and other associated components, such as, a gear box, a motor, and / or a control board..
[0068] According to various embodiments, a lift gate arm (e.g., arm 2004; see FIG. 20) may include a telescoping arm. For example, a length of the gate arm may be increased or decreased (e.g., remotely or otherwise) based on the environment and / or requirements. FIGS. 22-24 illustrate a mobile unit 2200 including an arm 2204 of an access control system. According to various embodiments, arm 2204 may include a telescoping arm.
[0069] According to some embodiments, during transport and / or storage of a mobile unit, an arm (e.g., a telescoping arm) may be positioned in a transport location wherein the arm is securely attached to a mobile unit (e.g., in a vertical orientation). Further, in a deployed state, the arm may be coupled to a lift gate box (e.g., via a mount, such as mount 2102), such that the arm may be used (e.g., raised and lowered as needed). FIGS. 24 and 25 depict arm 2204A in a deployed state, and arm 2204B in a transport and / or storage state. FIG. 26 depicts arm 2204B in a transport and / or storage state, and FIG. 27 depicts arm 2204A in a deployed state.
[0070] FIG. 28 depicts a cut-out of at least a portion of a telescoping arm 2804 (e.g., arm 2204) including a base plate 2805 and a number of sections 2810 configured for telescoping functionality. FIG. 29 is another illustration of telescoping arm 2804. FIG. 30 is a front (e.g., elevation) view of telescoping arm 2804 including base plate 2805 and sections 2810. As shown in at least FIGS. 28 and 30, sections 2810 may be sized such that one section may fit at least within another section (i.e., for telescoping functionality). FIG. 31 further depicts various parts of telescoping arm 2804.
[0071] As noted above and as shown in at least FIGS. 9-12, an arm (e.g., arm 906) of an interface device (e.g., interface device 902) may include a number of sections, wherein at least some sections of the number of sections may be physically coupled to another section via a pivot mechanism (e.g., pivot or swivel joint) 907. According to various embodiments, a joint, which may be a loadbearing joint, may be configured such that a wire, cord, and / or cable may pass therethrough while allowing an associated arm (e.g., arm 906) and interface (e.g., interface 904) to be adequately positioned and locked into place.
[0072] FIG. 32 depicts an example joint 3200 coupled to arm 3202 of an interface device (e.g., interface device 902 of FIG. 9), according to various embodiments of the disclosure. For example, joint 907 of FIG. 9 may include joint 3200. Joint 3200 may allow for a cable, cord, wire, etc., to extend from an interior of one portion 3204 of arm 3202 to an interior of another portion 3206 or arm 3202 (i.e., via a hole 3208). As will be appreciated, a wiring / cord / cable may be protected (i.e., within arm 3202 and joint 3200) from tampering, and thus joint 3200 may be a tamper resistant assembly. Further, joint 3200 may be configured to enable each portion of arm 3202 to be adjusted (i.e., independently) and locked into a desired positions (i.e., independently) (e.g., via a pull pin 3210 (e.g., including a spring) being positioned in a hole and locking one or more arms 3202 into position).
[0073] FIG. 33 depicts another example system 3300 including a unit 3302, in accordance with various embodiments of the disclosure. Unit 3302, which may also be referred to herein as a “mobile unit,” a “mobile security unit,” a “live unit,” or a “physical unit,” 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 3302 may include one or more sensors 3304 (e.g., cameras, weather sensors, motion sensors, noise sensors, without limitation) and one or more output devices 3306 (e.g., lights, speakers, electronic displays, without limitation). Unit 3302 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 3302. According to some embodiments, unit 3302 may include or may be part of at least a portion of system 100 of FIG. 1 or another system.
[0074] In some embodiments, unit 3302 may include a mobile security unit. In these and other embodiments, unit 3302 may include a portable trailer 3308, a storage box 3310, and a mast 3312 coupled to a head unit 3314, which may include, for example, one or more batteries, one or more cameras, one or more lights, one or more speakers, and / or one or more microphones. According to some embodiments, a first end of mast 3312 may be proximate storage box 3310, and a second, opposite end of mast 3312 may be proximate, and possibly adjacent, head unit 3314. More specifically, in some embodiments, head unit 3314 may be coupled to mast 3312 at an end opposite an end of mast 3312 proximate storage box 3310.
[0075] In some examples, unit 3302 may include one or more primary batteries (e.g., within storage box 3310) and one or more secondary batteries (e.g., within head unit 3314). In these embodiments, a primary battery positioned in storage box 3310 may be coupled to one or more loads and / or a secondary battery positioned within head unit 3314 via, for example, a cord reel (e.g., configured for Ethernet and / or power).
[0076] In some embodiments, unit 3302 may also include one or more solar panels 3316, which may provide power to one or more batteries of unit 3302. More specifically, according to some embodiments, one or more solar panels 3316 may provide power to a primary battery within storage box 3310. As noted herein, unit 3302 may also include one or more additional power sources, such as one or more generators (e.g., fuel cell generators), which may be positioned within storage box 3310. According to various embodiments, unit 3302 may include an access gate system and / or an interface device, as described herein. It is noted that although various embodiments disclosed herein show a lift gate box coupled to a storage box of a mobile unit, the disclosure is not so limited, and a lift gate box may be secured to a mobile unit via any suitable manner (e.g., secured to a frame of a trailer of a mobile unit, secured to a mast of a mobile unit, or any other suitable manner)
[0077] FIG. 34 depicts a system 3400, in accordance with various embodiments of the disclosure. System 3400 includes a mobile unit 3402, a server 3404, and one or more devices 3406. In one non-limiting example, mobile unit 3402 includes mobile unit 3302 (see FIG. 33), server 3404 may include a cloud server or any other server, and device(s) 3406 may include an electronic device, such as 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 3404 and device(s) 3406 may be remote from mobile unit 3402.
[0078] According to various embodiments of the present disclosure, mobile unit 3402, which includes a modem (e.g., communication device 112 of FIG. 1), may be within a first location (a “camera location” or a “remote location”), and server 3404 may be within a second location, remote from the camera location. In addition, in at least some examples, electronic device 3406 may be remote from the camera location and / or server 3404. As will be appreciated by a person having ordinary skill in the art, system 3400 is modular, expandable, and scalable.
[0079] FIG. 35 illustrates a system 3500 that may be used to implement embodiments of the disclosure. System 3500 may include a computer 3502 (e.g., computer 110 of FIG. 1) that comprises a processor 3504 and memory 3506. For example only, and not by way of limitation, computer 3502 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 116 / 3404), computer 110 (see FIG. 1), or any other processor-based device known in the art. In one embodiment, computer 3502 may be operably coupled to a display (not shown in FIG. 35), which presents images to the user via a GUI. As will be appreciated, computer 3502 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. Generally, computer 3502 may operate under control of an operating system 3508 stored in memory 3506, and interface with a user to accept inputs and commands and to present outputs through a GUI module 3510. Although GUI module 3510 is depicted as a separate module, the instructions performing the GUI functions may be resident or distributed in the operating system 3508, an application program 3512, or implemented with special purpose memory and processors. Computer 3502 may also implement a compiler 3514 that allows a program 3512 (e.g., code) written in a programming language to be translated into processor 3504 readable code. After completion, program 3512 may access and manipulate data stored in memory 3506 of computer 3502 using the relationships and logic that are generated using compiler 3514.
[0080] Further, operating system 3508 and program 3512 may include instructions that, when read and executed by computer 3502, may cause computer 3502 to perform the steps necessary to implement and / or use various embodiments of the disclosure. Program 3512 and / or operating instructions may also be tangibly embodied in memory 3506 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 “application program” or the term “program” as used herein is intended to encompass a computer program accessible from any computer readable device or media.
[0081] Program 3512 may exist on an electronic device (e.g., electronic device 113; see FIG. 1), a server (e.g., server 116; see FIG. 1), a unit (e.g., unit 102; see FIG. 1), and / or another device. Furthermore, portions of program 3512 may be distributed such that some of program 3512 may be included on a computer readable media within an electronic device (e.g., electronic device 113), some of program 3512 may be included on a computer readable media on a server (e.g., server 116), some of program 3512 may be included on a computer readable media on a unit (e.g., unit 102 / 300 / 900 / 1300 / 1400 / 2000 / 2200 / 3302), and / or some of program 3512 may be included on a computer readable media on another device. For example, with reference to FIG. 1, in some embodiments, program 3512 may be configured to run on electronic device 113, server 116, unit 102, another computing device, or any combination thereof. As a specific example, program 3512 may exist on server 116 and / or unit 102 and may be accessible to a user via electronic device 113.
[0082] Various embodiments may allow for fully self-contained site access control including various features of mobile security units coupled with physical access control of the gate and the interface device (e.g., a user identification device). A mobile unit, including various embodiments, may be readily deployed to any site without any existing infrastructure.
[0083] 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., 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.
[0084] 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.).
[0085] 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.
[0086] 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 modifiers, 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.
[0087] 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.”
[0088] As used herein, the term “approximately” or 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.
[0089] 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 1 10.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.
[0090] 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. Furthermore, absence a showing that the terns “first,” “second,” “third,” etc., connote a specific number of elements, these terms should not be understood to connote a specific number of elements.
[0091] 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.
Claims
CLAIMSWhat is claimed:
1. A mobile surveillance unit comprising: a trailer; a storage box coupled to the trailer; a mast coupled to the trailer; a head unit coupled to the mast and including at least one of an input device or an output device; and an access control system coupled to at least one of the trailer or the storage box and including a controllable access gate.
2. The mobile surveillance unit, further comprising an adjustable interface device coupled to at least one of the trailer or the storage box and including an interface.
3. The mobile surveillance unit of claim 2, wherein the interface includes at least one of an intercom, a scanner, or a keypad.
4. The mobile surveillance unit of claim 1, wherein the controllable access gate includes a telescoping arm.
5. The mobile surveillance unit of claim 2, wherein the head unit includes the input device comprising a camera.
6. A mobile surveillance unit, comprising: a portable trailer; and an access control system coupled to the portable trailer and including a controllable access gate.
7. The mobile surveillance unit of claim 6, wherein the controllable access gate includes an arm.
8. The mobile surveillance unit of claim 6, further comprising an adjustable interface device including an interface for providing at least one of audio communication or video communication.
9. A mobile surveillance unit, comprising: a trailer; a head unit coupled to the trailer and including at least one of an input device or an output device; and an interface device coupled to the trailer and including an interface and an articulating arm coupled to the interface.
10. The mobile surveillance unit of claim 9, wherein the interface includes at least one of an intercom, a reader, a camera, or a keypad.
11. The mobile surveillance unit of claim 9, wherein the interface device includes a number of tamper resistant joints coupled to at least one portion of the articulating arm.
12. The mobile surveillance unit of claim 9, further comprising an access barrier gate attached to the trailer.
13. The mobile surveillance unit of claim 12, wherein the access barrier gate includes a telescoping arm.
14. A method of operating a mobile surveillance unit, the method comprising: positioning an articulating arm of an interface device such that an interface of the interface device is at a desired location; adjusting a length of a telescoping arm of a lift gate device based on one or more environmental factors; and raising or lowering the arm of the lift gate device responsive to an input received via the interface of the interface device.
15. A method of manufacturing a mobile surveillance unit, the method comprising: attaching an interface device including an articulating arm and interface to a trailer of a mobile surveillance unit; and attaching a lift gate system including a box and a lift gate arm to the mobile surveillance unit.
16. The method of claim 15, wherein attaching the lift gate system comprises attaching the box to the trailer and separately attaching the lift gate arm to the trailer.
17. A method of transporting a mobile surveillance unit, the method comprising: securing an interface device including an articulating arm and interface to a trailer of a mobile surveillance unit in a folded configuration; and securing a lift gate arm of a lift gate access device to the mobile surveillance unit.
18. A mobile unit, comprising: a trailer; a mast coupled to the trailer; ahead unit coupled to the mast an including at least one of an input device or an output device; and an access control system coupled to the trailer and including a controllable access gate system including a lift gate arm.
19. The mobile unit of claim 18, the access control system further including a control box coupled to the trailer.
20. The mobile unit of claim 18, further comprising an interface device including an intercom interface and an articulating arm coupled between the trailer and the intercom interface.