ETSI ETS 300 805-1 ed.1 (1998-02)

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

DE/ECMA-00109-1

Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Vodovne osnovne storitve - Omrežna plast (NL) - 1. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP)

General Information

• Status: Published
• Publication Date: 09-Feb-1998
• Technical Committee: Ecma - Standardizing information and communications systems
• Current Stage: 12 - Completion
• Due Date: 13-Feb-1998
• Completion Date: 10-Feb-1998
• Mandate: T-245
• Ref Project: SIST ETS 300 805-1 E1:2005 - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 805-1 E1:2005
01-maj-2005
Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski
protokol - Vodovne osnovne storitve - Omrežna plast (NL) - 1. del: Zgradba
preskušalnega niza in nameni preskušanja (TSS&TP)
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit
mode basic services; Network Layer (NL); Part 1: Test Suite Structure and Test
Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: ETS 300 805-1 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 805-1 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 805-1 E1:2005

---------------------- Page: 2 ----------------------

SIST ETS 300 805-1 E1:2005
EUROPEAN ETS 300 805-1
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA 00109-1
ICS: 33.020
Key words: Circuit mode, layer 3, PINX, PISN, QSIG, testing, TSS&TP
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Circuit mode basic services;
Network Layer (NL);
Part 1: Test Suite Structure and Test Purposes (TSS&TP)
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 1998. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 805-1 E1:2005
Page 2
ETS 300 805-1: February 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 Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 805-1 E1:2005
Page 3
ETS 300 805-1: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .9
4 Test Suite Structure (TSS) .9
5 Test Purposes (TPs) .11
5.1 Introduction to TPs.11
5.1.1 TPs production method .11
5.1.2 STP identifier.12
5.1.3 "final" derived TP identifier .12
5.1.4 Standard options .12
5.1.5 Message segmentation .13
5.2 TP writing rules .13
5.2.1 Terminating, originating, incoming/outgoing gateway PINX.13
5.2.2 Transit PINX.14
5.3 TPs.15
5.3.1 Protocol control requirements for call establishment .15
5.3.1.1 Call Request (CR).15
5.3.1.2 Information channel selection.18
5.3.1.3 Overlap Sending and Receiving .19
5.3.1.4 Call Proceeding .21
5.3.1.5 Call Confirmation indication.22
5.3.1.6 Call Connected .23
5.3.1.7 Use of the PROGRESS message .25
5.3.1.8 Call collisions.26
5.3.2 Protocol control requirements for CC.29
5.3.2.1 Clearing .29
5.3.2.2 Clear collision .31
5.3.2.3 Exception conditions.31
5.3.3 Protocol control requirements for Message Segmentation .31
5.3.3.1 Procedures for segmentation .31
5.3.3.2 Procedures for reassembly.32
5.3.4 Protocol control requirements for STATUS procedures.38
5.3.4.1 Receiving a STATUS message.38
5.3.4.2 Status enquiry procedure.40
5.3.5 Protocol control requirements for layer management .43
5.3.5.1 Sending a RESTART.43
5.3.5.2 Receipt of RESTART.44
5.3.5.3 Restart Collision.45
5.3.6 Protocol control requirements for handling of protocol error conditions.47
5.3.6.1 Protocol discriminator error .47
5.3.6.2 Message too short .47
5.3.6.3 Call reference error.48
5.3.6.3.1 Invalid call reference format.48
5.3.6.3.2 Call Reference procedural errors.49
5.3.6.4 Message type or Message sequence errors .50
5.3.6.5 General IE errors .52
5.3.6.5.1 Duplicated IEs.52
5.3.6.5.2 IEs exceeding maximum length.52
5.3.6.6 Mandatory IE errors.53

---------------------- Page: 5 ----------------------

SIST ETS 300 805-1 E1:2005
Page 4
ETS 300 805-1: February 1998
5.3.6.6.1 Mandatory IEs missing. 53
5.3.6.6.2 Mandatory IE content error. 55
5.3.6.7 Non-mandatory IE errors . 56
5.3.6.7.1 Non-mandatory IE not recognized. 56
5.3.6.7.2 Non-mandatory IE content error. 59
5.3.6.8 Signalling Carriage Mechanism (SCM) reset. 59
5.3.6.9 Signalling Carriage Mechanism (SCM) failure . 60
5.3.7 Originating PINX call control requirements. 61
5.3.8 Terminating PINX call control requirements. 62
5.3.8.1 Call Establishment . 63
5.3.8.2 CC initiated by the terminating PINX. 65
5.3.9 Incoming gateway PINX call control requirements . 65
5.3.9.1 Call Establishment . 65
5.3.10 Outgoing gateway PINX call control requirements . 68
5.3.10.1 Call Establishment . 68
5.3.11 Call control requirements for a Transit PINX. 69
5.3.11.1 Call Establishment . 70
5.3.11.2 Call Clearing. 78
5.3.11.2.1 Call clearing not initiated by the transit
PINX. 78
5.3.11.2.2 Call clearing initiated by the transit
PINX. 82
5.3.11.3 Handling of basic call IEs at a transit PINX. 84
5.3.12 Protocol control requirements for the use of the Signalling Carriage
Mechanism (SCM). 89
5.3.13 Verification of state . 89
5.3.13.1 Protocol control State. 90
5.3.13.2 Layer management state . 90
5.4 Distribution of TPs over TSS. 90
6 Compliance clause . 91
Annex A (informative): Index of TPs. 92
History. 95

---------------------- Page: 6 ----------------------

SIST ETS 300 805-1 E1:2005
Page 5
ETS 300 805-1: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the standardizing Information
and Communication Systems Association (ECMA) on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
This ETS comprises two parts with the generic title "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Network Layer (NL); Circuit mode basic services". The title of each part
is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TPs)";
Part 2: "Abstract Test Suite (ATS) specification".
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 805-1 E1:2005
Page 6
ETS 300 805-1: February 1998
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 805-1 E1:2005
Page 7
ETS 300 805-1: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Test Suite Structure (TSS) and Test
Purposes (TPs) specification for the Network Layer (NL), Circuit Mode Basic Services (CMBS) of the
Inter-exchange signalling protocol for Private Integrated Services Networks (PISN).
The objective of this TSS and TPs specification is to provide conformance tests which give a high
probability of inter-operability of the Network Layer. The TSS and TPs specification covers the procedures
described in ETS 300 172 [1].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [4],
ISO/IEC 9646-2 [5] and ISO/IEC 9646-3 [6]) is used as basis for the test methodology.
This TSS and TPs specification standard is applicable for the support of Basic Call, at the Q-reference
point between Private Integrated Services Network Exchanges (PINXs) connected together within a PISN.
The Q reference point is defined in ETS 300 475-1 [7].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited in the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments or revisions to 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 172 (1995): "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Circuit–mode basic
services" [ISO/IEC 11572 (1996), modified].
[2] ETS 300 239 (1995): "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol, Generic functional protocol for the support of
supplementary services" [ISO/IEC 11582 (1995), modified].
[3] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[4] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection; Conformance testing methodology and framework - Part 1:
General concepts".
[5] ISO/IEC 9646-2 (1994): "Information technology- Open Systems
Interconnection; Conformance testing methodology and framework - Part 2:
Abstract Test Suite Specification".
[6] ISO/IEC 9646-3 (1992): "Information technology - Open Systems
Interconnection; Conformance testing methodology and framework - Part 3: The
Tree and Tabular Combined Notation (TTCN)".
[7] ETS 300 475-1 (1995): "Private Telecommunication Network (PTN); Reference
configuration; Part 1: Reference configuration for PTN eXchanges (PINX)"
[ISO/IEC 11579-1 (1994), modified].
[8] CCITT Recommendation I. 112 (1988): "Vocabulary of terms for ISDNs".

---------------------- Page: 9 ----------------------

SIST ETS 300 805-1 E1:2005
Page 8
ETS 300 805-1: February 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS the special terminology defined in CCITT Recommendation I.112 [8] applies
in addition to the following definitions:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [4].
final TP: A TP which is intended to be mapped to a single test case (except if it is untestable).
NOTE: In this ETS all "final" TPs are individual TPs as there is no combination of TPs.
Implementation Under Test (IUT): See ISO/IEC 9646-1 [4].
incoming call: See ETS 300 172 [1].
incoming gateway PINX: See ETS 300 172 [1].
individual TP:
A TP focusing on a single conformance requirement, produced before any combining of
TPs. This term is not defined in ISO/IEC 9646-1 [4] but corresponds to the "individual test purpose"
referred to in ISO/IEC 9646-2 [5], subclause 10.3.3.
Information Elements (IEs) with invalid contents: See ETS 300 172 [1].
originating PINX: See ETS 300 172 [1].
outgoing call: See ETS 300 172 [1].
outgoing gateway PINX: See ETS 300 172 [1].
preceding PINX: See ETS 300 172 [1].
Private Integrated Network Exchange (PINX): See ETS 300 172 [1].
Private Integrated Services Network (PISN): See ETS 300 172 [1].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [4].
Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [4].
reassembly: The process whereby an implementation on receipt of the parts of a single message which
has been segmented for transmission, reassembles these parts to make up the original message.
segmentation: The process by which a message is divided into parts when the message size exceeds
the maximum size of the SCM information field.
Signalling Carriage Mechanism (SCM): See ETS 300 172 [1].
subsequent PINX: See ETS 300 172 [1].
super Test Purpose (TP): A general TP from which one or more TPs may be derived. These derived
TPs may be more detailed than the STP. This term is not defined in ISO/IEC 9646-1 [4] but corresponds
to the "more specific test objectives" referred to in ISO/IEC 9646-2 [5] subclause 10.3.1.
terminating PINX: See ETS 300 172 [1].
transit PINX: See ETS 300 172 [1].
unexpected message: See ETS 300 172 [1].

---------------------- Page: 10 ----------------------

SIST ETS 300 805-1 E1:2005
Page 9
ETS 300 805-1: February 1998
unrecognized information element: See ETS 300 172 [1].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ATS Abstract Test Suite
BC Bearer Capability
BI Invalid Behavour
BO Inopportune Behavour
BV Valid Behavour
CA CApability test
CC Call Clearing
CE Call Establishing
CMBS Circuit Mode Basic Services
CR Call Reference
IE Information Element
IG Incoming Gateway
IUT Implementation Under Test
IV InValid behaviour tests
IO InOpportune behaviour test
MS Message Segmentation
NL Network Layer
OG Outgoing Gateway
PC Protocol Control
PICS Protocol Implementation Conformance Statement
PINX Private Integrated Services Network eXchange
PISN Private Integrated Services Network
PIXIT Protocol Implementation eXtra Information for Testing
PSS1 Private Integrated Signalling System Number 1
PV Parameter Variations
SCM Signalling Carriage Mechanism
SE State Event transitions
STP Super Test Purpose
TE TErminating
TI TImers
TP Test Purpose
TR TRansi
TSS Test Suite Structure
4 Test Suite Structure (TSS)
Following the rules described in ETS 300 406 [3], subclause 7.4.1.1, the test suite is structured as a tree
with the following levels:
1st level: the name representing the base specification (ETS 300 172 [1]);
PSS1_BC
2nd level: Call control for the major roles of the base specification (Originating, Terminating, Transit,
Incoming Gateway, Outgoing Gateway) and Protocol Control which is common to all the behaviours;
- Protocol Control (PC);
- call control for OrIginating (OI);
- call control for TErminating (TE);
- call control for TRansit (TR);
- call control for Incoming Gateway (IG);
- call control for Outgoing Gateway (OG).
3rd level: the nature of the test;
- Basic Interconnection test (BI);
- CApability test (CA);
- Valid Behaviour tests (BV);
- InValid behaviour tests (IV);
- InOpportune behaviour tests (IO);

---------------------- Page: 11 ----------------------

SIST ETS 300 805-1 E1:2005
Page 10
ETS 300 805-1: February 1998
- TImers (TI).
4th level: the functional aspects tested;
- State Event transitions (SE);
- Parameter Variations (PV).
5th level: the phases of the base specification;
- Call Establishing (CE);
- Call Clearing (CC);
- Message Segmentation (MS) (this group may be empty for call control requirements);
- STATUS Procedures (ST) (this group may be empty for call control requirements);
- Layer Management (LM) (this group may be empty for call control requirements).
Figure 1 shows the PSS1 Layer 3 TSS overview. Not all the branches have been expanded to the "final"
details.
PSS1_BC Test Suite
Call Control Call Control Call Control Call Control Protocol
Call Control
for Terminating for Incoming
for Transit for Originating Control
for Outgoing
Gateway
Gateway
(PC)
(TR) (OI) (TE) (IG) (OG)
....
... ... ...
...
Invalid
Basic Capability Valid Inopportune Timer
Behaviour
Interconnection Behaviour Behaviour
(BI) (CA) (BV) (IV) (IO) (TI)
... ... ... ...
...
State Parameter
Event Variations
Transitions
(SE) (PV)
...
Call
Message Call
STATUS Layer
Establishing
Segmentation Clearing
Procedures Management
(MS) (CC) (CE) (ST) (LM)
... ... ... ...
TC2211KW,
TC2211KU,
...
Figure 1: PSS1 Layer 3 TSS overview

---------------------- Page: 12 ----------------------

SIST ETS 300 805-1 E1:2005
Page 11
ETS 300 805-1: February 1998
Figure 2 shows the details of the PSS1 layer 3 TSS. Not all the branches have been expanded to the
"final" details.
PSS1_BC
PC
TR TE OI IG
OG
BI CA BV IV IO TI
BI CA BV IV IO TI
BI CA BV IV IO TI
BI CA BV IV IO TI
BI CA BV IV IO TI BI CA BV IV IO TI
SE PV SE PV SE PV SE PV
SE PV SE PV SE PV SE PV
SE PV SE PV SE PV SE PV
MS CC CE ST LM MS CC CE ST LM MS CC CE ST LM MS CC CE ST LM
Figure 2: Detailed PSS1 layer 3 TSS
5 Test Purposes (TPs)
5.1 Introduction to TPs
5.1.1 TPs production method
The TPs production method consists of reviewing the standard and specifying everything that should be
tested, i.e. all the characteristics that could be determined from the standard, which an implementation is
required to conform to.
This first phase led to the production of Super Test Purposes (STPs), which are general TPs, reflecting
more the functional aspects and the structure of the standard rather than the TSS itself (see clause 4).
The second phase consisted of deriving from each STP several "final" TPs. These "final" TPs are the
individual TPs as identified in the Abstract Test Suite (ATS) (each of which will give rise to a Test Case).
The criteria for deriving these "final" TPs was to take into account the TSS, in order to ensure good
coverage for testing. The objective was to derive "final" TPs and distribute them over the complete TSS,
taking into account all the testing aspects (valid behaviour, inopportune behaviour, timer, parameter
variations, state event transition, etc.), while retaining all the requirements of the standard. In this way, one
or more "final" TPs may be derived from an STP.
Although an STP may generate a number of "final" TPs, not all of them may be retained, as they may deal
with a requirement which has already been covered by a previous "final" TP. This ensures a more efficient
testing with good coverage, avoiding repeatedly testing the same aspect of the standard, probably leading
to the same verdict each time.
Some STPs are not decomposed into "final" derived TPs, either because the requirement of this STP has
already been covered by a previous "final" TP, or because it is determined to be untestable. In this case
the STP is referenced as an "untestable" TP.

---------------------- Page: 13 ----------------------

SIST ETS 300 805-1 E1:2005
Page 12
ETS 300 805-1: February 1998
5.1.2 STP identifier
The STP identifier is described using a 5 digit alphanumeric code, this code is used in the following
manner:
- characters 5-4 : "SP";
- digit 3-2-1 : STP number.
PATTERN: SP with = 000 -> 999.
5.1.3 "final" derived TP identifier
The TP identifier is described using an 8 digit alphanumeric code, this code is used in the following
manner:
- characters 8-7 : "TC";
- digit 6 : 2nd level of TSS;
- digit 5 : 3rd level of TSS;
- digit 4 : 4th level of TSS;
- digit 3 : 5th level of TSS;
- characters 2-1 : letters identifying the "final" TP.
PATTERN: TC with
- =
0: protocol control
1: call control originating
2: call control terminating
3: call control transit
4: call control outgoing gateway
5: call control incoming gateway
- =
0: basic interconnection test
1: capability test
2: valid behaviour tests
3: invalid behaviour test
4: inopportune behaviour tests
5: timer test
- =
0: state events transitions
1: parameter variations
- =
0: call establishing
1: call clearing
2: message segmentation
3: status procedures
4: layer management
- = AA-> ZZ
EXAMPLE 1: TC2211KW is the number of the TP KW, for a terminating PINX, to test the valid
behaviour of the IUT, with parameter variations, during CC.
EXAMPLE 2: TC2211KU is the number of the TP KU, for a terminating PINX, to test the valid
behaviour of the IUT, with parameter variations, during CC.
5.1.4 Standard options
In reviewing the standard to produce TPs, two situations have been identified regarding optional
requirements.

---------------------- Page: 14 ----------------------

SIST ETS 300 805-1 E1:2005
Page 13
ETS 300 805-1: February 1998
The first case is where either the Implementation Under Test (IUT) performs an action which can be
tested, or does nothing that can be tested. In this situation there is a TP for the case where the IUT does
something testable and a Protocol Implementation eXtra Information for Testing (PIXIT) question should
be used to select the associated test case.
The second case is where the IUT always performs a first action which has to be tested and optionally
performs a second action which has also to be tested if it occurs. In this situation no PIXIT question is
asked for this selection.
5.1.5 Message segmentation
Where a TP refers to a message sent by the IUT, this message may be segmented (unless otherwise
stated) without affecting the TP.
5.2 TP writing rules
Writing rules have been defined in order to have consistency between all the TPs. However, in some
cases, it is not possible to use them without losing the real objective of the test. Consequently, a small
number of TPs may deviate from these rules in a minor way.
5.2.1 Terminating, originating, incoming/outgoing gateway PINX
Table 1 gives the TPs writing rules for non-transit PINX requirements.
Table 1: TP writing rules for non-transit PINX requirements
Structure Values
Ensure that the IUT in call state
, 0,1, 2, 3, etc.
[ on receiving a XXX message, on expiry of Txxx, etc.
or ] in order to initiate CC, etc.
sends, saves, does, etc.
using en-bloc sending, using overlap sending, etc.
if the action is sending
a SETUP, CONNECT, etc.
message containing a
a) Channel Identification, Call Reference, etc.
IE with a
channel number, Call Reference Flag, etc.
b)
encoded as
16, 0, etc.
and back to a) or b)
[and remains in the same state
or and enters state]
. 0, 1, 2, etc.
NOTE: In this table normal text in the left hand column is included in the TP, text between < and
> is replaced by a value (examples given in the right column). Text in bold is not included
in the TP, [ and ] are used to delimit options and a) and b) are labels.

---------------------- Page: 15 ----------------------

SIST ETS 300 805-1 E1:2005
Page 14
ETS 300 805-1: February 1998
5.2.2 Transit PINX
Table 2 gives the TPs writing rules for transit PINX requirements.
Table 2: TP writing rules for transit PINX requirements
STRUCTURE VALUES
Ensure that the IUT in transit state
, TCC_Overlap, TCC_CallActive, etc.
in state
0, 1, 2,3, etc.
for the call on interface X and in state
0, 1, 2, etc.
for the call on interface Y,
[ on receiving a XXX message on interface X (or Y), on
expiry of Txxx on interface X (or Y), etc.
or ] in order to initiate CC on interface X (or Y), etc.
sends, saves, does, etc.
a)
using en-bloc sending, using overlap sending, etc.
if the action is sending
b) a SETUP, CONNECT, etc.
message containing a
c) Channel Identification, Call Reference, etc.
IE with a
channel number, Call Reference Flag, etc.
d)
encoded as
16, 0, in the XXX message received on interface X (or Y).
and back to c) or d)
on interface
X,Y.
and back to a) or b)
[and remains in the same state
or and enters state]
0, 1, 2, etc.
for the call on interface X,
[and remains in the same state
or and enters state]
0, 1, 2, etc.
for the call on interface Y.
NOTE: In this table normal text in the left hand column is included in the TP, text between < and >
is replaced by a value (examples given in the right column). Text in bold is not included in
the TP, [ and ] are used to delimit options and a) and b) are labels.

---------------------- Page: 16 ----------------------

SIST ETS 300 805-1 E1:2005
Page 15
ETS 300 805-1: February 1998
5.3 TPs
NOTE 1: Only the derived "final" TPs are used to produce test cases.
NOTE 2: Where a TP specifies that the IUT enters or remains in a specified Protocol Control
(PC) or Layer Management state, this is verified as specified in subclause 5.3.13.
NOTE 3: Some TPs are not applicable to all implementations. In most cases this is clear from
the TP (e.g. a TP which specifies an initial state, is only applicable to implementations
which support that state). Where it is not clear, the applicability of an STP (and derived
TPs), or all the TPs in a subclause, is indicated. The selection rule for the test case
associated with each TP is indicated in the ATS. This takes into account the
applicability of the TP and other factors (e.g. restrictions of the test method).
5.3.1 Protocol control requirements for call establishment
The TPs in this subclause refer to ETS 300 172 [1], subclause 10.1.
5.3.1.1 Call Request (CR)
The TPs in this subclause refer to ETS 300 172 [1], subclause 10.1.1.
SP001
- Ensure that the IUT in state 0, in order to initiate a call supporting 64 kbits/s Unrestricted, sends a
SETUP message containing a Bearer Capability (BC) IE with an Information Transfer Capability
field encoded as Unrestricted and enters state 1 (reference ETS 300 172 [1], subclauses 10.1.1,
14.5.5, A.4.1.Z1).
This STP and its derived TP are only applicable to an IUT if support of 64 kbit/s Unrestricted Digital
Information has been declared in the PICS.
PSS1_BC/PC/CA/PV/CE/TC0110XD
- Ensure that the IUT in state 0, in order to initiate a call supporting 64 kbits/s Unrestric
...