ETSI TS 129 540 V19.5.0 (2026-03)

5G; 5G System; SMS Services; Stage 3 (3GPP TS 29.540 version 19.5.0 Release 19)

RTS/TSGC-0429540vj50

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
SMS Services;
Stage 3
(3GPP TS 29.540 version 19.5.0 Release 19)


3GPP TS 29.540 version 19.5.0 Release 19 1 ETSI TS 129 540 V19.5.0 (2026-03)

Reference
RTS/TSGC-0429540vj50
Keywords
5G
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 the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
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
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
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 2026.
All rights reserved.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 2 ETSI TS 129 540 V19.5.0 (2026-03)
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 IPR online database.
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™, LTE™ and 5G™ logo 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 at 3GPP to ETSI numbering cross-referencing.
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 29.540 version 19.5.0 Release 19 3 ETSI TS 129 540 V19.5.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Overview . 8
5 Services offered by the SMSF . 9
5.1 Introduction . 9
5.2 Nsmsf_SMService Service . 9
5.2.1 Service Description . 9
5.2.2 Service Operations . 10
5.2.2.1 Introduction . 10
5.2.2.2 Activate . 10
5.2.2.2.1 General . 10
5.2.2.2.2 Registration procedure using Activate service operation . 10
5.2.2.2.3 Modify UE Context in SMSF using HTTP PATCH Method . 11
5.2.2.3 Deactivate. 12
5.2.2.3.1 General . 12
5.2.2.3.2 De-Registration procedure to remove SMS service authorization from SMSF . 13
5.2.2.3.3 De-Registration procedure to remove SMS service authorization from SMSF for one of the
registered Access Type . 13
5.2.2.4 UplinkSMS. 14
5.2.2.4.1 General . 14
5.2.2.4.2 Procedures of sending SMS payload in uplink direction using UplinkSMS service operation . 14
5.2.2.5 MtForwardSm . 15
5.2.2.5.1 General . 15
5.2.2.5.2 Procedures of sending SMS payload in downlink direction using MtForwardSm service

operation . 15
6 API Definitions . 16
6.1 Nsmsf_SMService Service API . 16
6.1.1 API URI . 16
6.1.2 Usage of HTTP . 16
6.1.2.1 General . 16
6.1.2.2 HTTP standard headers . 16
6.1.2.2.1 General . 16
6.1.2.2.2 Content type . 16
6.1.2.2.3 ETag . 17
6.1.2.2.4 If-Match . 17
6.1.2.3 HTTP custom headers . 17
6.1.2.3.1 General . 17
6.1.2.4 HTTP multipart messages . 17
6.1.3 Resources . 17
6.1.3.1 Overview . 17
6.1.3.2 Resource: UEContexts (Store) . 19
6.1.3.2.1 Description . 19
6.1.3.2.2 Resource Definition . 19
6.1.3.2.3 Resource Standard Methods . 20
6.1.3.3 Resource: UEContext (Document) . 20
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 4 ETSI TS 129 540 V19.5.0 (2026-03)
6.1.3.3.1 Description . 20
6.1.3.3.2 Resource Definition . 20
6.1.3.3.3 Resource Standard Methods . 20
6.1.3.3.4 Resource Custom Operations . 25
6.1.3.3.4.1 Overview . 25
6.1.3.3.4.2 Operation: sendsms . 25
6.1.3.3.4.2.1 Description . 25
6.1.3.3.4.2.2 Operation Definition . 25
6.1.3.3.4.3 Operation: send-mt-sms . 26
6.1.3.3.4.3.1 Description . 26
6.1.3.3.4.3.2 Operation Definition . 27
6.1.4 Custom Operations without associated resources . 28
6.1.5 Notifications . 28
6.1.6 Data Model . 28
6.1.6.1 General . 28
6.1.6.2 Structured data types . 29
6.1.6.2.1 Introduction . 29
6.1.6.2.2 Type: UeSmsContextData . 30
6.1.6.2.3 Type: SmsRecordData . 31
6.1.6.2.4 Void . 31
6.1.6.2.5 Type: SmsRecordDeliveryData . 31
6.1.6.3 Simple data types and enumerations . 31
6.1.6.3.1 Introduction . 31
6.1.6.3.2 Simple data types . 31
6.1.6.3.3 Enumeration: SmsDeliveryStatus . 32
6.1.6.4 Binary data . 32
6.1.6.4.1 Introduction . 32
6.1.6.4.2 SMS Payload Information . 32
6.1.7 Error Handling . 32
6.1.7.1 General . 32
6.1.7.2 Protocol Errors . 32
6.1.7.3 Application Errors . 32
6.1.8 Feature negotiation . 33
6.1.9 Security . 33
6.1.10 HTTP redirection . 33
Annex A (normative): OpenAPI specification . 35
A.1 General . 35
A.2 Nsmsf_SMService API . 35
Annex B (Informative): HTTP Multipart Messages . 43
B.1 Example of HTTP multipart message . 43
B.2 Void . 43
B.3 Example HTTP multipart message with SMS binary data . 43
Annex C (informative): Change history . 45
History . 48

ETSI
3GPP TS 29.540 version 19.5.0 Release 19 5 ETSI TS 129 540 V19.5.0 (2026-03)
Foreword
This Technical Specification has been produced by the 3rd 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.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 6 ETSI TS 129 540 V19.5.0 (2026-03)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.

ETSI
3GPP TS 29.540 version 19.5.0 Release 19 7 ETSI TS 129 540 V19.5.0 (2026-03)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nsmsf Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
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.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[7] IETF RFC 9113: "HTTP/2".
[8] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[9] IETF RFC 2387: "The MIME Multipart/Related Content-type".
[10] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[11] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[12] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[13] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[14] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[15] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
[16] 3GPP TR 21.900: "Technical Specification Group working methods".
[17] IETF RFC 9457: "Problem Details for HTTP APIs".
[18] Void.
[19] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 8 ETSI TS 129 540 V19.5.0 (2026-03)
[20] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch".
[21] 3GPP TS 23.540: "5G System; Technical realization of Service Based Short Message Service
Stage 2".
[22] 3GPP TS 29.577: "5G System; IP Short Message Gateway and SMS Router For Short Message
Services Stage 3".
[23] IETF RFC 9110: "HTTP Semantics".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP 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
3GPP TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
5GC 5G Core Network
AMF Access Management Function
JSON Javascript Object Notation
SMSF SMS Function
4 Overview
Within the 5GC, the SMSF offers services to the AMF, SMS-GMSC, IP-SM-GW and SMS Router via the Nsmsf
service based interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.540 [21]).
Figures 4.1 provides the reference model (in service based interface representation and in reference point
representation), with focus on the SMSF and the scope of the present specification.
AMF
N20
SMS-
GMSC
SM5
Nsmsf SMSF
SM7
SMS
Router
SM9
IP-SM-GW
Figure 4-1: Reference model – SMSF
The functionalities supported by the SMSF are listed in clause 6.2.13 of 3GPP TS 23.501 [2].
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 9 ETSI TS 129 540 V19.5.0 (2026-03)
The services and service operations provided by the Nsmsf interface are listed in clause 5.2.9 of 3GPP TS 23.502 [3]
and clause 6.4 of 3GPP TS 23.540 [21].
5 Services offered by the SMSF
5.1 Introduction
The SMSF supports the following services.
Table 5.1-1: NF Services provided by SMSF
Service Name Description Example
Consumer
Nsmsf_SMService This service allows AMF to authorize SMS and activate AMF, SMS-
SMS for the served user on SMSF. GMSC, SMS
This service also allows the SMS-GMSC, SMS Router Router, IP-SM-
and IP-SM-GW to send the SMS payload in downlink GW
direction to the SMSF.
Table 5.1-2 summarizes the corresponding APIs defined for this specification.
Table 5.1-2: API Descriptions
Service Name Clause Description OpenAPI Specification File apiName Annex
Nsmsf_SMService 6.1 SMSF SMService TS29540_Nsmsf_SMService.yaml nsmsf-sms A.2

5.2 Nsmsf_SMService Service
5.2.1 Service Description
The Nsmsf_SMService service provides the service capability for the NF Service Consumer (e.g. AMF) to authorize
SMS and activate SMS for a service user on SMSF, for the NF Service Consumer (e.g. SMS GMSC, SMS Router and
IP-SM-GW) to send the SMS payload in downlink direction to the SMSF. The following are the key functionalities of
this NF service:
- Activation or deactivation of SMS service for a given service user, which results in creating/updating/deleting an
UE Context for SMS in SMSF;
- Send SMS payload in uplink direction to SMSF;
- Send SMS payload in downlink direction to SMSF.
The Nsmsf_SMService service supports the following service operations.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 10 ETSI TS 129 540 V19.5.0 (2026-03)
Table 5.2.1-1: Service operations supported by the Nsmsf_SMService service
Service Operations Description Operation Example
Semantics Consumer(s)
Activate Activate SMS service for a given service user, Request/Response AMF
which results in creating or updating a UE
Context for SMS in SMSF.
Deactivate Deactivate SMS service for a given service Request/Response AMF
user, which results in deleting or updating a
UE Context for SMS in SMSF.
UplinkSMS Send SMS payload in uplink direction to Request/Response AMF
SMSF.
MtForwardSm Send SMS payload in downlink direction to Request/Response SMS-GMSC, SMS
SMSF. Router, IP-SM-
GW
5.2.2 Service Operations
5.2.2.1 Introduction
This clause introduces the related procedures using Nsmsf_SMService service operations for supporting SMS service.
5.2.2.2 Activate
5.2.2.2.1 General
The Activate service operation shall be used by the NF Service Consumer (e.g. AMF) to activate SMS service for a
given service user, which results in creating or updating an individual UE Context for SMS in the SMSF, in the
following procedures:
- Registration Procedure for SMS over NAS (see clause 4.13.3.1 of 3GPP TS 23.502 [3]);
- Registration Update Procedure for SMS over NAS due to AMF change (see clause 4.13.3.1 of
3GPP TS 23.502 [3]);
- Registration Update Procedure for SMS over NAS to add authorization for SMS over a new additional Access
Type;
- AMF initiated modification to UE Context in SMSF, e.g. modify the backup AMF information.
There shall be only one individual UE Context for SMS per service user.
5.2.2.2.2 Registration procedure using Activate service operation
The NF Service Consumer (e.g. AMF) shall activate SMS service for a given service user by using the HTTP PUT
method as shown in Figure 5.2.2.2.2-1.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 11 ETSI TS 129 540 V19.5.0 (2026-03)

Figure 5.2.2.2.2-1: Activation of SMS service
1. The NF Service Consumer (e.g. AMF) shall send a PUT request to the resource representing the UE Context for
SMS (i.e. …/ue-contexts/{supi}) in the SMSF to activate SMS service for a given service user. The content of
the PUT request shall contain a representation of the individual UE Context resource to be created or updated.
Depending on whether the target UE Context for SMS has already been created, the SMSF performs 2a or 2b:
2a. If the target UE Context for SMS is not created in SMSF, the SMSF registers itself in UDM for the Access
Type(s) provided, retrieves subscription data from the UDM, performs service authorization for the given UE,
and create UE Context for SMS for this UE.
If successful, "201 Created" shall be returned, the content of the PUT response shall contain the representation of
the created resource and the "Location" header shall contain the URI of the created resource.
2b. If the target UE Context for SMS has already been created, the SMSF updates the UE Context for SMS with the
NF Service Consumer (e.g. AMF) provided parameters.
If successful, "204 No Content" shall be returned.
2c. If the target UE Context for SMS has already been created and the NF Service Consumer (e.g. AMF) provided
parameters contains 2 access types (i.e. an additional Access Type), the SMSF registers itself in UDM for the
new Access Type for the given UE, performs service authorization for the given UE for the new Access Type
and updates the UE context for SMS for this UE with the new additional Access Type.
If successful, "204 No Content" shall be returned.
2d. On failure, the appropriate HTTP status code (e.g. "403 Forbidden") indicating the error shall be returned.
A ProblemDetails IE shall be included in the content of PUT response, with the "cause" attribute of
ProblemDetails set to application error codes specified in table 6.1.7.3-1.
2e. On redirection, the appropriate HTTP status code (e.g. "307 Temporary Redirect") shall be returned.
A RedirectResponse IE may be included in the content of PUT response, as specified in table 6.1.3.3.3.1-3.
5.2.2.2.3 Modify UE Context in SMSF using HTTP PATCH Method
The NF Service Consumer (e.g. AMF) may update UE context in SMSF for a given service user by using the HTTP
PATCH method as shown in Figure 5.2.2.2.3-1.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 12 ETSI TS 129 540 V19.5.0 (2026-03)
NF Service
SMSF
Consumer
1. PATCH ./ue-contexts/{supi} (array(PatchItem))
2a. 204 No Content
2b. 200 OK (PatchResult) or 200 OK (UeSmsContextData)
2c. 4xx/5xx (ProblemDetails)
2d. 3xx (RedirectResponse)
Figure 5.2.2.2.3-1: Modify UE Context in SMSF using HTTP PATCH Method
1. The NF Service Consumer (e.g. AMF) shall send a PATCH request to the resource representing the UE Context
for SMS (i.e. …/ue-contexts/{supi}) in the SMSF to modify the UE Context in SMSF for a given service user.
The request body shall contain a list of PatchItem for each the JSON pointer is set to the attribute to be modified.
2a. On success, the request is accepted, and all the modification instructions in the PATCH request have been
implemented, the SMSF shall respond with "204 No Content".
2b. On partial success, the request is accepted, but some of the modification instructions in the PATCH request have
been discarded:
- the SMSF shall respond with "200 OK" including PatchResult to indicate the failed modifications, if the NF
service consumer has included in the supported-feature query parameter the "PatchReport" feature; or
-the SMSF shall respond with "200 OK" with the response body containing UeSmsContextData, if the NF
service consumer does not support the "PatchReport" feature.
2c. On failure, the appropriate HTTP status code (e.g. "403 Forbidden") indicating the error shall be returned. A
ProblemDetails IE shall be included in the content of PATCH response, with the "cause" attribute of
ProblemDetails set to application error codes specified in table 6.1.7.3-1.
If the modification is not allowed, HTTP status code "403 Forbidden" should be returned including additional
error information in the response body (in the "ProblemDetails" element).
If the resource does not exist, e.g. the attribute to be modified cannot be found, HTTP status code "404 Not
Found" should be returned including additional error information in the response body (in the "ProblemDetails"
element).
2d. On redirection, the appropriate HTTP status code (e.g. "307 Temporary Redirect") shall be returned. A
RedirectResponse IE may be included in the content of PATCH response, as specified in table 6.1.3.3.3.1-3.
5.2.2.3 Deactivate
5.2.2.3.1 General
The Deactivate service operation shall be used by the NF Service Consumer (e.g. AMF) to deactivate SMS service for a
given service user, which results in deleting or updating an individual UE Context for SMS in the SMSF, in the
following procedures:
- De-Registration Procedure to remove SMS service authorization from SMSF for SMS over NAS (see
clause 4.13.3.2 of 3GPP TS 23.502 [3]);
- De-Registration procedure to remove SMS service authorization from SMSF for one of the registered Access
Type (see clause 4.13.3.2 of 3GPP TS 23.502 [3]);
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 13 ETSI TS 129 540 V19.5.0 (2026-03)
5.2.2.3.2 De-Registration procedure to remove SMS service authorization from SMSF
The NF Service Consumer (e.g. AMF) shall deactivate SMS service for a given service user by using the HTTP
DELETE method as shown in Figure 5.2.2.3.2-1.

Figure 5.2.2.3.2-1: Deactivation of SMS service
1. The NF Service Consumer (e.g. AMF) shall send a DELETE request to the resource representing the UE Context
for SMS (i.e. …/ue-contexts/{supi}) in the SMSF.
2a. The SMSF deactivates the SMS service for the service user, and deletes the UE context for SMS from the SMSF.
On success, "204 No Content" shall be returned.
2b. On failure, the appropriate HTTP status code (e.g. "404 Not Found") indicating the error shall be returned.
A ProblemDetails IE shall be included in the content of DELETE response, with the "cause" attribute of
ProblemDetails set to application error codes specified in table 6.1.7.3-1.
2c. On redirection, the appropriate HTTP status code (e.g. "307 Temporary Redirect") shall be returned.
A RedirectResponse IE may be included in the content of DELETE response, as specified in table 6.1.3.3.3.2-3.
5.2.2.3.3 De-Registration procedure to remove SMS service authorization from SMSF for
one of the registered Access Type
When the UE has SMS service activated on both of the Access Types and the NF Service Consumer (e.g. AMF) wants
to deactivate SMS service for the given UE for one of the affected Access Type, the NF Service Consumer (e.g. AMF)
shall use HTTP PUT method as shown in Figure 5.2.2.3.3-1.

Figure 5.2.2.3.3-1: Removal of SMS service authorization over one of the access types
1. The NF Service Consumer (e.g. AMF) shall send a PUT request to the resource representing the UE Context for
SMS (i.e. …/ue-contexts/{supi}) in the SMSF. The content of the PUT request shall contain a representation of
the individual UE Context resource to be updated. Only one Access Type that is allowed for SMS service shall
be included in the content of PUT request.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 14 ETSI TS 129 540 V19.5.0 (2026-03)
2a. Since the target UE Context for SMS was already created at the SMSF with both 3GPP and non-3GPP Access
Types for the same NF Service Consumer (e.g. AMF) and the NF Service Consumer provided parameters
contains only one Access Type, the SMSF deregisters itself in the UDM for the affected Access Type (i.e. the
access type not included in the PUT request) for the given UE and updates the UE context for SMS by removing
the affected Access Type.
On success, "204 No Content" shall be returned.
2b. On failure, the appropriate HTTP status code (e.g. "403 Forbidden") indicating the error shall be returned.
A ProblemDetails IE shall be included in the content of PUT response, with the "cause" attribute of
ProblemDetails set to application error codes specified in table 6.1.7.3-1.
2c. On redirection, the appropriate HTTP status code (e.g. "307 Temporary Redirect") shall be returned.
A RedirectResponse IE may be included in the content of PUT response, as specified in table 6.1.3.3.3.1-3.
5.2.2.4 UplinkSMS
5.2.2.4.1 General
The UplinkSMS service operation shall be used by NF Service Consumer (e.g. AMF) to send SMS payload (e.g. SMS
message or Ack) in the uplink direction to SMSF, in the following procedures:
- MO SMS delivery procedure (see clause 4.13.3.3-4.13.3.5 of 3GPP TS 23.502 [3]);
- MT SMS delivery procedure (see clause 4.13.3.6-4.13.3.8 of 3GPP TS 23.502 [3]);
5.2.2.4.2 Procedures of sending SMS payload in uplink direction using UplinkSMS service
operation
The NF Service Consumer (e.g. AMF) shall send SMS payload in uplink direction by using the "sendsms" custom
operation as shown in Figure 5.2.2.4.2-1.

Figure 5.2.2.4.2-1: Send SMS payload in uplink direction
1. The NF Service Consumer (e.g. AMF) shall send a POST request to the resource representing the UEContext
(i.e. …/ue-contexts/{supi}/sendsms) of the SMSF. The content of the POST request shall contain the SMS
record to be sent.
2a. On success, "200 OK" shall be returned with "SmsRecordDeliveryData" object in the response body.
The SMSF may immediately respond to the NF service consumer, after successful inspection of the SMS
payload, and set the "deliveryStatus" attribute to "SMS_DELIVERY_SMSF_ACCEPTED"; the SMSF may also
attempt to forward the SMS payload to SMS-GMSC/IWMSC/IP-SM-GW/SMS Router.
If successful, "200 OK" shall be returned. If needed, the content body of the POST response shall contain the
status of SMS record delivery attempts at the SMSF.
2b. On failure, the appropriate HTTP status code (e.g. "403 Forbidden") indicating the error shall be returned.
ETSI
3GPP TS 29.540 version 19.5.0 Release 19 15 ETSI TS 129 540 V19.5.0 (2026-03)
A ProblemDetails IE shall be included in the content of POST response, with the "cause" attribute of
ProblemDetails set to application error codes specified in table 6.1.7.3-1.
2c. On redirection, the appropriate HTTP status code (e.g. "307 Temporary Redirect") shall be returned.
A RedirectResponse IE may be included in the content of POST response, as specified in table 6.1.3.3.4.2.2-2.
5.2.2.5 MtForwardSm
5.2.2.5.1 General
The MtForwardSm service operation shall be used by NF Service Consumer (e.g. SMS GMSC, SMS Router and IP-
SM-GW) to send SMS payload (e.g. SMS message) in the downlink direction to SMSF, in the following procedures:
- Successful Mobile Terminated short message transfer as defined in 3GPP TS 23.540 [21] clause 5.1.2,
clause 5.1.3 and clause 5.1.4.
- Unsuccessful Mobile Terminated short message transfer as defined in 3GPP TS 23.540 [21] clause 5.1.5,
clause 5.1.6 and clause 5.1.9.
5.2.2.5.2 Procedures of sending SMS payload in downlink direction using MtForwardSm
service operation
The NF Service Consumer (e.g. SMS GMSC, SMS Router and IP-SM-GW) shall send SMS payload in downlink
direction by using the "send-mt-sms" custom operation as shown in Figure 5.2.2.5.2-1.
NF Service
SMSF
Consumer
1. POST ./ue-contexts/{supi}/send-mt-sms (SmsData)
2a. 200 OK (SmsDeliveryData)
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
Figure 5.2.2.5.2-1: Send SMS payload in downlink direction
1. The NF Service Consumer (e.g. SMS GMSC, SMS Router and IP-SM-GW) shall send a POST request to the
resource representing the UEContext (i.e. …/ue-contexts/{supi}/send-mt-sms) of the SMSF. The content of the
...