SIST-TS TS 101 890-3 V1.1.1:2004

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.245 - 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 Specifications; TIPHON profile for ITU-T H.245; 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 890-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 Specifications;
TIPHON profile for ITU-T H.245;
Part 3: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification
�
2 ETSI TS 101 890-3 V1.1.1 (2002-01)

Reference
DTS/TIPHON-06018-3
Keywords
ATS, IP, supplementary service, testing, VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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:
editor@etsi.fr
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 2002.
All rights reserved.
ETSI
3 ETSI TS 101 890-3 V1.1.1 (2002-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
5 Untestable Test Purposes (TP) .9
6 ATS conventions.10
6.1 Naming conventions.10
6.1.1 Declarations part.10
6.1.1.1 General.10
6.1.1.2 Test suite operations definition .10
6.1.1.3 Test suite parameter declarations .10
6.1.1.4 Test case selection expression definition .10
6.1.1.5 Test suite constant declarations.11
6.1.1.6 Test suite variable declarations .11
6.1.1.7 Test case variable declarations.11
6.1.1.8 Timer declarations.11
6.1.1.9 ASP type definitions .11
6.1.1.10 PDU type definitions.11
6.1.1.11 CM type definitions.11
6.1.1.12 Alias definitions.12
6.1.2 Constraints part.12
6.1.2.1 General.12
6.1.3 Dynamic part.12
6.1.3.1 General.12
6.1.3.2 Test Case (TC) identifier.12
6.1.3.3 Test step identifier.12
6.1.3.4 Default identifier.13
6.1.3.5 Label identifier.13
6.1.3.6 ATS abbreviations.13
6.2 Implementation conventions.13
6.2.1 Declaration part.13
6.2.2 Constraint part.14
6.2.3 Dynamic part.14
7 Primitives.14
7.1 Primitives at CHN_PCO .14
7.2 Primitives at TT_PCO.14
7.3 Primitives at UT_PCO.14
Annex A (normative): Abstract Test Suite (ATS) .16
A.1 The TTCN Graphical form (TTCN.GR) .16
A.2 The TTCN Machine Processable form (TTCN.MP).16
Annex B (normative): Partial PIXIT proforma .17
ETSI
4 ETSI TS 101 890-3 V1.1.1 (2002-01)
B.1 Identification summary.17
B.2 ATS summary.17
B.3 Test laboratory.17
B.4 Client identification.18
B.5 SUT.18
B.6 Protocol layer information.18
B.6.1 Protocol identification.18
B.6.2 IUT information.19
Annex C (normative): PCTR Proforma.20
C.1 Identification summary.20
C.1.1 Protocol conformance test report.20
C.1.2 IUT identification.20
C.1.3 Testing environment.20
C.1.4 Limits and reservation.21
C.1.5 Comments.21
C.2 IUT Conformance status .21
C.3 Static conformance summary.21
C.4 Dynamic conformance summary.21
C.5 Static conformance review report.22
C.6 Test campaign report for Originating Endpoint (OE) .22
C.7 Test campaign report for Terminating Endpoint (OE) .24
C.8 Observations.25
Annex D (informative): Bibliography.26
History .27

ETSI
5 ETSI TS 101 890-3 V1.1.1 (2002-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).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
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 multi-part deliverable covering Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3; Technology Compliance Specifications; TIPHON profile for
ITU-T Recommendation H.245, 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 890-3 V1.1.1 (2002-01)
1 Scope
The present document specifies the Abstract Test Suite (ATS) for TIPHON profile for ITU-T Recommendation
H.245 [4], according to TS 101 883 [1].
The objective of this test specification is to provide a basis for conformance tests for TIPHON profile for ITU-T
Recommendation H.245 equipment giving a high probability of inter-operability between different manufacturer's
TIPHON profile for ITU-T Recommendation H.245 equipments.
This test specification covers the procedures described in TS 101 883 [1], ITU-T Recommendation H.323 [2] and
ITU-T Recommendation H.245 [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.
[1] ETSI TS 101 883: "Telecommunications and Internet protocol Harmonization Over Networks
(TIPHON) Release 3; Technology Mapping; Implementation of TIPHON architecture using
H.323".
[2] ITU-T Recommendation H.323 (Version 3, 1999): "Packet-based multimedia communications
systems".
[3] ITU-T Recommendation H.225.0: "Call signalling protocols and media stream packetization for
packet-based multimedia communication systems".
[4] ITU-T Recommendation H.245 (Version 7, 2000): "Control protocol for multimedia
communication".
[5] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[6] ISO/IEC 9646-1 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-2 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract Test Suite specification".
[8] ISO/IEC 9646-3 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[9] ISO/IEC 9646-6 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 6: Protocol profile test specification".
ETSI
7 ETSI TS 101 890-3 V1.1.1 (2002-01)
[10] ISO/IEC 9646-7 (1991): "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.323 [2];
• Terms defined in ITU-T Recommendation H.245 [4];
• Terms defined in TS 101 883 [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 [9],
ISO/IEC 9646-7 [10] and TS 101 883 [1] and the following apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BLC Bi-directional Logical Channel
B-LCSE Bi-directional Logical Channel Signalling Entity
BO Inopportune Behaviour
BV Valid Behaviour
CEP Capability Exchange Procedures
CESE Capability Exchange Signalling Entity
CLC Close Logical Channel
CLCSE Close Logical Channel Signalling Entity
IUT Implementation Under Test
LCS Logical Channel Signalling
LCSE Logical Channel Signalling Entity
LT Lower Tester
MC H.323 Multipoint Control entity
MCU Multipoint Control Unit
MRS Mode RequeSt
MRSE Mode Request Signalling Entity
MSD Master Slave Determination
MSDSE Master Slave Determination Signalling Entity
MTC Main Test Component
OE Originating Endpoint
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
SUT System Under Test
TC Test Cases
TE Terminating Endpoint
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
ETSI
8 ETSI TS 101 890-3 V1.1.1 (2002-01)
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the TIPHON profile for ITU-T Recommendation H.245 [4], according to
TS 101 883 [1].
4.1 Network architecture
The IUT to be tested can be one of the following: Originating (outgoing) or Terminating (incoming) Endpoint. They are
a part of a Packet Based Network using a LAN with TCP/IP (see figure 1).
Terminating Originating
(Outgoing)
(Incoming)
Terminal
Terminal
LAN
TCP/IP
Figure 1: network architecture
4.2 Protocol architecture
The Implementation Under Test (IUT) for which this Test case specification applies consists of the H.245 protocol
(see figure 2).
IUT
H.245
H225.0
UDP TCP
IP
(LAN)
Figure 2: TIPHON protocol architecture (see note)
NOTE: According to TS 101 883 [1] clause 5.1.6.1.4.2: ITU-T Recommendation H.245 [4] messages are
encapsulated within ITU-T Recommendation H.225.0 [3] messages according to ITU-T Recommendation
H.323 [2] clause 8.2.1.
ETSI
9 ETSI TS 101 890-3 V1.1.1 (2002-01)
4.3 Test architecture
Notional UT
UT_PCO
Low er Tester SUT
TT_PCO
ATS
H245
H225.0
CHN_PCO
H225.0
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.
TT_PCO: A Point of Control and Observation (PCO) located at TT_SAP and used to open and to close the
H245 channel over the H225.0 protocol. All test events at the PCO are specified in terms of
Abstract Service Primitives (ASP).
CHN_PCO: A Point of Control and Observation (PCO) located at a virtual SAP corresponding to the H245
channel over the H225.0 protocol. All test events at the PCO are specified in terms of Abstract
Service Primitives (ASP) containing complete PDU.
UT_PCO: A specific Point of Control and Observation (PCO) located at specific SAP and used to control the
Upper layer of H245 in the IUT. The upper layer of H245 shall understand and answer to specific
primitives for testing. All test events at the PCO are specified in terms of Abstract Service
Primitives (ASP).
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 UT as
defined in ISO 9646. This notional UT is considered as part of the test system.
5 Untestable Test Purposes (TP)
This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions.
Table 1: Untestable TP
Test purpose Reason
ETSI
10 ETSI TS 101 890-3 V1.1.1 (2002-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 giving in the declarations part. All type definitions (simple type
definitions, structured type definitions, ASP type definitions and PDU type definitions) shall be written in uppercase.
All element names (structured type definition), parameter names (ASP type definition) and field names (PDU type
definition) shall be written in lowercase.
Predefined types (e.g. BITSTRING[8]) are never used in structured type definitions, ASP type definitions or PDU type
definitions. Simple types are used instead.
6.1.1.2 Test suite operations definition
The test suite operation identifiers are composed of substrings in lowercase letters, except for 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 in lowercase letters, except for 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_encryption_support.
If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.
EXAMPLE 3: TSPX_pid.
6.1.1.4 Test case selection expression definition
The test case selection expression identifiers are composed of substrings in lowercase letters, beginning with the prefix
"TCS_". An underscore character ("_") separates each substring.
ETSI
11 ETSI TS 101 890-3 V1.1.1 (2002-01)
6.1.1.5 Test suite constant declarations
The test suite constant identifiers are composed of substrings in lowercase letters, except for 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.
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 in lowercase letters, except for the prefix "TCV_". An
underscore character ("_") separates each substring.
Complete names as defined in the protocol standard are used.
6.1.1.8 Timer declarations
Two types of timers can be identified:
1) Standardized:
- Those defined in the protocol standard, e.g. T105. 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: T105_max, T105_min, and T105.
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 lowercase letters.
EXAMPLE 2: T_resp 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.
ETSI
12 ETSI TS 101 890-3 V1.1.1 (2002-01)
6.1.1.12 Alias definitions
Alias definitions are not used.
6.1.2 Constraints part
This
...