System and method for calculating turn cost for routing purposes
By receiving maps and telemetry data to calculate the turn cost value of the intersection and selecting the lowest cost route, it solves the problem of difficulty in turning at the intersection and improves turning efficiency and safety.
Patent Information
- Application Number
- CN202311408138.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2023-10-26
- Publication Date
- 2024-12-03
AI Technical Summary
The towing trailer requires more space and time when turning at an intersection, and the prior art is difficult to effectively evaluate and select the easiest route to avoid turning difficulties.
By receiving map data and telemetry data for remote vehicles, calculate the turn cost value of the intersection, select the lowest cost route to navigate through the intersection, consider the trailer's geometry and off-track situation, use crowdsourcing vehicle paths to determine the average and external path boundaries , compare to determine the operability of the route.
Improves the efficiency and safety of vehicles turning at intersections, and reduces challenging route navigation for drivers by dynamically assessing turn difficulty and route selection.
Smart Images

Figure CN119063748A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to systems and methods for calculating turn costs for routing purposes. Background Art
[0002] This introduction generally presents the background of the present disclosure. The work of the presently named inventors, to the extent it is described in this introduction, and aspects of the specification that may not have been identified as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0003] Sometimes vehicles tow trailers. These vehicles towing trailers may sometimes need to cross intersections and turn. Vehicles towing trailers may need more space and time to turn at intersections than vehicles not towing trailers. Summary of the invention
[0004] The present disclosure describes a system and method for calculating turn costs for route selection purposes. In one aspect of the present disclosure, the method can be used to select a route for a vehicle along an intersection and includes receiving map data. The map data includes geometric data about an intersection on a road. The vehicle is approaching an intersection on the road. The method also includes receiving crowdsourced vehicle telemetry data from multiple remote vehicles, wherein the vehicle telemetry data includes the speeds of multiple remote vehicles traveling along the road intersection; using the map data to determine the sight distance, using the vehicle telemetry data to determine the average vehicle speed along the intersection, using the sight distance and the average vehicle speed along the intersection to determine the time available for navigating through the intersection, determining the time ratio between the time available for navigating through the intersection and the time required to pass through the intersection, and using the ratio between the time available for navigating through the intersection and the time required to pass through the intersection to determine the cost value of the intersection. The method can include selecting a route based on the cost value of the intersection and commanding the vehicle to drive autonomously along the selected route. The method described in this paragraph improves vehicle technology by identifying the simplest route for the vehicle based on the difficulty of navigating through the intersection.
[0005] In one aspect of the disclosure, the method includes determining a time required for a vehicle and a trailer connected to the vehicle to navigate an intersection before an oncoming vehicle arrives. In one aspect of the disclosure, the method includes determining a time required for the vehicle and trailer to navigate an intersection without obstructing oncoming vehicles and subsequently reach a target speed. The vehicle telemetry data includes a plurality of paths along the intersection taken by a plurality of remote vehicles.
[0006] In one aspect of the disclosure, the method further includes determining an average path along the intersection using multiple paths along the intersection taken by multiple remote vehicles, determining an inner path boundary along the intersection using multiple paths along the intersection taken by multiple remote vehicles, and determining an outer path boundary along the intersection using multiple paths along the intersection taken by multiple remote vehicles. In one aspect of the disclosure, the method further includes comparing the average path with the inner path boundary and the outer path boundary to determine an operability cost value for the intersection. In one aspect of the disclosure, the method further includes considering the operability cost value of the intersection to determine a cost value for the intersection.
[0007] The present disclosure also describes a tangible, non-transitory machine-readable medium comprising machine-readable instructions, which, when executed by a processor, cause the processor to perform the above method.
[0008] The present disclosure also describes a system for selecting a route along an intersection. The system includes a communication transceiver and a controller communicating with the communication transceiver. The controller is programmed to perform the above method.
[0009] Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter.It should be understood that the detailed description and specific examples are intended for illustration purposes only and are not intended to limit the scope of the present disclosure.
[0010] The above features and advantages and other features and advantages of the systems and methods of the present disclosure are apparent from the following detailed description, including the claims and exemplary embodiments, when taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The present disclosure will be more fully understood from the detailed description and accompanying drawings, in which:
[0012] Figure 1 is a block diagram depicting an embodiment of a vehicle including a system for calculating turn costs for routing purposes;
[0013] Figure 2 is a flow chart of a method for determining turn times at an intersection; and
[0014] Figure 3 is a flow chart of a method for determining turn operability in an intersection. DETAILED DESCRIPTION
[0015] Reference will now be made in detail to several examples of the present disclosure illustrated in the accompanying drawings. Wherever possible, the same or similar reference numerals are used in the drawings and the description to refer to the same or similar components or steps.
[0016] Reference Figure 1, the main vehicle 10 generally includes a chassis 12, a body 14, front wheels and rear wheels 17 and can be referred to as a vehicle system. In the depicted embodiment, the main vehicle 10 includes two front wheels 17a and two rear wheels 17b. The body 14 is arranged on the chassis 12 and generally surrounds the components of the main vehicle 10. The body 14 and the chassis 12 can form a frame together. Each wheel 17 is rotatably connected to the chassis 12 near the corresponding corner of the body 14. The main vehicle 10 includes a front axle 19 connected to the front wheels 17a and a rear axle 25 connected to the rear wheels 17b. The main vehicle 10 can be connected to the trailer 13. Methods 100 and 200 are not limited to a single trailer. On the contrary, methods 100 and 200 can be applied to any number of trailers towed in series. The main vehicle 10 and the trailer 13 can be collectively referred to as a vehicle system 15.
[0017] In various embodiments, the host vehicle 10 can be an autonomous vehicle or a semi-autonomous vehicle, and can be considered as part of a system 98 that calculates turn costs through crowdsourcing for route selection. The system 98 can be referred to as a control system. In the present disclosure, the term "crowdsourcing" means requesting information from multiple remote vehicles 47. The host vehicle 10 is, for example, a vehicle that is automatically controlled to transport passengers from one location to another. The host vehicle 10 is depicted as a pickup truck in the illustrated embodiment, but it should be understood that other vehicles can also be used, including trucks, sedans, coupes, sports utility vehicles (SUVs), recreational vehicles (RVs), etc. In one embodiment, the host vehicle 10 can be a so-called level 2, level 3, level 4, or level 5 automation system. Level 4 systems represent "high automation" and refer to the driving mode-specific performance of the autonomous driving system in dynamic driving tasks even if the human driver does not respond appropriately to the intervention request. Level 5 systems represent "full automation" and refer to the full-time performance of the autonomous driving system in various aspects of the dynamic driving task under a variety of road and environmental conditions that can be managed by the human driver. In a level 3 vehicle, the vehicle system performs the entire dynamic driving task (DDT) within its design area. The vehicle operator is responsible for DDT fallback only when the host vehicle 10 needs to "ask" the driver to take over when a problem occurs or the vehicle is about to leave the area in which it is capable of operating. In a Level 2 vehicle, the system provides steering, braking / acceleration support, lane centering and adaptive cruise control.
[0018] As shown, the main 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 actuator system 30, at least one data storage device 32, at least one vehicle controller 34, and a communication system 36. In various embodiments, the propulsion system 20 may include an electric motor such as a traction motor and / or a fuel cell propulsion system. The main 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 provide electrical energy to the propulsion system 20. In some embodiments, the propulsion system 20 may include an internal combustion engine. The transmission system 221 is configured to transmit power from the propulsion system 20 to the wheels 17 according to a selectable speed ratio. According to various embodiments, the transmission system 22 may include a stepped automatic transmission, a continuously variable transmission, or other suitable transmission. However, it is conceivable that if the propulsion system 20 is configured as an electric motor, the main vehicle 10 may not include the transmission system 22. The braking system 26 is configured to provide braking torque to the wheels 17. In various embodiments, the braking system 26 may include friction brakes, brake-by-wire, a regenerative braking system (such as an electric motor), and / or other suitable braking systems. The steering system 24 affects the position of the wheels 17 and may include a steering wheel 33. Although depicted as including a steering wheel 33 for purposes of illustration, in some embodiments contemplated within the scope of the present disclosure, the steering system 24 may not include a steering wheel 33.
[0019] The sensor system 28 includes one or more sensors 40 (i.e., sensing devices) that sense observable conditions of the external environment and / or the internal environment of the host vehicle 10. The sensors 40 communicate with the vehicle controller 34 and may include, but are not limited to, one or more radars, one or more light detection and ranging (lidar) sensors, one or more proximity sensors, one or more odometers, one or more ground penetrating radar (GPR) sensors, one or more steering angle sensors, one or more global navigation satellite system (GNSS) transceivers 45 (e.g., global positioning system (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 that indicates a sensed observable condition of the external environment and / or the internal environment of the host vehicle 10. Because the sensor system 28 provides data to the vehicle controller 34, the sensor system 28 and its sensors 40 are considered to be information sources (or simply sources).
[0020] As described above, the sensor system 28 includes one or more global navigation satellite system (GNSS) transceivers 45 (e.g., global positioning system (GPS) transceivers) configured to detect and monitor route data (i.e., route information). The GNSS transceiver 45 is configured to communicate with the GNSS to locate the position of the host vehicle 10 on the earth. The GNSS transceiver 45 is in electronic communication with the vehicle controller 34.
[0021] The actuator system 30 includes one or more actuators 42 that control one or more vehicle features, such as, but not limited to, the propulsion 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, but not limited to, doors, trunks, and cabin features such as air, music, lighting, etc.
[0022] The data storage device 32 stores data for automatically controlling the host vehicle 10. In various embodiments, the data storage device 32 stores a map defined by the navigable environment. In various embodiments, the defined map may be predefined by a remote system and obtained from the remote system. For example, the defined map may be collected by a remote system, transmitted (wirelessly and / or wiredly) to the host vehicle 10, and stored in the data storage device 32. The data storage device 32 may be part of the vehicle controller 34, may be separate from the vehicle controller 34, or may be part of the vehicle controller 34 and part of a separate system.
[0023] 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 bag and is configured to transition between a stowed configuration and a deployed configuration to cushion the effects of external forces applied to the host vehicle 10. The sensor 40 may include an airbag sensor, such as an IMU, that is configured to detect external forces and generate a signal indicating the magnitude of such external forces. The vehicle controller 34 is configured to command the deployment of the airbag 35 based on signals from one or more sensors 40, such as airbag sensors. Accordingly, the vehicle controller 34 is configured to determine when the airbag 35 has been deployed.
[0024] The vehicle controller 34 includes at least one vehicle processor 44 and a vehicle non-transitory computer-readable storage device or medium 46. The vehicle processor 44 can be a custom processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor of multiple processors associated with the vehicle controller 34, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or a device generally used to execute instructions. The vehicle non-transitory computer-readable storage device or medium 46 may include volatile and non-volatile storage devices 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 when the vehicle processor 44 is powered off. The vehicle non-transitory computer-readable storage device or medium 46 can be implemented using a plurality of storage devices, such as a programmable read-only memory (PROM), an electrically programmable read-only memory (EPROM), an erasable programmable read-only memory (EEPROM), flash memory, or other magnetic, optical, or combination storage devices capable of storing data, some of which represent executable instructions used by the vehicle controller 34 when controlling the host vehicle 10. The vehicle controller 34 of the host vehicle 10 may be programmed to perform the methods 100 and 400 described in detail below.
[0025] The instructions may include one or more separate programs, each of which includes an ordered list of executable instructions for implementing logical functions. When the instructions are executed by the vehicle processor 44, signals from the sensor system 28 are received and processed, logic, calculations, methods and / or algorithms for automatically controlling components of the host vehicle 10 are executed, and control signals 30 for the actuator system are generated to automatically control components of the host vehicle 10 based on the logic, calculations, methods and / or algorithms. Although Figure 1 Although shown as a single vehicle controller 34, embodiments of the host vehicle 10 may include multiple vehicle controllers 34 that communicate via a suitable communication medium or combination of communication mediums and cooperate to process sensor signals, execute logic, calculations, methods and / or algorithms, and generate control signals to automatically control features of the host vehicle 10.
[0026] In various embodiments, one or more instructions of the vehicle controller 34 are included in the control system 98. The main vehicle 10 includes a user interface 23, which can be a touch screen in the dashboard. The user interface 23 can include, but is not limited to, an alarm, such as one or more speakers 27 for providing audible sounds, tactile feedback in a vehicle seat or other object, one or more displays 29, one or more microphones 31, and / or other devices suitable for providing notifications to a vehicle user of the main 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 operator or a vehicle passenger). For example, the user interface 23 may include a touch screen and / or buttons configured to receive input from a vehicle user 11. Accordingly, the vehicle controller 34 is configured to receive input from a user via the user interface 23. The main vehicle 10 may include one or more displays 29, which are configured to display information to a user (e.g., a vehicle operator or a passenger).
[0027] The communication system 36 communicates with the vehicle controller 34 and is configured to wirelessly transmit information to and receive information from one or more remote servers 48, such as, but not limited to, a remote system of a remote call center (e.g., General Motors' ON-STAR). 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 for other programs or devices of the "client". In this case, the client is the remote vehicle 47 and the main vehicle 10. In the present disclosure, the term "remote vehicle" refers to a vehicle that is not physically connected to the main vehicle or the remote server 48. As used herein, the term "remote server" refers to a server that is not physically connected to the main vehicle 10 and / or the remote vehicle 47. The remote server 48 may include a server controller 49 and a server non-transitory computer-readable storage device or medium 51. The server processor 49 may be a custom processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor in a plurality of processors associated with the vehicle controller 34, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or a device generally used to execute instructions. The server computer readable storage device or medium 51 may include volatile and non-volatile storage devices 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 when the vehicle processor 44 is powered off. The server computer readable storage device or medium 51 can be implemented using a plurality of storage devices, such as a PROM (programmable read-only memory), an EPROM (electrically programmable read-only memory), an EEPROM (electrically erasable programmable read-only memory), flash memory, or other magnetic, optical, or combination storage devices capable of storing data, some of which represent executable instructions used by the control system 98. The remote server 48 may also include a communication transceiver 37 for wirelessly transmitting data to the host vehicle 10 and / or the remote vehicle 47. The server controller 49 may be programmed to perform the method 200 described in detail below.
[0028] In some embodiments, the communication system 36 of the main vehicle 10 is a wireless communication system that is configured to communicate via a wireless local area network (WLAN) using the IEEE 802.11 standard or by using cellular data communications. Accordingly, the communication system 36 may include one or more antennas and / or communication transceivers 37 for receiving and / or transmitting signals, such as collaborative sensing messages (CSM). The communication transceiver 37 may be considered a sensor 40. The communication system 36 is configured to wirelessly transmit information between the main vehicle 10 and a remote server 48. In addition, the remote vehicle 47 may include all or some of the components of the main vehicle 10 described above. The remote server 48 communicates with the main vehicle 10.
[0029] The system 98 includes a vehicle controller 34 that is specifically programmed to predict whether there is enough time and space available to comfortably pass through an intersection when the host vehicle 10 is towing a trailer 13. Specifically, the system 98 provides an assessment of the difficulty of the vehicle system 15 including the host vehicle 10 and the trailer 13 passing through the intersection. The increased length and weight of the trailer 13 affect the time and space required for the host vehicle 10 to pass through the intersection. Due to the geometrically off-track characteristics, the trailer requires additional space when turning, which makes it challenging to operate through certain intersections. Drivers tend to avoid navigating routes through intersections with these challenging features. The currently disclosed system 98 can predict the sight distance at the intersection and the ratio between the required turning time and the available turning time based on map data and crowdsourced vehicle speeds. The system 98 can also predict the turning maneuverability at the intersection based on the vehicle / trailer geometry and the crowdsourced vehicle path. Subsequently, the system 98 uses the turning time ratio and the trailer off-track as part of the route selection process.
[0030] Figure 2 1 is a flow chart of a method 100 that uses map-based road geometry in combination with intersection and vehicle characteristics to estimate when the sight distance is insufficient for the towing vehicle 10 to comfortably navigate the intersection as the host vehicle 10 approaches the intersection. The method 100 begins at box 102. At box 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 (e.g., polyline points) about the road intersection. Each map polyline point has a latitude, longitude, and altitude. In addition, at box 102, the vehicle controller 34 receives crowdsourced vehicle telemetry data from a remote vehicle 47. The vehicle telemetry data includes the speed and path of the remote vehicle 47 traveling along the road intersection. The method 100 then proceeds to box 104.
[0031] At box 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 an equirectangular projection. The following equations can be used to determine the coordinates in the planar xy coordinate system:
[0032]
[0033]
[0034] in:
[0035] R is the radius of the Earth;
[0036] λ is the longitude of the broken line point;
[0037] is the latitude of the polyline point;
[0038] λ0 is the longitude of the intersection node;
[0039] is the latitude of the intersection node; and
[0040] An intersection node is a polyline point at a road intersection.
[0041] At block 104 , the road distance and height are transformed into coordinates in the planar pz coordinate system. The method 100 then continues to block 106 .
[0042] At box 106, the vehicle controller 34 determines the intersection characteristics. The intersection characteristics include information retrieved from the map data, such as the number of lanes, whether there is a stop, whether there is a traffic signal, and the turn angle. In addition, the intersection characteristics include information retrieved from the vehicle telemetry data crowdsourced by the remote vehicles 47 passing through the intersection, such as the average speed in each direction along the intersection. Then, the method 100 continues to box 108.
[0043] At box 108, the vehicle controller 34 uses the intersection characteristics to classify the intersection. As a non-limiting example, the classification of intersections can include stop sign controlled intersections, unique stop sign intersections, traffic light controlled intersections, and uncontrolled intersections. The intersection classification is then used to determine the relevant sight distance. For stop sign controlled intersections, the relevant sight distance can be inferred based on the number of intersecting roads, the required path through the intersection (i.e., left turn, right turn, straight ahead), the total number of stop signs (i.e., controlled road sections), whether the entry direction of the routing vehicle is controlled, and whether the direction of travel is into or from a one-way road. For unique stop sign intersections, the relevant sight distance can be determined by considering whether there are three stop signs at a four-way intersection and whether the special conditions annotated below the stop sign exist. For traffic light controlled intersections, the relevant sight distance can be divided into intersections with dedicated left turn signals and intersections without dedicated left turn signals. There is no turning time cost for intersections with dedicated left turn signals. Uncontrolled intersections are considered full stops with no travel time or acceleration time requirements. Afterwards, method 100 proceeds to frame 110 .
[0044] At box 110, the vehicle controller 34 determines the maximum sight distance from the intersection before a line of sight obstruction may occur. The maximum line of sight distance (i.e., line of sight) is determined for relevant line of sight (rather than irrelevant line of sight). Line of sight is evaluated based on the curvature of the road in the horizontal and vertical planes. For the horizontal plane, the maximum line of sight distance means that the line of sight is no longer within the range of the road and its shoulders. For the vertical plane, the maximum line of sight distance means that the line of sight begins to cross the road surface. The line of sight distance is determined directly based on the geometry of the road, which is provided by the map polyline points of each section along the intersection in the form of latitude, longitude and altitude. The line of sight from the intersection along a specific direction is determined by incrementally calculating the offset distance between the current line of sight and the point along the road until the offset distance threshold is exceeded. To do this, the vehicle controller 34 first finds the first polyline point whose offset distance is greater than the offset distance threshold. The offset distance threshold is defined by the following equation:
[0045] d max =n lanes LW+SW……Equation 3
[0046] in:
[0047] d max is the offset distance threshold;
[0048] n lanes is the number of lanes;
[0049] LW is the lane width; and
[0050] SW is the width of the shoulder.
[0051] The vehicle controller 34 may improve accuracy by linear interpolation between the points (if the points are far apart). The vehicle controller 34 then calculates the available turning time based on the maximum sight distance. To do this, the vehicle controller 34 may use the following equation:
[0052]
[0053] t sight_max is the available turning time;
[0054] d sight_max is the driving distance to the maximum viewpoint; and
[0055] v limit is the speed limit or average for the intersection from crowdsourced data.
[0056] At box 110, the vehicle controller 34 also determines the maximum sight distance due to the height of the road. In this case, the maximum sight distance is determined as described above, but with minor changes. First, the offset threshold is taken to be the estimated average vehicle height (e.g., 1.5 meters). The driver's head height is added to the intersection node height to account for the increased field of view of taller vehicles. Only positive offsets are considered to affect visibility (i.e., where the line of sight crosses the road). Take (p, z) as a coordinate system, where p is an approximation of a vertical plane parallel to the direction of travel. The sight distance calculation is performed in 2D. Therefore, for vertical sight distance, the point coordinates are located in the vertical plane (z) along the direction of travel (p). Then, method 100 proceeds to box 112.
[0057] At box 112, the vehicle controller 34 uses the predetermined maximum line of sight distance and the average vehicle speed obtained by the crowdsourced remote vehicles 47 to calculate the time available to navigate through the intersection (i.e., the turn time). By determining the turn time required to navigate through the intersection, the vehicle controller 34 identifies intersections that do not have sufficient time to navigate a turn due to line of sight obstructions caused by road curvature and / or slope based on two metrics, namely, the transit time and the acceleration time. The transit time is the time required for the host vehicle 10 and the trailer 13 to pass through the intersection before oncoming vehicles arrive. The acceleration time is the time required for the host vehicle 10 and the trailer 13 to navigate the intersection and then reach the target speed without obstructing oncoming vehicles. The transit time can be determined using the following equation:
[0058]
[0059] dclear=π·R·α·180+lvehicle...Equation 6
[0060] R=(nlanes+1 / 2)·LW
[0061] in:
[0062] Time-2-Clear is the clearance time (i.e., the time required for the host vehicle 10 and trailer 13 to pass through the intersection before the oncoming vehicle arrives);
[0063] C PWR is a predetermined weight coefficient;
[0064] C t2c is a predetermined slope factor, which is calculated using map data (crossing slopes determined by the broken line points);
[0065] α is the relative turning angle;
[0066] l vehicle The total length of the main vehicle 10 and the trailer 13;
[0067] LW is the lane width; and
[0068] n lanes is the number of lanes at the intersection.
[0069] The vehicle controller 34 may determine the acceleration time using the following equation:
[0070]
[0071]
[0072] d gap =v limit ·t gap ...Equation 9
[0073] d catch =v limit ·t accln ...Equation 10
[0074] d sight_min_reqd =d catch +l vehicle +d gao -d offset ...Equation 11
[0075]
[0076] in:
[0077] v limit for speed limits along intersections;
[0078] a avg is the average driving acceleration of the host vehicle 10;
[0079] daccln The host vehicle 10 has an average acceleration (a avg ) reaches the desired speed (v limit ) required distance;
[0080] d turn is the turning distance along the intersection;
[0081] t gap is the scheduled time, used to indicate the limit The safe driving distance between two vehicles (d gap );
[0082] t accln It is the time required for the host vehicle 10 to reach the average vehicle speed after turning at the intersection.
[0083] d gap is the distance from the nearest remote vehicle 47 to the host vehicle 10 after the host vehicle 10 turns at the intersection;
[0084] d catch is the minimum distance from the nearest remote vehicle 47 to the intersection before the host vehicle 10 impedes the remote vehicle's progress;
[0085] l vehicle is the total length of the host vehicle 10 and the trailer 13;
[0086] d offset is the distance from the center of the intersection to the position of the remote vehicle 47 closest to the host vehicle 10 after the host vehicle 10 turns at the intersection;
[0087] d signt_min_reqd is the minimum required sight distance;
[0088] The acceleration time is the minimum time required for the host vehicle 10 (connected to the trailer 13) to accelerate from rest to a target speed (ie, average speed vehicle) in a new direction of travel without interfering with oncoming vehicles at the intersection.
[0089] Then, the method 100 continues to box 114. At box 114, the vehicle controller 34 determines the time ratio of the transit time and the acceleration time. The time ratio is the ratio between the available time and the required time (i.e., the previously determined transit time and the acceleration time). The vehicle controller 34 then uses the time ratio of the transit time and the acceleration time to determine the cost value of the intersection. For example, the cost value of the intersection can be proportional to (e.g., directly proportional to) the time ratio of the transit time and the speed time. Turn complexity can be evaluated by traversing all nodes and edges along the route provided by the routing engine. For each route provided, the cost factor is accumulated and the route with the lowest score is presented as the preferred route. Through the utility function, other comfort indicators can be used to enhance route selection. The utility function can be as follows:
[0090]
[0091] in:
[0092] DC is the driving comfort from the first point to the second point;
[0093] x i is the risk of the ith factor selected from the following list of potential factors;
[0094] w i is the weight factor of the ith risk; and
[0095] i is the risk factor, which may include lane edge condition, road slope and driving stress.
[0096] Then, the method 100 continues to frame 116. At frame 116, the vehicle controller 34 selects a preferred route based on the cost value of the intersection. The preferred route is the route with the lowest cost. The selected route can be displayed on the user interface 23. Preferably, the vehicle controller 34 can command the host vehicle 10 to drive autonomously along the selected route.
[0097] Figure 3 is a flow chart of a method 200 for determining turn maneuverability in an intersection. The maneuverability of an intersection is evaluated by applying a trailer deviation track calculation to a crowdsourced vehicle path and then used to predict the difficulty of the maneuver. The turn maneuverability model described in method 200 uses the vehicle telemetry path, combined with the trailer deviation track calculation, to predict whether there is enough space for the trailer vehicle to pass through a specified intersection. The turn maneuverability model evaluates whether the travel path of the host vehicle 10 and the trailer 13 will exceed the virtual boundary generated by the crowdsourced vehicle path. The physical dimensions of the host vehicle 10 and the trailer 13 are required, which can be input by the driver or calculated by the vehicle camera. The method 200 starts at box 202.
[0098] At box 202, the vehicle controller 34 receives crowdsourced vehicle telemetry data from a remote vehicle 47. The vehicle telemetry data includes a path of the remote vehicle 47 traveling along a road intersection. The path of the remote vehicle 47 may be retrieved from a database generated using crowdsourced GPS telemetry data. The method 200 then continues to box 204.
[0099] At block 204 , the vehicle controller 34 uses the paths of the remote vehicles 47 traveling along the intersection, obtained from the crowdsourced vehicle telemetry data, to calculate the average turning path for each specific maneuver (e.g., left turn, right turn, etc.) through the specified intersection. The method 200 then proceeds to block 206 .
[0100] At block 206 , the vehicle controller 34 determines (e.g., calculates) an inner path boundary and an outer path boundary along the intersection based on the distribution of the crowdsourced paths along the intersection by the plurality of remote vehicles 47 . For example, ninety-five percent of the distribution of the crowdsourced paths along the intersection by the plurality of remote vehicles 47 . Next, the method 200 proceeds to block 208 .
[0101] At box 208, the vehicle controller 34 feeds the average steering path into a vehicle deviation track model, such as the vehicle deviation track model developed by Michael Sayers. The vehicle deviation track model outputs the driving path of the host vehicle 10 and the trailer 13. The trailer deviation / driving path calculation is performed based on an incremental analysis method. The basic premise of the incremental analysis method is that each vehicle unit - a unit consisting of a steering axis and a non-steering axis or a hitch pivot axis and a non-steering axis - is represented as a bicycle model, and the coordinates of each axis are calculated using the geometric relationship of the incremental position along the steering axis path. The incremental analysis method assumes that for each incremental step, the vehicle unit travels along an arc of a fixed radius, and the fixed radius is determined by the current coordinates and heading angle in a given step size. For sufficiently small step sizes, the position error is considered negligible. The method 200 then continues to box 210.
[0102] At block 210 , the vehicle controller 34 spatially compares the travel path and the inner and outer path boundaries to predict a level of maneuver difficulty. The method 200 then continues to block 212 .
[0103] At box 212, the vehicle controller 34 then determines the cost of the turn based on the level of difficulty of the operation. To determine the intersection cost value, the vehicle controller 34 uses the average turning path of the remote vehicle 47. Then, the vehicle controller 34 determines whether the driving path exceeds the inner or outer path boundary of the path determined using the distribution of the path of the remote vehicle 47. Then, the vehicle controller 34 determines a cost value, which can be proportional to the excess distance from the driving path to the inner or outer path boundary of the path, and the excess distance is determined by using the path distribution of the remote vehicle 47. Alternatively, the cost value can be a classification based on the excess distance, such as none, major or minor. In another example, the vehicle controller 34 uses the path of the remote vehicle 47 along the intersection to draw the intersection boundary. Next, the vehicle controller 34 uses the path generation algorithm to find the maximum possible outer and inner paths of the trailer. In this case, the cost can be proportional to the inner / outer path range or area (that is, proportional to the amount of available turning space). Then, the method 200 continues to box 214.
[0104] At box 214, the vehicle controller 34 selects a route based on the cost value determined at box 212. The selected route may be the route with the lowest cost value. Next, the method 200 continues to box 216. At box 216, the vehicle controller commands the user interface 23 to display the selected route. Alternatively, the vehicle controller 34 may command the host vehicle 10 to autonomously drive along the selected route.
[0105] Although exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms covered by the claims. The words used in the specification are descriptive rather than restrictive, and it should be understood that various changes can be made without departing from the spirit and scope of the present disclosure. As previously mentioned, the features of the various embodiments can be combined to form more embodiments of the currently disclosed system and method that may not be explicitly described or shown. Although each embodiment has been described as having advantages over other embodiments or prior art embodiments or it is preferred with respect to one or more desired characteristics, it should be understood by those of ordinary skill in the art that one or more features or characteristics can be omitted to achieve the desired overall system properties, depending on the specific application and embodiment. These properties may include, but are not limited to, cost, strength, durability, life cycle cost, marketability, appearance, packaging, size, maintainability, weight, manufacturability, ease of assembly, etc. Therefore, the described embodiments are not as ideal as other embodiments. Therefore, there are one or more features that are not as good as other embodiments or prior art embodiments, which do not exceed the scope of the present application and may be desirable for specific applications.
[0106] The drawings are in simplified form and are not drawn to exact scale. For convenience and clarity, directional terms such as top, bottom, left, right, up, above, above, below, below, rear, and front may be used with respect to the drawings. These directional terms and similar directional terms should not be construed as limiting the scope of the present disclosure in any way.
[0107] Embodiments of the present disclosure are described herein. However, it should be understood that the disclosed embodiments are merely exemplary, and other embodiments may take various alternative forms. The drawings are not necessarily drawn to scale, and certain features may be enlarged or reduced to show the details of a particular component. Therefore, the specific structural and functional details disclosed herein should not be interpreted as restrictive, but merely as a representative basis for teaching those skilled in the art to use the systems and methods of the present disclosure in different ways. It should be understood by those of ordinary skill in the art that the various features shown and described in any of the drawings may be combined with the features shown in one or more of the other drawings to produce embodiments that are not explicitly shown or described. The combination of the features shown provides representative embodiments of typical applications. However, various combinations and modifications of features consistent with the teachings of the present disclosure may be required for specific applications or implementations.
[0108] 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 multiple hardware, software, and / or firmware components configured to perform specified functions. For example, embodiments of the present disclosure may employ various integrated circuit components, such as memory elements, digital signal processing elements, logic elements, lookup tables, etc., which, when controlled by one or more microprocessors or other control devices, may perform various functions. In addition, those skilled in the art may appreciate that embodiments of the present disclosure may be implemented in conjunction with a variety of systems, and the systems described herein are merely exemplary embodiments of the present disclosure.
[0109] For the sake of brevity, technologies related to signal processing, data fusion, signaling, control and other functional aspects of the system (as well as the various operating components of the system) are not described in detail herein. In addition, the connecting lines shown in the various figures included herein 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 exist in the embodiments of the present disclosure.
[0110] This specification is merely illustrative in nature and is not intended to limit the present disclosure, its application or use. The broad teachings of the present disclosure can be implemented in a variety of forms. Therefore, although the present disclosure includes specific examples, since other modifications will become apparent after studying the drawings, the specification and the appended claims, the true scope of the present disclosure is not limited to the above examples.
Claims
1. A method for selecting a route along an intersection, comprising: receiving map data, wherein the map data includes geometric data of the intersection on the road, and the vehicle is approaching the intersection on the road; receiving crowdsourced vehicle telemetry data from a plurality of remote vehicles, wherein the vehicle telemetry data includes speeds of the plurality of remote vehicles traveling along an intersection of the road; using the map data to determine sight distance; using the vehicle telemetry data to determine an average vehicle speed along the intersection; determining a time available for navigating through the intersection using the sight distance and an average vehicle speed along the intersection; determining a ratio between the time available for navigating through the intersection and the time required to navigate through the intersection; and The cost value for the intersection is determined using the ratio between the time available to navigate through the intersection and the time required to navigate the intersection.
2. The method according to claim 1, further comprising: selecting a route based on the cost value of the intersection; The vehicle is commanded to automatically travel along the selected route.
3. The method of claim 2, wherein the sight distance and the average vehicle speed along the intersection are used to determine the time available for navigating through the intersection, including determining the time required for a vehicle and a trailer connected to the vehicle to pass through the intersection before an oncoming vehicle arrives.
4. The method of claim 3, wherein the sight distance and the average vehicle speed along the intersection are used to determine the time available for navigating through the intersection, including determining the time required for the vehicle and the trailer to navigate the intersection and subsequently reach a target speed without obstructing oncoming vehicles.
5. The method according to claim 4, wherein: The vehicle telemetry data includes a plurality of paths along the intersection taken by the plurality of remote vehicles, the method further comprising: determining an average path along the intersection using the plurality of paths along the intersection taken by the plurality of remote vehicles; determining an interior path boundary along the intersection using a plurality of paths along the intersection taken by the plurality of remote vehicles; and An outer path boundary along the intersection is determined using the plurality of paths along the intersection taken by the plurality of remote vehicles.
6. The method according to claim 5, further comprising: The average path is compared to the inner path boundary and the outer path boundary to determine an operability cost value for the intersection. 7 . The method of claim 6 , wherein determining the cost value of the intersection comprises determining the cost value of the intersection taking into account an operability cost value of the intersection.
8. A tangible, non-transitory machine-readable medium comprising machine-readable instructions that, when executed by a processor, cause the processor to: Receive map data, where The map data includes geometric data of the intersection on the road, and the vehicle is approaching the intersection on the road; receiving crowdsourced vehicle telemetry data from a plurality of remote vehicles, wherein the vehicle telemetry data includes speeds of the plurality of remote vehicles traveling along an intersection of the road; using the map data to determine sight distance; using the vehicle telemetry data to determine an average vehicle speed along the intersection; determining a time available for navigating through the intersection using the sight distance and an average vehicle speed along the intersection; determining a ratio between the time available for navigating through the intersection and the time required to navigate through the intersection; and The cost value for the intersection is determined using the ratio between the time available to navigate through the intersection and the time required to navigate 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: selecting a route based on the cost value of the intersection; The vehicle is commanded to automatically travel along the selected route.
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: The time required for a vehicle and a trailer connected to the vehicle to pass through the intersection before an oncoming vehicle arrives is determined.
