Patent Grant
10520581
The present invention relates generally to systems and methods for enabling vehicles to closely follow one another safely using automatic or partially automatic control.
In recent years significant strides have been made in the fields of autonomous and semi-autonomous vehicles. One segment of vehicle automation relates to vehicular convoying systems that enable vehicles to follow closely together in a safe, efficient and convenient manner. Following closely behind another vehicle has significant fuel savings benefits, but is generally unsafe when done manually by the driver. One type of vehicle convoying system is sometimes referred to as vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are autonomously or semi-autonomously controlled to closely follow a lead vehicle in a safe manner.
In vehicle platooning and convoying systems an understanding of the distance between the vehicles is a very important control parameter and multiple different independent mechanisms may be used to determine the distance between vehicles. These may include radar systems, transmitting absolute or relative position data between vehicles (e.g., GPS or other GNSS data), LIDAR systems, cameras, etc. A challenge that occurs when using radar in platooning type applications is that the partner vehicle must be reliably identified from a potentially ambiguous set of radar reflections and tracked under constantly changing conditions. The present application describes techniques for identifying and tracking specific vehicles based on vehicle radar data that are well suited for platooning, convoying and other autonomous or semi-autonomous driving applications.
A variety of methods, controllers and algorithms are described for fusing sensor data obtained from different vehicles for use in the at least partial automatic control of a particular vehicle. The described techniques are well suited for use in conjunction with a variety of different vehicle control applications including platooning, convoying and other connected driving applications.
In one aspect, information about a second vehicle is sensed at a first vehicle using a first sensor on the first vehicle while the first and second vehicles are driving. Information about the second vehicle is also received by the first vehicle from the second vehicle. The received second vehicle information is utilized to help determine whether the sensed information about the second vehicle is a valid measurement of the second vehicle. The first vehicle is then at least partially automatically controlled based at least in part on an aspect of the sensed information about the second vehicle.
In some embodiments, the first sensor measures a distance to the second vehicle. In some implementations, the first sensor also detects a velocity of the second vehicle relative to the first vehicle. In different embodiments, the first sensor may be any of a radar unit, a LIDAR unit, a sonar unit, a time-of-flight distance sensor, a sensor configured to receive a signal transmitted from a beacon on the second vehicle, a camera, and a stereo camera unit.
In some embodiments the received second vehicle information includes one or more of: a global navigation satellite systems (GNSS) position measurement of a current position of the second vehicle; speed information indicative of a speed or relative speed of the second vehicle (as for example wheel speed); and an indication of at least one of an acceleration, an orientation, a steering angle, a yaw rate, a tilt, an incline or a lateral motion of the second vehicle.
In some embodiments the received second vehicle information includes a predicted state of the second vehicle. The predicted state may optionally include one or more of a predicted position, a predicted speed, a predicted acceleration, a predicted orientation, a predicted yaw rate, a predicted tilt, a predicted incline and a predicted lateral motion of the second vehicle.
In various embodiments, the received second vehicle information is used to estimate the state of the second vehicle and/or to help validate the measured state of the second vehicle. In various implementations, the received second vehicle information may be used to update a Kalman filter or a particle filter that estimates the state of the second vehicle.
The received second vehicle information may be received over a radio frequency communications link—as for example, a link implementing a Dedicated Short Range Communications (DSRC) protocol (e.g. a IEEE 802.11p link), a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands.
In some embodiments second information about the second vehicle is received by the first vehicle from an external source other than the second vehicle. This second information may also be used to help determine whether the sensed information about the second vehicle is a valid measurement of the second vehicle.
In some connected driving embodiments information about the second vehicle may be transmitted to a third vehicle to help facilitate at least partially autonomous control of the third vehicle.
The described approaches are well suited for use in vehicle platooning and/or vehicle convoying systems including tractor-trailer truck platooning applications.
The invention and the advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
In the drawings, like reference numerals are sometimes used to designate like structural elements. It should also be appreciated that the depictions in the figures are diagrammatic and not to scale.
The Applicant has proposed various vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are autonomously or semi-autonomously controlled to closely follow a lead vehicle in a safe manner By way of example, U.S. application Ser. Nos. 13/542,622, 13/542,627 and 14/292,583; U.S. Provisional Application Nos. 61/505,076, 62/249,898, 62/343,819, 62/377,970 and; and PCT Application Nos. PCT/US2014/030770, PCT/US2016/049143 and PCT/US2016/060167 describe various vehicle platooning systems in which a trailing vehicle is at least partially automatically controlled to closely follow a designated lead vehicle. Each of these earlier applications is incorporated herein by reference.
One of the goals of platooning is typically to maintain a desired longitudinal distance between the platooning vehicles, which is frequently referred to herein as the “desired gap”. That is, it is desirable for the trailing vehicle (e.g., a trailing truck) to maintain a designated gap relative to a specific vehicle (e.g., a lead truck). The vehicles involved in a platoon will typically have sophisticated control systems suitable for initiating a platoon, maintaining the gap under a wide variety of different driving conditions, and gracefully dissolving the platoon as appropriate.
The architecture and design of control systems suitable for implementing vehicle platooning may vary widely. By way of example,
Some of the functional components of the platoon controller 110 include gap regulator 112, mass estimator 114, radar tracker 116 and brake health monitor 118. In many applications, the platoon controller 110 will include a variety of other components as well.
Some of the sensors utilized by the platoon controller 110 may include GNSS (GPS) unit 131, wheel speed sensors 132, inertial measurement devices 134, radar unit 137, LIDAR unit 138, cameras 139, accelerator pedal position sensor 141, steering wheel position sensor 142, brake pedal position sensor 143, and various accelerometers. Of course, not all of these sensors will be available on all vehicles involved in a platoon and not all of these sensors are required in any particular embodiment. A variety of other sensor (now existing or later developed or commercially deployed) may be additionally or alternatively be utilized by the platoon controller in other embodiments. In the primary embodiments described herein, GPS position data is used. However, GPS is just one of the currently available global navigation satellite systems (GNSS). Therefore, it should be appreciated that data from any other GNSS system or from other suitable position sensing systems may be used in place of, or in addition to the GPS system.
Many (but not all) of the described sensors, including wheel speed sensors, 132, radar unit 137, accelerator pedal position sensor 141, steering wheel position sensor 142, brake pedal position sensor 143, and accelerometer 144 are relatively standard equipment on newer trucks (tractors) used to pull semi-trailers. However, others, such as the GNSS unit 131 and LIDAR unit 138 (if used) are not currently standard equipment on such tractors or may not be present on a particular vehicle and may be installed as needed or desired to help support platooning.
Some of the vehicle actuators controllers 150 that the platoon controller directs at least in part include torque request controller 152 (which may be integrated in an ECU or power train controller); transmission controller 154, brake controller 156 and clutch controller 158.
The communications between vehicles may be directed over any suitable channel and may be coordinated by inter-vehicle communications controller 170. By way of example, the Dedicated Short Range Communications (DSRC) protocol (e.g. the IEEE 802.11p protocol), which is a two-way short to medium range wireless communications technology that has been developed for vehicle to vehicle communications, works well. Of course other communications protocols and channels may be used in addition to or in place of a DSRC link. For example, the inter vehicle communications may additionally or alternatively be transmitted over a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands or any other now existing or later developed communications channels using any suitable communication protocol.
The specific information transmitted back and forth between the vehicles may vary widely based on the needs of the platoon controller. In various embodiments, the transmitted information may include the current commands generated by the platoon controller such as requested/commanded engine torque, requested/commanded braking deceleration. They may also include steering commands, gear commands, etc. when those aspects are controlled by platoon controller. Corresponding information is received from the partner vehicle, regardless of whether those commands are generated by a platoon controller or other autonomous or semi-autonomous controller on the partner vehicle (e.g., an adaptive cruise control system (ACC) or a collision mitigation system (CMS)), or through other or more traditional mechanisms—as for example, in response to driver inputs (e.g., accelerator pedal position, brake position, steering wheel position, etc.).
In many embodiments, much or all of the tractor sensor information provided to platoon controller is also transmitted to the platoon partner and corresponding information is received from the platoon partner so that the platoon controllers on each vehicle can develop an accurate model of what the partner vehicle is doing. The same is true for any other relevant information that is provided to the platoon controller, including any vehicle configuration information that is relevant to the platoon controller. It should be appreciated that the specific information transmitted may vary widely based on the requirements of the platoon controllers, the sensors and actuators available on the respective vehicles, and the specific knowledge that each vehicle may have about itself.
The information transmitted between vehicles may also include information about intended future actions. For example, if the lead vehicle knows it approaching a hill, it may expect to increase its torque request (or decrease its torque request in the context of a downhill) in the near future and that information can be conveyed to a trailing vehicle for use as appropriate by the platoon controller. Of course, there is a wide variety of other information that can be used to foresee future torque or braking requests and that information can be conveyed in a variety of different forms. In some embodiments, the nature of the expected events themselves can be indicated (e.g., a hill, or curve or exit is approaching) together with the expected timing of such events. In other embodiments, the intended future actions can be reported in the context of expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected. Of course, there are a wide variety of different types of expected events that may be relevant to the platoon control.
The communications between the vehicles and the NOC may be transmitted over a variety of different networks, such as the cellular network, various Wi-Fi networks, satellite communications networks and/or any of a variety of other networks as appropriate. The communications with the NOC may be coordinated by NOC communications controller 180. The information transmitted to and/or received from the NOC may vary widely based on the overall system design. In some circumstances, the NOC may provide specific control parameters such as a target gap tolerance. These control parameters or constraints may be based on factors known at the NOC such as speed limits, the nature of the road/terrain (e.g., hilly vs. flat, winding vs. straight, etc.) weather conditions, traffic or road conditions, etc. In other circumstances the NOC may provide information such information to the platoon controller. The NOC may also provide information about the partner vehicle including its configuration information and any known relevant information about its current operational state such as weight, trailer length, etc.
Radar Tracking
The vehicles involved in a platoon will typically have one or more radar systems that are used to detect nearby objects. Since radar systems tend to be quite good at determining distances between objects, separation distances reported by the radar unit(s) are quite useful in controlling the gap between vehicles. Therefore, once a platooning partner is identified, it is important to locate that specific partner vehicle in the context of the radar system output. That is, to determine which (if any) of a variety of different objects that might be identified by the radar unit correspond to the targeted partner.
Preliminarily, it should be appreciated that the platoon partner will not always correlate to the closest vehicle detected by the radar unit or to the vehicle that is directly in front of the trailing truck. There are a wide variety of different scenarios that can cause this to be the case. For example, when the platoon is initially being set up, the partner may be out of sight of a host vehicle's radar unit because it is too far away. As the partner comes into sight of the radar unit, it becomes important to identify and distinguish that partner from other objects in the radar unit's field of view. The description below describes techniques that are particularly well suited for identifying and distinguishing a designated partner from other objects that may be detected by a radar unit so that the radar unit can effectively track the partner vehicle (sometimes referred to as “locking onto” the partner).
Furthermore, during the course of driving, there will be traffic in adjacent lanes that are traveling beside, passing or being passed by the platoon and it is important for the radar unit to be able to continue to differentiate the platoon partner from passing vehicles so that the gap controller doesn't start trying to maintain the gap from the wrong vehicle. In another example, a lead truck may change lanes at which point it may not be directly in front of the trailing vehicle, so again, it is important for that the distance between the platoon partners reported by the radar unit be associated with the platoon partner rather than merely the closest vehicle or a vehicle that happens to be directly in front of the trailing truck. There may also be times when the radar unit may not be able to “see” the platooning partner. This could be because an interloper has gotten between the platoon partners or the lead vehicle has maneuvered out of view of the trailing vehicle's radar unit, interference with the radar signals, etc.
For platoon control purposes, it is also important to understand where the back of the vehicle is relative to the vehicle's reported position. To elaborate, the position of the partner vehicle is generally known from the GPS based location information that is transmitted to the host vehicle. However, the GPS system typically reports a location on the tractor, which could for example, be the position of the antenna(s) that receive the GPS signals. The detected GPS position may then be translated to the position of a reference location on the vehicle that is a known distance from the GPS antenna, with the position of that reference location serving as the vehicle's reported GPS position. The specific reference location chosen may vary based on control system preferences. By way of example, in some tractor trailer truck platooning embodiments, the reference location may be the center of the rear axles of the tractor.
The difference between the reported GPS position and the physical back of the vehicle can be significant to the platoon control. Therefore, it is often important to know the distance between the reported vehicle position and the actual back of the vehicle. This is sometimes referred to herein as the “effective vehicle length.” The effective vehicle length is particularly important in the context of a tractor trailer truck where the reported GPS position is typically located somewhere on the cab (tractor) and the distance from the reported GPS position to the back of the trailer may be quite long. By way of example, trailer lengths on the order of 12-18 meters are common in the U.S. although they can be shorter or longer (indeed much longer in the context of double or triple trailers). The distance from the reported GPS position to the back of the vehicle must also account for the longitudinal distance from the reported GPS position to the front of the trailer and/or any extensions associate with the load. It should be appreciated that in the trucking industry, the effective vehicle length often will not be known since any particular tractor may pull a variety of different trailers and the attachment point between the tractor and trailer is adjustable on the tractor.
Establishing a Radar Fix on a Platoon Partner
As will be apparent from the discussion above, a challenge that occurs when using radar in platooning type applications is that the partner vehicle must initially be found and identified in the context of the radar system's output and thereafter reliably tracked under constantly changing conditions. In application such as the trucking industry, it is also desirable to determine the effective length of at least the lead vehicle.
Commercially available radar units used in general road vehicle driving automation systems typically output data that indicates the presence of any object(s) detected within a designated field together with the relative position and speed of such object(s). Thus, during driving, such a radar unit may detect the presence of a variety of objects within its operational field. The detected objects may include any vehicle positioned directly in front of the host vehicle, vehicles in adjacent lanes that may be passing, being passed by or driving in parallel to the platoon, stationary objects such as obstacles in the road, signs, trees, and other objects to the side of the road, etc. Although many different types of objects may be detected, the radar unit itself typically doesn't know or convey the identity or nature of the detected object. Rather it simply reports the relative position and motion of any and all perceived objects within its operational field. Therefore, to identify and track the partner vehicle in the context of the radar unit output, it is helpful for the logic interpreting the output of the radar unit to have and maintain a good understanding of exactly where the partner vehicle is expected to be relative to the radar unit's field of view regardless of whether the partner vehicle is even in that field of view. This is possible even when no explicit mechanism is provided for identifying the partner because the platooning system preferably has multiple independent mechanisms that can be used to help determine a vehicle's position.
When a platoon partner is identified a communications link is preferably established between the platooning vehicles. The communications may be established over one or more wireless links such as a Dedicated Short Range Communications (DSRC) link, a cellular link, etc. Once communications are established between the two vehicles, they begin transmitting data back and forth regarding their respective selves, their current locations and operational states. The processes used to identify potential platoon partners and to establish the platoon and appropriate communication links may vary widely. By way of example, a few representative techniques are described in U.S. patent application Ser. Nos. 13/542,622 and 13/542,627 as well as PCT Patent Application Nos. PCT/US2014/030770, PCT/US2016/049143 and PCT/US2016/060167 previously filed by Applicant, each of which is incorporated herein by reference.
Once a platoon partner has been identified, the platoon controller 110 requests the radar system control logic attempt to find the partner vehicle. More specifically, the trailing vehicle's radar tracker 116 needs to find and thereafter track the back of the lead vehicle in the context of the radar unit's outputs so that its data can be used in gap control. Referring next to
When the process initiates, radar tracker control logic determines, receives or requests an estimate of the current relative position of the partner vehicle and subscribes to or regularly receives updates regarding the partner vehicle's relative position as they become available as represented by step 203 of
In some embodiments, the radar tracker control logic is configured to estimate the current relative position, velocity and orientation (heading) of the partner vehicle based on a variety of sensor inputs from both the host vehicle and the partner vehicle. As mentioned above, the platoon partners are in communication with one another and during platooning, they send extensive information back and forth about themselves, including continually updated information about their current location and operating states. By way of example, some of the location related information that can be helpful to interpreting radar unit data may include information such as the partner vehicle's GPS position, wheel speed, orientation/heading (direction that the vehicle is heading), yaw rate (which indicates the vehicle's rate of turn), pitch, roll and acceleration/deceleration (longitudinal and angular in any of the forgoing directions). Operational related information may also include a variety of other information of interest such the current torque requests, brake inputs, gear, etc. Information about the vehicles, may include information such as the make and model of the vehicle, its length (if known), its equipment, estimated weight, etc. Any of these and/or other available information can be used in the position related estimates. By way of example, one particular position estimator is described below with respect to
Although a particular estimator is described, it should be appreciated that the estimated partner vehicle position related information can come from any appropriate source and the estimation does not need to be made by the radar tracker control logic itself. Additionally, although it is preferred that position and operational information be transmitted in both directions between vehicles, that is not necessary as long as the host vehicle is able to obtain the required information about the partner vehicle(s).
The current location related information is updated very frequently. Although the actual frequency of the updates can vary widely based on the nature of the information being updated and the nature of the communication link or vehicle system that provides the information, update frequencies for items such as GPS position and wheel speed received over a DSRC link at frequencies on the order of 10 to 500 Hz, as for example 50 Hz work well although slower and much faster update frequencies may be used as appropriate in other embodiments. Furthermore, although regular updates of the location related information are desirable, there is no need that they be received synchronously or at consistent intervals.
It should be appreciated that when the radar system begins trying to locate the partner vehicle, the partner vehicles may or may not be within the radar unit's field of view. However both the host vehicle's position and the partner vehicle's position are generally known based at least on the received GPS data so it is easy to estimate their separation with reasonable certainty. It should also be appreciated that although GPS location signals tend to be pretty good, the reported locations may be off by some amount and thus it is better to treat any reported GPS position as an estimate with some appropriate amount of uncertainty rather than treating the reported position as infallible information. More details regarding some specific algorithms that are suitable for estimating the partner vehicle position will be described in more detail below. Experience has shown that GPS position readings from commercially available GPS sensors used in vehicle automation applications tend to be accurate within about 2-3 meters in practical road conditions when there is a direct line of sight to at least 4 GPS satellites. However, it should be appreciated that some GPS sensors are regularly more precise and no GPS sensors are guaranteed to always be that accurate due to variables such as interference, operations is regions where there is not line of sight visibility to the required number of operational GPS satellites, etc.
Once the partner vehicle's relative position estimate is known, a bounding box is applied around the estimated relative position of the partner (step 206 of
The actual size and geometry of the bounding box used may vary but it is desirable that the region be large enough to encompass the entire range of vehicle lengths and widths that are possible plus a buffer to account of uncertainty in the estimated GPS position. Thus, for trucking applications, it is desirable that the longitudinal length of the bounding box be longer than any tractor-trailer combination that might be expected to be encountered. For example, U.S. commercial trucking applications involving normal tractor trailer combinations typically don't significantly exceed a combined length of 23 meters. In such applications, bounding boxes on the order of 32 meters long and 3-4.5 meters, as for example 3.8 meters wide have been found to work well. In regions that allow longer trailers or the use of double or triple trailers, the tractor-trailer combinations may be longer and therefore longer bounding boxes may be appropriate. If the actual length of the platoon partner is known, the size of the bounding box can be adjusted accordingly to more accurately reflect the expected offset between the GPS position and the back of the trailer—which correlates to the effective vehicle length. However, even when it is believed that the effective length and width of the platoon partner is “known,” it is still desirable to utilize a bounding box greater in size than the reported length and width to accommodate uncertainty in the GPS estimates and the possibility that the load may include a feature that extends beyond the vehicle's reported length.
It should be appreciated though that there is no need for the bounding box to be rectilinear in nature, rather, the bounding box may encompass any desired geometric shape and/or may include dimensions other than longitudinal length and lateral width—as for example relative velocity. Thus, the bounding box may be defined in any desired manner.
A representative bounding box 255 applied around a lead truck 251 in a platoon of two trucks is diagrammatically illustrated in
In some embodiments, the bounding box may be defined more complexly. For example, in one particular embodiment, the scaled squares of the lateral offset (Yoff) and the relative velocity (V) of the vehicles may be compared to a threshold (Th). A radar point would then be rejected if the sum of these squares exceeds the designated threshold (Th), even if the radar point is within the longitudinal range of the bounding box. Such a test may be represented mathematically as shown below:
If kYoff2+V2≥Th,then the object is rejected
In such an approach, the bounding box has the effective appearance of a tube with in a state space map with velocity being the third axis. The logic of such an approach is that if both the measured lateral offset and the measured velocity of a detected object are relatively lower probability matches, then the detected point is less likely to be a match (and therefore more appropriate to disregard for the purposes of identifying the back of a partner vehicle) than if one of those parameters is off but the other very nearly matches the expected value. Although only a couple specific bounding box definition approaches have been described, it should be apparent that a wide variety of other bounding box definitions may be used as appropriate in other implementations. Additionally, the bounding box definition may be arranged to change over time. For example, one or more selected dimensions of the bounding box may be reduced as the algorithm begins to develop a better understanding of what radar object sample points are more likely to correspond to the partner vehicle or the back of the partner vehicle.
Once the bounding box has been established, the logic determines whether the entire bounding box is within the other vehicle's radar unit's field of view 263 (step 209). If not, the logic waits for the entire bounding box to come within the radar unit's field of view thereby effectively ignoring the radar system outputs for the purpose of identifying the partner vehicle (although of course the radar system outputs can be used for other purposes such as collision avoidance if desired). There are a variety of reasons why the partner vehicle may not be within or fully within the radar units field of view at any particular time. Initially, it should be appreciated that although the radar unit(s) used to support platooning may be placed at a variety of different locations on the vehicles, they often have a relatively narrow field of view. For example, one common approach is to place a forward facing radar unit having a relatively narrow fixed beam in the vicinity of the middle of the front bumper to detect objects in front of the vehicle. Such an arrangement is illustrated in
When a forward facing radar unit is used, it will be unable to see any vehicle behind or to the side of its host vehicle. Even when the partner vehicle is ahead of the radar unit host, it may be out of the field of view if it is too far ahead of the host or is around a corner—as may be the case when a platoon partner is first identified. In some cases a platoon partner can be partially in the radar unit's field of view. A common example of this is when the partner vehicle in an adjacent lane and not far enough ahead for the back of its trailer to be seen by a narrow beamed forward facing radar unit. It should be appreciated that it is undesirable to utilize radar samples if the back of the bounding box is not within the radar unit's field of view, since there is a risk that the furthest back portion of the partner vehicle that is detected by the radar unit is not actually the back of the vehicle.
When the entire bounding box is within the radar unit's field of view (e.g. a scenario such as illustrated in
The nature of radar systems is that the transmitted radio waves can be reflected by most anything in their path including both any intended target(s) and potentially a wide variety of different items. Therefore, when trying to establish a platoon, it is important to identify the reflected signal(s) that represent the desired partner and to be able to distinguish that partner from the noise reflected from other objects. By way of example, when driving along a road, the radar unit may receive reflections from multiple different vehicles including any vehicle that is immediately ahead, passing vehicles going in the same or opposite direction objects to the side of the road such as highway or street signs, trees or other objects along the side of the road, etc.
When a sensed scene is received, the radar system control logic determines whether any of the identified objects are partner vehicle radar point candidates as represented by step 218. Representative objects that might be detected by the radar unit 260 are marked with X's in
Some of the reported radar objects may be traveling in the same direction as the host vehicle but are moving at a relative velocity that is different than the expected partner velocity. There is a relatively high probability that such radar objects do not correspond to the partner vehicle and therefore these types of radar points are also preferably discarded.
Any detected radar objects that appear to match the expected location and speed of the partner within the context of the defined bounding box are considered partner vehicle radar point candidates and are categorized with respect to how far they are longitudinally (along the longitudinal axis of the partner) from the estimated location of the partner (e.g., the partner's GPS position). In some embodiments, a histogram is utilized for to this categorization. The number of bins in the histogram may vary. For computational ease, 512 bins divided evenly over the length of the bounding box has been found to work well, although more or less bins can be used as appropriate for any particular application. In implementations that use a bounding box of approximately 32 meters, with 512 bins, each bin corresponds to approximately 6 cm (2-3 inches). If greater resolution is desired, then more bins can be used.
It has been observed that it is common for the short range radar units utilized in road vehicle applications to identify multiple different “objects” that may be actually part of the same vehicle as represented by radar points 276-279 in
After the histogram has been populated with any partner vehicle radar point candidates identified in the sample, a determination is made regarding whether sufficient samples have been obtained to analyze the radar data to identify the partner vehicle in step 224. If not, the logic returns to step 212 where the next sample is obtained and the process repeats until sufficient samples have been obtained to facilitate analysis. If the bounding box moves partially out of the field of view of the radar unit at any point (as represented by the “no” branch from decision block 225), then the logic returns to step 209 where it waits for the bounding box to come back into full view before taking additional samples.
As discussed above, commercially available short range radar units utilized in road vehicle applications are typically configured to output their sensed scene at a relatively rapid sample rate. By way of example, sample rates on the order of 20 to 25 hertz are common, although either higher or lower sample frequencies may be used. Therefore, the histogram will populate fairly quickly when the partner vehicle is within the radar unit's field of view and the histogram will provide a rather good indication of the radar signature of the partner.
The large cluster 290 located furthest back in the histogram typically corresponds to the back of the vehicle and is often (although not always) the largest cluster. Cluster 292 located further forward typically correspond to other features of the partner truck. Experience has shown that radar reflections from the forward features tend to be weaker and more sporadically identified as a discrete object by the radar unit, which translates to a smaller cluster in the histogram.
If sufficient samples have been obtained to support analysis, the logic follows the yes branch from decision block 224 and flows to step 227 where a clustering algorithm is applied to the histogram data. The trigger point for when processing may start can vary widely based on the needs of any particular system. In general, it is desirable for the histogram to contain enough data points so that the partner vehicle can be accurately identified. In some specific implementations, the histogram must include data from a first threshold worth of samples (e.g., samples corresponding to at least 3 seconds worth of data or 60 samples) and include at least a second threshold worth of partner vehicle radar point candidates (e.g., at least 60 partner vehicle radar points). The thresholds used may vary based on the needs of a particular implementation. By way of example, samples corresponding to at least 1-5 seconds worth of data or thresholds in the range of 40 to 500 points may be used in some implementations. In one specific example, samples corresponding to at least 3 seconds worth of data or 60 samples and 60 partner vehicle radar points are used as thresholds.
The dataset illustrated in
In general, the clustering algorithm bunches data points that are highly likely to represent the same point. A variety of conventional clustering algorithms can be used for this purpose. By way of example, modified mean shift algorithms work well.
The mean shift data is then analyzed to determine whether one of the clusters meets predefined back of partner vehicle criteria in step 230. If so, that cluster is identified as corresponding to the back of the vehicle. (Step 233). Since each cluster corresponds to a designated distance between the partner's reported GPS position and the back of the vehicle, the effective length of the vehicle is defined by the cluster. As noted above, the phrase “effective vehicle length” as used herein corresponds to the distance between the reported GPS position and the back of the vehicle—which is an important distance to know for control purposes. It should be appreciated that this is typically different than the actual length of the vehicle because the reported reference position may not be located at the front of the vehicle.
In some implementations the cluster located closest to the back of bounding box that has over a threshold percentage of the total number of radar points in the histogram is identified as back of the platoon partner vehicle. In some implementations a further constraint is used that requires that the cluster location not move by more than a certain threshold on the last sample. By way of example, maximum movement thresholds on the order of 1 mm have been found to work well in some applications. This approach has been found to very reliably identify the radar point that corresponds to the back of a truck even when the radar unit controller has no predetermined knowledge of the length of the vehicle and regardless of the presence of other traffic. However, it should be appreciated that the threshold percentage or other characteristics of the histogram used to identify the back of the vehicle may vary based on application. In the embodiment illustrated in
It is particularly noteworthy that even though other traffic moving in parallel with the platoon may be detected by the radar, the described approach very reliably filters those radar points by effectively applying a number of different types of filters. Radar points that report features that are not where the platoon partner is expected to be are filtered because they are not within the bounding box. Radar points that are not traveling at close to the expected relative speed are filtered regardless of where they are found. The back of vehicle criteria used on the clustered histogram data effectively filters any other vehicles traveling within the footprint of the bounding box at very near the same speed as the platoon partner because the bins are small enough that it is highly unlikely that such an interloper can maintain a constant enough gap to fool the algorithm into thinking that the interloper is part of the target (e.g., even if the interloper is traveling at nearly the same speed as the partner vehicle, if it is located within the bounding box, it's position relative to the partner vehicle's position is likely to vary enough to cause the back of partner vehicle test to fail. The back of vehicle criteria also filters out more random objects reported by the radar unit.
The effective vehicle length indicated by the selected mean shift cluster may be reported to the gap controller and any other controller concerned with the length of the partner. In most circumstances, the distance between the GPS reference location and the front of the host vehicle is known and therefore the effective vehicle length determined by the radar unit can readily be used in association with known information about the truck to positively indicate the front and back of the truck as represented by step 236.
In some circumstances none of the mean shift clusters will meet the back of partner vehicle criteria. In most cases this suggests that there is a risk that the partner vehicle is not being accurately tracked. In such cases (as illustrated by the no branch from decision 230) the process continues to run collecting radar points from additional samples until the criteria is met indicating that the partner vehicle has confidently been identified. In some embodiments, radar points may optionally be discarded after they become too old or the process restarted if the system has trouble identifying the back of the partner vehicle or for other reasons, such as the vehicles coming to a stop.
In some embodiments, the back of the partner identification process continues to run or is periodically rerun even after the vehicle length has been determined. There are several advantages to continuing to populate the histogram. Often the initial length determination is made while the platoon partners are relatively far apart (e.g., over 100 feet). Once the back of the partner vehicle has been reliably identified, the gap controller may tighten the gap thereby drawing the vehicles closer together. When the vehicles are closer together, the radar reading are often more precise than they are when the vehicles are 100+ feet apart. Additionally, remembering that in some circumstances the GPS measurements may be relatively far off for gap control purposes, more measurement give a better statistical indication of the relative position of the vehicle. By continuing to run the back of partner identification process, those better measurements can be used to more accurately determine the effective length of the partner vehicle, which is highly desirable for control purposes.
Continuing to run the back of partner identification process has other potential uses as well. For example, some trucks have the ability to draw the trailer closer to the cab when the truck is operating on the highway. Thus, although it is relatively rare, there are situations in which the effective length of the truck can vary over the course of a platoon. Such changes can automatically be detected by rerunning or continuing to run the back of the partner identification process.
Over time, the histogram and/or mean shift clusters also provide a very good indication of the radar signature of the partner vehicle. This known signature of the partner vehicle can be used in a number of different ways as an independent mechanism for verifying that the proper vehicle is being tracked. For example, in scenarios where GPS data becomes unavailable or communications between the vehicles are disrupted for a period of time, the histogram can be used as a check to verify that the correct vehicle is being tracked by the radar unit. In circumstances where the back of the lead truck is not within the view of the trailing vehicle's radar, but other portions of the trailer and tractor are within the radar's view, the portion of the truck that can be seen can be compared to the histogram signature to determine the relative positioning of the trucks, which can be used as a measurement for gap control or as part of autonomous or semi-autonomous control of the trailing vehicle.
In another example, in circumstances when radar contact is lost, a new histogram can be started at an appropriate time and a new histogram can be compared to a stored histogram indicative of the platoon partner. When there is a match, that match can be good independent evidence that radar contact with the platoon partner has been reestablished. Similarly, newly created histograms can be compared to stored histograms representing the platoon partner at various times during platooning as a way of independently verifying that the platoon partner is still being tracked. This can be a good safety check to verify that the radar unit has not inadvertently switched and locked onto a vehicle that is traveling in parallel next to the platoon partner. The histograms can also be saved as a radar signature of the partner vehicle and shared with other trucks that may later seek to platoon with that vehicle—which can be useful in the initial identification process.
Estimating Position of Platoon Partners
In the context of platooning, it is helpful to maintain accurate models of the expected relative positions, speeds and orientations of each of the vehicles in the platoon as such information is very helpful in the accurate control of the gap between platoon partners. Such models preferably utilize inputs from multiple different sensing systems and include at least some redundant information from different systems when practical. The provision of redundant information from different systems is helpful as a double check as to the integrity of received data and also provides backup mechanisms for the inevitable times when a system is unable to convey accurate information.
By way of example, the gap between vehicles can be determined using a number of different techniques. One general approach is to use the distance to the platoon partner detected by the radar system. Although radar tends to very accurately measure the distance between vehicles, it is important to ensure that the distance being reported is actually the distance to the platoon partner rather than some other vehicle or feature. There are also times when the partner vehicle is not within the radar's field of view or the radar or the radar unit is not operating as desired for a brief period. An independent way of determining the distance between the platoon partners is to utilize their respective GPS data. Specifically, the distance between the vehicles should be the difference between the vehicle's respective GPS positions, minus the effective length of the lead vehicle and the offset distance between the front of the trailing vehicle and its GPS receiver. Limitations of using the GPS data include the fact that the GPS data will not always be available due to factors such as the GPS receivers not having a clear view of sufficient GPS satellites to be able to determine a location or the communication link between vehicles being down for a period of time. The GPS data is also fundamentally limited by the fact that the accuracy of the GPS data, which while good, is often less precise than desired for gap control. Other systems for measuring distances between the platoon partners have their own advantages and limitations.
When the current gap between the vehicles is known, the gap expected at a time in the immediate future can be estimated based on factors such as the current positions, the relative velocities and yaw rates of the vehicles. The respective velocities of the vehicles may also be measured, determined, estimated and/or predicted in a variety of different manners. For example, wheel speed sensors can be used to relatively accurately indicate the current speeds of the respective vehicles. Knowledge of the vehicle's orientation can be used in conjunction with the knowledge of the vehicle's speed to determine its velocity. The radar unit can be used to measure the relative speeds of the platoon partners. Knowledge of other factors such as torque request, vehicle weight, engine characteristics and road grade can be used to predict vehicle speeds in the future.
In the context of the radar system control, knowing where the leading vehicle is expected to be relative to the radar unit on a trailing vehicle can be quite helpful in determining whether one or more objects detected by the radar unit correspond to the back of the lead vehicle. Therefore, in some embodiments, the radar system controller (or another controller whose determinations can be utilized by the radar system controller) includes a position estimator that maintains an estimate of the current position, orientation and relative speed of the partner vehicle relative to the radar unit. One suitable radar scene processor 600 that includes a position/state estimator 612 is illustrated in
In the embodiment illustrated in
In the illustrated embodiment, the gap monitor 610 includes a position/state estimator 612 having a Kalman filter 615 that is used to determine both the most recent estimate of the position of the partner vehicle relative to the host vehicle and to predict the expected position of the partner vehicle at the time the next radar sample will be taken. As described in more detail with respect to
The partner identifier 620 includes its own position/state estimator 622, a histogram 624, a clustering algorithm 625 which produces mean shift clusters 626 and partner length estimator 627. The partner identifier 620 executes an algorithm such as the algorithm discussed above with respect to
The position/state estimator 622 in the partner identifier 620 functions similarly to the position/state estimator 612 describe above and may also include a Kalman filter 623. A significant difference between position state estimator 622 used for partner identification and position/state estimator 612 is that what radar point corresponds to the back of the partner truck is not known during identification and therefore the radar unit samples cannot be used as part of the position/state estimates.
The position/state estimation, partner detection, partner length estimating and gap monitoring algorithms may be executed on a radar tracking processor dedicated to radar tracking alone, or they may be implemented on a processor that performs other gap or platoon management tasks as well. The respective algorithms may be implemented as distinct computing processes or they may be integrated in various manners with each other and/or other functionality in various computing processes. In other embodiments, discrete or programmable logic may be used to implement the described functionality. It should be apparent that a wide variety of different models can be used to track the position of the back of the partner vehicle relative to the radar unit and to estimate future positions. Two particular position/state estimators are diagrammatically illustrated as part of
Referring next to
Each time a new radar scene is received (step 502) a determination is made regarding whether any of the radar object points (targets) matches the expected position and relative velocity of the back of the partner vehicle (step 504). This is preferably a probabilistic determination in which it is concluded that that there is a high probability that the “matching” target indeed represents the back of the partner vehicle. One way to determine whether a matching target is to quantify an uncertainty factor in association with the estimated position. If a radar target point is within the range of the uncertainty factor of the expected position, then it can be considered a match. As will be described in more detail below in some implementations Kalman filtering is used to estimate the position of the back of the partner vehicle and to quantify the uncertainty. Kalman filtering is particularly appropriate because it inherently adjusts the uncertainty level based on the perceived accuracy of the measurements.
If more than one of the reported radar target points match the estimated position within the range defined by the uncertainty factor (sometimes referred to as a ball of uncertainty), then the closest radar object point identified in the radar scene is treated as the “matching” target. In the context of this determination, the “closest” match may be selected based on a combination of metrics including longitudinal position, lateral position, relative speeds, etc.
If a match is found, the radar tracker transmits the distance to the matched object and relative speed of the matched object to the gap controller 112 as the current gap to and relative speed of, the back of partner vehicle (step 506). In some embodiments, the only information transmitted is the longitudinal distance to the back of the trailer and its relative speed. This is because while currently available radar units are generally quite good at measuring distance and relative speed, they are not as good at precisely measuring lateral velocities or providing precise lateral position information regarding identified objects. However, if the radar unit used can accurately measure other useful attributes of the target such as lateral velocities, acceleration, etc.,—that information may optionally be transmitted as well.
When a match is found, the best matched target is used to update the radar tracking position and speed estimate for the back of the truck as well (step 508). The position and speed estimate is then propagated in time to the position expected for the next radar sample in step 510. That is, the logic estimates the expected position of the back of the truck at the time the next radar sample is expected. This is a relatively simple matter since the radar samples are provided at regular intervals so the timing of the next expected sample is easy to determine. For example, if the radar sample rate is 20 Hz, the next sample can be expected to occur 0.05 seconds after the last sample. If the front and rear vehicles are traveling at exactly the same velocity and both vehicles are traveling in the same direction, than the “expected” position of the back of the front vehicle would be exactly the same as the last detected position of the back of the front vehicle. However, often vehicles will be traveling at slightly different speeds and possibly in slightly different directions if one of the vehicles is turned or turning slightly relative to the other. For example, using a simple example, if the trailing vehicle is moving in exactly the same direction as the lead vehicle at a constant velocity of 1.00 meters per second faster than the lead vehicle, then the back of the lead vehicle would be expected to be 5 cm closer to the lead vehicle at the time the next radar sample is taken (0.05 seconds after the last sample was taken). Simple trigonometry may be used to determine the expected position if the vehicles are turned or turning slightly with respect to one another. Of course, any number of other relevant variables that are known to or obtainable by the radar system controller can be considered in the calculation of the expected position and speed to further improve the estimates. These might include the respective accelerations (measured or estimated) of the vehicles, the respective directions of travel and/or rates of turn of the two vehicles, etc. Factors that may influence the velocity, acceleration or rate of turn of the vehicles such as the respective vehicles torque requests, the current grade, the vehicle weights, etc. may also be used to further refine the estimate.
In addition to propagating the position estimate in time, the uncertainty estimate is updated as represented by block 512 as described in more detail below.
After the position estimate has been propagated in time and the uncertainty estimate has been updated, the process repeats for the next sample as represented in the flow chart of
As suggested above, the platoon system preferably utilizes multiple independent or partially-independent mechanisms for tracking the position and speed, of the respective vehicles. For example, as discussed above, the platoon controller may have access to GPS position data which provides an independent mechanism for determining the relative positions of the platooning vehicles. The platoon controller may also have access to wheel speed data which provides an alternative mechanism for determining the respective speeds, and thus the relative speed of the platoon partners. Such data for the host vehicle is available from the host vehicle sensors. Data for the partner vehicles is available over the communications link (e.g. the DSRC link, a cellular link or any other available communication method).
Each time that a new GPS position estimates are received (as represented by box 520 in
The GPS position, wheel speed and inertial measurements are preferably updated on a relatively rapid basis—which is often (although not necessarily) more frequent than the radar samples. By way of example, GPS update frequencies in the range of 25 to 500 Hz, as for example 50 Hz have been found to work well for open road platoon control applications. Similar wheel speed and inertial measurement update frequencies have also been found to work well—although there is no need to update the GPS positions, wheel speed and/or inertial measurements at the same sample rate as each other, or at the same sample rate as the radar unit.
In the embodiment shown, the updates from the radar unit, the GPS sensors, the wheel speed sensor and inertial measurements are handled asynchronously as they are received. Although not required, this is useful to help ensure that the latest sensor inputs are utilized in estimating the expected relative positions and speeds of the platooning vehicles at the time the next radar unit scene sample is received. This is contrasted with a system in which the wheel speed sensor and GPS sensor information is updated once each sample of the radar unit. Although synchronous updates can also work well, the use of asynchronous updates tends to improve the accuracy of the estimates because various sensor inputs can be updated more frequently than the radar unit sampling rate.
Although the different types of measurements do not need to be synchronized with one another, the same types of measurements on the different trucks are preferably synchronized in time. That is, GPS position measurements on the front truck are preferably synchronized in time with GPS position measurements on the back truck so that the relative positions of the trucks can be determined at a particular instant in time. Similarly, the wheel speed measurements on the front truck are preferably synchronized in time with wheel speed measurements on the back truck so that the relative speeds of the trucks can be determined at a particular instant in time. The various inertial measurements are also preferably synchronized with each other as well.
It should be appreciated that it is relatively simple to coordinate the timing of the various measurements between vehicles because GPS is used and the vehicles communicate with one another over the communications link. As is well known, the GPS system provides very accurate global timing signals. Thus, the clocks used for the platoon partners can be synchronized with the GPS signals and the various measurements (e.g. GPS position measurements, wheel speed measurements, inertial measurements, etc.) can therefore be instructed to occur at specific synchronized times on the respective trucks. Each measurement may also be accompanied by a timestamp that indicates when the measurement was taken so that the synchronization of the measurements can be verified (or accounted for if similar sensor measurements are not synchronized between vehicles).
The propagation of the estimated position in time is particularly useful in step 504 which utilizes the then current estimate of the position of the back of the lead vehicle to determine whether any of the received radar sample object points (targets) match the expected position of the back of the partner vehicle. It should be appreciated that there may be times when no radar sample targets match the expected position of the back of the partner vehicle as represented by the “no” branch from decision 504. In such cases the radar system controller still propagates the position estimate in time (step 510) so that the position estimate is updated for the next radar sample based on the other information the controller has. Such other information includes the then current estimates and may be further updated based on inputs from other systems (e.g., the GPS or wheel speed sensor) as previously discussed.
There are some operational circumstances where one or more measurements might be expected to be suspect. For example, when a host vehicle is shaken unusually hard—as may occur when a wheel runs over a pothole or encounters other unusual roughness in the road—the radar unit will be shaken accordingly and any radar measurement samples taken at that instant are less likely to be accurate and/or useful to the model. Other sensors such as the wheel speed and inertial measurement sensor are less likely to be accurate at such times as well. In another example, when the lead truck is aggressively braking it is more likely that its trailer will move back and forth more than usual which again suggests that any radar samples taken during such braking are less likely to be useful for predicting the future position of the back of the trailer. When the controller detects, or is informed, that an event is occurring that makes the measurements of any particular sensor suspect, the measurements from such sensor(s) can safely be ignored in the context of the position estimate. In such circumstances inputs from other sensors deemed more reliable (if any) may continue to be used to update the position model and the position estimate may continue to be propagated in time for each subsequent sample. The uncertainty associated with position estimate can be expected to increase slightly with each ignored sample, which has the effect of increasing the variation from the estimated position of the back of the partner vehicle that would be tolerated when determining whether there is a target that matches the expected position of the back of the partner vehicle.
The position model described above is relatively simple in that it utilizes a relatively small set of measured inputs including (1) the received radar scenes (which show the relative position and relative velocity of detected objects); (2) measured GPS positions of the platoon partners (which can be used to determine their relative positions); (3) measured wheel speeds of the platoon partners (which can be used to determine their relative speeds); and (4) measured yaw rate and orientation. In other embodiments, when different or additional types of sensor information is available to the radar controller, the position model can be adapted to utilize whatever relevant information is available to it in the position estimates. For example, if the pitch or roll of the vehicles are available, the position model can incorporate such measurements into the position estimates. The roll can be useful because on trucks the GPS antennas tend to be located on top of the cabs at locations over 4 meters above the ground (e.g. 14-15 feet). At such heights, even relatively small tilting in the roll direction can cause the reported position of the respective vehicles to vary significantly. The pitch can be useful for similar reasons. For example, with a platooning gap of 15 meters, a difference in pitch of just ±2 degrees can result in a difference of a meter in the apparent or detected height of an object. At further distances and/or larger pitch variations, those differences are amplified. Since many radar units used in platooning systems have relatively narrow views this can lead to expected objects not being detected, or detected objects being discarded, because they are further from the estimated position than expected when pitch is not considered. Similarly, if longitudinal and/or angular accelerations are available, the position model can incorporate the acceleration measurements into the position estimates.
In embodiments in which the relative positioning and/or speed and/or orientation of the vehicles can relatively accurately be measured using other systems such as LIDAR, sonar, other time of flight distance sensors, sensors configured to receive a signal transmitted from another vehicle, cameras, stereo cameras or other appropriate technologies, those measurements can be incorporated into the position model in addition to, or in place of, the GPS, wheel speed and inertial measurements.
In some embodiments, the position model can be considerably more sophisticated using inputs such a torque requests, braking signals and/or other operational information about the respective platoon partners to further refine the predicted position at the time of the next radar sample.
In the primary described embodiment the radar sample object points are compared to the estimated (expected) position and relative speed of the back of the partner vehicle. In other embodiments, more or fewer parameters can be compared to identify a match. For example, in some embodiments matches (or lack thereof) may be based on matching the expected position of the partner vehicle rather than position and speed/velocity. If the radar unit is capable of reliably reporting other information such as acceleration, rates of lateral movement, etc., then such information can also be compared to corresponding estimates as part of the match identification 504.
A significant advantage of the described approach is that the relative position and velocity estimates can reliably continue even when the back of the platoon partner is outside the view of the radar unit—as may sometimes be the case when the lead vehicle changes to a different lane, an interloper cuts in between the platooning vehicles, or a transitory fault occurs with the radar unit. With such tracking, radar identification of the platoon partner can more easily be reestablished when the back of the platoon partner comes back into the radar unit's view. As will be appreciated by those familiar with the art, this is very different than adaptive cruise control systems that utilize radar only to track the distance to the vehicle directly in front of the host vehicle—regardless of who that leading vehicle may be.
It is noted that the histogram and/or mean shift clusters described above with respect to
A noteworthy feature of the method described with respect to
Kalman Filtering
The method described with respect to
The state variables used in the Kalman filter may vary widely with the nature of the model used. One particular state array (X) suitable for use in some of the described embodiments that involve a pair of platooning tractor-trailer trucks includes:
(1) the longitudinal position of the center of the rear axles of the front truck relative to the center of the rear axles of the back truck (x);
(2) the lateral position of the center of the rear axle of the front truck relative to the center of the rear axles of the back truck (y);
(3) the heading of the front truck relative to the heading of the trailing truck (χ);
(4) the speed of the lead vehicle (v1); and
(5) the speed of the trailing vehicle (v2).
This can be represented mathematically as follows:
The estimated state at the time of the next radar sample (Xk+1) is a function of the previous state (Xk) and a covariance matrix (Pk) indicative of the level of uncertainty in the measurements. A covariance matrix corresponding to the state array (X) represented above is illustrated in
Xk+1=AXk+BUk
One particular control input array (U) includes:
(1) the yaw rate of the front vehicle (ψ1); and
(2) the yaw rate of the rear vehicle (ψ2)
This can be represented mathematically as follows:
Although specific state and modeled input arrays are illustrated, it should be appreciated that the specific state and control input variables used in any particular implementation may vary widely based on the nature of the estimation model used.
Kalman filtering is particularly well adapted to making the types of position and velocity estimations useful in the techniques described herein. Although Kalman filtering works particularly well, it should be appreciated that other state/space estimation algorithms, such as Particle Filtering, etc. can be used in alternative embodiments.
One of the reasons that Kalman filtering works well is that most of the measurements, including the GPS measurements, the radar measurements, the wheel speed measurements and the inertial measurements tend to be subject to varying measurement errors. For example, it is not uncommon for any particular GPS measurement to be off by more than a meter. The covariance matrix (Pk) quantifies the statistical variation (error) observed in the measurements and utilizes that knowledge to improve the quality of the position and speed estimates.
Integrating Other Information into Sensor Data Verification
In the embodiments described above, information about the state of the partner vehicle that is received from the partner vehicle is used by the host to help verify or confirm that data from a sensor on the host vehicle that is believed to measure a characteristic of the partner vehicle is actually representative of the partner vehicle. For example, in some of the described embodiments, information from a lead vehicle about its position, speed, orientation etc. is used by a radar scene processor on the trailing vehicle to predict an expected position and speed of the lead vehicle. Those predictions are then used to help determine which (if any) of the detected radar objects correspond to the lead vehicle. The state information received from the lead vehicle may be a measured value (such as a measure wheel speed) or a predicted value (such as a predicted speed) which may be even more reliable in circumstances in which the parameter (e.g., speed) is changing.
It should be appreciated that a wide variety of other information/data received from the partner vehicle can additionally or alternatively be used to further help with such verification. This can include other partner vehicle state information such as the partner vehicle's: current torque request; braking status (including the status of the foundation brakes, a retarder, engine braking and/or any other braking device in the context of larger trucks); or steering angle. The information can also include a status indicator such as an indication that a blinker, the hazard lights, the taillights or other lights are on. It can also include qualitative information about the partner vehicle such as its radar signature, or its visual appearance (e.g. its color, a identifying marker, or some other feature or characteristic that can be readily identified by one of the controllers on the host vehicle). It can also include information about an intended or expected action—such as notification that the lead vehicle is about to change lanes, will take the next exit or turn at the next intersection.
In some circumstances, the host vehicle may request that the partner vehicle take specific actions to help with such identification. The nature of such a request may vary widely—for example, the rear truck may request that the lead truck turn on specific lights, switch lanes, accelerate or decelerate to a specific speed, honk its horn, etc.
Additionally, it should be appreciated that additional information about the partner vehicle can also be obtained from a third vehicle, a larger mesh of vehicles or from another external source. For example a third vehicle travelling in parallel with the platoon partners may have measured the position, velocity and/or other characteristics of the partner vehicle and that information can be used as another independent check. In another example, a network operations center (NOC) in communication with both platoon partners may know the intended route and communicate that route, or more short term directions to the host vehicle as appropriate. In other circumstances information from the partner vehicle may be transmitted via an intermediary such as a third vehicle, a NOC, etc. Any of this type of data can be useful—and some of the information may be particularly helpful in circumstance in which communications between the vehicles is temporarily lost.
Although only a few embodiments of the inventions have been described in detail, it should be appreciated that the inventions may be implemented in many other forms without departing from the spirit or scope of the invention. The inventions have been described primarily in the context of a pair of trucks platooning with a forward facing radar unit being located at the front of the trailing truck. However, it should be appreciated that the same concepts can be applied to any types of vehicles operating in any type of connected vehicle applications, regardless of where the radar unit is located on the vehicle and/or the direction (or directions) that the radar unit(s) interrogates. Thus, for example, a backward facing radar unit on a lead vehicle can be used to identify and/or track following vehicles using radar in substantially the same manner as described. Similarly if omni-directional radar is used, similar approaches can be used to identify and/or track other vehicles using radar regardless of their position relative to the host vehicle.
As suggested above, the described radar based vehicle identification and tracking can be used in any type of connected vehicle application in which independent information about the position and/or velocity of one or more other vehicles is known or available to the unit interpreting the radar data. Thus, for example, the described techniques are particularly well suited for use in convoying systems involving more than two vehicles. Also, the described techniques are very well adapted for use in autonomous vehicle traffic flow applications where knowledge about the intentions of other specific vehicles is deemed important. Indeed, this is expected to be an important application of the inventions with the growth of the autonomous and connected vehicle markets.
The inventions have been described primarily in the context of identifying and tracking other vehicles using commercially available radar units designed for use in driving automation systems. Such units are typically designed to analyze the received radar energy and identify objects that are believed to the radar manufacturer to be relevant. Although the described inventions work well with such units, they are not so constrained. Rather, both the vehicle identification and vehicle tracking processes are well suited for use with radar units that don't filter the response as much and report the reflected radar signal intensities in a more general way rather than attempting to identify particular objects. In particular, the statistical nature of the radar return binning and the back of vehicle detection are quite well suited for using radar data provided in other forms such as intensity/location. Furthermore, the invention is not limited to distance measurement systems using electromagnetic energy in the frequency range of radar. Rather, it should be appreciated that the same target vehicle identification and/or tracking techniques may readily be used in conjunction with other electromagnetic energy based distance measuring technologies such as LIDAR which utilize electromagnetic energy in different frequency ranges, sound based distance measurement (e.g., sonar, ultrasound, etc.) or various time of flight based distance measuring systems. The described techniques can also be used in conjunction with distance measuring techniques using cameras or stereo cameras, beacon based technologies in which the sensor measures a beacon signal transmitted from the partner vehicle and/or other technologies.
In some implementations, the platooning vehicles may have mechanisms such as transponders suitable for identifying themselves to the radar unit. When available, information from such devices can be used to further assist with the identification and tracking of the platoon partner.
Therefore, the present embodiments should be considered illustrative and not restrictive and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
The present application is a continuation-in-part of PCT Application No. PCT/US2016/060167, filed on Nov. 2, 2016, which claims priority of U.S. Provisional Patent Application No. 62/249,898, filed on Nov. 2, 2015. Additionally, the present application is a Continuation-in-Part of U.S. application Ser. No. 14/292,583 filed May 30, 2014, which is a Divisional of U.S. application Ser. No. 13/542,622 filed Jul. 5, 2012 (now U.S. Pat. No. 8,744,666) and Ser. No. 13/542,627 also filed Jul. 5, 2012 (now U.S. Pat. No. 9,582,006), both of which claim priority of U.S. Provisional Patent Application No. 61/505,076, filed Jul. 6, 2011. All of these priority applications are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3725921 | Weidman et al. | Apr 1973 | A |
| 4317117 | Chasek | Feb 1982 | A |
| 4370718 | Chasek | Jan 1983 | A |
| 5166881 | Akasu | Nov 1992 | A |
| 5295551 | Sukonick | Mar 1994 | A |
| 5331561 | Barrett et al. | Jul 1994 | A |
| 5572449 | Ting et al. | Nov 1996 | A |
| 5633456 | Stander | May 1997 | A |
| 5680122 | Mio | Oct 1997 | A |
| 5777451 | Kobayashi et al. | Jul 1998 | A |
| 5781119 | Yamashita et al. | Jul 1998 | A |
| 5815825 | Tachibana et al. | Sep 1998 | A |
| 5880958 | Helms et al. | Mar 1999 | A |
| 6032097 | Iihoshi et al. | Feb 2000 | A |
| 6125321 | Tabata et al. | Sep 2000 | A |
| 6128559 | Saitou et al. | Oct 2000 | A |
| 6188950 | Tsutsumi et al. | Feb 2001 | B1 |
| 6265990 | Isogai et al. | Jul 2001 | B1 |
| 6285929 | Hashimoto | Sep 2001 | B1 |
| 6314366 | Farmakis et al. | Nov 2001 | B1 |
| 6345603 | Abboud et al. | Feb 2002 | B1 |
| 6356820 | Hashimoto et al. | Mar 2002 | B1 |
| 6370475 | Breed et al. | Apr 2002 | B1 |
| 6397149 | Hashimoto | May 2002 | B1 |
| 6418370 | Isogai et al. | Jul 2002 | B1 |
| 6484078 | Kageyama | Nov 2002 | B1 |
| 6510381 | Grounds et al. | Jan 2003 | B2 |
| 6604038 | Lesesky et al. | Aug 2003 | B1 |
| 6633006 | Wolf et al. | Oct 2003 | B1 |
| 6765495 | Dunning et al. | Jul 2004 | B1 |
| 6879910 | Shike et al. | Apr 2005 | B2 |
| 6898585 | Benson et al. | May 2005 | B2 |
| 6963795 | Haissig et al. | Nov 2005 | B2 |
| 6975246 | Trudeau | Dec 2005 | B1 |
| 7286825 | Shishido et al. | Oct 2007 | B2 |
| 7460951 | Altan et al. | Dec 2008 | B2 |
| 7554435 | Tengler et al. | Jun 2009 | B2 |
| 7593811 | Schmidt et al. | Sep 2009 | B2 |
| 7596811 | Schmidt et al. | Sep 2009 | B2 |
| 7729823 | Ruoppolo | Jun 2010 | B2 |
| 7782227 | Boss et al. | Aug 2010 | B2 |
| 7831345 | Heino et al. | Nov 2010 | B2 |
| 7894982 | Reeser et al. | Feb 2011 | B2 |
| 8026833 | Villaume et al. | Sep 2011 | B2 |
| 8073574 | Yamamoto et al. | Dec 2011 | B2 |
| 8116921 | Ferrin et al. | Feb 2012 | B2 |
| 8139109 | Broggi et al. | Mar 2012 | B2 |
| 8224551 | Grolle et al. | Jul 2012 | B2 |
| 8275491 | Ferrin et al. | Sep 2012 | B2 |
| 8326473 | Simpson et al. | Dec 2012 | B2 |
| 8352111 | Mudalige | Jan 2013 | B2 |
| 8352112 | Mudalige | Jan 2013 | B2 |
| 8354955 | Miyake et al. | Jan 2013 | B2 |
| 8442735 | Hrovat et al. | May 2013 | B2 |
| 8538656 | Yamashiro | Sep 2013 | B2 |
| 8554468 | Bullock | Oct 2013 | B1 |
| 8618922 | Debouk et al. | Dec 2013 | B2 |
| 8620517 | Caveney et al. | Dec 2013 | B2 |
| 8660779 | Shida | Feb 2014 | B2 |
| 8666587 | Anderson | Mar 2014 | B2 |
| 8676466 | Mudalige | Mar 2014 | B2 |
| 8682511 | Andreasson | Mar 2014 | B2 |
| 8688349 | Grolle et al. | Apr 2014 | B2 |
| 8738238 | Rekow | May 2014 | B2 |
| 8744666 | Switkes | Jun 2014 | B2 |
| 8775060 | Solyom et al. | Jul 2014 | B2 |
| 8798907 | Shida | Aug 2014 | B2 |
| 8947531 | Fischer et al. | Feb 2015 | B2 |
| 8948995 | Pandita et al. | Feb 2015 | B2 |
| 8954272 | Adam et al. | Feb 2015 | B2 |
| 8970401 | Molander et al. | Mar 2015 | B2 |
| 8992391 | Seastrom et al. | Mar 2015 | B2 |
| 9037389 | You | May 2015 | B2 |
| 9079587 | Rupp | Jul 2015 | B1 |
| 9141112 | Loo et al. | Sep 2015 | B1 |
| 9145137 | Doi et al. | Sep 2015 | B2 |
| 9174672 | Zeng et al. | Nov 2015 | B2 |
| 9182764 | Kolhouse et al. | Nov 2015 | B1 |
| 9221396 | Zhu et al. | Dec 2015 | B1 |
| 9224300 | Lee et al. | Dec 2015 | B2 |
| 9355423 | Slusar | May 2016 | B1 |
| 9367065 | Dolgov et al. | Jun 2016 | B2 |
| 9396661 | Okamoto | Jul 2016 | B2 |
| 9412271 | Sharma | Aug 2016 | B2 |
| 9423794 | Lind et al. | Aug 2016 | B2 |
| 9449258 | Palacio et al. | Sep 2016 | B1 |
| 9460622 | Ferguson et al. | Oct 2016 | B1 |
| 9494944 | Alam et al. | Nov 2016 | B2 |
| 9511764 | Pilutti et al. | Dec 2016 | B2 |
| 9582006 | Switkes et al. | Feb 2017 | B2 |
| 9598078 | Moran et al. | Mar 2017 | B2 |
| 9613466 | Bullock | Apr 2017 | B1 |
| 9616743 | Mays et al. | Apr 2017 | B1 |
| 9632507 | Korn | Apr 2017 | B1 |
| 9645579 | Switkes et al. | May 2017 | B2 |
| 9665102 | Switkes et al. | May 2017 | B2 |
| 9721474 | Eskilson | Aug 2017 | B2 |
| 9771070 | Zagorski et al. | Sep 2017 | B2 |
| 9799224 | Okamoto | Oct 2017 | B2 |
| 9823166 | Dudar et al. | Nov 2017 | B2 |
| 9852475 | Konrardy et al. | Dec 2017 | B1 |
| 9878657 | Wunsche, III et al. | Jan 2018 | B2 |
| 9884631 | James et al. | Feb 2018 | B2 |
| 9927816 | Li et al. | Mar 2018 | B2 |
| 9928746 | MacNeille et al. | Mar 2018 | B1 |
| 9940840 | Schubert et al. | Apr 2018 | B1 |
| 10013877 | Lu et al. | Jul 2018 | B2 |
| 10017039 | Colavincenzo | Jul 2018 | B1 |
| 10017179 | Alden et al. | Jul 2018 | B2 |
| 10027024 | Powell | Jul 2018 | B2 |
| 10031522 | Moran et al. | Jul 2018 | B2 |
| 20010001138 | Zhu et al. | May 2001 | A1 |
| 20020077748 | Nakano | Jun 2002 | A1 |
| 20020135507 | Winner et al. | Sep 2002 | A1 |
| 20020152015 | Seto | Oct 2002 | A1 |
| 20020198632 | Breed et al. | Dec 2002 | A1 |
| 20030094858 | Shiue et al. | May 2003 | A1 |
| 20030225517 | Schiffmann | Dec 2003 | A1 |
| 20040046448 | Brown | Mar 2004 | A1 |
| 20040078133 | Miller et al. | Apr 2004 | A1 |
| 20040140143 | Saeki | Jul 2004 | A1 |
| 20040245853 | Odagawa et al. | Dec 2004 | A1 |
| 20040252863 | Chang et al. | Dec 2004 | A1 |
| 20060074557 | Mulligan et al. | Apr 2006 | A1 |
| 20060095195 | Nishimura et al. | May 2006 | A1 |
| 20060106534 | Kawamata et al. | May 2006 | A1 |
| 20060161341 | Haegebarth et al. | Jul 2006 | A1 |
| 20060195250 | Kawaguchi | Aug 2006 | A1 |
| 20060229804 | Schmidt | Oct 2006 | A1 |
| 20070005609 | Breed | Jan 2007 | A1 |
| 20070021915 | Breed et al. | Jan 2007 | A1 |
| 20070027614 | Reeser et al. | Feb 2007 | A1 |
| 20070032245 | Alapuranen | Feb 2007 | A1 |
| 20070043502 | Mudalige et al. | Feb 2007 | A1 |
| 20070060045 | Prautzsch | Mar 2007 | A1 |
| 20070083318 | Parikh | Apr 2007 | A1 |
| 20070210953 | Abraham et al. | Sep 2007 | A1 |
| 20070213915 | Tange | Sep 2007 | A1 |
| 20070233337 | Plishner | Oct 2007 | A1 |
| 20070256481 | Nishiyama et al. | Nov 2007 | A1 |
| 20070276597 | Kato et al. | Nov 2007 | A1 |
| 20080009985 | Plishner | Jan 2008 | A1 |
| 20080033649 | Hasegawa et al. | Feb 2008 | A1 |
| 20080059007 | Whittaker et al. | Mar 2008 | A1 |
| 20080119965 | McCrary | May 2008 | A1 |
| 20080122652 | Tengler et al. | May 2008 | A1 |
| 20080147253 | Breed | Jun 2008 | A1 |
| 20080154629 | Breed et al. | Jun 2008 | A1 |
| 20080249667 | Horvitz et al. | Oct 2008 | A1 |
| 20080255722 | McClellan et al. | Oct 2008 | A1 |
| 20080258890 | Follmer et al. | Oct 2008 | A1 |
| 20090012666 | Simpson et al. | Jan 2009 | A1 |
| 20090051510 | Follmer et al. | Feb 2009 | A1 |
| 20090062974 | Tamamoto et al. | Mar 2009 | A1 |
| 20090079839 | Fischer et al. | Mar 2009 | A1 |
| 20090118889 | Heino et al. | May 2009 | A1 |
| 20090157461 | Wright et al. | Jun 2009 | A1 |
| 20090164082 | Kobayashi et al. | Jun 2009 | A1 |
| 20090198427 | Christopher et al. | Aug 2009 | A1 |
| 20090219161 | Kocher | Sep 2009 | A1 |
| 20090222186 | Jensen | Sep 2009 | A1 |
| 20090271083 | Kumar | Oct 2009 | A1 |
| 20090286648 | Vesenjak | Nov 2009 | A1 |
| 20090287412 | Menzel et al. | Nov 2009 | A1 |
| 20090326799 | Crook | Dec 2009 | A1 |
| 20100044998 | Franchineau | Feb 2010 | A1 |
| 20100045507 | Yamano et al. | Feb 2010 | A1 |
| 20100049374 | Ferrin et al. | Feb 2010 | A1 |
| 20100094509 | Luke et al. | Apr 2010 | A1 |
| 20100106356 | Trepagnier et al. | Apr 2010 | A1 |
| 20100191449 | Iwamoto | Jul 2010 | A1 |
| 20100194638 | Rivard | Aug 2010 | A1 |
| 20100256835 | Mudalige | Oct 2010 | A1 |
| 20100256836 | Mudalige | Oct 2010 | A1 |
| 20100256852 | Mudalige | Oct 2010 | A1 |
| 20100332101 | Braunberger | Dec 2010 | A1 |
| 20110010022 | Beavin | Jan 2011 | A1 |
| 20110083011 | DiCrescenzo | Apr 2011 | A1 |
| 20110093177 | Horn | Apr 2011 | A1 |
| 20110112730 | Rekow | May 2011 | A1 |
| 20110118967 | Tsuda | May 2011 | A1 |
| 20110184596 | Andreasson | Jul 2011 | A1 |
| 20110184605 | Neff | Jul 2011 | A1 |
| 20110210872 | Molander | Sep 2011 | A1 |
| 20110270514 | Shida | Nov 2011 | A1 |
| 20110270520 | Kronenberg | Nov 2011 | A1 |
| 20110274523 | Petalas | Nov 2011 | A1 |
| 20110301779 | Shida | Dec 2011 | A1 |
| 20120061154 | Pfister | Mar 2012 | A1 |
| 20120086582 | Durekovic et al. | Apr 2012 | A1 |
| 20120089294 | Fehse et al. | Apr 2012 | A1 |
| 20120105270 | Miyake et al. | May 2012 | A1 |
| 20120109421 | Scarola | May 2012 | A1 |
| 20120109610 | Anderson et al. | May 2012 | A1 |
| 20120139549 | Sufrin-Disler et al. | Jun 2012 | A1 |
| 20120166057 | Amato et al. | Jun 2012 | A1 |
| 20120206282 | Gorbold | Aug 2012 | A1 |
| 20120221235 | Prudhomme-Lacroix et al. | Aug 2012 | A1 |
| 20120226965 | Hammerschmidt et al. | Sep 2012 | A1 |
| 20120252415 | Menzel et al. | Oct 2012 | A1 |
| 20120259516 | Grolle et al. | Oct 2012 | A1 |
| 20120259538 | Oexmann | Oct 2012 | A1 |
| 20120323474 | Breed et al. | Dec 2012 | A1 |
| 20130015984 | Yamashiro | Jan 2013 | A1 |
| 20130018766 | Christman | Jan 2013 | A1 |
| 20130024084 | Yamashiro | Jan 2013 | A1 |
| 20130030606 | Mudalige et al. | Jan 2013 | A1 |
| 20130030657 | Chatterjee et al. | Jan 2013 | A1 |
| 20130041567 | Yamashiro | Feb 2013 | A1 |
| 20130041576 | Switkes et al. | Feb 2013 | A1 |
| 20130066511 | Switkes et al. | Mar 2013 | A1 |
| 20130079953 | Kumabe | Mar 2013 | A1 |
| 20130080040 | Kumabe | Mar 2013 | A1 |
| 20130080041 | Kumabe | Mar 2013 | A1 |
| 20130090803 | Stahlin et al. | Apr 2013 | A1 |
| 20130116861 | Nemoto | May 2013 | A1 |
| 20130124064 | Nemoto | May 2013 | A1 |
| 20130144465 | Shida | Jun 2013 | A1 |
| 20130144502 | Shida | Jun 2013 | A1 |
| 20130151058 | Zagorski et al. | Jun 2013 | A1 |
| 20130158852 | Stahlin et al. | Jun 2013 | A1 |
| 20130165146 | Stahlins et al. | Jun 2013 | A1 |
| 20130173114 | Pillai | Jul 2013 | A1 |
| 20130211624 | Lind et al. | Aug 2013 | A1 |
| 20130218365 | Caveney et al. | Aug 2013 | A1 |
| 20130231820 | Solyom et al. | Sep 2013 | A1 |
| 20130317676 | Cooper | Nov 2013 | A1 |
| 20130325306 | Caveney et al. | Dec 2013 | A1 |
| 20140005875 | Hartmann et al. | Jan 2014 | A1 |
| 20140005906 | Pandita et al. | Jan 2014 | A1 |
| 20140019031 | Solyom et al. | Jan 2014 | A1 |
| 20140067220 | Seiler | Mar 2014 | A1 |
| 20140100734 | Yamashiro | Apr 2014 | A1 |
| 20140107867 | Yamashiro | Apr 2014 | A1 |
| 20140129075 | Carleton | May 2014 | A1 |
| 20140136044 | Conrad | May 2014 | A1 |
| 20140142799 | Ferguson et al. | May 2014 | A1 |
| 20140142801 | Shah | May 2014 | A1 |
| 20140145838 | Tuukkanen | May 2014 | A1 |
| 20140148994 | Ando | May 2014 | A1 |
| 20140156118 | Wiemeyer et al. | Jun 2014 | A1 |
| 20140172265 | Funabashi | Jun 2014 | A1 |
| 20140197967 | Modica et al. | Jul 2014 | A1 |
| 20140210645 | Sharma | Jul 2014 | A1 |
| 20140214255 | Dolgov et al. | Jul 2014 | A1 |
| 20140222278 | Fujita | Aug 2014 | A1 |
| 20140236449 | Horn | Aug 2014 | A1 |
| 20140244144 | You | Aug 2014 | A1 |
| 20140249693 | Stark et al. | Sep 2014 | A1 |
| 20140277608 | Debouk et al. | Sep 2014 | A1 |
| 20140297063 | Shida | Oct 2014 | A1 |
| 20140303870 | Switkes | Oct 2014 | A1 |
| 20140306799 | Ricci | Oct 2014 | A1 |
| 20140306826 | Ricci | Oct 2014 | A1 |
| 20140309836 | Ollis | Oct 2014 | A1 |
| 20140316671 | Okamoto | Oct 2014 | A1 |
| 20140316865 | Okamoto | Oct 2014 | A1 |
| 20140324339 | Adam et al. | Oct 2014 | A1 |
| 20140350756 | Schoonmaker et al. | Nov 2014 | A1 |
| 20140350793 | Schrabler | Nov 2014 | A1 |
| 20140350835 | Martin | Nov 2014 | A1 |
| 20150012204 | Breuer et al. | Jan 2015 | A1 |
| 20150015267 | Mueller et al. | Jan 2015 | A1 |
| 20150025731 | Uehara | Jan 2015 | A1 |
| 20150045993 | Cooper et al. | Feb 2015 | A1 |
| 20150061492 | Braunberger | Mar 2015 | A1 |
| 20150100192 | Lee et al. | Apr 2015 | A1 |
| 20150120137 | Zeng et al. | Apr 2015 | A1 |
| 20150151737 | Birch et al. | Jun 2015 | A1 |
| 20150153733 | Ohmura et al. | Jun 2015 | A1 |
| 20150154871 | Rothoff et al. | Jun 2015 | A1 |
| 20150161894 | Duncan et al. | Jun 2015 | A1 |
| 20150262481 | Selin | Sep 2015 | A1 |
| 20150274161 | Stierlin | Oct 2015 | A1 |
| 20150279122 | Lorenzen | Oct 2015 | A1 |
| 20150296019 | Onishi et al. | Oct 2015 | A1 |
| 20150314790 | Deragarden et al. | Nov 2015 | A1 |
| 20150334371 | Galera et al. | Nov 2015 | A1 |
| 20150356635 | Thurston | Dec 2015 | A1 |
| 20150378722 | Zuniga-Hernandez | Dec 2015 | A1 |
| 20160009284 | Tokimasa et al. | Jan 2016 | A1 |
| 20160009288 | Yu | Jan 2016 | A1 |
| 20160019782 | Alam et al. | Jan 2016 | A1 |
| 20160026187 | Alam et al. | Jan 2016 | A1 |
| 20160039412 | Stahlin | Feb 2016 | A1 |
| 20160054735 | Switkes | Feb 2016 | A1 |
| 20160170021 | Rashid et al. | Jun 2016 | A1 |
| 20160194014 | Rajendran | Jul 2016 | A1 |
| 20160198303 | Grotendorst et al. | Jul 2016 | A1 |
| 20160267796 | Hiroma et al. | Sep 2016 | A1 |
| 20160272207 | Dolgov et al. | Sep 2016 | A1 |
| 20160297447 | Suzuki | Oct 2016 | A1 |
| 20160300186 | Scharaswak et al. | Oct 2016 | A1 |
| 20160359741 | Cooper et al. | Dec 2016 | A1 |
| 20160373261 | Tschache et al. | Dec 2016 | A1 |
| 20160375732 | Lazar et al. | Dec 2016 | A1 |
| 20170011633 | Boegel | Jan 2017 | A1 |
| 20170058477 | Niroumand | Mar 2017 | A1 |
| 20170069203 | Sharma | Mar 2017 | A1 |
| 20170083844 | Baker et al. | Mar 2017 | A1 |
| 20170115666 | Kolhouse et al. | Apr 2017 | A1 |
| 20170122841 | Dudar et al. | May 2017 | A1 |
| 20170132299 | Fox et al. | May 2017 | A1 |
| 20170146801 | Stempora | May 2017 | A1 |
| 20170168503 | Amla et al. | Jun 2017 | A1 |
| 20170178536 | Manci et al. | Jun 2017 | A1 |
| 20170186327 | Uysal et al. | Jun 2017 | A1 |
| 20170197544 | Wang et al. | Jul 2017 | A1 |
| 20170197615 | Elie et al. | Jul 2017 | A1 |
| 20170212511 | Ferreira et al. | Jul 2017 | A1 |
| 20170227972 | Sabau | Aug 2017 | A1 |
| 20170235316 | Shattil | Aug 2017 | A1 |
| 20170238321 | Sartori et al. | Aug 2017 | A1 |
| 20170242095 | Schuh et al. | Aug 2017 | A1 |
| 20170242443 | Schuh et al. | Aug 2017 | A1 |
| 20170261997 | Switkes et al. | Sep 2017 | A1 |
| 20170287233 | Nix | Oct 2017 | A1 |
| 20170289864 | Narasimha et al. | Oct 2017 | A1 |
| 20170293296 | Stenneth et al. | Oct 2017 | A1 |
| 20170308097 | Switkes et al. | Oct 2017 | A1 |
| 20170309187 | Lin | Oct 2017 | A1 |
| 20170323244 | Rani et al. | Nov 2017 | A1 |
| 20170329348 | Li et al. | Nov 2017 | A1 |
| 20170344023 | Laubinger et al. | Nov 2017 | A1 |
| 20170349058 | Bernier et al. | Dec 2017 | A1 |
| 20170349176 | Alden et al. | Dec 2017 | A1 |
| 20170361762 | Wunsche, III et al. | Dec 2017 | A1 |
| 20180006365 | Powell | Jan 2018 | A1 |
| 20180018605 | Light-Holets et al. | Jan 2018 | A1 |
| 20180032072 | Hoye | Feb 2018 | A1 |
| 20180047293 | Dudar | Feb 2018 | A1 |
| 20180050697 | Kuszmaul et al. | Feb 2018 | A1 |
| 20180082590 | MacNeille et al. | Mar 2018 | A1 |
| 20180082591 | Pandy | Mar 2018 | A1 |
| 20180084511 | Wu et al. | Mar 2018 | A1 |
| 20180111611 | MacNeille et al. | Apr 2018 | A1 |
| 20180120861 | Saxena et al. | May 2018 | A1 |
| 20180137763 | Deragarden et al. | May 2018 | A1 |
| 20180188725 | Cremona et al. | Jul 2018 | A1 |
| 20180188745 | Pilkington | Jul 2018 | A1 |
| 20180188746 | Lesher et al. | Jul 2018 | A1 |
| 20180190119 | Miller, Jr. et al. | Jul 2018 | A1 |
| 20180190128 | Saigusa | Jul 2018 | A1 |
| 20180210461 | Cremona et al. | Jul 2018 | A1 |
| 20190068582 | Kim et al. | Feb 2019 | A1 |
| 20190073908 | Neubecker et al. | Mar 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 10 2007 058 192 | Jun 2009 | DE |
| 102011002275 | Oct 2012 | DE |
| 3316064 | May 1918 | EP |
| 0 982 173 | Mar 2000 | EP |
| 0 991 046 | Mar 2005 | EP |
| 1 975 901 | Mar 2009 | EP |
| 2 390 744 | Nov 2011 | EP |
| 2540039 | Jan 1917 | GB |
| 2551248 | Dec 1917 | GB |
| 2557001 | Jun 1918 | GB |
| 2557434 | Jun 1918 | GB |
| 2558051 | Jul 1918 | GB |
| 2017-215681 | Dec 1917 | JP |
| 05-170008 | Jul 1993 | JP |
| 2995970 | Dec 1999 | JP |
| 2010-30525 | Feb 2010 | JP |
| 2014-056483 | Mar 2012 | JP |
| 5141849 | Feb 2013 | JP |
| WO 2016087555 | Jun 1916 | WO |
| WO 2016182489 | Nov 1916 | WO |
| WO 2016201435 | Dec 1916 | WO |
| WO 2017048165 | Mar 1917 | WO |
| WO 2017070714 | Apr 1917 | WO |
| WO 2017148113 | Sep 1917 | WO |
| WO 2017164792 | Sep 1917 | WO |
| WO 2017179193 | Oct 1917 | WO |
| WO 2017184062 | Oct 1917 | WO |
| WO 2017184063 | Oct 1917 | WO |
| WO 2017196165 | Nov 1917 | WO |
| WO 2017200433 | Nov 1917 | WO |
| WO 2017204712 | Nov 1917 | WO |
| WO 2017209124 | Dec 1917 | WO |
| WO 2017209666 | Dec 1917 | WO |
| WO 2018000386 | Jan 1918 | WO |
| WO 2018035145 | Feb 1918 | WO |
| WO 2018043519 | Mar 1918 | WO |
| WO 2018043520 | Mar 1918 | WO |
| WO 2018043753 | Mar 1918 | WO |
| WO 2018054520 | Mar 1918 | WO |
| WO 2018106774 | Jun 1918 | WO |
| WO 2018111177 | Jun 1918 | WO |
| WO 2018135630 | Jul 1918 | WO |
| WO 2018137754 | Aug 1918 | WO |
| WO 2004077378 | Sep 2004 | WO |
| WO 2009024563 | Feb 2009 | WO |
| WO 2009043643 | Apr 2009 | WO |
| WO 2009071345 | Jun 2009 | WO |
| WO 2010098554 | Sep 2010 | WO |
| WO 2011125193 | Oct 2011 | WO |
| WO 2013006826 | Jan 2013 | WO |
| WO 2013165297 | Apr 2013 | WO |
| WO 2013147682 | Oct 2013 | WO |
| WO 2013187835 | Dec 2013 | WO |
| WO 2014062118 | Apr 2014 | WO |
| WO 2014092628 | Jun 2014 | WO |
| WO 2014133425 | Sep 2014 | WO |
| WO 2014137270 | Sep 2014 | WO |
| WO 2014137271 | Sep 2014 | WO |
| WO 2014145918 | Sep 2014 | WO |
| WO 2015047174 | Apr 2015 | WO |
| WO 2015047175 | Apr 2015 | WO |
| WO 2015047176 | Apr 2015 | WO |
| WO 2015047177 | Apr 2015 | WO |
| WO 2015047178 | Apr 2015 | WO |
| WO 2015047179 | Apr 2015 | WO |
| WO 2015047181 | Apr 2015 | WO |
| WO 2015047182 | Apr 2015 | WO |
| WO 2015156731 | Oct 2015 | WO |
| WO 2016065055 | Apr 2016 | WO |
| WO 2016087901 | Jun 2016 | WO |
| WO 2016134610 | Sep 2016 | WO |
| WO 2016134770 | Sep 2016 | WO |
| WO 2016135207 | Sep 2016 | WO |
| WO 2017070714 | Apr 2017 | WO |
| Entry |
|---|
| Kuszmaul et al., U.S. Appl. No. 15/605,456, filed May 25, 2017. |
| Klaus et al., U.S. Appl. No. 15/860,024, filed Jan. 3, 2018. |
| Switkes et al., International Application No. PCT/US17/47771, filed on Aug. 21, 2017. |
| Browand et al., “Fuel Saving Achieved in the Field Test of Two Tandem Trucks”, California PATH Research Report, UCB-ITS-PRR-2001-20, Jun. 2004. |
| Shladover et al., “Demonstration of Automated Heavy-Duty Vehicles”, California PATH Research Report, UCB-ITS-PRR-2005-23, Jun. 2005. |
| Shladover et al., “Development and Evaluation of Selected Mobility Applications for VII (a.k.A. IntelliDrive)”, http://slideplayer.com/slide/6981587/, Jul. 1, 2009. |
| Tsugawa, “An Overview on an Automated Truck Platoon Within the Energy ITS Project”, 7th IFAC Symposium on Advances in Automotive Control, Tokyo, Japan, Sep. 4-7, 2013. |
| Sugimachi et al., “Development of Autonomous Platooning System for Heavy-Duty Trucks”, 7th IFAC Symposium on Advances in Automotive Control, Tokyo, Japan, Sep. 4-7, 2013. |
| Sheikholeslam et al., “Longitudinal Control of a Platoon of Vehicles; III; Nonlinear Model”, Program on Advanced Technology for the Highway, Institute of Transportation Studies, University of California at Berkeley, Apr. 1, 1990. |
| Sheikholeslam et al., “Longitudinal Control of a Platoon of Vehicles”, Department of Electrical Engineering and Computer Science, University of California, Berkeley, May 1990. |
| Sheikholeslam et al., “A System Level Study of the Longitudinal Control of a Platoon of Vehicles”, Department of Electrical Engineering and Computer Science, University of California, Berkeley, Jun. 1992. |
| Porche et al., “Real Time Task Manager for Communications and Control in Multicar Platoons”, Department of Electrical Engineering and Computer Science, University of California, Berkeley, Jun. 1992. |
| Gerdes et al., “Brake System Requirements for Platooning on an Automated Highway”, Department of Mechanical Engineering, University of California, Berkeley, Jun. 1995. |
| Zabat et al., “The Aerodynamic Performance of Platoons: Final Report”, California PATH Research Report, California PATH Program, Institute of Transportation Studies, University of California, Berkeley, Oct. 1995. |
| Gerdes et al., “Vehicle Speed and Spacing Control via Coordinated Throttle and Brake Actuation”, Department of Mechanical Engineering, University of California, Berkeley, Sep. 1997. |
| Alvarez et al., “Safe Platooning in Automated Highway Systems Part I: Safety Regions Design”, Department of Mechanical Engineering, University of California, Berkeley, 1999. |
| Alvarez et al., “Safe Platooning in Automated Highway Systems Part II: Velocity Tracking Controller”, Department of Mechanical Engineering, University of California, Berkeley, 1999. |
| Michaelian et al., “Field Experiments Demonstrate Fuel Savings for Close-Following”, University of Southern California, California PATH Research Report, Sep. 2000. |
| Simon Halle, “Automated Highway Systems: Platoons of Vehicles Viewed as a Multiagent System”, University of Quebec, Jun. 2005. |
| Friedrichs et al., “A Generic Software Architecture for a Driver Information System to Organize and Operate Truck Platoons”, https://www.researchgate.net/publication/256195846, May 2008. |
| Meisen et al., “A Data-Mining Technique for the Planning and Organization of Truck Platoons”, https://www.researchgate.net/publication/256195756, May 2008. |
| Ramakers et al., “Electronically Coupled Truck platoons on German Highways”, IEEE International Conference on Systems, Man, and Cybernetics, San Antonio, TX, Oct. 2009. |
| Kunze et al., “Organization and Operation of Electronically Coupled Truck Platoons on German Highways”, RWTH Aachen University, Center for Learning and Knowledge Management and Department of Information Management in Mechanical Engineering, Aachen, Germany, Dec. 2009. |
| Kunze et al., “Efficient Organization of Truck Platoons by Means of Data Mining”, 7th International Conference on Informatics in Control, Automation and Robotics, RWTH Aachen University, Center for Learning and Knowledge Management and Department of Information Management in Mechanical Engineering, Aachen, Germany, Jan. 2010. |
| Jacobson et al., “Functional Safety in Systems of Road Vehicles”, SP Technical Research Institute of Sweden, Jul. 2010. |
| Nowakowski et al., “Cooperative Adaptive Cruise Control: Testing Driver's Choices of Following Distances”, California PATH Program, Institute of Transportation Studies, University of California, Berkeley, Jan. 2011. |
| Tsugawa et al., “An Automated Truck Platoon for Energy Saving”, IEEE/RSJ International Conference on Intelligent Robots and Systems, San Francisco, CA, Sep. 25-30, 2011. |
| Desjardins et al., “Cooperative Adaptive Cruise Control: A Reinforcement Learning Approach”, IEEE Transactions on Intelligent Transportation Systems, vol. 12, No. 4, Dec. 2011. |
| Larson et al., “Coordinated Route Optimization for Heavy-duty Vehicle Platoons”, Proceedings of the 16th International IEEE Annual Conference on Intelligent Transportation Systems (ITSC 2013), The Hague, The Netherlands, Oct. 6-9, 2013. |
| Aoki, “Research and Development of Fully Automated Vehicles”, ITS Research Division, Japan Automobile Research Institute, Tokyo, Japan, Nov. 2013. |
| Lu et al., “Automated Truck Platoon Control and Field Test, Road Vehicle Automation”, https://www.researchgate.net/publication/266390502, Aug. 2014. |
| White Paper, “Automated Driving and Platooning Issues and Opportunities”, ATA Technology and Maintenance Council Future Truck Program, Sep. 21, 2015. |
| Nowakowski et al., “Cooperative Adaptive Cruise Control (CACC) for Truck Platooning: Operational Concept Alternatives”, California PATH, California Partners for Advanced Transportation Technology, UC Berkeley, Mar. 2015. |
| Erlien, “Shared Vehicle Control Using Studies Safe Driving Envelopes for Obstacle Avoidance and Stability”, A Dissertation submitted to the Department of Mechanical Engineering and the Committee on Graduate Studies of Stanford University, Mar. 2015. |
| Shladover et al., “Cooperative Adaptive Cruise Control, Definitions and Operating Concepts”, Transportation Research Record 2489, 2015. |
| Tsugawa et al., “A Review of Truck Platooning Projects for Energy Savings”, IEEE Transactions on Intelligent Vehicles, vol. 1, No. 1, Mar. 2016. |
| Geiger et al., “Team AnnieWAY's Entry to the 2011 Grand Cooperative Driving Challenge”, IEEE Transactions on Intelligent Transportation Systems, vol. 13, No. 3, Sep. 2012. |
| Bergenheim et al., “Vehicle-to-Vehicle Communication for a Platooning System”, SP Technical Research Institute of Sweden, Procedia—Social and Behavioral Sciences vol. 48, 2012. |
| Bae et al., “Road Grade and Vehicle Parameter Estimation for Longitudinal Control Using GPS”, 2001 IEEE Intelligent Transportation Systems Conference Proceedings, Oakland, CA, Aug. 25-29, 2001. |
| Holm, “Vehicle Mass and Road Grade Estimation Using Kalman Filter”, MSc Thesis, Department of Electrical Engineering, Sweden, Aug. 2011. |
| Kidambi et al., “Methods in Vehicle Mass and Road Grade Estimation”, SAE International, University of Michigan, Apr. 1, 2014. |
| Paulsson et al., “Vehicle Mass and Road Grade Estimation Using Recursive Least Squares”, MSc Thesis, Lund University, 2016. |
| Montvey, et al., Priority Document associated with EP Application No. 03 100457.5., Feb. 25, 2003. |
| Schuh et al., U.S. Appl. No. 15/590,715, filed May 9, 2017. |
| International Search Report and Written Opinion dated Feb. 23, 2018 from International Application No. PCT/US2017/058477. |
| Bergenheim et al., “Overview of Platooning Systems”, http://publications.lib.chalmers.se/records/fulltext/174621.pdf, 2012. |
| Schuh et al., U.S. Appl. No. 15/936,271, filed Mar. 26, 2018. |
| Switkes et al., U.S. Appl. No. 15/926,809, filed Mar. 20, 2018. |
| Switkes et al., U.S. Appl. No. 15/926,813, filed Mar. 20, 2018. |
| Switkes et al., U.S. Appl. No. 15/926,805, filed Mar. 20, 2018. |
| Switkes et al., U.S. Appl. No. 15/908,677, filed Feb. 28, 2018. |
| Switkes et al., U.S. Appl. No. 15/908,745, filed Feb. 28, 2018. |
| U.S. Office Action dated Jun. 19, 2018 from U.S. Appl. No. 15/936,271. |
| Alam et al., “An Experimental Study on the Fuel Reduction Potential of Heavy Duty Vehicle Platooning”, 2010 13th International IEEE, Annual Conference on Intelligent Transportation Systems, Sep. 19-22, 2010. |
| U.S. Final Office Action dated Sep. 5, 2018 from U.S. Appl. No. 15/936,271. |
| “Automated Highway System: Milestone 2 Report, Task C2: Downselect System Configurations and Workshop #3” (National Automated Highway System Consortium, Troy, MI, Jun. 1997), 604 pages. |
| Wille, Matthias et al., “KONVOI: Electronically coupled truck convoys”, in Human Factors for Assistance and Automation, D. de Waard et al. (Eds.) (Shaker Publishing, Maastricht, the Netherlands, Jan. 2008), pp. 243-256. |
| Shladover, Steven E. et al. “Development and Evaluation of Selected Mobility Applications for VII: Concept of Operations”, California PATH Working Paper UCB-ITS-PWP-2009-3 (U.C. Berkeley, Berkeley, CA, Mar. 2009), 14 pages. |
| Shladover, Steven E. et al., “Development and Evaluation of Selected Mobility Applications for VII”, California PATH Research Report UCB-ITS-PRR-2011-09, (U.C. Berkeley, Jun. 2011), 109 pages. |
| Al Alam, Assad et al. “Establishing Safety for Heavy Duty Vehicle Platooning: A Game Theoretical Approach”, Proceedings of the 18th World Congress, The International Federation of Automatic Control (IFAC'11) Milano, Italy, Sep. 2011, pp. 3818-3823. |
| Roeth, Michael, “CR England Peloton Technology Platooning Test Nov. 2013”, (North American Council on Freight Efficiency (NACFE.org), Fort Wayne, IN, Dec. 2013);Retrieved Aug. 23, 2018 at https://nacfe.org/wp-content/uploads/2018/02/Peloton-NACFE-Fuel-Test-Report-120213.pdf. |
| Bevly, David et al. “Heavy Truck Cooperative Adaptive Cruise Control: Evaluation, Testing, and Stakeholder Engagement for Near Term Deployment: Phase One Final Report”, Report to Federal Highway Administration (Auburn University, Auburn, AL, Apr. 2015), 135 pages; Retrieved Aug. 23, 2018 at http://atri-online.org/wp-content/uploads/2015/05/DATPPhase1FinalReport.pdf. |
| Nowakowski, Christopher et al., “Heavy vehicle automation: Human factors lessons learned”, Procedia Manufacturing vol. 3, Jul. 2015, pp. 2945-2952. |
| Zhao, Siyang et al., “Vehicle to Vehicle Communication and Platooning for EV with Wireless Sensor Network”, SICE Annual Conference 2015, Hangzhou, China, Jul. 2015, pp. 1435-1440. |
| Brizzolara, Davide & Toth, Andrea, “The Emergence of Truck Platooning”, Baltic Transport Journal, Mar. 2016, pp. 58-59. |
| European Patent No. 3316064—an English abstract of which is included. |
| Japanese Publication No. 2014-056483—a computerized English translation of which is included. |
| Japanese Publication No. 2017-215681—a computerized English translation of which is included. |
| International Publication No. WO 2016/087555—a English abstract of which is included. |
| International Publication No. WO 2017/148113—an English abstract of which is included. |
| International Publication No. WO 2017/209124—a computerized English translation of which is included. |
| International Publication No. WO 2018/000386—a computerized English translation of which is included. |
| International Publication No. WO 2018/043519—a computerized English translation of which is included. |
| International Publication No. WO 2018/043520—a computerized English translation of which is included. |
| International Publication No. WO 2018/043753—a computerized English translation of which is included. |
| International Publication No. WO 2018/054520—a computerized English translation of which is included. |
| International Publication No. WO 2018/135630—a computerized English translation of which is included. |
| U.S. Final Office Action dated Feb. 12, 2019 from U.S. Appl. No. 15/936,271. |
| International Search Report and Written Opinion dated Dec. 24, 2018 from International Application No. PCT/US2018/023723. |
| U.S. Office Action dated Nov. 26, 2018 from U.S. Appl. No. 15/936,271. |
| U.S. Office Action dated May 9, 2019 from U.S. Appl. No. 15/936,271. |
| Number | Date | Country | |
|---|---|---|---|
| 20170242095 A1 | Aug 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62249898 | Nov 2015 | US | |
| 61505076 | Jul 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13542622 | Jul 2012 | US |
| Child | 14292583 | US | |
| Parent | 13542627 | Jul 2012 | US |
| Child | 14292583 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2016/060167 | Nov 2016 | US |
| Child | 15590803 | US | |
| Parent | 14292583 | May 2014 | US |
| Child | PCT/US2016/060167 | US |
