ETSI ETS 300 393-11 ed.1 (1998-12)
Terrestrial Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 11: Protocol Implementation Conformance Statement (PICS) proforma specification
Terrestrial Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 11: Protocol Implementation Conformance Statement (PICS) proforma specification
DE/TETRA-04004-11
Prizemni snopovni radio (TETRA) – Optimiran sistem za prenos paketiranih podatkov (PDO) – 11. del: Izjava o skladnosti izvedbe protokola (PICS) – Proforma specifikacija
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 393-11 E1:2003
01-december-2003
Prizemni snopovni radio (TETRA) – Optimiran sistem za prenos paketiranih
podatkov (PDO) – 11. del: Izjava o skladnosti izvedbe protokola (PICS) – Proforma
specifikacija
Terrestrial Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 11: Protocol
Implementation Conformance Statement (PICS) proforma specification
Ta slovenski standard je istoveten z: ETS 300 393-11 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 393-11 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 393-11 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 393-11 E1:2003
EUROPEAN ETS 300 393-11
TELECOMMUNICATION December 1998
STANDARD
Source: TETRA Reference: DE/TETRA-04004-11
ICS: 33.020
Key words: PICS, TETRA
Terrestrial Trunked Radio (TETRA);
Packet Data Optimized (PDO);
Part 11: Protocol Implementation Conformance Statement (PICS)
proforma specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1998. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 393-11 E1:2003
Page 2
ETS 300 393-11: December 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST ETS 300 393-11 E1:2003
Page 3
ETS 300 393-11: December 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Conformance to this PICS proforma specification .8
Annex A (normative): Protocol ICS proforma for ETS 300 393-2 .9
A.1 Guidance for completing the PICS proforma .9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions.9
A.1.3 Instructions for completing the PICS proforma.11
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 .12
A.2.4 Product supplier.13
A.2.5 Client.14
A.2.6 PICS contact person.14
A.3 Identification of the protocol .15
A.4 Global statement of conformance .15
A.5 Major capabilities.15
A.6 Connection Oriented Network Protocol (CONP) .15
A.7 Specific Connectionless Network Protocol.15
A.7.1 SCLNP procedures.15
A.7.2 SCLNP PDUs.16
A.7.3 SCLNP PDU elements.16
A.8 Mobility Management (MM).17
A.8.1 MM features.17
A.8.2 MM procedures.17
A.8.3 MM PDUs.18
A.8.4 MM PDU elements.19
A.8.5 MM timers .21
A.9 Mobile Link Entity (MLE).22
A.9.1 MLE features.22
A.9.2 MLE procedures.22
A.9.3 MLE PDUs .24
A.9.4 MLE timers.25
A.9.5 MLE PDU elements .25
A.10 Layer 2.26
A.10.1 Layer 2 PDUs.26
---------------------- Page: 5 ----------------------
SIST ETS 300 393-11 E1:2003
Page 4
ETS 300 393-11: December 1998
A.10.2 Layer 2 PDU elements .27
A.10.3 Logical Link Control (LLC). 28
A.10.3.1 LLC procedures . 28
A.10.3.2 LLC constants. 29
A.10.3.3 LLC timers . 29
A.10.4 Medium Access Control (MAC). 29
A.10.4.1 MAC procedures. 30
A.10.4.2 MAC constants . 31
A.10.4.3 MAC timers. 31
History. 32
---------------------- Page: 6 ----------------------
SIST ETS 300 393-11 E1:2003
Page 5
ETS 300 393-11: December 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
This ETS is a multi-part standard and will consist of the following parts:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 7: "Security";
Part 10: "SDL model of the Air Interface (AI)";
Part 11: "Protocol Implementation Conformance Statement (PICS) proforma specification".
Transposition dates
Date of adoption of this ETS: 27 November 1998
Date of latest announcement of this ETS (doa): 28 February 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1999
Date of withdrawal of any conflicting National Standard (dow): 31 August 1999
---------------------- Page: 7 ----------------------
SIST ETS 300 393-11 E1:2003
Page 6
ETS 300 393-11: December 1998
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 393-11 E1:2003
Page 7
ETS 300 393-11: December 1998
1 Scope
This ETS provides the Protocol Implementation Conformance Statement (PICS) proforma for the TETRA
Mobile Station (MS), Packet Data Optimized (PDO) Air Interface (AI) defined in ETS 300 393-2 [1] in
compliance with the relevant requirements, and in accordance with the relevant guidance given in
ISO/IEC 9646-7 [5], ETS 300 406 [2], and in ETR 212 [3].
The details of Supplementary Services (SS) and security aspects of PDO are outside the scope of this
ETS.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 393-2 (1996): "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 2: Air Interface
(AI)".
[2] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[3] ETR 212 (1995): "Methods for Testing and Specification (MTS); Implementation
Conformance Statement (ICS) proforma style guide".
[4] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts".
[5] ISO/IEC 9646-7 (1995): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation Conformance Statements".
[6] ISO/IEC 8208 (1995): "Information technology - Data Communications - X25
Packet Layer Protocol for Data Terminal equipment".
[7] ISO/IEC 8348 (1997): "Information technology - Open Systems
Interconnection - Network Service Definition".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 393-2 [1];
- terms defined in ISO/IEC 9646-1 [4] and in ISO/IEC 9646-7 [5].
In particular, the following terms defined in ISO/IEC 9646-1 [4] apply:
---------------------- Page: 9 ----------------------
SIST ETS 300 393-11 E1:2003
Page 8
ETS 300 393-11: December 1998
Implementation Conformance Statement (ICS): A statement made by the supplier of an implementation
or system claimed to conform to a given specification, stating which capabilities have been implemented.
The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.
ICS proforma: A document, in the form of a questionnaire, which when completed for an implementation
or system becomes an ICS.
Protocol ICS (PICS): An ICS for an implementation or system claimed to conform to a given protocol
specification.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AI Air Interface
BS Base Station
CONP Connection Oriented Network Protocol
DTMF Dual Tone Multi Frequency
ETS European Telecommunication Standard
ICS Implementation Conformance Statement
ITSI Individual TETRA Subscriber Identity
IUT Implementation Under Test
LLC Logical Link Control
LLME Lower Layer Management Entity
MAC Medium Access Control
MCC Mobile Country Code
MLE Mobile Link Entity
MM Mobility Management
MNC Mobile Network Code
MS Mobile Station
PDO Packet Data Optimized
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PTT Push To Talk
RES Radio Equipment and Systems
RPDI Radio Packet Data Infrastructure
SAP Service Access Point
SCLNP Specific Connectionless Network Protocol
SCS System Conformance Statement
SDU Service Data Unit
SP Service Primitive
SS Supplementary Services
SUT System Under Test
4 Conformance to this PICS proforma specification
If it claims to conform to this ETS, 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.
A PICS which conforms to this ETS shall be a conforming PICS proforma completed in accordance with
the guidance for completion given in clause A.1.
---------------------- Page: 10 ----------------------
SIST ETS 300 393-11 E1:2003
Page 9
ETS 300 393-11: December 1998
Annex A (normative): Protocol ICS proforma for ETS 300 393-2
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PICS.
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 ETS 300 393-2 [1] may provide information about the implementation in a
standardized manner.
The PICS proforma is subdivided into subclauses for the following categories of information:
- guidance for completing the PICS proforma;
- identification of the implementation;
- identification of the protocol;
- global statement of conformance;
- Mobility Management (MM);
- Mobile Link Entity (MLE);
- Logical Link Control (LLC);
- Medium Access Control (MAC);
- Connection Oriented Network Protocol (CONP);
- Specific Connectionless Network Protocol (SCLNP).
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprising information in tabular form in accordance with
the guide-lines presented in ISO/IEC 9646-7 [5].
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. elements, timers, etc.). It
implicitly means "is supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7 [5], 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.
---------------------- Page: 11 ----------------------
SIST ETS 300 393-11 E1:2003
Page 10
ETS 300 393-11: December 1998
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 gives reference to ETS 300 393-2 [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 [5], 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)
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
NOTE 1: As stated in ISO/IEC 9646-7 [5], support for a received Protocol Data Unit (PDU)
requires the ability to encode/decode all mandatory elements of that PDU. Supporting
a PDU while having no ability to encode/decode a mandatory element is
non-conformant. Support for an element of a PDU means that the semantics of that
element are supported. It does not mean that the element shall always be present in
the PDU.
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 1: 5 . 20
- list of values: , , .,
EXAMPLE 2: 2, 4, 6, 8, 9
EXAMPLE 3: '1101'B, '1011'B, '1111'B
---------------------- Page: 12 ----------------------
SIST ETS 300 393-11 E1:2003
Page 11
ETS 300 393-11: December 1998
EXAMPLE 4: '0A'H, '34'H, '2F'H
- list of named values: (), (), ., ()
EXAMPLE 5: reject(1), accept(2)
- length: size ( . )
EXAMPLE 6: 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.
References to items
For each possible item answer (answer in the support column) within the PICS proforma exists a unique
reference, 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 7: A.5/4 is the reference to the answer of item 4, in table 5 of annex A.
EXAMPLE 8: 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 in the beginning of a clause or table indicates that the whole clause or the whole table
is not required to be completed if the predicate is FALSE.
NOTE 2: In this PICS proforma, all the tables have a prerequisite independently on the status of
the predicate referred to being mandatory or optional. This is done for readability
reasons.
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 subclause A.1.2.
If necessary, the supplier may provide additional comments in space at the bottom of the tables, or
separately on sheets of paper.
More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.
---------------------- Page: 13 ----------------------
SIST ETS 300 393-11 E1:2003
Page 12
ETS 300 393-11: December 1998
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:
........................................................................................................................................................................
A.2.3 System Under Test (SUT) identification
SUT name:
........................................................................................................................................................................
........................................................................................................................................................................
Hardware configuration:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Operating system:
........................................................................................................................................................................
---------------------- Page: 14 ----------------------
SIST ETS 300 393-11 E1:2003
Page 13
ETS 300 393-11: December 1998
A.2.4 Product supplier
Name:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
---------------------- Page: 15 ----------------------
SIST ETS 300 393-11 E1:2003
Page 14
ETS 300 393-11: December 1998
A.2.5 Client
(If different from product supplier)
Name:
........................................................................................................................................................................
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:
........................................................................................................................................................................
........................................................................................................................................................................
---------------------- Page: 16 ----------------------
SIST ETS 300 393-11 E1:2003
Page 15
ETS 300 393-11: December 1998
A.3 Identification of the protocol
This PICS proforma applies to the following standard:
ETS 300 393-2 (1996): "Radio Equipment and Systems (RES); Trans-European Trunked Radio (TETRA);
Packet Data Optimized (PDO); Part 2: Air Interface (AI)".
A.4 Global statement of conformance
Are all mandatory capabilities implemented? (Yes/No) .
NOTE: Answering "No" to this question indicates non-conformance to the protocol
specification. Non-supported mandatory capabilities are to be identified in the PICS,
with an explanation of why the implementation is non-conforming, on pages attached
to the PICS proforma.
A.5 Major capabilities
The supplier of the implementation shall state the support of the implementation for each of the following
protocol entities, in table A.1.
Table A.1: Entities supported
Item Entity Reference Status Support
1 Connection Oriented Network Protocol (CONP) 11, 12 o.1
2 Specific Connectionless Protocol (SCLNP) 13, 14 o.1
3 Mobility Management (MM) 15, 16 m
4 Mobile Link Entity (MLE) 17, 18 m
5 Logical Link Control (LLC) 20, 21 m
6 Medium Access Control (MAC) 20, 22 m
o.1 It is mandatory to support at least one of these items.
A.6 Connection Oriented Network Prot
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.