Skip to main content

UC 5: Accident/ vehicle breakdown warning

Operation use case​

Definition​

Warn and inform about incidents (traffic accident or vehicle breakdown) that the road user will encounter.

Traffic accidents: DENM does not allow for quantifiable details on the accidents’ gravity and impact on traffic: can be anything from a small accident on the hard shoulder upto a fully blocked roadway in both directions. . The awareness zones in the DENM messages will include all directions where there is impact for road users.

Broken down vehicles: Can be any stopped vehicle, within Mobilidata is currently no information about the cause for stopping available. Also: vehicle can be present ON the roadway, or on the hard/soft shoulder. The message type in use can provide the cause and possible sub causes.

Operational Road Environment​

  • Territory: Flanders
  • Border passing cases: N/A
  • Road class: All
  • Time restrictions: None
  • Weather restrictions: None
  • Special restrictions: None

MI & Historical archive​

DENM information​

CausecodeDescriptionSubcausecodeDescription
2Accident0unavailable
1multiple vehicles accidents
2heavy accident
3accident involving lorry
4accident involving bus
5accident involving hazardous materials (ADR transports)
7Unsecured accident
94Stationary vehicle0unavailable
2Vehicle breakdown
  • Default time to live 10 minutes (600 sec’s in the DENM message).
  • Updated based upon more or more reliable data and system awareness of extended life-time
  • Lat/Long position of event (can be updated if a better data source corrects the position)
  • Awareness zone(s) defined, upstream the lat/long position:
  • Type of accidents/vehicle breakdown vehicle (motorcycle/car/truck): not specified– sometimes some reference to be found in the Subcause codes.

MI headers​

Capability descriptor:

{
  "messageType": "DENM",
  "originatingCountry": "BE",
  "protocolVersion": "DENM:1.3.1",
  "publisherId": "BE00004",
  "publicationId": "BE00004:DENM_ACCIDENT_BREAKDOWN_01",
  "custom-mobilidata-publisherType": "PIP",
  "custom-mobilidata-dtapEnvironment": "production",
  "custom-mobilidata-useCase": [5],
  "quadTree": []
}

Historical archive​

As well as the original messages as the (agregated) RUF message are stored in the historical archive.

Data sources​

  • Traffic center DATEX feed: The Flemish Road Authority has got a network of CCTV camera’s and rely on police patrols who report accidents. These accident reports are shared in the VC DATEX-II feed connected to Mobilidata.
  • RUF (road user feedback/new notifications) coming from Mobilidata connected Road users, currently Flitsmeister and KartaGPS. Under unspecified validation processes before transmission towards Mobilidata (e.g., required trust level user? number of notifications required? location bundling process?) The user trust system of the C-ITS service provider is not questioned.
  • Touring Mobilis traffic center by Be-Mobile : service provider Be- Mobile has its own traffic editorial. This editorial also receives information about accidents.

Risk and remarks​

For lower level (secondary and tertiary) roads, the availablility of information is relying mostly on voluntary RUF information and location accuracy may be limited

Alert cancelling​

  • Default time to live 10’ (source confirmation disappears, without alert cancelling)
  • Source alert cancellation.

RUF/ ES Cooperative information options​

For this use case it is the (strongly) recommended to participate in the Mobilidata feedback channel.

  • ES (event sourcing – creating new information points) is possible in form of ‘a new event’ information. The user can indicate that at the location of creation of his/her ES a new event is applicable.
  • Feedback only (Road user feedback - upvoting/downvoting of existing notifications).

RUF message

Use case implementation recommendations in applications and apps​

disclaimer

Mobilidata does not warrant an optimal safe usage system with recommendations below. It fully remains the responsibility of the information provider to know the usage situation and needs of their users and provide a safety enhancing service based on Mobilidata information.

Message​

The alert for road users entering a zone with encounter of accident or broken down vehicle.

Message Example​

UC 5 Message Example
{
    "shardId": "1",
    "latitude": "50.979638",
    "quadTree": ",120202132033200232,1202021320332,",
    "causeCode": "91",
    "longitude": "4.486181",
    "shardCount": "1",
    "messageType": "DENM",
    "publisherId": "BE00004",
    "subCauseCode": "0",
    "publicationId": "BE00004:DENM_ACCIDENT_BREAKDOWN_02",
    "baselineVersion": "2.1.0",
    "protocolVersion": "DENM:1.3.1",
    "originatingCountry": "BE",
    "custom-mobilidata-useCase": ",5,",
    "custom-mobilidata-timestamp": "1737355772126",
    "custom-mobilidata-alertCCodes": "211",
    "custom-mobilidata-publisherType": "PIP",
    "custom-mobilidata-baselineVersion": "1.0.0",
    "custom-mobilidata-dtapEnvironment": "production"
}
Tags:
Last updated on by taeyma41