CROSS-REFERENCE TO RELATED APPLICATION
BACKGROUND
[0002] Radar is often used in vehicles to support a variety of driver assist and autonomous
driving functionalities. Radar systems that are upstream of these functions produce
radar detections from received radar reflections and place the detections within a
buffer that is accessed by functions of a vehicle. The downstream functions receive
the detections from the buffer and perform their respective operations. Often times,
a radar buffer becomes saturated (e.g., full) with detections corresponding to close
and large objects. Some of the objects (or portions thereof) may not be of particular
importance to downstream functions. As such, the buffer may be full of unimportant
detections; certain important detections may not have space within the buffer and,
thus, are never processed by the downstream functions. In addition, certain more-meaningful
detections may be processed later than they otherwise could be (e.g., because they
can only be stored when space becomes available) or simply not be processed at all.
SUMMARY
[0003] Aspects described below include a method, performed by a processor of a vehicle,
of radar detection prioritization based on downstream feedback. The method includes
receiving radar detections as the vehicle is traveling in a travel corridor, the radar
detections having associated locations relative to the vehicle. The method further
includes receiving, from another processor of the vehicle, feedback related to a downstream
function executed by the other processor as the vehicle is traveling in the travel
corridor and determining, based on the locations of the radar detections and the feedback
related to the downstream function, whether any of the radar detections are within
the travel corridor. For at least one of the radar detections that are within the
travel corridor, the method also includes assigning a priority to the at least one
of the radar detections, the priority being dependent on the locations of the at least
one of the radar detections and the feedback related to the downstream function. For
the at least one of the radar detections that are within the travel corridor, the
method further includes storing, in a detection buffer, the at least one of the radar
detections along with an indication of the assigned priority.
[0004] Aspects described below also include a system, configured to be implemented in a
vehicle, for radar detection prioritization based on downstream feedback. The system
comprises a processor and computer-readable storage media comprising instructions
that, when executed by the processor, cause the processor to receive radar detections
as the vehicle is traveling in a travel corridor. The radar detections having associated
locations relative to the vehicle. The instructions further cause the processor to
receive, from another processor of the vehicle, feedback related to a downstream function
executed by the other processor as the vehicle is traveling in the travel corridor
and determine, based on the locations of the radar detections and the feedback related
to the downstream function, whether any of the radar detections are within the travel
corridor. The instructions also cause the processor to, for at least one of the radar
detections that are within the travel corridor, assign a priority to the at least
one of the radar detections, the priority being dependent on the locations of the
at least one of the radar detections and the feedback related to the downstream function.
The instructions further cause the processor to store, in a detection buffer, the
at least one of the radar detections along with an indication of the assigned priority.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Systems and techniques enabling radar detection prioritization based on downstream
feedback are described with reference to the following drawings. The same numbers
are used throughout the drawings to reference like features and components:
Fig. 1 is an example illustration of an environment in which radar detection prioritization
based on downstream feedback may be implemented, in accordance with techniques of
this disclosure;
Fig. 2 is an example illustration of a system configured to perform radar detection
prioritization based on downstream feedback, in accordance with techniques of this
disclosure;
Fig. 3 is an example illustration of radar detection prioritization based on downstream
feedback, in accordance with techniques of this disclosure;
Fig. 4 is another example illustration of radar detection prioritization based on
downstream feedback, in accordance with the techniques of this disclosure; and
Fig. 5 is an example illustration of a method of radar detection prioritization based
on downstream feedback, in accordance with the techniques of this disclosure.
DETAILED DESCRIPTION
Overview
[0006] Radar is often used to support a wide variety of driver assist and autonomous driving
functions. Many times, radar detections of objects (e.g., radar returns) are placed
within a buffer for downstream processing. Downstream functions then pull the detections
from the buffer to perform various operations. As long as there is room in the buffer,
the detections can be added without issue. When the buffer is full, however, radar
systems may wait until space is freed (e.g., detections are pulled by the downstream
functions) prior to adding new detections.
[0007] This can lead to processing of important detections being delayed or even missed.
Because the storing of the detections in the buffer is uninfluenced, the buffer may
become full of detections that are not particularly relevant to the downstream operations.
For example, the buffer may become saturated with detections of an upcoming bridge
even though it may not be relevant to a downstream function (e.g., speed control using
a leading vehicle). As such, the buffer may be unable to store detections indicative
of slow-moving traffic ahead, which may be more-relevant to the downstream operations
than the bridge detections. By not influencing the storage of the detections, processing
of important detections may be delayed or simply missed. This can lead to unsafe driving
conditions, decreased safety, and diminished driver satisfaction.
[0008] Methods and systems are described that enable radar detection prioritization based
on downstream feedback. Radar detections are received as a vehicle is traveling in
a travel corridor, the radar detections having associated locations relative to the
vehicle. Feedback related to a downstream function is received from another processor
as the vehicle is traveling in the travel corridor, and it is determined, based on
the locations and feedback, whether any of the radar detections are within the travel
corridor. For at least one of the radar detections that are within the travel corridor,
a priority is assigned based on the locations of the at least one of the radar detections
and the feedback related to the downstream function. The at least one of the radar
detections are then stored in a detection buffer along with an indication of the assigned
priority. In this way, the detection buffer may be optimized for the downstream function
by filtering out certain detections and prioritizing others. The downstream function
can process detections that matter most for driving safety and situational awareness,
without being burdened evaluating less important detections. Consequently, because
the downstream function's receipt of important detections is expedited, computational
loads on the downstream function are reduced.
Example Environment
[0009] Fig. 1 is an example illustration 100 of an environment in which radar detection
prioritization based on downstream feedback may be implemented. The example illustration
100 shows a radar system 102 of a system (not shown) that is within a vehicle 104.
The vehicle 104 is traveling in a travel corridor 106 that may correspond to a portion
of a roadway that the vehicle 104 is traveling on. For example, the travel corridor
106 may correspond to a portion of the roadway that corresponds to a same direction
of travel as the vehicle 104 (e.g., one side of a roadway). The travel corridor 106
may be defined by extents 108 (e.g., barriers, fences, guardrails, or edges of pavement/concrete)
on the lateral edges of the travel corridor 106.
[0010] As the vehicle 104 traverses through the travel corridor 106, radar detections (detections
110) are received. The detections 110 comprise information, derived from radar reflections,
about objects 112 (or portions thereof) proximate to the vehicle 104. For example,
detection 110-1 corresponds to object 112-1 (e.g., an overpass support), detection
110-2 corresponds to object 112-2 (e.g., another overpass support), and the detection
110-3 corresponds to object 112-3 (e.g., another vehicle). The detections 110 have
associated locations relative to the vehicle 104 and movement information.
[0011] It should be noted that the detections 110 are merely representations of the respective
objects 112 (or portions thereof). That is, the detections 110 themselves do not have
locations or movement data; rather, the corresponding objects 112 do. For the sake
of simplicity, detections 110 are used herein. For example, by stating that a detection
110 is moving, it should be understood that an object (or portion thereof) to which
the detection 110 corresponds is moving.
[0012] The radar system 102 uses feedback received from a downstream function to prioritize
the detections 110. For example, the radar system 102 may use the feedback to determine
which of the detections 110 are outside of the travel corridor 106. The radar system
102 may then refrain from placing those detections 110 that are outside of the travel
corridor 106 into a detection buffer for processing by the downstream function. For
the detections 110 that are within the travel corridor 106, the radar system 102 may
prioritize the detections 110 and place them within the detection buffer for processing
by the downstream function.
[0013] For example, in the example illustration 100, by using conventional techniques, the
detection buffer may become full or saturated with detections 110-1 and 110-2 corresponding
to the overpass because it is large and close to the vehicle. In this case, detection
110-3 corresponding to the other vehicle may not be able to be stored within the detection
buffer. In many cases, a detection of a moving object within the travel corridor 106
(the other vehicle) can be more important than a static object outside of the travel
corridor 106 (the overpass). Thus, by using the techniques described herein, the detection
buffer may be optimized for relevancy (e.g., by not storing the detections 110-1 and
110-2 while storing the detection 110-3) while reducing a computational load on the
downstream function. Doing so may enable certain detections 110 to be processed earlier,
leading to increased safety and driver satisfaction.
Example System
[0014] Fig. 2 is an example illustration 200 of a system 202 in which radar detection prioritization
based on downstream feedback may be implemented. The system 202 is configured to be
disposed in the vehicle 104. Although the vehicle 104 is illustrated as a car, the
vehicle 104 may comprise any vehicle (e.g., a truck, a bus, a boat, a plane, etc.)
without departing from the scope of this disclosure. As shown underneath, the system
202 includes the radar system 102 and an environment-perception system 204. The radar
system 102 and the environment-perception system 204 are shown as having respective
processors 206 (e.g., 206-1 and 206-2) and respective computer-readable storage media
208 (e.g., 208-1 and 208-2). In some implementations, the radar system 102 and the
environment-perception system 204 may share a processor 206 and/or a computer-readable
storage medium 208.
[0015] The processors 206 (e.g., application processors, microprocessors, digital-signal
processors (DSP), or controllers) execute instructions 210 (e.g., code) stored within
the computer-readable storage media 208 (e.g., non-transitory storage devices such
as hard drives, SSD, flash memories, read-only memories (ROM), EPROM, or EEPROM) to
cause the radar system 102 and the environment-perception system 204 to perform the
techniques described herein.
[0016] The instructions 210 cause the radar system 102 and the environment-perception system
204 to act upon (e.g., create, receive, modify, delete, transmit, or display) data
212 (e.g., application data, module data; sensor data, or I/O data). Although shown
as being within the respective computer-readable storage media 208, portions of the
data 212 may be within a random-access memory (RAM) or a cache (not shown) of the
radar system 102 and the environment-perception system 204. Furthermore, the instructions
210 and/or the data 212 may be remote to the radar system 102 and the environment-perception
system 204.
[0017] The environment-perception system 204 is configured to provide downstream feedback
to the radar system 102 for radar detection prioritization. The radar system 102 is
configured to receive the downstream feedback from the environment-perception system
204 and use it to perform radar detection prioritization. In order to do so, the radar
system 102 may contain or interface with a radar sensor (not shown), and the environment-perception
system 204 may contain or interface with other types of sensors (e.g., lidar, imagers,
lasers, or GNSS) that are not shown.
Example Data Flows
[0018] Fig. 3 is an example illustration 300 of radar detection prioritization based on
downstream feedback. The example illustration 300 shows aspects of the radar system
102 and the environment-perception system 204. Example illustration 300 further depicts
data flows between the radar system 102 and the environment-perception system 204.
[0019] The radar system 102 contains a prioritization module 302 that receives the detections
110 and receives coefficients and constants 304 (e.g., downstream feedback) from the
environment-perception system 204. The detections 110 are generally unfiltered, not
prioritized, and may be determined by the radar system 102. The detections 110 have
associated locations (e.g., Cartesian coordinates) relative to the vehicle 104 and
velocities (e.g., range rates, relative velocities, or absolute velocities).
[0020] The prioritization module 302 uses the locations and the coefficients and constants
304 to determine prioritized detections 306, as will be discussed further in regard
to Fig. 4. The prioritized detections 306 are any of the detections 110 that have
been assigned a priority greater than zero. The prioritized detections 306 are placed,
by the prioritization module 302, into a detection buffer 308.
[0021] The detection buffer 308 may be of various structures or types, including derivatives
of buffer types, depending on application. As only one example, the detection buffer
308 may function as a first-in-first-out (FIFO) buffer, and overwrite detections that
are oldest, before overwriting any more-recent detections to make space.
[0022] In some implementations, the prioritization module 302 may only prioritize the detections
110 responsive to determining that the detection buffer 308 is full. For example,
if there is room in the detection buffer 308, the prioritization module 302 may not
prioritize the detections or place all of the detections 110 (e.g., including the
prioritized detections 306 and detections 110 that have been assigned a priority of
zero) into the detection buffer 308. Furthermore, the prioritization module 302 may,
at 310, remove priorities from the prioritized detections 306 that are within the
detection buffer 308. For example, the prioritization module 302 may occasionally
(e.g., periodically or in response to a hardware or software interrupt) remove the
priorities to re-establish a baseline for generating the feedback. Doing so periodically
(e.g. at regular intervals) keeps the detections 110 continuous.
[0023] The environment-perception system 204 is a downstream module (e.g., downstream function)
from the radar system 102. That is, the environment-perception system 204 receives
the prioritized detections 306 or pulls the prioritized detections 306 from the detection
buffer 308. The environment-perception system 204 uses the prioritized detections
306 along with other sensor data 312 (e.g., lidar, camera, sonar, GNSS, or map data)
to implement a fusion road model 314, a radar side barrier model 316, and a vision
road edge model 318. The environment-perception system 204 may contain more models/functions
than are shown/discussed herein. The non-shown models/functions may provide other
functionalities that may, but do not necessarily, contribute to the coefficients and
constants 304 for the prioritization of the detections 110.
[0024] The fusion road model 314 uses the other sensor data 312 (e.g., map data) and/or
the prioritized detections 306 to determine a polynomial representation of the travel
corridor 106 of the vehicle 104 in Cartesian coordinates according to Equation 1:

where
x and y are Cartesian coordinates (e.g.,
x is left-right of the vehicle 104 and y is back-front of the vehicle 104 while traveling
along the travel corridor 106). The coefficients
c1, c2, and
c3 correspond to heading, curvature, and curvature rate, respectively, of the travel
corridor 106, and the constant

corresponds to an extent 108 of the travel corridor 106 (e.g., an edge of a roadway).
[0025] The radar side barrier model 316 uses the prioritized detections 306 to determine
a constant

that corresponds to an extent 108 of the travel corridor 106 (e.g., a guard rail,
k-rail, or fence). The vision road edge model 318 uses the other sensor data 312 (e.g.,
camera data) to determine a constant

that corresponds to an extent 108 of the travel corridor 106 (e.g., an edge of the
pavement or concrete or foliage adjacent to the road).
[0026] Two or more of the constants

,

, and

may correspond to a same extent 108. For example, a location of a guardrail may be
represented by two of the constants (with slight differences based on the respective
models).
[0027] The coefficients
c1, c2, and
c3 and the constants

,

and

make up the coefficients and constants 304 that are fed back to the prioritization
module 302 for use in prioritizing the detections 110. It should be noted that more
or fewer of the described coefficients and constants 304 may be fed back or returned
to the prioritization module 302. For example, not all of the constants may be available
at any given time; thus, only one or two may be fed back. Furthermore, the three coefficients
are indicative of a third-order polynomial representation of the travel corridor 106.
In some implementations, a higher or lower order polynomial may be used. In such cases,
more or fewer coefficients, respectively, would be fed back.
[0028] By using downstream feedback (e.g., the coefficients and constants 304 from the environment-perception
system 204), the radar system 102 may store more relevant and prioritized detections
(e.g., prioritized detections 306) in the detection buffer 308. In doing so, downstream
functions (e.g., the environment-perception system 204) can be computationally optimized
(e.g., by not acting upon every detection 110) and able to act upon relevant detections
(e.g., prioritized detections 306) earlier. Furthermore, by only using coefficients
and at least one constant (e.g., 4-6 numbers) as the feedback, computational and memory
loads on both the environment-perception system 204 and the radar system 102 are minimized.
[0029] Fig. 4 is an example illustration 400 of radar detection prioritization based on
downstream feedback. The example illustration 400 illustrates techniques performed
by the prioritization module 302 to generate the prioritized detections 306 for storing
within the detection buffer 308.
[0030] As discussed above, the prioritization module 302 receives the detections 110 and
the coefficients and constants 304. The following is performed for each of the detections
110 (or for each of a subset of the detections 110).
[0031] At 402, the location of the detection 110 is converted from Cartesian coordinates
to Frenet coordinates 404 according to Equations 2 and 3.

where s and
l are the Frenet coordinates 404 of the detection 110 (e.g.,
l is left-right of the vehicle 104 and s is back-front of the vehicle 104),
x is the Cartesian coordinate of the detection 110, and the coefficients and constant

are those described above.
[0032] At 406, a priority is determined for the detection 110. In order to do so, the prioritization
module 302 determines, at decision 408, if the detection 110 is within the travel
corridor 106. Since the constants received from the environment-perception system
204 correspond to side extents of the roadway, the prioritization module 302 compares
the
l coordinate of the detection 110 with the constants

,

, and

. Again, not all of the constants may be received. If the
l coordinate is outside of a minimum of the constants (e.g., if
l is positive than greater than a minimum of the constants, and if
l is negative than less than a negative minimum of the constants), then it is determined
that the detection 110 is not within the travel corridor 106. In that case, the detection
110 is assigned a priority of zero, at 410. As such, the detection 110 does not become
a prioritized detection 306.
[0033] If, however, it is determined at 408 that the detection 110 is within the travel
corridor 106, the process proceeds to decision 412. At 412, the prioritization module
302 determines if the detection 110 is moving. In order to do so, the prioritization
module 302 may compare a range-rate and azimuth angle of the detection 110 with a
velocity of the vehicle 104. In some implementations, the detection 110 may already
have an associated relative velocity, absolute velocity, and/or direction relative
to the vehicle 104. If the detection 110 already has an associated absolute velocity,
for example, then the prioritization module 302 may simply determine if it is above
zero (e.g., moving).
[0034] If it is determined at 412 that the detection is not moving (e.g., it is stationary),
then the prioritization module 302 may assign, at 414, a priority to the detection
110 based on Equation 4.

where p is the priority of the detection 110, C is a calibration constant,
l is the Frenet coordinate 404 of the detection 110, and
aminor is a sensor limit in the
l direction.
[0035] If it is determined at 412 that the detection 110 is moving, then the prioritization
module 302 may assign, at 416, a priority to the detection 110 based on Equation 5.

where
A and
B are calibration constants with
A +
B = 1 and
A, B ∈ [0 1], s is the Frenet coordinate 404 of the detection 110, and
amajor is a sensor limit in the s direction.
[0036] Accordingly, the prioritization module 302 may assign a priority of zero to detections
110 that are outside of the travel corridor 106, a priority based on Equation 4 to
detections 110 that are within the travel corridor 106 and stationary, and a priority
based on Equation 5 to detections 110 that are within the travel corridor 106 and
moving. As stated above, the detections with priorities greater than zero (e.g., the
prioritized detections 306) can then be stored within the detection buffer 308. By
using the coefficients and constants 304, the prioritization module 302 can filter
the detections 110 (e.g., those with priorities of zero) and generate the prioritized
detections 306 that get stored into the detection buffer 308 in a computationally
efficient manner. Doing so enables the environment-perception system 204 to have access
to an optimized detection buffer with the most relevant detections.
Example Method
[0037] Fig. 5 is an example illustration 500 of a method for radar detection prioritization
based on downstream feedback. Example illustration 500 may be implemented utilizing
the previously described examples, such as the example illustrations 100, 300, and
400 and the system 202. Operations 502 through 510 may be performed by one or more
entities (e.g., the radar system 102 or other modules or components of the system
202). The order in which the operations are shown and/or described is not intended
to be construed as a limitation, and any number or combination of the operations can
be combined in any order to implement the method of example illustration 500 or an
alternate method.
[0038] The example illustration 500 generally starts, at 502, by a processor of a vehicle
receiving radar detections as the vehicle is traveling in a travel corridor. The radar
detections correspond to objects (or portions thereof) proximate to the vehicle as
the vehicle is traveling in the travel corridor and have corresponding locations relative
to the vehicle. For example, the processor 206-1 of the radar system 102 may receive
the detections 110 that correspond to objects 112.
[0039] At 504, feedback related to a downstream function is received from another processor
of the vehicle that is executing the downstream function as the vehicle is traveling
in the travel corridor. For example, the processor 206-1 of the radar system 102 may
receive the coefficients and constants 304 from the processor 206-2 of the environment-perception
system 204.
[0040] At 506, a determination is made as to whether any of the radar detections are within
the travel corridor. As stated above, the radar detections have characteristics that
are indicative of their respective objects. As such, the radar detections themselves
may not be within the travel corridor, per se; rather, their corresponding objects
(or portions thereof) may be within the travel corridor. For example, the prioritization
module 302 may convert coordinates of the locations, if need be (e.g., at 402), and
compare the locations of the detections 110 to the constants of the coefficients and
constants 304 (e.g., at 408) to determine if the respective detections 110 are within
the travel corridor 106.
[0041] At 508, for the radar detections that are within the travel corridor, a priority
is assigned based on the locations and feedback. For example, the prioritization module
302 may prioritize the detections 110 that are within the travel corridor 106 at 414
if the respective detections 110 are stationary or at 416 if the respective detections
110 are moving.
[0042] At 510, the radar detections that are within the travel corridor are stored within
a detection buffer along with their respective priorities. For example, the prioritization
module 302 may store the prioritized detections 306 in the detection buffer 308.
[0043] By performing the above actions, the detection buffer is optimized while reducing
computational loads on the prioritization function and the downstream function. Consequently,
important detections may be recognized sooner, thereby improving safety and driver
satisfaction.
Examples
[0044] Example 1: A method comprising: receiving, by a processor of a vehicle, radar detections
as the vehicle is traveling in a travel corridor, the radar detections having associated
locations relative to the vehicle; receiving, from another processor of the vehicle,
feedback related to a downstream function executed by the other processor as the vehicle
is traveling in the travel corridor; determining, based on the locations of the radar
detections and the feedback related to the downstream function, whether any of the
radar detections are within the travel corridor; and for at least one of the radar
detections that is within the travel corridor: assigning, by the processor, a priority
to the at least one of the radar detections, the priority being dependent on the locations
of the at least one of the radar detections and the feedback related to the downstream
function; and storing, by the processor, in a detection buffer, the at least one of
the radar detections along with an indication of the assigned priority.
[0045] Example 2: The method of example 1, further comprising: determining, by the processor,
whether the at least one of the radar detections is stationary, wherein assigning
the priority to the at least one of the radar detections is based further on whether
the at least one of the radar detections is stationary.
[0046] Example 3: The method of example 1 or 2, wherein assigning the priority to the at
least one of the radar detections is based further on one or more radar sensor limits
or one or more calibration constants.
[0047] Example 4: The method of any preceding example, wherein the travel corridor comprises
a portion of a roadway that corresponds to a direction the vehicle is traveling.
[0048] Example 5: The method of any preceding example, further comprising, providing, by
the processor, the at least one of the radar detections to the downstream function.
[0049] Example 6: The method of any preceding example, further comprising, for at least
one of the radar detections that are not within the travel corridor, refraining from
storing, in the detection buffer, the at least one of the radar detections that are
not within the travel corridor.
[0050] Example 7: The method of any preceding example, further comprising removing, by the
processor, the indication of the assigned priority from the at least one of the radar
detections that are in the detection buffer after a predetermined time.
[0051] Example 8: The method of any preceding example: wherein the locations are received
in Cartesian coordinates; further comprising converting, by the processor, the Cartesian
coordinates to Frenet coordinates based on the feedback; and wherein assigning the
priority to the at least one of the radar detections is based further on the Frenet
coordinates of the at least one of the radar detections.
[0052] Example 9: The method of example 8, wherein the feedback comprises a plurality of
coefficients and one or more constants.
[0053] Example 10: The method of example 9, wherein: the plurality of coefficients correspond
to a polynomial representation of the travel corridor; the one or more constants correspond
to lateral offsets that define extents of the travel corridor; the coefficients are
used to convert the Cartesian coordinates to the Frenet coordinates; and the constants
are used to determine whether any of the radar detections are within the travel corridor.
[0054] Example 11: A system configured to be implemented in a vehicle, the system comprising:
a processor; computer-readable storage media comprising instructions that, when executed
by the processor, cause the processor to: receive radar detections as the vehicle
is traveling in a travel corridor, the radar detections having associated locations
relative to the vehicle; receive from another processor of the vehicle, feedback related
to a downstream function executed by the other processor as the vehicle is traveling
in the travel corridor; determine, based on the locations of the radar detections
and the feedback related to the downstream function, whether any of the radar detections
are within the travel corridor; and for at least one of the radar detections that
is within the travel corridor: assign a priority to the at least one of the radar
detections, the priority being dependent on the locations of the at least one of the
radar detections and the feedback related to the downstream function; and store, in
a detection buffer, the at least one of the radar detections along with an indication
of the assigned priority.
[0055] Example 12: The system of example 11, wherein: the instructions further cause the
processor to determine whether the at least one of the radar detections is stationary;
and assigning the priority to the at least one of the radar detections is based further
on whether the at least one of the radar detections is stationary.
[0056] Example 13: The system of example 11 or 12, wherein assigning the priority to the
at least one of the radar detections is based further on one or more radar sensor
limits or one or more calibration constants.
[0057] Example 14: The system of any of examples 11-13, wherein the travel corridor comprises
a portion of a roadway that corresponds to a direction the vehicle is traveling.
[0058] Example 15: The system of any of examples 11-14, wherein the instructions further
cause the processor to provide the at least one of the radar detections to the downstream
function.
[0059] Example 16: The system of any of examples 11-15, wherein the instructions further
cause the processor to, for at least one of the radar detections that are not within
the travel corridor, refrain from storing, in the detection buffer, the at least one
of the radar detections that is not within the travel corridor.
[0060] Example 17: The system of any of examples 11-16, wherein the instructions further
cause the processor to remove the indication of the assigned priority from the at
least one of the radar detections that are in the detection buffer after a predetermined
time.
[0061] Example 18: The system of any of examples 11-17, wherein: the locations are received
in Cartesian coordinates; the instructions further cause the processor to convert
the Cartesian coordinates to Frenet coordinates based on the feedback; and assigning
the priority to the at least one of the radar detections is based further on the Frenet
coordinates of the at least one of the radar detections.
[0062] Example 19: The system of example 18, wherein the feedback comprises a plurality
of coefficients and one or more constants.
[0063] Example 20: The system of example 19, wherein: the plurality of coefficients correspond
to a polynomial representation of the travel corridor; the one or more constants correspond
to lateral offsets that define extents of the travel corridor; the coefficients are
used to convert the Cartesian coordinates to the Frenet coordinates; and the constants
are used to determine whether any of the radar detections are within the travel corridor.
[0064] Example 21: A system comprising means for performing any of examples 1-10.
[0065] Example 22: A system comprising at least one processor configured to perform any
of examples 1-10.
[0066] Example 23: Computer-readable storage media comprising instructions that, when executed
by at least one processor, cause the processor to perform any of examples 1-10.
[0067] Example 24: The method of any of examples 1-10, further comprising altering a function,
operation, or control of the vehicle based on the at least one of the radar detections.
[0068] Although implementations of radar detection prioritization based on downstream feedback
have been described in language specific to certain features and/or methods, the subject
of the appended claims is not necessarily limited to the specific features or methods
described. Rather, the specific features and methods are disclosed as example implementations
for radar detection prioritization based on downstream feedback. Further, although
various examples have been described above, with each example having certain features,
it should be understood that it is not necessary for a particular feature of one example
to be used exclusively with that example. Instead, any of the features described above
and/or depicted in the drawings can be combined with any of the examples, in addition
to or in substitution for any of the other features of those examples.
1. A method comprising:
receiving, by a processor of a vehicle, radar detections as the vehicle is traveling
in a travel corridor, the radar detections having associated locations relative to
the vehicle;
receiving, from another processor of the vehicle, feedback related to a downstream
function executed by the other processor as the vehicle is traveling in the travel
corridor;
determining, based on the locations of the radar detections and the feedback related
to the downstream function, whether any of the radar detections are within the travel
corridor; and
for at least one of the radar detections that are within the travel corridor:
assigning, by the processor, a priority to the at least one of the radar detections,
the priority being dependent on the locations of the at least one of the radar detections
and the feedback related to the downstream function; and
storing, by the processor, in a detection buffer, the at least one of the radar detections
along with an indication of the assigned priority.
2. The method of claim 1, further comprising:
determining, by the processor, whether the at least one of the radar detections is
stationary,
wherein assigning the priority to the at least one of the radar detections is based
further on whether the at least one of the radar detections is stationary.
3. The method of claim 1 or 2, wherein assigning the priority to the at least one of
the radar detections is based further on one or more radar sensor limits or one or
more calibration constants.
4. The method of claim 1, 2 or 3, wherein the travel corridor comprises a portion of
a roadway that corresponds to a direction the vehicle is traveling.
5. The method of any preceding claim, further comprising, providing, by the processor,
the at least one of the radar detections to the downstream function.
6. The method of any preceding claim, further comprising, for at least one of the radar
detections that are not within the travel corridor, refraining from storing, in the
detection buffer, the at least one of the radar detections that are not within the
travel corridor.
7. The method of any preceding claim, further comprising removing, by the processor,
the indication of the assigned priority from the at least one of the radar detections
that are in the detection buffer after a predetermined time.
8. The method of any preceding claim:
wherein the locations are received in Cartesian coordinates;
further comprising converting, by the processor, the Cartesian coordinates to Frenet
coordinates based on the feedback; and
wherein assigning the priority to the at least one of the radar detections is based
further on the Frenet coordinates of the at least one of the radar detections.
9. The method of any preceding claim, wherein the feedback comprises a plurality of coefficients
and one or more constants.
10. The method of claim 9, wherein:
the plurality of coefficients corresponds to a polynomial representation of the travel
corridor; and
the one or more constants correspond to lateral offsets that define extents of the
travel corridor.
11. The method of claim 9 or 10, wherein:
the coefficients are used to convert the Cartesian coordinates to Frenet coordinates;
and
the constants are used to determine whether any of the radar detections are within
the travel corridor.
12. The method of any preceding claim, further comprising altering a function, operation,
or control of the vehicle based on the at least one of the radar detections.
13. Computer-readable storage media comprising instructions that, when executed by at
least one processor, cause the processor to perform the method of any one of claims
1-10.
14. A system comprising at least one processor configured to perform the method of any
one of claims 1-10.
15. A system comprising means for performing the method of any one of claims 1-10.