16.2 Short message service point to point on PS mode
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
All of test cases in this clause are applied to the UE supported PS mode.
16.2.1 SMS mobile terminated
16.2.1.1 Definition
16.2.1.2 Conformance requirements
An active UE shall be able to receive short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is a PDP context in progress. A report will always be returned to the SC, confirming that the UE has received the short message.
References
3GPP TS 23.040 clauses 3.1, 9.2.3.16.
16.2.1.3 Test purpose
To verify the ability of a UE to receive and decode the SMS where provided for the point to point service.
16.2.1.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the SMS message storage shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Support for session management state "PDP-ACTIVE".
Maximum number of retransmissions of an unacknowledged CP-DATA message.
Test procedure
a) Mobile terminates establishment of Radio Resource Connection. After the completion of RRC Connection the SS authenticates the UE and activates ciphering.
After the SS receives SECURITY MODE COMPLETE, the SS sends a CP-DATA message. The information element of the CP-DATA message will be RP-DATA RPDU (SMS DELIVER TPDU).
b) The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
c) The SS sends a CP-ACK to the UE within TC1M with no further CP-DATA messages and the SS initiates RRC connection release.
d) Steps a), b) and c) are repeated but the first CP-DATA message from the UE is not acknowledged. The second CP-DATA message from the UE is acknowledged by a CP-ACK within a time TC1M.
e) Steps a) and b) are repeated. The SS is configured not to send CP-ACK. Then maximum 3 CP‑DATA retransmissions may occur. After a duration of 4 times TC1M + 10 s (Maximum for T3317) SS initiates the RRC connection release. This is the appropriate time to wait to verify that the UE does not send more than the maximum allowed (3) CP-DATA retransmissions.
f) The SMS message store shall be cleared manually by the operator.
g) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered.
The SS sends a CP-DATA message. The information element of the CP-DATA message will be RP-DATA RPDU (SMS DELIVER TPDU). The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
h) The SS sends a CP-ACK to the UE within TC1M with no further CP-DATA messages and the SS initiates RRC connection release. The SMS message store shall be cleared manually by the operator.
i) Steps g) and h) are repeated but the first CP-DATA message from the UE is not acknowledged. The second CP-DATA message from the UE is acknowledged by a CP-ACK within a time TC1M.
j) Step g) is repeated. The SS is configured not to send CP-ACK. Then maximum 3 CP-DATA retransmissions may occur. After a duration of 4 times TC1M + 10 s (Maximum for T3317) SS initiates the RRC connection release. This is the appropriate time to wait to verify that the UE does not send more than the maximum allowed (3) CP-DATA retransmissions (during PDP context in progress).
k) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The PDP context is cleared by the SS with a disconnect message. (The PDP context deactivating is continued in parallel to the following exchange of messages related to SMS).
The SS sends a CP-DATA RPDU (SMS DELIVER TPDU) message. The information element of the CP-DATA message is RP-DATA.
The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
The SS sends a CP-ACK to the UE within TC1M with no further CP-DATA messages and the SS initiates RRC connection release.
The SMS message store shall be cleared manually by the operator.
l) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The PDP context shall be cleared from the UE. (The PDP context deactivating is continued in parallel to the following exchange of messages related to SMS).
The SS sends a CP-DATA message. The information element of the CP-DATA message is RP‑DATA RPDU (SMS DELIVER TPDU).
The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
The SS sends a CP-ACK to the UE within TC1M with no further CP-DATA messages and the SS initiates RRC connection release.
The SMS message store shall be cleared manually by the operator.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108. The IE “Paging cause” in the PAGING TYPE 1 message is set to “Terminating Low Priority Signalling”. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Terminating Low Priority Signalling”. |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
SS |
The SS starts integrity protection |
||
|
6 |
(void) |
|||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
8 |
SS |
Waits max 25 s for CP-ACK |
||
|
9 |
–> |
CP-ACK |
||
|
10 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
11 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
12 |
<– |
CP-ACK |
||
|
13 |
SS |
The SS releases the RRC connection. |
||
|
14 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
15 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108. The IE “Paging cause” in the PAGING TYPE 1 message is set to “Terminating Low Priority Signalling”. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Terminating Low Priority Signalling” |
||
|
16 |
–> |
SERVICE REQUEST |
||
|
17 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
SS |
The SS starts integrity protection |
||
|
20 |
(void) |
|||
|
21 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
22 |
SS |
Waits max 25 s for CP-ACK |
||
|
23 |
–> |
CP-ACK |
||
|
24 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
25 |
–> |
CP-DATA |
First CP-DATA from UE, contains RP-ACK RPDU |
|
|
26 |
SS |
First CP-DATA message not acknowledged by SS |
||
|
27 |
–> |
CP-DATA |
Retransmitted CP-DATA from UE within twice TC1M, after step 25, contains RP-ACK RPDU |
|
|
28 |
<– |
CP-ACK |
Second CP_DATA message is acknowledged |
|
|
29 |
SS |
The SS releases the RRC connection. |
||
|
30 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
31 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108. The IE “Paging cause” in the PAGING TYPE 1 message is set to “Terminating Low Priority Signalling”. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Terminating Low Priority Signalling”. |
||
|
32 |
–> |
SERVICE REQUEST |
||
|
33 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
34 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
35 |
SS |
The SS starts integrity protection |
||
|
36 |
(void) |
|||
|
37 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
38 |
SS |
Waits max 25 s for CP-ACK |
||
|
39 |
–> |
CP-ACK |
||
|
40 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
41 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
42 |
SS |
First CP-DATA message not acknowledged by SS |
||
|
43 |
CP-DATA |
Retransmitted CP-DATA from UE within twice TC1M after step 41, contains RP-ACK RPDU |
||
|
44 |
SS |
Retransmitted CP-DATA message not acknowledged by SS |
||
|
45 |
UE |
Depending upon the maximum number of CP-DATA retransmissions implemented, step 43 and 44 may be repeated. The maximum number of retransmissions may however not exceed three. The UE may also send less than 3 re-transmissions. The same RRC connection shall be used for CP-DATA retransmissions. |
||
|
45a |
UE |
The UE may send a Signalling Connection Release Indication message immediately when TC1M has run out. This is according to TS 24.011 clause 5.3.2.1. |
||
|
46 |
SS |
The SS releases the RRC connection after a duration of 4*TC1M + 10 s (Maximum for T3317) from step 41. |
||
|
47 |
Void |
|||
|
48 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
49 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
50 |
(void) |
|||
|
51 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
52 |
SS |
Waits max 25 s for CP-ACK |
||
|
53 |
–> |
CP-ACK |
||
|
54 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
55 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
56 |
<– |
CP-ACK |
||
|
57 |
<– |
DEACTIVATE PDP CONTEXT REQUEST |
Deactivates an existing PDP context. |
|
|
58 |
–> |
DEACTIVATE PDP CONTEXT ACCEPT |
||
|
58a |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
58b |
<– |
DETACH ACCEPT |
||
|
58c |
SS |
The SS releases the RRC connection. |
||
|
59 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
60 |
UE |
Clear the SMS message store |
||
|
61 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
62 |
(void) |
|||
|
63 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
64 |
SS |
Waits max 25 s for CP-ACK |
||
|
65 |
–> |
CP-ACK |
||
|
66 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
67 |
–> |
CP-DATA |
First CP-DATA from UE, contains RP-ACK RPDU |
|
|
68 |
SS |
First CP-DATA message not acknowledged by SS |
||
|
69 |
–> |
CP-DATA |
Retransmitted CP-DATA message within twice TC1M after step 67, contains RP-ACK RPDU |
|
|
70 |
<– |
CP-ACK |
Second CP-DATA message is acknowledged |
|
|
71 |
<– |
DEACTIVATE PDP CONTEXT REQUEST |
Deactivates an existing PDP context. |
|
|
72 |
–> |
DEACTIVATE PDP CONTEXT ACCEPT |
||
|
72a |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
72b |
<– |
DETACH ACCEPT |
||
|
73 |
SS |
The SS releases the RRC connection |
||
|
74 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
75 |
UE |
Clear the SMS message store |
||
|
76 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
77 |
(void) |
|||
|
78 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
79 |
SS |
Waits max 25 s for CP-ACK |
||
|
80 |
–> |
CP-ACK |
||
|
81 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
82 |
–> |
CP-DATA |
First CP-DATA from UE, contains RP-ACK RPDU |
|
|
83 |
SS |
First CP-DATA message not acknowledged by SS |
||
|
84 |
–> |
CP-DATA |
Retransmitted CP-DATA message within twice TC1M after step 82, contains RP-ACK RPDU |
|
|
85 |
SS |
Retransmitted CP-DATA message not acknowledged by SS |
||
|
86 |
UE |
Depending on the maximum number of CP-DATA retransmissions implemented, step 83-84 may be repeated. The maximum number of retransmissions may however not exceed three. The UE may also send less than 3 re-transmissions. The same RRC connection shall be used for CP-DATA retransmissions. |
||
|
86a |
<– |
DEACTIVATE PDP CONTEXT REQUEST |
Deactivates an existing PDP context. |
|
|
86b |
–> |
DEACTIVATE PDP CONTEXT ACCEPT |
||
|
86c |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
86d |
<– |
DETACH ACCEPT |
||
|
87 |
SS |
The SS releases the RRC connection after a duration of 4*TC1M + 10 s (Maximum for T3317) from step 82. |
||
|
88 |
(void) |
|||
|
89 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
90 |
UE |
Clear the SMS message store |
||
|
91 |
SS |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
92 |
(void) |
|||
|
93 |
(void) |
|||
|
94 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
94a |
<– |
DEACTIVATE PDP CONTEXT REQUEST |
The PDP context is deactivated by the SS. The PDP context deactivating is continued in parallel to the following exchange of messages related to SMS. |
|
|
94b |
–> |
DEACTIVATE PDP CONTEXT ACCEPT |
This message should be transmitted within T3395 Expiry and at any step before step 96 |
|
|
94c |
VOID |
|||
|
94d |
VOID |
|||
|
94e |
VOID |
|||
|
95 |
SS |
Waits max 25 s for CP-ACK |
||
|
96 |
–> |
CP-ACK |
||
|
97 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
98 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
99 |
<– |
CP-ACK |
||
|
99a |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
99b |
<– |
DETACH ACCEPT |
||
|
100 |
SS |
The SS releases the RRC connection |
||
|
101 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
102 |
UE |
Clear the SMS message store |
||
|
103 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
104 |
(void) |
|||
|
105 |
–> |
DEACTIVATE PDP CONTEXT REQUEST |
The PDP context is deactivated by the UE. The PDP context deactivation is continued in parallel to the following |
|
|
106 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
107 |
<– |
DEACTIVATE PDP CONTEXT ACCEPT |
||
|
107a |
VOID |
|||
|
107b |
VOID |
|||
|
107c |
VOID |
|||
|
108 |
|
CP-ACK |
shall be sent before 25 s after the start of step 106 |
|
|
109 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
110 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
111 |
<– |
CP-ACK |
||
|
111a |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
111b |
<– |
DETACH ACCEPT |
||
|
112 |
SS |
The SS releases the RRC connection |
||
|
113 |
UE |
The UE shall indicate that an SM has arrived. |
||
|
114 |
UE |
Clear the SMS message store |
||
|
NOTE: Time values for SS wait time are chosen sufficiently high to be sure that the UE has enough time to respond to the different messages. |
||||
Specific Message Contents
SMS DELIVER TPDU (not containing a type 0 message)
|
Information element |
Comment Value |
||
|
TP-PID |
Different from Type 0: “01000000”B |
||
|
TP-UDL |
160 |
||
|
TP-UD (140 octets) |
text of message (160 characters) |
||
|
NOTE: The 160 characters in TP-UD shall include at least one occurrence of each character in the default alphabet (see 3GPP TS 23.038, clause 6.2.1). |
|||
16.2.1.5 Test requirements
After step 7 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s.
After step 14 UE shall indicate that an SM has arrived.
After step 27 UE shall retransmit CP-DATA containing RP-ACK within twice TC1M.
After step 30 UE shall indicate that an SM has arrived.
After step 43 UE shall repeat CP-DATA retransmissions and the maximum number of retransmissions must not exceed three.
After step 48 UE shall indicate that an SM has arrived.
After step 51 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s.
After step 59 UE shall indicate that an SM has arrived.
After step 69 UE shall retransmit CP-DATA containing RP-ACK within twice TC1M.
After step 74 UE shall indicate that an SM has arrived.
After step 84 UE shall repeat CP-DATA retransmissions and the maximum number of retransmissions must not exceed three.
After step 89 UE shall indicate that an SM has arrived.
After step 94 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s.
After step 101 UE shall indicate that an SM has arrived.
After step 106 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s.
After step 113 UE shall indicate that an SM has arrived.
16.2.2 SMS mobile originated
16.2.2.1 Definition
16.2.2.2 Conformance requirements
An active UE shall be able to submit short message TPDU (SMS-SUBMIT) at any time, independently of whether or not there is a PDP context in progress.
References
3GPP TS 23.040 clause 3.1, 9.2.3.16.
16.2.2.3 Test purpose
To verify that the UE is able to correctly send a short message where the SMS is provided for the point to point service.
16.2.2.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the SMS message storage shall be empty.
Related ICS/IXIT Statements
Support for Short message MO/PP.
Support for state PDP-ACTIVE of session management.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Maximum number of retransmissions of an unacknowledged CP-DATA message.
Test procedure
a) The UE shall be set up to send an SM to the SS. The UE establishes successfully an RRC connection.
b) The SS performs authentication and after that, the SS starts integrity protection.
c) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the UE with a CP-ACK message within TC1M followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for the CP-ACK message.
d) The SS sends a RRC connection release message to the UE.
e) Steps a) and b) are repeated. The SS is configured not to send the CP-ACK message. Then maximum 3 CP-DATA retransmissions may occur. After a duration of 4 times TC1M + 10 s (Maximum for T3317) SS initiates RRC connection release. This is the appropriate time to wait to verify that the UE does not send more than the maximum CP-DATA retransmissions.
f) Steps a) and b) are repeated. On receipt of the CP-DATA from the UE the SS sends a CP-ERROR message within TC1M containing a "Network Failure" cause. Then the SS initiates RRC connection release.
g) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The UE is set up to send an SM to the SS.
h) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the UE with a CP-ACK message within TC1M followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for the CP-ACK message. Then the SS sends a RRC connection release message to the UE.
i) Step g) is repeated. The SS is configured not to send the CP-ACK message. Then maximum 3 CP‑DATA retransmissions may occur. After a duration of 4 times TC1M + 10 s (Maximum for T3317) the SS initiates RRC connection release. This is the appropriate time to wait to verify that the UE does not send more than the maximum CP-DATA retransmissions (during a PDP context in progress).
j) (void)
k) The UE is set up to send an SM to the SS. On receipt of the SERVICE REQUEST the SS sends a SERVICE REJECT message with the reject cause set to "GPRS services not allowed". After 5 s the SS initiates RRC connection release.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
The UE is set up to send an SM |
||
|
2 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”. |
||
|
3 |
(void) |
|||
|
4 |
(void) |
|||
|
5 |
–> |
SERVICE REQUEST |
||
|
6 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
7 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
8 |
SS |
The SS starts integrity protection |
||
|
9 |
(void) |
|||
|
10 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
11 |
<– |
CP-ACK |
Sent within TC1M after step 10 |
|
|
12 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
13 |
SS |
Waits max 25 s for CP-ACK |
||
|
14 |
–> |
CP-ACK |
||
|
15 |
SS |
The SS releases the RRC connection |
||
|
16 |
(void) |
|||
|
17 |
UE |
The UE is set up to send an SM |
||
|
18 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”. |
||
|
19 |
(void) |
|||
|
20 |
(void) |
|||
|
21 |
–> |
SERVICE REQUEST |
||
|
22 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
23 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
24 |
SS |
The SS starts integrity protection |
||
|
25 |
(void) |
|||
|
26 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
27 |
SS |
SS configured not to send CP-ACK |
||
|
28 |
–> |
CP-DATA |
Retransmitted CP-DATA message within twice TC1M after step 26 |
|
|
29 |
UE |
Depending on the maximum number of CP-DATA retransmissions implemented, step 28 may be repeated. The maximum number of retransmissions may however not exceed three. The UE may also send less than 3 re-transmissions. The same RRC connection shall be used for CP-DATA retransmissions. |
||
|
29a |
UE |
The UE may send a Signalling Connection Release Indication message immediately when TC1M has run out. This is according to TS 24.011 clause 5.3.2.1. |
||
|
30 |
SS |
The SS releases the RRC connection after a duration of 4*TC1M + 10 s (Maximum for T3317) from step 26. |
||
|
30a |
(void) |
|||
|
31 |
(void) |
|||
|
32 |
UE |
The UE is set up to send an SM |
||
|
33 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”. |
||
|
34 |
(void) |
|||
|
35 |
(void) |
|||
|
36 |
–> |
SERVICE REQUEST |
||
|
37 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
38 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
39 |
SS |
The SS starts integrity protection |
||
|
40 |
(void) |
|||
|
41 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
42 |
<– |
CP-ERROR |
Sent within TC1M containing "Network Failure" cause. |
|
|
43 |
SS |
The SS releases the RRC connection. |
||
|
44 |
(void) |
|||
|
45 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
46 |
UE |
The UE is set up to send an SM |
||
|
47 |
(void) |
|||
|
48 |
(void) |
|||
|
49 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
50 |
<– |
CP-ACK |
Sent within TC1M after step 49 |
|
|
51 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
52 |
SS |
Waits max 25 s for CP-ACK |
||
|
53 |
–> |
CP-ACK |
||
|
53a |
<– |
DEACTIVATE PDP CONTEXT REQUEST |
Deactivates an existing PDP context. |
|
|
53b |
–> |
DEACTIVATE PDP CONTEXT ACCEPT |
||
|
53c |
–> |
DETACH REQUEST |
A manual attach UE is detached |
|
|
53d |
<– |
DETACH ACCEPT |
||
|
54 |
SS |
The SS releases the RRC connection. |
||
|
55 |
(void) |
|||
|
56 |
UE |
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. |
||
|
56a |
UE |
The UE is set up to send an SM. Continue at step 59 (signalling connection already established in step 56). |
||
|
56b |
(void) |
|||
|
56c |
(void) |
|||
|
56d |
(void) |
|||
|
56e |
(void) |
|||
|
57 |
(void) |
|||
|
58 |
(void) |
|||
|
59 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
60 |
SS |
SS configured not to send CP-ACK |
||
|
61 |
–> |
CP-DATA |
Retransmitted CP-DATA message within twice TC1M after step 59 |
|
|
62 |
UE |
Depending on the maximum number of CP-DATA retransmissions implemented, step 61 may be repeated. The maximum number of retransmissions may however not exceed three. The UE may also send less than 3 re-transmissions. The same RRC connection shall be used for CP-DATA retransmissions. |
||
|
63 |
SS |
The SS releases the RRC connection after a duration of 4*TC1M + 10 s (Maximum for T3317) from step 59. |
||
|
63a |
(void) |
|||
|
64 |
(void) |
|||
|
65-77 |
(void) |
|||
|
78 |
UE |
The UE is set up to send an SM |
||
|
79 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”. |
||
|
80 |
(void) |
|||
|
81 |
–> |
SERVICE REQUEST |
||
|
82 |
<– |
SERVICE REJECT |
Reject cause set to "GPRS services not allowed" |
|
|
83 |
SS |
The SS releases the RRC connection. The RRC connection is releases 5 s after SERVICE REJECT |
||
|
NOTE: Time values for SS wait times are chosen sufficiently high to be sure that the UE has enough time to respond to the different messages. |
||||
Specific Message Contents
SMS SUBMIT TPDU
|
Information element |
Comment Value |
|
TP-UDL |
as applicable |
|
TP-UD (140 octets) |
160 ASCII characters |
16.2.2.5 Test requirements
After step 10 UE shall send a CP-DATA containing RP-data. The RP-DATA shall contain SMS SUBMIT TPDU.
After step 26 UE shall retransmit a CP-DATA containing RP-data. The RP-DATA shall contain SMS SUBMIT TPDU.
After step 49 UE shall send a CP-DATA containing RP-data. The RP-DATA shall contain SMS SUBMIT TPDU.
After step 61 UE shall repeat CP-DATA retransmissions and the maximum number of retransmissions must not exceed three.
After step 82 UE shall not send CP-DATA.
16.2.3 Test of memory full condition and memory available notification:
The Memory Available Notification provides a means for the UE to notify the network that it has memory available to receive one or more short messages. The SMS status field in the USIM contains status information on the "memory available" notification flag.
16.2.3.1 Definition
16.2.3.2 Conformance requirement
1. When a mobile terminated message is Class 2, the UE shall ensure that the message has been transferred to the SMS data field in the USIM before sending an acknowledgement to the SC. The UE shall return a protocol error message if the short message cannot be stored in the USIM and there is other short message storage available in the UE. If all the short message storage in the UE is already in use, the UE shall return "memory capability exceeded".
2. When the UE rejects a short message due to lack of available memory capability the need to transfer notification shall be stored in the USIM.
3. If the memory capability becomes available because memory is cleared, the value of the memory capability exceeded notification flag in the USIM is read. If the flag is set, the UE notifies the network that memory capability is now available. After a positive acknowledgement from the network, the ME unsets the memory capability exceeded notification flag in the USIM.
References
– 3GPP TS 23.038 clause 4.
– 3GPP TS 23.040 clauses 9.2.3.10, 10.3 (operation 14).
16.2.3.3 Test purpose
1. To verify that the UE sends the correct acknowledgement when its memory in the USIM becomes full.
2. To verify that the UE sends the correct acknowledgement when its memory in the ME and the USIM becomes full, and sets the "memory exceeded" notification flag in the USIM.
3. To verify that the UE performs the "memory available" procedure when its message store becomes available for receiving short messages, and only at this moment.
16.2.3.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the SMS message storage shall be empty;
– the UE shall be connected to the USIM simulator. The following shall be present in the USIM simulator:
– EFSMS with at least one record;
– EFSMSS, with SMS "Memory Cap. Exceed" notification flag set to "memory available";
– Service no. 10 (SMS) in EFUST set to allocated and activated.
– for storing of Class 1 Short Messages the UE shall be set up to store Short Messages in the ME memory (by way of MMI, as described in ICS/IXIT statement).
Related ICS/IXIT Statements
Support for Short message MT/PP.
Whether SMS messages are stored in the USIM and/or the ME.
The value of timer TC1M.
Test procedure
a) step a) of clause 16.2.5.3 (test of Class 2 Short Messages) is repeated until the UE sends a negative acknowledgement (RP-ERROR). The USIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the USIM.
b) a Class 1 Short Message is sent to the UE.
c) step b) is repeated until the UE sends a negative acknowledgement (RP-ERROR). The USIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the USIM.
d) a Short Message is sent to the UE with the DCS field of the SMS-DELIVER TPDU set to 0.
e) the SS prompts the operator to read a short message and to remove it from the message store of the UE.
f) the SS waits for a RRC CONNECTION REQUEST from the UE, and sends a RRC CONNECTION SETUP.
g) after the SS receives a RRC CONNECTION SETUP COMPLETE, the SS authenticates the UE and activates ciphering.
h) the SS answers to the RP-SMMA from the UE with a CP-DATA containing a RP-ACK RPDU.
i) after the UE has acknowledged the CP-DATA with a CP-ACK, the SS releases the RRC connection. The USIM simulator shall indicate if the "memory capability exceeded" notification flag has been unset on the USIM.
j) step e) is repeated.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 2 Short Message |
|
|
8 |
SS |
Waits max 25 s for CP-ACK |
||
|
9 |
–> |
CP-ACK |
||
|
10 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
11 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
12 |
<– |
CP-ACK |
Within TC1M after step 11 |
|
|
13 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. Step 1-13 is repeated until UE sends a negative acknowledgement (RP-ERROR) in step 11. The RP-ERROR RPDU cause field shall be "Protocol error, unspecified" if there is message capability in the USIM, or "Memory capability exceeded" if there is no message capability in the USIM. If the total memory store of the UE is full, the ME shall set the "memory capability exceeded" notification flag on the USIM. |
|
|
14 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
15 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
16 |
–> |
SERVICE REQUEST |
||
|
17 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
<– |
SECURITY MODE COMMAND |
||
|
20 |
–> |
SECURITY MODE COMPLETE |
||
|
21 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 1 Short Message |
|
|
22 |
SS |
Waits max 25 s for CP-ACK |
||
|
23 |
–> |
CP-ACK |
||
|
24 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
25 |
–> |
CP-DATA |
Shall contain RP-ACK RPDU if there is memory capability in the ME. If not it shall contain RP-ERROR RPDU which cause field shall be "memory capability exceeded". If the total memory store of the UE now becomes full at this step, the ME shall set the "memory cap. exceed" notification flag on the USIM. |
|
|
26 |
<– |
CP-ACK |
Within TC1M after step 25 |
|
|
27 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. Step 16-27 is repeated until the UE sends an RP-ERROR. The USIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the USIM. |
|
|
28 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
29 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
30 |
–> |
SERVICE REQUEST |
||
|
31 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
32 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
33 |
<– |
SECURITY MODE COMMAND |
||
|
34 |
–> |
SECURITY MODE COMPLETE |
||
|
35 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) with TP-DCS set to 0 |
|
|
36 |
SS |
Waits max 25 s for CP-ACK |
||
|
37 |
–> |
CP-ACK |
||
|
38 |
SS |
Waits max 60 s for RP-ACK RPDU |
||
|
39 |
–> |
CP-DATA |
Shall contain RP-ERROR RPDU with error cause "memory capability exceeded". |
|
|
40 |
<– |
CP-ACK |
Within TC1M after step 39 |
|
|
41 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. |
|
|
42 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
43 |
SS |
Prompts the operator to remove one of the short messages from the message store of the UE. |
||
|
44 |
<– |
SYSTEM INFORMATION |
BCCH |
|
|
45 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
46 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
47 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
48 |
–> |
SERVICE REQUEST |
||
|
49 |
<– |
SERVICE ACCEPT |
||
|
50 |
–> |
CP-DATA |
Contains RP-SMMA RPDU |
|
|
51 |
<– |
CP-ACK |
||
|
52 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
53 |
–> |
CP-ACK |
Acknowledge of CP-DATA containing the RP-ACK RPDU. The ME shall unset the "memory capability exceeded" notification flag on the USIM. |
|
|
54 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. The USIM simulator shall indicate if the "memory capability exceeded" notification flag has been unset on the USIM. |
|
|
55 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
56 |
SS |
Prompts the operator to remove one of the short messages from the message store of the UE. |
||
|
57 |
UE |
Shall not attempt to send a RP-SMMA RPDU. This is verified by checking that the UE does not send a CHANNEL REQUEST message with the establishment cause "Other services which can be completed with an SDCCH" |
||
|
NOTE: Time values for SS wait time are chosen sufficiently high to be sure that the UE has enough time to respond to the different messages. |
||||
Specific Message Contents
SMS-DELIVER TPDU in step 7
|
Information element |
Comment Value |
|
TP-DCS |
default alphabet, class 2 "11110010"B |
SMS-DELIVER TPDU in step 21
|
TP-DCS |
default alphabet, class 1 "11110001"B |
SMS-DELIVER TPDU in step 35
|
TP-DCS |
default alphabet "00000000"B |
16.2.3.5 Test requirements
After UE sends a negative acknowledgement (RP-ERROR) in step 11, the USIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the USIM.
After UE sends a negative acknowledgement (RP-ERROR) in step 25, the USIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the USIM.
After step 53 the ME shall unset the "memory capability exceeded" notification flag on the USIM.
After step 57 UE shall not attempt to send a RP-SMMA RPDU.
16.2.4 Test of the status report capabilities and of SMS-COMMAND:
This test applies to UEs which support the status report capabilities.
16.2.4.1 Definition
16.2.4.2 Conformance requirement
The SMS offers the SC the capabilities of informing the UE of the status of a previously sent mobile originated short message. This is achieved by the SC returning a status report TPDU (SMS-STATUS-REPORT) to the originating UE.
SMS-COMMAND enables an UE to invoke an operation at the SC.
The UE shall increment TP-MR by 1 for each SMS-SUBMIT or SMS-COMMAND being submitted.
References
– 3GPP TS 23.040 clauses 3.2.9, 9.2.3.2, 9.2.3.4, 9.2.3.5, 9.2.3.6, 9.2.3.14, 9.2.3.18, 9.2.3.19, 9.2.3.26.
16.2.4.3 Test purpose
1) To verify that the UE is able to accept a SMS-STATUS-REPORT TPDU.
2) To verify that the UE is able to use the SMS-COMMAND functionality correctly and sends an SMS-COMMAND TPDU with the correct TP-Message-Reference.
16.2.4.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED".
Related ICS/IXIT Statements
Support of SMS MO/PP and MT/PP.
Test procedure
a) The UE is made to send a Mobile Originated short message setting TP-SRR as in steps a) to d) of test 16.2.2 (SMS Mobile originated).
b) The SS sends a CP-DATA message containing a RP-DATA RPDU itself containing an SMS-STATUS-REPORT TPDU.
c) The SS sends a RRC CONNECTION RELEASE message.
d) The UE is made to send an SMS-COMMAND message enquiring about the previously submitted short message.
e) Void.
f) The SS acknowledges the CP-DATA message from the UE with a CP-ACK followed by a CP-DATA message containing an RP-ACK RPDU.
g) After receiving the CP-ACK from the UE, the SS releases the RRC connection by using a RRC CONNECTION RELEASE message.
h) The UE is made to send an SMS-COMMAND message requiring to delete the previously submitted short message.
i) steps e) to g) are repeated.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
<– |
SYSTEM INFORMATION |
BCCH |
|
|
2 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
3 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
4 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
5 |
–> |
SERVICE REQUEST |
||
|
6 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
7 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
8 |
<– |
SECURITY MODE COMMAND |
||
|
9 |
–> |
SECURITY MODE COMPLETE |
||
|
10 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
11 |
<– |
CP-ACK |
Sent within TC1M after step 10 |
|
|
12 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
13 |
SS |
Waits max 25 s for CP-ACK |
||
|
14 |
–> |
CP-ACK |
||
|
15 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. |
|
|
16 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
17 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
18 |
–> |
SERVICE REQUEST |
||
|
19 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
20 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
21 |
<– |
SECURITY MODE COMMAND |
||
|
22 |
–> |
SECURITY MODE COMPLETE |
||
|
23 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS-STATUS-REPORT TPDU) |
|
|
24 |
–> |
CP-ACK |
||
|
25 |
–> |
CP-DATA |
Contains RP-ACK RPDU |
|
|
26 |
<– |
CP-ACK |
||
|
27 |
<– |
RRC CONNECTION RELEASE |
||
|
28 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
29 |
UE |
The UE is made to send an SMS-COMMAND message enquiring about the previously submitted SM |
||
|
30 |
<– |
SYSTEM INFORMATION |
BCCH |
|
|
31 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
32 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
33 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
34 |
–> |
SERVICE REQUEST |
||
|
35 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
36 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
37 |
<– |
SECURITY MODE COMMAND |
||
|
38 |
–> |
SECURITY MODE COMPLETE |
||
|
39 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR |
|
|
40 |
<– |
CP-ACK |
||
|
41 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
42 |
–> |
CP-ACK |
||
|
43 |
<– |
RRC CONNECTION RELEASE |
||
|
44 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
45 |
UE |
The UE is made to send an SMS-COMMAND |
message requiring to delete the previously submitted SM. |
|
|
46 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
47 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
48 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
49 |
–> |
SERVICE REQUEST |
||
|
50 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
51 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
52 |
<– |
SECURITY MODE COMMAND |
||
|
53 |
–> |
SECURITY MODE COMPLETE |
||
|
54 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR |
|
|
55 |
<– |
CP-ACK |
||
|
56 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
57 |
–> |
CP-ACK |
||
|
58 |
<– |
RRC CONNECTION RELEASE |
||
|
59 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
Specific Message Contents
SMS SUBMIT TPDU
|
Information element |
Comment Value |
|
TP-SRR |
status report is requested "1"B |
SMS-STATUS-REPORT TPDU (SS to UE in step 23):
|
Information element |
Comment Value |
|
TP-MR |
same as previous SMS-SUBMIT |
|
TP-MMS |
no more messages "1"B |
|
TP-SRQ |
result of SMS-SUBMIT "0"B |
|
TP-RA |
same as the Destination address of the SMS-SUBMIT |
|
TP-ST |
SM received "00000000"B |
first SMS-COMMAND TPDU (UE to SS in step 39)
|
Information element |
Comment Value |
|
TP-MR |
TP-MR in previous SMS-SUBMIT plus "1" |
|
TP-SRR |
status report requested "1"B |
|
TP-CT |
Enquiry relating to previously submitted short message "00000000"B |
|
TP-MN |
not checked (TP-MR in previous SMS-SUBMIT) |
second SMS-COMMAND TPDU (UE to SS in step 54)
|
Information element |
Comment Value |
|
TP-MR |
TP-MR in previous SMS-COMMAND plus "1" |
|
TP-CT |
Delete previously submitted short message |
|
TP-MN |
not checked (TP-MR in previous SMS-SUBMIT) |
16.2.4.5 Test requirements
After step 23 UE accept a SMS-STATUS-REPORT TPDU.
After step 39 UE shall send a SMS-COMMAND TPDU with the correct TP-Message-Reference.
After step 54 UE shall send a SMS-COMMAND TPDU with the correct TP-Message-Reference.
16.2.5 Test of message class 0 to 3
16.2.5.1 Short message class 0
16.2.5.1.1 Definition
16.2.5.1.2 Conformance requirement
When a mobile terminated message is class 0 and the UE has the capability of indicating short messages, the UE shall indicate the message immediately and send an acknowledgement to the SC when the message has successfully reached the UE irrespective of whether there is memory available in the USIM or ME. The message shall not be automatically stored in the USIM or ME.
Reference
3GPP TS 23.038 clause 4.
16.2.5.1.3 Test purpose
To verify that the UE will accept and indicate but not store a class 0 message, and that it will accept and indicate a class 0 message if its message store is full.
NOTE: failure of this test in a UE could cause it to reject a class 0 message when its SMS memory becomes full. This could lead to unwanted repetitions between the UE and the service centre.
16.2.5.1.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Test procedure
a) The SS sends a class 0 message by using the method described in step a) of clause 16.2.1 but with the TPDU described in this clause.
b) The UE message store shall be filled (for example by using the method of clause 16.2.3 test of the memory available notification) with the same SMS-DELIVER TPDU except that TP-DCS is set to class 1.
c) The SS sends a class 0 message as in step a).
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 0 Short Message |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
UE |
The content of the short message shall be indicated by the ME. The UE shall not store the message. This can be checked by verifying that it is impossible to retrieve any short messages from the UE message store. |
||
|
14 |
SS |
The UE message store shall be filled (for example by using the method of 16.2.3) with Class 1 SMS-DELIVER TPDU. |
||
|
15 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
16 |
–> |
SERVICE REQUEST |
||
|
17 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
<– |
SECURITY MODE COMMAND |
||
|
20 |
–> |
SECURITY MODE COMPLETE |
||
|
21 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 0 Short Message |
|
|
22 |
–> |
CP-ACK |
||
|
23 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
24 |
<– |
CP-ACK |
||
|
25 |
<– |
RRC CONNECTION RELEASE |
||
|
26 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
27 |
UE |
The content of the short message shall be indicated by the ME. |
||
Specific Message Contents
SMS-DELIVER TPDU (containing a class 0 message) (SS to UE)
|
Information element |
Comment Value |
|
TP-DCS |
default alphabet, class 0 "1111 0000"B |
SMS-DELIVER TPDU (containing a class 1 message to fill the UE message store) (SS to UE)
|
Information element |
Comment Value |
|
TP-DCS |
default alphabet, class 1 "1111 0001"B |
16.2.5.1.5 Test requirements
After step 7 UE shall accept and indicate but not store a class 0 message.
After step 21 UE shall accept and indicate a class 0 message.
16.2.5.2 Test of class 1 short messages
This test shall apply to UEs which support:
– storing of received Class 1 Short Messages; and
– indicating of stored Short Messages.
16.2.5.2.1 Definition
16.2.5.2.2 Conformance requirement
When a mobile terminated message is class 1, the UE shall send an acknowledgement to the SC when the message has successfully reached the UE and can be stored, either in the ME or in the USIM.
Reference
3GPP TS 23.038 clause 4.
16.2.5.2.3 Test purpose
This procedure verifies that the UE acts correctly on receiving a class 1 message, i.e. that it stores the message in the ME or USIM and sends an acknowledgement (at RP and CP-Layer).
16.2.5.2.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the UE message store shall be empty;
– for storing of class 1 Short Messages, the UE shall be set up to store Short Messages in the ME memory (by way of MMI, as described in ICS/IXIT statement).
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Test procedure
a) The SS delivers a Short Message of class 1 to the UE as specified in clause 16.2.1, step a).
b) The Short Message is recalled (e.g. by means of the MMI).
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 1 Short Message |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
UE |
The short message shall be recalled and indicated at the UE. |
||
Specific Message Contents
SMS-DELIVER TPDU (containing a class 1 message) (SS to UE)
|
Information element |
Comment Value |
|
TP-DCS |
default alphabet, class 1 "1111 0001"B |
16.2.5.2.5 Test requirements
After step 7 UE shall store the message in the ME or USIM and send an acknowledgement.
16.2.5.3 Test of class 2 short messages
16.2.5.3.1 Definition
Class 2 Short Messages are defined as USIM specific, and the UE shall ensure that a message of this class is stored on the USIM.
16.2.5.3.2 Conformance requirement
When a mobile terminated message is Class 2, the UE shall ensure that the message has been correctly transferred to the SMS data field in the USIM before sending an acknowledgement to the SC. The UE shall return a "protocol error, unspecified" error message if the short message cannot be stored in the USIM and there is other short message storage available at the UE. If all the short message storage at the UE is already in use, the UE shall return "memory capacity exceeded".
References
3GPP TS 23.040 clause 9.2.3.10.
3GPP TS 23.038 clause 4.3
3GPP TS 34.108 clause 8.3.2.28.
16.2.5.3.3 Test purpose
This procedure verifies that the UE acts correctly on receiving a class 2 message, i.e. that it stores the message correctly in the USIM, and if this is not possible, returns a protocol error message, with the correct error cause, to the network.
There are 2 cases:
1) if the UE supports storing of short messages in the USIM and in the ME, and storage in the ME is not full, and the short message cannot be stored in the USIM, the error cause shall be "protocol error, unspecified";
2) if the UE supports storing of short messages in the USIM and not in the ME, and storage in the ME is not full, and the short message cannot be stored in the USIM, the error cause shall be "memory capacity exceeded".
NOTE: If the UE supports storing of short messages in the USIM and the ME, and storage in the ME is full, and the short message cannot be stored in the USIM, the error cause shall be "memory capacity exceeded". This case is not tested in this test.
16.2.5.3.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the ME message store shall be empty;
– the ME shall be connected to the USIM simulator. The following shall be present in the USIM simulator:
– EFSMS with at least two free records and one full record;
– EFSMSS, with SMS "Memory Cap. Exceed" notification flag set to "memory available";
– Service no. 10 (SMS) in EFUST set to allocated and activated;
– for storing of Class 1 Short Messages the UE shall be set up to store Short Messages in the ME memory (by way of MMI, as described in ICS/IXIT statement).
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Test procedure
a) The SS delivers a Short Message of class 2 to the UE as specified in clause 16.2.1, step b).
b) Following an attempt by the ME to store the short message in a free record of EFSMS in the USIM, the USIM simulator returns the status response "OK" ("90 00").
c) Step a) is repeated.
d) Following an attempt by the ME to store the short message in a free record of EFSMS in the USIM, the USIM simulator returns the status response "memory problem" ("92 40").
e) The USIM simulator indicates if an attempt was made in steps a) and c) to store the messages and if the messages are stored according to the requirement.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 2 Short Message |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
ME |
The ME shall correctly store the short message in a free record of EFSMS in the USIM, i.e. – the ME shall use a free record – the first byte of the record shall indicate "message received by UE from network" – the TS-Service-Centre-Address shall be correctly stored – the TPDU shall be identical to that sent by the SS – bytes following the TPDU shall be set to "FF" |
||
|
10 |
USIM |
The USIM simulator returns the status response "OK" ("90 00"). The USIM simulator shall indicate if an attempt was made by the ME to store the short message in the USIM. |
||
|
11 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
12 |
<– |
CP-ACK |
||
|
13 |
<– |
RRC CONNECTION RELEASE |
||
|
14 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
15 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
16 |
–> |
SERVICE REQUEST |
||
|
17 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
<– |
SECURITY MODE COMMAND |
||
|
20 |
–> |
SECURITY MODE COMPLETE |
||
|
21 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 2 Short Message |
|
|
22 |
–> |
CP-ACK |
||
|
23 |
ME |
The ME shall attempt to store the short message in a free record of EFSMS in the USIM. |
||
|
24 |
USIM |
The USIM simulator returns the status response "memory problem" ("92 40"). The USIM simulator shall indicate if an attempt was made by the ME to store the short message in the USIM. |
||
|
25 |
–> |
CP-DATA |
Contains RP-ERROR RPDU with error cause "protocol error, unspecified" if the UE supports storing of short messages in the ME, or error cause "memory capacity exceeded" if not. |
|
|
26 |
<– |
CP-ACK |
||
|
27 |
<– |
RRC CONNECTION RELEASE |
||
|
28 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
Specific Message Contents
SMS-DELIVER TPDU (containing a class 2 message) (SS to UE)
|
Information element |
Comment Value |
|
TP-DCS |
default alphabet, class 2 "1111 0010"B |
16.2.5.3.5 Test requirements
After step 10 UE shall confirm that the short message is stored in the USIM and send CP-DATA containing RP-ACK RPDU.
After step 24 UE shall confirm that the short message cannot be stored in the USIM and send CP-DATA containing RP-ERROR RPDU. If UE supports storing of short message in the ME, the error cause of RP-ERROR RPDU shall be "protocol error, unspecified", and if not the error cause of RP-ERROR RPDU shall be "memory capacity exceeded"
16.2.5.4 Test of class 3 short messages
For further study.
16.2.6 Test of short message type 0 (R99 and REL-4 UE)
16.2.6.1 Definition and applicability
This tests that the UE correctly acknowledges the receipt of the short message type 0 to the SC in Packet Switched mode. It is highly recommended that the UE discards the contents of the short message type 0.
This test shall apply to all R99 and REL-4 UEs supporting receipt of short messages in PS mode.
16.2.6.2 Conformance requirement
When a mobile terminated message is type 0, the UE shall acknowledge receipt of the short message to the SC but may discard its contents.
Note: It is highly recommended that the UE discards the type 0 short message. This means that the UE is able to receive the type 0 short message irrespective of whether there is memory available in the (U)SIM or ME or not, the UE does not indicate the receipt of the type 0 short message to the user, and the message is not stored in the (U)SIM or ME.
Reference(s)
3GPP TS 23.040, 9.2.3.9.
16.2.6.3 Test purpose
To verify that the UE will acknowledge receipt of the short message to the SC. The UE should discard its contents.
NOTE: failure of this test in a UE could cause it to reject a type 0 message when the network is trying to reach the UE. This could lead to unwanted repetitions between the UE and the service centre.
16.2.6.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
the UE shall be in GMM-state "GMM-REGISTERED";
Related ICS/IXIT Statements
Support for Short Message MT/PP.
The value of timer TC1M.
Foreseen Final State of UE
Idle, updated.
Test Procedure
The SS sends a type 0 message by using the method described in step a) of section 16.2.1 but with the TPDU described in this section.
Maximum Duration of Test
1 minute
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), type 0 Short Message |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
–> |
CP-DATA |
Contains RP-ACK TP-Protocol-Identifier (TP-PID). |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
UE |
It is highly recommended that the UE discards the type 0 short message. This means that the UE is able to receive the type 0 short message irrespective of whether there is memory available in the (U)SIM or ME or not, the UE does not indicate the receipt of the type 0 short message to the user, and the message is not stored in the (U)SIM or ME. |
||
Specific Message Contents:
SMS-DELIVER TPDU (containing a type 0 message) (SS to UE):
|
Information element |
Comment Value |
|
TP-MTI |
SMS-DELIVER "00"B |
|
TP-MMS |
more messages are waiting in SC "0"B |
|
TP-RP |
no reply path "0"B |
|
TP-UDHI |
TP-UD contains only the SM "0"B |
|
TP-SRI |
no status report returned 0 |
|
TP-OA |
an international number coded E.164 |
|
TP-PID |
Type 0: "01000000"B |
|
TP-DCS |
default alphabet “0000 0000"B |
|
TP-SCTS |
any legal value (cf. 3GPP TS 23.040) |
|
TP-UDL |
160 |
|
TP-UD (140 octets) |
text of message (160 characters) |
16.2.6a Test of short message type 0 ( REL-5 UE)
16.2.6a.1 Definition and applicability
This tests that the UE correctly acknowledges the receipt of the short message type 0 to the SC in Packet Switched mode. The UE discards the contents of the short message type 0.
This test shall apply to all REL-5 UEs supporting receipt of short messages in PS mode.
16.2.6a.2 Conformance requirement
When a mobile terminated message is type 0, the UE shall acknowledge receipt of the short message to the SC but shall discard its contents. This means that
– the UE shall be able to receive the type 0 short message irrespective of whether there is memory available in the (U)SIM or ME or not,
– the UE shall not indicate the receipt of the type 0 short message to the user,
– the short message shall neither be stored in the (U)SIM nor ME.
References
3GPP TS 23.040 9.2.3.2, 9.2.3.4, 9.2.3.7, 9.2.3.9, 9.2.3.10, 9.2.3.11, 9.2.3.16, 9.2.3.17, 9.2.3.23.
16.2.6a.3 Test purpose
To verify that the UE will acknowledge receipt of the short message to the SC. The UE shall discard its contents. This means that
– the UE shall be able to receive the type 0 short message irrespective of whether there is memory available in the (U)SIM or ME or not,
– the UE shall not indicate the receipt of the type 0 short message to the user,
– the short message shall neither be stored in the (U)SIM nor ME.
NOTE: failure of this test in a UE could cause it to reject a type 0 message when the network is trying to reach the UE. This could lead to unwanted repetitions between the US and the service centre. In addition service affecting restrictions could happen to the customer.
16.2.6a.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
the UE shall be in GMM-state "GMM-REGISTERED";
the ME- and (U)SIM message store shall be empty.
Related ICS/IXIT Statements
Support for Short Message MT/PP.
The value of timer TC1M.
Foreseen Final State of UE
Idle, updated.
Test Procedure
a) The SS sends a type 0 short message by using the method described in step a) of clause 16.2.1 but with the TPDU described in this section.
b) The ME- and (U)SIM short message store shall be filled (for example by using the method of clause 16.2.3 test of the memory available notification).
c) The SS sends a type 0 short message as in step a).
Maximum Duration of Test
5 minutes
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), type 0 Short Message |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
UE |
The UE shall discard the type 0 short message. This means that the UE does not indicate the receipt of the type 0 short message to the user. The UE shall not store the message in the (U)SIM or ME. This can be checked by verifying that it is impossible to retrieve any short messages from the ME- and (U)SIM message store. |
||
|
14 |
SS |
The ME- and (U)SIM message store shall be filled (for example by using the method of 16.1.3). |
||
|
15 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
16 |
–> |
SERVICE REQUEST |
||
|
17 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
<– |
SECURITY MODE COMMAND |
||
|
20 |
–> |
SECURITY MODE COMPLETE |
||
|
21 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU), type 0 Short Message |
|
|
22 |
–> |
CP-ACK |
||
|
23 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
24 |
<– |
CP-ACK |
||
|
25 |
<– |
RRC CONNECTION RELEASE |
||
|
26 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
27 |
UE |
The UE shall discard the type 0 short message. This means that the UE does not indicate the receipt of the type 0 short message to the user. The UE shall not store the message in the (U)SIM or ME. This can be checked by verifying that it is impossible to retrieve any short messages from the ME- and (U)SIM message store. |
||
Specific Message Contents:
SMS-DELIVER TPDU (containing a type 0 message) (SS to UE):
|
Information element |
Comment Value |
|
TP-MTI |
SMS-DELIVER "00"B |
|
TP-MMS |
more messages are waiting in SC "0"B |
|
TP-RP |
no reply path "0"B |
|
TP-UDHI |
TP-UD contains only the SM "0"B |
|
TP-SRI |
no status report returned "0"B |
|
TP-OA |
an international number coded E.164 |
|
TP-PID |
Type 0: "01000000"B |
|
TP-DCS |
default alphabet “0000 0000"B |
|
TP-SCTS |
any legal value (cf. 3GPP TS 23.040) |
|
TP-UDL |
160 |
|
TP-UD (140 octets) |
text of message (160 characters) |
16.2.6a.5 Test requirements
After step 9 (ME- and (U)SIM message store not filled) UE shall send CP-DATA containing RP-ACK RPDU (TP-Protocol-Identifier: type 0 Short Message).
After step 13 UE shall discard the type 0 short message (it is impossible to retrieve any short messages from the ME- and (U)SIM message store).
After step 23 (ME- and (U)SIM message store filled) UE shall send CP-DATA containing RP-ACK RPDU (TP-Protocol-Identifier: type 0 Short Message).
After step 27 UE shall discard the type 0 short message (it is impossible to retrieve any short messages from the ME- and (U)SIM message store).
16.2.7 Test of the replace mechanism for SM type 1-7
16.2.7.1 Definition
16.2.7.2 Conformance requirement
On receipt of a short message, the UE shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code. If such a code is present, then the UE will check the associated originating address (TP-OA) and replace any existing stored message having the same Protocol Identifier code and originating address with the new short message.
References
3GPP TS 23.040 clause 9.2.3.2, 9.2.3.9.
16.2.7.3 Test purpose
This procedure verifies the correct implementation of the replace mechanism for Replace Short Messages.
16.2.7.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Test procedure
a) Two different numbers n and m are drawn randomly between 1 and 7. Two different addresses for TP-Originating-Address (TPOA1 and TPOA2) are drawn.
b) The SS delivers a short message to the UE as specified in clause 16.2.1 step a). In the SMS‑DELIVER TPDU, the TP-Protocol-Identifier parameter is "Replace Short Message Type n", the TP-Originating-Address is TPOA1, and the RP-Originating-Address is RPOA.
c) Step b) is repeated but with a different TP-Originating-Address (TPOA2), and different contents of TP-User-Data in the SMS-DELIVER TPDU. The other parameters are the same as in step b).
d)
e) Step c) is repeated but with the TP-Protocol-Identifier equal to "Replace Short Message Type m", and contents of TP-User-Data different from the former two messages. The other parameters are the same as in step c).
f) Step e) is repeated but the contents of TP-User-Data are different from that used in step e).
g) The SS prompts the operator to indicate the Short Messages stored in the UE.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type n", TP-OA is TPOA1 and RP-OA is RPOA |
|
|
8 |
–> |
CP-ACK |
||
|
9 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
14 |
–> |
SERVICE REQUEST |
||
|
15 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
16 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
17 |
<– |
SECURITY MODE COMMAND |
||
|
18 |
–> |
SECURITY MODE COMPLETE |
||
|
19 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type n", TP-OA is TPOA2 and RP-OA is RPOA1, TP-UD different from step 7 |
|
|
20 |
–> |
CP-ACK |
||
|
21 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
22 |
<– |
CP-ACK |
||
|
23 |
<– |
RRC CONNECTION RELEASE |
|
|
|
24 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
25 |
(void) |
|||
|
26 |
(void) |
|||
|
27 |
(void) |
|||
|
28 |
(void) |
|||
|
29 |
(void) |
|||
|
30 |
(void) |
|||
|
31 |
(void) |
|||
|
32 |
(void) |
|||
|
33 |
(void) |
|||
|
34 |
(void) |
|||
|
35 |
(void) |
|||
|
36 |
(void) |
|||
|
37 |
(void) |
See 3GPP TS34.108 |
||
|
38 |
–> |
SERVICE REQUEST |
||
|
39 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
40 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
41 |
<– |
SECURITY MODE COMMAND |
||
|
42 |
–> |
SECURITY MODE COMPLETE |
||
|
43 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type m", TP-OA is TPOA2 and RP-OA is RPOA, TP-UD different from step 7 and 19 |
|
|
44 |
–> |
CP-ACK |
||
|
45 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
46 |
<– |
CP-ACK |
||
|
47 |
<– |
RRC CONNECTION RELEASE |
||
|
48 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
49 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
50 |
–> |
SERVICE REQUEST |
||
|
51 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
52 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
53 |
<– |
SECURITY MODE COMMAND |
||
|
54 |
–> |
SECURITY MODE COMPLETE |
||
|
55 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type m", TP-OA is TPOA2 and RP-OA is RPOA, TP-UD different from step 43 |
|
|
56 |
–> |
CP-ACK |
||
|
57 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
58 |
<– |
CP-ACK |
||
|
59 |
<– |
RRC CONNECTION RELEASE |
||
|
60 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
61 |
SS |
Prompts the operator to indicate the Short Messages stored in the UE. Only the Short Messages delivered in step 7, 19 and 55 shall be retrievable and indicated |
||
Specific Message Contents
SMS-DELIVER TPDU
|
Information element |
Comment Value |
|
TP-MMS |
no more messages are waiting in SC "1"B |
|
TP-PID |
binary 01000xxx, xxx represents n resp. m (see test method description) |
16.2.7.5 Test requirements
After step 61 only the Short Messages delivered in step 7, 19 and 55 shall be retrieved and indicated.
16.2.8 Test of the reply path scheme
16.2.8.1 Definition
16.2.8.2 Conformance requirement
When a replying UE receives an original mobile terminated short message it has:
– originating SME = TP-Originating Address in the SMS-DELIVER TPDU;
– original SC = RP-Originating Address in the RP-MT-DATA.
When submitting the reply mobile originated short message, the replying UE should use parameters as follows:
– TP-Destination Address in SMS-SUBMIT TPDU = originating SME;
– RP-Destination Address in RP-MO-DATA = original SC.
References
3GPP TS 23.040 3.2.10, 9.2.3.2, 9.2.3.17, Annex D clauses D.5 and D.6.
NOTE: Annex D of 3GPP TS 23.040 is only informative.
16.2.8.3 Test purpose
This procedure verifies that the UE is able to send a Reply Short Message back to the correct originating SME even if in the meantime it receives another Short Message.
16.2.8.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
Support for Short message MO/PP.
The value of timer TC1M.
Test procedure
a) The SS delivers a Short Message as specified in clause 16.2.1, step b) with TP-Reply-Path set to 1.
b) Step a) is repeated but with:
– different TP-Originating-Address for the originating SME;
– different RP-Originating-Address for the original SC; and
– different message contents TP-User-Data.
c) UE sends the Reply Short Message corresponding to one of two received Short Messages (e.g. by means of the MMI).
d) step c) is repeated for the other Short Message.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
2 |
–> |
SERVICE REQUEST |
||
|
3 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
<– |
SECURITY MODE COMMAND |
||
|
6 |
–> |
SECURITY MODE COMPLETE |
||
|
7 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-RP set to 1 |
|
|
8 |
–> |
CP-ACK |
Sent within TC1M after step 7 |
|
|
9 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
10 |
<– |
CP-ACK |
||
|
11 |
<– |
RRC CONNECTION RELEASE |
||
|
12 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
13 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS34.108 |
||
|
14 |
–> |
SERVICE REQUEST |
||
|
15 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
16 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
17 |
<– |
SECURITY MODE COMMAND |
||
|
18 |
–> |
SECURITY MODE COMPLETE |
||
|
19 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-OA, RP-OA and TP-UD different from step 7 |
|
|
20 |
–> |
CP-ACK |
Sent within TC1M after step 7 |
|
|
21 |
–> |
CP-DATA |
Contains RP-ACK RPDU. |
|
|
22 |
<– |
CP-ACK |
||
|
23 |
<– |
RRC CONNECTION RELEASE |
||
|
24 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
25 |
UE |
UE establishes the RRC connection in order to send the Reply Short Message corresponding to one of two received Short Messages |
||
|
26 |
<– |
SYSTEM INFORMATION |
BCCH |
|
|
27 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
28 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
29 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
30 |
–> |
SERVICE REQUEST |
||
|
31 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
32 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
33 |
<– |
SECURITY MODE COMMAND |
||
|
34 |
–> |
SECURITY MODE COMPLETE |
||
|
35 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) RP-DA = RP-OA corresponding to the message TP-DA = TP-OA corresponding to the message |
|
|
36 |
<– |
CP-ACK |
Sent within TC1M after step 35 |
|
|
37 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
38 |
SS |
Waits max 25 s for CP-ACK |
||
|
39 |
–> |
CP-ACK |
||
|
40 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. |
|
|
41 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
|
42 |
UE |
UE establishes the RRC connection in order to send the Reply Short Message corresponding to other Short Message. |
||
|
43 |
<– |
SYSTEM INFORMATION |
BCCH |
|
|
44 |
–> |
RRC CONNECTION REQUEST |
CCCH |
|
|
45 |
<– |
RRC CONNECTION SETUP |
CCCH |
|
|
46 |
–> |
RRC CONNECTION SETUP COMPLETE |
DCCH |
|
|
47 |
–> |
SERVICE REQUEST |
||
|
48 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
49 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
50 |
<– |
SECURITY MODE COMMAND |
||
|
51 |
–> |
SECURITY MODE COMPLETE |
||
|
52 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) RP-DA = RP-OA corresponding to the Message TP-DA = TP-OA corresponding to the message |
|
|
53 |
<– |
CP-ACK |
Sent within TC1M after step 52 |
|
|
54 |
<– |
CP-DATA |
Contains RP-ACK RPDU |
|
|
55 |
SS |
Waits max 25 s for CP-ACK |
||
|
56 |
–> |
CP-ACK |
||
|
57 |
<– |
RRC CONNECTION RELEASE |
RRC connection is released. |
|
|
58 |
–> |
RRC CONNECTION RELEASE COMPLETE |
||
Specific Message Contents
SMS-DELIVER TPDU
|
Information element |
Comment Value |
|
TP-MMS |
no more messages are waiting in SC "1"B |
|
TP-RP |
Reply Path exists "1"B |
16.2.8.5 Test requirements
After step 35 UE shall send the Reply Short Message corresponding to one of two previously received short messages.
After step 52 UE shall send the Reply Short Message corresponding to the other of two previously received short messages.
16.2.9 Multiple SMS mobile originated
16.2.9.1 UE in idle mode
This test is not applicable for R99.
16.2.9.2 UE in active mode
This test is not applicable for R99.
16.2.10 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated short message
16.2.10.1 Definition
16.2.10.2 Conformance requirements
An active UE shall be able to receive a short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is an SMS mobile originated call (SMS-SUBMIT or SMS-COMMAND) in progress.
References
3GPP TS 23.040 clause 3.1, 9.2.3.16.
3GPP TS 24.011 clause 3.2.
16.2.10.3 Test purpose
The test verifies that the UE is capable of simultaneously receiving a network originated SM whilst sending a mobile originated SM.
16.2.10.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in GMM-state "GMM-REGISTERED";
– the SMS message storage shall be empty.
Related ICS/IXIT Statements
Support for Short message MO/PP and MT/PP.
Support for state PDP-ACTIVE of session management.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
Test procedure
a) The SS is configured to receive a mobile originated SM. In clause 16.2.2 steps a) and b) are repeated and, using the end of the CP-DATA message from the UE as a trigger, the SS sends a SM to the UE. In this case a new transaction identifier shall be used in the CP messages of SMS mobile terminated.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
The UE is set up to send an SM |
||
|
2 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”. |
||
|
3 |
(void) |
|||
|
4 |
(void) |
|||
|
5 |
–> |
SERVICE REQUEST |
||
|
6 |
<– |
AUTHENTICATION AND CIPHERING REQUEST |
||
|
7 |
–> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
8 |
SS |
The SS starts integrity protection |
||
|
9 |
||||
|
10 |
–> |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
|
|
11 |
SS |
The SS sends an SM to the UE triggered by the end of the CP-DATA message from the UE |
||
|
12 |
<– |
CP-DATA |
Contains RP-DATA RPDU (SMS DELIVER TPDU) |
|
|
13 |
UE |
The UE shall correctly receive the SM and indicate that a message has arrived. In the MO case the UE shall send the CP-ACK message with transaction identifier assigned to this transfer. In the MT case the UE shall send a CP-ACK message and a CP-DATA message containing the RP-ACK RPDU. The transaction identifier shall be the same as chosen by the SS for the MT transfer. |
||
|
NOTE: Time values for SS wait times are chosen sufficiently high to be sure that the UE has enough time to respond to the different messages. |
||||
Specific Message Contents
SMS SUBMIT TPDU
|
Information element |
Comment Value |
|
TP-UDL |
as applicable |
|
TP-UD (140 octets) |
160 ASCII characters |
16.2.10.5 Test requirements
After step 12 UE shall correctly receive the SM and indicate that a message has arrived.