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)

RTS/INT-00114-2

General Information

• Status: Published
• Publication Date: 28-Jun-2015
• Technical Committee: INT - Core Network and Interoperability Testing
• Current Stage: 12 - Completion
• Due Date: 17-Jul-2015
• Completion Date: 29-Jun-2015

Standards Content (Sample)

ETSI TS 103 261-2 V1.2.1 (2015-06)






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

---------------------- Page: 1 ----------------------
2 ETSI TS 103 261-2 V1.2.1 (2015-06)



Reference
RTS/INT-00114-2
Keywords
diameter, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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 2015.
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 261-2 V1.2.1 (2015-06)
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 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Test Suite Structure (TSS) and Test Purposes (TP) . 6
4.1 Test Suite Structure . 6
4.1.1 TP naming convention . 6
4.1.2 Test strategy . 6
4.1.3 TP structure . 6
4.2 Test Purposes . 7
4.2.0 PICS references . 7
4.2.1 MME Role . 7
4.2.1.0 Test Selection . 7
4.2.1.1 Update Location . 8
4.2.1.2 Cancel Location . 10
4.2.1.3 Purge UE . 11
4.2.1.4 Insert Subscriber Data . 12
4.2.1.5 Delete Subscriber Data . 18
4.2.1.6 Authentication Information Retrieval . 19
4.2.1.7 Reset . 20
4.2.1.8 Notification . 21
4.2.2 HSS Role . 21
4.2.2.0 Test Selection . 21
4.2.2.1 Update Location . 21
4.2.2.2 Cancel Location . 26
4.2.2.3 Purge UE . 28
4.2.2.4 Insert Subscriber Data . 32
4.2.2.5 Delete Subscriber Data . 35
4.2.2.6 Authentication Information Retrieval . 36
4.2.2.7 Reset . 43
4.2.2.8 Notification . 43
History . 45

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 261-2 V1.2.1 (2015-06)
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 (http://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 covering the test specifications for the Diameter protocol on
the S6a interface, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
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", "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 261-2 V1.2.1 (2015-06)
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 S6a interface as specified in ETSI TS 129 272 [1] in compliance with the relevant
requirements and in accordance with the relevant guidance 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 references, 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 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 (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 Implementation 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 framework -- 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 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
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 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 261-2 V1.2.1 (2015-06)
3 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-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 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 organized according to the TSS.
Table 1: TP identifier naming convention scheme
Identifier: ___
= Test Purpose: fixed to "TP"
= type of IUT: MME or HSS
= 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 requirements 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 checkable. 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

---------------------- Page: 6 ----------------------
7 ETSI TS 103 261-2 V1.2.1 (2015-06)
Table 2: Structure of a single TP
TP part Text 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 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 [6], clause 5.6 Open state
and/or further actions before stimulus
having sent an AA-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, etc.
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 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 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 .

4.2 Test Purposes
4.2.0 PICS references
All PICS items referred to in this clause are as specified 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
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 261-2 V1.2.1 (2015-06)
4.2.1.1 Update Location
Test Selection: IUT supports location management procedures; PICS A.3/1.
TP_MME_UL_01 Standards Reference: PICS item:
5.2.1.1.1 and 7.2.3
Summary: Verify that the IUT can indicate request for update location information to inform HSS
about 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 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
 containing a Visited-PLMN-ID AVP
Comments:

TP_MME_UL_02 Standards Reference: PICS item:
5.2.1.1.2¶4 A.2/1.2
Summary: Verify that the IUT due to an 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_UL_03 Standards Reference: PICS item:
5.2.1.1.2¶5
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-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-Realm AVP
 containing a User-Name AVP
 containing a RAT-Type AVP
 containing a ULR-Flags AVP
  with S6a-indicator bit set
  with Initial-Attach-Indicator bit set
 containing a Visited-PLMN-ID AVP
Comments:

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 261-2 V1.2.1 (2015-06)
TP_MME_UL_04 Standards Reference: PICS item:
5.2.1.1.2¶6 A.2/1.1
Summary:
Verify that the IUT, when subscriber data are already available due to previous location
update, successfully 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
  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 set
  with Skip-Subscriber-Data bit set
 containing a Visited-PLMN-ID AVP
Comments:

TP_MME_UL_05 Standards Reference: PICS item:
5.2.1.1.2¶7 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 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 an ID-Request
sends an ID-Answer
Comments:

TP_MME_UL_06 Standards Reference: PICS item:
5.2.1.1.2¶7 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 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 an DS-Request
sends an DS-Answer
Comments:


TP_MME_UL_07 Standards Reference: PICS item:
5.2.1.1.2¶10 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 the 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

---------------------- Page: 9 ----------------------
10 ETSI TS 103 261-2 V1.2.1 (2015-06)
4.2.1.2 Cancel Location
Test Selection: IUT supports cancel location procedures; PICS A.3/2.
TP_MME_CL_01 Standards Reference: PICS item:
Table 5.2.1.2.1/2 and 5.2.1.2.2¶2 and
7.2.8
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 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
 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
  indicating DIAMETER_SUCCESS
Comments:

TP_MME_CL_02 Standards Reference: PICS item:
Table 5.2.1.2.1/2 and 5.2.1.2.2¶3 and
7.2.8
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 shall
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 Destination-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 an Origin-Host AVP
 containing an Origin-Realm AVP
 containing a Result-Code AVP
  indicating DIAMETER_SUCCESS
Comments:

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 261-2 V1.2.1 (2015-06)
4.2.1.3 Purge UE
Test Selection: IUT supports Purge UE procedures; PICS A.3/3.
TP_MME_PUE_01 Standards Reference: PICS item:
Table 5.2.1.3.1/1 and 7.2.13
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-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
Comments:

TP_MME_PUE_02 Standards Reference: PICS item:
5.2.1.3.2¶1
Summary:
Verify that the IUT makes use of UE Purge procedure and sets appropriate flag when the
subscription profile is deleted from database or after long UE inactivity.
Test purpose: Ensure that the IUT
to indicate a request for purge UE procedure,
sends a PU-Request
 containing a PUR-Flags AVP
  with "UE Purged in MME" bit set
Comments:


TP_MME_PUE_03 Standards Reference: PICS item:
5.2.1.3.2¶3 A.2/1.1
Summary: Verify that the IUT makes use of UE Purge procedure and sets appropriate flags when
the subscription profile is deleted from database or after long UE inactivity on all
registered accesses.
Test purpose:
Ensure that the IUT
to indicate a request for purge UE procedure,
sends a PU-Request
 containing a PUR-Flags AVP
  with "UE Purged in MME" bit set
  with "UE Purged in SGSN" bit set
Comments:

TP_MME_PUE_04 Standards Reference: PICS item:
5.2.1.3.2¶3 A.2/1.1 and A.4/13
Summary: Verify that in case when HSS indicates support for Partial Purge feature IUT may also
indicate a Purge of the UE in only one of the serving nodes in the combined node (either
in the MME or in the SGSN).
Test purpose:
Ensure that the IUT
to indicate a request for update location information,
sends a UL-Request
on receipt of a UL-Answer
 containing a Supported-Features AVP
  containing a Vendor-Id AVP
  containing a Feature-List-ID AVP
  containing a Feature-List AVP
  indicating Partial Purge
sends a PU-Request
 containing a PUR-Flags AVP
  either
  with "UE Purged in MME" bit set or
  with "UE Purged in SGSN" bit set
Comments:

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 261-2 V1.2.1 (2015-06)
4.2.1.4 Insert Subscriber Data
Test Selection: IUT supports subscriber data handling procedures; PICS A.3/4.
TP_MME_ISD_01 Standards Reference: PICS item:
Table 5.2.2.1.1/2 and 5.2.2.1.2¶4 and
7.2.10
Summary: Verify that the IUT when receiving an ID-Request checks whether the IMSI is known and
returns Insert Subscriber Data response with all mandatory AVPs and with appropriate
result code.
Test purpose: Ensure that the IUT
on receipt of an ID-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
 containing a User-Name AVP
  indicating known IMSI
 containing a Subscription-Data AVP,
sends an ID-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
  indicating DIAMETER_SUCCESS
Comments:

TP_MME_ISD_02 Standards Reference: PICS item:
5.2.2.1.2¶1,2 and 7.4.3
Summary: Verify that the IUT when receiving an ID-Request checks whether the IMSI is known and
if not the IUT returns Insert Subscriber Data response with appropriate result code.
Test purpose:
Ensure that the IUT
on receipt of an ID-Request
 containing a User-Name AVP
  indicating not known IMSI,
sends an ID-Answer
 not containing a Result-Code AVP
 containing an Experimental-Result AVP
  containing an Experimental-Result-Code AVP
  indicating DIAMETER_ERROR_USER_UNKNOWN
Comments:


ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 261-2 V1.2.1 (2015-06)
TP_MME_ISD_03 Standards Reference: PICS item:
5.2.2.1.2¶18
Summary:
Verify that the IUT when receiving an ID-Request with IDR-Flags with "T-ADS Data
Request" bit set and when UE is in attached state the IUT returns Insert Subscriber Data
response with time stamp of UE's most recent radio contact, and the associated RAT
Type, and an indication of whether or not IMS Voice over PS is supported.
Test purpose: Ensure that the IUT
on receipt of an ID-Request
 containing a User-Name AVP
  indicating known IMSI
 containing an IDR-Flags AVP
  with T-ADS Data Request bit set,
sends an ID-Answer
 containing an IMS-Voice-Over-PS-Sessions-Supported AVP
 containing a Last-UE-Activity-Time AVP
 containing a RAT-Type AVP
 containing a Result-Code AVP
  indicating DIAMETER_SUCCESS
Comments:

TP_MME_ISD_04 Standards Reference: PICS item:
5.2.2.1.2¶18
Summary: Verify that the IUT when receiving an ID-Request with IDR-Flags with "T-ADS Data
Request" bit set and when UE is in detached state the IUT returns Insert Subscriber Data
response not including any of T_ADS IEs.
Test purpose: Ensure that the IUT
on receipt of
...