ETSI TS 101 595-2 V6.1.1 (2019-01)

Core Network and Interoperability Testing (INT); Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP™ Release 12); Part 2: Test Suite Structure and Test Purposes (TSS&TP)

RTS/INT-00153-2

General Information

• Status: Published
• Publication Date: 07-Jan-2019
• Technical Committee: INT - Core Network and Interoperability Testing
• Current Stage: 12 - Completion
• Due Date: 14-Dec-2018
• Completion Date: 08-Jan-2019

Standards Content (Sample)

ETSI TS 101 595-2 V6.1.1 (2019-01)






TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Malicious Communication Identification (MCID)
using IP Multimedia (IM) Core Network (CN) subsystem;
Conformance Test Specification (3GPP™ Release 12);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
Release 12 2 ETSI TS 101 595-2 V6.1.1 (2019-01)



Reference
RTS/INT-00153-2
Keywords
conformance, IMS, MCID, testing, 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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
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.

© 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 ----------------------
Release 12 3 ETSI TS 101 595-2 V6.1.1 (2019-01)
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 Suite Structure (TSS) . 6
4.0 Test Suite Structure table . 6
4.1 Configuration . 7
4.1.0 Introduction. 7
4.1.1 Testing of the AS . 7
4.1.2 Testing of the UE . 8
5 Test Purposes (TP) . 8
5.1 Introduction . 8
5.1.1 TP naming convention . 8
5.1.2 Test strategy . 8
5.2 TPs for Malicious Communication Identification (MCID) . 9
5.2.1 Actions at the AS of the terminating user . 9
5.2.2 Actions at the destination UE . 16
5.3 Interaction with other services . 18
5.3.1 Explicit Communication Transfer (ECT) . 18
History . 19


ETSI

---------------------- Page: 3 ----------------------
Release 12 4 ETSI TS 101 595-2 V6.1.1 (2019-01)
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).
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 ----------------------
Release 12 5 ETSI TS 101 595-2 V6.1.1 (2019-01)
1 Scope
The present document is part 2 of a multi-part deliverable covering Malicious Communication Identification (MCID)
using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)".
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 124 616 (V12.1.0): "Digital cellular telecommunications system (Phase 2+); Universal
Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification
(MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP
TS 24.616 version 12.1.0 Release 12)".
[2] ETSI TS 101 595-1: "Core Network and Interoperability Testing (INT); Malicious
Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem;
Conformance Test Specification (3GPP™ Release 12); Part 1: Protocol Implementation
Conformance Statement (PICS)".
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.
[i.1] IETF RFC 3966: "The tel URI for Telephone Numbers".
[i.2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
ETSI

---------------------- Page: 5 ----------------------
Release 12 6 ETSI TS 101 595-2 V6.1.1 (2019-01)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 124 616 [1] and the following apply:
communication information: information collected and registered by the MCID service
identity information: all the information identifying a user, including trusted (network generated) and/or untrusted
(user generated) identities
NOTE: See IETF RFC 3966 [i.1]/IETF RFC 3986 [i.2].
3.2 Symbols
For the purposes of the present document, the symbols given in ETSI TS 124 616 [1] apply.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 124 616 [1] and the following apply:
AS Application Server
ID user IDentification
IM IP Multimedia
IMS IP Multimedia Subsystem
IP Internet Protocol
ISC IP multimedia subsystem Service Control
MCID Malicious Call Identification
MIME Multipurpose Internet Mail Extensions
SIP Session Initiation Protocol
TP Test Purposes
TSS Test Suite Structure
UE User Equipment
URI Uniform Resource Identifier
XML eXtensible Markup Language
4 Test Suite Structure (TSS)
4.0 Test Suite Structure table
Table 4.0-1: Test Suite Structure (TSS)
MCID
terminating_AS MCID_N01_xxx
destination_UE MCID_U01_xxx
interaction ECT MCID_N02_xxx

ETSI

---------------------- Page: 6 ----------------------
Release 12 7 ETSI TS 101 595-2 V6.1.1 (2019-01)
4.1 Configuration
4.1.0 Introduction
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as
described in ETSI TS 124 616 [1]. The stage 3 description describes the requirements for several network entities and
also the requirements regarding for terminal devices. Therefore several interfaces (reference points) are addressed to
satisfy the test of the different entities.
Therefore to test the appropriate entities the configurations below are applicable.
4.1.1 Testing of the AS
The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for
testing.

Figure 4.1.1-1: Applicable interface to test AS functionalities
If the ISC interface is not accessible it is also possible to perform the tests of the AS using any NNI (Mw, Mg, Mx)
interface (see figure 4.1.1-2). In case only the Gm interface is accessible this interface can be used instead for testing,
but the verification of all requirements may not be possible.

Figure 4.1.1-2: Applicable interfaces for tests using a (generic) NNI interface
ETSI

---------------------- Page: 7 ----------------------
Release 12 8 ETSI TS 101 595-2 V6.1.1 (2019-01)
4.1.2 Testing of the UE
There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating
user equipment. Therefore the test configuration below has been chosen.

Figure 4.1.2-1: Applicable configuration to test UE functionalities
5 Test Purposes (TP)
5.1 Introduction
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 5.1.1-1).
Table 5.1.1-1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "MCID"
= type of IUT: U User equipment
N Network entity
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)

5.1.2 Test strategy
As the base standard ETSI TS 124 616 [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 101 595-1 [2]. The criteria applied include
the following:
• whether or not a test case can be built from the TP is not considered.
ETSI

---------------------- Page: 8 ----------------------
Release 12 9 ETSI TS 101 595-2 V6.1.1 (2019-01)
5.2 TPs for Malicious Communication Identification (MCID)
5.2.1 Actions at the AS of the terminating user
TSS TP MCID reference Selection expression
MCID/terminating_AS MCID_N01_001 4.5.2.5.2 PICS 4.5.1/2 AND
PICS 4.7.1/2
Test purpose
The AS holds the call state after a BYE from the originating UE
Ensure that the AS holds the confirmed call state while T is running, if MCID is subscribed by the called user
MCID-BYE
and a BYE was received from the originating user UE. When T is expired, the BYE is forwarded to the
MCID-BYE
terminating UE.
Preconditions: Called user shall be configured with MCID subscription with Temporary Mode
SIP header values:
Comments:
Test equipment (ISC) AS Test equipment (Gm)
INVITE   INVITE
100 Trying   100 Trying
180 Ringing   180 Ringing
200 OK INVITE   200 OK INVITE
ACK   ACK

T started
BYE 
MCID-BYE
200 OK BYE 

T expires

MCID-BYE
   BYE
   200 OK BYE

TSS TP MCID reference Selection expression
MCID/terminating_AS MCID_N01_002 4.5.2.5.2 PICS 4.5.1/2 AND
PICS 4.7.1/2
Test purpose
The AS holds the early dialogue state after a CANCEL from the originating UE
Ensure that the AS hol
...