A.2 S6c, SGd, Gdd interfaces
29.3383GPPDiameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)Release 18TS
The Diameter message priority mechanism is an optional feature which may apply on one or several of the S6c,SGd,Gdd interfaces.
A 3GPP functional entity supporting the Diameter message priority mechanism over one or several of the S6c,SGd,Gdd interfaces shall comply with IETF RFC 7944 [19].
A 3GPP functional entity sending a request shall determine the required priority according to its policies. When priority is required, it shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level.
When a 3GPP functional entity receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request.
When a 3GPP functional entity receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response.
The decisions of the 3GPP functional entity for a required priority and for the priority level value are implementation specific.
If:
– a 3GPP functional entity supports using the Diameter message priority mechanism for DSCP marking purposes,
– the transport network utilizes DSCP marking, and
– message-dependant DSCP marking is possible for the protocol stack transporting Diameter,
then the 3GPP functional entity shall set the DSCP marking for transport of the request or response according to the required priority level.
Diameter requests related to high priority traffic shall contain a DRMP AVP with a high priority of which the level value is operator dependent.
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2012 |
CT#58 |
CP-120762 |
F |
TS sent for approval |
|||
|
2013-03 |
CT#59 |
CP-130030 |
0003 |
2 |
F |
Validity Time of Short Message |
|
|
2013-06 |
CT#60 |
CP-130300 |
0001 |
2 |
F |
Diameter for SMS with SGSN General |
|
|
2013-06 |
CT#60 |
CP-130300 |
0002 |
2 |
F |
Diameter for SMS with SGSN Complements |
|
|
2013-06 |
CT#60 |
CP-130300 |
0004 |
1 |
F |
S6c complements related to Diameter for SMS with SGSN |
|
|
2013-09 |
CT#61 |
CP-130450 |
0007 |
1 |
F |
Correction on Routing for MO SM |
|
|
2013-0 |
CT#61 |
CP-130456 |
0008 |
2 |
F |
SGSN Diameter address with Gdd support |
|
|
2013-12 |
CT#62 |
CP-130800 |
0009 |
3 |
F |
Diameter based protocols with SMS for IMS UE without MSISDN |
|
|
2014-09 |
CT#65 |
CP-140513 |
0010 |
2 |
F |
Identification of the HSS |
|
|
2014-12 |
CT#66 |
CP-140767 |
0013 |
1 |
F |
Corrections for some AVPs |
|
|
2014-12 |
CT#66 |
CP-140767 |
0011 |
1 |
F |
SC-Address in SRR |
|
|
2014-12 |
CT#66 |
CP-140767 |
0014 |
– |
F |
AVP codes corrections for SMSMI |
|
|
2014-12 |
CT#66 |
CP-140767 |
0016 |
F |
OFR-Flags AVP correction |
||
|
2015-12 |
CT#70 |
CP-150776 |
0017 |
3 |
F |
Mobile Terminating SMS handling for extended Idle mode DRX |
13.0.0 |
|
2015-12 |
CT#70 |
CP-150776 |
0018 |
1 |
F |
Mobile Terminating SMS handling for extended Idle mode DRX – Additional Option |
|
|
2016-03 |
CT#71 |
CP-160030 |
0019 |
– |
F |
Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX |
13.1.0 |
|
2016-03 |
CT#71 |
CP-160023 |
0020 |
1 |
F |
Diameter message priority over S6c, SGd, Gdd |
|
|
2016-06 |
CT#72 |
CP-160226 |
0021 |
– |
F |
Missing Requested-Retransmission-Time AVP in TFA Command |
13.2.0 |
|
2016-12 |
CT#74 |
CP-160664 |
0023 |
F |
Correction to change IETF drmp draft version to official RFC 7944 |
13.3.0 |
|
|
2016-12 |
CT#74 |
CP-160673 |
0022 |
1 |
F |
MO SMS over T4 |
14.0.0 |
|
2017-03 |
CT#75 |
CP-170036 |
0024 |
F |
SMS-MO over T4 |
14.1.0 |
|
|
2017-03 |
CT#75 |
CP-170048 |
0025 |
1 |
F |
Update of reference for the Diameter base protocol |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170048 |
0026 |
1 |
F |
Handling of the Vendor-Specific-Application-Id AVP |
14.1.0 |
|
2017-03 |
CT#75 |
CP-170048 |
0027 |
1 |
F |
Cardinality of the Failed-AVP AVP in answer |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171018 |
0029 |
1 |
F |
Support for signaling transport level packet marking |
14.2.0 |
|
2017-09 |
CT#77 |
CP-172013 |
0032 |
– |
F |
Correction of DRMP Procedures |
14.3.0 |
|
2017-09 |
CT#77 |
CP-172022 |
0030 |
2 |
F |
Correction of the data type used for SC-Address and SMS-GMSC-Address |
15.0.0 |
|
2018-12 |
CT#82 |
CP-183100 |
0033 |
2 |
F |
Clarification on presence of SC-Address in SRR and on MWD Status |
15.1.0 |
|
2020-06 |
CT#88e |
CP-201016 |
0034 |
1 |
F |
SMSF Address |
15.2.0 |
|
2020-06 |
CT#88e |
CP-201016 |
0035 |
1 |
F |
Support of SMS in 5G |
15.2.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2020-09 |
CT#89e |
CP-202043 |
0037 |
– |
A |
SMSF Address Corrections |
16.1.0 |
|
2021-03 |
CT#91e |
CP-210053 |
0039 |
1 |
F |
Corrections on SM-Delivery-Not-Intended |
16.2.0 |
|
2021-03 |
CT#91e |
CP-210027 |
0038 |
– |
d |
Inclusive language review: EIR lists |
17.0.0 |
|
2022-06 |
CT#96 |
CP-221060 |
0040 |
– |
F |
Clarification on detailed HSS behaviour for SMS |
17.1.0 |
|
2022-12 |
CT#98e |
CP-223038 |
0042 |
1 |
B |
UE Location (Cell-ID) missing over SGd (OFR & TFA) |
18.0.0 |