|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
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 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 1 ETSI TS 124 616 V15.0.0 (2018-07)
Reference
RTS/TSGC-0124616vf00
Keywords
GSM,LTE,UMTS
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 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
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 2018.
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 protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 2 ETSI TS 124 616 V15.0.0 (2018-07)
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 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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: 3 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 3 ETSI TS 124 616 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Malicious Communication Identification (MCID) . 7
4.1 Introduction . 7
4.2 Description . 8
4.2.1 General description . 8
4.3 Operational requirements . 8
4.3.1 Provision/withdrawal . 8
4.3.2 Requirements on the originating network side. 8
4.3.3 Void . 8
4.3.4 Requirements on the terminating network side . 8
4.4 Coding requirements . 8
4.5 Signalling requirements . 9
4.5.1 Activation/deactivation . 9
4.5.2 Invocation and operation . 9
4.5.2.1 Actions at the originating UE . 9
4.5.2.2 Void. 10
4.5.2.3 Void. 10
4.5.2.4 Void. 10
4.5.2.5 Actions at the AS of the terminating user . 10
4.5.2.5.0 General . 10
4.5.2.5.1 Subscriber has a permanent subscription . 10
4.5.2.6 Void. 11
4.5.2.7 Void. 11
4.5.2.8 Void. 11
4.5.2.9 Void. 11
4.5.2.10 Void. 11
4.5.2.11 Void. 11
4.5.2.12 Actions at the destination UE . 11
4.5.2.12.0 Subscriber has a permanent subscription . 11
4.5.2.12.1 Subscriber has a temporary subscription . 11
4.6 Interaction with other services . 12
4.6.1 Communication Hold (HOLD) . 12
4.6.2 Terminating Identification Presentation (TIP) . 12
4.6.3 Terminating Identification Restriction (TIR) . 12
4.6.4 Originating Identification Presentation (OIP) . 12
4.6.5 Originating Identification Restriction (OIR) . 12
4.6.6 Conference (CONF) . 12
4.6.7 Communication Diversion Services (CDIV) . 12
4.6.7.1 Communication Forwarding Unconditional (CFU) . 12
4.6.7.2 Communication Forwarding Busy (CFB) . 12
4.6.7.3 Communication Forwarding No Reply (CFNR) . 12
4.6.7.4 Communication Forwarding on Not Logged-In (CFNL) . 12
4.6.7.5 Communication Deflection (CD) . 13
4.6.8 Call Waiting (CW) . 13
4.6.9 Anonymous Communication Rejection and Communication session Barring (ACR/CB) . 13
4.6.10 Explicit Communication Transfer (ECT) . 13
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 4 ETSI TS 124 616 V15.0.0 (2018-07)
4.6.11 Enhanced Calling Name (eCNAM) . 13
4.7 Interactions with other networks . 13
4.7.1 Void . 13
4.7.2 Void . 13
4.7.3 Void . 13
4.8 Parameter values (timers) . 13
Annex A (informative): Signalling Flows . 14
A.1 MCID invocation . 14
A.2 Identity information not present in the initial request . 15
A.3 MCID invocation during the call in temporary mode. 16
Annex B (informative): Example of filter criteria . 20
B.1 Terminating S-CSCF . 20
B.2 Originating S-CSCF . 20
Annex C: (void) . 21
Annex D (informative): Void . 22
Annex E (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 5 ETSI TS 124 616 V15.0.0 (2018-07)
Foreword
This Technical Specification (TS) was been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN) and originally published as
rd
ETSI TS 183 016 [12]. It was transferred to the 3 Generation Partnership Project (3GPP) in December 2007.
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 6 ETSI TS 124 616 V15.0.0 (2018-07)
1 Scope
The present document specifies the stage three Protocol Description of the Malicious Call Communication
Identification (MCID) service based on the stage one and two of ISDN Malicious Call Identification supplementary
service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session
Initiation Protocol (SIP) and the Session Description Protocol (SDP). The MCID service will store session related
information independent of the service requested.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the MCID supplementary service.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 22.173: " IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service
and supplementary services, Stage 1 ".
[2] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[3] Void.
[4] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN);Direct Communication Service in NGN; Service Description
[Endorsement of OMA-ERELD-PoC-V1] NGN DC stage 1".
[5] Void.
[6] Void.
[7] Void.
[8] Void.
[9] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and
message contents".
[10] IETF RFC 3966: "The tel URI for Telephone Numbers".
[11] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[12] ETSI TS 183 016 V2.5.0: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication
Identification (MCID); Protocol specification".
[13] ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Terminology".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 7 ETSI TS 124 616 V15.0.0 (2018-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 22.173 [1], ETSI TS 181 006 [4],
ETSI TR 180 000 [13] and the following apply:
communication information: information collected and registered by the MCID service
identity information: includes all the information (IETF RFC 3966 [10] and IETF RFC 3986 [11]) identifying a user,
including trusted (network generated) and/or untrusted (user generated) identities
trusted identity: network generated user address information
untrusted identity: user generated user address information
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACR Anonymous Communication Rejection
AS Application Server
CB Communication session Barring
CD Communication Deflection
CDIV Communication DIVersion Services
CFB Communication Forwarding Busy
CFNL Communication Forwarding on Not Logged-in
CFNR Communication Forwarding No Reply
CFU Communication Forwarding Unconditional
CONF Conference
CW Call Waiting
ECT Explicit Communication Transfer
HOLD communication Hold
IM IP Multimedia
IMS IP Multimedia Subsystem
IP Internet Protocol
ISDN Integrated Service Digital Network
MCID Malicious Call Identification
MGCF Media Gateway Control Function
OIP Originating Identification Presentation
OIR Originating Identification Restriction
PSTN Public Switched Telephone Network
S-CSCF Service - Call Session Control Function
SDP Session Description Protocol
SIP Session Initiation Protocol
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
UE User Equipment
URI Uniform Resource Identifier
4 Malicious Communication Identification (MCID)
4.1 Introduction
The MCID service will store session related information of incoming communications independent of the service
requested. The following communication information shall be registered:
- Destination Party Identity Information;
- originating Party Identity Information; and
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 8 ETSI TS 124 616 V15.0.0 (2018-07)
- local time and date of the invocation in the network serving the called user.
The communication information shall not be available to the terminal equipment under the control of the called user nor
the originating user. The communication information shall be stored at a location(s) under the control of the network
operator. In order for the MCID service to operate when two networks are involved both networks need to be within the
same trust domain for identity information transfer.
A network subscription option can be provided which allows automatic invocation of MCID service on communications
to the served user which are not answered.
NOTE: The purpose of this option is to allow for registration of communications that ring for a short time only.
A user subscription option can be provided where the MCID service can either be invoked during the active phase of
the communication, or for a limited period after the communication has ceased.
4.2 Description
4.2.1 General description
The Malicious Communication Identification (MCID) service allows the service provider to trace the identity
information of the source of an incoming communication on request of the destination user.
4.3 Operational requirements
4.3.1 Provision/withdrawal
This service shall be provided and withdrawn after pre-arrangement with the service provider, in accordance with
national legal requirements.
This service has two modes: permanent mode and temporary mode. In permanent mode the MCID service is invoked
for all incoming communications, and in temporary mode the MCID service is invoked only for the incoming
communications declared by the served user.
As a network option, the MCID service can be offered with several subscription options. A network providing the
MCID service shall support permanent mode at a minimum. Subscription options are summarized in table 4.3.1.1.
Table 4.3.1.1: Subscription options for MCID services
Subscription options Value
Mode Permanent Mode
Temporary Mode
4.3.2 Requirements on the originating network side
No specific requirements are needed in the originating network.
4.3.3 Void
Void.
4.3.4 Requirements on the terminating network side
No specific requirements are needed in the terminating network.
NOTE: If the subscriber has a permanent or case by case subscription, based on Initial Filter Criteria (IFC) the
INVITE request is forwarded to the AS that provides the MCID service. Annex B provides an example on
how an Initial Filter Criteria (IFC) can be configured.
4.4 Coding requirements
The present clause defines the XML Schema to be used for providing the MCID Request/Response and to invoke the
temporary mode of the MCID Service.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 9 ETSI TS 124 616 V15.0.0 (2018-07)
The application/vnd.etsi.mcid+xml MIME type used to provide request of a missing originating ID and the delivery of
the requested originating id AS of the served user shall be coded as following described:
xmlns="http://uri.etsi.org/ngn/params/xml/simservs/mcid"
targetNamespace="http://uri.etsi.org/ngn/params/xml/simservs/mcid" elementFormDefault="qualified">
XML Schema Definition to the mcid request-response to the Malicious
Communication Identification service
minOccurs="0"/>
minOccurs="0"/>
4.5 Signalling requirements
4.5.1 Activation/deactivation
The MCID service is provisioned only by the network operator. The MCID service is activated at provisioning and de-
activated at withdrawal.
4.5.1a Registration/erasure
The MCID service requires no registration. Erasure is not applicable.
4.5.1b Interrogation
Interrogation of MCID is not applicable.
4.5.2 Invocation and operation
4.5.2.1 Actions at the originating UE
Basic communication procedures according to 3GPP TS 24.229 [2] shall apply.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 24.616 version 15.0.0 Release 15 10 ETSI TS 124 616 V15.0.0 (2018-07)
4.5.2.2 Void
4.5.2.3 Void
4.5.2.4 Void
4.5.2.5 Actions at the AS of the terminating user
4.5.2.5.0 General
The AS shall at the minimum store the following elements of a received INVITE request:
- Destination Party Identity Information included in the Request-URI;
- Originating Party Identity Information included in the P-Asserted-Identity header field, if the
P-Asserted-Identity header field is included in the request;
- local time and date of the invocation in the network serving the called user;
- call diversion information ("cause" SIP URI parameter) received in the History-Info header field, if included in
the request;
- Referred-By header field when available;
- Contact header field;
- To header field; and
- From header field.
NOTE: The Originating Party Identity Information included in the P-Asserted-Identity header field is always
present in the INVITE request if the request is originated in a trusted network.
If the INVITE request does not contain the information of the originating party, the AS shall send an INFO request
including an Identification Request MIME body.
When receiving the INFO request containing identification information, the AS shall in addition to the already stored
information elements of the earlier received INVITE request, at the minimum store the information as received in the
body of the INFO request.
4.5.2.5.1 Subscriber has a permanent subscription
The AS shall register stored information. The exact procedure to register the information is implementation dependent
and out of scope of the present document.
4.5.2.5.2 Subscriber has a temporary subscription
The AS shall store the required elements of a received INVITE request for a limited period after the communication has
been released. If an initial INVITE request as
...