ETSI TS 102 381-2004 Methods for Testing and Specification (MTS) SS7 Message Transfer Part 3 - User Adaptation Layer (IETF RFC 3332) Test Suite Structure and Test Purposes (TSS&TP)_1.pdf

1、 ETSI TS 102 381 V1.1.1 (2004-12)Technical Specification Methods for Testing and Specification (MTS);SS7 Message Transfer Part 3 - User Adaptation Layer;(IETF RFC 3332);Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards

2、“, 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 I

3、PRs 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 Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI TS 102

4、 381 V1.1.1 (2004-12) 5 1 Scope The present document proposes a Test Suite Structure and Test Purposes (TSS MTP/SCCP/SSCOP and SIGTRAN (Message of SS7 over IP); 3332 (2002) modified“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions

5、given in M3UA RFC 3332 1, ISO/IEC 9646-1 2, -2 3, -3 4 and the following apply. inOpportune: tests that handle invalid signalling exchanges of messages, i.e. signalling messages that are properly structured and correctly encoded but are used out of sequence invalid: tests that handle valid signallin

6、g exchanges of messages, which are either not properly structured or incorrectly encoded Test Purpose (TP): non-formal high-level description of a test, mainly using text. NOTE: This test description can be used as the basis for a formal test specification (e.g. Abstract Test Suite in TTCN). See ISO

7、/IEC 9646-2 and ISO/IEC 9646-3. valid: tests that handle valid signalling exchanges of messages, which are properly structured and correctly encoded ETSI ETSI TS 102 381 V1.1.1 (2004-12) 6 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Application S

8、erver ASP Application Server Process ASPM ASP Maintenance Procedures ASPSM Application Server Process State Maintenance ASPTM Application Server Process Traffic Maintenance ATS Abstract Test Suite I Invalid IUT Implementation Under Test MSG MeSsaGing MTR Message Transfer O InOpportunePICS Protocol I

9、mplementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing RKM Routing Key Management SCTP Stream Control Transmission Protocol SG Signalling Gateway SGP Signalling Gateway Process SSNM SS7 Signalling Network Management SUT System Under Test TSS Test Suite Struct

10、ure V Valid 4 Test Suite Structure (TSS) 4.1 Introduction 4.1.1 M3UA entities Test Purposes have been written for M3UA Peers according to the M3UA RFC 3332 1. Two kinds of entities are considered successively as IUT: - Signalling Gateway Process. - Application Server Process. SGP MTP-3 M3UA MTP2 SCT

11、P L1 IP NIF ASP M3UA SCTP IP ISUP IP Figure 1: M3UA protocol entities ETSI ETSI TS 102 381 V1.1.1 (2004-12) 7 To enable the verification of certain aspects of the protocol, certain test purposes will require the use of multiple ASPs within an AS. 4.1.2 General assumptions Test Purposes have been wri

12、tten for behaviours requested with “MUST“ or that appear as obvious in present form. In addition test purposes have been defined for implementation dependent behaviour, where at least one of the implementation options is mandatory. The listed features below are not covered by the present document. R

13、easons are described along with their description: - Registration Status 1 “Error-Unknown“: No statement in RFC 3332 1 clearly outlines its use or applications. - Deregistration Status 1 “Error-Unknown“: No statement in RFC 3332 1 clearly outlines its use or applications. - Deregistration Status 2 “

14、Error-Invalid Routing Context“: No statement in RFC 3332 1 clearly outlines its use or applications. A more complete set of torture tests for both ASPs and SGPs shall be provided. 4.1.3 System Under Test In SIGTRAN M3UA, one or more ASP can be contained within an ASP; furthermore, one or more SGP ca

15、n be contained within an SGP. ASPs and SGPs can be interconnected so that full redundancy is provided. Several scenarios have been envisioned in the present document: - One ASP within the AS. - Several ASPs within the ASP. - One ASP connected to one SGP. - Several ASPs connected to one SGP. 4.2 Over

16、view of the Test Suite Structure The Test Suite Structures is based on the main functionalities as defined above. Figure 2 shows the Test Suite Structure. Last Sub groups may be subdivided in three subgroups: Valid behaviour (V), Invalid behaviour (I), inOpportune behaviour (O). Test Suite Main Func

17、tionalities Functionality Subgroup Test Group M3UA SGP ASP State Maintenance V-I-O ASP Traffic Maintenance V-I-O Message Transfer V-I Routing Key Management V-I ASP ASP State Maintenance V-I-O ASP Traffic Maintenance V-I-O Message Transfer V-I Routing Key Management V-I Figure 2: TSS for M3UA5 ETSI

18、ETSI TS 102 381 V1.1.1 (2004-12) 8 5 Test Purposes (TP) 5.1 Introduction 5.1.1 TP naming convention Table 1: TP identifier naming convention scheme Identifier: _ M3UA SGP (Signalling Gateway Process) ASP (Application Server Process) ASPM (ASP Maintenance procedures) RKM (Routing Key Management) MSG

19、(MeSsaGing) Valid behaviour (V) Invalid behaviour (I), inOpportune behaviour (O). sequential number (01 to 99). 5.1.2 TP structure Each test purpose is decomposed in six keywords: - The TPId gives a unique identifier to each test purpose. - The Status specifies whether the test purpose or the group

20、is mandatory or optional according to RFC 3332 1. - The Group Status applies to all test purposes belonging to this group. Within the present document only test purposes that are mandatory have been defined. - The Precondition determines the initial state of the SUT for the evaluating the test purpo

21、se. - The Reference outlines the references in RFC 3332 1 used to create the test purpose. - The Purpose describes the objective of the test. ETSI ETSI TS 102 381 V1.1.1 (2004-12) 9 5.2 Test Purposes for Signalling Gateway Process (SGP) 5.2.1 ASP State Maintenance Procedures 5.2.1.1 Valid behaviour

22、TPId M3UA_SGP_ASPSM_V_001 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-DOWN at the SGP Reference Section 4.3.1 1 Section 4.3.4.1 1 Purpose Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack.

23、Comments This test case, even though included in M3UA_SGP_ASPSM_v_003 validates the response with an ASP Up Ack regardless of the number of ASPs configured in the AS. TPId M3UA_SGP_ASPSM_V_003 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP One AS

24、P configured within the AS ASP marked as ASP-DOWN at the SGP Reference Section 3.8.2 1 Section 4.3.1 1 Section 4.3.2 1 Section 4.3.4.1 1 Section 4.3.4.5 1 Purpose Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack and sends a NOTIFY message indicating the AS state

25、change to AS-INACTIVE Comments TPId M3UA_SGP_ASPSM_V_005 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-INACTIVE at the SGP Reference Section 4.3.1 1 Section 4.3.4.2 1 Purpose Ensure that the IUT, upon reception of an ASP Down m

26、essage, responds with an ASP Down Ack. Comments This test case, even though included in M3UA_SGP_ASPSM_v_007 validates the response with an ASP Down Ack regardless of the number of ASPs configured in the AS. TPId M3UA_SGP_ASPSM_V_009 Status Optional Pre-condition Successfully established SCTP associ

27、ation between the SGP and the ASP ASP marked as blocked at the SGP Reference Section 3.8.1 1 Section 4.3.4.1 1 Purpose Ensure that the IUT, upon reception of an ASP Up message sent by an ASP marked as blocked at the SGP, responds with an ERROR message with reason 0x0d “Refused-Management Blocking“ C

28、omments ETSI ETSI TS 102 381 V1.1.1 (2004-12) 105.2.1.2 Invalid behaviour TPId M3UA_SGP_ASPSM_I_001 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP Reference Section 3.1.11 Section 3.8.1 1 Section 4.3.4.1.1 1 Purpose Ensure that the IUT, upon rece

29、ption of an ASP Up message that contains an invalid M3UA version (e.g. 2), responds with an ERROR message with reason 0x01 (“Invalid Version“) Comments TPId M3UA_SGP_ASPSM_I_002 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-DOW

30、N at the SGP Reference Section 3.1.2 1 Section 3.8.1 1 Section 4.3.2 1 Purpose Ensure that the IUT, upon reception of a message which class is 3 (ASPSM) and type is different from 0 (Reserved) 1 (ASP Up), 2 (ASP Down), 3 (BEAT), 4 (ASP Up Ack), 5 (ASP Down Ack) and 6 (BEAT Ack) responds with an ERRO

31、R message with reason 0x04 “Unsupported Message Type“ Comments TPId M3UA_SGP_ASPSM_I_003 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-DOWN at the SGP Reference Section 3.1.2 1 Section 3.8.1 1 Section 4.3.2 1 Purpose Ensure tha

32、t the IUT, upon reception of a message which class is 4 (ASPTM) responds with an ERROR message with reason 0x06 “Unexpected Message“ or silently discards the message. Comments TPId M3UA_SGP_ASPSM_I_004 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the A

33、SP ASP marked as ASP-INACTIVE at the SGP Reference Section 3.1.2 1 Section 3.8.1 1 Section 4.3.2 1 Purpose Ensure that the IUT, upon reception of a message which class is 3 (ASPSM) and type is different from 0 (Reserved) 1 (ASP Up), 2 (ASP Down), 3 (BEAT), 4 (ASP Up Ack), 5 (ASP Down Ack) and 6 (BEA

34、T Ack) responds with an ERROR message with reason 0x04 “Unsupported Message Type“ Comments 5.2.1.3 inOpportune behaviour TPId M3UA_SGP_ASPSM_O_001 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-INACTIVE at the SGP Reference Sect

35、ion 4.3.1 1 Section 4.3.4.1 1 Purpose Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack Comments ETSI ETSI TS 102 381 V1.1.1 (2004-12) 11TPId M3UA_SGP_ASPSM_O_003 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP

36、ASP marked as ASP-ACTIVE at the SGP One ASP in the AS Reference Section 3.8.1 1 Section 4.3.1 1 Section 4.3.4.1 1 Section 4.3.4.4 1 Purpose Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack, sends an ERROR message with reason 0x06 “Unexpected Message“ and sends a

37、NOTIFY message indicating the AS state change to AS-INACTIVE Comments TPId M3UA_SGP_ASPSM_O_004 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-DOWN at the SGP Reference Section 4.3.1 1 Section 4.3.4.2 1 Purpose Ensure that the I

38、UT, upon reception of an ASP Down message, responds with an ASP Down Ack Comments 5.2.2 ASP Traffic Maintenance procedures 5.2.2.1 Valid behaviour TPId M3UA_SGP_ASPTM_V_001 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-INACTIVE

39、 at the SGP Reference Section 4.3.1 1 Section 4.3.4.3 1 Purpose Ensure that the IUT, upon reception of an ASP Active message, responds with an ASP Active Ack Comments TPId M3UA_SGP_ASPTM_V_003 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP One AS

40、P configured in the AS ASP marked as ASP-INACTIVE at the SGP Reference Section 3.8.2 1 Section 4.3.1 1 Section 4.3.2 1 Section 4.3.4.3 1 Purpose Ensure that the IUT, upon reception of an ASP Active message, responds with an ASP Active Ack and sends a NOTIFY message indicating the AS state change to

41、AS-ACTIVE Comments TPId M3UA_SGP_ASPTM_V_005 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-INACTIVE at the SGP Reference Section 4.3.4.3 1 Purpose Ensure that the IUT, upon reception of an ASP Active message that contains a Rou

42、ting Context, responds with an ASP Active Ack that contains the Routing Context Comments ETSI ETSI TS 102 381 V1.1.1 (2004-12) 12TPId M3UA_SGP_ASPTM_V_006 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-ACTIVE at the SGP Referenc

43、e Section 4.3.1 1 Section 4.3.4.4 1 Purpose Ensure that the IUT, upon reception of an ASP Inactive message, responds with an ASP Inactive Ack Comments TPId M3UA_SGP_ASPTM_V_008 Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-ACTIVE at the SGP One

44、 ASP in the AS Reference Section 3.8.2 1 Section 4.3.1 1 Section 4.3.2 1 Section 4.3.4.4 1 Status Mandatory Purpose Ensure that the IUT, upon reception of an ASP Inactive message, responds with an ASP Inactive Ack and sends a NOTIFY message indicating the AS state change to AS-PENDING Comments TPId

45、M3UA_SGP_ASPTM_V_010 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-ACTIVE at the SGP Reference Section 4.3.4.6 1 Purpose Ensure that the IUT, upon reception of a Heartbeat message, responds with a Heartbeat Ack Comments TPId M3

46、UA_SGP_ASPTM_V_011 Status Mandatory Pre-condition Successfully established SCTP association between the SGP and the ASP ASP marked as ASP-ACTIVE at the SGP Reference Section 4.3.4.6 1 Purpose Ensure that the IUT, upon reception of a Heartbeat message that contains an opaque Heartbeat Data parameter,

47、 responds with a Heartbeat Ack that echoes back unchanged the opaque Heartbeat Data parameter Comments TPId M3UA_SGP_ASPTM_V_013 Status Optional Pre-condition Successfully established SCTP association between the SGP and the ASP 2 ASP in the AS Both ASPs marked as ASP ACTIVE at the SGP AS configure

48、in Broadcast mode Reference Section 3.8.2 1 Section 4.3.4.4 1 Purpose Ensure that the IUT, upon reception of an ASP Inactive message from ASP1 responds with an ASP Inactive Ack and sends a NOTIFY message with status “Insufficient ASP Resources Active in AS“ to all Inactive ASPs Comments The use of “

49、Broadcast“ mode is not recommended by ETSI ETSI ETSI TS 102 381 V1.1.1 (2004-12) 13TPId M3UA_SGP_ASPTM_V_014 Status Optional Pre-condition Successfully established SCTP association between the SGP and the ASP 2 ASP in the AS ASP1 marked as ASP INACTIVE at the SGP ASP2 marked as ASP ACTIVE at the SGP ASP1 and ASP2 configured in “Override“ mode Reference Section 3.8.2 1 Section 4.3.4.3 1 Purpose Ensure that the IUT, upon reception of an ASP Active message from ASP1 that in