DIRECT TRUCK ASSIGNMENT SYSTEM

Abstract

A direct truck assignment system, device and method that allows for efficient assignment of a driven or autonomous vehicle from amongst a group of available, unassigned delivery vehicles within a container loading area, and arranging the assignment and transportation of a container directly with the selected vehicle, eliminating the need for prior matching and assignment before the truck(s) arrive at the container loading area or the need for a third party intermediary in the delivery assignment and vehicle engagement processes.

Claims

1. A method of directly assigning trucks to each transport a container comprising: determining, by a controller, characteristics of a plurality of trucks and/or an operator of each truck; allowing or providing an indication to allow, by the controller, each respective truck to access a container terminal if the determined characteristics for the respective truck satisfy one or more predetermined conditions; directing the trucks within the container terminal to join a queue; dynamically assigning a respective container to each truck in the queue in sequential order within the queue; and providing each truck assigned with a respective container with container and/or delivery information associated with the container.

2. The method according to claim 1, wherein the delivery information comprises a final destination of the container.

3. The method according to claim 1, further comprising: receiving a selected delivery preference area from each truck and/or each operator of each truck; and wherein the directing the trucks within the container terminal to join a queue is based on the received selected preference area.

4. The method according to claim 3, wherein the selected preference area is a local area, a regional area or a long-haul area.

5. The method according to claim 3, wherein the selected preference area comprises a driving distance or a range of driving distance.

6. The method according to claim 3, wherein the container terminal comprises a plurality of truck queues, and wherein the queue each respective truck is directed to corresponds to the received selected preference area.

7. The method according to claim 6, wherein each queue of the plurality of truck queues is associated with a different grouping of containers within the container terminal, and wherein each container of each respective grouping of containers has a final destination within a common driving distance range.

8. The method according to claim 1, wherein each truck of the plurality of trucks that enters the container terminal has not been assigned to a container or delivery address for transport prior to entering the container terminal.

9. The method according to claim 1, wherein the determining, by the controller, the characteristics of the plurality of trucks and/or the operator of each truck comprises interrogating a respective transponder of each truck of the plurality of trucks.

10. The method according to claim 9, wherein the characteristics comprise a loading system of the truck registration status, vehicle registration status, insurance status, and/or operator background check status.

11. The method according to claim 1, wherein the plurality of trucks are driven trucks.

12. The method according to claim 1, wherein the plurality of trucks are autonomous driving vehicles.

13. A direct truck assignment system comprising: a transponder configured to be associated with a truck; a beacon interrogator configured to be associated with a container terminal; a controller configured to communicate with the beacon interrogator and/or control the beacon interrogator; wherein the controller is configured to instruct the beacon interrogator to interrogate the transponder to determine characteristics of the truck and/or an operator of the truck transmitted by the transponder; wherein, based on the determined characteristics, the controller is configured to allow access to the container terminal and/or generate an indication that access is allowed.

14. The direct truck assignment system according to claim 13, wherein the controller is configured to provide container and/or delivery information to the truck in a queue based on a container assigned to the truck after the controller allows access and/or generates the indication that access is allowed.

15. A direct truck assignment system comprising: a plurality of transponders, each transponder of the plurality of transponders associated with a respective vehicle; a beacon interrogator associated with a container terminal; a controller configured to communicate with the beacon interrogator and/or control the beacon interrogator; wherein the controller is configured to instruct the beacon interrogator to interrogate each transponder of the plurality of transponders that move through an entry point of the container terminal to determine characteristics of each respective vehicle and/or an operator of each respective vehicle transmitted by the respective transponder; wherein, based on the determined characteristics, the controller is configured to allow access to the container terminal and/or generate an indication that access is allowed for each respective vehicle.

16. The direct truck assignment system according to claim 15, wherein the controller is configured to provide container and/or delivery information to each vehicle in a queue based on a container assigned to the vehicle after the controller allows access and/or generates the indication that access is allowed for the respective vehicle.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The foregoing summary, as well as the following detailed description, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, exemplary embodiments are shown in the drawings, it being understood, however, that the present application is not limited to the specific embodiments disclosed in the drawings:

[0034] FIG. 1 shows an exemplary Direct Vehicle Engagement System (DVES) in accordance with the present disclosure.

[0035] FIG. 2 is an exemplary representation of the screen of a user mobile device illustrating use of the DVES in accordance with the present disclosure.

[0036] FIG. 3 is another exemplary representation of the screen of a user mobile device illustrating additional use of the DVES in accordance with the present disclosure.

[0037] FIG. 4 is an exemplary flow diagram describing operation of the DVES in an “Ad-hoc” Mode in accordance with the present disclosure.

[0038] FIG. 5 shows an alternate set-up of the DVES in accordance with the present disclosure.

[0039] FIG. 6 is an exemplary flow diagram describing operation of the DVES in a “Queue” Mode in accordance with the present disclosure.

[0040] FIG. 7 shows a schematic representation of an exemplary Direct Truck Assignment System (DTAS) associated with a container terminal in accordance with the present disclosure.

[0041] FIG. 8 shows an exemplary flow diagram describing operation of a DTAS in accordance with the present disclosure.

DETAILED DESCRIPTION

[0042] Before the various exemplary embodiments are described in further detail, it is to be understood that the present invention is not limited to the particular embodiments described. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the claims of the present application.

[0043] In the drawings, like reference numerals refer to like features of the systems and methods of the present disclosure. Accordingly, although certain descriptions may refer only to certain figures and reference numerals, it should be understood that such descriptions might be equally applicable to like reference numerals in other figures.

[0044] The present disclosure provides a Direct Vehicle Engagement System (DVES), designated as reference numeral 10, that allows a user of a handheld device that is running a DVES application to randomly select (or arbitrarily select) any available “for-hire” vehicle, either operating by itself, or co-located within a group of other for-hire vehicles within a select area, and extemporaneously engage and directly set up an trip with an available vehicle of interest without having to engage a ride-hail service to create the trip. The “select area” may be a visually perceptible area, an area within a selected physical distance from the user, or an area within a selected device communication distance from the user. The DVES 10 and method provides two general variations: an “Ad-hoc” Mode, and a “Queue” Mode. With the “Ad-hoc” Mode, generally illustrated in FIG. 1, a user 12 that wishes to engage the services of a ride-hail vehicle 14 could utilize the DVES 10 to self-identify and self-engage available, unassigned vehicles 14 located within the selected area or range of the user 12. With the “Queue” Mode shown in FIG. 5, a user 12 could utilize the DVES 10 to identify, select, confirm, and engage a desired available, unassigned vehicle 14 either pre-positioned in a designated area or in a formal “next-up” line, analogous to a traditional taxi-cab stand or “queue”. Any engagement of a vehicle 14 according to either Mode would occur in real-time and would not require the user 12 to go through a Central Operations Center or a third-party intermediary to have a vehicle 14 assigned to a trip request.

[0045] Referring to FIG. 1, an exemplary embodiment of the DVES 10 is shown. In this embodiment, a user 12 is shown at a street corner using a mobile device 16 to identify and engage available, unassigned vehicle(s) 14 in general visual proximity to the user 12. As illustrated, the user 12 generally has a user mobile device 16, such as a cellphone, smart phone, tablet device, or the like, with which the user can access a DVES application 18 to identify available, unassigned vehicles 14 within a visual geographic proximity to the user 12. For illustration purposes, FIG. 1 shows vehicles 14a, 14b and 14c, of which vehicles 14a and 14b are currently available (as designated by a check mark) and unassigned, while vehicle 14c is unavailable (as designated by an “X”).

[0046] In the “Ad-hoc” Mode of the system 10, an exemplary embodiment of which is shown in the flow diagram of FIG. 4, the user 12 first accesses the DVES application 18 on the user mobile device 16 (Block 100). In accordance with preferred embodiments, the camera of the user mobile device 16 is activated and provides a video overview of the nearby vehicles 14 in the application's “search” mode Block 110). In preferred embodiments, the DVES application 18 defaults immediately to search for and visually highlight and/or annotate all available, unassigned vehicles 14 located within a geographical area proximate to the user 12 (Block 120). In embodiments of the DVES application 18, by pointing the user mobile device 16 in various directions, the user 12 can select the geographical area to be searched within visual range. In the “search” mode of the DVES application 18, the camera looks for, and identifies, any and all available, unassigned vehicles 14 within the geographic proximity to the user's location. All “available” for-hire vehicles 14 are displayed and differentiated on the screen or display 20 of the user mobile device 16 (Block 120). The mobile device 16 could be configured to dynamically display a video on the display 20 based on detections by the camera. Thus, the mobile device 16 could be configured to highlight and/or annotate the vehicles 14 on the display 20 based on the availability status signal.

[0047] Additional information details regarding the vehicle(s) 14 could be provided on the screen 20, for example, in accordance with such vehicle information provided by the vehicle 14 along with the availability signal. Based on such additional provided information, the user 12 could input conditional trip parameters, and the DVES application 18 would then either “grey-out” (or disregard) those vehicles that do not comply with the desired characteristics, or display those vehicles that match preselected parameters with highlighting or other visual augmentation amongst those vehicles 14 originally designated as being “available”. Even if some initial filtering was already selected (e.g., by range) with symbols such as “$”, “$$”, and “$$$” appearing above the available vehicles, even within a screen already filtered for some criteria, the symbols would further allow a user with their selection process to “post filter” the displayed vehicles by factoring individual prices, etc. into the selection process. Further, by using different highlighting colors, for example, the user could further make a selection based on type of vehicle service, e.g., Uber, Lyft, Taxicab, etc.

[0048] In accordance with embodiments of the present disclosure, each vehicle 14 includes a DVES beacon 22 (or emitter or signaling beacon) which transmits an availability status signal. Each beacon 22 may include a housing(s), lens(es), emitter(s), shield(s), heater(s), receiver(s) and necessary circuitry for transmitting/receiving signals. In some embodiments, the beacon 22 comprises the receiver(s). In some embodiments, the receiver(s) is standalone or separate from the beacon 22. The signal transmitted by the beacons 22 may be constantly (or substantially constantly) transmitted, regardless of whether the vehicle 14 is available or unassigned. Such signals are preferably transmitted by digitally modulated infra-red or other spectral emissions and optionally through a fixed visible indication (such as a red or green light which appears to be steadily on, but in reality is digitally modulated too fast for the eye to perceive). The DVES application 18 searches for any and all vehicles 14 that are actively transmitting a digitally modulated infra-red or visible “I am available” signal. When the DVES application 18 senses (or detects) one or more vehicles 14 with this signal, the application 18 may either highlight those vehicles on the screen 20 of the user mobile device 16 and/or annotate all such vehicles 14 that are transmitting this signal status (i.e., “available” vehicles), and/or grey-out those vehicles 14 that are not transmitting this availability code (i.e., “unavailable” vehicles). The DVES application 18 could also be capable of providing additional visual, audible, and/or haptic alerts indicating the availability status of each vehicle 14 within the geographic proximity to the user 12 (such as, superimposing visual graphics on the screen 20 that point with visually augmented arrows 24 or the like to each vehicle 14 that is transmitting this signal and is therefore “available” for selection and trip engagement). This identification process is preferably dynamic, and as any new vehicles 14 with this signal becomes available, they are instantly (or substantially instantly) automatically added to user mobile device's screen 20 or augmented display along with optionally sounding an audible signal, while conversely each vehicle 14 that becomes assigned or otherwise stops transmitting the “availability” code will have its availability status altered and have its augmentation graphical treatment removed from the search/identification display process.

[0049] Referring to FIG. 1, the user 12 receives signals from the vehicles 14a and 14b indicating that they are available for selection and engagement. However, the vehicle 14c transmits a signal to the user indicating that the vehicle 14c is currently unavailable. This information can be displayed on the screen 20 of the user mobile device 16, as shown in FIG. 2. As soon as the vehicle 14c becomes available — for example, an engaged passenger reaches his or her destination and leaves vehicle 14c — the signal transmitted to user 12 immediately (or substantially immediately) would change to an “I am available” signal. Similarly, if vehicle 14b is selected and engaged by another user 12b, then the signal transmitted from vehicle 14b immediately (or substantially immediately) would change to an “unavailable” signal, and the user mobile device 16 would be alerted to such a change and the user 12 cannot select the now-assigned vehicle 14b.

[0050] In the basic embodiment of the “search” mode, the user 12 could be provided with a search screen 20 showing all available vehicles 14 (Block 120). In some embodiments, as noted above, the user 12 may select different “filtered” trip conditions or parameters that narrow the display on the screen 20 to show, for example, only those highlighted or annotated vehicles 14 that meet a desired selected trip condition or parameter(s). For example, a user 12 can filter the “search” to show just those vehicles 14 within the proximity with an available travel range ability of greater than “x” miles, or only vehicles 14 with “x” number of seats, or only vehicles 14 with a certain seating layout, or only vehicles 14 with special equipment such as for handicapped persons, or just those vehicles that are from specific categories (i.e. just taxicabs, or just private vehicles, etc.). In use, the user 12 would select desired filter parameters via the user mobile device 16 prior to the search screen being engaged. The vehicles 14 would normally transmit such data along with the availability signal via the DVES beacons 22.

[0051] Conditions and/or parameters of each vehicle 14 may be set in advance by the driver of the vehicle (or administrator/operator if the vehicle is an autonomous vehicle), which would be reflected in the data stream transmitted by the beacon 22 of the vehicle 14. For example, a driver, administrator or operator could set a maximum number of allowed passengers, a maximum/minimum possible trip distance or radius, a minimum fee amount, smoking/non-smoking cabin policy, etc. for the vehicle 14. The DVES application 18 could allow a user 12 the choice of selecting one or more filters (e.g., trip conditions or parameters) which would limit the identification of available vehicles 14 to only those vehicles 14 that meet the filter requirements, and only those vehicles 14 that meet the conditions and parameters selected would be displayed to the user 12 as being available for selection and engagement.

[0052] Typically, each vehicle 14 would be equipped with a DVES beacon 22, as illustrated in FIG. 1. More particularly, the DVES beacons 22 could be mounted on the roof, a short mast, or other high point of each vehicle 14 to maximize the transmission range of the beacon signal. The use of an internal beacon heating system would allow unimpaired beacon transmissions during freezing weather conditions. The DVES beacon 22 may also be used to digitally transmit various other statuses, ID, data, pricing information, or other indications via additional modulated data fields that can be read by the mobile device 16 camera(s) or receiver(s). For example, trip conditions and parameters can be transmitted from the DVES beacon 22 along with the availability signal so that a user 12 can identify and select a vehicle 14 according to a specific trip need. As a result, the DVES 10 in accordance with the present disclosure has the capability to transmit multiple sequential data fields during each transmission cycle.

[0053] In a preferred embodiment of the “Ad-hoc” Mode of the DVES 10, all that is necessary for a user 12 to preliminarily engage a particular vehicle 14 of interest would be for the user 12 to tap on the handheld touch-screen 20 of the user mobile device 16 at, or over, the image of the vehicle 14 of interest (Block 130), as displayed on the screen 20 during the application “search” mode, e.g. as shown in FIG. 2. Such selection may also be accomplished by using other selection gestures, such as by utilizing a single tap or press, a double tap or press, or a press held for a certain duration over the image of the desired vehicle 14, i.e. through any desired type of user input. Upon any appropriate selection gesture being accomplished, the DVES application 18 would then change from the “search” mode to the “engagement” mode (Block 140), with the handheld screen graphical treatment changing to highlight only the just-selected vehicle 14, which is now displaying a unique ID code 26 for the vehicle 14 on the user mobile device 16, for example, next to the vehicle's image on the mobile device display screen 20, e.g. as shown in FIG. 3. At the same time, all other vehicles 14 displayed on the screen 20 of the mobile device 16 would be “greyed out” as not being selected for engagement.

[0054] In preferred embodiments of the DVES 10, the user can formally engage the selected vehicle 14 by confirming the unique vehicle ID code 26 using the user mobile device 16 (Block 155). For example, the user mobile device 16 can transmit an acceptance of the unique vehicle ID code 26 back to the vehicle 14 as a confirmation. Alternatively, the selected vehicle 14 can be directly engaged using optical means associated with the user mobile device 16 to interact with an optical scanner in or outside the selected vehicle 14 for optical recognition of an image displayed on a display of the mobile device 16, e.g. a bar code, QR code, or the like. Still further, the selected vehicle 14 can be engaged using any kind of known radio frequency (RF) transmission means associated with the user mobile device 16 to interact with an RF receiver on the selected vehicle 14. The exchange with an optical scanner or an RF receiver on the selected vehicle 14 can include provision of the unique vehicle ID code 26 to verify the vehicle engagement. Thus, the selected vehicle 14 may be configured to receive the unique vehicle ID code (or confirmation code) 26 from the mobile device 16 through wireless radio communication, from the mobile device 16 through optical recognition, and/or from the user 12 by manual input through an interface on or in the vehicle 14.

[0055] At the point of initial selection of a particular vehicle by a user (i.e. preliminary engagement), several associated actions may also be triggered. First, the vehicle's beacon transmission status as displayed on the selecting party's screen would instantly (or substantially instantly) change from indicating an “I am available” signal to instead, indicating the vehicle's confirmation ID code 26, while simultaneously (or substantially simultaneously) removing the vehicle 14 from showing up as “available” on any other handheld device screen 20 that may be functioning in a DVES search mode (Block 160). This initial selection process by the user 12 may also cause any in-motion vehicle 14 that has been selected for hire to immediately (or substantially immediately) come to a stop (or provide an instruction to stop) at the nearest appropriate location for passenger pickup (Block 165), and start a timer for the user to enter an appropriate confirmation in order to formally engage the vehicle 14 (Block 175) within a predetermined amount of time. In accordance with preferred embodiments, the timer can be pre-set—for example, at 120 seconds. That is, once the timer starts, the user has 120 seconds in which to enter a confirmation code or otherwise formally engage the vehicle 14 for confirmation of a trip arrangement (e.g., by optical scan or RF transmission) (Block 180). If the confirmation code is entered by an appropriate means, then the trip can begin (Block 190). If the timer exceeds 120 seconds without such a confirmation, then the vehicle beacon 22 reverts to again showing the vehicle 14 as being “available” (Block 185). For driven vehicles, the DVES 10 will trigger an audible and visual “vehicle engaged” alert for the driver to allow them to pull over at the nearest safe spot, just like a taxicab would do if physically hailed. In the case of autonomous vehicles, the vehicle would similarly pull over and may engage its four-way flashers during the pendency of the fare physically finding and entering the vehicle.

[0056] If the vehicle 14 that is selected is already parked in an appropriate pickup location, it may also wait a pre-determined length of time for the hailing party to finalize the engagement (or formally engage the vehicle) — such as by: entering the vehicle 14; electronically or manually providing the unique vehicle ID code 26; interacting with an optical scanner; and/or interacting with an RF receiver—before the vehicle 14 reverts back to an “available” status (Block 185).

[0057] The actual trip information data input of the DVES selection/engagement process can take several forms, with the preferred and fastest method requiring just the selection of a pre-loaded destination that has already been stored on the user mobile device 16 running the DVES application 18 to be transmitted to the selected vehicle 14, along with the stored user and billing information. Alternatively, the user 12 can manually enter the destination information after the initial vehicle selection. Upon selecting the desired destination, either from a saved list or manually entering it into the application 18, the user mobile device 16 sends a burst transmission to the vehicle 14 confirming the selected vehicle's unique ID code 26, as well as sending all of the needed pertinent trip and billing information which would be necessary to effectuate the desired trip (Block 150). The user 12 then approaches the selected vehicle 14, and then scans the user mobile device's screen 20 (that has started displaying a QR or other information code) in front of an optical reader that is mounted either inside and/or outside the vehicle 14. Optionally, a user could enter the unique vehicle ID code 26 manually on a keypad located on or in the vehicle 14. Optionally, other methods such as voice input may be used to effectuate the engagement of a vehicle 14 by inputting a user ID code 26 and destination if the user mobile device 16 fails or if desired.

[0058] If the selected vehicle 14 is within the desired geographical proximity to the user 12 but not immediately apparent to the user 12, then the DVES application 18 can include a vehicle locator mode to assist and direct the user 12 to the selected vehicle 14 (Block 170), with an annotated screen similar to the “search mode” screen wherein the engaged vehicle is highlighted or annotated.

[0059] In embodiments according to the present disclosure, there is no communication needed between the user 12 and a central or off-site assignment system in order to initially or preliminarily engage a vehicle or set up a trip request. Instead, the user 12 deals directly with any available, unassigned vehicles 14. More preferably, a user 12 can use the DVES application 18 on a user mobile device 16 to identify available vehicles 14, select a specific vehicle 14 from a group of available vehicles 14, and engage the selected vehicle 14 for a trip. In some embodiments, the user 12 can identify particular desired trip parameters (or filter parameters), including but not limited to, type of vehicle, size of vehicle, seating capacity of vehicle, seating configuration of the vehicle, available operating range of the vehicle, charge/gas level of the vehicle, or the existence of special accommodations (e.g., handicap accommodations), and use the DVES 10 in accordance with the present disclosure to identify available, unassigned vehicles 14 that also meet any such selected trip conditions or parameters.

[0060] With the DVES 10, any available, unassigned vehicle 14 that is proximate to a user 12 may be directly selected in real time, on the spot, with no need for the user 12 to communicate with a “third party” central/off-site control system, such as a Central Operations Center, in order to set up or effectuate a trip engagement. Communication with a third-party to eventually finalize the trip-transaction, e.g., such as payment, is not precluded by use of the DVES 10. With the DVES 10, the entire process for a trip engagement is entirely between the user 12 and any vehicle 14 selected by that user 12. There is no need for the user 12 to pre-arrange with a particular ride-hail service in order to have a specific vehicle sent to their location, and subsequently attempt to search for and identify the specific vehicle from amongst a plethora of other similar vehicles.

[0061] In an alternate embodiment of the DVES 10, a “Queue” Mode, shown in FIG. 5 and operating in accordance with the exemplary flow diagram shown in FIG. 6, can be utilized for vehicle engagement. By utilizing the “Queue” Mode, regardless of whether DVES-equipped vehicles 14 pre-position themselves in a formal line analogous to a traditional taxi cab stand, or cluster themselves as part of a waiting group of available vehicles 14, end users 12 may directly and spontaneously engage any desired vehicle 14 waiting in such a queue rather than being limited to selecting just the first vehicle in line.

[0062] In accordance with preferred operation in the “Queue” Mode, the user 12 accesses the DVES application 18 to start the selection/engagement process (Block 200). The user 12 inputs trip and/or billing information into the DVES application 18 (Block 210). Then, instead of searching for available, unassigned vehicles 14, as with the “Ad-hoc” Mode described above, the user 12 can find available vehicles 14 at pre-designated locations, such as queue lines outside airports, bus stations, train stations, sporting events, concerts, malls, or any other highly populated locations. The application 18 could still assist the user 12 to confirm availability status of a vehicle 14 in the queue so as to ensure that another user 12 has not already claimed a particular vehicle 14. Once confirmed, the user 12 can engage the available vehicle 14 through a variety of means.

[0063] With the “Queue” Mode, in addition to a vehicle 14 broadcasting an informational signal via the beacon 22, or via another portion of the vehicle 14, the vehicle 14 could also display a visible indication 28, such as a green light to indicate availability status, or a red light to indicate an unavailable status. In this regard, a user 12 can hire the vehicle 14 without using the DVES application 18 or even needing a user mobile device 16. In effect, all that is required for a user 12 to engage a vehicle 14 is for the user 12 to walk up to and open the door of any vehicle 14 that is showing a green light/available beacon status (Block 220). Once an idle/available vehicle 14 senses (or detects) that a door to that vehicle 14 has been opened and/or an occupancy sensor indicates that one or more people have entered the vehicle 14, the vehicle 14 could immediately change its availability status and color indication to “unavailable” to preclude a duplicate engagement attempt by another user 12 for a set period of time after the start of a timer (Block 225).

[0064] To effectuate the vehicle engagement in accordance with an alternate approach, a user 12 merely needs to hold the user mobile device 16 against a “near-field” antenna on or in a vehicle 14 to transmit a burst transmission from the DVES application 18 to the vehicle 14 which transmits salient trip information, such as the desired destination address that the vehicle 14 needs to go to, as well as other pertinent information that is needed or desired to execute a trip engagement request (Block 240).

[0065] Optionally, trip information can be provided from the user mobile device 16 via RF transmissions that are picked up by an RF receiver associated with the vehicle 14, or the user 12 can simply manually enter appropriate trip information and other optional information such as billing data, such as via a touch-screen on the vehicle 14, or by voice input. Still further, the user 12 can hold the user mobile device 16 under an optical reader or scanner on the vehicle 14 which, through a QR or other commonly used visible codes, allows salient trip information to be instantly entered into the DVES 10 (Block 230).

[0066] Once a vehicle 14 in the queue is selected and preliminarily engaged, the selected vehicle 14 changes its status automatically to “unavailable” by adjusting the beacon availability signal and also changing its visible indication (e.g., from green to red) for a set period of time after the start of a timer (Block 235). Thereafter, the user 12 confirms the trip information with the vehicle 14 (Block 260), and the trip begins (Block 270).

[0067] It is envisioned that as traditional parking lots for private vehicles become less and less necessary due to the increased adoption of “for-hire” vehicles, increasingly large areas will be designed and designated to more efficiently hold and/or queue such available vehicles for use by departing patrons. By properly designing the queue “lines” or areas, any newly engaged vehicle 14 may immediately get underway regardless of their place in a queue, lineup, or mobility status of other nearby vehicles 14 by the use of diagonal or perpendicular parking spaces designs, as shown in FIG. 5.

[0068] In addition to vehicles 14 electronically advertising their “available for-hire” status, the beacon 22 may also contain a visible indication that through color change or other visible alterations would convey its “availability” status. For those situations where a user 12 may not have access to a working user mobile device 16, and thus not have immediate access to the DVES application 18, the DVES 10 may be configured to accept all information entered manually via a touch-screen or keypad on and/or in the vehicle 14, as well as be equipped with a credit-card reader for billing purposes. To accommodate “walk up” trip requests, the user 12 touching or pulling an available vehicle's door handle could cause the vehicle 14 to immediately be placed in a temporary engaged status condition for a pre-set period of time. If the vehicle's 14 doors are not opened and/or the vehicle's seat occupancy sensors do not detect any occupancy, then the vehicle 14 would automatically revert back to an “available” status condition and transmit such availability information accordingly.

[0069] In the case of a multi-passenger party comprised of multiple persons desiring several sequential trip termination destinations, the trips can be ad-hoc preconfigured in toto, or multiple stored locations can be selected and added from an address book, or alternately entered and transmitted to the vehicle 14 prior to formal engagement. The DVES 10 in accordance with the present disclosure could also be capable of splitting up a fare amount equally amongst several passengers, or by proportionally allocating the cost of trip segments in the case of multiple drop-off locations, or charged entirely to a primary user 12 regardless of the number of destination locations, the decision of which can be pre-determined prior to the formal engagement of the vehicle 14 to maximize efficiency.

[0070] Additional drop-off locations may also be dynamically added during the pendency of a trip.

[0071] Optionally, when weather conditions or other local factors limit the visual range of a handheld device, the DVES application 18 may show a list of nearby available vehicles (filtering allowed) with selection accomplishable for a vehicle that is not yet within a visible range to the handheld device. In this case, a selection may be made by choosing a vehicle from the list. The list may highlight and/or annotate the vehicles on the list based on the filter parameters as discussed above. Although a preliminary selection of a particular vehicle may be made while it is outside the immediate area to the hailing party (or visually perceptible area), which will remove the vehicle further showing an “available for hire” status for all users other than the engaging user, the actual engagement would only take place once the selected vehicle was within the visible range. Upon initial selection of a vehicle, the geographic coordinates of the engaging party (user) would be transmitted to either the driver of the selected vehicle in the case of a ‘driven’ vehicle, or to the vehicle's navigation system in the case of an Autonomous Vehicle. For those situations beyond the range of optical and/or short-range radio-frequency transmissions, both the vehicles as well as the mobile devices running the DVES application may utilize cellular or other known communications networks to transfer data, along with GPS or other commonly used location data to exchange instantaneous location data (i.e. real-time location data).

[0072] In addition to coordinating direct engagement of ride-hail or ride-share vehicles, the systems, devices and methods described above may also be applied in direct truck assignment applications for coordinating the transportation of cargo as is described in greater detail below.

[0073] As the final destination for each cargo container on a ship is known by both the applicable Customs authorities as well as the shipping companies in advance of a ship's arrival to a port, as soon as each container is unloaded off of a ship and then clears customs, the container can be immediately directed to one or more grouping areas, such as for example: (i) a local grouping area; (ii) a regional grouping area; or a (iii) a long-haul grouping area as opposed to placing it in a warehouse or other holding area to await a pickup delivery vehicle to be scheduled.

[0074] Each grouping area may include multiple marshalling areas consisting of different loading areas, lanes, etc. Under a Direct Truck Assignment System (DTAS) according to the present disclosure, random delivery trucks may immediately proceed to, or may be directed to, any available loading area at a facility or lane as it does not matter which shipping container is matched with which truck. After a container is physically paired with a truck, the truck (or truck's driver) is provided with a specific and appropriate destination address and the “match” details are recorded in the location's computer system. This way, there does not need to be any waiting for a particular lane to become available and no need for a trucker to find a particular pre-assigned load for transport.

[0075] In an exemplary embodiment of a DTAS according to the present disclosure, trucks (tractors) arrive to a shipping facility with an empty container chassis already attached, to which a random freight container (i.e. cargo) is subsequently attached. In some embodiments, the freight containers have been already fitted with a container chassis that would allow any compatible truck (tractor) to be immediately attached to the freight container/container chassis thus allowing said combination to directly proceed to the corresponding “final mile” destination location. A “final Mile” destination location may mean the address of a company or individual, or a warehouse or storage facility offsite from a port, container terminal, or other such facility.

[0076] In some embodiments, trucks are required to check into an entry point of a container terminal where a DTAS controller interrogates each vehicle to ascertain whether various elements in order to determine whether one or more qualifying conditions are satisfied, such as the truck (loading) system registration status, vehicle registration status, insurance status, and/or driver background check status, etc. If all of the required and predetermined conditions are satisfied, then the truck is granted access to the terminal facility. Other characteristics are within the scope of the present disclosure.

[0077] Upon entry clearance, each truck may signal to the DTAS controller a target or preference grouping area that the truck or truck operator would like to be assigned to (e.g. local area, regional area or long-haul area). The DTAS controller is configured to direct each truck to the appropriate marshalling area for the preference selected. Once in the selected area of the container terminal, each truck would join any queue that is in the selected marshalling area and be assigned and matched to the next available/unassigned container (cargo).

[0078] A DTAS may be configured to assign driven trucks and/or autonomous trucks.

[0079] Referring to FIG. 7, a schematic representation of a DTAS container terminal 300 in accordance with the present disclosure. The DTAS container terminal 300 comprises a plurality of cargo containers 301A-D. Each cargo container 301 includes a radio frequency (RF) container transponder 303A-D that is configured and/or programmed to report to the cargo terminal unique identifying information of the container 301 associated with the transponder 303.

[0080] Each truck 305 (commonly referred to as a tractor, semi-trailer truck, semi- tractor truck, etc.) that enters the DTAS container terminal 300 through the entry point 307A has a radio frequency (RF) truck transponder 309 configured and/or programmed to report unique identifying characteristics and other operational information of the truck 305 and/or of the driver/operator of the truck 305. Each truck 305 also includes a hitch 305A for connecting to a container and/or container chassis (or any other known connection mechanism or means for hauling containers or other cargo). As the truck 305 drives through the entry point 307A, as part of an initial registration process, the truck transponder 309 is interrogated by one or more beacon interrogators 311 that relay return information received from the truck transponder(s) 309 to a central facility 313 (through known wired or wireless means) to be received and analyzed by a DTAS controller 315 of the central facility 313. If the characteristics of the truck 305 and/or of the driver/operator satisfy one or more predetermined conditions, the controller 315 is configured to allow access to the container terminal 300 and/or provide an indication that access is allowed (e.g. a green light or other visual indicator and/or an audible sound to inform an entry point attendant to provide access to the truck 305). If the truck 305 has a malfunctioning transponder 309, no transponder, or the transponder 309 does not transmit qualifying information to satisfy one or more of the predetermined conditions (as determined by the controller 315), then the truck 305 will not be granted access to the container terminal 300 or the controller will provide an indication that access is not allowed (e.g. a red light or other visual indicator and/or an audible sound, the visual indicator and audible sound being different for an indication allowing access and an indication not allowing access).

[0081] Once allowed access to the container terminal 300, the truck 305 can proceed to navigate to a queue for any available and/or desired cargo container grouping area, such as the local grouping area 317A, the regional grouping area 317B or the long-haul grouping area 317C. The truck 305 can exit the container terminal 300 with a cargo container 301 at the exit point 307B.

[0082] While the DTAS central facility 313 and controller 315 are shown in FIG. 7 as being arranged on-site in the container terminal 300, in some embodiments the central facility 313 and/or controller 315 are arranged off-site.

[0083] Referring to FIG. 8, an exemplary flow diagram illustrating operation of a method of a DTAS in accordance with the present disclosure. The method begins at block 319, where the initial registration process described above. Once granted access, the truck 305 enters the container terminal 300 at block 321. Then, at block 323, the truck (or truck operator) selects either the desired grouping area category 317 for approximate cargo transportation range, or indicates any/all. The grouping areas may be divided as having a final destination within a particular distance range or driving distance range, e.g. the local grouping area being within “X” miles of the port/shipping terminal, the regional grouping area being within “Y” miles of the port/shipping terminal, and the long-haul grouping area being within “Z” miles of the port/shipping terminal, where X<Y<Z. For example and without limitation, the local grouping area can be for cargo containers with a final destination within 100 miles (or a different range, e.g. within a particular city or county), the regional grouping area for cargo containers with final destinations within 100-500 miles, and the long-haul grouping area for cargo containers with final destinations greater than 500 miles (e.g. final destinations that are thousands of miles away).

[0084] After having selected the desired grouping area category, at block 327, the truck 305 moves to the selected area category marshalling area and enters the queue at block 329. The truck 305 is matched with first available load in the selected area at block 331 after trucks ahead in the queue have been matched with respective first available loads. After being matched with a load, at block 333 the truck 305 and/or operator of the truck 305 is provided by the controller 315 (or other controller of the DTAS) with relevant cargo information of the matched cargo load matched with the truck (which can be before, during or after the truck 305 physically attaches to the cargo container or load). Such relevant information can contain the final destination of the cargo container 301, weight of the cargo container 301, owner of the cargo container 301 and/or its contents, required delivery date and/or time, and/or any other information typically provided by shipping companies to truck hauling entities for transporting cargo. Then, at block 335, the truck 305 now physically and/or electrically paired to the container 301 and/or container chassis and hauls/exits the container terminal 300 at the exit point 307B with the cargo container 301. The paired truck 305 and container 301 may be recorded by the controller 315 prior to exiting for record keeping purposes and for coordinating the direct truck assignments with the delivery customer(s).

[0085] An advantage of a DTAS according to the present disclosure is that trucks participating in the assignment of cargo for transportation may be individually owned/operated and be seamlessly integrated alongside existing fleets of trucks and, thus, effectively be managing assignments of trucks in a “fleet of fleets.”

[0086] Another advantage of a DTAS according to the present disclosure is that an arriving truck can be dynamically assigned to an already waiting load almost immediately after arriving to the facility as all loads that are already in a marshalling area are in position for immediate assignment and pickup. With cargo containers handled in this manner, many uncertainties and delays regarding matching a particular pre-assigned load with a particular truck are avoided or eliminated, which inherently results in an unprecedented level of pickup efficiency and cargo throughput for most all parties concerned.

[0087] The systems and devices disclosed herein may be computer controlled systems and devices having the necessary electronics, computer processing power, interfaces, memory, hardware, software, firmware, logic/state machines, databases, microprocessors, communication links, displays or other visual or audio interfaces, to provide the functions or achieve the results described herein.

[0088] The foregoing description of embodiments of the present invention has been presented for the purpose of illustration and description. It is not intended to be exhaustive or to limit the invention to the form disclosed. Obvious modifications and variations are possible in light of the above disclosure. The embodiments described were chosen to best illustrate the principles of the invention and practical applications thereof to enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as suited to the particular use contemplated.