Patent Application
20200125117
Enabling a vehicle to follow closely behind one vehicle safely through partial or full automation has significant fuel savings, safety, and/or labor savings benefits, but is generally unsafe when a driver tries to do this manually. Presently, during normal driving, vehicle motion is controlled either manually, by a driver, or by convenience systems, such as cruise control or adaptive cruise control. The various types of cruise control systems control vehicle speed to make driving more pleasurable or relaxing, by partially automating the driving task. Some of these systems use range sensors and/or vehicle sensors to control the speed to maintain a constant headway relative to the leading vehicle (also referred to herein as a front vehicle). In general, these cruise control systems provide minimal added safety, and do not have full control of the vehicle (in terms of being able to fully brake or accelerate).
Driver control does not match the safety performance of even current systems, for several reasons. First, a driver cannot safely maintain a close following distance. In fact, the relatively short distances between vehicles necessary to get any measurable fuel savings results in an unsafe condition if the vehicle is under driver control, thereby risking a costly and destructive accident. Further, the driver is not as capable of maintaining an optimal headway as an automated system is. In fact, a driver trying to maintain a constant headway often causes rapid and large changes in command (accelerator pedal position for example), resulting in a loss of efficiency.
Thus, it would be desirable to have reliable and economical semi-automated vehicular convoying/platooning systems which enable vehicles to follow closely together in a safe, efficient, convenient manner.
While this is a lofty goal, it is generally easier said than done. In particular, as the platooning industry matures, unforeseen difficulties arise when attempting to create a platooning system (or any system that employs vehicle-to-vehicle communication) that is safe. As such, there is a need in the art to address safety issues as they arise.
In order to describe the various aspects of the present disclosure, some detailed description now will be provided, by way of illustration, with reference to the accompanying drawings, in which:
The present invention will now be described in detail with reference to several embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention, including the description of a plurality of different aspects of the invention, including, in some cases, one or more alternatives. It will be apparent to those skilled in the art that the invention can be practice without implementing all of the features disclosed herein. Further, although many embodiments included in the instant application are related to the concept of platooning, it should be appreciated that many broader applications are envisioned.
Without limitation, the Applicant has proposed various vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are automatically, or semi-automatically controlled to closely follow a lead/front vehicle in a safe manner. By way of example, U.S. patent application Ser. Nos. 15/605,456, 15/607,902; 13/542,622 and 13/542,627; U.S. Provisional Patent Application Nos. 61/505,076, 62/377,970 and 62/343,819; and PCT Patent Application Nos. PCT/US2014/030770, PCT/US2016/049143, PCT/US2018/41684, PCT/US2017/04771, PCT/US2017/047825 and PCT/US2016/060167 describe various vehicle platooning systems in which a trailing vehicle (also referred to herein as a rear vehicle) is at least partially automatically controlled to closely follow a designated lead vehicle (also referred to herein as a front vehicle). Each of these earlier applications are incorporated herein by reference in their entirety for all purposes.
In the present application, section titles may be used. It should be understood that section titles are not meant to be limiting in any way whatsoever (including with regard to information presented in that section). Section titles are meant to make the instant disclosure easier to read, but should not be construed to indicate that a discussion in one section is not applicable to other sections, and vice versa.
One of the goals of platooning is typically to maintain a desired position between the platooning vehicles and/or a desired relative speed and/or time headway (e.g., a gap may refer to a distance, a headway, or both). Thus, it should be appreciated that, herein, any reference to the term “gap” could refer to a distance, a headway, or both. Further, while the term “maintain” is used throughout this disclosure, maintaining may mean staying within a gap (e.g., staying within a threshold amount of a distance/headway (e.g., +/−3 meters, +/−0.3 seconds)), staying at a gap, and/or keeping at least a certain gap. Further, a desired gap may include a relative distance, time headway, and/or angle/offset. A longitudinal distance and/or time headway is frequently referred to herein as a “target gap”. That is, it is desirable for the trailing vehicle (e.g., a rear vehicle) to maintain a designated gap relative to a specific vehicle (e.g., a lead vehicle). The vehicles involved in a platoon will typically have sophisticated control systems suitable for initiating a platoon, maintaining the gap under a wide variety of different driving conditions, and gracefully dissolving (e.g., ending) the platoon as appropriate. It should be appreciated that herein, a gap may refer to a distance, a time headway, or either.
As described herein, the concept of platooning, also known as convoying, is still in its infancy. Academics have toyed with the concept over the last few decades, but to date there are no commercial systems on the road where a vehicle is at least partially controlled by another vehicle via a vehicle-to-vehicle connection (V2V). The benefits provided by such systems are obvious. Namely, the safety provided by these systems is far greater than a system where a rear vehicle doesn't begin to slow down until its radar or LIDAR sensors determine that a lead vehicle is slowing down. Further, by being able to follow another vehicle at a close distance, in some cases both a rear vehicle and a front vehicle may experience significant fuel savings.
As platoonable vehicles (e.g., vehicles capable of platooning) begin to roll out of the labs and into commercial production, their adoption faces significant challenges. For example, original equipment manufacturers (OEMs), fleets (e.g., freight hauling companies), and other customers of platooning systems require systems that platoon safely.
Herein, systems and methods for such a safe platooning systems are described.
In various embodiments, vehicles 110, 112, 114, 116, 120, and 122 may be configured to platoon, and may platoon with one another. In some embodiments, vehicles may transmit and/or receive data (e.g., to a NOC and/or fleet management system, etc.) including, but not limited to data indicating: whether they are available to platoon; whether they are platooning; whether a platoon they were part of dissolved; what direction they are traveling; what direction they are predicted (e.g., predetermined/planning on/suggested) to be traveling on for a particular period of time; when they are expected to stop (e.g., predetermined to stop, planning on stopping, suggested stopping time); where they plan on stopping; what route(s) they plan to travel (e.g., a route suggested and/or determined by a system, a route determined by a navigation/mapping system based on their destination such a system may be a rendezvousing system, a fleet management system, a navigation system, etc.); what type of platooning system they are equipped with; how many hours they have been on the road; weather they are capable of following the leader (e.g., if one or more vehicles can platoon without a driver); whether they are capable of being the leader in a follow-the-leader system; whether the vehicle is fully autonomous (e.g., capable of level 4 according to the SAE classification system); how much fuel they have saved; how much money they have saved; an area they are allowed to travel within; an area they are not allowed to travel outside of; whether they are capable of platooning on city streets; whether they are only capable of platooning on a highway; whether they are capable of platooning on non-public roads; whether they are capable of platooning in a particular construction site, mine, forest, etc.; and whether other attributes associated with a vehicle's account allows them to platoon. As should be understood, one or more of these attributes may be used to determine whether a vehicle can platoon with one or more additional vehicles, and whether a vehicle should platoon with one or more additional vehicles. It is contemplated that in some embodiments, a system may rank one or more vehicles with which a vehicle should platoon. In such an embodiment, if a target vehicle (e.g., a vehicle with a high ranking) that a first vehicle attempts to platoon with platoons with second vehicle before the first vehicle is able to platoon with the target vehicle, then the first vehicle may select another (e.g., the next) ranked vehicle that the system would like it to (e.g., determines that it should attempt to) platoon with.
In addition to these factors, other information that a vehicle may transmit and/or receive may include data including, but not limited to data associated with a/an: position, latitude, longitude, altitude, heading, speed, longitudinal and lateral acceleration, relative angle, type of load (e.g., type of materials a vehicle is carrying), brake status, brake pressure, path history, path projection, travel plans, vehicle size, vehicle type, brake type, current operating mode (autonomous or manual), map data, traffic information, GPS augmentation information (e.g., delays from infrastructure), wheel speed, wheel torque, gross torque, net torque, wind, rain, music, video, infotainment system, suspension, axle weight(s), transmission status (e.g., what gear the vehicle is in, what gear the vehicle was in, what gears the vehicle transferred from and to (e.g., fifth gear to fourth gear)), previous transmission status, hybrid vehicle drivetrain (e.g., a parallel hybrid or an electric hybrid), whether a vehicles with a vehicle with an electric mo, battery, electronic throttle control, throttle pedal, brake pedal, power steering, adaptive cruise control, a blowout, interior lighting, exterior lighting, retarder, anti-lock brakes, emergency braking, engine governor, powertrain, gear ratio, wheel size, wheel type, trailer length, trailer type, trailer height, amount of trailers, trailer position, current trailer position, past trailer position, tractor type, tractor height, transceiver type, current fuel, next determined stop, projected miles remaining until fuel tanks are empty, malfunctions, turn signals, LIDAR, radar, ultrasonic sensors, road surface, wheel angle, tire pressure, cabin temperature, engine temperature, trailer interior temperature, camera, fleet of vehicles, NOC, computer vision, other vehicle traveling in the same direction, other vehicle traveling in an opposite direction, and intervening traffic (e.g., cut-ins, also referred to as the situation when a vehicle enters an area between a lead vehicle and a rear vehicle). This information can be used by one or more vehicles, systems, fleets, etc. to determine whether a vehicle may platoon with another vehicle and/or to determine the best vehicle with which a vehicle may platoon. Again, it is contemplated that in some embodiments, a system may rank one or more vehicles with which a vehicle should platoon, and this ranking may be based on vehicle the vehicle attributes described above. In such an embodiment, if a target vehicle that a first vehicle wishes to platoon with platoons with another vehicle before the first vehicle is able to platoon with the target vehicle, then the first vehicle may move to another (e.g., the next) ranked vehicle that the system would like it to (e.g., determines that it should attempt to) platoon with.
It should be understood that, herein, when a system determines a rendezvous location and/or rendezvous time, that any of these attributes/information/data may be used alone or in combination to determine: whether two or more vehicles can platoon together, a rendezvous location, a rendezvous time, etc.
In addition to NOC 240, client devices 252 (e.g., a smartphone or tablet), 254 (e.g., a desktop computer or terminal), and 256 (e.g., a laptop computer or terminal) may be used to send and/or receive information about vehicles 210 and 220, NOC 240, or information from canonical sources such as the Internet (e.g., Google Maps or another online map provider, a traffic provider, a weather provider, etc.). Client devices can be used to view attributes of vehicles 210 and 220 such as their location, an estimate of their weight, their speed, an amount of engine torque, amount of applied break, a destination, etc.
Of course, it should be appreciated that the system described in
In the example embodiment illustrated in system 300, a platoon controller 310, receives inputs from a number of sensors 330 on the tractor and/or one or more trailers or other connected units, and a number of actuator controllers 350 (also referred to as electronic control units or ECUs) arranged to control operation of the tractor's powertrain and other vehicle systems. An actuator interface 360 may be provided to facilitate communications between the platoon controller 310 and the actuator controllers 350. In some embodiments, one or more of the actuator interfaces 360 may be included in one or more of the actuator controllers 350 (e.g., an actuator interface may be included in an ECU). Platoon controller 310 also interacts with an inter-vehicle communications controller 370 (also referred to as an inter-vehicle communications ECU) which orchestrates communications with the platoon partner and a NOC communications controller 380 (also referred to as a NOC communication ECU) that orchestrates communications with a NOC. The vehicle also may have selected configuration files 390 that include known information about the vehicle.
Some of the functional components of the platoon controller 310 include gap controller 312, a variety of estimators 314, one or more partner vehicle trackers 316 and various monitors 318. In many applications, the platoon controller 310 will include a variety of other components 319 as well.
Some of the sensors utilized by platoon controller 310 may include GNSS unit 331, wheel speed sensors 332, inertial measurement devices 334, radar unit 337, lidar unit 338, cameras 339, accelerator pedal position sensor 341, steering wheel position sensor 342, brake pedal position sensor 343, and various accelerometers 344. Of course, not all of these sensors will be available on all vehicles involved in a platoon and not all of these sensors are required in any particular embodiment. A variety of other sensors 349 (now existing or later developed or commercially deployed) may be additionally or alternatively be utilized by platoon controller 310 in other embodiments.
Many (but not all) of the described sensors, including wheel speed sensors 332, radar unit 337, accelerator pedal position sensor 341, steering wheel position sensor 342, brake pedal position sensor 343, and accelerometer 344 are relatively standard equipment on newer trucks (tractors) used to pull semi-trailers. However, others, such as GNSS unit 331 and lidar unit 338 (if used) are not currently standard equipment on such tractors or may not be present on a particular vehicle and may be installed as needed or desired to help support platooning.
Some of the vehicle actuator controllers 350 that platoon controller 310 may direct at least in part include engine torque controller 352; brake controller 354; transmission controller 356; steering/automated steering controller 357; and clutch controller 358. Of course, not all of these actuator controllers will be available or are required in any particular embodiment and it may be desirable to interface with a variety of other vehicle actuator controllers 359 that may be available on the vehicle as well. Therefore, it should be appreciated that the specific actuator controllers 350 directed or otherwise utilized by the platoon controller on any particular controlled vehicle may vary widely. Further, the capabilities of any particular actuator controller (e.g. engine torque controller 352), as well as its interface (e.g., the nature and format of the commands, instructions, requests and messages it can handle or generate) will often vary with the make and model of that particular actuator controller. Therefore, an actuator interface 360 is preferably provided to translate requests, commands, messages and instructions from the platoon controller 310 into formats that are appropriate for the specific actuator controller hardware and software utilized on the controlled vehicle. The actuator interface 360 also provides a mechanism for communicating/translating messages, commands, instructions and requests received from the various actuator controllers back to the platoon controller 310. In some embodiments, an appropriate actuator interface may be provided to interact with each of the specific vehicle controllers utilized. In various embodiments, this may include one or more of: an engine torque interface 361; a brake interface 362; a transmission interface 364; a retarder interface 365; a steering interface 367; and/or any other appropriate controller interface 369. In some embodiments, various controllers may be combined (e.g., in the case of a chasses controller, or an engine ECU that also controls a retarder—which may obviate the need for a retarder ECU).
Large trucks and other heavy vehicles frequently have multiple systems for “braking” the truck. These include the traditional brake system assemblies mounted in the wheels of the vehicle—which are often referred to in the industry as the “foundation brakes.” Most large trucks/heavy vehicles also have a mechanism referred to as a “retarder” that is used to augment the foundation brakes and serve as an alternative mechanism for slowing the vehicle or to help prevent the vehicle from accelerating down a hill. Often, the retarder may be controlled by the engine torque controller 352 and in such embodiments, the retarder can be controlled by sending appropriate torque commands (which may be negative) to engine torque controller 352. In other embodiments a separate retarder controller (not shown) may be accessible to, and therefore directed by, platoon controller 310 through an appropriate retarder interface 365. In still other embodiments, the platoon controller 310 may separately determine a retarder command that it sends to the actuator interface 360. In such embodiments the actuator interface will interpret the retard command and pass on appropriate retardation control commands to an Engine ECU or other appropriate vehicle controller.
The communications between vehicles may be directed over any suitable channel and may be coordinated by inter-vehicle communications controller 370. As described above, the DSRC protocol may work well.
The specific information transmitted back and forth between the vehicles may vary widely based on the needs of the controllers. In various embodiments, the transmitted information may include the current commands generated by the platoon controller 310 such as requested/commanded engine torque, and/or requested/commanded braking deceleration 382. They may also include steering commands, gear commands, etc. when those aspects are controlled by platoon controller 310. Corresponding information is received from the partner vehicle, regardless of whether those commands are generated by a platoon controller or other suitable controller on the partner vehicle (e.g., an adaptive cruise control system (ACC) or a collision mitigation system (CMS)), or through other or more traditional mechanisms—as for example, in response to driver inputs (e.g., accelerator pedal position, brake position, steering wheel position, etc.).
In many embodiments, much or all of the tractor sensor information provided to platoon controller 310 is also transmitted to the platoon partner and corresponding information is received from the platoon partner so the platoon controllers 310 on each vehicle can develop an accurate model of what the partner vehicle is doing. The same is true for any other relevant information that is provided to platoon controller 310, including any vehicle configuration information 390 that is relevant to platoon controller 310. It should be appreciated that the specific information transmitted may vary widely based on the requirements of platoon controllers 310, the sensors and actuators available on the respective vehicles, and the specific knowledge that each vehicle may have about itself.
The information transmitted between vehicles may also include information/data about intended future actions as will be discussed in greater detail below. For example, if the lead vehicle knows it is approaching a hill, it may expect to increase its torque request (or decrease its torque request in the context of a downhill) in the near future and that information can be conveyed to a rear vehicle for use as appropriate by the platoon controller 310. Of course, there is a wide variety of other information that can be used to foresee future torque or braking requests and that information can be conveyed in a variety of different forms. In some embodiments, the nature of the expected events themselves can be indicated (e.g., a hill, curve, or exit is approaching) together with the expected timing of such events. In other embodiments, the intended future actions can be reported in the context of expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected. Of course, there are a wide variety of different types of expected events that may be relevant to the platoon control.
The communications between the vehicles and the NOC may be transmitted over a variety of different networks, such as a cellular network, various Wi-Fi networks, DSRC networks, satellite communications networks and/or any of a variety of other networks as appropriate. The communications with the NOC may be coordinated by NOC communications controller 380. The information transmitted to and/or received from the NOC may vary widely based on the overall system design. In some circumstances, the NOC may provide specific control parameters such as a target gap. These control parameters or constraints may be based on factors known at the NOC such as speed limits, the nature of the road/terrain (e.g., hilly vs. flat, winding vs. straight, etc.) weather conditions, traffic or road conditions, etc. In other circumstances the NOC may provide information such information to platoon controller 310. The NOC may also provide information about the partner vehicle including its configuration information and any known relevant information about its current operational state such as weight, trailer length, etc.
Lastly, with regard to
Safety Associated with Weather
For example, in some embodiments the activation of windshield wipers may cause a vehicle to take various actions to improve safety. In some embodiments, a dissolve may occur in response to the activation of windshield wipers. Of course, not every activation of windshield wipers may cause a dissolve, since, for instance, a driver may accidently activate windshield wipers (in various safety mechanisms described herein, a video camera may receive information and a system may determine that a safety mechanism (such as those described herein), and may activate a response (such) as a dissolve, or prevent a response from occurring based on the received camera information). As such, in some embodiments, various other factors may contribute to a determination as to whether a platoon should dissolve. For example, in some embodiments a dissolve may occur when a speed of windshield wipers exceeds a threshold amount (e.g., when the speed of windshield wipers exceeds half of their maximum speed), and/or various attributes of a platooning or other automation system are present.
In some embodiments, devices other than, or in addition to windshield wipers may be used to determine whether a dissolve or other action (e.g., an increase in gap) may be performed. For example, modern vehicles are often equipped with rain and/or other weather sensors. In some embodiments, the detection of rain and/or other weather conditions (e.g., ice) detected by a sensor (e.g., a rain sensor that would cause windshield wipers to activate) may cause a dissolve. Similarly, the activation of rain wipers on other parts of a vehicle may cause a dissolve and/or other action. For example, the detection of weather, and/or the activation of wipers on a headlight, mirror, and/or other portion of a vehicle may cause a dissolve or other action.
Further, the detection of the conditions of a road may cause a dissolve and/or other action. For example, sensors indicating that a threshold amount (e.g., any, 1 inch) of liquid (e.g., rain water) may cause a platoon to dissolve, or at least travel at below a certain speed, or at or above a threshold gap (e.g., distance/headway). In some embodiments it is contemplated that a vehicle sensor may determine at least a portion of a composition of a liquid (e.g., determine an amount of oil, grease, water) within a liquid, and perform various actions based on the composition (e.g., dissolve if the liquid includes a threshold amount of oil).
Safety Associated with Tire Pressure
Tire pressure that is too high can (see, overinflated tire 530) result in less tire touching the ground. In turn, this can create a harsher ride as well as compromised traction and the ability to stop quickly. Moreover, an overinflated tire can lead to excessive inner tire tread wear—decreasing the overall life of tires.
Conversely, if tire pressure is too low (see, underinflated tire 510), too much of the tire may be in contact with the road, and too much deformation may occur as the tire rolls through the contact patch (e.g., the portion of the tire that is in contact with the road). Underinflated tires wear prematurely and have the potential to overheat. Underinflation can also cause a tire to bend more as it moves, resulting in a build-up of excessive heat, an increase in rolling resistance, and a decrease in fuel economy by as much as 5 percent.
As such, in various embodiments tire pressure may be monitored as condition precedent to platooning. As discussed herein, goals of platooning include safety and fuel efficiency. Underinflated tires 510 can reduce fuel efficiency. Overinflated tires can reduce a vehicle's ability to brake as intended/projected. In either case, in response to tires being underinflated by a particular amount (e.g., being inflated less than a threshold amount) or to tires being overinflated by a particular amount (e.g., being overinflated over a threshold amount), an action may be taken by a platooning system (e.g., a PECU) or other vehicle system. For example, platooning may be disabled (which may include causing a platoon to dissolve) if a threshold number of tires are under and/or overinflated. In some embodiments a notification may be provided (e.g., on a GUI, by a dashboard light, via audio) indicating that tires are under and/or over inflated, and that they should be corrected, must be corrected, etc. In some embodiments a notification may indicate a location where a vehicle may refill their tires. In some embodiments, a tire may be inflated and/or deflated (e.g., by a pump) in response to determining that a tire is overinflated or underinflated when vehicles are platooning. In some embodiments, an amount of inflation in a tire (or an amount of change in inflation) may cause one or more a system to cause (e.g., notify drivers) vehicles in a platoon to change positions in the platoon. Moreover, it is contemplated that in some embodiments, if a tire is losing air rapidly (e.g., if a nail punctures a tire), a notification may be provided, which may be more prominent than a notification simply indicating that a tire is not inflated to a correct amount.
In some embodiments involving platooning, a model may project how long it takes a vehicle to stop. An amount of tire pressure may affect this model as it may increase or decrease a predicted distance/time it may take a vehicle to stop. As such, in order to ensure a rear vehicle may brake better than a lead vehicle, an ordering of vehicles may be arranged based at least in part on tire pressure. It should be understood that various sensors may be implemented to determine tire pressure (and/or weight, among other characteristics). For example, strain gauges may be used to measure tire pressure.
Of course, tire pressure is just one of a variety of vehicle attributes that can be determined, and in which an action may be taken in response. Herein, it should be understood that in addition to, or in the alternative, an action such as braking, dissolving, or another measure to provide increased safety may be based on attributes (e.g., system attributes, vehicle attributes) including, but not limited to a/an: position, latitude, longitude, altitude, heading, speed, longitudinal and lateral acceleration, relative angle, type of load (e.g., type of materials a vehicle is carrying), brake status, brake pressure, path history, path projection, travel plans, vehicle size, vehicle type, brake type, current operating mode (autonomous or manual), map data, traffic information, GPS augmentation information (e.g., delays from infrastructure), wheel speed, wheel torque, gross torque, net torque, wind, rain, music, video, infotainment system, suspension, axle weight(s), transmission status (e.g., what gear the vehicle is in, what gear the vehicle was in, what gears the vehicle transferred from and to (e.g., fifth gear to fourth gear)), previous transmission status, hybrid vehicle drivetrain (e.g., a parallel hybrid or an electric hybrid), whether a vehicles with a vehicle with an electric mo, battery, electronic throttle control, throttle pedal, brake pedal, power steering, adaptive cruise control, a blowout, interior lighting, exterior lighting, retarder, anti-lock brakes, emergency braking, engine governor, powertrain, gear ratio, wheel size, wheel type, trailer length, trailer type, trailer height, amount of trailers, trailer position, current trailer position, past trailer position, tractor type, tractor height, transceiver type, current fuel, next determined stop, projected miles remaining until fuel tanks are empty, malfunctions, turn signals, LIDAR, radar, ultrasonic sensors, road surface, wheel angle, tire pressure, cabin temperature, engine temperature, trailer interior temperature, camera, fleet of vehicles, NOC, computer vision, other vehicle traveling in the same direction, other vehicle traveling in an opposite direction, and intervening traffic (e.g., cut-ins, also referred to as the situation when a vehicle enters an area between a lead vehicle and a rear vehicle).
Safety Associated with Brake Inputs
As described herein, in some embodiments a vehicle's brakes may be employed due to a dissolve, traveling down a hill, during a draw-in, when slowing down for traffic, and/or in countless other situations. Generally, platooning systems cause at least a rear vehicle to apply its brakes in response to a front vehicle applying its brakes. Although, it is contemplated that a platooning system may cause various vehicles (e.g., front, rear) to apply their brakes in response to a variety of other conditions (e.g., if a vehicle in front of a front truck slows down).
While the system may provide a correct amount of braking (e.g., brake pressure), in some embodiments a driver may assert more control over a vehicle. For example, a driver may desire more brake than a platooning system applies in a certain situation, for example to avoid a merging vehicle. In some embodiments, a driver may accomplish this by applying pressure (additional pressure in some cases) to a brake pedal (e.g., such that even though a platooning system is applying brakes, a driver may apply more brakes). This may provide a driver with an extra sense of control over a vehicle. Although, in some cases a platoon may dissolve in response to a driver applying pressure to a brake pedal. The determination of whether to dissolve or not may be based on which vehicle (for example the lead or follow truck) is applying the brakes, and how hard that vehicle's brakes are being applied.
In some instances, it is contemplated that other devices in addition to, or in combination with, a brake pedal being depressed may allow a driver/user to cause a vehicle to apply more brakes than a platooning system applies. For example, an emergency stop mechanism may be used by a driver, which may cause brakes to engage and cause a gradual decrease in speed, a dissolve, and/or a hard brake. In some instances, such mechanisms may be disengaged. For example, in some embodiments a platooning system may control an amount of brakes despite pressure being put on a brake pedal, or any other type of stopping mechanism being activated.
Safety Associated with Braking Notifications
Such a setup may provide additional safety since some vehicles (e.g., trucks) may not be configured to activate brake lights in response to a braking activity caused by a platooning system. For example, some vehicles may be configured to only apply brake lights in response to a brake pedal being depressed. To add safety and cure such a deficiency, brake lights may be activated when a platooning system causes a vehicle to brake.
Moreover, brake lights 610A and 610B need not be located in the locations shown in
Safety Associated with Network Authorization
As described herein, such as with reference to
In some embodiments, a system may automatically determine how often a vehicle's authorization status should be updated. For example, a system may determine that it should update (e.g., either at a NOC or at a vehicle) its authorization to platoon based on various attributes such as weather, an amount of sunlight, an amount of traffic, wind, attributes of a particular route/road, etc. In one example, if a system determines that there is a small amount of rain it may update whether a vehicle may platoon every minute, and if the system determines that a larger amount of rain is falling the system may update whether the vehicle may platoon every 10 seconds.
In a similar manner, an authorization may only be valid in response to factors being met including: a vehicle being located in a particular geographic region, a vehicle traveling within a particular speed range, a vehicle traveling for a particular time/within a particular time range, a vehicle traveling for an amount of time after the initiation of a platoon, and/or other transient factors.
Safety Associated with Brake Temperatures
In some embodiments, an assessment (measurement, estimate, calculation) of brake temperatures may be used to determine actions performed by one or more platooning vehicles. For example, if brake temperatures become too high brake fade may occur. Brake fade is a term used to describe a temporary reduction or complete loss of braking power of a vehicle's braking system. Brake fade occurs when the brake pad and the brake rotor no longer generate sufficient mutual friction to stop the vehicle at its preferred rate of deceleration. The end result being inconsistent or unexpected braking system behavior, often resulting in increased stopping distances. As discussed herein (e.g., with reference to improper tire pressure), unpredicted braking distances/times can cause problems with a platooning system because vehicles may not stop as a system predicts. As such, it is important to assess at least one brake's temperature to correctly model and/or estimate how long a vehicle will take to stop, determine a desirable distance/headway of a gap, and/or determine an ordering of one or more platooning vehicles.
In some embodiments, a platoon may dissolve in response to a brake temperature being above a threshold amount. Further, in some embodiments, a brake temperature may cause a gap between two or more vehicles to increase and/or decrease when traveling over a hill and/or a grade and/or distance of a downhill section of a road. In one example, a notification may be provided to one or more vehicles in a platoon, and/or a NOC/remote terminal, indicating that a temperature of one or more brakes is too high. For example, a notification may appear on a graphical user interface (GUI), a heads-up user display (HUD), a dashboard, and/or an audio notification may be provided to a user within a vehicle and/or remotely. Of course, other notifications described herein may be provided in the same and/or similar ways.
Further, braking temperature may be used alone or in combination with other vehicle and/or system attributes described herein to determine a gap, whether a dissolve should occur, etc.
Safety Associated with Driver Takeovers
In some embodiments, a user may takeover a vehicle from a system (e.g., a platooning system), such that the user controls at least a portion of a vehicle. In various embodiments, a user may be a driver of a vehicle, a passenger in a vehicle, an operator of a vehicle (e.g., at a remote terminal), or otherwise be in control of a vehicle (e.g., a driver of a front vehicle controlling some or all of a rear vehicle).
In various embodiments described herein, a takeover may cause at least some of the automated functions of a vehicle to stop (e.g., command of these functions may be turned over to a user of a vehicle). For example, if a user depresses a brake pedal (e.g., at all, for a particular period of time, above a threshold amount, longer than a threshold amount of time, etc.) a platoon may dissolve. Similarly, in some embodiments if a user depresses a throttle/accelerator pedal or if it is actuated/an equivalent signal is provided to an engine/motor (e.g., at all, for a particular period of time such as 2 seconds, 5 seconds, etc.), a platoon may dissolve. In one example, the activation of a hand brake and/or emergency mechanism may cause a takeover to occur (e.g., cause at least some of the automated functions of a vehicle to stop).
Of course, in some embodiments only a portion of automated controls of a vehicle may stop when a brake pedal or throttle is depressed. For example, in some embodiments automatic steering may stop such that a user may need to steer, while controls such as accelerating and braking may still be automated. In some embodiments, the stopping of various automated functions may occur only for a certain amount of time before returning to being automated. For example, a brake may be tapped and a user may obtain control of braking and/or accelerating for a few seconds (or a time which may be based on a gap), and then control of braking and/or accelerating may return to being automated.
In some embodiments, an indicator may be activated when a user gains control of a vehicle. For example, in response to a dissolve a light, sound, or other notification may be provided to other drivers (e.g., other platoon members, other vehicles on a road), a NOC, a user at a remote terminal, etc. For example, when a user gains at least some or total control of a vehicle a light on a side of a platooning vehicle indicating the vehicle is platooning may turn off. As another example, a vehicle may sound an alarm, flash one or more lights, cause one or more other vehicles to activate one or more lights, etc. in order to notify others that a user has regained control of a vehicle (e.g., a platoon dissolved).
Safety Associated with Platooning Conditions
As described herein, a variety of attributes associated with vehicles, conditions exterior to vehicles, conditions associated with a NOC, and/or conditions associated with a remote terminal may contribute to whether it is safe to platoon or unsafe to platoon. In various embodiments, a determination as to whether it is safe to platoon may be based on a combination and/or amount of factors. For example, platooning may be allowed if a vehicle is in a particular area, if there is less than a particular amount of rain, and a vehicle's drive wheels are inflated above a particular threshold. It should be understood that certain attributes may contribute to and/or cause a safe or unsafe condition when that attribute is below or above a threshold amount. For example, a vehicle may be allowed to platoon when a road's grade is below a threshold amount, when a trailer height is below a threshold amount, when a vehicle's available horsepower is above a threshold amount, when an amount of traffic is below a threshold amount, etc.
As such, in various embodiments, these attributes may include, but are not limited to a/an: position, latitude, longitude, altitude, heading, speed, longitudinal and lateral acceleration, relative angle, type of load (e.g., type of materials a vehicle is carrying), brake status, brake pressure, path history, path projection, travel plans, vehicle size, vehicle type, brake type, current operating mode (autonomous or manual), map data, traffic information, GPS augmentation information (e.g., delays from infrastructure), wheel speed, wheel torque, gross torque, net torque, wind, rain, music, video, infotainment system, suspension, axle weight(s), transmission status (e.g., what gear the vehicle is in, what gear the vehicle was in, what gears the vehicle transferred from and to (e.g., fifth gear to fourth gear)), previous transmission status, hybrid vehicle drivetrain (e.g., a parallel hybrid or an electric hybrid), whether a vehicles with a vehicle with an electric motor, battery, electronic throttle control, throttle pedal, brake pedal, power steering, adaptive cruise control, a blowout, interior lighting, exterior lighting, retarder, anti-lock brakes, emergency braking, engine governor, powertrain, gear ratio, wheel size, wheel type, trailer length, trailer type, trailer height, amount of trailers, trailer position, current trailer position, past trailer position, tractor type, tractor height, transceiver type, current fuel, next determined stop, projected miles remaining until fuel tanks are empty, malfunctions, turn signals, LIDAR, radar, ultrasonic sensors, road surface, wheel angle, tire pressure, cabin temperature, engine temperature, trailer interior temperature, camera, fleet of vehicles, NOC, computer vision, other vehicle traveling in the same direction, other vehicle traveling in an opposite direction, and intervening traffic (e.g., cut-ins, also referred to as the situation when a vehicle enters an area between a lead vehicle and a rear vehicle).
As repeated throughout this disclosure, one of the goals of platooning is to increase driver safety. To that end, safety benchmarks may be generated, for example, based on publicly available Federal Motor Carrier Safety Administration (FMSCA) collision data.
In various embodiments, in particular for testing, some safety attributes may be activated or not activated. This disclosure described many of these attributes, but the attributes should not be considered limiting in any way. For example, in some embodiments safety measures described herein may be used during system testing but not normal system use. In some embodiments safety measures described herein may be implemented during normal system use, but not activated during testing. Of course, it should be understood that a system can be configured to use some, all, or none of the safety measures described herein (e.g., dissolving a platoon due to weather, activating brake lights in response to system braking, updating authorization status, etc.). Further, safety measures that are not discussed herein may be contemplated and implemented in various tests and/or full commercial deployment.
In some embodiments, to increase the safety of a system, various ECUs and software versions are checked and rechecked at various times. Similarly, safety monitors (e.g., a PECU safety monitor) may be updated and/or checked at various times. These times may include while a vehicle is traveling (e.g., every hour, every day, every week), in response to a software update (e.g., an over-the-air update), before a vehicle begins a platoon, after a vehicle platoons, before a vehicle starts travelling, and/or after a vehicle stops (e.g., when it is in park).
In some embodiments herein, various actions may occur if a vehicle does not operate as desired (e.g., if it does not meet safety requirements). For example, any of the attributes above may be tested, and instead of dissolving a platoon or some other action while a vehicle is moving, a vehicle may be prevented from moving and/or platooning in response to the vehicle not meeting a desired safety goal. For example, a vehicle may not be allowed to start and/or platoon if: its ECUs and/or software is not configured correctly; its safety monitor is not updated and/or is configured incorrectly; if a brake ECU (BECU) and/or other device does not activate brake lights when a system causes a braking event; if weather is undesirable and/or a road surface is suboptimal (e.g., too wet); if a driver is too aggressive while driving and/or platooning (e.g., if they are exceeding a speed limit, taking turns to fast, and/or otherwise being unsafe); etc.
In some embodiments, a platooning system may only operate in certain domains, which may be referred to as operational design domains (ODDs). Although nothing in this section is not intended to be limiting and should not be construed as being limiting, it should be understood that for some purposes, limiting a system to operate in an ODD may be required (e.g., for safety purposes). It should also be understood that an ODD may include none, some, all, or additional attributes such as those described in this paragraph. In some embodiments, an operational design domain may define operational capabilities, driver vehicle control responsibilities, operating environments, and/or operating environment constraints. An operational capability may include vehicle controls and/or user interfaces. For example, vehicle controls may include acceleration, deceleration, and/or disengaging a platoon (e.g., dissolving a platoon). User interfaces may include information including a system's status, whether a platoon is being engaged (e.g., drawing-in), whether a platoon is being disengaged (e.g., dissolving), and/or information/connectivity to/from a platoon cloud service (e.g., a NOC). Driver vehicle control responsibilities may include responsibilities for a front (lead) vehicle driver and/or a rear (following) vehicle driver. Front vehicle driver responsibilities may include steering, accelerating, and/or decelerating. Rear vehicle driver responsibilities may include steering. Operating environments may include weather conditions and/or road attributes. Weather conditions may include dry roads, wet roads, rain, crosswinds, and/or whether it is dusk/dawn. Road attributes may include a divided highway, a multi-lane highway, and/or a limited access road. Operating environment constraints may include road constraints, situational constraints, and/or weather conditions. Road constraints may include whether a road is urban, city, residential, and/or rural, includes undivided highways, construction zones, mountain passes with unsecured steep slopes, roads without a shoulder or viable runoff area, and/or weather a road is dirt/unpaved. Situational conditions may include vehicle cut-ins, when a vehicle speed is below 45 miles/hour, when a vehicle speed is above 70 miles/hour, an amount of highway entrance/exit ramps, whether an engine fault is indicated, whether an ABS fault is indicated, whether a weight or load is not within a specification, whether tire pressure is low and/or high, and/or whether a brake fault is indicated. Weather conditions may include whether there is snow and/or ice.
In some embodiments, a platoon may be dissolved to maintain a certain level of safety. For example, a platoon may be dissolved in response to deceleration less than necessary during platooning. A platoon may be dissolved in response to unintended or excessive acceleration during platooning. A platoon may be dissolved in response to acceleration that is less than necessary during platooning. A platoon may be dissolved in response to unintended or excessive deceleration during platooning. A platoon may be dissolved in response to an unintended platoon being formed. A platoon may be dissolved in response to a failure to notify a user (e.g., a driver or user at a remote terminal) of a platoon status. A platoon may be dissolved in response to vehicle instability during intended deceleration while platooning. A platoon may be dissolved if inaccurate information is received from a NOC/network while platooning. Of course, this list is not exhaustive, in some embodiments a platoon may dissolve in response to a combination of the aforementioned situations, and in some embodiments action may be taken that does not include dissolving a platoon. For example, in response to unintended or excessive deceleration during platooning, braking may be lessened or prevented (either by the vehicle that is decelerating unintendedly or excessively, or by an external command).
In addition to the list above, in various embodiments, a platoon may be dissolved in response to: one or more platooning vehicles stopping; a curve above a threshold degree on a highway; a curve above a threshold degree in addition to rain/wet roads on a highway; vehicles being offset (e.g., where two vehicles are in two different lanes) and one of the vehicles stops; an aggressive braking event by a front and/or rear vehicle; erroneous braking by a front and/or rear vehicle; a vehicle tailgating a rear vehicle; a cut-in (e.g., where a vehicle changes lanes to be in between two platooning vehicles); a vehicle slowing down in front of a front vehicle; inadvertently engaging (e.g., beginning a draw-in) in a platoon while in an urban or city environment; a user attempting to dissolve a platoon and the platoon not dissolving as intended; in advertently engaging a platoon while on a highway; a platoon failing to disengage during a cut-in; platooning in an unauthorized segment of a road; inadvertently engaging at low speeds lower than allowable for engaging; failing to notify a user of an engagement; failing to notify a user of a disengagement; unintended lateral movement of a trailer; and/or any combination thereof.
In various embodiments, a system meets or exceeds safety goals. For example, such goals may be determined to be protected to a requisite ASIL level. Various methods presented below may describe various goals and attributes associated with those goals (e.g., how to detect, when to detect by, when to dissolve by, etc.). Further, it should be understood that during any of these safety goals, a vehicle operator may be able to take control of one or more vehicles, which may cause a dissolve. In such an embodiment, a vehicle operator may takeover after one or more actions is taken by a platooning system (e.g., a detection of a fault). Further, a driver may be notified that a dissolve is occurring, and in some embodiments a platooning indicator (e.g., on an exterior of a vehicle) may indicate that a platoon has dissolved. In various embodiments, safety goals described below may be accomplished by the actuation of an automated emergency braking system and/or manual brake inputs that are greater than a braking level requested/commanded by a platooning system. In various embodiments, safety goals may be detected in within substantially 0.2 seconds (e.g., +/−0.1 seconds), and a dissolve may be initiated within substantially 0.2 seconds or 0.4 seconds (e.g., +/−0.2 seconds). In some embodiments, a dissolve may be considered initiated when a rate of a gap between a front vehicle and a rear vehicle is decreasing. A dissolve may be considered complete when a headway of substantially 1.6 seconds (e.g., +/−0.3 seconds) is achieved, for example.
In some embodiments, a safety goal is avoiding decelerating less than necessary. When decelerating less than necessary is detected, a platoon may dissolve. In some embodiments, decelerating less than necessary may be detected in response to: determining that a PECU is not commanding sufficient braking relative to a threat in front of it (e.g., a vehicle), determining the existence of a hardware and/or software fault, determining a single point fault, the initiation of an automated emergency braking system, and/or a brake pedal being manually depressed such that the manual braking request exceeds the braking levels requested by a platooning system
In some embodiments, a safety goal is avoiding unintended and/or excessive acceleration. Such a safety goal may be detected by: detecting that a PECU acceleration is incorrect relative to a threat in front of it (e.g., a vehicle), detecting a hardware and/or software fault, detecting a single point fault, a gap exceeds a required gap during ordinary platooning, and/or a relative velocity differential between two vehicles being greater than substantially 30 miles/hour (e.g., +/−5 miles/hour).
In some embodiments, a safety goal is avoiding unintended and/or excessive deceleration during platooning. Such a safety goal may be detected by a single point fault, a hardware and/or software fault, and/or a fault in a safety mechanism for detecting unintended or excessive deceleration. In some embodiments, brake lights shall activate (e.g., illuminate) when a platooning system initiates braking. Further, in some embodiments, a platooning system (e.g., a PECU) may stop external braking commands (e.g., from another vehicle and/or a NOC) within substantially 0.4 seconds (e.g., +/−0.2 seconds) when conditions exist that can result in excessive and/or unintended deceleration (e.g., a single point fault, which may be detected within substantially 0.2 seconds).
In some embodiments, a safety goal is avoiding inadvertent platooning. Such a safety goal may be accomplished at least in part by ensuring the absence of safety critical faults and/or conditions prior to enabling platooning, and/or detecting: an engage platoon fault, platooning after a driver initiates a disengage mechanism, platooning after a cut-in, platooning when platooning is not authorized (e.g., due to location, weather), a loss of an automated braking system's (ABS) integrity, and/or hardware and/or software faults. In some embodiments the detection of inadvertent/erroneous platooning may cause a dissolve within substantially 0.2 or 0.4 seconds.
It should be understood that the terms inadvertent and erroneous may be used interchangeably herein. For example, a platoon may inadvertently form, and/or a platoon may be platooning inadvertently. For example, a platoon may be inadvertently platooning when it continues to platoon despite a PECU detecting a system fault that would normally cause the platoon to dissolve. Similarly, a platoon may be erroneously platooning when it continues to platoon despite a PECU detecting a system fault that would normally cause the platoon to dissolve.
In some embodiments, a safety goal is to avoid failing to notify a driver of a platoon status (e.g., the platoon the driver's vehicle is a part of). A status may include a draw in, a dissolve, a disengaged, an engaged, and/or a normal platooning. Notifying a driver of a platoon status may be accomplished by conveying system status via a visual notification (e.g., a notification on a GUI on a vehicle's dashboard or a HUD), an audio notification (e.g., a beep, voice, horn), and/or a physical notification (e.g., a vibration, haptic response). Detecting such a safety goal may occur when it is determined that two or more of a visual notification, an audio notification, and a physical notification fault (e.g., by a hardware and/or software fault). In some embodiments, in response to determining a fault in one or more notification modalities (e.g., visual, audio, physical) prior to platooning, a platoon may not engage.
In some embodiments, a safety goal is to avoid vehicle instability during an intended deceleration. Such a safety goal may be accomplished at least in part by ensuring ABS integrity for and entire vehicle configuration prior to platooning, or detecting: a software and/or hardware fault and dissolving, a mismatch between a PECU and a BECU's trailer ABS integrity determinations. All of these conditions may result in a dissolve.
In various embodiments, as described throughout this application, a variety of safety mechanisms may be in place on a vehicle. In some cases, a platoon may dissolve, or not form, in response to a safety mechanism not operating as intended. Safety mechanisms may at least in part include, but are not limited to: a PECU heartbeat (e.g., where a PECU sends a status message at a specified regular interval, and a watchdog (e.g. a BECU) can monitor the status message and detect any faults that prevent the PECU from issuing its heartbeat within a specified amount of time); a platoon dissolve backup (e.g., where a dissolve is handled by BECU due to PECU's inability to cause a dissolve as it normally would), platooning dissolve); a platoon dissolve alert (e.g., UI/UX alerts indicating a dissolve is occurring when a PECU is unable to cause the alerts); an external brake request check (e.g., to ensure a desired external brake request is achieved (e.g., an amount, within a threshold time); ensuring braking is operating correctly using two of a DSRC signal, a radar, and a camera; monitoring gap control stability for encroachment on a minimum gap using a BECU; ensuring AEB is operating correctly; fusing radar information with camera information; updating/refreshing NOC authorization; platooning enable checks (e.g., an absence of safety faults, traveling above a threshold, having NOC authorization, having two or more vehicles indicate it is safe to platoon); counting an amount of successfully transmitted DSRC packets; ensuring that a BECU issues heartbeat messages to extended braking requests and/or a brake pedal position; counting an amount of received external brake control commands; dissolving in response to a BECU determining a PECU is not operating as desired; a PECU monitoring a status of a driver input device (DID); timestamps on video frames; a speed threshold; a brake air pressure monitor; a NOC authorization heartbeat; checking CAN data (e.g., to determine whether camera, radar, and/or fusion data is being dropped, stuck, and/or stale); BECU saturation; monitoring a yaw rate (e.g., of a trailer/5th wheel); PECU chip heartbeat monitoring; trailer ABS health monitoring; steering wheel monitoring; and windshield wiper monitoring.
In some embodiments, in addition to proactively dissolving when certain faults are present, both a PECU and a BECU may monitor a platooning gap and other conditions. There may be certain vehicle or environmental conditions or latent faults that cannot be indicated via J1939 that result in the system's control of the gap to be unstable. In various embodiments, a PECU and a BECU both monitor the gap independent of one another to determine if the current braking level is sufficient to avoid collision. In various embodiments, sufficiency may be defined by a braking command by a rear vehicle at exceeds the level required to avoid collision if a lead vehicle or cut-in vehicle were to apply an maximum/hard brake and the rear vehicle has some time delay and brake capacity to prevent a collusion.
In some embodiments, checks (also referred to as verifications) must be performed before platooning is enabled. These checks may include: an ability to monitor a PECU, EECU, and BECU; the absence of platoon disable faults; confirmation of intent to platoon from two drivers; determining that a road segment authorized for platooning; platoon proximity dissolve (PXD) conditions are not present (e.g., a dissolve due to a vehicle decelerating in front of a front vehicle, and other embodiments described in U.S. patent application Ser. No. 15/926,809, which is incorporated herein in its entirety for all purposes); a measured headway is at least the minimum platoon enable headway; ABS integrity for an entire vehicle configuration (e.g., tractor & trailers) is ensured; and/or two vehicle speeds are greater than or equal to 35 mph.
In addition, in some embodiments, a safety monitor software image may update/install only occur when a vehicle's key is not in its ignition (e.g., it is in an off mode). Further, in some embodiments, safety monitor software image checksums shall be validated prior to attempting image update/installs.
As described herein, dissolving and/or disabling platooning may be caused by: driver takeover actions including switching a disengage switch, depressing a brake pedal, depressing a throttle pedal; operational dissolve conditions including cut-ins, invalid NOC authorization, insufficient lead truck headway (e.g., PXD), when wipers are active for a period of time, and/or when stability control is inactive in either truck; and/or platoon disable faults including safety critical component faults, driver takeover mechanism faults, and/or a fault in unintended platooning safety mechanisms.
It is contemplated that multiple types of dissolves are possible, including a normal controller (e.g., PECU) dissolve, a safety monitor dissolve, a platoon dissolve backup, and a retarder dissolve.
In a normal controller dissolve the PECU causes a dissolve when a driver take-over action is indicated or any fault that does not trigger one of the other dissolves is present. A safety monitor dissolve may be executed by a PECU monitoring safety by indicating a fault. A platoon dissolve backup (PDB) may be a dissolve executed by the BECU when the PECU cannot or does not cause a dissolve. A retarder dissolve may be performed by the PECU when a BECU is missing from a J1939 CAN and Proprietary (e.g., ABS) CAN. A PECU may attempt to dissolve with the retarder while alerting the driver to take back control as quickly as possible by applying foundation brakes. In a case where both J1939 and Private/proprietary/ABS CANs are down but the BECU is healthy, a “brake now” alert may be issued.
In some embodiments, in response to a system determining that conditions are safe, a PECU may enable to driver to “takeover” complete longitudinal control of the system and no longer provide (at least some) automated commands. Until this point, in some embodiments, a system will honor manual inputs when they exceed the systems generated response, but continue to command external braking requests as necessary to react to a front vehicle or a cut-in. In some embodiments, there are three conditions the system will look for to determine whether it is safe to enable driver takeover based on whether an offset is detected while platooning and a headway is sufficient. Further, in some embodiments, when takeover is enabled, a system may look for driver indicators that they are back in the loop prior to giving up control, such as a brake pedal being depressed and/or a throttle pedal being depressed for two or more seconds.
As discussed herein, the stability health of a tractor-trailer may be required for platooning to occur. Confirmation of the stability health for the entire vehicle configuration (e.g., tractor+trailers) may detect how the number of trailers reporting healthy ABS units for comparison with a driver selected configuration by using the power-line communication (PLC) connector and standard. In some embodiments, a driver may select a configuration indicative of a number of ABS units the PLC should expect to get a healthy ABS indication from. A BECU may take the driver selected configuration reported by the PECU and compare it to the PLC count and confirm a match. A confirmation of ABS integrity is then reported back to the PECU, which indicates to the PECU that the ABS check that serves as a platoon enable condition. In some embodiments, after ABS health is confirmed and if an ABS unit indicates a faulted state while platooning a BECU may report the fault to the PECU and look for it to dissolve and perform a platoon dissolve backup if the PECU fails to do so in a timely manner.
In various embodiments, a driver or other user may select a type of trailer(s) that a tractor is towing. In various embodiments, a graphical user interface may display the type of trailer(s) that driver or other user selected. In various embodiments, a PECU may perform this operation to allow a driver to ensure they selected the correct type of trailer(s).
In some embodiments, a system may determine whether user (or another system) correctly chose the types of one or more trailers and/or the configuration of one or more trailers. In some embodiments, this may be performed by a second vehicle, a system at a weigh station, a system at a dock, a V-2-infrastructure system, etc. In various embodiments, an action may occur (e.g., a dissolve, the presentation of a notification/alert, a deauthorization from platooning, the prevention of authorizing a platoon, etc.) in response to a determination that the selected/assumed types of one or more trailers and/or the configuration of one or more trailers is incorrect.
In step 810, the method begins.
In step 820, a determination is made as to whether a vehicle is decelerating less than necessary. If a vehicle is decelerating less than necessary, a platoon may dissolve. If the vehicle is not decelerating less than necessary, the method may progress to step 830. A vehicle may be decelerating less than necessary if it is a rear vehicle and creates a gap between itself and a front vehicle that is less than a minimum/threshold gap.
In step 830, a determination is made as to whether a vehicle is accelerating unintendedly or excessively. If a vehicle is accelerating unintendedly or excessively, a platoon may dissolve. If the vehicle is not accelerating unintendedly or excessively, the method may progress to step 840. A vehicle may be accelerating unintendedly or excessively if it is a rear vehicle and creates a gap between itself and a front vehicle that is less than a minimum/threshold gap.
In step 840, a determination is made as to whether a vehicle is decelerating unintendedly or excessively. If a vehicle is decelerating unintendedly or excessively, a platoon may dissolve. If the vehicle is not decelerating unintendedly or excessively, the method may progress to step 850. A vehicle may be decelerating unintendedly or excessively if it is a rear vehicle and creates a gap between itself and a front vehicle that is greater than a desired/threshold amount.
In step 850, a determination is made as to whether a vehicle is platooning unintendedly. If a vehicle is platooning unintendedly, the platoon may dissolve. If the vehicle is not platooning unintendedly, the method may progress to step 860. A vehicle may be platooning unintendedly if it is not authorized to platoon, if it is platooning in an area it is not authorized to platoon in, if it is platooning on city streets, if it is platooning below a threshold speed (e.g., 30 miles/hour), if it is platooning above a threshold speed (e.g., 55 miles/hour, 60 miles/hour, 65 miles/hour, 70 miles/hour), and/or if it is platooning and either its PECU or BECU are unable to cause the vehicle's brakes to stop the vehicle.
In step 860, a determination is made as to whether a user is notified by a PECU. If the user is not notified by the PECU, a platoon may dissolve. If the user is notified by the PECU, the method may progress to step 870. A user may be notified by the PECU by receiving a notification at a graphical user interface, via an audio signal, and/or via a physical communication.
In step 870, a determination is made as to whether a vehicle is receiving inaccurate information from a NOC. If a vehicle is receiving inaccurate information from a NOC, a platoon may dissolve. If the vehicle is receiving accurate information from the NOC, the method may progress to step 880. A vehicle may be receiving inaccurate information from a NOC if a checksum is incorrect.
In step 880, a determination is made as to whether a vehicle is unstable. If a vehicle is unstable, it may dissolve. If the vehicle is not unstable, the method may progress to step 895. A vehicle may be unstable if one or more of its wheels, and/or one or more of the wheels on a trailer it is towing do not include brakes that utilize an automatic braking system.
In step 895, a platoon is dissolved. At least four types of dissolves are possible, as described above. These types of dissolves may include: a normal controller (e.g., PECU) dissolve, a safety monitor dissolve, a platoon dissolve backup, and a retarder dissolve.
In step 890, the method ends.
Throughout this application, it should be understood that the titles/headings of various sections are not meant to limit this application in any way. Similar or same aspects of a system may be discussed in multiple portions of this application, and it should be appreciated that one of skill in the art would understand that various portions of a system discussed in one or more portions of this application may be combined, ordered, reordered, added, removed, etc. In some embodiments, a portion of a system other than a PECU may be used to determine, monitor, and/or issue commands (e.g., one of the following components may be used instead of a PECU to cause actions: a backup PECU, a BECU, an EECU, a VECU, etc.)
Further, in some embodiments herein, even if an action such as dissolving a platoon in response to an event is described, the action dissolving may be exchanged with another action in this application. In other words, an event/attribute/condition described herein that causes an action—even if the action is “causes a platoon to dissolve”—may instead cause actions such as, but not limited to: deauthorize a vehicle from platooning, authorizing a vehicle to platoon, preventing a vehicle from being authorized to platoon/not authorizing a vehicle to platoon, disabling a vehicle from moving (e.g., under its own power), enabling a vehicle to move, causing a one or more vehicles in a platoon to change a gap, causing a platoon to form, causing a backup portion of a system (e.g., a backup module/component/mechanism) to activate and/or issue commands, activating an automatic emergency braking system (AEB), activating an anti-lock braking system (ABS), etc.
For example, an action may occur that causes to a vehicle and/or platoon (such as being deauthorized from platooning, being authorized to platoon, changing a gap, causing a vehicle to platoon, dissolving a platoon, etc.) when windshield wipers are activated. The same actions may occur if windshield wipers increase in speed, decrease in speed, a system detects rain, a system detects liquid and/or snow on a road, etc.
Further, in some embodiments described herein, the phrase “an action may occur” may be used interchangeably with the phrase “a system may cause an action to occur”.
In some embodiments, an action may occur in response to attributes of system software. For example, an action may occur if the a desired/expected version of software is not installed and/or detected by a system. A system may also cause an action to be performed, in some embodiments, if a configuration file is incorrect and/or corrupt, and/or if a vehicle is not configured correctly.
In some embodiments, a safety monitor may be updated (e.g., a safety monitor as described in PCT Application US2017/047825, filed on Aug. 21, 2017, hereby incorporated herein in its entirety for all purposes). In some embodiments a system may verify whether a safety monitor was updated correctly, and based on the outcome, perform an action may be performed.
In some embodiments, an action may occur when a BECU vehicle dynamics control (VDC) activate brake light request is not issued when PECU issues a break request.
In some embodiments, an action may occur based on the outcome of determining and/or verifying that lights (e.g., brake lights) are activated when a retarder command is issued and/or when a retarder is activated.
In some embodiments, an action may occur (e.g., a platoon may be prevented/dissolved/not authorized)) when a driver is too aggressive (or is assessed to be too aggressive by the system, cloud (e.g., NOC) or other means) or weather is affecting a road surface. Weather and/or road conditions may be monitored more frequently, and/or other actions may occur in response to attributes of the weather and/or road conditions. Driver aggressiveness may be assessed based on driver inputs such as steering (e.g., a steering rate above or below a threshold amount), accelerator pedal (e.g., an amount of pedal pressure and/or movement above and/or below a threshold amount), brake pedal (e.g., an amount of pedal pressure and/or movement above and/or below a threshold amount), or any combination thereof. In some embodiments, in addition to driver inputs, driver aggressiveness may be determined based at least in part on external conditions such as surrounding traffic, weather, or other conditions. For example, following closely, accelerating hard, steering hard, braking hard, braking hard with regard to road conditions, may each be an indicator of aggressiveness.
In some embodiments, an action may occur based on a attributes of a Push-To-Talk system (e.g., as described in U.S. Provisional Application No. 62/678,056, filed on May 30, 2018, hereby incorporated herein in its entirety for all purposes). For example, a Push-To-Talk System may be a system wherein voice communications are conducted over: (1) the same data link used to transfer control data for maintaining a platoon between two (or more) vehicles; (2) on one of two data links, wherein one of the two data links are used to transfer the control data; (3) on one of two data links, wherein one of the two data links are used to transfer the control data and the control data is transmitted over a first data link, and the voice communications are conducted over a second (e.g., different) data link. Data transmitted over a data link may be sent via a transceiver located at least partially: in a mirror, on a tractor, on the trailer, etc. In various embodiments, an action may occur based on a status of at least a portion of a Push-to-Talk system. For example, a platoon may dissolve if a Push-to-Talk system is not operating correctly (e.g., experiencing too much noise, being accessed by an unauthorized system, not having the correct software and/or configuration, not being updated, etc.) In some embodiments, a platoon may not be authorized to form, or dissolved in response to transmissions sent from at least one vehicle to another (e.g., a verbal test, voice transmitted from one vehicle to another, and/or vice-versa (e.g., a verbal acknowledgement/). For example, a driver may need to wait for a platooning partner's acknowledgement to dissolve and/or platoon before executing an action. These functionalities may apply to any voice link between the drivers, including those that are always active, full duplex, or have other attributes beyond push to talk.
In some embodiments, a system that may comprise at least one component that backs up various portions of the systems herein. In some embodiments, herein, the term “module” may be used interchangeably with the terms “component” and/or “mechanism.” These terms may refer to software and/or hardware that may be part of a larger platooning system, and may be within a PECU.
In one example, a system may include a module that causes a platoon to dissolve in response to another platoon dissolve module failing to operate correctly. For example, if a dissolve component of a system is producing a fault (e.g., transmitting data indicating an error), a system may cause a backup dissolve component to cause a dissolve. In some embodiments, a fault may be caused if a dissolve command expected to be issued by a dissolve module is not received by another portion of a system within a threshold amount of time. In such a case, a backup dissolve module may issue a dissolve command. In some embodiments, a dissolve may be caused by a BECU due to PECU's inability to cause a dissolve.
In various embodiments, there may be one, two, three, four, etc. backup modules (e.g., for any backup module described herein, including a backup dissolve module).
In some embodiments, an action may occur in response to attributes of a PECU Heartbeat. For example, a PECU Heartbeat may refer to the process where a PECU sends a status message at a specified regular interval. A watchdog (e.g., a BECU, an EECU) can then monitor the message and detect any faults that prevent PECU from issuing its heartbeat within a specified amount of time. A fault may be detected if a message contains certain information (e.g., indicating a fault) and/or if a message expected to arrive at a watchdog (or other component) does not arrive within a threshold amount of time. As described above, an action may include many things, including: causing a dissolve, deauthorizing platooning, causing a backup PECU to activate and/or issue commands, etc.
In some embodiments, an action may be caused based on attributes of a platoon dissolve backup system. For example, in response to a platoon dissolve backup system being activated, an alert may sound and/or a notification may be displayed (e.g., at a dashboard/infotainment system of a vehicle). Such alerts and/or notifications may indicate dissolve is occurring. In various embodiments, alerts and/or notifications may be caused to occur by the PECU, or another device. For example, a backup PECU, a BECU, and/or another module may cause alerts/notifications. These alerts and/or notifications may be caused by one or more portions of a system (e.g., a chip) that is relatively slow and reliable as opposed to other chips (e.g., that may process video) in a system.
In some embodiments, an action may occur in response to a system (which, herein, may refer to a PECU, BECU, EECU, a combination thereof, or other component) determining whether a request for braking is sufficient. In some embodiments, a maximum amount of braking (e.g., a braking threshold) may be based on a gap (e.g., the braking cannot exceed that threshold when far away from a target gap). In some embodiments, a PECU may determine a maximum amount of allowable acceleration, and based on the maximum amount of allowable acceleration, require that no (or a minimal amount (e.g., less than 5%, 10%, 20% of braking capability) be applied.
In some embodiments, an action may occur in response to a system determining the maximum amount of time that a request for braking is allowable. For example, a PECU (e.g., a monitor within a PECU) may check at least one brake request (e.g., from within a PECU and/or external to a PECU—as with all brake requests described herein) to determine whether the brake requests are above received when they are expected to be received and/or within a period of time (e.g., the expectation of receipt may be based on a sensor (e.g., radar, camera, LIDAR, sonar), a camera, information provided by a brake pedal, another controller, a wireless transmission, etc.).
In some embodiments, an action may occur in response to a system determining that a gap is being encroached (e.g., becoming too small). In some embodiments, an action may include activating an automatic emergency braking system to mitigate collision impact.
In some embodiments, an action may occur in response to a system determining that an error detection module is not determining that there is a fault. For example, a portion of a PECU may use a checksum to detect an error associated with incoming and/or outgoing messages over a wireless transmission (e.g., a checksum on DSRC messages).
In some embodiments, an action may occur in response to a system determining that a DSRC heartbeat is acting irregularly. In other words, if information associated with DSRC messages such as a time of arrival being incorrect, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action.
In some embodiments, an action may occur in response to a system determining that a front looking camera and/or radar and/or information created by fusing the outputs/inputs of the front looking camera and/or radar is incorrect. For example, if a camera is used to verify that data received from a radar is correct, a vehicle may be allowed to continue platooning.
In some embodiments, an action may occur in response to a system determining that a DSRC heartbeat is acting irregularly. In other words, if information associated with DSRC messages such as a time of arrival being incorrect, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action.
In some embodiments, an action may occur in response to a system determining that an NOC heartbeat is acting irregularly. In other words, if information associated with NOC messages such as a time of arrival being incorrect, messages authorizing platooning not being received for a threshold amount of time, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action.
In some embodiments, platooning may not be enabled unless certain conditions are met (e.g. absence of safety faults, one or more vehicles traveling above a speed threshold, NOC authorization being received, one/both/all drivers indicating it is safe to platoon (e.g., by providing input to the system such as pressing a button, turning a dial, and/or providing voice commands).
In some embodiments, an action may occur in response to a message counter being included in a message, or not included in one or more messages. For example, a platoon may continue, dissolve, and/or a vehicle may be authorized/deauthorized to platoon in response to a counter (e.g., that indicates an order of messages, or a number of messages sent and/or received) being included with a threshold amount (e.g., each) of messages, which may be messages from another vehicle, a vehicle included in a platoon, messages from a NOC, messages sent using DSRC, messages sent using cellular communications, messages requesting brakes to be applied, etc.
In some embodiments, an action may occur in response to ABS health being degraded or not operating correctly. For example, an action may occur in response to braking commands being saturated (which may also refer to the situation where a BECU is saturated with commands). In various embodiments, saturation may occur when more commands are issued to a braking system (or a portion thereof) than that braking system (or the portion thereof) can execute/handle. In various embodiments described herein, a BECU being saturated, a BECU being saturated with commands, braking commands being saturated, and/or a braking system being saturated may be used interchangeably/refer to the same situation.
In some embodiments, an action may occur in response to a system determining that a BECU heartbeat is acting irregularly. In other words, if information associated with NOC messages such as a time of arrival being incorrect, messages authorizing platooning not being received for a threshold amount of time, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action. In some embodiments, BECU messages which may be used/monitored to determine that a BECU is operating irregularly may be an EBC5 (status) message and/or an EBC1 (pedal position) message.
In some embodiments, an action may occur that includes using a retarder (e.g., as part of a backup safety system). For example, if a BECU indicates that there is a vault, a PECU may execute a dissolve using a retarder.
In some embodiments, a response to an action may include an alert indicating that a driver must takeover may be provided by a system. In various embodiments, errors mentioned above and below may cause an alert, even if a platoon does not dissolve.
In some embodiments, an action may occur in response to a system determining whether a checksum included with braking requests indicates that the messages may be used (e.g., are valid).
In some embodiments, an action may occur in response to a system determining that a gap and/or braking and/or throttle commands are sufficient to safely maintain a platoon gap. For example, attributes may be verified to determine whether commands are sufficient to safely maintain a platoon gap such as a whether late braking is occurring (e.g., braking occurring after a threshold amount of time), whether a gap's lower bound is exceeded (e.g., whether the gap threshold is too small), or whether an instantaneous brake check does not perform correctly.
In some embodiments, an action may occur in response to cancelling remote cruise control. For example, if a BECU detects that a PECU is faulting, it may cause a backup system (e.g., a BECU, which may include ACC/ABS functions) to dissolve a platoon and ignore requests from a PECU.
In some embodiments, an action may occur in response to a BECU detecting a PECU is faulting. For example, a BECU may cause itself, or another controller, to issue a command causing remote cruise control to be cancelled, and for a dissolve backup system to activate (e.g., wherein a EECU, BECU, VECU, etc. may cause a dissolve and/or ignore requests from a PECU).
In some embodiments, an action may occur in response to attributes of a pedal (e.g., a gas, brake, throttle, or go pedal (e.g., in electric vehicles). In some embodiments, pedal input may override a platooning system's commands. For example, a driver inputting information via a pedal may override commands from a PECU, BECU, and/or platooning system.
In some embodiments, a driver can trigger dissolves via one or more of the following methods: applying a brake pedal apply, applying a throttle pedal, and triggering the engage/disengage switch.
In some embodiments, how a vehicle performs as described herein may be at least a part of a driver training program/class/workshop, which may include video presentations.
In some embodiments, an action may occur at one vehicle in response to attributes of another vehicle. For example, attributes that cause actions to occur, as described herein, at one vehicle may cause one or more actions to occur at a second vehicle. For example, a system (e.g., a PECU) may determine that messages received from at least one other vehicle indicate the health and/or status of the at least one other vehicle. A system may monitor the status of a partner vehicle, and if a fault is present in a partner vehicle an action such as a dissolve may occur, and in some cases this dissolve may be communicated to at least the partner vehicle, a NOC, and/or a remote terminal operable to display the status of one or more vehicles that may be capable of platooning.
In some embodiments, an action may occur in response to a system determining that a driver input device (DID) heartbeat is acting irregularly. In other words, if information associated with messages from a DID such as a time of arrival being incorrect, messages authorizing platooning not being received for a threshold amount of time, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action. In some embodiments, DID messages which may be used/monitored to determine that a pedal, steering wheel, Push-to-Talk button, and/or activation switch, may be monitored, and an action may occur if they are acting irregularly.
In some embodiments, an action may occur in response to a system determining that a video transmission is not operating correctly. For example, a vehicle that sends and/or receives a video may determine (e.g., based on timestamps corresponding to video frames) that a video transmission is dropping frames, or other irregularities. An action may also occur is a system detects that images are frozen. Incorrect or otherwise irregular timestamps of video frames may also cause an action to occur.
In some embodiments, an action may occur in response to a system determining that a BECU's internal fault diagnostics detect faults affecting the execution of braking requests (e.g., when a tractor ABS indicates a fault).
In some embodiments, an action may occur in response to a system determining that one or more vehicles are traveling at a speed below a threshold speed. Further, a system by perform an action in response to a system determining that a vehicle is attempting to platoon in an unauthorized environment such an urban area.
In some embodiments, an action may occur in response to a system receiving information from a camera. Such information may include: the presence of traffic lights on a road a vehicle is traveling on; pedestrians/cyclists/animals on a road a vehicle is traveling on; construction; etc.
In some embodiments, an action may occur in response to a system determining that an air pressure in a braking system is below a threshold.
In some embodiments, an action may occur in response to a system determining that AEB or ABS is at least temporarily unavailable. Such an action may include using state/behavior data from a wireless transmission sent by another vehicle (e.g., information received via a wireless transmission from another vehicle may cause a vehicle to initiate AEB, ABS, or another system when that system would not otherwise operate correctly).
In some embodiments, an action may occur in response to a system determining that an ACC and/or platooning system is not correctly tracking an object, including whether tracking data is stuck, stale, or otherwise not reliable.
In some embodiments, an action may occur in response to a system determining that a component configured to provide brake requests heartbeat is acting irregularly. In other words, if information associated with messages (e.g., status messages) from a component that such as a time of arrival being incorrect, messages authorizing platooning not being received for a threshold amount of time, intervals at which messages should be received being incorrect, a determination that a transceiver of messages is not operating correctly, then a system may perform an action. In some embodiments, a BECU may monitor brake request message on a J1939 bus while platooning. If the BECU does not receive a brake request for a certain amount of cycles, it may cause an action such as a dissolve.
In some embodiments, an action may occur in response to a system determining that a foundation brake is overused, reaching a threshold temperature, and/or was overused.
In some embodiments, an action may occur in response to a system determining that a portion of a system that: determines a trailer size, determines a number of trailers, or receives input indicating a number of trailers (e.g., received from another portion of a system and/or from a driver) is operating incorrectly.
In some embodiments, an action may occur in response to a system determining that a pedal is not positioned in a plausible range (e.g., 0%-100% of possible ranges of a pedal). For example, if a system receives a signal indicating a pedal is depressed 110%, an action may occur.
In some embodiments, an action may occur in response to a system determining that a stability control system's heartbeat is acting irregularly. In other words, if information associated with messages (e.g., status messages) from a stability control module such as a time of arrival being incorrect, messages from a stability control module not being received within a threshold amount of time, intervals at which messages should be received being incorrect, a determination that a transceiver of messages associated with stability control is not operating correctly, then a system may perform an action. In some embodiments, any indication that a stability control module/unit/sub-system/system/mechanism is operating incorrectly may cause an action such as a dissolve.
In some embodiments, an action may occur in response to a system determining that a yaw and/or a yaw rate (e.g., a yaw/yaw rate of one or more trailers) is operating outside of a possible range. For example, is a system determines that an amount of yaw is at 110%, a system may perform an action such as disabling a vehicle from moving.
In some embodiments, an action may occur in response to a system determining that received data indicating a wheel speed is outside of a possible and/or allowable wheel-speed range. For example, a system may determine that data indicating wheel speeds, as received from various sources, are not possible/outside of a range, and an action may occur such as using other sensors to estimate speed (e.g., a GPS, an inertial measurement unit, a backup wheel speed sensor, communications with another vehicle, distance sensors, etc.) In some embodiments, an action may occur in response to a determination that a vehicle is traveling outside of a threshold and/or allowable speed based on information received from a sensor that can/assists with determining wheel speed.
In some embodiments, an action may occur in response to the version of software and/or firmware determined to be on (e.g., running on, stored on) one or more ECUs present on the vehicle(s). This may include the safety monitor, the platooning ECU, other automation ECUs, the brake ECU, the Engine ECU, a stability control ECU, trailer ECUs, or any other ECUs. For example, a system may determine whether one or more vehicles may platoon (e.g., with one another) based on a determination of the software included in a vehicle (e.g., version of software determined to be on an ECU). In some examples, a software image may be validated using a checksum before it is installed into a platooning system. A checksum may verify that an over-the-air (OTA) downloaded image and/or mounted image had not been modified. In some cases, if a determination is made that a downloaded image and/or mounted image has been modified, an action may occur such as deauthorizing a vehicle from being able to platoon.
In some embodiments, an action may occur in response to a system determining that no messages from a BECU are being transmitted over a bus and/or have not been transmitted over a bus for a threshold period of time. For example, a safety monitor (which, in some cases, may be part of a PECU) may check for loss of BECU messages on J1939 and/or private/ABS CAN against EECU, TECU, and/or the health of other ECUs and/or components. For example, in response to determining at least one device (e.g., an EECU) is transmitting messages over a network and a BECU is not, a system may determine that a BECU is not operating properly.
In some embodiments, an action may occur based on one or more attributes including, but not limited to: whether a throttle pedal is pressed (e.g., at all, or for more than a threshold amount of time, such as 2 seconds), a driver take-over action is performed (e.g., as described herein, such as braking, turning a wheel, pressing a pedal); an engage and/or disengage switch/button/input device is switched/pressed or otherwise activated whether a brake pedal is pressed (e.g., at all, or for more than a threshold amount of time, such as 2 seconds); when a cut-in occurs (e.g., a vehicle enters an area in between vehicles); when a NOC does not authorize a platoon; when a gap (including a distance and/or headway, as described herein) is insufficient; when an automatic braking system (ABS) is detected and/or operating correctly in one or more vehicles; whether windshield or other wipers are active for a threshold period of time; whether stability control is active in either truck; whether there is a safety critical component fault; whether there a driver takeover mechanism is operating correctly; whether a section of road is designated as being authorized or not-authorized to platoon on, whether a system that determines and/or corrects unintended platooning is operating correctly, etc.
In some embodiments, an action may occur to various fault types. Such fault types may include faults determined at least in part by timestamps (e.g., on video frames). For example, a fault may occur in response to a timestamp sent from a first vehicle and not reaching a second vehicle for an unacceptable period of time. Such a fault may occur when video and/or commands from one vehicle to another are not received at all. In some embodiments, faults may be determined when an amount of transmission latency (e.g., from another vehicle and/or NOC) is above a threshold.
In some embodiments, an action may occur in response to a trailer configuration being selected incorrectly. For example, in some embodiments a user may be asked to manually enter a trailer configuration using, for example, a GUI, knob, and/or button. In some embodiments a system may be able to determine a trailer configuration based on information received from a NOC, base station, loading dock, and/or portable electronic device (e.g., a trailer configuration may be determined based on a picture taken of a tractor and trailer(s) by a smart phone). In various embodiments, systems may verify whether the determined trailer configuration is correct (e.g., by receiving signals via a PLC such as ABS health, by a video, image, information received from another vehicle, portable electronic device, etc.). If a trailer configuration is not correct an action such as being deauthorized from platooning may occur.
In some systems, different types of dissolves may exist. As described herein, a dissolve is at least a portion of the process of ending a platoon (e.g., transmitting information between vehicles, notifying drivers, causing a gap to grow, etc.).
For example, in some systems at least four types of dissolves may exist: (1) a normal dissolve; (2) a safety monitor dissolve; (3) a platoon dissolve backup; and (4) a retarder dissolve.
In some embodiments, a normal dissolve process is executed at least in part by a PECU when systems are operating correctly and a platoon ends. For example, exiting a geofenced area, a driver take-over action, and/or a cut-in.
In some embodiments, a safety monitor dissolve may include a dissolve caused by a PECU (or other controller) in response to a fault. A safety monitor is described in PCT Application US2017/047825, filed on Aug. 21, 2017, which is incorporated herein in its entirety for all purposes. In some embodiments described herein, a safety monitor dissolve may occur in response to a detected fault (e.g., at a PECU, BECU, EECU, TECT, communication link, NOC, ABS, vehicle attribute (as described in the list of vehicle attributes above), etc.), an unresponsive controller (e.g., any electronic control unit (ECU)), the absence of a heartbeat of a component of a system, etc. The safety monitor dissolve may be commanded by the safety monitor, by sending commands to the brake ECU, Engine ECU, Vehicle ECU or other ECUs. In various embodiments, a safety monitor may be located within, or external to, a PECU, BECU, VECU, or other ECU. In various embodiments, a safety monitor may monitor data coming from one or more of a vehicle's ECUs, and/or issue commands to one or more ECUs and/or other components. In various embodiments, a safety monitor may be software, hardware, or a combination thereof. In some embodiments, a safety monitor dissolve may include a proximity dissolve, where a dissolve occurs in response to a vehicle other than the vehicles platooning coming too close, decelerating into, or otherwise coming close to causing a collision. In some embodiments, a proximity dissolve may include a situation where a lead vehicle is not safely following traffic in front of it. Proximity dissolves are described in U.S. patent application Ser. No. 15/926,809, filed on Mar. 20, 2018, which is hereby incorporated herein in its entirety for all purposes.
In some embodiments, a platoon dissolve backup may be executed by a controller (e.g., a BECU) in response to a safety monitor (which may be included in a PECU) indicating a fault, and/or when tractor ABS is faulting and causing a brake request interface to be unavailable. In some embodiments, if a PECU safety monitor has ended the PECU's heartbeat or fails to relay a braking command to a BECU while platooning, a BECU may use radar, camera, LIDAR, and/or other sensor data to determine and/or cause a dissolve. If a PECU and a forward looking radar, camera, LIDAR and/or other sensor data are faulting, a BECU may perform an open-loop braking profile based on a last known good brake request from a PECU.
In some embodiments, a retarder dissolve is executed at least in part by a retarder. A retarder dissolve may occur in response to a PECU determining that BECU messages and/or a BECU heartbeat is absent from one or more of a J1939 CAN and a Proprietary (e.g., ABS) CAN. In some embodiments, a PECU may attempt to dissolve with the retarder while alerting the driver to take back control as quickly as possible by applying foundation brakes. In some embodiments, if both J1939 and Private/ABS CANs are down but the BECU is healthy, a “brake now” alert will be issued when a BECU is executing a platoon dissolve backup.
Embodiments described herein may be discussed in the general context of computer-executable instructions residing on some form of computer-readable storage medium, such as program modules, executed by one or more computers or other devices. By way of example, and not limitation, computer-readable storage media may comprise non-transitory computer-readable storage media and communication media; non-transitory computer-readable media include all computer-readable media except for a transitory, propagating signal. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or distributed as desired in various embodiments.
This disclosure contains numerous references to a NOC, a PECU, a BECU, an EECU, a TECU, and one or more processors. According to various aspects, each of these items may include various kinds of memory, including non-volatile memory, to store one or more programs containing instructions for performing various aspects disclosed herein.
For example, as shown in
One or more elements of the aforementioned computing system 900 may be located at a remote location and connected to the other elements over a network 914. Further, embodiments of the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention may be located on a subset of nodes within the distributed system. In one embodiment of the invention, the node corresponds to a distinct computing device. Alternatively, the node may correspond to a computer processor with associated physical memory. The node may alternatively correspond to a computer processor or micro-core of a computer processor with shared memory and/or resources.
For example, one or more of the software modules disclosed herein may be implemented in a cloud computing environment. Cloud computing environments may provide various services and applications via the Internet (e.g., the NOC). These cloud-based services (e.g., software as a service, platform as a service, infrastructure as a service, etc.) may be accessible through a Web browser or other remote interface.
Communication media can embody computer-executable instructions, data structures, and program modules, and includes any information delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media. Combinations of any of the above can also be included within the scope of computer-readable media.
While the foregoing disclosure sets forth various embodiments using specific block diagrams, flowcharts, and examples, each block diagram component, flowchart step, operation, and/or component described and/or illustrated herein may be implemented, individually and/or collectively, using a wide range of hardware, software, or firmware (or any combination thereof) configurations. In addition, any disclosure of components contained within other components should be considered as examples because many other architectures can be implemented to achieve the same functionality.
The embodiments disclosed herein may also be implemented using software modules that perform certain tasks. These software modules may include script, batch, or other executable files that may be stored on a computer-readable storage medium or in a computing system. These software modules may configure a computing system to perform one or more of the example embodiments disclosed herein. One or more of the software modules disclosed herein may be implemented in a cloud computing environment.
While this disclosure has been described in terms of several aspects, there are alterations, modifications, permutations, and equivalents which fall within the scope of this disclosure. In view of the many alternative ways of implementing the methods and apparatuses of the present disclosure, it is intended that the following appended claims be interpreted to include all such alterations, modifications, permutations, and substitute equivalents as falling within the true scope of the present disclosure.
This application is a continuation-in-part of U.S. patent application Ser. No. 16/134,341, filed Oct. 23, 2018, entitled “SYSTEMS AND METHODS FOR PLATOONING AND AUTOMATION SAFETY”. This application claims priority to the aforementioned application (U.S. patent application Ser. No. 16/134,341), and incorporates it herein in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16134341 | Oct 2018 | US |
| Child | 16236153 | US |
