ETSI I-ETS 300 697-2 ed.1 (1998-03)
Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming Communication Interface (PCI); Part 2: Abstract Test Suite (ATS) specification for the PCI User Facility (PUF)
Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming Communication Interface (PCI); Part 2: Abstract Test Suite (ATS) specification for the PCI User Facility (PUF)
DI/TE-02028-3
Digitalno omrežje z integriranimi storitvami (ISDN) – Preskušanje skladnosti programirljivega komunikacijskega vmesnika (PCI) sistema Euro-ISDN – 2. del: Specifikacija abstraktnega preskušalnega niza (ATS) za uporabniške pripomočke vmesnika PCI (PUF)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 ±3UHVNXãDQMHVNODGQRVWL
SURJUDPLUOMLYHJDNRPXQLNDFLMVNHJDYPHVQLND 3&, VLVWHPD(XUR,6'1±GHO
6SHFLILNDFLMDDEVWUDNWQHJDSUHVNXãDOQHJDQL]D $76 ]DXSRUDEQLãNHSULSRPRþNH
YPHVQLND3&, 38)
Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN
Programming Communication Interface (PCI); Part 2: Abstract Test Suite (ATS)
specification for the PCI User Facility (PUF)
Ta slovenski standard je istoveten z: I-ETS 300 697-2 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
INTERIM
EUROPEAN I-ETS 300 697-2
TELECOMMUNICATION March 1998
STANDARD
Source: TE Reference: DI/TE-02028-3
ICS: 33.020
Key words: ISDN, PCI, ATS, testing
Integrated Services Digital Network (ISDN);
Conformance testing for the Euro-ISDN Programming
Communication Interface (PCI);
Part 2: Abstract Test Suite (ATS) specification
for the PCI User Facility (PUF)
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
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
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 1998. All rights reserved.
Page 2
I-ETS 300 697-2: March 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 3
I-ETS 300 697-2: March 1998
Contents
Foreword .7
Introduction.7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 General constraints for testing and applicable test methods .11
4.1 Testing model .11
4.2 Test methods for PCI message testing .11
4.3 Default values for directions in the Control and User Planes .13
5 ATS naming conventions and use of language conventions .14
6 Typical scenario for a Test Case.16
7 Order of parameters.16
8 Test Purpose (TP) to Test Case (TC) mapping .16
Annex A (normative): Abstract Test Suite (ATS) for ETS 300 325 PUF .17
A.1 The TTCN Graphical form (TTCN.GR) .17
A.2 The TTCN Machine Processable form (TTCN.MP) .17
Annex B (normative): PCTR for ETS 300 325 PUF .18
B.1 Identification summary .18
B.1.1 Protocol Conformance Test Report (PCTR).18
B.1.2 IUT .18
B.1.3 Testing environment .19
B.1.4 Limits and reservations.19
B.1.5 Comments .19
B.2 IUT conformance status.19
B.3 Static conformance summary.19
B.4 Dynamic conformance summary.19
B.5 Static conformance review report.20
B.6 Test campaign report .20
B.7 Observations .24
Annex C (normative): Partial IXIT proforma for ETS 300 325 PUF.25
C.1 Identification summary .25
Page 4
I-ETS 300 697-2: March 1998
C.2 Abstract Test Suite summary . 25
C.3 Test laboratory. 25
C.4 Client. 25
C.5 SUT. 26
C.6 Protocol information for ETS 300 325 PUF . 26
C.6.1 Protocol identification . 26
C.6.2 IUT information. 26
C.6.2.1 Addresses and compatible incoming parameters . 26
C.6.2.1.1 Exchange Mechanism. 26
C.6.2.1.2 Control Plane . 27
C.6.2.1.3 User Plane . 30
C.6.2.2 Information about connection . 31
C.6.2.3 Procedural information. 31
C.6.2.3.1 Exchange Mechanism. 31
C.6.2.3.2 Administration Plane . 32
C.6.2.3.3 Control Plane . 34
C.6.2.3.4 User Plane . 37
C.6.2.4 Upper interface observation. 38
C.6.2.4.1 Administration Plane . 39
C.6.2.4.2 Control Plane . 40
C.6.2.4.3 User Plane . 41
Annex D (informative): ETS 300 325 PUF PCI ICS proforma . 43
D.1 Instructions for completing the PUF PCI ICS proforma. 43
D.1.1 Purposes and structure .43
D.1.2 Symbols, abbreviations and conventions. 45
D.1.2.1 Standardized symbols for the status column. 45
D.1.2.2 Standardized symbols for the support column. 45
D.1.3 Instructions for completing the PCI ICS . 45
D.2 Identification of the implementation . 46
D.2.1 Date of statement. 46
D.2.2 Implementation Under Test (IUT) identification . 46
D.2.3 System Under Test (SUT) identification. 46
D.2.4 Product supplier . 46
D.2.5 Client . 47
D.2.6 ICS contact person. 47
D.3 PCI ICS/System Conformance Statement (SCS). 48
D.4 Identification of the PCI. 48
D.5 Global statement of conformance . 48
D.6 Static requirements. 49
D.6.1 Major capabilities. 49
D.6.1.1 Underlying Operating System. 49
D.6.1.2 Exchange Mechanism . 49
D.6.1.3 Connection types . 50
D.6.1.4 Dialling mode . 50
D.6.1.5 User Plane protocols . 50
D.6.2 Messages. 51
D.6.2.1 Administration Plane messages . 51
D.6.2.2 Control Plane messages. 52
D.6.2.3 User Plane messages . 54
D.6.3 Messages parameters. 55
D.6.3.1 Administration Plane messages parameters. 55
D.6.3.1.1 ACreateNCOReq . 55
Page 5
I-ETS 300 697-2: March 1998
D.6.3.1.2 ACreateNCOCnf.56
D.6.3.1.3 ADestroyNCOReq .56
D.6.3.1.4 ADestroyNCOCnf .56
D.6.3.1.5 AErrorInd .57
D.6.3.1.6 AGetNCOInfoReq.57
D.6.3.1.7 AGetNCOInfoCnf.57
D.6.3.1.8 ASecurityReq.57
D.6.3.1.9 ASecurityCnf.58
D.6.3.1.10 AManufacturerReq .58
D.6.3.1.11 AManufacturerInd .58
D.6.3.2 Control Plane messages parameters.58
D.6.3.2.1 CAlertReq .58
D.6.3.2.2 CAlertInd.59
D.6.3.2.3 CConnectReq .59
D.6.3.2.4 CConnectInd.60
D.6.3.2.5 CConnectRsp .60
D.6.3.2.6 CConnectCnf .60
D.6.3.2.7 CDisconnectReq.61
D.6.3.2.8 CDisconnectInd .61
D.6.3.2.9 CDisconnectRsp.62
D.6.3.2.10 CDisconnectCnf.62
D.6.3.2.11 CProgressInd.62
D.6.3.2.12 CStatusInd.62
D.6.3.2.13 CSetupAckInd.63
D.6.3.2.14 CConnectInfoReq .63
D.6.3.2.15 CProceedingInd.63
D.6.3.2.16 CUserInformationReq.64
D.6.3.2.17 CUserInformationInd .64
D.6.3.2.18 CCongestionControlReq.64
D.6.3.2.19 CCongestionControlInd .65
D.6.3.2.20 CSuspendReq .65
D.6.3.2.21 CSuspendCnf .65
D.6.3.2.22 CResumeReq .65
D.6.3.2.23 CResumeCnf.66
D.6.3.2.24 CNotifyInd .66
D.6.3.2.25 CFacilityReq .66
D.6.3.2.26 CFacilityInd .66
D.6.3.2.27 CExtEquipAvailibilityInd .67
D.6.3.2.28 CExtEquipBlockDiallingInd .67
D.6.3.2.29 CExtEquipKeyPressedInd .67
D.6.3.2.30 CExtEquipOffHookInd .67
D.6.3.2.31 CExtEquipOnHookInd .68
D.6.3.3 User Plane messages parameters.68
D.6.3.3.1 U3ConnectReq .68
D.6.3.3.2 U3ConnectInd.69
D.6.3.3.3 U3ConnectRsp .70
D.6.3.3.4 U3ConnectCnf .71
D.6.3.3.5 U3DisconnectReq.72
D.6.3.3.6 U3DisconnectInd .72
D.6.3.3.7 U3DataReq.73
D.6.3.3.8 U3DataInd.73
D.6.3.3.9 U3ExpeditedDataReq.73
D.6.3.3.10 U3ExpeditedDataInd.74
D.6.3.3.11 U3ResetReq .74
D.6.3.3.12 U3ResetInd.74
D.6.3.3.13 U3ResetRsp .75
D.6.3.3.14 U3ResetCnf .75
D.6.3.3.15 U3DataAcknowledgeReq.75
D.6.3.3.16 U3DataAcknowledgeInd .75
D.6.3.3.17 U3ReadyToReceiveReq.76
D.6.3.3.18 U3ReadyToReceiveInd.76
D.6.3.3.19 U3ErrorInd .76
D.6.3.3.20 U1DataReq.76
Page 6
I-ETS 300 697-2: March 1998
D.6.3.3.21 U1DataInd. 77
D.6.3.3.22 U1ErrorInd. 77
D.6.4 Miscellaneous features and supplementary services. 77
History. 78
Page 7
I-ETS 300 697-2: March 1998
Foreword
The second part of this Interim European Telecommunication Standard (I-ETS) has been produced by the
Terminal Equipment (TE) Technical Committee of the European Telecommunications Standards Institute
(ETSI).
An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution ahead
of a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETS
is limited to three years after which it can be converted into an ETS, have its life extended for a further two
years, be replaced by a new version, or be withdrawn.
This is the second part of a I-ETS which comprises four Parts:
"Integrated Services Digital Network (ISDN); Conformance testing for the Euro-ISDN Programming
Communication Interface (PCI);
Part 1: "Test Suite Structure and Test Purposes (TSS&TP) for the PCI User Facility (PUF);
Part 2: "Abstract Test Suite (ATS) for the PCI User Facility (PUF);
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) for the Network Access Facility (NAF);
Part 4: "Abstract Test Suite (ATS) for the Network Access Facility (NAF)".
Annexes A, B and C to this part of the I-ETS are normative whereas annex D is informative.
Announcement date
Date of adoption of this I-ETS: 6 March 1998
Date of latest announcement of this I-ETS (doa): 30 June 1998
Introduction
I-ETS 300 697, Parts 1 to 4 comprises the Test Suite Structure and Test Purposes (TSS&TP) and the
Abstract Test Suites (ATS) to ETS 300 325 [1]. The Euro-ISDN PCI is a PCI which provides access to the
Euro-ISDN. The basic model of the ISDN PCI consists of two entities, a service user called the PCI User
Facility (PUF) and a service provider called the Network Access Facility (NAF). For the purpose of
conformance testing, the PUF and the NAF are treated separately. This is because the PUF manufacturer
and the NAF manufacturer may be completely different and their testing needs should be treated
separately. Each part is tested to ensure that they each meet the conformance requirements of the ETS
and to increase their probability of inter-operating. This is the reason why a separate TSS&TP and a
separate ATS has been produced for each of the PCI User Facility (PUF) and the Network Access Facility
(NAF).
All Parts have been produced according to ISO/IEC 9646 [2, 3, 4, 5, 6] and ETS 300 406 [8].
As stated above, this I-ETS is structured in four parts:
- part 1 contains the TSS&TP for the PUF;
- part 2 contains the ATS for the PUF;
- part 3 contains the TSS&TP for the NAF;
- part 4 contains the ATS for the NAF.
Page 8
I-ETS 300 697-2: March 1998
Part 1 (TSS&TP for the PUF) contains all Test Purposes (TPs) for the PUF (PCI messages). It describes
what is covered by the TPs for the PUF and what areas of the ETS are not covered. The Test Suite
Structure is described and the convention followed in naming the TPs is described. A list of basic
interconnection tests is given.
This second Part of the I-ETS (ATS for the PUF) contains the ATS for the PUF (PCI messages). The
test method used is described in detail and diagrams explaining the test method are presented. The
reasons for choosing that test method are also given. The ATS is written in Tree and Tabular Combined
Notation language (TTCN) and the TTCN is contained in annex A. Annex B contains the Protocol
Conformance Test Report (PCTR), annex C contains the Implementation eXtra Information for Testing
(IXIT) and annex D contains an Implementation Conformance Statement (ICS).
Part 3 (TSS&TP for the NAF) contains all the TPs for the NAF (PCI messages and Exchange
Mechanism). It describes what is covered by the TPs for the NAF and what areas of the ETS are not
covered. The TSS is described and the TPs are given. A list of basic interconnection tests is given.
Part 4 (ATS for the NAF) contains the ATS for the NAF (PCI messages and Exchange Mechanism). The
test method used is described in detail and a diagram explaining the test method is given. The reasons for
choosing that test method is also given. The ATS is written in concurrent TTCN and the TTCN is
contained in annex A. Annex B contains the PCTR, annex C contains the IXIT and annex D contains an
ICS.
NOTE: The ICS in annexes D of part 2 and part 4 are informative as ETS 300 325 [1] already
contains an ICS. However, the ICS in ETS 300 325 [1] is not adequate for these ATSs
and should eventually be replaced by annex D of part 2 and part 4.
Page 9
I-ETS 300 697-2: March 1998
1 Scope
Part 2 of this I-ETS contains the Abstract Test Suite (ATS) for the PUF (PCI messages). The test method
used is described in detail and diagrams explaining the test method are presented. The reasons for
choosing this test method are also given. The Abstract Test Suite is written in TTCN and the TTCN is
contained in annex A. Annex B contains the PCTR, annex C contains the IXIT and annex D contains an
ICS.
2 Normative references
Part 2 of this I-ETS incorporates by dated or 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 I-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 325 (1994): "Integrated Services Digital Network (ISDN); Programming
Communication Interface (PCI) for Euro-ISDN".
[2] ISO/IEC 9646-1 (1991): "Information Technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts".
[3] ISO/IEC 9646-2 (1991): "Information Technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 2:
Abstract Test Suite specification".
[4] ISO/IEC 9646-3 (1992): "Information Technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 3:
The Tree and Tabular Combined Notation (TTCN)".
[5] ISO/IEC 9646-5 (1994): "Information Technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 5:
Requirements on test laboratories and clients for the conformance assessment
process".
[6] ISO/IEC DIS 9646-7 (1991): "Information Technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation Conformance Statement".
[7] ETS 300 697-1: "Integrated Services Digital Network (ISDN); Conformance
testing for the Euro-ISDN Programming Communication Interface (PCI); Part 1:
Test Suite Structure and Test Purposes (TSS&TP) for the PCI User facility
(PUF)".
[8] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization Methodology".
[9] ETS 300 080: "Integrated Services Digital Network (ISDN); ISDN lower layer
protocols for telematic terminals".
[10] ISO/IEC 8208 (1990): "Information technology; Data communications - X.25
Packet Layer Protocol for Data Terminal Equipment".
[11] CCITT Recommendation T.70 (1998): "Network-independent basic transport
service for the telematic services".
Page 10
I-ETS 300 697-2: March 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of part 2 of this I-ETS, the terms defined in ETS 300 325 [1], ISO/IEC 9646, Parts 1, 2,
3, 5 and 7 ([2] to [6]) and its amendments and draft amendments apply.
3.2 Abbreviations
For the purposes of this I-ETS, the following abbreviations apply:
AOC-E Advice Of Charging at End of call
API Application Programming Interface
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
CLIR Calling Line Identification Restriction
DDI Direct Dialling In
ExID Exchange IDentifier
HDLC High level Data Link Control
ICS Implementation Conformance Statement
ISDN Integrated Services Digital Network
IUT Implementation Under Test
IXIT Implementation eXtra Information for Testing
LT Lower Tester
MTS Methods for Testing and Specification
NAF Network Access Facility
NCO Network Connection Object
NCOID Network Connection Object Identifier
NMA Network layer Message Access
OSI Open Systems Interconnection
PCI Programming Communication Interface
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PUF PCI User Facility
SCS System Conformance Statement
SUT System Under Test
TC Test Case
TCV Test Case Variable
TMA Transparent Message Access
TP Test Purpose
TSC Test Suite Constant
TSO Test Suite Operation
TSS Test Suite Structure
TSS&TP Test Suite Structure & Test Purposes
TSV Test Suite Variable
TTCN Tree and Tabular Combined Notation
UT Upper Tester
Page 11
I-ETS 300 697-2: March 1998
4 General constraints for testing and applicable test methods
4.1 Testing model
A Euro-ISDN PCI is an interface and not a protocol standard. ISO/IEC 9646-2 [3] explicitly states that it
applies only to protocols of the Open Systems Interconnection (OSI) stack. This means that
ISO/IEC 9646-3 [4] cannot be used directly for testing ETS 300 325 [1]. This is why, whilst testing, the
layer model is applied to the EURO-ISDN PCI even though this notion does not exist in the ETS itself.
In the EURO-ISDN PCI, it is as if the Exchange Mechanism is a layer below the three planes,
Administration, Control and User. The Exchange Mechanism transports the messages of the three planes,
just as Layer 2 of a protocol transports Layer 3 Protocol Data Units (PDUs). The Exchange Mechanism
provides a service to the 3 planes.
Within this ATS, the upper layer, i.e. the layer of messages of the three planes, is referred to as the
"message layer" and the lower layer, i.e. the Exchange Mechanism, is referred to as the "Exchange
Mechanism layer". By using this model, ISO 9646, Parts 1, 2 and 3 [2,3,4] terminology can be used and
abstract test methods can be defined for each of the layers of this interface standard.
Using this model, PCI messages and the Exchange Mechanism should be tested in two different test
suites. Only PCI message testing is dealt with here.
4.2 Test methods for PCI message testing
a) Definitions
As previously stated, ISO 9646, Parts 1, 2 and 3 [2], [3], [4] can be used by mapping its concepts onto PCI
concepts.
PDUs: In ISO 9646, Parts 1, 2 and 3 [2,3,4] the data unit tested is called a "PDU", only because it normally
applies to protocols. However, the important concept behind this word is "what is tested" In this case, what
is tested are PCI messages. However, they shall still be called PDUs in the test suite.
Abstract Service Primitives (ASPs): In ISO 9646, Parts 1, 2 and 3 [2], [3], [4], ASPs are an
implementation-independent description of an interface between a service-user and a service-provider. In
particular, ASPs transport PDUs between the tested layer N+1 (service-user) and the layer N below
(service-provider) in the Lower Tester (LT). In this case, the Exchange Mechanism is the layer below the
message layer. Consequently, the description of Exchange Mechanism functions, independent of the
operating system, shall be called ASPs in the test suite. According to the test methods described below,
they are used within the LT (the NAF emulator).
Each function is translated into a pair of "FunctionName_Ind"/"FunctionName_Rsp" ASPs. A
"FunctionName_Ind" contains parameters provided by the PUF and a "FunctionName_Rsp" contains the
return parameters provided by the NAF.
EXAMPLE 1: PciDeregister function is translated into two ASPs: PciDeregister_ind with ExID
parameter, and PciDeregisterRsp with ErrorCode parameter.
Page 12
I-ETS 300 697-2: March 1998
b) Abstract Test Methods (ATMs)
There are two kinds of Test Purposes (TPs):
- one for which a point of observation is located in the LT and the control at the upper interface is not
specified and consists only of an implicit specification such as "do whatever is necessary within the
System Under Test (SUT) in order to provoke the required behaviour". In TTCN it is specified using
the implicit send event, with a reference to a procedural information item in the IXIT in annex C;
EXAMPLE 2: Ensure that the IUT in order to initiate an outgoing call sends a CConnectReq.
- one for which the point of observation is located at the upper interface of the Implementation Under
Test (IUT) (the verdict shall be assigned by the test operator who observes the behaviour of the IUT
at the upper interface). What is to be observed at this interface is not defined in ETS 300 325 [1]
and may vary greatly from IUT to IUT, therefore, the required observations are described as upper
interface observation items in the IXIT. The point of control is located in the LT.
These TPs are the "OP" (optional) TPs and may be de-selected as a group by answering "NO" to
an IXIT item. For more details, see ETS 300 697-1 [7].
EXAMPLE 3: Ensure that the IUT, on receiving a CAlertInd message, reacts as stated in the
IXIT.
There are two different ATMs to deal with these two kinds of TPs:
- a remote test method for the first case, called the PCIMsgRemote ATM (see figure 1);
- a distributed test method for the second one, called the PCIMsgDistributed ATM (see figure 2).
TEST SYSTEM
SUT
(NAF)
LT
IUT
PCI msg
"PDUs"
PCI messages
PCI messages
layer layer
PCO_L
Exch. mech ASPs
Exchange Exchange
mechanism mechanism
layer layer
Operating system
Key:
ASP Abstract Service Primitive
Exch mech ASPs Exchange Mechanism ASPs
IUT Implementation Under test
LT Lower Tester
NAF emul. NAF emulator
Operating system Operating system used by the Exchange Mechanism
PCI Msg PDUs PCI message PDUs
PCO_L Point of Control and Observation (Lower)
SUT System Under Test
Figure 1: PCIMsgRemote ATM
Page 13
I-ETS 300 697-2: March 1998
TEST SYSTEM
SUT
(NAF)
UT
PCO_U test operator
observation
LT
IUT
PCI msg
PCI messages "PDUs"
PCI messages
layer layer
PCO_L
Exch. mech ASPs
Exchange Exchange
mechanism mechanism
layer layer
Operating system
Key:
ASP Abstract Service Primitive
Exch mech ASPs Exchange Mechanism ASPs
IUT Implementation Under Test
LT Lower Tester
NAF emul. NAF emulator
Operating system Operating system used by the Exchange Mechanism
PCI Msg PDUs PCI message PDUs
PCO_L Point of Control and Observation (Lower)
PCO_U Point of Control and Observation (Upper)
SUT System Under Test
UT Upper Tester
Figure 2: PCIMsgDistributed ATM
4.3 Default values for directions in the Control and User Planes
There are very few mandatory features in a PUF, including the direction of calls on the Control and User
planes. When directions are not specified in a TP, the default direction is incoming for both planes.
However, this can only be if the IUT has claimed to support the incoming direction in answer to an
Implementation Conformance Statement (ICS) question.
An outgoing user connection can only be supported on an outgoing call in the Control Plane. In this
instance, for TCs about outgoing connection establishment on the User Plane, (the direction of the Control
Plane is not specified in such TPs), the direction for the Control Plane shall be outgoing.
IXIT items indicate the CDirection/UDirection combinations supported by the IUT, and allow the tester to
select the direction of the Control Plane.
The same problem can arise for the direction of data transfer and the direction of a user connection. It is
also dealt with by IXIT items used to indicate the UDirection/data transfer direction combinations.
Page 14
I-ETS 300 697-2: March 1998
5 ATS naming conventions and use of language conventions
The naming conventions described here have been chosen to ensure easy understanding of the ATS. As
far as possible, the names reflect their role in the ATS. When a name is used to represent an item from
the ETS, then the name shall be taken directly from the ETS and prefixed with the correct prefix. Where
an identifier is made up of one or more words, the words shall each start with a capital letter.
- The term IUT refers to the PUF under test.
- The term tester refers to the NAF emulator which performs the testing on the IUT.
- The test suite comprises one test component called the Lower Tester (LT).
- There are two Points of Control and Observation (PCO) used. A PCO is prefixed by PCO_
EXAMPLE 1: PCO_L PCO in the LT.
- Selection expressions start with SE_.
EXAMPLE 2: SE_NCOTypeC.
- Test suite operations start with TSO_.
EXAMPLE 3: TSO_CalculNCOType.
- Test suite constants start with TSC_.
EXAMPLE 4: TSC_CalledDTEAddress.
- When a TSC is used for to fill a field of a structured type, the name shall be generated as follow:
EXAMPLE 5: TSC_, e.g.TSC_NCOIDValue1.
- Test suite variables start with TSV_.
EXAMPLE 6: TSV_NCOTypeVal.
- Test suite parameters start with TSP_.
EXAMPLE 7: TSP_LocalNumber.
- Structured type definitions are named to reflect the nature of the type. Parameters of PCI
messages, e.g. GroupID, are denoted by par_GroupID and shall always be of type ,
e.g. GroupID.
EXAMPLE 8: GroupID is a structured type definition for the PCI parameter GroupID. and
par_GroupID is of type GroupID.
- Simple type definitions are named to reflect the nature of the type.
EXAMPLE 9: OCTETSTRING4 is a type definition for octetstrings of length 4.
- Test case variables start with TCV_.
EXAMPLE 10: TCV_Pci.
Page 15
I-ETS 300 697-2: March 1998
- Timers start with T_.
EXAMPLE 11: T_OptAct.
- PCI messages use the same names as in the ETS.
EXAMPLE 12: ACreateNCOReq.
- PCI message parameters use the same names as in the ETS but are prefixed by par_. The fields
of the parameters use the same names as the fields of the parameters in the ETS.
EXAMPLE 13: par_GroupID.
- When a parameter is used in the formal parameter list of a TTCN object, e.g. test step, constraint
etc., it is prefixed by p_.
EXAMPLE 14: p_Cause.
- There is a one-to-one mapping between the test purpose identifiers in ETS 300 697-1 [7] and the
test case names used in this test suite. The TPxxxxxx maps to TCxxxxxx.
EXAMPLE 15: TP431001 maps to TC431001.
- Test step names reflect the purpose of the test step. Those which are concerned with preambles
are prefixed with pre_ and those concerned with postambles are prefixed with post_.
EXAMPLE 16: pre_C2.
For each PDU a base constraint is defined, with the same name as the PDU followed by the digit 0. In
the base constraint of a message which is used in the direction from the tester to the PUF, optional fields
shall be omitted and mandatory fields shall have a value. In the direction from the PUF to the tester,
mandatory fields may take any legal value and optional fields can contain any value if present.
EXAMPLE 17: CDisconnectReq0.
Each modified constraint on the PDU shall be a modification of the base constraint. The modified
constraint shall be named by appending a mnemonic to the name of the base constraint. When a base
constraint is used, fields of the modified constraint which remain the same as fields of the base constraint
shall not appear in the subsequent constraint.
EXAMPLE 18: base constraint: CConnectInd0;
modified constraint: CConnectIndAlert.
Page 16
I-ETS 300 697-2: March 1998
6 Typical scenario for a Test Case
The initial state for all tests is that the NAF shall have declared itself.
The state of the interface may be either NULL or REGISTERED. The tester shall keep track of this state
because calls to Exchange Mechanism functions shall only allowed in certain states.
If the interface is in the REGISTERED state, then the test may proceed, else the PUF shall register.
If the test requires that an NCO be created because none exists at the moment, then the IUT shall be
asked to create an NCO with the correct characteristics.
If the test requires a D-channel to be present and there is none at the moment, then the NAF emulator
can initiate setting up a D-channel. This shall be used by both User Plane tests and tests such as
disconnection messages on the D-channel. One reason for the NAF emulator to initiate the call is that this
can be automated and, therefore, speed up execution of the test suite. In order to test more paths through
the ETS, some tests shall use the PUF to initiate the D-channel setup and they shall allow either en bloc
or overlap sending.
7 Order of parameters
The parameters in either a PCI message or an ISDN message can be sent by the NAF in any order. This
has not been taken into account in the test suite because all PDUs are represented in TTCN tabular form.
This shall be dealt with by the implementor of the ATS.
8 Test Purpose (TP) to Test Case (TC) mapping
There is a one-to-one mapping between the TCs and the TP identifiers, and they both have the same
identifier except for the TPs starting with TP and the TCs starting with TC.
Page 17
I-ETS 300 697-2: March 1998
Annex A (normative): Abstract Test Suite (ATS) for ETS 300 325 PUF
This ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according to
ISO/IEC 9646-3 [4].
The ATS was developed on a separate TTCN software tool and therefore the TTCN tables are not
completely referenced in the table of contents. The ATS itself contains a test suite overview part which
provides additional information and references.
A.1 The TTCN Graphical form (TTCN.GR)
The TTCN.GR representation of this ATS is contained in a Portable Document Format (DI16972.PDF
contained in archive 6972_i1.lzh) which accompanies this I-ETS.
A.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to this ATS is contained in an ASCII file (DI16972.MP
contained in archive 6972_i1.lzh) which accompanies this I-ETS.
NOTE: According to ISO/IEC 9646-3 [4], in case of a conflict in interpretation of the
operational semantics of TTCN.GR and TTCN.MP, the operational semantics of the
TTCN.GR representation takes precedence.
Page 18
I-ETS 300 697-2: March 1998
Annex B (normative): PCTR for ETS 300 325 PUF
Notwithstanding the provisions of the copyright clause related to the text of this I-ETS, ETSI grants that
users of this I-ETS may freely reproduce the ICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed ICS.
This annex contains a PCTR proforma which shall be used by a test laboratory to document the results of
conformance testing against ETS 300 325 [1] for the PUF, using the ATS specification in annex A, for a
specific client.
Text in italics is comment for guidance only and shall not to be included in the actual PCTR.
The name of the test laboratory, the PCTR number, the page number and the total number of pages
should appear on every page of the PCTR.
The PCTR shall use the format given as follows:
B.1 Identification summary
B.1.1 Protocol Conformance Test Report (PCTR)
PCTR Number:
PCTR Date:
Test laboratory:
Accreditation status:
Accreditation reference:
Technical Authority:
Job Title:
Signature:
Test Laboratory Manager:
Signature:
B.1.2 IUT
Name:
Version:
Protocol specification(s):
Information object specification(s)
ICS:
Page 19
I-ETS 300 697-2: March 1998
B.1.3 Testing environment
IXIT:
ATS specification:
Abstract Test Method:
Means of testing identification:
Period of testing:
Conformance Log references(s):
Retention Date for Log reference(s):
B.1.4 Limits and reservations
Additional information relevant to the technical contents or further use of the test report, or the rights and
obligations of the test laboratory and the client may be given here. Such information may include
restrictions on the publication of the report.
The order of TCs listed in clause B.6 of this PCTR corresponds to the ordering of TCs defined in the ATS
referenced in subclause B.1.3. This does not indicate that the TCs
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...