ETSI TS 103 374-2-2017 Core Network and Interoperability Testing (INT) Diameter Conformance testing for Rf Ro interface Part 2 Test Suite Structure (TSS) and Test Purposes (TP) (V1_1.pdf

1、 ETSI TS 103 374-2 V1.2.1 (2017-01) Core Network and Interoperability Testing (INT); Diameter Conformance testing for Rf/Ro interface; (3GPP Release 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP) TECHNICAL SPECIFICATION ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)2 Reference RTS/INT-00131

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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including I

3、PR searches, 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

4、 produced by ETSI Technical Committee Core Network and Interoperability Testing (INT). The present document is part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1 4. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“,

5、 “may“, “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 374

6、-2 V1.2.1 (2017-01)6 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 Rf/Ro interfaces as specified in ETSI TS 132 260 1 and ETSI TS 132 299 2 in compliance with the relevant requirements and in a

7、ccordance with the relevant guidance given in ISO/IEC 9646-7 6 and ETSI ETS 300 406 7. 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 app

8、lies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in

9、this clause were valid at the time 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 132 260 (V10.14.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Tele

10、communications System (UMTS); LTE; Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging (3GPP TS 32.260 version 10.14.0 Release 10)“. 2 ETSI TS 132 299 (V10.15.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System

11、(UMTS); LTE; Telecommunication management; Charging management; Diameter charging applications (3GPP TS 32.299 version 10.15.0 Release 10)“. 3 ETSI TS 102 790-2: “Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and

12、 Session Description Protocol (SDP); Conformance Testing; Part 2: Test Suite Structure (TSS) and Test Purposes (TP)“. 4 ETSI TS 103 374-1: “Core Network and Interoperability Testing (INT); Diameter Conformance testing for Rf/Ro interface; (3GPP Release 10); Part 1: Protocol Implementation Conformanc

13、e Statement (PICS)“. 5 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 6 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7

14、: Implementation Conformance Statements“. 7 ETSI ETS 300 406: “Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 8 IETF RFC 3588: “Diameter Base Protocol“. 9 IETF RFC 4005: “Diameter Network Access Server Application“.

15、 10 IETF RFC 4006: “Diameter Credit-Control Application“. ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)7 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 ap

16、plies. For non-specific references, the latest version of the referenced 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 n

17、ecessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 132 260 1, ETSI TS 132 299 2 an

18、d the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 5. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 5. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 5. Test Purpose (TP): Refer to ISO/IEC 9646-1 5. 3.2 Abbreviations For the purposes of the present document, th

19、e abbreviations given in ETSI TS 132 260 1, ETSI TS 132 299 2 and the following apply: CDF Charging Data Function CTF Charging Trigger Function TP Test Purpose TSS Test Suite Structure 4 Test configurations 4.1 Introduction Test purposes of the present document address the IMS functional entities th

20、at are accessible via the following standardized DIAMETER interfaces: Ro and Rf. NOTE: In a real operating network the different Diameter nodes would not connect directly to each other. The connection is usually proxied through one or more Diameter Agents. In the following test architecture figures

21、the Diameter Agent is not explicitly depicted as it is seen as a transparent message handler for conformance testing purposes. ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)8 4.2 Test configurations using Rf interface The Rf interface is located between a CTF equipment hosted by an x-CSCF or a SIP AS and t

22、he CDF. Figure 1: Test configuration CF_1Rf Figure 2: Test configuration CF_1Rf1Gm Figure 3: Test configuration CF_1Rf1Gm1Mw TS or (SUT) SUT or (TS) Rf CDF CTF TS SUT Gm CTFs UE1 TS CDF Rf TS SUT Gm CTFs UE TS CDF Rf I-CSCF Mw ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)9 Figure 4: Test configuration CF_

23、1Rf1Gm1Ic Figure 5: Test configuration CF_1Rf1Isc Figure 6: Test configuration CF_2Rf1Gm1Mw TS SUT Gm CTFs UE TS CDF Rf IBCF Ic TS SUT CTFs TS CDF Rf S-CSCF Isc SUT TS TS Gm CTFs UE CDF Rf I-CSCF Mw CDF Rf ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)10 4.3 Test configurations using Ro interface The Ro in

24、terface is located between a CTF equipment hosted by an MRFC or a SIP AS or an IMS GW and the OCF. Figure 7: Test configuration CF_1Ro Figure 8: Test configuration CF_2Ro Figure 9: Test configuration CF_1Ro1Gm1Mw TS or (SUT) SUT or (TS) Ro OCF CTF TS or (SUT) SUT or (TS) Ro OCF CTF OCF Ro TS SUT Gm

25、CTFs UE TS OCF Ro I-CSCF Mw ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)11 Figure 10: Test configuration CF_1Ro1Gm1Ic Figure 11: Test configuration CF_1Ro1Isc Figure 12: Test configuration CF_2Ro1Gm1Mw TS SUT Gm CTFs UE TS OCF Ro IBCF Ic TS SUT CTFs TS OCF Ro S-CSCF Isc TS SUT Gm CTFs UE TS OCF Ro I-CSCF

26、 Mw OCF Ro ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)12 5 Test Suite Structure (TSS) and Test Purposes (TP) 5.1 Test Suite Structure 5.1.1 TP naming convention TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Table 1: TP identifier naming convention scheme

27、 Identifier: _ = Test Purpose: fixed to “TP“ Interface: RF or RO = type of IUT: CDF, OCF or CTF = group MS Message syntax TC Type of Charging EC Error Cases CH Tariff Changes RE Re-authorization FH Failure Handling FA Failover CP Credit Pooling OP Other procedures (2, clause 6.5) = sequential number

28、 (01 to 99) 5.1.2 Test strategy As the base standards in ETSI TS 132 260 1 and ETSI TS 132 299 2 contain 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 374-1 4. 5.1.3 TP structure Each TP has been wr

29、itten 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. Table 2 should be read in conjunction with any TP, i.e. please use a TP as an example to facilitate th

30、e full comprehension of table 2. ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)13 Table 2: Structure of a single TP TP part Text Example Header see table 6.2.3 clause 6.2.3 A.2/3 Summary Short free text description of the test objective Verify that the IUT can successfully process all mandatory AVPs in a C

31、C-Request received due to IP-CAN session establishment Configuration One of the test configurations as described in clauses 4.2 and 4.3 CF_1Rf Initial condition (optional) Free text description of the condition that the IUT has reached before the test purpose applies The IUT has received AF provisio

32、ns information about the AF signalling flows between UE and AF Start point Ensure that the IUT in the see IETF RFC 3588 8 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 AC-Request Stimulus , see below for

33、 message structure on receipt of a Capabilities-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)

34、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: All messages are considered as “valid and compatible“ unless otherwise specified in the test purpose.

35、This includes the presence of all mandatory AVPs as specified in IETF RFC 3588 8 and in ETSI TS 132 299 2, clauses 6.2.2, 6.2.3, 6.4.2 and 6.4.3. 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 t

36、his will be expressed like this: sends/receives Message 1 containing AVP1 containing AVP3indicating . containing AVP2indicating . 5.2 Test Purposes 5.2.1 PICS references All PICS items referred to in this clause are as specified in ETSI TS 103 374-1 4 unless indicated otherwise by another numbered r

37、eference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. 5.2.2 Rf interface 5.2.2.1 CDF Role 5.2.2.1.1 Test selection The IUT takes the role of the CDF; PICS A.2/1. ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)14 5.2.2.

38、1.2 Message Syntax TP_RF_CDF_MS_01 Standards Reference: Clause 6.2.3 - Table 6.2.3 and IETF RFC 4005 9, clause 3.92 and Clause 3.103 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in an AC-Request received due to Charging Data Transfer. Configuration: CF_1Rf Test

39、 purpose: Ensure that the IUT on receipt of an AC-Request containing a Session-ID AVP containing an Origin-Host AVP containing an Origin-Realm AVP containing a Destination-Realm AVP containing an Accounting-Record-Type AVP containing an Accounting-Record-Number AVP containing an Acct-Application-Id

40、AVP indicating the value 3 sends an AC-Answer containing a Session-ID AVP containing a Result-Code AVP indicating DIAMETER_SUCCESS not containing an Experimental-Result AVP containing an Origin-Host AVP containing an Origin-Realm AVP containing an Accounting-Record-Type AVP containing an Accounting-

41、Record-Number AVP containing an Acct-Application-Id AVP indicating the value 3. Comments: TP_RF_CDF_MS_02 Standards Reference: IETF RFC 3588 8, clause 32 and 4 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in an AC-Request received due to Charging Data Transfer

42、and responds with a valid AC-Answer message. Configuration: CF_1Rf Test purpose: Ensure that the IUT on receipt of an AC-Request containing a Session-ID AVP containing an Origin-Host AVP containing an Origin-Realm AVP containing a Destination-Realm AVP containing an Accounting-Record-Type AVP contai

43、ning an Accounting-Record-Number AVP containing an Acct-Application-Id AVP indicating the value 3 sends an AC-Answer containing a Diameter-Header containing a Version indicating value 1 containing a Command-Flags containing T bit indicating value 0 containing r bits indicating value 0000. Comments:

44、ETSI ETSI TS 103 374-2 V1.2.1 (2017-01)15 5.2.2.1.3 Type of Charging TP_RF_CDF_TC_01 Standards Reference: Clause 6.1.1/Steps1 to 4 - Table 6.2.2/3 PICS item: A.3/1.1 Summary: Verify that the IUT can successfully process an AC-Request Event where Event Based Charging is used. Configuration: CF_1Rf Te

45、st purpose: Ensure that the IUT on receipt of an AC-Request containing an Accounting-Record-Type AVP indicating EVENT_RECORD containing an Event-Timestamp AVP optionally containing a Service-Information AVP containing at least one Subscription-ID AVP indicating the identification of the user optiona

46、lly containing an IMS-Information AVP containing a Node-Functionality AVP indicating the value 3 optionally containing a Service-Generic-Information AVP indicating the service specific parameters optionally containing a Service-Context-Id AVP sends an AC-Answer containing a Result-Code AVP indicatin

47、g DIAMETER_SUCCESS not containing an Experimental-Result AVP containing an Accounting-Record-Type AVP indicating EVENT_RECORD containing an Accounting-Record-Number AVP. Comments: TP_RF_CDF_TC_02 Standards Reference: Clause 6.1.2/Steps 2 to 4 - Table 6.2.2/3 PICS item: A.3/1.2 Summary: Verify that t

48、he IUT can successfully process an AC-Request Start where Session Based Charging is used. Configuration: CF_1Rf Test purpose: Ensure that the IUT on receipt of an AC-Request containing an Accounting-Record-Type AVP containing an Accounting-Record-Type AVP indicating START_RECORD containing an Accoun

49、ting-Record-Number AVP containing an Event-Timestamp AVP containing a Service-Information AVP indicating the service specific parameters sends an AC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS not containing an Experimental-Result AVP containing an Accounting-Record-Type AVP indicating START_RECORD optionally containing an Acct-Interim-Interval AVP indicating the desired intermediate charging interval. Comments: Postamble action: ACR Stop is sent. ETSI ETSI TS 103 374-2 V1.2.1 (201