ETSI TS 124 341 V18.0.0 (2024-05)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Support of SMS over IP networks; Stage 3 (3GPP TS 24.341 version 18.0.0 Release 18)

RTS/TSGC-0124341vi00

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 22-May-2024

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Support of SMS over IP networks;
Stage 3
(3GPP TS 24.341 version 18.0.0 Release 18)


3GPP TS 24.341 version 18.0.0 Release 18 1 ETSI TS 124 341 V18.0.0 (2024-05)

Reference
RTS/TSGC-0124341vi00
Keywords
5G,GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://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 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
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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2024.
All rights reserved.
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 2 ETSI TS 124 341 V18.0.0 (2024-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 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.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under https://webapp.etsi.org/key/queryform.asp.
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
3GPP TS 24.341 version 18.0.0 Release 18 3 ETSI TS 124 341 V18.0.0 (2024-05)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 9
4 Overview of SMS over IP functionality . 9
4.1 Introduction . 9
4.2 SMS over IP . 9
4.3 Application utilisation of SMS over IP . 10
4.4 SMS over IP and subscription without MSISDN . 10
5 SIP related procedures . 10
5.1 Introduction . 10
5.2 Functional entities . 10
5.2.1 User Equipment (UE) . 10
5.2.1.1 General . 10
5.2.1.2 Configuration . 10
5.2.1.3 Policy enforcement. 10
5.2.2 Application Server (AS) . 12
5.3 Roles . 12
5.3.1 SM-over-IP sender . 12
5.3.1.1 General . 12
5.3.1.2 Submitting a short message . 12
5.3.1.3 Receiving a status report . 14
5.3.1.4 SM-over-IP sender procedures for operation without MSISDN . 14
5.3.1.4.1 General . 14
5.3.1.4.2 Submitting a short message and subscription without MSISDN . 14
5.3.1.4.3 Receiving a status report and subscription without MSISDN . 14
5.3.2 SM-over-IP receiver . 15
5.3.2.1 General . 15
5.3.2.2 Registration . 15
5.3.2.3 Delivery of a short message . 15
5.3.2.4 Sending a delivery report . 15
5.3.2.5 Sending a notification about SM-over-IP receiver having memory available . 16
5.3.2.6 SM-over-IP receiver procedures for operation without MSISDN . 16
5.3.2.6.1 General . 16
5.3.2.6.2 Registration . 16
5.3.2.6.3 Delivery of a short message . 16
5.3.2.6.4 Sending a notification about SM-over-IP receiver having memory available . 17
5.3.3 IP-Short-Message-Gateway (IP-SM-GW) . 17
5.3.3.1 General . 17
5.3.3.2 Indication of SM-over-IP receiver availability status for delivery of short messages . 18
5.3.3.3 Answering routing information query . 18
5.3.3.4 Transport layer interworking . 19
5.3.3.4.1 Receiving a short message in a SIP MESSAGE request . 19
5.3.3.4.2 Delivering a short message in a SIP MESSAGE request . 21
5.3.3.4.3 Forwarding a submit report in a SIP MESSAGE request . 21
5.3.3.4.4 Delivering a status report in a SIP MESSAGE request . 21
5.3.3.5 IP-SM-GW procedures for operation without MSISDN . 22
5.3.3.5.1 General . 22
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 4 ETSI TS 124 341 V18.0.0 (2024-05)
5.3.3.5.2 Receiving a short message in a SIP MESSAGE request from a SM-over-IP sender or SM-
over-IP receiver . 22
5.3.3.5.3 Delivering a short message in a SIP MESSAGE request to a SM-over-IP receiver . 24
5.3.3.5.4 Delivering a delivery report in a SIP MESSAGE request . 25
5.3.3.5.5 Delivering a submit report in a SIP MESSAGE request . 26
5.3.3.5.6 Procedures for receiving a SIP MESSAGE request from an IP-SM-GW . 26
5.3.3.6 SIP failure case . 27
Annex A (normative): Media feature tags defined within the current document . 28
A.1 General . 28
A.2 Definition of media feature tag g.3gpp.smsip . 28
A.3 Definition of media feature tag g.3gpp.smsip-msisdn-less . 28
Annex B (informative): Example signalling flows of SMS over IP functionality . 29
B.1 Scope of signalling flows . 29
B.2 Introduction . 29
B.2.1 General . 29
B.2.2 Key required to interpret signalling flows . 29
B.3 Signalling flows demonstrating how IP-SM-GW indicates to HSS the availability of public user
identity for delivery of short messages . 30
B.4 Signalling flows demonstrating how IP-SM-GW indicates to HSS the unavailability of UE for
delivery of short messages . 33
B.5 Signalling flows demonstrating successful UE originated SM submit procedure over IP . 35
B.6 Signalling flows demonstrating successful UE terminated SM deliver procedure over IP
(including delivery report) . 39
B.7 Signalling flow demonstrating successful procedures for SM over IP in case terminating side is
addressed with SIP URI . 43
Annex C (normative): XML schemas . 47
C.1 Short-messsage-info XML schema . 47
C.1.1 General . 47
C.1.2 application/vnd.3gpp.sms+xml. 47
C.1.3 Data semantics . 47
C.1.4 XML schema . 48
C.1.5 IANA registration . 48
C.1.5.1 Name . 48
C.1.5.2 Email . 49
C.1.5.3 MIME media type name . 49
C.1.5.4 MIME subtype name . 49
C.1.5.5 Required parameters . 49
C.1.5.6 Optional parameters . 49
C.1.5.7 Encoding considerations . 49
C.1.5.8 Security considerations . 49
C.1.5.9 Interoperability considerations . 49
C.1.5.10 Published specification . 49
C.1.5.11 Applications which use this media . 49
C.1.5.12 Applications that manipulate MIME typed objects (messaging, download etc.). 49
C.1.5.13 Additional information . 49
C.1.5.14 Intended usage . 50
C.1.5.8.15 Other information/general comment . 50
C.1.5.8.16 Person to contact for further information . 50
Annex D (normative): Feature-capability indicators defined within the current document . 51
D.1 General . 51
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 5 ETSI TS 124 341 V18.0.0 (2024-05)
D.2 Definition of feature-capability indicator g.3gpp.smsip-msisdn-less . 51
Annex E (normative): IP-Connectivity Access Network specific concepts when using EPS to
access IM CN subsystem . 52
E.1 Scope . 52
E.2 EPS aspects when connected to the IM CN subsystem . 52
E.2.1 Procedures at the UE . 52
E.2.1.1 Smart Congestion Mitigation . 52
E.3 Application usage of SIP . 53
E.3.1 Procedures at the UE . 53
E.3.1.1 3GPP PS data off . 53
E.3.1.1.1 General . 53
E.3.1.1.2 Enforcement . 53
E.3.2 Procedures at the AS . 54
E.3.2.1 3GPP PS data off . 54
Annex F (normative): IP-Connectivity Access Network specific concepts when using GPRS
to access IM CN subsystem . 55
F.1 Scope . 55
F.2 GPRS (Iu mode only) aspects when connected to the IM CN subsystem . 55
F.2.1 Procedures at the UE . 55
F.2.1.1 General . 55
F.2.1.2 Application specific Congestion control for Data Communication (ACDC) procedure. 55
F.3 Application usage of SIP . 56
F.3.1 Procedures at the UE . 56
F.3.1.1 3GPP PS data off . 56
F.3.1.1.1 General . 56
F.3.1.1.2 Enforcement . 56
F.3.2 Procedures at the AS . 56
F.3.2.1 3GPP PS data off . 56
Annex G (normative): IP-Connectivity Access Network specific concepts when using 5GS to
access IM CN subsystem . 57
G.1 Scope . 57
G.2 5GS aspects when connected to the IM CN subsystem . 57
G.2.1 Procedures at the UE . 57
G.2.1.1 Indications to lower layers about start and stop of SMSoIP . 57
G.3 Application usage of SIP . 58
G.3.1 Procedures at the UE . 58
G.3.1.1 3GPP PS data off . 58
G.3.1.1.1 General . 58
G.3.1.1.2 Enforcement . 58
G.3.2 Procedures at the AS . 59
G.3.2.1 3GPP PS data off . 59
Annex H (informative): Change history . 60
History . 62

ETSI
3GPP TS 24.341 version 18.0.0 Release 18 6 ETSI TS 124 341 V18.0.0 (2024-05)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
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
3GPP TS 24.341 version 18.0.0 Release 18 7 ETSI TS 124 341 V18.0.0 (2024-05)
1 Scope
The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN)
subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in 3GPP TS 24.229 [10].
The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN)
subsystem based on the SMS layer as defined in 3GPP TS 24.011 [8].
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by 3GPP TS 24.229 [10].
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing SMS over IP
functionality.
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 TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.002: "Network Architecture".
[3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[4] 3GPP TS 23.140: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[5] 3GPP TS 23.204: "Support of SMS over generic 3GPP IP access; Stage 2".
[6] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[7] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[8] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[8A] 3GPP TS 24.167: "3GPP IMS Management Object (MO)".
[9] 3GPP TS 24.228 Release 5: "Signalling flows for the IP multimedia call control based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[10] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[11] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[12] RFC 3261 (June 2002): "SIP: Session Initiation Protocol".
[13] RFC 3325 (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks".
[14] RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[15] RFC 3680 (March 2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 8 ETSI TS 124 341 V18.0.0 (2024-05)
[16] RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol
(SIP)".
[17] RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[18] 3GPP TS 31.103: "Characteristics of the IP Multimedia Services Identity Module (ISIM)
Application".
[19] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)
Application".
[20] 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module, Mobile Equipment
(SIM - ME) interface".
[21] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".
[22] 3GPP TS 23.003: "Numbering, addressing and identification".
[23] 3GPP TS 29.311: "Service Level Interworking (SLI) for messaging services".
[24] RFC 6809 (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the
Session Initiation Protocol (SIP)".
[25] RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)".
[26] RFC 4288 (December 2005): "Media Type Specifications and Registration Procedures".
[27] RFC 6665 (July 2012): "SIP-Specific Event Notification".
[28] 3GPP TS 22.011: "Service accessibility".
[29] 3GPP TS 23.221: "Architectural requirements".
[30] 3GPP TS 24.216: "Communication Continuity Management Object (MO)".
[31] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
MSISDN less operation: Operation of SMS over IP for subscriber without MSISDN in the subscription profile as
defined in 3GPP TS 23.204 [5] in clause 6.0a.
SM-over-IP sender: the A party that sends an SM using a SIP MESSAGE request including a vnd.3gpp.sms payload
(introduced in 3GPP TS 23.140 [4]).
SM-over-IP receiver: the B party that receives an SM encapsulated in the vnd.3gpp.sms payload of a SIP MESSAGE
request.
For the purposes of the present document, the following terms and definitions given in RFC 3261 [12] apply.
Header
Header field
Method
Request
Response
(SIP) transaction
Status-code (see RFC 3261 [12], clause 7.2)
Tag (see RFC 3261 [12], clause 19.3)
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 9 ETSI TS 124 341 V18.0.0 (2024-05)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.002 [2],
clauses 4.1.1.1 and 4a.7 apply:
Call Session Control Function (CSCF)
Home Subscriber Server (HSS)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.218 [6], clause 3.1
apply:
Filter criteria
Initial filter criteria
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [7],
clauses 4.3.3.1, 4.3.6 and 4.6 apply:
Interrogating-CSCF (I-CSCF)
Public Service Identity (PSI)
Proxy-CSCF (P-CSCF)
Serving-CSCF (S-CSCF)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.011 [28] apply:
3GPP PS data off
3GPP PS data off exempt service
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.229 [10] apply:
3GPP PS data off status
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122 [31] apply:
Equivalent Home PLMN (EHPLMN)
Home PLMN (HPLMN)
Visited PLMN (VPLMN)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.040 [3] and the following
apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if
any, in TR 21.905 [1].
AS Application Server
IP-SM-GW IP-Short-Message-Gateway
PS Packet Switched
4 Overview of SMS over IP functionality
4.1 Introduction
SMS over IP functionality provides the UE with the capability of sending traditional short messages over IMS network.
The architecture for SMS is specified in 3GPP TS 23.040 [3] and for SMS over IP functionality in 3GPP TS 23.204 [5].
4.2 SMS over IP
In order to guarantee SMS interoperability the SM-over-IP sender, the SM-over-IP receiver and the IP-SM-GW shall
support encapsulation of RPDUs defined in 3GPP TS 24.011 [8], clause 7.3. The SM-over-IP sender, the SM-over-IP
receiver and the IP-SM-GW shall use the MIME type "application/vnd.3gpp.sms" for this purpose.
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 10 ETSI TS 124 341 V18.0.0 (2024-05)
4.3 Application utilisation of SMS over IP
SMS over generic IP access can be used to support all applications and services that use SMS.
4.4 SMS over IP and subscription without MSISDN
When SMS over IP is to be delivered to a subscriber where the subscription profile does not contain an MSISDN, then
there is a need for the IP-SM-GW to become aware of the IMSI during IMS registration for later correlation of short
messages. In order to do so the IP-SM-GW derives the IMSI from the private user identity of the user that the UE
includes in the REGISTER request at registration or if the private user identity is not available, derives the IMSI from
the public user identity.
3GPP TS 23.003 [22] defines the relationship between the private user identity and the IMSI and the relationship
between the public user identity and the IMSI.
5 SIP related procedures
5.1 Introduction
5.2 Functional entities
5.2.1 User Equipment (UE)
5.2.1.1 General
To be compliant with short message over IP in this document, a UE shall implement:
a) the role of an SM-over-IP sender as specified in clause 5.3.1.1, clause 5.3.1.2, and clause 5.3.1.3;
b) the role of an SM-over-IP receiver as specified in clause 5.3.2.1, clause 5.3.2.2, clause 5.3.2.3, clause 5.3.2.4,
and clause 5.3.2.5; or
c) the roles described in item a) and item b).
To be compliant with short message over IP in MSISDN less operation in this document, a UE shall implement:
a) the role of an SM-over-IP sender as specified in clause 5.3.1.4.1, clause 5.3.1.4.2, and clause 5.3.1.4.3;
b) the role of an SM-over-IP receiver as specified in clause 5.3.2.6.1, clause 5.3.2.6.2, clause 5.3.2.6.3, and
clause 5.3.2.6.4; or
c) the roles described in item a) and item b).
NOTE: The capability of sending short messages over IP does not affect current limitations, thus the UE is
limited to send at most one UE originated SM and to receive at most one UE terminated SM at a time.
5.2.1.2 Configuration
Parameters such as the PSI of the SC of the SM-over-IP sender can be obtained from the UICC as per
3GPP TS 31.103 [18] and 3GPP TS 31.102 [19] if used or from the SIM as per 3GPP TS 51.011 [20] if used.
5.2.1.3 Policy enforcement
The network operator's preference for selection of the domain to be used for short message service originated by the UE
indicates the domain for originating short messages.
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 11 ETSI TS 124 341 V18.0.0 (2024-05)
The network operator's preference for selection of the domain to be used for short message service originated by the UE
can be set to one of the following values:
a) the SMS service is not to be invoked over the IP networks; and
b) the SMS service is preferred to be invoked over the IP networks.
The UE shall support the network operator's preference for selection of the domain to be used for short message service
originated by the UE.
The UE may support being configured with the network operator's preference for selection of the domain to be used for
short message service originated by the UE in the SMS_Over_IP_Networks_Indication of 3GPP TS 24.167 [8A].
Editor's note [CR#0086, IOC_UE_conf]: Handling of any configuration on UICC related to the network operator's
preference for selection of the domain to be used for short message service originated by the UE is FFS.
If the network operator's preference for selection of the domain to be used for short message service originated by the
UE is set to "the SMS service is not to be invoked over the IP networks", the UE shall not perform the procedures in
clause 5.3.1.
The policy on usage of SMS over IP indicates when the UE is allowed to use SMS over IP.
The policy on usage of SMS over IP can be set to one of the following values:
a) SMS over IP is used only if voice over PS is available and only on the IP-CAN bearer that is used for the
transport of SIP signalling associated with voice over PS;
b) SMS over IP is used only if voice over PS is available and on any IP-CAN bearer; and
c) SMS over IP is used irrespective of whether voice over PS is available and on any IP-CAN bearer.
The UE may support the policy on usage of SMS over IP.
If the UE supports the policy on usage of SMS over IP and the network operator's preference for selection of the domain
to be used for short message service originated by the UE is set to "the SMS service is preferred to be invoked over the
IP networks":
a) the UE may support being configured with SMSoIP usage policy using one or more of the following methods:
1) the SMSoIP usage policy leaf of the EF file described in 3GPP TS 31.102 [19];
IMSConfigData
2) the SMSoIP usage policy leaf of the EF file described in 3GPP TS 31.103 [18]; and
IMSConfigData
3) the SMSoIP usage policy leaf of 3GPP TS 24.167 [8A].
If the UE is configured with both the SMSoIP usage policy leaf of 3GPP TS 24.167 [8A] and the SMSoIP usage
policy leaf of the EF file described in 3GPP TS 31.102 [19] or the SMSoIP usage policy leaf of the
IMSConfigData
EF file described in 3GPP TS 31.103 [18], then the SMSoIP usage policy leaf of the EF file
IMSConfigData IMSConfigData
shall take precedence.
NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [18].
b) if the policy on usage of SMS over IP is set to "SMS over IP is used only if voice over PS is available and only
on the IP-CAN bearer that is used for the transport of SIP signalling associated with voice over PS":
1) if the domain selection for originating voice calls specified in 3GPP TS 23.221 [29] determines that the UE
does not use the IMS to originate voice call then the UE shall not perform the procedures in clause 5.3.1 and
clause 5.3.2 and determines that SMS over IP is restricted (see 3GPP TS 24.229 [10]); and
2) if:
A) the domain selection for originating voice calls specified in 3GPP TS 23.221 [29] determines that the UE
uses the IMS to originate voice calls;
B) the UE supports multiple registrations as specified in 3GPP TS 24.229 [10];
C) the UE registered several registration flows; and
ETSI
3GPP TS 24.341 version 18.0.0 Release 18 12 ETSI TS 124 341 V18.0.0 (2024-05)
D) at least one of the registration flow was registered via an IP-CAN different than the remaining registration
flows;
then the UE shall not perform the procedures in clause 5.3.1 and clause 5.3.2 and determines that SMS over
IP is restricted (see 3GPP TS 24.229 [10]) over access technology where the audio is restricted or not
preferred according to 3GPP TS 24.216 [30]; and
c) if the policy on usage of SMS over IP is set to "SMS over IP is used only if voice over PS is available and on any
IP-CAN bearer" and the domain selection for originating voice calls specified in 3GPP TS 23.221 [29]
determines that the UE does not use the IMS to originate voice call then the UE shall not perform the procedures
in clause 5.3.1 and clause 5.3.2 and determines that SMS over IP is restricted (see 3GPP TS 24.229 [10]).
NOTE 2: If the network operator's preference for selection of the domain to be used for short message service
originated by the UE is set to "the SMS service is not to be invoked over the IP networks", the policy on
usage of SMS over I
...