Vehicle identification and guidance systems and associated methods
Identification and guidance systems configured to facilitate vehicle management in logistics yards or the like are described. The systems can include an identification and guidance (I/G) unit attached to each transport vehicle within the logistics yard. The I/G unit transmits information (e.g., location and guidance information) over a wireless network to a remote controller. The remote controller can transmit relevant information received from the I/G unit to a portable communications device associated with the transport vehicle to which the I/G unit is mounted. For example, the portable communications device may be located in a tractor being used to maneuver the transport vehicle about the logistics yard so that the driver can use the information displayed on the portable communications device to assist with maneuvering the transport vehicle. Related methods are also described.
Latest ASSA ABLOY Entrance Systems AB Patents:
- Automatic door operator
- Control arrangement for an entrance system having one or more swing door movable door members
- Automatic door operator and drive mechanism thereof
- Automatic door operator and method of operating automatic door operator
- Control systems for operation of loading dock equipment, and associated methods of manufacture and use
This application is a division of U.S. patent application Ser. No. 16/438,347, filed Jun. 11, 2019, issued as U.S. Pat. No. 11,262,747, and entitled “VEHICLE IDENTIFICATION AND GUIDANCE SYSTEMS AND ASSOCIATED METHODS,” which is hereby incorporated by reference in its entirety.
TECHNICAL FIELDThe following disclosure relates generally to systems and methods for identifying and guiding transport vehicles in logistics yards and the like.
BACKGROUNDCommercial enterprises typically utilize distribution, processing, and/or manufacturing centers for a variety of purposes. Distribution centers, for example, are often used to receive, process, and/or re-ship units, parcels, and other goods and materials. Manufacturing centers typically require the delivery of consumable materials and the shipment of finished products. Regardless of their specific function, distribution, processing and manufacturing centers may include a warehouse or other industrial building having one or more loading dock stations, a perimeter barrier, a gated entrance and/or exit, and parking or staging areas where idle transport vehicles may be parked. For ease of reference, such areas may be referred to herein as a “logistics yards.”
A common feature of logistics yards is that transport vehicles are entering, moving within, and exiting the logistics yard throughout the day. For example, even moderate-size logistics yards typically include numerous loading dock stations that see a great deal of inbound and outbound traffic and require coordinated use. As a result, it is often necessary to keep detailed tracking information for each transport vehicle within logistics yards that include numerous transport vehicle parking spaces or staging areas. Maintaining detailed tracking information may also be important when some or all transport vehicles within the logistics yard look alike.
As used herein, the term “transport vehicle” broadly refers to any type of vehicle capable of storing and transporting goods. Transport vehicles include, for example, over the road (OTR) trailers (typically towed by an OTR tractor or dedicated logistics yard tractor) as well as transport vehicles permanently integrated with a towing vehicle (e.g., U-Haul trucks or UPS delivery trucks). Regardless of the specific type of transport vehicle, the transport vehicle is typically maneuvered within the logistics yard by a driver. Drivers maneuvering transport vehicles within a logistics yard may benefit from various types of assistance, especially with respect to aligning a transport vehicle at a loading dock station. Previously disclosed maneuvering and parking aids include U.S. Pat. No. 9,623,859, titled TRAILER CURVATURE CONTROL AND MODE MANAGEMENT WITH POWERTRAIN AND BRAKE SUPPORT; U.S. Pat. No. 9,656,691, titled METHOD FOR PERFORMING AN AT LEAST SEMI-AUTONOMOUS PARKING PROCESS; U.S. Pat. No. 9,623,859, titled TRAILER CURVATURE CONTROL AND MODE MANAGEMENT WITH POWERTRAIN AND BRAKE SUPPORT; U.S. Pat. No. 8,364,334, titled SYSTEM AND METHOD FOR NAVIGATING AN AUTO VEHICLE USING LASER DETECTION AND RANGING; U.S. Pat. No. 9,283,935, titled RAIL GUIDED VEHICLE SYSTEM; U.S. Pat. No. 8,978,562, titled RAIL GUIDED VEHICLE SYSTEM; U.S. patent application Ser. No. 15/408,242, titled METHOD AND DEVICE FOR MONITORING AN AUTONOMOUS DRIVING OPERATION OF A MOTOR VEHICLE WITHIN A PARKING FACILITY; U.S. patent application Ser. No. 15/450,210, titled TRAILER CURVATURE CONTROL AND MODE MANAGEMENT WITH POWERTRAIN AND BRAKE SUPPORT; U.S. Pat. No. 10,126,754, titled METHOD FOR SETTING TRAVEL PATH OF AUTONOMOUS VEHICLE; U.S. Pat. No. 9,896,130, titled GUIDANCE SYSTEM FOR A VEHICLE REVERSING A TRAILER; U.S. Pat. No. 9,821,845, titled TRAILER LENGTH ESTIMATION METHOD USING TRAILER YAW RATE SIGNAL; U.S. Pat. No. 9,656,691, titled METHOD FOR PERFORMING AN AT LEAST SEMI-AUTONOMOUS PARKING PROCESS IN A GARAGE; U.S. Pat. No. 9,541,409, titled MARKER AIDED AUTONOMOUS VEHICLE LOCALIZATION, and U.S. Pat. No. 9,540,043, titled TRAILER BACKUP ASSIST SYSTEM WITH ACTIVE TRAILER BRAKING FOR CURVATURE CONTROL, each of which is incorporated herein by reference in its entirety. Many of the maneuvering aids disclosed in the above-mentioned patents and published patent applications only provide limited or specialized maneuvering assistance and/or are complicated systems that do not lend themselves to broad applicability. Accordingly, a need exists for improved systems and methods of identifying, tracking, and guiding transport vehicles within a logistics yard.
Described herein are various embodiments of systems and methods for identifying and/or guiding transport vehicles within a logistics yard, and more specifically, to an identification/guidance (I/G) unit that can be attached to a transport vehicle and communicate with a remote controller and/or a portable communications device (e.g., smart phone, tablet, etc.) to facilitate management of the logistics yard. In some embodiments, the I/G unit can be attached to a transport vehicle upon the transport vehicle entering a logistics yard, at which point the I/G unit is linked in the system to the transport vehicle to which it is attached such that any subsequent transport vehicle information transmitted by the I/G unit is understood to be associated with that specific transport vehicle. As the transport vehicle moves or is moved through the logistics yard, transport vehicle information such as the location of the transport vehicle is transmitted by the I/G unit to a remote controller via a network. The transport vehicle information can then be relayed from the remote controller to a portable communications device, such as a smart phone or tablet, via the network. The I/G unit can include one or more cameras and/or sensors that can be used to assist a driver in maneuvering the transport vehicle through the logistics yard. For example, the I/G unit can transmit video taken by a camera on the I/G unit to the remote controller, which relays the video to a portable communications device for use by the driver to maneuver the transport vehicle on which the I/G unit is attached. The video can be particularly useful when backing the transport vehicle up to a dock station.
Certain details are set forth in the following description and
In the Figures, identical reference numbers identify identical, or at least generally similar, elements. Many of the details, dimensions, angles, and other features shown in the Figures are merely illustrative of particular embodiments of the disclosure. Accordingly, other embodiments can have other details, dimensions, angles, and features without departing from the spirit or scope of the present invention. In addition, those of ordinary skill in the art will appreciate that further embodiments of the invention can be practiced without several of the details described below.
Any type of perimeter barrier 110 can be used for the logistics yard 100, such as a concrete wall or chain link fence. In some embodiments, the perimeter barrier 110 can fully enclose the logistics yard 100, and in other embodiments, the perimeter barrier 110 can only partially enclose the logistics yard 100. In some embodiments, the perimeter barrier 110 is optional and can be eliminated altogether. In the illustrated embodiment, the antennas 194 are located at the perimeter barrier 110 (e.g., at the corners of the perimeter barrier 110), although in other embodiments, other antenna locations within the logistic yard 100 are possible.
The entrance/exit gate 120 can be any type of gate or barrier suitable for controlling access into and out of the logistics yard 100. While
The guard shack 130 can be any type of structure positioned proximate an entrance/exit gate 120 and used to control entry or exit of transport vehicles 160 into and out of the logistics yard 100. As described in further detail below, the guard shack 130 can also play a role in attaching and removing the I/G units 191 to the transport vehicles 160 entering and exiting the logistics yard 100, and/or in entering I/G unit 191 information into the remote controller 192 so that subsequent information transmitted by the I/G unit 191 can be associated with the corresponding transport vehicle 160.
The warehouse 140 can be any type of warehouse or other building, including a warehouse configured for distribution, manufacture and/or processing. The logistics yard 100 may also include multiple warehouses 140. The warehouse 140 can include any number of the loading dock stations 141, and the loading dock stations 141 can include any type of equipment typically used at loading docks (e.g., a dock door, a trailer restraint, a dock leveler, etc.). The loading dock stations 141 can further include automated loading dock equipment systems, such as those disclosed in U.S. Pat. No. 10,081,504, titled SYSTEMS AND METHODS FOR AUTOMATICALLY CONTROLLING LOADING DOCK EQUIPMENT; and U.S. patent application Ser. No. 15/145,605, titled CONTROL SYSTEMS FOR OPERATION OF LOADING DOCK EQUIPMENT, AND ASSOCIATED METHODS OF MANUFACTURE AND USE, both of which are incorporated herein by reference in their entirety.
The parking area 150 can have any size, shape and location within the logistics yard 100, and the logistics yard 100 can include any number of parking areas 150. As described previously, the transport vehicle 160 can be any type of transport vehicle, including trailers that are towed by OTR tractors or dedicated logistics yard tractors and integrated cargo vehicles.
In
The front surface 220 of the I/G unit 191 located opposite the rear surface 210 faces outwardly from the rear surface of the transport vehicle 160 when attached thereto. Various data collection components of the I/G unit 191 can be located at or near the front surface 220, with each of the components being configured to gather transport vehicle information that is sent to the remote controller 192 and/or the portable communications device 193 via a network.
In some embodiments, a camera 221 is located on the front surface 220 of the I/G unit 191. The camera 221 can be configured to take video and/or still images of a field of view extending outward from the I/G unit 191. For example, when the I/G unit 191 is attached to the rear door of the transport vehicle 160, the camera 221 will take video and/or still images of an area proximate the transport vehicle (i.e., immediately behind the transport vehicle 160). The video and/or still images can be sent to the remote controller 192 and/or the portable communications device 193 via a wireless network so that the video and/or still images can be displayed on the remote controller 192 and/or the portable communications device 193. When the video and/or still images are displayed on the portable communications device 193, the driver of the transport vehicle 160 can view the video and/or still images displayed on the portable communications device 193 to assist with, e.g., positioning the transport vehicle 160 at a loading dock station 141. For example, the camera 221 can obtain video of the area behind and proximate the transport vehicle 190 as the driver is backing the transport vehicle 160 up to the loading dock station 141 or maneuvering the transport 160 trailer into the parking area 150, and the I/G unit 191 transmits this video feed in real time or near real time to the portable communications device 193 located in the cab of the tractor 161 maneuvering the transport vehicle 160. Using the video feed provided on the display of the portable communications device 193, the driver can view the area behind the transport vehicle 160 and use this information to align the transport vehicle 160 at the loading dock station 141 or into a parking space in the parking area 150. The video feed provided by the camera 221 can be either direct imaging or mirrored imaging (i.e., where the video feed displayed on the display of the portable communications device 193 is the mirror image of the actual view of the camera). Mirrored imaging can be beneficial for use with articulated transport vehicles. In the illustrated embodiment, the camera 221 is recessed into the front surface 220 of the I/G unit 191 in order to provide some measure of protection to the camera from, e.g., weather. Non-recessed configurations can also be used.
The I/G unit 191 can further include a positioning device 222 configured to receive location data relating to the location of the I/G unit 191 (and the transport vehicle 160 to which it is attached) and to determine the location of the I/G unit 191 based on the received location data. Any positioning device capable of receiving real time or near real time location data and determining the location of the I/G unit 191 based on the received location data can be used. In some embodiments, the positioning device 222 includes a receiver that is configured to receive location data from an external positioning source. The external positioning source transmitting location data can be satellites (such as when the Global Positioning System (GPS) is used), cellular towers, WiFi networks, beacons (such as Bluetooth beacons), terrestrial transmitters, etc. Depending on the external source, the positioning device 222 may further include a processor configured to process raw location data into specific location information. For example, the positioning device 222 may be able to perform triangulation calculations based on the raw location data received from the external source to thereby compute the specific location of the I/G unit 191. Once the specific location of the I/G unit 191 has been received and/or computed by the positioning device 222, it can be transmitted by the I/G unit 191 to, e.g., the remote controller 192. While shown on a top surface of the I/G unit 191 in
The I/G unit 191 can also include one or more sensors 223 configured to provide transport vehicle guidance information, such as information relating to the proximity of the transport vehicle 160 to surrounding objects (e.g., the loading dock station 141). The sensors 223 can be any type of sensors, including infrared sensors, laser sensors, microwave sensors, inductive loop sensors, photo sensors, pressure sensors, ultrasonic sensors, sonar sensors, thermal sensors, optical sensors, magnetic sensors, or camera analytics sensors, and multiple types of sensors can be used on the I/G package 191.
In some embodiments, the sensors 223 can be located on one or more surfaces of the I/G unit 191 in order to provide multi-faceted guidance information. For example, a downward looking sensor 223a can be used to sense objects on or toward the ground as the transport vehicle 160 backs up to the loading dock station 141, such as a trailer restraint positioned on the ground in front of the loading dock station 141. When the trailer restraint is identified by the downward looking sensor 223a, a signal can be sent to the driver (via the portable communications device 193) to let the driver know the transport vehicle 160 is aligned with the trailer restraint. Similarly, a front facing sensor 223b can be used to send signals to the driver (via the portable communications device 193) letting the driver know how close or far away from the loading dock station 141 the transport vehicle 160 is as it is backing up to the loading dock station 141. In some embodiments, a proximity sensor configured to emit an electromagnetic field or a beam of electromagnetic radiation can be used for detecting an object (such as in the case of the downward looking sensor 223a sensing for a trailer restraint described above) and/or for determining distance (such as in the case of the front facing sensor 223b determining the distance to the loading dock station 141 described above). In the case of detecting an object, the proximity sensor detects a change in the emitted electromagnetic field or beam of electromagnetic radiation to identify an object. In the case of determining distance, the proximity sensor measures the time it takes for the beam of electromagnetic radiation to bounce off an object and return to the sensor and calculates distance based on the speed at which the beam travels.
In some embodiments, the one or more sensors 223 are configured to detect positional locating devices 101 embedded or otherwise positioned on or in the logistics yard 100. For example, the logistics yard 100 can include a plurality of locating devices 101, such as magnetic, electrical, electro-optical, RFID transponder, wireless transmitter, or similar devices that are embedded in, or otherwise attached to or near, the surface of the logistics yard 100. In such embodiments, the sensor 223 can be configured to detect the presence of a locating device 101, receive identification information relating to the locating device 101, and/or receive physical location information from the locating device 101. In some embodiments, each locating device 101 is associated with a location in the logistics yard 100 such that when the sensor 223 detects the locating device 101, the physical location information associated with the sensed locating device 101 is transmitted to the sensor 223 (or processor of the I/G unit 191). Alternatively, the sensor 223 (in association with the processor, transceiver, etc. of the I/G unit 191) can detect a specific locating device 101, receive locating device identification information from the locating device 101, and transmit this identification information to the remote controller 192, which then accesses a database including physical location information for each identified locating device 101. In some embodiments, the sensor 223 can include a magnetic field sensor, such as an FLC 100 magnetic field sensor from Stefan Mayer Instruments, Wallstr. 7, D-46535 Dinslaken, Germany. Additional disclosure of a system of sensors and locating devices suitable for use in the embodiments described herein is set forth in U.S. patent application Ser. No. 16/109,603, titled VEHICLE GUIDANCE SYSTEMS AND ASSOCIATED METHODS OF USE AT LOGISTICS YARDS AND OTHER LOCATIONS, which is hereby incorporated by reference in its entirety.
In some embodiments, the locating devices 101 can be used to establish paths along which the transport vehicle 160 can travel, such as a path for backing the transport vehicle 160 up to one of the loading dock stations 141 or parking the transport vehicle 160 in the parking area 150. Such a path can include a locating device 101 located at a starting position. The sensor 223 is used to detect the starting position locating device 101 and subsequent locating devices 101 along the path. In some embodiments, a path of locating devices 101 can be provided for each loading dock station 141. These paths are one embodiment of the track or rail guidance system described in U.S. patent application Ser. No. 16/109,603, titled VEHICLE GUIDANCE SYSTEMS AND ASSOCIATED METHODS OF USE AT LOGISTICS YARDS AND OTHER LOCATIONS, which is hereby incorporated by reference in its entirety.
The I/G unit 191 can also include a unique identifier 224 configured for use in identifying the I/G unit 191 and the transport vehicle 160 to which it is attached. The unique identifier 224 can include any type of unique identifier, including both identifier devices and identifying indicia. Specific, though non-limiting, examples include a QR code, a bar code, or an alphanumeric code. The unique identifier 224 can be used when initially pairing the I/G unit 191 with the transport vehicle 160. For example, with reference to
The I/G unit 191 further includes an antenna 225 configured to transmit data from the I/G unit 191 to the remote controller 192 and/or a portable communications device 193. In the illustrated embodiment, the antenna 225 is located on a side surface of the I/G unit 191, although in other embodiments, the antenna 225 may be located on any suitable surface of the I/G unit 191. Any type of antenna suitable for transmitting data can be used for antenna 225. In some embodiments, the antenna 225 can be selected based on the type of network used with the system 190. For example, when a LAN is used to transmit data within the system 190, the antenna 225 can be a LAN-configured antenna. The antenna 225 cooperates with the transceiver 204 (
Other features of the I/G unit 191 can include a housing 201 that is hardened so that the I/G unit 191 can withstand inclement weather, electromagnetic interference (EMI) and/or other harsh conditions and handling. The housing 201 can also have a color that provides a high contrast with the color of the transport vehicle 160 so that it is easy to visually identify the I/G unit 191 on the exterior of the transport vehicle 160. The I/G unit 191 can also include a visible centerline guide 226 that can be used to assist with proper positioning of the I/G unit 191 on the rear end of the transport vehicle 160. For example, in order for real time video sent from the I/G unit 191 to the portable communications device 193 to be helpful in assisting a driver align the transport vehicle 160 with the loading dock station 141, it may be necessary for the camera 221 to be positioned at the centerline of the rear end of the transport vehicle 160. The centerline guide 226 can include, e.g., a transparent window extending from the front surface 220 to the rear surface 210 of the I/G unit 191. A centerline marking may be provided on the rear end of the transport vehicle 160 so that the I/G unit 191 can be aligned by viewing the centerline guide 226. The I/G unit 191 can also include a manual switch 227 that allows a user to manually turn the I/G unit 191 on and off. In some embodiments, the manual switch 227 also allows a user to manually switch the I/G unit 191 between power modes (described in further detail below).
As described previously, the I/G unit 191 is configured to transmit both identification and guidance information. However, it should be appreciated that in some embodiments, the I/G unit 191 is configured to transmit only identification information or only guidance information.
In some embodiments, the I/G unit 191 is powered by the battery 205. Any suitable type of battery may be used to power the I/G unit 191, including a rechargeable battery such as a lithium ion rechargeable battery. In embodiments using a rechargeable battery 205, the I/G units 191 can be recharged at the guard shack 130 (
In order to manage battery power in the I/G unit 191 and generally extend the life of the I/G unit 191 during use, the I/G unit 191 can be configured to operate in two or more power modes. In some embodiments, the I/G unit operates in at least a low power mode and a high power mode. In low power mode, the battery 205 provides a relatively low amount of power, so that only a limited number of functions, or no functions, can be carried out by the I/G unit 191. In full power mode, enough power is provided to the I/G unit 191 so that it is mostly or fully functional. Examples of when the I/G unit 191 may be put in low power mode include when the I/G unit 191 is not in use (i.e., not attached to a transport vehicle 160) and when the transport vehicle 160 to which the I/G unit 191 is attached is parked in a parking area 150. In some embodiments, the functionality of the I/G unit 191 when in low power mode is limited to positioning/location functionality. In other words, guidance functionality (e.g., camera and sensors) may not be operational when the I/G unit 191 is in low power mode. As such, the transport vehicle 160 to which the low power mode I/G unit 191 is attached can still be located within the logistic yard 100. In other embodiments, the functionality of the I/G unit 191 when in low power mode is limited to receiving and processing instructions to enter high power mode. In other words, the I/G unit does not even provide positioning/location functionality in low power mode.
Implementation of the battery power management described previously is generally carried out by the processor 201 and/or the remote controller 192. The processor 201 can execute software that changes the power mode to, for example, a low power mode or a high power mode. Instructions to execute this software may come from, for example, the remote controller 192. In some embodiments, instructions from the remote controller 192 to enter a low power mode or a high power mode are initiated by an operator at the remote controller 192. For example, the display 195 of the remote controller 192 can display a user interface that allows an operator to monitor various aspects of the system 190, including the power mode of each I/G unit 191 being used in the logistics yard 100. The user interface can include the ability to change the power mode of any I/G unit 191. When an operator changes the power mode of an I/G unit 191 via the user interface, the remote controller 192 transmit instructions to the I/G unit 191. When received by the I/G unit 191, the instructions cause the processor to execute the software in accordance with the instructions sent (i.e. move into low power mode or move into high power mode). In an example, the user interface of the remote controller 192 indicates that an I/G unit 191 has been attached to a transport vehicle 160 entering the logistics yard 100, at which point the operator sends instructions to the I/G unit 191, via the remote controller 192, to enter a high power mode. The user interface can display movement of the transport vehicle 160 through the logistics yard 100, and when the operator sees that the transport vehicle 160 has parked in the parking area 150 or at the loading dock station 141, the operator can send another instruction to the I/G unit 191, via the remote controller 192, to enter a low power mode. In embodiments where low power mode does not include positioning/location functionality, the operator can send instructions to the I/G unit 191, via the remote controller 192, to enter high power mode so that positioning/location functionality is activated, and the location of the transport vehicle 160 can be verified.
In some embodiments, the location of the I/G unit 191 within the logistics yard 100 controls the power mode of the I/G unit 191. For example, when the I/G unit 191 sends transport vehicle location information to the remote controller 192 indicating that the transport vehicle 160 to which the I/G unit 191 is attached is located in the parking area 150, the remote controller 192 transmits instructions to the I/G unit 191 that, when executed by the processor 201, puts the I/G unit 191 in low power mode. Similarly, when the I/G unit 191 transmits transport vehicle location information indicating that the transport vehicle 160 to which the I/G unit 191 is attached is near a loading dock station 141, the remote controller 192 sends instructions to the I/G unit 191 that, when executed by the processor 201, puts the I/G unit 191 in full power mode so that guidance functionality (e.g., camera and/sensors) becomes operational.
Other manners of controlling the power mode of the I/G unit 191 include use of an accelerometer, motion detector, or related device built in to the I/G unit 191 to detect when the transport vehicle 160 is moving. If the accelerometer or other motion detecting device determines that the I/G unit 191 is in motion, then the processor 201 executes the software such that the I/G unit 191 enters the high power mode. Alternatively, if the accelerometer or other motion detecting device does not detect movement for a prescribed period of time (e.g., 5 minutes), the processor 201 executes the software such that the I/G unit 191 enter the low power mode. The I/G unit 191 can also include a manual switch 227 that provides the ability to change the power mode of the I/G unit 191 directly at the I/G unit 191. Yard workers can use the manual switch 227 to briefly change the power mode of the I/G unit from low power mode to high power mode so that, for example, the I/G unit can send updated location information to the remote controller 192.
The remote controller 192 may be any type of computer system configured to receive, process and/or transmit transport vehicle information. In some embodiments, the remote controller 192 is a desktop computer, a CPU with one or more sensors, or the like. A primary role of the remote controller 192 is to receive transport vehicle information from one or more of the I/G units 191 via a network of the system 190 and to transmit transport vehicle information to one or more of the portable communication devices 193 via the network. In the process of receiving and transmitting transport vehicle information, the remote controller 192 can also store transport vehicle information in an associated database, display transport vehicle information (such as on the display 195), process transport vehicle information, and/or transmit instructions for execution by the portable communications device 193 and/or the I/G unit 191 based on how the transport vehicle information has been processed by the remote controller 192. For example, and as described previously, the remote controller 192 can receive transport vehicle location information from the I/G unit 191, process the transport vehicle location information, and, based on how the transport vehicle location information is processed by the remote controller 192, transmit instructions to the I/G unit 191 to toggle between different power modes.
In some embodiments, the remote controller 192 is configured to receive transport vehicle information from multiple I/G units 191 and transmit transport vehicle information (e.g., video and/or still image data, etc.) to multiple portable communication devices 193 in a manner that promotes efficient management of the logistics yard 100. As such, the remote controller 192 is configured to keep track of which of the portable communications devices 193 is associated with which of the I/G units 191 and convey information (e.g., video and/or still image data) to the portable communication devices 193 in accordance with these associations. For example, the remote controller 192 receives and utilizes information linking a specific I/G unit 191 to a specific transport vehicle 160 to which it is attached, such that video and/or still image data transmitted by the I/G unit 191 to the remote controller 192 is processed by the remote controller 192 in a way that recognizes that video and/or still image data as relating to the specific transport vehicle 160. The remote controller 192 is then configured to transmit the video and/or still image data to the specific portable communication device 193 associated with the same transport vehicle 160 (i.e., to the portable communication 193 device being used by the driver responsible for maneuvering the transport vehicle 160 about the logistics yard 100). The remote controller 192 can also be configured to communicate with or incorporate an ERP system to further link together information pertaining to the specific transport vehicles 160 within logistics yard 100.
In some embodiments, the remote controller 192 includes a display 195 on which various information transmitted by the I/G unit 191 can be displayed. The display may include a user interface 305 that allows a user to access information transmitted to the remote controller 192 and, in some embodiments, send instructions to the I/G unit 191 and/or the portable communications device 193. In one example, the user interface includes a map of the logistics yard 100 shown on the display 195, including the location of all of the transport vehicles 160 in the logistics yard 100 (with location information obtained from the I/G units 191 associated with each of the transport vehicles 160). The map may be updated in real time or near real time such that movement of the transport vehicles 160 about the logistics yard 100 is shown on the map. The map may be interactive such that moving a cursor, clicking or tapping (in embodiments where display 195 is a touch screen) on a specific transport vehicle 160 brings up additional information regarding the transport vehicle 160. The type of information that can be accessed by clicking or tapping on a transport vehicle 160 can include, for example, the contents of the transport vehicle 160, the loading dock station 141 at which the transport vehicle 160 is to be loaded or unloaded (obtained, e.g., via integration of the system 190 with an ERP system), the time of entry of the transport vehicle 160 into the logistics yard, the driver assigned to the transport vehicle 160, and the time elapsed since the last movement of the transport vehicle 160. This information may be displayed in a window overlaid on the map or in a separate window. Clicking or tapping on the transport vehicle 160 may also access the type of information that is relayed to the portable communications device 193, such as the video feed from the camera 221 of the I/G unit 191, and sensor information from the sensors 223 on the I/G unit 191. This may allow for remote supervision of a transport vehicle as it moves around the logistics yard, such as may be desirable when a trainee or new employee is maneuvering the transport vehicle 160.
As described above, the remote controller 192 can be located within the warehouse 140. By locating the remote controller 192 within the warehouse 140, a warehouse manager or the like may be able to use the remote controller 192 to better manage operations within the warehouse 140 and in the logistics yard 100 in general. However, the remote controller 192 need not be located in the warehouse 140, and in other embodiments, the remote controller 192 can be located anywhere in the logistics yard 100, or at a location remote form the logistics yard 100.
In some embodiments, the portable communications device 193 includes a display screen 405 configured to display video and/or still images transmitted by the camera 221 of the I/G unit 191. The portable communications device 193 can also include a user interface that allows a user to access information transmitted to the portable communications device 193. In some embodiments, the portable communications device 193 is preferably a device that can be located in the cab of the tractor 161 so that the driver can view the information displayed on the screen 405 of the portable communications device 193 while maneuvering the transport vehicle 160. For example, when real time video is taken by the camera 221 of the field of view behind the transport vehicle 160, the real time video can be transmitted to the remote controller 192, relayed to the portable communications device 193, and then displayed on the screen 405 of the portable communications device 193. The driver can then view and use the real time video while backing up and aligning the transport vehicle 160 at the loading dock station 141. In some embodiments, the portable communications device 193 can include a dedicated screen 405 in the cab of the tractor 161 such that other devices such as laptops, smart phones and tablets do not need to be used or available in order to receive the transport vehicle information transmitted by the remote controller 192.
The system 190 described herein generally uses a wireless network in order to transmit data between components of the system 190 (i.e., the I/G unit 191, the remote controller 192, and the portable communications device 193). The components of the system 190 are each provided with the necessary hardware, software, electronics, sensors, etc., for communicating with the other components of the system 190 via a wireless network, such as conventional wireless networks known in the art. The specific type of network used for the system 190 is generally not limited, provided the network is capable of wirelessly transmitting data between the I/G unit 191, the remote controller 192, and the portable communications device 193. In some embodiments, the network is a local area network (LAN), a wide area network (WAN), a WiFi network, a cellular network, a mesh network, the Cloud, and IoT network, or any other type of network configured for wireless transmission of data between components of the identification and guidance system 190. The antennas 194 can be provided throughout the logistics yard 100 to facilitate transmission of data via the network between the components of the system 190. The antennas 194 may be configured for the specific type of network being used.
In some embodiments, a LAN is the preferred network type such that transmitted data is maintained locally and the overall system is simplified. The LAN provides a computer network that spans a relatively small area and therefore may require less infrastructure. In some embodiments in which the logistics yard 100 includes multiple warehouses 140, a LAN may be provided for each warehouse 140 (
In an IOT environment, the components of the system 190 may all be connected to the Internet so that each component of the system 190 is capable of communicating with other components of the system 190. Cloud computing may also be used to network the components of the system 190. The system 190 can be configured such that all components of the system 190 communicate over the network through the remote controller 192. The network can also be configured so that all components of the system 190 are directly connected with the network, thereby permitting direct communication between any components of the system 190. In a mesh network, the mesh network is used to network together individual components of the system, e.g., multiple of the I/G units 191.
When the network of the system 190 is a Bluetooth mesh network, the mesh network provides a dynamic and non-hierarchical infrastructure where each node in the network (e.g., each of the I/G units 191) is directly connected to as many other nodes in the network as possible. A mesh network thereby provides for efficient routing of information within the network.
When a cellular network is used with the system 190, the network can include a cellular gateway to provide reliable and flexible Internet access to all components of the system 190. For example, a cellular gateway can facilitate communication between a mesh network of the I/G units 191. Use of a cellular gateway as a component of the network can eliminate the need for the components of the system 190 to access a LAN or WAN set up at the warehouse but used for other purposes.
The identification and guidance system 190 can also include a non-local network 500 in place of or as a supplement to the LAN 501. The non-local network 500 can include, for example, the Internet, the Cloud, a WAN, or a cellular network. Transmissions 500a carry information from components of the identification and guidance system 190 to the non-local network 500 and back. In some embodiments, the transmissions 500a pass directly from components of the identification and guidance system 190 (e.g., the I/G unit 191, the remote controller 192, and the portable communications device 193) and back, while in some embodiments the information is first passed to antennas 194 and then to network 500.
In block 610, the transport vehicle 160 enters the logistics yard 100 and the I/G unit 191 is attached to the rear end of the transport vehicle 160 as described above. As part of attaching the I/G unit 191 to the transport vehicle 160, the unique identifier 224 of the I/G unit 191 and the identity of the transport vehicle 160 input into the remote controller 192 and linked together (as described above) such that any subsequent information transmitted by the I/G unit 191 is linked to the transport vehicle 160 to which the I/G unit 191 is attached. In some embodiments, the I/G unit 191 is attached to the rear end of the transport vehicle 160 at the centerline of the transport vehicle 160. Any suitable manner of attaching the I/G unit 191 to the transport vehicle 160 can be used, such as via an adhesive, Velcro, magnets, clips, straps or the like.
Once the I/G unit 191 is attached to the transport vehicle 160 in block 610 and the unique identifier 224 and the identity of the transport vehicle 160 are entered into the remote controller 192 and associated, the remote controller 192 instructs the I/G unit 191 to enter full power mode so that the I/G unit 191 is fully functional and all components of the I/G unit 191 are operational. Once the I/G unit 191 is in full power mode, the I/G unit 191 begins to transmit a variety of transport vehicle information, including location information and guidance information.
In block 620, the transport vehicle 160 is parked and temporarily stored in the parking area 150 of the logistics yard 100. The transport vehicle 160 can be parked and stored in the parking area 150 if, e.g., the loading dock station 141 where the transport vehicle 160 is to be loaded or unloaded is not available when the transport vehicle 160 enters the logistics yard 100 (e.g., another transport vehicle is occupying the assigned loading dock station). While parked, the I/G 191 transmits location data to the remote controller 192 via the network providing the location of the transport vehicle 160 within the logistics yard 100. The location information is received by the remote controller 192, which then relays the location information to the portable communications device 193. In some embodiments, the location information is transmitted to the portable communications device 193 of the driver who will ultimately be responsible for moving the transport vehicle 160 to the assigned loading dock station 141 once the loading dock station 141 becomes available. In this way, the driver can easily locate the transport vehicle 160 when necessary, even if the transport vehicle 160 is parked amongst several other transport vehicles 160 that may look similar or identical to the assigned transport vehicle 160.
When the transport vehicle 160 is parked at the parking area 150 in block 620, the remote controller 192 receives the location information from the I/G unit 191 and determines from this information that the transport vehicle 160 is located in the parking area 150. The remote controller 192 responds to this information by sending instructions to the I/G unit 191 to switch to the low power mode. In the low power mode, the functionality of the I/G unit 191 is limited so as to not expend excess power and thereby prolong the battery life of the I/G unit 191. In some embodiments, the I/G unit 191 only transmits location information in the low power mode, and no other functionality (e.g., guidance functionality) is enabled.
In block 630, the transport vehicle 160 is hooked up to a tractor 161 and moved to the loading dock station 141 once it becomes available. As the transport vehicle 160 leaves the parking area 151, location information is transmitted by the I/G unit 191 to the remote controller 192, which processes this information and determines that the transport vehicle 160 has left the parking area 151. The remote controller 192 then transmits instructions to the I/G unit 191 to toggle into full power mode so that the I/G unit 191 becomes fully functional. In the fully functional state, the I/G unit 191 can transmit guidance information, such as video feed from the camera 221 and/or object proximity information from one or more of the sensors 223. The guidance information is received by the remote controller 192 and transmitted to the portable communications device 193 used by the driver maneuvering the transport vehicle 160. The guidance information assists the driver with aligning the transport vehicle 160 at the loading dock station 141.
In block 640, the transport vehicle 160 leaves the loading dock station 141 after loading or unloading is complete and proceeds toward the exit of the logistics yard 100. When the transport vehicle 160 arrives at the guard shack 130 of the logistics yard 100, the attendant removes the I/G unit 191 from the transport vehicle 160. In some embodiments, the removed I/G unit 191 is stored in the guard shack 130. Storage of the I/G unit 191 in the guard shack 130 can include docking the I/G unit 191 in a recharging station so that the I/G unit 191 is fully charged before subsequent use. Information transmitted to the remote controller 192 by the I/G unit 191 as it approaches the exit gate (e.g., location information) causes the remote controller 192 to send instructions to the I/G unit 191 to toggle to low power mode. Alternatively, the attendant at the guard shack can manually toggle the I/G unit 191 using the manual switch 227 to low power mode or even turn the I/G unit 191 off once it has been removed from the transport vehicle 160.
Although the method 600 described above includes a single parking step (i.e., between entering the logistics yard 100 and moving to the loading dock station 141), the method 600 may include other parking steps as necessary. For example, after being loaded or unloaded at the loading dock station 141, the transport vehicle 160 may require an additional parking step before leaving the logistics yard 100. In such embodiments, the parking step as described above can be repeated as necessary (e.g., location information transmitted by the I/G unit 191 indicating placement within a parking area 151 can result in the remote controller 192 instructing the I/G unit 191 to toggle to low power mode). Similarly, the method 600 described above may be altered when no parking is required (e.g., when the transport vehicle 160 can proceed directly to the loading dock station 141 upon entering the logistics yard 100). In such scenarios, the I/G unit 191 remains in full power mode so that the I/G unit 191 has full functionality (including guidance functionality) while being maneuvered around the logistics yard 100.
In block 710, the transport vehicle 160 enters the logistics yard 100 and the I/G unit 191 is attached to the transport vehicle 160. As described above, the I/G unit 191 can include an attachment mechanism 211 for releasably attaching the I/G unit 191 to the transport vehicle, and the I/G unit 191 can be attached to the transport vehicle 160 by an attendant at the guard shack 130. In some embodiments, the I/G unit 191 is attached to a rear external surface of the transport vehicle 160. Once the I/G unit 191 is attached to the transport vehicle 160, the I/G unit 191 begins to transmit information to the remote controller 192 via the network. The I/G unit 191 can transmit information including, but not limited to, the location of the I/G unit 191. The I/G unit 191 can continue to transmit updated location information to the remote controller 192 throughout the time that the transport vehicle is located within the logistics yard 100.
As described above, the process of attaching the I/G unit 191 to the transport vehicle 160 can include entering the unique identifier 224 into the remote controller 192, entering identify information of the transport vehicle 160 to which the I/G unit is attached into the remote controller 192, and pairing the identifier information within the remote controller 192. This results in associating the I/G unit 191 with the transport vehicle 160 within the remote controller 192 so that any data, information, signals, etc., sent by the I/G unit 191 is associated with the transport vehicle 160 within the remote controller 192. For example, any location information transmitted by the I/G unit 191 and received by the remote controller 192 is automatically processed by the remote controller 192 as providing the location of the transport vehicle 160.
In block 720, the transport vehicle 160 exits the logistics yard 100 and the I/G unit 191 is removed from the transport vehicle 160. The attendant at the guard shack 130 can remove the I/G unit 191 from the transport vehicle when the transport vehicle 160 stops at the guard shack 130 prior to exiting the logistics yard 100. Because the I/G unit 191 is releasably attached to the transport vehicle 160, removing the I/G unit 191 is relatively easy. As described above, the removed I/G unit 191 may be recharged in the guard shack so that it is ready for further use upon entry of another transport vehicle 160 into the logistics yard 100.
The method 600 and embodiments thereof described above can be facilitated by the processor 301 of the remote controller 192 according to computer-executable instructions. Those skilled in the relevant art will appreciate that methods such as method 600 can be practiced with other computer system configurations, including Internet appliances, hand-held devices, wearable computers, cellular or mobile phones, multi-processor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, mini-computers, local servers, cloud-based servers and the like. Methods can be embodied in a special purpose computer or data processor that is specifically programmed, configured or constructed to perform one or more of the computer-executable instructions explained in detail herein. Indeed, the term “computer” (and like terms), as used generally herein, refers to any of the above devices, as well as any data processor or any device capable of communicating with a network, including consumer electronic goods such as game devices, cameras, or other electronic devices having a processor and other components, e.g., network communication circuitry.
The method 600 and embodiments thereof can also be practiced in distributed computing environments, where tasks or modules are performed by remote processing devices, which are linked through a communications network, such as a LAN, WAN or the Internet. In a distributed computing environment, program modules or sub-routines may be located in both local and remote memory storage devices. Aspects of the methods described herein may be stored or distributed on computer-readable media, including magnetic and optically readable and removable computer discs, stored as in chips (e.g., EEPROM or flash memory chips). Alternatively, aspects of the routine may be distributed electronically over the Internet or over other networks (including wireless networks). Those skilled in the relevant art will recognize that portions of the method may reside on a server computer, while corresponding portions reside on a client computer. Data structures and transmission of data particular to aspects of the method are also encompassed within the scope of the invention.
Embodiments of the systems and methods described herein can be integrated into other systems used for managing logistics yards. For example, U.S. patent application Ser. No. 16/109,603, titled VEHICLE GUIDANCE SYSTEMS AND ASSOCIATED METHODS OF USE AT LOGISTICS YARDS AND OTHER LOCATIONS, the entirety of which is incorporated herein by reference, may be integrated with embodiments of the system described herein to facilitate management and guidance of transport vehicles located within the logistics yard. Guidance systems such as those described in U.S. patent application Ser. No. 16/109,603 can include sensors located throughout the logistics yard. These sensors are configured to provide guidance information to vehicles moving about the logistics yard to thereby improve movement of transport vehicles and avoid collisions. The I/G units as described herein can communicate with such sensors to thereby provide additional information to the remote controller and/or portable communications device and further assist with maneuvering transport vehicles about the logistics yard. The I/G units attached to the transport vehicles as described herein can also be used to provide, for example, location information to systems such as those described in U.S. patent application Ser. No. 16/109,603. Where autonomous vehicles are used for maneuvering trailers as described in U.S. patent application Ser. No. 16/109,603, the I/G units described herein can provide geolocation information such that autonomous vehicles can locate trailers to be moved and maneuver the trailers based on the information collected by the I/G units. In some embodiments, the autonomous vehicle maneuvering a trailer having an I/G unit attached thereto includes a personal communication device as described herein, with the personal communication device serving as or incorporating an autonomous guidance package that is responsible for autonomous movement of the vehicle (and as described in greater detail in U.S. patent application Ser. No. 16/109,603). In such embodiments, information transmitted by the I/G unit and received by the personal communication device can be used by the autonomous guidance package, along with other information, as part of determining where to direct the autonomous vehicle.
From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention.
Claims
1. A unit configured to be releasably attached to a transport vehicle, the unit comprising:
- a transceiver;
- a positioning device configured to receive, via the transceiver, location data from an external positioning source and determine a transport vehicle location based on the location data;
- at least one sensor configured to detect a location device; and
- a processor operably connected to the positioning device, the at least one sensor, and the transceiver, the processor being programmed with computer readable instructions that, when executed, cause the processor to: receive the transport vehicle location from the positioning device; receive a location and an identity of the location device from the location device; and transmit, via the transceiver, the transport vehicle location, the location of the location device, and the identity of the location device to a central controller located remote from the transport vehicle.
2. The unit of claim 1, further comprising:
- a housing configured to house the positioning device and the processor; and
- an attachment mechanism configured to releasably attach the housing to the transport vehicle.
3. The unit of claim 2, wherein the attachment mechanism is configured to releasably attach the housing to a rear exterior surface of the transport vehicle.
4. The unit of claim 2, wherein the attachment mechanism includes a magnet.
5. The unit of claim 2, wherein the attachment mechanism is selected from the group consisting of an adhesive, a clip, a hook and loop fastener, and a strap.
6. The unit of claim 1, wherein the external positioning source is selected from the group consisting of satellites, cellular towers, WiFi networks, beacons, and terrestrial transmitters.
7. A unit configured to be releasably attached to a transport vehicle, the unit comprising:
- a transceiver;
- a positioning device configured to receive, via the transceiver, location data from an external positioning source and determine a transport vehicle location based on the location data;
- a camera configured to record video data, still image data, or both of a field of view proximate the transport vehicle;
- a processor operably connected to the positioning device, the camera, and the transceiver, wherein the processor is programmed with computer readable instructions that, when executed, cause the processor to: receive the transport vehicle location from the positioning device; receive at least one of the video data or the still image data from the camera; and transmit, via the transceiver, the transport vehicle location and at least one of the video data or the still image data to a central controller located remote from the transport vehicle.
8. The unit of claim 7, wherein the central controller is configured to transmit at least one of the video data or the still image data to a display device positioned in a cab of the transport vehicle.
9. The unit of claim 1, further comprising:
- at least one sensor configured to determine the proximity of an object to the unit;
- wherein the processor is further operatively connected to at least one sensor, and wherein the computer readable instructions, when executed, further cause the processor to: receive the proximity of the object from the at least one sensor; and transmit, via the transceiver, the proximity of the object to the remote central controller located remote from the transport vehicle.
10. The unit of claim 1, further comprising:
- at least one sensor configured to detect a location device;
- wherein the processor is further operatively connected to the at least one sensor, and wherein the computer readable instructions, when executed, further cause the processor to: receive a location and an identity of the location device from the location device; and transmit, via the transceiver, the location and identity to the central controller located remote from the transport vehicle.
11. A unit configured to be releasably coupled to a transport vehicle, the unit comprising:
- a transceiver;
- a positioning device configured to receive, via the transceiver, location data from an external positioning source and determine a transport vehicle location based on the location data;
- a processor operably connected to the positioning device and the transceiver, the processor being programmed with computer readable instructions that, when executed, cause the processor to: receive the transport vehicle location from the positioning device; and transmit, via the transceiver, the transport vehicle location to a central controller located remote from the transport vehicle;
- a housing configured to house the positioning device and the processor;
- an attachment mechanism configured to releasably attach the housing to the transport vehicle; and
- a unique identifier located on a surface of the housing, wherein the unique identifier is selected from the group consisting of a QR code, a bar code, and an alphanumeric code.
12. A unit configured to be releasably coupled to a transport vehicle, the unit comprising:
- a transceiver;
- a positioning device configured to receive, via the transceiver, location data from an external positioning source and determine a transport vehicle location based on the location data;
- a processor operably connected to the positioning device and the transceiver, the processor being programmed with computer readable instructions that, when executed, cause the processor to: receive the transport vehicle location from the positioning device; and transmit, via the transceiver, the transport vehicle location to a central controller located remote from the transport vehicle; and
- a rechargeable battery configured to supply power to the positioning device, the transceiver and the processor, wherein the unit is configured to operate in a low power mode or a full power mode based on the transport vehicle location.
13. The unit of claim 1, further comprising:
- a rechargeable battery configured to supply power to the positioning device, the transceiver and the processor, wherein the unit is configured to operate in a low power mode or a full power mode based an instruction received from the central controller.
14. A unit configured to be releasably coupled to a transport vehicle, the unit comprising:
- a transceiver;
- a positioning device configured to receive, via the transceiver, location data from an external positioning source and determine a transport vehicle location based on the location data;
- a camera configured to record video data, still image data, or both of a field of view proximate the transport vehicle; and
- at least one sensor configured to determine the proximity of an object to the unit or to detect a location device;
- a processor operably connected to the positioning device, the camera, the at least one sensor, and the transceiver, the processor being programmed with computer readable instructions that, when executed, cause the processor to: receive the transport vehicle location from the positioning device; and transmit, via the transceiver, the transport vehicle location to a central controller located remote from the transport vehicle; and
- a rechargeable battery configured to supply power to the positioning device, the camera, the at least one sensor, the transceiver, and the processor, wherein the unit is configured to operate in a low power mode or a full power mode based an instruction received from the central controller;
- wherein in the low power mode, the rechargeable battery provides power to the positioning device but not to the camera or the at least one sensor, and in the full power mode the rechargeable battery provides power to at least the positioning device, the camera, and the at least one sensor.
15. A method for changing a power mode of a transport vehicle identification and guidance unit attached to a transport vehicle located in a loading dock yard, the method comprising:
- determining, via a positioning device on the transport vehicle identification and guidance unit, a location of the transport vehicle within the loading dock yard;
- automatically adjusting the power mode of the transport vehicle identification and guidance unit to a low power mode when the location of the transport vehicle is determined to be within a first area of the loading dock yard; and
- automatically adjusting the power mode of the transport vehicle identification and guidance unit to a full power mode when the location of the transport vehicle is determined to be within a second area of the loading dock yard.
16. The method of claim 15, wherein the vehicle identification and guidance unit includes:
- a camera configured to record video data, still image data, or both of a field of view proximate the transport vehicle;
- at least one sensor configured to determine the proximity of an object to the unit; and a battery configured to provide power to the positioning device, the camera, and the at least one sensor;
- and wherein, in the low power mode, the battery provides power to the positioning device but not the camera or the at least one sensor; and
- in the full power mode, the battery provides power to at least the positioning device, the camera, and the at least one sensor.
17. The method of claim 15, wherein the first area is a parking area in the loading dock yard.
18. The method of claim 15, wherein the second area is a loading dock station in the loading dock yard.
19. A method of operating a transport vehicle within a logistics yard, the method comprising:
- attaching a transport vehicle identification and guidance unit to an external surface of the transport vehicle when the transport vehicle enters the logistics yard, wherein, as the transport vehicle moves within the logistics yard, the transport vehicle identification and guidance unit transmits locations of the transport vehicle to a remote controller located remote from the transport vehicle; and
- removing the transport vehicle identification and guidance unit from the transport vehicle when the transport vehicle exits the logistics yard.
20. The method of claim 19, wherein attaching the transport vehicle identification and guidance unit to the external surface of the transport vehicle further comprises:
- inputting a first unique identifier into the remote controller, wherein the first unique identifier is associated with the transport vehicle identification and guidance unit;
- inputting a second unique identifier into the remote controller, wherein the second unique identifier is associated with the transport vehicle; and
- associating the first unique identifier with the second unique identifier at the remote controller such that location data transmitted by the identification and guidance unit to the remote controller is associated with the transport vehicle.
21. The method of claim 19, wherein the transport vehicle identification and guidance unit is releasably attached to a rear external surface of the transport vehicle.
| 1775909 | September 1930 | Mikkelsen |
| 2362981 | November 1944 | Philemon |
| 2883182 | April 1959 | William |
| 2887865 | May 1959 | Moler |
| 3051014 | August 1962 | Houk |
| 3439728 | April 1969 | Martini |
| 3630557 | December 1971 | Pierce et al. |
| 3635277 | January 1972 | Bahnsen |
| 3813119 | May 1974 | Panici |
| 3894571 | July 1975 | Hinchliff |
| 4009051 | February 22, 1977 | Kazis et al. |
| 4010571 | March 8, 1977 | Mcguire et al. |
| 4147073 | April 3, 1979 | Mercier |
| 4286911 | September 1, 1981 | Benjamin |
| 4476853 | October 16, 1984 | Arbogast |
| 4590118 | May 20, 1986 | Yatabe et al. |
| 4625456 | December 2, 1986 | Lafontaine |
| 4626983 | December 2, 1986 | Harada et al. |
| 4661758 | April 28, 1987 | Whittaker |
| 4744121 | May 17, 1988 | Swessel et al. |
| 4821456 | April 18, 1989 | Nogaki |
| 4843373 | June 27, 1989 | Trickle et al. |
| 4860813 | August 29, 1989 | Ballyns et al. |
| 4878529 | November 7, 1989 | Hormann |
| 4936731 | June 26, 1990 | Noble |
| 4988254 | January 29, 1991 | Alexander |
| 5026242 | June 25, 1991 | Alexander |
| 5047748 | September 10, 1991 | Trickle |
| 5056847 | October 15, 1991 | Stillwell et al. |
| 5085094 | February 4, 1992 | Clawson et al. |
| 5168262 | December 1, 1992 | Okayama |
| 5168267 | December 1, 1992 | Trickle |
| 5181401 | January 26, 1993 | Hodan |
| 5196965 | March 23, 1993 | Lang et al. |
| 5277240 | January 11, 1994 | Epema et al. |
| 5323098 | June 21, 1994 | Hamaguchi et al. |
| 5403142 | April 4, 1995 | Stewart |
| 5495102 | February 27, 1996 | Fine |
| 5544924 | August 13, 1996 | Paster |
| 5576533 | November 19, 1996 | Tantraporn |
| 5775107 | July 7, 1998 | Sparkman |
| 5831540 | November 3, 1998 | Sullivan et al. |
| 5886863 | March 23, 1999 | Nagasaki et al. |
| 5886883 | March 23, 1999 | Rail |
| 5898585 | April 27, 1999 | Sirichote et al. |
| 5915446 | June 29, 1999 | De |
| 6082952 | July 4, 2000 | Alexander |
| 6125582 | October 3, 2000 | Mondragon et al. |
| 6134835 | October 24, 2000 | Krupke et al. |
| 6179036 | January 30, 2001 | Harvey |
| 6276744 | August 21, 2001 | Huber et al. |
| 6367259 | April 9, 2002 | Timm |
| 6369462 | April 9, 2002 | Siri |
| 6390245 | May 21, 2002 | Metz |
| 6442897 | September 3, 2002 | Mullet |
| 6476572 | November 5, 2002 | Lounsbury |
| 6523823 | February 25, 2003 | Bakoledis |
| 6543375 | April 8, 2003 | Sargent et al. |
| 6663527 | December 16, 2003 | Phelan et al. |
| 6781516 | August 24, 2004 | Reynard et al. |
| 6787259 | September 7, 2004 | Colborn et al. |
| 6810817 | November 2, 2004 | James |
| 6812849 | November 2, 2004 | Ancel |
| 6917298 | July 12, 2005 | Romano et al. |
| 6972226 | December 6, 2005 | Deppe et al. |
| 6975226 | December 13, 2005 | Reynard et al. |
| 7032720 | April 25, 2006 | Jette et al. |
| 7045764 | May 16, 2006 | Beggs et al. |
| 7119673 | October 10, 2006 | Eager et al. |
| 7162762 | January 16, 2007 | Gleason |
| 7165486 | January 23, 2007 | Alexander et al. |
| 7230819 | June 12, 2007 | Muchow et al. |
| 7254868 | August 14, 2007 | Mullet et al. |
| 7256703 | August 14, 2007 | Duvernell et al. |
| 7264092 | September 4, 2007 | Jette |
| 7274300 | September 25, 2007 | Duvernell et al. |
| 7327107 | February 5, 2008 | Mullet et al. |
| 7333016 | February 19, 2008 | Ancel |
| 7380375 | June 3, 2008 | Maly |
| 7686061 | March 30, 2010 | Mullet et al. |
| 7730981 | June 8, 2010 | Mccabe et al. |
| 7750890 | July 6, 2010 | Fitzgibbon et al. |
| 7864030 | January 4, 2011 | Jette |
| 7956718 | June 7, 2011 | Murphy et al. |
| 8058970 | November 15, 2011 | Mullet et al. |
| 8065770 | November 29, 2011 | Proffitt et al. |
| 8112949 | February 14, 2012 | Eungard |
| 8181401 | May 22, 2012 | Eungard |
| 8286757 | October 16, 2012 | Nelson |
| 8307589 | November 13, 2012 | Eungard |
| 8307956 | November 13, 2012 | Andersen et al. |
| 8345010 | January 1, 2013 | Fitzgibbon et al. |
| 8364334 | January 29, 2013 | Au et al. |
| 8407842 | April 2, 2013 | Story et al. |
| 8410895 | April 2, 2013 | Murphy et al. |
| 8421611 | April 16, 2013 | Coshow et al. |
| 8490669 | July 23, 2013 | Fletcher et al. |
| 8497761 | July 30, 2013 | Mcneill et al. |
| 8510888 | August 20, 2013 | Eungard |
| 8528622 | September 10, 2013 | Ehrlich |
| 8547234 | October 1, 2013 | Maly et al. |
| 8590087 | November 26, 2013 | Swessel et al. |
| 8590674 | November 26, 2013 | Jette |
| 8775710 | July 8, 2014 | Miller et al. |
| 8893764 | November 25, 2014 | Mascari et al. |
| 8959838 | February 24, 2015 | Marinelli |
| 8976006 | March 10, 2015 | Krupke et al. |
| 8978562 | March 17, 2015 | Nagamine et al. |
| 9211889 | December 15, 2015 | Hoetzer et al. |
| 9230419 | January 5, 2016 | Beggs et al. |
| 9274522 | March 1, 2016 | Boos et al. |
| 9283935 | March 15, 2016 | Fujioka |
| 9487984 | November 8, 2016 | Wachtell et al. |
| 9517902 | December 13, 2016 | Harrington |
| 9564072 | February 7, 2017 | Senfleben et al. |
| 9623859 | April 18, 2017 | Lavoie et al. |
| 9633537 | April 25, 2017 | Beggs et al. |
| 9656691 | May 23, 2017 | Heimberger et al. |
| 9771225 | September 26, 2017 | Stone et al. |
| 9776511 | October 3, 2017 | Brooks et al. |
| 9777529 | October 3, 2017 | Mcneill et al. |
| 9926148 | March 27, 2018 | Hochstein et al. |
| 9957121 | May 1, 2018 | Sveum et al. |
| 10032380 | July 24, 2018 | Mushynski et al. |
| 10053904 | August 21, 2018 | Mcneill et al. |
| 10081504 | September 25, 2018 | Walford et al. |
| 10096187 | October 9, 2018 | Deneen et al. |
| 10106342 | October 23, 2018 | Avalos |
| 10227190 | March 12, 2019 | Brooks et al. |
| 10358858 | July 23, 2019 | Lietz et al. |
| 10435936 | October 8, 2019 | Lietz et al. |
| 10494205 | December 3, 2019 | Hoofard et al. |
| 10878386 | December 29, 2020 | Hoofard et al. |
| 10947069 | March 16, 2021 | Brooks et al. |
| 11124372 | September 21, 2021 | Hoofard et al. |
| 11142413 | October 12, 2021 | Hoofard et al. |
| 11225824 | January 18, 2022 | Hoofard et al. |
| 11256264 | February 22, 2022 | Hoofard et al. |
| 11262747 | March 1, 2022 | Hoofard et al. |
| 11305953 | April 19, 2022 | Hoofard et al. |
| 11358813 | June 14, 2022 | Walford et al. |
| 11507926 | November 22, 2022 | Hoofard et al. |
| 20010035667 | November 1, 2001 | Gaeta |
| 20020089427 | July 11, 2002 | Aratani et al. |
| 20030167238 | September 4, 2003 | Zeif et al. |
| 20040146384 | July 29, 2004 | Whelan |
| 20040182619 | September 23, 2004 | Mcgregor et al. |
| 20050050438 | March 3, 2005 | Cheung et al. |
| 20050102041 | May 12, 2005 | Duvernell et al. |
| 20050102042 | May 12, 2005 | Reynard et al. |
| 20050126081 | June 16, 2005 | Patel et al. |
| 20050262549 | November 24, 2005 | Ritt et al. |
| 20060119132 | June 8, 2006 | Rivers et al. |
| 20060137261 | June 29, 2006 | Maly |
| 20060145853 | July 6, 2006 | Richards et al. |
| 20060158752 | July 20, 2006 | Perkes |
| 20060181391 | August 17, 2006 | Mcneill et al. |
| 20060235737 | October 19, 2006 | Fleurant et al. |
| 20060289128 | December 28, 2006 | Ressel et al. |
| 20070062422 | March 22, 2007 | Wotring |
| 20070157614 | July 12, 2007 | Goldman |
| 20070256797 | November 8, 2007 | Orton et al. |
| 20070258798 | November 8, 2007 | Foster et al. |
| 20070283806 | December 13, 2007 | Morrison |
| 20080011799 | January 17, 2008 | Chang |
| 20080018438 | January 24, 2008 | Ehrlich et al. |
| 20080022596 | January 31, 2008 | Boerger et al. |
| 20080124203 | May 29, 2008 | Mcdonald |
| 20080127435 | June 5, 2008 | Maly et al. |
| 20080143290 | June 19, 2008 | Chavakula |
| 20090013497 | January 15, 2009 | Squyres et al. |
| 20090024979 | January 22, 2009 | Chessell et al. |
| 20100073197 | March 25, 2010 | Eagleton |
| 20100146719 | June 17, 2010 | Swessel et al. |
| 20100289623 | November 18, 2010 | Roesner |
| 20110075441 | March 31, 2011 | Swessel et al. |
| 20110203059 | August 25, 2011 | Whitley et al. |
| 20110313893 | December 22, 2011 | Weik |
| 20120025964 | February 2, 2012 | Beggs et al. |
| 20120125545 | May 24, 2012 | Ehrlich |
| 20120304558 | December 6, 2012 | Iglesias et al. |
| 20130024334 | January 24, 2013 | Kozlay |
| 20130038731 | February 14, 2013 | Brey et al. |
| 20130117078 | May 9, 2013 | Weik et al. |
| 20130188050 | July 25, 2013 | Winget |
| 20130261958 | October 3, 2013 | Herron |
| 20130312205 | November 28, 2013 | Riviere et al. |
| 20130327914 | December 12, 2013 | Mcneill et al. |
| 20130332217 | December 12, 2013 | Mcneill et al. |
| 20140075842 | March 20, 2014 | Mcneill et al. |
| 20140137447 | May 22, 2014 | Mama |
| 20140222971 | August 7, 2014 | Cooper et al. |
| 20140225509 | August 14, 2014 | Wiegel et al. |
| 20140247347 | September 4, 2014 | Mcneill et al. |
| 20140251556 | September 11, 2014 | Orton |
| 20150009046 | January 8, 2015 | Senfleben et al. |
| 20150013083 | January 15, 2015 | Palmersheim |
| 20150039552 | February 5, 2015 | Moyne |
| 20150047132 | February 19, 2015 | Sveum et al. |
| 20150047133 | February 19, 2015 | Sveum |
| 20150294166 | October 15, 2015 | Kuehnle et al. |
| 20150308175 | October 29, 2015 | Wachtell et al. |
| 20160075526 | March 17, 2016 | Avalos |
| 20160090072 | March 31, 2016 | Eppley et al. |
| 20160104364 | April 14, 2016 | Brooks et al. |
| 20160031482 | February 4, 2016 | Lavoie |
| 20160178382 | June 23, 2016 | Penna et al. |
| 20160288833 | October 6, 2016 | Heimberger et al. |
| 20160362135 | December 15, 2016 | Xu et al. |
| 20160368489 | December 22, 2016 | Aich |
| 20160369619 | December 22, 2016 | Parmeshwar et al. |
| 20170017392 | January 19, 2017 | Castaneda et al. |
| 20170043967 | February 16, 2017 | Walford et al. |
| 20170044817 | February 16, 2017 | Mcneill et al. |
| 20170073005 | March 16, 2017 | Jawad et al. |
| 20170106794 | April 20, 2017 | Constantine |
| 20170120734 | May 4, 2017 | Westerdale |
| 20170168501 | June 15, 2017 | Aoki et al. |
| 20170174209 | June 22, 2017 | Lavoie |
| 20170205824 | July 20, 2017 | Nordbruch et al. |
| 20170213404 | July 27, 2017 | Sivalingam et al. |
| 20170320685 | November 9, 2017 | Hoofard et al. |
| 20180035606 | February 8, 2018 | Burdoucci |
| 20180278897 | September 27, 2018 | Seaman et al. |
| 20180346029 | December 6, 2018 | Kabos et al. |
| 20190002216 | January 3, 2019 | Walford et al. |
| 20190039425 | February 7, 2019 | Dodd et al. |
| 20190056736 | February 21, 2019 | Wood et al. |
| 20190064835 | February 28, 2019 | Hoofard et al. |
| 20190144218 | May 16, 2019 | Hoofard et al. |
| 20190187716 | June 20, 2019 | Cantrell et al. |
| 20190197318 | June 27, 2019 | Krishnamurthy et al. |
| 20190202646 | July 4, 2019 | Brooks et al. |
| 20190226239 | July 25, 2019 | Trentham et al. |
| 20190301224 | October 3, 2019 | Barton |
| 20190302764 | October 3, 2019 | Smith et al. |
| 20190316403 | October 17, 2019 | Aiello |
| 20190392402 | December 26, 2019 | Vandergon et al. |
| 20200002993 | January 2, 2020 | Thouin |
| 20200018110 | January 16, 2020 | Lindley et al. |
| 20200087970 | March 19, 2020 | Nielson et al. |
| 20200115948 | April 16, 2020 | Lietz et al. |
| 20200125074 | April 23, 2020 | Ramos et al. |
| 20200133259 | April 30, 2020 | Van Wiemeersch |
| 20200239242 | July 30, 2020 | Hoofard et al. |
| 20200273133 | August 27, 2020 | Morris |
| 20200334631 | October 22, 2020 | Conlon |
| 20200393828 | December 17, 2020 | Hoofard et al. |
| 20210079710 | March 18, 2021 | Evans et al. |
| 20210238908 | August 5, 2021 | Ramage et al. |
| 20220243524 | August 4, 2022 | Hoofard et al. |
| 20220306410 | September 29, 2022 | Hoofard et al. |
| 20220338719 | October 27, 2022 | Walford et al. |
| 20220388380 | December 8, 2022 | Hoofard et al. |
| 20230003074 | January 5, 2023 | Hoofard et al. |
| 2005100075 | April 2005 | AU |
| 2963656 | November 2017 | CA |
| 3067610 | July 2020 | CA |
| 2075169 | April 1991 | CN |
| 101716959 | June 2010 | CN |
| 103485613 | June 2015 | CN |
| 19836432 | March 1999 | DE |
| 202005008059 | November 2005 | DE |
| 102004037933 | February 2006 | DE |
| 202004016760 | March 2006 | DE |
| 102006014153 | October 2007 | DE |
| 202013008638 | November 2013 | DE |
| 0729856 | September 1996 | EP |
| 2215612 | August 2012 | EP |
| 2660170 | November 2013 | EP |
| 2692561 | February 2014 | EP |
| 933292 | April 1948 | FR |
| 2797246 | February 2001 | FR |
| 2869470 | October 2005 | FR |
| 1527046 | October 1978 | GB |
| 8902808 | June 1991 | NL |
| 2005045169 | May 2005 | WO |
| 2006066013 | June 2006 | WO |
| 2006076538 | July 2006 | WO |
| 2008014026 | January 2008 | WO |
| 2008014206 | January 2008 | WO |
| 2008036087 | March 2008 | WO |
| 2009070509 | June 2009 | WO |
| 2010077977 | July 2010 | WO |
| 2011037839 | March 2011 | WO |
| 2015023666 | February 2015 | WO |
| 2015023669 | February 2015 | WO |
| 2015084167 | June 2015 | WO |
| 2015166339 | November 2015 | WO |
| 2016007321 | January 2016 | WO |
| 2016209141 | December 2016 | WO |
| 2017100716 | June 2017 | WO |
| 2019090199 | May 2019 | WO |
| 2019173811 | September 2019 | WO |
| 2019209773 | October 2019 | WO |
| 2020156936 | August 2020 | WO |
- Dock Lighting Goes Green with the FT Ultra LED Docklight:, APS Resource, News Release. 1 page.
- Pentalift introduces industry's first solar powered dock leveler! www.pentalift.com, Jun. 14, 2011, 1 page.
- APS&GO—LED Communication System Specification Sheet, APS Resource, For APS1102, Nov. 2009, 2 pages.
- Bin et al., Constrained Model Predictive Control for Backing-up Tractor-Trailer System, Proceeding of the 10th World Congress on Intelligent Control and Automation, Jul. 6-8, 2012, Beijing, China, pp. 2165-2170.
- Desantis et al., Path-Tracking for Tractor-Trailers with Hitching of Both the On-Axle and the Off-Axle Kind, Proceedings of the 2002 IEEE International Symposium on Intelligent Control, 2002.
- Energy Saving Products Brochure, APS Resource, Mar. 2009, 4 pages.
- FT Ultra LED Flex Arm Docklight Specification Sheet, APS Resource, Form APS 1168, Nov. 2009, 2 pages.
- Fuchs C et al: “3D pose estimation for articulated vehicles using Kalman-filter based tracking”, Pattern Ricognition. Image Analysis, Allen Press, Lawrence, KS, US, vol. 26, No. 1, Jul. 23, 2016 (Jul. 23, 2016), pp. 109-113.
- High Impact LED Dock Light Specification Sheet, APS Resource, Form APS1171, Nov. 2009, 2 pages.
- Kelley Company; product brochure; 2008; 8 pages.
- Kelley Company; Vehicle Restraints brochure; 2008 ; 8 pages.
- Manual and Automatic Light Communication Systems, User's Manual, Serco, Oct. 2009, 28 pages.
- McGovern et al., An Articulated Truck on a Spreadsheet, Level 3, Issue 1, Nov. 2003, 23 pages.
- Model G307K2 Kadet 2 Operator Interface with 7″ TFT Display, Red Lion Controls, Inc., Nov. 23, 2015, 4 pages.
- Oreh et al., A New Method for Directional Control of a Tractor Semi-Trailer, Australian Journal of Basic and Applied Sciences, 6(12): 369-409, 2012.
- Rite-Hite Corporation, Rite-Vu Light Communication Systems Brochure, 6 pages [Not dated].
- Safety & Lighting Products Brochure, APS Resource, Sep. 2004, 2 pages.
- Serco Vehicle Restraints brochure; 2008; 4 pages.
- Serco; Loading Dock Solutions brochure; 2008; 8 pages.
- Smart Power Systems International GmbH, Web pages for Hybrid DC/AC Power Supply, Jun. 1, 2004.
- Tofael Ahamed: “Navigation of an Autonomous Tractor Using Multipìe Sensors”, Thesis, Feb. 22, 2008 (Feb. 22, 2008), XP055527539, retrieved from the Internet URL: https ://tsukuba.repo.nii.ac,jp, [retrieved õn Nov. 27, 2018], Chapter 9.
Type: Grant
Filed: Jan 24, 2022
Date of Patent: Oct 31, 2023
Patent Publication Number: 20220146269
Assignee: ASSA ABLOY Entrance Systems AB (Landskrona)
Inventors: Richard K. Hoofard (Dallas, TX), Daryl Day (Frisco, TX)
Primary Examiner: Muhammad Shafi
Application Number: 17/582,944
International Classification: G05D 1/00 (20060101); H04W 4/40 (20180101); G07C 5/00 (20060101); H04W 4/029 (20180101); B60R 1/22 (20220101); G06V 20/56 (20220101); B60R 11/00 (20060101); G01C 21/34 (20060101); G06Q 50/30 (20120101); H04N 5/77 (20060101); H04N 7/18 (20060101); H04N 23/51 (20230101); H04N 23/65 (20230101); H01M 10/0525 (20100101);
