Commission Implementing Regulation (EU) 2016/799Show full title

5.4.7 Detailed DSRC transaction description U.K.

DSC_44 Initialisation is performed according to DSC_44 — DSC_48 and Tables 14.4 — 14.9. In the initialisation phase, the REDCR starts sending a frame containing a BST (Beacon Service Table) according to EN 12834 and EN 13372, 6.2, 6.3, 6.4 and 7.1 with settings as specified in the following Table 14.4. U.K.

Table 14.4
Initialisation — BST frame settings
Field	Settings
Link Identifier	Broadcast address
BeaconId	As per EN 12834
Time	As per EN 12834
Profile	No extension, 0 or 1 to be used
MandApplications	No extension, EID not present, Parameter not present, AID= 2 Freight&Fleet
NonMandApplications	Not present
ProfileList	No extension, number of profiles in list = 0
Fragmentation header	No fragmentation
Layer 2 settings	Command PDU, UI command

A practical example of the settings specified in Table 14.4, with an indication of bit encodings, is given in the following Table 14.5.

Table 14.5
Initialisation — BST frame contents example
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Broadcast ID		Broadcast address
3	MAC Control Field		Command PDU
4	LLC Control field		UI command
5	Fragmentation header		No fragmentation
6	BST		Initialisation request
	SEQUENCE {
	OPTION indicator BeaconID SEQUENCE { ManufacturerId INTEGER (0..65535)		NonMand applications not present
			Manufacturer Identifier
7
8
	IndividualID INTEGER (0..134217727) }		27 bit ID available for manufacturer
9
10
11
12	Time INTEGER (0..4294967295)		32 bit UNIX real time
13
14
15
16	Profile INTEGER (0..127,...)		No extension. Example profile 0
17	MandApplications SEQUENCE (SIZE(0..127,...)) OF {		No extension, Number of mandApplications = 1
18	SEQUENCE {
	OPTION indicator		EID not present
	OPTION indicator		Parameter not present
	AID DSRCApplicationEntityID } }		No extension. AID= 2 Freight&Fleet
19	ProfileList SEQUENCE (0..127,...) OF Profile }		No extension, number of profiles in list = 0
20	FCS		Frame check sequence
21
22	Flag		End Flag

DSC_45 A DSRC-VU, when receiving a BST, requires the allocation of a private window, as specified by EN 12795 and EN 13372, 7.1.1, with no specific RTM settings. Table 14.6 provides an example of bit encoding. U.K.

Table 14.6
Initialisation — Private window allocation request frame contents
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of specific DSRC-VU
3
4
5
6	MAC Control field		Private window request
7	FCS		Frame check sequence
8
9	Flag		End Flag

DSC_46 The REDCR then answers by allocating a private window, as specified by EN 12795 and EN 13372, 7.1.1 with no specific RTM settings. U.K.

Table 14.7 provides an example of bit encoding.

Table 14.7
Initialisation — Private window allocation frame contents
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of the specific DSRC-VU
3
4
5
6	MAC Control field		Private window allocation
7	FCS		Frame check sequence
8
9	Flag		End Flag

DSC_47 The DSRC-VU, when receiving the private window allocation, sends its VST (Vehicle Service Table) as defined in EN 12834 and EN 13372, 6.2, 6.3, 6.4 and 7.1 with settings as specified Table 14.8, using the allocated transmission window. U.K.

Table 14.8
Initialisation — VST frame settings
Field	Settings
Private LID	As per EN 12834
VST parameters	Fill=0, then for each supported application: EID present, parameter present, AID=2, EID as generated by the OBU
Parameter	No extension, Contains the RTM Context Mark
ObeConfiguration	The optional ObeStatus field may be present, but shall not be used by the REDCR
Fragmentation header	No fragmentation
Layer 2 settings	Command PDU, UI command

DSC_48 The DSRC-VU shall support the ‘Freight and Fleet’ application, identified by the Application Identifier ‘2’. Other Application Identifiers may be supported, but shall not be present in this VST, as the BST only requires AID=2. The ‘Applications’ field contains a list of the supported application instances in the DSRC-VU. For each supported application instantiation, a reference to the appropriate standard is given, made of an Rtm Context mark, which is composed of an OBJECT IDENTIFIER representing the related standard, its part (9 for RTM) and possibly its version, plus an EID that is generated by the DSRC-VU, and associated to that application instance. U.K.

A practical example of the settings specified in Table 14.8, with an indication of bit encodings, is given in Table 14.9.

Table 14.9
Initialisation — VST frame contents example
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of the specific DSRC-VU
3
4
5
6	MAC Control field		Command PDU
7	LLC Control field		UI command
8	Fragmentation header		No fragmentation
9	VST SEQUENCE {		Initialisation response
	Fill BIT STRING (SIZE(4))		Unused and set to 0
10	Profile INTEGER (0..127,...) Applications SEQUENCE OF {		No extension. Example profile 0
11			No extension, 1 application
12	SEQUENCE {
	OPTION indicator		EID present
	OPTION indicator		Parameter present
	AID DSRCApplicationEntityID		No extension. AID= 2 Freight&Fleet
13	EID Dsrc-EID		Defined within the OBU and identifying the application instance.
14	Parameter Container {		No extension, Container Choice = 02, Octet string
15			No extension, Rtm Context Mark length = 8
16	Rtm-ContextMark::= SEQUENCE { StandardIdentifier standardIdentifier		[F1 Object Identifier of the supported standard, part, and version. Example: ISO (1) Standard (0) TARV (15638) part9 (9) Version1 (1). First octet is 06H, which is the Object Identifier. Second octet is 06H, which is its length. Subsequent 6 octets encode the example Object Identifier.]
17
18
19
20
21
22
23
24	ObeConfiguration Sequence {
	OPTION indicator		ObeStatus not present
	EquipmentClass INTEGER (0..32767)
25
26	ManufacturerId INTEGER (0..65535)		Manufacturer identifier for the DSRC-VU as described in ISO 14816 Register
27
28	FCS		Frame check sequence
29
30	Flag		End Flag

DCS_49 The REDCR then reads the data by issuing a GET command, conforming to the GET command defined in EN 13372, 6.2, 6.3, 6.4 and EN 12834, with settings as specified in Table 14.10. U.K.

Table 14.10
Presentation — GET request frame settings
Field	Settings
Invoker Identifier (IID)	Not present
Link Identifier (LID)	Link address of the specific DSRC-VU
Chaining	No
Element Identifier (EID)	As specified in the VST. No extension
Access Credentials	No
AttributeIdList	No extension, 1 attribute, AttributeID = 1 (RtmData)
Fragmentation	No
Layer2 settings	Command PDU, Polled ACn command

Table 14.11 shows an example of reading the RTM data.

Table 14.11
Presentation — Get Request frame example
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of the specific DSRC-VU
3
4
5
6	MAC Control field		Command PDU
7	LLC Control field		Polled ACn command, n bit
8	Fragmentation header		No fragmentation
9	Get.request SEQUENCE {		Get request
	OPTION indicator		Access Credentials not present
	OPTION indicator		IID not present
	OPTION indicator		AttributeIdList present
	Fill BIT STRING(SIZE(1))		Set to 0.
10	EID INTEGER(0..127,…)		The EID of the RTM application instance, as specified in the VST. No extension
11	AttributeIdList SEQUENCE OF { AttributeId }}		No extension, number of attributes = 1
12			AttributeId=1, RtmData. No extension
13	FCS		Frame check sequence
14
15	Flag		End Flag

DSC_50 The DSRC-VU, when receiving the GET request, sends a GET response with the requested data conforming to the GET response defined in EN 13372, 6.2, 6.3, 6.4 and EN 12834, with settings as specified in Table 14.12. U.K.

Table 14.12
Presentation — GET response frame settings
Field	Settings
Invoker Identifier (IID)	Not present
Link Identifier (LID)	As per EN 12834
Chaining	No
Element Identifier (EID)	As specified in the VST.
Access Credentials	No
Fragmentation	No
Layer2 settings	Response PDU, Response available and command accepted, ACn command

Table 14.13 shows an example of reading the RTM data.

Table 14.13
Presentation — Response frame contents example
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of the specific DSRC-VU
3
4
5
6	MAC Control field		Response PDU
7	LLC Control field		Response available, ACn command n bit
8	LLC Status field		Response available and command accepted
9	Fragmentation header		No fragmentation
10	Get.response SEQUENCE {		Get response
	OPTION indicator		IID not present
	OPTION indicator		Attribute List present
	OPTION indicator		Return status not present
	Fill BIT STRING(SIZE(1))		Not used
11	EID INTEGER(0..127,…)		Responding from the RTM application Instance. No extension,
12	AttributeList SEQUENCE OF {		No extension, number of attributes = 1
13	Attributes SEQUENCE { AttributeId		No extension, AttributeId=1 (RtmData)
14	AttributeValue CONTAINER {		No extension, Container Choice = 1010.
15			RtmData
16
17
…		…
n	}}}}
n+1	FCS		Frame check sequence
n+2
n+3	Flag		End Flag

DSC_51 The REDCR then closes the connection by issuing a EVENT_REPORT, RELEASE command conforming to EN 13372, 6.2, 6.3, 6.4 and EN 12834,7.3.8, with no specific RTM settings. Table 14.14 shows a bit encoding example of the RELEASE command. U.K.

Table 14.14
Termination. EVENT_REPORT Release frame contents
Octet #	Attribute/Field	Bits in octet	Description
1	FLAG		Start flag
2	Private LID		Link address of the specific DSRC-VU
3
4
5
6	MAC Control field		The frame contains a command LPDU
7	LLC Control field		UI command
8	Fragmentation header		No fragmentation
9	EVENT_REPORT.request SEQUENCE {		EVENT_REPORT (Release)
	OPTION indicator		Access Credentials not present
	OPTION indicator		Event parameter not present
	OPTION indicator		IID not present
	Mode BOOLEAN		No response expected
10	EID INTEGER (0..127,…)		No extension, EID = 0 (System)
11	EventType INTEGER (0..127,…) }		Event type 0 = Release
12	FCS		Frame check sequence
13
14	Flag		End Flag

DSC_52 The DSRC-VU is not expected to answer to the Release command. The communication is then closed. U.K.