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

《ETSI TS 103 262-2-2015 Core Network and Interoperability Testing (INT) Diameter Conformance testing for S9 interface (3GPP Release 10) Part 2 Test Suite Structure (TSS) and Test Pu.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 262-2-2015 Core Network and Interoperability Testing (INT) Diameter Conformance testing for S9 interface (3GPP Release 10) Part 2 Test Suite Structure (TSS) and Test Pu.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 103 262-2 V1.2.1 (2015-07) Core Network and Interoperability Testing (INT); Diameter Conformance testing for S9 interface; (3GPP Release 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP) TECHNICAL SPECIFICATION ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)2 Reference RTS/INT-00115-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 S9 interface, as identified below: Part 1: “Protocol Implementation Conformance Statement (PI

5、CS)“; 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 262-2 V1.

7、2.1 (2015-07)5 1 Scope The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specifications for the Diameter protocol on the S9 interface as specified in ETSI TS 129 215 1 in compliance with the relevant requirements and in accordance with the relevant guid

8、ance 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 reference

9、s, 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 215 (V10.6.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; P

11、olicy and Charging Control (PCC) over S9 reference point; Stage 3 (3GPP TS 29.215 version 10.6.0 Release 10)“. 2 ETSI TS 103 262-1: “ Core Network and Interoperability Testing (INT); Diameter Conformance testing for S9 interface; (3GPP Release 10); Part 1: Protocol Implementation Conformance Stateme

12、nt (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 framework - Part 7: Impleme

13、ntation 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“. 7 ETSI TS 129 212 (V10.5.0): “Universal Mobile Telecommunications Syste

14、m (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)“. 8 ETSI TS 129 213 (V10.11.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling flow

15、s and Quality of Service (QoS) parameter mapping (3GPP TS 29.213 version 10.11.0 Release 10)“. 2.2 Informative 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 applie

16、s. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necess

17、ary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETS

18、I TS 129 215 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-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 pre

19、sent document, the abbreviations given in ETSI TS 129 215 1 and the following apply: TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (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 organ

20、ized according to the TSS. Table 1: TP identifier naming convention scheme Identifier: _ = Test Purpose: fixed to “TP“ = type of IUT: HPCRF or VPCRF = group MS S9 Message Syntax HSE Home Access/S9 Session Establishment HSM Home Access/S9 Session Modification HPQ Home Access/Provision of QoS Rules HS

21、T Home Access/S9 Session Termination HMB Home Access/Multiple BBERF Handling HDS Home Access/Deferred Session Linking Handling HSL Home Access/Session Linking Handling When Multiple PDN Connection to a single APN VQR Visited Access/QoS and PCC Rules VPQ Visited Access/Provision of QoS and PCC Rules

22、VST Visited Access/S9 Session/Subsession Termination VMB Visited Access/Multiple BBERF Handling VRS Visited Access/Rx over S9 VEH Visited Access/Event Handling VDS Visited Access/Deferred Session Linking Handling VSL Visited Access/Session Linking Handling When Multiple PDN Connection to a single AP

23、N VIF Visited Access/IP Flow mobility support = sequential number (01 to 99) 4.1.2 Test strategy As the base standard ETSI TS 129 215 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ETSI TS 103 262-1 2

24、. ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)7 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 checkable. A particular structure has been used which is illustrated in table 2. This table should be

25、read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2. Table 2: Structure of a single TP TP part Text Example Header see table 1 clause 4.4.1 A.2/3 Summary Short free text description of the test objective Verify that the IUT can successf

26、ully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Initial condition (optional) Free text description of the condition that the IUT has reached before the test purpose applies. The IUT has received AF provisions information about the AF signalling flows bet

27、ween 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 sending/receiving see below for message structure having sent an AA-Request Stimulus , see below for message structure on receipt of a Capabilities

28、-Exchange-Request (see note 2) or to require PCC supervision Reaction . sends, saves, does, etc. if the action is sending see below for message structure , 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) Ve

29、ndor-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: All messages are considered as “valid and compatible“ unless otherwise specified in the test purpose. This includes the presence of all mandatory AVP

30、s as specified in IETF RFC 3588 6 and in ETSI TS 129 215 1, clause 5. NOTE 3: An AVP can be embedded into another AVP. This is expressed by indentations, 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 co

31、ntaining AVP3indicating . containing AVP2indicating . ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)8 4.2 Test Purposes 4.2.0 PICS references All PICS items referred to in this clause are as specified in ETSI TS 103 262-1 2 unless indicated otherwise by another numbered reference. PICS items are only meant

32、 for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. 4.2.1 H-PCRF Role 4.2.1.0 Test Selection IUT takes the role of the H-PCRF; PICS A.2/1 4.2.1.1 S9 Messages TP_HPCRF_MS_01 Standards Reference: 5.5.3 PICS item: Summary: Verify that the IUT can

33、 successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a Session-Id AVP containing an Auth-Application-Id AVP containing an Origin-Host AVP containing an Origin-Realm AVP containin

34、g a Destination-Realm AVP containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a CC-Request-Number AVP containing a Subscription-Id AVP containing the user identification containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio acce

35、ss technology containing a Framed-IP-Address AVP indicating the full IP address of the UE, sends a CC-Answer containing a Session-Id AVP containing an Auth-Application-Id AVP containing an Origin-Host AVP containing an Origin-Realm AVP containing a CC-Request-Type AVP indicating INITIAL_REQUEST cont

36、aining a CC-Request-Number AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)9 4.2.1.2 Home access 4.2.1.2.0 Test Selection IUT takes the role of the H-PCRF; PICS A.2/1.1 4.2.1.2.1 S9 Session Establishment TP_HPCRF_HSE_01 Standards Referen

37、ce: 4.5.1.1 and 4.5.2.1 19 and ETSI TS 129 212 7, 4a.5.1 3 PICS item: A.3/1 Summary: Verify that the IUT can successfully provision QoS rules due to case 2a for S9 session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_

38、REQUEST containing a Subscription-Id AVP indicating IMSI containing a AN-GW-Address AVP indicating access network gateway address containing attributes provided by the BBERF sends a CC-Answer containing a QoS-Rule-Install AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: TP_HPC

39、RF_HSE_02 Standards Reference: 4.5.1.1 and 4.5.2.1 20 PICS item: A.3/1 Summary: Verify that the IUT can successfully provision QoS rules in CCA command due to case 2b for S9 session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicatin

40、g INITIAL_REQUEST containing a Subscription-Id AVP indicating IMSI containing a AN-GW-Address AVP indicating access network gateway address containing a Subsession-Enforcement-Info AVP containing a Subsession-Id AVP indicates a session-id from Gxx containing a Subsession-Operation AVP indicating EST

41、ABLISHMENT containing attributes provided by the BBERF sends a CC-Answer containing a Subsession-Decision-Info AVP containing a QoS-Rule-Install AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)10 4.2.1.2.2 S9 Session Modification TP_HPCR

42、F_HSM_01 Standards Reference: 4.5.1.1 and 4.5.2.1 1 9 and ETSI TS 129 212 7, 4a.5.1 7 PICS item: Summary: Verify that the IUT can successfully provision QoS rules due to case 2a for S9 session modification. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP

43、 indicating UPDATE_REQUEST containing a QoS-Rule-Report AVP containing attributes provided by the BBERF sends a CC-Answer containing a QoS-Rule-Install AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: NOTE: CCR and CCA command with INITIAL_REQUEST exchanged before above check.

44、 TP_HPCRF_HSM_02 Standards Reference: 4.5.1.1 and 4.5.2.1 20 and ETSI TS 129 212 7, 4a.5.1 7 PICS item: Summary: Verify that the IUT can successfully provision QoS rules in CCA command due to case 2b for S9 session modification. Test purpose: Ensure that the IUT on receipt of a CC-Request containing

45、 a CC-Request-Type AVP indicating UPDATE_REQUEST containing a QoS-Rule-Report AVP containing a Subsession-Enforcement-Info AVP containing a Subsession-Id AVP indicates a session-id from Gxx containing a Subsession-Operation AVP indicating MODIFICATION containing attributes provided by the BBERF send

46、s a CC-Answer containing a Subsession-Decision-Info AVP containing a QoS-Rule-Install AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: NOTE: CCR and CCA command with INITIAL_REQUEST exchanged before above check. ETSI ETSI TS 103 262-2 V1.2.1 (2015-07)11 TP_HPCRF_HSM_03 Standar

47、ds Reference: 4.5.1.1 and 4.5.2.1 21, 22 and ETSI TS 129 212 7, 4a.5.1 7 PICS item: Summary: Verify that the IUT in case of incomplete, erroneous or missing information when it is not able to provision a policy decision to a specific subsession sends CC-Answer with appropriate error within Experimen

48、tal-Result-Code AVP at the command level and Subsession-Decision-Info AVP for each of the rejected subssesions. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a QoS-Rule-Report AVP containing a Subsession-Enforcement

49、-Info AVP containing a Subsession-Id AVP indicates an erroneous session-id from Gxx containing a Subsession-Operation AVP indicating MODIFICATION containing attributes provided by the BBERF sends a CC-Answer containing an Experimental-Result AVP containing an Experimental-Result-Code AVP indicating DIAMETER_ERROR_SUBSESSION containing a Subsession-Decision-Info AVP containing a Subsession-Id AVP indicating rejected value (containing an Experimental-Result AVP or containing a Result-Code AVP). Comments: NOTE 1: CC