ETSI TS 101 889-3 V1.1.1 (2003-01)

Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Compliance Specification; TIPHON profile for ITU-T H.248; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification

DTS/TIPHON-06017-3

Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3. izdaja - Specifikacija tehnološke ustreznosti - Profil TIPHON za ITU-T H.248 - 3. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proforma specifikacija

General Information

• Status: Published
• Publication Date: 06-Jan-2003
• Technical Committee: TIPHON 6 - TIPHON Verification, demonstration and implementation matters
• Current Stage: 12 - Completion
• Due Date: 20-Jan-2003
• Completion Date: 07-Jan-2003
• Ref Project: SIST-TS TS 101 889-3 V1.1.1:2004 - Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Compliance Specification; TIPHON profile for ITU-T H.248; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification

Standards Content (Sample)

SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Specifikacija tehnološke ustreznosti - Profil TIPHON za ITU-T H.248 - 3. del:
Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje
izvedbe protokola (PIXIT) - Proforma specifikacija
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Technology Compliance Specification; TIPHON profile for ITU-T H.248; Part
3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification
Ta slovenski standard je istoveten z: TS 101 889-3 Version 1.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3;
Technology Compliance Specification;
TIPHON profile for ITU-T H.248;
Part 3: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification
�
2 ETSI TS 101 889-3 V1.1.1 (2003-01)

Reference
DTS/TIPHON-06017-3
Keywords
ATS, H.248, IP, PIXIT, supplementary service,
telephony, testing, voice, VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 101 889-3 V1.1.1 (2003-01)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Abstract Test Method (ATM).8
4.1 Network architecture.8
4.2 Protocol architecture.8
4.3 Test architecture.9
4.4 Primitives at TR_PCO.10
5 Untestable Test Purposes (TP) .10
6 ATS conventions.11
6.1 Naming conventions.11
6.1.1 Declarations part.11
6.1.1.1 General.11
6.1.1.2 Test Suite Operations definition.11
6.1.1.3 Test Suite Parameter declarations .11
6.1.1.4 Test Case Selection expression definition.11
6.1.1.5 Test Suite Constant declarations .11
6.1.1.6 Test Suite Variable declarations.12
6.1.1.7 Test Case Variable declarations .12
6.1.1.8 Timer declarations.12
6.1.1.9 ASP type definitions .12
6.1.1.10 PDU type definitions.12
6.1.1.11 CM type definitions.12
6.1.1.12 Alias definitions.12
6.1.2 Constraints part.13
6.1.2.1 General.13
6.1.3 Dynamic part.13
6.1.3.1 General.13
6.1.3.2 Test Case (TC) identifier.13
6.1.3.3 Test step identifier.13
6.1.3.4 Default identifier.14
6.1.3.5 Label identifier.14
6.1.3.6 ATS abbreviations.14
6.2 Implementation conventions.14
6.2.1 Declaration part.14
6.2.2 Constraint part.15
6.2.3 Dynamic part.15
7 PCTR conformance.15
8 PIXIT conformance.16
9 ATS Conformance.16
Annex A (normative): Abstract Test Suite (ATS) .17
A.1 The TTCN Graphical form (TTCN.GR) .17
A.2 The TTCN Machine Processable form (TTCN.MP).17
Annex B (normative): Partial PIXIT proforma .18
ETSI
4 ETSI TS 101 889-3 V1.1.1 (2003-01)
B.1 Identification summary.18
B.2 ATS summary.18
B.3 Test laboratory.18
B.4 Client identification.19
B.5 SUT.19
B.6 Protocol layer information.19
B.6.1 Protocol identification.19
B.6.2 IUT information.20
B.6.2.1 General address parameters .20
B.6.2.2 Parameters for ephemeral terminations.21
B.6.2.3 Parameters for physical terminations.22
B.6.2.4 Parameters for descriptors .23
B.6.2.5 MG properties.25
B.6.2.6 Timers.25
Annex C (normative): PCTR proforma .26
C.1 Identification summary.26
C.1.1 Protocol conformance test report.26
C.1.2 IUT identification.26
C.1.3 Testing environment.26
C.1.4 Limits and reservation.27
C.1.5 Comments.27
C.2 IUT Conformance status .27
C.3 Static conformance summary.27
C.4 Dynamic conformance summary.28
C.5 Static conformance review report.28
C.6 Test campaign report for Media Gateway (MG).29
C.7 Test campaign report for Media Gateway Controller (MGC).32
C.8 Observations.34
History .35

ETSI
5 ETSI TS 101 889-3 V1.1.1 (2003-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON).
The present document is part 3 of a multi-part deliverable covering Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON); Technology Compliance Specification; TIPHON profile for ITU-T
Recommendation H.248, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification".
ETSI
6 ETSI TS 101 889-3 V1.1.1 (2003-01)
1 Scope
The present document specifies the Abstract Test Suite (ATS) for TIPHON profile for ITU-T Recommendation H.248,
according to TS 101 885 [1].
The objective of the present document is to provide a basis for conformance tests for TIPHON profile for ITU-T
Recommendation H.248 equipment giving a high probability of inter-operability between different manufacturer's
TIPHON profile for ITU-T Recommendation H.248 equipments.
The present document covers the procedures described in TS 101 885 [1] and ITU-T Recommendation H.248 [4].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [6] and ISO/IEC 9646-2 [7]) as well as
the ETSI rules for conformance testing (ETS 300 406 [5]) are used as a basis for the test methodology.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS.
Annex B provides the partial Protocol Implementation eXtra Information for Testing (PIXIT) Proforma of the ATS.
Annex C provides the Protocol Conformance Test Report (PCTR) proforma of the ATS.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ETSI TS 101 885: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 3; Technology Mapping; Technology Mapping of TIPHON reference point N
to H.248/MEGACO protocol".
[2] ETSI TS 101 889-1: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 3; Technology Compliance Specification; TIPHON profile for ITU-T H.248;
Part 1: Protocol Implementation Conformance Statement (PICS) proforma specification".
[3] ETSI TS 101 889-2: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 3; Technology Compliance Specification; TIPHON profile for ITU-T H.248;
Part 2: Test Suite Structure and Test Purposes (TSS&TP) specification".
[4] ITU-T Recommendation H.248 v2 (2002/02): "Gateway control protocol".
[5] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[6] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[8] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
ETSI
7 ETSI TS 101 889-3 V1.1.1 (2003-01)
[9] ISO/IEC 9646-4: " Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
[10] ISO/IEC 9646-5: "Information Technology-OSI Conformance Testing Methodology and
Framework, Part 5: Requirements on test laboratories and clients for the conformance assessment
process".
[11] ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 6: Protocol profile test specification".
[12] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
• Terms defined in ITU-T Recommendation H.248 [4];
• Terms defined in TS 101 885 [1];
• Terms defined in ISO/IEC 9646-1 [6] and in ISO/IEC 9646-2 [7].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [6], ISO/IEC 9646-6 [11],
ISO/IEC 9646-7 [12], TS 101 885 [1] and the following apply:
AC Audit Capabilities command
AD ADd command
AM Administration and Maintenance
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
AV Audit Value command
BI Invalid behaviour
BO Inopportune behaviour
BV Valid behaviour
IUT Implementation Under Test
LT Lower Tester
MD MoDify command
MG Media Gateway
MGC Media Gateway Controller
MO MOve command
MTC Main Test Component
N NOtify command
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SC Service Change command
SU SUbtract command
SUT System Under Test
TC Test Cases
TP Test Purpose
ETSI
8 ETSI TS 101 889-3 V1.1.1 (2003-01)
TR TRansport
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the TIPHON profile for ITU-T Recommendation H.248 [4], according to
TS 101 885 [1].
4.1 Network architecture
The IUT to be tested can be one of the following: Media Gateway or Media Gateway Controller (see figure 1).

Controller
CC
BC
Media Gateway
MC
Figure 1: Network architecture
4.2 Protocol architecture
The Implementation Under Test (IUT) for which this test case specification consists of the H.248 protocol
(see figure 2).
IUT
H.248
UDP TCP
IP
(LAN)
Figure 2: TIPHON protocol architecture
ETSI
9 ETSI TS 101 889-3 V1.1.1 (2003-01)
4.3 Test architecture
It is possible to specify an ATS based on a Single party (remote) test method for such an IUT when acting as an end
entity. However, it is considered that an ATS based on such an approach is of limited use as the only way to specify
IUT generated PDUs is to use the "implicit send" statement. Many users of such an ATS would replace the "implicit
send" statements with descriptions of the behaviour at other interfaces.
An ATS based on a multi-party test method is considered to be more useful as it is closer to the way a real test suite
would be constructed. Such a test method specifies behaviour at multiple network interfaces. One very important
limitation here is that tests are focussed on one particular interface. Hence the test system is made up of a Main Test
Component (MTC) plus one or more Parallel Test Components (PTC), see figure 4.

Notional UT
TR_PCO
Low er Tester SUT
ATS
H248
UDP/TCP
UDP/TCP
IP
IP
LAN/PHY
LAN/PHY
Figure 3: Test architecture
A single-party testing concept is used, which consists of the following abstract testing functions:
Lower Tester: A Lower Tester (LT) is located in the remote test system. It controls and observes the behaviour of
the IUT.
ATS: The Abstract Test Suite (ATS), defined in the present document, and located in the remote test
system.
CHN_PCO: A Point of Control and Observation (PCO) located at a virtual SAP corresponding to the H.248
port over the TCP/IP or UDP/IP protocol. All test events at the PCO are specified in terms of
Abstract Service Primitives (ASP) containing complete PDU.
Notional UT: No explicit Upper Tester (UT) exists in the system under test. Nevertheless, some specific actions
to cover implicit send events and to obtain feedback information are necessary for the need of the
test procedures. A black box covering these requirements is used in the SUT as a notional U. This
notional UT is considered as part of the test system.
ETSI
10 ETSI TS 101 889-3 V1.1.1 (2003-01)
Master part  Slave part
MTCA OPERATOR
CP1 (CP) PTC1 O
(PCO)
L0 (PCO)   L1 (PCO)
IUT
SUT
Figure 4: Multi-party test method
In a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves. The "slave"
testers are only an explicit description of how to deal with the remote interfaces during the testing process, i.e. "how to
make the IUT send the required message".
This means, in particular, that the verdict will only be assigned from the protocol aspects observed on the interface
under test (i.e. by the "master" tester), as it would be observed by a terminal connected to this interface. A failure in the
correlation between the protocol at the different interfaces to which the different testers are connected, i.e. in the
mechanism of the functional service itself, will not cause a FAIL verdict. For instance, if the IUT fails to send a
message on the tested interface after another interface has received the proper stimulus, the verdict will be
INCONCLUSIVE.
The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling the one PTC.
Thus it is responsible for starting the PTC and afterwards coordinates activities by exchanging Coordination Messages
(CM) with the PTCs. Secondly it is responsible for the behaviour of the Lower Tester (LT) at TR_PCO.
4.4 Primitives at TR_PCO
The primitive rcv_pdu (port_number, PDU_message) is used to receive H.248 messages from the IUT. The
port_number value shall be obtained by using primitives at TT_PCO at the beginning of the test case.
The primitive snd_pdu (port_number, PDU_message) is used to transmit H.248 messages to the IUT. The
channel_number value shall be obtained by using primitives at TT_PCO at the beginning of the test case.
5 Untestable Test Purposes (TP)
There are no untestable test purposes.
ETSI
11 ETSI TS 101 889-3 V1.1.1 (2003-01)
6 ATS conventions
The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions
made for the development of the ATS. These conventions shall be considered during any later maintenance or further
development of the ATS.
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.
To define the ATS, the guidelines of the document ETS 300 406 [5] was considered.
6.1 Naming conventions
6.1.1 Declarations part
This clause describes the naming conventions chosen for the elements of the ATS declarations part.
6.1.1.1 General
The following general rules apply for the name given in the declarations part. All type definitions (simple type
definitions, structured type definitions, ASP type definitions and PDU type definitions) shall be written according to the
ASN.1 definitions.
6.1.1.2 Test Suite Operations definition
The Test Suite Operation identifiers are composed of substrings beginning with the standard prefix "TSO_". An
underscore character ("_") separates each substring.
EXAMPLE: TSO_substring
6.1.1.3 Test Suite Parameter declarations
The Test Suite Parameter identifiers are composed of substrings beginning with the standard prefix "TSP_". An
underscore character ("_") separates each substring.
EXAMPLE 1: TSP_t_wait
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the letter "C" is
added to the standard prefix.
EXAMPLE 2: TSPC_MG
If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.
EXAMPLE 3: TSPX_TS_PORT
6.1.1.4 Test Case Selection expression definition
The Test Case Selection expression identifiers are composed of substrings in uppercase letters, beginning with the
prefix "TCS_". An underscore character ("_") separates each substring.
6.1.1.5 Test Suite Constant declarations
The Test Suite Constant identifiers are composed of substrings beginning with the prefix "TSC_". An underscore
character ("_") separates each substring.
If the test suite constant represents a system parameter, the complete name defined in the protocol standard is used.
ETSI
12 ETSI TS 101 889-3 V1.1.1 (2003-01)
6.1.1.6 Test Suite Variable declarations
The Test Suite Variable identifiers are composed of substrings in lowercase letters, except for the prefix "TSV_". An
underscore character ("_") separates each substring.
Complete names as defined in the protocol standard are used.
6.1.1.7 Test Case Variable declarations
The Test Case Variable identifiers are composed of substrings beginning with the prefix "TCV_". An underscore
character ("_") separates each substring.
6.1.1.8 Timer declarations
Two types of timers can be identified:
1) Standardized:
- Those defined in the protocol standard, e.g. LONG_TIMER. They use exactly the same name as in the
standard.
As there is a tolerance margin accepted for these timers, three values are needed:
- The maximum value allowed, which will use the suffix "_max";
- The minimum value allowed, which will use the suffix "_min";
- The value actually implemented, with no suffix;
EXAMPLE 1: LONG_TIMER _max, LONG_TIMER _min, and LONG_TIMER.
2) Not standardized:
- Those not defined in the protocol standard, i.e. for execution use, e.g. a timer waiting for a response.
These timers begin with the prefix "T_", followed by a string in uppercase letters.
EXAMPLE 2: T_ACK represents a timer for controlling the response time of the IUT.
6.1.1.9 ASP type definitions
The general conventions in clause 6.1.1.1 apply.
The identifier of an ASP type uses the same name as the name defined in the protocol standard.
6.1.1.10 PDU type definitions
The general conventions in clause 6.1.1.1 apply.
The PDU type identifier shall identify the related structure or type as defined in the protocol standard.
6.1.1.11 CM type definitions
The CM types are defined as the ASP types without sub-fields.
6.1.1.12 Alias definitions
Alias definitions are not used.
ETSI
13 ETSI TS 101 889-3 V1.1.1 (2003-01)
6.1.2 Constraints part
This clause describes the naming conventions chosen for the elements of the ATS constraints part.
6.1.2.1 General
Constraints are started in general with lowercase letters, except for the constraints for the H.248 Descriptors that start
with upper cases.
6.1.3 Dynamic part
This clause describes the naming conventions used for the elements of the ATS dynamic part.
6.1.3.1 General
All test cases shall be listed in the order in which they appear in the Test Suite Structure (TSS) and TP document.
6.1.3.2 Test Case (TC) identifier
The identifier of the test case is built in the same way as for the test purpose described in TS 101 889-2 [3], with the
exception that "TP" is replaced by "TC". The identifier of a TC is built according to table 1.
Table 1: TC naming convention
Identifier: TC____
  = IUT type MG Media Gateway
MGC Media Gateway Controller
  = group of procedures AD Procedures using ADd command (AD)
MD
Procedures using MoDify command (MD)
SU
Procedures using SUbtract command (SU)
MO
Procedures using MOve command (MO)
AV
Procedures using Audit Value command (AV)
AC
Procedures using Audit Capabilities command (AC)
NO
Procedures using NOtify command (NO)
SC
Procedures using Service Change command (SC)
AM
Administration and Maintenance procedures (AM)
TR
TRansport related procedures (TR)
E2
Base root package procedures
E11
Network package procedures
E13
TDM circuit package procedures
TN2
TIPHON profile procedures for TIPHON N2 interface
TN3
TIPHON profile procedures for TIPHON N3 interface
type   = Type of testing BV Valid Behaviour tests
BI Invalid Behaviour tests
BO Inopportune Behaviour tests
 = sequential number (01-99) Test Case Number

EXAMPLE: TP identifier: TP/MG/AD/BV-10
TC identifier: TC_MG_AD_BV_10.
6.1.3.3 Test step identifier
The test step identifier is built of substrings in lowercase letters, preceded by a string of uppercase letters. Underscore
characters join the substrings. The first substring indicates the main function of the test step; e.g. PR for preamble, PO
for postamble, LTS for local tree and STP for general test step. The second substring indicates the purpose of the step.
EXAMPLE: PO_general.
ETSI
14 ETSI TS 101 889-3 V1.1.1 (2003-01)
6.1.3.4 Default identifier
The default identifiers begin with the prefix "DF_", followed by a string in uppercase letters.
6.1.3.5 Label identifier
The identifiers in the label column are built according to table 2.
Table 2: Naming convention for verdict assignment identifier
Identifier:

 = type of table TB Test Body
CS Check State test step
DF DeFault
PO POstamble
PR PReamble
TS TestStep
   = sequential number (00-99) Label number

6.1.3.6 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
cac audit capabilities command request
cadd add command request
cav audit value command request
cmod modify command request
Cmov move command request
Cnot notify command request
Csc service change command request
Csub subtract command request
msg message
LC_Descr Local Control descriptor
L_Descr Local Descriptor
R_Descr Remote Descriptor
Stat_Descr Statistic Descriptor
rac audit capabilities command reply
radd add command reply
rav audit value command reply
rmod modify command reply
rmov move command reply
rnot notify command reply
rsc service change command reply
rsub subtract command reply
trq transaction request
tre transaction reply
tpe transaction pending
tack transaction acknowledge
tid transaction 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 standards. 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. ASP) is used to reference to the protocol standard.
ETSI
15 ETSI TS 101 889-3 V1.1.1 (2003-01)
The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations the comment column is further used to give information about the parameter/field
value, in particular if the parameter/field contains a fixed spare value.
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant parameters/fields 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 no modified constraints are used. This allows an easier reuse and adaptation of constraints if they are reused
in other test specifications.
The comment line of a constraint always contains a reference to the relevant protocol standard.
The detailed comment footer is used to describe any particularity of the table.
6.2.3 Dynamic part
All events, which are defined as a conformance requirement by the TP, cause a preliminary verdict PASS if the
requirement is met.
All invalid events are handled in the default tree. Only FAIL or INCONC verdicts are assigned in the default tree.
The preamble, the test body and the postamble may have different default trees, which allows a specific verdict
handling, e.g. only INCONC verdicts are assigned in the preamble.
All verdict assignments are labelled. According to ISO/IEC 9646-3 [8], clause E.2, labels should be written to the
conformance log. This allows, for example, to identify were the test failed. To allow an exact identification of the table,
in which the verdict was assigned, the convention described in clause 6.1.3.5 is applied.
TP, which are listed in the untestable TP list in clause 5, are not considered in the ATS, thus these TC identifiers are
missing in the ATS and the numbering of the TC is not always continuous.
7 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [10], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [10].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a
client to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A of
the present document.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
ETSI
16 ETSI TS 101 889-3 V1.1.1 (2003-01)
8 PIXIT conformance
A test realizer, producing an executable test suite for the Abstract Test Suite (ATS) specification contained in annex C,
is required, as specified in ISO/IEC 9646-4 [9], to produce an augmented partial PIXIT proforma conformant with this
partial PIXIT proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a
minimum, have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may
contain additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular
Implementation Under Test (IUT).
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [10], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma
conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents
which are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be
answered in order to prepare the test laboratory for a particular IUT.
9 ATS Conformance
The test realizer, producing a Means Of Testing (MOT) and Executable Test Suite (ExTS) for this Abstract Test Suite
(ATS) specification, shall comply with the requirements of ISO/IEC 9646-4 [9]. In particular, these concern the
realization of an Executable Test Suite (ExTS) based on each ATS. The test realizer shall provide a statement of
conformance of the MOT to this ATS specification.
An ExTS which conforms to this ATS specification shall contain test groups and test cases which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall
be capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each test
case.
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [10].
A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.
ETSI
17 ETSI TS 101 889-3 V1.1.1 (2003-01)
Annex A (normative):
Abstract Test Suite (ATS)
This ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [8].
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 an Adobe Portable Document Format™ file (H248.PDF
contained in archive ts_10188903v010101p0.ZIP) which accompanies the present document.
A.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to this ATS is contained in an ASCII file (H248.MP contained in archive
ts_10188903v010101p0.ZIP) which accompanies the present document.
NOTE: Where an ETSI Abstract Test Suite (in TTCN) is published in both .GR and .MP format these two forms
shall be considered equivalent. In the event that there appears to be syntactical or semantic differences
between the two then the problem shall be resolved and the erroneous format (whichever it is) shall be
corrected.
ETSI
18 ETSI TS 101 889-3 V1.1.1 (2003-01)
Annex B (normative):
Partial PIXIT proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PIXIT.
The PIXIT Proforma is based on ISO/IEC 9646-6. Any needed additional information can be found in this international
standard document.
B.1 Identification summary
Table B.1
PIXIT Number:
Test Laboratory Name:
Date of Issue:
Issued to:
B.2 ATS summary
Table B.2
Protocol Specification: TS 101 885

Protocol to be tested:
ATS Specification: TS 101 889-3

Abstract Test Method: TS 101 889-3, clause 4

B.3 Test laboratory
Table B.3
Test Laboratory Identification:

Test Laboratory Manager:
Means of Testing:
SAP Address:
ETSI
19 ETSI TS 101 889-3 V1.1.1 (2003-01)
B.4 Client identification
Table B.4
Client Identification:
Client Test manager:
Test Facilities required:
B.5 SUT
Table B.5
Name:
Version:
SCS Number:
Machine configuration:
Operating System Identification:

IUT Identification:
PICS Reference for IUT:
Limitations of the SUT:
Environmental Conditions:
B.6 Protocol layer information
B.6.1 Protocol identification
Table B.6
Name: TIPHON profile for ITU-T Recommendation H.248, according to TS 101 885.

Version:
PICS References: TS 101 889-1
ETSI
20 ETSI TS 101 889-3 V1.1.1 (2003-01)
B.6.2 IUT information
B.6.
...