Kiosk and/or gate systems may be employed for traffic control. A mobile kiosk may be repositioned and/or relocated without new construction to adapt traffic control to changing situations, such as changes in facility layout (e.g., in intermodal container handling facilities or distribution centers), changes in projected traffic flows, changes in flows of equipment and traffic patterns, or the like. The mobile kiosk may be self-contained, so that fixed mounting installations (e.g., concrete poured bases), as well as fixed conduit connections to power and/or communications networks, may not be necessary. For example, the mobile kiosk may utilize wireless technologies such as WiFi, Cellular/LTE/4G/5G, and satellite for communications and may use environmental friendly/neutral (e.g., solar, wind turbine, water turbine, fuel cell, etc.) power sources to supply power for operations. Accordingly, the mobile communications kiosk may be relocated without new construction
As shown in
The lower section 120 may contain a ballast area 122 as shown in
The upper section 130 may contain network communications equipment (e.g., IP switches 218, network bridges 220, modems 216, and/or other communications equipment). The network communications equipment may utilize wireless technologies to transmit data, audio, and video for use in the gate systems to support operations, as discussed in greater detail below. The upper section 130 may also include mounting locations 132 for installation of gate systems equipment to support a gate system implementation by outside vendors, as shown in
The top of the mobile kiosk 100 may include mounting points 134 for solar panels, wind turbines, or water turbines with cabling to the lower section to provide charging power to the power supply system, as shown in
The mobile kiosk 100 may include locking doors providing access to the inside of the enclosure 100. For example, the mobile kiosk 100 may include a door 128 with access to the entire lower section 120 of the pedestal, as shown in
Access for interface with truckers may be accomplished through the front of the mobile kiosk 100. The mobile kiosk 100 may include one or more openings 140 to support installation of intercom, telephone handset, barcode scanner, printer, RFID systems, cameras, and/or other data/audio/video communications systems, as shown in
Mounting points 142 may be included on the side of the mobile kiosk 100 to allow for installation of a ladder and platform to allow maintenance access to the upper section of the mobile kiosk 100 while it is in place. See
System 200 elements powered by batteries 210 and/or external sources 214 may include equipment load 224 (e.g., gate equipment such as a gate motor, signals, etc.). Equipment load 224 may be controlled by load relay 222. System 200 elements powered by batteries 210 and/or external sources 214 may also include network switch 218, and wireless bridge 220. These communication elements may send equipment status and other data and may receive commands to operate the equipment.
The mobile kiosk of
Mobile kiosk 35 may utilize a power storage system, power supply system, and power distribution system, controlled by a power management and monitoring system. These systems may be contained within mobile kiosk 35. The power storage system may be enclosed within the base of the kiosk or within compartment 11 depending on installation needs. The power management and monitoring system may be installed within the same compartment as the storage system or may be installed into another compartment with other equipment as needed.
The power storage system may provide a primary source of power to the equipment attached to the distribution system (e.g., the other electronic equipment of mobile kiosk 35 described herein). The power storage system may be monitored and controlled by the management and monitoring system. The management and monitoring system may control the recharge of the power storage system and may charge the storage system through an external power supply (e.g., solar panels 1, wind turbine 4, rain-water turbine 15, or other power sources as described above). The power distribution system may include components to regulate the flow of electricity and may include methods to disconnect the distribution system from the power source for maintenance and repair. For more details about connections between power storage system, management and monitoring systems, power sources, and power-drawing loads, see
In some embodiments, mobile kiosk 35 may include communication elements such as network antenna 2, GPS antenna 3, communication circuitry disposed in HMI-OCR-RFID-GPS-Network system and control cabinet 5, satellite dish antenna 14, and/or other elements.
Mobile kiosk 35 may include user interface elements for providing user communications, traffic signaling, and the like. For example, mobile kiosk 35 may include red-green entrance-exit traffic control lights 6, gate actuator 7, camera for facial identification and visual communication 19, key pad 20, push buttons 21, voice over IP (VOIP) phone 22, card reader (e.g., for reading smart cards, transportation worker identity cards (TWIC), and/or credit cards) 23, barcode scanner 24, near field communication (NFC) input device 25, radio frequency (RF) reader 32, gate arm 33, touchscreen 34, and/or other elements. Communication elements (e.g., camera 19, key pad 20, push buttons 21, phone 22, card reader 23, barcode scanner 24, NFC device 25, RF reader 32, touchscreen 34) may be used to communicate or relay information to an operator located away from the kiosk and/or (e.g, in the case of the touchscreen) interact directly with systems of mobile kiosk 35 without communicating with the operator.
Mobile kiosk 35 may include drive control and operation elements such as drive circuitry disposed in drive and powertrain system compartment 8 (e.g., including drive motors), drive wheels 10 or drive tracks (e.g., which may be driven by the drive equipment in drive and powertrain system compartment 8 and/or provide a solid footing for the kiosk 35), chassis with forklift pickup points 12 (e.g., which may engage with lifting equipment and/or provide a solid footing for the kiosk 35), system and control center for drive system proximity sensing/access control/sensing/alarming 13, cameras for drive sensing/monitoring/controlling (which may also be used for optical character recognition (OCR), e.g., of signs) 16, LED light (e.g., serving as a headlight and/or spotlight) 17, horn 18, infrared (IR) sensors for proximity sensing and drive safety 26, magnetic sensor for proximity sensing 27, lasers for proximity sensing and driving safety 28, motion detectors for proximity sensing and drive safety 29, acoustic sensors for proximity sensing and drive safety 30, and/or yellow/red strobe warning/alarm safety lights 31, and/or other elements. Mobile kiosk 35 may contain an area for inclusion of ballast to maintain a low center of gravity for the entire unit, as discussed above.
Mobile kiosk 35 may include mounting points for equipment to be installed into mobile kiosk 35 as needed. Some elements discussed above may be removably mounted to mobile kiosk 35 at mounting points. Examples of equipment that may be mounted on mobile kiosk 35 may include network antenna 2 (e.g., including 802.11 and/or Cellular/LTE/4G/5G), GPS antenna 3, traffic control lights 6, traffic control arm 7, and/or satellite antenna 14.
The mobile communications kiosk may include access doors in various locations allowing maintenance/repair access to components installed within internal compartments. The mobile communications kiosk may also include external attachment points to allow additional hardware to be installed for maintenance use (e.g., attaching a semi-permanent ladder to the unit for quick maintenance access)
Mobile kiosk 35 may control access to locations by various vehicles. As shown in detail in
As shown in detail in
Mobile kiosk 35 may facilitate communication between in-vehicle systems and/or users and KOS 500 using a variety of elements and connections. For example, mobile kiosk 35 may be configured to read characters using optical character recognition (OCR). Mobile kiosk 35 can read a TWIC or other identification document, a license plate, or some other identifier. Accordingly, mobile kiosk 35 may include camera 538 (e.g., as discussed above), camera controller 506 configured to obtain image data from camera 538, and OCR hardware and/or software 508 configured to analyze the image data to recognize characters. For example, if a TWIC identifies a user who has permission to access the controlled area, KOS 500 may detect the user's identity through analysis by OCR hardware and/or software 508 and permit access (e.g., by raising the gate).
Mobile kiosk 35 may be configured to read RFID tags. Mobile kiosk 35 can read an identification card or other identifying object equipped with an RFID tag using an RF reader 510. Mobile kiosk 35 may include RFID hardware and/or software 512 configured to analyze the data read from an RFID tag. For example, if an RFID tag identifies a user who has permission to access the controlled area, KOS 500 may detect the user's identity through analysis by RFID hardware and/or software 512 and permit access (e.g., by raising the gate).
Mobile kiosk 35 may be configured to communicate with in-vehicle ELD systems described above. For example, mobile kiosk 35 may include networking hardware and/or software 514 configured to receive data from in-vehicle ELD systems over a network (e.g., WiFi or 5G). For example, if an ELD system identifies a user who has permission to access the controlled area, KOS 500 may detect the user's identity through data received by networking hardware and/or software 514 and permit access (e.g., by raising the gate).
Mobile kiosk 35 may include human-machine interface (HMI) hardware and/or software 516 configured to operate one or more HMI elements 518 (e.g., VOIP, key pad, barcode scanner, NFC device, pushbuttons, and/or card readers as discussed above). A user may be able to enter identifying information using HMI elements 518. KOS 500 may evaluate the entered information and, if the user has entered information identifying them as permitted to access the controlled area, permit access (e.g., by raising the gate).
Mobile kiosk 35 may include proximity awareness hardware and/or software 520 configured to automatically detect vehicles using I/O elements 522 (e.g., motion sensors, light sensors, IR sensors, magnetic sensors, and/or acoustic sensors). In some embodiments, proximity awareness hardware and/or software 520 may detect a vehicle using I/O elements 522, and KOS 500 may permit access (e.g., by raising the gate) or perform some other action (e.g., activate audible or visual alarms).
As discussed above, KOS 500 may operate the gate and/or activate lights and/or alarms. Accordingly, mobile kiosk 35 may include access control hardware and/or software 524 configured to receive commands from KOS 500 and control the gate arm, lights, and alarms.
As discussed above, mobile kiosk 35 may include power control systems. In some embodiments, power control systems may include power control hardware and/or software 526 configured to control operation of and/or direct power from power generation elements 530 such as the solar panels, wind turbines, water turbines, fuel cells, etc. based on commands from KOS 500.
As discussed above, mobile kiosk 35 may include communications control systems. In some embodiments, communications control systems may include communications control hardware and/or software 528 configured to control operation of and/or receive data from communications elements 532 such as the GPS antenna, network antenna(s), satellite dish, etc. based on commands from KOS 500.
As discussed above, mobile kiosk 35 may be configured to drive and reposition itself in new locations. Accordingly, mobile kiosk 35 may include drive control hardware and/or software 534 configured to control and/or receive information from drive I/O elements 536. For example, based on commands from KOS 500, drive control hardware and/or software 534 may operate drive motors, brakes, horns, lights, etc. Drive control hardware and/or software 534 may receive environmental information from motion sensors, light sensors, IR sensors, magnetic sensors, etc. Sensor data may be used by KOS 500 and/or drive control hardware and/or software 534 for decision-making regarding collision avoidance and/or positioning. Drive control hardware and/or software 534 may allow mobile kiosk 35 to operate as a self-propelled, automatic, self-sufficient, autonomous, intelligent kiosk (SASAICK).
KOS client 602 may use communications equipment (e.g., 802.11 and/or Cellular/LTE/4G/5G as described above) to communicate with KOS server 652, for example using an API. KOS server 652 may comprise one or more processors configured to, for example, direct movement of the mobile kiosk and/or direct traffic control operations performed by the mobile kiosk. KOS server 652 may communicate with KOS client 602, KOS control client 654, gate system 656, and/or TOS 658. KOS server 652 may be physically separate from the mobile kiosk. In some embodiments, one or more kiosk systems 600 and/or outside kiosk systems 650 may comprise off the shelf components such as the BlueSky Solar charge controllers 3000i and IPN-REMOTE.
KOS client 602 may receive power status data, power consumption data, power collection data, and/or power capacity data from power systems 622. The data may describe the current power status as reported by the charging system, for example. KOS client 602 may report this data to KOS server 652. In some embodiments, KOS server 652 may process this data to determine and send additional commands to KOS client 602. KOS client 602 may send power control commands to power systems 622. These commands may include system on/off, change power source, and/or shut off load commands. For example, KOS server 652 may send instructions to issue a power control command to KOS client 602. Such commands may be ordered by a user and/or may be automatically generated by KOS server 652.
KOS client 602 may receive video stream data and/or pan-tilt-zoom (PTZ) responses from camera systems 612. KOS client 602 may report this data to KOS server 652. In some embodiments, KOS server 652 may process this data to determine and send additional commands to KOS client 602. KOS client 602 may send PTZ and/or camera programming commands to camera systems 612. For example, camera commands may include Up/Down/Left/Right/Zoom In/Zoom Out. For example, KOS server 652 may send instructions to issue a camera command to KOS client 602. Such commands may be ordered by a user and/or may be automatically generated by KOS server 652.
KOS client 602 may receive input data from human interface device (HID) systems 614. KOS client 602 may output this data to KOS server 652. In some embodiments, KOS server 652 may process this data to determine and send additional commands to KOS client 602.
KOS client 602 may send lighting on/off commands to lighting controls 616. For example, KOS server 652 may send instructions to issue a lighting command to KOS client 602. Such commands may be ordered by a user and/or may be automatically generated by KOS server 652.
KOS client 602 may send gate open/close commands to gate arm controls 618. For example, KOS server 652 may send instructions to issue a gate command to KOS client 602. Such commands may be ordered by a user and/or may be automatically generated by KOS server 652.
KOS client 602 may direct VOIP systems 620 to establish and/or disconnect connections to gate system servers 656. For example, in response to a user attempting to communicate at the kiosk using the VOIP phone, KOS client 602 may command VOIP systems 620 to establish a connection. When the user hangs up the phone, KOS client 602 may command VOIP systems 620 to terminate the connection. In some cases, KOS server 652 may send instructions to establish or terminate a VOIP connection to KOS client 602 (e.g., when a user away from the kiosk is attempting to call the kiosk). Such commands may be ordered by a user and/or may be automatically generated by KOS server 652.
KOS client 602 may communicate with drive control 604. Drive control 604 may manage collision avoidance systems 606, hydraulic lift control systems 608, and/or movement warning systems 610, for example.
KOS client 602 may send drive commands and/or other data to drive control 604. KOS client 602 may send directional movement commands, drive system on/off commands, override commands, geolocation data, path data, destination data, and/or emergency stop commands. For example, KOS server 652 may send drive instructions to KOS client 602. Such commands may be ordered by a user and/or may be automatically generated by KOS server 652. As noted above, KOS client 602 may communicate with individual kiosk systems using one or more APIs specific to each individual kiosk system (e.g., an API for drive control 604) in order to deliver the commands to drive control 604.
Drive control 604 may use commands from KOS client 602 and collision avoidance data from collision avoidance system 606 (e.g., sensor data about objects in kiosk path) to maneuver the kiosk. When the kiosk is in place, drive control 604 may direct hydraulic lift controls 608 to lift the kiosk off its wheels using a hydraulic lift system to reduce strain on the wheels and/or provide kiosk stability. Drive control 604 may direct movement warning systems 610 to generate audible and/or visual movement warnings while the kiosk is in motion, for example sounding alerts and/or flashing lights.
Drive control 604 may send feedback to KOS client 602. For example, feedback may include drive system alerts, status, failures, location data, and/or subsystem status. For example, in case of alert or failure that could pose a risk to one or more of the device systems, KOS client 602 may would shut down the drive system and notify KOS server 652.
The TOS may be a third party system specific to the location where the KOS is deployed. The TOS has functions that may vary depending on TOS vendor and location. The TOS may not be required for KOS system to function. The KOS Control Client may comprise an end-user client interface which may include software or hardware (e.g., a console) to allow a user to control functions of the KOS that may not be controlled automatically by the server.
While various embodiments have been described above, it should be understood that they have been presented by way of example and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments.
In addition, it should be understood that any figures which highlight the functionality and advantages are presented for example purposes only. The disclosed methodology and system are each sufficiently flexible and configurable such that they may be utilized in ways other than that shown.
Although the term “at least one” may often be used in the specification, claims and drawings, the terms “a”, “an”, “the”, “said”, etc. also signify “at least one” or “the at least one” in the specification, claims and drawings.
Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112(f). Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112(f).
This application is based on and derives priority from U.S. Provisional Patent Application No. 62/405,553, filed Oct. 7, 2016, the entire contents of which are incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
62405553 | Oct 2016 | US |