Patent Description:
Threatening situations may occur involving a vehicle. An example is described in patent publication <CIT> where multiple people surround a vehicle for carjacking or robbing. <CIT> suggests providing an autonomous vehicle with an emergency escape mode for handling such situations.

While providing one possible threat mitigation approach, the emergency escape mode suggested by <CIT> is not always sufficiently effective, or effective at all. Therefore, there is a need for additional or alternative threat mitigation approaches.

Other Examples of art in the field are XP055692654 and XP55692689 A1 that discloses parts of a manual document of a Mercedes R-Klasse model, and <CIT> that discloses a blind spot potential-hazard avoidance system. The document <CIT> equally represents valuable background art to the present disclosure.

A first aspect is a method for controlling a vehicle according to claim <NUM>. The method comprises determining whether one or more surrounding vehicles demonstrate threatening behavior, and (when it is determined that one or more surrounding vehicles demonstrate threatening behavior) controlling the vehicle to perform one or more threat evasive actions.

An advantage of this aspect is that a method is provided that enables mitigation of threatening behavior by surrounding vehicles.

In some embodiments, determining whether one or more surrounding vehicles demonstrate threatening behavior is based on information regarding surrounding vehicles acquired by one or more external sensors mounted on the vehicle, and interpretation of the information regarding surrounding vehicles to provide one or more threat determining metric associated with the one or more surrounding vehicles.

In some embodiments, the method further comprises acquiring information regarding surrounding vehicles from one or more external sensors mounted on the vehicle, and interpreting the information regarding surrounding vehicles to provide one or more threat determining metric associated with the one or more surrounding vehicles.

In some embodiments, the one or more threat determining metric associated with a surrounding vehicle comprise one or more of a speed of the surrounding vehicle, a velocity of the surrounding vehicle, a difference between speed of the surrounding vehicle and speed of the vehicle, a difference between velocity of the surrounding vehicle and velocity of the vehicle, a distance between the surrounding vehicle and the vehicle, and a trend of the distance between the surrounding vehicle and the vehicle.

An advantage of any of these embodiments is that determination of threatening behavior is enabled by means of suitable metric(s), thereby enabling accurate determination of whether or not surrounding vehicles behave threatingly.

In accordance to the invention, one or more surrounding vehicles demonstrating threatening behavior comprises a first surrounding vehicle directly in front of the vehicle slowing down in absence of traffic related reason to slow down as well as a second surrounding vehicle in an adjacent lane to the vehicle slowing down in association with the first surrounding vehicle.

An advantage of any of these embodiments is that certain threatening scenarios can be accurately recognized.

In some embodiments, controlling the vehicle to perform one or more threat evasive actions comprises controlling the vehicle to perform one or more of activating a visual deterrent maneuver, activating an audial deterrent maneuver, activating an intrusion mitigating maneuver, disabling a collision avoidance system, taking an available escape route, initiating an emergency call, and initiating a call to remote controller.

An advantage of any of these embodiments is that performance of threat evasive actions is enabled by suitable means, thereby providing effective and/or flexible threat mitigation.

A second aspect is a computer program product comprising a computer readable medium carrying a computer program comprising program instructions. The computer program is loadable into a data processing unit and configured to cause execution of the method according to the first aspect when the computer program is run by the data processing unit.

An advantage of this aspect is that a carrier is provided for the software implementing the method that enables mitigation of threatening behavior by surrounding vehicles.

A third <NUM>. aspect is an apparatus for controlling a vehicle according to claim.

An advantage of this aspect is that a physical apparatus is provided that enables mitigation of threatening behavior by surrounding vehicles.

The controlling circuitry of the apparatus is configured to cause acquisition of information regarding surrounding vehicles from one or more external sensors mounted on the vehicle, and interpretation of the information regarding surrounding vehicles to provide one or more threat determining metric associated with the one or more surrounding vehicles, wherein determination of whether one or more surrounding vehicles demonstrate threatening behavior is based on the one or more threat determining metric.

In some embodiments, the one or more control signals for controlling the vehicle to perform one or more threat evasive actions comprise one or more control signals for controlling the vehicle to perform one or more of activating a visual deterrent maneuver, activating an audial deterrent maneuver, activating an intrusion mitigating maneuver, disabling a collision avoidance system, taking an available escape route, initiating an emergency call, and initiating a call to a remote controller.

In some embodiments, the system further comprises one or more of a visual interface, an audial interface, an intrusion mitigator, a collision avoidance system, a route planner, and a remote communication system.

Various different criteria may be used to define whether surrounding vehicle(s) demonstrate threatening behavior. For example, it may be defined that surrounding vehicle(s) demonstrate threatening behavior when a probability that the surrounding vehicle(s) will be part of an upcoming criminal activity (e.g., towards the vehicle subject to control, and/or its occupants) exceeds a probability threshold. Such probabilities may, for example, be estimated based on statistics and/or machine learning. Examples of surrounding vehicle(s) demonstrating threatening behavior will be elaborated on later herein.

Various different criteria may be used to define threat evasive actions (i.e., threat mitigating actions). For example, a threat evasive action may be defined as any act that lowers a probability that upcoming - or ongoing - criminal activity (e.g., towards the vehicle subject to control, and/or its occupants) is commenced and/or carried through. Such probabilities may, for example, be estimated based on statistics and/or machine learning. Examples of threat evasive actions will be elaborated on later herein. The terms "threat evasion" and "threat mitigation" will be used interchangeably herein.

Generally, the vehicle subject to control may be an autonomous vehicle or a manually operable vehicle.

The vehicle subject to control is generally referred to herein as "a/the vehicle", but may alternatively be termed "a/the vehicle subject to control" or "a/the primary vehicle".

Also generally, any surrounding vehicle may be an autonomous vehicle or a manually operable vehicle.

Furthermore, any of the methods described herein may typically be fully, or partly, computer-implemented.

A general advantage of some embodiments is that threat mitigation approaches are provided.

An advantage of some embodiments is that threat mitigation may be improved (e.g., resulting in an increased probability to defer an ongoing criminal act).

Generally, the threat mitigation approaches according to some embodiments may be applied alone or in combination with other threat mitigation approaches (e.g., the emergency escape mode of <CIT>).

In the following, embodiments will be described for controlling a vehicle to mitigate threatening situations involving one or more surrounding vehicles.

<FIG> illustrates an example method <NUM> for controlling a vehicle according to some embodiments.

The method comprises determining whether one or more surrounding vehicles demonstrate threatening behavior, as illustrated by step <NUM>.

Determining whether one or more surrounding vehicles demonstrate threatening behavior may comprise interpreting information regarding surrounding vehicles acquired by one or more external sensors mounted on the vehicle. Example sensors include, but are not limited to, image sensors (e.g., cameras), RADAR sensors, and LIDAR sensors.

In some embodiments, the method comprises acquiring information regarding surrounding vehicles from one or more external sensors mounted on the vehicle, as illustrated by optional step <NUM>.

Alternatively or additionally, the method may comprise interpreting information regarding surrounding vehicles, as illustrated by optional step <NUM>.

Example approaches that may be used in the interpretation includes, but are not limited to, image recognition, distance estimation, speed estimation, and velocity estimation.

For example, the interpretation may provide as result one or more threat determining metric associated with the one or more surrounding vehicles. It may then be determined that surrounding vehicles demonstrate threatening behavior if the threat determining metric(s) fulfill one or more threatening behavior criteria. An example of a threatening behavior criterion is when a threat determining metric falls on a first side of (e.g., exceeds or subceeds) a metric threshold.

The one or more threat determining metric associated with a surrounding vehicle may, for example, comprise one or more of a speed of the surrounding vehicle, a velocity of the surrounding vehicle, a difference between speed of the surrounding vehicle and speed of the vehicle (i.e., a relative speed), a difference between velocity of the surrounding vehicle and velocity of the vehicle (i.e., a relative velocity), a distance between the surrounding vehicle and the vehicle, and a trend (increasing/decreasing) of the distance between the surrounding vehicle and the vehicle.

A potentially threatening situation wherein it may be determined that one or more surrounding vehicles demonstrate threatening behavior comprises a first surrounding vehicle, which is directly in front of the vehicle, slowing down in absence of traffic related reason to slow down. This situation is illustrated in <FIG>.

A suitable threat determining metric may then include a trend of the speed (acceleration/retardation) of the first surrounding vehicle, and a threatening behavior criterion may be retardation being above a first threshold value, possibly combined with traffic related information.

According to the invention, the traffic related reasons to slow down include other vehicle(s) (in front of the first surrounding vehicle) also slowing down, a queueing indication, a speed limit change (decreasing speed limit), an upcoming junction or road bend, decreasing visibility (e.g., due to fog, rain, or snow), an obstacle in front of the first surrounding vehicle (e.g., an animal or a fallen tree), etc. Traffic related information is acquired in any suitable way, e.g., through image sensors, from a navigation system, from a cloud service, etc..

According to the invention, a potentially threatening wherein it may be determined that two or more surrounding vehicles demonstrate threatening behavior comprises a first surrounding vehicle, which is directly in front of the vehicle, slowing down in absence of traffic related reason to slow down combined with a second surrounding vehicle in an adjacent lane to the vehicle (typically the adjacent lane to the left in the travelling direction) slowing down in association with (e.g., keeping substantially the same speed as the first surrounding vehicle) the first surrounding vehicle. For example, the second surrounding vehicle may be an autonomous car set up to follow the first surrounding vehicle (which may be autonomous or manually operated) in the neighbouring lane and at a certain distance behind the first surrounding vehicle. This situation is also illustrated in <FIG>.

Suitable threat determining metrics may then include speeds of the first and second surrounding vehicles, and a trend of the speed of the first surrounding vehicle. A threatening behavior criterion may be retardation of the first surrounding vehicle being above a first threshold value while a difference between the speeds of the first and second surrounding vehicles is below a second threshold value, possibly combined with traffic related information.

Further examples of potentially threatening situations, not comprised by the scope of the claims, wherein it may be determined that one or more surrounding vehicles demonstrate threatening behavior comprise a surrounding vehicle approaching fast behind the vehicle, a surrounding vehicle closing up from the side of the vehicle (potential ramming), a surrounding vehicle approaching in the same lane as the vehicle but in opposite direction, surrounding vehicles blocking alternative routes of the vehicle without traffic related reasons, etc..

When the vehicle is stationary, or has a speed below a threshold value, examples of potentially threatening situations not comprised by the scope of the claims include one or more doors of surrounding vehicles being open/opened, one or more persons approaching the vehicle, one or more persons outside the vehicle wearing face mask, one or more persons outside the vehicle carrying a weapon (e.g., a gun, a knife, a knuckle-duster, or similar), etc..

The further examples may be combined with the above examples in any suitable manner to define potentially threatening situations. For example, a potentially threatening situation wherein it may be determined that one or more surrounding vehicles demonstrate threatening behavior comprises a first surrounding vehicle, which is directly in front of the vehicle, slowing down in absence of traffic related reason to slow down combined with a second surrounding vehicle in an adjacent lane to the vehicle slowing down in association with the first surrounding vehicle and a third surrounding vehicle approaching fast behind the vehicle.

When it is determined that one or more surrounding vehicles demonstrate threatening behavior (Y-path out of step <NUM>), the method comprises controlling the vehicle to perform one or more threat evasive actions, as illustrated by step <NUM>. For example, step <NUM> may comprise generating one or more control signals and transmit the generated signals to respective parts of the vehicle to cause performance of the one or more threat evasive actions.

When it is determined that no surrounding vehicles demonstrate threatening behavior (N-path out of step <NUM>), the method may avoid causing the vehicle to perform any threat evasive actions. Alternatively or additionally, the method may continue monitoring surrounding vehicles for threatening behavior when it is determined that no surrounding vehicles demonstrate threatening behavior (N-path out of step <NUM>), as illustrated by the loop-back in <FIG>.

Typically, the controlling step <NUM> may be an automatic step performed directly responsive to a determination that one or more surrounding vehicles demonstrate threatening behavior.

However, in some embodiments, determination that one or more surrounding vehicles demonstrate threatening behavior may trigger generation of a query to a vehicle occupant, inquiring whether or not the one or more threat evasive actions should be performed.

The threat evasive actions may be performed in response to an instruction to proceed being received via a user interface in such embodiments. Alternatively or additionally, the threat evasive actions may, in such embodiments, be performed in response to absence of any instruction being received via the user interface (e.g., during a specified duration of time starting when the query is issued). Yet alternatively or additionally, performance of the threat evasive actions may be canceled/aborted in response to an instruction not to proceed being received via the user interface.

According to some embodiments, determination that one or more surrounding vehicles demonstrate threatening behavior may trigger generation of a query to a remote controller, inquiring whether or not the one or more threat evasive actions should be performed.

The threat evasive actions may be performed in response to an instruction to proceed being received from the remote controller in such embodiments. Alternatively or additionally, the threat evasive actions may, in such embodiments, be performed in response to absence of any instruction being received from the remote controller (e.g., during a specified duration of time starting when the query is issued). Yet alternatively or additionally, performance of the threat evasive actions may be canceled/aborted in response to an instruction not to proceed being received from the remote controller.

The remote controller may be completely computer-implemented, or may involve a human control operator and a user interface rendering audio and/or imagery from the vehicle.

Termination of the one or more threat evasive actions could, similarly, be automatic (e.g., after some duration of time has passed, responsive to the threat being considered removed, etc.), or depending on instructions from a vehicle occupant or a remote controller.

Some example threat evasive actions include visual deterrent maneuvers (e.g., shining or blinking some or all lights of the vehicle), audial deterrent maneuvers (e.g., sounding the horn of the vehicle), intrusion mitigating maneuvers (e.g., lock all doors of the vehicle, raising all windows of the vehicle, activate shielding of the vehicle such as bullet-proofing, release a spray such as pepper spray, tear gas, fogging spray, or deoxyribonucleic acid - DNA - spray), disabling of a collision avoidance system (e.g., to be able to ram a surrounding vehicle), taking of an available escape route (e.g., by reversing and/or turning; possibly off-road), initiation of an emergency call (possibly including transmission, rendering, and/or recording of audio and/or imagery - stills or video), and initiation of a call to a remote controller (possibly including transmission, rendering, and/or recording of audio and/or imagery - stills or video). The threat evasive actions may be performed alone or in any suitable combination.

<FIG> schematically illustrate an example vehicle <NUM> in a threatening scenario, wherein it may be determined that one or more surrounding vehicles <NUM>, <NUM> demonstrate threatening behavior.

In this scenario, a first surrounding vehicle <NUM> is directly in front of the vehicle <NUM> (traveling in the same direction as the vehicle <NUM>). If the first surrounding vehicle <NUM> begins to slow down (retardation; decreasing speed <NUM>) for no apparent reason (e.g., in absence of traffic related reason to slow down), this may be determined as a demonstration of threatening behavior according to some embodiments.

Possibly, the above criterion for threatening behavior may be supplemented by a second surrounding vehicle <NUM> in an adjacent lane to the vehicle slowing down in association with the first surrounding vehicle <NUM> (e.g., speeds <NUM> and <NUM> being substantially equal).

An example will now be elaborated on to illustrate how the method <NUM> may be implemented.

The vehicle recognizes that it is being rammed to the side of the road by using an exterior camera (e.g., <NUM> degree camera), a radar system, and/or vehicle-to-vehicle (V2V) communication. If the vehicle notices that one vehicle is driving in decreasing speed in front of it, another vehicle to the side is driving in the same decreasing speed, and no other vehicle is in front of either of them, this may be determined as threatening behavior. The vehicle may also be configured to recognize if doors of the other vehicles are being open/opened and/or if persons are walking towards the rammed vehicle.

When threatening behavior is recognized, the proposed system could automatically connect to a communication service, where an operator can use the camera and/or other sensors remotely to see what is happening live.

If the operator judges that there is threatening behavior, the operator may activate one or more threat mitigating functions of the vehicle (e.g., blinking all lights and/or sounding the horn) and/or inform the authorities (e.g., via an emergency call) so that the police may be able to intervene.

Alternatively or additionally, the threat mitigating functions of the vehicle may be configured for automatic activation; without the interaction with a remote operator. For example, the threat mitigating functions may be activated automatically when the vehicle does not have Internet coverage.

<FIG> illustrates an example method <NUM>. The method <NUM> may be seen as an example implementation of the method <NUM> of <FIG>.

In step <NUM>, it is determined if there is a (first) vehicle driving in front with decreasing speed. If so (Y-path out of step <NUM>), the method continues to step <NUM>. If not (N-path out of step <NUM>), the method loops back to step <NUM> and continues monitoring.

In step <NUM>, it is determined if there are other vehicles driving in front of the first vehicle, which are also decreasing their speed, and/or if there is another obstacle in front of the first vehicle (e.g., an animal or a fallen tree). If so (Y-path out of step <NUM>), the method loops back to step <NUM> and continues monitoring. If not (N-path out of step <NUM>), the method continues to step <NUM>.

In step <NUM>, it is determined if there is any escape route, which is not blocked by another (second) vehicle. If so (Y-path out of step <NUM>), the method continues to step <NUM> where the escape route is taken. If not (N-path out of step <NUM>), the method continues to step <NUM>.

In step <NUM>, it is determined if coverage is available for contacting a remote operator. If so (Y-path out of step <NUM>), the method continues to step <NUM>. If not (N-path out of step <NUM>), the method continues to step <NUM>.

In step <NUM>, it is determined if doors of the first or second vehicles are open. If so (Y-path out of step <NUM>), the method continues to step <NUM>. If not (N-path out of step <NUM>), the method loops back to step <NUM> and continues monitoring doors.

In step <NUM>, it is determined if persons are walking towards the vehicle and/or if image recognition reveals unfriendly facial expressions or covered faces. If so (Y-path out of step <NUM>), the method continues to step <NUM>. If not (N-path out of step <NUM>), the method loops back to step <NUM> and continues monitoring.

In step <NUM>, a remote operator is contacted, and in step <NUM> the remote operator determines if there is indications of threatening behavior. If so (Y-path out of step <NUM>), the method continues to step <NUM>. If not (N-path out of step <NUM>), the method continues to step <NUM> where the method ends without further actions.

In step <NUM>, the remote operator selects one or more actions to be taken. If it is selected to contact authorities, the method continues to step <NUM> where an emergency call is initiated. If, alternatively or additionally, other actions are selected, the method continues to step <NUM>.

In step <NUM> threat mitigation may be performed by the vehicle; e.g., blinking all lights and/or sounding the horn.

Steps <NUM>-<NUM> may be seen as implementations of determining whether one or more surrounding vehicles demonstrate threatening behavior (compare with <NUM>-<NUM> of <FIG>).

Steps <NUM>-<NUM> may be seen as implementations of controlling the vehicle to perform one or more threat evasive actions (compare with <NUM> of <FIG>).

<FIG> schematically illustrates an example arrangement for controlling a vehicle according to some embodiments. The arrangement may be a system suitable for installation (or installed) in a vehicle. The arrangement comprises a controller (CNTR; e.g., controlling circuitry, processing circuitry, a control module, or a control unit) <NUM>, which may be comprised in any suitable apparatus.

For example, the system (e.g., the controller <NUM>) may be configured to execute (or cause execution of) one or more method steps as described in connection with <FIG>.

Particularly, the controller <NUM> is configured to cause determination of whether one or more surrounding vehicles demonstrate threatening behavior (compare with <NUM> of <FIG>) and - responsive to determination that one or more surrounding vehicles demonstrate threatening behavior (compare with <NUM> of <FIG>) - control of the vehicle to perform one or more threat evasive actions (compare with <NUM> of <FIG>).

To this end, the controller <NUM> may comprise, or be otherwise associated with (e.g., be connected, or connectable, to) one or more of a determiner (DET; e.g., determination circuitry or a determination module) <NUM> and a evasive action triggerer (EVA; e.g., triggering circuitry or a triggering module) <NUM>. The determiner <NUM> may be configured to determine whether one or more surrounding vehicles demonstrate threatening behavior. The evasive action triggerer <NUM> may be configured to control the vehicle to perform one or more threat evasive actions responsive to determination that one or more surrounding vehicles demonstrate threatening behavior.

As mentioned before, the one or more threat evasive actions may comprise one or more of activating a visual deterrent maneuver, activating an audial deterrent maneuver, activating an intrusion mitigating maneuver, disabling a collision avoidance system, taking an available escape route, initiating an emergency call, and initiating a call to a remote controller.

For example, the controller <NUM> (e.g., the evasive action triggerer <NUM>) may be configured to control the vehicle to perform one or more threat evasive actions by issuing one or more control signals for one or more respective threat mitigators.

Example threat mitigators include, but are not limited to, visual interfaces (e.g., vehicle lights), audial interfaces (e.g., vehicle horn), intrusion mitigators (e.g., locks, shields, spraying devices, etc.), a collision avoidance system deactivator, a route planner, and a remote communication system (e.g., a wireless communication system suitable for emergency calls and/or calls to a remote controller).

In some embodiments, the arrangement further comprises one or more intrusion mitigators; e.g., a visual interface (VIS) <NUM>, an audial interface (AUD) <NUM>, an intrusion mitigator (INTR) <NUM>, a collision avoidance system (CAS) <NUM>, a route planner (RP) <NUM>, and a remote communication system (RCS) <NUM>.

In some embodiments, the controller <NUM> is further configured to cause acquisition of information regarding surrounding vehicles from one or more sensors (SENS) <NUM> (compare with <NUM> of <FIG>). For example, the controller may be configured to acquire (e.g., receive) such information from the sensors.

The sensors <NUM> may be comprised in the arrangement according to some embodiments. Furthermore, the sensors <NUM> may be mountable on the vehicle (typically on the exterior of the vehicle). Example sensors have already been elaborated on above.

In some embodiments, the controller <NUM> is further configured to cause interpretation of information regarding surrounding vehicles (compare with <NUM> of <FIG>); e.g., to provide one or more threat determining metric associated with the one or more surrounding vehicles that can be used to determine whether surrounding vehicles demonstrate threatening behavior.

To this end, the controller <NUM> may comprise, or be otherwise associated with (e.g., be connected, or connectable, to) an interpreter (INT; e.g., interpretation circuitry or an interpretation module) <NUM>. The interpreter <NUM> may be configured to interpret information regarding surrounding vehicles; e.g., to provide one or more threat determining metric associated with the one or more surrounding vehicles. Example interpretation approaches have already been elaborated on above.

<FIG> schematically illustrates an example vehicle <NUM> (compare with <NUM> of <FIG>) according to some embodiments. The vehicle <NUM> comprises an arrangement (e.g., the arrangement of <FIG>) for controlling a vehicle according to some embodiments.

The arrangement comprises a controller <NUM> (compare with <NUM> of <FIG>) configured to cause determination of whether one or more surrounding vehicles demonstrate threatening behavior and - responsive to determination that one or more surrounding vehicles demonstrate threatening behavior - control of the vehicle <NUM> to perform one or more threat evasive actions.

The vehicle also comprises one or more sensors <NUM> (compare with <NUM> of <FIG>) and one or more intrusion mitigators <NUM> (compare with <NUM>-<NUM> of <FIG>).

In conclusion, some embodiments provide mitigation of threatening behavior, e.g., prevention of ramming autonomous vehicle to rob passengers or strip the vehicle for parts.

The threatening behavior scenario is particularly relevant for autonomous vehicles since it is comparatively easy to predict in their behavior. For example, a manually driven vehicle can easily cause an autonomous vehicle to pull to a halt at the side of the road (e.g., by driving slowly in front of the autonomous vehicle and then stopping, possibly while another - autonomous or manually driven - vehicle drives along the side of the autonomous vehicle, preventing it from escaping).

The described embodiments and their equivalents may be realized in software or hardware or a combination thereof. The embodiments may be performed by general purpose circuitry. Examples of general purpose circuitry include digital signal processors (DSP), central processing units (CPU), co-processor units, field programmable gate arrays (FPGA) and other programmable hardware. Alternatively or additionally, the embodiments may be performed by specialized circuitry, such as application specific integrated circuits (ASIC). The general purpose circuitry and/or the specialized circuitry may, for example, be associated with or comprised in an apparatus such as a vehicle.

Embodiments may appear within an electronic apparatus (such as a vehicle part/system) comprising arrangements, circuitry, and/or logic according to any of the embodiments described herein. Alternatively or additionally, an electronic apparatus (such as a vehicle part/system) may be configured to perform methods according to any of the embodiments described herein.

According to some embodiments, a computer program product comprises a tangible, or non-tangible, computer readable medium such as, for example a universal serial bus (USB) memory, a plug-in card, an embedded drive or a read only memory (ROM). <FIG> illustrates an example computer readable medium in the form of a compact disc (CD) ROM <NUM>. The computer readable medium has stored thereon a computer program comprising program instructions. The computer program is loadable into a data processor (PROC; e.g., data processing circuitry or a data processing unit) <NUM>, which may, for example, be comprised in a vehicle part/system <NUM>. When loaded into the data processor, the computer program may be stored in a memory (MEM) <NUM> associated with or comprised in the data processor. According to some embodiments, the computer program may, when loaded into and run by the data processor, cause execution of method steps according to, for example, any of the methods illustrated in <FIG> or otherwise described herein.

Claim 1:
A method for controlling a vehicle (<NUM>, <NUM>), characterized in that the method comprising:
determining (<NUM>) that one or more surrounding vehicles (<NUM>, <NUM>) demonstrate threatening behavior by determining that a first surrounding vehicle (<NUM>), which is directly in front of the vehicle (<NUM>, <NUM>), is slowing down in absence of traffic related reason to slow down, and determining that a second surrounding vehicle (<NUM>) in an adjacent lane is slowing down in association with the first surrounding vehicle (<NUM>); and
upon determining that said one or more surrounding vehicles demonstrate threatening behaviour,
controlling (<NUM>) the vehicle (<NUM>, <NUM>) to perform one or more threat evasive actions,
wherein a traffic related reason includes at least one of determining: that another vehicle in front of the first surrounding vehicle (<NUM>) is also slowing down; a queueing indication;
a speed limit change; an upcoming junction or road bend; decreasing visibility; an obstacle in front of the first surrounding vehicle (<NUM>),
and wherein the traffic related reason is determined based on obtained traffic related information acquired by at least any of a sensor; a navigation system; and a cloud service.