SIST ETS 300 403-3:1998

• Abstract:

  ISDN user-network layer 3 protocol implementation conformance statement (PICS) proforma considering the compatible extension of the base standard ETS 300 102-1.

• Status: Published
• Publication Date: 31-May-1998
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• ICS: 35.100.30 - Network layer
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jun-1998
• Due Date: 01-Jun-1998
• Completion Date: 01-Jun-1998
• Ref Project: ETSI ETS 300 403-3 ed.1 (1996-09) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification

SIST ETS 300 403-3:1998 is the Slovenian adoption of ETS 300 403-3 Edition 1, a European Telecommunications Standard from ETSI. It specifies a Protocol Implementation Conformance Statement (PICS) proforma for the Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one (DSS1) signalling network layer for circuit-mode basic call control. In practice, it tells a supplier how to document which protocol features a user-side or network-side implementation supports against ETS 300 403-1 and ETS 300 403-2.

What does SIST ETS 300 403-3:1998 specify?

SIST ETS 300 403-3:1998 specifies the PICS proforma for ISDN DSS1 signalling network layer conformance for circuit-mode basic call control. It is the document a supplier completes when claiming conformance to ETS 300 403-1 and ETS 300 403-2, using the PICS rules of ISO/IEC 9646-7.

The scope is limited to the user-network layer 3 protocol implementation conformance statement. Packet communication procedures and User Signalling Bearer Service (USBS) procedures are outside the scope.

The document is organized as follows:

• Clause 1 - Scope
• Clause 2 - Normative references
• Clause 3 - Definitions and abbreviations
• Clause 4 - Conformance
• Annex A - normative PICS proforma
• Annex B - differences from the earlier DSS1 PICS proforma
• Annex C - bibliography

Annex	What it covers
Annex A	The full PICS proforma for ETS 300 403-1 and ETS 300 403-2, including completion guidance and the role-specific tables
Annex B	Differences between the proforma in this standard and the earlier PICS proforma associated with ETS 300 102-1
Annex C	Bibliographic references

What are the key requirements of SIST ETS 300 403-3:1998?

SIST ETS 300 403-3:1998 is a questionnaire-style conformance document, so its practical requirement is that the supplier completes the right tables for the implementation being declared. The completed PICS must identify the supplier and the implementation, and it must match the structure and numbering of annex A.

Completing the PICS in annex A

Clause 4 requires a conforming PICS to be technically equivalent to annex A and to preserve its numbering and ordering. For a reader, this means the answers are not free-form - they must follow the exact structure so test labs and customers can compare implementations consistently.

Annex A also says the completed PICS must include enough information to identify both the supplier and the implementation. In practice, this avoids ambiguity about which product, version, or configuration the conformance statement refers to.

Selecting the applicable role and interface

Table A.1 and annex A.6 distinguish whether the implementation is the user or the network side of the user-network interface. The same proforma covers both, but only the tables for the chosen role need to be completed.

Annex A also asks which interface applies, including basic access or primary rate access, and whether the procedures are for the coincident S and T reference point or for interworking with private ISDNs at the T reference point. This matters because the supported procedures can differ by access and reference point, so the declaration must match the actual installation.

Declaring type and capability support

Annex A groups the declaration into Type of implementation, Major capabilities, and Subsidiary capabilities. The tables use the status markers from the PICS method, including mandatory, optional, prohibited, not applicable, and supported or not supported choices.

For an engineer or buyer, this is where the implementation profile becomes visible. It shows which capabilities are implemented, which are optional selections, and which items are explicitly excluded.

Recording protocol data units and information elements

Annex A requires the supplier to state support for Protocol Data Units (PDUs), including messages received and transmitted by the user or the network. It then breaks those messages down into information elements and parameter conditions.

This is the most detailed part of the proforma and is the part that matters most in testing. It tells the supplier to declare, message by message, which fields are supported, which are mandatory, and which depend on selected options or roles.

Capturing timers and structured information elements

Annex A includes tables for Timers, Compatibility information elements structure, and Numbering information elements structure for both user and network implementations. These sections capture support for timing behavior and for structured information carried in the protocol.

That matters in practice because conformance is not only about sending the right messages - it also depends on handling timing and encoding details in a way that matches the base protocol and its extensions.

Applying the conformance rule

Clause 4 states that a PICS conforming to this proforma must describe an implementation that conforms to ETS 300 403-1 and ETS 300 403-2, must be completed according to the guidance in annex A.1, and must uniquely identify the supplier and implementation. In plain terms, the form is only valid when it is both filled in correctly and tied to a specific product instance.

Annex A also gives guidance on how to complete the form, including symbols, conventions, and instructions. This helps keep responses consistent across suppliers, which is important when a customer compares different implementations.

What terms does SIST ETS 300 403-3:1998 define?

SIST ETS 300 403-3:1998 defines several terms used throughout the PICS process and the DSS1 context.

• Implementation Conformance Statement (ICS) - A statement from the supplier saying which capabilities of an implementation are present for a given specification.
• Protocol Implementation Conformance Statement (PICS) - An ICS for a protocol implementation or system claimed to conform to a specification.
• PICS proforma - The questionnaire form that becomes a PICS when the supplier completes it.
• Implementation Under Test (IUT) - The implementation being assessed in the conformance statement.
• System Under Test (SUT) - The system in which the IUT resides during assessment.
• user - The DSS1 protocol entity at the user side of the user-network interface.
• network - The DSS1 protocol entity at the network side of the user-network interface.

Who uses SIST ETS 300 403-3:1998?

SIST ETS 300 403-3:1998 is used by suppliers of ISDN DSS1 implementations that claim conformance to ETS 300 403-1 and ETS 300 403-2. It is also used by test and evaluation teams that need a structured declaration of supported protocol behavior before conformance testing or procurement review.

In practice, the people who use it include:

• equipment suppliers documenting a user-side or network-side implementation
• engineers identifying supported messages, information elements, and timers
• quality managers checking that product declarations are complete and comparable
• buyers and procurement teams comparing declared protocol support between products
• conformance test teams preparing tests against the declared capabilities

What changed in SIST ETS 300 403-3:1998 from the previous edition?

SIST ETS 300 403-3:1998 is associated with the earlier DSS1 basic call control PICS proforma defined for ETS 300 102-1, and annex B describes the differences. The main changes are structural and editorial in the PICS framework rather than a change of protocol subject.

The differences stated in annex B are:

• user and network proformas were combined into one document, with separate table sets and new role questions R 2.1 and R 2.2
• basic access and primary rate access were combined into one proforma, with new questions R 6.1 and R 6.2
• separate questions were added for the coincident S and T reference point and for the T reference point
• item references gained a suffix, u or n, to show whether they apply to the user role or the network role
• the older N/A 1, N/A 2, and N/A statuses were removed in favor of ISO/IEC 9646-7 status usage such as X and I
• information element tables were replaced by more detailed PDU parameter tables
• call state questions were removed
• structure questions for HLC and LLC information elements were removed for the network
• structure questions for the Channel Identification information element were removed, with channel selection moved into subsidiary capability questions

Which standards are used with SIST ETS 300 403-3:1998?

SIST ETS 300 403-3:1998 depends on two companion ETS 300 403 parts and two ISO/IEC conformance-testing standards.

• ETS 300 403-1 - provides the protocol specification for the ISDN DSS1 signalling network layer for circuit-mode basic call control, derived from ITU-T Recommendation Q.931 with modifications.
• ETS 300 403-2 - provides the Specification and Description Language (SDL) diagrams for the same protocol.
• ISO/IEC 9646-1 - gives the general concepts and framework for Open Systems Interconnection (OSI) conformance testing.
• ISO/IEC 9646-7 - provides the rules for Implementation Conformance Statements and the PICS method used by this document.

What does the SIST ETS 300 403-3:1998 document contain?

SIST ETS 300 403-3:1998 contains the completion guidance, identification sections, and a large set of role-specific tables that form the PICS questionnaire. Annex A covers implementation identification, protocol identification, role selection, major and subsidiary capabilities, messages received and transmitted, information elements, timers, compatibility structures, and numbering structures.

The document also includes a global conformance statement and detailed yes/no or not applicable style questions for the user and network roles. Annex B provides a comparison with the earlier DSS1 PICS proforma, and annex C gives bibliographic references.

For practical use, the document is mainly a structured checklist for design verification, supplier declarations, and conformance assessment. It tells the respondent what to record, how to organize the answers, and which parts apply only to the user side or only to the network side.

SLOVENSKI STANDARD
01-junij-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'666LJQDOL]DFLMVNDRPUHåQDSODVW]DNUPLOMHQMHYRGRYQHJD
RVQRYQHJDNOLFDGHO,]MDYDRVNODGQRVWLL]YHGEHSURWRNROD3,&63URIRUPD
VSHFLILNDFLMH
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 3:
Protocol Implementation Conformance Statement (PICS) proforma specification
Ta slovenski standard je istoveten z: ETS 300 403-3 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.100.30 Omrežni sloj Network layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 403-3
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05050
ICS: 33.020, 33.080, 35.100.30
Key words: ISDN, DSS1, layer 3, PICS
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Signalling network layer for circuit-mode basic call control;
Part 3: 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
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 403-3: 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 403-3: 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 403-1 and ETS 300 403-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.4.3 Complexity of conditions in PDU parameter tables .14
A.4.4 Support for received PDU parameters.14
A.5 Global statement of conformance .15
A.6 Roles .15
A.7 User.16
A.7.1 Type of implementation .16
A.7.2 Major capabilities .16
A.7.3 Subsidiary capabilities.18
A.7.4 Protocol data units .21
A.7.4.1 Messages received by the user.21
A.7.4.2 Messages transmitted by the user .22
A.7.5 PDU parameters .23
A.7.5.1 Information elements in messages received by the user.24
A.7.5.2 Information elements in messages transmitted by the user.32
A.7.6 Timers.40
A.7.7 Compatibility information elements structure.41
A.7.8 Numbering information elements structure.47

Page 4
ETS 300 403-3: September 1996
A.8 Network. 51
A.8.1 Type of implementation.51
A.8.2 Major capabilities. 51
A.8.3 Subsidiary capabilities. 53
A.8.4 Protocol data units. 56
A.8.4.1 Messages received by the network . 56
A.8.4.2 Messages transmitted by the network . 57
A.8.5 PDU parameters . 58
A.8.5.1 Information elements in messages received by the network. 59
A.8.5.2 Information elements in messages transmitted by the network . 65
A.8.6 Timers . 71
A.8.7 Compatibility information elements structure . 72
A.8.8 Numbering information elements structure. 74
Annex B (informative): Differences from PICS proforma for ETS 300 102-1. 77
B.1 Introduction. 77
B.2 Identification of relevant ETSs. 77
B.3 Differences . 77
Annex C (informative): Bibliography . 78
History. 79

Page 5
ETS 300 403-3: 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 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) signalling network layer
for circuit-mode basic call control, as described below:
Part 1: "Protocol specification";
Part 2: "Specification and Description Language (SDL) diagrams";
Part 3: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 4: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 5: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the user";
Part 6: "TSS&TP specification for the network";
Part 7: "ATS and partial PIXIT proforma specification for the network".
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".
ETS 300 403-1 is derived from ITU-T Recommendation Q.931 (1993). However, no PICS proforma exists
for this Recommendation. Therefore, ETSI has created a PICS proforma that is specific to the European
environment. This PICS proforma reflects the requirements contained in ITU-T Recommendation Q.931
with the modifications applied by ETS 300 403-1 [1]. This has been done to assist understanding of how
the European requirements relate to the requirements contained within ITU-T Recommendation Q.931
(and in particular, to the options specified in that Recommendation that are selected by the ETS). In
practical terms, this means that a number of capabilities specified by ITU-T Recommendation Q.931
appear as items in this PICS proforma with a status more akin to the status that would be expected in a
profile ICS (i.e. out-of-scope (I), prohibited (X)).
Annex B of this ETS describes the differences between the proforma contained in annex A and the
proforma for the earlier version of the DSS1 protocol as specified in ETS 300 102-1 (1990).

Page 6
ETS 300 403-3: September 1996
Blank page
Page 7
ETS 300 403-3: September 1996
1 Scope
This third part of ETS 300 403 provides the Protocol Implementation Conformance Statement (PICS)
proforma for the Integrated Services Digital Network (ISDN) Digital Subscriber Signalling System No. one
(DSS1) protocol signalling network layer for circuit-mode basic call control as specified in
ETS 300 403-1 [1] and ETS 300 403-2 [2] in compliance with the relevant requirements and in accordance
with the relevant guidance given in ISO/IEC 9646-7 [4].
Both the packet communication procedures (see clause 6 of ETS 300 403-1 [1]) and the User Signalling
Bearer Service (USBS) procedures (see clause 7 of ETS 300 403-1 [1]) are excluded from this PICS
proforma.
The supplier of an implementation that is claimed to conform to ETS 300 403-1 [1] and ETS 300 403-2 [2]
is required to complete a copy of the PICS proforma provided in annex A of this ETS and is required to
provide the information necessary to identify both the supplier and the implementation.
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 403-1 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer
for circuit-mode basic call control; Part 1: Protocol specification [ITU-T
Recommendation Q.931 (1993), modified]".
[2] ETS 300 403-2 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer
for circuit-mode basic call control; Part 2: Specification Description Language
(SDL) diagrams".
[3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[4] 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 403-1 [1],
ETS 300 403-2 [2], ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [4]:
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 [3]).
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 [3]).
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 [3]).
user: The DSS1 protocol entity at the user side of the user-network interface.

Page 8
ETS 300 403-3: September 1996
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AND Boolean "and"
BC Bearer Capability information element
CDP Called Party information element
CGP Calling Party information element
DSS1 Digital Subscriber Signalling System No. one
HLC High Layer Compatibility information element
ICS Implementation Conformance Statement
IS Information element structure
ISDN Integrated Services Digital Network
IUT Implementation Under Test
LLC Low Layer Compatibility information element
M Mandatory requirement (to be observed in all cases)
MC Major Capabilities
MR Messages Received
MT Messages Transmitted
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
PABX Private Automatic Branch eXchange
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
R Roles
SC Subsidiary Capabilities
SUT System Under Test
(T) Transparent (PDU parameter)
TI Type of Implementation
TM Timer
USBS User Signalling Bearer Service
Yes supported
4 Conformance
A PICS proforma that conforms to this PICS proforma specification shall be technically equivalent to
annex A, and shall preserve the numbering and ordering of the items in annex A.
A PICS that conforms to this PICS proforma specification shall:
a) describe an implementation which conforms to ETS 300 403-1 [1] and ETS 300 403-2 [2];
b) be a conforming PICS proforma, which has been completed in accordance with the instructions for
completion given in clause A.1; and
c) include the information necessary to uniquely identify both the supplier and the implementation.

Page 9
ETS 300 403-3: September 1996
Annex A (normative): PICS proforma for ETS 300 403-1 and ETS 300 403-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 403-1 [1] and ETS 300 403-2 [2] 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 [4].
Item column:
The item column contains a unique reference (a mnemonic plus a number) for each item within the PICS
proforma.
NOTE: Where possible, backwards compatibility has been maintained between the item
references used in this PICS proforma and those used in the PICS proforma for the
earlier version of the DSS1 protocol described in ETS 300 102-1.
In general, the same mnemonics have been used in this PICS proforma as in earlier 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 proforma both these cases were
identified by the same mnemonic (e.g. MC).
A further consequence of maintaining backwards compatibility is the appearance of discontinuities in the
numeric part of the item reference. There are, for example, PICS items listed as messages transmitted by
the network with the references "MTn 2" and "MTn 4"; the reference between, "MTn 3" is not used.
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 403-3: September 1996
Status column:
The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column:
I Irrelevant or out-of-scope - this capability is outside the scope of the ETS to
which this PICS proforma applies and is not subject to conformance testing in
this context.
M Mandatory - the capability is required to be supported.
N/A Not Applicable - in the given context, it is impossible to use the capability. No
answer in the support column is required.
O Optional - the capability may be supported or not.
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 403-1 [1] and ETS 300 403-2 [2].
Reference column:
Except where explicitly stated, the reference column refers to the appropriate parts of ETS 300 403-1 [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 403-1 [1] and ETS 300 403-2 [2]
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 [4], 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 tickbox, 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 403-3: 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 403-3: 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 403-3: 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 standards:
ETS 300 403-1 (1995): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System
No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol
specification [ITU-T Recommendation Q.931 (1993), modified]"; and
ETS 300 403-2 (1995): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System
No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 2: Specification
Description Language (SDL) diagrams".
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 3
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 3 PICS
shall be created for each type of interface (and for each configuration of each interface) provided by the
SUT.
Page 14
ETS 300 403-3: 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. The answers to the "type
of interface" questions (represented by items R 3.x, R 6.x and R 7.x) condition the answers to the further
questions within each major role (user and network).
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.4.3 Complexity of conditions in PDU parameter tables
The conditions governing when an individual information element has to be supported in a specific
message are quite complex. This is particularly so for the Bearer capability, Progress indicator, and High
layer compatibility information elements when they are transmitted by an IUT in the user role. To make the
conditions for status easier to understand questions about these information elements have been split into
several sub-items.
A.4.4 Support for received PDU parameters
In the PDU parameter tables (subclauses A.7.5 and A.8.5), the PICS proforma asks questions about the
information elements (parameters) supported in messages (PDUs) received by the IUT. This subclause
explains, in the context of ETS 300 403-1 [1], what "to support a received PDU parameter" means.
The requirement that an IUT is able to parse an information element in a received message is already
implied by claiming support for the receipt of that received message. This means that "to support a
received PDU parameter" implies more.
Information elements in received messages are regarded as either transparent or non-transparent.
A non-transparent information element is one that causes the protocol control entity to vary its behaviour
in accordance with the content of the information element. To support a non-transparent information
element means an IUT can process the received parameter and behave according to the procedures
described in ETS 300 403-1 [1].
An information element is transparent if the actions taken according to its contents are not detectable in
the subsequent behaviour of the protocol (i.e. ETS 300 403-1 [1] does not specify the protocol behaviour).
To support a transparent information element means an IUT can receive the information element
concerned and pass it to an appropriate processing entity (e.g. call control); the information element is not
discarded by the protocol control entity. Non-support of a transparent information element means the IUT
discards it.
Where ETS 300 403-1 [1], in addition to not specifying the protocol behaviour, does not specify the non-
protocol behaviour, transparent parameters have been allocated the status Irrelevant (I). In such cases
the Client may choose not to answer whether or not the IUT supports the item. If the item is claimed to be
supported, an explanation shall be given in the comments field of the table indicating what actions are
performed on receipt of the parameter.
This PICS proforma considers the Cause, Display, and Keypad facility information elements to be
transparent in all circumstances where they are possible to be received. Other information elements may
be transparent in some circumstances (e.g. High layer compatibility and Low layer compatibility when
received by the network). Transparent parameters are marked by "(T)" in the PDU parameter tables.

Page 15
ETS 300 403-3: September 1996
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
Does the implementation support. status
R 1 not used
Major role
R 2.1 the user role O.1 [ ]Yes [ ]No
R 2.2 the network role O.1 [ ]Yes [ ]No
Type of interface
R 3.1 requirements at the coincident S and T reference O.2 [ ]Yes [ ]No
point
R 3.2 requirements for interworking with private ISDNs at O.2 [ ]Yes [ ]No
the T reference point
R 4 not used
R 5 not used
R 6.1 basic access O.3 [ ]Yes [ ]No
R 6.2 primary rate access O.3 [ ]Yes [ ]No
R 7.1 point-to-point configuration R 6.1 O.4 [ ]Yes [ ]No
R 6.2 M
R 7.2 multi-point configuration R 6.1 O.4 [ ]Yes [ ]No
R 6.2 N/A [ ]N/A
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.
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 403-3: 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 Type of implementation
Answers to the questions in table A.2 are required to permit the conditions for status for the user role to be
properly evaluated for a specific IUT. The questions refer to aspects outside the scope of
ETS 300 403-1 [1], but which affect the behaviour of the basic call protocol.
Table A.2: Type of implementation
Item Type of implementation Conditions for Status Reference Support
Does the implementation. status
TIu 1 (e.g. a PABX) provide interworking capability with I 5.1.6, 5.2.6 [ ]Yes [ ]No
non-ISDN equipment
TIu 2 support one or more of the speech, 3,1 kHz audio I 5.1 [ ]Yes [ ]No
or unrestricted digital information with
tones/announcements bearer capabilities
TIu 3 provide (or transmit) in-band I 5.2.6, Annex K [ ]Yes [ ]No
tones/announcements as a called user
TIu 4 support one or more "existing services" (note) I 5.13 [ ]Yes [ ]No
TIu 5 support services other than "existing services" I 5.13 [ ]Yes [ ]No
(note)
NOTE: "Existing services" are those basic telecommunication services associated with the speech, 3,1 kHz audio and
64 kbit/s unrestricted bearer capabilities. Services other than the existing services include services based on, for
example, the unrestricted digital information with tones / announcements bearer capability.
A.7.2 Major capabilities
Each question in table A.3 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 403-1 [1]. Answering "No" to a particular question
states that the implementation does not support that function of the protocol.
Table A.3: Major capabilities of the user role
Item Major capability Conditions for Status Reference Support
Does the implementation support. status
Call establishment at the originating interface
MCu 1 outgoing calls O.5 5.1 [ ]Yes [ ]No
MCu 1.1 called party addressing information sent only in the MCu 1 O.6 5.1.1, 5.1.5.1 [ ]Yes [ ]No
SETUP message (en-bloc sending) NOT MCu 1 N/A [ ]N/A
MCu 1.2 called party addressing information split across, MCu 1 O.6 5.1.3, 5.1.5.2 [ ]Yes [ ]No
and sent in, SETUP and INFORMATION NOT MCu 1 N/A [ ]N/A
messages (overlap sending)
MCu 1.3 sending of a notification of interworking on an MCu 1 AND TIu 1 M 5.1.6 (last [ ]Yes [ ]No
outgoing call (notification sent by the calling user) NOT MCu 1 OR NOT N/A paragraph) [ ]N/A
TIu 1
MCu 1.4 transit network selection MCu 1 O 5.1.10, annex C [ ]Yes [ ]No
NOT MCu 1 N/A [ ]N/A
MCu 1.5 procedures associated with network's provision of MCu 1 AND TIu 2 M 5.1.2, 5.1.3, 5.1.6, [ ]Yes [ ]No
in-band tones/announcements MCu 1 AND NOT O 5.4 [ ]N/A
TIu 2
NOT MCu 1 N/A
MCu 1.6 interpretation of a notification of interworking on an MCu 1 M 5.1.6 (first to third [ ]Yes [ ]No
NOT
outgoing call (notification received by the calling MCu 1 N/A paragraph) [ ]N/A
user)
MCu 1.7 generation of local tones and local alerting MCu 1 O 5.1.2, 5.1.7 [ ]Yes [ ]No
indications NOT MCu 1 N/A [ ]N/A
(continued)
Page 17
ETS 300 403-3: September 1996
Table A.3 (continued): Major capabilities of the user role
Item Major capability Conditions for Status Reference Support
Does the implementation support. status
Call establishment at the destination interface
MCu 2 incoming calls O.5 5.2 [ ]Yes [ ]No
MCu 2.1 called party addressing information sent only in the MCu 2 M 5.2.1, 5.2.5.1 [ ]Yes [ ]No
SETUP message (en-bloc receiving) NOT MCu 2 N/A [ ]N/A
MCu 2.2 called party addressing information split across, MCu 2 O 5.2.1, 5.2.4, [ ]Yes [ ]No
and sent in, SETUP and INFORMATION NOT MCu 2 N/A 5.2.5.1 [ ]N/A
messages (overlap receiving)
MCu 2.3 interpretation of a notification of interworking on an MCu 2 M 5.2.6 (first [ ]Yes [ ]No
incoming call (notification received by the called NOT MCu 2 N/A paragraph) [ ]N/A
user)
MCu 2.4 acceptance of the SETUP message on a point-to- MCu 2 AND R 7.1 M 5.2.1, 5.2.3.1 [ ]Yes [ ]No
point data link NOT MCu 2 OR NOT [ ]N/A
R 7.1 N/A
MCu 2.5 acceptance of the SETUP message on a MCu 2 AND R 7.2 M 5.2.1, 5.2.3.2 [ ]Yes [ ]No
broadcast data link NOT MCu 2 OR NOT [ ] N/A
R 7.2 N/A
MCu 2.6 sending of a notification of interworking on an MCu 2 AND TIu 1 M 5.2.6 (second to [ ]Yes [ ]No
incoming call (notification sent by the called user) NOT MCu 2 OR NOT fourth paragraph) [ ]N/A
TIu 1 N/A
MCu 2.7 compatibility checking MCu 2 M 5.2.2, annex B [ ]Yes [ ]No
NOT MCu 2 N/A [ ]N/A
Others
MCu 3 initiation of call clearing M 5.3.3 [ ]Yes [ ]No
MCu 4.1 call clearing initiated by the network when O 5.3.4.1 [ ]Yes [ ]No
tones/announcements provided
MCu 4.2 call clearing initiated by the network when M 5.3.4.2 [ ]Yes [ ]No
tones/announcements are not provided
MCu 5.1 restart procedure (interpretation of a received R 7.1 M 5.5.2 [ ]Yes [ ]No
RESTART me
...