SIST-TS TS 101 889-2 V1.1.1:2004

• Abstract:

  Design of Test Suite Structure and implementation of Test Purposes for conformance testing of an H.248 protocol implementation in a physically decomposed multimedia gateway for the H.323 environment.

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI TS 101 889-2 V1.1.1 (2002-08) - 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

SIST-TS TS 101 889-2 V1.1.1:2004 is the Slovenian adoption of ETSI TS 101 889-2, published by SIST. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for conformance testing of the TIPHON profile for ITU-T H.248.1, focused on H.248 protocol implementations in physically decomposed multimedia gateways for the H.323 environment. The document is written for both Media Gateway (MG) and Media Gateway Controller (MGC) roles, and it organizes tests into valid, invalid and inopportune behaviour cases.

What does SIST-TS TS 101 889-2 V1.1.1:2004 specify?

SIST-TS TS 101 889-2 V1.1.1:2004 defines the test suite structure and test purposes used to check conformance of TIPHON mapping to the H.248 protocol as defined in TS 101 885. In practice, it tells a tester or supplier what behaviours must be exercised when validating an H.248.1 implementation against the TIPHON profile.

The scope is limited to conformance testing of an H.248 protocol implementation in a physically decomposed multimedia gateway for the H.323 environment. The foreword places it as part 2 of a multi-part deliverable, alongside the PICS proforma in part 1 and the ATS/PIXIT material in part 3.

The document is organized into these main parts:

• Foreword
• Scope
• References
• Definitions and abbreviations
• Test Suite Structure (TSS)
• Test Purposes (TP)
• Annex A, which gives normative remarks and wildcard rules

Annex	What it covers
Annex A	General remarks on the H.248.1 test purposes and the wildcard matrix for Context Ids and Termination Ids

What are the key requirements of SIST-TS TS 101 889-2 V1.1.1:2004?

SIST-TS TS 101 889-2 V1.1.1:2004 is primarily a test specification, so its key content is the way it classifies tests and the message patterns each test is meant to cover. For users, the practical value is that it tells you which H.248.1 behaviours should be checked, how to name them, and how to relate them to the protocol roles and command types.

The test suite is built as a three-level tree

Clause 4 structures the TSS as a tree with a protocol group at the top, then the role of the implementation under test, then groups of procedures, and finally the ISO subgroups BV, BI and BO. This matters because it gives a repeatable way to select tests for a gateway acting as an MG or an MGC.

The two protocol groups are:

• Media Gateway (MG)
• Media Gateway Controller (MGC)

Within each role, the test groups are organized around H.248.1 commands and profile-specific procedures. That lets a test plan focus on the functions actually implemented in a product.

The document separates valid, invalid and inopportune behaviour

Clause 4.1.3 defines three main test subgroups:

• BV - valid behaviour
• BI - invalid behaviour
• BO - inopportune behaviour

BV tests verify normal exchanges of valid PDUs. BI tests check how the implementation reacts to syntactically invalid PDUs. BO tests cover validly encoded PDUs that are not expected in the current state or message exchange. In practice, this distinction matters because a compliant gateway must handle both normal traffic and protocol errors predictably.

Test purposes have a defined naming convention and structure

Clause 5.1.1 gives the TP identifier format TP/<iut>/<gp>/<type>-<nn>. The identifier shows the role under test, the procedure group, the test type and the sequence number. That helps engineers trace a failed case back to the exact command and behaviour being tested.

Clause 5.1.2 defines a common TP structure with a header, stimulus, reaction and message structure. This makes the text suitable as a basis for an Abstract Test Suite in TTCN, which is important if the test purposes will later be turned into executable conformance tests.

The test strategy is based on external behaviour and the PICS

Clause 5.1.3 says the TPs are derived from analysis of the base standard and the corresponding PICS proforma in TS 101 889-1. The tests focus on externally observable behaviour over the TCP or UDP interface and on realistic situations likely to be encountered by a real implementation. For a buyer or lab, this means the document is aimed at observable interoperability, not internal design details.

Wildcards and addressing rules are central to the test cases

Clause 5.1.4 and Annex A define how wildcarded Context Ids and Termination Ids are used in the test purposes. The document uses special conventions for ALL and CHOOSE, and Annex A explains the allowed and forbidden combinations for each command.

This matters in practice because H.248 test cases often depend on whether the MG or MGC is addressing:

• a specific Context
• all Contexts
• the Null Context
• a specific Termination
• all matching Terminations
• the ROOT Termination

If a wildcard combination is not allowed by the protocol, the implementation under test is expected to return an Error Descriptor.

The command coverage is broad and role-specific

Clauses 5.1.5 to 5.2.12 cover test purposes for both MG and MGC across the main H.248.1 commands and related procedures, including Add, Modify, Subtract, Move, Audit Value, Audit Capabilities, Notify, Service Change, Administration and Maintenance, and transport-related procedures. The MG side also includes TIPHON profile procedures for the N2 and N3 interfaces, while the MGC side includes the corresponding call setup and release procedures.

For a reader deciding whether this is the right standard, the practical point is that it does not only check command syntax. It also checks gateway state handling, context and termination addressing, service change handling, and profile-specific call behaviour.

Annex A gives the protocol logic behind the test selection

Annex A separates generic TPs from profile-specific TPs. It states that generic tests cover Context and Termination addressing, transport mechanisms such as timers, and administration topics such as cold start and protocol negotiation. The profile-specific tests follow the call establishment and call release procedures defined in TS 101 885.

That means Annex A is the part to consult when you need to understand why a particular TP is allowed, forbidden or only meaningful for a certain command and role.

What terms does SIST-TS TS 101 889-2 V1.1.1:2004 define?

• IUT (Implementation Under Test) - The protocol implementation being tested for conformance.
• MG (Media Gateway) - One of the two roles covered by the test suite, representing the gateway side of the H.248 relationship.
• MGC (Media Gateway Controller) - The controller-side role covered by the test suite.
• TP (Test Purpose) - A non-formal test description that can be used as the basis for a formal test specification.
• TSS (Test Suite Structure) - The organized tree of protocol groups, procedure groups and test subgroups.
• BV (Valid Behaviour) - Tests where the messages exchanged are valid and correctly encoded.
• BI (Invalid Behaviour) - Tests where the implementation receives a syntactically invalid PDU.
• BO (Inopportune Behaviour) - Tests where the message is valid but not expected in the current state or exchange.

Who uses SIST-TS TS 101 889-2 V1.1.1:2004?

SIST-TS TS 101 889-2 V1.1.1:2004 is used by conformance test engineers, gateway developers, quality managers, and buyers who need to check whether an H.248.1 implementation follows the TIPHON profile. It is also useful in interoperability testing between equipment from different manufacturers, because the scope explicitly aims at improving the probability of interworking.

The document is relevant for:

• Media Gateway suppliers
• Media Gateway Controller suppliers
• Test labs preparing conformance tests
• Quality teams reviewing protocol coverage
• Procurement teams comparing gateway implementations

In practice, these users apply it when planning lab tests, creating test cases, checking protocol support, or confirming that a gateway behaves correctly under valid, invalid and unexpected signalling.

Which standards are used with SIST-TS TS 101 889-2 V1.1.1:2004?

SIST-TS TS 101 889-2 V1.1.1:2004 is used together with the following documents:

• ETSI TS 101 885 - Defines the TIPHON mapping of reference point N to the H.248/MEGACO protocol, which is the basis for the profile-specific test purposes.
• ETSI TS 101 889-1 - Provides the PICS proforma specification used to derive and select the test purposes.
• ITU-T Recommendation H.248.1 - Supplies the gateway control protocol being tested.
• ISO/IEC 9646-1 - Provides the general concepts for conformance testing methodology and framework.
• ISO/IEC 9646-2 - Provides the Abstract Test Suite specification framework.
• ISO/IEC 9646-3 - Provides the Tree and Tabular Combined Notation used for formal test specification.
• ETSI ETS 300 406 - Provides ETSI conformance testing methodology rules.

What does the SIST-TS TS 101 889-2 V1.1.1:2004 document contain?

SIST-TS TS 101 889-2 V1.1.1:2004 contains a structured catalogue of test purposes for MG and MGC behaviour. It covers generic H.248.1 command handling, transport behaviour, administration and maintenance, and TIPHON profile-specific procedures for the N2 and N3 interfaces.

The document also gives the TP naming convention, the common TP text structure, and the test strategy used to derive the test purposes from the base standard and the PICS. That makes it useful both as a human-readable conformance outline and as a starting point for formal test case development.

Annex A is especially important because it explains wildcard usage for Context Ids and Termination Ids and maps allowed or forbidden combinations to the relevant valid or invalid test purposes. For labs, that annex is what links the abstract protocol rules to concrete test selection.

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 - 2. del:
Specifikacija zgradbe preskušalnega niza in namenov preskušanja (TSS&TP)
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
Ta slovenski standard je istoveten z: TS 101 889-2 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 IUT-T H.248;
Part 2: Test Suite Structure and
Test Purposes (TSS&TP) specification

2 ETSI TS 101 889-2 V1.1.1 (2002-08)

Reference
DTS/TIPHON-06017-2
Keywords
H.248, IP, telephony, testing, TSS&TP, 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 2002.
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-2 V1.1.1 (2002-08)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Test Suite Structure (TSS).9
4.1 Test groups.9
4.1.1 Protocol groups.9
4.1.2 Media Gateway (MG).9
4.1.2.1 Media Gateway Controller (MGC) .10
4.1.3 Main test groups.10
4.1.3.1 Valid Behaviour (BV) tests.10
4.1.3.2 Invalid Behaviour (BI) tests .10
4.1.3.3 Inopportune Behaviour (BO) tests .10
5 Test Purposes (TP).11
5.1 Introduction.11
5.1.1 TP naming convention.11
5.1.2 TP structure.12
5.1.3 Test strategy.12
5.1.4 Textual conventions within the Test Purposes.12
5.1.5 TPs for Media Gateway (MG) Procedures using Add command (AD) .13
5.1.5.1 Valid behaviour test purposes (BV).13
5.1.5.2 Invalid behaviour test purposes (BI) .15
5.1.5.3 Inopportune behaviour test purposes (BO) .17
5.1.6 Procedures using Modify command (MD) .17
5.1.6.1 Valid behaviour test purposes (BV).17
5.1.6.2 Invalid behaviour test purposes (BI) .19
5.1.6.3 Inopportune behaviour test purposes (BO) .21
5.1.7 Procedures using Subtract command (SU) .22
5.1.7.1 Valid behaviour test purposes (BV).22
5.1.7.2 Invalid behaviour test purposes (BI) .23
5.1.7.3 Inopportune behaviour test purposes (BO) .26
5.1.8 Procedures using Move command (MO).27
5.1.8.1 Valid behaviour test purposes (BV).27
5.1.8.2 Invalid behaviour test purposes (BI) .28
5.1.8.3 Inopportune behaviour test purposes (BO) .30
5.1.9 Procedures using Audit Value command (AV) .31
5.1.9.1 Valid behaviour test purposes (BV).31
5.1.9.2 Invalid behaviour test purposes (BI) .33
5.1.9.3 Inopportune behaviour test purposes (BO) .35
5.1.10 Procedures using Audit Capabilities command (AC) .35
5.1.10.1 Valid behaviour test purposes (BV).35
5.1.10.2 Invalid behaviour test purposes (BI) .38
5.1.10.3 Inopportune behaviour test purposes (BO) .40
5.1.11 Procedures using Notify command (NO).40
5.1.11.1 Valid behaviour test purposes (BV).40
5.1.11.2 Invalid behaviour test purposes (BI) .40
5.1.11.3 Inopportune behaviour test purposes (BO) .40
5.1.12 Procedures using Service Change command (SC).41
5.1.12.1 Valid behaviour test purposes (BV).41
5.1.12.2 Invalid behaviour test purposes (BI) .44
ETSI
4 ETSI TS 101 889-2 V1.1.1 (2002-08)
5.1.12.3 Inopportune behaviour test purposes (BO) .44
5.1.13 Administration and Maintenance procedures (AM) .44
5.1.13.1 Valid behaviour test purposes (BV).44
5.1.13.2 Invalid behaviour test purposes (BI) .46
5.1.13.3 Inopportune behaviour test purposes (BO) .47
5.1.14 Transport related procedures (TR).47
5.1.14.1 Valid behaviour test purposes (BV).47
5.1.14.2 Invalid behaviour test purposes (BI) .48
5.1.14.3 Inopportune behaviour test purposes (BO) .48
5.1.15 clause E.2 Base Root Package procedures.48
5.1.15.1 Valid behaviour test purposes (BV).48
5.1.15.2 Invalid behaviour test purposes (BI) .48
5.1.15.3 Inopportune behaviour test purposes (BO) .48
5.1.16 clause E.11 Network Package procedures .49
5.1.16.1 Valid behaviour test purposes (BV).49
5.1.16.2 Invalid behaviour test purposes (BI) .49
5.1.16.3 Inopportune behaviour test purposes (BO) .49
5.1.17 clause E.13 TDM Circuit Package procedures .49
5.1.17.1 Valid behaviour test purposes (BV).49
5.1.17.2 Invalid behaviour test purposes (BI) .49
5.1.17.3 Inopportune behaviour test purposes (BO) .50
5.1.18 TIPHON profile procedures for N2 interface .50
5.1.18.1 Valid behaviour test purposes (BV).50
5.1.18.2 Invalid behaviour test purposes (BI) .56
5.1.18.3 Inopportune behaviour test purposes (BO) .56
5.1.19 TIPHON profile procedures for N3 interface .57
5.1.19.1 Valid behaviour test purposes (BV).57
5.1.19.2 Invalid behaviour test purposes (BI) .60
5.1.19.3 Inopportune behaviour test purposes (BO) .60
5.2 TPs for Media Gateway Controller (MGC).61
5.2.1 Procedures using Add command (AD) .61
5.2.1.1 Valid behaviour test purposes (BV).61
5.2.1.2 Invalid behaviour test purposes (BI) .62
5.2.1.3 Inopportune behaviour test purposes (BO) .62
5.2.2 Procedures using Modify command (MD) .62
5.2.2.1 Valid behaviour test purposes (BV).62
5.2.2.2 Invalid behaviour test purposes (BI) .63
5.2.2.3 Inopportune behaviour test purposes (BO) .63
5.2.3 Procedures using Subtract command (SU) .63
5.2.3.1 Valid behaviour test purposes (BV).63
5.2.3.2 Invalid behaviour test purposes (BI) .64
5.2.3.3 Inopportune behaviour test purposes (BO) .64
5.2.4 Procedures using Move command (MO).64
5.2.4.1 Valid behaviour test purposes (BV).64
5.2.4.2 Invalid behaviour test purposes (BI) .65
5.2.4.3 Inopportune behaviour test purposes (BO) .65
5.2.5 Procedures using Audit Value command (AV) .65
5.2.5.1 Valid behaviour test purposes (BV).65
5.2.5.2 Invalid behaviour test purposes (BI) .67
5.2.5.3 Inopportune behaviour test purposes (BO) .67
5.2.6 Procedures using Audit Capabilities command (AC) .67
5.2.6.1 Valid behaviour test purposes (BV).67
5.2.6.2 Invalid behaviour test purposes (BI) .68
5.2.6.3 Inopportune behaviour test purposes (BO) .68
5.2.7 Procedures using Notify command (NO).69
5.2.7.1 Valid behaviour test purposes (BV).69
5.2.7.2 Invalid behaviour test purposes (BI) .70
5.2.7.3 Inopportune behaviour test purposes (BO) .73
5.2.8 Procedures using Service Change command (SC).73
5.2.8.1 Valid behaviour test purposes (BV).73
5.2.8.2 Invalid behaviour test purposes (BI) .78
5.2.8.3 Inopportune behaviour test purposes (BO) .81
ETSI
5 ETSI TS 101 889-2 V1.1.1 (2002-08)
5.2.9 Administration and Maintenance procedures (AM) .81
5.2.9.1 Valid behaviour test purposes (BV).81
5.2.9.2 Invalid behaviour test purposes (BI) .84
5.2.9.3 Inopportune behaviour test purposes (BO) .84
5.2.10 Transport related procedures (TR).84
5.2.10.1 Valid behaviour test purposes (BV).84
5.2.10.2 Invalid behaviour test purposes (BI) .85
5.2.10.3 Inopportune behaviour test purposes (BO) .85
5.2.11 TIPHON profile procedures for N2 interface .86
5.2.11.1 Valid behaviour test purposes (BV).86
5.2.11.2 Invalid behaviour test purposes (BI) .89
5.2.11.3 Inopportune behaviour test purposes (BO) .89
5.2.12 TIPHON profile procedures for N3 interface .90
5.2.12.1 Valid behaviour test purposes (BV).90
5.2.12.2 Invalid behaviour test purposes (BI) .92
5.2.12.3 Inopportune behaviour test purposes (BO) .92
Annex A (normative): Remarks to the H.248.1 Test Purposes (TPs).93
A.1 General Remarks.93
A.2 Wildcard matrix of Context Ids and Termination Ids .93
History .99

ETSI
6 ETSI TS 101 889-2 V1.1.1 (2002-08)
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 2 of a multi-part deliverable covering Conformance Testing for TIPHON Release 3;
TIPHON profile for ITU-T Recommendation H.248.1 [3], 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
7 ETSI TS 101 889-2 V1.1.1 (2002-08)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the TIPHON mapping to
H248 protocol as defined in TS 101 885 [1].
The objective of the present document is to provide conformance tests for TIPHON profile for ITU-T Recommendation
H.248.1 equipment giving a greater probability of inter-operability between different manufacturer's TIPHON profile
for ITU-T Recommendation H.248.1 equipments.
ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5] and
ISO/IEC 9646-3 [6]) as well as the ETSI rules for conformance testing (ETS 300 406 [7]) are used as basis for the test
methodology.
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 885 (V1.1.1): "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 (V1.1.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] ITU-T Recommendation H.248.1 (02/2002): "Gateway control protocol: Version 1".
[4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[5] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[6] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation".
[7] ETSI ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
ETSI
8 ETSI TS 101 889-2 V1.1.1 (2002-08)
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.1 [3];
• terms defined in ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5] and ISO/IEC 9646-3 [6].
inopportune: specifies a test purpose covering a signalling procedure where an inopportune message (type of message
not expected in the IUT current state) is sent to the IUT
syntactically invalid: specifies a test purpose covering a signalling procedure where a valid (expected in the current
status of the IUT) but not correctly encoded (unknown or incorrect parameter values) message is sent to the IUT, which
shall react correctly and eventually reject the message
Test Purpose: non-formal test description, mainly using text. This test description can be used as the basis for a formal
test specification (e.g. Abstract Test Suite in TTCN)
NOTE: See ISO/IEC 9646-3 [6].
valid: specifies a test purpose covering a signalling procedure where all the messages sent to or received from the IUT
are valid (expected in the current status of the IUT) and correctly encoded
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
CID Context Id
IUT Implementation Under Test
MG Media Gateway
MGC Media Gateway Controller
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PDU Protocol Data Unit
TID Termination Id
TP Test Purpose
TSS Test Suite Structure
ETSI
9 ETSI TS 101 889-2 V1.1.1 (2002-08)
4 Test Suite Structure (TSS)
Figure 1 shows the H.248.1 Test Suite Structure (TSS) including its subgroups defined for the conformance testing.
Test Suite Protocol group Protocol subgroup Test group
H248 Media Gateway (MG) Procedures using Add command (AD) BV - BI - BO
Procedures using Modify command (MD) BV - BI - BO
Procedures using Subtract command (SU) BV - BI - BO
Procedures using Move command (MO) BV - BI - BO
Procedures using Audit Value command (AV) BV - BI - BO
Procedures using Audit Capabilities command (AC) BV - BI - BO
Procedures using Notify command (NO) BV - BI - BO
Procedures using Service Change command (SC) BV - BI - BO
Administration and Maintenance procedures (AM) BV - BI - BO
Transport related procedures (TR) BV - BI - BO
clause E.2 Base Root Package procedures BV - BI - BO
clause E.11 Network Package procedures BV - BI - BO
clause E.13 TDM Circuit Package procedures BV - BI - BO
TIPHON profile procedures for TIPHON N2 interface (TN2) BV - BI - BO
TIPHON profile procedures for TIPHON N3 interface (TN3) BV - BI - BO
Media Gateway Controller Procedures using Add command (AD) BV - BI - BO
(MGC)
Procedures using Modify command (MD) BV - BI - BO
Procedures using Subtract command (SU) BV - BI - BO
Procedures using Move command (MO) BV - BI - BO
Procedures using Audit Value command (AV) BV - BI - BO
Procedures using Audit Capabilities command (AC) BV - BI - BO
Procedures using Notify command (NO) BV - BI - BO
Procedures using Service Change command (SC) BV - BI - BO
Administration and Maintenance procedures (AM) BV - BI - BO
Transport related procedures (TR) BV - BI - BO
TIPHON profile procedures for TIPHON N2 interface (TN2) BV - BI - BO
TIPHON profile procedures for TIPHON N3 interface (TN3) BV - BI - BO

Figure 1: TSS of TIPHON profile for H.248.1
The Test Suite is structured as a tree with a first level defined as H.248.1 representing the protocol group: "TIPHON
profile for H.248.1".
4.1 Test groups
The test groups are organized in three levels. The first level creates two protocol groups representing the role of the
IUT. The second level separates the selected role for the IUT in groups of procedures. The last level in each branch
contains one or more of the standard ISO subgroups BV, BI, BO.
4.1.1 Protocol groups
The protocol groups identify the two roles of the IUT: Media Gateway (MG) and Media Gateway Controller (MGC) as
defined in ITU-T Recommendation H.248.1 [3].
4.1.2 Media Gateway (MG)
The Media Gateway protocol group is divided in 15 groups of procedures. The first eight groups identify the procedures
using different commands as defined in clause 7 of ITU-T Recommendation H.248.1 [3]. The ninth group of procedures
identifies the Administration and Maintenance procedures (e.g.: cold start procedure and procedures against restart
avalanche). The tenth group of procedures distinguishes the procedures related to transport of H.248.1 messages.
Groups 11 to 13 distinguish the procedures for H.248.1 basic packages, group 14 and group 15 identify TIPHON profile
specific procedures.
ETSI
10 ETSI TS 101 889-2 V1.1.1 (2002-08)
4.1.2.1 Media Gateway Controller (MGC)
The Media Gateway protocol group is divided in ten groups of procedures. The first eight groups identify the
procedures using different commands as defined in clause 7. Of ITU-T Recommendation H.248.1 [3]. The ninth group
of procedures identifies the Administration and Maintenance procedures (e.g.: Service changes procedures). The tenth
group of procedures distinguishes the procedures related to transport of H.248.1 messages. Group 11 and group 12
identify TIPHON profile specific procedures.
4.1.3 Main test groups
The main test groups are the valid behaviour group, the invalid behaviour group and the inopportune behaviour group.
4.1.3.1 Valid Behaviour (BV) tests
This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt or exchange of valid Protocol
Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged messages are
considered as valid.
4.1.3.2 Invalid Behaviour (BI) tests
This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt of a syntactically invalid
PDU.
4.1.3.3 Inopportune Behaviour (BO) tests
This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt of a syntactically correct
PDU not expected in the actual message exchange or state.
ETSI
11 ETSI TS 101 889-2 V1.1.1 (2002-08)
5 Test Purposes (TP)
5.1 Introduction
5.1.1 TP naming convention
Table 1: TP identifier naming convention scheme
Identifier: TP///-
= type of IUT MG Media Gateway
MGC Media Gateway Controller
= group of procedures AD Procedures using Add command
MD Procedures using Modify command
SU Procedures using Subtract command
MO Procedures using Move command
AV Procedures using Audit Value command
AC Procedures using Audit Capabilities command
NO Procedures using Notify command
SC Procedures using Service Change command
AM Administration and Maintenance procedures
TR Transport related procedures
E2 clause E.2 Base Root Packages procedures
E11 clause E.11 Network Packages procedures
E13 clause E.12 TDM Circuit Package procedures
TN2 TIPHON profile procedures for N2 interface
TN3 TIPHON profile procedures for N3 interface
= type of testing BV Valid Behaviour Tests
BI Invalid Behaviour Tests
BO Inopportune Behaviour Tests
= sequential number (01-99) Test Purpose Number

ETSI
12 ETSI TS 101 889-2 V1.1.1 (2002-08)
5.1.2 TP structure
Each TP has been written in a manner, which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. use a TP as an example to fully understand the table.
Table 2: Structure of a single TP for H.248
TP part Text Example
tab
Header
 clause 0.0.0
Stimulus Ensure that the IUT
in the idle state
having sent a XXX message
see below for message structure on receipt of a YYY message
or
to request a .
Reaction  sends, does, etc.
 .
if the action is sending
see below for message structure
, etc.
Message
structure message containing a
a) TerminalType, statusDetermination
b) or Number.
encoded as or including
and back to a or b,
NOTE: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one
TP to the next.
5.1.3 Test strategy
As the base standard ITU-T Recommendation H.248.1 [3] contains no explicit requirements for testing, the TPs were
generated as a result of an analysis of the base standard and the corresponding PICS proforma.
The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, over
the TCP or UDP interface, and are limited to conceivable situations to which a real implementation is likely to be faced.
As indicated by the existence of the part 3 of this multi-part standard (see Foreword), the intention is to derive the test
purposes to an abstract test suite in TTCN. Consequently the test purposes are written in a manner, which fit the TTCN
methodology, and will consist of the textual documentation of the test cases.
All PICS items referred to in this clause are specified in TS 101 889-1 [2].
Unless specified otherwise, the messages indicated are valid and contain at least the mandatory parameters and possibly
optional parameters.
5.1.4 Textual conventions within the Test Purposes
According to the ALL wildcard for TerminationIDs the following abbreviation conventions are used:
• ALL(p12) means a wildcard ALL which addresses only the physical Termination TID1 and TID2 as given in the
initial conditions.
• ALL(e1234) means a wildcard ALL which addresses only the ephemeral Terminations TID1, TID2, TID3 and
TID4 as given in the initial conditions.
The wildcard CHOOSE for the TerminationID can be used either for creating a complete new (ephemeral) Termination
or to select/choose a physical Termination within a range of already existing physical TerminationIDs in the Null
Context.
ETSI
13 ETSI TS 101 889-2 V1.1.1 (2002-08)
If wildcard combinations for the ContextID and TerminationID are used in the TPs that are not allowed from protocol
point of view an Error Descriptor shall be returned. The Error Descriptor should have an appropriate error value
(e.g. 401, protocol error).
5.1.5 TPs for Media Gateway (MG) Procedures using Add command (AD)
5.1.5.1 Valid behaviour test purposes (BV)
TP/MG/AD/BV-01 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: any
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CHOOSE
o ADD Command request with
TID set to CHOOSE
acceptable descriptors
(note: e.g. for creation of a RTP Termination)
sends a Transaction Reply containing
• Action reply with
o CID set to a specific value (assigned by the MG)
o ADD Command reply with
TID set to a specific value (assigned by the MG).
TP/MG/AD/BV-02 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: a physical Termination, characterized by TID1, in the NULL Context,
The physical Termination TID1 shall NOT be in serviceState "outOfService".
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CHOOSE
o ADD Command request with
TID set to TID1
acceptable descriptors
sends a Transaction Reply containing
• Action reply with
o CID set to a specific value (assigned by the MG)
o ADD Command reply with
TID set to TID1.
TP/MG/AD/BV-03 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: 2 physical Terminations, characterized by TID1 and TID2, each of
them in the NULL Context. The physical Terminations TID1 and TID2 shall NOT be in
serviceState "outOfService".
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CHOOSE
o ADD Command request with
TID set to ALL(p12)
acceptable descriptors
sends a Transaction Reply containing
• Action reply with
o CID set to a specific value (assigned by the MG)
o ADD Command reply with
TID set to TID1
o ADD Command
TID set to TID2.
ETSI
14 ETSI TS 101 889-2 V1.1.1 (2002-08)
TP/MG/AD/BV-04 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: a Termination characterized by TID1 in a Context, characterized by
CID1.
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CID1
o ADD Command request with
TID set to CHOOSE
acceptable descriptors
(note: e.g. for creation of a RTP Termination)
sends a Transaction Reply containing
• Action reply with
o CID set to CID1
o ADD Command reply with
TID set to a specific value (assigned by the MG).
TP/MG/AD/BV-05 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: 2 physical Terminations, characterized by TID1 and TID2, each of
them in the NULL Context and a Termination (TID3) in a Context CID1. The physical
Terminations TID1 and TID2 shall NOT be in serviceState "outOfService".
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CID1
o ADD Command request with
TID set to ALL(p12)
acceptable descriptors
sends a Transaction Reply containing
• Action reply with
o CID set to CID1
o ADD Command reply with
TID set to TID1
o ADD Command reply with
TID set to TID2.
TP/MG/AD/BV-06 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: a physical Termination, characterized by TID1, in the NULL Context
and a Termination (TID2) in a Context CID1. The physical Terminations TID1 and TID2
shall NOT be in serviceState "outOfService".
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CID1
o ADD Command request with
TID set to TID1
acceptable descriptors
sends a Transaction Reply containing
• Action reply with
o CID set to CID1
o ADD Command reply with
TID set to TID1.
ETSI
15 ETSI TS 101 889-2 V1.1.1 (2002-08)
TP/MG/AD/BV-07 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: 2 Terminations (TID1 and TID2) each in a Context, characterized by
CID1 and CID2 (NULL Context is excluded).
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to ALL
o ADD Command request with
TID set to CHOOSE
acceptable descriptors
sends a Transaction Reply containing
• Action reply with
o CID set to CID1
o ADD Command reply with
TID set to TID3
• Action reply with
o CID set to CID2
o ADD Command reply with
TID set to TID4
5.1.5.2 Invalid behaviour test purposes (BI)
TP/MG/AD/BI-01 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria: ROOT termination implemented
Initial condition: any
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CHOOSE
o ADD Command request with
TID set to ROOT
sends a Transaction Reply containing
• Action reply with
o CID set to CHOOSE
o ADD Command reply with
TID set to ROOT
Error descriptor (e.g. value 401 "Protocol Error")
TP/MG/AD/BI-02 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: a Termination (TID1) in a Context, characterized by CID1.
Ensure that the IUT, on receipt of a Transaction Request containing
• Action request with
o CID set to CID1
o ADD Command request with
TID set to ROOT
sends a Transaction Reply containing
• Action reply with
o CID set to CID1
o ADD Command reply with
TID set to ROOT
Error descriptor (e.g. value 401 "Protocol Error")
TP/MG/AD/BI-03 Reference: ITU-T Recommendation H.248.1 [3] clause 7.2.1
Selection criteria:
Initial condition: 2 Terminations (TID1 and TID2) each in a Context, c
...