SYSTEM AND METHOD FOR CALCULATING TURN COSTS FOR ROUTE SELECTION
The system calculates turn costs for vehicles with trailers by using map and telemetry data to select routes that minimize maneuvering difficulties and ensure safe intersection navigation.
Patent Information
- Application Number
- DE102023129283
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2023-10-25
- Publication Date
- 2024-12-05
AI Technical Summary
Vehicles towing trailers often require more space and time to navigate intersections, leading to difficulties in route planning and potential conflicts with oncoming traffic.
A system and method that calculates turn costs for route selection by using map data and vehicle telemetry to determine visibility distances, average vehicle speeds, and time ratios, considering the maneuverability of vehicles with trailers, and selects the easiest route based on these calculations.
Improves route selection by predicting the difficulty of navigating intersections with trailers, ensuring sufficient time and space for safe passage without impeding oncoming traffic.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
INTRODUCTION
[0001] The present disclosure relates to a system and method for calculating turn costs for route selection.
[0002] This introduction generally sets forth the context of the disclosure. Works of the presently named inventors, to the extent described in this introduction, as well as aspects of the description that may not be prior art at the time of filing, are neither expressly nor implicitly admitted as prior art against this disclosure.
[0003] Sometimes vehicles tow trailers. These vehicles with trailers occasionally need to enter and turn at an intersection. A vehicle towing a trailer may need more space and time to turn at an intersection than a vehicle not towing a trailer. SUMMARY
[0004] The present disclosure describes a system and method for calculating turn costs for route selection. In one aspect of the present disclosure, the method may be used for selecting a route through an intersection for a vehicle and includes receiving map data. The map data includes geometric data about the intersection of a road. The vehicle approaches the intersection on the road. The method further includes receiving vehicle telemetry data crowdsourced from a plurality of remote vehicles, the vehicle telemetry data including the speeds of the plurality of remote vehicles traveling through the road intersection; determining a sight distance using the map data; determining an average vehicle speed through the intersection using the vehicle telemetry data; determining the available time to travel through the intersection;using the sight distance and the average vehicle speed at the intersection, determining a ratio between the time available to travel through the intersection and the time required to travel through the intersection, and determining a cost value of the intersection using the ratio between the time available to travel through the intersection and the time required to travel through the intersection. The method may include selecting a route based on the cost value of the intersection and instructing the vehicle to travel the selected route autonomously. The method described in this paragraph improves vehicle engineering by determining the easiest route for the vehicle based on the difficulty of navigating the intersection.
[0005] In one aspect of the present disclosure, the method includes determining a time required for a vehicle and a trailer attached to the vehicle to exit the intersection prior to the arrival of oncoming traffic. In one aspect of the present disclosure, the method includes determining a time required for the vehicle and trailer to clear the intersection and subsequently reach a target speed without impeding oncoming traffic. The vehicle telemetry data includes a plurality of travel paths selected by the plurality of remote vehicles through the intersection.
[0006] In one aspect of the present disclosure, the method further comprises determining an average travel path through the intersection using the plurality of travel paths selected by the plurality of remote vehicles through the intersection, determining an inner travel path boundary through the intersection using the plurality of travel paths selected by the plurality of remote vehicles through the intersection, and determining an outer travel path boundary through the intersection using the plurality of travel paths selected by the plurality of remote vehicles through the intersection. In one aspect of the present disclosure, the method further comprises comparing the average travel path to the inner travel path boundary and the outer travel path boundary to determine a maneuverability cost of the intersection.In one aspect of the present disclosure, the method further includes considering the cost value for maneuverability of the intersection to determine the cost value of the intersection.
[0007] The present disclosure also describes a tangible, non-transitory, machine-readable medium containing machine-readable instructions that, when executed by a processor, cause the processor to perform the method described above.
[0008] The present disclosure also describes a system for selecting a route through an intersection. The system includes a communications transceiver and a controller that communicates with the communications transceiver. The controller is programmed to perform the method described above.
[0009] Further applicability of the present disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
[0010] The above features and advantages, as well as other features and advantages of the presently disclosed system and method, are readily apparent from the following detailed description, including the claims, and exemplary embodiments, taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] This disclosure will become more fully apparent from the detailed description and the accompanying drawings, in which: Fig. 1 is a block diagram showing one embodiment of a vehicle having a system for calculating turn costs for route selection; Fig. 2 is a flowchart of a method for determining the turn time at an intersection; and Fig. 3 is a flowchart of a method for determining turning ability in the intersection area. DETAILED DESCRIPTION
[0012] Reference will now be made in detail to several examples of the disclosure, which are illustrated in the accompanying drawings. Wherever possible, the same or similar reference numerals are used throughout the drawings and the description to refer to the same or similar parts or steps.
[0013] As in Fig. 1, a host vehicle 10 generally includes a chassis 12, a body 14, front and rear wheels 17, and may be referred to as a vehicle system. In the illustrated embodiment, the host vehicle 10 has two front wheels 17a and two rear wheels 17b. The body 14 is disposed on the chassis 12 and substantially encloses the components of the host vehicle 10. The body 14 and the chassis 12 together may form a frame. The wheels 17 are each rotatably connected to the chassis 12 near a respective corner of the body 14. The host vehicle 10 has a front axle 19 connected to the front wheels 17a and a rear axle 25 connected to the rear wheels 17b. The host vehicle 10 may be attached to a trailer 13. The methods 100 and 200 are not limited to a single trailer.Rather, methods 100 and 200 may be applied to any number of trailers towed in tandem. Host vehicle 10 and trailer 13 may collectively be referred to as vehicle system 15.
[0014] In various embodiments, the host vehicle 10 may be an autonomous vehicle or a semi-autonomous vehicle and may be considered part of a crowdsourcing turn cost calculation system 98 for route selection. The system 98 may also be referred to as the control system. In the present disclosure, the term "crowdsourcing" refers to gathering information from a plurality of remote vehicles 47. For example, the host vehicle 10 is a vehicle that is automatically controlled to transport passengers from one location to another. The host vehicle 10 is a pickup truck in the illustrated embodiment, but it should be understood that other vehicles, including trucks, sedans, coupes, sport utility vehicles (SUVs), recreational vehicles (RVs), etc., may be used.In one embodiment, the host vehicle 10 may be a so-called Level 2, Level 3, Level 4, or Level 5 automation system. A Level 4 system indicates a "high level of automation," meaning an automated driving system performs certain aspects of the dynamic driving task even if a human driver does not respond appropriately to a request for intervention. A Level 5 system means "full automation," meaning that an automated driving system fully performs aspects of the dynamic driving task under a range of road and environmental conditions that can be handled by a human driver. In Level 3 vehicles, the vehicle systems perform the entire dynamic driving task (DDT) within the range for which they are designed.The vehicle operator is only expected to be responsible for DDT fallback if the host vehicle 10 essentially "requests" the driver to take over when something goes wrong or the vehicle is about to leave the area in which it can operate. On Level 2 vehicles, the systems support steering, braking / acceleration, lane centering, and adaptive cruise control.
[0015] As illustrated, the host vehicle 10 generally includes a propulsion system 20, a transmission system 22, a steering system 24, a braking system 26, a sensor system 28, an actuation system 30, at least one data storage device 32, at least one vehicle controller 34, and a communication system 36. The propulsion system 20, in various embodiments, may include an electric machine such as a traction motor and / or a fuel cell propulsion system. The host vehicle 10 may also include a battery (or battery pack) 21 electrically connected to the propulsion system 20. Accordingly, the battery 21 is configured to store electrical energy and supply electrical energy to the propulsion system 20. In certain embodiments, the propulsion system 20 may include an internal combustion engine.The transmission system 22 is configured to transfer the power of the drive system 20 to the vehicle wheels 17 in selectable gear ratios. According to various embodiments, the transmission system 22 may include a continuously variable automatic transmission, a continuously variable transmission, or other suitable transmission. However, it is conceivable that the host vehicle 10 may not include a transmission system 22 if the drive system 20 is embodied as an electric motor. The braking system 26 is configured to transfer braking torque to the vehicle wheels 17. In various embodiments, the braking system 26 may include friction brakes, an electromechanical brake, a regenerative braking system, such as an electric machine, and / or other suitable braking systems. The steering system 24 influences the position of the vehicle wheels 17 and may include a steering wheel 33.Although a steering wheel 33 is shown for illustrative purposes, the steering system 24 may not include a steering wheel 33 in some embodiments contemplated by the present disclosure.
[0016] The sensor system 28 includes one or more sensors 40 (i.e., measuring devices) that detect observable conditions of the external environment and / or the internal environment of the host vehicle 10. The sensors 40 are in communication with the vehicle controller 34 and may include, among others, one or more radars, one or more LIDAR (Light Detection and Ranging) sensors, one or more proximity sensors, one or more odometers, one or more GPR (Ground Penetrating Radar) sensors, one or more steering angle sensors, one or more GNSS (Global Navigation Satellite System) transceivers 45 (e.g., GPS transceivers), one or more tire pressure sensors, one or more cameras (e.g.,optical cameras and / or infrared cameras), one or more gyroscopes, one or more accelerometers, one or more inclinometers, one or more speed sensors, one or more ultrasonic sensors, one or more inertial measurement units (IMUs) 41, and / or other sensors. Each sensor 40 is configured to generate a signal indicative of the sensed observable conditions of the external environment and / or the internal environment of the host vehicle 10. Since the sensor system 28 provides data to the vehicle controller 34, the sensor system 28 and its sensors 40 are considered information sources (or simply sources).
[0017] As previously mentioned, the sensor system 28 includes one or more GNSS transceivers 45 (e.g., Global Positioning System (GPS) transceivers) configured to collect and monitor the route data (i.e., route information). The GNSS transceiver 45 is configured to communicate with a GNSS to determine the position of the host vehicle 10 on the globe. The GNSS transceiver 45 is in electronic communication with the vehicle controller 34.
[0018] The actuation system 30 includes one or more actuators 42 that control one or more vehicle functions, such as, but not limited to, the drive system 20, the transmission system 22, the steering system 24, and the braking system 26. In various embodiments, the vehicle features may also include interior and / or exterior vehicle features, such as doors, a trunk, and cabin features such as ventilation, music, lighting, etc.
[0019] The data storage device 32 stores data used for the automatic control of the host vehicle 10. In various embodiments, the data storage device 32 stores defined maps of the navigable environment. In various embodiments, the defined maps may be predefined and retrieved by a remote system. For example, the defined maps may be compiled by the remote system and transmitted to the host vehicle 10 (wirelessly and / or wired) and stored in the data storage device 32. The data storage device 32 may be part of the vehicle controller 34, separate from the vehicle controller 34, or part of the vehicle controller 34 and part of a separate system.
[0020] The host vehicle 10 may also include one or more airbags 35 that communicate with the vehicle controller 34 or another controller of the host vehicle 10. The airbag 35 includes an inflatable bladder and is configured to transition between a stowed and a deployed configuration to cushion the effects of an external force applied to the host vehicle 10. The sensors 40 may include an airbag sensor, e.g., an IMU, configured to detect an external force and generate a signal indicative of the magnitude of that external force. The vehicle controller 34 is configured to command deployment of the airbag 35 based on the signal from one or more sensors 40, e.g., the airbag sensor. Accordingly, the vehicle controller 34 is configured to determine when the airbag 35 has been deployed.
[0021] The vehicle controller 34 includes at least one vehicle processor 44 and a non-transitory computer-readable vehicle storage device or medium 46. The vehicle processor 44 may be a custom processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor among multiple processors connected to the vehicle controller 34, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or generally an instruction-executing device. The computer-readable vehicle storage device or medium 46 may include volatile and non-volatile memory, such as read-only memory (ROM), random access memory (RAM), and keep-alive memory (KAM).KAM is a persistent or non-volatile memory that can be used to store various operating variables while the vehicle processor 44 is powered off. The vehicle computer-readable storage device or medium 46 can be implemented using a variety of storage devices such as PROMs (programmable read-only memories), EPROMs (electrical PROMs), EEPROMs (electrically erasable PROMs), flash memory, or other electrical, magnetic, optical, or combination storage devices capable of storing data, some of which are executable instructions used by the vehicle controller 34 in controlling the host vehicle 10. The vehicle controller 34 of the host vehicle 10 can be programmed to execute the methods 100 and 400 described in detail below.
[0022] The instructions may comprise one or more separate programs, each containing an ordered list of executable instructions for implementing logical functions. When executed by the vehicle processor 44, the instructions receive and process signals from the sensor system 28, perform logic, calculations, methods, and / or algorithms to automatically control the components of the host vehicle 10, and generate control signals for the actuation system 30 to automatically control the components of the host vehicle 10 based on the logic, calculations, methods, and / or algorithms. Although in Fig. 1 illustrates a single vehicle controller 34, embodiments of the host vehicle 10 may include a plurality of vehicle controllers 34 that communicate and cooperate via a suitable communication medium or combination of communication media to process the sensor signals, perform logic, calculations, methods and / or algorithms, and generate control signals to automatically control functions of the host vehicle 10.
[0023] In various embodiments, one or more instructions from the vehicle controller 34 are implemented in the control system 98. The host vehicle 10 has a user interface 23, which may be a touchscreen in the dashboard. The user interface 23 may include, among other things, an alarm system, e.g., one or more speakers 27 for generating an audible tone, haptic feedback on a vehicle seat or other object, one or more displays 29, one or more microphones 31, and / or other devices suitable for providing notification to the vehicle user of the host vehicle 10. The user interface 23 is in electronic communication with the vehicle controller 34 and is configured to receive input from a user (e.g., a vehicle user or a vehicle occupant).The user interface 23 may, for example, include a touchscreen and / or buttons configured to receive inputs from a vehicle user 11. Accordingly, the vehicle controller 34 is configured to receive user inputs via the user interface 23. The host vehicle 10 may include one or more displays 29 configured to display information to the user (e.g., the vehicle driver or passenger).
[0024] The communication system 36 is in communication with the vehicle controller 34 and is configured to wirelessly communicate information to and from one or more remote servers 48, such as, but not limited to, remote systems in a remote call center (e.g., ON-STAR from GENERAL MOTORS). The remote server 48 may be a cloud-based system. In the present disclosure, the term "remote server" refers to computer hardware or software (computer program) that provides functionality to other programs or devices, called "clients." In this case, the clients are remote vehicles 47 and the host vehicle 10. In the present disclosure, the term "remote vehicle" means a vehicle that is not physically connected to the host vehicle or the remote server 48.As used herein, the term "remote server" refers to a server that is not physically connected to the host vehicle 10 and / or the remote vehicles 47. The remote server 48 may include a server controller 49 and a non-transitory computer-readable server storage device or medium 51.
[0025] The server processor 49 may be a custom processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor among multiple processors connected to the vehicle controller 34, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or generally an instruction-executing device. The computer-readable server storage device or medium 51 may include volatile and non-volatile memory, such as read-only memory (ROM), random access memory (RAM), and keep-alive memory (KAM). KAM is persistent or non-volatile memory that can be used to store various operating variables while the vehicle processor 44 is powered off.The computer-readable server storage device or medium 51 may be implemented using a variety of storage devices such as PROMs (programmable read-only memories), EPROMs (electrical PROMs), EEPROMs (electrically erasable PROMs), flash memory, or other electrical, magnetic, optical, or combination storage devices capable of storing data, some of which may be executable instructions used by the control system 98. The remote server 48 may also include communications transceivers 37 for wirelessly transmitting data to the host vehicle 10 and / or the remote vehicles 47. The server controller 49 may be programmed to perform the method 200 described in detail below.
[0026] In certain embodiments, the communication system 36 of the host vehicle 10 is a wireless communication system configured to communicate via a wireless local area network (WLAN) using IEEE 802.11 standards or via cellular data communication. Accordingly, the communication system 36 may include one or more antennas and / or communication transceivers 37 for receiving and / or transmitting signals, such as cooperative sensing messages (CSMs). The communication transceivers 37 may be considered sensors 40. The communication system 36 is configured to wirelessly communicate information between the vehicle 10 and the remote server 48. Furthermore, the remote vehicles 47 may include all or some of the components of the host vehicle 10 described above. The remote server 48 is in communication with the host vehicle 10.
[0027] The system 98 includes the vehicle controller 34, which is specifically programmed to predict whether sufficient time and space will be available to comfortably negotiate an intersection while the host vehicle 10 is towing the trailer 13. Specifically, the system 98 provides an estimate of how difficult it will be for the vehicle system 15, which includes the host vehicle 10 and the trailer 13, to negotiate an intersection. The added length and weight of the trailer 13 impact the time and space required by the host vehicle 10 to negotiate an intersection. Trailers require more room when turning due to their geometric characteristics, making maneuvering at certain intersections difficult. Drivers prefer navigation routes that avoid intersections with these difficult features.The system 98 presented here can predict sight distances and the ratio of required to available turn times at intersections based on map data and crowdsourced vehicle speeds. The system 98 can also predict turnability at intersections based on vehicle / trailer geometry and crowdsourced vehicle travel paths. The system 98 then uses the turn time ratios and trailer lane deviation as part of the route selection process.
[0028] Fig. 2 is a flowchart of a method 100 that uses map-based road geometry in combination with intersection and vehicle features to estimate when sight distances are insufficient for trailer-pulling vehicles 10 to comfortably navigate the intersection as the host vehicle 10 approaches the intersection. The method 100 begins at block 102. At block 102, the vehicle controller 34 receives map data within a bounding area (e.g., a bounding box or bounding radius around the intersection). The map data includes geometric data about the intersection on a road (e.g., polyline points). Each map polyline point has a latitude, a longitude, and an elevation. At block 102, the vehicle controller 34 also receives vehicle telemetry data crowdsourced from the remote vehicles 47.The vehicle telemetry data includes the speeds and paths of the remote vehicles 47 entering the intersection. Method 100 then proceeds to block 104.
[0029] In block 104, the vehicle controller 34 converts the map data into points in a planar coordinate system. Specifically, the latitude and longitude are converted into coordinates in a planar xy coordinate system using the equirectangular and equirectangular projections, respectively. The following equations can be used to determine the coordinates in the planar xy coordinate system: x=R(λ−λ0)cosφ1 y=R(φ−φ0) where: R is the radius of the Earth; λ is the longitude of the polyline point; φ is the latitude of the polyline point; λ0 is the longitude at the crossing node; φ0 is the latitude at the crossing node; and the intersection node is the polyline point at the road intersection.
[0030] In block 104, the road distance and elevation are converted into coordinates in a planar pz coordinate system. Method 100 then continues with block 106.
[0031] In block 106, the vehicle controller 34 determines the intersection features. The intersection features include information retrieved from the map data, such as the number of lanes, the presence or absence of a stop, the presence or absence of a traffic signal, and the turn angle. In addition, the intersection features include information obtained from the vehicle telemetry data of the remote vehicles 47 moving through the intersection, such as the average speeds across the intersection for each direction of travel. The method 100 then continues with block 108.
[0032] In block 108, the vehicle controller 34 classifies the intersection based on the intersection characteristics. As non-limiting examples, the intersection classifications may include stop sign-controlled intersections, definite stop sign intersections, traffic light-controlled intersections, and uncontrolled intersections. The intersection classifications are then used to determine the relevant sight distances. For stop sign-controlled intersections, the relevant sight distances may be derived based on the number of intersecting streets, the desired path of travel through the intersection (i.e., left, right, straight ahead), the total number of stop signs (i.e., controlled branches); whether the lead vehicle's entry direction is controlled; and whether or not the direction of travel is into or out of a one-way street.For unambiguous stop sign intersections, the relevant sight distances may be determined by considering the presence or absence of three stop signs at a four-way intersection and the presence or absence of special conditions noted below the stop sign. For traffic light-controlled intersections, the relevant sight distances may be divided into an intersection with a dedicated left-turn signal and an intersection without a left-turn signal. Intersections with a dedicated left-turn signal do not incur turn time costs. Uncontrolled intersections are treated as non-right-way roads with respective stop signs, for which no clearance time or time to reach the target speed applies. Next, the method 100 proceeds to block 110.
[0033] In block 110, the vehicle controller 34 determines the maximum line-of-sight distance from the intersection before a visual obstruction is likely. The maximum line-of-sight sight distance (i.e., the sight distance) is determined for relevant sight distances (not for irrelevant sight distances). The sight distances are evaluated based on the road curvature in both the horizontal and vertical planes. In the horizontal plane, the maximum line-of-sight distance is where the line of sight no longer lies within the boundaries of the road and its shoulder. In the vertical plane, the maximum line-of-sight distance is where the line of sight begins to pass through the roadway surface. The sight distances are determined directly from the geometry of the road, which is provided by the polyline points on the map along each branch of the intersection in the form of latitude, longitude, and elevation.The sight distance from an intersection along a given direction of travel is determined by incrementally calculating the offset distance between the current line of sight and points along the road until an offset distance threshold is exceeded. To do this, the vehicle controller 34 first finds the first polyline point where the offset distance is greater than the offset distance threshold. The offset distance threshold is defined by the following equation: dmax=nlanes⋅LW+SW where: d max is the threshold value for the offset distance; n lanes is the number of lanes; LW is the width of the lane; and SW is the width of the shoulder.
[0034] The vehicle controller 34 can increase the accuracy by linear interpolation between the points (if the points are far apart). The vehicle controller 34 then calculates the available turn time from the maximum visibility distance. To do so, the vehicle controller 34 can use the following equation: tsight_max=dsight_maxvlimit t sight_max is the available turning time; d sight_max is the distance to the maximum point of maximum visibility; and v limit is the speed limit at the intersection or an average value from crowdsourced data.
[0035] In block 110, the vehicle controller 34 also determines the maximum line of sight distance due to road elevation. In this case, the maximum line of sight distance is determined as described above, but with slight variations. First, the estimated average vehicle height (e.g., 1.5 meters) is assumed as the threshold for the offset. The driver's head height is added to the intersection node height to account for the increased visibility of taller vehicles. Only positive offsets affect visibility (i.e., if the line of sight were through the road). The coordinate system is assumed to be (p, z), where p is an approximation of the vertical plane parallel to the direction of travel. The sight distance calculation is performed in 2D. Therefore, for the vertical sight distance, the point coordinates lie in the vertical plane (z) along the direction of travel (p). The method 100 then proceeds to block 112.
[0036] In block 112, the vehicle controller 34 calculates the time available to navigate through the intersection (i.e., the turn time) using the previously determined maximum line-of-sight distance and the average vehicle speed of the remote vehicles 47, which is determined through crowdsourcing. By determining the turn time required to navigate through the intersection, the vehicle controller 34 identifies intersections that do not have sufficient navigation time to turn due to road curvature and / or grade obstructions, based on two metrics: clearance time and time to reach target speed. Clearance time is the time required for the host vehicle 10 and trailer 13 to clear an intersection before oncoming traffic arrives.The time to reach the target speed is the time required for the host vehicle 10 and trailer 13 to clear the intersection and then reach the target speed without impeding oncoming traffic. The clearance time can be determined using the following equations: Time-2-Clear=CPWR⋅Ct2c⋅2⋅dclearaavg dclear=π⋅R⋅α⋅180+lvehicleR=(nlanes+1 / 2)⋅LW where: Time-2-Clear is the clearance time (i.e., the time required for the host vehicle 10 and trailer 13 to clear an intersection before the arrival of oncoming traffic); C PWR is a predetermined weight coefficient; C t2c is a predetermined gradient coefficient calculated from map data (slope of the intersection determined from polyline points); α is the relative turning angle; I vehicleis the combined length of the host vehicle 10 and the trailer 13; LW is the lane width; and n lanes is the number of lanes at the intersection.
[0037] The vehicle controller 34 can determine the time to reach the target speed using the following equations: daccln=12vlimit2aavg doffset≈daccln−12dturn dgap=vlimit⋅tgap dcatch=vlimit⋅taccln dsight_min_reqd=dcatch+lvehicle+dgap−doffset Time_2_Speed=CPWR⋅Ct2s⋅dsight_min_reqdvlimit where: Vlimit is the maximum speed limit at the intersection; a avg is the average starting acceleration of the host vehicle 10; d aceln is the distance required by the host vehicle 10 to reach the desired speed (v limit ) at the average acceleration (a avg ) to reach; dturn is the turning distance at the intersection; t gap is a predetermined time that determines the safe distance (d gap ) between two vehicles marked with v limit drive; t accln is the time required for the host vehicle 10 to reach the average vehicle speed after turning at the intersection; d gap is the distance between the nearest remote vehicle 47 and the host vehicle 10 after the host vehicle 10 has turned at the intersection; d catch is the minimum distance that the nearest remote vehicle 47 can travel to the intersection before the host vehicle 10 impedes the remote vehicle's travel; I vehicle is the combined length of the host vehicle 10 and the trailer 13; d offsetis the distance from the center of the intersection to the location of the remote vehicle 47 closest to the host vehicle 10 after the host vehicle 10 has turned at the intersection; d sight_min_reqd is the required minimum visibility; Time_2_Speed is the minimum time required for the host vehicle 10 (attached to the trailer 13) to accelerate from a standstill to the target speed (i.e., average speed of the vehicle) in a new direction of travel without disrupting the flow of oncoming traffic at the intersection.
[0038] The method 100 then continues with block 114. In block 114, the vehicle controller 34 determines the time ratios for the clearance time and the time to reach the target speed. The time ratios are the available time relative to the required time (i.e., the previously determined clearance time and the time to reach the target speed). The vehicle controller 34 then determines the cost of the intersection based on the time ratios for the clearance time and the time to reach the target speed. For example, the cost of the intersection may be proportional (e.g., directly proportional) to the time ratios for the clearance time and the time to reach the target speed. The complexity of the turn may be assessed by traversing all nodes and edges along a route provided by the routing engine or route selector.For each route provided, the cost factors are cumulated, and the route with the lowest score is presented as the preferred route. Route selection can be enhanced or improved using a utility function to include other convenience metrics. The utility function might look like this: DC=∑inwixi where: DC is the ride comfort from a first point to a second point; x i is the risk of the i-th factor selected from a list of possible factors; w i is the weighting factor for the i-th risk; and i is the risk factor, which may include the condition of the road edges, the road gradient and the drive load.
[0039] Method 100 then proceeds to block 116. In block 116, vehicle controller 34 selects the preferred route based on the intersection cost. The preferred route is the route with the lowest cost. The selected route may be displayed on user interface 23. Optionally, vehicle controller 34 may instruct host vehicle 10 to autonomously travel the selected route.
[0040] Fig.3 is a flowchart of a method 200 for determining intersection turnability. Intersection maneuverability is assessed by applying trailer lane deviation calculations to crowdsourced vehicle trajectories, which are then used to predict maneuvering difficulty. The turnability model described by method 200 uses vehicle telemetry trajectories in conjunction with trailer lane deviation calculations to predict whether there is sufficient room for a trailer-pulling vehicle to negotiate a particular intersection. The turnability model evaluates whether the swept paths of the host vehicle 10 and trailer 13 will cross virtual boundaries generated from the crowdsourced vehicle trajectories.The physical dimensions of the host vehicle 10 and the trailer 13 are required and can be entered by the driver or possibly calculated by vehicle cameras. The method 200 begins in block 202.
[0041] In block 202, the vehicle controller 34 receives vehicle telemetry data crowdsourced from the remote vehicles 47. The vehicle telemetry data includes the travel paths of the remote vehicles 47 traveling through the intersection. The travel paths of the remote vehicles 47 can be retrieved from a database crowdsourced using GPS telemetry data. Method 200 then continues with block 204.
[0042] At block 204, the vehicle controller 34 calculates an average steering path for each particular maneuver (e.g., a left turn, a right turn, etc.) through a given intersection using the paths of the remote vehicles 47 traveling through the intersection, which are obtained from the vehicles' telemetry data from the crowdsourced database. The method 200 then proceeds to block 206.
[0043] In block 206, the vehicle controller 34 determines (e.g., calculates) an inner travel path boundary and an outer travel path boundary across the intersection based on the distribution of travel paths crowdsourced from the plurality of remote vehicles 47 at the intersection. For example, the ninety-fifth percentile of the travel path distribution of the travel paths crowdsourced from the plurality of remote vehicles 47 at the intersection. Next, the method 200 proceeds to block 208.
[0044] In block 208, the vehicle controller 34 feeds the average steering path into a vehicle off-tracking model, such as the vehicle off-tracking models developed by Michael Sayers. The vehicle off-tracking model outputs a trial-and-error path for the host vehicle 10 and the trailer 13. The trailer off-tracking / trial-and-error path calculations are based on the incremental analysis method. The basic premise of the incremental analysis method is that each vehicle unit—a unit consisting of a steered and an unsteered axle, or a coupling pin and an unsteered axle—is represented as a bicycle model, and the coordinates of each axle are calculated using geometric relationships along incremental positions of the steer axle path.The incremental analysis method assumes that a vehicle unit traverses an arc with a fixed radius at each incremental step, determined by the current coordinates and heading angle at that step. For sufficiently small steps, the position error is considered negligible. Method 200 then continues with block 210.
[0045] In block 210, the vehicle controller 34 spatially compares the tested path and the inner and outer path boundaries to predict the difficulty of the maneuver. Method 200 then continues with block 212.
[0046] In block 212, the vehicle controller 34 then determines the turn cost based on the difficulty of the maneuver. To determine the cost value of the intersection, the vehicle controller 34 uses the average steering distance of the remote vehicles 47. The vehicle controller 34 then determines whether the attempted path exceeds the inner or outer travel limits of the travel paths determined from the distribution of the travel paths of the remote vehicles 47. The vehicle controller 34 then determines the cost value, which may be proportional to the distance exceeded from the attempted path to the inner or outer travel limits of the travel paths determined from the distribution of the travel paths of the remote vehicles 47. Alternatively, the cost value may also be a classification based on the distance exceeded, e.g., no, large, or small exceedance.In another example, the vehicle controller 34 uses the travel paths of the remote vehicles 47 through the intersection to map the intersection boundaries. Next, the vehicle controller 34 uses a path generation algorithm to find the maximum possible outer and inner travel paths for towing trailers. In this case, the cost could be proportional to the inner / outer travel path area or area (i.e., proportional to the available space for turning). Method 200 then proceeds to block 214.
[0047] In block 214, the vehicle controller 34 selects a route based on the cost value determined in block 212. The selected route may be the route with the lowest cost value. The method 200 then continues with block 216. In block 216, the vehicle controller instructs the user interface 23 to display the selected route. Optionally, the vehicle controller 34 may instruct the host vehicle 10 to autonomously travel the selected route.
[0048] While exemplary embodiments are described above, these embodiments are not intended to describe all possible forms encompassed by the claims. The words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the disclosure. As described above, the features of various embodiments may be combined to form further embodiments of the presently disclosed system and method that may not be explicitly described or illustrated.While various embodiments might be described as advantageous or preferred over other embodiments or prior art implementations with respect to one or more desired characteristics, those skilled in the art will recognize that one or more features or characteristics may be compromised to achieve the desired overall system characteristics, depending on the specific application and implementation. These attributes may include, but are not limited to, cost, strength, durability, life cycle cost, marketability, appearance, packaging, size, usability, weight, manufacturability, ease of assembly, etc.Thus, embodiments that are described as less desirable than other embodiments or prior art implementations with respect to one or more features are not outside the scope of the disclosure and may be desirable for certain applications.
[0049] The drawings are simplified and not to scale. For simplicity and clarity only, directional terms such as top, bottom, left, right, on, over, above, below, beneath, behind, and front may be used with reference to the drawings. These and similar directional terms should not be construed to limit the scope of the disclosure in any way.
[0050] Embodiments of the present disclosure are described herein. It should be understood, however, that the disclosed embodiments are merely examples, and other embodiments may take various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be considered limiting, but merely as a representative basis for teaching those skilled in the art to variously employ the presently disclosed system and method. As will be appreciated by those skilled in the art, various features illustrated and described with reference to one of the figures may be combined with features illustrated in one or more other figures to produce embodiments not expressly illustrated or described.The depicted feature combinations represent representative embodiments for typical applications. However, various combinations and modifications of the features consistent with the teachings of this disclosure may be desirable for particular applications or implementations.
[0051] Embodiments of the present disclosure may be described herein in terms of functional and / or logical block components and various processing steps. It should be understood that such block components may be implemented by a variety of hardware, software, and / or firmware components configured to perform the specified functions. For example, an embodiment of the present disclosure may utilize various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, lookup tables, or the like, which may perform a variety of functions under the control of one or more microprocessors or other control devices.Furthermore, it will be appreciated by those skilled in the art that embodiments of the present disclosure may be used in connection with a variety of systems and that the systems described herein are merely exemplary embodiments of the present disclosure.
[0052] For the sake of brevity, techniques for signal processing, data fusion, signaling, control, and other functional aspects of the systems (and the individual operating components of the systems) are not described in detail here. Furthermore, the connecting lines depicted in the various figures are intended to represent exemplary functional relationships and / or physical connections between the various elements. It should be noted that alternative or additional functional relationships or physical connections may be present in an embodiment of the present disclosure.
[0053] This description is merely illustrative in nature and is not intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure may be embodied in a variety of forms. Therefore, while this disclosure contains specific examples, the true scope of the disclosure should not be so limited, since other modifications will become apparent upon a study of the drawings, the specification, and the following claims.
Claims
[1] A method for selecting a route through an intersection, comprising: Receiving map data, wherein the map data includes geometric data about the intersection on a road and a vehicle is approaching the intersection on the road; Receiving crowdsourced vehicle telemetry data from a plurality of remote vehicles, the vehicle telemetry data including speeds of the plurality of remote vehicles traveling across the intersection of the road; Determining visibility based on map data; Determining an average vehicle speed across the intersection using the vehicle telemetry data; Determining the time available to pass through the intersection based on visibility and average vehicle speed at the intersection; Determining a ratio between the time available to pass through the intersection and the time required to pass through the intersection; and Determining a cost value of the intersection using the ratio between the time available to traverse the intersection and the time required to traverse the intersection. [2] The method of claim 1, further comprising: Selecting a route based on the cost value of the intersection; Instruct the vehicle to drive the selected route autonomously. [3] The method of claim 2, wherein determining the time available to proceed through the intersection using visibility and average vehicle speed through the intersection includes determining the time required for the vehicle and a trailer attached to the vehicle to clear the intersection prior to the arrival of oncoming traffic. [4] The method of claim 3, wherein determining the time available to negotiate the intersection using visibility and average vehicle speed through the intersection comprises determining the time required for the vehicle and trailer to negotiate the intersection and then reach a target speed without impeding oncoming traffic. [5] The method of claim 4, wherein the vehicle telemetry data comprises a plurality of travel paths taken by the plurality of remote vehicles at the intersection, and the method further comprises: determining an average travel path through the intersection using the plurality of travel paths taken by the plurality of remote vehicles at the intersection; Determining an inner travel path boundary at the intersection using the plurality of travel paths taken by the plurality of remote vehicles at the intersection; and Determining an outer travel path boundary at the intersection using the plurality of travel paths traversed by the plurality of remote vehicles at the intersection. [6] The method of claim 5, further comprising: Comparing the average travel path with the inner travel path boundary and the outer travel path boundary to determine a cost value for maneuverability at the intersection. [7] The method of claim 6, wherein determining the cost value of the intersection comprises considering the cost value for maneuverability at the intersection to determine the cost value of the intersection. [8] Tangible, non-transitory, machine-readable medium containing machine-readable instructions that, when executed by a processor, cause the processor to: Receiving map data, wherein the map data includes geometric data about an intersection on a road, and a vehicle is approaching the intersection on the road; Receiving crowdsourced vehicle telemetry data from a plurality of remote vehicles, the vehicle telemetry data including speeds of the plurality of remote vehicles traveling across the intersection of the road; Determining visibility based on map data; Determining an average vehicle speed at the intersection using the vehicle telemetry data; Determining the time available to pass through the intersection based on visibility and average vehicle speed at the intersection; Determining a ratio between the time available to pass through the intersection and the time required to pass through the intersection; and Determining a cost value of the intersection based on the ratio between the time available to pass through the intersection and the time required to pass through the intersection. [9] The tangible, non-transitory, machine-readable medium of claim 8, wherein the tangible, non-transitory, machine-readable medium further comprises machine-readable instructions that, when executed by the processor, cause the processor to: Choosing a route based on the cost value of the intersection; Instruct the vehicle to drive the selected route autonomously. [10] The tangible, non-transitory, machine-readable medium of claim 9, wherein the tangible, non-transitory, machine-readable medium further comprises machine-readable instructions that, when executed by the processor, cause the processor to: Determining the time required for a vehicle and any trailer attached to the vehicle to clear the intersection before the arrival of oncoming traffic.
