9.1.8 SMS over NAS
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
9.1.8.1 SMS over NAS / MO and MT SMS over NAS / Idle mode
9.1.8.1.1 Test Purpose (TP)
(1)
with { the UE in switched off state with valid USIM inserted }
ensure that {
when { the UE requests initial registration for SMS over NAS }
then { the UE shall send REGISTRATION REQUEST message with SMS requested bit of the 5GS update type IE "SMS over NAS supported" }
}
(2)
with { the UE in 5GMM-REGISTERED state }
ensure that {
when { the UE initiates a periodic registration update and the requirements to use SMS over NAS transport have not changed in the UE}
then { the UE sets the SMS requested bit of the 5GS updatetype IE in the REGISTRATION REQUEST message to the same value as indicated by the UE in the last REGISTRATION REQUEST message }
}
(3)
with { the UE in 5GMM_Connected state with NR RRC_IDLE mode and the UE has sent a SERVICE REQUEST message triggered by initiating MO SMS}
ensure that {
when { UE receives a SERVICE ACCEPT message from SS }
then { UE sends CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
}
(4)
with { UE has sent CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message }
then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }
}
(5)
with { the UE in 5GMM-REGISTERED state with NR RRC_IDLE mode, UE has received a paging request and UE has completed a SERVICE REQUEST procedure}
ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message }
then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message}
}
9.1.8.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 5.5.1.2.2, 5.5.1.2.4, 5.5.1.3.2, 5.5.1.3.4, 9.11.3.6 and 9.11.3.9A. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501 clause 5.5.1.2.2]
The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF,
a) when the UE performs initial registration for 5GS services;
b) when the UE performs initial registration for emergency services;
c) when the UE performs initial registration for SMS over NAS; and
d) when the UE moves from GERAN to NG-RAN coverage or the UE moves from a UTRAN to NG-RAN coverage.
…
The UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511.
…
If the UE requests the use of SMS over NAS, the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to “SMS over NAS supported”. When the 5GS update type IE is included in the REGISTRATION REQUEST for reasons other than requesting the use of SMS over NAS, and the UE does not need to register for SMS over NAS, the UE shall set the SMS requested bit of the 5GS update type IE to “SMS over NAS not supported” in the REGISTRATION REQUEST message.
[TS 24.501 clause 5.5.1.2.4]
If the initial registration request is accepted by the network, the AMF shall send a REGISTRATION ACCEPT message to the UE.
…
If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to “SMS over NAS supported”, and SMSF selection is successful, then the AMF shall send the REGISTRATION ACCEPT message after the SMSF has confirmed that the activation of the SMS service was successful. When sending the REGISTRATION ACCEPT message, the AMF shall:
a) set the SMS allowed bit of the 5GS registration result IE to “SMS over NAS allowed” in the REGISTRATION ACCEPT message, if the UE has set the SMS requested bit of the 5GS registration type IE to “SMS over NAS supported” in the REGISTRATION REQUEST message and the network allows the use of SMS over NAS for the UE; and
b) store the SMSF address and the value of the SMS allowed bit of the 5GS registration result IE in the UE 5GMM context and consider the UE available for SMS over NAS.
[TS 24.501 clause 5.5.1.3.2]
The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF,
l) when the UE needs to register for SMS over NAS, indicate a change in the requirements to use SMS over NAS, or de-register from SMS over NAS;
…
The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic update by sending a REGISTRATION REQUEST message to the AMF when the UE needs to request the use of SMS over NAS transport or the current requirements to use SMS over NAS transport change in the UE. The UE shall set the SMS requested bit of the 5GS update type IE in the REGISTRATION REQUEST message as specified in subclause 5.5.1.2.2.
When initiating a registration procedure for mobility and periodic registration update and the UE needs to send the 5GS update type IE for a reason different than indicating a change in requirement to use SMS over NAS, the UE shall set the SMS requested bit of the 5GS update type IE in the REGISTRATION REQUEST message to the same value as indicated by the UE in the last REGISTRATION REQUEST message.
If the UE no longer requires the use of SMS over NAS, then the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to “SMS over NAS not supported”.
[TS 24.501 clause 5.5.1.3.4]
If the registration update request has been accepted by the network, the AMF shall send a REGISTRATION ACCEPT message to the UE.
…
If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to “SMS over NAS not supported” and:
a) the SMSF address is stored in the UE 5GMM context and:
1) the UE is considered available for SMS over NAS; or
2) the UE is considered not available for SMS over NAS and the SMSF has confirmed that the activation of the SMS service is successful; or
b) the SMSF address is not stored in the UE 5GMM context, the SMSF selection is successful and the SMSF has confirmed that the activation of the SMS service is successful;
then the AMF shall set the SMS allowed bit of the 5GS registration result IE in the REGISTRATION ACCEPT message as specified in subclause 5.5.1.2.4. If the UE 5GMM context does not contain an SMSF address or the UE is not considered available for SMS over NAS, then the AMF shall:
a) store the SMSF address in the UE 5GMM context if not stored already; and
b) store the value of the SMS allowed bit of the 5GS registration result IE in the UE 5GMM context and consider the UE available for SMS over NAS.
If SMSF selection in the AMF or SMS activation via the SMSF is not successful, or the AMF does not allow the use of SMS over NAS, then the AMF shall set the SMS allowed bit of the 5GS registration result IE to “SMS over NAS not allowed" in the REGISTRATION ACCEPT message.
If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS not supported", then the AMF shall:
a) mark the 5GMM context to indicate that the UE is not available for SMS over NAS; and
NOTE 2: The AMF can notify the SMSF that the UE is deregistered from SMS over NAS based on local configuration.
b) set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not supported" in the REGISTRATION ACCEPT message.
When the UE receives the REGISTRATION ACCEPT message, if the UE is also registered over another access to the same PLMN, the UE considers the value indicated by the SMS allowed bit of the 5GS registration result IE as applicable for both accesses over which the UE is registered.
[TS 24.501 clause 9.11.3.6]
The purpose of the 5GS registration result information element is to specify the result of a registration procedure.
The 5GS registration result information element is coded as shown in figure 9.11.3.6.1 and table 9.11.3.6.1.
The 5GS registration result is a type 4 information element with a length of 3 octets.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||||||
|
5GS registration result IEI |
octet 1 |
||||||||||||||
|
Length of 5GS registration result contents |
octet 2 |
||||||||||||||
|
0 Spare |
0 Spare |
0 Spare |
0 Spare |
SMS allowed |
5GS registration result value |
octet 3 |
|||||||||
Figure 9.11.3.6.1: 5GS registration result information element
Table 9.11.3.6.1: 5GS registration result information element
|
5GS registration result value (octet 3, bits 1 to 3) |
||||
|
Bits |
||||
|
3 |
2 |
1 |
||
|
0 |
0 |
1 |
3GPP access |
|
|
0 |
1 |
0 |
Non-3GPP access |
|
|
0 |
1 |
1 |
3GPP access and non-3GPP access |
|
|
1 |
1 |
1 |
reserved |
|
|
All other values are unused and shall be treated as "3GPP access", if received by the UE. |
||||
|
SMS over NAS transport allowed (SMS allowed) (octet 3, bit 4) |
||||
|
Bit |
||||
|
4 |
||||
|
0 |
SMS over NAS not allowed |
|||
|
1 |
SMS over NAS allowed |
|||
|
Bits 5 to 8 of octet 3 are spare and shall be coded as zero. |
||||
[TS 24.501 clause 9.11.3.9A]
The purpose of the 5GS update type IE is to allow the UE to provide additional information to the network when performing a registration procedure.
The 5GS update type information element is coded as shown in figure 9.11.3.9A.1 and table 9.11.3.9A.1.
The 5GS update type is a type 4 information element.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||||||||
|
5GS update type IEI |
octet 1 |
||||||||||||||||
|
Length of 5GS update type |
octet 2 |
||||||||||||||||
|
0 Spare |
0 Spare |
0 Spare |
0 Spare |
0 Spare |
0 Spare |
NG-RAN-RCU |
SMS requested |
octet 3 |
|||||||||
Figure 9.11.3.9A.1: 5GS update type information element
Table 9.11.3.9A.1: 5GS update type information element
|
SMS over NAS transport requested (SMS requested) (octet 3, bit 1) |
||
|
Bit |
||
|
1 |
||
|
0 |
SMS over NAS not supported |
|
|
1 |
SMS over NAS supported |
|
|
NG-RAN Radio Capability Update (NG-RAN-RCU) (octet 3, bit 2) |
||
|
Bits |
||
|
2 |
||
|
0 |
NG-RAN radio capability update not needed |
|
|
1 |
NG-RAN radio capability update needed |
|
|
Bits 3 to 8 of octet 3 are spare and shall be coded as zero. |
||
9.1.8.1.3 Test description
9.1.8.1.3.1 Pre-test conditions
System Simulator:
NGC Cell A belongs to Home PLMN and TAI1;
UE:
The UE does not have any stored SMS message.
Preamble:
The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4].
9.1.8.1.3.2 Test procedure sequence
Table 9.1.8.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The UE is switched ON. |
– |
– |
– |
– |
|
2 – 4 |
UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS 38.508-1 [4]. |
– |
– |
– |
– |
|
5 |
Check: Does UE transmit a REGISTRATION REQUEST message including 5GS update type IE with SMS requested bit set to "SMS over NAS supported"? |
–> |
REGISTRATION REQUEST |
1 |
P |
|
6 – 14 |
Steps 5 to 13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4]are performed. |
– |
– |
– |
– |
|
15 |
SS transmits REGISTRATION ACCEPT message including 5GS registration result with SMS allowed bit set to “SMS over NAS allowed” and T3512 value set to 3 minutes. |
<– |
REGISTRATION ACCEPT |
– |
– |
|
16 -21a1 |
Steps 15 to 20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] . |
– |
– |
– |
– |
|
21A |
Wait for the expiry of T3512. |
– |
– |
– |
– |
|
22 – 24 |
UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4]. |
– |
– |
– |
– |
|
25 |
Check: Does UE perform periodic Registration, including 5GS update type IE with SMS requested bit set to "SMS over NAS supported"? |
–> |
REGISTRATION REQUEST |
2 |
P |
|
26 – 34 |
Void. |
– |
– |
– |
– |
|
35 |
SS transmits REGISTRATION ACCEPT message including 5GS registration result with SMS allowed bit set to “SMS over NAS allowed” and T3512 value set to 3 minutes. |
<– |
REGISTRATION ACCEPT |
– |
– |
|
35A |
The UE transmits a REGISTRATION COMPLETE message. |
–> |
REGISTRATION COMPLETE |
– |
– |
|
36 |
The SS transmits an RRCRelease message. |
– |
– |
– |
– |
|
37 |
Sending of a 160 character MO SMS is initiated at the UE via MMI or AT command. |
– |
– |
– |
– |
|
38 |
The UE establishes RRC connection and transmits a SERVICE REQUEST message by executing steps 2-4 of Table 4.5.4.2-2 in TS 38.508-1 [4]. |
–> |
SERVICE REQUEST |
||
|
39 -42 |
Steps 5 to 8 of Table 4.5.4.2-3 of the generic procedure in TS 38.508-1 [4]are performed. |
– |
– |
– |
– |
|
43 |
The UE transmits a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message. |
–> |
UPLINK NAS TRANSPORT |
3 |
P |
|
44 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
45 |
The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
46 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message? |
–> |
UPLINK NAS TRANSPORT |
4 |
P |
|
47 |
The SS transmits an RRCRelease message |
– |
– |
– |
– |
|
48 |
The SS pages the UE using NG-5G-S-TMSI. |
– |
– |
– |
– |
|
49 |
The UE establishes RRC connection and transmits a SERVICE REQUEST message by executing steps 2-4 of Table 4.5.4.2-3 in TS 38.508-1 [4]. |
–> |
SERVICE REQUEST |
– |
– |
|
50-53 |
Steps 5 to 8 of Table 4.5.4.2-3 of the generic procedure in TS 38.508-1 [4] are performed. |
– |
– |
– |
– |
|
54 |
The SS transmits a CP-DATA containing a RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message to the UE. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
55 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
5 |
P |
|
56 |
Check: Does the UE transmit a CP-DATA containing a RP-ACK RPDU encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
5 |
P |
|
57 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS transport message to the UE. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
9.1.8.1.3.3 Specific message contents
Table 9.1.8.1.3.3-1: REGISTRATION REQUEST (step 5, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration type |
||||
|
5GS registration type value |
‘001’B |
INITIAL |
||
|
5GS update type |
||||
|
SMS requested |
SMS over NAS supported |
|||
Table 9.1.8.1.3.3-2: REGISTRATION ACCEPT (steps 15 and 35, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration result |
||||
|
SMS allowed |
SMS over NAS allowed |
|||
|
T3512 value |
||||
|
Timer value |
‘00011’B |
|||
|
Unit |
‘101’B |
|||
Table 9.1.8.1.3.3-3: REGISTRATION REQUEST (step 25, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GS registration type |
||||
|
5GS registration type value |
‘011’B |
PERIODIC |
||
|
5GS update type |
||||
|
SMS requested |
SMS over NAS supported |
|||
Table 9.1.8.1.3.3-3A: SERVICE REQUEST (step 38, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-16 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Service type |
||||
|
Service type value |
‘0000’B |
signalling |
||
Table 9.1.8.1.3.3-4: UL NAS TRANSPORT (step 43, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU |
||
Table 9.1.8.1.3.3-5: DL NAS TRANSPORT (step 44, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.1.3.3-6: DL NAS TRANSPORT (step 45, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.1.3.3-7: UL NAS TRANSPORT (step 46, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.1.3.3-8: DL NAS TRANSPORT (step 54, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA |
||
Table 9.1.8.1.3.3-9: UL NAS TRANSPORT (step 55, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.1.3.3-10: UL NAS TRANSPORT (step 56, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK |
||
Table 9.1.8.1.3.3-11: DL NAS TRANSPORT (step 57, Table 9.1.8.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
9.1.8.2 SMS over NAS / Multiple MO and MT SMS over NAS / Connected mode
9.1.8.2.1 Test Purpose (TP)
(1)
with { the UE is in 5GMM-REGISTERED state and 5GMM-CONNECTED mode over 3GPP access }
ensure that {
when { a Multiple MO SMS is initiated at the UE }
then { UE sends CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
}
(2)
with { UE has sent CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message and has another MO SMS to send }
ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message }
then { UE does not send a final CP-ACK before it sends a CP-DATA containing the successive RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
}
(3)
with { UE has sent CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message and has no further MO SMS to send }
ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message }
then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message }
}
(4)
with { the UE is in 5GMM-REGISTERED state and 5GMM-CONNECTED mode over 3GPP access }
ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message, and subsequently a second CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message with different transaction identifier }
then { UE sends twice a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message}
}
9.1.8.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501 clause 4.5.4.2, and TS 24.011 clause 9.11.3.9A. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501 clause 4.5.4.2]
If the lower layers indicate that the access attempt is allowed, the NAS shall take the following action depending on the event which triggered the access attempt:
a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication or an MO-SMSoIP-attempt-started indication, the NAS shall notify the upper layers that the access attempt is allowed;
b) if the event which triggered the access attempt was a request from upper layers to send a mobile originated SMS over NAS, 5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message;
[TS 24.011 clause 5.4]
In the case of a SMS transfer via the PS domain, when the MS chooses to use the same PS signalling connection (in Iu mode and in S1 mode if packet-switched service is used); or in the case of a SMS transfer via the PS domain in A/Gb mode; or in the case of SMS transfer through the EPS, or in the case of SMS transfer in N1 mode, then:
– the MS shall transmit the CP-DATA for the successive RPDU and shall not transmit the final CP‑ACK for the current SMS (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK);
– the Transaction Identifier used for the successive RPDU shall be different to that used for the current RPDU; and
– the MS shall not transmit the CP-DATA for the successive RPDU before the final CP‑DATA (i.e. the one that carried the RP‑ACK) has been received.
NOTE: When an MS sends successive memory available notifications and/or mobile originated short messages on different RR connections (in A/Gb mode) or signalling connections (in Iu mode and S1 mode), the MS is strongly recommended to use different Transaction Identifiers for the old and new MM connections.
It is possible that the final CP‑ACK of a short message transfer may not be received (e.g. due to transmission errors and/or hand overs).
For mobile terminated transfers, if the CP‑ACK is lost, the reception of a CP‑DATA with a different transaction identifier and carrying an RPDU shall be interpreted as the implicit reception of the awaited CP‑ACK followed by the reception of the new CP‑DATA message.
For mobile originated transfers, if the CP‑ACK is lost or not sent by the MS, the following events shall be interpreted as the implicit reception of the awaited CP‑ACK:
– in the case of a SMS transfer via the CS domain,, the reception of a CM SERVICE REQUEST followed by a CP‑DATA with a different transaction identifier and carrying an RPDU; or
– in the case of a SMS transfer via the PS domain, the reception of a CP-DATA with a different transaction identifier and carrying an RPDU.
9.1.8.2.3 Test description
9.1.8.2.3.1 Pre-test conditions
System Simulator:
NGC Cell A belongs to Home PLMN and TAI1.
UE:
The UE does not have any stored SMS message.
Preamble:
The UE is in state 3N-A, registered with "SMS over NAS supported".
9.1.8.2.3.2 Test procedure sequence
Table 9.1.8.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Sending of 3 MO SMS as multiple SMS is initiated at the UE via MMI or AT command |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
1 |
P |
|
3 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
4 |
The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
5 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 6 is transmitted? |
–> |
UPLINK NAS TRANSPORT |
2 |
F |
|
6 |
Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
2 |
P |
|
7 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
8 |
The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
9 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 10 is transmitted? |
–> |
UPLINK NAS TRANSPORT |
2 |
F |
|
10 |
Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
2 |
P |
|
11 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
12 |
The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
13 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message? |
–> |
UPLINK NAS TRANSPORT |
3 |
P |
|
14 |
The SS transmits a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message to the UE. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
15 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
4 |
P |
|
16 |
Check: Does the UE transmit a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
4 |
P |
|
17 |
The SS transmits a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message to the UE. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
|
18 |
Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
4 |
P |
|
19 |
Check: Does the UE transmit a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message? |
–> |
UPLINK NAS TRANSPORT |
4 |
P |
|
20 |
The SS transmits a CP-ACK encapsulated in a Downlink NAS transport message to the UE. |
<– |
DOWNLINK NAS TRANSPORT |
– |
– |
9.1.8.2.3.3 Specific message contents
Table 9.1.8.2.3.3-1: UL NAS TRANSPORT (step 2, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU TI used in steps 2, 3 and 4 shall be x1. |
||
Table 9.1.8.2.3.3-2: DL NAS TRANSPORT (step 3, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-3: DL NAS TRANSPORT (step 4, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.2.3.3-4: UL NAS TRANSPORT (step 6, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU TI used in steps 6, 7 and 8 shall be x2, with x1 <> x2 (see step 2). |
||
Table 9.1.8.2.3.3-5: DL NAS TRANSPORT (step 7, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-6: DL NAS TRANSPORT (step 8, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.2.3.3-7: UL NAS TRANSPORT (step 10, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU TI used in steps 10, 11, 12 and 13 shall be x3, with x3 <> x2 (see step 6). |
||
Table 9.1.8.2.3.3-8: DL NAS TRANSPORT (step 11, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-9: DL NAS TRANSPORT (step 12, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.2.3.3-10: UL NAS TRANSPORT (step 13, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-11: DL NAS TRANSPORT (step 14, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU TI used in steps 14, 15 and 16 is y1. |
||
Table 9.1.8.2.3.3-12: UL NAS TRANSPORT (step 15, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-13: UL NAS TRANSPORT (step 16, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.2.3.3-14: DL NAS TRANSPORT (step 17, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-DATA RPDU TI used in steps 17, 18, 19 and 20 is y2, with y2 <> y1 (see step 14). |
||
Table 9.1.8.2.3.3-15: UL NAS TRANSPORT (step 18, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||
Table 9.1.8.2.3.3-16: UL NAS TRANSPORT (step 19, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-DATA |
RP-ACK RPDU |
||
Table 9.1.8.2.3.3-17: DL NAS TRANSPORT (step 20, Table 9.1.8.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-11 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0010’B |
SMS |
||
|
Payload container |
CP-ACK |
|||