* Common message header for application and facilities layer messages.
* It is included at the beginning of an ITS message as the message header.
*
* @param protocolVersion: version of the ITS message,
*
* @param messageID: Type of the ITS message.
* Following message type values are assigned in the present document:
* - denm(1): Decentralized Environmental Notification Message (DENM) as specified in ETSI EN 302 637-3 [i.3],
* - cam(2): Cooperative Awareness Message (CAM) as specified in ETSI EN 302 637-2 [i.2],
* - poi(3): Point of Interest message as specified in ETSI TS 101 556-1 [i.11],
* - spatem(4): Signal Phase And Timing (SPAT) message as specified in SAE J2735 [i.12] and in ETSI TS 103 301 [i.17],
* - mapem(5): MAP message as specified in SAE J2735 [i.12] and in ETSI TS 103 301 [i.17],
* - ivim(6): In Vehicle Information (IVI) message as defined in ISO TS 19321 [i.13],
* - ev-rsr(7): Electric vehicle recharging spot reservation message, as defined in ETSI TS 101 556-3 [i.14],
* - tistpgtransaction(8): messages for Tyre Information System (TIS) and Tyre Pressure Gauge (TPG) interoperability, as specified in ETSI TS 101 556-2 i.15,
* - srem(9): Traffic light Signal Request Message as specified in ETSI TS 103 301 [i.17],
* - ssem(10): Traffic Light Signal Request Status Message as specified in ETSI TS 103 301 [i.17].
* - evcsn(11): Electrical Vehicle Charging Spot Notification message as specified in ETSI TS 101 556-1 [i.11],
* - saem(12): Services Announcement Extended Message as specified in ETSI TS 102 890-1 i.19,
* - rtcmem(13): Radio Technical Commission for Maritime Services (RTCM) Message as specified in ETSI TS 103 301 [i.17],
* - value 14-255: reserved for future usage,
*
* @param stationID: the identifier of the ITS-S that generates the ITS message in question. It shall be represented as specified in clause A.77 @ref StationID.
* Current controlling mechanism for longitudinal movement of the vehicle. The data may be provided via the in-vehicle network. It indicates whether a specific in-vehicle acceleration control system is engaged or not. Currently, this DE includes the information of the vehicle brake pedal, gas pedal, emergency brake system, collision warning system, adaptive cruise control system, cruise control system and speed limiter system.
*
* The corresponding bit shall be set to 1 under the following conditions:
* - `brakePedalEngaged(0)`: Driver is stepping on the brake pedal,
* - `gasPedalEngaged(1)`: Driver is stepping on the gas pedal,
* - `emergencyBrakeEngaged(2)`: emergency brake system is engaged,
* - `collisionWarningEngaged(3)`: collision warning system is engaged,
* - `accEngaged(4)`: ACC is engaged,
* - `cruiseControlEngaged(5)`: cruise control is engaged,
* - `speedLimiterEngaged(6)`: speed limiter is engaged.
*
* Otherwise (for example when the corresponding system is not available due to non equipped system or information is unavailable), the corresponding bit shall be set to `0`.
* @note: The system engagement condition is OEM specific and therefore out of scope of the present document.
* Encoded value of the sub cause codes of the event type `accident` as defined in clause A.10 of ETSI TS 102 859-2.
* Sub event cause and value setting rule is defined according to clause 7.1.4 of ETSI EN 302 637-3 [i.3].
* @category: Traffic information
*
* The sub causes are described as following:
*/
AccidentSubCauseCode ::= INTEGER {
unavailable(0), --!< in case the information on the sub cause of the accident is unavailable
multiVehicleAccident(1), --!< in case more than two vehicles are involved in accident
heavyAccident(2), --!< in case the airbag of the vehicle involved in the accident is triggered, the accident requires important rescue and/or recovery work
accidentInvolvingLorry(3), --!< in case the accident involves a lorry
accidentInvolvingBus(4), --!< in case the accident involves a bus
accidentInvolvingHazardousMaterials(5), --!< in case the accident involves hazardous material
accidentOnOppositeLane(6), --!< in case the accident happens on opposite lanes
unsecuredAccident(7), --!< in case the accident is not secured
assistanceRequested(8) --!< in case rescue and assistance are requested
} (0..255) --!< value 9-255 are reserved for future usage
* The absolute accuracy of a reported vehicle acceleration value with a predefined confidence level (e.g. 95 %). The required confidence level is defined by the corresponding standards applying the DE.
*
* The value shall be set to:
* - `1` if the acceleration accuracy is equal to or less than 0,1 m/s2.
* - `n (n > 1 and n < 100)` if the acceleration accuracy is equal to or less than n × 0,1 m/s2.
* - `100` if the acceleration accuracy is equal to or less than 10 m/s2.
* - `101` if the acceleration accuracy is out of range i.e. greater than 10 m/s2.
* - `102` if the data is unavailable.
*
* The DE is used in LateralAcceleration DF as defined in clause A.115, LongitudinalAcceleration DF as defined in clause A.116, or VerticalAcceleration DF as defined in clause A.129.
*
* NOTE: The fact that an acceleration value is received with confidence set to 'unavailable(102)' can be caused by several reasons, such as:
* - the sensor cannot deliver the accuracy at the defined confidence level because it is a low-end sensor,
* - the sensor cannot calculate the accuracy due to lack of variables, or
* - there has been a vehicle bus (e.g. CAN bus) error.
*
* In all 3 cases above, the reported acceleration value may be valid and used by the application.
*
* If an acceleration value is received and its confidence is set to `outOfRange(101)`, it means that the value is not valid and therefore cannot be trusted. Such value is not useful for the application.