Core Network and Interoperability Testing (INT); Diameter Conformance testing for Rf/Ro interface; (3GPPTM Release 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP)

RTS/INT-00131-2

General Information

Status
Published
Publication Date
18-Jan-2017
Current Stage
12 - Completion
Due Date
19-Jan-2017
Completion Date
19-Jan-2017
Ref Project

Buy Standard

Standard
ETSI TS 103 374-2 V1.2.1 (2017-01) - Core Network and Interoperability Testing (INT); Diameter Conformance testing for Rf/Ro interface; (3GPPTM Release 10); Part 2: Test Suite Structure (TSS) and Test Purposes (TP)
English language
85 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 103 374-2 V1.2.1 (2017-01)






TECHNICAL SPECIFICATION
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)

---------------------- Page: 1 ----------------------
2 ETSI TS 103 374-2 V1.2.1 (2017-01)



Reference
RTS/INT-00131-2
Keywords
diameter, TSS&TP

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 374-2 V1.2.1 (2017-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Test configurations . 7
4.1 Introduction . 7
4.2 Test configurations using Rf interface . 8
4.3 Test configurations using Ro interface . 10
5 Test Suite Structure (TSS) and Test Purposes (TP) . 12
5.1 Test Suite Structure . 12
5.1.1 TP naming convention . 12
5.1.2 Test strategy . 12
5.1.3 TP structure . 12
5.2 Test Purposes . 13
5.2.1 PICS references . 13
5.2.2 Rf interface . 13
5.2.2.1 CDF Role . 13
5.2.2.1.1 Test selection . 13
5.2.2.1.2 Message Syntax . 14
5.2.2.1.3 Type of Charging . 15
5.2.2.1.4 Error Cases . 17
5.2.2.2 CTF Role . 18
5.2.2.2.1 Test selection . 18
5.2.2.2.2 Message Syntax . 18
5.2.2.2.3 Type of Charging . 19
5.2.2.2.4 Error Cases . 22
5.2.3 Ro interface . 25
5.2.3.1 OCF Role . 25
5.2.3.1.1 Test selection . 25
5.2.3.1.2 Message Syntax . 25
5.2.3.1.3 Type of Charging . 26
5.2.3.1.4 Error Cases . 30
5.2.3.1.5 Tariff Changes . 34
5.2.3.1.6 Re-authorization . 35
5.2.3.1.7 Failure Handling . 36
5.2.3.1.8 Failover . 37
5.2.3.1.9 Credit Pooling . 38
5.2.3.1.10 Other procedures . 39
5.2.3.2 CTF Role . 47
5.2.3.2.1 Test selection . 47
5.2.3.2.2 Message Syntax . 47
5.2.3.2.3 Type of Charging . 48
5.2.3.2.4 Error Cases . 52
5.2.3.2.5 Tariff Changes . 56
5.2.3.2.6 Re-authorization . 61
5.2.3.2.7 Failure Handling . 62
5.2.3.2.8 Failover . 64
5.2.3.2.9 Credit Pooling . 66
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 374-2 V1.2.1 (2017-01)
5.2.3.2.10 Other procedures . 67
History . 85

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 374-2 V1.2.1 (2017-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); 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 IPR 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 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", "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

---------------------- Page: 5 ----------------------
6 ETSI TS 103 374-2 V1.2.1 (2017-01)
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 accordance 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 applies. 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 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 Telecommunications 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 (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 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 Conformance
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: 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".
[10] IETF RFC 4006: "Diameter Credit-Control Application".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 374-2 V1.2.1 (2017-01)
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 applies. 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 necessary 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]
and 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, the 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 that 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 the Diameter Agent is not explicitly depicted as it is seen as a transparent message handler for
conformance testing purposes.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 374-2 V1.2.1 (2017-01)
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 the CDF.
SUT or
TS or
(TS)
(SUT)
Rf
CTF
CDF

Figure 1: Test configuration CF_1Rf
SUT
TS
TS
Gm
Rf
CDF
UE1
CTFs

Figure 2: Test configuration CF_1Rf1Gm

SUT
TS
TS
Gm
UE
Rf
CDF
CTFs
Mw
I-CSCF

Figure 3: Test configuration CF_1Rf1Gm1Mw

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 374-2 V1.2.1 (2017-01)
SUT
TS
TS
Gm
UE
Rf
CDF
CTFs
Ic
IBCF

Figure 4: Test configuration CF_1Rf1Gm1Ic

SUT
TS
TS
Isc Rf
S-CSCF CDF
CTFs

Figure 5: Test configuration CF_1Rf1Isc

SUT TS
TS
Gm Rf
UE
CDF
CTFs
Mw
Rf
CDF
I-CSCF

Figure 6: Test configuration CF_2Rf1Gm1Mw
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 374-2 V1.2.1 (2017-01)
4.3 Test configurations using Ro interface
The Ro interface is located between a CTF equipment hosted by an MRFC or a SIP AS or an IMS GW and the OCF.
SUT or
TS or
(TS)
(SUT)
Ro
CTF
OCF

Figure 7: Test configuration CF_1Ro
SUT or
TS or
(TS)
(SUT)
Ro
OCF


CTF
Ro
OCF

Figure 8: Test configuration CF_2Ro
SUT
TS
TS
Gm
UE
Ro
OCF
CTFs
Mw
I-CSCF

Figure 9: Test configuration CF_1Ro1Gm1Mw
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 374-2 V1.2.1 (2017-01)
SUT
TS
TS
Gm
UE
Ro
OCF
CTFs
Ic
IBCF

Figure 10: Test configuration CF_1Ro1Gm1Ic
SUT
TS TS
Isc Ro
OCF
S-CSCF CTFs

Figure 11: Test configuration CF_1Ro1Isc
SUT
TS
TS
Gm
Ro
UE
OCF
CTFs
Mw
Ro
I-CSCF OCF

Figure 12: Test configuration CF_2Ro1Gm1Mw
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 374-2 V1.2.1 (2017-01)
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
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 (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 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. Table 2 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

---------------------- Page: 12 ----------------------
13 ETSI TS 103 374-2 V1.2.1 (2017-01)
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
CC-Request received due to IP-CAN
session establishment
Configuration One of the test configurations as described in clauses 4.2 and CF_1Rf
4.3
Initial
Free text description of the condition that the IUT has reached The IUT has received AF provisions
condition before the test purpose applies information about the AF signalling
(optional) 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 having sent an AC-Request
if the action is sending/receiving
  see below for message structure
Stimulus , see below for 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 Capabilities-Exchange-Answer, etc.
structure (see note 2)

a) containing a(n) AVP Vendor-Id, etc.
b) indicating
and back to a) or b) (see note 3)
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 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 this will be expressed like this:
sends/receives Message 1
 containing AVP1
  containing AVP3
  indicating .
 containing AVP2
  indicating .

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 reference. 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

---------------------- Page: 13 ----------------------
14 ETSI TS 103 374-2 V1.2.1 (2017-01)
5.2.2.1.2 Message Syntax
TP_RF_CDF_MS_01 Standards Reference: PICS item:
Clause 6.2.3 - Table 6.2.3 and
IETF RFC 4005 [9], clause 3.9¶2 and
Clause 3.10¶3
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 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 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-Record-Number AVP
 containing an Acct-Application-Id AVP
  indicating the value 3.
Comments:


TP_RF_CDF_MS_02 Standards Reference: PICS item:
IETF RFC 3588 [8], clause 3¶2 and ¶4
Summary: Verify that the IUT can successfully process all mandatory AVPs in an AC-Request
received due to Charging Data Transfer 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
 containing 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:

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 103 374-2 V1.2.1 (2017-01)
5.2.2.1.3 Type of Charging
TP_RF_CDF_TC_01 Standards Reference: PICS item:
Clause 6.1.1/Steps1 to 4 - Table 6.2.2/3 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
Test 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
  optionally 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
  indicating 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: PICS item:
Clause 6.1.2/Steps 2 to 4 - Table 6.2.2/3 A.3/1.2
Summary: Verify that the 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 Accounting-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

---------------------- Page: 15 ----------------------
16 ETSI TS 103 374-2 V1.2.1 (2017-01)
TP_RF_CDF_TC_03 Standards Reference: PICS item:
Clause 6.2.2/Steps 5 to 7 - Table 6.2.2/3 A.3/1.2
Summary:
Verify that the IUT can successfully process an AC-Request [Interim] 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 INTERIM_RECORD
 containing an Accounting-Record-Number AVP
 containing an Event-Timestamp AVP
 optionally containing a Service-Information AVP
  indicating a Subscription-Id AVP
  indicating an IMS-Information AVP
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 INTERIM_RECORD
 containing an Accounting-Record-Number AVP
 optionally containing an Acct-Interim-Interval AVP
  indicating the desired intermediate charging interval.
Comments:
Preamble action: ACR, ACA [Start] are exchanged.
Postamble action: ACR [Stop] is sent.

TP_RF_CDF_TC_04 Standards Reference: PICS item:
Clause 6.2.2/Steps 9 to 11 - Table 6.2.2/3 A.3/1.2
Summary: Verify that the IUT can successfully process an AC-Request [Stop] 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 STOP_RECORD
 containing an Accounting-Record-Number AVP
 containing an Event-Timestamp AVP
 optional
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.