Update CDD reference, Add OCIT SREM Requestor (4bce23ca) · Commits · ITS - Intelligent Transport Systems / ASN1 / IS TS 103 301

DSRC-addgrp-C.asn

+45 −38

DSRC.asn

+98 −4

Original line number	Original line	Diff line number	Diff line
	@@ -169,7 +169,7 @@ SPAT ::= SEQUENCE {
	* each request is set. Each request defines a path through the intersection which is desired in terms of lanes and		* 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.		* 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		* 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		* 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		* 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.		* be found in the Signal Status Message (SSM), and may be reflected in the SPAT message contents if successful.
	@@ -325,7 +325,7 @@ ComputedLane ::= SEQUENCE {
	}		}

	/**		/**
	* 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		* 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.		* data frame is not used in some lane object types.
	*		*
	@@ -806,7 +806,7 @@ LaneDataAttribute ::= CHOICE {
	LaneDataAttributeList ::= SEQUENCE (SIZE(1..8)) OF LaneDataAttribute		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		* @category: Infrastructure information
	* @revision: V1.3.1		* @revision: V1.3.1
	@@ -1238,6 +1238,32 @@ NodeXY ::= SEQUENCE {
	*/		*/
	NodeSetXY ::= SEQUENCE (SIZE(2..63)) OF NodeXY		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.		* This DF is a sequence of lane IDs which refers to lane objects that overlap or overlay the current lane's spatial path.
	*		*
	@@ -1336,6 +1362,7 @@ RegulatorySpeedLimit ::= SEQUENCE {
	* @field transitOccupancy: current vehicle occupancy		* @field transitOccupancy: current vehicle occupancy
	* @field transitSchedule: current vehicle schedule adherence		* @field transitSchedule: current vehicle schedule adherence
	* @field regional: optional region specific data.		* @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		* @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		* those used when the status of an active or pending request is reported (the ack). Typically, when reporting the status to
	@@ -1355,7 +1382,9 @@ RequestorDescription ::= SEQUENCE {
	transitSchedule DeltaTime OPTIONAL,		transitSchedule DeltaTime OPTIONAL,
	regional SEQUENCE (SIZE(1..4)) OF		regional SEQUENCE (SIZE(1..4)) OF
	RegionalExtension {{Reg-RequestorDescription}} OPTIONAL,		RegionalExtension {{Reg-RequestorDescription}} OPTIONAL,
	...		...,
			[[ -- Extension for OCIT
			ocit OcitRequestorDescriptionContainer ]]
	}		}

	/**		/**
	@@ -2706,6 +2735,14 @@ LayerType ::= ENUMERATED {
	*/		*/
	LaneWidth ::= INTEGER (0..32767)		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		* 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.		* attributes and used to describe the angle of the departing or merging lane. Note that oblique and obtuse angles are allowed.
	@@ -3014,6 +3051,14 @@ PrioritizationResponseStatus ::= ENUMERATED {
	...		...
	}		}

			/**
			* 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		* 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.		* a new service request, a request update, or a request cancellation for either preemption or priority services.
	@@ -3052,6 +3097,14 @@ RegionId ::= INTEGER (0..255)
	addGrpB RegionId ::= 2		addGrpB RegionId ::= 2
	addGrpC RegionId ::= 3		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.		* 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		* Combined with the sender's VehicleID (consisting of a TempID or a Station ID), this provides a unique string for some
	@@ -3239,6 +3292,14 @@ RoadSegmentID ::= INTEGER (0..65535)
	*/		*/
	RoadwayCrownAngle ::= INTEGER (-128..127)		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.		* 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.		* The message’s contents are defined in RTCM Standard 10403.1 and in RTCM Standard 10402.1 and its successors.
	@@ -3666,6 +3727,30 @@ TimeConfidence ::= ENUMERATED {
	*/		*/
	TimeIntervalConfidence ::= INTEGER (0..15)		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.		* This DE is used to relate basic level of current ridership.
	*		*
	@@ -3801,6 +3886,14 @@ VehicleType ::= ENUMERATED {
	*/		*/
	Velocity ::= INTEGER (0..8191)		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.		* This DE is used to indicate to the vehicle that it must stop at the stop line and not move past.
	*		*
	@@ -3833,6 +3926,7 @@ ZoneLength ::= INTEGER (0..10000)
	* ## References:		* ## References:
	* 1. [ISO TS 19091]: "Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections".		* 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"		* 2. [SAE J2735]: "SURFACE VEHICLE STANDARD - V2X Communications Message Set Dictionary"
			* 3. [OCIT]: "OCIT Developer Group. https://ocit.org"
	*/		*/

	END		END

IVIM-PDU-Descriptions.asn

+6 −5

Original line number	Original line	Diff line number	Diff line
	@@ -29,12 +29,13 @@ WITH SUCCESSORS;

	/**		/**
	* In vehicle information Message Message		* In vehicle information Message Message
	* This DF includes DEs for the IVIM protocolVersion, the IVI message type identifier _messageID_,		* 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.		* 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.		* @field header: The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S.
	* The DE _messageID_ shall be ivim(6).		* It shall be set to 2.
	* @field ivi: The DE _ivi_ contains the IVI data as defined in ISO TS 19321.		* The DE `messageID` shall be ivim(6).
			* @field ivi: contains the IVI data as defined in ISO TS 19321.
	*		*
	* @category: Basic Information		* @category: Basic Information
	* @revision: V1.3.1		* @revision: V1.3.1

MAPEM-PDU-Descriptions.asn

+6 −5

Original line number	Original line	Diff line number	Diff line
	@@ -35,12 +35,13 @@ WITH SUCCESSORS;

	/**		/**
	* Map (lane topology) extended Message		* Map (lane topology) extended Message
	* This DF includes DEs for the MAPEM: protocolVersion, the MAPEM message type identifier _messageID_,		* 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.		* 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.		* @field header: The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S.
	* The DE _messageID_ shall be mapem(5).		* It shall be set to 2.
	* @field map: The DE _map_ contains the MAP data as defined in ETSI-ITS-DSRC.		* The DE `messageID` shall be mapem(5).
			* @field map: contains the MAP data as defined in ETSI-ITS-DSRC.
	*		*
	* @category: Basic Information		* @category: Basic Information
	* @revision: V1.3.1		* @revision: V1.3.1

RTCMEM-PDU-Descriptions.asn

+6 −5

Original line number	Original line	Diff line number	Diff line
	@@ -35,12 +35,13 @@ WITH SUCCESSORS;

	/**		/**
	* RTCM corrections extended extended Message		* RTCM corrections extended extended Message
	* This DF includes DEs for the RTCMEM: protocolVersion, the RTCMEM message type identifier _messageID_,		* 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.		* 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.		* @field header: The DE `protocolVersion` is used to select the appropriate protocol decoder at the receiving ITS-S.
	* The DE _messageID_ shall be rtcmem(13).		* It shall be set to 1.
	* @field srm: The DE _rtcmc_ contains the RTCM corrections data as defined in ETSI-ITS-DSRC.		* The DE `messageID` shall be rtcmem(13).
			* @field rtcmc: contains the RTCM corrections data as defined in ETSI-ITS-DSRC.
	*		*
	* @category: Basic Information		* @category: Basic Information
	* @revision: V1.3.1		* @revision: V1.3.1

Original line number	Original line	Diff line number	Diff line
	@@ -26,7 +26,7 @@ FROM ETSI-ITS-CDD {
	WITH SUCCESSORS;		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		* @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 driving lane as defined in the lane topology of the MapData message or the GNSS position
	@@ -42,9 +42,9 @@ ConnectionManeuverAssist-addGrpC ::= SEQUENCE {
	}		}

	/**		/**
	* The data frame "ConnectionTrajectory-addGrpC" defines the trajectory for travelling through the		* This DF defines the trajectory for travelling through the conflict area of an intersection and connects
	* conflict area of an intersection and connects e.g an ingress with an egress lane. The trajectory is defined		* e.g an ingress with an egress lane. The trajectory is defined by two or more nodes.
	* by two or more nodes. The starting node overlaps e.g. with the node of the ingress lane towards the		* 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.		* 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.		* See the example in clause [ISO TS 19091] G.8.2.5.
	*		*
	@@ -52,10 +52,10 @@ ConnectionManeuverAssist-addGrpC ::= SEQUENCE {
	* to a connected egressing lane and the X/Y position value of the first node of the trajectory is the same as		* 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		* 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.		* node of the egressing lane.
	* @field connectionID: defines the identifier of an allowed "maneuver" (e.g. ingress / egress relation).		* @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".		* 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.		* priority should be given to connecting trajectories of motorized traffic and complex manoeuvres.
	*		*
	*		*
	@@ -69,12 +69,12 @@ ConnectionTrajectory-addGrpC ::= SEQUENCE {
	}		}

	/**		/**
	* 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.		* 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.		* 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 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).
	* the "IntersectionState-addGrpC" data element (see [ISO TS 19091] G.5.1.9).

Admin message