SIST ETS 300 806-1 E1:2005

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic functional protocol for the support of supplementary services; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

Conformance Test Specification (TTCN) for the protocol for layer 3 generic functional protocol for the support of supplementary services between exchanges of private integrated services networks for the control of circuit-switched.

Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Generični funkcijski protokol za podporo dopolnilnim storitvam - 1. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - Specifikacija

General Information

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Mandate: IT-74
• Mandate: T-245
• Ref Project: ETSI ETS 300 806-1 ed.1 (1998-02) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic functional protocol for the support of supplementary services; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 806-1 E1:2005
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,610HGFHQWUDOQLVLJQDOL]DFLMVNL
SURWRNRO*HQHULþQLIXQNFLMVNLSURWRNRO]DSRGSRURGRSROQLOQLPVWRULWYDPGHO
=JUDGEDSUHVNXãDOQHJDQL]DLQQDPHQLSUHVNXãDQMD766 736SHFLILNDFLMD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic
functional protocol for the support of supplementary services; Part 1: Test Suite Structure
and Test Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: ETS 300 806-1 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 806-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 806-1 E1:2005

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

SIST ETS 300 806-1 E1:2005
EUROPEAN ETS 300 806-1
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA-00110-1
ICS: 33.020
Key words: Layer 3, PINX, PISN, QSIG, supplementary service, testing, TSS&TP
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Generic functional protocol for the
support of supplementary services;
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 806-1 E1:2005
Page 2
ETS 300 806-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 806-1 E1:2005
Page 3
ETS 300 806-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) .10
4.1 TSS for individual TPs .10
4.2 TSS for combined TPs.12
5 Test Purposes (TP).14
5.1 Introduction to Test Purposes.14
5.1.1 Test purposes production method.14
5.1.2 STP identifier.14
5.1.3 Individual TP identifier .14
5.1.4 CTP identifier.14
5.2 Test purpose writing rules.14
5.2.1 Protocol Control.15
5.2.2 GFTC.17
5.3 TPs.18
5.3.1 Call Related procedures for the transport of APDUs .19
5.3.1.1 PC requirements.19
5.3.1.1.1 PC - Sending Facility IE .19
5.3.1.1.2 PC - Receiving Facility IE .19
5.3.1.1.3 PC - Protocol error handling .20
5.3.1.2 GFTC requirements.21
5.3.1.2.1 GFTC - Actions at a Receiving PINX.21
5.3.1.2.2 GFTC - Actions at a Destination PINX.24
5.3.1.3 Relaying requirements.24
5.3.2 Connection Oriented Call Independent APDU transport mechanism .25
5.3.2.1 PC requirements.25
5.3.2.1.1 PC - Actions in the Null state .25
5.3.2.1.2 PC - Actions in the Call Initiated state.26
5.3.2.1.3 PC - Actions in the incoming Call
Proceeding state.26
5.3.2.1.4 PC - Actions in the outgoing Call
Proceeding state.26
5.3.2.1.5 PC - Actions in the Connect Request
state .27
5.3.2.1.6 PC - Actions in the Active state.27
5.3.2.1.7 PC - Connection release.27
5.3.2.1.8 PC - Actions in the Release Request
state .28
5.3.2.1.9 PC - Transport of APDUs associated
with a CISC.28
5.3.2.1.10 PC - Protocol error handling .30
5.3.2.1.11 PC requirements - Layer Management
procedures.38
5.3.2.1.12 PC - Protocol timer values .39
5.3.2.2 GFTC requirements.40
5.3.2.2.1 GFTC - Actions at a Transit PINX .40
5.3.2.2.2 GFTC - Actions at an End PINX .43
5.3.2.2.3 GFTC - Actions at a Terminating PINX 44
5.3.2.2.4 GFTC - Actions at a Destination PINX.45

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

SIST ETS 300 806-1 E1:2005
Page 4
ETS 300 806-1: February 1998
5.3.2.3 Relaying requirements . 45
5.3.3 Call Related procedures for the transport of Notifications. 46
5.3.3.1 PC requirements . 46
5.3.3.1.1 PC - Sending Notification information . 46
5.3.3.1.2 PC - Receiving Notification
information . 47
5.3.3.1.3 PC - Protocol error handling. 48
5.3.3.2 Generic Functional Transport Control requirements. 50
5.3.3.2.1 GFTC - Actions at a Transit PINX. 50
5.3.3.2.2 GFTC - Actions at a Receiving End
PINX. 50
5.3.4 Application Layer requirements . 50
5.3.4.1 Co-ordination Function requirements. 50
5.3.4.2 ROSE requirements. 51
5.3.5 Verification of state . 52
6 Final TPs. 52
6.1 Requirements for Call Related procedures for the transport of APDUs. 52
6.1.1 Combined TPs. 52
6.1.2 TPs end-use cross reference table. 58
6.2 Requirements for Call Independent Connection Oriented procedures for the transport
of APDUs. 61
6.2.1 Combined TPs. 61
6.2.2 TPs end-use cross reference table. 68
6.3 Requirements for Call Related procedures for the transport of Notifications. 73
6.3.1 Combined TPs. 73
6.3.2 TPs end-use cross reference table. 76
6.4 Requirements for Application Layer . 78
6.4.1 Combined TPs. 78
6.4.2 Test purposes end-use cross reference table . 78
7 Compliance clause . 79
Annex A (informative): Index of TPs. 80
History. 82

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

SIST ETS 300 806-1 E1:2005
Page 5
ETS 300 806-1: February 1998
Foreword
This final 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; Generic functional protocol for the support of supplementary services".
The title of each part is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS & TP)";
Part 2: "Abstract Test Suite specification (ATS)".
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 806-1 E1:2005
Page 6
ETS 300 806-1: February 1998
Blank page

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

SIST ETS 300 806-1 E1:2005
Page 7
ETS 300 806-1: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Test Suite Structure (TSS) and Test
Purposes (TPs) specification for the Generic Functional Protocol (GFP) for the support of supplementary
services 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 greater
probability of inter-operability. The TSS and TPs specification covers the procedures described in
ETS 300 239 [1], but omitting those procedures that are better tested by testing the individual
supplementary services that use those procedures.
This ETS excludes the following:
- Connectionless APDU Transport Mechanism, (i.e. no TPs have been derived from ETS 300 239 [1],
subclause 7.2);
- Dialogue Service Element (DSE), (i.e. no TPs have been derived from ETS 300 239 [1],
subclause 8.4);
- Remote Operation Service Element (ROSE) except for actions on receiving invalid or unrecognized
APDUs;
- Manufacturer Specific Information;
- Testing of originating and incoming gateway PINXs for Call Related procedures and Call
Independent Signalling Connections (CISC);
- Source PINX requirements for APDUs and Notifications (i.e. no TPs have been derived from
ETS 300 239 [1], subclauses 7.1.2.1, 7.3.2.1, 7.3.3.4, 7.4.3.1).
NOTE 1: Originating, incoming gateway and Source PINX and valid behaviour of ROSE are
excluded because they are impractical to test without the use of a particular
supplementary service. However, although it is outside the scope of this ETS, some
TPs within this ETS may be applicable to originating or incoming gateway PINX in
addition to roles covered by the scope.
NOTE 2: Although there are no test purposes testing source PINX requirements, some test
purposes test the behaviour where the IUT acts as a source PINX, for example where
a PINX is acting as a source PINX to send a Reject APDU.
NOTE 3: This ETS does not contain any test purposes specifically for outgoing gateway PINXs,
however the test purposes for terminating PINXs are generally also applicable to
outgoing gateway PINXs.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646 [5]) is used as basis for the
test methodology.
This TSS and TP specification standard is applicable for the support of supplementary services at the
Q-reference point between Private Integrated Services Network Exchanges (PINXs) connected together
within a PISN. The Q reference point is defined in ISO/IEC 11579-1 [13].
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 239 (1995): "Private Integrated Services Network (PISN); Inter-
exchange signalling protocol; Generic functional protocol for the support of
supplementary services". [ISO/IEC 11582 modified]

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

SIST ETS 300 806-1 E1:2005
Page 8
ETS 300 806-1: February 1998
[2] ETS 300 172 (1995): "Private Integrated Services Network (PISN) ; Inter-
exchange signalling protocol; Circuit-mode basic services" [ISO/IEC 11572
modified]
[3] ETS 300 406 (1995): "Methods for testing and specification (MTS); Protocol and
profile conformance testing specifications; Standardization Methodology".
[4] ETS 300 415 (1996): "Private Integrated Services Network (PISN); Terms and
definitions".
[5] ISO/IEC 9646-1: "Information technology; Open Systems Interconnection;
Conformance testing methodology and framework - Part 1: General Concepts".
[6] ETS 300 475-1 (1995): "Private Integrated Services Network (PISN); Reference
configuration - Part 1: Reference configuration for PISN eXchanges (PINXs)".
[7] CCITT Recommendation I.112 (1988): "Vocabulary of terms for ISDNs".
[8] CCITT Recommendation X.219 (1988): "Remote operations: Model, Notation
and Service definition".
[9] CCITT Recommendation X.229 (1988): "Remote Operations: Protocol
specification".
[10] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference model".
[11] ISO/IEC 11582 (1995): "Information technology - telecommunications and
information exchange between systems - Private Integrated Services Network -
Generic functional protocol for the support of supplementary services - Inter-
exchange signalling procedures and protocol".
[12] ISO/IEC 9646-2: "Information technology; Open Systems Interconnection;
Conformance testing methodology and framework - Part 2: Abstract Test Suite
Specification".
[13] ISO/IEC 11579-1 (1994): "Information technology - Telecommunications and
information exchange between systems - Private integrated services network -
Part 1: Reference configuration for PISN Exchanges (PINX)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the terminology defined in ETS 300 415 [4] and in CCITT
Recommendation I.112 [7] applies. If there is any conflict the definitions in ETS 300 415 [4] shall take
precedence. The following definitions also apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [5].
combined test purpose: A test purpose produced by combining two or more individual test purposes.
Implementation Under Test (IUT): See ISO/IEC 9646-1 [5].
individual test purpose: A test purpose focusing on a single conformance requirement, produced before
any combining of test purposes.
final test purpose : A test purpose which is intended to be mapped to a single test case (except if it is
untestable).

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

SIST ETS 300 806-1 E1:2005
Page 9
ETS 300 806-1: February 1998
NOTE: In this ETS final test purposes are either combined TPs or uncombined (i.e. individual)
TPs.
originating PINX: See ETS 300 239 [1].
PICS proforma: See ISO/IEC 9646-1 [5].
PIXIT proforma: See ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5].
Protocol Implementation eXtra Information For Testing (PIXIT): See ISO/IEC 9646-1 [5].
Super Test Purpose (STP): A general test purpose from which one or more test purposes may be
derived. These derived test purposes may be more detailed than the Super Test Purpose.
terminating PINX: See ETS 300 239 [1].
transit PINX: See ETS 300 239 [1].
uncombined test purpose: An individual test purpose which is not combined into any Combined Test
Purpose.
NOTE 2: These terms are not defined in ISO/IEC 9646 but correspond to items referred to in
ISO/IEC 9646-2 [12] subclause 10.3. The "more specific test objectives" referred to in
subclause 10.3.1 are here referred to as Super Test Purposes. The terms Individual
Test Purpose and Combined Test Purpose have the same meanings here as in
subclause 10.3.3.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
APDU Application Protocol Data Unit
ATS Abstract Test Suite
BI Basic Interconnection test
BV ValiBehaviour tests
CA CApability test
CF Co-ordination Function
CISC Call Independent Signalling Connection
CLTA ConnectionLess Transport of APDUs
COTA Connection Oriented Transport of APDUs
COTN Connection Oriented Transport of Notifications
CR Call Related procedures
DSE Dialogue Service Element
GFT Generic Functional Transport
GFTC Generic Functional Transport Control
IE Information Element
IO InOpportune behaviour tests
ISO International Organization for Standardization
IUT Implementation Under Test
IV InValid behaviour tests
MI Mixed
MSI Manufacturer Specific Information
MTS Methods for testing and specification
NFE Network Facility Extension
NFE Network Facility Extension
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
QSIG Q interface Signalling protocol

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

SIST ETS 300 806-1 E1:2005
Page 10
ETS 300 806-1: February 1998
ROSE Remote Operations Service Element
SCM Signalling Carriage Mechanism
STP Super Test Purpose
TI TImers
TP Test Purpose
TSS Test Suite Structure
4 Test Suite Structure (TSS)
Two separate Test Suite Structures (TSSs) have been designed, one to cover the individual TPs, and
another one to cover the combined TPs (CTPs) and uncombined TPs.
4.1 TSS for individual TPs
Following the rules described in ETS 300 406 [3], subclause 7.4.1.1, the test suite for the individual TPs is
structured as a tree with the following levels:
1st level: the name representing the base specification (ETS 300 239 [1]);
Generic Functional Protocol (GFP).
2nd level: the entities of the base specification;
- Protocol Control (PC);
- Generic Functional Transport Control (GFTC);
- Co-ordination Function (CF);
- ROSE (RO).
3rd level: the type of signalling connection;
- Call Related procedures (CR);
- Call Independent procedures (CISC);
- Procedures.
4th level: the type of transport mechanism;
- Connection Oriented Transport of APDUs (COTA);
- Connection Oriented Transport of Notifications (COTN);
- ConnectionLess Transport of APDUs (CLTA);
- Transport of APDUs (TA).
5th level: the nature of the test;
- Basic Interconnection test (BI);
- CApability test (CA);
- ValiBehaviour tests (BV);
- InValid behaviour tests (IV);
- InOpportune behaviour tests (IO);
- TImers (TI).
NOTE 1: All Basic Interconnection and Capability test purposes are also Valid Behaviour test
purposes. Basic interconnection test purposes are also Capability test purposes.
NOTE 2: As the scope of this ETS does not cover the whole of ETS 300 239 [1] certain groups
in the TSS contain no test purposes.

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

SIST ETS 300 806-1 E1:2005
Page 11
ETS 300 806-1: February 1998
Figure 1 shows the GFP Test Suite Structure overview. Not all the branches have been expanded to the
final details.
GFP Test Suite
Generic Functional Coordination Protocol Control
ROSE
Transport Control Function
(GFTC) (CF) (RO) (PC)
Call Related Call Independent Call Related Call Independent
Procedures Procedures
procedures procedures procedures procedures
(CR) (CISC) (P) (P) (CR) (CISC)
...
...
Connection Connection Connection Connection
Transport of Transport of
Oriented
Oriented Less
Oriented
Transport of
Transport Transport
Transport
APDUs APDUs
Notifications
of APDUs
of APDUs
of APDUs
(COTN) (TA) (TA)
(COTA)
(CLTA)
(COTA)
... ... ... ...
...
Basic Capability Valid Invalid Inopportune Timer
Behaviour
Behaviour Behaviour
Interconnection
(BI) (CA) (TI)
(BV) (IV) (IO)
... ... ... ... ... ...
Figure 1: GFP TSS overview for individual TPs

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

SIST ETS 300 806-1 E1:2005
Page 12
ETS 300 806-1: February 1998
Figure 2 shows the details of the GFP TSS.
GFP
PC
GFTC
CF RO
P P CR CISC
CR CISC
COTA CLTA
COTA COTN TA TA COTA COTN COTA CLTA
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
TI IO IV BV CA BI
BI CA BV IV IO TI
TI IO IV BV CA BI
BI CA BV IV IO TI
Figure 2: Detailed GFP TSS for individual TPs
4.2 TSS for combined TPs
Following the rules described in ETS 300 406 [3], subclause 7.4.1.1, the test suite for the combined TPs
(CTPs) and TPs which remain uncombined is structured as a tree with the following levels:
1st level: the name representing the base specification (ETS 300 239 [1]);
Generic Functional Protocol (GFP).
2nd level: the type of signalling connection;
- Call Related procedures (CR);
- Call Independent procedures (referred by CISC).
3rd level: the type of transport mechanism;
- Connection Oriented Transport of APDUs (COTA);
- Connection Oriented Transport of Notifications (COTN);
- ConnectionLess Transport of APDUs (CLTA).
4th 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);
- TImers (TI);
- Mixed (MI) (This group contains CTPs combining Valid and Invalid behaviour).
NOTE: All Basic Interconnection and Capability test purposes are also Valid Behaviour test
purposes.

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

SIST ETS 300 806-1 E1:2005
Page 13
ETS 300 806-1: February 1998
Figure 3 shows the GFP Test Suite Structure overview. Not all the branches have been expanded to the
final details.
GFP Test Suite
Call Related Call Independent
procedures procedures
(CR) (CISC)
Connection
Connection Connection Connection
Oriented
Oriented Oriented Less
Transport of
Transport Transport Transport
of APDUs Notifications of APDUs of APDUs
(COTA) (COTN) (COTA) (CLTA)
... ... ...
Basic Capability Valid Invalid Inopportune Timer Mixed
Interconnection Behaviour Behaviour Behaviour
(BI) (CA) (BV) (IV) (IO) (TI) (MI)
... ... ... ... ... ... ...
Figure 3: GFP TSS overview for combined TPs
Figure 4 shows the details of the GFP TSS.
GFP
CISC
CR
COTA COTN COTA CLTA
BI CA BV IV IO TI MI
BI CA BV IV IO TI MI
BI CA BV IV IO TI MI BI CA BV IV IO TI MI
Figure 4: Detailed GFP TSS for combined TPs

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

SIST ETS 300 806-1 E1:2005
Page 14
ETS 300 806-1: February 1998
5 Test Purposes (TP)
5.1 Introduction to Test Purposes
5.1.1 Test purposes 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, but excluding those that are more effectively tested by testing the individual
supplementary services which used them.
This first phase led either 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), or directly to the production of individual TPs.
The second phase consisted of deriving from each STP several individual TPs. The criteria for deriving
these individual TPs took into account the TSS, in order to ensure good coverage for testing. The
objective was to derive individual 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 individual
TPs may be derived from an STP.
Although an STP may generate a number of individual TPs, not all those possible are retained, as they
may deal with a requirement which has already been covered by a previous individual TP. This ensures
more efficient testing with good coverage, avoiding repeatedly testing the same aspect of the standard,
probably leading to the same verdict each time.
Some individual TPs have been combined together in order to have a more complete test, generally
where it is not possible to test particular test purposes in isolation. These are called Combined Test
Purposes (CTPs). The final set of Test Purposes will be composed of both CTPs and uncombined
individual TPs, and it is this final set of TPs which corresponds to test cases in the ATS.
5.1.2 STP identifier
The identifier for a super test purpose consists of the letters SP and a four digit number in the range 1 001
to 1 067, (e.g. SP1009).
5.1.3 Individual TP identifier
The identifier for an individual test purpose consists of the letters TP and a four digit number in the range
2 001 to 2 254, (e.g. TP2058). The identifier for an uncombined TP in the final set of test purposes is the
corresponding individual TP identifier.
5.1.4 CTP identifier
The identifier for an combined test purpose consists of the letters CP and a four digit number in the range
3 001 to 3 073, (e.g. CP3025).
5.2 Test purpose 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.

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

SIST ETS 300 806-1 E1:2005
Page 15
ETS 300 806-1: February 1998
5.2.1 Protocol Control
Table 1 gives the writing rules for test purposes with a goal, for protocol control requirements.
Table 1: TP writing rules with a goal for protocol control requirements
STRUCTURE VALUES
Ensure that the IUT
in state for a 0,1, 2, 3, etc.
, call,
CISC, etc.
In order to initiate/release a CISC,
in order to indicate that the CISC is established,
in order to send a Facility IE related to that call,
when requested by GFT-Control to send a Facility IE related
to that call, etc.
When a SCM connection does not already exist,
when a/no XXX message is to be sent, etc.
Passes that IE to GFT-Control,
establishes a SCM connection,
sends, saves, does, etc.
if the action is sending
a message containing FACILITY, NOTIFY, etc.
a) a IE including Facility, Notification Indicator, etc.
a with a NFE, APDU, etc.
sourceEntity, destinationEntityAddress, etc.
b)
[encoded as endPINX, anyTypeOfPINX, etc.
or not included]
and back to a) or b)
[and remains in the same state
0, 1, 2, etc.
or and enters state ]
NOTE: In this table normal text in the left hand column is included in the test purpose, text between
< and > is replaced by a value (examples given in the right column). Text in bold is not
included in the test purpose, [ and ] are used to delimit options, and a) and b) are labels.

---------------------- Page: 17 ----------------------

SIST ETS 300 806-1 E1:2005
Page 16
ETS 300 806-1: February 1998
Table 2 gives the writing rules for TPs with a trigger, for protocol control requirements.
Table 2: TP writing rules with a trigger for protocol control requirements
STRUCTURE VALUES
Ensure that the IUT
i
...