Document Information - Connected Motorcycle Consortium · 2020. 12. 6. · CMC Basic Specification...

Application Specification

CMC Basic Specification 1

Document Information

Document Title: Application Specification

Chapter: Hazardous Location Notification (HLN)

Version: 1.0

Release Date: 11/12/2020

Disclaimer

This document has been developed within the Connected Motorcycle Consortium and might be further

elaborated within the consortium. The Connected Motorcycle Consortium and its members accept no

liability for any use of this document and other documents from the consortium.

Copyright Notification: No part may be reproduced except as authorized by written prior permission. The

copyright and the foregoing restriction extend to reproduction in all media. © 2020, Connected

Motorcycle Consortium.



4.2 Hazardous Location Notification (HLN)

4.2.1 General description

The Hazardous Location Notification (HLN) application uses Vehicle-to-Infrastructure (V2I) and

Vehicle-to-Vehicle (V2V) communication to inform PTW riders of a series of potentially

hazardous events on the road. Its hazardous information is detected and set by the road

operator and broadcast to the surroundings using infrastructures such as Road Side Unit

(RSU). If the rider is approaching a dangerous situation or spot, its notifications should be

provided automatically by the HMI on time to inform a potential hazard.

4.2.2 Use case description1

This C-ITS service informs a V2I warning message related to a series of potentially hazardous

events on the road and provides information about the event to the approaching PTW rider. If

more detailed information is available, the location, type of the hazard, and the duration of the

event will be informed to the rider.

4.2.2.1 Scenario description: PTW receive DENM

The events and the Use Cases of HLN: PTW receive DENM can be the following:

Accident Zone (HLN–AZ)

Traffic Jam Ahead (HLN–TJA)

Stationary Vehicle (HLN–SV)

Weather Condition Warning (HLN–WCW)

Temporarily Slippery Road (HLN–TSR)

Animal or Person on the Road (HLN–APR)

Obstacle on the Road (HLN–OR)

Emergency Vehicle Approaching (HLN–EVA)

Emergency Vehicle in Intervention (HLN–EVI)

Rail Level Crossing (HLN–RLX)

Unsecured Blockage of a Road (HLN–UBR)

Alert Wrong Way Driving (HLN–AWWD)

Public Transport Vehicle Crossing (HLN–PTVC)

Public Transport Vehicle at a Stop (HLN–PTVS)

1 Common C-ITS Service Definitions Version 1.6 from C-Roads

(https://www.c-roads.eu/platform/about/news/News/entry/show/release-16-of-c-roads-harmonised-c-its-specifications.html),

“accessed 13.11.2020”.

https://www.c-roads.eu/platform/about/news/News/entry/show/release-16-of-c-roads-harmonised-c-its-specifications.html



4.2.2.1.1 Accident Zone (HLN-AZ)

HLN-AZ is one of the use cases to inform the road users of accidents that happened on the

road network. When the road operator detects the accident on the road network, the Traffic

Control Centre (TCC) shall broadcast the information about the accident zone as DENM to the

surroundings by using infrastructure such as RSU. If the PTW receives the above message,

the C-ITS system on the PTW calculates the potential risk of the event, and if necessary,

forwards the information about the event to the rider in order to adapt the riding behaviour and

reduce the risk.

© This picture was created using the C2C-CC Illustration Toolkit, owned by the CAR 2 CAR Communication Consortium

Figure 1: Overview of HLN-AZ



4.2.2.1.2 Traffic Jam Ahead (HLN-TJA)

HLN-TJA is one of the use cases to inform the road user of traffic jam situations on the

motorway. When the road operator detects a traffic jam on the road network, the TCC shall

broadcast the TJA warning as DENM to the surroundings by using infrastructure such as RSU.

If the PTW receives the above message with one message ID through various channels of

information from other vehicles and/or the TCC, the C-ITS system on the PTW calculates the

potential risk of the traffic jam using the ego vehicle data with the position of the traffic jam, the

length of traffic jam, and the section/lanes if the information is available. And the information

about the traffic jam will be informed to the rider in order to adapt the riding behaviour and

reduce the risk.


Figure 2: Overview of HLN-TJA



4.2.2.1.3 Stationary Vehicle (HLN–SV)

HLN-SV is one of the use cases to inform the road user of stationary/broken down vehicles as

information of the obstacles ahead on the motor way lane. When the road operator having an

event management system detects slowly moving or broken down vehicles on the motorway,

the TCC shall broadcast SV warning as DENM to nearby vehicles by using infrastructure such

as RSU. If the PTW receives the above message with one message ID through various

channels of information from other vehicles and/or the TCC, the C-ITS system on the PTW

calculates the potential risk of the collision with the vehicles, and if necessary, forwards the

information about the event to the rider in order to adapt the riding behaviour and reduce the

risk.


Figure 3: Overview of HLN-SV



4.2.2.1.4 Weather Condition Warning (HLN–WCW)

HLN-WCW is one of the use cases to inform the road user of both static and dynamic

information of dangerous weather conditions and road status. When the road operator gets

informed about extreme weather conditions from the weather information provider, the TCC

shall broadcast the Weather Condition Warning as DENM to the surroundings by different

communication channels. If the PTW receives the above message, the C-ITS system on the

PTW calculates the potential risk of the event and forwards the information of the weather

conditions to the rider in order to adapt the riding behaviour and reduce the risk.


Figure 4: Overview of HLN-WCW



4.2.2.1.5 Temporarily Slippery Road (HLN–TSR)

HLN-TSR is one of the use cases to inform the road user of a road condition that is

temporarily slippery on the road network. When the road operator gets informed about a

section that is slippery on the road network, the TCC shall broadcast the TSR warning as

DENM to the surroundings by using infrastructure such as RSU. If the PTW receives the

above message with one message ID through various channels of information from TCC

and/or other vehicles, the C-ITS system on the PTW calculates the potential risk of the event,

and if necessary, forwards the information of the slippery road to the rider in order to adapt

the riding behaviour and reduce the risk.


Figure 5: Overview of HLN-TSR



4.2.2.1.6 Animal or Person on the Road (HLN–APR)

HLN-APR is one of the use cases to inform the road user of the presence of animals or persons

on the road network. When the road operator gets informed about the presence of animals or

persons on the road network, the TCC shall broadcast the APR warning as DENM to the

surroundings by using infrastructure such as RSU. If the PTW receives the above message,

the C-ITS system on the PTW calculates the potential risk of the collision with the animals or

persons, and if necessary, forwards the information of them to the rider in order to adapt the

riding behavior and reduce the risk.


Figure 6: Overview of HLN-APR



4.2.2.1.7 Obstacles on the road (HLN–OR)

HLN-OR is one of the use cases to inform the road user of the obstacles on one or several

lanes on the road network. When the road operator gets informed about the presence of

obstacles on the road network, the TCC shall broadcast the OR warning as DENM to the

surroundings by using infrastructure such as RSU. If the PTW receives the above message

from TCC and/or other vehicles, the C-ITS system on the PTW calculates the potential risk of

the collision with the obstacles, and if necessary, forwards the information of the obstacles to

the rider in order to adapt the riding behaviour and reduce the risk.


Figure 7: Overview of HLN-OR



4.2.2.1.8 Emergency Vehicle Approaching (HLN–EVA)

HLN-EVA has the same use case as AEVW, and doesn't broadcast the V2I messages from

infrastructures. (Please refer to the “4.3 - AEVW - Use Case Description & Technical

Description”)



4.2.2.1.9 Emergency Vehicle in Intervention (HLN–EVI)

HLN-EVI is one of the use cases to inform the road user of the location of an emergency

vehicle in intervention (e.g. a traffic accident, rescue, and recovery work) on the road network.

When the road operator gets informed about the emergency vehicle intervention on the road

network, the TCC shall broadcast the EVI warning as DENM to the road users approaching

the respective segments involved by using infrastructure such as RSU. If the PTW receives

the above message from the TCC and/or the emergency vehicle, the C-ITS system on the

PTW calculates the potential risk of the collision with the emergency vehicle, and if necessary,

forwards the information of that to the rider in order to adapt the riding behaviour and reduce

the risk.


Figure 8: Overview of HLN-EVI



4.2.2.1.10 Railway Level Crossing (HLN–RLX)

HLN-RLX is one of the use cases to inform the road user of the presence of a railway level

crossing and its type/parameters/status. When the train approaches the level crossing, C-ITS

system on the level crossing shall automatically and continuously broadcast the RLX warning

about the warning state active at the crossing, including optional information with one message

ID, to the road users. If the PTW receives the above message, the C-ITS system on the PTW

calculates the potential risk of the collision with the approaching train at the crossing, and if

necessary, forwards the information of that to the rider in order to adapt the riding behaviour

and reduce the risk.


Figure 9: Overview of HLN-RLX



4.2.2.1.11 Unsecured Blockage of a Road (HLN–UBR)

HLN-UBR is one of the use cases to inform the road user of a complete blockage of a road

where it is not allowed to go through the road segment. When the road operator gets

informed about a section of road that is blocked on the road network, the TCC shall

broadcast the information to road users by using infrastructure such as RSU. If the PTW

receives the above message, the C-ITS system on the PTW calculates the potential risk of

the hazard with the blockage of the road, and if necessary, forwards the information of that to

the rider in order to adapt the riding behaviour and reduce the risk.


Figure 10: Overview of HLN-UBR



4.2.2.1.12 Alert Wrong Way Driving (HLN–AWWD)

HLN-AWWD is one of the use cases to inform the road user of encountering a vehicle that is

driving in the wrong way on a road with separate carriageways or motorways. When the road

operator gets informed about the presence of a wrong way driving vehicle on the road

network, the TCC shall broadcast the information of it for the relevant road segment for both

directions on the road. And then, the detailed information of the vehicle, including driving

position, speed, heading, and driving lane, shall be confirmed by the road operator in the

Traffic Management Centre and broadcast the details as updated information to the rider. If

the PTW receives the above message, the C-ITS system on the PTW calculates the potential

risk of the collision with the wrong way driving vehicle, and if necessary, forwards the

information of that to the rider in order to adapt the riding behaviour and reduce the risk.


Figure 11: Overview of HLN-AWWD



4.2.2.1.13 Public Transport Vehicle Crossing (HLN–PTVC)

HLN-PTVC is one of the use cases to inform the road user of a high risk of collision with

public transport vehicles crossing on the urban road. When the public transport vehicle

enters a defined trigger area of a dangerous location, the C-ITS system on the public

transport vehicle shall broadcast the PTVC warning about the presence of the vehicle to the

surroundings. If the PTW receives the above message, the C-ITS system on the PTW

calculates the potential risk of the collision with the public transport vehicle, and if necessary,

forwards the information of that to the rider in order to adapt the riding behavior and reduce

the risk.


Figure 12: Overview of HLN-PTVC



4.2.2.1.14 Public Transport Vehicle at a stop (HLN–PTVS)

HLN-PTVC is one of the use cases to inform the road user of a high risk of collision with public

transport vehicles halting at a stop. When the public transport vehicle halting at a stop, the C-

ITS system on the public transport vehicle shall broadcast the PTVS warning about the

presence of the vehicle to the surroundings. If the PTW receives the above message, the C-

ITS system on the PTW calculates the potential risk of the collision with the public transport

vehicle, and if necessary, forwards the information of that to the rider in order to adapt the

riding behaviour and reduce the risk.


Figure 13: Overview of HLN-PTVS



4.2.3 Technical description

4.2.3.1 PTW receive DENM

4.2.3.1.1 Accident Zone (HLN-AZ)

4.2.3.1.1.1 State flow

The function state flow from Service-In to Service-Out is indicated in the following figure.

Figure 14: State Flow of HLN-AZ



4.2.3.1.1.2 Preconditions

The preconditions of HLN-AZ are stated below.

All of the following preconditions (PC_1 to PC_8) shall be satisfied every time before this use

case is activated:

Table 1: Preconditions of ego vehicle (HLN-AZ)

# Item Condition

PC_1 Ego vehicle PTW

PC_2 Speed range > 5 km/h

PC_3 Location -

PC_4 Road type -

PC_5 Time -

PC_6 Weather -

PC_7 Other conditions -

PC_8 Out of scope -

All of the preconditions of target (PC_9 to PC_12) shall be satisfied before active and

deactivate condition check.

Table 2: Preconditions of target (HLN-AZ)

# Item Condition

PC_9 Target NA

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 2 (accident)

PC_12 subCauseCode between 0 and 7 except 6 (vehicle; which is implicit for

an accident)



4.2.3.1.1.3 Activation and deactivation requirements

The activating and deactivating warning requirements of HLN-AZ are stated below.

Activate the warning scheme when all of the conditions below are (AC_1 to AC_3) satisfied:

Table 3: Activating conditions (HLN-AZ)

# Item Condition Used data

AC_1 Target Relative DENM received (HLN-

AZ)

Target signal cause

(causeCode and

subCauseCode)

AC_2 Event position On the route of ego vehicle eventPosition

pathHistory

AC_3 TTC To set the adequate time that is

not too early and late to adapt the

rider's behaviour.

eventPosition

Deactivate the warning when at least one of the conditions below (DC_1 OR DC_2) is satisfied.

Table 4: Deactivating conditions (HLN-AZ)


DC_1 Event position Passed the location of the

event.

eventPosition

DC_2 Receive

cancellation

DENM

Cancellation DENM received

(HLN-AZ)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.2 Traffic Jam Ahead (HLN–TJA)


Please refer to the “4.7 - TJW - Use Case Description & Technical Description”.







4.2.3.1.3 Stationary Vehicle (HLN–SV)


Please refer to the “4.6 - SVW - Use Case Description & Technical Description”.







4.2.3.1.4 Weather Condition Warning (HLN–WCW)


Please refer to the “4.4 - AWW - Use Case Description & Technical Description”.







4.2.3.1.5 Temporarily Slippery Road (HLN–TSR)









4.2.3.1.6 Animal or Person on the Road (HLN–APR)


The state machine diagram as state flow from Service-In to Service-Out is same as one

described in HLN-AZ (4.2.3.1.1.1).


The preconditions of HLN-APR are stated below.


case is activated:

Table 5: Preconditions of ego vehicle (HLN-APR)

# Item Condition



PC_3 Location -

PC_4 Road type -

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 6: Preconditions of target (HLN-APR)

# Item Condition

PC_9 Target NA

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 11 (animal on the road) or 12 (human presence on the

road)

PC_12 subCauseCode 0, 2, 4 in causeCode 11 (animal on the road)

0-2 in causeCode 12 (human presence on the road)




The activating and deactivating warning requirements of HLN-APR are stated below.


Table 7: Activating conditions (HLN-APR)



AZ)

Target signal cause

(causeCode and

subCauseCode)


pathHistory


not too early and late to adapt

the rider's behaviour.

eventPosition


Table 8: Deactivating conditions (HLN-APR)


DC_1 Event position Passed the location of the

event.

eventPosition

DC_2 Receive

cancellation DENM


(HLN-APR)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.7 Obstacle on the Road (HLN–OR)





The preconditions of HLN-OR are stated below.


case is activated:

Table 9: Preconditions of ego vehicle (HLN-OR)

# Item Condition



PC_3 Location -

PC_4 Road type -

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 10: Preconditions of target (HLN-OR)

# Item Condition

PC_9 Target NA

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 10 (obstacle on the road)

PC_12 subCauseCode 0-5




The activating and deactivating warning requirements of HLN-OR are stated below.


Table 11: Activating conditions (HLN-OR)



OR)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 12: Deactivating conditions (HLN-OR)


DC_1 Event position Passed the location of the event. eventPosition

DC_2 Receive

cancellation

DENM


(HLN-OR)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.8 Emergency Vehicle Approaching (HLN–EVA)


Please refer to the “4.3 - AEVW - Use Case Description & Technical Description”.







4.2.3.1.9 Emergency Vehicle in Intervention (HLN–EVI)









4.2.3.1.10 Railway Level Crossing (HLN–RLX)

4.2.3.1.10.1 State flow




The preconditions of HLN-RLX are stated below.


case is activated:

Table 13: Preconditions of ego vehicle (HLN-RLX)

# Item Condition



PC_3 Location -

PC_4 Road type -

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 14: Preconditions of target (HLN-RLX)

# Item Condition

PC_9 Target Railway level crossing

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 97 (collision risk)

PC_12 subCauseCode 2 (crossing collision risk)




The activating and deactivating warning requirements of HLN-RLX are stated below.


Table 15: Activating conditions (HLN-RLX)



RLX)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 16: Deactivating conditions (HLN-RLX)



DC_2 Receive

cancellation

DENM


(HLN-RLX)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.11 Unsecured Blockage of a Road (HLN–UBR)

4.2.3.1.11.1 State flow




The preconditions of HLN-UBR are stated below.


case is activated:

Table 17: Preconditions of ego vehicle (HLN-UBR)

# Item Condition



PC_3 Location -

PC_4 Road type -

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 18: Preconditions of target (HLN-UBR)

# Item Condition

PC_9 Target NA

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 10 (Hazardous location - Obstacle on the road)

PC_12 subCauseCode 7 (waiting vehicles)




The activating and deactivating warning requirements of HLN-UBR are stated below.


Table 19: Activating conditions (HLN-UBR)



UBR)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 20: Deactivating conditions (HLN-UBR)



DC_2 Receive

cancellation

DENM


(HLN-UBR)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.12 Alert Wrong Way Driving (HLN–AWWD)

4.2.3.1.12.1 State flow




The preconditions of HLN-AWWD are stated below.


case is activated:

Table 21: Preconditions of ego vehicle (HLN-AWWD)

# Item Condition



PC_3 Location -

PC_4 Road type Road with separate carriageways (non-urban) including

entrance and exit segments

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 22: Preconditions of target (HLN-AWWD)

# Item Condition

PC_9 Target NA

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 14 (wrongWayDriving)

PC_12 subCauseCode 2 (wrongDirection)


The activating and deactivating warning requirements of HLN-AWWD are stated below.




Table 23: Activating conditions (HLN-AWWD)



AWWD)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 24: Deactivating conditions (HLN-AWWD)



DC_2 Receive

cancellation

DENM


(HLN-AWWD)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.13 Public Transport Vehicle Crossing (HLN–PTVC)

4.2.3.1.13.1 State flow




The preconditions of HLN-PTVC are stated below.


case is activated:

Table 25: Preconditions of ego vehicle (HLN-PTVC)

# Item Condition



PC_3 Location -

PC_4 Road type Urban road

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 26: Preconditions of target (HLN-PTVC)

# Item Condition

PC_9 Target Public Transport vehicle

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 97 (collision risk)

PC_12 subCauseCode 2 (crossing collision risk)




The activating and deactivating warning requirements of HLN-PTVC are stated below.


Table 27: Activating conditions (HLN-PTVC)



PTVC)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 28: Deactivating conditions (HLN-PTVC)



DC_2 Receive

cancellation

DENM


(HLN-PTVC)

Target signal cause

(causeCode and

subCauseCode)



4.2.3.1.14 Public Transport Vehicle at a Stop (HLN–PTVS)

4.2.3.1.14.1 State flow




The preconditions of HLN-PTVS are stated below.


case is activated:

Table 29: Preconditions of ego vehicle (HLN-PTVS)

# Item Condition



PC_3 Location -

PC_4 Road type Urban road

PC_5 Time -

PC_6 Weather -


PC_8 Out of scope -



Table 30: Preconditions of target (HLN-PTVS)

# Item Condition

PC_9 Target Public Transport vehicle

PC_10 Relevance

distance

< 1000m

PC_11 causeCode 94 (stationary vehicle)

PC_12 subCauseCode 4 (publicTranportStop)




The activating and deactivating warning requirements of HLN-PTVS are stated below.


Table 31: Activating conditions (HLN-PTVS)



PTVS)

Target signal cause

(causeCode and

subCauseCode)


pathHistory



rider's behaviour.

eventPosition


Table 32: Deactivating conditions (HLN-PTVS)



DC_2 Receive

cancellation

DENM


(HLN-PTVS)

Target signal cause

(causeCode and

subCauseCode)



Abbreviations

Please refer to the abbreviations in Preamble document.

Document Information - Connected Motorcycle Consortium · 2020. 12. 6. · CMC Basic Specification...

Documents

Transcript of Document Information - Connected Motorcycle Consortium · 2020. 12. 6. · CMC Basic Specification...