ETSI TS 102 380-2004 Methods for Testing and Specification (MTS) SS7 Message Transfer Part 2 - User Adaptation Layer (M2UA) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)_1.pdf

《ETSI TS 102 380-2004 Methods for Testing and Specification (MTS) SS7 Message Transfer Part 2 - User Adaptation Layer (M2UA) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 380-2004 Methods for Testing and Specification (MTS) SS7 Message Transfer Part 2 - User Adaptation Layer (M2UA) Test Suite Structure and Test Purposes (TSS&TP) (V1 1 1)_1.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

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

2、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 r

3、eferenced 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). To evaluate conformance o

4、f a particular implementation, it is necessary to have a set of test purposes to evaluate the dynamic behaviour of the Implementation Under Test (IUT). The specification containing those test purposes is called a Test Suite Structure and Test Purposes (TSS MTP/SCCP/SSCOP and SIGTRAN (Transport of SS

5、7 over IP); Message transfer part 2 User Adaptation layer (M2UA); Endorsement of RFC 3331 (2002), modified“. 2 IETF RFC 3331 (September 2002): “Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection -

6、 Conformance testing methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 5 ETSI ETS 300 406: “Methods for Testing and Specificatio

7、n (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. ETSI ETSI TS 102 380 V1.1.1 (2004-12) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 102 141 1, ISO/IEC 9646-1 3, ISO/IEC

8、 9646-2 4 and the following apply: abstract test case: Refer to ISO/IEC 9646-1 3. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Imp

9、lementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 3. ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1 3. IXIT proforma: Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. Valid behaviour test pu

10、rpose: tests that handle valid signalling exchanges of messages, which are properly structured and correctly encoded Inoportune behaviour test purpose: tests that handle valid signalling exchanges of messages, which are properly structured and correctly encoded but are received when not expected Inv

11、alid behaviour test purpose: tests that handle valid signalling exchanges of messages, which are not properly structured or incorrectly encoded 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Application Server ASP Application Server Process ATM Abst

12、ract Test Method ATS Abstract Test Suite CCS Common Channel Signalling IID Interface IDentifier IO InOpportune behaviour IUT Implementation Under Test IV InValid behaviour LT Lower Tester M2UA Message transfer part 2 User Adaptation layer MGC Media Gateway Control MTP Message Transfer Part NIF Nodal

13、 Inter-working Function SCTP Stream Control Transmission Protocol SEP Signalling End Point SG Signalling Gateway SGP Signaling Gateway Process SLT Signalling Link Terminal ETSI ETSI TS 102 380 V1.1.1 (2004-12) 7 SS7 Signalling System No. 7 STP Signalling Transfer Point TSS Test Suite Structure V Val

14、id behaviour 4 Test Suite Structure (TSS) 4.1 Introduction 4.1.1 M2UA Entities Test Purposes have been written for M2UA Peers according to TS 102 141 1. Two kinds of entities are considered successively as IUT: - Signalling Gateway Process (SGP); - Application Server Process (ASP). In a Signalling G

15、ateway, it is expected that the SS7 Signalling is received over a standard SS7 network termination, using the SS7 Message Transfer Part (MTP) to provide transport of SS7 Signalling messages to and from an SS7 Signalling End Point (SEP) or SS7 Signalling Transfer Point (STP). In other words, the SG a

16、cts as a Signalling Link Terminal (SLT). The SG then provides an interworking of transport functions with IP Signalling Transport, in order to transport the MTP3 signalling messages to the network element (e.g. an MGC) actings as Application Server (AS) where the peer MTP3 protocol layer exists, as

17、shown below: MTP L2 L1 M2UA SCTP IP MTP (L3) M2UA SCTP IP NIF NOTE 1: NIF - Nodal Interworking Function NOTE 2: P - Internet Protocol NOTE 3: SCTP - Stream Control Transmission Protocol Figure 1: Embedding of M2UA protocol stack in the SGP and ASP To enable the verification of certain aspects of the

18、 protocol, certain optional test purposes will require the use of multiple ASPs within an AS. 4.1.2 General assumptions Test purposes have been written for behaviours requested with “MUST“ or that appear as obvious in present form. In addition test purposes have been defined for implementation depen

19、dent behaviour, where at least one of the implementation options is mandatory. ETSI ETSI TS 102 380 V1.1.1 (2004-12) 8 4.2 Overview of the Test Suite Structure The following figure shows the Test Suite Structure (TSS). Functionality subgroups may be subdivided in three subgroups: Valid behaviour (V)

20、; Inopportune behaviour (IO); Invalid behaviour (IV). Table 1: TSS for M2UA Test suite Main functionalities Functionality subgroup Test group M2UA Signalling Gateway Process (SGP) State and traffic transactions (ASPM) V-IO-IV Interface identifier Management (IIM) V-IO-IV M2UA User Adaptation Message

21、s (MAUP) V-IO-IV Application Server Process (ASP) State and traffic transactions (ASPM) V-IO-IV Interface identifier Management (IIM) V-IO-IV M2UA User Adaptation Messages (MAUP) V-IO-IV General Error Handling (GEH) - - 4.3 Conformance Test Cases This clause describes the test steps and the message

22、flows corresponding to the test cases. The test cases are broadly divided into a number of different groups according to the protocol functionality. State and traffic transactions (ASPM): This group validates the ASP / SG state and traffic transaction messages. Interface identifier Management (IIM):

23、 The dynamic registration and de-registration procedures are covered in this section. M2UA User Adaptation Messages (MAUP): MTP2 user adaptation procedures are covered in this section. Each group is further categorized based on the test case configuration of the IUT i.e. whether ASP or SG of M2UA la

24、yer is under test. Then the group has the normal category of valid, inopportune and invalid behaviour tests. A further group has been added to cover the error handling procedures in a general manner. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming con

25、vention TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite (see table 2). ETSI ETSI TS 102 380 V1.1.1 (2004-12) 9 Table 2: TP identifier naming convention scheme Identifier: _ M2UA SGP (Sig

26、nalling Gateway Process) ASP (Application Server Process) GEH. (General Error Handling) ASPM (ASP Maintenance Procedures) IIM (Interface Identifier MGMT Messaging) M2UA User Adaptation Messages (MAUP) Valid Behaviour (V) Inopportune Behaviour (IO), Invalid Behaviour (IV) sequential number (01 to 99)

27、. 5.1.2 Source of TP definition The TPs are based on TS 102 141 1. 5.1.3 Test strategy As the base standard TS 102 141 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard. The TPs are only based on conformance requirements related t

28、o the externally observable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see ETS 300 406 5). 5.1.4 TP structure Each test purpose is decomposed in five keywords. The TPId gives a unique identifier to each test purpose. The Statu

29、s specifies whether the test purpose or the group is mandatory or optional according to RFC 3331 2. The Test Configuration of the IUT within the test architecture. The Precondition determines the initial state of the SUT for the evaluating the test purpose. The Ref. outlines the references in RFC 33

30、31 2 used to create the test purpose. The Purpose describes the objective of the test. ETSI ETSI TS 102 380 V1.1.1 (2004-12) 105.2 Test Purposes for Signalling Gateway Process (SGP) 5.2.1 ASPM STATE and Traffic Transactions Management 5.2.1.1 Valid Behaviour Test Cases TPId: M2UA_SGP_ASPM_V_01 Statu

31、s: Mandatory Test Configuration One ASP is configured in an AS. If necessary the AS and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP is in down state. Ref: Sections 3.3.2.1, 4.3.1, 4.3.2 and 4.3.4.5 of RFC 3331 2 Purpose: To validat

32、e that the ASP Up message received with mandatory and optional parameters, moves the state of the ASP and AS to Inactive at the IUT. Ensure that the IUT responds with the ASP Up Ack and Notify (AS-Inactive) message indicating the AS state has been changed to inactive. TPId: M2UA_SGP_ASPM_V_02 Status

33、: Optional Test Configuration Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT. Pre-Condition SCTP associations are established between ASP and IUT. ASP is in down state. Ref: Sections 4.3.4.1, 4.3.1, 4.3.2 and 4.3.4.5 of RFC 3331 2 Purp

34、ose: To ensure that, upon reception of the ASP Up message, IUT responds with ASP Up Ack and 2 Notify (AS-Inactive) messages corresponding to each AS. TPId: M2UA _SGP_ASP_V_03 Status: Optional Test Configuration Two ASPs (ASP1 and ASP2) are configured in a single AS. If necessary the AS and ASPs have

35、 to be pre-configured at the IUT. Pre-Condition SCTP associations are established between IUT and both ASPs. Both ASPs are in down state. Ref: Sections 4.3.4.1, 4.3.1, 4.3.2 and 4.3.4.5 of RFC 3331 2 Purpose: Validate that when IUT receives an ASP Up message for ASP1, it responds with ASP Up Ack and

36、 a Notify (AS-Inactive) message, indicating the AS state has moved to inactive. It should be verified that no Notify message is sent to the ASP that has not yet sent the ASP Up message. Now send the ASP Up message for ASP2 and validate that the IUT responds with ASP Up Ack message only. TPId: M2UA_S

37、GP_ASPM_V_04 Status: Mandatory Test Configuration One ASP is configured in an AS. If necessary the AS and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. AS is in inactive state. Ref: Sections 3.3.2.7, 3.3.2.8 and 4.3.4.3 of RFC 3331 2 Pur

38、pose: To validate the ASP Active message having all parameters and one configured IID (using tag of 0x1), moves the state of the ASP to active. Ensure that the IUT responds with the ASP Active Ack and a Notify (AS-Active) message to indicate that the AS state has moved to the active. If the ASP was

39、pre-configured to serve more than one IID, the ASP Active Ack message should contain all pre-configured IIDs and not only the one contained in the ASP Active message. ETSI ETSI TS 102 380 V1.1.1 (2004-12) 11TPId: M2UA_SGP_ASPM_V_05 Status: Mandatory Test Configuration One ASP is configured in an AS.

40、 If necessary the AS and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP is in inactive state. Ref: Sections 3.3.2.7 and 4.3.4.3 of RFC 3331 2 Purpose: To validate the ASP Active message having all parameters and multiple configured II

41、D (using tag of 0x1), moves the state of the ASP to active. Ensure that the IUT responds with the ASP Active Ack and a Notify (AS-Active) message to indicate the AS state has moved to the active. TPId: M2UA_SGP_ASPM_V_06 Status: Mandatory Test Configuration One ASP is configured in an AS. If necessa

42、ry the AS and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP is in inactive state. Ref: Sections 3.3.2.7 and 4.3.4.3 of RFC 3331 2 Purpose: Ensure that an on reception of an ASP Active message with integer range parameters with config

43、ured start and stop values (tag of 0x8) from peer, IUT responds with the ASP Active Ack and a Notify (AS-Active) message having the value of (AS_active) in status type field. TPId: M2UA_SGP_ASPM_V_07 Status: Mandatory Test Configuration One ASP is configured in an AS. If necessary the AS and ASP hav

44、e to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP is in active state. Ref: Sections 3.3.2.9, 4.3.2 and 4.3.4.4 of RFC 3331 2 Purpose: Ensure that upon reception of an ASP Inactive message, IUT responds with ASP Inactive Ack message and one or m

45、ore Notify messages depending whether the IUT has T(r) implemented or not. TPId: M2UA_SGP_ASPM_V_08 Status: Optional Test Configuration Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established betwe

46、en ASP and IUT. ASP is in inactive state in both AS1 and AS2. Ref: Sections 3.3.2.8 and 4.3.4.3 of RFC 3331 2 Purpose: Ensure that the IUT responds with one or two ASP Active Ack and one or two Notify (AS Active) messages, indicating the AS state transaction to active in both AS, upon receiving an A

47、SP Active message with only the mandatory parameters. TPId: M2UA_SGP_ASPM_V_09 Status: Optional Test Configuration Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP i

48、s in inactive state in both AS1 and AS2. Ref: Sections 3.3.2.8 and 4.3.4.3 of RFC 3331 2 Purpose: Ensure that the IUT responds with an ASP Active Ack and Notify (AS Active) messages indicating the AS1 state transaction to active, when it receives an ASP Active message with IID values as that of AS1.

49、 Also, validate that on receiving an ASP Active message with IID as configured for AS2, IUT responds with the ASP Active Ack and Notify (AS-Active) message. ETSI ETSI TS 102 380 V1.1.1 (2004-12) 12TPId: M2UA_SGP_ASPM_V_10 Status: Optional Test Configuration Single ASP is configured in two different AS. If necessary the ASs and ASP have to be pre-configured at the IUT. Pre-Condition SCTP association is established between ASP and IUT. ASP is in active state in both AS. Ref: Sections 3.3.2.10 and 4.3.4