ETSI ETS 300 402-4 ed.1 (1996-09)

Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 4: Protocol Implementation Conformance Statement (PICS) proforma specification for the general protocol

DE/SPS-05052

Digitalno omrežje z integriranimi storitvami (ISDN) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - Podatkovna povezovalna plast - 4. del: Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacije za splošni protokol

General Information

• Status: Published
• Publication Date: 12-Sep-1996
• Technical Committee: SPS 5 - Digital access signalling
• Current Stage: 12 - Completion
• Due Date: 27-Sep-1996
• Completion Date: 13-Sep-1996
• Ref Project: SIST ETS 300 402-4:1998 - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 4: Protocol Implementation Conformance Statement (PICS) proforma specification for the general protocol

Standards Content (Sample)

SLOVENSKI STANDARD
01-junij-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'663RGDWNRYQDSRYH]RYDOQDSODVWGHO,]MDYDR
VNODGQRVWLL]YHGEHSURWRNROD3,&63URIRUPDVSHFLILNDFLMH]DVSORãQLSURWRNRO
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Data link layer; Part 4: Protocol Implementation Conformance
Statement (PICS) proforma specification for the general protocol
Ta slovenski standard je istoveten z: ETS 300 402-4 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.100.20 Podatkovni povezovalni sloj Data link layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 402-4
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05052
ICS: 33.020, 33.080, 35.100.20
Key words: ISDN, DSS1, layer 2, D-channel, LAPD, PICS
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Data link layer;
Part 4: Protocol Implementation Conformance Statement (PICS)
proforma specification for the general protocol
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
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 1996. All rights reserved.

Page 2
ETS 300 402-4: September 1996
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 Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 402-4: September 1996
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Conformance.8
Annex A (normative): PICS proforma for ETS 300 402-2 .9
A.1 Guidance for completing the PICS proforma .9
A.1.1 Purpose and structure .9
A.1.2 Symbols, abbreviations and conventions.9
A.1.3 Instructions for completing the PICS proforma.10
A.2 Identification of the implementation.11
A.2.1 Date of the statement .11
A.2.2 Implementation Under Test (IUT) identification .11
A.2.3 System Under Test (SUT) identification .11
A.2.4 Product supplier.11
A.2.5 Client.12
A.2.6 PICS contact person.13
A.3 Identification of the protocol to which this PICS proforma applies .13
A.4 The PICS proforma tables.13
A.4.1 Correspondence to a physical interface.13
A.4.2 Structure of the tables.14
A.5 Global statement of conformance .14
A.6 Roles .14
A.7 User.15
A.7.1 Major capabilities .15
A.7.2 Subsidiary capabilities.16
A.7.3 Protocol data units .17
A.7.3.1 Frames received by the user.17
A.7.3.2 Frames transmitted by the user .18
A.7.4 PDU parameters .19
A.7.4.1 Service data units.19
A.7.4.1.1 Service data units received by the user.19
A.7.4.1.2 Service data units transmitted by the user.19
A.7.4.2 Address field variables .20
A.7.5 Timers.21
A.7.6 System parameters.21

Page 4
ETS 300 402-4: September 1996
A.8 Network. 22
A.8.1 Major capabilities. 22
A.8.2 Subsidiary capabilities. 23
A.8.3 Protocol data units. 23
A.8.3.1 Frames received by the network. 23
A.8.3.2 Frames transmitted by the network . 24
A.8.4 PDU parameters . 24
A.8.4.1 Service data units . 24
A.8.4.1.1 Service data units received by the network. 24
A.8.4.1.2 Service data units transmitted by the network . 25
A.8.4.2 Address field variables. 25
A.8.5 Timers . 26
A.8.6 System parameters . 26
Annex B (normative): PICS proforma for annex ZA of ETS 300 402-2 . 27
B.1 Guidance for completing the PICS proforma. 27
B.1.1 Purpose and structure. 27
B.1.2 Symbols, abbreviations and conventions. 27
B.1.3 Instructions for completing the PICS proforma . 28
B.2 Identification of the implementation . 28
B.2.1 Date of the statement. 28
B.2.2 Implementation Under Test (IUT) identification . 28
B.2.3 System Under Test (SUT) identification. 29
B.2.4 Product supplier . 29
B.2.5 Client . 30
B.2.6 PICS contact person . 30
B.3 Identification of the protocol to which this PICS proforma applies. 31
B.4 The PICS proforma tables. 31
B.4.1 Correspondence to a physical interface. 31
B.4.2 Structure of the tables . 31
B.5 Global statement of conformance . 31
B.6 Roles. 31
B.7 PICS questions. 32
B.7.1 Major capabilities. 32
B.7.2 Subsidiary capabilities. 32
B.7.3 Protocol data units. 33
B.7.3.1 Frames received. 33
B.7.3.2 Frames transmitted. 34
B.7.4 PDU parameters . 34
B.7.5 Timers . 35
B.7.6 System parameters . 35
History. 36

Page 5
ETS 300 402-4: September 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 4 of a multi-part standard covering the Integrated Services Digital Network (ISDN) Digital
Subscriber Signalling System No. one (DSS1) data link layer specification as described below:
Part 1: "General aspects [ITU-T Recommendation Q.920 (1993), modified]";
Part 2: "General protocol specification [ITU-T Recommendation Q.921 (1993), modified]";
Part 3: "Frame relay protocol specification";
Part 4: "Protocol Implementation Conformance Statement (PICS) proforma specification for
the general protocol";
Part 5: "PICS proforma specification for the frame relay protocol";
Part 6: "Test Suite Structure and Test Purposes (TSS&TP) specification for the general protocol";
Part 7: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the general protocol".
Transposition dates
Date of adoption of this ETS: 6 September 1996
Date of latest announcement of this ETS (doa): 31 December 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1997
Date of withdrawal of any conflicting National Standard (dow): 30 June 1997
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which
capabilities and options have been implemented for a given Open Systems Interconnection (OSI)
protocol. Such a statement is called an Implementation Conformance Statement (ICS). An ICS stating
what capabilities and options have been implemented for a particular protocol is called a protocol ICS.
This is commonly abbreviated to "PICS".

Page 6
ETS 300 402-4: September 1996
Blank page
Page 7
ETS 300 402-4: September 1996
1 Scope
This fourth part of ETS 300 402 provides the Protocol Implementation Conformance Statement (PICS)
proforma for the Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one
(DSS1) protocol data link layer general protocol as specified in ETS 300 402-2 [1] in compliance with the
relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3].
The supplier of an implementation that is claimed to conform to ETS 300 402-2 [1] is required to complete
a copy of the PICS proforma provided in annex A of this ETS.
The supplier of an implementation that is claimed to conform to annex ZA of ETS 300 402-2 [1] is required
to complete a copy of the PICS proforma provided in annex B 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 402-2 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2:
General protocol specification [ITU-T Recommendation Q.921 (1993),
modified]".
[2] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[3] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, in addition to those in ETS 300 402-2 [1],
ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [3]:
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, and information object ICS
(see ISO/IEC 9646-1 [2]).
network: The DSS1 protocol entity at the network side of the user-network interface.
Protocol Implementation Conformance Statement (PICS): An ICS for an implementation or system
claimed to conform to a given specification (see ISO/IEC 9646-1 [2]).
PICS proforma: A document, in the form of a questionnaire, which when completed for an
implementation or system becomes a PICS (see ISO/IEC 9646-1 [2]).
user: The DSS1 protocol entity at the user side of the user-network interface.

Page 8
ETS 300 402-4: September 1996
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AND Boolean "and"
DL Data Link
DSS1 Digital Subscriber Signalling System No. one
FR Frames Received
FT Frames Transmitted
ICS Implementation Conformance Statement
ISDN Integrated Services Digital Network
IUT Implementation Under Test
M Mandatory requirement (to be observed in all cases)
MC Major Capabilities
N/A Not applicable, not supported or the conditions for status are not met
No not supported
NOT Boolean "not"
O Option (may be selected to suit the implementation, provided that any
requirements applicable to the option are observed)
O.n Options, but support required for either at least one or only one of the options in
the group labelled with the same numeral "n"
OR Boolean "or"
OSI Open Systems Interconnection
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PR Parameter Received
PT Parameter Transmitted
R Role
SAP Service Access Point
SAPI Service Access Point Identifier
SC Subsidiary Capabilities
SCS System Conformance Statement
SDU Service Data Unit
SP System Parameter
SUT System Under Test
TEI Terminal Endpoint Identifier
TM Timer
Yes supported
4 Conformance
A PICS proforma that conforms to this PICS proforma specification shall be technically equivalent to either
annex A or annex B, and shall preserve the numbering and ordering of the items in annex A or annex B,
respectively.
A PICS that conforms to this PICS proforma specification shall:
a) describe an implementation which conforms to the main text or to annex ZA of ETS 300 402-2 [1] ;
b) be a conforming PICS proforma, which has been completed in accordance with the instructions for
completion given in clauses A.1 or B.1, respectively; and
c) include the information necessary to uniquely identify both the supplier and the implementation.

Page 9
ETS 300 402-4: September 1996
Annex A (normative): PICS proforma for ETS 300 402-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 Purpose 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 402-2 [1] may provide information in a standardized manner.
The PICS proforma is subdivided into clauses as follows:
A.1: instructions for completing the various parts of the PICS proforma;
A.2: identification of the implementation;
A.3: identification of the protocol to which this PICS proforma applies;
A.4: explanation of the PICS proforma tables;
A.5: global statement of conformance;
A.6: questions to determine roles;
A.7: questions for the user role; and
A.8: questions for the network role.
A.1.2 Symbols, 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 [3].
Item column:
The item column contains a unique reference (a mnemonic plus a number) for each item within the PICS
proforma.
An additional lower case letter has been added to differentiate PICS items related to the user role (e.g.
MCu) and PICS items related to the network role (e.g. MCn). In earlier PICS proformas both these cases
were identified by the same mnemonic (e.g. MC).
Item description column:
The item description contains a brief summary of the static requirement for which a support answer is
required.
Conditions for status column:
The conditions for status column contains a specification, if appropriate, of the predicate upon which a
conditional status is based.
Page 10
ETS 300 402-4: September 1996
Status column:
The following notations, defined in ISO/IEC 9646-7 [3], 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.
O.i qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer that identifies an unique group of related optional items and the logic
of their selection, defined below the table.
X eXcluded or prohibited - there is a requirement not to use this capability in a
given context.
NOTE: To support a capability means that the capability is implemented in conformance to
ETS 300 402-2 [1].
Reference column:
Except where explicitly stated, the reference column refers to the appropriate parts of ETS 300 402-2 [1]
describing the particular item.
NOTE: A reference indicates only the location of the most essential information about an item.
All additional requirements contained in ETS 300 402-2 [1] have also to be taken into
account when making a statement about the conformance of that particular item.
Support column:
The following notation, defined in ISO/IEC 9646-7 [3], is used for the support column:
[ ] Yes [ ] No Tick "Yes" if item is supported, tick "No" if item is not supported.
[ ] N/A Tick "N/A" if the item is "not applicable".
Prerequisite line:
A prerequisite line takes the form: Prerequisite: .
A prerequisite line after a subclause heading or table title indicates that the whole subclause 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. For each row in each PICS
proforma table the supplier shall enter an explicit answer (i.e. by ticking the appropriate "Yes", "No", or
"N/A" in each of the support column boxes provided. Where a support column box is left blank, or where it
is marked "N/A" without any tick box, no answer is required. If necessary, the supplier may enter additional
comments at the end of each table, or separately.
More detailed instructions may be found at the beginning of each subclause of the proforma.

Page 11
ETS 300 402-4: September 1996
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 to provide as much detail as possible regarding version numbers
and configuration options.
The product supplier 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:
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.4 Product supplier
Name:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................

Page 12
ETS 300 402-4: September 1996
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
A.2.5 Client
Name:
........................................................................................................................................................................
E-mail address:
........................................................................................................................................................................
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................

Page 13
ETS 300 402-4: September 1996
A.2.6 PICS contact person
Name:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.3 Identification of the protocol to which this PICS proforma applies
This PICS proforma applies to the following standard:
ETS 300 402-2 (1995): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System
No. one (DSS1) protocol; Data link layer; Part 2: General protocol specification [ITU-T Recommendation
Q.921 (1993), modified]".
A.4 The PICS proforma tables
A.4.1 Correspondence to a physical interface
The "implementation" (IUT) about which this PICS proforma asks questions corresponds to a layer 2
implementation on top of ONE physical interface (i.e. one ISDN Basic access or one ISDN Primary rate
access interface structure). If the SUT implements both Basic access and Primary rate access interface
structures, and in the case of the Basic access, supports more than one configuration, then a layer 2 PICS
shall be created for each type of interface (and for each configuration of each interface) provided by the
SUT.
Page 14
ETS 300 402-4: September 1996
A.4.2 Structure of the tables
The supplier shall provide answers to the questions concerning the major roles of the IUT and the type of
interface (table A.1). The supplier shall then provide answers to the questions relating to the capabilities of
the IUT in one of the major roles as appropriate. The supplier shall also provide answers to the questions
relating to the type of interface supporting the IUT (the behaviour of the IUT is dependant on the type of
interface and its configuration). Apart from the initial questions to determine roles, the major roles of the
IUT - the user role (R 2.1) and the network role (R 2.2), are treated completely separately in the PICS
proforma. It is only necessary to complete the questions for the supported role.
Clause A.7 concerns the capabilities of the IUT whilst in the user role. Clause A.8 concerns the
capabilities of the IUT whilst in the network role.
A.5 Global statement of conformance
The implementation described in this PICS meets all the mandatory requirements of the referenced
standard?
[ ] 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. Explanations may
be entered in the comments field at the bottom of each table or on attached pages.
A.6 Roles
Table A.1: Roles
Item Role Conditions for Status Reference Support
status
R 1 not used
R 2.1 the user role O.1 [ ]Yes [ ]No
R 2.2 the network role O.1 [ ]Yes [ ]No
Type of implementation
R 3 not used
R 4 not used
R 5 not used
R 6.1 basic access O.2 [ ]Yes [ ]No
R 6.2 primary rate access O.2 [ ]Yes [ ]No
O.1 Support of one and only one of these options is required.
O.2 Support of one and only one of these options is required.
Comments:
Page 15
ETS 300 402-4: September 1996
A.7 User
The tables provided in this subclause need only to be completed for user implementations.
Prerequisite: R 2.1
A.7.1 Major capabilities
Each question in table A.2 refers to a major function of the protocol. Answering "Yes" to a particular
question states that the implementation supports all the mandatory procedures for that function defined in
the referenced clauses and subclauses of ETS 300 402-2 [1]. Answering "No" to a particular question
states that the implementation does not support that function of the protocol.
Table A.2: Major capabilities - user
Item Major capability: Conditions for status Status Reference Support
does the IUT support.
General
MCu 1.1 configurations using more than one Terminal O.3 Annex A [ ]Yes [ ]No
Endpoint Identifier (TEI)?
MCu 1.2 point-to-point configurations using only one TEI O.3 Annex A [ ]Yes [ ]No
value?
Procedures for unacknowledged information transfer
MCu 2.1 the unacknowledged information transfer service in MCu 3 M 5.2 [ ]Yes [ ]No
the broadcast data link (using TEI value 127)? NOT MCu 3 O
MCu 2.2 the unacknowledged information transfer service in O 5.2, 5.2.1 [ ]Yes [ ]No
a point-to-point data link (using a TEI value other
than 127)?
TEI management procedure
MCu 3 TEI management procedures? MCu 1.1 M 5.3 [ ]Yes [ ]No
MCu 1.2 O Annex A
MCu 3.1.1 the automatic TEI assignment procedures? MCu 3 O.4 5.3.2 [ ]Yes [ ]No
NOT MCu 3 N/A [ ]N/A
MCu 3.1.2 the non-automatic TEI assignment procedures? MCu 3 O.4 5.3.2 [ ]Yes [ ]No
NOT MCu 3 N/A [ ]N/A
MCu 3.2 the TEI check procedures? MCu 3 M 5.3.3 [ ]Yes [ ]No
NOT MCu 3 N/A [ ]N/A
MCu 3.3 the TEI removal procedures? MCu 3 M 5.3.4 [ ]Yes [ ]No
NOT MCu 3 N/A [ ]N/A
MCu 3.4 the TEI identity verify procedures? MCu 3 O 5.3.5 [ ]Yes [ ]No
NOT MCu 3 N/A [ ]N/A
Initialization of data link layer parameters
MCu 4 the procedures for initialization of the data link M 5.4 [ ]Yes [ ]No
parameters to the default values?
Multiple frame operations
MCu 5 multiple frame operations? M 5.5 [ ]Yes [ ]No
MCu 5.1.1 the self initiated establishment of multiple frame O 5.5.1, 5.5.5, [ ]Yes [ ]No
operation? 5.5.6
MCu 5.1.2 the peer initiated establishment of multiple frame M 5.5.1, 5.5.5, [ ]Yes [ ]No
operation? 5.5.6
MCu 5.2.1 the self initiated termination of multiple frame O 5.5.3, 5.5.5, [ ]Yes [ ]No
operation? 5.5.6
MCu 5.2.2 the peer initiated termination of multiple frame M 5.5.3, 5.5.5, [ ]Yes [ ]No
operation? 5.5.6
MCu 5.3 information transfer in multiple frame operation? M 5.6 [ ]Yes [ ]No
MCu 5.4 the re-establishment of multiple frame operation? M 5.7 [ ]Yes [ ]No
MCu 5.5 the data link layer monitor function? O 5.10 [ ]Yes [ ]No
O.3 Support of one and only one of these options is required.
O.4 Support of one and only one of these options is required.
Comments:
Page 16
ETS 300 402-4: September 1996
A.7.2 Subsidiary capabilities
Indicating support for an item in table A.3 states that the implementation supports special cases or options
within a major capability.
Table A.3: Subsidiary capabilities - user
Item Subsidiary capability: Conditions for Status Reference Support
does the IUT support. status
TEI management procedures
SCu 1.1 the multiple use of the TEI assignment procedure MCu 3.1.1 O 5.3.1 [ ]Yes [ ]No
to obtain a number of TEI values? NOT MCu 3.1.1 N/A [ ]N/A
SCu 1.2 the checking of whether the TEI received in an MCu 3.1.1 O 5.3.2, 5.3.4.2 [ ]Yes [ ]No
Identity Assigned message is already used, when NOT MCu 3.1.1 N/A [ ]N/A
no Identity Request message is outstanding?
after having assumed a possible duplicate assignment by checking a received Identity Assigned message, .
SCu 1.3.1 initiation of TEI removal? MCu 3.3 O.5 5.3.2, 5.3.4.2 [ ]Yes [ ]No
NOT MCu 3.3 N/A [ ]N/A
SCu 1.3.2 initiation of TEI identity verify procedures? MCu 3.4 O.5 5.3.2, 5.3.4.2 [ ]Yes [ ]No
NOT MCu 3.4 N/A [ ]N/A
after having received a MDL-ERROR primitive indicating that the DL entity has assumed a possible duplicate
assignment, .
SCu 1.4.1 initiation of TEI removal? MCu 3.3 O.6 5.3.2, 5.3.4.2 [ ]Yes [ ]No
NOT MCu 3.3 N/A [ ]N/A
SCu 1.4.2 initiation of TEI identity verify procedures? MCu 3.4 O.6 5.3.2, 5.3.4.2 [ ]Yes [ ]No
NOT MCu 3.4 N/A [ ]N/A
SCu 1.5 the sending of more than one TEI value within a MCu 3.2 O 5.3.3 [ ]Yes [ ]No
single Identity check response message? NOT MCu 3.2 N/A [ ]N/A
Multiple frame operations
SCu 2 the transmission of I frames in the own receiver O 5.6.1 [ ]Yes [ ]No
busy condition?
O.5 Support of at least one of these options is required.
O.6 Support of at least one of these options is required.
Comments:
Page 17
ETS 300 402-4: September 1996
A.7.3 Protocol data units
The tables in this subclause ask questions related to the support of Protocol Data Units (PDUs) in the user
role.
A.7.3.1 Frames received by the user
Indicating support for an item in table A.4 states that the implementation has the ability to recognize the
frame specified by that item. Support for the receipt of a particular type of PDU means support for
recognizing and acting upon all valid instances of that PDU type, including all valid PDU parameters, to
the extent required by ETS 300 402-2 [1].
Table A.4: Frames received - user
Item Message: Conditions for Status Reference Support
does the IUT support the receipt of a frame of status
type.
Information transfer (I) format
FRu 1 I command? M 3.6.2, 5.6 [ ]Yes [ ]No
Supervisory (S) format
FRu 2 RR command? M 3.6.6, 5.6, 5.10 [ ]Yes [ ]No
FRu 3 RR response? M 3.6.6, 5.6, 5.10 [ ]Yes [ ]No
FRu 4 RNR command? M 3.6.8, 5.6, 5.10 [ ]Yes [ ]No
FRu 5 RNR response? M 3.6.8, 5.6, 5.10 [ ]Yes [ ]No
FRu 6 REJ command? M 3.6.7, 5.6, 5.8.1 [ ]Yes [ ]No
FRu 7 REJ response? M 3.6.7, 5.6, 5.8.1 [ ]Yes [ ]No
Unnumbered (U) format
FRu 8 SABME command? M 3.6.3, 5.5.1, 5.7 [ ]Yes [ ]No
FRu 9 DISC command? M 3.6.4, 5.5.3 [ ]Yes [ ]No
FRu 10 UA response? M 3.6.9, 5.5 [ ]Yes [ ]No
FRu 11 DM response? M 3.6.10, 5.5 [ ]Yes [ ]No
FRu 12 UI command? MCu 2.1 OR M 3.6.5, 5.2.3, 5.3 [ ]Yes [ ]No
MCu 2.2
NOT (MCu 2.1 OR O
MCu 2.2)
FRu 13 FRMR response? M 3.6.11, 5.8.6 [ ]Yes [ ]No
FRu 14 XID command? M 3.6.12 [ ]Yes [ ]No
FRu 15 XID response? M 3.6.12 [ ]Yes [ ]No
Comments:
Page 18
ETS 300 402-4: September 1996
A.7.3.2 Frames transmitted by the user
Indicating support for an item in table A.5 states that the implementation has the ability to transmit the
frame specified by that item.
Table A.5: Frames transmitted - user
Item Message: Conditions for Status Reference Support
does the IUT support the transmission of a status
frame of type.
Information transfer (I) format
FTu 1 I command? M 3.6.2, 5.6 [ ]Yes [ ]No
Supervisory (S) format
FTu 2 RR command? M 3.6.6, 5.6, 5.10 [ ]Yes [ ]No
FTu 3 RR response? M 3.6.6, 5.6, 5.10 [ ]Yes [ ]No
FTu 4 RNR command? M 3.6.8, 5.6, 5.10 [ ]Yes [ ]No
FTu 5 RNR response? M 3.6.8, 5.6, 5.10 [ ]Yes [ ]No
FTu 6 REJ command? M 3.6.7, 5.6, 5.8.1 [ ]Yes [ ]No
FTu 7 REJ response? M 3.6.7, 5.6, 5.8.1 [ ]Yes [ ]No
Unnumbered (U) format
FTu 8 SABME command? M 3.6.3, 5.5.1, 5.7 [ ]Yes [ ]No
FTu 9 DISC command? MCu 5.2.1 M 3.6.4, 5.5.3 [ ]Yes [ ]No
NOT MCu 5.2.1 O
FTu 10 UA response? M 3.6.9, 5.5 [ ]Yes [ ]No
FTu 11 DM response? M 3.6.10, 5.5 [ ]Yes [ ]No
FTu 12 UI command? MCu 2.1 OR M 3.6.5, 5.2.2, 5.3 [ ]Yes [ ]No
MCu 2.2
NOT (MCu 2.1 OR O
MCu 2.2)
FTu 13 FRMR response? X 3.6.11, 5, 5.8.6 [ ]Yes [ ]No
Comments:
Page 19
ETS 300 402-4: September 1996
A.7.4 PDU parameters
A.7.4.1 Service data units
A.7.4.1.1 Service data units received by the user
The tables in this subclause ask questions related to the support of Service Data Unit (SDU) parameters
in UI frames received and transmitted by the IUT in the user role.
Table A.6: SDUs received in UI frames - user
Item Does the IUT support in the UI frame Conditions for Status Reference Support
information field the interpretation of . status
PRu 1 Layer 3 messages? FRu 12 O 5.2 [ ]Yes [ ]No
NOT FRu 12 N/A [ ]N/A
Layer management messages
PRu 2.1 Identity assign? MCu 3.1.1 M 5.3.2 [ ]Yes [ ]No
NOT MCu 3.1.1 N/A [ ]N/A
PRu 2.2 Identity denied? MCu 3.1.1 M 5.3.2 [ ]Yes [ ]No
NOT MCu 3.1.1 N/A [ ]N/A
PRu 2.3 Identity check request? MCu 3.2 M 5.3.3 [ ]Yes [ ]No
NOT MCu 3.2 N/A [ ]N/A
PRu 2.4 Identity remove? MCu 3.3 M 5.3.4 [ ]Yes [ ]No
NOT MCu 3.3 N/A [ ]N/A
Comments:
A.7.4.1.2 Service data units transmitted by the user
Table A.7: SDUs transmitted in UI frames - user
Item Does the IUT support in the UI frame Conditions for Status Reference Support
information field the inclusion of . status
PTu 1 Layer 3 messages? FTu 12 O 5.2 [ ]Yes [ ]No
NOT FTu 12 N/A [ ]N/A
Layer management messages
PTu 2.1 Identity reques
...