SIST ETS 300 374-3 E2:2005
(Main)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)
- Abstract
To supply PIXIT & TTCN test suite for ETS 300 374-1 & 2.
- Status
- Published
- Publication Date
- 31-Mar-2005
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Apr-2005
- Due Date
- 01-Apr-2005
- Completion Date
- 01-Apr-2005
SIST ETS 300 374-3 E2:2005 is the Slovenian adoption of ETS 300 374-3 Edition 2 from ETSI. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for conformance testing of the Service Switching Function (SSF) and Specialized Resource Function (SRF) in Intelligent Network Capability Set 1 (CS1) Core Intelligent Network Application Protocol (INAP). The document is used to support PIXIT and TTCN test suites for ETS 300 374-1 and ETS 300 374-2.
What does SIST ETS 300 374-3 E2:2005 specify?
SIST ETS 300 374-3 E2:2005 specifies how to structure conformance tests and what each test is meant to prove for SSF and SRF behavior in IN CS1 INAP. In practice, it tells a test lab or implementer which test groups exist, how they are organized by state and event type, and how the test purposes are named and selected.
The scope is limited to the Test Suite Structure and Test Purposes for SSF and SRF conformance testing according to ETS 300 374-1. The document uses ISO/IEC 9646-1 and ISO/IEC 9646-2 as the basis for the test methodology.
Clause 4 defines the test suite structure, clause 5 lists the test purposes, and clause 6 defines compliance for an Abstract Test Suite (ATS). Annex A is informative and gives test purpose coverage.
What are the key requirements of SIST ETS 300 374-3 E2:2005?
Test suite organization and coverage
SIST ETS 300 374-3 E2:2005 organizes tests by interface, behavior category and state. For SSF it uses the interface groups bS, rS, iS and aS, and for SRF it uses cI; the main categories are CA, BV, BI and BO in clause 4.3.
That matters because a conformance plan can be built only for the role actually implemented by the equipment. A basic SSP, a relay SSP, an initiating SSP, an assisting SSP and an IP with direct path to SCP do not all need the same test set.
Clause 4.2 maps Functional Entities to Physical Entities and shows example physical scenarios in figures 1 to 5. In practice, this tells the test team how the abstract SSF/SRF functions fit into real network arrangements such as SCP with a single SSP, direct SCP-IP paths, and assist or hand-off cases.
Test step structure and timer handling
Clause 4.4 defines preambles and postambles for the test steps, and clause 4.5 defines the ATS timers and counters. The ATS timer limits are based on the ETS timers, with the minimum equal to the minimum ETS timer and the maximum set to the maximum ETS timer multiplied by 1.2.
That is important for real testing because the ATS allows tolerance for test-simulator delay. A test case should therefore be judged against the ATS timing rules, not only against the protocol timer values in ETS 300 374-1.
State-based behavior for SSF and SRF
Clause 5 is built around state-specific test purposes. For the SSF, the document covers basic SSF behavior, SSF relay behavior, initiating SSF behavior and assisting SSF behavior across states such as Idle, Waiting For Instructions and Monitoring.
In practice, this means the implementation is not tested only for message syntax. It is tested for the right reaction in the right call-processing state, for example to InitialDP, Connect, Continue, ReleaseCall, RequestReportBCSMEvent, ApplyCharging, CallInformationRequest, SendChargingInformation and ResetTimer.
For the SRF-related part, the document covers Intelligent Peripheral behavior in the SRSM-FSM states Idle, Connected and User Interaction. The test purposes check actions such as PlayAnnouncement, PromptAndCollectUserInformation and Cancel.
That matters because the IP must handle announcement and digit-collection procedures correctly while the call or interaction is in progress.
Event reporting and charging-related procedures
The Monitoring state test purposes in clause 5 cover event-driven reporting such as EventReportBCSM, EventNotificationCharging, CallInformationReport and ApplyChargingReport. They also cover cases where events are armed as EDP-N or EDP-R and where the dialogue continues or ends.
This is the part that matters when the network uses INAP to supervise a call, collect information, or trigger charging actions. A test campaign can verify that the implementation reports the correct event, with the correct call-leg context and supporting information, when the trigger occurs.
Non-call-associated treatment and filtering
Clause 5 also includes SSME-FSM behavior for non-call-associated procedures. The key operations are ActivateServiceFiltering and CallGap, followed by ServiceFilteringResponse when the filtering duration ends.
In practice, this is how the standard checks that a system can handle service filtering and call gapping without a live call setup. That is important for operator-controlled filtering and for validating service-level behavior outside normal call processing.
Valid, invalid and inopportune behavior
Clause 5 separates test purposes into Valid Behaviour, Invalid Behaviour and Inopportune Behaviour groups. Valid tests confirm that an allowed operation is accepted; invalid tests check rejection of malformed or incomplete operations; inopportune tests check that an operation is rejected or a dialogue is ended when it is not allowed in the current state.
This matters because conformance testing is not only about accepting correct messages. It also checks that the implementation refuses the wrong message, the wrong sequence, or the wrong operation in the wrong state.
Compliance and test selection
Clause 6 states that a compliant ATS shall contain a set of test cases corresponding to the test purposes in clause 5, use a suitable subset of the structure in clause 4, keep the same naming conventions, preserve the link to the PICS proforma in ETS 300 374-2, and comply with ISO/IEC 9646-2.
In practice, a lab or vendor uses the PICS proforma to deselect non-applicable cases and keeps only the relevant test purposes for the implementation under test. Annex A gives the TP coverage figures that help estimate test volume.
What terms does SIST ETS 300 374-3 E2:2005 define?
- Abstract Test Suite (ATS) - the set of abstract test cases used for conformance testing before any concrete test equipment or implementation details are added.
- Implementation Under Test (IUT) - the implementation whose behavior is being checked against the test purposes.
- System Under Test (SUT) - the overall system or equipment arrangement being tested.
- Protocol Implementation Conformance Statement (PICS) - the proforma used to state which protocol features and options an implementation supports.
- Service Switching Function (SSF) - the network function whose call control behavior is exercised by the SSF test groups.
- Specialized Resource Function (SRF) - the resource function tested through the SRF-related and IP-related test purposes.
- Intelligent Peripheral (IP) - the function tested for announcement and user-interaction behavior in the SRSM-FSM.
- Test Purpose (TP) - a stated objective for one test case or group of cases.
Who uses SIST ETS 300 374-3 E2:2005?
SIST ETS 300 374-3 E2:2005 is used by INAP implementers, conformance test laboratories, and telecom quality teams working on SSF, SRF and IP functions. It is also relevant to network operators and buyers who need to specify acceptance tests for IN CS1 equipment.
In practice, these users apply it to design ATS or TTCN test cases, select cases from a PICS proforma, verify state-dependent call control behavior, and check event reporting, charging and user-interaction procedures.
What changed in SIST ETS 300 374-3 E2:2005 from the previous edition?
SIST ETS 300 374-3 E2:2005 is the second edition of ETS 300 374-3. The document history records a first edition in February 1996 and this second edition in December 1997.
Which standards are used with SIST ETS 300 374-3 E2:2005?
- ETS 300 374-1 - provides the protocol specification that the TSS&TP refers to for SSF and SRF conformance testing.
- ETS 300 374-2 - provides the Protocol Implementation Conformance Statement (PICS) proforma used to select and deselect test cases.
- ISO/IEC 9646-1 - provides the general conformance testing concepts and framework used as the basis for the methodology.
- ISO/IEC 9646-2 - provides the abstract test suite specification rules that the compliance clause requires.
What does the SIST ETS 300 374-3 E2:2005 document contain?
- Clause 4 contains the test suite structure, including interface groups, main test groups, physical scenarios, preambles, postambles and ATS timer rules.
- Figures 1 to 5 show example physical scenarios for SSF and SRF arrangements, including SCP with a single SSP, direct SCP-IP paths and assist or hand-off cases.
- Clause 5 contains the test purposes, grouped by SSF, SRF and IP behavior, and by state, event, operation or error path.
- Clause 5 also contains the TP naming convention, which encodes the interface, category, state, group and sequence number.
- Clause 6 contains the compliance rules for building an ATS from the listed test purposes and for linking test selection to the PICS proforma.
- Annex A contains a TP coverage table that summarizes how many test purposes belong to each test group.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 374-3 E2:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)". This standard covers: To supply PIXIT & TTCN test suite for ETS 300 374-1 & 2.
To supply PIXIT & TTCN test suite for ETS 300 374-1 & 2.
SIST ETS 300 374-3 E2:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 374-3 E2:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2005
Inteligentno omrežje (IN) - Nabor zmožnosti 1 (CS1) inteligentnega omrežja - Jedrni
aplikacijski protokol inteligentnega omrežja (INAP) - 3. del: Specifikacija zgradbe
preskušalnega niza in nameni preskušanja (TSS&TP) za funkcijo komutacije
storitev (SSF) in funkcijo posebnih virov (SRF)
Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent
Network Application Protocol (INAP); Part 3: Test Suite Structure and Test Purposes
(TSS&TP) specification for Service Switching Function (SSF) and Specialized Resource
Function (SRF)
Ta slovenski standard je istoveten z: ETS 300 374-3 Edition 2
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 ETS 300 374-3
TELECOMMUNICATION December 1997
STANDARD Second Edition
Source: SPS Reference: RE/SPS-03058
ICS: 33.020
Key words: IN, CS1, INAP, TSS&TP, testing
Intelligent Network (IN);
Intelligent Network Capability Set 1 (CS1);
Core Intelligent Network Application Protocol (INAP);
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for Service Switching Function (SSF) and
Specialized Resource Function (SRF)
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: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1997. All rights reserved.
Page 2
ETS 300 374-3: December 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
ETS 300 374-3: December 1997
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .9
3.1 Definitions .9
3.2 Abbreviations .10
4 Test Suite Structure (TSS) .11
4.1 Overview .11
4.2 Physical scenarios .13
4.3 Test groups.16
4.3.1 Interface groups .16
4.3.1.1 Basic SSF - bS .16
4.3.1.2 SSF relay - rS .16
4.3.1.3 Initiating SSF - iS .16
4.3.1.4 Assisting SSF - aS.17
4.3.1.5 IP with direct path to SCP - cI.17
4.3.2 Main test groups.17
4.3.2.1 Capability tests (CA) .17
4.3.2.2 Valid Behaviour tests (BV).17
4.3.2.3 Invalid Behaviour tests (BI).17
4.3.2.4 Inopportune Behaviour tests (BO) .17
4.4 Test step structure.17
4.4.1 Preambles .17
4.4.2 Postambles.17
4.5 Timers of the Abstract Test Suite (ATS).18
5 Test Purposes (TP).20
5.1 Introduction .20
5.1.1 Test purpose naming convention .20
5.1.2 Source of test purpose definition.21
5.1.3 Initial state .21
5.1.4 Untested procedures.21
5.2 Service Switching Point (SSP).21
5.2.1 Basic SSF - bS .21
5.2.1.1 Capability tests (CA) .21
5.2.1.1.1 SSF-FSM state "Idle".21
5.2.1.1.2 SSF-FSM state "Waiting For
Instructions" .22
5.2.1.1.3 SSF-FSM state "Monitoring".22
5.2.1.1.4 SSME-FSM state "Idle".22
5.2.1.2 Valid Behaviour tests (BV).23
5.2.1.2.1 SSF-FSM state "Idle".23
5.2.1.2.2 SSF-FSM state "Waiting For
Instructions" .27
5.2.1.2.3 SSF-FSM state "Monitoring".37
5.2.1.2.4 SSME-FSM state "Idle".48
5.2.1.2.5 SSME-FSM state "Non Call
Associated Treatment" .49
5.2.1.3 Invalid Behaviour tests (BI).50
5.2.1.3.1 SSF-FSM state "Idle".50
5.2.1.3.2 SSF-FSM state "Waiting For
Instructions" .51
5.2.1.3.3 SSF-FSM state "Monitoring".52
Page 4
ETS 300 374-3: December 1997
5.2.1.3.4 SSME-FSM state "Idle" . 53
5.2.1.4 Inopportune Behaviour tests (BO) . 53
5.2.1.4.1 SSF-FSM state "Idle" . 53
5.2.1.4.2 SSF-FSM state "Waiting For
Instructions". 54
5.2.1.4.3 SSF-FSM state "Monitoring" . 55
5.2.2 SSF relay - rS . 56
5.2.2.1 Valid Behaviour tests (BV) . 56
5.2.2.1.1 SSF-FSM state "Waiting For
Instructions". 56
5.2.2.1.2 SSF-FSM state "Waiting For End Of
User Interaction". 57
5.2.2.2 Invalid Behaviour tests (BI) . 62
5.2.2.2.1 SSF-FSM state "Waiting For
Instructions". 62
5.2.2.2.2 SSF-FSM state "Waiting For End Of
User Interaction". 63
5.2.2.3 Inopportune Behaviour tests (BO) . 63
5.2.2.3.1 SSF-FSM state "Idle" . 63
5.2.2.3.2 SSF-FSM state "Waiting For
Instructions". 64
5.2.2.3.3 SSF-FSM state "Waiting for End of
User Interaction". 64
5.2.2.3.4 SSF-FSM state "Monitoring" . 65
5.2.3 Initiating SSF - iS . 65
5.2.3.1 Valid Behaviour tests (BV) . 65
5.2.3.1.1 SSF-FSM state "Waiting For
Instructions". 65
5.2.3.1.2 SSF-FSM state "Waiting For End Of
Temporary Connection" . 67
5.2.3.2 Invalid Behaviour tests (BI) . 68
5.2.3.2.1 SSF-FSM state "Waiting For
Instructions". 68
5.2.3.2.2 SSF-FSM state "Waiting For End Of
Temporary Connection" . 68
5.2.3.3 Inopportune Behaviour tests (BO) . 68
5.2.3.3.1 SSF-FSM state "Idle" . 68
5.2.3.3.2 SSF-FSM state "Waiting For
Instructions". 69
5.2.3.3.3 SSF-FSM state "Waiting for End of
Temporary Connection" . 70
5.2.3.3.4 SSF-FSM state "Monitoring" . 70
5.2.4 Assisting SSF - aS. 71
5.2.4.1 Valid Behaviour tests (BV) . 71
5.2.4.1.1 SSF-FSM state "Idle" . 71
5.2.4.1.2 SSF-FSM state "Waiting For
Instructions". 72
5.2.4.1.3 SSF-FSM state "Waiting For End Of
User Interaction". 74
5.2.4.2 Invalid Behaviour tests (BI) . 76
5.2.4.2.1 SSF-FSM state "Waiting For
Instructions". 76
5.2.4.2.2 SSF-FSM state "Waiting for End of
User Interaction". 76
5.2.4.3 Inopportune Behaviour tests (BO) . 77
5.2.4.3.1 SSF-FSM state "Waiting For
Instructions". 77
5.3 Intelligent Peripheral (IP). 78
5.3.1 Valid Behaviour tests (BV). 78
5.3.1.1 SRSM-FSM state "Idle". 78
5.3.1.2 SRSM-FSM state "Connected" . 78
5.3.1.2.1 Network events . 78
5.3.1.2.2 Operations. 79
Page 5
ETS 300 374-3: December 1997
5.3.1.2.3 Operation errors.83
5.3.1.3 SRSM-FSM state "User Interaction".84
5.3.1.3.1 Network events .84
5.3.1.3.2 Operations .84
5.3.2 Invalid Behaviour tests (BI) .85
5.3.2.1 SRSM-FSM state "Connected".85
5.3.2.2 SRSM-FSM state "User Interaction".85
5.3.3 Inopportune Behaviour tests (BO).86
5.3.3.1 SRSM-FSM state "Idle" .86
5.3.3.2 SRSM-FSM state "Connected".86
6 Compliance .86
Annex A (informative): TP coverage .87
History.88
Page 6
ETS 300 374-3: December 1997
Blank page
Page 7
ETS 300 374-3: December 1997
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the Signalling
Protocols and Switching (SPS) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
This ETS is part 3 of a multi-part standard covering the Capability Set 1 (CS1) core Intelligent Network
Protocol (INAP) as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching
Function (SSF) and Specialized Resource Function (SRF)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for SSF and SRF";
Part 5: "Protocol specification for the Service Control Function (SCF) - Service Data Function (SDF)
interface";
Part 6: "PICS proforma specification for the SCF-SDF interface".
Transposition dates
Date of adoption: 5 December 1997
Date of latest announcement of this ETS (doa): 31 March 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 1998
Date of withdrawal of any conflicting National Standard (dow): 30 September 1998
Page 8
ETS 300 374-3: December 1997
Blank page
Page 9
ETS 300 374-3: December 1997
1 Scope
This third part of ETS 300 374 provides the Test Suite Structure and Test Purposes (TSS&TP) for
conformance testing of the Service Switching Function (SSF) and the Specialized Resource Function
(SRF) of the core Intelligent Network Application Protocol (INAP) of Intelligent Network (IN) Capability
Set 1 (CS1) according to ETS 300 374-1 [1].
ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4] are used as the basis for the test methodology.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 374-1 (1994): "Intelligent Network (IN); Intelligent Network Capability
Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1:
Protocol specification".
[2] ETS 300 374-2 (1996): "Intelligent Network (IN); Intelligent Network Capability
Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 2:
Protocol Implementation Conformance Statement (PICS) proforma specification
for Service Switching Function (SSF), Specialized Resource Function (SRF) and
Service Control Function (SCF)".
[3] ISO/IEC 9646-1: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[4] ISO/IEC 9646-2: "Information technology - Open systems interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 374-1 [1];
- terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-2 [4].
In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:
- Abstract Test Suite (ATS);
- Implementation Under Test (IUT);
- System Under Test (SUT);
- Protocol Implementation Conformance Statement (PICS).
Page 10
ETS 300 374-3: December 1997
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
aS assisting SSF
aSSP assisting SSP
ATS Abstract Test Suite
BI Invalid Behaviour tests
BO Inopportune Behaviour tests
bS tests for SSP basic functions
BV Valid Behaviour tests
CA Capability tests
cI IP with direct path to SCP
EDP-N Event Detection Point - Notification
EDP-R Event Detection Point - Request
FE Functional Entity
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
PICS Protocol Implementation Conformance Statement
PDU Protocol Data Unit
rS SSF relay
SCF Service Control Function
SCP Service Control Point
SDF Service Data Function
SDP Service Data Point
SRF Specialized Resource Function
SRSM SRF call State Model
SSF Service Switching Function
SSME SSF Management Entity
SSP Service Switching Point
SUT System Under Test
TCAP Transaction Capabilities Application Part
TDP Trigger Detection Point
TP Test Purpose
TSS Test Suite Structure
Page 11
ETS 300 374-3: December 1997
4 Test Suite Structure (TSS)
4.1 Overview
Tables 1 and 2 show the structure of the test suites for SSF and SRF.
Table 1: Test suite structure of the SSF tests
SUT Interface Category State Group
SSP SCF-SSF CA State 1 Network event
bS: SSP basic functions
Operation
State 3 Operation
State 6 Network event
State 7 Operation
BV State 1 Network event
Operation
State 3 Network event
Operation
Operation error
State 6 Network event
Operation
Operation error
State 7 Operation
State 8 Network event
BI State 1 Operation
State 3 Operation
Operation error
State 6 Operation
State 7 Operation
BO State 1 Operation
State 3 Operation
State 6 Operation
SCF-SSF-SRF BV State 3 Operation
rS: add. for SSP with
State 4 Network event
relay functions
Operation
Operation error
BI State 3 Operation
State 4 Operation
BO State 1 Operation
State 3 Operation
State 4 Operation
State 6 Operation
(continued)
Page 12
ETS 300 374-3: December 1997
Table 1 (concluded): Test suite structure of the SSF tests
SUT Interface Category State Group
SSP SCF-SSF BV State 3 Operation
iS: add. for SSP acting
State 5 Network event
as initiating SSP
Operation
Operation error
BI State 3 Operation
State 5 Operation
BO State 1 Operation
State 3 Operation
State 5 Operation
State 6 Operation
SCF-SSF BV Network event
State 1
aS: add. for SSP acting
State 3 Network event
as assisting SSP
Operation
Operation error
State 4 Network event
Operation
Operation error
BI State 3 Operation
State 4 Operation
BO State 3 Operation
State 4 Operation
Table 2: Test suite structure of the SRF tests
SUT Interface Category State Group
IP SCF-SRF BV State 1 Network event
cI (IP direct path to SCP)
State 2
Network event
Operation
Operation error
State 3 Network event
Operation
BI State 2 Operation
State 3 Operation
BO State 1 Operation
State 2 Operation
Page 13
ETS 300 374-3: December 1997
4.2 Physical scenarios
The test suites given in subclause 4.1 are based on the mapping of Functional Entities (FE) to Physical
Entities (PE) as shown in table 3.
Table 3: Mapping of functional entities to physical entities
FE
PE SRF SSF SCF SDF
SSP o m n/a n/a
SCP n/a n/a m o
n/a n/a n/a m
SDP
IP m n/a n/a n/a
The application of the test suites according to subclause 4.1 is given in figures 1 to 5 for a number of
different example physical scenarios.
The following figures illustrate mainly the SRF configurations. The SDP is included for better
understanding of the whole IN configuration. Nevertheless, it possible to support an SCP with an
integrated SDF.
SCP
SDF
SCF
Non-integrated SRF
Integrated SRF
SSP
IP
SSF
CCF
SRF
applied test suite groups for SSP testing: bS + rS
Figure 1: Example for SCP with single SSP Non-integrated or Integrated SRF
Page 14
ETS 300 374-3: December 1997
SCP
SDF
SCF
SSP
IP
SSF
CCF
SRF
applied test suite groups for iSSP testing: bS + iS
applied test suite groups for IP testing: cI
Figure 2: Example for direct path SCP - IP
SCP
SDF
SCF
Non-integrated SRF
Integrated SRF
initiating SSP assisting SSP
IP
SSF
SSF
CCF SRF
CCF
applied test suite groups for iSSP testing: bS + iS
applied test suite groups for aSSP testing: aS + rS
Figure 3: Example for SSP Assist/Hand-off (assisting SSP with relay)
Page 15
ETS 300 374-3: December 1997
SCP
SDF
SCF
Non-integrated SRF
Integrated SRF
initiating SSP
IP
IP
SSF
CCF
SRF SRF
applied test suite groups for iSSP testing: bS + iS + rS
applied test suite groups for IP testing: cI
Figure 4: Example for SSP Assist/Hand-off (initiating SSP with relay)
SCP
SDF
SCF
Non-integrated SRF
Non-integrated SRF
Integrated SRF
Integrated SRF
assisting SSP
initiating SSP
IP IP
SSF
SSF
CCF SRF
SRF CCF
applied test suite groups for iSSP testing: bS + iS + rS
applied test suite groups for aSSP testing: aS + rS
Figure 5: Example for SSP Assist/Hand-off (initiating and assisting SSP with relay)
Page 16
ETS 300 374-3: December 1997
4.3 Test groups
4.3.1 Interface groups
4.3.1.1 Basic SSF - bS
The defined test purposes cover the INAP procedures at the SSP for the basic functions as described in
ETS 300 374-1 [1], clauses 7 to 10. The basic functions are the INAP procedures at the SSP for the
following operations:
ActivateServiceFiltering
ActivityTest
ApplyCharging
ApplyChargingReport
CallInformationRequest
CallInformationReport
Cancel (CCF events)
CollectInformation
Connect
Continue
EventNotificationCharging
EventReportBCSM
FurnishChargingInformation
InitialDP
InitiateCallAttempt
ReleaseCall
RequestNotificationChargingEvent
RequestReportBCSMEvent
ResetTimer
SendChargingInformation
ServiceFilteringResponse
4.3.1.2 SSF relay - rS
The defined test purposes cover the INAP procedures at the SSP needed in addition to the basic
functions for the user interaction with relay as described in ETS 300 374-1 [1], clauses 7 to 10. These are
the procedures for the following operations:
Cancel (PA, PC)
ConnectToResource
DisconnectForwardConnection
PlayAnnouncement
PromptAndCollectUserInformation
SpecializedResourceReport
4.3.1.3 Initiating SSF - iS
The defined test purposes cover the INAP procedures at the initiating SSP needed in addition to the basic
functions as described in ETS 300 374-1 [1], clauses 7 to 10. These are the procedures for the following
operations:
Connect (hand-off)
DisconnectForwardConnection
EstablishTemporaryConnection
Page 17
ETS 300 374-3: December 1997
4.3.1.4 Assisting SSF - aS
The defined test purposes cover the INAP procedures at the assisting SSP needed in addition to the basic
and relay functions as described in ETS 300 374-1 [1], clauses 7 to 10. These are the procedures for the
following operations:
AssistRequestInstructions
4.3.1.5 IP with direct path to SCP - cI
The defined test purposes cover the INAP procedures at the IP related to the SRF-SCF interface in case
of a direct path between SCP and IP as described in ETS 300 374-1 [1], clauses 7 to 10. These are the
procedures for the following operations:
AssistRequestInstructions
Cancel
PlayAnnouncement
PromptAndCollectUserInformation
SpecializedResourceReport
4.3.2 Main test groups
4.3.2.1 Capability tests (CA)
Capability testing provides a limited testing to ascertain the capabilities stated in the PICS can be
observed.
4.3.2.2 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.
4.3.2.3 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.
4.3.2.4 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).
4.4 Test step structure
4.4.1 Preambles
The preamble test group contains the preamble test steps needed for initialization of the IUT before
testing the particular test purpose. Each preamble shall start from the IUT initial state as defined in
subclause 5.1.4.
4.4.2 Postambles
After each test case the IUT shall be brought back to the initial state as defined in subclause 5.1.4.
Page 18
ETS 300 374-3: December 1997
4.5 Timers of the Abstract Test Suite (ATS)
This subclause describes the timers and counters used in the ATS. The "min" and "max" indications
define if the timer value represents the minimum or maximum limit of a timer. The timer values contain
some additional tolerances for delays caused by test simulators. Therefore, a bigger timer tolerance is
given than defined in ETS 300 374-1 [1]:
Minimum value of ATS timer = minimum ETS timer;
Maximum value of ATS timer = maximum ETS timer × 1,2.
Table 4 shows the identified timers used in the ATS and the references to ETS 300 374-1 [1].
Table 4: ATS timer values
ATS timer name ATS timer value ETS timer name Reference to
[s] ETS 300 374-1 [1]
T (see note) T not defined
SSFmin SSF
T (see note)
SSFmax
T (see note) T not defined
SRFmin SRF
T (see note)
SRFmax
T (see note) T not defined
SCF-SSFmin SCF-SSF
T (see note)
SCF-SSFmax
T (see note) T not defined
ActTestmin ActTest
T (see note)
ActTestmax
T (see note) T not defined
ASSIST/HAND-OFFmin ASSIST/HAND-OFF
T (see note)
ASSIST/HAND-OFFmax
T 1T 6.1
asfmin asf
T 12
asfmax
T 1T 6.1
atmin at
T 12
atmax
T 1T 6.1
acmin ac
T 12
acmax
T 1T 6.1
acrmin acr
T 12
acrmax
T 1T 6.1
arimin ari
T 12
arimax
T 1T 6.1
cgmin cg
T 12
cgmax
T 1T 6.1
cirpmin cirp
T 12
cirpmax
T 1T 6.1
cirqmin cirq
T 12
cirqmax
T 1T 6.1
canmin can
T 12
canmax
T 1T 6.1
cimin ci
T 72
cimax
(continued)
Page 19
ETS 300 374-3: December 1997
Table 4 (concluded): ATS timer values
ATS timer name ATS timer value ETS timer name Reference to
[s] ETS 300 374-1 [1]
T 1T 6.1
conmin con
T 12
conmax
T 1T 6.1
ctrmin ctr
T 12
ctrmax
T 1T 6.1
cuemin cue
T 12
cuemax
T 1T 6.1
dfcmin dfc
T 12
dfcmax
T 1T 6.1
etcmin etc
T 72
etcmax
T 1T 6.1
encmin enc
T 12
encmax
T 1T 6.1
erbmin erb
T 12
erbmax
T 1T 6.1
fcimin fci
T 12
fcimax
T 1T 6.1
idpmin idp
T 12
idpmax
T 1T 6.1
icamin ica
T 12
icamax
T 1T 6.1
rcmin rc
T 12
rcmax
T 1T 6.1
rncmin rnc
T 12
rncmax
T 1T 6.1
rrbmin rrb
T 12
rrbmax
T 1T 6.1
rtmin rt
T 12
rtmax
T 1T 6.1
scimin sci
T 12
scimax
T 1T 6.1
sfrmin sfr
T 12
sfrmax
T 1T 6.1
pamin pa
T 1 800
pamax
T 1T 6.1
pcmin pc
T 1 800
pcmax
T 1T 6.1
srrmin srr
T 12
srrmax
NOTE: The value of this timer is given in ETS 300 374-2 [2].
Page 20
ETS 300 374-3: December 1997
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
At the start of each test sub group the preambles and the postambles are listed.
5.1.1 Test purpose naming convention
The identifier of the TP is built according to the scheme in table 5.
Table 5: TP identifier naming convention scheme
Identifier: IN
= interface: (1) SCP: Basic SCF (bC) (not used)
(2) SCP: SCF-SSF relay handling (rC) (not used)
(3) SCP: SCF Assist with relay handling (aC) (not used)
(4) SCP: SCF direct path IP handling (pC) (not used)
(5) SCP: SCF-SDF handling (dC) (not used)
6 SSP: Basic SSF (bS)
7 SSP: SSF relay (rS)
8 SSP: Initiating SSF (iS)
9 SSP: Assisting SSF (aS)
A IP: SCF-SRF direct path to SCP (cI)
(B) SDP: SCF-SDF direct path to SCP (cD) (not used)
= category: 1 BIT, Basic Interconnection tests (not used)
2 CA, Capability tests
3 BV, Valid Behaviour tests
4 BI, Invalid Behaviour tests
5 BO, Inopportune Behaviour tests = state: 0 not relevant
1 State 1 / State a in case of SSF
2 State 2 / State b in case of SSF
3 State 3 / State c in case of SSF
4 State 4 / State d in case of SSF
5 State 5 / State e in case of SSF
6 State 6 / State f in case of SSF
7 State 7 / State ma in case of SSF
8 State 8 / State mb in case of SSF
= group: 0 Network event
1 Operation
2 Return result
3 Operation error
= sequential number: (01-99)
Page 21
ETS 300 374-3: December 1997
5.1.2 Source of test purpose definition
The test purposes are based on ETS 300 374-1 [1]. In each test purpose, a reference to the relevant
subclauses of ETS 300 374-1 [1] is made below the test purpose name.
5.1.3 Initial state
The initial state for all SUTs (SSP, IP) shall be "Idle" for all test purposes.
5.1.4 Untested procedures
Application Context Name negotiation is not tested. Tests on Application Context Name negotiation shall
be part of test purposes and associated ATS for Transaction Capabilities Application Part (TCAP) testing.
5.2 Service Switching Point (SSP)
5.2.1 Basic SSF - bS
The test group objective is to test the INAP procedures at the SSP for basic functions.
5.2.1.1 Capability tests (CA)
The test group objective is to test the SSP general capability of interconnecting with the partner entity.
5.2.1.1.1 SSF-FSM state "Idle"
The test group objective is to check the capability of the IUT of establishing a relation between the SCP
and SSP initiated by the SSP or by the SCP.
5.2.1.1.1.1 Network events
Preamble: -
Postamble: ReleaseCall invoke and terminate the dialogue.
IN621001 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
initiates a dialogue and sends an InitialDP invoke containing all mandatory
7.1.5.1,
9.19 parameters and all parameters related to the called party, with at least the
parameters:
- serviceKey,
- calledPartyNumber.
5.2.1.1.1.2 Operations
Preamble: -
Postamble: ReleaseCall invoke and terminate the dialogue.
IN621101 To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttempt
invoke containing mandatory parameters only, with:
7.1.5.1, - destinationRoutingAddress,
9.20 followed by a RequestReportBCSMEvent invoke with:
- bcsmEvents including at least:
- eventTypeBCSM (routeSelectFailure),
- eventTypeBCSM (oCalledPartyBusy),
- eventTypeBCSM (oNoAnswer),
- eventTypeBCSM (oAnswer),
- monitorMode being interrupted,
and a Continue invoke,
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
Page 22
ETS 300 374-3: December 1997
5.2.1.1.2 SSF-FSM state "Waiting For Instructions"
The test group objective is to check the capability of the IUT to handle Connect operations on a detected
IN call.
Preamble: Trigger detected. InitialDP invoke has been sent.
Postamble: Terminate the dialogue.
IN623101 To ensure that the IUT being in the "Waiting For Instructions" state, receiving a
Connect invoke containing mandatory parameters only, with:
7.1.5.3, - destinationRoutingAddress,
9.11
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
5.2.1.1.3 SSF-FSM state "Monitoring"
The test group objective is to check the capability of the IUT to handle detection point related instructions
sent by the SCP.
Preamble: Originating trigger detected. InitialDP invoke has been sent. EDP-R armed on
oAnswer, Connect invoke received.
Postamble: ReleaseCall invoke and terminate the dialogue.
IN626001 To ensure that the IUT being in the "Monitoring" state, at detection of an EDP-R on
oAnswer,
7.1.5.6,
sends an EventReportBCSM invoke, containing all mandatory parameters, with
9.17
at least the parameter:
- eventTypeBCSM (oAnswer).
5.2.1.1.4 SSME-FSM state "Idle"
The test group objective is to check the capability of the IUT to handle non call associated operation sent
by the SCP.
Preamble: -
Postamble: ActivateServiceFiltering invoke with filteringTimeOut being duration with
value = 0.
IN627101
To ensure that the IUT being in the "Idle" state, receiving an ActivateServiceFiltering
invoke containing mandatory parameters only, with:
7.1.1.4, - filteredCallTreatment including sFBillingChargingCharacteristics only,
9.1 - filteringCharacteristics being interval,
- filteringTimeOut being duration,
- filteringCriteria being serviceKey,
sends ActivateServiceFiltering result and terminates the dialogue by means of
basic end.
Preamble: -
Postamble: CallGap invoke with gapIndicators including duration (0).
IN627102 To ensure that the IUT being in the "Idle" state, receiving a CallGap invoke containing
mandatory parameters only, with:
7.1.1.4, - gapCriteria being gapOnService,
9.6 - gapIndicators
does not return any error, reject the invoke or abort the dialogue within the
operation timeout and terminates the dialogue by means of prearranged end.
Page 23
ETS 300 374-3: December 1997
5.2.1.2 Valid Behaviour tests (BV)
The test group objective is to test the SSP capability of reacting correctly on network events and of
accepting and if appropriate responding to PDUs (operations, operation errors) that are syntactically and
semantically valid.
5.2.1.2.1 SSF-FSM state "Idle"
The test group objective is to check that a valid operation InitialDP is sent to the SCP and a valid
InitiateCallAttempt operation is accepted in the SSF-FSM state "Idle".
5.2.1.2.1.1 Network events
Preamble: -
Postamble: ReleaseCall invoke and terminate the dialogue.
IN631001 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
initiates a dialogue and sends an InitialDP invoke containing all mandatory
7.1.5.1,
9.19 parameters and all parameters related to the called party, with at least the
parameters:
- serviceKey,
- calledPartyNumber.
IN631002 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to the calling party, with at least the
parameters:
- serviceKey,
- callingPartyNumber.
IN631003 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
parameters and all parameters related to the calling party, with at least the
9.19
parameters:
- serviceKey,
- callingPartysCategory.
IN631004 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to location information, with at least the
parameters:
- serviceKey,
- locationNumber.
IN631005 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to supplementary services, with at least
the parameters:
- serviceKey,
- originalCalledPartyID.
Page 24
ETS 300 374-3: December 1997
IN631006 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to supplementary services, with at least
the parameters:
- serviceKey,
- forwardCallIndicators.
IN631007 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
initiates a dialogue and sends an InitialDP invoke containing all mandatory
7.1.5.1,
9.19 parameters and all parameters related to supplementary services, with at least
the parameters:
- serviceKey,
- redirectingPartyID.
IN631008 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to supplementary services, with at least
the parameters:
- serviceKey,
- redirectionInformation.
IN631009 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to the type of connection and teleservice,
with at least the parameters:
- serviceKey,
- highLayerCompatibility,
- bearerCapability being bearerCap.
IN631010 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and all parameters related to additional information, with at least the
parameters:
- serviceKey,
- additionalCallingPartyNumber.
IN631011 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and indicating the TDP, with at least the parameters:
- serviceKey,
- eventTypeBCSM.
IN631012 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and the network operator specific parameter indicating SRF
capabilities, with at least the parameters:
- serviceKey,
- iPSSPCapabilities.
Page 25
ETS 300 374-3: December 1997
IN631013 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and the network operator specific parameter indicating IP
availability, with at least the parameters:
- serviceKey,
- iPAvailable.
IN631014 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
initiates a dialogue and sends an InitialDP invoke containing all mandatory
7.1.5.1,
9.19 parameters and network operator specific extensions, with at least the
parameters:
- serviceKey,
- extensions.
IN631015 To ensure that the IUT being in the "Idle" state, at detection of a TDP,
7.1.5.1, initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19 parameters and the network operator specific parameter indicating service
interaction, with at least the parameters:
- serviceKey,
- serviceInteractionIndicators.
Preamble: Call Gap invoke sent.
Postamble: ReleaseCall invoke and terminate the dialogue.
IN631016 To ensure that the IUT being in the "Idle" state, at detection of a TDP which matches
the Call Gap Criteria,
7.1.5.1,
initiates a dialogue and sends an InitialDP invoke containing all mandatory
9.19
parameters and indicating call gapping encountered, with at least the
parameters:
- serviceKey,
- cGEncountered.
5.2.1.2.1.2 Operations
Preamble: -
Postamble: ReleaseCall invoke and terminate the dialogue.
IN631101 To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttempt
invoke containing mandatory parameters only, with:
7.1.5.1, - destinationRoutingAddress,
9.20 followed by a RequestReportBCSMEvent invoke with:
- bCSMEvent being at least
- eventTypeBCSM (routeSelectFailure),
- eventTypeBCSM (oCalledPartyBusy),
- eventTypeBCSM (oNoAnswer),
- eventTypeBCSM (oAnswer),
- monitorMode being interrupted,
and a Continue invoke
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
Page 26
ETS 300 374-3: December 1997
IN631102 To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttempt
invoke containing mandatory and optional parameters, with:
7.1.5.1, - destinationRoutingAddress,
9.20 - alertingPattern,
- callingPartyNumber,
followed by a RequestReportBCSMEvent invoke with:
- bCSMEvent being at least
- eventTypeBCSM (routeSelectFailure),
- eventTypeBCSM (oCalledPartyBusy),
- eventTypeBCSM (oNoAnswer),
- eventTypeBCSM (oAnswer),
- monitorMode being interrupted,
and a Continue invoke
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
IN631103 To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttempt
invoke containing network operator specific extensions, with:
7.1.5.1, - destinationRoutingAddress,
- extensions,
9.20
followed by a RequestReportBCSMEvent invoke with:
- bCSMEvent being at least
- eventTypeBCSM (routeSelectFailure),
- eventTypeBCSM (oCalledPartyBusy),
- eventTypeBCSM (oNoAnswer),
- eventTypeBCSM (oAnswer),
- monitorMode being interrupted,
and a Continue invoke
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
IN631104 To ensure that the IUT being in the "Idle" state, receiving an InitiateCallAttempt
invoke containing the network operator specific parameter indicating service
7.1.5.1, interaction, with:
9.20 - destinationRoutingAddress,
- serviceInteractionIndicators,
followed by a RequestReportBCSMEvent invoke with:
- bCSMEvent being at least
- eventTypeBCSM (routeSelectFailure),
- eventTypeBCSM (oCalledPartyBusy),
- eventTypeBCSM (oNoAnswer),
- eventTypeBCSM (oAnswer),
- monitorMode being interrupted,
and a Continue invoke
does not return any error, reject the invoke or abort the dialogue within the
operation time out.
Page 27
ETS 300 374-3: December 1997
5.2.1.2.2 SSF-FSM state "Waiting For Instructions"
The test group objective is to check that the SSF reacts correctly on network events, expiration of the
application timer T , and a valid operation or operation sequence is accepted in the SSF-FSM state
SSF
"Waiting for Instructions".
5.2.1.2.2.1 Network events
Preamble: Trigger detected. InitialDP invoke has been sent. ResetTimer invoke has been
received.
Postamble: -
IN633001 To ensure that the IUT being in the "Waiting For Instructions State", at detection of
calling party abandon and no call information or charging reports pending,
7.1.5.
aborts the dialogue.
IN633002 To ensure that the IUT being in the "Waiting For Instructions" state, at detection of
T expiration,
SSF
7.1.5.1,
aborts the dialogue.
8.3.1
Preamble: Originating trigger detected. InitialDP invoke has been sent. oAbandon DP is
armed as an EDP-N.
Postamble: -
IN633003 To ensure that the IUT being in the "Waiting For Instructions State", at detection of
calling party abandon as an EDP-N
7.1.5.
sends an EventReportBCSM and terminates the dialogue by means of
prearranged end.
Preamble: Originating trigger detected. InitialDP invoke has been sent. oAbandon DP is
armed as an EDP-N and call information report is requested.
Postamble: -
IN633004 To ensure that the IUT being in the "Waiting
...