ANNEX I CRequirements for construction, testing, installation, and inspection

Appendix 14

REMOTE COMMUNICATION FUNCTION

5.REMOTE COMMUNICATION DESIGN AND PROTOCOLS

5.4DSRC Protocol requirements for RTM

5.4.7Detailed DSRC transaction description

DSC_44Initialisation 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.

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

Image_r00710

Start flag

2

Broadcast ID

Image_r00711

Broadcast address

3

MAC Control Field

Image_r00712

Command PDU

4

LLC Control field

Image_r00713

UI command

5

Fragmentation header

Image_r00714

No fragmentation

6

BST

Image_r00715

Initialisation request

SEQUENCE {

OPTION indicator

BeaconID

SEQUENCE {

ManufacturerId

INTEGER (0..65535)

Image_r00716

NonMand applications not present

Image_r00717

Manufacturer Identifier

7

Image_r00718

8

Image_r00719

IndividualID

INTEGER (0..134217727)

}

Image_r00720

27 bit ID available for manufacturer

9

Image_r00721

10

Image_r00722

11

Image_r00723

12

Time

INTEGER (0..4294967295)

Image_r00724

32 bit UNIX real time

13

Image_r00725

14

Image_r00726

15

Image_r00727

16

Profile

INTEGER (0..127,...)

Image_r00728

No extension. Example profile 0

17

MandApplications

SEQUENCE (SIZE(0..127,...)) OF {

Image_r00729

No extension, Number of mandApplications = 1

18

SEQUENCE {

OPTION indicator

Image_r00730

EID not present

OPTION indicator

Image_r00731

Parameter not present

AID

DSRCApplicationEntityID } }

Image_r00732

No extension. AID= 2 Freight&Fleet

19

ProfileList

SEQUENCE (0..127,...) OF Profile }

Image_r00733

No extension, number of profiles in list = 0

20

FCS

Image_r00734

Frame check sequence

21

Image_r00735

22

Flag

Image_r00736

End Flag

DSC_45A 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.

Table 14.6

Initialisation — Private window allocation request frame contents

Octet #

Attribute/Field

Bits in octet

Description

1

FLAG

Image_r00737

Start flag

2

Private LID

Image_r00738

Link address of specific DSRC-VU

3

Image_r00739

4

Image_r00740

5

Image_r00741

6

MAC Control field

Image_r00742

Private window request

7

FCS

Image_r00743

Frame check sequence

8

Image_r00744

9

Flag

Image_r00745

End Flag

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

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

Image_r00746

Start flag

2

Private LID

Image_r00747

Link address of the specific DSRC-VU

3

Image_r00748

4

Image_r00749

5

Image_r00750

6

MAC Control field

Image_r00751

Private window allocation

7

FCS

Image_r00752

Frame check sequence

8

Image_r00753

9

Flag

Image_r00754

End Flag

DSC_47The 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.

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_48The 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.

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

Image_r00755

Start flag

2

Private LID

Image_r00756

Link address of the specific DSRC-VU

3

Image_r00757

4

Image_r00758

5

Image_r00759

6

MAC Control field

Image_r00760

Command PDU

7

LLC Control field

Image_r00761

UI command

8

Fragmentation header

Image_r00762

No fragmentation

9

VST

SEQUENCE {

Image_r00763

Initialisation response

Fill

BIT STRING (SIZE(4))

Image_r00764

Unused and set to 0

10

Profile

INTEGER (0..127,...)

Applications

SEQUENCE OF {

Image_r00765

No extension. Example profile 0

11

Image_r00766

No extension, 1 application

12

SEQUENCE {

OPTION indicator

Image_r00767

EID present

OPTION indicator

Image_r00768

Parameter present

AID

DSRCApplicationEntityID

Image_r00769

No extension. AID= 2 Freight&Fleet

13

EID Dsrc-EID

Image_r00770

Defined within the OBU and identifying the application instance.

14

Parameter Container {

Image_r00771

No extension, Container Choice = 02, Octet string

15

Image_r00772

No extension, Rtm Context Mark length = 8

16

Rtm-ContextMark::= SEQUENCE {

StandardIdentifier

standardIdentifier

Image_r00773

F1Object 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

Image_r00774

18

Image_r00775

19

Image_r00776

20

Image_r00777

21

Image_r00778

22

Image_r00779

23

Image_r00780

24

ObeConfiguration Sequence {

OPTION indicator

Image_r00781

ObeStatus not present

EquipmentClass

INTEGER (0..32767)

Image_r00782

25

Image_r00783

26

ManufacturerId

INTEGER (0..65535)

Image_r00784

Manufacturer identifier for the DSRC-VU as described in ISO 14816 Register

27

Image_r00785

28

FCS

Image_r00786

Frame check sequence

29

Image_r00787

30

Flag

Image_r00788

End Flag

DCS_49The 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.

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

Image_r00789

Start flag

2

Private LID

Image_r00790

Link address of the specific DSRC-VU

3

Image_r00791

4

Image_r00792

5

Image_r00793

6

MAC Control field

Image_r00794

Command PDU

7

LLC Control field

Image_r00795

Polled ACn command, n bit

8

Fragmentation header

Image_r00796

No fragmentation

9

Get.request

SEQUENCE {

Image_r00797

Get request

OPTION indicator

Image_r00798

Access Credentials not present

OPTION indicator

Image_r00799

IID not present

OPTION indicator

Image_r00800

AttributeIdList present

Fill

BIT STRING(SIZE(1))

Image_r00801

Set to 0.

10

EID INTEGER(0..127,…)

Image_r00802

The EID of the RTM application instance, as specified in the VST. No extension

11

AttributeIdList SEQUENCE OF {

AttributeId }}

Image_r00803

No extension, number of attributes = 1

12

Image_r00804

AttributeId=1, RtmData. No extension

13

FCS

Image_r00805

Frame check sequence

14

Image_r00806

15

Flag

Image_r00807

End Flag

DSC_50The 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.

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

Image_r00808

Start flag

2

Private LID

Image_r00809

Link address of the specific DSRC-VU

3

Image_r00810

4

Image_r00811

5

Image_r00812

6

MAC Control field

Image_r00813

Response PDU

7

LLC Control field

Image_r00814

Response available, ACn command n bit

8

LLC Status field

Image_r00815

Response available and command accepted

9

Fragmentation header

Image_r00816

No fragmentation

10

Get.response

SEQUENCE {

Image_r00817

Get response

OPTION indicator

Image_r00818

IID not present

OPTION indicator

Image_r00819

Attribute List present

OPTION indicator

Image_r00820

Return status not present

Fill

BIT STRING(SIZE(1))

Image_r00821

Not used

11

EID

INTEGER(0..127,…)

Image_r00822

Responding from the RTM application

Instance. No extension,

12

AttributeList

SEQUENCE OF {

Image_r00823

No extension, number of attributes = 1

13

Attributes

SEQUENCE {

AttributeId

Image_r00824

No extension, AttributeId=1 (RtmData)

14

AttributeValue

CONTAINER {

Image_r00825

No extension, Container Choice = 1010.

15

Image_r00826

RtmData

16

Image_r00827

17

Image_r00828

…

…

n

}}}}

Image_r00829

n+1

FCS

Image_r00830

Frame check sequence

n+2

Image_r00831

n+3

Flag

Image_r00832

End Flag

DSC_51The 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.

Table 14.14

Termination. EVENT_REPORT Release frame contents

Octet #

Attribute/Field

Bits in octet

Description

1

FLAG

Image_r00833

Start flag

2

Private LID

Image_r00834

Link address of the specific DSRC-VU

3

Image_r00835

4

Image_r00836

5

Image_r00837

6

MAC Control field

Image_r00838

The frame contains a command LPDU

7

LLC Control field

Image_r00839

UI command

8

Fragmentation header

Image_r00840

No fragmentation

9

EVENT_REPORT.request

SEQUENCE {

Image_r00841

EVENT_REPORT (Release)

OPTION indicator

Image_r00842

Access Credentials not present

OPTION indicator

Image_r00843

Event parameter not present

OPTION indicator

Image_r00844

IID not present

Mode

BOOLEAN

Image_r00845

No response expected

10

EID

INTEGER (0..127,…)

Image_r00846

No extension, EID = 0 (System)

11

EventType

INTEGER (0..127,…) }

Image_r00847

Event type 0 = Release

12

FCS

Image_r00848

Frame check sequence

13

Image_r00849

14

Flag

Image_r00850

End Flag

DSC_52

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