Skip to content

Interpretation of Traffic Messages

Specific Rules Regarding Semantics in Traffic Messages

Termination of Messages

Messages can be terminated in three different ways:

  1. Terminate message (without notification)
  2. Cancel message with notification
  3. Terminate message with notification

Ad 1) This is the standard way of terminating messages. The message is immediately removed from the current traffic picture using an informationManagement message of type "closed" in the payload. See also the explanation on Lifecycle management in situationRecord.

Ad 2) This indicates that the message is being withdrawn. The message is immediately removed from the current traffic picture using an informationManagement message of type "cancelled" in the payload. See also the explanation on Lifecycle management in situationRecord.

Ad 3) This is an alternative way to terminate messages, where, by updating the message, the end time is communicated. The purpose is that the recipient actively forwards this end time. Shortly afterward, the message is actually removed from the traffic picture using an informationManagement message of type "closed" in the payload. See also the explanation on Lifecycle management in situationRecord.

Messages with a Set End Time

Messages can be provided with an expected end time, which is included in the current traffic picture using the element overallEndTime.

Termination

If a message with a set end time is terminated (options (1) and (3) from the previous section), then:

  • If the previously entered end time has not been reached, the end time will be updated with the termination time.
  • If the previously entered end time has passed, the end time will not be updated.
  • If the message is canceled (option (2) from the previous section), the previously entered end time will also not be adjusted.

Identifying Overrunning Messages

If a message with a set end time is part of the current traffic picture AND that end time is exceeded AND the message has not been terminated (option 3 from the previous section), this is indicated using the element overrunning.

Linked Messages

BMessages can be linked by establishing a cause → effect relationship. If this is applied, it results in DATEXII output where a ManagedCause is described.

Go back to the previous page