ETSI TS 103 261-2-2015 Core Network and Interoperability Testing (INT) Diameter Conformance testing for S6a interface (3GPP Release 10) Part 2 Test Suite Structure (TSS) and Test P_1.pdf

1、 ETSI TS 103 261-2 V1.2.1 (2015-06) Core Network and Interoperability Testing (INT); Diameter Conformance testing for S6a interface; (3GPP Release 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP) TECHNICAL SPECIFICATION ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)2Reference RTS/INT-00114-2

2、Keywords diameter, TSS 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:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR se

3、arches, 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 prod

4、uced by ETSI Technical Committee Core Network and Interoperability Testing (INT). The present document is part 2 of a multi-part deliverable covering the test specifications for the Diameter protocol on the S6a interface, as identified below: Part 1: “Protocol Implementation Conformance Statement (P

5、ICS)“; Part 2: “Test Suite Structure (TSS) and Test Purposes (TP)“; Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification“. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may

6、“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 261-2 V1

7、.2.1 (2015-06)51 Scope The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specifications for the Diameter protocol on the S6a interface as specified in ETSI TS 129 272 1 in compliance with the relevant requirements and in accordance with the relevant gui

8、dance given in ISO/IEC 9646-7 4 and ETSI ETS 300 406 5. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific referenc

9、es, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time

10、 of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 129 272 (V10.8.0): “Universal Mobile Telecommunications System (UMTS); LTE; Evolved Packet System (EPS); Mobility Management Entity

11、 (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol (3GPP TS 29.272 version 10.8.0 Release 10)“. 2 ETSI TS 103 261-1: “Core Network and Interoperability Testing (INT); Diameter Conformance testing for S6a interface; (3GPP Release 10); Part 1: Protocol Implementa

12、tion Conformance Statement (PICS)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and fra

13、mework - Part 7: Implementation Conformance Statements“. 5 ETSI ETS 300 406: “Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 6 IETF RFC 3588: “Diameter Base Protocol“. 2.2 Informative references References are eithe

14、r specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in

15、cluded in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI T

16、S 103 261-2 V1.2.1 (2015-06)63 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 129 272 1 and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646

17、-1 3. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 129 272 1 and the following apply: TP Test Purpose TSS Test Suite Structure 4 Test Suite Stru

18、cture (TSS) and Test Purposes (TP) 4.1 Test Suite Structure 4.1.1 TP naming convention TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Table 1: TP identifier naming convention scheme Identifier: _ = Test Purpose: fixed to “TP“ = type of IUT: MME or HS

19、S = group UL Update Location CL Cancel Location PUE Purge UE ISD Insert Subscriber Data DSD Delete Subscriber Data AIR Authentication Information Retrieval RES Reset NOT Notification = sequential number (01 to 99) 4.1.2 Test strategy As the base standard ETSI TS 129 272 1 contains no explicit requir

20、ements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ETSI TS 103 261-1 2. 4.1.3 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 checka

21、ble. A particular structure has been used which is illustrated in table 2. This table should be read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2. ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)7Table 2: Structure of a single TP TP part Text

22、Example Header see table 1 clause 5.2.1.1.2 A.2/3 Summary Short free text description of the test objective Verify that the IUT can successfully process all mandatory AVPs in a UL-Request received due to IP-CAN session establishment. Initial condition (optional) Free text description of the conditio

23、n that the IUT has reached before the test purpose applies. The IUT has received AF provisions information about the AF signalling flows between UE and AF. Start point Ensure that the IUT in the see IETF RFC 3588 6, clause 5.6 Open state and/or further actions before stimulus if the action is sendin

24、g/receiving see below for message structure having sent an AA-Request Stimulus , see below for message structure on receipt of a Capabilities-Exchange-Request (see note 2) or to require PCC supervision, etc. Reaction . sends, saves, does, etc. if the action is sending see below for message structure

25、 , etc. Message structure Capabilities-Exchange-Answer, etc. (see note 2) a) containing a(n) AVP b) indicating and back to a) or b) (see note 3) Vendor-Id, etc. NOTE 1: 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. NOTE 2: Al

26、l messages shall be considered as “valid and compatible“ unless otherwise specified in the test purpose. This includes the presence of all mandatory AVPs as specified in IETF RFC 3588 6 and in ETSI TS 129 272 1, clause 7. NOTE 3: An AVP can be embedded into another AVP. This is expressed by indentat

27、ions, e.g. if Message1 contains AVP1 and AVP2 where AVP1 has AVP3 embedded this will be expressed like this: sends/receives Message 1 containing AVP1 containing AVP3indicating . containing AVP2indicating . 4.2 Test Purposes 4.2.0 PICS references All PICS items referred to in this clause are as speci

28、fied in ETSI TS 103 261-1 2 unless indicated otherwise by another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. 4.2.1 MME Role 4.2.1.0 Test Selection IUT takes the role of the MME; PICS A.2/1

29、ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)84.2.1.1 Update Location Test Selection: IUT supports location management procedures; PICS A.3/1. TP_MME_UL_01 Standards Reference: 5.2.1.1.1 and 7.2.3 PICS item: Summary: Verify that the IUT can indicate request for update location information to inform HSS ab

30、out the identity of the currently serving user. Test purpose: Ensure that the IUT to indicate a request for update location information, sends a UL-Request containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Orig

31、in-Realm AVP containing a Destination-Realm AVP containing a User-Name AVP containing a RAT-Type AVP containing a ULR-Flags AVP with S6a-indicator bit set containing a Visited-PLMN-ID AVP Comments: TP_MME_UL_02 Standards Reference: 5.2.1.1.24 PICS item: A.2/1.2 Summary: Verify that the IUT due to an

32、 inter node (SGSN to MME) update sends UL-Request where “Single-Registration-Indication“ is set. Test purpose: Ensure that the IUT to indicate an inter node update, sends a UL-Request containing a ULR-Flags AVP with S6a-indicator bit set with Single-Registration-Indication bit set Comments: TP_MME_U

33、L_03 Standards Reference: 5.2.1.1.25 PICS item: Summary: Verify that the IUT can indicate request for update location information which is sent due to an initial attach. Test purpose: Ensure that the IUT to indicate a request for update location information due to an initial attach, sends a UL-Reque

34、st containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Origin-Realm AVP containing a Destination-Realm AVP containing a User-Name AVP containing a RAT-Type AVP containing a ULR-Flags AVP with S6a-indicator bit se

35、t with Initial-Attach-Indicator bit set containing a Visited-PLMN-ID AVP Comments: ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)9TP_MME_UL_04 Standards Reference: 5.2.1.1.26 PICS item: A.2/1.1 Summary: Verify that the IUT, when subscriber data are already available due to previous location update, success

36、fully processes additional request for update location information. Test purpose: Ensure that the IUT sends a UL-Request and on receipt of a UL-Answer to indicate additional request for update location information, sends a UL-Request containing a Session-ID AVP containing an Auth-Session-State AVP i

37、ndicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Origin-Realm AVP containing a Destination-Realm AVP containing a User-Name AVP containing a RAT-Type AVP containing a ULR-Flags AVP with S6a-indicator bit set with Skip-Subscriber-Data bit set containing a Visited-PLMN-ID AVP

38、Comments: TP_MME_UL_05 Standards Reference: 5.2.1.1.27 PICS item: A.2/1.1 and A.3/1.1 Summary: Verify that the IUT, that has chosen the option to include the SSGN number within ULR request is prepared to receive a single subscription data update message IDR from HSS when the subscription data is mod

39、ified. Test purpose: Ensure that the IUT sends a UL-Request containing a SGSN-Number AVP on receipt of a UL-Answer and on receipt of an ID-Request sends an ID-Answer Comments: TP_MME_UL_06 Standards Reference: 5.2.1.1.27 PICS item: A.2/1.1 and A.3/1.1 Summary: Verify that the IUT, that has chosen th

40、e option to include the SSGN number within ULR request is prepared to receive a single subscription data update message DSR from HSS when the subscription data is modified. Test purpose: Ensure that the IUT sends a UL-Request containing a SGSN-Number AVP on receipt of a UL-Answer and on receipt of a

41、n DS-Request sends an DS-Answer Comments: TP_MME_UL_07 Standards Reference: 5.2.1.1.210 PICS item: NOT A.2/1.1 Summary: Verify that the standalone IUT, does not indicate its support for any SGSN specific features and does not request explicitly the download of GPRS data. Test purpose: Ensure that th

42、e IUT sends a UL-Request containing a ULR-Flags AVP with S6a-indicator bit set with GPRS-Subscription-Data-Indicator bit not set with Node-Type-Indicator bit not set Comments: ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)104.2.1.2 Cancel Location Test Selection: IUT supports cancel location procedures; PI

43、CS A.3/2. TP_MME_CL_01 Standards Reference: Table 5.2.1.2.1/2 and 5.2.1.2.22 and 7.2.8 PICS item: Summary: Verify that the IUT when receiving Cancel location request checks whether the IMSI is known and if not the IUT shall return Cancel location response with all mandatory AVPs and with appropriate

44、 result code. Test purpose: Ensure that the IUT on receipt of a CL-Request containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Origin-Realm AVP containing a Destination-Host AVP containing a Destination-Realm AVP

45、 containing a User-Name AVP indicating not known IMSI containing a Cancelation-Type AVP, sends a CL-Answer containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Origin-Realm AVP containing a Result-Code AVP indicat

46、ing DIAMETER_SUCCESS Comments: TP_MME_CL_02 Standards Reference: Table 5.2.1.2.1/2 and 5.2.1.2.23 and 7.2.8 PICS item: Summary: Verify that the IUT when receiving Cancel location request checks whether the IMSI is known and if cancelation type of “Initial attach procedure“ is received then the IUT s

47、hall return Cancel location response with appropriate result code. Test purpose: Ensure that the IUT on receipt of a CL-Request containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing an Origin-Host AVP containing an Origin-Realm AVP containing a De

48、stination-Host AVP containing a Destination-Realm AVP containing a User-Name AVP indicating known IMSI containing a Cancelation-Type AVP indicating INITIAL_ATTACH_PROCEDURE, sends a CL-Answer containing a Session-ID AVP containing an Auth-Session-State AVP indicating NO_STATE_MAINTAINED containing a

49、n Origin-Host AVP containing an Origin-Realm AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS Comments: ETSI ETSI TS 103 261-2 V1.2.1 (2015-06)114.2.1.3 Purge UE Test Selection: IUT supports Purge UE procedures; PICS A.3/3. TP_MME_PUE_01 Standards Reference: Table 5.2.1.3.1/1 and 7.2.13 PICS item: Summary: Verify that the IUT can indicate request for purge UE procedure. Test purpose: Ensure that the IUT to indicate a request for purge UE procedure, sends a PU-Request containing a Session-ID AVP containing an Auth-Session-S