ETSI TS 102 374-2-2004 Methods for Testing and Specification (MTS) Conformance Test Specification for ITU-T H 248 1 Part 2 Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《.pdf

《ETSI TS 102 374-2-2004 Methods for Testing and Specification (MTS) Conformance Test Specification for ITU-T H 248 1 Part 2 Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 374-2-2004 Methods for Testing and Specification (MTS) Conformance Test Specification for ITU-T H 248 1 Part 2 Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)《.pdf（77页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 374-2 V1.1.1 (2004-11)Technical Specification Methods for Testing and Specification (MTS);Conformance Test Specification for ITU-T H.248.1;Part 2: Test Suite Structure andTest Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which i

2、s 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 re

3、ferenced 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 Technical Committee Methods for Testing and Specification (MTS). The present document is pa

4、rt 2 of a multi-part deliverable covering Conformance Testing Specification for ITU-T H.248.1, as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS) proforma“; Part 2: “Test Suite Structure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS) and partial Protocol Im

5、plementation eXtra Information for Testing (PIXIT) proforma“. ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 6 1 Scope The present document specifies the Test Suite Structure and Test Purposes (TSS Conformance Test Specification for ITU-T H.248.1; Part 1: Protocol Implementation Conformance Statement (PICS

6、) proforma“. 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: Abstra

7、ct 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 (TTCN)“. 7 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conf

8、ormance testing specifications; Standardization methodology“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ITU-T Recommendation H.248.1 1, ISO/IEC 9646-1 4, ISO/IEC 9646-2 5, ISO/IEC 9646-3 6 and the following apply: ino

9、pportune: 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 ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 7 syntactically invalid: specifies a test purpose covering a signalling procedure where a

10、 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 (TP): non-formal test description, mainly using text NOTE 1: This test descripti

11、on can be used as the basis for a formal test specification (e.g. Abstract Test Suite in TTCN). NOTE 2: 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)

12、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 PDU Protocol Data Unit PICS Protocol Implementation Conformance Stat

13、ement PIXIT Protocol Implementation eXtra Information for Testing TID Termination IDTP Test Purpose TSS Test Suite Structure 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 Proto

14、col subgroup Test group H248.1 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 - B

15、O 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 Media Gateway Control

16、ler (MGC) 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 co

17、mmand (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 Figure 1: TSS of H.248.1 The Test Suite is structured as a tr

18、ee with a first level defined as H.248.1 representing the protocol group: “H.248.1“. ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 8 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 s

19、elected 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 Recomm

20、endation H.248.1 1. 4.1.1.1 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 1. The ninth group of procedures identifies the Admini

21、stration 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, and groups 11 to 13 distinguish the procedures for H.248.1 basic packages. 4.1.1.2 Media Gat

22、eway 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 1. The ninth group of procedures identifies the Administration and Maintenanc

23、e procedures (e.g. Service changes procedures). The tenth group of procedures distinguishes the procedures related to transport of H.248.1 messages. 4.1.2 Main test groups The main test groups are the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. 4.1.2.1 Val

24、id 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.2.2 Invalid Beh

25、aviour (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.2.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 co

26、rrect PDU not expected in the actual message exchange or state. ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 9 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 = gr

27、oup 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 Ser

28、vice Change command AM Administration and Maintenance procedures TR Transport related procedures = type of testing BV Valid Behaviour Tests BI Invalid Behaviour Tests BO Inopportune Behaviour Tests = sequential number (01-99) Test Purpose Number 5.1.2 TP structure Each TP has been written in a manne

29、r, 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. T

30、able 2: Structure of a single TP for H.248.1 TP part Text Example Header tab 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 b

31、elow for message structure , etc. Message structure message containing a a) b) or encoded as or including and back to a or b, TerminalType, statusDetermination Number. 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. ETSI

32、ETSI TS 102 374-2 V1.1.1 (2004-11) 105.1.3 Test strategy As the base standard ITU-T Recommendation H.248.1 1 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 conformanc

33、e 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 intenti

34、on 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 102 374-1 3. Unl

35、ess 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) mean

36、s 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

37、 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. If wildcard combinations for the ContextID and TerminationID are used in the TPs that are not allowed from pr

38、otocol point of view an Error Descriptor shall be returned. The Error Descriptor should have an appropriate error value (e.g. 401, protocol error). 5.2 TPs for Media Gateway (MG) 5.2.1 Procedures using Add command (AD) 5.2.1.1 Valid behaviour test purposes (BV) TP/MG/AD/BV-01 Reference: ITU-T Recomm

39、endation H.248.1 1, 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: square4 TID set to CHOOSE; square4 acceptable descriptors. NOTE: e.g. for creation of

40、 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: square4 TID set to a specific value (assigned by the MG). ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 11TP/MG/AD/BV-02 Reference: ITU-T Recommendatio

41、n H.248.1 1, 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

42、CID set to CHOOSE; o ADD Command request with: square4 TID set to TID1; square4 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: square4 TID set to TID1. TP/MG/AD/BV-03 Reference: ITU-T Recom

43、mendation H.248.1 1, 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 Re

44、quest containing: Action request with: o CID set to CHOOSE; o ADD Command request with: square4 TID set to ALL(p12); square4 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: square4 TID set

45、to TID1; o ADD Command: square4 TID set to TID2. TP/MG/AD/BV-04 Reference: ITU-T Recommendation H.248.1 1, 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:

46、 Action request with: o CID set to CID1; o ADD Command request with: square4 TID set to CHOOSE; square4 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: square4 TID set to a spe

47、cific value (assigned by the MG). TP/MG/AD/BV-05 Reference: ITU-T Recommendation H.248.1 1, 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 Terminati

48、ons 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: square4 TID set to ALL(p12); square4 acceptable descriptors. Sends a Transaction Reply containing: A

49、ction reply with: o CID set to CID1; o ADD Command reply with: square4 TID set to TID1; o ADD Command reply with: square4 TID set to TID2. ETSI ETSI TS 102 374-2 V1.1.1 (2004-11) 12TP/MG/AD/BV-06 Reference: ITU-T Recommendation H.248.1 1, 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 Transact