Update CDD reference, Add OCIT SREM Requestor

WITH SUCCESSORS;

/**

* This Element adds positioning support from the infrastructure to the vehicle.

* This DF adds positioning support from the infrastructure to the vehicle.

*

* @field itsStationPositions: defines a list of ITS stations (e.g. vehicles) and their corresponding position on

*                             the driving lane as defined in the lane topology of the MapData message or the GNSS position

}

/**

* The data frame "ConnectionTrajectory-addGrpC" defines the trajectory for travelling through the

* conflict area of an intersection and connects e.g an ingress with an egress lane. The trajectory is defined

* by two or more nodes. The starting node overlaps e.g. with the node of the ingress lane towards the

* This DF defines the trajectory for travelling through the conflict area of an intersection and connects 

* e.g an ingress with an egress lane. The trajectory is defined by two or more nodes. 

* The starting node overlaps e.g. with the node of the ingress lane towards the

* conflict zone. The ending node overlaps e.g. with the first node of the connected egress lane. 

* See the example in clause [ISO TS 19091] G.8.2.5.

*

*               to a connected egressing lane and the X/Y position value of the first node of the trajectory is the same as

*               the node of the ingress lane. The X/Y position of the last node is the same as the X/Y position of the first

*               node of the egressing lane.

* @field connectionID: defines the identifier of an allowed "maneuver" (e.g. ingress / egress relation). 

*               A generic Lane offers one or more allowed "maneuvers", therefore the trajectory is reference to the related "maneuver".

* @field connectionID: defines the identifier of an allowed `maneuver` (e.g. ingress / egress relation). 

*               A generic Lane offers one or more allowed `maneuvers`, therefore the trajectory is reference to the related `maneuver`.

*

* @note: "Reg-GenericLane" allows providing up to 4 connecting trajectories. In case a lane has more than 4 connecting trajectories, 

* @note: @ref Reg-GenericLane allows providing up to 4 connecting trajectories. In case a lane has more than 4 connecting trajectories,

* priority should be given to connecting trajectories of motorized traffic and complex manoeuvres.

*

*

}

/**

* The data frame "IntersectionState-addGrpC" defines a list of prioritization responses e.g. public transport acceleration.

* This DF defines a list of prioritization responses e.g. public transport acceleration.

* The signal prioritization (e.g. public transport) procedure in this profile follows two strategies.

* - For simple prioritization requests, the CAM/SPAT messages are used. This allows the migration of old legal systems towards C-ITS. 

* - For simple prioritization requests, the CAM/SPAT messages are used. 

*   This allows the migration of old legal systems towards C-ITS.

*   In this case, the CAM message is used to trigger the request towards the traffic light controller. 

*   The traffic light controller checks the request and broadcasts the status for the priority request within 

*   the "IntersectionState-addGrpC" data element (see [ISO TS 19091] G.5.1.9).

*   The traffic light controller checks the request and broadcasts the status for the priority request with this DF (see [ISO TS 19091] G.5.1.9).

* - For more complex signal requests, the SignalRequestMessage/SignalStatusMessage messages are to be used.

*

* @field activePrioritizations: list of Prioritizations.

/**

* Lanes may have limitations regarding vehicle height (e.g. due to a tunnel) and vehicle weight (e.g. due to a bridge). 

* To indicate these limitations, two data elements are added which are already defined in SAE J2735 for other messages.

*

* @field maxVehicleHeight: maximum allowed vehicle height

* @field maxVehicleWeight: maximum allowed vehicle mass

}

/**

* The data frame "MapData-addGrpC" defines a list of three-dimensional positions of signal heads in an intersection. 

* This DF defines a list of three-dimensional positions of signal heads in an intersection. 

* It enables vehicles to identify the signal head location for optical evaluation of the traffic light. 

* Combined with the SPAT/MapData messages, it enables e.g. driving vehicles to enhance safety decision in critical situations.

*

}

/**

* The data frame "NodeAttributeSet-addGrpC" defines additional attributes to support public transport and to enable a simple way of defining lane links.

* This DF defines additional attributes to support public transport and to enable a simple way of defining lane links.

*

* @field ptvRequest: defines control types attached to a node on a lane used by public transport for triggering

*                    the transmission of messages (e.g. prioritization request). It includes control points for public transport prioritization. 

}

/**

* The data frame "Position3D-addGrpC" includes the altitude data element defined in the common data dictionary [ETSI CDD].

* This DF includes the altitude data element defined in the common data dictionary [ETSI CDD].

*

* @field elevation: the data element is replaced by the ETSI "altitude" data element using the regional extension. 

*                   The "altitude" data element is defined in "Position3D-addGrpC" of this profile (see [ISO TS 19091] G.5.1.8).

*                   "Position3D-addGrpC" extends the "DF_Position3D" using the regional extension framework as defined in [ISO TS 19091] G.7.7.

* @field elevation: the data element is replaced by the ETSI `altitude` data element using the regional extension. 

*                   The `altitude` data element is defined in Position3D-addGrpC of this profile.

*                   Position3D-addGrpC extends the @ref Position3D using the regional extension framework.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data frame "RestrictionUserType-addGrpC" defines the driving restriction based on toxic emission type. 

* The meaning of the word 'restriction' is ambiguous as it may have a double interpretation, being:

* This DF defines the driving restriction based on toxic emission type. 

* The meaning of the word `restriction` is ambiguous as it may have a double interpretation, being:

*  - only these vehicles are allowed OR 

*  - these vehicles are not allowed and all others are. 

* The former is what is intended by the base standard.

* @field synchToSchedule: DeltaTime.

* @field rejectedReason: RejectedReason.

*

* @Note: The "PrioritizationResponseStatus" provides optionally the reason for prioritization response rejection.

* @Note: The @ref PrioritizationResponseStatus provides optionally the reason for prioritization response rejection.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data frame "ItsStationPosition" is used to provide real-time positioning information feedback to a

* specific ITS station (e.g. vehicle, pedestrian, bicycle) by infrastructure equipment. The position

* information includes, for example, the driving, crossing lane and/or the X/Y coordinates in relation to

* the reference position of the MapData. The "timeReference" indicates the time stamp of the the

* This DF is used to provide real-time positioning information feedback to a specific ITS station 

* (e.g. vehicle, pedestrian, bicycle) by infrastructure equipment.

*  The position information includes, for example, the driving, crossing lane and/or the X/Y coordinates in relation to

* the reference position of the MapData. The `timeReference` indicates the time stamp of the the

* message (received from an ITS station) for which the positioning feedback has been computed.

* 

* @field stationID: unique identifier.

ItsStationPositionList ::=	SEQUENCE SIZE(1..5) OF ItsStationPosition

/**

* The data frame "Node" is used to to identify a node of a lane (waypoint) by its "lane" and node identifier

* "id". The "intersectionID" is used if the referenced lane belongs to an adjacent intersection. If the node

* belongs to a connection trajectory (G.5.1.2) the "connectionID" is used.

* This DF is used to to identify a node of a lane (waypoint) by its `lane` and node identifier `id`. 

*

* The `intersectionID` is used if the referenced lane belongs to an adjacent intersection. If the node

* belongs to a connection trajectory ([ISO TS 19091] G.5.1.2) the `connectionID` is used.

*

* @field id: unique identifier.

* @field lane: identifier from lane.

NodeLink ::= SEQUENCE SIZE (1..5) OF Node

/**

* The data frame "PrioritizationResponse" is used to provide the prioritization status response and the

* This DF is used to provide the prioritization status response and the

* signal group identifier for a specific ITS station (e.g. vehicle).

*

* @field stationID: StationID.

PrioritizationResponseList ::=	SEQUENCE SIZE(1..10) OF PrioritizationResponse

/**

* The data frame "SignalHeadLocation" defines the XYZ position of a signal head within an intersection

* This DF defines the XYZ position of a signal head within an intersection

* and indicates the related signal group identifier.

*

* @category: Infrastructure information

SignalHeadLocationList ::=	SEQUENCE (SIZE(1..64)) OF	SignalHeadLocation

/**

* The data element "BatteryStatus" element defines an enumerated list of battery states.

* This DE defines an enumerated list of battery states.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data element "EmissionType" element defines an enumerated list of toxic emission types for vehicles.

* This DE defines an enumerated list of toxic emission types for vehicles.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data element "ExceptionalCondition" element defines a list of reasons for sudden changes in

* This DE defines a list of reasons for sudden changes in

* eventState parameters, thereby offering a reason for extended waiting times.

*

* @category: Infrastructure information

}

/**

* The data element "PtvRequestType" element defines a list of activation requests used for C-ITS

* migration of legacy public transport prioritization systems. The activation points are used while approaching to an intersection.

* This DE defines a list of activation requests used for C-ITS migration of legacy public 

* transport prioritization systems. 

* The activation points are used while approaching to an intersection.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data element "RejectedReason" element defines a list of reasons for rejected priority requests.

* This DE defines a list of reasons for rejected priority requests.

*

* @category: Infrastructure information

* @revision: V1.3.1

}

/**

* The data element "TimeReference" element defines a value in milliseconds in the current minute

* related to UTC time. A range of 60 000 covers one minute (60 seconds * 1 000 milliseconds)

* This DE defines a value in milliseconds in the current minute related to UTC time. 

* The range of 60 000 covers one minute (60 seconds * 1 000 milliseconds)

*

* @category: Infrastructure information

* @revision: V1.3.1

*/

TimeReference ::= INTEGER { oneMilliSec(1) } (0..60000)

/** 

* ## References:

* 1. [ISO TS 19091]: "Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections".

* 2. [SAE J2735]: "SURFACE VEHICLE STANDARD - V2X Communications Message Set Dictionary"

*/

END

* each request is set. Each request defines a path through the intersection which is desired in terms of lanes and

* approaches to be used. Each request can also contain the time of arrival and the expected duration of the service.

* Multiple requests to multiple intersections are supported. The requestor identifies itself in various ways (using methods

* supported by the RequestorDescription data frame), and its current speed, heading and location can be placed in this

* supported by the @refRequestorDescription data frame), and its current speed, heading and location can be placed in this

* structure as well. The specific request for service is typically based on previously decoding and examining the list of lanes

* and approaches for that intersection (sent in MAP messages). The outcome of all of the pending requests to a signal can

* be found in the Signal Status Message (SSM), and may be reflected in the SPAT message contents if successful.

}

/**

* This DE is used in the generic lane descriptions to provide a sequence of other defined

* This DF is used in the generic lane descriptions to provide a sequence of other defined

* lanes to which each lane connects beyond its stop point. See the Connection data frame entry for details. Note that this

* data frame is not used in some lane object types.

*

LaneDataAttributeList ::= SEQUENCE (SIZE(1..8)) OF LaneDataAttribute

/**

* This DF frame consists of a list of GenericLane entries.

* This DF consists of a list of GenericLane entries.

*

* @category: Infrastructure information

* @revision: V1.3.1

*/

NodeSetXY ::= SEQUENCE (SIZE(2..63)) OF NodeXY

/** This DF is the ODG Addition for Legancy R09 telegrams.

* 

* @field reportingPoint: reporting point as of R09 (maps to R09 field M Meldepunktnummer)

* @field priorityLevel:  priority level as of R09 (maps to R09 field P Prioritaet)

* @field length:         train length point as of R09 (maps to R09 field A Zuglaenge)

* @field route:          route as of R09 (maps to R09 field K Kursnummer)

* @field line:           line as of R09 (maps to R09 field L Liniennummer)

* @field direction:      direction as of R09 (maps to R09 field H Richtung von Hand)

* @field tour:           tour as of R09 (maps to R09 field Z Zielnummer)

* @field version:        version of R09

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

OcitRequestorDescriptionContainer ::= SEQUENCE {

  reportingPoint      ReportingPoint OPTIONAL,

  priorityLevel       PriorityLevel OPTIONAL,

  length              TrainLength OPTIONAL,

  route               RouteNumber OPTIONAL,

  line                LineNumber OPTIONAL,

  direction           TransitDirection OPTIONAL,

  tour                TourNumber OPTIONAL,

  version             VersionId OPTIONAL,

  ...

}

/**

* This DF is a sequence of lane IDs which refers to lane objects that overlap or overlay the current lane's spatial path.

*

* @field transitOccupancy: current vehicle occupancy

* @field transitSchedule:  current vehicle schedule adherence

* @field regional:         optional region specific data.

* @field ocit:             Extension container for Legacy R09 data (as defined by [OCIT]).

*

* @note: Note that the requestor description elements which are used when the request (the req) is made differ from

*        those used when the status of an active or pending request is reported (the ack). Typically, when reporting the status to

  transitSchedule   DeltaTime OPTIONAL,

  regional          SEQUENCE (SIZE(1..4)) OF

                    RegionalExtension {{Reg-RequestorDescription}} OPTIONAL,

  ...

  ...,

  [[ -- Extension for OCIT

    ocit OcitRequestorDescriptionContainer ]]

}

/**

*/

LaneWidth ::= INTEGER (0..32767)

/**

* This DE is used to provide the R09 line information.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

LineNumber ::= INTEGER (0..4294967295)

/**

* The angle at which another lane path meets the current lanes at the node point. Typically found in the node

* attributes and used to describe the angle of the departing or merging lane. Note that oblique and obtuse angles are allowed.

  ...

}

/**

* This DE is used to provide the R09 priority.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

PriorityLevel ::= INTEGER (0..255)

/**

* This DE provides a means to indicate if a request (found in the Signal RequestMessage) represents

* a new service request, a request update, or a request cancellation for either preemption or priority services.

  addGrpB      RegionId ::= 2

  addGrpC      RegionId ::= 3

/**

* This DE is used to provide the R09 reporting point.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

ReportingPoint ::= INTEGER (0..65535)

/**

* This DE is used to provide a unique ID between two parties for various dialog exchanges.

* Combined with the sender's VehicleID (consisting of a TempID or a Station ID), this provides a unique string for some

*/

RoadwayCrownAngle ::= INTEGER (-128..127)

/**

* This DE is used to provide the R09 route information.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

RouteNumber ::= INTEGER (0..4294967295)

/**

* This DE contains the stream of octets of the actual RTCM message that is being sent.

* The message’s contents are defined in RTCM Standard 10403.1 and in RTCM Standard 10402.1 and its successors.

*/

TimeIntervalConfidence ::= INTEGER (0..15)

/**

* This DE is used to provide the R09 tour information.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

TourNumber ::= INTEGER (0..4294967295)

/**

* This DE is used to provide the R09 train length.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

TrainLength ::= INTEGER (0..7)

/**

* This DE is used to provide the R09 direction information.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

TransitDirection ::= INTEGER (0..255)

/**

*  This DE is used to relate basic level of current ridership.

*

*/

Velocity ::= INTEGER (0..8191)

/**

* This DE is used to provide the R09 version information.

*

* @category: Infrastructure information

* @revision: V2.2.1

*/

VersionId ::= INTEGER (0..4294967295)

/**

* This DE is used to indicate to the vehicle that it must stop at the stop line and not move past.

*

* ## References:

* 1. [ISO TS 19091]: "Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections".

* 2. [SAE J2735]: "SURFACE VEHICLE STANDARD - V2X Communications Message Set Dictionary"

* 3. [OCIT]: "OCIT Developer Group. https://ocit.org"

*/

END

/**

* In vehicle information Message Message

* This DF includes DEs for the IVIM protocolVersion, the IVI message type identifier _messageID_,

* the station identifier _stationID_ of the originating ITS-S and the IVI data from ISO TS 19321.

* This DF includes DEs for the IVIM protocolVersion, the IVI message type identifier `messageID`,

* the station identifier `stationID` of the originating ITS-S and the IVI data from ISO TS 19321.

*

* @field header: The DE _protocolVersion_ is used to select the appropriate protocol decoder at the receiving ITS-S. It shall be set to 2.

*                The DE _messageID_ shall be ivim(6).

* @field ivi: The DE _ivi_ contains the IVI data as defined in ISO TS 19321.

* @field header: The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S. 

*                It shall be set to 2.

*                The DE `messageID` shall be ivim(6).

* @field ivi:    contains the IVI data as defined in ISO TS 19321.

* 

* @category: Basic Information

* @revision: V1.3.1

/**

* Map (lane topology) extended Message

* This DF includes DEs for the MAPEM: protocolVersion, the MAPEM message type identifier _messageID_, 

* the station identifier _stationID_ of the originating ITS-S and the Map data from ETSI-ITS-DSRC.

* This DF includes DEs for the MAPEM: protocolVersion, the MAPEM message type identifier `messageID`, 

* the station identifier `stationID` of the originating ITS-S and the Map data from ETSI-ITS-DSRC.

* 

* @field header:  The DE _protocolVersion_ is used to select the appropriate protocol decoder at the receiving ITS-S. It shall be set to 2.

*                 The DE _messageID_ shall be mapem(5).

* @field map: The DE _map_ contains the MAP data as defined in ETSI-ITS-DSRC.

* @field header:  The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S. 

*                 It shall be set to 2.

*                 The DE `messageID` shall be mapem(5).

* @field map:     contains the MAP data as defined in ETSI-ITS-DSRC.

* 

* @category: Basic Information

* @revision: V1.3.1

/**

* RTCM corrections extended extended Message

* This DF includes DEs for the RTCMEM: protocolVersion, the RTCMEM message type identifier _messageID_,

* the station identifier _stationID_ of the originating ITS-S and the RTCM corrections as of ETSI-ITS-DSRC.

* This DF includes DEs for the RTCMEM: protocolVersion, the RTCMEM message type identifier `messageID`,

* the station identifier `stationID` of the originating ITS-S and the RTCM corrections as of ETSI-ITS-DSRC.

*

* @field header: The DE _protocolVersion_ is used to select the appropriate protocol decoder at the receiving ITS-S. It shall be set to 1.

*                The DE _messageID_ shall be rtcmem(13).

* @field srm:    The DE _rtcmc_ contains the RTCM corrections data as defined in ETSI-ITS-DSRC.

* @field header: The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S. 

*                It shall be set to 1.

*                The DE `messageID` shall be rtcmem(13).

* @field rtcmc:  contains the RTCM corrections data as defined in ETSI-ITS-DSRC.

* 

* @category: Basic Information

* @revision: V1.3.1