ETSI TS 129 338 V17.2.0 (2023-10)

Universal Mobile Telecommunications System (UMTS); LTE; 5G; Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) (3GPP TS 29.338 version 17.2.0 Release 17)

RTS/TSGC-0429338vh20

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 05-Oct-2023

Standards Content (Sample)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Diameter based protocols to support
Short Message Service (SMS)
capable Mobile Management Entities (MMEs)
(3GPP TS 29.338 version 17.2.0 Release 17)

3GPP TS 29.338 version 17.2.0 Release 17 1 ETSI TS 129 338 V17.2.0 (2023-10)

Reference
RTS/TSGC-0429338vh20
Keywords
5G,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
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 2023.
All rights reserved.
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 2 ETSI TS 129 338 V17.2.0 (2023-10)
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 29.338 version 17.2.0 Release 17 3 ETSI TS 129 338 V17.2.0 (2023-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 8
2 References . 8
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 General . 9
4.1 Introduction . 9
4.2 Use of Diameter Base protocol . 10
4.3 Securing Diameter messages . 10
4.4 Accounting functionality . 10
4.5 Use of sessions . 10
4.6 Transport protocol . 10
4.7 Advertising application support . 10
4.8 Diameter Application Identifier . 11
4.9 Use of the Supported-Features AVP . 11
5 Diameter based S6c interface between HSS and central SMS functions . 11
5.1 Introduction . 11
5.2 Procedures description . 11
5.2.1 Send Routing Info for SM procedure . 11
5.2.1.1 General . 11
5.2.1.2 Detailed behaviour of the SMS-GMSC. 16
5.2.1.3 Detailed behaviour of the HSS . 16
5.2.1.4 Detailed behaviour of the SMS Router . 17
5.2.2 Alert Service Centre procedure . 17
5.2.2.1 General . 17
5.2.2.2 Detailed behaviour of the HSS . 18
5.2.2.3 Detailed behaviour of the SMS-IWMSC . 19
5.2.3 Report SM Delivery Status procedure . 19
5.2.3.1 General . 19
5.2.3.2 Detailed behaviour of the SMS-GMSC. 21
5.2.3.3 Detailed behaviour of IP-SM-GW . 21
5.2.3.4 Detailed behaviour of the HSS . 21
5.3 Protocol specification . 21
5.3.1 Routing considerations . 21
5.3.1.1 Requests from the SMS-GMSC or the SMS router . 21
5.3.1.1.1 Introduction . 21
5.3.1.1.2 Routing from the originating PLMN . 22
5.3.1.1.3 Routing in the HPLMN . 22
5.3.1.2 Requests from the HSS . 23
5.3.2 Commands . 23
5.3.2.1 Introduction . 23
5.3.2.2 Command-Code values . 23
5.3.2.3 Send-Routing-Info-for-SM-Request (SRR) Command . 24
5.3.2.4 Send-Routing-info-for-SM-Answer (SRA) Command . 24
5.3.2.5 Alert-Service-Centre-Request (ALR) Command . 25
5.3.2.6 Alert-Service-Centre-Answer (ALA) Command . 25
5.3.2.7 Report-SM-Delivery-Status-Request (RDR) Command . 25
5.3.2.8 Report-SM-Delivery-Status-Answer (RDA) Command . 26
5.3.3 AVPs . 26
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 4 ETSI TS 129 338 V17.2.0 (2023-10)
5.3.3.1 General . 26
5.3.3.2 SM-RP-MTI . 28
5.3.3.3 SM-RP-SMEA . 28
5.3.3.4 SRR-Flags . 29
5.3.3.5 SM-Delivery-Not-Intended . 29
5.3.3.6 Serving-Node . 29
5.3.3.7 Additional-Serving-Node . 30
5.3.3.8 MWD-Status . 30
5.3.3.9 MME-Absent-User-Diagnostic-SM . 31
5.3.3.10 MSC-Absent-User-Diagnostic-SM . 31
5.3.3.11 SGSN-Absent-Subscriber-Diagnostic-SM . 31
5.3.3.12 Feature-List-ID AVP . 31
5.3.3.13 Feature-List AVP . 31
5.3.3.14 SM-Delivery-Outcome . 32
5.3.3.15 MME-SM-Delivery-Outcome . 32
5.3.3.16 MSC-SM-Delivery-Outcome . 32
5.3.3.17 SGSN-SM-Delivery-Outcome . 32
5.3.3.18 IP-SM-GW-SM-Delivery-Outcome . 32
5.3.3.19 SM-Delivery-Cause. 33
5.3.3.20 Absent-User-Diagnostic-SM . 33
5.3.3.21 RDR-Flags . 33
5.3.3.22 Maximum-UE-Availability-Time . 33
5.3.3.23 SMS-GMSC-Alert-Event . 33
5.3.3.24 DRMP . 34
5.3.3.25 SMSF-3GPP-Absent-User-Diagnostic-SM . 34
5.3.3.26 SMSF-Non-3GPP-Absent-User-Diagnostic-SM . 34
5.3.3.27 SMSF-3GPP-SM-Delivery-Outcome . 34
5.3.3.28 SMSF-Non-3GPP-SM-Delivery-Outcome . 34
5.3.3.29 SMSF-3GPP-Number . 34
5.3.3.30 SMSF-Non-3GPP-Number . 34
5.3.3.31 SMSF-3GPP-Name . 35
5.3.3.32 SMSF-Non-3GPP-Name . 35
5.3.3.33 SMSF-3GPP-Realm . 35
5.3.3.34 SMSF-Non-3GPP-Realm . 35
5.3.3.35 SMSF-3GPP-Address . 35
5.3.3.36 SMSF-Non-3GPP-Address . 35
5.4 User identity to HSS resolution . 35
6 Diameter based SGd/Gdd interfaces between MME/SGSN and central SMS functions . 36
6.1 Introduction . 36
6.2 Procedures description . 37
6.2.1 MO Forward Short Message procedure . 37
6.2.1.1 General . 37
6.2.1.2 Detailed behaviour of the MME, the SGSN and the IP-SM-GW. 38
6.2.1.3 Detailed behaviour of the SMS-IWMSC . 38
6.2.2 MT Forward Short Message procedure . 39
6.2.2.1 General . 39
6.2.2.2 Detailed behaviour of the MME and the SGSN . 40
6.2.2.3 Detailed behaviour of the SMS-GMSC. 41
6.2.3 Alert Service Centre procedure . 42
6.2.3.1 General . 42
6.2.3.2 Detailed behaviour of the MME and the SGSN . 43
6.2.3.3 Detailed behaviour of the SMS-GMSC. 44
6.2.3.4 Detailed behaviour of the SMS-Router . 44
6.3 Protocol specification . 44
6.3.1 Routing considerations . 44
6.3.1.1 Routing for MO Forward SM messages: . 44
6.3.1.2 Routing for MT Forward SM messages: . 45
6.3.2 Commands . 45
6.3.2.1 Introduction . 45
6.3.2.2 Command-Code values . 45
6.3.2.3 MO-Forward-Short-Message-Request (OFR) Command . 46
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 5 ETSI TS 129 338 V17.2.0 (2023-10)
6.3.2.4 MO-Forward-Short-Message-Answer (OFA) Command . 46
6.3.2.5 MT-Forward-Short-Message-Request (TFR) Command . 47
6.3.2.6 MT-Forward-Short-Message-Answer (TFA) Command . 47
6.3.3 AVPs . 48
6.3.3.1 General . 48
6.3.3.2 SC-Address . 49
6.3.3.3 SM-RP-UI . 49
6.3.3.4 TFR-Flags . 49
6.3.3.5 SM-Delivery-Failure-Cause . 50
6.3.3.6 SM-Enumerated-Delivery-Failure-Cause . 50
6.3.3.7 SM-Diagnostic-Info . 50
6.3.3.8 Feature-List-ID AVP . 50
6.3.3.9 Feature-List AVP . 50
6.3.3.10 SM-Delivery-Timer. 50
6.3.3.11 SM-Delivery-Start-Time . 50
6.3.3.12 OFR-Flags . 51
6.3.3.13 SMSMI-Correlation-ID . 51
6.3.3.14 HSS-ID . 51
6.3.3.15 Originating-SIP-URI . 51
6.3.3.16 Destination-SIP-URI . 51
6.3.3.17 Maximum-Retransmission-Time . 51
6.3.3.18 Requested-Retransmission-Time . 51
6.3.3.19 SMS-GMSC-Address . 52
6.3.3.20 DRMP . 52
7 Result Codes and Experimental-Result values . 52
7.1 General . 52
7.2 Success . 52
7.3 Permanent Failures . 52
7.3.1 General . 52
7.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) . 52
7.3.3 DIAMETER_ERROR_ABSENT_USER (5550) . 52
7.3.4 DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS (5551) . 53
7.3.5 DIAMETER_ERROR_FACILITY_NOT_SUPPORTED (5552) . 53
7.3.6 DIAMETER_ERROR_ILLEGAL_USER (5553) . 53
7.3.7 DIAMETER_ERROR_ILLEGAL_EQUIPMENT (5554) . 53
7.3.8 DIAMETER_ERROR_SM_DELIVERY_FAILURE (5555) . 53
7.3.9 DIAMETER_ERROR_SERVICE_NOT_SUBSCRIBED (5556) . 53
7.3.10 DIAMETER_ERROR_SERVICE_BARRED (5557) . 53
7.3.11 DIAMETER_ERROR_MWD_LIST_FULL (5558) . 53
7.4 Transient Failures . 53
7.4.1 General . 53
Annex A (normative): Diameter message priority mechanism . 54
A.1 General . 54
A.2 S6c, SGd, Gdd interfaces . 54
Annex B (informative): Change history . 55
History . 57

ETSI
3GPP TS 29.338 version 17.2.0 Release 17 6 ETSI TS 129 338 V17.2.0 (2023-10)
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.338 version 17.2.0 Release 17 7 ETSI TS 129 338 V17.2.0 (2023-10)
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.338 version 17.2.0 Release 17 8 ETSI TS 129 338 V17.2.0 (2023-10)
1 Scope
The present document defines the Diameter-based interfaces specific to SMS when they are used in conjunction with
the "SMS in MME" architecture specified in 3GPP TS 23.272 [2] or for SGSN supporting EPS interfaces, or the" SMS
in 5GS" architecture specified in 3GPP TS 23.501 [21]. It comprises:
- the Diameter application for the S6c interface between the HSS/UDM and the central SMS functions (SMS-
GMSC, SMS Router) ;
- the Diameter application
- for the SGd interface between the MME/SMSF, the SMS-IWMSC, the SMS-GMSC and the SMS Router.
- for the Gdd interface between the SGSN, the SMS-IWMSC, the SMS-GMSC and the SMS Router.
For the purpose of supporting SMS in 5GS, the UDM may implement the requirements specified in the present
specification for HSS, with the following modification:
- "HSS" is to be replaced with "UDM".
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.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[4] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and
Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
[5] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details".
[6] IETF RFC 2234: "Augmented BNF for Syntax Specifications: ABNF".
[7] Void.
[8] IETF RFC 5516: "Diameter Command Code Registration for the Third Generation Partnership
Project (3GPP) Evolved Packet System (EPS)".
[9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[10] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane
LCS".
[11] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security ".
[12] IETF RFC 4960: "Stream Control Transport Protocol".
[13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[14] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; Protocol details".
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 9 ETSI TS 129 338 V17.2.0 (2023-10)
[15] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with
packet data networks and applications".
[16] 3GPP TS 23.003: "Numbering, addressing and identification".
[17] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol
(IP) access; Stage 2".
[18] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data
networks and applications".
[19] IETF RFC 7944: "Diameter Routing Message Priority".
[20] IETF RFC 6733: "Diameter Base Protocol".
[21] 3GPP TS 23.501:"System Architecture for the 5G System".
3 Definitions, symbols 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].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 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
TR 21.905 [1].
ABNF Augmented Backus-Naur Form
DRMP Diameter Routing Message Priority
DSCP Differentiated Services Code Point
IANA Internet Assigned Numbers Authority
IP-SM-GW IP Short Message Gateway
MWD Message Waiting Data
RP Relay layer Protocol
RP-MTI RP Message Type Indicator
RP-SMEA RP SME-Address
RP-UI RP User Information
SM RL Short Message Relay Layer
SMS-GMSC Gateway MSC for SMS
SMS-IWMSC Interworking MSC for SMS
SMSMI SMS without MSISDN in IMS
4 General
4.1 Introduction
The SMS in MME architecture is described in 3GPP TS 23.272 [2] and the SMS in 5GS architecture is described in
3GPP TS 23.501 [21], have specified the reference points S6c and SGd.
The clause 4 addresses Diameter aspects which are common to S6c, SGd and Gdd.
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 10 ETSI TS 129 338 V17.2.0 (2023-10)
4.2 Use of Diameter Base protocol
The Diameter base protocol as specified in IETF RFC 6733 [20] shall apply except as modified by the defined support
of the methods and the defined support of the commands and AVPs, result and error codes as specified in this
specification. Unless otherwise specified, the procedures (including error handling and unrecognised information
handling) shall be used unmodified.
4.3 Securing Diameter messages
For secure transport of Diameter messages, see 3GPP TS 33.210 [11].
4.4 Accounting functionality
Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on
the S6c, SGd and Gdd interfaces.
4.5 Use of sessions
Diameter sessions shall be implicitly terminated over the S6c, SGd and Gdd interfaces. An implicitly terminated session
is one for which the server does not maintain state information. The client shall not send any re-authorization or session
termination requests to the server.
The Diameter base protocol specified in IETF RFC 6733 [20] includes the Auth-Session-State AVP as the mechanism
for the implementation of implicitly terminated sessions.
The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value
NO_STATE_MAINTAINED (1), as described in IETF RFC 6733 [20]. As a consequence, the server shall not maintain
any state information about this session and the client shall not send any session termination request. Neither the
Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
4.6 Transport protocol
Diameter messages over the S6c, SGd and Gdd interfaces shall make use of SCTP as specified in IETF RFC 4960 [12]
as transport protocol.
4.7 Advertising application support
The MME, HSS, SMS-IWMSC, SMS-GMSC and SMS Router shall advertise support of the Diameter S6c Application
over the S6c interface and of the Diameter SGd Application over the SGd interface by including the value of the
application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The MME, SMS-GMSC and SMS
Router shall additionally advertise support of the Diameter S6c Application over the SGd interface if they support the
Alert Service Centre procedure between the MME, SMS-GMSC and SMS Router.
The SGSN, SMS-IWMSC, SMS-GMSC and SMS Router shall advertise support of the Diameter SGd Application over
the Gdd interface by including the value of the application identifier in the Auth-Application-Id AVP within the
Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-
Answer commands. The SGSN, SMS-GMSC and SMS Router shall additionally advertise support of the Diameter S6c
Application over the Gdd interface if they support the Alert Service Centre procedure between the SGSN, SMS-GMSC
and SMS Router.
The MTC-IWF and SMS-IWMSC shall advertise support of the Diameter SGd Application over the T4 interface if they
support the MO-Forward-Short-Message procedure between the SMS-IWMSC and the MTC-IWF.
The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-
Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-
Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer
commands.
ETSI
3GPP TS 29.338 version 17.2.0 Release 17 11 ETSI TS 129 338 V17.2.0 (2023-10)
The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is
not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the
Diameter node as per IETF RFC 6733 [20].
4.8 Diameter Application Identifier
The S6c and the SGd/Gdd interface protocols shall be defined, each, as an IETF vendor specific Diameter application,
where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP
(http://www.iana.org/assignments/enterprise-numbers) is 10415.
The Diameter application identifier assigned to the S6c Diameter application is 16777312 (allocated by IANA).
The Diameter application identifier assigned to the SGd Diameter application, which is also applicable to the Gdd and
T4 interfaces is 16777313 (allocated by IANA).
4.9 Use of the Supported-Features AVP
When new functionality is introduced on the S6c or SGd Diameter applications, it should be defined as optional. If
backwards incompatible changes can not be avoided, the new functionality shall be introduced as a new feature and
support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the S6c or SGd
applications is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2
of 3GPP TS 29.229 [5].
When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the
AVP shall not be defined mandatory in the command ABNF.
As defined in 3GPP TS 29.229 [5],
...