|
TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Diameter Conformance testing for the Sh/Dh interfaces;
(3GPP™ Release 13);
Part 2: Test Suite Structure (TSS) and Test Purposes (TP)
---------------------- Page: 1 ----------------------
2 ETSI TS 103 571-2 V1.1.1 (2019-04)
Reference
DTS/INT-00138-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:
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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
If you find errors in the present document, please send your comment to one of the following services:
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.
© ETSI 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI TS 103 571-2 V1.1.1 (2019-04)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Test configurations . 6
4.1 Introduction . 6
4.2 Test configurations using the Sh interface . 7
4.3 Test configurations using the Dh interface . 8
5 Test Suite Structure (TSS) and Test Purposes (TP) . 9
5.1 Test Suite Structure . 9
5.1.1 TP naming convention . 9
5.1.2 Test strategy . 9
5.1.3 TP structure . 9
5.2 Test Purposes . 11
5.2.1 PICS references . 11
5.2.2 Sh interface . 11
5.2.2.1 HSS Role . 11
5.2.2.1.1 Test selection . 11
5.2.2.1.2 Message Syntax . 11
5.2.2.1.3 User Data . 12
5.2.2.1.4 Profile Update . 24
5.2.2.1.5 Subscription to Notification. 33
5.2.2.1.6 Push Notification . 38
5.2.2.2 AS and OSA SCS Role . 39
5.2.2.2.1 Test selection . 39
5.2.2.2.2 Message Syntax . 39
5.2.2.2.3 User Data . 40
5.2.2.2.4 Profile Update . 41
5.2.2.2.5 Subscription to Notification. 41
5.2.2.2.6 Push Notification . 42
5.2.3 Dh interface . 43
5.2.3.1 SLF Role . 43
5.2.3.1.1 Test selection . 43
5.2.3.1.2 User Data . 43
5.2.3.1.3 Profile Update . 44
5.2.3.1.4 Subscription to Notification. 44
5.2.3.2 AS and OSA SCS Role . 45
5.2.3.2.1 Test selection . 45
5.2.3.2.2 User Data . 45
5.2.3.2.3 Profile Update . 45
5.2.3.2.4 Subscription to Notification. 46
History . 47
ETSI
---------------------- Page: 3 ----------------------
4 ETSI TS 103 571-2 V1.1.1 (2019-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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 [3].
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: 4 ----------------------
5 ETSI TS 103 571-2 V1.1.1 (2019-04)
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 Sh/Dh interfaces as specified in ETSI TS 129 328 [1] and ETSI TS 129 329 [2] in compliance
with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5] and ETSI
ETS 300 406 [6].
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 129 328 (V13.10.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) Subsystem Sh
interface; Signalling flows and message contents (3GPP TS 29.328 version 13.10.0 Release 13)".
[2] ETSI TS 129 329 (V13.1.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter
protocol; Protocol details (3GPP TS 29.329 version 13.1.0 Release 13)".
[3] ETSI TS 103 571-1: "Core Network and Interoperability Testing (INT); Diameter Conformance
TM
testing for the Sh/Dh interfaces; (3GPP Release 13); Part 1: Protocol Implementation
Conformance Statement (PICS)".
[4] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 1: General concepts".
[5] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 7: Implementation Conformance Statements".
[6] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[7] IETF RFC 3588: "Diameter Base Protocol".
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.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI TS 103 571-2 V1.1.1 (2019-04)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 129 328 [1], ETSI TS 129 329 [2] and the
following apply:
Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [4].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [4].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [4].
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 129 328 [1], ETSI TS 129 329 [2] and
the following apply:
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: Sh and Dh.
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: 6 ----------------------
7 ETSI TS 103 571-2 V1.1.1 (2019-04)
4.2 Test configurations using the Sh interface
The Sh interface is located between an AS or OSA SCS and the HSS.
SUT or
TS or
(TS)
(SUT)
Sh
AS -
HSS
OSA
SCS
Figure 1: Test configuration CF_1Sh
NOTE 1: Sh interface (DIAMETER protocol) is located between an HSS and AS or between an HSS and OSA
SCS.
SUT
TS
TS
AS
Sh Isc
CSCF
HSS OSA-
SCS
Figure 2: Test configuration CF_1Sh1Isc
NOTE 2: Within figure 2 CSCF represents S-CSCF component. Isc interface (SIP protocol) is located between a
AS and S-CSCF. Sh interface (DIAMETER protocol) is located between an HSS and as or between an
HSS and OSA_SCS.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI TS 103 571-2 V1.1.1 (2019-04)
4.3 Test configurations using the Dh interface
The Dh interface is located between an AS or OSA SCS and the SLF.
SUT or
TS or
(TS)
(SUT)
Dh
AS -
SLF
OSA
SCS
Figure 3: Test configuration CF_1Dh
SUT
TS
TS
SLF
Dh
AS
Isc
CSCF
OSA
Sh
SCS
HSS
Figure 4: Test configuration CF_1Dh1Sh or CF_1Dh1Sh1Isc
NOTE: Within figure 4 CSCF represents S-CSCF component. Isc interface (SIP protocol) is located between an
AS and S-CSCF. The Sh interface (DIAMETER protocol) is located between an HSS and AS or between
an HSS and OSA-SCS. The Dh interface (DIAMETER protocol) is located between an SLF and AS or
between an SLF and OSA-SCS.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI TS 103 571-2 V1.1.1 (2019-04)
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: SH or DH
= type of IUT: AS, OSA SCS, HSS or SLF
= group MS Message Syntax
UD User Data
PU Profile Update
SN Subscription to Notification
PN Push Notification
= sequential number (01 to 99)
5.1.2 Test strategy
As the base standards in ETSI TS 129 328 [1] and ETSI TS 129 329 [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 571-1 [3].
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: 9 ----------------------
10 ETSI TS 103 571-2 V1.1.1 (2019-04)
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
UD-Request received due to User-
Identity.
Configuration One of the test configurations as described in clauses 4.2 and CF_1Sh
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 [7] clause 5.6 Open state
and/or further actions before stimulus having sent an PU-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 [7] and in
ETSI TS 129 329 [2], clauses 6.1.1, 6.1.2, 6.3.1 and 6.3.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 .
ETSI
---------------------- Page: 10 ----------------------
11 ETSI TS 103 571-2 V1.1.1 (2019-04)
5.2 Test Purposes
5.2.1 PICS references
All PICS items referred to in this clause are as specified in ETSI TS 103 571-1 [3] 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 Sh interface
5.2.2.1 HSS Role
5.2.2.1.1 Test selection
The IUT takes the role of the HSS; PICS A.2/3 and applicable test configuration is CF_1Sh if not specified differently
in the TP.
HSS shall be provisioned for all specified tests.
5.2.2.1.2 Message Syntax
TP_SH_HSS_MS_01 Standards Reference: PICS item:
Clause 6 paragraph.2
Summary: Verify that the IUT sends the appropriate Result-Code AVP when the mandatory User-
Identity AVP is absent.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
not containing a User-Identity AVP
containing a Data-Reference AVP
sends a UD-Answer
containing a Session-ID AVP
containing a Result-Code AVP
indicating DIAMETER_MISSING_AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Failed AVP
indicating missing Information Element.
Comments:
ETSI
---------------------- Page: 11 ----------------------
12 ETSI TS 103 571-2 V1.1.1 (2019-04)
5.2.2.1.3 User Data
TP_SH_HSS_UD_01 Standards Reference: PICS item:
Clauses 6.1.1 and 6.1.1.1/last paragraph
and
Table 6.1.1.1 and Table 6.1.1.2
Summary: Verify that the IUT successfully processes all mandatory AVPs in a UD-Request if
requested data exists or if there are valid empty data elements and returns a UD-Answer
containing the Result-Code AVP with DIAMETER_SUCCESS.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
containing a Data-Reference AVP
sends a UD-Answer
containing a Session-ID AVP
containing a Result-Code AVP
indicating DIAMETER_SUCCESS
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP.
Comments:
TP_SH_HSS_UD_02 Standards Reference: PICS item:
Clause 6.1.1.1 (Item 1)
Summary: Verify that the IUT checks in the AS permission list if the requested user data is allowed
to be read and if one or more Data Reference in the request are not allowed the IUT
returns a UD-Answer with appropriate experimental result code.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
containing a Data-Reference AVP
sends a UD-Answer
containing a Session-ID AVP
containing an Experimental-Result AVP
indicating DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP.
Comments:
ETSI
---------------------- Page: 12 ----------------------
13 ETSI TS 103 571-2 V1.1.1 (2019-04)
TP_SH_HSS_UD_03 Standards Reference: PICS item:
Clause 6.1.1.1 (Item 2)
Summary: Verify that the IUT checks if the User Identity for which data is asked does not exist and
the IUT returns the UD-Answer with the appropriate experimental result code.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
indicating not existing user
containing a Data-Reference AVP
sends a UD-Answer
containing a Session-ID AVP
containing an Experimental-Result AVP
indicating DIAMETER_ERROR_USER_UNKNOWN
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP.
Comments:
TP_SH_HSS_UD_04 Standards Reference: PICS item:
Clause 6.1.1.1 (Item 2a)
Summary: Verify that the IUT checks the Private Identity and if it does not correspond to the
IMPU/MSISDN and the IUT returns a UD-Answer with the appropriate experimental
result code.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
indicating not related Private Identity
containing a Data-Reference AVP
sends a UD-Answer
containing a Session-ID AVP
containing an Experimental-Result AVP
indicating DIAMETER_ERROR_IDENTITIES_DONT_MATCH
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP.
Comments:
ETSI
---------------------- Page: 13 ----------------------
14 ETSI TS 103 571-2 V1.1.1 (2019-04)
TP_SH_HSS_UD_05 Standards Reference: PICS item:
Clause 6.1.1.1 (Item 3) and Table 7.6.1
Summary: Verify that the IUT checks the type of User Identity and if it does not apply according to
the Table 7.6.1 due to the Data-Reference indicated in the request the IUT, returns a
UD-Answer with the appropriate experimental result code.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
indicating MSISDN
containing a Data-Reference AVP
indicating RepositoryData (0)
containing a Service-Indication AVP
sends a UD-Answer
containing a Session-ID AVP
containing an Experimental-Result AVP
indicating DIAMETER_ERROR_OPERATION_NOT_ALLOWED
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP.
Comments:
TP_SH_HSS_UD_06 Standards Reference: PICS item:
Clause 6.1.1.1 (Item 3a)
Summary: Verify that the IUT, when the data-reference is IPAddressSecureBindingInformation (22)
and the User Identity is an IMS Public User Identity that is shared between multiple
Private User Identities, returns a UD-Answer with the appropriate experimental result
code.
Test purpose: Ensure that the IUT
on receipt of a UD-Request
containing a Session-ID AVP
containing a Vendor-Specific-Application-Id AVP
containing an Auth-Session-State AVP
containing an Origin-Host AVP
containing an Origin-Realm AVP
containing a Destination-Realm AVP
containing a User-Identity AVP
indicating IMS Public User Identity
containing a Data-Reference AVP
indicating IPAddressSecurityBindingInformation (22)
sends a UD-Answer
containing a Session-ID AVP
containing an Experimental-Result AVP
indicating DIAMETER_ERROR_OPERATION_NOT_ALLOWED
containing a
...