SIST EN 301 933-3 V1.1.1:2005

• Abstract:

  Conformance Testing for SRF specification.

• Status: Published
• Publication Date: 31-Dec-2004
• 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-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI EN 301 933-3 V1.1.1 (2003-01) - Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF); Part 3: Specialized Resource Function (SRF)

SIST EN 301 933-3 V1.1.1:2005 is the SIST edition of ETSI EN 301 933-3 V1.1.1 for Intelligent Network (IN) Capability Set 3 (CS3). It specifies the Test Suite Structure and Test Purposes (TSS&TP) for conformance testing of the Specialized Resource Function (SRF) behaviour of the Service Switching Function (SSF) in INAP implementations.

What does SIST EN 301 933-3 V1.1.1:2005 specify?

SIST EN 301 933-3 V1.1.1:2005 specifies the TSS&TP for testing SRF-related SSF operations in Core INAP CS3. It is a conformance-testing document: it defines what to test and how the test purposes are organized, not a product specification for network operation.

The document says the Implementation Under Test (IUT) is always an SSF. It also states that the direct SCF-SRF interface is outside the scope of this part, so the testing focuses on SSF behaviour when it relays SRF operations or sets up temporary connections.

The document is organized into clauses for scope, references, definitions and abbreviations, general test-purpose rules, test configurations, and SRF test purposes. It is completed by annexes that provide parameter values and bibliography material.

Annex	What it covers
Annex A	Parameter values used in MSCs for CORE INAP CS3 - SRF primitives
Annex B	Bibliography

What are the key requirements of SIST EN 301 933-3 V1.1.1:2005?

SIST EN 301 933-3 V1.1.1:2005 sets out the conformance test purposes for SSF behaviour in SRF scenarios. In practice, this means a test campaign can use the document to decide which SSF features are applicable, which test cases to include, and what result each test must produce.

Test scope and basic model

Clause 4 says the IUT is always an SSF, and it distinguishes two basic scenarios:

• the SSF acts as a relay between SCF and SRF operations
• the SSF establishes a temporary connection to an assisting SSF, a handed-off SSF, or directly to an SRF

This matters because the same SRF-related function can be exercised through different SSF roles. A lab has to choose the right scenario before running a test case.

Test-purpose organization and selection

Clause 4 groups the test purposes into two main groups:

• SSF Relaying
• Direct SCF-SRF operation

Within each group, test purposes are further grouped by elementary procedures such as ConnectToResource, PlayAnnouncement, ScriptRun, or EstablishTemporaryConnection. Clause 4.6 also defines selection parameters such as CONFIGURATION, SSF_IS_INITIATING, SSF_IS_ASSISTING, SSF_IS_HANDED_OFF, SSF_IMPLEMENTS_SCRIPTS, SSF_PREDEFINED_SRF, SSF_ADRESSED_SRF, ETC_TO_ASSIST, ETC_TO_SRF, CO_TO_HANDED_OFF, and CO_TO_SRF. These parameters let a test lab deselect cases that do not apply to a specific implementation.

In practice, this is the part that maps the standard to a real product. A buyer or tester can compare the implemented SSF functions against the selection conditions and see which cases are mandatory for that implementation.

How each test purpose is described

Clause 4.5 defines the structure of each test-purpose entry. Each TP gives a name, a purpose, requirement references, an optional selection condition, a preamble, a test description, pass criteria, and a postamble.

That structure matters because it tells the tester exactly what to set up, what event sequence to send or expect, and how to judge success. It also makes the document suitable for deriving an Abstract Test Suite (ATS), with each TP intended to become a test case of the same name.

Test configurations

Clause 5 defines two generic test configurations:

• Configuration A - the SSF relays INAP operations between the SCF and the SRF
• Configuration B - the Initiating SSF uses EstablishTemporaryConnection or Connect to reach the SRF through an assisting or handed-off SSF

This distinction matters because the observable interfaces are different. In Configuration A, the tester observes the relay behaviour on the L1 interface and any signalling connections. In Configuration B, the tester also simulates the assisting or handed-off SSF role.

SRF-related procedures and expected behaviour

Clause 6 covers the test purposes themselves. The main procedures include:

• ConnectToResource
• DisconnectForwardConnection and DisconnectForwardConnectionWithArgument
• PlayAnnouncement
• PromptAndCollectUserInformation
• PromptAndReceiveMessage
• ScriptRun, ScriptClose, ScriptEvent, ScriptInformation
• RequestReportUTSI and SendSTUI
• EstablishTemporaryConnection and Connect for the direct methods

The practical point is that the document checks whether the SSF accepts valid requests, rejects invalid ones with the right error, and handles state-dependent sequences correctly. It also checks user interaction functions, such as announcement, prompting, recording, and script-driven interactions.

Error handling and state-dependent sequencing

A major part of clause 6 is negative testing. The test purposes check for errors such as missingParameter, unknownLegID, unexpectedDataValue, unexpectedComponentSequence, taskRefused, cancelled, cancelFailed, and eTCFailed.

This matters because SRF behaviour is not just about accepting valid operations. The SSF must also respond correctly when a request is out of sequence, refers to the wrong leg or call segment, or omits a required parameter. In practice, this is how interoperability and robustness are verified.

Preambles, postambles, and abstract signalling

Clause 6 defines preambles and postambles for SRF testing, along with the Abstract Signalling Primitives used to model call progress and user data. It also describes how CallProgress and Data primitives represent the effects of operations such as PlayAnnouncement, PromptAndCollectUserInformation, PromptAndReceiveMessage, SendSTUI, RequestReportUTSI, and script interactions.

This means the test suite does not only watch for INAP messages. It also models the signalling and user-side effects that should accompany those messages, which is important when validating end-to-end call handling.

What terms does SIST EN 301 933-3 V1.1.1:2005 define?

• Abstract Test Suite (ATS) - the set of test cases derived from the test purposes and used to execute conformance testing.
• Implementation Under Test (IUT) - the SSF implementation being tested.
• System Under Test (SUT) - the implementation or system being exercised during testing.
• Protocol Implementation Conformance Statement (PICS) - the implementer’s statement used to identify the implemented features and select applicable tests.
• Protocol Implementation eXtra Information for Testing (PIXIT) - additional implementation-specific information used to parameterize the test suite.
• Test Purpose (TP) - a statement of one conformance requirement to be checked by one test case.
• Service Switching Function (SSF) - the network function tested in this document.
• Specialized Resource Function (SRF) - the SRF behaviour that the SSF must support or relay in the tested scenarios.

Who uses SIST EN 301 933-3 V1.1.1:2005?

SIST EN 301 933-3 V1.1.1:2005 is used by conformance test laboratories, equipment manufacturers, network operators, and quality or procurement teams working with INAP CS3 implementations. It is especially relevant when a project needs to verify SSF behaviour for SRF-related services before deployment or acceptance.

Typical uses include:

• building an ATS from the listed test purposes
• mapping PICS and PIXIT information to the TP selection conditions
• verifying correct handling of announcements, user input, scripts, and service-user information
• checking error handling for invalid call states, wrong legs, or missing parameters
• confirming whether an SSF works as a relay, an initiating node, an assisting node, or a handed-off node

Which standards are used with SIST EN 301 933-3 V1.1.1:2005?

Standard	What it contributes
ETSI EN 301 931-1	Common aspects of INAP CS3 protocol specification
ETSI EN 301 931-2	SCF-SSF interface protocol specification and the testing-related protocol basis used by this part
ETSI EN 301 931-3	SCF-SRF interface protocol specification referenced for SRF-related testing and resource addressing details
ETSI EN 301 933-1	CS3 SSF TSS&TP for the basic capability set, used as part of the overall testing framework
ETSI EN 301 933-2	CS3 SSF TSS&TP for Call Party Handling, used alongside this part in the complete CS3 test set
ISO/IEC 9646-1	Base conformance testing methodology
ISO/IEC 9646-2	Additional conformance testing methodology basis

What does the SIST EN 301 933-3 V1.1.1:2005 document contain?

The document contains the test-purpose structure, the selection model, and the detailed TP descriptions for SRF-related SSF behaviour. It also includes the two generic test configurations, the procedure groupings, and the notation rules used in the TP descriptions.

It uses tables to define selection parameters, test parameters for parametrization, abstract signalling primitive parameters, and the work-item structure of the test purposes. It also provides many preamble and postamble names, which are the reusable setup and cleanup sequences for specific call states.

Annex A gives parameter values used in MSCs for CORE INAP CS3 - SRF primitives, so a test designer can build consistent message sequences without redefining the same values in every test. Annex B provides bibliography references for related documents.

The result is a document that supports conformance test design, test execution, and acceptance review for SSF implementations that interact with SRF functions under INAP CS3.

SLOVENSKI STANDARD
01-januar-2005
Inteligentno omrežje (IN) – Tretji nabor zmožnosti inteligentnega omrežja (CS3) –
Aplikacijski protokol inteligentnega omrežja (INAP) – Zgradba preskušalnega niza
in namen preskušanja (TSS&TP) – Specifikacija za funkcijo komutacije storitev
(SSF) – 3. del: Funkcija posebnih virov (SFR)
Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network
Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS&TP)
specification for Service Switching Function (SSF); Part 3: Specialized Resource
Function (SRF)
Ta slovenski standard je istoveten z: EN 301 933-3 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Intelligent Network (IN);
Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP);
Test Suite Structure and Test Purposes (TSS&TP)
specification for Service Switching Function (SSF);
Part 3: Specialized Resource Function (SRF)

2 ETSI EN 301 933-3 V1.1.1 (2003-01)

Reference
DEN/SPAN-120063-3-3
Keywords
IN, CS3, INAP, TSS&TP, SSF, CTM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
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 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 301 933-3 V1.1.1 (2003-01)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Test Purpose generalities.8
4.1 Introduction.8
4.2 Grouping of Test purposes .8
4.3 Source of Test purpose definitions .8
4.4 Method used for developing Test purposes.8
4.5 Method used for Test purpose description .9
4.5.1 Void.9
4.5.2 Test categories.9
4.5.3 Test purpose naming convention .10
4.5.4 Preambles and their naming conventions.10
4.6 Test purpose parametrization and selection.11
5 Test configurations.17
6 Test purposes for SRF functions .19
6.1 SRF-related procedures.19
6.1.1 List of procedures .19
6.1.2 Definitions of the procedures.20
6.2 Structure of the test purposes .22
6.3 Notations.23
6.4 Preambles and postambles for SRF.26
6.4.1 Preambles used for SRF function testing.26
6.4.1.1 PRE_WFI preamble.26
6.4.1.2 PRE_S2P_MON preamble.26
6.4.1.3 PRE_S1P_1P_MON preamble.27
6.4.1.4 PRE_1P_MON preamble.27
6.4.1.5 PRE_S1P_1P_WFI preamble.27
6.4.1.6 PRE_1P_WFI preamble.27
6.4.1.7 PRE_OS_ASSIST preamble.28
6.4.1.8 PRE_OS_HANDED_OFF preamble.28
6.4.1.9 PRE_UI_S2P_MON preamble.28
6.4.1.10 PRE_UI_S1P_1P_MON preamble.28
6.4.1.11 PRE_UI_1P_MON preamble.28
6.4.1.12 PRE_UI_1P_WFI preamble.29
6.4.1.13 PRE_UI_CTR_PA preamble.29
6.4.1.14 PRE_UI_CTR_PR_S2P preamble.30
6.4.1.15 PRE_UI_CTR_PR_S1P_1P preamble.30
6.4.1.16 PRE_UI_CTR_PR_1P preamble.30
6.4.1.17 PRE_UI_CTR_UT_S2P preamble.30
6.4.1.18 PRE_UI_CTR_UT_S1P_1P preamble.30
6.4.1.19 PRE_UI_CTR_UT_1P preamble.31
6.4.2 Postambles used for SRF function testing .31
6.4.2.1 ReleaseA.31
6.4.2.2 ReleaseAB.31
6.4.2.3 ReleaseAC.31
6.4.2.4 ReleaseABC.32
6.4.2.5 ReleaseABCD.32
6.4.2.6 DisconnectForwardReleaseA.32
ETSI
4 ETSI EN 301 933-3 V1.1.1 (2003-01)
6.4.2.7 DisconnectForwardReleaseAB.32
6.4.2.8 DisconnectForwardReleaseAC.32
6.4.2.9 DisconnectForwardReleaseABC.33
6.4.2.10 ScriptCloseDisconnectForwardReleaseA().33
6.4.2.11 ScriptCloseDisconnectForwardReleaseAB().33
6.4.2.12 DisconnectFWAReleaseA().33
6.4.2.13 DisconnectFWAReleaseAB().33
6.4.2.14 DisconnectFWAReleaseAB2().34
6.4.2.15 DisconnectFWAReleaseAC().34
6.4.2.16 DisconnectFWAReleaseABC().34
6.4.2.17 DisconnectFWAReleaseABCD().34
6.5 Test purposes for the relay method.34
6.5.1 AssistRequestInstructions procedure.35
6.5.2 ConnectToResource (CR) procedure.36
6.5.3 DisconnectForwardConnection procedures.44
6.5.3.1 DisconnectForwardConnection (DF) procedure (without argument).44
6.5.3.2 DisconnectForwardConnectionWithArgument (DW) procedure.45
6.5.4 Play Announcement (PA) procedure .47
6.5.5 PromptAndCollectUserInformation (PC) procedure .51
6.5.6 PromptAndReceiveMessage (PR) procedure.55
6.5.7 Scripts.58
6.5.7.1 ScriptRun.58
6.5.7.2 ScriptClose.61
6.5.7.3 ScriptEvent.63
6.5.7.4 ScriptInformation.64
6.5.8 User-service information (USI) procedures.67
6.5.8.1 RequestReportUTSI procedure.67
6.6.8.2 SendSTUI procedure.69
6.5.8.3 ReportUTSI procedure.72
6.5.9 ActivityTest (AT) procedure.73
6.6 Test purposes for the direct SCF-SRF interaction method .73
6.6.1 Initiating SSF (IUT) interacting with Assisting SSF .73
6.6.1.1 EstablishTemporaryConnection (EC) procedure .73
6.6.1.2 Disconnect procedures.77
6.6.1.2.1 DisconnectForwardConnection (DF) procedure (without argument).77
6.6.1.2.2 DisconnectForwardConnectionWithArgument (DW) procedure .78
6.6.2 Initiating SSF (IUT) interacting with Handed-off SSF.80
6.6.2.1 Connect (CO) procedure .80
6.6.3 Initiating SSF (IUT) directly interacting with SRF.82
6.6.3.1 EstablishTemporaryConnection (EC) procedure .82
6.6.3.2 Disconnect procedures.85
6.6.3.2.1 DisconnectForwardConnection (DF) procedure (without argument).85
6.6.3.2.2 DisconnectForwardConnectionWithArgument (DW) procedure .86
Annex A (normative): Parameter values used in MSCs for CORE INAP CS3 - SRF
primitives.89
Annex B (informative): Bibliography.91
History .92

ETSI
5 ETSI EN 301 933-3 V1.1.1 (2003-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 3 of a multi-part deliverable covering the Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS&TP) specification for
Service Switching Function (SSF), as identified below:
Part 1: "Basic capability set of CS3";
Part 2: "Call Party Handling (CPH)";
Part 3: "Specialized Resource Function (SRF)".

National transposition dates
Date of adoption of this EN: 10 January 2003
Date of latest announcement of this EN (doa): 30 April 2003
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 October 2003
Date of withdrawal of any conflicting National Standard (dow): 31 October 2003

ETSI
6 ETSI EN 301 933-3 V1.1.1 (2003-01)
1 Scope
The present document contains the Test Suite Structure and Test Purposes (TSS&TP) for Specialized Resource
Function (SRF), part of Core INAP CS-3.
The present document provides the Test Suite Structure and Test Purposes (TSS&TP) for the testing of the Specialized
Resource Function (SRF) operations of the Service Switching Function (SSF), defined for the Intelligent Network
Application Protocol (INAP) of Intelligent Network (IN) Capability Set 3 (CS3) according to EN 301 931-1 [1] and
EN 301 931-2 [2].
The present document is completed by other parts constituting the testing of the CS3 Core INAP specifications:
EN 301 933-1 [5] (Service Switching Function) and EN 301 933-2 [6] (Call party handling functions).
ISO/IEC 9646-1 [8] and ISO/IEC 9646-2 [9] are used as the basis for the testing methodology.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ETSI EN 301 931-1: "Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP); Protocol specification; Part 1: Common
aspects".
[2] ETSI EN 301 931-2: "Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP); Protocol specification; Part 2: SCF-SSF
interface".
[3] ETSI EN 301 931-3: "Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP); Protocol specification; Part 3: SCF-SRF
interface".
[4] Void.
[5] ETSI EN 301 933-1: "Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3);
Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes
(TSS&TP) specification for Service Switching Function (SSF); Part 1: Basic capability set of
CS3".
[6] ETSI EN 301 933-2: "Intelligent Network (IN); Intelligent Network capability Set 3 (CS3);
Intelligent Network Application protocol (INAP); Test Suite Structure and Test Purposes
(TSS&TP) specification for Service Switching Function (SSF); Part 2: Call Party Handling
(CPH)".
[7] Void.
[8] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[9] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
ETSI
7 ETSI EN 301 933-3 V1.1.1 (2003-01)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
- terms defined in EN 301 931-1 [1];
- terms defined in ISO/IEC 9646-1 [8] and in ISO/IEC 9646-2 [9].
In particular, the following terms defined in ISO/IEC 9646-1 [8] apply:
- Abstract Test Suite (ATS);
- Implementation Under Test (IUT);
- System Under Test (SUT);
- Protocol Implementation Conformance Statement (PICS).
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
BI Invalid Behaviour tests
BO Inopportune Behaviour tests
BV Valid Behaviour tests
CA Capability tests
CPH Call Party Handling
CS Call Segment
CS Capability Set
EDP-R Event Detection Point - Request
FSM Finite State Machine
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Intelligent Peripheral
iS initiating SSF
iSSP initiating SSP
IUT Implementation Under Test
MSC Message Sequence Chart
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
SCF Service Control Function
SCP Service Control Point
SDF Service Data Function
SDL Specification and Description Language
SRF Specialized Resource Function
SSF Service Switching Function
SSP Service Switching Point
SUT System Under Test
TCAP Transaction Capabilities Application Part
TP Test Purpose
TSS Test Suite Structure
ETSI
8 ETSI EN 301 933-3 V1.1.1 (2003-01)
4 Test Purpose generalities
4.1 Introduction
The Implementation Under Test (IUT) is always an SSF. The testing of the direct interface between SCF and SRF is
not within the scope of the present document.
Two basic scenarios are possible:
A) The SSF acts as a relay for operations exchanged between the SCF and the SRF;
B) The SSF establishes a temporary connection to an assisting SSF or handed-off SSF or directly to an SRF.
In A) the SSF is tested together with the addressed SRF, and, possibly, together with an intermediate
Assisting/Handed-off SSF. The SRF can be integrated in the SSF or not. Case A) is applicable to an SSF operating as:
1) Initiating SSF,
2) Assisting SSF, or
3) Handed-off SSF.
Individual TPs can be applicable to a true subset of the three SSF sub-functions. To handle this, Test Parameters
applicable to TP Selection are defined (see clause 4.6).
Case B) is only applicable to an SSF operating as an Initiating SSF. The operation used to connect to the SRF is
EstablishTemporaryConnection.
Configurations for cases A) and B) are defined in clause 5.
A TP is defined for one or several conformance requirements to be tested. It is expected, that each TP will result in a
test case keeping the same name, specified in the ATS.
4.2 Grouping of Test purposes
According to the two basic scenarios defined in the previous clause, the test purposes are grouped in the following 2
main groups:
a) SSF Relaying, and
b) Direct SCF-SRF operation.
Inside a main group the Test purposes are grouped by elementary procedures. A procedure groups elementary INAP
operations belonging together conceptually. The procedures are defined in clause 6.2.
4.3 Source of Test purpose definitions
The test purposes are based on the requirement documented in EN 301 931-1 [1], EN 301 931-2 [2] and
EN 301 931-3 [3].
4.4 Method used for developing Test purposes
See EN 301 933-1 [5].
ETSI
9 ETSI EN 301 933-3 V1.1.1 (2003-01)
4.5 Method used for Test purpose description
The table describing each TP is as shown in table 1.
Table 1: Test purpose description sample
TP name, e.g. IN3_A_BASIC_FC_BV_01

Work item no.:
Temporary work item number; to be deleted when the TPs are stable
IN2 Ref
Reference to INAP CS2 TP (optional)
Purpose: Textual phrasing of the TP to be achieved.
Requirements refs Reference to clause(s) of EN 301 931-2 [2].
For TPs related to the SRF function: also reference to clause(s) of EN 301 931-3 [3].
In the latter case the Part numbers are explicitly indicated (part 2 and/or part 3).
Selection Cond. Reference to a formal selection expression, if the TP is related to an optional INAP feature. If
the field is empty, the TP is unconditional (mandatory requirement(s)).
Preamble: Reference to a preamble or "None".
Test description Sequence of transmitted and received events and timeouts (see clause "TTCN-like
notation").
Textual description is also used, as appropriate.
Pass criteria Indication of reception (or assured non-reception) of decisive message(s) related to the TP.
Postamble: Reference to a postamble or "None".

4.5.1 Void
4.5.2 Test categories
Valid Behaviour tests (BV)
Predefined state transitions are considered as valid. The test purposes in the valid behaviour test sub group cover as far
as reasonable the verification of the normal and exceptional procedures of the various Finite State Machines (FSMs),
i.e. a valid behaviour test is a test where the message sequence and the message contents is considered as valid.
Invalid Behaviour tests (BI)
This test sub group is intended to verify that the IUT is able to react properly having received an invalid Protocol Data
Unit (PDU). An invalid PDU is defined as a syntactically incorrect message.
Inopportune Behaviour tests (BO)
This test group is intended to verify that the IUT is able to react properly in the case an inopportune protocol event
occurring. Such an event is syntactically correct but occurs when it is not expected, e.g. a correctly coded operation is
received in a wrong state (the IUT may respond by sending error UnexpectedComponentSequence).
ETSI
10 ETSI EN 301 933-3 V1.1.1 (2003-01)
4.5.3 Test purpose naming convention
The identifier of the TP is built according to the scheme in table 2.
Table 2: TP identifier naming convention scheme
Identifier: IN3_____
IN3 indicates IN Capability Set 3
= interface: A SSF-SCF interface
B SSF-SRF interface
C SCF-SCF interface
= common set BASIC Basic set for CS3
CPH Call Party Handling from Capability Set 3
SRF SRF-related functions from Capability Set 3
= procedure name like
SF ServiceFiltering
= test category:
BV Valid Behaviour tests
BI Invalid Behaviour tests
BO Inopportune Behaviour tests
= sequential number: (01-99)

Example of test purpose and test case name: IN3_A_BASIC_SF_BV_02

4.5.4 Preambles and their naming conventions
Preambles are used to bring the IUT from the initial state to the state where the test takes place. In the CS3 scheme, the
set of the preambles forms a tree, which means that in order to reach the state created by preamble P3, it is necessary to
execute preamble P1 followed by preambles P2 then P3.
The naming convention used reflects the description of the connection view set by executing the preamble, in terms of
nature of the legs per Call Segment (CS), starting from the stable legs then the ones on hold then the ones in transfer,
with the indication of the number of legs, while the first letter indicates how this configuration was initiated.
The general form is:
a_[stableLegsParty or onHold (legs) or transfer(legs) for CallSegment 1]_[idem for CallSegment2]_[idem for
CallSegment 3]
where:
a is letter:
O for Originating (outgoing call for a user);
T for Terminating (incoming call for a user);
I for Initiate Call Attempt (initiated from the network).
ETSI
11 ETSI EN 301 933-3 V1.1.1 (2003-01)
The state names and their abbreviations used are:
Null
1_Party 1P
Originating_Set-up OS
Terminating_Set-up TS
Originating_ 1_Party_Setup O1PS
Stable_1_Party S1P
Stable_2_Party S2P
Forward FW
Stable_Multi_Passive_Party (no. of passive legs n) SnPP
Stable_Multi_Party (no. of passive legs n) SnP
The term "null" stands for "none" as in preamble O_NULL_S2P_OH3.
There can be two set of CSs with the same nature of legs present at the same time, as in the preamble name
O_S2P_S1P_S1P.
4.6 Test purpose parametrization and selection
As shown in the "Introduction" clause, the Implementation under Test (IUT) is always an SSF, either connected to an
Assisting SSF, a Handed-off SSF or to an SRF. Not all sub-functions defined for an SSF need to be implemented at the
same time (see e.g. figure 37 in clause 8 of EN 301 931-2 [2]), and possibly not all operations are implemented (e.g. the
use of scripts).
In order to define an appropriate set of TPs for all functions and operations, but to enable deselection of TPs not
applicable to particular IUTs, the following Test Parameters are defined in table 3.
NOTE: It is assumed, that these Test Parameters are mapped to corresponding PIXIT/Test Suite Parameters.
ETSI
12 ETSI EN 301 933-3 V1.1.1 (2003-01)
Table 3: Test Parameters applicable to TP selection
Test Parameter name Type Explanation
CONFIGURATION IA5STRING The allowed values are:
"CONFIGURATION A"
and
"CONFIGURATION B"
SSF_RELAYS_SRF_OPERATIONS BOOLEAN This parameter shall be set to TRUE, if the IUT relays
the user interaction operations (PlayAnnouncement
etc.) between SCF and SRF. Otherwise it shall be set
to FALSE.
SSF_RELAYS_SRF_ASSISTING BOOLEAN This parameter shall be set to TRUE, if the IUT relays
the user interaction operations (PlayAnnouncement
etc.) between SCF and SRF via an Assisting SSF.
Otherwise it shall be set to FALSE.
SSF_IS_INITIATING BOOLEAN This parameter shall be set to TRUE, if the IN SSM
FSM is implemented in the IUT and is used for testing.
Otherwise it shall be set to FALSE.
See figure 37 in clause 8 of EN 301 931-2 [2].
(see note 1)
SSF_IS_ASSISTING BOOLEAN This parameter shall be set to TRUE, if the Assisting
SSM FSM is implemented in the IUT and is used for
testing. Otherwise it shall be set to FALSE.
See figure 37 in clause 8 of EN 301 931-2 [2].
(see note 1)
SSF_IS_HANDED_OFF BOOLEAN This parameter shall be set to TRUE, if the Handed-off
SSM FSM is implemented in the IUT and is used for
testing. Otherwise it shall be set to FALSE.
See figure 37 in clause 8 of EN 301 931-2 [2].
(see note 1)
SSF_IMPLEMENTS_SCRIPTS BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the script operations ScriptRun, ScriptClose
and ScriptInformation. Otherwise it shall be set to
FALSE.
SSF_IMPLEMENTS_SCRIPT_EVENTS BOOLEAN This parameter shall be set to TRUE, if the IUT
implements a script invoking the ScriptEvent operation.
Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_PA BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PlayAnnouncement procedure.
Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_PA_INTERRUPT BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PlayAnnouncement procedure in an
interruptable way, i.e. it can be cancelled with the
Cancel operation. Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_PCU BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PrompAndCollectUserInformation
procedure. Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_PCU_INTERRUPT BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PrompAndCollectUserInformation
procedure in an interruptable way, i.e. it can be
cancelled with the Cancel operation. Otherwise it shall
be set to FALSE.
SSF_IMPLEMENTS_PRM BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PrompAndReceiveMessage procedure.
Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_PRM_INTERRUPT BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the PrompAndReceiveMessage procedure
in an interruptable way, i.e. it can be cancelled with the
Cancel operation. Otherwise it shall be set to FALSE.
SSF_IMPLEMENTS_UTSI BOOLEAN This parameter shall be set to TRUE, if the IUT
implements the RequestReportUTSI, SendSTUI and
ReportUTSI procedure. Otherwise it shall be set to
FALSE.
SSF_TIMER_USED BOOLEAN The SSF timer is used.
ETSI
13 ETSI EN 301 933-3 V1.1.1 (2003-01)
Test Parameter name Type Explanation
SSF_PREDEFINED_SRF BOOLEAN The SSF has associated a predefined SRF being
selected automatically when no Resource IP Address is
specified.
(see note 2).
SSF_ADRESSED_SRF BOOLEAN The SSF can select an SRF by a valid Resource IP
Address.
(see note 2).
ETC_EXPLICIT_CORRELATION BOOLEAN This parameter shall be set to TRUE, if the SSF
expects the correlationID and sCFID parameters to be
explicitly contained in the
EstablishTemporaryConnection argument (and not
implicitly encoded in the
assistingSSPIPRoutingAddress), and FALSE
otherwise.
ETC_TO_ASSIST BOOLEAN This parameter shall be set to TRUE, if the SSF
establishes the Temporary Connection to the SRF via
an Assisting SSF, and FALSE otherwise.
(see note 3).
ETC_TO_SRF BOOLEAN This parameter shall be set to TRUE, if the SSF
establishes the Temporary Connection directly to the
SRF, and FALSE otherwise.
(see note 3).
CO_EXPLICIT_CORRELATION BOOLEAN This parameter shall be set to TRUE, if the SSF
expects the correlationID and sCFID parameters to be
explicitly contained in the Connect argument (and not
implicitly encoded in the destinationRoutingAddress
parameter), and FALSE otherwise.
(see note 4)
CO_TO_HANDED_OFF BOOLEAN This parameter shall be set to TRUE, if the SSF
establishes the Connection to the SRF via a Handed-
OFF SSF, and FALSE otherwise.
(see notes 4 and 5).
CO_TO_SRF BOOLEAN This parameter shall be set to TRUE, if the SSF
establishes the Connection directly to the SRF, and
FALSE otherwise.
(see notes 4 and 5).
NOTE 1: Exactly one of the parameters SSF_IS_INITIATING, SSF_IS_ASSISTING and
SSF_IS_HANDED_OFF shall be set to TRUE (if more than one of the related functions is
implemented, the tests should be repeated with the other applicable settings of this parameter).
NOTE 2: At least one of these Parameters must be set to TRUE.
NOTE 3: At least one of these Parameters must be set to TRUE.
NOTE 4: Connect operation only related to Handed-off SSF.
NOTE 5: At least one of these Parameters must be set to TRUE.

ETSI
14 ETSI EN 301 933-3 V1.1.1 (2003-01)
The following Test Parameters used to parameterize the TP descriptions, when necessary, are defined in table 4.
NOTE: It is assumed, that these Test Parameters are mapped to corresponding PIXIT/Test Suite Parameters.
Table 4: Test Parameters applicable to TP parametrization
Test Parameter name Type Explanation
UI_CTR_RES_ADDR_PA ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_PA (used in TPs for the
PlayAnnouncement operation). In case of an
Initiating SSF the ResourceAddress identifies leg 1
or the CS containing leg 1. Otherwise only the
resourceAddress formats "None" and
"ipRoutingAddress" are applicable.
UI_CTR_RES_ADDR_PA_S2P ResourceAddress Resource address value related to a CS with 2 legs
(see used in the ConnectToResource invoke component
ConnectToResourceArg) issued after preamble PRE_UI_S2P_MON (used in
TPs for the PlayAnnouncement operation).
UI_CTR_RES_ADDR_PR_S1P_1P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_PR_S1P_1P (used in TPs
for the PromptAndCollectUserInformation,
PromptAndReceiveMessage and Script
operations).
The address identifies leg 1 in CS 2.
Only applicable to an Initiating SSF
UI_CTR_RES_ADDR_PR_1P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_PR_1P (used in TPs for
the PromptAndCollectUserInformation,
PromptAndReceiveMessage and Script
operations).
In case of an Initiating SSF the resourceAddress
identifies leg 1 in (initial) CS 1. Otherwise only the
resourceAddress formats "None" and
"ipRoutingAddress" are applicable.
UI_CTR_RES_ADDR_PR_S2P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_PR_S2P (used in TPs for
the PromptAndCollectUserInformation,
PromptAndReceiveMessage and Script
operations).
The address identifies legs 1 and 2 in (initial) CS 1.
Only applicable to an Initiating SSF.
UI_CTR_RES_ADDR_UT_S2P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_UT_S2P (used in TPs for
the RequestReportUTSI and SendSTUI
operations).
The address identifies the CS containing 2 legs.
Only applicable to an Initiating SSF.
UI_CTR_RES_ADDR_UT_1P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_UT_1P (used in TPs for
the RequestReportUTSI and SendSTUI
operations).
In case of an Initiating SSF the resourceAddress
identifies the CS containing 1 leg (the initial leg).
Otherwise only the resourceAddress formats "None"
and "ipRoutingAddress" are applicable.
ETSI
15 ETSI EN 301 933-3 V1.1.1 (2003-01)
Test Parameter name Type Explanation
UI_CTR_RES_ADDR_UT_S1P_1P ResourceAddress Resource address value used in the
(see ConnectToResource invoke component issued in
ConnectToResourceArg) preamble PRE_UI_CTR_UT_S1P_1P (used in TPs
for the RequestReportUTSI and SendSTUI
operations).
The address identifies CS 2 containing leg 1
(controlling).
Only applicable to an Initiating SSF.
UI_PA_CS CallSegmentID ID of Call segment affected by the
PlayAnnouncement operation (according to
preamble PRE_UI_CTR_PA and compatible with
UI_CTR_RES_ADDR_PA).
UI_PA_INV_CONN_PTY ConnectedParty Syntactically valid value for the connectedParty
(see parameter (used in the PlayAnnouncement invoke
PlayAnnouncementArg) component), which is not compatible to the
ResourceAddress value UI_CTR_RES_ADDR_PA.
See first (unnumbered) table in clause 7.3.1.1 of
EN 301 931-3 [3].
SCRIPT_INFO_1 UISCRIPT.&SpecificInfo Contains the necessary information to be sent by
the SCF as uIScriptSpecificInfo in the first
ScriptInformation invoke component of SCRIPT_3
(see table 10).
SCRIPT_INFO_2 UISCRIPT.&SpecificInfo Contains the necessary information to be sent by
the SCF as uIScriptSpecificInfo in the second
ScriptInformation invoke component of SCRIPT_3
(see table 10).
SCRIPT_INFO_3 UISCRIPT.&SpecificInfo Contains the necessary information to be sent by
the SCF as uIScriptSpecificInfo in the first
ScriptInformation invoke component of SCRIPT_4
(see table 10).
SCRIPT_INFO_4 UISCRIPT.&SpecificInfo Contains the necessary information to be sent by
the SCF as uIScriptSpecificInfo in the second
ScriptInformation invoke component of SCRIPT_4
(see table 10).
Table 5 combines the Test Parameter as selection expressions, used in the TP description tables.
Table 5: Selection expressions
Selection expression name Boolean expression
ConfigurationA CONFIGURATION = "CONFIGURATION A"
ConfigurationB CONFIGURATION = "CONFIGURATION B"
RelayMethod SSF_RELAYS_SRF_OPERATIONS = TRUE
NotRelayAssistingMethod SSF_RELAYS_SRF_OPERATIONS AND
NOT SSF_RELAYS_SRF_ASSISTING
DirectMethod SSF_RELAYS_SRF_OPERATIONS = FALSE
Initiating SSF_IS_INITIATING
InitiatingA (CONFIGURATION = "CONFIGURATION A") AND
SSF_IS_INITIATING
Assisting CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_ASSISTING
HandedOff CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_HANDED_OFF
AssistingOrHandedOff Assisting OR HandedOff
InitiatingAndTimeout CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_INITIATING AND SSF_TIMER_USED
AssistingAndTimeout CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_INITIATING AND SSF_TIMER_USED
HandedOffAndTimeout CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_HANDED_OFF AND SSF_TIMER_USED
InitiatingPredefinedSRF CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_INITIATING AND SSF_PREDEFINED_SRF
ETSI
16 ETSI EN 301 933-3 V1.1.1 (2003-01)
Selection expression name Boolean expression
AssistingHandoffPredefinedSRF CONFIGURATION = "CONFIGURATION A" AND
(SSF_IS_ASSISTING OR SSF_IS_HANDED_OFF) AND
SSF_PREDEFINED_SRF
PredefinedSRF AssistingHandoffPredefinedSRF OR InitiatingPredefinedSRF
InitiatingAddressedSRF CONFIGURATION = "CONFIGURATION A" AND
SSF_IS_INITIATING AND SSF_ADDRESSED_SRF
AssistingHandoffAddressedSRF CONFIGURATION = "CONFIGURATION A" AND
(SSF_IS_ASSISTING OR SSF_IS_HANDED_OFF) AND
SSF_ADDRESSED_SRF
AddressedSRF InitiatingAddressedSRF OR AssistingHandoffAddressedSRF
InitiatingBAssist CONFIGURATION = "CONFIGURATION B" AND
SSF_IS_INITIATING AND
ETC_TO_ASSIST
InitiatingBHandedOff CONFIGURATION = "CONFIGURATION B" AND
SSF_IS_INITIATING AND
CO_TO_HANDED_OFF
InitiatingBAssistExplicitCorrelation InitiatingBAs
...