ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment; Part 2: DSRC application layer; Sub-Part 1: Protocol Implementation Conformance Statement (PICS) proforma specification
Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment; Part 2: DSRC application layer; Sub-Part 1: Protocol Implementation Conformance Statement (PICS) proforma specification
RTS/ITS-0040008
General Information
Standards Content (Sample)
Technical Specification
Intelligent Transport Systems (ITS);
Road Transport and Traffic Telematics (RTTT);
Test specifications for Dedicated Short
Range Communication (DSRC) transmission equipment;
Part 2: DSRC application layer;
Sub-Part 1: Protocol Implementation Conformance
Statement (PICS) proforma specification
2 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Reference
RTS/ITS-0040008
Keywords
ITS, DSRC, application, PICS, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Overview of the templates . 9
5 Conformance requirement concerning PICS . 9
Annex A (normative): ICS proforma for DSRC application layer for OBU . 10
A.1 Guidance for completing the PICS proforma . 10
A.1.1 Purposes and structure . 10
A.1.2 Abbreviations and conventions . 10
A.1.3 Instructions for completing the PICS proforma. 12
A.2 Identification of the implementation . 12
A.2.1 Date of the statement . 12
A.2.2 Implementation Under Test (IUT) identification . 12
A.2.3 System Under Test (SUT) identification . 13
A.2.4 Product supplier . 13
A.2.5 Client (if different from product supplier) . 13
A.2.6 PICS contact person . 14
A.3 Identification of the protocol . 14
A.4 Global statement of conformance . 15
A.5 Kernels . 15
A.6 Initialization Kernel . 15
A.6.1 Procedures . 15
A.6.2 PDU . 15
A.7 Transport Kernel . 16
A.7.1 Procedures . 16
A.7.2 PDU . 17
A.8 Broadcast Kernel . 20
A.8.1 Procedures . 20
A.8.2 PDU . 20
A.9 ASN.1 Data Types . 21
A.9.1 Extendable data types . 21
A.9.2 Extendable lists . 21
Annex B (normative): ICS proforma for DSRC application layer for RSU . 22
B.1 Guidance for completing the PICS proforma . 22
B.1.1 Purposes and structure . 22
B.1.2 Abbreviations and conventions . 22
B.1.3 Instructions for completing the PICS proforma. 24
B.2 Identification of the implementation . 24
B.2.1 Date of the statement . 24
ETSI
4 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
B.2.2 Implementation Under Test (IUT) identification . 24
B.2.3 System Under Test (SUT) identification . 25
B.2.4 Product supplier . 25
B.2.5 Client (if different from product supplier) . 25
B.2.6 PICS contact person . 26
B.3 Identification of the protocol . 26
B.4 Global statement of conformance . 27
B.5 Kernels . 27
B.6 Initialization Kernel . 27
B.6.1 Procedures . 27
B.6.2 PDU . 27
B.7 Transport Kernel . 28
B.7.1 Procedures . 28
B.7.2 PDU . 29
B.8 Broadcast Kernel . 32
B.8.1 Procedures . 32
B.8.2 PDU . 32
B.9 ASN.1 Data Types . 33
B.9.1 Extendable data types . 33
B.9.2 Extendable lists . 33
Annex C (normative): Profile Requirement List for RTTT profile of DSRC application
layer for OBU . 34
C.1 General . 34
C.1.1 Profile Requirement List (profile RL) . 34
C.2 Identification of the profile . 34
C.3 Kernels . 35
C.4 Initialization Kernel . 35
C.5 Transport Kernel . 35
C.5.1 PDU . 35
C.6 ASN.1 Data Types . 36
C.6.1 Extendable data types . 36
C.6.2 Extendable lists . 36
Annex D (normative): Profile Requirement List for RTTT profile of DSRC application
layer for RSU . 37
D.1 General . 37
D.1.1 Profile Requirement List (profile RL) . 37
D.2 Identification of the profile . 37
D.3 Kernels . 38
D.4 Initialization Kernel . 38
D.5 Transport Kernel . 38
D.5.1 PDU . 38
D.6 ASN.1 Data Types . 39
D.6.1 Extendable data types . 39
D.6.2 Extendable lists . 39
Annex E (normative): Profile specific ICS proforma for RTTT profile of DSRC application
layer for OBU . 40
ETSI
5 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
E.1 Guidance for completing the profile ICS proforma . 40
E.1.1 Purposes and structure . 40
E.1.2 Abbreviations and conventions . 40
E.1.3 Instructions for completing the profile ICS proforma . 42
E.2 Identification of the implementation . 42
E.2.1 Date of the statement . 42
E.2.2 Implementation Under Test (IUT) identification . 42
E.2.3 System Under Test (SUT) identification . 43
E.2.4 Product supplier . 43
E.2.5 Client (if different from product supplier) . 43
E.2.6 Profile ICS contact person . 44
E.3 Identification of the profile . 44
E.4 Global statement of conformance . 45
E.5 Profiles . 45
E.6 Interlayer Relations . 45
E.6.1 Receiver . 45
E.6.2 Transmitter . 46
Annex F (normative): Profile specific ICS proforma for RTTT profile of DSRC application
layer for RSU . 47
F.1 Guidance for completing the profile ICS proforma . 47
F.1.1 Purposes and structure . 47
F.1.2 Abbreviations and conventions . 47
F.1.3 Instructions for completing the profile ICS proforma . 49
F.2 Identification of the implementation . 49
F.2.1 Date of the statement . 49
F.2.2 Implementation Under Test (IUT) identification . 49
F.2.3 System Under Test (SUT) identification . 50
F.2.4 Product supplier . 50
F.2.5 Client (if different from product supplier) . 50
F.2.6 Profile ICS contact person . 51
F.3 Identification of the profile . 51
F.4 Global statement of conformance . 52
F.5 Profiles . 52
F.6 Interlayer Relations . 52
F.6.1 Transmitter . 52
F.6.2 Receiver . 53
History . 54
ETSI
6 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport System(ITS).
The present document is part 2, sub-part 1 of a multi-part deliverable covering Intelligent Transport Systems (ITS);
Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated ShortRange Communication (DSRC)
transmission equipment as identified belowas identified below:
Part 1: "DSRC data link layer: medium access and logical link control";
Part 2: "DSRC application layer":
Sub-part 1: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Sub-part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Sub-part 3: "Abstract Test Suite (ATS) and partial PIXIT proforma".
ETSI
7 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
1 Scope
The present document specifies partial Protocol Implementation Conformance Statement (PICS) proformas for the
application layer of CEN DSRC as defined in EN 12834 [1], in compliance with the relevant requirements, and in
accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5].
This proforma is intended for use by suppliers of equipment which is claimed to conform to the CEN DSRC application
layer, as specified in EN 12834 [1].
The present document also contains profile Implementation Conformance Statement (ICS) proformas and profile
Requirements Lists for the application layer for use by suppliers of equipment which is claimed to conform to
EN 13372 [2], DSRC Profiles for RTTT.
To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and
options have been implemented for a telecommunication specification. Such a statement is called an Implementation
Conformance Statement (ICS). The present document provides proforma ICS templates, to be filled in by equipment
suppliers.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] CEN EN 12834 (2003): "Road transport and traffic telematics - Dedicated Short Range
Communication (DSRC). DSRC application layer".
[2] CEN EN 13372 (2004): "Road Transport and Traffic Telematics (RTTT) - Dedicated short-range
communication - Profiles for RTTT applications".
[3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concept".
ETSI
8 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
[4] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 12834 [1], EN 13372 [2],
ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply:
Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system
claimed to conform to a given specification, stating which capabilities have been implemented
NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS,
etc.
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes an ICS
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in EN 12834 [1], EN 13372 [2], ISO/IEC 9646-1 [3],
ISO/IEC 9646-7 [4] and the following apply:
DSRC Dedicated Short Range Communication
ICS Implementation Conformance Statement
IUT Implementation Under Test
ME Mobile Equipment
OBU On Board Unit
NOTE: An alternative descriptor to Mobile Equipment.
PICS Protocol Implementation Conformance Statement
RL Requirements List
RSU Road Side Unit
NOTE: An alternative descriptor to Fixed Equipment.
RTTT Road Transport and Traffic Telematics
SUT System Under Test
ETSI
9 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
4 Overview of the templates
The present document contains separate PICS templates for On Board Unit (OBU) and Road Side Unit (RSU). These
can be found in annexes A and B respectively.
In addition, the present document contains profile Requirement Lists (RL) and profile-specific ICS proformas for
equipment claimed to conform to EN 13372 [2]. Again, these exist for the OBU and for the RSU.
5 Conformance requirement concerning PICS
If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be
technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and
ordering of the proforma items.
An ICS which conforms to the present document shall be a conforming PICS proforma completed in accordance with
the instructions for completion given at the start of each annex.
ETSI
10 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Annex A (normative):
ICS proforma for DSRC application layer for OBU
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the ICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed ICS.
A.1 Guidance for completing the PICS proforma
A.1.1 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in EN 12834 [1] may provide information about the implementation in a standardized manner.
The PICS proforma is subdivided into clauses for the following categories of information:
• guidance for completing the PICS proforma;
• identification of the implementation;
• identification of the protocol;
• global statement of conformance;
• PICS proforma tables:
- Kernels;
- Initialization Kernel;
- Transport Kernel;
- Broadcast Kernel;
- ASN.1 Data Types.
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the
guidelines presented in ISO/IEC 9646-7 [4].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is supported by the implementation?".
ETSI
11 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Status column
The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.
x prohibited (excluded) - there is a requirement not to use this capability in the given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which
identifies a unique group of related optional items and the logic of their selection which is defined
immediately following the table.
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying a unique conditional status
expression which is defined immediately following the table.
Reference column
The reference column makes reference to EN 12834 [1], except where explicitly stated otherwise.
Support column
The support column shall be filled in by the supplier of the implementation. The following common notations, defined
in ISO/IEC 9646-7 [4], are used for the support column:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
NOTE: As stated in ISO/IEC 9646-7 [4], support for a received PDU requires the ability to parse all valid
parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is
non-conformant. Support for a parameter on a PDU means that the semantics of that parameter are
supported.
Values allowed column
The values allowed column contains the type, the list, the range, or the length of values allowed. The following
notations are used:
- range of values: .
example: 5 . 20
- list of values: , , .,
example: 2, 4, 6, 8, 9
example: '1101'B, '1011'B, '1111'B
example: '0A'H, '34'H, '2F'H
- list of named values: (), (), ., ()
example: reject(1), accept(2)
- length: size ( . )
example: size (1 . 8)
Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the values or the
ranges of values supported by the implementation shall be indicated.
ETSI
12 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
References to items
For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists,
used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/",
followed by the item number in the table. If there is more than one support column in a table, the columns are
discriminated by letters (a, b, etc.), respectively.
EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in
table 6 of annex A.
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be
completed if the predicate is FALSE.
A.1.3 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an
explicit answer shall be entered, in each of the support or supported column boxes provided, using the notation
described in clause A.1.2.
If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately.
A.2 Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides (the
System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and
configuration options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
A.2.1 Date of the statement
.........................................................................................................................................................................................
A.2.2 Implementation Under Test (IUT) identification
IUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
IUT version:
.........................................................................................................................................................................................
ETSI
13 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
A.2.3 System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Operating system:
.........................................................................................................................................................................................
A.2.4 Product supplier
Name:
.........................................................................................................................................................................................
Address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
Additional information:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.2.5 Client (if different from product supplier)
Name:
.........................................................................................................................................................................................
ETSI
14 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
Address:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
Additional information:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.2.6 PICS contact person
(A person to contact if there are any queries concerning the content of the PICS)
Name:
.........................................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................................
Additional information:
.........................................................................................................................................................................................
.........................................................................................................................................................................................
.........................................................................................................................................................................................
A.3 Identification of the protocol
This PICS proforma applies to the following standard:
EN 12834 [1]: "Road transport and traffic telematics - Dedicated Short Range Communication (DSRC) - DSRC
application layer". This PICS proforma applies only for On-Board Units.
ETSI
15 ETSI TS 102 486-2-1 V1.2.1 (2008-10)
A.4 Global statement of conformance
Are all mandatory capabilities implemented? (Yes/No) .
NOTE: Answering "No" to this questi
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...