SIST ETS 300 324-4 E1:2003
(Main)V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)
V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)
Abstract Test Suite specification (ATS in TTCN) and protocol implementation extra information for testing (PIXIT) proforma V5.1 interface for support of Access Network; 2048 kBit/s interface without concentration capability within the Access Network
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 324-4 E1:
01-RNWREHU-
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna
dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma
specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN
side)
Ta slovenski standard je istoveten z: ETS 300 324-4 E1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
SIST ETS 300 324-4 E1: en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 324-4 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 324-4 E1:2003
DRAFT
EUROPEAN pr ETS 300 324-4
TELECOMMUNICATION December 1997
STANDARD
Source: SPS Reference: DE/SPS-03003.3-5
ICS: 33.020
Key words: V interface, V5 interface, AN, ATS, ISDN, layer 3, PIXIT, PSTN, testing
Signalling Protocols and Switching (SPS);
V interfaces at the digital Local Exchange (LE);
V5.1 interface for the support of Access Network (AN);
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network layer (AN side)
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: 3 ----------------------
SIST ETS 300 324-4 E1:2003
Page 2
Draft prETS 300 324-4: 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: 4 ----------------------
SIST ETS 300 324-4 E1:2003
Page 3
Draft prETS 300 324-4: December 1997
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .9
4 Abstract test method .9
4.1 ATM .10
4.2 NWK protocol testing.10
4.3 Data link addresses .11
4.4 Execution of TCs .11
4.4.1 Handling of error indication .11
4.4.2 TC execution sequence.11
5 Untestable test purposes.12
5.1 Control protocol.12
5.2 PSTN protocol.13
6 Abstract test suite conventions.14
6.1 Naming conventions .14
6.1.1 Declaration part .14
6.1.2 Constraint part.15
6.1.3 Dynamic part .15
6.1.3.1 TC.15
6.1.3.2 Test steps .15
6.1.3.3 General aspects .15
6.1.4 ATS abbreviations .16
6.2 Implementation conventions .16
6.2.1 Declaration part .16
6.2.2 Constraint part.17
6.2.3 Dynamic part .17
6.2.4 Documentation .18
Annex A (normative): Abstract test suite for NWK testing .19
A.1 The TTCN Graphical form (TTCN.GR) .19
A.2 The TTCN Machine Processable form (TTCN.MP) .19
Annex B (normative): Partial PIXIT proforma.20
B.1 Introduction.20
B.2 PIXIT proforma.20
B.2.1 Identification summary.20
B.2.2 Abstract test suite summary .20
B.2.3 Test laboratory.20
B.2.4 Client.20
B.2.5 SUT.20
B.2.6 Protocol layer information .20
B.2.6.1 Protocol identification .20
B.2.6.2 IUT information.21
---------------------- Page: 5 ----------------------
SIST ETS 300 324-4 E1:2003
Page 4
Draft prETS 300 324-4: December 1997
Annex C (informative): Bibliography . 26
History. 27
---------------------- Page: 6 ----------------------
SIST ETS 300 324-4 E1:2003
Page 5
Draft prETS 300 324-4: December 1997
Foreword
This draft European Telecommunication Standard (ETS) has been produced by the Signalling Protocols
and Switching (SPS) Technical Committee of the European Telecommunications Standards Institute
(ETSI), and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.
This ETS is part 4 of a multi-part standard covering the V5.1 interface as described below:
Part 1: "V5.1 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN
side)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the network layer (AN side)";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LE
side)";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the network layer (LE side)";
Part 7: "Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer";
Part 8: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the data link layer";
Part 9: "Test specification for the physical layer".
Proposed transposition dates
Date of latest announcement of this ETS (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
---------------------- Page: 7 ----------------------
SIST ETS 300 324-4 E1:2003
Page 6
Draft prETS 300 324-4: December 1997
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 324-4 E1:2003
Page 7
Draft prETS 300 324-4: December 1997
1 Scope
This fourth part of ETS 300 324 contains the Abstract Test Suite (ATS) as well as the Abstract Test
Method (ATM) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for
the Network layer (NWK) of the V5.1 interface and parts of the system management of the Access
Network (AN) side of a V5.1 interface.
The objective of this ETS is to provide an ATS containing conformance tests which give a high probability
of inter-operability of an AN and a Local Exchange (LE) from different manufacturers over the V5.1
interface.
ISO/IEC 9646-1 [5] and ISO/IEC 9646-2 [6] are used as the basis for the test methodology. The ATS is
defined using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [7].
The ATS in annex A describes a set of Test Cases (TCs) which are based on the Test Purposes (TPs)
specified in ETS 300 324-3 [3]. The TCs provide the implementation of the TPs and can be converted into
an executable test suite by using available TTCN translators and the corresponding tools.
Annex B provides the partial PIXIT proforma.
Annex C lists the bibliography.
2 Normative references
This 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 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 324-1 (1994) including amendment A1 (1996): "Signalling Protocols
and Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 1: V5.1 interface
specification".
[2] ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS)
proforma".
[3] ETS 300 324-3: "Signalling Protocols and Switching (SPS); V interfaces at the
digital Local Exchange (LE); V5.1 interface for the support of Access Network
(AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for
the network layer (AN side)".
[4] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference Model".
[5] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[6] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
[7] ISO/IEC 9646-3: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation (TTCN)".
[8] ISO/IEC 9646-5: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 5: Requirements on
test laboratories and clients for the conformance assessment process".
---------------------- Page: 9 ----------------------
SIST ETS 300 324-4 E1:2003
Page 8
Draft prETS 300 324-4: December 1997
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, together with those given in
ETS 300 324-1 [1]:
Abstract Test Case (ATC): Refer to ISO/IEC 9646-1 [5].
NOTE: In this ETS, the commonly used term TC is applied in the same way as ATC.
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].
current provisioning variant: ID for the presently active data set.
Data Link Layer (DLL): Refer to ISO 7498 [4].
embedded variant: Refer to ISO/IEC 9646-2 [6].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5].
incorrect information element: Specified IE carrying IE types not defined in ETS 300 324-1 [1].
invalid PSTN information element: PSTN IE not according to national specific requirements.
invalid protocol data unit: Protocol Data Unit (PDU) which contains an incorrect message format.
invalid PSTN message: PSTN message carrying IEs not according to national specific requirements.
Lower Tester (LT): Refer to ISO/IEC 9646-1 [5].
Network Layer (NWK): Refer to ISO 7498 [4].
new provisioning variant: ID for the data set which was announced to the IUT to become the next active
data set through re-provisioning.
Physical Layer (PHL): Refer to ISO 7498 [4].
PICS proforma: Refer to ISO/IEC 9646-1 [5].
PIXIT proforma: Refer to ISO/IEC 9646-1 [5].
Point Of Control And Observation (PCO): Refer to ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].
Protocol Implementation eXtra Information For Testing (PIXIT): Refer to ISO/IEC 9646-1 [5].
remote test method: Refer to ISO/IEC 9646-2 [6].
specified information element: IE ID defined in ETS 300 324-1 [1].
System Under Test (SUT): Refer to ISO/IEC 9646-1 [5].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
unknown provisioning variant: ID for a non-available data set.
unspecified information element: IE ID not defined in ETS 300 324-1 [1].
---------------------- Page: 10 ----------------------
SIST ETS 300 324-4 E1:2003
Page 9
Draft prETS 300 324-4: December 1997
valid information element: PSTN IE according to national specific requirements.
valid PSTN message: PSTN message carrying IEs according to national specific requirements.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATC Abstract Test Case
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA CApability test
CTRL Control
DLL Data Link Layer
DSAP Data link SAP
FE Function Element
FSM Finite State Machine
ID Identifier
IE Information Element
IEI Information Element Identifier
ISDN Integrated Services Digital Network
ISDN-BA ISDN-Basic Access
IT basic Interconnection Test
IUT Implementation Under Test
L3addr Layer 3 address
LC Line Circuit
LE Local Exchange
LT1 Lower Tester 1
PCO Point of Control and Observation
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PSTN Public Switched Telephone Network
SAP Service Access Point
SUT System Under Test
TC Test Case, the same definition as for ATC applies
TP Test Purposes
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UL Upper Layer
UT Upper Tester
V5DLaddr V5 Data Link address
---------------------- Page: 11 ----------------------
SIST ETS 300 324-4 E1:2003
Page 10
Draft prETS 300 324-4: December 1997
4 Abstract test method
This clause describes the Abstract Test Method (ATM) and the Point of Control and Observation (PCO)
used to test the NWK of the V5.1 protocol for the AN components.
4.1 ATM
Principally, the remote test method is used for V5.1 AN NWK conformance testing. Certain V5.1 AN NWK
TPs need also part of the service and national functions. Therefore, the embedded variant of the remote
test method is applied.
The national dependant information is defined in the PIXIT.
NOTE: The multi-party testing ATM (MPyT) (ISO/IEC 9646-2 [6], subclause 12.7), was also
considered for this ATS. But as the interfaces on the user port side may be
implemented on national specific standards the MPyT ATM was not applicable for this
ATS. To solve this need for operations on the user port interfaces, terminals will be
connected to the user ports. All necessary functions which would have been provided
by a lower tester connected to the user ports can be achieved by manual operations on
the connected terminal.
4.2 NWK protocol testing
The V5.1 implementations do not offer a direct access to the upper service boundary. The remote test
method was chosen because any co-ordination procedures can only be expressed in an informal way.
SUT V5 Test System
UT
LT1
V 5 NW K PD Us
IUT
DL-DATA
PCO/DSAP
V5-NW K
Service Provider
Control and PSTN
DLL & PHL layers DL connection endpoints
Figure 1: Remote single layer test method applied to the V5.1 NWK testing
LT1: A Lower Tester (LT1) is located in a remote V5.1 test system. It controls and
observes the behaviours of the IUT.
DSAP: A unique Data link Service Access Point (DSAP) is defined at the V5.1 interface
and commonly used for exchanging service data of the different Network layer
protocol functional entities: PSTN, Control protocols.
PCO: The PCO for NWK testing is located on the DSAP. All test events at the PCO
are specified in terms of data link Abstract Service Primitives (ASPs) and
network layer PDUs.
---------------------- Page: 12 ----------------------
SIST ETS 300 324-4 E1:2003
Page 11
Draft prETS 300 324-4: December 1997
UT: No explicit Upper Tester (UT) exists in the test system. However, the SUT
needs to carry out some UL functions to achieve some effects of test co-
ordination procedures. Designing ATS, the capability of the system
management functions, such as controls of the IUT, its interactions with the Q
interface may be taken into account. The controls of the IUT will be implied or
informally expressed in the ATS, but no assumption shall be made regarding
their feasibility or realisation. An example of such controls could be to provoke
restarting of the IUT through the Q interface.
V5-NWK: To test the PSTN and ISDN-BA protocols, a simulator shall be attached to
relevant User Port (UP).
4.3 Data link addresses
Within the DSAP, different V5DLaddr are used to identify each corresponding data link connection. Each
network layer protocol functional entity can have only one data link connection, e.g. all PSTN signalling
information shares one data link connection.
Table 1 shows the allocated V5DLaddr used by protocol function entities.
Table 1: V5DLaddr
Protocol PSTN Control
V5DLaddr 8176 8177
4.4 Execution of TCs
4.4.1 Handling of error indication
During the execution of the NWK ATS many error indications will be sent to the system management due
to the invalid and the inopportune TCs. It is up to the IUT supplier to take the necessary precautions to
avoid any impact on the test result.
4.4.2 TC execution sequence
The following test sequence shall be applied:
The TC containing the start-up procedure (TC11__SM_01) shall always be the first TC executed. Also in
any case where the IUT has to be restarted this TC shall be first executed.
Protocol groups: CTRL ⇒ PSTN.
Test groups: IT ⇒ CA ⇒ TI ⇒ BV ⇒ BO ⇒ BI.
Interactions between the different test groups are not considered. It is up to the IUT supplier to take the
necessary precautions to avoid any impact on the test result.
NOTE: This applies in particular to PORT CONTROL messages from ISDN ports while testing
PSTN-related protocols and vice versa.
---------------------- Page: 13 ----------------------
SIST ETS 300 324-4 E1:2003
Page 12
Draft prETS 300 324-4: December 1997
5 Untestable test purposes
This clause gives a list of TPs which are not implemented in the ATS due to the chosen abstract test
method or other restrictions.
5.1 Control protocol
The following test purposes are not implemented in the ATS due to unknown reaction of the IUT after
testing the TPs.
Table 2: Untestable TPs (1)
Test Purpose Reference to ETS 300 324-3 [3]
TP1324S1101 subclause 5.2.3.2.2
TP1324S1002 subclause 5.2.3.2.2
TP1324SM_06 subclause 5.2.3.2.2
TP1324SM_07 subclause 5.2.3.2.2
TP1325SM_03 subclause 5.2.3.2.3
TP1325S2207 subclause 5.2.3.2.3
TP1325S2208 subclause 5.2.3.2.3
TP1325S2209 subclause 5.2.3.2.3
TP1424S1101 subclause 5.2.4.2.2
TP1425SM_01 subclause 5.2.4.2.3
---------------------- Page: 14 ----------------------
SIST ETS 300 324-4 E1:2003
Page 13
Draft prETS 300 324-4: December 1997
5.2 PSTN protocol
The following test purposes are not implemented in the ATS due to unknown reaction of the IUT after
testing the TPs.
Table 3: Untestable TPs (2)
Test Purpose Reference to ETS 300 324-3 [3]
TP23__S0_01 subclause 5.3.3.1
TP23__S0_02 subclause 5.3.3.1
TP23__S0_03 subclause 5.3.3.1
TP23__S0_04 subclause 5.3.3.1
TP23__S0_05 subclause 5.3.3.1
TP23__S0_06 subclause 5.3.3.1
TP23__S0_07 subclause 5.3.3.1
TP23__S1_11 subclause 5.3.3.2
TP23__S2_11 subclause 5.3.3.3
TP23__S3_11 subclause 5.3.3.4
TP23__S4_10 subclause 5.3.3.5
TP23__S5_09 subclause 5.3.3.6
TP23__S6_03 subclause 5.3.3.7
TP23__S7_10 subclause 5.3.3.8
TP24__S0_01 subclause 5.3.4.1
TP24__S0_02 subclause 5.3.4.1
TP24__S0_03 subclause 5.3.4.1
TP24__S0_04 subclause 5.3.4.1
TP24__S0_05 subclause 5.3.4.1
TP24__S0_06 subclause 5.3.4.1
TP24__S0_07 subclause 5.3.4.1
TP24__S0_08 subclause 5.3.4.1
TP24__S2_03 subclause 5.3.4.3
TP24__S2_04 subclause 5.3.4.3
TP24__S3_04 subclause 5.3.4.4
TP24__S3_05 subclause 5.3.4.4
TP24__S4_05 subclause 5.3.4.5
TP24__S5_04 subclause 5.3.4.6
TP24__S5_05 subclause 5.3.4.6
TP24__S5_06 subclause 5.3.4.6
TP24__S7_02 subclause 5.3.4.8
Table 4 lists TPs which are not covered by the ATS because it is not possible to provoke the generation of
the necessary events.
Table 4: Untestable TPs (3)
Test Purpose Reference to ETS 300 324-3 [3]
TP23__S1_08 Refer to subclause 5.3.3.2
TP23__S1_09 Refer to subclause 5.3.3.2
TP23__S3_10 Refer to subclause 5.3.3.4
TP23__S4_06 Refer to subclause 5.3.3.5
TP23__S4_09 Refer to subclause 5.3.3.5
TP23__S6_05 Refer to subclause 5.3.3.7
TP23__S7_11 Refer to subclause 5.3.3.8
---------------------- Page: 15 ----------------------
SIST ETS 300 324-4 E1:2003
Page 14
Draft prETS 300 324-4: December 1997
6 Abstract test suite conventions
The ATS conventions are intended to give a better understanding of the ATS but they describe also the
conventions made for the development of the ATS, thus for any later maintenance purposes or further
development of the ATS the conventions described in this clause shall be considered.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions.
The naming conventions describe the structure of the naming of all ATS elements. The implementation
conventions describe the functional structure of the ATS.
NOTE: To define the ATS, the guidelines given in ETS 300 406 and ETR 141 were
considered.
6.1 Naming conventions
6.1.1 Declaration part
The ID names of the following definitions are written in lowercase:
- structured type definitions;
- ASP type definitions;
- PDU type definitions.
The ID names of the following definitions are written in uppercase:
- Test Suite Parameter Declarations;
- Test Case Selection Expression Definitions;
- Test Suite Constant Declarations;
- Test Case Variable Declarations.
ID names of PDUs and structured types commence with a protocol identifier to define which protocol they
are belonging to. The following identifiers are used:
- control protocol: ctrl e.g. crtl_common_control_ack;
- PSTN signalling: pstn e.g. pstn_signal_ack.
ID names of PDUs and structured types which are used for invalid tests commence with "bi".
EXAMPLE: bi_com_ctrl_two_mety.
Complete names as defined in the specifications are used for ID names of declarations.
EXAMPLE: ctrl_control_function_element.
Test suite parameter ID names commence with TSP:
- PICS are identified by adding the letter "C": TSPC_. (e.g.: TSPC_PSTN);
- PIXIT are identified by adding the letter "X": TSPX_. (e.g.: TSPX_PORT_ADDRESS).
If the test suite parameter is representing a system parameter or value, only the parameter name is used.
EXAMPLE: MR (receive sequence number in signal message).
Test suite operations commence with TSO.
EXAMPLE: TSO_INTEGER_TO_O_1.
Test suite constant ID names commence with TSC.
EXAMPLE: TSC_CFE_FE201_2_UNBL.
---------------------- Page: 16 ----------------------
SIST ETS 300 324-4 E1:2003
Page 15
Draft prETS 300 324-4: December 1997
If the constant is representing a system parameter or value, only the parameter name is used.
EXAMPLE: N01.
ID names of timers commence with T. The same names as in the specification are used.
EXAMPLE: T01.
6.1.2 Constraint part
Constraint names commence with uppercase. The remaining part of the ID name is written in lowercase.
ID names of elements concerning the same subject have equivalent names in the declaration and the
constraint part:
Declaration part: ctrl_control_function_element;
Constraint part: Ctrl_control_function_element.
The name of the modified constraint describes the particularity of the modified constraint.
EXAMPLE: Ctrl_cc_mand_only (common control message which contains only the
mandatory IEs).
If formal parameter lists are used, the variable names are written in lowercase. The variable name is the
same as the name of the element it is representing.
6.1.3 Dynamic part
6.1.3.1 TC
The identifier of the TCs is constructed in the same way as for the TPs described in ETS 300 324-3 [3],
subclause 5.1.1, with the exception that "TP" is replaced by "TC":
TP identifier: TP1324S1106;
TC identifier: TC1324S1106.
6.1.3.2 Test steps
In TCs, test steps as well as local trees are used. To allow an easy distinction, the following naming is
applied:
local tree: LTS_[local_tree_name];
test step: STEP_[test-step_name].
6.1.3.3 General aspects
All verdict assignments are labelled. To allow an exact identification in which table the verdict was
assigned, the following name convention is applied:
B test Body
CS Check State test steps
D Default
E Error handling test steps
PO POstamble
PR PReamble
S test Step
Combinations of labels are also possible.
EXAMPLE: DPR --> label which is used in a default for preambles.
---------------------- Page: 17 ----------------------
SIST ETS 300 324-4 E1:2003
Page 16
Draft prETS 300 324-4: December 1997
6.1.4 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
act activate
acc access
ack acknowledgement
cau cause
cc common control
cfe control function element
cfi control function identifier
com common
ctrl control
dl data link
enq enquiry
est establish
func function
ind indication
interf interface
mand mandatory
mety message type
mod modified
par parameter
pc port control
pd protocol discriminator
perform performance
prog progress
prot protocol
prov provisioned
repro re-provisioning
req request
rest restart
rsp response
var variant
verify verifying
vid variant & interface ID
6.2 Implementation conventions
6.2.1 Declaration part
The comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference
where the format and content of the element is described in the relevant protocol specifications. Any
particularity of the element format or content is described in the comment line.
The comment line in the header of multi-element TTCN tables (e.g. ASPs) is used to reference to the
protocol specification. The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations, the comments column is used to identify if an element is mandatory or
option
...
SLOVENSKI STANDARD
SIST ETS 300 324-4 E1:2003
01-december-2003
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna
dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma
specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN
side)
Ta slovenski standard je istoveten z: ETS 300 324-4 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
SIST ETS 300 324-4 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 324-4 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 324-4 E1:2003
EUROPEAN ETS 300 324-4
TELECOMMUNICATION April 1999
STANDARD
Source: SPS Reference: DE/SPS-09003.3-5
ICS: 33.020
Key words: V interface, V5 interface, PSTN, ISDN, AN, ATS, PIXIT, testing, layer 3
V interfaces at the digital Local Exchange (LE);
V5.1 interface for the support of Access Network (AN);
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network layer (AN side)
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.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 1999. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 324-4 E1:2003
Page 2
ETS 300 324-4: April 1999
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 Standards Making Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST ETS 300 324-4 E1:2003
Page 3
ETS 300 324-4: April 1999
Contents
Foreword . 5
1 Scope. 7
2 Normative references . 7
3 Definitions and abbreviations. 8
3.1 Definitions. 8
3.2 Abbreviations. 9
4 Abstract test method. 10
4.1 ATM. 10
4.2 NWK protocol testing.10
4.3 Data link addresses. 11
4.4 Execution of TCs . 11
4.4.1 Handling of error indication . 11
4.4.2 TC execution sequence . 11
5 Untestable test purposes . 12
5.1 Control protocol . 12
5.2 PSTN protocol . 13
6 Abstract test suite conventions . 14
6.1 Naming conventions. 14
6.1.1 Declaration part. 14
6.1.2 Constraint part . 15
6.1.3 Dynamic part. 15
6.1.3.1 TC. 15
6.1.3.2 Test steps. 15
6.1.3.3 General aspects . 15
6.1.4 ATS abbreviations. 16
6.2 Implementation conventions. 16
6.2.1 Declaration part. 16
6.2.2 Constraint part . 17
6.2.3 Dynamic part. 17
6.2.4 Documentation. 18
Annex A (normative): Abstract test suite for NWK testing . 19
A.1 The TTCN Graphical form (TTCN.GR). 19
A.2 The TTCN Machine Processable form (TTCN.MP). 19
Annex B (normative): Partial PIXIT proforma . 20
B.1 Introduction . 20
B.2 PIXIT proforma . 20
B.2.1 Identification summary . 20
B.2.2 Abstract test suite summary. 20
B.2.3 Test laboratory. 20
B.2.4 Client . 21
B.2.5 SUT . 21
B.2.6 Protocol layer information. 21
B.2.6.1 Protocol identification. 21
B.2.6.2 IUT information . 22
---------------------- Page: 5 ----------------------
SIST ETS 300 324-4 E1:2003
Page 4
ETS 300 324-4: April 1999
Annex C (informative): Bibliography.28
History.29
---------------------- Page: 6 ----------------------
SIST ETS 300 324-4 E1:2003
Page 5
ETS 300 324-4: April 1999
Foreword
This 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 4 of a multi-part standard covering the V5.1 interface as described below:
Part 1: "V5.1 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN
side)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the network layer (AN side)";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LE
side)";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the network layer (LE side)";
Part 7: "Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer";
Part 8: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the data link layer";
Part 9: "Test specification for the physical layer".
Transposition dates
Date of adoption of this ETS: 26 March 1999
Date of latest announcement of this ETS (doa): 30 June 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1999
Date of withdrawal of any conflicting National Standard (dow): 31 December 1999
---------------------- Page: 7 ----------------------
SIST ETS 300 324-4 E1:2003
Page 6
ETS 300 324-4: April 1999
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 324-4 E1:2003
Page 7
ETS 300 324-4: April 1999
1 Scope
This fourth part of ETS 300 324 contains the Abstract Test Suite (ATS) as well as the Abstract Test
Method (ATM) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for
the Network layer (NWK) of the V5.1 interface and parts of the system management of the Access
Network (AN) side of a V5.1 interface.
The objective of this ETS is to provide an ATS containing conformance tests which give a high probability
of inter-operability of an AN and a Local Exchange (LE) from different manufacturers over the V5.1
interface.
ISO/IEC 9646-1 [5] and ISO/IEC 9646-2 [6] are used as the basis for the test methodology. The ATS is
defined using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [7].
The ATS in annex A describes a set of Test Cases (TCs) which are based on the Test Purposes (TPs)
specified in ETS 300 324-3 [3]. The TCs provide the implementation of the TPs and can be converted into
an executable test suite by using available TTCN translators and the corresponding tools.
Annex B provides the partial PIXIT proforma.
Annex C lists the bibliography.
2 Normative references
This 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 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 324-1 (1994) including amendment A1: "V interfaces at the digital
Local Exchange (LE); V5.1 interface for the support of Access Network (AN);
Part 1: V5.1 interface specification".
[2] ETS 300 324-2 (1994): "V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 2: Protocol
Implementation Conformance Statement (PICS) proforma".
[3] ETS 300 324-3 (1999): "V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 3: Test Suite Structure
and Test Purposes (TSS&TP) specification for the network layer (AN side)".
[4] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference Model".
[5] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[6] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
[7] ISO/IEC 9646-3: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation (TTCN)".
[8] ISO/IEC 9646-5: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 5: Requirements on
test laboratories and clients for the conformance assessment process".
---------------------- Page: 9 ----------------------
SIST ETS 300 324-4 E1:2003
Page 8
ETS 300 324-4: April 1999
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, together with those given in
ETS 300 324-1 [1]:
Abstract Test Case (ATC): Refer to ISO/IEC 9646-1 [5]
NOTE: In this ETS, the commonly used term TC is applied in the same way as ATC.
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]
current provisioning variant: ID for the presently active data set
Data Link Layer (DLL): Refer to ISO 7498 [4]
embedded variant: Refer to ISO/IEC 9646-2 [6]
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5]
incorrect information element: Specified IE carrying IE types not defined in ETS 300 324-1 [1]
invalid PSTN information element: PSTN IE not according to national specific requirements
invalid protocol data unit: Protocol Data Unit (PDU) which contains an incorrect message format
invalid PSTN message: PSTN message carrying IEs not according to national specific requirements
Lower Tester (LT): Refer to ISO/IEC 9646-1 [5]
Network Layer (NWK): Refer to ISO 7498 [4]
new provisioning variant: ID for the data set which was announced to the IUT to become the next active
data set through re-provisioning
Physical Layer (PHL): Refer to ISO 7498 [4]
PICS proforma: Refer to ISO/IEC 9646-1 [5]
PIXIT proforma: Refer to ISO/IEC 9646-1 [5]
Point Of Control And Observation (PCO): Refer to ISO/IEC 9646-1 [5]
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5]
Protocol Implementation eXtra Information For Testing (PIXIT): Refer to ISO/IEC 9646-1 [5]
remote test method: Refer to ISO/IEC 9646-2 [6]
specified information element: IE ID defined in ETS 300 324-1 [1]
System Under Test (SUT): Refer to ISO/IEC 9646-1 [5]
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5]
unknown provisioning variant: ID for a non-available data set
unspecified information element: IE ID not defined in ETS 300 324-1 [1]
---------------------- Page: 10 ----------------------
SIST ETS 300 324-4 E1:2003
Page 9
ETS 300 324-4: April 1999
valid information element: PSTN IE according to national specific requirements
valid PSTN message: PSTN message carrying IEs according to national specific requirements
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATC Abstract Test Case
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA CApability test
CTRL Control
DLL Data Link Layer
DSAP Data link SAP
FE Function Element
FSM Finite State Machine
ID Identifier
IE Information Element
IEI Information Element Identifier
ISDN Integrated Services Digital Network
ISDN-BA ISDN-Basic Access
IT basic Interconnection Test
IUT Implementation Under Test
L3addr Layer 3 address
LE Local Exchange
LT1 Lower Tester 1
PCO Point of Control and Observation
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PSTN Public Switched Telephone Network
SAP Service Access Point
SUT System Under Test
TC Test Case, the same definition as for ATC applies
TP Test Purposes
TTCN Tree and Tabular Combined Notation
UL Upper Layer
UT Upper Tester
V5DLaddr V5 Data Link address
---------------------- Page: 11 ----------------------
SIST ETS 300 324-4 E1:2003
Page 10
ETS 300 324-4: April 1999
4 Abstract test method
This clause describes the Abstract Test Method (ATM) and the Point of Control and Observation (PCO)
used to test the NWK of the V5.1 protocol for the AN components.
4.1 ATM
Principally, the remote test method is used for V5.1 AN NWK conformance testing. Certain V5.1 AN NWK
TPs need also part of the service and national functions. Therefore, the embedded variant of the remote
test method is applied.
The national dependant information is defined in the PIXIT.
NOTE: The multi-party testing ATM (MPyT) (ISO/IEC 9646-2 [6], subclause 12.7, was also
considered for this ATS. But as the interfaces on the user port side may be
implemented on national specific standards the MPyT ATM was not applicable for this
ATS. To solve this need for operations on the user port interfaces, terminals will be
connected to the user ports. All necessary functions which would have been provided
by a lower tester connected to the user ports can be achieved by manual operations on
the connected terminal.
4.2 NWK protocol testing
The V5.1 implementations do not offer a direct access to the upper service boundary. The remote test
method was chosen because any co-ordination procedures can only be expressed in an informal way.
SUT V 5 Test System
UT
LT1
V 5 NW K PD Us
IUT
PCO/DSAP
V5-NW K
DL-DATA
Control,BCC, LINK,
Service Provider
Protection and PSTN
DLL & PHL layers
DL connection endpoints
Figure 1: Remote single layer test method applied to the V5.1 NWK testing
LT1: A Lower Tester (LT1) is located in a remote V5.1 test system. It controls and
observes the behaviours of the IUT.
DSAP: A unique Data link Service Access Point (DSAP) is defined at the V5.1 interface
and commonly used for exchanging service data of the different Network layer
protocol functional entities: PSTN, Control protocols.
PCO: The PCO for NWK testing is located on the DSAP. All test events at the PCO
are specified in terms of data link Abstract Service Primitives (ASPs) and
network layer PDUs.
---------------------- Page: 12 ----------------------
SIST ETS 300 324-4 E1:2003
Page 11
ETS 300 324-4: April 1999
UT: No explicit Upper Tester (UT) exists in the test system. However, the SUT
needs to carry out some UL functions to achieve some effects of test co-
ordination procedures. Designing ATS, the capability of the system
management functions, such as controls of the IUT, its interactions with the Q
interface may be taken into account. The controls of the IUT will be implied or
informally expressed in the ATS, but no assumption shall be made regarding
their feasibility or realization. An example of such controls could be to provoke
restarting of the IUT through the Q interface.
V5-NWK: To test the PSTN and ISDN-BA protocols, a simulator shall be attached to
relevant User Port (UP).
4.3 Data link addresses
Within the DSAP, different V5DLaddr are used to identify each corresponding data link connection. Each
network layer protocol functional entity can have only one data link connection, e.g. all PSTN signalling
information shares one data link connection.
Table 1 shows the allocated V5DLaddr used by protocol function entities.
Table 1: V5DLaddr
Protocol PSTN Control
V5DLaddr 8176 8177
4.4 Execution of TCs
4.4.1 Handling of error indication
During the execution of the NWK ATS many error indications will be sent to the system management due
to the invalid and the inopportune TCs. It is up to the IUT supplier to take the necessary precautions to
avoid any impact on the test result.
4.4.2 TC execution sequence
The following test sequence shall be applied:
The TC containing the start-up procedure (TC11__SM_01) shall always be the first TC executed. Also in
any case where the IUT has to be restarted this TC shall be first executed.
Protocol groups: CTRL ⇒ PSTN.
Test groups: IT ⇒ CA ⇒ TI ⇒ BV ⇒ BO ⇒ BI.
Interactions between the different test groups are not considered. It is up to the IUT supplier to take the
necessary precautions to avoid any impact on the test result.
NOTE: This applies in particular to PORT CONTROL messages from ISDN ports while testing
PSTN-related protocols and vice versa.
---------------------- Page: 13 ----------------------
SIST ETS 300 324-4 E1:2003
Page 12
ETS 300 324-4: April 1999
5 Untestable test purposes
This clause gives a list of TPs which are not implemented in the ATS due to the chosen abstract test
method or other restrictions.
5.1 Control protocol
The test purposes listed in table 2 are not implemented in the ATS due to unknown reaction of the IUT
after testing the TPs.
Table 2: Untestable TPs
Test Purpose
TP1311S1_01
TP1313S0_01
TP1321S2_01
TP1324S1001
TP1324S1002
TP1324SM_06
TP1324SM_07
TP1325SM_03
TP1325S2207
TP1325S2208
TP1325S2209
TP1424S1101
TP1425SM_01
TP1511S1_11
---------------------- Page: 14 ----------------------
SIST ETS 300 324-4 E1:2003
Page 13
ETS 300 324-4: April 1999
5.2 PSTN protocol
The test purposes listed in table 3 are not implemented in the ATS due to unknown reaction of the IUT
after testing the TPs.
Table 3: Untestable TPs
Test Purpose
TP23__S0_04
TP23__S0_05
TP23__S0_06
TP23__S0_07
TP23__S1_08
TP23__S1_09
TP23__S2_11
TP23__S3_10
TP23__S3_11
TP23__S4_06
TP23__S4_09
TP23__S4_10
TP23__S6_05
TP23__S7_11
TP24__S2_03
TP24__S2_04
TP24__S3_04
TP24__S3_05
TP24__S4_05
TP24__S5_03
TP24__S5_04
TP24__S5_05
TP24__S5_06
TP24__S7_02
TP26__S5_01
---------------------- Page: 15 ----------------------
SIST ETS 300 324-4 E1:2003
Page 14
ETS 300 324-4: April 1999
6 Abstract test suite conventions
The ATS conventions are intended to give a better understanding of the ATS but they describe also the
conventions made for the development of the ATS, thus for any later maintenance purposes or further
development of the ATS the conventions described in this clause shall be considered.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions.
The naming conventions describe the structure of the naming of all ATS elements. The implementation
conventions describe the functional structure of the ATS.
NOTE: To define the ATS, the guidelines given in ETS 300 406 and ETR 141 were
considered.
6.1 Naming conventions
6.1.1 Declaration part
The ID names of the following definitions are written in lowercase:
- structured type definitions;
- ASP type definitions;
- PDU type definitions.
The ID names of the following definitions are written in uppercase:
- Test Suite Parameter Declarations;
- Test Case Selection Expression Definitions;
- Test Suite Constant Declarations;
- Test Case Variable Declarations.
ID names of PDUs and structured types commence with a protocol identifier to define which protocol they
are belonging to. The following identifiers are used:
- control protocol: ctrl e.g. crtl_common_control_ack;
- PSTN signalling: pstn e.g. pstn_signal_ack.
ID names of PDUs and structured types which are used for invalid tests commence with "bi".
EXAMPLE 1: bi_com_ctrl_two_mety.
Complete names as defined in the specifications are used for ID names of declarations.
EXAMPLE 2: ctrl_control_function_element.
Test suite parameter ID names commence with TSP:
- PICS are identified by adding the letter "C": TSPC_. (e.g.: TSPC_PSTN);
- PIXIT are identified by adding the letter "X": TSPX_. (e.g.: TSPX_PORT_ADDRESS).
If the test suite parameter is representing a system parameter or value, only the parameter name is used.
EXAMPLE 3: MR (receive sequence number in signal message).
Test suite operations commence with TSO.
EXAMPLE 4: TSO_INTEGER_TO_O_1.
Test suite constant ID names commence with TSC.
EXAMPLE 5: TSC_CFE_FE201_2_UNBL.
If the constant is representing a system parameter or value, only the parameter name is used.
---------------------- Page: 16 ----------------------
SIST ETS 300 324-4 E1:2003
Page 15
ETS 300 324-4: April 1999
EXAMPLE 6: N01.
ID names of timers commence with T. The same names as in the specification are used.
EXAMPLE 7: T01.
6.1.2 Constraint part
Constraint names commence with uppercase. The remaining part of the ID name is written in lowercase.
ID names of elements concerning the same subject have equivalent names in the declaration and the
constraint part:
Declaration part: ctrl_control_function_element;
Constraint part: Ctrl_control_function_element.
The name of the modified constraint describes the particularity of the modified constraint.
EXAMPLE: Ctrl_cc_mand_only (common control message which contains only the
mandatory IEs).
If formal parameter lists are used, the variable names are written in lowercase. The variable name is the
same as the name of the element it is representing.
6.1.3 Dynamic part
6.1.3.1 TC
The identifier of the TCs is constructed in the same way as for the TPs described in ETS 300 324-3 [3],
subclause 5.1.1, with the exception that "TP" is replaced by "TC":
TP identifier: TP1324S1106;
TC identifier: TC1324S1106.
6.1.3.2 Test steps
In TCs, test steps as well as local trees are used. To allow an easy distinction, the following naming is
applied:
local tree: LTS_[local_tree_name];
test step: STEP_[test-step_name].
6.1.3.3 General aspects
All verdict assignments are labelled. To allow an exact identification in which table the verdict was
assigned, the following name convention is applied:
B test Body
CS Check State test steps
D Default
E Error handling test steps
PO POstamble
PR PReamble
S test Step
Combinations of labels are also possible.
EXAMPLE: DPR --> label which is used in a default for preambles.
---------------------- Page: 17 ----------------------
SIST ETS 300 324-4 E1:2003
Page 16
ETS 300 324-4: April 1999
6.1.4 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
act activate
acc access
ack acknowledgement
cau cause
cc common control
cfe control function element
cfi control function identifier
com common
ctrl control
dl data link
enq enquiry
est establish
func function
ind indication
interf interface
mand mandatory
mety message type
mod modified
par parameter
pc port control
pd protocol discriminator
perform performance
prog progress
prot protocol
prov provisioned
repro re-provisioning
req request
rest restart
rsp response
var variant
verify verifying
vid variant & interface ID
6.2 Implementation conventions
6.2.1 Declaration part
The comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference
where the format and content of the element is described in the relevant protocol specifications. Any
particularity of the element format or content is described in the comment line.
The comment line in the header of multi-element TTCN tables (e.g. ASPs) is used to reference to the
protocol specification. The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations, the comments column is used to identify if an element is mandatory or
optional:
m: mandatory;
o: optional.
In the ASP and PDU declarations the comments column is further used to give information about the
element value, in particular if the element contains a fixed spare value.
In tables where structure types are used the information element and the relevant structured type have
always the same name, that allows to have the same structure as in the protocol standards is used to
document the relation between information elements in a table and their specific description in an other
clause of the protocol standard.
---------------------- Page: 18 ----------------------
SIST ETS 300 324-4 E1:2003
Page 17
ETS 300 324-4: April 1999
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant element are parameterized. That improves the
transparency of the constraints in the dynamic part, as all values which are relevant for the test are always
present.
Generally the base constraint contains all possible parameters and the relevant formal parameter list
which goes with the base constraint. In case where a specific message IE is not used at all in the ATS, the
base constraint will not contain such an IE. The base constraints of the PSTN protocol contain all
mandatory IEs. The optional IEs are defined in one element of type OCTETSTRING. The actual value and
format of the optional IE has to be defined in the PIXITs according to the PSTN specifications which is
implemented in the IUT.
Modified constraints have the same parameter list as the base constraint. Unused elements of the
parameter list are set to a default value OMIT ("-") in the dynamic part. The number of base constraints is
reduced to a minimum.
The comment line of a constraint contains always the reference to the used specifications. The detailed
com
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.