Method, device, and computer program for annoncing road using in an intelligent transport system
By including RoadUsage Containers in CAMs to convey road usage areas and safety information, connected vehicles can better assess and adapt to each other's driving conditions, addressing the limitations of existing technologies and enhancing safety and traffic flow.
Patent Information
- Application Number
- GB2023006847
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-13
AI Technical Summary
Connected vehicles lack complete information about other vehicles' properties, such as braking distance and adaptive control systems, which limits their ability to predict and maintain safe driving conditions, potentially leading to safety issues like collisions or failure to respect safety distances.
Incorporating RoadUsage Containers in Cooperative Awareness Messages (CAMs) to disseminate road usage areas, including specific distances or shapes, along with safety indications and controllability classes, to inform other vehicles about the required areas for safe driving, allowing them to adapt their trajectories and maintain nominal driving conditions.
Enhances safety by enabling vehicles to accurately assess and adapt to the driving conditions of nearby vehicles, reducing the risk of collisions and maintaining safe distances, thereby improving overall road traffic safety and efficiency.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Still for the sake of illustration, the bicycle at position 150 carries an ITS equipment disseminating VAMs 151. According to the disclosure, VAMs 151 comprise road usage information as described by reference to Figure 3. Accordingly, using VAMs 151, bicycle at position 150 shares with other receiving ITS-Ss (e.g., receiving ITS-Ss 170,130, and 140) a road usage area denoted 152, using a Roadllsage Container. Roadllsage area 152 is used to alert other ITS-Ss (e.g., receiving ITS-Ss 170,130, and 140) that the bicycle at position 150 requests to respect a safety area 152 around it. For example, the Roadllsage area 152 can be described as longitudinal and lateral distances which may vary according to countries, VRU size, VRU speed, and VRU preferences. Additionally, the Roadllsage Container may include a Roadllsage type to explain to other receiving ITS-Ss, such as vehicles at positions 130 and 140, the purpose of this Roadllsage area. For the sake of illustration, the Roadllsage type of Roadllsage area 150 may be set to ‘safety’. Still for the sake of illustration, the vehicle at position 130 embeds an ITS equipment disseminating CAMs 131. According to the disclosure, CAMs 131 comprise road usage information as described by reference to Figure 2. Accordingly, using CAMs 131, the vehicle at position 130 shares with other receiving ITS-Ss (e.g., receiving ITS-Ss 170, 150, and 140) a road usage area denoted 132, using a Roadllsage Container. The Roadllsage area 132 is used to alert other ITS-Ss (e.g., receiving ITS-Ss 170,150, and 140) that the vehicle at position 130 needs a Roadllsage area 132 in front of it to be able to gently break if needed. For example, The Roadllsage area 132 can be specified as a rectangle using CAM the Referenceposition data element as a reference point (as described with reference to Figure 2). As another example, the Roadllsage area 132 may be described as a distance value using the CAM Referenceposition data element and the heading data element (as described with reference to Figure 2). The Roadllsage area 132 may vary over time as a function of the vehicle dynamics such as the speed, the acceleration, the road conditions, the occupancy, the vehicle weight, the braking system performance, or user comfort preferences. In addition, the RoadUsage Container may include a Roadllsage type to explain to other receiving ITS-Ss (e.g., ITS-Ss located at position 140,150,160) the purpose of this Roadllsage area. For the sake of illustration, the Roadllsage type of Roadllsage area 132 may be set to ‘breaking distance’. The vehicle located at position 130 may use the algorithm described by reference to Figure 4 to disseminate CAMs 131 comprising the Road Usage Container. Using ITS 100, the vehicle located at position 140 is informed of the ‘breaking distance’ needs of the approaching vehicle located at position 130. Using an algorithm such as the one described by reference to Figure 5 and CAMs 131 and VAMs 151, the vehicle located at position 140 may decide to enter in the intersection 110 or to stay at the position140 to prevent to cut-in the RoadUsage areas 132 and / or 152. Alternately, the vehicle located at position 140 may decide to adapt its trajectory. As described in reference to Figure 9, the RoadUsage areas may be defined using different means. Structure of a CAM according to some embodiments of the disclosure Figure 2 illustrates an example of a structure of a cooperative awareness message, CAM, according to some embodiments of the disclosure. The illustrated CAM structure, referenced 200, is based on specification ETSI TS 103 900 V0.0.4_2.1.1 (2023-03) and is extended with one or more RoadUsage Containers. As illustrated, it comprises an ITS PDU header referenced 210, a Basic Container 220, a High-Frequency Container 230, a Low-Frequency Container 240, and a special vehicle Container 250. ITS PDU header 210 may be a common header including information about the protocol version, a message type (set to 2 for CAM), and an ITS-S identifier (ID) of the originating ITS-S. Each container includes some data elements (DE) and / or data frames (DF). ETSI TS 102 894-2 Specification defines conventional data elements and data frames used in ITS messages. ITS PDU header 210 comprises generationDeltaTime 211. It is a value expressed in milliseconds indicating the amount of time spent since ITS epoch to generate CAM 200. Basic Container 220 comprises stationType and Referenceposition 221. stationType is used to indicate the type of station (vehicle or Road side unit) and Referenceposition is the position of the ITS at ITS epoch + generationDeltaTime. It is expressed as WGS84 coordinates with a confidence level. High-Frequency Container 230 is used to transmit any dynamics of a vehicle. It is transmitted in each CAM 200 and comprises a Heading that includes orientation of the VRU, for example according to WGS84 north, a Speed that includes the speed value, for example in centimeters per second, a Lane position that includes a lane on the road (same as for a vehicle), a lane off the road, or an island between two lanes to allow the correlation to a map, and an Acceleration, that includes the acceleration value, for example in centimeters per second squared. Low-Frequency Container 240 is used to transmit additional information, not having place in High-Frequency Container 230 as it is static or slow-changing according to dynamics. Low-Frequency Container240 is conditionally transmitted in CAM 200. GenerationDeltaTime, Referenceposition, Heading, Speed, Lane position, and Acceleration information can be used by an algorithm such as the one described by reference to Figure 5 to predict the originating ITS-S path trajectory. As illustrated, High-Frequency Container 230 and / or Low-frequency Container 240 may comprise one or more Roadllsage Containers 231. In turn, each Roadllsage Container comprises one or more RoadUsage areas (denoted RoadUsageArea[]) and optional characteristics associated with the RoadUsage areas. According to some embodiments, a RoadUsageArea may be: an area as defined in a Common Data Dictionary (CDD), a distance (e.g., in meter, with centimeter precision) between a first point and a second point, considering Referenceposition from Basic Container 221 as the first point and the heading from High-Frequency Container 230 as the direction to join the second point at the given distance; a distance (e.g., in meter, with centimeter precision), referenced from a previous RoadUsage area, defined as a distance, considering the same heading from High-Frequency Container 230 and the second point of the previous RoadUsage as first point, a vector from Referenceposition 221 as defined in Basic Container 220, or a vector referenced from a previous RoadUsage area defined as a vector. Different possibilities to describe RoadUsage areas are described by reference to Figure 9. As described above, a Roadllsage type (denoted RoadUsageType[]) may be associated with each defined Roadllsage area. It makes it possible to provide information regarding the usage of the corresponding Roadllsage area. According to some embodiments of the disclosure, the following types may be used as values for the Roadllsage type: collision, auto-braking, assist braking, safety distance, protective or warning field, comfort or economic mode (smooth drive), maneuver on-going, emergency requirements, parking, pedestrian exits from a vehicle, and others. In addition, a Roadllsage safety indication (denoted RoadUsageSafety[]) may be associated with each defined RoadUsageArea. The Roadllsage safety indication may be used to inform an ITS-S that the corresponding Roadllsage area is directed to a safety issue. It may be used to indicate a danger level and / or a controllability class as defined by the originating ITS-S. It may be used by an ITS receiving the corresponding Roadllsage Container to assess the risk in case of presence in the road usage area. For the sake of illustration, the Roadllsage safety indication may comprise: a ControllabilityClass that can be used to define the controllability class (ASI L) of the vehicle if a hazardous event occurs in the RoadUsageArea. These classes may be the following: o CO: controllable in general, o C1: simply controllable, o C2: normally controllable (most drivers could act to prevent injury), and o C3: difficult to control or uncontrollable, a DangerLevel that can be used to define the danger level for the vehicle occupants and / or for the occupants of any other vehicle in case of collision in the RoadUsage area. These levels may be the following: o Level 4: high danger, o Level 3: considerable danger, o Level 2: moderate danger, and o Level 1: no or minor danger. In addition also, a RoadUsage validity indication (denoted RoadUsageValidity[ ]) may provide information about the period of time during which the items of information regarding the RoadUsage area are valid. For the sake of illustration, it may comprise a start time and an end time or only an end time if it is considered that the start time corresponds to the time at which the CAM or VAM is sent. For example, the time at which the CAM or VAM is sent may be determined by the receiving ITS-S by adding generationDeltaTime 211 to ITS epoch. ITS epoch is known and common reference between every ITS-S. Structure of a CAM according to some embodiments of the disclosure Figure 3 illustrates an example of a structure of a cooperative awareness message, VAM, according to some embodiments of the disclosure. The illustrated VAM structure, referenced 300, is based on specification ETSI TS 103 300-3 and is extended with one or more RoadUsage Containers. As illustrated, VAM 300 comprises: a common ITS PDU header referenced 305, a generation delta time referenced 310, a basic container referenced 315, a VRU high frequency container referenced 320 with dynamic properties of the VRU (motion, acceleration, etc.), an optional VRU low frequency container referenced 325, with physical properties of the VRU and static or slow-changing vehicle state (such as exterior lights), an optional cluster information container referenced 330, an optional cluster operation container referenced 335, and an optional motion prediction container referenced 340. ITS PDU header 305 may be a common header including information about the protocol version, a message type (set to 16 for VAM), and an ITS-S identifier (ID) of the originating ITS-S. Each container includes some data elements (DE) and / or data frames (DF). ETSI TS 102 894-2 Specification defines conventional data elements and data frames used in ITS messages. Basic container 315 provides basic information of the originating ITS-S, in particular: a stationType that represents the station type of the originating ITS-S. This data element may take one of the following values: 1 for a pedestrian, 2 for a bicyclist, 3 for a moped, 4 for a motorcycle, 12 for a lightVRU vehicle, or 13 for an animal, and a Position or referenceposition that is the latest geographic position of the originating ITS-S as obtained by the VBS at the VAM generation. It provides the position and position confidence measured at the reference point of the originating ITS-S. The measurement time corresponds to generationDeltaTime that is similar to the generationDeltaTime of a CAM, as described previously. VRU High-Frequency container 320 of the VAM may contain potentially fastchanging status information of the VRU ITS-S such as: a Heading that includes an orientation of the VRU, for example according to WGS84 north, a Speed that includes the speed value, for example in centimeters per second, a Lane position that includes a lane on the road (same as for a vehicle), a lane off the road, or an island between two lanes to allow the correlation to a map, and an Acceleration the includes the acceleration value, for example in centimeters per second squared. GenerationDeltaTime, Referenceposition, Heading, Speed, Lane position, and Acceleration information may be used by an algorithm such as the one described by reference to Figure 5 to predict the originating ITS-S path trajectory. VRU Low-Frequency container 325 of the VAM may contain potentially slow-changing status information of the VRU ITS-S such as: Lights that indicate the profile or the status of the exterior lights, a Sub-Profile that provides a status of the VRU lights, and a Size class that provides the range of dimensions of the VRU. Cluster information container 330 provides information when a VRU is a VRU cluster leader. When effective, a VRU cluster leader reports VAMs on behalf of the other devices located inside the cluster, and cluster operation container 335 provides information and / or parameters relevant to a VRU cluster to which the originating ITS-S belongs according to Cluster information container 330 VRU motion prediction container 340 provides dynamic VRU motion prediction information as well as explicit path prediction, when such information is available in the VRU ITS-S. The path prediction can be used as an alternative method to determine the originating ITS-S path trajectory in an algorithm such as the one described by reference to Figure 4. In addition, and when such information is available, VRU motion prediction container 340 may provide safe distance indicating that one or more new vehicles or other VRUs (e.g. VRU Profile 3 - Motorcyclist) have come closer than a minimum safe lateral distance (MSLaD) laterally, closer than a minimum safe longitudinal distance (MSLoD) longitudinally, and closer than a minimum safe vertical distance (MSVD) vertically. As illustrated, VAM structure 400 further comprises RoadUsage Containers referenced 321, that may be part of High-Frequency Container 320 and / or of Low-frequency Container 325. RoadUsage Containers 321 are similar to RoadUsage Containers 231 described in reference to Figure 2. Generation, transmission, and processing ofCAMs or VAMs and decision Figures 4 and 5 illustrate, using flowcharts, examples of general steps of methods according to embodiments of the present disclosure respectively at an originating ITS-S sending a CPM containing information about road usage needs and at a corresponding receiving ITS-S. As illustrated in Figure 4, a method of communication in an ITS according to some embodiments of the present disclosure aims at transmitting, from an originating ITS-S (for example the vehicle located in position 130 or the VRU located in position 150 in Figure 1), one or more RoadUsage Containers in a CAM or in a VAM (e.g., in CAM 131 or in VAM 151 in Figure 1). In step 400, the originating ITS-S determines a required road usage or road usage needs according to needs or recommendations from an active system, an automatic or assist braking system, vehicle characteristics, a vehicle type, vehicle driver settings, or vulnerable user settings. Environment conditions such as the road slope, the road quality, and / or the weather conditions may also be taken into account. Next, in step 405, the originating ITS-S determines one or more road usage areas according to the previously determined road usage needs. The road usage areas define particular areas on the road, that may be referenced from the referenceposition of the origination ITS-S. The road usage areas may be used to inform other ITS-Ss of a specific usage of these road areas, in order to maintain driving in nominal conditions if these areas remain free from other ITS-Ss and obstacles. Next, in step 410, the originating ITS-S generates one or more RoadUsage Containers (e.g., Roadllsage Containers 231 in Figure 2 or RoadUsage Containers321 in Figure 3), for example by concatenating the RoadUsageArea, RoadUsageType, RoadUsageSafety, and / or RoadUsageValidity as described by reference to Figure 2. Next, in step 415, the originating ITS-S transmits the generated RoadUsage Containers in an Awareness message (i.e., a CAM if the originating ITS-S is a vehicle or a VAM if the originating ITS-S is a VRU). As illustrated in Figure 5, a method of communication in an ITS according to some embodiments of the present disclosure aims at processing, in a receiving ITS-S (e.g., the vehicle located at position 130 or 140 or the VRU located at position 150 or 160 in Figure 1), one or more RoadUsage Containers received in a CAM or in a VAM (e.g., CAM 131 or VAM 151 in Figure 1) to increase the overall safety of the ITS. In step 500, the receiving ITS-S receives an Awareness Message comprising at least one RoadUsage Container. Next, in step 505, the receiving ITS-S obtains one or more road usage areas from the one or more RoadUsage Containers comprised in the received Awareness Message. Next, in step 510, the receiving ITS-S determines whether there exists one or more overlapping portions between the road usage areas and next ego vehicle dynamics. The receiving ITS-S may determine such overlapping portions by determining if its trajectory will overlap the road usage areas in a near future. For the sake of illustration, the trajectory of a receiving ITS-S may be defined by a mathematical relation representing positions as a function of time (e.g., a list of 2D points). A Cartesian coordinate system (S) may be defined with a center C, using the metric convention according to which the abscissa axis is aligned with the East axis and the ordinate axis is aligned with the North axis, such relation may be expressed as follows: Pr(t) = x(t) + y(t) in (S) with x(t) being abscissa coordinate of the receiving ITS-S and y(t) being ordinate coordinate of the receiving ITS-S. Pr(0) is equal to (0,0) in (S). Pr(0) corresponds to the position of the receiving ITS-S at the time TO. Time TO is determined using the ITS epoch and generationDeltaTime received from the originating ITS-S, as follows: TO = ITS epoch + generationDeltaTime Pr(t) may also be defined as a road usage area, as illustrated in Figure 9 being constant or changing as a function of time. It is noted here that a receiving ITS-S may predict the trajectory of an originating ITS-S by using path prediction from the Motion Prediction container (if present). Alternatively, a receiving ITS-S may predict the trajectory of an originating ITS-S by extrapolating its position as a function of time, using received information from the Basic Container comprising the Referenceposition and / or heading, DriveDirection, Speed from the High Frequency Container: Po(t) = T( RPoTO , RPrTO) + Mo(t) in (S) wherein RPoTO is the Referenceposition of the originating ITS-S from the Basic Container at time TO and RPrTO is the Referenceposition of the originating ITS-S at the previously determined time TO. T(RPoT0 , RPrTO) is the translation from point RPoTO to RPrTO in (S). For example, Mo(t) can be determined using heading, DriveDirection and Speed from the High Frequency Container, wherein: heading is indicating the orientation of the originating ITS-S using reference to the WGS84 North axis. The following value can be set: wgs84North(0), wgs84East(900), wgs84South(1800), wgs84West(2700) or any value from 0 to 3601 corresponding 1 / 10 of degrees according to WGS84 North axis, DriveDirection is indicating forward or backward movement, and Speed is indicating the velocity of the originating ITS-S with SpeedValue expressed in centimeters per seconds (Ocm / s for standstill, up to 16383). According to the Speed and heading, the coordinates offsets can be defined as a function of time in meters according to (S): dx(t) = SpeedValue / 10 x cos (2 x PI x heading / 3600) x t in (S) dy(t) = SpeedValue / 10 x sin (2 x PI x heading / 3600) x t in (S) Mo(t) = (dx(t), dy(t)) in (S) PI being the constant number ‘pi’ that is the ratio of a circle's circumference to its diameter. The translation from point RPoTO to RPrTO, T(RPoT0 , RPrTO), in (S), may be determined by converting it as a translation in meter: DY = PI / 180 x R x ( Lat_RPrT0 - Lat_RPoT0 ) DX = PI / 180 x R x (long_RPrT0 x cos (lat_RPrT0 x PI / 180) - long_RPoT0 x cos (lat_RPoT0x PI / 180)) where R is the Earth’s radius in meter (R = 6378137m), Lat_RPrT0 is the latitude of RPrTO, Long_RPrT0 is the longitude of RPrTO, Lat_RPoT0 is the latitude of RPoTO, and long_RPoT0 is the longitude of RPoTO. All longitude and latitude are referring to WGS84 system. Po(t) can be defined as Po(t) = (DX, DY) + (dx(t), dy(y)) Po(t) function can be refined by the receiving ITS-S when a new CAM from the originating ITS-S is received. The function to determine the successive geometry of the Road usage area, denoted AreaPrediction, may be defined by using the geometry definition used by the Road usage area added with the predicted trajectory of the Originating ITS-S: AreaPrediction(t) = Po(t) + RoadllsageArea The overlapping function can be defined as a function in time for a given duration of prediction, denoted prediction_time, with a resolution denoted prediction_resolution, as follows: Overlap(t) = Po(t) D Pr(t) with t € [0 to prediction_time] in step [prediction_resolution] in (S) For the sake of illustration, the value of prediction_resolution may be set to 25ms. Still for the sake of illustration, the value of prediction_time may be estimated at 5 seconds. The overlapping function should be reevaluated at every received CAM or VAM messages by the receiving ITS-S. Using the overlapping function previously defined or any other overlapping function, the receiving ITS-S is able to determine the various overlapping points between the road usage area of the originating ITS-S and the trajectory of the receiving ITS-S. Turning back to Figure 5, the receiving ITS-S evaluates the consequences of the next ego vehicle movement on the originating ITS-S transmitting the Road usage Container(s) (step 515), for example in terms of comfort, disabling adaptive system, emergency breaking, and / or safety risk. For each previously determined overlapping portion, the receiving ITS-S may obtain, from the RoadUsageArea, the associated RoadllsageType information as described with reference to Figure 2. According to the RoadllsageType, the receiving ITS-S may determine the impact on the driving conditions of the originating ITS-S if it is present in the associated RoadllsageArea. For example, if the RoadllsageType is indicating ‘collision’, ‘auto-braking’, ‘assist braking’, ‘safety distance’, ‘protective field’, or ‘warning field’ and any value indicating a system in relationship with the safety, the receiving ITS-S determines that its trajectory will create a safety risk. In addition, for each previously determined overlapping portion, the receiving ITS-S may obtain, from the Roadllsage area, the associated RoadUserSafety information as described with reference to Figure 2. Using this field, the receiving ITS-S may determine a danger level if a DangerLevel information is present. From the danger level, the receiving ITS-S S determines that its trajectory will create a safety risk if DangerLevel is greater than 0. Using the RoadUserSafety information field, the receiving ITS-S may determine the ControllabilityClass associated with the RoadUsage area, if ControllabilityClass information is present. From the controllability class, if DangerLevel is different than CO, the receiving ITS-S may determine that its trajectory will create a safety risk. Accordingly, the receiving ITS-S may, in step 520, adapt its trajectory to reduce the overlapping portions previously determined, adapt its trajectory if there is a safety risk, - take into account multiple RoadUsage Containers containing multiple RoadUsageArea, and / or adapt its trajectory by reducing its speed, by accelerating or stopping. Figure 6 illustrates a use case according to some embodiments of the present disclosure, according to which a vehicle is using an adaptive cruise control system and disseminates a RoadUsage Container to indicate, in CAMs, to other ITS-Ss, the set distance. Considering the road situation 600, the vehicle located at position 605, being an originating IT-S, and the vehicle located at position 610, being a receiving ITS-S, are able to receive and transmit CAMs as described with reference to Figure 1. According to some embodiments of the disclosure, the vehicle located at position 605 executes an algorithm such as the one described with reference to Figure 5 and the vehicle located at position 610 executes an algorithm such as the one described with reference to Figure 5. Accordingly, the vehicle located at position 605 disseminates CAMs comprising a RoadUsage Container having a single Roadllsage area associated with a Roadllsage type. According to the illustrated example, the Roadllsage area 620 is the rectangle aligned with the heading of the vehicle located at position 605. For the sake of illustration, the rectangle width is equal to the vehicle width and the rectangle length corresponds to the setting programmed by the driver ‘set distance’, for example 100 meters. Roadllsage type is equal ‘adaptive cruise control’. By receiving, the previous Roadllsage Container, the vehicle located at position 610 can adapt its trajectory 615 without cut-in Roadllsage area 620. Figure 7 illustrates a use case according to some embodiments of the present disclosure, according to which a VRU disseminates a Roadllsage Container to indicate, in VAMs, to other ITS, a safety area. Considering the road situation 700, the vehicle located at position 705, being an originating IT-S, and the VRU located at position 710, being a receiving ITS-S, are able respectively to receive and transmit VAM, as described with reference to Figure 1. According to some embodiments of the disclosure, the VRU located at position 710 executes an algorithm such as the one described with reference to Figure 4 and the vehicle located at position 705 executes an algorithm such as the one described with reference to Figure 5. Therefore, the VRU located at position 710 disseminates VAMs including a RoadUsage Container with a single RoadUsage area 720 associated with a RoadUsage type. The RoadUsage area can be defined as distances referenced from a bounding box of the VRU located at position 710. For example, the distances can be the recommend values defined as the minimum safe lateral distance (MSLaD) laterally, and the minimum safe longitudinal distance (MSLoD) longitudinally and the minimum safe vertical distance (MSVD) vertically as specified with the minimum safe distance condition in clause 6.5.10.5 of ETSI TS 103 300-2. The RoadUsageType is equal to ‘safety distance’. Additionally, the RoadUsageSafety can be defined as ControllabilityClass equals to C5 or DangerLevel equals to 5 because it concerns a Vulnerable Road User. By receiving the previous RoadUsage Container, the vehicle located at position 705 can adapt its trajectory 715 without cut-in RoadUsage area 720. Figure 8 illustrates a use case according to some embodiments of the present disclosure, according to which a vehicle is using an assist parking system and disseminates a Road Usage Container to indicate, in CAMs, to other ITS, the required area for its maneuver. Considering the road situation 800, the vehicle 801, at time TO, T1, T2, and T3, being an originating IT-S, and the vehicle 802, at time TO, T1, T2, T3, and T4 being a receiving ITS-S, are able to receive and transmit CAMs as described by reference to Figure 1. Likewise, the vehicle 806, at time T4, being a receiving ITS-S, is able to receive and transmit CAMs as described by reference to Figure 1. According to some embodiments of the disclosure, vehicle 802 executes an algorithm like the one described by reference to Figure 4 and vehicles 801 and 806 execute an algorithm like the one described by reference to Figure 5. It is assumed that at time TO, vehicle 802 is using an assisted system to perform a parking maneuver targeting the free place referenced 810. The other neighboring places are occupied by different vehicles generically referenced 820. At time TO, vehicle 802 generates a CAM message including a RoadUsage Container with a RoadUsage area corresponding to the overall area required to execute the parking maneuver until reaching the situation at T3 where vehicle 802 is over the previous free place 810 at TO. The RoadUsage Container with this RoadUsage area contains a RoadUsage type set to ‘parking’. At time TO, the RoadUsage area is defined with polygon 803a referenced from the Referenceposition of vehicle 802 (at time TO). Therefore, at time TO, vehicle 802 generates a CAM including a RoadUsage Container with the RoadUsage area 803a and an associated RoadUsage type set to ‘parking’. Next, at time T1, the RoadUsage area is modified. It is defined with polygon 803b referenced from the Referenceposition of vehicle 802 (at time T1). Accordingly, at time T1, vehicle 802 generates a CAM including a RoadUsage Container with the updated RoadUsage area 803b and an associated RoadUsage type set to ‘parking’. Next, at time T2, the RoadUsage area is modified again. It is defined with polygon 803c referenced from the Referenceposition of vehicle 802 (at time T2). Accordingly, at time T2, vehicle 802 generates a CAM including a RoadUsage Container with the updated RoadUsage area 803c and an associated RoadUsage type set to ‘parking’. Next, at time T3, vehicle 802 has completed its maneuver using the assisted system. There is no longer need for a RoadUsage area. Therefore, vehicle 802 does not include any including RoadUsage Container in the CAMs it generates. Next, at time T4, an occupant opens a door of vehicle 802 on the street side. Accordingly, vehicle 802 determines a new RoadUsage area, referenced 804, that is required to protect the appearing pedestrian referenced 805. Roadllsage area 804 may be defined with a rectangle around the vehicle 802. The associated Roadllsage type may be set to ‘safety’. Accordingly, at time T4, vehicle 802 generates a CAM including a Roadllsage Container with the updated Roadllsage area 804 and an associated Roadllsage type set to ‘safety’. This CAM may be used, in particular, by vehicle 806. According to some embodiments, vehicle 802 transmits the corresponding Roadllsage Container in VAMs as long as pedestrian 805 is near vehicle 802. Alternately, pedestrian 805 may generate VAMs including a Roadllsage Container with the previous Roadllsage area 804 being defined as a rectangle around pedestrian 805. The associated Roadllsage type may still be set to ‘safety’. Vehicle 801 may use an algorithm like the one described by reference to Figure 5 in order to prevent itself for overlapping the different Roadllsage areas 803a, 803b, and 803c from time TO to time T2. Vehicle 801 stops itself so that vehicle 802 may execute safely its assisted maneuver, without conflicting with vehicle 801. At time T3, vehicle 801 may restart since it is no longer stopped by the previous Roadllsage areas. Similarly, vehicle 806 may use an algorithm like the one described by reference to Figure 5 to be aware of the Roadllsage areas transmitted by other ITS-Ss, in particular of Roadllsage area 804 of the ‘safety’ type (that may be transmitted either from vehicle 802 in CAMs or from pedestrian 805 in VAMs). Accordingly, vehicle 806 stops itself until pedestrian 805 left the Roadllsage area 804. Figure 9 illustrates examples of Road Usage areas defined either by using distances, vectors, rectangles, polygons, ellipses, or road sections according to some embodiments of the present disclosure. As illustrated, vehicle 901 may define a RoadUsage area 911 in a RoadUsage Container using a rectangle defined by 4 points having coordinates that are relative to the Referenceposition of vehicle 901. Similarly, vehicle 902 may define successive RoadUsage areas 912, 922, and 932 in a same RoadUsage Container using different rectangles defined by 4 points having coordinates that are relative to the Referenceposition of vehicle 902. Each of the RoadUsage areas 912, 922, and 932 may correspond to different safety levels. Still for the sake of illustration, vehicle 903 defines a RoadUsage area 913 in a Roadllsage Container using a single distance from the Referenceposition of vehicle 903, that is aligned with the heading of the vehicle. Likewise, vehicle 904 defines successive Roadllsage areas 912, 922, and 932 in the same Roadllsage Container, using successive distances, starting from the Referenceposition of vehicle 904. Still for the sake of illustration, vehicle 905 defines a Roadllsage area 915 in a Roadllsage Container, using a single polar vector starting from the Referenceposition of vehicle 903, that is referenced from the heading of vehicle 903. Likewise, vehicle 906 defines successive RoadUsage areas 1016, 1026, and 1036 in the same RoadUsage Container, using successive polar vectors starting from the Referenceposition of vehicle 906, that is referenced from the heading of vehicle 906. Still for the sake of illustration, vehicle 907 defines a RoadUsage area 907 in a RoadUsage Container, using a polygon having coordinates relative to the Referenceposition of vehicle 907, and vehicle 908 defines a RoadUsage area 913 in a RoadUsage Container, using an ellipsoid having coordinate relative to the Referenceposition of vehicle 908. Figure 10 illustrates examples of RoadUsage areas defined using road sections. According to some embodiments of the disclosure, RoadUsage areas are defined as a function of successive road sections determined according to a road representation and as a function of lanes per road section. Therefore, a RoadUsage area may be defined using a list of one or more successive road sections and a list of one or more lanes per section, according to a road representation, with preferably a first distance indicating the start of the RoadUsage area according to the first section in the list and / or a second distance indicating the end of the RoadUsage area according to the last section of the list. Considering the road situation referenced 1000 in Figure 10, vehicle 1001 is present in lane 1 of section 1 (this item of information may be disseminated in CAMs using LanePosition using the High-Frequency Container). For the sake of illustration, vehicle 1001 may define RoadUsage area 1002 in a RoadUsage Container, using a list containing (Sectionl, lanel, distance D1), (Sections, lanel), (Section 4, lane 2, distance D2). As specified in ‘ETSI TS 103 900 V0.0.4_2.1.1 (2023-03)’, Cooperative Awareness Messages (CAMs) are messages exchanged in the ITS network between ITS-Ss to create and maintain awareness of each other and to support cooperative performance of vehicles using the road network. A CAM contains status and attribute information of the originating ITS-S. The content varies depending on the type of the ITS-S. For vehicle ITS-Ss the status information includes time, position, motion state, activated systems, etc. and the attribute information includes data about the dimensions, vehicle type and role in the road traffic. On reception of a CAM, the receiving ITS-S becomes aware of the presence, type, and status of the originating ITS-S. The received information can be used by the receiving ITS-S to support several ITS applications. For example, by comparing the status of the originating ITS-S with its own status, a receiving ITS-S is able to estimate the collision risk with the originating ITS-S and if necessary, may inform the driver of the vehicle via the in-vehicle system. Even if a connected vehicle is able to determine and predict the near future movement of other vehicles by receiving CAMs, this prediction is limited by the lack of knowledge on vehicle properties such as breaking distance, active adaptative control system or safety systems and driving conditions. For example, a connected vehicle may use an adaptative cruise control system which properties are changing according to the road conditions (weather, light conditions, road type and traffic, vehicle speed, user preferences). For example, a connected vehicle may use an automatic driving mode relying on monitored fields (warning, protective) in its surroundings to maintain its safety conditions. Those properties are unknown by other connected vehicles and difficult to estimate by their nature. Consequently, another connected vehicle is not able to determine how its driving may impact the previous vehicle driving. It may result in various effects such as triggering an adaptative system, gently breaking or entering in safety issue (collision, automatic braking, non-respect of safety distance). According to the disclosure, it is proposed to solve this issue by adding information in the CAMs to make it possible to disseminate the road usage area required by the vehicle to maintain its driving in nominal conditions. In the example illustrated in Figure 11, the car is having the priority and would like to turn on its right. According to the road rule ‘Priority on the right’, the bus shall stop and let the car turns. Even by knowing the bus dynamics by receiving CAMs from the bus, the car is not able to determine if the bus is able to safely break. To solve this issue, the bus can disseminate its brake distance using CAMs. By receiving this status information over CAMs, the car is able to determine if it can safely turn and adapt its dynamics to maintain a safe distance with the bus, as illustrated in Figure 12. As illustrated, several road usage areas may be defined, for example a first area corresponding to a distance from the bus wherein a collision cannot be avoided, a second area corresponding to the distance needed for stopping the bus using an autobraking system, and a third area corresponding to the distance for stopping the bus in case of a normal breaking. As can be seen, since it exists a margin between the stop position of the bus (while considering a normal breaking) and the position of the car, the latter may decide to turn, without letting the bus pass. In the example illustrated in Figure 6, an adaptive cruise control is used by a car. The adaptive cruise control permits to maintain a safe distance with other cars. This kind of system has some limitations in close cut-in scenario and it may not assist. This car disseminates using CAMs the area corresponding to the distance set for the adaptative cruise control to maintain a safe distance with other cars. By receiving CAMs, the other car is informed of the road usage by the other car and prevents itself from cut-in it before it overtakes the area. It permits to keep safe distance and a fluent road traffic. Accordingly, it is proposed to add a container named ‘RoadllsageContainer’ including: RoadllsageArea: A distance, an area, a polygon or a vector. It’s Referred to the Referenceposition. RoadllsageType o it is used to define the corresponding road usage of the area ■ collision ■ auto-braking ■ assist braking ■ safety distance ■ protective or warning field ■ comfort or economic mode (smooth drive) ■ maneuver on-going ■ emergency requirement ■ parking ■ pedestrian exits from vehicle ■ other RoadUsageSafety: It’s used to indicate the danger level and / or the controllability class. It may be used by an ITS to assess the risk in case of presence in the road usage area. It may include: o Controllabilityclassification: it is used to define the controllability class (ASIL) of the vehicle if a hazardous event occurs in the RoadllsageArea: ■ CO Controllable in general ■ C1 Simply controllable ■ C2 Normally controllable (most drivers could act to prevent injury) ■ C3 Difficult to control or uncontrollable o DangerLevel: it is used to define the danger level for the car occupancy and / or any other vehicle in case of collision in RoadllsageArea ■ Level 4 High danger ■ Level 3 Considerable danger ■ Level 2 Moderate danger ■ Level 1 No or minor danger Example of a hardware to carry out steps of the method of embodiments of the present disclosure Figure 9 is a schematic representation of an example of a communication ITS-S device configured to implement some embodiments of the present disclosure. It may be either an ITS-S embedded in a vehicle or in a unit such as a mobile phone of a Vulnerable Road User, for example unit in vehicles 130,140 or held by Vulnerable Road Users 150,160 in Figure 1. The communication device 1300 may preferably be a device such as a microcomputer, a workstation or a light portable device embedded in a vehicle. The communication device 1300 comprises a communication bus 1313 to which there are preferably connected: a central processing unit 1311, such as a microprocessor, denoted CPU or a GPU (for graphical processing unit); a read-only memory 1307, denoted ROM, for storing computer programs for implementing some embodiments of the disclosure; a random access memory 1312, denoted RAM, for storing the executable code of methods according to embodiments of the disclosure as well as the registers adapted to record variables and parameters necessary for implementing methods according to embodiments of the disclosure; and at least one communication interface 1302 connected to the radio communication network over which ITS messages are transmitted. The ITS messages are written from a FIFO sending memory in RAM 1312 to the network interface for transmission or are read from the network interface for reception and writing into a FIFO receiving memory in RAM 1312 under the control of a software application running in the CPU 1311. Optionally, the communication device 1300 may also include the following components: a data storage means 1304 such as a hard disk, for storing computer programs for implementing methods according to one or more embodiments of the disclosure; a disk drive 1305 for a disk 1306, the disk drive being adapted to read data from the disk 1306 or to write data onto said disk; a screen 1309 for serving as a graphical interface with the user, by means of a keyboard 1310 or any other pointing means. The communication device 1300 may be optionally connected to various peripherals including perception sensors 1308, such as for example a digital camera, each being connected to an input / output card (not shown) so as to supply data to the communication device 1300. Preferably the communication bus provides communication and interoperability between the various elements included in the communication device 1300 or connected to it. The representation of the bus is not limiting and in particular the central processing unit is operable to communicate instructions to any element of the communication device 1300 directly or by means of another element of the communication device 1300. The disk 1306 may optionally be replaced by any information medium such as for example a compact disk (CD-ROM), rewritable or not, a ZIP disk, a USB key ora memory card and, in general terms, by an information storage means that can be read by a microcomputer or by a microprocessor, integrated or not into the apparatus, possibly removable and adapted to store one or more programs whose execution enables a method according to the disclosure to be implemented. The executable code may optionally be stored either in read-only memory 1307, on the hard disk 1304 or on a removable digital medium such as for example a disk 1306 as described previously. According to an optional variant, the executable code of the programs can be received by means of the communication network, via the interface 1302, in order to be stored in one of the storage means of the communication device 1300, such as the hard disk 1304, before being executed. The central processing unit 1311 is preferably adapted to control and direct the execution of the instructions or portions of software code of the program or programs according to the disclosure, which instructions are stored in one of the aforementioned storage means. On powering up, the program or programs that are stored in a nonvolatile memory, for example on the hard disk 1304 or in the read-only memory 1307, are transferred into the random access memory 1312, which then contains the executable code of the program or programs, as well as registers for storing the variables and parameters necessary for implementing the disclosure. In a preferred embodiment, the apparatus is a programmable apparatus which uses software to implement the disclosure. However, alternatively, the present disclosure may be implemented in hardware (for example, in the form of an Application Specific Integrated Circuit or ASIC). Although the present disclosure has been described herein above with reference to specific embodiments, the present disclosure is not limited to the specific embodiments, and modifications will be apparent to a skilled person in the art which lie within the scope of the present disclosure. Many further modifications and variations will suggest themselves to those versed in the art upon referring to the foregoing illustrative embodiments, which are given by way of example only and which are not intended to limit the scope of the disclosure, that being determined solely by the appended claims. In particular, the different features from different embodiments may be interchanged, where appropriate. Each of the embodiments of the disclosure described above can be implemented solely or as a combination of a plurality of the embodiments. Also, features from different embodiments can be combined where necessary or where the combination of elements or features from individual embodiments in a single embodiment is beneficial. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be advantageously used.
Claims
1. A method of communication in an Intelligent Transport System, ITS, the method comprising, at a transmitting ITS station:determining at least one road usage area that the transmitting ITS station, an object, or a person associated with the transmitting ITS station may possibly use; and transmitting an ITS message comprising an item of information indicating the at least one road usage area.
2. The method of claim 1, wherein the road usage area is an area to be traversed by the transmitting ITS station within a given time period.
3. The method of claim 1 or claim 2, further comprising determining a road usage type associated with the at least one road usage area and transmitting an item of information indicating the road usage type.
4. The method of any one of claims 1 to 3, further comprising determining a road usage safety indication associated with the at least one road usage area and transmitting an item of information indicating the road usage safety indication.
5. The method of any one of claims 1 to 4, wherein the at least one road usage area is defined with a distance, a vector, a polygon, and / or an ellipse.
6. The method of any one of claims 1 to 4, wherein the at least one road usage area extends over at least two adjacent lane sections of a road.
7. The method of any one of claims 1 to 4, wherein the at least one road usage area extends over two lane sections belonging to two intersected roads.
8. The method of any one of claims 1 to 7, further comprising obtaining road usage needs, the at least one road usage area being determined as a function of the obtained road usage needs.
9. The method of any one of claims 1 to 8, wherein the item of information indicating the at least one road usage area is transmitted in at least one RoadUsage Container of a Cooperative Awareness Message, CAM, or of a Vulnerable Road Users Awareness Message, VAM.
10. The method of claim 9, further comprising generating the at least one RoadUsage Container, the generated at least one RoadUsage Container belonging to a High-Frequency Container or to a Low-Frequency Container.
11. A method of communication in an Intelligent Transport System, ITS, the method comprising, at a receiving ITS station:receiving, from a transmitting ITS station, an ITS message comprising an item of information indicating at least one road usage area; anddetermining, from the received ITS message, at least one road usage area that the transmitting ITS station, an object, or a person associated with the transmitting ITS station may possibly use.
12. The method of claim 11, wherein the road usage area is an area to be traversed by the transmitting ITS station within a given time period.
13. The method of claim 11 or claim 12, further comprising determining, from the received ITS message, a road usage type associated with the at least one road usage area.
14. The method of any one of claims 11 to 13, further comprising determining, from the received ITS message, a road usage safety indication associated with the at least one road usage area.
15. The method of any one of claims 11 to 14, further comprising determining whether the at least one road usage area overlaps a predicted path of the receiving ITS station.
16. The method of claim 15, depending on claim 14, further comprising, in case the at least one road usage area overlaps the predicted path of the receiving ITS station, evaluating effects of the overlap.
17. The method of claim 16, further comprising adapting parameters of the receiving ITS station as a function of the evaluated effects.
18. The method of any one of claims 11 to 17, wherein the received ITS message is a Cooperative Awareness Message, CAM, or a Vulnerable Road Users Awareness Message, VAM.
19. The method of claim 18, wherein the received ITS message comprises at least one RoadUsage Container, the at least one RoadUsage Container comprising at least one High-Frequency Container and / or at least one Low-Frequency Container, the at least one High-Frequency Container and / or the at least one Low-Frequency Container comprising a RoadUsage Container comprising the item of information indicating the at least one road usage area.
20. A computer program product for a programmable apparatus, the computer program product comprising a sequence of instructions for implementing each of the steps of the method according to any one of claims 1 to 19 when loaded into and executed by the programmable apparatus.
21. A non-transitory computer-readable storage medium storing instructions of a computer program for implementing each of the steps of the method according to any one of claims 1 to 19.
22. A device for an Intelligent Transport System, ITS, station, the device comprising a processing unit configured for carrying out each of the steps of the method according to any one of claims 1 to 19.
Citation Information
Patent Citations
Method of determining moving path based on predictive path and mobile its station therefor
US20210270615A1
System and method for vehicle-to-everything (V2X) collaborative perception
US20230059897A1
Controlling v2x message distribution
WO2021223866A1
Intelligent transport system service dissemination
WO2021226062A1
Method of coordinating a maneuver among vehicles
WO2022043099A1
