A.7 Default messages for SMS
34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification
A.7.1 MESSAGE for MT SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP |
|||
|
sent-by |
SS P-CSCF address: protected server port of SS |
|||
|
via-branch |
value starting with ‘z9hG4bK’ (NOTE 1) |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the IP-SM-GW |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
default public user identity of the UE |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
a random text string generated by the SS |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
Accept-Contact |
RFC 3841 [64] |
|||
|
ac-value |
+g.3gpp.smsip;require;explicit |
|||
|
Request-Disposition |
RFC 3841 [64] |
|||
|
fork-directive |
no-fork |
|||
|
P-Asserted-Identity |
RFC 3325 [89] |
|||
|
addr-spec |
SIP URI of the SS representing IP-SM-GW (same as in the From header) |
|||
|
P-Called-Party-ID |
RFC 7315 [132] |
|||
|
called-pty-id-spec |
same value as in the To header |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
RFC 3261 [15] |
|||
|
value |
length of message-body |
|||
|
Message-body |
RP-DATA message as specified in A.7.8 with RP‑User Data set to SMS-DELIVER type equal to – TP-MTI=’00’B |
TS 24.011 [92] |
NOTE 1: Branch parameter values sent by SS are different within a test case execution.
A.7.2 MESSAGE for delivery report for MT SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
same P-Asserted-Identity URI as received in A.7.1 |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP (when using UDP) or |
|||
|
sent-by |
not checked |
|||
|
via-branch |
value starting with ‘z9hG4bK’ |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the UE |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
same as P-Asserted-Identity URI received in A.7.1 |
TS 24.341 [90] |
||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
any value (but different from the Call-ID values used in preceding requests of this test case) |
|||
|
In-Reply-to |
RFC 3261 [15] |
|||
|
callid |
The value of the Call-Id received in the original MT SMS |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
header shall be present if UE uses TCP to send this request |
RFC 3261 [15] |
||
|
value |
length of message-body |
|||
|
Message-body |
RP-ACK message with RP‑User Data including SMS-DELIVERY-REPORT: TP-MTI=‘00’B (SMS-DELIVERY-REPORT) |
TS 24.011 [92] |
NOTE: X is not checked
A.7.3 MESSAGE for MO SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
Public Service Identity of the SM-SC: value not checked |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP (when using UDP) or |
|||
|
sent-by |
IP address or FQDN and protected server port of the UE |
|||
|
via-branch |
value starting with ‘z9hG4bK’ |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the UE |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
same as Request-URI. |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
must be present, value not checked |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
P-Access-Network-Info |
A2 |
RFC 7315 [132] |
||
|
access-net-spec |
A4 |
access network information and, if applicable, the cell ID |
||
|
A5 |
access network information for NR, containing access-class parameter with value "3GPP-NR" or access-type parameter with value "3GPP-NR-FDD" or "3GPP-NR-TDD", and also containing the cell ID |
Rel-15 |
||
|
Route |
RFC 3261 [15] |
|||
|
route-param |
<sip:SS P-CSCF address: protected server port of SS ;lr>, <sip:scscf.3gpp.org;lr> |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
header shall be present if UE uses TCP to send this request |
RFC 3261 [15] |
||
|
Value |
length of message-body |
|||
|
Message-body |
RP-DATA message as specified in A.7.7 with RP‑User Data set to SMS-SUBMIT type equal to – TP-MTI=’ 01’B (SMS-SUBMIT) – TP-RD=any allowed value – TP-VPF=any allowed value – TP-RP=any allowed value – TP-MR=any allowed value – TP-DA=any allowed value – TP-PID=any allowed value – TP-DCS=any allowed value – TP-VP=any allowed value if TP-VPF indicates TP-VP field present; TP-VP=not present otherwise – TP-UDL=set according to length of TP-UD field – TP-UD=must be present and non-empty |
TS 24.011 [92] |
|
Condition |
Explanation |
|
A1 |
Void |
|
A2 |
IMS security (A.6a/2 3GPP TS 34.229-2 [5]) |
|
A3 |
GIBA (A.6a/1 3GPP TS 34.229-2 [5]) |
|
A4 |
UE uses E-UTRAN access (A.18/1 3GPP TS 34.229-2 [5]) |
|
A5 |
UE uses NR access (A.18/5 3GPP TS 34.229-2 [5]) |
A.7.4 MESSAGE for submission report for MO SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP |
|||
|
sent-by |
SS P-CSCF address: protected server port of SS |
|||
|
via-branch |
value starting with ‘z9hG4bK’ (NOTE 1) |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the IP-SM-GW |
|||
|
Tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
default public user identity of the UE |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
Callid |
any value (but different from the Call-ID values used in preceding requests of this test case) |
|||
|
In-Reply-to |
RFC 3261 [15] |
|||
|
callid |
the value of the Call-Id received in the original MO SMS |
|||
|
Cseq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
Value |
non-zero value |
|||
|
Request-Disposition |
RFC 3261 [15] |
|||
|
fork-directive |
fork |
|||
|
P-Called-Party-ID |
RFC 3261 [15] |
|||
|
value |
same value as in the To header |
|||
|
P-Asserted-Identity |
RFC 3325 [136] |
|||
|
value |
Public Service Identity of the SM-SC (as received from UE in Request URI and To header in corresponding MESSAGE for MO SMS) |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
RFC 3261 [15] |
|||
|
value |
length of message-body |
|||
|
Message-body |
RP-ACK message with RP‑User Data including SMS-SUBMIT-REPORT: TP-MTI=‘01’B (SMS-SUBMIT-REPORT) |
TS 24.011 [92] |
NOTE 1: Branch parameter values sent by SS are different within a test case execution.
A.7.5 MESSAGE for status report for MO SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP |
|||
|
sent-by |
SS P-CSCF address: protected server port of SS |
|||
|
via-branch |
value starting with ‘z9hG4bK’ (NOTE 1) |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the IP-SM-GW |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
default public user identity of the UE |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
any value (but different from the Call-ID values used in preceding requests of this test case) |
|||
|
P-Asserted-Identity |
RFC 3325 [89] |
|||
|
addr-spec |
Public Service Identity of the SM-SC (as received from UE in Request URI and To header in corresponding MESSAGE for MO SMS) |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
CSeq value used in A.7.4 incremented by one |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
Request-Disposition |
RFC 3841 [64] |
|||
|
fork-directive |
no-fork |
|||
|
Accept-Contact |
RFC 3841 [64] |
|||
|
ac-value |
+g.3gpp.smsip;require;explicit |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
RFC 3261 [15] |
|||
|
value |
length of message-body |
|||
|
Message-body |
RP-DATA message as specified in A.7.8 with RP‑User Data set to SMS-STATUS-REPORT type equal to TP-MTI=’10’B (SMS-STATUS-REPORT) TP-MMS=’0’B TP-SRQ=’0’B TP-MR=same value as that set by the UE in the RP-DATA of the MO SMS TP-RA=same value as the TP-DA set by the UE in the RP-DATA of the MO SMS TP-SCTS=same value as that set by the SS in the RP-ACK acknowledging the MO SMS TP-DT=set by the SS (encoded as specified in TS 23.040 clause 9.2.3.11) TP-ST=’0000000’B (Short message received by the SME) |
TS 24.011 [92] |
NOTE 1: Branch parameter values sent by SS are different within a test case execution.
A.7.6 MESSAGE for acknowledgement for status report for MO SMS
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
same as P-Asserted-Identity URI received in A.7.5 |
TS 24.341 [90] |
||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP (when using UDP) or |
|||
|
sent-by |
not checked |
|||
|
via-branch |
value starting with ‘z9hG4bK’ |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the UE |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
Same as P-Asserted-Identity URI received in A.7.5 |
TS 24.341 [90] |
||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
any value (but different from the Call-ID values used in preceding requests of this test case) |
|||
|
In-Reply-to |
Rel-11 |
RFC 3261 [15] |
||
|
callid |
The value of the Call-Id received in the status report for which this is a delivery report |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/vnd.3gpp.sms |
|||
|
Content-Length |
header shall be present if UE uses TCP to send this request |
RFC 3261 [15] |
||
|
value |
length of message-body |
|||
|
Message-body |
RP-ACK message |
TS 24.011 [92] |
A.7.7 RP-DATA message (UE to Network)
|
Information element |
Value/Remark |
|
RP‑Message Type |
‘000’B |
|
RP‑Message Reference |
Any valid value |
|
RP‑Originator Address |
0 length address |
|
RP‑Destination Address |
TS-Service Centre Address(default value as defined in E.3.2.14) |
|
RP‑User Data |
Any valid value |
A.7.8 RP-DATA message (Network to UE)
|
Information element |
Value/Remark |
|
RP‑Message Type |
‘001’B |
|
RP‑Message Reference |
Any valid value |
|
RP‑Originator Address |
TS-Service Centre Address(default value as defined in E.3.2.14) |
|
RP‑Destination Address |
0 length address |
|
RP‑User Data |
Any valid value |