Vehicle-to-vehicle communication

Abstract

A computer-implemented method performed by vehicle-to-vehicle communication system (1) for adapting operational performance of a receiving vehicle. The method comprises by processing circuitry of the system (1): monitoring ( 1001) in a host vehicle with support from at least a first onboard sensor, host vehicle status changes and / or host vehicle surroundings; determining (1002) that an event has occurred when detected that monitored host vehicle status changes and / or host vehicle surroundings fulfill predeterminable criteria, wherein a type of said event is determined based on the detected host vehicle status changes and / or host vehicle surroundings; determining (1003) a notification zone radius based on vehicleoperational factors and the event type; transmitting (1004) from said host vehicle via Bluetooth, data indicative at least of said event type and the notification zone; receiving (1005) said event data at a secondary vehicle within Bluetooth communication range; and assessing (1006) said event data at said secondary vehicle. The method further comprises when assessed that the secondary vehicle is within the notification range, adapting (1007) operational performance of the secondary vehicle by adjusting a speed control system based on the event type; and retransmitting (1008) said event data via Bluetooth from said secondary vehicle in a chain notification

Description

(0001) The disclosure relates generally to vehicle-to-vehicle (V2V) communication. In particular aspects, the disclosure relates to a vehicle-to-vehicle communication system for adapting operational performance of a receiving vehicle. The disclosure is applicable in view of vehicles e.g. heavy-duty vehicles, such as trucks and construction equipment, among other vehicle types. Although the disclosure may be described with respect to a particular vehicle, the disclosure is not restricted to any particular vehicle.BACKGROUND(0002) In the field of detecting traffic and operating environment conditions, OEMs commonly rely on cloud and / or third-party devices to optimize routes and communication, such as between vehicles and / or drivers. By relying on vehicle-to-infrastructure (V2I) communication, cost is incurred to integrate third party devices, and cellular costs may be high. There may also be gaps in cellular coverage in tunnels and / or remote areas, such as for instance in the Western United States, Alaska, Canada and so forth. In view thereof, there is room for improvements when it comes to communicating traffic and operating environment conditions detected by a first vehicle to other vehicles in the surroundings, and subsequently potentially affecting such surrounding vehicles’ operational performance.SUMMARY(0003) According to a first aspect of the disclosure, there is provided a computerimplemented method performed by a vehicle-to-vehicle communication system for adapting operational performance of a receiving vehicle.(0004) The method comprises, by processing circuitry of the system, monitoring in a host vehicle - such as a primary vehicle - with support from at least a first onboard sensor - such as a driver input switch and / or a surrounding detecting sensor e.g. radar and / or camera host vehicle status changes and / or host vehicle surroundings e.g. road conditions.(0005) The method further comprises determining - e.g. with support from a Vehicle Control Module (VCM) communicatively coupled to the at least first onboard sensor - that an event has occurred when detected that monitored host vehicle status changes and / or host vehicle surroundings fulfill prcdctcrminablc criteria - such as c.g. accident detected ahead wherein a type of the event is determined based on the detected host vehicle status changes and / or host vehicle surroundings.(0006) Moreover, the method comprises determining - such as calculating - a notification zone radius based on vehicle-operational factors such as for instance one or more of impact severity, slowdown impact, event duration, rerouting necessities, prior rerouting opportunities - and further based on the event type.(0007) Furthermore, the method comprises transmitting - such as broadcasting and / or notifying - from the host vehicle via Bluetooth - for instance with support from a Bluetooth Long Range (BT LR) module - data indicative at least of the event type and the notification zone, such as to surrounding vehicles within Bluetooth communication range.(0008) The method further comprises receiving the event data at a secondary vehicle within Bluetooth communication range, for instance with support from a BT LR module. (0009) Moreover, the method comprises assessing - such as interpreting - the event data at the secondary vehicle, for instance with support from a VCM communicatively coupled to the BT LR module.(0010) Furthermore, the method comprises when assessed that the secondary vehicle is within the notification range, adapting operational performance of the secondary vehicle by adjusting a speed control system for instance Cruise Control based on the event type. (0011) The method further comprises, when assessed that the secondary vehicle is within the notification range, retransmitting - such as rebroadcasting, renotifying and / or leapfrogging - the event data via Bluetooth from the secondary vehicle in a chain notification, such as to surrounding vehicles within Bluetooth communication range.(0012) The disclosure may seek to enable sharing of vehicle operating environment -such as traffic, lane closures etc. vehicle to vehicle to optimize c.g. fuel economy, routes, and driver communication, without reliance on cellular connection. A technical benefit includes that with the introduced concept, there is supported Bluetooth Long Range Communication and vehicle performance adaptation based on V2V Bluetooth communications, such as truck performance adaptation based on truck-to-truck Bluetooth communications. Thereby, Bluetooth technology is utilized to communicate between vehicles, enabling to standardize messaging and alert communications from vehicle to vehicle - such as from truck to truck - utilizing Bluetooth long range / high power. A further technical benefit accordingly include with support from onboard Bluetooth devices enabling “leapfrogging” and / or relaying messages and signals from vehicle to vehicle to signify alerts, improve driver awareness of the road ahead, optimize safety, optimize fuel efficiency, and / or optimize range, etc.(0013) The disclosed aspect(s), examples (including any preferred examples), and / or accompanying claims may be suitably combined with each other as would be apparent to anyone of ordinary skill in the art. Additional features and advantages are disclosed in the following description, claims, and drawings, and in part will be readily apparent therefrom to those skilled in the art or recognized by practicing the disclosure as described herein.BRIEF DESCRIPTION OF THE DRAWINGS(0014) FIG. 1 depicts an exemplary flow chart of a computer-implemented method performed by a vehicle-to-vehicle communication system for adapting operational performance of a receiving vehicle, according to an example.(0015) FIG. 2 illustrates a vehicle-to-vehicle communication system for adapting operational performance of a receiving vehicle, according to an example.DETAILED DESCRIPTION(0016) The detailed description set forth below provides information and examples of the disclosed technology with sufficient detail to enable those skilled in the art to practice the disclosure.(0017) FIG. 1 depicts an exemplary flow chart of a computcr-implcmcntcd method performed by a vehicle-to-vehicle communication system for adapting operational performance of a receiving vehicle, according to an example. The actions may be performed by a processing circuitry of the vehicle-to-vehicle communication system. Moreover, the below actions which may be repeated may be taken in any suitable order.(0018) Action 1001:(0019) The method comprises monitoring 1001 in a host vehicle with support from at least a first onboard sensor, host vehicle status changes and / or host vehicle surroundings. (0020) Action 1002:(0021) The method further comprises determining 1002 that an event has occurred when detected that monitored host vehicle status changes and / or host vehicle surroundings fulfil predeterminable criteria, wherein a type of said event is determined based on the detected host vehicle status changes and / or host vehicle surroundings.(0022) Action 1003:(0023) Moreover, the method comprises determining 1003 a notification zone radius based on vehicle-operational factors and the event type. Optionally, said vehicle-operational factors may comprise one or more of impact severity, slowdown impact, event duration, rerouting necessities, and / or prior rerouting opportunities.(0024) Action 1004:(0025) Furthermore, the method comprises transmitting 1004 from said host vehicle via Bluetooth, data indicative at least of said event type and the notification zone.(0026) Action 1005:(0027) The method further comprises receiving 1005 said event data at a secondary vehicle within Bluetooth communication range.

[0028] Action 1006:(0029) Furthermore, the method comprises assessing 1006 said event data at said secondary vehicle.(0030) Action 1007:(0031) Moreover, the method comprises, when assessed that the secondary vehicle is within the notification range, adapting 1007 operational performance of the secondary vehicle by adjusting a speed control system based on the event type.(0032) Action 1008:(0033) The method further comprises, when assessed that the secondary vehicle is within the notification range, retransmitting 1008 said event data via Bluetooth from said secondary vehicle in a chain notification.(0034) The approach presented herein accordingly relate to integration of Bluetooth technology to communicate vehicle to vehicle - such as truck to truck - to then “leapfrog” from that vehicle to the next, down e.g. a highway, without using cellular or satellite communication, thus representing a de-centralized and / or “off grid” approach. These communications may then be integrated into vehicle functions, and vehicle status changes communicated, for instance relating to speed changing, braking events, driver input through button / situation identifiers, etc. Based on these communications, drivers and / or vehicles ahead / behind of a situation may be alerted, instructed to slow down and / or to steer away from an emergency vehicle, etc. The approach is exemplified in FIG. 2, which illustrates a vehicle-to-vehicle communication system 1 for adapting operational performance of a receiving vehicle, according to an example.(0035) As illustrated, monitored signals of an exemplifying e.g. first vehicle may for instance relate to one or more of current vehicle speed, ACC following distance, speed of forward vehicle, automatic emergency braking activation, TPMS event such as blowout etc., whereas sensor input for instance may be derived from one or more of forward looking radar(s) / camera(s), GPS antenna(s), tyre pressure monitoring sensor(s) and / or user switch(es) for road events, etc. Events that may occur - and which for instance may infer receiving vchiclc(s) to c.g. with support from a VECU and / or CDC or the like reduce speed and / or prompt a vehicle driver with a notification - may for instance relate to AEB event(s), driver button presses to signify current situation, emergency vehicle communication, emergency hazard button input, etc. As described herein, vehicle-to-vehicle using Long Range Bluetooth is utilized to leapfrog communication about the exemplifying first vehicle’s operating environment. Issues may in this manner be communicated - for instance using both sides of traffic - in advance to vehicles that may be affected.(0036) As described above, vehicle sensors such as radar(s) and / or camera(s) may be utilized to identify obstacles and / or road conditions e.g. fog. Moreover, there may be utilized buttons and / or notification methods where a driver can communicate issues e.g. without looking away from the road or taking his / her hand off the wheel for an extended period of time. The use of vehicle-to-vehicle communication as described herein may thus support optimization of routes and / or functions, such as supporting predictive cruise control feature(s) that saves fuel by optimizing speed, gear changes and coasting to the topography, curves, roundabouts and speed limits ahead like for instance exemplifying i-Scc to avoid incurring fuel economy losses. It may be noted that as an alternative or supplement to V2V communication - such as to support changing predictive cruise control based on traffic information - other means of communication may also be feasible, for instance V2Cloud. (0037) The following table reflects exemplifying events and / or scenarios identified e.g. by a VCM - to be of importance - such as fulfilling predeterminable criteria - to communicate to other vehicles, and further reflects how these events potentially may be identified, corresponding exemplifying types of the events, and corresponding exemplifying notification zones.(0038) To determine a Notification Zone, several factors may be considered, such as for instance whether a reroute is necessary. If the event relates to things that can be avoided by the vehicle / driver during normal driving, such as for instance lane closure or object in lane, then there is no reason to reroute. These events could be resolved by changing lanes ahead of time and / or by being more vigilant e.g. in case of fog. If on the other hand a reroute is necessary, the following factors may be considered: slow down impact - e.g. 1 kph slow down or 60 kph slow down - and duration, as well as previous rerouting opportunities e.g. was the last chance to reroute 1 km ago or 20 km ago. Once those factors have been considered, the notification zone may be determined. If the slowdown is significant and the previous reroute opportunity for instance was 20 km ago on this path, then the notification zone may be 21 km, derived from the route 1 km, to allow for choice and route adjustment such as for instance changing lanes, etc. The notification radius is accordingly determined based on event type.(0039) Data may then be generated indicative at least of the event type and the notification zone, such as by means of a VCM, and according to an example the VCM may generate a unique ID for the event comprising one or more of initial vehicle ID, event type, notification zone - e.g. including path of travel / path agnostic and / or distance from event -initial report location - e.g. latitude, longitude, heading, time, road - and / or a cancellation counter which e.g. may be zero to start.(0040) Said data is transmitted utilizing Bluetooth, such as with support from a VCM, and according to an example the VCM notifies through e.g. a CGW BLE interface to all vehicles within range. Upon a vehicle within range receiving the notification, said receiving vehicle assesses the data, such as by a VCM of the receiving vehicle interpreting the notification unique ID. Such an interpretation may for instance involve considerations such as: Have 1 been notified of this before? If yes, ignore. If no, then identify whether the event affects the path of travel or is notifiable to the driver. Further considerations involve identifying whether the receiving vehicle is within the notification zone. If within the notification zone, continue to retransmit the event to other vehicles until outside of notification zone, i.e. if the notification zone was determined to be e.g. 5 miles of agnostic path and the receiving vehicle is e.g. 6 miles away - cease leapfrog retransmit activity.Furthermore, if within the notification zone, all informed vehicle IDs may be logged to not continue to notify informed vehicles, that is if the notification is sent to a vehicle x, then blacklist from notifying of event with same ID this could for instance be maintained by respective vehicles such as by respective VCM. If the receiving vehicle on the other hand is outside of the notification zone, then clear the unique ID notification and unique ID vehicle blacklist. When there in vehicle x - which also has been notified of the incident - is determined that the incident is no longer present, attempt may be made to clear notification by incrementing a cancellation counter. Once the cancellation counter exceeds e.g. 2, event blacklists are cleared and restarted.(0041) According to an example, data indicative at least of the event type and the notification zone may be leapfrogged to any device i.e. vehicle within leapfrog range. Further according to this example, there is notification in the receiving vehicle(s) only if impacted -the data may nevertheless be leapfrogged to other vehicles in range. Retroactive path / possible reroute may be leapfrogged. If there for instance is a new route within e.g. 1 mile then only 1 mile, if reroute is e.g. 50 miles away leapfrog until 50 miles away.(0042) A potential scenario supported by the inventive concept herein, may be represented by a host vehicle detecting a crash, E-call or a driver of the vehicle pressing button to signify crash / slow down. There is no notification to a driver in a secondary vehicle within range going in an opposite direction on a different road; however, said secondary vehicle is used to leapfrog to yet another vehicle within its range. The driver of this latter vehicle is however similarly not notified, since in the exemplifying scenario, this vehicle’s future route is not impacted. In the scenario, the secondary vehicle leapfrogs also to still another vehicle within its range, within which the driver is notified in that in this example the vehicle’s navigation is not planned. Should this latest vehicle however had a navigation planned in the path, the driver would e.g. have been notified and / or the vehicle e.g. redirected if deemed faster. Should the vehicle’s planned navigation on the other hand not had been in path, then the driver would not have been notified.(0043) It should be noted that controllers VMCU, CGW, VEUC etc. discussed herein merely are exemplifying and that other e.g. generic and / or feasible ECUs and / or controllers alternatively may be utilized in a similar manner.(0044) The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. It will be further understood that the terms "comprises," "comprising," "includes," and / or "including" when used herein specify the presence of stated features, integers, actions, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, actions, steps, operations, elements, components, and / or groups thereof.(0045) It will be understood that, although the terms first, second, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the scope of the present disclosure.(0046) Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.(0047) It is to be understood that the present disclosure is not limited to the aspects described above and illustrated in the drawings; rather, the skilled person will recognize that many changes and modifications may be made within the scope of the present disclosure and appended claims. In the drawings and specification, there have been disclosed aspects for purposes of illustration only and not for purposes of limitation, the scope of the disclosure being set forth in the following claims.

Claims

1. A computer-implemented method performed by a vehicle-to-vehicle communication system (1) for adapting operational performance of a receiving vehicle, said method comprising by processing circuitry of the system (1):monitoring (1001) in a host vehicle with support from at least a first onboard sensor, host vehicle status changes and / or host vehicle surroundings;determining ( 1002) that an event has occurred when detected that monitored host vehicle status changes and / or host vehicle surroundings fulfill prcdctcrminablc criteria, wherein a type of said event is determined based on the detected host vehicle status changes and / or host vehicle surroundings;determining (1003) a notification zone radius based on vehicle-operational factors and the event type;transmitting (1004) from said host vehicle via Bluetooth, data indicative at least of said event type and the notification zone;receiving (1005) said event data at a secondary vehicle within Bluetooth communication range;assessing ( 1006) said event data at said secondary vehicle; andwhen assessed that the secondary vehicle is within the notification range, adapting (1007) operational performance of the secondary vehicle by adjusting a speed control system based on the event type; and retransmitting (1008) said event data via Bluetooth from said secondary vehicle in a chain notification2. The method of claim 1, wherein said vehicle-operational factors comprises one or more of impact severity, slowdown impact, event duration, rerouting necessities, prior rerouting opportunities.