# ASN.1 module ETSI-ITS-DSRC-AddGrpC
OID: _{ itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts103301 (103301) dsrc (6) addgrpc (0) major-version-2 (2) minor-version-1 (1) }_
draft 001 of the ETSI-ITS-DSRC-AddGrpC module for TS 103 301 V2.2.1 integrating:
initial revision based on ASN.1 files of [ISO TS 19091] and [SAE J2735]
## Imports:
* **[ETSI-ITS-DSRC](ETSI-ITS-DSRC.md)** *{ itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts103301 (103301) dsrc (6) major-version-2 (2) minor-version-1 (1) } WITH SUCCESSORS*
* **[ETSI-ITS-CDD](ETSI-ITS-CDD.md)** *{ itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) 102894 cdd (2) major-version-4 (4) minor-version-1 (1) } WITH SUCCESSORS*
## Data Elements:
### ConnectionManeuverAssist-addGrpC
This DF adds positioning support from the infrastructure to the vehicle.
* _itsStationPosition_ of type [**ItsStationPositionList**](#ItsStationPositionList) OPTIONAL
* 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
deviation of the ITS Station from the high precision reference position in X/Y coordinates. It
enables accurate, real-time positioning support to the moving ITS entities by the infrastructure.*
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
ConnectionManeuverAssist-addGrpC ::= SEQUENCE {
itsStationPosition ItsStationPositionList OPTIONAL,
...
}
```
### ConnectionTrajectory-addGrpC
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.
* _nodes_ of type [**NodeSetXY**](ETSI-ITS-DSRC.md#NodeSetXY)
defines a list of nodes for the trajectory. It defines e.g. a geometric trajectory from an ingressing
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.
* _connectionID_ of type [**LaneConnectionID**](ETSI-ITS-DSRC.md#LaneConnectionID)
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`.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: [**Reg-GenericLane**](#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.
>>>
```asn1
ConnectionTrajectory-addGrpC ::= SEQUENCE {
nodes NodeSetXY,
connectionID LaneConnectionID,
...
}
```
### IntersectionState-addGrpC
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.
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 with this DF (see [ISO TS 19091] G.5.1.9).
- For more complex signal requests, the SignalRequestMessage/SignalStatusMessage messages are to be used.
* _activePrioritizations_ of type [**PrioritizationResponseList**](#PrioritizationResponseList) OPTIONAL
list of Prioritizations.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
IntersectionState-addGrpC ::= SEQUENCE {
activePrioritizations PrioritizationResponseList OPTIONAL,
...
}
```
### LaneAttributes-addGrpC
Lanes may have limitations regarding vehicle height (e.g. due to a tunnel) and vehicle weight (e.g. due to a bridge).
* _maxVehicleHeight_ of type [**VehicleHeight**](ETSI-ITS-DSRC.md#VehicleHeight) OPTIONAL
maximum allowed vehicle height
* _maxVehicleWeight_ of type [**VehicleMass**](ETSI-ITS-CDD.md#VehicleMass) OPTIONAL
maximum allowed vehicle mass
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-addGrpC ::= SEQUENCE {
maxVehicleHeight VehicleHeight OPTIONAL,
maxVehicleWeight VehicleMass OPTIONAL,
...
}
```
### MapData-addGrpC
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.
* _signalHeadLocations_ of type [**SignalHeadLocationList**](#SignalHeadLocationList) OPTIONAL
list of geo positions
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
MapData-addGrpC ::= SEQUENCE {
signalHeadLocations SignalHeadLocationList OPTIONAL,
...
}
```
### MovementEvent-addGrpC
Priority and preemption have a considerable impact to the timing parameters in the SPAT message (eventState).
User acceptance is expected to increase if the reason for sudden changes in timing parameters is communicated to them.
* _stateChangeReason_ of type [**ExceptionalCondition**](#ExceptionalCondition) OPTIONAL
reason code
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
MovementEvent-addGrpC ::= SEQUENCE {
stateChangeReason ExceptionalCondition OPTIONAL,
...
}
```
### NodeAttributeSet-addGrpC
This DF defines additional attributes to support public transport and to enable a simple way of defining lane links.
* _ptvRequest_ of type [**PtvRequestType**](#PtvRequestType) OPTIONAL
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.
These control points are currently implemented by legacy systems using hardware sensors mounted on the roadside.
* _nodeLink_ of type [**NodeLink**](#NodeLink) OPTIONAL
defines a link to one or to a set of another node/lane from this node. The nodeLink allows to set a link between specific nodes
of generic lanes or trajectories. This supports e.g. lane merging/diverging situations ([ISO TS 19091] G.8.2.7) and the linking of trajectories
in the conflict zone to lanes (see example [ISO TS 19091] G.8.2.5).
* _node_ of type [**Node**](#Node) OPTIONAL
defines an identifier of this node.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
NodeAttributeSet-addGrpC ::= SEQUENCE {
ptvRequest PtvRequestType OPTIONAL,
nodeLink NodeLink OPTIONAL,
node Node OPTIONAL,
...
}
```
### Position3D-addGrpC
This DF includes the altitude data element defined in the common data dictionary [ETSI CDD].
* _altitude_ of type [**Altitude**](ETSI-ITS-CDD.md#Altitude)
* 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 [**Position3D**](#Position3D) using the regional extension framework.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Position3D-addGrpC ::= SEQUENCE {
altitude Altitude,
...
}
```
### RestrictionUserType-addGrpC
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.
* _emission_ of type [**EmissionType**](#EmissionType) OPTIONAL
restriction baesed on emission.
* _fuel_ of type [**FuelType**](ETSI-ITS-DSRC.md#FuelType) OPTIONAL
restriction baesed on fuel.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionUserType-addGrpC ::= SEQUENCE {
emission EmissionType OPTIONAL,
fuel FuelType OPTIONAL,
...
}
```
### RequestorDescription-addGrpC
Some road authorities like to give priority to vehicles based on the type of fuel they use. In addition,
electric vehicles may receive priority based on their battery status.
* _fuel_ of type [**FuelType**](ETSI-ITS-DSRC.md#FuelType) OPTIONAL
fuel used by vehicle.
* _batteryStatus_ of type [**BatteryStatus**](#BatteryStatus) OPTIONAL
current batter status of vehicle.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RequestorDescription-addGrpC ::= SEQUENCE {
fuel FuelType OPTIONAL,
batteryStatus BatteryStatus OPTIONAL,
...
}
```
### SignalStatusPackage-addGrpC
The traffic control centre (TCC) may advice a public transport vehicle (e.g. bus) to synchronize his travel time.
This may happen when, for example, two busses, due to special traffic conditions, are out of schedule.
The first might be too late, the second too fast. The consequence is that the second is driving
just behind the first and is empty as all passengers are within the first one. To avoid this often-occurring
situation, the TCC transmits time synchronization advices to the public transport vehicles using the
signal status message.
* _synchToSchedule_ of type [**DeltaTime**](ETSI-ITS-DSRC.md#DeltaTime) OPTIONAL
DeltaTime.
* _rejectedReason_ of type [**RejectedReason**](#RejectedReason) OPTIONAL
RejectedReason.
@Note: The [**PrioritizationResponseStatus**](ETSI-ITS-DSRC.md#PrioritizationResponseStatus) provides optionally the reason for prioritization response rejection.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalStatusPackage-addGrpC ::= SEQUENCE {
synchToSchedule DeltaTime OPTIONAL,
rejectedReason RejectedReason OPTIONAL,
...
}
```
### ItsStationPosition
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.
* _stationID_ of type [**StationID**](ETSI-ITS-CDD.md#StationID)
unique identifier.
* _laneID_ of type [**LaneID**](ETSI-ITS-DSRC.md#LaneID) OPTIONAL
LaneID.
* _nodeXY_ of type [**NodeOffsetPointXY**](ETSI-ITS-DSRC.md#NodeOffsetPointXY) OPTIONAL
NodeOffsetPointXY.
* _timeReference_ of type [**TimeReference**](#TimeReference) OPTIONAL
TimeReference.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: The computation of the positioning feedback is out of focus of this standard.
>>>
```asn1
ItsStationPosition ::= SEQUENCE {
stationID StationID,
laneID LaneID OPTIONAL,
nodeXY NodeOffsetPointXY OPTIONAL,
timeReference TimeReference OPTIONAL,
...
}
```
### ItsStationPositionList
```asn1
ItsStationPositionList ::= SEQUENCE SIZE(1..5) OF ItsStationPosition
```
### Node
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.
* _id_ of type **INTEGER**
unique identifier.
* _lane_ of type [**LaneID**](ETSI-ITS-DSRC.md#LaneID) OPTIONAL
identifier from lane.
* _connectionID_ of type [**LaneConnectionID**](ETSI-ITS-DSRC.md#LaneConnectionID) OPTIONAL
identifier from connection.
* _intersectionID_ of type [**IntersectionID**](ETSI-ITS-DSRC.md#IntersectionID) OPTIONAL
identifier from intersection.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Node ::= SEQUENCE {
id INTEGER,
lane LaneID OPTIONAL,
connectionID LaneConnectionID OPTIONAL,
intersectionID IntersectionID OPTIONAL,
...
}
```
### NodeLink
```asn1
NodeLink ::= SEQUENCE SIZE (1..5) OF Node
```
### PrioritizationResponse
This DF is used to provide the prioritization status response and the
signal group identifier for a specific ITS station (e.g. vehicle).
* _stationID_ of type [**StationID**](ETSI-ITS-CDD.md#StationID)
StationID.
* _priorState_ of type [**PrioritizationResponseStatus**](ETSI-ITS-DSRC.md#PrioritizationResponseStatus)
PrioritizationResponseStatus.
* _signalGroup_ of type [**SignalGroupID**](ETSI-ITS-DSRC.md#SignalGroupID)
SignalGroupID.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PrioritizationResponse ::= SEQUENCE {
stationID StationID,
priorState PrioritizationResponseStatus,
signalGroup SignalGroupID,
...
}
```
### PrioritizationResponseList
```asn1
PrioritizationResponseList ::= SEQUENCE SIZE(1..10) OF PrioritizationResponse
```
### SignalHeadLocation
This DF defines the XYZ position of a signal head within an intersection
and indicates the related signal group identifier.
* _nodeXY_ of type [**NodeOffsetPointXY**](ETSI-ITS-DSRC.md#NodeOffsetPointXY)
* _nodeZ_ of type [**DeltaAltitude**](ETSI-ITS-CDD.md#DeltaAltitude)
* _signalGroupID_ of type [**SignalGroupID**](ETSI-ITS-DSRC.md#SignalGroupID)
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalHeadLocation ::= SEQUENCE {
nodeXY NodeOffsetPointXY,
nodeZ DeltaAltitude,
signalGroupID SignalGroupID,
...
}
```
### SignalHeadLocationList
```asn1
SignalHeadLocationList ::= SEQUENCE (SIZE(1..64)) OF SignalHeadLocation
```
### BatteryStatus
This DE defines an enumerated list of battery states.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
BatteryStatus ::= ENUMERATED {
unknown,
critical,
low,
good,
...
}
```
### EmissionType
This DE defines an enumerated list of toxic emission types for vehicles.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
EmissionType ::= ENUMERATED {
euro1,
euro2,
euro3,
euro4,
euro5,
euro6,
...
}
```
### ExceptionalCondition
This DE defines a list of reasons for sudden changes in
eventState parameters, thereby offering a reason for extended waiting times.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
ExceptionalCondition ::= ENUMERATED {
unknown,
publicTransportPriority,
emergencyVehiclePriority,
trainPriority,
bridgeOpen,
vehicleHeight,
weather,
trafficJam,
tunnelClosure,
meteringActive,
truckPriority,
bicyclePlatoonPriority,
vehiclePlatoonPriority,
...
}
```
### PtvRequestType
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.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PtvRequestType ::= ENUMERATED {
preRequest,
mainRequest,
doorCloseRequest,
cancelRequest,
emergencyRequest,
...
}
```
### RejectedReason
This DE defines a list of reasons for rejected priority requests.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RejectedReason ::= ENUMERATED {
unknown,
exceptionalCondition,
maxWaitingTimeExceeded,
ptPriorityDisabled,
higherPTPriorityGranted,
vehicleTrackingUnknown,
...
}
```
### TimeReference
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)
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
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"