US20160207529A1 - Vehicle side impact control - Google Patents
Vehicle side impact control Download PDFInfo
- Publication number
- US20160207529A1 US20160207529A1 US14/600,086 US201514600086A US2016207529A1 US 20160207529 A1 US20160207529 A1 US 20160207529A1 US 201514600086 A US201514600086 A US 201514600086A US 2016207529 A1 US2016207529 A1 US 2016207529A1
- Authority
- US
- United States
- Prior art keywords
- host vehicle
- zone
- impact
- passenger
- vehicle
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012545 processing Methods 0.000 claims abstract description 41
- 238000000034 method Methods 0.000 claims description 31
- 238000001514 detection method Methods 0.000 claims description 9
- 230000001133 acceleration Effects 0.000 claims 3
- 230000008569 process Effects 0.000 description 20
- 230000015654 memory Effects 0.000 description 4
- 230000006378 damage Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 240000005020 Acaciella glauca Species 0.000 description 1
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 208000027418 Wounds and injury Diseases 0.000 description 1
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 235000003499 redwood Nutrition 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R21/013—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R21/015—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting the presence or position of passengers, passenger seats or child seats, and the related safety parameters therefor, e.g. speed or timing of airbag inflation in relation to occupant position or seat belt use
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R21/015—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting the presence or position of passengers, passenger seats or child seats, and the related safety parameters therefor, e.g. speed or timing of airbag inflation in relation to occupant position or seat belt use
- B60R21/01512—Passenger detection systems
- B60R21/01516—Passenger detection systems using force or pressure sensing means
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R21/015—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting the presence or position of passengers, passenger seats or child seats, and the related safety parameters therefor, e.g. speed or timing of airbag inflation in relation to occupant position or seat belt use
- B60R21/01554—Seat position sensors
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units, or advanced driver assistance systems for ensuring comfort, stability and safety or drive control systems for propelling or retarding the vehicle
- B60W30/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units, or advanced driver assistance systems for ensuring comfort, stability and safety or drive control systems for propelling or retarding the vehicle
- B60W30/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/085—Taking automatic action to adjust vehicle attitude in preparation for collision, e.g. braking for nose dropping
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units, or advanced driver assistance systems for ensuring comfort, stability and safety or drive control systems for propelling or retarding the vehicle
- B60W30/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/095—Predicting travel path or likelihood of collision
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/12—Limiting control by the driver depending on vehicle state, e.g. interlocking means for the control input for preventing unsafe operation
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R2021/0002—Type of accident
- B60R2021/0006—Lateral collision
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R2021/01013—Means for detecting collision, impending collision or roll-over
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
- B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
- B60R21/015—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting the presence or position of passengers, passenger seats or child seats, and the related safety parameters therefor, e.g. speed or timing of airbag inflation in relation to occupant position or seat belt use
- B60R21/01512—Passenger detection systems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W2554/00—Input parameters relating to objects
- B60W2554/80—Spatial relation or speed relative to objects
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W2720/00—Output or target parameters relating to overall vehicle dynamics
- B60W2720/10—Longitudinal speed
- B60W2720/106—Longitudinal acceleration
Definitions
- Vehicles include various restraint systems to reduce the risk of harm to occupants in the event of a collision.
- Examples of common restraint devices include seatbelts and airbags.
- seatbelts seek to hold passengers in their respective seats while airbags seek to cushion passengers from impacting certain parts of the vehicle interior.
- Vehicle body design can also help minimize injury by diverting impact forces away from passengers.
- FIG. 1 illustrates an example host vehicle that incorporates a side impact control system.
- FIG. 2 is a block diagram showing example components of the side impact control system that may be incorporated into the vehicle of FIG. 1 .
- FIGS. 3A and 3B illustrate example scenarios of how the side impact control system may change an impact zone.
- FIG. 4 is a flowchart of an example process that may be executed by the side impact control system.
- the host vehicle may incorporate a side impact control system that includes a sensor and a processing device.
- the sensor may detect an impact vehicle.
- the impact vehicle may include a vehicle that will imminently collide with the host vehicle.
- the processing device is programmed to predict an impact zone.
- the impact zone may be a location relative to the host vehicle where the impact vehicle is likely to collide with the host vehicle.
- the processing device may be further programmed to define a passenger zone relative to the host vehicle.
- the passenger zone may be based, at least in part, on where occupants are located in the passenger compartment of the host vehicle. For example, if the impact zone includes the driver's side of the host vehicle, the passenger zone may be limited to the area of the passenger compartment near the driver seat if no other passengers are present in the host vehicle. The passenger zone may be expanded to include the area of the passenger compartment near the driver seat and driver side rear seat if a passenger is present in the seat behind the driver seat.
- the side impact control system may generate a control signal that can divert the host vehicle to move the impact zone away from the passenger zone. Diverting the host vehicle may include accelerating or decelerating the host vehicle. While the side impact control system may not be able to cause the impact vehicle to completely avoid colliding with the host vehicle, the side impact control system may cause the impact to occur as far away from passengers of the host vehicle as possible.
- the elements shown may take many different forms and include multiple and/or alternate components and facilities.
- the example components illustrated are not intended to be limiting. Indeed, additional or alternative components and/or implementations may be used.
- the host vehicle 100 includes a side impact control system 105 that detects an imminent impact with another vehicle (referred to as the “impact vehicle”).
- the term “imminent” may include impacts predicted to occur within, e.g., a few seconds.
- the side impact control system 105 may predict an impact zone 110 (see FIGS. 3A-3B ) relative to the host vehicle 100 .
- the impact zone 110 may refer to the location where the impact with the impact vehicle is most likely to occur.
- the impact zone 110 may be predicted based on, e.g., the speeds and trajectories of the host vehicle 100 and the impact vehicle.
- the side impact control system 105 may further define a passenger zone 115 .
- the passenger zone 115 may include all or parts of the passenger compartment of the host vehicle 100 . Parts of the passenger compartment may include, e.g., a driver seat area 120 corresponding to a location of a driver seat in the host vehicle 100 , a passenger seat area 125 (see FIGS. 3A-3B ) corresponding to a location of a passenger seat in the host vehicle 100 , a first rear seat area 130 corresponding to a location of a first rear seat (e.g., behind the driver seat) in the host vehicle 100 , and a second rear seat area 135 (see FIGS.
- the passenger zone 115 may be defined to include any areas of the passenger compartment where an occupant is present. For instance, if the only occupant of the host vehicle 100 is sitting in the driver seat, the passenger zone 115 may be limited to the driver seat area 120 . If occupants are identified in both the driver and front passenger seats, the passenger zone 115 may include the driver seat area 120 and the passenger seat area 125 . If an occupant is identified in the rear seat behind the driver seat, the passenger zone 115 may include the first rear seat area 130 . If an occupant is identified in the rear seat behind the front passenger seat, the passenger zone 115 may include the second rear seat area 135 .
- the side impact control system 105 may generate a control signal that diverts the host vehicle 100 to move the impact zone 110 away from the passenger zone 115 . Diverting the host vehicle 100 may include accelerating or decelerating the host vehicle 100 . While the side impact control system 105 may not be able to cause the impact vehicle to completely avoid colliding with the host vehicle 100 , the side impact control system 105 may cause the impact to occur as far away from passengers of the host vehicle 100 as possible.
- the host vehicle 100 may include any passenger or commercial automobile such as a car, a truck, a sport utility vehicle, a crossover vehicle, a van, a minivan, a taxi, a bus, etc.
- the host vehicle 100 is an autonomous vehicle configured to operate in an autonomous (e.g., driverless) mode or a partially autonomous mode.
- the side impact control system 105 may include an impact sensor 140 , an occupant detection system 145 , and a processing device 150 .
- the impact sensor 140 may include an electronic device that can detect the impact vehicle relative to the host vehicle 100 . That is, the impact sensor 140 may be configured to detect an impact vehicle with a trajectory that is likely to collide with the host vehicle 100 . Examples of such sensors 140 may include a radar sensor, a lidar sensor, a vision sensor, or the like. The impact sensor 140 may be configured to output a signal representing the presence of the impact vehicle, the trajectory of the impact vehicle, or both.
- the occupant detection system 145 may include any number of devices configured to determine which seats of the host vehicle 100 are occupied.
- the occupant detection system 145 may include seat sensors, such as proximity sensors, associated with each seat in the passenger compartment. Each seat sensor may output a signal representing that an occupant has been detected. The absence of the signal may indicate that no occupant has been detected in the corresponding seat.
- the processing device 150 may receive and process the signals generated by the impact sensor 140 and the occupant detection system 145 .
- the processing device 150 may be programmed to predict the impact zone 110 , define the passenger zone 115 , and generate a control signal.
- the control signal may be used to move the host vehicle 100 so that the impact zone 110 is moved away from the passenger zone 115 since, as discussed above, the passenger zone 115 includes the locations of occupants within the host vehicle 100 .
- the control signal generated by the processing device 150 therefore, may cause the host vehicle 100 to accelerate or decelerate since doing so would change the impact zone 110 .
- another control signal may be generated to prepare or pre-charge certain passive safety systems such as airbags, belt tensioners, or the like.
- the processing device 150 may be programmed to evaluate certain powertrain and braking characteristics of the host vehicle 100 . That is, the processing device 150 may be programmed to determine whether the powertrain of the host vehicle 100 can accelerate the host vehicle 100 fast enough to move the impact zone 110 . Alternatively, the processing device 150 may be programmed to determine whether the braking system of the host vehicle 100 can decelerate the host vehicle 100 fast enough to move the impact zone 110 .
- the processing device 150 may be programmed to receive a driver input signal relating to the driver's intent for operating the host vehicle 100 .
- the driver input signal may be generated in response to, e.g., the driver of the host vehicle 100 pressing the accelerator pedal or the brake pedal, or the driver turning the steering wheel.
- the processing device 150 may be programmed to ignore or override certain driver input signals. For instance, the processing device 150 may ignore driver input signals that would keep the impact zone 110 within the passenger zone 115 or move the impact zone 110 to the passenger zone 115 .
- FIGS. 3A and 3B illustrate example scenarios of how the side impact control system 105 may move the impact zone 110 out of the passenger zone 115 .
- the host vehicle 100 has two passengers—one in the driver seat and one in the rear seat behind the driver seat.
- the passenger zone 115 may be defined as including the driver seat area 120 and the first rear seat area 130 .
- the impact zone 110 is initially predicted to occur near both the driver seat area 120 and the first rear seat area 130 .
- the side impact control system 105 may further predict where the impact zone 110 will be if the host vehicle 100 were to accelerate or brake. In the example of FIG. 3A , accelerating will place the impact zone 110 close to the rear passenger.
- the side impact control system 105 may control the host vehicle 100 to brake so that the impact may occur away from the passenger zone 115 .
- both braking and accelerating will move the impact zone 110 away from the passenger zone 115 . Accelerating, however, will move the impact zone 110 further from the only passenger. Therefore, the side impact control system 105 may control the host vehicle 100 to accelerate.
- FIG. 4 is a process flow diagram of an example process 400 that may be implemented by the side impact control system 105 .
- the process 400 may begin when the host vehicle 100 is turned on and continue to run until the host vehicle 100 is turned off.
- the processing device 150 may define a passenger zone 115 .
- the passenger zone 115 may be based on the location of occupants in the passenger compartment of the host vehicle 100 . The locations of passengers may be determined from the signals output by the occupant detection system 145 . As discussed above, the passenger zone 115 may include all or parts of the passenger compartment of the host vehicle 100 . Parts of the passenger compartment may include the driver seat area 120 the passenger seat area 125 the first rear seat area 130 and the second rear seat area 135 . If the only occupant of the host vehicle 100 is sitting in the driver seat, the passenger zone 115 may be limited to the driver seat area 120 .
- the passenger zone 115 may include the driver seat area 120 and the passenger seat area 125 . If an occupant is identified in the rear seat behind the driver seat, the passenger zone 115 may include the first rear seat area 130 . If an occupant is identified in the rear seat behind the front passenger seat, the passenger zone 115 may include the second rear seat area 135 .
- the processing device 150 may detect the impact vehicle.
- the impact vehicle may be detected from the impact signal output by the impact sensor 140 , such as a radar sensor, a lidar sensor, a vision sensor, or the like.
- the impact signal may represent the presence of the impact vehicle, the trajectory of the impact vehicle, or both.
- the processing device 150 may determine the impact zone 110 relative to the host vehicle 100 .
- the impact zone 110 may be determined from the speed of the host vehicle 100 , and the speed and trajectory of the impact vehicle relative to the host vehicle 100 .
- the processing device 150 may compare the impact zone 110 to the passenger zone 115 . If the impact zone 110 is predicted to occur within the passenger zone 115 , the process 400 may continue at block 425 . Otherwise, the process 400 may proceed at block 435 .
- the processing device 150 may select a countermeasure. Examples of countermeasures may include accelerating or decelerating the host vehicle 100 .
- the processing device 150 may determine whether accelerating or decelerating the host vehicle 100 will cause the impact zone 110 to move away from the passenger zone 115 .
- the processing device 150 may consider powertrain characteristics—e.g., how quickly the host vehicle 100 can accelerate—and braking characteristics—e.g., how quickly the host vehicle 100 can decelerate—in selecting the countermeasure. If both countermeasures are sufficient to move the impact zone 110 away from the passenger zone 115 , or if moving the impact zone 110 out of the passenger zone 115 is impossible, the processing device 150 may select the countermeasure that places the impact zone 110 as far from the occupants as possible.
- the processing device 150 may generate a control signal.
- the control signal may be output to a vehicle control system that can cause the host vehicle 100 to implement the countermeasure. That is, the control signal may maneuver the host vehicle 100 in a way that moves the impact zone 110 away from the passenger zone 115 as much as possible. Thus, the control signal may cause the host vehicle 100 to accelerate or decelerate, among other countermeasures.
- the processing device 150 may determine whether a driver input signal has been received.
- the driver input signal may be generated by a driver input device such as the accelerator pedal, brake pedal, or steering wheel. If received, the process 400 may proceed to block 440 . Otherwise, the process 400 may continue to execute block 435 until a driver input signal is received.
- the processing device 150 may determine whether the driver input signal will cause the impact zone 110 to move to, or stay within, the passenger zone 115 . If the driver input signal will maneuver the host vehicle 100 in a manner contrary to the selected countermeasure or will cause the impact zone 110 to enter into the passenger zone 115 , the process 400 may continue at block 445 . Otherwise, the process 400 may continue at block 450 .
- the processing device 150 may override the driver input signal. For instance, the processing device 150 may prevent the host vehicle 100 to responding in accordance with the driver input signal. Therefore, if the driver input signal would have the host vehicle 100 accelerate, but accelerating will move the impact zone 110 to within the passenger zone 115 , the processing device 150 may override the driver input signal to prevent the host vehicle 100 from accelerating. Alternatively, if the driver input signal would have the host vehicle 100 decelerate, but decelerating will move the impact zone 110 to within the passenger zone 115 , the processing device 150 may override the driver input signal to prevent the host vehicle 100 from decelerating.
- the processing device 150 may generate a control signal to operate the host vehicle 100 in accordance with the driver input signal.
- the process 400 may end after blocks 445 or 450 . If the collision with the impact vehicle is avoided, however, the process 400 may return to block 410 and so that the process 400 may continue to execute until the host vehicle 100 is turned off.
- the computing systems and/or devices described may employ any of a number of computer operating systems, including, but by no means limited to, versions and/or varieties of the Ford Sync® operating system, the Microsoft Windows® operating system, the Unix operating system (e.g., the Solaris® operating system distributed by Oracle Corporation of Redwood Shores, California), the AIX UNIX operating system distributed by International Business Machines of Armonk, N.Y., the Linux operating system, the Mac OSX and iOS operating systems distributed by Apple Inc. of Cupertino, Calif., the BlackBerry OS distributed by Blackberry, Ltd. of Waterloo, Canada, and the Android operating system developed by Google, Inc. and the Open Handset Alliance.
- Examples of computing devices include, without limitation, an on-board vehicle computer, a computer workstation, a server, a desktop, notebook, laptop, or handheld computer, or some other computing system and/or device.
- Computing devices generally include computer-executable instructions, where the instructions may be executable by one or more computing devices such as those listed above.
- Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, JavaTM, C, C++, Visual Basic, Java Script, Perl, etc.
- a processor e.g., a microprocessor
- receives instructions e.g., from a memory, a computer-readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein.
- Such instructions and other data may be stored and transmitted using a variety of computer-readable media.
- a computer-readable medium includes any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by a processor of a computer).
- a medium may take many forms, including, but not limited to, non-volatile media and volatile media.
- Non-volatile media may include, for example, optical or magnetic disks and other persistent memory.
- Volatile media may include, for example, dynamic random access memory (DRAM), which typically constitutes a main memory.
- Such instructions may be transmitted by one or more transmission media, including coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to a processor of a computer.
- Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.
- Databases, data repositories or other data stores described herein may include various kinds of mechanisms for storing, accessing, and retrieving various kinds of data, including a hierarchical database, a set of files in a file system, an application database in a proprietary format, a relational database management system (RDBMS), etc.
- Each such data store is generally included within a computing device employing a computer operating system such as one of those mentioned above, and are accessed via a network in any one or more of a variety of manners.
- a file system may be accessible from a computer operating system, and may include files stored in various formats.
- An RDBMS generally employs the Structured Query Language (SQL) in addition to a language for creating, storing, editing, and executing stored procedures, such as the PL/SQL language mentioned above.
- SQL Structured Query Language
- system elements may be implemented as computer-readable instructions (e.g., software) on one or more computing devices (e.g., servers, personal computers, etc.), stored on computer readable media associated therewith (e.g., disks, memories, etc.).
- a computer program product may comprise such instructions stored on computer readable media for carrying out the functions described herein.
Abstract
Description
- Vehicles include various restraint systems to reduce the risk of harm to occupants in the event of a collision. Examples of common restraint devices include seatbelts and airbags. During a collision, seatbelts seek to hold passengers in their respective seats while airbags seek to cushion passengers from impacting certain parts of the vehicle interior. Vehicle body design can also help minimize injury by diverting impact forces away from passengers.
-
FIG. 1 illustrates an example host vehicle that incorporates a side impact control system. -
FIG. 2 is a block diagram showing example components of the side impact control system that may be incorporated into the vehicle ofFIG. 1 . -
FIGS. 3A and 3B illustrate example scenarios of how the side impact control system may change an impact zone. -
FIG. 4 is a flowchart of an example process that may be executed by the side impact control system. - If an impact cannot be avoided, one way to reduce the risk of harm to occupants in the host vehicle is to divert the host vehicle so that the impact occurs at a location as far from the passenger compartment as possible. In the context of an unavoidable side impact, the host vehicle may incorporate a side impact control system that includes a sensor and a processing device. The sensor may detect an impact vehicle. The impact vehicle may include a vehicle that will imminently collide with the host vehicle. The processing device is programmed to predict an impact zone. The impact zone may be a location relative to the host vehicle where the impact vehicle is likely to collide with the host vehicle. The processing device may be further programmed to define a passenger zone relative to the host vehicle. The passenger zone may be based, at least in part, on where occupants are located in the passenger compartment of the host vehicle. For example, if the impact zone includes the driver's side of the host vehicle, the passenger zone may be limited to the area of the passenger compartment near the driver seat if no other passengers are present in the host vehicle. The passenger zone may be expanded to include the area of the passenger compartment near the driver seat and driver side rear seat if a passenger is present in the seat behind the driver seat. When the passenger zone has been defined, the side impact control system may generate a control signal that can divert the host vehicle to move the impact zone away from the passenger zone. Diverting the host vehicle may include accelerating or decelerating the host vehicle. While the side impact control system may not be able to cause the impact vehicle to completely avoid colliding with the host vehicle, the side impact control system may cause the impact to occur as far away from passengers of the host vehicle as possible.
- The elements shown may take many different forms and include multiple and/or alternate components and facilities. The example components illustrated are not intended to be limiting. Indeed, additional or alternative components and/or implementations may be used.
- As illustrated in
FIG. 1 , thehost vehicle 100 includes a sideimpact control system 105 that detects an imminent impact with another vehicle (referred to as the “impact vehicle”). The term “imminent” may include impacts predicted to occur within, e.g., a few seconds. The sideimpact control system 105 may predict an impact zone 110 (seeFIGS. 3A-3B ) relative to thehost vehicle 100. Theimpact zone 110 may refer to the location where the impact with the impact vehicle is most likely to occur. Theimpact zone 110 may be predicted based on, e.g., the speeds and trajectories of thehost vehicle 100 and the impact vehicle. - The side
impact control system 105 may further define apassenger zone 115. Thepassenger zone 115 may include all or parts of the passenger compartment of thehost vehicle 100. Parts of the passenger compartment may include, e.g., adriver seat area 120 corresponding to a location of a driver seat in thehost vehicle 100, a passenger seat area 125 (seeFIGS. 3A-3B ) corresponding to a location of a passenger seat in thehost vehicle 100, a firstrear seat area 130 corresponding to a location of a first rear seat (e.g., behind the driver seat) in thehost vehicle 100, and a second rear seat area 135 (seeFIGS. 3A-3B ) corresponding to a location of a second rear seat (e.g., behind the front passenger seat) in thehost vehicle 100. Thepassenger zone 115 may be defined to include any areas of the passenger compartment where an occupant is present. For instance, if the only occupant of thehost vehicle 100 is sitting in the driver seat, thepassenger zone 115 may be limited to thedriver seat area 120. If occupants are identified in both the driver and front passenger seats, thepassenger zone 115 may include thedriver seat area 120 and thepassenger seat area 125. If an occupant is identified in the rear seat behind the driver seat, thepassenger zone 115 may include the firstrear seat area 130. If an occupant is identified in the rear seat behind the front passenger seat, thepassenger zone 115 may include the secondrear seat area 135. - With the
passenger zone 115 defined, the sideimpact control system 105 may generate a control signal that diverts thehost vehicle 100 to move theimpact zone 110 away from thepassenger zone 115. Diverting thehost vehicle 100 may include accelerating or decelerating thehost vehicle 100. While the sideimpact control system 105 may not be able to cause the impact vehicle to completely avoid colliding with thehost vehicle 100, the sideimpact control system 105 may cause the impact to occur as far away from passengers of thehost vehicle 100 as possible. - The
host vehicle 100 may include any passenger or commercial automobile such as a car, a truck, a sport utility vehicle, a crossover vehicle, a van, a minivan, a taxi, a bus, etc. In some possible approaches, thehost vehicle 100 is an autonomous vehicle configured to operate in an autonomous (e.g., driverless) mode or a partially autonomous mode. - Referring now to
FIG. 2 , the sideimpact control system 105 may include animpact sensor 140, anoccupant detection system 145, and aprocessing device 150. - The
impact sensor 140 may include an electronic device that can detect the impact vehicle relative to thehost vehicle 100. That is, theimpact sensor 140 may be configured to detect an impact vehicle with a trajectory that is likely to collide with thehost vehicle 100. Examples ofsuch sensors 140 may include a radar sensor, a lidar sensor, a vision sensor, or the like. Theimpact sensor 140 may be configured to output a signal representing the presence of the impact vehicle, the trajectory of the impact vehicle, or both. - The
occupant detection system 145 may include any number of devices configured to determine which seats of thehost vehicle 100 are occupied. Theoccupant detection system 145, therefore, may include seat sensors, such as proximity sensors, associated with each seat in the passenger compartment. Each seat sensor may output a signal representing that an occupant has been detected. The absence of the signal may indicate that no occupant has been detected in the corresponding seat. - The
processing device 150 may receive and process the signals generated by theimpact sensor 140 and theoccupant detection system 145. Thus, theprocessing device 150 may be programmed to predict theimpact zone 110, define thepassenger zone 115, and generate a control signal. The control signal may be used to move thehost vehicle 100 so that theimpact zone 110 is moved away from thepassenger zone 115 since, as discussed above, thepassenger zone 115 includes the locations of occupants within thehost vehicle 100. The control signal generated by theprocessing device 150, therefore, may cause thehost vehicle 100 to accelerate or decelerate since doing so would change theimpact zone 110. In some possible implementations, such as when a collision in thepassenger zone 115 is imminent and unavoidable, another control signal may be generated to prepare or pre-charge certain passive safety systems such as airbags, belt tensioners, or the like. - In determining whether to accelerate or decelerate the
host vehicle 100, theprocessing device 150 may be programmed to evaluate certain powertrain and braking characteristics of thehost vehicle 100. That is, theprocessing device 150 may be programmed to determine whether the powertrain of thehost vehicle 100 can accelerate thehost vehicle 100 fast enough to move theimpact zone 110. Alternatively, theprocessing device 150 may be programmed to determine whether the braking system of thehost vehicle 100 can decelerate thehost vehicle 100 fast enough to move theimpact zone 110. - In some implementations, the
processing device 150 may be programmed to receive a driver input signal relating to the driver's intent for operating thehost vehicle 100. The driver input signal may be generated in response to, e.g., the driver of thehost vehicle 100 pressing the accelerator pedal or the brake pedal, or the driver turning the steering wheel. When an impact is imminent, theprocessing device 150 may be programmed to ignore or override certain driver input signals. For instance, theprocessing device 150 may ignore driver input signals that would keep theimpact zone 110 within thepassenger zone 115 or move theimpact zone 110 to thepassenger zone 115. -
FIGS. 3A and 3B illustrate example scenarios of how the sideimpact control system 105 may move theimpact zone 110 out of thepassenger zone 115. As shown inFIG. 3A , thehost vehicle 100 has two passengers—one in the driver seat and one in the rear seat behind the driver seat. Accordingly, thepassenger zone 115 may be defined as including thedriver seat area 120 and the firstrear seat area 130. Theimpact zone 110 is initially predicted to occur near both thedriver seat area 120 and the firstrear seat area 130. The sideimpact control system 105 may further predict where theimpact zone 110 will be if thehost vehicle 100 were to accelerate or brake. In the example ofFIG. 3A , accelerating will place theimpact zone 110 close to the rear passenger. In other words, accelerating will not move theimpact zone 110 away from thepassenger zone 115. Rather, accelerating would move theimpact zone 110 toward one of the passengers. Braking, however, will place theimpact zone 110 in front of thepassenger zone 115. Therefore, between accelerating and braking, the sideimpact control system 105 may control thehost vehicle 100 to brake so that the impact may occur away from thepassenger zone 115. Turning now to the example ofFIG. 3B , where no rear passenger is present, both braking and accelerating will move theimpact zone 110 away from thepassenger zone 115. Accelerating, however, will move theimpact zone 110 further from the only passenger. Therefore, the sideimpact control system 105 may control thehost vehicle 100 to accelerate. -
FIG. 4 is a process flow diagram of anexample process 400 that may be implemented by the sideimpact control system 105. Theprocess 400 may begin when thehost vehicle 100 is turned on and continue to run until thehost vehicle 100 is turned off. - At
block 405, theprocessing device 150 may define apassenger zone 115. Thepassenger zone 115 may be based on the location of occupants in the passenger compartment of thehost vehicle 100. The locations of passengers may be determined from the signals output by theoccupant detection system 145. As discussed above, thepassenger zone 115 may include all or parts of the passenger compartment of thehost vehicle 100. Parts of the passenger compartment may include thedriver seat area 120 thepassenger seat area 125 the firstrear seat area 130 and the secondrear seat area 135. If the only occupant of thehost vehicle 100 is sitting in the driver seat, thepassenger zone 115 may be limited to thedriver seat area 120. If occupants are identified in both the driver and front passenger seats, thepassenger zone 115 may include thedriver seat area 120 and thepassenger seat area 125. If an occupant is identified in the rear seat behind the driver seat, thepassenger zone 115 may include the firstrear seat area 130. If an occupant is identified in the rear seat behind the front passenger seat, thepassenger zone 115 may include the secondrear seat area 135. - At
block 410, theprocessing device 150 may detect the impact vehicle. The impact vehicle may be detected from the impact signal output by theimpact sensor 140, such as a radar sensor, a lidar sensor, a vision sensor, or the like. The impact signal may represent the presence of the impact vehicle, the trajectory of the impact vehicle, or both. - At
block 415, theprocessing device 150 may determine theimpact zone 110 relative to thehost vehicle 100. Theimpact zone 110 may be determined from the speed of thehost vehicle 100, and the speed and trajectory of the impact vehicle relative to thehost vehicle 100. - At
decision block 420, theprocessing device 150 may compare theimpact zone 110 to thepassenger zone 115. If theimpact zone 110 is predicted to occur within thepassenger zone 115, theprocess 400 may continue atblock 425. Otherwise, theprocess 400 may proceed atblock 435. - At
block 425, theprocessing device 150 may select a countermeasure. Examples of countermeasures may include accelerating or decelerating thehost vehicle 100. Theprocessing device 150 may determine whether accelerating or decelerating thehost vehicle 100 will cause theimpact zone 110 to move away from thepassenger zone 115. Theprocessing device 150 may consider powertrain characteristics—e.g., how quickly thehost vehicle 100 can accelerate—and braking characteristics—e.g., how quickly thehost vehicle 100 can decelerate—in selecting the countermeasure. If both countermeasures are sufficient to move theimpact zone 110 away from thepassenger zone 115, or if moving theimpact zone 110 out of thepassenger zone 115 is impossible, theprocessing device 150 may select the countermeasure that places theimpact zone 110 as far from the occupants as possible. - At
block 430, theprocessing device 150 may generate a control signal. The control signal may be output to a vehicle control system that can cause thehost vehicle 100 to implement the countermeasure. That is, the control signal may maneuver thehost vehicle 100 in a way that moves theimpact zone 110 away from thepassenger zone 115 as much as possible. Thus, the control signal may cause thehost vehicle 100 to accelerate or decelerate, among other countermeasures. - At
decision block 435, theprocessing device 150 may determine whether a driver input signal has been received. The driver input signal may be generated by a driver input device such as the accelerator pedal, brake pedal, or steering wheel. If received, theprocess 400 may proceed to block 440. Otherwise, theprocess 400 may continue to execute block 435 until a driver input signal is received. - At
decision block 440, theprocessing device 150 may determine whether the driver input signal will cause theimpact zone 110 to move to, or stay within, thepassenger zone 115. If the driver input signal will maneuver thehost vehicle 100 in a manner contrary to the selected countermeasure or will cause theimpact zone 110 to enter into thepassenger zone 115, theprocess 400 may continue atblock 445. Otherwise, theprocess 400 may continue atblock 450. - At
block 445, theprocessing device 150 may override the driver input signal. For instance, theprocessing device 150 may prevent thehost vehicle 100 to responding in accordance with the driver input signal. Therefore, if the driver input signal would have thehost vehicle 100 accelerate, but accelerating will move theimpact zone 110 to within thepassenger zone 115, theprocessing device 150 may override the driver input signal to prevent thehost vehicle 100 from accelerating. Alternatively, if the driver input signal would have thehost vehicle 100 decelerate, but decelerating will move theimpact zone 110 to within thepassenger zone 115, theprocessing device 150 may override the driver input signal to prevent thehost vehicle 100 from decelerating. - At
block 450, theprocessing device 150 may generate a control signal to operate thehost vehicle 100 in accordance with the driver input signal. - The
process 400 may end afterblocks process 400 may return to block 410 and so that theprocess 400 may continue to execute until thehost vehicle 100 is turned off. - In general, the computing systems and/or devices described may employ any of a number of computer operating systems, including, but by no means limited to, versions and/or varieties of the Ford Sync® operating system, the Microsoft Windows® operating system, the Unix operating system (e.g., the Solaris® operating system distributed by Oracle Corporation of Redwood Shores, California), the AIX UNIX operating system distributed by International Business Machines of Armonk, N.Y., the Linux operating system, the Mac OSX and iOS operating systems distributed by Apple Inc. of Cupertino, Calif., the BlackBerry OS distributed by Blackberry, Ltd. of Waterloo, Canada, and the Android operating system developed by Google, Inc. and the Open Handset Alliance. Examples of computing devices include, without limitation, an on-board vehicle computer, a computer workstation, a server, a desktop, notebook, laptop, or handheld computer, or some other computing system and/or device.
- Computing devices generally include computer-executable instructions, where the instructions may be executable by one or more computing devices such as those listed above. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, Java™, C, C++, Visual Basic, Java Script, Perl, etc. In general, a processor (e.g., a microprocessor) receives instructions, e.g., from a memory, a computer-readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions and other data may be stored and transmitted using a variety of computer-readable media.
- A computer-readable medium (also referred to as a processor-readable medium) includes any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by a processor of a computer). Such a medium may take many forms, including, but not limited to, non-volatile media and volatile media. Non-volatile media may include, for example, optical or magnetic disks and other persistent memory. Volatile media may include, for example, dynamic random access memory (DRAM), which typically constitutes a main memory. Such instructions may be transmitted by one or more transmission media, including coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to a processor of a computer. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.
- Databases, data repositories or other data stores described herein may include various kinds of mechanisms for storing, accessing, and retrieving various kinds of data, including a hierarchical database, a set of files in a file system, an application database in a proprietary format, a relational database management system (RDBMS), etc. Each such data store is generally included within a computing device employing a computer operating system such as one of those mentioned above, and are accessed via a network in any one or more of a variety of manners. A file system may be accessible from a computer operating system, and may include files stored in various formats. An RDBMS generally employs the Structured Query Language (SQL) in addition to a language for creating, storing, editing, and executing stored procedures, such as the PL/SQL language mentioned above.
- In some examples, system elements may be implemented as computer-readable instructions (e.g., software) on one or more computing devices (e.g., servers, personal computers, etc.), stored on computer readable media associated therewith (e.g., disks, memories, etc.). A computer program product may comprise such instructions stored on computer readable media for carrying out the functions described herein.
- With regard to the processes, systems, methods, heuristics, etc. described herein, it should be understood that, although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating certain embodiments, and should in no way be construed so as to limit the claims.
- Accordingly, it is to be understood that the above description is intended to be illustrative and not restrictive. Many embodiments and applications other than the examples provided would be apparent upon reading the above description. The scope should be determined, not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the technologies discussed herein, and that the disclosed systems and methods will be incorporated into such future embodiments. In sum, it should be understood that the application is capable of modification and variation.
- All terms used in the claims are intended to be given their ordinary meanings as understood by those knowledgeable in the technologies described herein unless an explicit indication to the contrary is made herein. In particular, use of the singular articles such as “a,” “the,” “said,” etc. should be read to recite one or more of the indicated elements unless a claim recites an explicit limitation to the contrary.
- The Abstract is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
Claims (20)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/600,086 US9381915B1 (en) | 2015-01-20 | 2015-01-20 | Vehicle side impact control |
RU2015154607A RU2015154607A (en) | 2015-01-20 | 2015-12-18 | VEHICLE PREVENTION |
DE102016100398.0A DE102016100398A1 (en) | 2015-01-20 | 2016-01-12 | VEHICLE SIDE IMPACT CONTROL |
CN201610021320.4A CN105818770B (en) | 2015-01-20 | 2016-01-13 | Vehicle side impact control |
MX2016000755A MX355868B (en) | 2015-01-20 | 2016-01-19 | Vehicle side impact control. |
GB1601030.8A GB2536116A (en) | 2015-01-20 | 2016-01-20 | Vehicle side impact control |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/600,086 US9381915B1 (en) | 2015-01-20 | 2015-01-20 | Vehicle side impact control |
Publications (2)
Publication Number | Publication Date |
---|---|
US9381915B1 US9381915B1 (en) | 2016-07-05 |
US20160207529A1 true US20160207529A1 (en) | 2016-07-21 |
Family
ID=55488216
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/600,086 Active US9381915B1 (en) | 2015-01-20 | 2015-01-20 | Vehicle side impact control |
Country Status (6)
Country | Link |
---|---|
US (1) | US9381915B1 (en) |
CN (1) | CN105818770B (en) |
DE (1) | DE102016100398A1 (en) |
GB (1) | GB2536116A (en) |
MX (1) | MX355868B (en) |
RU (1) | RU2015154607A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11110916B2 (en) | 2016-09-13 | 2021-09-07 | Mando Corporation | Impact-absorbing apparatus and method for vehicle |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9869560B2 (en) | 2015-07-31 | 2018-01-16 | International Business Machines Corporation | Self-driving vehicle's response to a proximate emergency vehicle |
US9896100B2 (en) | 2015-08-24 | 2018-02-20 | International Business Machines Corporation | Automated spatial separation of self-driving vehicles from other vehicles based on occupant preferences |
US9566986B1 (en) | 2015-09-25 | 2017-02-14 | International Business Machines Corporation | Controlling driving modes of self-driving vehicles |
US9944291B2 (en) | 2015-10-27 | 2018-04-17 | International Business Machines Corporation | Controlling driving modes of self-driving vehicles |
US10607293B2 (en) | 2015-10-30 | 2020-03-31 | International Business Machines Corporation | Automated insurance toggling for self-driving vehicles |
US10176525B2 (en) | 2015-11-09 | 2019-01-08 | International Business Machines Corporation | Dynamically adjusting insurance policy parameters for a self-driving vehicle |
US10685391B2 (en) | 2016-05-24 | 2020-06-16 | International Business Machines Corporation | Directing movement of a self-driving vehicle based on sales activity |
US10093322B2 (en) | 2016-09-15 | 2018-10-09 | International Business Machines Corporation | Automatically providing explanations for actions taken by a self-driving vehicle |
US10643256B2 (en) | 2016-09-16 | 2020-05-05 | International Business Machines Corporation | Configuring a self-driving vehicle for charitable donations pickup and delivery |
KR101891612B1 (en) * | 2016-09-30 | 2018-08-24 | 엘지전자 주식회사 | Autonomous vehicle |
US10129643B2 (en) * | 2016-11-03 | 2018-11-13 | Ford Global Technologies, Llc | Autonomous vehicle ingress and egress |
US10259452B2 (en) * | 2017-01-04 | 2019-04-16 | International Business Machines Corporation | Self-driving vehicle collision management system |
US10363893B2 (en) | 2017-01-05 | 2019-07-30 | International Business Machines Corporation | Self-driving vehicle contextual lock control system |
US10529147B2 (en) | 2017-01-05 | 2020-01-07 | International Business Machines Corporation | Self-driving vehicle road safety flare deploying system |
US11292460B2 (en) * | 2017-01-19 | 2022-04-05 | Honda Motor Co., Ltd. | Vehicle control system, vehicle control method, and vehicle control program |
DE102017201936A1 (en) * | 2017-02-08 | 2018-08-09 | Robert Bosch Gmbh | Method for reducing collision damage |
CN110723139A (en) * | 2019-11-15 | 2020-01-24 | 联想(北京)有限公司 | Vehicle control method, electronic equipment and vehicle |
CN111619557B (en) * | 2020-04-10 | 2023-06-09 | 浙江吉利汽车研究院有限公司 | Dangerous road section vehicle control method and device, electronic equipment and storage medium |
KR20210137308A (en) * | 2020-05-08 | 2021-11-17 | 주식회사 만도모빌리티솔루션즈 | Driver assistance system and method therof |
US20220212658A1 (en) * | 2021-01-05 | 2022-07-07 | Toyota Motor Engineering & Manufacturing North America, Inc. | Personalized drive with occupant identification |
CN113306550B (en) * | 2021-06-25 | 2023-03-03 | 北京梧桐车联科技有限责任公司 | Vehicle emergency risk avoiding method and device, vehicle-mounted equipment and storage medium |
GB2617864A (en) * | 2022-04-21 | 2023-10-25 | Continental Automotive Systems Srl | Method of collision point calculation and emergency brake assist deceleration based on the method of collision point calculation |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6136473A (en) * | 1995-09-28 | 2000-10-24 | Yuasa Corporation | Hydrogen absorbing electrode, nickel electrode and alkaline storage battery |
JPH10119699A (en) * | 1996-10-21 | 1998-05-12 | Mitsubishi Motors Corp | Occupant protecting device for vehicle |
DE19741631B4 (en) * | 1997-09-20 | 2013-08-14 | Volkswagen Ag | Method and device for avoiding and / or minimizing conflict situations in road traffic |
JP2003025945A (en) * | 2001-07-11 | 2003-01-29 | Honda Motor Co Ltd | Air bag system |
US6721659B2 (en) | 2002-02-01 | 2004-04-13 | Ford Global Technologies, Llc | Collision warning and safety countermeasure system |
DE10233575A1 (en) | 2002-07-24 | 2004-02-12 | Robert Bosch Gmbh | Personal protection during impact of object on vehicle involves transmitting control instruction to vehicle steering system depending on detected impact position to enable compensating collision |
EP1772322A3 (en) | 2003-07-11 | 2007-05-16 | Toyota Jidosha Kabushiki Kaisha | Crash-safe vehicle control system |
FR2909958B1 (en) | 2006-12-14 | 2009-07-31 | Peugeot Citroen Automobiles Sa | SYSTEM FOR MINIMIZING DAMAGE CAUSED BY A VEHICLE FOLLOWING A COLLISION WITH AN OBSTACLE, SUCH AS ANOTHER VEHICLE |
JP5146288B2 (en) * | 2008-12-02 | 2013-02-20 | トヨタ自動車株式会社 | Vehicle control device |
US8812226B2 (en) | 2009-01-26 | 2014-08-19 | GM Global Technology Operations LLC | Multiobject fusion module for collision preparation system |
JP5464333B2 (en) * | 2009-09-18 | 2014-04-09 | ダイムラー・アクチェンゲゼルシャフト | Front collision overlap amount control device |
KR101029096B1 (en) * | 2010-11-18 | 2011-04-13 | 김은숙 | Method of avoiding side collision of vehicle |
JP2012245954A (en) * | 2011-05-31 | 2012-12-13 | Denso Corp | Collision detecting device, and occupant protection system |
DE102014212898A1 (en) * | 2014-07-03 | 2016-01-07 | Robert Bosch Gmbh | Method for determining an emergency trajectory and method for partially automated or automated guidance of an ego vehicle |
-
2015
- 2015-01-20 US US14/600,086 patent/US9381915B1/en active Active
- 2015-12-18 RU RU2015154607A patent/RU2015154607A/en not_active Application Discontinuation
-
2016
- 2016-01-12 DE DE102016100398.0A patent/DE102016100398A1/en active Pending
- 2016-01-13 CN CN201610021320.4A patent/CN105818770B/en active Active
- 2016-01-19 MX MX2016000755A patent/MX355868B/en active IP Right Grant
- 2016-01-20 GB GB1601030.8A patent/GB2536116A/en not_active Withdrawn
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11110916B2 (en) | 2016-09-13 | 2021-09-07 | Mando Corporation | Impact-absorbing apparatus and method for vehicle |
Also Published As
Publication number | Publication date |
---|---|
MX355868B (en) | 2018-05-02 |
US9381915B1 (en) | 2016-07-05 |
CN105818770A (en) | 2016-08-03 |
DE102016100398A1 (en) | 2016-07-21 |
GB201601030D0 (en) | 2016-03-02 |
CN105818770B (en) | 2020-10-30 |
GB2536116A (en) | 2016-09-07 |
MX2016000755A (en) | 2016-07-19 |
RU2015154607A (en) | 2017-06-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9381915B1 (en) | Vehicle side impact control | |
US9746550B2 (en) | Detecting low-speed close-range vehicle cut-in | |
US9650019B2 (en) | Vehicle car wash mode | |
US9925920B2 (en) | Extended lane blind spot detection | |
US9802566B2 (en) | Adaptive suppression of vehicle restraint system | |
US9988046B2 (en) | Enhanced collision avoidance | |
US20170123430A1 (en) | In-path target selection during lane change | |
US20160207495A1 (en) | Velocity based pedestrian sensing | |
US9509775B2 (en) | Cooperative occupant sensing | |
US9412277B2 (en) | Vehicle cut-in strategy | |
US11167754B2 (en) | Systems and methods for trajectory based safekeeping of vehicles | |
US20190118827A1 (en) | Decentralized minimum risk condition vehicle control | |
US20160299617A1 (en) | Vehicle passenger input source identification | |
GB2561443A (en) | Two-point supplemental seatbelt with secondary buckle | |
US20210316722A1 (en) | Systems and methods for trajectory based safekeeping of vehicles | |
US9682669B2 (en) | Vehicle safety power management | |
US20160214555A1 (en) | Two dimensional pedestrian impact sensing | |
US9067555B1 (en) | Side impact vehicle restraint deployment | |
US11577726B2 (en) | Vehicle assist feature control | |
EP4017772A1 (en) | Systems and methods for trajectory based safekeeping of vehicles |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FORD GLOBAL TECHNOLOGIES, LLC, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CROMBEZ, DALE SCOTT;LAUFFER, SCOTT J.;SIGNING DATES FROM 20150113 TO 20150115;REEL/FRAME:034751/0388 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |